Network Working Group R. Kumar
Request for Comments: 3441 Cisco Systems
Category: Informational January 2003
Network Working Group R. Kumar
Request for Comments: 3441 Cisco Systems
Category: Informational January 2003
Asynchronous Transfer Mode (ATM) Package for the Media Gateway Control Protocol (MGCP)
媒体网关控制协议（MGCP）的异步传输模式（ATM）包
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 describes an Asynchronous Transfer Mode (ATM) package for the Media Gateway Control Protocol (MGCP). This package includes new Local Connection Options, ATM-specific events and signals, and ATM connection parameters. Also included is a description of codec and profile negotiation. It extends the MGCP that is currently being deployed in a number of products. Implementers should be aware of developments in the IETF Megaco Working Group and ITU SG16, which are currently working on a potential successor to this protocol.
本文档描述了媒体网关控制协议（MGCP）的异步传输模式（ATM）包。该包包括新的本地连接选项、ATM特定事件和信号以及ATM连接参数。还包括对编解码器和配置文件协商的描述。它扩展了目前正在许多产品中部署的MGCP。实施者应了解IETF Megaco工作组和ITU SG16的发展情况，这两个工作组目前正在研究该协议的潜在后续协议。
Table of Contents
目录
1.0 Conventions Used in this Document..............................2
2.0 Introduction...................................................2
3.0 Local Connection Options.......................................3
3.1 ATM Bearer Connection.........................................4
3.2 ATM Adaptation Layer (AAL)....................................8
3.3 Service Layer................................................15
3.4 ATM Bearer Traffic Management................................19
3.5 AAL Dimensioning.............................................27
4.0 Signals and Events.............................................30
5.0 Connection Parameters..........................................35
6.0 Negotiation of Profiles and Codecs in ATM Applications.........37
6.1 Consistency of Parameters...................................37
6.2 Codec/Profile Negotiation in ATM Networks...................38
7.0 Security Considerations.......................................45
8.0 IANA Considerations...........................................45
9.0 References....................................................45
10.0 Acronyms......................................................48
1.0 Conventions Used in this Document..............................2
2.0 Introduction...................................................2
3.0 Local Connection Options.......................................3
3.1 ATM Bearer Connection.........................................4
3.2 ATM Adaptation Layer (AAL)....................................8
3.3 Service Layer................................................15
3.4 ATM Bearer Traffic Management................................19
3.5 AAL Dimensioning.............................................27
4.0 Signals and Events.............................................30
5.0 Connection Parameters..........................................35
6.0 Negotiation of Profiles and Codecs in ATM Applications.........37
6.1 Consistency of Parameters...................................37
6.2 Codec/Profile Negotiation in ATM Networks...................38
7.0 Security Considerations.......................................45
8.0 IANA Considerations...........................................45
9.0 References....................................................45
10.0 Acronyms......................................................48
11.0 Acknowledgements..............................................49
12.0 Author's Address..............................................49
13.0 Full Copyright Statement......................................50
11.0 Acknowledgements..............................................49
12.0 Author's Address..............................................49
13.0 Full Copyright Statement......................................50
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14, RFC 2119.
本文件中的关键词“必须”、“不得”、“要求”、“应”、“不应”、“应”、“不应”、“建议”、“可”和“可选”应按照BCP 14、RFC 2119中的说明进行解释。
MGCP identifiers are case-insensitive. This includes package names, event names, local connection options and other elements of the MGCP header.
MGCP标识符不区分大小写。这包括包名、事件名、本地连接选项和MGCP头的其他元素。
The Media Gateway Control Protocol or MGCP [36] is used to control voice media gateways from external call control elements. Even though the bearer network might be IP, ATM, TDM or a mix of these, MGCP is transported over IP. Packages such as the MGCP CAS packages [38] are modular sets of parameters such as connection options, signal, event and statistics definitions that can be used to extend it into specific contexts. A related, IP-based mechanism for the description of ATM connections [18] has been generated by the IETF MMUSIC group. Due to the IP-centric nature of all aspects of the MGCP device control protocol, and for consistency with other MGCP package definitions, it is desirable to publish the MGCP ATM package in an IETF document.
媒体网关控制协议或MGCP[36]用于从外部呼叫控制元件控制语音媒体网关。即使承载网络可能是IP、ATM、TDM或它们的组合，MGCP也是通过IP传输的。MGCP CAS软件包[38]等软件包是模块化的参数集，如连接选项、信号、事件和统计定义，可用于将其扩展到特定上下文中。IETF MMUSIC组已经生成了一种相关的、基于IP的ATM连接描述机制[18]。由于MGCP设备控制协议的所有方面都以IP为中心，并且为了与其他MGCP包定义保持一致，需要在IETF文档中发布MGCP ATM包。
MGCP [36] allows the auditing of endpoints for package versions supported. The package version for the MGCP ATM package, as specified in this document, is 0. Even if the ATM package is the default package for some endpoints, the package prefix "atm" shall not be omitted in local connection option names, event names, signal names etc. If the ATM package is the default package for an endpoint, it will be listed as the first package in the audit response list. It is not necessary for the MGCP ATM package to be the default package for ATM to be supported on an endpoint.
MGCP[36]允许对受支持的包版本的端点进行审核。本文件中规定的MGCP ATM包的包版本为0。即使ATM包是某些端点的默认包，也不得在本地连接选项名称、事件名称、信号名称等中省略包前缀“ATM”。如果ATM包是端点的默认包，它将作为审核响应列表中的第一个包列出。MGCP ATM包不必是端点上支持的ATM的默认包。
The ATM package in this document consists of Local Connection Options (Section 3.0), Events and Signals (Section 4.0) and ATM Statistics Parameters (Section 5.0). Section 6.1 has guidelines for consistency in the use of Local Connection Options. Section 6.2 describes codec and profile negotiation. Section 7.0 addresses security considerations.
本文件中的ATM包包括本地连接选项（第3.0节）、事件和信号（第4.0节）和ATM统计参数（第5.0节）。第6.1节提供了本地连接选项使用一致性的指南。第6.2节描述了编解码器和配置文件协商。第7.0节介绍了安全注意事项。
In the ATM networks addressed in this document, services are carried directly over ATM without an intervening IP layer. The Local Connection Options, Events, Signals and Statistics Parameters described in this section are not needed for VoIP calls which can be carried, in whole or in part, over an ATM network. In that case, the constructs defined elsewhere for IP are sufficient.
在本文所述的ATM网络中，服务直接通过ATM进行，无需中间IP层。本节中描述的本地连接选项、事件、信号和统计参数不需要用于可通过ATM网络全部或部分承载的VoIP呼叫。在这种情况下，在别处为IP定义的构造就足够了。
The ATM local connection option names, event names and signal names MUST always have an "atm" package prefix. Backward compatibility with older implementations that use X-atm as the package name is desirable.
ATM本地连接选项名称、事件名称和信号名称必须始终具有“ATM”包前缀。与使用X-atm作为包名的旧实现的向后兼容性是可取的。
MGCP grammar [36] must be followed with regard to the use of white spaces. The examples in this document attempt to follow MGCP grammar in this and all other respects.
关于空格的使用，必须遵循MGCP语法[36]。本文中的示例试图在这方面和所有其他方面遵循MGCP语法。
The Local Connection Options (LCOs) defined in this section are specific to ATM applications. Like other LCOs, these can be used in commands to create connections, modify connections and audit connections. However, unless noted otherwise below, they are not to be returned when an endpoint is audited for capabilities.
本节中定义的本地连接选项（LCO）特定于ATM应用。与其他LCO一样，可以在命令中使用这些命令来创建连接、修改连接和审核连接。但是，除非下面另有说明，否则在对端点的功能进行审核时，不会返回它们。
ATM Local Connection Options are divided into the following categories: ATM bearer connection, ATM adaptation layer, service layer, ATM bearer traffic management and AAL dimensioning.
ATM本地连接选项分为以下类别：ATM承载连接、ATM适配层、服务层、ATM承载流量管理和AAL标注。
When parameter values are represented in decimal format, leading zeros are omitted.
当参数值以十进制格式表示时，前导零将被忽略。
These local connection options are used to parameterize ATM bearer connections.
这些本地连接选项用于参数化ATM承载连接。
TABLE 1: Local Connection Options for ATM Bearers
+---------+---------------+---------------------------------------+
| LCO | Meaning | Values |
+---------+---------------+---------------------------------------+
| ct | Connection |AAL1, AAL1_SDT, AAL1_UDT, AAL2, AAL3/4,|
| | Type |AAL5, USER_DEFINED_AAL |
+---------+---------------+---------------------------------------+
| vc |VC/Bearer type | PVC, SVC, CID |
+---------+---------------+---------------------------------------+
| se | Enable path | on, off |
| | set-up | |
+---------+---------------+---------------------------------------+
| ci | Connection | See below |
| | Element | |
| | Identifier | |
+---------+---------------+---------------------------------------+
TABLE 1: Local Connection Options for ATM Bearers
+---------+---------------+---------------------------------------+
| LCO | Meaning | Values |
+---------+---------------+---------------------------------------+
| ct | Connection |AAL1, AAL1_SDT, AAL1_UDT, AAL2, AAL3/4,|
| | Type |AAL5, USER_DEFINED_AAL |
+---------+---------------+---------------------------------------+
| vc |VC/Bearer type | PVC, SVC, CID |
+---------+---------------+---------------------------------------+
| se | Enable path | on, off |
| | set-up | |
+---------+---------------+---------------------------------------+
| ci | Connection | See below |
| | Element | |
| | Identifier | |
+---------+---------------+---------------------------------------+
Connection type (ct): This parameter describes the ATM adaptation layer. The values that can be assigned to it are: AAL1, AAL1_SDT, AAL1_UDT, AAL2, AAL3/4, AAL5 and USER_DEFINED_AAL. The user defined adaptation layer is per amendment 2 of ITU-T Q.2931.
连接类型（ct）：此参数描述ATM适配层。可分配给它的值有：AAL1、AAL1_SDT、AAL1_UDT、AAL2、AAL3/4、AAL5和用户定义的_AAL。用户定义的适配层符合ITU-T Q.2931的修改件2。
Type of Bearer/VC (vc): This indicates whether a PVC, CID or an SVC is to be used for an ATM connection. Possible values are: PVC, SVC or CID. Omitting this parameter will result in the use of a default, which could be embedded or provisioned. The value "PVC" covers both classical PVCs and SPVCs. The value "CID" covers subchannels within AAL1 [35] and AAL2 [10] virtual circuits. A value of "SVC" for atm/vc does not necessarily imply that the addressed media gateway should initiate signaling for bearer set-up, since this might be done by another node such as the far-end media gateway.
承载类型/VC（VC）：表示ATM连接是使用PVC、CID还是SVC。可能的值为：PVC、SVC或CID。省略此参数将导致使用默认值，可以嵌入或设置默认值。“PVC”值包括经典PVC和SPVC。值“CID”涵盖AAL1[35]和AAL2[10]虚拟电路中的子信道。atm/vc的“SVC”值并不一定意味着寻址媒体网关应启动承载设置的信令，因为这可能由另一个节点（如远端媒体网关）完成。
Enable path set-up (se): This local connection option is used to explicitly enable or disable the use of bearer signaling for path set-up. Permitted values of this local connection option are "on" and "off". Examples of bearer signaling are SVC signaling, ITU Q.2630.1 signaling and combinations thereof. Examples of such combinations are the set-up of an AAL2 SVC and the assignment of a CID within it or the set-up of a concatenation of an AAL2 single-CID SVC and a CID channel within a multiplexed AAL2 VC. This parameter can be used with both the backward and forward bearer connection
启用路径设置（se）：此本地连接选项用于显式启用或禁用承载信令用于路径设置。此本地连接选项的允许值为“开”和“关”。承载信令的示例是SVC信令、ITU Q.2630.1信令及其组合。此类组合的示例包括AAL2 SVC的设置和其中CID的分配，或AAL2单个CID SVC和多路复用AAL2 VC中CID通道的串联设置。此参数可用于向后和向前承载连接
set-up methods. In the former case, the call-terminating gateway sets up the bearer connection. In the latter case, the call-originating gateway sets up the bearer connection.
设置方法。在前一种情况下，呼叫终止网关建立承载连接。在后一种情况下，呼叫发起网关建立承载连接。
This option may or may not be used in conjunction with atm/sc event notification. When this option and the atm/sc event notification are omitted, creating and modifying connection commands, the call agent is deferring any relevant decision to set up an ATM or AAL2 connection to the media gateways. In the absence of this parameter, a media gateway's autonomous decision to set up an ATM or AAL2 path via bearer signaling depends on default/provisioned behaviors, such as the applicability and nature (backward/forward) of a bearer connection set-up model, the network type ('nt'), connection type ('atm/ct') and bearer type/VC ('atm/vc') local connection options, and the media gateway's awareness of whether it is the originating gateway or terminating gateway in a call. This awareness may be based on the presence or absence of an SDP remote connection descriptor in the initial create connection command.
此选项可能与atm/sc事件通知一起使用，也可能与atm/sc事件通知一起使用。当省略此选项和atm/sc事件通知时，创建和修改连接命令，呼叫代理将推迟任何相关决定，以建立到媒体网关的atm或AAL2连接。在没有此参数的情况下，媒体网关通过承载信令建立ATM或AAL2路径的自主决定取决于默认/设置的行为，例如承载连接建立模型的适用性和性质（向后/向前）、网络类型（'nt'）、连接类型（'ATM/ct'）和承载类型/VC（'ATM/VC'）本地连接选项，以及媒体网关对呼叫中是发起网关还是终止网关的感知。这种感知可能基于初始创建连接命令中是否存在SDP远程连接描述符。
Connection Element Identifier (ci): This indicates the Virtual Circuit or CID to be used for the bearer connection. It is used when the call agent manages VC and/or CID resources in the bearer network.
连接元素标识符（ci）：表示用于承载连接的虚拟电路或CID。它用于呼叫代理管理承载网络中的VC和/或CID资源。
The ci parameter can be in one of the following formats:
ci参数可以采用以下格式之一：
* VCCI-<vcci> * VCCI-<vcci>/CID-<cid> * <ATMaddressType>-<ATMaddress>/VCCI-<vcci> * <ATMaddress>/VCCI-<vcci> * <ATMaddressType>-<ATMaddress>/VCCI-<vcci>/CID-<cid> * <ATMaddress>/VCCI-<vcci>/CID-<cid> * BCG-<bcg>/VCCI-<vcci> * BCG-<bcg>/VCCI-<vcci>/CID-<cid> * BCG-<bcg>/VPI-<vpi>/VCI-<vci> * BCG-<bcg>/VPI-<vpi>/VCI-<vci>/CID-<cid> * PORT-<portId>/VPI-<vpi>/VCI-<vci> * PORT-<portId>/VPI-<vpi>/VCI-<vci>/CID-<cid> * VPCI-<vpci>/VCI-<vci> * VPCI-<vpci>/VCI-<vci>/CID-<cid> * <ATMaddressType>-<ATMaddress>/VPCI-<vpci>/VCI-<vci> * <ATMaddress>/VPCI-<vpci>/VCI-<vci> * <ATMaddressType>-<ATMaddress>/VPCI-<vpci>/VCI-<vci>/CID-<cid> * <ATMaddress>/VPCI-<vpci>/VCI-<vci>/CID-<cid>
* VCCI—<VCCI<VCCI<VCCI<VCCI<VCCI<VCCI<VCCI<VCCI<VCCI<VCCI<VCCI<VCCI<VCCI<VCCI<VCCI<VCCI<VCCI<VCCI<VCCI<VCCI<VCCI<VCCI<VCCI<VCCI<VCCI<VCCI<VCCI<VCCI<VCCI-<VCCI<VCCI<<VCCI<<VCCI<<<风德德式式>>>>>><<风德德德式>><<<风CDCDCDCCCCCCCCCCCC<<<<<<<<<<<<<风都都都都式>>>>>>><农村农村农村农村农村农村农村农村农村式>>>>>>><农村农村农村农村农村农村农村农村农村农村农村农村发展类型>>>>>>><<农村农村农村农村农村农村农村农村农村农村农村农村农村发展类型>>>>>>><农村农村农村CID-<CID>*“Porti-<VPI-<<部分部分部分<<<部分部分部分<<部分部分部分<<<部分部分部分<<部分部分部分<<部分部分部分<<部分部分部分<<<部分部分端口<<<部分部分端口>/VPI-<部分部分端口<<部分部分端口<<部分部分端口<<部分部分部分端口>/VPI-<部分部分部分部分<<VPI-<部分<<部分部分<<部分部分部分<<部分部分部分部分部分<<部分部分部分端口<<<部分部分<<部分<<<VPI-<部分部分部分部分<<VPI>//部分<<VPI-<部分<<VPI>///部分部分部分部分部分<<VPI-<VPI-<<<VPI-<VPI-<VPI-<VPI>//////VPI-<VPI-<VPI-<VPI-<VPI-<VPI-<VPI<<VPI-<VPI-<<<<<VCI-<VCI>/CID-<CID>
The subparameters of the ci parameter are defined as follows:
ci参数的子参数定义如下：
|--------------|-----------------------|----------------------------|
| Subparameter | Meaning | Representation |
|--------------|-----------------------|----------------------------|
| vcci | VC connection Id | Decimal Integer |
| | | (16-bit equivalent) |
|--------------|-----------------------|----------------------------|
| cid | Channel Id | Decimal Integer |
| | | (8-bit equivalent) |
|--------------|-----------------------|----------------------------|
|ATMaddressType| ATM address type | "NSAP", "E164", "GWID", |
| | | "ALIAS" |
|--------------|-----------------------|----------------------------|
| ATMaddress | ATM address | 40 hex digits ("NSAP") |
| | | upto 15 digits ("EI64") |
| | | upto 32 chars ("GWID") |
| | | upto 32 chars ("ALIAS") |
|--------------|-----------------------|----------------------------|
| bcg |Bearer Connection Group| Decimal Integer |
| | | (8-bit equivalent) |
|--------------|-----------------------|----------------------------|
| vpi | Virtual Path Id | Decimal Integer |
| | | (8 or 12-bit equivalent) |
|--------------|-----------------------|----------------------------|
| vci | Virtual Channel Id | Decimal Integer |
| | | (16-bit equivalent) |
|--------------|-----------------------|----------------------------|
| portID | Port Id | Decimal Integer |
| | | (32-bit equivalent) |
|--------------|-----------------------|----------------------------|
| vpci | VP connection ID | Decimal Integer |
| | | (16-bit equivalent) |
|--------------|-----------------------|----------------------------|
|--------------|-----------------------|----------------------------|
| Subparameter | Meaning | Representation |
|--------------|-----------------------|----------------------------|
| vcci | VC connection Id | Decimal Integer |
| | | (16-bit equivalent) |
|--------------|-----------------------|----------------------------|
| cid | Channel Id | Decimal Integer |
| | | (8-bit equivalent) |
|--------------|-----------------------|----------------------------|
|ATMaddressType| ATM address type | "NSAP", "E164", "GWID", |
| | | "ALIAS" |
|--------------|-----------------------|----------------------------|
| ATMaddress | ATM address | 40 hex digits ("NSAP") |
| | | upto 15 digits ("EI64") |
| | | upto 32 chars ("GWID") |
| | | upto 32 chars ("ALIAS") |
|--------------|-----------------------|----------------------------|
| bcg |Bearer Connection Group| Decimal Integer |
| | | (8-bit equivalent) |
|--------------|-----------------------|----------------------------|
| vpi | Virtual Path Id | Decimal Integer |
| | | (8 or 12-bit equivalent) |
|--------------|-----------------------|----------------------------|
| vci | Virtual Channel Id | Decimal Integer |
| | | (16-bit equivalent) |
|--------------|-----------------------|----------------------------|
| portID | Port Id | Decimal Integer |
| | | (32-bit equivalent) |
|--------------|-----------------------|----------------------------|
| vpci | VP connection ID | Decimal Integer |
| | | (16-bit equivalent) |
|--------------|-----------------------|----------------------------|
The CID, or Channel ID, can refer to AAL1 as well as AAL2 applications. In AAL1 applications based on [35], it refers to the octet position, starting from one, within an n x 64 SDT frame.
CID或通道ID可以引用AAL1和AAL2应用程序。在基于[35]的AAL1应用程序中，它指的是n x 64 SDT帧内从1开始的八位元位置。
The VPCI is a 16 bit field defined in Section 4.5.16 of ITU Q.2931. The VPCI is similar to the VPI, except for its width and the fact that it retains its value across VP crossconnects.
VPCI是ITU Q.2931第4.5.16节中定义的16位字段。VPCI与VPI类似，只是其宽度和在VP交叉连接中保留其值的事实不同。
The VCCI is a 16 bit field defined in ITU Recommendation Q.2941.2 [14]. The VCCI is similar to the VCI, except for the fact that it retains its value across VC crossconnects.
VCCI是ITU建议Q.2941.2[14]中定义的16位字段。VCCI与VCI类似，只是它在VC交叉连接中保持其值。
In general, <vpci> and <vcci> values are unique between a pair of nodes. When they are unique between a pair of nodes, but not unique within a network, they need to be qualified at any node, by the ATM address of the remote node. These parameters can be pre-provisioned or signaled via SVC signaling messages. When VPCI and VCCI values are pre-provisioned, administrations have the option of provisioning them uniquely in a network. In this case, the ATM address of the far end is not needed to qualify these parameters.
通常，<vpci>和<vcci>值在一对节点之间是唯一的。当它们在一对节点之间是唯一的，但在网络中不是唯一的时，它们需要在任何节点上通过远程节点的ATM地址进行限定。这些参数可以预先设置或通过SVC信令消息发送信号。当预先设置VPCI和VCCI值时，管理部门可以选择在网络中唯一地设置它们。在这种情况下，不需要远端的ATM地址来限定这些参数。
The <portId> parameter is used to identify the physical trunk port on an ATM module. It can be represented as a decimal or hex number of up to 32 digits.
<portId>参数用于标识ATM模块上的物理中继端口。它可以表示为最多32位的十进制数或十六进制数。
In some applications, it is meaningful to bundle a set of connections between a pair of ATM nodes into a bearer connection group. The <bcg> subparameter is an eight bit field that allows the bundling of up to 255 VPCs or VCCs.
在某些应用中，将一对ATM节点之间的一组连接捆绑到承载连接组中是有意义的。<bcg>子参数是一个8位字段，允许绑定多达255个VPC或VCC。
In some applications, it is necessary to wildcard some elements of the ci local connection option. The "$" wildcard character can be substituted for some of the terms of this parameter. While wildcarding, the constant strings that qualify the terms in the ci parameter are retained. The concatenation <ATMaddressType>- <ATMaddress> can be wildcarded in the following ways:
在某些应用程序中，需要通配符ci本地连接选项的某些元素。可以用“$”通配符替换此参数的某些术语。通配符时，将保留限定ci参数中术语的常量字符串。可以通过以下方式对串联<ATMaddress type>-<ATMaddress>进行通配符：
* The entire concatenation, <ATMaddressType>-<ATMaddress>, is replaced with a "$". * <ATMaddress> is replaced with a "$", but <ATMaddressType> is not.
* 整个连接，<ATMaddressType>-<AtMadAddress>，被替换为“$”*<ATMaddress>被替换为“$”，但<ATMaddress type>不是。
Examples of wildcarding the ci parameter in the AAL1 and AAL5 contexts are: VCCI-$, BCG-100/VPI-20/VCI-$.
在AAL1和AAL5上下文中通配符ci参数的示例有：VCCI-$、BCG-100/VPI-20/VCI-$。
Examples of wildcarding the ci parameter in the AAL2 context are: VCCI- 40/CID-$, BCG-100/VPI-20/VCI-120/CID-$.
在AAL2上下文中通配符ci参数的示例有：VCCI-40/CID-$、BCG-100/VPI-20/VCI-120/CID-$。
If the addressType is NSAP, the address is expressed in the standard dotted hex form. This is a string of 40 hex digits, with dots after the 2nd, 6th, 10th, 14th, 18th, 22nd, 26th, 30th, 34th and 38th digits. The "0x" prefix is not used, since this is always represented in hex. The last octet of the NSAP address is the 'selector' field that is available for non-standard use. For example:
如果addressType为NSAP，则地址以标准点十六进制形式表示。这是一个由40位十六进制数字组成的字符串，在第2位、第6位、第10位、第14位、第18位、第22位、第26位、第30位、第34位和第38位后面有点。不使用“0x”前缀，因为它总是用十六进制表示。NSAP地址的最后八位字节是可供非标准使用的“选择器”字段。例如：
L: atm/ci:NSAP-47.0091.8100.0000.0060.3e64.fd01.0060.3e64.fd01.00/
VCCI-65
L: atm/ci:NSAP-47.0091.8100.0000.0060.3e64.fd01.0060.3e64.fd01.00/
VCCI-65
If the ATMaddressType is E164, the ATMaddress is expressed as a decimal number with up to 15 digits. For example:
如果ATMaddress类型为E164，则ATMaddress表示为最多15位的十进制数。例如：
L: atm/ci:E164-9738294382/VCCI-100
L: atm/ci:E164-9738294382/VCCI-100
The E.164 numbers used can be in the International Format E.164 or conform to a private numbering plan.
使用的E.164编号可以采用国际格式E.164或符合专用编号计划。
If the ATMaddressType is GWID, it means that the address is a Gateway Identifier or Node Alias. This may or may not be globally unique. In this format, the ATMaddress is expressed as an alphanumeric string ("A"-"Z", "a"-"z", "0" - "9",".","-","_"). For example:
如果ATMaddressType为GWID，则表示该地址是网关标识符或节点别名。这可能是唯一的，也可能不是唯一的。在这种格式中，ATMaddress表示为字母数字字符串（“A”-“Z”、“A”-“Z”、“0”-“9”、“、”、“-”和“”）。例如：
L: atm/ci:GWID-officeABCmgx101vism12
L: atm/ci:GWID-officeABCmgx101vism12
The keyword "ALIAS" can be substituted for "GWID". For example:
关键字“别名”可以替换为“GWID”。例如：
L: atm/ci:ALIAS-officeABCmgx101vism12
L: atm/ci:ALIAS-officeABCmgx101vism12
An example of a GWID (ALIAS) is the CLLI code used for telecom equipment. For all practical purposes, it should be adequate for the GWID (ALIAS) to be a variable length string with a maximum size of 32 characters.
GWID（别名）的一个示例是用于电信设备的CLLI代码。出于所有实际目的，GWID（别名）应该是最大长度为32个字符的可变长度字符串。
When an endpoint supporting the ATM package is audited for capabilities, the following local connection options from Section 3.1 shall be returned: connection type (atm/ct) and VC/bearer type (atm/vc). If more than one value is supported, these shall be expressed as a list of semicolon-separated values. Although this is not very useful, it is permissible for these values to have overlapping semantics (e.g., AAL1 and AAL1_SDT). An example of returning, in audit response, the local connection options defined in Section 3.1 is:
当审核支持ATM包的端点的能力时，应返回第3.1节中的以下本地连接选项：连接类型（ATM/ct）和VC/承载类型（ATM/VC）。如果支持多个值，这些值应表示为分号分隔的值列表。虽然这不是很有用，但允许这些值具有重叠语义（例如AAL1和AAL1_SDT）。在审计响应中，返回第3.1节中定义的本地连接选项的示例如下：
A: atm/ct:AAL1_SDT;AAL2, atm/vc:PVC;CID
A: atm/ct:AAL1_SDT;AAL2, atm/vc:PVC;CID
These local connection options are used to parameterize the ATM adaptation layer (AAL). These are further classified as: generic AAL connection options, AAL1-related connection options and AAL2-related connection options. Currently, there are no local connection options defined in this category that pertain to AAL5.
这些本地连接选项用于参数化ATM适配层（AAL）。这些进一步分类为：通用AAL连接选项、AAL1相关连接选项和AAL2相关连接选项。目前，该类别中没有定义与AAL5相关的本地连接选项。
TABLE 2: Generic Local Connection Options for the AAL
+---------+---------------+---------------------------------------+
| LCO | Meaning | Values |
+---------+---------------+---------------------------------------+
| aalApp | Application |itu_h323c,af83,AAL5_SSCOP, |
| | |itu_i3661_unassured, itu_i3661_assured |
| | |itu_i3662, itu_i3651, itu_i3652, |
| | |itu_i3653, itu_i3654, |
| | |FRF5, FRF8, FRF11,itu_h2221 |
+---------+---------------+---------------------------------------+
| sbc | Subchannel | 1...24 for T1-based applications |
| | Count | 1...31 for E1-based applications |
+---------+---------------+---------------------------------------+
TABLE 2: Generic Local Connection Options for the AAL
+---------+---------------+---------------------------------------+
| LCO | Meaning | Values |
+---------+---------------+---------------------------------------+
| aalApp | Application |itu_h323c,af83,AAL5_SSCOP, |
| | |itu_i3661_unassured, itu_i3661_assured |
| | |itu_i3662, itu_i3651, itu_i3652, |
| | |itu_i3653, itu_i3654, |
| | |FRF5, FRF8, FRF11,itu_h2221 |
+---------+---------------+---------------------------------------+
| sbc | Subchannel | 1...24 for T1-based applications |
| | Count | 1...31 for E1-based applications |
+---------+---------------+---------------------------------------+
AAL application (aalApp): This connection option specifies the controlling standard for an application layer above the ATM adaptation layer. Other strings can be defined. If used, these need to be prefixed with an "X-".
AAL应用程序（aalApp）：此连接选项指定ATM适配层之上的应用程序层的控制标准。可以定义其他字符串。如果使用，则需要在其前面加上前缀“X-”。
"itu_h323c" Annex C of H.323 which specifies direct RTP on AAL5 [12].
H.323的“itu_h323c”附录C规定了AAL5上的直接RTP[12]。
"af83" af-vtoa-0083.001, which specifies variable size AAL5 PDUs with PCM voice and a null SSCS [13].
“af83”af-vtoa-0083.001，其中规定了具有PCM语音和空SSC的可变大小AAL5 PDU[13]。
"AAL5_SSCOP" SSCOP as defined in ITU Q.2110 [14] running over an AAL5 CPS [27]. No information is provided regarding any layers above SSCOP such as Service Specific Coordination Function (SSCF) layers.
“AAL5_SSCOP”指ITU Q.2110[14]中定义的在AAL5 CP上运行的SSCOP[27]。未提供有关SSCOP之上任何层的信息，如服务特定协调功能（SSCF）层。
"itu_i3661_unassured" SSCS with unassured transmission, per ITU I.366.1 [11].
根据itu I.366.1[11]，具有未保证传输的“itu_i3661_未保证”SSC。
"itu_i3661_assured" SSCS with assured transmission, per ITU I.366.1 [11]. This uses SSCOP [14].
根据itu I.366.1[11]，具有保证传输的“itu_i3661_保证”SSC。这使用SSCOP[14]。
"itu_i3662" SSCS per ITU I.366.2 [2].
符合itu I.366.2[2]的“itu_i3662”SSC。
"itu_i3651" Frame relay SSCS per ITU I.365.1 [15].
“itu_i3651”帧中继SSC符合itu I.365.1[15]。
"itu_i3652" Service-specific coordination function, as defined in ITU I.365.2, for Connection Oriented Network Service (SSCF-CONS) [16]. This uses SSCOP [14].
“itu_i3652”特定于服务的协调功能，如itu I.365.2中所定义，用于面向连接的网络服务（SSCF-CONS）[16]。这使用SSCOP[14]。
"itu_i3653" Service-specific coordination function, as defined in ITU I.365.3, for Connection Oriented Transport Service (SSCF-COTS) [17]. This uses SSCOP [14].
“itu_i3653”特定于服务的协调功能，如itu I.365.3中所定义，用于面向连接的传输服务（SSCF-COTS）[17]。这使用SSCOP[14]。
"itu_i3654" Service-specific coordination function, as defined in ITU I.365.4 [28].
“itu_i3654”特定于服务的协调功能，如itu I.365.4[28]所定义。
"FRF5" Use of the FRF.5 frame relay standard [23], which references ITU I.365.1 [15].
“FRF5”使用参考ITU I.365.1[15]的FRF.5帧中继标准[23]。
"FRF8" Use of the FRF.8 frame relay standard [24]. This implies a null SSCS and the mapping of the frame relay header into the ATM header.
“FRF8”使用FRF.8帧中继标准[24]。这意味着空SSC和帧中继报头到ATM报头的映射。
"FRF11" Use of the FRF.11 frame relay standard [25].
“FRF11”使用FRF.11帧中继标准[25]。
"itu_h2221" Use of the ITU standard H.222.1 for audiovisual communication over AAL5 [22].
“itu_h2221”将itu标准H.222.1用于AAL5上的视听通信[22]。
Subchannel count (sbc): This parameter indicates the number of DS0s in an n x 64 connection. Such connections use an ATM adaptation layer 1 (ATM forum af-vtoa-78) or 2 (ITU I.366.2). For T1-based applications, it can take on integral values in the inclusive range [1...24]. For E1-based applications, it can take on integral values in the inclusive range [1...31]. When this parameter is omitted, the subchannel count must be known by other means.
子通道计数（sbc）：此参数表示n x 64连接中的DS0数。此类连接使用ATM适配层1（ATM论坛af-vtoa-78）或2（ITU I.366.2）。对于基于T1的应用程序，它可以采用包含范围[1…24]内的整数值。对于基于E1的应用，它可以采用包含范围[1…31]内的整数值。省略此参数时，必须通过其他方式知道子通道计数。
TABLE 3: Local Connection Options for AAL Type 1
+---------+---------------+---------------------------------------+
| LCO | Meaning | Values |
+---------+---------------+---------------------------------------+
| pf | Partial fill | 1...48 |
| | | |
+---------+---------------+---------------------------------------+
| crt | Clock Recovery| NULL, SRTS, ADAPTIVE |
| | Type | |
+---------+---------------+---------------------------------------+
| fe | FEC enable | NULL, DELAY_SENSITIVE,LOSS_SENSITIVE |
+---------+---------------+---------------------------------------+
TABLE 3: Local Connection Options for AAL Type 1
+---------+---------------+---------------------------------------+
| LCO | Meaning | Values |
+---------+---------------+---------------------------------------+
| pf | Partial fill | 1...48 |
| | | |
+---------+---------------+---------------------------------------+
| crt | Clock Recovery| NULL, SRTS, ADAPTIVE |
| | Type | |
+---------+---------------+---------------------------------------+
| fe | FEC enable | NULL, DELAY_SENSITIVE,LOSS_SENSITIVE |
+---------+---------------+---------------------------------------+
Partial Fill Count (pf): When present, the 'pf' parameter is used to indicate the fill level of cells. When this local connection option is absent, then other means (such as provisionable defaults) are used to determine the presence and level of partial fill.
部分填充计数（pf）：存在时，“pf”参数用于指示单元格的填充级别。如果缺少此本地连接选项，则使用其他方法（例如可设置的默认值）来确定部分填充的存在和级别。
This parameter indicates the number of non-pad payload octets, not including any AAL SAR or convergence sublayer octets. For example, in some AAL1 applications that use partially filled cells with padding at the end, this attribute indicates the number of leading payload octets not including any AAL overhead.
此参数表示非pad有效负载八位字节的数量，不包括任何AAL SAR或聚合子层八位字节。例如，在某些AAL1应用程序中，该属性表示不包括任何AAL开销的前导有效负载八位字节的数量，这些应用程序在末尾使用部分填充的单元格和填充。
In general, permitted values of the pf parameter are integers in the range 1 - 48 inclusive. However, this upper bound is different for different adaptations since the AAL overhead, if any, is different. If a specified partial fill (e.g. 47) is greater than or equal to the maximum fill (in this example, 46 for AAL1 P-cells), then complete fill (46 in this example) is used. Using a 'partial' fill of 48 effectively disables partial fill. Values below or above the permissible range of 1-48 MUST be rejected with an error code of 532 {Unsupported value(s) in LocalConnectionOptions}.
通常，pf参数的允许值为1-48（含1-48）范围内的整数。然而，由于AAL开销（如果有的话）不同，因此对于不同的适应，该上限是不同的。如果指定的部分填充（例如47）大于或等于最大填充（在本例中，AAL1 P单元为46），则使用完全填充（本例中为46）。使用48的“部分”填充有效禁用部分填充。必须拒绝低于或高于允许范围1-48的值，错误代码为532{LocalConnectionOptions中不支持的值}。
In the AAL1 context, this parameter applies uniformly to both P and non-P cells. In AAL1 applications that do not distinguish between P and non-P cells, a value of 47 indicates complete fill (i.e., the absence of partial fill). In AAL1 applications that distinguish between P and non-P cells, a value of 46 indicates no padding in P-cells and a padding of one in non-P cells.
在AAL1上下文中，此参数统一应用于P和非P单元格。在不区分P和非P单元格的AAL1应用中，值47表示完全填充（即不存在部分填充）。在区分P和非P单元格的AAL1应用程序中，值46表示P单元格中没有填充，而非P单元格中的填充为1。
If partial fill is enabled (i.e., there is padding in at least some cells), then AAL1 structures must not be split across cell boundaries. These shall fit in any cell. Hence, their size shall be less than or equal to the partial fill size. Further, the partial fill size is preferably an integer multiple of the structure size. If it is not, then the partial fill size stated in the local connection options shall be truncated to an integer multiple of the structure size (e.g., a partial fill size of 40 is truncated to 36 to support six 6 x 64 channels).
如果启用了部分填充（即，至少在某些单元格中存在填充），则AAL1结构不得跨单元格边界拆分。这些应适用于任何单元。因此，其尺寸应小于或等于部分填充尺寸。此外，部分填充尺寸优选为结构尺寸的整数倍。如果不是，则本地连接选项中规定的部分填充大小应被截断为结构大小的整数倍（例如，40的部分填充大小被截断为36，以支持6个6 x 64通道）。
Clock recovery type (crt): This is used in AAL1 UDT (unstructured data transfer) applications only. It can be assigned the values: "NULL", "SRTS", or "ADAPTIVE". A value of "NULL" is equivalent to omitting this parameter and implies that the stream (T1 or E1) encapsulated in ATM is either synchronous to the ATM network or is re-timed, before AAL1 encapsulation, via slip buffers. The default value used in the absence of this LCO can be hardcoded or provisioned.
时钟恢复类型（crt）：仅在AAL1 UDT（非结构化数据传输）应用程序中使用。可以为其分配值：“空”、“SRTS”或“自适应”。值“NULL”相当于省略此参数，并意味着封装在ATM中的流（T1或E1）要么与ATM网络同步，要么在AAL1封装之前通过滑动缓冲器重新计时。没有此LCO时使用的默认值可以硬编码或设置。
Forward Error Correction Enable (fe): This indicates whether FEC, as defined in ITU I.363.1 [1], is enabled or not. Possible values are: "NULL", "DELAY_SENSITIVE" and "LOSS_SENSITIVE". FEC can be enabled differently for delay-sensitive and loss-sensitive connections. A "NULL" value implies disabling FEC for an AAL1 connection.
前向纠错启用（fe）：这表示是否启用了ITU I.363.1[1]中定义的FEC。可能的值为：“空”、“延迟敏感”和“丢失敏感”。对于延迟敏感和丢失敏感的连接，FEC可以以不同的方式启用。“NULL”值表示禁用AAL1连接的FEC。
TABLE 4: Local Connection Options for AAL Type 2
+---------+---------------+---------------------------------------+
| LCO | Meaning | Values |
+---------+---------------+---------------------------------------+
| pfl | Profile List | See below |
| | | |
+---------+---------------+---------------------------------------+
| smplCPS | Simplified CPS| on, off |
| | [21] | |
+---------+---------------+---------------------------------------+
| tmcu | Combined use | Integer microseconds |
| | timer | (32-bit equivalent) |
+---------+---------------+---------------------------------------+
| aalsap |Service access | AUDIO, MULTIRATE |
| |point | |
+---------+---------------+---------------------------------------+
| cktmd | Circuit mode | on, off |
| | | |
+---------+---------------+---------------------------------------+
| frmd | Frame mode | on,off |
| | enable | |
+---------+---------------+---------------------------------------+
| genpcm | Generic PCM | PCMA, PCMU |
| | setting | |
+---------+---------------+---------------------------------------+
| ted | Transmission | on,off |
| |error detection| |
+---------+---------------+---------------------------------------+
|rastimer | SSSAR | |
| | reassembly | Integer microseconds |
| | timer | (32-bit equivalent) |
+---------+---------------+---------------------------------------+
TABLE 4: Local Connection Options for AAL Type 2
+---------+---------------+---------------------------------------+
| LCO | Meaning | Values |
+---------+---------------+---------------------------------------+
| pfl | Profile List | See below |
| | | |
+---------+---------------+---------------------------------------+
| smplCPS | Simplified CPS| on, off |
| | [21] | |
+---------+---------------+---------------------------------------+
| tmcu | Combined use | Integer microseconds |
| | timer | (32-bit equivalent) |
+---------+---------------+---------------------------------------+
| aalsap |Service access | AUDIO, MULTIRATE |
| |point | |
+---------+---------------+---------------------------------------+
| cktmd | Circuit mode | on, off |
| | | |
+---------+---------------+---------------------------------------+
| frmd | Frame mode | on,off |
| | enable | |
+---------+---------------+---------------------------------------+
| genpcm | Generic PCM | PCMA, PCMU |
| | setting | |
+---------+---------------+---------------------------------------+
| ted | Transmission | on,off |
| |error detection| |
+---------+---------------+---------------------------------------+
|rastimer | SSSAR | |
| | reassembly | Integer microseconds |
| | timer | (32-bit equivalent) |
+---------+---------------+---------------------------------------+
Profile List (pfl): This is a list of profiles. Profile types are followed by profile numbers for each type. The ordering of profiles can imply preference, with the most preferred profile first. There can be multiple instances of the same profile type in this list. Spaces are used as delimiters within this list. Therefore, to comply with MGCP syntax [36], it is necessary to enclose this list in double quotes.
配置文件列表（pfl）：这是一个配置文件列表。配置文件类型后面是每种类型的配置文件编号。配置文件的顺序可能意味着偏好，首先是最偏好的配置文件。此列表中可以有相同配置文件类型的多个实例。空格用作此列表中的分隔符。因此，为了符合MGCP语法[36]，有必要将此列表用双引号括起来。
The format of the pfl parameter is as follows:
pfl参数的格式如下所示：
"<profileType#1><format list#1><profileType#2><format list#2> ...
<profileType #M><format list#M>"
"<profileType#1><format list#1><profileType#2><format list#2> ...
<profileType #M><format list#M>"
where <format list#i> has the form <profile#i_1>...<profile#i_N>
where <format list#i> has the form <profile#i_1>...<profile#i_N>
The <profileType> parameter indicates the type of profile. It is expressed in the format AAL2/<profileClass> where <profileClass> identifies the source of the definition of the profile.
<profileType>参数表示配置文件的类型。它以AAL2/<profileClass>格式表示，其中<profileClass>标识配置文件定义的来源。
The <profileClass> can be assigned a string value indicating the source of the subsequent profile numbers until the next <profileType> field. The following rules apply to the contents of the <profileClass> field:
可以为<profileClass>分配一个字符串值，指示后续配置文件编号的来源，直到下一个<profileType>字段。以下规则适用于<profileClass>字段的内容：
- <profileClass> = "ITU" indicates profiles defined by ITU.
Examples: profiles defined in the I.366.2 specification [2].
- <profileClass> = "ATMF" indicates profiles defined by ATM
forum. Examples: profiles defined in af-vtoa-0113 [3] or af-
vmoa-0145.000 [21].
- <profileClass> = "custom" indicates profiles defined by a
corporation or a multi-vendor agreement. Since there is no
standard administration of this convention, care should be
taken to preclude inconsistencies within the scope of a
deployment.
- <profileClass> = <corporateName>
An equipment vendor or service provider can use its registered,
globally unique corporate name (e.g., Cisco, Telcordia etc.) as
a string value of the <profileClass>. It is suggested that
organizations maintain consistent definitions of the advertised
AAL2 profiles that bear their corporate name.
- The <profileClass> can be based on IEEE Standard 802-1990,
Section 5.1, which defines the globally unique, IEEE-
administered, three-octet OUIs used in MAC addresses and
protocol identifiers. In this case, the <profileClass> field
shall be assigned a string value of "IEEE:" concatenated with
<oui> where <oui> is the hex representation of a three-octet
field identical to the IEEE OUI. Since this is always
represented in hex, the "0x" prefix is not used. Leading zeros
may be omitted. For example, "IEEE:00000C" and "IEEE:C" both
refer to Cisco Systems, Inc.
- <profileClass> = "ITU" indicates profiles defined by ITU.
Examples: profiles defined in the I.366.2 specification [2].
- <profileClass> = "ATMF" indicates profiles defined by ATM
forum. Examples: profiles defined in af-vtoa-0113 [3] or af-
vmoa-0145.000 [21].
- <profileClass> = "custom" indicates profiles defined by a
corporation or a multi-vendor agreement. Since there is no
standard administration of this convention, care should be
taken to preclude inconsistencies within the scope of a
deployment.
- <profileClass> = <corporateName>
An equipment vendor or service provider can use its registered,
globally unique corporate name (e.g., Cisco, Telcordia etc.) as
a string value of the <profileClass>. It is suggested that
organizations maintain consistent definitions of the advertised
AAL2 profiles that bear their corporate name.
- The <profileClass> can be based on IEEE Standard 802-1990,
Section 5.1, which defines the globally unique, IEEE-
administered, three-octet OUIs used in MAC addresses and
protocol identifiers. In this case, the <profileClass> field
shall be assigned a string value of "IEEE:" concatenated with
<oui> where <oui> is the hex representation of a three-octet
field identical to the IEEE OUI. Since this is always
represented in hex, the "0x" prefix is not used. Leading zeros
may be omitted. For example, "IEEE:00000C" and "IEEE:C" both
refer to Cisco Systems, Inc.
The <profile#> parameter is expressed as a decimal number in the range 1-255.
<profile#>参数表示为1-255范围内的十进制数。
An example of the use of the pfl parameter is:
pfl参数的使用示例如下：
L: atm/pfl:"AAL2/ITU 8 AAL2/ATMF 7 8 AAL2/custom 100 AAL2/cisco 200"
L: atm/pfl:"AAL2/ITU 8 AAL2/ATMF 7 8 AAL2/custom 100 AAL2/cisco 200"
The syntax for pfl can be represented compactly in the following ABNF (RFC2234) form:
pfl的语法可以用以下ABNF（RFC2234）形式简洁地表示：
pfl = "%x22" 1*(profileType (1*profile#))"%x22"
profileType = "AAL2/" profileClass space
profile# = 1-255 space ; decimal integer followed by space
profileClass =
"ATMF"/"ITU"/"custom"/corporateName/("IEEE:" oui)
corporateName = 1*ALPHA ;one or more alphanumeric characters
oui = 1*6 HEXDIG; 1-6 hex digits per IEEE Standard 802-1990
space = %d32
pfl = "%x22" 1*(profileType (1*profile#))"%x22"
profileType = "AAL2/" profileClass space
profile# = 1-255 space ; decimal integer followed by space
profileClass =
"ATMF"/"ITU"/"custom"/corporateName/("IEEE:" oui)
corporateName = 1*ALPHA ;one or more alphanumeric characters
oui = 1*6 HEXDIG; 1-6 hex digits per IEEE Standard 802-1990
space = %d32
Simplified CPS (smplCPS): This enables the AAL2 CPS simplification described in [21]. It can be assigned the following values: on, off. Under this simplification, each ATM cell contains exactly one AAL2 packet. If necessary, octets at the end of the cell are padded with zeros.
简化CP（SMPLCP）：这使得[21]中描述的AAL2 CP简化成为可能。可以为其指定以下值：开、关。在这种简化下，每个ATM信元只包含一个AAL2数据包。如有必要，单元格末尾的八位字节用零填充。
AAL2 combined use timer (tmcu): This is defined in ITU I.363.2 [10]. It is an integer number of microseconds, represented as the decimal equivalent of 32 bits.
AAL2组合使用定时器（tmcu）：这在ITU I.363.2[10]中定义。它是微秒的整数，表示为相当于32位的十进制数。
AAL service access point (aalsap): The service access point for AAL2 is defined in ITU I.366.2 [2]. The aalsap local connection option can take on the following string values: AUDIO, MULTIRATE.
AAL服务接入点（aalsap）：AAL2的服务接入点在ITU I.366.2[2]中定义。aalsap本地连接选项可以采用以下字符串值：音频、多速率。
Circuit mode (cktmd): This is used to enable circuit mode data [2]. It can be assigned a value of "on" or "off".
电路模式（cktmd）：用于启用电路模式数据[2]。可以为其指定“开”或“关”的值。
Frame mode (frmd): This is used to enable frame mode data [2]. It can be assigned a value of "on" or "off".
帧模式（frmd）：用于启用帧模式数据[2]。可以为其指定“开”或“关”的值。
Generic PCM setting (genpcm): This indicates whether generic PCM encoding in AAL2 profiles is A-law or Mu-law. It can be assigned the string values of "PCMA" and "PCMU".
通用PCM设置（genpcm）：这表示AAL2配置文件中的通用PCM编码是A定律还是Mu定律。可以为其分配字符串值“PCMA”和“PCMU”。
Transmission error detection (ted): Transmission error detection is defined in ITU I.366.1 [11]. The ted local connection option can take on the following values: on, off. This local connection option is useful in qualifying the aalApp local connection option, when the value of the latter is "itu_i3661_unassured".
传输错误检测（ted）：传输错误检测在ITU I.366.1[11]中定义。ted本地连接选项可以采用以下值：on、off。当aalApp本地连接选项的值为“itu_i3661_Unsaured”时，此本地连接选项可用于限定aalApp本地连接选项。
SSSAR reassembly timer (rastimer): This is defined in ITU I.366.1 [11]. It is an integer number of microseconds, represented as the decimal equivalent of 32 bits.
SSSAR重组计时器（rastimer）：这在ITU I.366.1[11]中定义。它是微秒的整数，表示为相当于32位的十进制数。
When an endpoint supporting the ATM package is audited for capabilities, the following local connection options from Section 3.2 shall be returned: application (atm/aalApp). Further, if one of the values atm/ct is "AAL2", the following additional local connection options shall be returned: profile list (atm/pfl), simplified CPS (atm/smplCPS), service access point (atm/aalsap), circuit mode enable(atm/cktmd), frame mode enable (atm/frmd) and generic PCM setting (atm/genpcm). If more than one value is supported, these shall be expressed as a list of semicolon-separated values. For atm/smplCPS, atm/cktmd and atm/frmd, an audit can return "on", "off" or "on;off" depending on whether the mode is mandatory, unsupported or optional for the endpoint.
当审核支持ATM包的端点的能力时，应返回第3.2节中的以下本地连接选项：应用程序（ATM/aalApp）。此外，如果atm/ct值之一为“AAL2”，则应返回以下附加本地连接选项：配置文件列表（atm/pfl）、简化CP（atm/SMPLCP）、服务接入点（atm/aalsap）、电路模式启用（atm/cktmd）、帧模式启用（atm/frmd）和通用PCM设置（atm/genpcm）。如果支持多个值，这些值应表示为分号分隔的值列表。对于atm/SMPLCP、atm/cktmd和atm/frmd，审核可以返回“开”、“关”或“开；关”，这取决于端点的模式是强制的、不支持的还是可选的。
An example of returning, in audit response, the local connection options defined in Section 3.2 is:
在审计响应中，返回第3.2节中定义的本地连接选项的示例如下：
A: atm/aalApp:itu_i3662, atm/pfl:"AAL2/ATMF 7 8", smplCPS:on;off,
aalsap:MULTIRATE, cktmd:off, frmd:off, genpcm:PCMU;PCMA
A: atm/aalApp:itu_i3662, atm/pfl:"AAL2/ATMF 7 8", smplCPS:on;off,
aalsap:MULTIRATE, cktmd:off, frmd:off, genpcm:PCMU;PCMA
TABLE 5: Local Connection Options for the Service Layer
+--------------+---------------+----------------------------------+
| LCO | Meaning | Values |
+--------------+---------------+----------------------------------+
| vsel | Voice codec | See below |
| | Selection | |
+--------------+---------------+----------------------------------+
| dsel | Data codec | See below |
| | Selection | |
+--------------+---------------+----------------------------------+
| fsel | Fax codec | See below |
| | Selection | |
+--------------+---------------+----------------------------------+
| ccnf | Codec | Even number (4 - 32) hex digits |
| | Configuration | |
+--------------+---------------+----------------------------------+
| usi | ISUP User | Two hex digits |
| | Information | |
+--------------+---------------+----------------------------------+
TABLE 5: Local Connection Options for the Service Layer
+--------------+---------------+----------------------------------+
| LCO | Meaning | Values |
+--------------+---------------+----------------------------------+
| vsel | Voice codec | See below |
| | Selection | |
+--------------+---------------+----------------------------------+
| dsel | Data codec | See below |
| | Selection | |
+--------------+---------------+----------------------------------+
| fsel | Fax codec | See below |
| | Selection | |
+--------------+---------------+----------------------------------+
| ccnf | Codec | Even number (4 - 32) hex digits |
| | Configuration | |
+--------------+---------------+----------------------------------+
| usi | ISUP User | Two hex digits |
| | Information | |
+--------------+---------------+----------------------------------+
Voice codec selection (vsel): This is a prioritized list of one or more 3-tuples describing voice service. Each vsel 3-tuple indicates a codec, an optional packet length and an optional packetization period.
语音编解码器选择（vsel）：这是描述语音服务的一个或多个3元组的优先列表。每个vsel 3元组表示一个编解码器、一个可选的数据包长度和一个可选的数据包化周期。
The vsel local connection option is structured as follows:
vsel本地连接选项的结构如下所示：
"<encodingName #1> <packetLength #1><packetTime #1>
<encodingName #2> <packetLength #2><packetTime #2>
...
<encodingName #N> <packetLength #N><packetTime #N>"
"<encodingName #1> <packetLength #1><packetTime #1>
<encodingName #2> <packetLength #2><packetTime #2>
...
<encodingName #N> <packetLength #N><packetTime #N>"
where the <encodingName> refers to a codec name such as PCMU, G726- 32, G729 etc. See [18] and [34] for a list of codecs with static payload types. The <packetLength> is a decimal integer representation of the packet length in octets. The <packetTime> is a decimal integer representation of the packetization interval in microseconds.
其中，<encodingName>指编解码器名称，如PCMU、G726-32、G729等。有关静态负载类型的编解码器列表，请参见[18]和[34]。<packetLength>是以八位字节表示的数据包长度的十进制整数。<packetTime>是以微秒为单位的打包间隔的十进制整数表示。
Voiceband data codec selection (dsel): This is a prioritized list of one or more 3-tuples describing voiceband data passthrough service. Each dsel 3-tuple indicates a codec, an optional packet length and an optional packetization period. Depending on the application, the dsel local connection option may or may not cover facsimile service. This is indicated via an <fxIncl> flag preceding the list of 3- tuples. This flag indicates whether the dsel list explicitly addresses facsimile ("on" value) or not ("off" value). This flag can also be set to "-", which is equivalent to setting it to "off".
声带数据编解码器选择（dsel）：这是描述声带数据直通服务的一个或多个3元组的优先列表。每个dsel 3元组表示一个编解码器、一个可选的数据包长度和一个可选的数据包化周期。根据应用情况，dsel本地连接选项可能包括也可能不包括传真服务。这通过3元组列表前面的<fxIncl>标志表示。此标志指示dsel列表是否明确寻址传真（“开”值）或不（“关”值）。此标志也可以设置为“-”，这相当于将其设置为“关”。
If <fxIncl> is "on", then it is rarely useful to also include an fsel option. However, it is syntactically correct to do so as long as the dsel and fsel options include an identical set of 3-tuples, perhaps in a different order.
如果<fxIncl>处于“开”状态，则还包括一个fsel选项很少有用。但是，只要dsel和fsel选项包含一组相同的3元组（可能顺序不同），这样做在语法上是正确的。
If <fxIncl> is "off", then any fsel list may still be ignored if the media gateway does not provide separate treatment of voiceband data passthrough and fax. Since, in this case, there is no distinct facsimile service from the media gateway's perspective, any fsel list does not apply.
如果<fxIncl>处于“关闭”状态，则如果媒体网关未单独处理语音带数据传递和传真，则仍可忽略任何fsel列表。由于在这种情况下，从媒体网关的角度来看，没有明确的传真服务，因此任何fsel列表都不适用。
The dsel local connection option is structured as follows:
dsel本地连接选项的结构如下所示：
"<fxIncl> <encodingName #1> <packetLength #1><packetTime #1>
<encodingName #2> <packetLength #2><packetTime #2>
...
<encodingName #N> <packetLength #N><packetTime #N>"
"<fxIncl> <encodingName #1> <packetLength #1><packetTime #1>
<encodingName #2> <packetLength #2><packetTime #2>
...
<encodingName #N> <packetLength #N><packetTime #N>"
where the <encodingName> refers to a codec name such as PCMU, G726- 32, G729 etc. The <packetLength> is a decimal integer representation of the packet length in octets. The <packetTime> is a decimal integer representation of the packetization interval in microseconds.
其中，<encodingName>指编解码器名称，如PCMU、G726-32、G729等。<packetLength>是以八位字节表示的数据包长度的十进制整数。<packetTime>是以微秒为单位的打包间隔的十进制整数表示。
Facsimile codec selection (fsel): This is a prioritized list of one or more 3-tuples describing fax service. Each fsel 3-tuple indicates a codec, an optional packet length and an optional packetization period. If the dsel option includes facsimile, the fsel connection option should be consistent with it. Each fsel 3-tuple indicates a codec, an optional packet length and an optional packetization period. The fsel local connection option is structured as follows:
传真编解码器选择（fsel）：这是描述传真服务的一个或多个3元组的优先列表。每个fsel 3元组表示一个编解码器、一个可选的数据包长度和一个可选的数据包化周期。如果dsel选项包括传真，则fsel连接选项应与其一致。每个fsel 3元组表示一个编解码器、一个可选的数据包长度和一个可选的数据包化周期。fsel本地连接选项的结构如下：
"<encodingName #1> <packetLength #1><packetTime #1>
<encodingName #2> <packetLength #2><packetTime #2>
...
<encodingName #N> <packetLength #N><packetTime #N>"
"<encodingName #1> <packetLength #1><packetTime #1>
<encodingName #2> <packetLength #2><packetTime #2>
...
<encodingName #N> <packetLength #N><packetTime #N>"
where the <encodingName> refers to a codec name such as PCMU, G726- 32, G729 etc. The <packetLength> is a decimal integer representation of the packet length in octets. The <packetTime> is a decimal integer representation of the packetization interval in microseconds.
其中，<encodingName>指编解码器名称，如PCMU、G726-32、G729等。<packetLength>是以八位字节表示的数据包长度的十进制整数。<packetTime>是以微秒为单位的打包间隔的十进制整数表示。
Since spaces are used as delimiters within the vsel, dsel and fsel lists, it is necessary to enclose these lists in double quotes [36].
由于空格用作vsel、dsel和fsel列表中的分隔符，因此有必要将这些列表用双引号括起来[36]。
The vsel, fsel and dsel parameters complement the rest of the local connection options and should be consistent with them.
vsel、fsel和dsel参数补充了其余的本地连接选项，并应与它们保持一致。
Examples of the use of these parameters are:
这些参数的使用示例如下：
L: atm/vsel:"G729 10 10000 G726-32 40 10000"
L: atm/dsel:"off PCMA 10 10000 G726-32 40 10000"
L: atm/fsel:"PCMU 40 5000 G726-32 20 5000"
L: atm/vsel:"G729 10 10000 G726-32 40 10000"
L: atm/dsel:"on PCMA 10 10000 G726-32 40 10000"
L: atm/vsel:"G729 10 10000 G726-32 40 10000"
L: atm/dsel:"off PCMA 10 10000 G726-32 40 10000"
L: atm/fsel:"PCMU 40 5000 G726-32 20 5000"
L: atm/vsel:"G729 10 10000 G726-32 40 10000"
L: atm/dsel:"on PCMA 10 10000 G726-32 40 10000"
The <packetLength>and <packetTime> can be set to "-" when not needed. A <fxIncl> value of "-" is equivalent to setting it to "off". For example:
当不需要时，<packetLength>和<packetTime>可以设置为“-”。<fxIncl>值“-”相当于将其设置为“关”。例如：
L: atm/vsel:"G729 - - G726-32 - -"
L: atm/dsel:"- G729 - - G726-32 - -"
L: atm/fsel:"G729-24 - -"
L: atm/vsel:"G729 - - G726-32 - -"
L: atm/dsel:"- G729 - - G726-32 - -"
L: atm/fsel:"G729-24 - -"
The vsel, dsel and fsel local connection options can be used in the AAL1, AAL2 and AAL5 contexts. The <packetLength> and <packetTime> are not meaningful in the AAL1 case and should be set to "-". In the AAL2 case, these local connection options indicate the preferred use of some or all of the rows in a given profile table. If multiple 3- tuples are present, they can indicate a preferentially ordered assignment of some rows in that profile to voice, voiceband data passthrough or facsimile service (e.g., row A preferred to row B etc). If multiple profiles are specified in the pfl parameter (described in section 3.2), the profile qualified by these local connection options is the first profile in the list.
vsel、dsel和fsel本地连接选项可在AAL1、AAL2和AAL5上下文中使用。<packetLength>和<packetTime>在AAL1情况下没有意义，应设置为“-”。在AAL2情况下，这些本地连接选项表示首选使用给定概要文件表中的部分或所有行。如果存在多个3元组，则它们可以表示该配置文件中某些行优先顺序分配给语音、声带数据直通或传真服务（例如，a行优先于B行等）。如果在pfl参数中指定了多个配置文件（如第3.2节所述），则由这些本地连接选项限定的配置文件是列表中的第一个配置文件。
Codec configuration (ccnf): This is used to convey the contents of the single codec information element (IE) defined in [30]. The contents of this IE are: a single-octet Organizational Identifier (OID) field, followed by a single-octet Codec Type field, followed by zero or more octets of a codec configuration bit-map. The semantics of the codec configuration bit-map are specific to the organization[30, 31]. Since this bit-map is always represented in hex format, the "0x" prefix is omitted. Leading zeros are not omitted. For example:
编解码器配置（ccnf）：用于传达[30]中定义的单个编解码器信息元素（IE）的内容。此IE的内容包括：单个八位字节组织标识符（OID）字段，后跟单个八位字节编解码器类型字段，后跟编解码器配置位图的零个或多个八位字节。编解码器配置位图的语义特定于组织[30,31]。由于此位图始终以十六进制格式表示，“0x”前缀被省略。前导零不会被忽略。例如：
L: atm/ccnf:01080C
L: atm/ccnf:01080C
indicates an Organizational Identifier of 0x01(the ITU-T). Using [57], the second octet (0x08) indicates a codec type of G.726 (ADPCM). The last octet, 0x0C indicates that 16 kbps and 24 kbps rates are NOT supported, while the 32 kbps and 40 kbps rates ARE supported.
表示组织标识符0x01（ITU-T）。使用[57]，第二个八位字节（0x08）表示编解码器类型为G.726（ADPCM）。最后一个八位字节0x0C表示不支持16 kbps和24 kbps速率，而支持32 kbps和40 kbps速率。
ISUP User Information (usi): This is used to convey the contents of the 'User Information Layer 1 protocol' field within the bearer capability information element defined in Section 4.5.5 of [32], and reiterated as the user service information element (IE) in Section 3.57 of [33]. The 'User Information Layer 1 protocol' field consists of the five least significant bits of Octet 5 of this information element.
ISUP用户信息（usi）：用于在[32]第4.5.5节中定义的承载能力信息元素内传达“用户信息层1协议”字段的内容，并在[33]第3.57节中重申为用户服务信息元素（IE）。“用户信息层1协议”字段由该信息元素的八位字节5的五个最低有效位组成。
The usi LCO represented as a string of two hex digits. The "0x" prefix is omitted since this value is always hexadecimal. These hex digits are constructed from an octet with three leading '0' bits and the last five bits equal to the 'User Information Layer 1 protocol' field described above. Digits to the left are more significant than digits to the right. The resulting values of the usi local connection option are as follows:
usi LCO表示为两个十六进制数字的字符串。“0x”前缀被省略，因为该值始终为十六进制。这些十六进制数字由八位字节构成，八位字节有三个前导“0”位，最后五位等于上述“用户信息层1协议”字段。左边的数字比右边的数字更重要。usi本地连接选项的结果值如下所示：
VALUE MEANING 0x01 CCITT standardized rate adaption V.110 and X.30 0x02 Recommendation G.711 Mu-law 0x03 Recommendation G.711 A-law 0x04 Recommendation G.721 32 kbps ADPCM and Recommendation I.460 0x05 Recommendations H.221 and H.242 0x06 Recommendation H.223 and H.245 0x07 Non-ITU-T standardized rate adaption 0x08 ITU-T standardized rate adaption V.120 0x09 CCITT standardized rate adaption X.31 HDLC flag stuffing
值含义0x01 CCITT标准化速率自适应V.110和X.30 0x02建议G.711 Mu法则0x03建议G.711 A法则0x04建议G.721 32 kbps ADPCM和建议I.460 0x05建议H.221和H.242 0x06建议H.223和H.245 0x07非ITU-T标准化速率自适应0x08 ITU-T标准化速率自适应V.120 0x09 CCITT标准化速率自适应X.31 HDLC标志填充
These local connection options are used to convey ATM traffic parameters.
这些本地连接选项用于传送ATM流量参数。
TABLE 6: Local Connection Options for ATM bearer traffic management
+---------+---------------+---------------------------------------+
| ATM LCO | Meaning | Values |
+---------+---------------+---------------------------------------+
| atc | ATM transfer |CBR, nrt-VBR, rt-VBR, UBR, ABR, GFR, |
| | capability or |DBR,SBR,ABT/IT,ABT/DT |
| | service | |
| | category | |
+---------+---------------+---------------------------------------+
| sbt |atc subtype | 1...5 |
+---------+---------------+---------------------------------------+
| qos | QoS class | 0...5 |
+---------+---------------+---------------------------------------+
| bcob |Broadband | 0...31 |
| |Connection |(Defined values listed below) |
| |-Oriented | |
| |Bearer Class | |
+---------+---------------+---------------------------------------+
| eetim |End-to-end |on,off |
| |timing required| |
+---------+---------------+---------------------------------------+
| stc |Susceptibility | 0...3 |
| |to clipping |(Defined values listed below) |
+---------+---------------+---------------------------------------+
| upcc |User plane |0...3 |
| |connection |(Defined values listed below) |
| |configuration | |
+---------+---------------+---------------------------------------+
TABLE 6: Local Connection Options for ATM bearer traffic management
+---------+---------------+---------------------------------------+
| ATM LCO | Meaning | Values |
+---------+---------------+---------------------------------------+
| atc | ATM transfer |CBR, nrt-VBR, rt-VBR, UBR, ABR, GFR, |
| | capability or |DBR,SBR,ABT/IT,ABT/DT |
| | service | |
| | category | |
+---------+---------------+---------------------------------------+
| sbt |atc subtype | 1...5 |
+---------+---------------+---------------------------------------+
| qos | QoS class | 0...5 |
+---------+---------------+---------------------------------------+
| bcob |Broadband | 0...31 |
| |Connection |(Defined values listed below) |
| |-Oriented | |
| |Bearer Class | |
+---------+---------------+---------------------------------------+
| eetim |End-to-end |on,off |
| |timing required| |
+---------+---------------+---------------------------------------+
| stc |Susceptibility | 0...3 |
| |to clipping |(Defined values listed below) |
+---------+---------------+---------------------------------------+
| upcc |User plane |0...3 |
| |connection |(Defined values listed below) |
| |configuration | |
+---------+---------------+---------------------------------------+
+---------+---------------+---------------------------------------+
| aqf |ATM QoS | List, see below |
| |parameters, | |
| |forward | |
| |direction | |
+---------+---------------+---------------------------------------+
| aqb |ATM QoS | List, see below |
| |parameters, | |
| |backward | |
| |direction | |
+---------+---------------+---------------------------------------+
| adf0+1 |ATM traffic | List, see below |
| |descriptor, | |
| |forward | |
| |direction, | |
| |CLP-independent| |
+---------+---------------+---------------------------------------+
| adf0 |ATM traffic | List, see below |
| |descriptor, | |
| |forward | |
| |direction, | |
| |CLP=0 | |
+---------+---------------+---------------------------------------+
| adb0+1 |ATM traffic | List, see below |
| |descriptor, | |
| |backward | |
| |direction, | |
| |CLP-independent| |
+---------+---------------+---------------------------------------+
| adb |ATM traffic | List, see below |
| |descriptor, | |
| |backward | |
| |direction, | |
| |CLP=0 | |
+---------+---------------+---------------------------------------+
| abrf |ABR parameters,| List, see below |
| |forward | |
| |direction | |
+---------+---------------+---------------------------------------+
| abrb |ABR parameters,| List, see below |
| |backward | |
| |direction | |
+---------+---------------+---------------------------------------+
|abrSetup |ABR connection | List, see below |
| |set-up | |
| |parameters | |
+---------+---------------+---------------------------------------+
+---------+---------------+---------------------------------------+
| aqf |ATM QoS | List, see below |
| |parameters, | |
| |forward | |
| |direction | |
+---------+---------------+---------------------------------------+
| aqb |ATM QoS | List, see below |
| |parameters, | |
| |backward | |
| |direction | |
+---------+---------------+---------------------------------------+
| adf0+1 |ATM traffic | List, see below |
| |descriptor, | |
| |forward | |
| |direction, | |
| |CLP-independent| |
+---------+---------------+---------------------------------------+
| adf0 |ATM traffic | List, see below |
| |descriptor, | |
| |forward | |
| |direction, | |
| |CLP=0 | |
+---------+---------------+---------------------------------------+
| adb0+1 |ATM traffic | List, see below |
| |descriptor, | |
| |backward | |
| |direction, | |
| |CLP-independent| |
+---------+---------------+---------------------------------------+
| adb |ATM traffic | List, see below |
| |descriptor, | |
| |backward | |
| |direction, | |
| |CLP=0 | |
+---------+---------------+---------------------------------------+
| abrf |ABR parameters,| List, see below |
| |forward | |
| |direction | |
+---------+---------------+---------------------------------------+
| abrb |ABR parameters,| List, see below |
| |backward | |
| |direction | |
+---------+---------------+---------------------------------------+
|abrSetup |ABR connection | List, see below |
| |set-up | |
| |parameters | |
+---------+---------------+---------------------------------------+
ATM transfer capability (atc): This parameter indicates the ATM Transfer Capability described in ITU I.371 [19], equivalent to the ATM Service Category described in the UNI 4.1 Traffic Management specification [8]. In applications conforming to ITU I.371, this parameter can be assigned the following values: DBR, SBR, ABT/IT, ABT/DT, ABR. In applications conforming to the UNI 4.1 Traffic Management specification, this parameter can be assigned the following values: CBR, nrt-VBR, rt-VBR, UBR, ABR, GFR.
ATM传输能力（atc）：该参数表示ITU I.371[19]中描述的ATM传输能力，相当于UNI 4.1流量管理规范[8]中描述的ATM服务类别。在符合ITU I.371的应用中，该参数可指定以下值：DBR、SBR、ABT/IT、ABT/DT、ABR。在符合UNI 4.1交通管理规范的应用中，此参数可指定以下值：CBR、nrt VBR、rt VBR、UBR、ABR、GFR。
Subtype (sbt): This qualifies the atc local connection option. It can be assigned integer values of 1...5. The following combinations of the atc and sbt local connection options are meaningful:
子类型（sbt）：这将限定atc本地连接选项。可以为其分配1…5的整数值。atc和sbt本地连接选项的以下组合是有意义的：
atc sbt Resulting transport
atc sbt结果传输
CBR/DBR 1 Voiceband signal transport (ITU G.711, G.722, I.363) CBR/DBR 2 Circuit transport (ITU I.363) CBR/DBR 4 High-quality audio signal transport (ITU I.363) CBR/DBR 5 Video signal transport (ITU I.363) nrt-VBR 1 nrt-VBR.1 nrt-VBR 2 nrt-VBR.2 nrt-VBR 3 nrt-VBR.3 rt-VBR 1 rt-VBR.1 rt-VBR 2 rt-VBR.2 rt-VBR 3 rt-VBR.3 UBR 1 UBR.1 UBR 2 UBR.2 GFR 1 GFR.1 GFR 2 GRR.2 SBR 1 SBR1 SBR 2 SBR2 SBR 3 SBR3
CBR/DBR 1语音带信号传输（ITU G.711、G.722、I.363）CBR/DBR 2电路传输（ITU I.363）CBR/DBR 4高质量音频信号传输（ITU I.363）CBR/DBR 5视频信号传输（ITU I.363）nrt VBR 1 nrt VBR.1 nrt VBR 2 nrt VBR.2 nrt VBR 3 nrt VBR.3 rt VBR 1 rt VBR.1 rt VBR.2 rt VBR.3 UBR 1 UBR.1 UBR 2 UBR.2 GFR 1 GFR.1 GFR 2 GRR.2 SBR 1 SBR 1 SBR 2 SBR 3 SBR
Subtypes for the atc values of CBR or DBR are per [29]. Subtypes for the remaining atc values are per [8] and [19].
CBR或DBR atc值的子类型符合[29]。其余atc值的子类型符合[8]和[19]。
QoS class (qos): This indicates the QoS class specified in ITU I.2965.1 [4]. It can take on the integer decimal values in the range 0 - 5. These values are mapped into QoS classes as follows:
QoS等级（QoS）：表示ITU I.2965.1[4]中规定的QoS等级。它可以采用0-5范围内的整数十进制值。这些值映射到QoS类，如下所示：
----------------------------------------------------------
| VALUE | MEANING |
----------------------------------------------------------
| 0 | Default QoS |
----------------------------------------------------------
| 1 | Stringent |
----------------------------------------------------------
| 2 | Tolerant |
----------------------------------------------------------
| 3 | Bi-level |
----------------------------------------------------------
| 4 | Unbounded |
----------------------------------------------------------
| 5 | Stringent bi-level |
----------------------------------------------------------
----------------------------------------------------------
| VALUE | MEANING |
----------------------------------------------------------
| 0 | Default QoS |
----------------------------------------------------------
| 1 | Stringent |
----------------------------------------------------------
| 2 | Tolerant |
----------------------------------------------------------
| 3 | Bi-level |
----------------------------------------------------------
| 4 | Unbounded |
----------------------------------------------------------
| 5 | Stringent bi-level |
----------------------------------------------------------
Broadband Connection-Oriented Bearer Class (bcob): The bcob local connection option indicates the Broadband Connection-Oriented Bearer Class specified in ITU Q.2961.2 [5]. It is represented as a decimal number in the range 0 - 31, or its hex equivalent (range 0x0 - 0x1F). The following values are currently defined:
宽带连接导向承载类（bcob）：bcob本地连接选项表示ITU Q.2961.2[5]中规定的宽带连接导向承载类。它表示为0-31范围内的十进制数，或其十六进制等效值（范围0x0-0x1F）。当前定义了以下值：
----------------------------------------------------------
| VALUE | MEANING |
----------------------------------------------------------
| 1 | BCOB-A |
----------------------------------------------------------
| 3 | BCOB-C |
----------------------------------------------------------
| 5 | Frame relaying bearer service |
----------------------------------------------------------
| 16 | BCOB-X |
----------------------------------------------------------
| 24 | BCOB-VP (transparent VP service) |
----------------------------------------------------------
----------------------------------------------------------
| VALUE | MEANING |
----------------------------------------------------------
| 1 | BCOB-A |
----------------------------------------------------------
| 3 | BCOB-C |
----------------------------------------------------------
| 5 | Frame relaying bearer service |
----------------------------------------------------------
| 16 | BCOB-X |
----------------------------------------------------------
| 24 | BCOB-VP (transparent VP service) |
----------------------------------------------------------
End-to-end timing (eetim): This indicates whether end-to-end timing is required (Table 4-8 of [29]). It can be assigned a value of "on" or "off".
端到端定时（eetim）：表示是否需要端到端定时（见[29]表4-8]）。可以为其指定“开”或“关”的值。
Susceptibility to clipping (stc): The stc local connection option indicates susceptibility to clipping. It is represented as a decimal number in the range 0 - 3, or its hex equivalent (range 0x0 - 0x3). All values except those listed below are reserved.
易受剪裁影响（stc）：stc本地连接选项表示易受剪裁影响。它表示为0-3范围内的十进制数，或其十六进制等效值（范围0x0-0x3）。除下列值外，所有值均保留。
----------------------------------------------------------
| VALUE | MEANING |
----------------------------------------------------------
| 0 | Not susceptible to clipping |
----------------------------------------------------------
| 1 | Susceptible to clipping |
----------------------------------------------------------
----------------------------------------------------------
| VALUE | MEANING |
----------------------------------------------------------
| 0 | Not susceptible to clipping |
----------------------------------------------------------
| 1 | Susceptible to clipping |
----------------------------------------------------------
User plane connection configuration (upcc): The upcc local connection option is represented as a decimal number in the range 0 - 3, or its hex equivalent (range 0x0 - 0x3). All values except those listed below are reserved.
用户平面连接配置（upcc）：upcc本地连接选项表示为0-3范围内的十进制数，或其十六进制等效值（0x0-0x3范围）。除下列值外，所有值均保留。
----------------------------------------------------------
| VALUE | MEANING |
----------------------------------------------------------
| 0 | Point to point |
----------------------------------------------------------
| 1 | Point to multipoint |
----------------------------------------------------------
----------------------------------------------------------
| VALUE | MEANING |
----------------------------------------------------------
| 0 | Point to point |
----------------------------------------------------------
| 1 | Point to multipoint |
----------------------------------------------------------
ATM QoS parameters, forward direction (aqf) and backward direction (aqb): Here, forward is the direction away from the media gateway, backward is the direction towards the gateway. If the directional convention used by bearer signaling at the gateway is different, then appropriate translations must be done by the media gateway. These parameters have the following format:
ATM QoS参数，前向（aqf）和后向（aqb）：这里，前向是远离媒体网关的方向，后向是朝向网关的方向。如果网关上承载信令使用的方向约定不同，则媒体网关必须进行适当的转换。这些参数具有以下格式：
"<cdvType><acdv><ccdv><eetd><cmtd><aclr>"
"<cdvType><acdv><ccdv><eetd><cmtd><aclr>"
Since spaces are used in this list, it must be enclosed in double quotes for MGCP compliance [36].
由于此列表中使用了空格，因此必须用双引号将其括起来，以符合MGCP的要求[36]。
The <cdvType> parameter can take on the string values of "PP" and "2P". These refer to the peak-to-peak and two-point CDV as defined in UNI 4.0 [6] and ITU Q.2965.2 [7] respectively.
<cdvType>参数可以采用字符串值“PP”和“2P”。这些分别指UNI 4.0[6]和ITU Q.2965.2[7]中定义的峰间和两点CDV。
The CDV parameters, <acdv> and <ccdv>, refer to the acceptable and cumulative CDVs respectively. These are expressed in units of microseconds and represented as the decimal or hex equivalent of 24- bit fields. These use the cell loss ratio, <aclr>, as the "alpha" quantiles defined in the ATMF TM 4.1 specification [8] and in ITU I.356 [9].
CDV参数<acdv>和<ccdv>分别指可接受和累积CDV。它们以微秒为单位表示，并表示为24位字段的十进制或十六进制等效值。它们使用小区丢失率<aclr>作为ATMF TM 4.1规范[8]和ITU I.356[9]中定义的“α”分位数。
The transit delay parameters, <eetd> and <cmtd>, refer to the end-to-end and cumulative transit delays respectively in milliseconds. These are represented as the decimal equivalents of 16-bit fields. These parameters are defined in Q.2965.2 [7], UNI 4.0 [8] and Q.2931 [29].
传输延迟参数<eetd>和<cmtd>分别指以毫秒为单位的端到端传输延迟和累积传输延迟。这些字段表示为16位字段的十进制等效值。这些参数在Q.2965.2[7]、UNI 4.0[8]和Q.2931[29]中定义。
The <aclr> parameter refers to forward and backward acceptable cell loss ratios. This is the ratio between the number of cells lost and the number of cells transmitted. It is expressed as the decimal or hex equivalent of an 8-bit field. This field expresses an order of magnitude n, where n is an integer in the range 1-15. The Cell Loss Ratio takes on the value 10 raised to the power of minus n.
<aclr>参数指向前和向后可接受的信元丢失率。这是丢失的小区数与传输的小区数之间的比率。它表示为8位字段的十进制或十六进制等效值。该字段表示一个数量级n，其中n是范围为1-15的整数。电池损耗率的值为10，增加到负n的幂次方。
If any of these parameters is not specified, is inapplicable or is implied, then it is set to "-".
如果这些参数中的任何一个未指定、不适用或隐含，则将其设置为“-”。
Examples of the use of the aqf and aqb local connection options are:
aqf和aqb本地连接选项的使用示例如下：
L: atm/aqf:"PP 8125 3455 32000 - 11"
L: atm/aqb:"PP 4675 2155 18000 - 12"
L: atm/aqf:"PP 8125 3455 32000 - 11"
L: atm/aqb:"PP 4675 2155 18000 - 12"
This implies a forward acceptable peak-to-peak CDV of 8.125 ms, a backward acceptable peak-to-peak CDV of 4.675 ms, forward cumulative peak-to-peak CDV of 3.455 ms, a backward cumulative peak-to-peak CDV of 2.155 ms, a forward end-to-end transit delay of 32 ms, a backward end-to-end transit delay of 18 ms, an unspecified forward cumulative transit delay, an unspecified backward cumulative transit delay, a forward cell loss ratio of 10 raised to minus 11 and a backward cell loss ratio of 10 to the minus 12.
这意味着前向可接受的峰间CDV为8.125 ms，后向可接受的峰间CDV为4.675 ms，前向累积峰间CDV为3.455 ms，后向累积峰间CDV为2.155 ms，前向端到端传输延迟为32 ms，后向端到端传输延迟为18 ms，未指定的前向累积传输延迟、未指定的后向累积传输延迟、前向信元丢失率10提高到-11、后向信元丢失率10提高到-12。
ATM traffic descriptors, forward direction CLP=0+1 (adf0+1), backward direction CLP=0+1 (adb0+1), forward direction CLP=0 (adf0), backward direction CLP=0 (adb0): Here, forward is the direction away from the media gateway, backward is the direction towards the gateway. If the directional convention used by bearer signaling at the gateway is different, then appropriate translations must be done by the media gateway. The adf0+1, adb0+1, adf0 and adb0 local connection options have the following format:
ATM流量描述符，前向CLP=0+1（adf0+1），后向CLP=0+1（adb0+1），前向CLP=0（adf0），后向CLP=0（adb0）：这里，前向是远离媒体网关的方向，后向是朝向网关的方向。如果网关上承载信令使用的方向约定不同，则媒体网关必须进行适当的转换。adf0+1、adb0+1、adf0和adb0本地连接选项具有以下格式：
"<pcr><scr><mbs><cdvt><mcr><mfs><fd><te>"
"<pcr><scr><mbs><cdvt><mcr><mfs><fd><te>"
Since spaces are used in these lists, they must be enclosed in double quotes for MGCP compliance [36].
由于这些列表中使用了空格，因此必须用双引号将空格括起来，以符合MGCP的要求[36]。
These parameters are defined per the ATMF TM 4.1 specification [8]. Each of these parameters can be set to "-" if the intent is to not specify it via MGCP. These definitions are listed briefly in Table 7 below.
这些参数根据ATMF TM 4.1规范定义[8]。如果不希望通过MGCP指定，则可以将这些参数中的每一个设置为“-”。下文表7简要列出了这些定义。
TABLE 7: ATM Traffic Descriptor Parameters
表7:ATM流量描述符参数
PARAMETER MEANING UNITS pcr Peak Cell Rate Cells per second scr Sustained Cell Rate Cells per second mbs Maximum Burst Size Cells cdvt Cell Delay Variation Tolerance Microseconds mcr Minimum Cell Rate Cells per second mfs Maximum Frame Size Cells fd Frame Discard Allowed on/off te CLP tagging enabled on/off
参数含义单位pcr峰值信元速率每秒信元速率scr持续信元速率每秒信元速率mbs最大突发大小信元cdvt信元延迟变化容差微秒mcr最小信元速率每秒信元速率mfs最大帧大小信元fd帧丢弃允许开/关te CLP标记启用开/关
The pcr, scr, cdvt and mbs can be represented as the decimal equivalents of 24-bit fields. The mbs and mfs can be represented as the decimal equivalents of 16-bit fields.
pcr、scr、cdvt和mbs可以表示为24位字段的十进制等价物。mbs和mfs可以表示为16位字段的十进制等价物。
Examples of these local connection options are:
这些本地连接选项的示例包括：
L: atm/adf0+1:"200 100 20 - - - on -",
atm/adf0:"200 80 15 - - - - off",
atm/adb0+1:"200 100 20 - - - on -",
atm/adb0:"200 80 15 - - - - off"
L: atm/adf0+1:"200 100 20 - - - on -",
atm/adf0:"200 80 15 - - - - off",
atm/adb0+1:"200 100 20 - - - on -",
atm/adb0:"200 80 15 - - - - off"
This implies a forward and backward PCR of 200 cells per second for all cells regardless of CLP, forward and backward PCR of 200 cells per second for cells with CLP=0, a forward and backward SCR of 100 cells per second for all cells regardless of CLP, a forward and backward SCR of 80 cells per second for cells with CLP=0, a forward and backward MBS of 20 cells for all cells regardless of CLP, a forward and backward MBS of 15 cells for cells with CLP=0, an unspecified CDVT which can be known by other means, and an MCR and MFS which are unspecified because they are inapplicable. Frame discard is enabled in both the forward and backward directions. Tagging is not enabled in either direction.
这意味着无论CLP如何，所有细胞的正向和反向PCR为每秒200个细胞，CLP=0的细胞的正向和反向PCR为每秒200个细胞，无论CLP如何，所有细胞的正向和反向SCR为每秒100个细胞，CLP=0的细胞的正向和反向SCR为每秒80个细胞，不考虑CLP的所有小区的前向和后向MBS为20个小区，CLP=0的小区的前向和后向MBS为15个小区，可以通过其他方式知道的未指定CDVT，以及由于不适用而未指定的MCR和MFS。帧丢弃在向前和向后方向都启用。两个方向均未启用标记。
ABR parameters, forward direction (abrf) and backward direction (abrb): Here, forward is the direction away from the media gateway, backward is the direction towards the gateway. If the convention used by bearer signaling at the gateway is different, then appropriate translations must be done by the media gateway. The abrf and abrb local connection options have the following format:
ABR参数，前进方向（abrf）和后退方向（abrb）：这里，前进是远离媒体网关的方向，后退是朝向网关的方向。如果网关上承载信令使用的约定不同，则媒体网关必须进行适当的翻译。abrf和abrb本地连接选项的格式如下：
"<nrm><trm><cdf><adtf>"
"<nrm><trm><cdf><adtf>"
Since spaces are used in these lists, they must be enclosed in double quotes for MGCP compliance [36].
由于这些列表中使用了空格，因此必须用双引号将空格括起来，以符合MGCP的要求[36]。
These ABR parameters are defined per [6] and [8]. Their definition is summarized in Table 8 below. In MGCP, these are represented as the decimal equivalent of the binary fields mentioned below. If any of these parameters is meant to be left unspecified, it is set to "- ".
这些ABR参数根据[6]和[8]定义。下文表8概述了它们的定义。在MGCP中，这些字段表示为下面提到的二进制字段的十进制等效值。如果这些参数中的任何一个未指定，则将其设置为“-”。
TABLE 8: ABR Parameters
+-----------+---------------------------------+-----------------------+
| PARAMETER | MEANING | FIELD SIZE |
+-----------+---------------------------------+-----------------------+
| NRM | Maximum number of cells per | 3 bits |
| | forward Resource Management cell| |
+-----------+---------------------------------+-----------------------+
| TRM | Maximum time between | 3 bits |
| |forward Resource Management cells| |
+-----------+---------------------------------+-----------------------+
| CDF | Cutoff Decrease Factor | 3 bits |
+-----------+---------------------------------+-----------------------+
| ADTF | Allowed Cell Rate Decrease | 10 bits |
| | Time Factor | |
+-----------+---------------------------------+-----------------------+
TABLE 8: ABR Parameters
+-----------+---------------------------------+-----------------------+
| PARAMETER | MEANING | FIELD SIZE |
+-----------+---------------------------------+-----------------------+
| NRM | Maximum number of cells per | 3 bits |
| | forward Resource Management cell| |
+-----------+---------------------------------+-----------------------+
| TRM | Maximum time between | 3 bits |
| |forward Resource Management cells| |
+-----------+---------------------------------+-----------------------+
| CDF | Cutoff Decrease Factor | 3 bits |
+-----------+---------------------------------+-----------------------+
| ADTF | Allowed Cell Rate Decrease | 10 bits |
| | Time Factor | |
+-----------+---------------------------------+-----------------------+
ABR set-up parameters (abrSetup): This local connection option is used to indicate the ABR parameters needed during call/connection establishment (Section 10.1.2.2 of the UNI 4.0 signaling specification [6]). The abrSetup local connection option has the following format:
ABR设置参数（ABR设置）：此本地连接选项用于指示呼叫/连接建立期间所需的ABR参数（UNI 4.0信令规范第10.1.2.2节[6]）。abrSetup本地连接选项具有以下格式：
"<ficr><bicr><ftbe><btbe><crmrtt><frif><brif><frdf><brdf>"
"<ficr><bicr><ftbe><btbe><crmrtt><frif><brif><frdf><brdf>"
Since spaces are used in this list, it must be enclosed in double quotes for MGCP compliance [36].
由于此列表中使用了空格，因此必须用双引号将其括起来，以符合MGCP的要求[36]。
These parameters are defined per [6]. Their definitions are listed briefly in Table 9 below. In these definitions, forward is the direction away from the media gateway, backward is the direction towards the gateway. If the convention used by bearer signaling at the gateway is different, then appropriate translations must be done by the media gateway. If any of these parameters is meant to be left unspecified, it is set to "-".
这些参数根据[6]定义。下文表9简要列出了它们的定义。在这些定义中，向前是远离媒体网关的方向，向后是朝向网关的方向。如果网关上承载信令使用的约定不同，则媒体网关必须进行适当的翻译。如果这些参数中的任何一个未指定，则将其设置为“-”。
TABLE 9: ABR Set-up Parameters
+-----------+----------------------------------+---------------------+
| PARAMETER | MEANING | REPRESENTATION |
+-----------+----------------------------------+---------------------+
| <ficr> | Forward Initial Cell Rate | Decimal equivalent |
| |(Cells per second) | of 24-bit field |
+-----------+----------------------------------+---------------------+
| <bicr> | Backward Initial Cell Rate | Decimal equivalent |
| | (Cells per second) | of 24-bit field |
+-----------+----------------------------------+---------------------+
| <ftbe> | Forward transient buffer | Decimal equivalent |
| | exposure (Cells) | of 24-bit field |
+-----------+----------------------------------+---------------------+
| <btbe> | Backward transient buffer | Decimal equivalent |
| | exposure (Cells) | of 24-bit field |
+-----------+----------------------------------+---------------------+
| <crmrtt> | Cumulative RM round-trip time | Decimal equivalent |
| | (Microseconds) | of 24-bit field |
+-----------+----------------------------------+---------------------+
| <frif> | Forward rate increase factor | Decimal integer |
| | (used to derive cell count) | 0 -15 |
+-----------+----------------------------------+---------------------+
| <brif> | Backward rate increase factor | Decimal integer |
| | (used to derive cell count) | 0 -15 |
+-----------+----------------------------------+---------------------+
| <frdf> | Forward rate decrease factor | Decimal integer |
| | (used to derive cell count) | 0 -15 |
+-----------+----------------------------------+---------------------+
| <brdf> | Backward rate decrease factor | Decimal integer |
| | (used to derive cell count) | 0 -15 |
+-----------+----------------------------------+---------------------+
TABLE 9: ABR Set-up Parameters
+-----------+----------------------------------+---------------------+
| PARAMETER | MEANING | REPRESENTATION |
+-----------+----------------------------------+---------------------+
| <ficr> | Forward Initial Cell Rate | Decimal equivalent |
| |(Cells per second) | of 24-bit field |
+-----------+----------------------------------+---------------------+
| <bicr> | Backward Initial Cell Rate | Decimal equivalent |
| | (Cells per second) | of 24-bit field |
+-----------+----------------------------------+---------------------+
| <ftbe> | Forward transient buffer | Decimal equivalent |
| | exposure (Cells) | of 24-bit field |
+-----------+----------------------------------+---------------------+
| <btbe> | Backward transient buffer | Decimal equivalent |
| | exposure (Cells) | of 24-bit field |
+-----------+----------------------------------+---------------------+
| <crmrtt> | Cumulative RM round-trip time | Decimal equivalent |
| | (Microseconds) | of 24-bit field |
+-----------+----------------------------------+---------------------+
| <frif> | Forward rate increase factor | Decimal integer |
| | (used to derive cell count) | 0 -15 |
+-----------+----------------------------------+---------------------+
| <brif> | Backward rate increase factor | Decimal integer |
| | (used to derive cell count) | 0 -15 |
+-----------+----------------------------------+---------------------+
| <frdf> | Forward rate decrease factor | Decimal integer |
| | (used to derive cell count) | 0 -15 |
+-----------+----------------------------------+---------------------+
| <brdf> | Backward rate decrease factor | Decimal integer |
| | (used to derive cell count) | 0 -15 |
+-----------+----------------------------------+---------------------+
The Local Connection Options in Table 10 are used to dimension the operation of the AAL. In these parameters, forward is the direction away from the media gateway. Backward is the direction towards the media gateway. These parameters are represented as decimal integers in the ranges listed in Table 10.
表10中的本地连接选项用于标注AAL的操作。在这些参数中，前进是远离媒体网关的方向。后退是指向媒体网关的方向。这些参数在表10中列出的范围内表示为十进制整数。
TABLE 10: Local Connection Options used to dimension the AAL
+---------+---------------+---------------------------------------+
| LCO | Meaning | Values (Decimal Integer) |
+---------+---------------+---------------------------------------+
| str | Structure | 1...65,535 |
| | Size | |
+---------+---------------+---------------------------------------+
TABLE 10: Local Connection Options used to dimension the AAL
+---------+---------------+---------------------------------------+
| LCO | Meaning | Values (Decimal Integer) |
+---------+---------------+---------------------------------------+
| str | Structure | 1...65,535 |
| | Size | |
+---------+---------------+---------------------------------------+
+---------+---------------+---------------------------------------+
| cbrRate | CBR rate | Bit map per Table 4-6 of [29] |
+---------+---------------+---------------------------------------+
| fcpcs | Forward | AAL2: 45 or 64 |
| | maximum CPCS | AAL5: 1-65,535 |
| | SDU size | |
+---------+---------------+---------------------------------------+
| bcpcs | Backward | AAL2: 45 or 64 |
| | maximum CPCS | AAL5: 1-65,535 |
| | SDU size | |
+---------+---------------+---------------------------------------+
|fSDUrate | Forward | 24-bit equivalent |
| | maximum AAL2 | |
| | CPS SDU rate | |
+---------+---------------+---------------------------------------+
|bSDUrate | Backward | 24-bit equivalent |
| | maximum AAL2 | |
| | CPS SDU rate | |
+---------+---------------+---------------------------------------+
| ffrm |Forward maximum| 1-65,535 |
| |frame block | |
| |size | |
+---------+---------------+---------------------------------------+
| bfrm |Backward | 1-65,535 |
| |maximum frame | |
| |block size | |
+---------+---------------+---------------------------------------+
|fsssar |Forward maximum| 1-65,568 |
| |SSSAR-SDU | |
| |size | |
+---------+---------------+---------------------------------------+
|bsssar |Backward | 1-65,568 |
| |maximum SSSAR | |
| |SDU size | |
+---------+---------------+---------------------------------------+
|fsscopsdu|Forward maximum| 1-65,528 |
| |SSCOP-SDU | |
| |size | |
+---------+---------------+---------------------------------------+
| | | |
|bsscopsdu|Backward | 1-65,528 |
| |maximum SSCOP | |
| |SDU size | |
+---------+---------------+---------------------------------------+
|fsscopuu |Forward maximum| 1-65,524 |
| |SSCOP-UU field | |
| |size | |
+---------+---------------+---------------------------------------+
+---------+---------------+---------------------------------------+
| cbrRate | CBR rate | Bit map per Table 4-6 of [29] |
+---------+---------------+---------------------------------------+
| fcpcs | Forward | AAL2: 45 or 64 |
| | maximum CPCS | AAL5: 1-65,535 |
| | SDU size | |
+---------+---------------+---------------------------------------+
| bcpcs | Backward | AAL2: 45 or 64 |
| | maximum CPCS | AAL5: 1-65,535 |
| | SDU size | |
+---------+---------------+---------------------------------------+
|fSDUrate | Forward | 24-bit equivalent |
| | maximum AAL2 | |
| | CPS SDU rate | |
+---------+---------------+---------------------------------------+
|bSDUrate | Backward | 24-bit equivalent |
| | maximum AAL2 | |
| | CPS SDU rate | |
+---------+---------------+---------------------------------------+
| ffrm |Forward maximum| 1-65,535 |
| |frame block | |
| |size | |
+---------+---------------+---------------------------------------+
| bfrm |Backward | 1-65,535 |
| |maximum frame | |
| |block size | |
+---------+---------------+---------------------------------------+
|fsssar |Forward maximum| 1-65,568 |
| |SSSAR-SDU | |
| |size | |
+---------+---------------+---------------------------------------+
|bsssar |Backward | 1-65,568 |
| |maximum SSSAR | |
| |SDU size | |
+---------+---------------+---------------------------------------+
|fsscopsdu|Forward maximum| 1-65,528 |
| |SSCOP-SDU | |
| |size | |
+---------+---------------+---------------------------------------+
| | | |
|bsscopsdu|Backward | 1-65,528 |
| |maximum SSCOP | |
| |SDU size | |
+---------+---------------+---------------------------------------+
|fsscopuu |Forward maximum| 1-65,524 |
| |SSCOP-UU field | |
| |size | |
+---------+---------------+---------------------------------------+
+---------+---------------+---------------------------------------+
|bsscopuu |Backward | 1-65,524 |
| |maximum SSCOP | |
| |UU size | |
+---------+---------------+---------------------------------------+
+---------+---------------+---------------------------------------+
|bsscopuu |Backward | 1-65,524 |
| |maximum SSCOP | |
| |UU size | |
+---------+---------------+---------------------------------------+
Structured Data Transfer Block Size (str): This parameter is meaningful only when structured AAL1 is used. It indicates the size (in octets) of the block used for structured data transfer. If not included as a local connection option, the structure size is to be known by other means. For instance, af-vtoa-78 [20] fixes the structure size for n x 64 service, with or without CAS. The L: atm/str parameter is coded as the decimal equivalent of a 16-bit field [29]. The theoretical maximum value of this parameter is 65,535, although most services use much less.
结构化数据传输块大小（str）：仅当使用结构化AAL1时，此参数才有意义。它表示用于结构化数据传输的块的大小（以八位字节为单位）。如果未包括在本地连接选项中，则应通过其他方式了解结构尺寸。例如，af-vtoa-78[20]固定了n x 64服务的结构大小，包括或不包括CAS。L:atm/str参数编码为16位字段的十进制等效值[29]。该参数的理论最大值为65535，尽管大多数服务使用的数据要少得多。
CBR Rate (cbrRate): This is a hexadecimal representation of the bit map defined in Table 4-6 of ITU Q.2931 [29]. This is represented as exactly two hex digits. For example:
CBR速率（cbrRate）：这是ITU Q.2931[29]表4-6中定义的位图的十六进制表示形式。这正好表示为两个十六进制数字。例如：
L: atm/cbrRate:04
L: atm/cbrRate:04
implies a CBR rate of 1.544 Mbps.
表示CBR速率为1.544 Mbps。
Forward maximum CPCS-SDU size (fcpcs): This is the maximum size of the AAL2 or AA5 CPCS SDU in the forward direction.
前进最大CPCS-SDU大小（fcpcs）：这是前进方向上AAL2或AA5 CPCS SDU的最大大小。
Backward maximum CPCS-SDU size (bcpcs): This is the maximum size of the AAL2 or AA5 CPCS SDU in the backward direction.
向后最大CPCS-SDU大小（bcpcs）：这是AAL2或AA5 CPCS SDU在向后方向上的最大大小。
Forward maximum AAL2 CPCS-SDU rate (fSDUrate): This is the maximum rate of the AAL2 CPCS-SDUs in the forward direction.
前向最大AAL2 CPCS-SDU速率（fSDUrate）：这是前向AAL2 CPCS SDU的最大速率。
Backward maximum AAL2 CPCS-SDU rate (bSDUrate): This is the maximum rate of the AAL2 CPCS-SDUs in the backward direction.
向后最大AAL2 CPCS-SDU速率（bSDUrate）：这是AAL2 CPCS SDU在向后方向上的最大速率。
The fSDUrate and bSDUrate local connection options can be used to rate-limit AAL2 CIDs, especially when used in the SSSAR [1] and frame mode [2] contexts.
fSDUrate和bSDUrate本地连接选项可用于限制AAL2 CID的速率，特别是在SSSAR[1]和帧模式[2]上下文中使用时。
Forward maximum frame mode block size (ffrm): This is the maximum size, in the forward direction, of the AAL2 frame mode data unit (I.366.2) [2].
正向最大帧模式块大小（ffrm）：这是AAL2帧模式数据单元（I.366.2）[2]在正向上的最大大小。
Backward maximum frame mode block size (bfrm): This is the maximum size, in the backward direction, of the AAL2 frame mode data unit (I.366.2) [2].
向后最大帧模式块大小（bfrm）：这是AAL2帧模式数据单元（I.366.2）[2]在向后方向上的最大大小。
Forward maximum SSSAR-SDU size (fsssar): This is the maximum size, in the forward direction, of the AAL2-based SSSAR-SDU (I.366.1) [1].
正向最大SSSAR-SDU尺寸（fsssar）：这是基于AAL2的SSSAR-SDU（I.366.1）[1]在正向上的最大尺寸。
Backward maximum SSSAR-SDU size (bsssar): This is the maximum size, in the backward direction, of the AAL2-based SSSAR-SDU (I.366.1) [1].
向后最大SSSAR-SDU大小（bsssar）：这是基于AAL2的SSSAR-SDU（I.366.1）[1]在向后方向上的最大大小。
Forward maximum SSCOP-SDU size (fsscopsdu): This is the maximum size, in the forward direction, of the AAL2-based SSCOP-SDU (I.366.1) [1].
正向最大SSCOP-SDU尺寸（fsscopsdu）：这是基于AAL2的SSCOP-SDU（I.366.1）[1]的正向最大尺寸。
Backward maximum SSCOP-SDU size (bsscopsdu): This is the maximum size, in the backward direction, of the AAL2-based SSCOP-SDU (I.366.1) [1].
反向最大SSCOP-SDU尺寸（bsscopsdu）：这是基于AAL2的SSCOP-SDU（I.366.1）[1]的反向最大尺寸。
Forward maximum SSCOP-UU size (fsscopuu): This is the maximum size, in the forward direction, of the AAL2-based SSCOP-UU field(I.366.1) [1].
正向最大SSCOP-UU大小（fsscopuu）：这是基于AAL2的SSCOP-UU字段（I.366.1）[1]的正向最大大小。
Backward maximum SSCOP-UU size (bsscopuu): This is the maximum size, in the backward direction, of the AAL2-based SSCOP- UU field (I.366.1) [1].
反向最大SSCOP-UU大小（bsscopuu）：这是基于AAL2的SSCOP-UU字段（I.366.1）[1]的反向最大大小。
Standard MGCP syntax and keywords [36] are used in Table 11 to define the events in this package. Since these are all connection events, they cannot be requested for endpoints. For consistency with MGCP [36], it is required that the suffix @<connection-id> NOT be omitted even if there is only one connection to an endpoint. This suffix can also be wildcarded per MGCP rules.
表11中使用标准MGCP语法和关键字[36]来定义此包中的事件。由于这些都是连接事件，因此无法为端点请求它们。为了与MGCP[36]保持一致，要求即使只有一个端点连接，也不要省略后缀@<connection id>。该后缀也可以根据MGCP规则进行通配符。
There are no auditable event-states associated with the ATM package.
没有与ATM包关联的可审核事件状态。
Set-up complete ("sc"):
设置完成（“sc”）：
Within the RequestedEvents (R:) structure, "sc" is used to request notification of successful ATM or AAL2 connection set-up. The ATM OR AAL2 bearer path is ready for subscriber payload carriage when this notification is sent.
在RequestedEvents（R:）结构中，“sc”用于请求ATM或AAL2连接设置成功的通知。发送此通知时，ATM或AAL2承载路径已准备好用于用户有效负载传输。
This could be the set-up of an SVC, the assignment of an AAL2 CID path and combinations thereof. Examples of such combinations are the set-up of an AAL2 SVC and the assignment of a CID within it or the set-up of a concatenation of an AAL2 single-CID SVC and a CID channel within a multiplexed AAL2 VC.
这可能是SVC的设置、AAL2 CID路径的分配及其组合。此类组合的示例包括AAL2 SVC的设置和其中CID的分配，或AAL2单个CID SVC和多路复用AAL2 VC中CID通道的串联设置。
This event is included for backward compatibility. It is preferred that the call agent and the media gateway rely on provisional acknowledgements in the case in which connection set-up has a long
包含此事件是为了向后兼容。优选的是，呼叫代理和媒体网关在连接建立具有长时间延迟的情况下依赖于临时确认
latency. However, if this event is requested, the media gateway must issue notification of connection set-up via this event. In this case, a provisional acknowledgement is not very useful, and full acknowledgement of the create connection or modify connection need not be deferred until connection set up.
延迟但是，如果请求此事件，媒体网关必须通过此事件发出连接设置通知。在这种情况下，临时确认不是很有用，创建连接或修改连接的完整确认不需要推迟到连接建立之后。
The designated trigger for an ATM OR AAL2 connection set-up is an "on" value of the L: atm/se local connection option provided with a create or modify connection command. However, it is recognized that certain applications use the presence of an atm/sc event notification to initiate the set-up of an ATM or AAL2 connection.
ATM或AAL2连接设置的指定触发器是随创建或修改连接命令提供的L:ATM/se本地连接选项的“开”值。然而，人们认识到，某些应用程序使用atm/sc事件通知的存在来启动atm或AAL2连接的设置。
TABLE 11: Signals and Events in the ATM package
|---------------|-----------------------|-----|------|--------------|
| SYMBOL | DEFINITION | R | S | DURATION |
|---------------|-----------------------|-----|------|--------------|
| sc | Bearer path set-up | C | | |
| | complete | | | |
|---------------|-----------------------|-----|------|--------------|
| sf | Bearer path set-up | C | | |
| | failed | | | |
|---------------|-----------------------|-----|------|--------------|
| ec | Enable CAS via | | oo | |
| | type 3 packets | | | |
|---------------|-----------------------|-----|------|--------------|
| etd | Enable DTMF tone | | oo | |
| | forwarding via | | | |
| | packets | | | |
|---------------|-----------------------|-----|------|--------------|
| etm | Enable MF tone | | oo | |
| | forwarding via | | | |
| | packets | | | |
|---------------|-----------------------|-----|------|--------------|
| etr1 | Enable MF-R1 tone | | oo | |
| | forwarding via | | | |
| | packets | | | |
|---------------|-----------------------|-----|------|--------------|
| etr2 | Enable MF-R2 tone | | oo | |
| | forwarding via | | | |
| | packets | | | |
|---------------|-----------------------|-----|------|--------------|
| uc (string) | Used codec changed | C | | |
| | to codec named by | | | |
| | the string | | | |
|---------------|-----------------------|-----|------|--------------|
| ptime (#) | Packetization period | C | | |
| | changed to # | | | |
|---------------|-----------------------|-----|------|--------------|
TABLE 11: Signals and Events in the ATM package
|---------------|-----------------------|-----|------|--------------|
| SYMBOL | DEFINITION | R | S | DURATION |
|---------------|-----------------------|-----|------|--------------|
| sc | Bearer path set-up | C | | |
| | complete | | | |
|---------------|-----------------------|-----|------|--------------|
| sf | Bearer path set-up | C | | |
| | failed | | | |
|---------------|-----------------------|-----|------|--------------|
| ec | Enable CAS via | | oo | |
| | type 3 packets | | | |
|---------------|-----------------------|-----|------|--------------|
| etd | Enable DTMF tone | | oo | |
| | forwarding via | | | |
| | packets | | | |
|---------------|-----------------------|-----|------|--------------|
| etm | Enable MF tone | | oo | |
| | forwarding via | | | |
| | packets | | | |
|---------------|-----------------------|-----|------|--------------|
| etr1 | Enable MF-R1 tone | | oo | |
| | forwarding via | | | |
| | packets | | | |
|---------------|-----------------------|-----|------|--------------|
| etr2 | Enable MF-R2 tone | | oo | |
| | forwarding via | | | |
| | packets | | | |
|---------------|-----------------------|-----|------|--------------|
| uc (string) | Used codec changed | C | | |
| | to codec named by | | | |
| | the string | | | |
|---------------|-----------------------|-----|------|--------------|
| ptime (#) | Packetization period | C | | |
| | changed to # | | | |
|---------------|-----------------------|-----|------|--------------|
|---------------|-----------------------|-----|------|--------------|
| pftrans (#) | Profile element | C | | |
| | changed to row # | | | |
|---------------|-----------------------|-----|------|--------------|
| cle (#) | Cell Loss | C | | |
| | threshold (# ) | | | |
| | exceeded | | | |
|---------------|-----------------------|-----|------|--------------|
| pl (#) | Packet Loss Threshold| C | | |
| | exceeded (# ) | | | |
|---------------|-----------------------|-----|------|--------------|
| qa | Quality Alert | C | | |
| | | | | |
|---------------|-----------------------|-----|------|--------------|
| of (#) | Operation failure: | C | | |
| | Loss of connectivity | | | |
| | with reason code # | | | |
-------------------------------------------------------------------
|---------------|-----------------------|-----|------|--------------|
| pftrans (#) | Profile element | C | | |
| | changed to row # | | | |
|---------------|-----------------------|-----|------|--------------|
| cle (#) | Cell Loss | C | | |
| | threshold (# ) | | | |
| | exceeded | | | |
|---------------|-----------------------|-----|------|--------------|
| pl (#) | Packet Loss Threshold| C | | |
| | exceeded (# ) | | | |
|---------------|-----------------------|-----|------|--------------|
| qa | Quality Alert | C | | |
| | | | | |
|---------------|-----------------------|-----|------|--------------|
| of (#) | Operation failure: | C | | |
| | Loss of connectivity | | | |
| | with reason code # | | | |
-------------------------------------------------------------------
Set-up failed ("sf"):
设置失败（“sf”）：
Within the RequestedEvents (R:) structure, "sf" is used to request notification of a failed ATM OR AAL2 connection set-up. The ATM OR AAL2 connection set-ups addressed by "sf" are the same as for the "sc" event.
在RequestedEvents（R:）结构中，“sf”用于请求ATM或AAL2连接设置失败的通知。“sf”处理的ATM或AAL2连接设置与“sc”事件相同。
In some ATM OR AAL2 applications with SVC set-up or bearer-signalled AAL2 path assignment, the "sf" event might not be used. In these cases, the following options are available:
在一些具有SVC设置或承载信号AAL2路径分配的ATM或AAL2应用程序中，可能不使用“sf”事件。在这些情况下，以下选项可用：
* the call agent receives a spontaneous delete from the media gateway with an appropriate reason code (902). * the call agent receives the "of" event described below with the optional reason code (902).
* 呼叫代理从媒体网关接收带有适当原因代码的自发删除（902）。*呼叫代理接收下面描述的带有可选原因码的“of”事件（902）。
Enable CAS via type 3 packets ("ec"):
通过类型3数据包（“ec”）启用CAS：
This signal indicates that the media gateway is to forward CAS signaling via type 3 packets on an AAL2 connection. This does not preclude the call agent from requesting notification of CAS state changes. On receiving this signal request, the gateway sustains a bidirectional type 3 CAS protocol over the AAL2 path. This comes to an end when the request is cancelled through a subsequent NotificationRequest command or when the VoAAL2 connection is deleted.
此信号表示媒体网关将通过AAL2连接上的类型3数据包转发CAS信令。这并不妨碍呼叫代理请求CAS状态更改通知。在接收到该信号请求时，网关通过AAL2路径维持双向类型3 CAS协议。当通过后续NotificationRequest命令取消请求或删除VoAAL2连接时，此操作结束。
Enable DTMF tones via type 3 packets ("etd"):
通过类型3数据包（“etd”）启用DTMF音调：
A gateway will ignore this signal request if it normally forwards and receives DTMF tones via type 3 packets. This signal indicates that the media gateway is to forward and receive DTMF tones via type 3 packets on an AAL2 connection. This does not preclude the call agent from requesting notification of DTMF tones.
如果网关通常通过类型3数据包转发和接收DTMF音调，则它将忽略此信号请求。此信号表示媒体网关将通过AAL2连接上的类型3数据包转发和接收DTMF音调。这并不妨碍呼叫代理请求DTMF音通知。
Enable MF tones via type 3 packets ("etm"):
通过类型3数据包（“etm”）启用MF音调：
A gateway will ignore this signal request if it normally forwards and receives MF tones via type 3 packets. This signal indicates that the media gateway is to forward and receive MF tones via type 3 packets on an AAL2 connection. This does not preclude the call agent from requesting notification of MF tones. This signal request does not specify the MF tone type, which is known by other means.
如果网关通常通过类型3数据包转发和接收MF音调，则它将忽略此信号请求。此信号表示媒体网关将通过AAL2连接上的类型3数据包转发和接收MF音。这并不妨碍呼叫代理请求MF音通知。此信号请求未指定MF音调类型，这是通过其他方式知道的。
Enable R1 MF tones via type 3 packets ("etr1"):
通过类型3数据包（“etr1”）启用R1 MF音调：
A gateway will ignore this signal request if it normally forwards and receives R1 MF tones via type 3 packets. This signal indicates that the media gateway is to forward and receive R1 MF tones via type 3 packets on an AAL2 connection. This does not preclude the call agent from requesting notification of R1 MF tones.
如果网关通常通过类型3数据包转发和接收R1 MF音调，则网关将忽略此信号请求。此信号表示媒体网关将通过AAL2连接上的类型3数据包转发和接收R1 MF音调。这并不妨碍呼叫代理请求通知R1 MF音。
Enable R2 MF tones via type 3 packets ("etr2"):
通过类型3数据包（“etr2”）启用R2 MF音调：
A gateway will ignore this signal request if it normally forwards and receives R2 MF tones via type 3 packets. This signal indicates that the media gateway is to forward and receive R2 MF tones via type 3 packets on an AAL2 connection. This does not preclude the call agent from requesting notification of R2 MF tones.
如果网关通常通过类型3数据包转发和接收R2 MF音调，则网关将忽略此信号请求。此信号表示媒体网关将通过AAL2连接上的类型3数据包转发和接收R2 MF音调。这并不妨碍呼叫代理请求R2 MF音的通知。
Used codec changed ("uc (string)"):
已更改使用的编解码器（“uc（字符串）”）：
If armed via an R:atm/uc, a media gateway signals a codec change through an O:atm/uc. The alphanumeric string in parentheses is optional. It is the encoding name of the codec to which the switch is made. Although this event can be used with all ATM adaptations (AAL1, AAL2 and AAL5):
如果通过R:atm/uc启用，媒体网关将通过O:atm/uc向编解码器更改发送信号。括号中的字母数字字符串是可选的。它是切换到的编解码器的编码名称。尽管此事件可用于所有ATM适配（AAL1、AAL2和AAL5）：
* The pftrans event is more suited to AAL2 applications. * Codec switches do not generally occur mid-call in AAL1 applications.
* pftrans事件更适合AAL2应用。*在AAL1应用程序中，编解码器开关通常不会在呼叫中期出现。
Packet time changed ("ptime(#)"):
数据包时间已更改（“ptime（#））：
If armed via an R:atm/ptime, a media gateway signals a packetization period change through an O:atm/ptime. The decimal number in parentheses is optional. It is the new packetization period in milliseconds. In AAL2 applications, the pftrans event can be used to cover packetization period changes (and codec changes).
如果通过R:atm/ptime启用，媒体网关将通过O:atm/ptime发出打包周期变化的信号。括号中的小数是可选的。它是以毫秒为单位的新打包周期。在AAL2应用程序中，pftrans事件可用于覆盖打包周期更改（和编解码器更改）。
Profile element changed ("pftrans(#)"):
配置文件元素已更改（“pftrans（#））：
If armed via an R:atm/pftrans, a media gateway signals a mid-call profile element change through an O:atm/ptime. This event is used with AAL2 adaptation only. A profile element is a row in a profile table. Profile elements indicating silence should not trigger this event. The decimal number in parentheses is optional. It is the row number to which the switch is made. Rows are counted downward, beginning from 1.
如果通过R:atm/pftrans进行防护，则媒体网关通过O:atm/ptime向中间呼叫配置文件元素更改发出信号。此事件仅用于AAL2自适应。纵断面元素是纵断面表中的一行。表示静默的配置文件元素不应触发此事件。括号中的小数是可选的。它是进行切换的行号。行从1开始向下计数。
Cell loss exceeded ("cle(#)"):
超过单元损失（“cle（#））：
This event indicates that the cell loss rate exceeds the threshold #. If the threshold is omitted in the requested events and observed events parameters, it is known by other means. The optional decimal number is the number of dropped cells per 100,000 cells. For example, cle(10) indicates cells are being dropped at a rate of 1 in 10,000 cells.
此事件表示单元丢失率超过阈值#。如果在请求的事件和观察到的事件参数中忽略了阈值，则通过其他方式知道该阈值。可选的十进制数是每100000个单元丢弃的单元数。例如，cle（10）表示正在以1/10000的速率丢弃细胞。
Packet loss exceeded ("ple(#)"):
超过数据包丢失（“ple（#））：
This event indicates that the packet loss rate exceeds the threshold #. If the threshold is omitted in the requested events and observed events parameters, it is known by other means. The optional decimal number is the number of dropped packets per 100,000 packets. For example, ple(10) indicates packets are being dropped at a rate of 1 in 10,000 packets.
此事件表示数据包丢失率超过阈值#。如果在请求的事件和观察到的事件参数中忽略了阈值，则通过其他方式知道该阈值。可选的十进制数是每100000个数据包丢弃的数据包数。例如，ple（10）指示分组正以1/10000分组的速率被丢弃。
When the bearer connection uses an AAL2 CID within a multiplexed VCC rather than an entire VCC, the 'ple' event is used instead of 'cle'. The packets are AAL2 CPS PDUs.
当承载连接在多路复用VCC中使用AAL2 CID而不是整个VCC时，将使用“ple”事件而不是“cle”。这些数据包是AAL2 CPS PDU。
Quality alert ("qa"):
质量警报（“qa”）：
This event indicates that the bearer path fails to any predetermined combination of quality criteria such as loss, delay, jitter etc. This criterion is not defined and is left to the application. The gateway reports this quality violation to the call agent if armed to do so.
此事件表示承载路径未达到任何预定的质量标准组合，如丢失、延迟、抖动等。此标准未定义，由应用程序决定。网关将向呼叫代理报告此质量冲突（如果已准备好这样做）。
Report failure ("of (#)"):
报告失败（“of（#））：
This indicates a connection failure. It can also indicate failure to establish a connection, in lieu of "sf".
这表示连接失败。它还可以表示未建立连接，而不是“sf”。
The most common response to these events is for the media gateway to delete the connection. Some applications might choose to report an "of" with the appropriate reason code, a decimal number, optionally included in parentheses. Reason codes are the same as for spontaneous deletes by the gateway.
对这些事件最常见的响应是媒体网关删除连接。有些应用程序可能会选择报告一个带有适当原因代码的“of”，一个十进制数，可以选择包含在括号中。原因代码与网关自动删除的原因代码相同。
The MGCP connection parameters structure is returned in an autonomous delete connection message, and in a response to a delete or audit connection command. The standard connections parameters [36] it contains are redefined below for ATM. Also, a new extension parameter specific to the ATM package is defined.
MGCP连接参数结构在自主删除连接消息中返回，并在对删除或审核连接命令的响应中返回。它包含的标准连接参数[36]在下文中针对ATM重新定义。此外，还定义了特定于ATM包的新扩展参数。
The standard connection parameters redefined for ATM are:
为ATM重新定义的标准连接参数为：
Number of packets sent: If a VCC is assigned to the connection, this is the total number of ATM cells transmitted for the duration of the connection. If a CID within an AAL2 VCC is assigned to the connection, it is the number of AAL2 common part sublayer (CPS) packets transmitted for the duration of the connection.
发送的数据包数：如果为连接分配了VCC，则这是连接期间传输的ATM信元总数。如果将AAL2 VCC中的CID分配给连接，则它是在连接期间传输的AAL2公共部分子层（CPS）数据包的数量。
Number of octets sent: If a VCC is assigned to the connection, this is the total number of ATM payload octets transmitted for the duration of the connection. If a CID within an AAL2 VCC is assigned to the connection, this is the total number of AAL2 CPS payload octets transmitted for the duration of the connection.
发送的八位字节数：如果为连接分配了VCC，则这是连接期间传输的ATM有效负载八位字节总数。如果将AAL2 VCC中的CID分配给连接，则这是连接期间传输的AAL2 CPS有效负载八位字节总数。
Number of packets received: If a VCC is assigned to the connection, this is the total number of ATM cells received for the duration of the connection. If a CID within an AAL2 VCC is assigned to the connection, it is the number of AAL2 common part sublayer (CPS) packets received for the duration of the connection.
接收的数据包数：如果VCC被分配给连接，这是连接期间接收的ATM信元总数。如果将AAL2 VCC中的CID分配给连接，则它是在连接期间接收的AAL2公共部分子层（CPS）数据包的数量。
Number of octets received: If a VCC is assigned to the connection, this is the total number of ATM payload octets received for the duration of the connection. If a CID within an AAL2 VCC is assigned to the connection, this is the total number of AAL2 CPS payload octets received for the duration of the connection.
接收的八位字节数：如果VCC分配给连接，则这是连接期间接收的ATM有效负载八位字节总数。如果将AAL2 VCC中的CID分配给连接，则这是连接期间接收的AAL2 CPS有效负载八位字节总数。
Number of packets lost: If a VCC is assigned to the connection, this is the total number of ATM cells lost for the duration of the connection, in the direction towards the gateway. If a CID within an
丢失的数据包数：如果VCC被分配给连接，这是连接期间朝向网关方向丢失的ATM信元总数。如果一个CID在
AAL2 VCC is assigned to the connection, it is the number of AAL2 common part sublayer (CPS) packets lost for the duration of the connection, in the direction towards the gateway. If these losses cannot be assessed, then the gateway omits this parameter.
AAL2 VCC被分配给连接，它是在连接期间，朝向网关的方向上丢失的AAL2公共部分子层（CPS）数据包的数量。如果无法评估这些损失，则网关将忽略此参数。
Interarrival jitter: If a VCC is assigned to the connection, this is the interarrival jitter for ATM cells. If a CID within an AAL2 VCC is assigned to the connection, this is the interarrival jitter for AAL2 common part sublayer (CPS) packets. If this cannot be determined, then it is omitted or set to 0.
到达间隔抖动：如果一个VCC被分配给连接，这就是ATM信元的到达间隔抖动。如果将AAL2 VCC中的CID分配给连接，则这是AAL2公共部分子层（CPS）数据包的到达间隔抖动。如果无法确定该值，则忽略该值或将其设置为0。
Average Transmission Delay: This should be understood to be the average cell transmission delay in both cases: VCC assignment and CID assignment to the connection. This requires the use of ATM performance monitoring techniques. If it is not possible to assess this delay, it is omitted or set to 0.
平均传输延迟：这应该理解为两种情况下的平均小区传输延迟：VCC分配和连接的CID分配。这需要使用ATM性能监控技术。如果无法评估该延迟，则忽略该延迟或将其设置为0。
The following extension parameter is defined for the connection parameters structure:
为连接参数结构定义了以下扩展参数：
Connection qualification ("atm/CQ"): This qualifies the connection with enough granularity to be able to use the other connection parameters without a priori knowledge of network or connection type. Defined values are:
连接限定（“atm/CQ”）：这使连接具有足够的粒度，能够使用其他连接参数，而无需事先了解网络或连接类型。定义值为：
1 ATM Virtual Circuit Connection (VCC)
1个ATM虚拟电路连接（VCC）
2 AAL2 Channel Identifier (CID)
2 AAL2信道标识符（CID）
3 Direct transfer i.e., without an ATM or other packet path
3直接传输，即无ATM或其他数据包路径
When omitted, the connection parameters must be interpreted on one of the following bases:
省略时，连接参数必须基于以下基础之一进行解释：
* The default interpretations for MGCP in Ref. 36. * The call agent's prior knowledge, if it governs the type of network and connection through the network type 'nt' LCO [Ref. 36] and/or the connection type 'ct' LCO defined here. * The call agent's snooping of the local connection descriptor provided by one or more media gateway. This is used to determine the network and connection type.
* 参考文献36中MGCP的默认解释。*呼叫代理的先验知识，如果它通过此处定义的网络类型“nt”LCO[参考文献36]和/或连接类型“ct”LCO来控制网络和连接的类型。*呼叫代理对一个或多个媒体网关提供的本地连接描述符的窥探。这用于确定网络和连接类型。
An example of connection parameter encoding for an ATM VCC is the following:
ATM VCC的连接参数编码示例如下：
P: PS=1245, OS=59760, PR=1244, OR=59712, PL=20, JI=0, LA=0,atm/CQ=1
P: PS=1245, OS=59760, PR=1244, OR=59712, PL=20, JI=0, LA=0,atm/CQ=1
Note that the PL value refers to the receive direction and is unrelated to PS. Also, since atm/CQ=1, these parameters refer to ATM cells rather than to AAL2 CPS packets.
请注意，PL值指的是接收方向，与PS无关。此外，由于atm/CQ=1，这些参数指的是atm信元，而不是AAL2 CPS数据包。
As in other applications, any of these parameters can be omitted if not relevant to an application. Also, the entire P: structure is optional.
与其他应用一样，如果这些参数与应用无关，则可以忽略这些参数中的任何一个。另外，整个P:structure是可选的。
When connection parameters are audited, all parameters normally returned with a delete connection are returned. This includes the connection qualification parameter, atm/CQ.
审核连接参数时，将返回通常随删除连接一起返回的所有参数。这包括连接限定参数atm/CQ。
The measurement or estimation of some or all of these connection parameters might not be feasible or beneficial in some applications. In such cases, these may be individually omitted, or the entire connection parameters structure, which is optional in MGCP, might be omitted. Further, parameters which indicate impairments might be set to 0 to nullify their impact, if any.
在某些应用中，测量或估计部分或全部这些连接参数可能不可行或不有益。在这种情况下，可以单独省略这些参数，或者可以省略MGCP中可选的整个连接参数结构。此外，指示损害的参数可以设置为0，以消除其影响（如果有）。
For ATM networks, the "nt" local connection option in MGCP must be set to "ATM".
对于ATM网络，MGCP中的“nt”本地连接选项必须设置为“ATM”。
In any ATM application, the following Local Connection Options should not be used:
在任何ATM应用中，不应使用以下本地连接选项：
Type of service, L: t Resource reservation, L: r
服务类型，L:t资源预留，L:r
This is because the Local Connection Options listed in Table 6 provide information equivalent to the L: t and L: r local connection options.
这是因为表6中列出的本地连接选项提供的信息相当于L:t和L:r本地连接选项。
The following Local Connection Option is not meaningful in the AAL1 case and should not be used:
以下本地连接选项在AAL1情况下没有意义，不应使用：
Packetization period, L: p
包装期，L:p
In AAL2 applications, the following Local Connection Options should not be used:
在AAL2应用程序中，不应使用以下本地连接选项：
Encoding algorithm, L: a Packetization period, L: p
编码算法，L:a分组周期，L:p
The following ATM Local Connection Options provide equivalent information in the AAL2 case:
以下ATM本地连接选项在AAL2情况下提供等效信息：
Profile list, L: atm/pfl
Priority list of voice codec selections, L: atm/vsel
Priority list of voiceband data passthrough codec selections,
L: atm/dsel
Priority list of fax codec selections, L: atm/fsel
Profile list, L: atm/pfl
Priority list of voice codec selections, L: atm/vsel
Priority list of voiceband data passthrough codec selections,
L: atm/dsel
Priority list of fax codec selections, L: atm/fsel
The use of a disallowed local connection option should be flagged with a return code of 524 (inconsistent local connection options). Although it is not recommended that these be ignored, it is recognized some applications choose to do so for the sake of backward compatibility. Note that the inconsistency in this case is between the local connection option (e.g., L:a) and the application (e.g., AAL2) which does not allow it.
不允许的本地连接选项的使用应标记为返回代码524（不一致的本地连接选项）。尽管不建议忽略这些，但可以认识到一些应用程序选择这样做是为了向后兼容。请注意，在这种情况下，本地连接选项（例如，L:a）和不允许它的应用程序（例如，AAL2）之间存在不一致。
In AAL1 and AAL5 applications, codec negotiation is similar to the IP case, although some of the local connection options and SDP connection descriptor parameters are different. See [18] for conventions for the use of the Session Description Protocol [26] in the ATM context.
在AAL1和AAL5应用程序中，编解码器协商类似于IP情况，尽管某些本地连接选项和SDP连接描述符参数不同。有关在ATM上下文中使用会话描述协议[26]的约定，请参见[18]。
In AAL2 applications, the L:a and L:p parameters are disallowed. Profile negotiation takes the place of codec negotiation. The remainder of this section addresses how this is done.
在AAL2应用程序中，不允许使用L:a和L:p参数。配置文件协商取代了编解码器协商。本节的其余部分将介绍如何实现这一点。
The specifics of the AAL2 bearer are not germane to profile negotiation. The bearer could be PVC-based or SVC-based, based on single-CID or multi-CID VCs, subcell multiplexed or not.
AAL2承载的细节与配置文件协商无关。承载可以基于PVC或SVC，基于单个CID或多CID VCs，子小区复用或不复用。
The most general case involves different prioritized lists of profiles at the originating gateway, the terminating gateway, the originating call agent and the terminating call agent. Whether these lists are based on network policies, end subscriber service level agreements or equipment design is immaterial to the profile negotiation that is done as part of the connection establishment process. It is also irrelevant whether these lists are hardcoded defaults or provisionable. In the connection establishment process, a series of ordered intersections is performed. This leaves a single ordered list in the end. The highest priority profile in this list is the selected profile.
最常见的情况涉及始发网关、终接网关、始发呼叫代理和终接呼叫代理处的不同优先级配置文件列表。这些列表是否基于网络策略、最终用户服务级别协议或设备设计，对于作为连接建立过程一部分进行的配置文件协商来说并不重要。这些列表是硬编码的默认值还是可设置的也无关紧要。在连接建立过程中，执行一系列有序交叉。最后只剩下一个有序的列表。此列表中优先级最高的配置文件是选定的配置文件。
The call agent conveys its priority list through the pfl local connection option. The gateway conveys intersection results through the media information line in SDP [18]. Whether these lists imply a real priority or not, a profile is, as a general rule, preferred to profiles that follow it in a list.
呼叫代理通过pfl本地连接选项传送其优先级列表。网关通过SDP[18]中的媒体信息线传送交叉点结果。无论这些列表是否意味着真正的优先级，作为一般规则，概要文件都比列表中紧随其后的概要文件更可取。
Each media gateway has a policy for assigning priorities to different lists (inter-list priority) which is different from the positional ordering of profiles within a list (intra-list priority). This policy might be a hardcoded default or provisioned. The inter-list priority specifies an ordering of the following lists with respect to each other:
每个媒体网关都有一个为不同列表分配优先级（列表间优先级）的策略，该策略不同于列表中配置文件的位置顺序（列表内优先级）。此策略可能是硬编码的默认策略或已设置的策略。列表间优先级指定以下列表之间的顺序：
* 'C-list', which is the priority list from the call agent, received through L: atm/pfl. * 'R-list', which is the priority list from the remote end, received through the SDP remote connection descriptor. * 'L-list', which is the local priority list, hardcoded or provisioned.
* “C-list”，是通过L:atm/pfl接收的呼叫代理的优先级列表。*”R-list'，是通过SDP远程连接描述符从远程端接收的优先级列表。*'L-list'，是本地优先级列表，硬编码或配置。
Depending on the application, different inter-list priorities may be used in cases where the gateway originates and terminates a call.
根据应用，在网关发起和终止呼叫的情况下，可以使用不同的列表间优先级。
The policy mentioned above will vary depending on the type, capabilities and deployment of the media gateway. Network administrations or equipment vendors will provision/default this policy for various reasons such as resource usage optimization, quality of service, likelihood of finding a common profile etc.
上述策略因媒体网关的类型、功能和部署而异。网络管理部门或设备供应商将出于各种原因提供/默认此策略，如资源使用优化、服务质量、找到公共配置文件的可能性等。
When doing an ordered intersection of lists, the intra-list priorities of the highest priority list are used. Any profile that cannot be supported due to resource (bandwidth, processing power etc.) limitations is eliminated from the intersection.
在对列表进行有序交集时，将使用最高优先级列表的列表内优先级。由于资源（带宽、处理能力等）限制而无法支持的任何配置文件都将从交叉点中消除。
In the absence of one or more of these lists, the remaining list(s) are used in the profile selection process. If the call agent does not provide a list of profiles, the C-list is absent. In this case, the intersection of the C-list, R-list and L-list simply becomes the intersection of the R-list and the L-list. If the R-list is also absent, no intersection is performed and the result of this null operation is the L-list. Previous values, if any, of the C-list and R-list are not used.
如果缺少一个或多个列表，则在配置文件选择过程中使用剩余列表。如果呼叫代理未提供配置文件列表，则C-list不存在。在这种情况下，C-list、R-list和L-list的交集只是成为R-list和L-list的交集。如果R-list也不存在，则不执行交叉，此空操作的结果为L-list。不使用C-list和R-list的先前值（如果有）。
The process of profile negotiation is as shown below:
配置文件协商流程如下所示：
ORIGINATING TERMINATING GATEWAY GATEWAY
始发端接网关
(1) On receiving CRCX
do a policy-based ordered
intersection of the C-list,
and L-list. No R-list present.
---------------------------------->
(2)Send resulting ordered list
to the terminating gateway
via SDP.
(1) On receiving CRCX
do a policy-based ordered
intersection of the C-list,
and L-list. No R-list present.
---------------------------------->
(2)Send resulting ordered list
to the terminating gateway
via SDP.
(3) On receiving CRCX do
a policy-based
ordered
intersection of the
C-list, R-list and
L-list.
(4) The highest priority
profile in the
resulting
list is the
selected
profile.
<-----------------------------------
(5) Send selected profile
to the originating gateway
via SDP.
(3) On receiving CRCX do
a policy-based
ordered
intersection of the
C-list, R-list and
L-list.
(4) The highest priority
profile in the
resulting
list is the
selected
profile.
<-----------------------------------
(5) Send selected profile
to the originating gateway
via SDP.
Prior to receiving the final profile in step 5, if the originating gateway has indicated multiple profiles in step 2, the originating gateway does not always have a usable basis for decoding AAL2 packets. This is because a combination of packet length and UUI (user-to-user indication) codepoint range may indicate different codecs in different profiles. The time lag between when the terminating gateways start sending AAL2 packets and when the originating gateway becomes aware of the selected AAL2 profile should be minimized so that any ensuing clipping of the front-end of the audio stream is tolerable for voice circuits. It is unlikely that this will introduce errors in modem or fax circuits since these will not have entered their user data transfer phase at this time.
在步骤5中接收最终简档之前，如果发起网关在步骤2中指示了多个简档，则发起网关并不总是具有解码AAL2分组的可用基础。这是因为分组长度和UUI（用户到用户指示）码点范围的组合可能指示不同配置文件中的不同编解码器。终端网关开始发送AAL2数据包和发起网关意识到所选AAL2配置文件之间的时间间隔应最小化，以便语音电路可以承受音频流前端的任何后续剪辑。这不太可能在调制解调器或传真电路中引入错误，因为此时这些电路尚未进入用户数据传输阶段。
When connection establishment is complete, there is only one profile associated with a connection. This implies that both endpoints are ready to receive, on the fly, packets that comply with any row in the profile. Some applications may elect to associate profile rows with
连接建立完成后，只有一个配置文件与连接关联。这意味着两个端点都可以随时接收符合配置文件中任何行的数据包。某些应用程序可能会选择将配置文件行与
one or more of the following service types: voice service, voiceband data (modem) passthrough service and fax service. This binding can be by default, through provisioning or as part of profile negotiation during call establishment. Such service type associations, when communicated to another entity, are advisory and do not limit the requirement for supporting, at any time, on-the-fly switches to any profile element.
以下一种或多种服务类型：语音服务、声带数据（调制解调器）直通服务和传真服务。默认情况下，可以通过设置或作为呼叫建立期间配置文件协商的一部分进行绑定。此类服务类型关联在传达给另一个实体时是建议性的，并且不限制在任何时候支持任何配置文件元素的动态切换的要求。
Media gateways can have internal default (or provisioned) bindings between service types and profile elements. Note that not all of these bindings might be meaningful in an application context (e.g., the fax service binding might be ignored and omitted). As part of profile negotiation, applications might choose to coordinate those bindings that are meaningful. When this is done, the vsel, dsel and fsel LCOs described in this document, and the vsel, dsel and fsel media attribute lines [18] are used to effect this coordination. Using these constructs, entities such as call agents and media gateways can indicate preferred bindings for the first, most preferred profile in a profile list.
媒体网关可以在服务类型和配置文件元素之间具有内部默认（或配置）绑定。请注意，并非所有这些绑定在应用程序上下文中都有意义（例如，传真服务绑定可能被忽略和省略）。作为概要文件协商的一部分，应用程序可能会选择协调那些有意义的绑定。完成此操作后，将使用本文档中描述的vsel、dsel和fsel LCO以及vsel、dsel和fsel介质属性行[18]来实现此协调。使用这些构造，诸如呼叫代理和媒体网关之类的实体可以为配置文件列表中的第一个、最首选的配置文件指示首选绑定。
When performing ordered intersections of the C-list, L-list and R-list in the call flow above, media gateways MUST use the inter-list priority to choose between a service to profile row binding suggested by the call agent, the remote gateway or it own internal (provisioned or default) binding. Thus, a service type to profile row binding inherits its relative priority from the profile list generated by the same source. If the C-list has the highest priority, and the first profile in the C-list is selected as the first profile of the intersected list, then any service type to profile row bindings provided by the call agent via the vsel, dsel and fsel LCOs are associated with the first profile. If the R-list has the highest priority, and the first profile in the R-list is selected as the first profile of the intersected list, then any service type to profile row bindings provided by the remote gateway via the vsel, dsel and fsel SDP attributes [18] are associated with the first profile. If the L-list has the highest priority, then any internal (default or provisioned) service to profile row bindings are associated with the first profile. At the end of profile negotiation (step 4 in the call flow above), there is one profile selected by the terminating media gateway. It MAY convey any applicable service type to profile row bindings for this profile to the originating gateway via the vsel, dsel and fsel SDP attributes [18].
在执行上述呼叫流中的C-list、L-list和R-list的有序交叉时，媒体网关必须使用列表间优先级，在呼叫代理建议的用于配置行绑定的服务、远程网关或其自身的内部（配置或默认）绑定之间进行选择。因此，服务类型到概要文件行绑定从同一源生成的概要文件列表继承其相对优先级。如果C-list具有最高优先级，并且C-list中的第一个配置文件被选择为相交列表的第一个配置文件，则呼叫代理通过vsel、dsel和fsel LCO提供的任何服务类型到配置文件行绑定都与第一个配置文件相关联。如果R-list具有最高优先级，并且R-list中的第一个配置文件被选择为相交列表的第一个配置文件，则远程网关通过vsel、dsel和fsel SDP属性[18]提供的任何服务类型到配置文件行绑定都与第一个配置文件相关联。如果L-list具有最高优先级，则任何内部（默认或配置的）服务到配置文件行绑定都与第一个配置文件相关联。在配置文件协商结束时（上述呼叫流中的步骤4），终止媒体网关选择了一个配置文件。它可以通过vsel、dsel和fsel SDP属性将此配置文件的任何适用服务类型到配置文件行绑定传送到发起网关[18]。
If the first profile in the intersected list is not the first profile in the highest priority profile list, then any service to profile row bindings associated with the highest priority profile list cannot be used with the first (or only profile) in the intersected list. In this case, the originating or terminating media gateway MUST attempt
如果相交列表中的第一个配置文件不是最高优先级配置文件列表中的第一个配置文件，则与最高优先级配置文件列表关联的任何服务到配置文件行绑定都不能与相交列表中的第一个（或仅一个配置文件）一起使用。在这种情况下，发起或终止媒体网关必须尝试
to associate internal (default or provisioned) service to profile row bindings with the first (or only profile) in the intersected list.
将内部（默认或配置）服务与配置文件行绑定与相交列表中的第一个（或唯一配置文件）关联。
Since there is more than one service type, it is possible that the service type to profile row bindings for the first profile in the intersected list be derived from different sources (the call agent, the remote media gateway, internal defaults or provisioning). For consistency, if the voiceband data (passthrough) service mappings include fax, then a different set of fax service mappings cannot apply to the profile under consideration. If applied in this case, the set of fax service mappings must include the same codecs, packet lengths and packetization periods as the voiceband data service mappings. However, they may be in a different order.
由于存在多个服务类型，因此可能会从不同的源（呼叫代理、远程媒体网关、内部默认值或配置）派生用于为相交列表中的第一个配置文件配置文件行绑定的服务类型。为了一致性，如果语音带数据（直通）服务映射包括传真，则不同的传真服务映射集不能应用于所考虑的配置文件。如果在这种情况下应用，传真服务映射集必须包括与语音带数据服务映射相同的编解码器、数据包长度和分组周期。但是，它们的顺序可能不同。
If the media gateway lumps fax service with voiceband data (modem) passthrough service, then it can ignore any fax service to profile row bindings provided by another entity such as the call agent or the remote gateway. From the media gateway's perspective, there is no distinct fax service in this case. In this case, the media gateway will not indicate a separate preference for the use of certain profile rows in conjunction with fax service.
如果媒体网关将传真服务与语音带数据（调制解调器）直通服务混为一谈，则它可以忽略任何传真服务来分析由另一个实体（如呼叫代理或远程网关）提供的行绑定。从媒体网关的角度来看，在这种情况下没有明显的传真服务。在这种情况下，媒体网关将不会指示将某些配置文件行与传真服务结合使用的单独首选项。
It is possible that the procedure described in this section for associating service types with profile rows fail to yield mappings between a given service type and the row(s) of the first profile in the intersected list of profiles. This is acceptable since these bindings are merely indications of the preferred codecs and packetizations in the context of a given service. They do not obviate the AAL2 requirement that, given a profile that is bound to a connection, a transmitter may switch to any profile row on the fly.
本节中描述的将服务类型与概要文件行关联的过程可能无法生成给定服务类型与概要文件相交列表中第一个概要文件的行之间的映射。这是可以接受的，因为这些绑定只是给定服务上下文中首选编解码器和打包的指示。它们并不排除AAL2的要求，即给定绑定到连接的配置文件，发射机可以动态切换到任何配置文件行。
An example of profile negotiation:
配置文件协商的一个示例：
The L-list at gateway #1, which is the originating gateway in this example, is:
网关#1处的L列表（在本例中为始发网关）为：
custom 100, itu 3, itu 1, itu 8
定制100、itu 3、itu 1、itu 8
The L-list at gateway #2, which is the terminating gateway in this example, is:
网关#2处的L列表（在本例中为终止网关）为：
itu 2, itu 3, itu 1, itu 5
国际电联2、3、1、5
The originating call agent sends the following profile list (C-list) to the originating gateway in the first create connection command:
发起呼叫代理在第一个创建连接命令中将以下配置文件列表（C-list）发送到发起网关：
itu 8, itu 9, atmf 7, itu 3, itu 1, custom 100
itu 8、itu 9、atmf 7、itu 3、itu 1、定制100
Further, the originating call agent qualifies the first profile in its list with the following service type bindings:
此外，发起呼叫代理使用以下服务类型绑定限定其列表中的第一个配置文件：
L: atm/vsel:"G729 10 10000", atm/dsel:"on PCMU 40 5000"
L: atm/vsel:"G729 10 10000", atm/dsel:"on PCMU 40 5000"
There is no atm/fsel local connection option. Facsimile is included with voiceband data in the atm/dsel local connection option.
没有atm/fsel本地连接选项。传真包含在atm/dsel本地连接选项中的语音带数据中。
In step 1 at the originating gateway, there is no remote connection descriptor, hence no R-list. The policy for originating calls at gateway #1 is:
在发起网关的步骤1中，没有远程连接描述符，因此没有R-list。在网关#1发起呼叫的策略是：
C-List > R-list > L-list
C-List>R-List>L-List
where '>' means 'has higher priority than'. The term 'R-list' can be omitted from this series of inequalities since, in case under study, profile negotiation does not include any further ordered intersections at the originating gateway.
其中“>”表示“优先级高于”。术语“R-list”可以从这一系列不等式中省略，因为在所研究的情况下，纵断面协商不包括始发网关处的任何进一步有序交叉口。
In accordance with this policy, the originating gateway performs an ordered intersection of the C-list and the L-list to produce:
根据该策略，发起网关执行C列表和L列表的有序交集，以产生：
itu 8, itu 3, itu 1, custom 100
itu 8、itu 3、itu 1、定制100
Since the C-list has the highest priority and the first profile in the intersected profile list is also the first profile in the C-list, the service bindings provided by the originating call agent are associated with the first profile, itu 8. The originating gateway sends this result(intersected profile list and service bindings for the first profile, itu 8) via the SDP remote session descriptor to the terminating gateway. The service bindings are expressed as follows [18]:
由于C-list具有最高优先级，并且交叉配置文件列表中的第一个配置文件也是C-list中的第一个配置文件，因此发起呼叫代理提供的服务绑定与第一个配置文件itu 8相关联。发起网关通过SDP远程会话描述符将此结果（第一个配置文件的交叉配置文件列表和服务绑定，itu 8）发送到终止网关。服务绑定的表达方式如下[18]：
a=vsel:G729 10 10000
a=dsel:on PCMU 40 5000
a=vsel:G729 10 10000
a=dsel:on PCMU 40 5000
The intersected profile list produced by gateway 1 becomes the R-list for gateway #2. The terminating call agent sends the following profile list (C-list) to the terminating gateway in the first create connection command:
网关1生成的相交配置文件列表成为网关2的R列表。终止呼叫代理在第一个创建连接命令中将以下配置文件列表（C-list）发送到终止网关：
itu 1, itu 4, itu 3, custom 110, custom 100, itu 2
itu 1、itu 4、itu 3、自定义110、自定义100、itu 2
Any service bindings (not shown) sent by the terminating call agent apply to the first profile in this list, itu 1.
终止呼叫代理发送的任何服务绑定（未显示）都适用于此列表中的第一个配置文件itu 1。
The policy for terminating calls at gateway #2 is:
在网关#2终止呼叫的策略是：
R-list > L-list > C-list
R-list>L-list>C-list
Using this policy, gateway #2 produces the following ordered intersection of R-list, L-list and C-list:
使用此策略，网关#2生成R-list、L-list和C-list的以下有序交集：
itu 3, itu 1
国际电联3、1
The first profile in this list, itu 3, is to be used for this connection. Gateway 2 indicates this to the call agent through the SDP local connection descriptor.
此列表中的第一个配置文件itu 3将用于此连接。网关2通过SDP本地连接描述符向呼叫代理指出这一点。
Note that the service bindings provided by the originating gateway have not been specified with respect to itu 3. Therefore, these cannot be used even though the R-list has the highest priority at the terminating gateway. Any existing internal (default or provisioned) service bindings for AAL2 profile itu 3 must be associated by the terminating gateway with the selected profile, itu 3. Those service bindings that are internally unavailable are left unspecified.
请注意，始发网关提供的服务绑定尚未针对itu 3进行指定。因此，即使R-list在终止网关处具有最高优先级，也不能使用它们。终止网关必须将AAL2配置文件itu 3的任何现有内部（默认或配置）服务绑定与所选配置文件itu 3相关联。那些内部不可用的服务绑定未指定。
Since the internal service type bindings do exist for the profile itu 3 at the terminating gateway, they are selected and bound to the connection. In these, fax service is lumped with voiceband data passthrough. These bindings are indicated to the originating gateway via the following SDP media attribute lines:
由于终端网关上的配置文件itu 3存在内部服务类型绑定，因此会选择它们并将其绑定到连接。在这些系统中，传真服务与语音带数据传输集中在一起。这些绑定通过以下SDP媒体属性行指示给发起网关：
a=vsel:G726-32 20 5000 G726-24 15 5000
a=dsel:on PCMU 40 5000 G726-40 25 5000
a=vsel:G726-32 20 5000 G726-24 15 5000
a=dsel:on PCMU 40 5000 G726-40 25 5000
The vsel line maps voice service to certain rows in the itu 3 profile table. The dsel line maps voiceband data service to certain rows in the itu 3 profile table. The "on" in the dsel line indicates that voiceband data includes fax, otherwise a separate fsel line might have been used. Two codecs each are indicated for voice and for voiceband data, with the first codec being the preferred one. Although the originating gateway is not constrained by these advisory indications of profile element to service type mapping, applications may choose to limit on-the-fly switches based on the current service state (voice, voiceband data etc.). If done, this provides greater simplicity at the expense of flexibility.
vsel线路将语音服务映射到itu 3配置文件表中的某些行。dsel线路将声带数据服务映射到itu 3配置文件表中的某些行。dsel行中的“on”表示语音带数据包括传真，否则可能会使用单独的fsel行。两个编解码器分别用于语音和声带数据，第一个编解码器是首选编解码器。尽管发起网关不受配置文件元素到服务类型映射的这些建议指示的限制，但应用程序可以根据当前服务状态（语音、语音带数据等）选择限制即时开关。如果这样做，将以牺牲灵活性为代价提供更大的简单性。
The ATM package extends the base Media Gateway Control Protocol (MGCP) [36]. This package specifies no additional security requirements or recommendations over those of the base MGCP protocol.
ATM包扩展了基本媒体网关控制协议（MGCP）[36]。与基本MGCP协议相比，该包未规定任何其他安全要求或建议。
The ATM package described in this document has been registered as an MGCP package under the name "atm", without the quotes. The current version of this package is 0 (default). This registration has been completed per the IANA considerations in the MGCP specification [36].
本文件中描述的ATM包已注册为MGCP包，名称为“ATM”，无引号。此程序包的当前版本为0（默认）。该注册已按照MGCP规范[36]中的IANA注意事项完成。
The contact for the MGCP ATM package is the author of this document (Section 12).
MGCP ATM包的联系人是本文件的作者（第12节）。
[1] ITU-T I.366.1, B-ISDN ATM Adaptation Layer Specification: Type 1 AAL.
[1] ITU-T I.366.1，B-ISDN ATM适配层规范：类型1 AAL。
[2] ITU-T I.366.2, AAL Type 2 Reassembly Service Specific Convergence Sublayer for Trunking, Nov. 2000.
[2] ITU-T I.366.2，用于中继的AAL 2型重组服务特定汇聚子层，2000年11月。
[3] af-vtoa-0113.000, ATM trunking using AAL2 for narrowband services.
[3] af-vtoa-0113.000，使用AAL2进行窄带服务的ATM中继。
[4] ITU Q. 2965.1, Digital subscriber signalling system no.2 (DSS 2) - Support of Quality of Service classes.
[4] ITU Q.2965.1，第2号数字用户信号发送系统（DSS 2）——对服务质量等级的支持。
[5] ITU Q.2961, Digital subscriber signalling system no.2 (DSS 2) - additional traffic parameters. Also, Amendment 2 to Q.2961.
[5] ITU Q.2961，第2号数字用户信号系统（DSS 2）-附加业务参数。此外，Q.2961的修正案2。
[6] ATMF UNI 4.0 Signaling Specification, af-sig-0061.000.
[6] ATMF UNI 4.0信令规范，af-sig-0061.000。
[7] ITU Q. 2965.2, Digital subscriber signalling system no.2 (DSS 2) - Signalling of individual Quality of Service parameters.
[7] ITU Q.2965.2，第2号数字用户信号发送系统（DSS 2）-单个服务质量参数的信号发送。
[8] ATMF Traffic Management Specification, Version 4.1, af-tm-0121.000.
[8] ATMF交通管理规范，版本4.1，af-tm-0121.000。
[9] I.356, BISDN ATM layer cell transfer performance.
[9] I.356，BISDN ATM层信元传输性能。
[10] ITU-T I.363.2, B-ISDN ATM Adaptation Layer Specification: Type 2 AAL, Sept. 1997.
[10] ITU-T I.363.2，B-ISDN ATM适配层规范：类型2 AAL，1997年9月。
[11] ITU-T I.366.1, Segmentation and Reassembly Service Specific Convergence Sublayer for AAL Type 2, June 1998.
[11] ITU-T I.366.1，AAL类型2的特定于服务的聚合子层的分段和重新组装，1998年6月。
[12] H.323-2, Packet-based multimedia communications systems.
[12] H.323-2，基于分组的多媒体通信系统。
[13] af-vtoa-0083.000, Voice and Telephony Over ATM to the Desktop.
[13] af-vtoa-0083.000，通过ATM到桌面的语音和电话。
[14] Q.2110, B-ISDN ATM adaptation layer - service specific connection oriented protocol (SSCOP).
[14] Q.2110，B-ISDN ATM适配层-特定于服务的面向连接协议（SSCOP）。
[15] I.365.1,Frame relaying service specific convergence sublayer (FR-SSCS).
[15] I.365.1，帧中继服务特定汇聚子层（FR-SSCS）。
[16] I.365.2, B-ISDN ATM adaptation layer sublayers: service specific coordination function to provide the connection oriented network service.
[16] I.365.2，B-ISDN ATM适配层子层：提供面向连接的网络服务的特定于服务的协调功能。
[17] I.365.3, B-ISDN ATM adaptation layer sublayers: service specific coordination function to provide the connection-oriented transport service.
[17] I.365.3，B-ISDN ATM适配层子层：提供面向连接的传输服务的特定于服务的协调功能。
[18] Kumar, R. and M. Mostafa, "Conventions for the use of the Session Description Protocol (SDP) for ATM Bearer Connections", RFC 3108, May 2001.
[18] Kumar，R.和M.Mostafa，“ATM承载连接使用会话描述协议（SDP）的公约”，RFC 3108，2001年5月。
[19] ITU I.371, Traffic Control and Congestion Control in the BISDN.
[19] ITU I.371，BISDN中的流量控制和拥塞控制。
[20] ATMF Circuit Emulation Service (CES) Interoperability Specification, af-vtoa-0078.000.
[20] ATMF电路仿真服务（CES）互操作性规范，af-vtoa-0078.000。
[21] af-vmoa-0145.000, Voice and Multimedia over ATM, Loop Emulation Service using AAL2.
[21] af-vmoa-0145.000，ATM上的语音和多媒体，使用AAL2的环路模拟服务。
[22] ITU-T H.222.1, Multimedia multiplex and synchronization for audiovisual communication in ATM environments.
[22] ITU-T H.222.1，ATM环境中视听通信的多媒体多路复用和同步。
[23] FRF.5, Frame Relay/ATM PVC Network Interworking Implementation Agreement.
[23] FRF.5，帧中继/ATM PVC网络互通实施协议。
[24] FRF.8, Frame Relay/ATM PVC Service Interworking Implementation Agreement.
[24] FRF.8，帧中继/ATM PVC业务互通实施协议。
[25] FRF.11, Voice over Frame Relay Implementation Agreement.
[25] FRF.11，语音帧中继实施协议。
[26] Handley, M. and V. Jacobson, "SDP: Session Description Protocol", RFC 2327, April 1998.
[26] Handley，M.和V.Jacobson，“SDP：会话描述协议”，RFC 2327，1998年4月。
[27] ITU-T I.363.5, B-ISDN ATM Adaptation Layer Specification: Type 5 AAL, Aug. 1996.
[27] ITU-T I.363.5，B-ISDN ATM适配层规范：5型AAL，1996年8月。
[28] I.365.4, B-ISDN ATM adaptation layer sublayers: Service specific convergence sublayer for HDLC applications.
[28] I.365.4，B-ISDN ATM适配层子层：HDLC应用的特定于服务的汇聚子层。
[29] ITU-T Q.2931, B-ISDN Application Protocol for Access Signaling.
[29] ITU-T Q.2931，接入信令的B-ISDN应用协议。
[30] ITU Q.765.5, Application Transport Mechanism - Bearer Independent Call Control.
[30] ITU Q.765.5，应用传输机制-承载独立呼叫控制。
[31] http://www.3gpp.org/ftp/Specs for specifications related to 3GPP, including AMR codecs.
[31] http://www.3gpp.org/ftp/Specs 有关3GPP的规范，包括AMR编解码器。
[32] ITU Q.931, Digital Subscriber Signaling System No. 1: Network Layer.
[32] ITU Q.931，数字用户信号系统第1号：网络层。
[33] ITU Q.763, SS7 - ISUP formats and codes.
[33] ITU Q.763，SS7-ISUP格式和代码。
[34] http://www.iana.org/assignments/rtp-parameters
[34] http://www.iana.org/assignments/rtp-parameters
[35] ATMF Voice and Telephony over ATM - ATM Trunking using AAL1 for Narrowband Services, version 1.0, af-vtoa-0089.000, July 1997.
[35] ATM上的ATMF语音和电话-使用AAL1的窄带业务ATM中继，版本1.0，af-vtoa-0089.000，1997年7月。
[36] Andreasen, F. and B. Foster, "Media Gateway Control Protocol (MGCP) Version 1.0", RFC 3435, January 2003.
[36] Andreasen，F.和B.Foster，“媒体网关控制协议（MGCP）1.0版”，RFC 3435，2003年1月。
[37] Handley, M. and V. Jacobson, "SDP: Session Description Protocol", RFC 2327, April 1998.
[37] Handley，M.和V.Jacobson，“SDP：会话描述协议”，RFC 2327，1998年4月。
[38] Foster, B., "MGCP CAS Packages", RFC 3064, February 2001.
[38] Foster，B.，“MGCP CAS包”，RFC 3064，2001年2月。
AAL ATM Adaptation Layer ABR Available Bit Rate ABT/DT ATM Block Transfer/Delayed Transmission ABT/IT ATM Block Transfer/Immediate Transmission ATM Asynchronous Transfer Mode ATMF ATM Forum BCG Bearer Connection Group CAS Channel Associated Signaling CBR Constant Bit Rate CDV Cell Delay Variation CDVT Cell Delay Variation Tolerance CID Channel Identifier CLR Cell Loss Ratio CPS Common Part Sublayer DBR Deterministic Bit Rate FEC Forward Error Correction FRF Frame Relay Format GFR Guaranteed Frame Rate GWID Gateway Identifier IP Internet Protocol ITU International Telecommunications Union LCO Local Connection Option MBS Maximum Burst Size MCR Minimum Cell Rate MFS Maximum Frame Size MGCP Media Gateway Control Protocol nrt-VBR Non-real-time Variable Bit Rate NSAP Network Service Access Point PCR Peak Cell Rate PDU Protocol Data Unit PVC Permanent Virtual Circuit QoS Quality of Service rt-VBR Real-time Variable Bit Rate SAR Segmentation and Re-assembly SCR Sustained Cell Rate SDT Structured Data Transfer SDU Service Data Unit SPVC Switched Permanent Virtual Circuit SRTS Synchronous Residual Time-Stamp SSCOP Service-specific Connection Oriented Protocol SSSAR Service-specific Segmentation and Re-assembly SVC Switched Virtual Circuit TDM Time-Division Multiplexing UBR Unspecified Bit Rate UDT Unstructured Data Transfer VC Virtual Circuit
AAL ATM适配层ABR可用比特率ABT/DT ATM块传输/延迟传输ABT/IT ATM块传输/即时传输ATM异步传输模式ATMF ATM论坛BCG承载连接组CAS信道相关信令CBR恒定比特率CDV信元延迟变化CDVT信元延迟变化容差CID信道标识符CLR信元丢失率CPS公共部分子层DBR确定性比特率FEC前向纠错FRF帧中继格式GFR保证帧速率GWID网关标识符IP Internet协议ITU国际电信联盟LCO本地连接选项MBS最大突发大小MCR最小信元速率MFS最大帧大小MGCP媒体网关控制协议nrt VBR非实时可变比特率NSAP网络服务接入点PCR峰值信元速率PDU协议数据单元PVC永久虚拟电路QoS服务质量rt VBR实时可变比特率SAR分段和重新组装SCR持续信元速率SDT结构化数据传输SDU服务数据单元SPVC交换永久虚拟电路SRTS同步剩余时间戳SSCOP特定于服务的面向连接协议SSSAR特定于服务的分段和重新组装SVC交换虚拟电路TDM时分复用UBR未指定比特率UDT非结构化数据传输VC虚拟电路
VCCI Virtual Circuit Connection Identifier VCI Virtual Circuit Identifier VP Virtual Path VPCI Virtual Path Connection Identifier VPI Virtual Path Identifier
VCCI虚拟电路连接标识符VCI虚拟电路标识符VP虚拟路径VPCI虚拟路径连接标识符VPI虚拟路径标识符
The author wishes to thank several colleagues at Cisco and the industry who have contributed towards the development of the MGCP ATM package, and who have implemented and tested these constructs. Special thanks are due to Bill Foster, Flemming Andreasen, Raghu Thirumalai Rajan, Joe Stone, Hisham Abdelhamid, Joseph Swaminathan, Sushma Srikanth, Amit Agrawal, Mohamed Mostafa, Latha Idury, David Auerbach and Robert Biskner of Cisco systems and to Mahamood Hussain of Hughes Software Systems for their contributions. Finally, thanks are due to Scott Bradner for guiding the final phase of the publication of this document.
作者希望感谢Cisco和业界的几位同事，他们为MGCP ATM包的开发做出了贡献，并实施和测试了这些结构。特别感谢思科系统公司的比尔·福斯特、弗莱明·安德烈森、拉古·蒂鲁玛莱·拉詹、乔·斯通、希沙姆·阿卜杜勒哈米德、约瑟夫·斯瓦米纳坦、苏希玛·斯利坎特、阿米特·阿格拉瓦尔、穆罕默德·莫斯塔法、拉塔·艾杜里、大卫·奥尔巴赫和罗伯特·比斯克纳以及休斯软件系统公司的马哈茂德·侯赛因，感谢他们的贡献。最后，感谢Scott Bradner指导本文件出版的最后阶段。
Rajesh Kumar Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA 95134-1706
Rajesh Kumar Cisco Systems，Inc.加利福尼亚州圣何塞西塔斯曼大道170号，邮编95134-1706
Phone: 1-408-527-0811 EMail: rkumar@cisco.com
电话：1-408-527-0811电子邮件：rkumar@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 assigns.
上述授予的有限许可是永久性的，互联网协会或其继承人或受让人不会撤销。
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编辑功能的资金目前由互联网协会提供。