sr-users April 2012

sr-users@lists.kamailio.org

75 participants
132 discussions

Freezing development today for release 3.3.0
by Daniel-Constantin Mierla 23 Apr '12

23 Apr '12

Hello, quick reminder for everyone that by end of today is planned the freezing for the development of the new features to be in version 3.3.0. I know there are going to be few hammerings to newly added features, when discovering issues, that's the testing phase for. But try to get at least the database structure settled by today, as most of the users need to adapt management interfaces to start using the new version. Cheers, Daniel

1 0

replace body content
by Konstantin M. 22 Apr '12

22 Apr '12

Hi, Is there a way to change/replace anything in body message ? Used: replace_body_atonce, replace_body_all, replace_all, subst_body. Nothing is working. Thanks,

1 0

Core Dump from select stmt
by Akan Technology 22 Apr '12

22 Apr '12

hello, I am running kamailio 3.2.2 on Solaris 10 64 bit and I am getting a core dump on this statement: $ru = "sip:" + $rU + "@" + $sel(cfg_get.registrar1.server_ip) + $sel(cfg_get.registrar1.server_port); Here is how the variable is defined: registrar1.server_ip = "xxx.xxx.xxx.xxx" desc "Registrar server IP address" registrar1.server_port = "5080" desc "Registrar server Port" Here is the output from the logs with debug: 10(25373) ERROR: *** cfgtrace: c=[/opt/kamailio-3.2/etc/kamailio/kamailio.cfg] l=1072 a=65 n=assign 10(25373) DEBUG: <core> [select.c:424]: Calling SELECT 1004b2bc0 10(25373) DEBUG: <core> [select.c:424]: Calling SELECT 1004b4da0 10(25373) ERROR: *** cfgtrace:14(25377) : <core> [pass_fd.c:293]: ERROR: receive_fd: EOF on 22 14(25377) DEBUG: <core> [tcp_main.c:3555]: DBG: handle_ser_child: dead child 10, pid 25373 (shutting down?) 14(25377) DEBUG: <core> [io_wait.h:617]: DBG: io_watch_del (1003738b8, 22, 0, 0x0) fd_no=18 called 14(25377) DEBUG: <core> [tcp_main.c:3316]: DBG: handle_tcp_child: dead tcp child 0 (pid 25373, no 10) (shutting down?) 14(25377) DEBUG: <core> [io_wait.h:617]: DBG: io_watch_del (1003738b8, 24, 1, 0x0) fd_no=17 called 0(25363) ALERT: <core> [main.c:751]: child process 25373 exited by a signal 11 0(25363) ALERT: <core> [main.c:754]: core was generated 0(25363) INFO: <core> [main.c:766]: INFO: terminating due to SIGCHLD 14(25377) INFO: <core> [main.c:817]: INFO: signal 15 received Here is the full route code: route[TO_REGISTRAR] { # check if Registrar server's IP is defined if (strempty($sel(cfg_get.registrar1.server_ip))) { xlog("SCRIPT: REGISTRAR - registrar1.server_ip not defined\n"); return; } $ru = "sip:" + $rU + "@" + $sel(cfg_get.registrar1.server_ip) + ":" + $sel(cfg_get.registrar1.server_port); route(RELAY); exit; } # End of TO_Registrar Route I am trying to setup the proxy server to route all registers requests to another kamailio server Thanks Nathaniel

4 10

reminder - freezing development for next major release v3.3.0
by Daniel-Constantin Mierla 20 Apr '12

20 Apr '12

Hello, a short reminder about freezing the development for next major release v3.3.0. It is planned for April 23, less than two weeks away. If you have new features to add for v3.3.0, commit them or send the patches before the date. Cheers, Daniel -- Daniel-Constantin Mierla Kamailio Advanced Training, April 23-26, 2012, Berlin, Germany http://www.asipto.com/index.php/kamailio-advanced-training/

3 4

htable feature request
by Andreas Granig 20 Apr '12

20 Apr '12

Hi, I'd like to ask for a feature request for htable. Would it be possible to add an MI function to delete specific entries from an htable, e.g. with "sercmd htable.remove <table> <key>" before freezing 3.3? That'd be handy for example if you hold blocked IPs in htable, but want to unblock some of them manually. At the moment, I only see the method of restarting kamailio to whipe the whole table (and it'd only work if dbmode=0). Thanks in advance, Andreas

2 2

Help about VoIP
by Zuzu 20 Apr '12

20 Apr '12

I got my sip account ipadvoip(a)iptel.org what is next step VoIP to complete plz reply thank you my email yahya_satofa(a)yahoo.com

1 0

SIP Attack
by Ricardo Martinez 20 Apr '12

20 Apr '12

Hello. I was wondering if someone could help me here. From time to time I stat to receive from the internet this SIP message : U 190.22.140.170:51316 -> 64.76.154.110:5060 SIP/2.0 400 BadRequest. Via: . From: . To: . Call-ID: . CSeq: . User-Agent: AddPac SIP Gateway. Content-Length: 0. . At burst rate of 124 pps (packets per second), this meesage is entering to Kamailio routine and generating a lot of ERROR logs lie these : Apr 1 03:32:19 kmborde /usr/local/sbin/kamailio[2311]: ERROR: <core> [parser/msg_parser.c:179]: ERROR: get_hdr_field: bad to header Apr 1 03:32:19 kmborde /usr/local/sbin/kamailio[2311]: INFO: <core> [parser/msg_parser.c:353]: ERROR: bad header field [To: <sip:Re gister=>5] Apr 1 03:32:19 kmborde /usr/local/sbin/kamailio[2311]: ERROR: <core> [parser/msg_parser.c:179]: ERROR: get_hdr_field: bad to header Apr 1 03:32:19 kmborde /usr/local/sbin/kamailio[2311]: INFO: <core> [parser/msg_parser.c:353]: ERROR: bad header field [To: <sip:Re gister=>5] Apr 1 03:32:19 kmborde /usr/local/sbin/kamailio[2311]: ERROR: <core> [parser/msg_parser.c:179]: ERROR: get_hdr_field: bad to header Apr 1 03:32:19 kmborde /usr/local/sbin/kamailio[2311]: INFO: <core> [parser/msg_parser.c:353]: ERROR: bad header field [To: <sip:Re gister=>5] Apr 1 03:32:19 kmborde /usr/local/sbin/kamailio[2311]: ERROR: <core> [msg_translator.c:1943]: ERROR: build_res_buf_from_sip_req: al as, parse_headers failed Apr 1 03:32:19 kmborde /usr/local/sbin/kamailio[2311]: WARNING: sanity [sanity.c:254]: sanity_check(): check_required_headers(): fa iled to send 400 via sl reply Apr 1 03:32:20 kmborde /usr/local/sbin/kamailio[2301]: ERROR: <core> [parser/msg_parser.c:179]: ERROR: get_hdr_field: bad to header Apr 1 03:32:20 kmborde /usr/local/sbin/kamailio[2301]: INFO: <core> [parser/msg_parser.c:353]: ERROR: bad header field [To: <sip:Re gister=>5] Apr 1 03:32:20 kmborde /usr/local/sbin/kamailio[2301]: ERROR: <core> [parser/msg_parser.c:179]: ERROR: get_hdr_field: bad to header Apr 1 03:32:20 kmborde /usr/local/sbin/kamailio[2301]: INFO: <core> [parser/msg_parser.c:353]: ERROR: bad header field [To: <sip:Re gister=>5] Apr 1 03:32:20 kmborde /usr/local/sbin/kamailio[2301]: ERROR: <core> [parser/msg_parser.c:179]: ERROR: get_hdr_field: bad to header Apr 1 03:32:20 kmborde /usr/local/sbin/kamailio[2301]: INFO: <core> [parser/msg_parser.c:353]: ERROR: bad header field [To: <sip:Re gister=>5] Apr 1 03:32:20 kmborde /usr/local/sbin/kamailio[2301]: ERROR: <core> [msg_translator.c:1943]: ERROR: build_res_buf_from_sip_req: al as, parse_headers failed Apr 1 03:32:20 kmborde /usr/local/sbin/kamailio[2301]: WARNING: sanity [sanity.c:254]: sanity_check(): check_required_headers(): fa iled to send 400 via sl reply Apr 1 03:32:23 kmborde /usr/local/sbin/kamailio[2320]: ERROR: <core> [parser/msg_parser.c:179]: ERROR: get_hdr_field: bad to header Apr 1 03:32:23 kmborde /usr/local/sbin/kamailio[2320]: INFO: <core> [parser/msg_parser.c:353]: ERROR: bad header field [To: <sip:Re gister=>5] Apr 1 03:32:23 kmborde /usr/local/sbin/kamailio[2320]: ERROR: <core> [parser/msg_parser.c:179]: ERROR: get_hdr_field: bad to header Apr 1 03:32:23 kmborde /usr/local/sbin/kamailio[2320]: INFO: <core> [parser/msg_parser.c:353]: ERROR: bad header field [To: <sip:Re gister=>5] Apr 1 03:32:23 kmborde /usr/local/sbin/kamailio[2320]: ERROR: <core> [parser/msg_parser.c:179]: ERROR: get_hdr_field: bad to header Apr 1 03:32:23 kmborde /usr/local/sbin/kamailio[2320]: INFO: <core> [parser/msg_parser.c:353]: ERROR: bad header field [To: <sip:Re gister=>5] Apr 1 03:32:23 kmborde /usr/local/sbin/kamailio[2320]: ERROR: <core> [msg_translator.c:1943]: ERROR: build_res_buf_from_sip_req: al as, parse_headers failed Apr 1 03:32:23 kmborde /usr/local/sbin/kamailio[2320]: WARNING: sanity [sanity.c:254]: sanity_check(): check_required_headers(): fa iled to send 400 via sl reply The only way that I have now for blocking this packet to hit the Kamailio server is via iptables : iptables -A INPUT -s 190.22.140.170 -p udp --dport 5060 --jump REJECT Is there a better way to do this?! Thanks in advance, * * *Ricardo Martinez.-*

5 5

Re: [SR-Users] sr-users Digest, Vol 83, Issue 77
by Ali Wazni 20 Apr '12

20 Apr '12

Chefta men chway. Jaydeeeeee 7adret el consultant!!!!! Ali Wazni On 20 avr. 2012, at 08:41, sr-users-request(a)lists.sip-router.org wrote: > Send sr-users mailing list submissions to > sr-users(a)lists.sip-router.org > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users > or, via email, send a message with subject or body 'help' to > sr-users-request(a)lists.sip-router.org > > You can reach the person managing the list at > sr-users-owner(a)lists.sip-router.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of sr-users digest..." > > > Today's Topics: > > 1. Kamailio v3.2.3 Released (Daniel-Constantin Mierla) > 2. Re: [sr-dev] reminder - freezing development for next major > release v3.3.0 (Peter Dunkley) > 3. Stateless Proxy (Akan) > 4. How does RLS work with kamailio. (Gnaneshwar Gatla) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Thu, 19 Apr 2012 19:15:29 +0200 > From: Daniel-Constantin Mierla <miconda(a)gmail.com> > Subject: [SR-Users] Kamailio v3.2.3 Released > To: "SIP Router - Kamailio (OpenSER) and SIP Express Router (SER) - > Users Mailing List" <sr-users(a)lists.sip-router.org>, sr-dev > <sr-dev(a)lists.sip-router.org>, business(a)lists.kamailio.org > Message-ID: <4F904831.1030503(a)gmail.com> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > Hello, > > Kamailio SIP Server v3.2.3 stable release is out. > > This is a maintenance release of the latest stable branch, 3.2, that > includes fixes since release of v3.2.2. There is no change to database > schema or configuration language structure that you have to do on > installations of v3.2.0, v3.2.1 or v3.2.2. Deployments running previous > v3.2.x versions are strongly recommended to be upgraded to v3.2.3. > > For more details about version 3.2.3 (including links and hints to > download the tarball or from GIT repository), visit: > > * http://www.kamailio.org/w/2012/04/kamailio-v3-2-3-released/ > > RPMs and Debian/Ubuntu packages will be available soon. > > Cheers, > Daniel > > -- > Daniel-Constantin Mierla > Kamailio Advanced Training, April 23-26, 2012, Berlin, Germany > http://www.asipto.com/index.php/kamailio-advanced-training/ > > > > > ------------------------------ > > Message: 2 > Date: Thu, 19 Apr 2012 18:33:49 +0100 > From: Peter Dunkley <peter.dunkley(a)crocodile-rcs.com> > Subject: Re: [SR-Users] [sr-dev] reminder - freezing development for > next major release v3.3.0 > To: miconda(a)gmail.com, Development mailing list of the sip-router > project <sr-dev(a)lists.sip-router.org> > Cc: "SIP Router - Kamailio $OpenSER$ and SIP Express Router $SER$ > - Users Mailing List" <sr-users(a)lists.sip-router.org> > Message-ID: <1334856829.2795.29.camel@pd-laptop-linux> > Content-Type: text/plain; charset="utf-8" > > Hi, > > One of the developments I am currently working on is to add notifier > processes to presence. I have already done this for RLS. This is > needed not just for performance, but because there are race conditions > (I see them under load) where you get multiple NOTIFY requests > outstanding on the same dialog and, when in DB only mode, they often > have the same CSeq (despite being different requests). > > Unfortunately, I don't believe I will get this finished by the end of > Monday (April 23). I still expect to complete this development next > week. > > As the CSeq issue is quite clearly a problem I would like to get this > development into Kamailio 3.3. Will it be OK for me to put this > development into master next week after the freeze? > > Thanks, > > Peter > > On Wed, 2012-04-11 at 11:34 +0200, Daniel-Constantin Mierla wrote: > >> Hello, >> >> a short reminder about freezing the development for next major release >> v3.3.0. It is planned for April 23, less than two weeks away. If you >> have new features to add for v3.3.0, commit them or send the patches >> before the date. >> >> Cheers, >> Daniel >> > > > -- > Peter Dunkley > Technical Director > Crocodile RCS Ltd >

1 0

XCAP_Client version error
by Gnaneshwar Gatla 20 Apr '12

20 Apr '12

Hey, In Kamailio 3.2.2: I was working with XCAP and RLS today and found that the XCAP client has not been updated to the latest version of the xcap table. This resulted in error while starting Kamailio. Currently in modules_k/xcap_client/xcap_client.c : #define XCAP_TABLE_VERSION 3 I have set this macro to 4 and started the Kamailio instance. This is in regard to the followup email for rls service, does this have any impact to the rls module? Regards Gnani Gnaneshwar Gatla | InTouch Health | Software Developer 6330 Hollister Ave. Goleta CA, 93117 | P: 805.562.8686 ext: 199

2 1

Stateless Proxy
by Akan 20 Apr '12

20 Apr '12

Hello, I am trying to setup a stateless proxy where certain requests are forwarded to another sip server that will handle those requests specifically. I have the request message forwarding to the other sip server but the reply is being sent back to the original sip server then to the client. When I look at the SIP request and reply, I see a new "Via" header line with the IP address of the original sip proxy server. What I am trying to setup is a stateless proxy which just forwards the original request to another sip server and then this second sip server will handle everything from there. Basically offloading the traffic to other servers. Currently i am rewriting the ruri host and port as done in the sample config and issuing the forward() function. I have tried t_relay() as also in the sample config but I get the same results. Is there something else that I need to do before forwarding to the other sip server? How can I get rid of the new "Via" line? I believe this is from record_route() but I am not issue this before I perform the relay. I have Kamailio 3.2.3 loaded and used the sample config as my base config. Thanks Nathaniel

1 0

← Newer
1
2
3
4
5
6
7
8
9
...
14
Older →

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