IMG 1010 - Configure IMG as SG Server
Procedure:
The steps below describe how to configure the IMG 1010 as a Signaling Gateway as displayed in the diagram above. 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.
Initial Configuration:
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 SS7 MTP and M3UA stack:
In the procedure below the Application Servers that the IMG 1010 Signaling Gateway stack will connect to are third party Application Servers that are already configured. This procedure will not explain how to configure them but just how to configure the IMG Signaling Gateway 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. This stack will be used in the configuration of both the M3UA side and the Traditional SS7 tdm side. In the OPC field enter the point code for the stack. In the SCCP field select ANSI or ITU from drop down menu, and in the M3UA Service Mode field select Signaling Gateway Mode. See IMG 1010 - SS7 Stack for more information.
Right Click on the SS7 stack and select New Sigtran Links and the Sigtran Links ClientView Pane will appear. There is no configuration needed in this pane. This is a placeholder to be able to create multiple St-links under. See IMG 1010 - M3UA Sigtran Link
Right Click on Sigtran Links Pane and select New Sigtran Link. The Sigtran Link Pane will appear. Enter the following fields:
LinkID - This is automatically populated with next available ID
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 server 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 Application 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
See St-link Pane below.
Right Click on the Sigtran Links Pane again and create a second signaling link. This link will communicate with the second AS server in the Diagram. See Screen capture below.
Right Click on the SS7 stack and select New Remote Application Server (AS) and the Remote Application Server ClientView Pane will appear. Enter in the following fields. See IMG 1010 - M3UA Remote Application Server (AS) for more information
Application Server ID - This field is automatically populated with the next available ID.
Routing Context - Click in the Routing Context field and enter a value for the routing context. The routing context value entered should be the same as the Routing Context value of the remote M3UA Application Server this stack will be communicating with.
Comments (Optional) - Enter any comments that will identify this Remote Application Server
As of 10.5.3 SP6 the Routing Context parameter can be an empty value when Remote SG or Remote AS is configured.
In this example there are two Remote Application servers that the Signaling Gateway Server will communicate with. A second Remote Application Server Object must be created to communicate with the second Remote Application Server. See below
Once the Remote Application Server and Sigtran Links have been created the stack being created needs to be bound to a specific St-link and Remote Application Server. To do this, right click on the SS7 stack and select New Remote Application Server AS) Bind. A pane like below will appear. See IMG 1010 - M3UA Remote Application Server (AS) Bind for more information.
Remote Application Server - Select from drop down menu which Remote Application Server to bind
Sigtran Link - Select from drop down menu which St-link to bind to.
Primary/Secondary - Select which Signaling Gateway stack on the IMG to bind to. Select Primary or Secondary from drop down menu. If configuring a Standalone system, the field will default to Primary.
In this example there are two Remote Application Servers that will communicate with one Signaling Gateway. Right Click and add a second Remote Application Server Bind object that will bind a second St-link and second Remote Application Server to the Signaling Gateway Stack on the IMG. See screen capture below
The next step is to configure a Subsystem Number. The Subsystem number along with the St-link and Remote Application server adds to the routing information. Right Click on the SS7 stack and select New SSN - AS Route and the pane below will appear. See IMG 1010 - M3UA Subsystem Number AS Route for more information.
Remote Application Server - Select from a drop down menu containing all the Remote Application Servers configured under the SS7 stack. In this example Remote AS 0 was selected.
Subsystem Number - Select from drop down menu which Subsystem number to use.
Create a second Subsystem Number AS Route ClientView Pane for routing to the second Application Server. See Screen capture below.
Right Click on the SS7 stack and select New SCCP AS Designates. Select from drop down menu the Remote Application Server signaling will be sent to. See IMG 1010 - M3UA SCCP AS Designates for more information.
Remote AS for GTT - Select from drop down menu a Remote Application Server
Remote AS for SSN Wildcard - Select from drop down menu a Remote Application Server
The M3UA portion of this stack has been configured. The TDM side can now be configured on the same stack. To set up the Link Set, Links, and Routes for the TDM side, see IMG 1010 - Overview of SS7 Configuration - 10.5.1 and other pertinent documents located at IMG 1010 - SS7 (versions 10.5.1+) in this Wiki document.
The Signaling Gateway stack has been created and is communicating with the remote servers. Verify all stacks and links are In Service by viewing the Status bar which is the yellow bar at the bottom of the Stack, link, and St-link ClientView Panes. Below is screen capture of the ClientView object tree.
