Does anyone know of a SIP product that will block outbound calls to the PSTN from a PBX, based on a database match? It would need to be loaded with the national registry, as well as allow the end user to load numbers themselves. This could reside on a local server, or out in the cloud. Not quite a predictive dialer, since the end user will dial the number from the handset themselves, and receive an appropriate recording notifying them if the number dialed matched a "blocked" number. Thanks for any help -Mark S
A number of switches will allow you to do database lookups and take action based on the result. One open source project is Freeswitch (www.freeswitch.org) and it can do this. On Friday 02 December 2011 18:02:44 Stappenbeck, Mark wrote:
Does anyone know of a SIP product that will block outbound calls to the PSTN from a PBX, based on a database match? It would need to be loaded with the national registry, as well as allow the end user to load numbers themselves. This could reside on a local server, or out in the cloud. Not quite a predictive dialer, since the end user will dial the number from the handset themselves, and receive an appropriate recording notifying them if the number dialed matched a "blocked" number.
Thanks for any help -Mark S
DNC.com has a good HTTP API that allows real-time scrubbing. You coule probably modify an AsteriskNOW installation (or similar) to call an AGI script prior to outbound dialing. The AGI script could invoke the VERY simple HTTP call and analyze the result. This would, of course, require a full national FTC Org ID/SAN to be useful for calling anywhere in the US. From: voiceops-bounces at voiceops.org [mailto:voiceops-bounces at voiceops.org] On Behalf Of Stappenbeck, Mark Sent: Friday, December 02, 2011 4:03 PM To: voiceops at voiceops.org Subject: [VoiceOps] Do Not Call list Does anyone know of a SIP product that will block outbound calls to the PSTN from a PBX, based on a database match? It would need to be loaded with the national registry, as well as allow the end user to load numbers themselves. This could reside on a local server, or out in the cloud. Not quite a predictive dialer, since the end user will dial the number from the handset themselves, and receive an appropriate recording notifying them if the number dialed matched a "blocked" number. Thanks for any help -Mark S
On Fri, Dec 2, 2011 at 5:10 PM, Geoffrey Mina <gmina at connectfirst.com> wrote:
DNC.com has a good HTTP API that allows real-time scrubbing.? You coule probably modify an AsteriskNOW installation (or similar) to call an AGI script prior to outbound dialing.? The AGI script could invoke the VERY simple HTTP call and analyze the result.
Since you're making a call to an outside service, then you'll have a question to deal with... what do you want to happen if the remote server can't answer your query, your internet connectivity to the remote server has an issue, or the remote service is taking way too long to respond. Failed query, then allow? Failed query, then block? Failed query, then retry forever? If the database server is temporarily unavailable, then you hace to pick how you want to fail. Careful about the risk of potentially making an outgoing 911 call sit and wait 10 minutes on a query to a remote database, to see if the call will be allowed, b/c database happens to be experiencing a speed issue at the time. -- -JH
On 12/2/11 3:26 PM, Jimmy Hess wrote:
Since you're making a call to an outside service, then you'll have a question to deal with... what do you want to happen if the remote server can't answer your query, your internet connectivity to the remote server has an issue, or the remote service is taking way too long to respond.
Failed query, then allow? Failed query, then block? Failed query, then retry forever? If the database server is temporarily unavailable, then you have to pick how you want to fail.
Careful about the risk of potentially making an outgoing 911 call sit and wait 10 minutes on a query to a remote database, to see if the call will be allowed, b/c database happens to be experiencing a speed issue at the time.
Yeah, whole different scenario with a human agent vs. an autodialer. Presumably these are agents with a SIP trunk to a telemarketing system and not generic business users. With the Sansay you can deploy a blocking server based on the resource, so 911 and other service codes would not use it, only NPA-NXX-XXXX. If the trunk is used only for outbound telespam^H^H^H^Hmarketing, then logically you would probably want to reject on unreachable. Sansay is pretty flexible in terms of ability to use multiple blocking servers. -- Jay Hennigan - CCIE #7880 - Network Engineering - jay at impulse.net Impulse Internet Service - http://www.impulse.net/ Your local telephone and internet company - 805 884-6323 - WB6RDV
One route you could take is using an ENUM or SIP redirect server to query the destination number against a database and return a route that blocks the call. There are a quire a few directions could go on the ENUM side to do this. Something along the lines of NetNumber is one option, otherwise you can do something in house to store and query the database. It's possible to put together a fairly cheap and reliable database backed ENUM platform with something as simple as a pair of servers running a database backed DNS (PowerDNS is an option) and replicated MySQL/PostgreSQL. With a decent amount of RAM you could store the entire database in memory cache for quick response times. -- Jason Nesheim ----- Original Message ----- From: "Jay Hennigan" <jay at west.net> To: voiceops at voiceops.org Sent: Friday, December 2, 2011 3:48:53 PM Subject: Re: [VoiceOps] Do Not Call list On 12/2/11 3:26 PM, Jimmy Hess wrote:
Since you're making a call to an outside service, then you'll have a question to deal with... what do you want to happen if the remote server can't answer your query, your internet connectivity to the remote server has an issue, or the remote service is taking way too long to respond.
Failed query, then allow? Failed query, then block? Failed query, then retry forever? If the database server is temporarily unavailable, then you have to pick how you want to fail.
Careful about the risk of potentially making an outgoing 911 call sit and wait 10 minutes on a query to a remote database, to see if the call will be allowed, b/c database happens to be experiencing a speed issue at the time.
Yeah, whole different scenario with a human agent vs. an autodialer. Presumably these are agents with a SIP trunk to a telemarketing system and not generic business users. With the Sansay you can deploy a blocking server based on the resource, so 911 and other service codes would not use it, only NPA-NXX-XXXX. If the trunk is used only for outbound telespam^H^H^H^Hmarketing, then logically you would probably want to reject on unreachable. Sansay is pretty flexible in terms of ability to use multiple blocking servers. -- Jay Hennigan - CCIE #7880 - Network Engineering - jay at impulse.net Impulse Internet Service - http://www.impulse.net/ Your local telephone and internet company - 805 884-6323 - WB6RDV _______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops
Thank you everyone for the replies. I did find what I was looking for. A sip invite from the PBX to the ?device? generates a scrub of the DNC database, no match sends a refer back to us (the PBX) and is sent outbound to PSTN. A match connects to audio notifying the agent that dialed the number that it was a DNC and ?please hang up and dial another number?. From: voiceops-bounces at voiceops.org [mailto:voiceops-bounces at voiceops.org] On Behalf Of Jason L. Nesheim Sent: Friday, December 02, 2011 8:02 PM To: Jay Hennigan Cc: voiceops at voiceops.org Subject: Re: [VoiceOps] Do Not Call list One route you could take is using an ENUM or SIP redirect server to query the destination number against a database and return a route that blocks the call. There are a quire a few directions could go on the ENUM side to do this. Something along the lines of NetNumber is one option, otherwise you can do something in house to store and query the database. It's possible to put together a fairly cheap and reliable database backed ENUM platform with something as simple as a pair of servers running a database backed DNS (PowerDNS is an option) and replicated MySQL/PostgreSQL. With a decent amount of RAM you could store the entire database in memory cache for quick response times. -- Jason Nesheim ----- Original Message ----- From: "Jay Hennigan" <jay at west.net> To: voiceops at voiceops.org Sent: Friday, December 2, 2011 3:48:53 PM Subject: Re: [VoiceOps] Do Not Call list On 12/2/11 3:26 PM, Jimmy Hess wrote:
Since you're making a call to an outside service, then you'll have a question to deal with... what do you want to happen if the remote server can't answer your query, your internet connectivity to the remote server has an issue, or the remote service is taking way too long to respond.
Failed query, then allow? Failed query, then block? Failed query, then retry forever? If the database server is temporarily unavailable, then you have to pick how you want to fail.
Careful about the risk of potentially making an outgoing 911 call sit and wait 10 minutes on a query to a remote database, to see if the call will be allowed, b/c database happens to be experiencing a speed issue at the time.
Yeah, whole different scenario with a human agent vs. an autodialer. Presumably these are agents with a SIP trunk to a telemarketing system and not generic business users. With the Sansay you can deploy a blocking server based on the resource, so 911 and other service codes would not use it, only NPA-NXX-XXXX. If the trunk is used only for outbound telespam^H^H^H^Hmarketing, then logically you would probably want to reject on unreachable. Sansay is pretty flexible in terms of ability to use multiple blocking servers. -- Jay Hennigan - CCIE #7880 - Network Engineering - jay at impulse.net Impulse Internet Service - http://www.impulse.net/ Your local telephone and internet company - 805 884-6323 - WB6RDV _______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops
On 12/2/11 3:02 PM, Stappenbeck, Mark wrote:
Does anyone know of a SIP product that will block outbound calls to the PSTN from a PBX, based on a database match?
It would need to be loaded with the national registry, as well as allow the end user to load numbers themselves.
This could reside on a local server, or out in the cloud.
The Sansay VSXi has this capability. We haven't deployed that feature as we don't have customers in that business. We're happy with Sansay support and product in all other respects so I presume it should work as intended.
Not quite a predictive dialer, since the end user will dial the number from the handset themselves, and receive an appropriate recording notifying them if the number dialed matched a ?blocked? number.
Should work just fine. I don't know the default call handling if it matches a blocked number. I think that by default it returns a SIP "Forbidden" response of some type as opposed to an audible intercept but it may be tweakable to an alternate route that goes to a recording. -- Jay Hennigan - CCIE #7880 - Network Engineering - jay at impulse.net Impulse Internet Service - http://www.impulse.net/ Your local telephone and internet company - 805 884-6323 - WB6RDV
participants (6)
-
gmina＠connectfirst.com -
jay＠west.net -
jnesheim＠cytek.biz -
justlikeef＠gmail.com -
MStappenbeck＠allworx.com -
mysidia＠gmail.com