SS7 Technical Reference-Glenayre

Copyrights
1997 Glenayre Electronics, Inc.
This document is copyrighted with all domestic and international rights reserved.
No part of this document may be reproduced, stored in a retrieval system, or
transmitted, in any form, by any means, without the prior written permission of
Glenayre Electronics, Inc. No patent is assumed with respect to the use of the
information contained in this document.
Trademarks
Glenayre is a registered trademark of Glenayre Electronics, Inc.
All brand names and product names are trademarks or registered trademarks of
their respective companies and are used with the permission of their owners.
Revisions
This document is written and published by Glenayre Atlantas Technical

Publications Department, and every precaution has been taken to ensure its
accuracy. Should you find an error, please contact Technical Publications at the
Atlanta offices of Glenayre Electronics, Inc.
Glenayre Electronics, Inc. assumes no responsibility for errors in this document,

omissions, or their consequences. The information is subject to change without
notice.
Reordering
When purchasing additional copies of this document, please include the following
information:
Part Number: 9110.00616
Revision 2.1
Date of Issue: July 27, 1998
Address all comments and requests regarding this document to:
Glenayre Electronics
Technical Publications Department
11360 Lakefield Drive
Duluth, GA 30097
USA
Tel: (770) 283-1000

Fax: (770) 497-3981
Website: http://www.glenayre.com
SS7 Reference Manual
D OCUMENT C HANGE R ECORD

Revision Release Date Changes
1.0 25 October 1995 Original.
1.1 2 May 1996 Deleted all references to MVP-E.

Changed system file name from ss7/ss7ch to syspar/ss7ch.
Added J38 and J39 to Figure 2-4 (CPU 302 Jumper Configuration)
Updated Figure 2-5 (SS7 ASM).
Reworded Section 3.1.4 (SS7 Poll Task).
Deleted tailor sequence for the T1 cards in Section 3.1.7.
Reworded explanation for *patch <memory address><desired
value> in section 3.2.2.
Reworded note in Section 3.3.
Reworded objective for ccflow.r, for Section 3.3.3.4.
Added note to Id_ss7.r, Section 3.3.3.5.
Deleted Usage column in the Action Commands Table, Section
3.3.4.1.
2.0 23 March 1998 Corrected jumper settings for the SS7 Network Interface Card: CPU
302 (PCB 136.1906), CPU 302 (PCB 126.2067), and the SS7 ASM.
Incorporated a workaround procedure for extinguishing an
erroneously lit LOC lamp in section 3.1.1 of the document.
Incorporated instructions for configuring the MVP SS7 serial
interface as DCE into section 2.7 of the document.
Created an appendix based on the SS7 Install Kit Test Procedure
189-1506-TP Rev. B: 10/25/95 document.
Updated the information in the SS7 Install Kit Test Procedure for the
appendix.
Corrected serial link configuration information in section 2.6.2.
2.1 27 July 1998 Corrected PCM/Serial Connection directions, section 2.6.

Added new callflows to Chapter 3.
PN 9110.00616 iii
Document Change Record
Documentation Change Request Form
Use a copy of this form to report documentation errors and/or suggested

improvements. Please provide the following information, giving as full a
description of the error or recommended improvement as possible.
Date: ____________________
Name of Manual: _______________________________________
Part Number: ____________________
Issue Date: ____________________
Page Number: ___________
Description of error or suggested improvement:
_______________________________________________________________
_______________________________________________________________
_______________________________________________________________
_______________________________________________________________
Recommended Priority: _______
1 = extremely urgent
Major error in critical information; could result in severe system problems.
2 = moderately urgent
Highly useful but noncritical information is missing or incorrect; the flaw should
not, however, cause major system problems.
3 = not urgent
Relatively minor error which should be addressed with next scheduled
documentation update; this category includes, but is not limited to, minor
typographical and page layout errors.
Change requested by:
__________________________________________________________
(Name)(Company)
________________________
(Phone Number)
Send completed form to:
Glenayre Electronics, Inc.

Technical Publications Department
Duluth, GA 30097-1508
iv REV 2.1 Mar. 23, 1998

TABLE OF CONTENTS
1. GENERAL INFORMATION ................................................................................................................. 1
1.1 Introduction .................................................................................................................................. 1
1.1.1 SS7 Overview........................................................................................................................ 1
1.1.2 SS7 Call Flow Description ..................................................................................................... 2
1.2 Getting Technical Assistance ...................................................................................................... 3
1.3 Address for Repairs .....................................................................................................................4
1.4 Precautions for Handling Removable Assemblies .......................................................................5
2. SS7 HARDWARE DETAIL .................................................................................................................. 7

2.1 Network Interface Card ................................................................................................................ 7
2.1.1 CPU302 ................................................................................................................................. 8
2.1.2 SS7 ASM .............................................................................................................................12
2.2 SS7 Translator ...........................................................................................................................14
2.3 T1/CEPT Interface Card ............................................................................................................16
2.4 DSP Line Cards .........................................................................................................................16
2.5 Cables and Connectors .............................................................................................................17
2.6 Installing the Hardware ..............................................................................................................17
2.6.1 PCM Configuration ..............................................................................................................18
2.6.2 Serial Configuration .............................................................................................................19
2.6.3 Configuring the CPU302......................................................................................................20
2.6.4 Connecting the Diagnostic Port and Passthr .......................................................................21
2.6.5 Interconnecting the PCM Link (digital interface) ..................................................................21
2.6.6 Interconnecting the Serial Link (RS-530/RS-449/V.35) .......................................................21
2.6.7 Completing the Installation ..................................................................................................21
2.6.8 Interface Pin Configurations and Connector Illustrations ....................................................22
2.7 Configuring the MVP SS7 Serial Interface as DCE ...................................................................27
2.7.1 Configuring the ASM Jumpers............................................................................................. 27
2.7.2 Configuring the Software .....................................................................................................27
2.7.3 Using the Crossover Cable..................................................................................................28
3. SOFTWARE CONFIGURATION .......................................................................................................29

3.1 T1/CEPT ....................................................................................................................................29
3.1.1 /syspar/config ......................................................................................................................30
3.1.2 ccdigtk .................................................................................................................................30
3.1.3 /syspar/t1 .............................................................................................................................31
3.1.4 SS7 poll task........................................................................................................................31
3.1.5 TSC poll task .......................................................................................................................31
3.1.6 tktailor ..................................................................................................................................31
3.1.7 trunk.ares.............................................................................................................................32
3.2 MTP Controller Software ...........................................................................................................32
PN 9110.00616 v
TABLE OF CONTENTS
3.2.1 Configuring the Network Control Card.................................................................................33

3.2.1.1 Initiating a New MTP Download......................................................................................40
3.2.2 SS7CC Diagnostic Port .......................................................................................................41
3.2.3 Debug Message Printouts ...................................................................................................42
3.2.4 SS7CC Communication Tasks ............................................................................................42
3.2.5 Maximum Number of SS7 Links ..........................................................................................43
3.2.6 MTP Card Statistics.............................................................................................................43
3.3 Network User Part Software (TUP and ISUP) ...........................................................................43
3.3.1 Channel Task .....................................................................................................................44
3.3.2 SS7 state tables ..................................................................................................................44
3.3.3 Modifications to MVP System Files .....................................................................................45
3.3.3.1 /syspar/channels .............................................................................................................45
3.3.3.2 /syspar/ss7ch ..................................................................................................................45
3.3.3.3 tup.e & isup.e ..................................................................................................................47
3.3.3.4 ccflow.r............................................................................................................................47
3.3.3.5 Id_ss7.r ...........................................................................................................................48
3.3.3.6 ss7_flg.r ..........................................................................................................................48
3.3.4 Callflow Action Commands..................................................................................................51
3.3.5 Callflow Process Commands...............................................................................................52
3.3.6 Sample Callflows .................................................................................................................53
3.3.6.1 Inbound SS7 call.............................................................................................................54
3.3.6.2 Outbound SS7 call ..........................................................................................................59
A. SS7 LOOPBACK TEST PROCEDURE ............................................................................................61

A.1 Equipment Required..................................................................................................................61
A.2 System Setup ............................................................................................................................61
A.3 Test Procedures ........................................................................................................................62
A.3.1 Serial Link Check ................................................................................................................62
A.3.2 PCM Link Check .................................................................................................................63
A.4 MVP SS7 Loopback Connector.................................................................................................65
GLOSSARY ...........................................................................................................................................67
INDEX ....................................................................................................................................................69
vi REV 2.1 July 27, 1998

LIST OF FIGURES
Figure 2-1 SS7 Network Interface Card (PCB 136.1906)............................................................................ 8
Figure 2-2 SS7 Network Interface Card (PCB 126.2067).......................................................................... 10
Figure 2-3 SS7 ASM..................................................................................................................................12
Figure 2-4 SS7 Translator .........................................................................................................................15
Figure 2-5 Rev.2 MVP: Panel Illustration and Location Table for DB25 Connectors ................................22
Figure 2-6 Rev.3 MVP: Panel Illustration and Location Table for DB25 Connectors ................................23
Figure 2-7 RS-449 Connector: Pin Configuration and Front View Illustration ...........................................24
Figure 2-8 RS-530 Connector: Pin Configuration and Front View Illustration ...........................................25
Figure 2-9 V.35: Pin Configuration and Front View Illustration..................................................................26
Figure 2-10 Crossover Cable Pinout .........................................................................................................28
Figure 3-1 Sample ScreenMTP Configuration Menu: Board Number 0.................................................33
Figure 3-2 Sample ScreenLayer 3 Route Table ....................................................................................35
Figure 3-3 Sample ScreenLink Configuration Menu .............................................................................. 36
Figure 3-4 Sample ScreenLink Set 1 Route Configuration Menu ..........................................................38
Figure 3-5 SS7 Inbound Callflow...............................................................................................................53
PN 9110.00616 vii
LIST OF TABLES
Table 2-1 CPU302 Jumper Configuration (PCB 136.1906).......................................................................... 9
Table 2-2 CPU302 Jumper Configuration (PCB 126.2067)........................................................................11
Table 2-3 SS7 ASM jumper Configuration .................................................................................................13
Table 3-1 MTP Controller Address Assignments ......................................................................................32
Table 3-2 MTP Configuration Menu Help Information ...............................................................................34
Table 3-3 Layer 3 Route Table Help Information .......................................................................................35
Table 3-4 Link Configuration Menu Help Information .................................................................................36
Table 3-5 Link Set 1 Help Information ........................................................................................................39
PN 9110.00616 ix
GENERAL INFORMATION
1.1 Introduction
This document contains information necessary for connecting the Glenayre
MVP to an SS7 network. It includes hardware requirements and
configurations, software configuration, and installation procedures. This
document contains only SS7-specific data and is intended as a supplement to the
MVP Software Manual. Please refer to this manual for additional information on
the MVP, as well as for a breakdown of pertinent regulatory notices and
warnings.
Additional information on SS7 and Common Channel Signaling (CCS) can be

found in the following documents:
1988 (Blue Book) CCITT Recommendations Q.721Q.766 (Code ISBN
92-61-03521-3).
ISDN Message Service General RequirementsBellcore Technical Reference
TR-NWT-000866 (Issue 1, January 1991)
1.1.1 SS7 Overview

SS7 is a signaling method in which signaling information for all audio channels
is sent on a common channel (known as Common Channel Signaling
, or CCS). SS7 allows the MVP to be connected to the Advanced Intelligent

Network (AIN) for communication of information regarding call termination
and origination, call transfer and routing, ANI (Automatic Number
Identification), etc.
Interface to the SS7 network can either occur through T1/E1 interface cards or
through serial links between the switching network and the MVP. If the
signaling is combined with voice on a T1 or E1 stream, the T1/E1 interface card
strips out the channels containing the signaling information and routes those
channels to an SS7 Network Interface Card residing on the VME bus in the MVP.
PN 9110.00616 1
GENERAL INFORMATION
For serial links, the SS7 information enters the MVP through connectors on the
rear of the machine. The standard serial interface is RS-530, with V.35 and RS-449
as optional serial interfaces.
The Network Interface Card executes the MTP (Message Transfer Part) portion
of the SS7 protocol and handles the network requirements for maintaining the
SS7 link. Each Network Interface Card is capable of supporting two SS7 links,
and up to two such cards can be installed in the system. Call control information
(TUP or ISUP) is processed on the MVPs central processor and communicated
to the network CPU via a shared memory interface.
1.1.2 SS7 Call Flow Description

