sr-users March 2008

sr-users@lists.kamailio.org

169 participants
237 discussions

[Serusers] ser-0.9.6: modules/postgres bugreport & patch

by Alexandre Snarskii

Hi! I'm running ser-0.9.6, on FreeBSD 6.1-stable, database backend is postgresql version 8.1.3. Today I got errors in logfiles, saying: messages.2.bz2:May 29 14:35:03 <XXX> /usr/local/sbin/ser[51448]: ERROR:avpops:dbrow2avp: dbrow contains NULL fields The similar problem reported in: http://lists.iptel.org/pipermail/serusers/2005-May/019681.html with much more detailed description of error, database contents and config samples. Patch is trivial, and looks more like a fix to copy'n'paste error: in mysql/val.c function str2val states: if (!_s) { memset(_v, 0, sizeof(db_val_t)); VAL_TYPE(_v) = _t; VAL_NULL(_v) = 1; return 0; } VAL_NULL(_v) = 0; and the last line mentions that 'well, that's value is not NULL'. In postgresql/db_val.c, line 182, function str2valp, the same statement is the: if (!_s) { DLOG("str2valp", "got a null value"); VAL_TYPE(_v) = _t; VAL_NULL(_v) = 1; return 0; } without explicit notification that this is not-NULL value. More than, nowhere else in this function VAL_NULL(_v) not set to 0. So, if a value _v.val contained anyting but 0 at the function start, resulting value will be threated as NULL despite the fact, that _s is NOT NULL. Patch is obvious, just add VAL_NULL(_v)=0; after cited block (line 188) and everyting will be ok. At least for me it's ok for some hours :)

16 years

[OpenSER-Users] Acceptor peer failed establishing state[3003], closing

by bhargav.b＠renovau.com

actually i am authenticating a user using openser and opendiameters NASREQ application as the client and server.at present the openser is sending the all needed avp's to opendiameter client.i can see all the avp code and avp data on the client side. my problem is that the on the diameter server side the avp,s are not transferred by the client. the client is giving something like (6372|1698151312) Acceptor peer failed establishing state [3003], closing i am confused about it.by reading some drafts i came to know that the error is due to realm mismatch.but i am sending the same realm as the opendiameter's realm.in both the cases it is [bhargav.s]. before i sent the avp's from openser side there was no such problem showing on the client side.if anybody know the solution please help me regards bhargav.b(a)renovau.com

16 years, 5 months

[OpenSER-Users] UDP Buffer Size / OpenSER / Linux

by Carsten Bock

Hi, short question: Can anybody give me a hint regarding the Linux UDP-Buffer size? Are there any known good values for this or is the default value (128k) of Linux sufficient? I've read, regarding other SIP-Systems (namely IBM SIP Servlets and Communigate pro), the recommendation to increase the UDP-Buffer-size to 3 or even 4 MByte.... Are there any recommended / known best values for heavy load OpenSER Installations? Thanks in advance, Carsten Reference: http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/com.…

16 years, 5 months

[Serusers] SER Nokia CANCEL Problem

by Abdul Qadir

Hi , I tried to call from one nokia sip (E61 and other models )phone to another nokia sip phone. The call works fine. The problem comes only when I call from Phone A to Phone B and then immediately cancel the call(from Phone A). The Phone A will hangup the call as it sent CANCEL but the SER will ignore this CANCEL and still send INVITE to Phone B resulting in a ghost call situation. I tried to capture a log of message and found that Phone A "CANCEL" message is received on SER even before any provisional response from Phone B. Therefor SER doesnot relay this CANCEL request to Phone B. I even checked RFC which clearly says that UAC should not send CANCEL untill it receives any provisional response. I talked to Nokia expert and they said the 100 Trying message from your server is considered as provisional response, therefor behaviour of client is absolutely correct. Is there any way I can stop 100 Trying message and still run statefull SER, so that I can verify what nokia said. Any ideas suggestions are welcome. Thanking you all in advance. Best Regards, Abdul Qadir --------------------------------- Don't be flakey. Get Yahoo! Mail for Mobile and always stay connected to friends.

16 years, 6 months

