sr-users May 2016

sr-users@lists.kamailio.org

86 participants
127 discussions

Kamailio 5.0 - Routing blocks in Lua or Python
by Daniel-Constantin Mierla 04 May '16

04 May '16

Hello, I want to announce that the framework (named kemi) which allows writing the routing blocks in an embedded language is already in place. Lua or Python can be use as alternative to the native scripting language to write the routing blocks. More details can be found at: - https://www.kamailio.org/wiki/devel/config-engines Example of scripts that offer more or less same features as etc/kamailio-basic.cfg are available in source tree at examples/kemi. For convenience of reading, here are the links to git repository: - the common file setting global and modules parameters as well as specifying the config engine: https://github.com/kamailio/kamailio/blob/master/examples/kemi/kamailio-bas… - the part of config with routing blocks in native language: https://github.com/kamailio/kamailio/blob/master/examples/kemi/kamailio-bas… - the part of config with routing blocks in Lua: https://github.com/kamailio/kamailio/blob/master/examples/kemi/kamailio-bas… - the part of config with routing blocks in Python: https://github.com/kamailio/kamailio/blob/master/examples/kemi/kamailio-bas… You can compare the last three above and see how different or similar they look for providing same SIP routing features using different languages. A lot of modules need to export now functions to embedded config interface, which is quite straightforward: https://www.kamailio.org/wiki/devel/config-engines#exporting_functions_to_k… The main missing part is dealing with event_route blocks -- I will send a separate email to discuss that. Interesting that some incipient performance tests to compare the interpreters show good results for using especially Lua but also Python: - https://www.kamailio.org/wiki/devel/config-engines#interpreters_performances Anyone willing to help can start exporting functions from modules to embedded interface or test some more complex configs in Lua or Python. Cheers, Daniel -- Daniel-Constantin Mierla http://www.asipto.com http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda Kamailio World Conference, Berlin, May 18-20, 2016 - http://www.kamailioworld.com

1 0

t_on_branch_failure never called AND t_relay never fails in a, forked scenario
by Tristan Mahé 03 May '16

03 May '16

Hi fellow kamailio users, I'm playing actually with t_on_branch_failure, in a simultaneous forking scenario ( lookup("location") returns multiple contacts ). Any idea on how to get those "on_branch_failure" working ? Thanks in Advance ! * Test by putting failure_exec_mode: - at 1 => no branch failure being called, never. - at 0 => t_relay does not fail if a single branch answers the transaction, even if all other branches are failing. * Test by moving the t_on_branch_failure("manage_branch_failure"); line before or after the lookup("location") or on a _on_branch route to set it per branch. - The on_route branch are executed, but never the failure one. - tried also with failure_exec_mode = 0 or 1. * Using set_forward_no_connect, I can see in the logs a "Sending to branch X failed" but no failure route being executed. Without it, nothing in the logs indicating that the branch has timeout. * Config extract: # auto-discard branches from previous serial forking leg modparam("tm", "failure_reply_mode", 3) # 3 by default # default retransmission timeout: 30sec modparam("tm", "fr_timer", 30000) # default invite retransmission timeout after 1xx: 120sec modparam("tm", "fr_inv_timer", 120000) modparam("tm", "reparse_on_dns_failover", 0) # 1: Allow branches to have a per branch failure route # 0: t_relay should fail if a branch fail modparam("tm", "failure_exec_mode", 1) # Allow locally generated 408 to be forgotten in case a reply is received. #modparam("tm", "faked_reply_prio", 2000) # USER location service route[LOCATION] { t_on_branch_failure("manage_branch_failure"); if (!lookup("location")) { .... } # Let's get back after 2.5s if no 100/Trying received. t_set_fr(0, 2500); # set_forward_no_connect(); #t_on_branch("SET_BRANCH_FAILURE"); route(RELAY); exit; } route[RELAY] { .... if (!t_relay()) { xlog("L_WARN","$rm|$ci|$fu|$tu|RELAY_FAILED"); sl_reply_error(); } exit(); } # set failure route per branch branch_route[SET_BRANCH_FAILURE] { xlog("L_WARN","$rm|$ci|$fu|$tu|SETTING_BrANCH_FAILURE_ROUTE"); t_on_branch_failure("manage_branch_failure"); } # manage failure routing cases per branch event_route[tm:branch-failure:manage_branch_failure] { xlog("L_WARN","$rm|$ci|$fu|$tu[$avp(dest_to)]|MANAGE_BRANCH_FAILURE"); }

