[asterisk-bugs] [Asterisk 0007403]: [patch] allow SIP Spiral to work instead of causing a '482 Loop Detected' condition

[noreply at bugs.digium.com]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=7403 
====================================================================== 
Reported By:                stephen_dredge
Assigned To:                putnopvut
====================================================================== 
Project:                    Asterisk
Issue ID:                   7403
Category:                   Channels/chan_sip/General
Reproducibility:            N/A
Severity:                   tweak
Priority:                   normal
Status:                     assigned
Asterisk Version:            SVN 
SVN Branch (only for SVN checkouts, not tarball releases):  trunk 
SVN Revision (number only!): 47646 
Disclaimer on File?:        No 
Request Review:              
====================================================================== 
Date Submitted:             06-21-2006 00:13 CDT
Last Modified:              06-18-2008 16:34 CDT
====================================================================== 
Summary:                    [patch] allow SIP Spiral to work instead of causing
a '482 Loop Detected' condition
Description: 
A sip call originating from asterisk causes a '482 Loop Detected' response
when forwarded back to asterisk from a external proxy. This should be
allowed when the request URI has been changed by the proxy and the call is
now targeted at a different user.
====================================================================== 

---------------------------------------------------------------------- 
 putnopvut - 06-18-08 16:34  
---------------------------------------------------------------------- 
I have uploaded working_spiral.patch. This has passed the "works for me"
stage of development.

Here's a breakdown of the patch:

If a possible loop is detected on an incoming INVITE, a comparison is made
to see if the Request URI has changed. If pedantic is turned on, then the
comparison will follow RFC 3261 section 19.1.4's rules for URI comparison.
If pedantic is turned off, then the comparison is just a string comparison
of the two URI's. Asterisk then will update the routing information and
send the INVITE to the new URI.

I would like to see if it works for others as well. The patch is made
against the 1.4 branch of Asterisk. Thanks! 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
06-18-08 16:34  putnopvut      Note Added: 0088883                          
======================================================================