[asterisk-bugs] [Asterisk 0014198]: [patch] Not possible to register to a registrar via a host with different port number

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=14198 
====================================================================== 
Reported By:                Nick_Lewis
Assigned To:                putnopvut
====================================================================== 
Project:                    Asterisk
Issue ID:                   14198
Category:                   Channels/chan_sip/Registration
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     confirmed
Asterisk Version:           1.6.0 
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             2009-01-08 08:51 CST
Last Modified:              2009-01-09 05:35 CST
====================================================================== 
Summary:                    [patch] Not possible to register to a registrar via
a host with different port number
Description: 
It is currently possible to register to a registrar indirectly via a host
using an extended format of the registration string
[transport://]user[:secret[:authuser]]@host[:port][/contact][~expiry]

In this extended format the "user" portion is expanded to
"username at domain". In this case the registration packet is sent to the
address of the "host" but the request line uri indicates that the registrar
is at the address of the "domain". This works fine as long as default port
numbers are used

However if the host includes a "port" other than 5060 then the request
line uri also contains this port even though the registrar may be on a
different port number or on the standard port

There needs to be a way in the registration string to specify the port of
the registar too e.g. "user" expand to "username at domain:domainport"
====================================================================== 

---------------------------------------------------------------------- 
 (0097266) Nick_Lewis (reporter) - 2009-01-09 05:35
 http://bugs.digium.com/view.php?id=14198#c97266 
---------------------------------------------------------------------- 
Yes it is not an easy one. I cannot imagine having a domainport separator
other than the : character but it is not possible to change the secret
separator without adversely affecting compatibility. 

I need this functionality due to the natproxy requirements of some of the
ITSP that I need to interwork with. Therefore I am prepared to live with
the requirement to specify a secret and authuser. I think others in my
situation may be too.

I guess that one solution may be to use something like [:domainport/]  but
this looks only a little less odd than [/domainport] 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-01-09 05:35 Nick_Lewis     Note Added: 0097266                          
======================================================================