[asterisk-bugs] [JIRA] (ASTERISK-27402) AMI generating incorrect ContactStatus events
Jared Hull (JIRA)
noreply at issues.asterisk.org
Wed Nov 8 12:05:27 CST 2017
[ https://issues.asterisk.org/jira/browse/ASTERISK-27402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jared Hull updated ASTERISK-27402:
----------------------------------
Description:
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 contain 110, then it sends events for those endpoints at the same time with the same ContactStatus and RoundtripUsec as 110 has. It does not generate events for 1110 and 7110 at all, even if 110 is unavailable. Endpoint 1101 is matched for both endpoints 110 and 101.
was:
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 end in 110, then it sends events for those endpoints at the same time with the same ContactStatus and RoundtripUsec as 110 has. It does not generate events for 1110 and 7110 at all, even if 110 is unavailable. Endpoint 1101 is not effected, only endpoints which end with 110.
> 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
> Components: Resources/res_pjsip
> 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 contain 110, then it sends events for those endpoints at the same time with the same ContactStatus and RoundtripUsec as 110 has. It does not generate events for 1110 and 7110 at all, even if 110 is unavailable. Endpoint 1101 is matched for both endpoints 110 and 101.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
More information about the asterisk-bugs
mailing list