Hi,<br>we have checked the presence extension for DB_MODE only in the master branch. But it's not complete DB_ONLY mode, it seems that it still uses the cache for active_watchers in write through mode. Is there any reason for it? That can still make problem for the scalability for the multiple presence servers, because if an presence event (either SIP or XCAP) of an active subscription in the cache of one presence server, goes to another presence server, can still cause the problem even the DB is sync with the cache.<br>
<br><br>Best Regards,<br>Laura<br><br><div class="gmail_quote">On Fri, Jul 1, 2011 at 5:02 PM, Henning Westerholt <span dir="ltr"><<a href="mailto:henning.westerholt@1und1.de">henning.westerholt@1und1.de</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">On Thursday 30 June 2011, laura testi wrote:<br>
> [...]<br>
<div class="im">> pres_refresh_watchers triggered by xcap message in another presence server:<br>
> with the hashing over to uri in dispacther workaround, it seems solve the<br>
> first problem for SIP/SIMPLE messages, but we have the same kind of<br>
> problem for xcap message. For example, a subscription is in a local cache<br>
> of one server, and the incomming xcap message related to the same<br>
> subscription goes to another server, and this message trigger the<br>
> pres_update_watchers pres_refresh_watchers presence functions from the<br>
> configuration script in the server where there is no subscription in the<br>
> local cache, then it send the wrong notify message. This can happen when a<br>
> user add/remove a contact, and the SUBSCRIBE goes to one server and XCAP<br>
> PUT goes to another server. Unfortunately there is no DB mode only in<br>
> PRESENCE module like REGISTRAR module. The fallback to db can't help<br>
> either for point 1 or for point 2. Can you help please?<br>
<br>
</div>Hi laura,<br>
<br>
i can't comment on the other question, but Marius B did some presence<br>
extensions in master branch a few month ago, that the presence module now<br>
supports a db_mode module parameter including DB_ONLY. It will be in kamailio<br>
3.2, maybe you can have a look to the master branch and backport it, if you<br>
need it faster.<br>
<br>
Best regards,<br>
<font color="#888888"><br>
Henning<br>
</font></blockquote></div><br>