RFC3261: SIP:8.1.1.4呼叫ID

8.1.1.4 Call-ID
8.1.1.4呼叫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.

呼叫ID报头字段充当唯一标识符，将一系列消息分组在一起。对话中任一UA发送的所有请求和响应都必须相同。在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.

​在UAC在任何对话之外创建的新请求中，除非被特定于方法的行为覆盖，否则UAC必须将呼叫ID头字段选择为空间和时间上的全局唯一标识符。所有SIP UA都必须有一种方法来保证它们生成的呼叫ID头字段不会被任何其他UA无意中生成。请注意，当在某些请求修改的失败响应（例如，身份验证挑战）之后重试请求时，这些重试的请求不被视为新请求，因此不需要新的呼叫ID报头字段；参见第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.

​建议在生成呼叫ID时使用加密随机标识符（RFC 1750[12]）。实施可使用表格“localid@host“.调用ID区分大小写，只需逐字节进行比较。

      Using cryptographically random identifiers provides some protection against session hijacking and reduces the likelihood of unintentional Call-ID collisions.

使用加密随机标识符提供了一些防止会话劫持的保护，并降低了无意的呼叫ID冲突的可能性。

   No provisioning or human interface is required for the selection of the Call-ID header field value for a request.

选择请求的“呼叫ID”报头字段值不需要设置或人工界面。

   For further information on the Call-ID header field, see Section 20.8.

​有关呼叫ID标题字段的更多信息，请参阅第20.8节。
   
   Example:
示例：

      Call-ID: f81d4fae-7dec-11d0-a765-00a0c91e6bf6@foo.bar.com