[asterisk-bugs] [JIRA] (ASTERISK-28388) Endpoint sync causes device unreach when a new contact is added

[Jason Hord (JIRA)]

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

Jason Hord updated ASTERISK-28388:
----------------------------------

    Attachment: full
                asterisk-16.3.0-sync-endpoint.diff

I have included a patch which fixes this issue for me.  I have no idea if this even close to the correct solution.

I've also included a full log which shows the reported issue.  When endpoint 111-Nihil comes online, it knocks multiple other endpoints offline.  This includes endpoint 555-Nihil which is a completely separate device on a completely separate AOR that was valid at the time.


> Endpoint sync causes device unreach when a new contact is added
> ---------------------------------------------------------------
>
>                 Key: ASTERISK-28388
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-28388
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Resources/res_pjsip
>    Affects Versions: 16.3.0
>            Reporter: Jason Hord
>              Labels: patch
>         Attachments: asterisk-16.3.0-sync-endpoint.diff, full
>
>
> I am seeing unrelated endpoints being set to unavailable when a contact is added to a completely different endpoint.  As best I can tell from the code this is because an endpoint sync happens when the contact is added.  This causes an AOR search which marks every other endpoint as unreachable.  The unrelated endpoints are skipped which means the task_data structure is never initialized properly.  After the loop exits, a check is made to see if an endpoint compositor was found and if not, the endpoint is marked offline.  In my scenario, I can't see how the task_data structure would ever be valid for endpoints that match the filter criteria.



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