Summary:	ASTERISK-23086: pjsip aor record name must match username for successful registration
Reporter:	Scott Griepentrog (sgriepentrog)	Labels:
Date Opened:	2014-01-02 15:46:24.000-0600	Date Closed:	2014-01-02 16:21:38.000-0600
Priority:	Minor	Regression?
Status:	Closed/Complete	Components:	Resources/res_pjsip_registrar
Versions:	12.0.0	Frequency of Occurrence
Related Issues:
Environment:		Attachments:
Description:	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@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@example.com:5060 {noformat}
Comments:	By: Rusty Newton (rnewton) 2014-01-02 16:21:38.909-0600 This isn't a bug. It is documented here https://wiki.asterisk.org/wiki/display/AST/Configuring+res_pjsip in the AOR section and from our talks in chat, it sounds like you are already updating the pjsip.conf.sample file to be clear on the subject. By: Abhay Gupta (agupta) 2015-02-25 07:23:19.255-0600 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 By: Abhay Gupta (agupta) 2015-02-25 07:36:10.516-0600 Or else pls let me know how to create such endpoint from AMI By: Rusty Newton (rnewton) 2015-02-25 14:16:52.804-0600 Don't post about a new issue on a closed issue. Your comment and the new issue could go unnoticed. This issue ASTERISK-23086 does not represent a bug in itself. It is this way by design. If this causes an issue with something else, such as an AMI command then you should file a new issue demonstrating the problem and provide debug for us to reproduce the issue.