Internet Engineering Task Force Wendy Bothwell Michael Brown Keven Chapman Internet Draft Nortel Networks Document: draft-bothwell-megaco-mftonepkgs- 01.txt Category: Informational December 2000 MF Tone Generation and Detection Packages 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 provides multi-frequency (MF) tone generation and MF tone detection packages for Megaco/H.248. 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. Multi-Frequency Tone Generation Package 3.1 Package PackageID: mfg Description: This package defines the basic MF tones as signals and extends the allowed values of parameter t1 of playtone in tonegen. Version: 1 Extends: tonegen version 1 3.2 Properties Bothwell Informational -- Expires June 17, 2001 1 MF Tone Generation and Detection Packages October 2000 None. 3.3 Events None. 3.4 Signals Signal Name: MF signal code 0 SignalID: mf0 (0x0050) Description: Generate MF signal code 0. The characteristics of the MF signal code, including frequencies and durations, are provisioned on the MG. Signal Type: Brief Duration: Provisioned Additional Parameters: None Additional Values: mf0 (0x0050) is defined as a toneid for playtone. (0x0050 was chosen arbitrarily). The other MF signal codes are specified in exactly the same way. A table with all signal names and signal Ids is included below. Note that each mf signal code is defined as both a signal and a toneid, thus extending the basic tone generation package. Also note that mf signal Ids are different from the names used in a digit map. Signal Name Signal ID/ tone id mf signal code 0 mf0 (0x0050) mf signal code 1 mf1 (0x0051) mf signal code 2 mf2 (0x0052) mf signal code 3 mf3 (0x0053) mf signal code 4 mf4 (0x0054) mf signal code 5 mf5 (0x0055) mf signal code 6 mf6 (0x0056) mf signal code 7 mf7 (0x0057) mf signal code 8 mf8 (0x0058) mf signal code 9 mf9 (0x0059) mf signal code KP mfa (0x005a) mf signal code ST mfb (0x005b) mf signal code KP' or ST' mfc (0x005c) mf signal code KP'' or ST'' mfd (0x005d) mf signal code KP''' or ST''' mfe (0x005e) 3.5 Statistics None. 3.6 Procedures Bothwell Informational -- Expires June 17, 2001 2 MF Tone Generation and Detection Packages October 2000 None. 4. Multi-Frequency Tone Detection Package 4.1 Package PackageID: mfd Description: This package defines the events required for basic MF tone detection. This package extends the possible values of tone id in the "start tone detected", "end tone detected" and "long tone detected" events. Version: 1 Extends: tonedet version 1 4.2 Properties None. 4.3 Events Event Name: MF signal code 0 EventID: mf0 (0x0050) Description: Detect MF signal code 0. The characteristics of the MF signal code, including frequencies and durations, are provisioned on the MG. EventsDescriptor Parameters: None. ObservedEventsDescriptor Parameters: None. Additional Values: The other MF signal codes are specified in exactly the same way. A table with all event names, event Ids and digit map symbols is included below. The event Ids are defined with same names as the signal Ids in package mfg. The additional tone id values are the same tone id values defined in package mfg. Event Name Event ID/ Digit Map tone id Symbol mf signal code 0 mf0 (0x0050) "0" mf signal code 1 mf1 (0x0051) "1" mf signal code 2 mf2 (0x0052) "2" mf signal code 3 mf3 (0x0053) "3" mf signal code 4 mf4 (0x0054) "4" mf signal code 5 mf5 (0x0055) "5" mf signal code 6 mf6 (0x0056) "6" mf signal code 7 mf7 (0x0057) "7" mf signal code 8 mf8 (0x0058) "8" mf signal code 9 mf9 (0x0059) "9" mf signal code KP mfa (0x005a) "A" or "a" Bothwell Informational -- Expires June 17, 2001 3 MF Tone Generation and Detection Packages October 2000 mf signal code ST mfb (0x005b) "B" or "b" mf signal code KP' or ST' mfc (0x005c) "C" or "c" mf signal code KP'' or ST'' mfd (0x005d) "D" or "d" mf signal code KP''' or ST''' mfe (0x005e) "E" or "e" Event Name: Digit Map Completion Event EventID: ce Description: Generated when a digit map completes. EventsDescriptor Parameters: Digit map processing is activated only if a digit map parameter is present, specifying a digit map by name or by value. ObservedEventsDescriptor Parameters: Parameter Name: Digit String ParameterID: ds Description: The collected address string which matched part or all of an alternative event sequence specified in the digit map. Type: string of digit map symbols (possibly empty) returned as a quoted string. Possible values: a sequence of characters "0" through "9", "A" through "E". Parameter Name: Termination Method ParameterID: meth Description: indicates the reason for the generation of the address event. Type: enumeration Possible values: "UM" (0x0001) Unambiguous match "PM" (0x0002) Partial match, completion of timer expiry or unmatched event "FM" (0x0003) Full match, completion by timer expiry or unmatched event 4.4 Signals None. 4.5 Statistics None. 4.6 Procedures None. 5. Formal Syntax Bothwell Informational -- Expires June 17, 2001 4 MF Tone Generation and Detection Packages October 2000 Not Applicable 6. Security Considerations Not Applicable 7. 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 8. Acknowledgments 9. Author's Addresses Wendy Bothwell Nortel Networks 4008 Chapel Hill Road Research Triangle Park, NC USA 27709 Phone: (919) 991-7287 Email: Bothwell@nortelnetworks.com C. Michael Brown Nortel Networks 4008 Chapel Hill Road Research Triangle Park, NC USA 27709 Phone: (919) 991-7767 Email: C.Michael.Brown@nortelnetworks.com Keven Chapman Nortel Networks 4008 Chapel Hill Road Research Triangle Park, NC USA 27709 Phone: (919) 991-4785 Email: Keven@nortelnetworks.com Full Copyright Statement Bothwell Informational -- Expires June 17, 2001 5 MF Tone Generation and Detection Packages October 2000 "Copyright (C) The Internet Society (date). All Rights Reserved. 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 implmentation 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 Bothwell Informational -- Expires June 17, 2001 6