Yealink v85 links

tested

Reviewed-by: Alexandre Fournier <None>

Yealink, add CP920 firmware

Hi,
Yealink CP920 firmware is declared in pkgs.db, but not pushed up to the device.
Let's then fix this.
Thank you 👍

Reviewed-by: Alexandre Fournier <None>

WP-611 fanvil x[4-7][UXC] + 210i?

Adds firmware info for Fanvil X[4-7]U|C- + X210i Pro

Why: the phone cannot figure it out itself.

Update polycom.conf

Add new Poly MAC prefix to DHCP Known Host List (48:25:67) https://www.poly.com/content/dam/www/products/support/voice/polycom-uc/other/poly-audio-device-mac-ea189869.pdf



Reviewed-by: Sylvain Boily <sylvain@wazo.io>

Add new Poly MAC prefix to DHCP Know Host List (48:25:67)
https://www.poly.com/content/dam/www/products/support/voice/polycom-uc/other/poly-audio-device-mac-ea189869.pdf

reason: Future compatibility with Python 3

reason: Future compatibility with Python 3

Fanvil x7c key correction and last firmware

Update firmware and key correction (limited to the first 12 keys)

Reviewed-by: Alexandre Fournier <None>

Change Firmware version

Reviewed-by: Alexandre Fournier <None>

Snom, Yealink, allow autoprov with SIP TLS

Hello,
When a device is connected to the stack, for the first time, an autoprov configuration template is generated.
There's no problem if this template uses SIP TLS, device will properly reach the stack when provisioning using the  Provision Extension method.
However, SRTP can't be used here, because autoprov stack SIP template has it disabled (for good reasons *).
Let's then disable SRTP when in autoprov mode, for both SIP TLS validated plugin ; Snom & Yealink.
Thx 👍
BTW, while here, would really be nice for the autoprov mode to inherit from the global SIP template, so that it would really help for example in NATed environment etc... (see Wazo ticket #5571 / #6066).
(*) Note that even if autoprov mode would inherit from the global SIP template, we would not be able to enable SRTP there (media_encryption = sdes), because then it would break provisioning using the  Provision Extension method for devices not supporting SRTP.

Reviewed-by: Alexandre Fournier <None>

Gigaset N870 enhancements

Hello,
This PR brings enhancements for Gigaset N870 devices.
It's a whole copy of N870-83.v2.39.0 plugin, with following differences :

fix a bug with sip_subscribe_mwi handling preventing provd from building the template
fix of the _UA_REGEX for devices with old firmware (for ex 2.39) which get their new firmware sending their UA between plain double quotes...
update to last 2.48 firmware version (basic functions tested, working)
allow mobile devices firmware update
small cosmetic update on display name, to mimic other Gigaset devices, such as Gigaset N720
proper SIP TLS / SRTP handling

Unfortunately though, I've encountered a bug between N870 and Asterisk using SIP TLS, where calls are terminated as soon as they're put on hold (which is rather annoying).
I've then disabled SIP TLS support for now, I'll document bug report here for ref, and I'll bring an update of the plugin once solved.
Thank you 👍

Reviewed-by: Alexandre Fournier <None>

Snom quick fix

Hello,
Here's a very quick Snom fix.
I did not bump plugin version intentionally, as we already bump it a few minutes ago.
Thx 👍

Reviewed-by: Alexandre Fournier <None>

Snom enhancements

Hi,
This PR fixes a bug when Snom devices are using SRTP : on-hold calls which are resumed do not have sound anymore / are silent. Disabling user_auth_tag option corrects this.
https://service.snom.com/display/wiki/user_auth_tag
Note that Yealink phones also use a 80-bit auth-tag.
While here, let's be sure to enforce SRTP when used, thanks to user_savp option.
Also, let's set the setting_server option, so that it's not left blank in the web UI of the phone.
Let's then correct the BLF keys behavior, setting the quick_transfer to attended.
https://service.snom.com/display/wiki/quick_transfer
Snom behavior is now the same as on Yealink devices.
Finally, let's prevent Snom devices from rebooting when using the "Synchronize" Portal button.
https://service.snom.com/display/wiki/How+to+trigger+the+phone+to+reset+or+synchronize+its+settings+via+provisioning+-+mass+deployment
Note that even with reboot=false, devices will reboot if a provisioned option needs a reboot to apply.
reboot=false will allow to apply more easily (without impact) most of the options such as accounts, BLF etc...
Snom behavior is now the same as on Yealink devices here too.
Many thanks 👍

Reviewed-by: Alexandre Fournier <None>