[VoiceOps] Escalating a problem with a Cox routing error

Matthew Yaklin myaklin at firstlight.net
Thu Feb 16 15:36:03 EST 2017

Does the customer know anyone who is local to them that uses Cox and would kindly open up a ticket with Cox listing the ported numbers they cannot call?

That may be a possible fix if your customer understands your predicament and feels they can ask that Cox customer for a bit of help.


From: VoiceOps <voiceops-bounces at voiceops.org> on behalf of Carlos Alvarez <caalvarez at gmail.com>
Sent: Thursday, February 16, 2017 3:19:41 PM
To: voiceops at voiceops.org
Subject: [VoiceOps] Escalating a problem with a Cox routing error

We have a customer who ported us/Onvoy from Cox.  Nobody in the local area with Cox lines can call them, so clearly they didn't remove the numbers from their switch.  But their NOC is in Vegas, and they *can* call these numbers.  So they claim there's no problem on their end.  Onvoy says they never see these calls, so clearly it's a Cox issue.  Cox won't really respond to me much because I'm not their customer.

Any ideas?

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/voiceops/attachments/20170216/eef2e947/attachment.html>

More information about the VoiceOps mailing list