SS7 Quick Start Guide - Solacom

EdgeIQ R11.0

SS7 Quick Start Guide

The information furnished in this document by Solacom Technologies Inc. ("Solacom") is believed to be accurate. Solacom makes no warranties, expressed or implied, regarding the information contained herein, and assumes no liability for errors or omissions.

Solacom assumes no liability otherwise arising from the application or use of any such information or product for any infringement of patents or other intellectual property rights owned by others that may result from such application or use.

Neither the supply of this information or the purchase of product conveys any license, either expressed or implied, under patents or other intellectual property rights owned by Solacom or licensed from third parties by Solacom, whatsoever.

Purchasers of product are also hereby notified that the use of this information or product in certain ways or in combination with Solacom or non-Solacom furnished goods or services may infringe patents or other intellectual property rights.

This document and related products contain valuable trade secrets and proprietary information belonging to Solacom. No part of this document may be reproduced, stored in a retrieval system, or transmitted in any form or by any means without prior written permission from Solacom. Reverse engineering, decompiling and disassembling are explicitly prohibited.

The product specifications and information contained in this document are subject to change by Solacom without notice.

i

Solacom Services Team

Our Customer System Support & Services Centre is staffed by qualified Solacom service

professionals. We provide the support, service, and know-how you need to seamlessly

operate and manage your mission-critical communications infrastructure.

Our support team is available to:

answer queries and provide information

help diagnose and troubleshoot incidents

dispatch qualified personnel for field support, including:

training, installation, configuration, QoS audits, personalized requirements,

and more.

We offer a complete range of services to support you and your system.

You may request support online or by phone:

Web: services.solacom.com

Email: [email protected]

North America toll free: 1-888-Solacom (1-888-765-2266)

Phone anywhere: +1 613 693 0641

Our normal business hours are Monday to Friday from 09:00 to 17:00 ET.

For emergency or urgent requests, 7 days per week, 24 hours per day, use the phone

numbers above and follow the voice prompts.

http://services.solacom.com/

mailto:[email protected]

iii

Safety Summary

The following general safety precautions must be observed during all phases of operation,

service and repair of this product. Failure to comply with these precautions or with specific

warnings elsewhere in this manual violates safety standards of design, manufacture and

intended use of the product. Solacom assumes no liability for the customer’s failure to

comply with these requirements.

Ground the equipment

To minimize shock hazard, the equipment switch must be connected to an electrical

ground. The equipment has a three-conductor AC power cable. This power cable

must be plugged into an approved three-contact electrical outlet with the grounding

wire (green) firmly connected to an electrical ground at the power outlet. The power

cables meet International Electrotechnical Commission (IEC) safety standards.

Keep away from live circuits

Operating personnel must not remove modules or otherwise tamper with the

equipment switch or related components. Component replacement and internal

adjustments must be made by qualified maintenance personnel. Do not replace

components with the power cable connected. To avoid injuries, always disconnect

power and discharge circuits before removing equipment shelves or making major

modifications.

iv

Do not service or adjust alone

Do not attempt major component replacement, internal service or adjustment unless

another person, capable of rendering first aid and resuscitation, is present.

Replacement of modules

Replacement of modules should be performed by qualified maintenance personnel.

(Those who have been trained and certified by Solacom.)

Electrostatic discharge (ESD)

This product contains components that can be damaged by electrostatic discharge.

You must take precautions when handling modules. As a minimum precaution, use

grounded wrist straps at all times when handling modules.

Do not modify the product

Do not install, substitute parts or modify the product. Contact an authorized Sales

and Service Office for service and repair to ensure that product integrity is

maintained:

Solacom Technologies Inc.

84 Jean-Proulx

Gatineau, QC J8Z 1W1

Canada

Tel: 613-693-0641

Fax: 613-693-0642

Power surge advisory

Electrical surges (typically lightning transients) are very destructive to customer

terminal equipment connected to AC power sources. We recommend that the

customer install an AC surge arrestor in the AC outlet to which the equipment is

connected.

v

Contents

1 About This Document .................................................................................................... 1

1.1 References .................................................................................................................. 1

2 Introduction .................................................................................................................... 3

2.1 What is SS7? .............................................................................................................. 3

2.2 SS7 Stack (MTP1/MTP2) .......................................................................................... 5

2.3 SS7 Stack (MTP3/ISUP) ............................................................................................ 5

2.4 Solacom’s SS7 SIL and VSOS ................................................................................... 6

2.5 SSP and STP Support ................................................................................................. 6

2.6 Bearer Channel Level Maintenance ........................................................................... 6

2.7 Configuration ............................................................................................................. 7

2.8 SS7 Duplication ......................................................................................................... 7

3 Getting Started with SS7 ............................................................................................... 9

3.1 Reviewing the Factory Configuration ........................................................................ 9

3.2 Connecting the SS7 Module to the Network............................................................ 11

3.3 Viewing the Mesoware.ini Configuration ................................................................ 11

3.4 Configuring SS7 using the IQadmin ........................................................................ 13

3.4.1 SS7 Trunk Group Configuration ........................................................................ 16

3.4.2 Channel-based Trunk Group Configuration ....................................................... 18

3.5 Launching the MML Interface ................................................................................. 21

3.5.1 Viewing the SS7 Stack Configuration ............................................................... 22

3.5.2 Viewing the Default SS7 Module Configuration ............................................... 23

vi

3.5.3 Changing the Default SS7 Module Configuration .............................................. 24

3.6 Configuring the SS7 Links and Routes .................................................................... 26

3.7 The SS7 Processes .................................................................................................... 30

3.7.1 Verifying the Status of SS7 Processes ................................................................ 32

4 SS7 Procedures ............................................................................................................. 37

4.1 Adding a New Remote Destination .......................................................................... 37

5 Troubleshooting ............................................................................................................ 39

5.1 Viewing the SS7 Command Log File ....................................................................... 39

5.2 Viewing the SS7 Command History Log File .......................................................... 40

5.3 Viewing the SS7 Master Event Log Files ................................................................ 40

5.4 Viewing the SS7 Alarm Files ................................................................................... 41

5.5 Generating SS7 Event Reports ................................................................................. 43

5.6 Generating SS7 Alarm Reports ................................................................................ 43

5.7 Viewing the Log Files .............................................................................................. 44

A List of Acronyms ........................................................................................................... 45

B Level 2 Tracing SS7 ...................................................................................................... 47

1.1 Tracing SS7 – Using L2TOOL ................................................................................. 47

1.2 Automated Decoding SS7 using Wireshark ............................................................. 50

vii

Figures

Figure 1: Software Architecture and OS Compatibility ........................................................... 5

Figure 2: SS7 Duplication ........................................................................................................ 8

Figure 3: SS7 Module ............................................................................................................... 9

Figure 4: Processor Cards ....................................................................................................... 10

Figure 5: Network Connection ............................................................................................... 11

Figure 6: Mesoware.ini Configuration ................................................................................... 12

Figure 7: Default MML Prompt ............................................................................................. 21

Figure 8: MML Display Commands ....................................................................................... 22

Figure 9: The MML Help Menu ............................................................................................. 24

Figure 10: Help for modify-port Command ............................................................................ 26

Figure 11: Sample Network Configuration ............................................................................ 27

Figure 12: Network Connections with MML Commands ...................................................... 29

Figure 13: SS7 Command Log Sample................................................................................... 40

Figure 14: SS7 Command History Log Sample...................................................................... 40

Figure 15: SS7 Master Event Log Sample .............................................................................. 41

Figure 16: SS7 Master Alarm Sample .................................................................................... 42

