Bug in version 3 of YDMP?

[thomas.hauff]

(03-06-2019 01:12 PM)Bertin Wrote:  Since there was no reply at all on this topic from Yealink , I will update this thread myself:
After reporting this bug to Yealink and Lydis.nl, we blocked all access to the YDMP, as more and more T48S phones were getting the wrong account data provisioned, resulting in telephones which were not able to logon without manual intervention.
After a week, Lydis.nl provided us with a patched version (3.0.0.16) to test. We removed all wrong account data from the YDMP (accounts where the username was wrongfully overwritten with the sip-address) and run the new version for a week with access limited to only a few subnets. Today, we removed the firewall rule which blocked access for the other subnets, and the problem seems to be solved completely: phones are registering fine and accounts are written in the correct form in the database.
I hope Yealink will release this version asap for everyone, because version 3.0.0.13 can cause serious harm when deployed in a large environment where the sip-adres is different from the loginname.
I hope this information is useful for someone.

Kind regards,
Bertin

Hi Bertin,

we had the same error and were also provided with the version of YDMP (3.0.0.16) which fixed the problem.
I still have a question about what you wrote. "(accounts where the username was wrongfully overwritten with the sip-address)" Did I understand that correctly, that you had the account information in YDMP in the device overview where the SIP address was listed as the device name instead of the account name?
Because it seemed to me, that before the upgrade to v. 3.0.0.16 the device names were listed as the SIP address and not the users login name.
Today, we use version 3.3.0.0 and we only see the user`s logon name as the device name, which is not very helpful for us, as we can`t search in the overview for the name of the user.
Appreciate your feedback.
Regards
Thomas