Re: [SR-Users] Number of sql connections

[Sergiu Pojoga]

Assuming you expect less traffic on the alternative ports, you could lower
the number of socket workers for those ports.
https://www.kamailio.org/wiki/cookbooks/5.1.x/core#socket_workers

On Mon, Nov 19, 2018 at 2:19 PM Duarte Rocha 
wrote:

> Greetings,
>
> I have my core parameter listen like this :
>
> listen=udp:eth0
>
> children=12
>
> Like this and the other settings, my kamailio has 21 threads and 20 Sql
> connections.
>
> If I add more listens,
>
> listen=udp:eth0
> listen=udp:eth0:5072
> listen=udp:eth0:5074
>
> Now I have 45 threads and 45 Sql connections.
>
> Why does this happen and can i set a a number of threads and/or sql
> connections that doesn't change with the number of "listen" parameters that
> i have ?
>
> Best Regards,
>
> Duarte Rocha
> ___
> Kamailio (SER) - Users Mailing List
> sr-users@lists.kamailio.org
> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] Number of sql connections

[Alex Balashov]

Unfortunately, you can't. 

Every child worker process has its own database connections, and child
worker processes number (children * listeners).

This is actually by design; if database connections were shared among
child processes, then in high volume operations, the mutual exclusion
("mutex") locking required for multiple processes to share connections
would become a drag on performance. This way, every child process can
access the database in its own "lane" without having to fight with any
other process over a shared handle.

-- Alex

On Mon, Nov 19, 2018 at 07:18:48PM +, Duarte Rocha wrote:

> Greetings,
> 
> I have my core parameter listen like this :
> 
> listen=udp:eth0
> 
> children=12
> 
> Like this and the other settings, my kamailio has 21 threads and 20 Sql
> connections.
> 
> If I add more listens,
> 
> listen=udp:eth0
> listen=udp:eth0:5072
> listen=udp:eth0:5074
> 
> Now I have 45 threads and 45 Sql connections.
> 
> Why does this happen and can i set a a number of threads and/or sql
> connections that doesn't change with the number of "listen" parameters that
> i have ?
> 
> Best Regards,
> 
> Duarte Rocha

> ___
> Kamailio (SER) - Users Mailing List
> sr-users@lists.kamailio.org
> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users


-- 
Alex Balashov | Principal | Evariste Systems LLC

Tel: +1-706-510-6800 / +1-800-250-5920 (toll-free) 
Web: http://www.evaristesys.com/, http://www.csrpswitch.com/

___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

[SR-Users] Number of sql connections

[Duarte Rocha]

Greetings,

I have my core parameter listen like this :

listen=udp:eth0

children=12

Like this and the other settings, my kamailio has 21 threads and 20 Sql
connections.

If I add more listens,

listen=udp:eth0
listen=udp:eth0:5072
listen=udp:eth0:5074

Now I have 45 threads and 45 Sql connections.

Why does this happen and can i set a a number of threads and/or sql
connections that doesn't change with the number of "listen" parameters that
i have ?

Best Regards,

Duarte Rocha
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] Dispatcher on 5.2

[Daniel-Constantin Mierla]

Hello,

can you try with latest branch 5.2? Recently it was a fix related to
finding next destination.

Cheers,
Daniel

On 19.11.18 15:29, Igor Olhovskiy wrote:
> Hi!
>
> Am I missing something or it’s a bug?
>
> Idea is following. I’m using dispatcher to load-balance calls. Using
> same weight destinations, order like in a file.
>
> So, dispatcher.list looks like 
> 1 sip:172.28.11.6:5060
> 1 sip:172.28.11.4:5060
>
> I’m using round-robin algo with 
>
> ds_select_dst(«1», «4»)
>
> But when it selects 172.28.11.4 and it for a reason not working, it
> will never come back to 172.28.11.6.
>
> Log: 
> … Relaying packet du: sip:172.28.11.4:5060
> … BYE/INVITE timeout with no reply
> … 49(59) WARNING: dispatcher [dispatch.c:2314]: ds_update_dst(): no
> xavp uri field in next destination record ((nil))
>
> modparam("dispatcher", "list_file", "/tmp/kamailio/dispatcher.list")
> modparam("dispatcher", "flags", 2)
> modparam("dispatcher", "force_dst", 1)
> modparam("dispatcher", "ds_hash_size", 9)
>
> Kamailio: version: kamailio 5.2.0-pre0
>
> Regards, Igor
>
> ___
> Kamailio (SER) - Users Mailing List
> sr-users@lists.kamailio.org
> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