Figure 17: Sample Log ........................................................................................................... 44

Figure 18: Windows Script Host ............................................................................................ 50


ix

Tables

Table 1: MTP Level to Layer Mapping .................................................................................... 4

Table 2: SS7 Module Side A Default Parameters .................................................................. 23

Table 3: SS7 Module Side B Default Parameters ................................................................... 23

Table 4: apm_report Command Options ................................................................................ 43

Table 5: ebs_report Command Options .................................................................................. 43


1

1 About This Document

This document provides the necessary information to install, configure, and use SS7 as the

PSTN signaling system.

1.1 References

Some common industry acronyms are used throughout this document. For reference,

Appendix A contains a list of the acronyms used and their expanded form.

Other documents in the SS7 solution include the following:

EdgeIQ Configuration Guide

EdgeIQ Configuration Reference

Managed API Reference

OAMP Reference

SS8 Distributed7 User Manual (NewNet D7 User Guide)

Release Notes

Documents are stored on the Administration server in the

―I:\Documents\OEM\SS7_Board‖ folder.


3

2 Introduction

This section introduces SS7, the SS7 stack, and Solacom’s SS7 SIL and VSOS.

2.1 What is SS7?

Common Channel Signaling System No. 7 (SS7) is a global ITU standard that

defines the procedures and protocols by which network elements exchange call

information in the Public Switched Telephone Network (PSTN). The SS7 network is

an out-of-band digital overlay network using 56/64 kbps DS0 channels for relaying

message units.

SS7 network and protocol are used for:

basic call setup, management, and tear down

wireless services such as personal communications services (PCS), wireless

roaming, and mobile subscriber authentication

local number portability (LNP)

toll-free (800/888) and toll (900) wireline services

enhanced call features such as call forwarding, calling party name/number

display, and three-way calling

efficient and secure worldwide telecommunications

The Solacom SS7 Solution consists of SS7 signaling software and an SS7 module.

The signaling software integrates all layers of the SS7 protocol stack and the

Solacom SS7 SIL. The SIL translates messages for the Solacom switch operating

system (VSOS) and provides a seamless interface to the Solacom application

interface known as the Managed API.

Introduction

4

The SS7 Solution provides connectionless, UNIX stream-based interprocess

communications between EdgeIQ nodes and the PSTN. Control of the SS7 solution

is provided by the telephony application via the Managed API.

The SS7 implementation consists of basic call setup and maintenance following the

ANSI T1-113.1 standard (ISDN), ANSI T1-113.4 standard (TCAP), and ITU Q761

to ITU Q767. ISUP call control command, information elements (IEs), and

management functionality are supported.

The SS7 stack (MTP1/MTP2/MTP3/ISUP) is a third party offering. The hardware

and software functions of the SS7 protocol are categorized into levels that map to the

Open Systems Interconnect (OSI) 7-layer model defined by the International

Standards Organization (ISO). The association is shown below:

MTP Level OSI Layer

1 Physical layer (physical/electrical/functional)

2 Data link layer (end-to-end transmission)

3 Network layer (message routing over SS7

nodes)

Table 1: MTP Level to Layer Mapping

The ISDN User Part (ISUP) defines the protocol and procedures used to set up,

manage, and release trunk circuits that carry voice and data calls over the PSTN.

Software architecture and operating system compatibility is shown on the following

diagram:


5

Figure 1: Software Architecture and OS Compatibility

2.2 SS7 Stack (MTP1/MTP2)

An SS7 module installed on the processor card handles the electrical and mechanical

characteristics of the SS7 data transmission and reception required by MTP Level 1.

The SS7 module has its own processor and memory for running MTP Level 2

signaling software. The SS7 module supports two 24-channel T1 Interfaces and

communicates with MTP3/ISUP running on the processor card.

2.3 SS7 Stack (MTP3/ISUP)

The SS7 MTP3/ISUP Stack has several different UNIX daemons that control the two

different levels of the SS7 protocol stack. The SS7 stack receives SS7 messages from

the SS7 module and performs MTP3/ISUP processing on the SS7 messages. The

SS7 Module

Solaris processor

Solaris or Windows

Solaris, Windows, or Linux

Telephony Application

Versatel Managed API

(MAPI)

Voice Switching Operating System

(VSOS)

Versatel Signalling Interface Layer

(SS7 SIL)

SS7 API

SS7 ISDN User Part

(ISUP)

SS7 Message Transfer Part 3

(MTP3)


(MTP2)


(MTP1)

Introduction

6

stack then communicates with Solacom’s SS7 SIL that resides on the same Solaris

processor.

MTP Level 3 routes messages based on the routing label in the signaling information

field (SIF) of message signal units. The routing label includes a Destination Point

Code (DPC), an Originating Point Code (OPC), and a Signaling Link Selection

(SLS). Point codes are numeric addresses that uniquely identify each signaling point

in the SS7 network. When the destination point code in a message indicates the

receiving signaling point, the message is distributed to the appropriate user part

indicated by the service indicator. The selection of the outgoing link is based on

information in the DPC and SLS.

ISUP information is carried in the Signaling Information Field (SIF) of a Message

Signal Unit (MSU). The SIF contains the routing label followed by a 14-bit (ANSI)

or 12-bit (ITU) circuit identification code (CIC), also known as the Interface ID in

the Solacom domain.

2.4 Solacom’s SS7 SIL and VSOS

The SS7 SIL provides the interface between the SS7 stack and the EdgeIQ’s VSOS.

The SS7 SIL and SS7 stack run on the same processor whereas the VSOS can

operate on the same processor or on an external server. If VSOS is operating on an

external server, the SS7 SIL communicates with the VSOS over a TCP/IP

connection. The SS7 SIL receives SS7 maintenance and signaling messages from the

SS7 stack. The SS7 SIL forwards the SS7 messages to VSOS.

2.5 SSP and STP Support

The SS7 Solution supports Service Switching Point (SSP) services for its own

configuration but can be connected to a Signal Transfer Point (STP).

Connections are supported by a dedicated signaling link and cannot be used if bearer

channels are on the same link.

2.6 Bearer Channel Level Maintenance

The system supports maintenance at the span level only. All channel-level

maintenance messages to the stack are transferred with circuit group commands.


7

2.7 Configuration

EdgeIQ configuration is performed by IQ Admin (see Section 3.4). Full details on

the configuration are provided in the EdgeIQ Configuration Reference and the

EdgeIQ Configuration Guide. In this context, IQadmin is used to review and change

T1 card configurations and SS7 bearer channel trunk groups.

SS7 module configuration is performed by the Man Machine Language interface (see

Section 3.5). Full details on the MML are provided in the supplied SS8 Distributed7

User Manual. In this context, the MML is used to configure T1 framing, T1 line

encoding, local point codes, links, linksets, routes, and routesets.

2.8 SS7 Duplication

A sample fully redundant SS7 system with two VSOS servers, two SS7 modules, two

SS7SILs operating on independent processors is shown below. The system is divided

into side A and side B. The associated configuration fields stored in the

―Mesoware.ini‖ file are also shown (italicized characters).

The first SS7SIL to start registers all trunk groups. When the second SS7SIL starts,

the first SS7SIL transfers control of a set of trunk groups to the second SS7SIL. An

SS7SIL configured as the listen port in the ―Mesoware.ini‖ file controls the odd

bearer spans and an SS7SIL configured as the connect port controls the even bearer

spans. The SS7SILs are automatically setup in a load-sharing mode. Upon failure of

one SS7 SIL, load-sharing is stopped and the operational SS7SIL manages all SS7

links and bearer spans.

