[Home]

Summary:ASTERISK-24675: IAX2 sees peer as not connected but replies to POKE
Reporter:Y Ateya (yateya)Labels:
Date Opened:2015-01-10 14:18:56.000-0600Date Closed:2015-02-21 11:05:43.000-0600
Priority:MajorRegression?
Status:Closed/CompleteComponents:Channels/chan_iax2
Versions:13.1.0 Frequency of
Occurrence
Occasional
Related
Issues:
Environment:Ubuntu 12.04; built from source.Attachments:( 0) iax_peer1.conf
( 1) iax_peer2.conf
( 2) iax2_disconnect_peer1.pcap
( 3) iax2_disconnect_peer2.pcap
Description: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.
Comments:By: Rusty Newton (rnewton) 2015-01-30 09:47:55.789-0600

Looks like you forgot to attach the  iax_client_disappear.log

By: Rusty Newton (rnewton) 2015-01-30 09:48:28.037-0600

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

The debug log and IAX trace should correspond with a new pcap, so that we can compare the two.

By: Rusty Newton (rnewton) 2015-01-30 09:49:12.337-0600

Be sure the debug log you provide also includes an IAX trace "iax2 set debug on" I believe.

By: Matt Jordan (mjordan) 2015-02-21 11:05:52.349-0600

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