[asterisk-bugs] [Asterisk 0016066]: channel.c:2711 __ast_read: Exception flag set on 'SIP/xxx', but no exception handler

[Asterisk Bug Tracker]

The following issue has been UPDATED. 
====================================================================== 
https://issues.asterisk.org/view.php?id=16066 
====================================================================== 
Reported By:                Micc
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   16066
Category:                   Channels/General
Reproducibility:            random
Severity:                   major
Priority:                   normal
Status:                     new
Asterisk Version:           1.6.1.6 
JIRA:                        
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2009-10-13 16:17 CDT
Last Modified:              2010-05-07 13:05 CDT
====================================================================== 
Summary:                    channel.c:2711 __ast_read: Exception flag set on
'SIP/xxx', but no exception handler
Description: 
I'm running asterisk 1.6.1.6 and have been seeing this problem for about a
week or two. This happens seemingly randomly and on different channels. And
when it happens it fills the logs and the CLI with these messages as fast
as it can, jumping the cpu way up, probably 100% on one core.

I will try to get a sip debug when it happens, but I wanted to at least
get this on the issue tracker in case someone already knows what it is.
====================================================================== 

---------------------------------------------------------------------- 
 (0121574) Micc (reporter) - 2010-05-07 13:05
 https://issues.asterisk.org/view.php?id=16066#c121574 
---------------------------------------------------------------------- 
I just had this problem happen again and I'm running 1.6.1.18. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-05-07 13:05 Micc           Note Added: 0121574                          
2010-05-07 13:05 Micc           Status                   closed => new       
2010-05-07 13:05 Micc           Resolution               fixed => reopened   
======================================================================