ABA-520-0701-EN SIGTRAN M2UA - Oracle Knowledge … · 3 2. Make settings in NTD: (1) Choose Media+ Signaling Gateways as SUT, green icons stand for SUT, blue icons stand for Abacus.

1

Spirent Abacus SIGTRAN M2UA 编号 版本 修改时间 说明

2

1. Network Topology

2. Abacus requirement 4 ICG cards: First ICG: used M2UA Switch (SSW)

Second ICG: used Clear Ch Exchange (MGC) Third ICG: used M2UA Exchange (SG) Fourth ICG: used MGCP Subscriber (MG)

3. Operation Steps Step1: Use first and second ICG cards to emulate SSW and MGC (Clear Ch exchange) in one environment:

1. Open Configure/protocol selection / card Panel, Make setting as follow.

3

2. Make settings in NTD: (1) Choose Media+ Signaling Gateways as SUT, green icons stand for SUT, blue icons stand for Abacus. Make M2UA configuration as following picture. (Sigtran-----Sigtran)

(2) Make MGCP TG setting as following picture.

4

(3) Make phonebook as follow.

Step2 Use third and fourth cards to emulate SG and MG in another environment:

1. Make setting in protocol selection panel.

5

2. Open Configure/ Network Topology Diagram window, Make settings in NTD:

6

Step3: Make settings in Partition & Timing: A: If need Media in the call, we only can make call from MGC (slot 2 card2/Clear Ch exchange) to SG, because SG (M2UA exchange) only can use “No voice” script, if we use SG as originator with media, there will be No path confirm errors.

B: If don’t need Media in the call, we can both use MGC (Clear Ch exchange) to call SG or use SG to call MGC. Please note the MG card only can be set as terminator. Above scenario looks loop back test, in actual test network, there should be some SS7 subscribers under SG, therefore, it is easily understand that we just use SG to call MGC or use MGC exchange to call SG, but not use MG to call MGC exchange.

7

Step4: Run this Demo Test.

4. Note: (1) This is a typical Sigtran scenario case, and it can be done with 4 ICG cards in our lab, so we can better understand sigtran through doing this test in our lab. (2) With media, we just can make a call from MGC exchange to SG. (3) Above configurations are based on v5.20.