Summary:ASTERISK-19644: Loss of audio while running ChanSpy() on a specific prefix; channel gets stuck permanently.
Reporter:Robert Dailey (rdailey)Labels:
Date Opened:2012-04-05 23:33:52Date Closed:2012-04-24 14:56:05
Versions: Frequency of
Environment:CentOS (AsteriskNOW)Attachments:( 0) ASTERISK-19644_Backtrace.txt
Description:When I run ChanSpy() on a specific prefix to monitor incoming calls from the ITSP, eventually ChanSpy() is no longer attaching to new channels as they are created and the call (to chanspy) goes silent on the phone.  Sometimes it happens after just several minutes of spying on calls coming and going, sometimes it takes hours and a hundred calls have come and gone.  The time it takes to lose audio and stop cycling to new channels automatically is always random.  While there are several concurrent calls matching the prefix, I cycle them manually with the * key.  Asterisk always reports that it is done spying on one channel and is attaching to a new channel when I cycle manually.  When I lose audio, pressing * no longer causes any done spying and attaching messages in the CLI.

When I hang up the phone, the channel remains open on asterisk.  A message about the SIP channel being destroyed appears about 30 seconds after I hang up the phone, but the channel remains stuck on asterisk forever.

[Apr  5 14:21:06] WARNING[29147]: chan_sip.c:3873 __sip_autodestruct: Autodestruct on dialog '64d489e23f10a7e65a5cf8952a6acdac@' with owner in place (Method: BYE)

This sip_autodestruct never appears until after I hang up my phone AFTER the spy has lost audio.  When it loses audio, I always wait a while to see if it ever regains audio when the next channel begins.  When several new calls come and there has been no audio, I hang up the phone.  Then the autodestruct message shows up, and the channel remains stuck even though my call has ended.

The stuck channel does not respond to channel request hangup.  The gdb backtrace is below.

[Edited by mjordan]
Put gdb backtrace in attached file
Comments:By: Matt Jordan (mjordan) 2012-04-10 09:23:05.347-0500

Please don't place logs or backtraces inline in the issue text, unless they're to illustrate a specific point.  For large dumps of data, file attachments are preferred :-)

By: Matt Jordan (mjordan) 2012-04-10 09:24:34.692-0500

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

If you can collect a DEBUG log illustrating a channel leading up to the point where it fails to get destructed and ChanSpy stops working, that would help us debug this issue.  You may also want to generate the log with 'sip set debug on'.

By: Matt Jordan (mjordan) 2012-04-24 14:55:54.938-0500

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 can be found at http://www.asterisk.org/developers/bug-guidelines