sr-users January 2012

sr-users@lists.kamailio.org

72 participants
114 discussions

rpid to from header.
by David 27 Jan '12

27 Jan '12

One of my upstream gateways does not support rpid, so I want to rewrite the from header from the rpid. is just a matter if setting $fU = $rpid? Thanks.

3 3

dbcassandra - 483
by David 27 Jan '12

27 Jan '12

Anca, for some strange reason I am getting "SIP/2.0 483 Too Many Hops" back when I try to register. I am running kamaikio -EEEEEE and I see we get authenticated correctly but then lots of other info is spit out very quickly and I am having a hard time trying to understand it. I think it may have to do with the location table. But I could be wrong. Any ideas how to debug? Thank you.

2 3

Radius Generates Core Dump
by Omar Labs 188 Gmail 27 Jan '12

27 Jan '12

Hello: I was testing the Server Kamailio 3.2.1 with Accounting and Radius, it crash generating a Big Core Dump, and freezing up, If I remove the Radius module from configuration, accounting via the database works fine. Did anybody else have the same problem. Appears a Memory leak. Thanks

2 1

Kamailio for Wholesale Termination
by Abid Naseem 27 Jan '12

27 Jan '12

Dear *All*, I am new to voip world and interested in knowing if I we can use *KAMAILIO + * *SIREMIS *for wholesale voip termination? We buy direct routes and give it to resellers..currently using asterisk. appreciate your support! keep inspiring. -- Regards, *Abid Naseem* +44 (793) 741 5043 +1 (415) 562 6333

2 1

Kamailio with Private IP - ACK for 200 OK problem
by Krishna Kurapati 26 Jan '12

26 Jan '12

Hi, I am having trouble with setting Record Route when Kamailio is behind a Load balancer. The Load balancer acts as a static NAT where the public IP of the load balancer is mapped to private IP of the Kamailio. This is creating issues with ACK for 200 OK since Kamailio is stuffing the 200 OK with private-ip in the Record-Route. The UAC looks like trying to send ACK back to this private IP which is not reachable. Is there a configuration option to let kamailio use Public IP when setting record-route in 200 OK? Thanks for any help... Krish Kura

2 1

Memory usage problem in xmpp modules
by laura testi 26 Jan '12

26 Jan '12

