sr-users October 2010

sr-users@lists.kamailio.org

77 participants
158 discussions

WARNING: script writer didn't release transaction
by Juha Heinanen 07 Oct '10

07 Oct '10

after playing with t_newtran(), i started to get these to syslog: Oct 7 15:39:11 sip /usr/sbin/sip-proxy[26119]: WARNING: tm [t_lookup.c:1543]: WARNING: script writer didn't release transaction as far as i remember, in k these messages were not printed, because transactions were freed automatically when script ended. also, example in section 1.3.3. nonce_count of auth module does not include any t_release() calls. where exactly should they be put? -- juha

2 2

auth module README t_newtran() issue
by Juha Heinanen 07 Oct '10

07 Oct '10

in auth module readme, there is this kind of example code in section 1.3.3. nonce_count: # go stateful and catch retransmissions if (!t_newtran()) drop; # retransmission based on tm source comment, the #retransmission comment is not correct: /** if no transaction already exists for the message, create a new one. * atomic "new_tran" construct; it returns: * * @return <0 on error * +1 if a request did not match a transaction * 0 on retransmission that is, if t_newtran() returns false, there has been an error. drop happens automatically in case of retransmission. -- juha

2 1

kamailio 3.0.3 tls problems
by Rouskol Andrey 07 Oct '10

07 Oct '10

Hello, I have a problem running kamailio with tls support. I can successfully register only for the first time, all further registration fails with the following message in the log: Sep 28 11:53:55 siptest /usr/sbin/kamailio[16963]: ERROR: tls [tls_server.c:392]: SSL error:error:07064041:memory buffer routines:BUF_MEM_grow:malloc failure The system is a default kamailio installation on a Debian 5.0.6 system. Does somebody know what could cause the problem? Regards, Andrey.

5 17

authenticating users based on IP address and limiting the number of channels for the users using Kamailio 3.0 and Siremis 1.0
by Shrouk Khan 07 Oct '10

07 Oct '10

hi, i have been looking for a way to authenticate users based on the IP from they come from . Also i would like to limit the number of channels ( simultaneous calls) that each user can make . is their any way to do this using kamailio 3.0 and siremis 1.0 ? my configuration is like this: sipphones --->UserGroup1(Asterisk PBX)---->KamailioSipProxy--->AsteriskPSTNGateway--->PSTN 1. there can be many softphones on the user group 1 and there can be multiple calls coming from there at any time. 2. UserGroup1 is actually another SIP proxy [asterisk] with a fixed public IP 3. Kamailio Sip proxy is the one i am trying to configure . I would like to authenticate UserGroup1 based on its public IP address 4. From kamailio , calls will be forwarded to a asterisk pstn gateway. I would like to put restriction on this one : " User group 1 can not make more than 5 concurrent calls at a time" can anyone give me some suggestion or point me in some direction where I can do some reading on this one. Aslo , what would be best way to bill this UserGroup1 ? Using FreeRadius and CDRTool ? -- Regards Shrouk Khan (Khan) System Administrator / Telecommunication System Developer Office: +354 4400807 (Reykjavik) +44 2031370800 (London) Mobile: +66 875049439 (Bangkok) Web: www.softverk.is Reykjavik, Iceland // London, UK // Bangkok, Thailand

5 5

force_rtp_proxy assistance
by Stagg Shelton 06 Oct '10

06 Oct '10

I'm working on a setup where we have rtpproxy on a machine with eth0 IP 10.10.5.141/19 and eth1 IP 10.10.10.78/24. When using force_rtp_proxy("","10.10.5.141"); the connection information (c) field in the SDP is not being set to the ip 10.10.5.141 It is instead being set to 10.10.10.78 We are starting to run out of ideas on getting the proper contact address into the sdp based on call source signaling ip. Does anyone have any ideas what the problem could be? Thanks Stagg

3 8

Re: [SR-Users] add fromuser to sip request
by JR Richardson 06 Oct '10

06 Oct '10

>> Hi Alex. I use a general context in asterisk to route calls already >> and wanted to get away from pattern matches. I'm using asterisk >> realtime and want to decrease the load. I'll play around with the >> 'uac_replace_from()' and 'append_hf' to see what works best for me. > > Well, you don't have to use pattern matches. :-) You can always > direct to fixed extensions, a la: > > exten => moh,1,Answer > exten => moh,n,MusicOnHold > exten => moh,n,Hangup > > Those should be pretty snappy, even in realtime. > So the first thing I notice with using 'uac_replace_from()' is the caller ID number is replaced with the replaced value, so I guess this is not what I need for my particular application. I'll fool around with the 'append_hf' and some pattern matches. Thanks. JR -- JR Richardson Engineering for the Masses

