The Media GateWay Test Case
Click here to see this page in full context

The Media GateWay Test Case

Landslide Media Gateway supports the Mc Interface with H.248 codec. H248/MEGACO supports a separation of call control entities from bearer control entities and a separation of bearer control entities from transport entities. H.248 is used on the Mc interface between G(MSC) servers and the media gateway.

Abbreviations:

 

CS Core Network Logical Architecture

 

High Level View

 

 

                           

Phase-1 Test Scenario (PSTN/Wireline Network)

1.      In this test scenario for phase 1, MGW is the DUT, Landslide will emulate all the other nodal entities surrounding the MGW except the PSTN network part.

2.      The test will focus on the Mc interface which is based on H.248/MEGACO protocol and used to control the user plane bearer for call session, and the user plane transport interface between the MGW and IM-MGW which uses IP/UDP/RTP protocol.

3.      Landslide will not emulate the PSTN network part and the transport on the TDM circuit bearer between PSTN and MGW.

4.    Landslide will support the message sequences in above 4.3 Supported Procedures on the Mc interface to support bearer control for call session.

5.      IP/SCTP/H.248 will be supported on Mc interface and binary encoding ASN.1 for H.248 protocol will be supported.

6.      RTP over UDP over either IPv4 or IPv6 shall be used in the transport network user plane interface. The support of bearer transport without multiplexing shall be supported.

7.    Support mode will not be supported on the user plane.

8.    Bearer transport with multiplexing will not be supported on the user plane.

Test Cases (Phase 1)

In phase 1, two new test cases have been created: MGW Nodal and MGW Node. MGW Node is used to support back-to-back test.

MGW Nodal

1.     On MGW Nodal, the following test activities will be supported:

a)      Capacity;

b)      Session Loading.

2.     Call Establishment Configuration

3 patterns are supported to configure for the call establishment:

a)      All Originate;

b)      All Terminate;

c)      OTOT;

3.     Call Clearing Configuration

Three types of call clearing procedures will be supported to configure.

a)      Network Initiated

b)      User Initiated

c)      MSC Server Initiated

Besides, MGW Initiated Call Clearing is also supported on MGW Nodal.

4.     Traffic emulation is supported to configure on MGW Nodal.

a)      IP/UDP/RTP without multiplexing will be supported on the transport network user plane interface.

b)    rtpvoice DMF will be used to emulate the voice traffic between MGW and IM-MGW when the call bearer is established.

c)      The transparent mode will be supported on the user plane transport.

MGW Node

1.     MGW Node is to support back-to-back test.

2.     MGW will initiate MGW Registration to MGW Nodal.

3.   All three types of call establishment patterns will be supported.

4.   All three types of call clearing procedures will be supported, but we don’t support to emulate MGW initiated call clearing on our MGW Node.

5.     rtpvoice DMF will be used to emulate the voice traffic between MGW and IM-MGW when the call bearer is established.

 

Reference Documents:

3GPP TS 23.205 3GPP TS 23.231 3GPP TS 29.232   3GPP TS 29.414/415 3GPP TS 25.415   ITU-T Recommendation H.248.1 ITU-T Recommendation Q.1950 ITU-T Recommendation Q.1970

 

 

Learn more about:

Learn how to:

Measurements

Measurements collected for the MGW Nodal and MGW Node test cases are reported on the following tabs.