H.248

Last updated
H.248.1
Gateway control protocol
Converged Network Architecture.png
Relationship between network elements in a media gateway control architecture
StatusIn Force
Year started2000
Latest version(13/03)
Organization ITU-T, IETF
Related standardsH.248.2 ... H.248.98
Domain network architecture
Website https://www.itu.int/rec/T-REC-H.248.1

The Gateway Control Protocol (Megaco, H.248) 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. [1]

Contents

Megaco/H.248 follows the guidelines published in RFC 2805 in April 2000, entitled Media Gateway Control Protocol Architecture and Requirements. The protocol performs the same functions as the Media Gateway Control Protocol (MGCP), is however a formal standard while MGCP has only informational status. Using different syntax and symbolic representation, the two protocols are not directly interoperable. They are both complementary to H.323 and the Session Initiation Protocol (SIP) protocols. [2] [3]

H.248 was the result of collaboration of the MEGACO working group of the Internet Engineering Task Force (IETF) and the International Telecommunication Union Telecommunication Study Group 16. The IETF originally published the standard as RFC 3015, which was superseded by RFC 3525. The term Megaco is the IETF designation. Megaco combines concepts from MGCP and the Media Device Control Protocol (MDCP). [4] MGCP originated from a combination of the Simple Gateway Control Protocol (SGCP) with the Internet Protocol Device Control (IPDC). [5]

After the ITU took responsibility of the protocol maintenance, the IETF reclassified its publications as historic in RFC 5125. The ITU has published three versions of H.248, [1] the most recent in September 2005. H.248 encompasses not only the base protocol specification in H.248.1, but many extensions defined throughout the H.248 sub-series.

Protocol overview

3GPP / TISPAN IMS Architectural Overview. H.248 messages are used between Media Gateway Control Function (MGCF) control IMS - Media Gateways (IMS-MGW). SIP is used by MGCF to interact with Call Session Control Function (CSCF) and Breakout Gateway Control Function (BGCF) Ims overview-2.png
3GPP / TISPAN IMS Architectural Overview. H.248 messages are used between Media Gateway Control Function (MGCF) control IMS - Media Gateways (IMS-MGW). SIP is used by MGCF to interact with Call Session Control Function (CSCF) and Breakout Gateway Control Function (BGCF)

H.248/Megaco due to its master-slave nature does not describe the establishment of calls across domains or across media gateway controllers. H.248/Megaco is used for communication downward, to the media gateways and does not constitute a complete system. The architecture requires other protocols for communication between multiple MGCs.

The device that handles the call control function is referred to as an intelligent media gateway controller and the device that handles the media is referred to as a relatively unintelligent media gateway. H.248 defines the protocol for media gateway controllers to control media gateways for the support of multimedia streams across IP networks and the public switched telephone network (PSTN). It is typically used for providing Voice over Internet Protocol (VoIP) services like voice and fax between IP networks and the PSTN), or entirely within IP networks.

Because of the types of devices targeted for control by H.248/Megaco and the low level of its control structure, H.248 is generally viewed as complementary to H.323 and Session Initiation Protocol (SIP). While a media gateway controller (MGC) uses H.248/Megaco to manage media establishment and control with a number of media gateways (MGs), other VoIP protocols, such as SIP and H.323 are used for one communication between controllers. [3] From a SIP perspective, the combination of MGC and MGs are treated together as a SIP Gateway.


The H.248/Megaco model describes a connection model that contains the logical entities, or objects, within the Media Gateways (MGs) that can be controlled by the Media Gateway Controller. The main entities are Contexts and Terminations.


Terminations
These source or sink one or more media streams or control streams. Terminations may be physical or ephemeral
h.248 Connection Model ITU-T-h.248-connection-model.png
h.248 Connection Model
Contexts
These are star connections created by associating multiple terminations. A logical entity on an MG that is an association between a collection of Terminations. A NULL context contains all non-associated terminations. A Context is a logical entity on an MG that is an association between a collection of Terminations. A ContextID identifies a Context.
The normal, "active" context might have a physical termination (say, one DS0 in a DS3) and one ephemeral one (the RTP stream connecting the gateway to the network). Contexts are created and released by the MG under command of the MGC. A context is created by adding the first termination, and it is released by removing (subtracting) the last termination.
A termination may have more than one stream, and therefore a context may be a multistream context. Audio, video, and data streams may exist in a context among several terminations.

In IP Multimedia Subsystem (IMS), Media Gateway Control Function (MGCF) control Media Gateways (MGW)s to send and receive call to / from the PSTN circuit switched (CS) networks using. H.248. The MGCF uses SIP messages to interact with Call Session Control Function (CSCF) and Breakout Gateway Control Function (BGCF).

Although the modeling of the Media Gateway differs in H.248/Megaco when compared to MGCP, there is a similarity between the semantics of the commands in the two specifications. There is almost a one-to-one mapping between the commands of MEGACO and MGCP. For example, the Create connection command in MGCP has an equivalent ADD termination command in MEGACO, the Modify connection command in MGCP equates to the MODIFY termination command of MEGACO and the Delete connection command equates to the SUBTRACT termination command of MEGACO. [2]

