[OpenSIPS-Users] Opensips 2.5 and fraud module

Liviu Chircu liviu at opensips.org
Thu Jun 14 07:13:01 EDT 2018


The more I think about it, the more "call duration" makes sense as it is 
now.  If you want to force a shorter dialog lifetime, there is no need 
to duplicate this logic into check_fraud() -- you can already achieve it 
by setting custom $DLG_timeout values.

Ideally, we should be able to one or more stats [1].  And complete 
suggestions on how we can improve the existing ones are welcome.

Best regards,

[1]: https://github.com/OpenSIPS/opensips/issues/890

Liviu Chircu
OpenSIPS Developer
http://www.opensips-solutions.com

On 14.06.2018 13:20, Denis via Users wrote:
> As for me, it is not solve the problem, if we will still talking about 
> 'per call' criteria.
> For example. I set 10 "total calls" with 600 seconds of the "call 
> duration". Your idea will give us 100 minute of successful calls. Not 
> such many for minutes, but may be a lot in money.
> But, if it is difficult to make control of the "call duration" per 
> "interval", then "it is better, then nothing". Your idea decrease (in 
> combination of the "total calls") a number of successful minutes than 
> we can get now.
> But this feature should be switched off, if needed.
> -- 
> С уважением, Денис.
> Best regards, Denis
> 13.06.2018, 18:40, "Liviu Chircu" <liviu at opensips.org>:
>>
>> I agree - it seems like a "good in theory, bad in practice" kind of
>> feature.  So let's see how we can make it better: would it make more
>> sense to add a forced dialog lifetime equal to the critical threshold of
>> the "call duration" setting upon calling check_fraud() (which, by the
>> way, will also create the dialog if it's not there), while keeping the
>> event alerts just like they are now?
>>
>> Liviu Chircu
>> OpenSIPS Developer
>> http://www.opensips-solutions.com <http://www.opensips-solutions.com/>
>>
>> On 12.06.2018 13:12, Денис Путято via Users wrote:
>>
>>      Hmm.....
>>      And what is the purpose of control "per call"?
>>      As i understand it triggers AFTER calls finishing. What can we do in
>>      such situation?
>>      Just send email to, for example, support, that "potential fraud"
>>     call
>>      has been finished?
>>
>>
>>
>> _______________________________________________
>> Users mailing list
>> Users at lists.opensips.org <mailto:Users at lists.opensips.org>
>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>
>
>
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20180614/28ed4b20/attachment.html>


More information about the Users mailing list