Re: [SR-Users] RPCFIFOPATH / DEFINE_FIFO_NAME settings problem

[Ginhoux, Patrick]

Hi,

 

Kamailio 5.0.1 is now installed,

 

The start and then the stop command works fine now. Kamailio is correctly 
stopped. 

 

I also tested a reboot, and saw kamailio started with success. A new attempt to 
stop it is also successful.

 

So I can tell that this issue is closed; the fifo file are created as 
appropriate:

 

[root@vm-vse02-siprouter2 ~]# ll /var/run/kamailio/

total 4

srw--- 1 kamailio kamailio 0 Apr  5 17:57 kamailio_ctl

-rw-r- 1 kamailio kamailio 5 Apr  5 17:57 kamailio.pid

prwxr-xr-x 1 kamailio kamailio 0 Apr  5 17:57 kamailio_rpc_fifo

 

About the htable fix, it is included in the 5.0.1 as I don’t get the string 
error anymore.

 

That’s really a great job you did.

 

Thanks you so much.

 

Cordialement

Patrick GINHOUX

 

De : Daniel-Constantin Mierla [mailto:mico...@gmail.com] 
Envoyé : mercredi 5 avril 2017 17:55
À : Ginhoux, Patrick 
Cc : Kamailio (SER) - Users Mailing List 
Objet : Re: [SR-Users] RPCFIFOPATH / DEFINE_FIFO_NAME settings problem

 

Hello,

yes, the patch for htable should be in 5.0.1.

Cheers,
Daniel

 

On 05.04.17 17:14, Ginhoux, Patrick wrote:

Hi,

 

I’m going to install the kamailio 5.0.1 .

 

One question before:

 

Can you tell me if it included the patch for the htable (issue 
“ht_db_load_table(): key type must be string (type=6)”) ?

 

Cordialement

Patrick GINHOUX

 

De : Daniel-Constantin Mierla [mailto:mico...@gmail.com] 
Envoyé : mercredi 5 avril 2017 17:09
À : Ginhoux, Patrick  <mailto:patrick.ginh...@fr.unisys.com> 

Cc : Kamailio (SER) - Users Mailing List  
<mailto:sr-users@lists.sip-router.org> 
Objet : Re: [SR-Users] RPCFIFOPATH / DEFINE_FIFO_NAME settings problem

 

Hello,

killproc might be only in opensuse as standalone tool and the other rpms have 
it in init.d lib functions...

Can you install the rpms for kamailio 5.0.1? They are already built:

https://build.opensuse.org/package/show/home:kamailio:v5.0.x-rpms/kamailio50

I tried to force the pid file path to killproc, but maybe the version is not 
supporting it. You may need to do 'killall kamailio' first time to stop 
existing kamailio, then do start and stop after installing the new packages.

If it fails, I will look for a different solution and trigger rpms to be 
rebuilt.

Cheers,
Daniel





-- 
Daniel-Constantin Mierla
www.twitter.com/miconda <http://www.twitter.com/miconda>  -- 
www.linkedin.com/in/miconda <http://www.linkedin.com/in/miconda> 
Kamailio Advanced Training - May 22-24 (USA) - www.asipto.com 
<http://www.asipto.com> 
Kamailio World Conference - May 8-10, 2017 - www.kamailioworld.com 
<http://www.kamailioworld.com> 


smime.p7s
Description: S/MIME cryptographic signature
___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] RPCFIFOPATH / DEFINE_FIFO_NAME settings problem

[Ginhoux, Patrick]

Hi,

 

I’m going to install the kamailio 5.0.1 .

 

One question before:

 

Can you tell me if it included the patch for the htable (issue 
“ht_db_load_table(): key type must be string (type=6)”) ?

 

Cordialement

Patrick GINHOUX

 

De : Daniel-Constantin Mierla [mailto:mico...@gmail.com] 
Envoyé : mercredi 5 avril 2017 17:09
À : Ginhoux, Patrick 
Cc : Kamailio (SER) - Users Mailing List 
Objet : Re: [SR-Users] RPCFIFOPATH / DEFINE_FIFO_NAME settings problem

 

Hello,

killproc might be only in opensuse as standalone tool and the other rpms have 
it in init.d lib functions...

Can you install the rpms for kamailio 5.0.1? They are already built:

https://build.opensuse.org/package/show/home:kamailio:v5.0.x-rpms/kamailio50

I tried to force the pid file path to killproc, but maybe the version is not 
supporting it. You may need to do 'killall kamailio' first time to stop 
existing kamailio, then do start and stop after installing the new packages.

If it fails, I will look for a different solution and trigger rpms to be 
rebuilt.

Cheers,
Daniel

 

On 05.04.17 16:50, Ginhoux, Patrick wrote:

Hi,

 

The killproc command doesn’t exist :

 

[root@vm-vse02-siprouter2 ~]# killproc -h

-bash: killproc: command not found

 

To help the debug, I added ‘echo’ command at the case statement in the 
/etc/init.d/Kamailio script :

 

# See how we were called.

case "$1" in

start|debug)

echo "GINHOUX Start"

start

;;

stop)

echo "GINHOUX"

stop

;;

status)

status $KAM

RETVAL=$?

;;

restart)

stop

start

;;

condrestart)

if [ -f $PID_FILE ] ; then

stop

start

fi

;;

*)

echo "PATRICK 2"

echo $"Usage: $PROG 
{start|stop|restart|condrestart|status|debug|help}"

exit 1

esac

 

The results of the different action are :

 

-  service kamailio stop è Nothing is displayed

-  service kamailio start è Nothing is displayed

-  service kamailio XXX  è “PATRICK 2” is displayed

 

[root@vm-vse02-siprouter2 ~]#

[root@vm-vse02-siprouter2 ~]# service kamailio stop

Stopping kamailio (via systemctl):  Warning: Unit file of kamailio.service 
changed on disk, 'systemctl daemon-reload' recommended.

   [  OK  ]

 

[root@vm-vse02-siprouter2 ~]# service kamailio start

Starting kamailio (via systemctl):  Warning: Unit file of kamailio.service 
changed on disk, 'systemctl daemon-reload' recommended.

Job for kamailio.service failed. See 'systemctl status kamailio.service' and 
'journalctl -xn' for details.

   [FAILED]

 

[root@vm-vse02-siprouter2 ~]# service kamailio XXX

PATRICK 2

Usage: kamailio {start|stop|restart|condrestart|status|debug|help}

 

It seems that when ‘stop|start’ are used, linux doesn’t run the 
/etc/init.d/kamailio script.

 

As you can see that it is complaining about the ‘systemctl daemon-reload’ 
command to use.

 

I proceeded the same (add ‘echo’ command) on another server running the 
previous Kamailio rpm. On this server there are no display (from the ‘echo’ 
command) but kamailio stops:

 

[root@vm-vse02-siprouter1 ~]# ps -ef |grep kam

kamailio  1159 1  0 16:35 ?00:00:00 /usr/sbin/kamailio -P 
/var/run/kamailio.pid -m 1024 -M 8 -u kamailio -g kamailio

kamailio  1161  1159  0 16:36 ?00:00:00 /usr/sbin/kamailio -P 
/var/run/kamailio.pid -m 1024 -M 8 -u kamailio -g kamailio

kamailio  1162  1159  0 16:36 ?00:00:00 /usr/sbin/kamailio -P 
/var/run/kamailio.pid -m 1024 -M 8 -u kamailio -g kamailio

kamailio  1163  1159  0 16:36 ?00:00:00 /usr/sbin/kamailio -P 
/var/run/kamailio.pid -m 1024 -M 8 -u kamailio -g kamailio

kamailio  1164  1159  0 16:36 ?00:00:00 /usr/sbin/kamailio -P 
/var/run/kamailio.pid -m 1024 -M 8 -u kamailio -g kamailio

kamailio  1165  1159  0 16:36 ?00:00:00 /usr/sbin/kamailio -P 
/var/run/kamailio.pid -m 1024 -M 8 -u kamailio -g kamailio

kamailio  1166  1159  0 16:36 ?00:00:00 /usr/sbin/kamailio -P 
/var/run/kamailio.pid -m 1024 -M 8 -u kamailio -g kamailio

kamailio  1167  1159  0 16:36 ?00:00:00 /usr/sbin/kamailio -P 
/var/run/kamailio.pid -m 1024 -M 8 -u kamailio -g kamailio

kamailio  1168  1159  0 16:36 ?00:00:00 /usr/sbin/kamailio -P 
/var/run/kamailio.pid -m 1024 -M 8 -u kamailio -g kamailio

kamailio  1169  1159  0 16:36 ?00:00:00 /usr/sbin/kamailio -P 
/var/run/kamailio.pid -m 1024 -M 8 -u kamailio -g kamailio

kamailio  1170  1159  0 16:36 ?00:00:00 /us

Re: [SR-Users] RPCFIFOPATH / DEFINE_FIFO_NAME settings problem

[Ginhoux, Patrick]

evert back to the previous Kamailio rpm on the server where 
the stop command doesn’t work.

 

Cordialement

Patrick GINHOUX

 

De : Daniel-Constantin Mierla [mailto:mico...@gmail.com] 
Envoyé : mercredi 5 avril 2017 16:00
À : Ginhoux, Patrick 
Cc : Kamailio (SER) - Users Mailing List 
Objet : Re: [SR-Users] RPCFIFOPATH / DEFINE_FIFO_NAME settings problem

 

Hello,

 

On 05.04.17 15:46, Ginhoux, Patrick wrote:

Hi,

 

Nothing happens after the ‘service kamailio stop’; kamailio is still running 
(same pid) ((as detaillled below).

 

can you run in terminal and give the output of the next command?

killproc -h

It seems that some versions are using a default path to PID file, which may not 
match where kamailio writes it.

Cheers,
Daniel





-- 
Daniel-Constantin Mierla
www.twitter.com/miconda <http://www.twitter.com/miconda>  -- 
www.linkedin.com/in/miconda <http://www.linkedin.com/in/miconda> 
Kamailio Advanced Training - May 22-24 (USA) - www.asipto.com 
<http://www.asipto.com> 
Kamailio World Conference - May 8-10, 2017 - www.kamailioworld.com 
<http://www.kamailioworld.com> 


smime.p7s
Description: S/MIME cryptographic signature
___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] RPCFIFOPATH / DEFINE_FIFO_NAME settings problem

[Ginhoux, Patrick]

Hi,

 

