When configuring the IMG 2020 as an Application server, information such as Point Codes of other Application Servers and lists of Remote Signaling Gateways are needed. The M3UA DPC Route object is created under an Application Server (AS) stack. The DPC Route object is created under the stack object hat is being configured as an application server. Refer to the information below for more information on creating and configuring the M3UA DPC Route.
Web GUI Page
Dialogic > IMG 2020 > SS7 > SS7 Network > SS7 Stack (AS) > Destination > New M3UA AS Route
Maximum Objects
Up to 256 Routes per M3UA Application Server Stack
Related Topics and Dependencies
Must have Rem Signaling Gateways configured under SS7 AS Stack for Remote SG field to be populated
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
Route ID
The Route ID is automatically populated with the next Route ID available. To change the Route ID, click in the Route ID field and select a new Route ID from the drop down menu.
Remote SG
Click in the Remote SG field and a drop down menu appears displaying all the Remote Signaling Gateways created. Select which Remote Signaling Gateway from the Remote SG drop down menu to communicate with. This Remote Signaling Gateway is the Signaling Gateway that the Application Server stack will communicate with using M3UA/ISUP messaging through the sigtran links/associations.
Presume Available (Default: false)
When the IMG 2020 connects to a Signaling Gateway is it assumed that all routes or Point Codes in the Signaling Gateway are available.
false (Default) - When false is selected it is assumed that all routes in the Remote Signaling Gateway are NOT available.
true - When True is selected it is assumed that all routes in the Remote Signaling Gateway are available.