Hi Mihai, This behavior happens because the SIP phone that you use seems to have a broken SIP presence implementation.
When publishing the second or latter time, it should put in the Publish request the E-Tag received from the opensips presence server in the 200OK for the previous Publish. This way the server known that the Publish updates an existing state. I suppose that your client does not put the E-Tag, so the opensips presence server thinks it is a Publish from another device registered with the same account. And in this case it concatenates the states as you have seen. RFC 3903 explains this mechanism. Regards, Anca Vamanu
_______________________________________________ Users mailing list [email protected] http://lists.opensips.org/cgi-bin/mailman/listinfo/users