2 1

Kamailio v3.1.0 Released
by Daniel-Constantin Mierla 06 Oct '10

06 Oct '10

Kamailio (OpenSER) v3.1.0 is out – major release with impressing number of new features and improvements. This release is a result of more than 8 months of development and testing from the teams of Kamailio (OpenSER) and SIP Express Router (SER) projects. Backed up by a solid development group, we are proud to announce that this release brings a large set of features, many for first time on the SIP server market, such as asynchronous TLS, UDP raw sockets, embedded HTTP and XCAP servers, embedded Lua, configuration file debugger. All together, there are over 15 new modules and countless improvements to old components. Since last major release (version 3.0.0, which was out in January 10, 2010), the two SIP servers, Kamailio and SER, are practically the same application, the name making the difference regarding the database structure and the extensions used for certain features, such as user database based authentication or location service. Therefore another development direction was towards smooth integration of Kamailio and SER extensions, previously duplicated modules such as auth, sl, ratelimit or sms were merged during this development cycle. Continue reading the release notes at: http://www.kamailio.org/w/kamailio-openser-v3.1.0-release-notes/ Many thanks to all developers and community members that made possible this release. -- Daniel-Constantin Mierla http://www.asipto.com

2 2

General question
by Uriel Rozenbaum 06 Oct '10

06 Oct '10

Guys, This mail has nothing to do with Kamailio or SR, so feel free to discard it. I'm trying to find a command-line tool to grab updates from an RSS feed. I tried to install rsstail but it has a lot of dependencies and cannot make it work. Does anyone have some software I can download and use in Centos 5.2? Thanks! Uriel

1 0

Problem with debug memory: kill -SIGUSR1 doesn't work fine
by César Pinto Magán 06 Oct '10

06 Oct '10

