[asterisk-bugs] [JIRA] (ASTERISK-27996) PJSIP: match_header endpoint matching does not support inbound registration
Joshua C. Colp (JIRA)
noreply at issues.asterisk.org
Fri Jun 24 07:31:49 CDT 2022
[ https://issues.asterisk.org/jira/browse/ASTERISK-27996?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=259541#comment-259541 ]
Joshua C. Colp commented on ASTERISK-27996:
-------------------------------------------
The issue remains open, so there has been no change that has gone in mentioning it.
> PJSIP: match_header endpoint matching does not support inbound registration
> ---------------------------------------------------------------------------
>
> Key: ASTERISK-27996
> URL: https://issues.asterisk.org/jira/browse/ASTERISK-27996
> Project: Asterisk
> Issue Type: Bug
> Security Level: None
> Components: Resources/res_pjsip, Resources/res_pjsip_endpoint_identifier_ip, Resources/res_pjsip_registrar
> Affects Versions: 13.21.1
> Reporter: Edvin Vidmar
> Labels: pjsip, webrtc
> Attachments: output.txt, pjsip.conf
>
>
> Hi,
> I try to register webrtc client with identify set to header but it doesn’t work. I have attached pjsip.conf and asterisk cli output.
> From configuration you can see that {{match_header}} is set to {{From-WebRTC: 2000}} and from sip log you can see {{From-WebRTC}} header is set correctly, but I always get following error:
> {noformat}
> res_pjsip_registrar.c:967 find_registrar_aor: AOR ‘’ not found for endpoint ‘2000-webrtc’
> {noformat}
> Error says that AOR ‘’ is not found, but from config you can see that AOR is set and also if I check in asterisk cli it all looks OK.
> Also if I change the endpoint's {{identify_by=header}} to {{identify_by=username}} it works ok. So it looks like problem with header identification.
> br
> edvin
> https://community.asterisk.org/t/aor-not-found-for-endpoint-2000-webrtc/75366
--
This message was sent by Atlassian JIRA
(v6.2#6252)
More information about the asterisk-bugs
mailing list