[asterisk-bugs] [Asterisk 0016235]: Placing a URI call fails when URI string contains a non-standard port

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=16235 
====================================================================== 
Reported By:                test011
Assigned To:                file
====================================================================== 
Project:                    Asterisk
Issue ID:                   16235
Category:                   Channels/chan_sip/General
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     assigned
Asterisk Version:           SVN 
JIRA:                       SWP-419 
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2009-11-12 14:22 CST
Last Modified:              2009-12-05 02:15 CST
====================================================================== 
Summary:                    Placing a URI call fails when URI string contains a
non-standard port
Description: 
You can make a direct URI call with, say, a softphone register to an
Asterisk like this,

123 at myhome.dyndns.earth

with some entry in extensions.conf like this,

Dial(${EXTEN}@${SIPDOMAIN},.....)

Yes, this works great. Let's assume something else,

123 at myhome.dyndns.earth:8777  (notice the port number at the end)

This does not work. Because ${SIPDOMAIN} does not have ":8777" part of the
URI dialed. It seems Asterisk just throws that part away. If it's not, I
guess it's not documented well enough.

Some document claims that ${SIPDOMAIN} will contain all the string after
'@' But I guess this is not the case.
====================================================================== 

---------------------------------------------------------------------- 
 (0114816) test011 (reporter) - 2009-12-05 02:15
 https://issues.asterisk.org/view.php?id=16235#c114816 
---------------------------------------------------------------------- 
Regarding my previous note, in the asterisk's view point when client enters
URI, it can be seen as Inbound, I guess. 

Making a direct URI call without a trunk configuration may be something
out of scope of Asterisk too, even though so many community informers have
claimed that Asterisk supports direct URI calling. 

But it sure looks incomplete when we already have ${EXTEN} and
${SIPDOMAIN} parsed out of entered URI and 'PORT' information just
discarded. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-12-05 02:15 test011        Note Added: 0114816                          
======================================================================