<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
Hi Jeon,<br>
<br>
You are almost there :) but missing one piece of information that I
will provide to you now.<br>
<br>
Yoo Chan Jeon wrote:
<blockquote
cite="mid:8db572240810280906v43a9a7c1ve14d4d4854868296@mail.gmail.com"
type="cite">
<div><br>
Thanks Anca.</div>
<div>I checked the Wireshark trace, and your presentation.</div>
<div>Openser RLS seems to send a notify to the user before it
receives notify msgs from the presence server.</div>
<div>The Wireshark trace steps are following:</div>
<div>I explained the trace using your presentation: </div>
<div> </div>
<div>1.Eyebeam subscibes to my list</div>
<div>2. Openser RLS subscribes to Presence server.</div>
<div>3. Openser RLS sends a 200 to the Eyebeam.</div>
<div>4. Openser RLS sends a full notify to the Eyebeam without
presence states.</div>
</blockquote>
When receiving a Subscribe, RLS , as any notifier is obliged to send an
immediate Notify. So RLS check what state information it has , and
since it has none at that time - it sends a Notify with empty body.<br>
On the other hand, does this Notify receive a 200 OK from Eyebeam?<br>
<br>
<blockquote
cite="mid:8db572240810280906v43a9a7c1ve14d4d4854868296@mail.gmail.com"
type="cite">
<div>5. Presence server sends notify msgs to the Openser RLS.</div>
</blockquote>
Now, when receiving a Notify from the presence server, the RLS should
send a Notify to Eyebeam with the update of the state. Do you see that?<br>
<br>
I want to mention that there were some problems discovered in RLS at
SIPIT, two weeks ago and I am working now at fixing those. They could
also appear in your tests. Anyhow any trouble that you find, please
report and I will check to see if it is a new or know one. <br>
<br>
Do you use the latest version of Eyebeam? Does it have RLS support
again?<br>
<br>
regards,<br>
Anca Vamanu<br>
<blockquote
cite="mid:8db572240810280906v43a9a7c1ve14d4d4854868296@mail.gmail.com"
type="cite">
<div> </div>
<div>I guess that step 4 should be called after step 5.</div>
<div> </div>
<div>I checked the codes again.</div>
<div>The <font style="background-color: rgb(255, 255, 51);">rls_handle_subscribe()</font>
calls <font style="background-color: rgb(255, 255, 102);">resource_subscription(),</font>
<font style="background-color: rgb(255, 255, 102);">reply_200(),</font>
and <font style="background-color: rgb(255, 255, 102);">send_full_notify().</font></div>
<div>The resource_suscription() does the step 2.</div>
<div>The reply_200() does the step 3.</div>
<div>The send_full_notify() dose the step 4.</div>
<div> </div>
<div>The<font style="background-color: rgb(255, 255, 102);">
rls_handle_subscribe() never wait for step 5</font>.</div>
<div>What did I do wrong ? </div>
<div> </div>
<div>Thanks</div>
<div>Jeon</div>
<div><br>
</div>
<div class="gmail_quote">On Tue, Oct 28, 2008 at 9:14 AM, Anca Vamanu
<span dir="ltr"><<a moz-do-not-send="true"
href="mailto:anca@voice-system.ro">anca@voice-system.ro</a>></span>
wrote:<br>
<blockquote class="gmail_quote"
style="border-left: 1px solid rgb(204, 204, 204); margin: 0px 0px 0px 0.8ex; padding-left: 1ex;">You
can also find the slide presentation here: <a moz-do-not-send="true"
href="http://opensips.org/index.php?n=Resources.DocsPapPa"
target="_blank">http://opensips.org/index.php?n=Resources.DocsPapPa</a>.<br>
<br>
Anca<br>
<font color="#888888"><br>
Anca Vamanu wrote:<br>
</font>
<blockquote class="gmail_quote"
style="border-left: 1px solid rgb(204, 204, 204); margin: 0px 0px 0px 0.8ex; padding-left: 1ex;">
<div>
<div class="Wj3C7c">Hi Jeon,<br>
<br>
You are missing something.<br>
Here is a link at the slides from the presentation I held at VON, San
Jose this year - <a moz-do-not-send="true"
href="http://www.slideshare.net/alwaysoncarl/vamanu-anca/"
target="_blank">http://www.slideshare.net/alwaysoncarl/vamanu-anca/</a>
( we will put it on our site also).<br>
At page 24 there is a scheme with how RLS works.<br>
It interacts with the client by receiving a Subscribe to a list and
sending it an aggregate Notify.<br>
To get the info to put in the Notify it sends Notifies for each buddy
in list to the presence server ( where the clients have sent Publish
messages). The server will then reply with Notifies that will be
processed with rls_handle_notify function.<br>
<br>
regards,<br>
Anca<br>
<br>
<br>
Yoo Chan Jeon wrote:<br>
<br>
<blockquote class="gmail_quote"
style="border-left: 1px solid rgb(204, 204, 204); margin: 0px 0px 0px 0.8ex; padding-left: 1ex;">Hi,<br>
I looked at the codes.<br>
The send_full_notify() api in the rls/notif.c sends the notify msg.
That api is called in the rls_handle_subscribe().<br>
It is checking the rls_presentity table if the list has presence
states.<br>
The rls_presentity table is written in the rls_handle_notify() which
is called if the server receives a notify msg.<br>
The server recieves a subscribe(list) msg , sends a 200 msg, and a
notify msg.<br>
I do not think the notify msg will never have the presence states.<br>
Is this a bug in the codes or am I missing something?<br>
Thanks.<br>
Jeon<br>
<br>
<br>
On Mon, Oct 27, 2008 at 10:49 AM, Yoo Chan Jeon <<a
moz-do-not-send="true" href="mailto:yoojeon@gmail.com" target="_blank">yoojeon@gmail.com</a>
<mailto:<a moz-do-not-send="true" href="mailto:yoojeon@gmail.com"
target="_blank">yoojeon@gmail.com</a>>> wrote:<br>
<br>
Thanks Anca.<br>
I copied the xml file to the xcap.doc column. I put the<br>
username(list), doc_type(4), and domain(domain) I published the
joe, bob and tom's state. I sent a subscribe msg to the
list@domain <mailto:<a moz-do-not-send="true"
href="mailto:list@domain" target="_blank">list@domain</a>>.<br>
I received the notify msg with the following xml message body.<br>
I got a list of uri, but the xml body did not have a each uri's
state.<br>
I checekd the presentity database. it has the joe, bob, and<br>
tom presentity state.<br>
What am I missing?<br>
<?xml version="1.0" encoding="UTF-8"?><br>
<list uri=<a class="moz-txt-link-rfc2396E" href="sip:list@domain">"sip:list@domain"</a> xmlns="urn:ietf:params:xml:ns:rlmi"<br>
version="1" fullState="true"><br>
<resource uri="sip: joe@domain" <mailto:<a
moz-do-not-send="true" href="mailto:joe@domain" target="_blank">joe@domain</a>>>
<resource uri="sip: bob@domain"><br>
<resource uri="sip: tom@domain" <mailto:<a
moz-do-not-send="true" href="mailto:tom@domain" target="_blank">tom@domain</a>%22>>
</list><br>
<br>
Thanks.<br>
Jeon<br>
<br>
On Thu, Oct 23, 2008 at 7:08 AM, Anca Vamanu <<a
moz-do-not-send="true" href="mailto:anca@voice-system.ro"
target="_blank">anca@voice-system.ro</a><br>
<mailto:<a moz-do-not-send="true"
href="mailto:anca@voice-system.ro" target="_blank">anca@voice-system.ro</a>>>
wrote:<br>
<br>
Hi Jeon,<br>
<br>
The column was changed from type text to type blob because<br>
there was a problem with postgres db. However the text is not<br>
transformed into binary but written as text and extracted as
text.<br>
And yes, you should put the whole xml in the doc column.<br>
<br>
regards,<br>
Anca<br>
<br>
Yoo Chan Jeon wrote:<br>
<br>
Hi, Anca<br>
Thanks for your information.<br>
I was busy doing other issues in the presence server.<br>
Now I am back to this issue.<br>
I checked the xcap data structure, and source codes.<br>
The xcap doc column's type is a BLOB in the database. But<br>
I looked at the codes. It seems to save the doc as a<br>
string not a BLOB.<br>
I am still confused.<br>
How do I save the xml sample you wrote to the doc column?<br>
I mean the list.<br>
Should I put the whole xml to the doc column in the xcap<br>
table?<br>
Thanks.<br>
Jeon<br>
<br>
On Thu, Oct 2, 2008 at 9:38 AM, Anca Vamanu<br>
<<a moz-do-not-send="true"
href="mailto:anca@voice-system.ro" target="_blank">anca@voice-system.ro</a>
<mailto:<a moz-do-not-send="true" href="mailto:anca@voice-system.ro"
target="_blank">anca@voice-system.ro</a>><br>
<mailto:<a moz-do-not-send="true"
href="mailto:anca@voice-system.ro" target="_blank">anca@voice-system.ro</a><br>
<mailto:<a moz-do-not-send="true"
href="mailto:anca@voice-system.ro" target="_blank">anca@voice-system.ro</a>>>>
wrote:<br>
<br>
Hi Jeon,<br>
<br>
If you want to simulate an xcap server for rls you can<br>
do that by<br>
doing the following:<br>
1. set integrated_xcap_server parameter in rls module to
1.<br>
2. write the list in xcap table , putting value '4' in<br>
'doc_type'<br>
column.<br>
You should complete only columns: username, domain, doc
and<br>
doc_type, because these are the only ones used by the<br>
rls server.<br>
The list must have the format described in RFC 4826<br>
<<a moz-do-not-send="true"
href="http://www.ietf.org/rfc/rfc4826.txt" target="_blank">http://www.ietf.org/rfc/rfc4826.txt</a>>.
For the example<br>
that you<br>
gave it would look something like this:<br>
<br>
<?xml version="1.0" encoding="UTF-8"?><br>
<resource-lists<br>
xmlns="urn:ietf:params:xml:ns:resource-lists"><br>
<list name="SIMPLE Buddy List"><br>
<display-name>SIMPLE Buddy List</display-name><br>
<entry uri="sip: joe@domain <mailto:<a
moz-do-not-send="true" href="mailto:joe@domain" target="_blank">joe@domain</a><br>
<mailto:<a moz-do-not-send="true" href="mailto:joe@domain"
target="_blank">joe@domain</a>> <mailto:<a moz-do-not-send="true"
href="mailto:joe@domain" target="_blank">joe@domain</a><br>
<mailto:<a moz-do-not-send="true" href="mailto:joe@domain"
target="_blank">joe@domain</a>>>>"><br>
<br>
<display-name>joe</display-name><br>
</entry><br>
<entry uri="sip: bob@domain <mailto:<a
moz-do-not-send="true" href="mailto:joe@domain" target="_blank">joe@domain</a><br>
<mailto:<a moz-do-not-send="true" href="mailto:joe@domain"
target="_blank">joe@domain</a>> <mailto:<a moz-do-not-send="true"
href="mailto:joe@domain" target="_blank">joe@domain</a><br>
<mailto:<a moz-do-not-send="true" href="mailto:joe@domain"
target="_blank">joe@domain</a>>>>"><br>
<br>
<display-name>bob</display-name><br>
</entry><br>
<entry uri="<a class="moz-txt-link-freetext" href="sip:tom@domain">sip:tom@domain</a> <mailto:<a
moz-do-not-send="true" href="mailto:tom@domain" target="_blank">tom@domain</a><br>
<mailto:<a moz-do-not-send="true" href="mailto:tom@domain"
target="_blank">tom@domain</a>> <mailto:<a moz-do-not-send="true"
href="mailto:tom@domain" target="_blank">tom@domain</a><br>
<mailto:<a moz-do-not-send="true" href="mailto:tom@domain"
target="_blank">tom@domain</a>>>>"><br>
<br>
<display-name>tom</display-name><br>
</entry><br>
</list></resource-lists><br>
<br>
regards,<br>
Anca Vamanu<br>
<br>
Yoo Chan Jeon wrote:<br>
<br>
<br>
Hi,<br>
I just want to know how RLS handles SUBSCRIBE<br>
messages without<br>
using XCAP.<br>
I assume that the server already has the list<br>
information.<br>
I want send the SUBSRIBE message with resource list<br>
format:<br>
<br>
SUBSCRIBE <a class="moz-txt-link-freetext" href="sip:list@domain">sip:list@domain</a><br>
.<br>
.<br>
supported:eventlist<br>
Accept:application/rlmi+xml<br>
Accept:multipart/related<br>
I added rls, presence, presence_xml, and pua<br>
modlues in the<br>
configuration file.<br>
I do not have any problems to run the server.<br>
Which database should I add list@doamin<br>
<mailto:<a moz-do-not-send="true"
href="mailto:list@doamin" target="_blank">list@doamin</a> <mailto:<a
moz-do-not-send="true" href="mailto:list@doamin" target="_blank">list@doamin</a>><br>
<mailto:<a moz-do-not-send="true"
href="mailto:list@doamin" target="_blank">list@doamin</a> <mailto:<a
moz-do-not-send="true" href="mailto:list@doamin" target="_blank">list@doamin</a>>>>
to?<br>
<br>
How do I add the resource list?<br>
What kind of format do I need to add a list if I<br>
want to add<br>
joe@domain <mailto:<a moz-do-not-send="true"
href="mailto:joe@domain" target="_blank">joe@domain</a> <mailto:<a
moz-do-not-send="true" href="mailto:joe@domain" target="_blank">joe@domain</a>><br>
<mailto:<a moz-do-not-send="true" href="mailto:joe@domain"
target="_blank">joe@domain</a> <mailto:<a moz-do-not-send="true"
href="mailto:joe@domain" target="_blank">joe@domain</a>>>>,
bob@domain<br>
<mailto:<a moz-do-not-send="true"
href="mailto:bob@domain" target="_blank">bob@domain</a> <mailto:<a
moz-do-not-send="true" href="mailto:bob@domain" target="_blank">bob@domain</a>><br>
<mailto:<a moz-do-not-send="true" href="mailto:bob@domain"
target="_blank">bob@domain</a> <mailto:<a moz-do-not-send="true"
href="mailto:bob@domain" target="_blank">bob@domain</a>>>>,
tom@domain<br>
<mailto:<a moz-do-not-send="true"
href="mailto:tom@domain" target="_blank">tom@domain</a> <mailto:<a
moz-do-not-send="true" href="mailto:tom@domain" target="_blank">tom@domain</a>><br>
<mailto:<a moz-do-not-send="true" href="mailto:tom@domain"
target="_blank">tom@domain</a> <mailto:<a moz-do-not-send="true"
href="mailto:tom@domain" target="_blank">tom@domain</a>>>> ?<br>
<br>
<br>
Do you have some kind of examples?<br>
<br>
Thanks you.<br>
Jeon<br>
<br>
------------------------------------------------------------------------<br>
<br>
_______________________________________________<br>
Users mailing list<br>
<a moz-do-not-send="true"
href="mailto:Users@lists.opensips.org" target="_blank">Users@lists.opensips.org</a><br>
<mailto:<a moz-do-not-send="true"
href="mailto:Users@lists.opensips.org" target="_blank">Users@lists.opensips.org</a>><br>
<mailto:<a moz-do-not-send="true"
href="mailto:Users@lists.opensips.org" target="_blank">Users@lists.opensips.org</a><br>
<mailto:<a moz-do-not-send="true"
href="mailto:Users@lists.opensips.org" target="_blank">Users@lists.opensips.org</a>>><br>
<br>
<a moz-do-not-send="true"
href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users"
target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br>
<br>
<br>
<br>
<br>
<br>
<br>
</blockquote>
<br>
<br>
_______________________________________________<br>
Users mailing list<br>
<a moz-do-not-send="true" href="mailto:Users@lists.opensips.org"
target="_blank">Users@lists.opensips.org</a><br>
</div>
</div>
<div class="Ih2E3d"><a moz-do-not-send="true"
href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users"
target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br>
<br>
<br>
</div>
</blockquote>
<br>
</blockquote>
</div>
<br>
</blockquote>
<br>
</body>
</html>