Media gateway control protocol architecture

Last updated
Relationship of network components in a media gateway control protocol architecture Converged Network Architecture.png
Relationship of network components in a media gateway control protocol architecture

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). [1] 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).

Contents

The architecture divides the functions required for the integration of traditional telecommunication networks and modern packet networks into several physical and logical components, notably the media gateway, the media gateway controller, and signaling gateways. The interaction between the media gateway and its controller is defined in the media gateway control protocol.

Media gateway protocols were developed based on the Internet model of networking, the Internet Protocol Suite, and are referred to as device control protocols. A media gateway is a device that offers an IP interface and a legacy telephone interface and that converts media, such as audio and video streams, between them. The legacy telephone interface may be complex, such as an interface to a PSTN switch, or may be a simple interface to a traditional telephone. Depending on the size and purpose of the gateway, it may allow IP-originated calls to terminate to the PSTN or vice versa, or may simply provide a means to connect a telephone to a telecommunication system via an IP network.

Originally, gateways were viewed as monolithic devices that had call control, using protocols such as H.323 and the Session Initiation Protocol, and hardware required to control the PSTN interface. In 1998, the idea of splitting the gateway into two logical parts was proposed: one part, which contains the call control logic, is called the media gateway controller (MGC) or call agent (CA), and the other part, which interfaces with the PSTN, is called the media gateway (MG). With this functional split, a new interface existed between the MGC and the MG, requiring a framework for communication between the elements, resulting in the media gateway control protocol architecture.

SIP and H.323 are signaling protocols, while media gateway control protocols are device control protocols. The architectural difference between SIP and H.323, and the media gateway control protocols is that the relationships between entities in SIP and H.323 are peer-to-peer, while the relationships between entities in media gateway control protocols use the master/slave (technology) model. SIP and H.323 handle call setup, connection, management, and tear-down of calls between like interfaces, whereas media gateway control protocols define the mechanisms of setup of media paths and streams between IP and other networks. [2]

Implementations

Several implementations of the media gateway control protocol are in common use. The names of the best-known protocols 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 SIP, which both may be referred to as intelligent endpoint protocols. H.248/Megaco and MGCP may be referred to as device control protocols. [6] [7]

Other media gateway control protocols include the predecessors of MGCP, namely the Simple Gateway Control Protocol (SGCP) and the Internet Protocol Device Control (IPDC). A proprietary protocol using a similar architecture is the Cisco Skinny Client Control Protocol (SCCP).

Network elements

Media gateway

A media gateway is a device that converts media streams in the form of digital data or analog signals in telecommunication for services such as voice, video, and fax applications between two, usually dissimilar, interfaces using different technologies. One of the technologies usually is a packet, frame, or cell network. [1] For example, it may convert voice telephone calls between a traditional analog telephone to a digital format for transmission over an Internet Protocol (IP) network, to facilitate voice over IP communications.

Media gateway controller

A media gateway controller (MGC), also known as a call agent, controls the media gateways. It monitors the gateways for events, such as an off-hook state when a user intends to initiate a telephone call, and issues requests to the gateway to initiate or complete sessions, to alert the called party, or to terminate a call. The protocols used for this interaction between the gateway and its controller have evolved through various types and versions. The Simple Gateway Control Protocol (SGCP) and the Internet Protocol Device Control (IPDC) have been replaced by the Media Gateway Control Protocol (MGCP) and Megaco, which is also known as H.248.

Some MGCs interface with other signaling protocols, such as Signalling System No. 7 (SS7), for interconnection with the traditional telephone system, H.323, and the Session Initiation Protocol (SIP).

Protocols

The device control protocols evolved through several versions. MGCP emerged from a group now called the International SoftSwitch Consortium. This group started early with Level 3 Communications (through its acquisition of Xcom) and Telcordia (BellCore).

In July 1998, Telcordia (Bellcore) and Cisco Systems created a protocol called Simple Gateway Control Protocol (SGCP) for controlling Telephony Gateways from external call control elements. [8] Meanwhile, in mid-1998, Level 3 created a Technical Advisory Council (TAC), composed of a dozen leading communications equipment manufacturers. The TAC proposed a device protocol called Internet Protocol Device Control (IPDC) in August 1998. [9] IPDC was intended to be used between a media gateway and a media gateway controller. Media gateway were capable of acting as a voice over IP gateway, voice over ATM gateway, dialup modem media gateway, circuit switch, or cross- connect. In October 1998, Simple Gateway Control Protocol (SGCP) was combined with Internet Protocol Device Control (IPDC), resulting in MGCP. [10]

MGCP was submitted to the IETF’s MeGaCo working group in October 1998. [11] In November 1998, Lucent Technologies submitted a draft for third device protocol, called Media Device Control Protocol (MDCP) to use by media gateways and their controllers. [12] IETF merged MGCP and MDCP and proposed a new and improved protocol named MeGaCo protocol (also known as H.248) in April 1999. [13]

The first "official" version of MGCP is defined in RFC 2705 as informational. RFC 3435 obsoleted RFC 2705. MGCP currently is purely informational rather than a standard-track protocol, although it includes protocol specification. Even while MGCP was still an Internet Draft, many companies developed included MGCP with their own development rather than wait for a standardized protocol. Therefore, the decision was made to release MGCP as an informational RFC in October 1999. IETF development of MGCP has stopped, although companies continue to implement MGCP, [14] driven by the efforts of the PacketCable development of Network-based Call Signaling.

