[Spce-user] Concurrent max calls exceeded for callee

Sun Apr 17 16:32:09 EDT 2016

Hello,

today i found out this:

Apr 17 10:21:44 spce (local7.err) proxy[17506]: ERROR: db_mysql [km_dbase.c:124]: db_mysql_submit_query(): driver error on query: Lost connection to MySQL server during query (2013)

Apr 17 10:21:44 spce (local7.notice) proxy[17506]: NOTICE: <core> [db_query.c:60]: db_do_submit_query(): alert - query execution too long [563 ms] for [delete from `dialog` where `hash_entry`=3905 AND `]

Apr 17 10:21:44 spce (local7.err) proxy[17506]: ERROR: <core> [db_query.c:292]: db_do_delete(): error while submitting query

Apr 17 10:21:44 spce (local7.err) proxy[17506]: ERROR: dialog [dlg_db_handler.c:620]: remove_dialog_from_db(): failed to delete database information

Apr 17 10:26:06 spce (local7.err) proxy[17506]: ERROR: db_mysql [km_dbase.c:124]: db_mysql_submit_query(): driver error on query: Lost connection to MySQL server during query (2013)

Apr 17 10:26:06 spce (local7.notice) proxy[17506]: NOTICE: <core> [db_query.c:60]: db_do_submit_query(): alert - query execution too long [562 ms] for [delete from `dialog` where `hash_entry`=226 AND `h]

Apr 17 10:26:06 spce (local7.err) proxy[17506]: ERROR: <core> [db_query.c:292]: db_do_delete(): error while submitting query

Apr 17 10:26:06 spce (local7.err) proxy[17506]: ERROR: dialog [dlg_db_handler.c:620]: remove_dialog_from_db(): failed to delete database information

Maybe this has something to do with the REDIS Counter Problem?

Von: Daniel Grotti [mailto:dgrotti at sipwise.com] 
Gesendet: Donnerstag, 7. April 2016 11:32
An: Matthias Hohl <matthias.hohl at telematica.at>; spce-user at lists.sipwise.com
Betreff: Re: AW: [Spce-user] Concurrent max calls exceeded for callee

Hi Matthias,
we are aware of that and working to fix this. This is not so easy to figure it out.
Meanwhile you don't need to restart redis, but just to fllush redis db 3 and redis db 4 with redis command FLUSHDB.
You can do it during the night.

This is not a solution, I know, if you would be able to provide some traces where the counters are not decreased, it would be really nice.

Cheers,

Daniel Grotti 
Head of Customer Support 

Sipwise GmbH  <http://www.sipwise.com> , Campus 21/Europaring F15
AT-2345 Brunn am Gebirge 

Phone:  +43(0)1 301 2032  <callto:+4313012032> 
Email:  dgrotti at sipwise.com  <mailto:dgrotti at sipwise.com> 
Website:  www.sipwise.com  <http://www.sipwise.com> 

Particulars according Austrian Companies Code paragraph 14
"Sipwise GmbH" - Europaring F15 - 2345 Brunn am Gebirge
FN:305595f, Commercial Court Vienna, ATU64002206 

On 04/07/2016 11:16 AM, Matthias Hohl wrote:

Hello,

this problem is still there.
We must restart the REDIS service to clear this problem.
Sure it helps for the moment, but for long time, this is no solution to restart REDIS every week... :/ 

With the latest version, the failure appears much less often like before, but it is still there.

Do you have any idea?

thanks

-----Ursprüngliche Nachricht-----
Von: Spce-user [mailto:spce-user-bounces at lists.sipwise.com] Im Auftrag von Matthias Hohl
Gesendet: Freitag, 12. Februar 2016 17:13
An: Daniel Grotti  <mailto:dgrotti at sipwise.com> <dgrotti at sipwise.com>; spce-user at lists.sipwise.com <mailto:spce-user at lists.sipwise.com> 
Betreff: Re: [Spce-user] Concurrent max calls exceeded for callee