All trunk group configuration information is exchanged between the VSOS servers

over a cross connect link between the VSOS A and VSOS B servers. The link’s IP

address is specified in the DuplicationIP field of the ―Mesoware.ini‖ file.

All call information is exchanged between the SS7 SILs over a cross connect link

between the Solaris SBC cards. The link’s IP address is specified in the

SS7DuplicationIP field of the ―Mesoware.ini‖ file. The remote host’s IP address

is specified in the SS7DuplicationHostName field of the ―Mesoware.ini‖ file.

Introduction

8

Figure 2: SS7 Duplication

SS7SIL/ISUP/MTP3

(Solaris SBC Card)

MTP2/MTP1

(SS7 Module)

T1 Span with

SS7 signalling channels

Ethernet

(MesowareIP)

Handles odd

T1 bearer spans

(SS7DuplicationMode =

listen)

T1 Span with

SS7 signalling channels

(Solaris SBC Card)

(SS7 Module)

To VSOS Server

Ethernet

(MatedMesowareIP)

Ethernet

Cross connect

(SS7DuplicationIP)

Handles even

T1 bearer spans

(SS7DuplicationMode =

connect)

To VSOS Server

SS7SIL/ISUP/MTP3

MTP2/MTP1

SS7 module SS7 module Processor card Processor card

Side A Side B

Side A Side B


9

3 Getting Started with SS7

This section details the procedures to follow to get started with SS7. Once the procedures are

executed, you can route calls over SS7 signaling links.

3.1 Reviewing the Factory Configuration

SS7 software and hardware is already installed in your EdgeIQ platform. Your

system is configured as follows:

One SS7 module is installed in PMC slot 1 of the processor card.

Figure 3: SS7 Module

SER: Serial debug port (Not used)

L1: T1 Line 1 LED (Red/Green/Yellow)

L2: T1 Line 2 LED (Red/Green/Yellow)

Line 1: T1 Line 1 port (RJ-48C)

Line 2: T1 Line 2 port (RJ-48C)

SS7 Module dipswitches SW1 to SW4 are in the OFF position.

Side View

SS7 Module Processor (Main Card)

Getting Started with SS7

10

In a redundant configuration, a second SS7 module is installed in PMC slot 1

of a second processor card.

Each processor card is installed in the EdgeIQ shelf. The processor card

locations for each shelf type are shown below:

Figure 4: Processor Cards

The SS7 software is loaded onto each processor card. The default installation

path is

/export/home/NewNet

Solacom’s VSOS configuration file is configured for your system. The

filename and default location is:

export/home/SS7SIL/Mesoware.ini

The lifetime SS7 license filename and default location is

/export/home/NewNet/access/etc/license.dat

The $PATH is set up to contain the following:

/export/home/NewNet/access/bin

/export/home/SS7SIL

The $VERSATEL_PATH is set up to contain the following:

/export/home/SS7SIL

Side View

IQ1500 Shelf

Processor Slot 1

IQ4000 Shelf

Processor Slot 8 (Side A)

Processor Slot 18 (Side B)


11

The SS7 script files are in

/export/home/NewNet/access/bin

The SS7SIL script files supplied by Solacom are in

/export/home/SS7SIL

The administration server hosts the following:

IQadmin at:

Click Start>All Programs>Solacom Technologies>IQadmin>IQadmin

Log files at:

I:\EdgeIQ\Mesoware\Logs\

Logs can be viewed within IQadmin. Refer to IQadmin User Guide.

3.2 Connecting the SS7 Module to the Network

SS7 connectivity to the network is provided by T1 interfaces located on the SS7

module. Sample connections for a redundant system are listed below:

Side A SS7 Module Line 1 connection to the network using an RJ-48C

straight cable. Maximum cable length is 100 feet.

Side B SS7 Module Line 1 connection to the network using an RJ-48C straight

cable. Maximum cable length is 100 feet.

Typically one or two channels from a span are used to convey signaling information

to and from the SS7 network. The remaining channels are not used.

Figure 5: Network Connection

3.3 Viewing the Mesoware.ini Configuration

Typical connections and ―Mesoware.ini‖ file configurations for a sample shelf with

an ID of 25 and external VSOS servers are shown below:


12

Figure 6: Mesoware.ini Configuration

Ethernet Port 2

SS7SIL Duplication

Communication

SS7 A

T1 Link to

Network

Ethernet Port 1

VSOS Communication

SS7 B

T1 Link to

Network

[Mesoware]

MesowareIp=172.16.25.103

MesowarePort=15001

MesowareDSN=Nexus

[MatedMesoware]

MatedMesowareIp=172.16.25.104

MatedMesowarePort=15001

MatedMesowareDSN=MatedNexus

[SS7SIL]

SS7DuplicationIp=192.168.111.9

SS7DuplicationPort=15002

SS7DuplicationMode=listen

SS7DuplicationHost=Solacom 25-

2d

[Mesoware]

MesowareIp=172.16.25.104

MesowarePort=15001

MesowareDSN=Nexus

[MatedMesoware]

MatedMesowareIp=172.16.25.103

MatedMesowarePort=15001

MatedMesowareDSN=MatedNexus

[SS7SIL]

SS7DuplicationIp=192.168.111.9

SS7DuplicationPort=15002

SS7DuplicationMode=connect

SS7DuplicationHost=Solacom 25-

2d

Processor A

Front Rear

Processor B

Rear Front

Shelf 25 – Side A Shelf 25 – Side B

VSOS A

Server

VSOS B

Server

The SS7 SIL B IP address is the same as

processor B's IP address: 172.16.25.21 The SS7 SIL A IP address is the same as

processor A's IP address: 172.16.25.20


13

3.4 Configuring SS7 using the IQadmin

Some EdgeIQ default parameters may require updates to suit your requirements. To

change the default configuration or view the existing configuration, start the

IQadmin:

To start the IQadmin…

1. From the Start menu, click All Programs > Solacom Technologies >

IQadmin>IQadmin.

Figure 7: IQadmin

2. Enter DisplayHelp to display a full list of commands

The interface responds to keywords, so if you enter a string of one or more letters,

the commands containing the specified string are displayed. For example, to list all

commands containing the string ―trunkgroup‖, enter the keyword trunkgroup. To

get help on a specific command click the Help button.

More detailed information on IQadmin is provided in the IQadmin User Guide.

To view all cards …

1. Enter the command DisplayCard.

2. Enter -1 in the ShelfNumber field.

3. Enter -1 in the SlotNumber field.


14

4. Click on the Execute button. Refer to the figure below for sample output.

To view the configuration of the T1 cards…

1. Enter the command DisplaySpan

2. Enter 25 in the ShelfNumber field.

3. Enter 2 in the SlotNumber field. Refer to the figure below for sample output.

Sample output for a card in shelf 25, slot 2:

Note that Framing and Coding of the T1 card spans is independent of the

SS7's T1 span configuration (see Section 3.5.2). The fields do not have to

match.

An SS7 trunk group must be configured with the proper destination point code

(DPC) specific to your installation.

To view the default SS7 trunk group configuration…

1. Enter the command DisplayTrunkGroup

Sample output:


15

To view the channel configuration of the SS7 trunk groups…

1. Enter the command DisplayTrunkGroupChannels

2. Enter 3 in the TrunkGroupNumber field.

Sample output:

In this example, trunk group number 3 is an SS7 trunk group with 24 enabled

channels belonging to a card in shelf 25, slot 2, and span 0. The CICs (listed

under the InterfaceId column) for channels 0 to 23 are 24 to 47.


16

3.4.1 SS7 Trunk Group Configuration

