CXTool

User Guide

Part Number: 3008M300-004

Date: October 2002

3008M300-004
CXTool User Guide

PROPRIETARY NOTICE

This publication contains information proprietary and

confidential to Memotec Inc. Any reproduction, disclosure or
unauthorized use of this publication is expressly prohibited
except as Memotec Inc. may otherwise authorize in writing.

Memotec Inc. reserves the right to make changes without

notice in product or component design as warranted by
evolution in user needs or progress in engineering or
manufacturing technology. Changes that affect the operation of
the unit will be documented in the next revision of the manual.

Copyright © 2002 Memotec Inc.

All brand names and product names used in this manual are
trademarks, registered trademarks, or trade names of their
respective holders.

Printed in Canada

Memotec Inc.
600 McCaffrey Street
Montreal, Quebec H4T 1N1
Canada

Tel.: (514) 738-4781

FAX: (514) 738-4436
Website: http://www.memotec.com

2 3008M300-004

CXTool User Guide
CONTENTS
1 OVERVIEW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 1-5
CONTENTS . . . . . . . . . . . . . . . . . . . . . . . . . cfg TOC 11
2 GETTING STARTED . . . . . . . . . . . . . . . . . . cfg 2-21
3 CXTool USER INTERFACE . . . . . . . . . . . . . . . . . cfg 3-25
4 GENERAL CONFIGURATION . . . . . . . . . . . . . . . cfg 4-37
5 CONFIGURING HARDWARE . . . . . . . . . . . . . . . cfg 5-43
6 CONFIGURING DRIVERS . . . . . . . . . . . . . . . . . . cfg 6-55
7 CONFIGURING VOICE . . . . . . . . . . . . . . . . . . . . cfg 7-71
8 CONFIGURING ATM . . . . . . . . . . . . . . . . . . . . . cfg 8-115
9 CONFIGURING FRAME RELAY . . . . . . . . . . . . cfg 9-139
10 CONFIGURING IP . . . . . . . . . . . . . . . . . . . . . cfg 10-167
11 CONFIGURING ISDN AND QSIG . . . . . . . . . cfg 11-197
12 CONFIGURING T1/E1 . . . . . . . . . . . . . . . . . . cfg 12-217
13 CONFIGURING SNA . . . . . . . . . . . . . . . . . . . cfg 13-237
14 CONFIGURING ASYNCHRONOUS PAD . . . cfg 14-255
15 CONFIGURING X.25 . . . . . . . . . . . . . . . . . . . cfg 15-271
16 CONFIGURING IPX . . . . . . . . . . . . . . . . . . . . cfg 16-307
17 CONFIGURING MLPPP . . . . . . . . . . . . . . . . . cfg 17-315
18 CONFIGURING BRIDGING . . . . . . . . . . . . . . cfg 18-321
19 HDLC, BISYNC, AND BRI . . . . . . . . . . . . . . . cfg 19-333
3008M300-004
CXTool User Guide
CONTENTS . . . . . . . . . . . . . . . . . . . . . . . . pri TOC-339
20 PRIMER OVERVIEW. . . . . . . . . . . . . . . . pri 20-347
21 PREPARING TO CONFIGURE . . . . . . . . . . . . pri 21-353
22 TELEPHONY . . . . . . . . . . . . . . . . . . . . . . . . . . pri 22-357
23 INTRODUCTION TO ATM . . . . . . . . . . . . . . . . pri 23-365
24 INTRODUCTION TO FRAME RELAY . . . . . . . pri 24-375
25 INTRODUCING IP . . . . . . . . . . . . . . . . . . . . . . . pri 25-381
26 INTRODUCING ISDN . . . . . . . . . . . . . . . . . . . . pri 26-389
27 INTRODUCTING T1 AND E1 . . . . . . . . . . . . . . pri 27-397
28 INTRODUCING SNA . . . . . . . . . . . . . . . . . . . . pri 28-405
29 INTRODUCING ASYNC PAD . . . . . . . . . . . . . . pri 29-411
30 INTRODUCING X.25 . . . . . . . . . . . . . . . . . . . . . pri 30-415
31 INTRODUCING IPX . . . . . . . . . . . . . . . . . . . . . pri 31-419
32 INTRODUCING MLPPP . . . . . . . . . . . . . . . . . . pri 32-427
33 INTRODUCING BRIDGES . . . . . . . . . . . . . . . . pri 33-431
34 INTRODUCING HDLC, BISYNC, AND BRI . . . pri 34-437
User Guide INDEX. . . . . . . . . . . . . . . . . index 483
TOC-3
CXTool User Guide

TOC-4 3008M300-004
 1 OVERVIEW

CXTool is a Windows-based tool for configuring Memotec CX

products. Memotec’s CX800, CX900e, CX950, CX960,
CX1000e, and CX2000 can all be managed from a PC running
CXTool. Using CXTool, their configuration files may be
created and revised, and then loaded either through the network
or by direct connection to the device.

3008M300-004 1-5
CXTool User Guide
1.1 Using CXTool
CXTool configures CX devices with values that the user enters
in a series of dialog boxes. To arrive at the configuration
needed by the network the user can usually accept the default
values that are provided. Of course, other values may be
required and these can be entered directly where they are
required.
CXTool’s guided configuration leads through the configuring
steps with ranges of appropriate values, and prompts to
configure related objects. When an inappropriate value is typed
in, the user is informed either immediately or when the page is
completed.
When the configuration values are chosen, they need to be
loaded to the device. This can be done by means of a complete
load of all parameters to the device. However, CXTool
provides a quicker method for use when the configuration
involves only updates to certain parameters. To update only
certain parameters, Dynamic Mode may be used. See
Chapter 4.3 Dynamic Mode.
1.1.1 Friendly and Logical
The user is not required to know each and every step in the
configuration of a particular service in advance. There are
internal verification and validation processes that look after
this. Consequently, when an object is configured CXTool
prompts the user to configure supporting objects if they have
not yet been configured.
For instance, if VoIP services are configured without
configuring the IP port, CXTool prompts the user to configure
the IP port.
1-6
With Dynamic Mode turned on it is possible to implement a
configuration change without sending a full load to the device
and then rebooting. It is logical to be able to make an
adjustment to certain parameters without requiring a system
shutdown. The details are in Chapter 4.3 Dynamic Mode.
1.1.2 CXTool Features
CXTool is a Windows-based, configuration tool. It is
engineered specifically to configure Memotec’s CX family of
telecommunications products. Configuring telecom devices has
never been more straightforward.
With CXTool all configuration items are displayed on pages.
For the user, the result is a step by step process. By selecting
values from drop down lists and filling in dialog boxes,
parameters can be set, existing settings can be verified and
revised, and completely new settings can be added.
The graphical user interface (GUI) allows complete network
configurations to be developed quickly and easily. Most ports
and routing circuits can be configured using the default values
shown in the dialog boxes, or with only minor customization.
The key features of CXTool include:
3008M300-004

• The CXTool GUI is intuitive and user-friendly. Navigation
panels allow easy and unrestricted movement between many
levels of configuration.
• Configuring wtih the Learn Harware option, CXTool detects the
current hardware configuration and software version installed in
the selected device.
• Validation and verification functions reduce the possibility of
creating of an invalid configuration.
• CXTool can be used with Windows 95, Windows 98,
Windows Me (Millennuim Edition), Windows NT (Version 4),
and Windows 2000.
(For details, see “System Requirements” on page 2-22.)
1.1.3 Online Help for CXTool
Online help in HTML format is fully integrated with CXTool.
The help system is module-specific, fully indexed, and
includes search features. For example, when a module is
selected and then the Help button is clicked, information
related to the configuration fields of that module are displayed.
Each CXTool window, even if it has several tabs, has only one
Help button. The Help button opens the help system browser at
the appropriate description for the object being configured.
A complementary aid for reading and controlling mibs, called
Command Line Help, is also provided.
1.2 Prerequisites to Using CXTool
While the CXTool application is straightforward to use, the
environment in which the CX devices operate is much less so.
3008M300-004
1 OVERVIEW
Because of this, users of CXTool are assumed to be
experienced. This document is not a guide to the issues of
networking and internetworking.
1.3 Organization of This Guide
The CXTool User Guide has two sections.
• CXTool Configuration Companion is written for users who are
knowledgeable about the networking environment and who
have field experience in managing a digital network and its
protocols. Its chapters describe in detail the installation of
CXTool, how it is used, and the configuration of CX devices.
• CXTool Primer provides an introduction to the many protocols
that are managed by CXTool. It is intended to be a primer for
someone needing a place to start when approaching an
unfamiliar protocol, and to be a refresher for someone returning
to a protocol after an absence. Its chapters include an overview
of the CX configuration process and there are chapters giving a
perspective of each protocol.
1.3.1 Abstracts of Section One
The Chapter 1 OVERVIEW This chapter provides an introduction to
Preliminary CXTool, describing its main features and functions.
Chapters
Chapter 2 GETTING STARTED This chapter defines the
minimum system requirements and explains how to install and
start CXTool on the element management PC.
Chapter 3 CXTool USER INTERFACE This chapter provides
an introduction to the structure and the functions of the CXTool
graphical user interface.
1-7
CXTool User Guide

Chapter 4 GENERAL CONFIGURATION outlines the methods

for performing general tasks supporting: the configuration
process, and a recommended configuration sequence; script file
generation; and loading a configuration to a CX device.
Chapter 5 CONFIGURING HARDWARE describes how to
create and modify hardware configurations.
Chapter 6 CONFIGURING DRIVERS outlines the procedures
for configuring types of protocol drivers.
NOTE: Trying to create a configuration setting that is
inappropriate may cause the user to suspect that there
is a "bug". Instead, it may be that the setting is not
allowed due to wrong combinations of software
version, and CX device or I/O card. This can occur
when configuration is performed offline, and when
script files files do not match the actual hardware.
For more information on CX devices and slot allocation, refer
to the Hardware Reference Guide of the device.

The Protocol Chapters seven to nineteen of section one contain detailed

Chapters procedures for configuring each protocol and the services
associated with the protocol. These protocol chapters have two
parts.
• The first part identifies the protocol features that are
implemented in CX products.
• The second part describes how the protocol’s parameters are
set using the CXTool dialog boxes.

1.4 Products Configured by CXTool

The following CX devices can be configured using CXTool:
CX2000, CX1000e, CX960, CX950, CX900e, and CX800.

CX devices are supplied with appropriate software. One

method of configuring CX devices is to use CXTool. CXTool
creates configurations taking into account the version of the
software that is being used on the CX device.

CXTool has embedded within it the rules that govern the

various combinations of CX devices, I/O cards, and software
versions. Inappropriate settings are not presented to the user.

1-8 3008M300-004
 Section One

CXTool Configuration
Companion

3008M300-004 cfg-9
CXTool User Guide

cfg-10 3008M300-004

Section One
CXTool Configuration Companion
CONTENTS
List of Figures . . . . . . . . . . . . . . . . . . . . . . . . . cfg FIG-15
List of Tables . . . . . . . . . . . . . . . . . . . . . . . . . cfg TAB-19
GETTING STARTED . . . . . . . . . . . . . . . . . . . . . . cfg 2-21
2.1 System Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . cfg 2-22
2.2 Installing CXTool. . . . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 2-22
2.3 Starting CXTool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 2-23
CXTool USER INTERFACE . . . . . . . . . . . . . . . . cfg 3-25
3.1 CXTool Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 3-26
3.1.1 Module Navigational Panel . . . . . . . . . . . . . . . . . cfg 3-26
3.1.2 Main Panel. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 3-27
3.1.3 Toolbar Buttons . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 3-27
3.1.4 Status Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 3-27
3.1.5 Stack Navigation Panel . . . . . . . . . . . . . . . . . . . . cfg 3-28
3.2 Dialog Boxes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 3-28
3.2.1 Dialog Box Buttons. . . . . . . . . . . . . . . . . . . . . . . cfg 3-29
3.2.2 Values in the Dialog Boxes . . . . . . . . . . . . . . . . . cfg 3-30
3.2.3 Basic and Advanced Tabs . . . . . . . . . . . . . . . . . . cfg 3-31
3.3 Using the CXBrowser . . . . . . . . . . . . . . . . . . . . . . . . . cfg 3-31
3.4 Using CXView . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 3-34
3.4.1 CXView Device Tree. . . . . . . . . . . . . . . . . . . . . . cfg 3-34
3.4.2 Changing the Target Device . . . . . . . . . . . . . . . . cfg 3-35
GENERAL CONFIGURATION. . . . . . . . . . . . . . . cfg 4-37
4.1 Creating a Configuration . . . . . . . . . . . . . . . . . . . . . . . cfg 4-38
4.1.1 Device Hardware, Learning Via Serial Port . . . . cfg 4-38
3008M300-004
CXTool User Guide
4.1.2 Device Hardware, Learning Via IP Connection . . cfg 4-38
4.1.3 Device Hardware, Configuring Offline. . . . . . . . . cfg 4-38
4.2 Loading Script Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 4-39
4.3 Dynamic Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 4-40
4.3.1 Turning Dynamic Mode ON . . . . . . . . . . . . . . . . . cfg 4-41
4.3.2 Dynamic Mode Indicators. . . . . . . . . . . . . . . . . . . cfg 4-41
4.4 Next Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 4-42
CONFIGURING HARDWARE . . . . . . . . . . . . . . . cfg 5-43
5.1 Creating a Hardware Configuration. . . . . . . . . . . . . . . . cfg 5-44
5.1.1 Deriving a Hardware Configuration via a Serial Port . . . . .
cfg 5-44
5.1.2 Deriving a Hardware Configuration via an IP Connection .
cfg 5-45
5.1.3 Building a Hardware Configuration Offline . . . . . cfg 5-46
5.1.4 Offline Configuration of the CX800, CX900e, CX950, and
CX960 cfg 5-46
5.1.5 Offline Configuration of the CX1000e, and CX2000. . . . .
cfg 5-47
5.2 Modifying a Hardware Configuration . . . . . . . . . . . . . . cfg 5-47
5.2.1 Adding a CPU Card (CX2000 only). . . . . . . . . . . cfg 5-48
5.2.2 Configuring Multiple Chassis (CX2000 only) . . . cfg 5-49
5.2.3 Adding a CPU Card (CX1000e only) . . . . . . . . . . cfg 5-50
5.2.4 Adding, Modifying, Deleting I/O Cards . . . . . . . . cfg 5-51
5.3 Change the Default Password . . . . . . . . . . . . . . . . . . . . cfg 5-52
5.4 Changing SNMP Defaults . . . . . . . . . . . . . . . . . . . . . . . cfg 5-52
5.5 Operating System Defaults . . . . . . . . . . . . . . . . . . . . . . cfg 5-52
CONFIGURING DRIVERS . . . . . . . . . . . . . . . . . . cfg 6-55
6.1 Configuring an Async Driver . . . . . . . . . . . . . . . . . . . . cfg 6-56
6.2 Configuring a Bisync Driver . . . . . . . . . . . . . . . . . . . . . cfg 6-58
6.3 Configuring an Ethernet Driver . . . . . . . . . . . . . . . . . . . cfg 6-63
6.4 Configuring a Synchronous Driver . . . . . . . . . . . . . . . . cfg 6-64
6.5 Configuring a Token Ring Driver . . . . . . . . . . . . . . . . . cfg 6-69
cfg TOC-11
CXTool User Guide
CONFIGURING VOICE . . . . . . . . . . . . . . . . . . . . cfg 7-71
7.1 Memotec’s CX Products and the Voice Environment. . cfg 7-72
7.1.1 Adding Voice to an Existing Data Network . . . . . cfg 7-72
7.1.2 Examples of Voice Networks . . . . . . . . . . . . . . . . cfg 7-74
7.1.3 Configuring Voice on CX Products: An Overview cfg 7-76
7.1.4 Typical Voice Network . . . . . . . . . . . . . . . . . . . . . cfg 7-82
7.2 Voice Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 7-83
7.2.1 Configuring the Voice Station . . . . . . . . . . . . . . . . cfg 7-83
7.2.2 Configuring the VoIP Station . . . . . . . . . . . . . . . . cfg 7-84
7.2.3 Configuring the Local Port . . . . . . . . . . . . . . . . . . cfg 7-85
7.2.4 Configuring the Voice Dial Plan . . . . . . . . . . . . . . cfg 7-93
7.2.5 Configuring the Voice Bandwidth Group . . . . . . . cfg 7-99
7.2.7 Configuring the Advanced Definition. . . . . . . . . cfg 7-104
CONFIGURING ATM . . . . . . . . . . . . . . . . . . . . . cfg 8-115
8.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 8-116
8.1.1 Memotec ATM Services . . . . . . . . . . . . . . . . . . . cfg 8-116
8.1.2 Protocols Supported and Voice . . . . . . . . . . . . . . cfg 8-117
8.1.3 Encapsulation . . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 8-118
8.1.4 Tunneling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 8-119
8.1.5 OAM Flows. . . . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 8-120
8.1.6 Typical ATM Network . . . . . . . . . . . . . . . . . . . . cfg 8-120
8.1.7 Summary of ATM features supported on CX Products . . .
cfg 8-126
8.2 Configuring ATM Services . . . . . . . . . . . . . . . . . . . . . cfg 8-127
8.2.1 Configuring the Port . . . . . . . . . . . . . . . . . . . . . . cfg 8-127
8.2.2 Configuring the Virtual Channel. . . . . . . . . . . . . cfg 8-131
8.2.3 Configuring the ATM Traffic Descriptors. . . . . . cfg 8-134
8.2.4 Configuring the ATM Tunnel . . . . . . . . . . . . . . . cfg 8-135
8.3 Configuring DXI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 8-135
8.3.1 Configuring the DXI Circuit . . . . . . . . . . . . . . . . cfg 8-137
CONFIGURING FRAME RELAY . . . . . . . . . . . . cfg 9-139
9.1 Memotec’s CX Family and the Frame Relay Environment . . . .
cfg 9-140
9.1.1 Supported Frame Relay Features . . . . . . . . . . . . cfg 9-140
cfg TOC-12
9.1.2 Typical Frame Relay Configuration . . . . . . . . . . cfg 9-144
9.2 Configuring Frame Relay with CXTool . . . . . . . . . . . cfg 9-148
9.2.1 Configuring a Frame Relay Port . . . . . . . . . . . . . cfg 9-148
9.2.2 Configuring Frame Relay DLCIs. . . . . . . . . . . . cfg 9-153
9.2.3 Configuring Frame Relay Switching . . . . . . . . . cfg 9-156
9.2.4 Configuring the ATM Interworking Port . . . . . . cfg 9-158
9.2.5 Configuring Simplex Services . . . . . . . . . . . . . . cfg 9-163
9.2.6 Configuring Switched Multicast Service . . . . . . cfg 9-164
9.2.7 Configuring Non-Switched Multicast Services . cfg 9-165
CONFIGURING IP . . . . . . . . . . . . . . . . . . . . . . cfg 10-167
10.1 Memotec’s CX Family and the IP Environment . . . cfg 10-168
10.1.1 IP Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 10-168
10.1.2 Protocol Support . . . . . . . . . . . . . . . . . . . . . . . cfg 10-168
10.1.3 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 10-168
10.1.4 Typical IP Configuration. . . . . . . . . . . . . . . . . cfg 10-171
10.2 Configuring IP with CXTool . . . . . . . . . . . . . . . . . . cfg 10-178
10.2.1 Configuring the IP Station . . . . . . . . . . . . . . . cfg 10-178
10.2.2 Configuring the WAN Link. . . . . . . . . . . . . . . cfg 10-186
10.2.3 Configuring the OSPF Area . . . . . . . . . . . . . . cfg 10-187
10.2.4 Configuring the IP Port . . . . . . . . . . . . . . . . . . cfg 10-189
10.2.5 Configuring the IP QoS. . . . . . . . . . . . . . . . . . cfg 10-194
10.2.6 Configuring the IP Tunnel . . . . . . . . . . . . . . . cfg 10-196
CONFIGURING ISDN AND QSIG . . . . . . . . . . cfg 11-197
11.1 Memotec’s CX Products and the ISDN Environment cfg 11-198
11.1.1 Typical ISDN Configuration . . . . . . . . . . . . . . cfg 11-198
11.1.2 Summary of ISDN features supported on CX Products . .
cfg 11-202
11.2 Configuring ISDN with CXTool . . . . . . . . . . . . . . . cfg 11-204
11.2.1 Configuring the ISDN Port . . . . . . . . . . . . . . . cfg 11-204
11.2.2 Configure the ISDN Data Service Point . . . . . cfg 11-213
CONFIGURING T1/E1 . . . . . . . . . . . . . . . . . . . cfg 12-217
12.1 Memotec’s CX Products and the T1/E1 Environment cfg 12-218
12.1.1 Channelized and Unchannelized Ports . . . . . . cfg 12-218
3008M300-004

12.1.2 Slot Restrictions for the DIM . . . . . . . . . . . .
12.1.3 Typical T1/E1 Configuration. . . . . . . . . . . . .
12.1.4 Features of T1/E1 Supported on CX Products
12.2 Configuring T1/E1 . . . . . . . . . . . . . . . . . . . . . . . . .
12.2.1 Configuring the T1/E1 Port. . . . . . . . . . . . . .
12.2.2 Configuring T1/E1 Channels . . . . . . . . . . . .
CONFIGURING SNA . . . . . . . . . . . . . . . . . . . . cfg 13-237
13.1 Memotec’s CX Family and the SNA Environment
13.1.1 Protocol Support . . . . . . . . . . . . . . . . . . . . . .
13.1.2 Product Features . . . . . . . . . . . . . . . . . . . . . .
13.2 Typical SNA Configuration . . . . . . . . . . . . . . . . . .
13.3 Configuring SNA using CXTool . . . . . . . . . . . . . .
13.3.1 Configuring the SNA Link . . . . . . . . . . . . . .
13.3.2 Configuring the SDLC Port. . . . . . . . . . . . . .
13.3.3 Configuring the SDLC Control Unit (CU) . .
13.3.4 Configuring LLC2 LAN . . . . . . . . . . . . . . . .
13.3.5 Configuring LLC2 WAN. . . . . . . . . . . . . . . .
13.3.6 Configuring the QLLC Port . . . . . . . . . . . . .
13.3.7 Configuring the QLLC Control Unit (CU) . .
CONFIGURING ASYNCHRONOUS PAD . . . . cfg 14-255
14.1 Memotec’s CX Products and the Async PAD Environment . . .
cfg 14-256
14.1.1 Summary of Async PAD features supported on CX Products
cfg 14-256
14.1.2 Typical Async PAD Configuration . . . . . . . . cfg 14-256
14.2 Configuring Async PAD with CXTool . . . . . . . . . cfg 14-259
14.2.1 Configuring the Async PAD Station . . . . . . . cfg 14-260
14.2.2 Configuring the Async PAD Port . . . . . . . . . cfg 14-261
14.2.3 Configuring the X.3 Profile. . . . . . . . . . . . . . cfg 14-263
14.2.4 Configuring the SVC WAN DTE . . . . . . . . . cfg 14-268
CONFIGURING X.25 . . . . . . . . . . . . . . . . . . . . cfg 15-271
15.1 Memotec’s CX Products and the X.25 Environment cfg 15-272
15.1.1 Supported X.25 Features . . . . . . . . . . . . . . . . cfg 15-272
3008M300-004
CXTool User Guide
cfg 12-220 15.1.2 Typical X.25 Configuration . . . . . . . . . . . . . . cfg 15-273
cfg 12-222 15.2 Configuring X.25 with CXTool . . . . . . . . . . . . . . . . cfg 15-276
cfg 12-225 15.2.1 Configuring the X.25 Station . . . . . . . . . . . . . cfg 15-277
cfg 12-226 15.2.2 Configuring the X.25 Port. . . . . . . . . . . . . . . . cfg 15-278
cfg 12-227 15.2.3 Configuring the X.25 Service Point . . . . . . . . cfg 15-291
cfg 12-232 15.2.4 Configuring PVCs. . . . . . . . . . . . . . . . . . . . . . cfg 15-296
15.2.5 Configuring the SVC Route . . . . . . . . . . . . . . cfg 15-298
15.2.6 Configuring the Hunt Service . . . . . . . . . . . . . cfg 15-299
15.2.7 Configuring the Closed User Group Service . cfg 15-299
cfg 13-238 15.2.8 Configuring the Logical Link Service . . . . . . cfg 15-300
cfg 13-238 15.2.9 Configuring the Remote DTE Service . . . . . . cfg 15-301
cfg 13-238 15.2.10 LLC2 Using X.25 Over Ethernet LAN. . . . . cfg 15-303
cfg 13-239 15.2.11 X.25 Over TCP Ethernet LAN Using LAPB cfg 15-304
cfg 13-240
cfg 13-240
cfg 13-243 CONFIGURING IPX . . . . . . . . . . . . . . . . . . . . . cfg 16-307
cfg 13-245 16.1 Memotec’s CX Products and the IPX Environment cfg 16-308
cfg 13-247 16.1.1 IPX Routing . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 16-308
cfg 13-249 16.1.2 Typical IPX Configuration . . . . . . . . . . . . . . . cfg 16-308
cfg 13-251 16.2 Configuring IPX with CXTool . . . . . . . . . . . . . . . . cfg 16-309
cfg 13-251 16.2.1 Configuring the IPX Port . . . . . . . . . . . . . . . . cfg 16-309
16.2.2 Configuring IPX Packet Handling . . . . . . . . . cfg 16-312
16.2.3 Configuring IPX SAP Filters . . . . . . . . . . . . . cfg 16-313
CONFIGURING MLPPP. . . . . . . . . . . . . . . . . . cfg 17-315
17.1 Memotec’s CX Products and the MLPPP Environment . . . . . .
cfg 17-316
17.2 Configuring MLPPP with CXTool . . . . . . . . . . . . . cfg 17-316
17.2.1 Configuring the MLPPP Port . . . . . . . . . . . . . cfg 17-316
17.2.2 Configuring the MLPPP Bundle . . . . . . . . . . . cfg 17-319
CONFIGURING BRIDGING . . . . . . . . . . . . . . . cfg 18-321
18.1 Memotec’s CX Family and the Bridge Environment cfg 18-322
18.1.1 Typical Bridging Configuration . . . . . . . . . . . cfg 18-322
18.2 Configuring Bridging with CXTool. . . . . . . . . . . . . cfg 18-323
18.2.1 Configuring the Bridge Station . . . . . . . . . . . . cfg 18-323
18.2.2 Configuring the Source Routing Port . . . . . . . cfg 18-325
cfg TOC-13
CXTool User Guide

18.2.3 Configuring the Spanning Tree Port . . . . . . . . cfg 18-329

HDLC, BISYNC, AND BRI . . . . . . . . . . . . . . . . cfg 19-333

19.1 HDLC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 19-334
19.2 BISYNC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 19-334
19.3 BRI. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 19-335
19.4 Global Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 19-336

cfg TOC-14 3008M300-004

 CXTool User Guide

Section One Fig.5-8 Configuring Multiple Chassis on CX2000 . . . . . . . . . . cfg 5-50

Fig.5-9 Hardware List for a CX1000e. . . . . . . . . . . . . . . . . . . . cfg 5-51
CXTool Configuration Companion Fig.5-10 Hardware Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . cfg 5-51
Fig.5-11 System Information, Configuring Console. . . . . . . . . cfg 5-52
Fig.5-12 System Information, Configuring SNMP . . . . . . . . . . cfg 5-53
List of Figures Fig.5-13 System Information, OS Parameters Tab . . . . . . . . . . cfg 5-53

Fig.6-1 CX Device, Async Packets, and Network . . . . . . . . . . cfg 6-56

Fig.3-1 CXTool Window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 3-26
Fig.3-2 Module Navigation Panel and Stack Navigation Panel cfg 3-27
Fig.3-3 Status Bar Message . . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 3-28
Fig.3-4 Dialog Box Showing Grayed Out Parameters . . . . . . cfg 3-29
Fig.3-5 Dialog Box Buttons. . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 3-29
Fig.3-6 Port Parameter Value is slot.port . . cfg 3-30
Fig.3-7 Interface Channel Values are slot.port.channel .
cfg 3-31
Fig.3-8 Starting the CXBrowser . . . . . . . . . . . . . . . . . . . . . . .
Fig.3-9 SNMP Configuration of CXBrowser . . . . . . . . . . . . .
Fig.3-10 CXBrowser Main Window . . . . . . . . . . . . . . . . . . . .
Fig.3-11 CXBrowser With Selection and Details . . . . . . . . . .
Fig.3-12 CXBrowser Showing Filter Drop-down List . . . . . .
Fig.3-13 Adding the CXView Server Address . . . . . . . . . . . .
Fig.3-14 CXView Tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig.3-15 CXView Device Hardware Display . . . . . . . . . . . . .
Fig.4-1 Choosing Download Connection Type . . . . . . . . . . . .
Fig.4-2 Download Script Screen . . . . . . . . . . . . . . . . . . . . . . .
Fig.4-3 CXTool Main Window, with Dynamic Mode ON . . .
Fig.4-4 Module Navigation Panel With Dynamic Modules . .
Fig.5-1 Product Configuration Via a Serial Port . . . . . . . . . . .
Fig.5-2 Configuring CX Products Via an IP Connection . . . .
Fig.5-3 Configuring CX Products Offline . . . . . . . . . . . . . . . .
Fig.5-4 Configuring Hardware . . . . . . . . . . . . . . . . . . . . . . . .
Fig.5-5 Configuring Software Revision and Voice Capability
Fig.5-6 Configuring Hardware on CX2000. . . . . . . . . . . . . . .
Fig.5-7 Configuring the CPU on a CX2000 . . . . . . . . . . . . . .
Fig.6-2 Configuring an Async Driver . . . . . . . . . . . . . . . . . . . . cfg 6-56
Fig.6-3 CX Device, Bisync Packets, and Network . . . . . . . . . . cfg 6-58
Fig.6-4 Configuring the Bisync Driver, General Tab . . . . . . . . cfg 6-59
Fig.6-5 Configuring the Bisync Driver (Extended). . . . . . . . . . cfg 6-60
Fig.6-6 CX Device, Ethernet, and Network . . . . . . . . . . . . . . . cfg 6-63
Fig.6-7 Configuring the Ethernet Driver . . . . . . . . . . . . . . . . . . cfg 6-64
Fig.6-8 Configuring the Synchronous Driver (General) . . . . . . cfg 6-65
Fig.6-9 Configuring the Synchronous Driver (Extended). . . . . cfg 6-67
Fig.6-10 Configuring the Token Ring Driver . . . . . . . . . . . . . . cfg 6-70
cfg 3-32
cfg 3-32 Fig.7-1 Voice over Frame Relay Network: Basics . . . . . . . . . . cfg 7-75
cfg 3-32 Fig.7-2 Frame Relay-based Network: Adding Network Details cfg 7-75
cfg 3-33 Fig.7-3 Frame Relay-based Network: Complete Network . . . . cfg 7-76
cfg 3-34 Fig.7-4 Port/Channel Hunting . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 7-77
cfg 3-34 Fig.7-5 Voice Over Frame Relay . . . . . . . . . . . . . . . . . . . . . . . cfg 7-82
cfg 3-35 Fig.7-6 Configuring the Voice Station . . . . . . . . . . . . . . . . . . . cfg 7-83
cfg 3-35 Fig.7-7 Configuring the VoIP Station . . . . . . . . . . . . . . . . . . . . cfg 7-84
Fig.7-8 Configuring the DSP Channel . . . . . . . . . . . . . . . . . . . cfg 7-86
cfg 4-39 Fig.7-9 Adding a Hardware Port . . . . . . . . . . . . . . . . . . . . . . . . cfg 7-86
cfg 4-40 Fig.7-10 Configuring the Voice Channel . . . . . . . . . . . . . . . . . cfg 7-87
cfg 4-41 Fig.7-11 Configuring the Voice Channel (continued). . . . . . . . cfg 7-89
cfg 4-42 Fig.7-12 Configuring the VoIP Channel . . . . . . . . . . . . . . . . . . cfg 7-91
Fig.7-13 Configuring the Voice Dial Plan . . . . . . . . . . . . . . . . cfg 7-93
cfg 5-44 Fig.7-14 Configuring Voice Regeneration . . . . . . . . . . . . . . . . cfg 7-95
cfg 5-45 Fig.7-15 Configuring the Group ID. . . . . . . . . . . . . . . . . . . . . . cfg 7-96
cfg 5-46 Fig.7-16 Configuring the Local Book . . . . . . . . . . . . . . . . . . . . cfg 7-97
cfg 5-47 Fig.7-17 Configuring the Personal Identification Number . . . . cfg 7-98
cfg 5-48 Fig.7-18 Configuring the Bandwidth Group . . . . . . . . . . . . . . . cfg 7-99
cfg 5-48 Fig.7-19 Configuring the WAN Trunk . . . . . . . . . . . . . . . . . . cfg 7-100
cfg 5-49 Fig.7-20 Configuring the Secondary Trunk . . . . . . . . . . . . . . cfg 7-102

3008M300-004 cfg FIG-15

CXTool User Guide
Fig.7-21 Configuring the IP Trunk . . . . . . . . . . . . . . . . . . . . . cfg 7-102
Fig.7-22 Configuring Voice Digit . . . . . . . . . . . . . . . . . . . . . . cfg 7-104
Fig.7-23 Configuring the Call Progress Tones . . . . . . . . . . . . cfg 7-106
Fig.7-24 Configuring CAS . . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 7-107
Fig.7-25 Configuring CCS . . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 7-109
Fig.7-26 Configuring MFC-R2 . . . . . . . . . . . . . . . . . . . . . . . . cfg 7-110
Fig.8-1 Frame Relay/ATM Network Interworking . . . . . . . . . cfg 8-120
Fig.8-2 Frame Relay/ATM Service Interworking (FRF.8) . . . cfg 8-121
Fig.8-3 Frame Relay/ATM Service Interworking (FRF.8+) . . cfg 8-123
Fig.8-4 Voice Across an ATM Network . . . . . . . . . . . . . . . . . cfg 8-124
Fig.8-5 LAN across an ATM Network . . . . . . . . . . . . . . . . . . cfg 8-125
Fig.8-6 Configuring the ATM Port . . . . . . . . . . . . . . . . . . . . . cfg 8-127
Fig.8-7 Adding an ATM Card . . . . . . . . . . . . . . . . . . . . . . . . . cfg 8-128
Fig.8-8 View the ATM Circuit Configuration . . . . . . . . . . . . cfg 8-130
Fig.8-9 Configuring the ATM Port (continued) . . . . . . . . . . . cfg 8-130
Fig.8-10 Configuring the ATM Virtual Channel (General) . . cfg 8-131
Fig.8-11 Configuring the Virtual Channel Link (Extended) . . cfg 8-133
Fig.8-12 Configuring ATM Traffic Descriptors . . . . . . . . . . . cfg 8-134
Fig.8-13 Configuring the ATM Tunnel. . . . . . . . . . . . . . . . . . cfg 8-135
Fig.8-14 Configuring the DXI Port . . . . . . . . . . . . . . . . . . . . . cfg 8-136
Fig.8-15 Configuring the DXI Circuit. . . . . . . . . . . . . . . . . . . cfg 8-137
Fig.9-1 Committed Information Rate (CIR) . . . . . . . . . . . . . . cfg 9-140
Fig.9-2 Committed Burst Size (Bc). . . . . . . . . . . . . . . . . . . . . cfg 9-141
Fig.9-3 Excess Burst Size (Be) . . . . . . . . . . . . . . . . . . . . . . . . cfg 9-141
Fig.9-4 Frame Relay-Based Network . . . . . . . . . . . . . . . . . . . cfg 9-144
Fig.9-7 Configuring the Frame Relay Port, General . . . . . . . . cfg 9-148
Fig.9-8 Configuring the Frame Relay Port, Extended. . . . . . . cfg 9-150
Fig.9-9 Configuring the Dial Backup Service . . . . . . . . . . . . . cfg 9-152
Fig.9-10 Configuring the Frame Relay DLCI . . . . . . . . . . . . . cfg 9-153
Fig.9-11 Configuring the Frame Relay DLCI (Extended) . . . cfg 9-155
Fig.9-12 Configuring the Frame Relay Switch . . . . . . . . . . . . cfg 9-157
Fig.9-13 Configuring the ATM Interworking Port . . . . . . . . . cfg 9-158
Fig.9-14 Configuring FRF.5 Services . . . . . . . . . . . . . . . . . . . cfg 9-159
Fig.9-15 Configuring a DLCI for FRF.8 . . . . . . . . . . . . . . . . . cfg 9-160
Fig.9-16 Configuring a VCL for FRF.8 . . . . . . . . . . . . . . . . . cfg 9-161
Fig.9-17 Configuring a DLCI for FRF.8+. . . . . . . . . . . . . . . . cfg 9-162
cfg FIG-16
Fig.9-18 Configuring ATM Service Interworking, DLCI for FRF.8+ . .
cfg 9-163
Fig.9-19 Configuring the Simplex Broadcast Service. . . . . . . cfg 9-164
Fig.9-20 Configuring the Multicast Service . . . . . . . . . . . . . . cfg 9-165
Fig.9-21 Configuring Frame Relay, Bundle Service. . . . . . . . cfg 9-166
Fig.10-1 IP NBMA Example: IP Routing over Frame Relay cfg 10-170
Fig.10-2 Configuring IP QOS Services over ATM. . . . . . . . cfg 10-171
Fig.10-3 Configuring Traffic Shaping. . . . . . . . . . . . . . . . . . cfg 10-174
Fig.10-4 Configuring Traffic Sorting . . . . . . . . . . . . . . . . . . cfg 10-175
Fig.10-5 Configuring OSPF Services across an ATM Network . . . . . . .
cfg 10-176
Fig.10-6 RIP Services across a Frame Relay Network with OSPF. . . . .
cfg 10-177
Fig.10-7 Configuring the IP Station . . . . . . . . . . . . . . . . . . . cfg 10-179
Fig.10-8 Configuring the IP Static Route . . . . . . . . . . . . . . . cfg 10-181
Fig.10-9 Configuring the IP Static ARP . . . . . . . . . . . . . . . . cfg 10-182
Fig.10-10 Configuring the IP Filter. . . . . . . . . . . . . . . . . . . . cfg 10-182
Fig.10-11 Configuring the IP Filter (Continued) . . . . . . . . . cfg 10-183
Fig.10-12 Configuring the IP Filter (Continued) . . . . . . . . . cfg 10-183
Fig.10-13 Configuring the DHCP Relay Service . . . . . . . . . cfg 10-185
Fig.10-14 Configuring the IP Helper. . . . . . . . . . . . . . . . . . . cfg 10-185
Fig.10-15 Configuring the IP WAN Link . . . . . . . . . . . . . . . cfg 10-186
Fig.10-16 Configuring the OSPF Port. . . . . . . . . . . . . . . . . . cfg 10-188
Fig.10-17 Configuring the Virtual Interface (OSPF) . . . . . . cfg 10-189
Fig.10-18 Configuring the IP Port. . . . . . . . . . . . . . . . . . . . . cfg 10-190
Fig.10-19 Configuring the OSPF Port. . . . . . . . . . . . . . . . . . cfg 10-192
Fig.10-20 Configuring VRRP . . . . . . . . . . . . . . . . . . . . . . . . cfg 10-192
Fig.10-21 Configuring RIP Services . . . . . . . . . . . . . . . . . . . cfg 10-193
Fig.10-22 Configuring the IP QOS Service . . . . . . . . . . . . . cfg 10-195
Fig.10-23 Configuring the IP Tunnel . . . . . . . . . . . . . . . . . . cfg 10-196
Fig.11-1 ISDN-Frame Relay Backup . . . . . . . . . . . . . . . . . . cfg 11-199
Fig.11-2 Memotec Devices and QSIG . . . . . . . . . . . . . . . . . cfg 11-200
Fig.11-3 Configuring BRI Services. . . . . . . . . . . . . . . . . . . . cfg 11-201
Fig.11-4 Configuring the ISDN Port for BRI Services . . . . . cfg 11-205
Fig.11-6 Configuring the Hardware Port (BRI) . . . . . . . . . . cfg 11-206
Fig.11-7 Configuring BRI Channels . . . . . . . . . . . . . . . . . . . cfg 11-207
3008M300-004
 CXTool User Guide

Fig.11-8 Configuring the ISDN Port for PRI Services . . . . cfg 11-208 Fig.15-3 Configuring the X.25 Station . . . . . . . . . . . . . . . . . cfg 15-277
Fig.11-9 Configuring the T1/E1 Port for PRI Services . . . . cfg 11-208 Fig.15-4 Configuring the X.25 Port (General Features) . . . . cfg 15-279
Fig.11-10 Configuring the ISDN Data Service Point . . . . . cfg 11-214 Fig.15-5 Configuring the LCN Allocation for X.25 Port . . . cfg 15-280
Fig.11-11 Configuring the Global Directory . . . . . . . . . . . . cfg 11-215 Fig.15-6 Configuring the Facilities Service (X.25 Port) . . . . cfg 15-281
Fig.15-7 Configuring the Timer Service (X.25 Port) . . . . . . cfg 15-285
Fig.12-1 Voice via a T1/E1 Interface on CX950. . . . . . . . . cfg 12-222 Fig.15-8 Configuring Extended Service of X.25 Port. . . . . . cfg 15-287
Fig.12-2 Voice via a T1/E1 Interface on CX1000e . . . . . . . cfg 12-224 Fig.15-9 Configuring the X.25 Port (Continued) . . . . . . . . . cfg 15-289
Fig.12-3 Channel Options for DIM . . . . . . . . . . . . . . . . . . . cfg 12-227 Fig.15-10 Configuring the X.25 Service Point (General) . . . cfg 15-291
Fig.12-4 Configuring the T1/E1 Port. . . . . . . . . . . . . . . . . . cfg 12-228 Fig.15-11 Configuring X.25 Service Point LCN Allocation. cfg 15-293
Fig.12-5 Configuring the ISDN Service on T1/E1 . . . . . . . cfg 12-232 Fig.15-12 Configuring the X.25 Service Point (Facilities) . . cfg 15-294
Fig.12-6 Configuring the T1/E1 Port (Channelized) . . . . . . cfg 12-233 Fig.15-13 Configuring the X.25 Service Point (Timer) . . . . cfg 15-296
Fig.12-7 Configuring Data on a Channelized Data Port . . . cfg 12-233 Fig.15-14 Configuring a Permanent Virtual Circuit . . . . . . . cfg 15-297
Fig.12-8 Configuring T1/E1 Timeslots for Multiple Services cfg 12-234 Fig.15-15 Configuring the X.25 SVC Routing Table . . . . . . cfg 15-298
Fig.15-16 Configuring the X.25 Hunt Service . . . . . . . . . . . cfg 15-299
Fig.12-9 Configuring the T1/E1 Port. . . . . . . . . . . . . . . . . . cfg 12-235 Fig.15-17 Configuring the X.25 Closed User Group . . . . . . cfg 15-300
Fig.13-1 SNA Link Type Supported . . . . . . . . . . . . . . . . . . cfg 13-240 Fig.15-18 Configuring the X.25 Logical Link . . . . . . . . . . . cfg 15-301
Fig.13-3 Configuring LLC2 Between SDLC Devices . . . . cfg 13-241 Fig.15-19 Configuring the X.25 Remote DTE . . . . . . . . . . . cfg 15-302
Fig.13-4 Configuring the SNA Link . . . . . . . . . . . . . . . . . . cfg 13-241 Fig.15-20 Configuring LLC2 Using X.25 Over Ethernet . . . cfg 15-303
Fig.13-5 Configuring the SNA Link (Continued) . . . . . . . . cfg 13-242 Fig.15-21 LLC2 Traffic Routed Across a Frame Relay LAN cfg 15-304
Fig.13-6 Sample SNA Network Using SDLC . . . . . . . . . . . cfg 13-243 Fig.15-22 Configuring X.25 Over TCP. . . . . . . . . . . . . . . . . cfg 15-304
Fig.13-7 Configuring SDLC Port . . . . . . . . . . . . . . . . . . . . cfg 13-244 Fig.16-1 Configuring IPX Services. . . . . . . . . . . . . . . . . . . . cfg 16-308
Fig.13-8 Configuring the SDLC Control Unit. . . . . . . . . . . cfg 13-245 Fig.16-2 Configuring the IPX Port . . . . . . . . . . . . . . . . . . . . cfg 16-310
Fig.13-9 Sample SNA Network Using LLC2 . . . . . . . . . . . cfg 13-247 Fig.16-3 Configuring the IPX Packet Handling . . . . . . . . . . cfg 16-313
Fig.13-10 Configuring the LLC2 LAN . . . . . . . . . . . . . . . . cfg 13-247 Fig.16-4 Configuring the IPX SAP Filter . . . . . . . . . . . . . . . cfg 16-314
Fig.13-11 Configuring the LLC2 DataLink. . . . . . . . . . . . . cfg 13-248
Fig.13-12 Configuring the LLC2 WAN . . . . . . . . . . . . . . . cfg 13-250 Fig.17-1 Configuring the MLPPP Port . . . . . . . . . . . . . . . . . cfg 17-317
Fig.13-13 Configuring the QLLC Port . . . . . . . . . . . . . . . . cfg 13-251 Fig.17-2 Configuring the MLPPP Bundle. . . . . . . . . . . . . . . cfg 17-319
Fig.13-14 Configuring the QLLC-CU . . . . . . . . . . . . . . . . . cfg 13-252
Fig.13-15 Configuring the QLLC-CU (Continued). . . . . . . cfg 13-252 Fig.18-1 Ethernet STP Bridging . . . . . . . . . . . . . . . . . . . . . . cfg 18-322
Fig.18-2 Token Ring Source Routing Bridging . . . . . . . . . . cfg 18-323
Fig.14-1 Configuring Async PAD Services . . . . . . . . . . . . cfg 14-256 Fig.18-3 Configuring the Bridge Station. . . . . . . . . . . . . . . . cfg 18-324
Fig.14-2 Configuring the Async PAD Station. . . . . . . . . . . cfg 14-260 Fig.18-4 Configuring the Source Routing Port . . . . . . . . . . . cfg 18-325
Fig.14-3 Configuring the Async PAD Port . . . . . . . . . . . . . cfg 14-261 Fig.18-5 Configuring the Source Routing Port - Advanced . cfg 18-328
Fig.14-4 Configuring the X.3 Profile . . . . . . . . . . . . . . . . . cfg 14-263 Fig.18-6 Configuring the Spanning Tree Port. . . . . . . . . . . . cfg 18-329
Fig.14-5 Configuring the SVC WAN DTE . . . . . . . . . . . . . cfg 14-268
Fig.19-1 Configuring an HDLC Port. . . . . . . . . . . . . . . . . . . cfg 19-334
Fig.15-1 Configuring X.25 Services . . . . . . . . . . . . . . . . . . cfg 15-273 Fig.19-2 Configuring a BISYNC Port. . . . . . . . . . . . . . . . . . cfg 19-335
Fig.15-2 Configuring X.25 SVC Services . . . . . . . . . . . . . . cfg 15-275

3008M300-004 cfg FIG-17

CXTool User Guide

cfg FIG-18 3008M300-004

 CXTool User Guide

Section One
CXTool Configuration Companion

List of Tables

Tab.3-1 Toolbar Buttons . . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 3-28

Tab.5-1 CX2000 Slot Allocation . . . . . . . . . . . . . . . . . . . . cfg 5-50

Tab.6-1 Bisync Frames, Meaning of Preamble Length Values . . . . .

cfg 6-60
Tab.6-2 Parity Parameter, Meaning of Options . . . . . . . . . cfg 6-62
Tab.6-3 Synchronous Packets, CX Device, and Network . cfg 6-64
Tab.6-4 HDLC Frames, Meaning of Preamble Length Values . . . . .
cfg 6-67

Tab.7-1 Dialing Plan Guidelines. . . . . . . . . . . . . . . . . . . . . cfg 7-78

Tab.7-2 Configuring the Dialing Plan (Example 1) . . . . . . cfg 7-79
Tab.7-3 Configuring the Dialing Plan (Example 2) . . . . . . cfg 7-79

Tab.8-1 Memotec ATM Service and the UNI 3.1 Context cfg 8-116
Tab.8-2 Memotec ATM Service and the TM 4.0 Context cfg 8-116
Tab.8-3 Memotec ATM Priority List . . . . . . . . . . . . . . . . cfg 8-119
Tab.8-4 VCI and PTI Values for ATM OAM Flows . . . . cfg 8-120
Tab.8-5 Traffic Descriptor Configuration. . . . . . . . . . . . . cfg 8-134

Tab.9-1 Guidelines for Best Voice Quality . . . . . . . . . . . cfg 9-143

Tab.12-1 Services on Channelized Ports . . . . . . . . . . . . cfg 12-220

Tab.12-2 Services on Unchannelized Ports . . . . . . . . . . cfg 12-220
Tab.12-3 CX950 Slots in Which DIM is Allowed . . . . . cfg 12-221
Tab.12-4 CX960 Slots in Which DIMs are Allowed . . . cfg 12-221
Tab.12-5 CX2000 Slots in Which DIMs are Allowed . . cfg 12-222

3008M300-004 cfg TAB-19

CXTool User Guide

cfg TAB-20 3008M300-004

 2 GETTING STARTED

This chapter provides step-by-step procedures for installing

and starting CXTool on the PC that will be used for element
management. The recommended requirements for the PC are
also listed.

3008M300-004 2-21
CXTool User Guide

2.1 System Requirements
These are the system requirements for installing and using
CXTool.
• IBM-compatible PC with Intel Pentium processor 266 MHz
minimum required (Pentium III 350 MHz or higher strongly
recommended)
• 64 MB of RAM minimum required (128 MB or more strongly
recommmended)
• 70 MB of free disk space for full installation (30 MB without
CXBrowser and JRE)
• SVGA color monitor supporting 800 by 600 pixels and 256
colors minimum (1024 by 768 pixels is recommended for
optimum clarity)
• Serial COM port, for use of the console features
• Supported operating systems:
• Microsoft Windows 95, Win95B
• Internet Explorer 4.0 or higher, for CXView Client
• CD-ROM drive
2.2 Installing CXTool
To install the CXTool application on a PC, follow these steps.
1. Exit all programs that are currently active on your PC.
2. Insert the Memotec CD-ROM into the drive.
3. The CD-ROM includes an Autorun executable and normally
the Memotec Products Menu appears. If the menu does not
appear, do one of the following:
• On the Windows desktop, on the task bar click Start, and
choose Run.
In the Run dialog, in the Open: text box, type d:\autorun
and click OK.
(In place of d: substitute the name of the CDROM drive
where the Memotec CD-ROM is located.)

• Windows 98 • In Windows Explorer, in the All Folders pane, select the

CD-ROM drive. Then, in the Contents Of pane, double-click
• Windows Me (Millennium Edition) autorun.exe.
• Windows NT 4 with service pack 4 or above The Memotec Products Menu appears.
• Windows 2000 4. The Welcome dialog box appears.
Click Next.
5. Choose the Destination Location. (CXTool will suggest the
destination folder. To specify a different folder, click Browse.)
Click Next.
6. Choose the folder for the program icon.
Click Next.

2-22 3008M300-004
 CXTool User Guide

7. Choose whether to view the Readme file or to launch CXTool.

Click Finish.
During setup a CXTool shortcut is added to the Start menu and
to the desktop.

2.3 Starting CXTool

To start CXTool, do this.
1. From the Start menu, select: Programs → Memotec → CXTool.
2. The “Product Configuration” window appears. CXTool is now
ready to create or modify a configuration file.

The next two chapters walk you through the CXTool interface
and the configuration method:
• Chapter 3 CXTool USER INTERFACE
• Chapter 4 GENERAL CONFIGURATION

To bypass these steps and continue with configuring a device,

go to Chapter 5 CONFIGURING HARDWARE.

3008M300-004 2-23
CXTool User Guide

2-24 3008M300-004
 3 CXTool USER INTERFACE

This chapter provides an introduction to the structure and the

functions of the CXTool graphical user interface.

3008M300-004 3-25
CXTool User Guide

3.1 CXTool Window 3.1.1 Module Navigational Panel

CXTool’s window consists of five parts: module navigation
panel, toolbar, main panel, status bar, and stack navigation
panel (see Figure 3-1). These panels and other elements of the
CXTool user interface are described in this chapter.
Module Navigation Panel Toolbar
Main Panel
On the left side of the CXTool window is the module
navigation panel. It displays the hierarchy of the modules.
There is a folder for each module and each folder has its
components grouped under it. In Figure 3-1 for instance, under
the IP module are its Station, WAN Interface, OSPF Area, Port,
QOS, and Tunneling components.

To begin configuring a component, just select it.

Stack Navigation Panel

Status Bar
Figure 3-1: CXTool Window

3-26 3008M300-004
 3 CXTool USER INTERFACE

The current status of a module’s component is indicated by its
icon. For example, looking at Figure 3-2,
• when the icon is selected it is blue
• when the icon has horizontal lines, the component is
configured
• when the icon is blank, the component has no configuration
Additionally, when a module’s component is selected new
instances of it can be created. As an example, to configure a
port on the BRI module, do the following:
1. Click the plus icon in front of the BRI folder to expand its
component list. The expanded list is shown in Figure 3-2.
Clicking the minus icon contracts the list.
2. Select the BRI Port icon.
The parameters for BRI Port configuration are displayed in the
main panel. Values for these parameters may now be added and
modified as required.

Module icon 3.1.2 Main Panel

Module component
- configured and selected The main panel of the CXTool window displays the parameters
Module component of the component that is selected. For instance in Figure 3-1,
- configured the DLCI component of the frame relay module is selected and
the main panel displays the details for the three DLCIs.
Module component
- not configured To add, modify, or delete a configuration, use the buttons on
the tool bar, which is described in section 3.1.3 Toolbar
Buttons. Alternatively, choose Edit on the menu bar and use the
pull-down menu.

3.1.3 Toolbar Buttons

Buttons have been added to the standard Windows user

interface to form a toolbar. These buttons are a handy
alternative to the Edit menu. The buttons are described in
Table 3-1.

3.1.4 Status Bar

The CXTool status bar displays prompts associated with the

Figure 3-2: Module Navigation Panel and Stack Navigation Panel current context. When a value within a range of allowed values

3008M300-004 3-27
CXTool User Guide
Table 3-1: Toolbar Buttons
Toolbar Button Function
The Add (+) button is used to add a new object to the
configuration. Add is context-sensitive. For example, in the
Module Navigation Panel when the Port component of the
IP module is highlighted, clicking Add opens a dialog box
Add to configure a new IP port.
Use the Modify (+/-) button to open a dialog box
where the values of an existing object can be
modified. Modify is context sensitive.
Modify
When clicked, Delete (–) first shows a warning with a
Yes button to confirm the command. When confirmed,
Delete removes the currently selected object and also
removes all other objects that use it.
Delete
The Download button loads the current
configuration to the target device.
Download
Clicking the CXView button starts the CXView
application, which displays the current status and
configuration of a target device. The CXView
server must be installed and running for this
CXView feature to work. See 3.4 Using CXView.
Clicking the CXBrowser button starts the CX
browser application. A description of the CX
browser is given in 3.3 Using the CXBrowser.
CXBrowser
3-28
must be used, the status bar displays the range that is allowed.
Shortcut When CXTool detects an error or omission in a dialog box, the
Ctrl + A status bar displays a warning and a beep sounds. A sample
prompt of this kind is shown in Figure 3-3.
Figure 3-3: Status Bar Message
Ctrl + M
CXTool verifies the configuration parameters when the Finish
button is clicked. If the configuration is invalid or incomplete
an error message such as “Invalid IP Address” appears in the
status bar. The box will not close until it is correct.
Ctrl + D
3.1.5 Stack Navigation Panel
The Stack Navigation Panel is used to verify the configuration
link dependancies and to navigate to a particular module.
Ctrl + W
In Figure 3-1, in the module navigation panel, under the frame
relay module, DLCI is selected. As a result, in the stack
navigation panel, the Up Layer is the IP WAN interface. The
Down Layer shows that this DLCI is associated with FRPort1.
Ctrl + I Selecting an element of either layer displays the details
associated with it in the main panel. Selections in the main
panel are reflected in the Stack Navigation Panel.
3.2 Dialog Boxes
The usual purpose of a dialog box, is to collect information.
However, most of the parameters in CXTool dialog boxes have
default settings that fulfill standard communication
requirements reducing the amount of information to be input.
3008M300-004
 3 CXTool USER INTERFACE

But, when one of the default settings is not appropriate it must

be changed.

Sometimes a parameter is grayed out, which means it does not

apply at the present time and is inactive. When some other
condition elsewhere requires it, the parameter is no longer
grayed out, indicating that it does apply and is active.

For example, in Figure 3-4, the parameters for ATM

Interworking Port Type are grayed out because the ATM
Interworking Port is disabled. When the ATM Interworking
Port is enabled, they are no longer greyed and the user can
select an interworking service.

In the event that a value must be entered from an allowed range

and there is no drop-down menu provided, a tooltip is used to
show the range. A tooltip appears when the cursor is positioned
over the place where the value is to be entered, showing the
allowed range of values.

Figure 3-4: Dialog Box Showing Grayed Out Parameters

3.2.1 Dialog Box Buttons

The five buttons located at the bottom of configuration dialog

boxes are similar to Figure 3-5.

Figure 3-5: Dialog Box Buttons

3008M300-004 3-29
CXTool User Guide

• Use Back and Next to move between main panels when

Slot 8
protocols have parameters in multiple panels. These buttons Physical Port 1
are grayed out unless the module uses multiple main panels.
• Use Finish to close the dialog box and save the
configuration in a temporary file. To save the configuration
permanently, use the Save icon on the toolbar or the Save
command in the File menu.
On exiting, CXTool prompts for a permanent save if
temporary files are present.
• Use Cancel to close the dialog box and return to the
previous screen. Changes are ignored.
• Use Help to open the HTML help file for the current
module.

3.2.2 Values in the Dialog Boxes

For the most part, it is easy to understand the meaning of

parameter values. Occasionally though, the value of certain
parameters may not be so easy to understand. The parameters
of Ports and the parameters of Channels are two examples.

Port When a card is added, it is identified by its position in the

hardware. Its slot number and the numbers of its physical ports
are both reflected in the values given to the Port parameter. Figure 3-6: Port Parameter Value is slot.port

For example, Figure 3-6 shows the T1/E1 Timeslot window

where card slot 8 is the location of the T1/E1 card, and port 1 is
the physical port where the channels or time slots will be
configured. So, the value 8.1 is used.
Consequently, when referring to the T1/E1 Timeslot
configuration in the CXTool User Guide, it is shown this way:
DIM 8.1 (Channelized)
Channels When configuring voice services, the card’s slot number,
associated physical ports, and channels are combined to
identify it. This is illustrated in the Voice Channel window
shown Figure 3-7.
In the Interface Channels group box, each value is made up of
three numbers: the slot number, the physical port number, and

3-30 3008M300-004
 3 CXTool USER INTERFACE

the voice channel number. The values shown are 8.2.1, 8.2.2,
and so on.
In the DSP Channel Hunting group box, the first number is the
slot number and the second number refers to the DSP channel
number. The values shown are 8.1, 8.2, and so on.
3.2.3 Basic and Advanced Tabs
Many of the CXTool modules include two groups of settings;
basic settings, and advanced settings. In Figure 3-7, a typical
type of CXTool screen, the Basic tab and the Advanced tab are
shown. Clicking a tab displays the associated settings.

For the most part, the parameters on the Advanced tab do not
need to be configured. In general, this User Guide does not
include screen captures of the Advanced tabs, although
descriptions of these parameters are provided.

It is recommended that the advanced parameters not be

modified unless you have a full understanding of the options
and their impacts.

3.3 Using the CXBrowser

Use the CXBrowser to inspect the current settings of a CX
device. The CXBrowser is a component of the CXTool
application and it behaves much like an Internet browser.

Figure 3-7: Interface Channel Values are

slot.port.channel

3008M300-004 3-31
CXTool User Guide

Start CXBrowser by clicking Tools on the menu bar of CXTool type the community string—the password—and click OK.
and choosing CXBrowser, as shown in Figure 3-8. CXBrowser sends a query to the target device.

If an error message is received or if the display says that no

data is available, try increasing the Timeout value. It may be
that more time is required for the data to be received.

As the data is received from the CX device it is stored locally

in a database. When the CXBrowser is first connected, only a
few data items are requested and the data begins to load right
away. A tree of the target’s components appears in the left
pane. An example is shown in Figure 3-10.

Figure 3-8: Starting the CXBrowser

An SNMP Configuration screen appears, like the one shown in

Figure 3-9.

Figure 3-9: SNMP Configuration of CXBrowser

Figure 3-10: CXBrowser Main Window
Type the IP address of the target device, that is, the CX device
whose settings are to be inspected. It is assumed that the target
device has already been configured with this IP address. Then,

3-32 3008M300-004
 3 CXTool USER INTERFACE

In front of each component folder of the tree is an expand/

collapse icon. The icon is a toggle. Click it to expand the
folder’s contents. Click it again to collapse.

Selecting the icon of a component in the left pane sends a

query to the device. The results of the query are added to the
local database and displayed in the right pane of the browser.
Notice that a query is created only the first time an icon is
selected. Afterwards, when the icon is selected the current
values in the local database are displayed.

It is not necessary to wait for the response from the CX device

before making additional selections. As many icons as
necessary may be selected and they all create queries. The
results returned by the device are added to the local database as
they are received. To display a result, select the icon. To refresh
the result, that is, to update the results from the CX device,
click the refresh button shown at the bottom of the right pane in
Figure 3-10.

The Reload Config button is used to start over. It clears the Figure 3-11: CXBrowser With Selection and Details
local database and sends a query to the CX device. Only a few
items are requested. No other data remains in the local
database.

In the right pane of CXBrowser, a row of the results table can

be selected and if there are details associated with it, a Show
Detail button appears at the bottom of the pane. Clicking the
Show Detail button opens a Detailed Info table in the lower
half of the right pane. An example is shown in Figure 3-11.

For some tables, CXBrowser provides a filter. When the filter

is available a drop-down list button appears in the top right
corner of the right pane. An example is shown in Figure 3-12.
Selecting an item from the drop-down list applies the filter to

3008M300-004 3-33
CXTool User Guide

the table. Selecting All disables the filter and shows the whole Clicking the CXView button on the CXTool tool bar starts the
table. application. Its main window displays the device tree and a
group of buttons offering display options.

A basic description of CXView follows. For detailed

information, refer to the CXView user guide.

3.4.1 CXView Device Tree

Follow these steps to view the configuration of a device using

the device tree.
1. On the CXTool tool bar, click the CXView button without
opening a CXTool configuration. The screen shown in
Figure 3-13 appears when this feature is used for the first time.

Figure 3-12: CXBrowser Showing Filter Drop-down List

Figure 3-13: Adding the CXView Server Address

3.4 Using CXView
CXView is a client/server application in which the server stores
information from managed devices and the client views the
server database. The CXView client is installed along with
CXTool and it supports HP OpenView.
The CXView server is a separate application that must be
installed for this feature to work.
To proceed, enter the Server’s IP Address, and click on OK.
Otherwise, click Cancel.
Once the address of the server is entered, the address dialog
will not reappear. Instead, when the CXView button is clicked
the screen shown in Figure 3-14 appears.
2. Choose a device in the left pane, then click the ViewDevice
button to view the devices within a network.
The CXView Device List appears, as shown in Figure 3-15.

3-34 3008M300-004
 3 CXTool USER INTERFACE

Figure 3-14: CXView Tree Figure 3-15: CXView Device Hardware Display

3. View the configuration for the selected device by clicking on a DNS server. For a device within the network, select its IP
the appropriate IP address. Figure 3-15 shows the device address in the CXView tree.
details for 204.19.88.245.

In Figure 3-15, notice that the CXView server address is

204.19.88.242 and the IP address of the device being viewed in
the Web browser is 204.19.88.245.

3.4.2 Changing the Target Device

To access a different server, enter its IP address in the address

box of Internet Explorer, or use the FQDN if it is mapped with

3008M300-004 3-35
CXTool User Guide

3-36 3008M300-004
 4 GENERAL CONFIGURATION

This chapter describes the sequence of tasks used to configure

a CX product. The description is general but it is important
because the required task sequence may not be obvious.
Included are the configuration sequence and the
post-configuration tasks such as loading a script file to a CX
device.

3008M300-004 4-37
CXTool User Guide
4.1 Creating a Configuration
This section outlines the tasks required to create a
configuration file for Memotec CX devices. After it has been
created, the configuration file can be modified and revised to
suit the requirements of the system. The configuration file is
then loaded to the device. A new CX device can be given an
initial configuration as conveniently as the current
configuration of an existing device can be modified.
There are three methods:
• The existing hardware can be learned through the serial port,
that is, the current parameters of the device are acquired by
messaging through the serial port. Learning through the
serial port results in a local copy of the current configuration
file, which is appropriate for the hardware that is discovered.
See 4.1.1 Device Hardware, Learning Via Serial Port.
• The existing hardware can be learned by connecting to its IP
address, that is, the current parameters of the device are
acquired by an exchange of messages with its IP address.
Learning by connecting to its IP address results in a local
copy of the current configuration file, which is appropriate
for the hardware that is at that address. See 4.1.2 Device
Hardware, Learning Via IP Connection.
• A configuration can be created from scratch, which is
referred to as an offline configuration. To do this, the CX
device type is selected, and then a configuration is created
manually. See 4.1.3 Device Hardware, Configuring Offline
4.1.1 Device Hardware, Learning Via Serial Port
The sequence outlined below is for users who want CXTool to
learn the hardware configuration (CPU and I/O cards) of a CX
device using a serial port.
4-38
1. In the “Product Configuration” panel that appears when the
CXTool application is launched, select Learn Hardware from
Serial Port
Full details are given in 5.1.1 Deriving a Hardware
Configuration via a Serial Port.
2. Configure the CX device software.
3. Save the configuration, generate a script file, and load the script
file through the console port of the CX device.
Refer to 4.2 Loading Script Files for details.
4.1.2 Device Hardware, Learning Via IP Connection
The sequence outlined below should be followed by users who
want CXTool to learn the hardware configuration of a remote
CX device via an IP connection.
1. In the Product Configuration panel, select Learn Hardware
from an IP Connection.
Refer to 5.1.2 Deriving a Hardware Configuration via an IP
Connection for full details.
2. Configure the CX device software.
3. Save the configuration, generate a script file, and load the script
file through the console port of the CX device or through a
remote connection to a network port of the CX device.
Refer to 4.2 Loading Script Files for details.
4.1.3 Device Hardware, Configuring Offline
The following sequence creates a hardware configuration
offline for a remote CX device.
1. In the Product Configuration panel, select Offline
Configuration.
3008M300-004
 4 GENERAL CONFIGURATION

Full details are given in 5.1.3 Building a Hardware 1. From the File menu, select Download Configuration or click
Configuration Offline. the Download icon on the menu bar.
2. Configure the CX device software. The screen shown in Figure 4-1 appears.

3. Save the configuration and generate a script file.

4. Load the script file through the console port of the CX device
or through a remote connection to a network port of the CX
device.
Refer to 4.2 Loading Script Files for details.

4.2 Loading Script Files

When a configuration is created using CXTool, the data that is
Figure 4-1: Choosing Download Connection Type
entered into the dialog boxes is stored in a database. Then, to
configure the CX device, a script file is generated from the
database and loaded to the device.

NOTE: Before generating a script file, be sure to first save the

configuration.

To generate a script file and load the configuration, follow

these steps.

3008M300-004 4-39
CXTool User Guide

2. Select the connection type and then define the settings for the
connection. Click Next.
The screen shown in Figure 4-2 appears.
4.3 Dynamic Mode
Creating and revising the configuration of a CX device may
involve a lot of data exchange with the device, and this process
leads eventually to a reset of the device. To reduce the amount
of data moving back and forth, and also to avoid resetting the
device, CXTool includes a Dynamic Mode.

When turned on, Dynamic Mode creates scripts and uses

commands that revise certain parameters without exchanging
all of the configuration data, and without resetting the CX
device. These kinds of revisions are sometimes called
“changing on the fly”, which underlines that there is no need to
reset and that the revisions are done quickly.

Since only certain configuration values are revised with this

method, Dynamic Mode is not suitable for the initial, original
configuration of a device. Dynamic Mode applies only when a
device configuration is being revised, and only applies to
certain modules of Frame Relay/Frame Relay ATM
Interworking, Voice, and X.25.
Figure 4-2: Download Script Screen

3. Choose Full Download.

The process begins with a series of tests. When the tests are
completed successfully, the configuration is loaded to the CX
device.

For details regarding the configuration of hardware, see

Chapter 5 CONFIGURING HARDWARE.

For details regarding the configuration of drivers, see

Chapter 6 CONFIGURING DRIVERS.

4-40 3008M300-004
 4 GENERAL CONFIGURATION

4.3.1 Turning Dynamic Mode ON

NOTE: The process of automatic validation of synchronization
Once the CX device has an initial configuration loaded, the is not possible in versions of CXTool before
CXTool main window includes an enabling check box. A version 3.4. In versions before 3.4 a warning requires
check in the box means that Dynamic Mode is turned on. the user to verify that the configuration in CXTool and
the CX device are synchronized.

4.3.2 Dynamic Mode Indicators

When Dynamic Mode is on, the display in the Module

Navigation Panel includes a letter D, in green, superimposed
on the icons of the affected modules. An example is shown in
Figure 4-4. Those modules marked with the green D are able to

Figure 4-3: CXTool Main Window, with Dynamic Mode ON

Turning Dynamic Mode on initiates a process that compares

the current configuration of the device and the configuration
loaded in CXTool. If they are synchronized, then the turn-on of
Dynamic Mode will succeed. Otherwise Dynamic Mode will
not be turned on.

3008M300-004 4-41
CXTool User Guide

have parameters modified without loading the full During a configuration session when Dynamic Mode is on,
configuration to the device and without a device reset. only those modules marked as dynamic with a green D may be
revised, that is, added, or modified. The other non-dynamic
modules may be viewed but must not be revised.

After revisions have been made to Dynamic Mode modules,

CXTool generates a configuration script that reflects these
revisions. This configuration script is loaded to the CX device
and executed without resetting it.

The configuration script includes dynamic commands, the

original full script updated with the revisions to the Dynamic
Mode modules, and the zipped database of the current
configuration parameters of CXTool.

4.4 Next Steps

This manual provides an individual chapter for each protocol,
with detailed information about the tasks involved in its
configuration. The table of contents of Section One, CXTool
Configuration Companion lists the protocols and their chapter
numbers.

This manual also provides an introduction to the protocols and

their parameters in Section Two, CXTool Primer. The protocols
and their chapter numbers are listed in the table of contents of
Section Two.

Figure 4-4: Module Navigation Panel With Dynamic Modules

4-42 3008M300-004
 5 CONFIGURING HARDWARE

Configuring the hardware is the first step towards the successful

setup of a CX product. This chapter describes how to create and
modify a hardware configuration.

3008M300-004 5-43
CXTool User Guide

5.1 Creating a Hardware Configuration 1. Connect the console port of the CX device to the COM port of
the PC that will be used to do the configuration.
Hardware configuration usually precedes software 2. On the PC, start CXTool.
configuration. CXTool offers three general approaches to The CXTool window opens and the Product Configuration
creating a hardware configuration. Use the one that is most dialog box appears, as shown in Figure 5.1
effective for the situation.
• 5.1.1 Deriving a Hardware Configuration via a Serial Port
• 5.1.2 Deriving a Hardware Configuration via an IP Connection
• 5.1.3 Building a Hardware Configuration Offline

These methods are described below.

5.1.1 Deriving a Hardware Configuration via a Serial Port

This method invokes CXTool’s auto-learn function to retrieve

the hardware configuration of an existing CX product over a
serial port. The user can then start with the retrieved
configuration as a base, and make modifications to it.

To derive a hardware configuration via a serial port, do the

following.

Figure 5-1: Product Configuration Via a Serial Port

5-44 3008M300-004
 5 CONFIGURING HARDWARE

3. Select the New Configuration tab and choose the Learn 3. From the File menu, choose New. The screen that appears is
Hardware from Serial Port radio button. shown in Figure 5.2.
4. In the Serial group box choose a COM port from the Port list.
Click on Properties to display the COM port settings.
Configure these settings if the hardware configuration will be
learned over a modem (telephone network).
5. In the Serial group box accept the default password or change it
by following the steps outlined in 5.3 Change the Default
Password.
6. Click Next. CXTool retrieves the hardware configuration and
software version from the target device and displays them.
7. Modify the hardware configuration, if necessary.

NOTE: CXTool enforces restrictions regarding the location

and quantity of certain I/O card types. Refer to the
appropriate hardware guide for details.

5.1.2 Deriving a Hardware Configuration via an IP Connec-

tion

In this method, CXTool learns the configuration of an existing

remote CX product configuration via an IP connection.

To derive a hardware configuration via an IP connection, do the

following.
1. Make sure that there is an IP connection between the COM
port of the PC to be used to do the configuring and the network Figure 5-2: Configuring CX Products Via an IP Connection
over which the target CX device can be reached.
4. Select the New Configuration tab and choose the Learn
2. On the PC, start CXTool. Hardware from IP Connection radio button.
5. In the IP group box enter the IP Address of the remote device.

3008M300-004 5-45
CXTool User Guide

6. In the IP group box accept the default password in the Set

Community parameter or change it by following the steps
outlined in 5.3 Change the Default Password.
7. Click Next. The hardware configuration and software version
are retrieved from the target CX device and displayed on the
screen.
8. Modify the hardware configuration, if necessary.

5.1.3 Building a Hardware Configuration Offline

With this method a hardware configuration is created manually.

To build a hardware configuration offline, follow these steps.

1. From the File menu, choose New. The screen that appears is
shown in Figure 5-3
2. Select the New Configuration tab and choose the Offline
Configuration radio button.
3. In the Offline Configuration group box click the radio button
for the CX product to be configured.
4. Click Next. A configuration screen appears that is appropriate
for the selected CX product.

Since the CX product chosen determines the dialogs displayed

and the parameters required, apply one of the following
sections. The configuration parameters for CX800, CX900e,
CX950, and CX960 are outlined in section 5.1.4 Offline
Configuration of the CX800, CX900e, CX950, and CX960.
5.1.4
The configuration parameters for CX1000e and CX2000 are
outlined in section 5.1.5 Offline Configuration of the CX1000e,
and CX2000.
Figure 5-3: Configuring CX Products Offline
Offline Configuration of the CX800, CX900e, CX950,
and CX960
Begin in the Product Configuration dialog box shown in
Figure 5-3. Select the New Configuration tab, then choose
Offline Configuration. From the Offline Configuration group

5-46 3008M300-004
 5 CONFIGURING HARDWARE

box CX950 was chosen for this description and serves as a

guide for the configuration of a CX800, a CX900e, a CX950,
and a CX960.

5.1.5 Offline Configuration of the CX1000e, and CX2000

Begin in the Product Configuration dialog box shown in

Figure 5-3. Select the New Configuration tab, then choose
Offline Configuration.

For this description, the CX1000e was chosen from the Offline
Configuration group box and serves as a guide for the
configuration of a CX2000.

Click Next. The screen shown in Figure 5-4 appears.

To continue with the configuration, find the row that represents

the slot to be configured. Then, click the cell in that row of the
column for the item to be configured, as follows:
1. Click in the CPU column. Open the drop-down list, and choose
the CPU.
2. Click in the Revision column. Open the drop-down list, and
choose the software revision number.
3. Click in the Voice Capability column. Accept the default for Figure 5-4: Configuring Hardware
the Voice Capability parameter or open the drop-down list, and
choose the desired capability. appropriate voice capability. Figure 5-5 shows the voice
capability options for a CX950 when there is a DIM in slot 8.
4. Click in the I/O column. Open the drop-down list and choose
an I/O card.
5. Repeat steps 1 to 4 until the hardware configuration is
complete.
5.2 Modifying a Hardware Configuration
When configuring a voice capable CX product, it is important This section contains procedures for adding, deleting, and
to select the appropriate CPU software revision and the moving a card to another slot.

3008M300-004 5-47
CXTool User Guide

and they can all be configured by a single CXTool

configuration.

To configure a chassis, follow these steps.

1. In the Module Panel, select Hardware, then Card.
2. In the toolbar, click the Modify (+/-) button.
3. In the Number of Chassis parameter, Figure 5-6, enter the
number of chassis (the quantity of chassis) that you are about
to configure.
4. Choose the CPU slot, and the Revision number will
automatically be assigned.
5. Configure the Voice Capability and the I/O Card parameters as
required.

Figure 5-5: Configuring Software Revision and Voice Capability

5.2.1 Adding a CPU Card (CX2000 only)

As described in the CX2000 Hardware Manual, the CX2000

chassis can have up to four CPUs and 32 I/O cards.
Additionally, up to 4 CX2000 chassis can be interconnected Figure 5-6: Configuring Hardware on CX2000

5-48 3008M300-004
 5 CONFIGURING HARDWARE

NOTE: In the Module/CPU column shown in Figure 5-6, M1

refers to the first module, M2 refers to the second
module, and so on. The digit is the index of the CPU
module.

When the CX2000 is configured with multiple CPUs, select the

target CPU first, before going on to configure its service or
services. For instance, when configuring IP services on a
CX2000, together with many other services, the CPU must be
selected first (1 - M1, 9 - M2, 17 - M3, or 25 - M4, and so on)
from the Hardware CPU parameter, located in the Station
module of the IP folder. See Figure 5-7.

5.2.2 Configuring Multiple Chassis (CX2000 only)

With CXTool, the user can configure up to four CX2000s

chassis that are interconnected. It is important to note that the
numbering of the CPU slots and port is consecutive. To
configure multiple chassis, enter an appropriate number in the
Number of Chassis parameter, e.g., 2, 3, or 4. Figure 5-8 shows
that all four chassis have been configured and the user is
viewing the tab with the configuration for Chassis 1.

Figure 5-7: Configuring the CPU on a CX2000

3008M300-004 5-49
CXTool User Guide

Table 5-1: CX2000 Slot Allocation (cont.)

CXTool I/O CARD
CPU INDEX
CPU SLOT SLOT #•PORT #
M9 65 65.x - 72.x
M10 73 73.x - 80.x
M11 81 81.x - 88.x
M12 89 89.x - 96.x
M13 97 97.x - 104.x
M14 105 105.x - 112.x
M15 113 113.x - 120.x
M16 121 121.x - 132.x

NOTE: When the card is a DIM (T1/E1), the numbering uses

the format of slot.port, as in these examples:
105.1 and 105.2
Figure 5-8: Configuring Multiple Chassis on CX2000

The numbering of CPUs and cards is shown in Table 5-1. 5.2.3 Adding a CPU Card (CX1000e only)

Table 5-1: CX2000 Slot Allocation Adding a new CPU configuration to an existing hardware
configuration is straightforward if there is a sufficient number
CXTool I/O CARD of free card slots. If not, the user must first remove one or more
CPU INDEX
CPU SLOT SLOT #•PORT # I/O cards before adding the new CPU.
M1 1 1.x to 8.x
M2 9 9.x to 16.x NOTE: A newly added CPU card cannot be associated with
M3 17 17.x to 24.x preconfigured I/O cards that previously belonged to a
M4 25 25.x to 32.x different CPU.
M5 33 33.x to 40.x
To add a CPU, do the following:
M6 41 41.x to 48.x
1. In the Module Panel, expand the Hardware folder, and select
M7 49 49.x to 56.x Card.
M8 57 57.x to 64.x
2. In the toolbar, click the Modify (+/-) button.

5-50 3008M300-004
 5 CONFIGURING HARDWARE

3. Choose the CPU card slot and select the CPU type from the
drop-down list.
NOTE: Referring to Figure 5-9, if a CPU is added in slot 11,
then the current entry, “Analog Voice”, will be deleted.
4. Select the I/O card slot and choose an I/O card type from the
drop-down list.
5.2.4 Adding, Modifying, Deleting I/O Cards
CXTool allows the user to add new cards, and to modify or
delete them. To use any of these features, refer to Figure 5-10
and follow these steps.
1. In the Module Panel, expand the Hardware folder, and select
Card.
2. In the Main Panel, right click to view its context menu. Choose
Add New, Modify, or Delete. This is the only panel from which
the user is allowed to delete card configurations.

Figure 5-9: Hardware List for a CX1000e Figure 5-10: Hardware Dialog Box

WARNING: Deleting a CPU or I/O card also removes its

associated protocol configuration.

3008M300-004 5-51
CXTool User Guide

5.3 Change the Default Password

When a Memotec device is configured for the first time, the
user accepts the default password and configures the device
with it. However, it is recommended for security reasons that
this default password be changed. Follow these steps to change
a Memotec device password.
1. Complete the hardware configuration using any of the methods
described above.
2. In the Module Panel, expand the Hardware folder, and select
System Info.
3. Click the Modify button or select Modify from the Edit
pull-down menu.
4. In the System Information dialog, select the Console tab. The
screen shown in Figure 5-11 appears.

Change the password value as desired.

5.4 Changing SNMP Defaults

The SNMP settings are changed using the System Information
dialog. In the Module Panel, expand the Hardware folder, and Figure 5-11: System Information, Configuring Console
select System Info.
1. Click the Modify button or select Modify from the Edit pull-
down menu.
5.5 Operating System Defaults
2. In the System Information dialog, select the SNMP tab. The
screen shown in Figure 5-12 appears: Some operating system values can be examined through the OS
Parameters tab in the System Information dialog. In fact, these
Modify the Community name values as desired. values can be edited. However, it is strongly recommended that
these operating system parameters are not changed.

5-52 3008M300-004
 5 CONFIGURING HARDWARE

1. In the Module Panel, expand the Hardware folder, and select

System Info.
2. Click the Modify button or select Modify from the Edit pull-
down menu.
3. In the System Information dialog, select the OS Parameters tab.
The following screen appears:

Figure 5-12: System Information, Configuring SNMP

If it becomes necessary to change these parameters, here are

the steps.

NOTE: It is strongly recommended that no changes be made to

these operating system parameters.
Figure 5-13: System Information, OS Parameters Tab

3008M300-004 5-53
CXTool User Guide

5-54 3008M300-004
 6 CONFIGURING DRIVERS

The characteristics of the physical layer of a link are specified

in the configuration of drivers. Driver configurations include
link characteristics such as transmission speed and clock
source.

It is important that each driver be configured to match the

equipment and links to which it is attached.

This chapter has a section for each link type and the procedure
for configuring its driver with CXTool. The sections are:
• 6.1 Configuring an Async Driver
• 6.2 Configuring a Bisync Driver
• 6.3 Configuring an Ethernet Driver
• 6.4 Configuring a Synchronous Driver
• 6.5 Configuring a Token Ring Driver

3008M300-004 6-55
CXTool User Guide

6.1 Configuring an Async Driver

In asynchronous transmission, characters are sent at irregular
intervals. Each character is preceded by a start bit and followed
by a stop bit.

A CX device can accept async characters and transport them to

an async device across an X.25, ATM, IP, ISDN, or Frame
Relay network.

X.25, ISDN,
ATM, FR, IP

Asynchronous Asynchronous
CX Device CX Device
Packets Packets

Figure 6-1: CX Device, Async Packets, and Network

To configure an async driver, begin by opening the Driver

module. Select the Async component. Click on the Add (+)
button in the tool bar or select Add New from the pull-down
Edit menu. The screen that appears is shown in Figure 6-2.
3. Speed
Now, configure the parameters listed below.
1. Name
Enter a name for the driver.
2. I/O Port
This parameter allows the user to choose an async port.
Figure 6-2: Configuring an Async Driver
Determines the input and output speed in bits per second for
the port associated with this connection.
NOTE: When installing a Data Expansion Module, 134.5 bps
is the minimum speed supported on ports that are in
slots 5, 6, and 7.

6-56 3008M300-004

4. Character Size
Defines the character size, in number of bits, to be used on the
associated hardware port.
This value does not include the start, stop or parity bits.
5. Break Length
Defines the number of break characters to be transmitted on the
line when a reset is requested by the application port. A break
is an all-zeroes character without a stop bit(s).
6. Stop Bits
Defines the number of stop bits to be used on the associated
hardware port.
7. Port Traps Enable
Determines whether or not this port will send status change
traps.
8. Carrier Action Enable
Determines whether or not this port will inform the associated
application port that service is no longer available when its
associated hardware port has detected a loss of DCD or a loss
of DTR.
• Loss of Data Carrier Detect (DCD) if the port is physically
strapped as a DTE
• Loss of DTR (Data Terminal Ready) if the port is physically
strapped as a DCE.
9. Signal Down Timer
Defines the length of time, in seconds, after which the async
port will drop its signals when it has received a disconnect
request from the application port.
3008M300-004
6 CONFIGURING DRIVERS
10. Statistics Timer
Determines the period of time, in seconds, that is used to
measure the async driver’s performance and to collect
statistics.
11. Maximum Time Delay
Defines the maximum time, in milliseconds, for which the port
must wait before processing received characters.
12. Signal Sampling Period
Determines the sampling period, in 100 millisecond
increments, that the associated hardware port uses to sample
detectable signals.
13. DCD/DTR Samples
Defines the number of samples detected by the associated
hardware port before validating DCD or DTR signals.
• Data Carrier Detect (DCD) signals if the port is physically
strapped as a DTE
• Data Terminal Ready (DTR) signals if the port is strapped as
a DCE
14. TM/LL Samples
Defines the number of samples detected by the associated
hardware port before validating TM or LL.
• Test Mode (TM) signals if the port is physically strapped as
a DTE
• Local Loopback (LL) signals if the port is strapped as a DCE
6-57
CXTool User Guide
15. DSR/DRS Samples
Defines the number of samples detected by the associated
hardware port before validating DSR or DRS.
• Data Set Ready (DSR) signals if the port is strapped as a
DCE
• Data Rate Selector (DRS) signals if the port is physically
strapped as a DTE
16. CTS/RTS Samples
Defines the number of samples detected by the associated
hardware port before validating CTS or RTS.
BISYNC
• Clear To Send (CTS) signals if the port is physically
strapped as a DTE
• Request To Send (RTS) signals if the port is strapped as a
DCE
17. RI/RL Samples
Defines the number of samples detected by the associated
hardware port before validating RI or RL.
• Ring Indicator (RI) signals if the port is physically strapped
as a DTE
• Remote Loopback (RL) signals if the port is strapped as a
DCE
6.2 Configuring a Bisync Driver
Bisynchronous (BISYNC) transmission is a half-duplex,
character-oriented protocol that was developed by IBM for
synchronous transmission of binary-coded data between two
devices.
6-58
As shown in Figure 6-3, a CX device accepts bisync packets
and transports them transparently over a Frame Relay network,
that is, sends them and receives them, without looking at or
modifying the bisync stream.
Frame Relay
CX Device CX Device BISYNC
Figure 6-3: CX Device, Bisync Packets, and Network
To configure a bisync driver, begin by opening the Driver
module. Select the Bisync component. Click the Add (+)
button in the tool bar or select Add New from the pull-down
Edit menu. The screen shown in Figure 6-4 appears.
Now, configure the parameters listed below.
1. Clock Source
This parameter determines the active data clock source for this
port. This setting is locked to “internal” for ISDN ports.
The options available are as follows:
• internal: indicates that the transmit and receive clocks are
internally generated. The transmit clock is used for data
received by DCE. Data is sent on the falling edge of the
clock.
• external: indicates that the transmit and receive clocks are
externally supplied on separate pins. The transmit clock is
3008M300-004

Figure 6-4: Configuring the Bisync Driver, General Tab
used for data sent from DTE. Data is sent on the falling edge
of the clock.
NOTE: When the CX device is strapped for DCE then the
actual clock source is Internal.
When the CX device is strapped for DTE then the
actual clock source is External.
3008M300-004
6 CONFIGURING DRIVERS
• split: indicates that the transmit clock is internally generated
and the receive clock is externally supplied. The external
clocking is used for data sent from DTE and for data
received by DCE. Data is sent on the falling edge of the
clock.
• slave: indicates that the transmit and receive clocks are
externally supplied on the same pins. The transmit clocking
is used for data sent from DTE. Data is sent on the falling
edge of the clock.
2. Speed
This parameter determines the input and output speed in bits
per second for the port associated with this connection. The
speed should correspond to the network speed.
NOTE: This value is meaningful only if the parameter Clock
Source is set to 'internal' or set to 'split'. Otherwise, the
network determines the speed.
3. Port Duplex
This parameter determines whether or not this port
communicates simultaneously in both directions (full-duplex)
or alternates direction (half-duplex). The value in this
parameter must match the network setting.
4. Tx Queue Size
This parameter determines the maximum number of frames
that this port can hold before transmitting them. When this
value is 255, the system manages the number of buffers
devoted to different kinds of traffic. When this value is less
than 255, the system compares the value with its own and uses
the smaller one.
6-59
CXTool User Guide

5. Code Set
This parameter determines the character set used by this port.
The character set can be EBCDIC or ASCII.
6. Port - Look In
This parameter allows the user to configure a hardware port.
To continue with the configuration of this component, click on
the “Extended” tab. The screen shown in Figure 6-5 appears.
Configure the extended parameters of the bisync driver listed
below.
1. General group box - Max Frame Size
This parameter determines the maximum frame size (received
and transmitted) supported by the port associated with this
connection. If exceeded on the transmit side, an error message
is sent to the console port and the frame may or may not be
transmitted depending on available resources. On the receive
side, this parameter is only used by the IUSC driver (CX1000e
Secondary Serial I/O card) which truncates a frame received in
excess of this size.
2. General group box - Preamble Length
This parameter determines the minimum number of flags or
SYN pairs that are inserted between frames by the port
associated with this connection. This parameter applies to
Bisync frames. See Table 6-1 for the meaning of the values.

Table 6-1: Bisync Frames, Meaning of Preamble Length Values

Value Meaning
0 Causes one SYN pair to be inserted between frames (Same as value 1)

1 Causes one SYN pair to be inserted between frames (Same as value 0)

2 Causes two SYN pairs to be inserted between frames

3 Causes three SYN pairs to be inserted between frames

3. General group box - Statistics Timer

This parameter determines how often performance statistics are
updated. This value is measured in seconds. Note that if this
value is set to zero, performance statistics are not measured.
Figure 6-5: Configuring the Bisync Driver (Extended)

6-60 3008M300-004

4. General group box - Threshold Bandwidth
This parameter indicates the minimum bandwidth threshold
based on the external clock speed. Note that performance
statistics will consume resources. If the actual clock speed
drops below this value, frames specified in the filter are
discarded. The value entered must be a multiple of 1 kbps.
Note that if the port associated with this connection is a dial
port, then frames specified in filter are always discarded,
regardless of this bandwidth value.
5. Sampling group box - Sampling Period (Advanced Option)
This parameter determines the sampling period for the port
associated with this connection, in tenth of a second
increments. Control signals are read at the frequency you
specify with this parameter. This parameter has no meaning in
ISDN connections.
6. Sampling group box - DCD/DTR (Advanced Option)
This parameter determines the number of sampling periods
(defined in the Sampling Period parameter) that the port
associated with this connection waits before validating Data
Carrier Detect (DCD) or Data Terminal Ready (DTR) signals.
If the port is physically strapped as DTE, the port waits for
DCD signals; if the port is physically strapped as DCE, the port
waits for DTR signals.
7. Sampling group box - CTS/RTS (Advanced Option)
This parameter determines the number of sampling periods
(defined in the Sampling Period parameter) that the port
associated with this connection waits before validating Clear to
Send (CTS) or Request to Send (RTS) signals. If the port is
physically strapped as DTE, the port waits for CTS signals; if
the port is physically strapped as DCE, the port waits for RTS
signals.
3008M300-004
6 CONFIGURING DRIVERS
8. Sampling group box - DSR/DRS (Advanced Option)
This parameter determines the number of sampling periods
(defined in the Sampling Period parameter) that the port
associated with this connection waits before validating Data
Rate Selector (DRS) or Data Set Ready (DSR) signals. If the
port is physically strapped as DTE, the port waits for DRS
signals; if the port is physically strapped as DCE, the port waits
for DSR signals.
9. Sampling group box - RI/RL (Advanced Option)
This parameter determines the number of sampling periods
(defined in the Sampling Period parameter) that the port
associated with this connection waits before validating Ring
Indicator (RI) or Remote Loopback (RL) signals. If the port is
physically strapped as DTE, the port waits for RI signals; if the
port is physically strapped as DCE, the port waits for RL
signals.
10. Sampling group box - TM/LL (Advanced Option)
This parameter determines the number of sampling periods
(defined in the Sampling Period parameter) that the port
associated with this connection waits before validating Test
Mode (TM) or Local Loopback (LL) signals. If the port is
physically strapped as DTE, the port waits for TM signals; if
the port is physically strapped as DCE, the port waits for LL
signals.
11. Carrier group box - Carrier Action
This parameter determines whether or not this connection
informs its companion in the upper software layer that the port
has detected loss of DCD or DTR signals. If the port is
physically strapped as a DTE, the port waits for DCD signals;
6-61
CXTool User Guide
if the port is physically strapped as DCE, the port waits for
DTR signals. The options available are as listed below.
• disabled (box not checked): the companion connection is not
informed of service loss (locked for ISDN) (DCD is
ignored).
• enabled (box checked): the companion connection is
informed of service loss (DCD is monitored).
12. Carrier group box - Carrier Timer
If this port is configured as a DTE, the value in this parameter
determines the number of seconds that the port must wait for a
DCD signal after raising a DTR. If this port is configured as a
DCE, the value in this parameter determines the number of
seconds that the port must wait for a DTR signal after raising a
DCD. These signals are part of the initial attempt to establish a
connection.
In most cases this value should be zero because a pause
between signals is not necessary, or because these signals are
not used. In a dial-backup scenario however, a waiting period
should be specified.
This parameter has no meaning in ISDN connection.
Note that this value will be set to zero if the port does not
support an application that uses DTR and DCD signals.
13. Protocol
The options available are as follows:
• bsc3270: supports Bisync 3270 controllers
• borroughs: supports Borroughs controllers
• sperry: supports Sperry controllers
• bsc3780: supports Bisync 2780/3780 controllers
• aircat: supports Aircat500 air traffic radar controllers
• necbsc: supports NEC Bisync controllers
6-62
14. Dial Mode
This parameter determines the mode used for dial-up
connections. If this connection is used for dial backup
connections, then set this parameter to 'dial-out-only'. This
option ensures that a proper disconnection takes place when
the primary line comes back up after it has been down
(disabled). The options available are as follows:
• dial-in-only: indicates that only incoming calls are allowed
at this port. No outgoing calls can be made
• dial-out-only: indicates that only outgoing calls are allowed
at this port. No incoming calls are accepted
• dial-in-out: indicates that both incoming and outgoing calls
are allowed at this port
15. Parity
This parameter determines the type of parity used to
communicate with the Bisync device that is associated with
this port. This parameter does not apply to non-Bisync
interfaces.
The options available are shown in Table 6-2.
Table 6-2: Parity Parameter, Meaning of Options
Value Meaning
none indicates no parity
odd indicates odd parity
even indicates even parity
space indicates low parity (always 0s (zeros))
mark indicates high parity (always 1s (ones))
3008M300-004
 6 CONFIGURING DRIVERS

16. SS7 Idle Timer respectively. The user can also select 10Base-5 (also know as
Not supported in Bisync driver. the Attached Unit Interface [AUI]) for an Ethernet card.
17. Traps group box - Clock Trap
When this parameter is enabled, this port will send an SNMP X.25, ISDN,
trap message to the defined SNMP host monitoring station ATM, FR, IP
reporting that the port's transmit clock has changed state. See
NOTE about SNMP host IP address below.
18. Traps group box - Port Status Trap Ethernet: Ethernet:
When this parameter is enabled, this port will send an SNMP 10Base-T 10Base-T
CX Device CX Device
100Base-T 100Base-T
trap message to the defined SNMP host monitoring station 10Base-5 (AUI) 10Base-5 (AUI)
reporting that the hardware port has changed state. See NOTE
about SNMP host IP address below.
Figure 6-6: CX Device, Ethernet, and Network

NOTE: The SNMP host IP address for sending SNMP traps is To configure this service, open the Driver folder. Select the
defined in the Hardware folder under Ethernet module. Click on the Add (+) button in the tool bar or
System Information -->SNMP -->Trap Host. select Add New from the pull-down Edit menu. Figure 6-7
shows the window that appears.

Configure the parameters outlined below.

6.3 Configuring an Ethernet Driver 1. Connector Type
This parameter identifies the connector type used for the
The Ethernet driver allows the user to send and receive data
hardware port. CXTool will select the correct type
within a Local Area Network (LAN).
automatically. The options available are as follows:
CX devices support data transfer rate of 10 Mbps and 100 • auto: connector type detected automatically
Mbps, using the 10Base-T and the 100Base-T interfaces,
• aui: Attachment Unit Interface
• 10Base-T: 10 Mbps Ethernet
• 100Base-T: 100 Mbps Ethernet
2. Port
This parameter allows the user to add an Ethernet driver by
clicking on Add.

3008M300-004 6-63
CXTool User Guide

6.4 Configuring a Synchronous Driver

Synchronous transmission sends bits at regular intervals, using
a synchronized clock signal.

A CX device accepts synchronous packets and then transports

them across an X.25, ATM, IP, ISDN, or Frame Relay network
to a synchronous device.

X.25, ISDN,
ATM, FR, IP

Synchronous Synchronous
CX Device CX Device
Packets Packets

Table 6-3: Synchronous Packets, CX Device, and Network

To configure this service, open the Driver folder. Select the

Synchronous module. Click on the Add (+) button in the tool
Figure 6-7: Configuring the Ethernet Driver

3. Duplex - Full/Half
This parameter determines whether or not this port
communicates simultaneously in both directions (full-duplex)
or alternates direction (half-duplex) one way at a time.

6-64 3008M300-004

bar or select Add New from the pull-down Edit menu. The
window shown in Figure 6-8 appears.
Figure 6-8: Configuring the Synchronous Driver (General)
Configure the parameters outlined below.
1. Name
This parameter allows the user to change the default circuit
name. Choose a meaningful for ease of troubleshooting.
3008M300-004
6 CONFIGURING DRIVERS
2. Clock Source
This parameter determines the bit-rate clock source of the port
associated with this connection. When the user’s device acts as
Data Communications Equipment (DCE), then this should be
set to 'internal'. The options available are as follows:
• internal: indicates that the transmit and receive clocks are
generated internally
• external: indicates that the transmit and receive clocks are
supplied by the network
NOTE: When the CX device is strapped for DCE then the
actual clock source is Internal.
When the CX device is strapped for DTE then the
actual clock source is External.
• split: indicates that the transmit clock is generated internally
and receive clock is supplied by the network
• slave: indicates that the transmit and receive clocks are
supplied by the network on the same pins. This option is
usually used for X.21 ports
3. Speed
This parameter determines the clocking rate in bits per second
when a clock is provided for the port associated with this
connection.
NOTE: The value in this parameter is meaningful only if the
Clock Source parameter is set to “internal” or to
“split”; otherwise, the network determines the speed.
4. Port Duplex group box - Half/Full
This parameter determines whether the port associated with
this connection communicates simultaneously in both
6-65
CXTool User Guide
directions (full-duplex) or alternates direction (half-duplex)
one direction at a time. This value must match the protocol
setting. The options available are as follows:
• half: half-duplex
• full: full-duplex (locked for ISDN)
5. Tx Queue Size
This parameter determines the maximum number of frames
that the port associated with this connection can hold. When
this value is 255, the system automatically sets the number of
buffers. For voice applications, this parameter needs to be
modified. The relationship among buffer size, port speed, and
fragmentation size is described in 9.1.2 Typical Frame Relay
Configuration, in the subsection entitled Fragmentation.
6. SNA group box - Idle Line Condition
This parameter determines the idle line condition supported by
the port
associated with this connection. The idle line condition
specifies how the line is kept up when no data is being
exchanged. This value must match the attached SNA
equipment. The options available are as follows:
• flags: flags (7E) are sent when the line is idle
• marks: marks (FF) are sent when the line is idle
• as400: use this option for all IBM equipment
7. SNA group box - Encoding Method
This parameter determines the data formatting and encoding
method used by the port associated with this connection. Use
6-66
the option that matches the controller or Host settings. The
options available are as follows:
• nrz: NRZ (locked for ISDN 'D' channel; ISDN 'B' channel
can use only this value or NRZI-Space value)
• nrzi-mark: NRZI-Mark
• nrzi-space: NRZI-Space (ISDN 'B' channel can use only this
value or NRZ value)
NOTE: On the CX900e, ports 51x to 71x can use only NRZ or
NRZI-Space.
8. Port group box - Look in
Add a Synchronous Driver by clicking on Add.
To continue with the configuration of this module, click on the
“Extended” tab. The window shown in Figure 6-9 appears.
Configure the parameters as outlined below.
1. General group box - Max Frame Size
This parameter determines the maximum frame size (received
and transmitted) supported by the port associated with this
connection. If exceeded on the transmit side, an error message
is sent to the console port and the frame may or may not be
transmitted depending on available resources. On the receive
side, this parameter is only used by the IUSC driver (CX1000e
Secondary Serial I/O card) which truncates a frame received in
excess of this size.
2. General group box - Preamble Length
This parameter determines the minimum number of flags or
SYN pairs that are inserted between frames by the port
associated with this connection. This parameter is meaningful
3008M300-004

Figure 6-9: Configuring the Synchronous Driver (Extended)
for HDLC frames when Idle Line Condition is set to Flags.
Refer to Table 6-4.
3. General group box - Statistics Timer
This parameter determines how often performance statistics are
updated. This value is measured in seconds. Note that if this
value is set to zero, performance statistics are not measured.
3008M300-004
6 CONFIGURING DRIVERS
Table 6-4: HDLC Frames, Meaning of Preamble Length Values
Value Meaning
0 Causes flag sharing between frames
1 Means no flag sharing and zero flags inserted between
frames
2 Means no flag sharing and at least one flag inserted
between frames
3 Means no flag sharing and two flags inserted between
frames
4. General group box - Threshold Bandwidth
This parameter indicates the minimum bandwidth threshold
based on the external clock speed. Note that performance
statistics will consume resources. If the actual clock speed
drops below this value, frames specified in the filter are
discarded. The value entered must be a multiple of 1 kbps.
Note that if the port associated with this connection is a dial
port, then frames specified in filter are always discarded,
regardless of this bandwidth value.
5. Sampling group box - Sampling Period (Advanced Option)
This parameter determines the sampling period for the port
associated with this connection, in tenth of a second
increments. Control signals are read at the frequency you
specify with this parameter. This parameter has no meaning in
ISDN connections.
6. Sampling group box - DCD/DTR (Advanced Option)
This parameter determines the number of sampling periods
(defined in the Sampling Period parameter) that the port
associated with this connection waits before validating Data
Carrier Detect (DCD) or Data Terminal Ready (DTR) signals.
If the port is physically strapped as DTE, the port waits for
6-67
CXTool User Guide
DCD signals; if the port is physically strapped as DCE, the port
waits for DTR signals.
7. Sampling group box - CTS/RTS (Advanced Option)
This parameter determines the number of sampling periods
(defined in the Sampling Period parameter) that the port
associated with this connection waits before validating Clear to
Send (CTS) or Request to Send (RTS) signals. If the port is
physically strapped as DTE, the port waits for CTS signals; if
the port is physically strapped as DCE, the port waits for RTS
signals.
8. Sampling group box - DSR/DRS (Advanced Option)
This parameter determines the number of sampling periods
(defined in the Sampling Period parameter) that the port
associated with this connection waits before validating Data
Rate Selector (DRS) or Data Set Ready (DSR) signals. If the
port is physically strapped as DTE, the port waits for DRS
signals; if the port is physically strapped as DCE, the port waits
for DSR signals.
9. Sampling group box - RI/RL (Advanced Option)
This parameter determines the number of sampling periods
(defined in the Sampling Period parameter) that the port
associated with this connection waits before validating Ring
Indicator (RI) or Remote Loopback (RL) signals. If the port is
physically strapped as DTE, the port waits for RI signals; if the
port is physically strapped as DCE, the port waits for RL
signals.
10. Sampling group box - TM/LL (Advanced Option)
This parameter determines the number of sampling periods
(defined in the Sampling Period parameter) that the port
associated with this connection waits before validating Test
Mode (TM) or Local Loopback (LL) signals. If the port is
physically strapped as DTE, the port waits for TM signals; if
6-68
the port is physically strapped as DCE, the port waits for LL
signals.
11. Carrier Action
This parameter determines whether or not this connection
informs its companion in the upper software layer that the port
has detected loss of DCD or DTR signals. If the port is
physically strapped as a DTE, the port waits for DCD signals;
if the port is physically strapped as DCE, the port waits for
DTR signals. The options available are as listed below.
• disabled (box not checked): indicates that the companion
connection is not informed of service loss (locked for ISDN)
(DCD is ignored).
• enabled (box checked): indicates that the companion
connection is informed of service loss (DCD is monitored).
12. Carrier Timer
If this port is configured as a DTE, the value in this parameter
determines the number of seconds that the port must wait for a
DCD signal after raising a DTR. If this port is configured as a
DCE, the value in this parameter determines the number of
seconds that the port must wait for a DTR signal after raising a
DCD. These signals are part of the initial attempt to establish a
connection.
In most cases this value should be zero because a pause
between signals is not necessary, or because these signals are
not used. In a dial-backup scenario however, a waiting period
should be specified.
This parameter has no meaning in ISDN connection.
Note that this value will be set to zero if the port does not
support an application that uses DTR and DCD signals.
3008M300-004
 6 CONFIGURING DRIVERS

13. Protocol 16. Clock Trap

This parameter determines whether HDLC or Bisync is When this parameter is enabled, this port will send an SNMP
supported by this port. Note that only HDLC is supported by trap message to an SNMP host monitoring station indicating
ISDN and T1/E1 ports. The options available are as follows: that the port's transmit clock has changed state.
• hdlc: supports the HDLC protocol See NOTE about IP address of the SNMP host, below.

• ss7: SS7 Spoofing (Normal mode) 17. Port Status Trap

When this parameter is enabled, this port will send an SNMP
• ss7pcr: SS7 Spoofing (PCR mode) trap message to an SNMP host monitoring station reporting
14. SS7 Idle Timer that the hardware port has changed state.
This parameter determines the time (in msec) that the port must See NOTE about IP address of the SNMP host, below.
wait for an outgoing traffic to the network before sending a Fill
In Signal Unit (FISU) frame to the remote Global System for NOTE: SNMP traps are sent to the IP address of the SNMP
Mobile Communication (GSM) switch. This timer plus 500 host defined in the Hardware folder under
msec will determine the time that the port must wait for no System Information > SNMP > Trap Host
incoming traffic from the network before declaring the network
link DOWN and disable the SS7 spoofing to the GSM switch.
A value of 0 disables both features.
6.5 Configuring a Token Ring Driver
15. Dial Mode
This parameter determines the mode used for dial-up
NOTE: In CXTool, in the module navigation pane, under the
connections. If this connection is used for dial backup
module labeled Driver, there is a list of the link types
connections, then set this parameter to 'dial-out-only'. This
for which drivers can be configured.
option ensures that a proper disconnection takes place when
If there is no module component for Token Ring
the primary line comes back up. The options available are as
displayed, it may be necessary to change the version of
follows:
the CX software. The current version of the CX
• dial-in-only: indicates that only incoming calls are accepted software can be seen by selecting Card under the
at this port. No outgoing calls can be made Hardware module, in the module navigation pane, and
• dial-out-only: indicates that only outgoing calls can be made looking in the Revision column.
at this port. No incoming calls are accepted The Token Ring component is displayed only for
certain combinations of CX hardware and CX
• dial-in-out: indicates that both incoming and outgoing calls software.
can be established at this port
The Token Ring driver allows the user to send and receive data
within a Local Area Network (LAN).

3008M300-004 6-69
CXTool User Guide

CX devices support data transfer rates of 4 Mbps and 16 Mbps. 1. Speed

This parameter defines the input and output speed, in bits per
To configure this service, open the Driver folder. Select the second, for the associated hardware port. The options available
Token Ring module. Click on the Add (+) button in the tool bar are as follows:
or select Add New from the pull-down Edit menu. Figure 6-10 • speed_4_mbps: 4 Mbps ring speed
shows the window that appears.
• speed_16_mbps: 16 Mbps ring speed
2. Port
This parameter allows the user to add a Token Ring driver by
clicking on Add.
3. 4K Frame Size
When selected, the maximum frame size for Token Ring is
increased to 4 kB. When not selected, the default is 2.2 kB
(2200 bytes).

Figure 6-10: Configuring the Token Ring Driver

Configure the parameters outlined below.

6-70 3008M300-004
 7 CONFIGURING VOICE

This chapter describes how to configure voice on a Memotec

CX product using CXTool. Although users of this guide should
have a fundamental understanding of telephony, it may be
helpful to review some telephony basics before advancing to
the procedures. A general review of telephony is provided in
Chapter 22.

3008M300-004 7-71
CXTool User Guide
7.1 Memotec’s CX Products and the Voice
Environment
Memotec has a flexible voice architecture allowing users to set
up robust packet based voice networks that mimic the
functionality and flexibility of the PSTN based voice network.
The architecture allows for flexible routing of voice calls
(based upon number dialed), flexible regeneration of called
number information to remote stations, ample bandwidth
management functions for each remote destination, scaling of
packet voice network to a large number of sites, and a choice of
vocoders for toll quality compressed voice transmission.
Memotec’s CX products support both analog and digital
interfaces, together with PCM (G. 711), ACELP II, ADPCM
(G.726), and G.729 compression algorithms. The user can
configure the telephone signal interface such that it provides a
connection to any PBX or key system and supports all popular
telephony interfaces. Moreover, the voice module is
interoperable with Memotec’s analog and digital voice
products for maximum networking flexibility.
The user can configure voice on CX products and transport it
over Frame Relay, ATM, ISDN or IP.
7.1.1 Adding Voice to an Existing Data Network
The concepts applied in voice networking are similar to those
applied in data-networking design. What is different is the type
of equipment with which the network interfaces.
This section describes in general terms how the user can add
voice to an existing data network.
7-72
Create a The first step is to have a diagram of the sites that the user
Network would like to include in the proposed voice network. The sites
Diagram should be divided into head office, branches, and sub-branches.
Each of these sites may be further sub-divided according to
other considerations e.g., department, floor level, etc. This type
of administrative information is required to develop a logical
dialing plan.
In addition to the above, the user should also assess voice
traffic flow. There are different ways to profile voice traffic.
For instance, if the existing systems communicate with each
other through the public network, the traffic data can be
obtained from the call-detail reports. The pertinent variables to
be gathered are time of day, date, length of call, and
destination.
The call-detail report (in the case of leased lines) and/or
telephone bills should be analyzed and broken down into hour-
long increments, ideally over a one month period or more in
order to derive a total for each location in terms of number of
calls per hour/day/month, average call length per hour/day/
month, and total number of call minutes per hour/day/month.
The pertinent information should then be used to determine the
network’s peak traffic flow. There are several complex methods
for determining busy-hour calculation that involve statistical
analysis, probability theory, and extensive computation. A
simple method is described below.
1. Multiply the number of calls (initiated during the time interval)
with the average call duration during the interval to obtain the
call flow rate.
2. Add the call-flow rate per day for different durations (e.g., 9
AM to 10 AM).
3. Identify the time interval with the largest aggregate call-flow
rate.
3008M300-004
 7 CONFIGURING VOICE

4. Determine the average flow rate during the sample period 4. Number of Channels: Voice and Data.
(divide the sum by the number of days for which data were
5. Clocking Source: Internal or External.
collected).
6. Companding: Mu-law or A-law.
The traffic profile obtained from the above process should help
the user in determining the bandwidth and trunking 7. Type of Signaling:
requirements for each site and between each site. • T1 CAS Robbed Bit Signaling (Digital E&M, FXS, FXO)
Once the individual sites are organized, the next step is to • T1 CCS (ISDN)
gather information on the telephony equipment (e.g., PBX/key
system, analog phone or a fax machine) that will be connecting • E1 CAS (Digital E&M, FXS, FXO, MFC-R2, R2)
to the voice enabled devices (e.g., CX950) at each site. • E1 CCS (QSIG-GF)
8. ISDN Specific: Switch-type: 5ESS, 4ESS, DMS100, NI1, NI2,
Identify Secondly, the user should identify the connection type to a NET3, NET5, QSIG-BRI, or QSIG-PRI.
Connection PSTN and to voice-enabled devices.
Types The following is a sample of the type of information the user
The following is a sample of the type of information the user needs to record for WAN connections.
needs to record for analog connections. 1. Frame Relay
1. Interface Type: FXS, FXO, or E&M. • Physical WAN Interface:
2. E&M Type: Type: I, II, III, IV, or V; E&M implementation: 2- 56 Kbps, T1/E1
wire or 4-wire. 65 Kbps Clear Channel
Serial Interface, ISDN BRI or PRI
3. Off-hook Signaling: Loop Start, Ground Start, Immediate
Start, Delay-Dial, Wink. • Port
Network Interface: UNI (User/Network side), NNI
4. Additional Information.
LMI-type: ANSI Annex A/D, FR Forum
The following is a sample of the type of information the user • Per PVC
needs to record for digital connections: DLCI, CIR
1. Type of Interface: T1/E1, ISDN-PRI/BRI, QSIG-PRI/BRI,
SS7, Other.
2. Line Coding: AMI, B8ZS, or HDB3.
3. Framing: T1 SF(D4), T1 ESF, E1 MF, E1 CRC, or E1 non-
CRC.

3008M300-004 7-73
CXTool User Guide

2. ATM 1. Phone numbers/IP addresses should be assigned in a logical

manner, (e.g., according to head office, branches, sub-
• Physical WAN Interface:
branches, etc.), and the numbering plan should be compatible
T1/E1
with the external dialing schemes.
Mapping
Scrambling 2. Routing tables among PBXs/Memotec devices within a
corporation should be designed such that they are not only
• Port
logical but also scalable, i.e., they can be expanded to meet
Network Interface: UNI
growing demand.
• Per PVC
VPI/VCI
7.1.2 Examples of Voice Networks
• ATM Services
CBR, VBR (VBRrt, VBRnrt), UBR This section illustrates how the above three steps come
• Traffic Contract together in the field. Figure 7-1, Figure 7-2, and Figure 7-3
PCR, CDVT, SCR, MBS illustrate the steps involved in adding voice to a Frame Relay
CTD, CDV, CLR network with Memotec devices.

• Tunneling. Figure 7-1 represents the overall voice network as

conceptualized by the user. At this stage the user is simply
3. IP Transport
concerned with identifying voice devices (e.g., CX950), the
• Port WAN link, and phones.
Ethernet
Token Ring The user then adds relevant network details as shown in Figure 7-2.
Serial
First, all IP addresses related to IP telephony are added. Notice
that the details of the LAN environment have been omitted
Planning a Following an assessment of on-site resources and the because they are not relevant to the voice network.
Voice Network connection types, the next step is to develop a dialing plan for
the voice network within the context of the network diagram Second, all Frame-Relay links are identified, including the port
(mentioned in Step One). A dialing plan essentially associates speeds and the CIR of each PVC.
phone numbers/IP addresses to voice ports and it also identifies
call routing paths among voice-enabled devices in a voice Third, the relevant voice, LAN, and WAN ports are identified,
network. together with the type of voice interface for each voice port.

At the time of developing a dialing plan, the aspects mentioned

below should be considered.

7-74 3008M300-004
 7 CONFIGURING VOICE

CX950 (E) CX950 (E)

Branch Ethernet Branch

.10
PSTN CX950 (D) Office PSTN CX950 (D) ipv4:198.16.10 Office
s
10 Mbp

Head Quarter T1-CAS

Head Quarter

CX950 (F) PBX CX950 (F) T1

1.544 Mbps PBX
Ipv4: 198.16.40.12
T1
1.544 M
bps

Analog FXS
Frame Frame
Relay Relay CIR
CIR 256 kbps
512 kbps CIR
T1 384 kbps
1.544 Mbps FT1
CX950 (A) CX950 (A) 512 kbps

FT1
768 kbps
Branch Office CX950 (C) Branch Office CX950 (C)
Ipv4: 198.16.20.1
CX950 (B) Branch Office CX950 (B) Branch Office
Ipv4: 198.16.20.9

Branch Office slot- Branch Office

port
Key 1.1 Key Ipv4: 198.16.20.2
Analog
System - port System FXS
t
slo .1 Analog
2 Analog FXS
FXS

3.1 ort
slot-port slot-port

-p

t
slot
1.1 2.1

or
slo .1
t-p
4
slot-port slot-port
1.1 slot-port 3.1
2.1

Figure 7-1: Voice over Frame Relay Network: Basics Figure 7-2: Frame Relay-based Network: Adding Network Details

3008M300-004 7-75
CXTool User Guide

Finally, as shown in Figure 7-3, the user assigns phone numbers to discussion of Memotec’s dialing plan and other related
all the ports. Notice that in this example, the numbers have been features.
assigned without serious consideration to an existing dialing plan,
although they do adhere to the North American numbering plan, The sub-headings in this section correspond to the ones used in
that is, (xxx) yyy-zzzz. the Voice folder of CXTool.

CX950 (E)
Voice Station In this module the user configures the CPU on a CX product
Ethernet
PSTN CX950 (D) ipv4:198.16.1
0.10
Branch
Office
and the basic parameters for voice services.
10 Mbps
T1-CAS
Head Quarter

Local Port This module allows the user to configure the port by
CX950 (F) T1
PBX
Ipv4: 198.16.40.12
1.544 Mbps
configuring the following sub-modules: Voice Channel and
T1
1.544 M
bps Digital Signaling Processing (DSP) Channel.
Analog FXS
Frame • Channels
Relay CIR Extensions 5000 - 5999
8 phones
CIR
512 kbps CIR
256 kbps Channels are logical connections that are associated with a
x4001 - x4008 T1 384 kbps
1.544 Mbps FT1
physical port. A DSP provides voice encoding and/or digital to
CX950 (A) 512 kbps
analog conversion of one or more voice channel(s).
FT1
768 kbps
Branch Office CX950 (C)
Ipv4: 198.16.20.1
An analog port has one channel and a digital port has 2 to 30
CX950 (B) Branch Office
Ipv4: 198.16.20.9
channels.
slot- Branch Office
port
1.1 Key Ipv4: 198.16.20.2
Analog
3001 t-
slo .1
port System Analog
FXS • Voice/IP and DSP Channels
2 Analog FXS
FXS Voice channels are used to define the signaling for each voice
3.1 ort

slot-port slot-port
call, and DSP channels are used for voice compression.
p
slot-

ort

3002 1.1 2.1

slo .1
t -p
4

x2001 x2002
slot-port slot-port
1.1
x1001
slot-port
2.1
3.1
x1003 The number of voice and DSP channels associated with a port
x1002
3003 3004
depends upon the type of interface (e.g., analog or digital). For
instance, analog cards on CX1000e have one voice and one DSP
Figure 7-3: Frame Relay-based Network: Complete Network channel per physical port; the T1 and E1 cards have 24 and 30
voice channels, respectively per port. Each digital voice card
can support up to 30 DSP channels, by adding specific hardware
7.1.3 Configuring Voice on CX Products: An Overview
(DVDB cards). An ISDN BRI connection has two voice chan-
This section describes the method used to configure voice nels.
services on Memotec devices with CXTool. It also explains Channels may be combined to facilitate “channel hunting”.
some of the terms that the user will encounter during
configuration. Figure 7-3 is the reference for the following

7-76 3008M300-004
 7 CONFIGURING VOICE

• Channel Hunting • Remote Extension

This feature is best illustrated with an example. Remote extension is used to route the call inside one of
According to the scenario in of Figure 7-3, and the detail shown Memotec’s CX devices.
in Figure 7-4, the CX950 is configured such that when a caller • Called Number
dials 3000, the call is received by the first available port/chan- Called number represents the digits dialed out from one of
nel. For more information see 7.2 Voice Configuration. Memotec’s CX devices at the remote end.

CX950 The manner in which the above-mentioned values are built is

decided by the “dial pattern”. Evey entry in the dialing plan (1
of 64) can be used to build the “remote extension” and “called
slot-p
3000 4 lines sharing number”. The “dial pattern” is used as a selector of those
ort Ext. 3000
1.1
Key entries.
t -p
o rt System
Extensions 3001 slo
2.1
3001 - 3499 Analog
FXO
Memotec’s dialing plan is very versatile. It is, therefore,
3.1 ort
t-p

important that the user understand the pattern matching rules

t

3002
slo

por
4.1
slot-

in order to take full advantage of its inherent flexibility.

Extensions 3500 - 3999 Table 7-1 outlines the characters and symbols that the user can
enter to construct a pattern for each of the above-mentioned
Figure 7-4: Port/Channel Hunting parameters.

Alternatively, the user can associate a local extension with a

particular channel (i.e., time slot) by selecting “one-to-one
hunt,” thereby allowing a call to be directed to a specific exten-
sion.
Dialing Plan As mentioned in section 7.1.1, following is a way to assess on-
site resources and connection type requirements that the user
needs to develop a dialing plan for a voice network.
Memotec’s dialing plan is composed of three parameters: dial
pattern, remote extension, and called number
The dialing plan is used to transform the digits dialed by the
user to the following two values:
Internal For every digit that is dialed by the user, the “dial pattern” of
Working of every entry is scanned starting from the first entry (Index # 1)
the Dialing and ending at the last, which could be up to Index # 64. As
Plan soon as a match is found, the “remote extension” and “called
number” are built, using the rules described in Table 7-1.
First, the “remote extension” is built, given that it is used for
routing the call to the remote CX device. In effect, what this
implies is that the “remote extension” is used to route the call
to the “local extension” of the remote CX device.
It is important to note that when the “dial pattern” is matched,
there is a possibility of the “remote extension” not yet being
built because all the digits have not yet been processed. For

3008M300-004 7-77
CXTool User Guide

Table 7-1: Dialing Plan Guidelines Table 7-1: Dialing Plan Guidelines (cont.)
Example: Dialed Digits are 444 6261, Remote Extension is 44 Example: Dialed Digits are 444 6261, Remote Extension is 44

Characters Characters
Where Where
and Example Description and Example Description
Applicable Applicable
Symbols Symbols
x, X Dial Pattern 4xx x is a wildcard. 0-9, #, * Dial Pattern 444 Indicates that the user can enter
xxxx Remote 20 digits from 0-9, the # symbol, or the *
Extension 9--- symbol in each of the parameters. In
‘blank’ Dial Pattern ++- ---- Blank spaces may be used between Called Number ++++ our example, 444 is entered as the
Remote parameters to improve readability. Dial Pattern and it requires an exact
Extension match from the dialed digits. The
Called Number Remote Extension of 20 implies this
is the number that will be used for
+ Remote ++- ---- “+” indicates the digit in the routing this call. In the Called
Extension corresponding position is copied Number parameter, digit 9 is added,
Called Number from the dialed digits and used as digits 444 are ignored, and digits
the Remote Extension or the Called 6261 are copied and forwarded
Number. If the pattern in our (together with digit 9) to the
example is used to construct the destination of the voice call.
Remote Extension, then 44
becomes the number that is used for > Called Number --- > Indicates that Memotec devices will
routing the call. If the pattern is used reconstruct the called number from
to construct the Called Number, then the digit sequence following the >
44 is copied and forwarded to the symbol. Thus in our example, 444 is
destination of the voice call. ignored and 6261 copied and
forwarded to the destination of the
- Remote --- --++ “-” indicates the digit in the voice call.
Extension corresponding position is ignored
Called Number from the dialed digits when < Called Number 2556 < Indicates that Memotec devices will
constructing a Remote Extension or reconstruct the called number from
the Called Number. In our example, the digit sequence before the <
the first five digits (i.e., 444 62) are symbol. In our example, 2556 is
ignored when constructing the added and the dialed digits (444
Remote Extension or the Called 6261) are ignored. Note that in the
Number. absence of < symbol, Memotec
devices will forward the dialed digits
as extra digits.

7-78 3008M300-004

example, let us assume that the user is dialing 3002 and
configures the dialing plan parameters as shown in Table 7-2.
Table 7-2: Configuring the Dialing Plan (Example 1)
Dial Pattern Remote Extension Called Number
3xx ++++ 514 -- +++ -
Note that the CX device will wait for the user to dial all the four
digits (since that is the number of digits specified in the “remote
extension” parameter) before building a “remote extension”. If the
“dial pattern” finds a match for the first three digits ( “300”),
the “remote extension” will not be built until the digit “2” has
been received (i.e., dialed).
Lets take another example. Let us assume that the user is
dialing 30027 and configures the dialing plan as shown in
Dialing Plan •
Table 7-3.
Parameters
Table 7-3: Configuring the Dialing Plan (Example 2)
Dial Pattern Remote Extension Called Number
3xx +++ - + 514 -- +++ -
In this scenario, the CX device will wait for the user to dial all
the five digits (since that is the number of digits specified in the
“remote extension” parameter) before building a “remote
extension”. Using the rules in Table 7-1, the CX device will
build the following “remote extension”: 3007.
In both cases, as soon as the “remote extension” is built, a
signaling message is sent to verify whether or not the remote
CX device can be reached. If it can, then the “called number” is
constructed. Here again, the same building rules are used as in
the case of the “remote extension”. In other words, the “called
number” is built only when all the digits are received (i.e.,
3008M300-004
7 CONFIGURING VOICE
dialed), at which point a signaling message is sent to the
remote CX device to try and “connect” the remote CX device
to its attached equipment.
Lets say that the user dials 300274 and configures the “called
number” parameter as shown in Table 7-2 and Table 7-3. Note
that only after all six digits have been received, the following
“called number” will be built: 514027
It is important to remember that the “remote extension” has no
real meaning for the user, given that it is used only for the
purpose of routing calls between Memotec’s CX devices. The
“called number”, on the other hand, has a very important
meaning to the user because it may be regenerated by the
remote customer unit (e.g., PBX).
Dial Pattern
The pattern entered in this parameter is used as a match against
the digits dialed by the user (e.g., 418-249-5005). Based on the
type of pattern entered in this parameter, Memotec devices route
the call across the network to the remote Memotec device.
In the example we are using, the user may decide to configure
this parameter such that only the first three digits (“418” or
“4xx” or “xxx”) are used for routing the call and the remaining
digits are disregarded.
• Remote Extension
This parameter is used to derive the remote extension that the
user is trying to reach. Depending upon the pattern defined by
the user in this parameter, Memotec devices will construct a
remote extension from the called number. Unless otherwise
specified, all the dialed digits represent the called number.
In our example, let us assign “500” to the Remote Extension at
CX950 (E). Thus, in the dialing plan, the user may enter “500”
or use the following pattern to construct the remote extension
7-79
CXTool User Guide
from the called number (4182495005): “--- --- +++” which indi-
cates that the first six digits be ignored and only three digits
(i.e., 500) be used to construct the Remote Extension. When this
call is received by CX950 (D), it looks for a local extension that
matches the extracted remote extension (500). Upon realizing
that there is none, it forwards the call to CX950 (E). Since, at
this location, the local and remote extensions match, the call is
received, a called number is constructed based on the pattern
entered in the Called Number parameter, and then forwarded to
the remote PBX.
The user can configure 256 Local Extensions per port on
CX950, 128 on CX1000e (DI600), and 64 Local Extensions per
port on CX800, CX900, and FX600.
• Called Number
In this parameter, the user enters the number of the called party.
Depending upon the number of digits accepted by the PBX con-
nected to CX950 (E), the user may configure CX950 (E)
accordingly. For instance, if the remote PBX is able to handle
only four digits, the user could configure this parameter such
that only the last four digits (5005) from the called number are
forwarded to the PBX. In this case, the user could enter the fol-
lowing pattern: “--- --- >” (implying that “418249” be ignored
and “5005” be forwarded).
Digit When this service is enabled on a remote Memotec device (e.g.,
Regeneration CX950 (E)), it generates the outbound digits on the basis of
any one of the user-specified options listed below.
• Called Number
The called number is a number to be forwarded. It is generated
7-80
from the value in the “Called Number” parameter (e.g.,
“2495005”).
• Local Extension
The local extension is a number to be forwarded and it is
generated from the value in the “Local Extension” parameter
(e.g., “500”).
• all
The number to be forwarded is to be generated using both the
value in the “Local Extension” and “Called Number”
parameters (e.g., “500” and “2495005”).
The regeneration feature is versatile enough to generate a
number other than the one that is dialed. For instance, in the
above-mentioned example, if the PBX connected to CX950 (E)
expects a “20” before the telephone extension number, then
CX950 (E) can be configured to add “20” before the telephone
extension (“5005”) by using the following pattern: “--- --- 20>”
which indicates that the first six digits (from the dialed
number) be ignored, “20” be inserted, and “5005” be
forwarded.
Group ID This sub-module in the Dial Plan module allows the user to
combine a number of Remote Extensions into a group that is
identified by a reference number (e.g., 101). The association of
several extensions to a Group ID facilitate the hunting across
local extension hunt groups. Note that CX products can accept
up to 512 Group IDs.
• Local Book
This sub-module allows the user to define the Local Extension
of a port/channel or a group of ports/channels for hunting. The
3008M300-004

Local Extension is used by the remote device to build a route to
the Home Extension at which the call will received.
• PIN Number
The Personal Identification Number may be used as a security
code for access to the CX network. PIN Numbers may be used
to keep track of long-distance calls by designated users and
record voice billing information.
Bandwidth The user has the option of managing bandwidth by allocating a
Group certain amount to specific services. For instance, if the
bandwidth parameter is enabled for voice calls, then the user
can allocate a part of the total bandwidth for voice and the
remaining bandwidth for data or other applications. In the
absence of this allocation, voice will have no restriction on
bandwidth.
Trunk Once the Local Port module, Dialing Plan module, and where
applicable the Bandwidth module have been configured, the
user should proceed to configure either the WAN Trunk or an
IP Trunk.
• The WAN Trunk allows the user to select from among the
following options:
• FRDLCI: sends voice traffic across a Frame Relay network
• ATMVCL: sends voice traffic across an ATM network
• FR Bundle: sends voice traffic to a Frame Relay multicast
group
• IP Tunnel: sends voice traffic from one Memotec device to
another Memotec device via an IP routed network
• X.25 Service Point
3008M300-004
7 CONFIGURING VOICE
• The IP Trunk allows the user to send voice traffic across an IP
routed network to any device that is compliant with the ITU-T
H.323 standards.
NOTE: In both the WAN Trunk and the IP Trunk, the value in
the Route - Pattern parameter defines the rule to route a
call to a particular Remote Extension.
Advanced This module comprises the sub-modules listed below.
Definitions
• Digit
In this sub-module, the user defines the manner in which digits
are forwarded (e.g., tone or pulse).
• Call Progress Tones
In this sub-module, the user configures the different tones (e.g.,
busy, dial, etc.).
• Channel Associated Signaling (CAS)
In this sub-module, the user configures the voice signaling
parameters for CAS, It is a type of signaling in which the circuit
state is indicated by one or more bits of signaling status sent
repetitively and associated with that specific circuit or channel.
On the Transmit side, the parameters are configured in compli-
ance with the signaling requirements of a PBX and on the
Receive side, they are configured in compliance with the signal-
ing requirements of a Memotec device.
• Multifrequency Compelled (MFC-R2)
MFC-R2 is a part of CAS. When E1MFCR2 is set as the default
configuration in the CAS sub-module, the MFC-R2 sub-module
allows the signaling parameters to be refined.
7-81
CXTool User Guide

• Common Channel Signaling (CCS)

Local Site Remote Site
In this sub-module, the voice signaling parameters for CCS are Analog Voice FXS V.35 card Analog Voice FXS V.35 card
in slots 7 & 8 in slot 2 in slots 7 & 8 in slot 2
configured. It is a type of signaling in which a group of circuits
share a signaling channel. Its implementation in Memotec
CX950 CX950
devices allows the user to interface with digital networks. (C) (E)

The next section illustrates how the above steps are used to FRAME
RELAY
DLCI=100
configure a typical voice network with Memotec CX devices.

EXT 2002
7.1.4 Typical Voice Network EXT 2001
EXT 5005
EXT 5001

The user can configure a voice network that transports voice Figure 7-5: Voice Over Frame Relay
over a Frame Relay, or an ATM network. In the examples
below, we use the basic network layout in Figure 7-3 as a point • DSP Channel
of reference to illustrate the various ways in which a typical Analog Voice FXS 7.1
voice network may be configured. Vocoder Group: acelpII
• Dialing Plan: (digits dialed: 418-249-5005)
Voice Over Figure 7-5 illustrates a case of voice being transported across a Dial Pattern: 4XX (implies use first three digits dialed)
Frame Relay Frame Relay network. Remote Extension: --- --- +++
(means, use first three of last four digits dialed, i.e.,
Both, the local and remote sides have a CX950, each of which “500”)
has two analog voice cards and a Frame Relay (V.35) card. Called Number: --- --- >
(means, forward last four digits dialed to the remote
Let us assume that the caller at telephone extension 2002 telephone equipment)
would like to reach the caller at extension 5005 (see also
• WAN Trunk
Figure 7-1). In order for this call to go across a Frame Relay
Frame Relay Station (CPU)
network, the user configures the modules/sub-modules and
Frame Relay Port: V.35H 2.1
parameters on CX950 (C) with CXTool as described below.
Link: Sync Driver
• Voice Station: CPU on CX950 Frame Relay: DLCI - 100
• Voice Channel • Voice Pattern: xxx
Analog Voice FXS 7.1 (The compression parameters are configured automatically.)
Home Extension: 200 This call will be routed across the network based upon the
Local Extension: 200

7-82 3008M300-004
 7 CONFIGURING VOICE

pattern used in this parameter, which should match the

pattern in the Remote Extension parameter.
• Digit: Default Configuration: DTMF Standard
• Call Progress Tones: Default Configuration: USA
• Signaling Type: Analog FXS Loop Start.

The next section focuses primarily on how to configure Voice

services on Memotec devices with CXTool. It adheres to the
sequence in CXTool and provides a description of all the
parameters the user will encounter during configuration.

7.2 Voice Configuration

The Voice folder in CXTool contains all the modules/sub-
modules and parameters associated with Voice, including
Station, Local Port, Dialing Plan, Bandwidth Group, Trunk,
Advanced Definition.

7.2.1 Configuring the Voice Station

From the Voice folder, select the Voice Station module. To add
a voice station, click on the Add (+) button in the tool bar or
select Add New from the pull-down Edit menu. The following
screen will appear:
Configure the parameters listed below.
1. Name
This parameter allows the user to change the default name.
2. Hardware CPU
Configure a CPU on a CX Product.
Figure 7-6: Configuring the Voice Station
3. Ring Power Trap
When this parameter is enabled, messages are sent to the
network management console each time a change occurs in the
functional state of the ring generator power supply of the
Analog Voice I/O card AC/DC supply.
4. Call History
The three parameters of Call History (mentioned below) permit
the user to configure the voice history features of the CX

3008M300-004 7-83
CXTool User Guide

devices, which are used by the CXView program at the time of in the tool bar or select Add New from the pull-down Edit
generating voice statistics for each call. menu. The screen shown in Figure 7-7 appears:
5. Call History - Buffer Size
This parameter determines the maximum number of calls in the
history table.
6. Call History - History Trap
When this parameter is enabled, a call history trap is generated.
7. Call History - Trap Trigger Threshold [%]
This parameter determines the percentage of the history table
that must be filled before a trap is sent to the management
station. The ‘0’ (%) indicates the generation of a trap for each
call.

NOTE: The user can determine the correct value for the Buffer
Size and Trap Trigger Threshold parameters by having
prior information on the number of calls per minute
and the size of the network.

7.2.2 Configuring the VoIP Station

For VoIP services, select the VoIP Station module from the
Voice folder. To add a VoIP station, click on the Add (+) button
Figure 7-7: Configuring the VoIP Station

Configure the parameters listed below.

1. Local Address
This parameter refers to the local IP address of the primary IP
interface. When configured, it is used as the default source IP
address in the outgoing VoIP packets.

7-84 3008M300-004

2. RAS Enable
When this parameter is enabled, call signaling is done through
a gatekeeper using Registration Admission and Status (RAS)
function.
3. RAS - Gatekeeper
When this service is enabled, a gatekeeper can be accessed by
Memotec devices to provide call control services (i.e., address
translation, admission control, bandwidth control, and zone
management) to registered users. (For further information, see
Chapter 25 INTRODUCING IP).
4. RAS - Discovery
The options available for this parameter are as listed below.
ipv4: represents the IP address of the gatekeeper in decimal
notation.
mcast: allows the use of multicast discovery mechanism.
dns: represents a host name that can be resolved into an IP
address by a DNS server.
5. E164 Alias
This parameter indicates the local alias (i.e., a telephone 7.2.3 Configuring the Local Port
number) that
complies with E-164 ITU Recommendations. This alias is sent
to the gatekeeper during registration. DSP Channel From the Local Port module in the Voice folder, select the DSP
6. H.323 Alias
This parameter indicates the local alias as H.323 ID string
(alphanumeric) that is sent to the gatekeeper during
registration.
Advanced The remaining parameters in this module are advanced
functions. It is recommended that they not be modified. A
description of the advanced parameters is provided below
primarily for information.
3008M300-004
7 CONFIGURING VOICE
1. Max Number of Calls
This parameter indicates the maximum number of
simultaneous active
incoming and outgoing calls on all VoIP ports and routes.
2. Max Number of VoIP Channels
This parameter indicates the maximum number of VoIP
channels that can be configured.
3. Signaling Port
This parameter indicates the destination port for H.225
signaling. In UNIX environment, any port below 1024 is
reserved for system processes; the ones between 1024 and
5000 are automatically assigned. H.225 recommends port
1720.
4. RAS Port
The RAS Port is one of two ports used for RAS protocols. By
default, port 1718 is used for multicast gatekeeper discovery
and 1719 for all other RAS exchanges.
Channel sub-module. Click on the Add (+) button in the tool
bar or select Add New from the pull-down Edit menu. The
screen shown in Figure 7-8 will appear.
Configure the parameters listed below.
1. DSP channel State
Enable this parameter to activate the DSP channel.
7-85
CXTool User Guide

4. Click on Add to add a DSP Channel. The screen shown in

Figure 7-9 will appear:

Figure 7-8: Configuring the DSP Channel

2. DSP Channel - Vocoder Group

This parameter indicates the vocoder group associated with the
DSP channel being configured. The options are grouped by
compression schemes.
3. Hardware Card Type
This parameter identifies if the Voice Station chosen is either
Analog or Digital.
Figure 7-9: Adding a Hardware Port
Following the addition of the desired cards, the user will revert
back to the screen shown in Figure 7-8.
5. Impedance
This parameter indicates the input/output line impedance of the
analog FXS, FXO or E&M interfaces. Note that impedance for
the SLIM FXS/FXO/E&M is not software configurable, but

7-86 3008M300-004

hardware configurable. More information is available in the
device-specific Hardware Reference Manual.
6. E&M Type
The E&M type is not software configurable, but hardware
configurable. More information is available in the device-
specific Hardware Reference Manual.
Voice Channel From the Local Port module in the Voice folder, select the
Channel sub-module. Click on the Add (+) button in the tool
bar or select Add New from the pull-down Edit menu. The
following screen, Figure 7-10, appears:
Advanced The remaining parameters in this module are advanced
Figure 7-10: Configuring the Voice Channel
3008M300-004
7 CONFIGURING VOICE
Configure the parameters listed below.
1. Interface Type
This parameter allows the user to configure an Analog, T1/E1,
ISDN, or BRI interface type.
2. One-To-One DSP Hunt
When this parameter is enabled, there is a one-to-one
relationship between an Interface Channel and a DSP Channel.
This parameter is applicable only to digital interfaces.
3. Interface Channel
This parameter allows the user to configure the voice channel
on the selected interface.
4. DSP Channel Hunting
This parameter allows the user to configure the DSP
channel(s). Note that in Figure 7-10 since a DSP Channel and a
Port have already been configured, they appear in the Voice
Channel dialog box. Transfer the Interface Channel from the
“Available” column to the “Chosen” column, and in the DSP
Channel Hunting section, select the range of channel to be
hunted.
5. Voice Channel Enable
When this parameter is checked, this voice channel is enabled.
6. PIN Enable
When the Personal Identification Number (PIN) parameter is
enabled, the security feature is enabled.
functions. It is recommended that they not be modified. A
description of the advanced parameters provided below is
primarily for information.
7-87
CXTool User Guide
1. Skew Compensation
This parameter indicates the type of skew (or jitter)
compensation.
2. Max Skew
This parameter indicates the number of milliseconds of skew or
jitter for which the end-to-end synchronization algorithm must
compensate.
3. Echo Cancellation
When this feature is enabled, the local echo (heard by the
remote end) is cancelled.
4. Fast Connect box.
This parameter is applicable to incoming calls. If the Fast
Connect box is enabled, then the establishment of the
connection between the local and remote equipment is initiated
as soon as the Remote Extension is detected (according to the
Dial Plan). If this parameter is disabled, then this connection is
established only after the Called Number has been completely
dialed (according the Dial Plan).
5. Fax NSF Suppression
When the Non Standard Facility (NSF) option is enabled, the
control frame content is suppressed in order to allow
interoperability between different fax machines. When this
feature is disabled, the control frame content is transported
transparently.
6. Protocol Type Validation box.
When enabled, this parameter permits end-to-end connection
between similar protocols to carry User-to-User, Facility and
Notify Messages and Information Elements in a transparent
manner. If the protocols are different, there is a possibility of
the above-mentioned information not reaching its destination
in its entirety.
7-88
7. In-Band Signal - Outgoing Call Alerting
This parameter indicates whether or not an action is taken
when an Alerting signal is received from the local equipment
for outgoing calls.
8. In-Band Signal - Outgoing Call Progress
This parameter indicates whether or not an action is taken
when a progress message is received from the local equipment
for outgoing calls.
9. In-Band Signal - Incoming Call Alerting
This parameter indicates whether or not an action is to be taken
when an Alerting signal is received from the local equipment
for incoming calls.
10. Outgoing Called Number - Completion
When this parameter is enabled, it indicates that the
regeneration scheme must be completed before the calls are
initiated. When disabled, this parameter indicates that the calls
are initiated as soon as the called number is regenerated.
11. Outgoing Called Number - Inter Digit Timeout
This parameter indicates the length of the duration (in
milliseconds) for which no digits may be received before the
number of digits entered is considered complete. Note that
when this parameter is enabled, the “outgoing Called Number -
Completion” parameter must be disabled.
12. Calling Party Code in Global Directory (Incoming)
This parameter specifies the Global Directory Table index that
determines the calling party number and subaddress that are
used for incoming calls.
13. Calling Party Code in Global Directory (Outgoing)
This parameter specifies the Global Directory Table index that
determines the calling party number and subaddress that are
used for outgoing calls.
3008M300-004
 7 CONFIGURING VOICE

Click on the Next tab in the Voice Channel 1 dialog box. The 3. Call Progress Tone
following screen appears: This parameter configures the frequency and cadence of Dial,
Busy, Reorder, and Ring Back tones. Two profiles have been
pre-configured, USA and UK, which correspond to the
frequencies for these countries. However, a range of up to
thirty-two is possible. In order to facilitate configuration, the
two predefined profiles can be used as a template to create
customized configuration.
4. Digit Signaling.
This parameter indicates the dialing method of the channel.
5. MFC-R2
Configure the Multifrequency Compelled (MFC-R2)
parameter as explained in the section on Advanced Definition
(MFC-R2).
6. Dialing Plan
Configure this parameter by following the steps outlined in
7.2.4 Configuring the Voice Dial Plan.
7. Regeneration Mode
Configure this parameter (if required) by following the steps
outlined in 7.2.4 Configuring the Voice Dial Plan, section
titled Regeneration Table.
8. Audio Vocoder (Preferred)
Figure 7-11: Configuring the Voice Channel (continued)
This parameter indicates the preferred vocoder algorithm of the
compressed voice stream on the voice channel.
Voice Configure the parameters listed below.
9. Audio Vocoder (Alternate)
Channel 2
1. CCS This parameter indicates the alternate vocoder algorithm and
Enable this parameter if the CCS signaling is used. speed (in bits per second) of the compressed voice stream on
the voice channel.
2. Signaling Type
This parameter indicates the type of digit signaling used on this
voice channel.

3008M300-004 7-89
CXTool User Guide
10. Fax Capability
This parameter determines the fax relay capability. It is used to
configure the maximum speed that fax data can be transmitted
on the voice channel.
11. Gain [dB] - Tx
This parameter indicates the value defining the gain of the
output voice stream. This gain increments by 1dB steps.
12. Gain [dB] - Rx
This parameter indicates the value defining the gain of the
input voice stream. This gain increments by 1dB steps.
13. V.110 Capability
This object determines the V.110 relay capability (in bits per
second).
14. Emulation Mode
This parameter indicates the extent to which Memotec devices
emulate protocols on this channel. The options available are as
listed below.
• low: device waits first for remote acknowledgement and then
for an answer from the remote equipment connected to the
network, before completing the call.
• medium: device gives a local acknowledgement but waits for
an answer from the remote equipment connected to the
network, before completing the call.
• high: device gives a local acknowledgement and a local
answer before completing a call.
VoIP Channel From the Local Port module in the Voice folder, select the IP
7-90
The following are broad emulation guidelines recommended
for CCS:
• If the Memotec device is connected to a PBX, emulation
level should be low.
• If the Memotec device is connected to a public network or to
a satellite link, emulation level should be high.
• For CAS, medium level emulation is recommended.
However, if the delay is less than 100 ms, low level
emulation could be selected for optimization.
15. Home Extension
This parameter determines the extension on which a call should
be received. The value in this parameter should match that in
the Local Extension parameter (see Local Book sub-module in
the Dialing Plan module).
If the user leaves this field blank, CXTool will use, as the Home
Extension, the same value that is entered in the Local Extension
parameter.
16. AutoDial Pattern.
This parameter indicates the digit pattern to be automatically
inserted when initiating a call. It is similar to the “speed dial”
function on regular telephones.
17. Connection Type
This parameter indicates the method of connection used by the
channel.
Channel sub-module. Click on the Add (+) button in the tool
bar or select Add New from the pull-down Edit menu. The
following screen will appear.
3008M300-004
 7 CONFIGURING VOICE

3. Permission
This parameter indicates how H.323 calls are received or
generated. The options available are as follows:
• bothways: incoming calls can be accepted and outgoing calls
generated on this port
• outgoing: only outgoing calls can be generated on this port
• incoming: only incoming calls can be accepted on this port
4. Next Hop - Name
This parameter identifies the address of the H.323 end point,
together with the channel that is configured for all the outgoing
calls. Unless otherwise specified, the same channel can be used
for incoming calls as well.
5. Next Hop - Resolution
This parameter indicates the method used to find out the IP
address of the H.323 endpoint. The options available are as
listed below.
• ipv4: represents an IP address in decimal dotted notation
• ras_e164id: represents a telephone number that complies
with the E-164 ITU Recommendations, and which is
Figure 7-12: Configuring the VoIP Channel

Configure the parameters listed below.

1. Home Extension
This parameter indicates the local extension assigned to the
VoIP port. It is used only for incoming calls.
2. Address Mask
This parameter indicates the mask that is used on an incoming
call with an IP address, which is assigned to the port that can
match the IP address.

3008M300-004 7-91
CXTool User Guide
resolved by a GateKeeper into an IP address using the RAS
protocol (for future use).
• ras_h323id: represents an H323 ID string (alphanumeric),
which is resolved by a Gatekeeper into an IP address using
the RAS protocol (for future use).
• ras_urlid: represents and URL string which is resolved by a
Gatekeeper into an IP address using the RAS protocol (for
future use).
Advanced The remaining parameters in this module are advanced
• ras_emailid: represents an E-Mail ID string, which is
resolved by a GateKeeper into an IP address using the RAS
protocol (for future use).
• dns: represents a host name which can be resolved into an IP
address using the DNS protocol. This is necessary on a LAN
where a DHCP server dynamically assigns the IP address of
a device (TBD) (for future use).
6. Dialing Plan
This parameter allows the user to configure the Dialing Plan.
For details on how to configure this parameter,
see7.2.4 Configuring the Voice Dial Plan.
7. Regeneration Mode - Control
This parameter allows the user to add or modify a digit
regeneration entry. See “Digit Regeneration” on page 7-80, and
“Regeneration Table” on page 7-94 for further details.
8. Bandwidth - Max
This parameter is used by active calls. If any incoming or
outgoing call uses more than the bandwidth specified in this
parameter, it is cleared. A 0 value means that there is no
bandwidth limitation.
9. Bandwidth - Call Max
This parameter indicates the maximum bandwidth that an
individual call can have from a port’s total bandwidth. It is
7-92
normally used to filter out high-bandwidth vocoders like G.711
during the capability negotiation phase. A 0 value means that
there are no bandwidth restrictions.
10. Bandwidth - Group (Enable)
This parameter allows the user to select one of the predefined
bandwidths in the Voice Bandwidth Group module.
functions. It is recommended that they not be modified. A
description of the advanced parameters is provided below
primarily for the purpose of information.
1. PIN Enable
When this parameter is enabled, the called number is first
matched against the defined Personal Identification Numbers.
If no match is found, the call is rejected.
2. Fast Start Enable
When this parameter is enabled, the outgoing calls can be
generated and incoming calls can be accepted using the H.323
fast start mechanism. When disabled, a slow start mechanism is
used for incoming and outgoing calls. Note that a fast start call
can be forced to become a slow start call on the transmit side.
The same, however, is not true in the opposite direction: an in-
coming slow start call cannot be converted to a fast start
call.Dialing Plan
3. Header Compression-Enable
This parameter enables the Real Time Protocol (RTP) header
compression for calls originating in the local VoIP route.
4. Precedence
If this parameter is set to 0, the default IP precedence is used
for calls originating on this route, otherwise one of the eight IP
precedence levels is used (7 being the highest).
3008M300-004
 7 CONFIGURING VOICE

5. Regeneration Digit Timer 7.2.4 Configuring the Voice Dial Plan

This parameter indicates the timeout period (in milliseconds)
that the regeneration scheme will use when the regeneration
control is disabled. This parameter applies to instances when Dial Plan From the Dialing Plan module in the Voice folder, select the
the VoIP channel is configured as a port. Table Dialing Plan
sub-module. To add a dial plan table, click on the Add (+)
6. Vocoder ID button in the tool bar or select Add New from the pull-down
This parameter provides an ID to a vocoder configuration. Edit menu. The following screen will appear:
7. Vocoder Edit -MaxPkt
This parameter defines the vocoder selected for voice
compression. To create new vocoder groups or to change the
default value(s), click on Add or Modify, respectively. Alter the
value(s) and click on Save.
8. Vocoder Edit - Payload Type
This parameter defines the payload type for G.729 and G.723
when between 76 and 127. To create new vocoder groups or to
change the default value(s), click on Add or Modify,
respectively. Alter the value(s) and click on Save.
9. Vocoder Edit - Delay Jitter
This parameter indicates the maximum acceptable delay jitter
that is used for negotiation during the signaling phase. To
create new vocoder groups or to change the default value(s),
click on Add or Modify, respectively. Alter the value(s) and
click on Save.
10. Vocoder Edit - Audio (Preferred)
This parameter indicates the preferred vocoder algorithm of the
compressed voice stream on the VoIP channel.
11. Vocoder Edit - Audio (Alternate)
This parameter indicates the alternate vocoder algorithm and
speed (in bits per second) of the compressed voice stream on
the VoIP channel. Figure 7-13: Configuring the Voice Dial Plan

3008M300-004 7-93
CXTool User Guide
In the event that the user has more than one network, the Dial
Plan Table can be used to configure two plans: Plan 1 and Plan
2. In each Plan, CXTool permits the user to have a maximum of
64 entries with entry number 1 having the highest priority and
entry number 64 the lowest.
To insert an entry in between existing entries, highlight the
index number where the entry is to be made and click the insert
key on the key pad.
Configure the parameters listed below for Plan 1 or Plan 2.
1. Dialing Pattern
This parameter is used as a “matching” pattern against the
digits dialed by the user. The range of values may be as
follows: 0 to 32 digits, *, #, and wildcard (“x”). The “ ” (blank)
character can be used in any position to improve reliability. For
further information see section 7.1.3 Configuring Voice on CX
Products: An Overview, section entitled: Dialing Plan.
2. Remote Extension/Group ID
Relying on a set of construction rules to add digits, remove, or
select them, this parameter builds the Remote Extension/Group
ID from the digits dialed by the user.
The construction rules permit the use of the following values: 0
to 32 digits
(0 to 9), *, #, - and +.
The “-” indicates that the digit in the corresponding position is
ignored from the incoming digits.
The “+” indicates that the digit in the corresponding position is
copied from the inbound digits.
The “ ” (blank) character can be used in any position to
improve reliability.
Notice that the Remote Extension is the number within the
routing table that is assigned to the side that is receiving the
call. For further information see section 7.1.3 Configuring
7-94
Voice on CX Products: An Overview, section entitled: Dialing
Plan.
3. Called Number
Relying on a set of construction rules to add digits, remove, or
select them, this parameter builds the Called Number from the
digits dialed by the user.
The construction rules permit the use of the following values: 0
to 32 digits,
(0 to 9), *, #, -, +, <, and >. The “-” indicates that the digit in
the corresponding position is ignored from the incoming digits.
The “+” indicates that the digit in the corresponding position is
copied from the inbound digits. The “ “ (blank) character can
be used in any position to improve reliability. The “>” indicates
that all the buffered digits from that position will be included;
“<“ indicates that no digits should be included. For further
information see section 7.1.3 Configuring Voice on CX
Products: An Overview, section entitled: Dialing Plan.
WARNING: Two entries with the same Dialing Pattern, Remote
Extension/Group ID, and Called Number are not
permitted.
Regeneration From the Dialing Plan module in the Voice folder, select the
Table Regeneration sub-module. Click on the Add (+) button in the
tool bar or select Add New from the pull-down Edit menu. The
following screen will appear:
Configure the parameters listed below.
3008M300-004
 7 CONFIGURING VOICE

• local extension: the local extension’s digits are used as

outbound digits
• called_nb: the called number’s digits are used as outbound
digits
• all: the local extension’s digits and the called number’s digits
are used as outbound digits. For further information see
section 7.2.4 Configuring the Voice Dial Plan.
2. Pattern
This parameter indicates the pattern that filters the outbound
digits. If the parameter is left blank then the digits to be
generated are those specified by the Regeneration parameter.
3. Numbering Plan
This parameter is applicable to ISDN connections. It indicates
the numbering plan used by the regeneration group. The
options available are as listed below.
• transparent: regenerates the number received from the call
originator
• unknown: sets the numbering plan to “unknown”
• isdn_telephony: sets the numbering plan to “ISDN”
• national_standard: sets the numbering plan to “national”
• private: sets the numbering plan to “private”.
For further information see section 11.2.2 Configure the
Figure 7-14: Configuring Voice Regeneration ISDN Data Service Point.

1. Code Mode
This parameter indicates which numbers are used to generate
the outbound digits. The options available are as listed below.
• none: no digits received from the remote endpoint are used
(Called Number)

3008M300-004 7-95
CXTool User Guide

4. Number Type select Add New from the pull-down Edit menu. The following
This parameter indicates the Number Type that is used by the screen will appear:
regeneration group. The options available for this parameter
may be classified into the three groups mentioned below.
• Number Type common to all numbering plans: a)
transparent: the received number is sent as is b) unknown or
automatic: the Type is set automatically.
• Number Type associated with ISDN or National numbering
plan: a) international; b) national: c) net_specific; d)
subscriber; e) abbreviated.
• Number Type associated with a Private service: a)
level2_reg; b) level1_reg; c) pisn_specific; d) level0_reg.
For further information see section 11.2.2 Configure the
ISDN Data Service Point.
5. Number Digit
When enabled, this parameter indicates the number of digits
that are used to set the boundary of the automatic Number
Type.

Voice Group ID From the Dialing Plan module in the Voice folder, select the
Group ID
sub-module. Click on the Add (+) button in the tool bar or
Figure 7-15: Configuring the Group ID

Configure the parameters listed below.

1. Group ID
This parameter allows the user to associate a group of remote
extensions by a single identification number.
2. Remote Extensions
This parameter indicates the remote extensions (within the
routing table) that are included in the Group ID.

7-96 3008M300-004
 7 CONFIGURING VOICE

NOTE: The user is not allowed to configure two Group IDs

with the same number or assign the Group ID the same
number as Remote Extension within it.

3. Connection Type
This parameter determines the connection type. The options
available are as listed below.
• link_confirm: establishes the connection with the first
available Memotec port or voice channel at the remote
• connect_confirm: establishes the connection with the first
available subscriber at the remote
• broadcast: establishes a point-to-multipoint connection with
one way voice traffic from the calling end to the multiple
remote called voice ports
4. Number of Stations Polled
This parameter indicates the maximum number of remote voice
stations in an Extension Group that the local voice station polls
with a single call request.

Local Book From the Dialing Plan module in the Voice folder, select the
Group ID sub-module. Click on the Add (+) button in the tool
bar or select Add New from the pull-down Edit menu. The
following screen will appear:
Figure 7-16: Configuring the Local Book
Configure the parameters listed below.
1. Local Extension - Extension
The Local Extension is the number assigned to a local port.
The value in this parameter and in the Home Extension
parameter (see the Channel sub-module in the Local Port
module) must be the same.
If the user leaves the Home Extension parameter blank, CXTool will
use the value entered in the Local Extension parameter as its Home
Extension.

3008M300-004 7-97
CXTool User Guide

2. Local Extension - Type select Add New from the pull-down Edit menu. The following
This parameter defines the type of the local extension: cas_ccs screen will appear:
or voip.
3. One-To-One Hunt
This parameter allows the user to associate one time slot/
channel to one local extension. The value in the Local
Extension parameter is associated with the first channel.
CXTool assigns the remaining local extensions to each channel
that is configured for a One-To-One Hunt. For instance, in
Figure 7-1, the One-To-One Hunt feature is enabled for
channels 8.2.1 through to 8.2.7, and the Local Extension has
the value of 200. CXTool associates Channel 8.2.1 to Local
Extension 200, Channel 8.2.2 to Local Extension 201, and so
on.
4. Hunted Channels
This parameter allows the user to configure channels that will
be hunted when a particular local extension (associated with
these channels) is dialed. The range available to the user will
depend upon the type of CX product selected by the user. For
example, if the CX product is CX1000e, a maximum of three
Digital Voice I/O cards and six Digital Voice Channeling cards
can be inserted in the chassis. If we assume that the Digital
Voice I/O card is in slot 1, then the range of channels that can
be hunted will be from 1.1.1 to 1.1.24, where the first digit (1)
represents the slot, the second digit (1) represents the port, and Figure 7-17: Configuring the Personal Identification Number
the digit (1 or 24) represents the channel associated with the T1
port. Configure the parameters listed below.
5. Hunt Mode 1. Enable Pin Code
This parameter defines the way the local voice channels in a 2. PIN Length (in digits)
hunt group are polled when a call is being established. This parameter indicates the length of the Personal
Identification Number (PIN), which is entered for security
purposes.
PIN Table From the Dialing Plan module in the Voice folder, select the
PIN sub-module. Click on the Add (+) button in the tool bar or

7-98 3008M300-004
 7 CONFIGURING VOICE

3. PIN Code
This parameter indicates the PIN that is validated by the local
voice station before a call is established. The number of digits
in this parameter must match the number entered in the PIN
Length parameter.

NOTE: Two entries containing the same PIN code are not
permitted.

7.2.5 Configuring the Voice Bandwidth Group

From the Voice folder, select the Bandwidth Group module. To

make entries to this Group, click on the Add (+) button in the
tool bar or select Add New from the pull-down Edit menu. The
following screen will appear:

Figure 7-18: Configuring the Bandwidth Group

Select the Name and the corresponding Bandwidth (in Kbps)

for each bandwidth group. This table defines the global
bandwidth management parameters.

3008M300-004 7-99
CXTool User Guide

7.2.6 Configuring the Trunk 1. Transport Link

This parameter identifies the type of network across which a
call will be routed. The options available are listed below:
WAN Trunk From the Trunk module in the Voice folder, select the WAN
Trunk sub-module. Click on the Add (+) button in the tool bar • FRDLCI: sends voice traffic across a Frame Relay network
or select Add New from the pull-down Edit menu. The • ATMVCL: sends voice traffic across an ATM network
following screen will appear:
• FR Bundle: sends voice traffic to a Frame Relay multicast
group
• IP Tunnel: sends voice traffic from one Memotec device to
another Memotec device via an IP routed network
• X.25 Service Point
2. Reference
This parameter is similar to an ID for an end-to-end payload on
a circuit. It is relevant if the outbound circuit supports the
multi-protocol encapsulation option, whereby each outbound
voice/fax frame carries an extra 2-bytes proprietary header
derived from RFC-1490.
3. Remote X.25 DTE
This parameter allows the user to configure the Remote DTE
when the WAN connection is configured as X.25 Service Point.
4. Bandwidth
This parameter is used to monitor all the calls received and to
keep track of the bandwidth utilization on a particular source
route. If a call exceeds the configured bandwidth, it is rejected.
When the bandwidth is set to 0, Bandwidth Management is
disabled. Once the bandwidth value is configured, the system
Figure 7-19: Configuring the WAN Trunk needs to be restarted for the value to take effect.
5. Hop Counter
Configure the parameters listed below.
This parameter indicates the number of hops through which a
voice packet will routed before being dropped. A value of 0
will allow a locally generated voice call to travel over voice

7-100 3008M300-004
 7 CONFIGURING VOICE

route to another node, but it will not be routed further from that configured as 200, then the value in this parameter must be 200
node. or 2xx. The range of values that this parameter accepts are as
6. Secondary Trunk follows: 1 to 8 characters; 0 to 9 digits; and the letter “x” or
“X”.
When enabled, this parameter allows the user to configure a
second trunk which carries signaling information. 12. Route - WanDelay
7. Bandwidth Group This parameter indicates the round trip delay on the WAN link.
This parameter determines whether or not a certain bandwidth 13. Route - G711, G726 ADPCM_40 Kbps, G726 ADPCM_32
group will be used. If this parameter is enabled then the user Kbps, G726 ADPCM_24 Kbps, G726 ADPCM_16 Kbps,
can use a particular bandwidth group. G729, G723_6.3 Kbps, G723_5.3 Kbps, ACELPII 8 Kbps,
ACELPII_5.8 Kbps
8. Group
These are voice compression parameters. They are configured
This parameter allows the user to select from a number of pre- automatically, although they are user-configurable.
configured bandwith groups. Add a bandwidth group (if not
already added) by following the step in section
7.2.5 Configuring the Voice Bandwidth Group. Secondary When this trunk is configured, the signaling information of the
9. Time Division Multiplexing (TDM) Trunk primary voice system route may be transported over the
Secondary Trunk. And if the primary link goes down, this
This parameter indicates the type of voice route network that is
trunk may act as the backup.
in use. Time Division Multiplexing (TDM) networks are
essentially point-to-point networks where the dialed number is From the Trunk module in the Voice folder, select the Secondary
not used for routing the voice packets. The overhead of the Trunk sub-module. Click on the Add (+) button in the tool bar or
voice packet is minimized (from 3 to 6 bytes to 2 to 3 bytes, select Add New from the pull-down Edit menu. Alternatively, from
depending upon the channel number. For instance, if there are
less than 32 simultaneous calls, only 2 bytes of voice route
overhead are required, otherwise 3 bytes are required.
Notice that if the “TDM” box is left unchecked, this parameter
is set to Switched. This option is used in networks where voice
packets are routed or switched depending on the dialed
number.
10. Add a Voice Station (if not already added).
11. Route - Pattern
This parameter routes a call across the network. The value of
this parameter must match the value entered in the Remote
Extension parameter. For example, if the Remote Extension is

3008M300-004 7-101
CXTool User Guide
the the WAN Trunk sub-module, simply enable the Secondary
Trunk. The following screen, Figure 7-20, appears:
Figure 7-20: Configuring the Secondary Trunk
To create a Secondary Trunk, enable the “Outbound Signaling”
and/or “Backup” parameters and configure a transport link.
To configure the remaining parameters, refer to the
descriptions provided in the WAN Trunk section.
IP Trunk From the Trunk module in the Voice folder, select the IP Trunk
sub-module. Click on the Add (+) button in the tool bar or
7-102
select Add New from the pull-down Edit menu. The following
screen, Figure 7-21, will appear:
Figure 7-21: Configuring the IP Trunk
Configure the parameters listed below.
1. Next Hop Name
This parameter identifies the address of the H.323 end point
and it uses the local VoIP port for all the outgoing calls. Unless
specified otherwise, the same port can be used for outgoing as
well as incoming calls.
3008M300-004

2. Next Hop Resolution
This parameter indicates the method used to find out the IP
address of the H.323 endpoint which uses the local VoIP port to
send and receive calls. The options available are as listed
below.
• ipv4: represents an IP address in decimal dotted notation
• ras_e164id: represents a telephone number that complies
with the E-164 ITU Recommendations, and which is
resolved by a
GateKeeper into an IP address using the RAS protocol
• ras_h323id: represents an H323 ID string (alphanumeric),
which is resolved by a GateKeeper into an IP address using
the RAS protocol
• ras_urlidRAS/URLID: represents and URL string which is
resolved by a
GateKeeper into an IP address using the RAS protocol
• ras_emailid: represents an E-Mail ID string, which is
resolved by a GateKeeper into an IP address using the RAS
protocol
• dns: represents a host name which can be resolved into an IP
address using the DNS protocol. This is necessary on a LAN
where a DHCP server dynamically assigns the IP address of
a device (TBD).
3. Permission
This parameter indicates the types of calls that are permitted on
the voice channels associated with this configuration. The
options available are as listed below.
• outgoing: this voice channel can generate calls
• incoming: this voice channel can receive calls
• bothways: this voice channel can generate and receive calls
3008M300-004
7 CONFIGURING VOICE
4. Route - Pattern
This parameter routes a call across the network. The value
entered in this parameter must match the value entered in the
Remote Extension parameter. For example, if the Remote
Extension is configured as 200, then the value in this parameter
must be 200 or 2xx. The range of values that this parameter
accepts are as follows: 1 to 8 characters; 0 to 9 digits; and the
letter “x” or “X”.
5. Route - WanDelay
This parameter indicates the round trip delay on the WAN link
in milliseconds.
6. Route - G711, G726 ADPCM_40 Kbps, G726 ADPCM_32
Kbps, G726 ADPCM_24 Kbps, G726 ADPCM_16 Kbps,
G729, G723_6.3 Kbps, G723_5.3 Kbps, ACELPII 8 Kbps,
ACELPII_5.8 Kbps
These are voice compression parameters. They are configured
automatically, although they are user-configurable.
7. In the Bandwidth Group section, check the Enable box and add
a bandwidth group (if not already added) by following the steps
in section 7.2.5 Configuring the Voice Bandwidth Group.
8. Advance - Precedence
This parameter allows the user to set the Quality of Service
(QoS) priority on a scale from 0 to 7. If this parameter is set to
0, the default IP precedence is used for calls originating on this
route, otherwise the one specified by the user is used.
9. Advance - Header Compression Enable
When this parameter is enabled, the Real Time Protocol (RTP)
header compression is activated for calls originating in the
local VoIP route.
10. Advance - Max Bandwidth per Call
This parameter allows the user to reserve a certain amount of
bandwidth (from the total bandwidth) for an individual call.
7-103
CXTool User Guide

This function is generally used to filter out the high bandwidth

vocoders like G.711 during the capability negotiation phase. A
value of 0 means no bandwidth limitations have been imposed
on an individual call.
11. Advance - Bandwidth (Kbps)
This parameter allows the user to indicate the maximum
bandwidth that a route can have at any given moment. If any
incoming or outgoing call uses more than the bandwidth
allocated in this parameter, that call is cleared. A value of 0
means that no bandwidth limitations have been imposed on this
route.

7.2.7 Configuring the Advanced Definition

Digit From the Advance Definition module in the Voice folder, select
the Digit sub-module. Click on the Add (+) button in the tool
bar or select Add New from the pull-down Edit menu. The
screen shown in Figure 7-22 appears.

Configure the parameters listed below.

1. Signaling Name
This parameter allows the user to change the default name. The Figure 7-22: Configuring Voice Digit
characteristics of this parameter are based on the preconfigured
setting selected in the Default Configuration parameter. 4. Activate the MF, DTMF, Pulse, or the Hook Flash service in
the Receive Detection column by checking the appropriate box.
2. TransportMode Enable
When this parameter is enabled, the DTMF, MF tones, pulse
and hook flash detection and generation are activated. Advanced The remaining parameters in this module are advanced
functions. It is recommended that they not be modified. A
3. Activate the MF, DTMF, Pulse, or the Hook Flash service in description of the advanced parameters is provided below
the Transmit Generation column by checking the appropriate primarily for information.
box.

7-104 3008M300-004
 7 CONFIGURING VOICE

1. MF (ms) - Time On Min (Rx) 10. Pulse - Nominal Make Time (Tx)
This parameter indicates the minimum on time during MF tone This parameter defines the nominal make time during a pulse
detection. digit
2. MF (ms) - Time Off Min (Rx) detection.
This parameter indicates the minimum off time during MF tone 11. Pulse - Time Interval
detection. This parameter defines the time between two digits during a
pulse digit
3. MF (ms) - Nominal On Time (Tx) generation.
This parameter indicates the nominal on time during MF tone
detection. 12. Hook Flash - Break Time Min
This parameter defines the break time during a hook flash
4. MF (ms) - Nominal Off Time (Tx) detection.
This parameter indicates the nominal off time during MF tone
detection. 13. Hook Flash - Break Time Max
This parameter defines the break time during a hook flash
5. MF (ms) / DTMF (ms) - Time Interval (Tx) detection.
These parameters indicate the time between two digits during
MF and DTMF tone detection. 14. Hook Flash - Nominal Break Time
This parameter defines the nominal break time during a hook
6. Pulse - Break Time Min (Rx) flash generation.
This parameter defines the minimum break time during a pulse
digit 15. Out of Band
detection When enabled, this parameter is used for ISDN connections
that use out-of-band digits. When this parameter is disabled, it
7. Pulse - Break Time Max (Rx) can be used for connection that require an in-band frequency
This parameter defines the maximum break time during a pulse i.e., between 300hz and 3.30 Khz. Note that for analog
digit connections, this parameter must remain unchecked.
detection
16. Tone Delay - After Connection
8. Pulse -Validation Time (Rx) This parameter indicates the delay after the local connection
This parameter defines the waiting time before starting to has been
validate a pulse digit during a detection. established and before a tone is generated.
9. Pulse - Nominal Break Time (Tx) 17. Tone Delay - After Flash
This parameter defines the nominal break time during a pulse This parameter indicates the delay after the hook flash has been
digit signaled and before a tone is generated.
detection.

3008M300-004 7-105
CXTool User Guide
Call Progress From the Advance Definition module in the Voice folder, select
Tones the Call Progress Tones sub-module. Click on the Add (+)
button in the tool bar or select Add New from the pull-down
Edit menu. The screen shown in Figure 7-23 appears.
Advanced The remaining parameters in this module are advanced
Figure 7-23: Configuring the Call Progress Tones
Configure the parameters listed below.
7-106
1. Country Name
This parameter allows the user to enter the name of the country
from where the call is being made e.g., Germany.
2. Transmit - Dial, Busy, Reorder, and Ringback
On the transmit side, the user can enable those call progress
tones that s/he requires.
functions. It is recommended that they not be modified. A
description of the advanced parameters is provided below
primarily for information.
1. Dial
This is the constant tone that is heard when the telephone line
is off-hook. The Time On/Off parameter indicates the duration
for which the constant tone lasts.
2. Busy
This is a tone that is heard in intervals of first time on, first time
off, second time on and second time off, followed by a
repetition of the aforementioned ringing pattern. This tone
indicates that the called number is engaged.
3. Reorder
This type of tone generated by the values in this parameter
indicates that there is a problem within the network. The tone is
heard in intervals of first time on, first time off, second time on
and second time off, followed by a repetition of the
aforementioned ringing pattern.
4. Ringback
The type of tone generated by the values in this parameter
indicates that the remote telephone is ringing. The tone is heard
in intervals of first time on, first time off, second time on and
3008M300-004

second time off, followed by a repetition of the aforementioned
ringing pattern.
CAS From the Advanced Definition module in the Voice folder,
select the CAS sub-module. Click on the Add (+) button in the
tool bar or select Add New from the pull-down Edit menu.
Click on the General tab. The screen shown in Figure 7-24 will
appear:
Figure 7-24: Configuring CAS
Configure the parameters listed below.
3008M300-004
7 CONFIGURING VOICE
1. Name
This parameter allows the user to change the default name. The
characteristics of this parameter are based on the preconfigured
setting selected in the Default Configuration parameter
2. Default Configuration
This parameter is a 32 character parameter that describes the
current configuration row. The selection in the parameter is
based upon the upon the Interface Type (Analog, T1, or E1).
3. In the Transmit column, configure the ABCD signaling bits (in
binary format) for the parameters listed below.
• Idle: this parameter indicates the value that is used for
signaling an Idle (on hook) state.
• Seize: this parameter indicates the value that is used for
signaling a Seizure
Forward state.
• Seize Acknowledge: this parameter indicates the value that is
used for
signaling a Seizure Acknowledge state.
• Answer: this parameter indicates the value that is used for
signaling an Answer (off hook) state.
• Clear Forward: this parameter indicates the value that is used
for signaling a Clear Forward state. It can include wildcards
(*).
• Clear Backward: this parameter indicates the value that is
used for signaling a Clear Backward state.
7-107
CXTool User Guide

• Release Guard: this parameter indicates the value that is used • Clear Forward: this parameter indicates the value that is used
for signaling a Release Guard state. for detecting a Clear Forward state. It can include wildcards
(*).
• Ring On: this parameter indicates the value that is used for
signaling a Ringing On state. • Clear Backward: this parameter indicates the value that is
used for
• Ring Off: this parameter indicates the value that is used for
detecting a Clear Backward state.
signaling a Ringing Off state.
• Release Guard: this parameter indicates the value that is used
• Busyout: this parameter indicates the value that is used for
for detecting a Release Guard state.
signaling a Busy Out state.
• Ring On: this parameter indicates the value that is used for
• Fault: this parameter indicates the value that is used for
detecting a Ringing On state.
signaling Fault state.
• Ring Off: this parameter indicates the value that is used for
• Busy: this parameter indicates the value that is used for
detecting a Ringing Off state.
signaling a Busy state.
• Busyout: this parameter indicates the value that is used for
• Reorder: this parameter indicates the value that is used for
detecting a Busy Out state.
signaling a Reorder state.
• Fault: this parameter indicates the value that is used for
• Unavailable: this parameter indicates the value that is used
detecting Fault state.
for signaling an Unavailable state.
• Busy: this parameter indicates the value that is used for
4. In the Receive column, configure the ABCD signaling bits (in
detecting a Busy state.
binary format) for the parameters listed below.
• Reorder: this parameter indicates the value that is used for
• Idle: this parameter indicates the value that is used for
detecting a Reorder state.
detecting an Idle (on hook) state.
• Unavailable: this parameter indicates the value that is used
• Seize: this parameter indicates the value that is used for
for detecting an Unavailable state.
detecting a Seizure
Forward state. The remaining parameters in this module are advanced
• Seize Acknowledge: this parameter indicates the value that is functions. It is recommended that they not be modified.
used for
detecting a Seizure Acknowledge state.
CCS From the Advanced Definition module in the Voice folder,
• Answer: this parameter indicates the value that is used for select the CCS sub-module. Click on the Add (+) button in the
detecting an Answer (off hook) state. tool bar or select Add New from the pull-down Edit menu. The
screen shown in Figure 7-25 will appear.

7-108 3008M300-004
 7 CONFIGURING VOICE

2. Permission
This parameter indicates the types of calls that are permitted on
the voice channels associated with this configuration. The
options available are as listed below.
• remote: this voice channel can accept remote calls
• local: this voice channel can accept local calls
• both: this voice channel can accept remote and local calls
3. User information layer 1 Protocol (Advanced)
This parameter is applicable to calls coming from a remote
voice channel. The options available are as listed below.
• mu_law: this parameter is set to Recommendation G.711
mu-law
• a_law: this parameter is set to Recommendation G.711 A-
Law
• transparent: the User Information Layer 1 Protocol from a
remote voice channel is used.
4. Immediate Connection
This parameter is configurable only when the Voice Channel’s
Figure 7-25: Configuring CCS
Emulation Mode is set to “high”. See “Voice Channel 2” on
Configure the parameters listed below. page 7-89

1. Name
This parameter allows the user to change the default name.The MFC-General From the Advance Definition module in the Voice folder, select
characteristics of this parameter are based on the preconfigured the MFC sub-module. Click on the Add (+) button in the tool
setting selected in the Default Configuration parameter. bar or select Add New from the pull-down Edit menu. The
screen shown in Figure 7-26

3008M300-004 7-109
CXTool User Guide

appears. 3. Outgoing Register- Caller Category Digit (Normal)

This parameter determines the normal caller category and it is
sent from the outgoing register. Usually, this caller category
refers to Group II signals. The exceptions are Mexico, (Group
II3 signals) and China (KD Table signals) A value of 0
indicates that this signal is not used.
4. Outgoing Register- Caller Category Digit (Extended)
This parameter determines the extended caller category and it
is sent from the outgoing register. This caller category needs to
be configured for the following three countries: Mexico (refers
to Group II6 signals), China (refers to KA Table signals), and
Singapore (refers to Charging Category Table signals). A value
of 0 indicates that this signal is not used.

Advanced 1 The remaining parameters in this module are advanced

functions. It is recommended that they not be modified. A
description of the advanced parameters is provided below
primarily for information.
1. Outgoing Register - Information Sending (Digit)
Calling ID Unavailable
This parameter determines the digit used by the outgoing
register signal to inform the incoming register that the calling
Figure 7-26: Configuring MFC-R2
ID is not available.
Configure the parameters listed below. 2. Outgoing Register - Information Sending (Digit)
1. Name End of Calling ID
This parameter allows the user to change the default name.The The parameter determines the digit used by the outgoing
characteristics of this parameter are based on the preconfigured register signal to inform the incoming register that the address
setting selected in the Default Configuration parameter (calling ID) is sent completely.

2. Default Configuration 3. Outgoing Register - Information Sending (Digit)

Malicious Caller
This parameter allows the user to select the pre-configured
settings according to country. This parameter determines the digit that will be used by the
incoming register signal to inform the outgoing register that

7-110 3008M300-004

this is a malicious caller. A malicious caller can refer to a call
made as a test and not as an actual paid call.
4. Incoming Register - Category Request (Digit)
Cat. Only - Normal
The parameter determines the digit used by the incoming
register signal to request the “normal category” from the
outgoing register.
5. Incoming Register - Category Request (Digit)
Cat. & Switch to Group B - Normal
This parameter determines the digit used (from Group B) by
the incoming register signal to request the “normal category”
from the outgoing register.
6. Incoming Register - Category Request (Digit)
Cat.& Calling ID - Normal
This parameter determines the digit used by the incoming
register signal to request the “normal category and calling ID”
from the outgoing register.
7. Incoming Register - Category Request (Digit
Wait End Called Number
This parameter determines the digit that will be used by the
outgoing register signal to inform the incoming register that the
address (called number) is sent completely.
8. Incoming Register - Category Request (Digit)
Cat. & Calling ID and Switch to Group C - Normal
This parameter determines the digit used (from Group C) by
the incoming register signal to request the “normal category
and calling ID” from the outgoing register.
9. Incoming Register - Category Request (Digit)
Cat. Only - Extended
The parameter determines the digits used by the incoming
register signal to request the “extended category” from the
outgoing register.
3008M300-004
7 CONFIGURING VOICE
10. Incoming Register - Category Request (Digit)
Cat. & Switch to Group B - Extended
This parameter determines that digit used (from Group B) by
the incoming register signal to request the “extended category”
from the outgoing register.
11. Incoming Register - Category Request (Digit)
Cat. & Switch to Group C - Extended
This parameter determines that digit used (from Group C) by
the incoming register signal to request the “extended category”
from the outgoing register.
12. Incoming Register - Address Request (Digit)
First
The parameter determines the digit used by the incoming
register signal to request the “first address digit” from the
outgoing register.
13. Incoming Register - Address Request (Digit)
Next
The parameter determines the digit used by the incoming
register signal to request the “next address digit” from the
outgoing register.
14. Incoming Register - Address Request (Digit)
Last
The parameter determines the digit used by the incoming
register signal to request the “last address digit” from the
outgoing register.
15. Incoming Register - Address Request (Digit)
Last But One
The parameter determines the digit used by the incoming
register signal to request the “last but one address digit” from
the outgoing register.
7-111
CXTool User Guide
16. Incoming Register - Address Request (Digit)
Last But Two
The parameter determines the digit used by the incoming
register signal to request the “last but two address digit” from
the outgoing register.
17. Incoming Register - Address Request (Digit)
Last But Three
The parameter determines the digit used by the incoming
register signal to request the “last but three address digit” from
the outgoing register.
Advanced 2 1. Timers (ms) - Time Out (Forward)
This parameter determines the delay allowed for the receipt of
a forward signal.
2. Timers (ms) - Time Out (Backward)
This parameter determines the delay allowed for the receipt of
a backward signal.
3. Timers (ms) - Pulse Period
This parameter determines the duration of a pulse sent by an
incoming register.
4. Miscellaneous Request (Digit) - Calling ID
This parameter determines the digit used by the incoming
register signal to request the “calling ID” from the outgoing
register.
5. Miscellaneous Request (Digit) - Sending Info.Tone
This parameter determines the digit used by the incoming
register signal to request the “special info. tone” from the
outgoing register.
7-112
6. Information Sending (Digit) - Switch to Group B
This parameter determines the digit used by the incoming
register signal to inform the outgoing register to expect a digit
from Group B.
7. Information Sending (Digit) - Subscriber Line Busy
This parameter determines the digit used by the incoming
register to inform the outgoing register that the subscriber line
is busy.
8. Information Sending (Digit)- Unallocated Address
This parameter determines the digit used by the incoming
register signal to inform the outgoing register that the called
address is unallocated.
9. Information Sending (Digit)- Start Speech and Charge
This parameter determines the digit used by the incoming
register signal to inform the outgoing register that the called
address is starting the speech call for charging purposes.
10. Information Sending (Digit) - Line Available Charge
This parameter determines the digit used by the incoming
register signal to inform the outgoing register that the
subscriber line is available and the communication has been
established (charge).
11. Information Sending (Digit) - Line Available No Charge
This parameter determines the digit used by the incoming
register signal to inform the outgoing register that the
subscriber line is available and that communication has been
establish (no charge).
12. Information Sending (Digit) - Congestion
This parameter determines the digit used by the incoming
register signal to inform the outgoing register that the network
is congested.
3008M300-004
 7 CONFIGURING VOICE

13. Information Sending (Digit) - Line Out of Order

This parameter determines the digit used by the incoming
register signal to inform the outgoing register that the
subscriber line is out-of-order.
14. Information Sending (Digit) - Request Not Accepted
This parameter determines the digit used by the incoming
register signal to inform the outgoing register that the request
was not accepted.
15. Other Configuration - General Info. Requested
This parameter determines the information that the incoming
register requests from the outgoing register.
16. Other Configuration - Disconnect Process
This parameter determines the procedure to disconnect.

3008M300-004 7-113
CXTool User Guide

7-114 3008M300-004
 8 CONFIGURING ATM

This chapter describes how to configure ATM services on

Memotec CX950, CX960, and CX2000 devices using CXTool.

Users of this guide are assumed to have an understanding of

this transport protocol. However, a review of some ATM basics
is provided in Chapter 23 INTRODUCTION TO ATM.

3008M300-004 8-115
CXTool User Guide

8.1 Introduction Within UNI 3.1, conformance definitions are made according
to QoS class. Within the TM 4.0 context, conformance
The Memotec CX950, CX960, and CX2000 provide broad definitions are made according to service categories:
support for the transmission of compressed voice, video, and
data over an ATM network at T1/E1 and T3/E3 rates. Users Table 8-2: Memotec ATM Service and the TM 4.0 Context
have access to a full range of value-added features, including Memotec Service Conformance Definition
advanced traffic management techniques, QoS, monitoring, ATM Service Category SERVICE CELL STREAM
and fault detection.
CBR CBR CBR.1 PCR (CLP=0+1)

8.1.1 Memotec ATM Services VBR1 VBR ---- PCR (CLP=0+1)

VBR2 VBR VBR.1 PCR (CLP=0+1) SCR (CLP=0+1)

The ATM services found on Memotec devices are based on the
conformance definitions for user data traffic parameters as VBRC VBR VBR.2/VBR.3 PCR (CLP=0+1) SCR (CLP=0)
outlined by the ATM Forum.
UBR UBR UBR.1/UBR.2 --------
Within CX devices, ATM connections can be configured in one
of two contexts; the UNI 3.1 context, or the traffic management
TM 4.0 context. These contexts are outlined in Table 8-1 and
ATM The CX950, CX960, and CX2000 support the services listed
Table 8-2:
Services below.

Table 8-1: Memotec ATM Service and the UNI 3.1 Context • CBR
Memotec QoS Associated Conformance Definition and The implementation of the Constant Bit Rate provides a
ATM Service Class Service Class Applicable Cell Stream guaranteed amount of bandwidth that is continuously available
during the connection lifetime, yet is available to other services
CBR 1 A PCR (CLP=0+1)
when not used. The CBR service is ideal for the transport of
VBR1 2/3 ------- PCR (CLP=0+1) voice and video. The CBR service implementation utilizes a
single leaky bucket algorithm and supports a conformance
VBR2 2/3 B/C PCR (CLP=0+1) SCR (CLP=0+1) definition for PCR (CLP=0+1), which complies to both UNI 3.1
(Service Class A), and TM 4.0 (CBR.1).
VBRC 2/3 B/C PCR (CLP=0+1) SCR (CLP=0)
• VBR1
UBR 0 D --------
This Variable Bit Rate implementation is similar to CBR, but
does not have the same level of guarantees as CBR. The VBR1
service implementation also utilizes a single leaky bucket
algorithm and supports a conformance definition for PCR

8-116 3008M300-004

(CLP=0+1), which does not have any compliant equivalent in
both UNI 3.1 and TM 4.0.
• VBR2 and VBRC
These Variable Bit Rate implementations are similar in that they
can be used for both real-time and non-real-time applications.
Real-time applications are those requiring a tightly constrained Frame Relay
delay and delay variation bounds, such as voice and video. Non-
real-time applications are those which have bursty traffic
patterns, and which require no delay bounds within the network.
Real-time applications may also be bursty. The distinction
between real-time and non-real-time is made via prioritization
within CX devices.
The VBR2 and VBRC services differ in the following respects:
• The VBR2 service is implemented utilizing dual leaky
buckets and supports conformance definitions for PCR
(CLP=0+1) and SCR (CLP=0+1), which complies with both
UNI 3.1 (Service Class B and C), and TM 4.0 (VBR.1).
• The VBRC service is implemented utilizing dual leaky
buckets and supports conformance definitions for PCR
(CLP=0+1) and SCR (CLP=0), which complies with both
UNI 3.1 (Service Class B and C), and TM 4.0 (VBR.2 and
VBR.3).
• UBR
This Unspecified Bit Rate implementation is intended for non-
real-time applications and does not provide any guaranteed
bandwidth. The implementation does not utilize any leaky
buckets, and thus does not support the concept of PCR and
CDVT. This has the effect of permitting the use of as much
bandwidth as is available, right up to the full access line rate.
When no bandwidth is available, applications using the UBR
service will be “squeezed” out.
This UBR implementation is compliant with both UNI 3.1 (Ser-
vice Class D), and TM 4.0 (UBR.1 and UBR.2).
3008M300-004
8 CONFIGURING ATM
8.1.2 Protocols Supported and Voice
CX devices provide the following types of traffic services over
an ATM circuit.
The CX950, CX960, and CX2000 support two types of frame
relay services and both are in accordance with the requirements
of the Frame Relay Forum (FRF) “Frame Relay /ATM PVC
Network Interworking Implementation Agreement”. They are:
• FRF.5, the Frame Relay/ATM Network Interworking for
PVCs
• FRF.8, the Frame Relay/ATM Service Interworking for
PVCs
FRF.5
The Frame Relay /ATM PVC Network Interworking Function
(Network-IWF) provides ATM transport between two frame
relay entities. It encapsulates frame relay frames within ATM
cells, and the protocols are not translated.
FRF.8
The Frame Relay/ATM PVC Service Interworking Function
(Service-IWF) translates frame relay protocol to ATM
protocol before forwarding it to the ATM network. Since
Service-IWF can directly connect frame relay to ATM
backbones, Service-IWF offers a clear migration path to ATM.
Service Interworking enables an ATM user to interwork with a
frame relay user, and neither one needs to know that the peer
end uses a different technology.
NOTE: Network-IWF and Service-IWF are not interoperable.
8-117
CXTool User Guide

Given that Service-IWF implies a one-to-one mapping between currently support four types of LAN traffic. They are as
a frame relay circuit and an ATM circuit, a frame relay-MPE mentioned below.
circuit cannot connect to or participate in a multiprotocol
• Internet Protocol (IP)
encapsulated (MPE) ATM circuit. (See below).
• Internetwork Packet Exchange Protocol (IPX)
When protocols are combined on the same ATM circuit, there
• Spanning Tree Protocol (STP)
is a possibility that the Quality of Service (QoS) may suffer.
For instance, if LAN and Voice traffic were to be multiprotocol • Source Route (SR)
encapsulated and the ATM circuit was provisioned as a CBR,
LAN traffic would be deprived of its bursty capabilities in
favor of a more steady and constant flow. On the other hand, if DXI The CX950, CX960, and CX2000 can translate DXI protocol
the ATM circuit was provisioned as a VBR, LAN traffic would to ATM protocol, using AAL5. The ATM DXI provides ATM
maintain its bursting capabilities but Voice would loose its DSU functionality as per ATM Forum’s ATM Data Exchange
constant steady flow requirement, resulting in delays. In order Interface (DXI) Specification (version 1.0).
to ensure QoS, a proprietary standard has been developped that
supplements the FRF.8 standard, and is named FRF.8 Plus.
Legacy CX devices support the following legacy protocols: X.25,
FRF.8 Plus SNA, Async and Bisync.
CX products take advantage of the inherent QoS nature of
ATM because FRF.8 Plus permits multiple protocols to be
Voice Voice traffic can be carried directly over ATM using the service
spread across one or more ATM circuits, each associated with
provided by AAL5/AAL0. Constant Bit Rate (CBR) service is
its own QoS. Thus, a one-to-many mapping can exist between
recommended for carrying voice over ATM in order to
a Memotec MPE-enabled frame relay circuit and one or more
minimize cell jitter and Cell Delay Variation (CDV), although
ATM circuits. Each protocol or groups of protocols can be
"real-time" VBR can also be used.
more appropriately matched to its real traffic requirements,
e.g., CBR, VBR, and so on.
8.1.3 Encapsulation
It should be noted that FRF.8 Plus gives the CX950, CX960,
and CX2000 the ability to separate traffic according to The following encapsulation services are available in the
protocols and not according to specific instances of a given CX950, CX960, and CX2000.
protocol.
Virtual Circuit-Based Encapsulation
This method of multiplexing permits the encapsulation of a
LAN LAN protocols are carried directly over ATM as specified by single LAN protocol per ATM circuit.
RFC-1483 “Multiprotocol Encapsulation over ATM
Adaptation Layer 5.” The CX950, CX960, and CX2000

8-118 3008M300-004
 8 CONFIGURING ATM

Logical Link Control Encapsulation use, and cannot be assigned for tunneling. It is important to
This method of multiplexing permits the encapsulation of note that the priority default values cannot be altered. The
multiple LAN protocols over one ATM circuit. highest priority a VBR connection can have is priority 2, and,
with tunneling enabled, all VBR traffic that is assigned priority
Multiprotocol Encapsulation (MPE) 2 will share a tunnel. UBR and VBR traffic cannot share a
The implementation of MPE in CX devices provides the ability tunnel, however, they can each have their own tunnel.
to combine and transport one or more similar protocols from a
single or multiple sources, together with other (i.e., different) Table 8-3: Memotec ATM Priority List
protocols. It should be noted that the ability to combine
multiple protocols within a single ATM circuit is beneficial Service
Priority Memotec Priority Default Mapping
only when the QoS requirements of the shared protocols are Category
similar. The Memotec implementation of MPE allows for 0 CBR Only value for CBR
differentiation among various protocols or among multiple
1 UBR
instances of the same protocols or a combination of the two on
the same ATM circuit. Presently, however, the CX devices do 2 VBR Default value for VBR1
not separate protocols by their instance at the remote end
3 VBR Default value for VBR2/VBRC (non-real-time)

8.1.4 Tunneling 4 VBR

The Memotec CX950, CX960, and CX2000 support tunneling 5 ---- Reserved for future use.
as an advanced traffic management technique that conceptually
6 UBR Default value for UBR
segments an interface into smaller “virtual pipes.” All VCCs of
the same priority level can be grouped together to share a 7 UBR
tunnel, thereby limiting the amount of aggregate bandwidth
consumed by the group. While a tunnel does not guarantee 8 UBR
bandwidth statically, it does guarantee bandwidth for those
circuits that it carries, when required.
It should be noted that while every VCC is assigned a priority,
The amount of bandwidth used by the connections running not all priorities are necessarily assigned tunnels (this is done
through a tunnel is capped; this way, a tunnel guarantees that a at the user’s discretion). If there is higher priority traffic
specified amount of bandwidth will never be exceeded. anywhere in the interface that requires more bandwidth at any
given time, it will take the bandwidth away from the lower
priority traffic, whether the traffic is in a tunnel or not.
Tunnels and A maximum of seven tunnels can be created on the CX950,
Priorities CX960, and CX2000. As illustrated in Table 8-3, priority 0 is
reserved for CBR traffic, and priority 5 is reserved for future

3008M300-004 8-119
CXTool User Guide

8.1.5 OAM Flows Figure 8-1 illustrates a case in which CX devices carry traffic
(voice, LAN, or SNA) from one frame relay network to another
The CX950, CX960, and CX2000 use F4 and F5 OAM similar network across an ATM network.
(Operations, Administration, and Maintenance) cells to
facilitate proper functioning of an ATM network. OAM cells
for an F5 (VC) flow use the same Virtual Path Identifiers 1 ATM T1
T1/E T3 /E1
(VPIs) and Virtual Channel Identifiers (VCIs) as the user cells 3 /E
T3/E 3
of the VCC. The Payload Type Indicator (PTI) field of ATM
cell header is used to distinguish between segment and end-to-
end F5 flows.

When VP level OAM (F4) is enabled, two VCCs are created

and reserved for this purpose, as summarized in Table 8-4: Frame Relay

Table 8-4: VCI and PTI Values for ATM OAM Flows Frame Relay

Connection Type F4 Flow (VP) F5 Flow (VC)

Segment VCI = 3 PTI = 100
Figure 8-1: Frame Relay/ATM Network Interworking
End-to-End VCI = 4 PTI = 101
In our example in Figure 8-1, CX950 (A) is configured to carry
The next section illustrates some typical scenarios in which frame relay traffic (e.g., voice, SNA, or LAN) on an ATM
Memotec devices can be used for ATM services. circuit. The basic configuration that permits CX950 (A) to
perform FRF.5 functions are mentioned below.

8.1.6 Typical ATM Network • Configure a Physical Frame Relay Port (FRPort1)
Sync Driver (HW Port) V.24 1.1
The examples in this section illustrate the principal services for
which the CX950, CX960, and CX2000 can be configured. • Configure a Frame Relay DLCI (on FRPort1)
Frame Relay Port
DLCI: 100
Frame Relay/ As described in 8.1.2 Protocols Supported and Voice,
ATM Network
DLCI: 101
subsection Frame Relay, the FRF.5 service allows one frame
Interworking relay customer to interwork with another frame relay user over • Configure a Logical Frame Relay Port (FRPort2)
(FRF.5) an ATM PVC, and neither one need be aware that the peer end
is using a different technology. Frame Relay Port
FR/ATM Interworking Port: Network Interworking
(FRF.5)

8-120 3008M300-004
 8 CONFIGURING ATM

FRDLCI (on FRPort 2, created logically) Frame Relay/ As mentioned in 8.1.2 Protocols Supported and Voice, in the
DLCI: 200 ATM Service section titled: Frame Relay, the FRF.8 service translates frame
DLCI: 201 Interworking relay protocol to ATM protocol before forwarding it to the
(FRF.8) ATM network.
Link Type
ATMVCL1 (carries traffic on DLCIs 200 and 201) In the case illustrated in Figure 8-2, CX900 (B) is configured
• Configure an ATM Port with FRF.8 service. It receives the frame relay traffic (which
could be on an FR-MPE circuit), encapsulates it as ATM, and
ATM Port transports it across the ATM network to CX950 (C), which is
ATM Cell I/O 2.1 configured to provide ATM-MPE service.
• Configure an ATM Circuit (ATMVCL1) Remote SNA
Controller
ATM Virtual Circuit
aal5;
VPI=1; VCI=30 CX950 (C) FRF.8
Encapsulation Type: multiprotocolFrameRelaySscs LAN
ATM-MPE
Traffic Descriptors FXS ATM
T1 T1 CX950 (B)
Circuit Type: VBR

FXS
PCR: 300
3001
CDVT: 0
SCR: 200 3002

MBS: 200 Frame

Relay
• Configuring Frame Relay Switching Function
Switching 1 Figure 8-2: Frame Relay/ATM Service Interworking (FRF.8)
Source DLCI: 100
Destination DLCI: 200 The following configuration permits CX950 (B) to perform
Switching 2 FRF.8 functions.
Source DLCI: 101 • Configure an ATM Port
Destination DLCI: 201
ATM Port
ATM Cell I/O 1.1
NOTE: For this example, we assume that CX950 (B) is
configured to receive frame relay traffic from an ATM • Configure a Physical Frame Relay Port (FRPort1)
network and to forward it to its destination. Sync Driver (HW Port) V.35H Serial 2.1

3008M300-004 8-121
CXTool User Guide

• Configure a Frame Relay DLCI on Physical Port (FRPort1)

NOTE: For this example, we assume that CX950 (C) is
Frame Relay Port configured with ATM-MPE services to separate traffic
DLCI: 100 and to send each traffic type to its destination.
MPE Type: disabled
• Configure a Logical Frame Relay Port (FRPort2)
Frame Relay/ As mentioned in 8.1.2 Protocols Supported and Voice, section
Frame Relay Port ATM Service entitled: Frame Relay, the FRF.8+ service allows the user to
FR/ATM Interworking Port: Interworking separate traffic according to the Quality of Service (QoS)
Network Interworking (FRF.8) (FRF.8+) priorities specified by the user. That is, the user can select voice
FRDLCI (on FRPort 2, created logically) traffic to go on a CBR circuit, LAN traffic to go on a UBR
DLCI: 200 circuit, and so on.
MPE Type: translation
In the example in Figure 8-3, CX900 (B) is configured for
Link Type providing FRF.8+ service. It receives frame relay traffic (which
ATMVCL (carries traffic on DLCI 200) is carried on an FR-MPE circuit on DLCI 200), encapsulates it
as ATM traffic, and separates each traffic type according to its
• Configure an ATM Circuit
Quality of Service (i.e., CBR, VBR, or UBR) on an ATM
ATM Virtual Circuit circuit, before transporting it across an ATM network to
aal5; CX950 (C).
VPI=1; VCI=40
Encapsulation Type: multiprotocolFrameRelaySscs The basic configuration that permits CX950 (B) to perform
FRF.8+ functions is described below.
Traffic Descriptors
Circuit Type: VBR • Configure an ATM Port
PCR: 300
ATM Port
CDVT: 0
ATM Cell I/O 1.1
SCR: 200
MBS: 200 • Configure a Physical Frame Relay Port (FRPort1)
• Configuring Frame Relay Switching Function Sync Driver (HW Port) V.35H Serial 2.1
Source DLCI: 100 • Configure a Frame Relay DLCI on a Physical Port (FRPort1)
Destination DLCI: 200 Frame Relay Port
DLCI: 100
MPE Type: disabled

8-122 3008M300-004
 8 CONFIGURING ATM

• Configure an ATM Circuit (ATMVCL)

ATM Virtual Circuit
Frame
ATMVCL1
CX950 (D) Relay aal5;
VPI=1; VCI=40
Encapsulation Type: multiprotocolFrameRelaySscs
Frame
Relay
ATMVCL2
Frame CX950 (C)
Relay aal5;
VPI=1; VCI=30
LAN Encapsulation Type: multiprotocolFrameRelaySscs

ATMVCL3
aal5;
VPI=1; VCI=20
CX950 (A) Encapsulation Type: multiprotocolFrameRelaySscs
LAN Traffic Descriptors
ATMVCL1: Circuit Type - CBR
CX950 (B) - PCR: 300
- CDVT: 0
- SCR: 0
- MBS: 0

ATMVCL2: Circuit Type - UBR

Figure 8-3: Frame Relay/ATM Service Interworking (FRF.8+)
- PCR, CDVT, SCR, MBS: 0
• Configure a Logical Frame Relay Port (FRPort2)
ATMVCL3: Circuit Type - VBR
Frame Relay Port - PCR: 300
FR/ATM Interworking Port: - CDVT: 0
Network Interworking (FRF.8+) - SCR: 200
FRDLCI (on FRPort 2, created logically) - MBS: 200
DLCI: 200
Link Type
ATMVCL (carries traffic on DLCI 200)

3008M300-004 8-123
CXTool User Guide

• Configure the ATM Service Interworking DLCI (separates

traffic according to Protocol ID)
S 4141
ATMVCL1: pidVR (for voice traffic) FX

ATMVCL2: pidLan (for LAN traffic) FXS

4142
ATMVCL3: pidLlc2 (for SNA traffic) CX950 (B)
/E1
• Configure Frame Relay Switching Function T1

Source DLCI: 100

ATM
Destination DLCI: 200

/E1
NOTE: For this example, we assume that CX950 (C) is CX950 (A) T1

configured with ATM-MPE services to separate traffic

and to send each traffic type to its destination.

S
FX

FXS
Transporting The voice service provided by Memotec devices is proprietary.
Voice Across Consequently, Memotec devices are required at both ends of an 1001 1002
an ATM ATM circuit.
Network
In the example in Figure 8-4, let us assume that the caller at
telephone extension 4141 wants to reach the caller at extension
1001. Figure 8-4: Voice Across an ATM Network

The basic configuration that permits CX950 (B) to send voice • Configure an ATM Circuit (ATMVCL)
traffic to CX950 (A) is described below. aal5

Configure the Voice service, and in the WAN Trunk, select: VPI: 1; VCI: 70
ATMVCL Encapsulation: llcEncapsulation
For details on how to configure voice, refer to Chapter 7 Circuit Type: CBR
CONFIGURING VOICE. ATM Traffic Services
• Configure an ATM Port Traffic Type: CBR
PCR: 300
ATM port: ATM Cell I/O 1.1 CDVT: 0

8-124 3008M300-004
 8 CONFIGURING ATM

NOTE: For the purposes of this example, we assume that the

parameters mentioned above are configured correctly LAN
on CX950 (A). We also assume that the voice module
is configured correctly on both of the CX950s.

CX950 (B)
Transporting The Memotec LAN service is interoperable with other vendor
LAN traffic equipment that is compliant with RFC 1483.
across an
ATM Network In the example in Figure 8-5, the CX950 is configured to T1/E
1
receive LAN traffic and route it to a device from another
vendor (RFC 1483 compliant). ATM

The basic configurations that permit CX950 (B) to send LAN E1

T1/
traffic to another vendor device across an ATM network are
described below.
Device from
Configure the LAN service, and in the WAN Trunk, select:
another vendor
ATMVCL

For details on how to configure a LAN and an IP, refer to LAN

Chapter 10 CONFIGURING IP.
• Configure an ATM Port
Figure 8-5: LAN across an ATM Network
ATM port: ATM Cell I/O 1.1
• Configure an ATM Circuit (ATMVCL) NOTE: For the purposes of the example, assume that the LAN
aal5 traffic parameters are correctly configured on the
CX950.
VPI: 1; VCI: 70
Encapsulation: vcMultiplexBridgedProtocol 802.3 The next section focuses primarily on how to configure ATM
ATM Traffic Services services on Memotec devices with CXTool. The steps of the
Traffic Type: UBR configuration adhere to the sequence in CXTool, and includes a
description of the parameters the user will encounter during
configuration.

3008M300-004 8-125
CXTool User Guide

8.1.7 Summary of ATM features supported on CX Products Multimedia • Compressed Voice

Services
• Fax Relay
Interface • UNI interface (UNI 3.1 compliant and TM 4.0 compliant) • H.320 Video
Options
• T1 as per ITU-T G.703, ANSI T1.102, T1.107
• E1 per ITU-T G.703 ATM Framing • Direct cell mapping per ITU-T G.804
• PLCP (DS1) per ANSI TA-TSY-000772
AAL Layers • AAL5 and (E1) per ETSI T/NA (91) 17

• AAL0
Protocols • Frame Relay, LAN/IP, SNA, X.25, DXI, Voice
Supported
Virtual • Up to 255 Virtual Path Channels
Circuits
• Up to 65535 Virtual Channel Connections Voice • Analog
Currently, the CX950, CX960, and CX2000 can only be config- • Digital
ured wth PVCs (Permanent Virtual Circuits).

Interworking • FR/ATM Network Interworking (FRF.5)

Service
• FR/ATM Service Interworking (FRF.8) and (FRF.8+
[proprietary])

Traffic • CBR
Services
• VBR
• UBR

MPE • Frame Relay, LAN/IP, SNA, X.25, DXI, Voice

Tunneling • Proprietary

8-126 3008M300-004
 8 CONFIGURING ATM

8.2 Configuring ATM Services

The ATM folder contains all the parameters associated with
ATM, including Port, Virtual Channel Link, Traffic
Descriptors, and Tunnel.

8.2.1 Configuring the Port

From the ATM folder, select the Port module. Click on the Add
(+) button in the tool bar or select Add New from the pull-
down Edit menu. The screen shown in Figure 8-6 appears.

Configure the parameters described below.

1. Hardware Port
This parameter determines the slot and port numbers that are in
use. Click on Add. The following screen appears:
After adding the ATM card, configure the parameters listed
below. (Refer to Figure 8-6)
2. Maximum VPCs
This parameter indicates the maximum number of permanent
Virtual Path Connections (VPCs) supported at this ATM
interface.
3. Maximum VCCs
This parameter indicates the maximum number of permanent
Virtual Channel Connections (VCCs) supported at this ATM
interface. Figure 8-6: Configuring the ATM Port
4. Maximum VPI Bits
This parameter determines the maximum number of active VPI
bits that are configured for cell routing at this ATM interface.
5. Maximum VCI Bits
This parameter determines the maximum number of active VCI
bits that are configured for cell routing at this ATM interface.

3008M300-004 8-127
CXTool User Guide

8. Bandwidth Management
This parameter sets the upper limit on the bandwidth that is
allowed at all ATM interfaces. This limit ultimately determines
whether or not a Virtual Channel Link (VCL) or tunnel can be
activated. The options available are as follows:
• none: indicates no limit is imposed at this interface
• usWest: indicates that the bandwidth management scheme
used at this interface is based on the ATM service as defined
by UsWest, which is as follows:

 Sum of all   Sum of all 

CBR and VBR1×PCR + PCR Factor* ×VBR2 and VBRC× SCR
   
≤ Max line
cell rate
 connections   connections 

* The PCR Factor for UsWest is set to 1.25. This PCR

Factor takes into account the PCR burst nature of the data
flow from the user connection relative to the SCR.

• sprint: indicates that the bandwidth management scheme

used at this interface is based on the ATM service as defined
by Sprint, which is as follows:

Figure 8-7: Adding an ATM Card

6. Largest VPI value

This parameter reflects the value in the “Maximum VPI Bits”
parameter in decimal format. This is a “read-only” parameter.
7. Largest VCI value
This parameter reflects the value in the “Maximum VCI Bits”
parameter in decimal format. This is a “read-only” parameter.

8-128 3008M300-004
 8 CONFIGURING ATM

10. Frame Format

This parameter indicates the type of framing used at this
interface. The options available are as follows:
 Sum of all   Sum of all 
    ×PCR • g_804: ATM direct cell mapping as per ITU G.804
 VBR × PCR ÷5 ≤ Max Line Cell Rate – CBR
   
 connections connections • plcp: ATM Physical Layer Convergence Protocol (PLCP)
cell mapping as per Bellcore TR772 for DS1, and per ETS
300 213 for E1
 Sum of all   Sum of all 
 
 VBR ×SCR ÷ 2 ≤Max Line Cell Rate –  CBR × PCR

11. Idle Cell Payload
 
 connections  connections  This parameter indicates the type of pattern inserted in the idle/
unassigned cell payload. Idle/unassigned cells are inserted at
this interface when the PHY device detects that the transmit
If VBR, UBR, and CBR services are used, the sum of all FIFO contains no outstanding cells. The default pattern is
CBR PCRs must not exceed 50% of the line bandwidth. 6AH, as defined by the ATM Forum UNI specifications.
12. Transmit Coset
When enabled, this parameter indicates that the coset
9. Transmit Clock polynomial is applied to the HEC octet of transmitted cells in
the following manner: the polynomial X6+X4+X2+1 is added
This parameter indicates how the physical line’s transmit clock to the HEC octet of each cell prior to transmission as required
will be derived. For ATM DS1 and E1 implementation, this by the ATM Forum UNI specifications. The coset function
parameter defines the interface clocking which causes the prevents the HEC octet within a cell from taking on a value of
clocking at the DS1 and E1 layer to be ignored. This is contrary zero.
to non-ATM implementation where it is the clocking parameter
at the DS1 and E1 layer that defines the interface clocking. The 13. Receive Coset
available options are as follows: When enabled, this parameter indicates that the coset
• synchronized: the transmit clock will be derived from the polynomial is applied to the HEC octet of the received cells
receive clock. This is more commonly referred to as loop before comparison in the following manner: the polynomial
timing X6+X4+X2+1 is added to the HEC octet of each received cell
before comparison with the calculated result as required by the
• unsynchronized: the transmit clock will be derived internally ATM Forum UNI specifications. The coset function prevents
from an the HEC octet within a cell from taking on a value of zero.
oscillator, and it will not be synchronized to the receive
clock 14. Cell Scrambling and Cell Descrambling
These parameters permit the randomization of the cell payload
to avoid continuous non-variable bit patterns. It defines

3008M300-004 8-129
CXTool User Guide

whether or not the cell payload scrambling/descrambling is

applied to the transmitted cells at this interface. If this
parameter is enabled, the cell payload is scrambled using the
self synchronizing polynomial X43+1. If this parameter is
disabled, the cell payload that is transmitted is unscrambled.
15. Circuit Status
This parameter provides a summary of how the current circuit
is configured (see Figure 8-8).

Figure 8-9: Configuring the ATM Port (continued)

1. Line Type.
This parameter indicates whether the Line Type implemented
on this circuit is T1 or E1. The Line Type affects the number of
bits per second that the circuit can reasonably carry and it
affects the interpretation of the usage and error statistics. The
options available are as follows:
• ESF: Extended Superframe DS1
• D4: AT&T D4 format DS1
Figure 8-8: View the ATM Circuit Configuration
• E1: CCITT Recommendation G.704 (Table 41)
In the Port module, click on Next. The following screen
appears: • E1-CRC: CCITT Recommendation G.704 (Table 4b)

Configure the parameters listed below.

8-130 3008M300-004
 8 CONFIGURING ATM

2. Line Build Out value 8.2.2 Configuring the Virtual Channel

This parameter indicates the attenuation or the Line Build Out
to be used on the transmitter side of the T1/E1 line. From the ATM folder, select the Virtual Channel Link module.
Click on the Add (+) button in the tool bar or select Add New
3. Line Coding type. from the pull-down Edit menu. The following screen will
This parameter indicates the type of Zero Code Suppression appear:
(ZCS) used on the link. The options available are as follows:
• B8ZS for T1
• HDB3 for E1
• AMI for T1 or E1
4. FDL
This parameter describes the use of the Facilities Data Link
(FDL). The options available are as follows:
• Ansi-T1-403: refers to the FDL exchange recommended by
ANSI
• Att-54016: refers to ESF FSL exchanges
• fdl_none: indicates that the device does not use the FDL
5. Jitter Attenuator
When the Jitter Attenuator is enabled in the transmit or receive
direction, a buffer is used to ensure frame alignment and clock
synchronization. The options available are as follows:
• RxAttenuator32Bits Figure 8-10: Configuring the ATM Virtual Channel (General)
• RxAttenuator128Bits
Configure the parameters listed below.
• TxAttenuator32Bits
1. VPI
• TxAttenuator128Bits This parameter indicates the assigned VPI value of this VCC,
which is the point at which a group of Virtual Channel Links
access the ATM layer.
2. VCI
This parameter indicates the assigned VCI value of this VCC.

3008M300-004 8-131
CXTool User Guide
3. ATM Port
(see 8.2.1 Configuring the Port)
4. ATM Traffic Descriptor
(see 8.2.3 Configuring the ATM Traffic Descriptors)
5. Circuit Type
This is a “read-only” parameter. It reflects the configuration of
the “Type” parameter in the Traffic Descriptor module.
6. Line Type
This is a “read-only” parameter. It indicates whether this is a
T1 line, an E1 line, a T3 line, or an E3 line.
7. AAL Type.
This parameter indicates the type of ATM Adaptation Layer
protocol in use on this Virtual Channel Connection (VCC).
This parameter applies when the local Virtual Channel Link
(VCL) end-point is also the VCC end-point and AAL is in use.
The options available are as follows:
• aal5; indicates that ATM Adaptation Layer 5 is in use
• other: indicates that ATM Adaptation Layer 0 is in use
8. VC OAM (F5)
When enabled this parameter indicates that the segment and
end-to-end F5 Operations, Administration, and Maintenance
cells are processed at this VCL. When this parameter is
disabled, the F5 OAM cells that are received at this VCL are
ignored.
9. VP OAM (F4)
When enabled, this parameter indicates that the F4 OAM cells
are processed at this VPL, and automatically establishes
VCL=3 for F4 segment OAM, and VCL=4 for F4 end-to-end
OAM. When disabled, this parameter indicates that the F4
8-132
OAM cells received at this VPL are ignored. (Refer to
Table 8-4.)
NOTE: A change to this parameter will be reflected in all the
entries that share the same Port and VPI.
10. Transmit Size
This parameter indicates the maximum SDU size (in octets)
that this VCC supports in the transmit direction.
11. Receive Size
This parameter indicates the maximum SDU size (in octets)
that the VCC supports in the receive direction. This parameter
is applicable to situations when the local VCL end-point is also
the VCC end-point and AAL5 is in use.
12. Encapsulation type.
This parameter indicates the type of data encapsulation used at
the AAL5 level. The options available are as listed below.
• vcMultiplexRoutedProtocol: VC based multiplexing for
routed LAN traffic.
• vcMultiplexBridgedProtocol8023: VC based multiplexing
for 802.3 bridged LAN traffic.
• vcMultiplexBridgedProtocol8025: VC based multiplexing
for 802.5 bridged LAN traffic.
• vcMultiplexBridgedProtocol8026: VC based multiplexing
for 802.6 bridged LAN traffic.
The above options allow for one type of LAN traffic per ATM
circuit.
• llcEncapsulation: when this option is selected for routed or
bridged LAN protocols, many LAN protocols can be carried
on one ATM circuit. However, when it is selected for any
3008M300-004
 8 CONFIGURING ATM

other protocol, only one protocol can be sent on one ATM

circuit.
• multiprotocolFrameRelaySscs: used for Frame Relay
Network Interworking (FRF.5) traffic.
• MPE: used for Frame Relay Service Interworking (FRF.8
and FR.8 Plus) traffic.
13. Circuit Status
This parameter provides a summary of how the current circuit
is configured (see Figure 8-8).

In the Virtual Channel Link module, click on Extended. The

screen shown in Figure 8-11 appears.

Configure these parameters.

1. VCL Priority Level
This parameter establishes a practical priority sequence that
can improve the flow of traffic, thus ensuring that the most
important traffic will get through first. The options that are
available to the user depend upon the service configured in the
“Traffic Descriptor” module.
2. Policed SCR
This parameter is used to control the installation of the
Sustained Cell Rate (SCR) for this Virtual Channel Link
(VCL). When this parameter is enabled, the SCR is adjusted to
a value that ensures the traffic contract is not violated. When it
is disabled, the requested SCR is implemented even if it Figure 8-11: Configuring the Virtual Channel Link (Extended)
violates the traffic contract. This parameter should be disabled
parameter reflects the name of the tunnel associated with that
when “policing” is not a concern.
configuration.
3. Tunnel
4. Bridged FCS
This is a “read-only” parameter. If a tunnel has already been
When this parameter is enabled, the Frame Check Sequence
configured in the ATM Tunnel module (see below), this
(FCS) is included in the encapsulation of bridged LAN traffic.

3008M300-004 8-133
CXTool User Guide

8.2.3 Configuring the ATM Traffic Descriptors 2. Type

This parameter allows the user to define the traffic type. The
From the ATM folder, select the Traffic Descriptor module. options available are as follow:
Click on the Add (+) button in the tool bar or select Add New
from the pull-down Edit menu. The following screen appears: • UBR
• CBR
• VBR - VBR1, VBR2, and VBRC
3. Traffic Parameters
Each traffic type has its own set of traffic descriptors. In order
to know which traffic descriptor to configure, refer to the
following configuration table:

Table 8-5: Traffic Descriptor Configuration

UNI 3.1
TYPE P1 P2 P3 P4
QoS
CBR 1 PCR CDVT
VBR1 2 PCR CDVT
VBR2 3 PCR SCR MBS CDVT
VBRC 3 PCR SCR MBS CDVT
UBR 0

The user can enter values for each parameter either in terms of
characters per seconds (cps) or kilobits per seconds (kbps).

NOTE: The range for PCR and SCR vary depending on

whether the line type is T1, E1, T3, or E3.
Figure 8-12: Configuring ATM Traffic Descriptors

Configure the parameters listed below. 4. Circuit Status

This parameter provides a summary of how all currently
1. T1/ E1 T3/E3 Selection
configured circuits are configured (see Figure 8-8).
This parameter allows the user to select a physical interface.

8-134 3008M300-004

8.2.4 Configuring the ATM Tunnel
From the ATM folder, select the Tunnel module. Click on the
Add (+) button in the tool bar or select Add New from the pull-
down Edit menu. The following screen appear:
Figure 8-13: Configuring the ATM Tunnel
8.3 Configuring DXI
Configure the parameters listed below.
1. Priority
This parameter establishes a practical priorities sequence (for
VCLs) that can improve the flow of traffic, thus ensuring that
the most important traffic will get through first. For a list of the
priorities available, refer to Table 8-3.
2. ATM Port (see 8.2.1 Configuring the Port).
3008M300-004
8 CONFIGURING ATM
3. ATM Traffic Descriptor (see 8.2.3 Configuring the ATM Traffic
Descriptors).
To view the circuits that are associated with a tunnel, go back
to the Virtual Channel Link module.
4. ATM VCL Links
This parameter is a “read-only” parameter and reflects which
VCL is using a tunnel. The user may need to change the tunnel
Priority in order to see the VCL that is associated with this
tunnel.
NOTE: The highest priority a VBR connection can have is
priority 2; all VBR traffic (including VBR1, VBR2,
and VBRC) that is assigned priority 2 may share a
tunnel. Note that UBR and VBR traffic cannot share a
tunnel.
It is also important to note that while every VCC is
assigned a priority, not all priorities are necessarily
assigned tunnels nor can a given priority be duplicated
for the same ATM port.
5. Circuit Status
Not applicable. (Grayed out.)
The Data eXchange Interface (DXI) was developed by the
Switched Megabit Data Services (SMDS) Interest Group to
define the interaction between internetworking devices and
Channel Service Unit/Data Service Units (CSU/DSU) that
transmit over SMDS access lines. A DXI lies between a Data
Terminating Equipment (DTE), such as a personal computer,
and a DCE, such as a modem. The DTE sends DXI-formatted
8-135
CXTool User Guide
frames of variable length to the DSU, which then segments the
frames into cells and transports them across the ATM network.
The CX product acts as a DSU.
To configure DXI services on a Memotec device (e.g., CX950)
using CXTool, open the DXI folder, and select the Port
module. Click on the Add (+) button in the tool bar or select
Add New from the pull-down Edit menu. The following screen
appears:
Figure 8-14: Configuring the DXI Port
Configure the parameters listed below.
8-136
1. Sync Port
This parameter allows the user to configure a sync port.
2. Mode
This parameter defines the DXI operating mode to be used for
this connections. The options available are as follows:
• mode-1a: implies a one-to-one relationship between a DXI
circuit and an ATM circuit. If the user selects this option, the
next step is to configure an ATM circuit by opening the
Circuit module in the DXI folder. 8.2 Configuring ATM
Services.
• modeTransparent: gives the user the flexibility of
configuring a DXI port and associating it with an ATM
circuit. If the user selects this option, the next step is to
configure the following parameters in the Transparent Mode
section:
- Transparent DXI Frame Address: assign the DFA value
- ATM circuit: configure an ATM Virtual Channel
- Reference No.: assign a unique number to identify this
circuit
Only used when connecting to an ATM circuit that is
configured for circuit consolidation (MPE).
3008M300-004
 8 CONFIGURING ATM

8.3.1 Configuring the DXI Circuit

Open the DXI folder, and select the Circuit module. Click on
the Add (+) button in the tool bar or select Add New from the
pull-down Edit menu. The following screen appears:

Figure 8-15: Configuring the DXI Circuit

Enter the DXI Frame Address and configure the ATM circuit.
See 8.2 Configuring ATM Services.

3008M300-004 8-137
CXTool User Guide

8-138 3008M300-004
 9 CONFIGURING FRAME RELAY

This chapter describes how to configure frame relay on a

Memotec CX product using CXTool.

Users of this guide should have an understanding of

networking, and it may be helpful to review the frame relay
basics provided in Chapter 24 INTRODUCTION TO FRAME
RELAY before advancing to the procedures.

3008M300-004 9-139
CXTool User Guide

9.1 Memotec’s CX Family and the Frame which is the maximum data throughput level that the network
can support for a given connection as long as there is no
Relay Environment congestion in the network.

Frame relay connects all network sites through a single

physical access circuit. The access circuit connects through a Line Rate bps

single port at each site. As a result, there are significantly fewer Line rate
Bit Rate slope
router cards and DSU/CSUs required.
( bps )
Frame Frame Frame
1 2 3
9.1.1 Supported Frame Relay Features CIR bps

Calculated
average
Link The software for Memotec CX products conforms to the rate CIR slope
Management following link management standards:

• Frame Relay Forum LMI Time

• ANSI T1.617a -1994 Annex D Figure 9-1: Committed Information Rate (CIR)
• ITU Q.933 Annex A
In Figure 9-1, the vertical lines represent the threshold for CIR
and the line rate in bits per second. The diagonal lines represent
Interfaces • UNI - User the CIR average within the time window that would be met if
Supported data could be clocked at the CIR rate. The zig-zag line running
• UNI - Network between the two diagonal lines shows the calculated average
rate based on the time interval. Note that the calculated average
• NNI
rate increases along the line rate slope when data is transmitted
and runs flat when no data is sent.
Congestion Additional standard transmission and congestion management
Management features ensure that transmissions are optimized and mission-
It is recommended that when configuring CIR, Bc be set equal
to the CIR value.
critical data always has priority. Some of these features are
outlined below. Committed Burst Size (Bc)
Bc allows the user to transmit data above the CIR level for brief
Committed Information Rate (CIR)
periods of time. Bc is the maximum amount of user data that
CIR, measured in bits, is the minimum data throughput level
the network agrees to transfer under normal circumstances over
that the network commits to supporting. Providers usually
a certain time interval Tc.
allow users to operate at the excess information rate (EIR),

9-140 3008M300-004
 9 CONFIGURING FRAME RELAY

As illustrated in Figure 9-2, Tc is used to calculate the average (up to a maximum of the line speed), so long as there is no
rate of Bc and CIR. It is the sliding window that starts when a congestion.
frame is received. If the average amount of data within Tc
exceeds the CIR, then the data may be discarded if congestion Line Rate bps
occurs. EIR bps

Bit Rate
Line Rate bps (bps ) Frame
Frame Frame Frame 4
Frame
Bit Rate 1 2 3
Line rate 5
( bps
) Burst size CIR bps
slope
Be size
Frame Frame Frame Average
1 2 3 Rate
CIR bps DE = 1 DE = 1

Average
0 Time Tc
Rate

CIR slope

Figure 9-3: Excess Burst Size (Be)

0 Time Tc
Figure 9-2: Committed Burst Size (Bc)
Excess Burst Size (Be)
Be is the maximum amount of user data in excess of the Bc that
the network will attempt to deliver over a certain time interval
Tc. To ensure fair treatment and maintain CIR data when
congestion occurs, a discard eligibility (de) bit is used. Frames
transmitted within CIR will have de set to 0. The de bit is set to
1 in order to flag frames that are transmitted in excess of CIR.
Prioritization frames transmitted over a virtual circuit. Priority levels are
As shown in Figure 9-3, this feature allows the user to send
bursty data at rates which may exceed the committed burst size
Excess Information Rate (EIR) = CIR * [1 + (Be / CIR)]
The availability of EIR is contingent upon the availability of
the bandwidth.
A simple way to calculate Bc and Be is as follows:
• If Bc = CIR
• Then Be = EIR - CIR
Traffic Memotec devices can be configured to assign priority levels to
important tools for data management tasks performed by the
frame relay layer. Higher priority traffic (e.g., voice) takes
precedence over lower priority traffic. Each traffic type can be
assigned a priority level at the time of configuring the DLCI.
For more details, see 9.2.2 Configuring Frame Relay DLCIs.

3008M300-004 9-141
CXTool User Guide
Additionally, CX devices can be configured to map IP traffic to
frame relay priority. For more information on this subject refer
to CHAPTER 10 , sections entitled: Configuring Traffic Sorting
and 10.2.5 Configuring the IP QoS.
PVC Memotec CX Products support PVC (permanent virtual
Consolidation circuit) consolidation. A special PVC header is inserted into
the data from each PVC and the traffic is consolidated for
transmission over a single DLCI. This form of consolidation - a
sort of multiplexing - is of major importance in star topologies.
A single DLCI from each location can be used to transmit data
to the hub of the star; at that point, it is switched to its final
destination.
Alternate To ensure optimization of the network, the CPU provides
Routing alternate routing capabilities. In the event of circuit failure,
data is automatically rerouted to the configured alternate route.
In addition, when a condition is detected that requires re-
routing to a dial backup port, Memotec CX Products will raise
DTR to the external modem, or ISDN TA, to initiate the
backup procedure. This feature ensures high network uptime
and protects against loss of mission-critical data.
Data Memotec’s proprietary data compression algorithm is common
Compression to the CX Product family. All frame relay traffic can be
compressed to allow for bandwidth optimization. Additionally
the user can configure priority to different traffic types to
bypass the compression algorithm if so required.
Note that if voice is configured on a frame relay circuit and
MPE is enabled, the data compression algorithm uses the MPE
header to recognize voice frames and does not compress these
frames a second time.
9-142
If MPE is not enabled, compression should not be enabled
for this circuit, otherwise voice frames will be compressed
twice, once by the voice encoding algorithm and again by the
data compression algorithm.
Multiprotocol All CX products have the ability to carry single protocols (non-
Encapsulation MPE). Memotec devices also support multiprotocol
(MPE) encapsulation of different types of traffic, such as voice, LAN,
X.25, and SNA over a single frame relay circuit.
The implementation of MPE is compliant with RFC 1490
“Multiprotocol Interconnect Over Frame Relay.” This RFC is
the basis for Memotec’s proprietary services, such as Voice and
X.25.
In general, when the MPE service is enabled, Memotec devices
are required at both ends of the circuit.
Fragmentation Data packets received on a frame relay circuit may be large
enough to cause delays. Fragmentation allows the user to break
the packets into smaller sizes, which are then transmitted in
separate frames that contain a sequence identifier in the header.
The sequence identifier enables the original packet to be
reassembled upon arrival at the destination.
This feature requires that multiprotocol encapsulation be
enabled on the circuit, and is especially useful for voice traffic.
A non-zero value for fragmentation size indicates the
maximum size of the fragments. A value of zero indicates that
fragmentation is not enabled.
Table 9-1 serves as a guideline for a point to point link with the
same access rate at both ends and it illustrates the relationship
among three entities (port speed, the buffer size, and
3008M300-004
 9 CONFIGURING FRAME RELAY

fragmentation size) that must be configured accurately in order used alone, and at lower cost than using a next-higher
to have best voice quality (i.e., minimize voice delay). bandwidth physical line.

Table 9-1: Guidelines for Best Voice Quality • Load Balancing

Load balancing is a feature, which directs data traffic through
Fragmentation the links of a bundle. The link with the fastest effective
Tx Queue
Port Speed Size of throughput for the frame being sent will be selected to carry the
Size
(kbps) Packets information. Load balancing also minimizes re-sequencing
(buffer size)
(bytes)
delays, and maximizes the use of available bandwidth.
56000 2 175
• Bandwidth on Demand
64000 2 200
Bandwidth on demand allows dynamic sizing of the bandwidth
128000 2 400 capabilities of a “bundle”, by dynamically activating/
192000 3 400 deactivating its dial-on-demand member links (V.34 or ISDN).
256000 4 400
• Fault Tolerance
384000 6 400 Fault tolerance means that the “bundle” keeps functioning, even
512000 8 400 though some of its constituent links fail. The application is
768000 10 500 designed to recover data lost through the failed link.
1024000 12 500
1536000 16 600 Multicast Multicast services are connection-oriented. This implies that
2048000 20 600 Services multicast data can be sent to or received from a member (of a
multicast group) that has established a permanent virtual
connection to the multicast server. Multicast services provide
CX products support packet fragmentation and reassembly
the ability for active group members to participate in point to
according to RFC 1490.
multi-point data transfer. The multicast server receives frames
from a root member and forwards them to other active group
MLPPP Memotec’s implementation of Multi-Link Point-to-Point members, who are referred to as leafs.
Protocol (MLPPP) supports the following features:
Memotec’s implementation of frame relay multicasting
• Inverse Multiplexing includes the services outlined below.
Inverse multiplexing transparently merges several physical or
• One-Way Multicast Service: In this option, the root maintains
logical links into a single link with higher bandwidth and/or
a one-way connection with the multicast server. The frames are
reliability. Several frame relay ports can be logically “merged”
sent from the root to the multicast server, but no frames ever
into a single “fat WAN pipe” or “bundle”, providing more
return in the opposite direction. All the frames that are received
bandwidth for an application than any of the individual lines

3008M300-004 9-143
CXTool User Guide

from the root by the multicast server are replicated and sent to a case in which voice, data, and SNA traffic may be configured
active route partners of each active leaf member to go on one DLCI.
• Two-Way Multicast Service: This option provides full-duplex Remote SNA
transmission all around. One member is always a root, while Controller

others are leaves. All the frames that are sent by the root to the CX950 (C)

multicast server are replicated and sent to each active leaf. CX950 (D)
Frames that are sent by a leaf member to the multicast server are LAN

sent directly to the root and are not sent to any other leaf.
FXS

• N-Way Multicast Service: This option provides for full-duplex

FXS

DL
CI
DL
transmission all around. All members of the multicast group are CI

400
3001 3 00 Frame
roots. A frame sent by any member is always replicated and sent 3002 Relay
DLCI 200
to all other active members.
CX950 (A)
• Two-Way Single Pass: This options provides two way
transmission between a root and one leaf. Note that this is
CX900 (B)
different from a “two-way multicast service” in which a
FXS

S
FX
connection is established between a root and many leaves at the

FXS
2020
same time. FX
S LAN

Two-way single pass is intended to support backup applications 1010 1011 2021

that have more than one alternative path. To do this, the root
provides a path to the application while the leaves provide a SNA Host
path to each possible alternative path including the primary con-
nection.
Figure 9-4: Frame Relay-Based Network
Memotec’s implementation of frame relay multicast service
includes switched and non-switched multicasting.
Configuring Let us assume that CX900 (B) is configured to send
Multiple multiprotocol-enabled traffic across a frame relay network.
9.1.2 Typical Frame Relay Configuration Protocol
Encapsulation In the example shown in Figure 9-4, CX900 (B) has the
As illustrated in Figure 9-4, Memotec devices can be following cards:
configured to receive and carry multiple protocols on one
• Analog Voice FXS (for voice)
DLCI to one destination or to receive one protocol per DLCI
for transport to its destination. The configuration below shows

9-144 3008M300-004
 9 CONFIGURING FRAME RELAY

• V.35H (for frame relay) parameter, which should match that in the Remote
• V.24 (for SNA) Extension parameter.

• Ethernet (for LAN/IP) • Configuring LAN - Step 1

IP Port
In order that all protocols and voice traffic to be transported IP Address: 198.166.1.2
from CX900 (B) to CX950 (D), the configuration of Subnet Mask: 255.255.255.0
CX900 (B) is the following:
Link Type
• Configuring Frame Relay Ethernet 4.1
Frame Relay Port: • Configuring LAN - Step 2
V.35H 2.1
Link: Sync Driver IP Port
DLCI: 300 IP Address: 204.166.1.2
MPE Type: Enabled Subnet Mask: 255.255.255.0

• Configuring Voice WAN Link

Frame Relay: DLCI - 300
Voice Station: CPU on CX950
• Configuring SNA
Voice Channel
Analog Voice FXS 1.1 SDLC Port
Home Extension: 222 Sync Driver (HW Port) V.24 3.1
Local Extension: 222 SDLC CU
DSP Channel SDLCPort1_01
Analog Voice FXS 1.1 LLC2 WAN
Vocoder Group: acelpII Frame Relay: DLCI - 300
Dialing Plan: (digits dialed: 3133001) SNA Link
Dial Pattern: 3XX; Primary Link: SNALLC2WAN -> LLC2WAN1
Remote Extension: --- +++ Secondary Link: SNASDLCCU -> SDLCPort1-01
Called Number: --- ++++
WAN Trunk NOTE: For the purposes of this example, it is assumed that
Frame Relay: DLCI - 300 CX950 (D) is configured correctly.
Voice Pattern: xxx (the compression parameters are
configured automatically). This call will be routed
across the network based upon the pattern used in this

3008M300-004 9-145
CXTool User Guide

If the destination of each service was different, then a different In order for CX950 (D) to perform switching functions, it is
DLCI would be assigned to each frame relay circuit. For configured as illustrated below.
example, if SNA traffic was destined for the Remote SNA
Controller, it would go on DLCI 300. Similarly, if LAN traffic Frame Relay Port1
was destined for CX950 (C), it would go on DLCI 400, and if • V.35H 1.1
voice traffic was destined to telephone extension 1010, it would
be carried on DLCI 200. • Link: Sync Driver
• DLCI 100; DLCI: 200
Frame Relay Figure 9-5, illustrates how Memotec devices perform • MPE: disable
Switching switching functions. CX950 (D) is configured to receive two
DLCIs (DLCI 100 and DLCI 200) on port 1. It switches voice Frame Relay Port2
traffic to port 2, which is carried across a frame relay network • V.35H 2.1
on DLCI 300, and LAN traffic to port 3, which is also carried
across a frame relay network on DLCI 400. • Link: Sync Driver
• DLCI: 300
CX950 (C) • MPE: disable
CX950 (D)
Port 2 00 Frame
3
DLCI
Relay
Port 3
Frame Relay Port3
DLCI 400
Port 1 Port 1 • V.35H 3.1
Frame DLCI 200 DLCI 100
Relay • Link: Sync Driver
PBX
• DLCI: 400
Frame • MPE: disable
Relay
LAN Switching Function
Extensions 5000 - 5999

CX900 (B)
• Switch One
CX950 (A) FXS
Source DLCI: 100
2020
LAN
Destination DLCI: 300
S
FX Protocol ID: pidVR (switches voice traffic)
2021

Figure 9-5 Configuring Switching Functions

9-146 3008M300-004
 9 CONFIGURING FRAME RELAY

• Switch Two In order for CX950 (D) to perform switching functions, it is

Source DLCI: 200 configured as illustrated below.
Destination DLCI: 400
Protocol ID: pidLAN (switches LAN traffic) Frame Relay Port1
• V.35H 1.1

Frame Relay Figure 9-6 illustrates how Memotec devices perform switching • Link: Sync Driver
Switching functions when receiving traffic from an MPE-enabled circuit. • DLCI 100
(MPE) CX950 (D) is configured to receive one DLCI (DLCI 100) on
port 1. It switches voice traffic to port 2, which is carried across • MPE: enable
a frame relay network on DLCI 300, and LAN traffic to port 3,
Frame Relay Port2
which is also carried across a frame relay network on DLCI
400. • V.35H 2.1

CX950 (D) CX950 (C) • Link: Sync Driver

Port 2 00 Frame
3
DLCI • DLCI: 300
Relay
Port 3
DLCI 400 • MPE: disable
Port 1
Frame DLCI 100
Relay Frame Relay Port3
PBX • V.35H 3.1
Frame • Link: Sync Driver
Relay
• DLCI: 400
LAN
Extensions 5000 - 5999
• MPE: disable
CX900 (B)
CX950 (A) F XS
Switching Function
2020
S LAN • Switch One
FX

Source DLCI: 100

2021
Destination DLCI: 300
Protocol ID: pidVR (switches voice traffic)
Source Reference No: 1
Figure 9-6 Configuring Switching Functions on an MPE Circuit

3008M300-004 9-147
CXTool User Guide

• Switch Two
Source DLCI: 100
Destination DLCI: 400
Protocol ID: pidLAN (switches LAN traffic)
Source Reference No: 11

The next section focuses primarily on how to configure frame

relay services on Memotec devices with CXTool. It adheres to
the sequence in CXTool and provides a description of all the
parameters the user will counter during configuration.

9.2 Configuring Frame Relay with CXTool

The FR/FR ATM Interworking folder in CXTool contains all
the modules, sub-modules and parameters associated with
frame relay, including Port, DLCI, and Switch.

9.2.1 Configuring a Frame Relay Port

From the FR/FR ATM Interworking module, select the Port

component. To add a frame relay port, click the Add (+) button
in the tool bar or select Add New from the Edit menu. The
screen shown in Figure 9-7 appears.

To configure an ATM Interworking port, see section

9.2.4 Configuring the ATM Interworking Port.
Figure 9-7: Configuring the Frame Relay Port, General
Configure the remaining parameters as outlined below.
3. Internal Port
1. Port Name
The system provides a default name, which may be changed.
2. Transparent Port

9-148 3008M300-004

4. Link
In the Link group box, the Look in parameter provides the
following selections:
• IP Tunneling: provides proprietary service to carry traffic
end-to-end over an IP connection
• ISDN Service Point: allows configuring the ISDN services
as a backup, for situations when the primary physical link
goes down, or as a primary link
• MLPPP Bundle: allows frame relay to be carried over an
MLPPP bundle (inverse multiplexing)
• Sync Driver: allows configuration as one high speed frame
relay circuit
NOTE: To run frame relay over BRI channels see Chapter 11
CONFIGURING ISDN AND QSIG, section
11.2.1 Configuring the ISDN Port.
To run frame relay over Memotec’s T1/E1 fractional
channel, see Chapter 12 CONFIGURING T1/E1,
sections 12.2.1 Configuring the T1/E1 Port and
12.2.2 Configuring T1/E1 Channels.
5. Network Interface Type
This parameter allows the user to define the interface type. The
options available are as follows:
• for configuring a frame relay access port that connects to a
network device on the other side of the UNI, choose
UNI, user side
3008M300-004
9 CONFIGURING FRAME RELAY
• for configuring a device within the frame relay network that
is connected to user equipment outside the network, choose
UNI, network side
• for configuring a network node that performs switching
functions within the frame relay network, choose NNI
6. Link Management Scheme
This parameter monitors the status of PVC connections and
verifies the integrity of links to the frame relay network. The
standard chosen must match the standard configured on the
other side of the user-to-network interface (UNI). If the user
device is connected to a public frame relay, the standard for the
remote side can be requested from the service provider, or
automatic can be used to self configure this parameter.
To continue configuring the frame relay port, click on the
Extended tab. The screen shown in Figure 9-8 appears.
In the Link Mamagement Parameters group box, configure the
following:
7. Polling Interval (T391)
This parameter specifies (in seconds) how frequently the user
device at a UNI or NNI issues a Status Enquiry message.
8. Polling Verification (T392)
This parameter specifies the maximum number of seconds that
the network device at a UNI or NNI expects to wait between
Status Enquiry messages.
9. Full Enquiry Interval (N391)
This parameter determines the number of Status Enquiry
intervals that must pass before the user device at a UNI or NNI
issues a Full Status Enquiry message.
9-149
CXTool User Guide
Figure 9-8: Configuring the Frame Relay Port, Extended
10. Error Threshold (N392)
If the Interface Type is UNI-User side: this parameter
determines the number of unanswered Status Enquiry
messages that can occur within the “Link Management -
Monitored Events (N393)”. If a connection exceed the
9-150
threshold value, the user device at the UNI or NNI declares the
interface to be down.
If the Network Interface Type is UNI, Network Side: this
parameter determines the T392 timeouts that can occur within
the “Link Management - Monitored Events (N393).” If a
connection exceed the threshold value, the user device at the
UNI or NNI declares the interface to be down. A T392 timeout
occurs when the network device does not receive a Status
Enquiry message within the expected interval.
11. Link Management - Monitored Events (N 393)
This parameter determines the poll cycles of monitored events
that are counted to determine if the device at the remote end of
the link is still active. On the user side, a monitored event is the
transmission of a Status Enquiry message. On the network
side, it is the receipt of a Status Enquiry message or the
expiration of the T392 timer.
12. Link Management - LMI Flavor
This parameter determines if the behavior of the Link
Management is “strict” or “tolerant.” “Strict” implies that the
LMI frames containing error will be discarded, and “tolerant”
implies that LMI frames are interpreted but no errors are
registered.
13. Priority Queue - Queue #1
This parameter determines how frequently the queue for very
high priority outbound traffic is checked for frames awaiting
transmission. This value is meaningful only when compared to
frequency values assigned to very high, medium, and low
priority traffic queues. Queue parameters must be configured
so that q1 > q2 > q3 > q4, and q1 + q2 + q3 + q4 < 255.
14. Priority Queue - Queue #2
This parameter determines how frequently the queue for high
priority outbound traffic is checked for frames awaiting
transmission. This value is meaningful only when compared to
3008M300-004

frequency values assigned to very high, medium, and low
priority traffic queues. Queue parameters must be configured
so that q1 > q2 > q3 > q4, and q1 + q2 + q3 + q4 < 255.
15. Priority Queue - Queue #3
This parameter determines how frequently the queue for
medium priority outbound traffic is checked for frames
awaiting transmission. This value is meaningful only when
compared to frequency values assigned to very high, medium,
and low priority traffic queues. Queue parameters must be
configured so that q1 > q2 > q3 > q4, and q1 + q2 + q3 + q4 <
255.
16. Priority Queue - Queue #4
This parameter determines how frequently the queue for low
priority outbound traffic is checked for frames awaiting
transmission. This value is meaningful only when compared to
frequency values assigned to very high, medium, and low
priority traffic queues. Queue parameters must be configured
so that q1 > q2 > q3 > q4, and q1 + q2 + q3 + q4 < 255.
17. Congestion Management
When this parameter is enabled, the default, congestion
management techniques control the flow of data sent from this
connection. The frame relay protocol allows overloaded
network devices to discard frames, based on the resource
allocation value, to reduce congestion.
18. Resource Allocation (%)
This parameter determines the percentage of total system
memory resources that may be allocated to this connection. If
congestion management is enabled and resources for sending
data on the port exceed this percentage, excess frames are
discarded to prevent congestion.
3008M300-004
9 CONFIGURING FRAME RELAY
19. Send State Change Trap
When enabled, an SNMP trap will be sent to the management
station when the state of the link changes.
20. Filtering (Frame Relay, LAN, LLC2, Voice Routing, Voice
Routing Optimized, IP Tunnel, FR_USER)
When enabled, this parameter determines the type of traffic to
discard when the port speed falls below the value assigned to
the bandwidth parameter. This enables important traffic to flow
in backup situations when the link speed may be reduced.
Filtering is also activated on dial backup connections
regardless of the value of the bandwidth.
Frame Relay/ When long frames and short frames share the same UNI or
Fragmentation NNI, it may be necessary to fragment the long frames so that
(FRF.12) the short frames are not excessively delayed. Fragmentation
allows one VC carrying fragments of a long frame to be
interleaved with another VC carrying delay-sensitive traffic
and to pass both through the same interface.
Configuring The Dial feature enables the user to configure backup services,
Dial Service in the event that the frame relay link goes down. The options
available are as follows:
1. V.34 modem for data traffic
2. ISDN service for transport of voice and data traffic across an
ISDN network
To configure the Dial parameters, click on the Dial tab after
adding a sync port on a V.24 or V.35 card. The screen shown in
Figure 9-9 appears.
9-151
CXTool User Guide

link is taken down by dropping the DTR. The link will be

reactivated when frames are transmitted by raising the DTR.
2. Dial Backup Check Timer(s)
This parameter determines the maximum time for which the
frame relay software layer waits before polling (to check the
status of the primary link) and terminating connections of dial
backup ports when primary route partners related to these ports
have become active.
3. Dial Backup Delay Timer(s)
This parameter determines the number of seconds for which
the frame relay software layer waits before activating the dial
backup link.

To activate the V.34 section, the user is required to first select a

Figure 9-9: Configuring the Dial Backup Service
Configure the parameters listed below for Dial on Data
Terminal Ready (DTR).
1. Dial Port Inactivity Timer(s)
This parameter determines the duration (in seconds) for which
the port can remain idle between receiving frames, before a
Sync Driver and then the V.34 Dial Back-up modem from the
Hardware dialog box.
1. V.34 - Dial
This parameter determines the destination number of the call.
2. V.34 - Modem String
In this parameter, enter the appropriate AT Command—
intended for advanced modem settings if required.
3. Answer Enable
When enabled, the equipment is allowed to both receive and
place calls. When disabled, the equipment can only make calls.
To activate the ISDN section, the user is required to first
configure an ISDN interface in the ISDN section.
1. ISDN Dialing Number
This parameter allows the user to enter the destination number
from the ISDN Directory.

9-152 3008M300-004
 9 CONFIGURING FRAME RELAY

9.2.2 Configuring Frame Relay DLCIs

DLCIs are used to identify Permanent Virtual Circuits (PVCs)

within a frame relay port. When you configure DLCIs, you
associate a name and physical port with each DLCI number.

From the FR/FR ATM Interworking folder, select the DLCI

module. To add a frame relay DLCI, click on the Add (+)
button in the tool bar or select Add New from the pull-down
Edit menu. The screen shown in Figure 9-10 appears.

Configure the parameters listed below.

2. DLCI Name
This parameter is user configurable. For example, if the DLCI
goes to an endpoint in London, this DLCI can be named:
to_london.
3. DLCI #
This parameter assigns a unique number to a DLCI on a
particular port. If the user device is connected to a public
network, this number should be obtained from the network
provider.
4. Compression Enable
This parameter allows the user to enable data compression on
circuits that need to transmit large amounts of data within
limited bandwidth. Circuits that handle voice traffic will
bypass this compression, since voice frames are already
compressed. Figure 9-10: Configuring the Frame Relay DLCI

5. Backup DLCI
NOTE: When the data being transferred has already been
The parameter allows the user to define a DLCI that serves as a
compressed this option will create additional overhead
“backup” in the event that the primary physical link (and the
and is therefore not recommended.
DLCI associated with it) goes down. Note that this parameter is
configurable only after two or more DLCIs have been created.
For instance, if the user has configured three MPE-enabled

3008M300-004 9-153
CXTool User Guide
DLCIs (100, 101, and 102), then depending on which one is
already in use, the remaining two can be used as “backup.”
Note that once a DLCI has been used as “backup,” it cannot be
assigned to another configuration.
6. MPE
When enabled, this parameter allows the user to transmit traffic
from various sources such as SNA, X.25, Async, and voice
simultaneously, over one frame relay circuit. If this circuit
terminates in a third party FRAD (i.e., a non-Memotec device)
this parameter should be disabled due to the proprietary
implementation of this feature.
7. Fragmentation Size
When transmitting across the frame relay network to circuits
that support MPE, this parameter allows the user to break up
large data packets and reassemble the fragments when
received. Fragmentation breaks the data packet into smaller
fragments of a maximum size specified by Fragmentation Size.
Fragments are transmitted in separate frames that contain a
sequence identifier in the header. This enables the original
packet to be reassembled upon arrival at the destination.
For more information, see 9.1.2 Typical Frame Relay
Configuration, section entitled: Fragmentation.
9-154
8. DLCI Priority Level
This parameter allows the user to assign priority levels to
frames transmitted over the virtual circuit. The options
available to the user are:
• veryHigh: indicates that this circuit has very high priority.
Normally used for delay-sensitive traffic such as voice or
fax.
• high: indicates that this circuit has high priority. Normally
used for high priority interactive data traffic.
• medium: indicates that this circuit has medium priority.
Normally used for regular LAN traffic.
• low: indicates that this circuit has low priority. Used for low
priority data traffic.
NOTE: Priority levels only take effect if mpe (multiprotocol
encapsulation) is disabled. If mpe is enabled, priority
levels are determined automatically by the data type.
The most delay-sensitive traffic types (for example,
voice) are given the highest priority.
To continue configuring the frame relay DLCI, click on the
“Extended” tab. The screen shown in Figure 9-11 appears.
Configure the parameters listed below.
1. CIR Management
This parameter determines whether bandwidth management is
enabled for this virtual circuit. The options available as listed
below.
• disabled: indicates that congestion management is disabled
for this circuit.
• enabled_inbound: indicates that circuit congestion
management is enabled for inbound data. In the normal
3008M300-004

2. Trap Management - Billing Trap
Figure 9-11: Configuring the Frame Relay DLCI (Extended)
3. Trap Management - Status Change Trap
uncongested state, data received in the “Be” zone is tagged
with the de bit. When circuit congestion occurs, data
4. Pacing Rate
3008M300-004
9 CONFIGURING FRAME RELAY
transmitted with de = 1 is discarded. Excess data is held for
transmission until the next “Tc” window.
• monitor_inbound: indicates that congestion management
monitors the inbound data flow on this circuit, but takes no
steps to control it. de is not marked. This setting is used to
gather statistics.
• enabled_outbound: indicates that circuit congestion
management is enabled for outbound data. Under normal
uncongested conditions, data is restricted to the “Bc+Be”
zone, and data transmitted is not tagged.
• paced_outbound: indicates that the paced congestion
management is enabled for outbound data. This method is
the same as “enabled_outbound” but will not attempt to
catch up when bandwidth in the sliding time interval
window has gone unused. Instead it will continue pacing the
data and not allow any burst that might harm voice quality.
This method should always be used when voice is being
carried, the local access line has more bandwidth than
the remote site, and data and voice share the same PVC
or DCCI connection.
When enabled, this parameter generates an SNMP billing trap.
The trap provides information about the number of frames
transmitted over the circuit. This information can be collected
by a network management workstation and be used for billing
customers for their usage of the circuit.
When enabled, this parameter generates an SNMP trap every
time the status of the DLCI changes.
This parameter determines the maximum allowed rate of
outbound data for this circuit. It is used to calculate the pacing
9-155
CXTool User Guide
between frames when using the paced outbound management.
The value of this parameter should be set to the clock rate
(speed) of the slowest link in the data path.
5. Throughput Management - Committed Information Rate (bps)
[CIR]
This parameter determines the average data transmission rate
(bits/second) for inbound data at the user side of a frame relay
module.
CIR is the committed information rate. This value determines
the rate at which incoming user data will be transmitted onto
the frame relay network. A different CIR value can be
configured for each PVC.
6. Throughput Management - Committed Burst size (bits) [Bc]
This parameter determines the maximum number of inbound
data bits that the frame relay module agrees to transfer within
an established interval. This quantity of data is known as the
committed burst size. Transmission of this quantity of data is
guaranteed. The transmission interval is not a time period, but a
function of the quantity of incoming data and the data rate.
7. Throughput Management - Excess Burst size (bits) [Be]
This parameter determines the maximum number of inbound
data bits in excess of the “Bc” amount that the frame relay
module will attempt to transmit. This quantity of data is known
as the excess burst.
The Committed Burst size (Bc) determines the amount of data
that the system agrees to transmit. Excess burst is a fixed
amount of data that may be transmitted in addition to the Bc
amount. The delivery of excess burst data is not guaranteed. If
the network or module becomes congested, Be data may be
discarded.
8. EIR and Tc
The Excess Information Rate (EIR) and Committed Rate
Measurement Interval (Tc) parameters are “read-only.” The
9-156
values in these parameters are calculated on the basis of the
values entered in the CIR, Bc, and Be parameters. EIR is the
rate over and above CIR, and Tc is the average of the values in
Bc and CIR parameters.
9.2.3 Configuring Frame Relay Switching
Frame relay switching creates a data path between incoming
and outgoing DLCIs. The DLCI name associated with each
circuit is used to create the link. To see how Memotec devices
perform switching functions, refer to 9.1.2 Typical Frame
Relay Configuration, sections entitled: Frame Relay Switching
and Frame Relay Switching (MPE).
From the FR/FR ATM Interworking folder, select the Switch.
To configure the parameters in this module, click on the Add
(+) button in the tool bar or select Add New from the pull-
down Edit menu. The screen shown in Figure 9-12 appears.
Configure the parameters listed below.
1. Source DLCI
This parameter indicates the DLCI associated with the source
of the frame relay circuit. If the DLCI has already been
configured, it will appear in the pull-down list.
2. Destination DLCI
This parameter indicates the DLCI associated with the
destination of the frame relay circuit.
3. Advanced Frame Relay Switching
This parameter allows the user to configure advance switching
functions when MPE is enabled for this circuit. Refer to
9.1.2 Typical Frame Relay Configuration, section
entitled: Frame Relay Switching (MPE).
3008M300-004
 9 CONFIGURING FRAME RELAY

identify the type of traffic to be carried on the circuit. The

options available are the following:
• pidFR: the current connection is using the frame relay
protocol
• pidLan: the current connection is transmitting a LAN
protocol
• pidX25: the current connection is using the X.25 protocol
• pidCcm: the current connection is using the Common
Console protocol (CX 1000 only)
• pidGmf: the current connection is transmitting multiplexed
traffic from different sources
• pidLlc2: the current connection is transmitting LLC2 data
• pidVR: the current connection is routing voice traffic
• pidPPP: the current connection is routing voice traffic using
the MLPPP protocol
• pidVRopt: the current connection is routing voice traffic
using the optimized version. To use this value, the
Bandwidth Optimization parameter should be enabled.
• pidIPTN: the current connection is routing traffic using an IP
tunnel
• pidADX: the current connection is routing traffic over ATM
Data Exchange Interface

Figure 9-12: Configuring the Frame Relay Switch • pidAAL5: the current connection is routing traffic over ATM
Adaptation Layer 5 (AAL5)
4. Advanced Frame Relay Switching - Protocol ID
• pidFR_USER: the current connection is routing traffic
Protocol IDs listed here are proprietary to Memotec and used directly to a specific service
whenever MPE is enabled. This parameter allows the user to
5. Source Reference No.
This parameter is the reference number assigned to the source
of the frame relay circuit. When multiple users transmit using

3008M300-004 9-157
CXTool User Guide

the same Protocol ID the source reference number uniquely

identifies the data of each source.
6. Destination Reference No.
This parameter is the reference number assigned to the
destination of the frame relay circuit. When multiple users
transmit using the same Protocol ID the destination reference
number uniquely identifies the destination of the data.

9.2.4 Configuring the ATM Interworking Port

The ATM Interworking Port allows the user to take advantage

of FRF services. It can be configured according to different
requirements of the user. To have an idea of the different FRF
services supported by Memotec’s CX products, refer to
Chapter 8 CONFIGURING ATM, especially section
8.1.2 Protocols Supported and Voice.

In the Frame Relay module, Port component, enable the ATM

Interworking Port. The ATM Interworking Port Type group
box becomes available, as shown in Figure 9-13.

To configure FRF.5, add an ATM VCL if one is not already

configured (see 8.2.2 Configuring the Virtual Channel), and
then, when finished, click “Next” on the Frame Relay Port
dialog box. The screen shown in Figure 9-14 appears.

Configure the parameters listed below.

1. Frame relay de to ATM clp mapping
This parameter determines the mode that will be selected for
loss priority mapping in the frame relay to ATM direction.
When congestion occurs, the network may elect to drop low-
priority cells, as identified by their Cell Loss Priority (clp) or
Discard Eligibility (de) status. When traffic flows in the frame
relay to ATM direction, the Interworking Function (IWF) maps
Figure 9-13: Configuring the ATM Interworking Port
the frame relay de to the ATM clp. This mapping scheme
enhances the ATM network's ability to cope with congestion
and alert end users to throttle back their traffic. The options
available are listed below.
• mode1: indicates that the Discard Eligibility (de) field in the
Q.922 core frame is copied unchanged into the de field in

9-158 3008M300-004

2. ATM clp to Frame Relay de Mapping
3. ATM clp
Figure 9-14: Configuring FRF.5 Services
the FR-SSCS PDU header and mapped to the ATM Cell
Loss Priority (clp) of every ATM cell generated by the
segmentation process of that frame.
• mode2: indicates that the de field in the Q.922 core frame is
copied unchanged into the de field in the FR-SSCS PDU
header and the ATM clp of every ATM cell generated by the
3008M300-004
9 CONFIGURING FRAME RELAY
segmentation process of that frame will be set to a constant
value (either 0 or 1). The value is decided when the
connection is set up, and is used for all cells generated from
the segmentation process of every frame, until the ATM
connection characteristics are changed.
This parameter determines the mode that will be selected for
loss priority mapping in the ATM to frame relay direction.
When congestion occurs, the network may elect to drop low-
priority cells, as identified by their Cell Loss Priority (clp) or
Discard Eligibility (de) status. When traffic flows in the ATM
to frame relay direction, the Interworking Function (IWF)
maps the ATM clp to the frame relay de. This mapping scheme
enhances the ATM network's ability to cope with congestion
and alert end users to throttle back their traffic. The options
available are listed below.
• mode1: indicates that if one or more ATM cells belonging to
a frame has its clp field set to one or if the de field of the FR-
SSCS PDU is set to one, the de field of the Q.922 core frame
should be set.
• mode2: indicates that no mapping is performed from the
ATM layer to Q.922 core layer. The FR-SSCS PDU de field
is copied unchanged to the Q.922 core frame de field,
independent of clp indications received at the ATM layer.
This parameter indicates that when mode2 is selected for the
frame relay de to ATM clp Mapping parameter, then “clp”
9-159
CXTool User Guide

determines the Cell Loss Priority (clp) value that will be passed
to the ATM cell level.
The options available are listed below.
• zero: indicates that the clp bit will be set to 0 at the ATM cell
level.
• one: indicates that the clp bit will be set to 1 at the ATM cell
level.

To configure FRF.8, follow the steps outlined below.

1. Configure a frame relay port (e.g., Port2)
2. Select Service Interworking (FRF.8) from the frame relay port
3. Configure a DLCI (in this case on Port2), as illustrated in
Figure 9-15.
4. Select an MPE Type
5. Click on Next. The screen shown in Figure 9-16 appears.
6. Select (or configure a new) ATM VCL. Refer to
8.2.2 Configuring the Virtual Channel.
7. de to clp
This parameter determines the mode that will be selected for
Discard Eligibility (de) to Cell Loss Priority (clp) mapping in
the FR to ATM direction.
The options available are these:
• mode1: the de field in the Q.922 core frame is mapped to the Figure 9-15: Configuring a DLCI for FRF.8
ATM clp field of every ATM cell generated by the
segmentation process of that frame. the segmentation process of every frame, until the ATM
• mode2: the ATM clp field of every ATM cell generated by connect characteristics are changed.
the segmentation process of that frame is set to a constant 8. de Bit
value (either 0 or 1). The value is decided when the This parameter determines the Discard Eligibility (de) value
connection is set up, and is used for all cells generated from that will be passed to the Q.922 core frame when value

9-160 3008M300-004
 9 CONFIGURING FRAME RELAY

9. clp to de
This parameter determines the mode that will be selected for
Cell Loss Priority (clp) to Discard Eligibility (de) mapping in
the ATM to FR direction. The options available are listed
below.
• mode1: indicates that if one or more ATM cells belonging to
a frame has its clp field set to one, the de field of the Q.922
core frame should be set to one.
• mode2: indicates that the de field of the Q.922 core frame
shall be set to a constant value (either 0 or 1) configured at
service subscription time.
10. clp Bit
This parameter determines the Cell Loss Priority (clp) value
that will be passed to ATM when value “mode2” is selected for
the Frame Relay de to ATM clp Mapping parameter. The
options available are listed below.
• zero (1): The clp bit will be set to 0 at the ATM cell level.
• one (2): The clp bit will be set to 1 at the ATM cell level.
11. FECN to EFCI
This parameter determines the mode that will be selected for
Forward Explicit Congestion Notification (FECN) to Explicit
Forward Congestion Indicator (EFCI) mapping in the FR to
ATM direction. The options available are listed below.
• mode1: indicates that the FECN field in the Q.922 core
Figure 9-16: Configuring a VCL for FRF.8
frame will be mapped to the ATM EFCI field of every cell
“mode2” is selected for the ATM clp to Frame Relay de generated by the segmentation process of the AAL5 PDU
Mapping parameter. The options available are these: containing the information of that frame. This mode
provides congestion indication to the end-points where
• zero: the de bit will be set to 0 in the Q.922 core frame. higher-level protocol entities might be involved in traffic
• one: the de bit will be set to 1 in the Q.922 core frame.

3008M300-004 9-161
CXTool User Guide

control mechanisms. This mode may not be desirable with

future reactive congestion control mechanisms.
• mode2: indicates that the FECN field in the Q.922 core
frame will not be mapped to the ATM EFCI field of cells
generated by the segmentation process of the AAL5 PDU
containing the information of that frame. The EFCI field is
always set to “congestion not experienced”.
12. Configure frame relay switching functions. Refer to
9.2.3 Configuring Frame Relay Switching.

To see an illustration of a typical FRF.8 configuration, refer to

8.1.6 Typical ATM Network.

To configure FRF.8+, follow the steps outlined below.

1. Configure a frame relay port (e.g., Port2)
2. Select Service Interworking (FRF.8+) from the frame relay
port
3. Configure a DLCI (in this case on Port2), as illustrated in
Figure 9-17.
4. Click on Next. The screen shown in Figure 9-18 appears.
If an ATM VCL has already been configured, select it from the
ATMVCL column and associate it with an appropriate protocol
ID in the PID column. To add (i.e., create) an ATM VCL, click
on ADD. For details on configuring virtual channels, refer to
8.2.2 Configuring the Virtual Channel.
Figure 9-17: Configuring a DLCI for FRF.8+

9-162 3008M300-004
 9 CONFIGURING FRAME RELAY

5. Pid
This parameter allows the user to associate an ATM VCL to a
specific protocol ID (Pid). The options available are listed
below.
• pidFR: frame relay protocol
• pidLan: LAN protocol
• pidX25: X.25 protocol
• pidLlc2f: LLC2 data
• pidVR: Voice traffic
• pidPPP: MLPPP protocol (for future use)
• pidVRopt: Voice traffic using the optimized version
• pidIPTN: IP tunnel (for future use)
• pidADX: ATM Data Exchange Interface
Notice that Pids 14 and 15 are user-defined
6. For a description of each of the remaining parameters namely,
Pid, de to clp, de Bit, clp to de, clp Bit, and FECN to EFCI,
see the section above on configuring the FRF.8 services.

To see an illustration of a typical FRF.8+ configuration, refer to

8.1.6 Typical ATM Network.

9.2.5 Configuring Simplex Services

Figure 9-18: Configuring ATM Service Interworking, DLCI for FRF.8+
Memotec devices have the ability to send and receive frame
relay traffic using Simplex Broadcast over a satellite frame
relay network. Figure 9-19 shows that ports 2, 3, and 4 are
sending traffic to port 1, which forwards the frame relay traffic
to the satellite network.

3008M300-004 9-163
CXTool User Guide
From the FR/FR ATM Interworking folder, select the Simplex.
To configure the parameters in this module, click on the Add
(+) button in the tool bar or select Add New from the pull-
down Edit menu. The screen shown in Figure 9-19 appears.
9.2.6
Figure 9-19: Configuring the Simplex Broadcast Service
9-164
Configure the parameters outlined below.
1. Name
This parameter allows the user to change the default name.
2. Broadcast Port
This parameter allows the user to assign a port that forwards
the frame relay traffic to the satellite network.
3. Receive/Transmit
This parameter determines the direction of the call.
4. Ports - Available/Chosen
This column indicates the number of ports that are already
configured and are available for use. To select them, use the
arrow button and more them to the Chosen column.
If no ports are showing in the Available column, click on Add
to configure one or more ports.
Configuring Switched Multicast Service
As discussed in 9.1.1 Supported Frame Relay Features,
subsection Multicast Services, Memotec devices provide a
range of multicast services.
From the FR/FR ATM Interworking folder, select the
Multicast. To configure the parameters in this module, click on
the Add (+) button in the tool bar or select Add New from the
pull-down Edit menu. The screen shown in Figure 9-20
appears.
Configure the parameters outlined below.
1. Multicast Group Name
This parameter allows the user to change the default name.
3008M300-004
 9 CONFIGURING FRAME RELAY

3. Root
This parameter allows the user to select a DLCI that serves as
the root.
4. Members - Available/Chosen
This column indicates the number of DLCIs that are already
configured and are available for use. To select them, use the
arrow button and more them to the Chosen column.
If no DLCIs are showing in the Available column, click on Add
to configure one or more DLCIs.

9.2.7 Configuring Non-Switched Multicast Services

The non-switched multicast service allows non-frame relay

applications to access frame relay multicast services through
Memotec devices.

From the FR/FR ATM Interworking folder, select the Bundle.

To configure the parameters in this module, click on the Add
(+) button in the tool bar or select Add New from the pull-
down Edit menu.

The screen shown in Figure 9-21 appears.

Configure the parameters as outlined below.

Figure 9-20: Configuring the Multicast Service
2. Service Type
This parameter allows the user to select one of the following
services: oneWay; twoWay; nWay; twoWaySinglePass. For a
detailed explanation of each of these options, refer to
9.1.1 Supported Frame Relay Features, section Multicast
Services.
1. Service Type
This parameter allows the user to select one of the following
services: oneWay; twoWay; nWay; twoWaySinglePass. For a
detailed explanation of each of these options, refer to
9.1.1 Supported Frame Relay Features, section
entitled: Multicast Services.
2. MPE
This parameter allows the user to enable MPE on a particular
DLCI. Note that, in a bundle, when MPE is enabled or disabled

3008M300-004 9-165
CXTool User Guide

3. Members - Available/Chosen
This column indicates the number of DLCIs that are already
configured and are available for use. To select them, use the
arrow button and more them to the Chosen column.
If no DLCIs are showing in the Available column, click on Add
to configure one or more DLCIs.

Figure 9-21: Configuring Frame Relay, Bundle Service

the selection takes precedence over the selection made at the

DLCI level in the MPE Type parameter.

9-166 3008M300-004
 10 CONFIGURING IP

This chapter describes the features of IP that are supported by

CX products, and how to create IP configurations.

For an introduction to IP, see Chapter 25 INTRODUCING IP.

3008M300-004 10-167
CXTool User Guide

10.1 Memotec’s CX Family and the IP Address • ARP

Resolution
Environment Protocols • Reverse ARP
• Inverse ARP
The TCP/IP protocols transfer status information about the
network itself as well as moving payload data. In addition to
the usual routing and protocol support, CX products support IP Routing • RIP
Protocols
• RIP II
10.1.1 IP Routing
• OSPF
CX products route IP over many LAN/WAN services
including:
Management • SNMP
• Frame Relay (RFC 1490) Protocols
• ICMP
• Ethernet 802.3
• Token Ring 802.5
Dynamic IP • Boot - P Relay
• ATM (RFC 1483) Addressing
• DHCP Relay
• PPP

10.1.2 Protocol Support Other • UDP

Protocols
• TFTP
CX products support the following IP-related protocols:
• NBMA
• IP QoS
• TCP
• VRRP

10.1.3 Features

IP Filtering IP filtering has a two-fold purpose:

10-168 3008M300-004

• to enable/disable packet movement through the network;
• to prioritize traffic for timely delivery (on WAN links only).
Each filtering definition contains a source address, a
destination address, and source and destination port address.
These addresses can be either device addresses, subnets,
network addresses, or default address (0.0.0.0)
Forwarding
When the IP router receives a datagram, it checks the filter
table to determine whether any forwarding priority or discard
action has been configured for the source and destination
address combination that is specified in the IP header. If the
address combination appears in the table, the router takes the
specified action. If the addresses do not appear, the router
forwards the packet with normal priority. With respect to
outgoing packets, the IP router performs filtering on LAN and
WAN traffic.
Prioritization
Efficient network performance requires that the delay-sensitive
nature of certain traffic types be taken into consideration. As a
result, priority queues are established to ensure that delay-
sensitive traffic, such as voice, receives the highest priority.
Priority is also used when the amount of data to be transmitted
exceeds network capacity. Data stored in lower priority queues
is only transmitted when higher priority queues are empty.
Memotec implements four priority queues:
3008M300-004
10 CONFIGURING IP
• low
• normal
• high
• voice (highest)
The IP filtering feature allows a network administrator to both
enable or disable the movement of the packet, matching the
pattern, or to set a priority for the packet.
Note that prioritization is performed on outgoing WAN (not
LAN) packets only - i.e., packets leaving CX devices.
IP Tunneling Tunneling enables the transport of voice and SNA end to end in
an IP network. IP tunneling is an end-to-end transport
mechanism for the encapsulation of non-IP traffic over an IP
backbone. In Memotec’s implementation, a tunnel layer is
added over UDP in order to provide tunneling services to upper
layer applications. A tunnel header including protocol ID is
added at the source station and removed at the destination
station.
IP NBMA IP NBMA is a function intended for the transmission of IP
traffic over Multi-Access networks such as Frame Relay and
ATM. Basically, it facilitates IP configuration to the extent that
only one IP address is required for the local IP port which may
be connected to multiple WAN destinations. In the case of
Frame Relay, CXTool associates the local IP address with each
DLCI and IP address of the WAN destination. If the destination
10-169
CXTool User Guide

IP address is not specified, Inverse Address Resolution by way of changing the IP TOS bits in the IP header and they
Protocol is used to learn the IP address. sort traffic (separate) through the configuration of IP QOS.

The IP QOS implementation is consistent with the IETF

differentiated services RFC 2474 and RFC 2475. It uses the
IP TOS bits within the IP header to signify the priority to a packet.
The QOS implementation allows the user to:
192.1.1.2
DLCI 20
• configure the filtering table to identify packets that are to be
tagged and prioritized before being routed through CX devices
Frame
192.1.1.1 DLCI 30
Relay • route and forward packets on the basis of their priority.
IP
192.1.1.4 Applications can therefore be routed to the appropriate network
IP
service.
DLCI 40
• set IP priority for internally generated IP packets. Gateway
192.1.1.6
applications.
IP
In Figure 10-2, two VCs have been configured: one high
priority and one low priority. The local IP port on CX950 A is
Figure 10-1: IP NBMA Example: IP Routing over Frame Relay connected to multiple WAN destinations. IP QOS is enabled
for traffic going to CX950 B, but not to CX950 C, and its
In the example of Figure 10-1, a local CX1000e is connected to
three remotes through a Frame Relay network. Normally, a
separate IP address would be required at the local IP port for
each remote destination in order for the CX1000e to properly
route incoming traffic. With the IP NBMA feature, only a
single IP address (192.1.1.1) is required at the local IP port.
Traffic exiting this port is routed according to its Frame Relay
DLCI.

IP QOS IP QOS is a function intended for the transmission of all IP

traffic. When enabled, CX devices shape and sort the IP
traffic according to the priorities specified by the user. CX
devices shape traffic (assign priority) through the filtering table

10-170 3008M300-004
 10 CONFIGURING IP

implementation enables IP packets to use the high priority parameters that the user is required to configure for those
ATM VC. services.

10.1.4 Typical IP Configuration

Using Figure 10-2 as a point of reference, let us assume that

CX950 A is configured to send the following types of traffic on
B CX950 one port across an ATM network:
1. voice and IP to CX950 B, with NBMA and QOS functions
0
1V CI=2 enabled
VPI= I=40
1 VC
A VPI= 2. IP to CX950 C, with only NBMA function enabled
CX950 192.1.1.4
192.1.1.1 3. connected LAN on CX950 A
ATM
VPI=1 C CX950 In our example above, CX950 A has the following cards:
VCI=50
192.62.2.1
• Analog Voice FXS (for voice)

192.1.1.6 • ATM Cell I/O (for the ATM network)

• Fast Ethernet (for LAN)

Configuring In order for the voice and LAN traffic to be transported from
NBMA-QOS CX950 A to CX950 B, the configuration required on CX950 A
Functions is given below.
Figure 10-2: Configuring IP QOS Services over ATM
Configuring Voice
Backup The user can configure the Virtual Redundancy Routing • Voice Station: CPU on CX950 A
Routing Protocol (VRRP) on two devices in a LAN environment. In the
Service event that the main router is disabled, Memotec devices will • Voice Channel
automatically divert traffic to the second router. Analog Voice FXS 1.1
Home Extension: 222
The next section gives a brief overview of typical IP services Local Extension: 222
that are possible with Memotec devices, together with a list of

3008M300-004 10-171
CXTool User Guide

• DSP Channel • WAN Link

Analog Voice FXS 1.1 NBMA Interface: Enabled
Vocoder Group: acelpII Peer Address: 192.1.1.4
WAN Link Type: IP QOS
• Dialing Plan: (digits dialed: 3133001) IP QOS: ATMVCL2, real time
Dial Pattern: 3XX; IP QOS: ATMVCL!, default service
Remote Extension: --- +++
Called Number: --- ++++ Configuring ATM

• WAN Trunk (for voice) In the configuration below, two virtual circuits are configured:
Transport Link: IP Tunnel a high priority CBR ATM circuit to carry voice traffic and a
Name: IP Tunnel1 (for Voice) low priority VBR circuit to carry LAN. This ensures that the
Destination Address: 192.1.1.4 voice traffic is not delayed in the ATM backbone.
Voice Pattern: xxx. This call will be routed across the
network based upon the pattern used in this parameter, Note that when an IP tunnel is used, the traffic in the tunnel is
which should match that in the Remote Extension automatically treated as high priority.
parameter • ATM Port
Configuring LAN ATM Cell I/O 2.1

• IP Port
• ATM Virtual Circuit (for voice/NBMA-Q0S)
IP Address: 192.62.2.1
Subnet Mask: 255.255.255.0 Name: ATMVCL1
AAL Type: aal5
• Link Type VPI: 1; VCI: 20
Fast Ethernet 3.1 Encapsulation: llcEncapsulation
Circuit Type: CBR
Configuring WAN
• IP Port • ATM Traffic Services (for voice/NBMA-QOS)
IP Address:192.1.1.1 Traffic Type: CBR
Subnet Mask: 255.255.255.0 PCR: 300
CDVT: 0

10-172 3008M300-004
 10 CONFIGURING IP

• ATM Virtual Circuit (for LAN/NBMA-QOS) • WAN Link

Name: ATMVCL2 NBMA Interface: Enabled;
AAL Type: aal5 Peer Address: 192.1.1.6
VPI: 1; VCI: 40 WAN Link Type: ATMVCL3
Encapsulation: VCMultiplexRoutedProtocol
Circuit Type: UBR Configuring ATM
• ATM Port: ATM Cell I/O 1.1
• ATM Traffic Services (for LAN/NBMA-QOS)
• ATM Virtual Circuit (for LAN/NBMA)
Traffic Type: UBR
Name: ATMVCL3
Configuring IP QOS (for sorting traffic) AAL Type: aal5
VPI: 1; VCI: 50
• ATMVCL1 (carrying voice traffic); Service Provided: 5-Real Encapsulation: VCMultiplexRoutedProtocol
Time Circuit Type: UBR
• ATMVCL2 (for carrying IP/LAN traffic); Service Provided: 99-
Default Service • ATM Traffic Services (for LAN/NBMA)
Traffic Type: UBR
Configuring In order for the LAN traffic to be transported from CX950 A to
NBMA CX950 C, the configuration required on CX950 A is given
Configuring As mentioned above, CX products have the ability to shape
Functions below.
Traffic traffic (assign priority) through the filtering table by way of
Shaping changing the IP TOS bits in the IP header. Using Figure 10-3
Configuring LAN
as a point of reference, we illustrate how traffic can be shaped,
Since the LAN IP port has already been configured (see using CXTool.
above), we can proceed to Step 2.
Assume that a CX950 is configured with two WAN circuits and
Configuring WAN the filtering services are enabled on both, one for very high
priority traffic and the other with low priority traffic.
• IP Port
IP Address:192.1.1.1 The configuration for each service is illustrated below.
Subnet Mask: 255.255.255.0

3008M300-004 10-173
CXTool User Guide

• IP Station (Filter Table)

Source Address: 199.1.1.1
Source Netmask: 255.255.255.0
Destination Address: 199.1.1.4
Destination Netmask: 255.255.255.0
CX950
199.1.1.1 CX900 Protocol: 17-UDP
Frame
Relay
Start Port Number: 65434 IP Tunnel
199.1.1.4 End Port Number: when Start and End Port Number is the
192.62.2.1
188.62.2.1 same, leave this parameter empty
Action: priority_very_high
• IP Port

192.62.2.3
IP TOS: Enabled
Web Server
Default Service: Precendence-000-Best Effort

188.62.2.5
Figure 10-3: Configuring Traffic Shaping
In the example illustrated in Figure 10-3, we are assuming that
voice has been configured for transport through an IP Tunnel to
which we are giving high priority, and that the priority for LAN
traffic is set to “Best Effort”.
Configuring As mentioned above, CX products have the ability to sort
We are also assuming that both voice (shaped) and LAN traffic
(unshaped) are configured to go across a Frame Relay
Network. The following configuration illustrates how to filter
traffic that needs to be shaped and how to set the parameters for
non-shaped traffic.
NOTE: When IP TOS is enabled on this port and Default
Service is set to “000”, it implies that traffic other than
voice (e.g., LAN in Figure 10-3) is not shaped, and the
network will “do its best” to send it to its destination.
Traffic traffic according to the priority selected by the user. Using
Sorting Figure 10-4 as a point of reference, we illustrate how traffic can
be sorted with CXTool.
Let us assume that CX950 is configured with two WAN
circuits and the IP QOS service is configured to send voice on a
high priority circuit and IP/LAN data on a relative low priority
circuit.

10-174 3008M300-004
 10 CONFIGURING IP

The configuration for each service is illustrated below. • Voice -WAN Trunk
IP Tunnel
Destination Address: 199.1.1.4
• IP
IP Port 199.1.1.1
CX950
199.1.1.1 CX900 IP WAN Interface: IP QOS
ATM
Service Provided: 5-Real Time
199.1.1.4 ATMVCL2
192.62.2.1
188.62.2.1
In the above example, the same IP port is configured to
separate traffic according to the priority established in the
“Service Provided” parameter for each ATMVCL.
192.62.2.3 Web Server

Configuring Figure 10-5, illustrates how OSPF services can be configured

188.62.2.5 OSPF on CX products. Let us assume that CX900e (B) in Area
Figure 10-4: Configuring Traffic Sorting Services 3.3.3.3 is configured as an OSPF router. It sends information to
the Host(s) in Area 3.3.3.3 and to units in other Areas and
Configuring LAN receives information from the Host in Area 3.3.3.3 and from
units in other Areas.
• LAN
IP Port: 196.62.2.1
Subnetmask: 255.255.255.0
• WAN Interface
IP Port: 199.1.1.1
WAN Link: IP QOS
Service Provided: 99-Default Service
ATMVCL1

Configuring Voice

In this example we shall assume that the Voice Station, Dialing

Plan, Voice Channels, DSP Channels are already configured.

3008M300-004 10-175
CXTool User Guide

• OSPF Area
Autonomous System (AS) Area ID: 3.3.3.3
Authorization for area ID 3.3.3.3: None
AREA 1.1.1.1
Authentication for Area ID 0.0.0.0: None
Enable “Import As External Packets”
Host R • IP Station
AREA 3.3.3.3 Enable OSPF
Host Choose Area: 0.0.0.0 (default)
R*
AREA 0.0.0.0 192.1.1.1 Choose Area: 3.3.3.3
204.1.1.2

R
CX900e R Configuring IP Port
R
• IP Port
R IP Address: 192.1.1.1
Subnet Mask: 255.255.255.0
Routing Protocol: ospf
R*
BACKBONE (Area 0) • Link Type
ATM
R • IP Port
* Area Border Router IP Address: 204.1.1.2
AREA 2.2.2.2
Subnet Mask: 255.255.255.0
Routing Protocol: ospf
Figure 10-5: Configuring OSPF Services across an ATM
Network • WAN Link Type
In order for CX900e to service an OSPF router, the ATM
configuration required is given below.
Configuring ATM
Configuring OSPF ATM Cell I/O 1.1

10-176 3008M300-004
 10 CONFIGURING IP

• ATM Virtual Circuit

Name: ATMVCL1 Autonomous System (AS)
AAL Type: aal5
AREA 1.1.1.1
VPI: 1; VCI: 50
Encapsulation: VCMultiplexRoutedProtocol CX900e (A)
Circuit Type: UBR
Host R
• ATM Traffic Services 205.1.1.2
RIP
Traffic Type: UBR AREA 3.3.3.3
R*

Configuring In Figure 10-6, a Memotec device that is configured with RIP 192.1.1.1 Host
204.1.1.2
RIP Services services has been added to the scenario examined above. It R CX900e (B)
illustrates how Memotec devices can be configured for RIP R R
and OSPF services. Let us assume that CX900e (A) and
CX900e (B) have RIP and OSPF ports configured to exchange R
routing information.
AREA 0.0.0.0
R*
BACKBONE (Area 0)

AREA 2.2.2.2 * Area Border Router

Figure 10-6: RIP Services across a Frame Relay Network with

OSPF

In order for CX900e (B) to exchange information with routers

in Areas 1, 2, and 3 and with CX900e (A), the configuration
required on CX900e (B) is given below.

Configuring OSPF

3008M300-004 10-177
CXTool User Guide

• OSPF Area Configuring Frame Relay

Area ID: 3.3.3.3 V.35H 1.1
Authentication: None FRDLCI: 100 (IP Port1 configured for OSPF)
Authentication for Area ID 0.0.0.0: None FRDLCI: 200 (IP Port2 configured for OSPF)
Enable “Import As External Packets” FRDLCI: 300 (IP Port3 configured for RIP)

• IP Station The next section focuses primarily on how to configure IP

Enable RIP services on Memotec devices with CXTool. It adheres to the
Enable OSPF sequence in CXTool and provides a description of all the
Enable “As Boundary Router” to configure this OSPF port parameters the user will counter during configuration.
as Autonomous System
Choose Area: 0.0.0.0 (default)
Choose Area: 3.3.3.3 10.2 Configuring IP with CXTool
This section describes how to configure IP on a CX product.
Configuring IP Port The following procedures are organized into manageable
• IP Port1 blocks that correspond to the modules presented in the
Navigation panel of the CXTool user interface.
IP Address: 192.1.1.1
Subnet Mask: 255.255.255.0
Routing Protocol: ospf 10.2.1 Configuring the IP Station
• IP Port2 The IP Station module contains the global IP parameters
IP Address: 204.1.1.2 associated with a specific hardware CPU, and includes tables
Subnet Mask: 255.255.255.0 for static routes, ARP, and filtering.
Routing Protocol: ospf
From the IP folder, select the Station module. Click on the Add
• IP Port3 (+) button in the tool bar or select Add New from the pull-
IP Address: 205.1.1.2 down Edit menu. The following screen appears:
Subnet Mask: 255.255.255.0
Routing Protocol: rip
• WAN Link Type
Frame Relay

10-178 3008M300-004
 10 CONFIGURING IP

2. Directed Broadcast Forwarding

When enabled, this port transmits directed broadcasts to the
network.
3. Time To Live (TTL)
This value specifies the number of hops that packets are
allowed to take before they are discarded by the network.
Every router that sees this packet will decrement the TTL value
by one; if it reaches 0, the packet will be discarded. The setting
of this parameter to zero will disable routing functions. This
parameter should be set to 16 for routing applications.
4. Netmask Reply
When enabled, this parameter determines the address mask that
correspond to its IP address. If this parameter is disabled, then
no Internet Control Management Protocol (ICMP) address
mask requests are sent, and any ICMP address mask replies for
that local IP address are ignored.
5. Send Time Exceeded
When this parameter is enabled, a Send Time Exceeded packet
is sent by the gateway when it discards a datagram due to an
expired “Time To Live” field.
6. Send Redirected
Figure 10-7: Configuring the IP Station When this parameter is enabled, a Redirect message is sent by
the gateway. Upon receiving such a message, the host updates
its routing information according.
Configuring In the Global folder, configure the parameters listed below.
Global 7. Ping Reply
Parameters
1. IP Forwarding
When this parameter is enabled and the host is pinged, the host
When this parameter is enabled, it indicates that this port is
sends out ICMP Echo replies to the network.
acting as an IP gateway for datagrams received by, but not
addressed to, this port. This parameter should be enabled for all 8. Send Unreachable
router applications. When this parameter is disabled, no IP When this parameter is enabled, the host sends a Destination
routing is performed. Unreachable message. This message is generated to indicate
that the designated transport protocol is not supported or that it

3008M300-004 10-179
CXTool User Guide
is unable to inform the sender that the designated transport
protocol (e.g., UDP) is unable to process the datagram.
9. OSPF Enabled
This parameter determines whether or not the OSPF router in
the local Memotec unit is active.
10. RIP Configuration
The Routing Information Protocol (RIP) is used to
communicate routing information between routers on the
network. RIP accomplishes this task by sending the route table
contents to other routers at regular intervals. Each RIP packets
describes the contents of the sending router’s routing table. RIP
works with IP to allow interconnected routers to share
information about available routes. When more than one route
is available to the same destination, routers can compare the
number of hops via each route and choose the most efficient
path. The options available are as mentioned below.
• RIP: routes traffic dynamically based on the information in the
routing table of each router.
• RIP2: integrates all the RIP features, plus the ability to support
subnetting. If non standard subnetting is used, RIP2 must be
used.
• None: indicates that this port is configured for static routing as
opposed to dynamic routing, and RIP is disabled.
• Poison Rule: indicates whether or not RIP (routing information
protocol) and RIP-2 apply the poison rule when two routers
exchange their routing information. The poison rule causes any
route learned from an IP port not to be advertised back to the
original port, with its metric set to the poison value of 16 hops.
11. OSPF Configuration - Router ID
This parameter determines the numerical ID used to identify
the Memotec router connected to the console port. This ID
10-180
must be unique within the autonomous system (section of an
internetwork where information and data packets are
exchanged). By default, this parameter takes the value of one
of the router's IP interface addresses if no other value is
entered. The user must enter the router ID in the format of an
IP address (i.e., n.n.n.n), although it does not have to be an
actual address.
12. OSPF Configuration - AS Boundary Router
This parameter allows the user to configure a non- OSPF port
i.e., outside the autonomous system.
13. Area
This parameter permits users to configure the OSPF area. Note
that the backbone area (0.0.0.0) is preconfigured by the system.
14. Hardware CPU
The parameter allows the user to choose the hardware CPU that
is associated with this IP station. For the CX800, CX900e, and
CX950, there is only one CPU. The CX1000e and CX2000 can
have multiple CPU’s and, therefore, multiple IP stations.
Configuring Static routes are user-defined routes that packets will follow
the Static when traversing the network. Static route entries can only be
Route Table defined properly after all IP ports have been configured. To
build a static route table, click on the Static Route Table. The
following screen appears:
3008M300-004
 10 CONFIGURING IP

3. Next Hop Address

This parameter is the IP address of the next device to which
traffic is going.
4. Destination Netmask
This parameter allows the user to define a netmask, which is a
32-bit mask that indicates which address bits of the destination
network configured, belong to the network and subnetwork
fields and which bits belong to the host field.
5. Metric
This parameter indicates the estimated number of hops to reach
the destination network defined in the “Destination Network”
parameter.

Figure 10-8: Configuring the IP Static Route

Configure the parameters listed below.

1. IP Local Interface
This parameter represents the IP address of the port to which
the packet is destined.
2. Destination Network
This parameter determines the address of the destination
network.

3008M300-004 10-181
CXTool User Guide

Configuring To build a static ARP table and enter the IP address and
the Static corresponding physical address of the device, click on the
NOTE: Static ARP is an advanced function and should be used
ARP Table Static ARP Table. The following screen appears: with care.

Configuring The filter table is used to apply filtering (priority assignment or

the Filter forwarding/discard action) to packets that are received from a
Table specific source and sent to a specific destination. Each filtering
entry includes a source address and a destination address.

To build a filtering table, click on the Filter Table. The

following screen appears:

Figure 10-9: Configuring the IP Static ARP

Address Resolution Protocol (ARP) provides dynamic

mapping between IP addresses and hardware addresses or
physical addresses. Since most hosts support dynamic address
resolution, the user need not specify static ARP cache entries.
Configuring a static ARP table results in a permanent entry in
the ARP cache which maps the 32-bit IP addresses to 48-bit Figure 10-10: Configuring the IP Filter
physical addresses.

10-182 3008M300-004
 10 CONFIGURING IP

Figure 10-12: Configuring the IP Filter (Continued)

Figure 10-11: Configuring the IP Filter (Continued)
Configure the parameters listed below.
1. IP Local Interface
This parameter represents the IP address of the port to which
the packet is destined.
2. Source and Destination Addresses
The source and destination IP addresses identify the source and
destination IP stations to which the filtering or forwarding
information applies. This value can be a device address, a
subnet, or a network address. The default is 0.0.0.0.

3008M300-004 10-183
CXTool User Guide

3. Source and Destination Netmasks 8. Action

The Source and Destination Netmasks determine the subnet
masks associated with the source and destination IP addresses.
This mark is applied to all outgoing packets prior to attempting
a match against the source and destination address. This is
determined by comparing the mask to the standard network/
device allocation for the address class.
This parameter allows the user to enter the filtering or
forwarding action to packets that are received from the source
address and sent to the destination address.
The options available are as follows:
• discard

4. Protocol • forward
This value determines which protocol(s) are filtered or • priority_low
prioritized between the specified source and destination • priority_high
addresses. The value specified in this parameter is the Protocol
ID field in the IP header. • priority_very_high
The options available are as follows:
• 0: all IP protocols Configuring The Dynamic Host Configuration Protocol (DHCP) Relay
the DHCP service is used obtain an IP address by a given station. When
• 6: TCP Relay CX products receive such a request, they forward it to a DHCP
• 17: UDP server, which assigns a temporary IP address to the requesting
station for a particular session (i.e., until the station is shut
5. Start and End Port Numbers
down). To configure the DHCP Relay service, click on DHCP
The TCP and UDP protocols contain a port field in the packet Relay. The following screen appears:
header. If the port number specified in the filtering / forwarding
definition matches the port number in the packet header, the
specified filtering / forwarding action will be applied.
The Start and End port numbers specify the range of TCP or
UDP ports used by the IP filtering table. For example, if the
Start port number is set to 1025 and the End port number is set
to 1100, a range of 76 ports will be filtered.
6. NBMA Port
This parameter specifies a port from the NBMA configuration
table for which filtering is performed.
7. Direction
This parameter specifies the direction of the data being filtered.

10-184 3008M300-004
 10 CONFIGURING IP

configure this service, click on the IP Helper tab. The following

screen appears:

Figure 10-13: Configuring the DHCP Relay Service

Figure 10-14: Configuring the IP Helper
Enter the address of the DHCP servers. Note that CX products
can act as Relay Agents for up to a maximum of 32 DHCP Configure the parameters listed below.
servers. 1. IP Local Interface
This parameter determines the IP port from which packets will
be forwarded to their destination.
Configuring In general, a broadcast is a data packet that is for multiple hosts
the IP Helper and is not forwarded by a router. The IP Helper uses directed 2. Helper’s IP
broadcasts to forward local and UDP broadcasts to desired This parameter determines the IP Helper’s address to which a
destinations (hosts or a network) within an internetwork. To packet will be forwarded. It could be a directed broadcast
address or a host address.

3008M300-004 10-185
CXTool User Guide

3. UDP Port 10.2.2 Configuring the WAN Link

This parameter determines the UDP ports of protocols to be
forwarded. If this value is ‘0’, only the following protocols will From the IP folder, select the WAN Interface module. Click on
be forwarded: the Add (+) button in the tool bar or select Add New from the
pull-down Edit menu. The following screen appears:
• Trivial File Transfer (port 69)
• Domain Name System (port 53)
• Time Service (port 37)
• NetBios (port 137)
• NetBois Datagram Server (port (138)
• DHCP (port 67 and 68)
4. NBMA Port
This parameter determines the NBMA port that forwards UDP
packets. If this value is ‘0’, all UDP packets are forwarded
from all physical trunks, otherwise the packets are forwarded
to a specific trunk.

Figure 10-15: Configuring the IP WAN Link

Configure the parameters listed below.

1. Name
This parameter allows the user to change the default name.

10-186 3008M300-004

2. NBMA Interface
This parameter enables the NBMA service.
3. WAN Link Type - Frame Relay/ATM
This parameter allows the user to select WAN services at this
port, which could be either Frame Relay/ATM or IP QoS.
4. Peer Address - Auto-select
When enabled, the IP address of the destination unit is
determined automatically, using Inverse ARP. When this
parameter is disabled, the user is required to enter the Peer
Address.
5. WAN Link Type - IP QOS
This parameter allows the user to select a WAN service. When
IP QOS is enabled, Memotec devices separate traffic according
to the service selected.
6. NBMA MTU Size - Auto-select
This parameter represents the maximum IP packet size (in
bytes) that can be sent or received at the IP layer. If an IP
packet exceeds the MTU set for an interface, it will be
fragmented. The value should always be equal to or less than
the sub-layer (Ethernet, Token Ring, or Frame Relay) packet
size. If Auto-select is enabled, the value automatically
corresponds to the sub-layer packet size. This parameter should
only be modified when it is not possible to use the
“Fragmentation Size” parameter.
7. Frame Relay/ATM - Look In
If “Frame Relay/ATM” was selected as the WAN Link Type,
the user is required to configure the Frame Relay or ATM
services by clicking on Add. For configuring Frame Relay, see
Chapter 9 CONFIGURING FRAME RELAY, and for
configuring ATM, see Chapter 8 CONFIGURING ATM.
3008M300-004
10 CONFIGURING IP
8. Frame Relay/ATM - Reference Number
Reference numbers are used by WAN service providers that
offer multiplexing to identify traffic from different sources
travelling over the same virtual circuit (VC). Each reference
number on the WAN circuit must be unique.
This feature is used for Memotec MPE, whereby two or more
WAN links can be multiplexed over one Frame Relay or ATM
VC, and each WAN entry has a unique reference number.
Adding a second WAN link to the same VC is proprietary to
Memotec and therefore not interoperable.
9. Frame Relay/ATM - Fragmentation Size
This parameter determines the maximum frame size supported
on this WAN circuit. In general, the default value is acceptable
for most configurations, except for voice when fragmentation
is required.
10. Remote X.25 DTE
This parameter allows the user to configure the Remote X.25
DTE. For further information, see Chapter 15 CONFIGURING
X.25
11. IP QOS
If “IP QOS” was selected as the WAN Link Type, the user is
required to configure the QOS module by clicking on Add.
(Refer to 10.2.5 Configuring the IP QoS).
10.2.3 Configuring the OSPF Area
By default, the backbone area (0.0.0.0) is already defined by
the system.
10-187
CXTool User Guide

From the IP folder, select the OSPF Area module. Click on the
Add (+) button in the tool bar or select Add New from the Edit
menu. The following screen appears:
Figure 10-16: Configuring the OSPF Port
Configure the parameters listed below.
2. Authentication
This parameter determines whether or not to restrict the use of
this port only to those users who possess the correct “Key” (see
below). Authentication makes information exchange more
secure by requiring routers to include a shared password in all
OSPF packets. Those packets that lack this password are
discarded upon receipt.
3. Import As External Packet
When this parameter is enabled, it indicates that the device in
one area knows the architecture of the different Areas.
4. Stub Area Metric
When this parameter is enabled, it indicates that the device in
one area is aware only of the routers in its Area and is unaware
of the architecture of different Areas. In other words, the Stub
Area routers do not maintain routing information for
destinations outside their area.
Metrics are the key to OSPF's least-cost path routing. They
allow routers to compare the cost of alternative paths to the
same destination. When alternative paths are available, the
least-cost path is preferred, and will receive the most traffic. If
multiple paths offer the same cost, traffic will be split between
them.
This parameter does not need to be configured manually unless
the user wants to alter the amount of traffic travelling over a
certain interface. In that case, reducing the interface's metric
will make it more attractive; increasing the metric will make it
less attractive. Note that the value in this parameter represents
the cost of reaching any outside destination.

1. Area ID
This parameter determines the ID of a network that constitutes
an area.

10-188 3008M300-004

To continue configuring the OSPF module, click on the Virtual
Interface tab. The following screen appears:
Figure 10-17: Configuring the Virtual Interface (OSPF)
Configure the parameters listed below.
1. Neighbor’s ID
This parameter indicates the OSPF router ID of the next OSPF
device through which the backbone area is accessed.
10.2.4 Configuring the IP Port
2. Transmission Delay
This parameter indicates the required interval to transmit a
link-state update packet over this virtual interface.
3008M300-004
10 CONFIGURING IP
3. Retransmission Interval
This parameter determines the required interval between link-
state advertisement retransmissions over this virtual interface.
This value is also used when retransmitting database
description packets and link-state request packets between
neighboring routers.
4. Hello Interval
This parameter determines the required interval between hello
packets sent by this router over the virtual interface. Hello
packets are sent by the router over the virtual interface to
maintain a relationship with the virtual neighbor.
5. Dead Interval
This parameter determines the number of seconds that can
elapse between a router's hello packets before the virtual
neighbor declares the router to be down. In the event of a
bursty network, the user may consider increasing the value of
this parameter. When this is done, it is necessary to update all
the Dead Interval values of all the routers on the user’s
network.
6. Key
This parameter is enabled when the Authentication parameter
is set to Simple Password. The string entered in this parameter
is used for identifying valid users of the OSPF service.
NOTE: A Virtual Interface is required when the Area defined
is more than one hop from the OSPF backbone Area.
From the IP folder, select the Port module. Click on the Add
(+) button in the tool bar or select Add New from the pull-
down Edit menu. The following screen appears:
10-189
CXTool User Guide

3. Virtual MAC Address

This parameter allows the user to assign a MAC address other
than that coded on the card. Note that this is an advanced
function and should be used with caution.
4. Routing Protocol
This parameter determines the type of routing protocol
selected. The options available are as follows: None, RIP, and
OSPF.
5. Maximum Transmission Unit (MTU)
This parameter size determines the maximum number of bytes
that this port can transmit in one IP datagram. Packets that
exceed this size are fragmented. This value should always be
less than or equal to the sub-layer packet size. For local
connections, the sub-layer is Ethernet or Token Ring; for
remote connections, the sub-layer is Frame Relay.
6. Source Routed Network
This parameter determines whether or not this port supports
Source Route Bridging (SR).
When both IP routing and source route bridging are enabled on
the same Memotec device, the configuration for both the
services must be integrated successfully. In a source routing
Figure 10-18: Configuring the IP Port network, end stations specify the end-to-end route for a packet
by including route descriptors within the packet’s header. Thus,
Configure the parameters listed below. when an IP router needs to route a packet across an SR
network, it must behave like an SR end station; it must supply
route descriptors within the packet header before sending it
Configuring 1. IP Address onto the network.
the IP This parameter determines the IP address of the local port.
Interface
When the Source Route parameter is enabled, the IP router
2. Subnet Mask compiles a database that describes paths to all destinations on
the SR network. The router acquires this information from SR
This parameter indicates how much of the device address has
frames it receives off the SR network which are destined for
been allocated to the subnetwork.
other remote locations. When the router needs to send a packet
onto the SR network, it consults the database and applies an SR

10-190 3008M300-004
 10 CONFIGURING IP

header to the packet, including route descriptors to the 11. Link Type
destination The parameter determines the type of IP connection. The
7. Reply RARP option available are as follows:
This parameter determines whether or not this port replies to a • WAN Link (Frame Relay or ATM);
Reverse Address Resolution Protocol (RARP) request.
• Ethernet;
RARP is used to remotely start Memotec devices (e.g., one that
is installed at a branch office). This device contains no • Token Ring;
configuration, but will send RARP requests over any Frame • MLPPP.
Relay DLCIs it can find. When the central office receives this
RARP request, it responds by issuing a temporary IP address 12. If the Link Type is Frame Relay (NBMA interface), select one
for the branch office device. Once this address is assigned, it of the available Frame Relay DLCI’s. Click the left arrow
can be used to remotely configure the branch office device button to shift the selection to the Chosen window.
from the central office.
8. IP Station
This parameter allows the user to configure the hardware CPU
associated with the port.
9. IP TOS Enabled
Type of Service (TOS) routing is an IP concept. It allows
routers to distinguish among alternate routes to a single
destination by rating the speed, bandwidth, and reliability of
each route. When TOS is enabled, the differentiated services
on this port is automatically enabled in CX products.
10. Default Service
This parameter permits the user to select one of eight IP
services on this circuit used to differentiated services.

3008M300-004 10-191
CXTool User Guide

Configuring If “SPOOF” is selected in the Routing Protocol parameter of Protocol services by clicking on the VRRP tab. The following
OSPF the IP Port module, the user is then required to click on “Next.” screen will appears:
Services The following screen appears:

Figure 10-20: Configuring VRRP

Figure 10-19: Configuring the OSPF Port

For details on configuring the OSPF parameters, see section NOTE: VRRP is configurable only when OSPF is selected in
10.2.3 Configuring the OSPF Area. the IP Station and in the Routing Protocol parameter of
the IP Port module. To take advantage of this feature,
configure the IP Port on two devices (e.g., CX800) in a
Configuring If OSPF is selected in the Routing Protocol parameter of the IP LAN environment, together with a Virtual IP Address
VRRP Port (Interface) module, the user configures an Ethernet link that should be the same for both the devices.
Services type, and then configures the Virtual Redundancy Routing
Configure the parameters listed below.

10-192 3008M300-004
 10 CONFIGURING IP

1. Virtual IP Address Configuring If RIP is selected in the Routing Protocol parameter of the IP
This parameter determines the virtual IP address of the Master RIP Services Port (Interface) module, the user can click on the RIP
router and of all Backup routers. If the Master router goes off Configuration tab. The following screen will appear:
line, the Backup router with the next highest priority will
become the Master router, take over this IP address, and all
related routing duties. If the first Master router comes back on
line, after the failure disappears, it can become the Master
router again only if the Preemptive Mode is enabled.
2. Master Router
This parameter determines whether the Master Router is
enabled or disabled.
3. Priority
This parameter determines what priority is assigned to routers
in order to allow the Master router to preempt the Backup
router as soon as it comes back on. The priority of the Master is
always 255, with Backup routers having lower priorities.
4. Pre-emptive Mode Enabled
When this parameter is enabled, the initial Master router can
regain Master status from the Backup router after the failure
disappears. When it is disabled, the initial Master router cannot
regain Master status from the Backup router after the failure
disappears.
5. Advertising Interval
This parameter determines the duration of the intervals (in Figure 10-21: Configuring RIP Services
milliseconds) after which the Master router will broadcast IP
packets on the LAN advertising itself as the Master router. This Configure the parameters listed below:
interval value should be the same for the Master router and
1. Domain (Hex)
each Backup router.
This parameter determines the value inserted into the Routing
Domain field of all RIP packets sent from this interface. This
parameter is for future use.

3008M300-004 10-193
CXTool User Guide

2. Default Metric 5. Outgoing RIP Type

This parameter determines the metric to be used as a default
route in RIP updates. This parameter is for future use
3. Authentication
This parameter determines the type of authentication that is
used at this interface.
Authentication makes information exchange more secure by
requiring routers to include a shared password in all RIP
headers. Packets that lack this password are discarded.
Neighboring routers must therefore use the same password on
linked interfaces. The options available as follows:
• None: no authentication is used on this interface.
• Simple: authentication is used on this interface. Packets that
are sent and received by this interface must contain the
password specified by the Key parameter.
This parameter determines the update procedure that is used on
this interface. The options available are as follows:
• None: no RIP updates are sent. Routing tables must be
configured manually for static routing.
• RIP: the router sends RIP updates that are compliant with the
RIP standard specified in RFC 1058.
• RIP Compatible: the router broadcasts RIP updates as
specified for the RIP-2 standard but uses RFC 1058 route
subsumption rules.
• RIP-2: the router broadcasts RIP updates, as specified for the
RIP-2 standard.
10.2.5 Configuring the IP QoS

4. Incoming RIP Type The user should configure this module if IP traffic is to be
This parameter determines which version of RIP updates will sorted on the basis of an IP QOS priority established for each
be accepted at this interface. Note that RIP and RIP or RIP-2 WAN circuit. For an explanation of IP QOS, see “IP QOS” on
imply reception of multicast packets. page 170. and for an example of how to configure the IP QOS
services, see “Configuring Traffic Sorting” on page 174..
The user should set this parameter to correspond to the RIP
version supported by surrounding routers. If the user is unsure
of the version used, the default setting (RIP or RIP-2) is the
best choice. The options available are as follows:
• RIP: this interface accepts RIP packets only
• RIP-2: this interface accepts RIP2 packets only
• RIP or RIP-2: This interface accepts both RIP and RIP-2
packets.

10-194 3008M300-004

From the IP folder, select the QOS module. Click on the Add
(+) button in the tool bar or select Add New from the pull-
down Edit menu. The following screen appears:
Figure 10-22: Configuring the IP QOS Service
Configure the parameters listed below.
1. Service Provided
This parameter permits the user to select one of eight IP
services on this circuit.
2. WAN Link - Look in
This parameter allows the user to configure the WAN service.
The options available are as follows: ATM or Frame Relay.
3008M300-004
10 CONFIGURING IP
3. WAN Link - Reference Number
Reference numbers are used by WAN service providers that
offer multiplexing to identify traffic from different sources
travelling over the same virtual circuit (VC). Each reference
number on the WAN circuit must be unique.
This feature is used when MPE is enabled on the Frame Relay
DLCI, whereby two or more WAN links can be multiplexed
over one Frame Relay or ATM VC, and each WAN entry has a
unique reference number. Adding a second WAN link to the
same VC is proprietary to Memotec and therefore not
interoperable.
4. WAN Link - Fragmentation Size
This parameter determines the maximum frame size supported
on this WAN circuit. In general, the default value is acceptable
for most configurations, since frame size is a negotiated value.
However, if you want to take advantage of WAN that supports
large data packets, increase the fragmentation size accordingly.
For voice applications, it is recommended that fragmentation
be performed in the DLCI configuration and not here.
10-195
CXTool User Guide

10.2.6 Configuring the IP Tunnel 2. Tunnel Name

This parameter identifies the specific IP tunnel name in text
From the IP folder, select the IP Tunnel module. Click on the form. This alias is used by the service user to open a
Add (+) button in the tool bar or select Add New from the pull- connection to the remote IP address. When configuring
down Edit menu. The following screen appears: services such as voice or Frame Relay to run through this
tunnel, this name will be used.
3. Destination IP address
This parameter specifies the IP address of the destination
station where the tunnel terminates.
4. Add Sequence Number
This parameter gives the user the option to configure a tunnel
interface to drop datagrams that arrive out of order. Enabling
this function adds a sequence number to the outgoing data
stream. If an incoming datagram has a sequence number, then
sequence checking is automatically enabled at this end point.
Setting this function to Automatic enables sequence number
generation based on the application. In other words, only those
applications that require sequencing will use this option.

Figure 10-23: Configuring the IP Tunnel

Configure the parameters listed below.

1. IP station
This parameter is associated with a hardware CPU. For the
CX800, CX900e, and CX950, there is only one CPU. The
CX1000e can have multiple CPU’s and, therefore, multiple IP
stations.

10-196 3008M300-004
 11 CONFIGURING ISDN AND QSIG

This chapter describes how to configure the Integrated Services

Digital Network (ISDN) and Q-Interface Signaling Protocol
(QSIG) services on a Memotec CX product using CXTool.
Although users of this guide should have a fundamental
understanding of ISDN and QSIG, it may be helpful to review
some basics, covered in Chapter 26 INTRODUCING ISDN,
before advancing to the procedures.

This chapter begins with an overview of the implementation of

ISDN and QSIG in the CX product family.

3008M300-004 11-197
CXTool User Guide

11.1 Memotec’s CX Products and the ISDN
Environment
Memotec provides its customers with BRI and PRI modules.
The BRI supports 2B+D channels, and 1B+D.
In North America, the T1 PRI supports 23B+D channels and in
Europe, the E1 PRI supports 30B+D channels (E1).
Both interfaces support national, international, and CCITT
ISDN address schemes, together with the Service Profile
Identifier (SPID) for North American ISDN connections.
Incoming call filtering, based on address or sub-address, or
both, provide security and enhanced call routing. Both modules
provide bandwidth on demand with Multi-Link Point-to-Point
Protocol (MLPPP).
The implementation of BRI-QSIG and PRI-QSIG call handling
enables the user to facilitate communication between two or
more PINXs. This service is sometimes referred to as “routed
QSIG.”
The next section gives a brief overview of typical ISDN
services that are possible with Memotec devices, together with
a list of parameters that the user is required to configure for
those services.
11.1.1 Typical ISDN Configuration
Both, the local and remote sides have CX950. While the local
side is configured with a Voice Analog FXS (for voice), BRI S/
T, and V.35 (for Frame Relay), the remote side is configured
with a Voice Analog FXO, BRI S/T, and V.35.
As illustrated in Figure 11-1, both the CX950s are configured
such that when the Frame Relay link goes down, data packets
are automatically sent across the ISDN connection.
Let us assume that the caller at extension 2002 would like to
reach the caller at extension 5003. In order for this call to go
across a Frame Relay network, the user is required to configure
the parameters mentioned below on CX950 (A).
• Voice Station
CPU on CX950
• Voice Channel
Analog Voice FXS 3.1
Home Extension: 400
Local Extension: 400
Signaling Type: Analog FXS Loop Start
• DSP Channel
Analog Voice FXS 3.1
compression: acelpII
• Dialing Plan: (digits dialed: 418-249-5003)
Dial Pattern: 4XX
Remote Extension: --- --- +++
Called Number: --- --- >

Configuring Figure 11-2 illustrates a case of configuring Frame Relay on an

• ISDN Port:
ISDN for ISDN-BRI interface for backup of voice over a Frame Relay BRI S/T 6.1
Backup network. Switch Type: bri_NET3
Services Emulation: User

11-198 3008M300-004
 11 CONFIGURING ISDN AND QSIG

• WAN Trunk
Local Site Remote Site
Frame Relay station (CPU)
BRI S/T FXS V.35 BRI S/T FX0 V.35
in slot 6 in slot 3 in slot 2 in slot 6 in slot 3 in slot 2 Frame Relay Port: V.35H 2.1
Link: ISDN Service Point
Dial Port: ISDN Called Number - 515200
CX950
CX950 (B) Frame Relay: DLCI - 10
(A)
• Voice Pattern: xxx (the compression parameters are configured
515100 Frame 515200
automatically). This call will be routed across the network
Relay
DLCI = 10
based upon the pattern used in this parameter, which should
match that in the Remote Extension parameter
Ext. 2002 • Digit: Default Configuration: DTMF Standard; Transmit/
Generation: DTMF; Receive/Detection: DTMF
ISDN
(back up
network) • Call Progress Tones: Default Configuration: USA

NOTE: For the purpose of this example, we shall assume that

CX950(B) is configured to receive Frame Relay and
ISDN traffic and to forward it to the PBX.

P
B
X
Memotec As explained earlier, QSIG is a signaling standard uses by
Ext. 5005

Devices and PBXs in a corporate environment. As illustrated in Figure 11-2

QSIG and Figure 11-3, Memotec devices facilitate this
Ext. 5002
communication by way of receiving QSIG information from
one PBX, processing the information, and then sending it
Ext. 5004 transparently to another PBX over a relatively more
Ext. 5003
economical network, e.g., Frame Relay.
Figure 11-1: ISDN-Frame Relay Backup
In Figure 11-2 both, the local and remote sides have a
• BRI Channels CX1000e. They are each configured with two cards: Digital
D: ISDN
B1: ISDN
B2: ISDN

3008M300-004 11-199
CXTool User Guide

Voice I/O (for T1/E1 and Frame Relay services) and DVC (for • Voice Channel
voice compression).. Interface Type: E1
Channels Available: 1.1.1 to 1.1.15 & 1.1.17 to 1.1.31
Local Site Remote Site Channel 16: QSIG signaling
Digital Voice I/O DVCB Digital Voice I/O
DVCB
in slot 2 & 4
in slot 1 in slot 2 & 4 in slot 1 Home Extension: 400
Local Extension: 400
• DSP Channel
CX1000e CX1000e Channels Available: 2.1 - 2.15; 4.1 - 4.15
(A) (C) Compression: acelpII
Hardware Card Type: digital
Frame
DLCI = 40
Relay • Dialing Plan: (digits dialed: 618-239-5003)
PRI_QSIG PRI_QSIG
Dial Pattern: 6XX
Remote Extension: --- --- +++
Called Number: --- --- >
P P
I Fax I
N N
X X
• ISDN-Port
Ext. 5005 Ext. 5005
Ext. 5005
T1/E1 1.1
Interface Type: CEPT PRI/E1
Ext. 4001
Ext. 5002 Switch Type: pri_QSIG

Ext. 5004 • WAN Trunk

Ext. 4002 Ext. 5003

Frame Relay Station (CPU))

Figure 11-2: Memotec Devices and QSIG
Frame Relay Port: V.35H 1.4
Let us assume that both Memotec devices (CX1000e) are Link: Sync Driver 1.4
configured to receive and send QSIG and Frame Relay Frame Relay: DLCI - 40
protocols. Let us also assume that the user at telephone • Voice Pattern: xxx (the compression parameters are configured
extension 4001 is calling extension 5003. In order for this call automatically). This call will be routed across the network
to reach its destination, CX1000e (A) needs to be configured in
the manner illustrated below.
• voice station
CPU on CX1000e

11-200 3008M300-004
 11 CONFIGURING ISDN AND QSIG

based upon the pattern used in this parameter, which should

match that in the Remote Extension parameter Local Site Remote Site

DDVC BRI S/T V.35 DDVC BRI S/T V.35

• Digit: Default Configuration: DTMF Standard; Transmit/ in slot 5 in slot 3 in slot 2 in slot 7 in slot 5 in slot 2
Generation: DTMF; Receive/Detection: DTMF
• Call Progress Tones: Default Configuration: USA CX950 CX950
(A) (B)
• CCS: Default Configuration: Transparent Mode

FRAME
NOTE: Currently, Memotec devices support QSIG services DLCI=100
RELAY
only on the E1 interface. For the purpose of this
example, we shall assume that CX1000e (C)) is
configured correctly.

P P
B B
Configuring BRI services may be configured for ISDN or non-ISDN X X

BRI Services applications. Figure 11-3 illustrates a case of configuring voice Ext. 5005 Ext. 5005

Only on a BRI interface for transport across a Frame Relay network.

Note that since this is a point to point configuration, voice
Ext. 5002
traffic is carried transparently from one Memotec device to
another Memotec device.
Ext. 5004
Ext. 5003 Ext. 1001 Ext. 1002

Both, the local and remote sides have a CX950, each of which
has a BRI S/T card, a Frame Relay (V.35) card, and a DDVC Figure 11-3: Configuring BRI Services
card for encoding voice.
• Voice Channel
Let us assume that the caller at extension 5004 would like to Interface Type: BRI_DVC 3.1
reach the caller at extension 1002. In order for this call to go Channels available: 3.1.1 - 3.1.2
across a Frame Relay network, the user is required to configure Home Extension: 400
CX950 (A) in the manner illustrated below.
• DSP Channel
• Voice Station DDVC 5.1, 5.2
CPU on CX950 Compression: acelpII
Hardware Card Type: digital

3008M300-004 11-201
CXTool User Guide

• Dialing Plan: (digits dialed: 618-249-1002) 11.1.2 Summary of ISDN features supported on CX Products
Dial Pattern: 6XX
Remote Extension: --- --- +++
Interfaces BRI
Called Number: --- --- >
• RJ-45 female, ISO 8877 compliant
• Interface Type: BRI S/T 3.1
• BRI Channels
D: HDLC
B1: Voice
B2: Voice
• WAN Trunk
Frame Relay Station (CPU))
Frame Relay Port: V.35H 2.1
Link: Sync Driver 2.1
Frame Relay: DLCI - 100
• Voice Pattern: xxx (the compression parameters are configured
automatically). This call will be routed across the network
based upon the pattern used in this parameter, which should
match that in the Remote Extension parameter
• Digit: Default Configuration: DTMF Standard; Transmit/
Generation: DTMF; Receive/Detection: DTMF
• Call Progress Tones: Default Configuration: USA
• CCS: Default Configuration: Transparent Mode

NOTE: For the purpose of this example, we shall assume that

CX950(B) is configured correctly.

The next section gives summary of the ISDN interfaces,

protocols, and operational features supported by CX products.

11-202 3008M300-004
 11 CONFIGURING ISDN AND QSIG

• U-interface ANSI T1.601-1992 compliant (LAPD))

- Layer 3: Q.931
• S/T interface T1.605 CCITT 1.430 and ETSI ETS 300012
compliant • Euro ISDN support
- Layer 1: ESTI ETS 300012
PRI (T1) - Layer 2: ESTI ETS 300125
• physical interface: RJ-48C - Layer 3: ESTI ETS 300102-1 AND 300102-2

• framing: ESF • QSIG

- ETS 300172
• line code: B8ZS - ECMA - 148 (ETS 300173)
- ECMA - 164 (ETS 300238)
• soft line buildout: long haul (0, 7.5, 15, and 22.5 dB); short haul - QSIG GF, ECMA - 165 (ETS 300239)
(0 to 660) - ECMA 212
• DS0 assignment: user selectable
• clocking options: loop timing, local timing, or through timing Switch • Northern Telecom DMS-100 (BRI/PRI)
(through timing is not available with CX1000e) Support
• AT&T 4ESS (PRI) and 5ESS (BRI/PRI)
PRI (E1) • National ISDN-1 (BRI) and ISDN-2 (PRI)
• physical interface: RJ-48C and dual BNC coaxial connectors • NET3 compliant [Euro ISDN] (BRI)
75 ohms (CX1000e only)
• NET5 compliant [Euro ISDN] (PRI)
• framing: G.704
• line code: HDB3
BRI/PRI • Unrestricted digital 64 kbps (HDLC data)
• channel assignment: user selectable Capabilities
• Restricted digital 56 kbps (HDLC data)
• clocking options: loop timing, local timing, or through timing
• 3.1 kHz audio (PCM A-Law and µ-law). Voice and fax Group 3
(slave)
(up to 9.6 kpbs) payload types are supported.

Protocols • National ISDN-1 support

Emulation BRI (North America)
- Layer 1: T1.601
- Layer 2: Q.921 (Link Access Protocol on the D channel • User side only

BRI (Europe)

3008M300-004 11-203
CXTool User Guide

• User and Network side (Euro-ISDN) 11.2 Configuring ISDN with CXTool
• Slave and Master (QSIG)
This section provides configuration procedures for ISDN.
PRI (North America) From the navigation module, open the ISDN folder, which
contains all the parameters associated with the ISDN, including
• User and Network side the port and ISDN data service point.
BRI (Europe)
11.2.1 Configuring the ISDN Port
• User and Network side (Euro-ISDN)
• Slave and Master (QSIG) From the ISDN folder, select the ISDN Port module. Click on
the Add (+) button in the tool bar or select Add New from the
pull-down Edit menu. Click on the Basic tab, and the following
Time Slots BRI (North America and Europe) screen will appear:

• Two B channels (64 kbps each)

Basic Configure the parameters as listed below.
• One D channel (64 kbps)
1. Port
PRI (North America) The user chooses one of four types of interface to configure.
• 23 B channels (64 kbps each) • BRI (S/T)
• One D channel (64 kbps) • BRI (U)
• ANSI PRI (TI)
PRI (Europe)
• CEPT PRI (E1)
• 30 B channels (64 kbps each)
If an ISDN port is configured then the slot and port will appear
• One D channel--Time Slot 16--(64 kbps) in the Port field. If an ISDN port is not configured, the user can
add one by clicking on the Add tab. Note that when an
The next section focuses primarily on how to configure the incorrect Interface Type is selected, the port field remains
ISDN services on Memotec devices with CXTool. It adheres to empty.
the sequence in CXTool and provides a description of all the
parameters the user will encounter during configuration. As an example, assume that the user selected a BRI S/T
interface and would like to add a BRI port. When the user
clicks on the Add tab, the screen shown in Figure 11-5 appears.
Proceed by configuring the parameters as listed below.

11-204 3008M300-004
 11 CONFIGURING ISDN AND QSIG

Figure 11-4: Configuring the ISDN Port for BRI Services

Figure 11-5 Configuring the BRI Port

1. Hardware Port
Configure a port for ISDN, BRI (S/T), or BRI (U).
2. PCM Voice Coding
The options available are as follows:

3008M300-004 11-205
CXTool User Guide

• mu-Law (for North America)

• A-Law (for Europe)
3. Timer 1 (seconds)
This parameter indicates the maximum duration allocated for
the ISDN link synchronization at the NT interface.
4. Timer 3 (seconds)
This parameter indicate the maximum duration allocated for
the ISDN link synchronization at the TE interface.

NOTE: It is recommended that the user not modify the Timer 1

and Timer 3 parameters for the proper functioning of
the ISDN link synchronization.

5. User Side Power Source 1 Detection

This parameter indicates whether or not the driver has to wait
for the detection of the Power Source 1 before generating an
activation request at system power-up.
6. Hardware Port
This parameter allows the user to configure a BRI port. When
the user clicks on the Add tab, the following screen appears: Figure 11-6: Configuring the Hardware Port (BRI)

Note that the name of the Memotec device on which the BRI
port is defined will appear in the Device Type parameter. In the
sample screen above, the device is CX950. Here the user adds
the required cards.

11-206 3008M300-004

Following the configuration of the BRI Port, the user should
configure the Channels in the BRI folder. When the user clicks on
the (+) button (from the Channel sub-module), the following screen
appears:
Figure 11-7: Configuring BRI Channels
The D channel is used for carrying signaling information for
the ISDN protocol or for carrying data in High Level Data Link
Control (HDLC) format.
3008M300-004
11 CONFIGURING ISDN AND QSIG
When the D channel carries the ISDN protocol, the B channels
can carry voice or data traffic, controlled by the ISDN protocol
(ISDN) or only voice (voice) or data (HDLC).
When the D channel carries data, the B channels can carry
voice or data but not ISDN.
The channel configurations allow for the following
combinations:
1. D: ISDN; B1: ISDN; B2: Voice or HDLC or ISDN
2. D: HDLC; B1: Voice or HDLC; B2: Voice or HDLC
For an explanation of the different channels see 26.1.2 ISDN
Features and 26.1.3 Standardizing QSIG.
Lets take another example. Let us assume the user would like
to configure the PRI services. If a PRI port has already been
configured then the slot and port number will appear in the Port
field. If not, the user can add one by clicking on the Add tab.
Note that the Port field will remain empty if the Interface Type
is configured incorrectly.
11-207
CXTool User Guide

For the purpose of illustration, lets assume the user selected an

ANSI PRI (T1) and would like to add a PRI port. When the
user clicks on the Add tab, the following screen appears:

Figure 11-9: Configuring the T1/E1 Port for PRI Services

For complete details on configuring a T1/E1 port, see

Chapter 12 CONFIGURING T1/E1, section entitled:
Figure 11-8: Configuring the ISDN Port for PRI Services
12.2.1 Configuring the T1/E1 Port.
Click on the Add tab to configure a T1/E1 port. The following
In the ISDN Port module of the ISDN folder (Refer to
screen appears:
Figure 11-8.), configure the parameters as listed below.
1. Switch Type.
This parameter indicates the type of the protocol supported by
the switch providing the ISDN access. Depending upon the

11-208 3008M300-004
 11 CONFIGURING ISDN AND QSIG

type of interface selected, the options available for Switch Type • user: ISDN emulates the user side; QSIG - emulates the slave
will be from among the following: side
• bri_5ESS • network: ISDN emulates the network side; QSIG - emulates the
master side
• bri_DMS100
4. Terminal Endpoint Identifiers (TEI).
• bri_NET3
This parameter indicates the TEI assignment mode used by
• bri_NI1 Data Service Point (see below). The options available are as
follows:
• bri_QSIG
• nonAutomatic: TEIs are not automatically assigned
• pri_4ESS
• automatic: TEIs are automatically assigned
• pri_5ESS
5. Data Calling Party ID
• pri_DMS100 This parameter indicates the calling party number (i.e., the
• pri_NI2 number of person placing the call).

• pri_NET5 The remaining parameters in the ISDN Port module are

• pri QSIG
2. Information Rate.
This parameter indicates the speed of the B channel connected
to the Digital Subscriber Line (DSL) when a call is initiated on
that DSL. There are two speed options available for this
channel: 56 kbps and 64 kbps.
3. Emulation Mode.
This parameter indicates the emulation type. It is used
primarily for data services (see section on “Data Service
Point.” The options are as follows:
advanced functions. It is recommended that they not be
modified. A description of the advanced parameters is provided
below primarily for the purpose of information.
LAPD - 1. Standard
Advanced
This parameter indicates the manner in which TEI assignments
are handled. The three standards available are: CCITT, VN3,
and ETSI.
2. Link Establish Mode
This parameter indicates if the Data Service Point initiates the
link (active) between a DTE a DCE or if it waits for the other
side to initiate it (passive).

3008M300-004 11-209
CXTool User Guide
3. Always Connect Sub-Layer
This parameter indicates the manner in which the Data Service
Point handles connections with other sub-layers. The two
options available are: disabled and enabled.
4. MAC Window Size
This parameter indicates the maximum number of frames that
can be outstanding at any given time to a sub-layer. A frame is
considered to be outstanding until its receipt is acknowledged.
5. Connection Timer
This parameter indicates the maximum amount of time that the
LAPB/D layer waits for a sub-layer to respond to a connection
request. If the timer expires before a response is received, the
connection is retried.
6. Max Data Link Connections
This parameter indicates the maximum number of data link
connections supported at a Data Service Point.
7. Upper Threshold
This parameter is used for notifying that a data link connection
on this Data Service Point is congested. When the number of
frames in the queue for this data link connection exceeds the
threshold value, the congestion timer is started and link status
is set to congested. If congestion has not cleared before this
timer expires, the link is dropped. Each data link connection
through this Data Service Point maintains its own queue.
8. Lower Threshold
The parameter is used for notifying that a data link connection
on this MAC Data Service Point is no longer congested. When
the number of frames in the queue for this data link connection
reaches this value, the congestion timer is dropped and link
status is set to not congested.
11-210
9. Congestion Timer
This parameter indicates the maximum amount of time that the
LAPB/D waits for the link to become uncongested before it
terminates the link.The timer starts when the number of frames
queued for a data link connection associated with this Data
Service Point reach the congestion threshold. The timer stops
when the number of frames queued for data link connection
reach the congestion minimum. If the timer expires, the data
link connection is terminated.
10. Max Frame Size (N201)
This parameter indicates the maximum size (i.e., number of
bytes) that can pass through a Data Service Point in either
direction (to the upper or the lower layer).
11. Max. Retransmission (N200)
This parameter indicates the maximum number of attempts
made to successfully transfer a command frame after the
acknowledgement timer expires.
12. Response Wait Timer (T200)
This parameter indicates how long this Data Service Point
waits for a response to a command frame before initiating error
recovery.
13. Max Idle Timer (T203)
This parameter indicates the maximum time a Data Service
Point will allow the link to remain idle (i.e., no frames are
exchanged) before sending an RR poll to the other side.
14. Window Size (K)
This parameter indicates the maximum number of information
frames that can remain outstanding. A Frame is considered to
be outstanding until the other side acknowledges its receipt.
3008M300-004

Layer 3 1. Management Indication Timer
Advanced This parameter indicates the interval in seconds that the ISDN
software layer will wait for the completion of terminal
initialization. If the information and the Service Profile
IDentifier (SPID) messages fail during this interval, they will
be permitted only one retransmission.
2. Setup Ack Timer (T302)
This parameter indicates the intervals in seconds that the ISDN
software layer will wait for an information message when a
Setup Acknowledge message is sent.
3. Setup Timer (T303)
This parameter indicates the intervals in seconds that the ISDN
software layer will wait for an Alerting, Connect, Setup
Acknowledge, Call Proceeding, or Release Complete message
after sending a Setup message.
4. Information Timer (T304)
This parameter indicates the intervals in seconds that the ISDN
software layer will wait for a Call Proceeding, Alerting,
Connect, or Disconnect message after sending an Information
message.
5. Disconnect Timer (T305)
This parameter indicates the intervals in seconds that the ISDN
software layer will wait for a Release or Disconnect message
after sending a Disconnect message.
6. Disconnect with Progress Indication Timer (T306)
This parameter indicates the intervals in seconds that the ISDN
software layer will wait for a Release or Disconnect message
after sending a Disconnect message.
3008M300-004
11 CONFIGURING ISDN AND QSIG
7. Release Timer (T308)
This parameter indicates the intervals in seconds that the ISDN
software layer will wait for a Release or Release Complete
message after sending a Release message.
8. Reconnect Timer (T309)
This parameter indicates the intervals in seconds that the ISDN
software layer will wait for the data link to reconnect after it is
disconnected while in a stable state. Calls in stable states are
not lost.
9. Call Processing Timer (T310)
This parameter indicates the intervals in seconds that the ISDN
software layer will wait for an Alerting, Connect, Disconnect
or Progress message after receiving a Call Proceeding
message.
10. Enter a Broadcast Setup Timer (T312) value.
This parameter indicates the intervals in seconds that the ISDN
software layer will wait after a setup message is sent or resent
on the Broadcast Data Link, while in Call Present, Call Abort,
or the like states.
11. Connect Timer (T313)
This parameter indicates the intervals in seconds that the ISDN
software layer will wait for a Connect Acknowledge message
after sending a Connect message.
12. Resume Timer (T318)
This parameter indicates the intervals in seconds that the ISDN
software layer will wait for a Resume Acknowledge or
Resumer Reject message after sending a Resume message.
13. Suspend Timer (T319)
This parameter indicates the intervals in seconds that the ISDN
software layer will wait for a Suspend Acknowledge or
Suspend Reject message after sending a Suspend message.
11-211
CXTool User Guide
14. Status Enquiry Timer (T322)
This parameter indicates the intervals in seconds that the ISDN
software layer will wait for a Status, Disconnect, Release or
Release Complete message after sending a Status Enquiry
message.
15. B Channel: Maintenance
This parameter is used with the ISDN PRI T1 (ANSI)
interface. The options available are as follows:
• disabled: the B channel maintenance is disabled
• enabled: the B channel maintenance is enabled
16. BRI- QSIG:Call Reference Length.
This parameter is essentially for BRI-QSIG operation. The
options available are as follows:
• one-Byte: use a Call Reference of 1 byte
• two_Byte: use a Call Reference of 2 bytes
NOTE: This parameter should not be modified without the
supervision of Kontron personnel.
17. BRI-QSIG: Interface Type.
This parameter is essentially for BRI-QSIG operation that are
used in the Call Establishment message and for validation. The
Interface Type may be a BRI or a PRI.
18. Force LAPD Establishment
This parameter indicates the state of the LAPD link
establishment procedure at the time the physical link is up. The
options available are as follows:
11-212
• disabled: LAPD link establishment procedure is activated per
call request;
• enabled: LAPD link establishment procedure is activated at the
time the physical link is up.
B-Channel 1. Tx Queue Size
Advanced
This parameter indicates the maximum number of frames that
the port associated with this SAP can hold before transmitting
them. When this value is 255, the system manages the number
of buffers devoted to different kinds of traffic. When this value
is less than 255, the system compares the value with its own
and uses the smaller value.
2. Max. Frame Size
This parameter indicates the maximum frame size (received
and transmitted) supported by the port associated with Data
Service Point.
3. Preamble Length
This parameter indicates the minimum number of flags or SYN
pairs that are inserted between frames by the port associated
with a Data Service Point.
The options available for HDLC frames are as follows:
• a value of zero causes flag sharing between frames
• a value of one means no flag sharing and zero flags inserted
between frames
• a value of two means no flag sharing and one flag inserted
between frames
• a value of three means no flag sharing and two flags inserted
between frames and so on
3008M300-004

4. Bandwidth Threshold
This parameter indicates the minimum bandwidth threshold. If
the actual port speed drops below this value, the frames are
discarded. The value entered must be a multiple of 1 kbps.
5. Statistics Timer
This parameter indicates the frequency with which the
performance statistics are updated. If the value is set to zero,
the performance statistics are not measured.
6. Idle Link Condition
This parameter indicates the idle line condition supported by
the port associated with the connection. The idle line condition
specifies how the line is kept up when no data is being
exchanged. The value in this parameter must match the
network value. The options available are as follows:
• flags: Flags (7E) are sent when the line is idle
• marks: Marks (FF) are sent when the line is idle
• as400: use this option for all IBM equipment
7. Encoding Method
This parameter indicates the data formatting and encoding
method used by the port associated with a Data Service Point.
The value in this parameter must match the network value. The
options available are as follows:
3008M300-004
11 CONFIGURING ISDN AND QSIG
• nrz: NRZ (Locked for ISDN ‘D’ channel; ISDN ‘B’ channel
can use only this value or NRZI-Space value)
• nrzi-mark: NRZI-Mark
• nrzi-space: NRZI-Space (ISDN ‘B’ channel can use only this
value or NRZ value)
8. Port Status Trap
This parameter indicates the status of the port. If this parameter
is enabled (i.e., the box is checked) the Data Service Point
produces port status traps. If it is disabled, then the traps are
not produced.
D-Channel For an explanation of the parameters in this panel, refer to the
Advanced B-Channel Advanced section, steps 1 through 5 and step 8,
above.
11.2.2 Configure the ISDN Data Service Point
The ISDN Data Service Point is used for data services only.
This module allows the user to determine the type of action that
should be taken on incoming and outgoing data calls to and
from specific numbers. It also allows them to determine the
ISDN port that will be used for outgoing and incoming data
calls. The configuration in this module can be accessed by
MLPPP and Frame Relay.
From the ISDN folder, select the ISDN Data Service Point
module. Click on the Add (+) button in the tool bar or select
Add New from the pull-down Edit menu. The following screen
appears.
11-213
CXTool User Guide

2. Select a Call Security option.

This parameter indicates the type of action initiated on
outgoing and incoming calls. The options available are as
follows:
• originate: call can be originated through this Data Service Point
• answer: calls can be answered through this Data Service Point
• originate_answer: calls can be originated and answered through
this Data Service Point
3. In the “Attach Dialup DSL Link (ISDN Port) parameter, either
configure the ISDN Port (if not already configured) by clicking
on the Add tab or transfer the appropriate port from the
Available column to the Choose column in order to include this
port in the configuration.
4. Configure the Filter Action (Called Party On and Calling Party
On) parameters according to one of the following criterion that
defines the basis on which a call is accepted:
disable
number
subaddress
number and subaddress
For a brief description of the above parameters, see below.
Figure 11-10: Configuring the ISDN Data Service Point

Configure the parameters as listed below.

1. Enter the Data Service Point Name.
This parameter indicates the textual name uniquely identifying
this Data Service Point, which is simply a connection point for
the next layer.

11-214 3008M300-004
 11 CONFIGURING ISDN AND QSIG

If the Global Directory was not configured, no numbers will • Number

appear in the Filter Action parameters. In that case clicking on This number is assigned to a BRI/PRI port by the network.
the Add tab. The following screen will appear:
• in the “Numbering Plan” parameter, enter the local extension’s
digits and called number’s digits. The options available include
the following:
transparent (used only for voice applications)
unknown
ISDN
national
private
• in the “Number Type” parameter, choose the number type from
among the following options:
transparent (used only for voice applications)
unknown: this option is used when the user or the network
has no knowledge of the type of number, e.g.,
international number
international: prefix or escape digits should not be included
national: prefix or escape digits should not be included
network_specific: this option is used to indicate that the
administration/service number is specific to the
serving network, e.g., number to access an operator
subscriber: prefix or escape digits should not be included
• in the “Sub-Address” parameter, enter the ISDN address.

Figure 11-11: Configuring the Global Directory

• in the “Sub-Address Type” parameter indicates the ISDN sub-
address of the called party. The options available are as follows:
transparent (used only for voice applications)
Configuring Configure the parameters in the Global Directory beginning nsap: this is a Network Access Service Point (X.21/iso
the Global with Index 1 as shown below. Note that the fields at the bottom 8.348 AD2) address
Directory of the dialog box (Figure 11-2) are display only. user_specified.

3008M300-004 11-215
CXTool User Guide

• in the “Sub-Address Info” parameter, enter the ISDN stored at the switch. This information is used by the switch at
subaddress information. The options available are as follows: the time of sending “setup” messages.
transparent (used only for voice applications)
even_bn_or_address_signals: indicates that the sub-
address is even;
odd_nb_or_address_signal: indicates that the sub-address
is odd.
• in the “Presentation Indicator” parameter, select from among
the following options: transparent: the calling information is
sent transparently;
transparent (used only for voice applications)
allowed: presentation allowed
restricted: presentation restricted
not_available: number not available due to interworking
This parameter is used only for the calling party number. It
includes features
like displaying or restricting calling party information (e.g.,
telephone
number).
• in the “Screening Indicator” parameter (used only for the
calling party number), select from among the following options:
not_screened: user-provided, not screened
passed: user-provided, verified and passed
failed: user-provided
network: network provided
• The Service Provider Identifier (SPID) parameter is for DMS-
100, NI-1, NI-2, and optional for 5ESS switches supporting
BRI. It is 20-digit long and provided to a customer by the
telephone company for the purpose of connecting one or many
ISDN devices to a telephone line. When a customer orders
services or features, they are programmed into a Service Profile

11-216 3008M300-004
 12 CONFIGURING T1/E1

This chapter describes how to configure T1 and E1 services on

a Memotec CX product using CXTool.

Although users of this guide should have a fundamental

understanding of digital transmission, it may be helpful to
review Chapter 27 INTRODUCTING T1 AND E1, before using
these procedures.

3008M300-004 12-217
CXTool User Guide
12.1 Memotec’s CX Products and the T1/E1
Environment
This section describes the implications of channelized ports
and unchannelized ports. It also explains the restrictions that
apply to the selection of the slot into which the digital interface
module (DIM) is installed. Then, as an example, a T1/E1
interface is configured for voice traffic.
12.1.1 Channelized and Unchannelized Ports
In a transport network, the data transmissions of users are
assembled in hierarchies for transmission; the data signals of
one source are grouped with the data signals of other sources.
The grouped data signals are often grouped repeatedly forming
signals that occupy very large transmission bandwidth. When
the data signal nears its destination, it is ungrouped repeatedly,
until the original data signal emerges for delivery to its
destination.
Many of the traditional ways of grouping data to form larger
groups, then grouping again to form even larger groups, is
derived from the original methods of the telephone networks.
Their smallest data channel operates at 64 kbps and is known
as a DS0 channel. Twenty-four DS0 channels are grouped to
form a T1 channel. Similarly, in E1, 32 DS0 channels are
grouped to form an E1 channel.
The bandwidth of a T1 channel or an E1 channel can be
configured in many ways. However, in the particular case when
the data at the interface between the user and the transport
network is a group of 64 kbps channels, then the data at the
interface is said to be channelized.
12-218
Of course, it is very important that the parties on both sides of
the user/transport network interface agree on the form in which
the data will be transported. And since a certain number of the
transport networks are operated by the PSTN, the user/
transport network interface is often operated as channelized.
But there are many service providers and many exceptions. It is
valuable to be certain of the requirements of the interface
before configuration of the T1/E1 port begins.
Memotec’s Digital Interface Module (DIM) supports voice and
data transmission at T1 and E1 rates. The T1/E1 port can be
configured as channelized or unchannelized, and both T1 and
E1 support ISDN signaling. The available options are the
following.
T1/E1 Port CAS - Channel Associated Signaling
and
Channelized When the T1 port is configured for channelized data and the
Data signaling type is CAS, then up to 24 channels can be
configured for voice and/or data traffic.
When the E1 port is configured for channelized data and the
signaling type is CAS, then up to 30 channels can be
configured for voice and/or data traffic; channel 16 is reserved
for bit-oriented signaling and is not a data channel.
CCS - Common Channel Signaling
When the T1 port is configured for channelized data and the
signaling type is CCS, then up to 23 channels can be
configured for voice and/or data traffic. Channel 24 is reserved
for message oriented signaling and is a data channel.
When the E1 port is configured for channelized data and the
signaling type is CCS, then up to 30 channels can be
3008M300-004
 12 CONFIGURING T1/E1

configured for voice and/or data traffic. Channel 16 is reserved maximum of 32 data channels minus the number of ISDN ports
for message oriented signaling and is a data channel. for each system CPU.

Note that when a channel is configured for ISDN, the channel
is able to handle voice and data dynamically, except for the
signaling channels (16 for E1 and 24 for T1), which handle
data only.
T1/E1 Port When the T1/E1 port is configured for unchannelized data,
and each DIM can be configured as multiple voice channels along
Unchanneliz with one data bundle;
ed Data
• in the case of T1, 24 voice channels and a single data bundle
• in the case of E1, 31 voice channels and a single data bundle
For unchannelized data, there is only a single data bundle per
DIM. And, if used for ISDN the DIM is restricted to voice only
with no data channel.
Full details of the restrictions concerning suitable slots for the
DIM and configuration of the DIM are given in the hardware
manuals:
• CX950/960 Hardware Reference Manual (Part Number
3021M100-00x)
• CX2000 Hardware Reference Manual (Part Number
3027M100-00x)

If the T1/E1 port is configured for unchannelized data and

ISDN signaling, then each DIM can be configured as multiple
voice channels along with one reserved signaling channel,
however, there is no ISDN data call capability;
• in the case of T1, 23 voice channels with channel 24
reserved for message oriented ISDN signaling
• in the case of E1, 30 voice channels with channel 16
reserved for message oriented ISDN signaling

When the T1/E1 port is configured for E1 unframed, then the

channel is a bundle of 32 channels. It is a data pipe and cannot
be used for voice.

DIM When ISDN signaling is not in use, each voice configurable

Configuration DIM is restricted to a maximum of 32 data channels for each
Restriction system CPU that is configured as channelized data. When
ISDN signaling is in use, then one data channel is used for
signaling, and each voice configurable DIM is restricted to a

3008M300-004 12-219
CXTool User Guide

Channelized Table 12-1 summarizes the services supported by channelized Table 12-2: Services on Unchannelized Ports
and data ports and Table 12-2 summarizes the services supported
Unchannelized by unchannelized data ports. Unchannelized Unchannelized Unchannelized Unchannelized Unchannelized
Ports
T1 E1 T1 E1 E1 Unframed
Table 12-1: Services on Channelized Ports
CAS CAS CCS ISDN CCS ISDN No signalling
Channelized Channelized Channelized Channelized
24 voice 30 voice 23 voice 30 voice No voice,
T1 E1 T1 E1
channels channels channels channels 32 data
CAS CAS CCS ISDN CCS ISDN dynamically dynamically channels as
24 voice and 30 voice and 23 dynamically 30 dynamically allocated allocated 1 data bundle
data channels data channels allocated voice allocated voice
and data and data No ISDN No ISDN
channels channels data call data call
capability capability
No signaling 1 signaling, 1 signaling 1 signaling
channel non data, data channel data channel No signaling 1 signaling, 1 signaling, 1 signaling, No signaling
channel #16 #24 #16 channel non data data channel data channel channel
reserved channel #16 #24 #16 reserved
1 CPU 1 CPU 1 CPU 1 CPU
reserved (One per (One per
supports 32 supports 32 supports 32 supports 32
DIM) DIM)
data channels data channels data channels data channels
max. max. max. max.
1 data bundle 1 data bundle No data No data 1 data bundle
per DIM per DIM bundle bundle per DIM

12.1.2 Slot Restrictions for the DIM

Whenever a DIM card is installed, it is important that the
restrictions concerning suitable slots for the DIM and
configuration of the DIM be followed. The primary source for
the restrictions are the hardware manuals:
• CX950/960 Hardware Reference Manual (Part Number
3021M100-00x)
• CX2000 Hardware Reference Manual (Part Number
3027M100-00x)
Following is a summary of the DIM slot allocation restrictions
as they apply to the CX950, the CX960, and the CX2000.
CX950 and The CX950 supports only one DIM and it is installed in slot 8.
the DIM The DIM can access SEM resources only from slot 8 when
configured for channelized data.
However, if the DIM is configured for one data bundle, or
unchannelized data (as data, not voice) then the DIM can be
placed in any slot.

12-220 3008M300-004
 12 CONFIGURING T1/E1

Table 12-3 summarizes the slot restrictions of the CX950. Table 12-4 summarizes the slot restrictions of the CX960.

Table 12-3: CX950 Slots in Which DIM is Allowed Table 12-4: CX960 Slots in Which DIMs are Allowed

Slot Number Slot Number

Max Max
DIM 1 2 3 4 5 6 7 8 DIM 1 2 3 4 5 6 7 8
s s

Unchannelized Data 8 Yes Yes Yes Yes Yes Yes Yes Yes Unchannelized Data 8 Yes Yes Yes Yes Yes Yes Yes Yes
(no data or one data + + + + (no data or one data + + + +
bundle) SEM SEM SEM SEM bundle) SEM SEM SEM SEM

Unchannelized Data 1 No No No No No No No Yes Unchannelized Data 2 No No No No No No Yes Yes

(as voice only) (as voice only)
Channelized Data 1 No No No No No No No Yes Channelized Data 2 No No No No No No Yes Yes
(more than one data + (more than one data + +
bundle) SEM bundle) SEM SEM

Yes = DIM allowed in this slot Yes = DIM allowed in this slot
No = DIM not allowed in this slot No = DIM not allowed in this slot
+ SEM = SEM allowed on DIM in this slot + SEM = SEM allowed on DIM in this slot

CX960 and The CX960 supports two DIMs. The first is installed in slot 8.
the DIM The second is installed in slot 7. However, if the DIM is
configured for one data bundle, or unchannelized data (as data,
not voice) then the DIM can be placed in any slot.
The DIM can access SEM resources only from slot 8 when
configured for channelized data. When there is a second DIM
in slot 7, SEM resources such as SCCs and QMCs, are
accessed on the H.100/H.110 bus through the DIM in slot 8.
CX2000 and Each CPU module installed in the CX2000 supports up to three
the DIM DIMs. The first DIM is installed in slot 8. The second is
installed in slot 7. The third in slot 6. However, if the DIM is
configured for one data bundle, or unchannelized data (as data,
not voice) then the DIM can be placed in any slot.
The DIM can access SEM resources only from slot 8 when
configured for channelized data. When there DIMs with SEMs
in other slots, SEM resources such as SCCs and QMCs, are
accessed on the H.100/H.110 bus through the DIM in slot 8.

3008M300-004 12-221
CXTool User Guide

Table 12-5 summarizes the slot restrictions of the CX2000. Configuring In Figure 12-1, both the local site and the remote site have a
T1/E1 for CX950, and both have two cards; an ATM Cell I/O, and a
Table 12-5: CX2000 Slots in Which DIMs are Allowed Voice Digital Interface Module (DIM).
Services on
Slot Number CX950

Max
DIM 1 2 3 4 5 6 7 8 Local Site Remote Site
s
DIM card ATM Cell I/O
DIM card ATM Cell I/O
in slot 8 in slot 2
Unchannelized Data 8 Yes Yes Yes Yes Yes Yes Yes Yes in slot 8 in slot 2
(no data or one data + + + + CX950
CX950
bundle) SEM SEM SEM SEM (C) (E)

Unchannelized Data 3 No No No No No Yes Yes Yes

(as voice only) T1 T1
ATM
TM
Channelized Data 3 No No No No No Yes Yes Yes VPI = 1
(more than one data + + + VCI = 30
bundle) SEM SEM SEM
T1 T1
PBX PBX
Yes = DIM allowed in this slot
No = DIM not allowed in this slot
+ SEM = SEM allowed on DIM in this slot
Ext.2002 Ext. 5005

12.1.3 Typical T1/E1 Configuration

The following examples illustrate the modules, sub-modules,

Figure 12-1: Voice via a T1/E1 Interface on CX950
and parameters that need to be configured to send voice traffic
via a T1/E1 interface. Assume that the calling phone at extension 2002 would like to
reach the phone at extension 5005. For this call to go through a
T1 interface and cross an ATM network, the calling user
configures the system as outlined below.

12-222 3008M300-004
 12 CONFIGURING T1/E1

• Voice Capability: G.729/G.726/G.711 • ATM Virtual Circuit

• Voice station: CPU on CX950 aal5
VPI: 1
• T1 Port VCI: 30
DIM 8.1 (Channelized data) Encapsulation: llcEncapsulation
Trunk Type: T1 Circuit Type: CBR
Channels Available: 8.1.1 to 8.1.24
• ATM Traffic Services
Time slots 1 to 16: configured for voice
Time slots 17 to 24: configured for channelized data Traffic Type: CBR
Line Type: ESF PCR: 300
Line Coding: B8ZS CDVT: 0
Signal Mode: RobbedBit • WAN Trunk
Clock Source: LoopTiming
PCM Voice Coding: mu_law ATMVCL
Voice Pattern: xxxx (digits from the Remote Extension are
• Voice Channel compared to this pattern for routing)
Interface Type: T1
Home Extension: 2002
Local Extension: 2002
• DSP Channels
Channels Available: 8.1 to 8.30
Vocoder Group: g729_gr
Hardware Card Type: Digital
• Dialing Plan (digits dialed: 819 525-5005)
Dial Pattern: 819
Remote Extension: --- --- ++++
Called Number: --- --- ++++
• ATM Port
ATM Cell I/O 2.1

3008M300-004 12-223
CXTool User Guide

• Digit: Default Configuration: DTMF Standard; DTMF Local Site Remote Site
Standard; Transmit/Generation: DTMF; Receive/Detection: DVCB DVCB
Digital Voice I/O Digital Voice I/O
DTMF in slots
in slot 1
in slots
in slot 1
2&4 2&4
• Call Progress Tones: Default Configuration: USA
• Signaling Type: CAS CX1000 CX1000
(A) (C)

Configuring In Figure 12-2, both the local and remote sites have a
T1/E1 for CX1000e, and each has two cards; a Digital Voice I/O, and a
Voice DVCB.

T1
Services on

T1
CX1000e Frame
PBX DLCI = 40
Relay PBX
FAX

Ext. 5005
Ext. 4002
Ext. 5002
Ext. 4001

Ext. 5003

Ext. 5004

Figure 12-2: Voice via a T1/E1 Interface on CX1000e

Assume that the caller at telephone extension 4001 calls

extension 5003. In order for this call to go over a T1/E1
interface across a Frame Relay network, the user on the local
side is required to configure the modules, sub-modules, and
parameters. The configuration is described below.

NOTE: For the purpose of this example, we assume that

CX1000e(C) is configured correctly.

12-224 3008M300-004
 12 CONFIGURING T1/E1

• Voice Station: CPU on CX1000e • Voice Pattern: xxxx (The compression parameters are
configured automatically.) This call will be routed across the
• T1 Port
network based upon the pattern used in this parameter, which
Digital Voice I/O: 1.1 should match the pattern in the Remote Extension parameter.
Trunk Type: T1
ISDN: Enabled • Digit: Default Configuration: DTMF Standard; Transmit/
Channels Available: 1.1.1 to 1.1.23 Generation: DTMF; Receive/Detection: DTMF
Channel 24: reserved for signaling • Call Progress Tones: Default Configuration: USA
Line Type: ESF
Line Coding: B8ZS • CCS: Default Configuration: Transparent Mode.
Signal Mode: messageOriented
Clock Source: LoopTiming
PCM Voice Coding: mu_law
12.1.4 Features of T1/E1 Supported on CX Products

• Voice Channel:
T1 • physical interface: RJ-48C (100 ohms for CX1000e, 110 ohms
Interface Type: T1 Channelized for DIM)
Home Extension: 4001 Data
Local Extension: 4001 Interface • framing: D4 or ESF
(1.544 Mbps)
• DSP Channel: • line code: AMI or B8ZS
DVDB 2.1 to 2.15 • soft line buildout: long haul (0, 7.5, 15, and 22.5 dB); short haul
Compression: acelpII (0 to 660 feet)
Hardware Card Type: digital
• DS0 assignment: user selectable
• Dialing Plan: (digits dialed: 418-249-5003)
Dial Pattern: 4XX • clocking options: loop timing or local timing
Remote Extension: --- --- ++++ The options on the DIM are: loop timing, local timing, or
Called Number: --- --- > through timing.

• WAN Trunk • master clock (applies to DIM only): local, slave, or master
Frame Relay Station (CPU)
Frame Relay Port: V.35H 1.3
Link: Sync Driver
Frame Relay: DLCI - 40

3008M300-004 12-225
CXTool User Guide

E1 • physical interface: RJ-48C and dual BNC coaxial connectors • ISDN

Channelized 75 ohms (CX1000e only)
Data • SS7
Interface • framing: G.704 (E1 with/without CRC-4 and/or with/without
(2.048 Mbps) MF) • QSIG-GF

• line code: HDB3/AMI

• channel assignment: user selectable
• clocking options: loop timing or local timing
The options on the DIM are: loop timing, local timing, or
through timing.
• master clock (applies to DIM only): local, slave, or master
12.2 Configuring T1/E1
This section focuses on how to configure T1/E1 services on
Memotec devices with CXTool. The configuration sequence of
the CXTool application is followed and the parameters that are
encountered are described.

This configuration sequence is based on a DIM card plugged

Signaling T1 Robbed Bit Signaling into slot 8 of a CX950, and assumes that this hardware was
installed as described in Chapter 5.1 Creating a Hardware
• Digital E&M, FXS, and FXO Configuration or Chapter 5.2 Modifying a Hardware
Configuration.
T1 (CCS)
It is strongly advised that the following tables be consulted prior to
• ISDN configuring voice and data services.
• SS7 • Table 12-1: Services on Channelized Ports
E1 (CAS) • Table 12-2: Services on Unchannelized Ports
• Digital E&M, FXS, FXO, and R2 Full details of the restrictions concerning suitable slots for the
DIM and configuration of the DIM are given in the hardware
• MFC-R2
manuals:
E1 (CCS) • CX950/960 Hardware Reference Manual (Part Number
3021M100-00x)
• CX2000 Hardware Reference Manual (Part Number
3027M100-00x)

12-226 3008M300-004

For general information see section 12.1.1 Channelized and
Unchannelized Ports.
An overview of T1/E1 is provided in
Chapter 27 INTRODUCTING T1 AND E1.
12.2.1 Configuring the T1/E1 Port
The following configuration of a T1/E1 port is based on a
CX950 with a DIM installed in slot 8.
The T1/E1 folder contains the parameters associated with the
T1/E1 port and T1/E1 channels. From the T1/E1 folder in the
module navigation panel, select the Port module.
On the tool bar click the Add (+) button or, from the pull-down
Edit menu, select Add New. A warning appears, as shown in
Figure 12-3.
Figure 12-3: Channel Options for DIM
On the DIM card of a CX950, a CX960, or a CX2000, when
the need is for a single data bundle per DIM, or no data at all,
answer No. This instructs the system not to use the Quad
Multichannel Controller so that slot 5, slot 6, and slot 7 are able
to operate without any serial data I/O card restrictions.
3008M300-004
12 CONFIGURING T1/E1
However, if more than a single data bundle is needed, then
answer Yes. This restricts the use of serial data I/O cards in
slots 5, 6, and 7, as specified in the hardware manuals:
• CX950/960 Hardware Reference Manual (Part Number
3021M100-00x)
• CX2000 Hardware Reference Manual (Part Number
3027M100-00x)
After responding to the warning, the T1/E1 Port window
opens. When the hardware is a CX950 with a DIM in slot 8, the
screen is like the one shown in Figure 12-4.
The options for the T1/E1 port depend on the particular CX device
and previous selections.
1. Data Bundle State - Channelized/Unchannelized
Previous selections determine whether the Data Bundle State
group box is available or not. (See Figure 12-3.)
2. Voice
When enabled, this parameter allows the user to configure
multiple T1/E1 time slots of this port for voice traffic.
3. ISDN
This parameter allows the user to configure ISDN (PRI)
services on this port. Note that this service is available only
when the DIM card is in slot 8 of a CX950, in slot 7 or 8 of a
CX960, or in slot 6, 7, or 8 of a CX2000.
12-227
CXTool User Guide

4. Trunk Type
This parameter specifies the line (T1 or E1) that is configured
for the DIM card. The options available are listed below.
• T1: indicates that the link will be configured as a T1 trunk
(1.544 Mbps interface for North America).
• E1: indicates that the link will be configured as an E1 trunk
(2.048 Mbps interface for Europe).
• Clk_ref_t1 (applies to DIM only): indicates that port 2 of the
DIM (digital interface module) is configured as providing
the reference clock for port 1.
• Clk_ref_e1 (applies to DIM only): indicates that port 2 of the
DIM is configured as providing the reference clock for port
1.
5. Line Type
This parameter indicates the type of framing this interface is
using. The options available are listed below.
For T1
• ESF: Extended SuperFrame (24) DS1 (refer to Table 1 in
Recommendation G.704)
• D4: AT&T D4 format DS1 SuperFrame (12)
For E1
• Unframed: must be unchannelized data, and voice and ISDN
must not be checked
• E1: CCITT Recommendation G.704 (Table 4a)
Figure 12-4: Configuring the T1/E1 Port
• E1-CRC: CCITT Recommendation G.704 (Table 4b)
• E1-MF: G.704 (Table 4a) with TS 16 multiframing enabled
(refer to Table 9 in Recommendation G.704)
• E1-CRC-MF: G.704 (Table 4b) with TS 16 multiframing
enabled (refer to Table 9 in Recommendation G.704)

12-228 3008M300-004

6. Line Code
This parameter indicates the different types of Zero Code
Suppression used on the link, which in turn affects a number of
its characteristics. The options available are listed below.
• B8ZS (Binary 8 Zero Suppression): it codes the line by using
a specified pattern of normal bits and bipolar violations that
are used to replace a sequence of eight zero bits
• HDB3 (High Density Binary Three): it codes the line by
creating a Bipolar Polarity Violation (BPV) whenever more
than three zeros are encountered. HDB3 is used with or
without CRC
• AMI (Alternate Mark Inversion): it codes the line by
ensuring that successive ‘ones’ (marks) are alternately
inverted (sent with polarity opposite that of the preceding
mark). The AMI line coding provides high pulse density,
provided no long strings of zeros are to be transmitted
NOTE: T1 connections use B8ZS or AMI and E1 connections
use HDB3 or AMI.
7. Signal Mode
This parameter indicates the type of signaling used on this
channel. The options available are listed below.
• None: indicates that no bits are reserved for signaling on this
circuit
• Robbed Bit: indicates that T1 Robbed Bit signaling is in use
• Bit Oriented: indicates that E1 CAS is in use
• Message Oriented: indicates that the Common Channel
Signaling is in use either on channel 16 of an E1 link or on
channel 24 of a T1 link
3008M300-004
12 CONFIGURING T1/E1
8. Clock Source
This parameter indicates the source of the clock. The options
available are listed below.
• looptiming: indicates that the recovered receive clock is used
as the transmit clock
• localtiming: indicates that a local clock source is used as the
transmit clock
• throughtiming: indicates that recovered receive clock from
another interface is used as the transmit clock. This
parameter is applicable for DIM used in the CX950/CX960/
CX2000
9. PCM Voice Encoding
This parameter indicates the voice encoding scheme used by
the DSP channels. The mu_law scheme is used in North
America and A_law is used in Europe.
10. Port Enabled
When this parameter is enabled, this port can be used to send
and receive voice and/or data traffic.
Advanced The remaining parameters in this module are advanced
functions. It is recommended that they not be modified. A
description of the advanced parameters is provided below
primarily for the purpose of information.
1. LoopBack Configuration
This parameter sets the state of the loopback configuration of
the DS1 interface. The options available are listed below.
• NoLoop: indicates that there is no loopback.
• PayloadLoop: indicates that only the payload portion of the
received signal at this interface is looped back (e.g., a PBX).
Typically the received signal is looped back for re-
12-229
CXTool User Guide
transmission after it has passed through the device’s framing
function.
• LineLoop: indicates that the complete signal, received at this
interface is looped back to the device (e.g., a PBX).
NOTE: In T1 systems, both types of loopback can be
configured on any card. In E1 systems, LineLoop can
be configured on any card but PayloadLoop can be
configured only on a DIM.
2. Facility Data Link
This parameter describes the use of the T1 Facility Data Link.
It is used to exchange data with the remote equipment. The
options available are as follows:
• ANSI:T1-403: refers to the FDL exchange recommended by
ANSI.
• Att-54016: refers to ESF FDL exchange.
• Fdl-none: indicates that the device does not use the FDL.
3. Line Build Out
This parameter indicates the attenuation or the Line Build Out
to be used on the transmitter side of the T1 or E1 line, and is
activated on-the-fly.
4. Master Clock
Master Clock allows the user to set the clock type to be used by
the DIM.
This parameter applies only to a DIM card that is installed on a
CX960 or on a CX2000. This parameter also applies to a DIM
card installed on a CX950, but Master Clock should always be
set to Local on a CX950.
12-230
In general, the Master Clock option is set to Local, or a Master
DIM is established and related DIMs are set to Slave. Choose a
Master/Slave setup in the following circumstances:
• when the DIM is in a slot other than slot 8 and is configured
with channelized data
• when there is “drop and insert” involving more than one
DIM
• when the DSP channels of another DIM are to be used
• when all ports are to be synchronized, that is, all ports are to
use the same clock
In a CX960 there must be only one master network reference
clock. Note that if slots 7 and 8 are configured with
channelized data channels in a CX960, then the clocks of both
the DIMs must be synchronized. That is to say, if the Master
Clock type on the DIM in slot 7 is configured as “master”, then
the DIM in slot 8 must be configured as “slave”, and vice
versa.
In a CX2000 each CPU may have its own master reference
clock. Note that if slots 6, 7, and 8 are configured with
channelized data channels in a CX2000, then the clocks of all
three DIMs must be synchronized. That is to say, if the Master
Clock type on the DIM in slot 6 is configured as “master”, then
the DIMs in slots 7 and 8 must be configured as “slave”.
The options available for the Master Clock parameter are the
following:
• slave: if this option is selected, then for each CPU one other
port in the chassis must be configured as the master clock
reference and the Clock Source must be set to
“throughtiming”. This will ensure that the master clock
reference will be used on this port as well. Select this option
3008M300-004
 12 CONFIGURING T1/E1

when two ports on different DIMs need to interact with each • TxAttenuator 128Bits
other.
DIM cards:
• master: if this options is selected, the Clock Source must be
set to “looptiming” or “localtiming” and that will ensure that • noJitterAttenuator
this port will become the master clock reference. • TxAttenuator 40Bits
• local: if this option is selected, the port will be totally • RxAttenuator 40Bits
independent from those on other DIM I/O cards.
• TxRxAttenuator 40Bits
5. Backup Clock.
This parameter is applicable only to the DIM card. It indicates
NOTE: When the Trunk Type for DIM is T1, use
the backup clock for the one selected in Clock Source. The
“TxAttenuator 40Bits”.
Backup Clock is active only if the Master Clock is configured
as “master.” The options available are as follows:
• loop_STEP: indicates that the received recovered clock of
the Secondary T1/E1 Processor (STEP) interface will
become the backup clock in the event of a clock failure
• local_T1: indicates that the local clock from the 1.544 MHz
on-board oscillator will become the backup clock in the
event of a clock failure
• local_E1: indicates the local clock from the 2.048 MHz on-
board oscillator will become the backup clock in the event of
a clock failure
6. Jitter Attenuator
When the Jitter Attenuator is enabled in the transmit or receive
direction, a buffer is used to ensure frame alignment and clock
synchronization.
The options available are as follows:

Non DIM cards:

• RxAttenuator32Bits
• RxAttenuator128Bits
• TxAttenuator 32Bits

3008M300-004 12-231
CXTool User Guide
To configure channelized ISDN services on a T1 or E1
interface, click to put a check mark in the ISDN check box of
the T1/E1 Port module, as shown in Figure 12-5.
Figure 12-5: Configuring the ISDN Service on T1/E1
12.2.2 Configuring T1/E1 Channels
The T1/E1 ports may be configured as channelized data or
unchannelized data. Below we show how to configure both
options.
12-232
Channelized From the T1/E1 folder, select the T1/E1 Channel module.
Data Click on the Add (+) button in the tool bar or select Add New
from the pull-down Edit menu.
• In the case of a CX950, if the T1/E1 port is configured with a
DIM card in slot 8, the screen shown in Figure 12-6 appears.
• If the T1/E1 port is configured
in the case of a CX960 with a DIM card in slot 7, or slot 8,
or in the case of a CX2000 with a DIM card in slot 6, slot 7, or
slot 8, the screen shown in Figure 12-6 appears.
Configure the following parameters:
1. Timeslot
This parameter indicates the number of time slots that can be
configured (e.g., 24 for T1, and 31 for E1).
2. Type
This parameter indicates the type of service with which a
particular time slot is associated. The options available are
listed below.
• voice: indicates that this time slot is used for voice traffic
• ISDN: indicates that this time slot is used for carrying ISDN
traffic
• HDLC: indicates that this time slot is used for carrying data
traffic
• Drop and Insert type (applies to DIM only) This parameter is
for future use
3. Data Bundle ID
When the channel type is “hdlc”, the user has the option of
combining channels. This feature is useful when the bandwidth
3008M300-004
 12 CONFIGURING T1/E1

(configured as Data Bundle ID “BB”) are also going to the

same destination, but not the same destination as “AA”.

Figure 12-6: Configuring the T1/E1 Port (Channelized)

requirement is greater than 64 kbps and the destination of the

data streams is the same.
Figure 12-7 shows that the data on Timeslots 1, 2, 3, 4, and 5
(identified by a Data Bundle ID “AA”) are going to the same Figure 12-7: Configuring Data on a Channelized Data Port
destination. The data on Timeslots 11, 12, 13, and 14
NOTE: Refer to the restrictions shown in Table 12-1 and
Table 12-2.

3008M300-004 12-233
CXTool User Guide

4. Setting Group Selection TimeSlot Type 8, port 1 has been configured for ISDN, voice, and multiple
This parameter allows a group of time slots to be selected for a data services.
particular type of traffic.
To use this feature, first select the time slots under the “Type”
column. Then, in the Setting Group Selection TimeSlot Type
group box, select the traffic type from the drop-down list, and
click on “Set Selection”.
If the ISDN service is enabled on the T1 or E1 port, the user
can then configure the T1 or E1 time slots on that port for
ISDN PRI or ISDN PRI_QSIG services, together with voice
and data services. For example, Figure 12-8 illustrates that slot

Figure 12-8: Configuring T1/E1 Timeslots for Multiple Services

12-234 3008M300-004
 12 CONFIGURING T1/E1

The configuration types shown in Figure 12-8 are the

following:
• time slots 1 to 6 can be used dynamically for voice and data
when the Interface Type is an ISDN PRI or ISDN PRI_QSIG
• time slots 7 to 10 can only be used for voice
• time slots 11 to 14 can only be used for data when the
Interface Type is T1 or E1

Unchannelized From the T1/E1 folder, select the T1/E1 Channel module.
Data Click on the Add (+) button in the tool bar or select Add New
from the pull-down Edit menu.

The screen shown in Figure 12-9 appears if the T1/E1 port

was; configured on a DIM card in a slot other than those
mentioned in the sections under Channelized Data, above; or
on a T1/E1 card in any slot.

The only parameter that the user may configure is the one
titled: “Number of Timeslot Used”.

Figure 12-9 shows that time slot 1 through to time slot 10 are
used for data.

Remember that when the voice option is not checked (refer to

Figure 12-4), the data port may be used only for data.

Figure 12-9: Configuring the T1/E1 Port

(Voice not checked. Refer to Figure 12-4)

3008M300-004 12-235
CXTool User Guide

12-236 3008M300-004
 13 CONFIGURING SNA

This chapter describes how to configure SNA on a Memotec

CX product using CXTool. It also includes an overview of
Memotec’s SNA implementation in the CX product family.

Users of this guide are assumed to have an understanding of

networking and networking issues. A review of SNA basics is
provided in Chapter 28 INTRODUCING SNA.

3008M300-004 13-237
CXTool User Guide

13.1 Memotec’s CX Family and the SNA 10. Multipoint and/or Point-to-Point support.

Environment 11. BNN (Boundary Network Node) and BAN (Boundary Access
Node) support.
12. Locally acknowledged 802.2, 802.3, 802.5.
13.1.1 Protocol Support

SNA traffic presented on an access port of a CX product can Configurable The configurable parameters for the SDLC line are:
have any of the following forms: SDLC
1. SDLC (synchronous data link control) Parameters • Primary/Secondary device emulation.

2. X.25, QLLC (qualified logical link control) • Full/Half duplex communication with controllers sharing the
same SNA/SDLC port.
3. RFC1490 (FRF-3)
• Raising of SNA port signals upon an end-to-end connection
4. LLC2 on 802.3 (Ethernet) and 802.5 (Token Ring) establishment.
• Link type: PU1, PU2.0, PU2.1, switched, negotiable.
13.1.2 Product Features

Configurable The configurable parameters for each defined CU device are

General The SNA features supported by CX products are the following: Control Unit listed below.
Features (CU)
1. Local spoofing of SDLC packets.
Parameters • SDLC frame size.
2. Each port can be configured to work as either a primary or
secondary device. • SDLC window size.

3. Can have multiple physical SNA connections. • Poll retry counter.

4. Support for up to 126 devices or control units. • Slow poll retry counter.
5. Up to 4096 byte SDLC data frame length. • Poll timer.
6. NRZ/NRZI line encoding. • Slow poll timer.
7. Internal and external clock.
8. Support of marks between SDLC frames or flags between
SDLC frames, and IBM AS/400 support of marks when idle
with flags between non-poll bit frames.
9. Physical Full/Half duplex support.

13-238 3008M300-004
 13 CONFIGURING SNA

• Wait for next SNRM or XID Response from HOST before • SDLC CU
transmitting response. CUAdd: 01
• support of Disconnect Mode (On/Off). I-Frame Size: 521 Bytes
Transmit Window: 7
• Support of Disconnect (On/Off). WAN Delay Time: 0
Secondary-Poll Retry: 3
• Remote response timer.
Secondary-Slow Poll Timer: 10
The next section gives a brief overview of typical SNA services Poll Ack. Timer: 20
that are possible with Memotec devices, together with a list of CU Max Retry: 3
parameters that the user is required to configure for those Disconnect Command: DISC
services. • LLC2 WAN1
Frame Relay Port: 2.1 V.35H Serial
FRDLCI: 100
13.2 Typical SNA Configuration
• Link
Using the scenario in Figure 13-6 as a point of reference, let us Primary Link: LLC2 WAN1
assume that Side A has a CX800 and Side B has a CX900e. Secondary Link: SDLCPort1_01
Both sides can send and receive information. In the example
below, CX800 is configured as a secondary link station. SNA/ Configuring CX900e
SDLC traffic is sent from the Control Unit and is encapsulated • SDLC Port1
into Frame Relay. CX900e is configured as a primary link
station. It accepts Frame Relay traffic and converts it back into Synchronous Driver: 1.1 V.24 Serial
SDLC before sending it to the Host. Primary Link Station
Line Type: Negotiable
Both sides have two serial cards: V.24 and V.35H. In order for
• SDLC CU
SNA traffic to go from Side A to Side B, both sides are
configured in the manner indicated below. CUAdd: 01
I-Frame Size: 521 Bytes
Configuring CX800 Transmit Window: 7
WAN Delay Time: 0
• SDLC Port1 Primary-Hold UA/XID Response: No
Synchronous Driver: 1.1 V.24 Serial Primary-Disconnect Command: DM
Secondary Link Station

3008M300-004 13-239
CXTool User Guide

• LLC2 WAN1 • LLC2 LAN

Transmission Mode: BNN • LLC2 WAN
Frame Relay Port: 2.1 V.35H Serial;
FRDLCI: 200 • SDLC CU

• Link
Primary Link: SDLCPort1_01
Secondary Link: LLC2WAN1
Primary Side Seconary Side
The next section focuses primarily on how to configure SNA
services on Memotec devices with CXTool. It adheres to the Link types:
(host) (controller) Link types:
LLC2 LAN LLC2 LAN
sequence in CXTool and provides a description of all the LLC2 WAN CX device CX device LLC2 WAN
parameters the user will counter during configuration. SDLC CU emulates the emulates the SDLC CU
controller host

13.3 Configuring SNA using CXTool Figure 13-1: SNA Link Type Supported

Correctly identifying the primary and secondary sides for the

This section describes how to configure SNA on a CX product.
purpose of cross-connecting them will ensure a valid link.
The SNA folder in CXTool contains all the modules/sub-
Figure 13-2 and Figure 13-3 provide examples of cross-
modules and parameters associated with SNA, including
connecting the primary and secondary sides of a CX device for
SDLC Port, SDLC CU, LLC2 LAN, LLC2 WAN, QLLC, and
two different configurations. In Figure 13-2, the SDLC port of
Link.
the CX900e that is connected to the AS/400 is emulating a
secondary station, therefore it is considered the secondary side
13.3.1 Configuring the SNA Link of the link through the CX900e. The LAN port of the CX800 is
the secondary side in relation to the LAN port of the CX900e.
Within each CX device you must configure a cross-connection This principle extends to the relationship between the CX800
to enable end to end SNA communication. The cross- LAN port and its SDLC port which emulates a primary station.
connection links the Primary side with the Secondary side.
Memotec’s family of CX products support three types of
cross-connection, as diagramed in Figure 13-1.

13-240 3008M300-004
 13 CONFIGURING SNA

Configuring From the SNA folder, select the Link module. To add this
SNA Link module, click on the Add (+) button in the tool bar or select
AS/400 Add New from the pull-down Edit menu. The following screen
will appear:

SDLC SDLC CU SDLC SDLC CU

(SECONDARY) (PRIMARY)

ETHERNET

CX900e CX800

LLC2 LAN LLC2 LAN

(PRIMARY) (SECONDARY)
Figure 13-2 Configuring Ethernet Between SDLC Devices

SDLC SDLC CU SDLC SDLC CU

(SECONDARY) (PRIMARY) Figure 13-4: Configuring the SNA Link

Configure the parameters as shown below.

WAN
1. Primary Link
CX900e CX800
This parameter allows the user to choose an LLC2 WAN/LAN
LLC2 WAN LLC2 WAN
(PRIMARY) (SECONDARY) or SDLC CU that serves as the Primary side of the connection.
Figure 13-3: Configuring LLC2 Between SDLC Devices

3008M300-004 13-241
CXTool User Guide
2. Secondary Link
This parameter allows the user to choose an LLC2 WAN/LAN
or SDLC CU that serves as the Secondary side of the
connection.
To continue configuring the Link module, click on
“Properties.” The following screen appears:
Figure 13-5: Configuring the SNA Link (Continued)
Configure the parameters as shown below.
13-242
1. Max Retries
This parameter determines the maximum number of attempts
to establish this cross- connection before it is abandoned. If set
to 255, SNA Link Conversion continues to retry until
successful.
2. PU-ID
The value in this parameter must match the value in the
Exchange ID (XID) parameter on the host which is usually
given the network administrator. The PU identifier is composed
of the block ID and node ID. This parameter applies only when
the destination-side of a cross- connection is LLC-2 (IEEE
802.2 LLC) and when the “Cross Connect Method” is set to
'local'.
3. Transparent XID
This parameter determines if any changes are to be made to the
XID. If transparent mode is specified, XID information fields
are not modified, and the XID's are passed transparently
between the lower software layers (i.e.: SDLC, QLLC, LIM).
4. Connect Interval
This parameter determines the delay between attempts to
establish this cross-connection when not in slow connect mode.
5. Wait Contact Timer
This parameter determines the amount of time to wait for a Set
Mode or SNA XID frame from the remote station after the link
has been established.
6. Slow Connect - Threshold
This parameter determines the number of attempts that are
made to establish a cross- connection. When the threshold
defined by this parameter is reached, slow connect mode is
initialized. In this mode, cross-connection attempts continue,
but the interval between attempts is set by the value in the
“Slow Connect - Interval.”
3008M300-004
 13 CONFIGURING SNA

7. Slow Connect - Interval

This parameter determines the delay between attempts to
establish a cross-connection when in slow connect mode.
8. Cross Connect Method - Local
This parameter indicates that the cross-connection is
established by first attempting to bring up the source
connection. The destination connection is only established
CONTROL
after the source connection has transmitted data. This means UNIT
that connection establishment frames are not transported
between the source and destination links. SDLC SDLC

9. Cross Connect Method - End to End

This parameter indicates that the cross-connection is Frame
Relay
established by first bringing up both the source and destination
links layers. Next, connection establishment frames are CX900e CX800
transported (with conversion) between the source and
destination links to establish the connection. This option must Figure 13-6: Sample SNA Network Using SDLC
be selected when connecting PUs 1 or Nodes Type 2.1, or when
connecting SDLC or QLLC switched lines. It allows XID From the SNA folder, select the SDLC (Port) module. To add a
frames to be propagated between the two cross-connected Port, click on the Add (+) button in the tool bar or select Add
stations.

13.3.2 Configuring the SDLC Port

An SDLC port has two modes of operation depending on

which side of the link it serves. As illustrated in
Figure 13-6,when the SDLC port is connected to one or more
SNA control units (secondary link stations) and their supported
terminals, it emulates a primary link station. When the SDLC
port is connected to a host, it emulates the control units
(secondary link stations).

3008M300-004 13-243
CXTool User Guide

New from the pull-down Edit menu. The following screen will the attached device. A negotiable line can support more than
appear: one device.
3. Line Type - General Poll
When this parameter is enabled, the device receives an XID
using the general poll address (0xFF). The line is also
negotiable and unlike Line Type - Negotiable, it can support
only one attached device per port.

NOTE: The decision as to which one of the two line types to

use, depends upon the configuration of the attached
device.

4. Synchronous Driver
This parameter allows the user to configure a synchronous
driver that is associated with this SDLC port. For more details
see 6.4 Configuring a Synchronous Driver.
5. Attached Device - Primary Link Station
This parameter refers to the host station such as an IBM AS/
400.
6. Attached Device - Secondary Link Station
This parameter refers to the controller such as an IBM 5294.
7. Polling Interval
Figure 13-7: Configuring SDLC Port This parameter determines the length of time allowed to elapse
between the reception of an acknowledgment to a poll and the
Configure the parameters as shown below. transmission of the next poll. Certain control units require a
delay in order to successfully respond to polls. Since multiple
1. Name SDLC logical links may share the same port (i.e., multiple
This parameter allows the user to change the default name. control units communicating on the same physical link), this
2. Line Type - Negotiable timer applies globally to all logical links using this port.
When this parameter is enabled, the device receives an
eXchange identification (XID) frame without sending a poll to

13-244 3008M300-004
 13 CONFIGURING SNA

8. Transmission Mode - Full Duplex or Half Duplex Add New from the pull-down Edit menu. The following screen
This parameter allows the user to transmit data at full or half will appear:
duplex. Although SDLC is capable of full duplex operation,
almost all practical applications are strictly half duplex. This
means that either the primary or one of the secondaries can be
transmitting at any one time, but never both.
9. Data Terminal Ready (DTR) on Connect
When this parameter is enabled, DTR is raised on the physical
port in response to a connection request from the SNA Link
Conversion layer.

13.3.3 Configuring the SDLC Control Unit (CU)

An SDLC CU manages data communications. It also collects

diagnostics and status information and sends it to the host.

From the SNA folder, select the SDLC (CU) module. To add
this module, click on the Add (+) button in the tool bar or select

Figure 13-8: Configuring the SDLC Control Unit

SDLC Control Unit (CU) configuration is an extension of the

datalink parameters configuration for the SDLC port.

Configure the parameters as shown below.

1. CU Address
This parameter configures the Control Unit address based on
the attached device (host or controller).

3008M300-004 13-245
CXTool User Guide
2. I-Frame Size
This value in this parameter determines the largest information
frame that can be sent and received by the control unit or host.
The value must match the setting on the host or control unit the
port is communicating with.
3. Transmit Window
This value in this parameter determines the maximum number
of information frames that can be outstanding at any given
time. A frame is considered to be outstanding until the control
unit or host acknowledges its receipt.
4. Configure the remaining Primary or Secondary parameters, if
necessary. The availability of these parameters depends on the
Attached Device setting in the SDLC Port dialog box. Refer to
13.3.2 Configuring the SDLC Port.
• Primary - Hold UA/XUD Response: when the “No” option
is selected, the HIU sends the UA or XID response to the
host immediately. When the “Yes” option is selected, the
HIU holds the UA or XID response until the host repeats the
original poll. This is used in cases where the delay on the
link between the HIU and TIU can cause the host to time
out.
• Primary - Disconnect Command: when Disconnect Mode
(DM) is selected, a disconnect message is sent to the next
layer.
• Secondary - Poll Retry: determines the number of times an
unacknowledged poll is retransmitted. A poll is
retransmitted if an acknowledgment has not been received
from the control unit before the “Poll Ack. Timer” expires.
• Secondary - Slow Poll Time: determines the amount of time
the TIU waits for the control unit (secondary link station) to
respond to a SNRM poll during slow polling. Each time this
timer expires another poll is sent. The “Poll Retry”
13-246
parameter determines how many slow polls are transmitted.
The TIU begins slow polling if the “Poll Ack. Timer”
expires before the control unit has responded to the initial
SNRM, XID, or DISC poll.
• Secondary - Poll Ack Time: defines the amount of time the
TIU waits for the control unit (secondary link station) to
acknowledge a poll. If no response is received before this
timer expires, then the poll is retransmitted. The “Poll Retry”
parameter determines how many times the TIU retransmits a
poll. If the poll was a SNRM, XID, or DISC, then the first
time this timer expires, the “Slow Poll Timer” is started, and
the TIU slow polls the control unit.
• Secondary - Max Retry: determines the number of times an
unacknowledged DISC, SNRM, or XID is retransmitted
during slow polling. A poll is retransmitted if an
acknowledgment has not been received from the control unit
before the Slow Poll Timer expires. This timer is reset each
time a DISC, SNRM, or XID is transmitted. When this
counter is exceeded, the link with this control unit is
abandoned.
• Secondary - Disconnect Command: If this entry is associated
with an HIU port, this parameter determines the maximum
amount of time that the HIU waits for a response to a SNRM
or DISC sent to the TIU. This is used to control link setup
across the WAN between the HIU and TIU. When this timer
expires, the link is dropped.
If this entry is associated with a TIU port, this parameter
determines the maximum amount of time that the TIU waits
for a response to a DISC sent to the HIU. When this timer
expires, the link is dropped. At a minimum this timer should
be set greater than the propagation delay on the link.
3008M300-004
 13 CONFIGURING SNA

13.3.4 Configuring LLC2 LAN Add New from the pull-down Edit menu. The following screen
will appear:
SNA devices use LLC2, a connection-oriented data link layer,
when they establish sessions through a LAN topology. LLC2
LAN configuration requires the setup of the data link between
the LAN port and the local host or controller. Figure 13-6
illustrates an SNA network that uses LLC2.

AS/400

CONTROL
UNIT

Ethernet
Ethernet

LLC2
LLC2

Frame
Relay
CX900e CX800

Figure 13-9: Sample SNA Network Using LLC2

From the SNA folder, select the LLC2 (LAN) module. To add
Figure 13-10: Configuring the LLC2 LAN
this module, click on the Add (+) button in the tool bar or select
Configure the parameters as shown below.
1. Destination MAC Address
This parameter determines the MAC address of the host or end
station on a LLC2 LAN.

3008M300-004 13-247
CXTool User Guide

2. Local MAC Address To continue configuring LLC2, click on “Next.” The following
This parameter allows the user to configure the local MAC screen appears
address when the “Virtual MAC Address” parameter is
enabled.
3. Source and Destination Service Access Points (SAPs)
SAP addresses are used to establish a unique connection
between an application running on the end station and a route
through the CX product.
4. Look In
This parameter allows the user to configure a LAN Driver
(Ethernet or Token Ring) from the drop-down list. If the port is
not available, click Add; refer to 6.4 Configuring a
Synchronous Driver or 6.5 Configuring a Token Ring Driver,
as applicable.
5. Source Routing Network
When enabled, this parameter allows traffic to operate in a
source routed LLC2 LAN environment.

Figure 13-11: Configuring the LLC2 DataLink

The Data Link parameters include the setting of polling and

response timers that are critical to the maintenance of an LLC2
session.

Configure the following parameters in this folder:

1. Max Frame Size
This parameter determines the maximum size of the LAPB/D
information field supported by this port.

13-248 3008M300-004

2. Max Retrans
This parameter determines the maximum number of attempts
made to successfully transfer a command frame (error
recovery) after the acknowledgment timer expires. (Known as
N2.).
3. T2 Timer
This parameter determines the period of time (T1)within which
this port must acknowledge a frame it has received. This timer
must always be less than the setting for T1 timer on the remote
side. Otherwise, the remote side will time out before this port
can respond.
4. T1T200 Timer
This parameter determines how long this port waits for a
response to a command frame before initiating error recovery
(Known as the checkpoint timer (T1)). The value set in this
parameter must be smaller than the value set for object
T3T203.
5. Congestion Timer
This parameter determines the maximum amount of time
LAPB/D waits for the link to become uncongested before it
terminates the link. This timer is started when the number of
frames queued for a data link connection associated with this
port reaches the congestion threshold. This timer is stopped
when the number of frames queued for a data link connection
reaches the congestion minimum. If this timer expires, the data
link connection is terminated.
13.3.5 Configuring LLC2 WAN
3008M300-004
13 CONFIGURING SNA
6. Window - Modulo 8/Modulo 128
This parameter determines the range of sequence numbers
available for frame numbering at this port. The options
available are as follows:
• modulo8: implies that the sequence numbers range from 0 to
7 supporting a maximum window size of 7.
• modulo128: implies that the sequence numbers range from 0
to 128 supporting a maximum window size of 127.
7. Window - Window Size
This parameter determines the maximum number of
information frames that can be outstanding at any given time.
A frame is considered to be outstanding until the other side
acknowledges its receipt. This parameter supports modulo 8
and modulo 128 service. The options available are as follows:
• 1 - 7: select this size if object modulo is set to modulo8
• 1 - 127: select this size if object modulo is set to modulo128
.
8. Interface Module Connect method - Primary [Gen. XID]
This parameter indicates that this station initiates the NULL
XID exchange.
9. Interface Module Connect method - Secondary [Rec. XID]
This parameter indicates that this station waits for the remote
side to initiate the NULL XID exchange
CX devices support the routing of LLC2 over Frame Relay.
LLC2 WAN configuration requires the setup of the data link
between the local WAN port and the remote CX device.
13-249
CXTool User Guide

From the SNA folder, select the LLC2 (WAN) module. To add 2. Local MAC Address
this module, click on the Add (+) button in the tool bar or select This parameter allows the user to configure the local MAC
Add New from the pull-down Edit menu. The following screen address when the “BAN” parameter is enabled.
appears:
3. Source and Destination Service Access Points (SAPs)
SAP addresses are used to establish a unique connection
between an application running on the end station and a route
through the CX product.
4. Transmission Method
This parameter allows the user to send and receive traffic via a
Boundary Access Node (BAN) or a Boundary Network Node
(BNN) across a WAN (e.g., Frame Relay).
If the number of controllers per Host is less than 32, use BNN,
otherwise use BAN.
5. Priority
This parameter determines the priority level assigned to data
frames transmitted over this virtual circuit. Higher priority
traffic takes precedence over lower priority traffic. For
instance, if LAN, voice, SDLC/data are being carried on the
same Frame Relay circuit, CX devices will prioritize traffic in
the following manner:
• voice: priority_high
• SDLC/data: forward
• LAN: priority_low
Figure 13-12: Configuring the LLC2 WAN 6. Reference Number
This parameter specifies a reference number that uniquely
Configure the parameters as shown below. identifies this route. The number is used by the Frame Relay
1. Destination MAC Address Interface Module (FRIM) to identify routes using the same
DLCI (enables PVC consolidation). This number must be
This parameter determines the MAC address of the host or end
unique for all routes sharing the same DLCI.
station on a LLC2 LAN.

13-250 3008M300-004
 13 CONFIGURING SNA

7. Look In
This parameter allows the user to configure a WAN circuit. If
the desired WAN circuit has not yet been configured, click on
Add.
• For Frame Relay, refer to 9.2.2 Configuring Frame Relay
DLCIs.
• For IP Tunneling, refer to 10.2.6 Configuring the IP Tunnel.
• For ATM, refer to 8.2.2 Configuring the Virtual Channel.

13.3.6 Configuring the QLLC Port

QLLC is ideal for situations where the SNA traffic is sent

across an X.25 network. When the QLLC elements are
configured, the connection to X.25 is automatically configured
as well.

From the SNA folder, select the QLLC (Port) module. To add
this module, click on the Add (+) button in the tool bar or select
Add New from the pull-down Edit menu. The following screen
appears:

Figure 13-13: Configuring the QLLC Port

Configure the X.25 Service Point, if not already configured.

Refer to Chapter 15 CONFIGURING X.25.

13.3.7 Configuring the QLLC Control Unit (CU)

From the SNA folder, select the QLLC (CU) module. To add
this module, click on the Add (+) button in the tool bar or select
Add New from the pull-down Edit menu. The following screen
appears:

3008M300-004 13-251
CXTool User Guide

Figure 13-14: Configuring the QLLC-CU Figure 13-15: Configuring the QLLC-CU (Continued)

Configure the parameters listed below.

1. CU Address
This parameter identifies the control unit address associated
with this DTE entry.
2. Called Address
This parameter determines the DTE to call to establish a QLLC
connection.

13-252 3008M300-004

3. Attached Device
This parameter determines the type of interface (HIU or TIU)
associated with this DTE.
The options available are as follows:
• terminalInterfaceUnit: implies that the connection type is a
TIU, which means it is connected to one or more control
units (secondary link stations). The TIU emulates a primary
link station, and polls the attached control units. The SDLC
interface can support a total of 64 control units across all
TIU SAPs.
• hostInterfaceUnit: implies that the connection type is an
HIU, which means it is connected to an SNA host (primary
link station). The HIU emulates the control units connected
to a TIU. It responds to polls issued by the host.
4. Throughput Class
This parameter determines the transmit and receive throughput
class for this DTE when flow control negotiation is not
subscribed to, or when a D-bit call is routed through this port.
5. Packet Size
This parameter determines the maximum allowable transmit
and receive packet size for this DTE when flow control
negotiation is not subscribed to, or when a D-bit call is routed
through this port. Note that this value can never be negotiated
upwards, and that the size you set here must either be the same
as in the I-Frame Size parameter in the SDLC Control Unit
dialog box, or greater.
6. Window Size
This parameter determines the transmit and receive window
sizes for this DTE. This window size is used when establishing
calls from this DTE, or when receiving calls at this DTE.
QLLC only supports modulo 8 window size.
3008M300-004
13 CONFIGURING SNA
7. Segmentation
This parameter determines if segmentation is supported and is
to be performed by the QLLC layer for the specific DTE entry.
8. User Data
This parameter determines the data of each outgoing call
initiated by this DTE when calling non-Memotec devices. Up
to 12 characters can be specified and the format of this
parameter is determined by the value of the memotec
parameter.
9. Memotec
This parameter determines the type of product that the called
DTE address is associated with, which in turn determines how
the User Data parameter is constructed for all outgoing calls
from this DTE. This parameter also determines whether or not
the call is associated with a Switched Virtual Circuit (SVC) or
a Permanent Virtual Circuit (PVC).
The options available are as follows:
• nonMemotec: implies that the called DTE is not a memotec
device
• CXFamily: implies that the called DTE is a CX device
• legacy: implies that the called DTE is an older Memotec
product e.g., PX670
• PVC: implies that the connection type is PVC, which can be
either TIU or HIU.
Note that if the DTE is configured for an SVC but a PVC call is
received, the QLLC layer will attempt to connect to the PVC.
10. PVC
This parameter determines whether or not this DTE makes its
calls on a PVC.
13-253
CXTool User Guide

11. Connect Method

This parameter determines whether or not this DTE accepts
calls by validating the user-data field or by matching the calling
address with its corresponding called address. Note that this
object only applies to the HIU. The options available are as
follows:
• userdata: implies that the HIU DTE validates the call using
the user-data field
• callingaddress: implies that the HIU DTE validates the call
by matching the call's calling address with the configured
called address.
12. Facilities
This parameter determines the facility codes and associated
parameters for this DTE.

13-254 3008M300-004
 14 CONFIGURING ASYNCHRONOUS PAD

This chapter describes how to configure an Asynchronous

Packet Assembler/Disassembler (Async PAD) on a Memotec
CX device using CXTool. It includes an overview of
Memotec’s voice implementation in the family of CX devices.

Users of this guide should have an understanding of the Async

PAD before making changes to network systems. An
introduction to the AsyncPAD is provided in Chapter 29.

3008M300-004 14-255
CXTool User Guide

14.1 Memotec’s CX Products and the Async examples, the parameters that are preconfigured by CXTool
have not been mentioned.
PAD Environment
The Async PAD module in CXTool simplifies the
700
0 Central CX950
configuration of the async application. The following sections AsyncPAD
Toronto CX900e

show how Memotec implements Async PAD functions. Mainframe 1

7100
99
14.1.1 Summary of Async PAD features supported on CX 98

99
99
Products

00
72
Mainframe 2

0
730
Memotec’s implementation of Async supports these features:
X.25 TorTerminal 1 TorTerminal 2
• CCITT recommendations for X.3, X.25, and X.28
Async Terminals
• Traffic routing from X.25 to X.25 Main
Mainframe 3
Montreal CX900e
• Async over Frame Relay and async to X.25 over Frame
Relay Mainframe 4
11 1112
11
• SVC, PVC and pseudo PVC (auto connect)

MtlTerminal 2
14.1.2 Typical Async PAD Configuration MtlTerminal 1

Async Terminals
This section illustrates some of the typical scenarios in which
Memotec devices can be used for Async PAD services. In these
Figure 14-1: Configuring Async PAD Services

Referring to the scenario shown in Figure 14-1, here is the way

to configure the CX devices using Async PAD.

Montreal

The CX900e at the Montreal location has a Universal I/O card

in slot 1. It has five ports; two are configured as Async Ports,
and one is configured as X.25.

Configure the Async PAD Port

14-256 3008M300-004
 14 CONFIGURING ASYNCHRONOUS PAD

• Port 1
Async Driver: 1.1 DTE Name: Main2
WAN Connection: X.25 Service Point Service Type: Async
Service Point Name: MtlTerminal1 Called Address: 7100
Local X.25 Address: 1111
Associated Route Table: TableA DTE Name: Main3
• Port 2 Service Type: Async
Called Address: 7200
Async Driver: 1.2
WAN Connection: X.25 Service Point
Service Point Name: MtlTerminal2 DTE Name: Main4
Local X.25 Address: 1112 Service Type: Async
Associated Route Table: TableA Called Address: 7300

Configure the X.25 port Configuring an X.25 SVC Service - Some Scenarios

• Port • From Montreal to Toronto

Port Name: ToX25Network X.25 Address (Called Address): 999X
Link Type: Sync Driver: 1.3 Associated Route Table: TableA
Associated Route Table: TableA Route Call To: ToX25Network
• From Montreal to Main1
Configure the Remote DTEs
DTE Name: TorTerminal1 X.25 Address (Called Address): 7000
Service Type: Async Associated Route Table: TableA
Called Address: 9999 Route Call To: ToX25Network (routes the call through
Central)

DTE Name: TorTerminal2 Toronto

Service Type: Async
Called Address: 9998 The CX900e at the Toronto location has an Universal I/O card
in slot 1. It has five ports: two are configured as Async Ports,
DTE Name: Main1 and one as X.25.
Service Type: Async
Configure the Async PAD Port
Called Address: 7000

3008M300-004 14-257
CXTool User Guide
• Port 1
Async Driver: 1.1
WAN Connection: X.25 Service Point
Service Point Name: TorTerminal1
Local X.25 Address: 9999
Associated Route Table: TableA
• Port 2
Async Driver: 1.2
WAN Connection: X.25 Service Point
Service Point Name: TorTerminal2
Local X.25 Address: 9998
Associated Route Table: TableA
Configure the X.25 port
• Port
Port Name: ToX25Network
Link Type: Sync Driver: 1.3
Associated Route Table: TableA
Configure the Remote DTEs
DTE Name: MtlTerminal1
Service Type: Async
Called Address: 1111
DTE Name: MtlTerminal2
Service Type: Async
Called Address: 1112
DTE Name: Main1
Service Type: Async
Called Address: 7000
14-258
DTE Name: Main2
Service Type: Async
Called Address: 7100
DTE Name: Main3
Service Type: Async
Called Address: 7200
DTE Name: Main4
Service Type: Async
Called Address: 7300
Configuring an X.25 SVC Service - Some Scenarios
• From Toronto to Montreal
X.25 Address (Called Address): 111X
Associated Route Table: TableA
Route Call To: ToX25Network
• From Toronto to Main1
X.25 Address (Called Address): 7000
Associated Route Table: TableA
Route Call To: ToX25Network (routes the call through
Central)
Central
The CX950 at the Central location has a Universal I/O in slot 1;
four ports are configured as Async Port, and one port is
configured as X.25.
Configure the Async PAD Port
3008M300-004
 14 CONFIGURING ASYNCHRONOUS PAD

• Port 1 • Connecting Central to Montreal

Async Driver: 1.1 DTE Name: MtlTerminal1
WAN Connection: X.25 Service Point Service Type: Async
Service Point Name: Main1 Called Address: 1111
Local X.25 Address: 7000 Associated Route Table: TableA
• Port 2
Async Driver: 1.2 DTE Name: MtlTerminal2
WAN Connection: X.25 Service Point Service Type: Async
Service Point Name: Main2 Called Address: 1112
Local X.25 Address: 7100 Associated Route Table: TableA

• Port 3 • Connecting Central to Toronto

Async Driver: 1.3 DTE Name: TorTerminal1

WAN Connection: X.25 Service Point Service Type: Async
Service Point Name: Main3 Called Address: 9999
Local X.25 Address: 7200 Associated Route Table: TableA

• Port 4
DTE Name: TorTerminal2
Async Driver: 1.4 Service Type: Async
WAN Connection: X.25 Service Point Called Address: 9998
Service Point Name: Main4 Associated Route Table: TableA
Local X.25 Address: 7300

Configure the X.25 port

14.2 Configuring Async PAD with CXTool
• Port
Port Name: ToX25Network The Async PAD folder in CXTool contains all the modules/
Link Type: Sync Driver: 1.5 sub-modules and parameters associated with it, including
Associated Route Table: TableA Station, Port, X.3 Profile, and SVC WAN DTE.

Configuring Remote DTEs - Some Scenarios

3008M300-004 14-259
CXTool User Guide
14.2.1 Configuring the Async PAD Station
From the Async PAD folder, select the Station module and
click on the Add (+) button in the toolbar or select Add New
from the pull-down menu. The following screen appears:
Figure 14-2: Configuring the Async PAD Station
Configure the parameters listed below.
14-260
1. Queue Threshold
This parameter defines the global X.25 queue threshold, in
number of frames.
When the threshold is exceeded, a Disconnect Request, for
SVC, or a Reset Request, for PVC, takes place at the X.25
layer.
2. PAD Identification
This parameter defines the global Async PAD Identification
Banner. This banner is transmitted to the attached device
whenever it raises interface signals. For instance, when DTR is
detected from the attached terminal, the banner could read:
“Welcome to [name of your company/department].”
3008M300-004

14.2.2 Configuring the Async PAD Port
From the Async PAD folder, select the Port module and click
on the Add (+) button in the toolbar or select Add New from
the pull-down menu. The following screen appears:
Figure 14-3: Configuring the Async PAD Port
Configure the parameters listed below.
1. Async Driver
This parameter allows the user to add an async driver or
modify an existing one.
3008M300-004
14 CONFIGURING ASYNCHRONOUS PAD
2. X3 Profile
This parameter determines which set of X.3 parameters to use.
3. Disconnect Request
This parameter sends a Disconnect Request to the sync driver
when the YT timer expires.
4. SR Timer
This parameter determines the duration of the time that the
system will wait in command mode before returning to data
mode. The command mode is established when the user is
communicating with the remote Host; the data mode is
established when the user is communicating with the PAD.
Note that a value of 0 means that the timer is disabled.
5. YT Timer
This parameter defines the time of inactivity, in seconds, after
which the port will disconnect the X.25 session with the remote
port/device.
Note that a value of 0 (zero) means that the timer is disabled.
6. Port Prompt
This parameter allows the user to configure a message for a
particular port. For instance, “You are connected to port 5.”
7. SVC WAN DTE
This parameter allows the user to configure a point-to-point
WAN connection. This service is useful when a user wants to
connect to only one host. The options available are as follows:
• ATM
• FR DLCI
• FR Bundle
• IP Tunneling
14-261
CXTool User Guide
8. Hardware Flow Control
This parameter determines whether or not the hardware flow
control via the EIA Request to Send (RTS)/Clear to Send
(CTS) signal between the PAD and the start-stop mode DTE
(user) will be used.
Note that if this parameter is enabled, together with parameters
5 device and 12 flow in the X.3 Profile dialog box, then the
software flow control as defined in the aforementioned
parameters will take priority over hardware control.
9. WAN Connection
When this parameter is enabled, the user can proceed to
configure a point-to-multipoint WAN connection. This service is
useful when a user wants to connect to more than one host. The
options available are as follows:
• ATMVCL
• FR DLCI
• FR Bundle
• IP Tunneling
• X.25 Service Point
10. Reference Number
This parameter specifies a reference number that uniquely
identifies each instance of a protocol on this route.
11. Auto connect
When this parameter is enabled, the user can configure the AC
Timer and AC Retries parameters and connect automatically to
the DTE selected in the DTE Name parameter.
12. AC Timer
This parameter defines the time in seconds this async port will
wait before trying to connect to the remote DTE defined by the
14-262
DTE Name parameter whenever the port receives a Connect
Indication or Connect Confirm from the async driver.
13. AC Retries
This parameter defines the number of times this port will try to
connect to the remote DTE defined by the DTE Name
parameter whenever the port receives a Connect Indication or
Connect Confirm from the async driver. A value of '0' means
continuous retries.
14. DTE Name
This parameter identifies the remote DTE (by name) whenever
the port receives a Connect Indication or Connect Confirm
from the async driver. If no name is identified the Auto
Connect is disabled for this port.
15. Prot Type
This parameter determines the Async Protocol type for this
port. The options available are as follows:
• normal: use this option for the regular Async protocol (X.3,
X.28, X.29).
• iocProtocol: use this option for the IOC Protocol.
16. QoS Definition - Receive Throughput
This parameter determines the default Receive Throughput
class used by this port.
17. QoS Definition - Receive Packet Size
This parameter determines the size of the Receive Packet for
the Async driver.
Note that when transmitting Async traffic over an X.25 PVC,
the receive packet size is forced to the value of the transmit
packet size used by the associated destination port.
3008M300-004
 14 CONFIGURING ASYNCHRONOUS PAD

18. QoS Definition - Transmit Throughput 14.2.3 Configuring the X.3 Profile
This parameter determines the default Transmit Throughput
class used by this port. From the Async PAD folder, select the X3 Profile module and
click on the Add (+) button in the toolbar or select Add New
19. QoS Definition - Transmit Packet Size from the pull-down menu. The following screen appears:
This parameter defines the size of the Transmit Packet for the
Async driver.
20. QoS Definition - Transmit Window Size
This parameter defines the size of the Transmit Window for the
Async driver.

Figure 14-4: Configuring the X.3 Profile

Configure the parameters listed below.

1. Escape
This parameter defines the X.3 parameter 1, PAD recall using a
character. It allows the start-stop mode DTE (user) to initiate
an escape from the data transfer or the connection in progress

3008M300-004 14-263
CXTool User Guide

state in order to send PAD command signals. The range of available to the user are listed below, together with their
values available to the user are listed below, together with their meaning.
meaning.
• 0: No data forwarding character(s)
• 0: Not possible
• 1: Alphanumeric characters (A to Z, a to z and 0 to 9)
• 1: Character DLE
• 2: Character CR
2. Echo
• 4: Characters ESC, BEL, ENQ and ACK
This parameter defines the X.3 parameter 2, Echo. When
enabled, this port receives and transmits characters from the • 6: Characters CR, ESC, BEL, ENQ and ACK
start-stop mode DTE (user), which are then interpreted by the • 8: Characters DEL, CAN and DC2
PAD.
• 16: Characters ETX and EOT
3. Forward
• 18: Characters CR, ETX and EOT
This parameter defines the X.3 parameter 3, Selection of Data
Forwarding character(s). It allows the selection of defined sets • 32: Characters HT, LF, VT and FF
of characters received from the start-stop mode DTE (user) to • 64: All characters in columns 0 and 1 of IA5 except those
be recognized by the PAD as an indication to complete the shown for
assembly and forward a complete packet. The range of values values 2, 4, 8 and 32
• 126: All characters in columns 0 and 1 and character DEL
• 128: Character ETB
Note that some values are combinations of other values (i.e.,
value 18 is a combination of values 2 and 16).
4. Idle
This parameter defines the X.3 parameter 4, Selection of Idle
Timer Delay, in tenths of a second. It selects the duration of an
interval between successive characters received from the start-
stop mode DTE (user). When the interval is exceeded, the PAD
terminates the assembly of the packet and forwards it to the
async driver.
5. Device
This parameter defines the X.3 parameter 5, Ancillary Device
Control. This parameter allows for flow control between the
PAD and the start-stop mode DTE (user).

14-264 3008M300-004

6. Signals
This parameter defines the X.3 parameter 6, Control of PAD
service signals and PAD command signals. It provides the
start-stop mode DTE (user) with the ability to decide whether
or not and in what format PAD service signals are transmitted.
The range of values available to the user are listed below,
together with their meaning.
• 0: No PAD service signals are transmitted to the start-stop
mode DTE
• 1: PAD service signals are transmitted in the standard format
• 5: PAD service signals and prompt PAD service signal are
transmitted in the standard format
7. Break
This parameter defines the X.3 parameter 7, Selection of
operation of the PAD on receipt of a break signal from the
start-stop mode DTE. It allows the selection of the operation of
the PAD after the receipt of a break signal from the start-stop
mode DTE (user). The range of values available to the user are
listed below, together with their meaning.
• 0: Nothing
• 1: Interrupt
• 2: Reset
• 4: Send to DTE an indication of break PAD message
• 5: Interrupt and indication of break
• 8: Escape from data transfer state
• 16: Discard output, to start-stop mode DTE
• 21: Discard output, interrupt and indication of break
3008M300-004
14 CONFIGURING ASYNCHRONOUS PAD
8. Discard
This parameter defines the X.3 parameter 8, Discard output. It
provides for a PAD to discard the content of user sequences in
packets upon request rather than disassembling and
transmitting them to the start-stop mode DTE (user). The range
of values available to the user are listed below, together with
their meaning.
• 0: Normal data delivery
• 1: Discard output
9. CRpad
This parameter defines the X.3 parameter 9, Padding after
carriage return (CR). It provides for the automatic insertion of
padding characters by the PAD after a carriage return by the
DTE (user). This allows the printer of the DTE to perform the
carriage return function correctly. Note that a value of ‘0’
implies “No padding after CR.”
10. Folding
This parameter defines the X.3 parameter 10, Line folding. It
provides for the automatic insertion of graphic characters by
the PAD in the character stream transmitted to the start-stop
mode DTE (user). The predetermined maximum number of
graphic characters per line may be set. Note that a value of ‘0’
implies “No line folding.”
12. Flow
This parameter defines the X.3 parameter 12, Flow control of
the PAD. It allows for flow control between the start-stop mode
DTE (user) and the PAD. The range of values available to the
user are listed below, together with their meaning.
• 0: No use of X-ON (DC1) and X-OFF (DC3) for flow
control
• 1: Use of X-ON (DC1) and X-OFF (DC3) for flow control
14-265
CXTool User Guide
13. LFinsert
This parameter defines the X.3 parameter 13, Linefeed
insertion after carriage return. It allows for the automatic
insertion of a linefeed character in the character stream to and
from the start-stop DTE (user) or after each carriage return.
This parameter applies only in the data transfer state. The range
of values available to the user are listed below, together with
their meaning.:
• 0: No linefeed insertion
• 1: Insert linefeed after transmission of CR to the start-stop
mode DTE
• 2: Insert linefeed after each CR in the data stream from the
start-stop mode DTE
• 4: Insert linefeed after echo of CR to start-stop mode DTE
• 5: Insert linefeed after transmission to the start-stop mode
DTE and after echo of CR
• 6: Insert linefeed in data stream after CR from start-stop
mode DTE and after an echo of a CR to the start-stop mode
DTE
• 7: Insert linefeed in the data stream to and from the start-stop
mode DTE and after an echo of a CR to the start-stop mode
DTE
14. LFpad
This parameter defines the X.3 parameter 14, Padding after
linefeed. It provides for the automatic insertion of padding
characters in the character stream transmitted to the start-stop
mode DTE (user) after the occurrence of a linefeed character.
This allows the printer of the DTE to perform the linefeed
operation correctly. This parameter applies only in the data
transfer state. Note that a value of 0 (zero) means “No padding
after linefeed.”
14-266
15. Edit
This parameter defines the X.3 parameter 15, Editing. It
provides for character size delete, line delete and line display
editing capabilities in the PAD command state and the data
transfer state for the start-stop mode DTE (user). The range of
values available to the user are listed below, together with their
meaning.
• 0: No use of editing in the data transfer state
• 1: Use of editing in the data transfer state
16. Cdelete
This parameter defines the X.3 parameter 16, Character delete.
The options available are as follows:
• 0 to126: One character from IA5
• 127: Character 7/15 (DEL)
17. Ldelete
This parameter defines the X.3 parameter 17, Line delete. The
options available are as follows:
• 0 to 23: One character from the range of IA5
• 24: Character 1/8 (CAN)
• 25 to 127: One character from the range of IA5
18. Ldisplay
This parameter defines the X.3 parameter 18, Line display. The
options available are as follows:
• 0 to 17: One character from the range of IA5
• 18: Character 1/8 (DC2)
• 19 to 127: One character from the range of IA5
3008M300-004
 14 CONFIGURING ASYNCHRONOUS PAD

19. Esignals 21. Parity

This parameter defines the X.3 parameter 19, Editing PAD This parameter defines the X.3 parameter 21, Parity treatment.
service signals. It provides the start-stop mode DTE (user) with It allows the PAD to check parity in the data stream from the
the ability to decide whether or not editing PAD service signals start-stop mode DTE (user) or generate parity in the data
are transmitted and which format should be used. This stream to the DTE. The range of values together with their
parameter applies only in the data transfer state. The range of meanings are as follows:
values together with their meanings are as follows:
• 0: No parity checking or generation
• 0: No editing PAD service signals
• 1: Parity checking
• 1: Editing PAD service signals for printing terminals
• 2: Parity generation
• 2: Editing PAD service signals for display terminals
• 3: Parity checking and parity generation
• 8, 32 to 126: Editing PAD service signals using one
23. Parameter 23
character from the range of IA5
This parameter defines the X.3 parameter 23, Receive parity
20. Mask type. The range of values available to the user are listed below,
This parameter defines the X.3 parameter 20, Echo mask. It together with their meaning:
allows selected defined sets of characters received from the
• 1: Even parity
start-stop mode DTE (user) not to be transmitted back to the
DTE. The range of values available to the user are listed below, • 2: Odd parity
together with their meanings.
• 3: Space parity
• 0: No echo mask (all characters echoed)
• 4: Mark parity
• 1: No echo of CR
24. Parameter 24
• 2: No echo of LF This parameter defines the X.3 parameter 24, Transmit parity
• 4: No echo of VT, HT and FF type. The range of values available to the user are listed below,
together with their meaning:
• 8: No echo of BEL and BS
• 0: Parity disable
• 16: No echo of ESC and ENQ
• 1: Even parity
• 32: No echo of ACK, NAK, STX, SOH, EOT, ETB and ETX
• 2: Odd parity
• 64: No echo of editing characters as designated by
parameters 16, 17, and 18 • 3: Space parity

• 128: No echo of all other characters in columns 0 and 1 not • 4: Mark parity
mentioned above and DEL

3008M300-004 14-267
CXTool User Guide

25. Parameter 25 14.2.4 Configuring the SVC WAN DTE

This parameter defines the X.3 parameter 25, Flow control on
character to PAD. The range of values together with their From the Async PAD folder, select the SVC WAN DTE
meanings are as follows: module and click on the Add (+) button in the toolbar or select
Add New from the pull-down menu. The following screen
• 0 to 18: One character from the range of IA5 appears:
• 19: DC3
• 20 to 127: One character from the range of IA5
26. Parameter 26
This parameter defines the X.3 parameter 26, Flow control off
character to PAD. The range of values together with their
meanings are as follows:
• 0 to 16: One character from the range of IA5
• 17: DC1
• 18 to 127: One character from the range of IA5
27. Parameter 27
This parameter defines the X.3 parameter 27, Flow control on
character to ancillary device. The range of values together with
their meanings are as follows:
• 0 to 18: One character from the range of IA5
• 19: DC3
• 20 to 127: One character from the range of IA5
28. Parameter 28
This parameter defines the X.3 parameter 28, Flow control off Figure 14-5: Configuring the SVC WAN DTE
character to ancillary device. The range of values and their
meanings are: Configure the parameters listed below.

• 0 to 16: One character from the range of IA5

• 17: DC1
• 18 to 127: One character from the range of IA5

14-268 3008M300-004
 14 CONFIGURING ASYNCHRONOUS PAD

1. WAN Connection
This parameter allows a point-to-point WAN connection to be
configured. It is useful when a user wants to connect to only
one host. The options are:
• ATM
• FR DLCI
• FR Bundle
• IP Tunneling
2. Reference Number
This parameter allows numerous instances of the same protocol
to be configured. This number must be unique for each route
sharing the same destination circuit.

3008M300-004 14-269
CXTool User Guide

14-270 3008M300-004
 15 CONFIGURING X.25

This chapter describes how to configure X.25 services on a

Memotec CX product using CXTool. It begins with a
description of Memotec’s X.25 implementation in the CX
product family.

Users of this guide should have an understanding of X.25. A

review of some X.25 basics is offered in Chapter 30
INTRODUCING X.25.

3008M300-004 15-271
CXTool User Guide

15.1 Memotec’s CX Products and the X.25 • Support packet size from 16 to 4096

Environment • Switch packets

• Minimize congestion at any one port by prioritizing or
The X.25 module provides access and switching for IP, voice,
balancing logical link connections.
Frame Relay, SNA, Async and Bi-sync traffic. It also
configures Permanent Virtual Circuits (PVCs), Switched • LLC2 using X.25 over an Ethernet LAN
Virtual Circuits (SVCs), and pseudo PVCs using auto-connect.
Closed User Groups (CUGs) and hunting services are also • X.25 over an Ethernet LAN using LAP-B
provided.
PVC and SVC Memotec’s implementation of X.25 services allows users to
15.1.1 Supported X.25 Features Connections configure permanent or switched virtual circuits. PVCs may be
configured from an X.25 port to an X.25 Service Point or from
an X.25 port to another X.25 port, which is the case when a CX
Facilities Users of X.25 can take advantage of numerous capabilities that product is configured to provide switching services. SVCs may
it offers. Some of those implemented by CX products are listed be configured to route calls to an X.25 Service Point, an X.25
below. port, an X.25 logical link, or an X.25 hunt group.
• Provide throughput class negotiation
• Facilitate one-way logical channels (LCs) incoming or outgoing Link Levels At the X.25 Link level, the following are supported:
• Bar incoming or outgoing calls for closed user group (CUG) • LAPB, DTE or DCE; Modulo 8 or 128; Widow size 1 to 127,
subscribers and LAPD over ISDN-D

• Reverse charging and reverse charge acceptance At the X.25 Network Level, the following are supported:

• Provide local charge information • SVCs, PVCs, M, D, and Q bits

• Organize X.25 ports or X.25 Service Points in hunt groups The user can configure an X.25 interface as a DTE or a DCE.
• Provide fast select and fast select acceptance The next section illustrates some of the typical scenarios in
• Supply Network User Identification (NUI) numbers which Memotec devices can be used for X.25 services.

• Redirect calls
• Give an indication when there is a delay in transmission

15-272 3008M300-004
 15 CONFIGURING X.25

15.1.2 Typical X.25 Configuration Notice that in Figure 15-1 the cloud
IP showing three protocols (IP, Frame Relay,
This section illustrates how X.25 can be configured to carry and ATM) indicates that Memotec’s CX
voice, data, and async traffic across a PVC or an SVC ATM devices support all of the protocols, and the
connection. Note that in the examples below, those parameters Frame Relay
user may configure any one of them.
that are preconfigured by CXTool have not been mentioned.

In Figure 15-1, CX900e in Montreal has the following cards:

Configuring As shown in Figure 15-1, Memotec devices can be configured
a PVC to receive and carry multiple protocols. The configuration • V.24 (async driver)
Connection below shows a case of how voice, data, and async traffic may • Ethernet (LAN/IP)
be configured to go across an X.25 network.
• Analog Voice FXS (voice)
LAN
X.25 PAD (Calgary) IP For the purpose of illustration, the following is being assumed:
LAN
Vancouver
8000 ATM
Frame Relay 4545 CX950 1. async traffic from MtlTerminal1 in Montreal is going to Async
X.25
terminal in Calgary
Async Toronto 2. LAN traffic from Montreal is going to Calgary
Terminal X.25 PAD
8666 & Switch
3. voice traffic from telephone extension 2020 in Montreal is
nc

c
yn
y

As
As

PBX going to 5003 in Vancouver

X.25
In order for each protocol and the voice traffic to be transported
Extensions 5000 - 5999
from the CX900e to its respective destination, the CX900e
Main
Frame 2 configuration required is given below.
Main
Frame 1 Montreal
2000 CX900e
Configuring Voice
FXS 2540 LAN
2020
S 2535 • Voice Station: CPU on CX900e
FX

2021 • Voice Channel

MtlTerminal1 MtlTerminal2
Analog Voice FXS 2.1
Async Terminals
Local Extension: 2020

Figure 15-1: Configuring X.25 Services • DSP Channel

Analog Voice FXS 2.1
Vocoder Group: acelpII

3008M300-004 15-273
CXTool User Guide

• Dialing Plan: (digits dialed: 622 5003) • WAN Link

Dial Pattern: 6xx X.25 Service Point
Remote Extension: --- +++ X.25 Service Point Name: MtlLAN
Called Number: --- ++++ Local X.25 Address: 2540
Associated Routing Table: TableA
• WAN Trunk
X.25 Service Point Remote X.25 DTE Name: Calgary
X.25 Service Point Name: MtlVoice Service Type: IP
Local X.25 Address: 2020 Called Address: 8000
Associated Routing Table: TableA
Configuring Async Terminals
Remote X.25 DTE Name: Vancouver
• Port
Service Type: Voice
Called Address: 4545 Async Driver 3.1
X.25 Service Point
Voice Pattern: 500 (the compression parameters are X.25 Service Point Name: MtlAsync
configured automatically). This call will be routed Local X.25 Address: 2535
across the network based upon the pattern used in this Associated Routing Table: TableA
parameter, which should match that in the Remote
Extension parameter. Remote X.25 DTE Name: Calgary
Service Type: Async
• Signaling Called Address: 8666
CAS
Configuring X.25
Configuring LAN
• Port
• IP Port Port Name: ToNetwork
IP Address: 204.19.88.243 Sync Driver 4.1
Subnet Mask: 255.255.255.0 Associated Routing Table: TableA
Routing Protocol: RIP LAB Type: lapb
Logical Interface: DTE
• Link Type
Ethernet 1.1 • PVC
Source: X.25Port1; LCN: 1
Destination: X.25 Service Point (MtlVoice); LCN: 1

15-274 3008M300-004
 15 CONFIGURING X.25

In our example, CX950 in Ottawa is configured to provide

Source: X.25Port1; LCN: 2 switching and hunting services. It is equipped with a Universal
Destination: X.25 Service Point (MtlLAN); LCN: 1 I/O card which has 5 ports and a V.24. They are configured as
described below.
Source: X.25Port1; LCN: 3
Destination: X.25 Service Point (MtlAsync); LCN: 1 Configure X.25
• Port
Configuring With an SVC connection, the user can configure CX products Sync driver 1.1
an SVC for hunting and other services. Figure 15-2 and the Port Name: ToCalgary1
Connection configuration sequence following it illustrates the Link Type: Frame Relay (FRDLCI)
implementation of some of those services in a Memotec FRDLCI: 100
environment. Associated Route Table: TableA
LAP Type: LAPB
LAN
Logical Interface: DTE
FRAD (Calgary)
LAN Frame Relay
8000 Vancouver • Port
Ottawa CX950
8666

X.25
4545 Sync driver 1.1
CX950 Port Name: ToCalgary2
Async Switch
Terminal
Link Type: Frame Relay (FRDLCI)
X.25
X.25 FRDLCI: 200
PBX
Associated Route Table: TableA
LAP Type: LAPB
X.25 Logical Interface: DTE
Extensions 5000 - 5999
Main Main
• Port
Frame 1 Frame 2
Montreal Sync driver 1.2
1000

2530
CX900e
FXS 2540 LAN
Port Name: ToMain1
Ottawa
2020
2535
Link Type: Sync Port
S
FX Associated Route Table: TableA
2021 LAP Type: LAPB
Logical Interface: DTE
Async Terminals

Figure 15-2: Configuring X.25 SVC Services

3008M300-004 15-275
CXTool User Guide

• Port • Route call to Calgary1

Sync driver 1.3 X.25 Address (Called Address): 8000
Port Name: ToMain2 Route Call To X.25 Port: ToCalgary1
Link Type: Sync Port
Associated Route Table: TableA • Route call to Calgary2
LAP Type: LAPB X.25 Address (Called Address): 8666
Logical Interface: DTE Route Call To X.25 Port: ToCalgary2

• Port • Route call to Ottawa

Sync driver 1.4 X.25 Address (Called Address): 4000
Port Name: ToMontreal Route Call To X.25 Hunt: ToOttawa
Link Type: Sync Port
• Route call to Vancouver
Associated Route Table: TableA
LAP Type: LAPB X.25 Address (Called Address): 4545
Logical Interface: DTE Route Call To X.25 Port: ToVancouver

• Port • Route call to Montreal

Sync driver 1.5 X.25 Address (Called Address): 2XXX
Port Name: ToVancouver Route Call To X.25 Port: ToMontreal
Link Type: Sync Port
Associated Route Table: TableA The next section focuses primarily on how to configure X.25
LAP Type: LAPB services on Memotec devices with CXTool. It adheres to the
Logical Interface: DTE sequence in CXTool and provides a description of all the
parameters the user will encounter during configuration.
Configure the Hunting Service
• Hunt
Hunt Group Name: ToOttawa
15.2 Configuring X.25 with CXTool
Group Members Chosen: Main1 (Port 1.2) and Main2
The X.25 folder in CXTool contains all the modules/sub-
(Port 1.3)
modules and parameters associated with the X.25 protocol,
Configure SVCs including Station, Port, Service Point, SVC, Hunt, Closed User
Group, Logical Link, and Remote DTE.
The following examples show how the CX950 acts as a switch.

15-276 3008M300-004

15.2.1 Configuring the X.25 Station
From the X.25 folder, select the Station module and click on
the Add (+) button in the toolbar or select Add New from the
pull-down menu. The following screen appears:
2. Upper Queue Threshold
3. Routing Mask
Figure 15-3: Configuring the X.25 Station
Configure the parameters listed below.
1. Lower Queue Threshold
This parameter determines the minimum amount of system
resources required by the X.25 layer. When system resources
3008M300-004
15 CONFIGURING X.25
drop below this threshold, the X.25 layer clears any virtual
circuits for which data activity is detected.
The value of this parameter must not be greater than the value
stated in the Upper Queue Threshold parameter (see point 2,
next).
This parameter determines the amount of system resources
required by the X.25 layer to avoid congestion. When system
resources drop below this level, the X.25 layer does the
following:
• prohibits new virtual circuits from being established on a
port
• initiates flow control on all existing virtual circuits receiving
data (an RNR, Receiver Not Ready, is transmitted on each
circuit)
When global resources rise above this threshold after having
dropped below it, the X.25 layer does the following:
• it disables flow control on all suspended virtual circuits
(transmits a Receiver Ready (RR) on each circuit that it
previously transmitted an Receiver Not Ready (RNR) on)
• permits new virtual circuits to be established
The value of this object must not be less than the value of
Lower Queue Threshold (see point 1, above).
This parameter determines the number of digits to use for
routing calls. If set to value '0', calls are routed normally i.e.,
according to the called address specified. A value greater than
'0' indicates how many called address digits are used to scan
the route table. A call is refused when the called address
contains more or less digits than those specified for this
parameter.
15-277
CXTool User Guide
4. Network Type
This parameter determines the format of the cause codes the
X.25 layer adds to Reset, Restart, and Clear packets. Note that
the X.25 layer will not generate diagnostics packets for a
connection when this parameter is configured with value
'dteEndpoint'. The options available are the following:
• publicDataNetwork: standard cause codes are generated.
• privateDataNetwork: cause codes have the most significant
bit set.
• dteEndpoint: cause codes (with most significant bit set) are
only generated for ports configured as DCEs, and are set to 0
for ports configured as DTEs.
5. Hunt Group Rotation
When this parameter is enabled, hunting begins with a different
hunt group member each time. For example, a group with three
members would be hunted as follows: 123, 231, 312, 123.
Group members are rotated after each use or after detection of
a member that is unavailable.
6. Lap B/D Global Parameters - Lower Queue Threshold
This parameter determines the lower global resource threshold
(available buffer space), that when reached, causes the LAPB/
D layer to initiate flow control (transmission of RNRs). Thus if
resources are low, all links are affected.
The value set for this parameter must not exceed the value set
for the Upper Queue Threshold parameter (see point 7, next).
7. Lap B/D Global Parameters - Upper Queue Threshold
This parameter determines the upper global resource threshold
(available buffer space), that when reached, causes the LAPB/
D layer to cancel flow control.
The value set for this parameter must not be less than the value
set for the Lower Queue Threshold parameter.
15-278
8. System Route Connect Interval Timers - General Interface
Module
This parameter determines the number of seconds between
attempts to establish a connection for a X.25 system route. A
connection is attempted only for the defined non-connected
routes.
9. System Route Connect Interval Timers - Lap B Convergence
This parameter determines the number of seconds between
attempts to establish a connection for a LAPB system route. A
connection is attempted only for defined non-connected routes.
15.2.2 Configuring the X.25 Port
From the X.25 folder, select the Port module and click on Add
(+) button in the tool bar or select Add New from the pull-
down menu. The screen shown in Figure 15-4 appears.
Configure the parameters listed below.
1. Associated Routing Table
This parameter determines the X.25 Route Table that is
associated with this port.
2. Modulo
This parameter determines the range of sequence numbers
available for packet numbering for a given port. The modulo
specified for this object must match that specified on the
destination port for a route to be successful. If not, this
connection will refuse the call. The options available are as
follows:
• modulo8: sequence numbers range from 0 to 7, supporting a
maximum window size of 8.
• modulo128: sequence numbers range from 0 to 128, supporting
a maximum window size of 128
3008M300-004
 15 CONFIGURING X.25

3. Link - Look in
This parameter allows the user to configure a WAN
connections. The options available are as follows:
ATM
FR DLCI
IP Tunneling
ISDN Port
Sync Driver
4. Reference Number
This parameter specifies a reference number that uniquely
identifies each instance of a protocol on this route.
5. Back Plane Port
Put a check in this box to allow connection to the port of
another CPU through the backplane.
6. QoS Definition - Receive Throughput
This parameter determines the default receive throughput class
used by this port. This value is used only when throughput
class negotiation is not subscribed to, or when a D-bit call is
routed through this port.
7. QoS Definition - Receive Packet Size
This parameter determines the default receive packet size used
by this port. This value is used only when flow control
negotiation is not subscribed to, or when a D-bit call is routed
Figure 15-4: Configuring the X.25 Port (General Features) through this port.
8. QoS Definition - Receive Window Size
This parameter determines the default receive window size
used by this port This value is used only when flow control
negotiation is not subscribed to, or when a D-bit call is routed
through this port.

3008M300-004 15-279
CXTool User Guide

9. QoS Definition - Transmit Throughput

This parameter determines the default transmit throughput
class used by this port. This value is used only when
throughput class negotiation is not subscribed to, or when a D-
bit call is routed through this port.
10. QoS Definition - Transmit Packet Size
This parameter determines the default transmit packet size used
by this port This value is used only when flow control
negotiation is not subscribed to, or when a D-bit call is routed
through this port.
11. QoS Definition - Transmit Window Size
This parameter determines the default transmit window size
used by this port. This value is used only when flow control
negotiation is not subscribed to, or when a D-bit call is routed
through this port.

Configuring Within the X.25 Port dialog box, select LCN Allocation. The
LCN screen shown in Figure 15-5 appears.
Allocation
Configure the parameters as listed below. Notice that an LCN
of zero means "Don’t care." and the LCNs must respect the
following order:
• LCNs of outgoing VCs are greater than the LCNs for
two-way VCs
• LCNs of two-way VCs are greater than the LCNs for Figure 15-5: Configuring the LCN Allocation for X.25 Port
incoming VCs
• LCNs of incoming VCs are greater than the LCNs for PVCs 2. Permanent Virtual Circuit (PVC)
In this group box the highest and the lowest LCNs for PVCs on
1. Allocation Order this port are set. The range is zero to 4095. Zero has the special
This parameter determines the order (ascending or descending) meaning "Don’t care."
in which logical channel numbers (LCNs) are assigned for
SVC by this port.

15-280 3008M300-004
 15 CONFIGURING X.25

3. Two-Way Virtual Circuit (TVC)

In this group box the highest and the lowest LCNs that are
reserved for two-way virtual circuits at this port. The range is
zero to 4095. Zero has the special meaning "Don’t care."
4. Incoming Virtual Circuit
This parameter determines the highest and the lowest LCN for
incoming virtual circuits at this port. The range is zero to 4095.
Zero has the special meaning "Don’t care."
5. Outgoing Virtual Circuit (OVC)
This parameter determines the highest and lowest LCN for
outgoing virtual circuits at this port. The range is zero to 4095.
Zero has the special meaning "Don’t care."

Configuring Within the X.25 Port dialog box, select Facilities. The
Facilities following screen appears:

Figure 15-6: Configuring the Facilities Service (X.25 Port)

Configure the parameters as listed below.

1. Called Address Insertion
When this parameter is enabled, the called address is inserted
in the Call Accept packets at this port.
When this port receives a Call Accepted packet that contains a
called address, it verifies the address against the called address

3008M300-004 15-281
CXTool User Guide
contained in the Incoming Call packet. If they do not match,
the call is cleared.
When this port receives a Call Accepted packet that does not
contain a called address, the action it takes depends on the type
of route.
2. Calling Address Insertion
When this parameter is enabled, the calling address is inserted
in the Call Accept packets at this port.
When this port receives a Call Accepted packet that contains a
calling address, it verifies the address against the calling
address. If the two match, the call is cleared.
3. Packet Retransmission
When this parameter is enabled, it indicates that the user
subscribes to the Packet Retransmission service. This port
responds to reject packets by retransmitting all
unacknowledged data packets on the affected virtual circuit.
Copies of each data packets transmitted across all active virtual
circuits are maintained in anticipation of their rejection. The
copies are kept until they are acknowledged.
4. Incoming Calls Barred
When this parameter is enabled, it indicates that the user has
subscribed to the Incoming Calls Barred service. Assuming
that the X.25 port is configured as a DTE, this service allows
the user to originate virtual calls, but prevents the reception of
incoming calls.
5. Outgoing Calls Barred
When this parameter is enabled, it indicates that the user has
subscribed to the Outgoing Calls Barred service. Assuming
that the X.25 port is configured as a DTE, this service allows
the user to receive virtual calls, but prevents the user from
originating virtual calls.
15-282
6. Flow Control Parameter Navigation
When this parameter is enabled, it indicates that the user
subscribes to the Flow Control Parameter Negotiation service.
This allows negotiation of packet sizes and window sizes for all
incoming or outgoing calls.
With respect to incoming calls, the flow control facilities found
in incoming Call Request and Call Accept packets are not
altered.
With respect to the outgoing calls as well, the flow control
facilities found in outgoing Call Request and Call Accept
packets is not altered. If no flow control facilities are found at
this port, default settings are inserted into the Call Request or
Call Accept packets.
7. Throughput Class Negotiation
When this parameter is enabled, it indicates that the user has
subscribed to the Throughput Class Negotiation service. This
allows negotiation of performance characteristics for all
incoming or outgoing calls.
With respect to incoming calls, the throughput class facilities
found in incoming Call Request and Call Accept packets are
not altered.
With respect to outgoing calls too, the throughput class
facilities found in outgoing Call Request and Call Accept
packets are not altered. If the outgoing packet contain
throughput facilities they are compared against the settings for
this port and the lesser of the two is used. If no throughput class
facilities are found, this port inserts its default settings into the
Call Request or Call Accept packet.
8. Fast Select
When this parameter is enabled, it indicates that the user has
subscribed to the Fast Select service. It permits up to 128 bytes
of user data to be included in Call Request, Call Accept, and
Clear Request packets. The incoming calls at this port contains
3008M300-004

the fast select facility only if the destination side has subscribed
to the Fast Select Acceptance facility.
Note that this feature applies to outgoing calls only.
9. Fast Select Acceptance
When this parameter enabled, it indicates that the user has
subscribed to the Fast Select Acceptance service. A call
containing the fast select facility will only be routed here if the
inbound side subscribes to the fast select facility.
Note that this service applies to incoming calls only.
10. Reverse Charging Acceptance
When this parameter is enabled, it indicates that the user has
subscribed to the Reverse Charging Acceptance service. Note
that this facility applies to outgoing calls only.
11. Network User Identification
When this parameter is enabled, it indicates that the user has
subscribed to the Network User Identification (NUI) service. It
permits those incoming calls at this port that subscribe to the
NUI service. When such calls are established and are later
cleared, the billing information is inserted within the Clear
packet generated/received.
12. Local Charging Prevention
When this parameter is enabled, it indicates that the user has
subscribed to the Local Charging Prevention service. If an
incoming call contains neither the Reverse Charging, nor the
NUI facility, the Reverse Charging facility is added at this port
prior to routing the call to the outbound side, if the outbound
side has subscribed to the Reverse Charging facility. If the
outbound side has not subscribed to the Reverse Charging
facility, this call is refused.
Note that this facility applies to incoming calls only.
3008M300-004
15 CONFIGURING X.25
13. Charging Information
When this parameter is enabled, it indicates that the user has
subscribed to the Charging Information service. When such
calls that contain the Charging Information facility are
established and later cleared, the billing information about the
connection is inserted within the clear packet generated/
received. This is only done if the incoming call that established
the connection also contained the Charging Information facility
and if the port is configured as DCE.
Note that this facility applies to incoming calls only.
14. Permission To Redirect
When this parameter is enabled, it indicates that the user has
subscribed to the Permission to Redirect service. The incoming
calls are redirected to the address specified by the outgoing
side which refused the outgoing call. The redirection address is
only supplied by an outgoing side if it subscribes to the Call
Redirection facility, and is configured with a redirection
address.
Note that this facility applies to incoming calls only.
15. Call Redirection
When this parameter is enabled, it indicates that the user has
subscribed to the Call Redirection service. The outgoing calls
are redirected to the configured call redirection address only if:
• this outbound port is not available
• this outbound port is out of available LCNs
• incoming calls are barred at this outbound port (configured
as a DTE)
15-283
CXTool User Guide
• outgoing calls are barred at this outbound port (configured as
a DCE)
• the inbound side has subscribed to the Permission to
Redirect facility.
Note that this facility applies to outgoing calls only.
16. Calling Redirection Address - Redirection Address
This parameter determines the address of the port to which this
call is redirected. To make use of this address this port must
subscribe to the Call Redirection facility.
17. Calling Address Validation
When this parameter is enabled, it indicates that the user has
subscribed to the Calling Address Validation service. The
calling address is inserted into incoming call packets that do
not contain one, prior to routing the call. For incoming calls
that do contain a calling address, it is validated against the
specified address. If the addresses match, the incoming call is
routed, otherwise the incoming call is cleared.
Note that this facility applies to incoming calls only, and it can
be used for security purposes to restrict calls originating from a
specific source.
18. Calling Address Validation - Calling Address
When the user has subscribed to the Calling Address
Validation service this is the calling address used by the X.25
port. The called address is compared with the calling address.
If the two match, the call is accepted.
19. Transit Delay
This parameter enables the Transit Delay Timer service for a
particular virtual call.
20. Transit Delay - Transit Delay Timer (ms)
When Transit Delay is enabled, this parameter defines the
duration of the transit delay on outgoing and incoming calls.
15-284
21. Routing Mode
In this group box the user chooses one of the following routing
methods:
• Route on Call User Data Field
• Route on Sub-Address Field
• Route on Called Address Extension
Note that when no route is selected, calls will be routed using the
called address.
22. Route Mode group box - Call User Data Field
When this parameter is enabled, it indicates that the Call User
Data is used for routing a call. The digits in the Call User Data
field of incoming calls are used as the destination address for
routing.
Note that this facility applies to incoming calls only.
23. Routing Mode group box - Subaddress Field
When this parameter is enabled, it indicates that the
Subaddress Field is used for routing a call. The digits in the
called address of incoming calls are used as the destination
address for routing.
Note that this facility applies to incoming calls only.
24. Routing Mode group box - Called Address Extension
When this parameter is enabled, the Called Address Extension
facility of incoming calls is used as the destination address for
routing a call. The number of digits used for routing is
specified as part of the facility within the incoming call. If
enabled, an incoming call will be refused if the Called Address
Extension facility is not present.
25. Routing Mode group box - Route Address Length
When the Call User Data Field or the Subaddress Field is set,
then Route Address Length determines the number of digits
this SAP uses when incoming calls are routed.
3008M300-004
 15 CONFIGURING X.25

26. Closed User Group - Incoming Access Configuring Within the X.25 Port dialog box, select Timers. The following
When this parameter is enabled, it indicates that the user has Timers screen appears:
subscribed to the Closed User Group (CUG) with Incoming
Access service. If this port is part of a closed user group,
outgoing calls not containing the closed user group selection
facility (calls from the open network that are not part of any
CUG) are sent out to their destination.
Note that this facility applies to outgoing calls only.
27. Closed User Group - Outgoing Access
When this parameter is enabled, it indicates that the user has
subscribed to the CUG with Outgoing Access service. If this
port is part of a closed user group, incoming calls not
containing the closed user group selection facility (calls from
the open network which are not part of any CUG), are routed to
their destination.
Note that this facility applies to incoming calls only.
28. Preferred Index
When this SAP belongs to more than one Closed User Group
(CUG), this parameter determines the preferred CUG index. 0
(zero) means there is no preferred CUG.

Figure 15-7: Configuring the Timer Service (X.25 Port)

Configure the parameters listed below.

1. X.25 Timeout Waiting For - Restart Confirm (secs)
This parameter determines the maximum time that this connect
waits for a Restart Confirmation packet in response to a
previously sent Restart Request packet.

3008M300-004 15-285
CXTool User Guide
2. X.25 Timeout Waiting For - Call Connected (in secs)
This parameter determines the maximum amount of time this
port waits for a Call Connected packet in response to a
previously sent Call Request packet.
3. X.25 Timeout Waiting For - Reset Confirmation (secs)
This parameter determines the maximum amount of time this
port waits for a Reset Confirmation packet in response to a
previously sent Reset Request packet.
4. X.25 Timeout Waiting For - Clear Confirmation (secs)
This parameter determines the maximum amount of time this
port waits for a Clear Confirmation packet in response to a
previously sent Clear Request packet.
5. Virtual Circuit Control Timer - Queue Inactivity Reset (secs)
This parameter determines the maximum amount of time for
which this port can hold outbound queued data for a virtual
circuit. If this timer expires before the queued data can be sent,
the virtual circuit is reset. This is a global setting that applies to Configuring Within the X.25 Port dialog box, select the Extended tab. The
all virtual circuits established at this port
A value of '0' disables this timer.
6. Virtual Circuit Control Timer - Flow Control Check (secs)
This parameter determines the amount of time between checks
of available system resources when the virtual circuits at this
port have entered flow control. Flow control is initiated when
system resources have fallen below the value specified in the
Upper Queue Threshold parameter.
This timer is started when flow control is initiated, and when it
expires, system resources are rechecked. If resources have risen
above the value in the Upper Queue Threshold parameter, flow
control is terminated (a packet-level RR is issued on the
affected virtual circuit), otherwise the timer is restarted.
This is a global setting that applies to all virtual circuits
established at this port.
15-286
7. Virtual Circuit Control Timer - Window Status Timer
This parameter determines the maximum amount of time that
this port waits for an acknowledgment to be piggy-backed onto
an outgoing data packet. If this timer expires, it forces an
acknowledgment packet to be sent. This timer is restarted each
time a packet is sent.
8. Timeout With Data Link Layer - Connect (secs)
This parameter determines the maximum time that this port
waits for the sub-layer (typically the Data Link layer) to
establish the physical/logical line.
9. Timeout With Data Link Layer - Disconnect (secs)
This parameter determines the maximum time that this port
waits for the sub-layer (typically the Data Link layer) to
confirm that the physical/logical line has been taken down as
previously requested by this port.
Extended screen shown in Figure 15-8 appears.
Features
Configure the following parameters.
1. Logical Interface
This parameter determines the logical interface type of this
port: When the Lap Type parameter (in the LAP B dialog box)
is set to 'lapb', the user can set the Logical Interface type to a
DTE or a DCE, DTE being the user side and DTE being the
network side. When the LAP Type parameter is set to 'lapd',
DTE maps to user side and DCE maps to network side
automatically.
The network side is also known as the Assignment Source
Point (ASP) of all TEIs (terminal endpoint identifiers).
If the value of Lap B Protocol is set to v8022, then this
parameter is automatically set to a DTE. This value in this
3008M300-004
 15 CONFIGURING X.25

2. Activation Mode
This parameter determines the type of data link activation used
by this port. These are internal commands exchanged between
X.25 and the sub-layer.
The options available are as follows:
• normal: forces this port to attempt a connection to the sub-
layer immediately following a system reset, and periodically
thereafter until confirmed.
• dynamic: forces this port to attempt a connection to the
sub-layer only when an outgoing call is routed through this
port. Subsequently this port is disconnected from the sub-
layer after the last existing call routed through it has been
cleared.
• dynamic_30s_delay: forces this port to attempt a
connection to the sub-layer only when an outgoing call is
routed through this port. Subsequently a disconnection of
this port from the sub-layer is delayed, following the
clearing of the last existing call routed through this port. The
disconnect is delayed until 30 seconds have elapsed or until
a new call is received, whichever comes first.
• dynamic_60s_delay: forces this port to attempt a
connection to the sub-layer only when an outgoing call is
routed through this port. Subsequently a disconnection of
this port from the sub-layer is delayed, following the
clearing of the last existing call routed through this port. The
Figure 15-8: Configuring Extended Service of X.25 Port disconnect is delayed until 60 seconds have elapsed or until
a new call is received, whichever comes first.
parameter returns to its original value only when the Lap B
• dynamic_90s_delay: forces this port to attempt a
Protocol is set to 'standard'.
connection to the sub-layer only when an outgoing call is
The interface for ISDN-S/T is software and hardware routed through this port. Subsequently a disconnection of the
configurable. port from the sub-layer is delayed, following the clearing of
the last existing call routed through this port. The disconnect

3008M300-004 15-287
CXTool User Guide

is delayed until 90 seconds have elapsed or until a new call is 5. Routing Direction On Incoming Calls
received, whichever comes first. This parameter determines the direction in which incoming
• dynamic_120s_delay: forces this port to attempt a calls are routed. The options available are as follows:
connection to the sub-layer only when an outgoing call is • both: permits calls to be routed to outbound ports and
routed through this port. Subsequently a disconnection of the application ports
port from the sub-layer is delayed, following the clearing of
the last existing call routed through this port. The disconnect • upper: restricts the routing of calls to application ports only
is delayed until 120 seconds have elapsed or until a new call • lower: restricts the routing of calls to other outbound ports
is received, whichever comes first. only
3. Receive Window Threshold
Within the X.25 Port dialog box, click on the Next tab. The
This parameter determines the threshold at which this port is screen shown in Figure 15-9 appears.
forced to close its receive window (issue RNRs). This
threshold is only effective when the Receive Window settings
are as follows:
• if no receive window negotiation has taken place during the
call establishment phase, the threshold is effective if
configured to less than the value for the Receive Window
Size parameter.
• if the receive window has been negotiated to a value other
than its default, as specified by Receive Window Size
parameter, the threshold is only effective if configured less
than the negotiated value.
4. Link Type
This parameter determines the type of service provided by this
port. The options available are as follows:
• x25Link: this port provides support for the X.25 protocol
• x75Link: this port provides support for the X.75 protocol.
(For future use.)

15-288 3008M300-004

2. Active (Initiate Link)
3. Logical Interface
Figure 15-9: Configuring the X.25 Port (Continued)
Configure the parameters listed below.
4. Maximum Frame Size
1. Lap Type
This parameter determines the type of link access procedure
provided by this MAC port: LAPB or LAPD. It also determines
the number of data links that are automatically created and
associated with this port.
If the value of Lap B Protocol is set to 'v8022', then this
parameter is automatically set to a DTE. The value in this
3008M300-004
15 CONFIGURING X.25
parameter returns to its original value only when the Lap B
Protocol is set to 'standard'.
This parameter determines if the port initiates the link (active)
by sending a Set Asynchronous Balanced Mode (SABM) in the
case of LAPB or a Set Asynchronous Balanced Mode
Extended (SABME) in the case of LAPD to the other side.
Both sides can be active. However, typically the DCE side is
active and the DTE side is passive.
This parameter determines the logical interface type of this
connection: When the Lap Type parameter is set to 'lapb', the
user can set the Logical Interface type to a DTE or a DCE,
DTE being the user side and DTE being the network side.
When the LAP Type parameter is set to 'lapd', DTE maps to
user side and DCE maps to network side automatically.
The network side is also known as the Assignment Source
Point (ASP) of all TEIs (terminal endpoint identifiers).
If the value of Lap B Protocol is set to'v8022, then this
parameter is automatically set to a DTE. This value in this
parameter returns to its original value only when the Lap B
Protocol is set to 'standard'.
The interface for ISDN-S/T is software and hardware
configurable.
This parameter determines the maximum size of the LAPB/D
information field supported by this port. In other words, it is
the maximum number of bytes that can be passed through this
port in either direction (to the application or outbound ports).
Setting Lap B Protocol parameter to v8022 forces this
parameter to be set at 265.
15-289
CXTool User Guide
5. Maximum Retransmissions
This parameter determines the maximum number of attempts
made to successfully transfer a command frame (error
recovery) after the acknowledgment timer (t1t200) expires.
Known as N2.
6. Modulo
This parameter determines the range of sequence numbers
available for frame numbering at this port. The modulo limits
the size of the window to that set by the Window Size
parameter.
Setting LAPB Protocol parameter to v8022 forces this
parameter to be set at 128.
7. Window Size
This parameter determines the maximum number of
information frames that can be outstanding at any given time.
A frame is considered to be outstanding until the other side
acknowledges its receipt. This parameter supports modulo 8
and modulo 128 service.
Setting LAPB Protocol parameter to v8022 forces this
parameter to be set at 128, which affects the maximum setting
that can be made to this parameter.
8. LAPB Protocol
This parameter determines the LAPB protocol variant used by
this port. Setting this object to v8022 forces the following
changes:
• the Logical Interface is set to 'dte'
• the Modulo parameter is set to ‘128'
• the Maximum Size parameter is set to '521'
15-290
Once selected, these settings are locked. Only the restoration of
the LAPB Protocol parameter to 'standard' can unlock these
objects. The options available are as follows:
• standard: the standard LAPB protocol is used by this port
• v8022: the 802.2 variant of the LAPB protocol is used by
this port
9. MAC Window Size
This parameter determines the maximum number of frames
that can be outstanding at any given time to a sub-layer. A
frame is considered to be outstanding until its receipt is
acknowledged. This object controls the setting of internal
communications between layers. To control the actual window
size of the data link connection see the Window Size
parameter.
10. Timers - Response wait (T1) (100ms)
This parameter determines how long this port waits for a
response to a command frame before initiating error
recovery—known as the checkpoint timer (T1). The value set
for this object must be smaller than the value set for the Send
Acknowledge T2 parameter.
11. Timers - Send Acknowledge (T2) (100ms)
This parameter determines the period of time (T1) within
which this port must acknowledge a frame it has received.
This timer must always be less than the setting for T1 timer on
the remote side. Otherwise, the remote side will time out
before this port can respond.
12. Maximum Idle (T3) (100ms)
This parameter determines the maximum time for which this
port will allow the link to remain idle (no frames exchanged)
before sending a Receiver Ready (RR) poll to the other side—
known as idle probe timer (T3).
3008M300-004
 15 CONFIGURING X.25

13. Congestion Timer (100ms) reaches this value, the congestion timer is stopped and link
This parameter determines the maximum amount of time the status is set to not congested.
LAPB/D waits for the link to become uncongested before it Each data link connection through this MAC port, maintains its
terminates the link. own queue.
This timer is started when the number of frames queued for a
data link connection associated with this port reaches the 15.2.3 Configuring the X.25 Service Point
congestion threshold (Buffer Queue Upper Threshold).
This timer is stopped when the number of frames queued for a From the X.25 folder, select the Service Point module and click
data link connection reaches the congestion minimum (Buffer on Add (+) button in the tool bar or select Add New from the
Queue Lower Threshold). pull-down menu. The following screen appears:
If this timer expires, the data link connection is terminated.
14. Connect Timer (100ms)
This parameter determines the maximum amount of time that
the LAPB/D layer waits for a sub- layer to respond to a
connection request. If this timer expires before a response is
received, the connection is retried.
A positive response (connection confirmed) is only issued by
the sub-layer when the physical/logical line is active, otherwise
a negative response (disconnect indication) is issued.
15. Buffer Queue Upper Threshold
This parameter defines the threshold which declares a data link
connection on this MAC port to be congested. When the
number of frames in the queue for this data link connection
exceeds this value, the congestion timer is started and link
status is set to congested. If congestion has not cleared before
this timer expires, the link is dropped.
Each data link connection through this MAC port maintains its
own queue.
16. Buffer Queue Lower Threshold
This parameter defines the threshold which declares a data link
connection on this MAC port to no longer be congested. When
the number of frames in the queue for this data link connection Figure 15-10: Configuring the X.25 Service Point (General)

3008M300-004 15-291
CXTool User Guide

Configure the parameters listed below. negotiation is not subscribed to, or when a D-bit call is routed
through this port.
1. Local X.25 Address
This parameter determines the address of the local port.
2. QoS Definition - Receive Throughput
This parameter determines the default Receive Throughput
class used by this port. This value is used only when
throughput class negotiation is not subscribed to, or when a D-
bit call is routed through this port.
3. QoS Definition - Receive Packet Size
This parameter determines the default Receive Packet Size
used by this port. This value is used only when flow control
negotiation is not subscribed to, or when a D-bit call is routed
through this port.
4. QoS Definition - Receive Window Size
This parameter determines the default Receive Window Size
used by this port This value is used only when flow control
negotiation is not subscribed to, or when a D-bit call is routed
through this port.
5. QoS Definition - Transmit Throughput
This parameter determines the default Transmit Throughput
class used by this port. This value is used only when
throughput class negotiation is not subscribed to, or when a D-
bit call is routed through this port
6. QoS Definition - Transmit Packet Size
This parameter determines the default Transmit Packet Size
used by this port This value is used only when flow control
negotiation is not subscribed to, or when a D-bit call is routed
through this port.
7. QoS Definition - Transmit Window Size
This parameter determines the default Transmit Window Size
used by this port. This value is used only when flow control

15-292 3008M300-004
 15 CONFIGURING X.25

Configuring Within the X.25 Service Point dialog box, select LCN Configure the parameters listed below.
LCN Allocation. The screen shown in Figure 15-11 appears.
Allocation 1. Number of Two-Way LCNs
This parameter allows the user to configure the LCNs for
two-way virtual circuits at this port.
2. Number of PVC LCNs
This parameter allows the user to configure the number of
LCNs for PVCs established at this port.

Configuring Within the X.25 Service Point dialog box, select Facilities. The
Facilities screen shown in Figure 15-12 appears.

Configure the parameters listed below.

1. Incoming Calls Barred
When this parameter is enabled, it indicates that the user
subscribed to the Incoming Calls Barred service. Assuming
that the X.25 port is configured as a DTE, this service allows
the user to originate virtual calls, but prevents the reception of
incoming calls.
2. Fast Select
When this parameter is enabled, it indicates that the user has
subscribed to the Fast Select service. It permits up to 128 bytes
of user data to be included in Call Request, Call Accept, and
Clear Request packets. The incoming calls at this port contain
the fast select facility only if the destination side has subscribed
to the Fast Select Acceptance facility.
Note that this feature applies to outgoing calls only.
Figure 15-11: Configuring X.25 Service Point LCN Allocation 3. Fast Select Acceptance
When this parameter is enabled, it indicates that the user has
subscribed to the Fast Select Acceptance service. A call

3008M300-004 15-293
CXTool User Guide
4. Network User Identification
5. Charging Information
6. Permission To Redirect
Figure 15-12: Configuring the X.25 Service Point (Facilities)
containing the fast select facility will only be routed here if the
inbound side subscribes to the fast select facility.
Not that this service applies to incoming calls only.
15-294
When this parameter is enabled, it indicates that the user has
subscribed to the Network User Identification (NUI) service. It
permits the incoming calls at this port that subscribe to the NUI
service. When such calls are established and are later cleared,
the billing information is inserted within the Clear packet
generated/received.
Note that this facility applies to incoming calls only.
When this parameter is enabled, it indicates that the user has
subscribed to the Charging Information service. The incoming
calls containing the Charging Information facility. When such
calls that contain the Charging Information facility are
established and later cleared, the billing information about the
connection is inserted within the clear packet generated/
received. This is only done if the incoming call that established
the connection also contained the Charging Information facility
and if the port is configured as DCE.
Note that this facility applies to incoming calls only.
When this parameter is enabled, it indicates that the user has
subscribed to the Permission to Redirect service. The incoming
calls are redirected to the address specified by the outgoing
side which refused the outgoing call. The redirection address is
only supplied by an outgoing side if it subscribes to the Call
Redirection facility, and is configured with a redirection
address.
Note that this facility applies to incoming calls only.
3008M300-004

7. Call Redirection
When this parameter is enabled, it indicates that the user has
subscribed to the Call Redirection service. The outgoing calls
are redirected to the configured call redirection address only if:
• this outbound port is not available
• this outbound port is out of available LCNs
• incoming calls are barred at this outbound port (configured
as a DTE)
• outgoing calls are barred at this outbound port (configured as
a DCE)
• the inbound side has subscribed to the Permission to
Redirect facility
• Note that this facility applies to outgoing calls only.
8. Routing Mode
This parameter permits the user to use one of the following
routing methods:
• Call User Data Field
• Sub-Address
• Called Address Extension
9. Route Mode - Call User Data Field
When this parameter is enabled, it indicates that the Call User
Data is used for routing a call. The digits found in the call user
data field of incoming calls are used as the destination address
for routing.
Note that this facility applies to incoming calls only.
Configuring Within the X.25 Service Point dialog box, select Timers. The
10. Routing Mode - Subaddress Field
When this parameter is enabled, it indicates that the
Subaddress Field is used for routing a call. The digits found in
3008M300-004
15 CONFIGURING X.25
the called address of incoming calls are used as the destination
address for routing.
Note that this facility applies to incoming calls only.
11. Routing Mode - Called Address Extension
When this parameter is enabled, the Called Address Extension
facility of incoming calls is used as the destination address for
routing a call. The number of digits used for routing is
specified as part of the facility within the incoming call. An
incoming call will be refused if the Called Address Extension
facility is not present.
12. Closed User Group - Incoming Access
When this parameter is enabled, it indicates that the user has
subscribed to the Closed User Group with Incoming Access
service. If this port is part of a closed user group, outgoing calls
not containing the closed user group selection facility (calls
from the open network which are not part of any CUGs) are
sent out to their destination.
Note that this facility applies to outgoing calls only.
13. Closed User Group - Outgoing Access
When this parameter is enabled, it indicates that the user has
subscribed to the Closed User Group with Outgoing Access
service. If this port is part of a closed user group, incoming
calls not containing the closed user group selection Facility
(calls from the open network which are not part of any CUG),
are routed to their destination.
Note that this facility applies to outgoing calls only.
Timers screen shown in Figure 15-13 appears.
Configure the parameters listed below.
15-295
CXTool User Guide
15.2.4 Configuring PVCs
Figure 15-13: Configuring the X.25 Service Point (Timer)
1. X.25 Timeout Waiting For - Call connected (secs)
This parameter determines the maximum amount of time this
port waits for a Call Connected packet in response to a
previously sent Call Request packet.
15-296
2. X.25 Timeout Waiting For - Reset Confirmation (secs)
This parameter determines the maximum amount of time this
port waits for a Reset Confirmation packet in response to a
previously sent Reset Request packet.
3. X.25 Timeout Waiting For - Clear Confirmation (secs)
This parameter determines the maximum amount of time this
port waits for a Clear Confirmation packet in response to a
previously sent Clear Request packet.
4. Virtual Circuit Control Timer - Queue Inactivity Reset (secs)
This parameter determines the maximum amount of time for
which this port can hold outbound queued data for a virtual
circuit. If this timer expires before the queued data can be sent,
the virtual circuit is reset. This is a global setting that applies to
all virtual circuits established at this port
A value of '0' disables this timer
5. Virtual Circuit Control Timer - Window Status Timer
This parameter determines the maximum amount of time that
this port waits for an acknowledgment to be piggy-backed onto
an outgoing data packet. If this timer expires, it forces an
acknowledgment packet to be sent. This timer is restarted each
time a packet is sent.
From the X.25 folder, select the PVC module and click on the
Add (+) button in the tool bar or select Add New from the pull-
down menu. The screen shown in Figure 15-14 appears.
Configure the parameters as listed below.
1. Source - Look In
This parameter allows the user to select the source (X.25 port)
of a given connection.
3008M300-004

Figure 15-14: Configuring a Permanent Virtual Circuit
2. Source - LCN
This parameter determines the Logical Channel Number
(LCN) used by this PVC. The value of this parameter must be
the same as that in the Destination LCN parameter. The range
of allowed values is zero to 4095.
3008M300-004
15 CONFIGURING X.25
3. Source - Receive Packet Size
This parameter determines the receive packet size used by the
source port.
4. Source - Transmit Packet Size
This parameter determines the transmit packet size used by the
source port.
5. Destination- Look In
This parameter allows the user to configure the destination
(X.25 port or Service Point) of a given connection
6. Destination - LCN
This parameters determines the Logical Channel Number
(LCN) used by this PVC for the end point of a connection. The
value in this parameter must be the same as in the Source LCN
parameter. The range of allowed values is zero to 4095.
7. Destination - Receive Packet Size
This parameter determines the receive packet size used by the
destination port.
8. Destination - Transmit Packet Size
This parameter determines the transmit packet size used by the
destination port.
9. QoS Definition - Receive Throughput
This parameter determines the receive throughput class for the
external link. At the source side, it defines the throughput class
used for packets received from the source interface. At the
destination side, it defines the throughput class used for
packets transmitted to the destination interface.
10. QoS Definition - Receive Widow Size
This parameter determines the receive window size. At the
source side, it defines the window for packets received from
the source interface. At the destination side, it defines the
window for packets transmitted to the destination interface.
15-297
CXTool User Guide

11. QoS Definition - Transmit Throughput

This parameter determines the transmit throughput class across
the line. At the source side, it defines the throughput class used
for packets transmitted to the source interface. At the
destination side, it defines the throughput class used for
packets received from the destination interface.
12. QoS Definition - Transmit Window Size
This parameter determines the transmit window size. At the
source side, it defines the window for packets transmitted to the
source interface. At the destination side, it defines the window
for packets received from the destination interface.
13. Collect Billing Information
This parameter determines whether or not billing information
is collected for this PVC. Billing information can only be
collected for one or many outbound ports.
14. Collect Billing Information - Billing Source Address
This parameter determines the X.121 address that is associated
with the source side for billing purposes only.
15. Collect Billing Information - Billing Destination Address
This parameter determines the X.121 address that is associated
with the destination side for billing purposes only.

15.2.5 Configuring the SVC Route

From the X.25 folder, select the Routing Table (SVC) module
and click on Add (+) button in the tool bar or select Add New
from the pull-down menu. The screen shown in Figure 15-15
appears.
Configure the following parameters.
Figure 15-15: Configuring the X.25 SVC Routing Table
1. X.25 Address
This parameter determines the address of the called DTE that
triggers routing. If an incoming call is received at any
application port with this address, it is routed to the outbound
destination port.

15-298 3008M300-004
 15 CONFIGURING X.25

2. Route Table
This parameter allows the user to specify the X.25 Route Table
that is associated with this route entry.
3. Route Call To - Look in
This parameter allows the user to configure a destination for
this route. The options available are as follows:
• X25 Hunt
• X25 LL
• X25 Port
• X25 Service Point

15.2.6 Configuring the Hunt Service

From the X.25 folder, select the Hunt module and click the
Add (+) button or select Add New from the pull-down menu.
The screen shown in Figure 15-16 appears.

The X.25 Hunt dialog box allows the user to group specific
X.25 ports or service points within a hunt groups by simply
transferring them from the “Available” column to the “Chosen”
column. The call is received by the first available port or
service point within the hunt group.

15.2.7 Configuring the Closed User Group Service

CUGs provide the means to regulate incoming and outgoing
calls at particular ports. Generally, members of a CUG are
defined to only support making and receiving calls from other
members of the group. However, other options are available.
When a port belongs to more than one closed user group, a
preferential closed user group must be specified
Figure 15-16: Configuring the X.25 Hunt Service
To access this service, select the closed User Group module
from the X.25 folder, and click on Add (+) button in the tool
bar or select Add New from the pull-down menu. The screen
shown in Figure 15-17 appears.

3008M300-004 15-299
CXTool User Guide

2. Interlock Code
This parameter determines the CUG that a member belongs to.
The value in this parameter also represents the interlock code
used by the layer when translating index codes from one
member to another. Interlock codes must be unique at each
port.
3. Incoming Calls Barred
When this parameter is enabled, it indicates that this user has
subscribed to the Incoming Calls Barred with a Closed User
Group service. The subscribing member can originate virtual
calls to other members in this closed user group, but cannot
receive incoming calls from other members in this closed user
group.
4. Outgoing Calls Barred
When this parameter is enabled, it indicates that this user has
subscribed to the Outgoing Calls Barred with a Closed User
Group service. The subscribing member can receive virtual
calls from other members in this closed user group, but cannot
originate virtual calls to other members in this closed user
group.

15.2.8 Configuring the Logical Link Service

From the X.25 folder, select the Logical Link module and click
on Add (+) button in the tool bar or select Add New from the
pull-down menu. The screen shown in Figure 15-18 appears.
Figure 15-17: Configuring the X.25 Closed User Group
When the X.25 ports belong to a Logical Link group, the
Configure the following parameters.
incoming calls are received by the port that has the least
1. Member Name number of connections at any given moment.
This parameter allows the user to select X.25 ports or X.25
Service Points in order to include them within a member group.

15-300 3008M300-004
 15 CONFIGURING X.25

2. Routing Algorithm
This parameter determines the algorithm used by this logical
link to choose the port to route a call to. The value set for the
first member of a logical group overrides the settings for all
other members of the group. Therefore, if you want to change
the route algorithm for a group you need to alter the settings of
the first member only. The options available are as follows:
• balanced: the incoming calls are received by the port that has
the least number of connections at any given moment.
• prioritized: the first member is always chosen for routing.
The second is chosen if the first is not available
(disconnected or congested). The third is chosen if the first
and the second are not available, etc.

15.2.9 Configuring the Remote DTE Service

From the X.25 folder, select the Remote DTE module and click
on the Add (+) button in the tool bar or select Add New from
the pull-down menu. The screen shown in Figure 15-19
appears.

Now, configure the following parameters.

1. X3 Profile
This parameter defines the X.3 Profile number for a specific set
of X.3 parameters. The Async layer will initialize its port to
Figure 15-18: Configuring the X.25 Logical Link this X.3 Profile before establishing a logical connection for this
DTE entry. A value of '0' means no X.3 Profile.
Configure the following parameters. 2. DTE Name
1. X.25 Port This parameter identifies the DTE entry by a textual name.
The parameter allows the user to select the port through which Names are unique per Service Access Point. Note that the DTE
voice or data traffic will be routed. name must be preceded by a '.' (period) when used for X.28
with abbreviated address.

3008M300-004 15-301
CXTool User Guide

5. User Data
This parameter defines the user data field of the X.28
command for this DTE entry. A value of nul string (blank)
means no user data.
6. Facilities
The parameters in this section defines the facility codes and
parameters required for the X.28 Selection command for this
DTE entry. The facility codes and parameters must be entered
as defined in the CCITT X.28 Recommendation.
7. Facilities - NUI
This parameter allows the user to enter a NUI string.
8. Facilities - CUG
This parameter allows the user to enter a CUG index value.
9. Facilities - CUG with OA
When the user subscribes to the CUG with Outgoing Access
service, the DTE can belongs to one or more closed user
groups and originate virtual calls to DTEs in the open part of
the network (i.e., DTEs not belonging to any closed user
group) and to DTEs belonging to other CUGs with the
incoming access capability.
10. Facilities - Called address ext.
This parameter allows the user to configure the extension of the
destination DTE

Figure 15-19: Configuring the X.25 Remote DTE

11. Facilities - Charge request
When this parameter is enabled, charging information is
3. Service Type available to the user on a per call basis.
This parameter allows the user to select a service, e.g., async. 12. Facilities - Reverse charge
4. Called Address When this parameter is enabled, the Network can reverse the
This parameter defines the network address of a remote device charges of the incoming call to the user that is receiving the
for this DTE entry. call.

15-302 3008M300-004
 15 CONFIGURING X.25

13. Facilities - Fast select

When this parameter is enabled, it indicates that the user has
subscribed to the Fast Select service. It permits up to 128 bytes
of user data to be included in Call Request, Call Accept, and
Clear Request packets. The incoming calls at this port contains
the fast select facility only if the destination side has subscribed
to the Fast Select Acceptance facility.
Note that this feature applies to outgoing calls only.
14. Facilities - Fast Select with Restriction on Response
When this parameter is enabled, it allows the packet to contain
a user data field of up to 128 octets and authorizes the DCE to
transmit to the DTE.

15.2.10 LLC2 Using X.25 Over Ethernet LAN

From the X.25 folder, select the LLC XOE module and click
on the Add (+) button in the tool bar or select Add New from
the pull-down menu. The screen shown in Figure 15-20
appears.
1. Enter a Destination MAC Address in Hex. The Destination
MAC address should match the MAC address of the remote
LAN to which the LLC2 will be connected.
2. Normally the MAC address of the local LAN port is displayed
in the Local MAC Address box since it is dynamically returned
by the system. However, if a virtual MAC address is to be used
Figure 15-20: Configuring LLC2 Using X.25 Over Ethernet
then click to put a check in the Virtual MAC Address check
box and type the virtual MAC address in the box. easier to use a virtual MAC address instead of changing the
When each MAC address of a host has a small number of configuration of a host to accommodate a new device.
source interfaces and destination interfaces then using the When using IP, a virtual MAC address can be used to support
Virtual MAC Address feature makes sense. Also, it may be more than one IP network on the same physical port.
3. The Source SAP parameter contains the source LLC2 SAP
address of the connection. The default is 4, but another value

3008M300-004 15-303
CXTool User Guide

between 2 and 254 may be used. When a connection is to be 15.2.11 X.25 Over TCP Ethernet LAN Using LAPB
made with a Cisco device the value 126 is recommended.
From the X.25 folder, select the XOT module and click on the
4. The Destination SAP parameter contains the destination LLC
Add (+) button in the tool bar or select Add New from the pull-
SAP address of the connection. The default is 4, but another
down menu. The screen shown in Figure 15-22 appears.
value between 2 and 254 may be used. When a connection is to
be made with a Cisco device the value 126 is recommended.
5. Look in is a drop-down list box used to choose the type of link
that the LLC2 LAN port uses to transmit data.
When no driver links are displayed, click the Add button and
create one. If a driver link requires modification, select it then
click the Modify button and modify as required.
6. To enable source routing on this LLC2 SAP, click to put a
check mark in the Source Routing Network check box.
As shown in the diagram below, source routing must be
enabled on the CX unit for LLC2 traffic to be sent between the
hosts. The remote LAN card MAC address must be configured
and the most significant bit of the Local MAC Address set.
Even if the host is local, the Local MAC Address must still be
changed when this parameter is enabled.

X.25

CX950

Host Host

Figure 15-21: LLC2 Traffic Routed Across a Frame Relay LAN

7. Click Finish to implement the LLC2 SAP using X.25 over an

Ethernet LAN. Figure 15-22: Configuring X.25 Over TCP

1. The Station parameter is system generated and identifies the

X.25 station to be used in this configuration.

15-304 3008M300-004
 15 CONFIGURING X.25

When no stations are displayed, click the Add button and 6. The Mode drop-down list offers special features. The default is
create one. If a station requires modification, select it from the normal and this configuration is in accordance with RFC1613.
drop-down list then click the Modify button and modify it as In special circumstances the other selections may be
required. appropriate.
2. Name requires a unique name for this SAP to be entered. • keeplcn0 forces an X.25 Restart-Request to be sent to the
Remember that the first character must be an alpha character, peer
and spaces are not allowed. Up to 16 characters may be used.
• transparent allows non-X.25 traffic to be transported
3. The Destination Address parameter is the IP address of the
destination XOT device. The SAP establishes a TCP
connection to this remote IP address.
4. For Local Address, the system defaults to Listening on any
address and the local IP address is not required in the text box.
However, if Listening on any address is not checked the local
IP address must be entered in the text box. The SAP will create
a socket to listen to incoming TCP connections destined to this
local IP address and the port number defined below. The IP
address value is in dotted quad format.
To use an IP address, click the Add button and create one. If an
existing IP definition requires modification, select it from the
drop-down list then click the Modify button and modify it as
required.
5. The value of TCP Port Number assigns the destination port
number for this SAP TCP connection. The default is 1998,
which is the recommended value for an X.25 connection over
TCP.
The TCP Port Number is used to establish a socket connection
to the remote XOT device as well as to listen to any incoming
socket connections as determined in 4. above.

3008M300-004 15-305
CXTool User Guide

15-306 3008M300-004
 16 CONFIGURING IPX

This chapter begins with an overview of Memotec’s IPX

implementation within the CX product family. It is followed by
a detailed explanation of the configuration of IPX on CX
devices using CXTool.

Users of this guide should understand this protocol before

making changes to a system that implements IPX. A review of
IPX is provided in Chapter 31 INTRODUCING IPX.

3008M300-004 16-307
CXTool User Guide

16.1 Memotec’s CX Products and the IPX services is connected through a CX900e to the Frame Relay
network.
Environment
IPX Network 0x55667788 IPX Network 0x11223344
CX devices implement the IPX features identified in this
section.

Memotec’s implementation of IPX complies with Novell’s IPX

Version 3.X and 4.X.

16.1.1 IPX Routing Ethernet Ethernet

CX products route IPX over LAN and WAN services

including:
0x55667788 0x11223344
• Frame Relay (RFC 1490) 0xaabbccdd 0xaabbccdd

• Ethernet Frame Relay

• Token Ring
CX900e CX800
• ATM (RFC 1483) Figure 16-1: Configuring IPX Services

In Figure 16-1, both Memotec devices have the following

16.1.2 Typical IPX Configuration
cards:
This section describes typical IPX services that are possible • V.35H Serial, for the Frame Relay network
with Memotec devices. A list of parameters that must be
configured for those services is provided. • Ethernet, for the LAN network

Using Figure 16-1 as a point of reference, assume that users on

IPX Network 0x11223344 would like to access certain services
from the Novell server that belongs to IPX Network
0x55667788. The user’s network is connected through a
CX800 to the Frame Relay network. The network with the

16-308 3008M300-004
 16 CONFIGURING IPX

Configuring Configuring LAN Configuring WAN

CX800
• IPX Port1 • Sync Driver: 2.1 V.35H
• Network Number: 0x11223344 • Network Number: 0xaabbccdd
• Frame Type: raw_802.3 • Frame Relay DLCI: 100
• Spoofing: IPX Watch = On; SPX Watch = On; IPX Serial =
Configuring IPX Packet Handling
On
• Source Address: 0x55667788
• Driver: Port 1.1 Ethernet
• Destination Address: 0x11223344
Configuring WAN
• Handling: priority_low
• Sync Driver: 2.1 V.35H
IPX SAP Filter
• Network Number: 0xaabbccdd
• Service Type: Print Server (7)
• Spoofing: IPX Watch = On; SPX Watch = On
• Server Name: Novell
• Frame Relay DLCI: 100
• Handling: discard
Configuring IPX Packet Handling
The next section focuses primarily on how to configure IPX
• Source Address: 0x11223344
services on Memotec devices with CXTool. It adheres to the
• Destination Address: 0x55667788 sequence in CXTool and provides a description of all
parameters the user will encounter during configuration.
• Handling: priority_low

CX900e Configuring LAN 16.2 Configuring IPX with CXTool

• IPX Port1
The IPX folder in CXTool contains all the modules, sub-
• Network Number: 0x55667788
modules, and parameters associated with the IPX protocol,
• Frame Type: raw_802.3 including IPX Port, IPX Packet Handling, and IPX SAP Filter.
• Driver: Port 1.1 Ethernet
16.2.1 Configuring the IPX Port

From the IPX folder, select the Port module. To add an IPX
port, click on the Add (+) button in the tool bar or select Add

3008M300-004 16-309
CXTool User Guide

New from the pull-down Edit menu. The following screen 3. Look in
appears: This parameter allows the user to configure WAN services. The
options available are as follows: Ethernet, Token Ring, Frame
Relay, and ATM.
4. Reference Number
This parameter allows the user to identify multiple instance of
the same protocol by assigning the routing reference number
for data travelling through this convergence port and over this
circuit. Reference numbers are used by WAN service providers
that offer multiplexing to identify traffic from different sources
travelling over the same circuit. Each reference number on the
WAN circuit must be unique. The reference number is used in
the MPE header for RFC 1490 encapsulation.
5. Fragmentation Size
This parameter determines the maximum frame size supported
on this WAN circuit. In general, the default value is acceptable
for most configurations, since frame size is a negotiated value.
However, if you want to take advantage of WAN that supports
large data packets, increase the fragmentation size accordingly.
6. Frame Type
This parameter indicates the type of frame used for the IPX
header information. The framing format must correspond to the
Figure 16-2: Configuring the IPX Port requirements of the IPX destination address of each packet.
7. Transport Time (clock ticks)
Configure the following parameters:
This parameter allows the user to configure the clock timing.
1. Name One tick is 55 ms and it is the default for LANs.
This parameter allows the user to change the default name. It 8. SR Network
indicates the physical port that is bound to the IPX router port.
When this parameter is enabled, it indicates that the port
2. Network Number (hex) supports source routing (SR). The IPX route compiles a
This parameter indicates the IPX network number associated database that describes paths to all destinations on the SR
with the local IPX port. network. The router acquires this information from SR frames
it receives off the SR network which are destined for other

16-310 3008M300-004

remote locations. When the router needs to send a packet onto
the SR network, it consults the database and applies an SR
header to the packet, including route descriptors to the
destination.
9. Spoofing - IPX/SPX Watch
When spoofing is enabled, the router responds to watchdog
request packets on behalf of the WAN. It allows the WAN to
drop the physical link with the router when there is no traffic to
transmit. Without this capability, the WAN would incur
connection costs each time it received and replied to a
watchdog packet.
When IPX Watch and IPX Watch parameters are enabled, it
ensures that the IPX and SPX watchdog request packets are
sent at regular intervals by a server to verify if the connection
with the WAN is still active. If the WAN does not reply, the
server assumes that the connection is dead and terminates the
session. In order for this technique to be successful, the remote
WAN must also be configured to support IPX watchdog
spoofing.
10. Spoofing -IPX Serial
When this parameter is enabled, the router responds to IPX
serialization request packets on behalf of the LAN. It ensures
that the IPX serialization request packets are issued at regular
intervals by a server to exchange Novell software serial
numbers with the LAN device. The server uses this feature to
detect whether the LAN software is an illegal copy. If the LAN
fails to reply or if the LAN serial number is incorrect, the
server terminates the session.
11. Initial State
Each enabled port uses system resources, even if the port is
idle. Therefore, it is advisable to disable ports that are not
being used. A disabled port’s configuration is not deleted;
3008M300-004
16 CONFIGURING IPX
instead, the configuration is stored and the port can be re-
enabled without being reconfigured.
IPX Port - The remaining parameters in this module are advanced
Advanced functions. It is recommended that they not be modified. A
description of the advanced parameters is provided below
primarily for the purpose of information.
1. SAP - Periodic Broadcast
When SAP broadcasting is enabled, the network servers issue
broadcasts at regular intervals to advertise their services to
local devices. Routers (including Memotec devices) also
compile database records of all services they have learned
about through server broadcasts. The route propagates this
information on all the attached network in its own server
broadcasts.
This parameter must be set to Off on the WAN link that the user
does not want up, when Spoofing on a network (usually a
LAN) is enabled (i.e., set to On).
2. SAP - Timer
This parameter indicates the number of seconds between
periodic SAP
broadcasts. It needs to be configured only if the SAP- Periodic
Broadcast is set to On.
3. SAP - Reply
This parameter indicates whether or not the port is sending a
SAP broadcast in response to a SAP query from another router.
In addition to regular
broadcasts, servers can send SAP broadcasts in response to a
specific request. Such a request might be received if a new
device is initiated on the network in between regular
broadcasts.
16-311
CXTool User Guide

4. SAP - Aging Timer 9. Reply Diagnostic Request

This parameter indicates the number of seconds that an address This parameter determines whether or not the IPX port
can remain in the IPX port’s SAP database without being responds to diagnostic request packets received from other
updated. When this timer expires, the address is deleted from routers. Diagnostic request packets are issued periodically to
the SAP database. It can be re-entered if a new broadcast exchange address and version information between networks
confirms that the address is still active. and peers. This parameter should be disabled to avoid
unnecessary connection time costs which may be incurred if
5. RIP - Periodic Broadcast
the link is brought up only to exchange these periodic
Router use RIP broadcasts to exchange information contained messages.
in their routing tables. When this parameter is enabled, it
This parameter must be set to Off on the WAN link that the user
allows routers to dynamically update their data bases as new
does not want up, when Spoofing on a network (usually a
routes and destinations emerge or existing once are removed.
LAN) is enabled (i.e., set to On).
This parameter must be set to Off on the WAN link that the user
does not want up, when Spoofing on a network (usually a
LAN) is enabled (i.e., set to On). 16.2.2 Configuring IPX Packet Handling
6. RIP - Timer This module is used to handle packets that are received from a
This parameter indicates the number of seconds between specific source and sent to a specific destination. Each filtering
period RIP broadcasts. It needs to be configured only if the RIP entry includes a source address and a destination address.
- Periodic Broadcast is set to On.
In the IPX folder, click on the Packet Handling module. The
7. RIP - Reply
following screen appears:
This parameter indicates whether or not the port is sending RIP
broadcasts in response to RIP query from another router. In
addition to regular
broadcasts, servers can send RIP broadcasts in response to a
specific request. Such a request might be received if a new
device is initiated on the network in between regular
broadcasts.
8. RIP - Aging Timer
This parameter indicates the number of seconds that an address
can remain in the IPX port’s RIP database without being
updated. When this timer expires, the address is deleted from
the RIP database. It can be re-entered if a new broadcast
confirms that the address is still active

16-312 3008M300-004
 16 CONFIGURING IPX

and destination for the destination address. The options

available are as follows:
• discard: indicates that all packets from the specified source
to the specified destination are discarded.
• forward: indicates that the packets from the specified source
to the specified destination are forwarded with normal
priority. These packets are not placed into a special
transmission queue and receive no special treatment.
• priority_low: indicates that all packets from the specified
source to the specified destination are placed in the low
priority queue. The data is transmitted only when higher
priority queues are empty.
• priority_high: indicates that all packets from the specified
source to the specified destination are placed in the high
priority queue. The data is transmitted before all other
normal priority and low priority data.

16.2.3 Configuring IPX SAP Filters

An IPX SAP filter is composed of a service type and a server

Figure 16-3: Configuring the IPX Packet Handling
name. Each definition is compared against all service
Configure the following parameters: broadcasts received by the router. An IPX SAP filter controls
which SAP services the router accepts and advertises, and
1. Source Addresses which response messages it sends out.
This parameter indicates the source IPX address to which the
filtering or forwarding information applies. In the IPX folder, click on the SAP filter module and the
following screen will
2. Destination Address
This parameter indicates the destination IPX address to which
the filtering or forwarding information applies.
3. Handling
This parameter determines the filtering or forwarding action to
be applied to packets that are received from the source address

3008M300-004 16-313
CXTool User Guide

appear: 2. Server Name

This parameter determines the textual name of the Novell
server that is used in this filter.
3. Handling
This parameter determines whether or not the filter is enabled.
When the option “nodiscard” is selected, this parameter
disables individual filters without deleting them. If a filter is
not required for a period of time, it is a good idea to disable it
to prevent problems and to free up system resources. The filter
can later be re-enabled when it is needed by selecting
“discard”.

Figure 16-4: Configuring the IPX SAP Filter

Configure the following parameters:

1. Service Type
This parameter determines the IPX service type that is
examined by the filter. The service type works with the server
name to identify information that should be excluded from the
router’s SAP database. Service type identifiers are defined by
Novell.

16-314 3008M300-004
 17 CONFIGURING MLPPP

This chapter describes how to configure Multilink Point to

Point Protocol (MLPPP) on a Memotec CX device using
CXTool.

Users of this guide should have an understanding of this

protocol. Before advancing to the procedures it may be helpful
to review some MLPPP basics, which are provided in
Chapter 32 INTRODUCING MLPPP.

3008M300-004 17-315
CXTool User Guide
17.1 Memotec’s CX Products and the MLPPP
Environment
MLPPP has several noteworthy features. Memotec devices
implement the features described below.
Inverse Multiplexing
Inverse multiplexing is the process of merging several links
into a single pipe. It is accomplished by encapsulating a frame
into an MLPPP packet. MLPPP adds a protocol ID and
sequencing information to each frame.
Inverse multiplexing can be performed across almost any
physical or logical interface, the possible interfaces include
V.24, V.35, V.34 dial, ISDN B channel, Frame Relay ports and
Frame Relay DLCIs.
Load Balancing
When inverse multiplexing, MLPPP measures the round trip
delay of each link to make load balancing decisions. Links with
higher data speeds will therefore be used more often.
Bandwidth on Demand
This feature is also known as “dial on congestion.” Dial ports
are used to provide additional bandwidth when congestion
occurs.
If the bandwidth that is in use is greater than the configured
bandwidth threshold, MLPPP will start connecting new links to
reduce congestion. If the bandwidth in use drops below the
configured bandwidth threshold by at least 10%, then MLPPP
will start disconnecting links. If the bandwidth threshold is set
to a value of 10% or less, a link will not be disconnected once it
has been established.
17-316
Fault tolerance
MLPPP is able to handle the failure of one or more links in a
bundle. By default, the dial port will be used if all the links
have failed or congestion has reached 85%. Note that a high
congestion level percentage will prevent a dial backup link
from being established until required.
PPP Support
The multi link portion of MLPPP is disabled when only one
link in a bundle is being used, which could be an async PPP,
synchronous PPP, or Frame Relay PPP.
17.2 Configuring MLPPP with CXTool
The MLPPP folder in CXTool contains all the modules/sub-
modules and parameters associated with this protocol,
including port and bundle.
17.2.1 Configuring the MLPPP Port
MLPPP port entries are used to group interfaces together for
the purpose of multi-linking. Note that a single entry will
perform PPP only.
From the MLPPP folder, select the Port module. Click on the
Add (+) button in the tool bar or select Add New from the pull-
down Edit menu, and the following screen appears:
3008M300-004
 17 CONFIGURING MLPPP

NOTE: If “ISDN Service Point” is selected the user can

configure the ISDN link as the primary or the
secondary link. If it is the secondary link, the user
should configure ISDN as a “back up” service by
clicking on the Dial tab. To configure the ISDN as a
“back up” service, refer to Chapter 9 CONFIGURING
FRAME RELAY, section 9.2.1 Configuring a Frame
Relay Port.

3. Multilink Rules
When two or more ports are bundled, this parameter is enabled
automatically indicating that the bundle was created using
inherent rules for the following parameters:
• Async Control Character Map 0x
• Disable Compressed Protocol Field
• Disable Compressed Addr/Control Field
• Disable Magic Number
When this parameter is disabled, the user can configure the
above-mentioned parameters as desired.

Figure 17-1: Configuring the MLPPP Port 4. Max Receive Unit (MRU)
This parameter determines the MRU proposed by this
Configure the parameters as listed below. connection. This proposed MRU is negotiated with the
1. Port Name remote's proposed MRU. If the value in this parameter is set to
0, then no negotiation will occur with the remote, and the
This parameter allows the user to change the default name.
default MRU of 1500 octets is used. If this value is not 0, then
2. Link the local PPP link will negotiate for this value with the remote
This parameter allows the configure a frame relay, peer.
synchronous, or an ISDN port. 5. Max Configure-Request packets
This parameter determines the maximum number of
Configure-Request packets that the port can send without any
acknowledgment from the peer. The user will rarely need to

3008M300-004 17-317
CXTool User Guide
change the default value. If the maximum number of packets
has been sent and there is still no response from the other end
of the link, the Link Control Protocol (LCP) assumes that the
peer is unable to respond and that the link cannot be
established.
6. Max Termination-Request packets
This parameter determines the maximum number of
Termination-Request packets that the port can send without
any answer from the peer. The user will rarely need to change
the default value. If the maximum number of packets has been
sent and there is still no response from the other end of the link,
the Link Control Protocol (LCP) assumes that the peer is
unable to respond. The link is closed without negotiating the
termination.
7. Max Fail Packets
This parameter determines the maximum number of
Configure-Not-Acknowledge packets which can be sent
without receipt of a Configure-Acknowledge packet. The user
will rarely need to change the default value. A Configure-
Acknowledge packet is sent to confirm acceptance of a
configuration parameter proposed by the peer. A Configure-
Not-Acknowledge packet means that the peer does not accept
the proposal. If the maximum number is exceeded, the link is
closed down. This prevents endless loops in the configuration
process.
8. Restart Timer
This parameter determines the number of seconds between the
sending of a Configure-Request or Terminate-Request packet,
and the time before its retransmission if no acknowledgment is
received. The user will rarely need to change the default value.
The packet is retransmitted up to the maximum number
permitted in the “Max Configure_Request packets” parameter.
17-318
9. Asynchronous Control Character Map 0x
This parameter determines the Asynchronous Control
Character Map (ACC) that the local PPP link proposes for use
on its transmit side. The ACC proposed by the local side is
negotiated with that proposed by the remote side.
The ACC Map maps the first 32 ASCII control characters
(numbered 0 to 31). The map allows datagrams traveling over a
PPP link to be transparent to all intermediate devices such as
modems.
This value is a string of four octets, or 32 bits. Position
numbers (0-31) correspond to the first 32 control characters.
For example, if bit 19 is set to 1, then the ASCII control
character 19 (ctrl-s) is sent transparently.
Note that the value in this parameter should be cleared when
Multilink is used (value: 00 00 00 00). It is rare that the user
will need to change this value.
10. Disable Compressed Protocol Field
This parameter determines whether or not this port can receive
packets with a compressed PPP Protocol Field.
If enabled, the port informs its peer that it can receive packets
with a compressed PPP Protocol Field (when the configuration
of the PPP link is negotiated).
Note that this parameter should be enabled when Multilink is
used.
11. Disable Compressed Addr./Control Field
This parameter determines whether or not this port can receive
packets with compressed PPP Address and Control Fields.
If enabled, the port informs its peer that it can receive packets
with a compressed PPP Address and Control Field when the
configuration of the PPP link is negotiated.
Note that this parameter should be enabled when Multilink is
used.
3008M300-004
 17 CONFIGURING MLPPP

12. Disable Magic Number appears:

This parameter determines whether or not the Magic Number
is enabled.
The Magic Number is a unique random system generated
number that is present in every Configure-Request packet. The
Magic Number is used to ensure that the same packet is not
sent back and forth between the local and the remote in an
endless loop.
If this parameter is enabled, then the local end of the link will
check the Magic Number in each Configure-Request packet it
receives.
If the number is the same as its own, it will change its number
and send a NoAcknowledge packet back to the remote. If the
local end of the link continues to receive Configure-Requests
with its own number, it assumes a loopback.
Note that this parameter should be disabled when Multilink is
used.

17.2.2 Configuring the MLPPP Bundle

MLPPP bundle is used to define additional parameters for a

multilink port or group.

From the MLPPP folder, select the Bundle module. Click on
the Add (+) button in the tool bar or select Add New from the
pull-down Edit menu, and the following screen
Figure 17-2: Configuring the MLPPP Bundle
Configure the parameters as mentioned below.
1. Bundle Name
The parameter allows the user to accept the default name or to
configure another one.
2. Bandwidth Allocation Threshold
This parameter determines the bandwidth allocation threshold
value as a percentage (%) of the current maximum bandwidth
for a particular connection. If the current bandwidth in use is

3008M300-004 17-319
CXTool User Guide

greater than this threshold, MLPPP will start connecting new multiplexing takes place. This means that each message
links. If the bandwidth in use drops more than 10% under this received is sent out on a different MLPPP connection and no
threshold, this port will start disconnecting links. If the fragmentation or resequencing is done. The user will rarely
threshold is set to 10% or less, new links will not be need to change the default value.
disconnected, once they are already established.
7. Disable Bandwidth Allocation Control Protocol (BACP)
3. Maximum Receive Reconstructed Unit This parameter determines the bandwidth capabilities of a
This parameter determines the MRU proposed by this bundle by dynamically adding/removing its dial-on-demand
connection. This proposed MRU is negotiated with the member links (V.34 or ISDN). If Bandwidth Allocation
remote's proposed MRU. If the value in this parameter is set to Control Protocol (BACP) is enabled, the call initiator and the
0, then no negotiation will occur with the remote, and the peer will negotiate the bandwidth allocation.
default MRU of 1500 octets is used. If this value is not 0, then
8. Bundle
the local PPP link will negotiate for this value with the remote
peer. This parameter allows the user to select an MLPPP port for
configuration.
4. Transmit Window Size
This parameter determines the size of the transmit window for
this MLPPP. This window is the maximum number of buffers
queued by MLPPP before it starts to discard frames. The
current window size reflects the configured value in the
MLPPP. This value may vary depending on the amount of
buffers queued for transmission.
5. Disable Compressed Sequence Number Field
This parameter determines whether the Sequence Number
Field is compressed or not. If the Sequence Number Field is
compressed, then the short sequence number header format is
used and sequence numbers are 12 bits long. If the Sequence
Number Field is not compressed, then the long sequence
number header format is used and sequence numbers are 24
bits long.
6. Disable Inverse Multiplexing
This parameter determines the current use of MLPPP. If the
value in this parameter is enabled, MLPPP performs inverse
multiplexing. In inverse multiplexing fragmentation and re-
sequencing takes place. If this parameter is disabled, dumb

17-320 3008M300-004
 18 CONFIGURING BRIDGING

This chapter describes how to configure a bridge on Memotec

CX product using CXTool.

It is important to have an understanding of how a bridge works

before advancing to the procedures. A review of Chapter 33
INTRODUCING BRIDGES provides the basics.

3008M300-004 18-321
CXTool User Guide

18.1 Memotec’s CX Family and the Bridge For the CX950 (A) to forward the Ethernet data, the following
configuration is required.
Environment
Configuring STP Port1
Memotec devices use the spanning tree protocol (STP) and Fast Ethernet: 1.1
source routing (SR) on all bridge ports.
Handling: forward
The following subsections give an idea of the typical bridging Initial State: On
configurations that are possible with CXTool.
Configuring SNMP

18.1.1 Typical Bridging Configuration • SNMP Support: enabled

• IP Address: 192.168.1.1
The following examples illustrate the most common use of
Ethernet and Token Ring bridging. • Netmask: 255.255.255.0

Configuring STP Port2

Configuring Using Figure 18-1 as a point of reference, let us assume that • Frame Relay: V.35H Sync Driver 2.1
Ethernet STP CX950 (A) is configured for broadcasting Ethernet data, and it
has the following cards: • DLCI: 100

1. V.35H (for Frame Relay) • Handling: forward

2. Fast Ethernet (for LAN traffic) • Initial State: On

Notice that when the Ethernet port is associated with an IP

Ethernet
address, the Port State will read: 3.
CX950 (A)
192.168.1.2 NOTE: For the purposes of this example, the CX950 (B) is
Frame assumed to be correctly configured.
Relay
192.168.1.1
CX950 (B)

Configuring Using Figure 18-2 as a point of reference, let us assume that

Ethernet
Token Ring CX950 (A) is configured to provide Token Ring service, and
Source has the following cards:
Routing
Figure 18-1: Ethernet STP Bridging

18-322 3008M300-004
 18 CONFIGURING BRIDGING

1. Token Ring (for Token Ring traffic) Configuring Source Routing Port2
2. V.35H (for Frame Relay) • Frame Relay Port Sync Driver 2.1, V.35H
• Frame Relay DLCI: 100
Token
Ring • Segment: 2
199.188.1.2 Segment 3 • Handling: forward
CX950 (A) Segment 2
Frame
Segment 2
CX950 (B)
• Initial State: On
Relay

199.188.1.3
Segment 1 NOTE: For the purposes of this example, the CX950 (B) is
assumed to be correctly configured.
Token
Ring

The next section focuses primarily on how to configure

bridging services on Memotec devices with CXTool. It adheres
Figure 18-2: Token Ring Source Routing Bridging
to the sequence in CXTool and provides a description of all the
In order for the CX950 (A) to provide Token Ring service, the parameters the user will encounter during configuration.
configuration required is given below.

Configuring Source Route Port1 18.2 Configuring Bridging with CXTool

• Token Ring 1.1
The Bridge folder in CXTool contains all the modules/sub-
• Segment: 1
modules and parameters associated with this protocol,
• Port Speed: 16 mbps including Bridge Station, Source Routing Port, and Spanning
Tree Port.
• Handling: forward
• Initial State: On
18.2.1 Configuring the Bridge Station

From the Bridge folder, select the Station module. Click on the
Add (+) button in the tool bar or select Add New from the pull-
down Edit menu, and the screen shown in Figure 18-3 appears.

3008M300-004 18-323
CXTool User Guide
2. STP - Hello Time
Figure 18-3: Configuring the Bridge Station
3. STP - Max Age
Configure the parameters as described below.
1. STP - Priority
This parameter determines the first two octets of the bridge
identifier. The remaining six octets of the identifier are the
bridge's MAC address. The spanning tree algorithm maintains
effective communication routes by forcing a tree structure on
the network topology. This practice avoids the formation of
communication loops in the connection information stored by
each bridge. The bridge with the lowest bridge identifier
becomes the root bridge in the tree. Each bridge calculates the
cost of transmissions from itself to the root. When multiple
18-324
bridges connect the same LAN to the root bridge, the bridge
with the lowest cost becomes the designated bridge for the
LAN. Other ports on the LAN that lead to the root bridge are
disabled. STP recalculates the spanning tree each time a bridge
is added to or removed from the network. It should rarely be
necessary to change this parameter's default value. Note that a
higher priority number makes it less likely that this bridge will
be the root bridge of the spanning tree.
This parameter determines the value that all bridges use for
measuring the length of time between the transmission of
configuration bridge protocol data units (BPDUs) when this
bridge is the root bridge. Configuration BPDUs are sent by the
root bridge in the spanning tree to the designated bridge on
each LAN. The designated bridge repeats the configuration
BPDU information to other bridges on the same LAN. These
protocol messages confirm that bridges are still alive. If the
value in the Max Age parameter expires before a new
configuration BPDU arrives, the sending bridge is assumed to
be dead. This situation triggers a recalculation of the spanning
tree. All bridges in the spanning tree use the same hello time.
The hello time is learned from the root bridge.
This parameter determines the value that all bridges in the
spanning tree use to indicate the length of time that
configuration bridge protocol data units (BPDUs) are stored
before being discarded, when this bridge is the root bridge. The
root bridge in the spanning tree issues configuration BPDUs at
regular intervals. These protocol messages are received by the
designated bridge on each LAN. The designated bridge repeats
the configuration BPDU information to other routers on the
same LAN. These messages confirm that bridges are still alive.
Bridges reset their Max Age timers to '0' each time a BPDU
arrives. If a bridge fails to receive a configuration BPDU before
3008M300-004
 18 CONFIGURING BRIDGING

the timer expires, the sending bridge is assumed to be dead. appears:

This situation triggers a recalculation of the spanning tree. All
bridges in the spanning tree use the same Max Age. This value
is learned from the root bridge.
4. STP - Forward Delay
This parameter indicates the number of seconds that the
bridge's ports remain in the listening and learning states before
reaching the forwarding state. All bridges in the spanning tree
use the same Forward Delay value. This setting is specified by
the root bridge in the tree.
5. Transparent - Aging Time
This parameter indicates the duration for which an entry can
remain unused in the FDB before being deleted.
6. Transparent - Max Entries in Forwarding Table
This parameter indicates the size of the FDB.
The forwarding database stores destination addresses and
access routes. When the bridge receives a frame, the bridge
checks its forwarding database for information about which
port to use to reach the frame's destination. If the destination is
not listed, the bridge broadcasts the frame on all bridge ports
except the port through which the frame was received.
The default value for this parameter should be sufficient for
most small and medium-sized networks. If the user has a very Figure 18-4: Configuring the Source Routing Port
large network, the number of database entries will need to be
increased, given that the bridge will need to support a larger Configure the parameters as described below.
number of destinations. 1. Name
This parameter allows the user to change the default name.
18.2.2 Configuring the Source Routing Port

From the Bridge folder, select the Source Routing Port module.
Click on the Add (+) button in the tool bar or select Add New
from the pull-down Edit menu, and the following screen

3008M300-004 18-325
CXTool User Guide
2. Link
This parameter allows the user to configure one of the
following links:
• ATM VCL
• FR Bundle
• FR DLCI
• Token Ring Driver
3. Link - Reference Number
This parameter determines the routing reference number for
data travelling through this convergence port and over this
circuit.
Reference numbers are used by WAN service providers that
offer multiplexing. Multiplexing allows data from different
sources to be transmitted over the same WAN circuit, thereby
sharing bandwidth and reducing overall connection costs for
service users. Reference numbers identify traffic from different
sources travelling over the same circuit. Each reference number
on the WAN circuit must be unique.
If the service provider offers multiplexing, a value of ‘0’
instructs the provider not to multiplex other LAN traffic over
the same circuit. This includes encapsulated data travelling
over a Frame Relay network. If the service provider does not
provide multiplexing, this parameter should also be set to ‘0’.
If this parameter has a non-zero value, the provider uses this
value as a reference in its multiplexing encapsulation header.
The reference allows data from this circuit to be distinguished
from other data multiplexed over the same PVC.
4. Link - Fragmentation Size
This parameter determines the maximum frame size supported
on this WAN circuit. In general, the default value is acceptable
for most configurations, since frame size is a negotiated value.
18-326
For Frame Relay, fragmentation is normally incorporated
within the DLCI configuration.
5. Bridge Number
This parameter determines the number of this bridge. It
distinguishes this bridge from other bridges that are connected
to the same two LAN segments.
With source routing, data frame headers contain routing
descriptors that identify the path to the frame's destination.
When a frame arrives on the LAN, it is picked up by all
attached bridges. However, only the bridge whose number
appears in the frame's routing descriptors will forward the
frame. All other bridges will discard the frame. A value of
65535 indicates that no bridge number is assigned to this
bridge. Use this value only if parallel bridging is not
implemented (i.e., no other bridge is connected to the same two
LANs as this bridge).
6. Hop Count
This parameter determines the maximum number of routing
descriptors allowed in a frame's Routing Information field.
The Routing Information field defines the path that a frame
must take to reach its destination. Each routing descriptor
consists of a bridge number and an attached LAN number
(local segment number). The hop value applies to all frames
that pass through this port. Frames with too many routing
descriptors are discarded.
7. Span Mode
This parameter determines how this port handles Spanning
Tree Explorer (STE) frames. These frames are issued by a
sending station to discover the path to a destination. These
frames can only be transmitted through ports that are part of a
dynamic or manually configured spanning tree. The sending
3008M300-004

station forwards frames through the tree structure from LAN to
LAN until the destination is located.
Notice that this parameter must be set to 'auto-span' for ports
that use source route transparent (SRT) bridging.
The options available are as mentioned below.
• auto-span: indicates that the port supports both spanning tree
protocol (STP) and source route bridging. The port's state
determines how it handles incoming STE frames. If the port
is in the forwarding state, STE frames can be received and
forwarded. If the port is in any other state, STE frames are
discarded.
• disabled: indicates that the port does not accept or send STE
frames. STE packets that are received at this port will be
discarded.
• forced: indicates that the port forwards STE frames,
although the STP protocol is not supported. If you select this
option, you must ensure that there are no loops in the
topology, since the protocol does not protect against the
formation of loops.
8. Segment
This parameter determines the identifier for the LAN segment
that this port is connected to. The value should be unique
within the network.
With source routing, data frame headers contain routing
descriptors that identify the path to the frame's destination.
When a bridge receives a frame, it reads the routing descriptors
to determine whether to forward the frame. If a LAN number in
the header matches a LAN number associated with one of the
bridge's ports, the bridge forwards the frame on that port.
Otherwise, the bridge discards the frame.
A value of 65535 indicates that no segment is assigned to this
port (i.e., the port is not attached to a Token Ring LAN).
3008M300-004
18 CONFIGURING BRIDGING
9. Largest Frame
This parameter determines the maximum Info field size per
frame that this port can send and receive. This value is
measured in octets and excludes framing octets.
The Info field size is determined by the application used at the
port. For example, a size of 1500 octets is required for 802.3
CSMA/CD and Ethernet applications; a size of 4472 octets is
required for FDDI applications.
When an explorer frame is used to discover the route to a
destination, each bridge along the route can reduce the
maximum Info field size in the frame header if the bridge or its
attached LAN cannot handle the specified size. This enables
the discovery process to determine both the path to a given
destination and the maximum frame size supported on that
path.
10. Handling
This parameter determines the forwarding priority for data sent
from this source route (SR) bridge port.
Forwarding priority allows all packets from a given port to be
identified as high or low priority data. This setting has
significance only within the local Memotec device. When the
device has several active ports transmitting large quantities of
data, high priority packets take precedence. Data in the low
priority queue will not be transmitted until the high priority
queue is empty.
The priority parameter can also be configured to discard data.
This option is included to be consistent with prioritization and
filtering mechanisms found in other Memotec modules. In
other modules, prioritization can be applied to specific types of
18-327
CXTool User Guide

data or data from specific sources. The discard option,

therefore, acts as a filter.
The options available as listed below.
• discard: indicates that all data sent from the bridge port is
discarded.
• forward: indicates that all data sent from the bridge port is
forwarded with normal priority. Use this setting when you
do not need data from this port to take precedence over other
data.
• priority_low: indicates that all data sent from the bridge port
goes to the low priority transmission queue. The data is only
transmitted from the Memotec unit when the high priority
queues are empty.
• priority_high: indicates that all data sent from the bridge port
goes to the high priority transmission queue. The data is
transmitted before all other priority data.
11. Initial State - On/Off
This parameter enables and disables the SR port. A disabled
port's configuration is not deleted; instead, the configuration is Figure 18-5: Configuring the Source Routing Port - Advanced
stored and the port can be re-enabled without being
Configure the parameters described below.
reconfigured. Each enabled port uses system resources, even if
the port is idle. Therefore, disable any ports that are currently 1. SNMP Support
not needed. This parameter enables disables SNMP Support.
2. IP Address and Netmask
Source To configure the advanced parameters, click on the Advanced These parameters allow the user to define an IP address when
Routing - tab. The following screen appears: configuring IP bridging.
Advanced
3. MAC Address (Hex)
This parameter allows the user to modify the hardware address
of the Ethernet interface.

18-328 3008M300-004

4. Segment
The value in this parameter must match that in the Segment
parameter of the Source Routing Port.
18.2.3 Configuring the Spanning Tree Port
From the Bridge folder, select the Port module. Click on the
Add (+) button in the tool bar or select Add New from the pull-
down Edit menu, and the following screen appears:
Figure 18-6: Configuring the Spanning Tree Port
Configure the parameters as described below.
3008M300-004
18 CONFIGURING BRIDGING
1. Name
This parameter allows the user to change the default name.
2. Link group box
This parameter allows the user to configure one of the
following links:
• ATM VCL
• Ethernet
• FR Bundle
• FR DLCI
• Token Ring Driver
3. Link - Reference Number
This parameter determines the routing reference number for
data travelling through this convergence port and over this
circuit.
Reference numbers are used by WAN service providers that
offer multiplexing. Multiplexing allows data from different
sources to be transmitted over the same WAN circuit, thereby
sharing bandwidth and reducing overall connection costs for
service users. Reference numbers identify traffic from different
sources travelling over the same circuit. Each reference number
on the WAN circuit must be unique.
If the service provider offers multiplexing, a value of ‘0’
instructs the provider not to multiplex other LAN traffic over
the same circuit. This includes encapsulated data travelling
over a Frame Relay network. If the service provider does not
provide multiplexing, this parameter should also be set to 0
(zero).
If this parameter has a non-zero value, the provider uses this
value as a reference in its multiplexing encapsulation header.
The reference allows data from this circuit to be distinguished
from other data multiplexed over the same PVC.
18-329
CXTool User Guide
4. Link - Fragmentation Size
This parameter determines the maximum frame size supported
on this WAN circuit. In general, the default value is acceptable
for most configurations, since frame size is a negotiated value.
For Frame Relay, fragmentation is normally incorporated
within the DLCI configuration.
5. Handling
This parameter determines the forwarding priority for data sent
from this STP bridge port.
Forwarding priority allows all packets from a given port to be
identified as high or low priority data. This setting has
significance only within the local Memotec device. When the
device has several active ports transmitting large quantities of
data, high priority packets take precedence. Data in the low
priority queue will not be transmitted until the high priority
queue is empty.
The priority parameter can also be configured to discard data.
This option is included to be consistent with prioritization and
filtering mechanisms found in other Memotec modules. In
other modules, prioritization can be applied to specific types of
data or data from specific sources. The discard option,
therefore, acts as a filter.
The options available are listed below.
• discard: indicates that all data sent from the bridge port is
discarded.
• forward: indicates that all data sent from the bridge port is
forwarded with normal priority. Use this setting when you
do not need data from this port to take precedence over other
data.
• priority_low: indicates that all data sent from the bridge port
goes to the low priority transmission queue. The data is only
18-330
transmitted from the Memotec unit when the high priority
queues are empty.
• priority_high: indicates that all data sent from the bridge port
goes to the high priority transmission queue. The data is
transmitted before all other priority data.
6. Initial State - On/Off
This parameter enables and disables the STP port. A disabled
port's configuration is not deleted; instead, the configuration is
stored and the port can be re-enabled without being
reconfigured. Each enabled port uses system resources, even if
the port is idle. Therefore, it is advisable to disable any ports
that are currently not being used.
Spanning Tree The remaining parameters in this module are advanced
Port - functions. It is recommended that they not be modified. A
Advanced description of the advanced parameters is provided below
primarily for information.
1. Priority
This parameter determines the priority assigned to this port.
The priority value forms the last octet of the port identifier. The
first octet is the port number. The port identifier uniquely
identifies the port on this bridge.
2. Path Cost
This parameter determines the cost of transmitting a frame
onto the LAN through this port. Cost values can be based on
any criterion you choose. In general, the higher the cost, the
less likely the port will be used if alternative routes are
available. If you do not specify a cost, the system assigns a
value of '1' by default
When the spanning tree is recalculated, the port that offers the
lowest-cost path to the root on each LAN becomes the
3008M300-004
 18 CONFIGURING BRIDGING

designated port for that LAN. The designated port handles all
traffic for the LAN to and from the direction of the root bridge.
3. Frame Check Sequence
This parameter determines the frame check sequence (FCS)
handling required for data sent or received from the STP
bridge. The options available are as listed below.
• unknown: will function the same as local.
• local: indicates that the Cyclic Redundancy Check (CRC)
generation is handled by the STP bridge. The FCS is not
passed to or from upper layers.
• endToEnd: indicates that CRC generation is not handled by
the STP bridge. The FCS is passed to or from the upper
layers.
4. SNMP Support
• IP Address and Netmask
These parameters allow the user to define an IP address
when configuring IP bridging.
• MAC Address (Hex)
This parameter allows the user to modify the hardware
address of the Ethernet interface.
2. Value (Hex)
This parameter determines the value to be matched in the Mask
parameter.
3. Offset
This parameter determines where, in the frame, matching will
be done. Matching starts at this offset in the received frame.
4. Action
This parameter determines the filtering/forwarding action
performed when the frame matches this entry. The options
available are as follows:
• discard: indicates that the data is not forwarded
• forward: indicates that the data is forwarded
• priority_low: indicates that the data is forwarded with a low
priority (Frame Relay only)
• priority_high: indicates that he data is forwarded with a high
priority (Frame Relay only)

Spanning The Filter Table is also an advanced function. It is

Tree Port - recommended that the parameters not be modified. A
Filter Table description of the advanced parameters is provided below
primarily for information.
1. Mask (Hex)
This parameter determines a mask of the data filter/
prioritization. This mask is ANDed with data chosen by offset,
and the result is checked against this entry in the Value
parameter.

3008M300-004 18-331
CXTool User Guide

18-332 3008M300-004
 19 HDLC, BISYNC, AND BRI

This chapter provides reference information to the following

topics: HDLC, the High-level Data Link Control protocol;
BISYNC, the binary synchronous communications protocol;
and BRI, the basic rate interface.

3008M300-004 19-333
CXTool User Guide

19.1 HDLC
HDLC is a bit-oriented, synchronous, link layer, data-framing,
flow control, and error detection and correction protocol.

A Memotec device can accept HDLC packets, can transport

them transparently over a frame relay network, can receive
them from a frame relay network, and can forward them.

To configure this service, open the Transparent folder. Select

the HDLC Port module. Click on the Add (+) button in the tool
bar or select Add New from the pull-down Edit menu. The
screen shown in Figure 19-1 appears.

Configure the parameters listed below.

1. Sync Port
This parameter allows the user to configure a sync port. For
further details, see6.4 Configuring a Synchronous Driver
2. Frame Relay DLCI
This parameter allows the user to configure a Frame Relay
DLCI. For further details, see 9.2.2 Configuring Frame Relay
DLCIs.
3. Reference Number
This parameter is configured when multiple HDLCs are carried
on the same frame relay DLCI. Each Reference Number must
be unique.
4. PId Figure 19-1: Configuring an HDLC Port
This parameter allows the user to identify the type of traffic to
be carried on this circuit. For a list of options, see
9.2.3 Configuring Frame Relay Switching. 19.2 BISYNC
To configure this service, open the Transparent folder. Select the
BSC module. Click on the Add (+) button in the tool bar or select

19-334 3008M300-004
 19 HDLC, BISYNC, AND BRI

Add New from the pull-down Edit menu. The following screen ap- 2. Frame Relay DLCI
pears: This parameter identifies the DLCI on which BISYNC data
will be carried across a Frame Relay network to its destination.
3. Reference Number
This parameter indicates the reference number assigned to the
Frame Relay circuit. When multiple users transmit over the
same PVC, the reference number uniquely identifies data from
each source.
4. PId
This parameter allows the user to identify the type of traffic to
be carried on this circuit. To view a list of the options available,
see Chapter 9 CONFIGURING FRAME RELAY, section
9.2.4 Configuring the ATM Interworking Port.

In the event that a BISYNC parameter is empty, click on Add

and follow the configuration steps outlined in 6.2 Configuring
a Bisync Driver.

19.3 BRI
Refer to Chapter 11 CONFIGURING ISDN AND QSIG,
especially:
• “Interfaces” on page 11-202
• “Configuring BRI Services Only” on page 11-201
• “Summary of ISDN features supported on CX Products” on
page 11-202
Figure 19-2: Configuring a BISYNC Port
• “BRI/PRI Capabilities” on page 11-203
Configure the parameters listed below.
1. BISYNC port
This parameter allows the user to configure a BISYNC driver.

3008M300-004 19-335
CXTool User Guide

19.4 Global Directory

The Global Directory allows the user to store information
pertinent to voice and data calls.
• For voice calls, see“Configuring the Local Port” on
page 7-85, Voice Channel - Advanced, points 12 and 13
• For data calls, see“Configure the ISDN Data Service Point”
on page 11-213

19-336 3008M300-004
 Section Two

CXTool Primer

3008M300-004 pri-337
CXTool User Guide

pri-338 3008M300-004
 CXTool User Guide

Section Two 22.2.1 Telephone Switch Interfaces . . . . . . . . . . . . . . pri 22-360

22.3 Digital Voice and Encoding . . . . . . . . . . . . . . . . . . . pri 22-361
Primer 22.3.1 PAM and PCM (G.711 Encoding) . . . . . . . . . pri 22-361
22.3.2 Other Standards. . . . . . . . . . . . . . . . . . . . . . . . pri 22-362
22.4 Voice over IP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . pri 22-362
CONTENTS 22.5 The Next Step . . . . . . . . . . . . . . . . . . . . . . . . . . . . . pri 22-363

INTRODUCTION TO ATM . . . . . . . . . . . . . . . . . pri 23-365

List of Figures . . . . . . . . . . . . . . . . . . . . . . . . . pri FIG-343 23.1 About ATM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . pri 23-366
23.2 ATM Layers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . pri 23-366
List of Tables . . . . . . . . . . . . . . . . . . . . . . . . pri TAB-345 23.2.1 ATM Adaptation Layer (AAL) . . . . . . . . . . . . pri 23-367
23.2.2 ATM Layer . . . . . . . . . . . . . . . . . . . . . . . . . . . pri 23-368
PRIMER OVERVIEW . . . . . . . . . . . . . . . . . . . . . pri 20-347 23.2.3 Physical Layer. . . . . . . . . . . . . . . . . . . . . . . . . pri 23-368
23.3 ATM Cell Structure . . . . . . . . . . . . . . . . . . . . . . . . . pri 23-369
20.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . pri 20-348 23.4 Virtual Circuits. . . . . . . . . . . . . . . . . . . . . . . . . . . . . pri 23-369
20.2 Inherent Logic of CXTool . . . . . . . . . . . . . . . . . . . . pri 20-349 23.5 ATM Traffic Contract . . . . . . . . . . . . . . . . . . . . . . . pri 23-370
20.3 Prerequisites to Using CXTool . . . . . . . . . . . . . . . . pri 20-350 23.5.1 Quality of Service (QoS) . . . . . . . . . . . . . . . . pri 23-370
20.4 CXTool Features . . . . . . . . . . . . . . . . . . . . . . . . . . . pri 20-350 23.5.2 Connection Traffic Descriptor . . . . . . . . . . . . pri 23-370
20.5 Products Configured by CXTool . . . . . . . . . . . . . . . pri 20-351 23.5.3 Service Categories. . . . . . . . . . . . . . . . . . . . . . pri 23-370
20.6 Using CXTool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . pri 20-351 23.6 Traffic Management. . . . . . . . . . . . . . . . . . . . . . . . . pri 23-371
20.7 Online Help for CXTool . . . . . . . . . . . . . . . . . . . . . pri 20-352 23.6.1 Connection Admission Control. . . . . . . . . . . . pri 23-371
23.6.2 Traffic Shaping . . . . . . . . . . . . . . . . . . . . . . . . pri 23-372
PREPARING TO CONFIGURE . . . . . . . . . . . . . pri 21-353 23.6.3 Traffic Policing . . . . . . . . . . . . . . . . . . . . . . . . pri 23-372
23.7 Operation, Administration, and Maintenance . . . . . pri 23-372
21.1 Configuring CX Devices With CXTool . . . . . . . . . pri 21-354 23.7.1 OAM Flows. . . . . . . . . . . . . . . . . . . . . . . . . . . pri 23-372
21.2 Setting Parameters Through the Console Port . . . . . pri 21-354 23.8 The Next Step . . . . . . . . . . . . . . . . . . . . . . . . . . . . . pri 23-373
21.3 Setting Parameters Through a Network Connection pri 21-355
21.4 Parameter Setting in a System . . . . . . . . . . . . . . . . . pri 21-355
21.5 The Next Step. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . pri 21-356 INTRODUCTION TO FRAME RELAY . . . . . . . . pri 24-375
24.1 About Frame Relay . . . . . . . . . . . . . . . . . . . . . . . . . pri 24-376
TELEPHONY . . . . . . . . . . . . . . . . . . . . . . . . . . . pri 22-357 24.2 Network Interfaces. . . . . . . . . . . . . . . . . . . . . . . . . . pri 24-376
24.3 Permanent Virtual Circuits (PVCs) . . . . . . . . . . . . . pri 24-376
22.1 About Telephones . . . . . . . . . . . . . . . . . . . . . . . . . . pri 22-358 24.4 Data Link Connection Identifier (DLCI) . . . . . . . . . pri 24-376
22.1.1 Telephone Set . . . . . . . . . . . . . . . . . . . . . . . . . pri 22-358 24.5 Congestion Control . . . . . . . . . . . . . . . . . . . . . . . . . pri 24-376
22.1.2 Subscriber Line Types . . . . . . . . . . . . . . . . . . . pri 22-359 24.5.1 FECN Bit . . . . . . . . . . . . . . . . . . . . . . . . . . . . pri 24-377
22.1.3 Subscriber Signaling . . . . . . . . . . . . . . . . . . . . pri 22-359 24.5.2 BECN Bit . . . . . . . . . . . . . . . . . . . . . . . . . . . . pri 24-377
22.2 Trunks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . pri 22-360 24.5.3 DE Bit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . pri 24-377
24.6 Quality of Service . . . . . . . . . . . . . . . . . . . . . . . . . . pri 24-378

3008M300-004 pri TOC-339

CXTool User Guide

24.6.1 Traffic Parameters . . . . . . . . . . . . . . . . . . . . . . pri 24-378 INTRODUCTING T1 AND E1. . . . . . . . . . . . . . . pri 27-397
24.6.2 Service Expectations . . . . . . . . . . . . . . . . . . . . pri 24-378
27.1 About T1/E1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . pri 27-398
24.7 PVC Signaling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . pri 24-378
27.2 T1/E1 Components . . . . . . . . . . . . . . . . . . . . . . . . . pri 27-398
24.7.1 UNI Signaling . . . . . . . . . . . . . . . . . . . . . . . . . pri 24-379
27.2.1 T1/E1 Node. . . . . . . . . . . . . . . . . . . . . . . . . . . pri 27-399
24.7.2 NNI Signaling . . . . . . . . . . . . . . . . . . . . . . . . . pri 24-379
27.2.2 Frame Formats . . . . . . . . . . . . . . . . . . . . . . . . pri 27-401
24.8 Multiprotocol Encapsulation . . . . . . . . . . . . . . . . . . pri 24-379
27.2.3 Digital Line Encoding. . . . . . . . . . . . . . . . . . . pri 27-402
24.9 Fragmentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . pri 24-379
27.2.4 Voice Signaling Methods . . . . . . . . . . . . . . . . pri 27-403
27.3 Next Step . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . pri 27-403
INTRODUCING IP . . . . . . . . . . . . . . . . . . . . . . . pri 25-381
25.1 About TCP/IP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . pri 25-382 INTRODUCING SNA . . . . . . . . . . . . . . . . . . . . . pri 28-405
25.1.1 Internet Protocol . . . . . . . . . . . . . . . . . . . . . . . pri 25-382
28.1 About Systems Network Architecture . . . . . . . . . . . pri 28-406
25.1.2 Transmission Control Protocol . . . . . . . . . . . pri 25-384
28.2 Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . pri 28-406
25.1.3 User Datagram Protocol . . . . . . . . . . . . . . . . . pri 25-384
28.3 Components of an SNA Network . . . . . . . . . . . . . . pri 28-407
25.1.4 Address Resolution Protocols . . . . . . . . . . . . . pri 25-384
28.3.1 Data Links. . . . . . . . . . . . . . . . . . . . . . . . . . . . pri 28-407
25.2 IP Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . pri 25-385
28.3.2 Nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . pri 28-408
25.2.1 Static Routing . . . . . . . . . . . . . . . . . . . . . . . . . pri 25-385
28.3.3 Components of Nodes. . . . . . . . . . . . . . . . . . . pri 28-409
25.2.2 Dynamic Routing . . . . . . . . . . . . . . . . . . . . . . pri 25-386
28.3.4 Session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . pri 28-409
25.3 IP Tunneling. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . pri 25-387
28.4 The Next Step . . . . . . . . . . . . . . . . . . . . . . . . . . . . . pri 28-410

INTRODUCING ISDN. . . . . . . . . . . . . . . . . . . . . pri 26-389

INTRODUCING ASYNC PAD . . . . . . . . . . . . . . pri 29-411
26.1 Preamble . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . pri 26-390
29.1 Preamble . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . pri 29-412
26.1.1 Standardizing ISDN . . . . . . . . . . . . . . . . . . . . pri 26-390
29.2 X.3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . pri 29-412
26.1.2 ISDN Features. . . . . . . . . . . . . . . . . . . . . . . . . pri 26-391
29.3 X.28 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . pri 29-412
26.1.3 Standardizing QSIG . . . . . . . . . . . . . . . . . . . . pri 26-391
29.4 X.29 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . pri 29-413
26.1.4 QSIG Features. . . . . . . . . . . . . . . . . . . . . . . . . pri 26-391
29.5 Next Step . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . pri 29-413
26.2 ISDN System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . pri 26-392
26.2.1 ISDN Channels . . . . . . . . . . . . . . . . . . . . . . . . pri 26-392
26.2.2 ISDN Access Interface Types . . . . . . . . . . . . . pri 26-392 INTRODUCING X.25 . . . . . . . . . . . . . . . . . . . . . pri 30-415
26.3 ISDN Devices and Protocols . . . . . . . . . . . . . . . . . . pri 26-393 30.1 Preamble . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . pri 30-416
26.3.1 Functional Devices . . . . . . . . . . . . . . . . . . . . . pri 26-393 30.2 X.25 and OSI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . pri 30-416
26.3.2 ISDN Reference Points . . . . . . . . . . . . . . . . . . pri 26-394 30.2.1 Layer 1 - The Physical Layer . . . . . . . . . . . . . pri 30-416
26.3.3 ISDN and the OSI Model . . . . . . . . . . . . . . . . pri 26-395 30.2.2 Layer 2 - The Data Link Layer . . . . . . . . . . . . pri 30-416
26.3.4 ISDN Q-Reference Point . . . . . . . . . . . . . . . . pri 26-396 30.2.3 Layer 3 - The Network Layer . . . . . . . . . . . . . pri 30-417
26.4 Next Step . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . pri 26-396 30.3 Interfaces of X.25 . . . . . . . . . . . . . . . . . . . . . . . . . . pri 30-417
30.4 Next Step . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . pri 30-417

pri TOC-340 3008M300-004

 CXTool User Guide

INTRODUCING IPX . . . . . . . . . . . . . . . . . . . . . . pri 31-419

31.1 Preamble . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . pri 31-420
31.2 IPX Protocol Architecture . . . . . . . . . . . . . . . . . . . . pri 31-420
31.2.1 IPX Addressing . . . . . . . . . . . . . . . . . . . . . . . . pri 31-420
31.2.2 Reserved Network Numbers . . . . . . . . . . . . . . pri 31-421
31.2.3 IPX Packet. . . . . . . . . . . . . . . . . . . . . . . . . . . . pri 31-421
31.3 IPX Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . pri 31-422
31.3.1 RIP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . pri 31-423
31.3.2 SAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . pri 31-424
31.4 Next Step . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . pri 31-425

INTRODUCING MLPPP . . . . . . . . . . . . . . . . . . . pri 32-427

32.1 Preamble . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . pri 32-428
32.2 About MLPPP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . pri 32-428
32.2.1 Multilink Structure . . . . . . . . . . . . . . . . . . . . . pri 32-428
32.2.2 MLPPP Header . . . . . . . . . . . . . . . . . . . . . . . . pri 32-429
32.2.3 Establishing an MLPPP Link . . . . . . . . . . . . . pri 32-429
32.2.4 MLPPP and Reliable Transmission. . . . . . . . . pri 32-429
32.2.5 MLPPP and ISDN . . . . . . . . . . . . . . . . . . . . . . pri 32-429
32.3 Next Step . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . pri 32-430

INTRODUCING BRIDGES . . . . . . . . . . . . . . . . . pri 33-431

33.1 Preamble . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . pri 33-432
33.2 Bridge Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . pri 33-432
33.3 Spanning Tree Algorithm. . . . . . . . . . . . . . . . . . . . . pri 33-433
33.3.1 Bridge Filtering and Forwarding. . . . . . . . . . . pri 33-433
33.3.2 Bridge Learning. . . . . . . . . . . . . . . . . . . . . . . . pri 33-434
33.4 Source Routing Algorithm . . . . . . . . . . . . . . . . . . . . pri 33-435
33.4.1 Token Ring . . . . . . . . . . . . . . . . . . . . . . . . . . . pri 33-435
33.5 Next Step . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . pri 33-435

INTRODUCING HDLC, BISYNC, AND BRI. . . . pri 34-437

34.1 HDLC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . pri 34-438
34.2 BISYNC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . pri 34-438
34.3 BRI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . pri 34-439
34.4 Global Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . pri 34-440

3008M300-004 pri TOC-341

CXTool User Guide

pri TOC-342 3008M300-004

 Section Two Fig.27-2 T1 Node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . pri 27-399
Fig.27-3 E1 Node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . pri 27-399
CXTool Primer
Fig.28-1 SNA Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . pri 28-406

List of Figures Fig.31-1 OSI Model Compared With Netware Protocols . . . pri 31-420
Fig.31-2 IPX Packet Structure. . . . . . . . . . . . . . . . . . . . . . . . pri 31-422
Fig.31-3 Internal Components of an IPX Router . . . . . . . . . pri 31-422
Fig.31-4 IPX Network Scenario . . . . . . . . . . . . . . . . . . . . . . pri 31-423
Fig.21-1 Parameter Setting Through the Console Port . . . . . pri 21-355 Fig.31-5 RIP Packet Structure. . . . . . . . . . . . . . . . . . . . . . . . pri 31-424
Fig.21-2 Parameter Setting Through the Network . . . . . . . . pri 21-355 Fig.31-6 SAP Packet Structure . . . . . . . . . . . . . . . . . . . . . . . pri 31-425
Fig.21-3 Parameter Setting in a System . . . . . . . . . . . . . . . . pri 21-356
Fig.33-1 Bridge Between LAN and WAN . . . . . . . . . . . . . . pri 33-432
Fig.22-1 A Typical Telephone Call . . . . . . . . . . . . . . . . . . . . pri 22-358 Fig.33-2 Bridge FDB Flow: Filter/Forward and Learn . . . . . pri 33-434
Fig.22-2 Basic Analog Trunk . . . . . . . . . . . . . . . . . . . . . . . . pri 22-360
Fig.22-3 E & M Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . pri 22-361 Fig.34-1 Configuring an HDLC Port. . . . . . . . . . . . . . . . . . . pri 34-438
Fig.34-2 Configuring a BISYNC Port. . . . . . . . . . . . . . . . . . pri 34-439
Fig.23-1 ATM Network. . . . . . . . . . . . . . . . . . . . . . . . . . . . . pri 23-366
Fig.23-2 Three ATM Layers and Sublayers . . . . . . . . . . . . . pri 23-367
Fig.23-3 ATM Cell Structure . . . . . . . . . . . . . . . . . . . . . . . . pri 23-369
Fig.23-4 Virtual Circuits . . . . . . . . . . . . . . . . . . . . . . . . . . . . pri 23-370

Fig.24-1 Frame Relay Interface Categories. . . . . . . . . . . . . . pri 24-376

Fig.24-2 Example of DLCI Mapping . . . . . . . . . . . . . . . . . . pri 24-377
Fig.24-3 Notifications for Congestion Avoidance. . . . . . . . . pri 24-377
Fig.24-4 LMI at the User-to-Network Interface (UNI) . . . . . pri 24-379

Fig.25-1 TCP/IP Protocol, Layered Model . . . . . . . . . . . . . . pri 25-382

Fig.25-2 IP Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . pri 25-385
Fig.25-3 OSPF Routing Hierarchy . . . . . . . . . . . . . . . . . . . . pri 25-387
Fig.25-4 Example of IP Tunneling . . . . . . . . . . . . . . . . . . . . pri 25-387

Fig.26-1 ISDN Connection . . . . . . . . . . . . . . . . . . . . . . . . . . pri 26-393

Fig.26-2 ISDN Reference Points . . . . . . . . . . . . . . . . . . . . . . pri 26-395
Fig.26-3 Q-Reference Point. . . . . . . . . . . . . . . . . . . . . . . . . . pri 26-396

Fig.27-1 T1/E1 Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . pri 27-398

3008M300-004 pri FIG-343

CXTool User Guide

pri FIG-344 3008M300-004

 Section Two
CXTool Primer

List of Tables

Tab.23-1 CCITT Service Class and Service Examples . . . . . pri 23-367

Tab.23-2 ATM Service Categories. . . . . . . . . . . . . . . . . . . . . pri 23-371

Tab.25-1 IP Address Format. . . . . . . . . . . . . . . . . . . . . . . . . . pri 25-383

Tab.25-2 Subnet Mask Format . . . . . . . . . . . . . . . . . . . . . . . . pri 25-384

Tab.28-1 PU Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . pri 28-409

Tab.28-2 LU Types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . pri 28-409
Tab.28-3 Session Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . pri 28-410

Tab.31-1 IPX Reserved Network Numbers . . . . . . . . . . . . . . pri 31-421

Tab.33-1 OSI Layers and Internetworking Devices . . . . . . . . pri 33-432

Tab.33-2 Bridge Filtering and Forwarding. . . . . . . . . . . . . . . pri 33-434

3008M300-004 pri TAB-345

CXTool User Guide

pri TAB-346 3008M300-004

 20 PRIMER OVERVIEW

This chapter describes how the CXTool Primer section is

organized.

3008M300-004 20-347
CXTool User Guide
20.1 Overview
CXTool is a Windows-based tool for configuring Memotec CX
products. On a PC running CXTool you can connect to a CX800,
CX900e, CX950, CX960, CX1000e, or CX2000. Once connected,
CXTool can acquire the current status of the device, create and
revise configuration files for it, and then load the configuration
from the PC to the device through the network or by direct
connection.
This document is part of the supporting documentation for CX
Tool. It is divided into two major sections. They are:
• Section One CXTool Configuration Companion, which is a
detailed reference for those who are experienced in
telecommunications and digital network interworking. It
provides in-depth procedures for configuring each protocol and
their related services with CXTool.
• Section Two CXTool Primer, which describes concepts and
provides background information that are basic to the operation
of CX devices and the digital telecommunications environment
in which they operate.
This section, the CXTool Primer, includes these topics:
Chapter 20 PRIMER OVERVIEW
This chapter describes how the CXTool Primer section is
organized.
Chapter 21 PREPARING TO CONFIGURE
In this chapter is an introduction to the configuration of a CX
device using a PC that is running CXTool. CX devices may be
configured either by connecting directly to the console port of the
device or by connecting to it over a network.
20-348
Chapter 22 TELEPHONY
In this chapter there is a general review of telephony with emphasis
on telephone applications of CX devices and internetworking.
Chapter 23 INTRODUCTION TO ATM
This chapter introduces ATM (asynchronous transfer mode) and
describes some of its features. The focus is on providing the
background for configuring services over ATM using CXTool.
Chapter 24 INTRODUCTION TO FRAME RELAY
This chapter reviews frame relay basics. It provides background
information that is helpful during configuration of CX devices in a
frame relay network.
Chapter 25 INTRODUCING IP
An overview of IP (Internet Protocol) is provided in this chapter,
focusing particularly on those items that apply to the configuration
of CX devices with CXTool.
Chapter 26 INTRODUCING ISDN
This chapter describes basic ISDN, the integrated services digital
network.
Chapter 27 INTRODUCTING T1 AND E1
The basics of T1 (a North American digital transmission standard)
and E1 (a European digital transmission standard) are presented as
a general overview in this chapter.
Chapter 28 INTRODUCING SNA
The set of protocols and procedures known as SNA, Systems
Network Architecture, is described in this chapter.
Chapter 29 INTRODUCING ASYNC PAD
This chapter describes Async PAD, the asynchronous packet
assembler/disassembler.
3008M300-004
 Chapter 30 INTRODUCING X.25 20.2 Inherent Logic of CXTool
This chapter provides an overview of X.25 packets, how they are
assembled, and how they are routed. With CXTool the user does not need to know in advance each and
every step in the configuration of a particular service. CXTool’s
Chapter 31 INTRODUCING IPX
internal verification and validation processes look after this.
This chapter provides a general view of IPX, the Novell Netware
Consequently, when a particular module is to be implemented,
networking environment.
CXTool prompts the user to configure related modules. For
Chapter 32 INTRODUCING MLPPP instance, when configuring VoIP services without first configuring
This chapter describes MLPPP, the multi-link point-to-point the IP port, CXTool prompts for the IP port configuration.
protocol, that combines parallel data channels to achieve higher
throughput.

Chapter 33 INTRODUCING BRIDGES

A bridge is used to interconnect digital networks. This chapter
describes the functions of bridges, and how a bridge learns about
the topology of the network to which it is connected.

Chapter 34 INTRODUCING HDLC, BISYNC, AND BRI

This chapter provides reference information to the following
topics: HDLC, the High-level Data Link Control protocol;
BISYNC, the binary synchronous communications protocol; and
BRI, the basic rate interface.

3008M300-004 20-349
CXTool User Guide
20.3 Prerequisites to Using CXTool
While the CXTool application is straightforward to use, the
environment in which the CX devices operate is much less so.
Because of this, users of CXTool are assumed to be experienced.
This document is not a guide to the issues of networking and
internetworking.
The CXTool User Guide is divided into two sections.
Section One CXTool Configuration Companion is written for users
who are knowledgeable about the networking environment and
who have field experience in managing a digital network.
Installation of the application, how it is used, and configuration of
CX devices is described in detail.
Section Two CXTool Primer provides an introduction to the many
protocols that are managed by CXTool. It is intended to be a primer
for someone needing a starting place, and to be a refresher for
someone returning to a protocol after an absence.
20-350
20.4 CXTool Features
CXTool is a Windows-based, configuration tool. It is engineered
specifically to configure Memotec's CX family of
telecommunications products. Configuring telecom devices has
never been more straightforward.
With CXTool all configuration items are displayed as pages. For
the user, the result is a step by step process. By selecting values
from drop down lists and filling in dialog boxes, parameters can be
set, existing settings can be verified and revised, and completely
new configurations can be added.
The graphical user interface (GUI) allows complete network
configurations to be developed quickly and easily. Most ports and
routing circuits can be configured using the default values shown in
the dialog boxes, or with only minor customization.
The key features of CXTool include:
• The CXTool GUI is intuitive and user-friendly. Navigation
panels allow easy and unrestricted movement between many
levels of configuration.
• Auto-learn enables CXTool to detect the hardware
configuration and the software version installed in the selected
device.
• Validation and verification functions reduce the possibility of
creating an invalid configuration.
• CXTool can be used with Windows 95, Windows 98,
Windows Me (Millennium Edition), Windows NT (Version 4),
and Windows 2000.
(For details, see Chapter 2 GETTING STARTED, section
2.1 System Requirements.)
3008M300-004
 20.5 Products Configured by CXTool
The following CX devices are configurable using CXTool:
CX2000, CX1000e, CX960, CX950, CX900e, and CX800.
CX devices are supplied with appropriate software. One method of
configuring CX devices is to use CXTool. CXTool creates
configurations taking into account the version of the software that
is being used on the CX device.
CXTool has embedded within it the rules that govern the various
combinations of CX devices, I/O cards, and software versions.
Inappropriate settings are not presented to the user.
20.6 Using CXTool
CXTool configures each device with data that the user enters in a
series of dialog boxes, which offer choices of parameters, ranges,
and so on. To arrive at the exact, customized configuration needed
by the network the user can accept the default value or enter a
different one in the required fields. The user is guided through each
step needed to complete the configuration of a device. In the event
of an error, the user is informed either immediately or before the
configuration is completed.

NOTE: Trying to create a configuration setting that is

inappropriate may cause the user to suspect that there
is a “bug”. Instead, it may be that the setting is not
allowed due to wrong combinations of software
version, CX device or I/O card.

For more information on CX devices and slot allocation, refer to

the Hardware Reference Guide for the device.

3008M300-004 20-351
CXTool User Guide

20.7 Online Help for CXTool

Online help in HTML format is fully integrated with CXTool. The
help system is module-specific, fully indexed, and includes search
features. For example, when a module is selected and then the Help
button is clicked, information related to the configuration fields of
that module are displayed.

Each CXTool window, even if it has several tabs, has only one Help
button. The Help button opens the help system browser at the
appropriate description for the field being configured.

20-352 3008M300-004
 21 PREPARING TO CONFIGURE

In this chapter is an introduction to the configuration of a CX

device using a PC that is running CXTool. CX devices may be
configured either by connecting directly to the console port of the
device or by connecting to it over a network.

For the recommended PC requirements and step-by-step

procedures for installing and starting CXTool refer to Section
One, Chapter 2 GETTING STARTED, of this user guide.

3008M300-004 21-353
CXTool User Guide

21.1 Configuring CX Devices With CXTool
From a glance at any Memotec CX device it is clear that there
are no knobs or similar physical controls to adjust. Instead, the
behavior of the device is determined by the values of
parameters stored inside it.
To read the current parameter values of the device, or to make
changes to the values, a PC is used. When particular messages
are sent from the PC to the CX device, the device responds.
The other method of composing messages is through the use of
CXTool, which is the topic of this user guide. CXTool is also
supplied with the device.
CXTool has a graphical user interface (GUI), and is the tool of
choice for system installation and configuration since it allows
setting many parameters at the same time. It provides an
environment in which normal values are suggested and there
are warnings about unusual values or combinations of values.
Illegal values are prevented from being set.

There are several types of CX messages. Some messages

produce replies describing current status, others yield lists of 21.2 Setting Parameters Through the Console Port
parameters, and some cause parameter values to be changed
resulting in changes to the behavior of the device. In general,
To outline how parameters are set by direct connection to the
the process of sending messages for the purpose of reading and
console port, we use the example diagramed in Figure 21-1. In
changing the parameters of a device is called configuration.
this setup, service for the telephone is provided over the digital
Messages from the PC to the CX device may be sent over an network.
interconnecting cable. One end of the cable is connected to the
The CX device is a 950.
serial port of the PC and the other end is connected to the
console port of the target CX device. More about this follows To exchange configuration messages with the 950, the PC has
in “21.2 Setting Parameters Through the Console Port”. CXTool installed and running. An RJ-45 cable is connected
between the PC’s NIC (network interface card) and the console
Messages from the PC may also be sent over a network to
port of the 950.
which the target CX device is connected. More about this
follows in “21.3 Setting Parameters Through a Network Once connected, CXTool can learn, or acquire, from the 950
Connection”. the kind of device it is and the details of its current
configuration.
One method of composing messages on the PC is to use the
Command Line software that is supplied with the device.
Normally, the Command Line software is used for adjusting
one or two parameters, and for troubleshooting.

21-354 3008M300-004
 21 PREPARING TO CONFIGURE

PC PC

CX950

CX950
Network
Network

Figure 21-1: Parameter Setting Through the Console Port

Figure 21-2: Parameter Setting Through the Network

21.3 Setting Parameters Through a Network

Connection
A basic setup in which the CX device and the PC are connected
through a digital network is diagramed in Figure 21-2. The
connection allows them to exchange messages. In this
example, the CX device is a 950 and the network is what’s
called a WAN or wide area network.
The PC has CXTool installed and running. The PC has an IP
address and so does the 950.
21.4 Parameter Setting in a System
A system that provides communication service through a
digital network is shown in Figure 21-3. The telephone
attached to CX950 A is able to dial and be connected to the
telephone attached to CX950 B. When the connection is made,
the telephone at B will ring, and when the receiver is lifted a
voice circuit between the two parties will be implemented

By exchanging messages over the network, CXTool can learn

from the 950 what kind of device it is and the details of its
current configuration.

3008M300-004 21-355
CXTool User Guide

allowing them to have a conversation. When the parties hang- Once a connection with a CX device is established, CXTool
up the circuit will be disconnected. can learn what kind of device it is connected to, and the details
of its current configuration. This information can be stored in a
file. CXTool allows the values to be examined using a
hierarchy of windows. The windows display related parameters
on pages so their settings can be seen as groups.
PC
CXTool allows parameters to be revised as required. When
revisions are made, the file is saved locally in CXTool, and
when convenient the file can be loaded into the CX device.
CX950
B
Using CXTool, the reconfiguration of a CX device consists of
three steps:
1. Learn the current configuration of the CX device
CX950 Frame 2. Revise the current configuration in CXTool
A Relay 3. Load the new configuration from CXTool into the CX device

Figure 21-3: Parameter Setting in a System

21.5 The Next Step
To do this, the devices at A and B are configured to respond to From this outline of the process for exchanging configuration
the signals created by the telephones, to pass appropriate messages between a CX device and a PC running CXTool, the
datagrams to the frame relay network, and, based on the next step is to go to the configuration section of this user guide.
datagrams received from the network, to recreate signals for Chapter 5 CONFIGURING HARDWARE provides the details
reproduction by the telephone. needed to learn current configurations and to implement
changes.
CX950 A is referred to as central because it contains
information used by other network devices in the system. The
other network devices are referred to as remote. CX950 B is a
remote.

To configure CX950 A, a PC with CXTool installed is used. An

RJ-45 cable is connected between the PC’s NIC and the
CX950’s console port.

21-356 3008M300-004
 22 TELEPHONY

In this chapter there is a general review of telephony with emphasis

on telephone applications of CX devices and internetworking.

3008M300-004 22-357
CXTool User Guide

22.1 About Telephones

Telephony is the technology associated with the transmission
of voice between distant parties using systems historically CO Switch
associated with the telephone. With the arrival of computers CO Switch PSTN
and the transmission of digital information over telephone
systems as well as the use of radio to transmit telephone PBX
signals, the distinction between telephony and
telecommunication has become difficult to make. A telephone
set and subscriber line, however, are the most basic elements of CO Trunk
any telephone network. The next section examines the various Subscriber line
components of a telephone and describes how a subscriber line
is used to provide telephone services. Subscriber line

22.1.1 Telephone Set

A telephone set is made up of these components:

• A ringer, mechanical or electronic Figure 22-1: A Typical Telephone Call

• A dialing device, pulse or dual tone multi frequency
(DTMF)
• A hybrid circuit, used within a telephone to convert from 4-
wire (ear and mouth) to the 2-wire circuit of the link to the
central office
• A hook switch, that closes the loop (off hook, handset lifted
from cradle) and opens the loop (on hook, handset placed in
cradle)
Here are the steps involved in making a call. Refer to
Figure 22-1.
1. The side that wants to call (the calling party) picks up the
handset, taking the phone off hook and closing the circuit.
2. The off hook state is detected by the Central Office (CO) or
Private Branch eXchange (PBX) by measuring the line current.
3. The CO switch or PBX responds to the off hook by sending a
dial tone. The dial tone indicates that the switch is ready to
receive a call.
4. After hearing the dial tone, the caller dials the destination
telephone number.
5. The call is then routed to the destination based on the telephone
number.
6. If the destination switch cannot be reached due to congestion
or a network outage a re-order tone or “fast busy” tone is
returned to the calling party.

22-358 3008M300-004

7. If the destination telephone (called party) is on another call, a
busy signal is returned to the calling party.
8. When the called party is available to receive a call, it is sent a
ringing signal.
9. The originating switch sends a ring-back tone to the calling
party when a path is established to the called party.
10. When the called party answers (i.e., the called phone goes off
hook), the call setup is completed.
It is clear from the above that as a call proceeds from its origin
to its destination, it is carried first over a line (from the calling
telephone to a CO or switch) and then over a trunk (from one
CO or switch to another CO or switch). The following section
discusses the type of switch interfaces, subscriber lines, and
signaling that facilitate the progression of a phone call.
22.1.2 Subscriber Line Types
Subscriber lines extend from a switching device (CO or PBX)
to a terminating device. The lines may terminate with a key
system or a residential telephone set. There are three types of
subscriber lines.
1. Foreign eXchange (FX) Lines
FX lines are used to connect a residential telephone to a CO or
PBX. They are the most common subscriber lines.
2. Off Premise eXtension (OPX) Lines
OPX lines are used to connect to a PBX in another building.
3. Centrex Lines
Centrex is a service provided by subscription from the
telephone company. It offers PBX-like features without the
equipment investment. The equipment resides in the telephone
company’s CO.
3008M300-004
22 TELEPHONY
22.1.3 Subscriber Signaling
Subscriber signaling is used to exchange information between
a subscriber and a switch. In general, there are two methods of
exchanging signaling information. They are as listed below.
1. Loop Signaling
This type of signaling is also known as FX signaling. It uses
the hook switch and ringing to send information from the
telephone to the switch. There are two types of Loop Signaling:
• Loop Start Signaling
When the telephone handset is lifted, the hook switch closes
and the loop is completed, which signals the start of a call.
• If the call is initiated by the telephone, the CO adds a dial
tone that the user hears indicating that the system is ready
for dialing. The CO detects current in the loop and
prepares for addressing with a dial register.
• If the call is initiated by the CO, it adds a ringing voltage
to the line.
• Ground Start Signaling
When the tip lead or the ring lead is grounded the start of a
call is signalled.
• If the call is initiated by the FXO interface, it is answered
by grounding the ring lead.
• If the call is initiated by the FXS interface, it is answered
by grounding the tip lead. This type of signaling is
commonly used for analog trunks.
2. Tone Signaling
This type of signaling uses DTMF, dial tone, busy tone, and
more, to exchange information between the telephone and the
switch.
22-359
CXTool User Guide

There are different types of signals that are used to indicate the 822, 844, 855, 866, 877, 888, and 899. Note that WATS
start of a call (off hook), the end of a call (on hook), or the trunks use digital connections.
arrival of a call (ringing) used by the switch. Signals are also
• Tie Trunks
used to provide tones that inform users of the progress of their
Tie trunks are used to connect two or more PBXs. These
calls (i.e., phone busy, trunk busy, dial tone, and audible ring)
trunks are generally used to build a private telephone
or to notify them of certain alert conditions (i.e., flashing
network among different offices. Since this configuration
signal, re-ringing, and receiver off hook).
allows users to dial remote locations using only the
As mentioned earlier, once a call is forwarded to a CO or a extension number, long distance dialing is not required. Tie
switch, it may be carried over trunks to another CO or a switch. trunks can be analog or digital.
The following section reviews briefly the different kinds of • DID Trunks
trunks, together with the services they provide. Direct Inward Dial trunks allow the CO to pass calls to the
PBX using the telephone extension number. The PBX sends
a ring back tone until the call is answered. DID trunks must
be analog, that is, FXS to FXO.
22.2 Trunks
In a telephone network, a trunk carries multiple voice or data 22.2.1 Telephone Switch Interfaces
channels between two telephone exchange switching systems.
As discussed below, there are different types of trunk
connections. FXO and As shown in Figure 22-2, FXO, the foreign exchange office,
FXS and FXS, the foreign exchange station, are two ends of the
• CO Trunks same trunk. A CO trunk can use an FX loop to provide a
CO trunks connect a private network to a public network connection between the PBX and CO.
They can be analog or digital trunks, depending upon the
number of connections required and the services available in
the region.
• FX Trunks 2 wire FX Loop
FX Trunks are used to provide local access to another area
code. This is useful when the area code has been changed in
a particular region and the residents wish to keep the same
telephone number and area code as before. An FX trunk can FXS Interface
FXO Interface
be either an analog or digital connection.
• WATS Trunks (In WATS/ Out WATS)
Wide Area Telephone Service (WATS) trunks provide bulk Figure 22-2: Basic Analog Trunk
billing. Examples of In WATS numbers include 800, 811,

22-360 3008M300-004
 22 TELEPHONY

The FXO interface provides the following services:

E & M Interface
• DTMF dialing or pulse dialing
• ring detection CO
nk
c Tru
Publi
• 2-wire to 4-wire conversion 1001 2001
CE
E & M Interface
• earphone signal
• microphone signal CE
Priva
te Tr CE
1002 unk
The FXS interface provides the following services PBX
2002
• electrical power/battery, -48 volt DC
• ring signal 90 volts, AC at 20 Hz PBX

• ring back tone Figure 22-3: E & M Interface

• busy tone The previous sections reviewed the basics of telephony. The
next section reviews the internal process involved in sending
• reorder tone voice signals. In particular, it examines how speech is digitized.
• dial tone

Both the FXO and FXS interfaces support loop signalling
(including loop start and ground start) and DTMF signaling.
E & M The E & M interface (ear and mouth, or earphone and
Interface microphone) uses combinations of grounding of wires to
indicate on-hook, off-hook and dialing information. The E lead
is used by the Communications Equipment (CE) to signal on/
off hook and the M lead is used by the PBX to signal on/off
hook. This Interface supports Immediate Start, Delay Dial, and
Wink Start signaling, together with five other types (Type I, II,
III, IV, and V). Figure 22-3 shows the location of the E & M
interface in a voice network.
22.3 Digital Voice and Encoding
Analog signals are converted into digital signals using an
analog to digital converter. The analog signal is first sampled
and digitized using a standard method such as the Pulse
Amplitude Modulation (PAM) technique. Each sample is then
encoded using a CODEC (coder decoder). The next section
reviews both of these processes.
22.3.1 PAM and PCM (G.711 Encoding)
PAM uses a sampling technique to digitize analog signals. A
digital signal is created by measuring the amplitude of the

3008M300-004 22-361
CXTool User Guide
analog waveform at specific time intervals. These
measurements are called samples. Following Nyquist’s
theorem, it is generally accepted that in order to reproduce an
analog waveform, a minimum of two samples per wave cycle
are required. Therefore, the sampling rate must be twice the
highest frequency of the signal. Most telephone systems pass
frequencies between 300 Hz and 3.30 kHz. PAM has a standard
sampling rate of 8 kHz for voice. It produces a (12 bit × 8 kHz
=) 96 kbps digital data stream.
PCM is one method of encoding a digitized sample. PCM
encodes each 12 bit sample into 8 bits for a total of 64 kbps.
22.4 Voice over IP
There are two standards for coding the sample level. The Mu-
Law standard is used in North America and Japan for T1
framing, while the A-Law standard is used in most other
countries for E1 framing.
22.3.2 Other Standards
ADPCM Adaptive Differential Pulse Code Modulation (ADPCM) is a
(G.726 variation of PCM. It produces a digital signal with a lower bit
Encoding) rate than standard PCM, which is 64 kbps, and the user can
choose from among the following bandwidths: 16 kbps, 24
kbps, 32 kbps, and 40 kbps. ADPCM dynamically adjusts the
difference in amplitude represented by bits to more accurately
represent very loud or very quiet signals, thereby reducing the
number of bits required to represent a signal. Today, ADPCM
is an accepted standard for voice encoding and compatible with
many systems.
CS-ACELP G.729 Encoding is defined by the ITU-T as a standard voice
(G.729 compression method. It is the current standard for voice
Encoding) compression over Frame Relay. It provides toll quality voice
and uses only 8 kbps of bandwidth for encoding.
22-362
ACELP II Algebraic Code Excited Linear Prediction (ACELP II)
Encoding algorithm uses sophisticated modeling techniques to reproduce
the voice signal. It is one of Memotec’s proprietary vocoders.
Lately, the idea of transporting Voice over IP (VoIP) has
received a great deal of attention. The next section briefly
examines the relevance of VoIP and why it has come to gain
popularity.
VoIP is a term used in IP telephony for a set of facilities that
manage the delivery of voice information using IP. It means
sending voice information in digital form in discrete packets
rather than in the traditional circuit-committed protocols of the
PSTN (public switched telephone network). A major advantage
of VoIP and Internet telephony is that it avoids the tolls charged
by ordinary telephone service.
VoIP standards were developed by the ITU and the VoIP
Forum, which is comprised of major vendors of voice
equipment. The initial effort of this forum was to promote the
use of ITU-T, H.323—the standard for sending voice (audio)
and video using IP on the public Internet and within intranets.
During the implementation of Revision 1 of H.323, it became
clear that IP telephony was gaining popularity and relevance as
various infrastructure elements were improved upon. A number
of proprietary IP-based telephones were creating many small
islands that could not communicate with one another.
Recommendation H.323 provided a good basis for establishing
universal, IP voice, and multimedia communications in larger,
connected networks.
Communications under H.323 is a combination of audio,
video, data, and control signals. In addition to audio
3008M300-004
 22 TELEPHONY

capabilities, H.323 requires the following parameters; Q.931
call setup, registration, admission, status (RAS) control, and
H.245 standards. All the other capabilities are optional.
In the H.323 architecture, the three most important components
that facilitate a VoIP connection are the following:
1. Terminals
Terminals are essential as they support voice communications;
video and data are optional.
2. Gateways
Gateways are used for translating functions between H.323
endpoints and other terminal types.
3. Gatekeepers
Gatekeepers are used for providing call control services to
registered endpoints.
4. Gatekeepers provide the final important element for IP
telephony. They provide call control services to the H.323
endpoints such as address translation, admission control,
bandwidth control, and zone management. A zone is defined
by all the endpoints, gateways, and Multipoint Control Units
(MCUs). An MCU is composed of a Multipoint Controller
(MC) and a Multipoint Processor (MP). An MC handles H.245
negotiations among all the terminals and MP mixes, switches,
and processes audio, video, and/or data bits. These operations
are important for real-time voice or video when resources must
be balanced, and points of connectivity are highly dynamic.
Acknowledging the growing demand for VoIP, many
companies, including Memotec Communications offer a full
range of VoIP services in accordance with recommendation
H.323.

Note that a gateway is not required if connections to other

networks are not needed. Furthermore, a gatekeeper is not 22.5 The Next Step
required in an H.323 system. However, if a gatekeeper is
present, terminals must make use of the services offered by For the details about configuring voice on CX devices using
gatekeepers (see below). CXTool, go to Chapter 7 CONFIGURING VOICE.

Here are the characteristics of H.323 that make it suitable for

IP telephony.
1. The required voice CODEC of G.711 facilitates connections to
the legacy networks of telephones.
2. The 64 kbps stream can easily be translated between digital
and analog media.
3. One of the addressing formats provided in Recommendation
H.323 is the E.164 address, which specifies standard telephone
numbers (e.g., the digits 0 to 9, *, and #). This type of
addressing maps onto the IP addresses for the H.323 endpoints,
thus allowing regular telephone numbers to dial them.

3008M300-004 22-363
CXTool User Guide

22-364 3008M300-004
 23 INTRODUCTION TO ATM

This chapter introduces ATM (asynchronous transfer mode) and

describes some of its features. The focus is on providing the
background for configuring services over ATM using CXTool.

3008M300-004 23-365
CXTool User Guide

23.1 About ATM

LAN
LAN
Asynchronous Transfer Mode (ATM) is a digital

o
Vi

de
de
communications system that is circuit-switched, and ATM T1/

Vi
E
/E1

o
cell-switched, with fixed-length cells. It is capable of T3/ 1 e
Voic
e
T1 /E3 E3 Voic
high-speed, full-duplex operation that is suitable for data as T3
well as digitized voice and video over the same network.

Figure 23-1 is a sketch of an ATM network. It begins with

customers, who can send and receive voice, video, and data by
means of their CPE (customer provided equipment). CPE is
connected to an access device that is connected to the ATM
network. The CPE-to-access device interface is known as the
UNI, the user-to-network interface. The point where one
network device connects to another network device is known as
the NNI, the network-to-network interface. The signaling
protocols of the UNI and the NNI are not the same, though they
are developments of ISDN protocols. In addition, separate
specifications for NNI and UNI in private networks have been
defined by The ATM Forum, which is an organization
composed of vendors, service providers, researchers, and users.
Figure 23-1: ATM Network
An important characteristic of ATM is the wide range of the
services that the network can provide. The ATM Forum
describes the following service categories in terms of their
applications:
• constant bit-rate, for speech and video
• real time variable bit-rate, for compressed video/compressed
audio
• non-real time variable bit-rate, for file transfer

Typically, the links between access devices run at T1 speeds or • unspecified bit-rate for data
faster. ATM access devices are designed to be scalable, and
they provide most applications with interconnection to ATM
services. 23.2 ATM Layers
ATM protocols are standards-based. The ATM Forum is
The architecture of the ATM model is layered like the OSI
instrumental in defining the standards, including the interfaces
model. ATM behavior may be considered as operationally like
required to operate and manage an ATM network. The
OSI’s physical and data link layers. However, there are several
standards agreed upon by The ATM Forum are reviewed by the
key differences between the physical layer and the data link
International Telecommunications Union, Telecommunications
layer of the OSI model. As illustrated in Figure 23-2, it is in the
Standards Sector (ITU-T), and by the American National
bottom layers of the broadband ISDN model (B-ISDN) that the
Standards Institute (ANSI) before they are made public.
functions of the ATM model are shown.

23-366 3008M300-004
 23 INTRODUCTION TO ATM

The ATM model has three layers; the ATM adaptation layer, 23.2.1 ATM Adaptation Layer (AAL)
the ATM layer, and the physical layer. The ATM adaptation
layer and the physical layer have sublayers. The AAL adapts incoming and outgoing data in accordance
with the services that are being used.

Application Outgoing Cells

Legend: Data from upper layers is adapted to the ATM structure of the
SSCS = Service Specific Convergence Sublayer
CPCS = Common Part Convergence Layer service type; AAL-1, AAL-2, AAL-3/4, or AAL-5.
SAR = Segmentation And Reassembly
Presentation Incoming Cells
The data stream is reconstructed using the information fields.
Cell delay is equalized. Data is adjusted to match the protocol
Management required by the upper layers.
Session Plane
Layer User
Management Plane
Service Table 23-1 shows the classes of service that are identified by
Classes and CCITT, along with some features and examples of each class
Control
Transport Plane Types for comparison.

Higher layers Higher layers Table 23-1: CCITT Service Class and Service Examples
signaling user data
Network End-to-End
Class Bit Rate Connection Mode Service Examples
SSCS Timing
ATM
Adaptation CPCS A Required Constant Connection Voice, Video
Layer Oriented
Data Link SAR B Required Variable Connection Compressed Voice,
ATM Oriented Compressed Video
Layer ATM
Transmission C Not Required Variable Connection Frame Relay, X.25
Physical Physical convergence Oriented
Layer Physical
medium dependant D Not Required Variable Connectionless SMDS, LAN traffic
OSI X Proprietary AAL
Reference B-ISDN/ATM Layers
functions, raw cells
Model

Figure 23-2: Three ATM Layers and Sublayers

3008M300-004 23-367
CXTool User Guide

These classes of service are supported by AAL types. There are
four AAL types named AAL-1, AAL-2, AAL-3/4, and AAL-5.
(Originally there were five AAL types, but three and four were
combined as AAL-3/4.)
AAL-1 supports Class A service. The 48 byte ATM payload is
divided into a one-byte header and 47-bytes of application data.
Header functions include; lost cell detection, byte alignment,
and time stamp. The application data is treated as time-critical.
AAL-2 supports Class B service. The 48-byte ATM payload is
shared among multiple applications. The data from each
application begins with a header followed by its information,
which is allowed to vary in length. The application data is
treated as time-critical.
AAL-3/4 supports Class C and Class D service. The 48-byte
ATM payload begins with a 2-byte message identifier (MID),
followed by 44 bytes of data, and ends with a 2-byte CRC. This
ATM type adapts circuit-switched and circuitless data to the
format of the ATM cell.
AAL-5 supports Class C and Class D service. It was created to
transport frame relay data and TCP/IP data. It is intended to be
simple and efficient.
SAR creates segments that are fixed-length, 48-byte payloads
as diagramed in Figure 23-3).
23.2.2 ATM Layer
The tasks of this layer involve the transport and switching of
incoming and outgoing cells.
Outgoing Cells
A 5-byte header is added to the data received from the ATM
Adaptation Layer, as seen Figure 23-3. The header includes
control and address information. Also, special purpose cells are
marked, and a CRC value is added to the HEC.
Incoming Cells
The information contained in the VPI and VCI cells is
evaluated.
23.2.3 Physical Layer
This is the layer where the signal connects to the medium that
will carry it to the destination. ATM cells are converted to line
signals. Usually, ATM cells are independent of the physical
layer. ATM traffic is readily carried over SONET, T3/E3,
T1/E1, and numerous others.

AAL There are three sublayers in the AAL.

Sublayers
1. Service Specific Convergence Sublayer, providing the interface
to applications
2. Common Part Convergence Sublayer, regenerates timing and
regenerates the clock
3. Segmentation and Reassembly (SAR) sublayer, segmenting
cells for transmission to the ATM layer, and reassembling cells,
back to their original form, for the CPCS layer.

23-368 3008M300-004
 23 INTRODUCTION TO ATM

23.3 ATM Cell Structure ATM network. There are two types of VCs: Permanent Virtual
Circuits (PVCs) and Switched Virtual Circuits (SVCs). A PVC
ATM cells are moving all the time. If there is no payload to is a pre-configured network route in which the connection
move, idle cells must be sent. exists at all times, irrespective of whether or not the line is
Bit Number 7 6 5 4 3 2 1 0 being used. This type of circuit is ideal for situations where the
number of possible destinations is small. An SVC connection,
Generic Flow Control VPI on the other hand, requires call setup procedures prior to
establishing a network route, and the connection lasts only for
VPI VCI
the duration of the call. SVCs are preferred over PVCs where
5 Byte the number of possible destinations is large.
VCI
Header
VCI Payload Type Identifier CLP As illustrated in Figure 23-3, each ATM cell uses a two-part
addressing scheme to route traffic: a Virtual Path Identifier
Header Error Check
(VPI) and a Virtual Circuit Identifier (VCI). VPIs and VCIs are
Payload assigned by the network and they are used to route information
from one ATM switch to another. Since each VPI and VCI are
Payload assigned at each segment within a network, their identifiers
may change at intermediate nodes within a route.
48 Byte
Payload The physical transmission path contains one or more virtual
paths and, as illustrated in Figure 23-4, each virtual path can
contain one or more virtual channels, allowing asynchronous
Payload weaving of cells from multiple connections. The grouping of
channels makes it easier for network management, given that
action needs to be taken only on a single virtual path as
Legend:
VPI = Virtual Path Identifier opposed to all the individual virtual channels.
VCI = Virtual Channel Identifier
CLP = Cell Loss Priority As with all services over the network, users of ATM services
must enter into an agreement with their network providers with
Figure 23-3: ATM Cell Structure respect to various aspects of their ATM connection. The next
section briefly discusses some of the terms and conditions of a
traffic contract between the user and the network.
23.4 Virtual Circuits
A Virtual Circuit (VC) is a logical connection that routes data,
video, or voice traffic from one end-user to another via the

3008M300-004 23-369
CXTool User Guide
Physical Transmission Path
Virtual Path
Virtual Channels
Figure 23-4: Virtual Circuits
23.5 ATM Traffic Contract
Any communication between an ATM access device and the
ATM network is based on a traffic contract between the user
and the network. Such a contract specifies the negotiated
characteristics of the Quality of Service (QoS) guarantees, the
Connection Traffic Descriptors, and the Service Category (see
below). It also defines the agreed upon characteristics of
Virtual Path Connections (VPCs) and Virtual Channel
Connections (VCCs) from one end of the network to the other.
23.5.1 Quality of Service (QoS)
In order to establish a Traffic Contract, QoS parameters must
be defined for each connection. QoS refers to a specific list of
performance objectives for a given connection of a given
Service Category. The QoS parameters all represent
23-370
performance objectives expected from the network for the
duration of the connection. There are essentially three QoS
parameters. They are as mentioned below.
• Cell Transfer Delay (CTD) This is defined as the elapsed time
between a cell exit event at the source and the corresponding
cell entry event at the destination.
• Cell Delay Variation (CDV) This measures the deviation in
CTD between arriving cells.
• Cell Loss Ratio (CLR) This is the ratio of lost cells to total
transmitted cells.
23.5.2 Connection Traffic Descriptor
The Connection Traffic Descriptor includes two key elements.
They are the Source Traffic Descriptors and the Cell Delay
Variation Tolerance (CDVT).
• Source Traffic Descriptors are parameters that describe the
connection’s expected bandwidth use. There are basically three
types of descriptors: Peak Cell Rate (PCR), Sustainable Cell
Rate (SCR), and Maximum Burst Size (MBS).
• Cell Delay Variation Tolerance (CDVT) defines the maximum
amount of CDV that the end-user equipment will introduce and
the amount that a switch with the Usage Parameter Control
(UPC) enabled should tolerate.
23.5.3 Service Categories
The service categories define the network performance
objectives for a given connection. There is a set of parameters
that characterize the performance capabilities of each VCC.
When a VCC is set up, its service category is specified by a
3008M300-004
 23 INTRODUCTION TO ATM

combination of these parameters. The ATM service categories such as mission-critical transaction processing (e.g., banking or
are shown in Figure 23-2. Frame Relay traffic) where data loss is not acceptable.

Table 23-2: ATM Service Categories

UBR, The UBR service is a “best effort” service intended for
Memotec Specified Traffic Parameters Unspecified non-critical applications, which do not require tightly
Service Bit Rate constrained delay and delay variation, nor a specified QoS.
Category PCR CDVT SCR MBS
This service is suitable for applications that are not too
CBR 3 3 demanding, such as the background file transfers of data
VBR 3 3 3 3 applications in which there is minimal service requirement, and
UBR data transfers in which delays and cell loss are tolerated.

On the network side, the terms and conditions of a traffic

CBR, The CBR category is used by connections that require a fixed
Constant Bit amount of bandwidth. This service ensures that the PCR is
Rate available for the duration of the connection. Generally, this
service category is intended for real-time applications (e.g.,
video conferencing) that require tightly constrained CTD and
CDV.
VBR, The VBR service is suitable for any application where the
Variable Bit end-system can benefit from statistical multiplexing and can
Rate tolerate or recover from a potentially small random loss ratio.
There are two types of VBR available;. They are as mentioned
below.
• rt-VBR
Real-Time VBR service guarantees network latency and jitter,
and it is useful for compressed voice and video (e.g., MPEG-2)
traffic, where due to the variable compression ratio, the data is
bursty, but data loss cannot be tolerated.
• nrt-VBR
Non-Real-Time VBR service has an unknown amount of
network jitter and is suitable for short, bursty data messages,
contract are respected by putting in place certain control
measures that ensure flow of traffic. The next section briefly
examines some of these measures.
23.6 Traffic Management
Traffic Management is a set of network actions that monitor
and control the flow of traffic. It prevents streams from
interfering with one another and prevents each stream from
consuming more than its contracted share of network
resources. Traffic management protects the network and its end
system from congestion. There are basically three aspects to
managing ATM traffic: Connection Admission Control, Traffic
Shaping, and Traffic Policing. The following section discusses
each of these aspects.
23.6.1 Connection Admission Control
The Connection Admission Control (CAC) protocol
determines whether or not to accept a connection request (e.g.,
a PVC or a SVC). CAC accepts a connection request only if

3008M300-004 23-371
CXTool User Guide
sufficient resources are available throughout the network and if
the new connection will not affect the QoS of existing
connections. Prior to deciding whether to accept or reject a
connection request, CAC considers the factors listed below.
• Source Traffic Descriptor and QoS of requested connections.
• Traffic contract of connections currently supported.
• Previously allocated bandwidth at port level (logical and
physical).
• Shared buffer and output queue occupancy.
• A user-specific overbooking parameter.
23.6.2 Traffic Shaping
Traffic Shaping regulates traffic before it enters the network. It
ensures that traffic on a given virtual connection conforms to
the negotiated traffic contract, thereby minimizing the
possibility of cells being discarded inside the network. This
action changes the traffic characteristics of a stream of cells on
a VCC or VPC by properly spacing the cells of individual ATM
connections, while preserving the cell sequence integrity of the
connection.
23.6.3 Traffic Policing
ATM switches have the option of using traffic policing (also
known as UPC, usage parameter control) to enforce the traffic
contract between the user and the network. The switch can
measure the actual traffic flow and compare it against the
agreed upon traffic contract. If it finds that the traffic is outside
the terms and conditions of the traffic contract, the switch
either discards the cells or assigns them to a lower priority level
by setting the Cell Loss Priority (CLP) bit equal to one.
23-372
In the event that there is a problem during transmission of data,
the network is informed of such problems. This aspect is
discussed in the next section.
23.7 Operation, Administration, and Maintenance
Operation, Administration, and Maintenance (OAM) is a
network service that ensures the smooth operation of an ATM
network. Special cells provide information relating to cell flow.
The OAM cells can be sent on the network using a header that
uniquely identifies them as such. OAM is required to perform
these functions:
• detect faults
• localize faults
• monitor performance
23.7.1 OAM Flows
There are five OAM flows, identified as F1 to F5. The first
three (F1 to F3) are specific to the nature of the physical
connection. The two upper levels, called F4 and F5, deal
directly with ATM operations. The F4 flow operates at the
Virtual Path (VP) level, and the F5 flow operates at the Virtual
Channel (VC) level.
OAM flows may be either segment or end-to-end. An
end-to-end flow spans from one endpoint of a Virtual Channel
Connection (VCC) to another, or from one Virtual Path
Connection (VPC) endpoint to another. A segment flow only
spans a portion of a VCC or a VPC. Segment OAM flows
facilitate the management of a particular piece of a connection.
For example, if different service providers are involved in an
3008M300-004
 23 INTRODUCTION TO ATM

end-to-end connection, each provider may use segment flows

to support OAM in their particular portion of the connection.

23.8 The Next Step

In the CXTool Configuration Companion, Chapter 8
CONFIGURING ATM identifies the ATM features that are
implemented on Memotec’s CX devices, and explains how to
configure ATM services.

3008M300-004 23-373
CXTool User Guide

23-374 3008M300-004
 24 INTRODUCTION TO FRAME RELAY

This chapter reviews frame relay basics. It provides background

information that is helpful during configuration of CX devices in a
frame relay network.

3008M300-004 24-375
CXTool User Guide

24.1 About Frame Relay 24.3 Permanent Virtual Circuits (PVCs)

Frame relay is a fast, reliable WAN network technology. Frame relay technology is based on the concept of a virtual
Instead of using dedicated, end-to-end connections, it allows circuit (VC). Virtual circuits are two-way logical data paths
the setup of virtual connections for the transmission of frames. between two sites, or end-points.

Frame relay allows each site to connect to every other site
through a single physical interface. Since only a single access
circuit and port are required for each site, there is a significant
reduction in the number of router cards and DSU/CSUs
required.
A permanent virtual circuit (PVC) is a fixed path set up by the
network provider. Once users on either side of a PVC configure
their circuits, they are always available. There is no need for a
procedure to establish a connection nor for a procedure to
disconnect a connection.

24.2 Network Interfaces 24.4 Data Link Connection Identifier (DLCI)

Frame relay networks are have two categories of interface.
They are:
• User Network Interface, labeled UNI in Figure 24-1.
UNI is the interface between user equipment and the network.
• Network-to-Network Interface, labeled NNI in Figure 24-1.
NNI is the interface between network elements within a net-
work or between two networks.
The DLCI is used to identify the virtual circuit between the
user and the network. It has local significance only and does
not relate to any network-wide address. DLCIs are typically
assigned by the network provider and may change as the frame
traverses the network. It is the responsibility of the network to
ensure that the data is routed between the two DLCIs that form
a connection.
Figure 24-2 illustrates how a single virtual circuit may be
assigned a different DLCI value on each end of the connection.

UNI NNI UNI

USER USER
A
Frame Relay Frame Relay
B
24.5 Congestion Control
Network Network
Frame relay reduces network overhead with two simple
congestion notification mechanisms:
Figure 24-1: Frame Relay Interface Categories
• Forward-explicit congestion notification (FECN)
• Backward-explicit congestion notification (BECN)

24-376 3008M300-004
 24 INTRODUCTION TO FRAME RELAY

can relay this information to a higher-layer protocol for

processing. Depending on the implementation, flow-control
To site B, use DLCI 100
B
may be initiated, or the indication may be ignored.
To site C, use DLCI 200
A
To site A, use DLCI 130
To site C, use DLCI 210

Frame USER DATA USER DATA

Relay (FECN=0/BECN=0) (FECN=1/BECN=0)
FRAME
A RELAY B
USER DATA NETWORK USER DATA
(FECN=1/BECN=1) (FECN=0/BECN=0)
END END
DEVICE DEVICE
To site A, use DLCI 160
To site B, use DLCI 300

Figure 24-3: Notifications for Congestion Avoidance

C
24.5.2 BECN Bit

Figure 24-2: Example of DLCI Mapping In Figure 24-3, a frame originating at A is destined for B. The
frame experiences congestion. When the frame arrives at a
Both FECN and BECN are implemented using a single bit frame relay switch and there has been congestion, the switch
contained in the header of a frame. not only sets the frame’s FECN bit, it also sets the BECN bit of
the next frame going back to the origin. When this frame
The frame header also contains a Discard Eligibility (DE) bit, reaches the origin, A, the state of the BECN bit indicates that a
which is used to identify less important traffic that can be particular path through the network is congested. The origin
dropped during periods of congestion. device, A, can then relay this information to a higher-layer
protocol for processing. Depending on the implementation,
flow-control may be initiated, or the indication may be ignored.
24.5.1 FECN Bit

In Figure 24-3, a frame originating at A is destined for B. The 24.5.3 DE Bit

frame experiences congestion. When the frame arrives at a
frame relay switch and there has been congestion, the switch
sets the frame’s FECN bit. When the frame reaches the
destination, in this case B, the state of the FECN bit indicates
that the frame experienced congestion at one or more nodes in
the path from source to destination. The destination device, B,
When congestion occurs, the network must decide which
frames to discard in order to decrease traffic volume. The DE
bit provides the network with a tag that indicates which frames
are eligible for discard. The network discards frames with the
DE bit set before discarding other frames.

3008M300-004 24-377
CXTool User Guide
At the origin, all the DE bits of user frames are set to zero—
meaning that they are not eligible for discard. Routers and
switches may set the DE bit to one. This indicates to other
nodes that, if necessary, the frame may be discarded. For
example, the network switch sets the DE bit to one when traffic
volume exceeds the CIR. See “CIR, Committed Information
Rate” on page 378.
24.6 Quality of Service
As a service, frame relay allows the user to subscribe to a
certain level of bandwidth for traffic travelling between the two
end devices. This section describes the traffic parameters and
how the frame relay service uses them to define service
expectations, which establishes the network’s quality of
service.
24.6.1 Traffic Parameters
CIR, CIR is the committed information rate, the information transfer
Committed rate in bits per second that the network managers commit to
Information transfer under normal conditions. The rate is averaged over a
Rate specified length of time called the committed rate measurement
interval, Tc.
Tc, Tc is the committed rate measurement interval, usually the
Measurement number of seconds used to measure the CIR.
Interval
Bc, Committed Bc is the committed burst size, the maximum number of bits
Burst Size that the user may transmit to the network during the
24-378
measurement interval Tc that the network is committed to
deliver.
Be, Excess Be is the excess burst size, the maximum number of bits by
Burst Size which the user can exceed Bc, during Tc, that the network will
attempt to deliver.
24.6.2 Service Expectations
Frame relay service is defined to expect:
• data that conforms to CIR
• the Bc is transferred with a high probability of success, DE =
0
• data in excess of Bc, but less than Be, is transferred with a
lower probability of success and is more likely to be
discarded if the network experiences congestion, DE = 1
• data in excess of Be is not accorded any specific quality of
service and may be discarded at any time by the network, DE
=1
24.7 PVC Signaling
Frame relay specifies two types of network interfaces; the user-
to-network interface (UNI), and the network-to-network
interface (NNI). PVC signaling at these interfaces is very
similar but not identical.
3008M300-004
 24 INTRODUCTION TO FRAME RELAY

24.7.1 UNI Signaling 24.7.2 NNI Signaling

PVC signaling at the UNI is a link management function that PVC signaling at the NNI is similar to UNI signaling. The
provides the user with status and configuration information default operation is identical to the UNI procedures with the
relating to the virtual circuits operating over the frame relay exception that the STATUS and STATUS ENQUIRY messages
interface. There are three signaling standards: ANSI Annex D, are exchanged in both directions.
ITU-T Annex A, and Frame Relay Forum LMI. UNI signaling
is only applicable at the user interfaces to the network (UNI)
and includes the following main features:
24.8 Multiprotocol Encapsulation
• notification of the addition, deletion, and presence of PVCs
at the interface Multiprotocol encapsulation provides a flexible method for
• notification of the availability of a pre-configured PVC carrying multiple protocols on a given frame relay virtual
circuit. These methods are useful when there is a need to
• a polling sequence to determine if the interface is still active multiplex/demultiplex across a single frame relay connection.
Individual DLCIs on each frame relay Port can be selected to
The link management function transmits these messages using
use Multiprotocol Encapsulation. That is, each DLCI can carry
the reserved DLCI 1023 or DLCI 0, depending on the standard
many different type of traffic (Voice, LLC2, X.25 or LAN)
used. When link management is enabled, the user and network
over the same frame relay circuit.
exchange messages at periodic intervals. These messages are
generally unidirectional but can be configured to be Various mechanisms exist for multiprotocol encapsulation,
bidirectional. The two basic messages are STATUS and depending on the protocol type. These mechanisms are
STATUS ENQUIRY. Figure 24-4 shows the unidirectional addressed in standards such as RFC 1490.
exchange of messages which is the default method, although
bidirectional exchange is possible.

Local Local 24.9 Fragmentation

Management Management
Interface Interface
Fragmentation is the process by which typically large frames
Frame Relay are split into smaller frames before transmission; splitting these
A B
Network frames ensures that sensitive traffic such as voice will not
suffer lengthy delays while waiting for a large frame to finish
Status Enquiry Status Enquiry transmitting. Instead, because of fragmentation, voice traffic is
Status Status
sent as soon as the smaller frame—the fragment—has finished.
Fragmented frames are reassembled at the receiving device
before being transmitted to their final destination.
Figure 24-4: LMI at the User-to-Network Interface (UNI)

3008M300-004 24-379
CXTool User Guide

The CXTool Configuration Companion, in chapter nine, gives

an overview of typical frame relay services that are provided by
Memotec devices, and describes how to configure for those
services.

24-380 3008M300-004
 25 INTRODUCING IP

An overview of IP (Internet Protocol) is provided in this chapter,

focusing particularly on those items that apply to the configuration
of CX devices with CXTool.

3008M300-004 25-381
CXTool User Guide

25.1 About TCP/IP
IP, the Internet Protocol, is actually one of several closely
related protocols collectively known as the TCP/IP protocol
suite. These protocols transfer information across a network
and provide status information about the network itself.
This section briefly reviews the three major protocols as
described in the IP V.4 standards that make up the TCP/IP
suite. They are:
• IP, the Internet Protocol
• TCP, the Transmission Control Protocol
• UDP, the User Datagram Protocol.
network layer protocol providing the addressing information
for each IP packet that routes it across a network.
Once an IP packet has made it to the right network, the routers
in that network can then route it to the appropriate subnet, and
then finally to the host. However, IP does not guarantee
delivery to the host. This is the responsibility of upper layer
protocols.
An IP address is 32 bits in length, which is four bytes of 8 bits.
Refer to Table 25-1.
An IP address is typically formatted as a set of four numbers
that are separated by periods. The numbers are the decimal
values of the bytes that form the address.

Figure 25-1 shows the relationships between these protocols Here is a sample of an IP address: 207.102.120.88.
within the layered model of protocols. This format is known as dotted decimal notation.

IP addresses are hierarchical and were designed to be used for

APPLICATIONS routing. They are divided into two subfields:
• the NET_ID, which is the network identifier subfield
4 TCP UDP • the HOST_ID, which is the host identifier subfield.
3 IP The NET_ID identifies the subnetwork in which the IP is
located. The NET_ID is used for high-level routing between
2 Data Link networks, similar to the way the country code, city code, or
area code is used in the telephone network.
1 Physical
The HOST_ID identifies the specific host within the
Figure 25-1: TCP/IP Protocol, Layered Model subnetwork, similar to the way a specific telephone line is
identified by the last seven digits of a telephone number.
25.1.1 Internet Protocol
IP Address As specified in the protocol, IP address classes provide some
The Internet Protocol (IP) provides the foundation for the other
Classes variety in the number of subnet addresses so that a class can be
major protocols in the TCP/IP family: TCP and UDP. It is a

25-382 3008M300-004
 25 INTRODUCING IP

Table 25-1: IP Address Format

32-Bit IP Address

1 1 1 1 1 1 1 1 1 1 2 2 2 2 2 2 2 2 2 2 3 3

Class
0 1 2 3 4 5 6 7 8 9
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1

A 0 NET_ID HOST_ID
B 1 0 NET_ID HOST_ID
C 1 1 0 NET_ID HOST_ID
D 1 1 1 0 MULTICAST_ID
E 1 1 1 1 0 EXPERIMENTAL_ID

chosen that is appropriate to the number of hosts anticipated. Class C address lies between 192 and 223. Most addresses
The main difference between the classes is the portion of the IP assigned to networks today are Class C.
address bits used by NET_ID subfield and the number of bits
The remaining two address classes, D and E, are used for
remaining for the HOST_ID subfield.
special functions only and are not commonly assigned to
A Class A address always begins with a zero, followed by a individual hosts.
7-bit NET_ID, and then a 24-bit HOST_ID. Thus, the first
number of a Class A address when written in dotted decimal
Subnet Subnet masks are used for routing purposes. A subnet mask
notation always lies between 1 and 126. Class A addresses are
Masks defines the portion of the address that identifies the network
intended for very large subnetworks since the number of
(and/or subnetwork). The subnet mask is written in dotted
unique HOST_IDs per NET_ID is 16,777,214.
decimal and the number of 1s indicates the significant NET_ID
A Class B address has a 14-bit NET_ID and 16-bit HOST_ID. bits. For class A, class B, and class C addresses, the subnet
Class B addresses are intended for moderate sized networks mask and number of significant address bits for the NET_ID
and can address up to 65,536 hosts per network. The first are shown in Table 25-2.
number in a Class B address lies between 128 and 191. Note
Subnet masks can also be used to subdivide a large address
that 127 is reserved for testing.
space or to combine multiple small address spaces. For
A Class C address has a 21-bit NET_ID and 8-bit HOST_ID. example, a network may subdivide its address space to define
These addresses are intended for small networks and can multiple logical networks by segmenting the HOST_ID
address only up to 254 hosts per network. The first number in a subfield into a subnetwork identifier, a SUBNET_ID, and a
smaller HOST_ID.

3008M300-004 25-383
CXTool User Guide

Table 25-2: Subnet Mask Format These sequence numbers increase by one each time TCP puts
Number of
data into a new IP packet. The receiver of the IP packets can
Class Subnet Mask reorder the TCP data by the TCP sequence numbers if the
Mask Bits
packets become shuffled in transit. The receiver can also
A 255.0.0.0 8
determine whether anything is missing. If the sequence
B 255.255.0.0 16 numbers run 1, 2, 5 after reordering, two IP packets-worth of
C 255.255.255.0 24 TCP data are missing. So TCP arranges for the missing packets
to be re-sent.
In the case of a user who is assigned the Class B address space
Another important feature of TCP is its use of port numbers. A
172.16.0.0, the address might be segmented into a 16-bit
port number (also known as a socket) is like another layer of
NET_ID, 4-bit SUBNET_ID, and 12-bit HOST_ID.
address. It is used to identify within the receiving host the
Then, the subnet mask for routing to the NET_ID would be
service that the data should be sent to, and also to identify each
255.255.0.0, while the mask for routing to individual subnets
TCP connection.
within the larger Class B address space would be
255.255.240.0.
25.1.3 User Datagram Protocol
25.1.2 Transmission Control Protocol The User Datagram Protocol (UDP) provides an end-to-end
(connectionless) service. Some applications, such as those that
The Transmission Control Protocol (TCP) is built upon the IP
involve a simple query and response, are better suited to the
layer. TCP is a connection-oriented protocol that specifies the
datagram service of UDP because there is no time lost to
format of data and acknowledgments used in the transfer of
virtual circuit establishment and termination. UDP also has
data. TCP provides two major services that are not provided by
port numbers (sockets) associated with services within a
IP:
system to which data should be sent. UDP does not provide any
• guaranteed delivery of data guarantee for data delivery.
• serialization of data, that is, making sure data arrives in the
same order it is sent 25.1.4 Address Resolution Protocols
TCP guarantees data delivery by having each receiving end Address resolution is necessary to determine the physical port
acknowledge the data it receives. TCP sets a time-out when it address or IP address to which the IP packet should be sent. IP
sends data, and if the data isn't acknowledged within the time- supports three types of address resolution protocols: ARP,
out period, the sending end retransmits the data. RARP, and Inverse ARP.
To ensure serialization of data, TCP uses sequence numbers to
indicate the order in which the data it is sending should appear.

25-384 3008M300-004
 25 INTRODUCING IP

ARP, ARP is the neighbor discovery protocol for TCP/IP networks,

Address and is used to convert an IP address into a physical address (or Routing Table
Resolution hardware address), such as an Ethernet address. When a host Destination Next Hop
194.2.2.0 126.98.12.1
Protocol needs to send a datagram to another host on the same network, 192.1.1.0 126.98.20.1
193.20.1.0 126.98.30.1
the sending application must know both the IP address and Destination ID = 192.1.1.2

hardware address of the intended receiver. Datagram

A host wishing to obtain a hardware address, broadcasts an 192.1.1.0

R
ARP request onto the IP network. The host on the network that
has the requested IP address then replies with its hardware Datagram
AD R R AD
address. The reply information is stored locally for future use.
R
192.1.1.2

Source
IP Network
RARP, RARP performs the opposite task of ARP. That is, it obtains
Reverse ARP the IP address from a hardware address. RARP is used by
LEGEND
Memotec nodes to learn its own IP address. Access
AD Device R Router
Destination

Inverse ARP Inverse ARP is an extension of the ARP protocol. It enables a Figure 25-2: IP Routing
station to learn an IP address corresponding to a logical
interface. Inverse ARP specifically applies to frame relay There are two types of IP routing: static routing and dynamic
stations that may have a Data Link Connection Identifier routing, which are described below. Figure 25-2 is a sample
(DLCI) associated with an established Permanent Virtual network, for illustration.
Circuit (PVC), but do not know the IP address of the station on
the other side of this connection.
25.2.1 Static Routing

Static routing uses a preconfigured routing table that remains in

25.2 IP Routing
IP is an OSI Network Layer protocol, and has the responsibility
of routing packets. It performs this function by looking up a
packet's destination IP NET_ID in a routing table and
forwarding it based on the information in the table. (See
25.1.1 Internet Protocol for an explanation of NET_ID.)
effect indefinitely, unless it is changed manually by the user.
This is the most basic form of routing, and it usually requires
that all machines have statically configured addresses, and that
all machines remain on their respective networks. Otherwise,
the routing tables on all affected machines must be manually
altered by the user to reflect the changes in network topology,
addressing, and routing. Usually there is at least one static
entry for each network interface, and it is normally created at
the time when the interface is added.

3008M300-004 25-385
CXTool User Guide
25.2.2 Dynamic Routing
Dynamic routing uses routing protocols to automatically
update the routing table with routes known by peer routers.
There are several routing protocols in use today, two of the
most popular being RIP and OSPF.
RIP, Routing RIP is a method for routers to exchange routing table
Information information. With RIP, neighboring routers exchange routing
Protocol table information at regular intervals. When a router receives
routing information that includes changes to an entry, it
updates its routing table to reflect the new route. When more
than one route exists for a given destination, RIP routers
maintain only the best route (the route with the lowest metric
value). After updating its routing table, the router begins
transmitting routing updates to inform other network routers of
the change at the next update interval.
RIP uses a single routing metric (hop count) to measure the
distance between the source and a destination network or host.
Each hop in a path from source to destination adds 1 to the
hop-count value.
RIP prevents routing loops from continuing indefinitely by
implementing a limit on the number of hops allowed in a path
from the source to a destination. The maximum number of
hops in a path is 15. If a router receives a routing update that
contains a new or changed entry, and if increasing the metric
value by one causes the metric to be infinity (that is, 16), the
network destination is considered unreachable.
RIP version 2 (RIP-2) is an extension of the original RIP
intended to expand the amount of information carried in the
RIP messages and to add a measure of security. RIP-2 includes
25-386
the subnet mask for each route entry and is therefore useful
when subnetting.
OSPF, Open OSPF is a link state routing protocol that specifies the sending
Shortest Path of Link-State Advertisements (LSAs) to all other routers within
First the same hierarchical area. Information on attached interfaces,
link costs, and other variables are included in OSPF LSAs. As
OSPF routers accumulate link-state information, they use the
OSPF algorithm to calculate the shortest path to each node,
based on the total link cost to a destination.
OSPF is designed to operate within a hierarchy. An example is
shown in Figure 25-3. The largest entity of the hierarchy is the
autonomous system (AS), which is a collection of networks
under a common administration that share a common routing
strategy. The AS can be subdivided into areas.
An OSPF backbone is responsible for distributing routing
information between areas. The backbone itself is also an
OSPF area, so all backbone routers use the same procedures
and algorithms to maintain routing information within the
backbone that any area router would. The backbone consists of
all Area Border Routers, networks not wholly contained in any
area, and their attached routers.
Area Border Routers maintain separate topological databases
for each area. A topological database is essentially an overall
picture of networks in relationship to other routers. The
topological database contains the collection of LSAs received
from all routers in the same area. Because routers within the
same area share the same information, they have identical
topological databases.
3008M300-004
 25 INTRODUCING IP

In the example shown in Figure 25-4, IP and voice traffic are

Autonomous System (AS) being transported simultaneously through an IP tunnel to their
AREA 1 respective destinations.
Voice through an IP Tunnel
IP Tunnel
Host R
AREA 3 Analog
Voice
R* Host
IP
R* Network
Router
R IP
R IP
R
Data Data
R

Figure 25-4: Example of IP Tunneling

R*
BACKBONE (Area 0)
For a description of the operational features of IP supported by
CX products and how to configure them, see Chapter 10
R CONFIGURING IP.
AREA 2 * Area Border Router

Figure 25-3: OSPF Routing Hierarchy

25.3 IP Tunneling
Tunneling is a technology that enables one network protocol to
send its data via another network protocol without protocol
conversion. IP tunneling works by encapsulating a network
protocol within IP packets carried by an IP network. This
concept enables easy transport of non-IP traffic such as frame
relay, legacy traffic, and voice over an IP backbone.

3008M300-004 25-387
CXTool User Guide

25-388 3008M300-004
 26 INTRODUCING ISDN

This chapter describes basic ISDN, the integrated services digital

network.

3008M300-004 26-389
CXTool User Guide
26.1 Preamble
The early phone network was a pure analog system that
connected telephone users directly by an interconnection of
wires. While it was amazing at its inception, it was found to be
inefficient, prone to mechanical breakdown, very susceptible to
noise, and did not lend itself easily to data transmission. Today,
in North America, nearly all voice switching within the
telephone network is digital. However, the final connection
from the local central office to the customer equipment remains
largely analog.
The Integrated Services Digital Network (ISDN) evolved from
the telephony networks, but it is an all digital communications
system. It carries voice and data at the same time. ISDN is able
to use the existing copper infrastructure, fiber and wireless.
Use of ISDN is not restricted to PSTNs (public switched
telephone networks). ISDN may also be transmitted via
packet-based and circuit-based networks.
ISDN specifies interfaces and protocols with which the
customer may choose not only the destination of a connection,
but also the kind of communications service: telephone quality
voice; high quality audio; “best effort data”; large bandwidth
data stream; still images; streaming video; low price; high
performance. The details required to set up these access
choices can be complex, requiring specialized customer
premises equipment (CPE), but the service remains almost
transparent to the user.
Use of ISDN is not restricted to the public switched telephone
network (PSTN). ISDN may be carried by any network that is
packet-based or circuit-based.
26-390
In the mid-1980s, Digital Subscriber Signaling 1 (DSS1)
provided the first public access to ISDN services and was one
of the first global ISDN signaling standards.
This was followed by the QSIG family of standards that grew
out of the needs of corporate telecommunications networks for
a more detailed ISDN signaling standard. QSIG allows one
private integrated network exchange (PINX) to communicate
directly with another PINX. The design of QSIG makes it
particularly suitable as a protocol in peer-to-peer
communications.
In the early years, ISDN and QSIG developed along
proprietary lines like many other telecommunications products
and services. It is only within the last few years that industry
standards have emerged that are intended for public use.
26.1.1 Standardizing ISDN
In the U.S., the two competing companies were AT&T, with its
5ESS (Electronic Switching System), and Northern Telecom
(now Nortel Networks), with its DMS-100. During the 1980s,
there was a concerted effort by ITU-T to develop standards for
ISDN networks. Today, Custom ISDN refers to components and
services that are proprietary to a specific manufacturer. National
ISDN refers to those components and services that conform to
the Bellcore ISDN standards, that is, those in general use in
North America. Standard ISDN refers to those NET3 (Normes
europeene de telecommunication) components and services
that are used in Europe and elsewhere.
However, ISDN signaling is based on the ITU-T Q.921 (also
known as LAPD), and Q.931 (also known as ITU-T
Recommendation I.451). Thus, despite differences in the ISDN
system from one part of the world to another, the signaling
system is quite close to being the same everywhere.
3008M300-004
 26 INTRODUCING ISDN

26.1.2 ISDN Features the QSIG family, became the development underpinning of
other international standards for inter-PINX signaling.
ISDN has many interesting features. The following are notable.
Subsequently, the major manufacturers and vendors of ISDN
1. ISDN builds on groups of standard transmission channels.
PBX products and services also agreed to implement the
2. It handles all types of information, including voice, data, European Telecommunication Standards Institute (ETSI)
studio-quality sound, and images—both still images and standards, which include the following:
moving images in real time.
1. Incorporate PRI as defined in ETS 300 011
3. It handles many devices and many telephone numbers
2. Support Basic Call as defined in ETS 300 172
simultaneously on the same line.
3. Implement the generic procedures as defined in ETS 300 239
4. It supports up to three calls at the same time on the same ISDN
connection. 4. Implement QSIG supplementary services as far as possible
5. It uses switched digital connections.
6. It uses a flexible addressing scheme. 26.1.4 QSIG Features
7. It reduces call set-up time and tear-down time. QSIG is an important protocol among corporate, PINX
applications for signaling and control. Here are some of the
benefits.
26.1.3 Standardizing QSIG
1. Reduced communications costs.
In the 1980s, ECMA—the European association for
2. The ability to manage the network and the services it provides
standardizing information and communication systems—took
according to the evolving need the business.
a leading role in developing a comprehensive suite of standards
based on DSS1 for corporate ISDN networks. This initiative 3. Improved security and confidentiality.
was welcomed by the Public Network Operators (PNOs), PBX
4. Provision of an extensive list of supplementary services to
manufacturers, and vendors. Stimulated by these
enhance business communications: advice of charge; call
developments, the ISO/International Electrotechnical
completion; call forwarding and diversion; call interception;
Commission (IEC) initiated work to generate international
call waiting; call transfer; caller ID.
standards for Private Integrated Services Networks (PISN).
5. The option to customize features provides a competitive edge,
In July 1990 the ISDN PBX Networking Specification (IPNS) particularly for PBX vendors.
Forum was established to systematically support and accelerate
the standardization process. As a result, in October 1993 the
first of the ISO standards, IS 11572, were accepted as an
international standard. IS 11572, which was developed from

3008M300-004 26-391
CXTool User Guide
26.2 ISDN System
In data communications, a channel is a conduit through which
information flows. The information may be user data,
comprising digital or analog content, and network signaling
data.
An ISDN channel, like a channel in any other digital time
division multiplexing (TDM) environment, generally refers to
a cyclic, time slot on a channel. An ISDN channel sends and
receives data in both directions at the same time, that is, full
duplex.
26.2.1 ISDN Channels
There are two basic types of ISDN sub-channels defined for
user communications; the B, and the D.
1. B channel, carries user information including voice, audio,
video, and digital data. A B channel operates at 64 kbps. It is
possible to combine multiple B channels to achieve higher bit
rates.
2. D channel, carries signaling information between the user and
the network. When the service is ISDN BRI the D channel
operates at 16 kbps.
When the service is ISDN PRI the D channel operates at
64 kbps.
The way the above-mentioned channels are used depends upon
the type of access interface or service selected by the user.
There are essentially two type of access interfaces; BRI, the
basic rate interface, and PRI, the primary rate interface.
26-392
26.2.2 ISDN Access Interface Types
ISDN is delivered from a digital switch through one of two
types of user interface: either the Basic Rate Interface, BRI, or
the Primary Rate Interface, PRI.
BRI, Basic The BRI type of ISDN provides the user with access to the
Rate circuit switched network and to the X.25 packet network. The
Interface BRI interface consists of two 64 kbps bearer channels, or B
channels, and one 16 kbps data channel, or D channel. The
format is referred to as 2B+D.
The B channels are used for voice or data services that can be
accommodated by 64 kbps, such as fax, conferencing, and
PCM voice. The D channel is used for call setup, signaling, and
some data associated with network control. Generally, BRI
clients are home-based workers and small enterprises.
In effect, ISDN BRI presents a single physical channel as three
logical channels (2B+D). All signaling tasks are performed on
the D channel. The two B channels may be used for circuit
switched voice or data calls. Some ISDN customer premises
equipment (CPE) allows for the aggregation of multiple BRIs,
thereby increasing available bandwidth further. Moreover,
when applied to X.25 only part of the 16 kbps capacity of the
D channel is needed for signaling, leaving up to 9.6 kbps
available to the customer for packet transmission, which
provides still another communications option.
PRI, Primary The composition of a PRI type of ISDN dependents on whether
Rate T1 standards are being observed, or whether E1 standards are
Interface being observed.
In North America, PRI is supplied as 23 B channels and one D
channel, referred to as 23B+D. All of them, the 23 B channels
3008M300-004
 26 INTRODUCING ISDN

and the one D channel, operate at the same rate of 64 kbps. The 26.3.1 Functional Devices
complete bit stream of this type of PRI operates at the CCITT
designated rate of 1.544 Mbps. As illustrated in Figure 26-1, the customer’s devices reside on
the customer premises side of the connection, labelled CPE.
In Europe PRI is supplied as 30 B channels and one D channel,
referred to as 30B+D. All of the channels, the 30 B channels PSTN CPE
and the one D channel, operate at 64 kbps. The complete bit
ISDN Devices
stream of this type of PRI operates at the CCITT designated - fax (TE1)
NT2
rate of 2.048 Mbps. - phone (TE1)
- bridge (TE1)
ISDN
- router (TE1)
The PRI channels of a T1 or E1 ISDN system are typically
used by medium to large enterprises to connect with the CO of
the PSTN. Virtually all modern telephone and computing non-ISDN Devices
Exchange TA - fax (TE2)
systems can be connected to ISDN through a PRI including Termination - phone (TE2)
PBXs, mainframes and distributed systems, LANs and WANs, - modem (TE2)
multiplexers and ISDN controllers, videoconferencing units,
and so on.
Line
NT1
Termination
Several different devices may be present in the connection
between the customer premises equipment (CPE) and the
network to which the CPE is attached. The next section
examines the relations among ISDN devices and their specific
Legend:
functions.
NT1 Network Termination 1
NT2 Network Termination 2
TA Terminal Adapter
26.3 ISDN Devices and Protocols
Figure 26-1: ISDN Connection
As illustrated in Figure 26-1 and Figure 26-2, an ISDN
connection comprises functional devices and communications
between those devices. The place where one device connects to NT1, Network NT1 is a termination located on the premises of an ISDN
another device is important and many have been named so as to Termination 1 customer. It terminates the ISDN loop.
be clear about exactly which point is being discussed. These
places are called reference points. For each, there is a To provide BRI service, the PSTN provides a connection from
description of the interface at the reference point. one of its ISDN line terminations and delivers it to the
customer in one of two ways.

3008M300-004 26-393
CXTool User Guide

1. A single twisted pair, referred to as the U interface and
commonly used to deliver BRI service in the United States.
These two wires are connected to one side of an NT1. The
other side of the NT1 provides a T interface of four wires.
2. Two twisted pairs, which is a T interface of four wires,
commonly used to deliver BRI service outside the United
States.
The customer may then attach an NT2 or a TA, in accordance
with the devices that are to use the ISDN service.
NT2, Network NT2 is a termination located on the premises of an ISDN
Termination 2 customer. It is usually built into ISDN equipment such as a
PBX, a router, a concentrator, or an automatic call distributor
(ACD).
TA, Terminal A TA is the ISDN device that adapts non-ISDN equipment to
Adapter an NT1 interface. The purpose of the TA is to convert between
the bipolar signaling of the public network and the unipolar
signaling used by computers. The most prevalent use of a TA is
to connect a personal computer to an ISDN line.
26.3.2 ISDN Reference Points
The protocol reference points are used to help describe the way
that protocols function among the many kinds of ISDN
devices. For each reference point there are many protocols that
may be active. The five protocol reference points that are

TE, Terminal This is a general class of equipment that covers both equipment
Equipment that is ISDN-ready, called TE1, and equipment that is not ready
for ISDN, called TE2.

TE1, TE1 devices support the standard ISDN interface directly. A

Terminal TE1 device may connect to an NT1, or connect through an
Equipment 1 NT2 to an NT1—TE1 devices sometimes have NT2 interfaces
built into them. Digital phones, digital faxes, and integrated
voice/data terminals are typical TE1 devices.

TE2, TE2 devices do not support the standard ISDN interface

Terminal directly. A TE2 device needs an ISDN terminal adapter (TA)
Equipment 2 between it and an NT1 interface. TE2 equipment includes
analog telephones, faxes, and modems.

26-394 3008M300-004
 26 INTRODUCING ISDN

commonly defined for ISDN are called R, S, T, U, and V. They R Reference The R reference point lies between the TE2 device and a TA.
are illustrated in Figure 26-2. Point There are no specific standards for the R reference point, so the
TA manufacturer determines and specifies how a TE2 and TA
PSTN CPE communicate with each other.
ISDN Devices
- fax (TE1)
NT2 S and T The S reference point lies between the TE1 or TE2 with a TA
- phone (TE1)
ISDN
- bridge (TE1) Reference and the NT1 devices. The T reference point lies between the
- router (TE1) Points customer site PBX switching equipment (NT2) and the local
S loop termination (NT1). In the absence of the NT2 device—
Exchange non-ISDN Devices which is the case with BRI users—the user-network reference
Termination TA - fax (TE2) point is usually the S/T reference point.
V - phone (TE2)
- modem (TE2)
U T
R U Reference The U reference point is where the local telephone company
Point network arrives at the customer’s premise up to the NT1
Line
NT1
Termination device. This interface is also called the U-Loop because it
represents the loop between the customer’s premise and the
telephone company’s CO. Usually ISDN devices made for the
U interface include a built-in NT1 function.
Reference
Interface Devices
Designation
TA and non-ISDN device 26.3.3 ISDN and the OSI Model
R
S NT1 and NT2, and NT1 and TA, 4 wires Like other telecommunications networks including today’s
NT1 and NT2 telephone network, ISDN employs a number of protocols.
T
Messages between the user and the network, in addition to end-
U US only, Line Termination to NT1, 2 wires
user data, all flow simultaneously over ISDN channels.
V Exchange Termination and Line Termination Although they share the same physical medium, end-user and
user-network signaling use different protocols and are carried
Legend: separately on a D channel.
NT1 Network Termination 1
NT2 Network Termination 2 The D channel makes use of the three lowest layers of the OSI
TA Terminal Adapter model.
1. Layer 1, the physical layer, describes the physical connection
between the terminal equipment on the user side and the ISDN
Figure 26-2: ISDN Reference Points

3008M300-004 26-395
CXTool User Guide

network devices, including the connector, line coding scheme,

framing, and electrical characteristics. The physical connection
Digital Telephones Analog Telephones
is synchronous, serial, and full-duplex. In the case of PRI, the
1110 1111 5003
connection is always point-to-point. In the case of BRI it may 5043
be either point-to-point or point-to-multipoint. The B channel Q
and the D channel share the same physical medium using time Q
5002
division multiplexing (TDM).
PINX 5005
2. Layer 2, the data link layer, describes the procedures that PINX Fax
PRI_QSIG
ensure error-free communication over the physical link, and
defines the logical connection between the user and the
Frame
network. The protocol also provides rules for multiplexing Relay
multiple terminal equipment on a single physical channel CX950 (B) CX1000e (C)

(multipoint) in the BRI environment.

CX1000e (A)
3. Layer 3, the network layer, defines the signaling messages
used to request services from the network. B1 B30
PRI_QSIG
Q 4001

26.3.4 ISDN Q-Reference Point Analog Telephones

PINX 4002
As illustrated in Figure 26-3, “Q” is the reference point for the
signaling points between two PINXs. It shows CX1000e (A) Figure 26-3: Q-Reference Point
receiving 30 calls from the PBX, using PRI_QSIG. The B
channels are carried across a frame relay network to their
respective destinations, although to keep the example simple,
Figure 26-3 shows only the first call, B1, and the last call, B30. 26.4 Next Step
Considered as a powerful and intelligent inter-PINX signaling For a description of the ISDN features supported by CX
system among corporate telecommunications networks, QSIG products and how to configure them, see CXTool
is ideal for meeting the varied communication requirements of Configuration Companion, Chapter 11 CONFIGURING ISDN
corporate clients that range from a secure and confidential AND QSIG.
connection to a host of supplementary services and customized
features.

26-396 3008M300-004
 27 INTRODUCTING T1 AND E1

The basics of T1 (a North American digital transmission standard)

and E1 (a European digital transmission standard) are presented as
a general overview in this chapter.

3008M300-004 27-397
CXTool User Guide

27.1 About T1/E1

CPE CPE

In the telecommunications industry during the decade of the

1960s, there was an important technology development. Phone
company engineers found a way to establish point-to-point
communication between central offices (COs) using digital
methods. They called it T1—an abbreviated way of referring to
digital transmission at 1.544 Mbps (mega bits per second).
Following this breakthrough in North America, a similar Node Node
European system emerged called E1.
T1/E1 T1/E1
Some years later during the mid-eighties, the
CO CO
telecommunications industry experienced several major
changes. New tariffs made it cost-effective for some large telco
customers to bring the T1/E1 capacity in-house. T1/E1
equipment was relocated from COs to the offices of their
customers. This had the benefit of consolidating the
telecommunications traffic into a single T1/E1 circuit. As this
developed it resulted in an all-digital network between the
offices of telco customers.

As illustrated in Figure 27-1, a T1/E1 network is able to handle

telecom traffic from analog and digital phones, as well as Figure 27-1: T1/E1 Network
traffic from other devices such as PCs, terminals, PBXs, host
CPUs, fax machines, video, and local area networks (LANs).
As a group these inputs are referred to as CPE, customer 27.2 T1/E1 Components
premises equipment.

With its digital format, T1/E1 is adaptable to other
transmission media such as satellites, microwaves, and fiber
optics as well as twisted pairs of copper wire that make up
common telephone lines.
As shown in Figure 27-1, there is a wide variety of customer
premises equipment (CPE) that can be connected to a T1/E1
network. The connection is made through a T1/E1 node. Some
care is needed in the use of the term node, however, because
node is often used interchangeably with the term MUX.

27-398 3008M300-004
 27 INTRODUCTING T1 AND E1

27.2.1 T1/E1 Node

E1 Node E1 Node
The node of a T1 or E1 system receives analog or digital CPE connectors CPE connectors
64 kbps 64 kbps
signals from CPEs, converts them into T1/E1 signals, and channels channels
forwards them to a T1/E1 trunk. Figure 27-2 and Figure 27-3 PI1 PI1
show the three main components of a node: the port interface PI2 PI2
PI3 PI3
(PI), the multiplexer (MUX), and the channel service unit - -

(CSU). E1 E1 E1
- MUX CSU CSU MUX -

- -
CO CO
T1 Node T1 Node - -

- -
CPE connectors CPE connectors
- -
64 kbps 64 kbps - -
channels channels - -
PI1 PI1 PI32
PI32
PI2 PI2
PI3 PI3
- -
T1 T1 T1 Figure 27-3: E1 Node
- MUX CSU CSU MUX -

- -
CO CO
- -

- -
standard rate specified for all channels of a T1/E1 system. Thus
- - the output of a T1/E1 PI is always a 64 kbps channel, which is
- -
known as a DS0 channel (digital signal zero channel).
- -

PI24 PI24

Figure 27-2: T1 Node
The components of a T1/E1 node are discussed below.
Port Interface The port interface (PI) provides the mechanical and electronic
(PI) connection between the CPE devices and the T1/E1 node.
Sometimes just called a port, it is usually the connector that
physically attaches to a line. In addition to providing the
connection, the PI also transforms an incoming CPE signal into
a digital signal that the multiplexer can process.
For an analog voice signal to be accurately represented in
digital format, a bit rate of 64 kbps is required, which is the
In the case of a CPE computer connected to a PI, the signal
The channel rates from the computer is received one bit at a time and the channel
for T1 and E1 are output is in the form of eight-bit bytes. When the input to the PI
the same—64 is slower than the output to the channel, the PI produces extra
kbps. bytes in order to keep the data rate up to the 64 kbps standard.
This process is called “byte stuffing”. For example, when the
bit rate to the PI is 9.6 kbps, approximately every fifth byte to
the channel will contain new data.
Sometimes the signals from two or more CPE digital devices
can be sub-rate multiplexed and the combined signal connected
to a single PI. This allows two devices to be connected to one
T1/E1 channel. For example, two telephones using ADPCM
can be connected to one PI and the channel output will be their

3008M300-004 27-399
CXTool User Guide
combined signals running at 64 kbps. For details see
Chapter 7 CONFIGURING VOICE.
Multiplexer Each channel of the node is a 64 kbps digital bit stream. As
(MUX) shown in Figure 27-2 and Figure 27-3, the MUX gathers a byte
from each channel and merges them into a single bit stream. It
does this by dividing the bandwidth of the T1 circuit in a
process called time division multiplexing (TDM). To do this
the MUX uses a precision clock to create a set of time slots. In
the case of T1, typically, there are 24 time slots, one time slot
for each of the 24 channels. In the case of E1, typically, there
are 32 time slots, one for each of E1’s 32 channels.
T1 Standard
In a typical T1 system, like the one shown in Figure 27-2, each
PI channel generates bytes of 8 bits at a rate of 8,000 bytes per
second. The MUX collects the bytes, one byte from each
channel, then adds one bit, and merges them into a frame for
transmission. The one bit that is added to each frame is called
the F-bit. The F-bit identifies the instant when a complete cycle
of channel bytes have been generated and a new cycle is
beginning. Receiving nodes use the F-bit for frame alignment,
which allows the original 24 channels to be reconstituted.
Eight bits from 24 channels totals 192 bits. Adding the F-bit
brings the total to 193 bits in each frame. The frame repetition
rate is 8,000 frames per second, which yields the T1 standard
bit rate of (8,000 × 193 = ) 1,544 kbps.
Notice that at one F-bit per frame and 8,000 frames per second,
there are 8,000 F-bits generated every second. The F-bits form
an eight kbps channel. Since the F-bit itself can be either zero
or one it may be used to carry data for performance monitoring,
or it may be used as a data link.
27-400
The output of the MUX is a continuous stream of frames,
moving at 8,000 frames per second, that is delivered to the
CSU.
When signaling is required, one of the T1 channels may be
setup as a common signaling channel for the use of the other 23
channels. This method is called common channel signaling
(CCS). Alternatively, a method called channel associated
signaling (CAS) may be configured in which one bit is
“robbed” from every sixth frame and used to create up to four
independent signaling channels. This method is known as T1
CAS and accommodates signaling methods such as Switched
56, DDS, and ADN, but limits the T1 payload rate to 56 kbps.
However, a “clear channel”, one of those channels that have no
bits robbed, maintain their payload rate at 64 kbps. For more
about CCS and CAS see 27.2.4 Voice Signaling Methods.
The bits are robbed from frames numbered 6, 12, 18, and 24.
The bits are designated A, B, C, and D, and the same
designations are applied to their signaling channels. When four
individual signaling channels are configured, each one runs at
(1/24 × 8000 =) 333 bps. When two channels are used they run
at (2/24 × 8000 =) 667 bps. One signaling channel using all
four bits runs at (4/24 × 8000 =) 1333 bps.
E1 Standard
An E1 system is set up as frames of 256 bits, running at a rate
of 8,000 frames per second. Typically, each frame is divided
into 32 channels of 8 bits each, as shown schematically in
Figure 27-3. In this arrangement, there are 30 channels for
voice and data payloads, plus one channel for signaling, and
one channel for frame alignment and maintenance.
3008M300-004

The MUX collects one byte from each channel and merges
them into a frame. A continuous stream of 8,000 of these
frames per second is the E1 bit stream.
Eight bits from 32 channels totals 256 bits per frame. The
frame repetition rate is 8,000 frames per second, which yields
the E1 standard bit rate of (8,000 × 256 = ) 2,048 kbps.
The first bit of all frames is named Si and is reserved for
international use. However, in even numbered frames the Si bit
is often used for a CRC-4 (cyclic redundancy check-4).
In even numbered frames, the bits numbered two to eight
always carry the frame alignment signal; 0011011.
In odd numbered frames, bit number two always has the value
one, and bit three is a remote alarm signal.
Also, in odd numbered frames, bits four to eight are named
Sa4, Sa5, Sa6, Sa7, and Sa8. These are spare bits and may be
applied to point-to-point applications or used as a messaging
link for operations and maintenance.
CSU The CSU carries the data stream from the MUX to the T1/E1
trunk, protecting the link, conditioning the data stream, and
supporting troubleshooting. Functions of the CSU are the
following:
• Connects the node to the T1/E1 trunk line
• Protects the T1/E1 equipment
• Conditions the T1/E1 signal
• Monitors the T1/E1 line
• Provides switching for link loopbacks
3008M300-004
27 INTRODUCTING T1 AND E1
The next section briefly examines the different types of frame
formats used to organize data.
27.2.2 Frame Formats
Framing simplifies the organization of data. As mentioned
earlier, all data on a T1/E1 line is transmitted as frames. A few
of the different framing formats are described below.
T1 Frame Today, the most common T1 framing formats are the D4 frame
Formats and the D4 superframe.
D4 Frame
The D4 frame is one of the earliest T1 formats. Each D4 frame
consists of 24 time slots of 8 bits each plus one F-bit, which
brings the total bits in each frame to 193.
D4 Superframe
The D4 superframe format combines 12 frames of the D4 type,
and it uses the F-bits to provide alarm status as well as
alignment. In addition, the D4 superframe format may allow
“robbed bits” from some voice channels to provide signaling.
Extended Superframe (ESF)
The ESF format combines 24 frames of the D4 type, thereby
providing even more information for both framing and
signaling. It uses the F-bits for alignment, messaging (facility
data line), CRC (cyclical redundancy check), and alarm
indication.
27-401
CXTool User Guide

E1 Frame An E1 frame format has 32 time slots of 8 bits each and the
Formats data rate is 2.048 Mbps. The most common E1 framing format
is the E1 multiframe that combines 16 E1 frames (0 to 15).
Some of the E1 multiframes are as follows:
G.704 Table 4a
interfaces)
In this multiframe structure, the format of time slot (TS) 16
within the multiframe for E1 CAS is as follows: the first 4 bits
in frame 0 are used for signaling multiframe alignment. Frame
0 x-bit is a spare bit and Frame 0 y-bit is used for indicating an
alarm condition. Frames 1 to 15 contain ABCD bit values for
voice channels 1 to 30.

“Allocation of bits 1 to 8 of the frame” (Basic frame structure The next section briefly examines line encoding that prepares a
at 2048 kbit/s) digital signal for transmission over a T1/E1 line.
This is the most common multiframe structure. In this format,
bits 2 to 8 of every even frame (namely 0, 2, 4, 6, 8, 10, 12, and
14) contain the frame alignment signal. The first bit of all
27.2.3 Digital Line Encoding
frames is the Si bit that is usually reserved for international use.
Before a signal is transmitted on the T1/E1 line, the
The Si bit is allowed to be used for other purposes, such as
multiplexed signal needs to be line encoded. Line encoding
error checking when configuring CRC-4 mode. For further
functions are handled either by the MUX or the CSU, or both.
details on this framing format, refer to ITU-CCITT’s
Recommendation G.704 entitled: “General Aspects of Digital The most common line encoding methods are discussed below.
Transmission Systems: Terminal Equipments: Synchronous
Frame Structures Used at Primary and Secondary Hierarchical
Levels,” section 2.3.3.2. BRZ The Bipolar Return to Zero Signal (BRZ) is used on T1
transmissions. It inverts the polarity of every other pulse,
G.704 Table 4b preventing streams of pulses with the same polarity that can
cause errors. A zero in BRZ is represented by no pulse. A one,
“CRC-4 multiframe structure” (Basic frame structure at 2048 however, can be a positive or a negative pulse.
kbit/s)
In this multiframe structure, the C1, C2, C3, and C4 bits are
used for error checking. The use of frame alignment signal AMI AMI (Alternate Mark Inversion) ensures that successive ones
pattern, alarm bit, and Sa4 to Sa-8 bits is the same as in G.704 (marks) are alternately inverted (sent with polarity opposite
Table 4a. that of the preceding mark). AMI line coding requires high
pulse density, and no long strings of zeros, that is, no more than
seven zeros should be transmitted consecutively.
G.704 Table 9 (CAS)

“Bit allocation of channel associated 64 kbit/s slot 16 for

B8ZS B8ZS (Bipolar 8 Zero Suppression) uses a pattern of normal
channel associated signaling” (Characteristics of frame
bits and bipolar violations to replace a sequence of eight zero
structures carrying channels at various bit rates in 2048 kbit/s

27-402 3008M300-004
 27 INTRODUCTING T1 AND E1

bits. B8ZS allows long strings of zeros to be transmitted on T1
lines.
HDB3 HDB3 (High Density Binary Three) creates a bipolar polarity
violation (BPV) whenever more than three zeros are
encountered. HDB3 is the E1 equivalent of B8ZS.
There are different voice signaling methods used over T1/E1.
The common ones are discussed below.
27.3 Next Step
27.2.4 Voice Signaling Methods
The two most common signaling methods used on T1/E1
transmissions are Channel Associated Signaling (CAS) and
Common Channel Signaling (CCS).
with advanced voice services. T1/E1 CCS is also used to
exchange information between signaling nodes in a network
(e.g., QSIG and ISDN services). For further details, refer to
ITU-CCITT’s Recommendation G.704 entitled: “General
Aspects of Digital Transmission Systems: Terminal
Equipments: Synchronous Frame Structures Used at Primary
and Secondary Hierarchical Levels,” section 5.1.3.2.2.
The configuration of T1/E1 services on Memotec devices,
together with a list of parameters, is covered in
Chapter 12 CONFIGURING T1/E1.

CAS CAS uses digital E & M, FXS, or FXO signaling. On voice

(Channel circuits carried over T1 links, line supervision often uses
Associated robbed bit signaling (RBS). Depending on which framing
signaling) format is used (D4-SF G.704-Table 5 or ESF G.704-Table 1),
the eighth bit of frames 6, 12, 18, and 24 are called the A, B, C
and D bits, respectively. Combinations of these robbed bits
indicate on-hook, off-hook, and other supervisory signals. For
further details, refer to ITU-CCITT’s Recommendation G.704
entitled: “General Aspects of Digital Transmission Systems;
Terminal Equipments: Synchronous Frame Structures Used at
Primary and Secondary Hierarchical Levels,” section 2.1.3.

CCS, CCS uses a 64 kbps channel for voice signaling. This is a

Common protocol running over a separate packet-switching network,
Channel which carries line supervision and other information, such as
Signaling the phone number of the caller. In North America, the
Signaling System 7 (SS7) method is used to provided users

3008M300-004 27-403
CXTool User Guide

27-404 3008M300-004
 28 INTRODUCING SNA

The set of protocols and procedures known as SNA, Systems

Network Architecture, is described in this chapter.

3008M300-004 28-405
CXTool User Guide

28.1 About Systems Network Architecture

End-User
SNA is a communications architecture that was developed by Application
Application
IBM to support data exchange among its various networking
products. Initially, IBM’s method of interconnection was Transaction
oriented towards hierarchical networking with centralized End-user terminal interface, host applications
Services
Presentation
management and control, as well as centralized end user data Presentation
Data formatting, distributed transactions
flows. Services

Due to the subsequent evolution of PCs and LANs, SNA has Data Flow
Session Chaining, assignment of sequence numbers
evolved from being a strictly hierarchical networking scheme Control
to one that now allows for peer-oriented networks with
distributed management and control as well as distributed data
flows. Transmission
Transport Pacing, encryption, sequence number checking
Control
The main difference between hierarchical communications and
peer-oriented communications is that terminals in a
hierarchical structure are capable only of communicating with Network Path Control Network routing, segmentation
the host, while in a peer-oriented structure they are capable of
both communicating with the host and communicating with
each other.
Data Link Data Link Link management and error recovery

28.2 Architecture
Physical Physical Physical interface with transmission medium
SNA is defined as a set of layers that interact in a hierarchical
fashion much like other communications architectures, such as OSI SNA
X.25 and TCP/IP. Figure 28-1 shows the SNA reference model Reference Reference
and describes the function of each layer. For comparison, the Model Model
OSI (Open Systems Interconnection) model is shown beside it.
Figure 28-1: SNA Hierarchy

28-406 3008M300-004

28.3 Components of an SNA Network
An SNA network consists of two types of components; data
links and nodes.
28.3.1 Data Links
A data link connects nodes in an SNA network. Data link
protocols correspond to layer two of the OSI model. This layer
of the model ensures that data units are delivered successfully
from one network point to the next and flow at the right pace.
Following is a review of these data link types, as they apply to
SNA: SDLC (Synchronous Data Link Control), Token Ring,
Ethernet, Frame Relay, and X.25/QLLC (Qualified Logical
Link Control).
SDLC SDLC (Synchronous Data Link Control), a variation of high-
level data link control (HDLC), was invented by IBM for wide
area connections between IBM equipment. It is considered a
reliable protocol because two stations communicating with it
use all of these actions.
• Sessions are opened and closed with each other, both before and
after sending data.
• Receipt of frames from other stations is acknowledged.
• The flow of data between stations is controlled by limiting the
number of frames that may be sent from one station before they
are acknowledged by the other.
• Recovery from errors is provided and the sending station is
informed of this.
3008M300-004
28 INTRODUCING SNA
SDLC uses the primary station-secondary station model of
communication. Typically in IBM mainframe networks, the
host mainframe is the primary station. Workstations and other
devices are secondary stations. Each secondary station has its
own address. Multiple devices, including secondary stations,
may be attached to a common line in what is known as a
multipoint arrangement, or multidrop arrangement.
SDLC may also be used for point-to-point communication. It is
used primarily for remote communication over corporate
WANs.
Ethernet and Token Ring (IEEE 802.5) and Ethernet (IEEE 802.3) are link-
Token Ring access protocols running under IEEE 802.2 Logical Link
Control Type 2 (LLC2). Although both may be used, Token
Ring networks are the primary means used to provide media
access to LAN-based devices.
All frames used in LLC2 communication have both a source
address and destination address. LLC2-speaking stations
usually communicate over a LAN on which many stations are
communicating. Consequently, each station needs its own
address. Typically, the MAC (interface) address is used
because the LLC2 protocol runs at the link layer.
Like SDLC, LLC2 is a reliable protocol. Between two
communicating stations LLC2 includes the same session
establishment and session continuation characteristics.
Frame Relay There are two different methods of transporting SNA traffic
over Frame Relay WANs; Boundary Network Node (BNN),
and Boundary Access Node (BAN).
BNN does not carry the destination and source MAC addresses
in the network packets. As a result, the BNN format carries the
28-407
CXTool User Guide
fewest number of bits per packet and yields low network
overhead. However, with BNN you must explicitly define a
permanent virtual circuit (PVC) to carry the packet to its
destination.
Although BNN has less overhead, if you have a large number
of PUs (controllers) on the network, configuration becomes
increasingly complicated. The number of PUs should be less
than 32. If the number of PUs is greater than 32, then BAN is
the preferable transport method.
BAN carries the destination and source MAC addresses in its
network packets, and therefore the BAN packet is larger.
X.25/QLLC Qualified logical link control (QLLC) permits SNA commands
to be transmitted over an X.25 network. The use of this
additional link control information is transparent to X.25.
QLLC specifies the mapping between Synchronous Data Link
Control (SDLC) frames and X.25 packets.
When SNA is carried over X.25, it uses the qualifier-bit (Q-bit)
in the X.25 packet header to indicate that special link control
information is present. This information is relevant for SNA
control between the two communicating systems, but it is not
used by the X.25 link control. These qualified packets help
SNA to determine the source and destination addresses of the
two communicating systems as well as providing other
information such as maximum message size.
QLLC is used in the following two situations:
1. when two systems are communicating with each other by
means of SNA over X.25
2. when a system is communicating with a host by means of SNA
over X.25
28-408
28.3.2 Nodes
A node is any system in a network that implements some
portion of SNA. The different types of nodes are:
• host nodes
• communication controller nodes
• peripheral nodes
A collection of host nodes and a communication controller
nodes are called SNA subarea nodes. Subarea nodes form the
backbone of a class of SNA networks called subarea networks.
Host Nodes There are two characteristics of host nodes:
• They act as the network control point.
• They support end-user application programs that execute on the
host.
Communications The characteristics of communications controller nodes are the
Controller Nodes following.
• They manage data communications.
• They collect diagnostics and status information and send it to
the host.
Peripheral Peripheral nodes connect end users to SNA subarea networks.
Nodes There are three types of peripheral nodes:
• Type 1.0 (IBM 5250 device)
• Type 2.0 (IBM 3270 device)
• Type 2.1 (IBM 3270 device)
3008M300-004
 28 INTRODUCING SNA

There are three types of nodes in a peer-oriented network: To classify the services offered by the LUs, numbers are
APPN (Advanced Peer-to-Peer Networking) Network Nodes, assigned, as shown in Table 28-2.
APPN End Nodes, and LEN (Low Entry Networking) Nodes.
Table 28-2: LU Types
28.3.3 Components of Nodes LU Type Function
LU type 2 Interactive terminals attached to a 327x
SNA nodes are composed of physical units and logical units. cluster controller

LU type 3 Printer attached to a 327x cluster controller

Physical Unit The PU manages the resources of a node, such as data links.
(PU) The PU collects and funnels the diagnostic information from LU type 6.2 Used for program-to-program
the remote nodes back up to the host for network control communications when using any-to-any (PU
purposes. 2.1) connectivity

LU type 7 Programs implementing 5250 connectivity

To classify the services offered by the PUs, numbers are
for IBM S/36 or IBM AS/400
assigned to them. The most common PU types are:

Table 28-1: PU Types

28.3.4 Session
PU Type Function
Type 5 Host processor In an SNA network, session is the term used to describe an
exchange of data between two network addressable units
Type 4 Communications controller (NAU). Sessions are established for control purposes, and to
Type 2 Cluster controller for terminal to host
communications

Type 2.1 Any-to-any connectivity between LUs without host

involvement

Logical Units An LU is the entry point through which end-user equipment

(LU) such as terminals or printers obtain access to an SNA network.
Logical units reside within SNA nodes. For example, a cluster
controller node will usually implement one LU for each
terminal and printer it supports.

3008M300-004 28-409
CXTool User Guide

provide end-users with access to host applications. There are

three types of SNA session:

Table 28-3: Session Types

Session
Function
Type
SSCP-PU System Service Control Point-Physical Unit: used to
manage an SNA node and its resources

SSCP-LU System Service Control Point-Logical Unit used to

manage a logical unit (initialize and terminate an
LU-LU session)

LU-LU Used to exchange data between two SNA users,

end to end

28.4 The Next Step

Details of SNA support, the capabilities of Memotec CX
products, and the configuration of SNA is provided in
Chapter 13 CONFIGURING SNA.

28-410 3008M300-004
 29 INTRODUCING ASYNC PAD

This chapter describes Async PAD, the asynchronous packet

assembler/disassembler.

3008M300-004 29-411
CXTool User Guide
29.1 Preamble
As the packet network became prevalent in the 1970s, CCITT
recognized that the majority of terminals in operation were
asynchronous devices. Connecting an async terminal to a
packet network requires an interface. Consequently, standards
were developed for the interface. The standards required that
the interface provide protocol conversion and packet
assembler/disassembler (PAD) functions.
A PAD can receive a character stream from a terminal, can
convert the stream into packets, and forward the character
packets to the X.25 network. The PAD can also receive
character packets from the X.25 network, convert the packets
to a character stream, and forward the character stream to the
terminal.
The standards for the PAD functions were developped
following the 1976 draft of the X.25 standard. The standards
committee came up with recommendations for three
specifications that support X.25 connections with
asynchronous terminal interfaces. The three supporting
specifications are: X.3, X.28, and X.29.
29.2 X.3
The X.3 specification defines a set of parameters that a PAD
uses to identify and control each terminal that is
communicating with it. When a DTE to DCE connection is
established, the PAD parameters determine how the PAD
communicates with the user DTE and vice versa. The user
DTE also has the option of altering the parameters after the
logon is complete.
29-412
The PAD converts the async data of a user device (DTE) to
packets suitable for transmission over a public or private X.25
packet data network. The PAD also does the inverse,
converting X.25 packets to an async data stream. The goal is to
provide a transparent service between DTEs and the network.
Some of the key functions performed by an Async PAD are the
following.
1. Assembles ASCII characters into X.25 packets and forwards
them
2. Provides a data field for user definable call setup information
3. Handles virtual call setup, that is, it establishes calls, it clears
calls, it resets calls, and it interrupts calls
4. Generates service signals
5. Allows edits to PAD commands
29.3 X.28
The X.28 standard defines the procedures that control the data
flow between the user terminal and the PAD.
Upon receipt of an initial transmission from the user DTE, the
PAD establishes a connection and provides services in
accordance with X.28. The user DTE invokes X.28 commands
to the PAD, which may request an X.25 virtual call to a remote
DTE. The PAD is responsible for transmitting the appropriate
X.25 call request packet. X.28 supports the procedures for the
following functions.
1. Place a call.
2. Provide a prompt to user.
3. Exchange data.
3008M300-004
 29 INTRODUCING ASYNC PAD

4. Exchange control information.

X.28 requires the PAD to return a response when a terminal

issues a command to it.

X.28 also specifies that profiles of two types may be defined;

transparent profiles, and simple profiles. These profiles provide
services to the user DTE.

29.4 X.29
The X.29 standard is the procedure under which the PAD and a
remote DTE/PAD exchange control information on an X.25
call. X.29 allows a host computer (DTE) to change the PAD
X.3 parameters of terminals connected to it.

X.29 allows the exchange of information to occur at any time,

either at a data transfer phase or any other phase of the virtual
call.

29.5 Next Step

Chapter 14 CONFIGURING ASYNCHRONOUS PAD
identifies async PAD features that are implemented on
Memotec CX products and includes a detailed explanation of
how to configure Memotec devices.

3008M300-004 29-413
CXTool User Guide

29-414 3008M300-004
 30 INTRODUCING X.25

This chapter provides an overview of X.25 packets, how they are

assembled, and how they are routed.

3008M300-004 30-415
CXTool User Guide
30.1 Preamble
The CCITT’s Study Group VII developed the X Series of
protocols in the seventies. Since 1974, the standards have been
expanded to include many options, services, and facilities.
The X Series recommendations are categorized according to
the functions and services they provide. Those between X.20
and X.32 define data communications network interfaces.
X.25 is a packet switched data network protocol. X.25 is an
international recommendation that defines the exchange of data
and control information between a user device (host) and a
network node. The host device is called data terminal
equipment (DTE). The network node is called data circuit-
terminating equipment (DCE).
X.25 is a connection-oriented protocol that ensures that packets
are transmitted in order. An X.25 network is well suited to
situations where:
1. some delay is acceptable
2. the quality of the lines is poor (X.25’s error correction
capabilities compensate for poor line quality)
3. data volume is relatively small and bursty
30.2 X.25 and OSI
X.25 functions do not match exactly the OSI, 7-layer
architecture. It does operate within the first three layers of the
OSI model, and understanding X.25 within the OSI model is
useful.
30-416
30.2.1 Layer 1 - The Physical Layer
This layer is the transmission layer in which unstructured bit
streams pass over a physical medium. Protocols and interfaces
include X.21, X.21bis, RS-232, and V.35.
• X.21 defines synchronous operations between a DCE and a
DTE, including the connector type and the allocation of pin
numbers to functions. Balanced connections support transfer
rates up to 64 kbps. For unbalanced connections the
maximum transfer rate is 9.6 kbps.
• X.21bis defines operations over leased lines between a DTE
and a packet-switched network, including parameters for
synchronous interworking with V-series modems.
• RS-232 is the EIA (Electronic Industries Association)
standard. It specifies electrical values, procedures, and
functions in the transmission interface between a DTE and
DCE. No connector is specified.
• V.35 is used, typically, to connect between a DTE or DCE
and a high speed carrier with data rates up to T1, 1.54 Mbps.
A 34-pin connector is specified.
30.2.2 Layer 2 - The Data Link Layer
This layer is responsible for making logical connections and
ensuring error-free transmission. Under X.25 either of two
protocols may be used; HDLC—high-level data link control,
and LAPB—Link Access Procedure-Balanced.
The frame structure of HDLC and LAPB is the same: flag
field, address field, control field, information field (header +
payload), FCS field (frame check sequence), and flag field. The
difference between these two protocols is in the structure and
contents of the control field.
3008M300-004
 30 INTRODUCING X.25

30.2.3 Layer 3 - The Network Layer 30.4 Next Step

This layer provides the addressing and control functions for
For the X.25 features that are implemented on Memotec’s CX
moving data to and from the network. Data from OSI layers
devices and an explanation of how CX devices are configured
seven to four, is combined with a header and assembled into an
for X.25 services, refer to Chapter 15 CONFIGURING X.25.
X.25 packet for sending. Received packets have the header
removed and the data is passed to the upper layers.

The protocol used is X.25 PLP—Packet Level Procedure,

which supports packet sequencing, flow control, error
detection, and error recovery.

The are many kinds of X.25 packets. A sample of a few of

these types are; the call setup packet, the data packet, the
interrupt packet, and the diagnostic packet.

30.3 Interfaces of X.25

The connection types offered by X.25 include the following.
1. A Virtual Circuit (VC) is a logical connection between DCEs.
2. A Permanent Virtual Circuit (PVC) is a logical connection
between two DTEs that is set up and remains viable until it is
explicitly torn down. It offers efficiency in communication
because packets do not need to be addressed, which eliminates
some message overhead.
3. Switched Virtual Circuit (SVC) creates a connection between
two DTEs for the duration of a data transfer, and as such
requires call setup (connect) and call clear (disconnect)
procedures. Each DTE on the network is given a unique DTE
address, which can be used much like a telephone number.
4. Fast Select enables user data to be included in call request/
connected and clear packets.

3008M300-004 30-417
CXTool User Guide

30-418 3008M300-004
 31 INTRODUCING IPX

This chapter provides a general view of IPX, the Novell Netware

networking environment.

3008M300-004 31-419
CXTool User Guide

31.1 Preamble
NetWare
Application
Applications
IPX, an abbreviation for Internetwork Packet Exchange, is NetBIOS
actually one of seven NetWare protocols that enable a packet to Applications
be routed to its destination. However, it is important to note Presentation
that the abbreviation IPX is often used to refer to the Netware
SAP
system—the architecture and the protocols—as a whole. Session NCP
NetBIOS
Novell
Transport
31.2 IPX Protocol Architecture SPX

Novell
The Internet Packet Exchange (IPX) protocol was adapted by Network NLSP RIP
IPX
Novell from the Xerox Network System (XNS) Internet
Datagram Protocol (IDP). Data Link
MAC Protocols
IPX is a connectionless, datagram-based protocol that delivers (Ethernet, Fast Ethernet, Toket Ring)
packets across the internet and provides NetWare workstations Physical
and file servers with addressing and internetworking routing
services. As illustrated in Figure 31-1, IPX resides at the OSI Reference Netware Protocols
network level (OSI Layer 3). Model

IPX and the sequenced packet exchange (SPX) together
provide the delivery service for Netware traffic on a LAN.
31.2.1 IPX Addressing
IPX is responsible for the delivery of message packets from
sender to receiver. This may include routing a packet through
intermediate destinations. However, there is no guarantee or
verification of successful delivery.
SPX supervises the packet delivery process. That is, SPX
verifies packets and acknowledges packets. It also provides
error-checking capability and can force a message to be re-
transmitted when it is not acknowledged, or when it arrives
distorted.
Figure 31-1: OSI Model Compared With Netware Protocols
IPX uses the physical address assigned to the network interface
card when a packet is to be sent to an address within the
segment. Otherwise, a 12-byte IPX network address is used. It
consists of a 4-byte network number, a 6-byte node number,
and a 2-byte socket number IPX Internetwork Addressing
The basis of IPX internetworking addressing is the numbering
of network segments and the numbering of servers. These
numbers are assigned during the installation and configuration
process.

31-420 3008M300-004
 31 INTRODUCING IPX

Each network segment on a NetWare internetwork must be
assigned a unique network number, sometimes called the
external network number. Also, each server must be assigned a
unique internal network number. These network numbers are
used by routers to forward packets to their final destination. An
example is given in Figure 31-4.
Normally within a node there are multiple processes are
running. When a process needs to communicate on the
network, it requests that a socket number be assigned to it. As a
result, each process is associated with a socket number. Then,
when a packet is received it is passed on to the process with the
corresponding socket number. See the scenario in Figure 31-4.
31.2.2 Reserved Network Numbers
There are three network numbers that are reserved and must
not be used to identify a network. The reserved network
numbers are: 0x0, 0xFFFFFFFF, and 0xFFFFFFFE. The
special meanings of these numbers are shown in Table 31-1.
Table 31-1: IPX Reserved Network Numbers
Reserved
Definition
Number
0x0 Address of the local segment. When a router receives a
packer whose destination network number is 0 (zero), it means
that the packet’s source and destination nodes are attached to
the same segment.
0xFFFFFFFF All routes request. When a router receives a packet with this
destination network number it sends to the requesting router a
list of all the routes it knows about.
0xFFFFFFFE Default route. If this destination is advertised, IPX packets are
forwarded to it when the destination network is unknown.
If another router on the network is advertising 0xFFFFFFFE,
then the packet is forwarded to it. Otherwise the packet is
discarded.
This default route is not advertised dynamically. The router must
be configured to advertise it as a static route.

31.2.3 IPX Packet

The IPX packet consists of two parts: a 30-byte header and

data. The network, node, and socket addresses for both the
destination and the source are held within the packet’s IPX
header. Although in theory, IPX packet size may go up to
65,535 bytes, in practice, the media access control (MAC)
constraints will typically limit the actual maximum packet size
allowed, to less than 65,535 bytes. This would be the case if,
for instance, the IPX layer is handling Ethernet II packets
which are limited to a data size of 1500 bytes.

3008M300-004 31-421
CXTool User Guide

As illustrated in Figure 31-2, the IPX header is placed after the information packets to move single packets from one location
MAC header and before the packet data. to another on an internetwork.
MAC Protocol
Envelope IPX Packet

Others
Checksum (2 bytes)
Packet Length (2 bytes) Novell Upper
Transport Control (1 bytes) NetBIOS
NCP
Layers
Packet Type (1 bytes) Socket 0x455 Socket 0x451
MAC Header Destination Network (4 bytes) IPX SAP SPX
Destination Node (6 bytes) Packet
Header Socket 0x452
Destination Socket (2 bytes)
Data
Source Network (4 bytes)
Source Node (6 bytes)
MAC Trailer Source Socket (2 bytes)
RIP IPX NLSP Network
Higher-Level Protocol Headers Layer
Socket 0x453 Socket 0x9001

Packet Data

MAC Protocols
(Ethernet, Fast Ethernet, Token Ring)
Figure 31-2: IPX Packet Structure NIC Drivers
Data Link
Layer

31.3 IPX Routing NIC A NIC B NIC C

Node Node Node
Network segments are interconnected by routers. By definition, 101 201 999
routers are network layer devices. As illustrated in Figure 31-3, Physical
IPX performs the network layer’s tasks with the help of Router Network 01 Network 02 Network 99
Layer
Information Protocol (RIP) and Service Advertising Protocol
(SAP). These tasks include addressing, routing, and switching Figure 31-3: Internal Components of an IPX Router

31-422 3008M300-004
 31 INTRODUCING IPX

Since IPX is always dynamically routed, and the routing

architecture works by learning network addresses
automatically, there is usually no need for any action in the B
setup of an IPX network in order to get routing to function. Network
A Server
Figure 31-4 diagrams an IPX network as an example. Workstation
Node number
In Figure 31-4, A and D are workstations, and B, C, and E are 0x C0-20-87-01-00-02
Node number Internal Network Number
NetWare servers. C has two Ethernet cards and acts as an IPX 0x F0-10-00-01
0x 00-20-87-01-01-02 Network number
router between the two networks segments. 0x 00-10-00-01

NetWare servers broadcast routing information and service

advertisements to all nodes on the network segment using RIP Node number
C 0x A0-20-87-01-00-02
and SAP. Node C forwards this information to connected
networks, so that workstations are made aware of the addresses Internetworking Internal Network Number
Server 0x F0-10-00-02
of the file and print servers that are available.
Node number
As an example, A wants to access the file server at E. A would 0x B0-20-87-01-00-02
have been made aware of E’s address through service
advertisements broadcast by C. To learn how to reach E, A
broadcasts a routing request. C receives this request and returns Network number
0x 00-20-00-01
its own hardware MAC address (0x A0-20-87-01-00-02) which
is applicable for the network 0x 00-10-00-01. A then addresses D Node number
0x D0-20-87-01-03-02
an IPX packet to E, which specifies E’s network number (0x Workstation
Internal Network Number
00-20-00-01) and MAC address (0x D0-20-87-01-03-02). 0x F0-20-00-01
C receives this IPX packet and transmits it to E on the network E
0x 00-20-00-01. Node number Network
0x 00-20-87-01-02-02 Server

31.3.1 RIP

NetWare routers use RIP (router information protocol) to Figure 31-4: IPX Network Scenario
create and maintain a database of internetwork routing
information, commonly called a router table. Although the information packet, namely the transport time field. This
NetWare RIP is based on Xerox’s RIP, Novell differentiates change makes the two types of RIPs incompatible.
IPX RIP from XNS RIP by adding another field to the routing

3008M300-004 31-423
CXTool User Guide

RIP RIP broadcasts facilitate the exchange of routing information

Broadcasts by performing these functions.
IPX Packet RIP Packet Network Entry
• Workstation can locate the fastest route to a network number
by broadcasting route request
IPX Header(30 B) Operation(2 B) Network Number
(4 B)
• Routers can request routing information from other routers, · Packet Type = 0x 01
Network Entry #1
(8 B) Numberof Hops(2 B)
to update their own internal tables, by broadcasting a route · Destination Socket = 0x 04-53
request Number of Ticks
(2 B)

• Routers can respond to route requests from workstations and

other routers
• Routers can make periodic broadcasts to ensure that all other Data
routers are aware of the internetwork configuration
• Routers can make broadcasts whenever they detect a change
in the internetwork configuration

Network Entry #50

RIP Packet A RIP packet contains many fields. RIP packets are identified
in the IPX header as Packet Type 1 and Socket Number 453, as
shown in Figure 31-5.
The Operation field can be followed by one or more network
entries. Each network entry is 8 bytes in length. An RIP packet
can contain a maximum of 50 network entries. Thus,
depending on the amount of network information contained in
the packet, the size of an RIP packet will vary anywhere from a
minimum size of 40 bytes (IPX header plus one RIP network
entry) to a maximum size of 432 bytes (IPX header plus 50
entries).
31.3.2 SAP
SAP (Service Advertising Protocol) allows service-providing
nodes such as file servers, print servers, and gateway servers to
advertise their services and addresses. SAP makes the process
(8 B)
Figure 31-5: RIP Packet Structure
of adding and removing services on an internetwork dynamic.
As servers are booted up, they advertise their services using
SAP, and when their services are no longer available, they use
SAP to indicate so.
SAP Through SAP, clients on the network can determine what
Broadcasts services are available on the network and obtain the
internetwork address of the node that has the server where they
can access those services. This is an important function
because a workstation cannot initiate a session with a service
provider without first having that server’s address.
A gateway server, for instance, will broadcast a SAP packet
once every minute onto its network segment. The SAP agent in
each router on that segment copies the information contained in

31-424 3008M300-004
 31 INTRODUCING IPX

the SAP packet into an internal table, commonly referred to as
a server information table. Since the SAP agent in each router
keeps up-to-date information on available servers, a client
wanting to locate the gateway server can access a nearby router
for the correct IPX address.
SAP Packet SAP packets are identified in the IPX header as Packet Type 4
Structure and Socket Number 452. There are many fields in a SAP
packet. They are show in Figure 31-3.
• Get Nearest Server Response
Depending on the type of operation selected, the Operation
field is followed by at least a single field or any number of
fields up to seven. When the type is a SAP request, only the
first Service Type field is included in the packet. When the type
is a SAP response, the number of entries is allowed to be any
number between one and seven. As a result, SAP response
packets may vary in size from 96 bytes (IPX header plus one
network entry) to 480 bytes (IPX header plus 7 entries).

IPX Packet SAP Packet Server Entry

SAP Filter The SAP filter is one of three IPX filters. It controls which
SAP services the router accepts and advertises, and which Get
IPX Header(30 B) Nearest Server (GNS) response messages it sends out. As a
· Packet Type = 0x 04 result, information about a service provided by a particular
Operation(2 B)
· Destination Socket = 0x 04-52 Service Type
(2 B) source can be prevented from being stored in a router’s SAP
Network Entry #1
(64 B)
Server Name
(48 B) database by SAP filtering. When a router receives a service
broadcast packet, the router compares the source server name
Network Address
(4 B)
and service type with that in the SAP filtering definitions
Node Address
(6 B) (composed of a service type and a service name). If the packet
Data Socket Address
(2 B) matches a definition, a filtering and forwarding action is
Hops to Server
(2 B) applied, otherwise the service information is added to the
router’s SAP database.

Network Entry #7
(64 B)

Figure 31-6: SAP Packet Structure

31.4 Next Step
Chapter 16 CONFIGURING IPX identifies IPX features that
The Operation field in a SAP packet can perform any of the are implemented on Memotec CX products and includes a
following functions: detailed explanation of how to configure Memotec devices for
• Request IPX services.
• Respond
• Get Nearest Server Request

3008M300-004 31-425
CXTool User Guide

31-426 3008M300-004
 32 INTRODUCING MLPPP

This chapter describes MLPPP, the multi-link point-to-point

protocol, that combines parallel data channels to achieve higher
throughput.

3008M300-004 32-427
CXTool User Guide
32.1 Preamble
A key component of MLPPP is PPP, the Point-to-Point
Protocol. PPP is the Internet standard for transmitting IP
packets over serial lines.
It is important to note that PPP is not just one protocol. It is a
protocol suite that controls both physical and logical interfaces.
PPP does three things:
1. It encapsulates the data from other protocols.
2. It establishes a data-link connection with an LCP (Link Control
Protocol).
3. It establishes a network-layer connection with an NCP
(Network Control Protocol.
MLPPP combines multiple PPP links to achieve higher data
transmission rates with throughput that amounts to the sum of
the individual links. Though not the only standard for
combining links, MLPPP is the Internet standard.
MLPPP is sometimes referred to as Multilink PPP, or MPPP.
32.2 About MLPPP
MLPPP is a software method for splitting datagrams and
transmitting them over multiple logical data links. At the
destination the datagrams are recombined, and arranged in
their original sequence.
The general term for using multiple links in this way is
multilink. There are many multilink protocols and MLPPP is
one of them.
32-428
32.2.1 Multilink Structure
The goal of multilink operation is to coordinate multiple
independent links between a particular pair of systems, and to
provide a virtual link with greater bandwidth than any of the
constituent members.
When PPP links are combined in this way they are called
bundled links, or a bundle. A bundle is considered to be one
logical connection.
MLPPP packets to be transmitted using the multilink
procedure are encapsulated according to the rules for PPP.
The bundled links can be different kinds of physical links, such
as multiple async lines, and a bundle may also include
instances of multiplexed links, such as ISDN, X.25, and frame
relay. For example, mixtures of BRI, dial-up async line, and
X.25 SVC can be used.
Whatever the combination of links may be, the resulting
logical link is named using the pair of identifiers of the two
systems that are connected by the bundle.
The data rates of the channels that makeup a bundle should be
similar, otherwise the faster channels must wait for the slowest
channel.
NOTE: When reliable multilink operation is required, PPP
Reliable Transmission must be negotiated on each
member of the bundle prior to the use of the multilink
protocol. See 32.2.4 MLPPP and Reliable
Transmission.
3008M300-004

32.2.2 MLPPP Header
Maintaining the original order of the packets is important.
MLPPP does this by means of a four-byte sequencing header
on each packet, and simple synchronization rules. With a
unique header the packets can be divided among the
components of the bundle and reliably reconstructed at the
receiving system. Synchronization rules ensure that the
reconstructed packets reproduce the original data exactly.
Together, these characteristics achieve the goal; more packets
are sent, latency is reduced, and there is a potential increase in
the effective MRU.
32.2.3 Establishing an MLPPP Link
The process begins with the establishment of a point-to-point
link. First, there is a link setup negotiation during which each
end sends link control protocol (LPC) packets. This serves as a
configuration for the link setup phase.
Once the link has been established, PPP provides an
authentication phase in which the authentication protocols can
be used to determine identifiers for the systems that are
connected by the link.
MLPPP is a multilink operation. It is invoked by setting an
LCP option. This causes each system to indicate to its peer that
it is capable of combining multiple physical links. This
negotiation denotes three things about the system offering the
option.
1. It is capable of combining multiple physical links into one
logical link.
3008M300-004
32 INTRODUCING MLPPP
2. It is capable of receiving upper layer PDUs that are fragmented
using the multilink header, and reassembling those fragments
back into the original PDU for processing.
3. It is capable of receiving PDUs of size N octets, where N is
specified as part of the option even if N is larger than the MRU
for a single physical link.
Once multilink has been successfully negotiated, the PDUs are
sent using the multilink header. The sending system is free to
send PDUs created from encapsulated data, as well as PDUs
that are created from data that is fragmented and encapsulated.
32.2.4 MLPPP and Reliable Transmission
PPP Reliable Transmission means that ISO LAP-B (link access
procedure-balanced) is to be used. If reliable multilink
operation is desired, PPP reliable transmission must be
negotiated separately on each link of the bundle prior to the use
of the multilink protocol.
The bundled links may be terminated according to normal PPP
LCP procedures, using LCP terminate-request and terminate-
ack packets on the member link. However, if the multilink
procedure is used in conjunction with PPP reliable
transmission, and any link of the bundle is not closed
gracefully, then packets that violate the rule that requires
increasing sequence numbers should be expected to produce
errors.
32.2.5 MLPPP and ISDN
Basic Rate ISDN (BRI) and Primary Rate ISDN (PRI) both
allow two connected systems to have more than one channel
open between them. Opening multiple channels between
systems can give users additional bandwidth on demand.
32-429
CXTool User Guide

Although extra bandwidth means extra cost, when capacity and

timely delivery are important then the extra bandwidth choice
is made.

32.3 Next Step

Chapter 17 CONFIGURING MLPPP identifies async MLPPP
features that are implemented on Memotec CX products and
includes a detailed explanation of how to configure MLPPP on
Memotec devices.

32-430 3008M300-004
 33 INTRODUCING BRIDGES

A bridge is used to interconnect digital networks. This chapter

describes the functions of bridges, and how a bridge learns about
the topology of the network to which it is connected.

3008M300-004 33-431
CXTool User Guide

33.1 Preamble Table 33-1: OSI Layers and Internetworking Devices (cont.)
Networking
OSI Layer Device Function
Networks that have more than one segment can interconnect Device
the segments using a router, a switch, or a bridge, depending on 3 Network Router Connects networks that may
the functions required. be of the same type or of
different type
Commonly, a bridge is used to connect a LAN and to a WAN in
order to reduce unnecessary traffic. It does this by examining, 2 Data Link Bridge, Switch Connects segments, isolates
at both ends of the bridge, the destination address of each traffic
packet. A packet crosses the bridge only if its destination is on
1 Physical Repeater Boosts voltage, converts from
the other side.
Transceiver one medium to another (e.g.,
10BASE-2 to 10BASE-T)
A bridge is usually low in cost, able to handle high bandwidth,
and presents low delay to traffic.
To make choices about how to handle a packet, the bridge uses
an algorithm. There are two that are significant; the spanning
33.2 Bridge Functions tree algorithm, and the source routing algorithm. Some bridges
implement both algorithms, but some implement only one of
As shown in Table 33-1, there are several types of them.
internetworking devices. The bridge is one of these. Bridges
Figure 33-1 shows a bridge that connects a LAN to a WAN,
operate at OSI layer 2, which is the data link layer. Layer 2 is
and illustrates the descriptions that follow.
sometimes called the MAC (Media Access Control) layer. The
purpose of layer 2, from the point of view of a bridge, is to
move packets over a network segment, or link.
Bridge
WAN
Table 33-1: OSI Layers and Internetworking Devices
Networking
OSI Layer Device Function
Device
7 Application
LAN
6 Presentation

5 Session Firewall Monitors block session Figure 33-1: Bridge Between LAN and WAN

4 Transport Gateway Translates network protocol

33-432 3008M300-004

33.3 Spanning Tree Algorithm
When the spanning tree algorithm is implemented, the bridge
makes use of the source address field and the destination
address field in the header of the packet. With these the bridge
Filtering The filtering function of the spanning tree algorithm compares
determines whether to filter the packet or to forward it, and
learns the topology of the network.
In addition, the bridge maintains a forwarding database (FDB)
that is stored in the bridge. The spanning tree algorithm uses
the FDB to make choices; whether to filter or forward a packet,
and whether to update the FDB itself.
A bridge that employes the spanning tree algorithm is normally
associated with an Ethernet network and so it is sometimes
called an Ethernet bridge. Ethernet bridges usually implement
the IEEE 802.1d spanning tree algorithm whose purpose is to
ensure that frames are not forwarded through redundant
connections between bridges that form a never-ending loop. In
a network, these bridges form a transparent spanning tree that
forces a tree structure on the network and disables routes that
are redundant, which prevents loops.
33.3.1 Bridge Filtering and Forwarding
The bridge in Figure 33-1 handles traffic in both directions,
from LAN to WAN and from WAN to LAN. This means that a
packet on the LAN end of the bridge whose destination address
is on the WAN is forwarded to the WAN. A packet on the WAN
Forwarding The forwarding function of the spanning tree algorithm
end of the bridge whose destination address is on the LAN is
forwarded to the LAN.
Similarly, a packet on the LAN end of the bridge whose
destination address is on the LAN is filtered out, and prevented
from entering the WAN. A packet on the WAN end of the
3008M300-004
33 INTRODUCING BRIDGES
bridge whose destination address is not on the LAN is filtered
and not allowed onto the LAN. In this way, extraneous traffic is
significantly reduced.
the destination address of a packet with the bridge’s FDB.
When the comparison shows the destination is on the same side
of the bridge as the source then the packet is filtered. The term
filter is used here in the sense of “filter out”, meaning the
packet is not allowed to cross the bridge.
The upper half of Figure 33-2 diagrams the filter/forward
decision flow.
The treatment of packets by the spanning tree’s filter or
forward determination is shown in Table 33-2.
In a system like the one shown in Figure 33-1, a packet whose
source and destination are on the same LAN, is filtered by the
bridge and prevented from being added to the traffic on the
WAN. A packet on the WAN who’s destination address is not
on the LAN is also filtered and not passed onto the LAN.
A packet from the LAN whose destination address is found in
the FDB and whose incoming port ID is the same as the port ID
in the FDB is discarded because it is assumed to be a message
to itself.
compares the destination address of a packet with the bridge’s
FDB. When the comparison finds the destination in the FDB,
the packet is forwarded to the port associated with the address.
The packet is also forwarded if there is no entry in the FDB.
33-433
CXTool User Guide

Packet received without

Table 33-2: Bridge Filtering and Forwarding
errors on port A
Destination Incoming Port
Packet Source Packet Treatment
Address ID
Dest addr FDB LAN Not found in n/a Forward on all ports
Forward packet on all
of packet found No Addr. Port ID Age
ports except A FDB
in FDB?
LAN Found in FDB Not same as Forward on Port ID from
Determine Filter/Forward

Yes
packet FDB
Incoming LAN Found in FDB Same as Discard
Forward packet on
port ID is No
correct port packet
port A?
WAN Found in FDB Forwarded to LAN
Yes

WAN Not found in Filtered

Discard packet FDB

The upper half of Figure 33-2 diagrams the filter/forward

decision flow. The treatment of packets by the spanning tree’s
filter or forward determination is shown in Table 33-2.
Source addr Add source addr and
of packet found No port ID to FDB
in FDB? Set age = 0 In the sample system shown in Figure 33-1, a bridge is
connected between a LAN and a WAN. When the destination
Yes address a each packet from the LAN is found in the FDB, then
the packet is forwarded to the WAN for delivery.
Port ID
FDB Learn

Update port ID
of packet matches No
Rest age
FDB?
33.3.2 Bridge Learning
Yes
The learning function of the spanning tree algorithm refers to
Reset age the ability of a bridge to automatically update its FDB. This is
done using the source address of the packets that appear on the
ports of the bridge. As sketched in Figure 33-2, the record in
the FDB includes a field for the address, a field for the ID of
the port on which the packet was received, and a field for the
End age. The age of a record is used to ensure that records in the
FDB are recent. Old ages are deleted by the algorithm. The
Figure 33-2: Bridge FDB Flow: Filter/Forward and Learn

33-434 3008M300-004

lower half of Figure 33-2 diagrams the flow of the learn
decision.
If the source address is not found in the FDB, then a new
record is added to the FDB, including its port ID, and an age
value of zero.
If a record for the source address is found in the FDB and the
new port ID is the same as the port ID field, then the age is
reset to zero. If the new port ID is not the same as the port ID
field, then it is replaced by the new port ID, and the age is reset
to zero.
33.4 Source Routing Algorithm
33.4.1 Token Ring
A bridge in a Token Ring network uses an algorithm called
source route bridging. The header of each packet carries all the
routing information required to deliver it to its destination.
Before a station can send a packet, it must have a record of the
complete route to the destination, that is, the ring numbers and
bridge numbers as well as the destination address.
To do this the source route algorithm first sends a search frame,
an LLC Test, onto its LAN. A search frame is not forwarded
outside the LAN. If the destination replies to this search frame
then the destination is on the LAN and no additional routing
information is required. Packets with payloads can be sent
using the destination address and no other routing information
in the header.
If the destination does not reply to the search frame, then the
destination must be beyond the LAN. Now the source route
3008M300-004
33 INTRODUCING BRIDGES
algorithm sends a route discovery frame. A route discovery
frame is forwarded by all bridges, and, if the destination exists
then the packet must reach it. As the frame passes each bridge
the routing information is added to a route information field
(RIF) its header. When the discovery frame finds the
destination, the destination station inverts the route sequence
and records it. The inverted route is used to send a reply to the
source station. The reply contains the route of the discovery
frame from source to destination. The source station records
the route and uses it to send payload packets.
The source station typically receives many such replies, and
records the route taken by the first reply received. The first
reply received has the shortest round-trip, and so is assumed to
be the best route.
The source route algorithm has the advantage of trying all
available links between bridges, from which the fastest route is
used. The main disadvantage is that any change in network
connectivity results in the loss of a session.
33.5 Next Step
Chapter 18 CONFIGURING BRIDGING presents typical
configurations that are implemented on Memotec CX products
and includes a detailed explanation of configuring a Memotec
device.
33-435
CXTool User Guide

33-436 3008M300-004
 34 INTRODUCING HDLC, BISYNC, AND BRI

This chapter provides reference information to the following

topics: HDLC, the High-level Data Link Control protocol;
BISYNC, the binary synchronous communications protocol; and
BRI, the basic rate interface.

3008M300-004 34-437
CXTool User Guide

34.1 HDLC
HDLC is a bit-oriented, synchronous, link layer, data-framing,
flow control, and error detection and correction protocol.

A Memotec device can accept HDLC packets, can transport

them transparently over a frame relay network, can receive
them from a frame relay network, and can forward them.

To configure this service, open the Transparent folder. Select

the HDLC Port module. Click on the Add (+) button in the tool
bar or select Add New from the pull-down Edit menu. The
screen shown in Figure 34-1 appears.

Configure the parameters listed below.

1. Sync Port
This parameter allows the user to configure a sync port. For
further details, see 6.4 Configuring a Synchronous Driver
2. Frame Relay DLCI
This parameter allows the user to configure a Frame Relay
DLCI. For further details, see 9.2.2 Configuring Frame Relay
DLCIs.
3. Reference Number
Figure 34-1: Configuring an HDLC Port
This parameter is configured multiple HDLCs carried on the
same Frame Relay DLCI. Each Reference Number must be
unique.
34.2 BISYNC
4. PId
This parameter allows the user to identify the type of traffic to To configure this service, open the Transparent folder. Select
be carried on this circuit. For a list of options, see the BSC module. Click on the Add (+) button in the tool bar or
9.2.3 Configuring Frame Relay Switching. select Add New from the pull-down Edit menu. The following
screen appears:

Configure the parameters listed below.

34-438 3008M300-004
 34 INTRODUCING HDLC, BISYNC, AND BRI

same PVC, the reference number uniquely identifies data from

each source.
4. PId
This parameter allows the user to identify the type of traffic to
be carried on this circuit. To view a list of the options available,
see Chapter 9 CONFIGURING FRAME RELAY, section
9.2.4 Configuring the ATM Interworking Port.

In the event that a BISYNC parameter is empty, click on Add

and follow the configuration steps outlined in 6.2 Configuring
a Bisync Driver.

34.3 BRI
Refer to Chapter 11 CONFIGURING ISDN AND QSIG,
especially:
• “Interfaces” on page 11-202
• “Configuring BRI Services Only” on page 11-201
• “Memotec’s CX Products and the ISDN Environment” on
page 11-198
Figure 34-2: Configuring a BISYNC Port • “BRI/PRI Capabilities” on page 11-203

1. BISYNC port
This parameter allows the user to configure a BISYNC driver.
2. Frame Relay DLCI
This parameter identifies the DLCI on which BISYNC data
will be carried across a Frame Relay network to its destination.
3. Reference Number
This parameter indicates the reference number assigned to the
Frame Relay circuit. When multiple users transmit over the

3008M300-004 34-439
CXTool User Guide

34.4 Global Directory

The Global Directory allows the user to store information
pertinent to voice and data calls.
• For voice calls, see“Configuring the Local Port” on
page 7-85, Voice Channel - Advanced, points 12 and 13
• For data calls, see “Configure the ISDN Data Service Point”
on page 11-213

34-440 3008M300-004
 AAL ATM Adaptation Layer. A collection of standardized protocols access rate The data rate of the user access channel. The speed of the
that adapt user traffic to a cell format. Specifically, the ATM access channel determines how much data (maximum rate) the
adaptation layer (AAL) receives packets from upper-level end user can inject into a Frame Relay network.
protocols and breaks them into the 48-byte segments that form
the payload field of an ATM cell. Memotec currently supports
AAL0 and AAL5. access A Frame Relay access switch is a device that performs the
switch functions of a Frame Relay access device (see FRAD) and
those of a switch in a Frame Relay network.
AAL0 ATM Adaptation Layer type 0. Typically used by Memotec to
transport voice.
ACELP II Algebraic Code-Excited Linear Prediction. A voice
compression algorithm used in Memotec's Frame Relay
AAL5 ATM Adaptation Layer Type 5. Protocol used for the transport equipment that provides 5.8 and 8 kbps compression rates.
of all types of traffic over ATM. Applications over AAL5
include Frame Relay, LAN, ATM-DXI, Voice, as well as
legacy protocols. There are no limitations for new applications ADPCM Adaptive Differential Pulse Code Modulation. A speech coding
to be added over AAL5. method that uses fewer bits than the traditional PCM (Pulse
Code Modulation). ADPCM, which many makers of voice
processing equipment use, allows encoding of voice signals at
ABR Available Bit Rate. One of the two "best effort" service types 16, 24, 32 and 40 kbps.
(or service categories) in ATM (the other one is UBR), where
the network makes no absolute guarantee of cell delivery;
however, it guarantees a minimum bit rate for user
transmission. The objective of ABR service is to provide rapid
access to network bandwidth that is not being used.
alternate routing

access In a public network, the amount of bandwidth on a dedicated A routing algorithm feature that finds an alternate route for a
channel link that is dedicated to Frame Relay or ATM traffic. connection that has

been interrupted due to a fault or other cause.

access line A communications line interconnecting a Frame Relay-
compatible end-device (DTE) to a Frame Relay switch (DCE).

ANI

3008M300-004 -441
CXTool User Guide

Automatic Number Identification. A feature used by ISDN and American Standard Code for Information Interchange. An 8-bit
Signaling System 7 to coding method used by

provide the calling party number. computers for representing letters, numbers, punctuation, and
control codes into

digital form.

ANSI

American National Standards Institute. A non-profit, non-

governmental organization Async

that defines standards, including telecommunications Short form for asynchronous. Also a term used to designate
standards, for use in the United Async protocol. See also

States. ANSI is a member of the International Organization for asynchronous and Async protocol.
Standardization (ISO).

Asynchronous
ARP
A mode of data transmission in which data can be sent at any
Address Resolution Protocol. Internet Protocol utility used to time (no synchronization
dynamically map IP
of data transfer). In asynchronous transmission, the
addresses to Ethernet MAC address on local area networks. information unit does not always

have the same number of bits, which causes variable time delay
between data messages.

ASCII

-442 3008M300-004
 Async protocol ATM Forum

A transmission protocol in which data is transmitted one A consortium of organizations representing vendors,
character at a time, each manufacturers, carriers, service

character being preceded by a start bit and followed by a stop providers, research groups, consultants and users that
bit in order to ensure recommends and defines specifications

correct receipt. for ATM standards and promotes industry cooperation in the
implementation of ATM

technologies.

AT&T

American Telephone and Telegraph Company.

ATM Layer

The second layer of the ATM protocol stack model that

constructs and processes the
ATM ATM cells.
Asynchronous Transfer Mode. Very high-speed transmission
technology that allows multiple

types of traffic (voice, video, data) to be transmitted in fixed-

size cells of 53 B Channel

bytes. It can support transmission speeds up to several gigabits In an Integrated Services Digital Network (ISDN), a full-
per second. Also duplex 64 kbps channel which

known as cell relay. is used to carry end user data or voice information. Synonym:
bearer channel

3008M300-004 -443
CXTool User Guide

and control of a telephone line. Also referred to as 2B+D.

backbone network

The primary network of a hierarchical, distributed system that

links individual network
Bc
segments. Ensures that all systems that have connectivity to an
intermediate system Committed burst size. A Frame Relay term. The maximum
amount of data (in bits) that
on the backbone also have connectivity to one another.
the network agrees to transfer, under normal conditions, during
time interval Tc.

Bandwidth

An analog transmission term for a range of frequencies. For Be

digital transmissions,
Excess burst size. A Frame Relay term. The maximum allowed
bandwidth is expressed in kilobits per second (kbps). The amount of data by which
amount of bandwidth determines
a user can exceed Bc. Unlike Bc, there is no time interval.
the rate at which information can be sent through a channel.

BECN
Basic Rate Interface (BRI)
Backward Explicit Congestion Notification. A congestion
A service in ISDN that provides each user with two 64 kbps notification method used
"B" channels (bearer channels)
by Frame Relay to indicate congestion or approaching
for message information and one 16 kbps "D" channel (data congestion for the traffic in
channel) for signaling
the opposite direction.

-444 3008M300-004
 bisync

Bellcore Binary synchronous communications protocol. A half-duplex,

Bell Communications Research. An organization that performs
research and development
on behalf of the RBOC (Regional Bell Operating Companies).
character-oriented, synchronous
data communications transmission method developed by IBM.
Bisync is considered to
be the first synchronous protocol developed.

Best effort
bit-oriented protocol
An ATM term. A Quality of Service class in which no specific
traffic parameters and Communications protocol that assigns meaning at the bit level,
for example, the High-Level
no absolute guarantees are provided. Best effort includes UBR
and ABR (See also Service Data Link Control (HDLC) protocol, as opposed to character-
oriented protocol.
Categories).

BOC
BISDN
Bell Operating Company. In the United States, one of 22 local
Broadband Integrated Services Digital Network. Basically telephone companies
refers to any circuit capable
spun off from AT&T and reorganized into seven regional Bell
of transmitting more than one basic rate ISDN, i.e. 144 kbps Operating Companies (RBOCs).
(2B+D).
See also RBOC

3008M300-004 -445
CXTool User Guide

interconnected LANs look like a single LAN, passing data

between the networks and

filtering local traffic. A bridge connects networks that use

BRA dissimilar protocols

Basic Rate Access. Two 64 kbps "B" channels + one 16 kbps and it does not interpret the data it carries. It controls network
"D" channel (2B+D), carrying traffic and security,

user traffic and signaling information respectively to the user filters where necessary to boost network performance, and
via twisted pair constrains data to within
local loop. BRA thus provides ISDN users with access to two those LANs required for its delivery.
64 kbps data channels,

the 16 kbps channel being used only for signaling.

bridge/router

A term used to describe a network device that can perform the

BRI functions of both a
Basic Rate Interface. The ISDN interface composed of two 64 bridge and a router. A bridge/router routes some protocols and
kbps "B" channels and bridges others. Also

one 16 kbps "D" channel for circuit-switched communication known as brouter.

of voice, data and video.

broadband
Bridge
A system or service operating at high information transfer rates
An interconnection device used to link two or more physical usually at or above
networks. A bridge makes
10 Mbps.

-446 3008M300-004
 Broadcast bus

The simultaneous transmission of the same data to all A LAN topology in which all nodes share a single length of
destinations on a network. cable (backbone) running

between two points.

Brouter

A term used to describe a network device that can perform the bursty traffic
functions of both a
In a Frame Relay network, data that uses bandwidth only
bridge and a router. A brouter routes some protocols and sporadically; that is, information
bridges others. Also known
that does not use the total bandwidth of a circuit 100 percent of
as bridge/router. the time.

BSC Bursting

Binary synchronous communications protocol. A half-duplex, In a Frame Relay network, the ability to transmit above the
character-oriented, synchronous subscribed CIR (committed

data communications transmission method developed by IBM. information rate).

BSC is considered to be

the first synchronous protocol developed. Also known as

Bisync.

3008M300-004 -447
CXTool User Guide

byte CAS

A coding method in which a group of digital bits, called a byte, Channel Associated Signaling. A form of digital voice
is used to represent signaling in which the hook

a value. In the ASCII code a byte is eight bits (seven state is indicated by one or more signaling bits associated with
information bits and one parity a specific voice

bit), also known as an octet. EBCDIC uses eight information channel.

bits per byte. There

are 16 bits in a Unicode byte.

CBR

Constant Bit Rate. An ATM service category that supports a

byte-oriented protocol constant or guaranteed

Protocol that uses a full byte to communicate control rate for services such as video or voice as well as circuit
information. Also referred emulation, which requires

to as character-oriented protocol. rigorous timing control and performance parameters.

Carrier CCITT

Licensed, private utility company that supplies communication Comité Consultatif International Téléphonique et
services to the public Télégraphique (International Telegraph

at regulated prices. and Telephone Consultative Committee). A group within the

International Telecommunications

Union (ITU) that defines data communications standards.

-448 3008M300-004
 Cell Delay Variation Tolerance. One of the key traffic
parameters required to be

provided by the user to the ATM network service provider. It

CCS allows the user to specify
Common Channel Signaling, a method in which the signaling the acceptable amount of CDV (Cell Delay Variation) a
functions, associated with connection can handle.
establishing and terminating a telephone call, are located on
separate facilities

from those that carry the call. The separate signaling facilities
are the common Cell

signaling channel. Unit in ATM networking technology that has a length of 53

bytes (424 bits) and contains

user data and routing information.

CDV

Cell Delay Variation. A negotiated QoS parameter for ATM

that measures the difference CER

between a single cell's transfer delay (CTD) and the expected Cell Error Ratio. A QoS parameter for ATM. CER is the ratio
transfer delay. Peak-to-peak of errored cells in a

CDV is a QoS parameter associated with CBR and VBR transmission in compared to the total cells sent in the
services. transmission. CER is not

negotiated between the end-system and the network.

CDVT

3008M300-004 -449
CXTool User Guide

Channel

In a public network, the amount of bandwidth on a dedicated Committed Information Rate. The minimum guaranteed
link that is allocated throughput on the circuit set

to Frame Relay or ATM traffic. Generically refers to the user for each PVC and SVC. The CIR is subscribed to in 4 kbps
access channel across increments.

which Frame Relay data travels. Within a given T1 physical

line, a channel can be

one of the following, depending on how the line is configured:

clear channel
Unchannelized: the entire T1 line is considered a channel. The
T1 line operates at speeds of 1.536 Mbps and is a single 64 kbps service.
channel consisting of 24 T1 time slots.

Channelized: the channel is any one of N time slots within a

given line where the T1 line consists of one or more channels.
Each channel is any one of 24 time slots. The T1 line operates
CLID
at speeds in multiples of 56/64 kbps to 1.536 Mbps, with
aggregate speed not exceeding 1.536 Mbps. Calling Line Identification. Same as ANI (Automatic Number
Identification), except

it tends to refer to identification of local calling numbers. CLID

tends to be referred
fractional T1: the T1 channel is one of the following groupings
to as a service of CLASS (Custom Local Area Signaling
of consecutively
Services).
or non-consecutively assigned time slots: N T1 time slots (N x
56/64 kbps, where

N = 1 to 23 T1 time slots per FT1 channel)

CLP
CIR

-450 3008M300-004
 Cell Loss Priority. A bit in the ATM cell header that indicates See Bc
two levels of priority

for ATM cells. CLP=0 cells are higher priority than CLP=1
cells. CLP=1 cells may

be discarded during periods of congestion to preserve the CLR Common Channel Signaling
of CLP=0 cells.
A method in which the signaling functions, associated with
establishing and terminating

a telephone call, are located on separate facilities from those

that carry the call.
CLR
The separate signaling facilities are the common signaling
Cell Loss Ratio. A negotiated QoS parameter for ATM. The channel.
CLR is the ratio of lost

cells to total transmitted cells.

Concentrator

A device that connects to a group of nodes, thus providing a

CMR single shared connection

Cell Misinsertion Rate. A QoS parameter for ATM. The CMR to the network through a repeater.
is defined as the number

of misinserted cells (those that arrive from the wrong source)

per time interval.

Contention

Access method in which two or more devices compete for use

of the network bandwidth.
Committed burst size

3008M300-004 -451
CXTool User Guide

the connection, and the CSU portion connects to the line. A

CSU/DSU is the digital
CPE
equivalent of a modem. See also DCE
Customer Premises Equipment. Devices used at a customer
site, either leased or owned,

including telecommunications equipment.

D channel

In ISDN, a channel that is used to carry signaling information.

Full duplex 16 kbps
CSA
(basic rate) or 64 kbps (primary rate) ISDN channel.
Canadian Standards Association. A Canadian agency that
certifies products to Canadian

national safety standards.

Data Communications Equipment

See DCE

CSU/DSU Channel

Channel Service Unit/Data Service Unit. Devices used to

access digital data channels.
data compression
These devices perform much of the same function for digital
circuits that modems A way of reducing the amount of data to be transmitted by
applying one of several
provide for analog connections. They transform electrical
signals into a form that techniques that reduce the number of bits needed to represent
the information. When
can be transmitted on a digital circuit. The DSU part connects
to the DTE side of the data is received, it is decompressed into its original form.

-452 3008M300-004
 A direct connection between a terminal and a service, network,
or computer for the

use of a particular customer only.

Data Service Unit

See CSU/DSU

dedicated line

A line that is reserved for the exclusive use of a particular

Data Terminal Equipment customer. When the
See DTE line is not owned by the user, the term leased line is more
common.

DCE
dedicated T1
Data Communications Equipment. Equipment that can
establish, maintain, and terminate A T1 line that is permanently allocated to a particular user.
a connection between the Data Terminal Equipment (DTE) and
the telephone line or

data circuit. In a Frame Relay network this term applies to

switching equipment. De Facto standard

See also CSU/DSU An unofficial, but widely used, standard.

dedicated access De Jure standard

3008M300-004 -453
CXTool User Guide

A standard that has been officially approved by an organization

established to define
DSP
and develop standards.
Digital signal processor. Specialized computer chip that
performs high-speed calculations

on data that was originally analog voice or video. Used to

process sound and video.
dial access
Normally has a built-in analog to digital converter.
A connection through the public switched telephone network to
a service, network

or computer.

DSU

See CSU.

dial-up line

A standard telephone line in which the connection is

established by dialing.
DTE

Data Terminal Equipment. The device that is the origin or the

destination of data

DLCI within a communications system, e.g., a PC, a fax machine,

etc.).
Data Link Connection Identifier. A Frame Relay value
assigned by the service provider

that identifies a logical connection from the user to the Frame

Relay network.
duplex

-454 3008M300-004
 See full duplex rate of 2.048 Mbps.

dynamic routing EIA

Routing that adjusts automatically in response to changes in Electronics Industries Association. A trade association of
network topology or electronics equipment

traffic. manufacturers in the USA that develops various standards for

the industry.

edge switch
EMS
A switch that is located between the user premises and the
carrier switch in a Frame Element Management Software. The level of a network
management system concerned with
Relay network. An edge switch is the first point of user access
to, and the final collecting network management information from, and setting
parameters on, the network
point of exit from, a broadband network (e.g. Frame Relay and
ATM). Also used to elements. ThunderView™ EMS is proprietary Memotec
software.
access a backbone network.

Encapsulation
E1
A technique used by network-layer protocols in which a layer
The European equivalent to the North American T1 carrier adds header information
trunk. It offers a transmission

3008M300-004 -455
CXTool User Guide

to the protocol data unit from the preceding layer. The process EPROM
of "enveloping" one
Erasable Programmable Read Only Memory. An integrated
protocol inside another for transmission (for example, IP inside circuit read only memory device
IPX).
that can be electrically programmed and with ultraviolet light
be erased.

end device

The source-point or ultimate destination-point of data flowing Ethernet

through a Frame Relay
The most widely used LAN transmission protocol. It operates
network, sometimes referred to as a Data Terminal Equipment at 10 Mbps or 100 Mbps
(DTE). As a source device,
in a bus topology and is documented as an IEEE 802.3
it sends data to an interface device for encapsulation into a standard.
Frame Relay frame.

As a destination device, it receives de-encapsulated data from

the interface device.

excess burst size

See Be

end-to-end

An expression used in the networking environment to indicate

communication between
extranet
source and destination nodes in a network system.
A term applied to networks of information service providers
(ISPs) such as America

-456 3008M300-004
 Online and Prodigy. Such providers have deployed private the user that congestion-avoidance procedures should be
networks which operate on initiated, where applicable,

the same principles and make use of the same network for traffic in the same direction as the received frame. It
technologies as the Internet, indicates that this frame,

but are external to it. Access to the Internet can be gained on this logical connection, has encountered congested
through an extranet. resources.

fast packet switching Firewall

A technique in which both voice and high speed data can be A term used in reference to a router's ability to contain a fault
transmitted as packets. to the area of

Frame Relay and ATM are fast packet switching technologies. the network where it occurs. In other words, a firewall is a
system that enforces

a boundary between two or more networks. Commonly used to

provide secure access to
FDDI the Internet.
Fiber Distributed Data Interface. FDDI is a 100 megabits per
second fiber optic LAN.

FLASH memory

Readable and writeable memory implemented in silicon chips

FECN that are less prone to
Forward Explicit Congestion Notification. A Frame Relay mechanical failure because they have no moving parts. Often
term. A bit that notifies implemented in routers.

3008M300-004 -457
CXTool User Guide

The process by which large frames are split into smaller frames
before transmission;

splitting these frames ensures that sensitive material such as

fractional voice traffic will

T1A service in which a customer can use fewer than 24 not suffer lengthy delays waiting for a large frame to finish
channels on a T1 line without transmitting.

paying the cost of the entire line.

frameIn

FRAD Frame Relay, a variable-length unit of data having a header and

flags to mark the
Frame Relay access device. A device required for connection
into a Frame Relay network; beginning and end of the frame. A frame may contain control
and addressing information,
it receives information from various DTEs, performs the
encapsulation of that information as well as error detection and forward error correction
information.
into frames and sends it to the Frame Relay switch. The FRAD
is thus responsible

for framing data with header information prior to presentation

of the frame to the
Frame Relay
Frame Relay switch.
A fast packet-switching technology that transmits data between
end-point devices

like routers or FRADs at speeds between 56 kbps and 2.048

Mbps. Frame Relay also
Fragmentation
refers to the network access protocol used in a Frame Relay
network.

-458 3008M300-004
 A telecommunications network based on Frame Relay
technology. In a Frame Relay network,

data is divided into variable-length frames by the sending

Frame Relay access device device, with each frame
See FRAD containing a header with address information. Frames are
transmitted intermittently

over digital circuits and reassembled at the receiving end.

Frame Relay access switch

A device that performs the functions of a Frame Relay access

device (see FRAD) and Frame Relay switch
those of a switch in a Frame Relay network. A device within a network which receives, transmits and
switches frames in their

native form without encapsulation. The Frame Relay switch

receives data that is already
Frame Relay Forum in the frame format whereas the Frame Relay access device has
to encapsulate the
Organization of Frame Relay equipment vendors, carriers, end-
users and consultants information in frames before sending it.
working to promote the development and deployment of Frame
Relay products, as well

as interfaces with other broadband technologies, such as ATM.

FT1

Fractional T1See channel

Frame Relay network

3008M300-004 -459
CXTool User Guide

half duplex

full duplex A two-way means of transmission where data travels in one

direction at a time, and
A two-way means of transmission where information travels in
both directions simultaneously in the opposite direction when first transmission in complete.

over the same transmission medium. Synonym: duplex

HDLC

gateway High-Level Data Link Control. A generic link-level

A protocol conversion device used to interconnect LANs which
use different communications
protocols to communicate with each other.
communications protocol developed
by ISO. HDLC manages synchronous, code-transparent, serial
information transfer over
a link connection. See also SDLC

GUI
high-speed
Graphical User Interface. Often pronounced "goo-ee",
describes the interactive screen Refers to data communication systems operating at highest
speed for a service. This
display with which the user interfaces during the computer
session. A GUI makes use is a relative term since data rates are always increasing.

of windows, icons, menus and pointers.

Hub

-460 3008M300-004
 Specifically, the central device in a star topology to which all access method on a ring topology LAN.
nodes attach. Generically

used for any centralized device with multiple node

connections.

IEEE 802.3

The IEEE standard for Ethernet LAN.

hybrid network

A networking model using both leased lines and shared

network technologies. An amalgamation
Internetworking
of public and private network transmission facilities.
The use of linking devices such as gateways, bridges and
routers to connect network

systems of same or varied configurations.

IEEE

Institute of Electrical and Electronics Engineers. A

professional organization that
Interoperability
defines a variety of standards including data communications
technologies. Different types of systems or products are said to be
interoperable if they can communicate

and exchange information with each other.

IEEE 802.5

The IEEE standard for IBM Token Ring network. This

standard uses the Token Ring passing Intranet

3008M300-004 -461
CXTool User Guide

A private network that uses Internet software and Internet

standards. In essence,

an intranet is a private Internet reserved for use by people who

have been given ISDN

the authority and passwords necessary to use that network. Integrated Services Digital Network. A network that offers
integrated voice, data,

image and video services over the digital telephone network at

high speeds, thus

I/O card (module) allowing users to process a wide range of applications using a
single telephone line.
An input/output card capable of sending and receiving signals.

ISDN BRI
IP
The Basic Rate Interface of ISDN is composed of two 64 kbps
Internet Protocol. A layer 3 (network layer) protocol that "B" channels and one
contains addressing information
16 kbps "D" channel for circuit-switched communication of
and some control information allowing packets to be routed. voice, data, and video.
See also TCP/IP

ISO
IPX
International Organization for Standardization. Organization
Internet Packet Exchange. Novell Layer 3 protocol is similar to responsible for a wide
IP that is used in
range of standards, including those relevant to networking.
NetWare networks. Often incorrectly referred

-462 3008M300-004
 to as the International Standards Organization.

LAN

ISP Local area network. A local network connecting a defined set

of terminals. Could
Internet Service Provider. A vendor who provides direct access
to the Internet. The connect workstations in an office, offices in a building,
buildings on a campus,
ISP also usually provides a core group of internet utilities and
services like e-mail, etc. Ethernet and Token Ring are two widely used local area
networks.
news groups readers, weather reports, etc.

LAPB
ITU-T
Link Access Procedure-Balanced. CCITT bit-oriented protocol
International Telecommunication Union-Telecommunications. similar to the Synchronous
An organization established
Data-Link Control (SDLC) protocol.
by the United Nations that specializes in defining and adopting
telecommunications

standards and furthering telecommunications development

around the world.
LAPD

Link Access Procedure-D. The link-layer protocol for the D

channel in Integrated

kbps Services Digital Networks (ISDN).

kilobits per second. Data rate equal to 1,000 bps.

3008M300-004 -463
CXTool User Guide

leased line

A leased phone line rented from a common carrier that LLC2

provides a full-time, point-to-point
Logical Link Control 2. The frame format used to carry SNA
connection. traffic on Token Ring

or Ethernet LANs or Frame Relay.

legacy

A term used to refer to older synchronous or asynchronous LMI

protocols e.g. SNA, HDLC,
Local Management Interface for Frame Relay. It is used by the
X.25, Async, etc. switch to learn which

DLCIs are defined and the current status of the DLCIs.

LID

Line Interface Driver local access

The connection to the service provider's nearest point of

service. This connection

is also called the local loop.

link

A term used to refer to any node to node connection within a

data communications

network. local spoofing

-464 3008M300-004
 Networking term. A method by which the client and/or router
filters network traffic
meshed network
to keep unnecessary traffic from going over a WAN link.
Rather than forwarding the Network topology in which each node is connected either
logically or physically to
traffic over the connection, the device responds to the source of
the traffic with every other node in the network.

the response that would have been generated by the intended

destination device.

Mbps

Megabits per second. One megabit equals one million bits.

mainframe

A large, high-performance multi-user computer, capable of

performing large computing

tasks and information storage. MBS

Maximum Burst Size. An ATM term. A source traffic

parameter that specifies the maximum

number of cells that can be transmitted at the peak rate (PCR).

MaxCTD It serves to specify

Maximum Cell Transfer Delay. A negotiated QoS parameter the bandwidth requirement in various service categories such
for ATM. The elapsed time as real-time and non-real-time

between a cell exit event at the source and the corresponding Variable Bit Rate (VBR).
cell entry level at

the destination for a particular connection.

3008M300-004 -465
CXTool User Guide

MCR The transmission of the same data to a selected group of

workstations on a LAN, WAN
An ATM term. A parameter that gives the minimum rate that
cells can be transmitted or Internet. In contrast, in a broadcast, packets are sent to all
network addresses.
by a source over a virtual connection.
See also broadcast

MIB
multidrop
Management Information Base. Document defining the
variables needed for monitoring More commonly called multipoint, is a line or circuit
connecting several points along
and control of various components of a network. A database of
network management a single logical link, typically used in IBM SNA architecture.
In a multipoint configuration,
information that can be accessed via network management
protocols such as SNMP. the data is transmitted between a central site and a number of
remote terminals on

the same circuit.

MTBF

Mean time between failure. Average period of time a piece of

equipment or component multiplexer

remains working before failure. A device that combines individual signals into a composite
signal. A multiplexer

allows a single communications circuit to take the place of

several parallel ones,

multicast

-466 3008M300-004
 e.g. a T1 multiplexer combines 24 channels of 64 kbps each A device that can route different high level protocols across the
into a single bit stream same network, like

of 1.544 Mbps. IP to IP or DEC to DEC. Cannot route IP to DEC in same

network without a gateway.

multiplexing
multivendor network
The process of combining multiple channels over one
composite circuit. Network comprised of components and equipment from
different vendors.

multipoint
MUX
Multipoint is a line or circuit connecting several points along a
single logical A multiplexer, a device that combines individual signals into a
composite signal.
link, typically used in IBM SNA architecture. In a multipoint
configuration, the A multiplexer allows a single communications circuit to take
the place of several
data is transmitted between a central site and a number of
remote terminals on the parallel ones, e.g. a T1 multiplexer combines 24 channels of 64
kbps each into a
same circuit.
single bit stream of 1.544 Mbps.

multiprotocol router
NIU

3008M300-004 -467
CXTool User Guide

Network Interface Unit. The demarcation point between the The point in a transmission network where lines or trunks from
service provider's wiring many sources meet

and equipment and the customer's wiring and equipment. Also (i.e. a point of concentration or switching).
called network interface

device.

OEM

Original Equipment Manufacturer. The maker of equipment

NMS marketed by another vendor,

Network Management System. A comprehensive system of usually under the name of the second vendor.
equipment used in monitoring,

controlling and managing a data communications network.

Usually consists of testing

devices. OSI Model

Open Systems Interconnection Model. a seven-layer model for

data communications developed

by the ISO:
NNI
Layer 7 application, Layer 6 presentation , Layer 5 session,
Network-to-Network Interface in Frame Relay and ATM. The Layer 4 transport,
interface between two Frame
Layer 3 network, Layer 2 data-link, Layer 1 physical layer
Relay or ATM networks.

PAD
node

-468 3008M300-004
 A Packet Assembler/Disassembler, which collects async data Peak Cell Rate. A traffic parameter that characterizes the
and assembles it into source traffic. It gives

packets for transmission on a packet-switching system. At the the maximum rate (in cells/sec.) at which cells can be
receive end, another transmitted by an ATM source

PAD disassembles the packets, recovering the original data. end system. It serves to specify the bandwidth requirement in
various service categories

such as constant bit rate service (CBR), real-time and non-real-

time variable bit
payload rate (VBR).
Part of the protocol data unit that contains the user information
from higher layer

protocols that is to be carried. In ATM it occupies 48 bytes.

permanent virtual circuit

Permanent Virtual Circuit. A logical link offering a continually

available communications
PBX path between two fixed end points. Data terminating equipment
with a need for continuous
Private Branch Exchange. A privately owned telephone switch
that provides local communication communication use PVCs.
and access to trunk lines. Customer premises version of a
central office switch (CO).

piggybacking

Ability to carry acknowledgments within a data packet, thus

PCR saving bandwidth and

increasing performance.

3008M300-004 -469
CXTool User Guide

PPP

polling Point-to-Point Protocol. A standard protocol used to

communicate over a serial point-to-point
Any procedure that sequentially and periodically contacts
terminals in a network. link such as a T1 trunk between routers or a PC dial-up line.

In this procedure, a primary device inquires, in an orderly

fashion, whether secondary

devices have data to transmit.

PRI

Primary Rate Interface. An ISDN service that provides twenty-

three B channels (30

port
An access point for data entry or exit. Can also refer to the
physical or electrical
interface through which one gains access to a device.
in Europe) at 64 kbps for voice and data transmission, and one
D channel for signaling
between the user and the exchange, also at 64 kbps. Also called
23B+D (30B+D in Europe).

proprietary
POTS
A proprietary protocol is a protocol that is owned, often by the
Plain Old Telephone Service. Basic telephone service - dial company that developed
tone without any special
it, as opposed to a protocol developed by a standards
features. organization that is intended

to be used in common.

-470 3008M300-004
 QoS

PSTN Quality of Service. In ATM, QoS refers to the set of

performance parameters that
Public Switched Telephone Network. Refers to a shared,
switched voice network or characterize the traffic over a given virtual connection. The
ATM QoS is divided
a portion of that network.
into QoS classes, each class relating to a subset of QoS
parameters that provide

a particular level of service for ATM traffic.

PVC

Permanent Virtual Circuit. A logical link offering a continually

available communications
QoS - Frame Relay
path between two fixed end points. Data terminating equipment
with a need for continuous While standard QoS parameters and standard service classes
have been defined for
communication use PVCs.
ATM, such is not the case for frame relay. Each vendor uses its
own QoS parameters

for frame relay technology. Memotec's proprietary QoS

parameters for frame relay
Q.922A
are bandwidth optimization, congestion control, bandwidth on
Q.922 Annex A The international standard that defines the demand, traffic prioritization,
structure of Frame Relay
and packet fragmentation.
frames. Based on the Q.922A frame format developed by the
CCITT.

3008M300-004 -471
CXTool User Guide

QoS parameters A standard CAS (channel associated signalling) method

defined by the ITU.
QoS parameters represent performance objectives expected
from the network for the

duration of the connection. These parameters include the CDV,

CER, CLR, CMR, maxCTD
RARP
and SECBR. The CDV, maxCTD and CLR are negotiated
between the end-system and the Reverse Address Resolution Protocol is an Internet protocol
utility used by some
network, while the CER, SECBR and CMR are not.
hosts to find an IP address at startup. It maps a physical address
to an IP address.

QSIG

Unified international corporate network signaling standard. RBOC

Using proven ISDN technology
Regional Bell Operating Company. A term for the seven
and supported by the world's leading PBX vendors, QSIG is regional holding companies
the only corporate network
created when AT&T divested the Bell operating companies.
signaling system that provides both vendor independence and
guaranteed inter-operability

at a global level. QSIG ensures service compatibility between a

public ISDN and the
redundancy
private ISDN network.
Spare capacity that can be called upon in the event of trouble.
When there is more

than one path to a node, the secondary paths are said to provide
redundancy.
R2 Signaling

-472 3008M300-004
 A device that switches packets at the OSI Network layer.RS-
232A type of DTE-DCE interface

standard developed by the Electronics Industries Association.

remote

A term used to describe network devices that are controlled

from a network system

other than the central system to which they are directly S interface
connected.
The subscriber interface defined by the CCITT between the
ISDN service supplier and

the subscriber's equipment. See also T interface, U interface

RFC 1490

Refers to the standardization for encapsulation and

fragmentation of traffic into
SAP
Frame Relay frames for transmission over Frame Relay
networks. Service Access Point. An interface between adjacent OSI
layers.

RIP
SAR
Routing Information Protocol. A protocol used by IP routers to
exchange routing information. Segmentation And Reassembly.

router SCR

3008M300-004 -473
CXTool User Guide

Sustainable Cell Rate. An ATM term. A traffic parameter that cell blocks divided by the total number of cell blocks
characterizes a bursty transmitted.

source and specifies the maximum average rate at which cells

can be sent over a given

connection. It serves to specify the bandwidth requirement in

various service categories service categories

such as real-time and non-real-time variable bit rate (VBR). Service categories are specified by the ATM Forum to support
the various types of

traffic. They give end users a simpler approach to setting up

traffic descriptors,

SDLC priorities, and cell delay variation tolerance. There are four
service categories:
Synchronous Data-Link Control Protocol. A link-level
communications protocol used CBR, VBR, UBR and ABR. CBR and VBR are guaranteed
services while UBR and ABR are
in an IBM systems network architecture (SNA) that manages
synchronous, code-transparent, described as "best effort" services. See CBR, VBR, UBR and
ABR
serial information transfer over a link connection. SDLC is a
subset of the more

generic High-Level Data Link Control (HDLC) Protocol

developed by the ISO.
SLIM

Serial Line Interface Module

SECBR

Severely Errored Cell Block Ratio. A QoS parameter for ATM.

The result of errored Simple Network Management Protocol

-474 3008M300-004
 Also known as SNMP, it is a standard IP application protocol
that allows network
SNMP
management systems to retrieve management information from
the devices on the network. Simple Network Management Protocol. A standard IP
application protocol which allows

network management systems to retrieve management

information from the devices on

SNA the network.

Systems Network Architecture. The set of protocols,

procedures, etc. that defines

communication between IBM minicomputers and mainframe

computers. SOHO

Small Office, Home Office. An acronym for a telecom market

consisting of workers

in small or home offices.

SNA/SDLC

Synchronous Data-Link Control Protocol is a link-level

communications protocol used

in IBM systems network architecture (SNA) that manages source-route bridging

synchronous, code-transparent,
The process in which the source node in a Token Ring network
serial information transfer over a link connection. SDLC is a determines the best
subset of the more
path for a particular packet by transmitting an explorer packet.
generic High-Level Data Link Control (HDLC) protocol The route is actually
developed by the ISO.
determined by the end stations through a discovery process
supported by source route

3008M300-004 -475
CXTool User Guide

bridges. Spanning Tree Algorithm

An IEEE 802.1 standard algorithm used by bridges to

automatically compute a set of

routes between all bridges in the network to avoid loops.

source-route-to-transparent bridging

See SR/TB bridging

SPID

Service Profile Identifier. A SPID is an 8 to 12 digit number

source-route transparent bridging that uniquely identifies
See SRT bridging the services provided by the carrier. Only used in North
America.

source routing
spoofing
The process in which the source node in a Token Ring network
determines the best A networking term describing a method by which the client
and/or router filters network
path for a particular packet by transmitting an explorer packet.
The route is actually traffic to keep unnecessary traffic from going over a WAN link.
Rather than forwarding
determined by the end stations through a discovery process
supported by source route the traffic over the connection, the device responds to the
source of the traffic
bridges.
with the response that would have been generated by the
intended destination device.

Also called local spoofing.

-476 3008M300-004
 Source-route-to-transparent bridging. Method of bridging in
which source-route stations

can communicate with transparent bridge stations with the help

SR of an intermediate
Source routing is the process by which the source node in a bridge that translates between the two bridge protocols.
Token Ring network determines

the best path for a particular packet by transmitting an explorer

packet. The route

is actually determined by the end stations through a discovery STA

process supported
Spanning Tree Algorithm is an IEEE 802.1 standard algorithm
by source route bridges. used by bridges to automatically

compute a set of routes between all bridges in the network to

avoid loops within

the routes.
SRT bridging

Source-route transparent bridging. Bridging scheme proposed

by IBM that attempts

to merge the two most prevalent bridging strategies (source- static route
route bridging and transparent
A route that is manually entered into the routing table.
bridging); employs both technologies in one device.

statistical multiplexing
SR/TB bridging
A multiplexing technique in which data samples are
transmitted based on priority

3008M300-004 -477
CXTool User Guide

instead of assigned time slots. Transparent bridging is a scheme used in Ethernet and IEEE
802.3 LANs that makes

two LAN segments behave as one without modification at the

protocol level.

synchronous transmission

A mode of data transfer that requires synchronization of both

the sending and receiving
TCP/IP
device before transmission can occur.
Transmission Control Protocol/Internet Protocol. The two best
known Internet protocols,

often erroneously thought of as one protocol. TCP corresponds

to layer 4 (the transport
T interface
layer) of the OSI model while IP corresponds to layer 3 (the
A 4-wire ISDN BRI circuit. The same as the S interface, but network layer) of that
does not provide higher-layer
same model. TCP provides reliable transmission of data while
protocol services to ISDN terminals. IP provides connectionless

datagram service.

T1

A digital transmission service that carries up to 1.536 Mbps of TDM

data and/or voice.
Time division multiplexing. A technique by which signals from
many sources are combined

onto one transmission line. Signals are separated by time slots.

See also Multiplexer
TB

-478 3008M300-004
 A ring topology local area network that uses a token passing
access method. In a

Token Ring LAN, a supervisory frame, or token, must be

telco received by an attached terminal
Abbreviation for the local telephone company. or workstation before that terminal or workstation can start
transmitting.

throughput
toll quality
Rate of information arriving at, and passing through, a
particular point in the network. The minimum level of acceptable voice quality in long distance
transmission.
This term is commonly used to describe the maximum data
transfer rate.

TR
time division multiplexing Token Ring, is a local area network in a ring topology that
passes a token to determine
Time division multiplexing (TDM) is a technique for
combining signals from many sources which node will have access next. In a Token Ring LAN, a
supervisory frame, or token,
into one signal by allotting an interval of time for each.
must be received by an attached terminal or workstation before
that terminal or workstation

can start transmitting.

Token Ring

3008M300-004 -479
CXTool User Guide

traffic descriptors trunk line

Traffic descriptors are parameters which describe the A communications line connecting two switches to each other.
connection's expected bandwidth

use. They are: Peak Cell Rate (PCR), Sustainable Cell Rate
(SCR), Minimum Cell Rate

(MCR) and Maximum Burst Size (MBS). All are expressed in tunneling
cells per second. Syn.:
A LAN (local area network) term. Tunneling means to
traffic parameters. temporarily change the destination

of a packet in order to traverse one or more routers that are

incapable of routing

to the originally intended destination.

transparent

In reference to network functions, actions that are not seen by

other protocol layers.

U interface

Two-wire ISDN circuit - North American standard. Interface

between network termination
transparent bridging
equipment and the local loop for basic rate access.
Bridging scheme used for Ethernet and IEEE 802.3 LANs in
which bridges make two LAN

segments behave as one without modification at the protocol

level.
UBR

Unspecified Bit Rate. An ATM service category that does not

specify traffic related

-480 3008M300-004
 service guarantees. No numerical commitments are made with UNI specification that refers to signaling issues in ABR, VP
respect to the cell loss and QoS negotiation.

ratio expected by a UBR connection, nor as to the cell transfer

delay experienced

by cells on the connection.

VBR

Variable Bit Rate. An ATM service category which supports

variable bit rate data

UNI traffic with average and peak traffic parameters. Contrary to

User-to-Network Interface. The physical interface between the
user device and a network
switch. In Frame Relay & ATM, User-Network interface
between end users and the public
CBR, VBR traffic can
be bursty at times, it should be able to support the delay
variation as well as provide
a buffering capacity to support the bursty nature of traffic

carrier network.

V.34 modem

UNI 3.0/3.1 An optional module that gives Memotec products a dial back-
up capability, thus providing
The standard adopted by the ATM Forum to define connections
between users or end an alternate connection to the network in the event of a failure
of the main link
stations and a local switch.
(Frame Relay, ISDN).

UNI 4.0

3008M300-004 -481
CXTool User Guide

V.35 are assembled into packets and routed across the X.25 packet
network.
A CCITT standard for the interface between the user device
and the network.

10BaseT

WAN IEEE's specifications for running Ethernet over unshielded

twisted-pair wiring. 10BaseT
Wide Area Network. Generally used to refer to networks that
include telecommunications is referred to as a physical interface for Ethernet.

trunks from common carriers, satellite links, or other long

distance communications

links.
10Base5

IEEE's specifications for running Ethernet over thick coaxial

cable. 10Base5 is referred

X.21 to as a physical interface for Ethernet.

A CCITT standard that defines the interface between data

terminal equipment and data

circuit terminating equipment for circuit-switched networks.

X.25

Packet-switching technology. Also refers to the protocol

specifying how data streams

-482 3008M300-004

CXTool
User Guide
INDEX
A Filtering and Forwarding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . pri 33-433
AddressClasses, IP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . pri 25-382
Async Driver, Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 6-56
Async PAD
configuring services, case. . . . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 14-256
port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 14-261
SVC WAN DTE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 14-268
X.28 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . pri 29-412
X.29 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . pri 29-413
X.3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . pri 29-412
X.3 profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 14-263
ATM
Configuring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 8-115
CX device services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 8-116
DXI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 8-118
Encapsulation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 8-118
FRF.5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 8-117
FRF.8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 8-117
FRF.8 Plus. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 8-118
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . pri 23-365
LAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 8-118
Legacy protocols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 8-118
OAM Flows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 8-120
port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 8-127
protocols supported . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 8-117
traffic descriptors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 8-134
transporting LAN traffic, case . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 8-125
transporting voice traffic - an illustration . . . . . . . . . . . . . . . . cfg 8-124
tunnel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 8-135
Tunneling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 8-119
Tunnels and Priorities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 8-119
virtual channel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 8-131
Voice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 8-118
3008M300-003
CXTool User Guide
B
Bandwidth Group. See Voice
B-channel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . pri 26-392
Bisync Driver, Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 6-58
BRI Services Only - an illustration . . . . . . . . . . . . . . . . . . . . . . cfg 11-201
BRIDGES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . pri 33-431
Bridges
forwarding database (FDB) (FDB). . . . . . . . . . . . . . . . . . . . . pri 33-433
Learning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . pri 33-434
Source Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 18-322
Source Routing Algorithm . . . . . . . . . . . . . . . . . . . . . . . . . . . . pri 33-435
Source Routing Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 18-325
Spanning Tree Algorithm . . . . . . . . . . . . . . . . . . . . . . . . . . . . pri 33-433
Spanning Tree Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 18-329
Token Ring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . pri 33-435
bundle, bundled links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . pri 32-428
C
Call Progress Tones. SeeVoice
CAS. See Voice
CCS. See Voice
Channelized and Unchannelized Ports. See T1/E1 and DIM
Channels. See Voice
CIR. See Frame Relay
CXBrowser . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 3-31
CXTool User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 3-25
CXView . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 3-34
D
Data Link Layer 2 (X.25) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . pri 30-416
D-channel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . pri 26-392
Default Password - changing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 5-52
Dialing Plan. See Voice
Digit Regeneration. See Voice
Digit, Voice Digit. See Voice
Digital Voice Encoding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . pri 27-402
DIM
slot restrictions on CX950 . . . . . . . . . . . . . . . . . cfg 12-220, cfg 12-221
Index-483
CXTool User Guide

Drivers Frame Relay/ATM Service Interworking (FRF.8) - an illustration . . . . . .

async . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 6-56 cfg 8-121
bisync . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 6-58 FRF.12, frame relay, fragmentation . . . . . . . . . . . . . . . . . . . . . . . cfg 9-151
ethernet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 6-63 FRF.5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 8-117
synchronous . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 6-64 FRF.8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 8-117
token ring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 6-69 FRF.8Plus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 8-118
DXI Circuit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 8-137
Dynamic Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 4-40 G
General Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 4-37
E Getting Started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 2-21
Encapsulation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 8-118 Global Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 19-336, pri 34-440
Ethernet (STP) - an illustration. . . . . . . . . . . . . . . . . . . . . . . . . . cfg 18-322 ISDN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 11-215
Ethernet Driver, Configuring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 6-63 Global Directory (ISDN, Voice, MFC-R2) . . . . . . . . . . . . . . . cfg 11-215
Green D, dynamic mode indicator . . . . . . . . . . . . . . . . . . . . . . . . . cfg 4-41
F Group ID. See Voice
Facilities. See X.25
FDB. See Bridges, forwarding database H
Fragmentation, frame relay (FRF.12) . . . . . . . . . . . . . . . . . . . . . cfg 9-151 Hardware Configuration
Frame Relay Offline . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 5-46
backup dial service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 9-151 Via a Serial Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 5-44
CIR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 9-140 Via IP Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 5-45
committed burst size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 9-140
configuring FRF5 service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 9-158 I
configuring FRF8 service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 9-160 I/O Cards
configuring FRF8+ service . . . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 9-162 Adding, Modifying, Deleting . . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 5-51
data compression . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 9-142 Installing CXTool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 2-22
DLCIs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 9-153 Internet protocol, about . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . pri 25-382
excess burst size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 9-141 Inverse ARP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . pri 25-385
fragmentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 9-142
fragmentation (FRF.12) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 9-151
multicast services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 9-143
multiple protocols - an illustration . . . . . . . . . . . . . . . . . . . . . . cfg 9-144
non-switched multicast service . . . . . . . . . . . . . . . . . . . . . . . . . cfg 9-165
port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 9-148
simplex services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 9-163
switched multicast service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 9-164
switching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 9-146
switching (MPE) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 9-147
switching services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 9-156
the ATM interworking services . . . . . . . . . . . . . . . . . . . . . . . . cfg 9-158
Frame Relay/ATM Network Interworking (FRF.5) - an illustration . . . . .
cfg 8-120

Index-484 3008M300-003
 CXTool User Guide

IP IPX
About TCP/IP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . pri 25-382 addressing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . pri 31-420
Address Classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . pri 25-382 packet. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . pri 31-421
configuring OSPF services - an illustration . . . . . . . . . . . . . cfg 10-175 packet handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 16-312
configuring the filter table . . . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 10-182 port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 16-309
DHCP relay . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 10-184 protocol architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . pri 31-420
dyanamic routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . pri 25-386 RIP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . pri 31-423
filtering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 10-168 routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . pri 31-422
Inverse ARP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . pri 25-385 SAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . pri 31-424
NBMA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 10-169 SAP filters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 16-313
NBMA functions - an illustration . . . . . . . . . . . . . . . . . . . . . . cfg 10-173 ISDN
NBMA-QOS functions - an illustration . . . . . . . . . . . . . . . . . cfg 10-171 Access Interface Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . pri 26-392
OSPF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . pri 25-386 backup service - an illustration . . . . . . . . . . . . . . . . . . . . . . . . cfg 11-198
OSPF area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 10-187 B-channel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . pri 26-392
overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . pri 25-382 B-channel (advanced) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 11-212
port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 10-189 data service point . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 11-213
QOS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 10-194 D-channel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . pri 26-392
QoS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 10-170 D-Channel (Advanced). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 11-213
Reverse ARP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . pri 25-385 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . pri 26-391
RIP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . pri 25-386 functional devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . pri 26-393
RIP services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 10-192, cfg 10-193 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . pri 26-390
RIP services - an illustration . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 10-177 ISDN service on a T1/E1 port . . . . . . . . . . . . . . . . . . . . . . . . . cfg 12-232
Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . pri 25-385 LAPD (advanced) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 11-209
static ARP table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 10-182 layer 3 (Advanced) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 11-211
static route table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 10-180 port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 11-204
static routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . pri 25-385 Q-Reference Point . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . pri 26-396
Subnet Masks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . pri 25-383 QSIG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . pri 26-396
TCP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . pri 25-384 QSIG channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . pri 26-392
traffic shaping - an illustration. . . . . . . . . . . . . . . . . . . . . . . . . cfg 10-173 reference points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . pri 26-394
traffic sorting - an illustration . . . . . . . . . . . . . . . . . . . . . . . . . cfg 10-174 Standards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . pri 26-390
Transmission Control Protocol . . . . . . . . . . . . . . . . . . . . . . . . pri 25-384 System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . pri 26-392
Tunneling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . pri 25-387
tunneling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 10-169 L
tunneling services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 10-196 LAPB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . pri 30-416
UDP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . pri 25-384 LAPB, X.25 over TCP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 15-304
WAN links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 10-186 Layer 2 - The Data Link Layer (X.25) . . . . . . . . . . . . . . . . . . . pri 30-416
Layer 3 - The Network Layer (X.25) . . . . . . . . . . . . . . . . . . . . pri 30-417
LCN Allocation. See X.25
LCP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . pri 32-428
Link Access Procedure Balanced-Balanced, LAPB . . . . . . . . pri 30-416
Link Control Protocol, LCP . . . . . . . . . . . . . . . . . . . . . . . . . . . . pri 32-428
LLC2 using X.25 over Ethernet . . . . . . . . . . . . . . . . . . . . . . . . . cfg 15-303

3008M300-003 Index-485
CXTool User Guide

LMI QSIG. See also ISDN

Flavor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 9-150
signaling standards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . pri 24-379 R
WAN connection information . . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 7-73 RARP, Reverse ARP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . pri 25-385
Reset, Avoiding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 4-40
M Reverse ARP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . pri 25-385
Memotec Devices and QSIG - an illustration . . . . . . . . . . . . . cfg 11-199 RIP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . pri 25-386
MFC-General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 7-109 Routing Information Protocol. . . . . . . . . . . . . . . . . . . . . . . . . . . pri 25-386
MFC-R2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 7-81, cfg 7-89 Routing, IP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . pri 25-385
MLPPP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 9-143, pri 32-427
and ISDN. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . pri 32-429 S
Establishing an MLPPP Link . . . . . . . . . . . . . . . . . . . . . . . . . pri 32-429 Script Files
Header . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . pri 32-429 loading . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 4-39
MLPPP bundle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 17-319 SNA
port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 17-316 configuration - an illustration . . . . . . . . . . . . . . . . . . . . . . . . . cfg 13-239
Reliable Transmission. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . pri 32-429 data link types (token ring, ethernet, frame relay, and X.25/QLLC) . . .
Module Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 3-26 pri 28-407
Multilink . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . pri 32-428 link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 13-240
LLC2 LAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 13-247
N LLC2 WAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 13-249
NCP. See Network Control Protocol nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . pri 28-408
Network Control Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . pri 32-428 SDLC control unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 13-245
Network Layer Layer 3 (X.25) . . . . . . . . . . . . . . . . . . . . . . . . . . pri 30-417 SDLC port. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 13-243
Source Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 18-322
O Source Routing Algorithm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . pri 33-435
Open Shortest Path First . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . pri 25-386 Source Routing Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 18-325
OSPF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . pri 25-386 Spanning Tree Algorithm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . pri 33-433
OSPF. See also IP Spanning Tree Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 18-329
Subnet Masks, IP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . pri 25-383
P Switched Virtual Circuit (SVC) . . . . . . . . . . . . . . . . . . . . . . . . . pri 30-417
Packet Layer Protocol (PLP) . . . . . . . . . . . . . . . . . . . . . . . . . . . pri 30-417 Synchronous Driver, Configuring . . . . . . . . . . . . . . . . . . . . . . . . . cfg 6-64
Permanent Virtual Circuit (PVC) . . . . . . . . . . . . . . . . . . . . . . . . pri 30-417 System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 2-22
PLP (Packet Layer Protocol) . . . . . . . . . . . . . . . . . . . . . . . . . . . pri 30-417
Point-to-Point Protocol (PPP) . . . . . . . . . . . . . . . . . . . . . . . . . . . pri 32-428
PVC (Permanent Virtual Circuit) . . . . . . . . . . . . . . . . . . . . . . . . pri 30-417

Q
Q-Reference Point. See ISDN
QSIG
Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . pri 26-391
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . pri 26-390
Standards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . pri 26-391

Index-486 3008M300-003

T Voice
T1/E1
channelized and unchannelized ports . . . . . . . . . . . . . . . . . . . cfg 12-218
channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 12-232
configuring timeslots for ISDN, voice, and data . . . . . . . . . cfg 12-234
frame formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . pri 27-401
node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . pri 27-399
port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 12-227
port - channelized. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 12-232
port - unchannelized . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 12-235
See also DIM
voice services on CX1000e - an illustration . . . . . . . . . . . . . cfg 12-224
voice services on CX950 - an illustration . . . . . . . . . . . . . . . cfg 12-222
TCP, Transmission Control Protocol . . . . . . . . . . . . . . . . . . . . . pri 25-384
TCP,,X.25 over, using LAPB . . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 15-304
TCP/IP, About . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . pri 25-382
Telephone, Trunks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . pri 22-360
Telephones, About . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . pri 22-358
Token Ring bridging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . pri 33-435
Token Ring Driver, Configuring . . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 6-69
Traffic Prioritization (Frame Relay) . . . . . . . . . . . . . . . . . . . . . . cfg 9-141
Transmission Control Protocol (TCP) . . . . . . . . . . . . . . . . . . . . pri 25-384
Trunks, Telephone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . pri 22-360
Tunneling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 8-119
Tunneling, IP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . pri 25-387
U
User Datagram Protocol (UDP) . . . . . . . . . . . . . . . . . . . . . . . . . pri 25-384
V
Virtual Circuit (VC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . pri 30-417
3008M300-003
CXTool User Guide
bandwidth group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 7-81
call progress tones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 7-106
CAS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 7-81, cfg 7-107
CCS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 7-82, cfg 7-108
channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 7-76
dial plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 7-93
dialing plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 7-77
digit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 7-104
digit regeneration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 7-80, cfg 7-94
group ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 7-80
local book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 7-80
local port - voice channel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 7-85
MFC-R2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 7-81
trunk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 7-81
Voice over Frame Relay - an illustration . . . . . . . . . . . . . . . . . . . cfg 7-82
Voice Signaling Methods (CAS, CCS) . . . . . . . . . . . . . . . . . . . pri 27-403
Voice Station . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 7-83
VoIP
channel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 7-90
trunk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 7-102
X
X.21 and X.21bis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . pri 30-416
Index-487
CXTool User Guide

X.25
CUG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 15-299
Extended Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 15-286
facilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 15-281
Hunt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 15-299
Interfaces of X.25 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . pri 30-417
LCN Allocation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 15-280
LL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 15-300
port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 15-278, cfg 15-289
Preamble . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . pri 30-416
PVCs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 15-296
PVCs - an ilustration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 15-273
remote DTE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 15-301
routing table (SVC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 15-298
service point - facilities. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 15-293
service point - LCN Allocation . . . . . . . . . . . . . . . . . . . . . . . . cfg 15-293
service point - timer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 15-295
SVCs - an illustration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 15-275
timer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 15-285
X.25 and OSI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . pri 30-416
X.25 service point . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 15-291
X.25 over Ethernet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 15-303
X.25 over TCP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cfg 15-304
X.28. See Async PAD
X.29. See Async PAD
X.3. See Async PAD

Index-488 3008M300-003