Nothing happens after the ‘service kamailio stop’; kamailio is still running 
(same pid) ((as detaillled below).

 

Cordialement

Patrick GINHOUX

 

De : Daniel-Constantin Mierla [mailto:mico...@gmail.com] 
Envoyé : mercredi 5 avril 2017 15:44
À : Ginhoux, Patrick 
Cc : Kamailio (SER) - Users Mailing List 
Objet : Re: [SR-Users] RPCFIFOPATH / DEFINE_FIFO_NAME settings problem

 

Hello,

the log messages show only that kamailio is already running.

If you do only 'service kamailio stop' what happens?

The new init.d script is creating /var/run/kamailio if it doesn't exist and 
sets chown to it. So not really affecting how kamailio is stopped or started.

Cheers,
Daniel

On 05.04.17 15:25, Ginhoux, Patrick wrote:

Hi,

 

New update.

 

I attempt to stop kamailio with the ‘service kamailio stop command’ but it 
doesn’t stop:

 

[root@vm-vse02-siprouter2 ~]# ps -ef |grep kam

kamailio  1157 1  0 15:10 ?00:00:00 /usr/sbin/kamailio -P 
/var/run/kamailio/kamailio.pid -m 1024 -M 8 -u kamailio -g kamailio

kamailio  1159  1157  0 15:10 ?00:00:00 /usr/sbin/kamailio -P 
/var/run/kamailio/kamailio.pid -m 1024 -M 8 -u kamailio -g kamailio

kamailio  1160  1157  0 15:10 ?00:00:00 /usr/sbin/kamailio -P 
/var/run/kamailio/kamailio.pid -m 1024 -M 8 -u kamailio -g kamailio

kamailio  1161  1157  0 15:10 ?00:00:00 /usr/sbin/kamailio -P 
/var/run/kamailio/kamailio.pid -m 1024 -M 8 -u kamailio -g kamailio

kamailio  1162  1157  0 15:10 ?00:00:00 /usr/sbin/kamailio -P 
/var/run/kamailio/kamailio.pid -m 1024 -M 8 -u kamailio -g kamailio

kamailio  1163  1157  0 15:10 ?00:00:00 /usr/sbin/kamailio -P 
/var/run/kamailio/kamailio.pid -m 1024 -M 8 -u kamailio -g kamailio

kamailio  1164  1157  0 15:10 ?00:00:00 /usr/sbin/kamailio -P 
/var/run/kamailio/kamailio.pid -m 1024 -M 8 -u kamailio -g kamailio

kamailio  1165  1157  0 15:10 ?00:00:00 /usr/sbin/kamailio -P 
/var/run/kamailio/kamailio.pid -m 1024 -M 8 -u kamailio -g kamailio

kamailio  1166  1157  0 15:10 ?00:00:00 /usr/sbin/kamailio -P 
/var/run/kamailio/kamailio.pid -m 1024 -M 8 -u kamailio -g kamailio

kamailio  1167  1157  0 15:10 ?00:00:00 /usr/sbin/kamailio -P 
/var/run/kamailio/kamailio.pid -m 1024 -M 8 -u kamailio -g kamailio

kamailio  1168  1157  0 15:10 ?00:00:00 /usr/sbin/kamailio -P 
/var/run/kamailio/kamailio.pid -m 1024 -M 8 -u kamailio -g kamailio

kamailio  1169  1157  0 15:10 ?00:00:00 /usr/sbin/kamailio -P 
/var/run/kamailio/kamailio.pid -m 1024 -M 8 -u kamailio -g kamailio

kamailio  1170  1157  0 15:10 ?00:00:00 /usr/sbin/kamailio -P 
/var/run/kamailio/kamailio.pid -m 1024 -M 8 -u kamailio -g kamailio

kamailio  1171  1157  0 15:10 ?00:00:00 /usr/sbin/kamailio -P 
/var/run/kamailio/kamailio.pid -m 1024 -M 8 -u kamailio -g kamailio

root  1197  1175  0 15:12 pts/000:00:00 grep --color=auto kam

[root@vm-vse02-siprouter2 ~]#

[root@vm-vse02-siprouter2 ~]# service kamailio stop

Stopping kamailio (via systemctl): [  OK  ]

 

We can see that kamailio is still running:

 

[root@vm-vse02-siprouter2 ~]# ps -ef |grep kam

kamailio  1157 1  0 15:10 ?00:00:00 /usr/sbin/kamailio -P 
/var/run/kamailio/kamailio.pid -m 1024 -M 8 -u kamailio -g kamailio

kamailio  1159  1157  0 15:10 ?00:00:00 /usr/sbin/kamailio -P 
/var/run/kamailio/kamailio.pid -m 1024 -M 8 -u kamailio -g kamailio

kamailio  1160  1157  0 15:10 ?00:00:00 /usr/sbin/kamailio -P 
/var/run/kamailio/kamailio.pid -m 1024 -M 8 -u kamailio -g kamailio

kamailio  1161  1157  0 15:10 ?00:00:00 /usr/sbin/kamailio -P 
/var/run/kamailio/kamailio.pid -m 1024 -M 8 -u kamailio -g kamailio

kamailio  1162  1157  0 15:10 ?00:00:00 /usr/sbin/kamailio -P 
/var/run/kamailio/kamailio.pid -m 1024 -M 8 -u kamailio -g kamailio

kamailio  1163  1157  0 15:10 ?00:00:00 /usr/sbin/kamailio -P 
/var/run/kamailio/kamailio.pid -m 1024 -M 8 -u kamailio -g kamailio

kamailio  1164  1157  0 15:10 ?00:00:00 /usr/sbin/kamailio -P 
/var/run/kamailio/kamailio.pid -m 1024 -M 8 -u kamailio -g kamailio

kamailio  1165  1157  0 15:10 ?00:00:00 /usr/sbin/kamailio -P 
/var/run/kamailio/kamailio.pid -m 1024 -M 8 -u kamailio -g kamailio

kamailio  1166  1157  0 15:10 ?00:00:00 /usr/sbin/kamailio -P 
/var/run/kamailio/kamailio.pid -m 1024 -M 8 -u kamailio -g kamailio

kamailio  1167  1157  0 15:10 ?00:00:00 /usr/sbin/kamailio -P 
/var/run/kamailio/kamailio.pid -m 1024 -M 8 -u kamailio -g kamailio

kamailio  1168  1157  0 15:10 ?00:00:00 /usr/sbin/kamailio -P 
/var/run/kamailio/kamailio.pid -m 1024 -M 8 -u kamailio -g kamailio

kamailio  1169  1157  0 15:10 ?00:00:00 /usr/sbin/kamailio -P 
/var/run/kamailio/kamailio.pid -m 1024 -M 8 -u kamailio -g kamailio

kamailio  1170  1157  0 15:10 ?00:00:00 /usr/sbin/kamailio -P 
/var/run/kamailio/kamailio.pid -m 1024 -M 8

Re: [SR-Users] RPCFIFOPATH / DEFINE_FIFO_NAME settings problem

[Ginhoux, Patrick]

tatus kamailio.service' and 'journalctl -xn' for details.

   [FAILED]

[root@vm-vse02-siprouter2 ~]#

[root@vm-vse02-siprouter2 ~]# systemctl status kamailio.service -l

kamailio.service - SYSV: Kamailio is a fast, reliable and flexible SIP Server.

   Loaded: loaded (/etc/rc.d/init.d/kamailio)

   Active: failed (Result: exit-code) since Wed 2017-04-05 15:19:09 CEST; 13s 
ago

  Process: 1256 ExecStart=/etc/rc.d/init.d/kamailio start (code=exited, 
status=1/FAILURE)

 

Apr 05 15:19:09 vm-vse02-siprouter2 kamailio[1267]: DEBUG:  
[core/sr_module.c:694]: find_mod_export_record(): find_export_record: found 
 in module textops [/usr/lib64/kamailio/modules/textops.so]

Apr 05 15:19:09 vm-vse02-siprouter2 kamailio[1267]: DEBUG:  
[core/route_struct.c:129]: mk_action(): ACTION_#24 #0/2: 9(9)/ (nil)

Apr 05 15:19:09 vm-vse02-siprouter2 kamailio[1267]: DEBUG:  
[core/route_struct.c:129]: mk_action(): ACTION_#24 #1/2: 3(3)/ (nil)

Apr 05 15:19:09 vm-vse02-siprouter2 kamailio[1267]: WARNING:  
[core/cfg.y:3378]: warn_at(): warning in config file 
//etc/kamailio/kamailio.cfg, line 978, column 6-13: constant value in if(...)

Apr 05 15:19:09 vm-vse02-siprouter2 kamailio[1267]: INFO:  
[core/sctp_core.c:75]: sctp_core_check_support(): SCTP API not enabled - if you 
want to use it, load sctp module

Apr 05 15:19:09 vm-vse02-siprouter2 kamailio[1269]: CRITICAL:  
[core/daemonize.c:345]: daemonize(): running process found in the pid file 
/var/run/kamailio/kamailio.pid

Apr 05 15:19:09 vm-vse02-siprouter2 kamailio[1256]: Starting kamailio:

Apr 05 15:19:09 vm-vse02-siprouter2 systemd[1]: kamailio.service: control 
process exited, code=exited status=1

Apr 05 15:19:09 vm-vse02-siprouter2 systemd[1]: Failed to start SYSV: Kamailio 
is a fast, reliable and flexible SIP Server..

Apr 05 15:19:09 vm-vse02-siprouter2 systemd[1]: Unit kamailio.service entered 
failed state.

 

Does it help to understand why this happen with the new Kamailio rpm 
(kamailio-5.0.0-10.1.x86_64)?

 

Cordialement

Patrick GINHOUX

 

De : Ginhoux, Patrick 
Envoyé : mercredi 5 avril 2017 14:49
À : 'mico...@gmail.com' 
Cc : Kamailio (SER) - Users Mailing List 
Objet : RE: [SR-Users] RPCFIFOPATH / DEFINE_FIFO_NAME settings problem

 

Hi,

 

Actually I discovered that kamailio is running after I break the ‘service 
Kamailio start’ command because of no response.

 

So I kill the Kamailio processes, check that it is not running anymore. In this 
case the start command is sufficient.

 

Below the action I do:

 

[root@vm-vse02-siprouter2 ~]# ps -ef |grep kam

kamailio  1426 1  0 14:31 ?00:00:00 /usr/sbin/kamailio -P 
/var/run/kamailio/kamailio.pid -m 1024 -M 8 -u kamailio -g kamailio

kamailio  1427  1426  0 14:31 ?00:00:00 /usr/sbin/kamailio -P 
/var/run/kamailio/kamailio.pid -m 1024 -M 8 -u kamailio -g kamailio

kamailio  1428  1426  0 14:31 ?00:00:00 /usr/sbin/kamailio -P 
/var/run/kamailio/kamailio.pid -m 1024 -M 8 -u kamailio -g kamailio

kamailio  1429  1426  0 14:31 ?00:00:00 /usr/sbin/kamailio -P 
/var/run/kamailio/kamailio.pid -m 1024 -M 8 -u kamailio -g kamailio

kamailio  1430  1426  0 14:31 ?00:00:00 /usr/sbin/kamailio -P 
/var/run/kamailio/kamailio.pid -m 1024 -M 8 -u kamailio -g kamailio

kamailio  1431  1426  0 14:31 ?00:00:00 /usr/sbin/kamailio -P 
/var/run/kamailio/kamailio.pid -m 1024 -M 8 -u kamailio -g kamailio

kamailio  1432  1426  0 14:31 ?00:00:00 /usr/sbin/kamailio -P 
/var/run/kamailio/kamailio.pid -m 1024 -M 8 -u kamailio -g kamailio

kamailio  1433  1426  0 14:31 ?00:00:00 /usr/sbin/kamailio -P 
/var/run/kamailio/kamailio.pid -m 1024 -M 8 -u kamailio -g kamailio

kamailio  1434  1426  0 14:31 ?00:00:00 /usr/sbin/kamailio -P 
/var/run/kamailio/kamailio.pid -m 1024 -M 8 -u kamailio -g kamailio

kamailio  1435  1426  0 14:31 ?00:00:00 /usr/sbin/kamailio -P 
/var/run/kamailio/kamailio.pid -m 1024 -M 8 -u kamailio -g kamailio

kamailio  1436  1426  0 14:31 ?00:00:00 /usr/sbin/kamailio -P 
/var/run/kamailio/kamailio.pid -m 1024 -M 8 -u kamailio -g kamailio

kamailio  1437  1426  0 14:31 ?00:00:00 /usr/sbin/kamailio -P 
/var/run/kamailio/kamailio.pid -m 1024 -M 8 -u kamailio -g kamailio

kamailio  1438  1426  0 14:31 ?00:00:00 /usr/sbin/kamailio -P 
/var/run/kamailio/kamailio.pid -m 1024 -M 8 -u kamailio -g kamailio

kamailio  1439  1426  0 14:31 ?00:00:00 /usr/sbin/kamailio -P 
/var/run/kamailio/kamailio.pid -m 1024 -M 8 -u kamailio -g kamailio

root  1461  1171  0 14:45 pts/000:00:00 grep --color=auto kam

 

[root@vm-vse02-siprouter2 ~]# kill 1426

[root@vm-vse02-siprouter2 ~]#

[root@vm-vse02-siprouter2 ~]# ps -ef |grep kam

root  1465  1171  0 14:46 pts/000:00:00 grep --color=auto kam

[root@vm-vse02-siprouter2 ~]#

[root@vm-vse02-siprouter2 ~]# service kamailio start

Starting kamailio (via systemctl):  ^C

[root@vm-vse02-

Re: [SR-Users] RPCFIFOPATH / DEFINE_FIFO_NAME settings problem

[Ginhoux, Patrick]

Hi,

 

Actually I discovered that kamailio is running after I break the ‘service 
Kamailio start’ command because of no response.

 

So I kill the Kamailio processes, check that it is not running anymore. In this 
case the start command is sufficient.

 

Below the action I do:

 

[root@vm-vse02-siprouter2 ~]# ps -ef |grep kam

kamailio  1426 1  0 14:31 ?00:00:00 /usr/sbin/kamailio -P 
/var/run/kamailio/kamailio.pid -m 1024 -M 8 -u kamailio -g kamailio

kamailio  1427  1426  0 14:31 ?00:00:00 /usr/sbin/kamailio -P 
/var/run/kamailio/kamailio.pid -m 1024 -M 8 -u kamailio -g kamailio

kamailio  1428  1426  0 14:31 ?00:00:00 /usr/sbin/kamailio -P 
/var/run/kamailio/kamailio.pid -m 1024 -M 8 -u kamailio -g kamailio

kamailio  1429  1426  0 14:31 ?00:00:00 /usr/sbin/kamailio -P 
/var/run/kamailio/kamailio.pid -m 1024 -M 8 -u kamailio -g kamailio

kamailio  1430  1426  0 14:31 ?00:00:00 /usr/sbin/kamailio -P 
/var/run/kamailio/kamailio.pid -m 1024 -M 8 -u kamailio -g kamailio

kamailio  1431  1426  0 14:31 ?00:00:00 /usr/sbin/kamailio -P 
/var/run/kamailio/kamailio.pid -m 1024 -M 8 -u kamailio -g kamailio

kamailio  1432  1426  0 14:31 ?00:00:00 /usr/sbin/kamailio -P 
/var/run/kamailio/kamailio.pid -m 1024 -M 8 -u kamailio -g kamailio

kamailio  1433  1426  0 14:31 ?00:00:00 /usr/sbin/kamailio -P 
/var/run/kamailio/kamailio.pid -m 1024 -M 8 -u kamailio -g kamailio

kamailio  1434  1426  0 14:31 ?00:00:00 /usr/sbin/kamailio -P 
/var/run/kamailio/kamailio.pid -m 1024 -M 8 -u kamailio -g kamailio

kamailio  1435  1426  0 14:31 ?00:00:00 /usr/sbin/kamailio -P 
/var/run/kamailio/kamailio.pid -m 1024 -M 8 -u kamailio -g kamailio

kamailio  1436  1426  0 14:31 ?00:00:00 /usr/sbin/kamailio -P 
/var/run/kamailio/kamailio.pid -m 1024 -M 8 -u kamailio -g kamailio

kamailio  1437  1426  0 14:31 ?00:00:00 /usr/sbin/kamailio -P 
/var/run/kamailio/kamailio.pid -m 1024 -M 8 -u kamailio -g kamailio

kamailio  1438  1426  0 14:31 ?00:00:00 /usr/sbin/kamailio -P 
/var/run/kamailio/kamailio.pid -m 1024 -M 8 -u kamailio -g kamailio

kamailio  1439  1426  0 14:31 ?00:00:00 /usr/sbin/kamailio -P 
/var/run/kamailio/kamailio.pid -m 1024 -M 8 -u kamailio -g kamailio

root  1461  1171  0 14:45 pts/000:00:00 grep --color=auto kam

 

[root@vm-vse02-siprouter2 ~]# kill 1426

[root@vm-vse02-siprouter2 ~]#

[root@vm-vse02-siprouter2 ~]# ps -ef |grep kam

root  1465  1171  0 14:46 pts/000:00:00 grep --color=auto kam

[root@vm-vse02-siprouter2 ~]#

[root@vm-vse02-siprouter2 ~]# service kamailio start

Starting kamailio (via systemctl):  ^C

[root@vm-vse02-siprouter2 ~]#

[root@vm-vse02-siprouter2 ~]#

[root@vm-vse02-siprouter2 ~]# ps -ef |grep kam

kamailio  1495 1  0 14:47 ?00:00:00 /usr/sbin/kamailio -P 
/var/run/kamailio/kamailio.pid -m 1024 -M 8 -u kamailio -g kamailio

kamailio  1496  1495  0 14:47 ?00:00:00 /usr/sbin/kamailio -P 
/var/run/kamailio/kamailio.pid -m 1024 -M 8 -u kamailio -g kamailio

kamailio  1497  1495  0 14:47 ?00:00:00 /usr/sbin/kamailio -P 
/var/run/kamailio/kamailio.pid -m 1024 -M 8 -u kamailio -g kamailio

kamailio  1498  1495  0 14:47 ?00:00:00 /usr/sbin/kamailio -P 
/var/run/kamailio/kamailio.pid -m 1024 -M 8 -u kamailio -g kamailio

kamailio  1499  1495  0 14:47 ?00:00:00 /usr/sbin/kamailio -P 
/var/run/kamailio/kamailio.pid -m 1024 -M 8 -u kamailio -g kamailio

kamailio  1500  1495  0 14:47 ?00:00:00 /usr/sbin/kamailio -P 
/var/run/kamailio/kamailio.pid -m 1024 -M 8 -u kamailio -g kamailio

kamailio  1501  1495  0 14:47 ?00:00:00 /usr/sbin/kamailio -P 
/var/run/kamailio/kamailio.pid -m 1024 -M 8 -u kamailio -g kamailio

kamailio  1502  1495  0 14:47 ?00:00:00 /usr/sbin/kamailio -P 
/var/run/kamailio/kamailio.pid -m 1024 -M 8 -u kamailio -g kamailio

kamailio  1503  1495  0 14:47 ?00:00:00 /usr/sbin/kamailio -P 
/var/run/kamailio/kamailio.pid -m 1024 -M 8 -u kamailio -g kamailio

kamailio  1504  1495  0 14:47 ?00:00:00 /usr/sbin/kamailio -P 
/var/run/kamailio/kamailio.pid -m 1024 -M 8 -u kamailio -g kamailio

kamailio  1505  1495  0 14:47 ?00:00:00 /usr/sbin/kamailio -P 
/var/run/kamailio/kamailio.pid -m 1024 -M 8 -u kamailio -g kamailio

kamailio  1506  1495  0 14:47 ?00:00:00 /usr/sbin/kamailio -P 
/var/run/kamailio/kamailio.pid -m 1024 -M 8 -u kamailio -g kamailio

kamailio  1507  1495  0 14:47 ?00:00:00 /usr/sbin/kamailio -P 
/var/run/kamailio/kamailio.pid -m 1024 -M 8 -u kamailio -g kamailio

kamailio  1508  1495  0 14:47 ?00:00:00 /usr/sbin/kamailio -P 
/var/run/kamailio/kamailio.pid -m 1024 -M 8 -u kamailio -g kamailio

root  1511  1171  0 14:47 pts/000:00:00 grep --color=auto kam

 

Cordialement

Patrick GINHOUX

 

De : Daniel-Constantin Mierla [mailto:mico...@gmail.com] 
Envoyé : mercredi 5 avril 2017 14:42
À : Ginhoux, Patrick 
Cc : Kamailio (SER

Re: [SR-Users] RPCFIFOPATH / DEFINE_FIFO_NAME settings problem

[Ginhoux, Patrick]

Hi,

 

Yes, it is running that is something I don’t understand how it can start with 
this error:

 

[root@vm-vse02-siprouter2 ~]# ps -ef |grep kam

kamailio  1225 1  0 14:03 ?00:00:00 /usr/sbin/kamailio -P 
/var/run/kamailio/kamailio.pid -m 1024 -M 8 -u kamailio -g kamailio

kamailio  1226  1225  0 14:03 ?00:00:00 /usr/sbin/kamailio -P 
/var/run/kamailio/kamailio.pid -m 1024 -M 8 -u kamailio -g kamailio

kamailio  1227  1225  0 14:03 ?00:00:00 /usr/sbin/kamailio -P 
/var/run/kamailio/kamailio.pid -m 1024 -M 8 -u kamailio -g kamailio

kamailio  1228  1225  0 14:03 ?00:00:00 /usr/sbin/kamailio -P 
/var/run/kamailio/kamailio.pid -m 1024 -M 8 -u kamailio -g kamailio

kamailio  1229  1225  0 14:03 ?00:00:00 /usr/sbin/kamailio -P 
/var/run/kamailio/kamailio.pid -m 1024 -M 8 -u kamailio -g kamailio

kamailio  1230  1225  0 14:03 ?00:00:00 /usr/sbin/kamailio -P 
/var/run/kamailio/kamailio.pid -m 1024 -M 8 -u kamailio -g kamailio

kamailio  1231  1225  0 14:03 ?00:00:00 /usr/sbin/kamailio -P 
/var/run/kamailio/kamailio.pid -m 1024 -M 8 -u kamailio -g kamailio

kamailio  1232  1225  0 14:03 ?00:00:00 /usr/sbin/kamailio -P 
/var/run/kamailio/kamailio.pid -m 1024 -M 8 -u kamailio -g kamailio

kamailio  1233  1225  0 14:03 ?00:00:00 /usr/sbin/kamailio -P 
/var/run/kamailio/kamailio.pid -m 1024 -M 8 -u kamailio -g kamailio

kamailio  1234  1225  0 14:03 ?00:00:00 /usr/sbin/kamailio -P 
/var/run/kamailio/kamailio.pid -m 1024 -M 8 -u kamailio -g kamailio

kamailio  1235  1225  0 14:03 ?00:00:00 /usr/sbin/kamailio -P 
/var/run/kamailio/kamailio.pid -m 1024 -M 8 -u kamailio -g kamailio

kamailio  1236  1225  0 14:03 ?00:00:00 /usr/sbin/kamailio -P 
/var/run/kamailio/kamailio.pid -m 1024 -M 8 -u kamailio -g kamailio

kamailio  1237  1225  0 14:03 ?00:00:00 /usr/sbin/kamailio -P 
/var/run/kamailio/kamailio.pid -m 1024 -M 8 -u kamailio -g kamailio

kamailio  1238  1225  0 14:03 ?00:00:00 /usr/sbin/kamailio -P 
/var/run/kamailio/kamailio.pid -m 1024 -M 8 -u kamailio -g kamailio

root  1344  1171  0 14:26 pts/000:00:00 grep --color=auto kam

 

So I kill the processes and then start again Kamailio, that again doesn’t end 
without CTRL-C. After that I can see Kamailio running:

 

[root@vm-vse02-siprouter2 ~]# ps -ef |grep kam

kamailio  1426 1  0 14:31 ?00:00:00 /usr/sbin/kamailio -P 
/var/run/kamailio/kamailio.pid -m 1024 -M 8 -u kamailio -g kamailio

kamailio  1427  1426  0 14:31 ?00:00:00 /usr/sbin/kamailio -P 
/var/run/kamailio/kamailio.pid -m 1024 -M 8 -u kamailio -g kamailio

kamailio  1428  1426  0 14:31 ?00:00:00 /usr/sbin/kamailio -P 
/var/run/kamailio/kamailio.pid -m 1024 -M 8 -u kamailio -g kamailio

kamailio  1429  1426  0 14:31 ?00:00:00 /usr/sbin/kamailio -P 
/var/run/kamailio/kamailio.pid -m 1024 -M 8 -u kamailio -g kamailio

kamailio  1430  1426  0 14:31 ?00:00:00 /usr/sbin/kamailio -P 
/var/run/kamailio/kamailio.pid -m 1024 -M 8 -u kamailio -g kamailio

kamailio  1431  1426  0 14:31 ?00:00:00 /usr/sbin/kamailio -P 
/var/run/kamailio/kamailio.pid -m 1024 -M 8 -u kamailio -g kamailio

kamailio  1432  1426  0 14:31 ?00:00:00 /usr/sbin/kamailio -P 
/var/run/kamailio/kamailio.pid -m 1024 -M 8 -u kamailio -g kamailio

kamailio  1433  1426  0 14:31 ?00:00:00 /usr/sbin/kamailio -P 
/var/run/kamailio/kamailio.pid -m 1024 -M 8 -u kamailio -g kamailio

kamailio  1434  1426  0 14:31 ?00:00:00 /usr/sbin/kamailio -P 
/var/run/kamailio/kamailio.pid -m 1024 -M 8 -u kamailio -g kamailio

kamailio  1435  1426  0 14:31 ?00:00:00 /usr/sbin/kamailio -P 
/var/run/kamailio/kamailio.pid -m 1024 -M 8 -u kamailio -g kamailio

kamailio  1436  1426  0 14:31 ?00:00:00 /usr/sbin/kamailio -P 
/var/run/kamailio/kamailio.pid -m 1024 -M 8 -u kamailio -g kamailio

kamailio  1437  1426  0 14:31 ?00:00:00 /usr/sbin/kamailio -P 
/var/run/kamailio/kamailio.pid -m 1024 -M 8 -u kamailio -g kamailio

kamailio  1438  1426  0 14:31 ?00:00:00 /usr/sbin/kamailio -P 
/var/run/kamailio/kamailio.pid -m 1024 -M 8 -u kamailio -g kamailio

kamailio  1439  1426  0 14:31 ?00:00:00 /usr/sbin/kamailio -P 
/var/run/kamailio/kamailio.pid -m 1024 -M 8 -u kamailio -g kamailio

root  1444  1171  0 14:32 pts/000:00:00 grep --color=auto kam

 

Do you have an idea that could explain this result?

 

Cordialement

Patrick GINHOUX

 

De : Daniel-Constantin Mierla [mailto:mico...@gmail.com] 
Envoyé : mercredi 5 avril 2017 14:22
À : Ginhoux, Patrick 
Cc : Kamailio (SER) - Users Mailing List 
Objet : Re: [SR-Users] RPCFIFOPATH / DEFINE_FIFO_NAME settings problem

 

Hello,

is kamailio already running there?

Cheers,
Daniel

 

On 05.04.17 14:12, Ginhoux, Patrick wrote:

Hi,

 

I have downloaded and installed only the new rpm : 
kamailio-5.0.0-10.1.x86_64.rpm. Is it enough ?

Then I try to start Kamailio that fails :

 

[root@vm

Re: [SR-Users] RPCFIFOPATH / DEFINE_FIFO_NAME settings problem

[Ginhoux, Patrick]

Hi,

 

Message resend due to size exceeded.

 

 

Yes, it is running that is something I don’t understand how it can start with 
this error:

 

[root@vm-vse02-siprouter2 ~]# ps -ef |grep kam

kamailio  1225 1  0 14:03 ?00:00:00 /usr/sbin/kamailio -P 
/var/run/kamailio/kamailio.pid -m 1024 -M 8 -u kamailio -g kamailio

kamailio  1226  1225  0 14:03 ?00:00:00 /usr/sbin/kamailio -P 
/var/run/kamailio/kamailio.pid -m 1024 -M 8 -u kamailio -g kamailio

kamailio  1227  1225  0 14:03 ?00:00:00 /usr/sbin/kamailio -P 
/var/run/kamailio/kamailio.pid -m 1024 -M 8 -u kamailio -g kamailio

kamailio  1228  1225  0 14:03 ?00:00:00 /usr/sbin/kamailio -P 
/var/run/kamailio/kamailio.pid -m 1024 -M 8 -u kamailio -g kamailio

kamailio  1229  1225  0 14:03 ?00:00:00 /usr/sbin/kamailio -P 
/var/run/kamailio/kamailio.pid -m 1024 -M 8 -u kamailio -g kamailio

kamailio  1230  1225  0 14:03 ?00:00:00 /usr/sbin/kamailio -P 
/var/run/kamailio/kamailio.pid -m 1024 -M 8 -u kamailio -g kamailio

kamailio  1231  1225  0 14:03 ?00:00:00 /usr/sbin/kamailio -P 
/var/run/kamailio/kamailio.pid -m 1024 -M 8 -u kamailio -g kamailio

kamailio  1232  1225  0 14:03 ?00:00:00 /usr/sbin/kamailio -P 
/var/run/kamailio/kamailio.pid -m 1024 -M 8 -u kamailio -g kamailio

kamailio  1233  1225  0 14:03 ?00:00:00 /usr/sbin/kamailio -P 
/var/run/kamailio/kamailio.pid -m 1024 -M 8 -u kamailio -g kamailio

kamailio  1234  1225  0 14:03 ?00:00:00 /usr/sbin/kamailio -P 
/var/run/kamailio/kamailio.pid -m 1024 -M 8 -u kamailio -g kamailio

kamailio  1235  1225  0 14:03 ?00:00:00 /usr/sbin/kamailio -P 
/var/run/kamailio/kamailio.pid -m 1024 -M 8 -u kamailio -g kamailio

kamailio  1236  1225  0 14:03 ?00:00:00 /usr/sbin/kamailio -P 
/var/run/kamailio/kamailio.pid -m 1024 -M 8 -u kamailio -g kamailio

kamailio  1237  1225  0 14:03 ?00:00:00 /usr/sbin/kamailio -P 
/var/run/kamailio/kamailio.pid -m 1024 -M 8 -u kamailio -g kamailio

kamailio  1238  1225  0 14:03 ?00:00:00 /usr/sbin/kamailio -P 
/var/run/kamailio/kamailio.pid -m 1024 -M 8 -u kamailio -g kamailio

root  1344  1171  0 14:26 pts/000:00:00 grep --color=auto kam

 

So I kill the processes and then start again Kamailio, that again doesn’t end 
without CTRL-C. After that I can see Kamailio running:

 

[root@vm-vse02-siprouter2 ~]# ps -ef |grep kam

kamailio  1426 1  0 14:31 ?00:00:00 /usr/sbin/kamailio -P 
/var/run/kamailio/kamailio.pid -m 1024 -M 8 -u kamailio -g kamailio

kamailio  1427  1426  0 14:31 ?00:00:00 /usr/sbin/kamailio -P 
/var/run/kamailio/kamailio.pid -m 1024 -M 8 -u kamailio -g kamailio

kamailio  1428  1426  0 14:31 ?00:00:00 /usr/sbin/kamailio -P 
/var/run/kamailio/kamailio.pid -m 1024 -M 8 -u kamailio -g kamailio

kamailio  1429  1426  0 14:31 ?00:00:00 /usr/sbin/kamailio -P 
/var/run/kamailio/kamailio.pid -m 1024 -M 8 -u kamailio -g kamailio

kamailio  1430  1426  0 14:31 ?00:00:00 /usr/sbin/kamailio -P 
/var/run/kamailio/kamailio.pid -m 1024 -M 8 -u kamailio -g kamailio

kamailio  1431  1426  0 14:31 ?00:00:00 /usr/sbin/kamailio -P 
/var/run/kamailio/kamailio.pid -m 1024 -M 8 -u kamailio -g kamailio

kamailio  1432  1426  0 14:31 ?00:00:00 /usr/sbin/kamailio -P 
/var/run/kamailio/kamailio.pid -m 1024 -M 8 -u kamailio -g kamailio

kamailio  1433  1426  0 14:31 ?00:00:00 /usr/sbin/kamailio -P 
/var/run/kamailio/kamailio.pid -m 1024 -M 8 -u kamailio -g kamailio

kamailio  1434  1426  0 14:31 ?00:00:00 /usr/sbin/kamailio -P 
/var/run/kamailio/kamailio.pid -m 1024 -M 8 -u kamailio -g kamailio

kamailio  1435  1426  0 14:31 ?00:00:00 /usr/sbin/kamailio -P 
/var/run/kamailio/kamailio.pid -m 1024 -M 8 -u kamailio -g kamailio

kamailio  1436  1426  0 14:31 ?00:00:00 /usr/sbin/kamailio -P 
/var/run/kamailio/kamailio.pid -m 1024 -M 8 -u kamailio -g kamailio

kamailio  1437  1426  0 14:31 ?00:00:00 /usr/sbin/kamailio -P 
/var/run/kamailio/kamailio.pid -m 1024 -M 8 -u kamailio -g kamailio

kamailio  1438  1426  0 14:31 ?00:00:00 /usr/sbin/kamailio -P 
/var/run/kamailio/kamailio.pid -m 1024 -M 8 -u kamailio -g kamailio

kamailio  1439  1426  0 14:31 ?00:00:00 /usr/sbin/kamailio -P 
/var/run/kamailio/kamailio.pid -m 1024 -M 8 -u kamailio -g kamailio

root  1444  1171  0 14:32 pts/000:00:00 grep --color=auto kam

 

Do you have an idea that could explain this result?

 

Cordialement

Patrick GINHOUX

 

De : Daniel-Constantin Mierla [ <mailto:mico...@gmail.com> 
mailto:mico...@gmail.com] 
Envoyé : mercredi 5 avril 2017 14:22
À : Ginhoux, Patrick < <mailto:patrick.ginh...@fr.unisys.com> 
patrick.ginh...@fr.unisys.com>
Cc : Kamailio (SER) - Users Mailing List < 
<mailto:sr-users@lists.sip-router.org> sr-users@lists.sip-router.org>
Objet : Re: [SR-Users] RPCFIFOPATH / DEFINE_FIFO_NAME settings problem

 

Hello,

is kamailio 

Re: [SR-Users] RPCFIFOPATH / DEFINE_FIFO_NAME settings problem

[Ginhoux, Patrick]

Hi,

 

I have downloaded and installed only the new rpm : 
kamailio-5.0.0-10.1.x86_64.rpm. Is it enough ?

Then I try to start Kamailio that fails :

 

[root@vm-vse02-siprouter2 kamailio]# service kamailio start

Starting kamailio (via systemctl):  Job for kamailio.service failed. See 
'systemctl status kamailio.service' and 'journalctl -xn' for details.

   [FAILED]

[root@vm-vse02-siprouter2 kamailio]#

[root@vm-vse02-siprouter2 kamailio]#

[root@vm-vse02-siprouter2 kamailio]# systemctl status kamailio.service -l

kamailio.service - SYSV: Kamailio is a fast, reliable and flexible SIP Server.

   Loaded: loaded (/etc/rc.d/init.d/kamailio)

   Active: failed (Result: exit-code) since Wed 2017-04-05 13:58:33 CEST; 4s ago

  Process: 4724 ExecStop=/etc/rc.d/init.d/kamailio stop (code=exited, 
status=0/SUCCESS)

  Process: 4867 ExecStart=/etc/rc.d/init.d/kamailio start (code=exited, 
status=1/FAILURE)

Main PID: 2946 (code=exited, status=0/SUCCESS)

 

Apr 05 13:58:33 vm-vse02-siprouter2 kamailio[4878]: DEBUG:  
[core/route_struct.c:129]: mk_action(): ACTION_#63 #0/2: 21(15)/ 0x7fdd400f638  
   8

Apr 05 13:58:33 vm-vse02-siprouter2 kamailio[4878]: DEBUG:  
[core/route_struct.c:129]: mk_action(): ACTION_#63 #1/2: 22(16)/ 0x7fdd400f588  
   8

Apr 05 13:58:33 vm-vse02-siprouter2 kamailio[4878]: DEBUG:  
[core/pvapi.c:321]: pv_cache_lookup(): pvar [$var(i:NodePath)] found in cache

Apr 05 13:58:33 vm-vse02-siprouter2 kamailio[4878]: WARNING:  
[core/cfg.y:3378]: warn_at(): warning in config file //etc/kamailio/kamailio
 .cfg, line 978, column 6-13: constant value in if(...)

Apr 05 13:58:33 vm-vse02-siprouter2 kamailio[4878]: INFO:  
[core/sctp_core.c:75]: sctp_core_check_support(): SCTP API not enabled - if you 
 want to use it, load sctp module

Apr 05 13:58:33 vm-vse02-siprouter2 kamailio[4880]: CRITICAL:  
[core/daemonize.c:345]: daemonize(): running process found in the pid file  
/var/run/kamailio/kamailio.pid

Apr 05 13:58:33 vm-vse02-siprouter2 kamailio[4867]: Starting kamailio:

Apr 05 13:58:33 vm-vse02-siprouter2 systemd[1]: kamailio.service: control 
process exited, code=exited status=1

Apr 05 13:58:33 vm-vse02-siprouter2 systemd[1]: Failed to start SYSV: Kamailio 
is a fast, reliable and flexible SIP Server..

Apr 05 13:58:33 vm-vse02-siprouter2 systemd[1]: Unit kamailio.service entered 
failed state.

 

I get also a strange result when I try to start Kamailio using the service 
Kamailio command, that is nothing happen, the server doesn’t give a status :

 

[root@vm-vse02-siprouter2 ~]# service kamailio start

Starting kamailio (via systemctl):  ^C

 

I have to send a CTRL C to break the action.

 

Cordialement

Patrick GINHOUX

 

De : Daniel-Constantin Mierla [mailto:mico...@gmail.com] 
Envoyé : mercredi 5 avril 2017 13:45
À : Ginhoux, Patrick ; Kamailio (SER) - Users 
Mailing List ; Kamailio (SER) - Users Mailing 
List 
Objet : Re: [SR-Users] RPCFIFOPATH / DEFINE_FIFO_NAME settings problem

 

Hello,

apparently the /var/run/kamailio folder was not created by the init.d script 
for rpm, as it is done in the deb specs. I updated it and triggered a rebuild 
of rpms, available at:

https://build.opensuse.org/package/show/home:kamailio:v5.0.x-rpms/kamailio50

Try to upgrade and then see if it works.

Later today we will release v5.0.1 and the rpms for it will have the new init.d 
script.

Cheers,
Daniel

 

On 03.04.17 15:01, Ginhoux, Patrick wrote:

Hi,

 

I use « service kamailio start », so the init.d script that is the one created 
at the installation.

 

Cordialement

Patrick GINHOUX

 

De : sr-users [mailto:sr-users-boun...@lists.sip-router.org] De la part de 
Daniel-Constantin Mierla
Envoyé : lundi 3 avril 2017 14:56
À : Kamailio (SER) - Users Mailing List  <mailto:sr-us...@lists.kamailio.org> 

Objet : Re: [SR-Users] RPCFIFOPATH / DEFINE_FIFO_NAME settings problem

 

Hello,

how do you start Kamailio? Via init.d/systemd script?

Cheers,
Daniel

 

On 03.04.17 14:34, Ginhoux, Patrick wrote:

Hi,

 

Selinux is disabled.

 

Cordialement

Patrick GINHOUX

 

De : Daniel-Constantin Mierla [mailto:mico...@gmail.com] 
Envoyé : lundi 3 avril 2017 14:33
À : Ginhoux, Patrick  <mailto:patrick.ginh...@fr.unisys.com> 
; Kamailio (SER) - Users Mailing List  
<mailto:sr-users@lists.sip-router.org> 
Objet : Re: [SR-Users] RPCFIFOPATH / DEFINE_FIFO_NAME settings problem

 

Hello,

have you disabled selinux to see if starts ok without it?

Cheers,
Daniel

 

On 03.04.17 13:54, Ginhoux, Patrick wrote:

Hi,

 

Well, with one of my colleagues, we did some research and test, but we don’t 
find where the privilege issue is with the /var/ FS.

If the fifo filename is "/var/run/kamailio/kamailio_rpc_fifo" or 
"/var/run/kamailio_rpc_fifo", we have this privilege issue. 

I thought that the following declaration would prev

Re: [SR-Users] Why these 2 items in the same entry for a htable

[Ginhoux, Patrick]

Hi,

 

Thanks for these additional explanation on the htable.

 

Now I have to work more on this by myself.

 

Cordialement

Patrick GINHOUX

 

De : Daniel-Constantin Mierla [mailto:mico...@gmail.com] 
Envoyé : mardi 4 avril 2017 17:12
À : Ginhoux, Patrick 
Cc : Kamailio (SER) - Users Mailing List 
Objet : Re: [SR-Users] Why these 2 items in the same entry for a htable

 

Hello,

 

On 04.04.17 14:11, Ginhoux, Patrick wrote:

Hi,

 

Thanks for the link I’ll take a lot more later.

 

Now a quick look seems funny :

 

Ideally, the hash function will assign each key to a unique bucket, but most 
hash table designs employ an imperfect hash function, which might cause hash 
collisions <https://en.wikipedia.org/wiki/Collision_%28computer_science%29>  
where the hash function generates the same index for more than one key. Such 
collisions must be accommodated in some way.

 

If I understand well, this is typically the case I have. Am I correct ?


Yes, when there are collisions, then the slot has more than one item, stored as 
a linked list.

Actually, unlike the statements above, is quite common to have collisions, 
otherwise one cannot store more items than the number of allocated slots.

The main benefit is speeding up the searching. Imagine you have 1 000 000 
items. Finding one by its name can take in the worse case 1 000 000 string 
comparisons. But if you use a hash table having 1 000 slots with a hashing 
functions that gives you fair distribution, it means that once the hash id (a 
number) is computed (fast in memory operations), the index of the slot holding 
the item is 'hashid module nr_of_slots' , then there can be maximum 1 000 
string comparisons with the items in that slot.

In additions, by storing the hashid inside the item structure, we compare first 
the hashid values and if there is a match, then the string names, so 
practically there are number comparisons most of the time (very fast) and 
string comparisons (slower) only in very few occasions (typically only once, 
when matching the requested item).

Cheers,
Daniel




 

Cordialement

Patrick GINHOUX

 

De : sr-users [mailto:sr-users-boun...@lists.sip-router.org] De la part de 
Daniel-Constantin Mierla
Envoyé : mardi 4 avril 2017 12:45
À : Kamailio (SER) - Users Mailing List  <mailto:sr-users@lists.sip-router.org> 

Objet : Re: [SR-Users] Why these 2 items in the same entry for a htable

 

Hello,

if you are not familiar with hash table structure, take a bit of time to read 
about it, a good article on wikipedia:

  - https://en.wikipedia.org/wiki/Hash_table

The dump prints only details of the slots (buckets) that have data on it 
(size>0). The entry field in the dump content is practically the index of the 
slot.

I hope it helps!

Cheers,
Daniel

On 04.04.17 08:49, Ginhoux, Patrick wrote:

Hi,

 

While working on the project to migrate my kamailio.cfg script from kamailio 
3.3.1 to 5.0.x, I discovered that in there are 2 items in the same htable.

 

Below the figure that illustrate this case :

 

1)  Content of the MBXRANGE table :

 

mysql> select * from mbxrange;

+-+-+-++--+

| id  | key_name| key_value   | 
value_type | key_type |

+-+-+-++--+

|   0 | VERSION | 120104-173400   | 
 0 |0 |

| 101 | 1   | min=01;max=01;node=OPMVTS1VSE02 | 
 0 |0 |

| 102 | 2   | min=02;max=02;node=OPMVTS1VSE02 | 
 0 |0 |

| 103 | 3   | min=03;max=03;node=OPMVTS1VSE02 | 
 0 |0 |

| 104 | 4   | min=04;max=04;node=OPMVTS1VSE02 | 
 0 |0 |

| 105 | 5   | min=05;max=05;node=OPMVTS1VSE02 | 
 0 |0 |

| 106 | 6   | min=06;max=06;node=OPMVTS1VSE02 | 
 0 |0 |

| 107 | 7   | min=07;max=07;node=OPMVTS1VSE02 | 
 0 |0 |

| 108 | 8   | min=08;max=08;node=OPMVTS1VSE02 | 
 0 |0 |

| 109 | 9   | min=09;max=09;node=OPMVTS1VSE02 | 
 0 |0 |

| 199 | maxmbxrange | 9   | 
 0 |0 |

+-+-+-++--+

11 rows in set (0.00 sec)

 

2)  modparam instruction used in my kamailio.cfg script:

 

modparam("htable", "htable", "mbxrangeHash=>size=4;dbtable=mbxrange;")

 

3)  Result of « kamctl fifo sht_dump mbxrangeHash » command with kamailio 
version 3.3.x:

 

[root@op52is4router1 ~]# kamctl fifo sht_dump mbxrangeHash

Entry:: 0

6

Re: [SR-Users] ht_db_load_table(): key type must be string (type=6)

[Ginhoux, Patrick]

Hi,

 

Good news, one of my colleague help me to compile the htable.so including your 
patch. I have tested it with success.

 

Now, what is the next steps for you ? 

Are you going to include this patch in the different stream 5.0.x (or others) 
right away ? 

And do you generate new rpm for the different distros ?

 

Again thanks a lot for the help.

 

Cordialement

Patrick GINHOUX

 

De : Ginhoux, Patrick 
Envoyé : lundi 3 avril 2017 15:05
À : 'mico...@gmail.com' 
Cc : Kamailio (SER) - Users Mailing List 
Objet : RE: [SR-Users] ht_db_load_table(): key type must be string (type=6)

 

Hi,

 

I have not myself the knowledge to get this patch included in my installation 
(without a rpm) and then test it; and for the moment I don’t have anybody 
available that could help me.

 

I’ll keep you posted if I can get people around me.

 

Cordialement

Patrick GINHOUX

 

De : Daniel-Constantin Mierla [mailto:mico...@gmail.com] 
Envoyé : lundi 3 avril 2017 14:29
À : Ginhoux, Patrick mailto:patrick.ginh...@fr.unisys.com> >
Cc : Kamailio (SER) - Users Mailing List mailto:sr-users@lists.sip-router.org> >
Objet : Re: [SR-Users] ht_db_load_table(): key type must be string (type=6)

 

Hello,

thanks for reminder, actually I missed that email, not reading it so far.

I just pushed a patch in master that should handle the blob/text columns:

  - 
https://github.com/kamailio/kamailio/commit/24e729698017b5d898a92cdf7acb024e44252b84

Can you test it? If all ok, then I will backport.

Cheers,
Daniel

 

On 03.04.17 13:58, Ginhoux, Patrick wrote:

Hi Daniel,

 

Do you look at this error with the item type of ‘text’ in a mysql table?

 

Cordialement

Patrick GINHOUX

 

De : Ginhoux, Patrick 
Envoyé : vendredi 24 mars 2017 10:44
À : 'Kamailio (SER) - Users Mailing List'  
<mailto:sr-users@lists.sip-router.org> 
Objet : RE: [SR-Users] ht_db_load_table(): key type must be string (type=6)

 

Hi Daniel,

 

I think that this key type problem has to do with the type of ‘text’used for 
some fields in my myqsl db.

 

By changing the type from ‘text’ to varchar(256), the problem goes away.

 

It is for sure just a workaround, that is ok for me for the moment, but in the 
case people would need to have text, we can get this problem back.

 

I hope this help.

 

Cordialement

Patrick GINHOUX

 

De : Ginhoux, Patrick 
Envoyé : mardi 21 mars 2017 13:29
À : Kamailio (SER) - Users Mailing List mailto:sr-users@lists.sip-router.org> >
Objet : RE: [SR-Users] ht_db_load_table(): key type must be string (type=6)

 

Hi,

 

Below the structure of the properties table :

 

mysql> show create table properties;

+++

| Table  | Create Table 


  |

+++

| properties | CREATE TABLE `properties` (

  `id` int(6) unsigned NOT NULL AUTO_INCREMENT COMMENT 'UniqueID',

  `key_name` text NOT NULL,

  `key_value` text NOT NULL,

  `value_type` int(1) NOT NULL,

  `key_type` int(1) NOT NULL,

  PRIMARY KEY (`id`)

) ENGINE=InnoDB AUTO_INCREMENT=10001 DEFAULT CHARSET=latin1 |

+++

1 row in set (0.02 sec)

 

Cordialement

Patrick GINHOUX

 

De : sr-users [mailto:sr-users-boun...@lists.sip-router.org] De la part de 
Daniel-Constantin Mierla
Envoyé : mardi 21 mars 2017 13:25
À : Kamailio (SER) - Users Mailing List mailto:sr-users@lists.sip-router.org> >
Objet : Re: [SR-Users] ht_db_load_table(): key type must be string (type=6)

 

Hello,

can you give the structure of the table properties (show create table ...)?

Cheers,

Daniel

March 21, 2017 11:30 AM, "Ginhoux, Patrick" mailto:%22Ginhoux,%20patrick%22%20%3cpatrick.ginh...@fr.unisys.com%3e> > wrote:

Hi,

A second update for people who started to look at this issue.

I have identified the real cause of the problem by looking

Re: [SR-Users] Why these 2 items in the same entry for a htable

[Ginhoux, Patrick]

Hi,

 

Thanks for the link I’ll take a lot more later.

 

Now a quick look seems funny :

 

Ideally, the hash function will assign each key to a unique bucket, but most 
hash table designs employ an imperfect hash function, which might cause hash 
collisions <https://en.wikipedia.org/wiki/Collision_(computer_science)>  where 
the hash function generates the same index for more than one key. Such 
collisions must be accommodated in some way.

 

If I understand well, this is typically the case I have. Am I correct ?

 

Cordialement

Patrick GINHOUX

 

De : sr-users [mailto:sr-users-boun...@lists.sip-router.org] De la part de 
Daniel-Constantin Mierla
Envoyé : mardi 4 avril 2017 12:45
À : Kamailio (SER) - Users Mailing List 
Objet : Re: [SR-Users] Why these 2 items in the same entry for a htable

 

Hello,

if you are not familiar with hash table structure, take a bit of time to read 
about it, a good article on wikipedia:

  - https://en.wikipedia.org/wiki/Hash_table

The dump prints only details of the slots (buckets) that have data on it 
(size>0). The entry field in the dump content is practically the index of the 
slot.

I hope it helps!

Cheers,
Daniel

On 04.04.17 08:49, Ginhoux, Patrick wrote:

Hi,

 

While working on the project to migrate my kamailio.cfg script from kamailio 
3.3.1 to 5.0.x, I discovered that in there are 2 items in the same htable.

 

Below the figure that illustrate this case :

 

1)  Content of the MBXRANGE table :

 