-- 
Daniel-Constantin Mierla -- www.asipto.com
www.twitter.com/miconda -- www.linkedin.com/in/miconda
Kamailio World Conference -- www.kamailioworld.com
Kamailio Advanced Training, Nov 12-14, 2018, in Berlin -- www.asipto.com

___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

[SR-Users] Dispatcher on 5.2

[Igor Olhovskiy]

Hi!

Am I missing something or it’s a bug?

Idea is following. I’m using dispatcher to load-balance calls. Using same 
weight destinations, order like in a file.

So, dispatcher.list looks like
1 sip:172.28.11.6:5060
1 sip:172.28.11.4:5060

I’m using round-robin algo with

ds_select_dst(«1», «4»)

But when it selects 172.28.11.4 and it for a reason not working, it will never 
come back to 172.28.11.6.

Log:
… Relaying packet du: sip:172.28.11.4:5060
… BYE/INVITE timeout with no reply
… 49(59) WARNING: dispatcher [dispatch.c:2314]: ds_update_dst(): no xavp uri 
field in next destination record ((nil))

modparam("dispatcher", "list_file", "/tmp/kamailio/dispatcher.list")
modparam("dispatcher", "flags", 2)
modparam("dispatcher", "force_dst", 1)
modparam("dispatcher", "ds_hash_size", 9)

Kamailio: version: kamailio 5.2.0-pre0

Regards, Igor
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] Kamailio-5.1.6 Crash

[Hamid Hashmi]

 I am continuously receiving following error in the logs instead of disabling 
the sip trace module

captagent: [ERR] protocol_sip.c:132 Couldnot find this call

and when I restart the service there is a warning in the logs

Nov 18 20:33:47 kamailiostandby SIPSer[5495]: WARNING: tls [tls_init.c:781]: 
init_tls_h(): openssl bug #1491 (crash/mem leaks on low memory) workaround 
enabled (on low memory tls operations will fail preemptively) with free memory 
thresholds 17301504 and 8650752 bytes
Nov 18 20:33:47 kamailiostandby SIPSer[5495]: INFO:  
[core/cfg/cfg_ctx.c:598]: cfg_set_now(): tls.low_mem_threshold1 has been 
changed to 17301504
Nov 18 20:33:47 kamailiostandby SIPSer[5495]: INFO:  
[core/cfg/cfg_ctx.c:598]: cfg_set_now(): tls.low_mem_threshold2 has been 
changed to 8650752
Nov 18 20:33:47 kamailiostandby SIPSer[5495]: INFO:  
[core/udp_server.c:153]: probe_max_receive_buffer(): SO_RCVBUF is initially 
212992
Nov 18 20:33:47 kamailiostandby SIPSer[5495]: INFO:  
[core/udp_server.c:205]: probe_max_receive_buffer(): SO_RCVBUF is finally 425984

and the following line in some calls

Nov 18 20:33:23 kamailiostandby SIPSer[5063]: BYE 
WnsCPQeXMiJ-7KJZVQTxshtvGpTkG.GD WARNING: tm [h_table.c:142]: 
free_cell_helper(): removed cell 0x7f4358d2dea0 is still linked in hash table 
(t_lookup.c:1497)



Regards

Hamid R. Hashmi


From: Hamid Hashmi 
Sent: Monday, November 19, 2018 3:40 PM
To: Kamailio (SER) - Users Mailing List
Subject: Re: Kamailio-5.1.6 Crash

I have just changed '#define MAX_EXTRA 4' to '#define MAX_EXTRA 6' in the 
following file.

kamailio-5.1.6/src/modules/auth_radius/extra.h


Regards

Hamid R. Hashmi


From: sr-users  on behalf of Hamid Hashmi 

