2 srp operation

Alcatel University - 8AS 90200 1337 VH ZZA Ed.02 Page 2.1

Alcatel University - 8AS 90200 1337 VT ZZA Ed.022.1

2 SRP Operation


2.2

Alcatel 8686 SRP Operation Session presentation

Objective: to be able to manage N7 configuration, the service events, alarms and statistics.

Program: z 2.1 Pre-requisitesz 2.2 SS7 managementz 2.3 Events and alarms service managementz 2.4 Statistics service management



2 SRP Operation

2.1 Pre-requisites



SRP Operation Session presentation

z 2.1 Pre-requisitesOperation ConsiderationsOperator Login

z 2.2 SS7 managementz 2.3 Events and alarms service managementz 2.4 Statistics service management


2.5

2.1 Pre-requisitesOperation Considerations

For management purposes, the operator must have knowledge of the:z Location of the SMF: either located in the SRP (in SU) or in

a dedicated management point (SMP). the operator must know the URL address of the machine

supporting the SMF in order to connect to it through the GUI.

z Topology of the network: How many SRPs in the network? Which units do they contain? 9 the operator must know the name and/or IP address of each

Sun server in order to be able to open a Unix session on these units.

When management of the SRP is done through a GUI, the operator connects to the SMF.

When management requires a remote connection to the OS of a unit, the operator must open a rlogin or telnet session from his PC to this unit.




z 2.1 Pre-requisitesOperation ConsiderationsOperator Login

z 2.2 SS7 managementz 2.3 Events and alarms service managementz 2.4 Statistics service management


2.7

2.1 Pre-requisitesOperator login (1/3)

To manage the SRP, z Log on the SMP orz Log on a management PC if SMF is located in the SRPSuch a PC has only to be linked to the SRP public LAN,

z Start a Web browserNetscape Communicator (version 4.72 or higher) orMicrosoft Internet Explorer (version 5.5 or higher),

z Enter the URL address of the machine supporting the SMF in order to access the SRP management GUI.


2.8

2.1 Pre-requisitesOperator Login (2/3)

Enter the srpadmin login (default password = Change2)

Main management operations are done from the GUI interface on the PC provided with the SRP. The operator must use thesrpadmin login to open a management session.

This login allows the operator to: z configure the interface between SRP and SCP so that INAP operations can be exchanged between these 2 equipment.z observe SRP data such as the signaling information (links status, circuits status,) and modify their status (e.g put a

signaling link unavailable, block circuits,..). z subscribe and consult the SRP statistics, z observe and manage events and alarms occurring on the SRP system,z manage (creation, modification, deletion) announcement scripts.


2.9

2.1 Pre-requisitesOperator Login (3/3)

The operations presented below require to be performed directly on concerned computers using Solaris OS commands. They are not available through the SMF GUI.z Level 1 maintenance operations:

see Alcatel 8686 SRP Product Sun Fire V240 Server Hardware Maintenance Guide covering hardware components replacement.

z Unit operations: see Operators Guide Units module covering units stop and

restart.

z Put and get trace files.

Use telnet to connect to the concerned computers.

The default login is linus with the default password ChangeMe



2 SRP Operation

2.2 SS7 Management


2.11


z 2.1 Pre-requisitesz 2.2 SS7 management Introduction to SS7 ManagementMTP Management ISUP Management TCAP/INAP Management

z 2.3 Events and alarms service managementz 2.4 Statistics service management


2.12

2.2 SS7 Management Introduction to SS7 Management (1/2)

Management of ITU-T N 7 signaling System in the SRP is done via the GUI through the MTPMTP, ISUPISUP and TCAP/INAPTCAP/INAP objects:

MTP objects

TCAP/INAP objects

ISUP objects

Configuration of the SS7 is done in pfmomniss7 (MTP and SCCP configuration) and avpccfmgt (ISUP configuration) Display of the PCM can be done through HWA (hardware agent).


2.13

Level 1

Level 2

Level 3

Level 4

Level 7

Applications

TCAPISUP TUP

SCCP

BSSAP

INAP-CS2 MAP

INAP- ER1

INAP- CS1

MTP

Sub-Systems:

2.2 SS7 Management Introduction to SS7 Management (2/2)

SS7 Architecture:

This functional diagram presents the different parts of the n7 signaling system: MTP: Message Transfer Part. The overall function of MTP is to serve as a transport system, providing reliable transfer of signaling

messages between 2 SP. MTP consists on three sub-levels, known as MTP1, MTP2 and MTP3. User Parts: on the top of MTP there are several user parts. A user part supports a specific application and has its own set of

signaling messages. Each user part is totally independent from the other. TUP: Telephony User Part. Not used anymore. Replaced by ISUP. ISUP: ISDN User Part. SCCP: Signaling Connection Control part. TCAP: Transaction Capabilities Application Part. INAP-CS1: Intelligent Network -Capability Set 1 (ITU standard). INAP-CS2: latest release of the IN protocol (ITU standard). INAP-ER1: Intelligent Network Application Part developed by Alcatel. MAP: Mobile Application Part. BSSAP: BSS Application Part.


2.14





2.15

2.2 SS7 Management MTP Management - Overview (1/3)

MTP configuration is carried out at installation time and the operator should not change it.

Pre-requisite to this section:z Alcatel installer must have configured the Ulticom board

beforehand.

This section allows operator to understand the principles of MTPThis section allows operator to understand the principles of MTPdatabase creation.database creation.

To configure the Ulticom board the installer must execute commands such as configurePlatform and configureNodes ss7 C7 and then make sure the Signalware stack is launched.


2.16


There are two types of connections possible for the signaling links: z In the first one, signaling information is carried via the same trunks that

carry voice information, the extraction of signaling information is performed by

the MU that transmit it towards the SU via an E1 trunk between the MU and the Ulticom board.

MTP database creation is done in 3 steps:9 Step 1: create the signaling links routing configuration through

configure.sh9 Step 2: create the SRP to network SS7 configuration through

the SMF MTP GUI9 Step 3: display current MTP configuration


2.17


z In the second one, signaling information is carried via dedicated trunks

(one or several) which are directly connected to theUlticom boards (one board = one trunk).

The maximum number of signaling links supported by SRP is 16 multiplied by the number of Ulticom boards.

MTP database creation is done in 2 steps:9 Step 2: create the SRP to network SS7 configuration through

the SMF MTP GUI.9 Step 3: display current MTP configuration.


2.18

2.2 SS7 Management MTP Management - SL routing configuration through configure.sh (1/4)

1 - Use telnet to connect to the MU which receives the Signaling Links from the network as linus (default password = ChangeMe)

2 - Execute /opt/AVPOP/avphwa//etc/configure.sh

z Create a new avpop.rc file:

z Following menu appears:

Hardware Agent Configuration Tool

An avpop.rc file has been found. Would you like to regenerate it? (y/n):y

old file has been renamed /opt/AVPOP/avphwa/avpop.rc.030523155735

Press the ENTER key to continue

Hardware Agent Configuration Tool

An avpop.rc file has been found. Would you like to regenerate it? (y/n):y

old file has been renamed /opt/AVPOP/avphwa/avpop.rc.030523155735

Press the ENTER key to continue

List of available function:

1 --> create a new Signaling Link routing between two NMS trunks

2 --> Save configuration and exit

Enter your choice > 1

List of available function:

1 --> create a new Signaling Link routing between two NMS trunks

2 --> Save configuration and exit

Enter your choice > 1

z Choose 1 to create the signaling interface between two NMS trunks

Log to the MU using login = linus; password = ChangeMe TIP: from the PSMF find the MU IP address by the command: cat /etc/hosts

avpop.rc is the currently used MTP configuration file. To be safe you should make a copy of this file (command: cp avpop.rc) because as soon as you start the configure.sh script it overwrites avopop.rc.

Caution: Do not change avpop.rc manually. You should only modify it using the configure.sh scripts.


2.19


TS n 0 TS n 1 TS n 2 TS n 31GUI

numbering 0 1 2 31

avpop.rc numbering -1 0 1 30

Termhandler numbering 1 2 3 32

Numbering used when refering to timeslots :

Note: Numbering rules to be followed during MTP database creation:

When using configure.sh the following rules apply:z Trunk number between NMS and switch: numbered from 0 (right hand trunk on NMS - rear view) to 3 (left hand trunk on

NMS - rear view).

z TS on trunk: numbered from -1 to 30 (-1 being the synchronisation TS).


2.20


z Repeat this operation of all the Signaling Links to be routed from the network to the SU.

z Save configuration (option 2) and exit.

Information about Signaling Link coming from the network

Enter NMS logical board number > 1

Enter Trunk number (0-3) > 0

Enter TimeSlot number (0-30 for E1, 0-22 for T1) > 0

Information about Signaling Link going to the SU




Information about Signaling Link coming from the network




Information about Signaling Link going to the SU




Trunk 0 (rear view: it is on the left of board)NMS board n 1

TS 0 on trunk 0

NMS board n 2

Trunk 3 (rear view: it is on the right of board)

TS 0 on trunk 3


2.21


mu2040na05 linus>sepman -t mu2040na05-avphwa-P2-1mu2040na05-avphwa-P2-1: sending SIGTERM to pid 855 OK

mu2040na05 linus>

mu2040na05 linus>sepman -t mu2040na05-avphwa-P2-1mu2040na05-avphwa-P2-1: sending SIGTERM to pid 855 OK

mu2040na05 linus>

4 - Restart the HWA sep (terminate the sep and the defence will restart it):

5 - Check NMS configuration by editing the /opt/AVPOP/avphwa/avpop.rc file:mu2140na05 linus> cat avpop.rc

In (INPUT) on switch side;Out (OUTPUT) on SU sideboardCs0In=1 // SLC 0(= CS 0) on NMS board 1 on switch sidetrunkCs0In=0 // SLC 0(= CS 0) on trunk 0 on switch sideTsCs0In=0 // SLC 0(= CS 0).Physically TS n1 on switch sideboardCs0Out=2 // SLC 0(= CS 0) on NMS board 2 on SU sidetrunkCs0Out=3 // SLC 0(= CS 0) on trunk 3 on SU sideTsCs0Out=0 // SLC 0(= CS 0).Physically TS n1 on SU side

mu2140na05 linus> cat avpop.rc

In (INPUT) on switch side;Out (OUTPUT) on SU sideboardCs0In=1 // SLC 0(= CS 0) on NMS board 1 on switch sidetrunkCs0In=0 // SLC 0(= CS 0) on trunk 0 on switch sideTsCs0In=0 // SLC 0(= CS 0).Physically TS n1 on switch sideboardCs0Out=2 // SLC 0(= CS 0) on NMS board 2 on SU sidetrunkCs0Out=3 // SLC 0(= CS 0) on trunk 3 on SU sideTsCs0Out=0 // SLC 0(= CS 0).Physically TS n1 on SU side

Signaling Link

between SRP

and switch

mu2040na05 linus>sepman -l |grep avphwa|------------------------------------------------------------------------avphwa|

|0-0|mu2040na05-avphwa-P2-1 |1422| 855| 0| 35|May 22 16:12| 0| 2976| 1|

mu2040na05 linus>

mu2040na05 linus>sepman -l |grep avphwa|------------------------------------------------------------------------avphwa|

|0-0|mu2040na05-avphwa-P2-1 |1422| 855| 0| 35|May 22 16:12| 0| 2976| 1|

mu2040na05 linus>

3 - Find out the name of the hwa SEP:

Alcatel recommends not to use sepman -r to restart a sep. This option can end up with 2 versions of the SEP in some cases. Usesepman -t instead and leave the defense to restart the sep.


2.22

2.2 SS7 Management MTP Management - SRP to network SS7 configuration (1/18)

SRP connection to other network elements:

These objects must all be declared in the SRP. The SSP and SCP also has to contain equivalent objects.

SRP 4.1 One Box

(= PCM)

SSPTS x Ex: SCP

Ulticom driver

=

PC = 1

(=SLC) (here with 2 SLC)

PC = SP1PC = SP3CICs with unique

numbers

TS y

This slide is a simplified view of how the SRP is connected to network equipment (SSP, SCP etc). Indeed between the SSP and the Ulticom board in the SU, the signaling information normally transits through the MU (AG4000 board).This is hidden on the slide. However the signaling link could be directly connected to the Ulticom through a dedicated link (no CIC on it).

All messages go through the SSP, whatever the destination of the message. An equipment is identified uniquely in a given SS7 network (national or international or local) by a signaling point (SP or PC=Point

Code). z As part of the SRP SS7 configuration, the SRP itself is declared as a N7 End Point.z Other network equipment are declared as Destinations with a destination PC.

A FEP (Front End processor) allows the SRP to retrieve the signaling information from PCM links connected onto Ulticomboards in the SU.

A trunk is another name for PCM. A data link is a time slot (TS) on a PCM. When inserted into a signaling linkset, a data link becomes a signaling link (= SLC or COC in French)

z SLC: Signaling Link Code carrying signaling messages which can be relative to CICs (Circuit Identification Code carrying speech) or not.

These objects must all be declared in the SRP. The distant equipment also has to contain equivalent objects. Some constraints have to be respected when declaring signaling objects:z CIC numbers must be unique on both sides.z COC numbers must be unique on both sides.


The SRP does not use traffic distribution law to choose between routes and links. Instead it uses the route/link of rank 0 by default and if that route/link is not available it uses the route/link of rank 1 etc.

2.23


Situation: SRP wants to send a message to network element 1.Q.1: Which route is used to send signalling messages to element 1?

=> route of rank 0 in priority. If not available use route of rank 1.Q.2: Assuming Route1 has been chosen (and therefore linkset x). which link is used, link 0 or link1?

=> link of rank 0 is chosen in priority. If not available use link of rank 1.

SRP One boxSP = 1

Element 2SP = 2

Element 1SP = 391

link0 with rank 0

Linkset xdeclared in SRP

link1 with rank 1

Linkset ldeclared in SRP

Linkset mdeclared in entity2

ADJACENT SP (at the end of linkset x)

Route set

Route 1 with rank 0

Route 2 with rank 1

SS7 background information :


2.24


SS7 background information :

SIGNALINGLINKSETLinkset x

DATA LINK

Link0

DESTINATION: destavpsDISTANT POINT CODE = 2

LINK of rank 1SIGNALING


SIGNALINGLINKSET


Choose link in a given linkset

Choose route and therefore a linkset

Link

Signaling Point of distant equipment (SCP,SSP...)

A linkset features the adjacent point code

A TS on PCM linking OSP-ME to adjacent

equipment

ROUTE of rank 0

ROUTE1

ROUTE ofrank 1

ROUTE2

Linkset l

Link1


2.25


MTP Object Model:

N7 End Point: local (SRP) signaling point name and signaling point code. FEP (= Front End Processor) is the Ulticom driver. Its a SEP in charge of getting the SS7 information from the E1 links connected

to the Ulticom boards. We can do the analogy with a CDROM driver on your PC. It implements the MTP 1 and 2 levels as well as the signaling network management part of MTP 3.For the BEP (Back End Processor) we can do the analogy with Windows Explorer which allows you to see whatever is retrieved by the FEP. The BEP implements the message distribution part of MTP 3 by looking at the SI (Service Indicator) part of the SIO field.The SEP (Service Execution Process) corresponds to the SCP of the DLI or ISUP CCF and executes the messages it receives from the NED (ie. BEP). It implements the MTP 4 level.

Trunk: A PCM cable connected to an Ulticom board. Data Link: A time slot on a PCM. A data link is the physical media for a link (SLC). Link: SLC (COC in french). Carries signaling information from one SP to another. 16 SLC max between 2 SP. Linkset: A linkset is a group of signaling links used to carry signaling information between 2 adjacent points. One can only

declare a maximum of 4 linksets between 2 SP. Route: List of declared linksets that can be borrowed to reach to a given SP. Destination: SP name and code of distant network equipment (SSP, SCP, ) . Sub-System Number: local SSN declared in SU; 1 remote SSN per distant equipment. Global title: Allow to define type and value of a Global Title. Global Title translation rule: to associate a GT to a couple SPC/SSN.


2.26

Routing Map

DestinationName:Destination PC:SSN:

LinksetName:Destination Name:

LinkName:SLC :Rank :


RouteName:Destination Name:Linkset Name:Rank:

SCCP configuration (GT, SSN)SCCP configuration (GT, SSN)

Logical Map

N7 End PointName:PC:SSN:

FEPName:

TrunkName:

Data LinkName :Time slot :

Physical Map

SS7 Configuration Object Model:

When configuring the SS7 environment in the SRP, the objects have to be created in a particular order:

1- N7 End Point: represents the signaling point (SP) of the SRP.2- FEP: the Ulticom driver in the SU.3- Trunk: PCM cable on which the link will be declared.4- DataLink: a TS on a PCM cable. A datalink is the physical media for a llink.5- Destination: distant signaling point (SSP, SCP...).6- Linkset: set of links going to an adjacent SP (that adjacent SP will forward the message until it eventually reaches the distant SP).

The adjacent SP might be the distant SP.7- Link: the signaling link carrying signaling messages.8- Route: route to the remote signaling point .

If Global Title addresses are used to reach a distant equipment, the installer will also need to define the SCCP parameters. Seethe TCAP/INAP Management part later in this chapter.


2.27

To display this objects, double click...


Physical map:


2.28

1

2

3


Physical map - Displaying a N7 End Point:

1: double click on N7 End Point. 2: select a N7 End Point name in the list. 3: in N7 End Point menu choose display to display the characteristics of the N7 End Point.


2.29

Name of N7 End Point (=SRP name).

SS7: recommended name

Color meaning:green: normal state;orange:indeterminate state;red: blocked state

Signaling Point Code of SRP, here in the national network


ANSI & ITU-T: PC coded on 14 bits.China: PC coded on 24 bits

Color Meaning: Green OK state (means the SRP is successfully connected to the distant point). Red The link going to the distant point is blocked. Orange Reserved to the N7 End Point to indicate that an object linked to N7 stack is not working properly.


2.30

The object Identifier

The platform name

The name of the N7EndPoint object hosting this FEP

This will disconnect the FEPThe defense will restart and reconfigure the FEP during the following minute


Physical map - FEP (Front End Processor):

FEP (Front End Processor) is the Ulticom driver. Its a SEP in charge of getting the SS7 information from the E1 links connected to the Ulticom boards. We can do the analogy with a CDROM driver on your PC. It implements the MTP 1 and 2 levels as well as the signaling network management part of MTP 3.


2.31

The Trunk connected on the Ulticom Board

Trunk object is used for E1 board configuration. 3 E1 maximum per FEP.


Physical map - Trunk:

This window is used to associate a FEP with a device. The object Trunk indicates on which interface the PCM cable is connected to the Ulticom board

The Device Name parameter represents the Ulticom board number in the SU (starts at 0).


2.32

TS used as signaling channel between SSP

and N7EndPoint

When the fields have been filled in the appropriate way, the user has to select Create from the Datalink menu to store the values.


Physical map - Datalink:

The Time Slot field is a value between 1 and 31. See the ITU Recommendations for details. Data Link indicates which Time-Slot is used on the E1 for the Signaling Link. This information is internal if the E1 is connected to one MU or external if this E1 is connected directly to the SS7 network.


2.33


Routing map:


2.34

MTP3 Rule Name (= traffic distribution law) for Compaq only. Do not fill for SRP.


DISPL-RSET:RSET=DESTAVPS;

--- ROUTE SET ---

Name DPC State Status Load sharingDESTAVPS 2(0x2) ACTIVE ac0 No

--- ROUTES ---

Name Status

LKSET1 ax

--- ROUTE SET STATUS LEGEND ---

a - PC accessible A - PC inaccessible

c0- route set not congested Cx - route set congested to level x

--- ROUTE STATUS LEGEND ---

a - link set available A - link set not available

x - transfer allowed X - transfer prohibited


--- ROUTE SET ---

Name DPC State Status Load sharingDESTAVPS 2(0x2) ACTIVE ac0 No

--- ROUTES ---

Name Status

LKSET1 ax



c0- route set not congested Cx - route set congested to level x




8 characters max

Routing map - Destination:

If the DPC can not be reached because the signaling link (SLC) is blocked, then the destination, route, link set and link objects are red. Try to solve the problem by aligning the SLC. If this alignment is successful all objects will go back to green like shown on the slides.

Route set status should be ac0. Route status should be ax. When looking at an object status, all letters should be in lower case. An upper case character is bad news! You should pay special attention to the 2 first characters.

A destination can be an adjacent or a remote Point Code. Both have to be created.z An adjacent Point Code is directly connected via a trunk to one of the users FEPs. This Point Code has to be the

Adjacent PC attribute of one of the linksets.z A remote Point Code is a destination not directly connected to one of the users FEPs, but accessible via one of them or

more.


2.35

The simplest way to fill in this field is to increment the rank for each new Route on the same destination.



--- ROUTE SET ---

Name DPC State Status Load sharing

DESTAVPS 2(0x2) ACTIVE ac0 No

--- ROUTES ---Name Status

LKSET1 ax



c0 - route set not congested Cx - route set congested to level x





--- ROUTE SET ---




LKSET1 ax







Routing map - Routes:

Route set status should be ac0. In that case the route Name would be green. Route status should be ax.


2.36

Link

Linkset


Logical map:


2.37

Adjacent signaling point (equipment at the other end of linkset)

Activate linksetand its links

Deactivate linksetand its links


DISPL-LSET:LSET=LKSET1;

--- LINK SET ---

Name Nbr ADPC Status Active_Links PC_countLKSET1 3 2(0x2) a 1 1

--- SIGNALING LINKS ---

Name Nbr SLC StatusLK1 1 0 a

--- LINK SET STATUS LEGEND ---

a - active A - not active

--- SIGNALING LINK STATUS LEGEND ---

a - available A - not available


--- LINK SET ---








A rule is a traffic distribution law used for COC selection but in the SRP no rule has to be specified

Logical map - Linkset:

Note: dont forget to activate the Linkset. Linkset status should be a. Link (= COC) status should be a.


2.38


DISPL-SLK:SLK=LK1;

--- SIGNALING LINKS --

Name Lset_Name SLC Port Chan ADPC State StatusLK1 LKSET1 0 0 2 0x2 ACTIVE inbolraP


i - installed I - not installedn - link normal F - link failedb - not locally blocked B - link locally blockedo - not remotely blocked O - link remote blockedl - not locally inhibited L - locally inhibitedr - not remotely inhibited R - remotely inhibiteda - SLT Alignment enabled A - SLT Alignment disabledp - SLT Periodic enabled P - SLT Periodic disabled

DISPL-SLK:SLK=LK1;





Activate link.

Deactivate link

Logical map - Link:

DataLink name: Name of the IT that supports the link (Objet DataLink). Should be displayed in green.

Signaling Link Channel (SLC) identifier: value that must be unique between 2 signaling points. According to the ITU standard: 16 SLC max between 2 SP. In SRP: number of SLC depends on the version of the Ulticom board used and the number of Ulticom boards. z The currently used Ulticom boards in SU can manage 8 SLC max. (Latest version of board: 16 SLC - not integrated in SU

yet).z 2 Ulticom boards max/SUz A license is used to restrict the number of SLC allowed per SU.

Rank: Priority into the linkset. The rank value allows to choose a COC between several within a link set, based on a traffic distribution law.


2.39


Objects creationcreation:

Order Object Name1 N7End Point2 Fep3 Trunk4 Datalink5 Destination6 Linkset7 Link8 Route

Objects deletiondeletion:

Order Object Name1 Block Destination2 Route3 Link4 Linkset5 Destination6 Datalink7 Trunk8 Fep9 N7 End Point

MTP configuration summary:


2.40

DISPL-SLK:SLK=LK1;





DISPL-SLK:SLK=LK1;





2.2 SS7 Management MTP Management - Display current MTP configuration (1/7)

Display Signaling Links:

Displays the LK1 signaling link status

If OK, signalling link is in state inbolraP


2.41


Display Linksets:


--- LINK SET ---









--- LINK SET ---








If OK, link set and signalling link are in state a

If OK, link set and signalling link are in state a

Displays link set LKSET1


2.42


Display Route sets:


--- ROUTE SET ---




LKSET1 ax








--- ROUTE SET ---




LKSET1 ax







Displays the route set DESTAVPS status

