[asterisk-bugs] [JIRA] (ASTERISK-27402) AMI generating incorrect ContactStatus events

[Asterisk Team (JIRA)]

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

Asterisk Team commented on ASTERISK-27402:
------------------------------------------

Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution.

A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report.

Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process].

> AMI generating incorrect ContactStatus events
> ---------------------------------------------
>
>                 Key: ASTERISK-27402
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-27402
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>    Affects Versions: 14.6.0, 15.0.0, 15.1.0
>            Reporter: Jared Hull
>            Severity: Minor
>         Attachments: ami_events.txt, pjsip.conf.txt, pjsip_show_endpoints_and contacts.txt
>
>
> See attached ami_events.txt, Asterisk sends these events all at once.
> pjsip.conf.txt is my endpoint configuration, they all have different AORs.
> pjsip_show_endpoints_and contacts.txt shows that Asterisk knows the AORs and contacts are separate.
> It is as if Asterisk sees 110 and searches all endpoints for matches which include 110, then it sends events for those endpoints at the same time with the same ContactStatus and RoundtripUsec. It does not generate events for 1110 and 7110 at all, even if 110 is unavailable.



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