M3UA Remote Signaling Gateway - SG
The IMG 2020 can be configured to function as an Application Server in an M3UA network. The M3UA stack on the Application Server will communicate with the stacks created on a remote signaling gateway. The M3UA Remote Signaling Gateway object is created to configure any details needed to allow communication between the Application Server Signaling stack being configured on the IMG 2020 and the Remote Signaling Gateways M3UA stack. Refer to the information below
The Remote Signaling Gateway in the network accepts M3UA/ISUP messaging from the Application Server over the sigtran links/associations.Â
Web GUI Page
Dialogic > SS7 > SS7 Network > SS7 Stack (AS Mode) > New M3UA Remote SG
Â
Maximum Objects
16 Remote Signaling Gateway Objects per SS7 stack.
Related Topics and Dependencies
A stack must first be configured as a Application Server (AS) prior to being able to configure the Remote Signaling Gateway.
Links to M3UA Application Server Topics
Configure IMG 2020 as SG Server
M3UA Remote Application Server (AS)
M3UA Remote Application Server (AS) Bind
M3UA Subsystem Number AS Route
Links to M3UA Signaling Gateway Topics
Configure IMG 2020 as AS Server
M3UA Remote Signaling Gateway (SG)Â
Field Descriptions
Signaling Gateway ID
The Signaling Gateway ID is automatically populated with the next available ID. The ID identifies the Remote Signaling Gateway being configured. To change the ID, click in the Signaling Gateway ID field and a drop down menu with ID's available will appear. The drop down ID's range from 0 - 15.
Routing Context
To configure the Remote Signaling Gateway object, the Routing Context of the Remote Signaling Gateway must be known. The Routing Context number being configured needs to match up with the Routing Context number already configured in the Remote Signaling Gateway. Click in the Routing Context Field and enter the Routing Context Number.
The Routing Context parameter is an optional parameter and can be an empty value when Remote SG or Remote AS is configured.
Traffic Mode
This field is for redundancy situations only. Select the Traffic Mode from drop down menu.
Override (Default)Â - The Primary ASP (Application Server Process/M3UA stack) is active and the secondary is considered a backup.
Loadshare - Traffic is evenly distributed across all ASP's. (Broadcast Mode is not supported).
Â