If OK, route set should be in state ac0 and signalling link in state ax

If OK, route set should be in state ac0 and signalling link in state ax


2.43


mu2140na05 linus>termhandler -node ss7

+-------------+ Terminal Handler [Started]

| TermHandler | Copyright 2001 Ulticom, Inc.

+-------------+ All Rights Reserved

Usage: Filename: - to execute from a file

MML command: - series of mml command(s)

OMNI [23 Apr 2003 15:06:46] #1:

mu2140na05 linus>termhandler -node ss7

+-------------+ Terminal Handler [Started]

| TermHandler | Copyright 2001 Ulticom, Inc.

+-------------+ All Rights Reserved

Usage: Filename: - to execute from a file

MML command: - series of mml command(s)

OMNI [23 Apr 2003 15:06:46] #1:

Using Termhandler utility:z Termhandler: utility provided to display the current MTP

configuration. To start Termhandler: 9 Connect as linus on the SRP (on the SU).9 Type the following command: termhandler -node ss7

The N7 End Point name

This tool allows the operator to interrogate the signaling links states from any terminal connected to the SU for example.


2.44

OMNI [23 Apr 2003 18:03:47] #2:display-slk;Send [DISPLAY-SLK;]? [Y/N]y

Sent MML command #2 to mu2140na05.PM, cmd[DISPLAY-SLK;]


Name Nbr LSet LSet SLC Port Chan Speed ADPC State StatusName Nbr

LNK1 1 LSET0 1 0 1 2 64000 2(0x2) ACTIVE inbolraP

--- signaling LINK STATUS LEGEND ---

i - installed I - not installed

n - link normal F - link failed

b - not locally blocked B - link locally blocked

o - not remotely blocked O - link remote blocked

l - not locally inhibited L - locally inhibited

r - not remotely inhibited R - remotely inhibited

a - SLT Alignment enabled A - SLT Alignment disabled

p - SLT Periodic enabled P - SLT Periodic disabled

OMNI [23 Apr 2003 18:03:47] #2:display-slk;Send [DISPLAY-SLK;]? [Y/N]y

Sent MML command #2 to mu2140na05.PM, cmd[DISPLAY-SLK;]


Name Nbr LSet LSet SLC Port Chan Speed ADPC State StatusName Nbr

LNK1 1 LSET0 1 0 1 2 64000 2(0x2) ACTIVE inbolraP


i - installed I - not installed

n - link normal F - link failed

b - not locally blocked B - link locally blocked

o - not remotely blocked O - link remote blocked

l - not locally inhibited L - locally inhibited

r - not remotely inhibited R - remotely inhibited

a - SLT Alignment enabled A - SLT Alignment disabled

p - SLT Periodic enabled P - SLT Periodic disabled


In Termhandler, check the SRP to network SS7 configuration: Display signaling links:

Displays all signaling links managed by the SRP

If OK, signaling link is in state inbolraP

If you experience some problem when aligning the signaling link and that you are sure that switch configuration is ok, you can try to reboot the SU (init 6).


2.45

OMNI [23 Apr 2003 18:16:07] #1:display-lset;Send [DISPLAY-LSET;]? [Y/N]y

Sent MML command #1 to mu2140na05.PM, cmd[DISPLAY-LSET;]

--- LINK SET ---

Name Nbr ADPC Status Active_Links PC_count

LSET0 1 2(0x2) a 1 1

--- signaling LINKS ---Name Nbr SLC Status

LNK1 1 0 a





OMNI [23 Apr 2003 18:16:07] #1:display-lset;Send [DISPLAY-LSET;]? [Y/N]y

Sent MML command #1 to mu2140na05.PM, cmd[DISPLAY-LSET;]

--- LINK SET ---

Name Nbr ADPC Status Active_Links PC_count

LSET0 1 2(0x2) a 1 1

--- signaling LINKS ---Name Nbr SLC Status

LNK1 1 0 a





If OK, link set and signaling link are in state a


Displays all link sets

If OK, link set and signaling link are in state a

Display link sets:


2.46

OMNI [23 Apr 2003 18:16:07] #1:display-rset;--- ROUTE SET ---


RSET0 3(0x3) ACTIVE ac0 No

--- ROUTES ---

Name Status

LSET0 ax







OMNI [23 Apr 2003 18:16:07] #1:display-rset;--- ROUTE SET ---


RSET0 3(0x3) ACTIVE ac0 No

--- ROUTES ---

Name Status

LSET0 ax







If OK, route set should be in state ac0 and signalinglink in state ax


Displays all route sets

If OK, route set should be in state ac0 and signaling link in state ax

Display route sets:


2.47

1 - Edit avpop.rc to find out the Signaling link routingconfiguration:9 Board nb coming from the network: .9 Trunk nb coming from the network [0..3]: ..9 TimeSlot nb coming from the network: ..9 Board nb going to the SU: .9 Trunk nb going to the SU [0..3]: ..9 TimeSlot nb going to the SU: ..

2 - Use SMF GUI to find out the MTP objects between SRP and switch.

3 - Use termhandler to display the current MTP configuration.

2.2 SS7 Management MTP Management - Exercise

Time allowed: 15 minutes


2.48





2.49

2 objects for ISUP configuration and management part

2.2 SS7 Management ISUP Management - Graphical interface

For ISUP management go under the ISUP menu:

The TRUNKS MANAGEMENT object allows management of CICs on PCMs. It allows to:z manage the status of PCMs connected to the SRP, z manage the state of speech circuits (CIC = Circuit Identification Code) on these PCMs. The operator can:

Declare / undeclare one or several CIC(s), Put one or several CIC(s) in service, Block / Unblock one or several CIC(s).

The CONFIGURATION object allows to set up the ISUP parameters.


2.50

1

3

12

Select the partition ID and press OK

3

One MU with 2 AG4000 boards

Other Media Units

2.2 SS7 Management ISUP Management - Displaying a trunk connected to MU (1/5)

Displaying a trunk connected to MU:z TS allocation (CIC) can only be visualised in the Media Unitz To display the MUs currently attached to the SU:

select TRUNKS MANAGEMENT objectselect the partition id (usually 1)the list of MU names appears

Visualization of speech circuits can only be done by connecting to the MU since there are only signaling links between MUs and the SU.

Media Units (MU) were previously called Voice Units (VU). One SRP can handle up to 1920 ports distributed between various Media Units. Different configurations exist: from One-box (also

called Compact) systems to large distributed systems. 16 MU max.


2.51

double click on trunk

If trunk is not declared (no TS assigned), this popup window will be displayed

otherwise trunk management window is displayed (see following slides)

1

3

if you wish to declare the trunk at that point click on Yes (see Declaring CICs on a trunk).

4


' Trunks bet

ween MU and

external equ

ipment.

' SU MU lin

k is not

displayed

2

For each MU, the list of AG 4000C boards known to be in service are shown along with the trunks attached to each board. Reminders:

z The MU is made of a compact PCI chassis and integrates:z 1 CP1500 CPU board (SUN Micro Systems),z 2 AG-4000C boards maximum for speech circuits (called ports). One board connects up to 4 PCM, therefore each board

can handle 120 ports.z 1AG-4000C board dedicated to send the extracted signaling channel to the SU.

Unique signaling PCM between SU and one of the MUs does not appear in this window. To know which PCMs should be displayed, avpccfmgt looks in avpop.rc.

Trunks displayed are for CIC + SLC between SRP and other platforms (SSP) The number of maximum signaling links supported by 1 SU depends on the license of the Ulticom board. 4 Links

extracted from the 8 incoming E1 links is quite a common configuration. From the pfmomniss7 service we found one SLC on TS 1 of a trunk called TK1, between the SU and the MU. From here we conclude that TK1 declared in SU arrives on trunk 4 of MU.


2.52

The name the MU

The AG4000 board in the MU Trunk nb

The PCM is connected to a remote entity with SPC = 0-0-3 (3-8-3 format).A Point Code has 3 parts (ITU recommendation): Continent identification (3 bits) Zone/network identification (8 bits) Signaling Point identification (3 bits)Example:

decimal format: 8235binary format: 100 00000101 0113-8-3 format: 4 - 5 - 3

alarm codes


