THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#133 - kamailio 3.1.3 Presence + XCAP problem, is it a bug? User who did this - laura testi (lau.testi) ---------- Hi, In order to solve the problem, we have applied a little change on the presence module behavior. Here some details, that I would share with you: The function we have modified is the one below: int pres_update_status(subs_t subs, str reason, db_key_t* query_cols,db_val_t* query_vals, int n_query_cols, subs_t** subs_array) and the “diff” output beetwen the orig and the new presence.c file is: # diff presence.c.orig presence.c.patch 714a715,721 Our modification acts on the watchers_table state update: during a watcher state update, if: • the Xcap PRE-Rules doc doesn’t contain the record of an contact and • the previous state of a watcher in the watcher table is equal to “1” (active) then the new state is set to “3” (reason=deleted). Using this fix, the add/delete contact strange behavior described in our previous email seems to be solved.... Kind Regards, laura ---------- More information can be found at the following URL: http://sip-router.org/tracker/index.php?do=details&task_id=133#comment2… You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.