Installing Signalware 9

Steel-Belted Radius Carrier uses the Ulticom Signalware SS7 networking stack to communicate with SS7
networks. This chapter contains the basic Juniper Networks procedure that we recommend for a new
Signalware 9 with Service Pack 5T Installation. The installation example provided here is for your
convenience and assumes that this is a "clean" first time installation of Signalware.
These topics are in this chapter:
Beginning the Installation
Developing and Deploying SS7 Services
Configuring the Platform
Commission Instance
Configuring Nodes
Installing Signalware Service Pack 5T

5.4
Signalware provides a utility as part of its OLU packages to back up and save Signalware-specific
configuration files. They can be copied into the new Signalware 9 environment on the Release 7.0 server,
but they do require manual editing to make the appropriate changes to IP addresses, directory path
names, and other entries that change from server to server.
For more complete information about installing Signalware, moving existing configuration files from
another server, and re-installation of Signalware 9, refer to the Signalware Solaris Installation Manual.

Beginning the Installation

To install Signalware 9 with Service Pack 5T:
1

Log in as root.

Copy the Signalware 9 license file to the /etc directory.

To obtain a license file for Signalware 9, contact your Juniper Networks representative.

To find out information about your license, enter liceManViewer at a Solaris prompt.
Create a UNIX group called "users" and verify that the group exists.

To add a group, use the UNIX groupadd command.

$ groupadd users

To view a list of existing groups, use the UNIX cat command:

$ cat /etc/group
1

Create a UNIX user account called "siguser" as a member of the "users" group.

Copy the Signalware package from its location in your download directory or from a
Signalware CD to a temporary working directory (/export/local/siguser is used in the
example below).

Start the Signalware installation.

Execute:
swsetup
The script prompts for a user identifier.
1

Enter the unique user that you created in Step 3.

The script prompts for a scheduling priority.

1

Press Enter to accept the default value of 10.

The system checks for previous installations, a valid package file, and updates. Then it prompts for an
ECN Update.
1

Enter N.

The Main Menu screen is displayed.

Developing and Deploying SS7 Services

This group of steps installs the required software packages.
1

From the Main Menu, enter 1 to select "Signalware ... Develop/Deploy SS7 Services."

The Product Menu is displayed.

Enter 1 to select Signalware.

The Signalware Main Menu is displayed.

Enter 1 to select Install/Configure.

The Install/Configure menu is displayed.

Enter 3 to select Perform Initial Signalware Installation.

The script prompts for host names in a cluster.

1

Press Enter because this is a single node installation.

The Initial Install menu is displayed.

Enter 1 to select Install Packages.

The Select Instance screen is displayed and the script supplies the current (default) target directory.
1

Press Enter to accept the default target directory or specify an alternate location and
press Enter.

The script asks you to confirm the location.

1

Enter Y to continue.

The packages directory screen is displayed.

1

Enter the full path to the directory containing the packages.

The packages are validated and installed.

The Protocol Selection menu is displayed.
1

Select each protocol, in turn, that is appropriate to your location and system, and press Enter.

After each protocol is activated, the screen is displayed again. When all protocols have been selected,
type 0 and press Enter to continue.
The Interface Selection menu is displayed.
1

Type 1,3 to select SS7 and M3UA (SIGTRAN) because those are the interfaces supported by
Steel-Belted Radius Carrier and press Enter.

When the screen is redisplayed, type 0 and press Enter to continue.

The first page of the Select Packages menu is displayed.
1

Review the packages to be installed. (Generally, accept the defaults and do not deselect any
packages.
NOTE: The selected packages are based on the choices that you made in prior screens. We
recommend that you do not deselect any packages.

2
)
1

Type 0 and press Enter to accept the default selections and continue.

A confirmation screen is displayed.

1

Enter Y to confirm the selection of all packages and install them.

Status messages are displayed as the packages are installed.

1

When "Installation Complete" is displayed, press Enter to continue.

The More Packages screen is displayed, and you are prompted to indicate whether you are through
installing packages.
1

Enter Y.

The Initial Install screen is displayed.

Configuring the Platform

This group of steps configures the platform.
1

From the Initial Install screen, enter 2 to select Configure Platform.

The Configure Platform screen is displayed.

1

Enter 0 to accept the install directory that you entered earlier.

The Information Section screen is displayed.

1

Press Enter to accept the default "Yes" to answer the Continue with
configurePlatform procedure? prompt.

The CE Configuration screen is displayed.

Enter 1. (No other entry is supported.)

The UDP/TCP Port Configuration screen is displayed. It prompts you for a UDP port value.

We recommend that you press Enter to accept the default UDP port base value, but you may
enter an alternate.

The UDP/TCP Port Configuration screen prompts you for a TCP port value.
1

We recommend that you press Enter to accept the default TCP port base value, but you may
enter an alternate.

A confirmation screen prompts to apply the configuration.

Press Enter to accept yes, the default.
A "configurePlatform completed successfully" message is displayed.
1

Press Enter.

The Initial Install Screen is displayed.

Commission Instance
This set of steps installs drivers and configures the Signalware daemons.
1

From the Initial Install screen, enter 3 to select Commission Instance.

The Commission Instance screen is displayed, showing your install directory.

1

Enter 0 to accept the install directory that you entered earlier.

Status messages are displayed as the system is commissioned, then a "commission completed
Successfully" message is displayed.
1

Press Enter.

The Initial Install screen is displayed.

Configuring Nodes
This set of steps configures local nodes.
1

From the Initial Install screen, enter 4 to select Configure Nodes.

The Enter SHM screen is displayed.

Enter the shared memory value based on the user ID of the "siguser" user that you created
earlier (in Create a UNIX user account called "siguser" as a member of the "users" group.54).

To determine the user ID, open a new window and cat the /etc/passwd file as in this illustration:

The returned uid of 14583 is the value to enter in the Enter SHM screen.
The Signalware User screen is displayed.
1

Enter the username for running Signalware, siguser.

The Configure Nodes screen is displayed with the previously entered values in place.