The following is an overview of how the MVP handles a typical call in the SS7
environment:
1. The SS7 link presents an initial address message containing a subscriber
number.
2. The audio path is verified as connected and the requested subscriber
number is validated.
3. The MVP sends an "address complete" message indicating that the
requested subscriber number has been received and validated.
4. The trunk answers the call and the appropriate Answer message is sent to
the SS7 link. This signifies that the CO may now begin charging for the call
(if applicable).
5. The MVP enters into System Mode and the caller is connected to the
system.
6. When either the caller or MVP disconnects, a Clear message is sent to the
other party.
7. When the MVP receives the Clear message, a Release message is sent and
the trunk is returned to idle.
2 REV 2.1 July 27, 1998

1.2 Getting Technical Assistance

Technical Support is available to all Glenayre customers. Telephone support is
available Monday through Friday between the hours of 8:00 a.m. and 8:00 p.m.
EST. Other hours must be arranged in advance. Emergency service for down
systems only is available 24 hours a day. To get the quickest response, follow
these guidelines:
Please have all of the information about the system or product you are
experiencing problems with, or have questions about, with you at the time
of your call. You will be asked to provide your name, phone number,
address, and company name. You also will be asked for the machine name,
revision number, software version, and all relevant serial numbers.
If possible, try the operation several times to determine that the system
response is identical under identical circumstances. If the problem is not
repeatable, or if the responses are different for each attempt, make a note of
the input process, output results, and differences. If the problem is
completely random, try to repeat the situation until a pattern of cause and
effect can be distinguished. In any case, document all parts of the problem
thoroughly and have your notes in front of you when you call.
If you are calling with a system problem, be at the terminal ready to execute
any instructions given by the technical representative. Have all manuals
and documentation immediately available.
To contact Glenayre Electronics Technical Support call or write:
Glenayre Electronics, Inc.

Duluth, Georgia 30097-1508
(800) 688-4001
(770) 283-1000
PN 9110.00616 3
GENERAL INFORMATION
1.3 Address for Repairs

The following addresses are provided in the event equipment needs to be
returned for repair:
United States Glenayre Electronics, Inc.

Duluth, Georgia 30097-1508
(770) 283-1000
Canada Glenayre Electronics, Inc.

1570 Kootenay Street
Vancouver, B.C.
V5K 5B8
(604) 293-1611
United Kingdom Glenayre Electronics, Inc.

No. 3 Challenge House
Sherwood Drive
Bletchley
Milton Keynes MK3 6DP2
44-908-644642
4 REV 2.1 July 27, 1998

1.4 Precautions for Handling Removable Assemblies

Glenayre manufactures and tests all products in a static-controlled environment.
Improper handling may result in component failure or decreased performance.
Please observe the following guidelines when handling any removable
assembly.
1. Make sure you are grounded and working in a static-controlled
environment.
2. Handle electrical assemblies only by the edges, avoiding contact with the
connectors.
3. Never install an assembly into a powered-on system, unless clearly
indicated that it is safe to do so. As a general rule, you can install assemblies
that have a power switch with the switch in the off position. Only after you
seat and secure the assembly, should you turn the power on.
4. Never force a connection. Assemblies that are difficult to seat are not
normal. In instances where assemblies are difficult to seat, check the
following:
Make sure that nothing is obstructing the cables or connectors.
Verify that the card is in the proper slot and seated in the guides
correctly.
5. Verify all jumper configurations before the installation of any component.
Use the information in this manual to be sure that you properly configure
the assemblies.
6. Cabinet doors should remain closed and locked during normal operation
for proper cooling and for safety reasons.
PN 9110.00616 5
SS7 HARDWARE DETAIL
The following parts are required to connect the MVP to the SS7 network:
Network Interface Card (CPU302 w/SS7 ASM)
SS7 translator
T1/CEPT interface card
Serial port ribbon cable
10-pin ribbon cable, 26-pin DHR/DB25 ribbon cable, and Null modem
cable
RS-449 adapter cable or V.35 adapter cable (as required)
These items are available in upgrade kits 006.1356 and 189.1506. The
components may also be ordered individually if necessary. This chapter contains
a description of each item and provides individual part numbers.
2.1 Network Interface Card

The Network Interface Card (also known as the SS7 Control Card) consists of a
CPU302 and an SS7 ASM daughter board. The function of the SS7 ASM is to
select the SS7 signaling source and to translate the signaling data on the ST-Bus
and RS-530/RS-449/V.35 serial links to the Serial Communication Controllers
(SCCs) of the CPU302. The module also generates necessary timing signals
programmed through software for PCM data on proper time slots.
The desired serial or PCM mode is selected by setting jumpers and switches on
the SS7 ASM and the ASM Translator.
The CPU302 and SS7 ASM are discussed in detail later in this section.
Part Number 140.2004 - NIC module (CPU302 w/SS7 ASM)

140.1906 - CPU302 only
140.1919 - SS7 ASM only
Location Shelf C, any available slot
PN 9110.00616 7
SS7 HARDWARE DETAIL
2.1.1 CPU302
In an SS7 environment, the CPU302 must be configured as shown in the
following illustrations and tables. Figure 2-1 shows an SS7 Network Interface
Card (PCB 136.1906), and Table 2-1 details the configuration. Information on the
SS7 Network Interface Card (PCB 126.2067) is depicted in Figure 2-2 and Table
2-2.
Figure 2-1 SS7 Network Interface Card (PCB 136.1906)
8 REV 2.1 July 27, 1998

The following jumpers are normally installed on PCB 136.1906:

JR3, 16, 17, 18, 19, 21, 23, 34, 47, 63
The default settings are as follows:

Table 2-1 CPU302 Jumper Configuration (PCB 136.1906)
REF
DES DEFAULT DESCRIPTION
JR3 IN DRAM size visible to VME bus JR3 IN, JR4 OUT=8MB DRAM
JR4 OUT JR3 OUT, JR4 IN=4MB DRAM
JR6 OUT Enable System Controller Functions of MVME6000
JR16 IN JR16 IN=1ST SS7 CPU OUT=2ND SS7 CPU
JR17 IN
JR18 IN
JR19 IN
Short I/O Address of MVME6000
JR20 OUT
JR21 IN
JR22 OUT
JR23 IN
JR34 IN Enables Parity Error Interrupt When IN
JR 35 OUT Watchdog Timeout Interrupt OUT=DISABLE
IN=ENABLE
JR36 OUT Baud Rate Select OUT=9600
IN=2400
OUT Crash Dump Enable OUT=ENABLE
JR37 IN=DISABLE
JR38 OUT DIAG MODEM STRING: OUT=NO STRING
IN=ATS3=255 AFTER RESET
JR39 OUT Not Used
JR40 OUT Host/IPC Select
JR47 IN Size of DRAM
JR48 OUT
JR63 IN Mode Control JR63 IN=Host Mode
PN 9110.00616 9
SS7 HARDWARE DETAIL
Figure 2-2 SS7 Network Interface Card (PCB 126.2067)
10 REV 2.1 July 27, 1998

Table 2-2 CPU302 Jumper Configuration (PCB 126.2067)
REF
JR3 IN DRAM size visible to VME bus JR3 IN, JR4 OUT=8MB DRAM
JR4 OUT JR3 OUT, JR4 IN=4MB DRAM
JR6 OUT Enable System Controller Functions of MVME6000
JR16 IN JR16 IN=1ST SS7 CPU OUT=2ND SS7 CPU
JR17 IN
JR18 IN
JR19 IN
Short I/O Address of MVME6000
JR20 OUT
JR21 IN
JR22 OUT
JR23 IN
JR34 IN Enables Parity Error Interrupt When IN
JR 35 OUT Watchdog Timeout Interrupt OUT=DISABLE
IN=ENABLE
JR36 OUT Baud Rate Select OUT=9600
IN=2400
JR37 OUT Crash Dump Enable OUT=ENABLE
IN=DISABLE
JR38 OUT DIAG MODEM STRING: OUT=NO STRING
IN=ATS3=255 AFTER RESET
JR39 OUT Not Used
JR40 OUT Host/IPC Select
JR47 IN Size of DRAM
JR48 OUT
JR63 IN Mode Control JR63 IN=Host Mode
JR64 OUT JR64 OUT=Shared Memory Mode
PN 9110.00616 11
SS7 HARDWARE DETAIL
2.1.2 SS7 ASM

The SS7 ASM contains two 100-pin connectors, described as follows:
J3 provides interconnect with CPU302 for communication of internal data,

address, and control signals.
J4 provides interconnect between the ASM and ASM Translator through

columns A and C of the VME bus.
Note There could be an exception to the illustration in Figure 2-3. In some

cards, the A/B setting is reversed. You will need to note the position
of pin 1 for E3, E4, E5, and E6.
Jumpers and switches must be set as shown in the following illustration:
Figure 2-3 SS7 ASM
12 REV 2.1 July 27, 1998

Table 2-3 SS7 ASM jumper Configuration
REF DEFAULT DESCRIPTION

DES
E1 IN PCM/Serial Link IN=PCM OUT=SERIAL
C8 (8. 192 MHz) C4 (4.096 MHz) C2 (2.048 MHz)
E2A OUT IN OUT OUT
E2B IN Clock Source OUT IN OUT
E2C OUT OUT OUT IN
E3 A Serial Link A=RS-530/RS-449 B=V.35
E4 A (See Note regarding E5 just before Figure 2-3.)
E5 A
E6 A
E7A OUT Always Out
E7B OUT
E7C OUT
E7D OUT
Receive XMIT Clock (DTE)Provide XMIT Clock (DCE)
S1-1 Closed Port 1 Closed Open
S1-2 Open Open Closed
Receive XMIT Clock (DTE)Provide XMIT Clock (DCE)
S1-3 Closed Port 2 Closed Open
S1-4 Open Open Closed
S1-5 Open
S1-6 Open Serial Link RS-530/RS-449=All Open
S1-7 Open V.35 Closed S1-5, 6,9,10
Open S1-7,8
S1-8 Open
S1-9 Open
S1-10 Open
PN 9110.00616 13
SS7 HARDWARE DETAIL
2.2 SS7 Translator

The SS7 Translator Card is used to connect the CCS ST-Bus, RS-530/RS-449, and
V.35 signals to the CPU302 card. Its basic function is to make physical
connections.
Part Number 140.1970
Location Shelf C, in rear of same slot as Network Interface Card
Connectors The ASM Translator contains the following connectors:
Connector Function
J1 Serial Links #1 and #2 (for RS-530/RS-449/V.35)
J3 F0, CLK signals, and CCS-A signaling
J2, J4 & J5 CCS-B to CCS-D
J6 Diagnostic Port
Jumpers This table contains the jumper configuration for serial link:
REF
JR1 IN
Serial Link Interface
JR2 IN
IN=RS-530/RS-449
JR3 IN
OUT=V.35
JR4 IN
14 REV 2.1 July 27, 1998

Figure 2-4 SS7 Translator
PN 9110.00616 15
SS7 HARDWARE DETAIL
2.3 T1/CEPT Interface Card

The PC8081 T1/CEPT interface card must contain firmware that allows the
routing of one or more channels from the digital span to the Common Channel
Signaling (CCS) ST-Bus highway. IC U29 of the card should contain a label
reflecting the correct firmware version (see table below).
Part Number The following table reflects a breakdown of part numbers for the 8081 interface
card:
Part Numbers
Card EPROM only
T1 140.1542 249.0963 (version 1.01.00)
CEPT Twisted Pair 140.1540 249.0964 (version 1.01.00)
CEPT Coax 140.1541 249.0964 (version 1.01.00)
Additional information on the 8081 interface card can be found in the MVP
Hardware Manual.
2.4 DSP Line Cards

DSP line cards must contain an updated PROM to allow for continuity test
requirements for TUP and ISUP user parts. The required PROM is Rev. D1,
version 5.06.01 or later. This PROM provides the following:
Transmission of a 2000 Hz tone
Transmission of a 1780 Hz tone
Detection of a 2000 Hz tone
Detection of a 1780 Hz tone
Part Number The following table reflects part numbers for DSP line card modules containing
the SS7 PROM:
Termination Type
DSP Module R1 R2
8072/8063 4-wire 140.1338 140.1649
8072/8071 2-wire 140.1333 140.1648
8079/8200 4-wire E&M 140.1973 140.1845
8079/8098 2-wire 140.1972 140.1809
8079/8080 T1/CEPT 140.1545 140.1847
16 REV 2.1 July 27, 1998

Additional detail on the DSP line cards can be found in the MVP Hardware
Manual.
2.5 Cables and Connectors

