* Add new Yealink MWI Subscribe Variable
Adds new variable in Yealink provisioning templates to allow control of MWI subscribe setting behavior on all accounts. Setting the new variable once affects all accounts.
New variable:
yealink_subscribe_mwi_to_vm.
Setting affected:
account.X.subscribe_mwi_to_vm setting
Phones affected:
T1x
T2x
T3x
T4x
May affect MWI subscription behavior. Yealink default is 0, many of the old templates hard coded 1. This change may affect MWI behavior for some users, so check to make sure the variable is added in FusionPBX to match your previous settings before upgrading.
* Add Yealink alert_info Distinctive Ring Variables
Adds new variables in Yealink provisioning templates to allow control of distinctive ring text and distinctive ringtone options.
New variables:
yealink_ring_text_X
yealink_ring_file_X
Setting affected:
distinctive_ring_tones.alert_info.X.text
distinctive_ring_tones.alert_info.X.ringer
Phones affected:
T1x
T2x
T3x
T4x
T5x
User Effect
This should not have any effect on existing provisioning settings unless the new variables are defined.
* Add files via upload
* Fix yealink_firmware_url
* Add new Yealink MWI Subscribe Variable
Adds new variable in Yealink provisioning templates to allow control of MWI subscribe setting behavior on all accounts. Setting the new variable once affects all accounts.
New variable:
yealink_subscribe_mwi_to_vm.
Setting affected:
account.X.subscribe_mwi_to_vm setting
Phones affected:
T1x
T2x
T3x
T4x
May affect MWI subscription behavior. Yealink default is 0, many of the old templates hard coded 1. This change may affect MWI behavior for some users, so check to make sure the variable is added in FusionPBX to match your previous settings before upgrading.
* Add Yealink alert_info Distinctive Ring Variables
Adds new variables in Yealink provisioning templates to allow control of distinctive ring text and distinctive ringtone options.
New variables:
yealink_ring_text_X
yealink_ring_file_X
Setting affected:
distinctive_ring_tones.alert_info.X.text
distinctive_ring_tones.alert_info.X.ringer
Phones affected:
T1x
T2x
T3x
T4x
T5x
User Effect
This should not have any effect on existing provisioning settings unless the new variables are defined.
Adds new variable in Yealink provisioning templates to allow control of MWI subscribe setting behavior on all accounts. Setting the new variable once affects all accounts.
New variable:
yealink_subscribe_mwi_to_vm.
Setting affected:
account.X.subscribe_mwi_to_vm setting
Phones affected:
T1x
T2x
T3x
T4x
May affect MWI subscription behavior. Yealink default is 0, many of the old templates hard coded 1. This change may affect MWI behavior for some users, so check to make sure the variable is added in FusionPBX to match your previous settings before upgrading.
* Added yealink common files for each model and created folder for new conference phone models
* Modified Yealink t46g templates and added 3 new variables
* Add. Use `route_to_bridge` module to build routes fro ring groups.
This commit has several improvements
1. Select only needed fields. (do not select quite big XML text strings)
2. Filter routes also by context name
3. Filter dialplans also by hostname
4. Handle conditions based not only `destination_number`
5. Handle `break` and `continue` attributes for extensions
6. Escape vars inside dial-string
7. Add log messages similar as FS dialplan do
* Add. `route_to_bridge` set inline vars so it possible use then in next conditions.
Add. `route_to_bridge` can execute basic api commands from allowed lists.
`route_to_bridge` expand all known vars. If var is unknown then it pass as is.
Fix. `export nolocal:` action.
* Fix. Short variable names
* Add. some comments
* Fix. Do not try execute empty string
This produce error messages `[ERR] switch_cpp.cpp:759 No application specified`
* Fix. Export nolocal values.
