sr-users September 2013

sr-users@lists.kamailio.org

89 participants
128 discussions

Kamailio problem route
by Camilo Bozo 05 Sep '13

05 Sep '13

Hello! i am new in It, i speak spanish y very bad english, my problem is: i want route to announcement when is busy or request timeout(486|408): ... ... if(t_check_status("486|408")){ route(TEST); exit; } route[TEST] { setflag(1); append_hf("P-App-Name: announcement\r\n"); rewritehostport("sip.inf.uct.cl:5080"); route("RELAY"); exit; } route[RELAY] { if(is_method("ACK")) { exec_msg("/bin/echo \" $$SIP_HF_FROM $$SIP_HF_TO $$SIP_RURI \" >> /home/kaminfo/llamadas.log"); ... ... this just to prove that routing works. call with linphone and gives an error that says "I'm terribly sorry, server error occurred (6/SL). Are you missing something in code? Please help, is my final Thank you. -- Saludos ATTE: * * imagen mirje /*Camilo Bozo Mirje Soluciones informáticas Atención de Lunes a Viernes 9:30 a 18:30 hrs Fono: 81338638 Email: camilo.bozo(a)mirje.net */

2 1

rfc: accounting records time details
by Daniel-Constantin Mierla 05 Sep '13

05 Sep '13

Hello, there were old and recent discussions about the representation of time in accounting records. At this moment the acc module stores the unix timestamp as datetime value. In some countries is required to store more accuracy, beyond the seconds. Also, the datetime gives some troubles with converting back to unix timestamp, specifically with time zones and daylight saving times. I want to open a discussion that is visible for all users and devs, being something affecting probably everyone, input from anyone that is interested being relevant to select the right approach. Here are some suggestions presented so far. 1) store seconds.miliseconds as double - there is a patch (which probably needs some tunings itself) on tracker. The precision is shifted from seconds to milliseconds. Internally computed from microseconds from timeval structure. The other modules might need updates (iirc dbtext has only 2 decimals precisions for double, while miliseconds will require at least three -- could be the case for flatstore or other modules). Advantage is the computing of duration directly by subtraction of two values. 2) store seconds and microseconds as two separate values. Should be no issues with existing modules. Even more accuracy than above, no issues with other modules, but will require to use two columns (thus four values to compute the duration) Any other suggestions? Personally, at this moment, I will go with 2), but that might not meet everyone's needs. So a solution can be to make it configurable, as a bitmask of what time representation to store. Say, there will be a new parameter timestamp_mode for acc module: - bit one set - store seconds timestamp as for now (default) - bit two set - store seconds and microseconds in separate integer columns - bit three set - store seconds.miliseconds as double value in one column I could add the parameter and tune acc for bit one and two. For bit three a deeper review is needed for other modules, probably the developer that submitted to the tracker can do it. More suggestions? Pro or cons opinions? Cheers, Daniel -- Daniel-Constantin Mierla - http://www.asipto.com http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda Kamailio Advanced Training, San Francisco, USA - June 24016, 2013 * http://asipto.com/u/katu *

4 9

How to stop NOTIFY from being sent to stable location entries on unreliable network?
by Yufei Tao 05 Sep '13

05 Sep '13

Hi I'm using presence on Kamailio 4.0.3. I have in the cfg file: modparam("presence", "timeout_rm_subs", 0) to cope with unreliable networks. I have tried setting it to 1, but I saw sometimes server and client got out of sync, i.e. server removed active_watcher entries when NOTIFYs time out, while clients still thought the SUBSCRIBE dialogs are alive. Now I have a problem when client re-registers with different local IP/port (e.g. changing between wifi and ethernet, or simply crashed and rebooted), and sends new REGISTER and SUBSCRIBEs using the new local IP/port. In this case Kamailio still sends NOTIFYs to the old registered IP:port (as well as to the new one). NOTIFYs to old IP:port last until expiration it seems. Even though the stale location has been removed from the location table. I have a DB trigger to "SET expires=UNIX_TIMESTAMP()" to the corresponding active_watchers entries as well, when contact is removed from location table. So the DB tables have been updated to contain only entries with client's new IP:port, but it seems that the SUBSCRIBE dialogs are kept in the memory until expiration, even though they have been expired in the active_watchers table. My question is: is there any ways that I can stop all the NOTIFY messages from being sent to the stale locations, i.e. remove these SUBSCRIBE dialogs from memory? Thank you! Yufei -- Yufei Tao Red Embedded This E-mail and any attachments hereto are strictly confidential and intended solely for the addressee. If you are not the intended addressee please notify the sender by return and delete the message. You must not disclose, forward or copy this E-mail or attachments to any third party without the prior consent of the sender. Red Embedded Design, Company Number 06688253 Registered in England: The Waterfront, Salts Mill Rd, Saltaire, BD17 7EZ

