E-Book - SS7 Tutorial

SS7 1 January 2001

Signaling System 7 - SS7

566-013-09Revision C

SS7 2 January 2001

Copyright

Copyright 2001 Empirix, Inc.

All rights reserved

Printed in the United States of America

Warranty

Information in this document is subject to change without notice. Companies, names, and data used in examples herein are fictitious unless otherwise noted. No part of this document may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without the express written permission of Empirix, Inc. All third party hardware and software products mentioned in this guide are the registered trademarks of their respective companies or holders.

SS7 3 January 2001

Table of Contents

Manual Conventions…………………4 Board Utility - SS7/ISDN…………………33

Course Overview……………………..5 Configure SS7………………..………...….35

Hammer Product Overview…………6 Configure MTP Layer……………………36

Description of SS7..…………………..7 Create Link and Route on T1/E1………...38

SS7 Components …………...…… .….8 Create Link with V.35…………………….39

Signaling Links …………….………...9 Edit Link……………...…………...………40

SS7 Structure ……..………………...11 Configure ISUP Layer……….....………...41

SS7 Standards ……...……………….12 Configure TUP Layer…………...………..43

Call Setup………………….…….…..13 Timeslot to CIC Mapping………...………45

Call Release …...………………..…...14 Save Configuration.…………………...….47

Physical SS7 Link Interface ...……...15 Delete Configuration ……………..……...48

SS7 Board ……………..…………….16 Exercise 1………………………...………..50

SS7 Signaling over T1/E1………..….17 Exercise 2……………………………….…59

SS7 V.35 Board ……….………….…19 Exercise 3………………………….………68

V.35 Configurable Pod…………..…20 ISUP Trace………………………………..72

DTE&DCE Configuration….….…..21 Programming with Hammer SS7………..73

SS7 Signaling Over V.35.…...….…..22 Exercise 4……………………...…………..75

Hammer SS7 Glossary………….….23 SS7 Parameters………………….………..76

Configuration Files…………………25 Exercise 5 …………………………...…….77

Starting HammerSS7…………..…..27 Exercise 6……………...……………….….81

TxAlarm…………………………….28 Hammer - SUT Communication…………86

Hammer Login……………………..30 Calling - Called Party Messages …………87

Configuring HammerSS7………….32 Hammer SS7 Toolbars……………………88

Exercise 7………………………………….92

SS7 4 January 2001

Tutorial Conventions

Menu selections are indicated in bold with the main menu choice divided from the sub-menu choices by ->. Icons and buttons, that you need to click on, field names in dialogs, and text you have to type in the dialog fields are also indicated in bold.

Some terms or steps in the procedures are italicized to make them more visible.

When creating scripts, instructions, or portions of instructions, that you have to type are indicated in bold, and icons that you have to click on in order to insert lines of code are indicated in regular font style.

Procedures which require multiple steps are numbered.

This tutorial is provided for self-paced training. For more in-depth information on the HammerSS7 configuration files and low level programming please refer to the HammerSS7 On-line Help and the NMS web site:

1. Navigate to the NMS web site at

http://naturaledge.nmss.com/support/nms_support.nsf/frmMain

2. Select Product Manuals

3. Scroll down to

- Signaling System 7 (SS7)\ Installation and Configuration Manual

P/N 6464-13

- SS7 ISDN User Part Developer’s Manual

P/N 6471-25

SS7 5 January 2001

Course Overview• Description of SS7

• SS7 Components

• SS7 Structure and Standards

• Call Setup and call release

• SS7 Signaling over T1/E1 and V.35 Pod

• Configuration Files

• Board Utility - Configure SS7

• Programming with Hammer SS7

SS7 6 January 2001

Hammer Product Overview• HammerFAX

• Hammer Integrated Telecommunications Systems, HammerIT

• Hammer Integrated Stress Generator Systems, ISGII

• Hammer ISDN

• Hammer Operations Platform, HammerOP

• Hammer SS7

• Prompt Tag Builder

• Simplified Message Desk Interface, SMDI

• Speech Recognition

• Suite Master

• Hammer TCP/IP & Serial Port Communications

• Voice over IP, HammerIP

SS7 7 January 2001

Description of SS7

• Uses a specialized packet switched network to transmit call processing information

Exchange1

Exchange2

SS7 circuits

Voice circuits

The SS7 circuits are separate from the voice circuits and are used solely for switching data messages, for connecting telephone calls and maintaining the signaling network.

SS7 was originally defined as Common Channel Signaling and was first introduced in the U.S.A. in the 1960s.

The SS7 network and protocols are used for:

- call setup, management, and tear down

- local number portability (LNP)

- 800/888/877 and 900 calls

- enhanced call features (call forwarding, caller ID, three-way calling etc)

- wireless services for roaming, subscriber authentication

SS7 8 January 2001

SS7 Components

• SSP - Service Switching Point

• STP - Signal Transfer Point

• SCP - Service Control Point

SSP

SSP

STP

STP

SCP

SCP

Voice signalsSS7 signals

SSP - switches where the calls originate or terminate (local exchange). SSP sends messages to other SSP to setup, manage, and release voice circuits, performs database queries for additional information routing (800/888/877 and 900 calls). It requires ISUP and TCAP layers.

STP - serves as a router in the SS7 network. All SS7 packets travel from one SSP to another through STP. STP also performs global title translation. There are three levels of STPs:

- National STP - transfers messages using the same national standard of protocol (e.g. ANSI)

- International STP - same as national STP, but uses the international SS7 standard (ITU-TS)

- Gateway STP - provides protocol conversion from a national standard to ITU-TS and serves as the interface into another network.

SCP - serves as an interface to telephone company database (information about subscriber’s services, 800/888/877 and 900 numbers, calling card validation and fraud protection). SCP uses TCAP for database queries. The most commonly used databases are: Call Management Services Database (CMSDB), Line Information Database (LIDB), Business Services Database (BSDB), Home Location register (HLR), and Visitor Location register (VLR).

SSP, STP, and SCP are called signaling points, SP.

Signaling Links - 56 or 64 kbps digital links, A through F.

SS7 9 January 2001

Signaling Links (1)

Regional

Local

ASCPSCP

STP

STP

C

A

SSP STP

SSP SSP

SSP

STPSTP

STP

C CF

B

DE

B

Signaling links are logically organized according to their use in the SS7 network. There is no difference between the various links, only in the way the links are utilized during message transfer and the way network management interacts with the links.

A - Access links between end points (e.g. an SCP or SSP) to an STP

B - bridge links connect an STP to another STP. Typically, a quad of B links interconnect peer STPs (e.g. STPs from one network to the STPs of another network).

C - Cross links connect STPs performing identical functions into a mated pair.

D - Diagonal links connect mated pairs of STPs at different hierarchical level.

E - Extended links connect SSps to a remote STP pair. E links privide an alternate signaling path if an SSP’s home STP cannot be reached via an A link.

F - Fully associated links connect two signaling end points (e.g. SSps and SCPs).

SS7 10 January 2001

Signaling Links (2)

SSPSSP

STPSTP STP

SSP SSP

Signaling Path

Voice Trunk

Signaling PathSignaling Path

Voice Trunk

Non-associated signaling Quasi-associated signaling

Non-associated signaling - uses a separate logical path from the actual voice. There are multiple nodes involved to reach the final destination although the voice signal may have a direct path to the destination number.

Quasi-associated signaling - uses a minimal number of nodes to reach the final destination.

Links are placed into groups - linksets. All the links in a linkset must have the same adjacent node.

A route is a collection of linksets used to reach a particular destination.

SS7 11 January 2001

SS7 Structure

7 Application

6 Presentation

1 Physical

5 Session

4 Transport

3 Network

2 Data Link

MTP Level 1

MTP Level 2

MTP Level 3

TUP

ISUP

TCAP

SCCP

Message Transfer Part Level 1 (MTP Level 1) - equivalent to the OSI Physical layer; defines the physical, electrical, and functional characteristics of the digital signaling link. Physical interfaces defined include E1 (2048 kbps), DS1 (1544 kbps), V.35, DS0 (64 kbps), and DS0A (56kbps).

MTP Level 2 - provides error detection/correction, flow control, and message sequence validation. When an error occurs on a signaling link, the message is retransmitted.

MTP Level 3 - provides message routing between signaling points in the SS7 network. It reroutes traffic away from failed links and signaling points and controls traffic when congestion occurs.

ISDN User Part (ISUP) - defines the protocol used to setup, manage, and release trunk circuits that carry voice and data between the parties.

Telephone User Part (TUP) - is used in countries that follow ITU-ISU standards.

Signaling Connection Control Part (SCCP) - provides connectionless and connection-oriented network services and global title translation capabilities (a global title is an address, e.g., a dialed 800 number, calling card number, which is translated by SCCP into a destination point). SCCP is used as the transport layer for TCAP-based services.

Transaction Capabilities Application Part (TCAP) - to access network databases. It supports functions required to connect to an external database, perform a query, and retrieve information.