mysql> select * from mbxrange;

+-+-+-++--+

| id  | key_name| key_value   | 
value_type | key_type |

+-+-+-++--+

|   0 | VERSION | 120104-173400   | 
 0 |0 |

| 101 | 1   | min=01;max=01;node=OPMVTS1VSE02 | 
 0 |0 |

| 102 | 2   | min=02;max=02;node=OPMVTS1VSE02 | 
 0 |0 |

| 103 | 3   | min=03;max=03;node=OPMVTS1VSE02 | 
 0 |0 |

| 104 | 4   | min=04;max=04;node=OPMVTS1VSE02 | 
 0 |0 |

| 105 | 5   | min=05;max=05;node=OPMVTS1VSE02 | 
 0 |0 |

| 106 | 6   | min=06;max=06;node=OPMVTS1VSE02 | 
 0 |0 |

| 107 | 7   | min=07;max=07;node=OPMVTS1VSE02 | 
 0 |0 |

| 108 | 8   | min=08;max=08;node=OPMVTS1VSE02 | 
 0 |0 |

| 109 | 9   | min=09;max=09;node=OPMVTS1VSE02 | 
 0 |0 |

| 199 | maxmbxrange | 9   | 
 0 |0 |

+-+-+-++--+

11 rows in set (0.00 sec)

 

2)  modparam instruction used in my kamailio.cfg script:

 

modparam("htable", "htable", "mbxrangeHash=>size=4;dbtable=mbxrange;")

 

3)  Result of « kamctl fifo sht_dump mbxrangeHash » command with kamailio 
version 3.3.x:

 

[root@op52is4router1 ~]# kamctl fifo sht_dump mbxrangeHash

Entry:: 0

6:: min=06;max=06;node=OPMVTS1VSE02

Entry:: 1

7:: min=07;max=07;node=OPMVTS1VSE02

Entry:: 2

4:: min=04;max=04;node=OPMVTS1VSE02

Entry:: 3

5:: min=05;max=05;node=OPMVTS1VSE02

Entry:: 4

2:: min=02;max=02;node=OPMVTS1VSE02

Entry:: 5

3:: min=03;max=03;node=OPMVTS1VSE02

VERSION:: 120104-173400

Entry:: 6

maxmbxrange:: 9

Entry:: 7

1:: min=01;max=01;node=OPMVTS1VSE02

Entry:: 14

9:: min=09;max=09;node=OPMVTS1VSE02

Entry:: 15

8:: min=08;max=08;node=OPMVTS1VSE02

 

Result of « kamcmd htable.dump mbxrangeHash » command with kamailio version 
5.0.x :

 

[root@vm-vse02-siprouter1 ~]# kamcmd htable.dump mbxrangeHash

{

entry: 0

size: 1

slot: {

item: {

name: 6

value: min=06;max=06;node=OPMMMS1VSE02

type: str

}

}

}

{

entry: 1

size: 1

slot: {

item: {

name: 7

value: min=07;max=07;node=OPMMMS1VSE02

type: str

}

}

}

{

entry: 2

size: 1

slot: {

item: {

name: 4

value: min=04;max=04;node=OPMMMS1VSE02

type: str

   

[SR-Users] Why these 2 items in the same entry for a htable

[Ginhoux, Patrick]

Hi,

 

While working on the project to migrate my kamailio.cfg script from kamailio
3.3.1 to 5.0.x, I discovered that in there are 2 items in the same htable.

 

Below the figure that illustrate this case :

 

1)  Content of the MBXRANGE table :

 

mysql> select * from mbxrange;

+-+-+-+-
---+--+

| id  | key_name| key_value   |
value_type | key_type |

+-+-+-+-
---+--+

|   0 | VERSION | 120104-173400   |
0 |0 |

| 101 | 1   | min=01;max=01;node=OPMVTS1VSE02 |
0 |0 |

| 102 | 2   | min=02;max=02;node=OPMVTS1VSE02 |
0 |0 |

| 103 | 3   | min=03;max=03;node=OPMVTS1VSE02 |
0 |0 |

| 104 | 4   | min=04;max=04;node=OPMVTS1VSE02 |
0 |0 |

| 105 | 5   | min=05;max=05;node=OPMVTS1VSE02 |
0 |0 |

| 106 | 6   | min=06;max=06;node=OPMVTS1VSE02 |
0 |0 |

| 107 | 7   | min=07;max=07;node=OPMVTS1VSE02 |
0 |0 |

| 108 | 8   | min=08;max=08;node=OPMVTS1VSE02 |
0 |0 |

| 109 | 9   | min=09;max=09;node=OPMVTS1VSE02 |
0 |0 |

| 199 | maxmbxrange | 9   |
0 |0 |

+-+-+-+-
---+--+

11 rows in set (0.00 sec)

 

2)  modparam instruction used in my kamailio.cfg script:

 

modparam("htable", "htable", "mbxrangeHash=>size=4;dbtable=mbxrange;")

 

3)  Result of < kamctl fifo sht_dump mbxrangeHash > command with
kamailio version 3.3.x:

 

[root@op52is4router1 ~]# kamctl fifo sht_dump mbxrangeHash

Entry:: 0

6:: min=06;max=06;node=OPMVTS1VSE02

Entry:: 1

7:: min=07;max=07;node=OPMVTS1VSE02

Entry:: 2

4:: min=04;max=04;node=OPMVTS1VSE02

Entry:: 3

5:: min=05;max=05;node=OPMVTS1VSE02

Entry:: 4

2:: min=02;max=02;node=OPMVTS1VSE02

Entry:: 5

3:: min=03;max=03;node=OPMVTS1VSE02

VERSION:: 120104-173400

Entry:: 6

maxmbxrange:: 9

Entry:: 7

1:: min=01;max=01;node=OPMVTS1VSE02

Entry:: 14

9:: min=09;max=09;node=OPMVTS1VSE02

Entry:: 15

8:: min=08;max=08;node=OPMVTS1VSE02

 

Result of < kamcmd htable.dump mbxrangeHash > command with kamailio version
5.0.x :

 

[root@vm-vse02-siprouter1 ~]# kamcmd htable.dump mbxrangeHash

{

entry: 0

size: 1

slot: {

item: {

name: 6

value:
min=06;max=06;node=OPMMMS1VSE02

type: str

}

}

}

{

entry: 1

size: 1

slot: {

item: {

name: 7

value:
min=07;max=07;node=OPMMMS1VSE02

type: str

}

}

}

{

entry: 2

size: 1

slot: {

item: {

name: 4

value:
min=04;max=04;node=OPMMMS1VSE02

type: str

}

}

}

{

entry: 3

size: 1

slot: {

item: {

name: 5

value:
min=05;max=05;node=OPMMMS1VSE02

type: str

}

}

}

{

entry: 4

size: 1

slot: {

item: {

name: 2

value:
min=02;max=02;node=OPMMMS1VSE02

type: str

}

}

}

{

entry: 5

size: 2

slot: {

item: {

name: 3

value:
min=03;max=03;node=OPMMMS1VSE02

type: str

}

item: {

name: VERSION

value: 120104-173400

type: str

}

}

}

{

entry: 6

size: 1

slot: {

item: {

name: maxmbxrange

value: 9

type: str

}

}

}

