Does a CSR have to have the specific number being ported or just any number on the account? We're testing a third party network that we'll utilize in the short-term for out-of-area usage. We ported some of our own numbers to our account at the third party. The CSRs arrived with the main BTN on the account, not the number being ported. Our porting person rejected the CSRs because they weren't for the number being ported. Of course she knew what number was being attempted because it was an internal operation, but normally she wouldn't. It's my thought that the CSR is a customer information verification process. We wouldn't know the number actually being ported until the LSR came. Does the name, address, account number, TN, etc. match an account you have? If so, great. Where can I find a good resource on the process and what's normally acceptable for rejections? Of course I said, "Let me verify this before we do anything" and then she replied to the CSRs rejecting. *sigh* I guess we'll really be testing all scenarios. ----- Mike Hammett Intelligent Computing Solutions http://www.ics-il.com Midwest Internet Exchange http://www.midwest-ix.com
As a customer doing porting from one carrier to another my experience has been the CSR is just a record of everything (phone number, circuit, trunk, etc) on an account or BTN. It's not a verification document, per se. But is often used during porting to verify information if the port order gets rejected by the losing carrier or if the port order is somehow incomplete or fails an initial verification. All the CSRs I've ever seen were just everything on the BTN and weren't specific to the port order in question. That is, if I was porting 5 numbers from a BTN and there's 100 numbers on the BTN, the CSR would include all 100 numbers regardless of the port order. I've not seen any consistency with regards to what details are on the CSRs from one carrier to another. Some are quite verbose, and others are little more than a list of numbers. ________________________________ From: VoiceOps <voiceops-bounces at voiceops.org> on behalf of Mike Hammett <voiceops at ics-il.net> Sent: Friday, May 28, 2021 10:51 PM To: VoiceOps <voiceops at voiceops.org> Subject: [VoiceOps] CSR BTN Does a CSR have to have the specific number being ported or just any number on the account? We're testing a third party network that we'll utilize in the short-term for out-of-area usage. We ported some of our own numbers to our account at the third party. The CSRs arrived with the main BTN on the account, not the number being ported. Our porting person rejected the CSRs because they weren't for the number being ported. Of course she knew what number was being attempted because it was an internal operation, but normally she wouldn't. It's my thought that the CSR is a customer information verification process. We wouldn't know the number actually being ported until the LSR came. Does the name, address, account number, TN, etc. match an account you have? If so, great. Where can I find a good resource on the process and what's normally acceptable for rejections? Of course I said, "Let me verify this before we do anything" and then she replied to the CSRs rejecting. *sigh* I guess we'll really be testing all scenarios. ----- Mike Hammett Intelligent Computing Solutions http://www.ics-il.com<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.ics-2Dil.com&d=DwQFaQ&c=euGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM&r=O9zkNrKbQF1fgs1KTBRWpbNPvZEkJNea930OX6UPkBE&m=aR5JTq8SllMct1kRkYd2qv2GOoPcv9M9LFoAy20REIs&s=ImMHidIuRKsJodab9BGmkKWxVVa-0KwXhVZftefq3MQ&e=> Midwest Internet Exchange http://www.midwest-ix.com<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.midwest-2Dix.com&d=DwQFaQ&c=euGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM&r=O9zkNrKbQF1fgs1KTBRWpbNPvZEkJNea930OX6UPkBE&m=aR5JTq8SllMct1kRkYd2qv2GOoPcv9M9LFoAy20REIs&s=xr8izRMQ6mfH9a90W1aHPbgdH8NAZI9JsmyPlsion90&e=>
+1 to all that, Vonage for example often gives us a basic Excel sheet as a CSR. It's like they're a mom and pop shop with an admin assistant typing into Excel. Centurylink will sometimes give us hundreds of numbers on a CSR, some of which don't actually seem to belong to the customer. On Sat, May 29, 2021 at 12:50 PM Robert Schoneman via VoiceOps < voiceops at voiceops.org> wrote:
As a customer doing porting from one carrier to another my experience has been the CSR is just a record of everything (phone number, circuit, trunk, etc) on an account or BTN. It's not a verification document, per se. But is often used during porting to verify information if the port order gets rejected by the losing carrier or if the port order is somehow incomplete or fails an initial verification.
All the CSRs I've ever seen were just everything on the BTN and weren't specific to the port order in question. That is, if I was porting 5 numbers from a BTN and there's 100 numbers on the BTN, the CSR would include all 100 numbers regardless of the port order.
I've not seen any consistency with regards to what details are on the CSRs from one carrier to another. Some are quite verbose, and others are little more than a list of numbers.
------------------------------ *From:* VoiceOps <voiceops-bounces at voiceops.org> on behalf of Mike Hammett <voiceops at ics-il.net> *Sent:* Friday, May 28, 2021 10:51 PM *To:* VoiceOps <voiceops at voiceops.org> *Subject:* [VoiceOps] CSR BTN
Does a CSR have to have the specific number being ported or just any number on the account?
We're testing a third party network that we'll utilize in the short-term for out-of-area usage. We ported some of our own numbers to our account at the third party. The CSRs arrived with the main BTN on the account, not the number being ported. Our porting person rejected the CSRs because they weren't for the number being ported. Of course she knew what number was being attempted because it was an internal operation, but normally she wouldn't.
It's my thought that the CSR is a customer information verification process. We wouldn't know the number actually being ported until the LSR came. Does the name, address, account number, TN, etc. match an account you have? If so, great.
Where can I find a good resource on the process and what's normally acceptable for rejections?
Of course I said, "Let me verify this before we do anything" and then she replied to the CSRs rejecting. *sigh* I guess we'll really be testing all scenarios.
----- Mike Hammett Intelligent Computing Solutions http://www.ics-il.com <https://urldefense.proofpoint.com/v2/url?u=http-3A__www.ics-2Dil.com&d=DwQFa...>
Midwest Internet Exchange http://www.midwest-ix.com <https://urldefense.proofpoint.com/v2/url?u=http-3A__www.midwest-2Dix.com&d=D...>
_______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops
I guess to back up to a more basic level... What's the intent of the CSR? I thought it was for the gaining carrier to verify customer information with the losing carrier that would be required to port a number before actually issuing the LSR\port request. ----- Mike Hammett Intelligent Computing Solutions http://www.ics-il.com Midwest Internet Exchange http://www.midwest-ix.com ----- Original Message ----- From: "Mike Hammett" <voiceops at ics-il.net> To: "VoiceOps" <voiceops at voiceops.org> Sent: Friday, May 28, 2021 9:51:14 PM Subject: [VoiceOps] CSR BTN Does a CSR have to have the specific number being ported or just any number on the account? We're testing a third party network that we'll utilize in the short-term for out-of-area usage. We ported some of our own numbers to our account at the third party. The CSRs arrived with the main BTN on the account, not the number being ported. Our porting person rejected the CSRs because they weren't for the number being ported. Of course she knew what number was being attempted because it was an internal operation, but normally she wouldn't. It's my thought that the CSR is a customer information verification process. We wouldn't know the number actually being ported until the LSR came. Does the name, address, account number, TN, etc. match an account you have? If so, great. Where can I find a good resource on the process and what's normally acceptable for rejections? Of course I said, "Let me verify this before we do anything" and then she replied to the CSRs rejecting. *sigh* I guess we'll really be testing all scenarios. ----- Mike Hammett Intelligent Computing Solutions http://www.ics-il.com Midwest Internet Exchange http://www.midwest-ix.com _______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops
Depends on where the CSR is coming from. If coming from an RBOC I?ve always used it as an inventory of TNs and features. I?m mostly interested in the TNs so I ensure I don?t miss a number when porting. From non-RBOCs the CSR is essentially worthless as the information is incomplete or invalid. From: VoiceOps <voiceops-bounces at voiceops.org> on behalf of Mike Hammett <voiceops at ics-il.net> Date: Wednesday, June 2, 2021 at 9:14 AM To: VoiceOps <voiceops at voiceops.org> Subject: Re: [VoiceOps] CSR BTN CAUTION: This email originated from outside of Crocker. Do not click links or open attachments unless you recognize the sender and know the content is safe. I guess to back up to a more basic level... What's the intent of the CSR? I thought it was for the gaining carrier to verify customer information with the losing carrier that would be required to port a number before actually issuing the LSR\port request. ----- Mike Hammett Intelligent Computing Solutions http://www.ics-il.com Midwest Internet Exchange http://www.midwest-ix.com ________________________________ From: "Mike Hammett" <voiceops at ics-il.net> To: "VoiceOps" <voiceops at voiceops.org> Sent: Friday, May 28, 2021 9:51:14 PM Subject: [VoiceOps] CSR BTN Does a CSR have to have the specific number being ported or just any number on the account? We're testing a third party network that we'll utilize in the short-term for out-of-area usage. We ported some of our own numbers to our account at the third party. The CSRs arrived with the main BTN on the account, not the number being ported. Our porting person rejected the CSRs because they weren't for the number being ported. Of course she knew what number was being attempted because it was an internal operation, but normally she wouldn't. It's my thought that the CSR is a customer information verification process. We wouldn't know the number actually being ported until the LSR came. Does the name, address, account number, TN, etc. match an account you have? If so, great. Where can I find a good resource on the process and what's normally acceptable for rejections? Of course I said, "Let me verify this before we do anything" and then she replied to the CSRs rejecting. *sigh* I guess we'll really be testing all scenarios. ----- Mike Hammett Intelligent Computing Solutions http://www.ics-il.com Midwest Internet Exchange http://www.midwest-ix.com _______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops
The RBOCs use the CSR as their internal record of each USOC / rate associated with the service/account. It is true that non-RBOC carriers do not keep as detailed records but it should still tell you all the services associated with each account number. MARY LOU CAREY BackUP Telecom Consulting Office: 615-791-9969 Cell: 615-796-1111 On 2021-06-02 08:10 AM, Mike Hammett wrote:
I guess to back up to a more basic level...
What's the intent of the CSR?
I thought it was for the gaining carrier to verify customer information with the losing carrier that would be required to port a number before actually issuing the LSR\port request.
----- Mike Hammett Intelligent Computing Solutions http://www.ics-il.com
Midwest Internet Exchange http://www.midwest-ix.com
-------------------------
From: "Mike Hammett" <voiceops at ics-il.net> To: "VoiceOps" <voiceops at voiceops.org> Sent: Friday, May 28, 2021 9:51:14 PM Subject: [VoiceOps] CSR BTN
Does a CSR have to have the specific number being ported or just any number on the account?
We're testing a third party network that we'll utilize in the short-term for out-of-area usage. We ported some of our own numbers to our account at the third party. The CSRs arrived with the main BTN on the account, not the number being ported. Our porting person rejected the CSRs because they weren't for the number being ported. Of course she knew what number was being attempted because it was an internal operation, but normally she wouldn't.
It's my thought that the CSR is a customer information verification process. We wouldn't know the number actually being ported until the LSR came. Does the name, address, account number, TN, etc. match an account you have? If so, great.
Where can I find a good resource on the process and what's normally acceptable for rejections?
Of course I said, "Let me verify this before we do anything" and then she replied to the CSRs rejecting. *sigh* I guess we'll really be testing all scenarios.
----- Mike Hammett Intelligent Computing Solutions http://www.ics-il.com
Midwest Internet Exchange http://www.midwest-ix.com
_______________________________________________ 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
My experience with a CSR is that it's only required if the port order fails (rejected by losing carrier). The winning carrier will often verify that all the TNs belong to the losing carrier listed on the port order and use that as an easy way to "check" the port order without a CSR. ________________________________ From: VoiceOps <voiceops-bounces at voiceops.org> on behalf of Mike Hammett <voiceops at ics-il.net> Sent: Wednesday, June 2, 2021 9:10 AM To: VoiceOps <voiceops at voiceops.org> Subject: Re: [VoiceOps] CSR BTN I guess to back up to a more basic level... What's the intent of the CSR? I thought it was for the gaining carrier to verify customer information with the losing carrier that would be required to port a number before actually issuing the LSR\port request. ----- Mike Hammett Intelligent Computing Solutions http://www.ics-il.com<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.ics-2Dil.com&d=DwQFaQ&c=euGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM&r=O9zkNrKbQF1fgs1KTBRWpbNPvZEkJNea930OX6UPkBE&m=-ThpB4WHh29HhQvUzJX3BwMwbc_rwonPWCOM6MaVisg&s=jZrZSiZcvWtHOhSE8AbKiPvnyuAJAQQqqMC-Q4kj5hU&e=> Midwest Internet Exchange http://www.midwest-ix.com<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.midwest-2Dix.com&d=DwQFaQ&c=euGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM&r=O9zkNrKbQF1fgs1KTBRWpbNPvZEkJNea930OX6UPkBE&m=-ThpB4WHh29HhQvUzJX3BwMwbc_rwonPWCOM6MaVisg&s=CjNKq0dxRw1Qt_YrzsLIN-mfXxuGZtbN500gLYlQv5c&e=> ________________________________ From: "Mike Hammett" <voiceops at ics-il.net> To: "VoiceOps" <voiceops at voiceops.org> Sent: Friday, May 28, 2021 9:51:14 PM Subject: [VoiceOps] CSR BTN Does a CSR have to have the specific number being ported or just any number on the account? We're testing a third party network that we'll utilize in the short-term for out-of-area usage. We ported some of our own numbers to our account at the third party. The CSRs arrived with the main BTN on the account, not the number being ported. Our porting person rejected the CSRs because they weren't for the number being ported. Of course she knew what number was being attempted because it was an internal operation, but normally she wouldn't. It's my thought that the CSR is a customer information verification process. We wouldn't know the number actually being ported until the LSR came. Does the name, address, account number, TN, etc. match an account you have? If so, great. Where can I find a good resource on the process and what's normally acceptable for rejections? Of course I said, "Let me verify this before we do anything" and then she replied to the CSRs rejecting. *sigh* I guess we'll really be testing all scenarios. ----- Mike Hammett Intelligent Computing Solutions http://www.ics-il.com<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.ics-2Dil.com&d=DwQFaQ&c=euGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM&r=O9zkNrKbQF1fgs1KTBRWpbNPvZEkJNea930OX6UPkBE&m=-ThpB4WHh29HhQvUzJX3BwMwbc_rwonPWCOM6MaVisg&s=jZrZSiZcvWtHOhSE8AbKiPvnyuAJAQQqqMC-Q4kj5hU&e=> Midwest Internet Exchange http://www.midwest-ix.com<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.midwest-2Dix.com&d=DwQFaQ&c=euGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM&r=O9zkNrKbQF1fgs1KTBRWpbNPvZEkJNea930OX6UPkBE&m=-ThpB4WHh29HhQvUzJX3BwMwbc_rwonPWCOM6MaVisg&s=CjNKq0dxRw1Qt_YrzsLIN-mfXxuGZtbN500gLYlQv5c&e=> _______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops<https://urldefense.proofpoint.com/v2/url?u=https-3A__puck.nether.net_mailman_listinfo_voiceops&d=DwQFaQ&c=euGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM&r=O9zkNrKbQF1fgs1KTBRWpbNPvZEkJNea930OX6UPkBE&m=-ThpB4WHh29HhQvUzJX3BwMwbc_rwonPWCOM6MaVisg&s=iTLDBu_NiDo3ue9WyH9CxVPuj9zAmr9ddTBd5SSsrjI&e=>
Yes, but building CSRs standard as part of the business processes around porting can pay efficiency dividends with those rejection scenarios, and reduce the rate of rejections. At least, that was my observation in my time in the LEC world. It's good to make one's porting requests more robust from the get-go. On 6/4/21 9:54 AM, Robert Schoneman via VoiceOps wrote:
My experience with a CSR is that it's only required if the port order fails (rejected by losing carrier). The winning carrier will often verify that all the TNs belong to the losing carrier listed on the port order and use that as an easy way to "check" the port order without a CSR -- Alex Balashov | Principal | Evariste Systems LLC
Tel: +1-706-510-6800 / +1-800-250-5920 (toll-free) Web: http://www.evaristesys.com/, http://www.csrpswitch.com/
participants (6)
-
abalashov＠evaristesys.com -
caalvarez＠gmail.com -
marylou＠backuptelecom.com -
matthew＠corp.crocker.com -
rschoneman＠blumenthalarts.org -
voiceops＠ics-il.net