SS7 12 January 2001

SS7 Standrads

• 1980 Yellow Book

• 1984 Red Book

• 1988 Blue Book

• 1992 White Book

The following organizations have written standards related to SS7: International Telecommunications Union - Telecommunications Standardization Sector, ITU-TS, American National Standards Institute, ANSI, and bell Communications Research, Bellcore.

National operators can modify signaling to their own requirements. Only the international gateway switches have to be 100% compliant.

The ITU has released a series of recommendations, referred to as “books”, on how signaling should be implemented.

The following list identifies all SS7 documents:

Q.700 - Q.709 Message transfer Part (MTP)

Q.710 PBX Application

Q.711 - Q.716 Signaling Connection Control Part (SCCP)

Q.721 - Q.725 Telephone User Part (TUP)

Q.730 ISDN Supplementary Services

Q.741 Data User Part (DUP)

Q.761 - Q.766 ISDN User Part (ISUP)

Q.771 - Q.775 Transaction Capabilities Application Part (TCAP)

Q.791 - Q.795 Monitoring, Operations, and Maintenance

Q.780 - Q.783 Test Specifications

SS7 13 January 2001

Call setup

SSP SSPSTP

OFF-HOOK

DIAL TONE

DIGITS IAM IAM SETUP

ALERTINGACMACM

RINGTONEOFF-HOOK

ANMANM

CONNECT

An Initial Address Message (IAM) is sent in the “forward” direction by each switch needed to complete the circuit between the calling party and the called party until the circuit is connected to the destination switch. The AIM includes the originating point code, destination point code, circuit identification code, CIC, dialed digits, and the calling party number and name.

A Circuit Identification Code (CIC) - identifies the circuit being reserved by the originating switch to carry the call.

An Address Complete Message (ACM) is sent in the backward direction to indicate that the remote end of a voice circuit has been reserved.

An Answer Message (ANM) is sent by the destination switch when the called party answers.

SS7 14 January 2001

Call Release

SSP SSPSTP

DISCONNECT

RELREL

RELEASERLC

RLCRELEASE

DISCONNECT

REL ACK

A Release message (REL) is sent in either direction, when either the calling party or the called party hangs up, indicating that the circuit is released. It is also sent in the backward direction if the called party is busy.

A Release Complete message (RLC) is sent to acknowledge the release of the remote end of a circuit.

SS7 15 January 2001

Physical SS7 Link Interface

• SS7 link interface may be:– timeslot(s) on one of the T1/E1 boards

– a V.35 link

Two types of boards are needed to support the SS7 protocol: T1/E1 board(s) and SS7 board(s), Tx3000.

Depending on the physical hardware configuration of your TX Series boards, the physical SS7 link interface between Hammer SS7 board(s) and a system under test may be:

- timeslot(s) (one or more timeslots) on one of the T1/E1 boards

- a V.35 link

In the first scenario up to four time slots can be set aside for SS7 signaling on the Hammer system.

In the second scenario all voice channels on T1/E1 board are used for transmitting voice and SS7 signaling is transmitted over V.35 configurable pod.

Each Tx3000 board can support up to four links on T1/E1 board(s) and up to three SS7 V.35 serial link interfaces.

SS7 16 January 2001

SS7 Board

On T1/E1 board one or more voice channels are reserved for SS7 signaling. Any voice channel can be configured to carry SS7 signaling. Most often it’s the 24th channel on T1and 16th channel on E1. T1/E1 board installed in a Hammer system communicates with the outer world and not the SS7 board.

SS7 board and T1/E1 boards installed in a Hammer system communicate via MVIP bus.

All the necessary SS7 software resides on the SS7 board.

SS7 17 January 2001

SS7 Signaling Over T1/E1 (1)

SSP

SystemUnder

Test, SUT

T1/E1 Line

IAM, ACM(Link for SS7 Signaling)

Voice channels

Hammer

T1/E1 Board

SS7 Board

MVIP

The Hammer systems are most often connected to SSP.

SS7 signaling is transmitted from the T1 board to SSP on channels configured to carry SS7 signaling. After SSP receives SS7 signaling it assigns voice channels for the calls. Once the voice channels are assigned, voice signals are transmitted on them.

SS7 18 January 2001

SS7 Signaling Over T1/E1 (2)

IAM, ACM messages(Link for SS7 Signaling)

Hammer

T1/E1 Board

SS7 Board

SUT

SS7

Voice

T1/E1 Line

Up to four T1/E1 channels are used for SS7 signaling between a Hammer system and the SS7 portion of the SUT. The rest of the T1/E1 channels are used for voice transmission.

SS7 19 January 2001

SS7 V.35 Board

V.35

V.35 outlet

V.35 board is a daughter board to SS7 board. It has its own socket and it is connected to V.35 configurable pod. SS7 signaling is transmitted over the SS7 cable. Once the voice channels are assigned, voice signals are transmitted over T1 line.

SS7 20 January 2001

V.35 Configurable PodOuter screws

V.35 is used from a data service unit to the SS7 signaling point. It provides data rates up to 56 or 64 kbps.

DS0A interface is a 56 or 64 kbps , used in DS1 or higher facility.

Each port on the pod is configurable to suit the device connected to it by setting jumpers located inside. The pods can be configured as Digital Carrier Equipment, DCE, or Digital Terminal Equipment, DTE. The factory default setting is DTE. The DCE configuration makes the Tx3000 appear as a DCE device.

Three physical links (from one SUT or from three SUTs) can be connected to one V.35 pod.

To set the pod jumpers for DCE, remove the outer screws form the V.35 pod.

SS7 21 January 2001

DTE & DCE Configuration

DCE

DTE

DTE Configuration

DCE Configuration

The picture of the jumpers settings for DCE and DTE is shown in the slide.

The V.35 Configurable Pods allow you to configure the connectors to match the equipment.

Each port on the pod is configurable to suit the equipment it is connected to by setting jumpers inside the V.35 box.

The slide illustrates the position of the jumpers for DTE and DCE Configuration.

Continue

SS7 22 January 2001

SS7 Signaling Over V.35 Pod

Hammer

SUT1SUT3 SUT2

T1 Boards

SS7 Board

T1 T1 T1SS7 SS7 SS7

Up to three Systems Under Test, SUTs, can be connected to a V.35 Configurable Pod and tested with one HammerSS7 system.

SS7 23 January 2001

Hammer SS7 Glossary (1)

Hammer SUT

V.35 V.35

T1/E1 Boards

SS7 Board

Circuit Group

LinksetLink

MVIP

Voice

SS7

Circuit Group - a group of voice channels that connect one Hammer system with a SUT.

Link - channel that transmits SS7 signals between a Hammer system and a SUT.

Linksets - groups of links.

SS7 24 January 2001

Hammer SS7 Glossary (2)

Node 1.1.1

Node 1.1.2

Node 3.1.1

Node 2.1.1

Node 4.1.1

Hammer

Local Nodes

Adjacent nodefor Node 1.1.1

Adjacent nodefor Node 1.1.2

Non-adjacent nodefor Nodes 1.1.1 and1.1.2

Route

Link

Link

Link

Link

SS7 Boards

Local Node - each SS7 board, installed in a Hammer system, represents an SS7 local node.

Adjacent Node - neighboring node to a local node. The SS7 link can be created between a local node and its adjacent node.

Route - group of links that connect non-adjacent nodes. In our slide the route from node 1.1.1 to node 4.1.1 consists of two links, one that connects nodes 1.1.1 and 2.1.1 and the other that connects nodes 2.1.1 and 4.1.1.

SS7 25 January 2001

Configuration Files

• C:\nms\ag\cfg\ag.cfg -this file is not specific to SS7

• C:\tektx\config\ht_tdmcp1.txt -defines the connection between the SS7 board and the MVIP bus

• C:\tektx\config\ht_mtp3cp1.cfg -configuration file for the SS7 MTP2 and 3 layers

• C:\ tektx\config\ht_isupcp1.cfg -configuration file for the SS7 ISUP layer

Each layer of the SS7 protocol has a separate configuration file.

For more information on the HammerSS7 configuration files please refer to the NMS SS7 Installation and Configuration Guide in the Appendix.

SS7 26 January 2001

AG.CFG

• Common Section– DIGITALMODE = RAW

– RunFile = systn.run # for ISA Boards

– RunFile = sysqn.run # for Quad/Dual Boards

AG.cfg - specifies whether a board connects to the MVIP bus, communications protocols that are used, how is clock defined for the board.

ClockRef = OSC: master clock is generated from the board

ClockRef = MVIP: the clock is taken from the MVIP bus

ClockRef = NET1: the clock is taken from the network

The first board, Board 0, always provides clocking => for Board 0 ClockRef = OSC/NET1.

All additional boards must have ClockRef = MVIP.

When a new board is added to the system, a new board definition must be added to AG.cfg.

