sr-users March 2015

sr-users@lists.kamailio.org

88 participants
149 discussions

by Shane Harrison

Hi all ims'ers I have modified the ims_charging module to cope with the CCA return code of "CREDIT CONTROL NOT APPLICABLE". This means the call is not a chargeable call and the charging module now returns a unique return code for this. Currently there are two scenarios handled: 1) CCA grants the credit required for the call --> route the INVITE and then automatically new CCR requests are made for further credit as the call progresses 2) CCA doesn't grant the credit ---> send an error response back to INVITE originator - I assume this will clear all dialogs and no further credit requests are made. The question I have, is how do I cope with this unique return code so that I can continue to route the call but not make any more CCR requests to the credit control server? As I am not sure how the ims_charging module continues to generate CCR requests, it is difficult for me to understand how to essentially clear the whole CCR session without clearing the call. Kind regards Shane Shane Harrison Senior Software Engineer Imagination Technologies NZ Limited Level 2 1 Market Grove Lower Hutt, 5010 New Zealand PO Box 30-449 Lower Hutt, 5040 New Zealand Phone: +64 4 890-3681 ext 3361

9 years, 6 months

kamailio asterisk NOTIFY

by Slava Bendersky

Hello Everyone, Having issue with NOTIFY, is not forwarded to client properly. asterisk ---> private kamailio public ----> soft client http://fpaste.org/196257/99948714/ I see kamailio trying connect always with private IP to the client when NOTIFY is come is in. Is this something to do with rr_advertise_address ? Mar 10 13:44:23 canlvprx01 kamailio: 16(24971) ERROR: <core> [tcp_main.c:4338]: tcpconn_main_timeout(): connect 192.168.88.246:5064 failed (timeout) Mar 10 13:44:23 canlvprx01 kamailio: 16(24971) DEBUG: <core> [tcp_main.c:4362]: tcpconn_main_timeout(): tcp_main: timeout for 0x7fbbb64e2800 Mar 10 13:44:23 canlvprx01 kamailio: 16(24971) DEBUG: <core> [io_wait.h:610]: io_watch_del(): DBG: io_watch_del (0x9dbf00, 33, -1, 0x10) fd_no=24 called Mar 10 13:44:23 canlvprx01 kamailio: 16(24971) DEBUG: <core> [tcp_main.c:4320]: tcpconn_main_timeout(): tcp_main: entering timer for 0x7fbbb64eb6c0 (ticks=839577436, timeout=839634956 (3595 s), wr_timeout=839577436 (0 s)), write queue: 798 bytes Mar 10 13:44:23 canlvprx01 kamailio: 16(24971) ERROR: <core> [tcp_main.c:4338]: tcpconn_main_timeout(): connect 192.168.88.246:5066 failed (timeout) Mar 10 13:44:23 canlvprx01 kamailio: 16(24971) DEBUG: <core> [tcp_main.c:4362]: tcpconn_main_timeout(): tcp_main: timeout for 0x7fbbb64eb6c0 Mar 10 13:44:23 canlvprx01 kamailio: 16(24971) DEBUG: <core> [io_wait.h:610]: io_watch_del(): DBG: io_watch_del (0x9dbf00, 34, -1, 0x10) fd_no=23 called Mar 10 13:44:42 canlvprx01 kamailio: 5(24960) DEBUG: tm [t_reply.c:1294]: t_should_relay_response(): ->>>>>>>>> T_code=0, new_code=408 Mar 10 13:44:42 canlvprx01 kamailio: 5(24960) DEBUG: tm [t_reply.c:1812]: relay_reply(): DEBUG: relay_reply: branch=0, save=0, relay=0 icode=0 Mar 10 13:44:42 canlvprx01 kamailio: 5(24960) DEBUG: <core> [mem/shm_mem.c:111]: _shm_resize(): WARNING:vqm_resize: resize(0) called Mar 10 13:44:42 canlvprx01 kamailio: 5(24960) DEBUG: tm [t_reply.c:1294]: t_should_relay_response(): ->>>>>>>>> T_code=0, new_code=408 Mar 10 13:44:42 canlvprx01 kamailio: 5(24960) DEBUG: tm [t_reply.c:1812]: relay_reply(): DEBUG: relay_reply: branch=0, save=0, relay=0 icode=0 I have in configuration in WITHINDLG if (is_method("NOTIFY")) { record_route(); } and in NATDETECT if(is_method("INVITE|SUBSCRIBE|UPDATE|NOTIFY")) { set_contact_alias(); } Slava.

