Media Gateway Control Kevin Boyle II C. Michael Brown Internet Draft Nortel Networks Document: draft-boyle-megaco-alerting-01.txt January 2001 Category: Standards Track Enhanced Alerting Packages for Megaco/H.248 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 proposed definitions for several supplemental packages for Megaco/H.248. These packages address support of functionality for enhanced telephony services, specifically CLASS signaling services. This document is the updated version of the alerting and CLASS packages presented originally in draft-brown- megaco-supplpkgs-00.txt. 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. Enhanced Alerting Package PackageID: alert (0x????) Version: 1 Extends: none. This package defines enhanced alerting signals for analog lines. Boyle & Brown Standards Track - Expires July 2001 1 Enhanced Alerting Packages for Megaco/H.248 January 2001 3.1 Properties None. 3.2 Events None. 3.3 Signals Ring SignalID: ri (0x????) Applies ringing to the line. Signal Type: TimeOut Duration: Provisioned Additional Parameters: Pattern ParameterID: pattern (0x????) Type: Enumeration Possible Values: 1 - 10 (0x0001 - 0x000A) The pattern is an abstract indication of the distinctive alerting pattern that will be applied to the line. The alert/ri pattern parameter has a direct mapping to the alert/cw pattern parameter, and to the class/cid pattern parameter. The actual cadence/frequency combination is available in the gateway. The default is pattern 1, which indicates the default alerting style. Ring patterns repeat until the signal times out, or is interrupted. It is useful to note that ringing patterns and call waiting patterns are paired to allow for distinctive alerting sets. In expanding this parameter in the future, it would be desirable to expand the alert/ri, alert/cw, and class/cid signals together, maintaining the distinctive pattern pairings. This will continue to allow the class/cid signal to have a definition independent of alerting method, linking it only to the alerting style (pattern). Ringsplash SignalID: rs (0x????) Applies ringsplash to the line. Boyle & Brown Standards Track - Expires July 2001 2 Enhanced Alerting Packages for Megaco/H.248 January 2001 Signal Type: Brief Duration: Provisioned Additional Parameters: None. Call Waiting SignalID: cw (0x????) Generate call waiting indication. The cw signal definition takes a pattern parameter, to allow generation of distinctive waiting tones. Signal Type: Brief Duration: Varies by pattern. Additional Parameters: Pattern ParameterID: pattern (0x????) Type: Enumeration Possible Values: 1 - 10 (0x0001 - 0x000A) The pattern is an abstract indication of the distinctive alerting pattern that will be applied to the line. The alert/cw pattern parameter has a direct mapping to the alert/ri pattern parameter, and to the class/cid pattern parameter. The actual cadence/frequency combination is available in the gateway. The default is pattern 1, which indicates the default alerting style. Call wait patterns do not repeat. It is useful to note that ringing patterns and call waiting patterns are paired to allow for distinctive alerting sets. In expanding this parameter in the future, it would be desirable to expand the alert/ri, alert/cw, and class/cid signals together, maintaining the distinctive pattern pairings. This will continue to allow the class/cid signal to have a definition independent of alerting method, linking it only to the alerting style (pattern). 3.4 Statistics None. 3.5 Procedures It is anticipated that a Ringing MIB will be necessary to provision the proper frequencies and cadences onto the GW. 4. CLASS Signaling Package Boyle & Brown Standards Track - Expires July 2001 3 Enhanced Alerting Packages for Megaco/H.248 January 2001 PackageID: class (0x????) Version: 1 Extends: alert version 1 This package defines signaling for CLASS features for an analog line. 4.1 Properties None. 4.2 Events None. 4.3 Signals Caller Identification SignalID: cid (0x0001) Sends the date, caller's name and caller's number to the CPE display, if the set is so equipped. Caller ID is unique in that it must be applied during alerting -- either power ringing, or call waiting. Therefore, this signal implies alerting, which will be appropriately applied to the CPE by the gateway, based upon the on-hook/off-hook status of the line. Signal Type: Brief Duration: Variable Additional Parameters: CID Data Block ParameterID: cdb (0x0001) Type: String Possible Values: See description. The CID Data Block contains the hex message data to be sent to the set. For example, in North America for basic Caller ID, this would be the SDMF or MDMF construct. The default value is an empty data block, which will be silently discarded by the gateway. Failure to transmit CID data for any reason, excepting Megaco message formatting errors, SHALL NOT generate an Error Descriptor. Call processing should proceed as if there had been no CID data in the first place. This includes errors in the data itself, or a bad checksum. Pattern Boyle & Brown Standards Track - Expires July 2001 4 Enhanced Alerting Packages for Megaco/H.248 January 2001 ParameterID: pattern (0x0002) Type: Enumeration Possible Values: 1 _ 10 (0x0001 - 0x000A) The pattern is an abstract indication of the distinctive alerting pattern that will be applied to the line. The cid pattern parameter maps to the ri pattern parameter for on-hook signaling, and to the cw pattern parameter for off-hook signaling. The default is pattern 1, which indicates the default alerting style. It is useful to note that ringing patterns and call waiting patterns are paired to allow for distinctive alerting sets. In expanding this parameter in the future, it would be desirable to expand the ri, cw, and cid signals together, maintaining the distinctive pattern pairings. This will continue to allow the cid signal to have a definition independent of alerting method, linking it only to the alerting style (pattern). Failure to apply the patterned signal SHOULD generate an Error Descriptor, as would any failed attempt to apply a signal. Analog Display Services Interface Signaling SignalID: adsi (0x0002) Sends ADSI data to sets that are so equipped. ADSI is used for advanced features such as context-specific softkeys, and in-phone visual data editing. Signal Type: Brief Duration: Variable Additional Parameters: ADSI Data Block ParameterID: adb (0x0001) Type: String Possible Values: See description. The ADSI Data Block contains the hex message data to be sent to the set. The default value is an empty data block, which will be discarded by the gateway. Failure to transmit ADSI data for any reason, excepting Megaco message formatting errors, SHALL NOT generate an Error Descriptor. Call processing should proceed as if Boyle & Brown Standards Track - Expires July 2001 5 Enhanced Alerting Packages for Megaco/H.248 January 2001 there had been no ADSI data in the first place. This includes errors in the data itself, or a bad checksum. 4.4 Statistics None. 4.5 Procedures There may be some confusion as to how to build the Signals descriptor when attempting to deliver Caller ID to the set. The class/cid signal is designed to stand alone, and be independent of on-hook/off-hook status. Ringing (via the alert package) for a normal call would have a signals descriptor that looks like this: Signals{alert/ri{pattern=1}} Now let's add Caller ID to the set. To apply standard ringing, and signal the Caller ID information the signals descriptor would look like this: Signals{class/cid{cdb=802301083035313831363135020A3931393939313 2363930070B4B6576696E20426F796C656C,pattern=1}} (For the record, this block is North American MDMF Caller ID signaling, indicating a call at 4:15 PM, May 18 from Kevin Boyle at (919) 991-2690. The checksum is included [6C].) This signaling implies both standard ringing, and any other signaling necessary to perform the Caller ID function. For the UK, for example, this signal requests that the gateway ringsplash the set, send the CID data, and then apply normal ringing. For North America, it requests that the gateway apply normal ringing, sending the CID data between the first and second ring. This would be similarly applied to Call Waiting ID. For normal call waiting, the tone is requested as follows: Signals{alert/cw{pattern=1}} To perform Call Waiting ID, the descriptor looks identical to the on-hook case: Signals{class/cid{cdb=802301083035313831363135020A3931393939313 2363930070B4B6576696E20426F796C656C,pattern=1}} This signaling implies both application of call waiting tone, and any other signaling necessary to perform the Caller ID function. For North America, it requests that the gateway apply call wait tone, then apply the CAS, and send down the Caller ID info after receipt of the ACK digit. If the gateway controller wants Boyle & Brown Standards Track - Expires July 2001 6 Enhanced Alerting Packages for Megaco/H.248 January 2001 notification of the ACK digit, it should be requested in the Events descriptor. Bulk Calling Line ID is handled in the same way as Caller ID. The default ringing pattern for the BCLID link termination should be datafilled to produce no ringing. Transmission of Caller ID would proceed as normal for onhook transmission without ringing. For ADSI, there are similar constraints around ACK digits and softkey/digit responses. Any responses that the gateway controller wishes to be made aware of should be requested in the Events descriptor. Digitmaps would be especially useful for this application. The binary encoding of the data blocks is the hex data they represent. 5. Formal Syntax 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 3 Cuervo, et al., "Megaco Protocol Version 1.0", RFC 3015, November 2000 8. Acknowledgments None 9. Author's Addresses Kevin Boyle II Nortel Networks 4008 Chapel Hill Road Research Triangle Park, NC USA 27709 Phone: (919) 991-2690 Boyle & Brown Standards Track - Expires July 2001 7 Enhanced Alerting Packages for Megaco/H.248 January 2001 Email: kboyle@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 Boyle & Brown Standards Track - Expires July 2001 8 Enhanced Alerting Packages for Megaco/H.248 January 2001 Full Copyright Statement "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 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." 10. Expiration Date This memo is filed as , and expires July 23, 2001. Boyle & Brown Standards Track - Expires July 2001 9