{

entry: 7

size: 1

slot: {

item: {

name: 1

value:
min=01;max=01;node=OPMMMS1VSE02

   

Re: [SR-Users] ht_db_load_table(): key type must be string (type=6)

[Ginhoux, Patrick]

Hi,

 

I have not myself the knowledge to get this patch included in my installation 
(without a rpm) and then test it; and for the moment I don’t have anybody 
available that could help me.

 

I’ll keep you posted if I can get people around me.

 

Cordialement

Patrick GINHOUX

 

De : Daniel-Constantin Mierla [mailto:mico...@gmail.com] 
Envoyé : lundi 3 avril 2017 14:29
À : Ginhoux, Patrick 
Cc : Kamailio (SER) - Users Mailing List 
Objet : Re: [SR-Users] ht_db_load_table(): key type must be string (type=6)

 

Hello,

thanks for reminder, actually I missed that email, not reading it so far.

I just pushed a patch in master that should handle the blob/text columns:

  - 
https://github.com/kamailio/kamailio/commit/24e729698017b5d898a92cdf7acb024e44252b84

Can you test it? If all ok, then I will backport.

Cheers,
Daniel

 

On 03.04.17 13:58, Ginhoux, Patrick wrote:

Hi Daniel,

 

Do you look at this error with the item type of ‘text’ in a mysql table?

 

Cordialement

Patrick GINHOUX

 

De : Ginhoux, Patrick 
Envoyé : vendredi 24 mars 2017 10:44
À : 'Kamailio (SER) - Users Mailing List'  
<mailto:sr-users@lists.sip-router.org> 
Objet : RE: [SR-Users] ht_db_load_table(): key type must be string (type=6)

 

Hi Daniel,

 

I think that this key type problem has to do with the type of ‘text’used for 
some fields in my myqsl db.

 

By changing the type from ‘text’ to varchar(256), the problem goes away.

 

It is for sure just a workaround, that is ok for me for the moment, but in the 
case people would need to have text, we can get this problem back.

 

I hope this help.

 

Cordialement

Patrick GINHOUX

 

De : Ginhoux, Patrick 
Envoyé : mardi 21 mars 2017 13:29
À : Kamailio (SER) - Users Mailing List mailto:sr-users@lists.sip-router.org> >
Objet : RE: [SR-Users] ht_db_load_table(): key type must be string (type=6)

 

Hi,

 

Below the structure of the properties table :

 

mysql> show create table properties;

+++

| Table  | Create Table 


  |

+++

| properties | CREATE TABLE `properties` (

  `id` int(6) unsigned NOT NULL AUTO_INCREMENT COMMENT 'UniqueID',

  `key_name` text NOT NULL,

  `key_value` text NOT NULL,

  `value_type` int(1) NOT NULL,

  `key_type` int(1) NOT NULL,

  PRIMARY KEY (`id`)

) ENGINE=InnoDB AUTO_INCREMENT=10001 DEFAULT CHARSET=latin1 |

+++

1 row in set (0.02 sec)

 

Cordialement

Patrick GINHOUX

 

De : sr-users [mailto:sr-users-boun...@lists.sip-router.org] De la part de 
Daniel-Constantin Mierla
Envoyé : mardi 21 mars 2017 13:25
À : Kamailio (SER) - Users Mailing List mailto:sr-users@lists.sip-router.org> >
Objet : Re: [SR-Users] ht_db_load_table(): key type must be string (type=6)

 

Hello,

can you give the structure of the table properties (show create table ...)?

Cheers,

Daniel

March 21, 2017 11:30 AM, "Ginhoux, Patrick" mailto:%22Ginhoux,%20patrick%22%20%3cpatrick.ginh...@fr.unisys.com%3e> > wrote:

Hi,

A second update for people who started to look at this issue.

I have identified the real cause of the problem by looking more in the kamailio 
log with the debug traces. I discover that it is related to the load of the 
properties table in the htable.

I have the following entries in my mysql db :

+---++-++--+

| id | key_name | key_value | value_type | key_type |

+---++-++--+

| 0 | VERSION | 120104-1734 | 0 | 0 |

| 1 | mmm-retry | 408=Y;502=Y;503=Y | 0 | 0 |

| 2 | mgcf-retry | 408=Y;502=Y;503=Y | 0 | 0 |

| 3 | max-mmm-retry | 2 | 0 | 0 |

| 4 | max-mgcf-retry | 2 | 0 | 0 |

| 5 | target-uri | mgcf=10.10.10.

Re: [SR-Users] RPCFIFOPATH / DEFINE_FIFO_NAME settings problem

[Ginhoux, Patrick]

Hi,

 

I use « service kamailio start », so the init.d script that is the one created 
at the installation.

 

Cordialement

Patrick GINHOUX

 

De : sr-users [mailto:sr-users-boun...@lists.sip-router.org] De la part de 
Daniel-Constantin Mierla
Envoyé : lundi 3 avril 2017 14:56
À : Kamailio (SER) - Users Mailing List 
Objet : Re: [SR-Users] RPCFIFOPATH / DEFINE_FIFO_NAME settings problem

 

Hello,

how do you start Kamailio? Via init.d/systemd script?

Cheers,
Daniel

 

On 03.04.17 14:34, Ginhoux, Patrick wrote:

Hi,

 

Selinux is disabled.

 

Cordialement

Patrick GINHOUX

 

De : Daniel-Constantin Mierla [mailto:mico...@gmail.com] 
Envoyé : lundi 3 avril 2017 14:33
À : Ginhoux, Patrick  <mailto:patrick.ginh...@fr.unisys.com> 
; Kamailio (SER) - Users Mailing List  
<mailto:sr-users@lists.sip-router.org> 
Objet : Re: [SR-Users] RPCFIFOPATH / DEFINE_FIFO_NAME settings problem

 

Hello,

have you disabled selinux to see if starts ok without it?

Cheers,
Daniel

 

On 03.04.17 13:54, Ginhoux, Patrick wrote:

Hi,

 

Well, with one of my colleagues, we did some research and test, but we don’t 
find where the privilege issue is with the /var/ FS.

If the fifo filename is "/var/run/kamailio/kamailio_rpc_fifo" or 
"/var/run/kamailio_rpc_fifo", we have this privilege issue. 

I thought that the following declaration would prevent this security issue :

modparam("jsonrpcs", "fifo_name", DEFINE_FIFO_NAME)

modparam("jsonrpcs", "fifo_mode", 0755)

modparam("jsonrpcs", "fifo_group", "kamailio")

modparam("jsonrpcs", "fifo_user", "kamailio")

but it is not the case.

 

For the moment only the fifo filename “/tmp/kamailio_rpc_fifo" is valid for 
kamailio to start.

 

 

Cordialement

Patrick GINHOUX

 

De : Ginhoux, Patrick 
Envoyé : lundi 27 mars 2017 17:46
À : 'mico...@gmail.com <mailto:mico...@gmail.com> '  <mailto:mico...@gmail.com> 
; Kamailio (SER) - Users Mailing List  
<mailto:sr-users@lists.sip-router.org> 
Objet : RE: [SR-Users] RPCFIFOPATH / DEFINE_FIFO_NAME settings problem

 

Hi,

 

I continue to investigate on this area.

 

I’m thinking that there are some security settings on the FS /var/, and I’m 
looking for if we have the rights to change it (I work for a project and don’t 
have all the ability to change some settings without agreement).

 

I’ll update you later tomorrow. 

 

Cordialement

Patrick GINHOUX

 

De : Daniel-Constantin Mierla [mailto:mico...@gmail.com] 
Envoyé : lundi 27 mars 2017 15:28
À : Ginhoux, Patrick mailto:patrick.ginh...@fr.unisys.com> >; Kamailio (SER) - Users Mailing List 
mailto:sr-users@lists.sip-router.org> >
Objet : Re: [SR-Users] RPCFIFOPATH / DEFINE_FIFO_NAME settings problem

 

Hello,

as recently as last week, someone encountered an file access problem while 
installing Siremis, which is using also some temporary files in /var/, even it 
was granting provileges via chown and chmod. All went fine after disabling 
selinux. It was on a centos.

I am not saying it is the same, but it could, so try without centos to see if 
the issue persists.

Cheers,
Daniel

 

On 27/03/2017 15:10, Ginhoux, Patrick wrote:

Hi,

 

This is the RHEL 7.1 distro, and there is use of selinux, apparmor or other 
tools.  

 

Are you meaning that the /var/run/ folder would be secured more than other 
folders?

 

Cordialement

Patrick GINHOUX

 

De : sr-users [mailto:sr-users-boun...@lists.sip-router.org] De la part de 
Daniel-Constantin Mierla
Envoyé : lundi 27 mars 2017 13:52
À : Kamailio (SER) - Users Mailing List  <mailto:sr-users@lists.sip-router.org> 

Objet : Re: [SR-Users] RPCFIFOPATH / DEFINE_FIFO_NAME settings problem

 

Hello,

kamailio should attempt to create the /var/run/kamailio folder if the 
application is run with enough privileges. However, some operating systems add 
more constraints on top of the execution user.

What is your OS distro? Do you have selinux, apparmor or other similar tools 
enabled?

Cheers,
Daniel

 

On 24/03/2017 17:52, Ginhoux, Patrick wrote:

In my ‘kamctlrc’ file :

 

## path to FIFO file for engine RPCFIFO

RPCFIFOPATH="/var/run/kamailio/kamailio_rpc_fifo"

#RPCFIFOPATH="/tmp/kamailio_rpc_fifo"

 

In my ‘kamailio.cfg’ :

 

!!ifndef DEFINE_FIFO_NAME

!!define DEFINE_FIFO_NAME "/var/run/kamailio/kamailio_rpc_fifo"

!!endif   

 

 

modparam("jsonrpcs", "pretty_format", 1)

modparam("jsonrpcs", "transport", 2)

modparam("jsonrpcs", "fifo_name", DEFINE_FIFO_NAME)

modparam("jsonrpcs", "fifo_mode", 0755)

modparam("jsonrpcs", "fifo_group", "kamailio")

modparam("jsonrpcs", "fifo_user", "kamailio")

 

 

kamailio doesn’t start. It reports ‘Permission denied’ :

 

Mar 24 1

Re: [SR-Users] RPCFIFOPATH / DEFINE_FIFO_NAME settings problem

[Ginhoux, Patrick]

Hi,

 

Selinux is disabled.

 

Cordialement

Patrick GINHOUX

 

De : Daniel-Constantin Mierla [mailto:mico...@gmail.com] 
Envoyé : lundi 3 avril 2017 14:33
À : Ginhoux, Patrick ; Kamailio (SER) - Users 
Mailing List 
Objet : Re: [SR-Users] RPCFIFOPATH / DEFINE_FIFO_NAME settings problem

 

Hello,

have you disabled selinux to see if starts ok without it?

Cheers,
Daniel

 

On 03.04.17 13:54, Ginhoux, Patrick wrote:

Hi,

 

Well, with one of my colleagues, we did some research and test, but we don’t 
find where the privilege issue is with the /var/ FS.

If the fifo filename is "/var/run/kamailio/kamailio_rpc_fifo" or 
"/var/run/kamailio_rpc_fifo", we have this privilege issue. 

I thought that the following declaration would prevent this security issue :

modparam("jsonrpcs", "fifo_name", DEFINE_FIFO_NAME)

modparam("jsonrpcs", "fifo_mode", 0755)

modparam("jsonrpcs", "fifo_group", "kamailio")

modparam("jsonrpcs", "fifo_user", "kamailio")

but it is not the case.

 

For the moment only the fifo filename “/tmp/kamailio_rpc_fifo" is valid for 
kamailio to start.

 

 

Cordialement

Patrick GINHOUX

 

De : Ginhoux, Patrick 
Envoyé : lundi 27 mars 2017 17:46
À : 'mico...@gmail.com <mailto:mico...@gmail.com> '  <mailto:mico...@gmail.com> 
; Kamailio (SER) - Users Mailing List  
<mailto:sr-users@lists.sip-router.org> 
Objet : RE: [SR-Users] RPCFIFOPATH / DEFINE_FIFO_NAME settings problem

 

Hi,

 

I continue to investigate on this area.

 

I’m thinking that there are some security settings on the FS /var/, and I’m 
looking for if we have the rights to change it (I work for a project and don’t 
have all the ability to change some settings without agreement).

 

I’ll update you later tomorrow. 

 

Cordialement

Patrick GINHOUX

 

De : Daniel-Constantin Mierla [mailto:mico...@gmail.com] 
Envoyé : lundi 27 mars 2017 15:28
À : Ginhoux, Patrick mailto:patrick.ginh...@fr.unisys.com> >; Kamailio (SER) - Users Mailing List 
mailto:sr-users@lists.sip-router.org> >
Objet : Re: [SR-Users] RPCFIFOPATH / DEFINE_FIFO_NAME settings problem

 

Hello,

as recently as last week, someone encountered an file access problem while 
installing Siremis, which is using also some temporary files in /var/, even it 
was granting provileges via chown and chmod. All went fine after disabling 
selinux. It was on a centos.

I am not saying it is the same, but it could, so try without centos to see if 
the issue persists.

Cheers,
Daniel

 

On 27/03/2017 15:10, Ginhoux, Patrick wrote:

Hi,

 

This is the RHEL 7.1 distro, and there is use of selinux, apparmor or other 
tools.  

 

Are you meaning that the /var/run/ folder would be secured more than other 
folders?

 

Cordialement

Patrick GINHOUX

 

De : sr-users [mailto:sr-users-boun...@lists.sip-router.org] De la part de 
Daniel-Constantin Mierla
Envoyé : lundi 27 mars 2017 13:52
À : Kamailio (SER) - Users Mailing List  <mailto:sr-users@lists.sip-router.org> 

Objet : Re: [SR-Users] RPCFIFOPATH / DEFINE_FIFO_NAME settings problem

 

Hello,

kamailio should attempt to create the /var/run/kamailio folder if the 
application is run with enough privileges. However, some operating systems add 
more constraints on top of the execution user.

What is your OS distro? Do you have selinux, apparmor or other similar tools 
enabled?

Cheers,
Daniel

 

On 24/03/2017 17:52, Ginhoux, Patrick wrote:

In my ‘kamctlrc’ file :

 

## path to FIFO file for engine RPCFIFO

RPCFIFOPATH="/var/run/kamailio/kamailio_rpc_fifo"

#RPCFIFOPATH="/tmp/kamailio_rpc_fifo"

 

In my ‘kamailio.cfg’ :

 

!!ifndef DEFINE_FIFO_NAME

!!define DEFINE_FIFO_NAME "/var/run/kamailio/kamailio_rpc_fifo"

!!endif   

 

 

modparam("jsonrpcs", "pretty_format", 1)

modparam("jsonrpcs", "transport", 2)

modparam("jsonrpcs", "fifo_name", DEFINE_FIFO_NAME)

modparam("jsonrpcs", "fifo_mode", 0755)

modparam("jsonrpcs", "fifo_group", "kamailio")

modparam("jsonrpcs", "fifo_user", "kamailio")

 

 

kamailio doesn’t start. It reports ‘Permission denied’ :

 

Mar 24 17:31:21 localhost /usr/sbin/kamailio[1138]: ERROR: jsonrpcs 
[jsonrpcs_fifo.c:144]: jsonrpc_init_fifo_server(): Can't create FIFO: 
Permission denied (mode=493)

Mar 24 17:31:21 localhost /usr/sbin/kamailio[1138]: CRITICAL: jsonrpcs 
[jsonrpcs_fifo.c:489]: jsonrpc_fifo_process(): failed to init jsonrpc fifo 
server

Mar 24 17:31:21 localhost /usr/sbin/kamailio[1120]: ALERT:  [main.c:741]: 
handle_sigs(): child process 1138 exited normally, status=255

Mar 24 17:31:21 localhost /usr/sbin/kamailio[1130]: DEBUG:  
[core/sr_module.c:920]: init_mod_child(): rank 4: tm

Mar 24 17:31:21 localhost /usr/sbin/kamai

Re: [SR-Users] ht_db_load_table(): key type must be string (type=6)

[Ginhoux, Patrick]

Hi Daniel,

 

Do you look at this error with the item type of ‘text’ in a mysql table?

 

Cordialement

Patrick GINHOUX

 

De : Ginhoux, Patrick 
Envoyé : vendredi 24 mars 2017 10:44
À : 'Kamailio (SER) - Users Mailing List' 
Objet : RE: [SR-Users] ht_db_load_table(): key type must be string (type=6)

 

Hi Daniel,

 

I think that this key type problem has to do with the type of ‘text’used for 
some fields in my myqsl db.

 

By changing the type from ‘text’ to varchar(256), the problem goes away.

 

It is for sure just a workaround, that is ok for me for the moment, but in the 
case people would need to have text, we can get this problem back.

 

I hope this help.

 

Cordialement

Patrick GINHOUX

 

De : Ginhoux, Patrick 
Envoyé : mardi 21 mars 2017 13:29
À : Kamailio (SER) - Users Mailing List mailto:sr-users@lists.sip-router.org> >
Objet : RE: [SR-Users] ht_db_load_table(): key type must be string (type=6)

 

Hi,

 

Below the structure of the properties table :

 

mysql> show create table properties;

+++

| Table  | Create Table 


  |

+++

| properties | CREATE TABLE `properties` (

  `id` int(6) unsigned NOT NULL AUTO_INCREMENT COMMENT 'UniqueID',

  `key_name` text NOT NULL,

  `key_value` text NOT NULL,

  `value_type` int(1) NOT NULL,

  `key_type` int(1) NOT NULL,

  PRIMARY KEY (`id`)

) ENGINE=InnoDB AUTO_INCREMENT=10001 DEFAULT CHARSET=latin1 |

+++

1 row in set (0.02 sec)

 

Cordialement

Patrick GINHOUX

 

De : sr-users [mailto:sr-users-boun...@lists.sip-router.org] De la part de 
Daniel-Constantin Mierla
Envoyé : mardi 21 mars 2017 13:25
À : Kamailio (SER) - Users Mailing List mailto:sr-users@lists.sip-router.org> >
Objet : Re: [SR-Users] ht_db_load_table(): key type must be string (type=6)

 

Hello,

can you give the structure of the table properties (show create table ...)?

Cheers,

Daniel

March 21, 2017 11:30 AM, "Ginhoux, Patrick" mailto:%22Ginhoux,%20patrick%22%20%3cpatrick.ginh...@fr.unisys.com%3e> > wrote:

Hi,

A second update for people who started to look at this issue.

I have identified the real cause of the problem by looking more in the kamailio 
log with the debug traces. I discover that it is related to the load of the 
properties table in the htable.

I have the following entries in my mysql db :

+---++-++--+

| id | key_name | key_value | value_type | key_type |

+---++-++--+

| 0 | VERSION | 120104-1734 | 0 | 0 |

| 1 | mmm-retry | 408=Y;502=Y;503=Y | 0 | 0 |

| 2 | mgcf-retry | 408=Y;502=Y;503=Y | 0 | 0 |

| 3 | max-mmm-retry | 2 | 0 | 0 |

| 4 | max-mgcf-retry | 2 | 0 | 0 |

| 5 | target-uri | mgcf=10.10.10.10;mmm-legacy=20.20.20.10;mmm=20.20.20.20 | 0 
| 0 |

| 6 | pike-status | 503 Service Overload | 0 | 0 |

| 7 | mgcf-path | 99 | 0 | 0 |

| 16 | mmm-nodeid | OPMMMS1VSE01=1;OPMMMS1VSE02=2 | 0 | 0 |

| 17 | mmm-node-path | 1=1;2=2 | 0 | 0 |

+---++-++--+

In the kamailio.cfg, the << modparam("htable", "htable", 
"propertiesHash=>size=4;dbtable=properties;") >> command causes the load of the 
above table in the htable.

In the log we can see, that the load is done in the alphabetic order of the 
key_name and it fails to load the last entry “VERSION” :

Mar 21 10:25:28 localhost /usr/sbin/kamailio[5784]: DEBUG:  
[db_val.c:169]: db_str2val(): converting BLOB [VERSION]

Mar 21 10:25:28 localhost /usr/sbin/kamailio[5784]: DEBUG:  
[db_val.c:74]: db_str2val(): converting INT [0]

Mar 21 10:2

Re: [SR-Users] RPCFIFOPATH / DEFINE_FIFO_NAME settings problem

[Ginhoux, Patrick]

Hi,

 

Well, with one of my colleagues, we did some research and test, but we don’t 
find where the privilege issue is with the /var/ FS.

If the fifo filename is "/var/run/kamailio/kamailio_rpc_fifo" or 
"/var/run/kamailio_rpc_fifo", we have this privilege issue. 

I thought that the following declaration would prevent this security issue :

modparam("jsonrpcs", "fifo_name", DEFINE_FIFO_NAME)

modparam("jsonrpcs", "fifo_mode", 0755)

modparam("jsonrpcs", "fifo_group", "kamailio")

modparam("jsonrpcs", "fifo_user", "kamailio")

but it is not the case.

 

For the moment only the fifo filename “/tmp/kamailio_rpc_fifo" is valid for 
kamailio to start.

 

 

Cordialement

Patrick GINHOUX

 

De : Ginhoux, Patrick 
Envoyé : lundi 27 mars 2017 17:46
À : 'mico...@gmail.com' ; Kamailio (SER) - Users Mailing 
List 
Objet : RE: [SR-Users] RPCFIFOPATH / DEFINE_FIFO_NAME settings problem

 

Hi,

 

I continue to investigate on this area.

 

I’m thinking that there are some security settings on the FS /var/, and I’m 
looking for if we have the rights to change it (I work for a project and don’t 
have all the ability to change some settings without agreement).

 

I’ll update you later tomorrow. 

 

Cordialement

Patrick GINHOUX

 

De : Daniel-Constantin Mierla [mailto:mico...@gmail.com] 
Envoyé : lundi 27 mars 2017 15:28
À : Ginhoux, Patrick mailto:patrick.ginh...@fr.unisys.com> >; Kamailio (SER) - Users Mailing List 
mailto:sr-users@lists.sip-router.org> >
Objet : Re: [SR-Users] RPCFIFOPATH / DEFINE_FIFO_NAME settings problem

 

Hello,

as recently as last week, someone encountered an file access problem while 
installing Siremis, which is using also some temporary files in /var/, even it 
was granting provileges via chown and chmod. All went fine after disabling 
selinux. It was on a centos.

I am not saying it is the same, but it could, so try without centos to see if 
the issue persists.

Cheers,
Daniel

 

On 27/03/2017 15:10, Ginhoux, Patrick wrote:

Hi,

 

This is the RHEL 7.1 distro, and there is use of selinux, apparmor or other 
tools.  

 

Are you meaning that the /var/run/ folder would be secured more than other 
folders?

 

Cordialement

Patrick GINHOUX

 

De : sr-users [mailto:sr-users-boun...@lists.sip-router.org] De la part de 
Daniel-Constantin Mierla
Envoyé : lundi 27 mars 2017 13:52
À : Kamailio (SER) - Users Mailing List  <mailto:sr-users@lists.sip-router.org> 

Objet : Re: [SR-Users] RPCFIFOPATH / DEFINE_FIFO_NAME settings problem

 

Hello,

kamailio should attempt to create the /var/run/kamailio folder if the 
application is run with enough privileges. However, some operating systems add 
more constraints on top of the execution user.

What is your OS distro? Do you have selinux, apparmor or other similar tools 
enabled?

Cheers,
Daniel

 

On 24/03/2017 17:52, Ginhoux, Patrick wrote:

In my ‘kamctlrc’ file :

 

## path to FIFO file for engine RPCFIFO

RPCFIFOPATH="/var/run/kamailio/kamailio_rpc_fifo"

#RPCFIFOPATH="/tmp/kamailio_rpc_fifo"

 

In my ‘kamailio.cfg’ :

 

!!ifndef DEFINE_FIFO_NAME

!!define DEFINE_FIFO_NAME "/var/run/kamailio/kamailio_rpc_fifo"

!!endif   

 

 

modparam("jsonrpcs", "pretty_format", 1)

modparam("jsonrpcs", "transport", 2)

modparam("jsonrpcs", "fifo_name", DEFINE_FIFO_NAME)

modparam("jsonrpcs", "fifo_mode", 0755)

modparam("jsonrpcs", "fifo_group", "kamailio")

modparam("jsonrpcs", "fifo_user", "kamailio")

 

 

kamailio doesn’t start. It reports ‘Permission denied’ :

 

Mar 24 17:31:21 localhost /usr/sbin/kamailio[1138]: ERROR: jsonrpcs 
[jsonrpcs_fifo.c:144]: jsonrpc_init_fifo_server(): Can't create FIFO: 
Permission denied (mode=493)

Mar 24 17:31:21 localhost /usr/sbin/kamailio[1138]: CRITICAL: jsonrpcs 
[jsonrpcs_fifo.c:489]: jsonrpc_fifo_process(): failed to init jsonrpc fifo 
server

Mar 24 17:31:21 localhost /usr/sbin/kamailio[1120]: ALERT:  [main.c:741]: 
handle_sigs(): child process 1138 exited normally, status=255

Mar 24 17:31:21 localhost /usr/sbin/kamailio[1130]: DEBUG:  
[core/sr_module.c:920]: init_mod_child(): rank 4: tm

Mar 24 17:31:21 localhost /usr/sbin/kamailio[1137]: DEBUG:  
[core/sr_module.c:920]: init_mod_child(): rank -1: tm

Mar 24 17:31:21 localhost /usr/sbin/kamailio[1127]: DEBUG: htable 
[htable.c:226]: child_init(): rank is (1)

Mar 24 17:31:21 localhost /usr/sbin/kamailio[1120]: INFO:  [main.c:759]: 
handle_sigs(): terminating due to SIGCHLD

Mar 24 17:31:21 localhost /usr/sbin/kamailio[1139]: DEBUG:  
[core/sr_module.c:920]: init_mod_child(): rank -2: kex

Mar 24 17:31:21 localhost /usr/sbin/kamailio[1130]: DEBUG: tm [callid.c:137]: 
child_init_callid(): callid: '15b1f0d

Re: [SR-Users] Doubt about MI Datagram module in Kamailio 5

[Ginhoux, Patrick]

Hi,

 

I had the same issue for the MI_FIFO.

 

Both are replaced the jsonrpcs module. See the 5.0 changes here : 
http://www.kamailio.org/wiki/install/upgrade/4.4.x-to-5.0.0 

Modules

Removed Modules

mi_datagram

The jsonrpcs module can be used instead to execute RPC commands over datagram 
sockets (unix socket file, IPv4 or IPv6). 

mi_fifo

The jsonrpcs module can be used instead to execute RPC commands over a FIFO 
file. 

Cordialement

Patrick GINHOUX

 

De : sr-users [mailto:sr-users-boun...@lists.sip-router.org] De la part de 
Albert Petit
Envoyé : lundi 3 avril 2017 13:27
À : SIP Router - Kamailio (OpenSER) and SIP Express Router (SER) - Users 
Mailing List 
Objet : [SR-Users] Doubt about MI Datagram module in Kamailio 5

 

Dear list,

 

I've recently upgraded to Kamailio 5 in order to avoid issue parsing SDP 
multipart bodies which think are fixed in the update ( - symbol rejected in 
content type) .

 

I could upgrade without issues from my kamailio 4 dev deployment but i cannot 
load anymore  MI_Datagram module (seems not present in Kamailio 5 , MI Datagram 
module i refer to: 

http://www.kamailio.org/docs/modules/4.3.x/modules/mi_datagram.html )

 

Can i use MI Datagram module still in Kamailio 5 ?

Thanks

Albert



smime.p7s
Description: S/MIME cryptographic signature
___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] RPCFIFOPATH / DEFINE_FIFO_NAME settings problem

[Ginhoux, Patrick]

Hi,

I continue to investigate on this area.

I’m thinking that there are some security settings on the FS /var/, and I’m 
looking for if we have the rights to change it (I work for a project and don’t 
have all the ability to change some settings without agreement).

I’ll update you later tomorrow.

Cordialement
Patrick GINHOUX

De : Daniel-Constantin Mierla [mailto:mico...@gmail.com]
Envoyé : lundi 27 mars 2017 15:28
À : Ginhoux, Patrick ; Kamailio (SER) - Users 
Mailing List 
Objet : Re: [SR-Users] RPCFIFOPATH / DEFINE_FIFO_NAME settings problem


Hello,

as recently as last week, someone encountered an file access problem while 
installing Siremis, which is using also some temporary files in /var/, even it 
was granting provileges via chown and chmod. All went fine after disabling 
selinux. It was on a centos.

I am not saying it is the same, but it could, so try without centos to see if 
the issue persists.

Cheers,
Daniel


On 27/03/2017 15:10, Ginhoux, Patrick wrote:
Hi,

This is the RHEL 7.1 distro, and there is use of selinux, apparmor or other 
tools.

Are you meaning that the /var/run/ folder would be secured more than other 
folders?

Cordialement
Patrick GINHOUX

De : sr-users [mailto:sr-users-boun...@lists.sip-router.org] De la part de 
Daniel-Constantin Mierla
Envoyé : lundi 27 mars 2017 13:52
À : Kamailio (SER) - Users Mailing List 
<mailto:sr-users@lists.sip-router.org>
Objet : Re: [SR-Users] RPCFIFOPATH / DEFINE_FIFO_NAME settings problem


Hello,

kamailio should attempt to create the /var/run/kamailio folder if the 
application is run with enough privileges. However, some operating systems add 
more constraints on top of the execution user.

What is your OS distro? Do you have selinux, apparmor or other similar tools 
enabled?

Cheers,
Daniel

On 24/03/2017 17:52, Ginhoux, Patrick wrote:
In my ‘kamctlrc’ file :

## path to FIFO file for engine RPCFIFO
RPCFIFOPATH="/var/run/kamailio/kamailio_rpc_fifo"
#RPCFIFOPATH="/tmp/kamailio_rpc_fifo"

In my ‘kamailio.cfg’ :

!!ifndef DEFINE_FIFO_NAME
!!define DEFINE_FIFO_NAME "/var/run/kamailio/kamailio_rpc_fifo"
!!endif


modparam("jsonrpcs", "pretty_format", 1)
modparam("jsonrpcs", "transport", 2)
modparam("jsonrpcs", "fifo_name", DEFINE_FIFO_NAME)
modparam("jsonrpcs", "fifo_mode", 0755)
modparam("jsonrpcs", "fifo_group", "kamailio")
modparam("jsonrpcs", "fifo_user", "kamailio")


kamailio doesn’t start. It reports ‘Permission denied’ :

Mar 24 17:31:21 localhost /usr/sbin/kamailio[1138]: ERROR: jsonrpcs 
[jsonrpcs_fifo.c:144]: jsonrpc_init_fifo_server(): Can't create FIFO: 
Permission denied (mode=493)
Mar 24 17:31:21 localhost /usr/sbin/kamailio[1138]: CRITICAL: jsonrpcs 
[jsonrpcs_fifo.c:489]: jsonrpc_fifo_process(): failed to init jsonrpc fifo 
server
Mar 24 17:31:21 localhost /usr/sbin/kamailio[1120]: ALERT:  [main.c:741]: 
handle_sigs(): child process 1138 exited normally, status=255
Mar 24 17:31:21 localhost /usr/sbin/kamailio[1130]: DEBUG:  
[core/sr_module.c:920]: init_mod_child(): rank 4: tm
Mar 24 17:31:21 localhost /usr/sbin/kamailio[1137]: DEBUG:  
[core/sr_module.c:920]: init_mod_child(): rank -1: tm
Mar 24 17:31:21 localhost /usr/sbin/kamailio[1127]: DEBUG: htable 
[htable.c:226]: child_init(): rank is (1)
Mar 24 17:31:21 localhost /usr/sbin/kamailio[1120]: INFO:  [main.c:759]: 
handle_sigs(): terminating due to SIGCHLD
Mar 24 17:31:21 localhost /usr/sbin/kamailio[1139]: DEBUG:  
[core/sr_module.c:920]: init_mod_child(): rank -2: kex
Mar 24 17:31:21 localhost /usr/sbin/kamailio[1130]: DEBUG: tm [callid.c:137]: 
child_init_callid(): callid: 
'15b1f0d63a718465-1130@129.227.83.108<mailto:15b1f0d63a718465-1130@129.227.83.108>'
Mar 24 17:31:21 localhost /usr/sbin/kamailio[1137]: DEBUG: tm [callid.c:137]: 
child_init_callid(): callid: 
'15b1f0d63a718465-1137@129.227.83.108<mailto:15b1f0d63a718465-1137@129.227.83.108>'
Mar 24 17:31:21 localhost /usr/sbin/kamailio[1127]: DEBUG:  
[core/action.c:1656]: run_child_one_init_route(): attempting to run 
event_route[core:worker-one-init]
Mar 24 17:31:21 localhost /usr/sbin/kamailio[1136]: INFO:  [main.c:814]: 
sig_usr(): signal 15 received
Mar 24 17:31:21 localhost /usr/sbin/kamailio[1135]: INFO:  [main.c:814]: 
sig_usr(): signal 15 received
Mar 24 17:31:21 localhost /usr/sbin/kamailio[1134]: INFO:  [main.c:814]: 
sig_usr(): signal 15 received
Mar 24 17:31:21 localhost /usr/sbin/kamailio[1133]: INFO:  [main.c:814]: 
sig_usr(): signal 15 received
Mar 24 17:31:21 localhost /usr/sbin/kamailio[1132]: INFO:  [main.c:814]: 
sig_usr(): signal 15 received
Mar 24 17:31:21 localhost /usr/sbin/kamailio[1131]: INFO:  [main.c:814]: 
sig_usr(): signal 15 received
Mar 24 17:31:21 localhost /usr/sbin/kamailio[1129]: INFO:  [main.c:814]: 
sig_usr(): signal 15 received
Mar 24 17:31:21 localhost /usr/sb

Re: [SR-Users] Important problem with this test : if ($var(i:maxRangeInx)==$null)

[Ginhoux, Patrick]

Hi,

Great thanks to answer so quickly.

I tested the $vn ….in the 5.0.x script instead of $var…., and the results look 
good.

So I have to review the entire script to change all the ‘$var…. == $null’ 
entries to ‘$vn…. == $null’. I assume I have to do the same for the ‘!= $null” 
case. Am I correct ?

Now regarding my old kamailio 3.3.1 script, I notice that the ‘$var…. == $null’ 
works fine but no more with kamailio 5.0.x . So It’s something that has changed 
more recently. The 3.3.1 cookbooks doesn’t reference a ‘$vn’ variable.
But may be I misread it.

So if you have comments on this for my understanding, that would be fine.

Cordialement
Patrick GINHOUX

De : sr-users [mailto:sr-users-boun...@lists.sip-router.org] De la part de 
Daniel-Constantin Mierla
Envoyé : lundi 27 mars 2017 15:31
À : Kamailio (SER) - Users Mailing List 
Objet : Re: [SR-Users] Important problem with this test : if 
($var(i:maxRangeInx)==$null)


Hello,

$var(...) don't hold null values, they start initialed to 0 and they are reset 
to 0 (when assigning $null to them) -- this is the design from the beginning 
which brings benefits in many situation when one doesn't get a chance to init.

If you want a similar variable that works with null, then use $vn(...):

  - 
https://www.kamailio.org/wiki/cookbooks/5.0.x/pseudovariables#vn_name_-_private_memory_variables_null

Cheers,
Daniel

On 27/03/2017 15:22, Ginhoux, Patrick wrote:
Hi,

I’m continue my job to ‘migrate’ my 3.3.1 kamailio.cfg script on a RHEL 6.2 
server to the 5.0.x kamailio version on a RHEL 7.1 server, and I encounter a 
major problem with the ‘== $null’ test in the script.

My original script (3.3.1) contains this sequence :

$var(i:rangeInx)=0;
$var(i:maxRangeInx) = $sht(mbxrangeHash=>"maxrange");
xlog(" imbxRangeInx value before test : '$var(i:maxRangeInx)' ");
if ($var(i:maxRangeInx)==$null) {
$var(i:maxRangeInx)=99;
}
xlog(" imbxRangeInx after test : '$var(i:maxRangeInx)' ");

==> The results are :
imbxRangeInx value before test : ‘0’
imbxRangeInx value after test : ‘99’

I run the same script on my new server and I get ‘0’ before and after the test.

I attempted another kind of test to try to figure out where the problem is. So 
I write the simple test (with kamailio 5.0.x) :

$var(i:rangeInx)=0;
$var(i:maxRangeInx) = $sht(mbxrangeHash=>"maxrange");
$var(toto) = $null;
if ($var(toto) == $null)
xlog ("toto true");
else
xlog ("toto false");

The result I got is always ‘toto false’.

So it appears to me that the test ‘== $null’ doens’ that gives a good result 
with kamailio 3.3.1, doesn’t return the same with kamailio 5.0.x.

That is a major issue for me and it let me confused about the possibility to 
move to kamailio 5.0.x.

Have people an idea / explanation, why this issue ?

Cordialement
Patrick GINHOUX





___

SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list

sr-users@lists.sip-router.org<mailto:sr-users@lists.sip-router.org>

http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users



--

Daniel-Constantin Mierla

www.twitter.com/miconda<http://www.twitter.com/miconda> -- 
www.linkedin.com/in/miconda<http://www.linkedin.com/in/miconda>

Kamailio Advanced Training - Mar 6-8 (Europe) and Mar 20-22 (USA) - 
www.asipto.com<http://www.asipto.com>

Kamailio World Conference - May 8-10, 2017 - 
www.kamailioworld.com<http://www.kamailioworld.com>
___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

[SR-Users] Important problem with this test : if ($var(i:maxRangeInx)==$null)

[Ginhoux, Patrick]

Hi,

I'm continue my job to 'migrate' my 3.3.1 kamailio.cfg script on a RHEL 6.2 
server to the 5.0.x kamailio version on a RHEL 7.1 server, and I encounter a 
major problem with the '== $null' test in the script.

My original script (3.3.1) contains this sequence :

$var(i:rangeInx)=0;
$var(i:maxRangeInx) = $sht(mbxrangeHash=>"maxrange");
xlog(" imbxRangeInx value before test : '$var(i:maxRangeInx)' ");
if ($var(i:maxRangeInx)==$null) {
$var(i:maxRangeInx)=99;
}
xlog(" imbxRangeInx after test : '$var(i:maxRangeInx)' ");

==> The results are :
imbxRangeInx value before test : '0'
imbxRangeInx value after test : '99'

I run the same script on my new server and I get '0' before and after the test.

I attempted another kind of test to try to figure out where the problem is. So 
I write the simple test (with kamailio 5.0.x) :

$var(i:rangeInx)=0;
$var(i:maxRangeInx) = $sht(mbxrangeHash=>"maxrange");
$var(toto) = $null;
if ($var(toto) == $null)
xlog ("toto true");
else
xlog ("toto false");

The result I got is always 'toto false'.

So it appears to me that the test '== $null' doens' that gives a good result 
with kamailio 3.3.1, doesn't return the same with kamailio 5.0.x.

That is a major issue for me and it let me confused about the possibility to 
move to kamailio 5.0.x.

Have people an idea / explanation, why this issue ?

Cordialement
Patrick GINHOUX

___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] RPCFIFOPATH / DEFINE_FIFO_NAME settings problem

[Ginhoux, Patrick]

Hi,

This is the RHEL 7.1 distro, and there is use of selinux, apparmor or other 
tools.

Are you meaning that the /var/run/ folder would be secured more than other 
folders?

Cordialement
Patrick GINHOUX

De : sr-users [mailto:sr-users-boun...@lists.sip-router.org] De la part de 
Daniel-Constantin Mierla
Envoyé : lundi 27 mars 2017 13:52
À : Kamailio (SER) - Users Mailing List 
Objet : Re: [SR-Users] RPCFIFOPATH / DEFINE_FIFO_NAME settings problem


Hello,

kamailio should attempt to create the /var/run/kamailio folder if the 
application is run with enough privileges. However, some operating systems add 
more constraints on top of the execution user.

What is your OS distro? Do you have selinux, apparmor or other similar tools 
enabled?

Cheers,
Daniel

On 24/03/2017 17:52, Ginhoux, Patrick wrote:
In my ‘kamctlrc’ file :

## path to FIFO file for engine RPCFIFO
RPCFIFOPATH="/var/run/kamailio/kamailio_rpc_fifo"
#RPCFIFOPATH="/tmp/kamailio_rpc_fifo"

In my ‘kamailio.cfg’ :

!!ifndef DEFINE_FIFO_NAME
!!define DEFINE_FIFO_NAME "/var/run/kamailio/kamailio_rpc_fifo"
!!endif


modparam("jsonrpcs", "pretty_format", 1)
modparam("jsonrpcs", "transport", 2)
modparam("jsonrpcs", "fifo_name", DEFINE_FIFO_NAME)
modparam("jsonrpcs", "fifo_mode", 0755)
modparam("jsonrpcs", "fifo_group", "kamailio")
modparam("jsonrpcs", "fifo_user", "kamailio")


kamailio doesn’t start. It reports ‘Permission denied’ :

Mar 24 17:31:21 localhost /usr/sbin/kamailio[1138]: ERROR: jsonrpcs 
[jsonrpcs_fifo.c:144]: jsonrpc_init_fifo_server(): Can't create FIFO: 
Permission denied (mode=493)
Mar 24 17:31:21 localhost /usr/sbin/kamailio[1138]: CRITICAL: jsonrpcs 
[jsonrpcs_fifo.c:489]: jsonrpc_fifo_process(): failed to init jsonrpc fifo 
server
Mar 24 17:31:21 localhost /usr/sbin/kamailio[1120]: ALERT:  [main.c:741]: 
handle_sigs(): child process 1138 exited normally, status=255
Mar 24 17:31:21 localhost /usr/sbin/kamailio[1130]: DEBUG:  
[core/sr_module.c:920]: init_mod_child(): rank 4: tm
Mar 24 17:31:21 localhost /usr/sbin/kamailio[1137]: DEBUG:  
[core/sr_module.c:920]: init_mod_child(): rank -1: tm
Mar 24 17:31:21 localhost /usr/sbin/kamailio[1127]: DEBUG: htable 
[htable.c:226]: child_init(): rank is (1)
Mar 24 17:31:21 localhost /usr/sbin/kamailio[1120]: INFO:  [main.c:759]: 
handle_sigs(): terminating due to SIGCHLD
Mar 24 17:31:21 localhost /usr/sbin/kamailio[1139]: DEBUG:  
[core/sr_module.c:920]: init_mod_child(): rank -2: kex
Mar 24 17:31:21 localhost /usr/sbin/kamailio[1130]: DEBUG: tm [callid.c:137]: 
child_init_callid(): callid: 
'15b1f0d63a718465-1130@129.227.83.108<mailto:15b1f0d63a718465-1130@129.227.83.108>'
Mar 24 17:31:21 localhost /usr/sbin/kamailio[1137]: DEBUG: tm [callid.c:137]: 
child_init_callid(): callid: 
'15b1f0d63a718465-1137@129.227.83.108<mailto:15b1f0d63a718465-1137@129.227.83.108>'
Mar 24 17:31:21 localhost /usr/sbin/kamailio[1127]: DEBUG:  
[core/action.c:1656]: run_child_one_init_route(): attempting to run 
event_route[core:worker-one-init]
Mar 24 17:31:21 localhost /usr/sbin/kamailio[1136]: INFO:  [main.c:814]: 
sig_usr(): signal 15 received
Mar 24 17:31:21 localhost /usr/sbin/kamailio[1135]: INFO:  [main.c:814]: 
sig_usr(): signal 15 received
Mar 24 17:31:21 localhost /usr/sbin/kamailio[1134]: INFO:  [main.c:814]: 
sig_usr(): signal 15 received
Mar 24 17:31:21 localhost /usr/sbin/kamailio[1133]: INFO:  [main.c:814]: 
sig_usr(): signal 15 received
Mar 24 17:31:21 localhost /usr/sbin/kamailio[1132]: INFO:  [main.c:814]: 
sig_usr(): signal 15 received
Mar 24 17:31:21 localhost /usr/sbin/kamailio[1131]: INFO:  [main.c:814]: 
sig_usr(): signal 15 received
Mar 24 17:31:21 localhost /usr/sbin/kamailio[1129]: INFO:  [main.c:814]: 
sig_usr(): signal 15 received
Mar 24 17:31:21 localhost /usr/sbin/kamailio[1128]: INFO:  [main.c:814]: 
sig_usr(): signal 15 received
Mar 24 17:31:21 localhost /usr/sbin/kamailio[1120]: ERROR: ctl [ctl.c:387]: 
mod_destroy(): ERROR: ctl: could not delete unix socket 
/var/run/kamailio//kamailio_ctl: Permission denied (13)
Mar 24 17:31:21 localhost /usr/sbin/kamailio[1120]: ERROR: jsonrpcs 
[jsonrpcs_fifo.c:595]: jsonrpc_fifo_destroy(): FIFO stat failed: Permission 
denied

If I replace the values in the 2 files as appropriate :

In the ‘kamctlrc” to RPCFIFOPATH="/tmp/kamailio_rpc_fifo"

In the ‘kamailio.cfg” to !!define DEFINE_FIFO_NAME "/tmp/kamailio_rpc_fifo"

Then kamailo starts :

[root@vm-vse02-siprouter1 ~]# ps -ef |grep kam
kamailio  1235 1  0 17:37 ?00:00:00 /usr/sbin/kamailio -P 
/var/run/kamailio.pid -m 1024 -M 8 -u kamailio -g kamailio
kamailio  1236  1235  0 17:37 ?00:00:00 /usr/sbin/kamailio -P 
/var/run/kamailio.pid -m 1024 -M 8 -u kamailio -g kamailio
kamailio  1237  1235  0 17:37 ?00:00:00 /usr/sbin/kamailio -P 
/var/r

[SR-Users] RPCFIFOPATH / DEFINE_FIFO_NAME settings problem

[Ginhoux, Patrick]

In my 'kamctlrc' file :

## path to FIFO file for engine RPCFIFO
RPCFIFOPATH="/var/run/kamailio/kamailio_rpc_fifo"
#RPCFIFOPATH="/tmp/kamailio_rpc_fifo"

In my 'kamailio.cfg' :

!!ifndef DEFINE_FIFO_NAME
!!define DEFINE_FIFO_NAME "/var/run/kamailio/kamailio_rpc_fifo"
!!endif


modparam("jsonrpcs", "pretty_format", 1)
modparam("jsonrpcs", "transport", 2)
modparam("jsonrpcs", "fifo_name", DEFINE_FIFO_NAME)
modparam("jsonrpcs", "fifo_mode", 0755)
modparam("jsonrpcs", "fifo_group", "kamailio")
modparam("jsonrpcs", "fifo_user", "kamailio")


kamailio doesn't start. It reports 'Permission denied' :

Mar 24 17:31:21 localhost /usr/sbin/kamailio[1138]: ERROR: jsonrpcs 
[jsonrpcs_fifo.c:144]: jsonrpc_init_fifo_server(): Can't create FIFO: 
Permission denied (mode=493)
Mar 24 17:31:21 localhost /usr/sbin/kamailio[1138]: CRITICAL: jsonrpcs 
[jsonrpcs_fifo.c:489]: jsonrpc_fifo_process(): failed to init jsonrpc fifo 
server
Mar 24 17:31:21 localhost /usr/sbin/kamailio[1120]: ALERT:  [main.c:741]: 
handle_sigs(): child process 1138 exited normally, status=255
Mar 24 17:31:21 localhost /usr/sbin/kamailio[1130]: DEBUG:  
[core/sr_module.c:920]: init_mod_child(): rank 4: tm
Mar 24 17:31:21 localhost /usr/sbin/kamailio[1137]: DEBUG:  
[core/sr_module.c:920]: init_mod_child(): rank -1: tm
Mar 24 17:31:21 localhost /usr/sbin/kamailio[1127]: DEBUG: htable 
[htable.c:226]: child_init(): rank is (1)
Mar 24 17:31:21 localhost /usr/sbin/kamailio[1120]: INFO:  [main.c:759]: 
handle_sigs(): terminating due to SIGCHLD
Mar 24 17:31:21 localhost /usr/sbin/kamailio[1139]: DEBUG:  
[core/sr_module.c:920]: init_mod_child(): rank -2: kex
Mar 24 17:31:21 localhost /usr/sbin/kamailio[1130]: DEBUG: tm [callid.c:137]: 
child_init_callid(): callid: '15b1f0d63a718465-1130@129.227.83.108'
Mar 24 17:31:21 localhost /usr/sbin/kamailio[1137]: DEBUG: tm [callid.c:137]: 
child_init_callid(): callid: '15b1f0d63a718465-1137@129.227.83.108'
Mar 24 17:31:21 localhost /usr/sbin/kamailio[1127]: DEBUG:  
[core/action.c:1656]: run_child_one_init_route(): attempting to run 
event_route[core:worker-one-init]
Mar 24 17:31:21 localhost /usr/sbin/kamailio[1136]: INFO:  [main.c:814]: 
sig_usr(): signal 15 received
Mar 24 17:31:21 localhost /usr/sbin/kamailio[1135]: INFO:  [main.c:814]: 
sig_usr(): signal 15 received
Mar 24 17:31:21 localhost /usr/sbin/kamailio[1134]: INFO:  [main.c:814]: 
sig_usr(): signal 15 received
Mar 24 17:31:21 localhost /usr/sbin/kamailio[1133]: INFO:  [main.c:814]: 
sig_usr(): signal 15 received
Mar 24 17:31:21 localhost /usr/sbin/kamailio[1132]: INFO:  [main.c:814]: 
sig_usr(): signal 15 received
Mar 24 17:31:21 localhost /usr/sbin/kamailio[1131]: INFO:  [main.c:814]: 
sig_usr(): signal 15 received
Mar 24 17:31:21 localhost /usr/sbin/kamailio[1129]: INFO:  [main.c:814]: 
sig_usr(): signal 15 received
Mar 24 17:31:21 localhost /usr/sbin/kamailio[1128]: INFO:  [main.c:814]: 
sig_usr(): signal 15 received
Mar 24 17:31:21 localhost /usr/sbin/kamailio[1120]: ERROR: ctl [ctl.c:387]: 
mod_destroy(): ERROR: ctl: could not delete unix socket 
/var/run/kamailio//kamailio_ctl: Permission denied (13)
Mar 24 17:31:21 localhost /usr/sbin/kamailio[1120]: ERROR: jsonrpcs 
[jsonrpcs_fifo.c:595]: jsonrpc_fifo_destroy(): FIFO stat failed: Permission 
denied

If I replace the values in the 2 files as appropriate :

In the 'kamctlrc" to RPCFIFOPATH="/tmp/kamailio_rpc_fifo"

In the 'kamailio.cfg" to !!define DEFINE_FIFO_NAME "/tmp/kamailio_rpc_fifo"

Then kamailo starts :

[root@vm-vse02-siprouter1 ~]# ps -ef |grep kam
kamailio  1235 1  0 17:37 ?00:00:00 /usr/sbin/kamailio -P 
/var/run/kamailio.pid -m 1024 -M 8 -u kamailio -g kamailio
kamailio  1236  1235  0 17:37 ?00:00:00 /usr/sbin/kamailio -P 
/var/run/kamailio.pid -m 1024 -M 8 -u kamailio -g kamailio
kamailio  1237  1235  0 17:37 ?00:00:00 /usr/sbin/kamailio -P 
/var/run/kamailio.pid -m 1024 -M 8 -u kamailio -g kamailio
kamailio  1238  1235  0 17:37 ?00:00:00 /usr/sbin/kamailio -P 
/var/run/kamailio.pid -m 1024 -M 8 -u kamailio -g kamailio
kamailio  1239  1235  0 17:37 ?00:00:00 /usr/sbin/kamailio -P 
/var/run/kamailio.pid -m 1024 -M 8 -u kamailio -g kamailio
kamailio  1240  1235  0 17:37 ?00:00:00 /usr/sbin/kamailio -P 
/var/run/kamailio.pid -m 1024 -M 8 -u kamailio -g kamailio
kamailio  1241  1235  0 17:37 ?00:00:00 /usr/sbin/kamailio -P 
/var/run/kamailio.pid -m 1024 -M 8 -u kamailio -g kamailio
kamailio  1242  1235  0 17:37 ?00:00:00 /usr/sbin/kamailio -P 
/var/run/kamailio.pid -m 1024 -M 8 -u kamailio -g kamailio
kamailio  1243  1235  0 17:37 ?00:00:00 /usr/sbin/kamailio -P 
/var/run/kamailio.pid -m 1024 -M 8 -u kamailio -g kamailio
kamailio  1244  1235  0 17:37 ?00:00:00 /usr/sbin/kamailio -P 
/var/run/kamailio.pid -m 1024 -M 8 -u kamailio -g kamailio
kamailio  1245  1235  0 17:37 ?00:00:00 /usr/sbin/kamailio -P 
/var/run/kamailio.pid -m 1024 -M 8 -u kamailio -g kamailio
kamailio  1246  1235  0 17:37 ?0

Re: [SR-Users] ht_db_load_table(): key type must be string (type=6)

[Ginhoux, Patrick]

Hi Daniel,

I think that this key type problem has to do with the type of ‘text’used for 
some fields in my myqsl db.

By changing the type from ‘text’ to varchar(256), the problem goes away.

It is for sure just a workaround, that is ok for me for the moment, but in the 
case people would need to have text, we can get this problem back.

I hope this help.

Cordialement
Patrick GINHOUX

De : Ginhoux, Patrick
Envoyé : mardi 21 mars 2017 13:29
À : Kamailio (SER) - Users Mailing List 
Objet : RE: [SR-Users] ht_db_load_table(): key type must be string (type=6)

Hi,

Below the structure of the properties table :

mysql> show create table properties;
+++
| Table  | Create Table 


  |
+++
| properties | CREATE TABLE `properties` (
  `id` int(6) unsigned NOT NULL AUTO_INCREMENT COMMENT 'UniqueID',
  `key_name` text NOT NULL,
  `key_value` text NOT NULL,
  `value_type` int(1) NOT NULL,
  `key_type` int(1) NOT NULL,
  PRIMARY KEY (`id`)
) ENGINE=InnoDB AUTO_INCREMENT=10001 DEFAULT CHARSET=latin1 |
+++
1 row in set (0.02 sec)

Cordialement
Patrick GINHOUX

De : sr-users [mailto:sr-users-boun...@lists.sip-router.org] De la part de 
Daniel-Constantin Mierla
Envoyé : mardi 21 mars 2017 13:25
À : Kamailio (SER) - Users Mailing List 
mailto:sr-users@lists.sip-router.org>>
Objet : Re: [SR-Users] ht_db_load_table(): key type must be string (type=6)


Hello,

can you give the structure of the table properties (show create table ...)?

Cheers,

Daniel

March 21, 2017 11:30 AM, "Ginhoux, Patrick" 
mailto:%22Ginhoux,%20patrick%22%20%3cpatrick.ginh...@fr.unisys.com%3e>>
 wrote:

Hi,

A second update for people who started to look at this issue.

I have identified the real cause of the problem by looking more in the kamailio 
log with the debug traces. I discover that it is related to the load of the 
properties table in the htable.

I have the following entries in my mysql db :

+---++-++--+

| id | key_name | key_value | value_type | key_type |

+---++-++--+

| 0 | VERSION | 120104-1734 | 0 | 0 |

| 1 | mmm-retry | 408=Y;502=Y;503=Y | 0 | 0 |

| 2 | mgcf-retry | 408=Y;502=Y;503=Y | 0 | 0 |

| 3 | max-mmm-retry | 2 | 0 | 0 |

| 4 | max-mgcf-retry | 2 | 0 | 0 |

| 5 | target-uri | mgcf=10.10.10.10;mmm-legacy=20.20.20.10;mmm=20.20.20.20 | 0 
| 0 |

| 6 | pike-status | 503 Service Overload | 0 | 0 |

| 7 | mgcf-path | 99 | 0 | 0 |

| 16 | mmm-nodeid | OPMMMS1VSE01=1;OPMMMS1VSE02=2 | 0 | 0 |

| 17 | mmm-node-path | 1=1;2=2 | 0 | 0 |

+---++-++--+

In the kamailio.cfg, the << modparam("htable", "htable", 
"propertiesHash=>size=4;dbtable=properties;") >> command causes the load of the 
above table in the htable.

In the log we can see, that the load is done in the alphabetic order of the 
key_name and it fails to load the last entry “VERSION” :

Mar 21 10:25:28 localhost /usr/sbin/kamailio[5784]: DEBUG:  
[db_val.c:169]: db_str2val(): converting BLOB [VERSION]

Mar 21 10:25:28 localhost /usr/sbin/kamailio[5784]: DEBUG:  
[db_val.c:74]: db_str2val(): converting INT [0]

Mar 21 10:25:28 localhost /usr/sbin/kamailio[5784]: DEBUG:  
[db_val.c:74]: db_str2val(): converting INT [0]

Mar 21 10:25:28 localhost /usr/sbin/kamailio[5784]: DEBUG:  
[db_val.c:169]: db_str2val(): converting BLOB [120104-1734]

Mar 21 10:25:28 localhost /usr/sbin/kamailio[5784]: ERROR: htable 
[ht_db.c:276]: ht_db_load_table(): key type must be string (type=6)

If I add a new entry named “W”, then the failure occur

Re: [SR-Users] Question on the debug change level command with 5.0.x

[Ginhoux, Patrick]

Hi,

All right, I’ll remove this.

Thanks again for your help.

I can close this ticket.

Cordialement
Patrick GINHOUX

De : sr-users [mailto:sr-users-boun...@lists.sip-router.org] De la part de 
Federico Cabiddu
Envoyé : jeudi 23 mars 2017 20:46
À : SIP Router - Kamailio (OpenSER) and SIP Express Router (SER) - Users 
Mailing List 
Objet : Re: [SR-Users] Question on the debug change level command with 5.0.x

No, you don't. The debugger module, among other things, allows​ to set the 
debug level per module.

Regards,

Federico



On 23 Mar 2017 6:31 pm, "Ginhoux, Patrick" 
mailto:patrick.ginh...@fr.unisys.com>> wrote:
Hi,

Thanks you so much; it works fine as expected.

Now have I to keep the ‘debugger’ module lines in my config ?

Cordialement
Patrick GINHOUX

De : sr-users 
[mailto:sr-users-boun...@lists.sip-router.org<mailto:sr-users-boun...@lists.sip-router.org>]
 De la part de Federico Cabiddu
Envoyé : jeudi 23 mars 2017 17:38
À : Kamailio (SER) - Users Mailing List 
mailto:sr-users@lists.sip-router.org>>
Objet : Re: [SR-Users] Question on the debug change level command with 5.0.x

Hi,
you have to load the cfg_rpc module 
(http://www.kamailio.org/docs/modules/5.0.x/modules/cfg_rpc.html). Then you can 
run

kamcmd cfg.set_now_int core debug .

Regards,

Federico

On Thu, Mar 23, 2017 at 5:24 PM, Ginhoux, Patrick 
mailto:patrick.ginh...@fr.unisys.com>> wrote:
Hi,

Previously, in my kamailio.cfg 3.3.1, the debug level is set using the ‘debug’ 
option.
Then with the MI_FIFO module it was simple to change debug level on the flight 
using the simple command ‘kamctl fifo debug ’.

Moving to kamailio 5.0.x, there is no more MI_FIFO module. In the kamailio.cfg, 
I still have the ‘debug’ option set; so I’m looking for the command to use to 
change the debug level.

I look at the debugger module that seems the solution. So I add the following 
lines in y script:

debug=4

loadmodule "debugger.so"

modparam("debugger", "log_level", 1)
modparam("debugger", "mod_hash_size", 5)
modparam("debugger", "mod_level_mode", 1)

Then I try to use the following commands :

This one retrieves the debug level set by the debug=4) :
[root@vm-vse02-siprouter1 kamailio]# kamcmd dbg.get_mod_level core
4

This one changed the debug level for the core module
[root@vm-vse02-siprouter1 kamailio]# kamcmd dbg.set_mod_level core 2
200 ok

Same commands can be used for each of the module loaded:

[root@vm-vse02-siprouter1 kamailio]# kamcmd dbg.get_mod_level tm
4
[root@vm-vse02-siprouter1 kamailio]# kamcmd dbg.set_mod_level tm 2
200 ok

[root@vm-vse02-siprouter1 kamailio]# kamcmd dbg.get_mod_level dispatcher
4
[root@vm-vse02-siprouter1 kamailio]# kamcmd dbg.set_mod_level dispatcher 2
200 ok

Each command only applies to a specific module.

I don’t find a ‘global’ command that I could use in the same manner as the old 
‘kamctl fifo debug’ command.

Is there something I missed in my config ?

Cordialement
Patrick GINHOUX


___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org<mailto:sr-users@lists.sip-router.org>
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users


___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org<mailto:sr-users@lists.sip-router.org>
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] Question on the debug change level command with 5.0.x

[Ginhoux, Patrick]

Hi,

Thanks you so much; it works fine as expected.

Now have I to keep the ‘debugger’ module lines in my config ?

Cordialement
Patrick GINHOUX

De : sr-users [mailto:sr-users-boun...@lists.sip-router.org] De la part de 
Federico Cabiddu
Envoyé : jeudi 23 mars 2017 17:38
À : Kamailio (SER) - Users Mailing List 
Objet : Re: [SR-Users] Question on the debug change level command with 5.0.x

Hi,
you have to load the cfg_rpc module 
(http://www.kamailio.org/docs/modules/5.0.x/modules/cfg_rpc.html). Then you can 
run

kamcmd cfg.set_now_int core debug .

Regards,

Federico

On Thu, Mar 23, 2017 at 5:24 PM, Ginhoux, Patrick 
mailto:patrick.ginh...@fr.unisys.com>> wrote:
Hi,

Previously, in my kamailio.cfg 3.3.1, the debug level is set using the ‘debug’ 
option.
Then with the MI_FIFO module it was simple to change debug level on the flight 
using the simple command ‘kamctl fifo debug ’.

Moving to kamailio 5.0.x, there is no more MI_FIFO module. In the kamailio.cfg, 
I still have the ‘debug’ option set; so I’m looking for the command to use to 
change the debug level.

I look at the debugger module that seems the solution. So I add the following 
lines in y script:

debug=4

loadmodule "debugger.so"

modparam("debugger", "log_level", 1)
modparam("debugger", "mod_hash_size", 5)
modparam("debugger", "mod_level_mode", 1)

Then I try to use the following commands :

This one retrieves the debug level set by the debug=4) :
[root@vm-vse02-siprouter1 kamailio]# kamcmd dbg.get_mod_level core
4

This one changed the debug level for the core module
[root@vm-vse02-siprouter1 kamailio]# kamcmd dbg.set_mod_level core 2
200 ok

Same commands can be used for each of the module loaded:

[root@vm-vse02-siprouter1 kamailio]# kamcmd dbg.get_mod_level tm
4
[root@vm-vse02-siprouter1 kamailio]# kamcmd dbg.set_mod_level tm 2
200 ok

[root@vm-vse02-siprouter1 kamailio]# kamcmd dbg.get_mod_level dispatcher
4
[root@vm-vse02-siprouter1 kamailio]# kamcmd dbg.set_mod_level dispatcher 2
200 ok

Each command only applies to a specific module.

I don’t find a ‘global’ command that I could use in the same manner as the old 
‘kamctl fifo debug’ command.

Is there something I missed in my config ?

Cordialement
Patrick GINHOUX


___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org<mailto:sr-users@lists.sip-router.org>
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

[SR-Users] Question on the debug change level command with 5.0.x

[Ginhoux, Patrick]

Hi,

Previously, in my kamailio.cfg 3.3.1, the debug level is set using the 'debug' 
option.
Then with the MI_FIFO module it was simple to change debug level on the flight 
using the simple command 'kamctl fifo debug '.

Moving to kamailio 5.0.x, there is no more MI_FIFO module. In the kamailio.cfg, 
I still have the 'debug' option set; so I'm looking for the command to use to 
change the debug level.

I look at the debugger module that seems the solution. So I add the following 
lines in y script:

debug=4

loadmodule "debugger.so"

modparam("debugger", "log_level", 1)
modparam("debugger", "mod_hash_size", 5)
modparam("debugger", "mod_level_mode", 1)

Then I try to use the following commands :

This one retrieves the debug level set by the debug=4) :
[root@vm-vse02-siprouter1 kamailio]# kamcmd dbg.get_mod_level core
4