9 years, 6 months

Sipcapture module insert error

by Spencer Thomason

Hello, I’m not sure if this is the correct forum for this question but here goes… I’m facing an issue setting up a sipcapture server. I’m seeing several db errors in the logs: Mar 6 10:45:13 sipcapture /usr/local/sbin/kamailio[37872]: ERROR: db_mysql [km_dbase.c:123]: db_mysql_submit_query(): driver error on query: Data too long for column 'correlation_id' at row 1 I did a packet capture of the sql query and it appears that the value for the correlation_id is omitted. Interestingly its not all packets but maybe 60%. Do I have something misconfigured? Thanks, Spencer A sanitized version of the query is below: insert into sip_capture (date,micro_ts,method,reply_reason,ruri,ruri_user,from_user,from_tag,to_user,to_tag,pid_user,contact_user,auth_user,callid,callid_aleg,via_1,via_1_branch,cseq,reason,content_type,auth,user_agent,source_ip,source_port,destination_ip,destination_port,contact_ip,contact_port,originator_ip,originator_port,proto,family,rtp_stat,type,node,correlation_id,msg ) values ('2015-03-06 10:50:22',1425667824109829,'180','Ringing','','','+12052222222','gK007b315d','+12051111111','3Sr0m4vyjy2UK','','+12051111111','','2080378443_116641441(a)1.1.1.1','','SIP/2.0/UDP 1.1.1.1:5060;branch=z9hG4bK00B5617ed64f1ebf7d7','z9hG4bK00B5617ed64f1ebf7d7','1888238783 INVITE','','','','','3.3.3.3',5060,'1.1.1.1',5060,'2.2.2.2',6038,'',0,1,2,'',2,'node1:2001','SIP/2.0 180 Ringing\r\nVia: SIP/2.0/UDP 1.1.1.1:5060;branch=z9hG4bK00B5617ed64f1ebf7d7\r\nRecord-Route: <sip:3.3.3.3;lr;ftag=gK007b315d>\r\nFrom: <sip:+12052222222@1.1.1.1>;tag=gK007b315d\r\nTo: <sip:+12051111111@3.3.3.3>;tag=3Sr0m4vyjy2UK\r\nCall-ID: 2080378443_116641441(a)1.1.1.1\r\nCSeq: 1888238783 INVITE\r\nContact: <sip:+12051111111@2.2.2.2:6038;transport=udp>\r\nAccept: application/sdp\r\nAllow: INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, INFO, UPDATE\r\nSupported: path\r\nContent-Length: 0\r\n\r\n','SIP/2.0 180 Ringing\r\nVia: SIP/2.0/UDP 1.1.1.1:5060;branch=z9hG4bK00B5617ed64f1ebf7d7\r\nRecord-Route: <sip:3.3.3.3;lr;ftag=gK007b315d>\r\nFrom: <sip:+12052222222@1.1.1.1>;tag=gK007b315d\r\nTo: <sip:+12051111111@3.3.3.3>;tag=3Sr0m4vyjy2UK\r\nCall-ID: 2080378443_116641441(a)1.1.1.1\r\nCSeq: 1888238783 INVITE\r\nContact: <sip:+12051111111@2.2.2.2:6038;transport=udp>\r\nAccept: application/sdp\r\nAllow: INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, INFO, UPDATE\r\nSupported: path\r\nContent-Length: 0\r\n\r\n')

9 years, 6 months

building kamailio with MongoDB

by Tom Braarup Cuykens

I am trying to setup a Kamailio with MongoDB but the complilation fails: make include_modules="db_mongodb rtpproxy" cfg make all [...] In file included from mongodb_connection.c:24:0: mongodb_connection.h:26:20: fatal error: mongoc.h: No such file or directory compilation terminated. make[1]: *** [mongodb_connection.o] Error 1 make: *** [modules] Error 1 I have build the mongodb C driver from https://github.com/mongodb/mongo-c-driver/ Not sure if the issue is related to the Kamailio MongoDB module or the Mongo C driver. -- Med venlig hilsen Tom Braarup Cuykens plusTEL.dk

9 years, 6 months

