Summary:	ASTERISK-12348: Caller gets dropped and engaged tone after two Zap channels bridged.
Reporter:	Russell Brown (ruffle)	Labels:
Date Opened:	2008-07-09 09:21:57	Date Closed:	2011-06-07 14:03:00
Priority:	Major	Regression?	No
Status:	Closed/Complete	Components:	Core/Channels
Versions:		Frequency of Occurrence
Related Issues:
Environment:		Attachments:	( 0) failed-call.log ( 1) zaptel.conf
Description:	I have an ISDN PBX (Network Alchemy Argent Office) on Span 2 of a Wildcard TE205P with a British Telecom ISDN 30 on Span 1.  This configuration has been working well for ages and nothing has changed on the ISDN PBX. Using Asterisk 1.4.21.1 and Zaptel-1.4.11 when a call is made from the ISDN PBX the caller hears ring tone, the called party answers and the caller then hears the busy tone and the called party hears nothing. The channels remain bridged for a couple of minutes. Here's the output of show channels when it's in this state: asterisk*CLI> show channels Channel              Location             State   Application(Data) Zap/2-1              (None)               Up      Bridged Call(Zap/46-1) Zap/46-1             01780XXXX81@alchemy: Up      Dial(Zap/g1/01780XXXX81|9999) 2 active channels 1 active calls asterisk*CLI> This doesn't happen to all of the calls.... just most of them :-( I have attached the verbose=9 logging output of a failed call and my zaptel.conf (itself unchanged for ages). I'm happy to turn on whatever debugging is needed, provide traces/output and apply patches if needed.
Comments:	By: Russell Brown (ruffle) 2008-07-11 04:22:49 I've reverted to zaptel 1.4.9.2 and the problem seems to have gone away. What debug would help with this? By: Leif Madsen (lmadsen) 2008-12-05 08:48:37.000-0600 Hey ruffle (and also hello sruffell!) Sorry this issue hasn't been moved forward. Let me try and help it along a bit. First, do you still get this same issue on the latest DAHDI release? If so, I'm going to ask for the PRI debug information from the Asterisk CLI. I have good luck in attaching to the CLI and piping the output into tee: asterisk -rvvv | tee /tmp/my_debug_output.txt Lets start with that, and perhaps sruffell will have some better ideas for us. If this is resolved in the latest DAHDI, let me know, and I'll just close this bug out. Thanks! By: Tilghman Lesher (tilghman) 2009-02-26 12:21:02.000-0600 No response from reporter in 3 months.