Chaney, Charles (SNL US) wrote:
> Hi,
>
> I have a question regarding contact headers returned in the registration
> response where more than one contact binding exists. Should a new
> registration or refresh "touch" other existing contact bindings for the
> AoR? The question is specific to the expires value reported for each
> contact binding. I understand that if the registrar accepts the
> registration request the expires value reflects the accepted expiration
> time for that contact binding, but some questions have been raised about
> the expires value reported for the other contact binding. Should the
> other contact binding reflect the remaining (time-to-live) expiration
> value or be updated to reflect the new registration (or refresh), i.e.,
> all are reported with the same expires value. I cannot point to any
> definitive requirement in RFC3261.
It always seemed clear to me, even if only implicit.
Each registered contact has its own expiration time that counts down. In
a new register request, only the contacts mentioned in the request are
updated - the others continue counting down their existing expiration time.
There is no other way that makes sense if you assume there are two
separate UAs each registering their own contact to a common AOR.
Paul
_______________________________________________
Sip-implementors mailing list
[email protected]
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
