Bug in version 3 of YDMP?

[Bertin]

Hi,

We recently upgraded our YDMP from version 2.x to 3.0.0.13, but we have encountered a severe bug: each time we restart our Skype for Business servers, our T48S phones (working with the latest firmware) are trying to re-establish their connection, but they fail, as the account provisioning from YDMP is sending wrong account data.

Our sip-addresses differs from our loginnames (sip is like firstname.lastname@MX-domain, while our loginname is formed by a combination of characters from the first and lastname, followed by our active directory domain name).

In version 2.x of the YDMP, both the sip-adress and the loginname where registered fine in the YDMP-database, but in version 3.x, the sip-name is registered in both the "Register Name" and "Login Address"-fields in the YDMP-database. This results in a wrong loginname provisioning when the T48S-phones connects to the YDMP for their settings (the phone shows the sip-name filled in in both fields, and the phone is denied access to the server, as it is providing a wrong loginname)

I already contacted Lydis.nl (our local dealer for Yealink products), and they confirmed my findings. We have >700 T48S phones which were having this problems (users had to reset the loginname each time they restarted the phone or we restarted our servers), and the only solution at this moment is to block all access from the phones to the YDMP, making it impossible to change any settings on the phones.

Please resolve this bug ASAP, as we have no control over our phones anymore.

Regards,
Bertin