sr-users December 2011

sr-users@lists.kamailio.org

64 participants
108 discussions

CANCEL not matching INVITES !
by Sammy Govind 03 Dec '11

03 Dec '11

Hello list, I'm using Kamailio 3.1.5 in front of asterisk servers. Kamailio handles all the SIP registrations. Calls from SIP phones are forwarded to asterisks and then dialled out to Kamailio. root@SBCserver:~# kamailio -V version: kamailio 3.1.5 (x86_64/linux) 76fff5 flags: STATS: Off, USE_IPV6, USE_TCP, USE_TLS, TLS_HOOKS, USE_RAW_SOCKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MEM, SHM_MMAP, PKG_MALLOC, DBG_QM_MALLOC, USE_FUTEX, FAST_LOCK-ADAPTIVE_WAIT, USE_DNS_CACHE, USE_DNS_FAILOVER, … [View More]

2 10

rate limit module
by Fabian Borot 02 Dec '11

02 Dec '11

Hello, I am trying to use the rate limit module using Kamailio 1.5.2. I feel that I got it but I would like some pointers and recommendations. These are my settings: (this is a lab of course), I used 1 on the timer_interval because I am generating the calls manually and wanted to see it in action quickly: # ---- ratelimit ------- modparam("ratelimit", "timer_interval", 1) modparam("ratelimit", "reply_code", 506) modparam("ratelimit", "reply_reason", "Rejecting due to high load") … [View More]modparam("ratelimit", "queue", "0:INVITE") modparam("ratelimit", "pipe", "0:TAILDROP:1") then in the route section: if (method=="INVITE") { xlog("L_INFO","mylog: RL found INVITE.\n"); if (!rl_check()) { xlog("L_INFO","mylog: RL dropped message.\n"); rl_drop(); exit; }; xlog("L_INFO","mylog: RL found INVITE but did not drop it.\n"); }; The TAILDROP algorithm seems to work better than the RED, based on what I expected of course (with 1 sec timer interval and 1 calls/sec on the pipe). Making manual calls one right after the other almost always triggered the protecting when there was another call on the same second. But these lines (1.6.3. pipe) on the doc got me kind of confused: " When specifying a limit, the unit depends on the algorithm used and doesn't need to be specified also (eg, for TAILDROP or RED, limit means packets/sec, whereas with the FEEDBACK algorithm, it means [CPU] load factor). For these 2 lines below, does this mean that the interval =10 will be overridden by the 100 calls/sec on the TAILDROP algorithm? modparam("ratelimit", "timer_interval", 10) modparam("ratelimit", "pipe", "0:TAILDROP:100") I made a quick test and with timer_interval = 10 and TAILDROP:1, it looks like the protection kicks in almost every 10 secs: (Dec 2 19:44:07 and Dec 2 19:43:57), tail -f proxy.log | grep RL Dec 2 19:43:53 AW-ATL-PROXY-01 ./kamailio[17450]: mylog: RL found INVITE. Dec 2 19:43:53 AW-ATL-PROXY-01 ./kamailio[17450]: mylog: RL found INVITE but did not drop it. Dec 2 19:43:53 AW-ATL-PROXY-01 ./kamailio[17449]: mylog: RL found INVITE. Dec 2 19:43:53 AW-ATL-PROXY-01 ./kamailio[17449]: mylog: RL found INVITE but did not drop it. Dec 2 19:43:53 AW-ATL-PROXY-01 ./kamailio[17450]: mylog: RL found INVITE. Dec 2 19:43:53 AW-ATL-PROXY-01 ./kamailio[17450]: mylog: RL found INVITE but did not drop it. Dec 2 19:43:53 AW-ATL-PROXY-01 ./kamailio[17450]: mylog: RL found INVITE. Dec 2 19:43:53 AW-ATL-PROXY-01 ./kamailio[17450]: mylog: RL found INVITE but did not drop it. Dec 2 19:43:54 AW-ATL-PROXY-01 ./kamailio[17450]: mylog: RL found INVITE. Dec 2 19:43:54 AW-ATL-PROXY-01 ./kamailio[17450]: mylog: RL found INVITE but did not drop it. Dec 2 19:43:55 AW-ATL-PROXY-01 ./kamailio[17449]: mylog: RL found INVITE. Dec 2 19:43:55 AW-ATL-PROXY-01 ./kamailio[17449]: mylog: RL found INVITE but did not drop it. Dec 2 19:43:56 AW-ATL-PROXY-01 ./kamailio[17449]: mylog: RL found INVITE. Dec 2 19:43:56 AW-ATL-PROXY-01 ./kamailio[17449]: mylog: RL found INVITE but did not drop it. Dec 2 19:43:56 AW-ATL-PROXY-01 ./kamailio[17450]: mylog: RL found INVITE. Dec 2 19:43:56 AW-ATL-PROXY-01 ./kamailio[17450]: mylog: RL found INVITE but did not drop it. Dec 2 19:43:56 AW-ATL-PROXY-01 ./kamailio[17449]: mylog: RL found INVITE. Dec 2 19:43:56 AW-ATL-PROXY-01 ./kamailio[17449]: mylog: RL found INVITE but did not drop it. Dec 2 19:43:57 AW-ATL-PROXY-01 ./kamailio[17450]: mylog: RL found INVITE. Dec 2 19:43:57 AW-ATL-PROXY-01 ./kamailio[17450]: mylog: RL found INVITE but did not drop it. Dec 2 19:43:57 AW-ATL-PROXY-01 ./kamailio[17449]: mylog: RL found INVITE. Dec 2 19:43:57 AW-ATL-PROXY-01 ./kamailio[17449]: mylog: RL dropped message. Dec 2 19:43:58 AW-ATL-PROXY-01 ./kamailio[17449]: mylog: RL found INVITE. Dec 2 19:43:58 AW-ATL-PROXY-01 ./kamailio[17449]: mylog: RL found INVITE but did not drop it. Dec 2 19:43:59 AW-ATL-PROXY-01 ./kamailio[17449]: mylog: RL found INVITE. Dec 2 19:43:59 AW-ATL-PROXY-01 ./kamailio[17449]: mylog: RL found INVITE but did not drop it. Dec 2 19:43:59 AW-ATL-PROXY-01 ./kamailio[17450]: mylog: RL found INVITE. Dec 2 19:43:59 AW-ATL-PROXY-01 ./kamailio[17450]: mylog: RL found INVITE but did not drop it. Dec 2 19:44:01 AW-ATL-PROXY-01 ./kamailio[17450]: mylog: RL found INVITE. Dec 2 19:44:01 AW-ATL-PROXY-01 ./kamailio[17450]: mylog: RL found INVITE but did not drop it. Dec 2 19:44:02 AW-ATL-PROXY-01 ./kamailio[17450]: mylog: RL found INVITE. Dec 2 19:44:02 AW-ATL-PROXY-01 ./kamailio[17450]: mylog: RL found INVITE but did not drop it. Dec 2 19:44:02 AW-ATL-PROXY-01 ./kamailio[17449]: mylog: RL found INVITE. Dec 2 19:44:02 AW-ATL-PROXY-01 ./kamailio[17449]: mylog: RL found INVITE but did not drop it. Dec 2 19:44:04 AW-ATL-PROXY-01 ./kamailio[17449]: mylog: RL found INVITE. Dec 2 19:44:04 AW-ATL-PROXY-01 ./kamailio[17449]: mylog: RL found INVITE but did not drop it. Dec 2 19:44:06 AW-ATL-PROXY-01 ./kamailio[17450]: mylog: RL found INVITE. Dec 2 19:44:06 AW-ATL-PROXY-01 ./kamailio[17450]: mylog: RL found INVITE but did not drop it. Dec 2 19:44:06 AW-ATL-PROXY-01 ./kamailio[17449]: mylog: RL found INVITE. Dec 2 19:44:06 AW-ATL-PROXY-01 ./kamailio[17449]: mylog: RL found INVITE but did not drop it. Dec 2 19:44:07 AW-ATL-PROXY-01 ./kamailio[17449]: mylog: RL found INVITE. Dec 2 19:44:07 AW-ATL-PROXY-01 ./kamailio[17449]: mylog: RL found INVITE but did not drop it. Dec 2 19:44:07 AW-ATL-PROXY-01 ./kamailio[17450]: mylog: RL found INVITE. Dec 2 19:44:07 AW-ATL-PROXY-01 ./kamailio[17450]: mylog: RL dropped message. Dec 2 19:44:10 AW-ATL-PROXY-01 ./kamailio[17450]: mylog: RL found INVITE. Dec 2 19:44:10 AW-ATL-PROXY-01 ./kamailio[17450]: mylog: RL found INVITE but did not drop it. [View Less]