Messages and commands

The Media Gateway Controller always manages the media channels available on the Media Gateway itself by managing specific contexts and terminations. When the call state changes, the MGC sends a corresponding message to the gateway and waits for an acknowledgment.

Each message is a transport mechanism for transmitting commands, and not the command itself, unlike most other telecommunication protocols.

Protocol Commands:


Typical MGC and MG message exchange

        Media Gateway                    Media        Controller                     Gateway     ISUP IAM (Start Call)                    | ------  ADD REQUEST ------> |              | <-------  ADD REPLY ------- |              | ------  RESPONSE ---------> |                  | -----  MODIFY REQUEST ----> |              | <------  MODIFY REPLY ----- |              | ------  RESPONSE ---------> |           ISUP ACM (Destination Number Received)                             | -----  MODIFY REQUEST ----> |              | <------  MODIFY REPLY ----- |              | ------  RESPONSE ---------> |                   | ----  MODIFY REQUEST -----> |              | <------  MODIFY REPLY ----- |              | -------  RESPONSE --------> |       ISUP ANM (Ring Back Tone)                 | -----  MODIFY REQUEST ----> |                  | <------  MODIFY REPLY ----- |              | -------  RESPONSE --------> |           CONNECTION PHASE   ISUP REL (End call)                 | ---  SUBSTRACT REQUEST ---> |              | <----  SUBSTRACT REPLY ---- |              | -------  RESPONSE --------> |   

Message structure

Message {Transaction {Action {Context {Command {Termination {Descriptor {Package}}}}}}}

By analogy with the OSI model, the hierarchy of interworking levels from the point of view of transmission over the network (Ethernet or ATM) is following.

H.248
TCP UDP SCTP
IP
Ethernet ATM

Comparison with MGCP

The H.248/Megaco model is more complex than the Media Gateway Control Protocol (MGCP) model and it provides more flexibility when defining media control. For example, in MGCP a call can use an endpoint mode conference to manage the stream mixing, but it cannot achieve the fine grain control of H.248/Megaco in managing the media streams.

The H.248/Megaco model simplifies connection setup within the MG and to entities outside the MG. It simplifies the mechanism by which the media gateway controller (MGC) can specify associated media streams as well as specify the direction of media flow. H.248/Megaco is therefore able to provide greater application level support than MGCP. For example, setting up a multi-party conference with H.248 merely involves adding several terminations to a context. In case o MGCP, however, the MGC needs to establish several connections to a special type of endpoint called the conference bridge.

Following are the main differences between Megaco/H.248 and MGCP:

H.248/MegacoMGCP
A call is represented by terminations within a call contextA call is represented by endpoints and connections
Call types include any combination of multimedia and conferencingCall types include point-to-point and multipoint
Encoding is text or binaryEncoding is text
Transport protocol is TCP, UDP or SCTP.Transport protocol is UDP.
Standard protocol for media gateway controlIETF status is Informational. MGCP does not specify an Internet standard
Defined by ITU (formerly by IETF and ITU)Managed by implementors, many independent protocol extensions exists.

Standards documents

ITU-T H.248 Recommendations

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).

E.164 is an international standard, titled The international public telecommunication numbering plan, that defines a numbering plan for the worldwide public switched telephone network (PSTN) and some other data networks.

Voice over Internet Protocol (VoIP), also called IP telephony, is a method and group of technologies for voice calls, the delivery of voice communication sessions over Internet Protocol (IP) networks, such as the Internet.

Telephone number mapping is a system of unifying the international telephone number system of the public switched telephone network with the Internet addressing and identification name spaces. Internationally, telephone numbers are systematically organized by the E.164 standard, while the Internet uses the Domain Name System (DNS) for linking domain names to IP addresses and other resource information. Telephone number mapping systems provide facilities to determine applicable Internet communications servers responsible for servicing a given telephone number using DNS queries.

<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).

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.

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.

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.

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.

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

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 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). 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).

<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 multiple participants in the IP Multimedia Subsystem (IMS). It is therefore a key element in the IMS framework.

References

  1. 1 2 "H.248.1 : Gateway control protocol: Version 3". International Telecommunication Union - Telecommunication. Retrieved 2016-07-12.
  2. 1 2 "Use of MEGACO vis-à-vis MGCP to build a Gateway Solution" (PDF).
  3. 1 2 "H2.48 history". packetizer.com. Retrieved 2012-06-07.
  4. "Toward the PSTN/Internet Inter-Networking - MEDIA DEVICE CONTROL PROTOCOL". IETF. November 1998. Retrieved 8 June 2012.
  5. "Level 3 Communications, Bellcore Announce Merger of Protocol Specifications for Voice Over IPe". Level 3 Communications. Retrieved 8 June 2012.