sr-users April 2011

sr-users@lists.kamailio.org

64 participants
105 discussions

"kamctl fifo debug" does not work
by Klaus Darilion 07 Apr '11

07 Apr '11

root@pbx-kam-1:/home/klaus3000# kamctl fifo debug DEBUG:: 2 root@pbx-kam-1:/home/klaus3000# kamctl fifo debug 0 DEBUG:: 0 Mar 9 11:04:23 pbx-kam-1 /usr/sbin/kamailio[4548]: INFO: <core> [cfg/cfg_ctx.c:411]: INFO: cfg_set_now(): core.debug has been changed to 0 but: root@pbx-kam-1:/home/klaus3000# kamctl fifo debug DEBUG:: 2 Is this a bug? regards Klaus

2 2

Kamailio at Google Summer of Code 2011
by Daniel-Constantin Mierla 07 Apr '11

07 Apr '11

Hello, for the second year, Kamailio is participating in GSoC program. For 2011, the proposal is to implement a signaling gateway between SIP and JINGLE to enable voice calls between the two networks: http://www.jitsi.org/index.php/GSOC2011/KamailioJingle If you are a student, or you know a student, interested in this project, just write me or to sr-dev(a)lists.sip-router.org. The application starts today and the deadline is April 8, therefore it is quite a short period, you will have to hurry. You can read more about the GSoC program and Kamailio at: http://www.kamailio.org/w/gsoc-2011/ http://www.jitsi.org/index.php/Development/Gsoc2011 Cheers, Daniel -- Daniel-Constantin Mierla http://www.asipto.com

7 15

Cannot run Kamailio on public IP
by spamasbl＠gmail.com 07 Apr '11

07 Apr '11

Hello all, I have installed latest Kamailio 3.1.3 on latest ubuntu server. Everything seems to be working well on my LAN. I can successfully register with local Kamailio IP address (192.168.1.137). The issue is that I can not run Kamailio on my public IP: listen=udp:77.XX.XX.XX:5060 listen=udp:192.168.1.137:5060 port=5060 Kamailio runs behind Linksys WRT54GL router with latest Linksys firmware and DMZ is turned on (192.168.1.137). Here is the error I am getting when trying to run kamailio with my public IP: Apr 7 02:57:40 sipbox kamailio[1050]: ERROR: <core> [udp_server.c:400]: ERROR: udp_init: bind(7, 0x82cc6e4, 16) on 77.XX.XX.XX: Cannot assign requested address Do you have any idea what I'm doing wrong ? Thanks !

6 10

off-topic: jobs & projects - figuring out the best solution
by Daniel-Constantin Mierla 06 Apr '11

06 Apr '11

Hello, recently the demand in jobs and projects related to kamailio seemed to increase. I can just say that I am very happy with that. While announcing on the mailing lists is ok, I think we should try to make the process better and more productive, i.e., easier to advertise by publishers and easier to read for those interesting. For that, imo, we need a web page where someone can post such announcements and the others can read it. Since I had this idea in mind for some while, I searched for a dokuwiki plugin that could help, so we can reuse our wiki system. I found bureaucracy plugin, but does not seem to be ready for latest dokuwiki version according to its page: http://www.dokuwiki.org/plugin:bureaucracy But maybe it just works, I should try it instead of waiting, anyhow spare time is not my friend these days... Alternatives would be: - a wordpress plugin - haven't searched for one yet, but there are tons of plugins for WP, maybe one will fit the needs - another web application designed for such purposes My question to you is whether you can recommend a solution which we can evaluate. Ideally (or better said, as many characteristics to be met as possible), the system should be able to: - allow people to post announcements for jobs and projects (with or without prior registration, but with spam prevention - e.g., captcha) - allow to publish details about the job/projects, contact addresses, validity period - allow to invalidate an announcement when the position/project is taken - send an email notification when the announcement is done first time, with a link to the web page of the announcement, so we can send it one to a particular mailing list Cheers, Daniel -- Daniel-Constantin Mierla http://www.asipto.com

4 3