This one changed the debug level for the core module
[root@vm-vse02-siprouter1 kamailio]# kamcmd dbg.set_mod_level core 2
200 ok

Same commands can be used for each of the module loaded:

[root@vm-vse02-siprouter1 kamailio]# kamcmd dbg.get_mod_level tm
4
[root@vm-vse02-siprouter1 kamailio]# kamcmd dbg.set_mod_level tm 2
200 ok

[root@vm-vse02-siprouter1 kamailio]# kamcmd dbg.get_mod_level dispatcher
4
[root@vm-vse02-siprouter1 kamailio]# kamcmd dbg.set_mod_level dispatcher 2
200 ok

Each command only applies to a specific module.

I don't find a 'global' command that I could use in the same manner as the old 
'kamctl fifo debug' command.

Is there something I missed in my config ?

Cordialement
Patrick GINHOUX

___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] failed to find append_branch

[Ginhoux, Patrick]

Hi,

I'm a new user too and I'm working on a 'migration' from kamailio 3.3.x to 
5.0.x.

So first, what is the level of kamailio you use ?

Then what is the content of line 45, column 43, where kamailio finds a 'mi' 
command ?

At least, on the web you can see similar examples as yours : 
https://github.com/sipwise/kamailio/blob/master/examples/kamailio/fork.cfg . 
From your extract I see a difference in the following line:

append_branch("sip:paral...@kamailio.org:9");

Yours is :

append_branch("sip:paral...@kamailio.org");


I don't know much about this,and I hope this help.

Cordialement
Patrick GINHOUX

De : sr-users [mailto:sr-users-boun...@lists.sip-router.org] De la part de 
Anuradha Selvarajan
Envoyé : jeudi 23 mars 2017 00:02
À : sr-users@lists.sip-router.org
Objet : [SR-Users] failed to find append_branch

Hello,

I am a new user to kamailio. I am trying to use the fork.cfg to send sip 
registration to 2 destination. I get the following error but I have added 
loadmodule tm.so, why am I still getting this error?

Mar 22 15:53:48 emps116 kamailio[14065]: ERROR:  [cfg.y:3295]: yyparse(): 
cfg. parser: failed to find command append_branch (params 1)
Mar 22 15:53:48 emps116 kamailio[14065]: :  [cfg.y:3435]: yyerror_at(): 
parse error in config file /etc/kamailio/fork.cfg, line 45, column 43: unknown 
command, mi
Mar 22 15:53:48 emps116 kamailio[14065]: ERROR: bad config file (1 errors)
Mar 22 15:53:48 emps116 kamailio[14065]: loading modules under config path: 
/usr/lib/x86_64-linux-gnu/kamailio/modules
Mar 22 15:53:48 emps116 kamailio[14065]: loading modules under config path: 
/usr/lib/x86_64-linux-gnu/kamailio/modules/
Mar 22 15:53:48 emps116 kamailio[14065]: INFO:  [sctp_core.c:53]: 
sctp_core_destroy(): SCTP API not initialized
Mar 22 15:53:48 emps116 systemd[1]: kamailio.service: Control process exited, 
code=exited status=255
Mar 22 15:53:48 emps116 systemd[1]: Failed to start Kamailio (OpenSER) - the 
Open Source SIP Server.

My script looks like this (default one):

mpath="/usr/lib/x86_64-linux-gnu/kamailio/modules"


loadmodule "sl.so"
loadmodule "tm.so"
.
.
.
.
route{
# for testing purposes, simply okay all REGISTERs
if (method=="REGISTER") {
log("REGISTER");
sl_send_reply("200", "ok");
exit;
};
# try these two destinations first in parallel; the second
# destination is targeted to sink port -- that will make ser
# wait until timer hits
seturi("sip:nob...@kamailio.org");
append_branch("sip:paral...@kamailio.org");
# if we do not get a positive reply, continue at reply_route[1]
#t_on_failure("1");
# forward the request to all destinations in destination set now
t_relay();
}


Appreciate any help!
Thanks
Anu
___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] ht_db_load_table(): key type must be string (type=6)

[Ginhoux, Patrick]

Hi,

Below the structure of the properties table :

mysql> show create table properties;
+++
| Table  | Create Table 


  |
+++
| properties | CREATE TABLE `properties` (
  `id` int(6) unsigned NOT NULL AUTO_INCREMENT COMMENT 'UniqueID',
  `key_name` text NOT NULL,
  `key_value` text NOT NULL,
  `value_type` int(1) NOT NULL,
  `key_type` int(1) NOT NULL,
  PRIMARY KEY (`id`)
) ENGINE=InnoDB AUTO_INCREMENT=10001 DEFAULT CHARSET=latin1 |
+++
1 row in set (0.02 sec)

Cordialement
Patrick GINHOUX

De : sr-users [mailto:sr-users-boun...@lists.sip-router.org] De la part de 
Daniel-Constantin Mierla
Envoyé : mardi 21 mars 2017 13:25
À : Kamailio (SER) - Users Mailing List 
Objet : Re: [SR-Users] ht_db_load_table(): key type must be string (type=6)


Hello,

can you give the structure of the table properties (show create table ...)?

Cheers,

Daniel

March 21, 2017 11:30 AM, "Ginhoux, Patrick" 
mailto:%22Ginhoux,%20patrick%22%20%3cpatrick.ginh...@fr.unisys.com%3e>>
 wrote:

Hi,

A second update for people who started to look at this issue.

I have identified the real cause of the problem by looking more in the kamailio 
log with the debug traces. I discover that it is related to the load of the 
properties table in the htable.

I have the following entries in my mysql db :

+---++-++--+

| id | key_name | key_value | value_type | key_type |

+---++-++--+

| 0 | VERSION | 120104-1734 | 0 | 0 |

| 1 | mmm-retry | 408=Y;502=Y;503=Y | 0 | 0 |

| 2 | mgcf-retry | 408=Y;502=Y;503=Y | 0 | 0 |

| 3 | max-mmm-retry | 2 | 0 | 0 |

| 4 | max-mgcf-retry | 2 | 0 | 0 |

| 5 | target-uri | mgcf=10.10.10.10;mmm-legacy=20.20.20.10;mmm=20.20.20.20 | 0 
| 0 |

| 6 | pike-status | 503 Service Overload | 0 | 0 |

| 7 | mgcf-path | 99 | 0 | 0 |

| 16 | mmm-nodeid | OPMMMS1VSE01=1;OPMMMS1VSE02=2 | 0 | 0 |

| 17 | mmm-node-path | 1=1;2=2 | 0 | 0 |

+---++-++--+

In the kamailio.cfg, the << modparam("htable", "htable", 
"propertiesHash=>size=4;dbtable=properties;") >> command causes the load of the 
above table in the htable.

In the log we can see, that the load is done in the alphabetic order of the 
key_name and it fails to load the last entry “VERSION” :

Mar 21 10:25:28 localhost /usr/sbin/kamailio[5784]: DEBUG:  
[db_val.c:169]: db_str2val(): converting BLOB [VERSION]

Mar 21 10:25:28 localhost /usr/sbin/kamailio[5784]: DEBUG:  
[db_val.c:74]: db_str2val(): converting INT [0]

Mar 21 10:25:28 localhost /usr/sbin/kamailio[5784]: DEBUG:  
[db_val.c:74]: db_str2val(): converting INT [0]

Mar 21 10:25:28 localhost /usr/sbin/kamailio[5784]: DEBUG:  
[db_val.c:169]: db_str2val(): converting BLOB [120104-1734]

Mar 21 10:25:28 localhost /usr/sbin/kamailio[5784]: ERROR: htable 
[ht_db.c:276]: ht_db_load_table(): key type must be string (type=6)

If I add a new entry named “W”, then the failure occurs on this entry that 
is the last alphabetic entry :

| 1 | W | toto | 0 | 0 |

Mar 21 10:28:45 localhost /usr/sbin/kamailio[5817]: DEBUG:  
[db_val.c:169]: db_str2val(): converting BLOB [W]

Mar 21 10:28:45 localhost /usr/sbin/kamailio[5817]: DEBUG:  
[db_val.c:74]: db_str2val(): converting INT [0]

Mar 21 10:28:45 localhost /usr/sbin/kamailio[5817]: DEBUG:  
[db_val.c:74]: db_str2val(): converting INT [0]

Mar 21 10:28:45 localhost /usr/sbin/kamailio[5817]: DEBUG:  
[db_val.c:169]: db_str2val(): converting BLOB [toto]