You can add new boards, but be aware that software/hardware not supplied by Hammer Technologies should not be added to the system; doing so voids the system warranty. Consult with Hammer technical support.

SS7 27 January 2001

Starting HammerSS7

If your HammerSS7 has been configured and you do not want to make any changes in the configuration, you don’t run Board Utility when you are bringing your Hammer up.

To start HammerSS7:

1. Make sure that the Database is on (if it is on, ht_servername in the Windows NT Taskbar is displayed).

2. If it’s not displayed, click

Start -> Programs -> Hammer -> Database Server Start

3. Click ht_server name icon in the Windows NT Taskbar and you will get the dialog shown in the slide.

Continue

SS7 28 January 2001

TxAlarm

4. In order to monitor the Hammer processes bring up the Alarm utility:

Start -> Programs -> NMS INDC -> TxAlarm

Continue

SS7 29 January 2001

Telephony Loader

5. Wait for “Now accepting requests” to show in the Messages section of theDB dialog.

6. Double-click the Telephony Loader icon, or click Start on the Windows NT taskbar:

Start -> Programs -> Hammer -> Telephony Loader

7. Bring the Hammer up

Start -> Programs -> Hammer

or double-click the Hammer icon.

Continue

SS7 30 January 2001

Hammer Login

TESLAPUPINSAVA

8. The Hammer Login dialog appears.

9. Click OK.

10. To check whether your server is up and running, right-click on the empty space of the Windows NT Taskbar and the Task Manager dialog is brought up -> Processes.

In the list of Processes you should see htserver.exe if your server is up and running.

To get access to server(s) from a remote client:

1. Follow steps 7 and 8.

2. Select the servers you want to get access to.

3. Click OK.

Continue

SS7 31 January 2001

Bringing Hammer up Successfully

To check whether your Hammer is up and running properly:

1. Click ht_server name icon in the Windows NT Taskbar and you will get the ht_servername dialog shown in the slide.

2.If in the Multi user SQL Anywhere: ht_servername (per seat) dialog under Userid you see the list of all Hammer channels plus three userids for Hammer components, your Hammer was brought up successfully.

3. When you see the following message in the TxAlarm window:

MTP3 Link 0 Up

Resume received from MTP

SS7 is up and ready to run.

SS7 32 January 2001

Configuring HammerSS7

If you want to configure your HammerSS7, you have to run Board Utility when you are bringing your Hammer up.

To start HammerSS7:

1. Make sure that the Database is on (if it is on, ht_servername in the Windows NT Taskbar is displayed).

2. If it’s not displayed, click

Start -> Programs -> Hammer -> Database Server Start

3. Click ht_server name icon in the Windows NT Taskbar and you will get the dialog shown in the slide.

4. In order to monitor the Hammer processes bring the Alarm utility up:

Start -> Programs -> NMS INDC -> TxAlarm

5. Wait for “Now accepting requests” to show in the Messages section of theDB dialog.

6. Double-click the Telephony Loader icon, or click Start on the Windows NT taskbar:

Start -> Programs -> Hammer -> Telephony Loader

Continue

SS7 33 January 2001

Board Utility - SS7/ISDN

7. Double-click the Board Utility icon, or click Start on the WindowsNT taskbar:

Start -> Programs -> Hammer ->Board Utility

and the Board Configuration Utility dialog is brought up.

The SS7 check boxes appear to the left of each board listing. These boxes let you specify that a resource board is enabled for SS7.

8. To enable SS7 functions: Click and highlight the appropriate board, which is used forSS7 signaling in your Hammer system, listed in the Resource Boards list box. A check appears in the box to the left of the board listing.

Click until the appropriate function appears to the right of the board type.

9. If you specify a resource board as an SS7 board, the SS7 Signaling Only check box becomes active. This check box lets you specify whether the selected board is to be used exclusively for SS7 signaling:

- Check this box if the selected resource board is to be used for SS7 signaling only

- Do not check this box if the board is to be used for both T1 and SS7 signaling

10. You can save the configuration you want using the Board Utility dialog. The list of various saved configurations is displayed when you click the arrow in the Configure System As... field.

11. To save the Current configuration click the Save Configuration button.

Continue

SS7 34 January 2001

Save Configuration (1)

12. Save Configuration As…dialog is displayed. Type in the name of your configuration.

13. Click OK .

14. The BrdUti l dialog is displayed, click Yes.

15. The Registry Editor dialog is displayed, click OK .

At this point you don’t have to run Telephony Loader, it will be run by Board Utility.

16. Click the SS7 Configuration button and the Configure SS7 dialog is displayed.

Continue

SS7 35 January 2001

Configure SS7

Activated if the corresponding layer is enabled

The SS7 Configuration Tool is used to configure all Tx3000 boards. Buttons ISUP, TUP, SCCP,TCAP are enabled/disabled according to the Hammer SS7 license. Clicking each of the buttons you bring up a dialog to configure an SS7 layer. When the configuration tool is used on the system where Hammer SS7 configuration files have not been created, the following files are created: ht_tdmcp<SS7 board number>.txt – the TDM files for each SS7 board installed;

ht_Mtp3cp<SS7 board number>.cfg – the MTP files for each SS7 board installed;

ht_Isup<SS7 board number>.cfg – the ISUP files for each SS7 board installed (if licensed);

ht_Tup<SS7 board number>.cfg – the TUP files for each SS7 board installed (if licensed);

ht_Sccp<SS7 board number>.cfg – the SCCP files for each SS7 board installed (if licensed);

ht_Tcap<SS7 board number>.cfg – the TCAP files for each SS7 board installed (if licensed);

ht_SS7load< SS7 board number>.bat – the SS7 load batch files for each SS7 board.

Users should not change the names of these files.

Automatic Responses - enable this box if you want your Hammer system to respond to theSUT’s circuit management messages (Block, Unblock, Circuit Group Block, etc).

Send Block Messages - enable this box if you want the initial state of your Hammer System to be Blocked. Trace Messages into File - (not recommended because it affects the performance) if enabledtrace messages are saved in the C:\Hammer\LogMsgs directory.

SS7 36 January 2001

Configure MTP Layer (1)

1. Click the MTP button. Board utility checks how many Tx3000 boards are installed in the Hammer system.

2. The Configure MTP Layer dialog is displayed. The installed Tx3000 boards are listed in the Select SS7 Board section.

The Local Nodes section displays a Local Node identification code assigned to the Tx3000 board selected in the Select SS7 board section. If MTP files are not available because they have not been created, the Local Nodes list is empty. The Add button enables users to add a node, the Remove button enables users to remove the node selected in the list.

The All Nodes section displays all the SS7 Nodes available – local, adjacent and non-adjacent. The Add button enables users to add a node, the Remove button enables users to remove the node selected in the list.

The SS7 Link can be created between a Local Node and any other node, different from Local. The latter node is an adjacent node to the Local Node.

The Create Link button enables users to create links between a node in the Local Nodes list and nodes in the All Nodes list.

The Remove Link button enables users to delete a selected link.

The Routes section displays all the Routes, created and/or initialized from the MTP file, if available.

The Remove Route button enables users to remove a route from the list of routes.

3. Highlight a board in the Selected SS7 Board list for which you want to add a local node.

Continue

SS7 37 January 2001

Configure MTP Layer (2)

4. To add a node to the list of Local Nodes click the Add button in the Local Nodes section. The Add Node dialog is displayed.

5. Type in the point code for the node you are adding (e.g. 1.1.10). In the Hammer system, the point code parameter can be entered in hexadecimal (e.g. 0x1234) or in dotted notation (e.g. 98.124.21). We will use dotted notation in our examples.

6. Click OK.

7. If you want to remove a node from the list, highlight the node and click the Remove button in the Local Nodes section.

8. Highlight the second board in the Select SS7 Board list (if you have more than one SS7 boards) and repeat steps 4 through 6. The point code for the second Hammer node will be different, e.g. 1.1.2)

9. Now we have to add adjacent and non-adjacent nodes to the list of All Nodes. Click Add in the All Nodes section and the Add Node dialog displays.

10.Type in the point code for the node you are adding (e.g. 1.1.9).

11. Click OK.

12.Repeat steps 9 - 11. Point code will be different for other nodes.

13.Next we have to create Links. Highlight one node in the Local Nodes section and one in the All Nodes section if these two nodes are going to be physically connected.

14.Click the Create Link button.

15.The Create Link dialog displays.

Continue

SS7 38 January 2001

Create Link and Route on T1/E1

If you are using T1/E1 boards for SS7 signaling, proceed to the next step. If you are using V.35 for SS7 signaling, go to the next page.

16. If you are using the ANSI standard accept the default values in the dialog.

17.If you are using the ITU-T standard in the Link Type field select ITU-T, in the DPCLength field select the value appropriate for your system(14 or 24), and in the SSF field select INTERNATIONAL.

18.In the Links, Physical Resources section all the T1 boards channels are displayed. You have to highlight a channel on the corresponding T1 board (the channel which will be used for SS7 signaling). Highlight timeslot 0. Click OK.

