Typically, the new carrier would open the ticket with LNP from the losing 
carrier (Cox) and request the numbers be removed. If that does not yield a 
timely response, open an online complaint with the FCC.



[Vinix]            <http://www.vinixglobal.com>


Mark Diaz
[email protected]<mailto:[email protected]>

Vinix
Office: +1 954-414-1224 x1002  / Fax: +1 954-414-1225
6043 Kimberly Blvd Ste QNorth Lauderdale, FL 33068
www.vinixglobal.com<http://www.vinixglobal.com>

[Twitter]  <https://www.twitter.com/vinixglobal>   [Facebook]   
<https://www.facebook.com/govinix>   [LinkedIn]   
<https://www.linkedin.com/company/vinix-technologies-inc->





On Feb 16, 2017, at 3:37 PM, Carlos Alvarez 
<[email protected]<mailto:[email protected]>> 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 
<[email protected]<mailto:[email protected]>> 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 
<[email protected]<mailto:[email protected]>> on behalf 
of Carlos Alvarez <[email protected]<mailto:[email protected]>>
Sent: Thursday, February 16, 2017 3:19:41 PM
To: [email protected]<mailto:[email protected]>
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
[email protected]<mailto:[email protected]>
https://puck.nether.net/mailman/listinfo/voiceops

_______________________________________________
VoiceOps mailing list
[email protected]
https://puck.nether.net/mailman/listinfo/voiceops

Reply via email to