[VoiceOps] Escalating a problem with a Cox routing error

Carlos Alvarez caalvarez at gmail.com
Thu Feb 16 18:15:41 EST 2017

I don't know the internal machinations of the porting process.  I can tell
you that I've had Cox port out a block of numbers in literally seconds.
The losing carrier refused to respond, the Cox NOC asked a bunch of
recorded questions about ownership, and tap-tap-tap-done.

I was under the impression that a snapback could be done extremely quickly.

On Thu, Feb 16, 2017 at 4:01 PM, Alex Balashov <abalashov at evaristesys.com>

> Surely he couldn't have returned it in seconds. It'd still require a whole
> new NPAC subscription, concurrency window, and what have you?
> -- 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/599646c4/attachment-0001.html>

More information about the VoiceOps mailing list