[asterisk-bugs] [Asterisk 0012215]: [patch] Asterisk returns 482 Loop Detected upon receiving re-invite

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=12215 
====================================================================== 
Reported By:                jpyle
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   12215
Category:                   Channels/chan_sip/General
Reproducibility:            random
Severity:                   minor
Priority:                   normal
Status:                     confirmed
Asterisk Version:           1.4.18 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             2008-03-14 11:45 CDT
Last Modified:              2008-11-14 08:33 CST
====================================================================== 
Summary:                    [patch] Asterisk returns 482 Loop Detected upon
receiving re-invite
Description: 
Asterisk sends a 482 Loop Detected upon receiving a presumably valid
re-INVITE.  Pedantic is enabled globally in sip.conf.
======================================================================
Relationships       ID      Summary
----------------------------------------------------------------------
duplicate of        0007403 [patch] allow SIP Spiral to work instea...
====================================================================== 

---------------------------------------------------------------------- 
 (0094897) mneuhauser (reporter) - 2008-11-14 08:33
 http://bugs.digium.com/view.php?id=12215#c94897 
---------------------------------------------------------------------- 
Sorry, but I can see nothing suspicious in that trace. Anyhow, the changes
in my patch can not be responsible for the behaviour you see: the only
thing it CAN do wrong, is to not detect an actual loop (look at the code,
it just adds one &&-clause to the if condition for the loop-detected
case).

But it could be that another timing sensitive bug is exposed by fixing the
loop-detection problem (in the original Asterisk, it would have been
mis-detected as a loop and the new bug would not have had a chance to
manifest itself). 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2008-11-14 08:33 mneuhauser     Note Added: 0094897                          
======================================================================