Enter 0 to accept the values.

The How Many Nodes screen is displayed.

1

We recommend that you accept the default value of 1.

The Enter Node Name screen is displayed.

1

Enter the name of the node.

The Select Protocol screen is displayed.

Enter the protocol for the node.

The Select Protocol Type screen is displayed.

Enter the protocol type for the node. Choose 1 for SS7, 3 for SIGTRAN, or 1,3 for both.

The Select Options screen is displayed.

1

For most installations, enter 0 to continue.

Status messages are displayed as the node is configured.

1

The "Configure Nodes completed successfully" message is displayed.

The Initial Install screen is displayed.

1

Enter 6 to exit from the installation process without starting Signalware. (Do not start
Signalware at this point.)

The Install/Configure menu is displayed.

Return to the Main Menu and press 7 to exit.

A "You are about to exit..." confirmation message is displayed.

1

Enter N to exit from the installation process. (You want to exit at this point. You will start
Signalware later.)

A status message is displayed as the program shuts down, then the system prompt returns.

Installing Signalware Service Pack 5T

Installing Service Pack 5T builds on the example of a default Signalware 9 installation earlier in this
chapter.
This patch installation example uses the same user (siguser) and user group (users) information and
assumes that you have performed the base installation and configuration procedures documented earlier
in this chapter.

Installing the Patch Package

To add Service Pack 5T to a Signalware 9 installation:
1

Log in as root.

If you have not done so already, download and unpack the Signalware 9 Service Pack 5T file
(SIGNALWARE_9_SP5.T_SOLARIS10_UPGRADE.TGZ).

Copy the Signalware Service Pack 5T package file from its location in your download directory
or from a Signalware CD to a temporary working directory (/tmp/omni/5T is used in the
example below).

If Signalware is running, shut it down.

Start the Signalware installation.

Execute:
swsetup
The script prompts for a user identifier.
1

Enter the unique user that you created in the initial installation: siguser.

The Main Menu screen is displayed.

Welcome. This menu gives you options for different

Ulticom (R) products. Select
a product to get started.

HOST: mercury
sigusr (uid=0(root)
gid=0(root))

Ulticom (R) Product Menu

Signalware Main Menu

04 September 2008
18:15
1 = Install/Configure (Signalware is uninstalled or
off-line)
2 = Online Upgrade (Signalware is installed and
running)
3 = Installation Status and Reports
4 = Installation Maintenance
5 = Configuration Maintenance
6 = Start an Installed Instance of Signalware

>
Type 1-6 <enter>; <esc> or F11=Previous Menu;
F12=Help; ?<enter>=Status
1

Enter 1 to install the patch.

The Install/Configure screen is displayed.

Welcome. Signalware 9.02 or greater has been installed

on your system. All menu
options are available to you. Select an option to get
started. Remember,
additional help for each menu is available by typing F12
or entering "help" at
the prompt.
HOST: mercury
sigusr (uid=0(root)
gid=0(root))

Ulticom (R) Product Menu

Install/Configure

04 September 2008

18:15
1 = [ ]Limit Installations to a Single Instance
2 = [X]Allow Multiple Installation Instances of
Signalware
3 = Perform Initial Signalware Installation and
Configuration
4 = Replace Signalware (replace an existing
installation with new GA)
5 = Upgrade One of the Currently Installed Installation
Instances (SP or ECN)
6 = Clone a Currently Installed Instance and Upgrade
the Clone

>
Type 1-6 <enter>; <esc> or F11=Previous Menu;
F12=Help; ?<enter>=Status
1

Enter 5 to select the Signalware installation that requires the patch.

The Product Menu screen is displayed.

If you are working on a system with the default configuration, only one installation is listed.

The default behavior for installation allows multiple

installation instances
(Staged Installation). If you wish to restrict this
behavior, please select
option 1. Re-enable staged installation by selecting
option 2. To install for
the first time, select option 3. To delete and replace
an existing instance,
select option 4. To upgrade an instance, select option
5. To clone and upgrade
an instance, select option 6. More detailed descriptions
of these options are
available from the help menu. Remember, pressing F12 or
typing "help" at any

menu will display additional help.

HOST: mercury

Ulticom (R) Product Menu

sigusr (uid=0(root) gid=0(root))

Select Instance to Upgrade
04 September 2008 18:16
1 = (C) /opt/ulcm
>
Type 1-1 <enter>; <esc> or F11=Previous Menu;
F12=Help; ?<enter>=Status
1

Enter 1 to select the location of the Signalware 9 installation.

The Upgrade Instance screen is displayed.

Select the instance to upgrade.

"(C)" indicates the instance is commissioned while "(D)"
indicates
it is decommissioned or was never commissioned.
Please note, if you select the currently running
instance, (i.e. the
commissioned instance), you will be asked to terminate
Signalware
before installing the packages.
HOST: mercury
sigusr (uid=0(root)
gid=0(root))
/opt/ulcm
04 September 2008
18:16
1
2
3
4

=
=
=
=

[
[
[
[

]Install Packages
]Configure Platform
]Commission Instance
]Configure Nodes

Ulticom (R) Product Menu

Upgrade Instance

5 = [ ]Start Signalware
6 = Done
>
Type 1-6 <enter>; <esc> or F11=Previous Menu;
F12=Help; ?<enter>=Status
1

Enter 1 to install the package.

The Package Directory screen is displayed.

This path will perform an offline upgrade of an existing

instance. Begin by
selecting "Install Packages" to install Signalware in
the directory of your
choice. Remember, entering an option number followed by
-manpage or -help will
display the manpage for the corresponding command.
HOST: mercury
sigusr (uid=0(root)
gid=0(root))
/opt/ulcm
04 September 2008
18:16

Ulticom (R) Product Menu

Package Directory

Enter the directory path containing the packages to be

installed. This may be a
local or network path or the mount point for a CDROM or
DVD-ROM device. If the
packages to install are in more than one directory enter
the first directory to
install. You will be prompted for additional directory
paths after each set of
packages are installed.

