Network Working Group P. Blatherwick (Editor)
Request for Comments: 3054 Nortel Networks
Category: Informational R. Bell
Cisco Systems
P. Holland
Circa Communications
(Chair TIA TR-41.3.4)
January 2001
Network Working Group P. Blatherwick (Editor)
Request for Comments: 3054 Nortel Networks
Category: Informational R. Bell
Cisco Systems
P. Holland
Circa Communications
(Chair TIA TR-41.3.4)
January 2001
Megaco IP Phone Media Gateway Application Profile
Megaco IP电话媒体网关应用程序配置文件
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 specifies a particular application of the Megaco/H.248 Protocol for control of Internet telephones and similar appliances: the Megaco IP Phone Media Gateway. The telephone itself is a Media Gateway (MG), controlled by the Megaco/H.248 Protocol, with application control intelligence located in the Media Gateway Controller (MGC). To achieve a high degree of interoperability and design efficiency in such end-user devices, a consistent architectural approach, a particular organization of Terminations and Packages, and a Protocol Profile are described. The approach makes use of existing Protocol features and user interface related Packages, and is thus a straight-forward application of the Megaco/H.248 Protocol.
本文件规定了用于控制互联网电话和类似设备的Megaco/H.248协议的特定应用：Megaco IP电话媒体网关。电话本身是一个媒体网关（MG），由Megaco/H.248协议控制，应用控制智能位于媒体网关控制器（MGC）中。为了在这样的终端用户设备中实现高度的互操作性和设计效率，描述了一致的体系结构方法、终端和包的特定组织以及协议概要文件。该方法利用现有的协议功能和用户界面相关包，因此是Megaco/H.248协议的直接应用。
This document represents the current view from the TIA working group on VoIP (Voice over IP) telephone specification [1], TIA TR-41.3.4, with the intent of using this as part of its "whole device" specification as an optional method of device control.
本文件代表了TIA VoIP（IP语音）电话规范工作组的当前观点[1]，TIA TR-41.3.4，旨在将其作为“整个设备”规范的一部分，作为设备控制的可选方法。
Industry feedback has made it clear that interoperability and acoustic performance of Internet telephones is key to the rapid and extensive commercialization of these products. To facilitate this, the TIA has established working group TR-41.3.4 to develop a standard
行业反馈表明，互联网电话的互操作性和声学性能是这些产品快速和广泛商业化的关键。为了促进这一点，TIA成立了工作组TR-41.3.4，以制定标准
for VoIP telephones. The TR-41.3.4 working group has included the "whole device" within the scope of the standard, so a full range of requirements including acoustic performance, protocols, methods for powering and safety are provided. Where possible, the requirements are based on existing standards, which are included by reference.
用于VoIP电话。TR-41.3.4工作组已将“整个装置”纳入标准范围，因此提供了一整套要求，包括声学性能、协议、供电方法和安全性。在可能的情况下，这些要求以现有标准为基础，这些标准通过引用的方式包括在内。
The TIA TR-41.3.4 working group has also recognized that its proposed standard must enable creative application of the equipment, encourage the development of new capabilities and allow for high levels of product customization. To achieve this, peer to peer architectures that are based on protocols such as H.323 or SIP and master/slave architectures such as Megaco/H.248 Protocol are both necessary and complementary.
TIA TR-41.3.4工作组还认识到，其拟议标准必须能够创造性地应用设备，鼓励开发新能力，并允许高水平的产品定制。为了实现这一点，基于H.323或SIP等协议的对等体系结构和Megaco/H.248等主/从体系结构都是必要的，也是互补的。
In support of the Megaco/H.248 Protocol development effort, the TR-41.3.4 working group has considered product enabling issues and requirements, and has developed an approach to use the Megaco/H.248 Protocol for Internet telephone device control. This document represents the working group's current view.
为支持Megaco/H.248协议的开发工作，TR-41.3.4工作组审议了产品启用问题和要求，并开发了一种将Megaco/H.248协议用于互联网电话设备控制的方法。本文件代表了工作组的当前观点。
This document covers the general requirements of the Megaco IP Phone application (section 3), architectural approach and MG organization (section 4), details of specific Termination types used and Packages supported by each (section 5), and the Megaco IP Phone Protocol Profile (section 6).
本文件涵盖了Megaco IP电话应用的一般要求（第3节）、体系结构方法和MG组织（第4节）、使用的特定终端类型和每个终端支持的包的详细信息（第5节）以及Megaco IP电话协议概要（第6节）。
The keywords MUST, MUST NOT, REQUIRED, SHALL, SHALL NOT, SHOULD, SHOULD NOT, RECOMMENDED, MAY, and OPTIONAL, when they appear in this document, are to be interpreted as described in RFC 2119 [5].
本文件中出现的关键词必须、不得、必需、应、不应、应、不应、推荐、可和可选时，应按照RFC 2119[5]中的说明进行解释。
The following general requirements were identified to drive the Megaco IP Phone design [1]:
确定了以下一般要求，以推动Megaco IP电话设计[1]：
1. The Megaco IP Phone must meet the basic needs of the business user from day one;
1. Megaco IP电话必须从第一天起满足业务用户的基本需求；
2. Provide a path for rapid expansion to support sophisticated business telephony features;
2. 提供快速扩展的途径，以支持复杂的商务电话功能；
3. Flexibility to allow for a very wide range of telephones and similar devices to be defined, from very simple to very feature rich;
3. 灵活性，允许定义范围非常广泛的电话和类似设备，从非常简单到功能非常丰富；
4. Simple, minimal design;
4. 简单、简约的设计；
5. Allow device cost to be appropriate to capabilities provided;
5. 允许设备成本与提供的功能相适应；
6. Packages and Termination types must have characteristics that enable reliability;
6. 封装和终端类型必须具有能够实现可靠性的特性；
7. The IP Phone MG shall meet the appropriate Megaco/H.248 Protocol requirements as provided in the Megaco Requirements document [2] and be a straight-forward application of the Megaco/H.248 Protocol [3].
7. IP电话MG应满足Megaco要求文件[2]中规定的适当Megaco/H.248协议要求，并应是Megaco/H.248协议[3]的直接应用。
The following subsections describe the general design approach and organization of the Megaco IP Phone MG.
以下小节描述了Megaco IP电话MG的一般设计方法和组织结构。
Design intent of the Megaco IP Phone is to keep it determinedly simple while providing required support for fully featured business telephones and the flexibility to allow for a very wide range of telephone configurations and similar appliances.
Megaco IP电话的设计意图是使其绝对简单，同时为功能齐全的商务电话提供所需的支持，并提供灵活性，以允许非常广泛的电话配置和类似设备。
The approach to achieve this goal is to provide a very simple and direct master/slave control model in which very little feature intelligence is required in the end device. This design intent matches the Megaco/H.248 Protocol approach well.
实现这一目标的方法是提供一个非常简单和直接的主/从控制模型，在该模型中，终端设备只需要很少的功能智能。该设计意图与Megaco/H.248协议方法非常匹配。
It is important to note that additional functionality, built-in feature capability or system-specific optimization can easily be provided, at the option of the implementer, by defining additional Termination types, Event/Signal Packages, or providing built-in application capability. This document defines the minimal design only.
重要的是要注意，通过定义额外的终端类型、事件/信号包或提供内置的应用程序功能，可以根据实施者的选择轻松地提供额外的功能、内置特性功能或系统特定的优化。本文件仅定义了最小设计。
As shown in Figure 1 below, the Megaco IP Phone is organized as a Media Gateway (MG) that consists of a User Interface Termination and a set of Audio Transducer Terminations.
如下图1所示，Megaco IP电话被组织为媒体网关（MG），由一个用户界面终端和一组音频转换器终端组成。
Several - potentially thousands - of Megaco IP Phone MGs may be controlled by a single Media Gateway Controller (MGC). This is distinguished from the organization between traditional analog or PBX telephones behind an IP network, where the MGC would control an MG which in turn controls the collection of telephone devices in question. In the case of a Megaco IP Phone MG, the MG directly
数个（可能数千个）Megaco IP电话MG可由单个媒体网关控制器（MGC）控制。这与IP网络后面的传统模拟电话或PBX电话之间的组织不同，在IP网络中，MGC将控制MG，MG反过来控制相关电话设备的收集。对于Megaco IP电话MG，MG直接
implements the media terminations like handset, handsfree and headset, as well as the user interface. In this case, the Megaco IP Phone itself is the MG.
实现媒体终端，如手机、免提和耳机，以及用户界面。在这种情况下，Megaco IP电话本身就是MG。
+---------------+
| |
| MGC |
| |
+---------------+
^ \ \ \
|
v
+---------------------------------------------+
| |
| Megaco IP Phone MG |
| ================== Audio Transducer |
| Terminations: |
| Audio context(s): + - - - - - - - + |
| +---------------------+ +-----------+ |
| | Context A | | | Handset | | |
| | | +-----------+ |
RTP | | +-----+ +-----+ | | +-----------+ | |
<--------+-+->| Tr | | Ta2 |<-+-----| Handsfree | |
audio | | +-----+ +-----+ | | +-----------+ | |
stream | | | +-----------+ |
| +---------------------+ | | Headset | | |
| +-----------+ |
| | | |
| ETC. |
| + - - - - - - - + |
| |
| +----------------------------------------+ |
| | User Interface Termination | |
| | +--------------+ +--------------+ | |
| | | Text Display | | Keypad | | |
| | +--------------+ +--------------+ | |
| | +--------------+ +--------------+ | |
| | | Softkeys | | Indicators | | |
| | +--------------+ +--------------+ | |
| | +--------------+ | |
| | | Function Keys| ETC. | |
| | +--------------+ | |
| +----------------------------------------+ |
+---------------------------------------------+
+---------------+
| |
| MGC |
| |
+---------------+
^ \ \ \
|
v
+---------------------------------------------+
| |
| Megaco IP Phone MG |
| ================== Audio Transducer |
| Terminations: |
| Audio context(s): + - - - - - - - + |
| +---------------------+ +-----------+ |
| | Context A | | | Handset | | |
| | | +-----------+ |
RTP | | +-----+ +-----+ | | +-----------+ | |
<--------+-+->| Tr | | Ta2 |<-+-----| Handsfree | |
audio | | +-----+ +-----+ | | +-----------+ | |
stream | | | +-----------+ |
| +---------------------+ | | Headset | | |
| +-----------+ |
| | | |
| ETC. |
| + - - - - - - - + |
| |
| +----------------------------------------+ |
| | User Interface Termination | |
| | +--------------+ +--------------+ | |
| | | Text Display | | Keypad | | |
| | +--------------+ +--------------+ | |
| | +--------------+ +--------------+ | |
| | | Softkeys | | Indicators | | |
| | +--------------+ +--------------+ | |
| | +--------------+ | |
| | | Function Keys| ETC. | |
| | +--------------+ | |
| +----------------------------------------+ |
+---------------------------------------------+
Figure 1: Megaco IP Phone Termination / Package Model
图1:Megaco IP电话终端/包型号
As shown in Figure 1, each Audio Transducer Termination represents an individually controllable audio input/output element of the telephone device, such as Handset, Handsfree, Headset, etc. By separating each audio element as a distinct Termination, more flexible applications can be easily implemented, such as paging, group listening, and so on. Since this is actually only the logical view of the device, represented by protocol, it is also quite possible to simplify representation of the device by hiding all available audio input/outputs behind a single Audio Transducer Termination, for example the Handset, and implement control of multiple real input/outputs locally inside the device.
如图1所示，每个音频传感器终端代表电话设备的单独可控音频输入/输出元件，如手持电话、免提、耳机等。通过将每个音频元件分离为不同的终端，可以轻松实现更灵活的应用，如寻呼、群听等。由于这实际上只是由协议表示的设备的逻辑视图，因此通过将所有可用音频输入/输出隐藏在单个音频传感器终端（例如手持设备）后面，并在设备内部本地实现对多个真实输入/输出的控制，简化设备的表示也是非常可能的。
All non-audio user interface elements are associated with the User Interface Termination. This special Termination supports Packages to implement all user interaction with the telephone user interface, including Function Keys, Indicators, the Dialpad, etc, as appropriate for the specific device capabilities (within constraints given in the section on User Interface Termination). The User Interface Termination cannot be placed in any Context. This grouping of user interface elements behind a well-know Termination greatly simplifies audits to determine actual device configuration, and reduces the number of Terminations involved in representing user interface.
所有非音频用户界面元素都与用户界面终端相关联。此特殊终端支持实现所有用户与电话用户界面交互的软件包，包括功能键、指示器、拨号板等，适用于特定设备功能（在用户界面终端部分给出的限制范围内）。用户界面终止不能放在任何上下文中。众所周知的终端后面的用户界面元素分组大大简化了确定实际设备配置的审核，并减少了表示用户界面所涉及的终端数量。
In addition, TerminationID naming conventions are provided to identify specific Terminations within the Megaco IP Phone MG and group them into related sets. These conventions use a set of well known identifier names to specify the individual Terminations, for example the User Interface Termination ("ui"), the Handset Audio Transducer ("at/hs"), or the Handsfree Audio Transducer ("at/hf"). This specific naming is important in this application, especially for the Audio Transducer Terminations, since the real input/output elements to which they map on the physical device have very different functional significance to the end-user, yet they may be represented in the protocol using exactly the same sets of Packages. Naming conventions allow the controlling MGC to distinguish this end-user meaning without specific advance knowledge of physical device configuration and without the requirement to provide different Packages for each audio input/output type.
此外，还提供TerminationID命名约定，以识别Megaco IP Phone MG中的特定终端，并将其分组到相关集合中。这些约定使用一组众所周知的标识符名称来指定各个终端，例如用户界面终端（“ui”）、手持音频传感器（“at/hs”）或免提音频传感器（“at/hf”）。该特定命名在该应用中非常重要，尤其是对于音频传感器终端，因为它们在物理设备上映射到的实际输入/输出元素对最终用户具有非常不同的功能意义，但是它们可以使用完全相同的包集在协议中表示。命名约定允许控制MGC区分此最终用户含义，而无需预先了解物理设备配置，也无需为每种音频输入/输出类型提供不同的包。
Using these same TerminationID naming conventions in combination with wildcards, the MGC application can target commands to groups of related Terminations, for example the collection of all Audio Transducer Terminations ("at/*"). This is especially useful during the discover phase, for example to efficiently Audit all available Audio Transducer Terminations, and to efficiently send commands to a set of related Terminations in a single command, for example to
使用这些相同的TerminationID命名约定和通配符，MGC应用程序可以将命令定向到相关终端组，例如所有音频转换器终端的集合（“at/*”）。这在发现阶段尤其有用，例如有效地审计所有可用的音频转换器终端，并在单个命令中有效地向一组相关终端发送命令，例如
simultaneously Subtract all Audio Transducer Terminations from a particular Context. Further information on TerminationID naming conventions and their use can be found under the sections on Control Interaction and Capability Discovery (next two subsections) and under Termination Types.
同时从特定上下文中减去所有音频传感器终端。有关TerminationID命名约定及其使用的更多信息，请参见控制交互和功能发现部分（下两小节）和TerminationType部分。
To provide control of audio paths, Audio Transducer Terminations are manipulated using Contexts in the normal way, by sending Add, Move, Subtract and Modify commands addressed to the specific Terminations being manipulated. For example creating a Context (Context A) containing an RTP Termination (Tr) and a Handset Audio Transducer Termination (Ta1) creates a voice connection to/from the handset. Moving a Handsfree Audio Transducer Termination (Ta2) into the Context, and removing the Handset, sets up a handsfree conversation. This situation is shown in Figure 1. See the section on Audio Transducer Termination Types for further details on specific Package support requirements.
为了提供对音频路径的控制，音频转换器终端通过向被操作的特定终端发送添加、移动、减去和修改命令，以正常方式使用上下文进行操作。例如，创建包含RTP终端（Tr）和手持电话音频转换器终端（Ta1）的上下文（上下文a）创建与手持电话的语音连接。将免提音频转换器终端（Ta2）移动到上下文中，然后卸下手机，即可建立免提对话。这种情况如图1所示。有关特定封装支持要求的更多详细信息，请参见音频传感器终端类型部分。
User input elements, such as Keypad or Function Keys, generate Events through Notify commands sent from the User Interface Termination of the Megaco IP Phone MG to the controlling MGC for handling. These Events are according to the specific set of Packages supported by the User Interface Termination of the device. See the section on User Interface Termination Type for further details on specific Package support requirements.
用户输入元素（如键盘或功能键）通过从Megaco IP电话MG的用户界面终端发送到控制MGC进行处理的Notify命令生成事件。这些事件取决于设备的用户界面终端支持的特定包集。有关特定软件包支持要求的更多详细信息，请参阅“用户界面终端类型”部分。
User output elements such as the Text Display or Indicators are controlled by Signals sent by the MGC, addressed to the User Interface Termination of the Megaco IP Phone MG, generally as part of a Modify command, using syntax defined in the corresponding Packages. Since the User Interface Termination cannot be part of any context, Add, Move and Subtract commands sent to it are not valid. See the section on User Interface Termination Type for further details on specific Package support requirements.
用户输出元素（如文本显示或指示灯）由MGC发送的信号控制，该信号发送至Megaco IP电话MG的用户界面终端，通常作为修改命令的一部分，使用相应软件包中定义的语法。由于用户界面终止不能是任何上下文的一部分，因此发送给它的Add、Move和Subtract命令无效。有关特定软件包支持要求的更多详细信息，请参阅“用户界面终端类型”部分。
Some elements, for example Softkeys, have both user input and output aspects, so both react to Signals and generate Events as above.
某些元素，例如软键，具有用户输入和输出方面，因此两者都对信号作出反应并生成如上所述的事件。
The TerminationID naming conventions may be used to target commands to specific Terminations by well known name, for example to Add the Handsfree Audio Transducer Termination ("at/hf") to a Context. The naming conventions in combination with wildcards may be used to efficiently send commands to groups of related Terminations, for example to simultaneously Subtract all Audio Transducer Terminations ("at/*") from a particular Context.
TerminationID命名约定可用于以众所周知的名称将命令定向到特定终端，例如将免提音频传感器终端（“at/hf”）添加到上下文中。命名约定结合通配符可用于有效地向相关终端组发送命令，例如从特定上下文中同时减去所有音频传感器终端（“at/*”）。
At startup or service change, the Megaco IP Phone MG identifies itself to its controlling MGC as being a Megaco IP Phone class of device by use of the IPPhone Protocol Profile. This is the first and most important stage of capability discovery, and implicitly provides a great deal of the necessary information in a single step. Thereafter, the MGC can make a large number of assumptions regarding organization and behavior of the MG. See the section on IPPhone Protocol Profile for further details of ServiceChange operation.
在启动或服务变更时，Megaco IP电话MG通过使用IPPhone协议配置文件向其控制MGC确认自己是Megaco IP电话类设备。这是能力发现的第一个也是最重要的阶段，在一个步骤中隐含地提供了大量必要的信息。此后，MGC可以对MG的组织和行为进行大量假设。有关ServiceChange操作的更多详细信息，请参阅IPPhone协议配置文件部分。
Device capabilities, including the list of all Terminations and supported Packages for each, are queried through the AuditValue command. Wildcarded AuditValue commands targeted at the whole MG (i.e., addressed to ContextID=Null, TerminationID=ALL) return the list of all Terminations, including the User Interface Termination and all supported Audio Transducer Terminations. Since the returned TerminationIDs use well known identifier names, the MGC can derive the specific audio input/output elements available on the physical device, and their intended purpose. Further AuditValues commands on individual named Terminations provide further details of each, for example for the MGC to query user interface support Packages available on the User Interface Termination ("ui"). TerminationID naming conventions in combination with wildcards can be used with AuditValues commands to query specific Package support for the collection of all Audio Transducer Terminations ("at/*").
通过AuditValue命令查询设备功能，包括所有终端和每个终端支持的包的列表。针对整个MG的通配符AuditValue命令（即，地址为ContextID=Null，TerminationID=ALL）返回所有终端的列表，包括用户界面终端和所有支持的音频转换器终端。由于返回的TerminationID使用众所周知的标识符名称，因此MGC可以派生物理设备上可用的特定音频输入/输出元素及其预期用途。单个命名终端上的其他AuditValues命令提供了每个终端的详细信息，例如，MGC可以查询用户界面终端（“ui”）上可用的用户界面支持包。TerminationID命名约定与通配符可与AuditValues命令一起使用，以查询所有音频转换器终端集合的特定软件包支持（“at/*”）。
Since the structure of the Megaco IP Phone MG is well known in advance, by virtue of the IPPhone Protocol Profile, audits can be efficiently directed at discovering only what additional information is required by the MGC. Thus the MGC is able to efficiently and unambiguously discover both the specific user interface capabilities and the supported audio input/outputs of the Megaco IP Phone MG, without specific advance knowledge of physical device configuration. It is not necessary for the MGC to attempt to infer function from supported Packages within a random collection of Terminations, and a great deal of behavior common to all Megaco IP Phone MGs can simply be assumed. This pre-determined organization and behavior therefore greatly reduces design complexity of both MG and MGC, and greatly improves interoperability.
由于Megaco IP电话MG的结构事先众所周知，借助IPPhone协议配置文件，可以有效地指导审计，仅发现MGC需要哪些附加信息。因此，MGC能够高效且明确地发现Megaco IP电话MG的特定用户界面功能和支持的音频输入/输出，而无需预先了解物理设备配置。MGC没有必要尝试从随机终端集合中的受支持软件包推断功能，可以简单地假设所有Megaco IP电话MG共有的大量行为。因此，这种预先确定的组织和行为大大降低了MG和MGC的设计复杂性，并大大提高了互操作性。
The Termination types defined for use in the Megaco IP Phone MG are:
定义用于Megaco IP电话MG的终端类型有：
* User Interface (implements user interface);
* 用户界面（实现用户界面）；
* Audio Transducer (implements audio input/output to the user, and potentially appears as several individual Terminations corresponding to individual audio input/outputs on the physical device);
* 音频传感器（实现对用户的音频输入/输出，并可能显示为与物理设备上的单个音频输入/输出相对应的多个单独终端）；
* RTP (transport of audio streams over IP).
* RTP（通过IP传输音频流）。
These Termination types represent minimal capabilities to support fully featured business telephones. Additional Termination types can be defined to extend these capabilities.
这些终端类型代表了支持功能齐全的商务电话的最低能力。可以定义其他终端类型以扩展这些功能。
The following subsections describe requirements and constraints on each type in further detail.
以下小节详细描述了每种类型的要求和约束。
The User Interface Termination represents the Megaco IP Phone MG user interface elements. Megaco IP Phone MGs MUST support exactly one User Interface Termination.
用户界面终端代表Megaco IP Phone MG用户界面元素。Megaco IP电话MGs必须只支持一个用户界面终端。
TerminationID of the User Interface Termination MUST be "ui", used for both command addressing and command response return. ABNF text encoding for this MUST be as described in Megaco/H.248 Protocol Appendix B.1 [3].
用户界面终端的TerminationID必须为“ui”，用于命令寻址和命令响应返回。ABNF文本编码必须如Megaco/H.248协议附录B.1[3]所述。
Note: If ASN.1 binary encoding is used (OPTIONAL in this specification), TerminationID for the User Interface Termination MUST be encoded as described in Megaco/H.248 Protocol Appendix A.1 [3], with alphabetic characters of the identifier given above mapping to the equivalent octet string in the ASN.1 encoding.
注：如果使用ASN.1二进制编码（本规范中可选），用户界面终端的TerminationID必须按照Megaco/H.248协议附录A.1[3]中的描述进行编码，上面给出的标识符的字母字符映射到ASN.1编码中的等效八位字节字符串。
The User Interface Termination cannot be part of any context, hence Add, Move and Subtract commands are invalid for this Termination.
用户界面终止不能是任何上下文的一部分，因此添加、移动和减去命令对此终止无效。
The User Interface Termination MAY support the following Packages, defined in Megaco/H.248 Protocol H.248 Annex G: "User Interface Elements and Actions Packages" [4].
用户界面终端可支持Megaco/H.248协议H.248附录G中定义的以下包：“用户界面元素和操作包”[4]。
__________________________________________________________
| Package | Name | Support in User Interface |
| | | Termination |
|___________________|_______ |_____________________________|
| Text Display | dis | OPTIONAL |
| Keypad | kp | OPTIONAL |
| Function Key | kf | OPTIONAL |
| Indicator | ind | OPTIONAL |
| Softkey | ks | OPTIONAL |
| Ancillary Input | anci | OPTIONAL |
|___________________|________|_____________________________|
__________________________________________________________
| Package | Name | Support in User Interface |
| | | Termination |
|___________________|_______ |_____________________________|
| Text Display | dis | OPTIONAL |
| Keypad | kp | OPTIONAL |
| Function Key | kf | OPTIONAL |
| Indicator | ind | OPTIONAL |
| Softkey | ks | OPTIONAL |
| Ancillary Input | anci | OPTIONAL |
|___________________|________|_____________________________|
Additional Packages not listed above MAY also be provided where these are defined to extend to additional user interface elements.
如果定义了扩展到其他用户界面元素的附加包，则也可以提供上面未列出的附加包。
Note: The reasoning to make all Packages optional in the User Interface Termination is to allow maximum flexibility to create a very broad range of Internet telephones and similar devices. For example, anything from a simple hotel lobby phone (handset and hookswitch only), to conferencing units (handsfree unit and one or two buttons) to fully featured business telephones (display, rich set of keys and indicators, both handset and handsfree, etc) could be designed.
注：在用户界面终端中使所有软件包可选的理由是允许最大限度的灵活性来创建范围非常广泛的互联网电话和类似设备。例如，从简单的酒店大堂电话（仅限于手持电话和挂钩开关）、会议单元（免提单元和一个或两个按钮）到功能齐全的商务电话（显示器、丰富的按键和指示灯、手持电话和免提装置等），都可以设计。
The Audio Transducer Terminations are used to control audio input/output to/from the end user of the device. Megaco IP Phone MGs MUST support at least one Audio Transducer Termination, which MAY be chosen from the following well known types (with identifier name):
音频传感器终端用于控制设备最终用户的音频输入/输出。Megaco IP电话MGs必须至少支持一个音频转换器终端，可以从以下已知类型（具有标识符名称）中选择：
* Handset ("hs") -- input/output, * Handsfree ("hf") -- input/output, * Headset ("ht") -- input/output, * Microphone ("mi") -- input only, * Speaker ("sp") -- output only.
* 手持设备（“hs”）--输入/输出，*免提设备（“hf”）--输入/输出，*耳机（“ht”）--输入/输出，*麦克风（“mi”）--仅输入，*扬声器（“sp”）--仅输出。
TerminationIDs of the Audio Transducer Terminations MUST be of the form "at/<name>", where <name> is the 2 character identifier listed above, used for both command addressing and command response return. If more than one Audio Transducer Termination of a particular type is implemented, the TerminationIDs of each MUST be of the form "at/<name>/<num>", where <num> is a 2 digit index number in hexadecimal format beginning at 01. Examples of valid TerminationIDs include: "at/hs" (handset), "at/mi/02" (microphone 2), "at/*" (all audio input/outputs). ABNF text encoding for this MUST be as described in Megaco/H.248 Protocol Appendix B.1 [3].
音频传感器终端的终端ID必须为“at/<name>”格式，其中<name>是上面列出的2个字符的标识符，用于命令寻址和命令响应返回。如果实现了一种特定类型的多个音频传感器终端，则每个终端的终端ID必须为“at/<name>/<num>”格式，其中<num>是从01开始的十六进制格式的2位索引号。有效终端ID的示例包括：“at/hs”（手机）、“at/mi/02”（麦克风2）、“at/*”（所有音频输入/输出）。ABNF文本编码必须如Megaco/H.248协议附录B.1[3]所述。
Note: If ASN.1 binary encoding is used (OPTIONAL in this specification), TerminationIDs and wildcards MUST be encoded as described in Megaco/H.248 Protocol Appendix A.1 [3], with alphabetic characters of the identifiers given above mapping to octet sub-strings in the ASN.1 encoding and the '/' character not used.
注：如果使用ASN.1二进制编码（本规范中可选），则必须按照Megaco/H.248协议附录A.1[3]中的说明对TerminationID和通配符进行编码，上面给出的标识符的字母字符映射到ASN.1编码中的八位字节子字符串，并且不使用“/”字符。
Additional Audio Transducer Termination types MAY also be defined by the implementer, however well know identifier names for these are outside the scope of this specification.
其他音频传感器终端类型也可由实施者定义，但众所周知的标识符名称不在本规范范围内。
All Audio Transducer type Terminations MUST support the following Packages, defined in Megaco/H.248 Protocol Annex E [3].
所有音频传感器类型终端必须支持Megaco/H.248协议附录E[3]中定义的以下软件包。
____________________________________________________________
| Package | Name | Support in Audio Transducer |
| | | Terminations |
|_____________________|_______ |_____________________________|
| Basic DTMF Generator| dg | REQUIRED |
| Call Progress Tones | cg | REQUIRED |
| Generator | | |
|_____________________|________|_____________________________|
____________________________________________________________
| Package | Name | Support in Audio Transducer |
| | | Terminations |
|_____________________|_______ |_____________________________|
| Basic DTMF Generator| dg | REQUIRED |
| Call Progress Tones | cg | REQUIRED |
| Generator | | |
|_____________________|________|_____________________________|
Additional Packages not listed above MAY also be provided where applicable to audio input/output functions.
如果适用于音频输入/输出功能，也可提供上述未列出的附加软件包。
Megaco IP Phone MGs MUST support at least one RTP Termination in order to support audio streams to/from the device, as defined in Megaco/H.248 Protocol Annex E.12 [3].
Megaco IP电话MG必须支持至少一个RTP终端，以支持设备之间的音频流，如Megaco/H.248协议附录E.12[3]中所定义。
No special TerminationID naming convention is defined for RTP Terminations as part of this specification.
作为本规范的一部分，没有为RTP终端定义特殊的TerminationID命名约定。
The following subsections provide details of the IPPhone Protocol Profile, used between Megaco IP Phone MGs and their controlling MGCs. This includes implicit application-level agreements between the Megaco IP Phone MG and its controlling MGC on organization and behavior of the MG, types of Terminations used and the specific minimum Package support for each, and specific minimum selections on the transport and encoding methods used.
以下小节提供了Megaco IP电话MG及其控制MGC之间使用的IPPhone协议配置文件的详细信息。这包括Megaco IP Phone MG与其控制MGC之间就MG的组织和行为、所使用的终端类型和每个终端的特定最低包支持以及所使用的传输和编码方法的特定最低选择达成的隐式应用程序级协议。
Use of a this Profile greatly simplifies assumptions necessary by the MGC regarding MG organization, thereby reducing complexity and cost of both MG and MGC, and improves interoperability for the specific Megaco IP Phone application. Since the Profile is specific to the
此配置文件的使用大大简化了MGC对MG组织的必要假设，从而降低了MG和MGC的复杂性和成本，并提高了特定Megaco IP电话应用程序的互操作性。因为配置文件是特定于
Megaco IP Phone MG, no other applications of Megaco/H.248 Protocol are affected.
Megaco IP电话MG，Megaco/H.248协议的其他应用程序不受影响。
It is important to note that the IPPhone Profile specifies minimum functionality only, for interoperability purposes. Additional Termination types, Package support, transport or encoding methods, or other capabilities MAY be added at the discretion of the implementer within the general structure described.
请务必注意，IPPhone配置文件仅为互操作性目的指定了最低功能。实施者可自行决定在所述一般结构内添加其他终端类型、包支持、传输或编码方法或其他功能。
Profile name: "IPPhone" Version: 1
配置文件名称：“IPPhone”版本：1
The Megaco/H.248 Protocol [3] describes startup and service change procedures in detail, including use of Profiles.
Megaco/H.248协议[3]详细描述了启动和服务更改程序，包括配置文件的使用。
In brief, the above Profile name and version are supplied by the Megaco IP Phone MG on startup or at service change, in the ServiceChangeDescriptor parameter of the ServiceChange command, issued to the controlling MGC as part of the registration procedure. In response, the MGC may 1) accept control by acknowledging the Service Change, 2) pass control to a different MGC by replying with a new MGC to try, or 3) refuse control entirely by rejecting the Service Change. If MGC control is refused, the Megaco IP Phone MG may attempt registration with other MGCs in its list of MGCs to try.
简言之，以上配置文件名称和版本由Megaco IP Phone MG在启动时或在服务更改时提供，在ServiceChange命令的ServiceChangeDescriptor参数中，作为注册过程的一部分发送给控制MGC。作为响应，MGC可以1）通过确认服务更改来接受控制，2）通过回复新的MGC来尝试将控制传递给不同的MGC，或者3）通过拒绝服务更改来完全拒绝控制。如果MGC控制被拒绝，Megaco IP电话MG可以尝试向其MGC列表中的其他MGC注册以尝试。
Once a controlling MGC accepts the IPPhone Profile, both it and the Megaco IP Phone MG become bound by the Profile rules and constraints described in subsequent subsections as well as Megaco IP Phone Termination/Package organization and behavior rules described in previous sections of this document. Thereafter, any protocol use outside these rules is considered an error.
一旦控制MGC接受IPPhone配置文件，它和Megaco IP Phone MG将受到后续小节中描述的配置文件规则和约束以及本文档前面章节中描述的Megaco IP Phone终止/包组织和行为规则的约束。此后，在这些规则之外使用的任何协议都被视为错误。
Termination organization, required Termination types, and the specific Packages supported by each MUST be as described in sections 4 - 5 of this document.
终止组织、所需的终止类型以及各自支持的特定包必须如本文件第4-5节所述。
Note that additional Termination types and Package support MAY also be provided within the general structure described.
注意，在所述的一般结构中，还可以提供额外的终端类型和封装支持。
Megaco IP Phone MGs MUST support Application Layer Framing (ALF) over UDP transport, as specified in the Megaco/H.248 Protocol Appendix D.1 [3].
Megaco IP电话MGs必须支持UDP传输上的应用层帧（ALF），如Megaco/H.248协议附录D.1[3]中所述。
Note that this does not imply that the Megaco IP Phone MG cannot support other transport methods as well. TCP transport is OPTIONAL, but if used MUST conform to Megaco/H.248 Protocol Appendix D.2 [3].
请注意，这并不意味着Megaco IP电话MG也不能支持其他传输方式。TCP传输是可选的，但如果使用，必须符合Megaco/H.248协议附录D.2[3]。
Megaco IP Phone MGs MUST support ABNF text encoding of the protocol, as specified in the Megaco/H.248 Protocol Appendix B [3].
Megaco IP电话MGs必须支持协议的ABNF文本编码，如Megaco/H.248协议附录B[3]所述。
Note that this does not imply that the Megaco IP Phone MG cannot support ASN.1 binary encoding as well. ASN.1 binary encoding is OPTIONAL, but if used MUST conform to Megaco/H.248 Protocol Appendix A [3].
请注意，这并不意味着Megaco IP电话MG也不能支持ASN.1二进制编码。ASN.1二进制编码是可选的，但如果使用，必须符合Megaco/H.248协议附录A[3]。
The Megaco IP Phone Media Gateway Application Profile adds no new security issues beyond those endemic to all applications of Megaco/H.248 Protocol [3].
Megaco IP电话媒体网关应用程序配置文件没有添加任何新的安全问题，除了Megaco/H.248协议的所有应用程序特有的问题[3]。
[1] TIA/EIA, IS-811, Performance and Interoperability Requirements
for Voice-over-IP (VoIP) Feature Telephones,
http://www.tiaonline.org/standards/ip/voip/tia-eia-is-811-
final.pdf
[1] TIA/EIA, IS-811, Performance and Interoperability Requirements
for Voice-over-IP (VoIP) Feature Telephones,
http://www.tiaonline.org/standards/ip/voip/tia-eia-is-811-
final.pdf
[2] Greene, N., Ramalho, M. and B. Rosen, "Media Gateway Control Protocol Architecture and Requirements", RFC 2805, April 2000.
[2] Greene，N.，Ramalho，M.和B.Rosen，“媒体网关控制协议体系结构和要求”，RFC 2805，2000年4月。
[3] Cuervo, F., Greene, N., Rayhan, A., Huitema, C., Rosen, B. and J. Segers, "Megaco Protocol Version 1.0", RFC 3015, November 2000.
[3] Cuervo，F.，Greene，N.，Rayhan，A.，Huitema，C.，Rosen，B.和J.Segers，“Megaco协议版本1.0”，RFC 30152000年11月。
[4] ITU-T SG16, H.248 Annex G: User Interface Elements and Actions
Packages, Brown, M. & P. Blatherwick, November 2000.
http://www.itu.int/itudoc/itu-t/rec/h/h248anxg.html
[4] ITU-T SG16, H.248 Annex G: User Interface Elements and Actions
Packages, Brown, M. & P. Blatherwick, November 2000.
http://www.itu.int/itudoc/itu-t/rec/h/h248anxg.html
[5] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997.
[5] Bradner，S.，“RFC中用于表示需求水平的关键词”，BCP 14，RFC 2119，1997年3月。
Peter Blatherwick (Editor) Nortel Networks P.O. Box 3511, Stn C Ottawa, Ontario, Canada K1Y 4H7
Peter Blatherwick（编辑）加拿大安大略省渥太华市Stn C北电网络邮政信箱3511号K1Y 4H7
Phone: (613) 763-7539 (613) 724-4726 EMail: blather@nortelnetworks.com peter.blatherwick@home.com
电话：（613）763-7539（613）724-4726电子邮件：blather@nortelnetworks.com彼得。blatherwick@home.com
Bob Bell Cisco Systems Inc. 576 S. Brentwood Ln. Bountiful, UT 84010 USA
Bob Bell Cisco Systems Inc.576 S.Brentwood Ln。美国犹他州84010，慷慨
Phone: (801) 294-3034 EMail: rtbell@cisco.com
电话：（801）294-3034电子邮件：rtbell@cisco.com
Phil Holland Circa Communications Ltd. 1000 West 14th Street North Vancouver, British Columbia, Canada V7P 3P3
Phil Holland Circa通信有限公司，加拿大不列颠哥伦比亚省温哥华北部西14街1000号V7P 3P3
Phone: (604) 924-1742 EMail: phil.holland@circa.ca
电话：（604）924-1742电子邮件：菲尔。holland@circa.ca
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编辑功能的资金目前由互联网协会提供。