Send VoiceOps mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
https://puck.nether.net/mailman/listinfo/voiceops
or, via email, send a message with subject or body 'help' to
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of VoiceOps digest..."
Today's Topics:
1. Re: Testing DIDs from multiple providers (PE)
2. Re: Testing DIDs from multiple providers (Darren Schreiber)
----------------------------------------------------------------------
Message: 1
Date: Thu, 2 May 2013 13:43:32 -0400
From: PE <[email protected]>
To: Joshua Goldbard <[email protected]>, "[email protected]"
<[email protected]>
Subject: Re: [VoiceOps] Testing DIDs from multiple providers
Message-ID:
<CAHm=sa+ynddvq3vkgo_bzpo0e8pqincogspxgcxdip62pzr...@mail.gmail.com>
Content-Type: text/plain; charset="windows-1252"
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 <[email protected]> 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:[email protected]] *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 | [email protected]****
>
> ** **
>
> On Apr 29, 2013, at 12:33 PM, Peter Beckman <[email protected]> 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
> [email protected]
> http://www.angryox.com/
> ---------------------------------------------------------------------------
> _______________________________________________
> VoiceOps mailing list
> [email protected]
> https://puck.nether.net/mailman/listinfo/voiceops****
>
> ** **
>
> _______________________________________________
> VoiceOps mailing list
> [email protected]
> https://puck.nether.net/mailman/listinfo/voiceops
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://puck.nether.net/pipermail/voiceops/attachments/20130502/4df03115/attachment-0001.html>
------------------------------
Message: 2
Date: Thu, 2 May 2013 10:59:32 -0700
From: Darren Schreiber <[email protected]>
To: "[email protected]" <[email protected]>
Subject: Re: [VoiceOps] Testing DIDs from multiple providers
Message-ID: <cda7f781.10aebb%[email protected]>
Content-Type: text/plain; charset="windows-1252"
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 <[email protected]<mailto:[email protected]>>
Date: Thursday, May 2, 2013 10:43 AM
To: Joshua Goldbard <[email protected]<mailto:[email protected]>>,
"[email protected]<mailto:[email protected]>"
<[email protected]<mailto:[email protected]>>
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
<[email protected]<mailto:[email protected]>> 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:[email protected]<mailto:[email protected]>] 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> | [email protected]<mailto:[email protected]>
On Apr 29, 2013, at 12:33 PM, Peter Beckman
<[email protected]<mailto:[email protected]>> 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
[email protected]<mailto:[email protected]>
http://www.angryox.com/
---------------------------------------------------------------------------
_______________________________________________
VoiceOps mailing list
[email protected]<mailto:[email protected]>
https://puck.nether.net/mailman/listinfo/voiceops
_______________________________________________
VoiceOps mailing list
[email protected]<mailto:[email protected]>
https://puck.nether.net/mailman/listinfo/voiceops
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://puck.nether.net/pipermail/voiceops/attachments/20130502/da99ea99/attachment.html>
------------------------------
Subject: Digest Footer
_______________________________________________
VoiceOps mailing list
[email protected]
https://puck.nether.net/mailman/listinfo/voiceops
------------------------------
End of VoiceOps Digest, Vol 47, Issue 1
***************************************