The following cables are necessary for connecting the MVP to an SS7 network:
Two 10-pin ribbon cables (2303.60083) between the T1/CEPT translator and
SS7 translator to carry CCS signalling data, PCM (ST-BUS) clock C4, and
frame synchronization signal F0.
26-pin DHR/DB25 ribbon cable (2303.00079) between the SS7 translator
and DB25 diagnostic port at back door of the MVP.
Null modem cable (2303.00417) between MVP diagnostic port and terminal.
50-pin ribbon cable (2302.00105) between back panel of the MVP and the
SS7 translator card for RS-530/RS-449/V.35 serial links.
Adaptor cables to support RS-449 (2303.00077) and V.35 (2303.00078) serial
interfaces.
2.6 Installing the Hardware

Use the procedures described in this section for installing SS7 hardware in the
MVP.
Caution Be sure to take appropriate measures to avoid ESD damage to

the boards.
1. Configure the ASM board (140.1919) and SS7 translator (140.1970) by

setting the switches and jumpers according to the physical interface. See the
tables and drawings provided earlier in this section for locations of the
switches and jumpers.
2. Select PCM or Serial Communication by setting jumper E1 on the SS7 ASM:
For PCM, E1 should be installed.
For Serial Communication, E1 should be removed.
3. For PCM configuration procedures, see Section 2.6.1. For Serial
Communication configuration procedures, see Section 2.6.2.
PN 9110.00616 17
SS7 HARDWARE DETAIL
2.6.1 PCM Configuration

Follow these steps to set the PCM configuration. Note the following key
information:
1=jumper on or switch closed

0=jumper off or switch open
E1-E7a-d are on SS7 ASM
JR1-JR4 are on SS7 Translator
1. Set jumpers E7a-d and S7 & S8 as indicated here:
(Located on the SS7 ASM)
Signal Type E7a E7b E7c E7d S7 S8

Differential* 0 0 0 0 0 0
Single-ended 1 1 1 1 1 1
*Always use this setting
2. For SS7 board 0 link 0, set S1 to 1 and S2 to 0.

3. Set jumpers E2A-C as indicated here:
Clock Source E2A E2B E2C

C8 (8.192 MHz) 1 0 0
C4 (4.096 MHz)* 0 1 0
C2 (2.048 MHz) 0 0 1
*Always use this setting
18 REV 2.1 July 27, 1998

2.6.2 Serial Configuration

Follow these steps to set the serial configuration. Note the following key
information:
1=jumper on or switch closed

0=jumper off or switch open
E1-E7a-d are on SS7 ASM
JR1-JR4 are on SS7 Translator
1. Set jumpers E3-6, S5-10, and JR1-4 as indicated here. See Section 2.6.8 for
interface pin configurations and connector illustrations.
(Located on
the SS7
(Located on the SS7ASM)
Translator)
Interface E3-E6 S7, S8 S5, S6, S9, S10 JR1-JR4

RS-530/RS-449 A 0 0 1
V.35 B 0 1 0
2. Configure the Transmit Clock as indicated here:
(Port 1) (Port 2)
Transmit Clock S1 S2 S3 S4
Receive Xmit Clock* 1 0 1 0
(DTE)
Provide Xmit Clock 0 1 0 1
(DCE)
*Normal configuration
Note For information on how to configure the MVP as the Data

Communications Equipment (DCE) see Section 2.7 of this document.
PN 9110.00616 19
SS7 HARDWARE DETAIL
2.6.3 Configuring the CPU302

Follow these steps to configure the CPU302 (140.1906). For jumper locations, see
the tables and drawings shown in Section 2.1.1. Note the following key
information:
1=Install shunt
0=Remove shunt
1. To configure the CPU302 to its Shared Memory Mode, set jumpers JR40,
JR6, and JR3 as shown here:
System Mode JR40 JR6 JR3

Shared Memory 0 0 1
2. To configure the shared memory address, set jumpers JR16 to JR19 as

shown here:
CPU302 Card JR16 JR17 JR18 JR19 VME Address Local Address
1st SS7 CPU 1 1 1 1 A00000 200000
2nd SS7 CPU 0 1 1 1 A20000 220000
3. Attach the ASM board to the CPU302 processor board.

4. With the MVP system POWERED OFF, insert the CPU302 processor board
into the proper card slot as indicated here:
System Revision SS7 CPU Card Card Slot Number

MVP Rev. 2 1st card 21
MVP Rev. 2 2nd card 22
MVP Rev. 3 1st card 6
nd
MVP Rev. 3 2 card 7
20 REV 2.1 July 27, 1998

2.6.4 Connecting the Diagnostic Port and Passthr

1. To connect the diagnostic port, attach the 26-pin DHR/DB25 ribbon cable to
J6 of the SS7 translator.
2. Connect the 26-pin DHR/DB25 ribbon cable to the SS7 CPU Diagnostic
Port. To find the correct location for this port for your system, see Section
2.6.8.
3. To connect the passthr, attach a null modem cable to the designated passthr
port. This port should be configured as follows:
setty 7 -p 0xc1,0x44,0xe2
Note For more information, refer to passthr loadable in the Loadable

Commands section of Software Reference Release X.5.
2.6.5 Interconnecting the PCM Link (digital interface)

1. For Link 0, connect the 10-pin ribbon cable from J6 of the T1/CEPT
translator to J3 of the SS7 translator. If two SS7 co-processors are present,
this cable must be daisy-chained to J3 of the second SS7 translator.
2. For Link 1, connect the 10-pin ribbon cable from J6 of the T1/CEPT
translator to J2 of the SS7 translator. If two SS7 co-processors are present,
this cable must be daisy-chained to J2 of the second SS7 translator.
2.6.6 Interconnecting the Serial Link (RS-530/RS-449/V.35)

1. Connect the 50-pin serial port ribbon cable to J1 of the SS7 translator for two
serial ports.
2. Attach the DB25 connectors, including one diagnostic port and two serial
ports per SS7 CPU card, on the back door of the MVP. To find the correct
location for these connectors, see Figure 2-5 and Figure 2-6 and the
accompanying tables in Section 2.6.8.
2.6.7 Completing the Installation

Plug the SS7 translator into the corresponding slot of the CPU302 processor card
at the backplane.
PN 9110.00616 21
SS7 HARDWARE DETAIL
2.6.8 Interface Pin Configurations and Connector Illustrations
Serial Port Location

1st SS7 CPU Port 1 J49
st
1 SS7 CPU Diagnostic J31
2nd SS7 CPU Port 1 J41
2nd SS7 CPU Diagnostic J23
Figure 2-5 Rev.2 MVP: Panel Illustration and Location Table for DB25
Connectors
22 REV 2.1 July 27, 1998

Serial Port Location

st
1 SS7 CPU Diagnostic J39
2nd SS7 CPU Diagnostic J47
Figure 2-6 Rev.3 MVP: Panel Illustration and Location Table for DB25
Connectors
PN 9110.00616 23
SS7 HARDWARE DETAIL
Wire Color DB37 Signal Name

RS-449 Pin
Number
Black 1 Shield
Blk-Red 4 Transmitted Data (A)
Blk-Wht 6 Received Data (A)
Blk-Red-Wht 7 Request to Send (A)
Red 9 Clear to Send (A)
Red-Blk NC DCE Ready (A)
Red-Grn 19 Signal Ground
Red-Wht 13 Received Line Signal Detector (A)
Red-Wht-Blk 26 Receiver Signal Element Timing DCE (B)
Orange 31 Received Line Signal Detector (B)
Org-Blk 35 Transmitter Signal Element Timing DTE (B)
Org-Red 23 Transmitter Signal Element Timing DCE (B)
Org-Grn 27 Clear to Send (B)
Green 22 Transmitted Data (B)
Grn-Blk 5 Transmitter Signal Element Timing DCE (A)
Grn-Wht 24 Received Data (B)
Grn-Wht-Blk 8 Receiver Signal Element Timing DCE (A)
Blue NC Local Loopback
Blue-Blk 25 Request to Send (B)
Blue-Red 12 DTE Ready (A)
Blue-Wht NC Remote Loopback
White NC DCE Ready (B)
Wht-Blk 30 DTE Ready (B)
Wht-Red 17 Transmitter Signal Element Timing DTE (A)
Wht-Red-Blk NC Test Mode
Figure 2-7 RS-449 Connector: Pin Configuration and Front View

Illustration
24 REV 2.1 July 27, 1998


RS-449 Pin
Number
Black 1 Shield
Blk-Red 2 Transmitted Data (A)
Blk-Wht 3 Received Data (A)
Blk-Red-Wht 4 Request to Send (A)
Red 5 Clear to Send (A)
Red-Blk 6 DCE Ready (A)
Red-Grn 7 Signal Ground
Red-Wht 8 Received Line Signal Detector (A)
Red-Wht-Blk 9 Receiver Signal Element Timing DCE (B)
Orange 10 Received Line Signal Detector (B)
Org-Blk 11 Transmitter Signal Element Timing DTE (B)
Org-Red 12 Transmitter Signal Element Timing DCE (B)
Org-Grn 13 Clear to Send (B)
Green 14 Transmitted Data (B)
Grn-Blk 15 Transmitter Signal Element Timing DCE (A)
Grn-Wht 16 Received Data (B)
Grn-Wht-Blk 17 Receiver Signal Element Timing DCE (A)
Blue 18 Local Loopback
Blue-Blk 19 Request to Send (B)
Blue-Red 20 DTE Ready (A)
Blue-Wht 21 Remote Loopback
White 22 DCE Ready (B)
Wht-Blk 23 DTE Ready (B)
Wht-Red 24 Transmitter Signal Element Timing DTE (A)
Wht-Red-Blk 25 Test Mode
Figure 2-8 RS-530 Connector: Pin Configuration and Front View

Illustration
PN 9110.00616 25
SS7 HARDWARE DETAIL

RS-449 Pin
Number
Black A Shield
Blk-Red P Transmitted Data (A)
Blk-Wht R Received Data (A)
Blk-Red-Wht C Request to Send (A)
Red D Clear to Send (A)
Red-Blk NC DCE Ready (A)
Red-Grn B Signal Ground
Red-Wht F Received Line Signal Detector (A)
Red-Wht-Blk X Receiver Signal Element Timing DCE (B)
Orange NC Received Line Signal Detector (B)
Org-Blk W Transmitter Signal Element Timing DTE (B)
Org-Red AA Transmitter Signal Element Timing DCE (B)
Org-Grn NC Clear to Send (B)
Green S Transmitted Data (B)
Grn-Blk Y Transmitter Signal Element Timing DCE (A)
Grn-Wht T Received Data (B)
Grn-Wht-Blk V Receiver Signal Element Timing DCE (A)
Blue NC Local Loopback
Blue-Blk NC Request to Send (B)
Blue-Red H DTE Ready (A)
Blue-Wht NC Remote Loopback
White NC DCE Ready (B)
Wht-Blk NC DTE Ready (B)
Wht-Red U Transmitter Signal Element Timing DTE (A)
Wht-Red-Blk NC Test Mode
Figure 2-9 V.35: Pin Configuration and Front View Illustration
26 REV 2.1 July 27, 1998

2.7 Configuring the MVP SS7 Serial Interface as DCE

Though normally configured as the Data Terminal Equipment (DTE), the MVP
can be configured as the Data Communications Equipment (DCE). This
configuration allows the MVP to be cabled directly to another DTE device.
To use the MVP serial interface as DCE, you must:

Configure the ASM jumpers correctly
Configure the software correctly
Use a crossover cable
2.7.1 Configuring the ASM Jumpers

Set the Transmit Clock for Provide Xmit Clock (DCE). For Port 1, set S1 open
and S2 closed. For Port2, set S3 Open and S4 closed. For more information, see
Section 2.6.2.
2.7.2 Configuring the Software

Use mtpconf to set the SS7 configuration for serial interface. You will need to
change the SCON register from 0x31f2 to
0x11f2 for 64 kbps data links
0x11b4for 56 kbps data links (For Serial Link ONLY)
Make sure that the device that the MVP is connected to is configured as DTE (to
receive clocks) and is set at the correct data rate. For more information, see the
instructions for using mtpconf to set the SS7 configuration for serial interface in
Section 3.2.1 of this manual.
PN 9110.00616 27
SS7 HARDWARE DETAIL
2.7.3 Using the Crossover Cable

The pinout on the MVP connector is for a DTE. Use a crossover cable to convert
the pinout to DCE. Note in Figure 2-10 that this cable is not symmetrical. The
MVP side is connected to the MVP and the cable side connects to the external
adaptor cable.
MVP Cable
DB25 MALE DB25 FEMALE
2 3
3 2
4 5
5 4
7 7
8 20
20 6, 8
13 19
19 13
10 23
23 10
14 161
16 14
9, 11 9, 12
17, 24 15, 17
Figure 2-10 Crossover Cable Pinout
28 REV 2.1 July 27, 1998

