Network Working Group B. Foster
Request for Comments: 3661 C. Sivachelvan
Updates: 3435 Cisco Systems
Category: Informational December 2003
Network Working Group B. Foster
Request for Comments: 3661 C. Sivachelvan
Updates: 3435 Cisco Systems
Category: Informational December 2003
Media Gateway Control Protocol (MGCP) Return Code Usage
媒体网关控制协议（MGCP）返回代码用法
Status of this Memo
本备忘录的状况
This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited.
本备忘录为互联网社区提供信息。它没有规定任何类型的互联网标准。本备忘录的分发不受限制。
Copyright Notice
版权公告
Copyright (C) The Internet Society (2003). All Rights Reserved.
版权所有（C）互联网协会（2003年）。版权所有。
Abstract
摘要
This document provides implementation guidelines for the use of return codes in RFC 3435, Media Gateway Control Protocol (MGCP) Version 1.0. Return codes in RFC 3435 do not cover all possible specific situations that may ever occur in a gateway. That is not possible and not necessary. What is important is to ensure that the Call Agent that receives a return code behaves appropriately and consistently for the given situation. The purpose of this document is to provide implementation guidelines to ensure that consistency.
本文档提供了RFC 3435媒体网关控制协议（MGCP）1.0版中返回码的使用实施指南。RFC 3435中的返回代码不包括网关中可能出现的所有特定情况。这是不可能的，也不是必要的。重要的是确保接收返回代码的调用代理在给定情况下的行为适当且一致。本文件旨在提供实施指南，以确保一致性。
Table of Contents
目录
1. Introduction. . . . . . . . . . . . . . . . . . . . . . . . . 2
1.2. Document Organization . . . . . . . . . . . . . . . . . 2
2. Return Code Usage . . . . . . . . . . . . . . . . . . . . . . 2
2.1. Return Code Categories. . . . . . . . . . . . . . . . . 2
2.2. Return Code Situations and Categories . . . . . . . . . 3
2.3. Summary of Return Code Categories . . . . . . . . . . . 19
3. Additional Guidelines . . . . . . . . . . . . . . . . . . . . 21
3.1. Gateway Recommendations . . . . . . . . . . . . . . . . 21
3.2. Call Agent Recommendations. . . . . . . . . . . . . . . 21
4. Security Considerations . . . . . . . . . . . . . . . . . . . 22
5. Acknowledgements. . . . . . . . . . . . . . . . . . . . . . . 22
6. Normative References. . . . . . . . . . . . . . . . . . . . . 22
7. Authors' Addresses. . . . . . . . . . . . . . . . . . . . . . 23
8. Full Copyright Statement. . . . . . . . . . . . . . . . . . . 24
1. Introduction. . . . . . . . . . . . . . . . . . . . . . . . . 2
1.2. Document Organization . . . . . . . . . . . . . . . . . 2
2. Return Code Usage . . . . . . . . . . . . . . . . . . . . . . 2
2.1. Return Code Categories. . . . . . . . . . . . . . . . . 2
2.2. Return Code Situations and Categories . . . . . . . . . 3
2.3. Summary of Return Code Categories . . . . . . . . . . . 19
3. Additional Guidelines . . . . . . . . . . . . . . . . . . . . 21
3.1. Gateway Recommendations . . . . . . . . . . . . . . . . 21
3.2. Call Agent Recommendations. . . . . . . . . . . . . . . 21
4. Security Considerations . . . . . . . . . . . . . . . . . . . 22
5. Acknowledgements. . . . . . . . . . . . . . . . . . . . . . . 22
6. Normative References. . . . . . . . . . . . . . . . . . . . . 22
7. Authors' Addresses. . . . . . . . . . . . . . . . . . . . . . 23
8. Full Copyright Statement. . . . . . . . . . . . . . . . . . . 24
This document provides implementation guidelines for the use of return codes in the Media Gateway Control Protocol MGCP 1.0 [1]. Return codes in [1] do not cover all possible specific situations that may ever occur in the gateway. That is not possible and not necessary. What is important is to ensure that the Call Agent that receives that return code behaves appropriately and consistently for the situation that occurred. The solution described in this document is to categorize return codes that gateways return based on the expected behavior for the Call Agents that receive them.
本文件提供了媒体网关控制协议MGCP 1.0[1]中返回码使用的实施指南。[1]中的返回代码并未涵盖网关中可能出现的所有特定情况。这是不可能的，也不是必要的。重要的是确保接收该返回代码的调用代理在发生的情况下行为适当且一致。本文档中描述的解决方案是根据接收网关的呼叫代理的预期行为对网关返回的返回代码进行分类。
Categorizing errors helps both Call Agent and gateway developers: it helps gateway developers choose an appropriate return code when a specific one for the situation is not available; it also helps Call Agent developers ensure that there is consistent behavior for the return code that is received.
对错误进行分类有助于呼叫代理和网关开发人员：当特定的返回代码不可用时，它有助于网关开发人员选择适当的返回代码；它还帮助调用代理开发人员确保接收到的返回代码具有一致的行为。
In addition to categorizing return codes (section 2.1), section 2.2 provides a consolidated list of return codes in terms of "situations" that may have triggered and the "categories" that they fall under. This provides some additional implementation guidelines for the use of these return codes. Section 2.3 includes a summary of the return codes and their categories. Section 3 provides some additional implementation guidelines for Call Agent and gateway developers.
除了对退货代码进行分类（第2.1节），第2.2节还根据可能触发的“情况”及其所属的“类别”提供了退货代码的综合列表。这为这些返回代码的使用提供了一些附加的实现指南。第2.3节包括返回代码及其类别的摘要。第3节为呼叫代理和网关开发人员提供了一些额外的实现指南。
The following categorizes return codes from gateways based on expected Call Agent behavior.
下面根据预期的呼叫代理行为对来自网关的返回代码进行分类。
Category normal: These return codes are used in normal operation and do not represent error conditions.
正常类别：这些返回代码用于正常操作，不代表错误情况。
Category none (specific errors requiring specific action): A return code associated with a specific situation in the gateway that will invoke a corresponding specific Call Agent behavior. As such, these return codes are not categorized into a common behavioral category.
类别none（需要特定操作的特定错误）：与网关中的特定情况关联的返回代码，该情况将调用相应的特定调用代理行为。因此，这些返回代码不属于常见的行为类别。
Category "Service Failure": A category in which the endpoint is either out-of-service or the treatment by the Call Agent is expected to be the same as for an out-of-service endpoint.
类别“服务失败”：一个类别，其中端点要么停止服务，要么调用代理的处理预期与停止服务的端点相同。
Category "Provisioning Mismatch": A situation where the gateway has indicated that it does not support what the Call Agent has asked it to do. This may be caused by a lack of synchronization between the provisioning of the Call Agent and the gateway. Note that attempts should be made to weed out these types of error situations during integration testing.
类别“配置不匹配”：网关表示不支持呼叫代理要求其执行的操作的情况。这可能是由于呼叫代理和网关的设置之间缺乏同步造成的。请注意，在集成测试期间，应尝试消除这些类型的错误情况。
Category "Temporary Failure": The transient nature of this error is such that this particular call is likely to be permanently affected but later calls on the same endpoint may proceed successfully. Typically the situation that caused this error is not going to disappear unless there is some change in state in the gateway or network (e.g., more bandwidth becomes available, more CPU resources become available etc.). This situation is not likely to change in a few 10's of milliseconds but could change within some number of seconds or minutes later (as resources become free), i.e., within the time period that you might expect a different call to be tried on that endpoint.
类别“临时故障”：此错误的暂时性质是，此特定调用可能会受到永久影响，但同一端点上的后续调用可能会成功进行。通常，导致此错误的情况不会消失，除非网关或网络中的状态发生一些变化（例如，更多带宽变为可用，更多CPU资源变为可用等）。这种情况不太可能在10毫秒内发生变化，但可能会在几秒钟或几分钟后发生变化（随着资源变得可用），即在您可能期望在该端点上尝试不同调用的时间段内。
Category "State Mismatch": A case where there is a state mismatch between the Call Agent and the gateway that can be resolved by the Call Agent making a request that is more appropriate to the gateway state. Although categorized with a common category indicator the behavior of the Call Agent will depend on the situation (the type of state mismatch that has occurred as well as other state information, e.g., call state).
类别“状态不匹配”：呼叫代理和网关之间存在状态不匹配的情况，可通过呼叫代理发出更适合网关状态的请求来解决。尽管使用通用类别指示器进行分类，但呼叫代理的行为将取决于情况（已发生的状态不匹配类型以及其他状态信息，例如呼叫状态）。
Category "Remote Connection Descriptor Error": This indicates some mismatch between the two gateways involved in the call. Note that per RFC 2327, all gateways should ignore SDP attributes that they do not recognize (i.e., lack of recognition of an SDP attribute should not be the cause of an error indication).
类别“远程连接描述符错误”：这表示调用中涉及的两个网关之间存在某些不匹配。请注意，根据RFC 2327，所有网关都应忽略它们无法识别的SDP属性（即，SDP属性未被识别不应成为错误指示的原因）。
The exact behavior of the Call Agent for the above categories may depend on the type of endpoint (analog, ISUP trunk, CAS trunk, etc.), whether this is the originating or terminating endpoint in the call and possibly other information related to call state. This document does not attempt to outline the Call Agent behavior based on call state. Instead, it just recommends that the Call Agent behavior be consistent based on a combination of call state and the specific category of error received.
上述类别的呼叫代理的确切行为可能取决于端点的类型（模拟、ISUP中继、CAS中继等）、这是呼叫中的始发端点还是终止端点以及可能与呼叫状态相关的其他信息。本文档不试图概述基于调用状态的调用代理行为。相反，它只是建议呼叫代理行为基于呼叫状态和收到的特定错误类别的组合保持一致。
This section describes return codes in MGCP 1.0 [1] in terms of "situations" that may have triggered that return code and "categories" to which the return code belongs. The purpose is to provide developers additional guidelines for return code use.
本节介绍MGCP 1.0[1]中可能触发返回代码的“情况”以及返回代码所属的“类别”。目的是为开发人员提供额外的返回代码使用指南。
Note that any indication that a response is valid for a NotificationRequest (RQNT) is also an indication that it is valid for a connection handling request, i.e., CreateConnection (CRCX), ModifyConnection (MDCX), or DeleteConnection (DLCX) with an encapsulated RQNT. The same holds for the EndpointConfiguration (EPCF) command.
请注意，响应对NotificationRequest（RQNT）有效的任何指示也表示它对连接处理请求有效，即使用封装的RQNT的CreateConnection（CRCX）、ModifyConnection（MDCX）或DeleteConnection（DLCX）。EndpointConfiguration（EPCF）命令也是如此。
000 - Response acknowledgement
000-回应确认
Response valid for: Confirmation of a final response after a provisional response (3-way handshake).
响应有效期：临时响应（三方握手）后的最终响应确认。
Situation: If the final response that follows a provisional response contains an empty response acknowledgement parameter, a Response Acknowledgement is used to acknowledge the final response (section 3.5.6 of [1]).
情况：如果临时响应后的最终响应包含空响应确认参数，则响应确认用于确认最终响应（见[1]第3.5.6节）。
Category: normal.
类别：正常。
100 - Transaction in progress
100-正在进行的交易
Response valid for: Any command that may result in a long transaction execution time, e.g., more than 200 ms.
响应有效：任何可能导致长事务执行时间的命令，例如超过200毫秒。
Situation: When a transaction is expected to take a processing time that is beyond the normal retry timer, the gateway will return a provisional response. A final response will be provided later, after the transaction has completed. Refer to section 3.5.6 of [1]. An example of this might be a CreateConnection command using RSVP, where the time to create the connection may be longer than usual because of the need to perform the network resource reservation.
情况：当事务的处理时间超出正常重试计时器时，网关将返回临时响应。交易完成后，将提供最终响应。参考[1]第3.5.6节。例如，使用RSVP的CreateConnection命令，由于需要执行网络资源预留，因此创建连接的时间可能比平时长。
Category: normal.
类别：正常。
101 - Transaction has been queued for execution
101-事务已排队等待执行
Response valid for: Any command.
响应对以下命令有效：任意命令。
Situation: As described in [1], Section 4.4.8, we assume that Call Agents and gateways conceptually maintain a queue of incoming transactions to be executed. Associated with this transaction queue is a high-water and a low-water mark. Once the queue length reaches the high-water mark, the entity should start issuing 101 provisional responses (transaction queued) until the queue length drops to the low-water mark. This applies to new transactions as well as to retransmissions. A
情况：如[1]第4.4.8节所述，我们假设呼叫代理和网关在概念上维护一个要执行的传入事务队列。与此事务队列关联的是高水位和低水位线。一旦队列长度达到高水位线，实体应开始发出101个临时响应（事务排队），直到队列长度降至低水位线。这适用于新事务以及重新传输。A.
final response will be provided later, after the transaction has completed. In this case, the Call Agent should throttle back its request rate for this gateway.
最终响应将在交易完成后提供。在这种情况下，呼叫代理应该限制其对此网关的请求速率。
Category: normal.
类别：正常。
200 - Transaction executed normally
200-正常执行事务
Response valid for: Any command (including DeleteConnection).
响应适用于：任何命令（包括DeleteConnection）。
Situation: Normal response as a result of successful execution. The 250 response code can be used to acknowledge a successful completion of a DeleteConnection command. However, a 200 response code is also appropriate.
情况：成功执行后的正常响应。250响应代码可用于确认DeleteConnection命令的成功完成。但是，200响应代码也适用。
Category: normal
类别：正常
250 - The connection was deleted
250-连接已被删除
Response valid for: DeleteConnection.
响应对有效：DeleteConnection。
Situation: Response to a successful DeleteConnection command.
情况：对成功的DeleteConnection命令的响应。
Category: normal
类别：正常
400 - Unspecified transient error
400-未指定的瞬态错误
Response valid for: Any command.
响应对以下命令有效：任意命令。
Situation: Unspecified transient error. A more specific error code should be used if one is available since this error code provides very little information. If used, some specific commentary should be included to aid in debug.
情况：未指定的瞬时错误。如果可用，则应使用更具体的错误代码，因为此错误代码提供的信息很少。如果使用，应该包括一些特定的注释以帮助调试。
Category: "Temporary Failure".
类别：“暂时性故障”。
401 - The phone is already off-hook
401-电话已经挂断了
Response valid for: NotificationRequest.
响应对有效：NotificationRequest。
Situation: This is returned in response to a request for an off-hook transition requested event when the phone is already off-hook. It is also returned when a request is made to generate a signal that has an explicit on-hook precondition in the signal definition, such as the ringing signal ("rg") in the Line package [2]. It is also returned when requesting an
情景：当手机已脱离连接时，返回此消息以响应脱离连接转换请求事件的请求。当请求生成在信号定义中具有显式挂接先决条件的信号时，例如线路包[2]中的振铃信号（“rg”）时，也会返回该信号。它也会在请求时返回
incoming off-hook/seizure indication for a Channel Associated Signaling (CAS) trunk when the incoming hook-state for that trunk is already off-hook.
当信道相关信令（CAS）中继的传入挂接状态已为摘机时，该中继的传入摘机/占用指示。
Category: "State Mismatch". If the Call Agent makes the request with a requested event indicating a different hook-state, the request should not result in this return code again.
类别：“状态不匹配”。如果调用代理使用指示不同钩子状态的请求事件发出请求，则该请求不应再次导致此返回代码。
402 - The phone is already on-hook
402-电话已经挂上了
Response valid for: NotificationRequest.
响应对有效：NotificationRequest。
Situation: This is returned in response to a request for an on-hook or hook-flash requested event when the phone is already on-hook. It is also returned when a request is made to generate a signal that has an explicit off-hook precondition in the signal definition, such as the dial tone ("dl") in the Line package [2]. It is also returned when requesting an incoming on-hook indication for a CAS trunk when the incoming hook-state for that trunk is already on-hook.
情景：当手机已经挂机时，这是对挂机请求或挂机闪存请求事件的响应。当请求生成信号定义中具有明确摘机先决条件的信号时，如线路包[2]中的拨号音（“dl”）时，也会返回该信号。当CAS中继的传入钩子状态已处于钩子状态时，在请求CAS中继的传入钩子上指示时，也会返回该消息。
Category: "State Mismatch". If the Call Agent makes the request with a requested event indicating a different hook-state, the request should not result in this error again.
类别：“状态不匹配”。如果调用代理使用指示不同挂钩状态的请求事件发出请求，则该请求不应再次导致此错误。
403 - Insufficient resources available at this time
403-目前可用资源不足
Response valid for: Any command.
响应对以下命令有效：任意命令。
Situation: This is returned if the request cannot be processed due to a temporary lack of gateway resources, such as CPU utilization, DSP resources, memory etc; however, the command may succeed at a later time when resources free up. Note that lack of network resources should not result in this code (i.e., return code 404 would be more appropriate).
情况：如果由于暂时缺乏网关资源（如CPU利用率、DSP资源、内存等）而无法处理请求，则返回此消息；但是，该命令可能会在稍后资源释放时成功。请注意，缺少网络资源不应导致此代码（即，返回代码404更合适）。
Category: "Temporary Failure".
类别：“暂时性故障”。
404 - Insufficient bandwidth at this time.
404-此时带宽不足。
Response valid for: CreateConnection, ModifyConnection.
响应适用于：CreateConnection、ModifyConnection。
Situation: This is an indication that there is not enough bandwidth available to sustain the call. It is as a result of some failed bandwidth check (could be RSVP or some other mechanism). It is possible that the Call Agent could request a
情况：这表明没有足够的带宽来维持呼叫。这是由于某些带宽检查失败（可能是RSVP或其他机制）造成的。呼叫代理可能会请求
codec requiring lower bandwidth codec and have a successful result. Alternatively, it could treat this as a "Temporary Failure" for this codec.
编解码器需要较低带宽的编解码器，并有成功的结果。或者，它可以将此视为此编解码器的“暂时故障”。
Category: "Temporary Failure". Although categorized under this general category, note that the Call Agent could apply some specific behavior (try a lower bandwidth codec) depending on policy.
类别：“暂时性故障”。尽管属于这个一般类别，但请注意，呼叫代理可以根据策略应用某些特定行为（尝试较低带宽的编解码器）。
405 - Endpoint is restarting
405-终结点正在重新启动
Response valid for: Any command.
响应对以下命令有效：任意命令。
Situation: It may be returned to requests made when the endpoint is in-service and has initiated the restart procedures (see [1], Section 4.4.6) but the procedure has not yet completed. If the request is made at a later time, it may be "successful" but may not be appropriate (because of possible state mismatch). The Call Agent should proceed after it believes the restart procedure has completed.
情况：当端点处于服务状态且已启动重启过程（参见[1]，第4.4.6节）但该过程尚未完成时，可能会返回到请求。如果请求是在以后发出的，则可能是“成功”的，但可能不合适（因为可能存在状态不匹配）。呼叫代理应在认为重新启动过程已完成后继续。
Category: "Temporary Failure"
类别：“临时故障”
406 - Transaction Timeout
406-事务超时
Response valid for: Any command.
响应对以下命令有效：任意命令。
Situation: The transaction took longer than expected and has been aborted. An example might be a transaction where a provisional response (100 response code) was returned. Following that, the gateway determined that the actual transaction was taking longer than should reasonably be expected and as a result it aborted the transaction and returned 406 as the final response.
情况：事务花费的时间超过预期，已中止。例如，返回临时响应（100响应代码）的事务。随后，网关确定实际事务所用的时间比合理预期的时间长，因此它中止了事务并返回406作为最终响应。
Category: "Temporary Failure". If this error code is returned repeatedly, it could indicate a more serious problem.
类别：“暂时性故障”。如果反复返回此错误代码，则可能表明存在更严重的问题。
407 - Transaction aborted by some external action.
407-某些外部操作中止了事务。
Response valid for: Any command.
响应对以下命令有效：任意命令。
Situation: This is returned to indicate cancellation of a pending request (see [1] Section 4.4.4). For example, DeleteConnection is received while processing a CreateConnection or ModifyConnection. Also, if either a ModifyConnection,
情况：返回该值表示取消了挂起的请求（参见[1]第4.4.4节）。例如，在处理CreateConnection或ModifyConnection时接收DeleteConnection。此外，如果修改连接，
NotificationRequest, or EndpointConfiguration command is in progress, and the same command is received with a different transaction Id, 407 will be returned.
NotificationRequest或EndpointConfiguration命令正在执行中，如果接收到具有不同事务Id的相同命令，将返回407。
Category: none (specific situation and behavior).
类别：无（具体情况和行为）。
409 - Internal overload
409-内部过载
Response valid for: Any command.
响应对以下命令有效：任意命令。
Situation: Gateway is overloaded (e.g., too many requests per second from the Call Agent) and is unable to process any more transactions at this time. In this case, the Call Agent SHOULD throttle back its request rate for this gateway as described in [1], Section 4.4.8.
情况：网关过载（例如，每秒来自呼叫代理的请求太多），此时无法处理更多事务。在这种情况下，呼叫代理应按照第4.4.8节[1]中所述，限制其对该网关的请求速率。
Category: "Temporary Failure". Note that although the Call Agent behavior with respect to the call being set up corresponds to this general category, there is some specific Call Agent behavior implied as well (i.e., the Call Agent throttling back).
类别：“暂时性故障”。请注意，尽管与正在设置的调用相关的调用代理行为对应于此一般类别，但也隐含了一些特定的调用代理行为（即，调用代理节流）。
410 - No endpoint available
410-没有可用的端点
Response valid for: CreateConnection using an "any of" wildcard.
响应适用于：使用“任意”通配符创建连接。
Situation: A CreateConnection request was made with an "any of" ("$") wildcard and no endpoint was available to execute the request. As described in [1], Section 2.3.5, when the "any of" wildcard is used with the CreateConnection command, the endpoint assigned MUST be in-service and MUST NOT already have any connections on it.
情况：CreateConnection请求是使用“any of”（“$”）通配符发出的，没有端点可用于执行该请求。如[1]第2.3.5节所述，当CreateConnection命令使用“any of”通配符时，所分配的端点必须在服务中，并且不得已有任何连接。
Category: none (specific situation and behavior).
类别：无（具体情况和行为）。
500 - Endpoint unknown
500-端点未知
Response valid for: Any command.
响应对以下命令有效：任意命令。
Situation: There is no endpoint matching the EndpointId provided with the command. This could be the result of a provisioning mismatch between the Call Agent and the gateway or it could be because a card was removed from the gateway so that the endpoint is no longer available (in which case a RestartInProgress should be received, although the Call Agent cannot depend on this). Note that the endpoint is not just out-of-service (in which case 501 would be used); it is completely unknown/unavailable to the MGCP.
情况：没有与命令提供的EndpointId匹配的端点。这可能是由于呼叫代理和网关之间的配置不匹配造成的，也可能是因为从网关中移除了一张卡，因此端点不再可用（在这种情况下，应接收重新启动进程，尽管呼叫代理不能依赖于此）。请注意，端点不仅仅是停止服务（在这种情况下，将使用501）；MGCP完全不知道/不可用。
Category: "Provisioning Mismatch".
类别：“配置不匹配”。
501 - Endpoint is not ready or is out of service
501-终结点未就绪或已停止服务
Response valid for: Any command.
响应对以下命令有效：任意命令。
Situation: This is returned if the endpoint is in a permanent "not ready" state. This includes maintenance states such as out-of-service. Note that an endpoint that has initiated the restart procedure is in-service, and hence should not use this return code, even if the restart procedure has not yet completed (see [1], Section 4.4.5).
情况：如果端点处于永久的“未就绪”状态，则返回此消息。这包括维护状态，如停用。请注意，启动重新启动过程的端点处于服务中，因此即使重新启动过程尚未完成，也不应使用此返回代码（请参见[1]，第4.4.5节）。
Category: "Service Failure".
类别：“服务故障”。
502 - Insufficient resources (permanent).
502-资源不足（永久性）。
Response valid for: Any command.
响应对以下命令有效：任意命令。
Situation: This is returned when the endpoint does not have sufficient resources and future requests on this endpoint are expected to fail, meaning some resources dedicated to the endpoint are broken (e.g., return code 529 - "hardware failure" might be a more specific indication). For situations where resources may become available in the future (i.e., resources are pooled and not available at the present time), return code 403 should be used instead.
情况：当端点没有足够的资源，并且该端点上的未来请求预计将失败时，将返回此消息，这意味着一些专用于该端点的资源已中断（例如，返回代码529-“硬件故障”可能是更具体的指示）。对于将来可能变得可用的资源的情况（即，资源被汇集且当前不可用），应使用返回代码403。
Category: "Service Failure".
类别：“服务故障”。
503 - "All of" wildcard too complicated.
503-“所有”通配符太复杂了。
Response valid for: Any command.
响应对以下命令有效：任意命令。
Situation: This is returned when the wildcard convention used in the request is understood, but the requested command cannot be processed with the specified wildcarding. An example of this would be a NotificationRequest with a request such that a failure would make it too difficult to roll back the state of all the endpoints to what they were prior to the request.
情况：当理解请求中使用的通配符约定，但无法使用指定的通配符处理请求的命令时，将返回此消息。这方面的一个例子是NotificationRequest，其请求的失败会使将所有端点的状态回滚到请求之前的状态变得非常困难。
Category: Normally treated as a "Provisioning Mismatch". Note however, that the Call Agent could treat it differently by recovering with some specific behavior (e.g., generate a number of individual requests without wildcards instead of a single one with the wildcard).
类别：通常被视为“配置不匹配”。但是请注意，调用代理可以通过使用某些特定行为进行恢复（例如，生成多个不带通配符的单独请求，而不是一个带通配符的请求）来对其进行不同的处理。
504 - Unknown or unsupported command.
504-未知或不支持的命令。
Response valid for: Any unknown command.
响应对以下命令有效：任何未知命令。
Situation: A command was requested other than those specified in the MGCP specification [1], and the command is not supported.
情况：请求的命令不是MGCP规范[1]中指定的命令，该命令不受支持。
Category: "Provisioning Mismatch".
类别：“配置不匹配”。
505 - Unsupported remote connection descriptor.
505-不支持的远程连接描述符。
Response valid for: CreateConnection, ModifyConnection.
响应适用于：CreateConnection、ModifyConnection。
Situation: One or more mandatory parameters or values in the RemoteConnectionDescriptor are not supported by the gateway. Note that, per [3], unsupported attribute lines must be ignored and hence should not result in any errors.
情况：网关不支持RemoteConnectionDescriptor中的一个或多个必需参数或值。请注意，根据[3]，不支持的属性行必须忽略，因此不应导致任何错误。
Category: "Remote Connection Descriptor Error".
类别：“远程连接描述符错误”。
506 - Inability to satisfy both local connection options and remote connection descriptor simultaneously.
506-无法同时满足本地连接选项和远程连接描述符。
Response valid for: CreateConnection, ModifyConnection.
响应适用于：CreateConnection、ModifyConnection。
Situation: The LocalConnectionOptions and RemoteConnectionDescriptor contain one or more mandatory parameters or values that conflict with each other and/or cannot be supported at the same time (except for codec negotiation failure - see error code 534).
情况：LocalConnectionOptions和RemoteConnectionDescriptor包含一个或多个相互冲突和/或无法同时支持的强制参数或值（编解码器协商失败除外-请参阅错误代码534）。
Category: "Remote Connection Descriptor Error".
类别：“远程连接描述符错误”。
507 - Unsupported Functionality. Note that this error code SHOULD only be used if there is no other more specific error code for the unsupported functionality.
507-不支持的功能。请注意，仅当不支持的功能没有其他更具体的错误代码时，才应使用此错误代码。
Response valid for: Any command.
响应对以下命令有效：任意命令。
Situation: Any situation where a request from the Call Agent is not supported by the gateway - beyond the situations already covered by other more specific return codes.
情况：网关不支持来自呼叫代理的请求的任何情况-其他更具体的返回代码已经涵盖的情况除外。
Category: "Provisioning Mismatch".
类别：“配置不匹配”。
508 - Unknown or unsupported quarantine handling.
508-未知或不支持的隔离处理。
Response valid for: NotificationRequest.
响应对有效：NotificationRequest。
Situation: The endpoint does not support or does not recognize the requested quarantine handling.
情况：终结点不支持或不识别请求的隔离处理。
Category: "Provisioning Mismatch".
类别：“配置不匹配”。
509 - Error in RemoteConnectionDescriptor
509-RemoteConnectionDescriptor中的错误
Response valid for: CreateConnection, ModifyConnection.
响应适用于：CreateConnection、ModifyConnection。
Situation: There is a syntax or semantic error in the Remote Connection Descriptor. For example, there is no IP address for an RTP media stream.
情况：远程连接描述符中存在语法或语义错误。例如，RTP媒体流没有IP地址。
Category: "Remote Connection Descriptor Error".
类别：“远程连接描述符错误”。
510 - Protocol error
510-协议错误
Response valid for: Any command.
响应对以下命令有效：任意命令。
Situation: Some unspecified protocol error was detected. Gateways should use this error as a last resort since it provides very little information. If used, some specific commentary should be included to aid in debug.
情况：检测到一些未指定的协议错误。网关应使用此错误作为最后手段，因为它提供的信息很少。如果使用，应该包括一些特定的注释以帮助调试。
Category: "Provisioning Mismatch".
类别：“配置不匹配”。
511 - Unrecognized parameter extension.
511-无法识别的参数扩展。
Response valid for: Any command.
响应对以下命令有效：任意命令。
Situation: It is returned if the requested command contains an unrecognized mandatory parameter extension ("X+"). In MGCP 1.0, this specifically refers to unrecognized parameters, since other error codes are available for unrecognized connection modes (517), unrecognized packages (518), unrecognized local connection options (541), etc.
情况：如果请求的命令包含无法识别的强制参数扩展（“X+”），则返回该命令。在MGCP 1.0中，这是指无法识别的参数，因为其他错误代码可用于无法识别的连接模式（517）、无法识别的包（518）、无法识别的本地连接选项（541）等。
Category: "Provisioning Mismatch".
类别：“配置不匹配”。
512 - Gateway not equipped to detect one of the requested events.
512-网关未配备以检测请求的事件之一。
Response valid for: NotificationRequest.
响应对有效：NotificationRequest。
Situation: A valid event was requested however the gateway is not equipped to detect this event (i.e., the package is only implemented partially). Of course, such an implementation would not conform to [1]. Note that if an invalid event was requested, i.e., an event not defined in the relevant package,
情况：请求了一个有效的事件，但是网关没有配备检测该事件的设备（即，包仅部分实现）。当然，这样的实现不符合[1]。请注意，如果请求了无效事件，即相关包中未定义的事件，
then error code 522 should be used. Also note, that if the package is unknown or unsupported, then error code 518 should be used.
然后应使用错误代码522。还要注意，如果包未知或不受支持，则应使用错误代码518。
Category: "Provisioning Mismatch".
类别：“配置不匹配”。
513 - gateway is not equipped to generate one of the requested signals.
513-网关未配备用于生成一个请求的信号。
Response valid for: NotificationRequest.
响应对有效：NotificationRequest。
Situation: A valid signal was requested, however the gateway is not equipped to generate this signal (i.e., the package is only implemented partially). Of course, such an implementation would not conform to [1]. Note that if an invalid signal was requested, i.e., a signal not defined in the relevant package, then error code 522 should be used. Also note, that if the package is unknown or unsupported, then error code 518 should be used.
情况：请求了一个有效的信号，但网关未配备生成该信号的设备（即，该包仅部分实现）。当然，这样的实现不符合[1]。请注意，如果请求了无效信号，即相关软件包中未定义的信号，则应使用错误代码522。还要注意，如果包未知或不受支持，则应使用错误代码518。
Category: "Provisioning Mismatch".
类别：“配置不匹配”。
514 - The gateway cannot send the specified announcement.
514-网关无法发送指定的公告。
Response valid for: NotificationRequest with a request for an announcement to be played.
响应适用于：NotificationRequest，请求播放公告。
Situation: This is a specific situation with respect to playing announcements on an endpoint or connection associated with the endpoint. Error code 538 could be used instead.
情境：这是关于在端点或与端点关联的连接上播放公告的特定情境。可以改用错误代码538。
Category: "Provisioning Mismatch".
类别：“配置不匹配”。
515 - Incorrect connection-id.
515-不正确的连接id。
Response valid for: CreateConnection, ModifyConnection, DeleteConnection, NotificationRequest, AuditConnection.
响应适用于：CreateConnection、ModifyConnection、DeleteConnection、NotificationRequest、AuditConnection。
Situation: An unknown connection-id has been specified. It is possible that the connection has already been deleted. It should be noted that a connection-id can also supplied with events and signals (e.g., "S: L/rt@connId"). Note that a mismatch between connection-id and call-id should use error code 516.
情况：指定了未知的连接id。连接可能已被删除。应该注意的是，连接id还可以提供事件和信号（例如，“S:L/rt@connId"). 请注意，连接id和呼叫id之间的不匹配应使用错误代码516。
Category: "State Mismatch".
类别：“状态不匹配”。
516 - Unknown or incorrect call-id.
516-未知或不正确的呼叫id。
Response valid for: ModifyConnection, DeleteConnection.
响应适用于：ModifyConnection、DeleteConnection。
Situation: Unknown call-id, or the call-id supplied is incorrect (e.g., connection-id not associated with this call-id).
情况：未知的呼叫id，或提供的呼叫id不正确（例如，连接id与此呼叫id不关联）。
Category: "State Mismatch".
类别：“状态不匹配”。
517 - Invalid or unsupported mode.
517-无效或不支持的模式。
Response valid for: CreateConnection, ModifyConnection.
响应适用于：CreateConnection、ModifyConnection。
Situation: This is returned if the command specifies a connection mode that the endpoint does not support (note that not all endpoints will support all modes). Note that if the unsupported mode is an extension connection mode, error code 518 (unsupported package) should be used instead.
情况：如果命令指定了端点不支持的连接模式（请注意，并非所有端点都支持所有模式），则返回此消息。请注意，如果不支持的模式是扩展连接模式，则应改用错误代码518（不支持的包）。
Category: "Provisioning Mismatch".
类别：“配置不匹配”。
518 - Unsupported or unknown package.
518-不支持或未知的程序包。
Response valid for: Any command
响应对以下命令有效：任意命令
Situation: A package name included in a request is not supported (or unknown). Note that the package name may be a prefix to an event or other things (e.g., a parameter) as defined in [1]. Note that it is recommended to include a PackageList parameter with a list of supported packages in the response.
情况：请求中包含的包名称不受支持（或未知）。请注意，包名称可以是[1]中定义的事件或其他事物（例如，参数）的前缀。请注意，建议在响应中包含PackageList参数和支持的包列表。
Category: "Provisioning Mismatch".
类别：“配置不匹配”。
519 - Endpoint does not have a digit map.
519-端点没有数字映射。
Response valid for: NotificationRequest.
响应对有效：NotificationRequest。
Situation: Request was made to detect digits based on a digit map and the gateway does not have a digit map.
情况：请求根据数字映射检测数字，但网关没有数字映射。
Category: "State Mismatch". The Call Agent needs to send down a digit map in order to continue with the call.
类别：“状态不匹配”。呼叫代理需要发送数字映射才能继续呼叫。
520 - Endpoint is restarting.
520-终结点正在重新启动。
Situation: This is normally a transient error in which error code 405 SHOULD be used. Gateways SHOULD not use this error code unless there is some relevant situation that warrants the category of "Service Failure". Note that this was included in [1] only to maintain backwards compatibility with previous releases of the MGCP specification.
情况：这通常是一个瞬态错误，应使用错误代码405。网关不应使用此错误代码，除非存在某些相关情况，可以证明属于“服务故障”类别。请注意，[1]中包含这一点只是为了保持与MGCP规范早期版本的向后兼容性。
Category: If it is returned, this return code will be treated as category "Service Failure", i.e., as if this endpoint is out-of-service.
类别：如果返回，则此返回代码将被视为类别“服务失败”，即，就好像此端点已停止服务一样。
521 - Endpoint re-directed to another Call Agent.
521-端点重新定向到另一个呼叫代理。
Response valid for: RestartInProgress.
响应适用于：重新启动进程。
Situation: A RestartInProgress command was sent to the Call Agent and the Call Agent returns this return code along with a NotifiedEntity parameter pointing to another Call Agent. The gateway then sends a new RestartInProgress command to the Call Agent specified in the Notified Entity.
情况：向调用代理发送了RestartInProgress命令，调用代理返回此返回代码以及指向另一个调用代理的NotifiedEntity参数。网关然后向通知实体中指定的呼叫代理发送新的RestartInProgress命令。
Category: none (specific situation and behavior).
类别：无（具体情况和行为）。
522 - No such event or signal.
522-无此类事件或信号。
Response valid for: NotificationRequest.
响应对有效：NotificationRequest。
Situation: This is returned if the requested event/signal name is not registered with this package. If on the other hand the signal or event is part of the package but is not supported by the gateway, then return code 512 or 513 SHOULD be provided instead. If the package is not supported, return code 518 SHOULD be returned.
情况：如果请求的事件/信号名称未在此包中注册，则返回此消息。另一方面，如果信号或事件是包的一部分，但网关不支持，则应提供返回代码512或513。如果不支持该包，则应返回返回代码518。
Category: "Provisioning Mismatch".
类别：“配置不匹配”。
523 - Unknown action or illegal combination of actions.
523-未知行动或行动的非法组合。
Response valid for: NotificationRequest with one or more requested events.
响应适用于：NotificationRequest和一个或多个请求的事件。
Situation: Request was made with a requested event(s) that included an action or actions defined in [1] that are either unknown, unsupported or an illegal combination as indicated in section 2.3.3 of [1]. Note that unsupported extension actions should generate error code 518 (unsupported package).
情况：请求是通过请求的事件发出的，该事件包括[1]中定义的未知、不受支持或非法组合的一个或多个操作，如[1]第2.3.3节所述。请注意，不支持的扩展操作应生成错误代码518（不支持的包）。
Category: "Provisioning Mismatch".
类别：“配置不匹配”。
524 - Internal inconsistency in Local Connection Options
524-本地连接选项内部不一致
Response valid for: CreateConnection, ModifyConnection.
响应适用于：CreateConnection、ModifyConnection。
Situation: This is returned if one or more of the LocalConnectionOptions (LCO) parameters are coded with values that are not consistent with each other (e.g., other LCO parameters inconsistent with the network type).
情况：如果一个或多个LocalConnectionOptions（LCO）参数的编码值彼此不一致（例如，与网络类型不一致的其他LCO参数），则返回此消息。
Category: "Provisioning Mismatch".
类别：“配置不匹配”。
525 - Unknown extension in Local Connection Options.
525-本地连接选项中的未知扩展。
Response valid for: CreateConnection, ModifyConnection.
响应适用于：CreateConnection、ModifyConnection。
Situation: This is returned if the request contains a Local Connection Option with one or more unrecognized mandatory ("x+") extensions. Note that unsupported package extensions should use error code 518 (unsupported package) instead.
情况：如果请求包含具有一个或多个无法识别的强制（“x+”）扩展名的本地连接选项，则返回此选项。请注意，不支持的包扩展应该使用错误代码518（不支持的包）。
Category: "Provisioning Mismatch".
类别：“配置不匹配”。
526 - Insufficient bandwidth
526-带宽不足
Response valid for: CreateConnection, ModifyConnection.
响应适用于：CreateConnection、ModifyConnection。
Situation: In most cases where there is insufficient bandwidth, a 404 return code should be used. 526 would be used in cases where future requests are destined to fail. An example might be a very restricted bandwidth case, where there is not enough bandwidth available for the codec requested even for a single endpoint. Making a request with the same codec in the future will fail. However, making a request for some other codec (with a higher degree of compression) may pass. For cases, where the bandwidth is pooled over multiple endpoints and could free up at some future time (because an endpoint becomes inactive), then 404 is more appropriate.
情况：在带宽不足的大多数情况下，应该使用404返回码。526将用于将来的请求注定失败的情况。例如，带宽可能非常有限，即使对于单个端点，也没有足够的带宽可用于请求的编解码器。将来使用相同的编解码器发出请求将失败。但是，请求某些其他编解码器（具有更高的压缩程度）可能会通过。对于带宽集中在多个端点上并可能在未来某个时间释放（因为端点变为非活动）的情况，404更合适。
Category: If it is returned, this return code will be treated as category "Provisioning Mismatch", e.g., the codec was incorrectly provisioned for the bandwidth available.
类别：如果返回，此返回代码将被视为类别“配置不匹配”，例如，编解码器未正确配置可用带宽。
527 - Missing RemoteConnectionDescriptor.
527-缺少RemoteConnectionDescriptor。
Response valid for: CreateConnection, ModifyConnection, NotificationRequest.
响应对以下各项有效：CreateConnection、ModifyConnection、NotificationRequest。
Situation: This is returned if the connection has not yet received a RemoteConnectionDescriptor when one is required to support the request. This can for example happen if a connection is attempted to be placed in "send/receive mode", or if a signal is applied on a connection.
情况：如果连接尚未接收到RemoteConnectionDescriptor，则返回此消息，但需要一个RemoteConnectionDescriptor来支持请求。例如，如果试图将连接置于“发送/接收模式”，或在连接上应用信号，则可能发生这种情况。
Category: "Remote Connection Descriptor Error" in the case where the other end did not provide a connection descriptor. Alternatively, if this is an initial request made by a Call Agent (such there is no remote connection descriptor), then this is a "State Mismatch" problem.
类别：另一端未提供连接描述符的情况下的“远程连接描述符错误”。或者，如果这是呼叫代理发出的初始请求（例如没有远程连接描述符），则这是一个“状态不匹配”问题。
528 -Incompatible protocol version
528-不兼容的协议版本
Response valid for: Any command.
响应对以下命令有效：任意命令。
Situation: A command was received with a protocol version that was not supported.
情况：接收到协议版本不受支持的命令。
Category: "Provisioning Mismatch". This could also be treated as a "State Mismatch" problem if the there is a recovery mechanism (e.g., Call Agent recognizes the protocol version mismatch and switches to the correct protocol version)
类别：“配置不匹配”。如果存在恢复机制（例如，呼叫代理识别协议版本不匹配并切换到正确的协议版本），则这也可能被视为“状态不匹配”问题
529 - Internal Hardware Error.
529-内部硬件错误。
Response valid for: Any command.
响应对以下命令有效：任意命令。
Situation: A hardware fault occurred during the execution of a command such that repeating this command will result in a failure indication once again. This is a slightly more specific error code than error 502, although more commentary should be provided (for debug purposes) if possible.
情况：在执行命令期间发生硬件故障，重复此命令将导致再次出现故障指示。这是一个比错误502稍微更具体的错误代码，不过如果可能的话，应该提供更多的注释（用于调试目的）。
Category: "Service Failure".
类别：“服务故障”。
530 - CAS Signaling Protocol Error.
530-CAS信令协议错误。
Response valid for: NotificationRequest.
响应对有效：NotificationRequest。
Situation: This is specific to Channel Associated Signaling (CAS) interfaces. A typical example might be an attempt to outpulse digits failed for some reason.
情况：这特定于信道相关信令（CAS）接口。一个典型的例子可能是由于某种原因输出数字失败。
Category: none (specific situation and behavior).
类别：无（具体情况和行为）。
531 - Failure of a grouping of trunks (e.g., facility failure)
531-一组中继的故障（例如，设施故障）
Response valid for: CreateConnection, ModifyConnection, NotificationRequest.
响应对以下各项有效：CreateConnection、ModifyConnection、NotificationRequest。
Situation: Request made to an endpoint that has a failed trunk connection (e.g., T1 or E1 failed). Note that an RSIP should have been sent as a result of the facility failure. This is a more specific response than return code 501.
情况：向主干连接失败（例如T1或E1失败）的端点发出的请求。请注意，由于设施故障，应发送RSIP。这是比返回代码501更具体的响应。
Category: "Service Failure".
类别：“服务故障”。
532 - Unsupported value(s) in Local Connection Options.
532-本地连接选项中不支持的值。
Response valid for: CreateConnection, ModifyConnection.
响应适用于：CreateConnection、ModifyConnection。
Situation: This is returned if one or more of the LocalConnectionOptions parameters are coded with a value that the gateway does not support.
情况：如果一个或多个LocalConnectionOptions参数使用网关不支持的值进行编码，则返回此消息。
Category: "Provisioning Mismatch".
类别：“配置不匹配”。
533 - Response too large
533-响应太大
Response valid for: Any command.
响应对以下命令有效：任意命令。
Situation: This would only be likely to occur in the case of an audit where the maximum response packet size would end up being too large.
情况：只有在最大响应数据包大小过大的审计情况下，才可能发生这种情况。
Category: none (specific situation and behavior).
类别：无（具体情况和行为）。
534 - Codec negotiation failure
534-编解码器协商失败
Response valid for: CreateConnection, ModifyConnection.
响应适用于：CreateConnection、ModifyConnection。
Situation: The intersection between the list of codecs that the gateway supports, the codecs allowed by the local connection options and the codecs supplied in the Remote Connection Descriptor (if provided) is empty.
情况：网关支持的编解码器列表、本地连接选项允许的编解码器和远程连接描述符（如果提供）中提供的编解码器之间的交集为空。
Category: "Provisioning Mismatch" if the error resulted from an empty approved list of codes as described in [1], Section 2.6). "Remote Connection Descriptor Error" if the error resulted from an empty negotiated list of codecs, as described in [1], Section 2.6.
类别：“供应不匹配”，如果错误是由[1]第2.6节所述的空批准代码列表引起的。“远程连接描述符错误”，如果错误是由空的编解码器协商列表导致的，如第2.6节[1]中所述。
535 - Packetization period not supported
535-不支持打包期间
Response valid for: CreateConnection, ModifyConnection.
响应适用于：CreateConnection、ModifyConnection。
Situation: Normally this error should not be generated since if the gateway is unable to support the packetization period specified in the local connection options for the codec indicated, it should follow the behavior specified in [1] (which is to pick an appropriate value rather than failing the request).
情况：通常不应生成此错误，因为如果网关无法支持在所示编解码器的本地连接选项中指定的打包周期，则应遵循[1]中指定的行为（即选择适当的值而不是请求失败）。
Category: "none".
类别：“无”。
536 - Unknown or unsupported Restart Method
536-未知或不支持的重新启动方法
Response valid for: RestartInProgress.
响应适用于：重新启动进程。
Situation: This error is generated by the Call Agent if it receives a RestartInProgress command with an unsupported restart method. Note that if the restart method is an extension restart method, error code 518 (unsupported package) should be used instead.
情况：如果调用代理接收到带有不受支持的重新启动方法的RestartInProgress命令，则会生成此错误。请注意，如果重新启动方法是扩展重新启动方法，则应使用错误代码518（不支持的包）。
Category: "Provisioning Mismatch".
类别：“配置不匹配”。
537 - Unknown or unsupported digit map extension
537-未知或不支持的数字映射扩展
Response valid for: NotificationRequest.
响应对有效：NotificationRequest。
Situation: Digit map letter in the digit map unknown or unsupported. Note that this code does apply to extension digit map letters as well.
情况：数字映射中的数字映射字母未知或不受支持。请注意，此代码也适用于分机数字地图字母。
Category: "Provisioning Mismatch".
类别：“配置不匹配”。
538 - Event/signal parameter error
538-事件/信号参数错误
Response valid for: NotificationRequest.
响应对有效：NotificationRequest。
Situation: It is returned if the event/signal parameter is in error or not supported. If the event/signal or a package is not supported, then one of 512, 513, 518, or 522 should be used instead.
情况：如果事件/信号参数出错或不受支持，则返回。如果不支持事件/信号或包，则应使用512、513、518或522中的一个。
Category: "Provisioning Mismatch".
类别：“配置不匹配”。
539 - Invalid or unsupported command parameter
539-命令参数无效或不受支持
Response valid for: Any command.
响应对以下命令有效：任意命令。
Situation: This is returned if the command contains an invalid or unsupported parameter, which is neither a package (which would use return code 518) nor vendor specific extension (which would use return code 511). For example, if an endpoint does not support the BearerInformation parameter of the EndpointConfiguration command, this return code could be used. Of course, such an implementation would not conform to [1].
情况：如果命令包含无效或不受支持的参数，则返回该参数，该参数既不是包（使用返回代码518），也不是特定于供应商的扩展名（使用返回代码511）。例如，如果端点不支持EndpointConfiguration命令的BearerInformation参数，则可以使用此返回代码。当然，这样的实现不符合[1]。
Category: "Provisioning Mismatch".
类别：“配置不匹配”。
540 - Per endpoint connection limit exceeded
540-超出了每个端点连接的限制
Response valid for: CreateConnection.
响应对以下对象有效：CreateConnection。
Situation: A CreateConnection command was made, but the gateway cannot support any additional connections on that endpoint.
情况：发出了CreateConnection命令，但网关无法支持该端点上的任何其他连接。
Category: "State Mismatch".
类别：“状态不匹配”。
541 - Invalid or unsupported Local Connection Options
541-无效或不支持的本地连接选项
Response valid for: CreateConnection, ModifyConnection.
响应适用于：CreateConnection、ModifyConnection。
Situation: This is returned if the command contains an invalid or unsupported LocalConnectionOption, which is neither a package (which would use return code 518) nor vendor specific extension (which would use return code 511).
情况：如果命令包含无效或不受支持的LocalConnectionOption，则返回该选项，该选项既不是包（使用返回代码518），也不是特定于供应商的扩展（使用返回代码511）。
Category: "Provisioning Mismatch".
类别：“配置不匹配”。
A summary of the categories of the various error codes is included in the following table. This information is also repeated in the detailed error descriptions in the next section.
下表汇总了各种错误代码的类别。在下一节的详细错误描述中也会重复此信息。
------------------------------------------------------------------
| Category | Return Codes |
|-------------|----------------------------------------------------|
| normal | 000, 100, 101, 200, 250 |
|-------------|----------------------------------------------------|
| none | 405, 407, 410, 510, 521, 530, 533, 535 |
|-------------|----------------------------------------------------|
| "Service | 501, 502, 520, 529, 531 |
| Failure" | |
|-------------|----------------------------------------------------|
|"Provisioning| 500, 503*, 504, 507, 508, 510, 511, 512, 513, 514, |
| Mismatch" | 517, 518, 522, 523, 524, 525, 526, 528*, 532, 534*,|
| | 536, 537, 538, 539, 541 |
|-------------|----------------------------------------------------|
| "Temporary | 400, 403, 404*, 405, 406, 409 |
| Failure" | |
|-------------|----------------------------------------------------|
| "State | 401, 402, 515, 516, 519, 540 |
| Mismatch" | |
|-------------|----------------------------------------------------|
| "Remote | 505, 506, 509, 527* |
| Connection | |
| Descriptor | |
| Error" | |
------------------------------------------------------------------
------------------------------------------------------------------
| Category | Return Codes |
|-------------|----------------------------------------------------|
| normal | 000, 100, 101, 200, 250 |
|-------------|----------------------------------------------------|
| none | 405, 407, 410, 510, 521, 530, 533, 535 |
|-------------|----------------------------------------------------|
| "Service | 501, 502, 520, 529, 531 |
| Failure" | |
|-------------|----------------------------------------------------|
|"Provisioning| 500, 503*, 504, 507, 508, 510, 511, 512, 513, 514, |
| Mismatch" | 517, 518, 522, 523, 524, 525, 526, 528*, 532, 534*,|
| | 536, 537, 538, 539, 541 |
|-------------|----------------------------------------------------|
| "Temporary | 400, 403, 404*, 405, 406, 409 |
| Failure" | |
|-------------|----------------------------------------------------|
| "State | 401, 402, 515, 516, 519, 540 |
| Mismatch" | |
|-------------|----------------------------------------------------|
| "Remote | 505, 506, 509, 527* |
| Connection | |
| Descriptor | |
| Error" | |
------------------------------------------------------------------
Notes:
笔记：
* 404: may be treated as a "Temporary Failure", but specific behavior is possible (e.g., trying an alternate codec with lower bandwidth requirement rather than failing this call).
* 404：可能被视为“暂时故障”，但具体行为是可能的（例如，尝试带宽要求较低的替代编解码器，而不是失败此呼叫）。
* 503: rather than treating this as a "Provisioning Mismatch", it is possible for the Call Agent to recover from this error.
* 503：呼叫代理可以从该错误中恢复，而不是将其视为“配置不匹配”。
* 527: See the detailed description for this error code in section 2.2. This could be treated as a "State Mismatch" depending on the circumstances.
* 527：有关此错误代码的详细说明，请参见第2.2节。根据具体情况，这可能被视为“状态不匹配”。
* 528: See the detailed description for this error code in section 2.2. This could be treated as a "State Mismatch" depending on the circumstances.
* 528：有关此错误代码的详细说明，请参见第2.2节。根据具体情况，这可能被视为“状态不匹配”。
* 534: See the note on error code 534 in the detailed description section (2.2) of this document (may be treated as a "Remote Connection Descriptor Error" if no local connection options were supplied).
* 534：请参阅本文档详细说明部分（2.2）中关于错误代码534的说明（如果未提供本地连接选项，则可能被视为“远程连接描述符错误”）。
This section provides additional guidelines to Gateway and Call Agent developers.
本节为网关和呼叫代理开发人员提供了其他指南。
The following guidelines are recommended for gateway implementations:
建议网关实施遵循以下准则：
* For uncategorized return codes (category "none") that involve specific situations, gateways should make sure they do an accurate mapping between the situation and the return code.
* 对于涉及特定情况的未分类返回代码（类别“无”），网关应确保它们在情况和返回代码之间进行准确映射。
* Also for category "State Mismatch", it is equally important that the situation (and state) is accurately mapped to the specific error code.
* 同样对于“状态不匹配”类别，情况（和状态）准确映射到特定错误代码也同样重要。
* For situations similar to those involving return codes in "Service Failure", Provisioning Mismatch", "Temporary Failure" and "Remote Connection Descriptor Error" categories, the gateway should make sure that it uses a return code in the correct category.
* 对于类似于涉及“服务故障”、“配置不匹配”、“临时故障”和“远程连接描述符错误”类别中的返回码的情况，网关应确保使用正确类别中的返回码。
* MGCP allows additional commentary to be included with the return code. It is important that the gateway includes more specific information concerning the situation for debug purposes.
* MGCP允许在返回代码中包含附加注释。出于调试目的，网关应包含有关情况的更具体信息，这一点很重要。
* It is recommended that return codes 502, 520 and 526 not be used unless there is something that makes these permanent situations. As indicated in the detailed description of these return codes, 403, 405 and 404 respectively are more appropriate in almost all situations. If a gateway presently uses 502, 520 and 526 for temporary situations and expects to upgrade to 403, 405 and 404, the gateway should refrain from using 502, 520 and 526 for some other use immediately after the upgrade. This is to avoid problems where a Call Agent is expected to treat the same error code in two different ways, e.g., 403 is a category "Temporary Failure" which requires a different Call Agent behavior from 502 which is in category "Service Failure".
* 建议不要使用返回代码502、520和526，除非存在导致这些永久性情况的因素。如这些返回代码的详细描述所示，403、405和404分别在几乎所有情况下都更合适。如果网关目前将502、520和526用于临时情况，并期望升级到403、405和404，则网关应避免在升级后立即将502、520和526用于其他用途。这是为了避免呼叫代理预期以两种不同的方式处理相同错误代码的问题，例如，403是“临时故障”类别，需要与502不同的呼叫代理行为，502属于“服务故障”类别。
The following guidelines are recommended for gateway implementations:
建议网关实施遵循以下准则：
* Call Agents should handle return codes they do not recognize (or do not expect) based on the first digit in the return code as outlined in [1].
* 呼叫代理应根据[1]中所述的返回码中的第一位数字来处理他们无法识别（或不期望）的返回码。
* For categories "Service Failure", "Provisioning Mismatch", "Temporary Failure", and "Remote Connection Descriptor Error", Call Agents are expected to treat return codes that are within the same category in the same way (i.e., make the same decision, based on the return code and other state information available to them).
* 对于“服务故障”、“配置不匹配”、“临时故障”和“远程连接描述符错误”类别，呼叫代理应以相同的方式处理同一类别内的返回代码（即，根据返回代码和其他可用状态信息做出相同的决定）。
* Because there was little guidance given for return codes 502, 520 and 526 in RFC 2705 [4], Call Agents may have to treat these as 403, 405 and 404 respectively for gateways that have not been updated according to [1] and these recommendations. The gateway implementer should be consulted for information on the gateway behavior for (now and in the future) for these return codes (i.e., it may be that return codes 502, 520 and 526 are presently used incorrectly but will be replaced with 403, 405 and 404 in the future).
* 由于RFC 2705[4]中对返回代码502、520和526给出的指导很少，呼叫代理可能不得不将这些代码分别视为403、405和404，用于未根据[1]和这些建议进行更新的网关。对于这些返回码（即，可能返回码502、520和526当前使用不正确，但将来将被403、405和404替换），应咨询网关实现者以获取关于（现在和将来）这些返回码的网关行为的信息。
This document merely provides a convenient way to categorize MGCP return codes in order to facilitate decisions related to failure conditions; it does not impact MGCP security in any way.
本文件仅提供了对MGCP返回代码进行分类的方便方法，以便于做出与故障条件相关的决策；它不会以任何方式影响MGCP安全性。
Thanks also to Kevin Miller, Joe Stone, Flemming Andreasen, Bob Biskner for input contributions used in this document.
还要感谢Kevin Miller、Joe Stone、Flemming Andreasen和Bob Biskner在本文档中提供的投入。
[1] Andreasen, F. and B. Foster, "Media Gateway Control Protocol (MGCP) Version 1.0", RFC 3435, January 2003.
[1] Andreasen，F.和B.Foster，“媒体网关控制协议（MGCP）1.0版”，RFC 3435，2003年1月。
[2] Foster, B. and F. Andreasen, "Basic Media Gateway Control Protocol (MGCP) Packages", RFC 3660, December 2003.
[2] Foster，B.和F.Andreasen，“基本媒体网关控制协议（MGCP）包”，RFC3660，2003年12月。
[3] Handley, M. and V. Jacobson, "SDP: Session Description Protocol", RFC 2327, April 1998.
[3] Handley，M.和V.Jacobson，“SDP：会话描述协议”，RFC 2327，1998年4月。
[4] Arango, M., Dugan, A., Elliott, I., Huitema, C. and S. Pickett, "Media Gateway Control Protocol (MGCP) Version 1.0", RFC 2705, October 1999.
[4] Arango，M.，Dugan，A.，Elliott，I.，Huitema，C.和S.Pickett，“媒体网关控制协议（MGCP）1.0版”，RFC 27052999年10月。
C. Sivachelvan Cisco Systems 2200 East President George Bush Turnpike Richardson, TX, 75082
C.Sivachelvan Cisco Systems 2200东总统乔治·布什收费公路理查森，德克萨斯州，75082
EMail: chelliah@cisco.com
EMail: chelliah@cisco.com
B. Foster Cisco Systems
B.福斯特思科系统公司
EMail: bfoster@cisco.com
EMail: bfoster@cisco.com
Copyright (C) The Internet Society (2003). All Rights Reserved.
版权所有（C）互联网协会（2003年）。版权所有。
This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this paragraph are included on all such copies and derivative works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references to the Internet Society or other Internet organizations, except as needed for the purpose of developing Internet standards in which case the procedures for copyrights defined in the Internet Standards process must be followed, or as required to translate it into languages other than English.
本文件及其译本可复制并提供给他人，对其进行评论或解释或协助其实施的衍生作品可全部或部分编制、复制、出版和分发，不受任何限制，前提是上述版权声明和本段包含在所有此类副本和衍生作品中。但是，不得以任何方式修改本文件本身，例如删除版权通知或对互联网协会或其他互联网组织的引用，除非出于制定互联网标准的需要，在这种情况下，必须遵循互联网标准过程中定义的版权程序，或根据需要将其翻译成英语以外的其他语言。
The limited permissions granted above are perpetual and will not be revoked by the Internet Society or its successors or assignees.
上述授予的有限许可是永久性的，互联网协会或其继承人或受让人不会撤销。
This document and the information contained herein is provided on an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
本文件和其中包含的信息是按“原样”提供的，互联网协会和互联网工程任务组否认所有明示或暗示的保证，包括但不限于任何保证，即使用本文中的信息不会侵犯任何权利，或对适销性或特定用途适用性的任何默示保证。
Acknowledgement
确认
Funding for the RFC Editor function is currently provided by the Internet Society.
RFC编辑功能的资金目前由互联网协会提供。