Configure IMG 2020 as AS Server
- Kelli Higdon
Â
Procedure
The steps below describe how to configure two stacks on the IMG 2020 as Application Servers and have then communicate with an existing remote Signaling Gateway Server. The procedure below assumes the remote Signaling Gateway Server has already been configured with the information such as Sigtran Links (Associations) to be able to communicate with the Application Servers being configured.Â
Initial Configuration
Refer to the link Basic Configurations to configure the initial objects that need to be created before proceeding on with the configuration of the M3UA stacks and associations. The Basic Configurations topic sets up objects such as T1/E1 Profiles, T1/E1 DS-1's and ANSI/ITU ISUP Group profiles needed prior to Configuring the SS7 m3ua stacks and associated functionality.
Configure SS7 Network and SS7 Node objects
In the procedure below the Signaling Gateway Servers that the IMG 2020 Application Server stack will connect to are third party Signaling Gateway Server that is already configured. This procedure will not explain how to configure the third party Signaling Gateway but just how to configure the IMG 2020 Application Server stack to connect/communicate with them.
Right click on the Dialogic object and select New SS7. The SS7 object is a parent or container object and no configuration is needed within this object. Refer to the SS7 - Signaling topic for more information.
Right click on the SS7 object and select New SS7 Network. Select a Network ID from the drop down menu. Refer to the SS7 - Network topic for more information on this object.
Right click on the SS7 Network object and select New SS7 Nodes. The Nodes object is a parent or container object and no configuration is needed in this object. Refer to the SS7 - Nodes topic for more information on this object.
Right click on the SS7 Nodes object and select New Primary Node. Within the Primary Node object select from the drop down menu which node will be utilizing the SS7 network that is being created. Refer to the SS7 - Nodes - Primary Node topic for more information on this object.
Configure the two M3UA Application Server Stacks
Configure the SS7 signaling stack and enter its Originating Point Code. Configure the stack as an M3UA Application Server (AS) stack. Follow procedure below.
Right click on the SS7 Network object and select New SS7 Stack. The Stack ID is automatically populated with next available number. Configure the following parameters to configure Stack 0 as an Application Server stack.
OPC | Click in the OPC field and enter the point code being given to the Application Server Stack ID: 0. In this example, 0-0-7 was selected. |
SCCP | Select ANSI if T1 or ITU if E1 from drop down menu |
M3UA Service Mode | Select Application Server (AS) Mode from drop down menu. |
Refer to the SS7 - Stack topic for more information about configuring the rest of the Stack fields.
Right click on the SS7 Stack with ID: 0 created above and select New M3UA Remote SG. The remote Signaling Gateway is an external Signaling Gateway that the Application Server Stack on the IMG 2020 will communicate with. Configure the Remote SG Pane. The Routing Context of the Remote Signaling Gateway is 15.
Field | Description |
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 be either the same as the Routing Context value of the remote M3UA Signaling Gateway Server this stack will be communicating with or can be left empty or blank. |
Traffic Mode | The Traffic Mode 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 Sigtran Links (Associations). Right Click on the Remote SG object just created and select New Sigtran Link (Sigtran Associations are called Sigtran Links in the Web GUI). Enter the information in the fields as needed.
Â
Field | Description |
Link ID (Association) | The Link ID (Association) is automatically populated with the next available ID. To modify the Link ID click in the Link ID field and select a new ID from drop down menu. |
Primary/Secondary | Select whether the Sigtran Link/Association will be a primary or secondary link. Since SS7 stack redundancy is not being configured, Primary is displayed and cannot be modified. |
Network Appearance | Since this is a single setup, the Network Appearance is not needed. |
Client/Server | Select whether the IMG 2020 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 Sigtran Links/Associations is 2905. |
Destination Port | Enter the port number of the remote Application Server that the Sigtran Link/Association will be connecting to. The default port for local and remote Sigtran Links/Associations is 2905. |
Local IP 1 | Select which interface (by IP Address) from the drop down list of configured IP addresses on the IMG 2020. This IP will be used for M3UA signaling. |
Remote IP 1 | Enter the IP address of the Remote Signaling Gateway Server interface that the Sigtran Link/Association will be communicating with. In this example, the remote signaling gateway is at IP address 10.129.39.80. |
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. |
Â
Refer to the M3UA Sigtran Link topic for more information on each of the individual fields.
Right click on the stack being configured and select New Destination. Enter the Destination Point Code of the Remote Application Server stack. Refer to the topic and Web GUI Page below for more information.
Â
Field | Â Description |
Destination ID | The Destination ID is automatically populated with the next available ID and cannot be modified. |
DPC | Click in the DPC field and enter the Destination Point Code that will be given to the second Application Server stack that will get configured later. 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. |
Â
This example has two Application Server stacks configured on the same IMG 2020. 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 through the Remote Signaling Gateway. The next few steps describes how to create the second Application Server. Right click on the SS7 Network object and select New SS7 Stack. An SS7 Stack object 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 ID:1 created above and select New M3UA Remote SG. The Remote Signaling Gateway is the same Gateway as configured above except the Routing Context for this stack will be set to 16. This is what the Remote Signaling Gateways routing context is set to as well.
Right click on the Remote SG object and select New Sigtran Link (Association). Configure the Sigtran Link/Association pane as displayed below. Note that since this link is connected to the Remote Signaling Gateway stack that is already configured, the Remote IP address field will have the same IP address as above.
The Source and Destination Ports were modified to be a different port than the ports configured above. The Source and Destination Ports needed to be different than that configured on the first Application Server. Refer to the screen capture below.
Right click on Stack ID:1 being configured and select New Destination. Enter the Destination Point Code of the first remote Application Server configured in this procedure. This is the point code of the initial M3UA stack. Refer to the M3UA SS7 Destination topic and Web GUI Page below for more information.
Â
The M3UA DPC is the Point Code of the first Application server stack.
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 Sigtran Link Web GUI Pages.
Configure SS7 ISUP Groups and CICs
Once the M3UA stacks are configured, the CICs must be configured to be able to communicate between the two application servers as displayed in diagram above. Follow instructions below to accomplish this.
Right Click on the SS7 Destination object of the application server stack ID:0 and select New SS7 Group. Select the correct ISUP Profile from the ISUP Profile drop down menu. Refer to the ISUP Group topic for more information on configuring this object.
Right click on the SS7 ISUP Group object and select New SS7 Circuit Group. Select the starting and ending spans that will be part of this circuit group that will carry the CICs. In this example Span 0 Channels 0-23 was selected.
Enter a Starting CIC number in the Starting CIC field.
Create CICs for the second Application server as well. Right Click on the SS7 Destination object of the application server stack ID:1 and select New SS7 Group. Select the correct ISUP Profile from the ISUP Profile drop down menu. Refer to the ISUP Group topic for more information on configuring this object.
Right click on the SS7 ISUP Group object and select New SS7 Circuit Group. Select the starting and ending spans that will be part of this circuit group that will carry the CICs. In this example Span 1 Channels 0-23 was selected.
Enter a Starting CIC number in the Starting CIC field. Verify the starting CIC in this CIC Group does not overlap the numbering of the CIC Group created for Application Stack ID:0
Right click on the Dialogic object and select New Routing Configuration. The Routing Configuration object is a container or Parent object and no configuration is needed here. Refer Routing Configuration link for more information.
Right click on Routing Configuration just created and select New Channel Groups. The Channel Groups object is a container object as well and no configuration is needed here. Refer to the Channel Groups link 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 Channel Group link for more information on configuring the SS7 Channel Group.
Right click on the Channel Group just created and select New Circuit Group. In the Starting and Ending Span/Channel fields, select the Spans that were configured in the 1st ISUP group configured. (Span 0, Channels 0-23)
Right click on the Channel Groups object again and select New Channel Group. Enter a name for the Channel Group and select SS7 as the Signaling Type. See Channel Group link for more information on configuring the SS7 Channel Group.
Right click on the Channel Group just created and select New Circuit Group. In the Starting and Ending Span/Channel fields, select the Spans that were configured in the 2nd ISUP group configured. (Span 1, Channels 0-23).
The Channel Group object will have a yellow exclamation point for an Icon. This indicates the configuration needs to be sent to the IMG 2020. Click on the Download Resource Tables button to send the configuration to the IMG 2020.
Once configured, the CIC's will come In Service. Verify this by viewing the Object Table below the Circuits object pane.
This procedure configures the Application Server Stacks on the same IMG 2020. The Application server stacks can also be created on separate IMG 2020's.