sr-users February 2013

sr-users@lists.kamailio.org

84 participants
125 discussions

Kamailio and Ubuntu Upstart script
by Moacir Ferreira 17 Feb '13

17 Feb '13

As I posted here before, Ubuntu has moved to Upstart as the main engine to start daemons. As a result, Kamailio will fail to start on boot time because it starts before MySQL that has already been moved to the new Upstart daemon starting fashion. I am struggling to get some help from the Ubuntu community explaining how we can match the previous init script behavior when using Upstart but I got no success till now. Anyway, I have created an Upstart script for Kamailio that does most everything that the old script use to do. However, in this script I am making sure MySQL starts before Kamailio. If you have another SQL engine you must change the script to match your SQL engine by changing the “start on started” statement on the script. To use it you have to: A – Create a kamailio.conf file at “/etc/init/” with the contents of the kamailio.conf script in attach, that is the new Upstart stile init script. Please notice that I just adapted the existing script, no news… B – Create a symbolic link at /etc/init.d/ pointing to this kamailio.conf at /etc/init/. C – If you want, you can still have a /etc/default/kamailio file like it used to be and the script will behave like it used to behave when using the default file. Hopefully someone more “influent” at the Ubuntu community may get some help on how to adapt their “start on started” Upstart stanza to behave like we need for multiple possible SQL engines. Cheers! Moacir

3 2

app_python rewrite_ruri - BUG: do_action bad set*()
by V Tone 15 Feb '13

15 Feb '13

Hi, I'm having problems getting started with the app_python module. I'm getting the following in the logs: 5(8890) : <core> [action.c:785]: BUG: do_action: bad set*() type 14 5(8890) ERROR: <core> [action.c:1568]: run action error at: :0 5(8890) ERROR: app_python [python_msgobj.c:115]: Error in do_action 5(8890) ERROR: app_python [python_support.c:38]: python_exec2: Unhandled exception in the Python code: 5(8890) ERROR: app_python [python_support.c:78]: RuntimeError: Error in do_action My Python module is very basic: class Router(object): def child_init(self, child_id): return 0 def route(self, msg): msg.rewrite_ruri('sip:1000@1.2.3.4:5060') return 0 def mod_init(): instance = Router() return instance I've tested this in Kamailio 3.2 and 3.3. Can someone point me to what I'm doing wrong? Many thanks in advance, vtone

2 4

siptrace/sipcapture and MSRP
by Peter Dunkley 15 Feb '13

15 Feb '13

Hello, Is there any reason why I couldn't use the existing siptrace() function in event_route[msrp:frame-in] to relay all MSRP messages to a SIP Capture node? Will the SIP Capture node handle receiving these messages? What will end up in the WebHomer display in these cases? Regards, Peter

3 7

Warning - What does this mean?
by Krishna Kurapati 15 Feb '13

15 Feb '13

I am seeing this error lately. /usr/local/sbin/kamailio[28559]: WARNING: tm [t_lookup.c:1543]: WARNING: script writer didn't release transaction What does this mean? Krish Kura

1 0

Dialog is not cleaned up after failed calls and BYEs.
by Aft nix 15 Feb '13

15 Feb '13

