hi Manoj,
As far as my understanding goes, 'single boot cycle' refers to the time b/w
the starting and closing of the phone.
The requirement that an UA SHOULD use the same call-id for all registration during a
single boot cycle is to ensure sequencing of the Register requests. It ensures that an
out-of-order REGISTER request doesnot do any harm. (change or remove a binding
registered by a REGISTER request sent after it). Section 10.3, step 8 explains the
processing of the Registrar w.r.t to callids.
One more thing, you should not be posting this question on the
[EMAIL PROTECTED] mailing list.
Hope this helps.
gautham
On Mon, 14 Oct 2002 16:49:28 -0500
"manoj mallik" <[EMAIL PROTECTED]> wrote:
> In RFC 3261, sec 10.2.4 Refreshing Bindings: it says that
> "A UA SHOULD use the same Call-ID for all registrations during a single boot
> cycle."
>
> I have following doubts w.r.t the above statement:-
> 1. What exactly the "single boot cycle" in the above statement means? is it
> implies to one Registration and de-Registration procedure or only just
> Registration procedure or something else?
>
> 2. Does the above statement means that the REGISTER request that is used for
> Refresh the Registration will use the same call-ID as the initial REGISTER
> message which was used for Registration?
>
> 3.Does all the new REGISTER request after de-Register should also maintain
> the SAME call-id or will have new call-id?
>
> Regards,
> Manoj
>
> _______________________________________________
> Sipping mailing list https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP
> Use [EMAIL PROTECTED] for questions on current sip
> Use [EMAIL PROTECTED] for new developments of core SIP
>
_______________________________________________
Sip-implementors mailing list
[EMAIL PROTECTED]
http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
