[asterisk-bugs] [Asterisk 0010576]: Asterisk fails in Loop Back

noreply at bugs.digium.com noreply at bugs.digium.com
Wed Aug 29 14:25:52 CDT 2007


A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=10576 
====================================================================== 
Reported By:                ibc
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   10576
Category:                   Channels/chan_sip/General
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     new
Asterisk Version:           1.4.11  
SVN Branch (only for SVN checkouts, not tarball releases): N/A  
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             08-27-2007 19:52 CDT
Last Modified:              08-29-2007 14:25 CDT
====================================================================== 
Summary:                    Asterisk fails in Loop Back
Description: 
I have an OpenSer in port 5060 and Asterisk in 5070.

If Asterisk makes a call to an OpenSer extension and OpenSer rewrites URI
to come back to Asterisk, Asterisk returns a "482 Loop Detected" and tries
to establishe a internal call using chan_local **to the original URI**
(even if the URI has been changed by OpenSer).

This is a big issue because it doesn't allow a "forwarding" system where
Asterisk receives a call from PSTN and makes a call to a SIP user of
OpenSer, OpenSer rewrites the URI to call to PSTN via Asterisk -> so
Asterisk fails.
====================================================================== 

---------------------------------------------------------------------- 
 ibc - 08-29-07 14:25  
---------------------------------------------------------------------- 
Yes, it can be closed since I've realized this is not a bug but a not
implemented feature discussed in report 7403.

Thanks. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
08-29-07 14:25  ibc            Note Added: 0069649                          
======================================================================




More information about the asterisk-bugs mailing list