In the procedure below the Signaling Gateway Servers that the IMG 1010 Application Server stack will connect to are third party Signaling Gateway Servers that are already configured. This procedure will not explain how to configure them but just how to configure the IMG 1010 Application Server stack to connect/communicate with them.
- Right click on the IMG Name object in ClientView and select New Signaling. The Signaling Pane will appear. There is no configuration needed in this pane. This is a placeholder to be able to create SS7 signaling stacks. See IMG 1010 - Signaling Object for more information.
- Right Click on the Signaling object and select New SS7. An SS7 signaling pane will appear. Select whether this configuration will be a standalone or Redundant system. In this example, standalone was selected. See IMG 1010 - SS7 Signaling Object
- Right Click on the SS7 Signaling object created and select New SS7 Stack. An SS7 Stack 0 ClientView Pane will appear. Configure the following parameters to configure Stack 0 as an Application Server stack.
- OPC - Click in the OPC field and an Enter Point Code box will appear. Enter the point code for Application Server Stack 0. In this example 0-0-7 was selected.
- SCCP - Select ANSI if T1 or ITU if E1 from drop down menu
- M3UA Service - Select Application Server (AS) Mode from drop down menu.
- Create the St-links. Right Click on the Remote SG object just created and select New Sigtran Link. A Sigtran Link ClientView Pane will appear as shown below. Fill in the fields as needed. See IMG 1010 - M3UA Sigtran Link for more information.
- Link ID - The Link ID is automatically populated with the next available ID. To change the Link ID click in the Link ID field and select a new ID from drop down menu
- Primary/Secondary - Select whether the St-link will be a primary or secondary link.
- Network Appearance - Since this is a standalone setup, the Network Appearance is not needed
- Client/Server - Select whether the IMG will be server or client. In this example the default which is client was accepted.
- Source Port - Enter the Port Number to be utilized. The default port for local and remote ST-Links is 2905.
- Destination Port - Enter the port number of the remote Application Server that the St-link will be connecting to. The default port for local and remote ST-Links is 2905
- Local IP 1 - Select which interface on the IMG that the M3UA signaling will be utilizing.
- Remote IP 1 - Enter the IP address of the Remote Signaling Gateway Server interface that the St-link will be communicating with.
- Local IP 2 - If there is a second interface which would be used for Redundancy select from drop down menu the IP address of the second interface.
- Remote IP 2 - If redundancy is being configured, enter IP address of the remote application servers redundant IP interface
- Comments - Enter a comment to identify this St-link
- Right Click on the Signaling Gateway Stack being configured and select New DPC Route. Information such as Route ID, Destination Point Code, and Remote SG need to be configured in this pane. See IMG 1010 - M3UA DPC Route and ClientView Pane below for more information.
- Route ID - The Route ID is automatically populated with the next available ID. To change the Route ID click in the Route ID field and select new ID from drop down menu
- M3UA DPC - Click in the M3UA DPC field and an "Enter DPC" box will appear. Enter the Destination Point Code of a separate Application Server stack that the stack being configured will be communicating with through IP. In this example Application Server Stack 0 which has a Point Code of 0-0-7 will be communicating with Application Stack 1 which has a point code of 0-0-8. Therefore 0-0-8 which is the remote Application Server stack is input into this field.
- Remote SG - Click in the Remote SG field and a drop down menu displaying all the Remote Signaling Gateways created under the Application Server Stack. Select which Remote Signaling Gateway to communicate with.
- Presume Available
- False (Default) - When false is selected from drop down menu, it is assumed that all routes in the Remote Signaling Gateway are NOT available.
- True - When True is selected from drop down menu it is assumed that all routes in the Remote Signaling Gateway are available.