The table then describes, for each configured time-slot:z The Circuit number (unique between 2 SP)z The type (INcoming, outgoing or both). For a SRP a CIC will always be incoming meaning it has been selected by the

distant equipment (here the SSP). Thats normal since the SRP is never the initiator of the dialog.z The current state (see below for a short explanation of each state),z The current blocking states:

manual (i.e. due to an operator: In, Out or Dist), automatic (i.e. due to SRP platform: BLOS, BLOH or BLOF), miscellaneous (i.e. FAUA, FAUT or BLOK).

CIC states: the following states are defined:- UNDECLARED: not yet configured,- DECLARED: configured but not put in service,- IDLE: idle state = free and ready to take a call,- ESTABLISHED(IN): engaged by an incoming call,- ESTABLISHED(OUT): engaged by an outgoing call,


2.53

REFRESH: update the information shown on the window.

SELECT ALL: select all time slots already configured on the trunk


Signaling status:

T: BLOS

K: BLOH

A: BLOF

Miscellaneous blocking status:

S: FAUA

H: FAUT

C: BLOCK

Maintenance status:

In: BLOA

Out: BLOD

Rem: Blocked by distant (BLOJ)

A SLC between MU and external equipment

The meaning of the blocking states are:z Maintenance BlockageIn: operator blocking on a incoming circuit Out: operator blocking on an outgoing circuit - internal stateDist.: outgoing circuit blocked by the distant operator at the other end.

z signaling FaultBLOS: blocking (outgoing circuits) due to an alarm on the trunk (T)BLOH: blocking (outgoing or incoming circuits) due to an hardware failure of the remote equipment (K)BLOF: blocking (outgoing and incoming circuits) due to an hardware failure on the platform (A)

z Miscellaneous blockageFAUA: blocking (outgoing circuits) due to an error detected locally, (S)FAUT: blocking (outgoing and incoming circuits) due to a signaling error, (H)BLOCK: blocking (outgoing circuits) due to a lack of acknowledgement when unblocking. (C)

Operations:REFRESH: update the information shown on the window,SELECT ALL: select all the time slot already configured on the trunk (all but undeclared)IN SERVICE: put all selected CICs in service. Available only when the selected CICs are in declared state, UNDECLARE: delete all the selected CICs. The time slots can then be configured again with new CICs for instance. The

selected CICs must already be blocked,DECLARE: let the operator configure all or part of the time slots of that trunk.BLOCK: block the selected CICs. If there are calls in progress or established on the CICs, the action will be took into account

when they are finished. It is up to the operator to periodically use the refresh button to see when the command finally ends.

UNBLOCK: Unblock all the selected CICs.


2.54


A trunk with no alarm

All CICs are IDLE meaning ready to

take a call


2.55

Exit window without

modifying the current

configuration.

1

1

4

5

6

2.2 SS7 Management ISUP Management - Declaring CICs on a Trunk (1/3)

Case 1: declaring CICs on an empty trunk (no CIC declared)

z Step 1:declare the CICs

Declaring CICs on a trunk:

2

3

This window is used to declare CICs on a trunk where no CIC has been defined previously. However there might be some Signaling Links declared on it.

Some parameters are filled automatically according to the user navigation in upstream menus:z Voice unit (= Media Unit) name z board name (AG4000 board)z trunk number

Procedure to follow for declaring CICs on an empty PCM: 1 - Select all TS of the PCM by clicking on the Select all Its button or 1- Select the required TS on the PCM by clicking on the corresponding it check boxes.2 - Enter the CIC number in the entry box of your first TS. The CIC value must be a multiple of TS modulo 32.

Note: for trunk 1: 1


2.56


Case 1: declaring CICson an empty trunk (no CIC declared)

z Step 2: check the CICs appear as DECLARED


2.57


Case 2: declaring CICs on a PCM with at least one CIC already declared on it.

Declared CIC is greyed out (can not be modified)

DPC can not be modified

3

Existing CIC

Declare new CICs

2

1

This window is used to declare CICs on a trunk where CIC have already been declared previously. Procedure to follow for declaring CICs on a PCM where CICs already exist:

1- In the trunk management window click on the Declare button2- In the trunk declaration window, declare your new CICs:z Select the required TS on the PCM by clicking on the it check boxes. Already declared CIC are greyed out and can not

be modified.z Enter the CIC number in the entry box of your first TS. z Is this CIC part of an incoming or outgoing circuit group? Select the type accordingly (ex: for SRP it will always be IN).z Click on Automatic Allocation to automatically fill the CIC values for the other TS. z The Destination Point Code field can not be modified.

3 - Click on Apply to declare the CICs.


2.58

1

2.2 SS7 Management ISUP Management - Putting a CIC in service (1/2)

Putting a CIC in service: A CIC can only be put in

service if the COC is online.

2

Select the CIC you wish to put in service

The IN SERVICE button should be available Click on it to put the CIC in service


2.59

2.2 SS7 Management ISUP Management - Putting a CIC in service (2/2)

Check the CIC appears as IDLE: the CIC is now in service and ready to be used for speech transmission.

IDLE means they are not currently engaged in a call.

What does the T mean?If SRP sends a message BLOCK request to SSP. SRP expects a BLOCK acknowledgment message back. If no BLOCK acknowledgment is received, the CIC can still be IDLE but with a T signaling fault.


2.60

2.2 SS7 Management ISUP Management - Configuration of ISUP parameters (1/5)

Configuration of the ISUP parameters in the SRP: carried out through the CONFIGURATION object.

12

Click on OK

Double click on object

Select partition id on which the

SLEE is installed

3


2.61


MANDATORY PARAMETERS tab: configuration of mandatory parameters in IAM, ACM, CONNECT, SUSPEND and RESUME ISUP messages

MANDATORY PARAMETERS window:z Operator can modify the value for mandatory parameters in IAM, ACM,CONNECT, SUSPEND and RESUME ISUP

messages if these parameters are not included by application into requests to CCF sep. These parameters are fully described in document Recommendation Q763 (03/93).

z Signal termination box: possibility for each outgoing call to insert/not insert the end-of-pulse signal (0xF value) at the end of the called party number in IAM message.

z Real-time update as soon as the Apply button is pressed new parameters are taken into account.


2.62


TRIGGERS tab: configuration of the CCF-ISUP service behavior.

TRIGGERS window: operator can change the behavior of the CCF-ISUP service for the following events:z automatic sending of ACM: when an incoming call is received by ISUP-CCF which forwards it to SSF, an ACM message

is automatically sent back to the network.z GRS message sending available: if selected and more than 1 CIC has been reset, a reset group message will be sent

for a group of CIC to minimize the number of messages on the network. If not selected there will be 1 RSC message for each CIC.

z SUSPEND/RESUME management: allow/inhibit the management of the SUSPEND/RESUME ISUP procedure (seeRec.Q764 (03/93) 2.5). If selected the SUSPEND and RESUME messages will be transmitted to the SSF. If not they will be ignored and timer T6 is automatically set to 1s to release the call.

z Automatic sending of CONFUSION message: allows to send an ISUP Confusion message to the network on reception of an unrecognized signaling message or parameter (see rec.Q764 (03/93) 2.10.5.2).


2.63


TIMERS tab: configuration of ISUP protocol timers.

TIMERS window: z On top of the window, the statistic period field allow to modify the time between two consecutive sending of statistic

tickets to pfmstat service of the platform.z Allows the operator to change the value of ISUP protocol timers. See Recommendation Q764 Annex A for more details.


2.64


MISCELLANEOUS tab: otherISUP Parameters.


2.65

1 - How many CICs are declared on the SRP? ..

2 - To be able to receive a call, a CIC must be in a particular state. Which one?

3 - Can you see any signaling links? ...9 If yes, how many? ...

2.2 SS7 Management ISUP Management - Exercise

Time allowed: 15 minutes


2.66





2.67

Alcatel 8686SRP

interface between SCP and SRP

INAP-CS2 or CAP V2

SignalingVoice

ISUP

INAP-CS2 or CAP V2

SS7 Network

user

SCP

SSP

2.2 SS7 Management TCAP/INAP Management - General Overview

SRP connections - logical view:

SSRRPP

INAP-CS2 or CAP V2

