The steps below describe how to configure the IMG 1010 as an Application Server. The diagram above shows multiple application servers but this procedure explains how to configure only one. The procedure will not describe the initial few steps such as configuring facilities or profiles. This type of information is assumed to be already configured however links to some of these types of configuration will be provided.
- Configure Logical and Physical IMG Node. See IMG 1010 - Logical IMG and IMG 1010 - Physical IMG
- Configure the Network Interfaces. See IMG 1010 - Network Interface Scenarios Overview
- Configure T1/E1 facilities. See IMG 1010 - Configuring T1 or E1 Bearer Profile - 10.5.x and IMG 1010 - Configuring T1 or E1 Bearer Spans - 10.5.x and IMG 1010 - Configuring T1 or E1 Signaling Spans - 10.5.x
- Configure IMG 1010 - IP Bearer Profile and IMG 1010 - VoIP Resource
Configure M3UA Application Server Stack:
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.
See IMG 1010 - SS7 Stack for more information about configuring the rest of the Stack fields. (Non M3UA related)
- Right Click on the SS7 Stack 0 created above and select New Remote Signaling Gateway (SG). The remote Signaling Gateway is an external Signaling Gateway that the Application Server Stack on the IMG will communicate with. Configure the Remote SG Pane. The Routing Context of the Remote Signaling Gateway is 15 as shown below. See Below
- Signaling Gateway ID - This is automatically populated with next available ID. To change the ID, click in the Signaling Gateway field and select new ID from drop down menu
Routing Context - Click in the Routing Context field and enter a value for the routing context. The routing context value entered can either be the same as the Routing Context value of the remote M3UA Signaling Gateway Server this stack will be communicating with or be left empty or blank.As of 10.5.3 SP6 the Routing Context parameter can be an empty value when Remote SG or Remote AS is configured.
- Traffic Mode - This field is for redundancy situations only. The Default is Override. In Override mode, the Primary ASP is active and the secondary is considered a backup. In Loadshare Mode Traffic is evenly distributed across all ASP's. (Broadcast Mode is not supported). Select the Traffic 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.
- 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.
- 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.
- This example has two Application Server stacks configured on the same IMG 1010. In the first section of this procedure, the first Application Stack was created. The second portion of this example is to create the second Application server stack and configure it to communicate with the first. The next few steps describes how to create the second Application Server. Right Click on the SS7 Signaling object and select New SS7 Stack. An SS7 Stack 1 ClientView Pane will appear. Configure the following parameters to configure Stack 1 as the second Application Server stack in this example.
The OPC of this stack is 0-0-8 and the stack is configured as an Application Server.
- Right Click on SS7 Application Server Stack 1 created above and select New Remote Signaling Gateway (SG). The Remote Signaling Gateway is the same Gateway as configured above except the Routing Context is 16.
- Right Click on the Remote SG object and select New Sigtran Link. Configure the St-link pane as described above. Note that since this link is connected to the same Remote Signaling Gateway as described above. Note that the Source and Destination Ports needed to be different. See screen capture below.
- 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 ClientView Pane below.
- The two Application Server stacks have been created and are communicating with the remote Signaling Gateway. Verify all the links are Active by viewing the Status bar which is the yellow bar at the bottom of the St-link ClientView Panes.
Configure SS7 ISUP Groups and CICs:
Once the M3UA stacks are configured, the stacks must then be associated with a Channel Group/ISUP Group, and Bearer Span /Channel. Follow instructions below to accomplish this.
- Right Click on Dialogic IMG EMS object and select New Routing Configuration. See IMG 1010 - Routing Configuration Object for more information.
- Right Click on Routing Configuration just created and select New Channel Groups. See IMG 1010 - Channel Groups for more information.
- Right Click on the Channel Groups object and select New Channel Group. Enter a name for the Channel Group and select SS7 as the Signaling Type. See IMG 1010 - Channel Group for more information on configuring the SS7 Channel Group.
- Right Click on the Channel Group just created and select New ISUP Group. In the OPC-DPC field will be a drop down menu with the two Application Servers created above. Select Application Server Stack 0 (OPC=0-0-7). See screen capture below.
- Right Click on the ISUP Group and select New Circuits. Select the Spans/Channels to be used. See IMG 1010 - Circuit Group for more information
- Create a second Channel Group, ISUP Group, and Circuits Pane. The ISUP Group will have the OPC-DPC field of the second Application Server stack (0-0-8) created above and the circuit groups of both Application Server stacks must be physically connected.
- Once configured, the CIC's will come In Service. Verify this by viewing the 'Object Table' below the Circuits object pane in ClientView.
- Below is a screen capture of the object tree in ClientView. Note that this procedure configures the Application Server Stacks on the same IMG 1010. The Application server stacks can also be created on separate IMG 1010's.
Connect SS7 Stack to External Signaling Gateway
- The IMG 1010 can connect a traditional SS7 stack to an External Signaling Gateway also. See IMG 1010 - SS7 Stack for information on configuring SS7 stack. In this situation, there must be a physical connection for the link between the IMG 1010 and the external Signaling Gateway. Also there must be physical links between CIC's on the IMG 1010 in the SS7 network and CIC's configured on the Application Server Stack. See Network Diagram above.
- Below is screen capture of the ClientView object tree of a configured IMG 1010 connecting to IMG 1010 Application Server. Use diagram above for point codes etc.