Media Gateway Control Protocol

Last updated

Media Gateway Control Protocol
Communication protocol
Purpose Voice over IP
Developer(s) Bellcore, Cisco, Level 3, IETF
Introduction1998;25 years ago (1998)
OSI layer Application layer (7)
RFC(s)
  • RFC   3435

The Media Gateway Control Protocol (MGCP) is a telecommunication protocol for signaling and call control in hybrid voice over IP (VoIP) and traditional telecommunication systems. It implements the media gateway control protocol architecture for controlling media gateways connected to the public switched telephone network (PSTN). [1] The media gateways provide conversion of traditional electronic media to the Internet Protocol (IP) network. The protocol is a successor to the Simple Gateway Control Protocol (SGCP), which was developed by Bellcore and Cisco, and the Internet Protocol Device Control (IPDC). [2]

Contents

The methodology of MGCP reflects the structure of the PSTN with the control over the network residing in a call control center softswitch, which is analogous to the central office in the telephone network. The endpoints are low-intelligence devices, mostly executing control commands from a media gateway controller, also called call agent, in the softswitch and providing result indications in response. The protocol represents a decomposition of other VoIP models, such as H.323 and the Session Initiation Protocol (SIP), in which the endpoint devices of a call have higher levels of signaling intelligence.

MGCP is a text-based protocol consisting of commands and responses. It 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 the media streams.

Architecture

Gateway Control Protocol Relationship Converged Network Architecture.png
Gateway Control Protocol Relationship

The media gateway control protocol architecture and its methodologies and programming interfaces are described in RFC 2805. [1]

MGCP is a master-slave protocol in which media gateways (MGs) are controlled by a call control agent or softswitch. This controller is called a media gateway controller (MGC) or call agent (CA). With the network protocol it can control each specific port on a media gateway. This facilitates centralized gateway administration and provides scalable IP telephony solutions. The distributed system is composed of at least one call agent and one or usually, multiple media gateways, which performs the conversion of media signals between circuit-switched and packet-switched networks, and at least one signaling gateway (SG) when connected to the PSTN.

MGCP presents a call control architecture with limited intelligence at the edge (endpoints, media gateways) and intelligence at the core controllers. The MGCP model assumes that call agents synchronize with each other to send coherent commands and responses to the gateways under their control.

The call agent uses MGCP to request event notifications, reports, status, and configuration data from the media gateway, as well as to specify connection parameters and activation of signals toward the PSTN telephony interface.

A softswitch is typically used in conjunction with signaling gateways, for access to Signalling System No. 7 (SS7) functionality, for example. The call agent does not use MGCP to control a signaling gateway; rather, SIGTRAN protocols are used to backhaul signaling between a signaling gateway and the call agents.

Multiple call agents

Typically, a media gateway may be configured with a list of call agents from which it may accept control commands.

In principle, event notifications may be sent to different call agents for each endpoint on the gateway, according to the instructions received from the call agents by setting the NotifiedEntity parameter. In practice, however, it is usually desirable that all endpoints of a gateway are controlled by the same call agent; other call agents are available 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 reconfigure the media gateway so that it reports to the backup call agent. The gateway may be audited to determine the controlling call agent, a query that may be used to resolve any conflicts.

In case of multiple call agents, MGCP assumes that they maintain knowledge of device state among themselves. Such failover features take into account both planned and unplanned outages.

Protocol overview

MGCP recognizes three essential elements of communication, the media gateway controller (call agent), the media gateway endpoint, and connections between these entities. A media gateway may host multiple endpoints and each endpoint should be able to engage in multiple connections. Multiple connections on the endpoints support calling features such as call waiting and three-way calling.

MGCP is a text-based protocol using a command and response model. Commands and responses are encoded in messages that are structured and formatted with the whitespace characters space, horizontal tab, carriage return, linefeed, colon, and full stop. Messages are transmitted using the User Datagram Protocol (UDP). Media gateways use the port number 2427, and call agents use 2727 by default.