If you do not have a configured SS7 trunk group for your T1 cards, or the

configuration is not suited to your installation, you must create and configure an SS7

trunk group.

To change the default SS7 trunk group configuration…

1 Remove the existing trunk group (if present) using the DisableSpan and

RemoveTrunkGroup commands, and then create a new trunk group. For

example:

DisableSpan 25,2,-1

RemoveTrunkGroup 3

2 To define the ISUP (Voice) Trunks, enter Displaytrunkgroup all to

display the Trunk Groups.

The trunk groups already defined in the switch are displayed.

3 Enter ? createss7trunkgroup to view the syntax. See example below.

4 Convert point codes. For example:

If XXX-YYY-ZZZ is the Point Code, convert XXX to Hex AA, YYY to Hex

BB, and ZZZ to Hex CC. Then convert AABBCC to decimal 123456789.

Each SS7 node has a unique identity called the Destination Point Code

(DPC). The DPC is used in the SS7 protocol to address messages to nodes.

The Circuit Identification Code (CIC) uniquely identifies a telephone circuit

among those interconnecting a source and destination.

Note: To convert a destination point code to the Versatel DCP value required

for the CreateSS7TrunkGroup command, proceed as follows:


17

a Obtain the destination point code: For example, 005-014-159.

b Convert each numerical segment to hexadecimal notation: 05-0E-9F.

c Concatenate to form a hexadecimal value: 0x050E9F.

d Convert the hexadecimal value to a decimal value: 331423.

You can use the HelpConvertSS7DestPointCodeToVersatelDPCValue

command to convert a decimal SS7 destination point code to the Versatel

DPC value required for the CreateSS7TrunkGroup command, and you can

use the HelpConvertVersatelDPCValueToSS7DestPointCode

command to convert a Versatel DPC value as stored in DPC field of a SS7

trunk group to a decimal SS7 destination point code. For example:

HelpConvertSS7DestPointCodeToVersatelDPCValue 005-014-159

and

HelpConvertVersatelDPCValueToSS7DestPointCode 331423

5 Create a trunk.

CreateSS7TrunkGroup 3, SS7_TG1, 331423, 25, 2, 0, 24, _

MOST_IDLE, 0, 0, 61, 62, 0

Note: An underscore at the end of a line means continue on the same line.

The CreateSS7TrunkGroup command has the following parameters:

Parameter Values

TrunkGroupNumber 3 (0–134217727)

TrunkGroupName SS7_TG1 (string up to 50 characters)

DPC 331423 (Integer) — an address uniquely

identifying your network entity.

ShelfNumber 25 (0–31)

SlotNumber 2 (0–15)

SpanNumber 0 (0–15)

StartCIC 24 (0 or a Multiple of 24 for T1) — circuit

identification code.

HuntAlgorithm MOST_IDLE (FIRST_AVAILABLE,

ROUND_ROBIN_BACKWARD,

ROUND_ROBIN_FORWARD,

MOST_IDLE)

localSP 0 (0–7) — an arbitrary number used to

identify the local node with a single digit.

IEId 0 (Integer) — Information Element Profile.

LocalTxCOTToneID 61 (0–63) — tones from the GeneratedTone

table that will be played on this trunk group

when a ContinuityTest is performed.


18

Parameter Values

RemoteTxCOTToneID 62 (0–63) — tones from the GeneratedTone

table that will be played on this trunk group

when a ContinuityTest is performed.

PercentageOfOutgoingCOT 0 (0–100) — the percentage of outgoing

calls that COT will be performed on.

6 Use the MoveSpanToTrunkGroup command to add additional spans to the

trunk group. For example, to add the remaining 15 spans of the T1 card in

shelf 25, slot 2 to the SS7 trunk group, proceed as follows:

MoveSpanToTrunkGroup 25,2,1,3,48















The MoveSpanToTrunkGroup command has the following parameters:

Parameter Values

ShelfNumber 25 (0–31)

SlotNumber 2 (0–15)

SpanNumber 1 (0–15)

TrunkGroupNumber 3 (0–4095)

StartCIC circuit identification code.

7 Enable the spans. For example:

EnableSpan 25,2,-1

8 View the configuration. For example:

DisplayTrunkGroupChannels 3

3.4.2 Channel-based Trunk Group Configuration

EdgeIQ allows an operator to configure trunk groups with a small number of

channels that can be sent to a different destination. The following commands can be

launched at the SS7 channel level:


19

MoveChannelToTrunkGroup

MoveRangeOfChannelsToTrunkGroup

RemoveChannelFromTrunkGroup

EnableChannel

DisableChannel

EnableRangeOfChannels

DisableRangeOfChannels

The following example shows 2 trunk groups (500 and 600). Each trunk group has

12 channels.

Trunk group 500 has channels 1,3,5,7,9,11,13,15,17,19,21,23

Trunk group 600 has channels 0,2,4,6,8,10,12,14,16,18,20,22

To create the 2 trunk groups perform the following:

1. Select EdgeIQ from the IQadmin application.

2. Ensure the Shelf, Card, Span, Channel parameters are set to -1, to create an

empty trunk group.

3. CreateSS7TrunkGroup 500, SS7_MINI_CTL_1 , 15728412 ,-1,-1,-1,-

1,MOST_IDLE,0,0,61,62,0

4. CreateSS7TrunkGroup 600, SS7_RD_1 , 460809 ,-1,-1,-1,-

1,MOST_IDLE,0,0,61,62,0

5. Use MoveChannelToTrunkGroup to move each one of the 12 channels into the

trunkgroup. Notice the InterfaceID which is the last parameter is the SS7 CIC to

assign to the channel. Therefore starting channel 0 gets CIC 5, channel 2 gets

CIC 6 and so on until channel 22 gets CIC 16. The trunkgroup 600 is configured

the same but the channels in use will be 1, 3, 5 etc.

movechanneltotrunkgroup 30,3,0,0,500,5







20







The following displays how the trunk groups will appear once they are configured: Refer to Figure 7.

DisplayTrunkGroup 500

Name Num TrunkGroupType HuntAlgorithm ProfileID localSp DPC DS0s LocalTxCOTToneID RemoteTxCOTToneID PercentageOfOutgoingCOT

--------------------------------------------------------------------------------------------------------------

SS7_MINI_CTL_1 500 SS7 MOST_IDLE 0 0 15728412 12 61 62 0

DisplayTrunkGroup 600

Name Num TrunkGroupType HuntAlgorithm ProfileID localSp DPC DS0s LocalTxCOTToneID RemoteTxCOTToneID PercentageOfOutgoingCOT

--------------------------------------------------------------------------------------------------------------

SS7_RD_1 600 SS7 MOST_IDLE 0 0 460809 12 61 62 0


21

Figure 8: IQadmin Logical View

3.5 Launching the MML Interface

Some SS7 default parameters may require updates to suit your requirements. Based

on the factory configuration of your system, an MML session for your signaling

point is started by entering the following command at the Solaris prompt of the

processor card hosting the Distributed7 software:

# mml 0

The 0 represents the logical signaling point number of the node. This is the same

value assigned to the User Part Multiplexer daemon (upmd 0) and the ISDN

User Part daemon (isupd 0). The default MML prompt is shown below:

Figure 9: Default MML Prompt


22

Use the exit:; command to exit from MML.

Use the help:; command to get online help. A list of available commands is

displayed along with the help command prompt by entering the desired command.

For example:

HELP_MML_CMD> modify-line:;

or, from the MML prompt:

MML_TH> help:cmd=modify-line:;

Note: MML is not case sensitive with respect to command and parameter names.