>/tmp/omni/5T
Please enter directory containing the Signalware
software []:
1

Enter the path to the patch package file. In the screen above, /tmp/omni/5T is shown as
the location.

The Upgrade Instance screen is displayed after the patch is applied.

HOST: mercury
Ulticom (R) Product Menu
sigusr (uid=0(root) gid=0(root))
/opt/ulcm
Upgrade Instance
04 September 2008
18:17
1
2
3
4
5
6

=
=
=
=
=
=

[X]Install Packages
[ ]Configure Platform
[ ]Commission Instance
[ ]Configure Nodes
[ ]Start Signalware
Done

>
Type 1-6 <enter>; <esc> or F11=Previous Menu;
F12=Help; ?<enter>=Status
At this point, the patch has been applied. When you restart Signalware, the existing configuration is
invoked. Check both the Signalware and Steel-Belted Radius Carrier log entries to ensure that everything
is working properly.
1

Enter 6 -override (this is not a choice on the menu) to exit.

The Install/Configure screen is displayed.

>6 -override

Type 1-6 <enter>; <esc> or F11=Previous Menu;

F12=Help; ?<enter>=Status
You have completed the Configure Nodes step. Signalware
is now ready to run on this CE. To start
Signalware, select the "Start Signalware" option. You
will need to specify where the Signalware output
is to be displayed. The output may be displayed in a new
xterm by supplying a display value, to an
existing xterm or the console by supplying the device
file (ex. /dev/console) or to a file by supplying
the file name.
HOST: mercury
Ulticom (R) Product Menu
sigusr (uid=0(root) gid=0(root))
Install/Configure
04 September 2008 18:33
1 = [ ]Limit Installations to a Single Instance
2 = [X]Allow Multiple Installation Instances of
Signalware
3 = Perform Initial Signalware Installation and
Configuration
4 = Replace Signalware (replace an existing
installation with new GA)
5 = Upgrade One of the Currently Installed Installation
Instances (SP or ECN)
6 = Clone a Currently Installed Instance and Upgrade
the Clone

>Press Key "F11"

Type 1-6 <enter>; <esc> or F11=Previous Menu;
F12=Help; ?<enter>=Status
1

Press F11.

The Main Menu screen is displayed.

The default behavior for installation allows multiple

installation instances (Staged Installation). If
you wish to restrict this behavior, please select option
1. Re-enable staged installation by selecting
option 2. To install for the first time, select option
3. To delete and replace an existing instance,
select option 4. To upgrade an instance, select option
5. To clone and upgrade an instance, select
option 6. More detailed descriptions of these options
are available from the help menu. Remember,
pressing F12 or typing "help" at any
menu will display additional
help.
HOST: mercury
Ulticom (R) Product
Menu
sigusr (uid=0(root) gid=0(root))
Signalware Main
Menu
04 September 2008 18:34
1 = Install/Configure (Signalware is uninstalled or
off-line)
2 = Online Upgrade (Signalware is installed and
running)
3 = Installation Status and Reports
4 = Installation Maintenance
5 = Configuration Maintenance
6 = Start an Installed Instance of Signalware

>Press Key "F11"

Type 1-6 <enter>; <esc> or F11=Previous Menu;
F12=Help; ?<enter>=Status
1

Press F11.

The Product Menu screen is displayed.

Welcome. Signalware 9.02 or greater has been installed

on your system. All menu options are available
to you. Select an option to get started. Remember,
additional help for each menu is available by typing
F12 or entering "help" at the prompt.
HOST: mercury
Ulticom (R) Product Menu
sigusr (uid=0(root) gid=0(root))
Product Menu
04 September 2008 18:34
1 = Signalware ....................
Services
2 = nSignia .......................
Convergence
3 = Client/Server Client ..........
Client Components
4 = WLAN Libraries ................
Library Source
5 = Diameter ......................
IP Mobility Protocol
6 = Lower Layer Board (LLB) API ...
board
7 = Exit

Develop/Deploy SS7
SS7 and IP Networks
Client/Server
Authentication/SMS
Network Access or
ATM API for AMC

>7
Type 1-7 <enter>; <esc> or F11=Previous Menu;
F12=Help; ?<enter>=Status
1

Enter 7.

The Product Menu screen is displayed.

Welcome. This menu gives you options for different

Ulticom (R) products. Select a product to get
started.
HOST: mercury
Ulticom (R) Product Menu
sigusr (uid=0(root) gid=0(root))
Product Menu
04 September 2008
18:34
You are about to exit the Signalware Menu System. Are
you sure you want to exit? To continue using the
menu system enter Y. To exit enter N.

>
1

Enter N.

A confirmation prompt is displayed.

Would you like to continue the Signalware Menu System?

(Y/N)[Y]:
1

Press Enter to exit.

Configuring SS7/IP Network Communication Files

This chapter discusses configuring Signalware to communicate across SS7 gateways and configuring
SIGTRAN (provided as a module of Signalware) to allow SS7 communication over IP networks. These
topics are included in this chapter:

Configuring Communication Files Overview

Communication Pathways and Corresponding Files

Configuration Activities

Signalware MML Commands

Defining Links, Link Sets, and Route Sets

Configuring the authGateway Application for HLR Communication

Loading the MML Configuration Settings

SS7 Sample Configuration Files

Configuring Communication Files Overview

When configuring the communication pathways between Steel-Belted Radius Carrier and equipment in
the SS7 network, you need to configure certain files based on your choices of the following:
Type of network equipment Steel-Belted Radius Carrier communicates with for processing
authorization requests. (See Table 8 for information of which type of equipment is used.)

HLR

Type of network.

SS7

SS7 over IP (SIGTRAN)

Table 8: Network Equipment Used for Authorization
Action Needed to Process Access-Request

Network Equipment

Obtain SIM triplets

HLR

Obtain AKA quintets

HLR

Obtain IMSI (given the MSISDN)

HLR

Obtain MSISDN (given the IMSI)

HLR

