sr-users February 2013

sr-users@lists.kamailio.org

84 participants
124 discussions

by Techie Sup

Hi all, Sorry for this simple question. 1) I have made some changes to main.c file and want rebuild kamailio so that changes take Éffect, what is the command to rebuild? Thanks Selvam

11 years, 10 months

using dlg_manage before or after?

by Uri Shacked

Hi, I am trying to change the timeout of a dialog based on the $avp() I set on the modeparam. While testing, I notice that the change does not apply after I am using dlg_manage, only if i changed it before. Can anyone explain why is that? and is it possible to change it after doing dkg_manage? Thanks, URi

11 years, 10 months

mojtaba jahanbakhsh

by mojtaba jahanbakhsh

http://www.firstchoiceforyou.com/ecj/xnyfbj4f=4dbl9cu52nkdz

11 years, 10 months

Strip All but numbers/*/#

by Ali Jawad

Hi I am using the below to strip "-" from destination numbers, it does work just fine "I replace - with nothing", what i need to do now is to strip all characters except 0-9 * and #. Is there anyway to do it using the following configuration part if($rU =~ ".*-.*" ) { $rU = $(rU{re.subst,/-//g}); } Regards

11 years, 10 months

Re: [SR-Users] kamctl restart and mediaproxy

by Victor Seva

We use mediaproxy and kamailio and using the init.d script from the Debian package to restart kamailio has no effect on mediaproxy process. 2013/2/8 Eduardo Lejarreta <lejarreta.e(a)sarenet.es>: > Good morning Daniel. > > I send you the "messages" log which is a bit filtered. The flow is: > > Start a call, engage_mediaproxy on ports (50156, 50157, 50158, 50159) and > then "kamctl restart". As you see it seems that an instruction from kamailio > tells mediaproxy to drop the ports. > We have tried to script around "kamctl" to avoid sending orders to > mediaproxy, killing the "media-dispatcher" before Kamailio and then > restarting again (media-dispatcher) and this works OK, but seems not be a > reasonable way to fix it. > > ...... > Feb 8 11:04:51 kamailio-dev media-relay[2474]: > mediaproxy.mediacontrol.StreamListenerProtocol starting on 50156 > Feb 8 11:04:51 kamailio-dev media-relay[2474]: > mediaproxy.mediacontrol.StreamListenerProtocol starting on 50157 > Feb 8 11:04:51 kamailio-dev media-relay[2474]: > mediaproxy.mediacontrol.StreamListenerProtocol starting on 50158 > Feb 8 11:04:51 kamailio-dev media-relay[2474]: > mediaproxy.mediacontrol.StreamListenerProtocol starting on 50159 > Feb 8 11:05:06 kamailio-dev /sbin/kamailio[3461]: NOTICE: <core> > [main.c:706]: Thank you for flying kamailio!!! > Feb 8 11:05:06 kamailio-dev /sbin/kamailio[3561]: INFO: <core> > [main.c:817]: INFO: signal 15 received > Feb 8 11:05:06 kamailio-dev /sbin/kamailio[3558]: INFO: <core> > [main.c:817]: INFO: signal 15 received > Feb 8 11:05:06 kamailio-dev /sbin/kamailio[3560]: INFO: <core> > [main.c:817]: INFO: signal 15 received > Feb 8 11:05:06 kamailio-dev /sbin/kamailio[3553]: INFO: <core> > [main.c:817]: INFO: signal 15 received > Feb 8 11:05:06 kamailio-dev /sbin/kamailio[3557]: INFO: <core> > [main.c:817]: INFO: signal 15 received > Feb 8 11:05:06 kamailio-dev /sbin/kamailio[3549]: INFO: <core> > [main.c:817]: INFO: signal 15 received > Feb 8 11:05:06 kamailio-dev /sbin/kamailio[3552]: INFO: <core> > [main.c:817]: INFO: signal 15 received > Feb 8 11:05:06 kamailio-dev /sbin/kamailio[3547]: INFO: <core> > [main.c:817]: INFO: signal 15 received > Feb 8 11:05:06 kamailio-dev /sbin/kamailio[3545]: INFO: <core> > [main.c:817]: INFO: signal 15 received > Feb 8 11:05:06 kamailio-dev /sbin/kamailio[3546]: INFO: <core> > [main.c:817]: INFO: signal 15 received > Feb 8 11:05:06 kamailio-dev /sbin/kamailio[3541]: INFO: <core> > [main.c:817]: INFO: signal 15 received > Feb 8 11:05:06 kamailio-dev /sbin/kamailio[3538]: INFO: <core> > [main.c:817]: INFO: signal 15 received > Feb 8 11:05:06 kamailio-dev /sbin/kamailio[3536]: INFO: <core> > [main.c:817]: INFO: signal 15 received > Feb 8 11:05:06 kamailio-dev /sbin/kamailio[3526]: INFO: <core> > [main.c:817]: INFO: signal 15 received > Feb 8 11:05:06 kamailio-dev /sbin/kamailio[3492]: INFO: <core> > [main.c:817]: INFO: signal 15 received > Feb 8 11:05:06 kamailio-dev /sbin/kamailio[3528]: INFO: <core> > [main.c:817]: INFO: signal 15 received > Feb 8 11:05:06 kamailio-dev /sbin/kamailio[3521]: INFO: <core> > [main.c:817]: INFO: signal 15 received > Feb 8 11:05:06 kamailio-dev /sbin/kamailio[3530]: INFO: <core> > [main.c:817]: INFO: signal 15 received > Feb 8 11:05:06 kamailio-dev /sbin/kamailio[3495]: INFO: <core> > [main.c:817]: INFO: signal 15 received > Feb 8 11:05:06 kamailio-dev /sbin/kamailio[3532]: INFO: <core> > [main.c:817]: INFO: signal 15 received > Feb 8 11:05:06 kamailio-dev /sbin/kamailio[3493]: INFO: <core> > [main.c:817]: INFO: signal 15 received > Feb 8 11:05:06 kamailio-dev /sbin/kamailio[3539]: INFO: <core> > [main.c:817]: INFO: signal 15 received > Feb 8 11:05:06 kamailio-dev /sbin/kamailio[3523]: INFO: <core> > [main.c:817]: INFO: signal 15 received > Feb 8 11:05:06 kamailio-dev /sbin/kamailio[3534]: INFO: <core> > [main.c:817]: INFO: signal 15 received > Feb 8 11:05:06 kamailio-dev /sbin/kamailio[3489]: INFO: <core> > [main.c:817]: INFO: signal 15 received > Feb 8 11:05:06 kamailio-dev /sbin/kamailio[3496]: INFO: <core> > [main.c:817]: INFO: signal 15 received > Feb 8 11:05:06 kamailio-dev /sbin/kamailio[3488]: INFO: <core> > [main.c:817]: INFO: signal 15 received > Feb 8 11:05:06 kamailio-dev /sbin/kamailio[3525]: INFO: <core> > [main.c:817]: INFO: signal 15 received > Feb 8 11:05:06 kamailio-dev /sbin/kamailio[3487]: INFO: <core> > [main.c:817]: INFO: signal 15 received > Feb 8 11:05:06 kamailio-dev /sbin/kamailio[3498]: INFO: <core> > [main.c:817]: INFO: signal 15 received > Feb 8 11:05:06 kamailio-dev /sbin/kamailio[3484]: INFO: <core> > [main.c:817]: INFO: signal 15 received > Feb 8 11:05:06 kamailio-dev /sbin/kamailio[3500]: INFO: <core> > [main.c:817]: INFO: signal 15 received > Feb 8 11:05:06 kamailio-dev /sbin/kamailio[3482]: INFO: <core> > [main.c:817]: INFO: signal 15 received > Feb 8 11:05:06 kamailio-dev /sbin/kamailio[3501]: INFO: <core> > [main.c:817]: INFO: signal 15 received > Feb 8 11:05:06 kamailio-dev /sbin/kamailio[3479]: INFO: <core> > [main.c:817]: INFO: signal 15 received > Feb 8 11:05:06 kamailio-dev /sbin/kamailio[3499]: INFO: <core> > [main.c:817]: INFO: signal 15 received > Feb 8 11:05:06 kamailio-dev /sbin/kamailio[3474]: INFO: <core> > [main.c:817]: INFO: signal 15 received > Feb 8 11:05:06 kamailio-dev /sbin/kamailio[3476]: INFO: <core> > [main.c:817]: INFO: signal 15 received > Feb 8 11:05:06 kamailio-dev /sbin/kamailio[3475]: INFO: <core> > [main.c:817]: INFO: signal 15 received > Feb 8 11:05:06 kamailio-dev /sbin/kamailio[3477]: INFO: <core> > [main.c:817]: INFO: signal 15 received > Feb 8 11:05:06 kamailio-dev /sbin/kamailio[3491]: INFO: <core> > [main.c:817]: INFO: signal 15 received > Feb 8 11:05:06 kamailio-dev /sbin/kamailio[3480]: INFO: <core> > [main.c:817]: INFO: signal 15 received > Feb 8 11:05:06 kamailio-dev /sbin/kamailio[3490]: INFO: <core> > [main.c:817]: INFO: signal 15 received > Feb 8 11:05:06 kamailio-dev /sbin/kamailio[3486]: INFO: <core> > [main.c:817]: INFO: signal 15 received > Feb 8 11:05:06 kamailio-dev /sbin/kamailio[3483]: INFO: <core> > [main.c:817]: INFO: signal 15 received > Feb 8 11:05:06 kamailio-dev media-relay[2474]: (Port 50156 Closed) > Feb 8 11:05:06 kamailio-dev media-relay[2474]: (Port 50157 Closed) > Feb 8 11:05:06 kamailio-dev media-relay[2474]: (Port 50158 Closed) > Feb 8 11:05:06 kamailio-dev media-relay[2474]: (Port 50159 Closed) > Feb 8 11:05:08 kamailio-dev kamailio: INFO: <core> [tcp_main.c:4727]: > init_tcp: using epoll_lt as the io watch method (auto detected) > Feb 8 11:05:08 kamailio-dev /sbin/kamailio[3761]: INFO: usrloc > [hslot.c:53]: locks array size 512 > ...... > > Thanks and regards. > -- > Eduardo Lejarreta. > > -----Mensaje original----- > De: Daniel-Constantin Mierla [mailto:miconda@gmail.com] > Enviado el: viernes, 08 de febrero de 2013 9:38 > Para: lejarreta.e(a)sarenet.es; SIP Router - Kamailio (OpenSER) and SIP > Express Router (SER) - Users Mailing List > Asunto: Re: [SR-Users] kamctl restart and mediaproxy > > Hello, > > not using mediaproxy, but have you looked at its logs to see if prints some > messages? > > Cheers, > Daniel > > On 2/7/13 5:03 PM, Eduardo Lejarreta Langarica SARENET wrote: >> Good evening again. >> >> Kamailio 3.2.2 and mediaproxy 2.5.2 >> >> An long-time issue for us: >> >> kamctl restart stops mediaproxy audio. >> >> is there anyway to avoid this? >> >> Any idea will be helpful. >> >> Thanks and best regards. >> ---------------------------------------------------------------------- >> ------------------------------------------------------------- >> Eduardo Lejarreta >> >> >> >> >> _______________________________________________ >> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing >> list sr-users(a)lists.sip-router.org >> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users > > -- > Daniel-Constantin Mierla - http://www.asipto.com > http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda > Kamailio World Conference, April 16-17, 2013, Berlin > - http://conference.kamailio.com - > > > > _______________________________________________ > SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list > sr-users(a)lists.sip-router.org > http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

11 years, 10 months

branching for v4.4.x and unfreezing development

by Daniel-Constantin Mierla

Hello, it is time to sketch the road to the next major release, my plan is: - create branch 4.4 on Wednesday, February 27, 2013 - that will unfreeze development, so personal branches and contributions kept in external repositories can be merged in master branch - consider to release v4.4.0 in first or second week of March Any other opinions? Cheers, Daniel -- Daniel-Constantin Mierla - http://www.asipto.com http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda Kamailio World Conference, April 16-17, 2013, Berlin - http://conference.kamailio.com -

11 years, 10 months

Nonce secret and expiry value

by Andreas Granig

Hi guys, Nonces have a default expiry value of 300 seconds. Does this still apply if the "secret" parameter is set? So can you use both "secret" and "nonce_expire" value together, taking for granted that the time is in sync over multiple proxies? Andreas

11 years, 10 months

2 kamailio servers as proxy

by Andrei Rotaras

Hello, We have this situation: 2 servers, each with his own "location". First user is registered on one server and second user on other server. If we receive an invite for a user that is on other server's location, second server doesn't react on hostrewrite(dynamic routing,forward, append_branch, t_replicate, etc) from first server. Can you please advise us in what direction to look? Our kamailio version: kamailio-3.3.1-1.2.x86_64. (installed from rpm) Thank you! Best regards, Andrei Rotaras NOC Systems Engineer StarNet Moldova Phone: +(373-22) 844-770 Fax: +(373-22) 844-445 Mob: +(373-79) 700-552 E-mail: arotaras(a)starnet.md<mailto:arotaras@starnet.md> Address: 4th Floor, Calea Iesilor 10, Chisinau, Republic of Moldova Web: http://www.starnet.md<http://www.starnet.md/> [Description: Description: Description: starnet] This email message is confidential and may contain privileged information. If you are not the above named addressee, it may be unlawful for you to read, copy, distribute, disclose or otherwise use the information in this email message. If you are not the intended recipient of this email message please telephone one of the above indicated numbers immediately and delete this message.

11 years, 10 months

Any substitute or replace function for the request-/response line of SIP messages available?

by Klaus Feichtinger

Hi, I have a very specific situation that the implementation of a customer SIP user agent is absolutely not standards conform. Therefore, I use Kamailio as a SIP protocol adapter between the non-standard conform user agent(s) and the typical RFC3261 compliant user agents. Most conversions are working fine. But in a very specific scenario I have to change/convert a SIP response message to a SIP request message and change the SIP method´s name. This conversion is no problem for the SIP header fields. However, I haven't found a way for adapting the response-/request line of a SIP message. This line seems to be protected. The described situation of the perverse conversion I try to realize is following (please do not ask "why?" or think I'm mad...): (mad) UA1 == INVITE ==> SIP-Prot-Adapter(Kamailio) == INVITE ==> (typ.)UA2 UA1 <== BYE == SIP-Prot-Adapter(Kamailio) <== 488 == (typ.)UA2 UA1 == BYE ==> SIP-Prot-Adapter(Kamailio) == ACK ==> (typ.)UA2 I use the "textops" module for substitution and/or replacement in SIP header fields. But the "subst" and "replace" functions cannot be used for the request-/response line on top of the SIP messages. I was a little bit irritated, as the "search" function is still working on these lines, but not the subst/replace function. Creating a new SIP message with the UAC module (as alternative) is not okay, as this new message does not use the same values for Call-ID, From-tag a.s.o. and these values can't be changed before sending the message. Does anybody know a way / function / method for manipulating the request-/response line of a message? It would be perfect using a function á la "sed"/subst. Thanks Klaus P.S. I tested with kamailio-3.3.3

11 years, 10 months

Kamailio and Ubuntu Upstart script

by Moacir Ferreira

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

11 years, 10 months

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

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