Network Working Group A. Srinath
Request for Comments: 3149 G. Levendel
Category: Informational K. Fritz
Sylantro Systems
R. Kalyanaram
Wipro Systems
September 2001
Network Working Group A. Srinath
Request for Comments: 3149 G. Levendel
Category: Informational K. Fritz
Sylantro Systems
R. Kalyanaram
Wipro Systems
September 2001
MGCP Business Phone 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 (2001). All Rights Reserved.
版权所有（C）互联网协会（2001年）。版权所有。
Abstract
摘要
This document describes a collection of MGCP (Media Gateway Control Protocol) packages that can be used to take advantage of the feature keys and displays on digital business phones and IP-Phones.
本文档介绍了一系列MGCP（媒体网关控制协议）软件包，这些软件包可用于利用数字商务电话和IP电话上的功能键和显示。
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 that the IETF Megaco working group and the ITU-T Study Group 16 have produced a standards track RFC "Megaco Protocol Version 1.0" (RFC 3015, also published as ITU recommendation H.248) which addresses the same problem space and are developing extensions to that protocol for functions of this type.
本文件发布供社区参考。它描述了目前正在许多产品中部署的非IETF协议。实施者应意识到，IETF Megaco工作组和ITU-T研究组16已经制定了标准跟踪RFC“Megaco协议版本1.0”（RFC 3015，也发布为ITU建议H.248），该跟踪解决了相同的问题空间，并正在为该类型的功能开发对该协议的扩展。
Table of Contents
目录
1. Introduction. . . . . . . . . . . . . . . . . . . . . . . . 3
1.1 General Information. . . . . . . . . . . . . . . . . . 4
1.2 Objectives . . . . . . . . . . . . . . . . . . . . . . 5
2. MGCP Packages for Business Phones . . . . . . . . . . . . . 5
2.1 Feature Key Package. . . . . . . . . . . . . . . . . . 6
2.2 Business Phone Package . . . . . . . . . . . . . . . . 9
2.3 Display XML Package. . . . . . . . . . . . . . . . . . 9
1. Introduction. . . . . . . . . . . . . . . . . . . . . . . . 3
1.1 General Information. . . . . . . . . . . . . . . . . . 4
1.2 Objectives . . . . . . . . . . . . . . . . . . . . . . 5
2. MGCP Packages for Business Phones . . . . . . . . . . . . . 5
2.1 Feature Key Package. . . . . . . . . . . . . . . . . . 6
2.2 Business Phone Package . . . . . . . . . . . . . . . . 9
2.3 Display XML Package. . . . . . . . . . . . . . . . . . 9
3. Endpoint Naming and Phone Type Determination. . . . . . . .10
4. Functions that should be Locally Implemented. . . . . . . .11
4.1 Volume Control . . . . . . . . . . . . . . . . . . . .11
4.2 Audio Path . . . . . . . . . . . . . . . . . . . . . .11
4.3 Microphone mute button and light . . . . . . . . . . .11
5. XML Package Support . . . . . . . . . . . . . . . . . . . .12
5.1 XML Documents. . . . . . . . . . . . . . . . . . . . .12
5.2 XML Requests . . . . . . . . . . . . . . . . . . . . .13
5.3 XML Request History. . . . . . . . . . . . . . . . . .15
5.4 XML Events . . . . . . . . . . . . . . . . . . . . . .15
5.5 XML Tags . . . . . . . . . . . . . . . . . . . . . . .15
5.5.1 XML Tag. . . . . . . . . . . . . . . . . . . . . . .17
5.5.2 Card Tag . . . . . . . . . . . . . . . . . . . . . .18
5.5.3 P Tag. . . . . . . . . . . . . . . . . . . . . . . .18
5.5.4 Select Tag . . . . . . . . . . . . . . . . . . . . .18
5.5.5 Option Tag . . . . . . . . . . . . . . . . . . . . .19
5.5.6 Input Tag. . . . . . . . . . . . . . . . . . . . . .20
5.5.7 Echo Tag . . . . . . . . . . . . . . . . . . . . . .20
5.5.8 Calltimer Tag. . . . . . . . . . . . . . . . . . . .21
5.5.9 Time Tag . . . . . . . . . . . . . . . . . . . . . .21
5.5.10 Timer Tag . . . . . . . . . . . . . . . . . . . . .21
5.5.11 Do Tag. . . . . . . . . . . . . . . . . . . . . . .22
5.5.12 Go Tag. . . . . . . . . . . . . . . . . . . . . . .22
5.5.13 Prev Tag. . . . . . . . . . . . . . . . . . . . . .23
6. Security Considerations . . . . . . . . . . . . . . . . . .23
7. Acknowledgements. . . . . . . . . . . . . . . . . . . . . .23
8. References. . . . . . . . . . . . . . . . . . . . . . . . .23
9. Authors' Addresses. . . . . . . . . . . . . . . . . . . . .24
Appendix A: BNF description of XML grammar . . . . . . . . . .25
Appendix B: Sample XML Documents, Renderings and Events. . . .27
B.1 Sample Deck 1 (Itemized List Box). . . . . . . . . . .27
B.2 Sample Deck 2 (Enumerated List Box). . . . . . . . . .28
B.3 Sample Deck 3 (Text Box) . . . . . . . . . . . . . . .29
B.4 Sample Deck 4 (Echo Box) . . . . . . . . . . . . . . .30
B.5 Sample Deck 5 (Input Box). . . . . . . . . . . . . . .31
B.6 Sample Deck 6 (Timers) . . . . . . . . . . . . . . . .32
Appendix C: Example usage of MGCP extension packages . . . . .33
C.1 Setting Labels on Phone. . . . . . . . . . . . . . . .33
C.2 Activating a Feature on a Feature Key. . . . . . . . .33
C.3 Generating a Call using Feature Key as a Line Key. . .35
C.4 Determining Make and Model of a Phone. . . . . . . . .38
Appendix D: BNF Description of X-UA Parameter. . . . . . . . .39
Full Copyright Statement . . . . . . . . . . . . . . . . . . .41
3. Endpoint Naming and Phone Type Determination. . . . . . . .10
4. Functions that should be Locally Implemented. . . . . . . .11
4.1 Volume Control . . . . . . . . . . . . . . . . . . . .11
4.2 Audio Path . . . . . . . . . . . . . . . . . . . . . .11
4.3 Microphone mute button and light . . . . . . . . . . .11
5. XML Package Support . . . . . . . . . . . . . . . . . . . .12
5.1 XML Documents. . . . . . . . . . . . . . . . . . . . .12
5.2 XML Requests . . . . . . . . . . . . . . . . . . . . .13
5.3 XML Request History. . . . . . . . . . . . . . . . . .15
5.4 XML Events . . . . . . . . . . . . . . . . . . . . . .15
5.5 XML Tags . . . . . . . . . . . . . . . . . . . . . . .15
5.5.1 XML Tag. . . . . . . . . . . . . . . . . . . . . . .17
5.5.2 Card Tag . . . . . . . . . . . . . . . . . . . . . .18
5.5.3 P Tag. . . . . . . . . . . . . . . . . . . . . . . .18
5.5.4 Select Tag . . . . . . . . . . . . . . . . . . . . .18
5.5.5 Option Tag . . . . . . . . . . . . . . . . . . . . .19
5.5.6 Input Tag. . . . . . . . . . . . . . . . . . . . . .20
5.5.7 Echo Tag . . . . . . . . . . . . . . . . . . . . . .20
5.5.8 Calltimer Tag. . . . . . . . . . . . . . . . . . . .21
5.5.9 Time Tag . . . . . . . . . . . . . . . . . . . . . .21
5.5.10 Timer Tag . . . . . . . . . . . . . . . . . . . . .21
5.5.11 Do Tag. . . . . . . . . . . . . . . . . . . . . . .22
5.5.12 Go Tag. . . . . . . . . . . . . . . . . . . . . . .22
5.5.13 Prev Tag. . . . . . . . . . . . . . . . . . . . . .23
6. Security Considerations . . . . . . . . . . . . . . . . . .23
7. Acknowledgements. . . . . . . . . . . . . . . . . . . . . .23
8. References. . . . . . . . . . . . . . . . . . . . . . . . .23
9. Authors' Addresses. . . . . . . . . . . . . . . . . . . . .24
Appendix A: BNF description of XML grammar . . . . . . . . . .25
Appendix B: Sample XML Documents, Renderings and Events. . . .27
B.1 Sample Deck 1 (Itemized List Box). . . . . . . . . . .27
B.2 Sample Deck 2 (Enumerated List Box). . . . . . . . . .28
B.3 Sample Deck 3 (Text Box) . . . . . . . . . . . . . . .29
B.4 Sample Deck 4 (Echo Box) . . . . . . . . . . . . . . .30
B.5 Sample Deck 5 (Input Box). . . . . . . . . . . . . . .31
B.6 Sample Deck 6 (Timers) . . . . . . . . . . . . . . . .32
Appendix C: Example usage of MGCP extension packages . . . . .33
C.1 Setting Labels on Phone. . . . . . . . . . . . . . . .33
C.2 Activating a Feature on a Feature Key. . . . . . . . .33
C.3 Generating a Call using Feature Key as a Line Key. . .35
C.4 Determining Make and Model of a Phone. . . . . . . . .38
Appendix D: BNF Description of X-UA Parameter. . . . . . . . .39
Full Copyright Statement . . . . . . . . . . . . . . . . . . .41
The Media Gateway Control Protocol (MGCP) Version 1.0 defines a protocol for controlling Voice over IP Telephony Gateways from external call control elements. As defined, it supports external call control elements called Media Gateway Controllers and assumes that these Gateways can support collections of endpoints. The endpoint type known as an "analog line" can be used as a client interface to provide service to a basic analog telephone unit. The packages that are currently defined to handle events and signals allow for only a basic level of audio connection and signaling to such endpoints. To handle more advanced capabilities commonly found on business phones such as feature keys, speaker phones and displays, it is necessary to define additional packages as extensions to the MGCP protocol.
媒体网关控制协议（MGCP）1.0版定义了一种协议，用于控制来自外部呼叫控制元件的IP语音电话网关。根据定义，它支持称为媒体网关控制器的外部呼叫控制元素，并假设这些网关可以支持端点集合。称为“模拟线路”的端点类型可用作客户端接口，为基本模拟电话单元提供服务。当前定义用于处理事件和信号的包只允许基本级别的音频连接和到此类端点的信令。为了处理商务电话上常见的更高级功能，如功能键、扬声器电话和显示器，有必要将附加软件包定义为MGCP协议的扩展。
These packages, when used in conjunction with the packages currently defined in RFC 2705 (Media Gateway Control Protocol Version 1.0) [1], allow an MGCP Call Agent to control business phone endpoints.
这些包与RFC 2705（媒体网关控制协议版本1.0）[1]中当前定义的包一起使用时，允许MGCP呼叫代理控制业务电话端点。
The MGCP extension packages defined here are as follows:
此处定义的MGCP扩展包如下：
- Feature Key Package
- 功能密钥包
o Groups events and signals associated with the additional keys available on business phones that are non-DTMF and not locally-implemented. These include:
o 将事件和信号分组，这些事件和信号与非DTMF且非本地实现的商务电话上可用的其他按键相关。这些措施包括：
- Feature Key event to allow mapping of key numbers to features. - Key State signal to indicate the state of feature keys. - Set Label signal to display a label on the LCD next to a feature key.
- 功能键事件，以允许将键号映射到功能。-指示功能键状态的键状态信号。-设置标签信号以在LCD上功能键旁边显示标签。
- Business Phone Package
- 商务电话包
o Groups signals that are not related to feature keys, including:
o 对与功能键无关的信号进行分组，包括：
- Force Off-hook and Force On-hook signals to allow application integration with speaker phone capabilities. - Beep signal to play a beep on the phone.
- 强制挂断和强制挂断信号，以允许应用程序与扬声器电话功能集成。-蜂鸣声信号可在手机上播放蜂鸣声。
- Display XML Package
- 显示XML包
o Used to convey XML [2] script data to and from the phone to control the display and assign functions to the display soft-keys for event reporting. These include:
o 用于将XML[2]脚本数据传送至手机或从手机传送至手机，以控制显示，并为显示软键分配功能，以进行事件报告。这些措施包括：
- XML event to report user input or selection. - XML signal to render text to the LCD display.
- 用于报告用户输入或选择的XML事件。-将文本呈现到LCD显示器的XML信号。
An MGCP experimental parameter is also defined here:
此处还定义了MGCP实验参数：
- User Agent Parameter
- 用户代理参数
o Used to determine the make and model of a phone
o 用于确定手机的品牌和型号
A generic business phone typically includes a number of features that provide access to additional functionality useful in a business environment. Beyond the basic handset and dial pad, a business phone may optionally include a number of fixed buttons, line keys and programmable feature keys, along with an LCD display and soft-keys.
通用商务电话通常包括许多功能，这些功能提供对业务环境中有用的附加功能的访问。除了基本的手持设备和拨号板之外，商务电话还可以选择包括许多固定按钮、线路键和可编程功能键，以及LCD显示屏和软键。
Specific examples of items that may be included on a business phone are:
商务电话中可能包含的项目的具体示例如下：
- Speaker phone microphone and speaker - Speaker phone button and light - Messages button and light - Redial button - Volume up and down buttons - Hold button and light - Transfer button and light - Forward button and light - Conference button and light - Microphone mute button and light - Multiple feature keys with lights - Multi-line LCD Display - Multiple soft-keys next to the LCD display - Navigation keys
- 扬声器电话麦克风和扬声器-扬声器电话按钮和灯光-信息按钮和灯光-重拨按钮-音量上升和下降按钮-按住按钮和灯光-传输按钮和灯光-前进按钮和灯光-会议按钮和灯光-麦克风静音按钮和灯光-带灯光的多个功能键-多行LCD显示屏-LCD显示屏旁边的多个软键-导航键
Examples of fixed buttons functionality are 'hold', 'transfer', 'redial', 'conference', 'call-logs', 'directories', and 'messages'. Fixed buttons may vary from phone to phone. While the packages described here would allow these to be reported to a Call Agent, the Call Agent would also need to determine which feature key number corresponds to a particular pre-assigned function.
固定按钮功能的示例包括“保持”、“转接”、“重拨”、“会议”、“通话记录”、“目录”和“消息”。固定按钮可能因手机而异。虽然这里描述的包允许向呼叫代理报告这些功能，但呼叫代理还需要确定哪个功能密钥对应于特定的预分配功能。
Since MGCP assumes a call control architecture where the call control "intelligence" is outside the Gateways and handled by external call control elements, the programming of the feature keys would be resident in the Call Agent. If the user were to press the 'hold' button, the phone would simply report the key number, and the burden
由于MGCP采用呼叫控制体系结构，其中呼叫控制“智能”位于网关之外并由外部呼叫控制元件处理，因此功能键的编程将驻留在呼叫代理中。如果用户按下“保持”按钮，手机会简单地报告钥匙号码和负担
of recognizing that this feature key is assigned to the 'hold' function, and providing such functionality, is left to the Call Agent.
识别此功能键已分配给“保持”功能并提供此类功能的方法留给呼叫代理。
The high level objectives that were considered in generating the packages described here are:
生成此处所述包时考虑的高级别目标包括：
- Provide a minimum set of extension packages to the MGCP Version 1.0 protocol to allow applications to take advantage of generic business phone capabilities.
- 为MGCP 1.0版协议提供一组最少的扩展包，以允许应用程序利用通用商务电话功能。
- Provide event and control extensions at a sufficiently low level for an application to implement generic business phone functions without generating excessive or redundant data traffic. (e.g., sending feature key information on both press and release would be a "don't care" for a Call Agent. All it cares about is that the key was pressed.)
- 为应用程序提供足够低级别的事件和控制扩展，以便在不产生过多或冗余数据流量的情况下实现通用商务电话功能。（例如，在新闻和发布中发送功能键信息对呼叫代理来说是“不关心”的。它关心的只是按键被按下。）
- Provide a mechanism to interface with LCD displays and allow the flexibility to accommodate a variety of application needs and the different types of displays available.
- 提供与LCD显示器接口的机制，并允许灵活适应各种应用需求和不同类型的可用显示器。
The following packages should be implemented for business phones. The G,D,L, and H packages are defined in RFC 2705 [1]. Packages KY, BP and XML are defined in this specification.
应为商务电话实施以下软件包。RFC 2705[1]中定义了G、D、L和H包。本规范中定义了KY、BP和XML包。
______________________________________________________
| Package | Name | Defined |
|______________________________|_________|_____________|
| Generic Media Package | G |in RFC 2705 |
| DTMF package | D |in RFC 2705 |
| Line Package | L |in RFC 2705 |
| Handset Package | H |in RFC 2705 |
| Feature Key Package | KY |in this spec |
| Business Phone Package | BP |in this spec |
| Display XML Package | XML |in this spec |
|______________________________|_________|_____________|
______________________________________________________
| Package | Name | Defined |
|______________________________|_________|_____________|
| Generic Media Package | G |in RFC 2705 |
| DTMF package | D |in RFC 2705 |
| Line Package | L |in RFC 2705 |
| Handset Package | H |in RFC 2705 |
| Feature Key Package | KY |in this spec |
| Business Phone Package | BP |in this spec |
| Display XML Package | XML |in this spec |
|______________________________|_________|_____________|
In the tables of events for each package, there are five columns:
在每个包的事件表中，有五列：
Symbol: the unique symbol used for 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.
R：如果呼叫代理可以请求事件，则此列中会显示一个x。
S: if nothing appears in this column for an event, then the event cannot be signalled on command by the Call Agent. Otherwise, the following symbols identify the type of signal:
S：如果此列中没有显示任何事件，则调用代理无法通过命令通知该事件。否则，以下符号标识信号类型：
OO On/Off signal. The signal is turned on until requested by the Call Agent to turn it off, and vice versa.
OO开/关信号。该信号会一直打开，直到呼叫代理请求将其关闭，反之亦然。
TO Timeout signal. The signal lasts for a given duration unless it is superseded by a new signal.
发送超时信号。除非被新信号取代，否则信号将持续给定的时间。
BR Brief signal. The event has a short, known duration.
BR短信号。该事件的持续时间很短。
Duration: specifies the duration of TO signals.
持续时间：指定到信号的持续时间。
Package Name: KY
包装名称：KY
The Feature Key Package groups events and signals that are associated with the additional keys that are available on business phones.
功能密钥包将与商务电话上可用的其他密钥相关联的事件和信号分组。
____________________________________________________________________
| Symbol | Definition | R | S Duration |
|__________|____________________________|_____|______________________|
| fk1-fk99 | Feature Key | x | |
| ks | Key State | | OO |
| ls | Set Label | | OO |
|__________|____________________________|_____|______________________|
____________________________________________________________________
| Symbol | Definition | R | S Duration |
|__________|____________________________|_____|______________________|
| fk1-fk99 | Feature Key | x | |
| ks | Key State | | OO |
| ls | Set Label | | OO |
|__________|____________________________|_____|______________________|
Feature Key (fk1-fk99)
功能键（fk1-fk99）
These events map to all the keys on the phone that are not DTMF keys or locally implemented functions (such as volume). The mapping of fk number to key is expected to vary between phones.
这些事件映射到手机上所有非DTMF键或本地实现功能（如音量）的键。fk号码到钥匙的映射在不同的手机中可能会有所不同。
Note: Some have suggested parameterizing the fk event, i.e., sending an RQNT with "R: KY/fk" and an NTFY with "O: KY/fk(1)", but this is problematic; It is desirable to request only the keys that can be pressed in a given state, to eliminate the chance that a mis-pressed button will cancel a timeout signal, as well as to reduce message traffic. This is not possible within the confines of MGCP, as requested events cannot be parameterized.
注：一些人建议参数化fk事件，即发送带有“R:KY/fk”的RQNT和带有“O:KY/fk（1）”的NTFY，但这是有问题的；希望仅请求在给定状态下可按下的键，以消除误按按钮取消超时信号的可能性，并减少消息流量。这在MGCP的范围内是不可能的，因为请求的事件无法参数化。
Key State (ks)
关键州（ks）
This signal is used to indicate the state of a feature key. It should be ignored by phones without this capability.
此信号用于指示功能键的状态。没有这种功能的手机应该忽略它。
This signal has two parameters: key number and state. The key number maps directly to the feature key number. The state is a high level description of the state of the key. This allows different phones to implement different indications of state. For example, Phone A may have a multi-color LED associated with feature keys that can blink at different cadences. Phone B might have an LCD beside the keys that can display text or icons. It is up to each phone vendor to determine how to present the state indication.
该信号有两个参数：键号和状态。钥匙编号直接映射到功能钥匙编号。状态是密钥状态的高级描述。这允许不同的手机实现不同的状态指示。例如，手机A可能有一个与功能键相关联的多色LED，可以以不同的节奏闪烁。手机B的按键旁边可能有一个LCD，可以显示文本或图标。由每个电话供应商决定如何显示状态指示。
The following states are used:
使用以下状态：
______________________
| State | Definition |
|_______|______________|
| en | enabled |
| db | disabled |
| id | idle |
| dt | dial tone |
| cn | connected |
| dc | disconnected |
| rg | ringing |
| rb | ringback |
| ho | holding |
| he | held |
|_______|______________|
______________________
| State | Definition |
|_______|______________|
| en | enabled |
| db | disabled |
| id | idle |
| dt | dial tone |
| cn | connected |
| dc | disconnected |
| rg | ringing |
| rb | ringback |
| ho | holding |
| he | held |
|_______|______________|
For example: an RQNT with "S: KY/ks(5,en)" will cause an indicator corresponding to fk5 to indicate that it is enabled. An RQNT with "S: KY/ks(2,rg)" will cause an indicator corresponding to fk2 to indicate that it is ringing.
例如：带有“S:KY/ks（5，en）”的RQNT将导致对应于fk5的指示器指示其已启用。带有“S:KY/ks（2，rg）”的RQNT将导致与fk2对应的指示器指示其正在鸣响。
"en" state
“en”状态
The associated feature is enabled. Used for keys that turn a feature on or off, such as "Do Not Disturb."
关联的功能已启用。用于打开或关闭功能的按键，如“请勿打扰”
"db" state
“db”状态
The associated feature is disabled. Used for keys that turn a feature on or off, such as "Do Not Disturb."
关联的功能已禁用。用于打开或关闭功能的按键，如“请勿打扰”
"id" state
“id”状态
The specified line appearance is in the idle state, available for a call.
指定的线路外观处于空闲状态，可用于呼叫。
"dt" state
“dt”状态
The specified line appearance is providing dial-tone.
指定的线路外观提供拨号音。
"cn" state
“cn”国
The specified line appearance is actively in a call, in the connected state.
指定的线路外观在呼叫中处于活动状态，处于连接状态。
"dc" state
“dc”状态
The specified line appearance is disconnected, but the corresponding line is still active (the user is still offhook).
指定的行外观已断开连接，但相应的行仍处于活动状态（用户仍处于脱机状态）。
"rg" state
“rg”状态
The specified line appearance is terminating an incoming call, in the ringing state.
指定的线路外观是在振铃状态下终止传入呼叫。
"rb" state
“rb”状态
The specified line appearance is originating an outgoing call, in the ringing-back state.
在回铃状态下，指定的线路外观正在发起传出呼叫。
"ho" state
“何”国
The specified line appearance is in the holding state, with the far end held.
指定的线外观处于保持状态，远端保持不变。
"he" state
“他”状态
The specified line appearance is in the held state, with the far end holding.
指定的线外观处于保持状态，远端保持。
Set Label (ls)
设置标签（ls）
This signal is used to set the label on a key. This is used for phones that have an LCD next to the feature keys. It should be ignored by phones without this capability.
此信号用于设置钥匙上的标签。这用于功能键旁边有LCD的手机。没有这种功能的手机应该忽略它。
This signal has 2 parameters: key number and label. The key number maps directly to the feature key number. The label is free form text, restricted to the capabilities of the phone.
该信号有两个参数：钥匙号和标签。钥匙编号直接映射到功能钥匙编号。标签为自由格式文本，仅限于手机的功能。
For example, an RQNT with "S: KY/ls(1,2200)" sets the label next to the fk1 feature key to the string "2200" (a phone extension).
例如，带有“S:KY/ls（12200）”的RQNT将fk1功能键旁边的标签设置为字符串“2200”（电话分机）。
Package Name: BP
软件包名称：BP
The Business Phone Package groups signals other than those related to feature keys and displays.
商务电话包对与功能键和显示相关的信号以外的信号进行分组。
____________________________________________________________________
| Symbol | Definition | R | S Duration |
|__________|____________________________|_____|______________________|
| hd | Force Offhook | | OO |
| hu | Force Onhook | | OO |
| beep | Beep | | BR |
|__________|____________________________|_____|______________________|
____________________________________________________________________
| Symbol | Definition | R | S Duration |
|__________|____________________________|_____|______________________|
| hd | Force Offhook | | OO |
| hu | Force Onhook | | OO |
| beep | Beep | | BR |
|__________|____________________________|_____|______________________|
Force Offhook (hd)
离钩力（hd）
This signal is used to force the phone offhook. If the phone has a speaker phone, it should be activated. This signal can be negated by the user by hanging up.
此信号用于强制手机脱离挂钩。如果手机有扬声器，则应将其激活。用户可以通过挂断来消除该信号。
This can be used if a feature key causes a call to be initiated. See the sample call flow in Appendix C.
如果功能键导致启动呼叫，则可以使用此选项。参见附录C中的呼叫流程示例。
This can also be used for application integration. For example, a user could select a number in an application on their PC, and the phone would be forced offhook and a call initiated.
这也可用于应用程序集成。例如，用户可以在其PC上的应用程序中选择一个号码，手机将被强制摘机并启动通话。
Force Onhook (hu)
上钩力（hu）
This signal forces the phone onhook. This can be used when the far-end disconnects, or if a feature key causes a call to be terminated.
此信号强制手机挂接。这可以在远端断开连接时使用，或者在功能键导致呼叫终止时使用。
Beep (beep)
嘟嘟声（嘟嘟声）
Play a beep on the phone.
在手机上播放嘟嘟声。
Package Name: XML
包名称：XML
The XML Package contains one event/signal that is used to convey XML data to and from the phone.
XML包包含一个事件/信号，用于向手机传递XML数据和从手机传递XML数据。
_____________________________________________________________________
| Symbol | Definition | R | S Duration |
|__________|____________________________|_____|______________________|
| xml | XML Data | x | OO |
|__________|____________________________|_____|______________________|
_____________________________________________________________________
| Symbol | Definition | R | S Duration |
|__________|____________________________|_____|______________________|
| xml | XML Data | x | OO |
|__________|____________________________|_____|______________________|
XML Data (xml)
XML数据（XML）
As an event, if this event is requested in an RQNT with "R: XML/xml", any posts of data from an XML script are returned in an NTFY with "O: XML/xml(post data here)".
作为一个事件，如果在带有“R:XML/XML”的RQNT中请求此事件，则XML脚本中的任何数据发布都将在带有“O:XML/XML（此处的发布数据）”的NTFY中返回。
As a signal, the parameterized data indicates a URL to an XML script (possibly local), as well as substitution values that depend on the XML script selected. See section 5 for more information.
作为信号，参数化数据指示XML脚本的URL（可能是本地的），以及依赖于所选XML脚本的替换值。更多信息请参见第5节。
Because the display state can be asynchronous from the signaling state of the phone, it is desirable to address the display as a separate MGCP endpoint.
由于显示状态可以与电话的信令状态异步，因此希望将显示作为单独的MGCP端点进行寻址。
For example, suppose a call is presented to the phone, and a display is presented that gives the user the option of redirecting the caller immediately to voice-mail. Selecting the option via the display would cause an XML post to occur, cancelling any timeout signals (the ringing).
例如，假设向手机显示一个呼叫，并显示一个屏幕，用户可以选择立即将呼叫方重定向到语音邮件。通过显示器选择该选项将导致XML post发生，取消任何超时信号（铃声）。
In order to simplify the handling of such scenarios, it is expected that the related display have a different MGCP endpoint name, created by inserting a prefix before the phone endpoint name. The prefix used shall be "disp/".
为了简化此类场景的处理，预期相关显示具有不同的MGCP端点名称，通过在电话端点名称之前插入前缀创建。使用的前缀应为“disp/”。
For example, if the phone endpoint has the name "ep1@foo.whatever.net", the display endpoint would be named "disp/ep1@foo.whatever.net".
例如，如果电话端点的名称为“ep1@foo.whatever.net，则显示端点将命名为“disp”/ep1@foo.whatever.net".
The Call Agent must be able to determine which feature key number corresponds to a particular pre-assigned function. For example, one phone may have the pre-assigned functions of 'redial' and 'hold' mapped to feature keys numbered fk1 and fk23, respectively. Another phone may not report fk23 at all, and have the pre-assigned function of 'transfer' mapped to fk1. Also, since the programming of feature keys would be resident in the Call Agent, a user-interface that
呼叫代理必须能够确定与特定预分配功能对应的功能密钥号。例如，一部手机可能具有预先分配的“重拨”和“保持”功能，分别映射到编号为fk1和fk23的功能键。另一部手机可能根本不报告fk23，并将预先分配的“传输”功能映射到fk1。此外，由于功能键的编程将驻留在调用代理中，因此
allows the programming of these keys must know the keys supported on the phone, in order for the Call Agent to request the appropriate feature keys.
允许对这些按键进行编程必须知道手机支持的按键，以便呼叫代理请求相应的功能按键。
Determination of such basic capabilities must occur at the moment when the phone sends its first RSIP message to a Call Agent. While it might be possible to define packages with events and signals that allow for an exhaustive discovery of the layout of a particular phone, a simpler and more reasonable approach would be for the Call Agent to discover the make and model of the phone, and thus determine the capabilities of the phone. To this end, an experimental parameter, "X-UA" has been introduced for use in the Requested-Info field (F:) of the AUEP method. The response to the "X-UA" is expected to be a string that uniquely identifies the make and model of the phone. Note that per RFC 2705, a Gateway must ignore experimental parameters prefixed as "X-" that it cannot support, versus respond with an error code such as 511 (Unrecognized extension). See the sample call flow in Appendix C.
当手机向呼叫代理发送其第一条RSIP消息时，必须确定此类基本功能。虽然可以定义带有事件和信号的包，以允许详尽地发现特定电话的布局，但更简单、更合理的方法是呼叫代理发现电话的品牌和型号，从而确定电话的功能。为此，引入了一个实验参数“X-UA”，用于AUEP方法的请求信息字段（F:）。对“X-UA”的响应应该是唯一标识手机品牌和型号的字符串。请注意，根据RFC 2705，网关必须忽略前缀为“X-”的实验参数，而不是使用错误代码（如511（无法识别的扩展名））进行响应。参见附录C中的呼叫流程示例。
Some functions should be implemented locally on the Gateway. These are listed in the following sections.
有些功能应该在网关上本地实现。以下各节列出了这些问题。
Volume for ringing, handset, and speaker phone should be implemented locally on the Gateway.
铃声、手机和扬声器电话的音量应在网关上本地实现。
If the phone includes a speaker phone, activating the speaker phone from the idle state should generate an offhook (L/hd) event. The user should then be able to switch to handset mode by lifting the handset, and be able to switch back to speaker phone mode without any interaction with the Call Agent. De-activating the speaker phone with the handset on-hook should generate an onhook (L/hu) event.
如果手机包含扬声器电话，则从空闲状态激活扬声器电话应生成摘机（L/hd）事件。然后，用户应能够通过提起手机切换到手机模式，并能够在不与呼叫代理进行任何交互的情况下切换回扬声器电话模式。在手机挂机的情况下取消激活扬声器电话应产生挂机（L/hu）事件。
If the phone includes a microphone mute button and (optionally) an associated indicator (e.g., light), the functionality of these items should be implemented locally on the Gateway.
如果手机包含麦克风静音按钮和（可选）相关指示灯（如指示灯），则这些项目的功能应在网关上本地实现。
Not all business phones have the same display and keypad capabilities. To support these varying devices in a consistent manner, this section outlines an XML framework that is used to drive the phone. In this framework, the Call Agent pushes XML requests to the Gateway using MGCP signals. These XML requests indicate the XML document that is to be rendered on the phone.
并非所有的商务电话都具有相同的显示和键盘功能。为了以一致的方式支持这些不同的设备，本节概述了用于驱动手机的XML框架。在此框架中，调用代理使用MGCP信号将XML请求推送到网关。这些XML请求表示要在手机上呈现的XML文档。
When a user inputs data or makes a selection from a display, the Gateway "posts" an XML request to the Call Agent using MGCP events.
当用户输入数据或从显示器中进行选择时，网关使用MGCP事件向呼叫代理“发布”XML请求。
When an XML signal request is sent to an endpoint, it indicates the XML documents that the endpoint must process. These documents contain tags that are a subset of the Wireless Markup Language (WML) [3] plus some non-WML additions. These tags specify items to be displayed as well as XML events that may be reported as the result of user input.
当向端点发送XML信号请求时，它指示端点必须处理的XML文档。这些文档包含的标记是无线标记语言（WML）[3]的一个子集，加上一些非WML添加项。这些标记指定要显示的项目以及可能作为用户输入结果报告的XML事件。
Each XML document, known as a card, defines a user interaction. A group of cards is called a deck. One or more decks define an application. The cards define soft key behavior as well as display behavior, and are mapped to components that implement the behavior of a basic graphical user interface on the display phone. Based on the available requirements, the components needed are:
每个XML文档（称为卡片）定义了一个用户交互。一组牌叫做牌组。一个或多个组定义应用程序。这些卡定义软键行为和显示行为，并映射到实现显示电话上基本图形用户界面行为的组件。根据可用要求，所需组件包括：
- Input box:
- 输入框：
allows user input, including editing capabilities, via the keypad.
允许用户通过键盘输入，包括编辑功能。
- Enumerated list box:
- 枚举列表框：
allows the user to select one of a list of items.
允许用户从项目列表中选择一项。
- Itemized list box:
- 分项列表框：
allows the user to select an item using a soft key.
允许用户使用软键选择项目。
- Text box:
- 文本框：
displays read-only text to the user.
向用户显示只读文本。
- Echo box:
- 回音盒：
displays but does not process user input.
显示但不处理用户输入。
A card may have the following properties.
卡可能具有以下属性。
1. Timed content (e.g., card expiration) 2. Static content (e.g., text) 3. Dynamic content (e.g., call timers/time)
1. 定时内容（例如，卡过期）2。静态内容（如文本）3。动态内容（例如，通话计时器/时间）
Additionally, cards may also contain variables to be substituted for values that are specified in an XML request. See section 5.2 for details on variable substitution.
此外，卡还可能包含要替换XML请求中指定的值的变量。有关变量替换的详细信息，请参见第5.2节。
There are cases where the XML scripts handling the display need to use keys that are also used by the phone. For example, the display could present an enumerated list, where a particular item is selected by pressing the associated number on the dial pad. All user key presses must be routed through the XML component layer. The display layer either consumes the key presses or passes them on to the phone layer for consumption.
在某些情况下，处理显示的XML脚本需要使用手机也使用的按键。例如，显示器可能会显示一个枚举列表，在该列表中，通过按拨号板上的关联号码来选择特定项目。所有用户按键都必须通过XML组件层进行路由。显示层要么使用按键，要么将按键传递给电话层以供使用。
The code handling key presses should thus present a key press to the display code first. If the display code does not "use" the key press, then the key press should be presented to the phone code. This gives precedence to the XML scripts for key presses.
因此，代码处理按键应首先向显示代码显示按键。如果显示代码未“使用”按键，则按键应显示在手机代码中。这为按键的XML脚本提供了优先权。
The XML framework uses MGCP as its transport for making requests to the display phone. MGCP is also used to receive asynchronous events from the display phone (e.g., an item has been selected, or the user has entered text).
XML框架使用MGCP作为向显示电话发出请求的传输。MGCP还用于从显示电话接收异步事件（例如，已选择项目，或用户已输入文本）。
An XML request is made to an endpoint using the XML/xml signal. The signal has the following format:
使用XML/XML信号向端点发出XML请求。信号具有以下格式：
S: XML/xml(<url>?<card>?$<variable1>=<value1>?$<variable2>=<value2>)
S: XML/xml(<url>?<card>?$<variable1>=<value1>?$<variable2>=<value2>)
The first component of the signal parameter is a URL to the deck. If no scheme is indicated, the deck is assumed to be local to the phone. Here are some examples:
signal参数的第一个组件是指向数据组的URL。如果未指明任何方案，则假定该组是手机的本地组。以下是一些例子：
ftp://server.company.com/deck1?card1?$var1=val1
http://www.company.com/deck1?card1?$var1=val1
file://deck1?card1?$var1=val1
deck1?card1?$var1=val1
ftp://server.company.com/deck1?card1?$var1=val1
http://www.company.com/deck1?card1?$var1=val1
file://deck1?card1?$var1=val1
deck1?card1?$var1=val1
A card identifier and a list of variable/value pairs follow the URL. The card identifier indicates the card within the deck to display.
URL后面有卡标识符和变量/值对列表。卡标识符指示要显示的卡组中的卡。
The variable/value pairs are substituted into the deck before it is rendered to the display. This means that the variables are deck-scoped, and variables not defined in the requested card must be populated in other cards in the same deck if defined therein.
变量/值对在呈现到显示器之前被替换到数据组中。这意味着变量的作用域是卡组范围，如果在同一卡组中定义了变量，则请求卡中未定义的变量必须填充到同一卡组中的其他卡中。
For example, a deck may contain the following cards:
例如，牌组可能包含以下牌：
<card id="one">
<p>$line1</p>
<timer value="2"/>
<do type="ontimer">
<go href="#two"/>
</do>
</card>
<card id="one">
<p>$line1</p>
<timer value="2"/>
<do type="ontimer">
<go href="#two"/>
</do>
</card>
<card id="two">
<p>$line2</p>
</card>
<card id="two">
<p>$line2</p>
</card>
And an XML request may look like:
XML请求可能如下所示：
S: XML/xml(deck?one?$line1=abc$line2=xyz)
S: XML/xml(deck?one?$line1=abc$line2=xyz)
After variable substitution, the deck will look like:
变量替换后，甲板将如下所示：
<card id="one">
<p>abc</p>
</card>
<card id="one">
<p>abc</p>
</card>
<card id="two">
<p>$line2</p>
</card>
<card id="two">
<p>$line2</p>
</card>
Once variable substitution is complete, the card is rendered. If a parameter variable does not exist anywhere in the deck it should be ignored.
变量替换完成后，将呈现卡。如果参数变量不存在于数据组中的任何位置，则应忽略它。
When card two is invoked from card1 in response to the timeout action, card two's variables are substituted with the variables values passed as a request to card one. Card two will look like:
当响应超时操作从card1调用卡2时，卡2的变量将替换为作为请求传递给卡1的变量值。第二张牌看起来像：
<card id="two">
<p>xyz</p>
</card>
<card id="two">
<p>xyz</p>
</card>
In order to support navigation through a request history such as when a user cancels a card, the XML layer must maintain a last-in-first-out history of requests made for the endpoint. (See the <prev> tag definition in section 5.5.13.)
为了支持在请求历史记录中导航，例如当用户取消卡时，XML层必须维护针对端点的请求的后进先出历史记录。（参见第5.5.13节中的标签定义。）
Whenever the XML layer determines that an event has occurred, it reports the event using the MGCP observed event field:
每当XML层确定某个事件已发生时，它都会使用MGCP观察到的事件字段报告该事件：
O:
XML/xml(post?<deck>?<card>?<variable1>=<value1>?<variable2>=<value2>)
O:
XML/xml(post?<deck>?<card>?<variable1>=<value1>?<variable2>=<value2>)
Here, the event parameter contains the deck and card that generated the event, as well as data that is to be processed by the Call Agent. The data being posted is in the form of a list of variable/value pairs.
这里，event参数包含生成事件的卡片组和卡片，以及调用代理将要处理的数据。正在发布的数据以变量/值对列表的形式出现。
In order for the Gateway to properly generate the XML event, it is necessary for the Call Agent to request the event using the requested events field:
为了使网关正确生成XML事件，呼叫代理必须使用requested events字段请求事件：
R: XML/xml
R:XML/XML
This requested event should be combined with the signal request in an RQNT.
此请求的事件应与RQNT中的信号请求相结合。
Any XML implementation must at a minimum support the XML tags listed in the table that follows. All tags have a terminator tag of the form </tag> to indicate the end of the tag. See the XML grammar in Appendix A.
任何XML实现都必须至少支持下表中列出的XML标记。所有标记都有一个形式为</tag>的终止标记，以指示标记的结束。参见附录A中的XML语法。
_____________________________________________________________________
| Name | Usage |
|_______________|_____________________________________________________|
| <xml> | Marks the beginning of a deck. |
|_______________|_____________________________________________________|
| <card> | Marks the beginning of a card. |
|_______________|_____________________________________________________|
| <p> | Marks the beginning of a paragraph. |
|_______________|_____________________________________________________|
| <select> | Defines a list of items that may be selected (an |
| | enumerated or itemized list box). |
|_______________|_____________________________________________________|
| <option> | Used in conjunction with the <select> tag to |
| | specify an individual item that may be selected. |
|_______________|_____________________________________________________|
| <input> | Marks the beginning of user input (an input box). |
|_______________|_____________________________________________________|
| <echo> | Marks the beginning of an echo box. |
|_______________|_____________________________________________________|
| <calltimer> | Call Timer. An incremental timer usually used to |
| | maintain the duration of a call. |
|_______________|_____________________________________________________|
| <timer> | Card timer. Allows an event to be generated when |
| | the timer expires. |
|_______________|_____________________________________________________|
| <time> | A tag indicating the current time. |
|_______________|_____________________________________________________|
| <do> | Event consumer. |
|_______________|_____________________________________________________|
| <go> | Used in conjunction with the <do> tag to indicate |
| | a new page to be displayed. |
|_______________|_____________________________________________________|
| <prev> | Used in conjunction with the <do> tag to indicate |
| | that the previous card in the history should be |
| | displayed. |
|_______________|_____________________________________________________|
_____________________________________________________________________
| Name | Usage |
|_______________|_____________________________________________________|
| <xml> | Marks the beginning of a deck. |
|_______________|_____________________________________________________|
| <card> | Marks the beginning of a card. |
|_______________|_____________________________________________________|
| <p> | Marks the beginning of a paragraph. |
|_______________|_____________________________________________________|
| <select> | Defines a list of items that may be selected (an |
| | enumerated or itemized list box). |
|_______________|_____________________________________________________|
| <option> | Used in conjunction with the <select> tag to |
| | specify an individual item that may be selected. |
|_______________|_____________________________________________________|
| <input> | Marks the beginning of user input (an input box). |
|_______________|_____________________________________________________|
| <echo> | Marks the beginning of an echo box. |
|_______________|_____________________________________________________|
| <calltimer> | Call Timer. An incremental timer usually used to |
| | maintain the duration of a call. |
|_______________|_____________________________________________________|
| <timer> | Card timer. Allows an event to be generated when |
| | the timer expires. |
|_______________|_____________________________________________________|
| <time> | A tag indicating the current time. |
|_______________|_____________________________________________________|
| <do> | Event consumer. |
|_______________|_____________________________________________________|
| <go> | Used in conjunction with the <do> tag to indicate |
| | a new page to be displayed. |
|_______________|_____________________________________________________|
| <prev> | Used in conjunction with the <do> tag to indicate |
| | that the previous card in the history should be |
| | displayed. |
|_______________|_____________________________________________________|
Most of these tags have attributes. Each attribute has one of the following types: String, Time, Enum, Align, Action or URL:
大多数标签都有属性。每个属性都有以下类型之一：字符串、时间、枚举、对齐、操作或URL：
_______________ _____________________________________________________
| Type | Format |
|_______________|_____________________________________________________|
| String | Any string. May not contain any white spaces |
| | (tab, space or newline). |
|_______________|_____________________________________________________|
| Time | A string of the format hh:mm:ss where hh indicates |
| | the hour (24-hour format), mm indicates the |
| | minutes and ss indicates the seconds. |
|_______________|_____________________________________________________|
| Enum | Enumeration. A list of acceptable string values. |
|_______________|_____________________________________________________|
| Align | Indicates text alignment (left justified, centered |
| | or right justified). Valid values are: left, |
| | center, right. The default value is: left. |
|_______________|_____________________________________________________|
| Action | Defines a string to be sent to the Call Agent. |
| | This string has the format: |
| | post?%var1[=%val1[?%var2[=%val2]]] |
| | where variables that should be substituted before |
| | sending the string to the Call Agent begin |
| | with a '%'. |
| | The tags that make up the card determine what |
| | variables are available to this string. See the |
| | following sections for variables that are defined |
| | for each tag. |
|_______________|_____________________________________________________|
| URL | The URL may have take several forms: |
| | 1. #<card> to indicate another card within |
| | the same deck |
| | 2. A string of type Action |
| | 3. #<prev> to indicate the previous card in |
| | the history |
|_______________|_____________________________________________________|
_______________ _____________________________________________________
| Type | Format |
|_______________|_____________________________________________________|
| String | Any string. May not contain any white spaces |
| | (tab, space or newline). |
|_______________|_____________________________________________________|
| Time | A string of the format hh:mm:ss where hh indicates |
| | the hour (24-hour format), mm indicates the |
| | minutes and ss indicates the seconds. |
|_______________|_____________________________________________________|
| Enum | Enumeration. A list of acceptable string values. |
|_______________|_____________________________________________________|
| Align | Indicates text alignment (left justified, centered |
| | or right justified). Valid values are: left, |
| | center, right. The default value is: left. |
|_______________|_____________________________________________________|
| Action | Defines a string to be sent to the Call Agent. |
| | This string has the format: |
| | post?%var1[=%val1[?%var2[=%val2]]] |
| | where variables that should be substituted before |
| | sending the string to the Call Agent begin |
| | with a '%'. |
| | The tags that make up the card determine what |
| | variables are available to this string. See the |
| | following sections for variables that are defined |
| | for each tag. |
|_______________|_____________________________________________________|
| URL | The URL may have take several forms: |
| | 1. #<card> to indicate another card within |
| | the same deck |
| | 2. A string of type Action |
| | 3. #<prev> to indicate the previous card in |
| | the history |
|_______________|_____________________________________________________|
The <xml> tag must be the first tag specified in the deck. It indicates the beginning of the deck.
<xml>标记必须是组中指定的第一个标记。它表示甲板的开始。
This tag has no attributes.
此标记没有属性。
The <card> tag marks the beginning of a new card.
<card>标签标记新卡的开始。
This tag has the following attributes:
_______________ _____________________ _______________________________
|Attribute Name | Values | Usage |
|_______________|_____________________|_______________________________|
| Id | String | Defines the card identifier. |
| | | This identifier is referenced |
| | | in XML requests. |
|_______________|_____________________|_______________________________|
This tag has the following attributes:
_______________ _____________________ _______________________________
|Attribute Name | Values | Usage |
|_______________|_____________________|_______________________________|
| Id | String | Defines the card identifier. |
| | | This identifier is referenced |
| | | in XML requests. |
|_______________|_____________________|_______________________________|
The <p> tag marks the beginning of a new paragraph.
标签标记新段落的开头。
This tag has the following attributes:
_______________ _____________________ _______________________________
|Attribute Name | Values (default) | Usage |
|_______________|_____________________|_______________________________|
|Mode | Enum: wrap/nowrap | Specifies whether the |
| | (wrap) | paragraph wraps or is |
| | | truncated when it extends past|
| | | the display width. |
|_______________|_____________________|_______________________________|
| Align | Align | Specifies alignment of the |
| | | paragraph. |
|_______________|_____________________|_______________________________|
This tag has the following attributes:
_______________ _____________________ _______________________________
|Attribute Name | Values (default) | Usage |
|_______________|_____________________|_______________________________|
|Mode | Enum: wrap/nowrap | Specifies whether the |
| | (wrap) | paragraph wraps or is |
| | | truncated when it extends past|
| | | the display width. |
|_______________|_____________________|_______________________________|
| Align | Align | Specifies alignment of the |
| | | paragraph. |
|_______________|_____________________|_______________________________|
The <select> tag marks the beginning of a list of items that may be selected. Each item is defined using an <option> tag described in section 5.5.5.
<select>标记标记可选择项目列表的开始。使用第5.5.5节所述的<option>标签定义每个项目。
This tag has the following attributes:
_______________ _____________________ _______________________________
|Attribute Name | Values (default) | Usage |
|_______________|_____________________|_______________________________|
| type | Enum: item/enum | Specifies the type of list: |
| | (enum) | itemized or enumerated. An |
| | | itemized list maps options to |
| | | soft keys. |
|_______________|_____________________|_______________________________|
| name | String | Specifies name of the list. |
| | | This attribute is available to|
| | | any Action string in the card |
| | | by using the %name variable. |
|_______________|_____________________|_______________________________|
| iname | String | Defines an index variable with|
| | | the specified name. This |
| | | variable is used in the |
| | | <option> tag to specify the |
| | | index of an item that is |
| | | selected. The value of this |
| | | attribute is available to any |
| | | Action string in the card by |
| | | using the %iname variable. The|
| | | value of the index variable is|
| | | available by using the |
| | | %<string value> variable. |
| | | See examples below. |
|_______________|_____________________|_______________________________|
This tag has the following attributes:
_______________ _____________________ _______________________________
|Attribute Name | Values (default) | Usage |
|_______________|_____________________|_______________________________|
| type | Enum: item/enum | Specifies the type of list: |
| | (enum) | itemized or enumerated. An |
| | | itemized list maps options to |
| | | soft keys. |
|_______________|_____________________|_______________________________|
| name | String | Specifies name of the list. |
| | | This attribute is available to|
| | | any Action string in the card |
| | | by using the %name variable. |
|_______________|_____________________|_______________________________|
| iname | String | Defines an index variable with|
| | | the specified name. This |
| | | variable is used in the |
| | | <option> tag to specify the |
| | | index of an item that is |
| | | selected. The value of this |
| | | attribute is available to any |
| | | Action string in the card by |
| | | using the %iname variable. The|
| | | value of the index variable is|
| | | available by using the |
| | | %<string value> variable. |
| | | See examples below. |
|_______________|_____________________|_______________________________|
When used in conjunction with the <select> tag, the <option> tag specifies an individual item that may be selected from a list.
当与<select>标记一起使用时，<option>标记指定可以从列表中选择的单个项目。
This tag has the following attributes:
_______________ _____________________ _______________________________
|Attribute Name | Values | Usage |
|_______________|_____________________|_______________________________|
| value | String | Defines the value of the item.|
| | | This is used when reporting an|
| | | event to the Call Agent. The |
| | | value of this attribute is |
| | | available to any Action string|
| | | in the card by using the |
| | | %value variable. |
|_______________|_____________________|_______________________________|
| onpick | Action | Defines the string to be sent |
| | | to the Call Agent when the |
| | | item is selected. |
|_______________|_____________________|_______________________________|
This tag has the following attributes:
_______________ _____________________ _______________________________
|Attribute Name | Values | Usage |
|_______________|_____________________|_______________________________|
| value | String | Defines the value of the item.|
| | | This is used when reporting an|
| | | event to the Call Agent. The |
| | | value of this attribute is |
| | | available to any Action string|
| | | in the card by using the |
| | | %value variable. |
|_______________|_____________________|_______________________________|
| onpick | Action | Defines the string to be sent |
| | | to the Call Agent when the |
| | | item is selected. |
|_______________|_____________________|_______________________________|
The <input> tag specifies that user input is required.
<input>标记指定需要用户输入。
This tag has the following attributes:
_______________ _____________________ _______________________________
|Attribute Name | Values | Usage |
|_______________|_____________________|_______________________________|
| name | String | Specifies the name of the |
| | | input tag. The value of this |
| | | attribute is available to any |
| | | Action string in the card by |
| | | using the %name variable. |
|_______________|_____________________|_______________________________|
| type | Enum: password/text | Specifies whether the input |
| | (text) | box is in password mode |
| | | (password) or normal mode |
| | | (text). When in password mode,|
| | | user input should be masked. |
|_______________|_____________________|_______________________________|
This tag has the following attributes:
_______________ _____________________ _______________________________
|Attribute Name | Values | Usage |
|_______________|_____________________|_______________________________|
| name | String | Specifies the name of the |
| | | input tag. The value of this |
| | | attribute is available to any |
| | | Action string in the card by |
| | | using the %name variable. |
|_______________|_____________________|_______________________________|
| type | Enum: password/text | Specifies whether the input |
| | (text) | box is in password mode |
| | | (password) or normal mode |
| | | (text). When in password mode,|
| | | user input should be masked. |
|_______________|_____________________|_______________________________|
The <echo> tag indicates that user input is required. Any keypad activity is reported to the XML layer but not consumed when this tag is used.
<echo>标记表示需要用户输入。任何键盘活动都会报告给XML层，但在使用此标记时不会被使用。
This tag has the following attributes:
_______________ _____________________ _______________________________
|Attribute Name | Values (default) | Usage |
|_______________|_____________________|_______________________________|
| mode | Enum: on/off (on) | Specifies whether the echo box|
| | | is in password mode (off) or |
| | | normal mode (on). When in |
| | | password mode, user input |
| | | should be masked. |
|_______________|_____________________|_______________________________|
| align | Align | Specifies the alignment of the|
| | | echo tag. |
|_______________|_____________________|_______________________________|
This tag has the following attributes:
_______________ _____________________ _______________________________
|Attribute Name | Values (default) | Usage |
|_______________|_____________________|_______________________________|
| mode | Enum: on/off (on) | Specifies whether the echo box|
| | | is in password mode (off) or |
| | | normal mode (on). When in |
| | | password mode, user input |
| | | should be masked. |
|_______________|_____________________|_______________________________|
| align | Align | Specifies the alignment of the|
| | | echo tag. |
|_______________|_____________________|_______________________________|
The <calltimer> tag is used to indicate that an incrementing timer is to be displayed.
<calltimer>标记用于指示要显示递增计时器。
This tag has the following attributes:
_______________ _____________________ _______________________________
|Attribute Name | Values | Usage |
|_______________|_____________________|_______________________________|
| value | Time | Specifies the initial value of|
| | | the call timer. |
|_______________|_____________________|_______________________________|
| align |Align | Specifies the alignment of the|
| | | call timer. |
|_______________|_____________________|_______________________________|
This tag has the following attributes:
_______________ _____________________ _______________________________
|Attribute Name | Values | Usage |
|_______________|_____________________|_______________________________|
| value | Time | Specifies the initial value of|
| | | the call timer. |
|_______________|_____________________|_______________________________|
| align |Align | Specifies the alignment of the|
| | | call timer. |
|_______________|_____________________|_______________________________|
The <time> tag is used to display the current time on the phone.
<time>标签用于显示手机上的当前时间。
This tag has the following attributes:
_______________ _____________________ _______________________________
|Attribute Name | Values | Usage |
|_______________|_____________________|_______________________________|
| align | Align | Specifies the alignment of the|
| | | time. |
|_______________|_____________________|_______________________________|
This tag has the following attributes:
_______________ _____________________ _______________________________
|Attribute Name | Values | Usage |
|_______________|_____________________|_______________________________|
| align | Align | Specifies the alignment of the|
| | | time. |
|_______________|_____________________|_______________________________|
The <timer> tag is used to define a timeout for the card. When the timeout occurs, the XML Layer looks for the appropriate <do> tag to take appropriate action.
<timer>标记用于定义卡的超时。当超时发生时，XML层寻找适当的<do>标记以采取适当的操作。
This tag has the following attributes:
_______________ _____________________ _______________________________
|Attribute Name | Values | Usage |
|_______________|_____________________|_______________________________|
| Value | Time | Specifies the initial value of|
| | | the timer. The timer will |
| | | decrement the time until it |
| | | reaches zero at which point |
| | | the <do> tag is consulted. |
|_______________|_____________________|_______________________________|
This tag has the following attributes:
_______________ _____________________ _______________________________
|Attribute Name | Values | Usage |
|_______________|_____________________|_______________________________|
| Value | Time | Specifies the initial value of|
| | | the timer. The timer will |
| | | decrement the time until it |
| | | reaches zero at which point |
| | | the <do> tag is consulted. |
|_______________|_____________________|_______________________________|
The <do> tag indicates an action to be performed when the specified event occurs.
<do>标记表示发生指定事件时要执行的操作。
Currently, the <do> tag can process three events: prev, ontimer and accept. The prev event indicates that the user has requested to cancel the current card.
目前，<do>标记可以处理三个事件：prev、ontimer和accept。prev事件表示用户已请求取消当前卡。
The ontimer event indicates that the timer defined using the <timer> tag has expired.
ontimer事件表示使用<timer>标记定义的计时器已过期。
The accept event indicates that the user has completed inputting from the keypad.
accept事件表示用户已完成键盘输入。
This tag has the following attributes:
_______________ _____________________ _______________________________
|Attribute Name | Values (default) | Usage |
|_______________|_____________________|_______________________________|
|Type | Enum: | Indicates the event on which |
| | prev/ontimer/accept | the tag operates. |
|_______________|_____________________|_______________________________|
This tag has the following attributes:
_______________ _____________________ _______________________________
|Attribute Name | Values (default) | Usage |
|_______________|_____________________|_______________________________|
|Type | Enum: | Indicates the event on which |
| | prev/ontimer/accept | the tag operates. |
|_______________|_____________________|_______________________________|
The <go> tag is used in conjunction with the <do> tag to specify a URL to be loaded when the event occurs.
<go>标记与<do>标记一起用于指定事件发生时要加载的URL。
This tag has the following attributes:
_______________ _____________________ _______________________________
|Attribute Name | Values (default) | Usage |
|_______________|_____________________|_______________________________|
| href | URL | Defines the URL of the next |
| | | XML page. |
|_______________|_____________________|_______________________________|
This tag has the following attributes:
_______________ _____________________ _______________________________
|Attribute Name | Values (default) | Usage |
|_______________|_____________________|_______________________________|
| href | URL | Defines the URL of the next |
| | | XML page. |
|_______________|_____________________|_______________________________|
The <prev> tag is used in conjunction with the <do> tag to indicate that the previous page in the display history should be rendered.
<prev>标记与<do>标记一起使用，以指示应呈现显示历史中的上一页。
This tag has no attributes.
此标记没有属性。
This extension introduces no new security considerations beyond those discussed in RFC 2705 [1].
除了RFC 2705[1]中讨论的内容外，此扩展没有引入任何新的安全注意事项。
Thanks to the following companies and individuals for contributing their experience and thoughts for inclusion in this document.
感谢以下公司和个人为本文件提供经验和想法。
Arnie Chencinski, Sylantro Systems Bill Foster, Cisco Systems Howard Holgate, Cisco Systems John Weald, Sylantro Systems Michael Chack, Sylantro Systems Naga Surendran, Sylantro Systems Sunil Veluvali, Sylantro Systems
Arnie Chencinski、Sylantro Systems Bill Foster、Cisco Systems Howard Holgate、Cisco Systems John Weald、Sylantro Systems Michael Chack、Sylantro Systems Naga Surendran、Sylantro Systems Sunil Veluvali、Sylantro Systems
[1] Arango, M., Dugan A., Elliot, I., Huitema, C. and S. Pickett, "Media Gateway Control Protocol (MGCP)" RFC 2705, October 1999.
[1] Arango，M.，Dugan A.，Elliot，I.，Huitema，C.和S.Pickett，“媒体网关控制协议（MGCP）”，RFC 27052999年10月。
[2] Bray, T., Paoli, J. and C. Sperberg-McQueen, "Extensible Markup Language (XML) 1.0", W3C Proposed Recommendation, February 10, 1998.
[2] Bray，T.，Paoli，J.和C.Sperberg McQueen，“可扩展标记语言（XML）1.0”，W3C建议，1998年2月10日。
[3] "Wireless Application Protocol Wireless Markup Language Specification Version 1.2", WAP Forum, November 1999.
[3] “无线应用协议无线标记语言规范1.2版”，WAP论坛，1999年11月。
Ashok Srinath Sylantro Systems 910 E. Hamilton Avenue Campbell, Ca. 95008
Ashok Srinath Sylantro Systems加利福尼亚州坎贝尔汉密尔顿大道东910号，邮编95008
EMail: Ashok.Srinath@sylantro.com
EMail: Ashok.Srinath@sylantro.com
Gil Levendel Sylantro Systems 910 E. Hamilton Avenue Campbell, Ca. 95008
Gil Levendel Sylantro Systems加利福尼亚州坎贝尔汉密尔顿大道东910号，邮编95008
EMail: Gil.Levendel@sylantro.com
EMail: Gil.Levendel@sylantro.com
Kent Fritz Sylantro Systems 910 E. Hamilton Avenue Campbell, Ca. 95008
肯特·弗里茨·西兰特罗系统公司，加利福尼亚州坎贝尔汉密尔顿大道东910号，邮编95008
EMail: Kent.Fritz@sylantro.com
EMail: Kent.Fritz@sylantro.com
Raghuraman Kalyanaram Wipro Systems Keonics Electronic City Hosur Road, Bangalore-561 229, India
Raghuraman Kalyanaram Wipro Systems Keonics电子城Hosur路，班加罗尔-561 229，印度
EMail: Raghuraman.Kal@wipro.com
EMail: Raghuraman.Kal@wipro.com
Appendix A: BNF description of XML grammar
附录A:XML语法的BNF描述
The parser is case sensitive. In this section we will use the following conventions:
解析器区分大小写。在本节中，我们将使用以下约定：
1. Small letters means terminals. 2. Capital strings are non-terminals. 3. [A | B] means either A or B must appear in this place. 4. \t, \n, \r, blank space are separators.
1. 小写字母表示终端。2.大写字符串是非终结符。3.[A | B]表示A或B必须出现在此处。4. \t、 \n\r，空格是分隔符。
______________ _ ____________________________________________________
|ACTION |:|<go href="HREFSTRING"/> | <prev/> |
|______________|_|____________________________________________________|
|ALIGN |:|Align=["left" | "right" ] |
|______________|_|____________________________________________________|
|CALLTIMER |:|<calltimer CALLTIMERATTRS/> |
|______________|_|____________________________________________________|
|CALLTIMERATTRS|:|CALLTIMERATTR | CALLTIMERATTR CALLTIMERATTRS |
|______________|_|____________________________________________________|
|CALLTIMERATTR |:|value=STRING | ALIGN |
|______________|_|____________________________________________________|
|CARDS |:|CARD | CARD CARDS |
|______________|_|____________________________________________________|
|CARD |:|<card id=STRING> CLUSTERS </card> |
|______________|_|____________________________________________________|
|CARDREFERENCE |:|#STRING |
|______________|_|____________________________________________________|
|CLUSTERS |:|CLUSTER | CLUSTER CLUSTERS |
|______________|_|____________________________________________________|
|CLUSTER |:|CONTROL | TIMER | ECHO | PARAGRAPH COMPONENTS </p> |
|______________|_|____________________________________________________|
|COMPONENTS |:|COMPONENT | COMPONENT COMPONENTS |
|______________|_|____________________________________________________|
|COMPONENT |:|TEXT | INPUTBOX | SELECTBOX | STIME | CALLTIMER |
|______________|_|____________________________________________________|
|CONTROL |:|<do CONDITION> ACTION </do> |
|______________|_|____________________________________________________|
|CONDITION | |type=["accept" | "prev" | "ontimer"] label=STRING | |
| | |type=["accept" | "prev" |"ontimer"] |
|______________|_|____________________________________________________|
|DIGITS |:|DIGIT | DIGIT DIGITS |
|______________|_|____________________________________________________|
|DIGIT |:|0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 |
|______________|_|____________________________________________________|
|DECK |:|<xml id=STRING> CARDS </xml> |
|______________|_|____________________________________________________|
|ECHO |:|<echo/> | <echo ECHOMODE/> |
|______________|_|____________________________________________________|
______________ _ ____________________________________________________
|ACTION |:|<go href="HREFSTRING"/> | <prev/> |
|______________|_|____________________________________________________|
|ALIGN |:|Align=["left" | "right" ] |
|______________|_|____________________________________________________|
|CALLTIMER |:|<calltimer CALLTIMERATTRS/> |
|______________|_|____________________________________________________|
|CALLTIMERATTRS|:|CALLTIMERATTR | CALLTIMERATTR CALLTIMERATTRS |
|______________|_|____________________________________________________|
|CALLTIMERATTR |:|value=STRING | ALIGN |
|______________|_|____________________________________________________|
|CARDS |:|CARD | CARD CARDS |
|______________|_|____________________________________________________|
|CARD |:|<card id=STRING> CLUSTERS </card> |
|______________|_|____________________________________________________|
|CARDREFERENCE |:|#STRING |
|______________|_|____________________________________________________|
|CLUSTERS |:|CLUSTER | CLUSTER CLUSTERS |
|______________|_|____________________________________________________|
|CLUSTER |:|CONTROL | TIMER | ECHO | PARAGRAPH COMPONENTS </p> |
|______________|_|____________________________________________________|
|COMPONENTS |:|COMPONENT | COMPONENT COMPONENTS |
|______________|_|____________________________________________________|
|COMPONENT |:|TEXT | INPUTBOX | SELECTBOX | STIME | CALLTIMER |
|______________|_|____________________________________________________|
|CONTROL |:|<do CONDITION> ACTION </do> |
|______________|_|____________________________________________________|
|CONDITION | |type=["accept" | "prev" | "ontimer"] label=STRING | |
| | |type=["accept" | "prev" |"ontimer"] |
|______________|_|____________________________________________________|
|DIGITS |:|DIGIT | DIGIT DIGITS |
|______________|_|____________________________________________________|
|DIGIT |:|0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 |
|______________|_|____________________________________________________|
|DECK |:|<xml id=STRING> CARDS </xml> |
|______________|_|____________________________________________________|
|ECHO |:|<echo/> | <echo ECHOMODE/> |
|______________|_|____________________________________________________|
|ECHOMODE |:|mode=["on" | "off"] |
|______________|_|____________________________________________________|
|HREFSTRING |:|CARDREFERENCE | POSTSTRING |
|______________|_|____________________________________________________|
|INPUTBOX |:|<input INPUTATTRS/> |
|______________|_|____________________________________________________|
|INPUTATTRS |:|INPUTATTR | INPUTATTR INPUTATTRS |
|______________|_|____________________________________________________|
|INPUTATTR |:|name=STRING | type=["text" | "password"] | |
| | | value=STRING |
|______________|_|____________________________________________________|
|NAMEVALUES |:|NAMEVALUE | NAMEVALUE?NAMEVALUES |
|______________|_|____________________________________________________|
|NAMEVALUE |:|NAMEVALUEELEM | NAMEVALUEELEM=NAMEVALUELEM |
|______________|_|____________________________________________________|
|NAMEVALUELEM |:|%TEXT | TEXT |
|______________|_|____________________________________________________|
|OPTIONS |:|OPTION | OPTION OPTIONS |
|______________|_|____________________________________________________|
|OPTION |:|<option value=STRING onpick=HREFSTRING> TEXT |
| | | </option> |
|______________|_|____________________________________________________|
|PARAGRAPH |:|<p TXTFORMAT> | <p> |
|______________|_|____________________________________________________|
|POSTSTRING |:|post?%deck?%id?NAMEVALUES | post?NAMEVALUES |
|______________|_|____________________________________________________|
|SELECTBOX |:|<select SELECTATTRS> OPTIONS </select> |
|______________|_|____________________________________________________|
|SELECTATTRS |:|SELECTATTR | SELECTATTR SELECTATTRS |
|______________|_|____________________________________________________|
|SELECTATTR |:|name=STRING | iname=STRING | type="item" |
|______________|_|____________________________________________________|
|STIME |:|<time STIMEATTRS/> |
|______________|_|____________________________________________________|
|STIMEATTRS |:|STIMEATTR | STIMEATTR STIMEATTRS |
|______________|_|____________________________________________________|
|STIMEATTR |:|value=STRING | format=STRING | ALIGN |
|______________|_|____________________________________________________|
|STRING |:|Any string enclosed in a pair of quotes ("") |
|______________|_|____________________________________________________|
|TEXT |:|TEXTELEM | TEXTELEM TEXT |
|______________|_|____________________________________________________|
|TEXTELEM |:|any string outside of the < .. > and which consists |
| | |of any symbols except '<' and '\n' |
|______________|_|____________________________________________________|
|TIMER |:|<timer value="DIGITS"/> |
|______________|_|____________________________________________________|
|ECHOMODE |:|mode=["on" | "off"] |
|______________|_|____________________________________________________|
|HREFSTRING |:|CARDREFERENCE | POSTSTRING |
|______________|_|____________________________________________________|
|INPUTBOX |:|<input INPUTATTRS/> |
|______________|_|____________________________________________________|
|INPUTATTRS |:|INPUTATTR | INPUTATTR INPUTATTRS |
|______________|_|____________________________________________________|
|INPUTATTR |:|name=STRING | type=["text" | "password"] | |
| | | value=STRING |
|______________|_|____________________________________________________|
|NAMEVALUES |:|NAMEVALUE | NAMEVALUE?NAMEVALUES |
|______________|_|____________________________________________________|
|NAMEVALUE |:|NAMEVALUEELEM | NAMEVALUEELEM=NAMEVALUELEM |
|______________|_|____________________________________________________|
|NAMEVALUELEM |:|%TEXT | TEXT |
|______________|_|____________________________________________________|
|OPTIONS |:|OPTION | OPTION OPTIONS |
|______________|_|____________________________________________________|
|OPTION |:|<option value=STRING onpick=HREFSTRING> TEXT |
| | | </option> |
|______________|_|____________________________________________________|
|PARAGRAPH |:|<p TXTFORMAT> | <p> |
|______________|_|____________________________________________________|
|POSTSTRING |:|post?%deck?%id?NAMEVALUES | post?NAMEVALUES |
|______________|_|____________________________________________________|
|SELECTBOX |:|<select SELECTATTRS> OPTIONS </select> |
|______________|_|____________________________________________________|
|SELECTATTRS |:|SELECTATTR | SELECTATTR SELECTATTRS |
|______________|_|____________________________________________________|
|SELECTATTR |:|name=STRING | iname=STRING | type="item" |
|______________|_|____________________________________________________|
|STIME |:|<time STIMEATTRS/> |
|______________|_|____________________________________________________|
|STIMEATTRS |:|STIMEATTR | STIMEATTR STIMEATTRS |
|______________|_|____________________________________________________|
|STIMEATTR |:|value=STRING | format=STRING | ALIGN |
|______________|_|____________________________________________________|
|STRING |:|Any string enclosed in a pair of quotes ("") |
|______________|_|____________________________________________________|
|TEXT |:|TEXTELEM | TEXTELEM TEXT |
|______________|_|____________________________________________________|
|TEXTELEM |:|any string outside of the < .. > and which consists |
| | |of any symbols except '<' and '\n' |
|______________|_|____________________________________________________|
|TIMER |:|<timer value="DIGITS"/> |
|______________|_|____________________________________________________|
|TXTFORMAT |:|ALIGN | TXTMODE | ALIGN TXTMODE | TXTMODE ALIGN |
|______________|_|____________________________________________________|
|TXTMODE |:|mode=["wrap" | "nowrap"] |
|______________|_|____________________________________________________|
|TXTFORMAT |:|ALIGN | TXTMODE | ALIGN TXTMODE | TXTMODE ALIGN |
|______________|_|____________________________________________________|
|TXTMODE |:|mode=["wrap" | "nowrap"] |
|______________|_|____________________________________________________|
______________ _ ____________________________________________________
| | |\t, \n, \r, blank space are separators. |
|______________|_|____________________________________________________|
______________ _ ____________________________________________________
| | |\t, \n, \r, blank space are separators. |
|______________|_|____________________________________________________|
Appendix B: Sample XML Documents, Renderings and Events
附录B：示例XML文档、渲染和事件
This section presents some sample XML documents and details how they are translated to a business phone with a simple LCD display.
本节介绍一些示例XML文档，并详细介绍如何将它们转换为带有简单LCD显示屏的商务电话。
Below is a simple deck containing one card that defines a simple main menu interface using an itemized list box:
下面是一个简单的卡片组，其中包含一张卡片，该卡片使用逐项列表框定义了一个简单的主菜单界面：
<xml>
<card id="home">
<p mode="nowrap">$dn <time align="right"></time>
<select type="item" name="Menu" iname="StrMenu">
<option value="1" onpick="post?%deck?%id?%name=%value">MENU</option>
</select>
</p>
</card>
</xml>
<xml>
<card id="home">
<p mode="nowrap">$dn <time align="right"></time>
<select type="item" name="Menu" iname="StrMenu">
<option value="1" onpick="post?%deck?%id?%name=%value">MENU</option>
</select>
</p>
</card>
</xml>
The card (home) contains three components:
卡（主卡）包含三个组件：
1. A paragraph (<p>). The paragraph contains a variable ($dn) that shows the phone's extension. 2. A clock (<time>). The clock is aligned to the right. 3. An itemized list (<select>) containing one item (MENU).
1. 一段（<p>）。该段落包含一个变量（$dn），显示手机的分机。2.时钟（<time>）。时钟向右对齐。3.包含一项（菜单）的逐项列表（<select>）。
An XML request for this deck and card might look like:
此卡片组和卡片的XML请求可能如下所示：
S: XML/xml(deck?home?$dn=2344)
S: XML/xml(deck?home?$dn=2344)
After variable substitution, the phone may render the XML to the display as follows:
变量替换后，手机可能会将XML呈现到显示屏上，如下所示：
--------------------
|2344 11:59|
| MENU |
--------------------
[XX] [XX] [XX]
--------------------
|2344 11:59|
| MENU |
--------------------
[XX] [XX] [XX]
Here, MENU maps to the first soft key below the display. If the user presses the first soft key, the following event will be generated:
此处，菜单映射到显示屏下方的第一个软键。如果用户按下第一个软键，将生成以下事件：
O: XML/xml(post?basic?home?Menu=1).
O:XML/XML（post基本主菜单=1）。
The next sample deck defines a simple enumerated list box card:
下一个示例组定义了一个简单的枚举列表框卡：
<xml>
<card id="gelist">
<p>$title
<select name="x-name" iname="x-iname">
<option value="$value1"
onpick="post?%deck?%id?%name=%value?%iname=%x-iname">$opt1
</option>
<option value="$value2"
onpick="post?%deck?%id?%name=%value?%iname=%x-iname">$opt2
</option>
<option value="$value3"
onpick="post?%deck?%id?%name=%value?%iname=%x-iname">$opt3
</option>
<option value="$value4"
onpick="post?%deck?%id?%name=%value?%iname=%x-iname">$opt4
</option>
<option value="$value5"
onpick="post?%deck?%id?%name=%value?%iname=%x-iname">$opt5
</option>
</select>
</p>
<do type="prev">
<prev></prev>
</do>
</card>
</xml>
<xml>
<card id="gelist">
<p>$title
<select name="x-name" iname="x-iname">
<option value="$value1"
onpick="post?%deck?%id?%name=%value?%iname=%x-iname">$opt1
</option>
<option value="$value2"
onpick="post?%deck?%id?%name=%value?%iname=%x-iname">$opt2
</option>
<option value="$value3"
onpick="post?%deck?%id?%name=%value?%iname=%x-iname">$opt3
</option>
<option value="$value4"
onpick="post?%deck?%id?%name=%value?%iname=%x-iname">$opt4
</option>
<option value="$value5"
onpick="post?%deck?%id?%name=%value?%iname=%x-iname">$opt5
</option>
</select>
</p>
<do type="prev">
<prev></prev>
</do>
</card>
</xml>
The card (gelist) contains four components:
卡（gelist）包含四个组件：
1. A paragraph (<p>). The paragraph contains a title variable describing the list contents. 2. An enumerated list (<select>) containing five items. When an item is selected, the XML layer sends the XML/xml event to the Call Agent. 3. A do tag (<do>) indicating that when a "previous" event has occurred, to go to the previous page (<prev>).
1. 一段（<p>）。段落包含描述列表内容的标题变量。2.包含五项的枚举列表（<select>）。当选择一个项目时，XML层将XML/XML事件发送给调用代理。3.一个do标记（<do>），指示当发生“上一个”事件时，转到上一页（<prev>）。
An XML request for this deck and card might look like:
此卡片组和卡片的XML请求可能如下所示：
S: XML/xml(list?gelist?$title=Select a Car?
$value1=Item1?$opt1=Porsche?
$value2=Item2?$opt2=Chevrolet?
$value3=Item3?$opt3=Toyota?
$value4=Item4?$opt4=Daewoo?
$value5=Item5?$opt5=Yugo)
S: XML/xml(list?gelist?$title=Select a Car?
$value1=Item1?$opt1=Porsche?
$value2=Item2?$opt2=Chevrolet?
$value3=Item3?$opt3=Toyota?
$value4=Item4?$opt4=Daewoo?
$value5=Item5?$opt5=Yugo)
After variable substitution, the phone may render the XML to the display as follows:
变量替换后，手机可能会将XML呈现到显示屏上，如下所示：
--------------------
|SELECT A CAR |
|1. Porsche v|
--------------------
[XX] [XX] [XX]
--------------------
|SELECT A CAR |
|1. Porsche v|
--------------------
[XX] [XX] [XX]
Here, the display may be scrolled to reveal the additional items that may be selected and the keypad '1', '2', etc may be used to select the item. These details are phone-specific. For instance, on a larger 4-line display containing navigation keys, the XML may be rendered as follows:
此处，可滚动显示屏以显示可选择的其他项目，并可使用键盘“1”、“2”等选择项目。这些细节是特定于电话的。例如，在包含导航键的较大的4行显示器上，XML可能呈现如下：
--------------------
|SELECT A CAR |
|=>Porsche<= |
| Chevrolet |
| Toyota v|
--------------------
--------------------
|SELECT A CAR |
|=>Porsche<= |
| Chevrolet |
| Toyota v|
--------------------
When the user selects item 1, the following message will be sent to the Call Agent:
当用户选择项目1时，将向呼叫代理发送以下消息：
O: XML/xml(post?list?gelist?x-name=Item1?x-iname=1)
O: XML/xml(post?list?gelist?x-name=Item1?x-iname=1)
This sample shows how to implement a simple text box:
此示例演示如何实现一个简单的文本框：
<xml>
<card id="generic">
<p>$cldpty</p>
<p>CALL FAILED</p>
</card>
</xml>
<xml>
<card id="generic">
<p>$cldpty</p>
<p>CALL FAILED</p>
</card>
</xml>
The card (generic) contains two paragraphs. The absence of a selectable list, input box or echo box indicates that this is a text box.
卡片（通用）包含两个段落。缺少可选列表、输入框或回显框表示这是一个文本框。
An XML request for this deck and card might look like:
此卡片组和卡片的XML请求可能如下所示：
S: XML/xml(deck?generic?$cldpty=John Doe)
S: XML/xml(deck?generic?$cldpty=John Doe)
After variable substitution, the phone may render the XML to the display as follows:
变量替换后，手机可能会将XML呈现到显示屏上，如下所示：
--------------------
|JOHN DOE |
|CALL FAILED |
--------------------
[XX] [XX] [XX]
--------------------
|JOHN DOE |
|CALL FAILED |
--------------------
[XX] [XX] [XX]
This sample show how to implement a simple echo box. The XML layer does not consume any keystrokes.
此示例演示如何实现一个简单的回显框。XML层不使用任何击键。
<xml>
<card id="getdigits">
<p>Dial Number:</p>
<echo mode="$mode" align="left"/>
</card>
</xml>
<xml>
<card id="getdigits">
<p>Dial Number:</p>
<echo mode="$mode" align="left"/>
</card>
</xml>
The card (getdigits) contains a paragraph of text and an echo box.
卡片（getdigits）包含一段文本和一个回音框。
An XML request for this deck and card might look like:
此卡片组和卡片的XML请求可能如下所示：
S: XML/xml(deck?getdigits?$mode=on)
S: XML/xml(deck?getdigits?$mode=on)
After variable substitution, the phone may render the XML to the display as follows:
变量替换后，手机可能会将XML呈现到显示屏上，如下所示：
--------------------
|DIAL NUMBER: |
| |
--------------------
[XX] [XX] [XX]
--------------------
|DIAL NUMBER: |
| |
--------------------
[XX] [XX] [XX]
All user input is displayed but not consumed by the XML layer.
显示所有用户输入，但不被XML层使用。
This sample implements a basic input box:
此示例实现了一个基本输入框：
<xml>
<card id="ginput">
<p>$title
<input name="x-name"/>
</p>
<do type="accept">
<go href="post?%deck?%id?%name=%value"/>
</do>
<do type="prev">
<prev></prev>
</do>
</card>
</xml>
<xml>
<card id="ginput">
<p>$title
<input name="x-name"/>
</p>
<do type="accept">
<go href="post?%deck?%id?%name=%value"/>
</do>
<do type="prev">
<prev></prev>
</do>
</card>
</xml>
The card (ginput) contains:
该卡（ginput）包含：
1. A paragraph <p>. The paragraph contains a title. 2. An input box <input>. The input box consumes keypad events and reports them when input is complete. 3. Two event handlers <do>. The first handles the accept event. This event indicates that the user has completed keypad input and posts an observed event to the Call Agent. The second handles the prev event. This event indicates that the user has requested to revert back to the previous card.
1. 段落<p>。该段包含一个标题。2.一个输入框<input>。输入框使用键盘事件，并在输入完成时报告这些事件。3.两个事件处理程序<do>。第一个处理accept事件。此事件表示用户已完成键盘输入，并向呼叫代理发送观察到的事件。第二个处理prev事件。此事件表示用户已请求恢复到以前的卡。
An XML request for this deck and card might look like:
此卡片组和卡片的XML请求可能如下所示：
S: XML/xml(deck?ginput?$title=Enter Digits:)
S:XML/XML（deck？ginput？$title=输入数字：）
After variable substitution, the phone may render the XML to the display as follows:
变量替换后，手机可能会将XML呈现到显示屏上，如下所示：
--------------------
|ENTER DIGITS: |
|_ |
--------------------
[XX] [XX] [XX]
--------------------
|ENTER DIGITS: |
|_ |
--------------------
[XX] [XX] [XX]
It is up to the individual business phone implementation to determine which soft keys or keypad keys map to functions such as "backspace", "reset line", etc.
由个人商务电话实现来确定哪些软键或键盘键映射到诸如“退格”、“重设行”等功能。
To illustrate timers and deck-scoped variable substitution, a two-card deck is provided:
为了说明计时器和组作用域变量替换，提供了一个双卡组：
<xml>
<card id="connected1">
<timer value="$tvalue"/>
<p mode="nowrap">$cldpty
<select type="item" name="x-name" iname="x-iname">
<option value="1"
onpick="post?TRNSINIT">TRNS
</option>
<option value="2"
onpick="post?CONFINIT">CONF
</option>
<option value="3"
onpick="post?%deck?%card?%name=%value">MENU
</option>
</select>
</p>
<do type="ontimer">
<go href="#connected2"/>
</do>
</card>
<xml>
<card id="connected1">
<timer value="$tvalue"/>
<p mode="nowrap">$cldpty
<select type="item" name="x-name" iname="x-iname">
<option value="1"
onpick="post?TRNSINIT">TRNS
</option>
<option value="2"
onpick="post?CONFINIT">CONF
</option>
<option value="3"
onpick="post?%deck?%card?%name=%value">MENU
</option>
</select>
</p>
<do type="ontimer">
<go href="#connected2"/>
</do>
</card>
<card id="connected2">
<p mode="nowrap">
<calltimer value="$calltimer" align="right"/>
<select type="item" name="x-name">
<option value="1"
onpick="post?TRNSINIT">TRNS
</option>
<option value="2"
onpick="post?CONFINIT">CONF
</option>
<option value="3"
onpick="post?%deck?%card?%name=%value" >MENU
</option>
</select>
</p>
</card>
</xml>
<card id="connected2">
<p mode="nowrap">
<calltimer value="$calltimer" align="right"/>
<select type="item" name="x-name">
<option value="1"
onpick="post?TRNSINIT">TRNS
</option>
<option value="2"
onpick="post?CONFINIT">CONF
</option>
<option value="3"
onpick="post?%deck?%card?%name=%value" >MENU
</option>
</select>
</p>
</card>
</xml>
In this example, when the timer expires in card connected1, it generates an ontimer event. This event is consumed by the <do> tag and causes the XML layer to load card with the identifier connected2.
在本例中，当卡connected1中的计时器过期时，它会生成ontimer事件。此事件由<do>标记使用，并导致XML层加载标识符为connected2的卡。
An XML request for these cards might look like:
对这些卡的XML请求可能如下所示：
S: XML/xml(deck?connected1?$tvalue=00:00:05?$cldpty=John
Doe?$calltimer=00:00:00)
S: XML/xml(deck?connected1?$tvalue=00:00:05?$cldpty=John
Doe?$calltimer=00:00:00)
And might be rendered as:
并可能被呈现为：
--------------------
|JOHN DOE |
| TRNS CONF MENU |
--------------------
[XX] [XX] [XX]
--------------------
|JOHN DOE |
| TRNS CONF MENU |
--------------------
[XX] [XX] [XX]
Once the timer expires, the XML layer loads the referenced page:
计时器过期后，XML层将加载引用的页面：
--------------------
| 00:00:05|
| TRNS CONF MENU |
--------------------
[XX] [XX] [XX]
--------------------
| 00:00:05|
| TRNS CONF MENU |
--------------------
[XX] [XX] [XX]
Appendix C: Example usage of MGCP extension packages
附录C：MGCP扩展包的使用示例
Step 1. Call Agent sets labels on several used keys. Should be done at startup. The first 2 keys are line appearance keys. fk8 is a Do Not Disturb function.
第一步。呼叫代理在几个使用过的键上设置标签。应该在启动时完成。前两个关键点是线条外观关键点。fk8是一种请勿打扰功能。
RQNT 1876 d003@da-003.syltrx.com MGCP 1.0
N: cs@sage.syltrx.com:2427
X: 45
S: KY/ls(1,2315), KY/ls(2,2315), KY/ls(8,DND)
R: KY/fk1, KY/fk2, KY/fk8, KY/fk22, KY/fk23, L/hd
T: L/hu
K: 1873
RQNT 1876 d003@da-003.syltrx.com MGCP 1.0
N: cs@sage.syltrx.com:2427
X: 45
S: KY/ls(1,2315), KY/ls(2,2315), KY/ls(8,DND)
R: KY/fk1, KY/fk2, KY/fk8, KY/fk22, KY/fk23, L/hd
T: L/hu
K: 1873
Step 2. Gateway responds.
第二步。网关响应。
200 1876 OK
2001876行
This example shows a feature key that is assigned to "Do Not Disturb" being activated and deactivated.
此示例显示了一个被指定为“请勿打扰”的功能键被激活和停用。
Step 1. User presses DND key, which is assigned to fk8. Gateway sends NTFY to Call Agent.
第一步。用户按下指定给fk8的DND键。网关向呼叫代理发送NTFY。
NTFY 957 d003@da-003.syltrx.com MGCP 1.0
K: 956
N: cs@sage.syltrx.com:2427
X: 45
O: KY/fk8
NTFY 957 d003@da-003.syltrx.com MGCP 1.0
K: 956
N: cs@sage.syltrx.com:2427
X: 45
O: KY/fk8
Step 2. Call Agent responds.
第二步。呼叫代理回应。
200 957 OK
200957好
Step 3. Call Agent sends new RQNT, indicating that DND indicator be activated. Note that the Call Agent also re-sends the state of fk1, which is not actually necessary. The Call Agent requests notification of several of the feature keys: fk1 and fk2 are line keys, fk8 is DND, fk22 is redial, and fk23 is messages.
第三步。呼叫代理发送新的RQNT，指示DND指示灯被激活。请注意，呼叫代理还重新发送fk1的状态，这实际上不是必需的。呼叫代理请求通知几个功能键：fk1和fk2是线路键，fk8是DND，fk22是重拨，fk23是消息。
RQNT 2822 d003@da-003.syltrx.com MGCP 1.0
N: cs@sage.syltrx.com:2427
X: 45
S: KY/ks(1,id), KY/ks(8,en)
R: KY/fk1, KY/fk2, KY/fk8, KY/fk22, KY/fk23, L/hd
T: L/hu
K: 2743-2744
RQNT 2822 d003@da-003.syltrx.com MGCP 1.0
N: cs@sage.syltrx.com:2427
X: 45
S: KY/ks(1,id), KY/ks(8,en)
R: KY/fk1, KY/fk2, KY/fk8, KY/fk22, KY/fk23, L/hd
T: L/hu
K: 2743-2744
Step 4. Gateway responds.
第四步。网关响应。
200 2822 OK
2002822好的
Step 5. User presses DND key again to de-activate DND. Gateway sends NTFY to Call Agent.
第五步。用户再次按下DND键以取消激活DND。网关向呼叫代理发送NTFY。
NTFY 958 d003@da-003.syltrx.com MGCP 1.0
K: 957
N: cs@sage.syltrx.com:2427
X: 45
O: KY/fk8
NTFY 958 d003@da-003.syltrx.com MGCP 1.0
K: 957
N: cs@sage.syltrx.com:2427
X: 45
O: KY/fk8
Step 6. Call Agent responds.
第六步。呼叫代理回应。
200 958 OK
200958好
Step 7. Call Agent sends new RQNT, DND indicator is de-activated.
第七步。呼叫代理发送新的RQNT，DND指示灯停用。
RQNT 2823 d003@da-003.syltrx.com MGCP 1.0
N: cs@sage.syltrx.com:2427
X: 45
S: KY/ks(1,id), KY/ks(8,db)
R: KY/fk1, KY/fk2, KY/fk8, KY/fk22, KY/fk23, L/hd
T: L/hu
K: 2822
RQNT 2823 d003@da-003.syltrx.com MGCP 1.0
N: cs@sage.syltrx.com:2427
X: 45
S: KY/ks(1,id), KY/ks(8,db)
R: KY/fk1, KY/fk2, KY/fk8, KY/fk22, KY/fk23, L/hd
T: L/hu
K: 2822
Step 8. Gateway responds.
第八步。网关响应。
200 2823 OK
2002823好
This example shows the MGCP messages for dialing an extension after pressing a feature key that is configured as a line appearance key.
此示例显示在按下配置为线路外观键的功能键后拨打分机的MGCP消息。
Step 1. User presses fk1, which is configured as a line key.
第一步。用户按fk1键，该键配置为行键。
NTFY 959 d003@da-003.syltrx.com MGCP 1.0
K: 958
N: cs@sage.syltrx.com:2427
X: 45
O: KY/fk1
NTFY 959 d003@da-003.syltrx.com MGCP 1.0
K: 958
N: cs@sage.syltrx.com:2427
X: 45
O: KY/fk1
Step 2. Call Agent responds.
第二步。呼叫代理回应。
200 959 OK
200959好
Step 3. Call Agent puts the line key in the "dial tone" state and forces the phone offhook.
第三步。呼叫代理将线路键置于“拨号音”状态，并强制手机脱离连接。
RQNT 2833 d003@da-003.syltrx.com MGCP 1.0
N: cs@sage.syltrx.com:2427
RQNT 2833 d003@da-003.syltrx.com MGCP 1.0
N: cs@sage.syltrx.com:2427
X: 45
S: KY/ks(1,dt), BP/hd
R: KY/fk1, KY/fk2, KY/fk8, KY/fk22, KY/fk23, L/hu
T: L/hd
K: 2823
X: 45
S: KY/ks(1,dt), BP/hd
R: KY/fk1, KY/fk2, KY/fk8, KY/fk22, KY/fk23, L/hu
T: L/hd
K: 2823
Step 4. Gateway responds.
第四步。网关响应。
200 2833 OK
2002833好
Step 5. Call Agent applies dial-tone.
第五步。呼叫代理应用拨号音。
RQNT 2834 d003@da-003.syltrx.com MGCP 1.0
N: cs@sage.syltrx.com:2427
X: 45
S: L/dl, KY/ks(1,dt)
R: D/[0-9*#T](D), KY/fk1, KY/fk2, KY/fk8, KY/fk22, KY/fk23, L/hu
T: L/hd
D: (*xx|[1-7]xxx|9)
RQNT 2834 d003@da-003.syltrx.com MGCP 1.0
N: cs@sage.syltrx.com:2427
X: 45
S: L/dl, KY/ks(1,dt)
R: D/[0-9*#T](D), KY/fk1, KY/fk2, KY/fk8, KY/fk22, KY/fk23, L/hu
T: L/hd
D: (*xx|[1-7]xxx|9)
Step 6. Gateway responds.
第六步。网关响应。
200 2834 OK
2002834好
Step 7. User dials 2362. Gateway sends NTFY.
第七步。用户拨打2362。网关发送NTFY。
NTFY 960 d003@da-003.syltrx.com MGCP 1.0
K: 959
N: cs@sage.syltrx.com:2427
X: 45
O: D/2,D/3,D/6,D/2
NTFY 960 d003@da-003.syltrx.com MGCP 1.0
K: 959
N: cs@sage.syltrx.com:2427
X: 45
O: D/2,D/3,D/6,D/2
Step 8. Call Agent responds.
第八步。呼叫代理回应。
200 960 OK
200960好
Step 9. Call Agent puts line in the ringback state. Ringback not applied yet.
第九步。呼叫代理将线路置于回铃状态。振铃尚未应用。
RQNT 2836 d003@da-003.syltrx.com MGCP 1.0
N: cs@sage.syltrx.com:2427
X: 45
S: KY/ks(1,rb)
R: KY/fk1, KY/fk2, KY/fk8, KY/fk22, KY/fk23, L/hu
T: L/hd
K: 2833, 2834
RQNT 2836 d003@da-003.syltrx.com MGCP 1.0
N: cs@sage.syltrx.com:2427
X: 45
S: KY/ks(1,rb)
R: KY/fk1, KY/fk2, KY/fk8, KY/fk22, KY/fk23, L/hu
T: L/hd
K: 2833, 2834
Step 10. Gateway responds.
第十步。网关响应。
200 2836 OK
2002836 OK
Step 11. Call Agent creates connection.
第11步。呼叫代理创建连接。
CRCX 2838 d003@da-003.syltrx.com MGCP 1.0 C: 10B M: RECVONLY
CRCX 2838d003@da-003.syltrx.com MGCP 1.0 C:10B M:RecvoOnly
Step 12. Gateway responds.
步骤12。网关响应。
200 2838 OK I: 101
2002838好的I:101
v=0
o=- 998557784 998557784 IN IP4 38.187.114.41
s=MGCP RTP Session
c=IN IP4 172.16.130.32
t=0 0
m=audio 1108 RTP/AVP 0
a=rtpmap:0 PCMU/8000
v=0
o=- 998557784 998557784 IN IP4 38.187.114.41
s=MGCP RTP Session
c=IN IP4 172.16.130.32
t=0 0
m=audio 1108 RTP/AVP 0
a=rtpmap:0 PCMU/8000
Step 13. Call Agent applies ringback.
步骤13。呼叫代理应用回拨。
RQNT 2841 d003@da-003.syltrx.com MGCP 1.0
N: cs@sage.syltrx.com:2427
X: 45
S: KY/ks(1,rb), G/rt
R: KY/fk1, KY/fk2, KY/fk8, KY/fk22, KY/fk23, L/hu
T: L/hd
RQNT 2841 d003@da-003.syltrx.com MGCP 1.0
N: cs@sage.syltrx.com:2427
X: 45
S: KY/ks(1,rb), G/rt
R: KY/fk1, KY/fk2, KY/fk8, KY/fk22, KY/fk23, L/hu
T: L/hd
Step 14. Gateway responds.
第14步。网关响应。
200 2841 OK
2002841好的
Step 15. Call Agent modifies connection.
第15步。呼叫代理修改连接。
MDCX 2848 d003@da-003.syltrx.com MGCP 1.0 C: 10B I: 101 M: SENDRECV K: 2841-2842
MDCX 2848d003@da-003.syltrx.com MGCP 1.0 C:10B I:101 M:SENDRECV K:2841-2842
v=0 o=- 7960 7960 IN IP4 38.187.114.215 s=MGCP Call c=IN IP4 172.16.130.31 t=0 0 m=audio 1124 RTP/AVP 0
v=0 o=-7960 7960在IP4 38.187.114.215中s=MGCP呼叫c=IP4 172.16.130.31中t=0 0 m=音频1124 RTP/AVP 0
Step 16. Gateway responds.
第16步。网关响应。
200 2848 OK
2002848好
Step 17. Call Agent puts line in connected state. Added requested events looking for hold (fk21) and conference/transfer (fk24).
第17步。呼叫代理将线路置于已连接状态。添加了请求的等待事件（fk21）和会议/传输事件（fk24）。
RQNT 2849 d003@da-003.syltrx.com MGCP 1.0
N: cs@sage.syltrx.com:2427
X: 45
S: KY/ks(1,cn)
R: KY/fk1, KY/fk2, KY/fk8, KY/fk21, KY/fk24, L/hu
T: L/hd
K: 2842
RQNT 2849 d003@da-003.syltrx.com MGCP 1.0
N: cs@sage.syltrx.com:2427
X: 45
S: KY/ks(1,cn)
R: KY/fk1, KY/fk2, KY/fk8, KY/fk21, KY/fk24, L/hu
T: L/hd
K: 2842
Step 18. Gateway responds.
第18步。网关响应。
200 2849 OK
2002849好
Step 19. Far end disconnects. Call Agent deletes connection.
第19步。远端断开连接。呼叫代理删除连接。
DLCX 2873 d003@da-003.syltrx.com MGCP 1.0 C: 10B I: 101 K: 2848, 2849
DLCX 2873d003@da-003.syltrx.com MGCP 1.0 C:10B I:101 K:28482849
Step 20. Gateway responds.
步骤20。网关响应。
250 2873 Connection Deleted
250 2873连接已删除
Step 21. Call Agent forces endpoint onhook/idle.
步骤21。调用代理强制端点挂起/空闲。
RQNT 2876 d003@da-003.syltrx.com MGCP 1.0
N: cs@sage.syltrx.com:2427
RQNT 2876 d003@da-003.syltrx.com MGCP 1.0
N: cs@sage.syltrx.com:2427
X: 45
S: KY/ks(1,id), BP/hu
R: KY/fk1, KY/fk2, KY/fk8, KY/fk22, KY/fk23, L/hd
T: L/hu
K: 2873
X: 45
S: KY/ks(1,id), BP/hu
R: KY/fk1, KY/fk2, KY/fk8, KY/fk22, KY/fk23, L/hd
T: L/hu
K: 2873
Step 22. Gateway responds.
步骤22。网关响应。
200 2876 OK
2002876好
Step 1. Gateway restarts.
第一步。网关重新启动。
RSIP 1 *@alpha175.sylantro.com MGCP 1.0 RM: restart
RSIP 1*@alpha175.sylantro.com MGCP 1.0 RM:重新启动
Step 2. Call Agent responds.
第二步。呼叫代理回应。
200 1 OK
200 1好的
Step 3. Call Agent audits the Gateway to determine list of endpoints
第三步。呼叫代理审核网关以确定端点列表
AUEP 1000 *@alpha175.sylantro.com MGCP 1.0
AUEP 1000*@alpha175.sylantro.com MGCP 1.0
Step 4. Gateway responds.
第四步。网关响应。
200 1000 OK
Z: a004@alpha175.sylantro.com
Z: d001@alpha175.sylantro.com
Z: d002@alpha175.sylantro.com
Z: d003@alpha175.sylantro.com
200 1000 OK
Z: a004@alpha175.sylantro.com
Z: d001@alpha175.sylantro.com
Z: d002@alpha175.sylantro.com
Z: d003@alpha175.sylantro.com
Step 5. For each endpoint, Call Agent determines capabilities and user-agent (phone-type)
第五步。对于每个端点，呼叫代理确定功能和用户代理（电话类型）
AUEP 1040 d003@alpha175.sylantro.com MGCP 1.0 K: 1039 F: A,X-UA
AUEP 1040d003@alpha175.sylantro.comMGCP 1.0 K:1039 F:A，X-UA
Step 6. Gateway responds.
第六步。网关响应。
200 1040 OK
A: v:D;L;KY;X-BP;G;BP
X-UA: Sylantro/DKT2010-CA204#CA010
200 1040 OK
A: v:D;L;KY;X-BP;G;BP
X-UA: Sylantro/DKT2010-CA204#CA010
Appendix D: BNF Description of X-UA Parameter
附录D:X-UA参数的BNF说明
Since parts of the X-UA parameter must be parseable in order for a Call Agent to treat similar phones in a similar manner, a formal grammar for this parameter is provided.
由于X-UA参数的某些部分必须是可解析的，以便呼叫代理以类似的方式处理类似的电话，因此提供了此参数的正式语法。
______________ _ ____________________________________________________
|X-UA |:|ENDPOINTINFO |
|______________|_|____________________________________________________|
|ENDPOINTINFO |:|MAKE/MODEL[-VENDORINFO] |
|______________|_|____________________________________________________|
|MAKE |:|1*32 MAKECHAR |
|______________|_|____________________________________________________|
|MODEL |:|1*32 MODELCHAR |
|______________|_|____________________________________________________|
|VENDORINFO |:|1*32 VENDORCHAR |
|______________|_|____________________________________________________|
|MAKECHAR |:|ALPHA | DIGIT |
|______________|_|____________________________________________________|
|MODELCHAR |:|ALPHA | DIGIT |
|______________|_|____________________________________________________|
|VENDORCHAR |:|ALPHA | DIGIT | OTHER |
|______________|_|____________________________________________________|
______________ _ ____________________________________________________
|X-UA |:|ENDPOINTINFO |
|______________|_|____________________________________________________|
|ENDPOINTINFO |:|MAKE/MODEL[-VENDORINFO] |
|______________|_|____________________________________________________|
|MAKE |:|1*32 MAKECHAR |
|______________|_|____________________________________________________|
|MODEL |:|1*32 MODELCHAR |
|______________|_|____________________________________________________|
|VENDORINFO |:|1*32 VENDORCHAR |
|______________|_|____________________________________________________|
|MAKECHAR |:|ALPHA | DIGIT |
|______________|_|____________________________________________________|
|MODELCHAR |:|ALPHA | DIGIT |
|______________|_|____________________________________________________|
|VENDORCHAR |:|ALPHA | DIGIT | OTHER |
|______________|_|____________________________________________________|
Full Copyright Statement
完整版权声明
Copyright (C) The Internet Society (2001). All Rights Reserved.
版权所有（C）互联网协会（2001年）。版权所有。
This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this paragraph are included on all such copies and derivative works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references to the Internet Society or other Internet organizations, except as needed for the purpose of developing Internet standards in which case the procedures for copyrights defined in the Internet Standards process must be followed, or as required to translate it into languages other than English.
本文件及其译本可复制并提供给他人，对其进行评论或解释或协助其实施的衍生作品可全部或部分编制、复制、出版和分发，不受任何限制，前提是上述版权声明和本段包含在所有此类副本和衍生作品中。但是，不得以任何方式修改本文件本身，例如删除版权通知或对互联网协会或其他互联网组织的引用，除非出于制定互联网标准的需要，在这种情况下，必须遵循互联网标准过程中定义的版权程序，或根据需要将其翻译成英语以外的其他语言。
The limited permissions granted above are perpetual and will not be revoked by the Internet Society or its successors or assigns.
上述授予的有限许可是永久性的，互联网协会或其继承人或受让人不会撤销。
This document and the information contained herein is provided on an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
本文件和其中包含的信息是按“原样”提供的，互联网协会和互联网工程任务组否认所有明示或暗示的保证，包括但不限于任何保证，即使用本文中的信息不会侵犯任何权利，或对适销性或特定用途适用性的任何默示保证。
Acknowledgement
确认
Funding for the RFC Editor function is currently provided by the Internet Society.
RFC编辑功能的资金目前由互联网协会提供。