* Added two new minor hardware revisions, the CP925 and T42U, and added the voice.tone.country = {} to all templates, previously missing on most
* Minor typo from a wrong window issue, and removing the commented examples for easier grepping
* Grandstream HT802 Added Offhook Auto-dial variables
* Grandstream HT802 Added Offhook Auto-dial variables
* Grandstream GRP261x Make Configuration Keypad Lock configurable, fix default
* Grandstream Add grandstream_dhcp_time_zone across all templates
* Yealink Added yealink_missed_calllog to control whether missed calls are logged or not
* Grandstream HT802 update variable name to not use dash (which was breaking the template)
Changes to make the templates a bit more consistent while also fixing some typos and creating a new variable for the NAT Update setting.
By default, the account.x.nat.udp_update_enable is set to "3" which means to have the phone periodically send NOTIFY messages. This is not the case though on additional accounts. This makes for inconsistent configs that sometimes cause issues with phones ringing.
This fixes the issue while also giving the ability to use a variable to set it.
nway_conference == true was evaluating as true regardless if nway_conference was set to true or false, just as long as it had a value of any kind.
This also fixes it so that you can set nway_conference to false in the default settings and it will disable the network conference feature, previously once it was enabled on yealink phones it could not be disabled without manually changing it in the phone or a factory default.
By default, the dial pad only searches the Local phonebook and recent call history for suggestions while dialing. This adds support for searching the Remote Phonebook if configured and enabled. There is also commented out the definition to search an LDAP phonebook if one has been configured elsewhere.
Add the ability for the "History" to show the original caller ID when picking up parked/intercepted calls instead of the history showing the dial code that was used to pick up the call. The Call History on the phones would show park+*5901 after using a button to pick up a parked call. The Caller's name would display properly during the call but wasn't in the history unless this variable is set.
* Daylight Saving changes:
- enabled on server auto.DST.xml configuration for phones
- added new autoDST.xml file to fusionpbx server
- corrected autoDST.xml, addde balkans countries
* Fixed the yealink_auto_dst_url name to fix the syntax problem.
* Rename AutoDST.xml to auto_dst.xml
* Update app_config.php
* Update auto_dst.xml
Co-authored-by: FusionPBX <markjcrane@gmail.com>
* Updates to Yealink codec provisioning
Changed codecs to use variables set in default settings.
* Added basic provisioning for swissvoice cp2502 and cp2505g
Codec handling set in default settings.
Need to still work on directory and funtion keys.
* Update app_config.php
Add the following advanced SIP variable. Disabling this allows Yealink phones to display the SIP error reason in the format sent by the carrier rather than Q.850 format e.g. "User Busy" rather than "NORMAL_CLEARING"
sip.call_fail_use_reason.enable = {$yealink_sip_call_fail_use_reason_enable}
* 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
Adds yealink_language_gui variable to all Yealink templates.
Note: Some templates were forcing "English" through conditional statement or hard-coded.
Now, if no value is set, it will not set any value in the template. This should not hurt anything as default language on Yealink phones is "English"
* 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.
Alex
Harry Foster
markjcrane
Dan
Antonio Fernandez
Mendel
demonspork
agree
chansizzle
Baji Zsolt
Len
root
saraxxin
emaktech
AlexanderDCrane
TekMason