[OpenSER-Users] null socket list

by Michael Barinek

I have openser-1.3.1-notls installed although am unable to start openser. Any suggestions/ideas regarding the below error? Any existing docs/links would be great. Thanks /// Mar 20 08:59:14 [18124] WARNING:core:fix_socket_list: could not rev. resolve 10.138.86.56 Mar 20 08:59:14 [18124] WARNING:core:fix_socket_list: could not rev. resolve 10.138.87.100 Mar 20 08:59:14 [18124] WARNING:core:fix_socket_list: could not rev. resolve 10.37.129.2 Mar 20 08:59:14 [18124] WARNING:core:fix_socket_list: could not rev. resolve 10.211.55.2 Mar 20 08:59:14 [18124] WARNING:core:fix_socket_list: could not rev. resolve 10.138.86.56 Mar 20 08:59:14 [18124] WARNING:core:fix_socket_list: could not rev. resolve 10.138.87.100 Mar 20 08:59:14 [18124] WARNING:core:fix_socket_list: could not rev. resolve 10.37.129.2 Mar 20 08:59:14 [18124] WARNING:core:fix_socket_list: could not rev. resolve 10.211.55.2 Listening on udp: 127.0.0.1 [127.0.0.1]:5060 udp: 10.138.86.56 [10.138.86.56]:5060 udp: 10.138.87.100 [10.138.87.100]:5060 udp: 10.37.129.2 [10.37.129.2]:5060 udp: 10.211.55.2 [10.211.55.2]:5060 tcp: 127.0.0.1 [127.0.0.1]:5060 tcp: 10.138.86.56 [10.138.86.56]:5060 tcp: 10.138.87.100 [10.138.87.100]:5060 tcp: 10.37.129.2 [10.37.129.2]:5060 tcp: 10.211.55.2 [10.211.55.2]:5060 Aliases: tcp: my.machine.name:5060 udp: my.machine.name:5060 Mar 20 08:59:14 [18124] WARNING:core:main: no fork mode and more than one listen address found(will use only the first one) Mar 20 08:59:14 [18124] INFO:core:init_tcp: using kqueue as the TCP io watch method (auto detected) Mar 20 08:59:14 [18124] NOTICE:core:main: version: openser 1.3.1-notls (i386/darwin) Mar 20 08:59:14 [18124] INFO:core:main: using 32 Mb shared memory Mar 20 08:59:14 [18124] INFO:core:main: using 1 Mb private memory per process Mar 20 08:59:14 [18124] INFO:sl:mod_init: Initializing StateLess engine Mar 20 08:59:14 [18124] INFO:tm:mod_init: TM - initializing... Mar 20 08:59:14 [18124] CRITICAL:tm:uac_init: null socket list Mar 20 08:59:14 [18124] ERROR:tm:mod_init: uac_init failed Mar 20 08:59:14 [18124] ERROR:core:init_mod: failed to initialize module tm Mar 20 08:59:14 [18124] ERROR:core:main: error while initializing modules

16 years, 6 months

[OpenSER-Users] mediaproxy server NEW FEATURE!!!

by Gonzalo J. Sambucaro