19. If you want to remove a link from the list, highlight the link and click the Remove button in the Links section of the Configure MTP layer dialog.

20.For the selected Local Node and a node, which has no Link to the selected Local Node, the user can create a Route. In order to create a Route the user has to:

a) Highlight a Local Node;

b) Highlight a node from the All Nodes list, other than a local node, selected in a)

c) Highlight a Link through which the node, selected in b) will be reached;

21. Click the Create Route button. The Routes list displays all the Routes, created and/or initialized from the MTP file.

22.If you want to remove a Route from the list highlight the Route in the Routes list and click the Remove Route button in the Routes section of the Configure MTP layer dialog.

23. Click OK in the Configure MTP layer dialog.

SS7 39 January 2001

Create Link with V.35

16. If you are using the ANSI standard accept the default values in the dialog.


18.In the Links, Physical Resources section all the T1 boards channels are displayed and V.35 ports.You have to highlight a V.35 port for signaling. Highlight port 1. Enable DCE or DTE Interface Type radio button, depending on the function of your Hammer. Click OK.

19. If you want to remove a link from the list, highlight the link and click the Remove button in the Links section.

20.For the selected Local Node and a node, which has no Link to the selected Local Node, the user can create a Route. In order to create a Route the user has to:

a) Highlight a Local Node;

b) Highlight a node from the All Nodes list, other than a local node, selected in a)

c) Highlight a Link through which the node, selected in b) will be reached;

21. Click the Create Route button. The Routes list displays all the Routes, created and/or initialized from the MTP file.

22.If you want to remove a Route from the list highlight the Route in the Routes list and click the Remove Route button.

23. Click OK in the Configure MTP layer dialog.

SS7 40 January 2001

Edit Link

If you want to edit a link double click on the link in the Links section of the Configure MTP layer dialog. The dialog Edit Link… is displayed.

SS7 41 January 2001

Configure ISUP Layer

In the Configure SS7 dialog click the ISUP button and the Configure ISUP layer dialog is displayed.

To create a circuit group you highlight two nodes that are connected with voice channels, one in the Local Nodes list another in the All Nodes list, and click the Create Circuit Group button.

To remove a circuit group from the Circuit Groups list, highlight the group in the list and click the Remove Circuit Group button.

SS7 42 January 2001

Create Circuit Group - ISUP

When the Create Circuit Group dialog is displayed you select the channels that belong to that circuit group, type in CIC for the first voice channel in your circuit group, and in the Switch Type field select the standard that is pertinent to your system.

SS7 43 January 2001

Configure TUP Layer

In the Configure SS7 dialog click the TUP button and the Configure TUP layer dialog is displayed.

This layer is not used in ANSI standard.

SS7 44 January 2001

Create Circuit Group - TUP

When the Create Circuit Group dialog is displayed you select the channels that belong to that circuit group, type in CIC for the first voice channel in your circuit group, and in the Switch Type field select the standard that is pertinent to your system (standard for China or ITU-T).

.

SS7 45 January 2001

Timeslot to CIC MappingTimeslot to CIC mapping

Timeslot Span 0 Span 1 Span 2 Span 3 Span 4 Span 5Hammer Channel

CIC Hammer Channel

CIC Hammer Channel

CIC Hammer Channel

CIC Hammer Channel

CIC Hammer Channel

CIC

0 1 101 25 125 49 149 73 173 97 197 121 2211 2 102 26 126 50 150 74 174 98 198 122 2222 3 103 27 127 51 151 75 175 99 199 123 2233 4 104 28 128 52 152 76 176 100 200 124 2244 5 105 29 129 53 153 77 177 101 201 125 2255 6 106 30 130 54 154 78 178 102 202 126 2266 7 107 31 131 55 155 79 179 103 203 127 2277 8 108 32 132 56 156 80 180 104 204 128 2288 9 109 33 133 57 157 81 181 105 205 129 2299 10 110 34 134 58 158 82 182 106 206 130 23010 11 111 35 135 59 159 83 183 107 207 131 23111 12 112 36 136 60 160 84 184 108 208 132 23212 13 113 37 137 61 161 85 185 109 209 133 23313 14 114 38 138 62 162 86 186 110 210 134 23414 15 115 39 139 63 163 87 187 111 211 135 23515 16 116 40 140 64 164 88 188 112 212 136 23616 17 117 41 141 65 165 89 189 113 213 137 23717 18 118 42 142 66 166 90 190 114 214 138 23818 19 119 43 143 67 167 91 191 115 215 139 23919 20 120 44 144 68 168 92 192 116 216 140 24020 21 121 45 145 69 169 93 193 117 217 141 24121 22 122 46 146 70 170 94 194 118 218 142 24222 23 123 47 147 71 171 95 195 119 219 143 24323 24 124 48 148 72 172 96 196 120 220 144 244

The mapping of CIC to physical timeslot has NOTHING TO DO WITH THE HAMMER SYSTEM. The mapping of these entities is entirely arbitrary and is at the discretion of the customer.

The mapping in the slide is done for V.35 interface and it’s only one example of how this can be done.

SS7 46 January 2001

Edit Circuit Group

If you want to edit your circuit group, both for ISUP and TUP, double click on the circuit group in the Circuit Groups list in the Configure ISUP/TUP layer dialog, and the Edit Circuit Group dialog is brought up.

SS7 47 January 2001

Save Configuration (2)

When you finish configuring your layers files:

1. Click OK on the Configure SS7 dialog.

2. To save the configuration click the Save Configuration button.

3. The Save Configuration As…dialog is displayed. Type in the name of your configuration.

4. Click OK .

5. The BrdUti l dialog is displayed, click Yes.

6. The Registry Editor dialog is displayed, click OK .

7. Board Utility runs Telephony Loader.

9. Click OK on the Board Configuration Utility dialog.

10. Bring the Hammer up by double clicking the Hammer/ISGII icon on your desktop.

11. The Hammer or HammerISGII (depending what you have in your Hammer system)Login dialog appears.

12. Click OK .

13. To check whether your server is up and running, right-click on the empty space of the Windows NT Taskbar and the Task Managerdialog is brought up -> Processes.

In the list of Processes you should see htserver.exe if your server is up and running.

SS7 48 January 2001

Delete Configuration

• In Windows Explorer navigate to

C:\hammer\configuration

• Find the configuration you want to delete and delete it

To delete the configuration, right click on the configuration name -> Delete.

SS7 49 January 2001

End htserver.exe Process

For the following three exercises you have to stop your server.

1. Right-click on the empty space of the Windows NT Taskbar and the Task Manager dialog is brought up -> Processes.

2. If in the list of Processes you see htserver.exe, highlight it and click the End Process button.

SS7 50 January 2001

Exercise 1

Node 1.1.1

Hammer

Node 2.1.1T1 channel(s)for SS7 signalingor V.35

T1

Configure the SS7 Layers files for the configuration in the slide.

SUTCircuit group

Link

1. Click the SS7 Configuration button in the Board Utility dialog to start with SS7 configuration.




5. Type in the point code for the node you are adding, 1.1.1

6. Click OK.

7.To add nodes other than local nodes to the list of All Nodes click the Add button in the All Nodes section and the Add Node dialog displays.

8. Type in the point code 2.1.1.

9. Click OK.

SS7 51 January 2001

Exercise 1- Configure MTP Layer

10.To create links between nodes 1.1.1 and 2.1.1 highlight 1.1.1 in the Local Nodes section, then highlight 2.1.1 in the All Nodes section.

11.Click the Create Link button and the Create Link dialog is displayed.

Continue

SS7 52 January 2001

Exercise 1 - Create Link

12.If you are using the ANSI standard accept the default values in the dialog.


14.In the Links, Physical Resources section all the T1 boards channels are displayed. You have to highlight a channel on the first T1 board (the channel which will be used for SS7 signaling). Highlight timeslot, e.g., 0.

15.Click OK.

If you are using V.35 for SS7 signaling, follow the instructions on page 39 (Create Link with V.35).

Route for these two adjacent nodes is automatically created as the following slide illustrates.

Continue

SS7 53 January 2001

Exercise 1 - MTP Configured

Once you configure the MTP layer, the Configure MTP layer dialog will look like the one in the slide.

SS7 54 January 2001

Exercise 1 - Configure ISUP Layer

1. In the Configure SS7 dialog click the ISUP button and the Configure ISUP layer dialog is displayed.

2. Highlight 1.1.1 in the Local Nodes section.

3. Highlight 2.1.1 in the All Nodes section.

4. Click the Create Circuit Group button.

Continue

SS7 55 January 2001

Exercise 1 - ISUP Circuit Group

5. Select the channels that belong to that circuit group. Highlight, e.g., channels 1 - 23.

6. Type in CIC for the first voice channel. For our example CIC will be 1.

7. In the Switch Type field select the standard that is pertinent to your system.