1 0

testing - dialog-based cdrs to database
by Daniel-Constantin Mierla 05 Sep '13

05 Sep '13

Hello, being requested several times and as I did get to do some acc work, I added the code for storing dialog-based cdrs to database. But I had no time to setup a testbed for it, hopefully those interested in the feature will help testing a bit. It follows closely the same logic as writing cdrs to syslog. You have to create table acc_cdrs (see utils/kamctl/mysql/acc-create.sql), then add extra columns as you need. The attribute name in cdr_extra has to match the column name (the type for extra columns have to be string/varchar). In kamailio.cfg you have to set the cdrs_table parameter to acc_cdrs. One odd by now is that duration column is also string, because is how existing code (for syslog writing) stored in internally -- plan to change it in the near future, for now sql gives the tools for converting. More details can be found in acc module readme: - http://kamailio.org/docs/modules/devel/modules/acc.html Let me know the results, to tune it properly. Cheers, Daniel -- Daniel-Constantin Mierla - http://www.asipto.com http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda Kamailio Advanced Trainings - Berlin, Oct 21-24; Miami, Nov 11-13, 2013 - more details about Kamailio trainings at http://www.asipto.com -

2 1

PUBLISH/SUBSCRIBE in pidf format
by Rupayan Dutta 05 Sep '13

05 Sep '13

Can anybody suggest me whether kamailio 4.0.3 supports pidf format for handling presence related stuff instead of XCAP server.If yes what are the corrosponding changes in the kamaolio cfg file? If not, then how can I test my kamailio presence with XCAP functionality with a browser based client like SIPML5.Actually I want the XCAP related stuff instead of pidf which is currently available in Dubango SIPML5

2 2

kamailio's load balancing with DNS SRV
by hspproduct＠21cn.com 05 Sep '13

05 Sep '13

1 0

Auth credentials on ACK, 13.2.2.4
by David K 05 Sep '13

05 Sep '13

Hello, I am having difficulties with one of my SIP Trunk providers who insists that the dropped calls are my fault. Long story short, I send the final ACK for the INVITE 200 OK messages to the provider's SBC and 15% of the time the provider's SBC just drops the packet without any justification. I read through RFC 3261 and as near as I can tell, my packets conform to RFC3261. The only thing that seems to not conform is in " 13.2.2.4 2xx Responses" paragraph 4, sentence 4. " The ACK MUST contain the same credentials as the INVITE." I am using the UAC module to do authentification. How do I get UAC to add the same credentials to the ACK as it did to the INVITE ? I am using Kamailio as a load balancer ( module dispatcher ). Thanks in advance. David Here is my awesome failure route : failure_route[FAIL_ONE] { if ( t_check_status("401|407") ) { if ( isflagset(11) ) { t_reply("503", "Authentication failed"); break; } if (uac_auth()) { setflag(11); t_on_failure("FAIL_AUTH"); append_branch(); t_relay(); } } if (t_is_canceled()) { exit; } }

1 0

Re: [SR-Users] Issue with xpath in kamailio 4.0.2
by Ram Anji 04 Sep '13

04 Sep '13