Sent: Monday, November 19, 2018 3:32 PM
To: Kamailio (SER) - Users Mailing List
Subject: [SR-Users] Kamailio-5.1.6 Crash

I have been using the following version of kamailio

Version: kamailio 5.1.6 (x86_64/linux)
  Default config: /usr/local/etc/kamailio/kamailio.cfg
  Default paths to modules: /usr/local/lib64/kamailio/modules
  Compile flags: STATS: Off, USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, 
USE_RAW_SOCKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MEM, SHM_MMAP, 
PKG_MALLOC, Q_MALLOC, F_MALLOC, TLSF_MALLOC, DBG_SR_MEMORY, USE_FUTEX, 
FAST_LOCK-ADAPTIVE_WAIT, USE_DNS_CACHE, USE_DNS_FAILOVER, USE_NAPTR, 
USE_DST_BLACKLIST, HAVE_RESOLV_RES
  MAX_RECV_BUFFER_SIZE=262144
  MAX_URI_SIZE=1024
  BUF_SIZE=65535
  DEFAULT PKG_SIZE=8MB
  DEFAULT SHM_SIZE=64MB
  ADAPTIVE_WAIT_LOOPS=1024
  TCP poll methods: poll, epoll_lt, epoll_et, sigio_rt, select
  Source code revision ID: unknown
  Compiled with: gcc 4.8.5
  Compiled on: 11:48:33 Oct 11 2018

and I noticed today that the Kamailio service is crashing.

[root@kamailiostandby /]# gdb core.17805
GNU gdb (GDB) Red Hat Enterprise Linux 7.6.1-100.el7_4.1
Copyright (C) 2013 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-redhat-linux-gnu".
For bug reporting instructions, please see:
...
[New LWP 17805]
Core was generated by `/usr/local/sbin/kamailio -P /run/kamailio/kamailio.pid 
-f /usr/local/SIP'.
Program terminated with signal 11, Segmentation fault.
#0  0x7f636559e54b in ?? ()
"/core.17805" is a core file.
Please specify an executable to debug.
(gdb) list
No symbol table is loaded.  Use the "file" command.
(gdb) bt
#0  0x7f636559e54b in ?? ()
#1  0x7f63a9571810 in ?? ()
#2  0x in ?? ()



Regards


Hamid R. Hashmi
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] RTPengine: shouldn't SDP be incremented when SDP is updated in-dialog?

[George Diamantopoulos]

We've run into an issue again, where a provider won't accept re-INVITEs for
session refresh where the SDP version counter hasn't been incremented. Has
there been any work on this or should I open an issue at github to make
this issue more visible?

Thanks!
George

On Fri, 4 May 2018 at 17:51, Richard Fuchs  wrote:

> On 04/11/2018 09:28 AM, George Diamantopoulos wrote:
> > Hello all,
> >
> > I have the following issue (I think) with RTP engine. An INVITE comes
> > in, and rtpengine will rewrite the SDP accordingly, as configured in
> > kamailio.cfg. After some time a reINVITE is sent out in the opposite
> > direction, for session refresh purposes. As I use rtcp-mux-offer in
> > kamailio.cfg for this direction, RTPengine will inject the rtcp-mux
> > parameter, and this reINVITE is forwarded to the UAC that sent the
> > original INVITE.
> >
> > However, the SDP in the reINVITE is exactly the same as the SDP in the
> > 200 OK to the original INVITE, with the exception of the rtcp-mux
> > parameter. Since the SDP offered from the same end has changed,
> > shouldn't session version be incremented as well?
> >
> > Does this sound like something that should be reported as a bug to
> > rtpengine? Or am I missing something here?
>
> Technically of course you're correct in that the version counter should
> be incremented if the SDP changed. Currently rtpengine always leaves the
> o= line unchanged, so there can be a discrepancy here in certain cases.
> This should probably be fixed, but this is also the first time I've
> heard of this actually causing an issue.
>
> Cheers
>
> ___
> Kamailio (SER) - Users Mailing List
> sr-users@lists.kamailio.org
> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] Kamailio-5.1.6 Crash

[Hamid Hashmi]

I have just changed '#define MAX_EXTRA 4' to '#define MAX_EXTRA 6' in the 
following file.

kamailio-5.1.6/src/modules/auth_radius/extra.h


Regards

Hamid R. Hashmi


From: sr-users  on behalf of Hamid Hashmi 

Sent: Monday, November 19, 2018 3:32 PM
To: Kamailio (SER) - Users Mailing List
Subject: [SR-Users] Kamailio-5.1.6 Crash

I have been using the following version of kamailio

Version: kamailio 5.1.6 (x86_64/linux)
  Default config: /usr/local/etc/kamailio/kamailio.cfg
  Default paths to modules: /usr/local/lib64/kamailio/modules
  Compile flags: STATS: Off, USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, 
USE_RAW_SOCKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MEM, SHM_MMAP, 
PKG_MALLOC, Q_MALLOC, F_MALLOC, TLSF_MALLOC, DBG_SR_MEMORY, USE_FUTEX, 
FAST_LOCK-ADAPTIVE_WAIT, USE_DNS_CACHE, USE_DNS_FAILOVER, USE_NAPTR, 
USE_DST_BLACKLIST, HAVE_RESOLV_RES
  MAX_RECV_BUFFER_SIZE=262144
  MAX_URI_SIZE=1024
  BUF_SIZE=65535
  DEFAULT PKG_SIZE=8MB
  DEFAULT SHM_SIZE=64MB
  ADAPTIVE_WAIT_LOOPS=1024
  TCP poll methods: poll, epoll_lt, epoll_et, sigio_rt, select
  Source code revision ID: unknown
  Compiled with: gcc 4.8.5
  Compiled on: 11:48:33 Oct 11 2018

and I noticed today that the Kamailio service is crashing.

[root@kamailiostandby /]# gdb core.17805
GNU gdb (GDB) Red Hat Enterprise Linux 7.6.1-100.el7_4.1
Copyright (C) 2013 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-redhat-linux-gnu".
For bug reporting instructions, please see:
...
[New LWP 17805]
Core was generated by `/usr/local/sbin/kamailio -P /run/kamailio/kamailio.pid 
-f /usr/local/SIP'.
Program terminated with signal 11, Segmentation fault.
#0  0x7f636559e54b in ?? ()
"/core.17805" is a core file.
Please specify an executable to debug.
(gdb) list
No symbol table is loaded.  Use the "file" command.
(gdb) bt
#0  0x7f636559e54b in ?? ()
#1  0x7f63a9571810 in ?? ()
#2  0x in ?? ()



