[...Trimmed sipping...]
Please don't cross post to sipping and sip-implementors; most people
who monitor sipping also monitor sip-implementors.
manoj mallik 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?
Consider a SIP PDA or a SIP wireless phone that is powered on. For the
duration that it remains powered on, any registration, de-registration
and registration refresh requests can have the same Call-ID. Of course,
they MUST have a different CSeq number and topmost Via branch parameter
(if they are rfc3261 compliant) to be recognized as separate
transactions.
> 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?
Sure; no harm done.
> 3.Does all the new REGISTER request after de-Register should also
> maintain the SAME call-id or will have new call-id?
They can have the same Call-ID. Attention should be paid more to the
CSeq and topmost Via branch parameter, since for rfc3261 registrars, the
branch parameter in the topmost Via will indicate a new transaction and
for rfc2543 registrars, an increasing CSeq number will hash to a new
transaction.
Regards,
- vijay
--
Vijay K. Gurbani vkg@{lucent.com,research.bell-labs.com,acm.org}
Wireless Networks Group/Internet Software and Services
Lucent Technologies/Bell Labs Innovations, 2000 Lucent Lane, Rm 6G-440
Naperville, Illinois 60566 Voice: +1 630 224 0216
_______________________________________________
Sip-implementors mailing list
[EMAIL PROTECTED]
http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
