[asterisk-bugs] [Asterisk 0015433]: crash / call forwarding possibly due to loop detection - 1.4.26rc4

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=15433 
====================================================================== 
Reported By:                zerohalo
Assigned To:                mnicholson
====================================================================== 
Project:                    Asterisk
Issue ID:                   15433
Category:                   Core/Channels
Reproducibility:            have not tried
Severity:                   crash
Priority:                   normal
Status:                     assigned
Asterisk Version:           1.4.26-rc4 
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-07-01 13:41 CDT
Last Modified:              2009-10-08 14:45 CDT
====================================================================== 
Summary:                    crash / call forwarding possibly due to loop
detection - 1.4.26rc4
Description: 
I'm not sure how to interpret this one. It appears that a customer PBX was
forwarded to itself from an outside number, causing a crash.

CLI right up to the crash:

[Jul 1 12:33:19] VERBOSE[16909] logger.c: -- Executing
[s at CONTEXT_REMOVED:22] Dial("SIP/gateway1-b66b22e0", "SIP/5555555555|70|r")
in new stack
[Jul 1 12:33:19] VERBOSE[10250] logger.c: -- Got SIP response 482 "Loop
Detected" back from XX.XXX.XXX.XX
[Jul 1 12:33:19] VERBOSE[16910] logger.c: -- Now forwarding
SIP/5555555555-b637f1a8 to 'Local/3333333333 at inbound' (thanks to
SIP/server1-08f125c0)
[Jul 1 12:33:19] VERBOSE[16909] logger.c: -- Called 5555555555
[Jul 1 12:33:19] VERBOSE[10250] logger.c: -- Got SIP response 482 "Loop
Detected" back from XX.XXX.XXX.XX
[Jul 1 12:33:19] WARNING[16910] channel.c: PBX may not have been
terminated properly on 'SIP/server1-08f125c0'
[Jul 1 12:33:19] VERBOSE[16912] logger.c: -- Executing
AppendCDRUserField("Local/3333333333 at inbound-2a8e,2", "DST=3333333333|")
[Jul 1 12:33:19] WARNING[16911] channel.c: Unable to write to alert
pipe on (qlen = 0): Bad file descriptor!
[Jul 1 12:33:19] WARNING[16911] channel.c: Unable to write to alert
pipe on (qlen = 1): Bad file descriptor!
[Jul 1 12:33:19] VERBOSE[16911] logger.c: -- Executing
AppendCDRUserField("", "D=3333333333|")
[Jul 1 12:33:19] WARNING[10548] channel.c: read() failed: Bad file
descriptor
[Jul 1 12:33:19] WARNING[10548] channel.c: read() failed: Is a directory
[Jul 1 12:33:19] WARNING[10548] channel.c: read() failed: Bad file
descriptor

backtrace attached

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

---------------------------------------------------------------------- 
 (0112064) zerohalo (reporter) - 2009-10-08 14:45
 https://issues.asterisk.org/view.php?id=15433#c112064 
---------------------------------------------------------------------- 
attached is what I got from the messages log from a second crash that
happened within ten minutes of the last one. The files referenced do exist
- This machine is running 1.4.26.2 w/ filestream_frisolate-1.4.diff2.txt
from https://issues.asterisk.org/view.php?id=15609. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-10-08 14:45 zerohalo       Note Added: 0112064                          
======================================================================