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

[Oren Yehezkely]

Thank you both.

However it is not practical when a carrier has thousands of TNs for
many end users on the same account number.

If each TN had it's own account then I would agree with you.

Oren

On Tue, Jan 15, 2013 at 4:50 PM, Frank Bulk <frnkblk at iname.com> wrote:
> To the best of my recollection, the one of the few pieces of data needed for
> a port are the telephone number and account number.
> http://www.fcc.gov/guides/portability-keeping-your-phone-number-when-changin
> g-service-providers
> http://hraunfoss.fcc.gov/edocs_public/attachmatch/FCC-09-41A1.pdf page 6,
> comment 32
>
> Frank
>
> -----Original Message-----
> From: voiceops-bounces at voiceops.org [mailto:voiceops-bounces at voiceops.org]
> On Behalf Of Oren Yehezkely
> Sent: Tuesday, January 15, 2013 11:08 AM
> To: voiceops at voiceops.org
> Subject: [VoiceOps] Conversent Communications rejects port out request for
> incorrect account number
>
> 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
>
>