[asterisk-bugs] [JIRA] (ASTERISK-24675) IAX2 sees peer as not connected but replies to POKE

[Matt Jordan (JIRA)]

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

Matt Jordan commented on ASTERISK-24675:
----------------------------------------

Suspended due to lack of activity. Please request a bug marshal in #asterisk-bugs on the IRC network irc.freenode.net to reopen the issue should you have the additional information requested. Further information on issue tracker usage can be found in the Asterisk Issue Guidlines [1].

[1] https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines



> IAX2 sees peer as not connected but replies to POKE
> ---------------------------------------------------
>
>                 Key: ASTERISK-24675
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-24675
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Channels/chan_iax2
>    Affects Versions: 13.1.0
>         Environment: Ubuntu 12.04; built from source.
>            Reporter: Y Ateya
>            Assignee: Rusty Newton
>         Attachments: iax2_disconnect_peer1.pcap, iax2_disconnect_peer2.pcap, iax_peer1.conf, iax_peer2.conf
>
>
> In a test setup; I was trying to stress test IAX2 connection. So I sent a lot of calls (using sipp). After sometime maxcallnumber reached (see iax_client_disappear.log). After some more time peer2 became absent.
> Peer2 can see peer1 (iax2 show peers display it as connected). But peer1 see that peer2 is disconnected (status = UNKOWN).
> What I can see from the wireshark capture is that peer2 sends POKE to peer1; peer1 replies with PONG even while it sees that peer2 status is UNKOWN.
> Attached iax configurations in both sides and wireshark capture from both sides.
> Note that if peer1 didn't reply to peer2; peer2 will be fully disconnected. When peer2 sees that it is disconnected; It will try to re-register. 



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