Mar 21 10:28:45 localhost /usr/sbin/kamailio[5817]: ERROR: htable 
[ht

Re: [SR-Users] ht_db_load_table(): key type must be string (type=6)

[Ginhoux, Patrick]

Hi,

There was a mistake in the file attached ; the short kamailio.cfg file (that 
makes kamailio to start) was not the correct one; attached the correct one.

Have anyone an idea of this problem ?

Cordialement
Patrick GINHOUX

De : Ginhoux, Patrick
Envoyé : lundi 20 mars 2017 17:58
À : Kamailio users (sr-users@lists.sip-router.org) 

Objet : RE: ht_db_load_table(): key type must be string (type=6)

Hi,

To figure out what causes this issue, I work to shorten my kamailio.cfg to 
contains loadmodule/modparam instructions for the  htable module only.

My first attempt (see kamailio.cfg.ok) shows that the problem doesn't occur.

In the second attempt (see kamailio.cfg.ko) I add instructions previously 
removed from the original .cfg file. I have determined that, depending on the 
instructions that follows the "modparam("htable", "fetch_rows", 1000)" line, 
the "key type must be string (type=6)" error occurs or not.
In this ko file, if I comment out the following sequence, the error occurs :

modparam("htable", "fetch_rows", 1000)
#!!ifdef FIXED_ROUTING
#modparam("htable", "htable", "mbxrangeHash=>size=4;dbtable=mbxrange;")
#!!else
#modparam("htable", "htable", "abpqHash=>size=12;dbtable=abpq;")
#modparam("htable", "htable", "zabpqHash=>size=12;dbtable=zabpq;")
#!!endif
modparam("htable", "htable", "propertiesHash=>size=4;dbtable=properties;")

I hope my explanation is clearn and there are people who can help me on this 
problem that causes kamailio to not start.


Cordialement
Patrick GINHOUX

De : Ginhoux, Patrick
Envoyé : vendredi 17 mars 2017 15:46
À : Kamailio users 
(sr-users@lists.sip-router.org<mailto:sr-users@lists.sip-router.org>) 
mailto:sr-users@lists.sip-router.org>>
Objet : ht_db_load_table(): key type must be string (type=6)

Hi,

Now the kamailio installation is completed, I try to start kamailio but got an 
error on a modparam line.

By looking at the kamailio.cfg (with debug mode) it looks like the instruction 
is not correct :

modparam("htable", "fetch_rows", 1000)

[root@vm-vse02-siprouter1 ~]# systemctl status kamailio.service -l
kamailio.service - SYSV: Kamailio is a fast, reliable and flexible SIP Server.
   Loaded: loaded (/etc/rc.d/init.d/kamailio)
   Active: failed (Result: exit-code) since Fri 2017-03-17 15:38:13 CET; 17s ago
  Process: 1526 ExecStart=/etc/rc.d/init.d/kamailio start (code=exited, 
status=1/FAILURE)

Mar 17 15:38:13 vm-vse02-siprouter1 /usr/sbin/kamailio[1539]: INFO: pike 
[pike.c:99]: pike_init(): PIKE - initializing
Mar 17 15:38:13 vm-vse02-siprouter1 /usr/sbin/kamailio[1539]: INFO: pike 
[ip_tree.c:81]: init_lock_set(): probing 256 set size
Mar 17 15:38:13 vm-vse02-siprouter1 /usr/sbin/kamailio[1539]: INFO: cfgutils 
[cfgutils.c:767]: mod_init(): no hash_file given, disable hash functionality
Mar 17 15:38:13 vm-vse02-siprouter1 /usr/sbin/kamailio[1539]: ERROR: htable 
[ht_db.c:276]: ht_db_load_table(): key type must be string (type=6)
Mar 17 15:38:13 vm-vse02-siprouter1 /usr/sbin/kamailio[1539]: ERROR:  
[core/sr_module.c:968]: init_mod(): Error while initializing module htable 
(/usr/lib64/kamailio/modules/htable.so)
Mar 17 15:38:13 vm-vse02-siprouter1 /usr/sbin/kamailio[1539]: INFO:  
[core/sctp_core.c:53]: sctp_core_destroy(): SCTP API not initialized
Mar 17 15:38:13 vm-vse02-siprouter1 kamailio[1526]: Starting kamailio:
Mar 17 15:38:13 vm-vse02-siprouter1 systemd[1]: kamailio.service: control 
process exited, code=exited status=1
Mar 17 15:38:13 vm-vse02-siprouter1 systemd[1]: Failed to start SYSV: Kamailio 
is a fast, reliable and flexible SIP Server..
Mar 17 15:38:13 vm-vse02-siprouter1 systemd[1]: Unit kamailio.service entered 
failed state.
[root@vm-vse02-siprouter1 ~]#

modparam("htable", "fetch_rows", "1000")

[root@vm-vse02-siprouter1 ~]# systemctl status kamailio.service -l
kamailio.service - SYSV: Kamailio is a fast, reliable and flexible SIP Server.
   Loaded: loaded (/etc/rc.d/init.d/kamailio)
   Active: failed (Result: exit-code) since Fri 2017-03-17 15:26:21 CET; 3s ago
  Process: 1452 ExecStart=/etc/rc.d/init.d/kamailio start (code=exited, 
status=1/FAILURE)

Mar 17 15:26:20 vm-vse02-siprouter1 systemd[1]: Starting SYSV: Kamailio is a 
fast, reliable and flexible SIP Server
Mar 17 15:26:21 vm-vse02-siprouter1 kamailio[1452]: Not starting : invalid 
configuration file!
Mar 17 15:26:21 vm-vse02-siprouter1 kamailio[1452]: 0(1460) ERROR:  
[core/modparam.c:141]: set_mod_param_regex(): parameter  of type 
<1> not found in module 
Mar 17 15:26:21 vm-vse02-siprouter1 kamailio[1452]: 0(1460) CRITICAL:  
[core/cfg.y:3404]: yyerror_at(): parse error in config file 
//etc/kamailio/kamailio.cfg, line 308, column 41: Can't set module parameter
Mar 17 15:26:21 vm-vse02-siprouter1 kamailio

Re: [SR-Users] ht_db_load_table(): key type must be string (type=6)

[Ginhoux, Patrick]

Hi,

To figure out what causes this issue, I work to shorten my kamailio.cfg to 
contains loadmodule/modparam instructions for the  htable module only.

My first attempt (see kamailio.cfg.ok) shows that the problem doesn't occur.

In the second attempt (see kamailio.cfg.ko) I add instructions previously 
removed from the original .cfg file. I have determined that, depending on the 
instructions that follows the "modparam("htable", "fetch_rows", 1000)" line, 
the "key type must be string (type=6)" error occurs or not.
In this ko file, if I comment out the following sequence, the error occurs :

modparam("htable", "fetch_rows", 1000)
#!!ifdef FIXED_ROUTING
#modparam("htable", "htable", "mbxrangeHash=>size=4;dbtable=mbxrange;")
#!!else
#modparam("htable", "htable", "abpqHash=>size=12;dbtable=abpq;")
#modparam("htable", "htable", "zabpqHash=>size=12;dbtable=zabpq;")
#!!endif
modparam("htable", "htable", "propertiesHash=>size=4;dbtable=properties;")

I hope my explanation is clearn and there are people who can help me on this 
problem that causes kamailio to not start.


Cordialement
Patrick GINHOUX

De : Ginhoux, Patrick
Envoyé : vendredi 17 mars 2017 15:46
À : Kamailio users (sr-users@lists.sip-router.org) 

Objet : ht_db_load_table(): key type must be string (type=6)

Hi,

Now the kamailio installation is completed, I try to start kamailio but got an 
error on a modparam line.

By looking at the kamailio.cfg (with debug mode) it looks like the instruction 
is not correct :

modparam("htable", "fetch_rows", 1000)

[root@vm-vse02-siprouter1 ~]# systemctl status kamailio.service -l
kamailio.service - SYSV: Kamailio is a fast, reliable and flexible SIP Server.
   Loaded: loaded (/etc/rc.d/init.d/kamailio)
   Active: failed (Result: exit-code) since Fri 2017-03-17 15:38:13 CET; 17s ago
  Process: 1526 ExecStart=/etc/rc.d/init.d/kamailio start (code=exited, 
status=1/FAILURE)

Mar 17 15:38:13 vm-vse02-siprouter1 /usr/sbin/kamailio[1539]: INFO: pike 
[pike.c:99]: pike_init(): PIKE - initializing
Mar 17 15:38:13 vm-vse02-siprouter1 /usr/sbin/kamailio[1539]: INFO: pike 
[ip_tree.c:81]: init_lock_set(): probing 256 set size
Mar 17 15:38:13 vm-vse02-siprouter1 /usr/sbin/kamailio[1539]: INFO: cfgutils 
[cfgutils.c:767]: mod_init(): no hash_file given, disable hash functionality
Mar 17 15:38:13 vm-vse02-siprouter1 /usr/sbin/kamailio[1539]: ERROR: htable 
[ht_db.c:276]: ht_db_load_table(): key type must be string (type=6)
Mar 17 15:38:13 vm-vse02-siprouter1 /usr/sbin/kamailio[1539]: ERROR:  
[core/sr_module.c:968]: init_mod(): Error while initializing module htable 
(/usr/lib64/kamailio/modules/htable.so)
Mar 17 15:38:13 vm-vse02-siprouter1 /usr/sbin/kamailio[1539]: INFO:  
[core/sctp_core.c:53]: sctp_core_destroy(): SCTP API not initialized
Mar 17 15:38:13 vm-vse02-siprouter1 kamailio[1526]: Starting kamailio:
Mar 17 15:38:13 vm-vse02-siprouter1 systemd[1]: kamailio.service: control 
process exited, code=exited status=1
Mar 17 15:38:13 vm-vse02-siprouter1 systemd[1]: Failed to start SYSV: Kamailio 
is a fast, reliable and flexible SIP Server..
Mar 17 15:38:13 vm-vse02-siprouter1 systemd[1]: Unit kamailio.service entered 
failed state.
[root@vm-vse02-siprouter1 ~]#

modparam("htable", "fetch_rows", "1000")

[root@vm-vse02-siprouter1 ~]# systemctl status kamailio.service -l
kamailio.service - SYSV: Kamailio is a fast, reliable and flexible SIP Server.
   Loaded: loaded (/etc/rc.d/init.d/kamailio)
   Active: failed (Result: exit-code) since Fri 2017-03-17 15:26:21 CET; 3s ago
  Process: 1452 ExecStart=/etc/rc.d/init.d/kamailio start (code=exited, 
status=1/FAILURE)

Mar 17 15:26:20 vm-vse02-siprouter1 systemd[1]: Starting SYSV: Kamailio is a 
fast, reliable and flexible SIP Server
Mar 17 15:26:21 vm-vse02-siprouter1 kamailio[1452]: Not starting : invalid 
configuration file!
Mar 17 15:26:21 vm-vse02-siprouter1 kamailio[1452]: 0(1460) ERROR:  
[core/modparam.c:141]: set_mod_param_regex(): parameter  of type 
<1> not found in module 
Mar 17 15:26:21 vm-vse02-siprouter1 kamailio[1452]: 0(1460) CRITICAL:  
[core/cfg.y:3404]: yyerror_at(): parse error in config file 
//etc/kamailio/kamailio.cfg, line 308, column 41: Can't set module parameter
Mar 17 15:26:21 vm-vse02-siprouter1 kamailio[1452]: 0(1460) WARNING:  
[core/cfg.y:3378]: warn_at(): warning in config file 
//etc/kamailio/kamailio.cfg, line 971, column 6-13: constant value in if(...)
Mar 17 15:26:21 vm-vse02-siprouter1 kamailio[1452]: ERROR: bad config file (1 
errors)
Mar 17 15:26:21 vm-vse02-siprouter1 kamailio[1452]: 0(1460) INFO:  
[core/sctp_core.c:53]: sctp_core_destroy(): SCTP API not initialized
Mar 17 15:26:21 vm-vse02-siprouter1 systemd[1]: kamailio.service: control 
process exited, code=exited stat

[SR-Users] ht_db_load_table(): key type must be string (type=6)

[Ginhoux, Patrick]

Hi,

Now the kamailio installation is completed, I try to start kamailio but got an 
error on a modparam line.

By looking at the kamailio.cfg (with debug mode) it looks like the instruction 
is not correct :

modparam("htable", "fetch_rows", 1000)

[root@vm-vse02-siprouter1 ~]# systemctl status kamailio.service -l
kamailio.service - SYSV: Kamailio is a fast, reliable and flexible SIP Server.
   Loaded: loaded (/etc/rc.d/init.d/kamailio)
   Active: failed (Result: exit-code) since Fri 2017-03-17 15:38:13 CET; 17s ago
  Process: 1526 ExecStart=/etc/rc.d/init.d/kamailio start (code=exited, 
status=1/FAILURE)

Mar 17 15:38:13 vm-vse02-siprouter1 /usr/sbin/kamailio[1539]: INFO: pike 
[pike.c:99]: pike_init(): PIKE - initializing
Mar 17 15:38:13 vm-vse02-siprouter1 /usr/sbin/kamailio[1539]: INFO: pike 
[ip_tree.c:81]: init_lock_set(): probing 256 set size
Mar 17 15:38:13 vm-vse02-siprouter1 /usr/sbin/kamailio[1539]: INFO: cfgutils 
[cfgutils.c:767]: mod_init(): no hash_file given, disable hash functionality
Mar 17 15:38:13 vm-vse02-siprouter1 /usr/sbin/kamailio[1539]: ERROR: htable 
[ht_db.c:276]: ht_db_load_table(): key type must be string (type=6)
Mar 17 15:38:13 vm-vse02-siprouter1 /usr/sbin/kamailio[1539]: ERROR:  
[core/sr_module.c:968]: init_mod(): Error while initializing module htable 
(/usr/lib64/kamailio/modules/htable.so)
Mar 17 15:38:13 vm-vse02-siprouter1 /usr/sbin/kamailio[1539]: INFO:  
[core/sctp_core.c:53]: sctp_core_destroy(): SCTP API not initialized
Mar 17 15:38:13 vm-vse02-siprouter1 kamailio[1526]: Starting kamailio:
Mar 17 15:38:13 vm-vse02-siprouter1 systemd[1]: kamailio.service: control 
process exited, code=exited status=1
Mar 17 15:38:13 vm-vse02-siprouter1 systemd[1]: Failed to start SYSV: Kamailio 
is a fast, reliable and flexible SIP Server..
Mar 17 15:38:13 vm-vse02-siprouter1 systemd[1]: Unit kamailio.service entered 
failed state.
[root@vm-vse02-siprouter1 ~]#

modparam("htable", "fetch_rows", "1000")

[root@vm-vse02-siprouter1 ~]# systemctl status kamailio.service -l
kamailio.service - SYSV: Kamailio is a fast, reliable and flexible SIP Server.
   Loaded: loaded (/etc/rc.d/init.d/kamailio)
   Active: failed (Result: exit-code) since Fri 2017-03-17 15:26:21 CET; 3s ago
  Process: 1452 ExecStart=/etc/rc.d/init.d/kamailio start (code=exited, 
status=1/FAILURE)

Mar 17 15:26:20 vm-vse02-siprouter1 systemd[1]: Starting SYSV: Kamailio is a 
fast, reliable and flexible SIP Server
Mar 17 15:26:21 vm-vse02-siprouter1 kamailio[1452]: Not starting : invalid 
configuration file!
Mar 17 15:26:21 vm-vse02-siprouter1 kamailio[1452]: 0(1460) ERROR:  
[core/modparam.c:141]: set_mod_param_regex(): parameter  of type 
<1> not found in module 
Mar 17 15:26:21 vm-vse02-siprouter1 kamailio[1452]: 0(1460) CRITICAL:  
[core/cfg.y:3404]: yyerror_at(): parse error in config file 
//etc/kamailio/kamailio.cfg, line 308, column 41: Can't set module parameter
Mar 17 15:26:21 vm-vse02-siprouter1 kamailio[1452]: 0(1460) WARNING:  
[core/cfg.y:3378]: warn_at(): warning in config file 
//etc/kamailio/kamailio.cfg, line 971, column 6-13: constant value in if(...)
Mar 17 15:26:21 vm-vse02-siprouter1 kamailio[1452]: ERROR: bad config file (1 
errors)
Mar 17 15:26:21 vm-vse02-siprouter1 kamailio[1452]: 0(1460) INFO:  
[core/sctp_core.c:53]: sctp_core_destroy(): SCTP API not initialized
Mar 17 15:26:21 vm-vse02-siprouter1 systemd[1]: kamailio.service: control 
process exited, code=exited status=1
Mar 17 15:26:21 vm-vse02-siprouter1 systemd[1]: Failed to start SYSV: Kamailio 
is a fast, reliable and flexible SIP Server..
Mar 17 15:26:21 vm-vse02-siprouter1 systemd[1]: Unit kamailio.service entered 
failed state.
[root@vm-vse02-siprouter1 ~]#

The documentation shows that fetch_rows is an integer :
 fetch_rows (integer)
How many rows to fetch at once from database.
Default value is 100.
Example 1.12. Set fetch_rows parameter
...
modparam("htable", "fetch_rows", 1000)

So how to explain the first error.

Have you any thoughts on this case ?

Cordialement
Patrick GINHOUX

___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] Error on of type <2> not found in module and SCTP API Not initialized

[Ginhoux, Patrick]

Last update,

With the correct Perl package for Rhel 7, now my kamailio installation has 
complete with success.

And the module app_perl initialization error below goes away.

So that I can close this topic.

Cordialement
Patrick GINHOUX

De : Ginhoux, Patrick
Envoyé : vendredi 17 mars 2017 07:40
À : SIP Router - Kamailio (OpenSER) and SIP Express Router (SER) - Users 
Mailing List 
Objet : RE: [SR-Users] Error on  of type <2> not found 
in module  and SCTP API Not initialized

Thanks Federico for this answer,

I see that in my .cfg there was a double ‘h’ in the name, while now there is 
only one (I need probably new glasses ☺ ).

Now it is fixed but now I got an error with the PERL mdule I’m trying to get 
for Rhel 7:

Mar 16 13:46:38 vm-vse02-siprouter1 /usr/sbin/kamailio[6767]: INFO: app_perl 
[app_perl_mod.c:219]: parser_init(): setting lib path: 
'/usr/lib64/kamailio/modules/'
Mar 16 13:46:38 vm-vse02-siprouter1 /usr/sbin/kamailio[6767]: ERROR: app_perl 
[app_perl_mod.c:241]: parser_init(): failed to load perl file 
"/etc/kamailio/snmptrap.pl" with code 2.
Mar 16 13:46:38 vm-vse02-siprouter1 /usr/sbin/kamailio[6767]: ERROR:  
[core/sr_module.c:968]: init_mod(): Error while initializing module app_perl 
(/usr/lib64/kamailio/modules/app_perl.so)

I opened another topic related to the rpm package for PERL module that is not 
available for Rhel 7 (see thread “Search for kamailio PERL module for 5.0 
level”).

Because I’m a newbie in this domain, I don’t have the experience to build a rpm 
package. Then one of my colleague helps me to build it. But because of this 
error, there is maybe something missing in the PERL installation on my server.
I’m doing some research.

If you have some ideas…

Cordialement
Patrick GINHOUX

De : sr-users [mailto:sr-users-boun...@lists.sip-router.org] De la part de 
Federico Cabiddu
Envoyé : jeudi 16 mars 2017 13:41
À : SIP Router - Kamailio (OpenSER) and SIP Express Router (SER) - Users 
Mailing List 
mailto:sr-users@lists.sip-router.org>>
Objet : Re: [SR-Users] Error on  of type <2> not found 
in module  and SCTP API Not initialized

Hi,
param name has changed some versions ago:
http://www.kamailio.org/docs/modules/devel/modules/dispatcher.html#dispatcher.p.ds_probing_threshold

Cheers,

Federico

On 16 Mar 2017 13:35, "Ginhoux, Patrick" 
mailto:patrick.ginh...@fr.unisys.com>> wrote:
Hi,

I’m migrating my kamailio.cfg from the 3.3.1 release to 5.0.0 and encounter the 
following errors :

Mar 16 12:56:45 vm-vse02-siprouter1 systemd[1]: Starting SYSV: Kamailio is a 
fast, reliable and flexible SIP Server
Mar 16 12:56:45 vm-vse02-siprouter1 kamailio[6644]: Not starting : invalid 
configuration file!
Mar 16 12:56:45 vm-vse02-siprouter1 kamailio[6644]: 0(6652) ERROR:  
[core/modparam.c:141]: set_mod_param_regex(): parameter  
of type <2> not found in module 
Mar 16 12:56:45 vm-vse02-siprouter1 kamailio[6644]: 0(6652) CRITICAL:  
[core/cfg.y:3404]: yyerror_at(): parse error in config file 
//etc/kamailio/kamailio.cfg, line 295, column 49: Can't set module parameter
Mar 16 12:56:45 vm-vse02-siprouter1 kamailio[6644]: 0(6652) WARNING:  
[core/cfg.y:3378]: warn_at(): warning in config file 
//etc/kamailio/kamailio.cfg, line 971, column 6-13: constant value in if(...)
Mar 16 12:56:45 vm-vse02-siprouter1 kamailio[6644]: ERROR: bad config file (1 
errors)
Mar 16 12:56:45 vm-vse02-siprouter1 kamailio[6644]: 0(6652) INFO:  
[core/sctp_core.c:53]: sctp_core_destroy(): SCTP API not initialized
Mar 16 12:56:45 vm-vse02-siprouter1 systemd[1]: kamailio.service: control 
process exited, code=exited status=1
Mar 16 12:56:45 vm-vse02-siprouter1 systemd[1]: Failed to start SYSV: Kamailio 
is a fast, reliable and flexible SIP Server..
Mar 16 12:56:45 vm-vse02-siprouter1 systemd[1]: Unit kamailio.service entered 
failed state.

Below the extract of my kamailio.cfg file :

modparam("dispatcher", "list_file", DISPATCHER_FILE)
modparam("dispatcher", "ds_probing_mode", 1)
modparam("dispatcher", "ds_probing_threshhold",3)
modparam("dispatcher", "flags", 2)
modparam("dispatcher", "attrs_avp", "$avp(dsattrs)")
modparam("dispatcher", "dst_avp", "$avp(dsdst)")
modparam("dispatcher", "grp_avp", "$avp(dsgrp)")
modparam("dispatcher", "cnt_avp", "$avp(dscnt)")
modparam("dispatcher", "ds_hash_size", 8)
modparam("dispatcher", "ds_ping_interval", 10)
modparam("dispatcher", "force_dst", 1)

For the dispatcher error :
I don’t find any change (eg in the Changelog for 5.0.0.) regarding the 
dispatcher module.
So is it a bug in the dispatcher module or have I to change it to something 
else ?

For the SCTP API error :
I don’t know what to do here.

Thanks t

Re: [SR-Users] Search for kamailio PERL module for 5.0 level

[Ginhoux, Patrick]

Hi,

Thanks for the link as now I can see all I need for kamailio 5.0.x .

I just get the rpms and complete with success the installation.

So I can continue my installation.

Great job and thanks again for the help.

Cordialement
Patrick GINHOUX

De : Daniel-Constantin Mierla [mailto:mico...@gmail.com]
Envoyé : vendredi 17 mars 2017 08:06
À : Ginhoux, Patrick ; Kamailio (SER) - Users 
Mailing List 
Objet : Re: [SR-Users] Search for kamailio PERL module for 5.0 level


Hello,

links for various distros were added at:

  * https://www.kamailio.org/wiki/packages/rpms#kamailio_50x

A short report back on mailing list saying if the packages work ok would be 
appreciated.

Cheers,
Daniel

On 16/03/2017 16:25, Ginhoux, Patrick wrote:
Hi,

I just need to get the rpm but I have difficulties to find the correct link. 
Can you help on this ?

Cordialement
Patrick GINHOUX

De : Daniel-Constantin Mierla [mailto:mico...@gmail.com]
Envoyé : jeudi 16 mars 2017 16:10
À : Ginhoux, Patrick 
<mailto:patrick.ginh...@fr.unisys.com>; Kamailio 
(SER) - Users Mailing List 
<mailto:sr-users@lists.sip-router.org>
Objet : Re: [SR-Users] Search for kamailio PERL module for 5.0 level


Hello,

I already triggered the rebuild of rpms, some of them being completed already:

  - https://build.opensuse.org/package/show/home:kamailio:v5.0.0-rpms/kamailio50
If you want to get access and play with the specs in order to tune the rpms, 
then make an account on that portal and let me know the user id -- I will be 
glad to allow others helping with the generations of rpms, because I don't 
really use rpm-based systems myself.

Cheers,
Daniel
On 16/03/2017 15:08, Ginhoux, Patrick wrote:
Hi Daniel,

Thanks for the help.

Can you tell me when I can expect to get the PERL module built for 5.0 ?

If it is something that you need to schedule (it is something I can 
understand), then I could use the kamailio 4.4 level instead of 5.0 .

Cordialement
Patrick GINHOUX

De : sr-users [mailto:sr-users-boun...@lists.sip-router.org] De la part de 
Daniel-Constantin Mierla
Envoyé : jeudi 16 mars 2017 13:13
À : Kamailio (SER) - Users Mailing List 
<mailto:sr-users@lists.sip-router.org>
Objet : Re: [SR-Users] Search for kamailio PERL module for 5.0 level


Hello,

probably perl module failed to be build on this distros by the opensuse build 
service. I will try to re-enable building them on centos and redhat and see the 
results.

Cheers,
Daniel

On 14/03/2017 18:08, Ginhoux, Patrick wrote:
Hi,

I’m a beginner in the use of kamailio product, so I try below to explain my 
problem with my words:


1)  PERL module issue :


Some years ago a SIP Router proxy running RedHat 6.2 was developped using the 
kamailio version 3.3 and the following packages used  :

kamailio-3.3.2-1.1.1.x86_64.rpm
kamailio-snmpstats-3.3.2-1.1.1.x86_64.rpm
kamailio-mysql-3.3.2-1.1.1.x86_64.rpm
kamailio-perl-3.3.2-1.1.1.x86_64.rpm

We have the project to migrate this SIP Proxy to RedHat 7.1 and used the latest 
Kamailio v5.0.0 Release:

kamailio-5.0.0-24.1.x86_64.rpm
kamailio-mysql-5.0.0-24.1.x86_64.rpm
kamailio-snmpstats-5.0.0-24.1.x86_64.rpm

However I don’t find the kamalio-perl package for RedHat 7.1. I see that the 
perl module has been renamed to ‘app_perl’ but I don’t find it either for 
kamailio 5.0.0.


2)  Kamailio.cfg script



Our proxy used the kamailio.cfg from the sample  of the 3.3.3 release.



So can I reuse the same 3.3.3 kamailio.cfg file with the 5.0.0 release or 
should I migrate (rewrite it) from the 5.0.0 sample ?

So I’m looking for some help on these issues.

Is there people that had this case ?

Thanks in advance for any answer.

Cordialement
Patrick GINHOUX

PS : I just create my account today but don’t get the email to validate it.







___

SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list

sr-users@lists.sip-router.org<mailto:sr-users@lists.sip-router.org>

http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users





--

Daniel-Constantin Mierla

