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

[noreply at bugs.digium.com]

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:             03-14-2008 11:45 CDT
Last Modified:              06-01-2008 05:25 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.
====================================================================== 

---------------------------------------------------------------------- 
 rjain - 06-01-08 05:25  
---------------------------------------------------------------------- 
The INVITE-482 is not the actual problem here. The root of the problem here
is that the initial call through 63.216.250.91 is not being set up
correctly. The 200 OK from 63.216.250.82 is not being propagated by
63.216.250.91 to 66.61.7.219. Is this how the dial-plan has been programmed
to work?

Since the call doesn't set up correctly, Asterisk doesn't mark the
outbound channel 'UP'. And thus when it receives a RE-INVITE on the
outbound leg from 63.216.250.82, it sends back a 482. While 482 is not an
appropriate response code for this situation, the problem here really is to
get the initial call to setup properly. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
06-01-08 05:25  rjain          Note Added: 0087606                          
======================================================================