[VoiceOps] Escalating a problem with a Cox routing error

Carlos Alvarez caalvarez at gmail.com
Thu Feb 16 15:37:00 EST 2017

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>

> 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?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/voiceops/attachments/20170216/1b6f346f/attachment.html>

More information about the VoiceOps mailing list