8. Click OK.

Circuit Group which carries voice signals between nodes 1.1.1 and 2.1.1 is added.

Continue

SS7 56 January 2001

Exercise 1 - ISUP Configured

The Configure ISUP layer dialog will look as it is shown in the slide once you finish creating circuit groups.

SS7 57 January 2001

Exercise 1 - Configure TUP Layer

Skip this and the following slide if you are using ANSI standard.

1. In the Configure SS7 dialog click the TUP button and the Configure TUP layer dialog is displayed.




Continue

SS7 58 January 2001

Exercise 1 - TUP Circuit Group


6. Type in CIC for the first voice channel in the circuit group. For our example CIC will be 1.


8. Click OK.


SS7 59 January 2001

Exercise 2


Node 1.1.1

Node 3.1.1

Node 2.1.1

Hammer SUT

STP

T1

Link

Circuit group

Route

1. Click the SS7 Configuration button in the Board Utility dialog to start with SS7 configuration.



4. Highlight Tx3000 Board 1 in the Selected SS7 Board list .


6. Type in the point code for the node you are adding, 1.1.1

7. Click OK.

8. To add nodes other than local nodes to the list of All Nodes click the Add button in the All Nodes section and the Add Node dialog displays.

9. Type in the point code 2.1.1.

10. Click OK.

12.Repeat steps 8 through 10 for point code 3.1.1.

Continue

SS7 60 January 2001

Exercise 2 - Configure MTP Layer

Continue

SS7 61 January 2001

Exercise 2 - Create Link

13.To create links between nodes 1.1.1 and 3.1.1 highlight 1.1.1 in the Local Nodessection, then highlight 3.1.1 in the All Nodes section.

14.Click the Create Link button.

15.If you are using the ANSI standard accept the default values in the dialog.


17.In the Links, Physical Resources section all the T1 boards channels are displayed. You have to highlight a channel on the first T1 board (the channel which will be used for SS7 signaling). Highlight timeslot 0.

18.Click OK.

If you are using V.35 for SS7 signaling, follow the instructions on page 39 (Create Link with V.35)

Route for the adjacent nodes is automatically created as the following slide illustrates.

Continue

SS7 62 January 2001

Exercise 2 - Create Route

At this point in the Configure MTP layer dialog we see the list of Hammer SS7 boards, local nodes (Hammer SS7 boards point codes), the list of all nodes (adjacent to the local node and non-adjacent) the list of links between the local node and its adjacent node, as well as the list of routes between the local node and its adjacent node.

17. Now we have to create routes between the local node, 1.1.1 and 1.1.2, and node 4.1.1.

18. Highlight 1.1.1 in the Local Nodes list and highlight 2.1.1 in the All Nodes list.

19. Highlight 1.1.1=>3.1.1 in the Links section of the dialog.

20. Click the Create Route button. New route between the local node 1.1.1 and non-adjacent node 2.1.1 is created.

21. Click OK.

Continue

SS7 63 January 2001

Exercise 2 - MTP Configured

The slides shows the Configure MTP layer dialog after the MTP layer files have been configured.

SS7 64 January 2001

Exercise 2 - Configure ISUP Layer

1. In the Configure SS7 dialog click the ISUP button and the Configure ISUP layer dialog is displayed.




Continue

SS7 65 January 2001

Exercise 2 - ISUP Circuit Group


6. Type in CIC for the first voice channel. For our example CIC will be 1.


8. Click OK.


Continue

SS7 66 January 2001

Exercise 2 - Configure TUP Layer

Skip the slides related to the TUP layer Configuring if you are using ANSI standard.

1. In the Configure SS7 dialog click the TUP button and the Configure TUP layer dialog is displayed.




Continue

SS7 67 January 2001

Exercise 2 - TUP Circuit Group


6. Type in CIC for the first voice channel in the circuit group. For our example CIC will be 1.


8. Click OK.


SS7 68 January 2001

Exercise 3

Node 4.1.1

Node 1.1.1

Node 3.1.1

Node 2.1.1

Hammer


SUT

STP

STP V.35

V.35V.35

V.35

T1Circuit group

Link

Link

Follow the procedure similar to procedures in Exercises 1 and 2 and define a local node, all nodes, links, and routes.

Continue

SS7 69 January 2001

Exercise 3 - MTP Layer Configured

When you finish the procedure of configuring the MTP layer files the Configure MTP Layer dialog should look like the one in the slide.

SS7 70 January 2001

Exercise 3 - ISUP Configured

SS7 71 January 2001

Exercise 3 - TUP Configured

SS7 72 January 2001

ISUP Trace

Once you bring your HammerSS7 up you can monitor the ISUP messages exchanged between the Hammer and a SUT:

1. Start -> Programs -> Command Prompts

2. At the C prompt type in commands given with bold letters:

C:\>isupmgr

isupmgr[1]>trace data on

3. Hit Enter

4. isupmgr[1]>q

5. Hit Enter

6. isupmgr[1]>Hit Enter

7. C:\>txtrace

8. Hit Enter

The messages are in the hex format:

10:57:26.0 ISUP.1 <-- 0.0.1:

02 00 16

10:57:37.0 ISUP.1 <--0.0.1:

02 00 14

02 - Channel #; 00 14 message type in hex format; 0.0.1 is the point code of the equipment.

SS7 73 January 2001

Programming with Hammer SS7

• SS7 protocol– High-level call control HVB commands

• CCS protocol– low-level call control ISDN User Part messages

Unlike regular telephony channels, the Hammer SS7 link is hidden from users. This link is used to send out SS7 messages for all regular telephony channels in its circuit group. When the Hammer SS7 link receives incoming SS7 messages, it does not process these messages, it forwards the SS7 messages to the appropriate voice channels.

High-level programming is used with applications which do not require that the details of the SS7 protocol be understood or implemented by the tester or programmer. The commands such as placeCall, releaseCall, answerCall, rejectCall, startProtocol, stopProtocol are used.

Low-level programming is used with applications which require detailed information about call progress in order to implement a successful test by the tester or programmer. With low-level programming the script handles the sending and receiving of all SS7 messages.

Low-level function calls (messages used to send and receive Hammer SS7 messages through the SS7 links) SS7IsupMsg. It is used in the following way:

dim x as SS7IsupMsg

x.initSS7IsupMsg (msg Type)

where msgType can be HTTSS7ISUP_ConnectReq, HTTSS7ISUP_ReleaseReq, HTTSS7ISUP_DataReq, HTTSS7ISUP_StatusReq etc.

SS7 74 January 2001

SS7IsupMsg Functions

• The Hammer SS7 message (SS7IsupMsg) is used to send and receive Hammer SS7 messages through the SS7 links

• The following functions have been defined on the Hammer SS7 message (SS7IsupMsg)

initSS7IsupMsg

buildSetupRQ

buildConnRS

buildReleaseRS

Get

GetMsgType

Set

SetMsgType

GetCode

sendSS7IsupMsg

getSS7IsupMsg

buildBlockRQ

buildBlockRS

buildUnblockRQ

buildUnblockRS

buildResetRQ

To see more about the functions click:

Help -> Hammer SS7 -> Find -> Type in SS7IsupMsg.

SS7 75 January 2001

Exercise 4

• Create new scripts to send/receive a voice message

• Use high-level programming

Open a new script by double-clicking on the script icon.

Use the toolbar to edit the template script:

Start protocol, SS7

