sr-users August 2018

sr-users@lists.kamailio.org

73 participants
114 discussions

invalid version 8 for table aliases found, expected 9

by Abdulaziz Alghosh

Hi everyone, i am trying to start kamailio 5.1.4 after the migration from Kamailio 3.0.3 but getting newly the following error: ERROR: <core> [db.c:450]: db_check_table_version(): invalid version 8 for table aliases found, expected 9 (check table structure and table "version") Allegedlly, this error is because of a wrong version of "aliases" table. I followed the Upgrade process starting from 3.0.3 till 5.1.x and I altered the structure of my aliase table accordinglly. The last new version of aliases is 8 as it is described at the upgrade from 4.2.x to 4.3.0 Even though, the error here says that the newest version is 9: May someone help me to find out if the aliases table's structure was renewed in between ?? Is there any modification in the data types? Thanks in advance Abdulaziz

5 years, 8 months

ERROR: PID file /var/run/kamailio.pid does not exist -- Kamailio start failed

by Abdulaziz Alghosh

Greetings, i am at the final stages of emigrating from kamailio 3.0.3 to 5.1.0 including our own module. Unluckily, after writing the command " kamctl start", the following error is popping up: * PID file /var/run/kamailio.pid does not exist -- Kamailio start failed* Thus, I used the command " kamailio -M 8 -E -e -dd " to get more debugging Info and the output is detailing the following: 0(10334) ERROR: db_mysql [km_my_con.c:129]: db_mysql_new_connection(): driver error: Can't connect to MySQL server on '192.168.1.207' (4) 0(10334) ERROR: <core> [db.c:318]: db_do_init2(): could not add connection to the pool 0(10334) ERROR: ABDUL_functions [ABDUL_chk.c:1069]: init_db(): failed to connect database URL=mysql://ABDUL:ABDUL@192.168.1.207/ABDUL 0(10334) ERROR: ABDUL_functions [ABDUL_functions_mod.c:296]: mod_init(): Module ABDUL_functions not correktly initialized, pid[10334] 0(10334) ERROR: <core> [core/sr_module.c:991]: init_mod(): Error while initializing module ABDUL_functions (//lib64/kamailio/modules/ABDUL_functions.so) Seemingly the error relates to old databases url ( "URL=mysql:// ABDUL:ABDUL@192.168.1.207/ABDUL" ) inside an old Kamailio.cfg file from my 3.0.3 package which I put under another different directory. This old Kamailio.cfg file #includes my own module, so he is exporting this url. Consequently, my module is trying to connect again to this databases. I do not know why both kamailio.cfg (new: /etc/kamailio/kamailio.cfg and old one out of /etc/kamailio) are both seen for kamctl or (/sbin/kamailio). I know that my new url inside the new /etc/kamailio/kamailio.cfg is read and connected but again not sure why my hidden old kamailio.cfg is still being read as well. the attached shows my init file for "SUSE Linux Enterprise Server 11 (x86_64)" and my used kamailio *default *file under /etc/default. Thanks in advance and best regards Abdulaziz

5 years, 8 months

help

by Pravin .

Hello Team, I want to install Kamailio SIP server on centOS server...do we need to download kamailio ISO file and install on server..pls provide the installation procedure/guidelines. Regards Pravin

5 years, 8 months

Dialplan priority

by igor.potjevlesch＠gmail.com

Hello, I'm not sure to understand in which situation "pr" value is used. For example: if I have two identical rules except pr value: 1 with 1 and the second with 2, then the rule with pr 2 is never used. Someone can help me to understand? Thank you. The finality I'd like to accomplish is having some kind of load balacing between two values into "repl_exp" with the same inputs conditions. Thank you. Regards, Igor.

5 years, 8 months

Call Transfer Scenario Using Freeswitch

by Sunil More

Hi All, I am using kamailio and freeswitch in my setup. While all users are registered on Kamailio, calls are routed to Freeswitch back to kamailio and then upstream providers. I can make user to user calls but in cases of transfer I am stuck. I am using a Polycom IP phone to test this scenario. While I initiate a attended transfer and click on transfer all the legs hangup. When I register all users on Freeswitch this works well. I am missing something on Kamailio side. Please point me in the right direction. Thanking You, Sunil More Ph : 9503338275

5 years, 8 months

Enabling tcp_write_buf

by Gholamreza Sabery

Hi, In the documentation of "tcp_wq_max" option it is written that : > It has no effect if *tcp_write_buf *is not enabled. > > The interesting fact is that, there is not description of what it is and how one can enable it. There is even a question about it in the mailing lists: https://lists.kamailio.org//pipermail/sr-dev/2011-June/011521.html It seems that it is an inaccuracy in the documentation. If there is such an option how to enable it? Can anyone tell? Regards

5 years, 8 months

Best practice/routing block for TCP connection errors to UAC?

by Anthony Alba