job offer: System administrator internet access services
by Henning Westerholt 06 Apr '11

06 Apr '11

Job offer: Interested in working with one of the biggest Voice over IP networks in europe? We're hiring and have one additional IT operation position open in our team in Karlsruhe, Germany at the moment. You would be responsible in a team of motivated system administrators for the operation and maintenance of the radius and CPE auto-provisioning services at 1&1. Furthermore you would support our on-call service for all the services operated from the team, including VoIP. A solid understanding of german is necessary for the job, for more informations (additional requirements, how to apply..) please refer to the opening on the job web page. Of course please feel free to contact me per mail as well. http://www.united-internet.de/JobsJobDetail?__sendingdata=1&JobDetails.jobI… Best regards, Henning Westerholt -- Henning Westerholt - Head of IT Operations Internet Access & Communications 1&1 Internet AG, Brauerstraße 48, 76135 Karlsruhe, Germany

1 0

Re: [SR-Users] Kamailio ims / rtpproxy
by Carsten Bock 06 Apr '11

06 Apr '11

Hi, the Kamailio IMS modules are based on the OpenIMSCore-CSCF modules, which have built-in RTPProxy support. I am working on replacing the built-in RTPProxy support in the CSCF modules with the "original" rtpproxy-module of the Kamailio/sip-router.org. It does depend on your config, which RTPProxy support you use.... (but the focus is currently on other parts, be patient). Carsten 2011/4/6 Pavel Segeč <Pavel.Segec(a)fri.uniza.sk>: > Hi, > > I do not understand, may you clarify it? I'm using Kamailio based PCSCF not OIMSC, and kamailio has rtpproxy module...should I'm able to build PCSCF using sip router? > > palo > >> -----Original Message----- >> From: Carsten Bock [mailto:carsten@ng-voice.com] >> Sent: Wednesday, April 06, 2011 11:30 AM >> To: SIP Router - Kamailio (OpenSER) and SIP Express Router (SER) - Users >> Mailing List >> Cc: Pavel Segeč >> Subject: Re: [SR-Users] Kamailio ims / rtpproxy >> >> Hi, >> >> one reason more to replace the built-in RTP-Proxy support of the CSCF >> with the "real" rtpproxy moduie of sip-router.org! ;-) >> >> Carsten >> >> 2011/4/6 Pavel Segeč <Pavel.Segec(a)fri.uniza.sk>: >> > Hi Carsten, >> > >> > Thank you for answer. I did it as you described (anyway, i think, that >> nat traversal is by default on), but there were still some problems. >> After some deeper testing, the PCSCF with RTPproxy works well with two >> Monster client (caller and calle). The problem is with Boghe IMS >> clients, I do not know why, private address inside of the SDP is not >> rewritten, what is interesting, media ports are changing. >> > >> > regards >> > >> > palo >> > >> >> -----Original Message----- >> >> From: sr-users-bounces(a)lists.sip-router.org [mailto:sr-users- >> >> bounces(a)lists.sip-router.org] On Behalf Of Carsten Bock >> >> Sent: Wednesday, April 06, 2011 10:32 AM >> >> To: SIP Router - Kamailio (OpenSER) and SIP Express Router (SER) - >> Users >> >> Mailing List >> >> Cc: Pavel Segeč >> >> Subject: Re: [SR-Users] Kamailio ims / rtpproxy >> >> >> >> Hi, >> >> >> >> there is no documentation on the RTPProxy interface of the Kamailio >> >> IMS module yet. >> >> You need to have the following linse in the Kamailio.cfg: >> >> >> >> # Enabled Features on this host: >> >> #!define WITH_NAT >> >> [...] >> >> #!ifdef WITH_NAT >> >> #!define RTPPROXY "udp:127.0.0.1:22222" >> >> #!endif >> >> [...] >> >> #!ifndef WITH_NAT >> >> [...] >> >> #!else >> >> modparam("pcscf","NAT_enable", 1) >> >> modparam("pcscf","ping", 1) >> >> modparam("pcscf","ping_all", 0) >> >> modparam("pcscf","nat_detection_type", 0x17) >> >> modparam("pcscf","rtpproxy_socket", RTPPROXY) >> >> modparam("pcscf","rtpproxy_enable", 1) >> >> modparam("pcscf","rtpproxy_disable_tout", 60) >> >> modparam("pcscf","rtpproxy_retr", 5) >> >> modparam("pcscf","rtpproxy_tout", 1) >> >> #!endif >> >> >> >> Kind regards, >> >> Carsten >> >> >> >> 2011/4/5 Pavel Segeč <pavel.segec(a)fri.uniza.sk>: >> >> > Hi, >> >> > >> >> > >> >> > >> >> > I would like ask you if there is a kamailio ims module >> documentation >> >> > somewhere. I need some deeper information how some things are >> >> implemented, I >> >> > have problem to setup NAT traversal with RTPproxy for our Kamailio >> IMS >> >> > platform. There is no communication among the PCSCF and RTPproxy >> >> server over >> >> > control udp sock. We tried unix socket also with the same results. >> >> > >> >> > >> >> > >> >> > Thanks >> >> > >> >> > >> >> > >> >> > palo73 >> >> > >> >> > http://nil.uniza.sk >> >> > >> >> > __________ Informacia od ESET NOD32 Antivirus, verzia databazy 6016 >> >> > (20110405) __________ >> >> > >> >> > Tuto spravu preveril ESET NOD32 Antivirus. >> >> > >> >> > http://www.eset.sk >> >> > >> >> > _______________________________________________ >> >> > 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 >> >> > >> >> > >> >> >> >> >> >> >> >> -- >> >> Carsten Bock >> >> http://www.ng-voice.com >> >> mailto:carsten@ng-voice.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 >> >> >> >> >> >> __________ Informacia od ESET NOD32 Antivirus, verzia databazy 6017 >> >> (20110405) __________ >> >> >> >> Tuto spravu preveril ESET NOD32 Antivirus. >> >> >> >> http://www.eset.sk >> >> >> > >> > >> > __________ Informacia od ESET NOD32 Antivirus, verzia databazy 6017 >> (20110405) __________ >> > >> > Tuto spravu preveril ESET NOD32 Antivirus. >> > >> > http://www.eset.sk >> > >> > >> > >> > _______________________________________________ >> > 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 >> > >> >> >> >> -- >> Carsten Bock >> http://www.ng-voice.com >> mailto:carsten@ng-voice.com >> >> Schomburgstr. 80 >> 22767 Hamburg >> Germany >> >> Mobile +49 179 2021244 >> Office +49 40 34927219 >> Fax +49 40 34927220 >> >> >> __________ Informacia od ESET NOD32 Antivirus, verzia databazy 6017 >> (20110405) __________ >> >> Tuto spravu preveril ESET NOD32 Antivirus. >> >> http://www.eset.sk >> > > > __________ Informacia od ESET NOD32 Antivirus, verzia databazy 6017 (20110405) __________ > > Tuto spravu preveril ESET NOD32 Antivirus. > > http://www.eset.sk > > > > _______________________________________________ > 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 > -- Carsten Bock http://www.ng-voice.com mailto:carsten@ng-voice.com

