Media Gateway Control (Megaco) Selvam Rengasami Internet Draft Telcordia Technologies Document: draft-ietf-megaco-h248k-00.txt Zacharias Bilalis Category: Standards Track Siemens July 2000 H.248 Annex K (Pre-Decision White Document) Status of this Memo This document is an Internet-Draft and is in full conformance with all provisions of Section 10 of RFC2026 [1]. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet- Drafts. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet- Drafts as reference material or to cite them other than as "work in progress." The list of current Internet-Drafts can be accessed at http://www.ietf.org/ietf/1id-abstracts.txt The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html. 1. Abstract This document reproduces the content of the ITU-T Study Group 16 White Document draft of H.248 Annex K, which is scheduled for decision in Geneva in November 2000. H.248 Annex K provides the Generic Announcement package. This document is submitted for IETF comment prior to ITU-T decision, in accordance with procedures currently being negotiated between ITU-T Study Group and ISOC on behalf of the IETF. 2. Conventions used in this document The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC-2119 [2]. 3. Generic Announcement PACKAGE PackageID: an, 0x001d Version: 1 Extends: None Bilalis, Rengasami Standards Track - Expires January 2001 1 H.248 Annex K (White Document draft) July 2000 That package supports announcement functionality at a Media Gateway 3.1 Properties None 3.2 Events 3.2.1 Announcement completed EventID: ac (0x0001) Description: Indicates the completion of the announcement. EventDescriptor parameters: None ObservedEventDescriptor parameters: None 3.2.2 Announcement failure EventID: af (0x0002) Description: Indicates the failure of the announcement. EventDescriptor parameters None ObservedEventDescriptor parameters None 3.3 Signals 3.3.1 Fixed - Announcement play SignalID: apf (0x0003) Description: Initiates the play of a fixed announcement Parameters: Announcement name ParameterID: an (0x0001) Type: enumeration of announcements. Default is TO Bilalis, Rengasami Standards Track - Expires January 2000 2 H.248 Annex K (White Document draft) July 2000 Number of cycles ParameterID: noc (0x0002) Type: integer. Values: any Default: 1 3.3.2 Variable - Announcement play SignalID: apv (0x0004) Description: Initiates the play of a variable announcement Parameters: Announcement name ParameterID: an (0x0001) Type: enumeration of announcements. Default is TO Number of cycles ParameterID: noc (0x0002) Type: integer. Values: any Default: 1 Number ParameterID: num (0x0003) Type: integer Values: any Specific parameters interpretation ParameterID: spi (0x0004) Type: enumeration Values: any Specific parameters ParameterID: sp (0x0005) Type: string Values: any Default is provisioned for every anouncement. 3.3.3 Statistics None 3.3.4 Procedures An MGC may send a fixed play announcements message to the MG. An MG receiving such a signal plays the indicated announcement (indicated Bilalis, Rengasami Standards Track - Expires January 2000 3 H.248 Annex K (White Document draft) July 2000 by the name parameter) for the duration specified by the noc parameter. If an noc parameter is not included, the MG uses a default of 1 cycle. To provide additional information when an announcement is to be played, the MGC sends a play variable announcement signal to the MG. An MG receiving such a signal plays the indicated announcement (indicated by the name parameter) for the duration specified by the noc parameter. If an noc parameter is not included, the MG uses a default of 1. If the sp parameter is included, the MG uses the Specific parameters interpretation parameter to identify the particular type of information to be included in the announcement. Examples of the types of Specific parameters include a telephone number, date, or time. 4. Security Considerations Security considerations regarding media gateway control are discussed in section 10 of [3]. 5. References 1 Bradner, S., "The Internet Standards Process -- Revision 3", BCP 9, RFC 2026, October 1996. 2 Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. 3 ITU-T Recommendation H.248, "Gateway Control Protocol", Geneva, June 2000. Also to appear as RFC xxxx (currently draft-ietf- megaco-merged-01.txt). 6. Authors' Addresses Selvam Rengasami (editor) Telcordia Technologies Phone: + 1 732 758 5260 Email: srengasa@telcordia.com Zacharias Bilalis (editor) Siemens Phone: + 49 89 722 28391 Email: zacharias.bilalis@icn.siemens.de Bilalis, Rengasami Standards Track - Expires January 2000 4