Hello, We had been experiencing memory leaks issues with our Kamailio deployment. Some of the process started to use all their assigned memory and arises allocation memory errors. Using the "kill -SIGUSR1" as explained in the Kamailio wiki and found the problem: Sep 8 11:34:04 localhost /sbin/kamailio[17275]: INFO: <core> [main.c:788]: INFO: signal 15 received Sep 8 11:34:04 localhost /sbin/kamailio[17275]: INFO: <core> [main.c:799]: Memory status (pkg): Sep 8 11:34:04 localhost /sbin/kamailio[17275]: INFO: qm_status: (0x885a60): Sep 8 11:34:04 localhost /sbin/kamailio[17275]: INFO: qm_status: heap size= 67108864 Sep 8 11:34:04 localhost /sbin/kamailio[17275]: INFO: qm_status: used= 60641440, used+overhead=67096424, free=12440 Sep 8 11:34:04 localhost /sbin/kamailio[17275]: INFO: qm_status: max used (+overhead)= 67102896 Sep 8 11:34:04 localhost /sbin/kamailio[17275]: INFO: qm_status: dumping all alloc'ed. fragments: Sep 8 11:34:04 localhost /sbin/kamailio[17275]: INFO: qm_status: 0. N address=0x8baf78 frag=0x8baf48 size=16 used=1 Sep 8 11:34:04 localhost /sbin/kamailio[17275]: INFO: qm_status: alloc'd from <core>: rvalue.c: mk_rval_expr_v(2452) Sep 8 11:34:04 localhost /sbin/kamailio[17275]: INFO: qm_status: start check=f0f0f0f0, end check= c0c0c0c0, abcdefed ... Sep 8 11:34:06 localhost /sbin/kamailio[17275]: INFO: qm_status: 1618. N address=0x95e920 frag=0x95e8f0 size=936 used=1 Sep 8 11:34:06 localhost /sbin/kamailio[17275]: INFO: qm_status: alloc'd from <core>: rvalue.c: rval_new_empty(233) Sep 8 11:34:06 localhost /sbin/kamailio[17275]: INFO: qm_status: start check=f0f0f0f0, end check= c0c0c0c0, abcdefed Sep 8 11:34:06 localhost /sbin/kamailio[17275]: INFO: qm_status: 1633. N address=0x95f528 frag=0x95f4f8 size=936 used=1 Sep 8 11:34:06 localhost /sbin/kamailio[17275]: INFO: qm_status: alloc'd from <core>: rvalue.c: rval_new_empty(233) Sep 8 11:34:06 localhost /sbin/kamailio[17275]: INFO: qm_status: start check=f0f0f0f0, end check= c0c0c0c0, abcdefed Sep 8 11:34:06 localhost /sbin/kamailio[17275]: INFO: qm_status: 1634. N address=0x95f930 frag=0x95f900 size=936 used=1 Sep 8 11:34:06 localhost /sbin/kamailio[17275]: INFO: qm_status: alloc'd from <core>: rvalue.c: rval_new_empty(233) Sep 8 11:34:06 localhost /sbin/kamailio[17275]: INFO: qm_status: start check=f0f0f0f0, end check= c0c0c0c0, abcdefed Sep 8 11:34:06 localhost /sbin/kamailio[17275]: INFO: qm_status: 1696. N address=0x962298 frag=0x962268 size=944 used=1 Sep 8 11:34:06 localhost /sbin/kamailio[17275]: INFO: qm_status: alloc'd from <core>: rvalue.c: rval_new_empty(233) Sep 8 11:34:06 localhost /sbin/kamailio[17275]: INFO: qm_status: start check=f0f0f0f0, end check= c0c0c0c0, abcdefed . . (the rvalue.c repeats all the time) . Sep 8 11:34:23 localhost /sbin/kamailio[17275]: INFO: qm_status: 64963. N address=0x4885118 frag=0x48850e8 size=944 used=1 Sep 8 11:34:23 localhost /sbin/kamailio[17275]: INFO: qm_status: alloc'd from <core>: rvalue.c: rval_new_empty(233) Sep 8 11:34:23 localhost /sbin/kamailio[17275]: INFO: qm_status: start check=f0f0f0f0, end check= c0c0c0c0, abcdefed Sep 8 11:34:23 localhost /sbin/kamailio[17275]: INFO: qm_status: 64964. N address=0x4885528 frag=0x48854f8 size=1288 used=1 Sep 8 11:34:23 localhost /sbin/kamailio[17275]: INFO: qm_status: alloc'd from <core>: rvalue.c: rval_new_empty(233) Sep 8 11:34:23 localhost /sbin/kamailio[17275]: INFO: qm_status: start check=f0f0f0f0, end check= c0c0c0c0, abcdefed We saw there was several core memory leaks resolved in the 3.0.3 version (we had the 3.0.2), so we decided to upgrade to that version. Now I was trying to check the memory status of the process (in order to see if the problem is arising again) with "kill -SIGUSR1" but now only show the memory status of the shm and the memory of the attendant process (the one who launch the other ones). I had tried to send the signal to each of the son process but I see nothing in the log. Is this a new bug or is that there is other new way to see the memory status of the processes? Thanks in advance, http://www.alhambra-eidos.es/CO/1.gif<http://www.alhambra-eidos.es/CO/1.gif> César Pinto. ICM Team +34 91 787 23 00 http://www.alhambra-eidos.es/CO/3.gif <http://www.alhambra-eidos.es/>

2 2

Fwd: lua.h / lauxlib.h issue while making deb pkgs ! (for 3.1 master branch i.e)
by X- x -X 06 Oct '10

06 Oct '10

Shouldn't me doing " git pull " today /even now have fixed it ? (it still not doing it for me though). I still get that error. of not finding those lua.h etc.. I do see it being upgrade to 3.1 during the compile ........................... dpkg-buildpackage: source package kamailio dpkg-buildpackage: source version 3.1.0 dpkg-buildpackage: source changed by Daniel-Constantin Mierla < miconda(a)gmail.com> dpkg-buildpackage: host architecture i386 .......................... On Wed, Oct 6, 2010 at 6:03 AM, Jon Bonilla <manwe(a)aholab.ehu.es> wrote: > El Wed, 6 Oct 2010 04:55:55 -0400 > X- x -X <myonlinedisk(a)gmail.com> escribió: > > > Hey Jony, > > > > while during "make deb" it complains of lua files > > > > Make sure you have an updated 3.1 branch. There was a fix for this > yesterday by > Daniel. > >

1 0

Jump to page:

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 October 2010