Regards


Hamid R. Hashmi
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

[SR-Users] Kamailio-5.1.6 Crash

[Hamid Hashmi]

I have been using the following version of kamailio

Version: kamailio 5.1.6 (x86_64/linux)
  Default config: /usr/local/etc/kamailio/kamailio.cfg
  Default paths to modules: /usr/local/lib64/kamailio/modules
  Compile flags: STATS: Off, USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, 
USE_RAW_SOCKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MEM, SHM_MMAP, 
PKG_MALLOC, Q_MALLOC, F_MALLOC, TLSF_MALLOC, DBG_SR_MEMORY, USE_FUTEX, 
FAST_LOCK-ADAPTIVE_WAIT, USE_DNS_CACHE, USE_DNS_FAILOVER, USE_NAPTR, 
USE_DST_BLACKLIST, HAVE_RESOLV_RES
  MAX_RECV_BUFFER_SIZE=262144
  MAX_URI_SIZE=1024
  BUF_SIZE=65535
  DEFAULT PKG_SIZE=8MB
  DEFAULT SHM_SIZE=64MB
  ADAPTIVE_WAIT_LOOPS=1024
  TCP poll methods: poll, epoll_lt, epoll_et, sigio_rt, select
  Source code revision ID: unknown
  Compiled with: gcc 4.8.5
  Compiled on: 11:48:33 Oct 11 2018

and I noticed today that the Kamailio service is crashing.

