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 complains. 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. Beckman --------------------------------------------------------------------------- Peter Beckman Internet Guy beckman at angryox.com http://www.angryox.com/ ---------------------------------------------------------------------------
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? Cheers, Joshua 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 complains. 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. Beckman --------------------------------------------------------------------------- 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> https://puck.nether.net/mailman/listinfo/voiceops
On Mon, Apr 29, 2013 at 12:56 PM, Joshua Goldbard <j at 2600hz.com> wrote:
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?
There are two things our company would like that are relevant to this. An on-demand test from multiple carriers for one DID, and routine (daily? hourly?) testing of multiple DIDs from a single carrier (that is different from the one the DID is on). The latter would have to be cheap of course so we could do that a lot. The multi-carrier test at $1 would be fine with us, we'd use that when there are customer complaints. -- Carlos Alvarez TelEvolve 602-889-3003
Arptel makes a a great product that does this with their own network of probes around the world. I think they currently have support for 150 or so countries and multiple carriers. The nice part is you can use your own carriers to test to pre-existing DID's worldwide over your OWN carriers. On Apr 29, 2013, at 4:01 PM, Carlos Alvarez <carlos at televolve.com> wrote:
On Mon, Apr 29, 2013 at 12:56 PM, Joshua Goldbard <j at 2600hz.com> wrote:
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?
There are two things our company would like that are relevant to this. An on-demand test from multiple carriers for one DID, and routine (daily? hourly?) testing of multiple DIDs from a single carrier (that is different from the one the DID is on). The latter would have to be cheap of course so we could do that a lot. The multi-carrier test at $1 would be fine with us, we'd use that when there are customer complaints.
-- Carlos Alvarez TelEvolve 602-889-3003 _______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops
Sounds interesting. Pricing isn't on the site so it must be outrageous. If anyone else looks into it, I'd love to hear what you find out. On Mon, Apr 29, 2013 at 1:25 PM, Colin Brown <zavoid at gmail.com> wrote:
Arptel makes a a great product that does this with their own network of probes around the world. I think they currently have support for 150 or so countries and multiple carriers. The nice part is you can use your own carriers to test to pre-existing DID's worldwide over your OWN carriers.
On Apr 29, 2013, at 4:01 PM, Carlos Alvarez <carlos at televolve.com> wrote:
On Mon, Apr 29, 2013 at 12:56 PM, Joshua Goldbard <j at 2600hz.com> wrote:
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?
There are two things our company would like that are relevant to this. An on-demand test from multiple carriers for one DID, and routine (daily? hourly?) testing of multiple DIDs from a single carrier (that is different from the one the DID is on). The latter would have to be cheap of course so we could do that a lot. The multi-carrier test at $1 would be fine with us, we'd use that when there are customer complaints.
-- Carlos Alvarez TelEvolve 602-889-3003 _______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops
-- Carlos Alvarez TelEvolve 602-889-3003
What if the reported number rings to a live user? Need to be careful not to drive someone's mother or #1 customer crazy with tons of test calls, as that will likely generate a support call to the terminating carrier. The calling lines should also have valid ANI and CNAM to not make these look like telemarketer or junk calls, and any user that receives the call(s) should have an easy means to "opt out" of further tests. Otherwise I think it's a really good idea. As a carrier, I'd also like to be able to see trends regarding what tests are failing (such as if the system sees that more than X calls to Carrier Y in a given state/LATA/RC failed in a given time), and perhaps something to keep from multiple users testing the same called TN over and over. Lastly, I'd want to get a report/notification if someone tested one of my NPAC assigned TNs (or perhaps subscribed via a portal) and got a failure, especially across multiple carriers. -Scott From: VoiceOps [mailto:voiceops-bounces at voiceops.org] On Behalf Of Joshua Goldbard Sent: Monday, April 29, 2013 3:56 PM To: Peter Beckman Cc: VoiceOps Subject: Re: [VoiceOps] Testing DIDs from multiple providers 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? Cheers, Joshua Joshua Goldbard VP of Marketing, 2600hz 116 Natoma Street, Floor 2 San Francisco, CA, 94104 415.886.7923 | j at 2600hz.com On Apr 29, 2013, at 12:33 PM, Peter Beckman <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 complains. 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. Beckman --------------------------------------------------------------------------- Peter Beckman Internet Guy beckman at angryox.com http://www.angryox.com/ --------------------------------------------------------------------------- _______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops
Definitely an interesting idea with value. Would obviously depend on cost, of course, but I could see us using such a service. Another twist, but similar to Carlos's notion of doing routine testing, would be to place a periodic call to a known number (or numbers) on your network over a defined list of carriers and report back the failures. Maybe have it detect specific DTMF? For example, set up a mailbox with a greeting that plays ##00**. The subscriber would define a list of carriers (say, for example, 4) and have the service dial the mailbox once over each carrier, at the defined interval, and then listen for the expected digits. Maybe report MOS as well? If one were to create such a service, I would see it being rated on a per call basis. For example: Interval = x (in seconds) Number of Carriers = y Cost per call = z Calls per day = C = ((86400 / x) * y) Usage cost = (C * z) To further illustrate: x = 300 (every 5 minutes) y = 4 z = $0.05 C = ((86400 / 300) * 4) = 1152 Usage cost = 1152 * 0.05 = $57.60 Not sure what z would need to be to make it worth someone's time to create such a product. You'd need to be pretty well connected to be able to offer this ubiquitously. On Mon, Apr 29, 2013 at 6:32 PM, Scott Berkman <scott at sberkman.net> wrote:
What if the reported number rings to a live user? Need to be careful not to drive someone?s mother or #1 customer crazy with tons of test calls, as that will likely generate a support call to the terminating carrier.****
** **
The calling lines should also have valid ANI and CNAM to not make these look like telemarketer or junk calls, and any user that receives the call(s) should have an easy means to ?opt out? of further tests.****
** **
Otherwise I think it?s a really good idea.****
** **
As a carrier, I?d also like to be able to see trends regarding what tests are failing (such as if the system sees that more than X calls to Carrier Y in a given state/LATA/RC failed in a given time), and perhaps something to keep from multiple users testing the same called TN over and over.****
** **
Lastly, I?d want to get a report/notification if someone tested one of my NPAC assigned TNs (or perhaps subscribed via a portal) and got a failure, especially across multiple carriers.****
** **
-Scott****
** **
*From:* VoiceOps [mailto:voiceops-bounces at voiceops.org] *On Behalf Of *Joshua Goldbard *Sent:* Monday, April 29, 2013 3:56 PM *To:* Peter Beckman *Cc:* VoiceOps *Subject:* Re: [VoiceOps] Testing DIDs from multiple providers****
** **
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?****
** **
Cheers,****
Joshua****
** **
Joshua Goldbard****
VP of Marketing, 2600hz****
** **
116 Natoma Street, Floor 2****
San Francisco, CA, 94104****
415.886.7923 | j at 2600hz.com****
** **
On Apr 29, 2013, at 12:33 PM, Peter Beckman <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 complains.
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.
Beckman --------------------------------------------------------------------------- Peter Beckman Internet Guy beckman at angryox.com http://www.angryox.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
This is an ironic discussion. We are just about to release such a tool. It's free via 100% SIP so you can test your own carriers (at least we're going to try to keep it free as long as possible) and $ for a couple of features that took us a lot of time to build and/or require PSTN access. Stay tuned. We did the exact math, and tests, listed below, and then some. - Darren From: PE <peeip989 at gmail.com<mailto:peeip989 at gmail.com>> Date: Thursday, May 2, 2013 10:43 AM To: Joshua Goldbard <j at 2600hz.com<mailto:j at 2600hz.com>>, "VoiceOps at voiceops.org<mailto:VoiceOps at voiceops.org>" <VoiceOps at voiceops.org<mailto:VoiceOps at voiceops.org>> Subject: Re: [VoiceOps] Testing DIDs from multiple providers Definitely an interesting idea with value. Would obviously depend on cost, of course, but I could see us using such a service. Another twist, but similar to Carlos's notion of doing routine testing, would be to place a periodic call to a known number (or numbers) on your network over a defined list of carriers and report back the failures. Maybe have it detect specific DTMF? For example, set up a mailbox with a greeting that plays ##00**. The subscriber would define a list of carriers (say, for example, 4) and have the service dial the mailbox once over each carrier, at the defined interval, and then listen for the expected digits. Maybe report MOS as well? If one were to create such a service, I would see it being rated on a per call basis. For example: Interval = x (in seconds) Number of Carriers = y Cost per call = z Calls per day = C = ((86400 / x) * y) Usage cost = (C * z) To further illustrate: x = 300 (every 5 minutes) y = 4 z = $0.05 C = ((86400 / 300) * 4) = 1152 Usage cost = 1152 * 0.05 = $57.60 Not sure what z would need to be to make it worth someone's time to create such a product. You'd need to be pretty well connected to be able to offer this ubiquitously. On Mon, Apr 29, 2013 at 6:32 PM, Scott Berkman <scott at sberkman.net<mailto:scott at sberkman.net>> wrote: What if the reported number rings to a live user? Need to be careful not to drive someone?s mother or #1 customer crazy with tons of test calls, as that will likely generate a support call to the terminating carrier. The calling lines should also have valid ANI and CNAM to not make these look like telemarketer or junk calls, and any user that receives the call(s) should have an easy means to ?opt out? of further tests. Otherwise I think it?s a really good idea. As a carrier, I?d also like to be able to see trends regarding what tests are failing (such as if the system sees that more than X calls to Carrier Y in a given state/LATA/RC failed in a given time), and perhaps something to keep from multiple users testing the same called TN over and over. Lastly, I?d want to get a report/notification if someone tested one of my NPAC assigned TNs (or perhaps subscribed via a portal) and got a failure, especially across multiple carriers. -Scott From: VoiceOps [mailto:voiceops-bounces at voiceops.org<mailto:voiceops-bounces at voiceops.org>] On Behalf Of Joshua Goldbard Sent: Monday, April 29, 2013 3:56 PM To: Peter Beckman Cc: VoiceOps Subject: Re: [VoiceOps] Testing DIDs from multiple providers 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? Cheers, Joshua Joshua Goldbard VP of Marketing, 2600hz 116 Natoma Street, Floor 2 San Francisco, CA, 94104 415.886.7923<tel: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 complains. 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. Beckman --------------------------------------------------------------------------- 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> https://puck.nether.net/mailman/listinfo/voiceops _______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org<mailto:VoiceOps at voiceops.org> https://puck.nether.net/mailman/listinfo/voiceops
participants (7)
-
beckman＠angryox.com -
carlos＠televolve.com -
d＠d-man.org -
j＠2600hz.com -
peeip989＠gmail.com -
scott＠sberkman.net -
zavoid＠gmail.com