kamailio 4.2.3 Segmentation fault when using db_cluster module

by Jan Hazenberg

Hello, I have a issue on kamailio 4.2.3 when using the db_cluster module. I have the following config: #!define DBURL "cluster://cls1" # ----- db_cluster params ----- modparam("db_cluster", "connection", "con1=>mysql://kamailio:kamailiorw@10.121.0.120/kamailio") modparam("db_cluster", "connection", "con2=>mysql://kamailio:kamailiorw@10.121.0.121/kamailio") modparam("db_cluster", "connection", "con3=>mysql://kamailio:kamailiorw@10.121.0.122/kamailio") modparam("db_cluster", "cluster", "cls1=>con1=9r8r;con2=9r8r;con3=9r8r") modparam("db_cluster", "inactive_interval", 180) modparam("db_cluster", "max_query_length", 5) # ----- sqlops params ----- modparam("sqlops","sqlcon","ca=>cluster://cls1") When i start kamailio it fails with: Mar 9 17:11:49 localhost kamailio[31063]: INFO: rr [../outbound/api.h:54]: ob_load_api(): Failed to import bind_ob Mar 9 17:11:49 localhost kamailio[31063]: INFO: rr [rr_mod.c:160]: mod_init(): outbound module not available Mar 9 17:11:49 localhost kamailio[31063]: INFO: usrloc [hslot.c:53]: ul_init_locks(): locks array size 1024 Mar 9 17:11:49 localhost kamailio[31063]: INFO: permissions [parse_config.c:251]: parse_config_file(): file not found: /usr/local/etc/kamailio/permissions.allow Mar 9 17:11:49 localhost kamailio[31063]: INFO: permissions [permissions.c:608]: mod_init(): default allow file (/usr/local/etc/kamailio/permissions.allow) not found => empty rule set Mar 9 17:11:49 localhost kamailio[31063]: INFO: permissions [parse_config.c:251]: parse_config_file(): file not found: /usr/local/etc/kamailio/permissions.deny Mar 9 17:11:49 localhost kamailio[31063]: INFO: permissions [permissions.c:617]: mod_init(): default deny file (/usr/local/etc/kamailio/permissions.deny) not found => empty rule set Mar 9 17:11:49 localhost kernel: kamailio[31063]: segfault at 80 ip 00007f7f4f9ffddc sp 00007fffde2f88a0 error 4 in db_cluster.so[7f7f4f9ec000+28000] Mar 9 17:11:50 localhost kamailio: ERROR: <core> [daemonize.c:315]: daemonize(): Main process exited before writing to pipe Could this be a bug or is this a configuration issue? I tested the dbnodes and they seem to respond fine to any query's i send. Thanks, Jan Hazenberg

9 years, 6 months

SIP 500 on WSS connection lookup failure

by Armen Babikyan

Hello, I am setting up this scenario using Kamailio 4.2.2: [UA] <-> [kamailio1] <-> [kamailio2] <-> [other stuff] UA connects to kamailio1 using SIP/WSS, kamailio1 proxies request along to kamailio2. Note that my intent here is to have kamailio2 provide the registrar functionality. The kamailio2 (or something behind it) can also initiate transactions to UA, like OPTIONS, for example. I'm having an issue though: when the websocket connection between kamailio1 and UA dies, transaction requests from kamailio2 show up to kamailio1, and I get errors in kamailio1's logs because the WSS connection is gone. I get messages as follows (debug=2): Mar 6 00:17:33 kamailio1 /usr/local/sbin/kamailio[5653]: WARNING: <core> [msg_translator.c:2778]: via_builder(): TCP/TLS connection (id: 0) for WebSocket could not be found Mar 6 00:17:33 kamailio1 /usr/local/sbin/kamailio[5653]: ERROR: <core> [msg_translator.c:1996]: build_req_buf_from_sip_req(): could not create Via header Mar 6 00:17:33 kamailio1 /usr/local/sbin/kamailio[5653]: ERROR: tm [t_fwd.c:527]: prepare_new_uac(): could not build request Mar 6 00:17:33 kamailio1 /usr/local/sbin/kamailio[5653]: ERROR: tm [t_fwd.c:1777]: t_forward_nonack(): ERROR: t_forward_nonack: failure to add branches At debug=4, I get the output here: http://pastebin.com/d3RumekG In a running tshark, I see kamailio1 responding to kamailio2 with a "SIP/2.0 500 No error (2/TM)". It appears to me that this is happening before t_relay() even returns. Is there a way to prevent the SIP 500 from being sent back to the client? I am calling t_on_branch_failure("kam2bf") and t_on_failure("kam2f"), with each of those handlers (event_route[tm:branch-failure:kam2bf] and failure_route[kam2f]) written to print a log message, but it appears that neither of those handlers are being called. I tried installing these handlers independently to no avail. I also tried registering a t_on_reply() handler, thinking it was an internally-generated SIP response that might make it through my handler on its way out to kam2, but that is also not getting invoked. I want to return a 404 or something similar instead of having a 500 auto-returned for me. Related to this, is there a way to query kamailio's in-memory client connectivity data structure for the connectivity status of a client? Or is this something best done by keeping track of every client myself using (e.g.) localcache? Any pointers are appreciated. Thanks! Armen

