v11 Phone Web UI password

[Jason Buffa]

Hello all,

I wanted to rack some brains as we are trying to help out a potential client that is running v11 of 3CX. Does anyone know how that 3CX version set passwords on the phones' web UIs? We just had this client call us randomly and we have no info on the system, so it's possible someone manually changed the phone web passwords. But as it stands, he can't access any of his phone web UIs. These are Yealink T32 phones and it's not the default admin/admin. If we help them appropriately, they should be buying a new 3CX from us.

Thanks!
Jason

 

[VoIPTools]

In those days, 3CX didn't change the phone web password. It would be the default password that came with the phone unless someone manually changed the password.

 

[CentrexJ]

Those phones are very easy to reset to factory defaults by pressing and holding the OK button and then confirming OK again when prompted.

 

[Jason Buffa]

I was hoping to see how a remote phone was configured before resetting to factory.

 

[CentrexJ]

Remote phones of that era use STUN generally or sometimes a 3cx proxy software (now called 3CX SBC). They were generally manually configured. Perhaps you want to try configuring a newer Yealink phone remotely manually to their pbx so you can familiarize yourself with it.

Realistically though they need to be stepped up to the current version and re-provisioned through 3cx.

 

[VoIPTools]

If you can't get to the web interface on ANY of the phones (because someone changed the default phone password), then you are pretty much stuck with factory resetting the phone. As CentrexJ mentioned, it's easy to do with Yealink phones.

It's always good to know how things were set up previously before you factory reset the phone, but I'm tempted to say (in this case) "who cares how they used to be provisioned?". The RPS process is so much better than the old way that I would not worry about it. Take one of the old T32 phones, upgrade the firmware, factory reset it, and provision it against a test 15.5 server. You will agree that RPS is the way to go moving forward (for remote phones). Yes, there are situations where a VPN or an SBC might be another approach for remote phones, and you will have to decide what makes the most sense in your environment, but frankly, it's easy to test if you can get your hands on a spare phone.

Admittedly things get complicated when custom templates or manual settings were implemented on the phones. Happily, 3CX has added many of the common provisioning "customizations" that were previously necessary with V11. For example, VLANs, time format, background images, etc. Heck, I recently took over a failed V15.5 server (without a valid backup) and even recreating a 15.5 server in a 15.5 environment wasn't much fun getting all the settings recreated without a guide (backup) to start from, so I applaud your desire to get as much information as you can before you start from scratch.

 

[YiannisH_3CX]

Hello @Jason Buffa

I think this is a good opportunity to upgrade the client to the latest version, especially if all phones need to be reset. Older versions of 3CX can no longer activate against the activation server so i would recommend upgrading as soon as possible. The maintenance for the licence should have been automatically extended until the end of the month so you can perform the upgrade.

 

[Jason Buffa]

Oh yes, we are going to upgrade them once they approve. But we were hoping to show some goodwill by getting this one remote phone up and running for them. Actually got it registered, and now it shows "Caller forbidden" from the 3CX and can't make any outbound/inbound calls. The disallow use outside LAN is unchecked, so still trying to figure that out.

 

[ppickens]

Jason,

I hope this isn't too little, too late for you. Check the templates that they used for the phones. Typically if you wanted to change the web password for a phone, you would do it there in v11 if it was not done manually. Hopefully that saves you from factory defaulting!