[Spce-user] Feature Request for better fraud protection

Jon Bonilla (Manwe) manwe at sipdoc.net
Wed Jul 19 11:29:46 EDT 2017


El Wed, 19 Jul 2017 11:31:30 +0200 (CEST)
Matthias Hohl <matthias.hohl at telematica.at> escribió:

> Hello,
> 
>  
> 
> if a call is still active and the fraud prevention locks the subscriber the
> current active call will not be canceled.
> 
> So the subscriber fraud script locked outgoing calls, so you can’t initiate
> a new call cause of exceeding credit balance threshold but all currently
> active calls still produce more costs.
> 
>  
> 
> I got the problem this night with a subscriber:
> 
> The fraud script normally runs in 5 minute intervall and the subscriber got
> locked at 0:40 but a fraud call with duration of 2 ½ hours started at 0:39
> and was not beeing canceled from the fraud script, and produces a lot of
> costs.
> 
>  
> 
> Is there a way to implement a auto cancelation of all active outgoing calls
> in case of fraud limit reached?
> 
> It will be a good fraud prevention feature.
> 
>  

The only place you could do that is in sems. Using the sems xmlrpc interface
you can list and teardown active calls. You could modify a bit the fraud
scripts to accomplish that.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 833 bytes
Desc: Firma digital OpenPGP
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20170719/8a3c34f5/attachment-0001.sig>


More information about the Spce-user mailing list