Dear all
I am using OpenSER 1.3.1 branch release R3936. I face some bad behaviour
using pua and pua_mi modules.
I publish presence states via the management interface. Sometimes, it
happens that multiple PUBLISH message are sent by one request.
Unfortunately, there is no "system" or oder when this occurs. It just
happens after some publications.
In case of an expiration (Expires=0, E-Tag .) it is not that bad, I
receive the log message: ERROR:presence:update_presentity: No E_Tag
match.
In case of publication (Expires=-1, E-Tag .) it is very bad: After
publication, he receives also two similar messages, and threats both
PUBLISH messages as two different ones. Thus, creates two different
presentity entries with different E-Tags. If the state is expired now
via MI (Expires: -1, E-Tag .) only one of the E-Tags is removed. The
second stays in the presentity table and the user still appears online.
Any ideas what can be the reason and how to solve it?
Best regards
Sebastian