Avaya E129 phone with errors in 12.1

[oidm]

Unfortunately, Avaya release 12.1 misses some bit details with E129 phones. Those hard phones had the worst issues. They forgot to include that information in the bulletin notes, so the little issue is: 3rd party phones do not auto register after the system reboot. Sometimes got unregistered automatically.

They give information about this issue in the doc SOLN376450, but the solution is to change all E129 phones. I will attach the solution pdf in this post. My worry is warn other people that have E129 phones, and to know if there is some solution for the issue make sure phone can receive and reply to IPO OPTION info. Because you know the E129, actually, are Grandstream in the brackground.


Direct link of solution doc in Avaya Support: https://support.avaya.com/ext/index?page=content&id=SOLN376450&viewlocale=en_US

 

[MikeeOK]

They are such rubbish phones even worse than the 1603. Biff them and get some J129 would be cheaper than mucking around with them

 

[ipohead]

Thanks for the tip off oidm. They are basically a badged Grandstream GXP1165 and I am not sure why these were ever added to the IP Office line up.

 

[oidm]

They are such rubbish phones even worse than the 1603. Biff them and get some J129 would be cheaper than mucking around with them

yeah, we have a lot of customers with those Avaya e129 Phones, this customer has 120 of them. It's a pain in the neck

 

[oidm]

Thanks for the tip off oidm. They are basically a badged Grandstream GXP1165 and I am not sure why these were ever added to the IP Office line up.

It's true, I don't know if Grandstream could help me out

 

[telecomtekperson]

And EOMS for almost 10 years: https://support.avaya.com/css/public/documents/101033015

 

[lauraandonau]

Thanks for sharing this valuable insight! It’s unfortunate that 12.1 skipped over those key details for the E129 phones — especially considering how common they are in some deployments. You're absolutely right: the E129s being Grandstream-based makes troubleshooting a bit trickier if you're expecting native Avaya behavior.

I appreciate you pointing others to SOLN376450. While replacing all the E129s isn't an ideal solution for everyone, it's good to know there's at least a documented workaround. In the meantime, checking that the phones can properly receive and respond to IPO OPTION messages is a smart move — it might help others keep things stable post-reboot without full hardware replacement.

Thanks again for raising awareness. Hopefully, Avaya improves documentation clarity in future releases!