[VoiceOps] Escalating a problem with a Cox routing error

Carlos Alvarez caalvarez at gmail.com
Thu Feb 16 16:40:31 EST 2017

The port completed over a year ago.  Everyone we call at Cox says it works,
because they do their testing from their Vegas switch, but only the Phoenix
switch has issues.

I guess I'm going to fall back on telling our customer that a Cox customer
has to complain.

On Thu, Feb 16, 2017 at 1:40 PM, Jeff Waddell <
jeff+voiceops at waddellsolutions.com> wrote:

> When did the port go thru?
> The translations are still in Cox's switches - if you can find a NOC
> number for Cox, call it and tell them, they will do a lookup in the LERG
> and then remove the translations.
> Or call your Public Utilities commission for the state
> On Thu, Feb 16, 2017 at 3:37 PM, Carlos Alvarez <caalvarez at gmail.com>
> wrote:
>> They seemed very unhappy with that suggestion, so I was looking for other
>> options.  They are lawyers, and don't want to ask their customers to do
>> work for them.
>> On Thu, Feb 16, 2017 at 1:36 PM, Matthew Yaklin <myaklin at firstlight.net>
>> wrote:
>>> 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.
>>> Matt
>>> ------------------------------
>>> *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?
>> _______________________________________________
>> VoiceOps mailing list
>> VoiceOps at voiceops.org
>> https://puck.nether.net/mailman/listinfo/voiceops
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/voiceops/attachments/20170216/5ff57038/attachment-0001.html>

More information about the VoiceOps mailing list