[asterisk-bugs] [Asterisk 0011843]: Moved Temporarily Contact Transport information not used in next invite

[noreply at bugs.digium.com]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=11843 
====================================================================== 
Reported By:                pestermann
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   11843
Category:                   Channels/chan_sip/Transfers
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     acknowledged
Asterisk Version:           1.6.0-beta1 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             01-25-2008 02:34 CST
Last Modified:              04-29-2008 11:51 CDT
====================================================================== 
Summary:                    Moved Temporarily Contact Transport information not
used in next invite
Description: 
When getting back an Moved Temporarily from the called party the transport
information in the contact header is not used for the next invite based on
promiscredir=yes. 

In the SIP debug 
======================================================================
Relationships       ID      Summary
----------------------------------------------------------------------
has duplicate       0012026 Asterisk 1.6-beta3 does not follow sip ...
has duplicate       0012550 [SIP/TCP] received 302 Moved Temporaril...
====================================================================== 

---------------------------------------------------------------------- 
 pabelanger - 04-29-08 11:51  
---------------------------------------------------------------------- 
Does Dial(SIP/1234 at 192.168.0.10:3456;transport=tcp) exist today, or was
that a suggestion?  The second issue I see with this route, which is the
issue I currently have with 302, how to extract dynamic information from
the 302 message regarding port number.

The above example has a hardcoded '3456' port, the application I work with
dynamically generates the port to contact from the 302 moved.

Either way, attaching myself to the thread to trace progress. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
04-29-08 11:51  pabelanger     Note Added: 0086144                          
======================================================================