[asterisk-bugs] [JIRA] (ASTERISK-23086) pjsip aor record name must match username for successful registration

[Abhay Gupta (JIRA)]

    [ https://issues.asterisk.org/jira/browse/ASTERISK-23086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=225093#comment-225093 ] 

Abhay Gupta commented on ASTERISK-23086:
----------------------------------------

This is obviously a bug because if the need is that endpoint and aors category is same like 200 / 200 in the above example then the same cannot be created from Asterisk manager API . It gives the error category not created .

So something needs to be done to ensure that manager API is not broken with pjsip.conf 

> pjsip aor record name must match username for successful registration
> ---------------------------------------------------------------------
>
>                 Key: ASTERISK-23086
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-23086
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Resources/res_pjsip_registrar
>    Affects Versions: 12.0.0
>            Reporter: Scott Griepentrog
>            Severity: Minor
>
> The record name for an AOR type entry is being used to match the username on inbound registration requests (see res/res_pjsip_registrar.c:527).  This prevents using a more descriptive name for the AOR record.
> This will not successfully register an endpoint that has username 200:
> {noformat}
> [200]
> type=endpoint
> ...
> aors=200-aor
> [200-aor]
> type=aor
> max_contacts=1
> contact=sip:200 at example.com:5060
> {noformat}
> This will register the same endpoint:
> {noformat}
> [200]
> type=endpoint
> ...
> aors=200
> [200]
> type=aor
> max_contacts=1
> contact=sip:200 at example.com:5060
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.2#6252)