I’ve been beating my head against the wall for the last few hours trying to deal with a few issues with passwords.
I setup a test freepbx server running 2.210.62-2 with several Yealink T22P handsets. I can set up the extensions, associate the handsets with the extension using endpoint manager and the phones pick up the config and restart and then show the users name and details.
All appears normal.
Problem 1 is that we found that after the configuration stage the phones web-admin password changes. Before Freepbx issues the config and the phone restarts, it’s admin/admin. Afterwards this doesnt work. Even yealink couldn’t help and didn’t know why this might be. This may be by design but I couldn’t find any mention of a new password in the forums.
Problem 2 is that the phones report being connected for 60 seconds then show as being disconnected. The astericks log shows that they can’t connect because of “wrong password”. The set up the extensions we just enter the users name, extension number and a SIP secret. I can’t check what details the phone itself is using because of problem 1 (see above).
The bug comes in here. If I use 1.1100.211.63, the CD of which I have in my bag and have used many times around the place in the last 6 months, the whole test rig works just fine. The web-admin passwords don’t get changed and the handsets connect and stay connected even though I have filled in the same boxes as when setting up 2.210.
Does anyone know what might have changed between the two versions that might cause these symptoms or how I can move on?