<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">Hi,<br>
<br>
I don't know what might cause exactly the issues you are seeing,
but here's what I would do to track it down.<br>
<br>
1. If no xcap documents exist on the system, the client will get a
404 and should usually PUT some new (empty) documents.<br>
<br>
Assuming these 'empty' documents exist, the following should
happen when the client logs in.<br>
a. When the SUBSCRIBE to presence.winfo arrives it should create a
single entry in the 'active-watchers' table. It should show a
single subscription to presence.winfo where the watcher and
presentity URI are the same user.<br>
c. When the SUBSCRIBE to RLS arrives, it should create a single
entry in 'rls_watchers'. As there are no contacts in the
resource-list doc, there are no rls subscriptions.<br>
<br>
My questions to try and debug would be:<br>
1. Does the above happen when starting from a clean database and
not having any contacts or external links in the resource-list?<br>
<br>
2. If that works, can you add contacts directly to the
resource-list (like below) and try again. Does that cause a
problem? You should see entries in 'pua' and 'active-watchers' for
the added contacts.<br>
<blockquote><tt><?xml version="1.0" encoding="UTF-8"?></tt><br>
<tt><resource-lists
xmlns="urn:ietf:params:xml:ns:resource-lists"</tt>><br>
<tt> <list name="oma_buddylist"></tt><br>
<tt> <entry uri=<a class="moz-txt-link-rfc2396E" href="sip:160000@example.com">"sip:160000@example.com"</a>></tt><br>
<tt> <display-name>160000</display-name></tt><br>
<tt> </entry</tt><tt>></tt><br>
<tt> <entry uri=<a class="moz-txt-link-rfc2396E" href="sip:160001@example.com">"sip:160001@example.com"</a>></tt><br>
<tt> <display-name>160001</display-name></tt><br>
<tt> </entry</tt><tt>></tt><br>
<tt> </list></tt><br>
<tt></resource-lists></tt><br>
</blockquote>
3. Finally add the external documents and external anchors and try
again.<br>
<br>
I haven't personally used anything that uses the external anchors
feature, but if it is only the external URIs that are causing the
problem, kamailio may think it is subscribing to the same URI each
time causing a recursive loop. This may be visible on a network
trace taken on the loopback interface.<br>
<br>
Regards,<br>
Hugh<br>
<br>
<br>
On 26/10/2012 13:36, Sangeeta Shah wrote:<br>
</div>
<blockquote
cite="mid:CAKPk9+3dgmahzzewwa3KDPJJMfG9SXoN-aNFtXyDOFHBO1RuPw@mail.gmail.com"
type="cite">
<pre wrap="">Did anyone get a chance to look at this post. I upgraded to Kamailio
3.3.2 since the changelog indicated several RLS fixes. But as soon as
I bring my client up I see 4000 entries in my PUA table and about 500+
entries in the rls_watchers table for the same presentity.
What would trigger behavior like this? Either I have an error or am
missing something in the config file or it's my XML. Any thoughts. I
have included my config params in this email chain and my
rls-services, pres-rules and resource-lists documents are from the OMA
specs with external anchors etc.
Thanks,
Sangeeta
On Mon, Oct 22, 2012 at 3:32 PM, Sangeeta Shah <a class="moz-txt-link-rfc2396E" href="mailto:sangeeta.shah@gmail.com"><sangeeta.shah@gmail.com></a> wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Hello All,
I am hoping the authors of the RLS/PUA modules can answer this
question since I am not sure what's going on. I have the rls module
enabled, with the following config spec:
# ------rls module params ------
modparam("rls", "db_url", DBURL)
modparam("rls", "db_mode", 2)
modparam("rls", "integrated_xcap_server", 1)
modparam("rls", "to_presence_code" ,10)
modparam("rls", "server_address", <a class="moz-txt-link-rfc2396E" href="sip:rls@ip:5060">"sip:rls@ip:5060"</a>)
#!endif
and
modparam("pua_reginfo", "default_domain", "ip")
modparam("pua_reginfo", "server_address", <a class="moz-txt-link-rfc2396E" href="sip:reginfo@ip">"sip:reginfo@ip"</a>)
modparam("pua", "db_mode", 2)
So for both I have DB_MODE set to DB ONLY. For whatever reason, even
though all I am doing is bringing up my client I see over 250+ entries
in the rls_watchers table for the same watcher and over 100 entries in
the pua list table for the same presentity?
Anyone have any idea what would be triggering this. There is
definitely not anymore more than the normal messaging going on between
the client and the server.
Only error I see in the syslog:
Oct 22 15:22:22 RCS-Presence /usr/local/sbin/kamailio[11745]: ERROR:
db_mysql [km_dbase.c:122]: driver error on query: Duplicate entry
'1350937406' for key 'expires_idx'
Oct 22 15:22:22 RCS-Presence /usr/local/sbin/kamailio[11744]: DEBUG:
presence [subscribe.c:1216]: subs->contact= <a class="moz-txt-link-freetext" href="sip:rls@ip:5060">sip:rls@ip:5060</a> - len = 25
Oct 22 15:22:22 RCS-Presence /usr/local/sbin/kamailio[11761]: DEBUG:
<core> [db_val.c:117]: converting STRING [8475551001]
Oct 22 15:22:22 RCS-Presence /usr/local/sbin/kamailio[11746]: DEBUG:
<core> [parser/msg_parser.c:626]: method: <SUBSCRIBE>
Oct 22 15:22:22 RCS-Presence /usr/local/sbin/kamailio[11745]: ERROR:
<core> [db_query.c:210]: error while submitting query
Oct 22 15:22:22 RCS-Presence /usr/local/sbin/kamailio[11744]: DEBUG:
rls [rls.h:241]: did=
<a class="moz-txt-link-abbreviated" href="mailto:41826031568472f9-11752@127.0.0.1;533cb9e91f4b999cf76861cbb9ed54ed-93a3;a6a1c5f60faecf035a1ae5b6e96e979a-464d">41826031568472f9-11752@127.0.0.1;533cb9e91f4b999cf76861cbb9ed54ed-93a3;a6a1c5f60faecf035a1ae5b6e96e979a-464d</a>
Oct 22 15:22:22 RCS-Presence /usr/local/sbin/kamailio[11761]: DEBUG:
<core> [db_val.c:117]: converting STRING [10.50.251.12]
Oct 22 15:22:22 RCS-Presence /usr/local/sbin/kamailio[11746]: DEBUG:
<core> [parser/msg_parser.c:628]: uri: <a class="moz-txt-link-rfc2396E" href="sip:8475551001@ip"><sip:8475551001@ip></a>
Oct 22 15:22:22 RCS-Presence /usr/local/sbin/kamailio[11745]: ERROR:
pua [pua_db.c:1149]: DB insert failed
--
Sangeeta Shah
</pre>
</blockquote>
<pre wrap="">
</pre>
</blockquote>
<br>
<br>
<pre class="moz-signature" cols="72">--
Hugh Waite
Principal Design Engineer
Crocodile RCS Ltd.</pre>
</body>
</html>