Hello,

also with upgrade to 4.2.1 we still have the same problems with  Conncurent max calls exceeded for callee:

Example:
Feb 12 16:29:20 spce (local7.notice) proxy[3749]: NOTICE: <script>: Concurrent max calls exceeded for callee 'aef1bad0-ed48-4697-a55e-6ab25e723b5a' - R=sip:43137xxxxx at sip.xxx.at:5060 <mailto:R=sip:43137xxxxx at sip.xxx.at:5060>  ID=3b0717627b45827e6a9a0f7a50f5f42a at xx.170.208.xxx:5060 <mailto:ID=3b0717627b45827e6a9a0f7a50f5f42a at xx.170.208.xxx:5060>  UA='GlobalCall+T.38'
Feb 12 16:33:56 spce (local7.notice) proxy[3742]: NOTICE: <script>: Concurrent max calls exceeded for callee 'aef1bad0-ed48-4697-a55e-6ab25e723b5a' - R=sip:43137xxxxx at sip.xxx.at:5060 <mailto:R=sip:43137xxxxx at sip.xxx.at:5060>  ID=2277847967b2b40325f5720a268a9056 at xx.170.208.xxx:5060 <mailto:ID=2277847967b2b40325f5720a268a9056 at xx.170.208.xxx:5060>  UA='GlobalCall+T.38'

But there are no concurrent calls on this subscriber!!!!

After doing "redis restart" it works again without problems.

Thanks!

----- Ursprüngliche Mail -----
Von: "Matthias Hohl"  <mailto:matthias.hohl at telematica.at> <matthias.hohl at telematica.at>
An: "Daniel Grotti"  <mailto:dgrotti at sipwise.com> <dgrotti at sipwise.com>, spce-user at lists.sipwise.com <mailto:spce-user at lists.sipwise.com> 
Gesendet: Dienstag, 26. Januar 2016 12:30:17
Betreff: Re: [Spce-user] Concurrent max calls exceeded for callee

Hello,

when do you think, that you fix this issue, cause I have this problem several times a week :/ I am currently on the latest 4.1.1 version including updates from last week.

Thanks.

-----Ursprüngliche Nachricht-----
Von: Daniel Grotti [mailto:dgrotti at sipwise.com]
Gesendet: Mittwoch, 16. Dezember 2015 11:17
An: Matthias Hohl  <mailto:matthias.hohl at telematica.at> <matthias.hohl at telematica.at>; spce-user at lists.sipwise.com <mailto:spce-user at lists.sipwise.com> 
Betreff: Re: AW: [Spce-user] Concurrent max calls exceeded for callee

Hi Matthias,
We are aware of the problem on mr3.8.4 version and 4.x.
We are working on it since a while in order to fix definitely this issue.

Stay tuned.

--
Daniel Grotti
VoIP Engineer

Sipwise GmbH
Europaring F15 | 2345 Brunn am Gebirge, Austria | www.sipwise.com <http://www.sipwise.com> 

On 12/16/2015 01:13 AM, Matthias Hohl wrote:

Hello,

i have again this redis counter problem with "max calls exceeded for

callee"

for some subscribers.
It comes from time to time, that the SPCE told me, that max calls 
exceeded but nobody is calling.

After restarting redis service (/etc/init.d/redis-server restart) 
everything is working fine again, but I must restart the redis every 
few

days/week.

Is there another solution for this problem?

How could this happen, again and again on different subscribers?

Thanks for your answer!

-----Ursprüngliche Nachricht-----
Von: Spce-user [mailto:spce-user-bounces at lists.sipwise.com] Im Auftrag 
von Daniel Grotti
Gesendet: Mittwoch, 4. November 2015 10:24
An: spce-user at lists.sipwise.com <mailto:spce-user at lists.sipwise.com> 
Betreff: Re: [Spce-user] Concurrent max calls exceeded for callee

