Use Case: Configuring Tmedia and TSG Gateways for M3UA SGSG Passthrough

Applies to version(s): v3.0 and above

This configuration allows you to pass transparently all packets destined to the service provider network represented by a Signaling gateway (SGP).
Note that the Point code is shared between the SGSG and the SGP device

Configure MTP2	Configure MTP3	Configure IP Interface	Configure M3UA
Configure MTP2 Configure MTP2 Link In this use case, one MTP2 link is needed, but more are supported	Configure MTP3 MTP3 mode: SP Advanced Parameters -> SG Passthrough mode: True Configure an MTP3 Network Configure MTP3 Point Codes The following point code names are assigned: origination point code (OPC): PC_B1 destination point code (DPC): PC_A1 Mask: PC_Mask (0.0.0) There is no need to define other PC (PC_A2, PC_A3, PC_B2, etc) Configure an MTP3 Linkset In this use case, there is one linkset: OPC: PC_B1, DPC: PC_A1 Configure MTP3 Links Configure an MTP3 Route In this use case, there are two routes needed: One local route towards Customer switch (PC_A1) One route towards M3UA (PC_B1)	Configure IP Interface Defines local IP interface used to send SIGTRAN traffic	Configure SCTP Configure M3UA M3UA mode: SGSG Advanced Parameters -> Link status relay: True Create an M3UA SAP Create an M3UA Network Create an M3UA User Part Create an M3UA Peer Signalling Process Configured as: Remote IP/Port for M3UA of STP/SGP Create an M3UA Peer Server In this use case, Two peer servers are needed: one local and one remote Create an M3UA Route In this use case, two M3UA routes are needed: Route towards SGP: Psrv, PC_Mask (0.0.0), M3UA peer server above, M3UA Userpart=NONE, subservice=NONE Route towards Customer switch: MTP3, PC:0.0.0 mask, M3UA Userpart, subservice=NONE