RFC3261: SIP:8.1.3.2无法识别的响应

最新推荐文章于 2025-08-08 10:20:29 发布

翻译最新推荐文章于 2025-08-08 10:20:29 发布 · 73 阅读

0 ·

CC 4.0 BY-SA版权

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

文章标签：

#sip

SIP 专栏收录该内容

302 篇文章

订阅专栏

文章阐述了AUAC在处理网络请求时遇到无法识别的响应代码的行为准则，如将431错误视为400错误，并区分对待最终和临时响应，确保正确处理100和183响应码。

8.1.3.2 Unrecognized Responses
8.1.3.2无法识别的响应

   A UAC MUST treat any final response it does not recognize as being equivalent to the x00 response code of that class, and MUST be able to process the x00 response code for all classes.  For example, if a UAC receives an unrecognized response code of 431, it can safely assume that there was something wrong with its request and treat the response as if it had received a 400 (Bad Request) response code.  A UAC MUST treat any provisional response different than 100 that it does not recognize as 183 (Session Progress).  A UAC MUST be able to process 100 and 183 responses.

UAC必须将其未识别的任何最终响应视为等效于该类的x00响应代码，并且必须能够处理所有类的x0响应代码。例如，如果UAC接收到无法识别的响应代码431，它可以安全地假设其请求有问题，并将该响应视为接收到400（坏请求）响应代码。UAC必须将任何不同于100的临时响应视为183（会话进度）。UAC必须能够处理100个和183个响应。