3 2

set_body_multipart and memory leak
by Sergey Basov 03 May '16

03 May '16

Hi, All. I have some problems with pkg_memory leak. After each call used private memory of the "udp receiver" process increases at 2500 bytes. On test environment I hav set it to 2Mbyte, but it is full after 700 calls. I need to modify SDP in invite and other packets. When I do ==================================================== if(has_body("application/sdp")) set_body_multipart(); if (msg_apply_changes()) { xlog("L_INFO", "ISUP 1 Changes Applied Succesfully"); } } record_route(); dlg_manage route(RELAY); ==================================================== Debug from kamailio: Apr 21 15:38:20 sip1 /usr/sbin/kamailio-sipt[17775]: DEBUG: textops [textops.c:2627]: has_body_f(): content type is 196611 Apr 21 15:38:20 sip1 /usr/sbin/kamailio-sipt[17775]: DEBUG: textops [textops.c:1577]: set_multibody_helper(): delimiter<17>:[unique-boundary-1] Apr 21 15:38:20 sip1 /usr/sbin/kamailio-sipt[17775]: DEBUG: textops [textops.c:1486]: generate_boundary(): adding final CRLF+CRLF Apr 21 15:38:20 sip1 /usr/sbin/kamailio-sipt[17775]: DEBUG: textops [textops.c:1714]: set_multibody_helper(): content-type<44>:[multipart/mixed;boundary="unique-boundary-1"] Apr 21 15:38:20 sip1 /usr/sbin/kamailio-sipt[17775]: DEBUG: textops [textops.c:1766]: set_multibody_helper(): set flag FL_BODY_MULTIPART Apr 21 15:38:20 sip1 /usr/sbin/kamailio-sipt[17775]: ERROR: <core> [msg_translator.c:1691]: get_boundary(): Content-Type hdr has no params Apr 21 15:38:20 sip1 /usr/sbin/kamailio-sipt[17775]: WARNING: <core> [msg_translator.c:1954]: build_req_buf_from_sip_req(): check_boundaries error Apr 21 15:38:20 sip1 /usr/sbin/kamailio-sipt[17775]: DEBUG: <core> [msg_translator.c:422]: clen_builder(): content-length: 251 (251) Apr 21 15:38:20 sip1 /usr/sbin/kamailio-sipt[17775]: DEBUG: textopsx [textopsx.c:231]: msg_apply_changes_f(): SIP message content updated - reparsing Apr 21 15:38:20 sip1 /usr/sbin/kamailio-sipt[17775]: DEBUG: <core> [parser/msg_parser.c:608]: parse_msg(): SIP Request: Apr 21 15:38:20 sip1 /usr/sbin/kamailio-sipt[17775]: DEBUG: <core> [parser/msg_parser.c:610]: parse_msg(): method: <INVITE> Apr 21 15:38:20 sip1 /usr/sbin/kamailio-sipt[17775]: DEBUG: <core> [parser/msg_parser.c:612]: parse_msg(): uri: <sip:0637304494@10.56.42.27:5070;user=phone> Apr 21 15:38:20 sip1 /usr/sbin/kamailio-sipt[17775]: DEBUG: <core> [parser/msg_parser.c:614]: parse_msg(): version: <SIP/2.0> Apr 21 15:38:20 sip1 /usr/sbin/kamailio-sipt[17775]: DEBUG: <core> [parser/parse_via.c:1254]: parse_via_param(): Found param type 232, <branch> = <z9hG4bK09e6.2654d2382f7c4e4fb8bb62fe85f62dfa.0>; state=6 Apr 21 15:38:20 sip1 /usr/sbin/kamailio-sipt[17775]: DEBUG: <core> [parser/parse_via.c:1254]: parse_via_param(): Found param type 236, <i> = <1>; state=16 Apr 21 15:38:20 sip1 /usr/sbin/kamailio-sipt[17775]: DEBUG: <core> [parser/parse_via.c:2642]: parse_via(): end of header reached, state=5 Apr 21 15:38:20 sip1 /usr/sbin/kamailio-sipt[17775]: DEBUG: <core> [parser/msg_parser.c:496]: parse_headers(): parse_headers: Via found, flags=2 Apr 21 15:38:20 sip1 /usr/sbin/kamailio-sipt[17775]: DEBUG: <core> [parser/msg_parser.c:498]: parse_headers(): parse_headers: this is the first via Apr 21 15:38:20 sip1 /usr/sbin/kamailio-sipt[17775]: INFO: <script>: ISUP 1 Changes Applied Succesfully Apr 21 15:38:20 sip1 /usr/sbin/kamailio-sipt[17775]: DEBUG: <core> [parser/parse_via.c:1254]: parse_via_param(): Found param type 232, <branch> = <z9hG4bKsr-s7wTDLa0zUfsTql5zpl0zpl0z.lRD.zok.TLz.lSk2Fw1RY9PJYMxpdED.dED.aEG38LkpcsWhqMQr1v1bFAyJGCxrCoQdB71Mtceh52GpZKDpX3zRFAzVFJzhBLGpeJe.TczW7cDuT8GLs7O37vBbn6BbTfGhM2Gpl*>; state=16 Apr 21 15:38:20 sip1 /usr/sbin/kamailio-sipt[17775]: DEBUG: <core> [parser/parse_via.c:2642]: parse_via(): end of header reached, state=5 Apr 21 15:38:20 sip1 /usr/sbin/kamailio-sipt[17775]: DEBUG: <core> [parser/msg_parser.c:496]: parse_headers(): parse_headers: Via found, flags=ffffffffffffffff Apr 21 15:38:20 sip1 /usr/sbin/kamailio-sipt[17775]: DEBUG: <core> [parser/msg_parser.c:509]: parse_headers(): parse_headers: this is the second via Apr 21 15:38:20 sip1 /usr/sbin/kamailio-sipt[17775]: DEBUG: <core> [parser/parse_addr_spec.c:894]: parse_addr_spec(): end of header reached, state=10 Apr 21 15:38:20 sip1 /usr/sbin/kamailio-sipt[17775]: DEBUG: <core> [parser/msg_parser.c:173]: get_hdr_field(): DEBUG: get_hdr_field: <To> [46]; uri=[sip:0637304494@10.56.42.27:5070;user=phone] Apr 21 15:38:20 sip1 /usr/sbin/kamailio-sipt[17775]: DEBUG: <core> [parser/msg_parser.c:175]: get_hdr_field(): DEBUG: to body [<sip:0637304494@10.56.42.27:5070;user=phone>#015#012] Apr 21 15:38:20 sip1 /usr/sbin/kamailio-sipt[17775]: DEBUG: <core> [parser/msg_parser.c:153]: get_hdr_field(): get_hdr_field: cseq <CSeq>: <2> <INVITE> Apr 21 15:38:20 sip1 /usr/sbin/kamailio-sipt[17775]: DEBUG: <core> [parser/msg_parser.c:187]: get_hdr_field(): DEBUG: get_hdr_body : content_length=251 Apr 21 15:38:20 sip1 /usr/sbin/kamailio-sipt[17775]: DEBUG: <core> [parser/msg_parser.c:89]: get_hdr_field(): found end of header -- Best regards, Sergey Basov e-mail: sergey.v.basov(a)gmail.com

2 16

xmlrpc crash
by Juha Heinanen 03 May '16

03 May '16

i was sending some xmlrpc requests to kamailio and got crash. -- juha (gdb) where #0 0x00007f9c465da634 in __GI___libc_free (mem=0x17828c0) at malloc.c:2945 #1 0x00007f9c39e0b797 in collect_garbage () at xmlrpc.c:741 #2 0x00007f9c39e12669 in dispatch_rpc (msg=0x0, s1=0x17828b0 "ams", s2=0x7f9c46903628 <main_arena+8> "`\352w\001") at xmlrpc.c:2440 #3 0x000000000053c2c0 in do_action (h=0x7ffd17c562d0, a=0x7f9c46355c28, msg=0x7ffd17c563b0) at action.c:1060 #4 0x000000000053ad85 in run_actions (h=0x7f9c46903620 <main_arena>, a=0x17828b0, msg=0x7f9c46903628 <main_arena+8>) at action.c:1549 #5 0x00007f9c39e0d04b in em_receive_request (orig_msg=0x7f9c45cc43e8, new_buf=0x0, new_len=24651952) at xmlrpc.c:2303 #6 0x00007f9c39e14034 in process_xmlrpc (msg=0x7f9c45cc43e8) at xmlrpc.c:2385 #7 0x00000000004fdce3 in nonsip_msg_run_hooks (msg=0x7f9c45cc43e8) at nonsip_hooks.c:111 #8 0x0000000000549610 in receive_msg (buf=0x0, len=1171014632, rcv_info=0x7f9c3e4b0110) at receive.c:188 #9 0x00000000005cb97a in tcp_read_req (con=0x7f9c3e4b00f8, bytes_read=0x7ffd17c56e64, read_flags=0x7ffd17c56e68) at tcp_read.c:1418 #10 0x00000000005d0293 in handle_io (fm=0x7f9c3e4b00f8, events=10416, idx=-1) at tcp_read.c:1611 #11 0x00000000005d6bce in io_wait_loop_epoll (h=<optimized out>, t=<optimized out>, repeat=<optimized out>) at io_wait.h:1061 #12 tcp_receive_loop (unix_sock=1183856160) at tcp_read.c:1781 #13 0x00000000004d9df7 in tcp_init_children () at tcp_main.c:4788 #14 0x000000000050736f in main_loop () at main.c:1690 #15 0x000000000041cdbc in main (argc=0, argv=0x0) at main.c:2616

2 15

Kamailio Client-Server
by Shiv Patidar 02 May '16

02 May '16

hiii 1.We are writing our own SIP Client to test my Client i am using Kamailio server 2. So i am trying to map the identities used between Client and Server 3. If can possible can u please help me to the steps has to be follower to set identities common between Client and Server. 4. Or if u have some test code for client can u share the SIP message dump for test code so i can re-use the same for configuration my client code. Thank you

3 2

unixODBC failure/bug?
by Nagorny, Dimitry 02 May '16

02 May '16

Hi all, I am trying to use the unixODBC module to connect to MariaDB as a first step and then to test it to connect to MSSQL (please don't blame me on MSSQL...). I am using Kamailio 4.3.5 on CentOS7.2 fully patched. Here info about installed unixODBC: [root@r5dev-KAM1 ~]# yum list installed | grep unix unixODBC.x86_64 2.3.1-11.el7 @base unixODBC-devel.x86_64 2.3.1-11.el7 @base Which leads me to my possible problem that I can't start Kamailio with db_unixodbc.so because it is giving me this error: r5dev-KAM1 /usr/local/kamailio/sbin/kamailio[16307]: ERROR: <core> [db.c:203]: db_bind_mod(): Module db_unixODBC not found. Missing loadmodule? Followed by errors from modules depending on the DBURL are failing as well. Here my modules part: ... #!define DBURL "unixODBC://root:<passw>@localhost/MARIADB" ... # Module Path mpath="/usr/local/kamailio/lib64/kamailio/modules/" loadmodule "tls.so" # ----- tls params ----- modparam("tls", "config", "/usr/local/kamailio/etc/kamailio/tls.cfg") #loadmodule "db_mysql.so" loadmodule "db_unixodbc.so" ... I doublechecked that the module was compiled and is present: [root@r5dev-KAM1 ~]# ls -ll /usr/local/kamailio/lib64/kamailio/modules/ | grep unix -rwxr-xr-x. 1 root root 184451 28. Apr 08:56 db_unixodbc.so I tried to check the db.c and db_unixodbc.c but I am not familiar with the c-syntax. I somehow suspect that the error is related to Linux case sensitivity if db.c is trying to check if "unixODBC" is installed and then trying to match it with the "db_unixodbc.so" but I'm am not sure. Can someone please give further advice? Respectfully Dimitry Nagorny Trainee

2 5

SIP Notifications
by Safdar Khan 02 May '16

02 May '16

Hello, How i enable push notification in kamailio.How i proceed to configure the kamailio configuration file and which kamailio module should i look for? Thanks

3 4

2025

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 May 2016