Hnngh, talk about an anticlimax. Been hunting down this IP Office chassis to install in the telecoms lab and it *seems* to have a dead internal PSU.
It's gonna get repaired, of course, but it just totally killed all immediate forward progress.
#VoiceLab #OtherNetworks #HomeLab #RetroLab #Avaya #PhoneSystems #PBX #IPOffice
How To Factory Reset Avaya 1608L / 1608 H.323 IP Phone
I really want to get this #Force10 C300 switch into the #HomeLab to play with, but the thing is so damn heavy. Its lived on this cart for like four years now because moving it anywhere else is too arduous.
On top of that is some #Avaya #IPOffice gear, though, and we will definitely be connecting that up to the telephony lab.
Final follow-up to the phone provider porting/shenanigans.
While staying with the same provider; Migrating from a PRI to a cloud voice solution was ridiculous. Started at 1130. One location finished at 1330 another at 1845 and another at almost 1900.
Somehow the actual porting went without any drama, which was absolutely shocking. However, I was informed they had to port our numbers through *another provider* because #Comcast didn't have service in the area. Doesn't make a bit of sense to me, but it worked in the end 🤷♂️
Lastly; I am coming from an OLD #Avaya #IPOffice system.
While the capabilities of #Comcast may be superior their management portal is a pile of crap.
There is no interface that shows the entire call flow. You have to click back and forth UI elements (e.g. "hunt groups" "auto attendants" and "call queues"). These are all links and the important information to understand how it's all tied together is often deeply nested requiring 5-6 clicks JUST to see it.
You cannot simply open it all in separate tabs, Comcast has made their own UI.
The #IPOffice system I am migrating from was very very old and it was vastly superior in it's overview and management tools.
Ety, Ringer of Bells ^G
Linux Renaissance
Tarnkappe.info
James M. Woodward