The message sequence of command (or request) and its response is known as a transaction, which is identified by the numerical Transaction Identifier exchanged in each transaction. The protocol specification defines nine standard commands that are distinguished by a four-letter command verb: AUEP, AUCX, CRCX, DLCX, EPCF, MDCX, NTFY, RQNT, and RSIP. Responses begin with a three-digit numerical response code that identifies the outcome or result of the transaction.

Two verbs are used by a call agent to query the state of an endpoint and its associated connections.

Three verbs are used by a call agent to manage the connection to a media gateway endpoint.

One verb is used by a call agent to request notification of events occurring at the endpoint, and to apply signals to the connected PSTN network link, or to a connected telephony endpoint, e.g., a telephone.

One verb is used by an endpoint to indicate to the call agent that it has detected an event for which the call agent had previously requested notification with the RQNT command:

One verb is used by a call agent to modify coding characteristics expected by the line side of the endpoint:

One verb is used by an endpoint to indicate to the call agent that it is in the process of restarting:

Standards documents

Megaco

Another implementation of the media gateway control protocol architecture is the H.248/Megaco protocol, a collaboration of the Internet Engineering Task Force (RFC 3525) and the International Telecommunication Union (Recommendation H.248.1). Both protocols follow the guidelines of the overlying media gateway control protocol architecture, as described in RFC 2805. However, the protocols are incompatible due to differences in protocol syntax and underlying connection model.

See also

Related Research Articles

The Session Initiation Protocol (SIP) is a signaling protocol used for initiating, maintaining, and terminating communication sessions that include voice, video and messaging applications. SIP is used in Internet telephony, in private IP telephone systems, as well as mobile phone calling over LTE (VoLTE).

Voice over Internet Protocol (VoIP), also called IP telephony, is a method and group of technologies for the delivery of voice communications and multimedia sessions over Internet Protocol (IP) networks, such as the Internet. The terms Internet telephony, broadband telephony, and broadband phone service specifically refer to the provisioning of communications services over the Internet, rather than via the public switched telephone network (PSTN), also known as plain old telephone service (POTS).

The Skinny Client Control Protocol (SCCP) is a proprietary network terminal control protocol originally developed by Selsius Systems, which was acquired by Cisco Systems in 1998.

<span class="mw-page-title-main">Media gateway</span>

A media gateway is a translation device or service that converts media streams between disparate telecommunications technologies such as POTS, SS7, Next Generation Networks or private branch exchange (PBX) systems. Media gateways enable multimedia communications across packet networks using transport protocols such as Asynchronous Transfer Mode (ATM) and Internet Protocol (IP).

Inter-Asterisk eXchange (IAX) is a communications protocol native to the Asterisk private branch exchange (PBX) software, and is supported by a few other softswitches, PBX systems, and softphones. It is used for transporting VoIP telephony sessions between servers and to terminal devices.

A softswitch is a call-switching node in a telecommunications network, based not on the specialized switching hardware of the traditional telephone exchange, but implemented in software running on a general-purpose computing platform. Like its traditional counterparts it connects telephone calls between subscribers or other switching systems across a telecommunication network. Often a softswitch is implemented to switch calls using voice over IP (VoIP) technologies, but hybrid systems exist.

<span class="mw-page-title-main">Asterisk (PBX)</span> PBX software

Asterisk is a software implementation of a private branch exchange (PBX). In conjunction with suitable telephony hardware interfaces and network applications, Asterisk is used to establish and control telephone calls between telecommunication endpoints, such as customary telephone sets, destinations on the public switched telephone network (PSTN), and devices or services on voice over Internet Protocol (VoIP) networks. Its name comes from the asterisk (*) symbol for a signal used in dual-tone multi-frequency (DTMF) dialing.

The IP Multimedia Subsystem or IP Multimedia Core Network Subsystem (IMS) is a standardised architectural framework for delivering IP multimedia services. Historically, mobile phones have provided voice call services over a circuit-switched-style network, rather than strictly over an IP packet-switched network. Alternative methods of delivering voice (VoIP) or other multimedia services have become available on smartphones, but they have not become standardized across the industry. IMS is an architectural framework that provides such standardization.