Further standardization of MGCP effort was pursued in the IETF, in the MEGACO working group, and also in the ITU-T/SG16, under the code name H.GCP. RFC 3015 standard tracks the MEGACO protocol (also H.248) and

The motivation of Megaco was the need to satisfy various requirements that were not addressed properly by MGCP.[ citation needed ] Megaco is an evolution of MGCP. It is a combination of MGCP and MDCP, and was published as Standard in RFC 3015 in November 2000. Megaco and MGCP are different and not interoperable.

H.248 (H.248.1 Gateway Control Protocol version 3) is published by International Telecommunication Union Telecommunication (ITU-T) as a protocol standard. The ITU-T has published three versions of H.248.1. The IETF published it as Gateway Control Protocol Version 1 in informational RFC 3525.

Both H.248 and MGCP are protocol for controlling media gateways using a media gateway controller or call agent. In a VoIP system, H.248 and MGCP are used with SIP or H.323. SIP or H.323 provide intercommunication between gateway controllers and MGCP is used to manage media establishment in the media gateways. [15]

Standards documents

See also

Related Research Articles

The Session Initiation Protocol (SIP) is a signaling protocol used for initiating, maintaining, and terminating real-time sessions that include voice, video and messaging applications. SIP is used for signaling and controlling multimedia communication sessions in applications of Internet telephony for voice and video calls, in private IP telephone systems, in instant messaging over Internet Protocol (IP) networks 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.

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.

Asterisk (PBX) 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.

Analog telephone adapter

An analog telephone adapter (ATA) is a device for connecting traditional analog telephones, fax machines, and similar customer-premises devices to a digital telephone system or a voice over IP telephony network.

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.

H.248

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.

An Internet telephony service provider (ITSP) offers digital telecommunications services based on Voice over Internet Protocol (VoIP) that are provisioned via the Internet.

VoIP phone

A VoIP phone or IP phone uses voice over IP technologies for placing and transmitting telephone calls over an IP network, such as the Internet. This is in contrast to a standard phone which uses the traditional public switched telephone network (PSTN).

A dial plan establishes the permitted sequences of digits dialed on subscriber or station lines with subscriber premises equipment, such as telephones and private branch exchange (PBX) systems. Dialing plans in the public switch telephone network (PSTN) have traditionally been more commonly referred to as dialing procedures. The dialing plan of a private telephone system or a customer premise equipment, such as an analog telephone adapter (ATA) or an IP phone, is sometimes also called dial plan. The digit sequences (numbers) permissible in a dialing plan may be as short as a single digit, e.g. for reaching an operator, or as long as a complete international telephone number, including trunk prefixes and international prefixes.

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.

Text over IP is a means of providing a real-time text (RTT) service that operates over IP-based networks. It complements Voice over IP (VoIP) and Video over IP.

H.323 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.

Internet Protocol Device Control (IPDC) is a 1998 specification of a communications protocol for voice over Internet Protocol (VoIP) telephony, developed by Level 3 Communications.

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

The Media Gateway Control Protocol (MGCP) is a signaling and call control communications protocol used in voice over IP (VoIP) telecommunication systems. It implements the media gateway control protocol architecture for controlling media gateways connected to the public switched telephone network (PSTN). 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).

References

  1. 1 2 Greene, N.; Ramalho, M.; Rosen, B. (April 2000). Media Gateway Control Protocol Architecture and Requirements. doi: 10.17487/RFC2805 . RFC 2805.
  2. ↑ "Understanding VoIP Protocols". packetizer.com. Retrieved 2012-06-07.
  3. ↑ Andreasen, F.; Foster, B. (January 2003). Media Gateway Control Protocol (MGCP) Version 1.0. doi: 10.17487/RFC3435 . RFC 3435.
  4. ↑ Groves, C.; Pantaleo, M.; Anderson, T.; Taylor, T. (June 2003). Gateway Control Protocol Version 1. doi: 10.17487/RFC3525 . RFC 3525.
  5. ↑ Taylor, T. (February 2008). Reclassification of RFC 3525 to Historic. doi: 10.17487/RFC5125 . RFC 5125.
  6. ↑ title=Use of MEGACO vis-à-vis MGCP to build a Gateway Solution
  7. ↑ "SIP core working group charter h2.48 history". packetizer.comg. Retrieved 2012-06-07.
  8. ↑ "Simple Gateway Control Protocol (SGCP". IETF. 30 July 1998. Retrieved 8 June 2012.
  9. ↑ "IPDC - Connection Control Protocol". IETF. August 1998. Retrieved 8 June 2012.
  10. ↑ "Level 3 Communications, Bellcore Announce Merger of Protocol Specifications for Voice Over IPe". Level 3 Communications. Retrieved 8 June 2012.
  11. ↑ "Media Gateway Control Protocol (MGCP)". IETF. 27 October 1998. Retrieved 8 June 2012.
  12. ↑ "Toward the PSTN/Internet Inter-Networking - MEDIA DEVICE CONTROL PROTOCOL". IETF. November 1998. Retrieved 8 June 2012.
  13. ↑ "MEGACO Protocol". IETF. 16 April 1999. Retrieved 8 June 2012.
  14. ↑ Collins, Daniel (September 22, 2000). "Chapter 6: Media Gateway Control and the Softswitch Architecture". Big Compilation Book With Many Chapters and distinct chapter authors. Book Publishers. pp.  239–240. ISBN   0071363262.
  15. ↑ "Media Gateway Control Protocol". telecomspace.com. Retrieved 2012-06-07.
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.