Daniel-Constantin Mierla writes:
> > Is it possible to configure Kamailio that wouldn’t send NOTIFY request
> > to watchers when publication status refresh (PUBLISH without XML Body)
> > occur?
> >
>
> no NOTIFY should be sent? Or the NOTIFY in this case should be sent
> without body, just with a new expire value and same etag?
Based on first example in Section 15 of rfc3903 no notify should be
sent:
M9: The PUA determines that the event state it previously published
is about to expire, and refreshes that event state.
PUBLISH sip:present...@example.com SIP/2.0
Via: SIP/2.0/UDP pua.example.com;branch=z9hG4bK771ash02
To: <sip:present...@example.com>
From: <sip:present...@example.com>;tag=1234kljk
Call-ID: 98798...@pua.example.com
CSeq: 1 PUBLISH
Max-Forwards: 70
SIP-If-Match: dx200xyz
Expires: 3600
Event: presence
Content-Length: 0
M10: The presence agent receives, and accepts the publication
refresh. The timers regarding the expiration of the specific
event state identified by the entity-tag are updated. As always,
the ESC returns an entity-tag in the response to a successful
PUBLISH. Note that no actual state change has occurred, so the
watchers will receive no NOTIFYs.
-- Juha
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
