Remote MTP3 Users

An RMU (Remote MTP3 User) represents a remote SCCP subsystem to which the Signaling Network Interface forwards signaling. When a message is forwarded from an MSC to an SS7-MP node, an RMU must be configured for the subsystem on the SS7-MP node.

There are two configuration scenarios for remote subsystems to which only service messages will be sent. A service message is a failure indication such as UDTS and XUDTS.

• If an MP must route signaling for UDT, XUDT, UDTS, or XUDTS to an RMU (such as a remote SCCP peer), then an RMU must be configured for that remote SCCP subsystem.
• For a remote SCMG (SCCP Management) subsystem, it is not necessary or possible to create an RMU. SCCP Management uses subsystem 1 instead. Subsystem 1 is automatically created at the time the message is forwarded.

If an RMU exists, the subsystem status is tracked and used for routing SS7 messages (including service messages).

STPs generally do not have subsystems and therefore do not need RMUs. An exception would be an application such as LNP (Local Number Portability) that can be hosted on an STP.

The SS7/Sigtran > Configuration > Remote MTP3 Users GUI page displays an entry for each MTP3 user to which SS7 SCCP signaling is sent, or for which status tracking is desired. The fields are used to populate the Called Party Address parameters.

The SS7/Sigtran > Configuration > Remote MTP3 Users GUI page also provides a link to the SS7/Sigtran > Maintenance > Remote MTP3 Users page, where you can view the status of each configured RMU and reset the subsystem and point code status of an RMU.