MML converts this input to upper case. However, user-defined values entered for a

parameter are case-sensitive. Predefined options must be entered in upper case.

The following is a set of useful MML display commands. Details on these

commands are provided in the SS8 Distributed7 User Manual:

Figure 10: MML Display Commands

3.5.1 Viewing the SS7 Stack Configuration

The SS7 stack is factory configured using a set of Man Machine Language (MML)

commands entered at the Distributed7 MML prompt. This configuration defines the

rules for daemons that must run at all times. The daemons are listed below:

Application process manager (apmd)

Master event log (mlogd)

Service provider module or Signalling point module (spmd)

Network - TCP/IP (netd)

Alarm (alarmd)

Distributed shared memory manager (dsmd)

Distributed kernel memory manager (dkmd)

User part multiplexer (upmd 0)

ISDN user part (isupd 0)

The configuration is stored in the ―apmconfig‖ file located at

―/export/home/NewNet/access/RUN/config/PMGR‖. The commands in this file are

executed when the apm_start command is executed from the Solaris prompt.


23

Changes to the factory configuration are not required.

3.5.2 Viewing the Default SS7 Module Configuration

The SS7 module is factory configured using a set of Man Machine Language (MML)

commands entered at the Distributed7 MML prompt. This configuration includes

host names, spans, ports, and network parameters. The main default parameters are

listed below:

3.5.2.1 SS7 Module (Side A)

Parameter Description

Hostname solacomXX-1d (XX = shelf identifier)

Active span Line 1 (clock source is obtained from the line)

Span configuration T1 with ESF framing and B8ZS encoding

Maximum line length of 100 feet

Notify is enabled for framer line alarms

Network class type Class B

Signaling ports 1 port (port 0 on Line 1)

Signaling port 0 64000 bits/s with idle detection

Table 2: SS7 Module Side A Default Parameters

3.5.2.2 SS7 Module (Side B)

Parameter Description

Hostname solacomXX-2d (XX = shelf identifier)

Active span Line 1 (clock source is obtained from the line)

Span configuration T1 with ESF framing and B8ZS encoding

Maximum line length of 100 feet

Notify is enabled for framer line alarms

Network class type Class B

Signaling port (channel) 1 port (port 0 on Line 1)

Port 0 configuration 64000 bits/s with idle detection

Table 3: SS7 Module Side B Default Parameters

See Section 0 for information on changing the above configuration.


24

To view the system configuration…

Copy the following commands and paste them at the MML command prompt:

DISPLAY-SS7BOARD:;

DISPLAY-PORT:;

DISPLAY-LINK:;

DISPLAY-LINKSTAT:;

DISPLAY-LSET:;

DISPLAY-LSETSTAT:;

DISPLAY-ROUTE:;

DISPLAY-RTSET:;

DISPLAY-LINE:;

DISPLAY-LINESTAT:;

DISPLAY-SP:;

DISPLAY-HOST:;

DISPLAY-MTP:;

DISPLAY-ISUP:;

DISPLAY-NTWK:;

DISPLAY-ISUPCCT:;

DISPLAY-ISUPCGRP:;

DISPLAY-TCPCON:;

Additional display commands can be used to view other configured components. Or

enter the help:; command to view all SS7 commands. Sample output:

Figure 11: The MML Help Menu

Warning: Using the MODIFY-ISUPCCT command with the Group and

Range settings may cause unpredictable behavior.


25

3.5.3 Changing the Default SS7 Module Configuration

Sample commands defining the default configuration for the solacom25-1d host are

shown below:

MML_TH> add-ss7board:hostname=solacom25-1d,boardnm=pmc8260,_

inst=0,ports=1, conf=OFF,clockmode=LINE,clockspan=1;

MML_TH> modify-ntwk:hostname=solacom25-1d,mode=DSTRBTD, _

NETMASK1=1fffff00, NETMASK2=1fffff00,DUALHOST=solacom25-1;

MML_TH> add-host:hostname=solacom25-1d,rmthost=solacom25-2d, _

ALIAS=solacom25-2, rmthosttyp=AMGR,conf=ON;

MML_TH> modify-port:hostname=solacom25-1d,boardnm=pmc8260_

,inst=0,portnum=0,baud=64000,LPBKMODE=NONE,IDLEDETECT=ON;

MML_TH> modify-line:hostname=solacom25-1d,boardnm=pmc8260,_

inst=0,span=1,line_typ=T1,line_frmmod=T1ESF,line_cod=T1B8ZS,_

line_len=L110,line_NTFY=ON;


Highlighted parameters may require updates to suit your requirements.

To change the highlighted parameters…

1 Access the MML (see Section 3.5).

2 Update the parameter values.

For example, to change the port’s baud rate to 56000, the T1 framing mode to

T1ZBTSI, and the T1 line encoding to T1B7ZS, enter the following

commands:

MML_TH> modify-ss7board:hostname=solacom25-1d,_

boardnm=pmc8260,inst=0,ports=1,conf=OFF;

MML_TH> modify-port:hostname=solacom25-1d, baud=56000;

MML_TH> modify-line:hostname=solacom25-1d,_

boardnm=pmc8260,inst=0,span=1,line_typ=T1,_

line_frmmod=T1ZBTSI,line_cod=T1B7ZS,line_len=L110,_

line_NTFY=ON;

MML_TH> modify-ss7board:hostname=solacom25-

1d,boardnm=pmc8260,inst=0,ports=1,conf=ON;

MML commands are also described in the supplied SS8 Distributed7 User Manual.

Sample online help output for the modify-port command is shown below:


26

Figure 12: Help for modify-port Command

3.6 Configuring the SS7 Links and Routes

This section defines a sample network configuration and provides a procedure to

configure a set of redundant SS7 connections linking an SSP to a single destination

through two signal transfer points (STPs).

A connection between two points is defined by a link, linkset, route, and routeset.

These terms are defined below:

Link: a physical connection to a destination.

Linkset: a collection of links.

Route: a collection of linksets assigned to a destination.

Routeset: a collection of routes.


27

System specifications for these terms are as follows:

Maximum number of linksets per signaling point (SP): 64

Maximum number of links per signaling point: 256

Maximum number of links per linkset: 128

Maximum number of routesets per signaling point:: 2048

Maximum number of routesets on a linkset: 2048

Maximum number of routes per routeset: 16

Maximum number of load sharing linksets per routeset: 2

The sample network configuration below consists of the following:

One EdgeIQ with a DPC of 5-7-0, an SP of 0, two hosts, and two SS7

modules.

One SS7 module connects to STP1 that is configured with a DPC of 5-7-101.

A second SS7 module connects to STP2 that is configured with a DPC of

5-7-102.

The destination connects to STP1 and STP2 and has a DPC of 5-7-200.

Figure 13: Sample Network Configuration

To become a node in the SS7 network, you must modify the SP managed object to

provide your protocol a unique identity (point code).

To provide a point code…

1 Access MML 0 from the solacom25-1d host as follows:

EdgeIQ

(5-7-0)

(SP 0)

STP1

(5-7-101)

STP2

(5-7-102)

Dest.

(5-7-200)

Connection managed by the solacom25-1d host with 1 link, 1 linkset, 1 route, and 1 routeset.

Connection defined by the solacom25-1d host with 1 route and 1 routeset.

Connection managed by the solacom25-2d host with 1 link, 1 linkset, 1 route, and 1 routeset.

Connection defined by the solacom25-2d host with 1 route and 1 routeset.


28

# mml 0

2 Enter your signaling point number, name, and DPC (spc):

