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

Jason Hord (JIRA) noreply at issues.asterisk.org
Mon Sep 24 15:28:56 CDT 2018


     [ https://issues.asterisk.org/jira/browse/ASTERISK-28056?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jason Hord updated ASTERISK-28056:
----------------------------------

    Attachment: full

Here is the log with verbose/debug set to '4'.  During this run, here is what I saw:

Endpoint 555-Nihil came online and showed available on the contact and endpoint as well as showing the correct device status in a queue.

Endpoint 999-Nihil remained unavailable until the device re-registered.  At that point the endpoint and contact were both marked as available, but after some time the endpoint went unavailable.  The contact was still available but the device status in the queue was incorrect.

I keep seeing log messages like the following:

{noformat}
Endpoint 'XXX' has no AORs feeding it, setting it to offline state as default
{noformat}

I'm not sure why this is the case since all of the AORs and Endpoints should be configured in our realtime database.  It seems there is something amiss with the matching and I can't tell if it's a bug or config issue.  This is a working configuration for 15.2.2, however.


> 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: 16.0.0
>            Reporter: Jason Hord
>            Assignee: Jason Hord
>              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)



More information about the asterisk-bugs mailing list