Hi,
you can reset redis counters for that user to 0.
for example:

# redis-cli -n 3 keys \*

# redis-cli -n 3 get userout:<SUBS_UUID> "2"
# redis-cli -n 3 set userout:<SUBS_UUID> 0 OK # redis-cli -n 3 get 
userout:<SUBS_UUID> "0"

--
Daniel Grotti
VoIP Engineer

Sipwise GmbH
Europaring F15 | 2345 Brunn am Gebirge, Austria | www.sipwise.com <http://www.sipwise.com> 

On 11/03/2015 10:29 AM, Matthias Hohl wrote:

Today the same problem happen again by an other subscriber. The 
subscriber has 4 lines but just one person is using the subscriber.
They place several calls this morning and called me now and told me, 
that she cant call place calls anymore cause phone told her: "all 
concurrent lines are in use, please try again later". I checked the 
server and the pbx and there are no active calls, so the limit cant 
be

exceeded.

After set the concurrent max limit to 5 or higher in subscriber 
preferences, calls works again, if i set it back to 4, the voice 
message comes again.

This happen now several times with different subscribers in different 
time intervals. It looks like this is a redis bug or what do you think?

Hope to read from you soon with some more informations.

Btw: is restarting redis-server the right solution?

/etc/init.d/redis-server stop

rm -rf /var/lib/redis/*

/etc/init.d/redis-server start

Von meinem iPhone gesendet

Am 05.10.2015 um 13:09 schrieb Matthias Hohl 
<matthias.hohl at telematica.at <mailto:matthias.hohl at telematica.at>   <mailto:matthias.hohl at telematica.at> <mailto:matthias.hohl at telematica.at>>:

I found a hint in an older posting…

I have done now the following:

/etc/init.d/redis-server stop

rm -rf /var/lib/redis/*

/etc/init.d/redis-server start

It looks that it works now again, but can you tell me, what happened 
and how this problem can be reproduced, and if this is the only 
solution for it?

Thanks.

*Von:*Spce-user [mailto:spce-user-bounces at lists.sipwise.com] *Im 
Auftrag von *Matthias Hohl
*Gesendet:* Montag, 5. Oktober 2015 10:23
*An:* spce-user at lists.sipwise.com <mailto:spce-user at lists.sipwise.com> 
 <mailto:spce-user at lists.sipwise.com> <mailto:spce-user at lists.sipwise.com>
*Betreff:* [Spce-user] Concurrent max calls exceeded for callee

Hello,

found out new problem today…

I subscriber can’t place or get calls and kamilio-proxy.log told me, 
that “Concurrent max calls exceeded for callee” and also sometimes 
“Concurrent_max calls exceeded for caller”

But the subscriber has 8 lines and no concurrent calls.

What can I check to solve this problem?

_______________________________________________
Spce-user mailing list
Spce-user at lists.sipwise.com <mailto:Spce-user at lists.sipwise.com>   <mailto:Spce-user at lists.sipwise.com> <mailto:Spce-user at lists.sipwise.com>
https://lists.sipwise.com/listinfo/spce-user

_______________________________________________
Spce-user mailing list
Spce-user at lists.sipwise.com <mailto:Spce-user at lists.sipwise.com> 
https://lists.sipwise.com/listinfo/spce-user

_______________________________________________
Spce-user mailing list
Spce-user at lists.sipwise.com <mailto:Spce-user at lists.sipwise.com> 
https://lists.sipwise.com/listinfo/spce-user

_______________________________________________
Spce-user mailing list
Spce-user at lists.sipwise.com <mailto:Spce-user at lists.sipwise.com> 
https://lists.sipwise.com/listinfo/spce-user
_______________________________________________
Spce-user mailing list
Spce-user at lists.sipwise.com <mailto:Spce-user at lists.sipwise.com> 
https://lists.sipwise.com/listinfo/spce-user

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20160417/ea5730c4/attachment-0001.html>