Re: [VoiceOps] Test Numbers

2022-03-16 Thread Robert Schoneman via VoiceOps
800-437-7950 has been what we’ve used for as long as I can recall. From: VoiceOps On Behalf Of Mike Hammett Sent: Wednesday, March 16, 2022 1:40 PM To: voiceops@voiceops.org Subject: Re: [VoiceOps] Test Numbers A tangent off of this. What numbers are you using to report back to the caller the

Re: [VoiceOps] Five9 Issues / DDoS?

2021-09-27 Thread Robert Schoneman via VoiceOps
Didn’t Five9 use Voxbone who became part of Bandwidth.com? Also with the sale of Five9 to Zoom and Zoom using Bandwidth.com… From: VoiceOps On Behalf Of Ivan Kovacevic via VoiceOps Sent: Monday, September 27, 2021 6:19 PM To: VoiceOps Subject: [VoiceOps] Five9 Issues / DDoS? So we have a

Re: [VoiceOps] Market Leaders?

2021-06-22 Thread Robert Schoneman via VoiceOps
Bandwidth is who provides MS’s calling plans for Business Voice (Teams calling). Wouldn’t surprise me at all if MS is their biggest customer. From: VoiceOps On Behalf Of Mike Hammett Sent: Tuesday, June 22, 2021 8:33 PM To: VoiceOps Subject: [VoiceOps] Market Leaders? Does anyone other than

Re: [VoiceOps] CSR BTN

2021-06-04 Thread Robert Schoneman via 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.

Re: [VoiceOps] CSR BTN

2021-05-29 Thread Robert Schoneman via VoiceOps
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