Since the DATE field provided in the register response is useful to set the
UAC's time (per 10.2.5)...
If a DATE header field is included in the clients REGISTER request, does the
registrar take into
account the transmission time between the UAC sending the registration and
the registrar receiving
it (expires - (current time - date header time))? That is, if the
transmission time is 30 seconds and
the expires field was 300 seconds, does the registrar consider the intended
expiration to be 270 seconds
from the time it received the request? Or is transmission time not
considered applicable to the expires field?
It seems given the procotol timeouts and the small expires values allowed
that this may have be taken into
account already. If so, where did I miss it?
The same consideration applies when a UAC fetches the registration bindings
and a DATE header
field is included in the response. A couple of questions related to the
UACs handling of the REGISTER
response.
1. Is the expires value in the response the seconds remaining from the
original registration til now?
Or is it simply the original expires value? E.g. REGISTER at 10:00:00
with expires=3600.
Fetching the bindings 2400 seconds later would yield 1200 or 3600 for
the expires value?
2. Should the UAC use the DATE field (the registrars time) when evaluating
the actual time left in the
expires field (similar to what was asked for the registrar above)?
Thanks
Ken
_______________________________________________
Sip-implementors mailing list
[EMAIL PROTECTED]
http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
