Hi Mon,
It is better...
as you pointed out in secn. 10.2, the intention is to avoid overwriting
a more recent registration with a previous registration.
So as far as possible, retaining the old Call-ID is better for
registrations.
Cheers,
Prasanna
[EMAIL PROTECTED] wrote:
__MIME_VERSION 0, __SANE_MSGID 0, __TAG_EXISTS_HTML 0'
X-crf-test: 0
X-Content-Filtered-By: Mailman/MimeDel 2.1.4
X-Mailman-Version: 2.1.4
List-Post: <mailto:[email protected]>
List-Subscribe:
<http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors>,
<mailto:[EMAIL PROTECTED]>
List-Unsubscribe:
<http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors>,
<mailto:[EMAIL PROTECTED]>
List-Archive: <http://lists.cs.columbia.edu/pipermail/sip-implementors>
List-Help: <mailto:[EMAIL PROTECTED]>
List-Id: SIP implementors <sip-implementors.cs.columbia.edu>
Hi All,
RFC 3261 states that "A UA SHOULD use the same Call-ID for all registrations
during a single boot cycle." And technically a UA is still within the same
boot cycle even when the network connection is lost. Right?
Hence is it fair to assume that UA should generate the same Call-ID when UA
remains powered on, and got reconnected to network after a network failure ?
(maybe Home gateway or DSL/cable modem or Internet SP failure). Will be great if
anyone can confim if my assumptions are correct.
RFC 3261, Section 10.2
Call-ID: All registrations from a UAC SHOULD use the same Call-ID header
field value for registrations sent to a particular registrar.
If the same client were to use different Call-ID values, a registrar
could not detect whether a delayed REGISTER request might have arrived out of
order.
RFC 3261, Section 10.2.4
A UA SHOULD use the same Call-ID for all registrations during a single boot
cycle. Registration refreshes SHOULD be sent to the same network address as
the original registration, unless redirected.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Thanks & Regards
Monica Ingudam (Mail: [EMAIL PROTECTED])
Signal Engineer
AOL Dulles
_______________________________________________
Sip-implementors mailing list
[email protected]
http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
_______________________________________________
Sip-implementors mailing list
[email protected]
http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
