<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Apr 21, 2010, at 12:47 PM, Laurent Etiemble wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">Hello,<div><br></div><div>Mercuro does not modify the presence rules when it accepts a subscription, because it deals with lists instead of individual entries:</div><div>1) A subscription request is received by Mercuro and presented to the user</div> <div>2) The user accepts the subscription. Mercuro put the contact inside the allowed list.</div></blockquote><br><blockquote type="cite"><div>3) The presence server detects that a list linked to a presence rule has been changed. It sends any needed notification.</div></blockquote><div><br></div><div>It could be done.</div><div><br></div><div>However this requires processing in the server (potentially both Presence Agent and XCAP) based on some heuristics criteria unless there is something standardized about this behaviour. Different clients may also do different things. </div><div><br></div><div>Is there any normative reference for this that you know of?</div><div><br></div><div>Adrian</div><div><br></div><br><blockquote type="cite"> <div><br></div><div>The point is that if you have presence rules that apply to lists (in pres-rules), any modification of these lists (in resource-lists) must trigger a computation of the presence rules, to check if notifications are needed.</div> <div><br></div><div>Regards, Laurent Etiemble.<br><br></div>Need an IMS Client ?<br>Try out Mercuro IMS Client.<br>More info at <meta charset="utf-8"><a href="http://www.mercuro.net/">http://www.mercuro.net/</a><br><div> <br> <div class="gmail_quote">2010/4/21 Adrian Georgescu <span dir="ltr"><<a href="mailto:ag@ag-projects.com">ag@ag-projects.com</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"> If pres-rules document does not change, no call to refreshWatchers()<br> will occur.<br> <br> The client must update his presence rules when accepting a subscription.<br> <font color="#888888"><br> Adrian<br> </font><div><div></div><div class="h5"><br> On Apr 21, 2010, at 12:04 PM, calment wrote:<br> <br> ><br> ><br> > calment wrote:<br> >><br> >> I'm not a python expert but I have some time to spend on this issue<br> >> so I<br> >> just plunge to the code to seek the problem. Let me know if you found<br> >> something.<br> >><br> ><br> > Ok, I've checked the OpenXcap code. In backend/opensips.py I can see<br> > that a<br> > refreshWatcherMessage is sent if application_id is either "pres-<br> > rules" or<br> > "org.openmobilealliance.pres-rules" or "pidf-manipulation".<br> > Indeed, when Mercuro Client log for the first time, it HTTP PUT a<br> > org.openmobilealliance.pres-rules message (along with 2 resource-<br> > lists and 1<br> > rls-services) which make openXcap send a refreshWatcher message.<br> ><br> > The problem is that, when Mercuro accept to be viewed by a another<br> > contact<br> > (after a SIP NOTIFY presence.winfo), it does not send an<br> > org.openmobilealliance.pres-rules again. It justs add the contact in<br> > its<br> > buddylist by sending 2 "resource-lists" (index and<br> > properties-resource-list.xml) and obviously it doesn't make OpenXcpa<br> > to send<br> > a refreshWatchers message.<br> ><br> > Actualy I really wonder if the problem comes from the Mercuro Bronze<br> > 4.0.1624.0 client. But due to my misknowledge of xcap, I'm unable to<br> > determine.<br> ><br> > Could somebody point me a simple explanation of this technology ?<br> ><br> > Regards,<br> ><br> ><br> > --<br> > View this message in context: <a href="http://n2.nabble.com/Question-Regarding-Watchers-table-tp3856740p4936064.html" target="_blank">http://n2.nabble.com/Question-Regarding-Watchers-table-tp3856740p4936064.html</a><br> > Sent from the OpenSIPS - Users mailing list archive at Nabble.com.<br> ><br> > _______________________________________________<br> > Users mailing list<br> > <a href="mailto:Users@lists.opensips.org">Users@lists.opensips.org</a><br> > <a 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> Users mailing list<br> <a href="mailto:Users@lists.opensips.org">Users@lists.opensips.org</a><br> <a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br> </div></div></blockquote></div><br></div> _______________________________________________<br>Users mailing list<br><a href="mailto:Users@lists.opensips.org">Users@lists.opensips.org</a><br><a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br></blockquote></div><br></body></html>