Folks, I developed a new feature in the Media Proxy project of AG-Proyect. With this new feature the Media Proxy Server is now able to manage the problem of the NAT IP change in an established call. It is currently in production and working without any problem. Somebody wants to test it? I would like to know what to do to make this feature available to everybody. Does anybody know? Regards, ------------------------------ Details: ------- Supose that there is an established rtp connection between two endpoints and the media proxy is in the middle doing the relay of the rtp streams, let´s say (MP = mediaproxy) EP A <--------->[NAT with IP1]<-----------> MP <--------------------> EP B EP A sends rtp to MP_IP:MP_PORT passing through the NAT box. EP B sends rtp to MP_IP:MP_PORT without passing through a NAT box. The MP know that the caller = NAT_IP1:NAT_PORT1, and the called = EP_B_IP:EP_B_PORT Now, supose that the NAT box change their PUBLIC IP from IP1 to IP2, so this escenary EP A <------->[NAT with IP1]<---------> MP <-------------> EP B will change to this EP A <------->[NAT with IP2]<---------> MP <--------------> EP B so the MP should detect that change of IPs and continue relaying the rtp streams but now to IP2:PORT2 instead of IP1:PORT1. Well, that was the situation y have experienced. To fix this, I developed this solution, changing rtphandler.py file: 1) When the first rtp packet of a source arrives, save the SSRC field in the MP. - Save the SSRC of the caller. - Save the SSRC of the called. 2) If arrives a rtp packet with unknown source IP but with the same SSRC field of some of the two streams, updates the binding (with the new IP detected) between the caller and the MP or between the called and the MP according to the field SSRC previously saved. Note: SSRC (RFC 3550 RTP), (from the rfc: "The SSRC identifier carried in the RTP header and in various fields of RTCP packets is a random 32-bit number that is required to be globally unique within an RTP session ") -------------------------------- -- Gonzalo J. Sambucaro Ingeniería de Software Tel: +54-341-4230504 MSLC gonzalo.sambucaro(a)mslc.com.ar www.mslc.com.ar Ocampo y Esmeralda - Vivero de Empresas de Base Tecnológica Ciudad Universitaria Rosario UNR, CCT CONICET Rosario - Santa Fé - Argentina -- Gonzalo J. Sambucaro Ingeniería de Software Tel: +54-341-4230504 MSLC gonzalo.sambucaro(a)mslc.com.ar www.mslc.com.ar Ocampo y Esmeralda - Vivero de Empresas de Base Tecnológica Ciudad Universitaria Rosario UNR, CCT CONICET Rosario - Santa Fé - Argentina

16 years, 6 months

[Serusers] RTPProxy

by Strassburger, Patrick

> Hi all, > > Is there an easy way to disable RTPProxy for certain calls eg. based > on called number? > Am using the ser.cfg from > http://www.iptel.org/ser/howtos/optimizing_the_use_of_rtp_proxy. > > For whatever reason all calls are passing the RTPProxy. > - I would like to disable the RTPProxy for calls where I know the > destination is able to handle NAT. > - For calls where I know both UAT are behind the same NAT. > As soon as I update the realm of those clients with whatever > value beside the ser IP adress, those useres cannot login anymore. > > Is this sufficient information - do you need the ser.cfg? > > Thanks > Patrick > > > ************************************************************************************* The message is intended for the named addressee only and may not be disclosed to or used by anyone else, nor may it be copied in any way. The contents of this message and its attachments are confidential and may also be subject to legal privilege. If you are not the named addressee and/or have received this message in error, please advise us by e-mailing security(a)colt.net and delete the message and any attachments without retaining any copies. Internet communications are not secure and COLT does not accept responsibility for this message, its contents nor responsibility for any viruses. No contracts can be created or varied on behalf of COLT Telecommunications, its subsidiaries or affiliates ("COLT") and any other party by email Communications unless expressly agreed in writing with such other party. Please note that incoming emails will be automatically scanned to eliminate potential viruses and unsolicited promotional emails. For more information refer to www.colt.net or contact us on +44(0)20 7390 3900.

16 years, 6 months

[OpenSER-Users] Openser Mediaproxy

by Abdul

