- Joined
- Jun 13, 2017
- Messages
- 423
- Reaction score
- 254
I implore you to copy the below request to the ideas forum (and everyone else please go there and vote for the change). Personally I feel this would be a simple change with no possible negative impact. If I'm missing something, please feel free to share.
In the default Yealink provisioning templates, if the extension is configured to register via SBC, "account.1.outbound_proxy_enable" is set to "1" (enabled) (at the moment this is line 2783).
However, if the extension is configured to register via Direct SIP, "account.1.outbound_proxy_enable" has no value specified. (line 2757)
Line 2757 needs to be updated to "account.1.outbound_proxy_enable=0" instead of being left blank/no value.
The reason this is a problem is ...
Scenario 1
When a user occasionally takes a phone out of the office, for example to work from home, we make the change in the extension's settings but the phone continues to attempt to register via SBC and cannot. We then either have to do a remote session and manually change the parameter on the phone, factory reset the phone and reprovision, or use a custom template and reprovision to resolve the issue.
Scenario 2
In the event of an SBC going down and clustering/backup options are not available, even if the firewall is configured to pass the traffic, simply changing the provisioning method from SBC to Direct SIP will not allow the phone to register because it is still trying to use the SBC (proxy).
All this could be avoided by simply adding a "0" in the default template.
In the default Yealink provisioning templates, if the extension is configured to register via SBC, "account.1.outbound_proxy_enable" is set to "1" (enabled) (at the moment this is line 2783).
However, if the extension is configured to register via Direct SIP, "account.1.outbound_proxy_enable" has no value specified. (line 2757)
Line 2757 needs to be updated to "account.1.outbound_proxy_enable=0" instead of being left blank/no value.
The reason this is a problem is ...
Scenario 1
When a user occasionally takes a phone out of the office, for example to work from home, we make the change in the extension's settings but the phone continues to attempt to register via SBC and cannot. We then either have to do a remote session and manually change the parameter on the phone, factory reset the phone and reprovision, or use a custom template and reprovision to resolve the issue.
Scenario 2
In the event of an SBC going down and clustering/backup options are not available, even if the firewall is configured to pass the traffic, simply changing the provisioning method from SBC to Direct SIP will not allow the phone to register because it is still trying to use the SBC (proxy).
All this could be avoided by simply adding a "0" in the default template.
