MGCP is an extension of the earlier version of the protocol Simple Gateway Control Protocol (SGCP) and supports SGCP functionality
in addition to several enhancements. Systems using SGCP can easily migrate to MGCP, and MGCP commands are available to enable
An MGCP gateway handles translation between audio signals and the packet network. Gateways interact with a call agent (CA)--also
called a media gateway controller (MGC)--that performs signal and call processing on gateway calls. In the MGCP configurations
that Cisco IOS supports, a gateway can be a Cisco router, access server, or cable modem, and the CA is a server from a third-party
Configuration commands for MGCP define the path between the call agent and the gateway, the type of gateway, and the type
of calls handled by the gateway.
MGCP uses endpoints and connections to construct a call. Endpoints are sources of or destinations for data, and can be physical
or logical locations in a device. Connections can be point-to-point or multipoint.
Similar to SGCP, MGCP uses User Datagram Protocol (UDP) for establishing audio connections over IP networks. However, MGCP
also uses hairpinning to return a call to the PSTN when the packet network is not available.
A call connection involves a series of events and signals--such as off-hook status, a ringing signal, or a signal to play
an announcement--that are specific to the type of endpoint involved in the call.
MGCP groups these events and signals into packages. A trunk package, for example, is a group of events and signals relevant
to a trunking gateway; an announcement package is a group of events and signals relevant to an announcement server. MGCP supports
the following seven package types:
The trunk package and line package are supported by default on certain types of gateways. Although configuring a gateway with
additional endpoint package information is optional, you may want to specify packages for your endpoints to add to or override
MGCP provides the following benefits:
Alternative dial tone for VoIP environments--Deregulation in the telecommunications industry gives competitive local-exchange
carriers (CLECs) opportunities to provide toll bypass from the incumbent local-exchange carriers (ILECs) by means of VoIP.
MGCP enables a VoIP system to control call setup and teardown and Custom Local Area Subscriber Services (CLASS) features for
less sophisticated gateways.
Simplified configuration for static VoIP network dial peers--When you use MGCP as the call agent in a VoIP environment, you
need not configure static VoIP network dial peers. The MGCP call agent provides functions similar to VoIP-network dial peers.
Plain old telephone service (POTS) dial peer configuration is still required.