date:20120124

Re: [SR-Users] Homer SIP Capture Setup Question

2012-01-24 Thread Alexandr Dubovikov


Hi,

Sorry, it was my mistake in the sample.

in the FAQ we have fixed this issue :-)
http://code.google.com/p/homer/wiki/FAQ

*Q: I use HEP and see kamailio replying with 100 Trying, 200 OK. Why is 
that?*


A: The messages have been replied to by onreply_route; To disable 
replies, adjust your kamailio.cfg as follows:


onreply_route{
 sip_capture();
 drop;
}


Wbr,
Alexandr

1/17/2012 2:37 PM, JR Richardson wrote:

On 01/16/2012 09:11 PM, JR Richardson wrote:


So my question; what is the difference between a drop; and exit;
within the on_reply route

Remember that an onreply_route is a callback that allows you to
intercept a reply, but the reply is forwarded by default afterward (if
using stateful forwarding).  This is different from a request route,
where it's up to you to marshal everything, and to explicitly forward
the message.

Thus, exiting an onreply_route has null effect.  It doesn't do
anything to stop the reply from being forwarded, because forwarding is
the behaviour--the onreply_route is just a hook.  In contrast, 'drop'
explicitly drops the message and prevents further forwarding of the
reply from taking place.

This is different than in a request route, where exiting precludes any
forwarding action, because forwarding action must be taken explicitly
-- e.g. t_relay().

--
Alex Balashov - Principal

Aaaah, concise explanation, once again, thanks for turning on the light bulb
Alex.

JR


___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users


___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

[SR-Users] Memory usage problem in xmpp modules

2012-01-24 Thread laura testi

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 (first16)
qm_status: hash=   3. fragments no.: 6, unused: 0
 bucket size:24 -24 (first24)
qm_status: hash=   4. fragments no.: 1, unused: 0
 bucket size:32 -32 (first32)
qm_status: hash=   6. fragments no.: 3, unused: 0
 bucket size:48 -48 (first48)
qm_status: hash=   8. fragments no.: 8, unused: 0
 bucket size:64 -64 (first64)
qm_status: hash=   9. fragments no.: 6, unused: 0
 bucket size:72 -72 (first72)
qm_status: hash=  12. fragments no.: 5,

[SR-Users] Kamailio Crashing

2012-01-24 Thread Ali Jawad

Hi
I am running Kamailio and at times it just crashes, sometimes it happens
once a day sometimes a few times a day, in debug mode it shows the
following when it crashes

http://pastebin.com/ZcQRnXmM

GDB shows

http://pastebin.com/02wVK0eZ

GDB BT Shows

http://pastebin.com/3TBAuQAp

Please advice



-- 
*Ali Jawad
*
*Information Systems Manager*
*Splendor Telecom (www.splendor.net)
Beirut, Lebanon
Phone: +9611373725/ext 116
FAX: +9611375554*
___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] Homer SIP Capture Setup Question

[SR-Users] Memory usage problem in xmpp modules

[SR-Users] Kamailio Crashing

3 matches

Site Navigation

Mail list logo

Footer information