March 2017 - sr-users - kamailio.org

Alternative of SIPp for WebRTC2SIP load-test
by Jade SZ 21 Mar '17

21 Mar '17

Hi Guys, SIPp is great in testing pure SIP udp/tcp/tls but I was wondering if there is a similar tool for stress testing Kamailio websocket2sip. I am trying to load-test webrtc2sip kamailio's implementation closest to the real scenario. One way would be to fork multiple process of webrtc2sip client in loop. But would really like to hear how are kamailio webrtc users/community load-testing it for benchmarking their servers. Also roughly how much CPS they have achieved using single kamailio with webrtc enabled (share server specs as well) Thanks in advance. Regards, JSZ

2 1

do we need high available IP for S-CSCF?
by Valentin Christoph 21 Mar '17

21 Mar '17

Hi all, Maybe I need a small hint. I have got a configuration of 2 S-CSCF instances (both kamailio 4.4.5 with S-CSCF configuration, each on a separate virtual machine) in load sharing mode (50:50). Both instances work on the same "scscf" data base, so that it is only one S-CSCF from a logical point of view. Now I get into troubles with registration: * P-CSCF sends REGISTER to first S-CSCF * First S-CSCF answers with 401 Unauthorized an challenges the UE. So far everything OK. * Second REGISTER is sent to second S-CSCF (DNS SRV Load Balancing). * Second S-CSCF answers again with 401 Unauthorized (Error) * This goes back and forth until UE gives up to register This problem exists sporadically (approx. every fifth registration). Now the question: is it worth to debug this configuration or should we rather switch to high available IP configuration (if we want to use kamailio)? What's your opinion/experiences? Thanks Christoph The information contained in this e-mail message is privileged and confidential and is for the exclusive use of the addressee. The person who receives this message and who is not the addressee, one of his employees or an agent entitled to hand it over to the addressee, is informed that he may not use, disclose or reproduce the contents thereof, and is kindly asked to notify the sender and delete the e-mail immediately.

1 0

Siremis 4.3.0 with Apache 2.4
by kai.ohnacker＠cbc.de 21 Mar '17

21 Mar '17

Hello Community, I installed the Kamailio 4.4 and try to install the Siremis GUI based on apache 2.4. If I try to start the Siremis Wizard, the Webserver display the following line: "location.href='$url'"; exit; } ?>". The starting page of apache 2.4 is working fine, but the /siremis page doesn't. Due the installation I take the dedicated apache 2.4 commands. Are there some further requirements? Some ideas? OS: Ubuntu 16.04 Thanks a lot. Cheers, Kai

2 2

No cdr after Kamailio 5.0 restart
by Kordován Szabolcs 21 Mar '17

21 Mar '17

Hi, I use acc module for create cdr into db and also make acc log into db. After restart Kamailio cdr won't be created but acc log will be inserted into db. In the syslog also I see just the acc log. The dialog will be remove from db. I have read many threads. I know that it should work. Thanks for help! Regards, Szabolcs >From my configs: #!define FLT_ACC 1 #!define FLT_ACCMISSED 2 #!define FLT_ACCFAILED 3 modparam("acc", "db_url", DBURL) modparam("acc", "db_flag", FLT_ACC) modparam("acc", "db_missed_flag", FLT_ACCMISSED) modparam("acc", "db_extra", "src_user=$fU;src_domain=$fd;dst_ouser=$tU;dst_user=$rU;dst_domain=$rd;src_ip=$si") modparam("acc", "log_level", 3) modparam("acc", "log_flag", FLT_ACC) modparam("acc", "log_missed_flag", FLT_ACCMISSED) modparam("acc", "report_ack", 1) modparam("acc", "report_cancels", 1) modparam("acc", "early_media", 1) modparam("acc", "failed_transaction_flag", FLT_ACCFAILED) modparam("acc", "acc_prepare_always", 1) modparam("acc", "time_mode", 1) modparam("acc", "time_attr", "seconds") modparam("acc", "time_exten", "microsecs") modparam("acc", "reason_from_hf", 1) modparam("acc", "cdr_enable", 1) modparam("acc", "cdr_expired_dlg_enable", 1) modparam("acc", "cdr_start_on_confirmed", 1) modparam("acc", "cdrs_table", "acc_cdrs") modparam("acc", "cdr_on_failed", 1) modparam("acc", "cdr_extra", "callid=$ci;src_user=$dlg_var(fU);src_domain=$dlg_var(fd);dst_ouser=$dlg_var(tU);dst_user=$dlg_var(rU);dst_domain=$dlg_var(rd);src_ip=$dlg_var(si);peer_in=$dlg_var(peerin);peer_out=$dlg_var(peerout)") request_route { <------> <------>$var(loose) = loose_route(); <------>$var(check_trans) = t_check_trans(); <------>sip_trace(); <------>setflag(FLT_SIPTRACE); <------>dlg_manage(); <------># handle retransmissions <------>if(t_precheck_trans()) { <------> xlogl("LOG_LOCAL0", "L_ALERT", "================== kamaty $rm route $ci ==== $rm ==== precheck_trans exit\n"); <------> exit; <------>} <------>if(is_method("OPTIONS")) {. <------> # send reply for each options request. <------> sl_send_reply("200", "ok");. <------> exit();. <------>} <------># CANCEL processing <------>if (is_method("CANCEL")) { <------><------>if (t_check_trans()) { <------><------> route(RELAY); <------><------>} <------><------>exit; <------>} <------>if ( is_method("ACK") ) { <------><------>if ( $var(check_trans) ) { <------><------> route(RELAY); <------><------>} <------><------>exit; <------>} <------>if (is_method("BYE")) { <------> if ($var(loose)) { <------><------>setflag(FLT_ACC); # do accounting ... <------><------>setflag(FLT_ACCFAILED); # ... even if the transaction fails <------><------>setflag(FLT_ACCMISSED); <------><------>route(RELAY); <------> <-->exit; <------> } <------> exit; <------>} etc.