www.twitter.com/miconda<http://www.twitter.com/miconda> -- 
www.linkedin.com/in/miconda<http://www.linkedin.com/in/miconda>

Kamailio Advanced Training - Mar 6-8 (Europe) and Mar 20-22 (USA) - 
www.asipto.com<http://www.asipto.com>

Kamailio World Conference - May 8-10, 2017 - 
www.kamailioworld.com<http://www.kamailioworld.com>




--

Daniel-Constantin Mierla

www.twitter.com/miconda<http://www.twitter.com/miconda> -- 
www.linkedin.com/in/miconda<http://www.linkedin.com/in/miconda>

Kamailio Advanced Training - Mar 6-8 (Europe) and Mar 20-22 (USA) - 
www.asipto.com<http://www.asipto.com>

Kamailio World Conference - May 8-10, 2017 - 
www.kamailioworld.com<http://www.kamailioworld.com>



--

Daniel-Constantin Mierla

www.twitter.com/miconda<http://www.twitter.com/miconda> -- 
www.linkedin.com/in/miconda<http://www.linkedin.com/in/miconda>

Re: [SR-Users] Error on of type <2> not found in module and SCTP API Not initialized

[Ginhoux, Patrick]

Thanks Federico for this answer,

I see that in my .cfg there was a double ‘h’ in the name, while now there is 
only one (I need probably new glasses ☺ ).

Now it is fixed but now I got an error with the PERL mdule I’m trying to get 
for Rhel 7:

Mar 16 13:46:38 vm-vse02-siprouter1 /usr/sbin/kamailio[6767]: INFO: app_perl 
[app_perl_mod.c:219]: parser_init(): setting lib path: 
'/usr/lib64/kamailio/modules/'
Mar 16 13:46:38 vm-vse02-siprouter1 /usr/sbin/kamailio[6767]: ERROR: app_perl 
[app_perl_mod.c:241]: parser_init(): failed to load perl file 
"/etc/kamailio/snmptrap.pl" with code 2.
Mar 16 13:46:38 vm-vse02-siprouter1 /usr/sbin/kamailio[6767]: ERROR:  
[core/sr_module.c:968]: init_mod(): Error while initializing module app_perl 
(/usr/lib64/kamailio/modules/app_perl.so)

I opened another topic related to the rpm package for PERL module that is not 
available for Rhel 7 (see thread “Search for kamailio PERL module for 5.0 
level”).

Because I’m a newbie in this domain, I don’t have the experience to build a rpm 
package. Then one of my colleague helps me to build it. But because of this 
error, there is maybe something missing in the PERL installation on my server.
I’m doing some research.

If you have some ideas…

Cordialement
Patrick GINHOUX

De : sr-users [mailto:sr-users-boun...@lists.sip-router.org] De la part de 
Federico Cabiddu
Envoyé : jeudi 16 mars 2017 13:41
À : SIP Router - Kamailio (OpenSER) and SIP Express Router (SER) - Users 
Mailing List 
Objet : Re: [SR-Users] Error on  of type <2> not found 
in module  and SCTP API Not initialized

Hi,
param name has changed some versions ago:
http://www.kamailio.org/docs/modules/devel/modules/dispatcher.html#dispatcher.p.ds_probing_threshold

Cheers,

Federico

On 16 Mar 2017 13:35, "Ginhoux, Patrick" 
mailto:patrick.ginh...@fr.unisys.com>> wrote:
Hi,

I’m migrating my kamailio.cfg from the 3.3.1 release to 5.0.0 and encounter the 
following errors :

Mar 16 12:56:45 vm-vse02-siprouter1 systemd[1]: Starting SYSV: Kamailio is a 
fast, reliable and flexible SIP Server
Mar 16 12:56:45 vm-vse02-siprouter1 kamailio[6644]: Not starting : invalid 
configuration file!
Mar 16 12:56:45 vm-vse02-siprouter1 kamailio[6644]: 0(6652) ERROR:  
[core/modparam.c:141]: set_mod_param_regex(): parameter  
of type <2> not found in module 
Mar 16 12:56:45 vm-vse02-siprouter1 kamailio[6644]: 0(6652) CRITICAL:  
[core/cfg.y:3404]: yyerror_at(): parse error in config file 
//etc/kamailio/kamailio.cfg, line 295, column 49: Can't set module parameter
Mar 16 12:56:45 vm-vse02-siprouter1 kamailio[6644]: 0(6652) WARNING:  
[core/cfg.y:3378]: warn_at(): warning in config file 
//etc/kamailio/kamailio.cfg, line 971, column 6-13: constant value in if(...)
Mar 16 12:56:45 vm-vse02-siprouter1 kamailio[6644]: ERROR: bad config file (1 
errors)
Mar 16 12:56:45 vm-vse02-siprouter1 kamailio[6644]: 0(6652) INFO:  
[core/sctp_core.c:53]: sctp_core_destroy(): SCTP API not initialized
Mar 16 12:56:45 vm-vse02-siprouter1 systemd[1]: kamailio.service: control 
process exited, code=exited status=1
Mar 16 12:56:45 vm-vse02-siprouter1 systemd[1]: Failed to start SYSV: Kamailio 
is a fast, reliable and flexible SIP Server..
Mar 16 12:56:45 vm-vse02-siprouter1 systemd[1]: Unit kamailio.service entered 
failed state.

Below the extract of my kamailio.cfg file :

modparam("dispatcher", "list_file", DISPATCHER_FILE)
modparam("dispatcher", "ds_probing_mode", 1)
modparam("dispatcher", "ds_probing_threshhold",3)
modparam("dispatcher", "flags", 2)
modparam("dispatcher", "attrs_avp", "$avp(dsattrs)")
modparam("dispatcher", "dst_avp", "$avp(dsdst)")
modparam("dispatcher", "grp_avp", "$avp(dsgrp)")
modparam("dispatcher", "cnt_avp", "$avp(dscnt)")
modparam("dispatcher", "ds_hash_size", 8)
modparam("dispatcher", "ds_ping_interval", 10)
modparam("dispatcher", "force_dst", 1)

For the dispatcher error :
I don’t find any change (eg in the Changelog for 5.0.0.) regarding the 
dispatcher module.
So is it a bug in the dispatcher module or have I to change it to something 
else ?

For the SCTP API error :
I don’t know what to do here.

Thanks to people that can help me on these 2 errors

Cordialement
Patrick GINHOUX


___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org<mailto:sr-users@lists.sip-router.org>
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] Search for kamailio PERL module for 5.0 level

[Ginhoux, Patrick]

Hi,

I just need to get the rpm but I have difficulties to find the correct link. 
Can you help on this ?

Cordialement
Patrick GINHOUX

De : Daniel-Constantin Mierla [mailto:mico...@gmail.com]
Envoyé : jeudi 16 mars 2017 16:10
À : Ginhoux, Patrick ; Kamailio (SER) - Users 
Mailing List 
Objet : Re: [SR-Users] Search for kamailio PERL module for 5.0 level


Hello,

I already triggered the rebuild of rpms, some of them being completed already:

  - https://build.opensuse.org/package/show/home:kamailio:v5.0.0-rpms/kamailio50
If you want to get access and play with the specs in order to tune the rpms, 
then make an account on that portal and let me know the user id -- I will be 
glad to allow others helping with the generations of rpms, because I don't 
really use rpm-based systems myself.

Cheers,
Daniel
On 16/03/2017 15:08, Ginhoux, Patrick wrote:
Hi Daniel,

Thanks for the help.

Can you tell me when I can expect to get the PERL module built for 5.0 ?

If it is something that you need to schedule (it is something I can 
understand), then I could use the kamailio 4.4 level instead of 5.0 .

Cordialement
Patrick GINHOUX

De : sr-users [mailto:sr-users-boun...@lists.sip-router.org] De la part de 
Daniel-Constantin Mierla
Envoyé : jeudi 16 mars 2017 13:13
À : Kamailio (SER) - Users Mailing List 
<mailto:sr-users@lists.sip-router.org>
Objet : Re: [SR-Users] Search for kamailio PERL module for 5.0 level


Hello,

probably perl module failed to be build on this distros by the opensuse build 
service. I will try to re-enable building them on centos and redhat and see the 
results.

Cheers,
Daniel

On 14/03/2017 18:08, Ginhoux, Patrick wrote:
Hi,

I’m a beginner in the use of kamailio product, so I try below to explain my 
problem with my words:


1)  PERL module issue :


Some years ago a SIP Router proxy running RedHat 6.2 was developped using the 
kamailio version 3.3 and the following packages used  :

kamailio-3.3.2-1.1.1.x86_64.rpm
kamailio-snmpstats-3.3.2-1.1.1.x86_64.rpm
kamailio-mysql-3.3.2-1.1.1.x86_64.rpm
kamailio-perl-3.3.2-1.1.1.x86_64.rpm

We have the project to migrate this SIP Proxy to RedHat 7.1 and used the latest 
Kamailio v5.0.0 Release:

kamailio-5.0.0-24.1.x86_64.rpm
kamailio-mysql-5.0.0-24.1.x86_64.rpm
kamailio-snmpstats-5.0.0-24.1.x86_64.rpm

However I don’t find the kamalio-perl package for RedHat 7.1. I see that the 
perl module has been renamed to ‘app_perl’ but I don’t find it either for 
kamailio 5.0.0.


2)  Kamailio.cfg script



Our proxy used the kamailio.cfg from the sample  of the 3.3.3 release.



So can I reuse the same 3.3.3 kamailio.cfg file with the 5.0.0 release or 
should I migrate (rewrite it) from the 5.0.0 sample ?

So I’m looking for some help on these issues.

Is there people that had this case ?

Thanks in advance for any answer.

Cordialement
Patrick GINHOUX

PS : I just create my account today but don’t get the email to validate it.






___

SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list

sr-users@lists.sip-router.org<mailto:sr-users@lists.sip-router.org>

http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users




--

Daniel-Constantin Mierla

www.twitter.com/miconda<http://www.twitter.com/miconda> -- 
www.linkedin.com/in/miconda<http://www.linkedin.com/in/miconda>

Kamailio Advanced Training - Mar 6-8 (Europe) and Mar 20-22 (USA) - 
www.asipto.com<http://www.asipto.com>

Kamailio World Conference - May 8-10, 2017 - 
www.kamailioworld.com<http://www.kamailioworld.com>



--

Daniel-Constantin Mierla

www.twitter.com/miconda<http://www.twitter.com/miconda> -- 
www.linkedin.com/in/miconda<http://www.linkedin.com/in/miconda>

Kamailio Advanced Training - Mar 6-8 (Europe) and Mar 20-22 (USA) - 
www.asipto.com<http://www.asipto.com>

Kamailio World Conference - May 8-10, 2017 - 
www.kamailioworld.com<http://www.kamailioworld.com>
___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] Search for kamailio PERL module for 5.0 level

[Ginhoux, Patrick]

Hi Daniel,

Thanks for the help.

Can you tell me when I can expect to get the PERL module built for 5.0 ?

If it is something that you need to schedule (it is something I can 
understand), then I could use the kamailio 4.4 level instead of 5.0 .

Cordialement
Patrick GINHOUX

De : sr-users [mailto:sr-users-boun...@lists.sip-router.org] De la part de 
Daniel-Constantin Mierla
Envoyé : jeudi 16 mars 2017 13:13
À : Kamailio (SER) - Users Mailing List 
Objet : Re: [SR-Users] Search for kamailio PERL module for 5.0 level


Hello,

probably perl module failed to be build on this distros by the opensuse build 
service. I will try to re-enable building them on centos and redhat and see the 
results.

Cheers,
Daniel

On 14/03/2017 18:08, Ginhoux, Patrick wrote:
Hi,

I’m a beginner in the use of kamailio product, so I try below to explain my 
problem with my words:


1)  PERL module issue :


Some years ago a SIP Router proxy running RedHat 6.2 was developped using the 
kamailio version 3.3 and the following packages used  :

kamailio-3.3.2-1.1.1.x86_64.rpm
kamailio-snmpstats-3.3.2-1.1.1.x86_64.rpm
kamailio-mysql-3.3.2-1.1.1.x86_64.rpm
kamailio-perl-3.3.2-1.1.1.x86_64.rpm

We have the project to migrate this SIP Proxy to RedHat 7.1 and used the latest 
Kamailio v5.0.0 Release:

kamailio-5.0.0-24.1.x86_64.rpm
kamailio-mysql-5.0.0-24.1.x86_64.rpm
kamailio-snmpstats-5.0.0-24.1.x86_64.rpm

However I don’t find the kamalio-perl package for RedHat 7.1. I see that the 
perl module has been renamed to ‘app_perl’ but I don’t find it either for 
kamailio 5.0.0.


2)  Kamailio.cfg script



Our proxy used the kamailio.cfg from the sample  of the 3.3.3 release.



So can I reuse the same 3.3.3 kamailio.cfg file with the 5.0.0 release or 
should I migrate (rewrite it) from the 5.0.0 sample ?

So I’m looking for some help on these issues.

Is there people that had this case ?

Thanks in advance for any answer.

Cordialement
Patrick GINHOUX

PS : I just create my account today but don’t get the email to validate it.





___

SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list

sr-users@lists.sip-router.org<mailto:sr-users@lists.sip-router.org>

http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users



--

Daniel-Constantin Mierla

www.twitter.com/miconda<http://www.twitter.com/miconda> -- 
www.linkedin.com/in/miconda<http://www.linkedin.com/in/miconda>

Kamailio Advanced Training - Mar 6-8 (Europe) and Mar 20-22 (USA) - 
www.asipto.com<http://www.asipto.com>

Kamailio World Conference - May 8-10, 2017 - 
www.kamailioworld.com<http://www.kamailioworld.com>
___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

[SR-Users] Error on of type <2> not found in module and SCTP API Not initialized

[Ginhoux, Patrick]

Hi,

I'm migrating my kamailio.cfg from the 3.3.1 release to 5.0.0 and encounter the 
following errors :

Mar 16 12:56:45 vm-vse02-siprouter1 systemd[1]: Starting SYSV: Kamailio is a 
fast, reliable and flexible SIP Server
Mar 16 12:56:45 vm-vse02-siprouter1 kamailio[6644]: Not starting : invalid 
configuration file!
Mar 16 12:56:45 vm-vse02-siprouter1 kamailio[6644]: 0(6652) ERROR:  
[core/modparam.c:141]: set_mod_param_regex(): parameter  
of type <2> not found in module 
Mar 16 12:56:45 vm-vse02-siprouter1 kamailio[6644]: 0(6652) CRITICAL:  
[core/cfg.y:3404]: yyerror_at(): parse error in config file 
//etc/kamailio/kamailio.cfg, line 295, column 49: Can't set module parameter
Mar 16 12:56:45 vm-vse02-siprouter1 kamailio[6644]: 0(6652) WARNING:  
[core/cfg.y:3378]: warn_at(): warning in config file 
//etc/kamailio/kamailio.cfg, line 971, column 6-13: constant value in if(...)
Mar 16 12:56:45 vm-vse02-siprouter1 kamailio[6644]: ERROR: bad config file (1 
errors)
Mar 16 12:56:45 vm-vse02-siprouter1 kamailio[6644]: 0(6652) INFO:  
[core/sctp_core.c:53]: sctp_core_destroy(): SCTP API not initialized
Mar 16 12:56:45 vm-vse02-siprouter1 systemd[1]: kamailio.service: control 
process exited, code=exited status=1
Mar 16 12:56:45 vm-vse02-siprouter1 systemd[1]: Failed to start SYSV: Kamailio 
is a fast, reliable and flexible SIP Server..
Mar 16 12:56:45 vm-vse02-siprouter1 systemd[1]: Unit kamailio.service entered 
failed state.

Below the extract of my kamailio.cfg file :

modparam("dispatcher", "list_file", DISPATCHER_FILE)
modparam("dispatcher", "ds_probing_mode", 1)
modparam("dispatcher", "ds_probing_threshhold",3)
modparam("dispatcher", "flags", 2)
modparam("dispatcher", "attrs_avp", "$avp(dsattrs)")
modparam("dispatcher", "dst_avp", "$avp(dsdst)")
modparam("dispatcher", "grp_avp", "$avp(dsgrp)")
modparam("dispatcher", "cnt_avp", "$avp(dscnt)")
modparam("dispatcher", "ds_hash_size", 8)
modparam("dispatcher", "ds_ping_interval", 10)
modparam("dispatcher", "force_dst", 1)

For the dispatcher error :
I don't find any change (eg in the Changelog for 5.0.0.) regarding the 
dispatcher module.
So is it a bug in the dispatcher module or have I to change it to something 
else ?

For the SCTP API error :
I don't know what to do here.

Thanks to people that can help me on these 2 errors

Cordialement
Patrick GINHOUX

___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] mi_fifo: No module matching found

[Ginhoux, Patrick]

Hi,

I’m a newbie too and I’m looking at the 5.0.0 version.

For your issue, it seems you want to use jsonrpcs module, but it is not loaded.

Try to add the “loadmodule "jsonrpcs.so" in your file.

Cordialement
Patrick GINHOUX

De : sr-users [mailto:sr-users-boun...@lists.sip-router.org] De la part de 
Mostafa Zare
Envoyé : mercredi 15 mars 2017 16:39
À : sr-users@lists.sip-router.org
Objet : [SR-Users] mi_fifo: No module matching  found

hi guys
i'm newbie to kamailio.
i've installed kamailio version 5 (and all the modules) from pkgs on a jessie 
debian.
i have the below config on my kamailio.cfg
when i try to start kamailio service it throws the following error.
what's the problem?


  *   systemctl status kamailio:
kamailio.service - Kamailio (OpenSER) - the Open Source SIP Server
   Loaded: loaded (/lib/systemd/system/kamailio.service; enabled)
   Active: failed (Result: exit-code) since Wed 2017-03-15 19:01:17 IRST; 10s 
ago
  Process: 9377 ExecStart=/usr/sbin/kamailio -P /var/run/kamailio/kamailio.pid 
-f $CFGFILE -m $SHM_MEMORY -M $PKG_MEMORY -u $USER -g $GROUP (code=exited, 
status=255)
 Main PID: 1576 (code=exited, status=0/SUCCESS)

Mar 15 19:01:17 kamailio-debian kamailio[9377]: ERROR:  
[core/modparam.c:152]: set_mod_param_regex(): No module matching  
found
Mar 15 19:01:17 kamailio-debian kamailio[9377]: CRITICAL:  
[core/cfg.y:3404]: yyerror_at(): parse error in config file 
/etc/kamailio/kamailio.cfg, line 103, column 72: Can't set module parameter
Mar 15 19:01:17 kamailio-debian kamailio[9377]: ERROR:  
[core/modparam.c:141]: set_mod_param_regex(): parameter  
of type <2> not found in module 
Mar 15 19:01:17 kamailio-debian kamailio[9377]: CRITICAL:  
[core/cfg.y:3404]: yyerror_at(): parse error in config file 
/etc/kamailio/kamailio.cfg, line 135, column 50: Can't set module parameter
Mar 15 19:01:17 kamailio-debian kamailio[9377]: ERROR: bad config file (4 
errors)
Mar 15 19:01:17 kamailio-debian kamailio[9377]: INFO:  
[core/sctp_core.c:53]: sctp_core_destroy(): SCTP API not initialized
Mar 15 19:01:17 kamailio-debian kamailio[9377]: loading modules under config 
path: /usr/lib/x86_64-linux-gnu/kamailio/modules/
Mar 15 19:01:17 kamailio-debian systemd[1]: kamailio.service: control process 
exited, code=exited status=255
Mar 15 19:01:17 kamailio-debian systemd[1]: Failed to start Kamailio (OpenSER) 
- the Open Source SIP Server.
Mar 15 19:01:17 kamailio-debian systemd[1]: Unit kamailio.service entered 
failed state.



  *   kamailio.cfg:
# *** To run in debug mode:
# - define WITH_DEBUG
#

#!ifndef DBURL
#!define DBURL "mysql://kamailio:kamailiorw@localhost/kamailio"
#!endif

### Global Parameters #

#!ifdef WITH_DEBUG
debug=4
log_stderror=yes
#!else
debug=2
log_stderror=no
#!endif

memdbg=5
memlog=5

# log_facility=LOG_LOCAL0
# Ds increasing debug...
debug=2

fork=yes
children=4

/* comment the next line to enable TCP */
disable_tcp=yes

/* uncomment the next line to disable the auto discovery of local aliases
   based on revers DNS on IPs (default on) */
auto_aliases=no

/* add local domain aliases */
# alias="mysipserver.com"

port=5060

/* uncomment and configure the following line if you want Kamailio to
   bind on a specific interface/port/proto (default bind on all available) */
# listen=udp:0.0.0.0:5060
# listen=127.0.0.1:5060


sip_warning=no

### Modules Section 

# set paths to location of modules (to sources or installation folders)
mpath="/usr/lib/x86_64-linux-gnu/kamailio/modules/"

#!ifdef WITH_MYSQL
loadmodule "db_mysql.so"
#!endif

loadmodule "mi_fifo.so"
loadmodule "kex.so"
loadmodule "tm.so"
loadmodule "tmx.so"
loadmodule "sl.so"
loadmodule "rr.so"
loadmodule "pv.so"
loadmodule "maxfwd.so"
loadmodule "textops.so"
loadmodule "siputils.so"
loadmodule "xlog.so"
loadmodule "sanity.so"
loadmodule "ctl.so"
loadmodule "mi_rpc.so"
loadmodule "acc.so"
loadmodule "dispatcher.so"


# - setting module-specific parameters ---


# - mi_fifo params -
modparam("jsonrpcs", "fifo_name", "/var/run/kamailio/kamailio_rpc.fifo")


# - rr params -
# add value to ;lr param to cope with most of the UAs
modparam("rr", "enable_full_lr", 1)
# do not append from tag to the RR (no need for this script)
modparam("rr", "append_fromtag", 0)


# - acc params -
modparam("acc", "log_flag", 1)
modparam("acc", "failed_transaction_flag", 3)
modparam("acc", "log_extra",

"src_user=$fU;src_domain=$fd;dst_ouser=$tU;dst_user=$rU;dst_domain=$rd;src_ip=$si")

# - tm params -
modparam("tm", "fr_timer", 2000)
modparam("tm", "fr_inv_timer", 4)

# - dispatcher params -
# modparam("dispatcher", "db_url", DBURL)
# modparam("dispatcher", "table_name", "dispatcher")

modparam("dispatcher", "list_file", "/etc/kamailio/dispatcher.list")
modparam("dispatcher", "flags", 2)
modparam("dispatcher", "dst_avp", "$avp(AVP_DST)")
modparam("dispatcher", "grp_a

[SR-Users] Search for kamailio PERL module for 5.0 level

[Ginhoux, Patrick]

Hi,

I'm a beginner in the use of kamailio product, so I try below to explain my 
problem with my words:


1)  PERL module issue :


Some years ago a SIP Router proxy running RedHat 6.2 was developped using the 
kamailio version 3.3 and the following packages used  :

kamailio-3.3.2-1.1.1.x86_64.rpm
kamailio-snmpstats-3.3.2-1.1.1.x86_64.rpm
kamailio-mysql-3.3.2-1.1.1.x86_64.rpm
kamailio-perl-3.3.2-1.1.1.x86_64.rpm

We have the project to migrate this SIP Proxy to RedHat 7.1 and used the latest 
Kamailio v5.0.0 Release:

kamailio-5.0.0-24.1.x86_64.rpm
kamailio-mysql-5.0.0-24.1.x86_64.rpm
kamailio-snmpstats-5.0.0-24.1.x86_64.rpm

However I don't find the kamalio-perl package for RedHat 7.1. I see that the 
perl module has been renamed to 'app_perl' but I don't find it either for 
kamailio 5.0.0.


2)  Kamailio.cfg script



Our proxy used the kamailio.cfg from the sample  of the 3.3.3 release.



So can I reuse the same 3.3.3 kamailio.cfg file with the 5.0.0 release or 
should I migrate (rewrite it) from the 5.0.0 sample ?

So I'm looking for some help on these issues.

Is there people that had this case ?

Thanks in advance for any answer.

Cordialement
Patrick GINHOUX

PS : I just create my account today but don't get the email to validate it.

___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users