Hi Team
I did set origination capacity, as well as total capacity in Billing → Account…
I can see that the calls are still going over the set capacity. Setting in Dialpeer does not work either.
Please how do I go about troubleshooting this?
check your redis configuration.
OK, Thanks for your response.
Actually, Redis is running fine. And the config in the redis.conf is same as in other Yeti v1.9
So it is not clear what needs to be done on the Redis Config. Below is the config:
(can you help specify more how to go about debugging)
bind 127.0.0.1
protected-mode yes
port 6379
tcp-backlog 511
timeout 0
tcp-keepalive 300
daemonize yes
supervised no
pidfile /var/run/redis/redis-server.pid
loglevel notice
logfile /var/log/redis/redis-server.log
databases 16
save 900 1
save 300 10
save 60 10000
stop-writes-on-bgsave-error yes
rdbcompression yes
rdbchecksum yes
dbfilename dump.rdb
dir /var/lib/redis
slave-serve-stale-data yes
slave-read-only yes
repl-diskless-sync no
repl-diskless-sync-delay 5
repl-disable-tcp-nodelay no
slave-priority 100
appendonly no
appendfilename “appendonly.aof”
appendfsync everysec
no-appendfsync-on-rewrite no
auto-aof-rewrite-percentage 100
auto-aof-rewrite-min-size 64mb
aof-load-truncated yes
lua-time-limit 5000
slowlog-log-slower-than 10000
slowlog-max-len 128
latency-monitor-threshold 0
notify-keyspace-events “”
hash-max-ziplist-entries 512
hash-max-ziplist-value 64
list-max-ziplist-size -2
list-compress-depth 0
set-max-intset-entries 512
zset-max-ziplist-entries 128
zset-max-ziplist-value 64
hll-sparse-max-bytes 3000
activerehashing yes
client-output-buffer-limit normal 0 0 0
client-output-buffer-limit slave 256mb 64mb 60
client-output-buffer-limit pubsub 32mb 8mb 60
hz 10
aof-rewrite-incremental-fsync yes
@dmitry.s @EAfang
I seem to have encountered this problem. I have checked and tried limiting by account and Customer AUTH but I cannot limit the capacity. How were you able to resolve this?
I am using Yeti Admin ver: 1.9.9. Routing ver 20191018180427. CDR ver 20190707214813.
check if your redis running. If you sure everything is configured accoding to documentation - provide debug log for call that should be rejected by capacity limit. Also version 1.9 is very old, consider to upgrade your system
@dmitry.s Thank you for the prompt response.
How do I check that redis is configured ok. here is the result of the test as per the installation documentation
root@s0:~# redis-cli
127.0.0.1:6379>
127.0.0.1:6379> ping
PONG
127.0.0.1:6379> quit
root@s0:~#
When you say debug the call, do you mean the pcap file ?
I mean sems log with loglevel 3