Hi, I'm trying to limit concurrent calls through kamailio using following script: #!ifdef WITH_CALL_LIMIT if (is_method("INVITE")) { dlg_manage(); $var(100) = 0; get_profile_size("callquota", "$fd", "$var(100)"); if ($var(100) >= 100 ) { xdbg("DEBUG: Simultaneous calls limit reached"); sl_send_reply("503","Simultaneous calls limit reached"); exit; } set_dlg_profile("callquota","$fd"); } #!endif But the dialogs are not cleaned up after the call ends or a failed call happens. For example after two failed calls : [root@new tls]# kamctl fifo profile_get_size callquota profile:: name=callquota value= count=4 and the dialog list : [root@new tls]# kamctl fifo dlg_list dialog:: hash=896:11654 state:: 1 ref_count:: 1 timestart:: 0 timeout:: 0 callid:: iSGRqQR0C4suBpQD0rHAEgV42vw0Sbpe from_uri:: sip:123@205.164.40.150 from_tag:: d8x2LDBptN9FRJWtqFTj4DIpuQlKq.KN caller_contact:: sip:123@180.149.7.45:33852;ob caller_cseq:: 11755 caller_route_set:: caller_bind_addr:: udp:185.8.105.70:9547 callee_bind_addr:: to_uri:: sip:8801684077496@205.164.40.150 to_tag:: callee_contact:: callee_cseq:: callee_route_set:: dialog:: hash=896:11655 state:: 1 ref_count:: 1 timestart:: 0 timeout:: 0 callid:: iSGRqQR0C4suBpQD0rHAEgV42vw0Sbpe from_uri:: sip:123@205.164.40.150 from_tag:: d8x2LDBptN9FRJWtqFTj4DIpuQlKq.KN caller_contact:: sip:123@180.149.7.45:33852;ob caller_cseq:: 11755 caller_route_set:: caller_bind_addr:: udp:185.8.105.70:9547 callee_bind_addr:: to_uri:: sip:8801684077496@205.164.40.150 to_tag:: callee_contact:: callee_cseq:: callee_route_set:: dialog:: hash=896:11657 state:: 1 ref_count:: 1 timestart:: 0 timeout:: 0 callid:: iSGRqQR0C4suBpQD0rHAEgV42vw0Sbpe from_uri:: sip:123@205.164.40.150 from_tag:: d8x2LDBptN9FRJWtqFTj4DIpuQlKq.KN caller_contact:: sip:123@180.149.7.45:33852;ob caller_cseq:: 11756 caller_route_set:: caller_bind_addr:: udp:185.8.105.70:9547 callee_bind_addr:: to_uri:: sip:8801684077496@205.164.40.150 to_tag:: callee_contact:: callee_cseq:: callee_route_set:: dialog:: hash=1532:8089 state:: 1 ref_count:: 1 timestart:: 0 timeout:: 0 callid:: povqQaC.sRhKvmUaLzzR83bRXxouoNy8 from_uri:: sip:123@205.164.40.150 from_tag:: qXQll3QXrff.t27FHY2hucPfJ7K8Pfrs caller_contact:: sip:123@180.149.7.45:33852;ob caller_cseq:: 9232 caller_route_set:: caller_bind_addr:: udp:185.8.105.70:9547 callee_bind_addr:: to_uri:: sip:8801684077496@205.164.40.150 to_tag:: callee_contact:: callee_cseq:: callee_route_set:: You can see there are multiple entries. And these dialog does not get cleaned up. The data is collected when there was no call(pending or connected). My kamailio version is : [root@new tls]# kamailio -V version: kamailio 4.0.0-pre0 (x86_64/linux) 83eafc flags: STATS: Off, USE_IPV6, USE_TCP, USE_TLS, TLS_HOOKS, USE_RAW_SOCKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MEM, SHM_MMAP, PKG_MALLOC, USE_FUTEX, FAST_LOCK-ADAPTIVE_WAIT, USE_DNS_CACHE, USE_DNS_FAILOVER, USE_NAPTR, USE_DST_BLACKLIST, HAVE_RESOLV_RES ADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144, MAX_LISTEN 16, MAX_URI_SIZE 1024, BUF_SIZE 65535, DEFAULT PKG_SIZE 4MB poll method support: poll, epoll_lt, epoll_et, sigio_rt, select. id: 83eafc compiled on 18:34:58 Jan 17 2013 with gcc 4.4.6 Any suggestion?(It seems dialog module is not working as it should be. I've also tried calling unset_profile() forcefully in failure route with no luck) -- -aft

1 0

Registration and TCP connection
by Krishna Kurapati 15 Feb '13

15 Feb '13

