[asterisk-bugs] [JIRA] (ASTERISK-28056) res_pjsip: Incorrect endpoint status after endpoint synchronization for a specific AOR

[Jesse Ross (JIRA)]

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

Jesse Ross edited comment on ASTERISK-28056 at 2/13/20 10:18 AM:
-----------------------------------------------------------------

Hi, I believe I am running into this error as well on Asterisk 13.30.0. On 13.20.0, it is working fine. It looks like the commit "pjsip: Rewrite OPTIONS support with new eyes." that is related to this was added around 13.22.0.

I'm using a realtime database for all endpoints, auths, aors, contacts. When I add a new endpoint, then register to it, other registered endpoints become unreachable.

I have a log with debug set to 10 with a few endpoints on a test server that I can upload if you want.

I see the same message: 
{{Endpoint 'XXX' has no AORs feeding it, setting it to offline state as default}}

And reloading res_pjsip.so or restarting all clients fixes it.


was (Author: jmross):
Hi, I believe I am running into this error as well on Asterisk 13.30.0. On 13.20.0, it is working fine. It looks like the commit "pjsip: Rewrite OPTIONS support with new eyes." that is related to this was added around 13.22.0.

I'm using a realtime database for all endpoints, auths, aors, contacts. When I add a new endpoint, then register to it, other registered endpoints become unreachable.

I have a log with debug set to 10 with a few endpoints on a test server that I can upload if you want.

I see the same message: "Endpoint 'XXX' has no AORs feeding it, setting it to offline state as default"

And reloading res_pjsip.so or restarting all clients fixes it.




> res_pjsip: Incorrect endpoint status after endpoint synchronization for a specific AOR
> --------------------------------------------------------------------------------------
>
>                 Key: ASTERISK-28056
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-28056
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Resources/res_pjsip
>    Affects Versions: 13.22.0, 15.6.0, 16.0.0
>            Reporter: Jason Hord
>            Assignee: Unassigned
>              Labels: patch, pjsip
>         Attachments: 555-aor.txt, 555-endpoint.txt, 999-aor.txt, 999-endpoint.txt, full, pjsip_options-aor.diff
>
>
> I have two devices configured but am unable to get them to both consistently qualify after starting Asterisk.  I see the endpoint and AOR for the first device become reachable as expected, but as the second device is being qualified, the endpoint for the first device is marked as 'Unavailable'.  The contact and AOR for both devices are reachable, however.
> Based on my digging through the source code and logs, I believe this happens when sip_options_synchronize_endpoint() (res/res_pjsip/pjsip_options.c) is called for a specific AOR.  When called, it appears as though non-matching AORs are checked to see if they have an endpoint state compositor and will be set to an 'Unavailable' status if one is not present.  My thought is that this is what is setting the first endpoint to unavailable although I'm not sure why this would be the case.
> I have included a small patch that resolves the issue for me, but I don't know if it is the correct solution.  Any guidance would be appreciated.
> Thank-you.



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