RFC3261: SIP:8.1.1.8 Contact

最新推荐文章于 2024-07-16 14:19:04 发布

꧁白杨树下꧂

最新推荐文章于 2024-07-16 14:19:04 发布

阅读量460

点赞数

分类专栏： SIP 文章标签： sip

原文链接：https://www.ietf.org/rfc/rfc3261.html

版权

SIP 专栏收录该内容

302 篇文章

订阅专栏

Contact头字段在SIP请求中至关重要，它包含用于后续联系的SIP或SIPSURI。INVITE请求中必须有且只能有一个有效的Contact头，其URI适用于所有对话。如果Request-URI或topRoute包含SIPSURI，Contact头也会相应包含。更多信息可在第20.10节找到。

摘要生成于 C知道，由 DeepSeek-R1 满血版支持，前往体验 >

8.1.1.8 Contact

   The Contact header field provides a SIP or SIPS URI that can be used to contact that specific instance of the UA for subsequent requests. The Contact header field MUST be present and contain exactly one SIP or SIPS URI in any request that can result in the establishment of a dialog.  For the methods defined in this specification, that includes only the INVITE request.  For these requests, the scope of the Contact is global.  That is, the Contact header field value contains the URI at which the UA would like to receive requests, and this URI MUST be valid even if used in subsequent requests outside of any dialogs.

Contact报头字段提供SIP或SIPS URI，其可用于联系UA的该特定实例以进行后续请求。Contact报头字段必须存在，并且在任何可能导致建立对话的请求中仅包含一个SIP或SIPS URI。对于本规范中定义的方法，仅包括INVITE请求。对于这些请求，联系人的范围是全球性的。也就是说，Contact头字段值包含UA希望接收请求的URI，即使在任何对话之外的后续请求中使用该URI，该URI也必须有效。

   If the Request-URI or top Route header field value contains a SIPS URI, the Contact header field MUST contain a SIPS URI as well.

如果Request-URI或top Route头字段值包含SIPS URI，则Contact报头字段也必须包含SIPS URL。

   For further information on the Contact header field, see Section 20.10.

有关联系人标题字段的更多信息，请参阅第20.10节。