Yufei Tao writes:
This is when multiple SIP clients are registered using
the same
credentials, they each have a presentity entry, with the same username
and domain but different etags, which is fine. But when they expire, the
presentity.etag will be filled with '*#-OFFLINE-#*', and when both
expire at about the same time, kamailio tries to fill both with the same
'*#-OFFLINE-#*' etag. Because presentity table has a 'CONSTRAINT
presentity_idx UNIQUE (username, domain, event, etag)', this gives the
errors.
Should the constraint be removed to cope with this situation?
how are those '*#-OFFLINE-#*' records used? are both needed? does it
make sense to publish different information for the same presentity by
two UAs? if i subscribe to presence of that username@domain, do i get
two notifys one from each or just one?
-- juha