Media Gateway Control Protocol also known as MGCP is one of the implementations of the Media Gateway Control Protocol Architecture[1] for controlling media gateways on Internet Protocol (IP) networks and the public switched telephone network (PSTN). The general base architecture and programming interface is described in RFC 2805 and the current specific MGCP definition is RFC 3435 (obsoleted RFC 2705). It is a successor to the Simple Gateway Control Protocol (SGCP) which was developed by Bellcore and Cisco. In November 1998, Simple Gateway Control Protocol (SGCP) was combined Level 3 Communications Internet Protocol Device Control (IPDC), to form Media Gateway Control Protocol MGCP.[2]
MGCP is a signalling and call control protocol used within Voice over IP (VoIP) systems that typically inter-operate with the public switched telephone network (PSTN). As such it implements a PSTN-over-IP model with the power of the network residing in a call control center (softswitch, similar to the central office of the PSTN) and the endpoints being "low-intelligence" devices, mostly simply executing control commands. The protocol represents a decomposition of other VoIP models, such as H.323, in which the media gateways (e.g., H.323's gatekeeper) have higher levels of signalling intelligence.
MGCP uses the Session Description Protocol (SDP) for specifying and negotiating the media streams to be transmitted in a call session and the Real-time Transport Protocol (RTP) for framing of the media streams.
Another implementation of the Media Gateway Control Protocol Architecture which exists is the H.248/Megaco protocol, a collaboration of the Internet Engineering Task Force (RFC 3525) and International Telecommunication Union (Recommendation H.248.1). Both protocols follow the guidelines of the API Media Gateway Control Protocol Architecture and Requirements in RFC 2805. However, the protocols are incompatible due to differences in protocol syntax and underlying connection model.
Architecture
Gateway Control Protocol Relationship
The Media Gateway Control Protocol Architecture and its methodologies and programming interfaces are described in RFC 2805.[3]
MGCP is a master/slave protocol that allows a call control device such as Call Agent to take control of a specific port on a Media Gateway. In MGCP context Media Gateway Controller is referred to as Call Agent. This has the advantage of centralized gateway administration and provides for largely scalable IP Telephony solutions. The distributed system is composed of a Call Agent, at least one Media Gateway (MG) that performs the conversion of media signals between circuits and packets switched networks, and at least one Signaling gateway (SG) when connected to the PSTN (conversion from TDM voice to Voice over IP).
MGCP assumes a call control architecture where there is limited intelligence at the edge (endpoints, Media Gateways) and intelligence at the core Call Agent. The MGCP assumes that Call Agents, will synchronize with each other to send coherent commands and responses to the gateways under their control.
The Call Agent uses MGCP to tell the Media Gateway:
- what events should be reported to the Call Agent
- how endpoints should be connected together
- what signals should be played on endpoints.
MGCP also allows the Call Agent to audit the current state of endpoints on a Media Gateway.
The Media Gateway uses MGCP to report events (such as off-hook, or dialed digits) to the Call Agent.
(While any Signaling Gateway is usually on the same physical switch as a Media Gateway, this needn't be so. The Call Agent does not use MGCP to control the Signaling Gateway; rather, SIGTRAN protocols are used to backhaul signaling between the Signaling Gateway and Call Agent).
Multiple call agents
Typically, a Media Gateway is configured with a list of Call Agents from which it may accept programming (where that list normally comprises only one or two Call Agents).
In principle, event notifications may be sent to different Call Agents for each endpoint on the gateway (as programmed by the Call Agents, by setting the NotifiedEntity parameter). In practice, however, it is usually desirable that at any given moment all endpoints on a gateway should be controlled by the same Call Agent; other Call Agents are available only to provide redundancy in the event that the primary Call Agent fails, or loses contact with the Media Gateway. In the event of such a failure it is the backup Call Agent's responsibility to reprogram the MG so that the gateway comes under the control of the backup Call Agent. Care is needed in such cases; two Call Agents may know that they have lost contact with one another, but this does not guarantee that they are not both attempting to control the same gateway. The ability to audit the gateway to determine which Call Agent is currently controlling can be used to resolve such conflicts.
MGCP assumes that the multiple Call Agents will maintain knowledge of device state among themselves (presumably with an unspecified protocol) or rebuild it if necessary (in the face of catastrophic failure). Its failover features take into account both planned and unplanned outages.
Protocol overview
MGCP packets are unlike those generated by many other protocols. Usually wrapped in UDP port 2427, the MGCP datagrams are formatted with whitespace, much like you would expect to find in TCP protocols.
An MGCP packet is either a command or a response. Every issued MGCP command has a transaction ID and receives a response. Commands begin with a four-letter verb. Responses begin with a three number response code.
There are nine (9) command verbs:
AUEP, AUCX, CRCX, DLCX, EPCF, MDCX, NTFY, RQNT, RSIP
Two verbs are used by a Call Agent to query (the state of) a Media Gateway:
AUEP - Audit Endpoint AUCX - Audit Connection
Three verbs are used by a Call Agent to manage an RTP connection on a Media Gateway (a Media Gateway can also send a DLCX when it needs to delete a connection for its self-management):
CRCX - Create Connection DLCX - Delete Connection MDCX - Modify Connection
One verb is used by a Call Agent to request notification of events on the Media Gateway, and to request a Media Gateway to apply signals:
RQNT - Request for Notification
One verb is used by a Call Agent to modify coding characteristics expected by the "line-side" on the Media Gateway:
EPCF - Endpoint Configuration
One verb is used by a Media Gateway to indicate to the Call Agent that it has detected an event for which the Call Agent had previously requested notification of (via the RQNT command verb):
NTFY - Notify
One verb is used by a Media Gateway to indicate to the Call Agent that it is in the process of restarting:
RSIP - Restart In Progress
Implementations
Two implementations of the Media Gateway Control Protocol are in common use. The names of both are abbreviations of the protocol group:
Although similar in architecture, MGCP and H.248/Megaco are distinctly different protocols and are not interoperable. H.248/Megaco and MGCP protocols are complementary to H.323 and Session Initiation Protocol. Both H.323 and SIP can be referred to as "intelligent endpoint protocols". H.248/Megaco and MGCP can be referred to as "device control protocols".[7][8]
RFCs
- RFC 3435 - Media Gateway Control Protocol (MGCP) Version 1.0 (this supersedes RFC 2705)
- RFC 3660 - Basic Media Gateway Control Protocol (MGCP) Packages (informational)
- RFC 3661 - Media Gateway Control Protocol (MGCP) Return Code Usage
- RFC 3064 - MGCP CAS Packages
- RFC 3149 - MGCP Business Phone Packages
- RFC 3991 - Media Gateway Control Protocol (MGCP) Redirect and Reset Package
- RFC 3992 - Media Gateway Control Protocol (MGCP) Lockstep State Reporting Mechanism (informational)
- RFC 2805 - Media Gateway Control Protocol Architecture and Requirements
- RFC 2897 - Proposal for an MGCP Advanced Audio Package
See also
References
- ^ RFC 2805, Media Gateway Control Protocol Architecture and Requirements, N. Greene, M. Ramalho, B. Rosen, IETF, April 2000
- ^ "Level 3 Communications, Bellcore Announce Merger of Protocol Specifications for Voice Over IPe". Level 3 Communications. http://level3.mediaroom.com/index.php ?s=23600&item=65733. Retrieved 08 June 2012.
- ^ RFC 2805, Media Gateway Control Protocol Architecture and Requirements, N. Greene, M. Ramalho, B. Rosen, The Internet Society (April 2000)
- ^ RFC 3435, Media Gateway Control Protocol (MGCP) Version 1.0, F. Andreasen, B. Foster, The Internet Society (January 2003)
- ^ RFC 3525, Gateway Control Protocol Version 1, C. Groves, M. Pantaleo, T. Anderson, T. Taylor (editors), The Internet Society (June 2003)
- ^ RFC 5125, Reclassification of RFC 3525 to Historic, T. Taylor, The IETF Trust (February 2008)
- ^ |title=Use of MEGACO vis-à-vis MGCP to build a Gateway Solution
- ^ "SIP core working group charter h2.48 history". packetizer.comg. http://www.packetizer.com/ipmc/h248/h istory.html. Retrieved 2012-06-07.
External links
This article is based on material taken from the Free On-line Dictionary of Computing prior to 1 November 2008 and incorporated under the "relicensing" terms of the GFDL, version 1.3 or later.