[root@kamailiostandby /]# gdb core.17805
GNU gdb (GDB) Red Hat Enterprise Linux 7.6.1-100.el7_4.1
Copyright (C) 2013 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-redhat-linux-gnu".
For bug reporting instructions, please see:
...
[New LWP 17805]
Core was generated by `/usr/local/sbin/kamailio -P /run/kamailio/kamailio.pid 
-f /usr/local/SIP'.
Program terminated with signal 11, Segmentation fault.
#0  0x7f636559e54b in ?? ()
"/core.17805" is a core file.
Please specify an executable to debug.
(gdb) list
No symbol table is loaded.  Use the "file" command.
(gdb) bt
#0  0x7f636559e54b in ?? ()
#1  0x7f63a9571810 in ?? ()
#2  0x in ?? ()



Regards


Hamid R. Hashmi
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

[SR-Users] issue tracking dialogs with db_redis in kamailio 5.2

[David Escartín]

hello all

using version 5.2.0-rc0 of kamailio, we are trying to track the dialogs of 
dialog module using db_redis module with this setup
#!define DBURL_DIALOG "redis://127.0.0.1:6390/7"

# - dialog params -
modparam("dialog", "db_url", DBURL_DIALOG)
modparam("dialog", "enable_stats", 1)
modparam("dialog", "hash_size", 16384)
modparam("dialog", "dlg_flag", 31)
modparam("dialog", "dlg_match_mode", 1)
modparam("dialog", "db_mode", 1)
modparam("dialog", "timer_procs", 1)
modparam("dialog", "db_update_period", 1)


# - db_redis params -
modparam("db_redis", "schema_path", 
"/usr/local/kamailio/share/kamailio/db_redis/kamailio")
modparam("db_redis", "keys", "dialog=entry:hash_entry,hash_id,callid")
modparam("db_redis", "keys", 
"dialog_vars=entry:hash_entry,hash_id,dialog_key,dialog_value")


and we see it works and if a kamailio instance resets in the middle of a dialog 
it recovers all the dlg_vars and values because we have the db_skip_load to 0 
in dialog module.

But we have noticed that the redis is being written with the information of the 
dlg_var assigned until that moment when we get a provisional response with SDP, 
and we dom see a set on the redis with the dialog entry and id untill call is 
connected.

Nov 16 13:22:55 proxy-1 /usr/local/kamailio/sbin/kamailio[22424]: INFO: Call-ID 
1-1511@9.7.8.1: Status 180
Nov 16 13:22:55 proxy-1 /usr/local/kamailio/sbin/kamailio[22424]: WARNING: 
db_redis [redis_dbase.c:1489]: db_redis_perform_update(): performing full table 
scan on table 'dialog' while performing update
Nov 16 13:22:55 proxy-1 /usr/local/kamailio/sbin/kamailio[22424]: WARNING: 
db_redis [redis_dbase.c:1492]: db_redis_perform_update():   scan key 0 is 
'hash_entry'
Nov 16 13:22:55 proxy-1 /usr/local/kamailio/sbin/kamailio[22424]: WARNING: 
db_redis [redis_dbase.c:1492]: db_redis_perform_update():   scan key 1 is 
'hash_id'

on the redis (we only see hmset for dialog_vars key)
1542374575.721816 [7 127.0.0.1:56858] "HMSET" "dialog_vars:entry::13725:16494:_uac_funew:sip:1231215...@voda.interconnect.manxtelecom.im" 
"hash_entry" "13725" "hash_id" "16494" "dialog_key" "_uac_funew" "dialog_value" 
"sip:1231215...@voda.interconnect.manxtelecom.im"
1542374575.722001 [7 127.0.0.1:56858] "HMSET" "dialog_vars:entry::13725:16494:_uac_fu:sip:anonym...@voda.interconnect.manxtelecom.im" "hash_entry" 
"13725" "hash_id" "16494" "dialog_key" "_uac_fu" "dialog_value" 
"sip:anonym...@voda.interconnect.manxtelecom.im"


Nov 16 13:23:05 proxy-1 /usr/local/kamailio/sbin/kamailio[22425]: INFO: Call-ID 
1-1511@9.7.8.1: Status 200
Nov 16 13:23:05 proxy-1 /usr/local/kamailio/sbin/kamailio[22425]: WARNING: 
db_redis [redis_dbase.c:1489]: db_redis_perform_update(): performing full table 
scan on table 'dialog_vars' while performing update
Nov 16 13:23:05 proxy-1 /usr/local/kamailio/sbin/kamailio[22425]: WARNING: 
db_redis [redis_dbase.c:1492]: db_redis_perform_update():   scan key 0 is 
'hash_entry'
Nov 16 13:23:05 proxy-1 /usr/local/kamailio/sbin/kamailio[22425]: WARNING: 
db_redis [redis_dbase.c:1492]: db_redis_perform_update():   scan key 1 is 
'hash_id'
Nov 16 13:23:05 proxy-1 /usr/local/kamailio/sbin/kamailio[22425]: WARNING: 
db_redis [redis_dbase.c:1492]: db_redis_perform_update():   scan key 2 is 
'dialog_key'
Nov 16 13:23:05 proxy-1 /usr/local/kamailio/sbin/kamailio[22426]: WARNING: 
db_redis [redis_dbase.c:1489]: db_redis_perform_update(): performing full table 
scan on table 'dialog' while performing update
Nov 16 13:23:05 proxy-1 /usr/local/kamailio/sbin/kamailio[22426]: WARNING: 
db_redis [redis_dbase.c:1492]: db_redis_perform_update():   scan key 0 is 
'hash_entry'
Nov 16 13:23:05 proxy-1 /usr/local/kamailio/sbin/kamailio[22426]: WARNING: 
db_redis [redis_dbase.c:1492]: db_redis_perform_update():   scan key 1 is 
'hash_id'
Nov 16 13:23:05 proxy-1 /usr/local/kamailio/sbin/kamailio[22426]: WARNING: 
db_redis [redis_dbase.c:1489]: db_redis_perform_update(): performing full table 
scan on table 'dialog' while performing update
Nov 16 13:23:05 proxy-1 /usr/local/kamailio/sbin/kamailio[22426]: WARNING: 
db_redis [redis_dbase.c:1492]: db_redis_perform_update():   scan key 0 is 
'hash_entry'
Nov 16 13:23:05 proxy-1 /usr/local/kamailio/sbin/kamailio[22426]: WARNING: 
db_redis [redis_dbase.c:1492]: db_redis_perform_update():   scan key 1 is 
'hash_id'
Nov 16 13:23:05 proxy-1 /usr/local/kamailio/sbin/kamailio[22426]: INFO: Call-ID 
1-1511@9.7.8.1: ACK received in A-Leg

on the redis
1542374585.810520 [7 127.0.0.1:56882] "SCAN" "0" "MATCH" "dialog:entry::*" "COUNT" 
"1000"
1542374585.810672 [7 127.0.0.1:56882] "EXISTS" 
"dialog:entry::13725:16494:1-1511@9.7.8.1"
1542374585.810683 [7 127.0.0.1:56882] "HMGET" "dialog:entry::13725:16494:1-1511@9.7.8.1" 
"hash_entry" "hash_id"
1542374585.810776 [7 127.0.0.1:56882] "HMSET" "dialog:entry::13725:16494:1-1511@9.7.8.1" "state" "4" "timeout" "1542377585" "caller_cseq" 
"1" "callee_cseq" "0" "caller_contact" "sip:123456@9.7.8.1:5084" "callee_contact" 

[SR-Users] Releasing Kamailio v5.2.0

[Daniel-Constantin Mierla]

Hello,

I am consider to release v5.2.0 (the first stable version out of branch
5.2) next week, likely on Wednesday, Nov 28, 2018.

It still allows a bit more than a week of testing as well as well time
to prepare the online resources for it (documentation, wiki pages,
upgrade guidelines, etc...).

If there is any issue you are of and not yet reported to github bug
tracker, do it as soon as possible to give it a chance to be fixed in
time for the next major release.

Cheers,
Daniel

-- 
Daniel-Constantin Mierla -- www.asipto.com
www.twitter.com/miconda -- www.linkedin.com/in/miconda
Kamailio World Conference -- www.kamailioworld.com
Kamailio Advanced Training, Nov 12-14, 2018, in Berlin -- www.asipto.com


___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users