[asterisk-bugs] [Asterisk 0012215]: 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:                     new
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-08-28 11:45 CDT
====================================================================== 
Summary:                    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...
====================================================================== 

---------------------------------------------------------------------- 
 (0091875) mneuhauser (reporter) - 2008-08-28 11:45
 http://bugs.digium.com/view.php?id=12215#c91875 
---------------------------------------------------------------------- 
I've attached asterisk-1.4.19-chan_sip-loop-detection-fix.patch that
implements the fix(?) outlined above. While going through chan_sip, I've
seen a lot of checks for p->owner->_state ==/!= AST_STATE_UP -- I've got a
feeling that at least some of these (could have similar problems as the
loop check), maybe they should check the new flag instead of the _state 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2008-08-28 11:45 mneuhauser     Note Added: 0091875                          
======================================================================