[SIPForum-discussion] CALL-ID
shawn.degraw at comcast.net
shawn.degraw at comcast.net
Tue Dec 7 19:09:35 UTC 2010
See below excerpt from RFC3261:
8.1.1.4 Call-ID The Call-ID header field acts as a unique identifier to group
together a series of messages. It MUST be the same for all requests
and responses sent by either UA in a dialog. It SHOULD be the same
in each registration from a UA.
In a new request created by a UAC outside of any dialog, the Call-ID
header field MUST be selected by the UAC as a globally unique
identifier over space and time unless overridden by method-specific
behavior. All SIP UAs must have a means to guarantee that the Call-
ID header fields they produce will not be inadvertently generated by
any other UA. Note that when requests are retried after certain Rosenberg, et. al. Standards Track [Page 37] RFC 3261 SIP: Session Initiation Protocol June 2002 failure responses that solicit an amendment to a request (for
example, a challenge for authentication), these retried requests are
not considered new requests, and therefore do not need new Call-ID
header fields; see Section 8.1.3.5.
Use of cryptographically random identifiers (RFC 1750 [12]) in the
generation of Call-IDs is RECOMMENDED. Implementations MAY use the
form "localid at host". Call-IDs are case-sensitive and are simply
compared byte-by-byte.
Using cryptographically random identifiers provides some
protection against session hijacking and reduces the likelihood of
unintentional Call-ID collisions.
No provisioning or human interface is required for the selection of
the Call-ID header field value for a request.
For further information on the Call-ID header field, see Section
20.8.
Example:
Call-ID: f81d4fae-7dec-11d0-a765-00a0c91e6bf6 at foo.bar.com
----- Original Message -----
From: "Deepak Bhatia" <deepak.bhatia at nechclst.in>
To: discussion at sipforum.org
Sent: Tuesday, December 7, 2010 2:25:12 AM
Subject: [SIPForum-discussion] CALL-ID
----- Original Message -----
From: "Deepak Bhatia" <deepak.bhatia at nechclst.in>
To: discussion at sipforum.org
Sent: Tuesday, December 7, 2010 2:25:12 AM
Subject: [SIPForum-discussion] CALL-ID
Hi,
All SIP UAs must have a means to guarantee that the Call-ID header fields they produce will not be inadvertently generated by any other UA.
How is it achieved ?
Regards
Deepak Bhatia DISCLAIMER:
-----------------------------------------------------------------------------------------------------------------------
The contents of this e-mail and any attachment(s) are confidential and
intended
for the named recipient(s) only.
It shall not attach any liability on the originator or NECHCL or its
affiliates. Any views or opinions presented in
this email are solely those of the author and may not necessarily reflect the
opinions of NECHCL or its affiliates.
Any form of reproduction, dissemination, copying, disclosure, modification,
distribution and / or publication of
this message without the prior written consent of the author of this e-mail is
strictly prohibited. If you have
received this email in error please delete it and notify the sender
immediately. .
-----------------------------------------------------------------------------------------------------------------------
_______________________________________________
This is the SIP Forum discussion mailing list
TO UNSUBSCRIBE, or edit your delivery options, please visit http://sipforum.org/mailman/listinfo/discussion
Post to the list at discussion at sipforum.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://sipforum.org/pipermail/discussion/attachments/20101207/5d2cf8cc/attachment-0002.html>
More information about the discussion
mailing list