Hi, we are using the XMPP gateway modules: • PUA • PUA_XMPP • XMPP The behavior is ok but since the modules are started, the memory usage is getting increased and now also the swap memory area is used. I send to you the following information: 1. Numer of records from PUA and xmpp_presentity tables, they are quite stable: SQL> select count(*) from pua; COUNT(*) ---------- 10218 SQL> select count(*) from xmpp_presentity; COUNT(*) ---------- 754 2. list of PKG fragments with gdb : $1 = {size = 40, u = {nxt_free = 0x0, is_free = 0}, file = 0x2b657aa12c00 "presence: utils_func.h", func = 0x2b657aa1aed0 "uandd_to_uri", line = 66, check = 4042322160} $2 = {size = 32, u = {nxt_free = 0x0, is_free = 0}, file = 0x2b657aa12c00 "presence: utils_func.h", func = 0x2b657aa1aed0 "uandd_to_uri", line = 66, check = 4042322160} $3 = {size = 40, u = {nxt_free = 0x0, is_free = 0}, file = 0x2b657aa12c00 "presence: utils_func.h", func = 0x2b657aa1aed0 "uandd_to_uri", line = 66, check = 4042322160} $4 = {size = 40, u = {nxt_free = 0x0, is_free = 0}, file = 0x2b657aa12c00 "presence: utils_func.h", func = 0x2b657aa1aed0 "uandd_to_uri", line = 66, check = 4042322160} $5 = {size = 40, u = {nxt_free = 0x0, is_free = 0}, file = 0x2b657aa12c00 "presence: utils_func.h", func = 0x2b657aa1aed0 "uandd_to_uri", line = 66, check = 4042322160} $6 = {size = 104, u = {nxt_free = 0x0, is_free = 0}, file = 0x2b657aa12c00 "presence: utils_func.h", func = 0x2b657aa1aed0 "uandd_to_uri", line = 66, check = 4042322160} $7 = {size = 32, u = {nxt_free = 0x0, is_free = 0}, file = 0x2b657aa12c00 "presence: utils_func.h", func = 0x2b657aa1aed0 "uandd_to_uri", line = 66, check = 4042322160} $8 = {size = 32, u = {nxt_free = 0x0, is_free = 0}, file = 0x2b657aa12c00 "presence: utils_func.h", func = 0x2b657aa1aed0 "uandd_to_uri", line = 66, check = 4042322160} $9 = {size = 56, u = {nxt_free = 0x0, is_free = 0}, file = 0x2b657aa12c00 "presence: utils_func.h", func = 0x2b657aa1aed0 "uandd_to_uri", line = 66, check = 4042322160} $10 = {size = 96, u = {nxt_free = 0x0, is_free = 0}, file = 0x2b657aa12c00 "presence: utils_func.h", func = 0x2b657aa1aed0 "uandd_to_uri", line = 66, check = 4042322160} $11 = {size = 56, u = {nxt_free = 0x0, is_free = 0}, file = 0x2b657aa12c00 "presence: utils_func.h", func = 0x2b657aa1aed0 "uandd_to_uri", line = 66, check = 4042322160} $12 = {size = 112, u = {nxt_free = 0x0, is_free = 0}, file = 0x2b657aa12c00 "presence: utils_func.h", func = 0x2b657aa1aed0 "uandd_to_uri", line = 66, check = 4042322160} $13 = {size = 24, u = {nxt_free = 0x0, is_free = 0}, file = 0x2b657aa12c00 "presence: utils_func.h", func = 0x2b657aa1aed0 "uandd_to_uri", line = 66, check = 4042322160} $14 = {size = 24, u = {nxt_free = 0x0, is_free = 0}, file = 0x2b657aa12c00 "presence: utils_func.h", func = 0x2b657aa1aed0 "uandd_to_uri", line = 66, check = 4042322160} $15 = {size = 40, u = {nxt_free = 0x0, is_free = 0}, file = 0x2b657aa12c00 "presence: utils_func.h", func = 0x2b657aa1aed0 "uandd_to_uri", line = 66, check = 4042322160} $16 = {size = 40, u = {nxt_free = 0x0, is_free = 0}, file = 0x2b657aa12c00 "presence: utils_func.h", func = 0x2b657aa1aed0 "uandd_to_uri", line = 66, check = 4042322160} $17 = {size = 40, u = {nxt_free = 0x0, is_free = 0}, file = 0x2b657aa12c00 "presence: utils_func.h", func = 0x2b657aa1aed0 "uandd_to_uri", line = 66, check = 4042322160}…………. 3. Output of sercmd cfg.set_now_int core mem_dump_pkg : ……………….. 10969. N address=0xb1b320 frag=0xb1b2f0 size=104 used=1 qm_status: alloc'd from presence: utils_func.h: uandd_to_uri(66) qm_status: start check=f0f0f0f0, end check= c0c0c0c0, abcdefed qm_status: 10970. N address=0xb1b3e8 frag=0xb1b3b8 size=32 used=1 qm_status: alloc'd from presence: utils_func.h: uandd_to_uri(66) qm_status: start check=f0f0f0f0, end check= c0c0c0c0, abcdefed qm_status: 10971. N address=0xb1b468 frag=0xb1b438 size=32 used=1 qm_status: alloc'd from presence: utils_func.h: uandd_to_uri(66) qm_status: start check=f0f0f0f0, end check= c0c0c0c0, abcdefed qm_status: dumping free list stats : qm_status: hash= 1. fragments no.: 4, unused: 0 bucket size: 8 - 8 (first 8) qm_status: hash= 2. fragments no.: 8, unused: 0 bucket size: 16 - 16 (first 16) qm_status: hash= 3. fragments no.: 6, unused: 0 bucket size: 24 - 24 (first 24) qm_status: hash= 4. fragments no.: 1, unused: 0 bucket size: 32 - 32 (first 32) qm_status: hash= 6. fragments no.: 3, unused: 0 bucket size: 48 - 48 (first 48) qm_status: hash= 8. fragments no.: 8, unused: 0 bucket size: 64 - 64 (first 64) qm_status: hash= 9. fragments no.: 6, unused: 0 bucket size: 72 - 72 (first 72) qm_status: hash= 12. fragments no.: 5, unused: 0 bucket size: 96 - 96 (first 96) qm_status: hash= 14. fragments no.: 6, unused: 0 bucket size: 112 - 112 (first 112) qm_status: hash= 17. fragments no.: 32, unused: 0 bucket size: 136 - 136 (first 136) qm_status: hash= 19. fragments no.: 1, unused: 0 bucket size: 152 - 152 (first 152) qm_status: hash= 21. fragments no.: 1, unused: 0 bucket size: 168 - 168 (first 168) qm_status: hash= 29. fragments no.: 1, unused: 0 bucket size: 232 - 232 (first 232) qm_status: hash= 31. fragments no.: 2, unused: 0 bucket size: 248 - 248 (first 248) qm_status: hash= 33. fragments no.: 2, unused: 0 bucket size: 264 - 264 (first 264) qm_status: hash= 36. fragments no.: 1, unused: 0 bucket size: 288 - 288 (first 288) qm_status: hash= 57. fragments no.: 1, unused: 0 bucket size: 456 - 456 (first 456) qm_status: hash= 60. fragments no.: 1, unused: 0 bucket size: 480 - 480 (first 480) qm_status: hash= 76. fragments no.: 709, unused: 0 bucket size: 608 - 608 (first 608) qm_status: hash= 88. fragments no.: 1, unused: 0 bucket size: 704 - 704 (first 704) qm_status: hash= 116. fragments no.: 1, unused: 0 bucket size: 928 - 928 (first 928) qm_status: hash= 145. fragments no.: 1, unused: 0 bucket size: 1160 - 1160 (first 1160) qm_status: hash= 216. fragments no.: 2, unused: 0 bucket size: 1728 - 1728 (first 1728) qm_status: hash= 2049. fragments no.: 1, unused: 0 bucket size: 16384 - 32768 (first 22032) qm_status: hash= 2057. fragments no.: 1, unused: 0 bucket size: 4194304 - 8388608 (first 5982824) Is it a memory leak in one of these modules? Thanks in advance and kind regards, laura

