[asterisk-bugs] [Asterisk 0010829]: __zt_exception: We're Zap/1-1, not (null)

[noreply at bugs.digium.com]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=10829 
====================================================================== 
Reported By:                deeperror
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   10829
Category:                   Channels/chan_zap
Reproducibility:            always
Severity:                   crash
Priority:                   normal
Status:                     new
Asterisk Version:           1.4.11  
SVN Branch (only for SVN checkouts, not tarball releases): N/A  
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             09-26-2007 16:16 CDT
Last Modified:              12-05-2007 10:30 CST
====================================================================== 
Summary:                    __zt_exception: We're Zap/1-1, not (null)
Description: 
I get the following error:

[Sep 26 17:21:10] WARNING[9094]: chan_zap.c:4585 __zt_exception: We're
Zap/1-1, not (null)

The error is an endless loop and quickly fills log files with thousands of
lines.  

This occurs during a 3 way call.  

Callee A answers and is put on hold.

Callee B answers and is talking to caller.

Callee A hangs up before Callee B is added to the conference.

When flash is pressed to create the 3 way no one is there.  Caller then
tries to call back callee A by hanging up the telephone and the errors
occur.


====================================================================== 

---------------------------------------------------------------------- 
 Corydon76 - 12-05-07 10:30  
---------------------------------------------------------------------- 
Please test the patch in http://bugs.digium.com/view.php?id=9660 to see if it
solves the causing issue. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
12-05-07 10:30  Corydon76      Note Added: 0074821                          
======================================================================