| Summary: | ASTERISK-19454: outbound proxy not being cleared which sip reload performed | ||
| Reporter: | Bruce McAlister (asgaroth) | Labels: | |
| Date Opened: | 2012-03-01 11:24:05.000-0600 | Date Closed: | 2013-12-11 13:23:43.000-0600 |
| Priority: | Major | Regression? | |
| Status: | Closed/Complete | Components: | Channels/chan_sip/General |
| Versions: | 1.8.9.2 | Frequency of Occurrence | |
| Related Issues: | |||
| Environment: | CentOS 5.7 64-bit SunFire X4170M2 | Attachments: | ( 0) 0001-Reset-peer-outboundproxy-on-sip.conf-reload-1.8.patch |
| Description: | To reproduce perform the following steps: [1] Set the outboundproxy= parameter for a peer/friend definition to "something" for example "proxy.example.com:5060" [2] Perform "sip reload" [3] Perform "sip show peer <peername>" [4] Step 3 above will show the current outboundproxy as "proxy.example.com" [5] Set the outboundproxy= parameter for a peer/friend to blank, or remove the option from the peer definition [6] Perform "sip reload" [7] Perform "sip show peer <peername>" [8] Step 7 above will show that the outboundproxy parameter is still set to "proxy.example.com:5060" as in step 1 above. It appears that the outboundproxy definition is not updated on peer reload unless the value is defined to something else, even if it is invalid. Currently it is not possible to "unset" the outboundproxy if one has been previously set without restarting the asterisk environment. | ||
| Comments: | By: Russell Bryant (russell) 2013-12-11 12:09:19.508-0600 Fix for 1.8 attached. The same fix applies to 11 and trunk. By: Russell Bryant (russell) 2013-12-11 13:22:50.207-0600 Fix committed to 1.8, 11, 12, and trunk reviewed here https://reviewboard.asterisk.org/r/3065/ | ||