Obtain Authorization string

HLR or database

NOTE: If quintets are received but triplets are needed, then Steel-Belted Radius Carrier converts
the quintets to triplets according to specification 3G TS 33.102, available
at http://www.3gpp.org.

Communication Pathways and Corresponding Files

Figure 4 shows the communication pathways between the Steel-Belted Radius Carrier server and the
network equipment. It also lists the files that need to be configured for each segment in the
communication pathways.

Figure 4: Steel-Belted Radius Carrier Libraries and Corresponding Configuration Files

Configuration Activities
To configure the communication pathways, perform the following activities.
1

Install Signalware. For details on the recommended procedure to install and run Signalware 9,
see Chapter 6, Installing Signalware 9.

Define links, link sets, and route sets with MML commands for SS7 or SIGTRAN. See Defining
Links, Link Sets, and Route Sets.

Configure the authGateway application for HLR communication. See Configuring the
authGateway Application for HLR Communication.

Load the MML configuration settings. See Loading the MML Configuration Settings.

Start Signalware.

Signalware MML Commands

After Signalware is installed, you can configure and provision Signalware using commands sent to the
Signalware system. For details about installing and running Signalware see Chapter 6, Installing
Signalware 9.
These commands are in a format called MML (Man-Machine Language). You can input MML commands
individually using the SWMML program, or save them in a file. The procedures in this chapter assume
that you save the MML commands to .mml text files and execute them as described in Loading the MML
Configuration Settings.
The basic activities that require MML commands are:
Setting up link sets, links, and routes See Defining Links, Link Sets, and Route Sets.
Configuring the authGateway location and startup information See Configuring the
authGateway Application for HLR Communication.
Loading the MML configuration settings See Loading the MML Configuration Settings.
You can view a list of all MML commands and definitions by entering:
$ man MML_Intro
You can view specific information about any MML command by typing man cmdname. For example:
$ man CRTE-LSET

Defining Links, Link Sets, and Route Sets

Links identify point-to-point connections of an adjacent node. Link sets are sets of parallel links that can
be used for load sharing. Routes identify the final node destination. (The order in which they are defined
is important.) Figure 5 provides a simple example of links, link sets, and route sets. In the case of a
SIGTRAN installation, the link set most likely consists of a single link because redundancy might not be
needed.
You use MML commands to set up links, link sets, and routes to identify the path between Steel-Belted
Radius Carrier, the adjacent link, and the final destination (HLR).
Setting up links, link sets, and route sets involves the MML commands listed in Table 9. For more
information about the syntax and usage of the MML commands, see Signalware MML Commands.

Table 9: MML Commands for Defining Links, Link Sets, and Route Sets
Action

MML Command for SS7

Networks

MML Command for SIGTRAN

Networks

Identify the local point code and

network indicator (NI)

CRTE-OSPC

CRTE-OSPC

Create a link set and assign it a point

code

CRTE-LSET

CREATE-M3UA-LSET

Create one or more links that belong to

the link set

CRTE-SLK

CREATE-M3UA-SLK

Create a route set that identifies the

final destination

CRTE-RSET

CRTE-M3UA-RKEY

Allow the route set to be used

ALW-RSET

ALW-RSET

Activate the links

ACTV-SLK

ACTV-SLK

Example MML Commands

The examples in this section illustrate the MML commands used to create links, link sets, and route sets.

Figure 5:

Links, Link Sets, and Route Sets

Figure 6: MML Provisioning

SS7 Example: Creating Links, Link Sets, and Route Sets

CRTE-OSPC:PC=14275,NI=NAT0;
CRTE-LSET:LSET=LSET1,PC=253;
CRTESLK:SLK=LNK1,LSET=LSET1,SLC=0,SPEED=64K,PORT=0,CHANNEL=1
7
CRTE-RSET:RSET=RSET1,PC=253,RTES=LSET1,LOADSHR=YES;
CRTE-RSET:RSET=RSET2,PC=61,RTES=LSET1,LOADSHR=YES;
ALW-RSET:RSET=RSET1;
ALW-RSET:RSET=RSET2;
ACTV-SLK:SLK=LNK1;
SIGTRAN Example: Creating Links, Link Sets, and Route Sets
CREATE-OSPC:PC=4004,NI=INT0;
CREATE-M3UA-LSET:LSET=IPLSET,TYPE=IPSP-IPSP, RADDR=207.46.20.60,PC=5005;

CREATE-M3UA-SLK:SLK=IPSLK,LSET=IPLSET,LADDR=72.5.124.61,RADDR=207.46.20
.60,MODE=CONNECT,LPORT=2906;
ACTIVATE-M3UA-SLK:SLK=IPSLK;
CREATE-RSET:RSET=IPRSET,PC=5005,RTES=IPLSET;
ALLOW-RSET:RSET=IPRSET;
CREATE-M3UA-RKEY:RKEY=RK1,TYPE=STATIC-AS,TRAFFIC-MODE=LOADSHARE,LSET=IP
LSET,DPC=4004,SI=SCCP,SSN=1&251&252;
ACTIVATE-M3UA-RKEY:RKEY=RK1;

Configuring the authGateway Application for HLR

Communication
The authGateway application manages all communication between Steel-Belted Radius Carrier and the
HLR. The authGateway application also implements the MAP (Mobile Application Port) protocol and MAP
messages that get sent through the Signalware protocol stack and out to the HLR and back.
Configuration of the authGateway application requires the activities described in the following sections of
this chapter:
Configuring the authGateway Routing Location Information
Configuring the authGateway.conf File
Configuring the authGateway Startup Information
Configuring the ulcmmg.conf File

Configuring the authGateway Routing Location Information

This activity assigns the local routing options and the remote routing options using the MML commands
listed in Table 10.
Table 10: MML Commands for Configuring authGateway Routing Location
MML
Command

Description

CREATE-CPC

Identify the concerned point code (CPC), which is the destination point code and the
local application (authGateway).

CREATEREMSSN

Identify the point code of the HLR and the remote application.