MML_TH> modify-sp:spno=0, name=solacom, spc=5-7-0;

3 Repeat the above for the solacom25-2d host.

The details of the network connections including the MML commands to configure

the connections are shown below. For convenience, all component labels associated

with a node contain the node's DPC value when possible.


29

Figure 14: Network Connections with MML Commands

EdgeIQ

(5-7-0)

(SP 0)

STP1

(5-7-101)

STP2

(5-7-102)

Dest.

(5-7-200)

MML_TH> add-rtset:RTSET=RS_5_7_0_1, DPC=5-7-101;

MML_TH> add-lset:LSET=LS_5_7_0, DPC=5-7-101, TYPE=ALINK, _

LOADED=1, ACTIVE=1, EMERGENCY=ON;

MML_TH> add-route:RTSET=RS_5_7_0_1, LSET=LS_5_7_0, PRIORITY=0;

MML_TH> add-link:LINK=L_5_7_0, LSET=LS_5_7_0, SLC=0, PRIORITY=0, _

HOSTNAME=solacom25-1d, BOARDNM=pmc8260, INST=0,PORT=0;

MML_TH> mod-lsetstat:LSET=LS_5-7-0, status=SET_ACT;

MML_TH> mod-linkstat:LINK=L_5-7-0, status=SET_ACT;

MML_TH> add-rtset:RTSET=RS_5-7-0_2, DPC=5-7-200;


M MML_TH> add-rtset:RTSET=RS_5_7_0_1, DPC=5-7-102; MML_TH> add-lset:LSET=LS_5_7_0, DPC=5-7-102, TYPE=ALINK, _

LOADED=1, ACTIVE=1, EMERGENCY=ON;


MML_TH> add-link:LINK=L_5_7_0, LSET=LS_5_7_0, SLC=0, PRIORITY=0, _

HOSTNAME=solacom25-2d, BOARDNM=pmc8260, INST=0,PORT=0;

MML_TH> mod-lsetstat:LSET=LS_5-7-0, status=SET_ACT;

MML_TH> mod-linkstat:LINK=L_5-7-0, status=SET_ACT;

MML_TH> add-rtset:RTSET=RS_5-7-0_2, DPC=5-7-200;


Host: solacom25-1d RouteSet: RS_5_7_0_1 LinkSet: LS_5_7_0 Route: R_5_7_0_1 Link: L_5_7_0 Port: 0 (T1 channel 0) SLC: 0 (Sig. link code)

RouteSet: RS_5_7_0_2 Route: R_5_7_0_2

Host: solacom25-2d RouteSet: RS_5_7_0_1 LinkSet: LS_5_7_0 Route: R_5_7_0_1 Link: L_5_7_0 Port: 0 (T1 channel 0) SLC: 0 (Sig. link code)

RouteSet: RS_5_7_0_2 Route: R_5_7_0_2

Configure routeset/linkset/

route/link

Activate linkset//link

Deltas from the above configuration

are highlighted


30

3.7 The SS7 Processes

The system is configured to launch all processes upon Solaris start-up. The following

is executed:

apm_start – upon start-up, apmd creates and manages a set of processes as

defined in the ―apmconfig‖ file.

vn_ss7sil_start.sh – starts the SS7SIL and the SS7SIL watchdog.

The SS7SIL watchdog monitors the SS7SIL process and re-spawns the process upon

unexpected termination.

To stop SS7 processes…

1. Enter the command apm_stop to stop the processes defined in the ―apmconfig‖

file.

2. Enter the command vn_ss7sil_stop.sh to stop the SS7SIL and the SS7SIL

watchdog.

Sample output:

SS7 processes start automatically when the processor is rebooted.

To manually start SS7 processes…

1 Enter the command vn_ss7sil_start.sh

2 Enter the command apm_start

Sample output:


31

3 If any alarms are present, they are displayed on the screen. To halt alarm

message output to your screen, type CTRL-C.

4 If you want to resent alarm output to your screen, access the ―alarmlog‖

directory and enter tail -f:

# cd /export/home/NewNet/access/RUN/alarmlog

# tail -f

apmd started

mlogd started

spmd started

netdstarted

alarmd started

dsmd started

dkmd started

upmd started

isupd started

SS7 Distributed7 software is running


32

3.7.1 Verifying the Status of SS7 Processes

You can verify the operational status of the SS7 processes by accessing the host and

executing a set of commands from the Solaris prompt. This procedure allows you to

verify the following on the VSOS Solaris server:

1 Check the SS7 stack status.

2 Check the SS7 point code and ISUP stack.

3 Check SS7 SIL manager status.

4 Check the SS7 link status.

5 Check the linkset status.

6 Check the SS7’s T1 framing status.

7 Check the ISUP circuit status.

8 Check the ISUP circuit groups.

9 Display the logs and alarms issued by the stack in real-time.

10 Make a test call.

To view the status of SS7 processes…

1 Check that the SS7 stack is running.

The highlighted objects must be listed and their status must be set to ok as

shown:

2 Check that the SS7 point code and ISUP stack are running.

The highlighted objects must be listed and their status must be set to ok as

shown:


33

The Sp=0 and up=5 items of the ss7obj object indicate that the first local

point code and the ISUP stack are running.

The presence of the VN_ASP objects indicates that the SS7SILMngr has

connected to the stack.

3 Verify the status of the SS7 SIL process.

4 Check the SS7 link status by entering the MML mode and displaying the link

status.

ACT = ON indicates that the links are active.

LOADED = ON indicates that the links are available to carry traffic (if

aligned).

AVL = ON indicates that the links are aligned at MTP Level 3.

5 Check the linkset status by displaying the linkset status.

6 Check the SS7’s T1 framing status.


34

Item Description

HOSTNAME Host name of the SS7 module.

BOARDNM SS7 board name.

INST SS7 board driver instance number.

SPAN Span identifier.

ERREVENTS ESF error event count.

CURSTATUS Current signal status (UNAVailable or AVailable).

CUR_TIMER Current interval timer.

CUR-ES Errored seconds (ES) - current interval.

CUR-UAS Unavailable seconds (UAS) - current interval.

24H-ES Total count of ES in the last 24 hours.

24H-UAS Total count of UAS in the last 24 hours.

VLDINTTOTAL Number of valid 15-Min intervals.

Repeat the display-linestat:; command several times and observe that

only the CURTIMER field changes. The CUR-ES (Current Errored Seconds)

and the CUR-UAS (Current Unavailable Seconds) values must be static.

7 Check the status of the ISUP circuits.


35

Item Description

STATUS Indicates the current call status of the circuit (IDLE,

INCOMING, OUTGOING).

MNTCSTATUS The current maintenance status of the circuit

(UN-BLK, R-BLK, L-BLK, LR-BLK). The value

should be unblocked (UN-BLK).

8 Check the configuration of the ISUP circuit groups.

Circuit group identifier =

Modulus 24 of the first CIC (Interface ID) of the first channel in the trunk group.

Trunk group identifier =unique identifier for a circuit group

Call control name =

ESP0 > SS7SIL handling the even bearer spans

(connect side)

OSP0 > SS7SIL handling the odd bearer spans

(listen side)

Circuit number =

Maximum number of channels in the span.


36

9 Exit from MML using the command exit:;, and then check the alarms

issued by the stack.

where xxx is the highest numbered file in the directory.

The alarm logs are displayed in real-time. Sample output:

To stop the real-time display of alarms, type CTRL-C.

Upon failure of one or more of the above steps, refer to Section 3.7 to obtain

information on how to stop and restart the processes.

10 Make a call to a device associated with SS7 signaling and test the audio path.