SOFTWARE CONFIGURATION
Configuration of the MVP for an SS7 environment involves the following items:
T1/CEPT configuration
MTP Controller Software
User Parts (TUP/ISUP)
This chapter describes each element.
3.1 T1/CEPT
The SS7 T1/CEPT interface card contains firmware which allows the SS7
information to be passed to the Network Interface Card on the VMEbus.
Configuration of the T1/CEPT card occurs during installation of the SS7
software. The following system files are affected:
/syspar/config
ccdigtk
tktailor
trunk.ares
PN 9110.00616 29
3.1.1 /syspar/config
To allow specification of the CCS mode via a serial link, and to assign links to
the SS7 cards, four new keywords have been added for the digital_tk line in the
/syspar/config file. These keywords are CCS0, CCS1, CCS2, and CCS3. Note the
following conventions:
The number at the end of the keyword indicates the SS7 link being
assigned.
CCS0 and CCS1 are the first and second links on the first SS7 co-processor
card. CCS2 and CCS3 specify the links on the second SS7 card.
Each CCSx keyword can appear only once in the /syspar/config file. An error
will be reported by ccdigtk if any CCSx parameter is used more than once.
The value for each parameter will be the span channel to be routed to the
SS7 co-processor. Ex: CCS0:16 specifies that channel 16 of the span be
routed to the first link on the first SS7 card.
Note If a T1/E1 card in an SS7-equipped MAP is not actually carrying an

SS7 link, but the audio channels on the card are controlled by SS7 signaling, the
LOC (Loss of synC) lamp may light. The lighting does not indicate a real error.
If this situation occurs, follow this workaround procedure to extinguish the
lamp:
1. Add a CCS keyword to the /syspar/config digital_tk line corresponding to the

board with the lamp lit.
2. Use an unused CCS link number. For example, if two SS7 links are installed in
the system (CCS0 and CCS1), add the keyword CCS2, as shown here:
digital_tk0 DIGTK_INSTALLED: 1 T1:0 DIGTK_REDUNDANT:0 ESF:0 B8ZS:0 CCS2:16
3. To make the change effective: run ccdigtk, then run tktailor, and then reset the
offending T1/E1 card.
3.1.2 ccdigtk
The ccdigtk loadable is used to handle the CCSx parameters. For each signaling
link, the link number, span number, and span channel will be stored in the
/syspar/t1 file created by ccdigtk.
A fixed mapping of signaling links to the CCS ST_BUS highway timeslots will
be programmed into ccdigtk during installation of the SS7 software. Each link (0,
1, 2, or 3) is routed into the corresponding timeslot on the CCS highway. This
mapping will be maintained no matter which trunk shelf the link is coming
from.
30 REV 2.1 July 27, 1998

The trunk shelf used for each CCSx parameter is determined by ccdigtk, based
on the digital_tk line in which the parameter is used. Digital trunks 0, 1, and 6
correspond to Shelf A (the first trunk shelf) ; digital trunks 2 and 3 correspond
to Shelf B.
For CEPT cards, the CCS bit (bit 5) of the CEPT interface chip controls the CCS
mode. This bit must be set if using channel 16 for CCS. The ccdigtk loadable will
automatically detect when timeslot 16 is used on a CEPT span and will
automatically set the CCS bit in /syspar/t1.
3.1.3 /syspar/t1
The standard MVP T1 configuration file consists of one integer (4 bytes) for each
of eight possible spans. For SS7, an additional data area consisting of one integer
for each SS7 link is appended to the existing data. Each additional integer
contains four fields, with the most significant byte (MSB) holding the SS7 link
number. Since the order of storage of the integers in the file will be in link
number order, the stored link number can be used for consistency checking.
The next byte in each integer holds the span number (0, 1, 2, 3, 6) assigned to the
link. An unused link is indicated by -1 (0xff).
The third byte contains the channel number on the span that is routed to the SS7
link.
3.1.4 SS7 poll task

The SS7 poll task (one for each SS7 card) configures the signaling channels on
the SS7 card as specified by the syspar/t1 file.
3.1.5 TSC poll task

The TSC poll task communicates CCS tailoring information to the TSC cards.
The poll task reads the SS7 information from /syspar/t1 and loads the values into
the TSC memory structure. The poll task then notifies the TSC software that new
tailor information must be sent to the T1 cards.
3.1.6 tktailor
The tktailor loadable performs the same information download as described
above for the TSC poll task. The only difference is that tktailor can be run at the
command line to download new tailoring information while the system is
running.
PN 9110.00616 31
3.1.7 trunk.ares
Trunk.ares is the TSC operating system. The TSC software is modified under SS7
to accept the additional T1 tailoring information and to communicate that
information to the proper T1 cards. To prevent the CCS links from being
overwritten, channel tailoring is performed after setting the CCS routes and
before activating the CCS channels.
Note The T1/CEPT card does not maintain the integrity of the CCS link
when the card is reset. If the routing table is intact after a reset, the
CCS channel will be restored as part of the initialization of the card.
3.2 MTP Controller Software

Based on the OSI 7 layer model, layers 1 through 3 of the SS7 protocol (MTP)
operate on the Network Interface Card (a.k.a. SS7 Controller Card), with the
upper layers (TUP/ISUP) running on the host CPU (Central). Debug EPROMs
on the NIC communicate with the host computer after power-up to download
to the controller card the software program that executes the MTP layers.
The MVP Central can support two SS7 controller cards, addressed at 0xa00000
and 0xa20000 respectively on the VME bus. Communications between the host
CPU and the controller take place through shared memory which is accessed
from the central processor at the VME bus address and from the controller at the
local address. The following table reflects these address assignments.
Table 3-1 MTP Controller Address Assignments
CPU302 Jumpers
VME Local GCSR
JR19 JR18 JR17 JR16
Address Address Base Address
1st SS7CC X X X X A00000 200000 Y0xx
nd
2 SS7CC X X X 0 A20000 220000 Y1xx
Where: X indicates an Y indicates that the nibble of the CCSR
installed shunt on the address is determined by jumpers JR20
jumper position. through JR23.
xx is the address within the GCSR
register.
32 REV 2.1 July 27, 1998

3.2.1 Configuring the Network Control Card

Configuration parameters for the Network Control Card are stored in static
memory in the central processor. At start-up, a file called /syspar/mtpconf will be
loaded into this static memory area (if the file is present), and its values will be
downloaded to the controller card at initialization time.
The loadable command mtpconf allows the values to be edited and written back
to the memory area and to /syspar/mtpconf.
Any changes to the configuration parameters will not take effect until the SS7
controller card is reset using the loadable command ld_mtp.
Example
This example contains sample screens of the menus you will encounter using the
loadable command mtpconf. Each screen is followed by a table containing the
online help information for that particular menu. The first screen you will see in
this example is the MTP Configuration Menu (Figure 3-1). This screen is then
followed by several sub-menu screens: (1) the Layer 3 Route Table screen, (2) the
Link Configuration screen, and (3) the Link Set 1 Route Configuration screen.
At the command prompt (*), enter: mtpconf -c0
Where: -c0 is card 0

-c1 is card 1
The loadable responds with a screen similar to the following:
Figure 3-1 Sample ScreenMTP Configuration Menu: Board Number 0
PN 9110.00616 33
A help screen can be reached online from each field in the MTP Configuration
Menu (see Figure 3-1). The following table contains the information found in
each help screen:
Table 3-2 MTP Configuration Menu Help Information
Field Help Screen Information

Layer 3 General Profile 0 Current Value
1-5 Future Use
Layer 3 DPC Addresss Layer 3 Destination Point Code
L3 Management Priority Layer 3 Management Priorities
Keep-Alive Timer Active YES Keep Alive T imer Active
NO Keep Alive Timer Not Active
Note: The Keep-Alive timer verifies that the
controller card is responsive. If it is active and
expires, the Central will reset the controller card
and execute another download.
Number of Routes Total Number of Routes to Configure
Layer 3 Routes Screen Enter a Y to enter the Configuration Screen.
For a screen sample and help information,
see Figure 3-2 and Table 3-3.
Network SAP (service access Network SAP Profile:
point) Profile
0 Current Value
Other Future Use
Network SAP Link Type Layer 3 Data Link Type: ANSI
CCITT
Network SAP DPC Length Layer 3 Data Link SAP DPC Length:
14 bits CCITT
24 bits ANSI
Link Config. Screen Enter a Y to enter the Configuration Screen.
Number of Link Sets Number of Link Sets:
1 or 2
Link Set 1 Profile Number Link Set Profile Number:
0 For Stand-alone Link Set. Minimum
number of active links 1. C ombined
Link Set ID equals Link Set ID.
1 For 2 links in 1 Link Set. Minimum
number of active links 2. Combined
Link Set ID equals Link Set ID.
Link Set 1 Adjacent DPC Link Set Adjacent Destination Point Code
34 REV 2.1 July 27, 1998


Link Set 1 # of Route IDs Number of Routes to Configure for Link
Set.
Link Set 1 Screen Enter a Y to enter the Configuration Screen.
Layer 3 Route Table Menu
As noted in Table 3-2, if a Y is entered at the Edit Layer 3 Routes (y/n)?

field, the Layer 3 Route Table screen appears as shown here:
Figure 3-2 Sample ScreenLayer 3 Route Table
The table below contains information found in the help screens that can be
accessed from each field of the Layer 3 Route Table:
Table 3-3 Layer 3 Route Table Help Information

Profile Number 0 Our DPC (Up)
1 Adjacent DPC (Down)
Route is adjacent to link.
2 Adjacent DPC (Down)
Route is not adjacent to link.
Signaling Point Type 0 SP without Tranfer Func
1 SP Transfer Point
DPC Address Route Destination Point Code
PN 9110.00616 35

Switch Type Route Switch Type:
ANSI
CCITT
Combined LS ID Route Combined Link ID
The Combined LS ID is a unique ID number
from 0 to 9. This number is used in Link Set
1 and 2 Screens.
Link Configuration Menu
As noted in Table 3-2, if a Y is entered at the Link Config. Screen field,

the Link Configuration Menu screen appears as shown here:
Figure 3-3 Sample ScreenLink Configuration Menu
accessed from each field of the Link Configuration Menu:
Table 3-4 Link Configuration Menu Help Information

Link Active Is Link Active: YES or NO
Link Type Link Type: Serial or PCM
36 REV 2.1 July 27, 1998


68302 SCON Register 68302 SCON Register:
Default value for MVP extracting clocks:
0x31f2
For 64 kbs links MVP receiving clock:
0x31f2
For 64 kbs links MVP transmitting clock:
0x11f2
For 56 kbs links MVP transmitting clock:
0x11b4 (serial only)
See 68302 Manual for Additional Information.
68302 SCM Register 68302 SCM Register:
See 68302 Manual: Default is 0xa280
L2 DLSAP Profile Layer 2 Data Link SAP Profile:
0 Normal ErrorcheckingMode,
CCITT Timers
1 Cyclical Error Checking Mode,
CCITT Timers
2 Normal Error Checking Mode,
ANSI Timers
3 Cyclical Error Checking Mode,
ANSI Timers
L3 DLSAP Profile Layer 3 Data Link SAP Profile:
0 Current Value
1 to 4 Future Expansion
L3 DLSAP LS ID Layer 3 Link Set ID: 1 or 2
L3 DLSAP LS Priority Priority of Link within Link Set: There are
only 2 possible links within the link set.
0 or 1: 0 is the highest priority
L3 DLSAP DPC Address Destination Point Code for Link seen from
Layer 3. Typically, this is the Switch Point
Code.
L3 DLSAP DPC Type Layer 3 Data Link Type:
ANSI
CCITT
L3 DLSAP DPC Length Layer 3 Data Link SAP DPC Length:
14 Bits (CCITT)
24 Bits (ANSI)
PN 9110.00616 37

L3 DLSAP SLC Layer 3 Data Link SAP Signaling Link Test
Code: This number is configured on the
Switch and is used to align Layer 2.
Typical values are 0 or 1.
L3 DLSAP SSF Layer 3 Data Link SAP Sub Service Field:
International
National
Reserved (National)
Link Set 1 Route Configuration Menu
As noted in Table 3-2, if a Y is entered at the Link Set 1 Screen field, the
Link Set 1 Route Configuration Menu screen appears as shown here:
Figure 3-4 Sample ScreenLink Set 1 Route Configuration Menu
38 REV 2.1 July 27, 1998

accessed from each field of the Link Set 1 Route Configuration Menu:
Table 3-5 Link Set 1 Help Information

