[VoiceOps] Conversent Communications rejects port out request for incorrect account number

[Joshua Goldbard]

Hi,

Have you tried contacting conversant or your client to verify the account info for the port?

It might be strange that companies are actually following porting guidelines, but there's always been a requirement to include the account number.

Once upon a time I was working at the big bell and was asked to port the main number for Yellow Cab to a cellphone. In this case it was easy to say no (and not having the account number also helped) but one can imagine that with less famous clients (or less scrupulous reps) anyone could steal any number if there's no authentication.

So yeah it's lame that you actually have to include the account number, but there are good reasons.

Cheers,
Joshua

Sent from my iPhone

On Jan 15, 2013, at 9:10 AM, "Oren Yehezkely" <orenyny at gmail.com> wrote:

> Hi,
> 
> Does anybody have a clue why all of a sudden carriers started
> rejecting port out requests for an incorrect account number?
> Specifically done by Conversent Communications, but I think that L3
> and Global Crossing also started rejecting requests with this reason.
> 
> Until now this type of rejection was received for cell phone numbers only.
> 
> Any idea how to resolve it?
> 
> Thanks,
> 
> Oren
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops