[VoiceOps] Do Not Call list

Jay Hennigan jay at west.net
Fri Dec 2 18:48:53 EST 2011


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


More information about the VoiceOps mailing list