HI SR-Users Scenario: clients registered by TCP/TLS dropping off the network, kamailio stil thinks the client is registered and relays the INTIVE. The error occurs at the TCP layer so no failure route is called. ERROR: <core> [core/tcp_main.c:2690]: tcpconn_1st_send(): connect 127.0.0.1:48338 failed (RST) Connection refused ERROR: <core> [core/tcp_main.c:2700]: tcpconn_1st_send(): 127.0.0.1:48338: connect & send for 0x7f5494e906c0 failed: Connection refused (111) ERROR: tm [../../core/forward.h:251]: msg_send_buffer(): tcp_send failed WARNING: tm [t_fwd.c:1567]: t_send_branch(): sending request on branch 0 failed ERROR: sl [sl_funcs.c:362]: sl_reply_error(): stateless error reply used: I'm terribly sorry, server error occurred (1/SL) I want to send the caller instead a graceful failure route type message as if the callee is not registered (404/486/603/408 type) but don't understand how to hook a routing block for TCP errors. Anthony

5 years, 8 months

Fail to reload htable

by Soltanici Ilie

I'm trying to reload a hash table but receiving an error: error: 500 - Mtree reload failed [root@kamailio]# /usr/local/sbin/kamcmd htable.listTables { name: auth dbtable: dbmode: 0 expire: 0 updateexpire: 1 size: 256 dmqreplicate: 0 } [root@kamailio]# /usr/local/sbin/kamcmd htable.dump auth { entry: 69 size: 1 slot: { { name: username::8.8.8.8 value: 0 type: int } } } [root@kamailio]# /usr/local/sbin/kamcmd htable.reload auth error: 500 - Mtree reload failed [root@kamailio]# /usr/local/sbin/kamailio -v version: kamailio 5.1.4 (x86_64/linux) e8b2bf

5 years, 8 months

Kamailio 5.1 Nathelper sipping on different transport protocols.

by Володимир Іванець

Hello everyone! I have system with Kamailio v5.1 which needs to send OPTIONS packets to all active clients. Here is full Nathelper module configuration: *modparam("nathelper", "received_avp", "$avp(s:received)")* *modparam("nathelper", "natping_interval", 30)* *modparam("nathelper", "ping_nated_only", 0)* *modparam("nathelper", "sipping_bflag", FLB_SIPPING)* *modparam("nathelper", "sipping_from", "sip:pinger@kamailio.org <sip%3Apinger(a)kamailio.org>")* It works fine if client is connected over UDP. But as soon as I will switch to TCP or register with client that uses WS, Kamailio stops generating OPTIONS. Does anyone know if it is correct behavior or something is wrong? Thanks a lot!

5 years, 8 months

remove_hf function in INVITE message

by Mojtaba

Today i encounter with strange issue in SIP signalling in Kamailio, In INVITE message, I just change Contact Header and relay message to destination, But the message is like this: 192.168.122.245.4080 > 192.168.122.174.5060: [bad udp cksum 0x7b5e -> 0x3a4d!] SIP, length: 1104 INVITE sip:8000@r-kh.com;transport=UDP SIP/2.0 Record-Route: <sip:192.168.122.245:4080;lr;ftag=8e47e95e;nat=yes> Via: SIP/2.0/UDP 192.168.122.245:4080;branch=z9hG4bK14d7.dc974309aba269b24213204d3ea085e2.0 Via: SIP/2.0/UDP 192.168.122.1:36853;rport=36853;branch=z9hG4bK-d8754z-423b431a3ebc8a22-1---d8754z- Max-Forwards: 69 sip:7000@192.168.122.1:36853;transport=UDP;alias=192.168.122.1~36853~1To: <sip:8000@r-kh.com;transport=UDP> From: <sip:7000@r-kh.com;transport=UDP>;tag=8e47e95e Call-ID: YTZmYTJmYzg0ZDNiMjM2OGUxZGYwNzg4OWY1ZmIxYzc. CSeq: 1 INVITE Allow: INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, MESSAGE, OPTIONS, INFO, SUBSCRIBE Content-Type: application/sdp Supported: replaces, norefersub, extended-refer, timer, X-cisco-serviceuri User-Agent: Z 3.3.25608 r25552 Allow-Events: presence, kpml Content-Length: 241 <SDP Body> The code in Kamailio is: #!ifdef WITH_SBC_NASIM #if the Invite request is MO, forward it to Asterisk . if (is_method("INVITE") && $si!="192.168.122.245") { xlog("L_INFO", "The Invite message from $si:$sp, Forwart to Asterisk. <192.168.122.174:5060>.\n"); remove_hf("Contact"); append_hf("Contact:sip:$fU@sbc.r-kh.com\r\n"); $du = "sip:192.168.122.174:5060"; } #!endif Be notice that, i have the same procedure in REGISTER message, But it is work correct, if(is_method("REGISTER")) { xlog("L_INFO", "forward register to Asterisk\n"); remove_hf("Contact"); append_hf("Contact:sip:$fU@sbc.r-kh.com\r\n"); rewriteuri("sip:r-kh.com"); $du = "sip:192.168.122.174:5060"; route(RELAY); } Let me know what is the problem? -- --Mojtaba Esfandiari.S

5 years, 8 months

← Newer
1
2
3
4
5
6
7
8
9
...
12
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 August 2018