2 3

RPMs for 3.2.1
by Daniel-Constantin Mierla 02 Dec '11

02 Dec '11

Hello, RPM packages of Kamailio 3.2.1 for Centos, Fedora, Redhat and openSUSE (32b and 64b) were built and are available for download -- links specific for each distro in the wiki page: http://www.kamailio.org/wiki/packages/rpms Cheers, Daniel -- Daniel-Constantin Mierla -- http://www.asipto.com Kamailio Advanced Training, Dec 5-8, Berlin: http://asipto.com/u/kat http://linkedin.com/in/miconda -- http://twitter.com/miconda

1 0

transport=TLS
by Bruno Bresciani 02 Dec '11

02 Dec '11

Hi All, kamailio 3.1.2 recognize value "transport=TLS" on contact header or only "transport=tls"? kamailio forwards (t_relay function) the message with UDP protocol when value "transport=TLS" is on contact header. Cheers

3 13

Monitoring inquiry
by Jenkins, Rachel 01 Dec '11

01 Dec '11

I have a couple questions as it relates to monitoring a Kamailio SIP Server. 1. Do you have an OID that we can poll via SNMP-GETs to show call completion statistics? Either the % of completion or the accepting/connecting statistics. If you do not have an OID, do you have a syslog or trap message that can be generated? 2. Do you have an OID that we can poll to get a list errors that were generated? Ex-OID for a 408 or 503. If not, is there a syslog or trap? 3. Can you … [View More]

