The "call duration" is a "per call" statistic, while "sequential",
"concurrent", "cpm" and "total" are "interval-based" statistics --
indeed, once they trigger, subsequent calls have a good chance of also
being rejected (e.g. unlike "total" and "sequential", which are only
reset when a new interval starts, if you wait a bit, the "cpm" will cool
down and you will be able to safely dial again).
Cheers,
Liviu Chircu
OpenSIPS Developer
http://www.opensips-solutions.com
On 09.06.2018 15:51, Denis via Users wrote:
Liviu,
I expect that ones the module detects fraud, it should return -2 on
subsequent calls. As it does to "total calls" and "subsequent calls"
respectively.
In my example, the second call was successful (return 1) , although,
as i expected, it should be fail (return -2)
Thank you
--
С уважением, Денис.
Best regards, Denis
09.06.2018, 15:11, "Liviu Chircu" <[email protected]>:
Hi Denis,
If these are your tests:
1. 11111111 22222222 101 06.06.2018 15:34:54
2. 11111111 22222222 0 06.06.2018 15:38:21
Then the 1st one should return -2 ("call duration" critical threshold
hit, since 101 sec > 60 sec), and the second one should return 1
(success, no thresholds have been hit yet).
This seems to be exactly how it behaved in your case. Did I
misunderstand your test? If not, how exactly are you expecting it to
work?
Best regards,
Liviu Chircu
OpenSIPS Developer
http://www.opensips-solutions.com <http://www.opensips-solutions.com/>
On 09.06.2018 11:32, Denis via Users wrote:
Hello!
Liviu, can i be sure, that you will analyze my question?
_______________________________________________
Users mailing list
[email protected] <mailto:[email protected]>
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
