[asterisk-bugs] [Asterisk 0014233]: port :0 added to SIP INVITE URI when 'outboundproxy' used in [general] section of sip.conf

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=14233 
====================================================================== 
Reported By:                chris-mac
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   14233
Category:                   Channels/chan_sip/General
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     new
Asterisk Version:           SVN 
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases): 1.6.1 
SVN Revision (number only!): 168551 
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             2009-01-13 15:21 CST
Last Modified:              2009-01-13 22:45 CST
====================================================================== 
Summary:                    port :0 added to SIP INVITE URI when 'outboundproxy'
used in [general] section of sip.conf
Description: 
How to reproduce:

extensions.conf:
exten => _X.,1,Dial(SIP/enum-test at sip.nemox.net,45)

without 'outboundproxy' set in sip.conf [general] INVITE (sent directly to
final destination):
INVITE sip:enum-test at sip.nemox.net SIP/2.0
...

with 'outboundproxy' set INVITE (request sent via proxy):
INVITE sip:enum-test at sip.nemox.net:0 SIP/2.0 
...

NOTE: port :0 appended to URI!!! - Maybe this is related to
http://bugs.digium.com/view.php?id=14055 ?
====================================================================== 

---------------------------------------------------------------------- 
 (0097701) jamesgolovich (manager) - 2009-01-13 22:45
 http://bugs.digium.com/view.php?id=14233#c97701 
---------------------------------------------------------------------- 
I was able to duplicate the issue and this patch resolves the issue.

Even though we aren't sending the packet direct to the host we need to
parse out the port and include it in case the ultimate destination is on a
non standard port. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-01-13 22:45 jamesgolovich  Note Added: 0097701                          
======================================================================