Combination Link Set IDs Combination Link Set ID numbers are the
Combination Link Set ID numbers defined
in the Layer 3 Route Table. Here, the
Combination Link Set IDs field is used to set
the routing priority through the Link Set.
Priority The LinkSet Priority defines the routing
priority of the Combination Link Set ID
Number.
0 Highest Priority
1 Lowest Priority
A 0 priority in both Link Set 1 and Link Set 2
for the same combination ID means that
both Link SEts share the routing.
The following table contains navigational information for the mtconf loadable:
Control Characters for mtpconf

CTRL L Repaint Screen
CTRL J Skip To Next Column
CTRL K Skip To Previous Column
CTRL B Help For This Field
BS Go To Previous Field
CR Go To Next Field
ESC Exit Loadable
PN 9110.00616 39
3.2.1.1 Initiating a New MTP Download

The loadable ld_mtp is used to trigger a software reset to the SS7 controller card
and start a new download of the configuration parameters from /syspar/mtpconf.
Usage is as follows:
execute: ld_mtp [-b <bno>] [-f] [-y] [-r]
Variable options are described below:
-b < bno > The board number (bno) must be entered on the command line.
-f Use this option to download the configuration parameters from

/syspar/mtpconf. If this option is not entered, the configuration information
already in memory will be downloaded.
-y Start download without asking for confirmation. Leave this option out if
confirmation is desired.
-r Reset SS7CC and download configuration parameters from memory.
40 REV 2.1 July 27, 1998

3.2.2 SS7CC Diagnostic Port

Port 3 on the SS7CC card is used as a diagnostic port. This port controls an
interpreter which works in the same fashion as the MVP Central console
interpreter. The SS7 interpreter features commands to view memory, patch
memory, and set system flags.
Below is a display of the interpreter command set and an explanation of each

function:
302 Resident Commands, PORT 2
date flags h patch ps qlens
resume ver view
date Displays the time and date which is set on the SS7CC card. This date is set
during download from the Central, and cannot be set from the interpreter.
flags Displays and sets the system flags. Below is a list of the available flags.
TRACE_L1 Any value other than 0 will display all messages going into
layer 1 in a hexadecimal format on the diagnostic port.
TRACE_L4Any value other than 0 will display all messages going to

and from layer 4 in a hexadecimal format on the diagnostic port.
Note This flags loadable is similar in function to the flags loadable in the
MVP Central software.
h Displays the SS7CC 302 Resident Commands.
patch <memory address> <desired value> This command replaces the

short value at <memory address> with the value in <desired value>.
Example: patch 0x5000 0x1234

Replaces value at memory location 0x5000 with value 0x1234.
ps Displays all the operating system tasks, their name process IDs (PID), state,
priority (PRI.), stack size (STACK), base address of stack (BASE), and current
stack used (USED).
PN 9110.00616 41
qlens Displays the queue lengths for the layer 4 input queue, layer 4 output
queue, layer 3 input queue, layer 2 input queue, layer 1 input queue, SCC 1
device output queue, and SCC 2 device output queue.
resume <Process ID> Resumes the task indicated by <Process ID>.
ver Displays the version of the mtp-302 file which is currently executing.
view <memory address> Displays values in a hexadecimal format at the

memory location <memory address>.
3.2.3 Debug Message Printouts

Trace flags in the central processor and SS7CC allow messages passed to/from
a given layer to be dumped to the console. The trace flags for the SS7 controller
are described in the preceding section of this document. The trace flags for the
central are installed in the loadable debflags. The new fields in debflags are
described here:
Flag Value Description

ss7_l4_in 0x01 Displays in a hexadecimal format all messages being
passed to layer 4 from layer 3, on controller board 0.
ss7_l4_in 0x10 Displays in a hexadecimal format all messages being
ss7_l4_out 0x01 Displays in a hexadecimal format all messages being
ss7_l4_out 0x10 Displays in a hexadecimal format all messages being
3.2.4 SS7CC Communication Tasks

Each SS7CC card installed in the MVP has a task in the Central to handle all
communications to and from the controller card. This table contains a list of
these task names and the task ID.
Task Name Task Id Description

SS7_0 227 Task for controlling SS7CC card 0
SS7_1 228 Task for controlling SS7CC card 1
42 REV 2.1 July 27, 1998

3.2.5 Maximum Number of SS7 Links

The maximum number of SS7 links that can be configured and run in the MVP
is assigned during the install procedure. Use the loadable command view_cap to
view this information.
3.2.6 MTP Card Statistics

Use the loadable command mtpstats to view statistics and status of the MTP on
a given SS7CC card. Example: mtpstats -b0
3.3 Network User Part Software (TUP and ISUP)

The User Part layer of the SS7 software resides in the MVP Central processor.
This layer interprets and processes the data in an SS7 signaling message. User
Parts supported by the MVP are:
Telephone User Part (TUP)
ISDN User Part (ISUP)
TUP defines the necessary telephone signaling functions for call control in the
SS7 environment (functions such as setting up the call, performing call
supervision, call breakdown to and from the MVP, etc.).
ISUP performs similar functions as TUP using a different format. Although

ISUP is capable of supporting non-voice applications in an Integrated Services
Digital Network (ISDN), the MVP utilizes only the voice applications of ISUP.
Note The bulk of the User Part software resides in the MVP User Part
loadable files tup.e or isup.e (whichever is appropriate). Upon MVP
boot-up, these files must be present in the root directory so that the
User Part software will be loaded. If a User Part file is not found, then
that particular User Part will not be resident and therefore not
operable.
When an SS7 signaling message enters the MVP, it is first stripped down by the
MTP layer on the SS7 controller card until only the Signaling Information Field
(SIF) remains. The MTP passes this SIF data to the SS7 Task running in the MVP
Central OS. The SS7 Task then transfers the data to the appropriate Channel
Task. (Circuit group type messages are also handled by the SS7 Task.)
The signaling message passed from the MTP to the User Part contains a Service
Information Octet (SIO) that declares the User Part type to use in its lower
nibble. The User Part identifier values are shown below:
Telephone User Part = 4
ISDN User Part = 5
PN 9110.00616 43
If an SS7 message is received from the Trunk, the User Part is dictated by the SIO
User Part type previously received in the call. For an originating outdial
message from the Trunk, the User Part selection will be set according to the User
Part Type field in the SS7 User Part configuration file syspar/ss7ch. Additional
information on syspar/ss7ch can be found in Section 3.3.3.2 of this document.
3.3.1 Channel Task

The User Part interface utilizes the Channel Task to receive and transmit
messages from other tasks in the system, mainly the SS7 task and the Polling
Task. The SS7 task handles signaling messages between the SS7 signaling link
and the Channel Task. The Polling Task handles messages between the Channel
Task and the Trunk TSC.
Although the User Part uses the Channel Task message handling mechanism,
the signaling messages are separated from normal channel messages as follows:
If a mail message is from any of the four SS7 tasks, the message is sent to the
SS7 code.
If a mail message is from any of the two Polling Tasks, and the mail
message stimulus indicates that the message is for SS7 signaling, the
message is sent to the SS7 code.
3.3.2 SS7 state tables

The User Part software is designed to use state tables, much like the channel
tables used by the Channel Task. Each state has a table consisting of stimuli,
senders, and functions. When a message is received by the User Part code, the
state table determines what function to call. The called function performs the
necessary actions and also designates the next state.
The stimuli for the User Part state tables are different for TUP and ISUP:
TUP software uses a combination of the 4-bit Heading codes H1, H0.
Heading code H1 resides in the upper nibble and heading code H0 resides
in the lower nibble of the TUP stimulus.
ISUP software conveniently uses an 8-bit message type that acts as the
stimulus.
The User Part state tables are not accessible through an MVP file like the
Channel Task state tables. The User Part tables are hard-coded into the User
Part loadable. The stimulus used by the User Part state tables will be the byte
immediately following the 0xe8 SS7 User Part message flag.
Note The 0xe8 User Part message flag is not entered into the normal
channel tables. This stimulus is detected and parsed in the channel
code prior to the message reaching the channel tables.
44 REV 2.1 July 27, 1998

3.3.3 Modifications to MVP System Files

The following MVP system files are created or modified during SS7 software
installation:
Configuration Files
/syspar/channels
/syspar/ss7ch
Loadable Files
tup.e
isup.e
ccflow.r
ch_flag.r
ld_ss7.r
ss7_flg.r
3.3.3.1 /syspar/channels
The trunk configuration file /syspar/channels contains a new bit (Bit 20 -
0x100000) in the Type field to indicate that the channel is an SS7 trunk. If this bit
is set, all line signaling is communicated over the SS7 link.
3.3.3.2 /syspar/ss7ch
This system file determines the configuration of an SS7 channel. Memory
allocated data structures concerning SS7 User Parts are determined by the
set-up of this file.
The configuration parameters in /syspar/ss7ch are loaded during MVP boot-up.

If any changes are made to this file after the system is up and running, the
loadable command ld_ss7 must be executed before the changes are actually
implemented. Additional information on this command may be found later in
this section.
The file /syspar/ss7ch is created using the coledit editor as defined by the format
shown below. The coledit record number is equal to the trunk number, relative
to zero, for which the configuration is intended.
PN 9110.00616 45
The following table reflects the file format of /syspar/ss7ch:
Field Size Display Description

flag 2 hex Bit defined settings flag
cic 2 decimal Circuit ID code
dpc 1 hex Destination point code
suid 1 decimal User part type
spare 1 decimal Spare
Usage of each field is defined here:
flag The flag field is a 16-bit defined field used to set various features of the SS7
channel. The bits are defined as follows:
Bits Value Description

0 --- not used
thru : :
15 --- not used
cic The cic field contains the CIC code that is contained within the SS7 message and
determines for which trunk the signaling message is intended.
dpc The dpc field determines the destination point code that will be used on an
outdial. This value will be directly placed in the SS7 message routing label.
suid The suid field contains the User Part type that will be used on an outdial. This
value will be placed in the SS7 Service Information Octet. Valid values are:
0 - (TUP) Telephone User Part

1 - (ISUP) ISDN User Part
spare The spare field is an extra 1-byte field that is reserved for future use.
46 REV 2.1 July 27, 1998

3.3.3.3 tup.e & isup.e
Objective These two loadable files contain the core of the code necessary for the SS7 User
Part to operate. All message interpretation, message transmission, and actions
to be executed are contained in these files.
Function To supply the MVP Central with the software for the SS7 User Part layer.
The software uses a state table design, much like the channel tables used by the
Channel Task. As a message is sent to the User Part code, the stimulus and the
task sender (i.e. SS7 Task, Trunk) determine what function will be called.
The called function from the state table dictates the next state the code will
reside in after return of the function.
Usage Not applicable. Make sure that the loadable is bound to the MVP Central OS
prior to boot-up (similar to the loadable command dbminit.e). Only the
applicable executable name (tup.e or isup.e) is required with use of these
loadables. Since the User Part will have different versions, the.r loadable files
may contain varying names, but must be bound to the executable names shown
above.
Example
bind /startup/isup_ccitt.r isup.e MVP-147
Loadable file isup_ccitt.r is replaced by isup_q767.r in the international version.

This file is also bound to the executable file isup.e.
3.3.3.4 ccflow.r
Objective This file includes the process and action commands used for the SS7 User Part.
Descriptions of these process and action commands may be found in Section
3.3.4 and Section 3.3.5 of this document.
PN 9110.00616 47
3.3.3.5 Id_ss7.r
Objective This loadable reinitializes the SS7 User Part. This prevents the MVP from having
to reboot every time an SS7 configuration change is made.
Function This command sets up the SS7 user part configuration for each channel. The
following actions occur when this command is executed:
User Part loadable files entry points are determined.
MVP system file /syspar/ss7ch is loaded into memory.
SS7 User Part memory data structures are allocated.
Usage ld_ss7
Notes An MVP batch containing both tktailor.r and ld_ss7.r may be useful
when reinitializing the Trunk.
The SS7 configuration data is automatically loaded upon system

boot-up and therefore Id_ss7.r does not have to be run if system is
reset.
3.3.3.6 ss7_flg.r
Objective This command enables the system administrator to set various parameters
affecting operation of the SS7 protocol.
Function This command is used to view or modify the various SS7 service features. To
change a parameter, enter the parameter name then enter the parameter value
required. The function of each parameter is described below.
called_num_flag A bit defined flag that involves the called party number
passed in a message. Bit values are:
0 Enables international/national nature of address. If not set, the

nature of address will be subscriber number.
1-15 Spare
calling_line_flag A bit defined flag that involves the calling line identity (CLI)
passed in a message. Bit values are:
0 Enables international/national nature of address. If not set, the

