sr-users July 2011

sr-users@lists.kamailio.org

75 participants
119 discussions

Cancel issue
by Carl Wagner 09 Aug '11

09 Aug '11

Hi, I am having an issue getting Kamailio to properly cancel a call. I initiate the call with an INVITE from Asterisk and then hang up. According to rfc3665 the call flow should be: 3.8. Unsuccessful No Answer Alice Proxy 1 Proxy 2 Bob | | | | | INVITE F1 | | | |--------------->| INVITE F2 | | | 100 F3 |--------------->| INVITE F4 | |<---------------| 100 F5 |--------------->| | |<---------------| | | | | 180 F6 | | | 180 F7 |<---------------| | 180 F8 |<---------------| | |<---------------| | | | CANCEL F9 | | | |--------------->| | | | 200 F10 | | | |<---------------| CANCEL F11 | | | |--------------->| | | | 200 F12 | | | |<---------------| | | | | CANCEL F13 | | | |--------------->| | | | 200 F14 | | | |<---------------| | | | 487 F15 | | | |<---------------| | | | ACK F16 | | | 487 F17 |--------------->| | |<---------------| | | | ACK F18 | | | 487 F19 |--------------->| | |<---------------| | | | ACK F20 | | | |--------------->| | | In my case I only have one proxy - the Kamailio box, and the call is coming from Asterisk instead of Alice. The is the call flow that I am seeing: Asterisk Kamailio SIP_phone | | | | INVITE | | |--------------->| INVITE | | 100 |--------------->| |<---------------| 100 | | |<---------------| | | | | | 180 | | 180 |<---------------| |<---------------| | | CANCEL | | |--------------->| | | | CANCEL | | |--------------->| | 200 Canceling | | |<---------------| | | | 200 | | |<---------------| | | | | | | | | 487 | | |<---------------| | | ACK | | 487 |--------------->| |<---------------| | | ACK | | |--------------->| | | CANCEL | | |--------------->| | | 200 Canceling | | |<---------------| | | CANCEL | | |--------------->| | | 200 Canceling | | |<---------------| | It looks like the problem is that that "200 Canceling" has a To: tag and it shouldn't. ====================================== # cancel from Asterisk: U 2011/05/24 15:18:56.123714 3.3.3.3:5060 -> 2.2.2.2:5060 CANCEL sip:SIP_13034445555@2.2.2.2 SIP/2.0. Via: SIP/2.0/UDP 3.3.3.3:5060;branch=z9hG4bK51c9602a;rport. From: "+13032223333" <sip:+13032223333@3.3.3.3>;tag=as4c415d87. To: <sip:SIP_13034445555@2.2.2.2>. Call-ID: 605b8de40a05924177085d71154bda77(a)3.3.3.3. CSeq: 102 CANCEL. User-Agent: VerbalWorld. Max-Forwards: 70. Content-Length: 0. # 200 canceling from Kamailio to asterisk: U 2011/05/24 15:18:56.127349 2.2.2.2:5060 -> 3.3.3.3:5060 SIP/2.0 200 canceling. Via: SIP/2.0/UDP 3.3.3.3:5060;branch=z9hG4bK51c9602a;rport=5060. From: "+13032223333" <sip:+13032223333@3.3.3.3>;tag=as4c415d87. To: <sip:SIP_13034445555@2.2.2.2>;tag=4ed8ab9f3ed29a77613bb14b3431ff43-2f34. Call-ID: 605b8de40a05924177085d71154bda77(a)3.3.3.3. CSeq: 102 CANCEL. Server: kamailio (3.1.3 (i386/linux)). Content-Length: 0. ====================================== Why is kamialio adding a To: tag? Portion of kamailio.cfg ===================== ... route { ... route(WITHINDLG); ### only initial requests (no To: tag) from here on if (is_method("CANCEL")) { if (t_check_trans()) { xlog("L_INFO", "MAIN: Recieved Cancel, t_check_trans is true\n"); ... t_relay(); exit; } ... Thanks! Carl

3 9

AVPs missing in onreply_route
by Sebastian Damm 04 Aug '11

04 Aug '11

Hi, I'm still fighting problems in our Kamailio 1.5 to 3.1 migration. Right now I'm stuck with a strange behavior of AVPs in my dialplan. I set a lot of AVPs for accounting in the route directive, and I just inserted an avp_print() statement right before t_relay() is called, all values are set. Then I call avp_print() as the first statement of onreply_route(), and it doesn't print out anything. I call it again at the end of onreply_route, and the only AVP printed out is the one I set directly there. In 1.5 there was an option in the tm module to control AVP behavior in replies, but that doesn't exist anymore, I even found a mailing list post from Daniel where he explained that all AVPs I set in route are also available in onreply_route. Am I doing something wrong? Is there still a secret option that I accidentally turned on? What else could make kamailio forget all AVPs after t_relay? I tried both version 3.1.3 and 3.1.4. Any help appreciated. Best regards, Sebastian