Place a call (enter dialed #) Receive call (set timeout to -1)

Receive DTMF Send DTMF (enter digits e.g. 123)

Pause 5, HT_SECONDS Play a prompt (e.g. “Hello”)

Play a prompt (e.g. “Goodbye”) Pause 5, HT_SECONDS

Pause 5, HT_SECONDS

Release the call Release the call

Stop protocol

Compile the scripts. Run the scripts on a channel (e.g. 7).

Click on the Default View icon to monitor the procedure.

SS7 76 January 2001

SS7 Parameters

To see the SS7 parameters dialog open a new script.

1. Click Commands -> Parameters -> SS7

There are four tabs for Initial Address Message, IAM, and Address Complete Message, ACM, for ANSI and ITU standard.

Parameter names for SS7 ANSI IAM set should start with the prefix AI_.

From the fields in the dialog you can select various values for IAM and ACM message parameters.

The parameters which are not encompassed by the dialog box you have to type the values for in your scripts.

SS7 77 January 2001

Exercise 5

• Create scripts to place/(wait for) an infinite number of calls, receive/play prompt, and send/receive DTMF digits

• Use high-level programming

• Change the default SS7 parameters

Open a new script to place call.

1. Click Commands -> Parameters ->SS7. In the Param Name: field type in AI_SS7P

2. Click Ani/OrigCg Num/Change Num tab

3. In the Calling Party Number section:

- click the arrow at the nature of addr: field -> select NATNUM

- click the arrow at the numbering plan field -> select NP_ISDN

- click the arrow at the num incomplete field -> select NBMCMLTE

- type 7081234567 in the addr signal: field

4. After ’* HAMMER END PARAM DEFINITIONS add

dim connReq as SS7IsupMsg ’* SS7 connection request message

dim myEvent as TelEvent

dim myACM as SS7IsupMsg

dim chargeInfo as integer

dim count as integer

5.logMsg "start SS7 protocol..."

call startProtocol (HT_PROTO_SS7,,)

6.count = 0

while (1)

continue

SS7 78 January 2001

7. logMsg "=> Placing call to 7081234567"

set event = placeCall ("7081234567", AI_SS7P)

eventType = event.type()

if eventType <> HTEVT_CALL_CONNECTED then goto TelError

8. logMsg "check ACM message..."

set myEvent = getCallEvent(HTCALL_FIRST_RING)

myEvent.getSS7IsupMsg myACM

myACM.Get HTSS7ISUP_ConnectStatusReq, HTSS7PARM_bckCallInd,_

HTSS7PARM_chrgInd, chargeInfo

logMsg "charge info is " +CStr(chargeInfo)

9. pause 2,HT_SECONDS

10. logMsg "=> Sending DTMF digits 54321"

set event = sendDtmf("54321", )


if eventType <> HTEVT_TONES_DONE then goto TelError

11. logMsg "Now - release the call", HT_LOG_DEBUG

set event = releaseCall()


if eventType <> HTEVT_CALL_RELEASED then goto TelError

logMsg "=> Call released.”

12. count = count +1

logMsg “==== call # “ +CStr(count) + “finished”

13. logMsg "stop protocol..."

stopProtocol

SS7 79 January 2001

Exercise 5 - Answer Call Script

1. Open a new script to wait for call.

2. Click Commands -> Parameters -> CAS3. In the Param Name: field type in colP

After ’* HAMMER END PARAM DEFINITIONS add:

4. dim count as integerdim myACM as SS7IsupMsg ’* my SS7 ACM messagedim connReq as SS7IsupMsg ’* connection request from the other sidedim callerID as string

5. count = 06. logMsg "start SS7 protocol...", HT_LOG_DEBUG

call startProtocol (HT_PROTO_SS7,,)7. while (1)

8. logMsg "=> Waiting for incoming call...", HT_LOG_DEBUG

set event = waitForCall(HT_INFINITE)


if eventType <> HTEVT_INCOMING_CALL then goto TelError

9. logMsg "Call arrived. Check caller ID...", HT_LOG_FAIL

event.getSS7IsupMsg connReq

connReq.Get HTSS7ISUP_ConnectReq, HTSS7PARM_cdPtyNum,_

HTSS7PARM_addrSig, callerID

logMsg "called number is " + callerID, HT_LOG_FAIL

connReq.Get HTSS7ISUP_ConnectReq, HTSS7PARM_cgPtyNum, _

HTSS7PARM_addrSig, callerID

logMsg "caller ID is " + callerID, HT_LOG_FAIL

10. logMsg "prepare ACM message, set it to be charged call...", HT_LOG_DEBUG

myACM.initSS7IsupMsg HTSS7ISUP_AddrCompleted

myACM.Set HTSS7ISUP_ConnectStatusReq, HTSS7PARM_bckCallInd, _

HTSS7PARM_chrgInd, HT_SS7_CHRG_CHRG

continue

SS7 80 January 2001

11. logMsg " answer incoming call.", HT_LOG_DEBUG

set event = answerCall(1,myACM)


if eventType <> HTEVT_CALL_CONNECTED then goto TelError

12. logMsg "=> Playing ex1Prompt003", HT_LOG_DEBUG

set event = playPrompt("ex1Prompt003", HT_ENCODE_NMS_24, 10000, )


if eventType <> HTEVT_PLAY_DONE then goto TelError

13. logMsg "=> Waiting for DTMF digits.", HT_LOG_DEBUG

set event = receiveDTMF (colP, 5,recDigits)


if eventType <> HTEVT_COLLECTION_DONE then goto TelError

if event.value() <> HT_REASON_FINISHED then goto TelError

logMsg "Received digits " + recDigits, HT_LOG_DEBUG

15. set event = waitForDisconnect

16. logMsg "Releasing call.", HT_LOG_DEBUG

set event = releaseCall()


if eventType <> HTEVT_CALL_RELEASED then goto TelError

17. count = count + 1

logMsg "===== call # " +CStr(count)+" finished"

18. Wend

19. logMsg "stop SS7 protocol...", HT_LOG_DEBUG

stopProtocol

SS7 81 January 2001

Exercise 6

• Create scripts to place/(wait for) 100 calls, play a prompt and then release the call

• Use low-level programming

• To get information on the functions you are going to use in the scripts, right-click each function name in your script

For the place call side open a new script:

1. After ‘*HAMMER END DIM AREA add

dim msgBuffer as SS7IsupMsg '* SS7 message buffer

dim done as integer

dim SS7MsgCode as integer '* type of SS7 message received

dim count as integer

2. After ‘*HAMMER END PARAM DEFINITIONS add

3.logMsg "start CCS protocol..."

call startProtocol (HT_PROTO_CCS,,)

4.count = 0

5.while count < 100

6.logMsg "prepare SS7 setup message..."

msgBuffer.initSS7IsupMsg HTSS7ISUP_ConnectReq

msgBuffer.buildSetupRQ "7081234567"

7.logMsg "send SS7 connection request message..."

sendSS7IsupMessage msgBuffer

Continue

SS7 82 January 2001

8. logMsg "wait for connection response..."

done = 0

while (done <> 1)

set event = getnextevent(HT_INFINITE)

eventType = event.Type()

9. if eventType = HTEVT_SS7ISUP_MSG then

event.getSS7IsupMsg msgBuffer

SS7MsgCode = msgBuffer.getCode

if SS7MsgCode = HT_SS7_EVTSITCONCFM then ’* connection confirm

logMsg "=> get connection confirm"

done = 1

end if

end if

wend

logMsg "We are now connected..."

10. logMsg "=> Playing GoodBye", HT_LOG_DEBUG

set event = playPrompt("GoodBye", HT_ENCODE_NMS_24, 10000, )


if eventType <> HTEVT_PLAY_DONE then goto TelError

Continue

SS7 83 January 2001

11. logMsg "prepare release request..."

msgBuffer.initSS7IsupMsg HTSS7ISUP_ReleaseReq

12. logMsg "send SS7 release request..."

sendSS7IsupMessage msgBuffer

13. logMsg "wait for release confirm...”

done = 0

while (done <> 1)



if eventType = HTEVT_SS7ISUP_MSG then



if SS7MsgCode = HT_SS7_EVTSITRELCFM then '* release confirm

logMsg "=> get release confirm"

done = 1

end if

end if

wend

14. count = count + 1

15. logMsg "=== Call # " +Cstr(count)

16. Wend

17. stopProtocol

SS7 84 January 2001

Exercise 6 - Answer Call Script

Open a new script:

1. After ’* HAMMER END PARAM DEFINITIONS add

dim msgBuffer as SS7IsupMsg ’* SS7 message buffer (msg. bfr)dim addrMsg as SS7IsupMsg ’* SS7 address complete msg. bfr.dim conMsg as SS7IsupMsg ’* SS7 connection confirm msg.dim relMsg as SS7IsupMsg ’* SS7 release response messagedim done as integerdim SS7MsgCode as integer ’* type of SS7 message receiveddim count as integer

2. logMsg "start CCS protocol..."

call startProtocol (HT_PROTO_CCS,,)

3. count = 0

4. while < 100

logMsg "waiting for incoming calls..."

done = 0

5. while (done <> 1)






if SS7MsgCode = HT_SS7_EVTSITCONIND then ’* connection indication

logMsg "=> get connection indication"

done = 1

end if

end if

wend

continue

SS7 85 January 2001

6.logMsg "Get incoming call..."

logMsg "prepare address complete message..."

addrMsg.initSS7IsupMsg HTSS7ISUP_AddrCompleted

logMsg "send SS7 address complete message..."

sendSS7IsupMessage addrMsg

logMsg "prepare connection confirm message..."

conMsg.buildConnRS msgBuffer

logMsg "send SS7 connection confirm message..."

sendSS7IsupMessage conMsg

7.logMsg "wait for hang up...”

done = 0

while (done <> 1)






if SS7MsgCode = HT_SS7_EVTSITRELIND then '* release indication

logMsg "=> get release indication"

done = 1

end if

end if

wend

8.logMsg "prepare release response message..."

relMsg.buildReleaseRS msgBuffer

logMsg "send release response..."

sendSS7IsupMessage relMsg

count = count +1

logMsg "====Call #" +CStr(count)

wend

stopProtocol

SS7 86 January 2001

Hammer SUTLoad board driverTelephony

LoaderSetup MVIP switchingLink alignmentLink in serviceMTP Resume to ISUP

Start Hammer

Hammer is upBLO cic(1)

BLO cic(n)

BLA cic(1)

BLA cic(n)

Hammer-SUT Communication

SUT - System Under Test

In the SS7 environment on the Hammer the circuits are blocked before and/or after communication because there are no scripts running.

To prevent SUT placing a call to Hammer, the circuits are blocked.

BLO cic(1) - Blocked circuit 1

BLA cic(1) - Block acknowledged for circuit 1.

SS7 87 January 2001

Callingparty

Called partyUBL

UBA

UBL

UBA

IAM

ACM

ANM

Voice

Called partyRELRLC

RSC

BLO

RLC

BLA

RSC

Callingparty

Cir

cuit

man

agem

ent

Startprotocol

Cal

l set

up

Startprotocol

BLO

BLORLC

BLA

BLA

Rel

ease

cal

l

Cir

cuit

man

agem

ent

Rel

ease

cal

l

Calling-Called Party Messages

The message exchange between the Hammer and SUT (calling and called party) is illustrated in the slide.

UBL - unblock

UBA - unblock acknowledged

IAM - initial address message

ACM - address complete

ANM - answer

REL - release

RLC - release complete

RSC - reset circuit

The SS7 and CCS protocols send the UBL and UBA messages automatically. The NOCC protocol doesn’t send these messages and users have to include them in their scripts.

SS7 88 January 2001

HammerSS7 Toolbars

The purpose of the SS7 Toolbars is to simplify Hammer low level SS7 scripting. These toolbars allow a user to develop a SS7 script using ISUP signaling to place and receive calls.

1. Open a new script and name it, e.g., icons_SS7.

2. In the main menu click Toolbars -> SS7 Management and SS7 Call Control

3. The SS7 Management and SS7 Call Control Toolbars are displayed.

4. Click on each of the toolbars to see the code lines inserted in your script.

Do not compile this script, since you are not going to run it, we need it only to see the lines of code behind each of the SS7 icons.

SS7 89 January 2001

Insert SS7 Include FilesSend IAMReceive IAMSend ACMReceive ACMSend CPGReceive CPGSend ANM

Receive ANMSend RELReceive RELSend RLCReceive RLC

SS7 Call Control Toolbar

Insert SS7 Include Files – Inserts the two include files.

Send IAM – Sends a default Initial Address Message with no extra parameters. NOTE: Called Party must be set.

Receive IAM – Receives an Initial Address Message, and stores it in recSs7MsgBuf.

Send ACM – Sends an Address Complete Message with Backwards Call Indicators (required).

Receive ACM – Receives an Address Complete Message and stores it in recSs7MsgBuf.

Send CPG – Sends Call Progress Message.

Receive CPG – Receives Call Progress Message and stores it in recSs7MsgBuf.

Send ANM – Sends an Answer Message based on the received recSs7MsgBuf.

Receive ANM – Receives an Answer Message and stores it in recSs7MsgBuf.

Send REL – Sends a Release Message.

Receive REL – Receives a Release Message and stores it in recSs7MsgBuf.

Send RLC – Sends a Release Complete based on the received recSs7MsgBuf.

Receive RLC – Receives a Release Complete and stores it in recSs7MsgBuf.

SS7 90 January 2001

Insert SS7 Include FilesSend BLOReceive BLASend UBLReceive UBASend RSCReceive RLCSend GRSSend CGUSend CGUAReceive CGUA

SS7 Maintenance Toolbars

Insert SS7 Include Files – Inserts the two include files.

Send BLO – Send a Block message.

Receive BLA – Receive Block Acknowledgement message.

Send UBL – Send a Unblock message.

Receive UBA – Receive Unblock Acknowledgement message.

Send RSC – Send a Reset Circuit message.

Receive RLC – Receive Release Complete message.

Send GRS – Send Group Reset message

Send CGU – Send Circuit Group Unblock message

Send CGUA – Send Circuit Group Unblock Acknowledgement message.

Receive CGUA – Receive Circuit Group Unblock Acknowledgement message.

SS7 91 January 2001

• '$Include "HT_SS7Functions.sbl” containsReceiveSS7ISUPMessage( Timeout, Expected

Message, Receive Buffer)

