sr-users April 2016

sr-users@lists.kamailio.org

76 participants
117 discussions

Missing accounting events in ACC table
by Muhammad Shahzad 23 May '17

23 May '17

Hi, About 3 weeks ago i upgraded one of my production server with latest stable kamailio version 4.2.1-fad00a. Now i am getting a lot of complaints about missing CDR events in ACC table. I observe following problems, 1. There are only BYE records in acc table, no record for INVITE or ACK. 2. In kamailio logs when ACK is received against 200 OK response for INVITE, i see following errors, -- ERROR: <core> [parser/parse_from.c:113]: parse_from_uri(): failed to parse >From uri ERROR: pv [pv_core.c:434]: pv_get_xto_attr(): cannot parse From URI NOTICE: <script>: [udp:<null>@1.0.0.127:5060]: Call from 'you(a)kamailio.org' to 'you(a)kamailio.org' has been hanged up by '<null>' at '1419364717.255484' -- Of course all these errors are bogus, I have checked all headers in ACK (not just FROM header), they all seem perfectly fine and valid. 3. Then the dialog times out, -- WARNING: dialog [dlg_handlers.c:1440]: dlg_ontimeout(): timeout for dlg with CallID '6D8BD23CAC65AE3C1DE1D0B531F87B8CFEAA9CB9' and tags '1D3ECD34F5731AB845BA3064AC95BB2D' '7f55e81e0630-100007f-13c4-6009-2440a4-5fa31570-2440a4' -- 4. Any further sequential requests complain about "unable to find dialog", e.g. -- NOTICE: <script>: Sequencial 'BYE' request received from caller ERROR: uac [replace.c:591]: restore_uri(): new URI [] shorter than old URI [ sip:00xxxxxxxxxx@sip.domain.com] WARNING: dialog [dlg_handlers.c:1174]: dlg_onroute(): unable to find dialog for BYE with route param '5ae1.d595' [7845:22877] -- 5. However the acc record for BYE is written to db and log file, -- NOTICE: acc [acc.c:318]: acc_log_request(): ACC: transaction answered: timestamp=1419364760;method=BYE;from_tag=7f55e81e0630-100007f-13c4-6009-2440a4-5fa31570-2440a4;to_tag=1D3ECD34F5731AB845BA3064AC95BB2D;call_id=6D8BD23CAC65AE3C1DE1D0B531F87B8CFEAA9CB9;code=200;reason=OK;src_user=00xxxxxxxxxx;src_domain= sip.domain.com ;src_ip=xx.xx.xx.xx;dst_ouser=+1xxxxxxxxxx;dst_user=1xxxxxxxxxx;dst_domain=yy.yy.yy.yy -- The same config was working fine with older version 4.2.0-97cab8. The kamailio config i am using is pretty much standard, -- #!define FLT_ACC 1 #!define FLT_ACCMISSED 2 #!define FLT_ACCFAILED 3 #!define FLT_DLG 4 ... modparam("acc", "early_media", 1) modparam("acc", "report_ack", 1) modparam("acc", "report_cancels", 1) modparam("acc", "detect_direction", 1) modparam("acc", "log_flag", FLT_ACC) modparam("acc", "log_missed_flag", FLT_ACCMISSED) modparam("acc", "failed_transaction_flag", FLT_ACCFAILED) # log to db modparam("acc", "db_flag", FLT_ACC) modparam("acc", "db_missed_flag", FLT_ACCMISSED) modparam("acc", "db_url", "DBURL") ... request_route { # per request initial checks route(REQINIT); # NAT detection route(NATDETECT); # handle requests within SIP dialogs route(WITHINDLG); # CANCEL processing if (is_method("CANCEL")) { if (t_check_trans()) { t_relay(); }; exit; }; #### only initial requests (no To tag) #### t_check_trans(); .... # account only INVITEs if (is_method("INVITE")) { setflag(FLT_DLG); # create dialog setflag(FLT_ACC); # do accounting setflag(FLT_ACCFAILED); # ... even if the transaction fails $avp(dlg_timeout) = 60; dlg_manage(); .... } -- Any ideas why its happening? Since it is 3 weeks old so may be problem has already been spotted and fixed by someone else. Otherwise let me know how can i provide more info to help fix this issue. Thank you.

3 11

How to make OutBound calls with kamailio
by sharad tyagi 23 May '17

23 May '17

Hi I am novice to kamailio , I have installed kamailio-4.2.0 and SIREMIS. I have add and registered two IP phones with kamailio these phone able to call each other. How can i make outbound call with that I am using a asterisk server as PSTN Gateway. i am not famalier with kamailio script. Regards Sharad Tyagi SparkTG info Pvt Ltd

4 3

Cannot hear voice with symmetric NAT and STUN
by Khoa Pham 08 Feb '17

