LOL, I would *hope* they are trained not to do that! I've used one of my neighbors to call them and provide call samples. Then Cox does nothing for a week, then asks for another "fresh" call sample. Four times so far.
They are an awesome ISP, but crap for phones. On Thu, Feb 16, 2017 at 2:41 PM, Alex Balashov <[email protected]> wrote: > Isn't there anyone at Cox-Phoenix you can get a hold of? > > "Yes, I understand you're a receptionist. Just try dial this number real > quick..." > > On Thu, Feb 16, 2017 at 02:40:31PM -0700, Carlos Alvarez 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 < > > [email protected]> 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 <[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]> > > >> 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]> on behalf of Carlos > > >>> Alvarez <[email protected]> > > >>> *Sent:* Thursday, February 16, 2017 3:19:41 PM > > >>> *To:* [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] > > >> https://puck.nether.net/mailman/listinfo/voiceops > > >> > > >> > > > > > > _______________________________________________ > > VoiceOps mailing list > > [email protected] > > https://puck.nether.net/mailman/listinfo/voiceops > > > -- > Alex Balashov | Principal | Evariste Systems LLC > > Tel: +1-706-510-6800 / +1-800-250-5920 (toll-free) > Web: http://www.evaristesys.com/, http://www.csrpswitch.com/ >
_______________________________________________ VoiceOps mailing list [email protected] https://puck.nether.net/mailman/listinfo/voiceops