<span class="mw-page-title-main">H.248</span>

The Gateway Control Protocol is an implementation of the media gateway control protocol architecture for providing telecommunication services across a converged internetwork consisting of the traditional public switched telephone network (PSTN) and modern packet networks, such as the Internet. H.248 is the designation of the recommendations developed by the ITU Telecommunication Standardization Sector (ITU-T) and Megaco is a contraction of media gateway control protocol used by the earliest specifications by the Internet Engineering Task Force (IETF). The standard published in March 2013 by ITU-T is entitled H.248.1: Gateway control protocol: Version 3.

A session border controller (SBC) is a network element deployed to protect SIP based voice over Internet Protocol (VoIP) networks.

PacketCable network is a technology specification defined by the industry consortium CableLabs for using Internet Protocol (IP) networks to deliver multimedia services, such as IP telephony, conferencing, and interactive gaming on a cable television infrastructure.

The next-generation network (NGN) is a body of key architectural changes in telecommunication core and access networks. The general idea behind the NGN is that one network transports all information and services by encapsulating these into IP packets, similar to those used on the Internet. NGNs are commonly built around the Internet Protocol, and therefore the term all IP is also sometimes used to describe the transformation of formerly telephone-centric networks toward NGN.

SIGTRAN is the name, derived from signaling transport, of the former Internet Task Force (I) working group that produced specifications for a family of protocols that provide reliable datagram service and user layer adaptations for Signaling System and ISDN communications protocols. The SIGTRAN protocols are an extension of the SS7 protocol family. It supports the same application and call management paradigms as SS7 but uses an Internet Protocol (IP) transport called Stream Control Transmission Protocol (SCTP), instead of TCP or UDP. Indeed, the most significant protocol defined by the SIGTRAN group is SCTP, which is used to carry PSTN signaling over IP.

Network-based Call Signaling (NCS) is a profile of the Media Gateway Control Protocol (MGCP) for use in PacketCable applications for voice-over-IP.

The Simple Gateway Control Protocol (SGCP) is a communications protocol used within a voice over Internet Protocol (VoIP) system. It has been superseded by the Media Gateway Control Protocol (MGCP), another implementation of the media gateway control protocol architecture.

<span class="mw-page-title-main">H.323</span> Audio-visual communication signaling protocol

H.323 is a recommendation from the ITU Telecommunication Standardization Sector (ITU-T) that defines the protocols to provide audio-visual communication sessions on any packet network. The H.323 standard addresses call signaling and control, multimedia transport and control, and bandwidth control for point-to-point and multi-point conferences.

T.38 is an ITU recommendation for allowing transmission of fax over IP networks (FoIP) in real time.

UNIStim is a deprecated Telecommunications protocol developed by Nortel for IP Phone and IP PBX communications.

<span class="mw-page-title-main">Media gateway control protocol architecture</span>

The media gateway control protocol architecture is a methodology of providing telecommunication services using decomposed multimedia gateways for transmitting telephone calls between an Internet Protocol network and traditional analog facilities of the public switched telephone network (PSTN). The architecture was originally defined in RFC 2805 and has been used in several prominent voice over IP (VoIP) protocol implementations, such as the Media Gateway Control Protocol (MGCP) and Megaco (H.248), both successors to the obsolete Simple Gateway Control Protocol (SGCP).

The Session Initiation Protocol (SIP) is the signaling protocol selected by the 3rd Generation Partnership Project (3GPP) to create and control multimedia sessions with two or more participants in the IP Multimedia Subsystem (IMS), and therefore is a key element in the IMS framework.

References

  1. 1 2 RFC 2805, Media Gateway Control Protocol Architecture and Requirements, N. Greene, M. Ramalho, B. Rosen, IETF, April 2000
  2. ↑ "Level 3 Communications, Bellcore Announce Merger of Protocol Specifications for Voice Over IP". Level 3 Communications. Retrieved 8 June 2012.
This page is based on this Wikipedia article
Text is available under the CC BY-SA 4.0 license; additional terms may apply.
Images, videos and audio are available under their respective licenses.