Hi friends, I was trying to install Openser and Mediaproxy. but when i am starting media proxy using /etc/init.d/mediaproxy star I am getting some error in syslog. Jan 22 12:18:27 hatifserver4 mediaproxy[14707]: warning: accounting is enabled but the accounting module is missing. accounting is not available! Jan 22 12:18:27 hatifserver4 mediaproxy[14707]: Listening for commands on local socket `/var/run/mediaproxy.sock' Jan 22 12:18:27 hatifserver4 mediaproxy[14707]: Listening for remote commands on `212.XXXXXXXXXXXXXx:25060' Jan 22 12:18:27 hatifserver4 mediaproxy[14707]: Remote commands are allowed from: 212.XXXXXXXXXXXXXXXXXX, 127.0.0.1 Jan 22 12:18:27 hatifserver4 mediaproxy[14707]: Using IP address `XXXXXXXXXXXXX' for the RTP/RTCP proxy Jan 22 12:18:27 hatifserver4 proxydispatcher[14710]: Traceback (most recent call last): Jan 22 12:18:27 hatifserver4 proxydispatcher[14710]: File "/usr/local/mediaproxy/proxydispatcher.py", line 65, in <module> Jan 22 12:18:27 hatifserver4 proxydispatcher[14710]: Jan 22 12:18:27 hatifserver4 proxydispatcher[14710]: import dispatcher Jan 22 12:18:27 hatifserver4 proxydispatcher[14710]: File "/usr/local/mediaproxy/modules/dispatcher.py", line 39, in <module> Jan 22 12:18:27 hatifserver4 proxydispatcher[14710]: Jan 22 12:18:27 hatifserver4 proxydispatcher[14710]: from accounting import accounting, StopRecordSerializer, UnserializeError Jan 22 12:18:27 hatifserver4 proxydispatcher[14710]: File "/usr/local/mediaproxy/modules/accounting.py", line 17, in <module> Jan 22 12:18:27 hatifserver4 proxydispatcher[14710]: Jan 22 12:18:27 hatifserver4 proxydispatcher[14710]: from radius import * Jan 22 12:18:27 hatifserver4 proxydispatcher[14710]: File "/usr/local/mediaproxy/modules/radius.py", line 10, in <module> Jan 22 12:18:27 hatifserver4 proxydispatcher[14710]: Jan 22 12:18:27 hatifserver4 proxydispatcher[14710]: import pyrad.client Jan 22 12:18:27 hatifserver4 proxydispatcher[14710]: ImportError Jan 22 12:18:27 hatifserver4 proxydispatcher[14710]: : Jan 22 12:18:27 hatifserver4 proxydispatcher[14710]: No module named pyrad.client Jan 22 12:18:27 hatifserver4 proxydispatcher[14710]: exiting. this is our Mediaproxy.ini file i am not using any kind of accounting or radius in INI file but i don't kow why it is shwoing accounting is enable [Dispatcher] start = yes socket = /var/run/proxydispatcher.sock group = openser defaultProxy = /var/run/mediaproxy.sock [MediaProxy] start = yes socket = /var/run/mediaproxy.sock group = openser listen = XXXXXXXXXXXXXx allow = XXXXXXXXXXXXXXXXXXXXXXXXxx proxyIP = XXXXXXXXXXXXXXXXXXXXXX portRange = 20000:65000 TOS = 0xb8 idleTimeout = 60 holdTimeout = 3600 forceClose = 0 accounting = none [Accounting] accounting = none --------------------------------- Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now.

16 years, 6 months

[OpenSER-Users] Radius with additional parameters

by Alex Massover

Hello! I see how I can receive additional parameters from Radius server via AVPs. But I wonder if it's possible to send additional parameters (headers) to Radius server in requests? For example I want to pass to Radius server P-Asserted header, in case that I need validate it? -- Best Regards, Alex Massover VoIP Development Manager Jajah Inc.

16 years, 6 months

[OpenSER-Users] mi_datagram module bind failure

by Sigrid Thijs

Hi, we're setting up OpenSER 1.3.0 on a FreeBSD system, with the mi_datagram module configured, and when we start up openser, we get the following error: /usr/local/sbin/openser[3139]: NOTICE presence:child_init: init_child [1] pid [3139] /usr/local/sbin/openser[3138]: ERROR:mi_datagram:mi_init_datagram_server: bind: Invalid argument /usr/local/sbin/openser[3142]: NOTICE presence:child_init: init_child [4] pid [3142] /usr/local/sbin/openser[3138]: CRITICAL:mi_datagram:pre_datagram_process: function mi_init_datagram_server returned with error!!! /usr/local/sbin/openser[3138]: ERROR:core:start_module_procs: pre-fork function failed for process "MI Datagram" in module mi_datagram In the openser configuration: modparam ("mi_datagram", "socket_name", "udp:[ip.add.ress.here]:5068") We checked that the port is not in use. Note that this is working fine when running the same openser version on a linux based system. We are also not having this issue when we specify a UNIX socket. Do you have any idea what could be wrong? kind regards, Sigrid

16 years, 6 months

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 2008