08 Feb '17

Hi, I have Kamailio as SIP server and RTP server. Client is PJSIP. I read that STUN is for non-symmetric NAT, and RTP server is for symmetric NAT. Supposed A calls B. If A, B both use symmetric NAT and STUN, they cannot hear each other If A or B use non-symmetric NAT and NOT using STUN, they cannot hear each other. Why is that? I read http://tools.ietf.org/id/draft-takeda-symmetric-nat-traversal-00.txt for Prediction Failure, is that related to this problem ? -- Khoa Pham HCMC University of Science Faculty of Information Technology

8 18

Using the auth_ephemeral module
by Hemanshu Vadehra 17 Jan '17

17 Jan '17

I'm involved in setting up a Kamailio instance and was hoping to make use of the auth_ephemeral module for authentication. But the module documentation doesn't quite make clear how exactly the module is to be employed or the web service set up. Does anyone have a working example? Regards, Hemanshu Vadehra hemanshu.v(a)directi.com

5 8

Kamailio on Mac
by Carlos Ruiz Díaz 04 Aug '16

04 Aug '16

Hi all, I'm switching my development environment from Linux to Mac. Is there any tutorial on how to setup Kamailio on this OS? It may be an Unix flavor, but it's still quite different from Linux :). Thanks, -- Carlos http://caruizdiaz.com http://ngvoice.com +52 55 3048 3303

6 9

Sipcapture on SPARC
by Spencer Thomason 18 May '16

18 May '16

Hello, I’m attempting to deploy a homer sip capture server on SPARC and I’m seeing some strange date related errors: ERROR: db_mysql [km_dbase.c:128]: db_mysql_submit_query(): driver error on query: Incorrect datetime value: '2052-06-12 16:21:06' for column 'date' at row 1 (1292) Is there some sore of endianness issue? Thanks for any assistance! Regards, Spencer

2 3

[kamailio 5.0] upgrade VS rollback/backward compatibility
by Alex Lutay 18 May '16

18 May '16

Hi, We are heavily using Kamailio in our product Sipwise NGCP and currently testing possibility to provide rollback for the customers with the huge systems as the last resort functionality in case if upgrade went wrong. We hope never use it on practice but prefer to have such possibility. The main logic here is to change DB in 'backward compatible' way. So OLD code must work with NEW DB schema (but NOT a vice verse). We have some rules which helps us care about it, like "Do not drop columns, just discontinue them" and "All new fields should have defaults", etc. Also we have separated 'code', 'configs' and 'data' parts of our product and rollback 'code'/'configs' only, while 'data' (e.g. MySQL DB) stays in new state. Otherwise rollback will require a lot if time to revert all DB statements and sometimes it is just not possible. While every time we have to upgrade Kamailio we have a problems with rollback possibility. The point here that Kamailio checks DB table_version and doesn't start if the version mismatch found. Q: What about to add Kamailio possibility to work in backward compatible mode? Sample for upgrade Kamailio 4.3.x -> 4.4.x (the versions here as an example only!) https://www.kamailio.org/wiki/install/upgrade/4.3.x-to-4.4.0 We have 3 DB statements there which are adding new columns to 3 tables, like > -- table: active_watchers > ALTER TABLE active_watchers > ADD COLUMN flags INT(11) NOT NULL DEFAULT '0', > ADD COLUMN user_agent VARCHAR(255) NOT NULL; > DELETE FROM version WHERE TABLE_NAME='active_watchers'; > INSERT INTO version (`table_name`, `table_version`) VALUES ('active_watchers','12'); Problem here is missed default for column 'user_agent' which can be empty value as for me. So, lets assume we have it there. Then we can add new column to table 'version', like that: > mysql> select * from version where table_name='active_watchers'; > +-----------------+---------------+---------------------+ > | table_name | table_version | table_compatibility | > +-----------------+---------------+---------------------+ > | active_watchers | 12 | 11 | > +-----------------+---------------+---------------------+ > 1 row in set (0.00 sec) Currently: - module presence version 4.4.x starts check required version and refuse to load if table_version!=12 Proposed behaviour: - module presence version 4.4.x starts check required version and refuse to load if table_version!=12 and compatibility option is not set - if compatibility option is set, check value of table_compatibility and refuse to load if current version less then table_compatibility value >From the sample above I would say module presence in Kamailio 4.4.x is compatible with Kamailio 4.3.x if we define default value for the field 'user_agent'. Having that will allow us to rollback on previous NGCP release and _temporary_ work on Kamailio 4.3.x having new Kamailio DB 4.4.x P.S. This is just a question to check Kamailio community vision here and reality is more complex as described, so some additional checks/limitations will be in place. P.P.S Compatibility Kamailio option can/should be disabled by default. Field 'table_compatibility' can be outside table 'version', e.g. in separate table. Complete compatibility logic can be some separate Kamailio 'compatibility' module. Thank you! -- Alexander Lutay Head of Quality Assurance Sipwise GmbH, Campus 21/Europaring F15 AT-2345 Brunn am Gebirge Office: +43(0)13012036 Email: alutay(a)sipwise.com Website: https://www.sipwise.com Meet us @ ANGACOM: Hall 10.1 / booth N10 Exhibition and Congress for Broadband, Cable & Satellite: 07 – 09 June, 2016 in Cologne

