[VoiceOps] Testing DIDs from multiple providers

Joshua Goldbard j at 2600hz.com
Mon Apr 29 15:56:14 EDT 2013

Is this something the community would be willing to pay for?

I'd be willing to do more investigation into building a service like this if there's value here. Would you be willing to pay say $1 to test a DID on say 20 carriers?


Joshua Goldbard
VP of Marketing, 2600hz

116 Natoma Street, Floor 2
San Francisco, CA, 94104
415.886.7923 | j at 2600hz.com<mailto:j at 2600hz.com>

On Apr 29, 2013, at 12:33 PM, Peter Beckman <beckman at angryox.com<mailto:beckman at angryox.com>> wrote:

As a VoIP provider of numbers, we occasionally get complaints that a number
isn't working, or isn't working for specific callers. The trouble I'm
having is figuring out how to automate a test for this.

I've got an automated test now that makes a test call from a number known
to always ring busy. When my switch sees that CallerID, it plays a busy
signal and records the call in our database so I can have a record of a
successful test. When the number really is broken, that test consistently
fails and I have good data with which I can bug the carrier.

Most VoIP termination providers use Verizon or L3 or another major
provider. Often my DIDs are from them, so the calls always succeed within
the network. Often Verizon and L3 are both working when the customer

The issue is that sometimes its a cell carrier like Sprint that doesn't
route the number correctly, or even Comcast Business, though a Comcast home
phone successfully called the DID.

Is there any company out there that provides an API that allows me to
submit a request for a test of a number and will try that DID on a bunch of
carriers and report back? I suppose if you aren't the endpoint for that
DID, might be hard to automate, but I have ideas.

Peter Beckman                                                  Internet Guy
beckman at angryox.com<mailto:beckman at angryox.com>                                 http://www.angryox.com/
VoiceOps mailing list
VoiceOps at voiceops.org<mailto:VoiceOps at voiceops.org>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/voiceops/attachments/20130429/09bcfc2d/attachment.html>

More information about the VoiceOps mailing list