nature of address will be subscriber number.
1 CLI is required on incoming calls.
2-15 Spare
48 REV 2.1 July 27, 1998

dual_seize_flag A value that defines the control scheme used for dual
seizures. The controlling side is determined by the highest point code and the
type of control. Types of control are:
0 No circuit control
1 Odd CIC control
2 Even CIC control
3 Total circuit control
orig_addr_flag A bit defined flag that involves the original called address
(OCA) passed in a message. Bit values are:
0 Enables international/national nature of address. If not set,

the nature of address will be subscriber number.
1 OCA is required on incoming calls.
2-15 Spare
ss7_digit_feed A value that determines how many digits in the called party
number are required before the address is accepted. A value of 0 disables this
feature.
ss7_cot_flag A bit defined flag that involves continuity checks. Bit values are:
0 Check is required on outgoing calls.

1-15 Spare
ss7_extend_iam A bit defined flag that is used to include additional

information with the initial address message on outgoing calls. Bit values are:
0 Calling party ID included.

1-15 Spare
ss7_intl_flag A value that is placed into the SIO Sub-Service field for messages
sent to the MTP. Values are:
0 Set to International Network.

1 Spare
2 National Network.
3 Reserved for national use.
PN 9110.00616 49
ss7_min_addr The minimum number of address digits to receive in order for

the address to be deemed complete.
ss7_log_flag A bit defined flag that enables prints out information when an
event occurs. Bit values are:
0 Transmit Call setup failures

1 Transmit Blocking messages
2 Transmit Reset messages
3 Transmit Circuit group messages
4 Receive Call setup failures
5 Receive Blocking messages
6 Receive Reset messages
7 Receive Circuit group messages
8-15 Spare
view_cirgp_msgs A bit defined flag used to enable viewing of circuit group

messages. Bit values are:
0 View message type only

1 View message type and more information
2-15 Spare
50 REV 2.1 July 27, 1998

3.3.4 Callflow Action Commands
Command Function
SEIZE_TK Used when the Central specifically
requests the Trunk to seize. This
normally occurs when a new call is
being initialized.
ANSWER_TK Used when the Central specifically
requests the Trunk to answer. This
normally occurs when the called party
has answered the MVPs call.
CLEAR_TK Used when the Central specifically
requests the Trunk to clear. This
normally occurs when the other party
has hung-up prior to an MVP hang-up.
RELEASE_TK Used when the Central specifically
requests the Trunk to release. This
normally occurs after the remote party
indicates that it is ready for a new call.
At this point, the MVP should do the
same and make this trunk available for
another call.
COT_TEST Used when the Central specifically
requests the Trunk to perform a test
over the audio path. Since the SS7
signaling link is separate from the
audio path, integrity in both links are
essential for a completed call.
SETUP_COMPLETE Used when the Central indicates to the
Trunk that Call Setup is now complete
and we must now wait for the called
party to answer.
MORE_DIGITS Used when the Central indicates to the
Trunk that more digits have been
received during call setup. This is used
for determining Incomplete Address
time-outs.
SUSPEND_TK Used when the Central indicates to the
Trunk that calls should not be
processed.
RESUME_TK Used when the Central indicates to the
Trunk that the SUSPEND_TK
command should be released.
PN 9110.00616 51
3.3.5 Callflow Process Commands
Command Function Usage Delay

SEIZE_SIG Used to notify the Central that SEIZE_SIG 100 msecs
the Trunk has been seized.
Seized is defined as a state
where the trunk is now
considered as busy and that all
other calls attempting to access
this trunk shall be denied.
ANSWER_SIG Used to notify the Central that ANSWER_SIG 100 msecs
the Trunk has been answered.
Answered is defined as a state
where the trunk has accepted
the call and that MVP
functionality should now
begin.
CLEAR_SIG Used to notify the Central that CLEAR_SIG <cause> 100 msecs
the Trunk has been cleared. Where: <cause> = Reason for
Cleared is defined as a state disconnect.
where the trunk has (This value will vary depending on
disconnected but is not yet the SS7 User Part being used.)
ready for new calls.
TUP simply uses a 0 for
clearing due to a failure and 1
for a normal clearing.
ISUP contains a parameter

field named Cause and it is
this value that is passed in the
cause field.
RELEASE_SIG Used to notify the Central that RELEASE_SIG 100 msecs
the Trunk has been released.
Released is defined as a state
where the trunk is ready to
accept new calls.
COT_STATUS Used to notify the Central of COT_STATUS <status> 100 msecs
the continuity test results for Where: <status> = Continuity
outbound calls. test results.
0 Continuity test failed
1 Continuity test passed
OUTDIAL_SIG Used to notify the Central code OUTDIAL_SIG <buffer> 100 msecs
that an outdial is needed. SS7 Where: <buffer> = Buffer
uses the signaling link to number containing the
initiate the call (as opposed to outdial
non-SS7 channels in which the digits.
trunk performs the outdial via
DTMF tones).
52 REV 2.1 July 27, 1998

Command Function Usage Delay

TIMEOUT_SIG Used to notify the Central that TIMEOUT_SIG <reason> 100 msecs
a time-out has occurred. Where: <reason> = Reason for
time-out
0 Unknown
1 Address incomplete
time-out
3.3.6 Sample Callflows

The following is a flowchart example of an inbound call. When a call comes from
the switch, it is broken apart and processed. This flowchart shows the
breakdown of the inbound buffers.
Figure 3-5 SS7 Inbound Callflow
PN 9110.00616 53
Because SS7 is a stimulus and response type protocol, new callflows, along with
additional commands, are needed so that the User Part software will know what
status the trunk is in and send the appropriate response to the other remote
party. All supervisory trunk signals are sent using the SS7 signaling link instead
of the trunk.
The following are basic examples of how the callflows should be configured for
both SS7 incoming calls and outbound calls.
3.3.6.1 Inbound SS7 call

action 6 /***************** SS7 - ISUP Inbound Callflow *******************/
DIALOUT_REQUEST Idle Idle Dialout
OUTBOUND_RETURN 0x00 0xff Begin
BLOCK Idle Idle Block
UNBLOCK Uncond_block Unblock Unblock

UNBLOCK 0 0xff Unblock
UNCOND_UNBLOCK Cleanup 0xff Cleanup
/* test to make sure buffers recd are not 10 digits */

EQUAL_TO tstbf4 tstbf4 setbf4
/* decision to determine which buffers to load */

EQUAL_TO chk_direct1 Passwd_test chk_calling
/* decision to determining which greeting/prompt to be played */
INVALID_USER Req_acct2 Req_acct2 Gen_access /* Inval# genacces */

INVALID_USER Req_acct3 Req_acct3 clear_acct /* Inval# check Redir#*/
INVALID_USER Req_acct4 Req_acct4 nonvalsub /* account not found */
/* responses from request account by central between Req_acct2 and Req_acct4*/

ILLEGAL_NUMBER Req_acct2 Req_acct4 Invalid_num
SYSTEM_ACCT_ERROR Req_acct2 Req_acct4 Call_fail
DEPOSIT_MODE_FULL Req_acct2 Req_acct4 Val_sub
RETRIEVE_ONLY_LOCKOUT Req_acct2 Req_acct4 User_busy
DEPOSIT_OK Req_acct2 Req_acct4 Val_sub
RETRIEVE_ONLY_OK Req_acct2 Req_acct4 Val_sub
FREE_SUBSCRIBER Req_acct2 Req_acct4 System_md
/* decisions to make sure dont get in loop if 900-000-0000 isnt set up */

GREATER_THAN nonvalsub nonvalsub nonval
LESS_THAN nonvalsub nonvalsub nonval
GREATER_THAN nonvalsub1 nonvalsub1 nonval
LESS_THAN nonvalsub1 nonvalsub1 nonval
/* responses from Central during system mode */

ILLEGAL_PASSWORD System_md Prgm Norm_clear
ENTRY_TIMEOUT System_md Prgm Norm_clear
SYSTEM_ERROR System_md Prgm Norm_clear
ENTRY_ERROR System_md Prgm Norm_clear
CENTRAL_EXIT System_md Prgm Norm_clear
REMOTE_SYS_ERR System_md Prgm Release
SYSTEM_ERROR Dialout Dialend Cleanup
CENTRAL_EXIT Dialout Dialend Cleanup
54 REV 2.1 July 27, 1998

/* decisions for Fax detection */

AUTO_FAX_CHK System_md System_md Rx_CNG
RX_DIGIT7 cngwait cngend Got_CNG
/* NOTE: next 2 lines can be committed out if ring
during fax tone detect is required. However,
If this is done subscribers wont know the
difference from Toll saver and Fax rings. */
/* LESS_THAN cngwait cngwait cngsilent */
/* GREATER_THAN cngwait cngwait cngsilent */
/* decisions for toll saver */

DISABLED Val_sub Val_sub Answer
GREATER_THAN Num_msg Num_msg Answer
/* Timeouts */
BAILOUT_EXP Busy_loop Busy_end Release
BAILOUT_EXP digit_wait digit_wait Call_fail
/* SS7 commands */
RESET_TK Idle Bottom Cleanup /* Reset the trunk */
SEIZE_TK Idle Idle Start /* Seize the trunk */
RELEASE_TK Idle Bottom Release /* Release the trunk */
REMOTE_SYS_ERR Start Bottom Disconn
/* COT test */
START_COT_TEST Idle Idle Cot_idle /* start cot test */
START_COT_TEST Setup digit_wait Cot /* start cot test */
RX_DIGITD COT_start COT_rx COT_detect /*disable Receive high */
EQUAL_TO COT_hilotst COT_hilotst COT_low /*Send 1780 hz tone */
STOP_COT_TEST COT_start COT_tx COT_end /* stop cot test */
/* COT test during blocking states

START_COT_TEST Block Block_end Blk_COT_start /*start cot test*/
RX_DIGITD Blk_COT_start Blk_COT_rx Blk_COT_detect
EQUAL_TO Blk_COT_hilotst Blk_COT_hilotst Blk_COT_low /*Send 1780 hz tone*/
STOP_COT_TEST Blk_COT_start Blk_COT_tx Blk_COT_end /* stop cot test*/
RELEASE_TK Blk_COT_start Blk_COT_end Blk_COT_rel
END_ACTION
process 6
Line_zero: RESET_SIG /* SS7: Trunk has reset */
Cleanup: DISCONNECT 0 0
Begin: TONE_STOP /* turn off any tone generation */
SEND_TO_DSP 0xca 0
SEND_TO_DSP 0xc4 0x08 /* Enable Dsp for Dial tone Detect */
SEND_TO_DSP 0xc4 0x11 /* Enable Dsp for Ring tone Detect */
SEND_TO_DSP 0xc4 0x1a /* Enable Dsp for Busy tone Detect */
SEND_TO_DSP 0xc4 0x23
RX_FMT 0x10 /* enable supervisory decode */
CLEAR_BUFFER 6
INIT_COUNTER 1 COTVAL /* Initialize Counter for cot define */
Idle: WAIT 0 /* Wait for seizure */
Start: INIT_STATS /* enable tkstats */
SEIZE_SIG /* Seize trunk */
Setup: INIT_BAILOUT 25 /* Wait on digits from Central */
digit_wait: WAIT_BUFFS 7 /* wait for numbers from Central */

/* Buff1 - Called party number Buff5 - Generic Address
Buff2 - Calling party number Buff6 - Information
Buff3 - Original called number Digit 15 Redirection Counter
Buff4 - Redirecting Number Buffer 7 spare */
tstbf4: CMP_DIGIT 0xb 0xff 4 /*is buff4 11 digits, yes goto setbf4 */
GO_TO tstbf3 /*NO, go test buffer 3 */
setbf4: LSHIFT_BUF 4 1
PN 9110.00616 55
GO_TO setdigits /*NO, goto setdigits */
setdigits: SET_NUM_DIGS 1 /* set number of digits for Called */
SET_NUM_DIGS 2 /* set number of digits for ANI */
/* SET_NUM_DIGS 3 set number of digits for Orig Called */
SET_NUM_DIGS 4 /* set number of digits for Redirection#*/
chk_direct1: COMPARE_BYTE 0xff 7 6 /*redir cnt not present goto chk_calling*/
chk_direct2: COMPARE_BYTE 0 7 6 /*redir cnt equal to 0 goto chk_calling*/
SEND_ANI 2 /* send Calling party # to Central */
Passwd_test: COMPARE_BUFS 2 3 /* See if numbers are the same */
GO_TO reqact3 /* Call is a deposit goto reqact3 */
clear_acct: SEND_TO_CENTRAL 0xd0 0 0 /* Clear request account status */
GO_TO reqact4 /*OCN is invalid goto reqact/chk redir#*/
Gen_access: SEND_TO_CENTRAL 0xd0 0 0 /* Clear request account status */
GO_TO Val_sub /*Goto val_sub and play gen greeting */
chk_calling: SEND_CALLTYPE 21 0 /* Phone number is direct or Gen Access*/
reqact2: REQUEST_ACCT 2 /* request for CallingpartyDirect call?)*/

