| Summary: | ASTERISK-13458: outboundproxy parameter in sip.conf is not atomic | ||
| Reporter: | nick_lewis (nick_lewis) | Labels: | |
| Date Opened: | 2009-01-27 04:39:48.000-0600 | Date Closed: | 2011-06-07 14:10:11 |
| Priority: | Trivial | Regression? | No |
| Status: | Closed/Complete | Components: | Channels/chan_sip/General |
| Versions: | Frequency of Occurrence | ||
| Related Issues: | |||
| Environment: | Attachments: | ||
| 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 | ||
| Comments: | By: nick_lewis (nick_lewis) 2009-01-27 04:44:00.000-0600 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 By: Leif Madsen (lmadsen) 2009-01-28 13:01:44.000-0600 Closed at the request of the reporter. Thanks! | ||