So, since my last post on the topic of the Nortel/Avaya 1120E was way back in 2016, and since I never read the kind reply of icns01, I also never updated on the final word on these phones here. I was reminded today by a private message about these phones asking if I were still using them. So, as Paul Harvey would have said, here is the rest of the story:
After the issues I had with v14 and these phones unregistering/re-registering every half hour, we decided to purchase replacement phones. I was hoping for budget to purchase something more modern, but instead I found a quantity of Cisco 7960's for $9 each; to make a long story short, we purchased 50 of them at this price back in August of 2016. And while I know they aren't the best-supported phones for 3CX, hey, at $9 each we'll work with them as long as 3CX works with them.
Beginning in late 2016, after the 7960's arrived, I began rolling them out little by little as people requested or needed them, but I didn't just en mass migrate away from the 1120's, since they were still mostly usable. By the time 3CX v15 came around, I was down to less than a dozen 1120's (we have 1120SA's, not 1120E's, but the 1120E SIP firmware loads and runs fine); at that point, they broke completely. Here's what I wrote to my staff about the issue:
So I'm writing this to put a period on the end of this sentence started so long ago, so that people with this phone who read that early thread won't get a false sense of hope; if I could, I would edit that thread to say what I'm saying in this post there. Back when I first started trying to get these to work, I had contacted both 3CX and Avaya support; both said they were 'fully' SIP compliant; both said the other was at fault, and neither were willing to change anything to support the other, which is why I originally posted the workaround that I found. But the quirk quit working, back at 3CX v15, so I no longer have any 1120's in service.
After the issues I had with v14 and these phones unregistering/re-registering every half hour, we decided to purchase replacement phones. I was hoping for budget to purchase something more modern, but instead I found a quantity of Cisco 7960's for $9 each; to make a long story short, we purchased 50 of them at this price back in August of 2016. And while I know they aren't the best-supported phones for 3CX, hey, at $9 each we'll work with them as long as 3CX works with them.
Beginning in late 2016, after the 7960's arrived, I began rolling them out little by little as people requested or needed them, but I didn't just en mass migrate away from the 1120's, since they were still mostly usable. By the time 3CX v15 came around, I was down to less than a dozen 1120's (we have 1120SA's, not 1120E's, but the 1120E SIP firmware loads and runs fine); at that point, they broke completely. Here's what I wrote to my staff about the issue:
So I'm writing this to put a period on the end of this sentence started so long ago, so that people with this phone who read that early thread won't get a false sense of hope; if I could, I would edit that thread to say what I'm saying in this post there. Back when I first started trying to get these to work, I had contacted both 3CX and Avaya support; both said they were 'fully' SIP compliant; both said the other was at fault, and neither were willing to change anything to support the other, which is why I originally posted the workaround that I found. But the quirk quit working, back at 3CX v15, so I no longer have any 1120's in service.