5 10

Re: [SR-Users] ht_db_load_table(): key type must be string (type=6)
by Ginhoux, Patrick 21 Mar '17

21 Mar '17

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(a)lists.sip-router.org) <sr-users(a)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(a)lists.sip-router.org<mailto:sr-users@lists.sip-router.org>) <sr-users(a)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> [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> [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> [core/modparam.c:141]: set_mod_param_regex(): parameter <fetch_rows> of type <1> not found in module <htable> Mar 17 15:26:21 vm-vse02-siprouter1 kamailio[1452]: 0(1460) CRITICAL: <core> [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> [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> [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

1 0

Re: [SR-Users] ht_db_load_table(): key type must be string (type=6)
by Ginhoux, Patrick 20 Mar '17

20 Mar '17

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(a)lists.sip-router.org) <sr-users(a)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> [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> [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> [core/modparam.c:141]: set_mod_param_regex(): parameter <fetch_rows> of type <1> not found in module <htable> Mar 17 15:26:21 vm-vse02-siprouter1 kamailio[1452]: 0(1460) CRITICAL: <core> [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> [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> [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

1 0

ACC - Cdr enabled
by Diego Nadares 20 Mar '17

20 Mar '17

Hi guys, I have configured to use cdr with extra fields modparam("acc", "cdr_extra", * "sip_code=$rs;sip_reason=$rr;"* "hangup_src=$dlg_var(hangup_disposition);" "prefix=$dlg_var(prefix);gos=$dlg_var(gos);endpoint_type=$ dlg_var(endpoint_type);" "ip_a=$dlg_var(ip_a);ip_b=$dlg_var(ip_b);" Is this the right way to always save the hangup cause? Or is another better way? Because, when call is finished with a bye both fields are empty. The other thing is that I need to save, start_time and end_time with seconds.microseconds (1490013250.601707). Is this possible? Thanks! Diego

2 5

Is File Sharing between two Extensions Possible?
by Shahid Mehmood 20 Mar '17

20 Mar '17

Dear all, I want to share (any kind of) files between two extensions. Is it possible? If it is, then how ??? please elaborate with example. -- Shahid Mehmood

1 0

cisco spa502g issues
by ben＠wtf.com.au 19 Mar '17

19 Mar '17

Hi guys, we have a bunch of SIP phones behind a fire wall, with our kamalio server out on the internet. Most of them are the older SPA92x series, but we have some new SPA502g's. We have no problems calling between 92x and 502's. How ever the 502's calling each other do not get voice path. I have noticed that the phones REGISTER differently: AOR:: 5546@<our domain> Contact:: sip:5546@<OUR OFFICE IP>:1032 Q= Expires:: 180 Callid:: 4754c4f9-c67e1018(a)10.0.41.29 Cseq:: 43112 User-agent:: Cisco/SPA502G-7.6.2a State:: CS_DIRTY Flags:: 0 Cflag:: 0 Socket:: udp:<OUR SR IP>:5060 Methods:: 6815 AOR:: 5590(a)sip.skunkworks.net.au Contact:: sip:5590@10.0.41.14:5060 Q= Expires:: 1154 Callid:: 24435738-224b06db(a)10.0.41.14 Cseq:: 8012 User-agent:: Linksys/SPA921-5.1.8 Received:: sip:<OUR OFFICE IP>:1026 State:: CS_SYNC Flags:: 0 Cflag:: 64 Socket:: udp:<OUR SR IP>:5060 Methods:: 4767 The older 921 has its private IP in the contact, where as the newer 502 has the external IP of our office in the contact. Our file wall is a Watchguard T-10 (latest updates etc) with the SIP-ALG running. Any thoughts on where to start looking ? Cheers, Ben.

3 4

Generate extra cdr per dialog
by Diego Nadares 18 Mar '17

18 Mar '17

Hi Guys, I'm using acc module for accounting with the following conf: .... modparam("acc", "cdr_enable", 1) modparam("acc", "cdr_expired_dlg_enable", 1) modparam("acc", "cdr_start_on_confirmed", 1) modparam("acc", "cdr_facility", "LOG_LOCAL1") modparam("acc", "cdr_end_id", "end_time_dt") modparam("acc", "cdr_extra", "sip_code=$rs;sip_reason=$rr;" "hangup_src=$dlg_var(hangup_disposition);" "prefix=$dlg_var(prefix);gos=$dlg_var(gos);endpoint_type=$dlg_var(endpoint_type);" "ip_a=$dlg_var(ip_a);ip_b=$dlg_var(ip_b);" .... It works fine. At the end of the call the cdr is generated ok. BUT In MANAGE_FAILURE, If the first call failed and if there are more dests, we are generating a new call in the same dialog (Some of the dialog vars like ip_a, ip_b can change for the new dest ) I would like to generate both cdrs, the one that failed and the new one (with some dlg vars with new data). if(rtjson_next_route() && t_check_status("503")) { $avp(current_route) = $avp(current_route)+1; t_on_branch("MANAGE_BRANCH"); t_on_failure("MANAGE_FAILURE"); route(RELAY); exit; } Right now just the last call cdr is saved. I all ready made this work with db_acc (transaction oriented) but I think in my case it will be more reliable with cdr (dialog oriented). Thanks in advance! Diego.

1 1