[VoiceOps] Escalating a problem with a Cox routing error

Carlos Alvarez caalvarez at gmail.com
Thu Feb 16 17:47:04 EST 2017

I've done that, but they're NOC guys, they don't really give a damn.
That's why I was trying to find some sort of escalation level, or an
"inside guy."

Our customer confirmed that they simply can't bug their customer to do it.
I'm thinking maybe a demand letter sent certified?  I've already had to do
that once, they ported out OUR main number, and we made a monetary demand
after snapping it back.  They paid.

On Thu, Feb 16, 2017 at 2:45 PM, Teal, Brent M <Brent.Teal at charter.com>

> Call them and ask them to remove their local switch translations or you
> will contact the FCC/BBB.  That normally will motivate the losing carrier.
> *Sent from my Verizon 4G LTE Droid*
> On Feb 16, 2017 2:41 PM, Carlos Alvarez <caalvarez at gmail.com> wrote:
> 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@
> 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
> The contents of this e-mail message and
> any attachments are intended solely for the
> addressee(s) and may contain confidential
> and/or legally privileged information. If you
> are not the intended recipient of this message
> or if this message has been addressed to you
> in error, please immediately alert the sender
> by reply e-mail and then delete this message
> and any attachments. If you are not the
> intended recipient, you are notified that
> any use, dissemination, distribution, copying,
> or storage of this message or any attachment
> is strictly prohibited.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/voiceops/attachments/20170216/5b767f8e/attachment.html>

More information about the VoiceOps mailing list