Configure IMG as SG Server







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:

  1. Configure Logical and Physical IMG Node. See Logical IMG and Physical IMG links.

  2. Configure T1/E1 facilities. See Configuring T1/E1 Bearer Profile and Configuring T1/E1 Bearer Spans or Configuring T1/E1 Signaling Spans.

  3. Configure the Network Interfaces

  4. Configure IP Bearer Profiles and IP Bearer Spans/VoIP Modules.


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.


  1. 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 Signaling link for more information.

  2. 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 SS7 Signaling link.

  3. 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 SS7 Stack for more information.




  1. 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 M3UA Sigtran Links.

  2. Right Click on Sigtran Links Pane and select New Sigtran Link. The Sigtran Link Pane will appear. Enter the following fields:

See St-link Pane below.




  1. 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.




  1. 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 M3UA Remote Application Server (AS) for more information




Note: As of 10.5.3 SP6 the Routing Context parameter can be an empty value when Remote SG or Remote AS is configured.


  1. 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




  1. 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 M3UA Remote Application Server (AS) Bind link for more information.





  1. 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




  1. 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 M3UA Subsystem Number AS Route for more information.






  1. Create a second Subsystem Number AS Route ClientView Pane for routing to the second Application Server. See Screen capture below.




  1. 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 M3UA SCCP AS Designates for more information.





  1. 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 the Overview of SS7 Configuration Link-10.5.1 and other pertinent documents located at Configuration > Signaling >SS7_10.5.1+ in this WebHelp document.

  2. 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.