3 5

Re: [SR-Users] Kamailio ims / rtpproxy
by Alex Balashov 06 Apr '11

06 Apr '11

On 04/06/2011 05:48 AM, Pavel Segeč wrote: > I do not understand, may you clarify it? I'm using Kamailio based > PCSCF not OIMSC, and kamailio has rtpproxy module...should I'm able > to build PCSCF using sip router? Don't worry about this. This is a reference to an ongoing bit of development esoterica related to the fact that Kamailio already has--and has had for a very long time--a module to control rtpproxy. It is not part of the IMS module framework Carsten is developing. -- Alex Balashov - Principal Evariste Systems LLC 260 Peachtree Street NW Suite 2200 Atlanta, GA 30303 Tel: +1-678-954-0670 Fax: +1-404-961-1892 Web: http://www.evaristesys.com/

1 0

Re: [SR-Users] Kamailio ims / rtpproxy
by Carsten Bock 06 Apr '11

06 Apr '11

Hi, one reason more to replace the built-in RTP-Proxy support of the CSCF with the "real" rtpproxy moduie of sip-router.org! ;-) Carsten 2011/4/6 Pavel Segeč <Pavel.Segec(a)fri.uniza.sk>: > Hi Carsten, > > Thank you for answer. I did it as you described (anyway, i think, that nat traversal is by default on), but there were still some problems. After some deeper testing, the PCSCF with RTPproxy works well with two Monster client (caller and calle). The problem is with Boghe IMS clients, I do not know why, private address inside of the SDP is not rewritten, what is interesting, media ports are changing. > > regards > > palo > >> -----Original Message----- >> From: sr-users-bounces(a)lists.sip-router.org [mailto:sr-users- >> bounces(a)lists.sip-router.org] On Behalf Of Carsten Bock >> Sent: Wednesday, April 06, 2011 10:32 AM >> To: SIP Router - Kamailio (OpenSER) and SIP Express Router (SER) - Users >> Mailing List >> Cc: Pavel Segeč >> Subject: Re: [SR-Users] Kamailio ims / rtpproxy >> >> Hi, >> >> there is no documentation on the RTPProxy interface of the Kamailio >> IMS module yet. >> You need to have the following linse in the Kamailio.cfg: >> >> # Enabled Features on this host: >> #!define WITH_NAT >> [...] >> #!ifdef WITH_NAT >> #!define RTPPROXY "udp:127.0.0.1:22222" >> #!endif >> [...] >> #!ifndef WITH_NAT >> [...] >> #!else >> modparam("pcscf","NAT_enable", 1) >> modparam("pcscf","ping", 1) >> modparam("pcscf","ping_all", 0) >> modparam("pcscf","nat_detection_type", 0x17) >> modparam("pcscf","rtpproxy_socket", RTPPROXY) >> modparam("pcscf","rtpproxy_enable", 1) >> modparam("pcscf","rtpproxy_disable_tout", 60) >> modparam("pcscf","rtpproxy_retr", 5) >> modparam("pcscf","rtpproxy_tout", 1) >> #!endif >> >> Kind regards, >> Carsten >> >> 2011/4/5 Pavel Segeč <pavel.segec(a)fri.uniza.sk>: >> > Hi, >> > >> > >> > >> > I would like ask you if there is a kamailio ims module documentation >> > somewhere. I need some deeper information how some things are >> implemented, I >> > have problem to setup NAT traversal with RTPproxy for our Kamailio IMS >> > platform. There is no communication among the PCSCF and RTPproxy >> server over >> > control udp sock. We tried unix socket also with the same results. >> > >> > >> > >> > Thanks >> > >> > >> > >> > palo73 >> > >> > http://nil.uniza.sk >> > >> > __________ Informacia od ESET NOD32 Antivirus, verzia databazy 6016 >> > (20110405) __________ >> > >> > Tuto spravu preveril ESET NOD32 Antivirus. >> > >> > http://www.eset.sk >> > >> > _______________________________________________ >> > 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 >> > >> > >> >> >> >> -- >> Carsten Bock >> http://www.ng-voice.com >> mailto:carsten@ng-voice.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 >> >> >> __________ Informacia od ESET NOD32 Antivirus, verzia databazy 6017 >> (20110405) __________ >> >> Tuto spravu preveril ESET NOD32 Antivirus. >> >> http://www.eset.sk >> > > > __________ Informacia od ESET NOD32 Antivirus, verzia databazy 6017 (20110405) __________ > > Tuto spravu preveril ESET NOD32 Antivirus. > > http://www.eset.sk > > > > _______________________________________________ > 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 > -- Carsten Bock http://www.ng-voice.com mailto:carsten@ng-voice.com Schomburgstr. 80 22767 Hamburg Germany Mobile +49 179 2021244 Office +49 40 34927219 Fax +49 40 34927220