The exchange between SRP and SCP is done via:z INAP-CS2: Intelligent Network Application Part - Capability Set number 2.orz CAP V2: CAMEL Application Part version 2 where CAMEL = Customized Application for Mobile Enhanced Logic.

CAMEL is a tool to help the network operator to provide subscribers with operator specific services even when they are roaming outside the HPLMN.

CAP V2 INAP-CS2 + mobility management.


2.68

2.2 SS7 Management TCAP/INAP Management - Connections with SCP

The interface between SCP and SRP is based on the INAP CS2 (or CAP V2) standard at application level.

In direct or assist mode, z the transport protocol used is TCAP over #7 signaling

(according to the following specifications: level 2&3: #7 MTP, level 4&5&6: SCCP and TCAP).

In indirect or relay mode,z the SSP is in charge of relaying INAP messages in ISUP

messages to the SCP. z This mode is only implemented with Alcatel 1000 E10 switch

or Alcatel 1000 MSC switch. This latter also support direct mode.


2.69

2.2 SS7 Management TCAP/INAP Management - DLI service

Direct Link Interface (DLI) is the SRP INAP application that:z handle incoming calls,z identify the calling entity (SCFid: remote service in SCP),z exchange signaling messages with SCP in 2 possible ways:

direct mode: INAP messages sent/received to/from SCPor indirect mode: INAP messages sent/received to/from SCP

are encapsulated on ISUP,z execute operations requested by the remote service.


2.70

user

SRP

SCP

2) InitialDP (cdp,IPSSPCapability)

1) IAM(cdp)

3) EstablishTemporary Connection (@SRP, //routing Info

SCFid= Service Id,CorrelationId =call Id in SCP)

6 ') Oh ! my call... (CorrelationId)

7 ') BLA BLA

4 ) I must contact the SCP defined by SCFid

and transmit the CorrelationId to it

SSP

4) IAM (@SRP, SCFid, CorrelationId)

5) ACM +

ANM5')

Charging

7) PA(announcement #), PACUI etcvia Direct or Indirect link

6) ARI (CorrelationId, IpSSPCapabilities)

via Direct or Indirect link??

2.2 SS7 Management TCAP/INAP Management - SRP Call Flow

Note: In the case of a mobile accessing a service in his HPLMN when roaming, replace INAP-CS2 messages by CAP V2 messages. Ex: prepaid subscriber phoning from abroad.

1- User dials the service number (or Called Party Number = cdp). ISUP IAM (Initial Address Message) message arrives to SSP with in parameter the cdp.

2 - SSP detects it is an IN call and triggers the service by sending an INAP-CS2 InitialDP (Initial detection Point) operation to SCP.

3 - SCF to SSP: ETC (Establish Temporary Connection) operation in order to set up a temporary connection to SRP.4 - From the IAM the SRP extracts: Called Party Number (cdp), CorrelationId, SCFId. 5- ACM and ANM messages sent back to SSP. Note: sending ANM triggers the charging process. For free

announcements the operator can choose to send ANM later.6 - SRP sends the INAP operation ARI (Assist Request Instruction) to the destination indicated by the parameter

SCFId. NOTE: In IN standard when IP is linked to SSP via ISUP link only, SCP sends a CTR (Connect To Resource) operation

to SSP to setup a connection between user and external IP (SRF). In the case of the SRP, the platform does not wait for a CTR message.

7 - SCP sends INAP operations (PA, PACUI, etc) to SRP over a TCAP transaction.


2.71

2.2 SS7 Management TCAP/INAP Management - Charging starting point

According to the DLI configuration, 2 exchange modes for SSP-SRP interface function are possible:

z General exchange: ACM + ANM messages sent simultaneously by SRP.

z Delayed answer exchange mode: ACM sent on IAM reception; ANM sent later by DLI. In consequence the call is free before ANM is received by SSP.

ACM: Address Complete Message sent automatically to SSP when an IAM message is received. ANM: ANswer Message which triggers the charging process.

Delayed answer exchanged mode allows to play welcome or information announcement (without user interaction) without starting SSP tax counters.


2.72

2.2 SS7 Management TCAP/INAP Management - Call Flow in Direct Link Mode (1/2)

General exchange:

INAPapplication

SRP IAM

ACM

REL

RLC

INAP applicationtests

Application not present

ACCEPTANCEPHASE

process INAPoperation(s)

Send INAPoperation

in TCAP transactionTC_CONTINUE

USERDIALOGUE

PHASE

TC_CONTINUE

send "ARI"operation

& prompt restitutionto user

TC_BEGIN

SSP

SCP

ANM

Call Charged

Disconnect User

DISCONNECTIONPHASE

TC_END

Acceptance Phase: when the SRP receives an incoming call, the DLI will perform the following operations:z check availability of CorrelationId and SCFId in IAM message z Allocate internal resources in SRF. If resources can not be allocated the call will be released.

User dialog Phase (TCAP dialog):z Send CorrelationId to the SCF referred by SCFId via a AssistRequestInstruction INAP operation,z SCP asks SRP to perform INAP operations (e.g.: PA, PACUI, etc). SRP sends operations result to SCP. z Phase ends on release request either by the SSP (user hangs up) or the SRP.

Disconnection phase:z Call released by SCP or by user or by SRP.


2.73

2.2 SS7 Management TCAP/INAP Management - Call Flow in Direct Link Mode (2/2)

Delayed answer exchange mode:

INAPapplication

SRP IAM

ACM

REL

RLC

INAP applicationtests

Application not present

ACCEPTANCEPHASE

process INAPoperation(s)

Send INAPoperation

in TCAP transactionTC_CONTINUE

USERDIALOGUE

PHASE

TC_CONTINUE

send "ARI"operation

& prompt restitutionto user

TC_BEGIN

SSP

SCP

ANM

FREE

CALL

Call Charged

Disconnect User

DISCONNECTIONPHASE

TC_END

This exchange mode can be activated on operator commercial demand by setting the ANM sent by DLI flag in DLI configuration object.

It allows to play welcome or information announcement (without user interaction. This implies only PA operations can be free) without starting SSP tax counters.


2.74

user

SRP

SCP

2) InitialDP (cdp)

1) IAM(cdp)

3) Connect To Resource (cdp) 7 ) BLA BLA

SSP

6) Charging

4) PCUI (max nb of digits,end key= #,cancel key = *,announcement #)

8) USR (UUI = PCUI result)

6) ACM (UUSInd = UUS3)

+ANM

5) IAM (cdp,UUSInd = UUS3,UUI = PCUI operation)

2.2 SS7 Management TCAP/INAP Management - Call Flow in Indirect Link Mode using UUS3

(1/2)

Call flows varies according to the UUS used (UUS1 or UUS3).

Here is a call flow using UUS3.

1 - User dials the service number (Called Party Address = cdp). ISUP IAM (Initial Address Message) message arrives to SSP with in parameter the cdp.

2 - SSP detects it is an IN call and triggers the service by sending an INAP-CS2 InitialDP (Initial detection Point) operation to SCP.

3 - In IN standard when a SRP is linked to SSP via ISUP link only, the SCP sends a Connect To Resource operation to SSP to set up a connection between user and external IP (SRP). One of its parameter is IPResourceAddress = called Party Number

4 - SCP sends an INAP operation to SRP. Here for example a PCUI5 - SSP to SRP: IAM containing: Called Party Number (cdp) UUSIndicator (UUSInd): specifies if the ISUP dialogue with switch should be done in UUS1 or in UUS3. Ex: in a

trace if UUS3 is used then UUSInd = 40 (hexadecimal). Here SSP asks SRP to use UUS3. UUI: User to User Information field in which the INAP operation has been encapsulated. In a trace the field is in fact

UUSBuffer. Here the UUI field contains the PCUI operation.6 - ACM and ANM messages sent back to SSP. ACM confirms that the SRP dialogues in UUS3. 6 - Sending ANM triggers the charging process. Note: free announcements are supported on SRP!7 - Announcement is played and DTMF codes are detected to collect the user input.8 - The result of the PCUI operation (i.e.: the collected digits) is sent back to the switch in the UUI field of the ISUP

USR message.


2.75

SRP IAM(UUSInd= UUS3, UUI = PA

)

ACM (UUSInd =UUS3)

REL

RLC

USR (UUI = SRR)

SSP