5 6

get the kamailio up time and other params from the cfg file.
by Uri Shacked 26 Jan '12

26 Jan '12

Hi, is there a way to get the total up time of kamailio from the cfg file? like $stat(used_size) gives me the stat of the shared memory used size..... and if i am in it... is there a way to get the dispatcher status as well? i am trying to find a way to export these params with out the need to pull them using kamctl..... any ideas? thanks, Uri

4 3

Re: [SR-Users] detect the direction of the BYE
by Uri Shacked 26 Jan '12

26 Jan '12

On Thu, Jan 26, 2012 at 9:24 AM, Uri Shacked <uri.shacked(a)gmail.com> wrote: > Hi, > > i would like to detct the direction of the BYE. was it drom the caller or > the callee? > in the ACC module i can do that if i analyze the to and from tags... > how do i do it (in a nice way) in the cfg file? > > cheers. >

2 1

Call Control Behavior
by Reda Aouad 26 Jan '12

26 Jan '12

Hi, My question concerns Call Control. When a SIP call's timer ends, Call Control uses dlg_end_dlg MI command of the dialog module to send a BYE to the UA. Can I intercept the BYE message, drop it, change it and send instead an INVITE or a REDIRECT using (maybe) the UAC module? The INVITE/REDIRECT would connect the UA to a media gateway to announce a message when the session ends. Any ideas? This also leads to thoughts on accounting and rating. In the case of sending and INVITE, the rating of the call becomes inaccurate since there's no BYE when the call ends, but only after the media gateway's announcement ends. In the case of a REDIRECT, the UA sends a BYE to the established call before the INVITE to the media gateway, and thus rating remains totally accurate. What do you think? Thanks RA

1 0

Kamailio Redundancy examples/pointers required
by Sammy Govind 26 Jan '12

26 Jan '12

Hello list, I've been looking for ways to create a redundant Kamailio cluster. I've googled alot but haven't got any concrete or final wording on any one solution that'll just work perfectly. The basic requirement is that in case of Kamailio application failure or in case of physical machine error the whole setup just starts working on secondary server. Please suggest anything whichever you guys are using. Any reference URLs would be very much appreciated. Thanks and Regards, Sammy

2 2

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

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