Hello,
In RFC 3903:
3. The ESC examines the SIP-If-Match header field of the PUBLISH
request for the presence of a request precondition.
* If the request does not contain a SIP-If-Match header field,
the ESC MUST generate and store a locally unique entity-tag for
identifying the publication. This entity-tag is associated
with the event-state carried in the body of the PUBLISH
request.
So generating a new entity-tag should be done for each initial Publish
no matter if a record with the same attributes exist.
The idea is that there can be more publications for the same resource,
useful in the case in which you have more devices registered with the
same uri.
regards,
Anca
Juha Heinanen wrote:
i had a bug in my mwi publish script and it sent two initial publish
request (both without SIP-If-Match header). i noticed that it resulted
in two entries in presentity table with same username/domain/event/body,
but of course with different etag/expires/received_time values.
is this intended behavior or should the second initial publish have been
replaced the first one? i haven't yet checked what the rfc says. or
perhaps i should deal with this in a presence_mwi specific way using
some handler function?
-- juha
_______________________________________________
Devel mailing list
Devel@openser.org
http://openser.org/cgi-bin/mailman/listinfo/devel
_______________________________________________
Devel mailing list
Devel@openser.org
http://openser.org/cgi-bin/mailman/listinfo/devel
