* Added yealink common files for each model and created folder for new conference phone models
* Modified Yealink t46g templates and added 3 new variables
* Update app_config.php
* Update app_config.php
Changed yealink_ip_address_mode variable type from integer to standard type, numeric.
* Added yealink common files for each model and created folder for new conference phone models
* Modified Yealink t46g templates and added 3 new variables
When in dialplan edit form press `XML` and then `Back`
Fusion build wrong URL like `&?app_uuid` so if then press
save server will do not get this arg and change it.
This grabs a recording if started by bind_digit_action "*2" or by "nolocal:api_on_answer=uuid_record ${uuid} start ${recordings_dir}/${domain_name}/archive/${strftime(%Y)}/${strftime(%b)}/${strftime(%d)}/${uuid}.${record_ext}".
Fix. Symbol '^' should be inside double quotes on Windows system.
Fetch may be not possible in some cases but git still be valid.
I test git status on repo with changes. And it also returns 0 as
return code.
* Azure TTS
This is the first of a set of pull that will give FusionPBX TTS capabilities in many places. This is the main class that will interact with the other modifications.
Please suggest if this is the best place to put this file or if a /app/azure/resources/class is best. I am not sure about this.
This class is sponsored by my friend since he paid some Indian guys for a development and I discovered they were offering/selling that private development to other companies. He took the call to make this capability free.
* Moving to another place
* New place
FS Always mark xml as ISO-8859-1, but pass info as-is.
So if user send its contact info as UTF-8 then we get
corrupted xml. But RFC describe text as UTF8
RFC 3261 - 25.1 Basic Rules
```
qdtext = LWS / %x21 / %x23-5B / %x5D-7E / UTF8-NONASCII
```
In cluster installation first node search channel uuid
and send it inside special SIP header. So other node
can just use it and do not call Lua script again.
Adding this fix enables both remote phone book and provisioning to work correctly on the newly released android based Yealink devices.
It appears that during the provisioning process, the T5X series supply a colon formatted mac address in their user agent.
However, when requesting a remote phone book, the presented user agent has no colons. This allows both formats to work as expected.
FusionPBX
TekMason
Alexey Melnichuk
Pro-pra
konradSC
Len
Luis Daniel Lucio Quiroz
TylerP
Harrison Caldicott