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

[Birger "WIMPy" Harzenetter (JIRA)]

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

Birger "WIMPy" Harzenetter commented on ASTERISK-24549:
-------------------------------------------------------

It happened several times while reconfiguring Asterisk, but now that I try to reproduce it, it fails to fail.
But I captured the exact opposite issue last week.
The *CLI reported a peer as UNREACHABLE and while I was trying to find out where it had gone, I found that my ststus display, which listens on AMI, changed it to green again, yet the *CLI never reported it as REACHABLE again.
Several minutes earlier another peer had a small glitch but there both messages appeared.

[Nov 26 13:36:31] NOTICE[30448]: chan_iax2.c:12387 __iax2_poke_noanswer: Peer 'hbc-pgsw' is now UNREACHABLE! Time: 56
[Nov 26 13:36:37] NOTICE[30448]: chan_iax2.c:11217 socket_process_helper: Peer 'hbc-pgsw' is now REACHABLE! Time: 56
[Nov 26 13:59:19] NOTICE[30447]: chan_iax2.c:12387 __iax2_poke_noanswer: Peer 'hbc-grau' is now UNREACHABLE! Time: 58

'iax2 show peers' showed it as OK as well, but no further message ever appeared.


> 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)