Req_acct2: WAIT 200 /* If CN is invalid goto Gen_access */
GO_TO Call_fail
reqact3: REQUEST_ACCT 3 /* request for Orig Called # */
Req_acct3: WAIT 200 /* If OCN is invalid goto copybuf4_1 */
GO_TO Call_fail
reqact4: REQUEST_ACCT 4 /* request for Redirected Number */
Req_acct4: WAIT 200 /* If RN is invalid goto Invalid user */
GO_TO Call_fail
Cot_idle: GOTO_SUB COT_start /* Rechecks: Loop back audio */

GO_TO Idle
Cot: GO_TO Setup
COT_start: SEND_TO_DSP 0xc4 0x76 /* Enable Receive High: 2010 Hz */
COT_rx: WAIT 100 /* (>2secs) Arbitrary wait period */
GO_TO Call_fail /* Somebody had to timeout by now */
COT_detect: SEND_TO_DSP 0xc4 0x06 /* Disable Receive High: 2010 Hz */
COT_hilotst: COMPARE_COUNTER 1 COTVAL
COT_high: LOOPBACK
GO_TO COT_tx
COT_low: TONE_SEND 0xc0 0xa /* Send COT Low: 1780 Hz */
COT_tx: WAIT 30
COT_end: TONE_STOP
RET_SUB
Clr_busy: INIT_BAILOUT 180 /* 2-3 minute bailout Q.118 */

Busy_loop: TONE_SEND 0xc0 4 /* Busy */
WAIT 2
TONE_STOP
WAIT 3
REPEAT Busy_loop 10 /* 5 seconds */
WAIT 250 /* Wait 25 seconds */
Busy_end: GO_TO Busy_loop
/**** The following nonvalsub will build mailbox 900-000-0000, go back to

request account. The account must be set up as a secure depoist only
with a secondary ID that can be accessed with *2. The 2nd ID will
allow the administrator to log into the mailbox and record a greeting.
Finally, the mailbox should be set up with an account status 0x220.
This is a free subsciber record with announce and disconnect. ***/
nonvalsub: COMPARE_BYTE 0x9a 0 4 /* test to see if were in a loop */
56 REV 2.1 July 27, 1998

nonvalsub1: COMPARE_BYTE 0xaa 1 4 /* final test to see if were in a loop*/

GO_TO Busy_loop /* nobody set up record 900-000-0000 */
nonval: DISCONNECT 1 0
LOAD_BUFFER 0x9 0xff 4
loadnonval: LOAD_BUFFER 0xa 0xff 4
REPEAT loadnonval 8
GO_TO reqact4
Val_sub: TOLL_SAVE_TEST /* test for toll saver status in COS */

Num_msg: NUM_MSG_TEST 0 0 /* no new messages go to Answer */
Toll_save: RX_FMT 1 /* otherwise, enable DTMF & play */
CLEAR_BUFFER 1 /* clear buffer containing MB# */
TONE_SEND 0xc0 3
WAIT 20
TONE_STOP
WAIT 30
REPEAT Toll_save 1
Answer: ANSWER_SIG /* SS7: Answer signal */
System_md: SYSTEM_MODE 0
cont_sys_mode: SYSTEM_MODE 2
/* testing for Fax CNG tones */

Rx_CNG: SEND_TO_DSP 0xc4 0x02 /* Disable ring & dialtone detection */
SEND_TO_DSP 0xc4 0x54
SEND_TO_DSP 0xca 0
RX_FMT 0x10
cngwait: CMP_DIGIT 0 0xff 1 /*did we generate ring for toll saver*/
TONE_SEND 0xc0 0x03 /* yes, Send 2 seconds of ring */
cngsilent: WAIT 20
TONE_STOP
cngend: WAIT 30
DEPOSIT_TYPE 0
GO_TO cont_sys_mode
Got_CNG: DEPOSIT_TYPE 1
GO_TO cont_sys_mode
Prgm: NO_OP
/* ISUP Clearing Causes:

1 - Unallocated number 21 - Call rejected
16 - Normal clearing 27 - Destination out of service
17 - User busy 28 - Address incomplete
18 - No user responding 31 - Unspecified */
Invalid_num: CLEAR_SIG 1 /* SS7: Unallocated/Invalid number */

GO_TO Busy_loop
Norm_clear: CLEAR_SIG 16 /* SS7: Normal clearing */
GO_TO Clr_busy
User_busy: CLEAR_SIG 17 /* SS7: User is busy */
GO_TO Busy_loop
Call_fail: CLEAR_SIG 21 /* SS7: Call failure */
GO_TO Busy_loop
Illegal_num: CLEAR_SIG 28 /* SS7: Incomplete address */
GO_TO Busy_loop
Release: RELEASE_SIG /* SS7: Send release signal to link */

Disconn: DISCONNECT 1 0
GO_TO Begin
Dialout: INIT_STATS /* enable tkstats for outdial */

Dialend: SWITCH_TO_OUT /* goto outbound line process */
Bottom: GO_TO Begin
Blk_COT_start: TONE_STOP
RX_FMT 0x10
SEND_TO_DSP 0xc4 0x76 /* Enable Receive High: 2010 Hz */
PN 9110.00616 57
Blk_COT_rx: WAIT 100 /* (>2secs) Arbitrary wait period */

GO_TO Block_loop /* Somebody had to timeout by now */
Blk_COT_detect: SEND_TO_DSP 0xc4 0x06 /* Disable Receive High: 2010 Hz */
Blk_COT_hilotst: COMPARE_COUNTER 1 COTVAL
Blk_COT_hi: LOOPBACK
GO_TO Blk_COT_tx
Blk_COT_low: TONE_SEND 0xc0 0xa /* Send COT Low: 1780 Hz */
Blk_COT_tx: WAIT 30
Blk_COT_end: TONE_STOP
GO_TO Block_loop
Blk_COT_rel: RELEASE_SIG
DISCONNECT 1 0
GO_TO Block_loop
Uncond_block: RESET_SIG
DISCONNECT 1 0
Block: OUT_OF_SERV_SIG 0 /* SS7: Tk out-of-service signal */
Block_loop: TONE_SEND 0xc0 4
WAIT 2
TONE_STOP
WAIT 3
Block_end: GO_TO Block_loop
Unblock: IN_SERV_SIG 0 /* SS7: Tk in-service signal */
GO_TO Cleanup
/********* EOC for callflow 6 ********/
58 REV 2.1 July 27, 1998

3.3.6.2 Outbound SS7 call

process 16
Begin: INIT_BAILOUT 45 /* give ss7 45 secs to work */
SEIZE_SIG /* ss7 sieze tk */
INIT_COUNTER 4 DIGS /* load Spec. digits to outdial */
INIT_COUNTER 1 BILLCD /* load billing info from define */
RX_FMT 0x10 /* supervisory format */

WAIT_BUFFS 7
/* testing for proper digit loading */
DIGStst: COMPARE_COUNTER 4 12 /*must outdials be 10 or 11 digits */
dig7tst: CMP_DIGIT 0x7 0xff 1 /*NO, buff=7digs, yes goto dialbuf1 */
dig10tst: CMP_DIGIT 0xa 0xff 1 /*YES,buff=10digs,yes goto add_dig1 */
dig11tst: CMP_DIGIT 0xb 0xff 1 /*YES,buff=11digs,yes goto add_dig1 */
digfftst: COMPARE_COUNTER 4 0xff /*YES,buff1 can be varible */
GO_TO Done_bad30 /*NO, buff1 can not be varible */
add_dig1: LOAD_BUFFER 0xa 0x5 1 /*make sure 1 in 1-800 is cleared */

STRIP_NUM 1 0xa
tstDIGS: COMPARE_COUNTER 4 10 /*Are outdials restricted to 10digs */
LOAD_BUFFER 0x1 5 1 /* add 1 to buffer to dial */
tstBC: COMPARE_COUNTER 1 0xff /* Are billing codes enabled */
tstBC1: COMPARE_COUNTER 1 1 /* If 1 billing cd used goto billcd1 */
GO_TO Done_bad33
billcd3: LOAD_BUFFER BC3OPR 3 1 /* Load billing codes */
billcd2: LOAD_BUFFER BC2OPR 4 1
billcd1: LOAD_BUFFER BC1OPR 5 1
dialbuf1: SET_NUM_DIGS 1 /* justify number of digits to dial */
OUTDIAL_SIG 1 /* SS7: buffer 1 has outdial number */
Setup: WAIT 250 /* wait for further SS7 instruction */
GO_TO Done_bad4 /* Exit bad */
cot_test: SEND_TO_DSP 0xc4 0x6e /* SS7: Enable 2-wire 1780 Hz detect */
TONE_SEND 0xc0 0xa /* SS7: 2-wire 1780Hz COT tone */
cot_wait: WAIT 2 /* give continuity 200msecs to pass */
COT_STATUS_SIG 0 /* continuity test failed */
GO_TO cot_cleanup
cot_passed: COT_STATUS_SIG 1 /* continuity test passed */
cot_cleanup: SEND_TO_DSP 0xc4 0x06 /* SS7: Disable 2-wire 1780 Hz detect*/
TONE_STOP
End_setup: GO_TO Setup /* wait for address complete */
det_supv: WAIT 1
System_md: SYSTEM_MODE 0
System_md1: SYSTEM_MODE 3
Prgm: NO_OP
GO_TO Done
Clear: CLEAR_SIG 16 /* SS7: Trunk Normal clear signal */

Rel_wait: WAIT 250 /* wait for other party to release */
Release: RELEASE_SIG /* trunk is releasing */
Reset: SWITCH_TO_IN
Uncond_block: RESET_SIG
DISCONNECT 1 0
OUT_OF_SERV_SIG 0
Uncond_loop: TONE_SEND 0xc0 4
WAIT 2
TONE_STOP
WAIT 3
Uncond_end: GO_TO Uncond_loop
Unblock: WAIT 1
PN 9110.00616 59
IN_SERV_SIG 0
SWITCH_TO_IN
/* From this point to the End Of Callflow (EOC) let no ACTIONS interrupt */
Done: DISCONNECT 1 0 /* good outdial */
GO_TO Clear
Done_ok0: DISCONNECT 1 0 /* good outdial */
GO_TO Release
Done_bad: DISCONNECT 0 0 /* bad outdial repeat based on COS */
GO_TO Clear
Done_badr: DISCONNECT 2 0 /* bad outdial, repeat ASAP */
GO_TO Clear
Done_badr7: DISCONNECT 2 0 /* bad outdial due ss7,repeat ASAP */
GO_TO Release
Done_badnr: DISCONNECT 3 0 /* bad outdial, NO repeats */
GO_TO Clear
/* (0-9) Exit conditions due to SS7 */

Done_bad0: ERROR_MSG 3 0x16 0 /* Got SS7 reset condition */
DISCONNECT 2 0 /* repeat ASAP */
GO_TO Reset
Done_bad1: ERROR_MSG 3 0x16 1 /* Got SS7 Clear condition */
GO_TO Done_badr /* repeat */
Done_bad2: ERROR_MSG 3 0x16 2 /* Got onhook before Setup completio*/
GO_TO Done_badr7 /* repeat */
Done_bad3: ERROR_MSG 3 0x16 3 /* Got onhook before Call Completion*/
Done_bad4: ERROR_MSG 3 0x16 4 /* SS7 setup timeout more than 25sec*/
Done_bad5: ERROR_MSG 3 0x16 5 /* SS7 possible glare condition */
/* (10-19) Exit conditions due to Supervision tones or inproper line states */

Done_bad10: ERROR_MSG 3 0x16 0x10 /* detected a busy within 3 secs */
Done_bad11: ERROR_MSG 3 0x16 0x11 /* busy detect before display data */
Done_bad12: ERROR_MSG 3 0x16 0x12 /* busy detect before call completio*/
Done_bad13: ERROR_MSG 3 0x16 0x13 /* NO-offhook after supervision tone*/
GO_TO Done_badr /* go repeat outdial */
/* (20-29) Exit conditions due to bailouts */

Done_bad20: ERROR_MSG 3 0x16 0ax20 /* bailout exp (find the problem) */
/* (30-39) Exit conditions due to incorrect number to dial */

