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

Rusty Newton (JIRA) noreply at issues.asterisk.org
Fri Dec 5 08:33:29 CST 2014


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

Rusty Newton commented on ASTERISK-24549:
-----------------------------------------

I'm not sure we have much to go on here without a DEBUG log or being able to reproduce it reliably.

How difficult is it to reproduce and can you provide an example configuration to do so?

> 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
>            Assignee: 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