Media Gateway Control Protocol (MGCP) Call Flows
draft-huitema-megaco-mgcp-flows-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Christian Huitema , Mauricio Arango , Flemming Andreasen , K Prakash | ||
| Last updated | 1999-02-17 | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
The Media Gateway Control Protocol (MGCP) organizes the communication between a Media Gateway controller, or call agent, and a Media Gateway, e.g. a Voice over IP gateway or a Network Access Server. MGCP is defined in a companion document [1]. This document provides example of MGCP usage by providing a variety of call flows, in the case of telephony and network access servers.
Authors
Christian Huitema
Mauricio Arango
Flemming Andreasen
K Prakash
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)