9 years, 6 months

help with a new install

by David Dunlap

Hello, I am seeking help with a new test server. I have SIP messages coming from a working FreeSwitch and getting posted into the sip_capture table. Homer web service is responding allowing me to manage log on accounts and other database settings however I do not see any packets in the web gui. I used the install script from the web page and did not notice any errors as it worked. I sure would appreciate some help. The IRC channel was empty. Thanks David Dunlap [cid:D854C04A-3D89-4B99-AD05-D242790BFC94] 3105 N. Main St. East Peoria, IL 61611 Direct: 309-427-7226 Main: 309-427-7000 Fax: 309-427-7326 Email: ddunlap(a)heart.net www.heart.net

9 years, 6 months

Transfer call between devices

by Phil Daws

Hello: wish to ask how one may configure Kamailio so that if a user has a number of devices registered eg. deskphone, soft client on tablet, and soft client on cellphone when a call is originated or received how it can be passed between devices. Is it as simple as configuring a blind transfer ? Thanks for any help. Phil

9 years, 6 months

4.2.3 textops: flag "f" doesn't work in subst_hf(hf, subexp, flags)

by Julia Boudniatsky

Hello, I received INVITE with 3 Diversion headers. I try to make substitutions in the body of a first Diversion header field by using flag "f", command *subst_hf("Diversion", /sip:(.*)@/sip:$var(dU)@/", "f") ;* substitutes *all headers *Diversion instead of only first header, command *subst_hf("Diversion", /sip:(.*)@/sip:$var(dU)@/", "*l*") ;* substitutes only *last* Diversion header. Thanks for help, Julia.

9 years, 6 months

core parsing of SIP message failed errors

by Jeff Cohn

Hello, I finally got everything working but see to consistently receive the following 3 errors (see below) over and over when a call is being collected? Versions: Homer 3.6 kamailio 4.3.0-dev4 Captagent 4.2.0 Any assistance would be appreciated. Thanks, Jeff ------------------------- Errors: Mar 8 22:04:47 ce-homer2 /usr/local/kamailio/sbin/kamailio[9921]: ERROR: [parser/parse_fline.c:257]: parse_first_line(): parse_first_line: bad message (offset: 0) Mar 8 22:04:47 ce-homer2 /usr/local/kamailio/sbin/kamailio[9921]: ERROR: [parser/msg_parser.c:688]: parse_msg(): ERROR: parse_msg: message=> Mar 8 22:04:47 ce-homer2 /usr/local/kamailio/sbin/kamailio[9921]: ERROR: [receive.c:129]: receive_msg(): core parsing of SIP message failed (127.0.0.1:33264/1) Mar 8 22:04:47 ce-homer2 /usr/local/kamailio/sbin/kamailio[9922]: ERROR: [parser/parse_fline.c:257]: parse_first_line(): parse_first_line: bad message (offset: 0) Mar 8 22:04:47 ce-homer2 /usr/local/kamailio/sbin/kamailio[9922]: ERROR: [parser/msg_parser.c:688]: parse_msg(): ERROR: parse_msg: message= Mar 8 22:04:47 ce-homer2 /usr/local/kamailio/sbin/kamailio[9922]: ERROR: [receive.c:129]: receive_msg(): core parsing of SIP message failed (127.0.0.1:33264/1)

9 years, 6 months

← Newer
1
...
9
10
11
12
13
14
15
Older →

Jump to page:

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 2015