• We do not provide troubleshooting help for unsupported phones. Please try with a supported phone.
  • V20 Update 10 Alpha 2 Learn more

not possible to provision new Avaya Legacy SIP phones since Update 6

Status
Not open for further replies.

Gummies

Premier Customer
Advanced Certified
Joined
Apr 30, 2020
Messages
34
Reaction score
14
Dear 3CX team, I would like to express my concern regarding the recent change in version 18.0 Update 6, in which the authentication has been increased to 10 characters and has resulted in the removal of AVAYA phone provisioning without prior notice. As a 3CX user who still uses several of these phones,.

I would like to ask that you reconsider your decision and find a solution that allows businesses to continue using their AVAYA phones without compromising the security of their systems. I understand that it is important to stay up-to-date with the latest technologies, but it is also important to recognize the value of older equipment and provide options for users to continue using them.

Thank you for your attention, and I look forward to your response.
 
Yes, it seems Avaya hardware requires Auth ID to be the same as the extension. Of course this is quite insecure. However we are going to consider a setting that you can switch off this validation at your own risk so that you can allow the Avaya phones to connect again...
 
Hi @Nick Galea ,

Yes, that would be a good thing, we are experiencing the same issue with some Castel intercoms that cannot differentiate between the SIP identifier and the SIP login (only one field).

Thank you :)
François
 
hello, we are having problems here too because of the last update, we have several 3cx systems with avaya 9608G phones. I hope that 3cx soon releases an update that reverses this situation. I don't see how to tell my customers that they have to change all the phones.

Ícone Verificada pela comunidade
 
Hello, Any news about this case? We are having a lot of problems, we have a lot of customers, with a lot of awaya phones that need or will need changes in their extensions. We are concerned about this situation.

Ícone Verificada pela comunidade
 
Hello Nick, I was wondering if there are any plans to address this issue or if 3CX has officially decided to discard these units?
 
Hello, the restriction is removed in the Update 7A and you will be able to use them again.
 
Can we be provisioning Avaya 9608G IP phone in 3CX V18 Standard / Startup Free edition? also requesting 3CX at least allow to add phone template in Startup edition so that we can test phones and offer to the customer.

I have gone trough forum where mentioned procedures to provision Cisco SPA504G phones but we can't add this phones in Startup edition !!

Even if we download and add the firmware in to provisioning directory it would not show up in phone template list in the settings, would be appreciated if someone can help on this issue in Startup edition V18.
 
Last edited:
  • Like
Reactions: pilevic
Update 7A is out as an Alpha test build, you can now change your Auth ID.
 
Status
Not open for further replies.

Forum statistics

Threads
112,147
Messages
590,959
Members
165,167
Latest member
Finatra.us