Network Working Group B. Foster
Request for Comments: 3660 F. Andreasen
Updates: 2705 Cisco Systems
Category: Informational December 2003
Network Working Group B. Foster
Request for Comments: 3660 F. Andreasen
Updates: 2705 Cisco Systems
Category: Informational December 2003
Basic Media Gateway Control Protocol (MGCP) Packages
基本媒体网关控制协议（MGCP）包
Status of this Memo
本备忘录的状况
This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited.
本备忘录为互联网社区提供信息。它没有规定任何类型的互联网标准。本备忘录的分发不受限制。
Copyright Notice
版权公告
Copyright (C) The Internet Society (2003). All Rights Reserved.
版权所有（C）互联网协会（2003年）。版权所有。
IESG Note
IESG注释
This document is being published for the information of the community. It describes a non-IETF protocol that is currently being deployed in a number of products. Implementers should be aware of RFC 3525 [37], which was developed in the IETF Megaco Working Group and the ITU-T SG16, and is considered by the IETF and ITU-T to be the standards-based (including reviewed security considerations) way to meet the needs that MGCP was designed to address. The IETF Megaco Working Group and the ITU-T Study Group 16 are developing extensions to RFC 3525 [37] that for functions of the type in addressed in this document.
本文件发布供社区参考。它描述了目前正在许多产品中部署的非IETF协议。实施者应了解RFC 3525[37]，它是在IETF Megaco工作组和ITU-T SG16中开发的，并且被IETF和ITU-T视为基于标准（包括经审查的安全考虑）的方式，以满足MGCP旨在满足的需求。IETF Megaco工作组和ITU-T研究组16正在开发RFC 3525[37]的扩展，用于本文件中所述类型的功能。
Abstract
摘要
This document provides a basic set of Media Gateway Control Protocol (MGCP) packages. The generic, line, trunk, handset, RTP, DTMF (Dual Tone Multifrequency), announcement server and script packages are updates of packages from RFC 2705 with additional explanation and in some cases new versions of these packages. In addition to these, five new packages are defined here. These are the signal list, resource reservation, media format, supplementary services and digit map extension packages.
本文档提供了一组基本的媒体网关控制协议（MGCP）包。通用、线路、中继线、手持设备、RTP、DTMF（双音多频）、公告服务器和脚本软件包是RFC 2705软件包的更新，并附有附加说明，在某些情况下是这些软件包的新版本。除此之外，这里还定义了五个新包。这些是信号列表、资源预留、媒体格式、补充服务和数字地图扩展包。
Table of Contents
目录
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. List of Packages . . . . . . . . . . . . . . . . . . . . 3
1.2. Changes to Existing RFC 2705 Packages. . . . . . . . . . 3
1.2.1. Change in Signal Types . . . . . . . . . . . . . 3
1.2.2. Operation Complete and Operation Failure . . . . 3
1.2.3. Package Versions . . . . . . . . . . . . . . . . 4
1.2.4. Event Definitions, Aliases and Interoperability
Issues . . . . . . . . . . . . . . . . . . . . . 4
1.2.5. New Events . . . . . . . . . . . . . . . . . . . 5
1.3. New Packages and Excluded Packages . . . . . . . . . . . 5
2. Packages . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
2.1. Generic Media Package. . . . . . . . . . . . . . . . . . 7
2.2. DTMF Package . . . . . . . . . . . . . . . . . . . . . . 11
2.3. Trunk Package. . . . . . . . . . . . . . . . . . . . . . 16
2.4. Line Package . . . . . . . . . . . . . . . . . . . . . . 24
2.5. Handset Emulation Package. . . . . . . . . . . . . . . . 33
2.6. Supplementary Services Tone Package. . . . . . . . . . . 36
2.7. Digit Map Extension. . . . . . . . . . . . . . . . . . . 37
2.8. Signal List Package. . . . . . . . . . . . . . . . . . . 38
2.9. Media Format Parameter Package . . . . . . . . . . . . . 39
2.10. RTP Package. . . . . . . . . . . . . . . . . . . . . . . 43
2.11. Resource Reservation Package . . . . . . . . . . . . . . 48
2.11.1. Description. . . . . . . . . . . . . . . . . . . 48
2.11.2. Parameter Encoding . . . . . . . . . . . . . . . 52
2.11.3. Events . . . . . . . . . . . . . . . . . . . . . 53
2.12. Announcement Server Package. . . . . . . . . . . . . . . 55
2.13. Script Package . . . . . . . . . . . . . . . . . . . . . 56
3. IANA Considerations. . . . . . . . . . . . . . . . . . . . . . 59
4. Security Considerations. . . . . . . . . . . . . . . . . . . . 59
5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 59
6. References . . . . . . . . . . . . . . . . . . . . . . . . . . 60
6.1. Normative References . . . . . . . . . . . . . . . . . . 60
6.2. Informative References . . . . . . . . . . . . . . . . . 62
7. Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 63
8. Full Copyright Statement . . . . . . . . . . . . . . . . . . . 64
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. List of Packages . . . . . . . . . . . . . . . . . . . . 3
1.2. Changes to Existing RFC 2705 Packages. . . . . . . . . . 3
1.2.1. Change in Signal Types . . . . . . . . . . . . . 3
1.2.2. Operation Complete and Operation Failure . . . . 3
1.2.3. Package Versions . . . . . . . . . . . . . . . . 4
1.2.4. Event Definitions, Aliases and Interoperability
Issues . . . . . . . . . . . . . . . . . . . . . 4
1.2.5. New Events . . . . . . . . . . . . . . . . . . . 5
1.3. New Packages and Excluded Packages . . . . . . . . . . . 5
2. Packages . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
2.1. Generic Media Package. . . . . . . . . . . . . . . . . . 7
2.2. DTMF Package . . . . . . . . . . . . . . . . . . . . . . 11
2.3. Trunk Package. . . . . . . . . . . . . . . . . . . . . . 16
2.4. Line Package . . . . . . . . . . . . . . . . . . . . . . 24
2.5. Handset Emulation Package. . . . . . . . . . . . . . . . 33
2.6. Supplementary Services Tone Package. . . . . . . . . . . 36
2.7. Digit Map Extension. . . . . . . . . . . . . . . . . . . 37
2.8. Signal List Package. . . . . . . . . . . . . . . . . . . 38
2.9. Media Format Parameter Package . . . . . . . . . . . . . 39
2.10. RTP Package. . . . . . . . . . . . . . . . . . . . . . . 43
2.11. Resource Reservation Package . . . . . . . . . . . . . . 48
2.11.1. Description. . . . . . . . . . . . . . . . . . . 48
2.11.2. Parameter Encoding . . . . . . . . . . . . . . . 52
2.11.3. Events . . . . . . . . . . . . . . . . . . . . . 53
2.12. Announcement Server Package. . . . . . . . . . . . . . . 55
2.13. Script Package . . . . . . . . . . . . . . . . . . . . . 56
3. IANA Considerations. . . . . . . . . . . . . . . . . . . . . . 59
4. Security Considerations. . . . . . . . . . . . . . . . . . . . 59
5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 59
6. References . . . . . . . . . . . . . . . . . . . . . . . . . . 60
6.1. Normative References . . . . . . . . . . . . . . . . . . 60
6.2. Informative References . . . . . . . . . . . . . . . . . 62
7. Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 63
8. Full Copyright Statement . . . . . . . . . . . . . . . . . . . 64
This document provides a basic set of Media Gateway Control Protocol (MGCP) packages. The generic, line, trunk, handset, RTP, DTMF, announcement server and script packages are updates of packages from RFC 2705 [38] with additional explanation and in some cases new versions of these packages. In addition to these, five new packages are defined here. These are the signal list, resource reservation, media format, supplementary services and digit map extension packages.
本文档提供了一组基本的媒体网关控制协议（MGCP）包。通用包、线路包、中继包、手持包、RTP包、DTMF包、公告服务器包和脚本包是RFC 2705[38]中包的更新，并附有附加说明，在某些情况下还包括这些包的新版本。除此之外，这里还定义了五个新包。这些是信号列表、资源预留、媒体格式、补充服务和数字地图扩展包。
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 [31].
本文件中的关键词“必须”、“不得”、“要求”、“应”、“不应”、“应”、“不应”、“建议”、“可”和“可选”应按照BCP 14、RFC 2119[31]中的描述进行解释。
The basic set of packages specified in this document is for use with MGCP 1.0 as defined in [1]. Included are the following packages:
本文件中规定的基本包集用于[1]中定义的MGCP 1.0。包括以下软件包：
-------------------------------------------
| Package | Name |
|-------------------------------------------|
| Generic Media Package | G |
| DTMF package | D |
| Trunk Package | T |
| Line Package | L |
| Handset Package | H |
| Supplementary Services Package | SST |
| Digit Map Extension | DM1 |
| Signal List Package | SL |
| Media Format Package | FM |
| RTP Package | R |
| Resource Reservation Package | RES |
| Announcement Server Package | A |
| Script Package | Script |
-------------------------------------------
-------------------------------------------
| Package | Name |
|-------------------------------------------|
| Generic Media Package | G |
| DTMF package | D |
| Trunk Package | T |
| Line Package | L |
| Handset Package | H |
| Supplementary Services Package | SST |
| Digit Map Extension | DM1 |
| Signal List Package | SL |
| Media Format Package | FM |
| RTP Package | R |
| Resource Reservation Package | RES |
| Announcement Server Package | A |
| Script Package | Script |
-------------------------------------------
MGCP 1.0, as defined in RFC 2705 [38] (and now updated in [1]), provided some additional clarification on the meaning of On-Off (OO) signals compared to earlier versions of MGCP. This lead to some inconsistency in some of the signal definitions in the accompanying packages in RFC 2705 [38]. This has been corrected in the packages that are included here by changing some of the signals from type On-Off to type Time-Out (TO).
RFC 2705[38]中定义的MGCP 1.0（现在在[1]中更新）与MGCP的早期版本相比，对开关（OO）信号的含义提供了一些额外的澄清。这导致RFC 2705[38]中随附软件包中的一些信号定义存在一些不一致性。通过将某些信号从类型On Off更改为类型Time Out（到），在此处包含的软件包中对此进行了纠正。
Another change made to improve consistency and interoperability was to add the "operation complete" and "operation failure" events in packages where there are TO signals defined, but where the "operation complete" and "operation failure" events were not previously included as part of the package. By definition, all packages that contain
为提高一致性和互操作性而进行的另一项更改是在包中添加“操作完成”和“操作失败”事件，其中定义了信号，但“操作完成”和“操作失败”事件以前未作为包的一部分包含在包中。根据定义，包含
Time-Out type signals now contain the "operation failure" ("of") and "operation complete" ("oc") events as defined in [1], irrespective of whether they are provided as part of the package description or not.
超时类型信号现在包含[1]中定义的“操作失败”（“of”）和“操作完成”（“oc”）事件，无论它们是否作为包说明的一部分提供。
If a package without Time-Out signals contains definitions for the "oc" and "of" events, the event definitions provided in the package may over-ride those indicated here. Such practice is however discouraged and is purely allowed to avoid potential backwards compatibility problems.
如果没有超时信号的程序包包含“oc”和“of”事件的定义，则程序包中提供的事件定义可能超过此处所示的定义。然而，这种做法是不鼓励的，纯粹是为了避免潜在的向后兼容性问题。
It is considered good practice to explicitly mention that the "oc" and "of" events are supported in accordance with their default definitions. If no definition is included in the package, the default syntax and semantics are assumed.
明确提及“oc”和“of”事件是根据其默认定义支持的，这被认为是良好的实践。如果包中未包含任何定义，则采用默认语法和语义。
Please refer to [1] for additional details on these events.
有关这些活动的更多详细信息，请参阅[1]。
The generic, line, trunk, handset, RTP, DTMF, announcement server and script packages included in this document are new versions of packages that were previously contained in RFC 2705 [38]. The updated base MGCP 1.0 specification [1] provides an optional capability of auditing package versions. Any gateway that implements versioned packages SHOULD also implement this option.
本文档中包含的通用、线路、中继、手持设备、RTP、DTMF、公告服务器和脚本软件包是RFC 2705[38]中先前包含的软件包的新版本。更新的基本MGCP 1.0规范[1]提供了审计包版本的可选功能。任何实现版本化包的网关也应实现此选项。
Some event definitions or clarifications of previous event definitions have also been added in order to improve interoperability.
为了提高互操作性，还添加了一些事件定义或先前事件定义的澄清。
In some cases, events have aliases either in the same or in other packages and a recommendation has been made for the use of alternates by Call Agents for future implementations. For maximum interoperability, gateways MUST still implement these events (in fact they MUST always implement all of the events, signals, etc. in a package).
在某些情况下，事件在相同或其他包中都有别名，并且建议调用代理在将来的实现中使用替代项。为了实现最大的互操作性，网关仍然必须实现这些事件（事实上，它们必须始终实现包中的所有事件、信号等）。
Some events that were previously defined require specific provisioning in both the gateway and the Call Agent in order to allow for interoperability. In those cases, a warning to that affect has been included.
以前定义的某些事件需要在网关和呼叫代理中进行特定的配置，以便实现互操作性。在这些情况下，已经包括了对这种影响的警告。
In some cases, new events have been added to existing packages. Any changes to existing packages of course have resulted in the package version number being updated from unversioned (version 0) to version 1.
在某些情况下，新事件已添加到现有包中。当然，对现有软件包的任何更改都会导致软件包版本号从未版本（版本0）更新为版本1。
Two packages from RFC 2705 [38] have not been included. These are the "MF" and the "NAS" packages. These packages are still valid as are all unversioned (version 0) packages defined in RFC 2705 [38]. The reason these packages were not included are:
RFC 2705[38]中的两个包未包含在内。这些是“MF”和“NAS”软件包。这些包与RFC 2705[38]中定义的所有未版本（版本0）包一样仍然有效。未包括这些软件包的原因是：
* The original MF package had no defined way to outpulse MF digits so that MF CAS is now provided by other packages (i.e., the "MS", "MO" and "MD" packages) in a separate document.
* 原始MF包没有定义输出MF数字的方法，因此MF CA现在由其他包（即“MS”、“MO”和“MD”包）在单独的文档中提供。
* The "N" package, as defined in RFC 2705 [38], was incomplete. A new MGCP "NAS" package has been developed and provided in a separate document.
* RFC 2705[38]中定义的“N”包不完整。已开发了一个新的MGCP“NAS”包，并在另一份文件中提供。
New packages have also been included beyond what was included in RFC 2705 [38]. These are the signal list, resource reservation, media format, supplementary services and digit map extension packages. The Resource Reservation ("RES") and Media Format ("FM") packages in particular are different from other packages in this document in that they contain new LocalConnectionOptions. This is allowed by the new extension rules in [1]. Future packages of this type MUST use a packages prefix in front of local connection options ("<package-name>/<Local Connection Option>") so as to avoid name-space problems. However because of the timing of the arrival of these packages relative to updating MGCP 1.0, this was not done for the "RES" and "FM" packages. The resulting new local connection options have been registered with IANA. For future cases where a package prefix is included, only the package name needs to be registered.
除了RFC 2705[38]中包含的内容外，还包含了新的软件包。这些是信号列表、资源预留、媒体格式、补充服务和数字地图扩展包。资源保留（“RES”）和媒体格式（“FM”）包与本文档中的其他包不同，它们包含新的LocalConnectionOptions。[1]中的新扩展规则允许这样做。此类型的未来包必须在本地连接选项前面使用包前缀（“<package name>/<local connection Option>”），以避免名称空间问题。但是，由于这些包的到达时间与更新MGCP 1.0有关，“RES”和“FM”包没有这样做。由此产生的新本地连接选项已向IANA注册。对于包含包前缀的未来情况，只需要注册包名称。
For those packages that involve MGCP events, the terms "signal" and "event" are used to differentiate a request from a Call Agent to a Media Gateway to apply an event ("signal"), from the request for the detection of an "event" that occurs on the Media Gateway and is "Notified" to the Call Agent.
对于涉及MGCP事件的那些包，术语“信号”和“事件”用于区分呼叫代理对媒体网关应用事件（“信号”）的请求与对媒体网关上发生并被“通知”给呼叫代理的“事件”的检测请求。
For packages that involve events and signals, the tables contain five columns:
对于涉及事件和信号的包，表包含五列：
Symbol: the (package) unique symbol used to identify the event.
符号：用于标识事件的（包）唯一符号。
Definition: a short description of the event.
定义：事件的简短描述。
R: an x appears in this column if the event can be requested by the Call Agent. Alternatively, one or more of the following symbols may appear. An "S" is included if the event-state may be audited. A "C" indicates that the event can be detected on a connection, and a "P" indicates the event is persistent.
R：如果呼叫代理可以请求事件，则此列中会显示一个x。或者，可能会出现以下一个或多个符号。如果可以审核事件状态，则包含“S”。“C”表示可以在连接上检测到该事件，“P”表示该事件是持久的。
S: if nothing appears in this column for an event, then the event cannot be signaled by the Call Agent. Otherwise, the following symbols identify the type of event:
S：如果此列中没有显示任何事件，则呼叫代理无法通知该事件。否则，以下符号表示事件类型：
* OO On/Off signal
* OO开/关信号
* TO Time-Out signal.
* 暂停信号。
* BR Brief signal.
* BR短信号。
In addition, a "C" will be included if the signal can be generated on a connection.
此外，如果可以在连接上生成信号，则将包括“C”。
Duration: specifies the default duration of TO signals. If a duration is left unspecified, then the default timeout will be assumed to be infinite, unless explicitly noted in the description of the signal. A duration may also be declared as being variable in a case where signals involve complex sequencing (e.g., scripts or digit out-pulsing) where the amount of time may vary with either processing time or the signaling environment.
持续时间：指定到信号的默认持续时间。如果未指定持续时间，则默认超时将假定为无限，除非在信号说明中明确说明。在信号涉及复杂排序（例如，脚本或数字输出脉冲）的情况下，持续时间也可以被声明为可变的，其中时间量可以随处理时间或信令环境而变化。
Default time-out values may be over-ridden by the Call Agent for any Time-Out event defined in this document (with the exception of those that have a default value of "variable") by a "to" signal parameter which specifies the timeout value in milliseconds (see [1]). The following example indicates a timeout value of 20 seconds:
对于本文档中定义的任何超时事件（默认值为“variable”的事件除外），调用代理可能会通过“to”信号参数覆盖默认超时值，该参数以毫秒为单位指定超时值（请参见[1]）。以下示例指示20秒的超时值：
S: sst/cw(to=20000)
S: sst/cw(to=20000)
As indicated in [1]: by default, a supplied time-out value MAY be rounded to the nearest non-zero value divisible by 1000, i.e., whole second. However, individual signal definitions within a package may define other rounding rules.
如[1]所示：默认情况下，提供的超时值可以四舍五入到可被1000整除的最接近的非零值，即整秒。但是，包内的单个信号定义可能定义其他舍入规则。
Note that Time-Out signals that involve other parameters still allow the use of the "to" signal parameter e.g.:
请注意，涉及其他参数的超时信号仍允许使用“至”信号参数，例如：
S: T/sit(1,to=3000)
S: T/sit(1,to=3000)
The order of the "to" parameter relative to the other parameters is not important.
“to”参数相对于其他参数的顺序并不重要。
Note: as per [1], On-Off (OO) signals are parameterized with "+" (meaning turn on) or "-" (meaning turn off). If the parameter is missing, the default is to turn on the signal. Unlike Time-Out signals, On-Off signals do not stop when an event occurs.
注：根据[1]，开-关（OO）信号用“+”（表示打开）或“-”（表示关闭）参数化。如果缺少该参数，则默认为打开信号。与超时信号不同，开-关信号在事件发生时不会停止。
Other than the "to" parameter for Time-out (TO) signals and the "+" and "-" for On-Off (OO) signals, signals and events in the packages in this document do not have parameters unless explicitly indicated in the description of the event for that package.
除了超时（to）信号的“to”参数和开关（OO）信号的“+”和“-”参数外，本文件中的包中的信号和事件没有参数，除非在该包的事件描述中明确指出。
In some of the signal definitions below, specific tone definitions are provided even though actual frequencies may vary from country to country.
在下面的一些信号定义中，提供了特定的音调定义，即使实际频率可能因国家而异。
Package Name: G Version: 1
软件包名称：G版本：1
The generic media package groups the events and signals that can be observed on several types of endpoints, such as trunk gateway endpoints, access gateway endpoints or residential gateway endpoints.
通用媒体包将可在几种类型的端点（如中继网关端点、访问网关端点或住宅网关端点）上观察到的事件和信号分组。
---------------------------------------------------------------
| Symbol | Definition | R | S Duration |
|---------------------------------------------------------------|
| cf | Confirm Tone | | BR |
| cg | Congestion Tone | | TO infinite |
| ft | Fax Tone | x | |
| it | Intercept Tone | | TO infinite |
| ld | Long Duration Connection | C | |
| mt | Modem Tone | x | |
| oc | Operation Complete | x | |
| of | Operation Failure | x | |
| pat(###) | Pattern Detected | x | OO |
| pt | Preemption Tone | | TO infinite |
| rbk(...) | Ringback | | TO,C 180 seconds|
| rt | Ringback Tone | | TO,C 180 seconds|
---------------------------------------------------------------
---------------------------------------------------------------
| Symbol | Definition | R | S Duration |
|---------------------------------------------------------------|
| cf | Confirm Tone | | BR |
| cg | Congestion Tone | | TO infinite |
| ft | Fax Tone | x | |
| it | Intercept Tone | | TO infinite |
| ld | Long Duration Connection | C | |
| mt | Modem Tone | x | |
| oc | Operation Complete | x | |
| of | Operation Failure | x | |
| pat(###) | Pattern Detected | x | OO |
| pt | Preemption Tone | | TO infinite |
| rbk(...) | Ringback | | TO,C 180 seconds|
| rt | Ringback Tone | | TO,C 180 seconds|
---------------------------------------------------------------
New events added to this package from the previously unversioned package: "oc"
从以前未版本化的包中添加到此包的新事件：“oc”
Changes: "it" and "pt" signals changed from OO to TO.
变化：“it”和“pt”信号从OO变为。
Note that default time-out values may be over-ridden by the Call Agent for any Time-Out signal defined in this package by a "to" signal parameter. Refer to section 2 of this document, as well as [1] for details.
请注意，对于此包中由“to”信号参数定义的任何超时信号，调用代理可能会覆盖默认超时值。有关详细信息，请参阅本文件第2节以及[1]。
The events and signals are defined as follows:
事件和信号定义如下：
Confirmation Tone (cf): This is also referred to as "positive indication tone" in ITU-T E.182. In North America, Confirmation Tone uses the same frequencies and levels as dial tone (350 and 440 Hertz) but with a cadence of 0.1 second on, 0.1 second off, repeated three times. See GR-506-CORE [7] Section 17.2.4. It is considered an error to try and play confirmation tone on a phone that is on-hook and an error MUST consequently be returned when such attempts are made (error code 402 - phone on-hook).
确认音（cf）：在ITU-T E.182中也称为“肯定指示音”。在北美，确认音使用与拨号音相同的频率和音量（350和440赫兹），但频率为0.1秒打开，0.1秒关闭，重复三次。参见GR-506-CORE[7]第17.2.4节。尝试在挂机的电话上播放确认音被视为错误，因此在进行此类尝试时必须返回错误（错误代码402-挂机电话）。
Congestion Tone (cg): Refer to ITU-T E.180 [8] and E.182 [10]. This maps to re-order tone in North America (refer to GR-506-CORE [7] Section 17.2.7).
拥塞音（cg）：参考ITU-T E.180[8]和E.182[10]。这映射到北美的重新订购音调（参考GR-506-CORE[7]第17.2.7节）。
Fax Tone (ft): The fax tone event is generated whenever a fax call is detected by the presence of V.21 fax preamble. The fax tone event SHOULD also be generated when the T.30 CNG tone is detected. See ITU-T Recommendations T.30 [21] and V.21 [22].
传真音（ft）：只要存在V.21传真前导码检测到传真呼叫，就会生成传真音事件。当检测到T.30 CNG音调时，也应生成传真音调事件。见ITU-T建议T.30[21]和V.21[22]。
Intercept Tone(it): This is a country specific tone as defined in ITU-T E.180 Supplement 2 [9].
截获音（it）：这是ITU-T E.180补编2[9]中定义的特定于国家的音。
Long Duration Connection (ld): The "long duration connection" is detected when a connection has been established for more than a provisioned amount of time. The default value is 1 hour.
长持续时间连接（ld）：当建立连接的时间超过规定的时间量时，会检测到“长持续时间连接”。默认值为1小时。
This event is detected on a connection. When no connection is specified as part of the request, the event applies to all connections for the endpoint, regardless of when the connections are created. The "all connections" wildcard (see [1]) may also be used for this case, and is in fact preferred for consistency. In
在连接上检测到此事件。当请求中未指定任何连接时，事件将应用于端点的所有连接，而不管连接是在何时创建的。“所有连接”通配符（见[1]）也可用于这种情况，事实上，为了保持一致性，最好使用通配符。在里面
either case, the name of the connection on which the event was detected will be included when the event is observed, e.g.:
无论哪种情况，在观察到事件时，都会包括检测到事件的连接的名称，例如：
G/ld@0A3F58
G/ld@0A3F58
Modem Tone (mt): Indicates V.25 Answer tone (ANS) with or without phase reversals or V.8 Modified Answer Tone (ANSam) tone with or without phase reversals. Note that this implies the presence of a data call. Also note that despite the name of the event, devices other than modems may generate such tones, e.g., a fax machine.
调制解调器音调（mt）：表示带或不带相位反转的V.25应答音（ANS）或带或不带相位反转的V.8修改应答音（ANSam）音调。请注意，这意味着存在数据调用。还请注意，尽管事件的名称不同，但调制解调器以外的设备可能会生成此类音调，例如传真机。
Operation Complete (oc): The standard definition of operation complete [1].
操作完成（oc）：操作完成的标准定义[1]。
Operation Failure (of): The standard definition of operation failure [1].
操作失败（of）：操作失败的标准定义[1]。
Pattern Detected (pat(###)): This event requires special provisioning that needs to be agreed on between the Call Agent and media gateway in order to ensure interoperability. It is retained in order to maintain backwards compatibility with version 0 of the "G" package. This event MUST be parameterized with a decimal numeric value from 0 to 999 specifying the pattern to detect. When reported, the pattern is also included as a parameter.
检测到模式（pat（#####））：此事件需要特殊的设置，需要在呼叫代理和媒体网关之间达成一致，以确保互操作性。保留它是为了保持与“G”包版本0的向后兼容性。必须使用0到999之间的十进制数值参数化此事件，以指定要检测的模式。报告时，模式也作为参数包含。
Preemption Tone (pt): This is a country specific tone and is defined in ITU-T E.180 Supplement 2 [9].
先占权音调（pt）：这是一种特定于国家的音调，定义见ITU-T E.180增补2[9]。
Ringback (rbk(connectionID)): This is an alias for "rt@connectionID" and is included here for backwards compatibility only. It is recommended that Call Agents use "rt@connectionID" instead of "rbk(connectionID)" for ring-back over a connection for new implementations. Although the ringback signal is applied on a connection, the "rbk" signal does not support the "@connection" syntax. When the signal is requested, it MUST be parameterized with a connection-ID or a connection-ID wildcard as specified in [1].
回铃（rbk（connectionID））：这是“”的别名rt@connectionID“并包含在此处，仅用于向后兼容。建议呼叫代理使用“rt@connectionID而不是“rbk（connectionID）”，用于通过新实现的连接进行回铃。尽管回响信号应用于连接，“rbk”信号不支持“@connection”语法。请求信号时，必须使用[1]中指定的连接ID或连接ID通配符对其进行参数化。
Ringback Tone (rt): Refer to ITU-T E.180 [8] and ITU-T E.182 [10]. Also referred to as ringing tone - a tone advising the caller that a connection has been made and that a calling signal is being applied to the called party or service point. In North America, this tone is a combination of two AC tones with frequencies of 440 and 480 Hertz and levels of -19 dBm each, to give a combined level of -16 dBm.
回铃音（rt）：参考ITU-T E.180[8]和ITU-T E.182[10]。也被称为铃声-一种提示呼叫者已建立连接且呼叫信号正应用于被叫方或服务点的铃声。在北美，这种音调是两种交流音调的组合，频率分别为440和480赫兹，电平分别为-19 dBm，组合电平为-16 dBm。
The cadence for Audible Ring Tone is 2 seconds on, followed by 4 seconds off. See GR-506-CORE [7] - LSSGR: SIGNALING, Section 17.2.5.
可听铃声的节拍为开启2秒，然后关闭4秒。参见GR-506-CORE[7]-LSSGR：信号，第17.2.5节。
This signal can be applied directly to an endpoint or alternatively on a connection using the syntax "rt@connectionID". When the ringback signal is applied to an endpoint, it is considered an error to try and play ringback tone if the endpoint is considered on-hook, and an error MUST consequently be returned when such attempts are made (error code 402 - phone on-hook). When the ringback signal is applied to a connection, no such check is to be made.
此信号可以直接应用于端点，也可以使用以下语法应用于连接”rt@connectionID". 当向端点应用回铃信号时，如果端点被视为挂机，则尝试并播放回铃音被视为错误，并且在进行此类尝试时必须返回错误（错误代码402-挂机电话）。当回铃信号应用于连接时，不进行此类检查。
Note that as specified in [1], signals requested on a connection MUST be played regardless of the connection mode. For example, in a call-waiting situation, ringback tone may be played on a connection in "inactive" mode.
请注意，如[1]中所述，无论连接模式如何，都必须播放连接上请求的信号。例如，在呼叫等待情况下，可以在“非活动”模式下的连接上播放回铃音。
Package name: D Version: 1
软件包名称：D版本：1
--------------------------------------------------------------
| Symbol | Definition | R | S Duration |
|--------------------------------------------------------------|
| 0 | DTMF 0 | x | BR |
| 1 | DTMF 1 | x | BR |
| 2 | DTMF 2 | x | BR |
| 3 | DTMF 3 | x | BR |
| 4 | DTMF 4 | x | BR |
| 5 | DTMF 5 | x | BR |
| 6 | DTMF 6 | x | BR |
| 7 | DTMF 7 | x | BR |
| 8 | DTMF 8 | x | BR |
| 9 | DTMF 9 | x | BR |
| # | DTMF # | x | BR |
| * | DTMF * | x | BR |
| A | DTMF A | x | BR |
| B | DTMF B | x | BR |
| C | DTMF C | x | BR |
| D | DTMF D | x | BR |
| DD(..) | DTMF Tone Duration | x | TO 3 seconds |
| DO(..) | DTMF OO Signal | | OO |
| L | Long Duration Indicator | x | |
| oc | Operation Complete | x | |
| of | Operation Failure | x | |
| T | Interdigit Timer | x | TO 16 seconds |
| X | DTMF Tones Wildcard, | x | |
| | match any digit 0-9 | | |
--------------------------------------------------------------
--------------------------------------------------------------
| Symbol | Definition | R | S Duration |
|--------------------------------------------------------------|
| 0 | DTMF 0 | x | BR |
| 1 | DTMF 1 | x | BR |
| 2 | DTMF 2 | x | BR |
| 3 | DTMF 3 | x | BR |
| 4 | DTMF 4 | x | BR |
| 5 | DTMF 5 | x | BR |
| 6 | DTMF 6 | x | BR |
| 7 | DTMF 7 | x | BR |
| 8 | DTMF 8 | x | BR |
| 9 | DTMF 9 | x | BR |
| # | DTMF # | x | BR |
| * | DTMF * | x | BR |
| A | DTMF A | x | BR |
| B | DTMF B | x | BR |
| C | DTMF C | x | BR |
| D | DTMF D | x | BR |
| DD(..) | DTMF Tone Duration | x | TO 3 seconds |
| DO(..) | DTMF OO Signal | | OO |
| L | Long Duration Indicator | x | |
| oc | Operation Complete | x | |
| of | Operation Failure | x | |
| T | Interdigit Timer | x | TO 16 seconds |
| X | DTMF Tones Wildcard, | x | |
| | match any digit 0-9 | | |
--------------------------------------------------------------
Changes from the previous version of the package: events "dd", "do", "oc" were added.
与包的上一版本相比的更改：添加了事件“dd”、“do”、“oc”。
Note that DTMF tones including the DTMF tones wildcard can use the eventRange notation defined in [1] when requesting events, e.g., "D/[0-9](N)".
请注意，在请求事件时，包括DTMF音调通配符在内的DTMF音调可以使用[1]中定义的eventRange表示法，例如，“D/[0-9]（N）”。
Note that default time-out values may be over-ridden by the Call Agent for any Time-Out signal defined in this package by a "to" signal parameter. Refer to section 2 of this document, as well as [1] for details.
请注意，对于此包中由“to”信号参数定义的任何超时信号，调用代理可能会覆盖默认超时值。有关详细信息，请参阅本文件第2节以及[1]。
The events are defined as follows:
事件定义如下：
DTMF tones (0-9,#,*,A,B,C,D): Detection and generation of DTMF tones is described in GR-506-CORE [7] - LSSGR: SIGNALING, Section 15. Note that it is considered an error to try and play DTMF tones on a phone that is on-hook and an error MUST consequently be returned when such attempts are made (error code 402 - phone on-hook). The event codes can be specified in a digit map. When requested as a signal, as per GR-506-CORE [7], section 15, a minimum tone duration of 50 ms will be followed by a minimum interdigit silence period of 45 ms, i.e., if requested in a signal list such as "S: sl/s(d/5,d/6,d/7)", then interdigit timing requirements will be satisfied.
DTMF音调（0-9、#、*、A、B、C、D）：DTMF音调的检测和生成在GR-506-CORE[7]-LSSGR:信令，第15节中进行了描述。请注意，在挂机的手机上尝试播放DTMF音调被视为错误，因此，在进行此类尝试时必须返回错误（错误代码402-挂机的手机）。事件代码可以在数字映射中指定。根据GR-506-CORE[7]第15节的规定，当请求作为信号时，最短音调持续时间为50 ms，随后是最短交指静音时间为45 ms，即，如果在信号列表中请求，如“S:sl/S（d/5，d/6，d/7）”，则满足交指定时要求。
Note that some types of endpoints, such as announcement endpoints, MAY allow detection and/or generation of a DTMF tone over a connection. However, this requires consistent provisioning between the Call Agent and announcement server (it is not required in order to be compliant with the DTMF package).
请注意，某些类型的端点（例如公告端点）可能允许通过连接检测和/或生成DTMF音调。但是，这需要在呼叫代理和公告服务器之间进行一致的配置（为了与DTMF包兼容，不需要这样做）。
DTMF Tone Duration (dd(dg=<tone>,to=<time>,su=<TrueOrFalse>)): This event can be used to indicate if/when the specified <tone> has a duration greater than the <time> value indicated (and is reported once the duration is exceeded). The parameters can be supplied in any order. The value of <tone> can be any of the DTMF tone symbols (without including the package name) specified in the DTMF package (including X in the case of events, but not signals). If this parameter is absent, any DTMF tone that occurs will be reported. The parameter <time> is in milli-seconds and may be rounded to the nearest 10 ms by the gateway. The minimum value of <time> that can be requested when requesting an event is 40 ms. When requesting a signal, the minimum value of <time> that can be requested is 50 ms. The maximum value of <time> that can be requested for either an event or a signal is 60000 ms. If the "to=<time>" parameter is absent when requested as an event, the event will report the full duration (up to 60000 ms) of the tone when the tone is completed. When reported as an ObservedEvent, both parameters are always supplied. In this case, <tone> is the actual tone detected and <time> is either:
DTMF音调持续时间（dd（dg=<Tone>，to=<time>，su=<TrueOrFalse>）：此事件可用于指示指定的<Tone>的持续时间是否/何时大于所指示的<time>值（并在超过持续时间后报告）。可按任何顺序提供参数。<tone>的值可以是DTMF包中指定的任何DTMF音调符号（不包括包名）（在事件情况下包括X，但不包括信号）。如果不存在此参数，将报告出现的任何DTMF音调。参数<时间>以毫秒为单位，网关可将其四舍五入至最接近的10毫秒。请求事件时可请求的<time>最小值为40 ms。请求信号时，可请求的<time>最小值为50 ms。可请求事件或信号的<time>最大值为60000 ms。如果作为事件请求时不存在“to=<time>”参数，当音调完成时，事件将报告音调的完整持续时间（高达60000毫秒）。当报告为观察事件时，始终提供这两个参数。在这种情况下，<tone>是检测到的实际音调，<time>是：
* The <time> specified in the request (possibly rounded), or
* 请求中指定的<time>（可能四舍五入），或
* If the request did not contain a "to=<time>" parameter, the full duration of the tone.
* 如果请求不包含“to=<time>”参数，则为音调的完整持续时间。
The parameter "su" MAY be included when this is requested as an event (but is not reported). This parameter is used to indicate whether or not the DTMF digits requested should be suppressed
当作为事件请求（但未报告）时，可包括参数“su”。此参数用于指示是否应抑制请求的DTMF数字
in-band when it is requested. Possible values are "true", indicating that in-band DTMF should be suppressed and "false" indicating that DTMF should continue to be passed in-band. The default value of the parameter, if missing, is "false". The "su" parameter MUST NOT be included when requesting "D/dd" as a signal.
当需要时，在频带内。可能的值为“真”，表示应抑制带内DTMF，“假”表示应继续在带内传递DTMF。参数的默认值（如果缺少）为“false”。请求“D/dd”作为信号时，不得包括“su”参数。
When used as a signal, "dd" provides the ability to generate a DTMF tone as a TO signal. When applied as a signal, an additional 50 ms of silence will be tacked onto the end before the operation complete occurs, i.e., "S: dd(dg=5,to=2500)" will play the DTMF tone for the number "5" for 2.5 seconds, followed by 50 ms of silence period. The operation complete (if requested) will be notified after the silence interval occurs. Any value from 50 ms to 60000 ms can be requested. Gateways generating or detecting the tone may round off the requested time to the nearest 10 ms.
当用作信号时，“dd”提供生成DTMF音调作为to信号的能力。当作为信号应用时，在操作完成之前，端部将附加50毫秒的静音，即，“S:dd（dg=5，to=2500）”将播放数字“5”的DTMF音调2.5秒，然后是50毫秒的静音期。静默间隔出现后，将通知操作完成（如果要求）。可以请求从50 ms到60000 ms的任何值。产生或检测音调的网关可以将请求的时间四舍五入到最接近的10毫秒。
The "dd" event can be used in place of the "long duration" event in order to detect a digit pressed for longer than 2 seconds. For example, in order to detect if a user presses the long "#" for longer than 2 seconds, a request could be made with the RequestedEvents line "R: d/dd(N)(dg=#,to=2000)". The resulting ObservedEvents line would be "O: d/dd(dg=#,to=2000)".
可使用“dd”事件代替“长持续时间”事件，以检测按下超过2秒的数字。例如，为了检测用户按下长“#”键是否超过2秒，可以使用RequestedEvents行“R:d/dd（N）（dg=#，to=2000）”发出请求。由此产生的ObservedEvents行将是“O:d/dd（dg=#，to=2000）”。
Suppose instead, that the RequestedEvents line contains
相反，假设RequestedEvents行包含
R: d/[0-9*#],d/dd
R: d/[0-9*#],d/dd
Suppose the user then pushes the "#" for 2.5 seconds. In this case, two events will be notified:
假设用户按下“#”键2.5秒。在这种情况下，将通知两个事件：
O: d/#
O: d/#
when the "#" key is first pressed, and
第一次按下“#”键时
O: d/dd(dg=#,to=2500)
O: d/dd(dg=#,to=2500)
when the "#" key is finally released.
当“#”键最终释放时。
DTMF OO Signal (do(dg=<tone>,<on-or-off>)):
This signal is used to generate a DTMF tone as an on-off signal.
The <tone> parameter is any of the symbols for a specific tone in
the DTMF package (i.e., "0" to "9", "A", "B", "C", "D", "*", or
"#"). The <on-or-off> indicator is "+" for on and "-" for off as
per [1]. The <tone> parameter MUST be supplied, otherwise a
return code of 538 - "Event/signal parameter error" will be
provided in the response. If the <on-or-off> parameter is
missing, the default is to turn the signal on as usual (i.e., "+"
is the default). The order of the parameters is not significant
DTMF OO Signal (do(dg=<tone>,<on-or-off>)):
This signal is used to generate a DTMF tone as an on-off signal.
The <tone> parameter is any of the symbols for a specific tone in
the DTMF package (i.e., "0" to "9", "A", "B", "C", "D", "*", or
"#"). The <on-or-off> indicator is "+" for on and "-" for off as
per [1]. The <tone> parameter MUST be supplied, otherwise a
return code of 538 - "Event/signal parameter error" will be
provided in the response. If the <on-or-off> parameter is
missing, the default is to turn the signal on as usual (i.e., "+"
is the default). The order of the parameters is not significant
since "+" and "-" are reserved characters and are easily distinguished from the <tone> parameter.
因为“+”和“-”是保留字符，很容易与<tone>参数区分开来。
Long Duration Indicator (l): The "long duration indicator" is observed when a DTMF signal is produced for a duration larger than two seconds. In this case, the gateway will detect two successive events: first, when the signal has been recognized, the DTMF signal, and then, 2 seconds later, the long duration signal.
长持续时间指示器（l）：当DTMF信号持续时间大于两秒时，观察到“长持续时间指示器”。在这种情况下，网关将检测两个连续事件：首先，当信号被识别时，DTMF信号，然后，2秒后，长持续时间信号。
Operation Complete (oc): This is the standard definition of operation complete [1].
操作完成（oc）：这是操作完成[1]的标准定义。
Operation Failure (of): This is the standard definition of operation failure [1].
操作失败（of）：这是操作失败的标准定义[1]。
Timer (t): Timer T can be used as an event or as a time-out (TO) signal. As a signal, its only behavior is the normal characteristics of a "TO" signal as defined in [1] (i.e., if no event occurs before the time-out, an operation complete event will be generated).
定时器（t）：定时器t可用作事件或超时（TO）信号。作为信号，其唯一行为是[1]中定义的“至”信号的正常特征（即，如果在超时之前没有发生事件，将生成操作完成事件）。
As an event, Timer T is a digit input timer that can be used in two ways:
作为一个事件，定时器T是一个数字输入定时器，可通过两种方式使用：
* When timer T is used with the accumulate according to digit map action, the timer is not started until the first DTMF tone is entered, and the timer is restarted after each new DTMF tone is entered until either a digit map match or mismatch occurs. In this case, timer T functions as an inter-digit timer as illustrated by:
* 当定时器T与“根据数字映射累积”动作一起使用时，在输入第一个DTMF音调之前，定时器不会启动，并且在输入每个新DTMF音调之后，定时器会重新启动，直到出现数字映射匹配或不匹配。在这种情况下，计时器T起到数字间计时器的作用，如图所示：
R: D/[0-9T](D)
R: D/[0-9T](D)
* When timer T is used without the "accumulate according to digit map" action, the timer is started immediately and simply cancelled (but not restarted) as soon as a DTMF tone is entered. In this case, timer T can be used as an inter-digit timer when overlap sending is used, as in:
* 如果使用定时器T时没有“根据数字映射累加”操作，则定时器立即启动，并在输入DTMF音后立即取消（但不重新启动）。在这种情况下，当使用重叠发送时，定时器T可用作数字间定时器，如：
R: D/[0-9](N), D/T(N)
R: D/[0-9](N), D/T(N)
When used with the "accumulate according to digit map" action, timer T takes on one of two values, T-partial or T-critical. When at least one more symbol is required for the "current dial string" to match any one of the patterns in the digit map, timer T takes on the value T-partial, corresponding to partial dial timing. If a timer is all that is required to produce a match, timer T takes
当与“根据数字映射累加”动作一起使用时，定时器T采用两个值中的一个，T-部分或T-临界。当“当前拨号串”需要至少一个以上的符号来匹配数字映射中的任何一个模式时，定时器T采用与部分拨号定时相对应的值T-partial。如果生成匹配只需要一个计时器，则计时器T将
on the value T-critical corresponding to critical dial timing. When timer T is used without the "accumulate according to digit map" action, timer T takes on the value T-critical. The default value for T-partial is 16 seconds and the default value for T-critical is 4 seconds. The provisioning process may alter both of these. If timer T is not used, then inter-digit timing will not be performed.
对应于临界拨盘定时的T临界值。当使用定时器T时，没有“根据数字映射累积”动作，定时器T的值为T-临界值。T-partial的默认值为16秒，T-critical的默认值为4秒。供应过程可能会改变这两个方面。如果未使用定时器T，则不会执行数字间定时。
The following examples illustrate this. Consider the digit map:
下面的例子说明了这一点。考虑数字地图：
(xxxxxxx|x11T)
（xxxxxxx×x11T）
and assume that DTMF and the timer T is accumulated according to digit map. At the first DTMF input, say "4", timer T is started with a value of T-partial since at least one more symbol is required. If "1" is then input, it leads to a restart of timer T with a value of T-partial again. If "1" is now input again, we have a current dial string of "411" and a timer is now all that is required to produce a match. Hence timer T is now restarted with value T-critical.
并假设DTMF和定时器T根据数字映射累积。在第一个DTMF输入时，例如“4”，定时器T以T-partial值启动，因为至少需要一个以上的符号。如果随后输入“1”，则会导致计时器T重新启动，其值再次为T-partial。如果现在再次输入“1”，则当前拨号字符串为“411”，现在只需一个计时器即可生成匹配。因此，定时器T现在以值T-critical重新启动。
Finally, consider the following subtle examples (all assuming DTMF and timer T being accumulated according to digit map):
最后，考虑以下微妙的例子（所有假设DTMF和定时器T根据数字地图累积）：
The digit map
数字地图
(1[2-3T].)
（1[2-3T]）
will match immediately on the input "1" since zero or more matches of the range are specified.
将立即匹配输入“1”，因为指定了零个或多个范围匹配。
The digit map
数字地图
(1[2-3].T)
（1[2-3].T）
and an input of "1" will lead to timer T being set to T-critical.
输入“1”将导致定时器T设置为T-临界。
A digit map of
数字地图
(1[2-3]T.)
（1[2-3]T.）
and an input of "1" will lead to timer T being set to T-partial. Furthermore, upon subsequent input of "2" or "3" a perfect match will be triggered immediately since timer T is completely irrelevant.
输入“1”将导致定时器T设置为T-partial。此外，在随后输入“2”或“3”时，将立即触发完全匹配，因为计时器T完全不相关。
DTMF Tones Wildcard (X): The DTMF tones wildcard matches any DTMF digit between 0 and 9. The actual event code generated will however be the event code for the digit detected. The DTMF tones wildcard is often used to detect DTMF input to be matched against a digit map.
DTMF音调通配符（X）：DTMF音调通配符匹配0到9之间的任何DTMF数字。然而，生成的实际事件代码将是检测到的数字的事件代码。DTMF音调通配符通常用于检测要与数字映射匹配的DTMF输入。
Package Name: T Version: 1
软件包名称：T版本：1
----------------------------------------------------------------
| Symbol | Definition | R | S Duration |
|----------------------------------------------------------------|
| as | Answer Supervision | x | BR |
| bl | Blocking | | BR |
| bz | Busy | | TO 30 sec. |
| co1 | Continuity Tone (go tone, | x | TO 3 sec. |
| | or return tone) | | |
| co2 | Continuity Test (go tone, | x | TO 3 sec. |
| | or return tone in dual tone | | |
| | procedures) | | |
| ct(...) | Continuity Transponder | | OO |
| lb | Loopback | | OO |
| nm | New Milliwatt Tone | x | TO 3 sec |
| mm | Newest Milliwatt Tone | x | TO 3 sec |
| oc | Operation Complete | x | |
| of | Operation Failure | x | |
| om | Old Milliwatt Tone | x | TO 3 sec |
| pst | Permanent Signal Tone | | TO infinite |
| qt | Quiet Termination | | TO infinite |
| ro | Reorder Tone | x | TO 30 sec. |
| sit(#) | Special Information Tone | x | TO 2 sec. |
| | | | (see notes) |
| tl | Test Line | x | TO infinite |
| tp(###) | Test Pattern | x | TO 3 sec |
| zz | No Circuit | x | TO 2 sec |
----------------------------------------------------------------
----------------------------------------------------------------
| Symbol | Definition | R | S Duration |
|----------------------------------------------------------------|
| as | Answer Supervision | x | BR |
| bl | Blocking | | BR |
| bz | Busy | | TO 30 sec. |
| co1 | Continuity Tone (go tone, | x | TO 3 sec. |
| | or return tone) | | |
| co2 | Continuity Test (go tone, | x | TO 3 sec. |
| | or return tone in dual tone | | |
| | procedures) | | |
| ct(...) | Continuity Transponder | | OO |
| lb | Loopback | | OO |
| nm | New Milliwatt Tone | x | TO 3 sec |
| mm | Newest Milliwatt Tone | x | TO 3 sec |
| oc | Operation Complete | x | |
| of | Operation Failure | x | |
| om | Old Milliwatt Tone | x | TO 3 sec |
| pst | Permanent Signal Tone | | TO infinite |
| qt | Quiet Termination | | TO infinite |
| ro | Reorder Tone | x | TO 30 sec. |
| sit(#) | Special Information Tone | x | TO 2 sec. |
| | | | (see notes) |
| tl | Test Line | x | TO infinite |
| tp(###) | Test Pattern | x | TO 3 sec |
| zz | No Circuit | x | TO 2 sec |
----------------------------------------------------------------
New events added to this package from the previously unversioned package: "bz", "ct", "mm", "oc", "pst", "qt", "sit", and "tp".
从以前未版本的包中添加到此包的新事件：“bz”、“ct”、“mm”、“oc”、“pst”、“qt”、“sit”和“tp”。
Changes in event types: "co1", "co2", "nm", "om", "tl", "zz" signals changed from OO to TO; "as" and "bl" changed from OO to BR.
事件类型的变化：“co1”、“co2”、“nm”、“om”、“tl”、“zz”信号从OO变为；“as”和“bl”从OO更改为BR。
Note that default time-out values may be over-ridden by the Call Agent for any Time-Out signal defined in this package by a "to" signal parameter. Refer to section 2 of this document, as well as [1] for details.
请注意，对于此包中由“to”信号参数定义的任何超时信号，调用代理可能会覆盖默认超时值。有关详细信息，请参阅本文件第2节以及[1]。
The definition of the trunk package events are as follows:
中继包事件的定义如下：
Answer Supervision (as): This event is used to indicate the occurrence answer supervision. In most cases, it is a result of a steady off-hook in response to a call request. This event is included for backwards compatibility with the previous version of the package. The preferred alternative is to use the "answer" event in the appropriate CAS packages [34] (Note: check the details on the use of "answer" in the particular CAS package; in most cases "answer" as an event is an indication of a steady off-hook regardless of whether or not it is an indication of answer supervision). For details on when answer supervision is appropriate refer to [5].
应答监督（as）：此事件用于指示应答监督的发生。在大多数情况下，这是响应呼叫请求的稳定脱钩的结果。包含此事件是为了与包的早期版本向后兼容。首选的替代方案是在适当的CAS包中使用“应答”事件[34]（注：检查特定CAS包中使用“应答”的详细信息；在大多数情况下，“应答”作为一个事件是一个稳定脱钩的指示，无论它是否是应答监督的指示）。有关何时适合回答监督的详细信息，请参阅[5]。
Blocking (bl): This event is used to indicate an incoming off-hook for the purposes of blocking a one-way trunk in CAS trunks. This event is included for backwards compatibility with the previous version of the package. The preferred alternative is the "block" event in the appropriate CAS packages [34].
阻塞（bl）：此事件用于指示传入的摘机，以阻塞CAS中继中的单向中继。包含此事件是为了与包的早期版本向后兼容。首选方案是适当CAS包中的“阻塞”事件[34]。
Busy Tone (bz): Refer to ITU-T E.180 [8]. In North America, station Busy is a combination of two AC tones with frequencies of 480 and 620 Hertz and levels of -24 dBm each, to give a combined level of -21 dBm. The cadence for Station Busy Tone is 0.5 seconds on, followed by 0.5 seconds off, then repeating. See GR-506-CORE [7]- LSSGR: SIGNALING, Section 17.2.6.
忙音（bz）：参考ITU-T E.180[8]。在北美，station Busy是两个交流音的组合，频率分别为480和620赫兹，电平分别为-24 dBm，组合电平为-21 dBm。电台忙音的节奏为0.5秒打开，然后是0.5秒关闭，然后重复。参见GR-506-CORE[7]-LSSGR：信号，第17.2.6节。
Continuity Tone (co1): A tone at 2010 Hz (see section 3.1.1.3 of [2]). When generated as a signal, the frequency of the tone must be within + or - 8 Hz, while the frequency of the tone corresponding to the event must be within + or - 30 Hz.
连续性音调（co1）：2010 Hz时的音调（见[2]第3.1.1.3节）。当作为信号生成时，音调频率必须在+8 Hz或-8 Hz范围内，而与事件对应的音调频率必须在+30 Hz范围内。
Continuity Test (co2): A tone at 1780 Hz (see section 3.1.1.3 of [2]). When generated as a signal, the frequency of the tone must be within + or - 20 Hz, while the frequency of the tone corresponding to the event must be within + or - 30 Hz.
连续性测试（co2）：1780 Hz的音调（见[2]第3.1.1.3节）。当作为信号生成时，音调频率必须在+20 Hz或-20 Hz范围内，而与事件对应的音调频率必须在+30 Hz或-30 Hz范围内。
In continuity testing the tone corresponding to the signal at the originating gateway is referred to as the "go" tone, and the tone
在连续性测试中，与发起网关处的信号相对应的音调称为“go”音调，而
corresponding to the event at that same gateway is referred to as the "return" or "check" tone.
与同一网关上的事件相对应的是“返回”或“检查”音。
Note that generation and notification of continuity tones are done as per continuity test requirements as defined in ITU-T Q.724 [3], as well as by Bellcore GR-317-CORE [2] specifications, i.e., the semantics of notification of the return tone is more than that the tone was received, but is an indication that the test has passed. Details are provided in the following paragraphs.
请注意，根据ITU-T Q.724[3]中定义的连续性测试要求以及Bellcore GR-317-CORE[2]规范生成和通知连续性音调，即返回音调通知的语义大于接收到的音调，但表示测试已通过。下文提供了详细情况。
The continuity tones represented by co1 and co2 are used when the Call Agent wants to initiate a continuity test. There are two types of tests, single tone and dual tone; In the case of the dual tone, either tone can be sent and the opposite received depending on the trunk interconnections (4-wire or 2-wire) as indicated below:
当呼叫代理想要启动连续性测试时，使用由co1和co2表示的连续性音调。有两种类型的测试，单音和双音；在双音的情况下，根据中继线互连（4线或2线），可以发送任一音，也可以接收相反的音，如下所示：
Originating Terminating
============ ===========
Originating Terminating
============ ===========
4w -------------- 1780 Hz -----------> 2w
<------------- 2010 Hz ------------ (transponder)
4w -------------- 1780 Hz -----------> 2w
<------------- 2010 Hz ------------ (transponder)
2w -------------- 2010 Hz -----------> 2w/4w
<------------- 1780 Hz ------------ (transponder)
2w -------------- 2010 Hz -----------> 2w/4w
<------------- 1780 Hz ------------ (transponder)
4w -------------- 2010 Hz -----------> 4w
<------------- 2010 Hz ------------ (loopback)
4w -------------- 2010 Hz -----------> 4w
<------------- 2010 Hz ------------ (loopback)
The Call agent is expected to know, through provisioning information, which test should be applied to a given endpoint. As an example, for a 4-wire to 2-wire connection, the Call Agent might send a request like the following to an originating gateway:
通过设置信息，呼叫代理应该知道应该对给定端点应用哪个测试。例如，对于4线到2线连接，呼叫代理可能会向发起网关发送如下请求：
RQNT 1234 ds/ds1-1/17@tgw2.example.net
X: AB123FE0
S: t/co1
R: t/co2,t/oc,t/of
RQNT 1234 ds/ds1-1/17@tgw2.example.net
X: AB123FE0
S: t/co1
R: t/co2,t/oc,t/of
On a terminating side of a trunk, the call agent may request a continuity test connection (connection mode "conttest") to the terminating gateway as follows:
在中继线的终端侧，呼叫代理可以请求到终端网关的连续性测试连接（连接模式“conttest”），如下所示：
CRCX 3001 ds/ds1-2/4@tgw34.example.net
C: 3748ABC364
M: conttest
CRCX 3001 ds/ds1-2/4@tgw34.example.net
C: 3748ABC364
M: conttest
Alternatively, rather than using a connection mode, the "T/ct" signal can be used (see description of this signal further below):
或者，可以使用“T/ct”信号，而不是使用连接模式（参见下文对该信号的描述）：
RQNT 3001 ds/ds1-2/4@tgw34.example.net
X: 1233472
S: t/ct(in=co1,out=co2,+)
RQNT 3001 ds/ds1-2/4@tgw34.example.net
X: 1233472
S: t/ct(in=co1,out=co2,+)
The originating gateway would send the requested "go" tone, and would look for the appropriate "return tone". Once the return tone is received, the originating gateway removes the go tone and checks to see that the return tone has been removed within the specified performance limits (i.e., GR-246-CORE, T1.113.4, Annex B [23]). When it detects that the test is successful, the gateway will send a notification of the return tone event (Note that notification of the return tone event therefore must not be sent prior to detection of the removal of the return tone).
发起网关将发送请求的“go”音，并寻找适当的“return”音。一旦收到回音，发起网关将删除go音，并检查回音是否已在规定的性能限制范围内删除（即GR-246-CORE，T1.113.4，附录B[23]）。当检测到测试成功时，网关将发送回音事件通知（请注意，在检测到回音删除之前，不得发送回音事件通知）。
The "T/co1" and "T/co2" signals are TO signals so that an operation complete event will occur when the signal times out. If a timeout value other than the default is desired, the "to" parameter may be used (e.g., "S: T/co1(to=2000)").
“T/co1”和“T/co2”信号与信号相连，以便在信号超时时发生操作完成事件。如果需要默认值以外的超时值，则可以使用“to”参数（例如，“S:T/co1（to=2000）”。
If the gateway detects the failure of the continuity test prior to the timeout, an operation failure event will be generated. Otherwise, the failure of the continuity test is determined by the failure to receive the return tone event before the timeout occurs (operation complete event). As with TO signals in general, operation complete and operation fail events are parameterized with the name of the signal.
如果网关在超时之前检测到连续性测试失败，将生成操作失败事件。否则，导通性测试的失败取决于在超时发生（操作完成事件）之前未收到回音事件。与一般信号一样，操作完成和操作失败事件用信号的名称参数化。
In the example above where the go tone is "co1" and the return tone is "co2":
在上面的示例中，go音调为“co1”，返回音调为“co2”：
* A notification of the "co2" event indicates success (i.e., "O: t/co2").
* “co2”事件的通知表示成功（即“O:t/co2”）。
* A notification of the operation failure event indicates failure prior to timeout (i.e., "O: t/of(t/co1)").
* 操作失败事件的通知表示超时之前的失败（即“O:t/of（t/co1）”）。
* A notification of the operation complete event indicates that the return tone was not received properly prior to the occurrence of the timeout (i.e., "O: t/oc(t/co2)").
* 操作完成事件的通知表示在超时发生之前未正确接收到返回音（即“O:t/oc（t/co2）”）。
On a terminating end of a trunk, either a "loopback" connection (single tone test) or "conttest" connection (dual tone test) is made (or alternatively the "T/lb" or "T/ct" signals are requested). It is up to the termination end to make sure that the return tone is removed as soon as the go tone disappears. The
在中继线的端接端，进行“环回”连接（单音测试）或“连续测试”连接（双音测试）（或者请求“T/lb”或“T/ct”信号）。由终端确保在go音消失后立即删除返回音。这个
Call Agent requests the removal of "contest" or "loopback" connections (or "T/lb" or "T/ct" signals) at a termination end when the results of the continuity test are obtained.
当获得连续性测试结果时，呼叫代理请求删除终端端的“竞争”或“环回”连接（或“T/lb”或“T/ct”信号）。
When "conttest" is used, the endpoint is provisioned as to which transponder test is being performed (2010 Hz received and 1780 Hz sent or vice versa). In the case of the corresponding "T/ct" signal, the Call Agent can specify which tone is received and sent as parameters.
当使用“conttest”时，端点被设置为正在执行哪个应答器测试（接收到2010 Hz，发送到1780 Hz，反之亦然）。在对应的“T/ct”信号的情况下，呼叫代理可以指定作为参数接收和发送的音调。
Note that continuity tones in the trunk package are only ever sent to the telephony endpoint. For network-based continuity, there are continuity tones available in the RTP ("R") package. Although a transponder (dual tone) test can be done, a single tone test is generally sufficient in the case of continuity testing across an IP network.
请注意，中继包中的连续性音调仅发送到电话端点。对于基于网络的连续性，RTP（“R”）包中提供了连续性音调。虽然可以进行转发器（双音）测试，但在IP网络上进行连续性测试的情况下，单音测试通常就足够了。
Continuity Transponder(ct(in=<tone-in>,out=<tone-out>, <+ or ->)): This signal is used to provide transponder functionality independent of the connection mode, i.e., this is an alternative way to provide the same functionality as the "conttest" connection mode. The parameters can be provided in any order. The <tone-in> and <tone-out> parameters can have values "co1" or "co2", corresponding to the 2010 Hz and 1780 Hz tones associated with those symbols. If one of the tones is "co1", then the other must be "co2" and vice versa (i.e., <tone-in> and <tone-out> must have different values; if loopback is required, then the "lb" signal in this package or "loopback" connection mode should be used).
连续性收发器（ct（输入=<tone-in>，输出=<tone-out>，<+或->）：此信号用于提供独立于连接模式的收发器功能，即，这是提供与“ConTest”连接模式相同功能的替代方法。可以按任何顺序提供参数。<tone in>和<tone out>参数可以具有值“co1”或“co2”，对应于与这些符号相关联的2010 Hz和1780 Hz音调。如果其中一个音调为“co1”，则另一个音调必须为“co2”，反之亦然（即，<tone in>和<tone out>必须具有不同的值；如果需要环回，则应使用此软件包中的“lb”信号或“环回”连接模式）。
On detecting <tone-in>, <tone-out> will be generated in return. The tone corresponding to <tone-out> will continue to be generated until either:
检测到<音调输入>，将生成<音调输出>。与<音调输出>相对应的音调将继续生成，直到：
* The signal is explicitly turned off (e.g., "S: t/ct(-)") or
* 信号明确关闭（例如，“S:t/ct（-）”）或
* Removal of the <tone-in> tone is detected.
* 检测到<tone in>音调被删除。
Note that while the signal is active (regardless of whether a tone is active or not), media from the endpoint will not be forwarded to or from the packet network (i.e., the continuity transponder signal must be explicitly turned off by the Call Agent in order to resume passing media between the packet network and the endpoint).
注意，当信号处于活动状态时（无论音调是否处于活动状态），来自端点的媒体将不会转发到分组网络或从分组网络转发（即，呼叫代理必须明确关闭连续性应答器信号，以便恢复分组网络和端点之间的媒体传递）。
Loopback (lb): This signal is used to provide loopback functionality independent of the connection mode, i.e., this is an alternative way to provide the same functionality as "loopback" connection mode.
环回（lb）：该信号用于提供独立于连接模式的环回功能，即，这是提供与“环回”连接模式相同功能的替代方式。
Note that while the loop-back signal is active (regardless of whether a tone is active or not), media from the endpoint will not be forwarded to or from the packet network (i.e., the loopback signal must be explicitly turned off by the Call Agent in order to resume passing media between the packet network and the endpoint).
注意，当环回信号处于活动状态时（无论音调是否处于活动状态），来自端点的媒体将不会被转发到分组网络或从分组网络转发（即，呼叫代理必须明确关闭环回信号，以便恢复分组网络和端点之间的媒体传递）。
New Milliwatt Tone (nm): 1004 Hz tone - refer to [4] and section 8.2.5 of [5].
新毫瓦音调（nm）：1004 Hz音调-参考[4]和[5]的第8.2.5节。
Newest Milliwatt Tone (mm): 1013.8 Hz - refer to [4].
最新毫瓦音调（毫米）：1013.8赫兹-参考[4]。
Operation Complete (oc): This is the standard definition of operation complete [1].
操作完成（oc）：这是操作完成[1]的标准定义。
Operation Failure (of): This is the standard definition of operation failure [1].
操作失败（of）：这是操作失败的标准定义[1]。
Old Milliwatt Tone (om): 1000 Hz tone - refer to [4] and section 8.2.5 of [5].
旧毫瓦音调（om）：1000 Hz音调-参考[4]和[5]的第8.2.5节。
Permanent Signal Tone (pst): In North America, this tone is applied to a busy line verify/operator interrupt under specific circumstances as described in [17].
永久信号音（pst）：在北美，在[17]中所述的特定情况下，该音适用于占线验证/操作员中断。
Quiet Termination (qt): Quiet Termination is used in a 102 trunk test. Reference section 6.20.5 [5] as well as [4].
安静终端（qt）：安静终端用于102中继测试。参考第6.20.5[5]和[4]节。
Reorder Tone(ro): This maps to congestion tone in the ITU-T E.182 specification. In North America, reorder tone is a combination of two AC tones with frequencies of 480 and 620 Hertz and levels of -24 dBm each, to give a combined level of -21 dBm. The cadence for reorder tone is 0.25 seconds on, followed by 0.25 seconds off, repeating continuously (until time-out). See GR-506-CORE [7], Section 17.2.7.
重排序音调（ro）：这映射到ITU-T E.182规范中的拥塞音调。在北美，重排序音调是两个交流音调的组合，频率分别为480和620赫兹，电平分别为-24 dBm，组合电平为-21 dBm。重新排序音调的节拍为打开0.25秒，然后关闭0.25秒，持续重复（直到超时）。参见GR-506-CORE[7]，第17.2.7节。
Special Information Tone(sit(#)): As described in ITU-T E.180 [8], the special information tone consists of a tone period in which 3 tones are produced followed by a silent period of 1 second (total TO period of approximately 2 seconds). When used as a signal, it MUST be parameterized with a parameter value from 1 to 7, with the following meaning as defined in SR-2275, section 6.21.2 of [5].
特殊信息音（sit（#））：如ITU-T E.180[8]中所述，特殊信息音由一个音周期组成，其中产生3个音，然后是1秒的静音周期（总计约2秒）。当用作信号时，必须使用1到7之间的参数值对其进行参数化，其含义如SR-2275，第6.21.2节[5]所定义。
-------------------------------------------
| sit(1) | RO' | reorder SIT, intra-LATA |
| sit(2) | RO" | reorder SIT, inter-LATA |
| sit(3) | NC' | no circuit SIT, intra-LATA |
| sit(4) | NC" | no circuit SIT, inter-LATA |
| sit(5) | IC | intercept SIT |
| sit(6) | VC | vacant code SIT |
| sit(7) | IO | ineffective other SIT |
-------------------------------------------
-------------------------------------------
| sit(1) | RO' | reorder SIT, intra-LATA |
| sit(2) | RO" | reorder SIT, inter-LATA |
| sit(3) | NC' | no circuit SIT, intra-LATA |
| sit(4) | NC" | no circuit SIT, inter-LATA |
| sit(5) | IC | intercept SIT |
| sit(6) | VC | vacant code SIT |
| sit(7) | IO | ineffective other SIT |
-------------------------------------------
When requested as an event, the event MUST be parameterized with a decimal number from 1 to 7 to indicate which tone the gateway is required to detect. The resulting notification also includes the parameter. Other countries may have one or more special information tones with country specific definitions (refer to ITU-T E.180 supp. 2 [9]). In this case, special information tone 1 as defined in [9] is sit(1), special information tone 2 is sit(2) etc.
当作为事件请求时，必须使用1到7之间的十进制数字对事件进行参数化，以指示网关需要检测的音调。结果通知还包括参数。其他国家可能有一个或多个具有国家特定定义的特殊信息音（请参阅ITU-T E.180补充2[9]）。在这种情况下，[9]中定义的特殊信息音调1为sit（1），特殊信息音调2为sit（2）等。
As an example, the Call Agent might make a request such as:
例如，呼叫代理可能发出如下请求：
RQNT 1234 ds/ds1-1/17@tgw2.example.net
X: AB123FE0
R: t/sit(N)(2)
RQNT 1234 ds/ds1-1/17@tgw2.example.net
X: AB123FE0
R: t/sit(N)(2)
If the tone is detected, the resulting notification might appear as follows:
如果检测到音调，结果通知可能如下所示：
NTFY 3002 ds/ds1-3/6@gw-o.whatever.net MGCP 1.0
X: AB123FE0
O: t/sit(2)
NTFY 3002 ds/ds1-3/6@gw-o.whatever.net MGCP 1.0
X: AB123FE0
O: t/sit(2)
Test Line (tl): 105 Test Line test progress tone (2225 Hz + or - 25 Hz at -10 dBm0). Refer to section 8.2.5 of [5].
测试线（tl）：105测试线测试进度音（2225Hz+或-10dBm0时的-25Hz）。参考[5]第8.2.5节。
Test Pattern (tp(###)): The tp(###) signal inserts the pattern ### continuously into the channel until the timeout period expires. The parameter is provided as a decimal number from 0 to 255. If the parameter is omitted, the default value is decimal 95.
测试模式（tp）：tp（#######）信号将模式连续插入通道，直到超时时间到期。该参数以0到255之间的十进制数提供。如果省略该参数，则默认值为十进制95。
In RequestedEvents, the parameter MAY be supplied to indicate what pattern the Call Agent wishes the gateway to detect. If the parameter is omitted, the value 95 is assumed. The pattern MUST be returned in the ObservedEvent (even if the parameter was not requested).
在RequestedEvents中，可以提供参数来指示呼叫代理希望网关检测的模式。如果省略该参数，则假定值95。必须在ObservedEvent中返回模式（即使未请求参数）。
A typical use for the test pattern signal is for the test line 108 (digital loopback) test (refer to section 8.2.5 of [5]). At the termination side of a trunk, the Call Agent would request a connection in "loopback" mode, which would do a digital loopback. On the origination side of the trunk, the Call Agent would request that the test pattern be injected into the digital channel, and would check to see that the pattern was returned within the timeout period. As an example, the Call Agent would make the following request on the origination side:
测试模式信号的典型用途是测试线108（数字环回）测试（参考[5]第8.2.5节）。在中继线的终端端，呼叫代理将以“环回”模式请求连接，这将进行数字环回。在中继的起始端，呼叫代理将请求将测试模式注入数字通道，并检查模式是否在超时时间内返回。例如，呼叫代理将在发起端发出以下请求：
RQNT 1234 ds/ds1-1/17@tgw2.example.net
X: AB123FE0
S: t/tp
R: t/tp, t/oc, t/of
RQNT 1234 ds/ds1-1/17@tgw2.example.net
X: AB123FE0
S: t/tp
R: t/tp, t/oc, t/of
In this case the Call Agent will either receive:
在这种情况下，呼叫代理将接收：
* An ObservedEvent indicating that the test has passed (i.e., "O:t/op(95)") or
* 表明试验已通过的观察事件（即“O:t/op（95）”），或
* An ObservedEvent indicating that the timeout occurred before the pattern was received (i.e., "O:t/oc(t/tp)"), indicating that the test failed. Of course an operation failure would indicate failure as well.
* 一个ObservedEvent，指示超时发生在接收模式之前（即“O:t/oc（t/tp）”），指示测试失败。当然，操作失败也表示失败。
No Circuit (zz): This is an alias for Special Information Tone 2, i.e., "sit(2)".
无回路（zz）：这是特殊信息音调2的别名，即“sit（2）”。
Package Name: L Version: 1
软件包名称：L版本：1
----------------------------------------------------------------
|Symbol | Definition | R | S Duration |
|----------------------------------------------------------------|
|adsi(string) | ADSI Display | | BR |
|aw | Answer Tone | x | OO |
|bz | Busy Tone | | TO 30 sec. |
|ci(ti,nu,na) | Caller-id | | BR |
|dl | Dial Tone | | TO 16 sec. |
|e | Error Tone | x | TO 2 sec. |
|hd | Off-hook Transition | S | |
|hf | Flash-hook | x | |
|ht | On Hold Tone | | OO |
|hu | On-hook Transition | S | |
|lsa | Line Side Answer Sup. | | OO |
|mwi | Message Waiting ind. | | TO 16 sec. |
|nbz | Network busy | x | TO infinite |
|oc | Operation Complete | x | |
|of | Operation Failure | x | |
|osi | Network Disconnect | | TO 900 ms |
|ot | Off-hook Warning Tone | | TO infinite |
|p | Prompt Tone | x | BR |
|rg | Ringing | | TO 180 sec. |
|r0, r1, r2, | Distinctive Ringing | | TO 180 sec. |
|r3, r4, r5, | | | |
|r6 or r7 | | | |
|ro | Reorder Tone | | TO 30 sec. |
|rs | Ringsplash | | BR |
|s(###) | Distinctive Tone Pattern | x | BR |
|sit(#) | Special Information Tone | | TO 2 sec. |
| | | | (see notes) |
|sl | Stutter Dial Tone | | TO 16 sec. |
|v | Alerting Tone | | OO |
|vmwi | Visual Message | | OO |
| | Waiting Indicator | | |
|wt | Call Waiting Tone | | TO 12 sec |
|wt1, wt2, | Alternative Call | | TO 12 sec |
|wt3, wt4 | Waiting Tones | | (see notes) |
|y | Recorder Warning Tone | | TO infinite |
|z | Calling Card Service Tone| | BR |
----------------------------------------------------------------
----------------------------------------------------------------
|Symbol | Definition | R | S Duration |
|----------------------------------------------------------------|
|adsi(string) | ADSI Display | | BR |
|aw | Answer Tone | x | OO |
|bz | Busy Tone | | TO 30 sec. |
|ci(ti,nu,na) | Caller-id | | BR |
|dl | Dial Tone | | TO 16 sec. |
|e | Error Tone | x | TO 2 sec. |
|hd | Off-hook Transition | S | |
|hf | Flash-hook | x | |
|ht | On Hold Tone | | OO |
|hu | On-hook Transition | S | |
|lsa | Line Side Answer Sup. | | OO |
|mwi | Message Waiting ind. | | TO 16 sec. |
|nbz | Network busy | x | TO infinite |
|oc | Operation Complete | x | |
|of | Operation Failure | x | |
|osi | Network Disconnect | | TO 900 ms |
|ot | Off-hook Warning Tone | | TO infinite |
|p | Prompt Tone | x | BR |
|rg | Ringing | | TO 180 sec. |
|r0, r1, r2, | Distinctive Ringing | | TO 180 sec. |
|r3, r4, r5, | | | |
|r6 or r7 | | | |
|ro | Reorder Tone | | TO 30 sec. |
|rs | Ringsplash | | BR |
|s(###) | Distinctive Tone Pattern | x | BR |
|sit(#) | Special Information Tone | | TO 2 sec. |
| | | | (see notes) |
|sl | Stutter Dial Tone | | TO 16 sec. |
|v | Alerting Tone | | OO |
|vmwi | Visual Message | | OO |
| | Waiting Indicator | | |
|wt | Call Waiting Tone | | TO 12 sec |
|wt1, wt2, | Alternative Call | | TO 12 sec |
|wt3, wt4 | Waiting Tones | | (see notes) |
|y | Recorder Warning Tone | | TO infinite |
|z | Calling Card Service Tone| | BR |
----------------------------------------------------------------
New events added to this package from the previously unversioned package: "ht", "osi", and "lsa".
从以前的未版本包中添加到此包的新事件：“ht”、“osi”和“lsa”。
Changes in event types: signals "y", "z", changed from OO to TO and BR respectively. Ringing tones were extended to allow for a ring repetition signal parameter.
事件类型的变化：信号“y”、“z”，分别从OO变为to和BR。对铃声进行了扩展，以允许铃声重复信号参数。
Note that default time-out values may be over-ridden by the Call Agent for any Time-Out signal defined in this package by a "to" signal parameter. Refer to section 2 of this document, as well as [1] for details.
请注意，对于此包中由“to”信号参数定义的任何超时信号，调用代理可能会覆盖默认超时值。有关详细信息，请参阅本文件第2节以及[1]。
The description of events and signals in the line package are as follows:
线路包中的事件和信号说明如下：
ADSI Display (adsi): This signal is included here to maintain compatibility with the previous version of this package. The signal is not well-defined and its use is discouraged.
ADSI显示器（ADSI）：此信号包含在此处，以保持与此软件包以前版本的兼容性。信号定义不明确，不鼓励使用。
Answer Tone (aw): This event is included here to maintain compatibility with the previous version of this package. The event is not well-defined and its use is discouraged.
应答音（aw）：此事件包含在此处，以保持与此软件包以前版本的兼容性。事件定义不明确，不鼓励使用它。
Busy Tone (bz): Refer to ITU-T E.180 [8]. In North America, station Busy is a combination of two AC tones with frequencies of 480 and 620 Hertz and levels of -24 dBm each, to give a combined level of -21 dBm. The cadence for Station Busy Tone is 0.5 seconds on followed by 0.5 seconds off, repeating. See GR-506-CORE [7], Section 17.2.6. It is considered an error to try and play busy tone on a phone that is on-hook and an error MUST consequently be returned when such attempts are made (error code 402 - phone on-hook).
忙音（bz）：参考ITU-T E.180[8]。在北美，station Busy是两个交流音的组合，频率分别为480和620赫兹，电平分别为-24 dBm，组合电平为-21 dBm。电台忙音的节奏为0.5秒打开，然后0.5秒关闭，重复。参见GR-506-CORE[7]，第17.2.6节。尝试在挂机的手机上播放忙音被认为是错误的，因此在进行此类尝试时必须返回错误（错误代码402-挂机的手机）。
Caller-id (ci(time, number, name)): See GR-1188 [24], GR-30-CORE [14], and GR-31 [25]. For backwards compatibility, each of the three fields are optional, but each of the commas will always be included. In accordance with the general MGCP grammar, it is RECOMMENDED to always include all three fields - an empty quoted string can then be used in lieu of omitting a parameter:
呼叫方id（ci（时间、号码、名称））：参见GR-1188[24]、GR-30-CORE[14]和GR-31[25]。为了向后兼容，这三个字段中的每一个都是可选的，但始终包含每个逗号。根据通用MGCP语法，建议始终包括所有三个字段-然后可以使用带引号的空字符串代替省略参数：
The time parameter is coded as "MM/DD/HH/MM", where MM is a two-digit decimal value for a Month between 01 and 12, DD is a two-digit value for a Day between 01 and 31, and Hour and Minute are two-digit values coded according to military local time, e.g., 00 is midnight, 01 is 1 a.m., and 13 is 1 p.m. (Note: two digits MUST always be provided for each of the values of month, day, hour, minutes e.g., the month of January is indicated by the two digits "01" rather than just "1").
时间参数编码为“MM/DD/HH/MM”，其中MM是01和12之间一个月的两位数十进制值，DD是01和31之间一天的两位数值，小时和分钟是根据军事当地时间编码的两位数值，例如，00是午夜，01是凌晨1点，13是下午1点。（注：必须始终为月、日、小时、分钟的每个值提供两位数字，例如，一月由两位数字“01”表示，而不仅仅是“1”）。
The number parameter is coded as an ASCII character string of decimal digits that identify the calling line number. White spaces are permitted if the string is quoted, but they will be ignored. If a quoted-string is provided, the string itself is UTF-8 encoded (RFC 2279) as usual for signal parameters.
number参数编码为十进制数字的ASCII字符串，用于标识主叫线号码。如果字符串被引用，则允许使用空格，但它们将被忽略。如果提供了带引号的字符串，则该字符串本身按照信号参数的通常方式进行UTF-8编码（RFC 2279）。
The name parameter is coded as a string of ASCII characters that identify the calling line name. White spaces are permitted if the string is quoted. If a quoted-string is provided, the string itself is UTF-8 encoded (RFC 2279).
name参数编码为ASCII字符字符串，用于标识主叫线路名称。如果字符串被引用，则允许使用空格。如果提供了带引号的字符串，则字符串本身是UTF-8编码的（RFC 2279）。
A "P" in the number or name field is used to indicate a private number or name, and an "O" is used to indicate an unavailable number or name. Other letters MAY be used to provide additional clarification as per provider or vendor specifications.
数字或名称字段中的“P”用于表示私人数字或名称，“O”用于表示不可用的数字或名称。根据供应商或供应商规范，可使用其他信函提供额外澄清。
The following example illustrates the use of the caller-id signal:
以下示例说明了呼叫者id信号的使用：
S: l/ci(09/14/17/26, "555 1212", "John Doe")
S: l/ci(09/14/17/26, "555 1212", "John Doe")
An example indicating that the name and number are private:
指示名称和编号为专用的示例：
S: l/ci(09/14/17/26,P,P)
S: l/ci(09/14/17/26,P,P)
Dial Tone (dl): Refer to the ITU-T E.180 [8] specification. In North America, dial tone is a combination of two continuous AC tones with frequencies of 350 and 440 Hertz and levels of -13dBm each, to give a combined level of -10 dBm. See GR-506-CORE [7] - LSSGR: SIGNALING, Section 17.2.1. It is considered an error to try and play dial-tone on a phone that is on-hook and an error MUST consequently be returned when such attempts are made (error code 402 - phone on-hook).
拨号音（dl）：参考ITU-T E.180[8]规范。在北美，拨号音是两个连续交流音的组合，频率分别为350和440赫兹，电平分别为-13dBm，组合电平为-10dBm。参见GR-506-CORE[7]-LSSGR：信号，第17.2.1节。尝试在挂机的电话上播放拨号音被认为是错误的，因此在进行此类尝试时必须返回错误（错误代码402-挂机电话）。
Error Tone (e): This tone is maintained for backwards compatibility. The tone is not well defined and its use is discouraged.
错误提示音（e）：此提示音保持向后兼容。语气不明确，不鼓励使用。
Off-hook Transition (hd): See GR-506-CORE [7], Section 12. It is considered an error to try and request off-hook on a phone that is off-hook and an error MUST consequently be returned when such attempts are made (error code 401 - phone off-hook).
脱钩过渡（hd）：见GR-506-CORE[7]，第12节。尝试和请求摘机是一个错误，因此在进行此类尝试时必须返回一个错误（错误代码401-电话摘机）。
Flash Hook (hf): See GR-506-CORE [7], Section 12. It is considered an error to try and request flash hook on a phone that is on-hook and an error MUST consequently be returned when such attempts are made (error code 402 - phone on-hook).
闪光钩（hf）：见GR-506-CORE[7]，第12节。在挂机的手机上尝试并请求闪存挂机被认为是一个错误，因此在进行此类尝试时必须返回一个错误（错误代码402-挂机的手机）。
Tone On Hold (ht): A tone used to reassure a calling subscriber who has been placed on "hold". Refer to ITU-T E.182 [10].
等待音（ht）：一种用来使处于“等待”状态的主叫用户放心的音。参考ITU-T E.182[10]。
On-hook Transition (hu): See GR-506-CORE [7], Section 12. The timing for the on-hook signal is for flash response enabled, unless provisioned otherwise. It is considered an error to try and request flash hook on a phone that is on-hook and an error MUST consequently be returned when such attempts are made (error code 402 - phone on-hook).
钩上过渡（hu）：见GR-506-CORE[7]，第12节。挂机信号的定时为启用闪存响应，除非另有规定。在挂机的手机上尝试并请求闪存挂机被认为是一个错误，因此在进行此类尝试时必须返回一个错误（错误代码402-挂机的手机）。
Line Side Answer Supervision (lsa): This provides Reverse Loop Current Feed (RLCF) on the line (refer to GR-506-CORE [7]) and is a way of indicating that the called party has answered for some line-side equipment.
线路侧应答监控（lsa）：这在线路上提供反向回路电流馈送（RLCF）（参考GR-506-CORE[7]），是指示被叫方已对某些线路侧设备应答的一种方式。
Message Waiting Indicator (mwi): Message Waiting indicator tone uses the same frequencies and levels as dial tone (350 and 440 Hertz at -13dBm each), but with a cadence of 0.1 second on, 0.1 second off, repeated 10 times, followed by steady application of dial tone. See GR-506-CORE [7], Section 17.2.3. It is considered an error to try and play message-waiting indicator on a phone that is on-hook and an error MUST consequently be returned when such attempts are made (error code 402 - phone on-hook).
消息等待指示器（mwi）：消息等待指示器音调使用与拨号音相同的频率和级别（每种频率为-13dBm时为350和440赫兹），但节拍为打开0.1秒，关闭0.1秒，重复10次，然后稳定应用拨号音。参见GR-506-CORE[7]，第17.2.3节。在挂机的手机上尝试播放消息等待指示灯被视为错误，因此在进行此类尝试时必须返回错误（错误代码402-挂机的手机）。
Network Busy (nbz): This is included here to maintain compatibility with the previous version of this package. The "nbz" signal is an alias for re-order tone signal("ro"). Future Call Agent implementations that require a network busy signal should use the "ro" signal. It is also recommended that future Call Agents not request to be notified of the "nbz" event (a network busy event is generally not required in a line package; hence, "ro" is only a signal, not an event).
网络繁忙（nbz）：此处包含此选项是为了保持与此软件包的早期版本的兼容性。“nbz”信号是重新订购音调信号（“ro”）的别名。未来需要网络忙信号的呼叫代理实现应使用“ro”信号。还建议未来的呼叫代理不要请求通知“nbz”事件（线路包中通常不需要网络忙事件；因此，“ro”只是一个信号，而不是事件）。
Operation Complete (oc): This is the standard definition of operation complete [1].
操作完成（oc）：这是操作完成[1]的标准定义。
Operation Failure (of): This is the standard definition of operation failure [1].
操作失败（of）：这是操作失败的标准定义[1]。
Network Disconnect (osi): Network Disconnect indicates that the far-end party has disconnected. The signal that is sent on the line is provisioned in the media gateway since it may vary from country to country. In North America, this signal is an open switch interval which results in a Loop Current Feed Open Signal (LCFO) being applied to the line (refer to GR-506-CORE [7], see also See GR-505-CORE [6], Section 4.5.2.1). The default time-out value for this signal is 900 ms.
网络断开连接（osi）：网络断开连接表示远端方已断开连接。线路上发送的信号在媒体网关中设置，因为它可能因国家而异。在北美，该信号为开路开关间隔，导致回路电流馈电开路信号（LCFO）应用于线路（参考GR-506-CORE[7]，另见GR-505-CORE[6]，第4.5.2.1节）。此信号的默认超时值为900毫秒。
Off-hook Warning Tone (ot): Off-hook warning tone, also known as receiver Off-Hook Tone (ROH Tone). This is the irritating noise a telephone makes when it is not hung up correctly. In North America, ROH Tone is generated by combining four tones at frequencies of 1400 Hertz, 2060 Hertz, 2450 Hertz and 2600 Hertz, at a cadence of 0.1 second on, 0.1 second off, then repeating. GR-506-CORE [7], Section 17.2.8 contains details about required power levels. It is considered an error to try and play off-hook warning tone on a phone that is on-hook, and an error MUST consequently be returned when such attempts are made (error code 402 - phone on-hook).
摘机警告音（ot）：摘机警告音，也称为接收机摘机音（ROH音）。这是电话挂断不正确时发出的恼人噪音。在北美，ROH音调是通过组合频率为1400赫兹、2060赫兹、2450赫兹和2600赫兹的四个音调，以0.1秒打开、0.1秒关闭的节奏产生的，然后重复。GR-506-CORE[7]，第17.2.8节包含有关所需功率水平的详细信息。尝试在挂机的手机上播放挂机警告音被视为错误，因此在进行此类尝试时必须返回错误（错误代码402-挂机电话）。
Prompt Tone (p): The definition of the prompt tone and its use may be found in requirement GR-220 [20]. The tone in GR-220 (requirement "R3-170" or GR-220) is a 300 ms burst of a 400 Hz tone.
提示音（p）：提示音的定义及其使用可在要求GR-220[20]中找到。GR-220中的音调（要求“R3-170”或GR-220）是400 Hz音调的300毫秒突发。
Ringing (rg): See GR-506-CORE [7], Section 14. The provisioning process may define the ringing cadence. The ringing signal may be parameterized with the signal parameter "rep" which specifies the maximum number of ringing cycles (repetitions) to apply. The value for "rep" is specified in decimal and can have any value from 1 to 255. The following will apply the ringing signal for up to 6 ringing cycles:
振铃（rg）：见GR-506-CORE[7]，第14节。供应过程可定义振铃节奏。振铃信号可通过信号参数“rep”进行参数化，该参数指定了要应用的最大振铃周期数（重复次数）。“rep”的值以十进制形式指定，可以有1到255之间的任意值。以下将应用振铃信号最多6个振铃周期：
S: l/rg(rep=6)
S: l/rg(rep=6)
If the "rep" parameter is specified, the signal times-out when the number of repetitions are completed (i.e., an operation complete event can be requested and will occur at the end of the timeout/number of rings).
如果指定了“rep”参数，则信号在重复次数完成时超时（即，可以请求操作完成事件，并将在超时/响铃次数结束时发生）。
If the "rep" parameter is supplied, then any timeout ("to") value that is included will be ignored, i.e.:
如果提供了“rep”参数，则将忽略包含的任何超时（“to”）值，即：
S: l/rg(rep=6,to=12000)
S: l/rg(rep=6,to=12000)
will be treated the same as the previous example where the parameter "to=12000" was not included. Of course, if the "to" parameter is included without the "rep", it will be acted upon i.e.:
将被视为与上一示例相同，其中未包括参数“to=12000”。当然，如果包含“to”参数而不包含“rep”，则将对其进行操作，即：
S: l/rg(to=12000)
S: l/rg(to=12000)
will ring for 12 seconds.
将响12秒。
It is considered an error to try and ring a phone that is off-hook and an error MUST consequently be returned when such attempts are made (error code 401 - phone off-hook).
尝试拨打挂断的电话被视为错误，因此在进行此类尝试时必须返回错误（错误代码401-电话挂断）。
Distinctive Ringing (r0, r1, r2, r3, r4, r5, r6 or r7): See GR-506-CORE [7], Section 14. Default values for r1 to r5 are as defined for distinctive ringing pattern 1 to 5 in GR-506-CORE [7]. The default values for r0, r6 and r7 are normal ringing (i.e., the same cadence "rg"). The provisioning process may define the ringing cadence for each of these signals. The distinctive ringing signals may be parameterized with the signal parameter "rep" which specifies the maximum number of ringing cycles (repetitions) to apply. The value for "rep" is specified in decimal and can have any value from 1 to 255.
独特振铃（r0、r1、r2、r3、r4、r5、r6或r7）：见GR-506-CORE[7]，第14节。r1至r5的默认值与GR-506-CORE[7]中的独特振铃模式1至5的定义相同。r0、r6和r7的默认值为正常振铃（即相同的节奏“rg”）。供应过程可以为这些信号中的每一个定义振铃节奏。独特的振铃信号可通过信号参数“rep”进行参数化，该参数指定要应用的最大振铃周期数（重复次数）。“rep”的值以十进制形式指定，可以有1到255之间的任意值。
The following will apply the ringing signal for up to 6 ringing cycles:
以下将应用振铃信号最多6个振铃周期：
S: l/r1(rep=6)
S: l/r1(rep=6)
If the "rep" parameter is specified, the signal times-out when the number of repetitions are completed (i.e., an operation complete event can be requested and will occur at the end of the timeout/number of rings)
如果指定了“rep”参数，则信号在重复次数完成时超时（即，可以请求操作完成事件，并将在超时/响铃次数结束时发生）
If the "rep" parameter is supplied, then any timeout ("to") value that is included will be ignored, i.e.:
如果提供了“rep”参数，则将忽略包含的任何超时（“to”）值，即：
S: l/r1(rep=6,to=12000)
S: l/r1(rep=6,to=12000)
will be treated the same as the previous example where the parameter "to=12000" was not included. Of course, if the "to" parameter is included without the "rep", it will be acted upon i.e.:
将被视为与上一示例相同，其中未包括参数“to=12000”。当然，如果包含“to”参数而不包含“rep”，则将对其进行操作，即：
S: l/r1(to=12000)
S: l/r1(to=12000)
will ring for 12 seconds.
将响12秒。
It is considered an error to try and ring a phone that is off-hook and an error MUST consequently be returned when such attempts are made (error code 401 - phone off-hook).
尝试拨打挂断的电话被视为错误，因此在进行此类尝试时必须返回错误（错误代码401-电话挂断）。
Reorder Tone (ro): This maps to congestion tone in the ITU-T E.182 [10] specification. In North America, reorder tone is a combination of two AC tones with frequencies of 480 and 620 Hertz, and levels of -24 dBm each, to give a combined level of -21 dBm. The cadence for reorder tone is 0.25 seconds on, followed by 0.25 seconds off, repeating continuously.
重排序音调（ro）：这映射到ITU-T E.182[10]规范中的拥塞音调。在北美，重排序音调是两个交流音调的组合，频率分别为480和620赫兹，电平分别为-24 dBm，组合电平为-21 dBm。重新排序音调的节奏为0.25秒打开，然后是0.25秒关闭，持续重复。
Ringsplash (rs): Also known as "Reminder ring", this tone is a burst of ringing that may be applied to the physical forwarding line (when idle) to indicate that a call has been forwarded and to remind the user that a Call Forward sub-feature is active. In the US, it is defined to be a 0.5(-0,+0.1) second burst of power ringing (see [11]).
Ringsplash（rs）：也称为“提醒铃声”，此铃声是一种突发铃声，可应用于物理转发线路（空闲时），以指示呼叫已转发，并提醒用户呼叫转发子功能处于活动状态。在美国，它被定义为0.5（-0，+0.1）秒的电源振铃突发（见[11]）。
Distinctive Tone Pattern (s(###)): This is used to signal or detect a tone pattern defined by the parameter where the parameter may have a value from 0 to 999. When specified as an event, the parameter MUST be included. The parameter will also be included when the event is reported. This event (the definition of tones associated with each parameter value) requires special provisioning in the Call Agent and gateway to insure interoperability. This signal is included here to maintain compatibility with the previous version of this package.
独特的音调模式（s（#####））：用于向参数定义的音调模式发送信号或检测该模式，其中参数的值可能在0到999之间。当指定为事件时，必须包含参数。报告事件时，还将包括该参数。此事件（与每个参数值关联的音调定义）需要在呼叫代理和网关中进行特殊设置，以确保互操作性。此处包含此信号是为了保持与此软件包以前版本的兼容性。
Special Information Tone(sit(#)): As described in ITU-T E.180 [8], the special information tone consists of a tone period in which 3 tones are produced, followed by a silent period of 1 second (total TO period of approximately 2 seconds). It MAY be parameterized with a parameter value from 1 to 7, with the following meaning as defined in SR-2275, section 6.21.2 [5]:
特殊信息音（sit（#））：如ITU-T E.180[8]中所述，特殊信息音由一个音调周期组成，其中产生3个音调，然后是1秒的静音周期（总计约2秒）。可使用1至7的参数值对其进行参数化，其含义如SR-2275第6.21.2[5]节所定义：
-------------------------------------------
| sit(1) | RO' | reorder SIT, intra-LATA |
| sit(2) | RO" | reorder SIT, inter-LATA |
| sit(3) | NC' | no circuit SIT, intra-LATA |
| sit(4) | NC" | no circuit SIT, inter-LATA |
| sit(5) | IC | intercept SIT |
| sit(6) | VC | vacant code SIT |
| sit(7) | IO | ineffective other SIT |
-------------------------------------------
-------------------------------------------
| sit(1) | RO' | reorder SIT, intra-LATA |
| sit(2) | RO" | reorder SIT, inter-LATA |
| sit(3) | NC' | no circuit SIT, intra-LATA |
| sit(4) | NC" | no circuit SIT, inter-LATA |
| sit(5) | IC | intercept SIT |
| sit(6) | VC | vacant code SIT |
| sit(7) | IO | ineffective other SIT |
-------------------------------------------
If the parameter is left out, the NC' SIT tone that corresponds to the signal "L/sit(3)" is assumed.
如果忽略该参数，则假定与信号“L/SIT（3）”相对应的NC“SIT”音调。
Other countries may have one or more special information tones with country specific definitions (refer to ITU-T E.180 supp. 2 [9]). In this case, special information tone 1 as defined in [9] is sit(1), special information tone 2 is sit(2) etc.
其他国家可能有一个或多个具有国家特定定义的特殊信息音（请参阅ITU-T E.180补充2[9]）。在这种情况下，[9]中定义的特殊信息音调1为sit（1），特殊信息音调2为sit（2）等。
Stutter Dial Tone (sl): Stutter Dial Tone (also called Recall Dial Tone in GR-506-CORE [7] and "special dial tone" in ITU-T E.182 [10]) is used to confirm some action and request additional input from the user. An example application is to cancel call-waiting, prior to entering a destination address.
口吃拨号音（sl）：口吃拨号音（GR-506-CORE[7]中也称为召回拨号音，ITU-T E.182[10]中称为“特殊拨号音”）用于确认某些操作并请求用户提供额外输入。一个示例应用程序是在输入目的地地址之前取消呼叫等待。
The stutter dial tone signal may be parameterized with the signal parameter "del", which will specify a delay in milliseconds to apply between the confirmation tone and the dial tone. The parameter can have any value from 0 to 10000 ms, rounded to the nearest non-zero value divisible by 100 (i.e., tenth of a second). The following will apply stutter dial tone with a delay of 1.5 seconds between the confirmation tone and the dial tone:
口吃拨号音信号可通过信号参数“del”进行参数化，该参数将指定在确认音和拨号音之间应用的延迟（以毫秒为单位）。该参数可以有0到10000 ms的任意值，四舍五入到可被100整除的最接近的非零值（即十分之一秒）。以下将应用口吃拨号音，确认音和拨号音之间的延迟为1.5秒：
S: l/sl(del=1500)
S: l/sl(del=1500)
It is considered an error to try and play stutter dial tone on a phone that is on-hook and an error MUST consequently be returned when such attempts are made (error code 402 - phone on-hook).
在挂机的电话上尝试播放口吃拨号音被视为错误，因此在进行此类尝试时必须返回错误（错误代码402-挂机电话）。
Alerting Tone (v): A 440 Hz Tone of a 2 second duration, followed by a 1/2 second of tone every 10 seconds. This event is included for backwards compatibility with the previous version of the package.
警报音（v）：持续时间为2秒的440 Hz音调，随后每10秒发出1/2秒的音调。包含此事件是为了与包的早期版本向后兼容。
Visual Message Waiting Indicator (vmwi): The transmission of the VMWI messages will conform to the requirements in [13] and the CPE guidelines in [12]. Refer also to section 6.6 of GR-30-CORE [14]. VMWI messages will only be sent from the gateway to the attached equipment when the line is idle. If new messages arrive while the line is busy, the VMWI indicator message will be delayed until the line goes back to the idle state. After the gateway restarts, the state of the signal will be "off", and hence the Call Agent MUST refresh the CPE's visual indicator if it is supposed to be "on".
可视消息等待指示器（vmwi）：vmwi消息的传输将符合[13]中的要求和[12]中的CPE指南。另请参阅GR-30-CORE[14]第6.6节。只有当线路空闲时，VMWI消息才会从网关发送到连接的设备。如果新消息在线路繁忙时到达，VMWI指示灯消息将延迟，直到线路返回空闲状态。网关重新启动后，信号的状态将为“关闭”，因此呼叫代理必须刷新CPE的可视指示器（如果该指示器应为“打开”）。
Alternative Call Waiting Tones (wt, wt1, .., wt4): Refer to ITU-T E.180 [8]. For North American tone definitions, refer to GR-506-CORE [7], Section 14.2. "wt" and "wt1" are both aliases for the default Call Waiting tone, which in North America, is a 440-Hz tone applied for 300 plus or minus 50 ms. The tone is then repeated once after 10 seconds.
备选呼叫等待音（wt、wt1、wt4）：参考ITU-T E.180[8]。有关北美音调定义，请参考GR-506-CORE[7]，第14.2节。“wt”和“wt1”都是默认呼叫等待音调的别名，在北美，默认呼叫等待音调为440 Hz，持续时间为300±50 ms。然后在10秒后重复该音调一次。
These signals are timeout signals with a default timeout value of 12 seconds, which allows the tone to be played twice with a single request (refer to GR-571-CORE [16]). However, there are cases (Requirement R3-73 of GR-575-CORE [18]), in which only a single tone is required. In that case, the Call Agent may make the request with a shorter timeout period to eliminate the second tone (e.g., "S: wt(to=2000)" - which stops the signal after 2 seconds so that the second tone will not occur).
这些信号是超时信号，默认超时值为12秒，允许通过一个请求播放两次音调（参考GR-571-CORE[16]）。但是，在某些情况下（GR-575-CORE[18]的要求R3-73），只需要单音。在这种情况下，呼叫代理可以以较短的超时时间发出请求以消除第二音调（例如，“S:wt（to=2000）”-其在2秒后停止信号，以便第二音调不会发生）。
Signals wt2, wt3 and wt4 are alternates that are used for distinctive call-waiting tone patterns (refer to GR-506-CORE, Section 14.2 [7]. It is considered an error to try and apply call-waiting tone on a phone that is on-hook and an error MUST consequently be returned when such attempts are made (error code 402 - phone on-hook).
信号wt2、wt3和wt4是用于不同呼叫等待音调模式的替代信号（参考GR-506-CORE，第14.2[7]节）。尝试在挂接的电话上应用呼叫等待音调被视为错误，因此在进行此类尝试时必须返回错误（错误代码402-挂接电话）。
Recorder Warning Tone(y): Refer to ITU-T E.180 [8] - also Bellcore document SR-2275 [5] section 6.20. When recording equipment is used, this tone is connected to the line to inform the distant party that the conversation is being recorded - typical value used is a 1400 Hz Tone of a 0.5 second duration every 15 seconds.
记录器警告音（y）：参考ITU-T E.180[8]-以及Bellcore文件SR-2275[5]第6.20节。当使用录音设备时，将此音调连接到线路，以通知远方的一方正在录制对话-使用的典型值为1400 Hz音调，每15秒持续0.5秒。
Calling Card Service Tone(z): This tone is used to inform the customer that credit card information must be keyed in. Typically, it consists of 60 ms of 941 + 1477 Hz (the DTMF #digit) and 940 ms of 350 + 440 Hz (dial tone), decaying exponentially with a time constant of 200 ms. Refer to Bellcore document SR-2275 [5], section 6.20.
电话卡服务提示音（z）：此提示音用于通知客户必须输入信用卡信息。通常，它由60毫秒的941+1477赫兹（双音多频数字）和940毫秒的350+440赫兹（拨号音）组成，以指数形式衰减，时间常数为200毫秒。参考Bellcore文件SR-2275[5]，第6.20节。
Package Name: H Version: 1
软件包名称：H版本：1
----------------------------------------------------------------
|Symbol | Definition | R | S Duration |
|----------------------------------------------------------------|
|adsi(string) | ADSI Display | x | BR |
|aw | Answer Tone | x | OO |
|bz | Busy Tone | x | TO 30 sec. |
|ci(ti,nu,na) | Caller-id | x | BR |
|dl | Dial Tone | x | TO 16 sec. |
|e | Error Tone | x | TO 2 sec. |
|hd | Off-hook Transition | S | BR |
|hu | On-hook Transition | S | BR |
|hf | Flash Hook | x | BR |
|ht | Tone On Hold | x | OO |
|lsa | Line Side Answer Sup. | x | OO |
|mwi | Message Waiting Ind. | x | TO 16 sec. |
|nbz | Network Busy | x | TO infinite |
|oc | Operation Complete | x | |
|ot | Off-hook Warning Tone | x | TO infinite |
|of | Operation Failure | x | |
|osi | Network Disconnect | x | TO 900 ms |
|p | Prompt Tone | x | BR |
|rg | Ringing | x | TO 180 sec. |
|r0, r1, r2, | Distinctive Ringing | x | TO 180 sec. |
|r3, r4, r5, | | | |
|r6 or r7 | | | |
|ro | Reorder Tone | x | TO 30 sec. |
|rs | Ringsplash | x | BR |
|s(###) | Distinctive Tone Pattern | x | BR |
|sit(#) | Sit Tone | x | TO 2 sec. |
|sl | Stutter Dial Tone | x | TO 16 sec. |
|v | Alerting Tone | x | OO |
|vmwi | Vis. Message Waiting Ind.| x | OO |
|wt | Call Waiting tone | x | TO 12 sec. |
|wt1, wt2, | Alternative Call | x | TO 12 sec |
|wt3, wt4 | Waiting Tones | | (see notes) |
|y | Recorder Warning Tone | x | TO infinite |
|z | Calling Card Serv. Tone | x | BR |
----------------------------------------------------------------
----------------------------------------------------------------
|Symbol | Definition | R | S Duration |
|----------------------------------------------------------------|
|adsi(string) | ADSI Display | x | BR |
|aw | Answer Tone | x | OO |
|bz | Busy Tone | x | TO 30 sec. |
|ci(ti,nu,na) | Caller-id | x | BR |
|dl | Dial Tone | x | TO 16 sec. |
|e | Error Tone | x | TO 2 sec. |
|hd | Off-hook Transition | S | BR |
|hu | On-hook Transition | S | BR |
|hf | Flash Hook | x | BR |
|ht | Tone On Hold | x | OO |
|lsa | Line Side Answer Sup. | x | OO |
|mwi | Message Waiting Ind. | x | TO 16 sec. |
|nbz | Network Busy | x | TO infinite |
|oc | Operation Complete | x | |
|ot | Off-hook Warning Tone | x | TO infinite |
|of | Operation Failure | x | |
|osi | Network Disconnect | x | TO 900 ms |
|p | Prompt Tone | x | BR |
|rg | Ringing | x | TO 180 sec. |
|r0, r1, r2, | Distinctive Ringing | x | TO 180 sec. |
|r3, r4, r5, | | | |
|r6 or r7 | | | |
|ro | Reorder Tone | x | TO 30 sec. |
|rs | Ringsplash | x | BR |
|s(###) | Distinctive Tone Pattern | x | BR |
|sit(#) | Sit Tone | x | TO 2 sec. |
|sl | Stutter Dial Tone | x | TO 16 sec. |
|v | Alerting Tone | x | OO |
|vmwi | Vis. Message Waiting Ind.| x | OO |
|wt | Call Waiting tone | x | TO 12 sec. |
|wt1, wt2, | Alternative Call | x | TO 12 sec |
|wt3, wt4 | Waiting Tones | | (see notes) |
|y | Recorder Warning Tone | x | TO infinite |
|z | Calling Card Serv. Tone | x | BR |
----------------------------------------------------------------
The handset emulation package is similar to the line package except that events such as "off-hook" can be signaled as well as detected.
手机模拟软件包与line软件包类似，不同的是，诸如“摘机”之类的事件可以通过信号发送和检测。
Changes from the original package - are the same changes as were made for the line package, plus "hu" and "hd" signal types were changed from OO to BR.
原始包的更改-与线路包的更改相同，加上“hu”和“hd”信号类型从OO更改为BR。
Event definitions are the same as for the line package with the following exceptions:
事件定义与行包的定义相同，但有以下例外：
ASDI: When requested as an event by the Call Agent, the event is not parameterized. However, the parameter is included when the event is reported.
ASDI：当调用代理作为事件请求时，事件不会参数化。但是，报告事件时会包含该参数。
Caller-id: When requested as an event by the Call Agent, the event MUST not be parameterized. However, parameters are included when the event is reported i.e.:
呼叫者id：当呼叫代理作为事件请求时，事件不得参数化。但是，在报告事件时包括参数，即：
O: l/ci(09/14/17/26,"555 1212","John Doe")
O: l/ci(09/14/17/26,"555 1212","John Doe")
Line Side Answer Supervision: When requested as an event by the Call Agent, it indicates when the reverse loop current feed (RLCF) was turned on and off. The event is not parameterized when it is requested. However, a parameter is included when it is reported i.e.:
线路侧应答监控：当呼叫代理作为事件请求时，它指示反向回路电流馈送（RLCF）的开启和关闭时间。请求时，事件未参数化。但是，报告时包含一个参数，即：
O: l/lsa(+) to indicate RLCF was turned on
O: l/lsa(-) to indicate RLCF was turned off
O: l/lsa(+) to indicate RLCF was turned on
O: l/lsa(-) to indicate RLCF was turned off
Ringing (rg): When requested as an event, the Call Agent may optionally include the rep parameter indicating a request to report after some number of rings e.g.:
振铃（rg）：当作为一个事件被请求时，呼叫代理可以选择性地包括rep参数，该参数指示在若干次振铃后报告的请求，例如：
RQNT 1234 aaln/1@rgw2.example.net
X: AB123FE0
R: h/rg(N)(rep=3)
RQNT 1234 aaln/1@rgw2.example.net
X: AB123FE0
R: h/rg(N)(rep=3)
The resulting notification after the number of rings is detected includes the parameter again:
检测到环数后产生的通知再次包含以下参数：
NTFY 3002 ds/ds1-3/6@gw-o.whatever.net MGCP 1.0
X: AB123FE0
O: h/rg(rep=3)
NTFY 3002 ds/ds1-3/6@gw-o.whatever.net MGCP 1.0
X: AB123FE0
O: h/rg(rep=3)
If the parameter is not included in the request, it is also not included in the report. In that case, the event is reported as soon as ringing is detected.
如果该参数未包含在请求中，则该参数也不会包含在报告中。在这种情况下，一旦检测到振铃，就会报告该事件。
Distinctive Ringing (r0, r1, r2, r3, r4, r5, r6 or r7): As with the "rg" event, if the "rep" parameter is included when one of these is requested as an event, it is also reported. If it is not requested with the parameter, then the parameter is also not included in the report. In that case, the event is reported as soon as ringing with the requested cadence is detected.
独特的振铃（r0、r1、r2、r3、r4、r5、r6或r7）：与“rg”事件一样，如果其中一个作为事件请求时包含“rep”参数，则也会报告。如果未随参数一起请求，则该参数也不会包含在报告中。在这种情况下，一旦检测到具有请求的节奏的振铃，就会报告该事件。
Stutter Dial Tone (sl): Stutter Dial Tone MUST not be parameterized when requested as an event. However, the "del" parameter is reported.
口吃拨号音（sl）：作为事件请求时，口吃拨号音不得参数化。但是，报告了“del”参数。
RQNT 1234 aaln/1@rgw2.example.net
X: AB123FE0
R: h/sl
RQNT 1234 aaln/1@rgw2.example.net
X: AB123FE0
R: h/sl
The resulting notification indicates the delay between the confirmation tone and the dial tone:
产生的通知指示确认音和拨号音之间的延迟：
NTFY 3002 ds/ds1-3/6@gw-o.whatever.net MGCP 1.0
X: AB123FE0
O: h/sl(del=1500)
NTFY 3002 ds/ds1-3/6@gw-o.whatever.net MGCP 1.0
X: AB123FE0
O: h/sl(del=1500)
As with the signal, the report indicates the delay rounded to the nearest 100 ms.
与信号一样，报告显示延迟四舍五入到最接近的100毫秒。
Visual Message Waiting: When requested as an event by the Call Agent, it indicates when the visual message waiting indicator was turned on and off. The event is not parameterized when it is requested. However, a parameter is included when it is reported i.e.:
可视消息等待：当呼叫代理作为事件请求时，它指示可视消息等待指示灯何时打开和关闭。请求时，事件未参数化。但是，报告时包含一个参数，即：
O: l/vmwi(+) to indicate message waiting turned on
O: l/vmwi(-) to indicate message waiting turned off
O: l/vmwi(+) to indicate message waiting turned on
O: l/vmwi(-) to indicate message waiting turned off
Note that:
请注意：
* All TO signals in the handset package can include a "to" parameter when requested as a signal.
* 当作为信号请求时，手持设备包中的所有TO信号都可以包含“TO”参数。
* However, requests to be notified about these events MUST NOT include the "to" parameter, i.e., the "to" parameter is not valid in RequestedEvents.
* 但是，要通知这些事件的请求不得包含“to”参数，即“to”参数在RequestedEvents中无效。
Package Name: SST Version: 0
包名称：SST版本：0
---------------------------------------------------------------
|Symbol | Definition | R | S Duration |
|---------------------------------------------------------------|
|cd | Conference Depart | | BR |
|cj | Conference Join | | BR |
|cm | Comfort Tone | | TO infinite |
|cw | Caller Waiting Tone | | TO 30 sec. |
|ht | On Hold Tone | | OO |
|ni | Negative Indication | | TO infinite |
|nu | Number Unobtainable | | TO infinite |
|oc | Operation Complete | x | |
|of | Operation Failure | x | |
|pr | Pay Phone Recognition | | BR |
|pt | Pay Tone | | BR |
----------------------------------------------------------------
---------------------------------------------------------------
|Symbol | Definition | R | S Duration |
|---------------------------------------------------------------|
|cd | Conference Depart | | BR |
|cj | Conference Join | | BR |
|cm | Comfort Tone | | TO infinite |
|cw | Caller Waiting Tone | | TO 30 sec. |
|ht | On Hold Tone | | OO |
|ni | Negative Indication | | TO infinite |
|nu | Number Unobtainable | | TO infinite |
|oc | Operation Complete | x | |
|of | Operation Failure | x | |
|pr | Pay Phone Recognition | | BR |
|pt | Pay Tone | | BR |
----------------------------------------------------------------
Note that default time-out values may be over-ridden by the Call Agent for any Time-Out signal defined in this package by a "to" signal parameter. Refer to section 2 of this document, as well as [1] for details.
请注意，对于此包中由“to”信号参数定义的任何超时信号，调用代理可能会覆盖默认超时值。有关详细信息，请参阅本文件第2节以及[1]。
The events in this package are defined as follows:
此包中的事件定义如下：
Conference Depart(cd): Tone used to indicate that a participant has left a conference call. The tone characteristics are left to the specific gateway implementation.
会议离开（cd）：用于表示参与者已离开电话会议的音调。音调特征由特定网关实现决定。
Conference Join (cj): Tone used to indicate that a party has joined a conference call. The tone characteristics are left to the specific gateway implementation.
Conference Join（cj）：用于表示一方已加入电话会议的音调。音调特征由特定网关实现决定。
Comfort Tone (cm): Comfort Tone is used to indicate that the call is being processed and that the caller should wait. Refer to ITU-T E.182 [10].
舒适提示音（cm）：舒适提示音用于指示呼叫正在处理，呼叫方应等待。参考ITU-T E.182[10]。
Caller Waiting Tone (cw): Not to be confused with a call-waiting tone, this is a tone advising a caller that a called station, though busy, has a call waiting service active. Refer to ITU-T E.182 [10].
呼叫者等待音（cw）：不要与呼叫等待音混淆，这是一种提示呼叫者被叫站虽然忙，但有呼叫等待服务处于活动状态的音。参考ITU-T E.182[10]。
Tone on-hold (ht): A tone used to reassure a calling subscriber who has been placed on "hold". Refer to ITU-T E.182 [10].
等待音（ht）：一种用来使处于“等待”状态的主叫用户放心的音。参考ITU-T E.182[10]。
Negative Indication (ni): A tone advising a subscriber that the request for service cannot be accepted. Refer to ITU-T E.182 [10]. For North America, this maps to the re-order tone (see GR-506-CORE [7], Section 17.2.7).
负面指示（ni）：提示用户无法接受服务请求的音调。参考ITU-T E.182[10]。对于北美，这映射到重新订购音调（参见GR-506-CORE[7]，第17.2.7节）。
Number Unobtainable Tone (nu): Refer to ITU-T E.180, supplement 2 [9]. This is also referred to as "vacant tone" and maps to a "re-order tone" in North America (see GR-506-CORE [7], Section 17.2.7).
数字不可获得音调（nu）：参考ITU-T E.180，补充2[9]。这也称为“空置音调”，并映射到北美的“重新订购音调”（见GR-506-CORE[7]，第17.2.7节）。
Operation Complete (oc): The standard definition of operation complete [1].
操作完成（oc）：操作完成的标准定义[1]。
Operation Failure (of): The standard definition of operation failure [1].
操作失败（of）：操作失败的标准定义[1]。
Pay Phone Recognition (pr): A tone advising an operator that the endpoint is identified as a payphone. Refer to ITU-T E.182 [10].
付费电话识别（pr）：提示运营商终端被识别为付费电话的音调。参考ITU-T E.182[10]。
Pay Tone (pt): A tone indicating that payment is required. Refer to ITU-T E.182 [10].
付款提示音（pt）：表示需要付款的提示音。参考ITU-T E.182[10]。
Package Name: dm1 ("dm" followed by the number "1") Version: 0 Extension Digit Map Letters: P
软件包名称：dm1（“dm”后跟数字“1”）版本：0扩展位映射字母：P
This package defines an Extension Digit Map Letter that is used to override the shortest possible match behavior for a given entry in a digit map (see [1]). The letter "P" (for partial match override), at the end of a digit map entry, instructs the gateway to only consider that entry a match if the current dial string does not partially match another entry. For example, given the digit map
此包定义了一个扩展数字映射字母，用于覆盖数字映射中给定条目的最短匹配行为（请参见[1]）。在数字地图条目的结尾，字母“p”（对于部分匹配重写）指示网关只考虑当前拨号字符串与另一个条目部分匹配时的条目是否匹配。例如，给定数字地图
([3-7]11|123xxxxxxx|[1-7]xxxxxxP|8xxxP)
（[3-7]11 | 123xxxxxxx |[1-7]xxxxxx p | 8xxxP）
and a current dial string of "1234567", we would not consider this a match (as the rules in [1] would otherwise imply); however a current dial string of "411" would be considered a match as usual. A current dial string of "8234" would be considered a match since there is no other partial match.
和当前拨号字符串“1234567”，我们不会认为这是一个匹配（如规则（1）将意味着）；但是，当前的拨号字符串“411”将被视为与通常的匹配。当前拨号字符串“8234”将被视为匹配，因为没有其他部分匹配。
Note that the digit map letter "P" is not an event, but simply a syntactic and semantic digit map extension. Thus, the "P" is not included in the list of requested or observed events.
请注意，数字映射字母“P”不是事件，只是一个语法和语义数字映射扩展。因此，“P”不包括在请求或观察到的事件列表中。
Support for this package is strongly RECOMMENDED.
强烈建议支持此软件包。
Package Name: SL Version: 0
包名称：SL版本：0
---------------------------------------------------------
| Symbol | Definition | R | S Duration |
|---------------------------------------------------------|
| oc | Operation Complete | x | |
| of | Operation Failure | x | |
| s(list) | Signal List | | TO variable |
---------------------------------------------------------
---------------------------------------------------------
| Symbol | Definition | R | S Duration |
|---------------------------------------------------------|
| oc | Operation Complete | x | |
| of | Operation Failure | x | |
| s(list) | Signal List | | TO variable |
---------------------------------------------------------
Operation Complete (oc): This is the standard definition of operation complete from [1].
操作完成（oc）：这是[1]中操作完成的标准定义。
Operation Failure (of): This is the standard definition of operation failure from [1].
操作失败（of）：这是[1]中操作失败的标准定义。
Signal List(s(<list>)): The <list> contains a comma-separated list of signals to be played out. Each of the signals in <list> MUST be either of type BR or type TO. Semantically, the signal list is still treated as a single parameterized signal of type Time-Out though. The signals in the list are played to completion one after the other in the left to right order specified. The package for each signal in the list must be specified. For example, to play out the DTMF digits 123456:
信号列表（<List>）：该列表包含以逗号分隔的要播放的信号列表。<list>中的每个信号必须是BR类型或TO类型。从语义上讲，信号列表仍然被视为类型为超时的单个参数化信号。列表中的信号按指定的从左到右顺序依次播放至结束。必须指定列表中每个信号的包装。例如，要播放DTMF数字123456：
S: sl/s(d/1,d/2,d/3,d/4,d/5,d/6)
S: sl/s(d/1,d/2,d/3,d/4,d/5,d/6)
This will result in the DTMF digits 1, 2, 3, 4, 5 and 6 being played out in order.
这将导致按顺序播放DTMF数字1、2、3、4、5和6。
It is illegal to include an OO signal as one of the signals in the list or to request recursive definitions (signal lists within signal lists). If this or any other unsupported signal is included, error code 538 (event/signal parameter error) MUST be returned by the gateway.
将OO信号作为信号之一包含在列表中或请求递归定义（信号列表中的信号列表）是非法的。如果包括此信号或任何其他不受支持的信号，网关必须返回错误代码538（事件/信号参数错误）。
Note that as the gateway plays the ordered list of signals, if it encounters a TO signal with an infinite timeout, it will continue to play that signal until the Signal List signal is stopped (i.e., other signals later in the list will never be played).
请注意，当网关播放有序的信号列表时，如果遇到无限超时的TO信号，它将继续播放该信号，直到信号列表信号停止（即，列表中稍后的其他信号将永远不会播放）。
If the operation complete ("oc") event is requested, it will be detected once, when the last signal in the list has been played out (regardless of whether there are any TO signals in the list). The operation complete event will only report the signal list name itself, i.e., without the parameters supplied as in:
如果请求操作完成（“oc”）事件，则在播放完列表中的最后一个信号时（无论列表中是否有TO信号），将检测到该事件一次。操作完成事件将只报告信号列表名称本身，即，不报告如中所提供的参数：
O: sl/oc(sl/s)
O: sl/oc(sl/s)
Should any of the signals in the signal list result in an error, an operation failure event for the Signal List signal MUST be generated. Only the signal list name will be included, thus it is not possible to determine which of the signals in the signal list actually failed.
如果信号列表中的任何信号导致错误，则必须生成信号列表信号的操作故障事件。仅包括信号列表名称，因此无法确定信号列表中的哪些信号实际出现故障。
Note that if an event occurs while the "SL/S" signal is playing, the "SL/S" signal is stopped in the following manner:
请注意，如果在播放“SL/S”信号时发生事件，“SL/S”信号将按以下方式停止：
* If the signal in the list that was playing at the time the event occurred is of type BR, then the BR signal will be played to completion and no other signals in the list will be played.
* 如果事件发生时正在播放的列表中的信号类型为BR，则BR信号将播放到结束，并且不会播放列表中的其他信号。
* If the signal in the list that was playing at the time the event occurred is of type TO, then the TO signal will stop immediately and no other signals in the list will be played.
* 如果事件发生时正在播放的列表中的信号类型为TO，则TO信号将立即停止，并且不会播放列表中的其他信号。
Package Name: FM Version: 0
包名称：FM版本：0
This package provides support for the media format parameter Local Connection Option (LCO). The media format parameter LCO is similar to the "fmtp" attribute in SDP [15] and is applicable to all of the same media formats that the corresponding SDP fmtp attribute could be used with (i.e., media format parameters for any media format MIME type). The media format parameter is encoded as the keyword "fmtp" or "o-fmtp", followed by a colon and a quoted string beginning with the media format name (MIME subtype only) followed by a space, followed by the media format parameters associated with that media format. For simplicity, we will use the terms "codec" and "media
此软件包支持媒体格式参数本地连接选项（LCO）。媒体格式参数LCO类似于SDP[15]中的“fmtp”属性，并适用于相应SDP fmtp属性可用于的所有相同媒体格式（即，任何媒体格式MIME类型的媒体格式参数）。媒体格式参数编码为关键字“fmtp”或“o-fmtp”，后跟冒号和以媒体格式名称（仅限MIME子类型）开头的带引号的字符串，后跟空格，后跟与该媒体格式关联的媒体格式参数。为简单起见，我们将使用术语“编解码器”和“媒体”
format" interchangeably in the following. Multiple formats may be indicated by either repeating the "fmtp" local connection option multiple times, such as:
“格式”可在以下格式中互换。可通过多次重复“fmtp”本地连接选项指示多种格式，例如：
L:a:codec1;codec2, fmtp:"codec1 formatX", fmtp:"codec2 formatY"
L:a:codec1;codec2, fmtp:"codec1 formatX", fmtp:"codec2 formatY"
or alternatively by having a single "fmtp" keyword followed by a colon, and a semi-colon separated list of quoted strings for each media format parameter, as in:
或者，为每个媒体格式参数提供一个单独的“fmtp”关键字，后跟一个冒号和一个分号分隔的带引号字符串列表，如下所示：
L:a:codec1;codec2, fmtp:"codec1 formatX";"codec2 formatY"
L:a:codec1;codec2, fmtp:"codec1 formatX";"codec2 formatY"
The two formats may be mixed.
这两种格式可以混合使用。
If it is possible for the same codec to be requested with and without the special "fmtp" format, the following could result:
如果有可能在使用和不使用特殊“fmtp”格式的情况下请求相同的编解码器，则可能会产生以下结果：
L:a:codec1;codec1, fmtp:"codec1 formatX"
L:a:codec1;codec1, fmtp:"codec1 formatX"
However, it would not be clear if the fmtp parameter was to be applied to the first or the second occurrence of the codec. The problem with that is, that codec ordering is important (i.e., codecs are listed in preferred order), and the above syntax does not provide a way to indicate if "formatX" is preferred (i.e., associated with the first "codec1") or not (i.e., associated with the second "codec1"). In order to resolve this dilemma, when the same codec is requested with multiple formats, the codec name in the "fmtp" format string is followed by a colon and an <order>, where <order> is a number from one to N for N occurrences of the same codec in the codec list i.e.:
但是，不清楚fmtp参数是应用于第一次还是第二次出现的编解码器。这方面的问题是，编解码器顺序很重要（即，编解码器以首选顺序列出），并且上述语法没有提供指示“formatX”是首选（即，与第一个“编解码器1”关联）还是非首选（即，与第二个“编解码器1”关联）的方法。为了解决这一难题，当使用多种格式请求同一编解码器时，“fmtp”格式字符串中的编解码器名称后跟冒号和<order>，其中<order>是编解码器列表中出现N个相同编解码器时从1到N的数字，即：
L:a:codec1;codec1, fmtp:"codec1:2 formatX"
L:a:codec1;codec1, fmtp:"codec1:2 formatX"
indicates that "formatX" is associated with the second instance of "codec1" in the "a:codec1;codec1" list. If an invalid instance number is supplied (e.g., instance 3 where there are only two instances), then error code 524 - inconsistency in local connection options will be returned.
指示“formatX”与“a:codec1；codec1”列表中“codec1”的第二个实例相关联。如果提供了无效的实例号（例如，实例3，其中只有两个实例），则返回错误代码524-本地连接选项不一致。
Pre-pending "fmtp" with the string "o-" (i.e., "o-fmtp") indicates that the format is optional. In that case, the gateway may decide not to use the fmtp parameter specified, or only use it in part.
带有字符串“o-”（即“o-fmtp”）的预挂起的“fmtp”表示格式是可选的。在这种情况下，网关可能决定不使用指定的fmtp参数，或仅部分使用它。
If the "fmtp" in an LCO is not optional (i.e., does not have "o-" in front of it), and the LCO value is either not recognized or not supported, then the associated codec is considered "not supported".
如果LCO中的“fmtp”不是可选的（即前面没有“o-”），并且LCO值不可识别或不受支持，则相关编解码器被视为“不受支持”。
When auditing capabilities, the "fmtp" local connection option MUST be returned with a semi-colon separated list of supported formats and/or multiple independent "fmtp" parameters as in:
审核功能时，“fmtp”本地连接选项必须返回一个分号分隔的支持格式列表和/或多个独立的“fmtp”参数，如下所示：
A: a:telephone-event, fmtp:"telephone-event 0-15,32-35",...
A:A：电话事件，fmtp：“电话事件0-15,32-35”，。。。
A: a:PCMU;G729, fmtp:"PCMU foo";"PCMU bar", fmtp:"G729 foobar",...
A:A:PCMU；G729，fmtp：“PCMU-foo”；“PCMU酒吧”，fmtp：“G729 foobar”，。。。
One example uses the media format parameter LCO in conjunction with the media format "telephone-event", as defined in RFC 2833 [33]. If the media format "telephone-event" is used without the "fmtp" media format parameter, the DTMF digits (telephone events 0-15 from RFC 2833 [33]) are assumed - such practice is however discouraged. On the other hand, the media format parameter LCO MAY be used to specify the exact set of events that are being requested via RFC 2833 [33]. Example:
一个示例将媒体格式参数LCO与RFC 2833[33]中定义的媒体格式“电话事件”结合使用。如果使用的媒体格式“电话事件”没有“fmtp”媒体格式参数，则假定DTMF数字（RFC 2833[33]中的电话事件0-15），但不鼓励这种做法。另一方面，媒体格式参数LCO可用于指定通过RFC 2833请求的确切事件集[33]。例子：
L: a:PCMU;telephone-event,fmtp:"telephone-event 16"
L: a:PCMU;telephone-event,fmtp:"telephone-event 16"
indicates that if telephone events are supported at all, then this request is specifically for event 16.
指示如果完全支持电话事件，则此请求专门针对事件16。
In another case, the Call Agent may indicate that some format parameters are "required", while others are optional. In the example below, telephone events 0-15 are a "must", while telephone events 16, 70 and 71 are optional.
在另一种情况下，调用代理可能指示某些格式参数是“必需的”，而其他格式参数是可选的。在下面的示例中，电话事件0-15是“必须”的，而电话事件16、70和71是可选的。
L: a:PCMU;telephone-event, o-fmtp:"telephone-event 16,70,71",
fmtp:"telephone-event 0-15"
L: a:PCMU;telephone-event, o-fmtp:"telephone-event 16,70,71",
fmtp:"telephone-event 0-15"
If the gateway cannot support telephone events 0-15, it MUST NOT include the "telephone-event" media format in the SDP in its response. On the other hand, if it can support those telephone events, it SHOULD indicate support for those events, as well as any of the events 16, 70 and 71 that it supports.
如果网关不支持电话事件0-15，则其响应中不得在SDP中包含“电话事件”媒体格式。另一方面，如果它可以支持这些电话事件，它应该表示支持这些事件，以及它支持的任何事件16、70和71。
If a request is made to audit the capabilities of an endpoint, and the endpoint supports the "telephone event" media format with events "0-16", then the audit would include the following:
如果请求审核端点的功能，且端点支持事件为“0-16”的“电话事件”媒体格式，则审核将包括以下内容：
A: a:telephone-event, fmtp: "telephone-event 0-16"
A: a:telephone-event, fmtp: "telephone-event 0-16"
Another example is the use of redundancy with RFC 2198 [32]. Again, the format of the fmtp string is similar to that used in the SDP except that the literal string ("red" in this case) is used rather than the payload type:
另一个例子是在RFC 2198[32]中使用冗余。同样，fmtp字符串的格式与SDP中使用的格式类似，只是使用了文本字符串（本例中为“红色”），而不是有效负载类型：
L: a:G729;pcmu;red,fmtp:"red pcmu/g729"
L: a:G729;pcmu;red,fmtp:"red pcmu/g729"
The corresponding media description in the SDP as part of the connection request acknowledgment might look like:
SDP中作为连接请求确认的一部分的相应媒体描述可能如下所示：
m=audio 12345 RTP/AVP 98 18 0
a=rtpmap:98 red/8000/1
a=fmtp:98 0/18
m=audio 12345 RTP/AVP 98 18 0
a=rtpmap:98 red/8000/1
a=fmtp:98 0/18
If we combine both telephone events and redundancy, an example local connection option might look as follows (carriage return added for formatting reasons here):
如果我们将电话事件和冗余结合起来，本地连接选项的示例可能如下所示（出于格式原因，此处添加了回车）：
L: a:G729;pcmu;red;telephone-event,fmtp:"red pcmu/g729",
fmtp: "telephone-event 16"
L: a:G729;pcmu;red;telephone-event,fmtp:"red pcmu/g729",
fmtp: "telephone-event 16"
Note that we again specify the literal string for the encoding method rather than its payload type. This is a general principle that should be used with this LocalConnectionOption.
请注意，我们再次为编码方法指定文本字符串，而不是其有效负载类型。这是应与此LocalConnectionOption一起使用的一般原则。
The corresponding SDP might appear as follows:
相应的SDP可能如下所示：
m=audio 12345 RTP/AVP 97 98 18 0
a=rtpmap:97 red/8000/1
a=fmtp:97 0/18
a=rtpmap:98 telephone event
a=fmtp:98 16
m=audio 12345 RTP/AVP 97 98 18 0
a=rtpmap:97 red/8000/1
a=fmtp:97 0/18
a=rtpmap:98 telephone event
a=fmtp:98 16
Note that the fmtp LCO may be used in any situation where the corresponding SDP attribute may be used. An example of a local connection option that involves a media type other than audio and a "foobar" fmtp parameter:
注意，fmtp LCO可用于任何可能使用相应SDP属性的情况。本地连接选项的一个示例涉及音频以外的媒体类型和“foobar”fmtp参数：
L: a:image/tiff, fmtp:"tiff foobar"
L: a:image/tiff, fmtp:"tiff foobar"
Note that normally local connection options that are associated with a package should have the package prefix included as per the package extension rules in [1]. The "fmtp" and "o-fmtp" LCO in the "FM" package are an exception. The package prefix is not included in the case of the "fmtp" and "o-fmtp" local connection options because they were created before the extension rules in [1] were defined.
请注意，根据[1]中的包扩展规则，通常与包关联的本地连接选项应包含包前缀。“FM”包中的“fmtp”和“o-fmtp”LCO是一个例外。“fmtp”和“o-fmtp”本地连接选项不包括包前缀，因为它们是在定义[1]中的扩展规则之前创建的。
These two LocalConnectionOptions have been registered with IANA.
这两个LocalConnectionOption已向IANA注册。
Package Name: R Version: 1
软件包名称：R版本：1
-------------------------------------------------------------
| Symbol | Definition | R | S Duration |
|-------------------------------------------------------------|
| co1 | Continuity Tone (single | C | TO,C 3 sec. |
| | or return tone) | | |
| co2 | Continuity Test (go tone, | C | TO,C 3 sec. |
| | in dual tone procedures) | | |
| iu(..) | ICMP Unreachable | C | |
| | Received | | |
| ji(..) | Jitter Buffer Size Changed | C | |
| ma | Media Start | C | |
| oc | Operation Complete | x | |
| of | Operation Failure | x | |
| pl(..) | Packet Loss Exceeded | C | |
| qa | Quality Alert | C | |
| rto(..) | RTP/RTCP Timeout | C | |
| sr | Sampling Rate Changed | C | |
| uc | Used Codec Changed | C | |
-------------------------------------------------------------
-------------------------------------------------------------
| Symbol | Definition | R | S Duration |
|-------------------------------------------------------------|
| co1 | Continuity Tone (single | C | TO,C 3 sec. |
| | or return tone) | | |
| co2 | Continuity Test (go tone, | C | TO,C 3 sec. |
| | in dual tone procedures) | | |
| iu(..) | ICMP Unreachable | C | |
| | Received | | |
| ji(..) | Jitter Buffer Size Changed | C | |
| ma | Media Start | C | |
| oc | Operation Complete | x | |
| of | Operation Failure | x | |
| pl(..) | Packet Loss Exceeded | C | |
| qa | Quality Alert | C | |
| rto(..) | RTP/RTCP Timeout | C | |
| sr | Sampling Rate Changed | C | |
| uc | Used Codec Changed | C | |
-------------------------------------------------------------
Changes in event types: "co1" and "co2" signals changed from OO to TO.
事件类型的变化：“co1”和“co2”信号从OO变为。
New events added to this package from the previously unversioned package: "iu", "rto", "ma".
从以前未版本的包中添加到此包的新事件：“iu”、“rto”、“ma”。
Note that default time-out values may be over-ridden by the Call Agent for any Time-Out signal defined in this package by a "to" signal parameter. Refer to section 2 of this document, as well as [1] for details.
请注意，对于此包中由“to”信号参数定义的任何超时信号，调用代理可能会覆盖默认超时值。有关详细信息，请参阅本文件第2节以及[1]。
The events in this package all refer to media streams (connections), i.e., they cannot be detected on an endpoint. Furthermore, with the exception of the "iu" event, which is defined for any type of media, all other events in this package are defined for RTP media streams only (i.e., if they are used on connections that do not use RTP, the behavior is not defined).
此包中的事件都涉及媒体流（连接），即在端点上无法检测到它们。此外，除了为任何类型的媒体定义的“iu”事件外，此包中的所有其他事件仅为RTP媒体流定义（即，如果它们用于不使用RTP的连接，则不定义行为）。
Signals requested (e.g., "co1" and "co2") must indicate the connection ID (e.g., "S: r/co1@connectionID"). An event may be requested for all existing connections using the "*" wildcard for the connectionID as described in [1].
请求的信号（如“co1”和“co2”）必须指示连接ID（如“S:r/co1@connectionID"). 可以使用[1]中所述的connectionID的“*”通配符为所有现有连接请求事件。
Example:
例子：
R: r/uc@* (request to detect uc on all connections) or
R: r/uc@* (request to detect uc on all connections) or
R: r/uc@connectionID (request to detect uc only on a specific connection)
R:R/uc@connectionID（请求仅在特定连接上检测uc）
An event detected on a connection will include the connectionID, e.g.:
在连接上检测到的事件将包括connectionID，例如：
O: r/uc@connectionID(15)
O: r/uc@connectionID(15)
Continuity tones (co1 and co2): These are the same as the events defined in the Trunk package, except in this case, they are only played over a network connection and the connectionID MUST be supplied (e.g., "s: r/co1@connectionID"). They can be used in conjunction with the Network LoopBack (netwloop) or Network Continuity Test (netwtest) modes to test the continuity of an RTP circuit. However, in the case of testing IP continuity, a one-tone test is sufficient i.e., generating and detecting "co1" at one end, with connection mode in network loopback mode at the other end. Note that the test can also be done using telephone events rather than tones, i.e., event 167 in RFC 2833 [33] corresponds to "co1". In this case, connection requests are made with local connection options such as:
连续性音调（co1和co2）：这些与中继包中定义的事件相同，但在这种情况下，它们仅通过网络连接播放，并且必须提供connectionID（例如，“s:r”）/co1@connectionID"). 它们可与网络环回（netwloop）或网络连续性测试（netwtest）模式结合使用，以测试RTP电路的连续性。然而，在测试IP连续性的情况下，单音测试就足够了，即在一端生成并检测“co1”，在另一端连接模式为网络环回模式。请注意，测试也可以使用电话事件而不是铃声进行，即RFC 2833[33]中的事件167对应于“co1”。在这种情况下，使用本地连接选项进行连接请求，例如：
L: a:PCMU;telephone-event,fmtp:"telephone-event 167"
L: a:PCMU;telephone-event,fmtp:"telephone-event 167"
in order to request support for telephone event 167. If both ends support the event, then the network loopback proceeds as usual, except that telephone events corresponding to the co1 tone are sent, as opposed to the co1 tone itself.
以请求对电话事件167的支持。如果两端都支持该事件，则网络环回照常进行，除了发送与co1音调相对应的电话事件，而不是co1音调本身。
ICMP Unreachable Received (iu): This event indicates that some number of ICMP unreachable packets [19] was received for this connection since an RQNT was received requesting this event. This notification indicates that packets that were sent by the gateway on this connection either did not arrive at their destination or were not accepted (e.g., the port was closed). When this event is requested, a single parameter with a decimal number from 1 to 255 may be included to indicate the number of ICMP un-reachable packets that must occur before the event is notified. If no parameter is supplied, with the request then a default value of 3 is assumed. This is a one-shot event in that once the event occurs, a further request is required in order to re-initiate counting.
ICMP Unreachable Received（iu）：此事件表示由于接收到请求此事件的RQNT，因此为此连接接收了一定数量的ICMP Unreachable数据包[19]。此通知表示网关在此连接上发送的数据包未到达目的地或未被接受（例如，端口已关闭）。当请求此事件时，可以包括一个十进制数为1到255的单个参数，以指示在通知事件之前必须发生的ICMP不可访问数据包的数量。如果请求中未提供任何参数，则假定默认值为3。这是一个一次性事件，一旦事件发生，需要进一步请求以重新启动计数。
The observed event is parameterized with two parameters:
观察到的事件通过两个参数进行参数化：
* The first parameter is the number of ICMP unreachable packets received (i.e., the same value that was included in the request - or the value 3, if the requested event was not parameterized)
* 第一个参数是接收到的ICMP不可访问数据包的数量（即，请求中包含的相同值，或者如果请求的事件未参数化，则为值3）
* The second parameter is the error code indicated in the ICMP unreachable packet, e.g.:
* 第二个参数是ICMP不可访问数据包中指示的错误代码，例如：
0 = net unreachable;
0=无法到达的净距离；
1 = host unreachable;
1=无法访问主机；
2 = protocol unreachable;
2=协议无法访问；
3 = port unreachable;
3=无法访问端口；
4 = fragmentation needed and DF set;
4=所需碎片和DF设置；
5 = source route failed.
5=源路由失败。
etc.
等
An example of a request might be as follows:
请求的示例可能如下所示：
RQNT 2001 ds/ds1-3/6@gw-o.whatever.net MGCP 1.0
X: 0123456789B0
R: r/iu@364823(N)(5)
RQNT 2001 ds/ds1-3/6@gw-o.whatever.net MGCP 1.0
X: 0123456789B0
R: r/iu@364823(N)(5)
In this case, a notify will occur if 5 ICMP port unreachable packets are received as a result of RTP and/or RTCP packets being sent from this gateway on the connection with connection ID 364823.
在这种情况下，如果在连接ID为364823的连接上从该网关发送RTP和/或RTCP数据包，从而收到5个ICMP端口不可访问的数据包，则会发出通知。
The resulting NTFY with observed events might be as follows:
观察到的事件产生的NTFY可能如下所示：
NTFY 3002 ds/ds1-3/6@gw-o.whatever.net MGCP 1.0
X: 0123456789B0
O: r/iu@364823(5,3)
NTFY 3002 ds/ds1-3/6@gw-o.whatever.net MGCP 1.0
X: 0123456789B0
O: r/iu@364823(5,3)
The first parameter indicates 5 ICMP unreachable packets were received since the RQNT with this request was sent. The second parameter ("3") specifies the reason, which in this case, is "port unreachable".
第一个参数表示自发送带有此请求的RQNT以来，收到了5个ICMP无法访问的数据包。第二个参数（“3”）指定原因，在本例中为“端口不可访问”。
Jitter Buffer Size Changed (ji): This event is only included here to maintain compatibility with the previous version of this package. This event is used to indicate that the gateway has made an adjustment to the depth of the jitter buffer. The syntax for requesting notification is "ji", which tells the media gateway that the controller wants notification of any jitter buffer size changes. The syntax for notification from the media gateway to the controller is "JI(####)", where the #### is a decimal number from 1 to 65536, indicating the new size of the jitter buffer in milliseconds.
抖动缓冲区大小更改（ji）：此事件仅包含在此处，以保持与此软件包以前版本的兼容性。此事件用于指示网关已调整抖动缓冲区的深度。请求通知的语法是“ji”，它告诉媒体网关控制器需要任何抖动缓冲区大小更改的通知。从媒体网关到控制器的通知语法为“JI（########）”，其中####是从1到65536的十进制数，以毫秒为单位指示抖动缓冲区的新大小。
Media Start (ma): The media start event occurs on a connection when the first valid RTP media packet is received on the connection. This event can be used to synchronize a local signal, e.g., ringback, with the arrival of media from the other party.
媒体启动（ma）：当连接上收到第一个有效的RTP媒体包时，连接上会发生媒体启动事件。此事件可用于将本地信号（如回铃）与另一方的媒体到达同步。
The event is detected on a connection. If no connection is specified, the event applies to all connections for the endpoint, regardless of when the connections are created (i.e., if a connection is not specified, the event will occur when the first valid RTP packet arrives on any one of the connections on that endpoint).
在连接上检测到该事件。如果未指定连接，则事件将应用于该端点的所有连接，无论何时创建连接（即，如果未指定连接，则当第一个有效RTP数据包到达该端点上的任何一个连接时，事件将发生）。
Operation complete (oc): This is the standard definition of operation complete [1].
操作完成（oc）：这是操作完成[1]的标准定义。
Operation failure (of): This is the standard definition of operation failure [1].
操作失败（of）：这是操作失败的标准定义[1]。
Packet Loss Exceeded (pl): Packet loss rate exceeds the threshold of the specified decimal number (with a range of 1 to 100,000) of packets per 100,000 packets, where the packet loss number is indicated in parenthesis. For example, PL(10) is a drop rate of 10 in 100,000 packets. This event is requested with a parameter indicating at what packet loss rate the Call Agent wishes to be reported. If the packet loss exceeds that value, the event is reported with that same parameter. The event is only reported once when the packet loss threshold is exceeded. Once reported, a following request will re-initiate packet loss measurements and report when the threshold is exceeded again.
超过数据包丢失（pl）：数据包丢失率超过每100000个数据包的指定十进制数（范围为1到100000）的阈值，其中数据包丢失数在括号中表示。例如，PL（10）是100000个分组中的10个分组的丢弃率。请求此事件时使用一个参数，该参数指示呼叫代理希望报告的丢包率。如果数据包丢失超过该值，则使用该参数报告该事件。该事件仅在超过数据包丢失阈值时报告一次。一旦报告，以下请求将重新启动数据包丢失测量，并在再次超过阈值时报告。
Quality alert (qa): The packet loss rate or the combination of delay and jitter exceeding a quality threshold. The quality thresholds for delay, jitter and packet loss rate are provisioned values.
质量警报（qa）：数据包丢失率或超过质量阈值的延迟和抖动组合。延迟、抖动和丢包率的质量阈值是规定的值。
RTP/RTCP Timeout (rto(<timeout>,st=<start-time>)): This event indicates that neither RTP nor RTCP packets have been received on this connection for a period of time equal to the <timeout> value (in seconds). The timeout value can be supplied as a decimal number from 1 to 65535 in the parameter when the request is made. The <timeout> parameter will be supplied in ObservedEvents when the event is reported - it then simply repeats the value used. If an RTP or RTCP packet is received before the timer expires, then the timer is reset and re-started. The event will only be generated if the timer expires without an RTP or RTCP packet arriving on the specified connection during the specified period of time. Note that if the event is requested without the <timeout> parameter, then a default timeout of 60 seconds is assumed. The <timeout> value will still be reported in ObservedEvents, even if no timeout value was indicated in the request (the default value will be indicated in that case). This is a one-shot event in that once the event occurs, a further request is required in order to re-initialize the timer.
RTP/RTCP超时（rto（<Timeout>，st=<start time>）：此事件表示此连接上未收到RTP或RTCP数据包的时间段等于<Timeout>值（以秒为单位）。发出请求时，可以在参数中以1到65535之间的十进制数提供超时值。报告事件时，<timeout>参数将在ObservedEvents中提供-然后它将简单地重复使用的值。如果在计时器到期之前收到RTP或RTCP数据包，则计时器将重置并重新启动。只有当计时器在指定的时间段内没有RTP或RTCP数据包到达指定连接时，才会生成该事件。请注意，如果在没有<timeout>参数的情况下请求事件，则假定默认超时为60秒。<timeout>值仍将在observeEvents中报告，即使请求中未指示超时值（在这种情况下，将指示默认值）。这是一个一次性事件，一旦事件发生，需要进一步请求以重新初始化计时器。
Another optional <start-time> parameter may also be included. This is used to indicate when the timer starts. It can have one of the following values:
还可以包括另一个可选的<start time>参数。这用于指示计时器何时启动。它可以具有以下值之一：
* "im" for immediate i.e., the timer starts as soon as the request is received. This is the default.
* “im”表示立即，即收到请求后计时器立即启动。这是默认设置。
* "ra" to indicate that the timer should start only after an RTCP packet has been received from the other end (i.e., the timer will be initiated when the first RTCP packet is received after the request is made). Note that in the case where the other end does not support RTCP, the timer will never be initiated.
* “ra”表示计时器应仅在从另一端接收到RTCP数据包后启动（即，当发出请求后接收到第一个RTCP数据包时，计时器将启动）。请注意，在另一端不支持RTCP的情况下，计时器将永远不会启动。
Note that either the <timeout> or <start-time> may be included in the request, but only the <timeout> value is included in the report.
请注意，请求中可能包含<timeout>或<start time>，但报告中仅包含<timeout>值。
An example of a request might be as follows:
请求的示例可能如下所示：
RQNT 2001 ds/ds1-3/6@gw-o.whatever.net MGCP 1.0
X: 0123456789B0
R: r/rto@364823(N)(120,st=im)
RQNT 2001 ds/ds1-3/6@gw-o.whatever.net MGCP 1.0
X: 0123456789B0
R: r/rto@364823(N)(120,st=im)
In this case, a notify will occur if there is a period of time when no RTP or RTCP packets have been received on connection 364823 for 120 seconds.
在这种情况下，如果在连接364823上有一段时间未收到RTP或RTCP数据包达120秒，则会发出通知。
The resulting NTFY with observed events would be as follows:
观察到的事件产生的NTFY如下所示：
NTFY 3002 ds/ds1-3/6@gw-o.whatever.net MGCP 1.0
X: 0123456789B0
O: r/rto@364823(120)
NTFY 3002 ds/ds1-3/6@gw-o.whatever.net MGCP 1.0
X: 0123456789B0
O: r/rto@364823(120)
Sampling Rate Changed (sr): This event is only included here to maintain compatibility with the previous version of this package. This event indicates that the packetization period changed to some decimal number in milliseconds enclosed in parenthesis, as in SR(20).
采样率更改（sr）：此事件仅包含在此处，以保持与此软件包以前版本的兼容性。此事件表示打包周期更改为括号中以毫秒为单位的十进制数，如SR（20）中所示。
Used Codec Changed (uc): This event is only included here to maintain compatibility with the previous version of this package. This event is requested without a parameter, but when reported, the hexadecimal payload type is enclosed in parenthesis, as in UC(8), to indicate the codec was changed to PCM A-law. Codec Numbers are specified in RFC 3551 [26], or in a new definition of the audio profiles for RTP that replaces this RFC.
Used Codec Changed（uc）：此事件仅包含在此处，以保持与此软件包以前版本的兼容性。请求此事件时没有参数，但在报告时，十六进制有效负载类型被括在括号中，如UC（8）中所示，以指示编解码器已更改为PCM a-law。编解码器编号在RFC 3551[26]中指定，或在替代此RFC的RTP音频配置文件的新定义中指定。
Package Name: RES Version: 0
包名称：RES版本：0
The "RES" package provides local connection option support for resource reservations as well as an event to indicate reservation loss.
“RES”包为资源保留提供本地连接选项支持，并提供一个指示保留丢失的事件。
A number of LocalConnectionOption parameters are used in doing resource reservations: "reservation request", "reservation direction", "reservation confirmation" and "resource sharing".
许多LocalConnectionOption参数用于进行资源预留：“预留请求”、“预留方向”、“预留确认”和“资源共享”。
Reservation Request LocalConnectionOption: The gateways can be instructed to perform a reservation on a given connection using RSVP. When a reservation is needed, the Call Agent will specify the reservation profile that should be used, which is either "controlled load" or "guaranteed service". The absence of reservation can be indicated by asking for the "best effort" service, which is the default value for this parameter.
保留请求LocalConnectionOption：可以指示网关使用RSVP对给定连接执行保留。当需要预订时，呼叫代理将指定应使用的预订配置文件，即“受控负载”或“保证服务”。没有预订可以通过请求“尽力”服务来表示，这是此参数的默认值。
Whether or not RSVP will be done is dependent on whether the reservation request LocalConnectionOption parameter has been included in a connection request for this connection (with either "controlled load" or "guaranteed service" indicated). If a modify connection
是否执行RSVP取决于此连接的连接请求中是否包含保留请求LocalConnectionOption参数（指示“受控负载”或“保证服务”）。如果要修改连接
(MDCX) request requires a change in the reservation and the "reservation request" parameter is not included in the LocalConnectionOptions, but was included in the LocalConnectionOptions for a previous connection request for that connection, then the "reservation request" value defaults to its previously saved value for that connection. If a modify connection (MDCX) request explicitly contains a "reservation request", indicating a request for "best effort" for a connection that has an existing reservation, the existing reservation will be torn down.
（MDCX）请求需要更改保留，并且“保留请求”参数不包含在LocalConnectionOptions中，但包含在该连接的先前连接请求的LocalConnectionOptions中，则“保留请求”值默认为该连接先前保存的值。如果修改连接（MDCX）请求显式包含“保留请求”，表示对具有现有保留的连接的“尽力”请求，则现有保留将被删除。
Reservation Direction LocalConnectionOption: When reservation has been requested on a connection, the gateway will examine the reservation direction LocalConnectionOption parameter to determine the direction that the reservations require and do the following:
保留方向LocalConnectionOption：当对连接请求保留时，网关将检查保留方向LocalConnectionOption参数以确定保留所需的方向，并执行以下操作：
* Start emitting RSVP "PATH" messages if the reservation direction LocalConnectionOptions parameter specified "send-only" or "send-receive".
* 如果保留方向LocalConnectionOptions参数指定了“仅发送”或“发送-接收”，则开始发出RSVP“PATH”消息。
* Start emitting RSVP "RESV" messages as soon as it receives "PATH" messages if the reservation direction parameter specified "receive-only" or "send-receive".
* 如果保留方向参数指定为“仅接收”或“发送-接收”，则在收到“路径”消息后立即开始发出RSVP“RESV”消息。
If an RSVP reservation is requested, but the reservation direction LocalConnectionOption parameter is missing, the reservation direction defaults to the previously saved value of the reservation direction parameter for that connection. If there was no previous reservation direction parameter for that connection, the value is deduced from the connection mode. That is:
如果请求RSVP保留，但保留方向LocalConnectionOption参数丢失，则保留方向默认为该连接的保留方向参数先前保存的值。如果该连接之前没有预留方向参数，则该值将从连接模式中推导得出。即:
* Start emitting RSVP "PATH" messages if the connection is in "send-only", "send-receive", "conference", "network loop back" or "network continuity test" mode (if a remote connection descriptor has been received).
* 如果连接处于“仅发送”、“发送-接收”、“会议”、“网络回环”或“网络连续性测试”模式（如果已接收到远程连接描述符），则开始发出RSVP“路径”消息。
* Start emitting RSVP "RESV" messages as soon as it receives "PATH" messages if the connection is in "receive-only", "send-receive", "conference", "network loop back" or "network continuity test" mode.
* 如果连接处于“仅接收”、“发送-接收”、“会议”、“网络环回”或“网络连续性测试”模式，则在收到“路径”消息后立即开始发送RSVP“RESV”消息。
Reservation Confirmation LocalConnectionOption: Another LocalConnectionOption parameter for RSVP reservations is the reservation confirmation parameter, which determines what the resource reservation pre-condition (see [1]) is for acknowledging a successful connection request:
保留确认LocalConnectionOption:RSVP保留的另一个LocalConnectionOption参数是保留确认参数，它确定确认成功连接请求的资源保留先决条件（请参见[1]）：
* If the reservation confirmation parameter is set to "none", the gateway will "Ack" the connection request without waiting for reservation completion. This is the default behavior.
* 如果保留确认参数设置为“无”，网关将在不等待保留完成的情况下“确认”连接请求。这是默认行为。
* If the "reservation confirmation" parameter is set to "send-only", the gateway will "Ack" when the PATH message has been sent and the corresponding RESV is received to indicate successful reservation in the send direction.
* 如果“预订确认”参数设置为“仅发送”，则网关将在发送路径消息并接收到相应的RESV时“确认”，以指示发送方向上的预订成功。
* If the "reservation confirmation" parameter is set to "receive-only", the gateway will "Ack" when reservation confirm for a reservation has been received.
* 如果“预订确认”参数设置为“仅接收”，则当收到预订的预订确认时，网关将“确认”。
* If the reservation confirmation parameter is set to "send-receive", the gateway will "Ack" only after the PATH message has been sent and the corresponding RESV has been received for send direction, and reservation confirm has been received for the receive direction.
* 如果保留确认参数设置为“发送-接收”，则网关只有在发送路径消息并且接收到发送方向的相应RESV，并且接收到接收方向的保留确认后才会“确认”。
Note that:
请注意：
Values "receive-only" and "send-receive" are triggers for the gateway to request reservation confirm (RESVCONF) when it sends out the RESV.
值“仅接收”和“发送-接收”是网关发出RESV时请求保留确认（RESVCONF）的触发器。
Pre-conditions SHOULD only be added for the direction(s) for which resource reservations have been requested. If a direction is added as a pre-condition, and that direction was not requested in the resource reservation, the direction MUST simply be ignored as a pre-condition.
仅应为已请求资源预留的方向添加前提条件。如果添加了一个方向作为前提条件，而资源保留中未请求该方向，则必须将该方向作为前提条件忽略。
In this approach, resource reservation success is the pre-condition to final acknowledgement of the connection request. If the reservation fails, the connection request also fails (error code 404 - insufficient bandwidth) - as will any other part of the transaction, e.g., a notification request included as part of the connection request. A typical example of this would be a request to ring the phone and look for off-hook, included with the connection request. If the reservation fails, the phone will not ring. Similarly, if the phone is already off-hook, the command fails and there will be no resource reservation.
在这种方法中，资源预留成功是连接请求最终确认的先决条件。如果保留失败，连接请求也会失败（错误代码404-带宽不足）-事务的任何其他部分也会失败，例如，作为连接请求的一部分包含的通知请求。这方面的一个典型示例是，请求拨打电话并查找连接请求中包含的摘机。如果预订失败，电话将不会响。类似地，如果手机已经挂机，则该命令将失败，并且不会保留任何资源。
A provisional response SHOULD be provided if confirmation is expected to occur outside the normal retry timers and in fact a provisional response MUST be provided if the reservation confirmation parameter has value "send-receive" (without a provisional response, SDP information cannot be returned until the
如果预计在正常重试计时器之外进行确认，则应提供临时响应；事实上，如果保留确认参数的值为“send receive”，则必须提供临时响应（如果没有临时响应，则在
final "Ack" which will not occur until the reservation is complete. This can result in a deadlock since the SDP information typically needs to be passed to the other end in order for it to initiate the RSVP PATH message in the other direction). The SDP information and connectionID MUST be included in both the provisional response and the final response. Note that in order to ensure rapid detection of a lost final response, final responses issued after provisional responses for a transaction SHALL be acknowledged, i.e., they SHALL include an empty "ResponseAck" parameter in the final response (see [1]).
在预订完成之前不会出现的最终“确认”。这可能会导致死锁，因为SDP信息通常需要传递给另一端，以便在另一个方向上启动RSVP PATH消息）。SDP信息和连接ID必须包含在临时响应和最终响应中。请注意，为了确保快速检测丢失的最终响应，应确认在交易临时响应之后发布的最终响应，即在最终响应中应包含一个空的“ResponseAck”参数（见[1]）。
If the transaction time is outside the expected bounds (time T-HIST - see the section on provisional responses in [1]), error code 406 (transaction timeout) SHOULD be returned.
如果事务时间超出预期界限（时间T-HIST-参见[1]中关于临时响应的部分），则应返回错误代码406（事务超时）。
Also note that if the reservation confirmation parameter is omitted, the value of the reservation confirmation parameter defaults to its previously saved value. If there is no previously saved value for the reservation confirmation parameter, or the reservation confirmation parameter has the value "none", then successful resource reservation is not a pre-condition to providing an acknowledgement to the connection request (i.e., the gateway can "Ack" right away without waiting for the reservation to complete and a provisional response will not be necessary).
还要注意，如果省略了保留确认参数，则保留确认参数的值默认为其先前保存的值。如果预约确认参数之前没有保存值，或者预约确认参数的值为“无”，则成功的资源预约不是向连接请求提供确认的先决条件（即网关可以“确认”）立即，无需等待预订完成，无需临时回复）。
Resource Sharing LocalConnectionOption: It may be possible to share network resources across multiple connections. An example is a call-waiting scenario, where only one connection will ever be active at a time. In a 3-way calling scenario with a similar set of connections, sharing is not possible. Only the Call Agent knows what may be possible, depending on the feature that is being invoked.
资源共享LocalConnectionOption：可以跨多个连接共享网络资源。一个例子是呼叫等待场景，其中一次只有一个连接处于活动状态。在具有类似连接集的3路呼叫场景中，无法共享。根据所调用的功能，只有呼叫代理知道可能的情况。
In order to allow the Call Agent to indicate that sharing is possible, a resource sharing LocalConnectionOption parameter is introduced. This parameter can have one of the following values:
为了允许调用代理指示共享是可能的，引入了资源共享LocalConnectionOption参数。此参数可以具有以下值之一：
* A value "$" can be specified where $ refers to "this connection". This value is used when doing a create connection and indicates the intent to share resources with this connection.
* 可以指定值“$”，其中$表示“此连接”。此值在创建连接时使用，并指示与此连接共享资源的意图。
* A connection ID can be specified which indicates that this is a request to share resources with the connection having this connection ID (allowing multiple connections to share resources with the connection indicated).
* 可以指定一个连接ID，该ID指示这是一个与具有此连接ID的连接共享资源的请求（允许多个连接与所指示的连接共享资源）。
* The value can be empty, which indicates a request to no longer share the resources of this connection with other connections.
* 该值可以为空，这表示请求不再与其他连接共享此连接的资源。
In the case of a CRCX, the default value for the resource sharing local connection option is empty, and for an MDCX, the default value is its current value.
对于CRCX，资源共享本地连接选项的默认值为空，对于MDCX，默认值为其当前值。
The RSVP filters will be deduced from the characteristics of the connection. The RSVP resource profiles will be deduced from the connection's bandwidth and packetization period.
RSVP滤波器将根据连接的特性进行推导。RSVP资源配置文件将从连接的带宽和打包周期中推导出来。
Note that if RSVP is used with PacketCable Dynamic Quality of Service [35], then the parameters in NCS [36] would be used instead of the reservation direction, confirmation and reservation sharing parameters described here.
请注意，如果RSVP与PacketCable动态服务质量[35]一起使用，则将使用NCS[36]中的参数，而不是此处描述的保留方向、确认和保留共享参数。
The Local Connection Options for the "RES" package consist of the following:
“RES”包的本地连接选项包括以下内容：
* The resource reservation parameter, encoded as the keyword "r", followed by a colon and the value "g" (guaranteed service), "cl" (controlled load) or "be" (best effort).
* 资源保留参数，编码为关键字“r”，后跟冒号和值“g”（保证服务）、“cl”（控制负载）或“be”（尽力）。
* The reservation direction parameter, encoded as the keyword "r-dir" followed by a colon and the value "sendonly", "recvonly" or "sendrecv".
* 保留方向参数，编码为关键字“r-dir”，后跟冒号和值“sendonly”、“recvoOnly”或“sendrecv”。
* The reservation confirmation parameter, encoded as the keyword "r-cnf" followed by a colon and the value "none", "sendonly", "recvonly" or "sendrecv".
* 保留确认参数，编码为关键字“r-cnf”，后跟冒号和值“none”、“sendonly”、“RecvoOnly”或“sendrecv”。
* The resource sharing parameter, encoded as the keyword "r-sh" followed by a colon and either:
* 资源共享参数，编码为关键字“r-sh”，后跟冒号，并且：
* The wild-card character "$" indicating this connection, indicating future plans to share resources with this connection, or
* 通配符“$”表示此连接，表示将来计划与此连接共享资源，或
* A connection ID, indicating a request to share resources with the connection having the specified connection ID (and all other connections sharing resources with that connection), or
* 连接ID，指示与具有指定连接ID的连接（以及与该连接共享资源的所有其他连接）共享资源的请求，或
* An empty value (i.e., "r-sh:" with no value indicated), indicating a request to no longer share the resources of this connection with other connections
* 一个空值（即“r-sh:，未显示任何值），表示请求不再与其他连接共享此连接的资源
Note that normally local connection options that are associated with a package have the package prefix included as per the package extension rules in [1]. The local connection options in the "RES" package are exceptions. The package prefix is not included in the case of the "RES" package because it was created before the extension rules in [1] were defined.
请注意，通常情况下，与包关联的本地连接选项会根据[1]中的包扩展规则包含包前缀。“RES”包中的本地连接选项是例外。对于“RES”包，不包括包前缀，因为它是在定义[1]中的扩展规则之前创建的。
The following events are included as part of the resource reservation package:
以下事件包括在资源保留包中：
------------------------------------------------------
| Symbol | Definition | R | S Duration |
|------------------------------------------------------|
| re | Resource Error | C | |
| rl | Resource Lost | C | |
------------------------------------------------------
------------------------------------------------------
| Symbol | Definition | R | S Duration |
|------------------------------------------------------|
| re | Resource Error | C | |
| rl | Resource Lost | C | |
------------------------------------------------------
Resource Error (re): This is an indication that an error in the resource reservation occurred during the life of the connection. This event is not requested with a parameter, but is reported with a parameter (see possible values below). This event may or may not indicate the permanent loss of the reservation (i.e., any error associated with the reservation whether permanent or temporary will be reported). If requested on an endpoint (without specifying the connection ID), the request refers to all present and future connections on that endpoint. When reported, the connectionID is always supplied along with a reason for the error indicated as a parameter. One of the following possible reasons for loss MUST be included as the parameter when the event is reported:
资源错误（re）：这表示在连接的生命周期内发生了资源保留中的错误。此事件不是通过参数请求的，而是通过参数报告的（请参见下面的可能值）。该事件可能表示也可能不表示保留永久性丢失（即，将报告与保留相关的任何错误，无论是永久性的还是临时性的）。如果在端点上请求（不指定连接ID），该请求将引用该端点上所有当前和未来的连接。报告时，connectionID始终随参数一起提供错误原因。报告事件时，必须将以下可能的损失原因之一作为参数：
- "resverr" is used to indicate that a ResvErr message was received.
- “resverr”用于指示已收到resverr消息。
- "patherr" is used to indicate that a PathErr message was received.
- “patherr”用于指示已收到patherr消息。
- "other"
- “其他”
In addition to a parameter indicating one of the reasons above, additional information on the type of error MAY be included as a second parameter in the form of a quoted string.
除了指示上述原因之一的参数外，还可以将有关错误类型的附加信息作为第二个参数以带引号的字符串形式包括在内。
Example report might include:
示例报告可能包括：
O: res/rl@0A3F58(resverr)
O: res/rl@0A3F58(resverr)
or
或
O: res/rl@0A3F58(resverr, "some additional commentary")
O: res/rl@0A3F58(resverr, "some additional commentary")
Note that this event will not be reported if an error occurs while a resource reservation is initially being set up (i.e., the event was only reported as a result of an error that occurred after the reservation was set up).
请注意，如果在最初设置资源保留时发生错误，则不会报告此事件（即，仅当设置保留后发生错误时才会报告此事件）。
Resource Lost (rl): Loss of reservation during the life of a connection can be reported by using the "rl" event. This event is not requested with a parameter, but is reported with a parameter (see below for possible values). If requested on an endpoint (without specifying the connection ID), the request refers to all present and future connections on that endpoint.
资源丢失（rl）：可以使用“rl”事件报告连接生命周期内的保留丢失。此事件不是通过参数请求的，而是通过参数报告的（有关可能的值，请参阅下文）。如果在端点上请求（不指定连接ID），该请求将引用该端点上所有当前和未来的连接。
When reported, the connectionID is always supplied along with a reason for the loss indicated as a parameter. One of the following possible reasons for loss MUST be supplied as the parameter when the event is reported:
报告时，始终提供connectionID以及作为参数指示的丢失原因。报告事件时，必须提供以下可能的损失原因之一作为参数：
- "resvtear" indicating that the reservation loss was indicated by ResvTear message.
- “resvtear”表示resvtear消息指示保留丢失。
- "pathtear" indicating that the reservation loss was indicated by PathTear message.
- “pathtear”指示保留丢失由pathtear消息指示。
- "other"
- “其他”
In addition to a parameter indicating one of the reasons above, additional information on the type of error MAY be included as a second parameter in the form of a quoted string.
除了指示上述原因之一的参数外，还可以将有关错误类型的附加信息作为第二个参数以带引号的字符串形式包括在内。
Example report might include:
示例报告可能包括：
O: res/rl@0A3F58(ResvTear)
O: res/rl@0A3F58(ResvTear)
or
或
O: res/rl@0A3F58(ResvTear, "some other commentary")
O: res/rl@0A3F58(ResvTear, "some other commentary")
Note that this event will not be reported if an error occurs while a resource reservation is initially being set up (i.e., the event is only reported if the reservation was lost after it was initially set up).
请注意，如果初始设置资源保留时发生错误，则不会报告此事件（即，仅当初始设置后保留丢失时才会报告此事件）。
Package Name: A Version: 1
包名称：A版本：1
---------------------------------------------------------------
| Symbol | Definition | R | S Duration |
|---------------------------------------------------------------|
| ann(url) | Play an Announcement | | TO, C variable |
| oc | Operation Complete | x | |
| of | Operation Failure | x | |
---------------------------------------------------------------
---------------------------------------------------------------
| Symbol | Definition | R | S Duration |
|---------------------------------------------------------------|
| ann(url) | Play an Announcement | | TO, C variable |
| oc | Operation Complete | x | |
| of | Operation Failure | x | |
---------------------------------------------------------------
Changes from the previous version: change to conform to standard reporting of operation failure and operation complete events.
与上一版本的更改：更改为符合操作失败和操作完成事件的标准报告。
The announcement signal is qualified by a URL name:
公告信号由URL名称限定：
S: ann(http://scripts.example.net/all-lines-busy.au)
S: ann(http://scripts.example.net/all-lines-busy.au)
The URL name MAY be followed by a list of initial parameters, separated by commas. However, standard parameters are not included as part of this package definition (Note: use of additional parameters is optional and would result in a proprietary interface).
URL名称后面可以跟一个初始参数列表，用逗号分隔。但是，标准参数不包括在此包定义中（注：使用附加参数是可选的，会导致专有接口）。
The gateway SHOULD support one or more standard URL schemes such as:
网关应支持一个或多个标准URL方案，例如：
* file, http, ftp (RFC 1738 [28]), which indicate where the audio file is located (where to load the file from before playing the audio file on the gateway).
* 文件，http，ftp（RFC 1738[28]），指示音频文件的位置（在网关上播放音频文件之前从何处加载文件）。
* RTSP URL (section 3.2 of RFC 2326 [29]), which in this case allows the media gateway to directly initiate playing of the announcement via an RTSP server.
* RTSP URL（RFC 2326[29]第3.2节），在这种情况下，允许媒体网关通过RTSP服务器直接启动公告播放。
The pre-condition for a successful response (return code of "200") is correct syntax and capability (support is available for this request). Standard MGCP return codes apply in the case of failure. Further indications of failure are provided in the operation failure event as a comment after the name of the failed event in the form of a quoted string.
成功响应（返回代码“200”）的先决条件是语法和功能正确（支持此请求）。标准MGCP返回代码适用于故障情况。操作失败事件中提供了更多的失败指示，作为失败事件名称后的注释，以带引号的字符串形式提供。
If the announcement cannot be played out for a reason determined after a successful response to the request has been provided, an operation failure event will be returned. The failure MAY be explained by some commentary (in the form of a quoted string), as in:
如果在成功响应请求后，由于确定的原因无法播放公告，将返回操作失败事件。失败可以通过一些注释（以引用字符串的形式）来解释，如：
O: a/of(a/ann,"file not found")
O: a/of(a/ann,"file not found")
The "operation complete" event will be detected when the announcement is played out.
播放公告时将检测到“操作完成”事件。
O: a/oc(a/ann)
O: a/oc(a/ann)
Package Name: Script Version: 1
包名称：脚本版本：1
-----------------------------------------------------------------
| Symbol | Definition | R | S | Duration |
|-----------------------------------------------------------------|
| ir(..) | Intermediate Results/Req.| x | BR | |
| java(url,...) | Load & Run java script | | TO | variable |
| oc | operation complete | x | | |
| of | operation failure | x | | |
| perl(url,...) | Load & Run perl script | | TO | variable |
| tcl(url,...) | Load & Run TCL script | | TO | variable |
| vxml(url,...) | Load & Run VXML doc. | | TO | variable |
| xml(url,...) | Load & Run XML script | | TO | variable |
-----------------------------------------------------------------
-----------------------------------------------------------------
| Symbol | Definition | R | S | Duration |
|-----------------------------------------------------------------|
| ir(..) | Intermediate Results/Req.| x | BR | |
| java(url,...) | Load & Run java script | | TO | variable |
| oc | operation complete | x | | |
| of | operation failure | x | | |
| perl(url,...) | Load & Run perl script | | TO | variable |
| tcl(url,...) | Load & Run TCL script | | TO | variable |
| vxml(url,...) | Load & Run VXML doc. | | TO | variable |
| xml(url,...) | Load & Run XML script | | TO | variable |
-----------------------------------------------------------------
Changes from the previous version of the package: "vxml" was added as a language type for loading and running VXML documents; change to conform with standard reporting of operation failure and operation complete events; addition of "ir" event.
与以前版本的包相比，增加了“vxml”作为加载和运行vxml文档的语言类型；更改以符合操作失败和操作完成事件的标准报告；增加“ir”事件。
The current definition defines keywords for the most common languages. More languages may be defined in later versions of this package.
当前定义定义了最常用语言的关键字。此软件包的更高版本中可能会定义更多语言。
The "signal" specifying the scripting language is parameterized with a URL indicating the location of the script. The URL parameter MAY be optionally followed by a comma-separated list of arguments as initial parameters to use in running the script. URL schemes may include file ftp, or http schemes with syntax according to RFC 2396 [30]. As an example:
指定脚本语言的“信号”由指示脚本位置的URL参数化。URL参数后面可以有一个逗号分隔的参数列表，作为运行脚本时使用的初始参数。URL方案可能包括文件ftp或http方案，其语法符合RFC 2396[30]。例如：
S: script/vxml(ftp://ftp.example.net/credit-card.vxml,arg1,arg2,
...,argn)
S: script/vxml(ftp://ftp.example.net/credit-card.vxml,arg1,arg2,
...,argn)
The argument list "arg1,arg2,...,argn" is passed to the script/document as a list of initial parameters.
参数列表“arg1，arg2，…，argn”作为初始参数列表传递给脚本/文档。
The pre-condition for a successful response (return code of "200") is correct syntax and capability (support is available for this request). Standard MGCP return codes apply in the case of failure. Some further (non-application/script specific) failure indications MAY be provided in the operation failure event as a comment in the form of a quoted string following the name of the failed event.
成功响应（返回代码“200”）的先决条件是语法和功能正确（支持此请求）。标准MGCP返回代码适用于故障情况。操作失败事件中可能会提供一些其他（非应用程序/脚本特定的）失败指示，作为失败事件名称后带引号字符串形式的注释。
Example
实例
O: script/of(script/vxml,"file not found")
O: script/of(script/vxml,"file not found")
The script produces an output, which consists of one or several text strings, separated by commas. This provides the return-status of the script as well as return parameters (if there are any)
该脚本生成一个输出，该输出由一个或多个文本字符串组成，用逗号分隔。这将提供脚本的返回状态以及返回参数（如果有）
O: script/oc(script/vxml,return-status=<status>, name1=value1,name2=value2,...)
O:script/oc（script/vxml，返回状态=<status>，name1=value1，name2=value2，…）
where <status> can have one of the values "success" or "failure". This is then followed by output parameters as a comma-separated list of name-value pairs.
其中<status>可以有一个值“success”或“failure”。然后，输出参数以逗号分隔的名称-值对列表的形式出现。
Intermediate Result/Request (ir(<params>)): This provides a way for:
中间结果/请求（ir（<params>）：这提供了一种方法：
* The script to inform the Call Agent of intermediate results (e.g., a case where it is important because of timing concerns to inform the Call Agent prior to operation complete).
* 通知呼叫代理中间结果的脚本（例如，由于时间问题，在操作完成之前通知呼叫代理非常重要）。
* The script to request some information from the Call Agent.
* 从呼叫代理请求某些信息的脚本。
* The Call Agent to inform the script of some event or information that may be important for the operation of the script (in this case "ir" is used as a signal).
* 呼叫代理通知脚本一些事件或信息，这些事件或信息可能对脚本的操作很重要（在这种情况下，“ir”用作信号）。
Parameters (i.e., <params>) SHOULD be a comma-separated list of name-value pairs e.g., ir(name1=value1,name2=value2,..). The Call Agent MAY include event parameters when it requests this event, in which case, the MGCP syntax requirements require that the action be specified (e.g., "R: ir(N)(nam1=value1,name2=value2,..)").
参数（即，<params>）应该是以逗号分隔的名称-值对列表，例如ir（name1=value1，name2=value2，…）。调用代理在请求此事件时可能包括事件参数，在这种情况下，MGCP语法要求要求指定操作（例如，“R:ir（N）（nam1=value1，name2=value2，…））。
If the Call Agent requests "ir" as a signal, at least one parameter MUST be provided.
如果呼叫代理请求“ir”作为信号，则必须至少提供一个参数。
When requesting the "ir" signal, the Call Agent MUST also repeat the original script signal. This is in order to be consistent with the semantics of TO signals in MGCP (i.e., if the original "script" signal is not included, then the signal/script will be stopped). The only problem with this is that there is a possible race condition in which a request to send an "ir" signal could occur just as the script stopped. In order to avoid this confusion, the following is RECOMMENDED: when the script signal is included with an "ir" signal, include a parameter (of the script signal) to indicate that this is not a new instance of the script i.e., if there is no script executing at the present time do not start executing a new one.
请求“ir”信号时，呼叫代理还必须重复原始脚本信号。这是为了与MGCP中to信号的语义一致（即，如果未包括原始“脚本”信号，则信号/脚本将停止）。唯一的问题是存在一种可能的竞争条件，在这种情况下，发送“ir”信号的请求可能会在脚本停止时发生。为了避免这种混淆，建议如下：当脚本信号包括在“ir”信号中时，包括（脚本信号的）参数，以指示这不是脚本的新实例，即，如果当前没有执行脚本，则不要开始执行新实例。
The "ir" signal is only associated with an executing script. If none are running when a request for the event/signal is made, or if a new script request is not included with the request, then the "ir" signal/event will not be executed (i.e., the "ir" event with its parameters is passed to an existing script for parsing and execution and is considered opaque as far as MGCP as concerned. If no such script exists, response code "800" will be returned, indicating that the script is not executing).
“ir”信号仅与正在执行的脚本相关联。如果在发出事件/信号请求时没有运行任何脚本，或者如果请求中没有包含新的脚本请求，则不会执行“ir”信号/事件（即“ir”）事件及其参数被传递给现有脚本进行解析和执行，就MGCP而言，该事件被视为不透明的。如果不存在此类脚本，则将返回响应代码“800”，指示脚本未执行）。
The following response code is associated with this package:
以下响应代码与此包关联：
Code Text Explanation
代码文本解释
800 Script not Request for "ir" signal or event Executing but no script is executing at the time the request was received.
800脚本未请求执行“ir”信号或事件，但在收到请求时未执行脚本。
Note that package specific error codes include the package name following the error code. For example, if error code 800 occurs in response to a request with a transaction ID of 1001, it would be sent as:
请注意，特定于包的错误代码包括错误代码后面的包名称。例如，如果在响应事务ID为1001的请求时出现错误代码800，则它将被发送为：
800 1001 /SCRIPT
800 1001/脚本
The following packages and their versions have been registered with IANA as per the instructions in [1].
以下软件包及其版本已按照[1]中的说明向IANA注册。
Package Title Name Version
------------- ---- -------
Announcement A 1
DTMF D 1
Digit Map Extension DM1 0
Media Format FM 0
Generic G 1
Handset H 1
Line L 1
RTP R 1
Resource Reservation RES 0
Script SCRIPT 1
Supplementary Tones SST 0
Signal List SL 0
Trunk T 1
Package Title Name Version
------------- ---- -------
Announcement A 1
DTMF D 1
Digit Map Extension DM1 0
Media Format FM 0
Generic G 1
Handset H 1
Line L 1
RTP R 1
Resource Reservation RES 0
Script SCRIPT 1
Supplementary Tones SST 0
Signal List SL 0
Trunk T 1
The following extension digit map letter has been registered with IANA:
以下分机数字地图字母已在IANA注册：
Package Letter
------- ------
DM1 P
Package Letter
------- ------
DM1 P
The following Local Connections have been registered with IANA:
以下本地连接已向IANA注册：
Field Name
------- -----
Media Format fmtp
Reservation Confirmation r-cnf
Reservation Direction r-dir
Resource Sharing r-sh
Field Name
------- -----
Media Format fmtp
Reservation Confirmation r-cnf
Reservation Direction r-dir
Resource Sharing r-sh
The MGCP packages contained in this document do not require any further security considerations beyond those indicated in the base MGCP specification [1].
除了基本MGCP规范[1]中指出的安全注意事项外，本文件中包含的MGCP包不需要任何其他安全注意事项。
Special thanks are due to the authors of the original MGCP 1.0 specification: Mauricio Arango, Andrew Dugan, Isaac Elliott, Christian Huitema, and Scott Picket.
特别感谢原始MGCP 1.0规范的作者：Mauricio Arango、Andrew Dugan、Isaac Elliott、Christian Huitema和Scott Picket。
Thanks also to the reviewers of this document, including but not limited to: Jerry Kamitses, Sonus Networks; Dave Auerbach, Dan Wing, Cisco Systems; Ed Guy, EMC Software; Martin Wakley, Nortel Networks.
还要感谢本文件的审阅者，包括但不限于：Jerry Kamitses，Sonus Networks；Dave Auerbach，Dan Wing，思科系统公司；EMC软件公司的Ed Guy；Martin Wakley，北电网络公司。
[1] Andreasen, F. and B. Foster, "Media Gateway Control Protocol (MGCP) Version 1.0", RFC 3435, January 2003.
[1] Andreasen，F.和B.Foster，“媒体网关控制协议（MGCP）1.0版”，RFC 3435，2003年1月。
[2] Bellcore, "LSSGR: Switching System Generic Requirements for Call Control Using the Integrated Services Digital Network User Part (ISDNUP)", GR-317-CORE, Issue 2, December 1997.
[2] Bellcore，“LSSGR：使用综合业务数字网络用户部分（ISDNUP）的呼叫控制的交换系统通用要求”，GR-317-CORE，第2期，1997年12月。
[3] ITU-T, "Telephone User Part Signaling Procedures", ITU-T Q.724, November 1988.
[3] ITU-T，“电话用户部分信令程序”，ITU-T Q.724，1988年11月。
[4] ANSI, "OAM&P - Terminating Test Line Access and Capabilities", T1.207-2000.
[4] ANSI，“OAM&P-端接测试线接入和能力”，T1.207-2000。
[5] Bellcore, "Notes on the Network", Special Report SR-2275, Issue 3, December 1997.
[5] Bellcore，“网络注释”，特别报告SR-2275，第3期，1997年12月。
[6] Bellcore, "Call Processing" GR-505-CORE, Issue 1, December 1997.
[6] Bellcore，“呼叫处理”GR-505-CORE，第1期，1997年12月。
[7] Bellcore, "LSSGR: Signaling for Analog Interfaces", GR-506-CORE, Issue 1, June 1996.
[7] Bellcore，“LSSGR：模拟接口的信令”，GR-506-CORE，第1期，1996年6月。
[8] ITU-T, "Technical Characteristics of Tones for the Telephone Service", ITU-T E.180, March 1998.
[8] ITU-T，“电话业务音调的技术特征”，ITU-T E.180，1998年3月。
[9] ITU-T, "Various Tones Used in National Networks", ITU-T E.180, Supplement 2, January 1994.
[9] ITU-T，“国家网络中使用的各种音调”，ITU-T E.180，补编2，1994年1月。
[10] ITU-T, "Applications of Tones and Recorded Announcements in Telephone Services", ITU-T E.182, March 1998.
[10] ITU-T，“电话业务中音调和录音公告的应用”，ITU-T E.182，1998年3月。
[11] Bellcore, "Call Forwarding Sub-Features FSD-01-02-1450, GR-586, Issue 1, June 2000.
[11] Bellcore，“呼叫转接子功能FSD-01-02-1450，GR-586，第1期，2000年6月。
[12] Bellcore, "CPE Compatibility Considerations for the Voiceband Data Transmission Interface", SR-TSV-002476, December 1992.
[12] Bellcore，“语音带数据传输接口的CPE兼容性考虑”，SR-TSV-002476，1992年12月。
[13] Bellcore, "LSSGR: Visual Message Waiting Indicator Generic Requirements (FSD 01-02-2000)", GR-1401, Issue 01, June 2000.
[13] Bellcore，“LSSGR：可视信息等待指示器通用要求（FSD 01-02-2000）”，GR-1401，第01期，2000年6月。
[14] Bellcore, "LSSGR Voiceband Data Transmission Interface", Section 6.6, GR-30-CORE, Issue 02, December 1998.
[14] Bellcore，“LSSGR语音带数据传输接口”，第6.6节，GR-30-CORE，第02期，1998年12月。
[15] Handley, M. and V. Jacobson, "SDP: Session Description Protocol", RFC 2327, April 1998.
[15] Handley，M.和V.Jacobson，“SDP：会话描述协议”，RFC 2327，1998年4月。
[16] Bellcore, "LSSGR: Call Waiting, FSD 01-02-1201", GR-571, Issue 01, June 2000.
[16] Bellcore，“LSSGR:呼叫等待，FSD 01-02-1201”，GR-571，第01期，2000年6月。
[17] Bellcore, "LSSGR: Verification Connections FSD 25-05-0903", GR-531-CORE, Issue 1, June 2000.
[17] Bellcore，“LSSGR：验证连接FSD 25-05-0903”，GR-531-CORE，第1期，2000年6月。
[18] Bellcore, " LSSGR: CLASS Feature: Calling Identity Delivery on Call Waiting, FSD 01-02-1090, GR-575, Issue 01, June 2000.
[18] Bellcore，“LSSGR：类别特征：呼叫等待时呼叫身份传递”，FSD 01-02-1090，GR-575，2000年6月第01期。
[19] Postel, J., "Internet Control Message Protocol", STD 5, RFC 792, September 1981.
[19] Postel，J.，“互联网控制消息协议”，STD 5，RFC 792，1981年9月。
[20] Bellcore, "Class Feature: Screen Editing (FSD 30-28-0000)", GR-220, Issue 2, April 2002.
[20] Bellcore，“类别特征：屏幕编辑（FSD 30-28-0000）”，GR-220，第2期，2002年4月。
[21] ITU-T, "Procedure for document facsimile transmission in the general switched telephone network", ITU-T T.30, April 1999.
[21] ITU-T，“通用交换电话网中文件传真传输程序”，ITU-T.30，1999年4月。
[22] ITU-T, "300 bits per second duplex modem standardized for use in the general switched telephone network", ITU-T V.21, November 1988.
[22] ITU-T, "300 bits per second duplex modem standardized for use in the general switched telephone network", ITU-T V.21, November 1988.translate error, please retry
[23] Telcordia Technologies, "Telcordia Technologies Specification of Signaling System Number 7", GR-246-CORE, Issue 7, December 2002.
[23] Telcordia Technologies，“Telcordia Technologies第7号信令系统规范”，GR-246-CORE，第7期，2002年12月。
[24] Telcordia Technologies, "LSSGR: CLASS Feature: Calling Name Delivery Generic Requirements (FSD 01-02-1070)", GR-1188, Issue 02, December 2000.
[24] Telcordia Technologies，“LSSGR：类别特征：呼叫名称交付通用要求（FSD 01-02-1070）”，GR-1188，第02期，2000年12月。
[25] Telcordia Technologies, "LSSGR: CLASS Feature: Calling Number Delivery (FSD 01-02-1051)", GR-31, Issue 01, June 2000.
[25] Telcordia Technologies，“LSSGR：类别特征：呼叫号码传送（FSD 01-02-1051）”，GR-31，第01期，2000年6月。
[26] Schulzrinne, H. and S. Casner, "RTP Profile for Audio and Video Conferences with Minimal Control", RFC 3551, July 2003.
[26] Schulzrinne，H.和S.Casner，“具有最小控制的音频和视频会议的RTP配置文件”，RFC 3551，2003年7月。
[27] Braden, R., Ed., Zhang, L., Berson, S., Herzog, S. and S. Jamin, "Resource ReSerVation Protocol (RSVP) -- Version 1 Functional Specification", RFC 2205, September 1997.
[27] Braden，R.，Ed.，Zhang，L.，Berson，S.，Herzog，S.和S.Jamin，“资源预留协议（RSVP）——第1版功能规范”，RFC 22052997年9月。
[28] Berners-Lee, T., Masinter, L. and M. McCahill, Eds., "Uniform Resource Locators (URL)", RFC 1738, December 1994.
[28] Berners Lee，T.，Masinter，L.和M.McCahill编辑，“统一资源定位器（URL）”，RFC 17381994年12月。
[29] Schulzrinne, H., Rao, A. and R. Lanphier, "Real Time Streaming Protocol (RTSP)", RFC 2326, April 1998.
[29] Schulzrinne，H.，Rao，A.和R.Lanphier，“实时流协议（RTSP）”，RFC2326，1998年4月。
[30] Berners-Lee, T., Fielding, R. and L. Masinter, "Uniform Resource Identifiers (URI): Generic Syntax", RFC 2396, August 1998.
[30] Berners Lee，T.，Fielding，R.和L.Masinter，“统一资源标识符（URI）：通用语法”，RFC 2396，1998年8月。
[31] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997.
[31] Bradner，S.，“RFC中用于表示需求水平的关键词”，BCP 14，RFC 2119，1997年3月。
[32] Perkins, C., Kouvelas, I., Hodson, O., Hardman, V., Handley, M., Bolot, J.C., Vega-Garcia, A. and S. Fosse-Parisis, "RTP Payload for Redundant Audio Data", RFC 2198, September 1997.
[32] 帕金斯，C.，库维拉斯，I.，霍德森，O.，哈德曼，V.，汉德利，M.，博洛，J.C.，维加·加西亚，A.和S.福斯·帕里斯，“冗余音频数据的RTP有效载荷”，RFC 21981997年9月。
[33] Schulzrinne, H. and S. Petrack, "RTP Payload for DTMF Digits, Telephony Tones and Telephony Signals", RFC 2833, May 2000.
[33] Schulzrinne，H.和S.Petrack，“DTMF数字、电话音和电话信号的RTP有效载荷”，RFC 28332000年5月。
[34] Foster, B., "MGCP CAS Packages", RFC 3064, February 2001.
[34] Foster，B.，“MGCP CAS包”，RFC 3064，2001年2月。
[35] PacketCableTM, Dynamic Quality if Service Specification,
http://www.packetcable.com/downloads/specs/PKT-SP-DQOS-I07-
030815.pdf
[35] PacketCableTM, Dynamic Quality if Service Specification,
http://www.packetcable.com/downloads/specs/PKT-SP-DQOS-I07-
030815.pdf
[36] PacketCableTM Network-Based Call Signaling Protocol
http://www.packetcable.com/downloads/specs/PKT-SP-EC-MGCP-I08-
030728.pdf
[36] PacketCableTM Network-Based Call Signaling Protocol
http://www.packetcable.com/downloads/specs/PKT-SP-EC-MGCP-I08-
030728.pdf
[37] Groves, C., Pantaleo, M., Anderson, T. and T. Taylor, Eds., "Gateway Control Protocol Version 1", RFC 3525, June 2003.
[37] Groves，C.，Pantaleo，M.，Anderson，T.和T.Taylor，编辑，“网关控制协议版本1”，RFC 35252003年6月。
[38] Arango, M., Dugan, A., Elliott, I., Huitema, C. and S. Pickett, "Media Gateway Control Protocol (MGCP) Version 1.0", RFC 2705, October 1999.
[38] Arango，M.，Dugan，A.，Elliott，I.，Huitema，C.和S.Pickett，“媒体网关控制协议（MGCP）1.0版”，RFC 27052999年10月。
Bill Foster Cisco Systems
比尔·福斯特思科系统公司
Phone: +1 250 758 9418
EMail: bfoster@cisco.com
Phone: +1 250 758 9418
EMail: bfoster@cisco.com
Flemming Andreasen Cisco Systems Edison, NJ 08837
弗莱明·安德里森思科系统公司爱迪生，新泽西州，08837
EMail: fandreas@cisco.com
EMail: fandreas@cisco.com
Copyright (C) The Internet Society (2003). All Rights Reserved.
版权所有（C）互联网协会（2003年）。版权所有。
This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this paragraph are included on all such copies and derivative works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references to the Internet Society or other Internet organizations, except as needed for the purpose of developing Internet standards in which case the procedures for copyrights defined in the Internet Standards process must be followed, or as required to translate it into languages other than English.
本文件及其译本可复制并提供给他人，对其进行评论或解释或协助其实施的衍生作品可全部或部分编制、复制、出版和分发，不受任何限制，前提是上述版权声明和本段包含在所有此类副本和衍生作品中。但是，不得以任何方式修改本文件本身，例如删除版权通知或对互联网协会或其他互联网组织的引用，除非出于制定互联网标准的需要，在这种情况下，必须遵循互联网标准过程中定义的版权程序，或根据需要将其翻译成英语以外的其他语言。
The limited permissions granted above are perpetual and will not be revoked by the Internet Society or its successors or assignees.
上述授予的有限许可是永久性的，互联网协会或其继承人或受让人不会撤销。
This document and the information contained herein is provided on an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
本文件和其中包含的信息是按“原样”提供的，互联网协会和互联网工程任务组否认所有明示或暗示的保证，包括但不限于任何保证，即使用本文中的信息不会侵犯任何权利，或对适销性或特定用途适用性的任何默示保证。
Acknowledgement
确认
Funding for the RFC Editor function is currently provided by the Internet Society.
RFC编辑功能的资金目前由互联网协会提供。