[asterisk-bugs] [JIRA] (ASTERISK-19454) outbound proxy not being cleared which sip reload performed

[Russell Bryant (JIRA)]

    [ https://issues.asterisk.org/jira/browse/ASTERISK-19454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=212849#comment-212849 ] 

Russell Bryant commented on ASTERISK-19454:
-------------------------------------------

Fix committed to 1.8, 11, 12, and trunk

reviewed here https://reviewboard.asterisk.org/r/3065/
                
> outbound proxy not being cleared which sip reload performed
> -----------------------------------------------------------
>
>                 Key: ASTERISK-19454
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-19454
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Channels/chan_sip/General
>    Affects Versions: 1.8.9.2
>         Environment: CentOS 5.7
> 64-bit
> SunFire X4170M2
>            Reporter: Bruce McAlister
>            Assignee: Russell Bryant
>         Attachments: 0001-Reset-peer-outboundproxy-on-sip.conf-reload-1.8.patch
>
>
> 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.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.asterisk.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira