3CX password policy change

[Boris.Minakov.ITNow]

Dear Team,
Currently 3CX has changed a password policy, which is quite not good from physical phones side, especially Yealink Brank (old models)

For example, if you take Yealink Phone and sip user is is not numeric like 100 .. 105 ..
and there is a 3CX standard user: 3ABsdcdsGG

Phone will never register

Also some Cisco SPA models with SIP firmware have password length limit of 8 characters

Is there any way to change 3CX password policy?
To allow weak username and password in such cases, because last talked we had with a client, they said that they are not going to change phones only because 3CX updated password policy and they now can not use their phones (SIP T21P E2)

Note: Also customers do not like that now password does not come by email, because this was the best function for easy user set-up

 

[JohnS_3CX]

Hi Boris,

I think you probably have some other problem here. At least for the SIP T21P E2 you can use usernames and passwords as generated by 3CX V18 Update 7 without any problems.

We have tested this and can confirm it 100% works when using 3CX V18 Update 7 with T21P E2 firmware 52.84.0.140
And if you use the re-generate function to generate new passwords, the phone will auto-provision and accept them.

The Cisco SPA are legacy phones, we no longer provide any support for them.

While it was easy to see the passwords in the older welcome emails, this is not something we will be doing going forward. We are making changes to increase 3CX security overall, so now the user has to click the new link that appears in their email, and set their own password

 

[Boris.Minakov.ITNow]

Dear Team,
Thank you very much, I have advised customer to update 52.80.14.3 with T21P E2 firmware 52.84.0.140

Because seems their firmware is old and lets us know the results

For the password policy option, as we understand there is no chance to revert policy to an old one from options

 

[JohnS_3CX]

Yes, and thank you for the feedback, we always like to hear from our Partners.

If the phones do not accept the newer firmware, you might have to visit Yealink's site to download the missing versions in between the old one they have installed now, and the new one we have on our platform. You will have to reset the phones 1 time, upgrade them manually, then provision them back to 3CX and you will most likely not have to upgrade them again after this. The 3CX auto-provisioning should make this easier.

The Yealinks are still fully supported, so if you still have issues let us know and we advise further.

 

[SweetAction]

For devices that need weak sip credentials, the latest beta does allow you to use the extension number as a SIP username/password.

 

[Boris.Minakov.ITNow]

For devices that need weak sip credentials, the latest beta does allow you to use the extension number as a SIP username/password.

Thank you so much this was issue with yealink T22, it did nit allow alphabetical characters in username, after update 7Beta, i was able to input 202 as username and it was registerred

Thanks

 

[bit101]

Hi Boris,

I think you probably have some other problem here. At least for the SIP T21P E2 you can use usernames and passwords as generated by 3CX V18 Update 7 without any problems.

We have tested this and can confirm it 100% works when using 3CX V18 Update 7 with T21P E2 firmware 52.84.0.140
And if you use the re-generate function to generate new passwords, the phone will auto-provision and accept them.

The Cisco SPA are legacy phones, we no longer provide any support for them.

While it was easy to see the passwords in the older welcome emails, this is not something we will be doing going forward. We are making changes to increase 3CX security overall, so now the user has to click the new link that appears in their email, and set their own password

View attachment 35437

Hi John,

this is not a ggod idea to let the customer set his own password because user will set always unsecure passwords like "Love3412", "Mycar34" or very similar. I know that from experiances over many years! So therefore it is very important to have secure passwords generate from 3CX!
Is there a possibility to reactivate the passwort generation?

Regards, Norman