4 3

Kamailio v3.2.1 Released
by Daniel-Constantin Mierla 01 Dec '11

01 Dec '11

Hello, Kamailio SIP Server v3.2.1 stable release is out. This is a maintenance release of latest stable branch, 3.2, that includes fixes since release of v3.2.0. There is no change to database schema or configuration language structure that you have to do on installations of v3.2.0. Deployments running previous v3.2.0 versions are strongly recommended to be upgraded to v3.2.1. For more details about version 3.2.1 (including links and hints to download the tarball or from GIT repository),… [View More]

1 0

preparing to release v3.2.1
by Daniel-Constantin Mierla 01 Dec '11

01 Dec '11

Hello, the plan is to start packaging of v3.2.1 after 14:00GMT. If anyone has anything elst to commit to branch 3.2 to be in v3.2.1, please do it before, afterwards write me an email first to synchronize and avoid git conflicts. Cheers, Daniel -- Daniel-Constantin Mierla -- http://www.asipto.com Kamailio Advanced Training, Dec 5-8, Berlin: http://asipto.com/u/kat http://linkedin.com/in/miconda -- http://twitter.com/miconda

1 1

how approach nathelper when using usrloc db_mode 3?
by Albert Petit 01 Dec '11

01 Dec '11

Hello, We found an issue when using nat pinger Previously our system had 1 Kamailio as entry point and we were using usrloc in mode 2 so: modparam("usrloc", "db_mode",2) modparam("usrloc", "db_url", "mysql://openser:openserrw@<DB_IP>/openser") On our system we like to use the pinger NAT_HELPER module to keep the connections alive for the users of our system. Now we're trying to configure two Kamailio K1 and K2 as entry point of the system and having both of them active at … [View More]

1 0

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