Done_bad30: ERROR_MSG 3 0x16 0x30 /* Incorrect # of digits to dial */
GO_TO Done_badnr /* NO more Outdials */
Done_bad31: ERROR_MSG 3 0x16 0x31 /* Invalid NPA Code */
Done_bad32: ERROR_MSG 3 0x16 0x32 /* Digit 8 coded incorrectly */
Done_bad33: ERROR_MSG 3 0x16 0x33 /* Invalid billing code digits */
GO_TO Done_badnr /* No more Outdials */
/********* EOC for callflow 16 ********/
60 REV 2.1 July 27, 1998

APPENDIX
A
SS7 LOOPBACK TEST PROCEDURE
This appendix contains a loopback test for the SS7 option (006.1356 or 189.1506)
used in MVP terminals. You will find the information arranged in the following
sections:
Equipment Required
System Setup
Test Procedures:
Serial Link Check
PCM Link Check
A.1 Equipment Required
1 or 2 SS7 loopback connectors (106.1469)

An MVP3 system with T1 or E1 line interface cards, and SS7 software
support installedmtp-302 file in root directory. (This could be a system
drive specifically configured for these tests or the customer drive.)
A modem cable (170.1594) and null modem cable (176.1076) to connect to
the SS7 diagnostic port, or a VDT cable (170.1593).
A.2 System Setup
For Serial Loopback RS530/RS449/V.35

1. Jumper the SS7 Translator (140.1970) for RS530/449 (all jumpers in) or V.35
(all jumpers out). For more information, see Section 2.2.
2. Jumper the ASM Board (140.1919) and switches as follows:
PN 9110.00616 61
RS530/449 V.35
E1 out out
E2A and E2C out out
E2B in in
E3, E4, E5, E6 A B
E7 ABCD out out
S5, S6, S9, S10 open closed
S7, S8 open open
S1, S3 open open
S2, S4 closed closed
3. Install the following jumpers (140.2004) for pcbs (126.2067):
JR3, 16, 17, 18, 19, 21, 23, 34, 47, and JR63.
Note For 136.1906 pcbs, JR62 is also installed. Refer to 140.2004 JL Rev C or
later.
4. Install the ASM (140.1919) onto the CPU (140.2004) and install the rest of the
SS7 kit by following the hardware install procedure from step 4 of section
2.6 of the reference manual.
5. When all has been installed, power up the MVP.
A.3 Test Procedures
This section contains the procedures for testing both Serial and PCM links.
A.3.1 Serial Link Check
1. Connect the extra VDT to the SS7 diagnostic port, J39, with the null modem
cable.
2. Attach the loopback connectors (106.1469) to J25 and J26. If only one
loopback connector is being used put it on J25 and then move it to J26 to test
the second link.
Note The index mark on the 50 pin cable from the SS7 translator goes to the
first SS7 link.
62 REV 2.1 July 27, 1998

3. When the MVP has booted, type mtpconf and select controller 0.
Modify the following SS7 parameters for Link 0 and Link 1.
Link Active 1=(Link Active)

Link Type 1=(Serial Interface)
68302 SCON Reg 0x1340
68302 SCON Reg 0xa280
Press Esc to exit the menu. Save when prompted. Return to the command
prompt when you have finished.
4. Press the reset button on the SS7 CPU.
Note The Watchdog switch on the SS7 CPU must be enabled. The console
will display an SS7 error. The SS7 CPU RUN LED will flicker as it is
downloaded with the SS7 program and parameters.
5. At the diagnostic screen, type preptest. If messages are scrolling on the

screen, ignore them and continue typing.
6. To activate the Serial port loopback, Type looptest 0. At the loopback
hardware question, select y. If the test is running successfully, a loop
test passed message should appear on the diagnostic terminal within
15 seconds; otherwise, a failure message should appear.
A.3.2 PCM Link Check
1. Type mtpconf and select controller 0. Modify the following SS7

parameters for Link 0 and Link 1.
Link Active 1 (Link Active)

Link Type 2 (PCM Interface Common Channel Signaling)
68302 SCON Reg 0x3340
68302 SCM Reg 0xa280
Press Esc to exit the menu. Save when prompted. Return to the command
prompt when you have finished.
2. Edit the /syspar/config file to specify the Common Channel Signaling source
and PCM time slot. CCS0 is the first link of the first SS7 card and CCS1 is
the second link of the first SS7 card. CCS0:x routes channel x of the span to
the first link, and CCS1:y routes span channel y to the second link.
PN 9110.00616 63
Example
CEPT Interface cards
TK_DIGITAL:0 T1:0 CCS0:1TK_REDUNDANT:1 ESF:1 B8ZS:1

TK_DIGITAL:2 T1:0 CCS1:8TK_REDUNDANT:1 ESF: 1 B8ZS:1
where: span 0, time slot 1 connects to CCS0

span 2, time slot 8 connects to CCS1
Save the /syspar/config file and run ccdigtk.

3. Power down the MVP and move the SS7 CPU. Remove the ASM (140.1919)
from the CPU and reconfigure the jumpers and switches as indicated
below:
E1 in
S1, S3 closed
S2, S4 open
4. Re-install the ASM (140.1919) into slot 6 on the SS7 CPU. Power up the
MVP again. Toward the end of the boot up sequence, the SS7 CPU RUN
LED will flicker as it is downloaded with the SS7 program and parameters.
5. Flip the loopback switches on the T1/CEPT interface cards span 0, and span
2 to loopback. (Shelves A and B, slot 1)
6. At the diagnostic screen, type preptest. If messages are scrolling on the
screen, just ignore them and continue typing.
7. To activate the PCM channel loopback, type looptest 0. At the loopback
hardware question, select y. If the test is running successfully, a loop
test passed message should appear on the diagnostic terminal within 15
seconds; otherwise, a failure message should appear.
8. Substituting looptest 1, repeat step 7 to test the second PCM channel.
64 REV 2.1 July 27, 1998

A.4 MVP SS7 Loopback Connector
The following tables show the pin configurations of the Male D-25 Connector
and the Male V.35 Connector.
Pin to Pin of Same D-25 Pin to Pin of Same V.35

Connector Connector
2 .................... 3 P................. R
4 .................... 5 C ................ D
8 .................... 20 F................. H
9 .................... 11 X ................W
10 .................... 23
13 .................... 19
14 .................... 16 S ................. T
17 .................... 24 V ................ U
Male D-25 Connector Male V.35 Connector
PN 9110.00616 65
GLOSSARY
ANSI American National Standards Institute
ASM Application Specific Module
CCITT Consultative Committee on International Telegraphy and Telephony
CPU Central Processing Unit
DSP Digital Signal Processor
ISUP Integrated Services Digital Network (ISDN) User Part
MTP Message Transfer Part
NIC Network Interface Card (CPU302 w/SS7 ASM). Also called the SS7 Control
Card (SS7CC).
PROM Programmable Read-Only Memory
SIF Signaling Information Fieldthe portion of an SS7 message that is passed

from the MTP layer on the SS7 control card to the User Part software in the
central OS.
SIO Service Information Octet - a value in the SIF of an SS7 signaling message
specifying the User Part type (TUP=4; ISUP = 5).
SS7 Signaling System Number 7
SS7CC SS7 Control Card (CPU302 w/ASM). Also known as Network Interface
Card, or NIC.
TSC Time Space Controller
TUP Telephone User Part
PN 9110.00616 67
INDEX
A mtpconf, 33
action commands, 51 mtpstats, 43
tktailor, 31, 48
C view_cap, 43
cabling, 17 loopback test, 61
callflows, 2, 51
ccdigtk, 30 M
ccflow.r, 47 message transfer part (MTP)
channel task, 44 overview, 32
common channel signaling (CCS), 1, 16, 30 statistics & status, 43
configuration files message transfer part (MTP), 2
/syspar/channels, 45 mtpconf, 63
/syspar/config, 30, 63
/syspar/mtpconf, 33, 40 N
/syspar/ss7ch, 44, 45, 48 network interface card
/syspar/t1, 31 configuration parameters, 33
connectors overview, 7
male D-25 and male V.35, 65 network interface card, 1
RS-449, 24
RS-530, 25 P
V.35, 26 pcm link, 61
CPU302, 7, 8, 20 polling task, 44
process commands, 52
D
debug messages, 42 S
diagnostic port, 41 sample inbound, 54
digital_tk, 30 sample outbound, 59
serial communication controllers (SCCs), 7
I serial link, 7, 17, 30, 61
installation procedures, hardware service information cctet (SIO), 43
, 17 signaling information field (SIF), 43
PCM configuration, 18 SS7 ASM, 7
serial configuration, 19 SS7 control card (SS7CC), 7
integrated services digital network (ISDN), 43 SS7 links, maximum number of, 43
integrated services user part (ISUP), 2 SS7 overview, 1
isup.e, 47 SS7 poll task, 31
isup_ccitt.r, 46, 47 SS7 task, 43, 44, 47
isup_q.767.r, 47 SS7 translator, 14
ss7_flg, 48
L SS7CC communication tasks, 42
loadable commands state tables, 44
debflags, 42 system flags, 41
Id_ss7, 48
ld_mtp, 33, 40
PN 9110.00616 69
T
T1/CEPT interface card, 14, 29, 64
telephone user part (TUP), 2, 32
trunk.ares, 32
TSC poll task, 31
tup.e, 43, 47
U
user part software, 2, 32, 43
70 REV 2.1 July 27, 1998

SS7 Technical Reference-Glenayre

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

SS7 Technical Reference-Glenayre

Uploaded by

Copyright:

Available Formats

Copyrights

1997 Glenayre Electronics, Inc.

Glenayre is a registered trademark of Glenayre Electronics, Inc.

This document is written and published by Glenayre Atlantas Technical

Glenayre Electronics, Inc. assumes no responsibility for errors in this document,

Address all comments and requests regarding this document to:

Tel: (770) 283-1000

D OCUMENT C HANGE R ECORD

1.0 25 October 1995 Original.

1.1 2 May 1996 Deleted all references to MVP-E.

2.1 27 July 1998 Corrected PCM/Serial Connection directions, section 2.6.

Documentation Change Request Form

Use a copy of this form to report documentation errors and/or suggested

Description of error or suggested improvement:

Recommended Priority: _______

Change requested by:

Send completed form to:

Glenayre Electronics, Inc.

iv REV 2.1 Mar. 23, 1998

2. SS7 HARDWARE DETAIL .................................................................................................................. 7

3. SOFTWARE CONFIGURATION .......................................................................................................29

3.2.1 Configuring the Network Control Card.................................................................................33

A. SS7 LOOPBACK TEST PROCEDURE ............................................................................................61

vi REV 2.1 July 27, 1998

Additional information on SS7 and Common Channel Signaling (CCS) can be

1.1.1 SS7 Overview

, or CCS). SS7 allows the MVP to be connected to the Advanced Intelligent

1.1.2 SS7 Call Flow Description

2 REV 2.1 July 27, 1998

1.2 Getting Technical Assistance

To contact Glenayre Electronics Technical Support call or write:

Glenayre Electronics, Inc.

1.3 Address for Repairs

United States Glenayre Electronics, Inc.

Canada Glenayre Electronics, Inc.

United Kingdom Glenayre Electronics, Inc.

4 REV 2.1 July 27, 1998

1.4 Precautions for Handling Removable Assemblies

SS7 HARDWARE DETAIL

2.1 Network Interface Card

Part Number 140.2004 - NIC module (CPU302 w/SS7 ASM)

Location Shelf C, any available slot

Figure 2-1 SS7 Network Interface Card (PCB 136.1906)

8 REV 2.1 July 27, 1998

The following jumpers are normally installed on PCB 136.1906:

The default settings are as follows:

Figure 2-2 SS7 Network Interface Card (PCB 126.2067)

10 REV 2.1 July 27, 1998

Table 2-2 CPU302 Jumper Configuration (PCB 126.2067)

2.1.2 SS7 ASM

J3 provides interconnect with CPU302 for communication of internal data,

J4 provides interconnect between the ASM and ASM Translator through

Note There could be an exception to the illustration in Figure 2-3. In some

Jumpers and switches must be set as shown in the following illustration:

Figure 2-3 SS7 ASM

12 REV 2.1 July 27, 1998

Table 2-3 SS7 ASM jumper Configuration

REF DEFAULT DESCRIPTION

2.2 SS7 Translator

Part Number 140.1970

Location Shelf C, in rear of same slot as Network Interface Card

Connectors The ASM Translator contains the following connectors:

14 REV 2.1 July 27, 1998

Figure 2-4 SS7 Translator