[Spce-user] Suddenly many SIP-Accounts are "busy" (Concurrent max calls exceeded)
matthias.hohl at telematica.at
Thu Apr 22 09:15:13 EDT 2021
I just know this problem in correlation to redis counter.
After flush the redisdb counter, it was fine.
I am not sure if a system reboot also clear the redis counter too, but maybe this helps you a bit:
Searching for the problem:
# cat /var/log/ngcp/kamailio-proxy.log | grep -i 'concurrent'
# redis-cli -n 3 FLUSHDB
Or try this:
you will see the list of hanging calls that should be clean
# ngcp-dlgcnt-check -r
You will remove those calls from dialog list and decrease the counters properly.
Von: Thomas Georg via Spce-user <spce-user at lists.sipwise.com <mailto:spce-user at lists.sipwise.com> >
Gesendet: Donnerstag, 22. April 2021 13:18
An: spce-user at lists.sipwise.com <mailto:spce-user at lists.sipwise.com>
Betreff: [Spce-user] Suddenly many SIP-Accounts are "busy" (Concurrent max calls exceeded)
since 3 hours our customers complain about busy lines (in and outgoing).
This happens to customers who have „max concurrent calls“ set.
I tried with one customer which definitively did no call during this test and I always got the message „Concurrent max calls exceeded“ until i raised the limit to 10 or above then a call was possible.
We recognized that at exactly at 11:00 the answer seizure rate felt from 62% to 55%. Since then we also get complaints.
I restarted the system but the problem is still there.
We currently set all complaining customers to more concurrent calls, but this should be only a workaround.
What can I do to debug this? Is there a possibility to show the „real“ current calls per user/total?
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Spce-user