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?
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?
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?
?provide CPX NOC the Call Examples of the calls that dont work they can track why that COX customer couldn't place the call? also sometimes re-advertising the TN with the LRN can help 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
-- Izzy Goldstein Chief Technology Officer Main: (212) 477-1000 x 2085 <(212)%20477-1000> Direct: (929) 477-2085 Website: www.telego.com <http://www.telego.net/> <http://www.telego.com/> Confidentiality Notice: This e-mail may contain confidential and/or privileged information. If you are not the intended recipient or have received this e-mail in error please notify us immediately by email reply and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden. Any views or opinions presented in this email are solely those of the author and do not necessarily represent those of TeleGo (T). Employees of TeleGo are expressly required not to make defamatory statements and not to infringe or authorize any infringement of copyright or any other legal right by email communications. Any such communication is contrary to TeleGo policy and outside the scope of the employment of the individual concerned. TeleGo will not accept any liability in respect of such communication, and the employee responsible will be personally liable for any damages or other liability arising. TeleGo Hosted PBX <https://youtu.be/DaT8YAZ4V0w>
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 mdiaz at vinixglobal.com<mailto:mdiaz at vinixglobal.com> 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 <caalvarez at gmail.com<mailto: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<mailto: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<mailto:voiceops-bounces at voiceops.org>> on behalf of Carlos Alvarez <caalvarez at gmail.com<mailto:caalvarez at gmail.com>> Sent: Thursday, February 16, 2017 3:19:41 PM To: voiceops at voiceops.org<mailto: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<mailto:VoiceOps at voiceops.org> https://puck.nether.net/mailman/listinfo/voiceops
Can your porting department poke the people they exchanged paperwork with to tell the Cox switch guys to remove the subs in that local area? I know when I do not move fast enough our porting/prov dept comes hunting for me due to the winning carrier complaining to them. Matt ________________________________ From: VoiceOps <voiceops-bounces at voiceops.org> on behalf of Carlos Alvarez <caalvarez at gmail.com> Sent: Thursday, February 16, 2017 3:37:00 PM To: voiceops at voiceops.org Subject: Re: [VoiceOps] Escalating a problem with a Cox routing error 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<mailto: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<mailto:voiceops-bounces at voiceops.org>> on behalf of Carlos Alvarez <caalvarez at gmail.com<mailto:caalvarez at gmail.com>> Sent: Thursday, February 16, 2017 3:19:41 PM To: voiceops at voiceops.org<mailto: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?
participants (4)
-
caalvarez＠gmail.com -
igoldstein＠telego.net -
mdiaz＠vinixglobal.com -
myaklin＠firstlight.net