Hi, When client connects to server over TCP/TLS and REGISTERs two things that can happen. 1. Client can disconnect the connection when the App is killed abruptly and the client did not get a chance to send unregiter. 2. CRLF KA did not arrive due to network failures in the middle. Is there a way to remove contact from usrloc table. This can spare server from trying to send message to a client who is no longer connected to the server. It would be ideal if this can be done automatically with a module param in tcp or registrar. Any suggestion on how to tie TCP connection with usrloc? Thanks Krish Kura

2 1

kamailio - simple presence over port 5061
by David Thomson 15 Feb '13

15 Feb '13

I was wondering if simple presence can work over port 5061 or if it always goes over 5060. my client (jitsi) is configured to work over port 5061, xcap is configured to work over port 5061 but I am still seeing some messages flowing over port 5060. any ideas as to what is going on? ttyl,Dave

2 1

[Fwd: Re: Deleting the expired contacts using the Rtimer module]
by kiran bhosale 15 Feb '13

15 Feb '13

he array values that we are modifying and the function that we call periodically are from our module . to exemplify i have put the code below .our requirement is that we want to delete the expired contacts without relying on usrloc module as "we have not used any DB for contact storage" but developed our own module for storing them in a file.even we had installed the SIGALRM handler in our module for decrementing the contacts but the values of array (that stores the expires) elements were zero. we thought of workaround to store the expires values to file and decrement them periodically. but frequent I/O is very consuming. whats the solution for deleting the expired contacts . #define DB_PATH "/usr/local/etc/kamailio/dbtext/syntel" #define DB_PATH1 "/usr/local/etc/kamailio/dbtext/temp" #define MAX_BUFFER 128 #define MAX_USERS 128 typedef struct { int max_bindings; int syntel_index; int expires[8]; char ip_addr[8][16]; } Syntel_users; Syntel_users syntel_database[16]={{0}}; //this is function used for storing the contacts int write_to_file (char *uri, char *user, int locator,int expires) { int Retval = 0; int fd; int bytes; char ip[13]; strncpy (ip, &uri[9], 12); ip[12] = '\0'; fd = open (DB_PATH, O_CREAT | O_RDWR | O_APPEND, 0777); if (syntel_database[locator].max_bindings < 8) { strcpy (syntel_database[locator].ip_addr[syntel_database[locator].max_bindings], uri); syntel_database[locator].expires[syntel_database[locator].max_bindings]=expires; syntel_database[locator].max_bindings++; bytes = write (fd, uri, strlen (uri)); Retval = 1; } return Retval; } //AND THIS IS FUNCTION WE CALL FROM kamailio.conf WITH RTIMER MODULE AFTER INTERVAL OF 1 SECOND. int syntel_delete (void) { int counter; int j; for (counter = 0; counter < 16; counter++) { for (j = 0; j < syntel_database[counter].max_bindings; j++) { if(syntel_database[counter].expires[j]<=0) { memset(syntel_database[counter].ip_addr[j],0,strlen(syntel_database[counter].ip_addr[j])); syntel_database[counter].max_bindings--; } else syntel_database[counter].expires[j]--; } } return 0; } BUT WHAT THIS FUNCTION GETS IS ZERO VALUES FOR EXPIRES AND NOT MODIFIED IN SYNTEL_WRITE_TO_FILE HOW TO DECREMENT THESE VALUES PERIODICALLY THEN ??

2 3

Fwd:
by Maurice Vistan 15 Feb '13

15 Feb '13

http://www.hotelgloriachiancianoterme.it/ako7ed.php?s=lf

1 0

How to rewrite "tu" in CANCEL message ?
by Julia 14 Feb '13

14 Feb '13

Hello all, Is there any way to rewrite "tu" in CANCEL message in 3.2.1? We use remove_hf / insert_hf for INVITE's "tu" modification before t_relay. It works fine, but it doesn't work for CANCEL (INVITE re-parsing is disabled). Ths,

8 19

← Newer
1
...
5
6
7
8
9
10
11
12
13
Older →

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