RFC3261: SIP:12.2.1.2处理响应

最新推荐文章于 2025-12-17 10:18:55 发布

翻译最新推荐文章于 2025-12-17 10:18:55 发布 · 89 阅读

0 ·

CC 4.0 BY-SA版权

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

文章标签：

#sip

SIP 专栏收录该内容

302 篇文章

订阅专栏

本文详细阐述了UAC如何处理来自事务层的请求响应，包括处理超时、3xx响应的处理、对话中不同响应导致的对话操作，以及INVITE对话中BYE消息的发送。

12.2.1.2 Processing the Responses
12.2.1.2处理响应

   The UAC will receive responses to the request from the transaction layer.  If the client transaction returns a timeout, this is treated as a 408 (Request Timeout) response.

UAC将从事务层接收对请求的响应。如果客户端事务返回超时，则将其视为408（请求超时）响应。

   The behavior of a UAC that receives a 3xx response for a request sent within a dialog is the same as if the request had been sent outside a dialog.  This behavior is described in Section 8.1.3.4.

UAC接收在对话内发送的请求的3xx响应的行为与在对话外发送请求的行为相同。该行为在第8.1.3.4节中进行了描述。

      Note, however, that when the UAC tries alternative locations, it still uses the route set for the dialog to build the Route header of the request.

但是，请注意，当UAC尝试其他位置时，它仍然使用对话的路由集来构建请求的路由报头。

   When a UAC receives a 2xx response to a target refresh request, it MUST replace the dialog's remote target URI with the URI from the Contact header field in that response, if present.

当UAC接收到对目标刷新请求的2xx响应时，它必须将对话的远程目标URI替换为该响应中Contact报头字段中的URI（如果存在）。

   If the response for a request within a dialog is a 481 (Call/Transaction Does Not Exist) or a 408 (Request Timeout), the UAC SHOULD terminate the dialog.  A UAC SHOULD also terminate a dialog if no response at all is received for the request (the client transaction would inform the TU about the timeout.)

如果对话中的请求响应为481（呼叫/事务不存在）或408（请求超时），则UAC应终止对话。如果根本没有收到对请求的响应（客户端事务会通知TU超时），UAC也应该终止对话

      For INVITE initiated dialogs, terminating the dialog consists of sending a BYE.

对于INVITE启动的对话，终止对话包括发送BYE。