idnits 2.17.1 draft-andreasen-mgcp-rfc2705bis-05.txt: Skipping this file; it looks like a tombstone file to me. -------------------------------------------------------------------------------- 1 A new Request for Comments is now available in online RFC libraries. 3 RFC 3435 5 Title: Media Gateway Control Protocol (MGCP) 6 Version 1.0 7 Author(s): F. Andreasen, B. Foster 8 Status: Informational 9 Date: January 2003 10 Mailbox: fandreas@cisco.com, bfoster@cisco.com 11 Pages: 210 12 Characters: 467084 13 Obsoletes: 2705 15 I-D Tag: draft-andreasen-mgcp-rfc2705bis-05.txt 17 URL: ftp://ftp.rfc-editor.org/in-notes/rfc3435.txt 19 This document describes an application programming interface and a 20 corresponding protocol (MGCP) which is used between elements of a 21 decomposed multimedia gateway. The decomposed multimedia gateway 22 consists of a Call Agent, which contains the call control 23 "intelligence", and a media gateway which contains the media 24 functions, e.g., conversion from TDM voice to Voice over IP. 26 Media gateways contain endpoints on which the Call Agent can create, 27 modify and delete connections in order to establish and control 28 media sessions with other multimedia endpoints. Also, the Call Agent 29 can instruct the endpoints to detect certain events and generate 30 signals. The endpoints automatically communicate changes in service 31 state to the Call Agent. Furthermore, the Call Agent can audit 32 endpoints as well as the connections on endpoints. 34 The basic and general MGCP protocol is defined in this document, 35 however most media gateways will need to implement one or more MGCP 36 packages, which define extensions to the protocol suitable for use 37 with specific types of media gateways. Such packages are defined in 38 separate documents. 40 This memo provides information for the Internet community. It does 41 not specify an Internet standard of any kind. Distribution of this 42 memo is unlimited. 44 This announcement is sent to the IETF list and the RFC-DIST list. 45 Requests to be added to or deleted from the IETF distribution list 46 should be sent to IETF-REQUEST@IETF.ORG. Requests to be 47 added to or deleted from the RFC-DIST distribution list should 48 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 50 Details on obtaining RFCs via FTP or EMAIL may be obtained by sending 51 an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 52 help: ways_to_get_rfcs. For example: 54 To: rfc-info@RFC-EDITOR.ORG 55 Subject: getting rfcs 57 help: ways_to_get_rfcs 59 Requests for special distribution should be addressed to either the 60 author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless 61 specifically noted otherwise on the RFC itself, all RFCs are for 62 unlimited distribution.echo 63 Submissions for Requests for Comments should be sent to 64 RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC 65 Authors, for further information.