CREATE-GT

Create a global title translation for the remote HLR (if Global Title routing is used).

For more information about the syntax and usage of the MML commands, see Signalware MML
Commands.

Example 1 Global Title Routing Using Global Title Identification

In the following example, these actions take place:
Line 1 (CREATE-GT): Global Title type translation is used so that digits 22201 are sent to PC,SSN=61,6.
RI=GT tells 61,6 that it needs to find the next routing hop for the request.

CREATE-GT:TT=0,NP=ISDNMOB,NA=INT,DIG="22201",PC=61,SSN=6,RI=GT;
Example 2 PCSSN Routing Using Point Code Identification
In the following example, these actions take place:
Line 1 (CREATE-CPC): authGateway is assigned a subsystem number (SSN) of 7 on the local host and
the concerned point code on the HLR is identified as 61.
Line 2 (CREATE-REMSSN): The subsystem number (application) on the remote host is identified as 6.
Line 3 (CREATE-GT): Global Title type translation is used so that digits 22201 are sent to PC,SSN=61,6.
RI=PCSSN indicates that digits 22201 are handled by PC,SSN=61,6.

CREATE-CPC:PC=61,SSN=7;
CREATE-REMSSN:PC=61,SSN=6;
CREATE-GT:TT=0,NP=ISDNMOB,NA=INT,DIG="22201",PC=61,SSN=6,RI=PCSSN;

NOTE: MML commands are saved in MML files, which can be loaded into Signalware.
See Loading the MML Configuration Settings.

Configuring the authGateway.conf File

The authGateway.conf file specifies the remote routing and authorization options for the authGateway
application.
Remote routing options control how the remote HLR is addressed based on the incoming IMSI.
Authorization options control whether or not a subscriber requesting an account is authorized for
WLAN access, and which Steel-Belted Radius Carrier profile or native user is used.

Remote Routing Options

Each line in the authGateway.conf file represents a target HLR, where each HLR has its own routing
options and authorization options. Indicate each HLR listed in this file with the initial digits of the
subscriber password, specified by the odigits option.
Table 11 lists the remote routing options for the authGateway.conf file.
Table 11: authGateway.conf Remote Routing Options
Optio
n

Purpose

bs

Bearer Service. See Authorization Options.

msisd
n

The msisdn option can be used in place of ndigits and odigits when no translation is required.
See Example 2 authGateway.conf file.

ndigits

Replacement digits for numbering plan translation (hybrid IMSI).

odb

Operator-Determined Barring. See Authorization Options.

Initial digits of IMSI or password for this HLR. For each request, the first digits of the IMSI are
compared with odigits. The first line of the configuration file that matches is selected for the
current request.
If the routing indicator (rri) is 0 (Global Title), the leading digits are replaced with the new digits
(ndigits) to perform the numbering plan translation.

odigits

Example of direct replacement:

If the rule is "odigits 12345 ndigits 98765" and the IMSI is 123456789012345, the resulting
digits are 987656789012345.
Example of wildcard replacement:
If the rule is "odigits 12345* ndigits 98765" and the IMSI is 123456789012345, the resulting
digits are 98765.

rgti

(Global Title only) GTI value. 4 for C7; 2 for A7. (Usually 4.)

rnai

(Global Title only) Nature of Address Indicator.

(Global Title only) Numbering Plan.

Acceptable values are:
1 ISDN/Telephony
3 DATA
4 TELEX
rnp

5 Maritime Mobile
6 Land/Mobile
7 ISDN/Mobile
10 British Telecom special 1
11 British Telecom special 2
14 Private Network

rpc

Remote Point Code. Point Code of HLR.

rri

Routing indicator - 0 for GT (Global Title), 1 for PC/SSN (Point Code/Subsystem Number).

rssn

Subsystem Number of HLR.

rtt

(Global Title only) Translation Type (usually 0).

ts

Teleservice. See Authorization Options.

Authorization Options
The HLR database includes authorization information that is assigned to each subscriber. Three
authorization designations are relevant to Steel-Belted Radius Carrier with the SIM authentication
module:
BS (Bearer Service)
TS (Teleservice)

 ODB (Operator-Determined Barring)

You can specify subscriber HLR authorization (and barred service) designations in the MAP
Gateway authGateway.conf file.
NOTE: You can disable authorization completely from EAP-SIM (not fetch subscriber profile
information from the HLR and not perform a SQL/LDAP query). For instructions about disabling
authorization, see Disabling Authorization from EAP-SIM inChapter 18, Configuring SIM
Authentication, Steel-Belted Radius Carrier Reference Guide.

Each line in the authGateway.conf file corresponds to an HLR in your network. Each line also
specifies all potential authorization (and barred service) settings for any subscribers on this HLR.
Steel-Belted Radius Carrier with the SIM authentication module uses the service authorization information
that you list for each HLR in authGateway.conf:
When a TS or BS designation is assigned to a subscriber entry in the HLR database, SteelBelted Radius Carrier with the SIM authentication module permits the subscriber the
designated class of WLAN service upon authorization request.
When an ODB designation is assigned to a subscriber, Steel-Belted Radius Carrier with the SIM
authentication module denies the subscriber WLAN service upon authorization request.
When you do not specify service designations for a HLR listed in authGateway.conf, then all
subscribers on that HLR are authorized for WLAN service.
You can specify up to six authorization strings of each type (TS, BS, or ODB) on any given line
of authGateway.conf.
You can specify the service designations in authGateway.conf:
bs
ts

n1:auth1
n2:auth2

odb n3:auth3
Here, ni (i=1,2,3) is a decimal integer that specifies the setting, and authi (i=1,2,3) is the string
returned from the MAP Gateway to Steel-Belted Radius Carrier with the SIM authentication module.
For example, you might specify the potential subscriber designations on one HLR with the following text
in authGateway.conf:

bs 26:B1A ts 33:TS21 odb 128:bar