2 1

Re: [SR-Users] Kamailio ims / rtpproxy
by Carsten Bock 06 Apr '11

06 Apr '11

Hi, there is no documentation on the RTPProxy interface of the Kamailio IMS module yet. You need to have the following linse in the Kamailio.cfg: # Enabled Features on this host: #!define WITH_NAT [...] #!ifdef WITH_NAT #!define RTPPROXY "udp:127.0.0.1:22222" #!endif [...] #!ifndef WITH_NAT [...] #!else modparam("pcscf","NAT_enable", 1) modparam("pcscf","ping", 1) modparam("pcscf","ping_all", 0) modparam("pcscf","nat_detection_type", 0x17) modparam("pcscf","rtpproxy_socket", RTPPROXY) modparam("pcscf","rtpproxy_enable", 1) modparam("pcscf","rtpproxy_disable_tout", 60) modparam("pcscf","rtpproxy_retr", 5) modparam("pcscf","rtpproxy_tout", 1) #!endif Kind regards, Carsten 2011/4/5 Pavel Segeč <pavel.segec(a)fri.uniza.sk>: > Hi, > > > > I would like ask you if there is a kamailio ims module documentation > somewhere. I need some deeper information how some things are implemented, I > have problem to setup NAT traversal with RTPproxy for our Kamailio IMS > platform. There is no communication among the PCSCF and RTPproxy server over > control udp sock. We tried unix socket also with the same results. > > > > Thanks > > > > palo73 > > http://nil.uniza.sk > > __________ Informacia od ESET NOD32 Antivirus, verzia databazy 6016 > (20110405) __________ > > Tuto spravu preveril ESET NOD32 Antivirus. > > http://www.eset.sk > > _______________________________________________ > 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 > > -- Carsten Bock http://www.ng-voice.com mailto:carsten@ng-voice.com

