sr-users March 2017

sr-users@lists.kamailio.org

87 participants
110 discussions

by Kordován Szabolcs

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.

7 years, 1 month

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

by 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(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

7 years, 1 month

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

by 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(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

7 years, 1 month

ACC - Cdr enabled

by Diego Nadares

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

7 years, 1 month

Is File Sharing between two Extensions Possible?

by Shahid Mehmood

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

7 years, 1 month

cisco spa502g issues

by ben＠wtf.com.au

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.

7 years, 1 month

Generate extra cdr per dialog

by Diego Nadares

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.

7 years, 1 month

f_malloc WARNINGS in syslog

by Diego Nadares

Hi Guys, I'm seeing a lot of warnings in my syslog. Is this normal? Or maybe I am doing something wrong in my cfg? .... Mar 16 17:11:47 dwsipm03 ./kamailio[26226]: WARNING: <core> [mem/f_malloc.c:444]: fm_malloc(): fm_malloc(0x7f68e5199010, 8) called from nathelper: nathelper.c: nh_timer(2078) Mar 16 17:11:47 dwsipm03 ./kamailio[26226]: WARNING: <core> [mem/f_malloc.c:527]: fm_malloc(): fm_malloc(0x7f68e5199010, 8) returns address 0x7f68e52a2d50 Mar 16 17:11:47 dwsipm03 ./kamailio[26226]: WARNING: <core> [mem/f_malloc.c:588]: fm_free(): fm_free(0x7f68e5199010, 0x7f68e52a2d50), called from nathelper: nathelper.c: nh_timer(2222) Mar 16 17:11:47 dwsipm03 ./kamailio[26226]: WARNING: <core> [mem/f_malloc.c:607]: fm_free(): fm_free: freeing block alloc'ed from nathelper: nathelper.c: nh_timer(2078) ..... Mar 16 17:15:44 dwsipm03 ./kamailio[26210]: WARNING: <core> [mem/f_malloc.c:607]: fm_free(): fm_free: freeing block alloc'ed from core: xavp.c: xavp_new_value(94) Mar 16 17:15:44 dwsipm03 ./kamailio[26210]: WARNING: <core> [mem/f_malloc.c:588]: fm_free(): fm_free(0x7f68d9d51000, 0x7f68da069ca8), called from tm: h_table.c: free_cell_helper(246) Mar 16 17:15:44 dwsipm03 ./kamailio[26210]: WARNING: <core> [mem/f_malloc.c:607]: fm_free(): fm_free: freeing block alloc'ed from tm: h_table.c: build_cell(317) Mar 16 17:15:44 dwsipm03 ./kamailio[26210]: WARNING: <core> [mem/f_malloc.c:588]: fm_free(): fm_free(0x7f68d9d51000, 0x7f68da031f00), called from tm: h_table.c: free_cell_helper(150) .... Thanks in advance. Diego

7 years, 1 month

ht_db_load_table(): key type must be string (type=6)

by 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> [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

7 years, 1 month

Error on <ds_probing_threshhold> of type <2> not found in module <dispatcher> and SCTP API Not initialized

by 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> [core/modparam.c:141]: set_mod_param_regex(): parameter <ds_probing_threshhold> of type <2> not found in module <dispatcher> Mar 16 12:56:45 vm-vse02-siprouter1 kamailio[6644]: 0(6652) CRITICAL: <core> [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> [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> [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

7 years, 1 month

← Newer
1
2
3
4
5
6
7
8
9
10
11
Older →

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

sr-users March 2017