[asterisk-bugs] [Asterisk 0014342]: outboundproxy parameter in sip.conf is not atomic

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=14342 
====================================================================== 
Reported By:                Nick_Lewis
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   14342
Category:                   Channels/chan_sip/General
Reproducibility:            always
Severity:                   trivial
Priority:                   normal
Status:                     new
Asterisk Version:           1.6.1-beta4 
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2009-01-27 04:39 CST
Last Modified:              2009-01-27 04:44 CST
====================================================================== 
Summary:                    outboundproxy parameter in sip.conf is not atomic
Description: 
The outboundproxy parameter in both general and peer specific sections of
sip.conf is a concatenation of two pieces of data. The first is the
ipaddress or fqdn and the second is the tcp or udp port number. It would be
better if the outboundproxy port could be specified separately. This would
also align better with the host and port parameters. For backwards
compatibility the existing format would continue to be supported


====================================================================== 

---------------------------------------------------------------------- 
 (0098833) Nick_Lewis (reporter) - 2009-01-27 04:44
 http://bugs.digium.com/view.php?id=14342#c98833 
---------------------------------------------------------------------- 
Oh - I notice the same could also be said of outboundproxyforce and
outboundproxytransport 

It is too much work at the moment to do a patch for all of them so please
close this issue - sorry 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-01-27 04:44 Nick_Lewis     Note Added: 0098833                          
======================================================================