Commit Graph

14 Commits

Author SHA1 Message Date
Len 265e6b4317 Update {$mac}.cfg (#3982) 2019-01-29 12:26:39 -07:00
AlexanderDCrane 49239c97e9 Update {$mac}.cfg (#3617) 2018-09-28 13:04:37 -06:00
markjcrane 412a6bfc74 update the yealink templates 2018-09-26 17:47:21 -06:00
AlexanderDCrane c2f09bbd4e Update {$mac}.cfg (#3566) 2018-09-24 12:57:10 -06:00
AlexanderDCrane d62ed746fa Update {$mac}.cfg (#3555) 2018-09-21 23:52:16 -06:00
FusionPBX 0dfe1030fc Update {$mac}.cfg 2018-09-13 01:33:11 -06:00
Len 82cbaf8a3c Update {$mac}.cfg (#3449) 2018-09-12 21:22:33 -06:00
AlexanderDCrane f321075493 Update {$mac}.cfg (#3411) 2018-09-12 15:35:25 -06:00
Len 7562f151f8 Update {$mac}.cfg (#3256) 2018-07-17 14:55:38 -06:00
FusionPBX 30ad0b6bb8 Update {$mac}.cfg 2018-06-22 02:14:01 -06:00
emaktech 1839482f57 Fix Yealink Programmable Key Template Conflicts (#3073)
* Add language, dialect and voice selection

This scans the FreeSWITCH sounds directory to find installed languages and then allows the user to select the language, dialect and voice from a dropdown.  The selected option will then be built into the dialplan and saved in the database when saving the IVR.

This fixes many cases of inconsistent language problems with email templates, multilanguage voicemail support, etc. by setting an appropriate installed dialect and voice. This variable is then passed along to the next applications correctly rather than relying only on the default settings on the switch and creating inconsistent behaviors.

example of poor behavior before: Setting language to "fr" on the IVR with default switch settings as "en, us, callie" would set the language to fr-us callie which is an obviously incorrect configuration. By forcing all variables to be set to together in the IVR dialplan it avoids such inconsistent behaviors.

* Fix Yealink Programmable Key Template Conflicts

Some Yealink templates have both on the {$mac.cfg} files as well as the y000000000000.cfg files. This creates a conflict when configuring the pgorammable keys in the templates so all the programmable options have been removed from the {$mac.cfg} files to resolve the conflict.

* Update {$mac}.cfg

* Update {$mac}.cfg

* Update {$mac}.cfg

* Update {$mac}.cfg

* Update {$mac}.cfg

* Update {$mac}.cfg

* Update {$mac}.cfg

* Update {$mac}.cfg

* Update {$mac}.cfg

* Update {$mac}.cfg

* Update {$mac}.cfg

* Update {$mac}.cfg

* Update {$mac}.cfg

* Update {$mac}.cfg

* Update {$mac}.cfg

* Update {$mac}.cfg

* Update {$mac}.cfg

* Update {$mac}.cfg

* Update {$mac}.cfg

* Update {$mac}.cfg

* Update {$mac}.cfg

* Update ivr_menu_edit.php
2018-05-29 15:53:18 -06:00
FusionPBX 00d7bede89 Update {$mac}.cfg 2018-01-05 02:35:51 -07:00
emaktech 13e11fefba Add new Yealink MWI Subscribe Variable (#2920)
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.
2017-11-21 19:44:23 -07:00
FusionPBX bbcc12e195 Create {$mac}.cfg 2017-11-04 18:25:46 -06:00