37

4 SS7 Procedures

This section describes some of the procedures that you can use once you have installed and

configured SS7 as the PSTN signalling system

4.1 Add a New Remote Destination

This procedure assumes that you are going through the same adjacent point code to a

new one.

To add a remote destination for SS7…

1 Telnet into the Solaris Blade on the EdgeIQ (left side).

2 From the Administration server, open a DOS command window.

3 Enter the command ipconfig to obtain the Shelf number.

One of the Ethernet ports will have a 172.16.XX.100 IP address. Take note

of the XX digits.

4 Enter telnet 172.16.XX.20 (where XX is the Shelf number).

5 Enter mml 0 to enter the SS7 Stack.

6 Enter Display-rtset:; to display the Route Set.

This shows you the routes defined to the destination Point codes.

7 Enter Display-route:; to display the Route.

This shows you the linkset name that the route uses.

8 Add a new Destination Point Code.

Substitute the Point codes of your new destination into the Blue and Red text

below (blue is the route name; red is the DCP; green is the Linkset already

defined and will be the same). This procedure assumes you are not adding a

New Physical SS7 link, and that you are using one that is already working

and that all the messaging from the new destination Point code will be passed

SS7 Procedures

38

through the adjacent switch that already has a link to the EdgeIQ. Enter the

following:

add-rtset:RTSET=RTXXX-XXX-XXX, DPC=XXX-XXX-XXX;

add-route:RTSET=RTXXX-XXX-XXX, LSET=LS238-125-16, _

PRIORITY=0;


The first command defines a Route Name and a Destination Point code, and

the second command defines what linkset to use to get to the Destination

Point code defined by the Route Name. If there was already a linkset defined,

then it should be the Green in the above command.

9 Enter Exit:; to exit the MML.


39

5 Troubleshooting

Distributed7 and Solacom alarms and logs are indicators of certain problems and events.

They show the general status of the system at any given time. This section describes the

recommended tools for obtaining system status and troubleshooting problems.

The tools you can use include:

Command log (always active)

Command history log (always active)

Master event log (always active)

Alarm log (always active)

Event reports (user initiated)

Alarm reports (user initiated)

CLI command logs (always active)

5.1 View the SS7 Command Log File

MML logs all MML commands, except DISPLAY commands, that are entered by an

operator. Each log of a command also contains the login name and ID of the user

who entered the command along with the date and time at which it was entered.

Reviewing this file can help to verify the commands and values that were entered.

This logging operation can be turned on and off with the modify-mmlconf

command. The log file is located at

―/export/home/access/RUN0/backup/MML/commands.current‖. Sample output:

Troubleshooting

40

Figure 15: SS7 Command Log Sample

5.2 View the SS7 Command History Log File

Whether or not the logging of MML commands is enabled, a history facility exists,

which records the most recently executed MML commands. The number of

commands that are buffered is set with the modify-mmlconf command. The default

is 100 commands. The history file is located at

―/export/home/access.1.3.0.12/RUN0/config/MML/commands.history‖. Sample

output:

Figure 16: SS7 Command History Log Sample

5.3 View the SS7 Master Event Log Files

The master event log files continually collect messages that indicate problem cases,

major steps, or state changes that occur during the operation of the Distributed7

software. The event levels can be INFO, MINOR, MAJOR, or CRITICAL. The

master event logs are stored with dated filenames in the directory

―/export/home/access/RUN0/mlog/‖. Sample event log file entry:


41

Figure 17: SS7 Master Event Log

Sample

The oldest log file in the master log directory is automatically deleted when the size

of that directory reaches 8,192 kbytes (default configuration). The system

administrator is responsible for moving the log files to a backup medium before they

are deleted. A sample command to increase the mlog directory size to 32,768 kbytes

is shown below:

MML_TH> mlogd -m 32768

5.4 View the SS7 Alarm Files

The alarm process collects, analyzes, logs, and displays alarm messages that are

generated by the user/kernelspace components of the Distributed7 system software

and/or user application programs running under the Distributed7 environment. An

alarm message includes:

an alarm type (a hexadecimal identifier for each alarm made up of group

number, module number, and alarm number)

an alarm level (Info, Minor, Major, Critical, Fatal)

an ASCII description of the alarm (maximum of 128 Bytes)

The alarm log files are located at ―/export/home/access/RUN/alarmlog‖. Each

filename is prefixed with ―AccessAlarms‖. The file extension is a number. The

higher the number in the extension, the newer the alarm file.

A list of alarm conditions that may be encountered by the Distributed7 system

software is provided in the form of a set of alarm text files that are located at

―/export/home/access.1.3.0.12/RUN/config/ALARM‖. A list of individual alarm

groups is provided within the alarmGroups file, located in the same directory.

Sample alarm file entry:

Timestamp Process and hostname

Process ID Source code and line ID

Event level Event text

Troubleshooting

42

Figure 18: SS7 Master Alarm

Sample

The alarm messages are logged to an ―AccessAlarms.xxx‖ file until the file reaches

the default size of 512 kilobytes. Then, a new file is created with a higher numbered

extension. The default configuration allows up to 10 alarm files. When the directory

contains 10 files and a new log file is created, the oldest log file (the file with lowest

numbered extension) is automatically erased. A sample command to set the file size

to 1,024 kbytes and to set the number of files to 20 is shown below:

MML_TH> alarmd -n 20 -m 1024

The SS7 alarm groups and their associated alarm ID range are listed below:

TRMOD - translation module (820101 - 820104)

SPM - signaling point (SP) management (830101 - 830708)

UPM - user part management, such as MTP Level 3 (840101 - 840401)

SCCP - service connection control part management (850101 - 85150a)

MTPL1 - MTP Level 1 (860101 - 860136)

MTPL2 - MTP Level 2 (870101 - 870152)

ETMOD - Ethernet test module (880101 - 880501)

ISUP - ISUP management (890101 - 890133)

APM - Application Process Management (8b0101 - 8b030a)

OMAP - operation, maintenance, and administration part (8d0101 - 8d011f)

NIMOD - connection management (920101 - 920401)

TCAP - TCAP driver (950101 - 950806)

TCMOD - TCAP over TCP/IP connection management (960101 - 960206)

DKM - Distributed kernel memory (970101 - 970803)

ISUPMOD - ISUP management - distributed (990201 - 990407)

Timestamp Alarm ID Local signaling point

Hostname

Alarm text Alarm level


43

5.5 Generate SS7 Event Reports

Use the apm_report command to extract specific details from the available event

logs and generate a report.

Option Description

-b mmddyy List events that occurred on or before a specified date.

-e mmddyy List events that occurred on or after a specified date

-p priority identifier List events with a specific priority level:

(1:Info, 2:Minor, 3:Major, 4:Critical)

Table 4: apm_report Command Options

A sample command to display all major and critical event messages generated by the

local host on or after March 4, 2008 is shown below:

apm_report -b 030408 -p 34

5.6 Generate SS7 Alarm Reports

Use the ebs_report command to extract specific details from the available alarm

logs and generate a report.

Option Description

-b mmddyy List alarms that occurred on or before a specified date.

-e mmddyy List alarms that occurred on or after a specified date

-p priority identifier List alarms with a specific priority level:

(1:Info, 2:Minor, 3:Major, 4:Critical)

Table 5: ebs_report Command Options

A sample command to display all minor, major, critical, and fatal alarm messages

generated by the local host on or before March 4, 2008 is shown below:

ebs_report -e 030408 -p 2345

Troubleshooting

44

5.7 View the Log Files

The VSOS creates diagnostic logs and presents them through the OAM&P API. You

