1229 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

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@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@foo.bar.com