[asterisk-bugs] [JIRA] (ASTERISK-24549) on 'iax2 reload' all peers are annonced as unreachable via AMI

Matt Jordan (JIRA) noreply at issues.asterisk.org
Sun Nov 23 19:53:28 CST 2014


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

Matt Jordan commented on ASTERISK-24549:
----------------------------------------

We require a complete debug log to help triage the issue. This document will provide instructions on how to collect debugging logs from an Asterisk machine for the purpose of helping bug marshals troubleshoot an issue: https://wiki.asterisk.org/wiki/display/AST/Collecting+Debug+Information



> on 'iax2 reload' all peers are annonced as unreachable via AMI
> --------------------------------------------------------------
>
>                 Key: ASTERISK-24549
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-24549
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Channels/chan_iax2
>    Affects Versions: 11.14.0
>         Environment: Listening for status information on AMI
>            Reporter: Birger "WIMPy" Harzenetter
>            Severity: Minor
>
> After doing an 'iax2 reload' you get extensionstatus 4 events for all peers. Unfortunately they don't clear on the next successful qualify.
> So if you track the state of your peers, they stay in the unreachable state until the next call passes on that peer.



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



More information about the asterisk-bugs mailing list