<div>why do you configure " enable_publish_xcapdiff = no "?</div>
<div>As I known ,only you set it as yes,openxcap can publish diffenences to OpenSIPs.</div>
<div>Have a test!</div>
<div> </div>
<div><br> </div>
<div class="gmail_quote">2010/4/16 calment <span dir="ltr"><<a href="mailto:c.jeanne@astellia.com">c.jeanne@astellia.com</a>></span><br>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid"><br>I've set up both an OpenXcap and OpenSips 1.6 server to manage presence. I<br>use the Mercuro Bronze client to manage my contact list and store it in the<br>
xcap server. I would like to use the watcher mechanism in order to allow or<br>disallow a peer to view my presence.<br><br>When I connect the client to my infrastructure with a new sip account, it<br>tries to get its informations from xcap table through HTTP GET but obviously<br>
there is nothing about it (first session). Therefore it uses HTTP POST to<br>ask OpenXcap to INSERT into xcap table 2 RLS_SERVICES, 1 PIDF_MANIPULATION<br>and 1 RESOURCE_LIST. When it's done I can see an XMLRPC refreshWatchers<br>
message sent to OpenSips server and that is what I expect.<br><br>But, this is the only refreshWatchers message I get! Even if the client<br>perfoms changes in the xcap document, no new XMLRPC message is sent anymore!<br>
To clarify : I log a second user (Bob) and I add Alice in my contact list<br>thus OpenXcap modify xcap table in database. A SIP NOTIFY presence.winfo<br>message is sent to Alice and she accepts Bob to watch her status by<br>
modifying her xcap document. But once it's done, the expected XMLRPC<br>refreshWatcher is not sent ever.<br>This is a major isue because OpenSips is never aware that Alice has accepted<br>and do not send NOTFY to Bob (a least until SUBSCRIPTION is redone and xcap<br>
table is read once again by OpenSips).<br><br>Is my analysis correct ? Is there a specific configuration to do ?<br>Is there any known isues in OpenXcap that could explain my problem?<br><br>My openxcap.cfg :<br><br>[Server]<br>
address = 192.168.150.15<br>port = 80<br>root = <a href="http://xcap.open-ims.test/xcap-root" target="_blank">http://xcap.open-ims.test/xcap-root</a><br>backend = OpenSIPS<br>document_validation = Yes<br><br>[Logging]<br>
log_stacktrace=500<br>log_stacktrace=any<br>log_response_body=400,409<br>log_request_headers=401<br><br>[Authentication]<br>type = basic<br>cleartext_passwords = Yes<br>default_realm = open-ims.test<br>trusted_peers = 192.168.3.87, 192.168.3.124, 192.168.2.7<br>
<br>[TLS]<br><br><br>[Database]<br>authentication_db_uri =<br>mysql://opensips:opensipsrw@presence.open-ims.test/opensips<br>storage_db_uri = mysql://opensips:opensipsrw@presence.open-ims.test/opensips<br>subscriber_table = subscriber<br>
xcap_table = xcap<br><br>[OpenSIPS]<br>xmlrpc_url = <a href="http://presence.open-ims.test:8080/" target="_blank">http://presence.open-ims.test:8080</a><br>enable_publish_xcapdiff = no<br><font color="#888888"><br>--<br>View this message in context: <a href="http://n2.nabble.com/Question-Regarding-Watchers-table-tp3856740p4912886.html" target="_blank">http://n2.nabble.com/Question-Regarding-Watchers-table-tp3856740p4912886.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></font></blockquote></div><br>