You are here: CSP Developer’s Guide: Common Channel Signaling > 15 M3UA Implementation in the CSP > 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.
To activate any new feature, including M3UA Software, you must use a Product License Key, which Cantata 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 CSP 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
• 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:
|
Field |
Example (hex) |
|---|---|
|
AE - SS7 Slot |
21 |
|
OPC |
00FFFFFF |
|
Number of Modules |
03 (MTP, L3P, M3UA) |
|
Module 1 |
01 - MTP |
|
Module 1 Variant |
00 - ANSI ’97 |
|
Module 2 |
03 - Layer 3 Plus |
|
Module 2 Variant |
00 - ANSI ’97 |
|
Module 3 |
08 - M3UA |
|
Module 3 Variant |
00 - ANSI ’97 |
Adding M3UA Protocol Parameters
When adding M3UA protocol parameters, you need to use maps if the CSP is working with different types of networks. For example the CSP 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.
|
Field |
Example (hex) |
|---|---|
|
Address Method - Item |
03 |
|
Functional Area - Signaling |
67 02 00 01 |
|
Object Type - SS7 Stack |
64 02 10 00 |
|
Object Identifier - SS7 Stack ID |
65 02 00 00 |
|
Object Type - SIgtran M3UA |
64 02 10 20 |
|
Object Type - Sigtran M3UA Stack Parameter |
64 02 10 21 |
|
Object ID - -M3UA Stack ID |
65 02 00 00 |
|
Data Type - Number of TLVs |
00 02 |
|
Sigtran Command 0xE001 TLV |
E0 01 |
|
Length |
00 02 |
|
Add |
00 00 |
|
Data TLV - 0x9041 M3UA Protocol Parameters |
90 41 |
|
Length |
00 15 |
|
Default Standard |
00 00 00 01 |
|
Default Network Identity |
00 00 00 00 |
|
Number of MAPs |
01 |
|
MAPs Network Appearance |
00 00 00 01 |
|
MAPs Network Standard |
00 00 00 01 |
|
MAPs Network Identity |
00 00 00 00 |
Use the NGA Configure (0x0130) message type as described below. The example removes MAP 01.
|
Field |
Example (hex) |
|---|---|
|
Address Method - Item |
03 |
|
Functional Area - Signaling |
67 02 00 01 |
|
Object Type - SS7 Stack |
64 02 10 00 |
|
Object Identifier - Stack ID |
65 02 00 00 |
|
Object Type - Sigtran M3UA |
64 02 10 20 |
|
Object Type - Sigtran M3UA Stack Parameter |
64 02 10 21 |
|
Object ID - -M3UA Stack ID |
65 02 00 00 |
|
Data Type - Number of TLVs |
00 02 |
|
Sigtran Command TLV 0xE001 |
E0 01 |
|
Length |
00 02 |
|
Modify |
00 02 |
|
Sigtran Data TLV 0x9054 |
90 54 |
|
Length |
00 11 |
|
MAP Modify Option |
00 00 00 01 |
|
Remove 01 Map |
01 |
|
MAPs Network Appearance |
00 00 00 01 |
|
MAPs Network Standard |
00 00 00 01 |
|
MAPs Network Identity |
00 00 00 00 |
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.
|
Field |
Example (hex) |
|---|---|
|
Address Method - Item |
03 |
|
Functional Area - Signaling |
67 02 00 01 |
|
Object Type - SS7 Stack |
64 02 10 00 |
|
Object Identifier - Stack ID |
65 02 00 00 |
|
Object Type - Sigtran M3UA |
64 02 10 20 |
|
Object Type - Sigtran Remote Signaling Gateway Process |
64 02 10 29 |
|
Object ID - Remote Signaling Gateway Process |
65 02 00 01 |
|
Data Type - Number of TLVs |
00 02 |
|
Sigtran Command TLV 0xE001 |
E0 01 |
|
Length |
00 02 |
|
Add |
00 00 |
|
Signaling Gateway Process Add Data - Data TLV 0x9045 |
90 45 |
|
Length |
00 07 |
|
0B 59 |
|
|
Number of IP Addresses |
01 |
|
IP Addresses: 10.1.226.40 |
0A 01 E2 28 |
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 Sigtran Command TLV.
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..
|
Field |
Example (hex) |
|---|---|
|
Address Method - Item |
03 |
|
Functional Area - Signaling |
67 02 00 01 |
|
Object Type - SS7 Stack |
64 02 10 00 |
|
Object Identifier - Stack ID |
65 02 00 00 |
|
Object Type - Sigtran M3UA |
64 02 10 20 |
|
Object Type - Sigtran Remote Signaling Gateway |
64 02 10 27 |
|
Object ID - Remote Signaling Gateway |
65 02 00 01 |
|
Data Type - Number of TLVs |
00 02 |
|
Sigtran Command TLV 0xE001 |
E0 01 |
|
Length |
00 02 |
|
Add |
00 00 |
|
Signaling Gateway Add Data - Data TLV 0x9044 |
90 44 |
|
Length |
00 09 |
|
Traffic Mode: 01 Override; 02 Loadshare; 03 Broadcast |
00 00 00 01 |
|
Primary SGP ID |
00 01 |
|
Number of SGP |
01 |
|
First SGP ID |
00 01 |
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 Physical and logical connections for an overview of this concept.
Use the NGA Configure (0x0130) message type above but use the Remove (0x0001) value for the Sigtran Command TLV.
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.
|
Field |
Example (hex) |
|---|---|
|
Address Method - Item |
03 |
|
Functional Area - Signaling |
67 02 00 01 |
|
Object Type - SS7 Stack |
64 02 10 00 |
|
Object Identifier - Stack ID |
65 02 00 00 |
|
Object Type - Sigtran M3UA |
64 02 10 20 |
|
Object Type - Sigtran Route Set |
64 02 10 2A |
|
Object ID - Route Set |
65 02 00 01 |
|
Data Type - Number of TLVs |
00 02 |
|
Sigtran Command TLV 0xE001 |
E0 01 |
|
Length |
00 02 |
|
Add |
00 00 |
|
Sigtran Data First- Data TLV 0x9052 |
90 52 |
|
Length |
00 10 |
|
00 00 00 01 |
|
|
Number of Routes In current release, the maximum routes in the system is 255. |
00 01 |
|
Route ID |
00 01 |
|
Signaling Gateway ID |
00 01 |
|
Network Appearance |
00 00 00 01 |
|
Priority |
00 01 |
Use the NGA Configure (0x0130) message type as follows..
|
Field |
Example (hex) |
|---|---|
|
Address Method - Item |
03 |
|
Functional Area - Signaling |
67 02 00 01 |
|
Object Type - SS7 Stack |
64 02 10 00 |
|
Object Identifier - Stack ID |
65 02 00 00 |
|
Object Type - Sigtran M3UA |
64 02 10 20 |
|
Object Type - Sigtran Route Set |
64 02 10 2A |
|
Object ID - Route Set |
65 02 00 01 |
|
Data Type - Number of TLVs |
00 01 |
|
Sigtran Command TLV 0xE001 |
E0 01 |
|
Length |
00 02 |
|
Remove |
00 01 |
Use the NGA Configure (0x0130) message type as follows. The example removes route 1111.
|
Field |
Example (hex) |
|---|---|
|
Address Method - Item |
03 |
|
Functional Area - Signaling |
67 02 00 01 |
|
Object Type - SS7 Stack |
64 02 10 00 |
|
Object Identifier - Stack ID |
65 02 00 00 |
|
Object Type - Sigtran M3UA Protocol |
64 02 10 20 |
|
Object Type - Sigtran Route Set |
64 02 10 2A |
|
Object ID - Route Set |
65 02 00 01 |
|
Data Type - Number of TLVs |
00 02 |
|
Sigtran Command TLV 0xE001 |
E0 01 |
|
Length |
00 02 |
|
Modify |
00 02 |
|
Data TLV - 0x9053 Modify Destination |
90 53 |
|
Length |
00 10 |
|
Modify Option 00 00 00 01 - Remove Route Set |
00 00 00 01 |
|
Number of Routes |
00 01 |
|
Route ID |
00 01 |
|
Signaling Gateway ID |
00 01 |
|
Network Appearance |
00 00 00 01 |
|
Priority |
00 01 |
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..
|
Field |
Example (hex) |
|---|---|
|
Address Method - Item |
03 |
|
Functional Area - Signaling |
67 02 00 01 |
|
Object Type - SS7 Stack |
64 02 10 00 |
|
Object Identifier - Stack ID |
65 02 00 00 |
|
Object Type - Sigtran M3UA |
64 02 10 20 |
|
Object Type - Local Application Server Process |
64 02 10 24 |
|
Object ID - Application Server Process |
65 02 00 00 |
|
Data Type - Number of TLVs |
00 02 |
|
Sigtran Command TLV 0xE001 |
E0 01 |
|
Length |
00 02 |
|
Add |
00 00 |
|
Data TLV - 0x9043 Application Server Process |
90 43 |
|
Length |
00 08 |
|
Primary IP Address, B port of SS7: 135.119.48.82 |
87 77 30 52 |
|
Secondary IP Address A port of SS7 if not used |
00 00 00 00 |
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.
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.
|
Field |
Example Value (hex) |
|---|---|
|
Address Method - Item |
03 |
|
Functional Area - Signaling |
67 02 00 01 |
|
Object Type - SS7 Stack |
64 02 10 00 |
|
Object Identifier - Stack ID |
65 02 00 00 |
|
Object Type - Sigtran M3UA |
64 02 10 20 |
|
Object Type - Local Application Server |
64 02 10 22 |
|
Object ID - Application Server |
65 02 00 00 |
|
Data Type - Number of TLVs |
00 02 |
|
Sigtran Command TLV 0xE001 |
E0 01 |
|
Length |
00 02 |
|
Add |
00 00 |
|
Data TLV - 0x9042 |
90 42 |
|
Length |
00 25 |
|
Traffic Mode: 01 Override; 02 Loadshare; 03 Broadcast |
00 00 00 01 |
|
Routing Key Type - 00=DPC |
00 00 00 00 |
|
Routing Key Point Code |
00 00 00 01 |
|
Routing Key Network Appearance |
00 00 00 01 |
|
Routing Key Number of Ranges |
01 |
|
Routing Key Range OPC |
00 00 00 01 |
|
Routing Key Range SIO |
00 |
|
Routing Key SSN |
00 |
|
Routing Key Low CIC |
00 00 |
|
Routing Key High CIC |
00 01 |
|
Number of Application Server Processes |
01 |
|
ASP ID |
00 00 |
|
Number of routing contexts Up to 10 per Application Server (0-9) |
01 |
|
Routing Contexts |
|
|
Routing Contexts ID |
00 00 00 01 |
|
Signaling Contexts SG ID |
00 01 |
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.
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..
|
Field |
Example Value (hex) |
|---|---|
|
Address Method - Item |
03 |
|
Functional Area - Signaling |
67 02 00 01 |
|
Object Type - SS7 Stack |
64 02 10 00 |
|
Object Identifier - Stack ID |
65 02 00 00 |
|
Object Type - Sigtran M3UA |
64 02 10 20 |
|
Object Type - Sigtran Connection |
64 02 10 2B |
|
Object ID - Connection |
65 02 00 01 |
|
Data Type - Number of TLVs |
00 02 |
|
Sigtran Command TLV 0xE001 |
E0 01 |
|
Length |
00 02 |
|
Add |
00 00 |
|
Data TLV - 0x9046 Connection |
90 46 |
|
Length |
00 04 |
|
Application Server |
00 00 |
|
Signaling Gateway |
00 01 |
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 Sigtran Command TLV.