3 9

Carrierroute Compilation error Kamailio 3.1.4
by Omar 01 Aug '11

01 Aug '11

I am Using Solaris 10 and GCC 4.2, i do have libconfuse everything goes fine until this error comes up. carrierroute.c:54: error: 'MODULE_INTERFACE_VER' undeclared here (not in a function) carrierroute.c:87: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'cmds' carrierroute.c:132: error: variable 'exports' has initializer but incomplete type carrierroute.c:133: warning: excess elements in struct initializer carrierroute.c:133: warning: (near initialization for 'exports') carrierroute.c:134: warning: excess elements in struct initializer carrierroute.c:134: warning: (near initialization for 'exports') carrierroute.c:135: error: 'cmds' undeclared here (not in a function) carrierroute.c:135: warning: excess elements in struct initializer carrierroute.c:135: warning: (near initialization for 'exports') carrierroute.c:136: warning: excess elements in struct initializer carrierroute.c:136: warning: (near initialization for 'exports') carrierroute.c:137: warning: excess elements in struct initializer carrierroute.c:137: warning: (near initialization for 'exports') carrierroute.c:138: warning: excess elements in struct initializer carrierroute.c:138: warning: (near initialization for 'exports') carrierroute.c:139: warning: excess elements in struct initializer carrierroute.c:139: warning: (near initialization for 'exports') carrierroute.c:140: warning: excess elements in struct initializer carrierroute.c:140: warning: (near initialization for 'exports') carrierroute.c:141: warning: excess elements in struct initializer carrierroute.c:141: warning: (near initialization for 'exports') carrierroute.c:142: warning: excess elements in struct initializer carrierroute.c:142: warning: (near initialization for 'exports') carrierroute.c:143: warning: excess elements in struct initializer carrierroute.c:143: warning: (near initialization for 'exports') carrierroute.c:145: warning: excess elements in struct initializer carrierroute.c:145: warning: (near initialization for 'exports') carrierroute.c: In function 'mod_init': carrierroute.c:161: error: invalid use of undefined type 'struct module_exports' make[1]: *** [carrierroute.o] Error 1 make: *** [modules] Error 1

3 8

Detect phone and fax
by Linux Guy 31 Jul '11

31 Jul '11

Hi, Is there any way to separate detect phone and fax calls in kamailio ? I understand that kamailio is a signaling proxy only but is there any way we can detect if a call is a fax or phone ? Thanks Linux Guy..

2 1

what is tcp_accept_no_cl core param?
by Juha Heinanen 31 Jul '11

31 Jul '11

xcap_server module requires tcp_accept_no_cl=yes i didn't find that param defined in core cookbook. what does it do? -- juha

2 1

Set CLI.
by Henrik Aagaard Sørensen 29 Jul '11

29 Jul '11

Is it possible to set CLI via the usr_preferences table in Kamailio? Or any other way? So that certain subscribers get there from-number overwritten with a specific one.

3 2

[Urgent] Double REGISTER and MESSAGE issue in Kamailio3.1
by Coca 29 Jul '11

29 Jul '11

Dear List, I have Kamailio 3.1 installed in Amazon EC 2 server. Everything is working fine except that every REGISTER / MESSAGE was looped for twice or 3 times. And I am sure this is not caused by UA. I have attached the ngrep log in this message. And also, my main modification to the kamailio.cfg is like below: Your help will be great great appreciated. Thank you!! Coca ---------------------------------- #!define WITH_MYSQL #!define WITH_NAT alias="mydomain.org" alias="xx.xx.xx.xx" advertised_address="xx.xx.xx.xx" ... ... route { # per request initial checks route(REQINIT); # NAT detection route(NAT); # handle requests within SIP dialogs route(WITHINDLG); ### only initial requests (no To tag) # CANCEL processing if (is_method("CANCEL")) { if (t_check_trans()) t_relay(); exit; } t_check_trans(); # authentication route(AUTH); # record routing for dialog forming requests (in case they are routed) # - remove preloaded route headers remove_hf("Route"); if (is_method("INVITE|SUBSCRIBE")) { #record_route(); /* for NAT support */ record_route_preset("xx.xx.xx.xx"); } # account only INVITEs if (is_method("INVITE")) { setflag(FLT_ACC); # do accounting } # dispatch requests to foreign domains route(SIPOUT); ### requests for my local domains # handle presence related requests route(PRESENCE); # handle registrations route(REGISTRAR); if ($rU==$null) { # request with no Username in RURI sl_send_reply("484","Address Incomplete"); exit; } # dispatch destinations to PSTN route(PSTN); # user location service route(LOCATION); route(RELAY); } # Handle SIP registrations route[REGISTRAR] { if (is_method("REGISTER")) { if(isflagset(FLT_NATS)) { setbflag(FLB_NATB); # uncomment next line to do SIP NAT pinging setbflag(FLB_NATSIPPING); } if (!save("location")) sl_reply_error(); exit; } }

