Hi Denis,
It is difficult for me to assess your intervals, and triggering reasons.
For example, your sheet starts at 07:08 AM, but the counter accumulation
is reset way back, at 00:00.
Please provide some actual fraud event logs, with a log such as below,
so we can blame the sequential calls
Hi Denis,
Did you try to print the ruri port $rp before and after changes ?. is there any
function call that could cause the destination port to be change?
On Tuesday, April 24, 2018, 2:26:13 PM GMT+5:30, Denis via Users
wrote:
Hello! version: opensips 2.2.6 (x86_64/linux)flags: STAT
Hello Liviu! "Yes, the "sequential calls" holds the size of the last batch of callssent to the same number. For example, if a user were to dial 44 and 45prefixes in a round-robin manner, his "sequential calls" value wouldnever exceed 1." Here you can find acc from one of the client (from the beginn
Hello! version: opensips 2.2.6 (x86_64/linux)flags: STATS: On, DISABLE_NAGLE, USE_MCAST, SHM_MMAP, PKG_MALLOC, QM_MALLOC, DBG_MALLOC, FAST_LOCK-ADAPTIVE_WAITADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144, MAX_LISTEN 16, MAX_URI_SIZE 1024, BUF_SIZE 65535poll method support: poll, epoll_lt, ep