ANM

Call Charged


(2/2)

BLA BLA

USR (UUI = PCUI)

USR (UUI = PCUI result)

USR (UUI = INAP operation)

USR (UUI = INAP operation result)

BLA BLA

In UUS3 standard, INAP messages can be exchanged during call setup (IAM, ACM, ANM) and call release (REL) but also during the call using the USR message.

The response of an INAP operation is in the USR message. The UUSIndicator field in IAM is optional. If not present we talk about UUS implicit. If present: UUS explicit.

SRR (Specialized Resource Report): indicates that an operation has been successfully processed. Ex: A PA has nothing to return to the SCP so the SRP just sends an acknowledgement message called SRR).


2.76

SRP


BLA BLA

IAM(UUSInd= UUS1, UUI =

PA)

ACM (UUSInd =UUS1)

REL (UUI = SRR)

SSP

ANM

Call ChargedRLC

IAM(UUSInd= UUS1, UUI =

PCUI)

ACM (UUSInd =UUS1)

REL (UUI = PCUI result)

ANM

Call ChargedRLC

BLA BLA

In UUS1 standard, INAP messages can only be exchanged during call setup and call release. The response of an INAP operation is in the REL message. Each time the SCP sends an INAP operation to the SRP, a new call is setup. This is not very optimized, therefore the INAP

dialogue is usually done in UUS3.


2.77

2.2 SS7 Management TCAP/INAP Management - Parameters extraction from IAM message

ETC (@SRP, //routing InfoSCFid= Service Id,

CorrelationId =call Id in SCP)

user

SCP

SSP

SL

SL

Case 1:IAM (CalledPartyNumber, SCFid, CorrelationId)or

Case 2: IAM (CalledPartyNumber)

Parameters extraction:

Case 1: extract CorrelationId and SCFidfrom specific parameters

orCase 2: extract CorrelationId and SCFid

from CalledPartyNumber

1

2

3

Alcatel 8686SRP

SSRRPP

Parameters extraction: z From the IAM the SRP has to extract at least 3 values: Called Party Number, CorrelationId, SCFId:

The Called Party Number contains the address of the DLI service in SRP, also called routing info (@SRP on slide). This routing information is held in the Assisting SSPIPRouting Address parameter of theEstablishTemporaryConnection operation. It is in fact a phone number that will be translated by the SSP.

The SCFId indicates to the DLI which remote SCP (or SCF in SCP) to contact. The CorrelationId is the identifier for the call context in SCP. This value is sent to SCP as a parameter of the

ARI operation.

z Location of SCFId and CorrelationId can vary according to the ISUP version used between SRP and SSP: case 1 - CorrelationId and SCFId in ISUP specific parameters called CorrelationId and SCFId. case 2 - CorrelationId and SCFId concatenated in the CalledPartyNumber parameter in 2 possible formats:

CalledPartyNumber = routing info + SCFId + Correlation Id (length of each parameter is configurable in DLI Configuration object),

or CalledPartyNumber = routing info + Correlation Id + SCFId (length of each parameter is configurable in DLI Configuration object).


2.78

SignalingVoice

INAP (or CAP) message on SLeg: ARI, CTR ...

INAP (or CAP) message on SLeg: ARI, CTR ...

user

SCP

SSP

Semi-permanent link

2.2 SS7 Management TCAP/INAP Management - Direct / Assist Mode

INAP operations between SRP and SCP are transmitted over TCAP through semi-permanent links in SSP.

Alcatel 8686SRP

SSRRPP

Examples of INAP CS2 messages:z ARI (Assist Request Information)z CTR (Connect To Resource)

The link in the SSP can be made via a semi-permanent link (see slide) or through the STP function of SSP (if implemented in the switch). The Alcatel E10 switch supports the STP function and semi-permanent links.

CAUTION: To set up a direct link, the switch must support the ETC message. The Alcatel 1000 E10 switch in R25 or previous releases does not support the ETC message. Therefore the 8686 SRP could not be connected to an Alcatel 1000 E10 used in a fixed network. In the case of a mobile network the 8686 SRP can cooperate with an Alcatel MSC (1000 E10 SSP + RCP) because the ETC message is handled by the RCP.

The Alcatel 1000 E10 in R26.x supports the ETC message so it can be used along with a 8686 SRP in a fixed network or in a mobile network.


2.79

2.2 SS7 Management TCAP/INAP Management - Indirect / Relay Mode

SignalingVoice

INAP-CS2 (or CAP V2)

operation on SL

user

SCP

SSP

INAP operations between SRP and SCP are encapsulated in ISUP messages:

Alcatel 8686SRP

SSRRPP

INAP signaling exchanged according to UUS1 or UUS3 standard. In both standards: INAP operation is encapsulated in the UUI (User to User Information) field of ISUP messages.

Several versions of ISUP exists:z ISUP V1z ISUP V2 also known as ISUP Stockholmz ISUP 97 also known as ISUP V3 (supported by the Alcatel 1000 E10 R25)

In Indirect mode, the signaling exchange between SCP and SRP is done via ISUP messages according to two standards: User-to-User signaling service 1 (UUS1) or User-to-User signaling service 3 (UUS3). These standards are described in Recommendation I.257.1 (stage 1). The functional description (stage 2) for this service can be found in Recommendation Q.87. The stage 3 DSS 1 description is given in Recommendation Q.957.1.

UUS1 and UUS3 are both supported by the SRP. The choice depends on the switch capabilities.


2.80

AustraliaFrance International

VLR

MAPMAP

SCCP SCCP

MTPMTPMTPMTPMTPMTP

SP

STPSCCP

gateway

STP STP

SPSCCP

gateway

HLR

MTP

SCCP SCCP

2.2 SS7 Management TCAP/INAP Management - SCCP Addressing (1/2)

Why SCCP addressing is required?

SCCP: Signaling Connection Control Part. STP: Signaling Transfer Point for routing MTP messages. MAP: Mobile Application Part. Protocol used for inter-PLMN equipment dialog. Why do we need the SCCP layer?

Lets consider 2 equipment (ex: a VLR in Australia and a HLR in France) which need to exchange some signaling messages without any telephone circuits involved between these equipment. This a pure signaling procedure. SCCP routing is here required because the VLR does not know the SPC of the French HLR!

First step: the SCCP layer in the VLR is used to translate a routable address (in our example: the IMSI of the mobile subscriber) into the SPC of an Australian SCCP gateway. An SCCP gateway is an equipment that routes SCCP messages, just like the STP routes MTP messages in fact. This routable address is what we call the Global Title (GT).

Second step: the message is sent to this Australian gateway which analyses the GT included in the message to define the routing: France.

Third step: the message is then forwarded to the French SCCP gateway, and so on until it reaches its final destination, the HLR.

Remember: the SCCP layer provides a Global Title translation service.


2.81

MAP

SCCP

MTP3

INAP- CS1

ISUPSSN

SCCP header

SIMTP3 header

INAP- ER1

2.2 SS7 Management TCAP/INAP Management - SCCP Addressing (2/2)

What is a SSN (SubSystem Number)?z Code included in the SCCP headerz Used by the message distribution function to identify the

system type and the protocol (SCCP User) used.z Examples of SSN codes:

SSN Protocol12 INAP

146 CAP (SSP-SCP)147 MAP(SCP-HLR)

The SSN identifies a sub-system accessed via the SCCP and may be a User Part, e.g.: ISUP, INAP, MAP When examination of the DPC in an incoming message has determined that the message is for that SP, examination of the SSN

identifies the concerned SCCP User.z Eg.: SRP sends a message INAP Assist Request Instruction to SCP. Once the message gets to the SCP, the message

distribution function examines the SI (Service Indicator in MTP 3 layer) which indicates which User Part the message is for. If the message is for ISUP, SI=5; At the MTP level, some User Parts such as MAP, INAP-CS1, INAP CS2 are not coded in the SI field. Our message is for an SCCP User (SI=3) and it is only during SCCP analysis that we will find out the SCCP User. How will we find this out? By looking at the SSN field in the message SCCP header!


2.82

Destinations have to be created beforehand! You can create an SSN now without any destination and add destinations to it later.

2.2 SS7 Management TCAP/INAP Management - Local Sub-System Number Object