1 0

Problem using textops API
by Timo Klecker 29 Jul '11

29 Jul '11

Hi, I'm trying to extend a Kamailio Module and need to add and remove headers in a SIP Message. To do this I want to use the textops module and I am importing the api and trying to bind the textops module. #include "../textops/api.h" [..] struct textops_binds tob; [..] /* register callbacks to TEXTOPS */ if (load_textops_api(&tob)!=0) { LM_ERR("can't load textops api. Is module textops loaded?\n"); return -1; } Later I use tob.append_hf to add a header field. Everything compiles fine but on Kamailio startup there is a Error Message: [..] 0(21782) DEBUG: <core> [route_struct.c:166]: ACTION_#25 #0/2: 9(9)/ (nil) 0(21782) DEBUG: <core> [route_struct.c:166]: ACTION_#25 #1/2: 3(3)/ (nil) 0(21782) DEBUG: <core> [sr_module.c:625]: find_export_record: found <is_method> in module textops [/usr/lib/kamailio/modules_k/textops.so] 0(21782) DEBUG: <core> [route_struct.c:166]: ACTION_#25 #0/2: 9(9)/ (nil) 0(21782) DEBUG: <core> [route_struct.c:166]: ACTION_#25 #1/2: 3(3)/ (nil) 0(21782) DEBUG: <core> [sr_module.c:625]: find_export_record: found <is_method> in module textops [/usr/lib/kamailio/modules_k/textops.so] 0(21782) DEBUG: <core> [route_struct.c:166]: ACTION_#25 #0/2: 9(9)/ (nil) 0(21782) DEBUG: <core> [route_struct.c:166]: ACTION_#25 #1/2: 3(3)/ (nil) [..] 0(21784) DEBUG: <core> [sr_module.c:625]: find_export_record: found <t_release> in module tm [/usr/lib/kamailio/modules/tm.so] 0(21784) DEBUG: <core> [sr_module.c:631]: find_export_record: <load_textops> not found 0(21784) ERROR: siptrace [../../modules_k/textops/api.h:63]: Failed to import load_textops 0(21784) ERROR: siptrace [siptrace.c:314]: can't load textops api. Is module textops loaded? 0(21784) ERROR: <core> [sr_module.c:875]: init_mod(): Error while initializing module siptrace (/usr/lib/kamailio/modules_k/siptrace.so) ERROR: error while initializing modules 0(21784) DEBUG: tm [t_funcs.c:122]: DEBUG: tm_shutdown : start 0(21784) DEBUG: tm [t_funcs.c:125]: DEBUG: tm_shutdown : emptying hash table [..] I am running Kamailio 3.1.4. Is this a bug in Kamailio or am I doing anything wrong in my approach to use textops? Kind regards, Timo Klecker

2 3

problem with siptrace outgoing SIP message logging
by Peter Kaszas 29 Jul '11

29 Jul '11

Dear List members, Im quite new to kamailio, and i got a problem with the siptrace module. I read that siptrace module can capture and log all incoming and outgoing sip messages. So i put to the config file the following lines: loadmodule "siptrace.so" . . . #-------- siptrace paramas ----- modparam("siptrace", "db_url", DBURL) modparam("siptrace", "table", "sip_trace") modparam("siptrace", "trace_flag", 18) modparam("siptrace", "trace_on", 1) modparam("siptrace", "trace_sl_acks", 1) . . . route { sip_trace(); ....... } Now I can capture all incoming SIP messages, but I none of the outgoing. Where can I put the sip_trace(); command to capture also the outgoing messages? Thank you, Peter

2 3

Disk space went full in 3 days. Kamailio 3.1 @debian64
by Coca 29 Jul '11

29 Jul '11

Hi List , I have newly installed Kamailio 3.1 on a debian 64 server , replacing the OpenSIPs server And the subscribers are about 1000 people. After running 3 days, the disk with 8GB became full and caused Mysql stopped. I have checked /etc/my.cnf , and the setting about binary log is like: #log_bin = /var/log/mysql/mysql-bin.log expire_logs_days = 10 max_binlog_size = 100M It seems that binaly log for mysql is disabled. What else possible reason could cause this problem?? Any hint will be helpful. Thank you all, Coca

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 July 2011