can use the ResumeDiagnostic and SuspendDiagnostic commands to start and

stop the VSOS from sending these diagnostic logs to the CLI. Diagnostic logging is

automatically enabled when VSOS is started.

The filename format for the log files is DIAGmmdd.csv where mm is the month and

dd is the day of the month. The files are at ―I:\Mesoware\Logs‖.

The default maximum size of each diagnostic log file is 4,096 kbytes. The file is not

written to after the file reaches this size. The default configuration stores 30 days of

log files. When a log is created after midnight, the current log file is closed and a

new log file is created. At this time, any log files older than 30 days are deleted.

Log files can be read using the Versatel FileReader application located at

―I:\Mesoware\Applications‖. They can also be opened using a text editor. Sample log

output and record information for the CLIENT ALREADY CONNECTED log is

shown below:

Figure 19: Sample Log

Note: All SS7 alarms are also logged in the EdgeIQ log.


45

A List of Acronyms

Acronym Expanded Form

API Application Programming Interface

CIC Circuit Identification Code

DPC Destination Point Code

ESF Extended Super Frams

ISDN Integrated Services Digital Network

ISO International Standards Organization

ISUP ISDN User Part

LNP Local Number Portability

MAPI Messaging Application Programming Interface

MML Man Machine Language

MTP Message Transfer Part

MSU Message Signal Unit

OAM&P Operation, Administration, Maintenance, and Provisioning

OPC Originating Point Code

OSI Open System Interconnect

PCS Personal Communication System

PMC PCI Mezzanine Card

PSTN Public Switched Telephone Network

List of Acronyms

46

Acronym Expanded Form

SIF Signaling Information Field

SIL Signaling Interface Layer

SLS Signaling Link Selection

SP Signaling Point

SS7 Signaling System no. 7

SSP Service Switching Point

STP Signal Transfer Point


47

B Level 2 Tracing SS7

SS7 tracing is useful when there are issues with carrier interoperation; it allows a

hex dump to be captured and decoded. Tracing is only available on the SS7 Card,

and is accessed via command line on the Solaris processor that contains the SS7

Stack.

Note: The L2tool is used as a debugging tool mainly to troubleshoot a particular test

case failure scenario. It is not recommended to run this tool for long time on a live

system, since this will affect the performance of the SS7 Interface board.

It is not possible to relate the logs dumped from L2tool to the AccessAlarm logs

because the time that is displayed in the AccessAlarm logs is the system time

whereas the time displayed by L2tool output is the time the stack was started. This

time is cumulative and is reset when the Stack is restarted. The time displayed in the

L2tool is in milliseconds.

Standards to follow when breaking down SS7 messages.

ANSI: ansi+t1.113-1995.pdf

BellCore gr246.pdf

1.1 Tracing SS7 – Using L2TOOL

Log in to the Solaris console where the SS7 Stack is running and launch the NewNet

L2 tracing tool.

1. From the Solaris prompt # enter the following:

# l2tool

Level 2 Tracing SS7

48

The following information is displayed:

l2tool v0.1

Copyright (c) 1991-2002, SS8 Networks Inc.

type `?' for help.

2. Enter the following commands at the prompt:

l2tool> open /dev/pmc8260x

l2tool> dev 0

l2tool> select

l2tool> !ah

l2tool> db


Solaris 2.7+ poll(2) misbehavior correction activated.


j(db)> !ah


sal(pmc8260) v1.2.0 (2002)

Copyright (c) SS8 Networks, Inc.

mtpl2(pmc8260) v1.2.0 (2002)

Copyright (c) SS8 Networks, Inc.


db(level2)> n+rt *

This will begin to stream SS7 trace messages to the screen. Capture this trace by

copying the screen.

Note: When the trace is complete, exit the debug level correctly, refer to step 5. If

you do not exit correctly the processor must be restarted to use the trace again, which

means the SS7 stack will be down.

5. To exit the trace, enter the following commands at the prompt:

db(level2)> !q


49

l2tool> q

#

Note: NIC-01 refers to Network Incoming SS7 link 01 and NOG-01 refers to

Network Outgoing SS7 Link 01.

6. Capture the output from this command. The following information is displayed:

db(level2)> NOG-01: time=026949595 size=018 (#576)

c6a00f85 09080703 02010c18 00170200 0101

NOG-01: time=026949596 size=018 (#577)

c6a10f85 09080703 02010c18 00170200 0101

NOG-01: time=026949596 size=003 (#578)

c6a100

NIC-01: time=026949606 size=003 (#579)

a0c600

NIC-01: time=026949609 size=019 (#580)

a0c71085 03020109 08070c18 00290200 020100

NIC-01: time=026949609 size=003 (#581)

a0c700

NOG-01: time=026949609 size=003 (#582)

c7a100

NIC-01: time=026949610 size=003 (#583)

a1c700

NIC-01: time=026949611 size=003 (#584)

a1c700

NOG-01: time=026949615 size=019 (#585)

c7a21085 09080703 02010c18 00180001 020103

NOG-01: time=026949616 size=019 (#586)

c7a31085 09080703 02010c18 00180001 020103

NOG-01: time=026949617 size=003 (#587)

c7a300

NIC-01: time=026949626 size=003 (#588)

a2c700

NIC-01: time=026949629 size=019 (#589)

Level 2 Tracing SS7

50

a2c81085 03020109 08070c18 001a0001 020103

NIC-01: time=026949629 size=003 (#590)

a2c800

NOG-01: time=026949629 size=003 (#591)

c8a300

NIC-01: time=026949631 size=003 (#592)

a3c800

NIC-01: time=026949632 size=003 (#593)

a3c800

1.2 Automated Decoding SS7 using Wireshark

To access scripts to format L2tools output into a format readable by Wireshark, refer

to Solacom support. The following procedure lists the steps to decode SS7 using

Wireshark.

1. Copy the ss7wireshark directory into the C:\EdgeIQ directory.

2. Ensure Wireshark is installed at c:\Program Files\Wireshark.

3. Execute the following script from a command prompt:

C:\EdgeIQ\ss7wireshark\ss7wireshark.vbs <l2tools

tracefile> <out.txt>

Eg) C:\EdgeIQ\ss7wireshark\ss7wireshark.vbs good.txt

out.txt

Note: This step may take up to 20 seconds; wait for the following dialog box to

appear.

Figure 20: Windows Script Host

4. Click on the OK button.

The following files are created:


51

a. The following is an example of Out.txt which is the <l2tools tracefile>:

NOG-01: time=026949595 size=018 (#576)

c6a00f85 09080703 02010c18 00170200 0101

11112222 33

NOG-01: time=026949596 size=018 (#577)

c6a10f85 09080703 02010c18 00170200 0101

b. The following is an example of <out.txt>:

0000 c6 a0 0f 85 09 08 07 03 02 01 0c 18 00 17 02 00 01 01 11 11 22 22

0000 c6 a1 0f 85 09 08 07 03 02 01 0c 18 00 17 02 00 01 01

c. Output2 is the output of the command ―text2pcap.exe out.txt output2‖

d. Output3 can be loaded into wireshark. Output3 is the result of editcap -T mtp2

output2 output3

5. Launch Wireshark. Navigate to Edit->Preferences->Protocols->MTP3. The

Wireshark: Preferences Profile: Default window appears. See figure below.

6. Set the following preferences:

Set MTP3 standart to ANSI

Set Use 5-bit SLS(ANSI only)

Set Address Format to Dashed

Level 2 Tracing SS7

52

7. Load output 3 into Wireshark, the following window appears.

B2214167-6 SR1