RFC 3261: A UA SHOULD use the same Call-ID for all registrations during a
single boot cycle.
Does it mean only the register refresh should have the same call-Id for a register cycle (cycle mean register, and deregister), or all registrations cycles. ie. UA might register and deregister several times in a single boot cycle. Does all the new register request after deregister should also maintain the SAME call-id is it? or, once the UA deregisters, the next new register can have new call-id? have new call-id will work according to 10.3 Processing REGISTER Requests point 7.
For each address, the registrar then searches the list of
current bindings using the URI comparison rules. If the
binding does not exist, it is tentatively added. If the
binding does exist, the registrar checks the Call-ID value. If
the Call-ID value in the existing binding differs from the
Call-ID value in the request, the binding MUST be removed if
the expiration time is zero and updated otherwise. If they are
the same, the registrar compares the CSeq value. If the value
is higher than that of the existing binding, it MUST update or
remove the binding as above. If not, the update MUST be
aborted and the request fails.
please clarify.
Thanks
Yahoo! - We Remember
9-11: A tribute to the more than 3,000 lives lost
