[VoiceOps] Escalating a problem with a Cox routing error

[Carlos Alvarez]

Surely not on purpose, but the fact that they were arrogant ("there's no
way we'd port a number incorrectly") and didn't want to help was the only
reason I went after them for cash.  We wasted a lot of time on the matter.
The porting guy could have researched it and returned it in seconds, but he
simply refused to go find the physical port order.  "My database says we
should port this number."

But hey, I get 330x35 Mbps at home, so they're good as an ISP...



On Thu, Feb 16, 2017 at 3:49 PM, Alex Balashov <abalashov at evaristesys.com>
wrote:

> They slammed YOUR number? That's pretty balsy.
>
> -- Alex
>
> --
> Principal, Evariste Systems LLC (www.evaristesys.com)
>
> Sent from my Google Nexus.
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/voiceops/attachments/20170216/c65d1b37/attachment.html>