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" <voice...@ics-il.net> To: "VoiceOps" <voiceops@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@voiceops.org https://puck.nether.net/mailman/listinfo/voiceops
_______________________________________________ VoiceOps mailing list VoiceOps@voiceops.org https://puck.nether.net/mailman/listinfo/voiceops
