[VoiceOps] Escalating a problem with a Cox routing error
caalvarez at gmail.com
Thu Feb 16 18:47:56 EST 2017
The Cox issue is being fixed. Remember that my customer is a law office.
When the office manager told her boss that Cox told us to pound sand, he
made a call to their chief legal officer. Five minutes later I had a
call. Then a second, and now they said it will be fixed within two hours.
On Thu, Feb 16, 2017 at 4:43 PM, Jared Geiger <jared at compuwizz.net> wrote:
> Snapbacks can be done quickly if the carrier is modern and not full of red
> or blue tape *wink*. Someone ported a bunch of Peerless numbers away from
> us once and Peerless had them back to us within an hour. Plus somehow
> flagged our account that any port out request will be verified by us first.
> On Thu, Feb 16, 2017 at 3:15 PM, Carlos Alvarez <caalvarez at gmail.com>
>> 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
>> On Thu, Feb 16, 2017 at 4:01 PM, Alex Balashov <abalashov at evaristesys.com
>> > wrote:
>>> 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
>> VoiceOps mailing list
>> VoiceOps at voiceops.org
> VoiceOps mailing list
> VoiceOps at voiceops.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the VoiceOps