NOTE: If you require any HLR authorization strings to define different classes of service for your
subscribers, you must also specify those TS, BS, and ODB authorization strings in certain files
associated with the SIM authentication module. For information on how to match these strings to
Steel-Belted Radius Carrier variables, see the [ProfileMap] section in Chapter 21, Configuring
EAP-SIM and EAP-AKA Authentication, Steel-Belted Radius Carrier Reference Guide.

Example 1 authGateway.conf file

(Note: Lines are wrapped.)

odigits 2310 ndigits 2324 rnai 4 rnp 7 rgti 4 rtt 0 rri

0 rpc 3003 rssn 251 bs 12:gold
bs 23:silver ts 91:bronze ts 92:red ts 93:green odb
1:black aqua
odigits 31026 ndigits 32476 rnai 4 rnp 7 rgti 4 rtt 0
rri 1 rpc 3003 rssn 253 bs
23:morning bs 24:afternoon ts 1:night
Example 2 authGateway.conf file
(Note: Lines are wrapped.)
In this global title example, odigits and ndigits are the same and do not require translation. You can use
the msisdn option in place of ndigits and odigits when no translation is required.

msisdn 31026 rnai 4 rnp 7 rgti 4 rtt 0 rri 0 rpc 3003

rssn 251 bs 12:gold bs 23:silver
ts 91:bronze ts 92:red ts 93:green odb 1:black aqua

Configuring the authGateway Startup Information

The CREATE-PROCESS and START-PROCESS MML commands start the authGateway (by
calling authGatway.conf), using options that you specify.
Table 12 describes the MML commands needed to configure and start authGateway.
Table 12: MML Commands for Configuring the Start of authGateway

MML Command

Description

CREATE-PROCESS

Identify the authGateway configuration file and the authGateway options.

START-PROCESS

Start the process.

For more information about the syntax and usage of the MML commands, see Signalware MML
Commands. See Loading the MML Configuration Settings for information about executing the MML
commands.
Table 13 lists the options that you can use with the CREATE-PROCESS command.
Table 13: authGateway Process Options Used with CREATE-PROCESS
Option

Description

appctx

MAP protocol revision (2 or 3).

conf

Path and name of the authGateway configuration file. The default file
is OMNI_HOME/conf/authGateway.conf.
Sets a debug level. Use the following:

debug
-debug 0xff
host

Local hostname.

invkretry

Number of invoke retry.

invktimeout

Duration of invoke timeout in seconds.

lgti

(Global Title only) Local GTI value, usually 4 for C7 and 2 for A7.

lmsisdn

(Global Title only) MSISDN of this local node.

lnai

(GT only) Nature of Address Indicator. Indicates the scope of the address value, such

as whether it is an international number (includes country code) or a national number

