RFC 3064 on MGCP CAS Packages
RFC Editor <rfc-ed@ISI.EDU> Fri, 09 February 2001 01:10 UTC
Received: from loki.ietf.org (loki [10.27.2.29]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA22498; Thu, 8 Feb 2001 20:10:01 -0500 (EST)
Received: (from adm@localhost) by loki.ietf.org (8.9.1b+Sun/8.9.1) id TAA21561 for ietf-123-outbound.10@ietf.org; Thu, 8 Feb 2001 19:45:02 -0500 (EST)
Received: from ietf.org (odin.ietf.org [10.27.2.28]) by loki.ietf.org (8.9.1b+Sun/8.9.1) with ESMTP id TAA21411 for <all-ietf@loki.ietf.org>; Thu, 8 Feb 2001 19:24:09 -0500 (EST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA21824 for <all-ietf@ietf.org>; Thu, 8 Feb 2001 19:24:06 -0500 (EST)
Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by boreas.isi.edu (8.9.3/8.9.3) with ESMTP id QAA06491; Thu, 8 Feb 2001 16:24:06 -0800 (PST)
Message-Id: <200102090024.QAA06491@boreas.isi.edu>
To: IETF-Announce:;
Subject: RFC 3064 on MGCP CAS Packages
Cc: rfc-ed@ISI.EDU
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Thu, 08 Feb 2001 16:24:06 -0800
From: RFC Editor <rfc-ed@ISI.EDU>
A new Request for Comments is now available in online RFC libraries. RFC 3064 Title: MGCP CAS Packages Author(s): B. Foster Status: Informational Date: February 2001 Mailbox: bfoster@cisco.com Pages: 56 Characters: 116818 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-foster-mgcp-cas-packages-00.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3064.txt This document contains a collection of media gateway Channel Associated Signaling (CAS) packages for R1 CAS, North American CAS, CAS PBX interconnect as well as basic FXO support. Included are six packages. The "MS" package covers MF single stage dialing trunks. This includes wink start and immediate start PBX DID/DOD trunks as well as basic R1 and Feature Group D (FGD) Terminating protocol [3]. The "DT" package covers immediate start and basic DTMF and dial-pulse trunks and the "BL" package covers the interface to a basic PBX (digital or FXS interface). In addition to the Terminating protocol, there are three other FGD protocols described in [3]. These include EAIN and EANA which is covered by the enclosed "MD" package and the Operator Service Signaling protocol which is handled by the "MO" package. Support for basic FXO interconnect is provided by "DO" package. This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs.
- RFC 3064 on MGCP CAS Packages RFC Editor