Summary:	ASTERISK-01043: Secondary Zap Channel Zap/X-2 gets locked in weird state
Reporter:	sbisker (sbisker)	Labels:
Date Opened:	2004-02-17 09:31:25.000-0600	Date Closed:	2004-09-25 02:53:45
Priority:	Minor	Regression?	No
Status:	Closed/Complete	Components:	Core/General
Versions:		Frequency of Occurrence
Related Issues:
Environment:		Attachments:
Description:	Every few days, I have a couple of Zap channels that go into a weird state.  In the debug log, their is a message that their is already dsp on Zap/X-2.  The end-user symptom is that when they pickup the handset they hear audio audio on their handset, but the remote party can't hear them.  If you do a show channels, the channel is not in use.  If you do a Zap show channel, the Actual Confinfo line shows that their is audio on the line.  It seems to be related to flashhook.  Soft hangup doesn't work, because their is no record of the channel in show channels.  If you need any more info, let me know ****** STEPS TO REPRODUCE ****** Wait until it happens ****** ADDITIONAL INFORMATION ****** Zap show channel 47 Here's the output of zap show channel 37 File Descriptor: 111 Span: 2 Extension: Context: longdistance Caller ID string: "Bad Extension" <5239> Destroy: 0 Signalling Type: FXO Kewlstart Owner: <None> Real: <None> Callwait: <None> Threeway: <None> Confno: -1 Propagated Conference: -1 Real in conference: 0 DSP: no Relax DTMF: no Dialing/CallwaitCAS: 0/0 Default law: ulaw Fax Handled: no Pulse phone: no Echo Cancellation: 128 taps, currently OFF Actual Confinfo: Num/161, Mode/0x0009 Actual Confmute: No Debug info. Feb 13 08:52:03 DEBUG[22642704]: Already have a dsp on Zap/47-2? Feb 13 08:52:03 DEBUG[22642704]: Swapping 2 and 0 Feb 13 08:52:03 DEBUG[22642704]: disabled echo cancellation on channel 47 Feb 13 08:52:03 DEBUG[22642704]: Updated conferencing on 47, with 0 conference users Feb 13 08:52:04 DEBUG[114696]: Setting NAT on RTP to 0 Feb 13 08:52:04 DEBUG[22675479]: DTMF digit: 5 on Zap/47-2 Feb 13 08:52:04 DEBUG[22675479]: DTMF digit: 2 on Zap/47-2 Feb 13 08:52:04 DEBUG[114696]: Stopping retransmission on '6ee60da77cac5d7850468a810ab118db@192.168.1.15' of Request 102 : Found Feb 13 08:52:05 DEBUG[22675479]: DTMF digit: 2 on Zap/47-2 Feb 13 08:52:05 DEBUG[22675479]: DTMF digit: 0 on Zap/47-2 Feb 13 08:52:05 DEBUG[22675479]: Enabled echo cancellation on channel 47 Feb 13 08:52:06 DEBUG[22675479]: SIMPLE DIAL (NO URL) Feb 13 08:52:06 DEBUG[22675479]: Received AST_CONTROL_PROGRESS on Zap/47-2 Feb 13 08:52:06 DEBUG[22675479]: Received AST_CONTROL_PROGRESS on Zap/47-2 Feb 13 08:52:07 DEBUG[114696]: Stopping retransmission on '4995acef6ddb20401473880170e65589@192.168.1.15' of Request 102 : Found Feb 13 08:52:07 DEBUG[114696]: Stopping retransmission on '97f390d0-49231a66-2ed2b201@192.168.0.28' of Request 142: Foun d Feb 13 08:52:08 DEBUG[22675479]: Exception on 111, channel 47 Feb 13 08:52:08 DEBUG[22675479]: Got event On hook(1) on channel 47 (index 0) Feb 13 08:52:08 DEBUG[22675479]: Last flash was 4370 ms ago Feb 13 08:52:08 DEBUG[22675479]: Received AST_CONTROL_PROGRESS on Zap/169-1 Feb 13 08:52:08 DEBUG[22675479]: Planning to masquerade Zap/169-1 into the structure of Zap/47-2 Feb 13 08:52:08 DEBUG[22675479]: Done planning to masquerade Zap/47-2 into the structure of Zap/169-1 Feb 13 08:52:08 DEBUG[22675479]: Swapping 2 and 0 Feb 13 08:52:08 DEBUG[22675479]: Released sub 2 of channel 47 Feb 13 08:52:08 DEBUG[22675479]: Actually Masquerading Zap/169-1(6) into the structure of Zap/47-2(5) Feb 13 08:52:08 DEBUG[22675479]: Got clone lock on 'Zap/169-1' at 0x419eac28 Feb 13 08:52:08 DEBUG[22675479]: New owner for channel 47 is Zap/169-1<MASQ> Feb 13 08:52:08 DEBUG[22675479]: Updated conferencing on 47, with 0 conference users Feb 13 08:52:08 DEBUG[22675479]: Hangup: channel: 47 index = -1, normal = 111, callwait = -1, thirdcall = -1 Feb 13 08:52:08 DEBUG[22675479]: Released clone lock on 'Zap/47-2<ZOMBIE>'
Comments:	By: twisted (twisted) 2004-03-24 19:57:11.000-0600 Is this still an issue? By: sbisker (sbisker) 2004-03-29 15:37:09.000-0600 I have since disabled call-waiting and the problem went away.  After looking into it further, it looked like a T/R wiring problem.  You can close. By: twisted (twisted) 2004-03-29 17:09:23.000-0600 Reported fixed due to error in wiring/setup by sbisker.