[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:                bbryant
====================================================================== 
Project:                    Asterisk
Issue ID:                   11843
Category:                   Channels/chan_sip/Transfers
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     ready for testing
Asterisk Version:           1.6.0-beta9 
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:              07-21-2008 20:50 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 - 07-21-08 20:50  
---------------------------------------------------------------------- 
bbryant: My mistake looks like we still get an error from the CLI

 [Jul 21 21:44:39] ERROR[28370] astobj2.c: bad magic number 0x29 for
0x8236668

However, everything appears to be working properly. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
07-21-08 20:50  pabelanger     Note Added: 0090549                          
======================================================================