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

Asterisk Bug Tracker noreply at bugs.digium.com
Tue Mar 3 12:32:03 CST 2009


A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=12215 
====================================================================== 
Reported By:                jpyle
Assigned To:                mmichelson
====================================================================== 
Project:                    Asterisk
Issue ID:                   12215
Category:                   Channels/chan_sip/General
Reproducibility:            random
Severity:                   minor
Priority:                   normal
Status:                     ready for review
Asterisk Version:           1.4.18 
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2008-03-14 11:45 CDT
Last Modified:              2009-03-03 12:32 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...
====================================================================== 

---------------------------------------------------------------------- 
 (0101099) mmichelson (administrator) - 2009-03-03 12:32
 http://bugs.digium.com/view.php?id=12215#c101099 
---------------------------------------------------------------------- 
Well, taking a quick look at things a bit further down in
handle_request_invite, there is a large switch statement which uses the
channel's state as a means to gauge what action to take. My guess is that
since the re-INVITE is being handled while the channel is still in the
AST_STATE_RINGING state, we send back a 180 Ringing response instead of
actually doing what we should with a re-INVITE.

More updates will come from me as I make more discoveries. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-03-03 12:32 mmichelson     Note Added: 0101099                          
======================================================================




More information about the asterisk-bugs mailing list