Local SSN Object:Contains the Signaling Points allowed/forbidden to access the local equipment.

This window allows to configure the local SSN, that is the SSN of SRP. name: Object identifier. N7endPoint name: Local Signaling Point name (SP of SRP).SSN: Sub-System Number of our SRP.Remote SSN: NOT checked - meaning it is a local SSN.API: Must be TCAP. Why??? Since SSN is a field of SCCP!!!Point Code List: list of all SP that can have access to our SRP.Destination name: distant Signaling Point (Destination object) that can access our SRP application (referred to by SSN).Stack specific information: must be Ulticom.


2.83

2.2 SS7 Management TCAP/INAP Management - Distant Sub-System Number Object

Distant SSN Object:

This window allows to configure a distant SSN with which the SRP has to communicate.z name: Object identifier. z N7endPoint name: local Signaling Point Name (SP of SRP).z SSN: Sub-System Number of remote application.z Remote SSN: box checked - meaning it is a remote SSN.z N7destination name: distant Signaling Point (Destination object) containing the application referred by SSN.


2.84

2.2 SS7 Management TCAP/INAP Management - Global Title

What is a Global Title (GT) ?

z A GT is an address, such as a dialed-number, (E164) which does not explicitly contain information that allow the routing of the message in the signaling network.

z The translation function of the SCCP layer is then needed, to transform that dialed-number into a DPC + SSN.

GT is an address which cannot be used directly for routing within the signaling network. The GT translation function of the SCCP is required to transform the GT into a Destination Point Code and a SSN. The DPC can either be the destination point or a transfer point in the signaling network.

The address translation may be continued until the final destination is reached, meaning that the GT is carried over the signaling network.


2.85

The global title address field in SCCP header contains the Global Title Address Information (GTAI)plus other parameters depending on the value of the Global Title Indicator (GTI):

GTI = 1: + nature of address indicator (NAI)GTI = 2: + translation type (TT)GTI = 3: + translation type and numbering plan (NP) GTI = 4: + TT, NP and nature of address indicator (NAI)

The window appearance changes according to GTI. Here GTI= 4 so window shows NAI, TT, NP, GTAI.

2.2 SS7 Management TCAP/INAP Management - Global Title Object (1/2)

GT Parameters: definition of the value and the format of a Global Title:

If GT Indicator (GTI) = 1, the Global Title field in the SCCP header contains:z Nature of address Indicator (NAI)z Global Title Address Information (GTAI) - this field always figures in the Global Title field whatever the value of GTI

If GT Indicator (GTI) = 2, the Global Title field in the SCCP header contains:z translation type (TT) + GTAI

If GT Indicator (GTI) = 3, the Global Title field in the SCCP header contains:z translation type (TT) + Numbering plan (NP) + GTAI

If GT Indicator (GTI) = 4, the Global Title field in the SCCP header contains:z translation type (TT) + Numbering plan (NP) + Nature of address Indicator (NAI) + GTAI

Nature of Address Indicator (NAI) when present in the SCCP header means that the Global title is a:z 1: subscriber Numberz 3: National significant numberz 4: International Number


2.86

Translation type (TT) codes:0: unknown1


2.87

Hot-standby is mandatory

2.2 SS7 Management TCAP/INAP Management - Global Title Translation Rule Object

GT Translation Rule allows to associate one GT with one couple SPC/SSN:

Here you really impact the N7 stack when you create, modify or delete an instance. All creations, modifications and deletions are NOT committed directly. The purpose of this is that you can use the test method after a creation or modification before the rule is really used by the system.

The test method prompts you for a party address (see test_gtt command in s7mp reference manual). Once your modifications are correct, use the Create method from the menu. This will activate all current rules and effectively delete in the stack any rule you tested the deletion of.


2.88

GT Destination SPC Route Linkset Link Datalink

GT GT

Translation table

TCAP

INAP

SCCP SP

SPC SPC

MTP

SRP

GT SPC + SSN

SP

message sent on SLC

2.2 SS7 Management TCAP/INAP Management - Global Title Translation Rule

GT Translation Rule: the Routing Indicatorindicates if the routing is:z based on GT

used for intra or inter-network messages if the SPC of destination is not known.

Requires a SCCP relay (1) or SCCP international gateway (2)

z or based on originating and destination SPC + SSN used for intra-network messages if the SPC of

destination is known. No SCCP relay used.

(1) SCCP relay: equipment capable of routing SCCP messages in the national network.

(2) SCCP gateway: equipment capable of routing SCCP messages in the international network.

Routing indicator:z Flag included in the SCCP header.z keep existing (Ulticom default value) means that the equipment is routing a message from one machine to another.

The values in SCCP header are sent out the way they were received.


2.89

2.2 SS7 Management TCAP/INAP Management - SCCP Configuration Summary

SCCP configuration summary:z Objects have to be created in a specific order:

Order Object Name Description

1 Local SSN Sub-System Number value of SRP

2 Remote SSNSSN of a distant application (Ex: a prepaidapplication in SCP) that communicates with

the SRP.

3 Global Title Define the value and format of a GT

4 Global Title Translation Rule Associate a GT with a couple SPC+SSN


2.90

2.2 SS7 Management TCAP/INAP Management - DLI Configuration

To configure the DLI, use the DLI CONFIGURATION and SCP INFORMATION objects under TCAP/INAP item:

2 objects for DLI configuration

These objects allow the operator to configure the interface between SRP and SCP so that INAP operations can be exchanged between these 2 equipments.


2.91

2.2 SS7 Management TCAP/INAP Management - DLI Configuration Object (1/2)

General Information:

Name: dli-conf Link Management: z Direct link: the SRP receives INAP messages. The transport of these messages is based on:

TCAP over N7 signaling (default) or on TCAP over DpeRouter (TCP/IP). TCAP over DpeRouter box checked in that case.

z Indirect link: the SRP receives ISUP messages. z Both of them: SRP can handle both (INAP and ISUP messages).

Force UUS3: The UUSIndicator field in IAM is optional. What happens if the SRP receives an IAM with nothing in UUSInd? If the force UUS3 flag is checked, the SRP forces the dialogue to be done in UUS3. A Request Report User To Service Information (RRUTSI) message is sent to the SSP for forcing UUS3 use. The SRP will then send/receive INAP operations encapsulated in ISUP messages according to UUS3 standard. Note: You cannot modify this parameter if Indirect link is selected in the Link management frame.

Timer ARI: 1..10 in seconds, timer for the response from the SCP. IpSSPCapabilities present in ARI: feature required for CAP V2. This optional parameter may be sent in ARI to indicate to

SCP which SRF resources are supported within the SRP. By default the field is checked and set to C0 meaning nothing is supported (ex: voice back not supported by SCP). For more information refer to Recommendation Q.1218.

Timer for the CTR: 1..10 in seconds. The CTR (ConnectToResource) operation is the SCP response to ARI. In the SRP this field is set to 1 by default to specify that we dont wait the CTR message. After 1 s SRP assume there was a CTR.

After answering of SCP: CTR after SCP answering. If checked, SRP waits for SCP reply before checking availability of resources on SRP. Normally this option is not checked and SRP looks for resources as soon as it gets the IAM message.

ANM sent by DLI: SRP connection Mode. z Box unchecked: ACM+ANM sent just after reception of IAM: charging starts at that point (every interaction with user will be

charged).z Box checked: ACM (but not ANM) sent after reception of IAM. Interaction with user will not be charged until the ANM is

sent. Useful if the operator wants to play free announcements (ex: welcome announcements).


2.92

2.2 SS7 Management TCAP/INAP Management - DLI Configuration Object (2/2)

Location of SCFid and Correlation Id:

Location of SCFId and CorrelationId:z in ISUP specific parameters (SCFId and CorrelationId parameters in ISUP V2 or V3)

what is the format of the SCFId and CorrelationId? Should they be read as: Generic Digits: default format. (cf ISUP Recommendation Q.763) Generic Numbers (cf ISUP Recommendation Q.763) Other: SRP will not analyse the content of SCFId

The network operators have to agree on a format for these parameters.z or in CldPartyNumber parameter (ISUP V1)

Order of e

2 srp operation

Documents

srp statistics

srp management gui

vh zza

management session

srp operation2

srp data

vt zza

management pc