Commit Graph

11 Commits

Author SHA1 Message Date
AlexanderDCrane f5be2faa84 Update {$mac}.cfg (#3612) 2018-09-28 13:06:07 -06:00
markjcrane 412a6bfc74 update the yealink templates 2018-09-26 17:47:21 -06:00
AlexanderDCrane fef280f23b Update {$mac}.cfg (#3561)
* Update {$mac}.cfg

* Update {$mac}.cfg
2018-09-24 12:58:27 -06:00
AlexanderDCrane dbb9c40b82 Update {$mac}.cfg (#3549) 2018-09-21 20:33:52 -04:00
Len b07f3d99a6 Update {$mac}.cfg (#3454) 2018-09-12 21:13:07 -06:00
AlexanderDCrane 579219bfad Update {$mac}.cfg (#3406)
* Update {$mac}.cfg

* Update {$mac}.cfg

* Update {$mac}.cfg

* Update {$mac}.cfg
2018-09-12 15:30:05 -06:00
Len 5d6ee321f8 Update {$mac}.cfg (#3261) 2018-07-17 13:45:46 -06:00
FusionPBX 0953cc2e31 Update {$mac}.cfg 2018-06-22 02:19:40 -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 cd581bce4b Update {$mac}.cfg 2018-01-05 02:38:01 -07:00
emaktech faeb5e3578 Add Yealink T40G Template (#2940)
* 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
2017-12-02 15:11:49 -07:00