I found the following statement in log which causes to fail. xcap_server [xcap_misc.c:475]: xcaps_xpath_set(): unable to evaluate xpath expression [/presence/pdm:person?xmlns(pdm=urn:ietf:params:xml:ns:pidf:data-model)] Here are the logs which are requested. Aug 30 21:31:11 kamailio kamailio[9460]: ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=615 a=5 n=route Aug 30 21:31:11 kamailio kamailio[9520]: DEBUG: <core> [db_res.c:136]: db_free_result(): freeing result set at 0xb71c3d28 Aug 30 21:31:11 kamailio kamailio[9460]: ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=957 a=2 n=return Aug 30 21:31:11 kamailio kamailio[9520]: ERROR: xcap_server [xcap_misc.c:475]: xcaps_xpath_set(): unable to evaluate xpath expression [/presence/pdm:person?xmlns(pdm=urn:ietf:params:xml:ns:pidf:data-model)] Aug 30 21:31:11 kamailio kamailio[9460]: ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=627 a=16 n=if Aug 30 21:31:11 kamailio kamailio[9520]: ERROR: xcap_server [xcap_server.c:619]: w_xcaps_put(): could not update xcap document Aug 30 21:31:11 kamailio kamailio[9460]: ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=618 a=25 n=is_method Aug 30 21:31:11 kamailio kamailio[9520]: DEBUG: sl [sl.c:289]: send_reply(): reply in stateless mode (sl) Aug 30 21:31:11 kamailio kamailio[9460]: ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=627 a=5 n=route Aug 30 21:31:11 kamailio kamailio[9520]: DEBUG: <core> [parser/msg_parser.c:339]: parse_headers(): parse_headers: flags=8 Aug 30 21:31:11 kamailio kamailio[9460]: ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=771 a=16 n=if Aug 30 21:31:11 kamailio kamailio[9520]: DEBUG: <core> [parser/msg_parser.c:339]: parse_headers(): parse_headers: flags=ffffffffffffffff Aug 30 21:31:11 kamailio kamailio[9460]: ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=731 a=24 n=has_totag Aug 30 21:31:11 kamailio kamailio[9520]: DEBUG: <core> [msg_translator.c:206]: check_via_address(): check_via_address(192.168.41.60, 192.168.41.60, 0) Aug 30 21:31:11 kamailio kamailio[9460]: DEBUG: siputils [checks.c:103]: has_totag(): no totag Aug 30 21:31:11 kamailio kamailio[9520]: DEBUG: <core> [tcp_main.c:1497]: _tcpconn_find(): tcpconn_find: 33 port 58665 Aug 30 21:31:11 kamailio kamailio[9460]: ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=631 a=24 n=t_check_trans Aug 30 21:31:11 kamailio kamailio[9520]: DEBUG: <core> [ip_addr.c:247]: print_ip(): tcpconn_find: ip 192.168.41.60 Aug 30 21:31:11 kamailio kamailio[9460]: DEBUG: tm [t_lookup.c:1095]: t_check_msg(): DEBUG: t_check_msg: msg id=165 global id=163 T start=(nil) Aug 30 21:31:11 kamailio kamailio[9520]: DEBUG: <core> [tcp_main.c:1504]: _tcpconn_find(): c=0xb49ba648, c->id=33, port=58665 Aug 30 21:31:11 kamailio kamailio[9460]: DEBUG: <core> [parser/msg_parser.c:339]: parse_headers(): parse_headers: flags=ffffffffffffffff Aug 30 21:31:11 kamailio kamailio[9520]: DEBUG: <core> [ip_addr.c:247]: print_ip(): ip=192.168.41.60 Aug 30 21:31:11 kamailio kamailio[9460]: DEBUG: <core> [parser/msg_parser.c:339]: parse_headers(): parse_headers: flags=78 Aug 30 21:31:11 kamailio kamailio[9520]: DEBUG: <core> [tcp_main.c:2330]: tcpconn_send_put(): tcp_send: send from reader (9520 (27)), reusing fd Aug 30 21:31:11 kamailio kamailio[9460]: DEBUG: tm [t_lookup.c:534]: t_lookup_request(): t_lookup_request: start searching: hash=14466, isACK=0 Aug 30 21:31:11 kamailio kamailio[9520]: DEBUG: <core> [tcp_main.c:2566]: tcpconn_do_send(): tcp_send: sending... Aug 30 21:31:11 kamailio kamailio[9460]: DEBUG: tm [t_lookup.c:492]: matching_3261(): DEBUG: RFC3261 transaction matching failed Aug 30 21:31:11 kamailio kamailio[9520]: DEBUG: <core> [tcp_main.c:2600]: tcpconn_do_send(): tcp_send: after real write: c= 0xb49ba648 n=125 fd=14 Aug 30 21:31:11 kamailio kamailio[9460]: DEBUG: tm [t_lookup.c:716]: t_lookup_request(): DEBUG: t_lookup_request: no transaction found Aug 30 21:31:11 kamailio kamailio[9520]: DEBUG: <core> [tcp_main.c:2601]: tcpconn_do_send(): tcp_send: buf=#012HTTP/1.1 500 Server error#015#012Via: SIP/2.0/TCP 192.168.41.60:58665#015#012Server: kamailio (4.0.2 (i386/linux))#015#012Content-Length: 0#015#012#015#012 Aug 30 21:31:11 kamailio kamailio[9460]: DEBUG: tm [t_lookup.c:1164]: t_check_msg(): DEBUG: t_check_msg: msg id=165 global id=165 T end=(nil) Aug 30 21:31:11 kamailio kamailio[9525]: DEBUG: <core> [tcp_main.c:3634]: handle_ser_child(): handle_ser_child: read response= b49ba648, -1, fd -1 from 27 (9520) Aug 30 21:31:11 kamailio kamailio[9520]: ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=1231 a=16 n=if Aug 30 21:31:11 kamailio kamailio[9460]: ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=634 a=5 n=route Aug 30 21:31:11 kamailio kamailio[9460]: ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=921 a=16 n=if Aug 30 21:31:11 kamailio kamailio[9460]: ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=905 a=25 n=is_method Aug 30 21:31:11 kamailio kamailio[9460]: ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=934 a=16 n=if Aug 30 21:31:11 kamailio kamailio[9460]: ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=921 a=25 n=is_method Aug 30 21:31:11 kamailio kamailio[9460]: DEBUG: <core> [parser/parse_uri.c:1241]: parse_uri(): parsed uri:#012 type=1 user=<test>(6)#012 passwd=<>(0)#012 host=<kamailio.com>(22)#012 port=<>(0): 0#012 params=<>(0)#012 headers=<>(0) Aug 30 21:31:11 kamailio kamailio[9460]: DEBUG: <core> [parser/parse_uri.c:1242]: parse_uri(): uri flags : Aug 30 21:31:11 kamailio kamailio[9460]: DEBUG: <core> [parser/parse_uri.c:1245]: parse_uri(): value=0 Aug 30 21:31:11 kamailio kamailio[9460]: DEBUG: <core> [parser/parse_uri.c:1248]: parse_uri(): uri params:#012 transport=<>, val=<>, proto=0 Aug 30 21:31:11 kamailio kamailio[9460]: DEBUG: <core> [parser/parse_uri.c:1251]: parse_uri(): user-param=<>, val=<> Aug 30 21:31:11 kamailio kamailio[9460]: DEBUG: <core> [parser/parse_uri.c:1254]: parse_uri(): method=<>, val=<> Aug 30 21:31:11 kamailio kamailio[9460]: DEBUG: <core> [parser/parse_uri.c:1257]: parse_uri(): ttl=<>, val=<> Aug 30 21:31:11 kamailio kamailio[9460]: DEBUG: <core> [parser/parse_uri.c:1260]: parse_uri(): maddr=<>, val=<> Aug 30 21:31:11 kamailio kamailio[9460]: DEBUG: <core> [parser/parse_uri.c:1261]: parse_uri(): lr=<> Aug 30 21:31:11 kamailio kamailio[9460]: DEBUG: <core> [parser/parse_uri.c:1262]: parse_uri(): r2=<> Aug 30 21:31:11 kamailio kamailio[9460]: DEBUG: <core> [socket_info.c:589]: grep_sock_info(): grep_sock_info - checking if host==us: 22==25 && [ kamailio.com] == [2607:F0D0:2001:0:0:0:0:12] Aug 30 21:31:11 kamailio kamailio[9460]: DEBUG: <core> [socket_info.c:593]: grep_sock_info(): grep_sock_info - checking if port 5060 (advertise 0) matches port 5060 Aug 30 21:31:11 kamailio kamailio[9460]: DEBUG: <core> [socket_info.c:589]: grep_sock_info(): grep_sock_info - checking if host==us: 22==13 && [ kamailio.com] == [192.168.41.10] Regards, Anzi

2 1

sip distributed architecture with kamailio
by Marek Červenka 04 Sep '13

04 Sep '13

hello, i'm searching documentation/publications/blogs howto make distributed architecture with kamailio - spread over several datacenters - highly available - N+1 p.s. i know google, but i'm sure in your bookmarks are hidden more "valuable" links -- --------------------------------------- Marek Cervenka =======================================

1 0

Call Baring
by arun Jayaprakash 04 Sep '13

04 Sep '13

Hello, with outgoing white list/black list I am able to put a prefix in the user preference table to block certain out going calls. In the same way is it possible to block incoming calls depending on certain prefixes ( like 1-800)? Regards, A

2 2

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 September 2013