Wandering Thoughts archives

2023-11-30

My sysadmin's view of going from Centrex to VoIP (sort of)

I recently read j. b. crawford's Centrex, about the telephone service by that name that was offered to organizations in at least the US and Canada. It sparked not so much nostalgia as memories, because up until very recently the University of Toronto's downtown campus used Centrex, complete with what I now know (from the article) is a distinctive Centrex pattern of five-digit dialing for phone numbers inside the organization. In the University of Toronto's case, most phone numbers were 978-xxxx and so it was common for people and documentation to list numbers as, for example, '8-4942', which is what you actually dialed on a Centrex phone. If you were calling from a non-Centrex line, you were expected to remember the '97' in front.

(It's probably not hard to still find online web pages that talk about our numbers that way, never mind physical signs around the university. There are some remarkably old signs on things.)

I'm not sure what drove the university to move away from Centrex (if I was ever told I've forgotten now); it might have been the potential for cost savings, or it might have been Bell Canada suggesting that Centrex rates might or would be going up. The university's general replacement for our Centrex service was (and is) Voice over IP (VoIP). The actual rollout was rather slow, partly because it was just getting started in early 2020 and you can guess what happened next. You can still get hardwired phone lines if you want to, but they're now much more costly than they used to be (and the cost is paid by your department or group), so they tend to be reserved for situations where you really need them.

(We have one such line in our machine room for safety reasons.)

In general I'm sure Voice over IP is fine, but from a sysadmin's view it has a little problem, at least as implemented here at the university. That issue is that it runs over your regular network. There is no separate physical or even logical network for VoIP phones; instead you plunk them down on your department's network in some convenient place (physically and logically), and then they phone home to establish their VoIP circuits. For regular usage this is fine, but one of the times sysadmins may need to use their phones is exactly when the network is broken and they need to call someone about it. If your phone is VoIP and it runs over your broken network, you have a problem.

(The university's current VoIP setup also has some nice conveniences, like emailing you recordings of any voicemail messages people have left you, so you don't have to deal with the phone's voicemail interface and can just play them on your computer.)

The department could have dealt with this problem for us by leaving us on hardwired phone lines even after Centrex service stopped. However, it was cheaper to get us basic cellphones (with voice-only plans). At this point we've gone through three different models for reasons outside the scope of this entry; the current one and the previous one have been actual Android devices, which I haven't been too impressed with. But they work to make phone calls, probably, and they also do a few other things (also).

(One of the things we don't use these phones for is MFA authentication; instead we have much smaller and more convenient physical tokens. Nor do we normally carry them around, especially out of hours; in my group, everyone's smartphones spend all their time on their office desks. We view them almost entirely as a replacement for our old desk phones.)

sysadmin/CentrexToVoIPSysadminView written at 22:52:33; Add Comment


Page tools: See As Normal.
Search:
Login: Password:
Atom Syndication: Recent Pages, Recent Comments.

This dinky wiki is brought to you by the Insane Hackers Guild, Python sub-branch.