[Spce-user] Suddenly many SIP-Accounts are "busy" (Concurrent max calls exceeded)

[Walter Klomp]

Hi Thomas. Indeed this is a redis issue which you have to flush. But check
if proxy is crashing because that will also wreak havoc with the counters.
If for instance I make a change in the config which results in restarting
of kamailio proxy I have to reset the redis database as well, or all
counters are off.  This may need to be fixed by the Sipwise developers.

On Thu, 22 Apr 2021 at 21:16, Matthias Hohl <matthias.hohl at telematica.at>
wrote:

>
>
> Hallo Thomas,
>
>
>
> 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'
>
>
>
> Solution:
>
> # redis-cli -n 3 FLUSHDB
>
>
>
>
>
> Or try this:
>
> # ngcp-dlgcnt-check
>
> 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.
>
>
>
> Lg
>
>
>
>
>
> *Von:* Thomas Georg via Spce-user <spce-user at lists.sipwise.com>
> *Gesendet:* Donnerstag, 22. April 2021 13:18
> *An:* spce-user at lists.sipwise.com
> *Betreff:* [Spce-user] Suddenly many SIP-Accounts are "busy" (Concurrent
> max calls exceeded)
>
>
>
> Hi,
>
>
>
> 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[2] exceeded[10]“ 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?
>
>
>
> Regards
>
> Thomas
>
>
> --
> Spce-user mailing list
> Spce-user at lists.sipwise.com
> http://lists.sipwise.com/mailman/listinfo/spce-user_lists.sipwise.com
>
-- 

Warmest Regards,

<https://myrepublic.com.sg/>
*Walter Klomp*
Head of Voice & Systems
MyRepublic Limited
T: +65 6816 1120
F: +65 6717 2031

MyRepublic Limited
11 Lorong 3 Toa Payoh Block B Jackson Square
#04-11/15 Singapore 319579

myrepublic.com.sg
Follow us on: Twitter <https://twitter.com/myrepublic> | Facebook
<https://facebook.com/myrepublicsg> | LinkedIn
<https://www.linkedin.com/company/myrepublic>

-- 
The contents of this email and any attachments are confidential and may 
also be privileged. You must not disseminate the contents of this email and 
any attachments without permission of the sender. If you have received this 
email by mistake, please delete all copies and inform the sender 
immediately. You may refer to our company's Privacy Policy here 
<https://myrepublic.net/sg/legal/terms-of-use-policies/privacy-policy/>.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20210422/57650a8d/attachment-0002.html>