Yealink Forums

Full Version: T48G with SfB Firmware can't Signing in
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
I have updated my YEALINK T48G with latest Skype for Business Firmware (35.8.0.5) and valid license key. The device is configured to get DHCP Option 120.

I use following Login Information on Account/Register page

Login address = <username>@Domain.com
Register Name = <username>@Domain.com
+ Password

After singning in on the Website, I receive following message

Register Failed

the root Certificate from internal CA (Security/Trusted Certificate) have been uploaded to the device

Question: as my DHCP Server have been configured with DHCP Option from Lync Common Area Phones.

Can YEALINK use the same DHCP Option 120 as for Lync Common Area Phones ?

any experience from the field ?
Suggest that you can reset the phone then test again.
Please press the OK button about 10 sec to reset the phone.
After upgrade, reset the phone is necessary.
Can you let me know where you got FW (35.8.0.5)?
Website only has 35.7.0.50


(03-02-2016 05:47 AM)andre.hagmann@umb.ch Wrote: [ -> ]I have updated my YEALINK T48G with latest Skype for Business Firmware (35.8.0.5) and valid license key. The device is configured to get DHCP Option 120.

I use following Login Information on Account/Register page

Login address = <username>@Domain.com
Register Name = <username>@Domain.com
+ Password

After singning in on the Website, I receive following message

Register Failed

the root Certificate from internal CA (Security/Trusted Certificate) have been uploaded to the device

Question: as my DHCP Server have been configured with DHCP Option from Lync Common Area Phones.

Can YEALINK use the same DHCP Option 120 as for Lync Common Area Phones ?

any experience from the field ?
Hi,

I had the same issue and I had to factory reset the phone and it worked fine. We are using the provisioning server, so it's not so bad doing the factory reset.

Let me know how you go.

Cheers,
Gavin
Try This:

Login address = <username>@Domain.com
Regiser Name = Domain\<username>
+ Password
we've had this also on occasion.

check that the UPN for the user is the same as their email address, otherwise one of those user fields is the UPN value, not email or AD username.

Also, we've set the trusted root certificate setting from enabled to disabled and that gets us past in the few cases this has happened to us.

Also, you can have the user try logging in via the web gui and the error messages are a little more verbose than the screen. You can also set logging to 6 and then looking into the log will tell you a little more about what might be wrong.

But the allow the untrusted certs setting does get us past in some cases where all else fails. No idea why.
Reference URL's