<div dir="ltr">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? <div>
<br></div><div style>If one were to create such a service, I would see it being rated on a per call basis. For example:</div><div style><br></div><div style>Interval = x (in seconds)</div><div style>Number of Carriers = y</div>
<div style>Cost per call = z</div><div style><br></div><div style>Calls per day = C = ((86400 / x) * y)</div><div style><br></div><div style>Usage cost = (C * z)</div><div style><br></div><div style><br></div><div style><br>
</div><div style>To further illustrate:</div><div style>x = 300 (every 5 minutes)</div><div style>y = 4</div><div style>z = $0.05</div><div style><br></div><div style>C = ((86400 / 300) * 4) = 1152</div><div style>Usage cost = 1152 * 0.05 = $57.60</div>
<div style><br></div><div style><br></div><div style>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. </div>
<div style><br></div><div style><br></div><div style> </div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Mon, Apr 29, 2013 at 6:32 PM, Scott Berkman <span dir="ltr"><<a href="mailto:scott@sberkman.net" target="_blank">scott@sberkman.net</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div lang="EN-US" link="blue" vlink="purple"><div><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">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.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">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.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">Otherwise I think it’s a really good idea.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">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.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">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.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">-Scott<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></p><div><div style="border:none;border-top:solid #b5c4df 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> VoiceOps [mailto:<a href="mailto:voiceops-bounces@voiceops.org" target="_blank">voiceops-bounces@voiceops.org</a>] <b>On Behalf Of </b>Joshua Goldbard<br>
<b>Sent:</b> Monday, April 29, 2013 3:56 PM<br><b>To:</b> Peter Beckman<br><b>Cc:</b> VoiceOps<br><b>Subject:</b> Re: [VoiceOps] Testing DIDs from multiple providers<u></u><u></u></span></p></div></div><div><div class="h5">
<p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal">Is this something the community would be willing to pay for? <u></u><u></u></p><div><p class="MsoNormal"><u></u> <u></u></p></div><div><p class="MsoNormal">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?<u></u><u></u></p>
<div><p class="MsoNormal"><u></u> <u></u></p></div><div><p class="MsoNormal">Cheers,<u></u><u></u></p></div><div><p class="MsoNormal">Joshua<u></u><u></u></p></div><div><p class="MsoNormal"><u></u> <u></u></p><div><div><p class="MsoNormal">
<span style="font-size:13.5pt;font-family:"Helvetica","sans-serif"">Joshua Goldbard<u></u><u></u></span></p></div><div><p class="MsoNormal"><span style="font-size:13.5pt;font-family:"Helvetica","sans-serif"">VP of Marketing, 2600hz<u></u><u></u></span></p>
</div><div><p class="MsoNormal"><span style="font-size:13.5pt;font-family:"Helvetica","sans-serif""><u></u> <u></u></span></p></div><div><p class="MsoNormal"><span style="font-size:13.5pt;font-family:"Helvetica","sans-serif"">116 Natoma Street, Floor 2<u></u><u></u></span></p>
</div><div><p class="MsoNormal"><span style="font-size:13.5pt;font-family:"Helvetica","sans-serif"">San Francisco, CA, 94104<u></u><u></u></span></p></div><div><p class="MsoNormal"><span style="font-size:13.5pt;font-family:"Helvetica","sans-serif""><a href="tel:415.886.7923" value="+14158867923" target="_blank">415.886.7923</a> | <a href="mailto:j@2600hz.com" target="_blank">j@2600hz.com</a><u></u><u></u></span></p>
</div></div><p class="MsoNormal"><u></u> <u></u></p><div><div><p class="MsoNormal">On Apr 29, 2013, at 12:33 PM, Peter Beckman <<a href="mailto:beckman@angryox.com" target="_blank">beckman@angryox.com</a>> wrote:<u></u><u></u></p>
</div><p class="MsoNormal"><br><br><u></u><u></u></p><p class="MsoNormal">As a VoIP provider of numbers, we occasionally get complaints that a number<br>isn't working, or isn't working for specific callers. The trouble I'm<br>
having is figuring out how to automate a test for this.<br><br>I've got an automated test now that makes a test call from a number known<br>to always ring busy. When my switch sees that CallerID, it plays a busy<br>signal and records the call in our database so I can have a record of a<br>
successful test. When the number really is broken, that test consistently<br>fails and I have good data with which I can bug the carrier.<br><br>Most VoIP termination providers use Verizon or L3 or another major<br>provider. Often my DIDs are from them, so the calls always succeed within<br>
the network. Often Verizon and L3 are both working when the customer<br>complains.<br><br>The issue is that sometimes its a cell carrier like Sprint that doesn't<br>route the number correctly, or even Comcast Business, though a Comcast home<br>
phone successfully called the DID.<br><br>Is there any company out there that provides an API that allows me to<br>submit a request for a test of a number and will try that DID on a bunch of<br>carriers and report back? I suppose if you aren't the endpoint for that<br>
DID, might be hard to automate, but I have ideas.<br><br>Beckman<br>---------------------------------------------------------------------------<br>Peter Beckman Internet Guy<br>
<a href="mailto:beckman@angryox.com" target="_blank">beckman@angryox.com</a> <a href="http://www.angryox.com/" target="_blank">http://www.angryox.com/</a><br>---------------------------------------------------------------------------<br>
_______________________________________________<br>VoiceOps mailing list<br><a href="mailto:VoiceOps@voiceops.org" target="_blank">VoiceOps@voiceops.org</a><br><a href="https://puck.nether.net/mailman/listinfo/voiceops" target="_blank">https://puck.nether.net/mailman/listinfo/voiceops</a><u></u><u></u></p>
</div><p class="MsoNormal"><u></u> <u></u></p></div></div></div></div></div></div><br>_______________________________________________<br>
VoiceOps mailing list<br>
<a href="mailto:VoiceOps@voiceops.org">VoiceOps@voiceops.org</a><br>
<a href="https://puck.nether.net/mailman/listinfo/voiceops" target="_blank">https://puck.nether.net/mailman/listinfo/voiceops</a><br>
<br></blockquote></div><br></div>