2 1

[PATCH] modules_k/uac: fix from/to restore for small original URI
by Timo Teräs 06 Apr '11

06 Apr '11

Seems that the URI length check is superfluous and fails under certain conditions. It does not make sense for the URI to have zero bytes, so just use the first seen zero byte as end marker. I have a reproducible test case where the restore inserts URI with multiple zero-bytes to wire. This happens if the original URI is smaller than the one we rewrote it to using uac_replace_from. Signed-off-by: Timo Teräs <timo.teras(a)iki.fi> --- modules_k/uac/from.c | 14 ++++++++------ 1 files changed, 8 insertions(+), 6 deletions(-) However, I think the delta encoding used for the RR attribute is flawed. Hostile remote server could rewrite the RR attribute and/or From/To headers in a way to forge it to something it was not in the first place. Additionally the delta-encoded RR attribute breaks if the From/To header isn't exact copy of what we sent. Would it not make more sense to just send the real original header (possibly encrypted) but with a checksum? We could then verify if someone had clobbered the RR attribute and ignore it. And we could always restore the original URI even if the URI we are swapping was modified unexpectedly. diff --git a/modules_k/uac/from.c b/modules_k/uac/from.c index 4657e11..50822b6 100644 --- a/modules_k/uac/from.c +++ b/modules_k/uac/from.c @@ -463,15 +463,17 @@ int restore_from( struct sip_msg *msg, int *is_from ) LM_ERR("new URI shorter than old URI\n"); goto failed; } - for( i=0 ; i<old_uri.len ; i++ ) + for( i=0 ; i<old_uri.len ; i++ ) { new_uri.s[i] ^= old_uri.s[i]; - if (new_uri.len==old_uri.len) { - for( ; new_uri.len && (new_uri.s[new_uri.len-1]==0) ; new_uri.len-- ); - if (new_uri.len==0) { - LM_ERR("new URI got 0 len\n"); - goto failed; + if (new_uri.s[i] == 0) { + new_uri.len = i; + break; } } + if (new_uri.len==0) { + LM_ERR("new URI got 0 len\n"); + goto failed; + } LM_DBG("decoded uris are: new=[%.*s] old=[%.*s]\n", new_uri.len, new_uri.s, old_uri.len, old_uri.s); -- 1.7.1

2 1

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