<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
<META NAME="GENERATOR" CONTENT="GtkHTML/4.4.4">
</HEAD>
<BODY>
The purpose of RLS is to aggregate NOTIFYs. So RLS does not send NOTIFYs immediately. The presentities it receives are put in to the rls_presentity table.<BR>
<BR>
When not in DB only mode RLS runs a five second timer (configurable), and each five seconds it looks for updated rows in rls_presentity and sends out a batch of NOTIFYs (all at once). This is roughly as per the RFC, but not a great mechanism as for five whole seconds no update NOTIFYs are sent and then all are sent at once.<BR>
<BR>
When in DB only mode RLS runs one or more notifier processes that activate 10 times per second (configurable) and make sure that every front-end subscribe is serviced exactly once per five seconds (configurable). This spreads the NOTIFY message generation processing and network traffic out across time.<BR>
<BR>
In both cases (with default configuration) update NOTIFYs will take up to five seconds to come out of RLS.<BR>
<BR>
Regards,<BR>
<BR>
Peter<BR>
<BR>
On Tue, 2012-09-11 at 17:34 +0300, Juha Heinanen wrote:
<BLOCKQUOTE TYPE=CITE>
<PRE>
one rls thing that stilll wonders me is the about 2-5 sec delay that
occurs when backend notifies have been received and notify to subscriber
ua is sent:
Sep 11 17:27:41 siika /usr/sbin/sip-proxy[4495]: INFO: Routing PUBLISH <<A HREF="sip:foo@test.fi">sip:foo@test.fi</A>> to presence server
Sep 11 17:27:41 siika /usr/sbin/pres-serv[19270]: INFO: Handling PUBLISH <<A HREF="sip:foo@test.fi">sip:foo@test.fi</A>>
Sep 11 17:27:41 siika /usr/sbin/pres-serv[19270]: INFO: Routing locally generated NOTIFY <<A HREF="sip:rls@127.0.0.1:5082">sip:rls@127.0.0.1:5082</A>;transport=tcp> to <<A HREF="sip:jh@test.fi">sip:jh@test.fi</A>> from <<A HREF="sip:foo@test.fi">sip:foo@test.fi</A>>
Sep 11 17:27:41 siika /usr/sbin/pres-serv[19270]: INFO: presence [notify.c:1575]: NOTIFY <A HREF="sip:jh@test.fi">sip:jh@test.fi</A> via <A HREF="sip:rls@127.0.0.1:5082">sip:rls@127.0.0.1:5082</A>;transport=tcp on behalf of <A HREF="sip:foo@test.fi">sip:foo@test.fi</A> for event presence
Sep 11 17:27:41 siika /usr/sbin/pres-serv[19271]: INFO: Handling in-dialog NOTIFY <<A HREF="sip:rls@127.0.0.1:5082">sip:rls@127.0.0.1:5082</A>;transport=tcp> from <<A HREF="sip:foo@test.fi">sip:foo@test.fi</A>> to <<A HREF="sip:jh@test.fi">sip:jh@test.fi</A>>
Sep 11 17:27:46 siika /usr/sbin/pres-serv[19265]: INFO: Routing locally generated NOTIFY <<A HREF="sip:cyvrphbz@192.98.103.1:60122">sip:cyvrphbz@192.98.103.1:60122</A>;alias=192.98.103.1~47419~2;transport=tcp> to <<A HREF="sip:jh@test.fi">sip:jh@test.fi</A>> from <<A HREF="sip:jh-buddies@test.fi">sip:jh-buddies@test.fi</A>>
Sep 11 17:27:46 siika /usr/sbin/sip-proxy[4482]: INFO: Routing in-dialog NOTIFY <<A HREF="sip:cyvrphbz@192.98.103.1:60122">sip:cyvrphbz@192.98.103.1:60122</A>;transport=tcp> from <<A HREF="sip:jh-buddies@test.fi">sip:jh-buddies@test.fi</A>> to <<A HREF="sip:192.98.103.1:47419">sip:192.98.103.1:47419</A>;transport=tcp>
this does not depend on the pua patch nor which db_mode i have in rls
module.
-- juha
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
<A HREF="mailto:sr-users@lists.sip-router.org">sr-users@lists.sip-router.org</A>
<A HREF="http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users">http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users</A>
</PRE>
</BLOCKQUOTE>
<BR>
<TABLE CELLSPACING="0" CELLPADDING="0" WIDTH="100%">
<TR>
<TD>
<PRE>
--
Peter Dunkley
Technical Director
Crocodile RCS Ltd
</PRE>
</TD>
</TR>
</TABLE>
</BODY>
</HTML>