<div dir="ltr">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."<div><br></div><div>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.</div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Feb 16, 2017 at 2:45 PM, Teal, Brent M <span dir="ltr"><<a href="mailto:Brent.Teal@charter.com" target="_blank">Brent.Teal@charter.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>
<div>
<div>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.</div>
<div><br>
</div>
<div><font style="color:#333333"><i>Sent from my Verizon 4G LTE Droid</i></font></div>
</div><div><div class="h5">
<div class="m_-8029871318520842505elided-text">On Feb 16, 2017 2:41 PM, Carlos Alvarez <<a href="mailto:caalvarez@gmail.com" target="_blank">caalvarez@gmail.com</a>> wrote:<br type="attribution">
</div>
<div>
<div dir="ltr">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.
<div><br>
</div>
<div>I guess I'm going to fall back on telling our customer that a Cox customer has to complain.</div>
<div><br>
</div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Thu, Feb 16, 2017 at 1:40 PM, Jeff Waddell <span dir="ltr">
<<a href="mailto:jeff+voiceops@waddellsolutions.com" target="_blank">jeff+voiceops@<wbr>waddellsolutions.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">When did the port go thru?<br>
<br>
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.
<div><br>
</div>
<div>Or call your Public Utilities commission for the state</div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote"><span>On Thu, Feb 16, 2017 at 3:37 PM, Carlos Alvarez
<span dir="ltr"><<a href="mailto:caalvarez@gmail.com" target="_blank">caalvarez@gmail.com</a>></span> wrote:<br>
</span>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>
<div class="m_-8029871318520842505h5">
<div dir="ltr">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.
<div><br>
</div>
</div>
<div class="m_-8029871318520842505m_-666871729362011935HOEnZb">
<div class="m_-8029871318520842505m_-666871729362011935h5">
<div class="gmail_extra"><br>
<div class="gmail_quote">On Thu, Feb 16, 2017 at 1:36 PM, Matthew Yaklin <span dir="ltr">
<<a href="mailto:myaklin@firstlight.net" target="_blank">myaklin@firstlight.net</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>
<div id="m_-8029871318520842505m_-666871729362011935m_4468235674979805551m_4244232552833716727divtagdefaultwrapper" dir="ltr" style="font-size:12pt;color:#000000;font-family:Calibri,Arial,Helvetica,sans-serif">
<p>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?</p>
<p>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.</p>
<p><br>
</p>
<p>Matt</p>
</div>
<hr style="display:inline-block;width:98%">
<div id="m_-8029871318520842505m_-666871729362011935m_4468235674979805551m_4244232552833716727divRplyFwdMsg" dir="ltr">
<font face="Calibri, sans-serif" color="#000000" style="font-size:11pt"><b>From:</b> VoiceOps <<a href="mailto:voiceops-bounces@voiceops.org" target="_blank">voiceops-bounces@voiceops.org</a><wbr>> on behalf of Carlos Alvarez <<a href="mailto:caalvarez@gmail.com" target="_blank">caalvarez@gmail.com</a>><br>
<b>Sent:</b> Thursday, February 16, 2017 3:19:41 PM<br>
<b>To:</b> <a href="mailto:voiceops@voiceops.org" target="_blank">voiceops@voiceops.org</a><br>
<b>Subject:</b> [VoiceOps] Escalating a problem with a Cox routing error</font>
<div> </div>
</div>
<span>
<div>
<div dir="ltr">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.
<div><br>
</div>
<div>Any ideas?</div>
<div><br>
</div>
</div>
</div>
</span></div>
</blockquote>
</div>
<br>
</div>
</div>
</div>
<br>
</div>
</div>
<span>______________________________<wbr>_________________<br>
VoiceOps mailing list<br>
<a href="mailto:VoiceOps@voiceops.org" target="_blank">VoiceOps@voiceops.org</a><br>
<a href="https://puck.nether.net/mailman/listinfo/voiceops" rel="noreferrer" target="_blank">https://puck.nether.net/mailma<wbr>n/listinfo/voiceops</a><br>
<br>
</span></blockquote>
</div>
<br>
</div>
</blockquote>
</div>
<br>
</div>
</div></div></div>
The contents of this e-mail message and <br>any attachments are intended solely for the <br>addressee(s) and may contain confidential <br>and/or legally privileged information. If you<br>are not the intended recipient of this message<br>or if this message has been addressed to you <br>in error, please immediately alert the sender<br>by reply e-mail and then delete this message <br>and any attachments. If you are not the <br>intended recipient, you are notified that <br>any use, dissemination, distribution, copying,<br>or storage of this message or any attachment <br>is strictly prohibited.</div>
</blockquote></div><br></div>