Can't login to Yealink W60B after provisioning.

[DavisITSolutions]

As title says,

Site has 3 W60B stations provisioned. Need to make adjustments to handsets but can't login to the phones.

Every combination of usernames and passwords are failing.
Have tried usernames of admin, extension number and the User ID (generated one) from phones page.
Also have tried default passwords, "Phone Password" "Account Password" and FXS/DECT device passwords with above user combinations.

Any thing I am missing here?

 

[cobaltit]

So you say phones but I assume you mean the base stations. It should be username admin and the 'Device Web Page Password' under the appropriate 'FXS/DECT' entry.

 

[AWS2P]

 

[DavisITSolutions]

So you say phones but I assume you mean the base stations. It should be username admin and the 'Device Web Page Password' under the appropriate 'FXS/DECT' entry.

Yes, the base station. As I mentioned, I did use those. No change.

View attachment 15909

Negative. Not working. Tried copy and paste as well as manually typing them in. Has always worked for me in the past.

 

[Saqqara]

Factory default the unit, and enter the provisioning url into the phone gui to get it setup on 3cx

 

[DavisITSolutions]

Factory default the unit, and enter the provisioning url into the gui to get it setup on 3cx

I will likely have to do that with the earlier phones which is a pain due to the site location. I'm really more concerned as to why it happened. These were provisioned before the user account switching back in version 15 so I suspect it has to do with that but whatever. Haven't needed to log into them since then.

I sent a tech over with a new W60P and set it up on the lan to test. Since the provision, I couldn't log into it either at first. Then I refreshed the page and noticed that the password shown and the password copied wasn't the same. I logged out of 3cx and cleared cache, then got back into the system and the copy of the password matched the FXS password listed.

I'm still investigating. Could be a copy and paste bug in the newest one but the old ones would not be the case.

 

[cobaltit]

If you control the network that they are on I'd try doing Option 66 and see if you can force it to read the provisioning file from 3CX. Or if you if you have a Yealink DM account you could use that method.

 

[DavisITSolutions]

Option 66 was already setup and the phones are working and provisioned fine. That isn't the problem in this case. It just seems that the password in the 3cx console isn't the correct one for the phone.

We had planned on adding some additional handsets to the bases and can't.

It's a small site so no Yealink DM.