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
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
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
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
Oren, I see your point but respectfully still disagree. Even in the case of 1million DIDs on the same account, while you're not authenticating to any particular DID, you are authenticating to the account and should be able to port any number. Consider the alternative, how would you propose to attribute ownership to phone numbers without an account number? Some security is better than none, right? Cheers, Joshua Sent from my iPhone On Jan 15, 2013, at 4:31 PM, "Oren Yehezkely" <orenyny at gmail.com> wrote:
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
_______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops
participants (3)
-
frnkblk＠iname.com -
j＠2600hz.com -
orenyny＠gmail.com