Use Case: Configuring Tmedia Gateways for M3UA SGP with IP PC

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

This configuration allows you act as a signaling gateway towards an M3UA ASP
There needs to be a point code defined for the SGP, but is not used externally

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 Configure an MTP3 Network Configure MTP3 Point Codes The following point code names are assigned: origination point code (OPC): 7.7.7 destination point code (DPC): 3.3.3 IP point code (IP PC): 1.1.1 Configure an MTP3 Linkset In this use case, there is one linkset: OPC: 7.7.7, DPC: 3.3.3 Configure MTP3 Links Configure an MTP3 Route In this use case, there are three routes needed: One route towards Customer switch (3.3.3) One local route (7.7.7) One route towards M3UA (1.1.1)	Configure IP Interface Defines local IP interface used to send SIGTRAN traffic	Configure SCTP Configure M3UA M3UA mode: SGP Create an M3UA SAP Remote is ASP mode 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, one peer server is needed towards the M3UA ASP Create an M3UA Route In this use case, two M3UA routes are needed: Route towards ASP: Psrv, 1.1.1, M3UA peer server above, M3UA Userpart=NONE, subservice=NONE Route towards Customer switch: MTP3, PC:3.3.3, M3UA Userpart, subservice=NONE