4 3

Kamailio and Oracle database
by gmele 11 May '16

11 May '16

Hello, we are trying to connect our Kamailio SIP to an Oracle database. We tried both db_oracle and db_unixodbc modules to connect to the DB. With db_oracle, Kamailio core dumps when trying to access the active_watchers table (caused by the oracle CLOB?). Here is the kamailio logs: Apr 29 13:54:53 newvm1 /usr/sbin/kamailio[23665]: INFO: <core> [db_query.c:131]: db_do_query_internal(): DB-QUERY: select presentity_uri,callid,to_tag ,from_tag,event from active_watchers where updated=:1 AND event=:2 Apr 29 13:54:53 newvm1 /usr/sbin/kamailio[23665]: INFO: db_oracle [res.c:238]: get_columns(): COLUMN PRESENTITY_URI TYPE 4 SIZE 129 Apr 29 13:54:53 newvm1 /usr/sbin/kamailio[23665]: INFO: db_oracle [res.c:238]: get_columns(): COLUMN CALLID TYPE 4 SIZE 256 Apr 29 13:54:53 newvm1 /usr/sbin/kamailio[23665]: INFO: db_oracle [res.c:238]: get_columns(): COLUMN TO_TAG TYPE 4 SIZE 65 Apr 29 13:54:53 newvm1 /usr/sbin/kamailio[23665]: INFO: db_oracle [res.c:238]: get_columns(): COLUMN FROM_TAG TYPE 4 SIZE 65 Apr 29 13:54:53 newvm1 /usr/sbin/kamailio[23665]: INFO: db_oracle [res.c:238]: get_columns(): COLUMN EVENT TYPE 4 SIZE 65 Apr 29 13:54:53 newvm1 /usr/sbin/kamailio[23665]: INFO: db_oracle [res.c:378]: get_rows(): OCIStmtFetch2() returned 100 Apr 29 13:54:53 newvm1 /usr/sbin/kamailio[23667]: CRITICAL: <core> [pass_fd.c:275]: receive_fd(): EOF on 16 Apr 29 13:54:53 newvm1 /usr/sbin/kamailio[23667]: CRITICAL: <core> [pass_fd.c:275]: receive_fd(): EOF on 14 What is really strange is that this table is accessed several times before the crash, without any problem. The other point is that this table is absolutely empty... With db_unixodbc, all requests having dates check fail because because the date format is not understood by oracle. The date should be converted using the oracle to_date(date, format) funtion to work... Here are the Kamilio traces: Apr 29 14:10:38 newvm1 /usr/sbin/kamailio[17021]: ERROR: usrloc [dlist.c:183]: get_all_db_ucontacts(): query error Apr 29 14:10:38 newvm1 /usr/sbin/kamailio[17021]: ERROR: nathelper [nathelper.c:2089]: nh_timer(): failed to fetch contacts Apr 29 14:10:39 newvm1 /usr/sbin/kamailio[17021]: ERROR: db_unixodbc [dbase.c:133]: db_unixodbc_submit_query(): rv=-1. Query= select received,contact,socket,cflags,path,ruid from$ Apr 29 14:10:39 newvm1 /usr/sbin/kamailio[17021]: ERROR: db_unixodbc [connection.c:220]: db_unixodbc_extract_error(): unixodbc:SQLExecDirect=HY000:1:933:[Oracle][ODBC][Ora]ORA-00$ Apr 29 14:10:39 newvm1 /usr/sbin/kamailio[17021]: ERROR: <core> [db_query.c:132]: db_do_query_internal(): error while submitting query I tried the option modparam("db_unixodbc", "use_escape_common", 1), but without success. Has anyone been able to make Kamailio 4.4.0 work with Oracle 11g, either with db_oracle or with db_unixodbc module? Regards Giovanni -- View this message in context: http://sip-router.1086192.n5.nabble.com/Kamailio-and-Oracle-database-tp1479… Sent from the Users mailing list archive at Nabble.com.

3 28

sdp_remove_line_by_prefix
by Alberto Sagredo 09 May '16

09 May '16

Hi Im trying to remove my Asterisk s= line on SDP but when doing: sdp_remove_line_by_prefix("s=Asterisk"); Nothing happens. Loaded sdpops.so module as well. Is there any additional needed? BR

4 10

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

2026

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