[asterisk-bugs] [Asterisk 0014197]: [patch] Specifying a host port number in a registration string causes incorrect port in contact header

[Asterisk Bug Tracker]

The following issue has been RESOLVED. 
====================================================================== 
http://bugs.digium.com/view.php?id=14197 
====================================================================== 
Reported By:                Nick_Lewis
Assigned To:                putnopvut
====================================================================== 
Project:                    Asterisk
Issue ID:                   14197
Category:                   Channels/chan_sip/Registration
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     resolved
Asterisk Version:           1.6.0 
Blocks for Version:         None 
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
Resolution:                 duplicate
Duplicate:                  13633
Fixed in Version:           
====================================================================== 
Date Submitted:             2009-01-08 04:19 CST
Last Modified:              2009-01-08 14:12 CST
====================================================================== 
Summary:                    [patch] Specifying a host port number in a
registration string causes incorrect port in contact header
Description: 
The Register String format is 
[transport://]user[:secret[:authuser]]@host[:port][/contact][~expiry]

If a port is specified then it is correctly used for the uri in the
request line but it is also incorrectly used for the contact uri in the
contact header

For Example if the asterisk unit is at 123.123.123.123:5060 and the host
is at 21.21.21.21:5082 then incoming calls try to go to
123.123.123.123:5082 because the contact header is incorrect
======================================================================
Relationships       ID      Summary
----------------------------------------------------------------------
duplicate of        0013633 Asterisk won't register if SIP-port at ...
====================================================================== 

---------------------------------------------------------------------- 
 (0097220) putnopvut (administrator) - 2009-01-08 14:12
 http://bugs.digium.com/view.php?id=14197#c97220 
---------------------------------------------------------------------- 
Thanks for the effort in tracking this down.

The problem is that if you update your 1.6.0 branch, you'll see that this
line has already been removed and has been replaced with some different
logic for setting the port. This change was made to correct issue
http://bugs.digium.com/view.php?id=13633,
which appears to be the same as what you have brought up here. As such, I
am closing this issue since it appears to be a duplicate. If you find that
the fix already in place is not sufficient, then feel free to re-open this
ticket. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-01-08 14:12 putnopvut      Note Added: 0097220                          
2009-01-08 14:12 putnopvut      Relationship added       duplicate of 0013633
2009-01-08 14:12 putnopvut      Duplicate ID             0 => 13633          
2009-01-08 14:12 putnopvut      Status                   new => resolved     
2009-01-08 14:12 putnopvut      Resolution               open => duplicate   
2009-01-08 14:12 putnopvut      Assigned To               => putnopvut       
======================================================================