Media Gateway Control Part

Description

The Media Gateway Control Part (MGCP), defined in IETF RFC 3435 (obsoleted by RFC 3661), is a text-based master-slave protocol designed for controlling Media Gateways (MGWs) in a decomposed network architecture. In this model, the intelligence for call control resides in an external entity—a Media Gateway Controller (MGC), Call Agent, or Softswitch—while the MGW is a 'dumb' device responsible solely for media processing and switching. MGCP is the mechanism by which the controller commands the gateway to establish, modify, and terminate media connections. The protocol is transactional, with the controller sending commands (such as CreateConnection, ModifyConnection, DeleteConnection) and the gateway responding with acknowledgments and event notifications.

MGCP models a Media Gateway as a collection of endpoints and connections. Endpoints are sources or sinks of media data, which can be physical (like a DS0 timeslot on a T1 line) or virtual (like an RTP stream for packet audio). Connections are logical associations between endpoints to form a media path. The controller uses MGCP to instruct the gateway to place endpoints into contexts (which are like call legs or mixing points) and to specify how media should flow between them. The protocol also allows the controller to request the gateway to detect events (like DTMF digits, fax tones, or on-hook/off-hook transitions) and to generate signals (like dial tone, ringback, or busy signal). All call logic, including digit analysis, routing, and feature invocation, is handled by the controller; the gateway simply executes commands.

While MGCP was influential in early Voice over IP (VoIP) and softswitch deployments, 3GPP ultimately selected H.248/MEGACO as its standardized protocol for the Mc interface between the MGC/MGCF and the MGW/IMS-MGW. H.248 is a more robust and flexible successor, developed jointly by IETF and ITU-T. MGCP's architecture, however, directly informed the decomposed gateway model that became central to 3GPP's Core Network design in Release 99 and beyond. Understanding MGCP provides historical context for the evolution towards the fully standardized H.248 protocol used in modern networks.

Purpose & Motivation

MGCP was developed to address the need for a standardized interface to control relatively simple, low-cost media gateways from intelligent call control servers. Prior to its development, early VoIP gateways were often monolithic or used proprietary control protocols, leading to vendor lock-in and stifled innovation. MGCP emerged from the IETF's Megaco working group (and earlier work) to promote interoperability and accelerate the adoption of packet voice by separating the call control function, which could be implemented in software on standard servers, from the media processing function, which could be scaled independently.

Its creation was motivated by the telecom industry's shift towards packet-switched networks and the desire to replicate telephony services on IP infrastructure. MGCP solved the problem of how to control distributed media resources (gateways at the edge of the network) from a centralized point of intelligence, enabling new services and more efficient network designs. Although 3GPP later standardized on H.248 for its greater scalability and feature set (supporting multimedia and multiple control associations), MGCP played a crucial historical role in proving the decomposed gateway concept and was widely deployed in pre-IMS and early NGN architectures.

Key Features

• Text-based, transactional master-slave protocol for Media Gateway control
• Models gateways with endpoints (physical/virtual) and connections
• Commands include CreateConnection, ModifyConnection, DeleteConnection, and NotificationRequest
• Supports event detection (DTMF, hook-flash) and signal generation (tones, announcements)
• Enables centralized call control logic separate from distributed media processing
• Uses a straightforward command-response model over UDP or TCP

Evolution Across Releases

Defining Specifications