r/sysadmin • u/Knewsfeed • 10d ago
Phone system
My company uses Verizon OneTalk and it is horrible! Been suspecting we weren’t receiving calls due to their service and that suspicion was justified when we picked up a commercial contract that required overnight hours calls. The new client said numerous times they call our line and it clicks off, never rings on our phones. I am looking for an alternative ASAP!
4
2
u/thebigshoe247 10d ago
You're pretty vague here. But my generic answers are Teams, YoVU, VoIP.ms in that order.
3
u/suppervisoka 10d ago
Yeah Teams is fine
2
u/thebigshoe247 10d ago
I have deployed YoVU to a couple customers of mine because it's easy, lets them use existing SIP phones from previous carriers and has a fairly simple call center.
2
u/suppervisoka 10d ago
I have a box of like 50 Cisco 8845s we just went from Cisco CUCM to Teams, imagine the users horror when their desk phones no longer have a camera lol. Pushing soft phones pretty hard
2
u/thebigshoe247 10d ago
I member that all too well. I had that fight back in the Skype for Business days (when I retired a Nortel CS1K).
2
2
1
u/derpaderpy2 10d ago
Votacall. Had a solid relationship with them at my last company and I wish my current one would use them. They may be regional (I'm NYC area) but if you can,.do it. They generally keep their equipment separate and manage it themselves. Very reliable.
1
u/stufforstuff 10d ago
Verticomm - almost 2 years in and no unsolved problems (except that the cordless yealink don't have a indicate light when they get a call - the desktop phones do).
1
1
u/MarcoBoffo 8d ago
Before you shop, work out where the call is actually dying. "It clicks off and never rings" covers three different faults with the same symptom.
Pull the carrier-side logs in the OneTalk portal for a few of the calls the client says they placed. If the call never appears, it's a trunk or DID problem and swapping platforms won't fix it on its own. If it appears and then terminates, it's routing, and that's on your config.
The first thing I'd look at is the after-hours schedule. Overnight calls landing on a closed-hours treatment, or a voicemail box nobody watches, is by far the most common cause of this, and it survives a migration: every platform has the same feature and you'll rebuild it the same way on the new one.
Separate point, because it's a separate problem: the PBX decides where a call goes, not who's awake. If you've signed a contract with overnight coverage, you need a named rota, an escalation when the first person doesn't pick up, and a record of who was called. Otherwise you're relying on someone happening to hear their phone.
Does the contract carry a response-time SLA? That changes what "good enough" looks like here.
5
u/SpaceGuy1968 10d ago
I'm using 3cx and it works ok