• '$Include "HT_SS7Globals.sbl” contains Global parameters required by the HmrSS7Func.sbl script: SS7MsgBuffer and incSS7MsgBuf which are both of type SS7IsupMsg

SS7 Include Files Toolbar

ReceiveSS7ISUPMessage is a function used by both SS7 toolbars to wait for a particular SS7 ISUP message. The syntax used for this function is:

ReceiveSS7ISUPMessage( Timeout, Expected Message, Receive Buffer)

Timeout - the amount of time in seconds before the function times out. The SS7 Toolbars use a default timeout of 5 seconds, which can be changed by manually editing this field in the script.

Expected Message - the SS7 acronym for the message the Hammer is waiting for. This can be one of the following: ACM, ANM, BLO, BLA, CGB, CGBA, CQM, CQR, GRS, GRA, CGU, CGUA, IAM, REL, RLC, RSC, RES, SUS, UBL, and UBA.

Receive Buffer - the SS7IsupMsg object that the receive message will be stored in. The SS7 Call Control Toolbars default to recSS7MsgBuf. WARNING: Do not change the receive parameter as some other toolbar items will use these receive buffers in creating outgoing messages.

NOTE: When running this function, if other SS7 ISUP messages are received by the Hammer while waiting for an expected message, the type of ISUP message will be displayed, but the Hammer will continue to wait for the message it was expecting until timeout occurs or the message arrives. This can be handled by creating error handling within the script.

When the function executes the following messages may be displayed in the default view multiple times:

‘getNextEvent:not completed in time’ and ‘getNextEvent:completed successfully’

These messages do not indicate that the function has failed or succeeded, but are function calls within the ReceiveSS7ISUPMessage Function. Disregard these messages.

SS7 92 January 2001

• Create a script to place a call, send DTMF, and play a prompt

• Use the NOCC protocol

Exercise 7

1. Create two new scripts - one for the originating call, one for the terminating call.

2. Turn on SS7 Management and SS7 Call Control toolbars.

3. Using the toolbars create your SS7 scripts.

Continue

SS7 93 January 2001

Originate Call Script

1. Move cursor to a position after HAMMER END INCLUDE AREA and click on ‘SS7’ button

2. Move cursor to script insertion area (after HAMMER END PARAMETER DEFINITION)

3. Select the StartProtocol icon with NOCC (No Call Control) Protocol

4. Select Send UBL.

5. Select Receive UBA.

6. Select Send IAM.

7. Add the following Parameter line to the IAM to deal with Called Party Number:

HTSS7PARM_cdPtyNum, HTSS7PARM_addrSig, “5551212”

8. Select Receive ACM.

9. Select Receive ANM.

Bearer (voice) Channel Available for use.

Click the Hammer Send DTMF icon

Click the Hammer Play Prompt icon

10. Select Receive REL

11. Select Send RLC

12. Select Send BLO

13. Select Receive BLA

14. Select the StopProtocol icon

Placecall

Wait fordisconnect

Call connectedstate

SS7 94 January 2001

Terminate Call Script

1. Move cursor to a position after HAMMER END INCLUDE AREA and click on ‘SS7’ button

2. Move cursor to script insertion area (after HAMMER END PARAMETER DEFINITION)

3. Select the StartProtocol icon with NOCC (No Call Control) Protocol

4. Select Send UBL.

5. Select Receive UBA.

6. Select Receive IAM.

7. Select Send ACM

8. Select Send ANM.

Bearer (voice) Channel Available for use.

Click the Hammer Receive DTMF icon

Pause 2, HT_SECONDS

9. Select Send REL

10. Select Receive RLC

11. Select Send BLO

13. Select Receive BLA

14. Select the StopProtocol icon

Wait forcall

Call connectedstate

Releasecall

SS7 95 January 2001

’******************************************************************

’* FileName: tbGen_OriginateCall.sbl

’*

’* Version: 1.0

’*

’* Description: Toolbar Generated Originate Call Script

’*

’******************************************************************

’******************************************************************

’ The areas between HAMMER BEGIN... and

’ HAMMER END... are used by the enhanced editor.

’ Do NOT edit in these areas.

’******************************************************************

’* HAMMER BEGIN INCLUDE AREA

’* HAMMER END INCLUDE AREA

’$Include "HmrSs7Func.sbl"

’$Include "HmrSs7Global.sbl"

’* HAMMER BEGIN DIM AREA

’* (Do not edit in this area)

...

sub main

...

’* HAMMER BEGIN PARAM DEFINITIONS

’* HAMMER END PARAM DEFINITIONS

Call StartProtocol(HT_PROTO_NOCC,,)

Continue

SS7 96 January 2001

logMsg "****** SEND UNBLOCKING MESSAGE ******", HT_LOG_NORMAL

Ss7MsgBuffer.initSS7IsupMsg HTSS7ISUP_StatusReq

Ss7MsgBuffer.Set HTSS7ISUP_StatusReq, HTSS7PARM_evntType, _