(no country code).
1 Subscriber Number no area code (example: 5551234
2 unused
3 National Significant Number no country code (example: 2015551234)
4 International Number includes country code (example: 12015551234)
(Global Title only) Local Numbering Plan.
Acceptable values are:
1 ISDN/Telephony
3 DATA
4 TELEX
lnp

5 Maritime Mobile
6 Land/Mobile
7 ISDN/Mobile
10 British Telecom special 1
11 British Telecom special 2
14 Private Network

lpc

Local Point Code (PC).

lri

Routing indicator - 0 for GT (Global Title), 1 for PC/SSN.

lssn

Local Subsystem Number (SSN) (required).

ltt

(Global Title only) Local Translation Type. Generally in a live network TT is always 0.

max_request

The maximum number of simultaneous MAP dialogs.

monitor

Activates Message Activity Monitor.

name

Name of the process.

no rst

Disables automatic restart of process.

node

Node name.

port

Port number used by the SCTP association with the client.

prot

Variant used (C7, A7, or CH7).

trace

Enables debug tracing and displays the trace information on the console. (Consists of a
trace of all MAP messages that are formatted and sent down the stack.)
Use the tracefile option to capture the trace information to a file.

tracefile

Captures the trace information to a file. The filename follows the -tracefile switch.
Include the directory in the filename.

ExampleCreating and Starting the authGateway Process

Notice that the SSN=7 in the CREATE-CPC of the previous example (Example 1 in Configuring the
authGateway Routing Location Information) becomes the lssn (local subsystem number) in the CREATEPROCESS command of this example. The SSN=6 in the CREATE-REMSSN command of the previous
example (Example 1 in Configuring the authGateway Routing Location Information) becomes the -rssn
(remote subsystem number) in this example.
We recommend that the EXEC command use an absolute (full) pathname.
(Note: Lines are wrapped.)

CREATE-PROCESS:NAME="GMT", CE="sbrss7",
EXEC="/opt/JNPRsbr/radius/authGateway-name GMT -port
2000 -host sbrss7

-node MGW -prot C7 -conf

/opt/JNPRsbr/radius/conf/authGateway.conf -lri 0 -lpc
14275 -lssn 7 -rssn 6 -lmisdn 393558817298 -lgti 4 -lnp
7 -ltt 0 -lnai 4 -trace";
START-PROCESS:NAME="GMT", CE="sbrss7";
NOTE: MML commands are saved in MML files that can be loaded into Signalware. See Loading
the MML Configuration Settings.

Configuring the ulcmmg.conf File

The ulcmmg.conf file establishes the connection between the authGateway application and SteelBelted Radius Carrier.
The ulcmmg.conf file consists of two lines, as shown in the following example. Modify
the ulcmmg.conf file shipped with Steel-Belted Radius Carrier software so that the LOCAL_HOST
(Steel-Belted Radius Carrier server) and REMOTE_HOST (Signalware system) values identify their DNS
names and TCP port numbers. If you specify a DNS name for a local or remote host, you can enter the
host's IP address in brackets as a backup.

Example

LOCAL_HOST myhost.com:2001
REMOTE_HOST myhost.com:2000 [172.25.97.230]
For additional examples, see Sample authGateway Commands and Files.

Loading the MML Configuration Settings

The files containing MML commands need to be loaded into Signalware. Enter an SWMML command for
each .mml file that you created.
In the following example, three files are loaded into Signalware. The file called links.mml sets up the links,
link sets, and routes. The file called config_authgateway.mml configures the authGateway application.
The file called start_authgateway.mml configures the authGateway startup information.
These files do not exist and are used here as an example. You need to create your own files for
accomplishing the tasks of creating links, configuring the authGateway application, and starting the
authGateway application.

Example

$ swmml -node MGW -f links.mml

$ swmml -node MGW -f config_authgateway.mml
$ swmml -node MGW -f start_authgateway.mml

SS7 Sample Configuration Files

This section shows the sample configuration files for creating the basic SS7 connection to an HLR. These
sample files show how to set up one board with two SS7 links.

Basic Provisioning MML File with One Point Code/ Two SS7 Links
CRTE-OSPC:PC=9619,NI=NAT0;

CRTE-LSET:LSET=LSET1,PC=6400;

CRTESLK:SLK=LNK1,LSET=LSET1,SLC=0,SPEED=64K,PORT=0,CHANNEL=2;
CRTESLK:SLK=LNK2,LSET=LSET1,SLC=1,SPEED=64K,PORT=1,CHANNEL=3;

CRTE-RSET:RSET=RSET1,PC=6400,RTES=LSET1,LOADSHR=YES;

ALW-RSET:RSET=RSET1;

ACTV-SLK:SLK=LNK1;
ACTV-SLK:SLK=LNK2;
CREATE-GT:TT=0,NP=ISDNTEL,NA=INT,DIG="35840211430",PC=9619,SSN=0,RI=GT;
CREATE-GT:TT=0,NP=ISDNTEL,NA=INT,DIG="358",PC=6400,SSN=0,RI=DEF;
CREATE-GT:TT=0,NP=ISDNMOB,NA=INT,DIG="358",PC=6400,SSN=0,RI=DEF;

Notes:
TT usually 0.
NP 1=E.164=ISDN-TEL; 7=E.214=ISDN-MOB
NA INT
DIG Enter the first digits of MSISDN/IMSI. The routing decision is made with
"best match" method. The PC message is sent towards this Point Code if "digit"
matches the item specified as NP (ISDN-Tel).
Point codes in decimal format.

Routing Based on PC/SSN

CRTE-OSPC:PC=9619,NI=NAT1;

CRTE-LSET:LSET=LSET1,PC=11;
CRTESLK:SLK=LNK1,LSET=LSET1,SLC=0,SPEED=64K,PORT=0,CHANNEL=2
;
CRTESLK:SLK=LNK2,LSET=LSET1,SLC=1,SPEED=64K,PORT=1,CHANNEL=3
;
CRTE-RSET:RSET=RSET1,PC=11,RTES=LSET1,LOADSHR=YES;

CRTE-RSET:RSET=RSET2,PC=17,RTES=LSET1,LOADSHR=YES;

CRTE-RSET:RSET=RSET3,PC=18,RTES=LSET1,LOADSHR=YES;
CRTE-REMSSN:PC=17,SSN=6;

CRTE-REMSSN:PC=18,SSN=6;

ALW-RSET:RSET=RSET1;
ALW-RSET:RSET=RSET2;
ALW-RSET:RSET=RSET3;
ACTV-SLK:SLK=LNK1;
ACTV-SLK:SLK=LNK2;

CREATE-GT:TT=0,NP=ISDNTEL,NA=INT,DIG="35840299",PC=961,SSN=7,RI=PCSSN;
CREATE-GT:TT=0,NP=ISDNTEL,NA=INT,DIG="358402111",PC=17,SSN=6,RI=PCSSN;
CREATE-GT:TT=0,NP=ISDNTEL,NA=INT,DIG="358402112",PC=18,SSN=6,RI=PCSSN;

CREATE-GT:TT=0,NP=ISDNTEL,NA=INT,DIG="244911",PC=17,SSN=6,RI=PCSSN;
CREATE-GT:TT=0,NP=ISDNTEL,NA=INT,DIG="244912",PC=18,SSN=6,RI=PCSSN;
CREATE-GT:TT=0,NP=ISDNTEL,NA=INT,DIG="244913",PC=18,SSN=6,RI=PCSSN;
CREATE-GT:TT=0,NP=ISDNTEL,NA=INT,DIG="244914",PC=17,SSN=6,RI=PCSSN;
Redundant SS7 Links Backing Up Each Other (Two Point Codes)
CRTE-OSPC:PC=9619,NI=NAT0;
CRTE-LSET:LSET=LSET1,PC=6400;

CRTE-LSET:LSET=LSET2,PC=6401;
CRTE-SLK:SLK=LNK1,LSET=LSET1,SLC=0,SPEED=64K,PORT=0,CHANNEL=2;
CRTE-SLK:SLK=LNK2,LSET=LSET2,SLC=1,SPEED=64K,PORT=1,CHANNEL=3;
CRTE-SLK:SLK=LNK3,LSET=LSET1,SLC=2,SPEED=64K,PORT=16,CHANNEL=2;
CRTE-SLK:SLK=LNK4,LSET=LSET2,SLC=3,SPEED=64K,PORT=17,CHANNEL=3;
CRTE-RSET:RSET=RSET1,PC=6400,RTES=LSET1&LSET2;

CRTE-RSET:RSET=RSET2,PC=6401,RTES=LSET2&LSET1;
ALW-RSET:RSET=RSET1;
ALW-RSET:RSET=RSET2;
ACTV-SLK:SLK=LNK1;
ACTV-SLK:SLK=LNK2;
ACTV-SLK:SLK=LNK3;

ACTV-SLK:SLK=LNK4;
CRTE-GT:TT=0,NP=ISDN-TEL,NA=INT,DIG="358402114300",PC=9619,SSN=0,RI=GT;
CRTE-GT:TT=0,NP=ISDN-TEL,NA=INT,DIG="358",PC=6400,SSN=0,RI=GT,
BKUPPC=6401,BKUPSSN=0,BKUPRI=GT;

Sample authGateway Commands and Files

AS4StartMapGw.mml One Point Code/ Two SS7 Links

CRTE-PROCESS:NAME="GMT",CE="as1",EXEC="authGateway -name
GMT -port 2001
-host as1 -node MGW -prot C7 -conf
conf/authGateway.conf.100 -lri 0 -lgti 4 -lssn 7 -ltt 0
-lnp 1 -lnai 4 -appctx 2 -ldigits 358402114300";
START-PROCESS:NAME="GMT", CE="as1";
AS4StartMapGw.mml Routing Based on PC/SSN

CRTE-PROCESS:NAME="GMT",CE="as1",EXEC="authGateway -name
GMT -port 2001
-host as1 -node MGW -prot C7 -conf
conf/authGateway.conf.100 -lri 1 -lssn 7 -appctx 2
-ldigits 358402114300"; START-PROCESS:NAME="GMT",
CE="as1";
Table 14: Parameters Used in Create and Start Commands
Parameter

Description

name

Process name

port

Remote port specified in ulcmmg.conf

host

Hostname

node

Node name (used in swmml command)

prot

Variant used (C7, A7 or CH7). C7 in Europe

conf

Location of authGateway.conf file

lri

Routing indicator. 0=GT, 1=PC/SSN

lgti

(GT only) Local GTI value, 4 for C7 network; 2 for A7

lssn

Local Subsystem Number (SSN)

lnp

1=ISDN/Telephony

lnai

Nature of Address Indicator. (4=INT)

appctx

MAP version (2 or 3) to be used

ldigits

GT number for SIM Authentication module itself

NAME

Process name

CE

Hostname (CE means computing element)

EXEC

Program to be executed

authGateway.conf (Gateway routing configuration file)

Each line of this configuration file describes:
The parameters used to form the destination SCCP address.
The decimal value of the bearer service (bs) and/or teleservices (ts) indicating an authorization.

 A string associated with each bs or ts value. If no bs and no ts are specified, no authorization is

performed by the authGateway.
For each request, the first digits of the IMSI are compared with odigits. The first line of the
configuration file that matches is selected for the current request. If the routing indicator (rri) specifies that
the routing is done on GT, the leading digits are replaced with the new digits (ndigits) to perform the
numbering plan translation. If a parameter is not present on the line, it is not present in the SCCP
destination address. If this is incompatible with the routing indicator, an error message is issued when the
MAP authentication Gateway is started.
After modifying this configuration file, the authGateway has to be restarted. Modification of
the ndigits value may require the creation of a new GT rule (CREATE-GT command).

odigits 24491 ndigits 35840 rri 0 rgti 4 rssn 6 rtt 0

rnp 7 rnai 4 bs 17:B11 bs
26:B1A ts 33:T21 odb 128:NotAuthorized ss
146:NotAuthorized
odigits 244911 ndigits 244911 rri 1 rpc 17 rssn 6 bs
17:B11 bs 26:B1A ts 33:T21
odb 128:NotAuthorized ss 146:NotAuthorized
odigits 244912 ndigits 244912 rri 1 rpc 18 rssn 6 bs
17:B11 bs 26:B1A ts 33:T21
odb 128:NotAuthorized ss 146:NotAuthorized

Table 15: Parameters Used in Create and Start Commands

Paramete
r

Description

rri

Routing indicator - 0 for GT (Global Title), 1 for PC/SSN (Point Code/Subsystem Number).

rgti

Local Global Title Indicator value. 4 for C7; 2 for A7. (Usually 4.)

rssn

Subsystem Number of HLR.

rtt

(GT only) Translation Type (usually 0).

rnp

(GT only) Numbering Plan. 1=E.164=ISDN-TEL, 7=E.214=ISDN-MOB.

rnai

Nature of address indicator. (4=INT)

bs dec:string

bs

If the specified bearer service exists in HLR SIM-profile, then string is returned for
further processing (see ProfileMap in simauth.aut).
ts dec:string

ts

If the specified teleservice exists in HLR SIM-profile, then string is returned for further
processing (see ProfileMap in simauth.aut).

ulcmmg.conf

LOCAL_HOST as1:2000
REMOTE_HOST as1:2001 [192.89.210.12]

Example MML Commands

The examples in this section illustrate the MML commands used to create links, link sets, and route sets.

Figure 5:

Links, Link Sets, and Route Sets

Figure 6: MML Provisioning

SS7 Example: Creating Links, Link Sets, and Route Sets

CRTE-OSPC:PC=14275,NI=NAT0;
CRTE-LSET:LSET=LSET1,PC=253;
CRTESLK:SLK=LNK1,LSET=LSET1,SLC=0,SPEED=64K,PORT=0,CHANNEL=1
7
CRTE-RSET:RSET=RSET1,PC=253,RTES=LSET1,LOADSHR=YES;
CRTE-RSET:RSET=RSET2,PC=61,RTES=LSET1,LOADSHR=YES;
ALW-RSET:RSET=RSET1;
ALW-RSET:RSET=RSET2;
ACTV-SLK:SLK=LNK1;
SIGTRAN Example: Creating Links, Link Sets, and Route Sets
CREATE-OSPC:PC=4004,NI=INT0;
CREATE-M3UA-LSET:LSET=IPLSET,TYPE=IPSP-IPSP, RADDR=207.46.20.60,PC=5005;

CREATE-M3UA-SLK:SLK=IPSLK,LSET=IPLSET,LADDR=72.5.124.61,RADDR=207.46.20
.60,MODE=CONNECT,LPORT=2906;
ACTIVATE-M3UA-SLK:SLK=IPSLK;
CREATE-RSET:RSET=IPRSET,PC=5005,RTES=IPLSET;
ALLOW-RSET:RSET=IPRSET;
CREATE-M3UA-RKEY:RKEY=RK1,TYPE=STATIC-AS,TRAFFIC-MODE=LOADSHARE,LSET=IP
LSET,DPC=4004,SI=SCCP,SSN=1&251&252;
ACTIVATE-M3UA-RKEY:RKEY=RK1;