Configuring M3UA Software

Overview

Use the procedures in this section along with API Reference to configure M3UA software.

The procedures in this chapter includes an a description of the message and an example for each field. The header information is standard and is not included.

Activating M3UA Software

To activate any new feature, including M3UA Software, you must use a Product License Key, which Excel provides when you purchase the Product License. The key is unique and encrypted.

Follow the steps below:

1. Download the Product License to enable M3UA software.
The M3UA license key is provided as a text file: usually LICENSE.CFG or SERIALNO.CFG.

2. Send the Product License Key in the Product License ICB (0x24), within the Product License Download message (0x0079). This message identifies both the key type and the license authorization code associated with a specific feature. The key type for M3UA is 0x3132. The Excel platform verifies the key, then activates the feature.

3. You must download the license key each time new system software is downloaded or when you cycle the power.

Configuring the SS7 Stack

Prerequisites

• The SS7 Card must have the IP Address configured (See the IP Address Configure message in the API Reference.)

• CCS Redundancy must be configured. (See the CCS Redundancy Configure message in the API Reference.)

• The Object ID of the Application Server must match the Stack ID.

To configure the SS7 Signaling Stack to include M3UA use the SS7 Signaling Stack Configure 0x005C message with the SS7 Slot AIB as follows:

Adding M3UA Protocol Parameters

When adding M3UA protocol parameters, you need to use maps if the Excel platform is working with different types of networks. For example the Excel platform might be working in an international and national network at the same time. For each network you need to assign a different map. If you are not using maps, enter 0 in the Map Number field.

Use the NGA Configure (0x0130) message type to create a map and assign values for standard and network identity to the map.

Modifying Protocol Parameters

Use the NGA Configure (0x0130) message type as described below. The example removes Map 01.

Adding Signaling Gateway Process

You must configure all the Signaling Gateway Processes in the system and then configure the Signaling Gateways that use them. Note the following when adding Signaling Gateway Processes:

• A Signaling Gateway Process cannot be assigned to more than one Signaling Gateway.

• A Signaling Gateway can use up to two Signaling Gateway Processes.

• You can configure up to 20 Signaling Gateway Processes in the range 00-19.

Use the NGA Configure (0x0130) message type to add a Signaling Gateway Process.

Removing Signaling Gateway Processes

You must remove all connections to the Signaling Gateway Process before you remove it. Use the NGA Configure (0x0130) message type described above but use the Remove (0x0001) value for the Command TLV.

Adding Signaling Gateway

Once you configure all the Signaling Gateway Processes in the system, you can configure the Signaling Gateways that use them. Note the following when adding Signaling Gateways:

• A Signaling Gateway can use up to two Signaling Gateway Processes.

• You can configure up to 10 Signaling Gateways in the range 0-9.

• Use the NGA Configure (0x0130) message type to add a Signaling Gateway as indicated below. .

Removing Signaling Gateways

You must remove all connections to a Signaling Gateway before you remove it.

The Signaling Gateways are represented in the system by the sum of the logical connections that lead to it. Refer to Figure 1-1, Physical and logical connections (1-5) for an overview of this concept.

Use the NGA Configure (0x0130) message type above but use the Remove (0x0001) value for the Command TLV.

Adding Route Sets

Route Sets represent different ways to route a call through the network. Note the following when adding Route Sets:

• You can prioritize routes but you cannot load share.

• The signaling gateways associated with the route sets must exist before configuring the route sets.

• You can configure 64 route sets in the range 00 - 63. In the current release, the maximum number of routes in the system is 255.

Use the NGA Configure (0x0130) message type to add route sets as follows.

Removing Route Sets

Use the NGA Configure (0x0130) message type as follows. .

Modifying Route Sets

Use the NGA Configure (0x0130) message type as follows. The example removes route 1111.

Adding Application Server Process

You must configure the Application Server Processes before configuring the Application Servers that use them.

Note the following when adding Application Server Processes:

• Each Application Server Process should be assigned to a least one Application Server.

• You can configure two local Application Server Processes in the range 0-1.

• You can configure up to two IP Addresses per Application Server Process in the range 0-1.

Use the NGA Configure (0x0130) message type to add an Application Server Process as follows. .

Removing Application Server Processes

To remove the Application Server Process, you must follow the steps below:

1. Set an Application Server Process to inactive for all Application Servers that use it.

2. Remove all connections using this Application Server Process.

3. Disconnect the Application Server Process from all Signaling Gateway Processes on the Signaling Gateway side.

4. Remove the Application Server Process from all the Application Servers.

Adding Application Server

You must configure the Application Server Processes and Signaling Gateways before configuring the Application Servers that use them. Use the NGA Configure (0x0130) message type to add an Application Server.

Note the following when adding Application Servers:

• You can configure up to four Application Servers in the range 0-3.

• Each Application Server in the system must have a unique network appearance. The network appearance can have the same parameters (protocol type and network identity) but must have a unique number.

• The Object ID of the Application Server must match the Stack ID. In this example, they are both 00 01.

Removing Application Servers

You must stop all traffic to the Application Server by setting all the logical connections to inactive.

The inactive command should specify the Application Server that is going to be removed. This way the other Application Servers that are using the same Application Server Processes are not affected.

Adding a Connection

The Signaling Gateway Processes and Application Server Processes that will be connected should be configured before adding the connection.

You can configure 80 connections in the range 00-79.

Use the NGA Configure (0x0130) message type to add a connection. .

Removing Connections

Removing a connection is a configuration action not a control action. You must first must stop all traffic on the connection by setting the Application Server that uses the logical connection to Out of Service.

You can send an inactive command to each Application Server that uses the Application Server Process or to all Application Servers using one command.

Use the NGA Configure (0x0130) message type described above but use the Remove (0x0001) value in the Command TLV.