HTSS7PARM_evntType, HT_SS7_CIRUNBLKREQ

logMsg "********* Sending UBL message", HT_LOG_DEBUG

sendSS7IsupMessage(Ss7MsgBuffer)

logMsg "*** WAIT FOR UNBLOCKING ACKNOWLEDGEMENT MSG", HT_LOG_NORMAL

Ss7Status = receiveSS7ISUPMessage(5, "UBA", Ss7MsgBuffer)

if Ss7Status <> HT_SUCCESS then goto TelError

logMsg "****** SEND INITIAL ADDRESS MESSAGE ******", HT_LOG_NORMAL

Ss7MsgBuffer.initSS7IsupMsg HTSS7ISUP_ConnectReq

’Use following Set Method to change IAM Parameters & Sub Parameters

’ Ss7MsgBuffer.Set HTSS7ISUP_ConnectReq, HTSS7PARM_ParmName,

HTSS7PARM_SubParmName, HT_SS7_Value

Ss7MsgBuffer.Set HTSS7ISUP_ConnectReq, HTSS7PARM_cdPtyNum,_

HTSS7PARM_addrSig, HT_SS7_Value

logMsg " => Sending IAM message", HT_LOG_DEBUG


logMsg "****** WAIT FOR ADDRESS COMPLETE MESSAGE", HT_LOG_NORMAL

Ss7Status = receiveSS7ISUPMessage(5, "ACM", recSs7MsgBuf)


logMsg " => Received ACM Message", HT_LOG_DEBUG

logMsg "****** WAIT FOR ANSWER MESSAGE ******", HT_LOG_NORMAL

Ss7Status = receiveSS7ISUPMessage(5, "ANM", recSs7MsgBuf)


logMsg " => Received ANM Message", HT_LOG_DEBUG

logMsg "BEARER CHANNEL UP.........", HT_LOG_NORMAL

Continue

SS7 97 January 2001

logMsg "****** WAIT FOR RELEASE MESSAGE ******", HT_LOG_NORMAL

Ss7Status = receiveSS7ISUPMessage(5, "REL", recSs7MsgBuf)

‘* Timeout is 5 seconds, but this can be changed manually


logMsg " => Received REL Message", HT_LOG_DEBUG

logMsg "***** SEND RELEASE COMPLETE MESSAGE *****", HT_LOG_NORMAL

Ss7MsgBuffer.buildReleaseRS recSs7MsgBuf

'Use following Set Method to change RLC Parameters&Sub Parameters

' Ss7MsgBuffer.Set HTSS7ISUP_ReleaseResp, HTSS7PARM_ParmName, _


logMsg " => Sending RLC message", HT_LOG_DEBUG


logMsg "***** SEND CIRCUIT BLOCKING MESSAGE ******", HT_LOG_NORMAL



HTSS7PARM_evntType, HT_SS7_CIRBLKREQ

logMsg "********* Sending BLO message", HT_LOG_DEBUG


logMsg "*** WAIT FOR BLOCKING ACKNOWLEDGEMENT MSG", HT_LOG_NORMAL

Ss7Status = receiveSS7ISUPMessage(5, "BLA", Ss7MsgBuffer)


StopProtocol

setScriptResult HT_SUCCESS

goto done

TelError:

setScriptResult HT_FAILURE

...

SS7 98 January 2001

’******************************************************************

’* FileName: tbGen_TerminateCall.sbl

’*

’* Version: 1.0

’*

’* Description: Toolbar Generated Terminate Call Script

’*

’******************************************************************

’******************************************************************

’ The areas between HAMMER BEGIN... and

’ HAMMER END... are used by the enhanced editor.

’ Do NOT edit in these areas.

’******************************************************************

’* HAMMER BEGIN INCLUDE AREA

’* HAMMER END INCLUDE AREA

’$Include "HmrSs7Func.sbl"

’$Include "HmrSs7Global.sbl"

’* HAMMER BEGIN DIM AREA

’* (Do not edit in this area)

...

sub main

...

Call StartProtocol (HT_PROTO_NOCC,,)

logMsg "****** SEND UNBLOCKING MESSAGE ******", HT_LOG_NORMAL



HTSS7PARM_evntType, HT_SS7_CIRUNBLKREQ

logMsg "********* Sending UBL message", HT_LOG_DEBUG


Continue

SS7 99 January 2001

logMsg "*** WAIT FOR UNBLOCKING ACKNOWLEDGEMENT MSG",HT_LOG_NORMAL

Ss7Status = receiveSS7ISUPMessage(5, "UBA", Ss7MsgBuffer)


logMsg "****** WAIT FOR INITIAL ADDRESS MESSAGE",HT_LOG_NORMAL

Ss7Status = receiveSS7ISUPMessage(5, "IAM", recSs7MsgBuf)


logMsg " => Received IAM Message", HT_LOG_DEBUG

logMsg "****** SEND ADDRESS COMPLETE MESSAGE", HT_LOG_NORMAL

Ss7MsgBuffer.initSS7IsupMsg HTSS7ISUP_ConnectStatusReq

Ss7MsgBuffer.Set HTSS7ISUP_ConnectStatusReq, _

HTSS7PARM_evntType, HTSS7PARM_evntType, HT_SS7_ADDRCMPLT

’Use following Set Method to change ACM Parameters&Sub Parameters

’ Ss7MsgBuffer.Set HTSS7ISUP_ConnectStatusReq, HTSS7PARM_ParmName,_


Ss7MsgBuffer.Set HTSS7ISUP_ConnectStatusReq, HTSS7PARM_bckCallInd,_

HTSS7PARM_cadPtyCatInd, HT_SS7_CADCAT_ORDSUBS


HTSS7PARM_cadPtyStatInd, HT_SS7_CADSTAT_NOIND


HTSS7PARM_chrgInd, HT_SS7_CHRG_NOIND


HTSS7PARM_echoCtrlDevInd, HT_SS7_ECHOCDEV_NOTINCL


HTSS7PARM_end2EndInfoInd, HT_SS7_E2EINF_NOINFO


HTSS7PARM_end2EndMethInd, HT_SS7_E2EMTH_NOMETH


HTSS7PARM_holdInd, HT_SS7_HOLD_NOTREQD


HTSS7PARM_intInd, HT_SS7_INTIND_NOINTW


HTSS7PARM_isdnAccInd, HT_SS7_ISDNACC_ISDN

Continue

SS7 100 January 2001

Ss7MsgBuffer.Set HTSS7ISUP_ConnectStatusReq, HTSS7PARM_bckCallInd, _

HTSS7PARM_isdnUsrPrtInd, HT_SS7_ISUP_USED

Ss7MsgBuffer.Set HTSS7ISUP_ConnectStatusReq, HTSS7PARM_bckCallInd, _

HTSS7PARM_sccpMethInd, HT_SS7_SCCPMTH_NOIND

logMsg " => Sending ACM message", HT_LOG_DEBUG


logMsg "****** SEND ANSWER MESSAGE ******", HT_LOG_NORMAL

Ss7MsgBuffer.buildConnRS recSs7MsgBuf

’Use following Set Method to change ANM Parameters& Sub Parameters

’ Ss7MsgBuffer.Set HTSS7ISUP_ConnectResp, HTSS7PARM_ParmName, _


logMsg " => Sending ANM message", HT_LOG_DEBUG


logMsg "BEARER CHANNEL UP...........", HT_LOG_NORMAL

logMsg "****** SEND RELEASE MESSAGE ******", HT_LOG_NORMAL

Ss7MsgBuffer.initSS7IsupMsg HTSS7ISUP_ReleaseReq

’Use following Set Method to change IAM Parameters& Sub Parameters

’ Ss7MsgBuffer.Set HTSS7ISUP_ReleaseReq, HTSS7PARM_ParmName, _


logMsg " => Sending REL message", HT_LOG_DEBUG


logMsg "****** WAIT FOR RELEASE COMPLETE MESSAGE", HT_LOG_NORMAL

Ss7Status = receiveSS7ISUPMessage(5, "RLC", recSs7MsgBuf)


logMsg " => Received RLC Message", HT_LOG_DEBUG

Continue

SS7 101 January 2001

logMsg "****** SEND CIRCUIT BLOCKING MESSAGE", HT_LOG_NORMAL


Ss7MsgBuffer.Set HTSS7ISUP_StatusReq, HTSS7PARM_evntType,_

HTSS7PARM_evntType, HT_SS7_CIRBLKREQ

logMsg "********* Sending BLO message", HT_LOG_DEBUG


logMsg "*** WAIT FOR BLOCKING ACKNOWLEDGEMENT MSG", HT_LOG_NORMAL

Ss7Status = receiveSS7ISUPMessage(5, "BLA", Ss7MsgBuffer)


StopProtocol

setScriptResult HT_SUCCESS

goto done

TelError:

setScriptResult HT_FAILURE

...

Documents

E-Book - SS7 Tutorial