Manual Serie 3600 Newbridge

Information subject to change without notice.
Newbridge, the Newbridge logo and MainStreet are registered trademarks of Newbridge Networks Corporation.
Copyright 1997 Newbridge Networks Corporation.
All rights reserved
Distributor Disclaimer
Newbridge products are intended for standard commercial uses. Without the appropriate network design engineering,
they must not be sold, licensed or otherwise distributed for use in any hazardous environments requiring fail-safe
performance, such as in the operation of nuclear facilities, aircraft navigation or communication systems, air traffic control,
direct life-support machines, or weapons systems, in which the failure of products could lead directly to death, personal
injury, or severe physical or environmental damage. The distributor hereby agrees that the use, sale, licence or other
distribution of the products for any such application without the prior written consent of Newbridge, shall be at the
distributor's sole risk. The distributor hereby agrees to defend and hold Newbridge harmless from any claims for loss, cost,
damage, expense or liability that may arise out of or in connection with the use, sale, licence or other distribution of the
products in such applications.
PRINTED ON
RECYCLED PAPER
Customer Documentation and Product Support

Newbridge is committed to providing superior product documentation in
convenient and effective formats. Development and delivery of online
documentation is one way Newbridge continues to meet the changing needs of
customers.
For a wide range of documentation, see:
http://www.newbridge.com/documentation/index.html
Documentation Updates
Updates to Newbridge documentation, including Technical Practices, are easily
accessible on the World Wide Web.
For documentation updates, see:
http://www.newbridge.com/updates/index.html
TechInfo.NOW
TechInfo.NOW is a subscription service that gives customers access to the latest
Newbridge information, including new applications, improved methods of
configuration and upgrading, bug fixes, and product enhancements.
TechInfo.NOW provides access to:
Network Applications
Technical Practices
Technical Bulletins
Product Descriptions
General Information Books
Technical Updates
Software Updates
Upgrade Procedures
By providing up-to-date information, TechInfo.NOW can help customers increase

the business benefits of their Newbridge networks.
Subscribe to TechInfo.NOW at:
http://techinfo.now.newbridge.com
You can also order this service using part number 91-0030-01 TechInfo.NOW A La
Carte.
iii
Technical Support
Technical Support Engineers are available to assist you 24 hours a day, 7 days a
week.
To get technical help in your region, see the chart below:
Region
Contact Number
North and South America

Europe, Middle East and Africa
(703) 834-5300
(Within UK)
(Outside UK)
Asia Pacific and the former Soviet

Union
Internet
Fax Number
(703) 318-5153
0 1633 413 666

+44 1633 413 666
Australia
1 800 62 3645
Hong Kong
852 2807 3600
Japan
+81 45661 3612
Moscow
7 095 723 6375
http://www.newbridge.com
Customer Feedback
We value your feedback. Please direct questions or comments about Newbridge
documentation to:
http://www.newbridge.com/documentation/feedback.html
iv
3600 MainStreet Series Bandwidth Managers

NNP 95-2035-01-00-B
Table of Contents
Issue 1, November 1997
Table of Contents
Foreword
16. Getting Started

16.1
How to Use Operations and Configuration

16.1.1
16.1.2
16.2
Who Should Use this Manual ...................................................................... 16.1-1

How the Manual is Organized ...................................................................... 16.1-1
Getting Started ......................................................................................... 16.1-1
Node Parameters ..................................................................................... 16.1-1
Redundancy ............................................................................................. 16.1-1
System Cards .......................................................................................... 16.1-2
PRI Cards ................................................................................................ 16.1-2
Voice Interface Cards .............................................................................. 16.1-2
Data Interface Cards ................................................................................ 16.1-2
DSP Cards and IMCs ............................................................................... 16.1-2
DCP Cards ............................................................................................... 16.1-2
Frame Relay Services .............................................................................. 16.1-2
36120 MainStreet X.25 Service ............................................................... 16.1-2
BRI S/T Cards .......................................................................................... 16.1-2
CPCs ........................................................................................................ 16.1-3
HSA Cards ............................................................................................... 16.1-3
Running a Node Management Session

16.2.1
16.2.2
16.2.3
Table of Contents
Understanding Node Management Sessions .............................................. 16.2-1

Major nodes ............................................................................................. 16.2-2
Minor nodes ............................................................................................. 16.2-3
Active and inactive nodes ........................................................................ 16.2-3
Management Stations .................................................................................. 16.2-4
Network managers ................................................................................... 16.2-4
Craft Interface node manager .................................................................. 16.2-4
ASCII (VT100) terminal ............................................................................ 16.2-5
Connecting to System Serial Ports .............................................................. 16.2-6
Card faceplate serial ports ....................................................................... 16.2-7
Default configuration ................................................................................ 16.2-8
Pinouts ..................................................................................................... 16.2-8
(400)
xi
Table of Contents
16.3
Working with Node Management Sessions

16.3.1
16.3.2
16.3.3
16.3.4
16.3.5
16.3.6
16.4
Beginning a Node Management Session .................................................... 16.3-1

4601, 4602 and 46020 network managers .............................................. 16.3-1
Craft Interface .......................................................................................... 16.3-1
ASCII terminal .......................................................................................... 16.3-1
Screen Layout .............................................................................................. 16.3-2
Header line ............................................................................................... 16.3-2
Data area ................................................................................................. 16.3-3
Command line .......................................................................................... 16.3-4
Diagnostics line ........................................................................................ 16.3-4
Softkey area ............................................................................................. 16.3-4
Status line ................................................................................................ 16.3-4
Refreshing the display ............................................................................. 16.3-4
Softkeys ....................................................................................................... 16.3-4
Softkey menus ......................................................................................... 16.3-5
Selecting softkeys .................................................................................... 16.3-5
Instructions ............................................................................................... 16.3-6
Toggle softkeys ........................................................................................ 16.3-6
Softkey groups ......................................................................................... 16.3-6
Display-related softkeys ........................................................................... 16.3-6
Undoing a selection (CANCEL) ............................................................... 16.3-6
Returning to the main menu (QUIT) ......................................................... 16.3-7
To execute an instruction (PROCEED) .................................................... 16.3-7
To log off .................................................................................................. 16.3-7
Keyboard Entries ......................................................................................... 16.3-8
Keyboard entry formats ............................................................................ 16.3-8
To end a keyboard entry .......................................................................... 16.3-8
Trying a Sample Session ............................................................................. 16.3-9
To configure a card slot ........................................................................... 16.3-9
To configure a card slot using a tree form ............................................. 16.3-11
Programming Automatic Log-off ................................................................ 16.3-11
To program automatic log-off ................................................................. 16.3-12
Using Identifiers
16.4.1
16.4.2
16.4.3
16.4.4
xii

NNP 95-2035-01-00-B
About Identifiers ........................................................................................... 16.4-1

Shelf Identifiers ............................................................................................ 16.4-5
Switching shelf identifiers ......................................................................... 16.4-5
Locally controlled and peripheral shelf identifiers .................................... 16.4-6
HSPS identifiers ....................................................................................... 16.4-6
Shelf Numbers ............................................................................................. 16.4-6
Slot Numbers ............................................................................................... 16.4-7
Switching shelf ......................................................................................... 16.4-8
Locally controlled and peripheral shelves ................................................ 16.4-9
HSPS ..................................................................................................... 16.4-10
HSPS2 ................................................................................................... 16.4-11
(400)
Table of Contents

NNP 95-2035-01-00-B
16.5
Table of Contents
Displaying Configuration Information

16.5.1
16.5.2
Displaying Slot Information .......................................................................... 16.5-1

To view the switching shelf summary display .......................................... 16.5-1
To display the locally controlled, enhanced locally controlled,
peripheral shelf or DS-3 or E3 card summary .................................. 16.5-2
To display a detailed summary of a locally controlled, enhanced
locally controlled or peripheral shelf ................................................. 16.5-4
Displaying Card Information ........................................................................ 16.5-5
To display the Switching card summary .................................................. 16.5-5
To display a locally controlled, peripheral, DS-3 or E3 card
summary .......................................................................................... 16.5-6
To display summary information for an enhanced locally controlled
shelf .................................................................................................. 16.5-7
To display Control card module information for an enhanced locally
controlled shelf ................................................................................. 16.5-8
To display a circuit or connection summary ............................................. 16.5-9
To display a channel unit summary ....................................................... 16.5-11
17. Node Parameters

17.1
Circuit Connections
17.1.1
17.1.2
17.1.3
17.1.4
17.1.5
17.1.6
17.1.7
17.2
Understanding Connections ........................................................................ 17.1-1

Configuring Basic Circuit Connections ........................................................ 17.1-2
Using General Circuit Operations ................................................................ 17.1-3
To display circuit configuration information .............................................. 17.1-3
To name circuits ....................................................................................... 17.1-5
To copy circuit configuration .................................................................... 17.1-5
Configuring Simple Bidirectional Connections ............................................. 17.1-6
To configure simple bidirectional connections ......................................... 17.1-7
Configuring Simple Unidirectional Connections ........................................... 17.1-7
To configure simple unidirectional connections ....................................... 17.1-8
Configuring Broadcast Unidirectional Connections ..................................... 17.1-8
To configure broadcast unidirectional connections .................................. 17.1-9
Configuring TS0 Cross-connections ............................................................ 17.1-9
To configure TS0 cross-connections ....................................................... 17.1-9
Configuring Timing and Synchronization

17.2.1
17.2.2
17.2.3
17.2.4
Table of Contents
Understanding Timing and Synchronization ................................................ 17.2-1

Timing sources ............................................................................................ 17.2-1
Locally controlled shelf ............................................................................. 17.2-2
3600+ MainStreet enhanced locally controlled shelf ............................... 17.2-3
Peripheral shelf ........................................................................................ 17.2-4
Switching shelf ......................................................................................... 17.2-4
Synchronization methods ............................................................................ 17.2-5
Standalone ............................................................................................... 17.2-5
ANS .......................................................................................................... 17.2-7
Configuring Timing and Synchronization ................................................... 17.2-11
(400)
xiii
Table of Contents
17.2.5
17.2.6
17.2.7
17.2.8
17.2.9
17.3
Configuring ANS Node Parameters ........................................................... 17.2-13

Configuring the zone .............................................................................. 17.2-13
To enable and disable ANS on a node .................................................. 17.2-13
Configuring ANS Link Parameters ............................................................. 17.2-14
To display ANS links .............................................................................. 17.2-14
Enabling and disabling ANS on a link .................................................... 17.2-15
Link failure threshold .............................................................................. 17.2-16
Link failure recovery time ....................................................................... 17.2-16
SSU failure threshold ............................................................................. 17.2-17
SSU failure recovery time ...................................................................... 17.2-17
To configure ANS links .......................................................................... 17.2-18
Configuring Timing Sources ...................................................................... 17.2-18
Programmable external sources ............................................................ 17.2-19
Programmable derived sources ............................................................. 17.2-19
Internal source ....................................................................................... 17.2-19
Identifying a timing source ..................................................................... 17.2-19
To display the timing sources ................................................................ 17.2-20
Timing source parameters ..................................................................... 17.2-22
Timing source failures ............................................................................ 17.2-23
External timing frequency ...................................................................... 17.2-25
To configure timing sources for locally controlled shelves ..................... 17.2-28
To configure timing sources for switching shelves ................................. 17.2-29
To configure timing sources for peripheral shelves ............................... 17.2-30
To configure timing sources for enhanced locally controlled
shelves ........................................................................................... 17.2-31
To configure an external input timing source for the enhanced
locally controlled shelf .................................................................... 17.2-32
To configure timing output for an external timing receiver for
the enhanced locally controlled shelf ............................................. 17.2-32
Configuring Synchronization Status Messaging ........................................ 17.2-32
To configure synchronization status messaging .................................... 17.2-33
Configuring Synchronization Status Message Transmission ..................... 17.2-33
To configure synchronization status message transmission .................. 17.2-34
Serial and Ethernet Ports

17.3.1
xiv

NNP 95-2035-01-00-B
Understanding the Ports .............................................................................. 17.3-1

Location of backplane and bulkhead serial ports ..................................... 17.3-1
3600+ MainStreet Control card serial ports ............................................. 17.3-2
3600, 3645, 3664 and 36120 MainStreet Control cards serial ports ........ 17.3-3
CPCs ........................................................................................................ 17.3-4
DS-3 II, E3, DCP, FRS, FRE and PE cards ............................................. 17.3-4
Ethernet port ............................................................................................ 17.3-4
(400)
Table of Contents

NNP 95-2035-01-00-B
17.3.2
17.3.3
17.4
Configuring Serial Ports ............................................................................... 17.3-4

Device type .............................................................................................. 17.3-6
Baud rate ................................................................................................. 17.3-8
Flow control .............................................................................................. 17.3-9
Configuring CPSS cost on serial ports ................................................... 17.3-10
To configure Control card ports ............................................................. 17.3-10
To configure FRS, FRE and DCP card ports ......................................... 17.3-11
To configure FRE and PE card ports ..................................................... 17.3-11
To configure CPC ports ......................................................................... 17.3-12
To configure DS-3 II card ports .............................................................. 17.3-12
Configuring the Ethernet Port .................................................................... 17.3-12
Configuring the Ethernet port ................................................................. 17.3-15
Date, Time, and Node Name

17.4.1
17.5
Table of Contents
Configuring the Date, Time, and Node Name .............................................. 17.4-1

Date ......................................................................................................... 17.4-2
Time ......................................................................................................... 17.4-2
Node name .............................................................................................. 17.4-3
To configure the date, time, and node name ........................................... 17.4-3
Access Levels and Passwords

17.5.1
17.5.2
17.5.3
17.5.4
Table of Contents
Understanding Access Levels and Passwords ............................................ 17.5-1

Setting Access Levels and Passwords ........................................................ 17.5-1
Setting Access Levels .................................................................................. 17.5-2
Level 5 ..................................................................................................... 17.5-2
Levels 1 to 4 ............................................................................................. 17.5-3
Suggested definitions for levels 1 to 4 ..................................................... 17.5-4
Level 0 ..................................................................................................... 17.5-7
To define access levels 1 to 4 .................................................................. 17.5-8
To set level 0 access ............................................................................... 17.5-8
Setting Passwords ....................................................................................... 17.5-8
To set access-level passwords ................................................................ 17.5-9
(400)
xv
Table of Contents
17.6
CPSS Configuration
17.6.1
17.6.2
17.6.3
17.6.4
17.6.5
xvi

NNP 95-2035-01-00-B
Understanding CPSS Configuration ............................................................ 17.6-1

Shared CPSS circuits .............................................................................. 17.6-1
Dedicated CPSS circuits .......................................................................... 17.6-2
Backplane CPSS circuits ......................................................................... 17.6-2
FASTbus CPSS circuits ........................................................................... 17.6-2
CPSS cross-connections ......................................................................... 17.6-3
CPSS versions ......................................................................................... 17.6-3
Router version 2 ....................................................................................... 17.6-4
Domains ................................................................................................... 17.6-4
Enhanced network layer services ............................................................ 17.6-5
CPSS link cost ......................................................................................... 17.6-5
Master/slave protocol ............................................................................... 17.6-7
Upgrading to CPSSv2 .............................................................................. 17.6-8
CPSS status information ........................................................................ 17.6-10
CPSS grooming ..................................................................................... 17.6-10
Channel limitations ................................................................................. 17.6-11
Configuring CPSS ...................................................................................... 17.6-12
Configuring CPSS Node Parameters ........................................................ 17.6-14
Node number ......................................................................................... 17.6-15
NOC number .......................................................................................... 17.6-16
Domain number ..................................................................................... 17.6-16
CPSS connection type ........................................................................... 17.6-16
Router version ........................................................................................ 17.6-17
Router version 2 FRS, FRE and PE card restrictions ............................ 17.6-17
Cost of shared CPSS ............................................................................. 17.6-17
To configure node parameters ............................................................... 17.6-18
To configure the CPSS connection type ................................................ 17.6-18
To configure FRS, FRE and PE card router version .............................. 17.6-18
Configuring CPSS Options ........................................................................ 17.6-18
Dedicated CPSS cost ............................................................................ 17.6-19
Interface speed ...................................................................................... 17.6-19
Satellite delay ......................................................................................... 17.6-19
Signalling Restrictions ............................................................................ 17.6-20
To configure Control, DS-3 II and E3 card CPSS options ..................... 17.6-20
To configure DCP card CPSS options ................................................... 17.6-20
Configuring 64 kb/s CPSS Channels ......................................................... 17.6-20
To connect a Control, DS-3 II or E3 card CPSS channel ...................... 17.6-21
To connect a DCP card CPSS channel ................................................. 17.6-22
(400)
Table of Contents

NNP 95-2035-01-00-B
17.6.6
17.6.7
17.6.8
17.6.9
17.6.10
17.6.11
17.7
Table of Contents
Configuring CPSS over FDL and TS0 ....................................................... 17.6-22

T1 cards ................................................................................................. 17.6-23
E1 cards ................................................................................................. 17.6-23
X.21 and V.35 PRI cards ....................................................................... 17.6-24
MPA cards ............................................................................................. 17.6-24
To enable or disable CPSS over FDL on Dual T1 cards ....................... 17.6-25
To enable or disable CPSS over TS0 for Dual E1 cards ....................... 17.6-25
To enable CPSS over TS0 for Dual E1-2 cards ..................................... 17.6-25
To disable CPSS over TS0 for Dual E1-2 cards .................................... 17.6-25
To configure CPSS over TS0 for MPA cards ......................................... 17.6-25
To disable CPSS over TS0 for MPA cards ............................................ 17.6-26
To configure CPSS over TS0 for X.21 or V.35 cards ............................. 17.6-26
To connect or disconnect a Control card CPSS channel on
FDL or TS0 ..................................................................................... 17.6-26
To connect or disconnect a DCP card CPSS channel on
FDL or TS0 ..................................................................................... 17.6-26
Configuring Subrate CPSS Channels ........................................................ 17.6-27
To configure a Control card CPSS channel ........................................... 17.6-30
To configure a 4 kb/s DCP card CPSS channel .................................... 17.6-31
To configure an 8 to 56 kb/s DCP card CPSS channel (no SRMs) ....... 17.6-31
To configure an 8 to 56 kb/s DCP card CPSS channel (SRMs) ............ 17.6-32
Network Manager CPSS Connections ....................................................... 17.6-33
Connecting to the serial ports on the backplane .................................... 17.6-33
Connecting to the PSTN and modems .................................................. 17.6-33
FRS Card CPSS Connections ................................................................... 17.6-33
CPSS rerouting after fault detection in a frame relay network ............... 17.6-34
FASTbus CPSS Connections .................................................................... 17.6-35
To connect FASTbus CPSS circuits ...................................................... 17.6-36
To configure CPSS timers ..................................................................... 17.6-37
CPSS Routing Protocol ............................................................................. 17.6-37
To configure CPSS routing protocol ...................................................... 17.6-38
Backplane Card Communications

17.7.1
17.7.2
17.7.3
Overview ...................................................................................................... 17.7-1

Backplane Card Communication Types ...................................................... 17.7-1
To configure backplane card communications ......................................... 17.7-2
Fault Handling .............................................................................................. 17.7-2
Standard mode ........................................................................................ 17.7-2
Enhanced mode ....................................................................................... 17.7-2
To configure fault handling ....................................................................... 17.7-5
18. Redundancy
18.1
Control Redundancy
18.1.1
18.1.2
Table of Contents
Understanding Control Redundancy ............................................................ 18.1-1

3600+ MainStreet Control card ................................................................ 18.1-2
Configuring Control Redundancy ................................................................. 18.1-2
(400)
xvii
Table of Contents
18.1.3
18.1.4
18.1.5
18.1.6
18.1.7
18.1.8
18.1.9
18.2
Configuring Control Redundancy Parameters ............................................. 18.1-4

Configuring 3600, 3645, 3664 and 36120 MainStreet Control
cards for redundancy ....................................................................... 18.1-5
To configure 3600, 3645, 3664 and 36120 MainStreet Control
cards for redundancy ....................................................................... 18.1-5
Configuring 3600+ MainStreet Control card redundancy ......................... 18.1-5
To configure 3600+ MainStreet Control card redundancy ....................... 18.1-6
Configuring DS-3 II and E3 card redundancy .......................................... 18.1-6
To configure DS-3 II and E3 card redundancy ......................................... 18.1-7
To display control redundancy information .............................................. 18.1-7
Configuring Standby Modes ........................................................................ 18.1-8
Hot standby .............................................................................................. 18.1-8
Partitioned ................................................................................................ 18.1-9
To configure standby mode ................................................................... 18.1-10
Displaying System Demerits ...................................................................... 18.1-10
To display system demerits for a locally controlled or enhanced
locally controlled shelf .................................................................... 18.1-12
To display system demerits for a locally controlled, enhanced locally
controlled, switching or peripheral shelf, DS-3 II or E3 card .......... 18.1-12
To display system demerits for a Control card ....................................... 18.1-12
Configuring an Activity Switch ................................................................... 18.1-12
Alarms .................................................................................................... 18.1-13
Database reconciliation .......................................................................... 18.1-13
To force an activity switch ...................................................................... 18.1-14
Configuring Fast Protection Switching ....................................................... 18.1-15
Protection switching options .................................................................. 18.1-15
To configure DS-3 II fast protection switching ....................................... 18.1-17
To configure E3 fast protection switching .............................................. 18.1-17
Configuring Automatic Activity Switching ................................................... 18.1-17
To configure automatic activity switching ............................................... 18.1-18
Replacing a Control, DS-3, DS-3 II or E3 Card ......................................... 18.1-18
To replace a Control, DS-3, DS-3 II or E3 card ..................................... 18.1-18
Protection Switching
18.2.1
18.2.2
18.2.3
18.2.4
xviii

NNP 95-2035-01-00-B
Understanding Protection Switching ............................................................ 18.2-1

Configuring Protection Circuits .................................................................... 18.2-3
Designing Protecting Circuits ....................................................................... 18.2-3
Automatic override ................................................................................... 18.2-3
Circular protection .................................................................................... 18.2-4
Super-rate protection ............................................................................... 18.2-4
Using different cards ................................................................................ 18.2-4
Compatibility ............................................................................................ 18.2-4
Activity Qualified Access .......................................................................... 18.2-5
Configuring Protecting Connections ............................................................ 18.2-6
To configure protecting connections ........................................................ 18.2-7
To configure TTC2M cards as a protecting connection ........................... 18.2-7
To disconnect the protecting TTC2M card connection ............................ 18.2-7
(400)
Table of Contents

NNP 95-2035-01-00-B
18.3
Table of Contents
PRI Redundancy
18.3.1
18.3.2
18.3.3
18.3.4
18.3.5
18.3.6
18.3.7
Understanding PRI Redundancy ................................................................. 18.3-1

Hardware requirements ........................................................................... 18.3-1
Configuring PRI Redundancy ...................................................................... 18.3-2
Configuring PRI Redundancy Parameters ................................................... 18.3-3
To configure PRI redundancy .................................................................. 18.3-3
Handling Failures ......................................................................................... 18.3-3
Operating rules ........................................................................................ 18.3-4
Link faults ................................................................................................. 18.3-5
Forcing an Activity Switch ............................................................................ 18.3-6
Ones density on T1 links .......................................................................... 18.3-6
To force an activity switch ........................................................................ 18.3-6
Alarms ...................................................................................................... 18.3-6
Handling Fault Processing ........................................................................... 18.3-7
To clear outstanding demerit points ......................................................... 18.3-8
Example ................................................................................................... 18.3-8
Clearing Card Failures ................................................................................. 18.3-8
Alarms ...................................................................................................... 18.3-9
To clear card failures ............................................................................... 18.3-9
19. System Cards

19.1
Understanding System Card Configuration

19.1.1
19.1.2
19.2
Understanding System Cards ...................................................................... 19.1-1

Control cards ............................................................................................ 19.1-1
Expander card .......................................................................................... 19.1-1
Switching card .......................................................................................... 19.1-1
Common Carrier card .............................................................................. 19.1-2
Test card .................................................................................................. 19.1-2
GFC3 ....................................................................................................... 19.1-2
Configuring System Cards ........................................................................... 19.1-2
Control card parameters and options ....................................................... 19.1-2
Expander card parameters and options ................................................... 19.1-3
Switching card parameters and options ................................................... 19.1-3
Common Carrier card parameters and options ........................................ 19.1-3
Test card configuration parameters and options ...................................... 19.1-3
GFC3 configuration parameters and options ........................................... 19.1-6
Understanding GFC3 Card Operation

19.2.1
Table of Contents
GFC3 Card Operations ................................................................................ 19.2-1

To configure GFC3 card operations ......................................................... 19.2-2
(400)
xix
Table of Contents
19.3

NNP 95-2035-01-00-B
System Card Slots

19.3.1
19.3.2
19.3.3
19.3.4
19.3.5
19.3.6
19.3.7
19.3.8
Understanding System Card Slots ............................................................... 19.3-1

3600 MainStreet series bandwidth managers .......................................... 19.3-1
3600+ MainStreet Bandwidth Manager ................................................... 19.3-1
Configuring the SCC3(8+) Card Slot ........................................................... 19.3-2
To configure the SCC3(8+) card slot ....................................................... 19.3-2
Configuring the Expander Card Slot ............................................................ 19.3-3
To configure the Expander card slot ........................................................ 19.3-3
Configuring the Switching Card Slot ............................................................ 19.3-4
To configure the Switching card slot ........................................................ 19.3-4
Configuring the Common Carrier Card Slot ................................................. 19.3-4
To configure the Common Carrier card slot ............................................. 19.3-4
Configuring the Test Card Slot .................................................................... 19.3-5
To configure the Test card slot ................................................................ 19.3-5
To configure the Test card for the Test module ....................................... 19.3-5
Configuring 3600+ MainStreet Bandwidth Manager System
Card Slots ........................................................................................... 19.3-5
Configuring the Narrowband and Broadband Switching modules ........... 19.3-5
To configure Control card modules .......................................................... 19.3-6
Configuring the General Facilities Card Slot ................................................ 19.3-7
To configure the GFC or GFC2 slot ......................................................... 19.3-7
To configure the GFC3 slot ...................................................................... 19.3-7
20. Primary Rate Interface Cards

20.1
Understanding PRI Card Configuration

20.1.1
20.1.2
xx
Understanding PRI Cards ............................................................................ 20.1-1

T1 cards ................................................................................................... 20.1-1
E1 cards ................................................................................................... 20.1-2
Optical Extension Cards .......................................................................... 20.1-2
T1, E1 and Optical Extension card modules ............................................ 20.1-2
MPA cards ............................................................................................... 20.1-4
TTC2M cards ........................................................................................... 20.1-5
X.21 and V.35 PRI cards ......................................................................... 20.1-5
DS-3 cards ............................................................................................... 20.1-5
E3 cards ................................................................................................... 20.1-5
Data interfaces ......................................................................................... 20.1-5
Configuring PRI Cards ................................................................................. 20.1-6
(400)
Table of Contents

NNP 95-2035-01-00-B
20.2
PRI Card Slots

20.2.1
20.2.2
20.2.3
20.3
20.3.3
20.3.4
Understanding E1-to-T1 Conversion ........................................................... 20.3-1

Configuring the CCM ................................................................................... 20.3-2
To enable or disable companding conversion on a T1 or E1 card ........... 20.3-2
Configuring the SAM .................................................................................... 20.3-2
To configure the SAM .............................................................................. 20.3-5
Enabling or Disabling Companding Conversion on the TTC2M Card ......... 20.3-5
To enable or disable companding conversion on the TTC2M card ......... 20.3-5
Voice Compression
20.4.1
20.4.2
20.4.3
20.5
Understanding PRI Card Slots ..................................................................... 20.2-1

Configuring T1, E1, Optical Extension, MPA, TTC2M, X.21 or
V.35 Card Slots ................................................................................... 20.2-1
To configure PRI card slots ...................................................................... 20.2-3
To configure T1 and E1 card slot options ................................................ 20.2-4
To configure Dual T1, Dual E1, Dual E1-2 and Optical Extension card
slot options ....................................................................................... 20.2-4
To configure Dual T1-2 card slot options ................................................. 20.2-4
To configure ISDN and IFM link options for Dual E1 and Optical
Extension cards ................................................................................ 20.2-4
To configure ISDN on Dual T1-2 and Dual E1-2 card links ..................... 20.2-4
To configure Unidirectional cards ............................................................ 20.2-5
Configuring E3 Card Slots ........................................................................... 20.2-5
To configure E3 card slots ....................................................................... 20.2-5
E1-to-T1 Conversion
20.3.1
20.3.2
20.4
Table of Contents
Understanding Voice Compression ............................................................. 20.4-1

Viewing Compressor Connections ............................................................... 20.4-4
To view compressor connections ............................................................. 20.4-4
To view sub-channel connections ............................................................ 20.4-5
Configuring Voice Compression .................................................................. 20.4-6
To configure the DS0 that carries the compressed channels .................. 20.4-7
To set the compressor type as delta or transitional signalling ................. 20.4-7
To connect the subframe to a DS0 .......................................................... 20.4-8
To connect a voice channel to the VCM .................................................. 20.4-8
Timeslot 24 Signalling
20.5.1
20.5.2
Table of Contents
Understanding Timeslot 24 Signalling on Dual T1 and Dual T1-2 Cards .... 20.5-1
Configuring Timeslot 24 Signalling on Dual T1 and Dual T1-2 Cards ......... 20.5-2
To configure the DRM for a Dual T1-2 card ............................................. 20.5-2
To configure a Dual T1-2 link for timeslot 24 signalling ........................... 20.5-2
To configure a Dual T1 card for timeslot 24 signalling ............................. 20.5-2
(400)
xxi
Table of Contents
20.6
Framing
20.6.1
20.6.2
20.6.3
20.6.4
20.7
20.7.2
20.8.2
Understanding Zero Code Suppression ...................................................... 20.8-1

Transparent framing ................................................................................. 20.8-1
Binary 8-zero suppression framing .......................................................... 20.8-2
Jam bit 7 framing ..................................................................................... 20.8-2
Configuring Zero Code Suppression ........................................................... 20.8-2
To configure zero code suppression for T1 cards .................................... 20.8-2
To configure zero code suppression for DS-3 or DS-3 II cards ............... 20.8-3
Trunk Conditioning
20.9.1
20.9.2
xxii
Configuring Line Length for a T1 Card ........................................................ 20.7-1

T1 card with a DSX-1 module or LIM ....................................................... 20.7-1
T1 card with a CSU or CSU2 module ...................................................... 20.7-1
To configure the line length for a T1 card ................................................ 20.7-2
Configuring Line Length for a DS-3 or DS-3 II Card .................................... 20.7-2
To configure line length for a DS-3 or DS-3 II card .................................. 20.7-2
Zero Code Suppression

20.8.1
20.9
Understanding Framing for PRI Cards ........................................................ 20.6-1

Configuring Framing for T1 and DS-3 or DS-3 II Cards ............................... 20.6-1
Transmit as received (AUTO) framing ..................................................... 20.6-1
M13 framing ............................................................................................. 20.6-2
C-bit parity framing ................................................................................... 20.6-2
D4 framing ............................................................................................... 20.6-2
ESF framing ............................................................................................. 20.6-2
To configure the DS-3 framing format for DS-3 or DS3 II cards .............. 20.6-3
To configure the DS-1 framing format for T1, Dual T1 and
DS-3 or DS-3 II cards ....................................................................... 20.6-3
To configure the DS-1 framing format for Dual T1-2 cards ...................... 20.6-3
Configuring Framing for E1, E3 and Optical Extension Cards ..................... 20.6-3
CAS framing ............................................................................................. 20.6-5
CCS framing ............................................................................................ 20.6-5
31 channels framing ................................................................................. 20.6-5
X.21 NTU framing .................................................................................... 20.6-5
To configure framing for E1 and E3 cards ............................................... 20.6-6
To configure framing for Dual E1, Dual E1-2 and Optical
Extension cards ................................................................................ 20.6-6
Configuring Framing for X.21 PRI-2 Cards .................................................. 20.6-7
To configure framing for X.21 PRI-2 cards .............................................. 20.6-7
Line Length
20.7.1
20.8

NNP 95-2035-01-00-B
Understanding Trunk Conditioning for PRI Cards ....................................... 20.9-1

One-way trunk conditioning ..................................................................... 20.9-2
Two-way trunk conditioning ..................................................................... 20.9-5
Disabling trunk conditioning ..................................................................... 20.9-6
To disable trunk conditioning for PRI cards ............................................. 20.9-6
Trunk Conditioning Configuration Overview ................................................ 20.9-7
(400)
Table of Contents

NNP 95-2035-01-00-B
20.9.3
20.9.4
20.9.5
Table of Contents
Configuring One-way or Two-way Trunk Conditioning ................................ 20.9-7

To select one-way or two-way trunk conditioning for Dual E1-2 and
Dual T1-2 cards ................................................................................ 20.9-7
To select one-way or two-way trunk conditioning for MPA cards ............ 20.9-7
To set other PRI cards for one-way or two-way trunk conditioning .......... 20.9-8
Understanding Fault Class Trunk Conditioning ........................................... 20.9-8
Enabling or Disabling Fault Classes for PRI Cards ................................... 20.9-10
Disabling trunk conditioning using fault classes ..................................... 20.9-10
To set fault classes for MPA cards ........................................................ 20.9-10
To set fault classes for TTC2M cards .................................................... 20.9-10
To set fault classes for other PRI cards ................................................. 20.9-11
20.10 Fault Signalling

20.10.1
20.10.2
Understanding Fault Signalling for PRI Cards ........................................... 20.10-1

Disabling fault signalling for PRI cards .................................................. 20.10-3
Fault signalling codes for PRI cards ...................................................... 20.10-3
3664 MainStreet E1 and T1 cards ......................................................... 20.10-4
Configuring Fault Signalling for PRI Cards ................................................ 20.10-4
Restrictions ............................................................................................ 20.10-4
To configure fault signalling for PRI cards ............................................. 20.10-5
To configure fault signalling for TTC2M cards ....................................... 20.10-5
To configure fault signalling for DS0-DP channel units .......................... 20.10-5
To configure unused channels in 3664 MainStreet T1 and E1 cards .... 20.10-5
To disable trunk conditioning on PRI card circuits ................................. 20.10-6
20.11 Custom Trunk Conditioning

20.11.1
20.11.2
Understanding Custom Trunk Conditioning ............................................... 20.11-1

Configuring Custom Trunk Conditioning for PRI Cards ............................. 20.11-3
To configure custom trunk conditioning for PRI cards ........................... 20.11-3
To configure custom trunk conditioning for TTC2M cards ..................... 20.11-3
To configure unused channels in 3664 MainStreet T1 and E1 cards .... 20.11-4
20.12 PRI Signalling

20.12.1
20.12.2
Table of Contents
Understanding Signalling for PRI Cards .................................................... 20.12-1

Signalling types for PRI cards ................................................................ 20.12-1
Compatible PRI signalling types ............................................................ 20.12-2
PLAR D3 signalling ................................................................................ 20.12-3
R2 digital signalling ................................................................................ 20.12-4
RBS ........................................................................................................ 20.12-4
Configuring Signalling forT1, DS-3 and DS-3 II Cards .............................. 20.12-5
To enable signalling for T1, DS-3 and DS-3 II cards ............................. 20.12-5
To enable or disable RBS for T1, DS-3 and DS-3 II cards .................... 20.12-5
To create clear channels for T1 and DS-3 or DS-3 II cards ................... 20.12-6
(400)
xxiii
Table of Contents
20.12.3
20.12.4

NNP 95-2035-01-00-B
Configuring Signalling for E1, MPA, Optical Extension, X.21 and

V.35 PRI, E3 and 64 kb/s Codirectional Cards ................................. 20.12-6
Unidirectional circuits ............................................................................. 20.12-6
64 kb/s Codirectional card bidirectional circuits ..................................... 20.12-7
64 kb/s Codirectional unidirectional circuits ........................................... 20.12-7
MPA card signalling channels ................................................................ 20.12-7
To configure signalling type for E1, MPA, X.21 and V.35 PRI,
E3 and 64 kb/s Codirectional cards ............................................... 20.12-8
Signalling for the TTC2M Card .................................................................. 20.12-8
20.13 Inversion
20.13.1
20.13.2
Understanding Inversion for PRI Cards ..................................................... 20.13-1

Configuring Inversion of PRI Card Circuits ................................................ 20.13-1
To configure inversion of PRI card circuits ............................................ 20.13-2
To configure inversion of TTC2M card circuits ...................................... 20.13-2
20.14 Loopback Detection

20.14.1
20.14.2
20.14.3
20.14.4
20.14.5
20.14.6
Understanding Loopback Detection for PRI Cards .................................... 20.14-1

CPSS Loopback Detection for PRI Cards ................................................. 20.14-3
To establish CPSS loopback detection for PRI cards ............................ 20.14-4
Establishing TS24 Loopback Detection for PRI Cards .............................. 20.14-4
Establishing On-fault Loopback Detection for PRI Cards .......................... 20.14-5
Establishing In-band Signature Loopback Detection ................................. 20.14-6
Configuring Loopback Detection for PRI Cards ......................................... 20.14-6
To configure loopback detection on the Dual E1-2 card ........................ 20.14-7
To configure loopback detection on the MPA card ................................ 20.14-7
To configure loopback detection for other PRI cards ............................. 20.14-8
20.15 Super-rate Circuits

20.15.1
20.15.2
20.15.3
20.15.4
xxiv
Understanding Super-rate Circuits for PRI Cards ...................................... 20.15-1

Contiguous super-rate circuits ............................................................... 20.15-2
Non-contiguous super-rate circuits ........................................................ 20.15-2
Equidistant super-rate circuits ................................................................ 20.15-3
Delay equalization .................................................................................. 20.15-4
Protecting super-rate circuits ................................................................. 20.15-4
Configuring Super-rate Circuits for PRI Cards ........................................... 20.15-4
To configure a bidirectional tandem super-rate circuit ........................... 20.15-6
To configure a unidirectional tandem super-rate circuit ......................... 20.15-6
Connecting Tandem Super-rate Circuits ................................................... 20.15-7
To connect tandem super-rate circuits ................................................... 20.15-8
Connecting Unidirectional Super-rate Broadcast Circuits .......................... 20.15-8
To connect the unidirectional super-rate broadcast source ................... 20.15-9
To add multiple broadcast destinations to the super-rate
broadcast circuit ............................................................................. 20.15-9
To disconnect the unidirectional super-rate broadcast
connection .................................................................................... 20.15-10
To disconnect a broadcast destination from the broadcast
connection .................................................................................... 20.15-10
To view all broadcast destinations ....................................................... 20.15-10
(400)
Table of Contents

NNP 95-2035-01-00-B
Table of Contents
20.16 24 DS0 Super-rate Circuit Protection

20.16.1
20.16.2
20.16.3
Understanding 24 DS0 Super-rate Circuit Protection for Dual T1-2 Cards 20.16-1
TS24 Frame Fault Signalling ..................................................................... 20.16-1
Normal operation ................................................................................... 20.16-1
TS24 frame fault signalling .................................................................... 20.16-2
Access and Tandem fault signalling ...................................................... 20.16-2
Fault recovery ........................................................................................ 20.16-3
Configuring 24 DS0 Circuit Protection for Dual T1-2 Cards ...................... 20.16-4
To configure the DRM for TS24 signalling ............................................. 20.16-4
To configure the link ............................................................................... 20.16-4
To connect two 24 DS0 super-rate circuits ............................................ 20.16-5
20.17 Link Monitoring and Error Thresholds

20.17.1
20.17.2
20.17.3
20.17.4
20.17.5
Understanding Link Monitoring and Error Thresholds ............................... 20.17-1

Configuring Link Monitoring for Dual T1 and Dual T1-2 Cards .................. 20.17-2
Errored seconds threshold for links on Dual T1 and Dual T1-2 card ..... 20.17-3
To configure link monitoring for Dual T1-2 cards ................................... 20.17-4
To configure link monitoring for Dual T1 cards ...................................... 20.17-4
Configuring Link Monitoring for Dual E1-2 Cards ...................................... 20.17-4
To view link monitoring thresholds ......................................................... 20.17-6
To configure link monitoring thresholds ................................................. 20.17-6
Configuring SES Limit for Dual T1 and Dual T1-2 Cards .......................... 20.17-7
To set the SES limit for Dual T1 cards ................................................... 20.17-7
Configuring SES and DGM Limits for the MPA card ................................. 20.17-8
To set the SES and DGM limits for MPA cards ..................................... 20.17-8
20.18 E1, E3 and Optical Extension Card Parameters

20.18.1
20.18.2
20.18.3
20.18.4
20.18.5
Table of Contents
Understanding E1, E3 and Optical Extension Card Parameters ............... 20.18-1

Configuring the NU bit for E1, E3 and Optical Extension Cards ................ 20.18-2
Single and Dual E3 cards ...................................................................... 20.18-2
To configure the NU bits for Single and Dual E3 cards ......................... 20.18-2
To read the received NU bits for Single and Dual E3 cards .................. 20.18-2
Dual E1and Dual E1-2 cards ................................................................. 20.18-2
To enable or disable NU bit cross-connections for
Dual E1 cards ................................................................................. 20.18-3
To enable or disable NU bit cross-connections for
Dual E1-2 cards ............................................................................. 20.18-3
Configuring Signal or Chassis Ground for E1 and Optical
Extension cards ................................................................................ 20.18-4
To configure signal ground for the E1 and Dual E1 cards ..................... 20.18-4
To configure signal or chassis ground for the Dual E1-2 card ............... 20.18-4
Configuring SES Limit for Dual E1 and Dual E1-2 ..................................... 20.18-5
To configure SES limit for the Dual E1 card .......................................... 20.18-6
To configure SES limit for the Dual E1-2 card ....................................... 20.18-6
Configuring BER for Dual E1 and Dual E1-2 Cards .................................. 20.18-6
To configure SA4 and BER Alarm for the Dual E1 card ........................ 20.18-8
To configure BER Alarm for the Dual E1-2 card .................................... 20.18-8
To configure the SA4 Bit for the Dual E1-2 card .................................... 20.18-8
(400)
xxv
Table of Contents
20.18.6
20.18.7
20.18.8
20.18.9

NNP 95-2035-01-00-B
Configuring the E-bit for Dual E1 and Dual E1-2 Cards ............................ 20.18-9
To configure the E-bit for the Dual E1 card .......................................... 20.18-10
To configure the E-bit for the Dual E1-2 card ...................................... 20.18-10
Configuring CRC4 Reframing for Dual E1 and Dual E1-2 Cards ............ 20.18-10
To configure CRC4 reframing for the Dual E1 card ............................. 20.18-10
To configure the CRC4 reframing for the Dual E1-2 card .................... 20.18-11
Configuring Equalization for E3 Cards ..................................................... 20.18-11
To configure equalization for E3 cards ................................................ 20.18-11
Configuring E1 Link Quality Monitoring for E3 Cards .............................. 20.18-11
20.19 X.21 and V.35 PRI Card Parameters

20.19.1
20.19.2
20.19.3
20.19.4
20.19.5
20.19.6
Understanding X.21 and V.35 PRI Card Parameters ................................ 20.19-1

Configuring Bandwidth Utilization for X.21 and V.35 PRI Cards ............... 20.19-1
Number of circuits for X.21 and V.35 PRI cards .................................... 20.19-1
Number of circuits with signalling for X.21 and V.35 PRI cards ............. 20.19-2
To configure bandwidth utilization for X.21 and V.35 PRI cards ............ 20.19-3
Configuring the Supervisory Channel for X.21 and V.35 PRI Cards ......... 20.19-4
To configure the supervisory channel for X.21 and V.35 PRI cards ...... 20.19-5
Configuring the Clocking Source for X.21 and V.35 PRI Cards ................. 20.19-6
To configure the clocking source for X.21 and V.35 PRI cards ............. 20.19-6
Configuring Clock Inversion for X.21 Cards ............................................... 20.19-6
To configure clock inversion for X.21 cards ........................................... 20.19-8
Configuring the Slip Buffer for X.21 and V.35 PRI Cards .......................... 20.19-8
To configure the slip buffer for X.21 and V.35 PRI cards ....................... 20.19-8
20.20 MPA Card Parameters

20.20.1
20.20.2
General Configuration Overview ................................................................ 20.20-1

Configuring the Interface Type .................................................................. 20.20-3
To configure the interface type .............................................................. 20.20-4
20.20.3 Configuring Device Gender ....................................................................... 20.20-4
To configure the device gender ............................................................. 20.20-4
20.20.4 Configuring Channels on the Interface ...................................................... 20.20-4
Restrictions ............................................................................................ 20.20-6
To set the number of channels on the interface ..................................... 20.20-6
To set the number of signalling channels on the interface ..................... 20.20-7
To set the voice or data channel on the interface .................................. 20.20-7
20.20.5 Configuring Transport Bandwidth .............................................................. 20.20-7
To set transport bandwidth .................................................................... 20.20-8
20.20.6 Configuring HCM Framing Type for TS0 ................................................... 20.20-8
To configure HCM framing type for TS0 ................................................ 20.20-9
20.20.7 Configuring TS0 Framing Bit Positions ...................................................... 20.20-9
To set the aggregate link framing A-bit position ................................... 20.20-10
To change the F-bit position on HCM1 and HCM2 framed TS0 .......... 20.20-11
20.20.8 Configuring an SRM HCM Data Circuit on TS0 ....................................... 20.20-11
20.20.9 Configuring Control Signals and Lead Initiated Loopbacks ..................... 20.20-12
To configure control lead signals ......................................................... 20.20-14
To configure OOS conditioning ............................................................ 20.20-15
To enable or disable lead-initiated local loopbacks ............................. 20.20-15
20.20.10 Configuring Clock Inversion ..................................................................... 20.20-15
To configure clock inversion ................................................................ 20.20-16
xxvi
(400)
Table of Contents

NNP 95-2035-01-00-B
Table of Contents
20.20.11 Configuring the Slip or Doppler Buffer ..................................................... 20.20-16

To configure the slip buffer size ........................................................... 20.20-16
To set the number of slips .................................................................... 20.20-16
To enable or disable the doppler buffer ............................................... 20.20-16
21. Voice Interface Cards

21.1
Understanding Voice Interface Card Configuration

21.1.1
21.1.2
21.2
Voice Interface Card Slots

21.2.1
21.2.2
21.3
Understanding Voice Interface Cards .......................................................... 21.1-1

4WTO Line card ....................................................................................... 21.1-1
E&M cards and channel units .................................................................. 21.1-1
LGE cards and channel units ................................................................... 21.1-2
LGS cards and channel units ................................................................... 21.1-2
4WDX channel unit .................................................................................. 21.1-2
MRD channel unit .................................................................................... 21.1-2
Configuring Voice Interface Cards ............................................................... 21.1-2
Understanding Voice Interface Card Slots ................................................... 21.2-1

Voice interface cards ............................................................................... 21.2-1
Voice interface channel units ................................................................... 21.2-1
Companding laws .................................................................................... 21.2-2
Configuring Voice Interface Cards and Channel Units ................................ 21.2-3
To configure voice interface card slots .................................................... 21.2-4
To configure voice interface channel unit slots ........................................ 21.2-4
To configure the E&M and LGS CU companding law .............................. 21.2-5
Voice Interface Signalling

21.3.1
21.3.2
21.3.3
Table of Contents
Configuring E&M Signalling ......................................................................... 21.3-1

E&M signalling mode ............................................................................... 21.3-1
E&M signalling type ................................................................................. 21.3-1
To configure E&M card signalling ............................................................ 21.3-4
To configure E&M channel unit signalling ................................................ 21.3-4
Configuring LGE and LGS Signalling .......................................................... 21.3-4
LGE and LGS signalling types ................................................................. 21.3-6
To configure LGE signalling type ............................................................. 21.3-7
To configure LGS signalling type ............................................................. 21.3-7
Configuring 4WDX Signalling ...................................................................... 21.3-7
4WDX signalling mode ............................................................................. 21.3-8
To configure 4WDX signalling mode ........................................................ 21.3-9
(400)
xxvii
Table of Contents
21.4
Audio Wires
21.4.1
21.4.2
21.5
21.5.3
21.6.2
21.7.2
Understanding Line Balance for Voice Interface Cards and

Channel Units ..................................................................................... 21.7-1
Configuring Line Balance for Voice Interface Cards and
Channel Units ..................................................................................... 21.7-1
To configure line balance for E&M cards ................................................. 21.7-1
To configure line balance for LGE cards .................................................. 21.7-1
To configure line balance for LGS cards .................................................. 21.7-2
Line balance for channel units ................................................................. 21.7-2
To configure line balance for channel units ............................................. 21.7-3
Voice Interface Fault Signalling

21.8.1
21.8.2
xxviii
Understanding Line Impedance for Voice Interface Cards and

Channel Units ..................................................................................... 21.6-1
Configuring Line Impedance for Voice Interface Cards and
Channel Units ..................................................................................... 21.6-2
Configuring line impedance for E&M cards .............................................. 21.6-2
To configure line impedance for E&M cards ............................................ 21.6-2
Configuring line impedance for LGE and LGS cards ............................... 21.6-2
To configure line impedance for LGE and LGS cards ............................. 21.6-3
Configuring line impedance for channel units .......................................... 21.6-3
To configure line impedance for channel units ........................................ 21.6-3
Configuring line impedance for 4WDX channel units ............................... 21.6-3
To configure line impedance for 4WDX channel units ............................. 21.6-4
Line Balance
21.7.1
21.8
Understanding TLPs for Voice Interface Cards and Channel Units ............. 21.5-1
Configuring TLP Levels for Voice Interface Cards and Channel Units ........ 21.5-2
To select TLP levels for voice interface cards and channel units ............ 21.5-7
Configuring TLP Ranges for Voice Interface Cards ..................................... 21.5-7
To select a TLP range for the E&M card .................................................. 21.5-7
To select a TLP range for the LGE and LGS card ................................... 21.5-8
Line Impedance
21.6.1
21.7
Understanding Audio Wires for E&M Cards and Channel Units .................. 21.4-1
Configuring Audio Wires for E&M Cards and Channel Units ....................... 21.4-1
To configure audio wires for E&M cards .................................................. 21.4-1
To configure audio wires for E&M channel units ...................................... 21.4-1
TLPs
21.5.1
21.5.2
21.6

NNP 95-2035-01-00-B
Understanding Fault Signalling for Voice Interface Cards and

Channel Units ..................................................................................... 21.8-1
Configuring Fault Signalling for Voice Interface Cards and
Channel Units ..................................................................................... 21.8-1
To configure fault signalling for voice interface cards and
channel units .................................................................................... 21.8-1
(400)
Table of Contents

NNP 95-2035-01-00-B
21.9
Table of Contents
Tx Mute
21.9.1
21.9.2
Understanding Tx Mute for Voice Interface Channel Units .......................... 21.9-1

Enabling and disabling Tx mute for voice interface channel units ............... 21.9-2
Tx mute restrictions .................................................................................. 21.9-2
To enable and disable Tx mute for voice interface channel units ............ 21.9-2
21.10 Loop Balance

21.10.1
21.10.2
Understanding Loop Balance for 4WDX Channel Units ............................ 21.10-1

Configuring Loop Balance for 4WDX Channel Units ................................. 21.10-1
To configure loop balance for 4WDX channel units ............................... 21.10-2
21.11 Equalization
21.11.1
21.11.2
Understanding Equalization for 4WDX Channel Units ............................... 21.11-1

Configuring Equalization for 4WDX Channel Units .................................... 21.11-1
To configure equalization for 4WDX channel units ................................ 21.11-2
22. Data Interface Cards

22.1
Understanding Data Interface Card Configuration

22.1.1
22.1.2
22.1.3
22.1.4
22.2
Understanding Data Interface Cards ........................................................... 22.1-1

Direct Connect cards ............................................................................... 22.1-1
2B1Q, 27LC2 and DNIC Line cards ......................................................... 22.1-2
64 kb/s Codirectional card ....................................................................... 22.1-3
2B1Q channel unit ................................................................................... 22.1-4
4WTO channel unit .................................................................................. 22.1-5
DS0-DP channel unit ............................................................................... 22.1-5
OCU-DP channel unit .............................................................................. 22.1-5
Configuring DCCs and Line Cards .............................................................. 22.1-6
Connecting DTUs ........................................................................................ 22.1-6
Connecting 2600 and 2700 MainStreet series DTUs ............................... 22.1-6
Connecting a 2606 MainStreet DTU ........................................................ 22.1-7
Connecting a 2608 MainStreet DTU ........................................................ 22.1-7
To connect 2610 MainStreet DTU CPSS PAD ........................................ 22.1-8
Configuring Data Interface Cards ................................................................ 22.1-8
Data Interface Card Slots

22.2.1
22.2.2
22.2.3
22.2.4
Table of Contents
Understanding Data Interface Card Slots .................................................... 22.2-1

Configuring DCC slots ................................................................................. 22.2-1
To configure DCC slots ............................................................................ 22.2-2
Configuring Line Card Slots ......................................................................... 22.2-2
To configure line card slots ...................................................................... 22.2-3
Configuring 64 kb/s Codirectional Card Slots .............................................. 22.2-4
To configure 64 kb/s Codirectional card slots .......................................... 22.2-4
(400)
xxix
Table of Contents
22.2.5
22.3
Configuring Data Interface Channel Unit Slots ............................................ 22.2-4

To configure data interface channel unit slots ......................................... 22.2-5
To configure unit applications for a 2B1Q channel unit ........................... 22.2-5
Data Interface Circuits

22.3.1
22.3.2
22.3.3
22.3.4
22.3.5
22.3.6
22.3.7
22.3.8
22.3.9
22.3.10
22.3.11
22.3.12
22.3.13
22.3.14
xxx

NNP 95-2035-01-00-B
Understanding Data Interface Circuit Parameters ....................................... 22.3-1

Configuring Interface Type .......................................................................... 22.3-1
To configure interface type ...................................................................... 22.3-1
Configuring Device Mode ............................................................................ 22.3-2
To configure device mode ........................................................................ 22.3-2
Configuring Device Gender ......................................................................... 22.3-2
To configure device gender ..................................................................... 22.3-3
Configuring Duplex Method ......................................................................... 22.3-3
To configure duplex method .................................................................... 22.3-3
Configuring RTS/CTS Delay ........................................................................ 22.3-4
To configure RTS/CTS delay ................................................................... 22.3-4
Configuring Control Signals ......................................................................... 22.3-4
Enabling or disabling LL and RL control leads ......................................... 22.3-5
Configuring control signals ....................................................................... 22.3-5
To configure control signals ..................................................................... 22.3-7
Configuring OOS conditioning ................................................................. 22.3-7
To configure OOS conditioning ................................................................ 22.3-8
Configuring Clocking .................................................................................... 22.3-8
Transmit clock .......................................................................................... 22.3-9
Clock locked or independent .................................................................... 22.3-9
RS-422 DCC clocking ............................................................................ 22.3-10
Configuration limitations ......................................................................... 22.3-11
Configuring transmit clock ...................................................................... 22.3-12
Receive clock inversion ......................................................................... 22.3-13
To configure clocking ............................................................................. 22.3-13
Configuring Character Length, Stop Bits and Parity .................................. 22.3-13
To configure character length, stop bits and parity ................................ 22.3-14
Configuring Inversion ................................................................................. 22.3-14
To configure inversion ............................................................................ 22.3-14
Configuring SBM Depth ............................................................................. 22.3-15
To configure SBM depth ........................................................................ 22.3-15
Configuring Multidrop Master and Slave Devices ...................................... 22.3-15
To configure multidrop master and slave devices .................................. 22.3-15
Configuring Signal Propagation ................................................................. 22.3-16
Configuring RTS propagation ................................................................ 22.3-16
To propagate RTS ................................................................................. 22.3-16
To disable propagation .......................................................................... 22.3-16
Configuring control signal propagation .................................................. 22.3-16
To configure control signal propagation ................................................. 22.3-17
Configuring Super-rate DCC circuits ......................................................... 22.3-17
Transport bandwidth .............................................................................. 22.3-17
Valid interface speeds ............................................................................ 22.3-18
Clocking ................................................................................................. 22.3-21
To configure super-rate DCCs ............................................................... 22.3-21
(400)
Table of Contents

NNP 95-2035-01-00-B
22.3.15
22.3.16
22.3.17
22.3.18
22.3.19
22.3.20
22.3.21
22.3.22
22.3.23
22.3.24
22.3.25
22.3.26
Table of Contents
Table of Contents
Configuring Super-rate Line Card Circuits ................................................. 22.3-22

Configuration summary .......................................................................... 22.3-23
Setting up and connecting the DTU ....................................................... 22.3-23
To configure the DTU ............................................................................. 22.3-24
To connect the DTU to super-rate circuits ............................................. 22.3-24
Configuring DTU Port Redundancy ........................................................... 22.3-24
To configure the 2715 MainStreet DTU for redundant or
standalone operation ...................................................................... 22.3-25
To configure mate settings ..................................................................... 22.3-25
Activity switching .................................................................................... 22.3-25
To configure the debounce synchronization timer ................................. 22.3-27
Forced activity switching ........................................................................ 22.3-27
To force an activity switch ...................................................................... 22.3-28
Configuring a V.35 DCC Circuit for AQA ................................................... 22.3-28
To configure a V.35 DCC circuit for AQA ............................................... 22.3-28
Configuring 8 kHz Timing .......................................................................... 22.3-29
To configure 8 kHz timing ...................................................................... 22.3-29
Configuring the AIS .................................................................................... 22.3-29
To configure the AIS .............................................................................. 22.3-29
Configuring Interface Speed ...................................................................... 22.3-29
To configure interface speed ................................................................. 22.3-30
Configuring Error Correction ...................................................................... 22.3-30
To configure error correction .................................................................. 22.3-30
Configuring a Secondary Channel Operation ............................................ 22.3-31
To configure a secondary channel operation ......................................... 22.3-31
Configuring Switched 56 kb/s Operation ................................................... 22.3-31
To configure switched 56 kb/s operation ............................................... 22.3-31
Configuring Sealing Current ...................................................................... 22.3-32
To configure sealing current .................................................................. 22.3-32
Configuring a 2B1Q Channel Unit for ISDN Loop Extension ..................... 22.3-32
ISDN basics ........................................................................................... 22.3-32
ISDN loop extension .............................................................................. 22.3-33
3DS0 format ........................................................................................... 22.3-34
5DS0 format ........................................................................................... 22.3-34
2B1Q channel unit circuits ..................................................................... 22.3-35
To configure 2B1Q channel unit circuits ................................................ 22.3-36
To configure 3DS0 circuits ..................................................................... 22.3-36
To configure 5DS0 circuits ..................................................................... 22.3-36
Connecting 2B1Q channel unit circuits .................................................. 22.3-36
Connection example .............................................................................. 22.3-37
Complying with the 5DS0 format ........................................................... 22.3-37
Enabling or Disabling eoc for the 27LC2 Line Card ................................... 22.3-38
To enable or disable eoc on the 27LC2 line card .................................. 22.3-38
(400)
xxxi
Table of Contents
22.4

NNP 95-2035-01-00-B
DCC/Line Card Rate Adapted, SRM & Branch Channel

22.4.1
22.4.2
Understanding Rate Adaption, SRMs and Branch Channels ...................... 22.4-1

Configuring SRMs and Rate Adaption ......................................................... 22.4-3
Configuring DCCs for subrate multiplexing .............................................. 22.4-3
To configure DCCs for subrate multiplexing ............................................ 22.4-3
Configuring Line cards for rate adaption .................................................. 22.4-3
To configure Line cards for rate adaption ................................................ 22.4-4
To configure HCM and transparent rate adaption .................................... 22.4-4
To configure DDS and X.50 rate adaption ............................................... 22.4-5
To configure HCM and transparent SRMs ............................................... 22.4-6
To configure DDS SRMs .......................................................................... 22.4-6
23. DSP Cards and IMCs

23.1
Understanding DSP Card and IMC Configuration

23.1.1
23.1.2
23.2
Configuring Card Slots for DSP Cards and the IMC

23.2.1
23.3
Configuring Card Slots for the IMC and DSP Cards .................................... 23.2-1
Card type ................................................................................................. 23.2-1
Number of DSP card circuits .................................................................... 23.2-2
Hub identification ..................................................................................... 23.2-2
DSP card applications .............................................................................. 23.2-2
IMC BONDING timers .............................................................................. 23.2-3
To configure DSP card slots .................................................................... 23.2-3
To configure IMC slots ............................................................................. 23.2-5
Voice Compression
23.3.1
23.3.2
23.3.3
23.3.4
23.3.5
23.3.6
xxxii
Understanding DSP Cards and the IMC ...................................................... 23.1-1

Configuring DSP Cards and IMCs ............................................................... 23.1-2
DSP card configurable parameters .......................................................... 23.1-2
DSP card connection types ...................................................................... 23.1-7
IMC configurable parameters ................................................................... 23.1-8
Understanding Voice Compression ............................................................. 23.3-1

Voice Compression Using DSP Cards ........................................................ 23.3-1
Configuring the DSP Card Voice Compression Type .................................. 23.3-2
Configuring the Signalling Type for DSP Cards ........................................... 23.3-2
To configure signalling types ................................................................... 23.3-3
Configuring Rate Adaption Parameters for DSP Cards ............................... 23.3-4
Transparent rate adaption ........................................................................ 23.3-4
HCM rate adaption ................................................................................... 23.3-5
To configure the rate adaption parameters for DSP cards ...................... 23.3-5
Configuring the Companding Law for DSP Cards ....................................... 23.3-7
To configure the companding law for the DSP cards ............................... 23.3-8
(400)
Table of Contents

NNP 95-2035-01-00-B
23.3.7
23.3.8
23.4
23.4.2
Understanding PCM Multidrop Data Bridges ............................................... 23.4-1

PCM multidrop data bridge features ........................................................ 23.4-2
PCM multidrop data bridge sample application ....................................... 23.4-2
Antistreaming ........................................................................................... 23.4-3
Antistreaming timeout .............................................................................. 23.4-3
ADI ........................................................................................................... 23.4-4
Configuring PCM Multidrop Data Bridges .................................................... 23.4-4
To configure the card for PCM multidrop ................................................. 23.4-5
To configure the circuit for PCM multidrop ............................................... 23.4-5
To connect to the master circuit ............................................................... 23.4-5
To connect to the branch circuit ............................................................... 23.4-5
To configure master circuits ..................................................................... 23.4-5
To configure branch circuits ..................................................................... 23.4-5
Voice Conference Bridges

23.5.1
23.5.2
23.5.3
23.6
Configuring the Voice Compression Parameters ......................................... 23.3-9

Echo cancellation ..................................................................................... 23.3-9
Echo cancellation return loss threshold ................................................. 23.3-10
Echo clipping .......................................................................................... 23.3-10
6 dB attenuation pad .............................................................................. 23.3-10
AC15 tone detection .............................................................................. 23.3-11
LD-CELP post filter ................................................................................ 23.3-11
To configure voice compression parameters on the DSP cards ............ 23.3-11
Connecting Circuits for Voice Compression .............................................. 23.3-12
Valid input connections .......................................................................... 23.3-13
Valid output connections ........................................................................ 23.3-13
To connect the circuits for voice compression ....................................... 23.3-14
PCM Multidrop Data Bridges

23.4.1
23.5
Table of Contents
Understanding Voice Conference Bridges ................................................... 23.5-1

VCB Restrictions ...................................................................................... 23.5-3
Configuring Voice Conference Bridges ........................................................ 23.5-3
To configure the card for VCB ................................................................. 23.5-3
To configure the circuit for VCB ............................................................... 23.5-4
VCB conference parameters .................................................................... 23.5-4
To configure VCB inputs .......................................................................... 23.5-6
Broadcast mode ....................................................................................... 23.5-6
To configure broadcast mode .................................................................. 23.5-6
To configure the broadcaster ................................................................... 23.5-6
Connecting Voice Conference Bridges ........................................................ 23.5-7
To connect a VCB .................................................................................... 23.5-7
To connect a cascading bridge ................................................................ 23.5-8
Rate Adaption and SRMs

23.6.1
Table of Contents
Understanding Rate Adaption ...................................................................... 23.6-1

About transparent rate adaption .............................................................. 23.6-1
About HCM rate adaption ........................................................................ 23.6-3
About DDS rate adaption ......................................................................... 23.6-4
About X.50 rate adaption ....................................................................... 23.6-11
(400)
xxxiii
Table of Contents
23.6.2
23.6.3
23.6.4
23.6.5
23.6.6
23.6.7
23.6.8
23.6.9
23.6.10
23.6.11
23.6.12
xxxiv

NNP 95-2035-01-00-B
Understanding SRMs ................................................................................. 23.6-16

Transparent SRMs ................................................................................. 23.6-16
HCM SRMs ............................................................................................ 23.6-17
DDS SRMs ............................................................................................. 23.6-19
Cards supporting SRMs ......................................................................... 23.6-22
Understanding Branch Channels ............................................................... 23.6-26
Composite inputs ................................................................................... 23.6-27
User-reserved branch channels ............................................................. 23.6-27
Line cards .............................................................................................. 23.6-28
DSP cards .............................................................................................. 23.6-29
Understanding Transport Bandwidth ......................................................... 23.6-34
Transparent rate adaption ...................................................................... 23.6-34
HCM rate adaption ................................................................................. 23.6-35
Available data bandwidth ....................................................................... 23.6-36
Pointers for setting transport bandwidth ................................................ 23.6-36
Understanding Transport Position ............................................................. 23.6-37
Understanding Signalling ........................................................................... 23.6-38
S-bit signalling ........................................................................................ 23.6-39
H-bit Signalling ....................................................................................... 23.6-39
Understanding Interface Speed ................................................................. 23.6-40
DDS/X.50 rate adaption ......................................................................... 23.6-42
Understanding HCM Parameters ............................................................... 23.6-42
Setting the HCM frame bandwidth ......................................................... 23.6-42
Placing the HCM frame bandwidth ........................................................ 23.6-43
Setting the HCM data position ............................................................... 23.6-43
Understanding Subframe Position ............................................................. 23.6-43
Understanding Continuity Checking .......................................................... 23.6-45
Configuring Rate Adaption and SRMs ....................................................... 23.6-46
To configure the card for rate adaption and SRMs ................................ 23.6-47
To configure the rate adaption method .................................................. 23.6-47
To configure HCM and transparent SRMs ............................................. 23.6-48
To configure DDS SRMs ........................................................................ 23.6-48
To configure HCM and transparent branch channels ............................ 23.6-49
To configure DDS and X.50 branch channels ........................................ 23.6-49
Making SRM Connections ......................................................................... 23.6-50
DDS rules ............................................................................................... 23.6-50
X.50 rules ............................................................................................... 23.6-51
Making SRM connections ...................................................................... 23.6-51
To make SRM connections automatically .............................................. 23.6-51
To make SRM connections manually .................................................... 23.6-51
(400)
Table of Contents

NNP 95-2035-01-00-B
23.7
Multidrop Data Bridges and MJUs

23.7.1
23.7.2
23.7.3
23.7.4
23.8
Understanding Multidrop Data Bridges and MJUs ....................................... 23.7-1

Multidrop Data Bridges ............................................................................ 23.7-1
Circuit configuration ................................................................................. 23.7-2
DDS SRMs ............................................................................................... 23.7-2
MJUs ........................................................................................................ 23.7-3
Antistreaming ........................................................................................... 23.7-3
Configuring Multidrop Data Bridges ............................................................. 23.7-3
To configure multidrop data bridges ........................................................ 23.7-4
Configuring MJUs ........................................................................................ 23.7-4
To configure the card for SRMs ............................................................... 23.7-5
To configure the circuit for SRMs ............................................................. 23.7-5
To configure the composite branch channel ............................................ 23.7-5
To configure the SRM .............................................................................. 23.7-5
Configuring MJU Antistreaming ................................................................... 23.7-6
To configure antistreaming parameters ................................................... 23.7-7
To enable and disable an MJU branch .................................................... 23.7-7
Fax and Modem Data Transmission

23.8.1
23.8.2
23.9
Table of Contents
Configuring DSP Cards for Fax and Modem Data Transmission ................ 23.8-1
Configuring DSP Circuits for Data Transmission ......................................... 23.8-1
Enabling and disabling G3 fax relay ........................................................ 23.8-1
Enabling and disabling V.32 modem relay ............................................... 23.8-2
Data transmission rate ............................................................................. 23.8-2
Data bandwidth ........................................................................................ 23.8-3
NSF frame handling mode ....................................................................... 23.8-3
Data transmit level ................................................................................... 23.8-4
Automatic gain control ............................................................................. 23.8-4
To configure data transmission parameters for the DSP4 card ............... 23.8-5
To configure data transmission parameters for the DSP5 card ............... 23.8-5
To configure data transmission parameters for the DSP5H card ............ 23.8-6
Subrate Switching
23.9.1
23.9.2
23.9.3
23.9.4
Table of Contents
Understanding SRS ..................................................................................... 23.9-1

SRS display ............................................................................................. 23.9-2
Configuring SRS .......................................................................................... 23.9-3
To specify set identifiers .......................................................................... 23.9-4
To configure a DSP4 card for subrate switching ...................................... 23.9-5
To copy and change sets ......................................................................... 23.9-5
Creating Subrate Sets ................................................................................. 23.9-6
Transparent and HCM sets ...................................................................... 23.9-6
DDS and X.50 sets .................................................................................. 23.9-7
CPSS sets ................................................................................................ 23.9-7
To create sets .......................................................................................... 23.9-8
Configuring DS0 Ports ................................................................................. 23.9-9
Copying circuit configuration .................................................................... 23.9-9
(400)
xxxv
Table of Contents
23.9.5

NNP 95-2035-01-00-B
Making SRS Connections ............................................................................ 23.9-9

Making SRS connections ....................................................................... 23.9-10
To connect to an SRS DS0 port ............................................................. 23.9-10
To connect a transparent set ................................................................. 23.9-10
To connect an HCM set ......................................................................... 23.9-10
To connect a DDS or X.50 set ............................................................... 23.9-11
To connect a 4 kb/s CPSS circuit .......................................................... 23.9-11
23.10 BONDING
23.10.1
23.10.2
23.10.3
Understanding BONDING .......................................................................... 23.10-1

Using BONDING .................................................................................... 23.10-2
BONDING operation .............................................................................. 23.10-3
Configuring BONDING ............................................................................... 23.10-4
To configure BONDING ......................................................................... 23.10-4
Configuring BONDING call setup ........................................................... 23.10-4
To configure BONDING call setup ......................................................... 23.10-5
Making BONDING Connections ................................................................ 23.10-6
To connect the user side to the DSP ..................................................... 23.10-6
To connect the DSP to the network side ................................................ 23.10-6
23.11 Super Tandem Operation

23.11.1
23.11.2
Understanding Super Tandem Operation .................................................. 23.11-1

Configuring Super Tandem Operation for DSP Cards ............................... 23.11-2
To configure super tandem parameters on the DSP4 card ................... 23.11-3
To configure super tandem parameters on the DSP5H and
DSP5 cards .................................................................................... 23.11-3
23.12 Combined Voice Compression, Fax and Modem Operations

23.12.1
23.12.2
Understanding Combined Operations ....................................................... 23.12-1

Configuring Combined Operations ............................................................ 23.12-2
To configure the DSP4 card for combined operation ............................. 23.12-3
24. DCP Cards

24.1
Understanding DCP Card Configuration

24.1.1
24.1.2
24.2
DCP Card Slots

24.2.1
24.2.2
xxxvi
Understanding DCP Cards .......................................................................... 24.1-1

Configuring DCP Cards ............................................................................... 24.1-1
Understanding DCP Card Slots ................................................................... 24.2-1

Configuring DCP Card Slots ........................................................................ 24.2-1
To configure DCP card slots .................................................................... 24.2-2
(400)
Table of Contents

NNP 95-2035-01-00-B
Table of Contents
25. Frame Relay Services

25.1
Understanding Frame Relay Configuration

25.1.1
25.1.2
25.2
FRS, FRE and PE Card Slots

25.2.1
25.2.2
25.3
Understanding FRS, FRE and PE Card Slots ............................................. 25.2-1

Configuring FRS, FRE and PE Slots ........................................................... 25.2-1
To configure FRS, FRE and PE slots ...................................................... 25.2-2
Frame Relay Switch Congestion Parameters

25.3.1
25.3.2
25.4
Understanding Frame Relay on FRS, FRE and PE Cards .......................... 25.1-1

Frame streams ......................................................................................... 25.1-2
Data link connections ............................................................................... 25.1-2
Permanent virtual circuits ......................................................................... 25.1-3
Bandwidth use ......................................................................................... 25.1-3
Class-of-service parameters .................................................................... 25.1-4
Congestion management ......................................................................... 25.1-5
Link management protocol support ........................................................ 25.1-11
PVC management auto discovery protocol ............................................ 25.1-14
Configuration Overview ............................................................................. 25.1-15
Understanding Frame Relay Switch Congestion ......................................... 25.3-1

Configuring Frame Relay Switch Congestion Parameters .......................... 25.3-1
Frame switch congestion thresholds ........................................................ 25.3-3
Filtering .................................................................................................... 25.3-3
Clear time ................................................................................................. 25.3-4
Raise time ................................................................................................ 25.3-4
Report type .............................................................................................. 25.3-5
To configure switch congestion parameters ............................................ 25.3-5
FASTbus Configuration
25.4.1
25.4.2
Table of Contents
Understanding FASTbus Configuration ....................................................... 25.4-1

FASTbus topology ................................................................................... 25.4-1
FASTbus fault tolerance .......................................................................... 25.4-2
Viewing FASTbus station status .............................................................. 25.4-3
Configuring the FASTbus ............................................................................ 25.4-4
Viewing FASTbus parameters ................................................................. 25.4-4
Cable name .............................................................................................. 25.4-6
36120 ID .................................................................................................. 25.4-7
Station ID ................................................................................................. 25.4-7
FASTbus congestion thresholds .............................................................. 25.4-7
Filtering .................................................................................................... 25.4-8
Clear time ................................................................................................. 25.4-8
Raise time ................................................................................................ 25.4-9
Report type .............................................................................................. 25.4-9
To configure the FASTbus parameters .................................................. 25.4-10
(400)
xxxvii
Table of Contents
25.5
Creating Frame Streams

25.5.1
25.5.2
25.5.3
25.6
25.6.2
25.7.3
Understanding Data Link Connections ........................................................ 25.7-1

Viewing DLC Status Information .................................................................. 25.7-2
To view DLC status by frame stream ....................................................... 25.7-3
To view FASTbus DLC status .................................................................. 25.7-4
Configuring Data Link Connections ............................................................. 25.7-4
Configuring local DLCs ............................................................................ 25.7-5
To connect local DLCs ............................................................................. 25.7-6
Configuring card-to-card DLCs across the backplane ............................. 25.7-6
To connect card-to-card DLCs across the backplane .............................. 25.7-7
Configuring FASTbus DLCs ..................................................................... 25.7-7
To connect FASTbus DLCs ................................................................... 25.7-10
Class-of-service Parameters
25.8.1
xxxviii
Understanding Frame Stream Configuration ............................................... 25.6-1

Viewing frame stream status information ................................................. 25.6-1
To view frame stream status information ................................................. 25.6-3
Configuring Frame Stream Parameters ....................................................... 25.6-3
Frame stream congestion thresholds ....................................................... 25.6-5
Maximum frame size ................................................................................ 25.6-6
Flags between frames .............................................................................. 25.6-6
Protocol type ............................................................................................ 25.6-6
Heartbeat ................................................................................................. 25.6-7
Status rate ................................................................................................ 25.6-8
Timeout .................................................................................................... 25.6-8
Filtering .................................................................................................... 25.6-9
Clear time ................................................................................................. 25.6-9
Raise time .............................................................................................. 25.6-10
Report type ............................................................................................ 25.6-10
To configure frame stream parameters .................................................. 25.6-11
Data Link Connections

25.7.1
25.7.2
25.8
Understanding Frame Stream Creation ....................................................... 25.5-1

Local frame stream .................................................................................. 25.5-1
Card-to-card frame stream ....................................................................... 25.5-1
Configuring FRS, FRE and PE Circuits as Streams .................................... 25.5-2
Application ............................................................................................... 25.5-3
Transport bandwidth ................................................................................ 25.5-3
Interface speed ........................................................................................ 25.5-3
To configure an FRS, FRE or PE circuit as a stream .............................. 25.5-4
Connecting Frame Streams ......................................................................... 25.5-4
To connect a frame stream to a primary rate or data circuit .................... 25.5-5
To connect two frame stream circuits in the same node .......................... 25.5-6
Frame Stream Configuration

25.6.1
25.7

NNP 95-2035-01-00-B
Understanding Class-of-service Parameters ............................................... 25.8-1

Symmetric and asymmetric class-of-service ............................................ 25.8-1
Card-to-card DLCs ................................................................................... 25.8-1
DLCs over the FASTbus .......................................................................... 25.8-2
(400)
Table of Contents

NNP 95-2035-01-00-B
25.8.2
25.9
Table of Contents
Configuring Class-of-service Parameters and Rate Enforcement ............... 25.8-3

Class-of-service display ........................................................................... 25.8-3
Rate enforcement state ............................................................................ 25.8-4
Committed information rate ...................................................................... 25.8-5
Committed burst size ............................................................................... 25.8-5
Excess burst size ..................................................................................... 25.8-5
To configure class-of-service parameters and rate enforcement ............. 25.8-6
FRS Subrate Multiplexing

25.9.1
25.9.2
25.9.3
25.9.4
25.9.5
Understanding Subrate Multiplexing on the FRS Card ................................ 25.9-1

Interface speeds and protocols ................................................................ 25.9-1
Connections ............................................................................................. 25.9-2
SRIM configurable parameters ................................................................ 25.9-2
Configuring SRIM Card Options .................................................................. 25.9-4
Rate adaption ........................................................................................... 25.9-4
Speed range ............................................................................................ 25.9-5
Loopback detection .................................................................................. 25.9-5
A-bit handling ........................................................................................... 25.9-5
To configure the SRIM card options ........................................................ 25.9-5
Configuring Rate Adaption Circuits .............................................................. 25.9-6
To configure the rate adaption method .................................................... 25.9-7
To configure HCM circuits ........................................................................ 25.9-7
To configure DDS circuits ........................................................................ 25.9-7
Configuring Subrate Circuits ........................................................................ 25.9-8
To configure the rate adaption method .................................................... 25.9-9
To configure HCM streams ...................................................................... 25.9-9
To configure DDS and X.50 streams ..................................................... 25.9-10
To configure the circuit application ........................................................ 25.9-10
Connecting Subrate Streams ..................................................................... 25.9-10
To connect subrate streams .................................................................. 25.9-11
25.10 Frame Relay Encapsulation

25.10.1
25.10.2
25.10.3
25.10.4
25.10.5
Table of Contents
Understanding Frame Relay Encapsulation .............................................. 25.10-1

LAPB Annex G encapsulation ................................................................ 25.10-2
LAPB RFC 1490 encapsulation ............................................................. 25.10-3
Transparent HDLC encapsulation .......................................................... 25.10-5
Creating Frame Relay Encapsulation Circuits ........................................... 25.10-5
To create frame relay encapsulation circuits ......................................... 25.10-5
To create subrate frame relay encapsulation circuits ............................ 25.10-6
Viewing Encapsulation Circuit Parameters ................................................ 25.10-6
To view encapsulation circuit parameters .............................................. 25.10-8
Configuring Encapsulation Circuit Parameters .......................................... 25.10-8
Encapsulation circuit congestion thresholds .......................................... 25.10-8
Encapsulated protocol maximum frame size ......................................... 25.10-9
Encapsulation type ................................................................................. 25.10-9
To configure encapsulation circuit parameters .................................... 25.10-10
Connecting Encapsulation Circuits .......................................................... 25.10-10
To connect super-rate encapsulation circuits ...................................... 25.10-10
To connect subrate encapsulation circuits ........................................... 25.10-11
(400)
xxxix
Table of Contents

NNP 95-2035-01-00-B
25.11 Switched Access to Frame Relay PVCs

25.11.1
25.11.2
Understanding Switched Access to Frame Relay PVCs ........................... 25.11-1

Example configuration ........................................................................... 25.11-2
T1 Signalling Termination ...................................................................... 25.11-3
Newbridge system support .................................................................... 25.11-3
Central office switch requirements ......................................................... 25.11-3
Limitations and restrictions .................................................................... 25.11-4
Configuring Switched Access to Frame Relay PVCs ................................ 25.11-4
To provision switched access ................................................................ 25.11-5
26. Frame Relay SVC Service

26.1
Frame Relay Switched Virtual Circuits

26.1.1
26.1.2
26.1.3
26.2
SVC Signalling Channel Management

26.2.1
26.2.2
26.2.3
xl
Overview of Frame Relay SVCs .................................................................. 26.1-1

Physical requirements .............................................................................. 26.1-2
Call processing ........................................................................................ 26.1-2
Configuration Summary ............................................................................... 26.1-6
Setting up nodes at the edge of the network ........................................... 26.1-6
Setting up nodes within the network ........................................................ 26.1-6
Frame Relay SVC Configuration Example .................................................. 26.1-7
To configure the parameters for node e1613 through the
Control card .................................................................................... 26.1-10
FRE card ........................................................................................ 26.1-10
Control card .................................................................................... 26.1-11
FRE card ........................................................................................ 26.1-11
Control card .................................................................................... 26.1-12
FRE card ........................................................................................ 26.1-13
Understanding Signalling Channel Management ........................................ 26.2-1

Signalling Channel Connection and Disconnection ..................................... 26.2-1
To view and connect or disconnect a signalling channel ......................... 26.2-2
Signalling Channel Parameters ................................................................... 26.2-3
Name ....................................................................................................... 26.2-3
Signalling channel administrative status .................................................. 26.2-3
Signalling channel operational status ...................................................... 26.2-3
Associated signalling profile attribute ....................................................... 26.2-3
Prefix passing or stripping ........................................................................ 26.2-4
To set the signalling channel parameters ................................................ 26.2-5
(400)
Table of Contents

NNP 95-2035-01-00-B
26.2.4
26.3
Signalling Profiles ........................................................................................ 26.2-5

Profile name ............................................................................................. 26.2-5
Signalling protocol attribute ...................................................................... 26.2-5
To set the profile name and its protocol ................................................... 26.2-6
Network layer protocol timers .................................................................. 26.2-6
To set the network layer timers ................................................................ 26.2-6
Q.922 link layer protocol parameters ....................................................... 26.2-7
To set the link layer timers and counters ................................................. 26.2-7
SVC User Management

26.3.1
26.3.2
26.3.3
26.3.4
26.4
Table of Contents
Understanding User Management ............................................................... 26.3-1

Switch Address Prefix Management ............................................................ 26.3-1
Absolute and relative addresses .............................................................. 26.3-1
Prefix types .............................................................................................. 26.3-2
To assign and view the prefix value ......................................................... 26.3-2
User Configuration ....................................................................................... 26.3-2
Name ....................................................................................................... 26.3-2
User address ............................................................................................ 26.3-3
Physical access (frame stream) ............................................................... 26.3-3
Default user .............................................................................................. 26.3-3
User administrative status ........................................................................ 26.3-3
User operational status ............................................................................ 26.3-3
To view one or all user configurations ..................................................... 26.3-4
To set the user configuration parameters ................................................ 26.3-5
User Screening ............................................................................................ 26.3-5
SVC Connection Management

26.4.1
26.4.2
26.4.3
26.4.4
Table of Contents
Understanding Connection Management .................................................... 26.4-1

Allocation of Signalling Identifiers ................................................................ 26.4-3
DLCI allocation ......................................................................................... 26.4-3
Call reference allocation .......................................................................... 26.4-4
Call identification allocation ...................................................................... 26.4-4
To allocate the signalling identifiers ......................................................... 26.4-4
CIR and Booking Factor .............................................................................. 26.4-4
CIR ........................................................................................................... 26.4-4
Booking factor .......................................................................................... 26.4-4
To set CIR and the booking factor ........................................................... 26.4-5
Connection Admission Control .................................................................... 26.4-5
Class-of-service guarantee ...................................................................... 26.4-5
To set the COS guarantee ....................................................................... 26.4-6
(400)
xli
Table of Contents
26.5

NNP 95-2035-01-00-B
SVC Routing
26.5.1
26.5.2
26.5.3
26.5.4
Understanding SVC Routing ........................................................................ 26.5-1

Remote Address Table ................................................................................ 26.5-2
To create or change a remote address table ........................................... 26.5-4
Route Selection for a Call Setup .................................................................. 26.5-4
Route Failure Handling ................................................................................ 26.5-4
Crankback ................................................................................................ 26.5-5
Alternate path routing ............................................................................... 26.5-5
Call clearing ............................................................................................. 26.5-6
27. X.25 Service

27.1
Understanding the 36120 MainStreet X.25 Service

27.1.1
27.1.2
27.1.3
27.1.4
27.2
Internal Network Operation

27.2.1
27.2.2
27.2.3
xlii
X.25 Protocol Overview ............................................................................... 27.1-1

36120 MainStreet X.25 Overview ................................................................ 27.1-1
36120 MainStreet X.25 basic functional components .............................. 27.1-2
36120 MainStreet X.25 terminology ......................................................... 27.1-2
36120 MainStreet X.25 Protocol Subsystems ............................................. 27.1-3
Link layer .................................................................................................. 27.1-3
Network layer ........................................................................................... 27.1-3
Reliable Transfer Protocol ....................................................................... 27.1-4
Generic Frame Router ............................................................................. 27.1-4
End-to-end function of the protocol subsystems ...................................... 27.1-4
User Access to the Network ........................................................................ 27.1-5
Direct X.25 access ................................................................................... 27.1-5
Encapsulated access over frame relay .................................................... 27.1-6
Encapsulated access for basic rate and super-rate devices .................... 27.1-6
Encapsulated access for subrate devices ................................................ 27.1-7
Internal Network Architecture ...................................................................... 27.2-1

Understanding the Reliable Transfer Protocol ............................................. 27.2-3
Implementation of Q.2110 functions in the RTP ...................................... 27.2-3
RTP virtual connections ........................................................................... 27.2-4
Congestion management ......................................................................... 27.2-7
GFR load balancing support .................................................................... 27.2-9
Packet Segmenting and Combining .......................................................... 27.2-10
Restrictions for packet segmenting and combining ............................... 27.2-10
Tables 6-1 and 6-2 of Recommendation X.25 ....................................... 27.2-11
Conditions for packet segmenting and combining ................................. 27.2-11
No flow control negotiation subscription at the calling and
called DTEs .................................................................................... 27.2-13
Flow control negotiation subscription only at the calling DTE ................ 27.2-14
Flow control negotiation subscription only at the called DTE ................. 27.2-17
Flow control negotiation subscription at called DTEs ............................ 27.2-18
(400)
Table of Contents

NNP 95-2035-01-00-B
27.3
Standards Compliance
27.3.1
27.3.2
27.3.3
27.4
27.4.2
27.4.3
27.4.4
Understanding X.25 Configuration ............................................................... 27.4-1

Node management terminal interface ...................................................... 27.4-1
Using the node management interfaces .................................................. 27.4-2
Understanding Identifiers and Entering Data ............................................... 27.4-3
How to Use Configuration Information ......................................................... 27.4-4
Summary of X.25 Configurable Parameters ................................................ 27.4-6
X.25 Switch-wide Parameters

27.5.1
27.5.2
27.5.3
27.6
36120 MainStreet X.25 Compliance to ITU-T Recommendation X.2

(1988) ................................................................................................. 27.3-1
(1992) ................................................................................................. 27.3-3
(1993) ................................................................................................. 27.3-5
Compliance to sections 0 and 1 ............................................................... 27.3-6
Conformance ........................................................................................... 27.3-6
X.25 Configuration Overview

27.4.1
27.5
Table of Contents
Understanding X.25 Switch-wide Parameters ............................................. 27.5-1

Global switch resources ........................................................................... 27.5-1
Viewing X.25 Switch-wide Parameters ........................................................ 27.5-1
Viewing global switch resources .............................................................. 27.5-2
To view X.25 switch-wide parameters ..................................................... 27.5-4
To view global switch resources .............................................................. 27.5-4
Configuring the X.25 Switch-wide Parameters ............................................ 27.5-4
Number of XACs ...................................................................................... 27.5-4
Number of Trunk Circuits ......................................................................... 27.5-5
Restrictions and interdependencies ......................................................... 27.5-5
Change impact and activation .................................................................. 27.5-5
To configure the X.25 switch-wide parameters ........................................ 27.5-5
GFR Configuration
27.6.1
27.6.2
Table of Contents
Understanding Network Topologies ............................................................. 27.6-1

Network routing domains ......................................................................... 27.6-1
GFR routing concepts .............................................................................. 27.6-5
Hub domain dynamic routing ................................................................... 27.6-6
GFR addresses ........................................................................................ 27.6-7
Aliases ..................................................................................................... 27.6-7
Load balancing ......................................................................................... 27.6-8
Automatic FASTbus trunks ...................................................................... 27.6-9
Understanding the Generic Frame Router ................................................... 27.6-9
Route builder ............................................................................................ 27.6-9
Forwarding function ............................................................................... 27.6-10
Frame relay encapsulation ..................................................................... 27.6-10
How the GFR routes frames .................................................................. 27.6-12
Forwarding principles ............................................................................. 27.6-13
Redundant routing ................................................................................. 27.6-15
How the switch handles trunk failures .................................................... 27.6-16
(400)
xliii
Table of Contents
27.6.3
27.6.4
27.7
Viewing the GFR Parameters .................................................................... 27.6-17

To view GFR parameters ....................................................................... 27.6-17
Configuring the GFR Parameters .............................................................. 27.6-17
GFR address .......................................................................................... 27.6-17
Redundant routing ................................................................................. 27.6-18
Load balancing ....................................................................................... 27.6-19
Hub domain dynamic routing ................................................................. 27.6-19
Delta value ............................................................................................. 27.6-20
List of aliases ......................................................................................... 27.6-20
GFR transit cost ..................................................................................... 27.6-21
Rate enforcement state .......................................................................... 27.6-21
Aggregate committed information rate ................................................... 27.6-21
Aggregate committed burst size ............................................................ 27.6-21
Restrictions and limitations .................................................................... 27.6-22
Change impact and activation ................................................................ 27.6-22
To configure the GFR parameters ......................................................... 27.6-23
Call Routing
27.7.1
27.7.2
27.7.3
27.7.4
27.7.5
xliv

NNP 95-2035-01-00-B
Understanding Call Routing ......................................................................... 27.7-1

Global Address Table .............................................................................. 27.7-1
Link status updates .................................................................................. 27.7-8
Local Address Table ................................................................................ 27.7-9
Basic Routing ............................................................................................. 27.7-10
How basic routing occurs in a virtual call setup ..................................... 27.7-12
Gateway Routing ....................................................................................... 27.7-16
Network-wide hunt groups ..................................................................... 27.7-16
Gateway routing examples .................................................................... 27.7-16
Gateway routing process ....................................................................... 27.7-19
How gateway routing occurs in a virtual call setup ................................ 27.7-21
Viewing Call Routing Tables ...................................................................... 27.7-25
To view the GAT .................................................................................... 27.7-25
To view the LAT ..................................................................................... 27.7-26
Configuring the GAT .................................................................................. 27.7-26
Address prefix ........................................................................................ 27.7-26
GFR address .......................................................................................... 27.7-27
XAC ........................................................................................................ 27.7-27
Type ....................................................................................................... 27.7-27
Priority .................................................................................................... 27.7-28
Weight .................................................................................................... 27.7-28
Restrictions and interdependencies ....................................................... 27.7-29
To configure the GAT ............................................................................. 27.7-30
(400)
Table of Contents

NNP 95-2035-01-00-B
27.8
Trunk Circuits
27.8.1
27.8.2
27.8.3
27.8.4
27.8.5
27.9
Table of Contents
Understanding Backbone Trunks ................................................................ 27.8-1

Trunk circuits ............................................................................................ 27.8-1
Packet size considerations ...................................................................... 27.8-1
Viewing Trunk Circuit Configuration Information ......................................... 27.8-2
To view trunk circuit configuration information ......................................... 27.8-3
Configuring Trunk Circuits ........................................................................... 27.8-3
Cost .......................................................................................................... 27.8-3
Poll Timer ................................................................................................. 27.8-4
To configure trunk circuits ........................................................................ 27.8-5
Connecting Trunk Circuits ........................................................................... 27.8-5
To connect trunk circuits to frame stream-DLCIs ..................................... 27.8-5
To connect trunk circuits to FASTbus circuit-DLCIs ................................ 27.8-6
Provisioning Backbone Trunks .................................................................... 27.8-6
To provision backbone trunks over primary rate links .............................. 27.8-7
To provision backbone trunks over the FASTbus .................................... 27.8-8
NUI Validation Subsystem

27.9.1
27.9.2
27.9.3
27.9.4
Table of Contents
Understanding NUIs .................................................................................... 27.9-1

NUI validation servers .............................................................................. 27.9-1
NUI subscription ....................................................................................... 27.9-2
NUI override ............................................................................................. 27.9-2
How the switch handles NUIs .................................................................. 27.9-3
NUI formats .............................................................................................. 27.9-4
Understanding the NUI Validation Subsystem ............................................. 27.9-6
NUI server agent and XAC ...................................................................... 27.9-6
XACs for the validation servers ................................................................ 27.9-7
CUG considerations ................................................................................. 27.9-8
Viewing the NUI Server Agent Parameters ................................................. 27.9-9
To view NUI server agent parameters ..................................................... 27.9-9
Configuring the NUI Server Agent Parameters .......................................... 27.9-10
Primary NUI Server Address .................................................................. 27.9-10
Secondary NUI Server Address ............................................................. 27.9-10
Maximum Allowed Validation Period ...................................................... 27.9-11
To configure the NUI server agent parameters ...................................... 27.9-12
To configure a NUI agent XAC .............................................................. 27.9-12
(400)
xlv
Table of Contents

NNP 95-2035-01-00-B
27.10 Accounting Generation Subsystem

27.10.1
27.10.2
27.10.3
27.10.4
Understanding Virtual Circuit Accounting .................................................. 27.10-1

Accounting segments ............................................................................. 27.10-2
Collection intervals ................................................................................. 27.10-3
Accounting records ................................................................................ 27.10-3
Paced generation of accounting records ............................................... 27.10-9
Accounting record storage in NVM ...................................................... 27.10-10
Transfer of accounting records to the data collector ............................ 27.10-10
Understanding Accounting Generation Parameters ................................ 27.10-15
Viewing the Accounting Generation Parameters ..................................... 27.10-17
To view accounting generation parameters ......................................... 27.10-17
Configuring the Accounting Generation Parameters ............................... 27.10-17
Generate Accounting Records ............................................................. 27.10-18
Generate Accounting Records on Unsuccessful Calls ........................ 27.10-18
Accounting Segment Size .................................................................... 27.10-19
Collection Interval ................................................................................ 27.10-20
Intermediate Record Interval ................................................................ 27.10-20
Periodic Record Interval ....................................................................... 27.10-21
Optional User Defined Data Length ..................................................... 27.10-21
Time Zone ............................................................................................ 27.10-22
Accounting NVM Buffer Size ................................................................ 27.10-22
Restrictions and interdependencies ..................................................... 27.10-22
Change impact and activation .............................................................. 27.10-23
To configure the accounting generation parameters ........................... 27.10-23
27.11 Data Collector Agent Subsystem

27.11.1
27.11.2
27.11.3
27.11.4
xlvi
Understanding the Data Collector Agent ................................................... 27.11-1

Accounting generation subsystem ......................................................... 27.11-1
Data collector agent ............................................................................... 27.11-1
Data collector agent XAC ....................................................................... 27.11-1
Data collector interface XACs ................................................................ 27.11-2
Data collector ......................................................................................... 27.11-3
GDI protocol ........................................................................................... 27.11-3
Data Collector Agent Parameters .............................................................. 27.11-4
Viewing the Data Collector Agent Parameters .......................................... 27.11-5
To view data collector agent parameters ............................................... 27.11-5
Configuring the Data Collector Agent Parameters ..................................... 27.11-5
Primary Data Collector Address ............................................................. 27.11-5
Secondary Data Collector Address ........................................................ 27.11-6
Transfer Block Size ................................................................................ 27.11-6
Maximum Time Between Transfers ....................................................... 27.11-7
Transfer Block Retransmission Timer .................................................... 27.11-7
Transfer Block Retransmission Count ................................................... 27.11-7
To configure the data collector agent parameters ................................. 27.11-8
To configure a data collector agent XAC ............................................... 27.11-9
(400)
Table of Contents

NNP 95-2035-01-00-B
Table of Contents
27.12 Accounting Subsystem Configuration

27.12.1
27.13 Circuits for X.25 Access Lines

27.13.1
27.13.2
27.13.3
27.13.4
27.13.5
27.13.6
27.13.7
27.13.8
27.13.9
Table of Contents
Understanding X.25 Access Methods ........................................................ 27.13-1

Direct LAPB access ............................................................................... 27.13-1
Encapsulated access over frame relay .................................................. 27.13-2
LAPB Annex G encapsulation ................................................................ 27.13-2
LAPB RFC 1490 encapsulation ............................................................. 27.13-3
Frame relay encapsulation on the X.25 switch ...................................... 27.13-4
Frame relay encapsulation on the FRS card ......................................... 27.13-6
Configuring Direct Circuits ......................................................................... 27.13-7
To configure direct circuits ..................................................................... 27.13-8
Configuring Frame Relay Encapsulation Circuits ...................................... 27.13-8
To create frame relay encapsulation circuits ......................................... 27.13-8
To create subrate frame relay encapsulation circuits ............................ 27.13-9
Configuring the parameters for encapsulation circuits ........................... 27.13-9
Encapsulation circuit congestion thresholds ........................................ 27.13-11
Encapsulated Protocol Maximum Frame Size ..................................... 27.13-11
Encapsulation type ............................................................................... 27.13-11
To configure encapsulation circuit parameters .................................... 27.13-14
Viewing FRS circuit information ........................................................... 27.13-14
Configuring the Parameters for Frame Stream Circuits ........................... 27.13-15
Maximum frame size ............................................................................ 27.13-15
Congestion thresholds ......................................................................... 27.13-15
Link protocol type ................................................................................. 27.13-16
Configuring Connections for X.25 Access Lines ...................................... 27.13-16
Connecting Direct Circuits ....................................................................... 27.13-17
To connect direct circuits ..................................................................... 27.13-17
Connecting Encapsulation Circuits .......................................................... 27.13-17
Super-rate encapsulation circuits ......................................................... 27.13-18
To connect super-rate encapsulation circuits ...................................... 27.13-18
Subrate encapsulation circuits ............................................................. 27.13-19
To connect subrate encapsulation circuits ........................................... 27.13-20
Connecting XACs .................................................................................... 27.13-21
To connect XACs to direct circuits ....................................................... 27.13-21
To connect XACs to frame stream-DLCIs or
FASTbus station-DLCIs ............................................................... 27.13-21
Configuring Class-of-service Parameters for Encapsulated Access ....... 27.13-22
Non-statistical multiplexing approach .................................................. 27.13-22
Statistical multiplexing approach .......................................................... 27.13-22
(400)
xlvii
Table of Contents

NNP 95-2035-01-00-B
27.14 XAC Parameters

27.14.1
27.14.2
27.14.3
27.14.4
27.14.5
27.14.6
27.14.7
xlviii
Understanding XACs ................................................................................. 27.14-1

Configuration overview .............................................................................. 27.14-1
Understanding Link Layer Parameters ...................................................... 27.14-2
Viewing Link Layer Parameters ................................................................. 27.14-2
To view link layer parameters ................................................................ 27.14-3
Configuring Link Layer Parameters ........................................................... 27.14-3
Link Layer Interface Type ...................................................................... 27.14-3
Frame Sequence Numbering ................................................................. 27.14-4
Maximum Frame Window Size .............................................................. 27.14-4
Retransmission Count (N2) .................................................................... 27.14-4
Frame Response Timer (T1) .................................................................. 27.14-4
Response Delay Timer (T2) ................................................................... 27.14-5
Inactivity Timer (T3) ............................................................................... 27.14-5
Congestion Timer ................................................................................... 27.14-6
Maximum Information Frame Size ......................................................... 27.14-6
To configure link layer parameters ......................................................... 27.14-7
Understanding Network Layer Parameters ................................................ 27.14-7
Packet sequence numbering ................................................................. 27.14-8
Virtual circuits and logical channels ....................................................... 27.14-8
Network layer timers ............................................................................ 27.14-10
Negotiation facilities ............................................................................. 27.14-11
Addressing options .............................................................................. 27.14-11
Maximum packet size .......................................................................... 27.14-12
To ensure packet and frame size compatibility .................................... 27.14-12
Viewing Network Layer Parameters ........................................................ 27.14-13
To view network layer parameters ....................................................... 27.14-13
(400)
Table of Contents

NNP 95-2035-01-00-B
Table of Contents
27.14.8
Configuring Network Layer Parameters ................................................... 27.14-13

Service Type ........................................................................................ 27.14-14
Packet Layer Interface Type ................................................................ 27.14-14
X.25 Version ........................................................................................ 27.14-14
Packet Sequence Numbering .............................................................. 27.14-15
Base LCN ............................................................................................. 27.14-15
Number of LCNs .................................................................................. 27.14-15
Number of PVCs .................................................................................. 27.14-16
Number of Outgoing SVCs .................................................................. 27.14-16
Two-way SVCs .................................................................................... 27.14-17
Number of Incoming SVCs .................................................................. 27.14-17
Packet Layer Restart Timer (T10/T20) ................................................ 27.14-18
Packet Layer Call Timer (T11/T21) ...................................................... 27.14-18
Reset Timer (T12/T22) ......................................................................... 27.14-18
Clear Timer (T13/T23) ......................................................................... 27.14-18
Window Timer (T24) ............................................................................ 27.14-19
Inactivity Timer ..................................................................................... 27.14-19
Flow Control Timer ............................................................................... 27.14-20
Incoming Maximum Address Length Allowed ...................................... 27.14-20
Suppress Called Address .................................................................... 27.14-21
Suppress Calling Address .................................................................... 27.14-21
Local Address Validation ..................................................................... 27.14-22
Default NPI ........................................................................................... 27.14-22
Address Translation Table Entry .......................................................... 27.14-23
Allowable Packet Sizes ........................................................................ 27.14-23
Flow Control Negotiation ...................................................................... 27.14-23
Throughput Class Negotiation ............................................................. 27.14-24
Throughput Class Negotiation Format ................................................. 27.14-24
Generate Cause Codes in DTE Format ............................................... 27.14-24
Enhanced Diagnostics Codes .............................................................. 27.14-25
Generate Alarms .................................................................................. 27.14-25
To configure network layer parameters ............................................... 27.14-28
27.14.9 Understanding Address Translation and Screening Parameters ............. 27.14-29
How addressing works in a 36120 MainStreet X.25 network ............... 27.14-29
Address translation .............................................................................. 27.14-30
Wildcard characters ............................................................................. 27.14-35
Call screening ...................................................................................... 27.14-36
27.14.10 Viewing Address Translation and Screening Parameters ...................... 27.14-36
To view the address translation table .................................................. 27.14-37
To view address translation and screening parameters ...................... 27.14-37
Table of Contents
(400)
xlix
Table of Contents
27.14.11
27.14.12

NNP 95-2035-01-00-B
Configuring Address Translation and Screening Parameters ................. 27.14-37

Entry Number ....................................................................................... 27.14-38
External Translation Prefix ................................................................... 27.14-38
Internal Translation Prefix .................................................................... 27.14-38
Direction ............................................................................................... 27.14-39
Which Address ..................................................................................... 27.14-39
Trap Incoming Calling .......................................................................... 27.14-40
Trap Incoming Called ........................................................................... 27.14-40
Trap Outgoing Calling .......................................................................... 27.14-40
Trap Outgoing Called ........................................................................... 27.14-41
Trap Action Clear Call .......................................................................... 27.14-41
Trap Action Cause Alarm ..................................................................... 27.14-41
To configure address translation and screening parameters ............... 27.14-44
Resetting XACs ...................................................................................... 27.14-44
To reset an XAC .................................................................................. 27.14-44
27.15 NUA Parameters

27.15.1
27.15.2
27.15.3
27.15.4
27.15.5
27.15.6
Understanding NUAs ................................................................................. 27.15-1

Viewing Basic NUA Parameters ................................................................ 27.15-2
To view basic NUA parameters ............................................................. 27.15-3
Configuring Basic NUA Parameters .......................................................... 27.15-3
Network User Address ........................................................................... 27.15-3
Allocated XAC Number .......................................................................... 27.15-3
User Defined Data ................................................................................. 27.15-4
Accounting Activation ............................................................................. 27.15-4
Periodic Accounting Activation ............................................................... 27.15-5
Hot Billing ............................................................................................... 27.15-5
To define basic NUA parameters ........................................................... 27.15-6
Understanding NUA Subscription Options ................................................. 27.15-7
Charging facilities ................................................................................... 27.15-7
Fast Select and Fast Select Acceptance facilities ................................. 27.15-7
Call Redirection facility ........................................................................... 27.15-8
Viewing NUA Subscription Options ........................................................... 27.15-9
To view NUA subscription options ....................................................... 27.15-10
(400)
Table of Contents

NNP 95-2035-01-00-B
27.15.7
27.15.8
27.15.9
27.15.10
27.15.11
27.15.12
27.15.13
Table of Contents
Table of Contents
Configuring NUA Subscription Options .................................................... 27.15-10

Reverse Charge Acceptance ............................................................... 27.15-10
Local Charge Prevention ..................................................................... 27.15-11
Charging Information Subscription ....................................................... 27.15-11
Charging Information Request Allowed ............................................... 27.15-11
Incoming Fast Select Acceptance ........................................................ 27.15-12
Outgoing Restricted Fast Select Allowed ............................................. 27.15-12
Outgoing Unrestricted Fast Select Allowed ......................................... 27.15-12
Default NUA ......................................................................................... 27.15-13
TOA/NPI Address Format .................................................................... 27.15-13
Clear on Calling Address Failure ......................................................... 27.15-14
Redirection Address ............................................................................. 27.15-14
Signal CRN .......................................................................................... 27.15-14
Signal CLAMN ..................................................................................... 27.15-15
Call Deflection ...................................................................................... 27.15-15
NUI Subscription .................................................................................. 27.15-15
NUI Validation Required ...................................................................... 27.15-16
Default NUI Format .............................................................................. 27.15-16
Non-standard NUI Coding Method ....................................................... 27.15-17
Non-standard NUI First Subfield .......................................................... 27.15-17
Non-standard NUI First Subfield Length .............................................. 27.15-17
To configure NUA subscription options ................................................ 27.15-19
Understanding CUGs ............................................................................... 27.15-20
Viewing CUG Parameters ........................................................................ 27.15-21
To view CUG parameters .................................................................... 27.15-22
Configuring CUGs ................................................................................... 27.15-22
CUG Index ........................................................................................... 27.15-22
Interlock Code ...................................................................................... 27.15-22
Barring ................................................................................................. 27.15-23
Preferential CUG .................................................................................. 27.15-23
CUG with Incoming Access ................................................................. 27.15-24
CUG with Outgoing Access ................................................................. 27.15-24
Signal Preferential CUG ....................................................................... 27.15-24
To configure CUGs .............................................................................. 27.15-25
Understanding Flow Control and Throughput Class Parameters ............ 27.15-26
Viewing Flow Control and Throughput Class Parameters ...................... 27.15-26
To view flow control and throughput class parameters ........................ 27.15-27
Configuring Flow Control and Throughput Class Parameters ................ 27.15-27
Default Receive Packet Size ................................................................ 27.15-27
Default Send Packet Size .................................................................... 27.15-27
Default Receive Window Size .............................................................. 27.15-28
Default Send Window Size .................................................................. 27.15-28
Default Receive Throughput Class ...................................................... 27.15-28
Default Send Throughput Class ........................................................... 27.15-29
To configure flow control and throughput class parameters ................ 27.15-30
(400)
li
Table of Contents

NNP 95-2035-01-00-B
27.16 Copying XAC Configurations

27.16.1
27.16.2
Understanding the Copy Capability ........................................................... 27.16-1

Using the Copy Capability ......................................................................... 27.16-1
To use the COPY command .................................................................. 27.16-3
27.17 X.25 PVCs

27.17.1
27.17.2
27.17.3
Understanding X.25 PVCs ......................................................................... 27.17-1

How the network establishes PVCs ....................................................... 27.17-1
Packet size dependencies ..................................................................... 27.17-2
Packet sequence numbering ................................................................. 27.17-2
Viewing X.25 PVCs .................................................................................... 27.17-3
Viewing all PVCs or a group of PVCs .................................................... 27.17-3
To view all PVCs or a group of PVCs .................................................... 27.17-4
Viewing PVC parameters ....................................................................... 27.17-4
To view X.25 PVC parameters ............................................................... 27.17-5
Configuring X.25 PVCs .............................................................................. 27.17-5
To prepare XACs for PVCs .................................................................... 27.17-5
Local Address ........................................................................................ 27.17-6
Local LCN .............................................................................................. 27.17-6
Remote Address .................................................................................... 27.17-7
Remote LCN .......................................................................................... 27.17-7
Accounting Activation ............................................................................. 27.17-7
Periodic Accounting Activation ............................................................... 27.17-8
D-Bit Allowed ......................................................................................... 27.17-8
Local Send Packet Size ......................................................................... 27.17-8
Local Receive Packet Size .................................................................... 27.17-9
Remote Send Packet Size ..................................................................... 27.17-9
Remote Receive Packet Size .............................................................. 27.17-10
Send Window Size ............................................................................... 27.17-10
Receive Window Size .......................................................................... 27.17-10
Send Throughput Class ....................................................................... 27.17-11
Receive Throughput Class ................................................................... 27.17-11
Originating End .................................................................................... 27.17-12
To configure the X.25 PVC parameters ............................................... 27.17-13
To delete X.25 PVCs ........................................................................... 27.17-14
27.18 Hunt Groups

27.18.1
27.18.2
lii
Understanding Hunt Groups ...................................................................... 27.18-1

Switch-wide hunt groups ........................................................................ 27.18-1
Network-wide hunt groups ..................................................................... 27.18-2
Hunt group addresses ............................................................................ 27.18-2
Redirection addresses ........................................................................... 27.18-2
Viewing Hunt Group Information ................................................................ 27.18-3
To view hunt group information .............................................................. 27.18-4
(400)
Table of Contents

NNP 95-2035-01-00-B
27.18.3
Table of Contents
Configuring Hunt Groups ........................................................................... 27.18-4

Hunt group configuration overview ........................................................ 27.18-4
Hunt Group Address .............................................................................. 27.18-5
Redirection Address ............................................................................... 27.18-5
Hunt Group Member NUA ...................................................................... 27.18-5
To add and delete hunt group addresses .............................................. 27.18-6
To add and delete hunt group members ................................................ 27.18-7
27.19 Provisioning X.25 User Access

27.19.1
27.19.2
Direct X.25 Access .................................................................................... 27.19-1

To provision direct access lines ............................................................. 27.19-1
Encapsulated Access ................................................................................ 27.19-3
To provision encapsulated access to the X.25 switch ........................... 27.19-3
To provision subrate encapsulated access to the X.25 switch .............. 27.19-6
27.20 X.25 to Frame Relay Service Interworking

27.20.1
27.20.2
27.20.3
27.20.4
27.20.5
27.20.6
Table of Contents
Understanding the X.25 to frame relay service interworking ..................... 27.20-1

Service interworking ............................................................................... 27.20-1
Network interworking ............................................................................. 27.20-2
End-to-end protocol stack ...................................................................... 27.20-3
Frame loss ............................................................................................. 27.20-3
X.25 to Frame Relay Service Interworking Components ........................... 27.20-4
X.25 to frame relay service interworking XAC ....................................... 27.20-4
Frame relay permanent virtual circuit connection .................................. 27.20-4
X.25 virtual circuits ................................................................................. 27.20-4
Call Management ....................................................................................... 27.20-5
Call setup ............................................................................................... 27.20-5
Call routing ............................................................................................. 27.20-6
Data transfer .......................................................................................... 27.20-6
Connection management ....................................................................... 27.20-7
Link Management Interface ................................................................... 27.20-7
Flow control ............................................................................................ 27.20-8
Congestion level monitoring ................................................................... 27.20-8
Accounting ............................................................................................. 27.20-9
X.25 to frame relay service interworking features .................................. 27.20-9
X.25 to frame relay service interworking restrictions ........................... 27.20-10
X.25 to Frame Relay Service Interworking Parameters ........................... 27.20-10
Mild congestion threshold .................................................................... 27.20-10
Severe congestion threshold ............................................................... 27.20-10
Absolute congestion threshold (ACT) .................................................. 27.20-11
Frame relay reconnect timer ................................................................ 27.20-11
Viewing service interworking parameters ............................................ 27.20-11
To view service interworking parameters ............................................. 27.20-12
Network User Address Parameters ......................................................... 27.20-12
To view NUA parameters ..................................................................... 27.20-13
Configuring X.25 to frame relay service interworking .............................. 27.20-14
To configure X.25 to frame relay service interworking ......................... 27.20-14
(400)
liii
Table of Contents

NNP 95-2035-01-00-B
28. X.75 Gateway Service

28.1
Understanding the X.75 Gateway Service

28.1.1
28.1.2
28.1.3
28.1.4
28.1.5
28.1.6
28.1.7
28.1.8
28.1.9
28.1.10
28.2
X.75 XAC Parameters

28.2.1
28.2.2
28.2.3
28.2.4
liv
Overview of the X.75 Gateway Service ....................................................... 28.1-1

Understanding X.75 ..................................................................................... 28.1-1
X.75 Utilities ................................................................................................. 28.1-2
Call identifier ............................................................................................ 28.1-2
Throughput class indication ..................................................................... 28.1-2
Window size indication ............................................................................. 28.1-3
Packet size indication .............................................................................. 28.1-3
Fast select indication ............................................................................... 28.1-4
Reverse charge indication ....................................................................... 28.1-4
Called line address modification notification ............................................ 28.1-4
Transit network identification code ........................................................... 28.1-5
Clearing network identification code ........................................................ 28.1-5
Internetwork closed user group indication ............................................... 28.1-5
Internetwork closed user group with outgoing access indication ............. 28.1-5
X.75 Gateway Call Routing .......................................................................... 28.1-5
IPVCs ........................................................................................................... 28.1-6
Internetwork Closed User Groups ............................................................... 28.1-6
Mode of operation .................................................................................... 28.1-6
ICUG mapping tables ............................................................................... 28.1-7
X.75 Accounting ........................................................................................... 28.1-8
Diagnostic Code Mapping ............................................................................ 28.1-9
X.75 Gateway Service Configuration Overview ......................................... 28.1-10
Summary of X.75 Configurable Parameters .............................................. 28.1-11
X.75 Access Circuit Configuration Overview ............................................... 28.2-1

X.75 Link Layer Parameters ........................................................................ 28.2-1
To view X.75 link layer parameters .......................................................... 28.2-2
Configuring X.75 Link Layer Parameters ..................................................... 28.2-2
LAPB Address Assignment ...................................................................... 28.2-2
Frame Sequence Numbering ................................................................... 28.2-3
Maximum Frame Window Size ................................................................ 28.2-3
Retransmission Count (N2) ...................................................................... 28.2-3
Frame Response Timer (T1) .................................................................... 28.2-4
Response Delay Timer (T2) ..................................................................... 28.2-4
Inactivity Timer (T3) ................................................................................. 28.2-4
Congestion Timer ..................................................................................... 28.2-5
Maximum Information Frame Size (N1) ................................................... 28.2-5
To configure X.75 link layer parameters .................................................. 28.2-6
X.75 Network Layer Parameters .................................................................. 28.2-7
To view X.75 network layer parameters ................................................... 28.2-8
(400)
Table of Contents

NNP 95-2035-01-00-B
28.2.5
28.2.6
Table of Contents
Table of Contents
Configuring X.75 Network Layer Parameters .............................................. 28.2-8

Service Type ............................................................................................ 28.2-8
X.75 Logical Channel Number Selection ................................................. 28.2-9
Version ..................................................................................................... 28.2-9
Packet Sequence Numbering .................................................................. 28.2-9
Base LCN ............................................................................................... 28.2-10
Number of LCNs .................................................................................... 28.2-10
Number of PVCs .................................................................................... 28.2-10
Number of Outgoing SVCs .................................................................... 28.2-11
Two-way SVCs ...................................................................................... 28.2-11
Number of Incoming SVCs .................................................................... 28.2-12
Restart Timer (T30) ................................................................................ 28.2-12
Call Request Timer (T31) ....................................................................... 28.2-13
Reset Timer (T32) .................................................................................. 28.2-13
Clear Timer (T33) ................................................................................... 28.2-13
Window Timer (T24) .............................................................................. 28.2-14
Inactivity Timer ....................................................................................... 28.2-14
Flow Control Timer ................................................................................. 28.2-15
Incoming Maximum Address Length Allowed ........................................ 28.2-15
Default NPI ............................................................................................. 28.2-16
Allowable Packet Sizes .......................................................................... 28.2-16
Incoming Transit Calls Allowed .............................................................. 28.2-17
Throughput Class Negotiation Format ................................................... 28.2-17
Diagnostic Code Mapping ...................................................................... 28.2-17
Generate Alarms .................................................................................... 28.2-18
Status Monitoring ................................................................................... 28.2-18
Gateway TNIC/CNIC .............................................................................. 28.2-18
Insert TNIC ............................................................................................. 28.2-19
Signal TNIC ............................................................................................ 28.2-19
Signal CNIC ........................................................................................... 28.2-19
To configure X.75 network layer parameters ......................................... 28.2-22
Configuring X.75 Address Translation Parameters ................................... 28.2-23
External Translation Prefix ..................................................................... 28.2-23
Internal Translation Prefix ...................................................................... 28.2-23
Translate Calling Address ...................................................................... 28.2-24
Translate Called Address ....................................................................... 28.2-24
Translate Incoming Packets ................................................................... 28.2-24
Translate Outgoing Packets ................................................................... 28.2-25
Trap Incoming Calling ............................................................................ 28.2-25
Trap Incoming Called ............................................................................. 28.2-25
Trap Outgoing Calling ............................................................................ 28.2-26
Trap Outgoing Called ............................................................................. 28.2-26
Trap Action: Clear Call ........................................................................... 28.2-26
To configure X.75 address translation parameters ................................ 28.2-27
(400)
lv
Table of Contents
28.3

NNP 95-2035-01-00-B
X.75 NUA Parameters

28.3.1
28.3.2
28.3.3
Understanding NUAs ................................................................................... 28.3-1

Viewing X.75 NUA Parameters .................................................................... 28.3-1
To view X.75 NUA parameters ................................................................ 28.3-2
Configuring X.75 NUA Parameters .............................................................. 28.3-2
Network User Address ............................................................................. 28.3-2
Allocated XAC Number ............................................................................ 28.3-2
Accounting Activation ............................................................................... 28.3-3
Signal CLAMN ......................................................................................... 28.3-3
Signal CRN .............................................................................................. 28.3-4
Reverse Charge Acceptance ................................................................... 28.3-4
Default Receive Window Size .................................................................. 28.3-4
Default Send Window Size ...................................................................... 28.3-5
Default Receive Throughput Class .......................................................... 28.3-5
Default Send Throughput Class ............................................................... 28.3-5
Default Receive Packet Size .................................................................... 28.3-6
Default Send Packet Size ........................................................................ 28.3-6
Outgoing Fast Select Allowed .................................................................. 28.3-6
Incoming Restricted Fast Select Allowed ................................................. 28.3-7
Incoming Unrestricted Fast Select Allowed ............................................. 28.3-7
TOA/NPI Address Format ........................................................................ 28.3-7
Clear On Calling Address Failure ............................................................ 28.3-8
Periodic Accounting Activation ................................................................. 28.3-8
To configure X.75 NUA parameters ....................................................... 28.3-10
29. BRI S/T Cards

29.1
Understanding BRI S/T Card Configuration

29.1.1
29.1.2
29.2
BRI S/T Card Slots

29.2.1
29.2.2
lvi
Understanding BRI S/T Cards ..................................................................... 29.1-1

ISDN basics ............................................................................................. 29.1-1
ISDN application ..................................................................................... 29.1-2
BRI S/T cards ........................................................................................... 29.1-2
Applications .............................................................................................. 29.1-2
Configuring BRI S/T Cards .......................................................................... 29.1-3
Understanding BRI S/T Card Slots .............................................................. 29.2-1

Configuring BRI S/T Card Slots ................................................................... 29.2-1
To configure BRI S/T card slots ............................................................... 29.2-1
(400)
Table of Contents

NNP 95-2035-01-00-B
29.3
Non-ISDN Applications
29.3.1
29.3.2
29.3.3
29.3.4
29.4
Table of Contents
Understanding Non-ISDN Applications ........................................................ 29.3-1

Leased lines ............................................................................................. 29.3-1
ISDN loop extension ................................................................................ 29.3-3
Configuring BRI S/T Interfaces in a Non-ISDN Application ......................... 29.3-4
Interface type ........................................................................................... 29.3-4
Interface mode ......................................................................................... 29.3-4
Layer 1 standard ...................................................................................... 29.3-4
T3 timer .................................................................................................... 29.3-5
Bus configuration ..................................................................................... 29.3-5
To configure BRI S/T interfaces in a non-ISDN application ..................... 29.3-6
Configuring BRI S/T Circuits in a Non-ISDN Application ............................. 29.3-6
B-channel inversion type .......................................................................... 29.3-6
Tandem super-rate .................................................................................. 29.3-7
Automatic loopback on physically unconnected BRI circuits ................... 29.3-8
To configure B1 channels ........................................................................ 29.3-9
To configure B2 channels ........................................................................ 29.3-9
D-channel 3DS0 transport ....................................................................... 29.3-9
D-channel transport position .................................................................. 29.3-10
To configure D channels ........................................................................ 29.3-10
Making BRI Connections ........................................................................... 29.3-11
BRI channel connections ....................................................................... 29.3-11
To make connections ............................................................................. 29.3-12
ISDN Applications
29.4.1
29.4.2
29.4.3
29.4.4
Understanding the ISDN Backup Application .............................................. 29.4-1

Understanding the ISDN Channel Search Facility ....................................... 29.4-2
Configuring BRI S/T Interfaces in an ISDN Application ............................... 29.4-3
Interface type ........................................................................................... 29.4-3
Interface mode ......................................................................................... 29.4-3
Layer 1 standard ...................................................................................... 29.4-3
T3 timer .................................................................................................... 29.4-3
Forced activation ...................................................................................... 29.4-4
To configure BRI S/T interfaces in an ISDN application .......................... 29.4-4
Configuring BRI S/T Circuits in an ISDN Application ................................... 29.4-4
30. CPCs
30.1
Understanding CPC Configuration

30.1.1
30.1.2
30.2
Understanding CPCs ................................................................................... 30.1-1

Configuring CPCs ........................................................................................ 30.1-1
CPC Card Slots

30.2.1
Table of Contents
Understanding CPC Card Slots ................................................................... 30.2-1

To configure CPC slots ............................................................................ 30.2-1
(400)
lvii
Table of Contents
30.3
CPC Circuit Configuration

30.3.1
30.3.2
30.3.3
30.3.4
30.4
Understanding ISDN Indices on CPC Circuits ............................................. 30.4-1

Configuring Indices on CPC Circuits ........................................................... 30.4-1
Directory number ..................................................................................... 30.4-1
Bearer capability ...................................................................................... 30.4-4
Verification ............................................................................................... 30.4-5
Number of retries ..................................................................................... 30.4-5
Dial or non-dial ......................................................................................... 30.4-5
Dial delay ................................................................................................. 30.4-5
Number of channels ................................................................................. 30.4-6
To configure indices on CPC circuits ....................................................... 30.4-7
CPC Connections
30.5.1
30.5.2
lviii
Understanding ISDN Backup ....................................................................... 30.3-1

Understanding ISDN Channel Search ......................................................... 30.3-2
Configuration Process for the ISDN Backup and
Channel Search Applications .............................................................. 30.3-2
To configure the ISDN applications ......................................................... 30.3-2
Interface and channel numbering ............................................................ 30.3-3
Configuring CPC Circuits ............................................................................. 30.3-3
Interface type ........................................................................................... 30.3-4
Interface standard .................................................................................... 30.3-4
Number of B channels ............................................................................. 30.3-4
B-channel search order ............................................................................ 30.3-5
PCM encoding ......................................................................................... 30.3-5
Call status information reporting .............................................................. 30.3-5
Bearer service .......................................................................................... 30.3-5
BRI initialization ....................................................................................... 30.3-6
Bus configuration ..................................................................................... 30.3-6
To configure CPC circuits ........................................................................ 30.3-7
ISDN Indices
30.4.1
30.4.2
30.5

NNP 95-2035-01-00-B
Understanding CPC Connections for the ISDN Applications ....................... 30.5-1

CPSS ....................................................................................................... 30.5-1
Super-rate ................................................................................................ 30.5-1
Non super-rate ......................................................................................... 30.5-2
Making the Connections to Set Up the ISDN Applications .......................... 30.5-2
To connect D channels ............................................................................ 30.5-2
To configure preferred connections ......................................................... 30.5-2
To connect protecting connection ............................................................ 30.5-2
(400)
Table of Contents

NNP 95-2035-01-00-B
Table of Contents
31. HSA Cards

31.1
SONET/SDH and 3600+ MainStreet System Applications

31.1.1
31.1.2
31.2
Understanding High-speed Aggregate Card Configuration

31.2.1
31.2.2
31.3
Understanding HSA Card Slots ................................................................... 31.3-1

Configuring HSA Card Slots ........................................................................ 31.3-1
To configure an HSA slot card type ......................................................... 31.3-2
To configure HSA card name ................................................................... 31.3-2
HSA Card Traffic Protection

31.4.1
31.4.2
31.4.3
31.5
Understanding High-speed Aggregate Cards .............................................. 31.2-1

HSA card configurable parameters .......................................................... 31.2-1
SONET or SDH Service Configuration ....................................................... 31.2-6
HSA Card Slots

31.3.1
31.3.2
31.4
Understanding SONET and SDH Basics ..................................................... 31.1-1

SONET and SDH Data Transmission Rates and Structures ................... 31.1-1
Multiplexing .............................................................................................. 31.1-2
3600+ MainStreet Bandwidth Manager Applications ................................... 31.1-3
High-density time-division multiplexing .................................................... 31.1-3
Linear add/drop multiplexing and signal termination ................................ 31.1-3
Ring multiplexing ...................................................................................... 31.1-4
Understanding Traffic Protection ................................................................. 31.4-1

Traffic protection mode ............................................................................ 31.4-1
Protection switching options .................................................................... 31.4-2
1+1 mode line protection switching .......................................................... 31.4-5
Ring mode path protection switching ....................................................... 31.4-8
Configuring Traffic Protection Switching Options ...................................... 31.4-10
Protection switching options for 1+1 and ring modes ........................... 31.4-10
To configure HSA card traffic protection mode ...................................... 31.4-11
To configure 1+1 traffic protection options ............................................. 31.4-11
To configure ring traffic protection options ............................................. 31.4-12
Protection Switching Commands ............................................................... 31.4-12
Card or circuit lockout ............................................................................ 31.4-12
Forced switch ......................................................................................... 31.4-12
Manual switch ........................................................................................ 31.4-13
Clear command ...................................................................................... 31.4-13
To issue protection switching commands .............................................. 31.4-13
OC-3 and STM-1 Card Port Synchronization

31.5.1
Table of Contents
Understanding OC-3 or STM-1 Card Port Synchronization ......................... 31.5-1

Synchronization sources .......................................................................... 31.5-1
Slot options for port synchronization ........................................................ 31.5-1
To configure OC-3 or STM-1 card port synchronization .......................... 31.5-2
(400)
lix
Table of Contents
31.6
Broadband Circuits
31.6.1
31.6.2
31.6.3
31.6.4
31.6.5
31.7
Configuring the OC-3 or STM-1 Card Section DCC .................................... 31.8-1

To configure the OC-3 card DCC ............................................................. 31.8-1
To configure the STM-1 card DCC .......................................................... 31.8-1
Broadband Circuit Connections

31.9.1
31.9.2
31.9.3
31.9.4
lx
Understanding Broadband Signal Labels .................................................... 31.7-1

Configuring Broadband Signal Labels ......................................................... 31.7-1
To configure the OC-3 card STS-1 signal label ....................................... 31.7-2
To configure the STM-1 card AU-3 signal label ....................................... 31.7-2
To configure the STM-1 card AU-4 signal label ....................................... 31.7-2
To configure a VT-1.5 card VT- 1.5 circuit signal label ............................ 31.7-2
To configure a TU-12 card TU-12 circuit signal label ............................... 31.7-2
SONET and SDH Data Communication Channels

31.8.1
31.9
Understanding Broadband Circuits .............................................................. 31.6-1

OC-3 and STM-1 card broadband circuits ............................................... 31.6-1
VT-1.5 and TU-12 mapper card broadband circuits ................................. 31.6-2
Configuring OC-3 Card Circuit Structure ..................................................... 31.6-2
To configure an STS-1 as a link or circuit ................................................ 31.6-3
To configure STS-1 link VT structure ....................................................... 31.6-3
Configuring STM-1 Card Circuit Structure ................................................... 31.6-4
To configure SDH mode .......................................................................... 31.6-6
To configure an AU-3 as a link or circuit .................................................. 31.6-6
To configure TUG-3 structure .................................................................. 31.6-6
To configure TUG-3 or AU-3 TUG-2 structure ......................................... 31.6-6
Configuring Mapper Card Broadband Circuits ............................................. 31.6-7
Configuring broadband circuit provisioning .............................................. 31.6-7
To configure mapper card broadband circuit provisioning ....................... 31.6-7
Copying and Naming Circuits ...................................................................... 31.6-7
Copying and naming circuits .................................................................... 31.6-7
To copy or name circuits .......................................................................... 31.6-8
Broadband Signal Labels

31.7.1
31.7.2
31.8

NNP 95-2035-01-00-B
Understanding Broadband Connections ...................................................... 31.9-1

Viewing circuit connections ...................................................................... 31.9-2
To view circuit connection information ..................................................... 31.9-3
Bidirectional Broadband Circuit Connections .............................................. 31.9-3
To configure simple bidirectional or terminal add-drop connections ........ 31.9-4
To disconnect a bidirectional circuit ......................................................... 31.9-4
Pass-through Connections .......................................................................... 31.9-4
To configure a pass-through connection .................................................. 31.9-5
To disconnect a pass-through connection ............................................... 31.9-5
UPSR add-drop connections ....................................................................... 31.9-5
To configure a UPSR add-drop connection ............................................. 31.9-6
To disconnect all circuits in a UPSR add-drop connection ...................... 31.9-6
To disconnect a UPSR add-drop connection from a single ring .............. 31.9-6
(400)
Table of Contents

NNP 95-2035-01-00-B
Table of Contents
31.10 Mapper Card Super-rate Circuits

31.10.1
31.10.2
Understanding Super-rate Circuits for Mapper Cards ............................... 31.10-1

Contiguous super-rate circuits ............................................................... 31.10-1
Non-contiguous super-rate circuits ........................................................ 31.10-2
Equidistant super-rate circuits ................................................................ 31.10-2
Protecting super-rate circuits ................................................................. 31.10-3
Configuring Super-rate Circuits for Mapper Cards .................................... 31.10-4
To configure a tandem super-rate circuit ............................................... 31.10-5
To deconfigure a super-rate bundle ....................................................... 31.10-5
31.11 Zero Code Suppression for Narrowband Ports

31.11.1
Understanding Zero Code Suppression for VT-1.5 Card Narrowband

T1 Ports ............................................................................................ 31.11-1
Transparent framing ............................................................................... 31.11-1
Jam Bit 7 framing ................................................................................... 31.11-2
To configure zero code suppression for narrowband DS1 ports ............ 31.11-2
31.12 Narrowband Port Trunk Conditioning

31.12.1
31.12.2
31.12.3
31.12.4
31.12.5
Understanding Trunk Conditioning for Mapper Cards ............................... 31.12-1

One-way trunk conditioning ................................................................... 31.12-2
Two-way trunk conditioning ................................................................... 31.12-4
Disabling trunk conditioning ................................................................... 31.12-5
Trunk Conditioning Configuration Overview .............................................. 31.12-6
Configuring One-way or Two-way Trunk Conditioning .............................. 31.12-6
To select one-way or two-way trunk conditioning for
mapper cards ................................................................................. 31.12-6
Understanding Fault Class Trunk Conditioning ......................................... 31.12-6
Enabling or Disabling Fault Classes for Mapper Cards ............................. 31.12-8
Disabling trunk conditioning using fault classes ..................................... 31.12-8
To set mapper card fault classes ........................................................... 31.12-8
31.13 Narrowband Port Framing

31.13.1
31.13.2
31.13.3
Table of Contents
Understanding Framing for Narrowband Ports .......................................... 31.13-1

Configuring Framing for VT-1.5 Cards ....................................................... 31.13-1
D4 framing ............................................................................................. 31.13-1
ESF framing ........................................................................................... 31.13-2
To configure framing format on the narrowband DS-1 port ................... 31.13-2
Configuring Framing for TU-12 Cards ....................................................... 31.13-3
CAS framing ........................................................................................... 31.13-3
CCS framing .......................................................................................... 31.13-4
31 channels framing ............................................................................... 31.13-4
To configure framing for TU-12 card narrowband ports ......................... 31.13-4
(400)
lxi
Table of Contents

NNP 95-2035-01-00-B
31.14 Narrowband Circuit Fault Signalling

31.14.1
31.14.2
Understanding Fault Signalling for Mapper Cards ..................................... 31.14-1

Disabling fault signalling for mapper cards ............................................ 31.14-2
Fault signalling codes for mapper cards ................................................ 31.14-2
Configuring Fault Signalling for Mapper Cards .......................................... 31.14-2
Restrictions ............................................................................................ 31.14-3
To configure fault signalling for mapper cardprimary rate circuits ......... 31.14-3
31.15 Mapper Card PRI Signalling

31.15.1
31.15.2
31.15.3
Understanding Signalling for mapper cards ............................................... 31.15-1

Signalling types for mapper cards .......................................................... 31.15-1
Compatible mapper and PRI card signalling types ................................ 31.15-2
PLAR D3 signalling ................................................................................ 31.15-3
R2 digital signalling ................................................................................ 31.15-3
RBS ........................................................................................................ 31.15-3
Configuring Signalling for VT-1.5 Cards .................................................... 31.15-4
To enable signalling for VT-1.5 card narrowband port circuits ............... 31.15-4
To enable or disable VT-1.5 card narrowband port circuits ................... 31.15-4
To create clear channels on VT-1.5 card narrowband ports .................. 31.15-5
Configuring Signalling for TU-12 Card Circuits .......................................... 31.15-5
To configure signalling type for TU-12 cards ......................................... 31.15-6
31.16 Mapper Card Narrowband Circuit Inversion

31.16.1
31.16.2
Understanding Inversion for VT-1.5 and TU-12 Cards .............................. 31.16-1

Configuring Inversion for Card Narrowband Port Circuits .......................... 31.16-1
To configure inversion for mapper card narrowband port circuits .......... 31.16-1
31.17 TU-12 Card NU Bits Configuration

31.17.1
Configuring the NU bits for TU-12 Cards ................................................... 31.17-1

To configure NU bits for TU-12 cards .................................................... 31.17-1
To view the received NU bits for TU-12 cards ....................................... 31.17-1
31.18 TU-12 Card CRC-4 Reframing and Link Quality Monitoring

31.18.1
31.18.2
31.18.3
Understanding CRC-4 Reframing and Link Quality Monitoring ................. 31.18-1

Configuring CRC-4 Reframing ................................................................... 31.18-1
To configure narrowband E1 port CRC-4 reframing .............................. 31.18-1
Configuring CRC-4 or FAS Link Quality Monitoring ................................... 31.18-2
To select CRC-4 or FAS error detection ................................................ 31.18-2
31.19 Narrowband Circuit Custom Trunk Conditioning

31.19.1
31.19.2
lxii
Understanding Custom Trunk Conditioning ............................................... 31.19-1

Configuring Custom Trunk Conditioning for Mapper Cards ....................... 31.19-2
To configure custom trunk conditioning for mapper cards ..................... 31.19-3
(400)
Table of Contents

NNP 95-2035-01-00-B
Table of Contents
31.20 Mapper Card Narrowband Port Loopback Detection

31.20.1
31.20.2
31.20.3
Understanding Loopback Detection for Mapper Cards .............................. 31.20-1

CPSS Loopback Detection for Mapper Cards ........................................... 31.20-2
Establishing CPSS Loopback Detection for Mapper Cards ....................... 31.20-2
To configure loopback detection on mapper cards ................................ 31.20-2
List of Figures
Figure
Title
16.2-1
16.2-2
16.2-3
16.2-4
16.2-5
16.2-6
16.2-7
16.2-8
16.2-9
Node Management Session Nodes .......................................................................... 16.2-2

Serial Port Pinouts for a Class A Locally Controlled Shelf System ........................... 16.2-9
Serial Port Pinouts for a Class A Switching Shelf System ...................................... 16.2-10
Serial Port Pinouts for a Class B or 23-inch Locally Controlled or
Peripheral Shelf System ................................................................................... 16.2-11
Serial Port Pinouts for a Class B or 23-inch Switching Shelf System ..................... 16.2-12
Serial Port Pinout for CPC and FRS Card Faceplates ............................................ 16.2-13
Serial Port Pinout for DCP Card Faceplates ........................................................... 16.2-13
Serial Port Pinout for DS-3, E3, FRE and PE Card Faceplates .............................. 16.2-13
Serial Port Pinout for Control Card Faceplates ....................................................... 16.2-14
16.3-1
16.3-2
Header Line Fields .................................................................................................... 16.3-2

Main Menu for the MainStreet Node ......................................................................... 16.3-5
16.4-1
16.4-2
16.4-3
16.4-4
16.4-5
Peripheral Shelf and HSPS Card Shelf Numbering .................................................. 16.4-7

Slot Numbers for the Switching Shelf ....................................................................... 16.4-8
Slot Numbers for the Locally Controlled or Peripheral Shelf ................................... 16.4-10
Slot Numbers for the HSPS .................................................................................... 16.4-11
Slot Numbers for the HSPS2 .................................................................................. 16.4-12
16.5-1
16.5-2
16.5-3
16.5-4
16.5-5
16.5-6
16.5-7
16.5-8
16.5-9
Switching Shelf Display ............................................................................................ 16.5-2

Summary Display for a Typical Conguration ........................................................... 16.5-3
SHOW_A Display ...................................................................................................... 16.5-4
Switching Card Information Display .......................................................................... 16.5-6
Card Information Display .......................................................................................... 16.5-7
3600+ MainStreet Control Card Information Display ................................................ 16.5-8
Control Card Module Information Display ................................................................ 16.5-9
Switching Shelf Connection Display ....................................................................... 16.5-10
Peripheral Shelf Connection Display ...................................................................... 16.5-10
17.1-1
17.1-2
CONFIG CONNECT Display (Peripheral Shelf) ....................................................... 17.1-4

CONFIG CONNECT Display (Switching Shelf) ........................................................ 17.1-4
17.2-1
17.2-2
Locally Controlled Shelf Timing Source Display ....................................................... 17.2-3

Enhanced Locally Controlled Shelf Timing Source Display Status
Message Mode ................................................................................................... 17.2-3
Peripheral Shelf Timing Source Display .................................................................... 17.2-4
Switching Shelf Timing Source Display .................................................................... 17.2-5
17.2-3
17.2-4
Table of Contents
(400)
lxiii
Table of Contents

NNP 95-2035-01-00-B
17.2-5
17.2-6
17.2-7
17.2-8
17.2-9
Example of an ANS Network .................................................................................... 17.2-9

ANS Zones ............................................................................................................. 17.2-10
ANS Links Display .................................................................................................. 17.2-15
Timing Source Display ............................................................................................ 17.2-20
DDS Composite Clock Display ............................................................................... 17.2-27
17.3-1
17.3-2
Jumper W4 Location on the 3600+ MainStreet Control Card .................................. 17.3-3

3600+ MainStreet Bandwidth Manager HOUSE Display ........................................ 17.3-13
17.4-1
Header Line Fields .................................................................................................... 17.4-1
17.5-1
CONFIG SLOT Access Level Denition .................................................................... 17.5-4
17.6-1
17.6-2
17.6-3
17.6-4
17.6-5
17.6-6
17.6-7
17.6-8
17.6-9
17.6-10
17.6-11
17.6-12
17.6-13
CPSS Cost Example ................................................................................................. 17.6-6

CPSS Master/Slave Protocol - Switching Shelf Controlled System .......................... 17.6-7
CPSS Master/Slave Protocol - Locally Controlled System ....................................... 17.6-7
Example of Upgrade from Release 4 ........................................................................ 17.6-9
CPSS Grooming Application ................................................................................... 17.6-12
CPSS Node Parameter Display .............................................................................. 17.6-15
4 kb/s CPSS Channel with Framing Bit at F0-B7 .................................................... 17.6-28
4 kb/s CPSS Channel with Framing Bit at F0-B4 .................................................... 17.6-28
16 kb/s CPSS Channel with Framing Bit at F0-B5 .................................................. 17.6-29
48 kb/s CPSS Channels with Framing Bit at F0-B6 ................................................ 17.6-30
CPSS Rerouting ..................................................................................................... 17.6-34
FASTbus CPSS Connections ................................................................................. 17.6-35
CONFIG CONNECT CPSSx NMTI Screen ........................................................... 17.6-36
18.2-1
18.2-2
18.2-3
18.2-4
Terminology for Protecting Connections ................................................................... 18.2-1

Out-of-Service Signalling for Tandem Nodes ............................................................ 18.2-2
Preferred Connection Available ................................................................................ 18.2-4
Activity Qualied Access ........................................................................................... 18.2-5
18.3-1
Operating Rules for Redundant Primary Rate Pair ................................................... 18.3-4
20.4-1
20.4-2
20.4-3
20.4-4
20.4-5
20.4-6
20.4-7
M48 Transitional Signalling ....................................................................................... 20.4-1

M60 Transitional Signalling ....................................................................................... 20.4-2
Delta (M44/M55) ADPCM Subframe ........................................................................ 20.4-3
Transitional (M48/M60) ADPCM Subframe ............................................................... 20.4-4
Viewing Compressor Connections ............................................................................ 20.4-5
Viewing Sub-channel Connections ........................................................................... 20.4-6
Connecting a Compressed Channel ......................................................................... 20.4-9
20.5-1
TSM Timeslot Assignment ........................................................................................ 20.5-1
20.6-1
20.6-2
D4 Framing Format ................................................................................................... 20.6-2

ESF Framing Format ................................................................................................ 20.6-3
20.9-1
20.9-2
20.9-3
One-way Trunk Conditioning (Group 1) ..................................................................... 20.9-4

One-way Trunk Conditioning (Group 2) ..................................................................... 20.9-5
Two-way Trunk Conditioning ..................................................................................... 20.9-6
20.10-1
Fault Signalling ....................................................................................................... 20.10-1
lxiv
(400)
Table of Contents

NNP 95-2035-01-00-B
Table of Contents
20.11-1
Connection Path with Custom Trunk Conditioning .................................................. 20.11-1
20.12-1
20.12-2
Example of Signalling Type Conguration .............................................................. 20.12-3

TS0 Bits for the TTC2M Card ................................................................................. 20.12-9
20.14-1
20.14-2
20.14-3
20.14-4
20.14-5
Loopback Detection ................................................................................................ 20.14-2

CPSS Loopback Detection Path ............................................................................. 20.14-4
TS24 Loopback Detection Path .............................................................................. 20.14-5
On-fault Loopback Detection Path .......................................................................... 20.14-5
NMTI Display for Loopback Detection .................................................................... 20.14-7
20.15-1
Equidistant Super-rate DS0s on E1 Links .............................................................. 20.15-3
20.16-1
24 DS0 Super-rate Connection RAPID Switch to an Alternative Path .................... 20.16-2
20.17-1
20.17-2
20.17-3
Conguration Link Options Display ......................................................................... 20.17-3

Errored Second Threshold Equation ....................................................................... 20.17-3
Dual E1-2 Card Link Monitoring Performance Thresholds Display ......................... 20.17-6
20.18-1
20.18-2
20.18-3
E1 Links Used for Access and Network Termination .............................................. 20.18-5

The E1 Multi-frame Showing the SA4 Bit ............................................................... 20.18-7
Dual E1 and Dual E1-2 Card E-bits ........................................................................ 20.18-9
20.19-1
20.19-2
Supervisory Channel Showing Signalling Bits ........................................................ 20.19-4

X.21 PRI Screen Display ........................................................................................ 20.19-5
20.20-1
20.20-2
20.20-3
20.20-4
20.20-5
Slot Display for an MPA Card Link .......................................................................... 20.20-3

Default Backplane Channel Assignments on a Double Bandwidth Shelf ............... 20.20-5
Default Backplane Channel Assignments on a Single Bandwidth Shelf ................. 20.20-6
Example TS0 Framed with HCM3, HCM4 or HCM5 ............................................. 20.20-10
Example SRM Data on TS0 Framed with HCM1 or HCM2 ................................... 20.20-11
21.3-1
21.3-2
E&M Signalling ......................................................................................................... 21.3-3

4WDX Signalling Interface ........................................................................................ 21.3-8
21.5-1
Transmission Level Points ......................................................................................... 21.5-1
21.9-1
21.9-2
21.9-3
Audio Loop Singing ................................................................................................... 21.9-1

Tx Mute ..................................................................................................................... 21.9-1
Tx Mute Display ........................................................................................................ 21.9-2
21.11-1
CONFIG CIRCUIT EQUALIZER NMTI Display ...................................................... 21.11-2
22.3-1
22.3-2
22.3-3
22.3-4
22.3-5
22.3-6
22.3-7
22.3-8
22.3-9
Transmit and Receive Clocks .................................................................................... 22.3-8

RS-422 DCC Hardware Genders ........................................................................... 22.3-10
DCC/DTU Clocking Applications ............................................................................ 22.3-12
Calculating the multiplier ......................................................................................... 22.3-17
Maximum Super-rate Interface Speeds .................................................................. 22.3-20
2B1Q, 27LC2 and DNIC Line Card Super-rate Connections .................................. 22.3-22
Port Activity Switching Display ................................................................................ 22.3-28
Basic ISDN Reference Model ................................................................................. 22.3-33
ISDN Loop Extension ............................................................................................. 22.3-33
Table of Contents
(400)
lxv
Table of Contents

NNP 95-2035-01-00-B
22.3-10
22.3-11
22.3-12
23.3-1
23.3-2
3DS0 ISDN Loop Extension Application ................................................................. 22.3-34

5DS0 ISDN Loop Extension Application ................................................................. 22.3-35
2B1Q Channel Unit Connection Display ................................................................. 22.3-38
Transparent 8 kb/s and 16 kb/s Compressed Voice Circuits ..................................... 23.3-4
HCM 16 kb/s Compressed Voice Circuit ................................................................... 23.3-5
23.4-1
23.4-2
23.4-3
23.4-4
PCM Multidrop Bridges ............................................................................................. 23.4-1

Cascading PCM Multidrop Data Bridges .................................................................. 23.4-2
Master and Slave Bridging Application ..................................................................... 23.4-3
ADI Application ......................................................................................................... 23.4-4
23.5-1
23.5-2
23.5-3
23.5-4
23.5-5
23.5-6
23.5-7
VCB Conference Conguration ................................................................................. 23.5-1

VCB Broadcast Conguration ................................................................................... 23.5-2
Large VCBs ............................................................................................................... 23.5-2
Invalid Loop Types .................................................................................................... 23.5-3
Gain Examples ......................................................................................................... 23.5-5
VCB Example ........................................................................................................... 23.5-7
Cascading VCB Example .......................................................................................... 23.5-7
23.6-1
23.6-2
23.6-3
23.6-4
23.6-5
23.6-6
23.6-7
23.6-8
23.6-9
23.6-10
23.6-11
23.6-12
23.6-13
23.6-14
23.6-15
23.6-16
23.6-17
23.6-18
23.6-19
23.6-20
23.6-21
23.6-22
23.6-23
23.6-24
23.6-25
23.6-26
23.6-27
23.6-28
23.6-29
23.6-30
23.6-31
23.6-32
23.6-33
Transparent Channel ................................................................................................ 23.6-2

Enhanced Transparent Rate Adaption Supervisory Circuit .................................... 23.6-3
Enhanced Transparent Rate Adaption Transparent Synchronous Signalling ......... 23.6-3
HCM Frame .............................................................................................................. 23.6-4
DDS DS0-A and DS0-B Frame Structure ................................................................. 23.6-6
DS0-A Format for 56 kb/s DDS Channel .................................................................. 23.6-7
DS0-A Format for 9.6 kb/s DDS Channel ................................................................. 23.6-8
DS0-A Format for 19.2 kb/s DDS Channel ............................................................. 23.6-10
X.50 Framing Structure ........................................................................................... 23.6-12
X.50 Division 3 Framing Pattern ............................................................................. 23.6-13
Branch Channels and Aggregate Channels ........................................................... 23.6-16
Transparent SRM Default Conguration ................................................................. 23.6-17
Transparent SRM Conguration Examples ............................................................. 23.6-17
HCM SRM Default Conguration ............................................................................ 23.6-18
HCM SRM Conguration Examples ....................................................................... 23.6-18
DS0-B Format for 9.6 kb/s and 19.2 kb/s DDS Channels ....................................... 23.6-19
DS0-B Format for 4.8 kb/s DDS Channel ............................................................... 23.6-20
DS0-B Format for 2.4 kb/s DDS Channel ............................................................... 23.6-21
19.2 kb/s Channels on a DS0-B_9.6 SRM ............................................................. 23.6-21
Transparent or HCM SRMs on a DCC .................................................................... 23.6-24
Transparent or HCM SRMs on a Line Card ............................................................ 23.6-24
DDS or X.50 SRMs on a Line Card ........................................................................ 23.6-24
DDS Access or X.50 Telco SRMs on a Line Card .................................................. 23.6-25
Transparent or HCM SRMs on a DSP Card ........................................................... 23.6-25
DDS or X.50 SRMs on a DSP Card ........................................................................ 23.6-26
Channels on Line Card Transparent and HCM SRMs ............................................ 23.6-28
Channels on Line Card DDS or X.50 SRMs ........................................................... 23.6-29
Channels on Line Card DDS Access or X.50 Telco SRMs ..................................... 23.6-29
Channels on Two-circuit DSP Card Transparent and HCM SRMs .......................... 23.6-30
Channels on Six-circuit DSP Card Transparent and HCM SRMs ........................... 23.6-31
Channels on DSP5H Card Transparent and HCM SRMs ....................................... 23.6-32
lxvi
(400)
Table of Contents

NNP 95-2035-01-00-B
Table of Contents
23.6-34
23.6-35
23.6-36
23.6-37
23.6-38
23.6-39
23.6-40
23.6-41
23.6-42
Channels on Two-circuit DSP Card DDS or X.50 SRMs ......................................... 23.6-33

Channels on Six-circuit DSP Card DDS Access or X.50 Telco SRMs .................... 23.6-33
Channels on Six-circuit DSP Card DDS Core SRMs .............................................. 23.6-34
Transparent Transport Bandwidth ........................................................................... 23.6-35
HCM Transport Bandwidth ...................................................................................... 23.6-36
Bit Numbering Conventions .................................................................................... 23.6-36
H-bit Signalling Results for 2612, 2613 and 2715 MainStreet DTUs ...................... 23.6-39
Continuity Checking on DS0-B SRMs .................................................................... 23.6-45
Continuity Checking on DS0-A SRMs and MJUs ................................................... 23.6-46
23.7-1
23.7-2
SRM Creating a Multidrop Data Bridge .................................................................... 23.7-1

Multijunction Units and Branch Identication Numbers ............................................ 23.7-3
23.9-1
23.9-2
SRS Connections ..................................................................................................... 23.9-2

HCM SRS Display Example ..................................................................................... 23.9-3
23.10-1
23.10-2
23.10-3
23.10-4
23.10-5
Data Transmission without BONDING .................................................................... 23.10-1

Data Transmission with BONDING ......................................................................... 23.10-2
BONDING Application ............................................................................................ 23.10-2
BONDING in the 3600 MainStreet System ............................................................. 23.10-3
IMC BONDING Display ........................................................................................... 23.10-6
23.12-1
G3 Fax Example ..................................................................................................... 23.12-2
25.1-1
25.1-2
25.1-3
25.1-4
25.1-5
25.1-6
25.1-7
Frame Relay Network Example ................................................................................ 25.1-4

Class-of-service Parameters .................................................................................... 25.1-5
Congestion Thresholds ............................................................................................. 25.1-7
Congestion Filtering .................................................................................................. 25.1-8
FECN and BECN Bits ............................................................................................. 25.1-10
Congestion Avoidance and Recovery Procedures ................................................. 25.1-11
Link Management Protocol Support ....................................................................... 25.1-12
25.3-1
25.3-2
Switch Congestion Thresholds Display ..................................................................... 25.3-2

Switch Congestion Notication Parameters Display ................................................. 25.3-2
25.4-1
25.4-2
25.4-3
25.4-4
25.4-5
FASTbus Topology .................................................................................................... 25.4-1

FASTbus Fault Recovery .......................................................................................... 25.4-2
FASTbus Station Status Display ............................................................................... 25.4-3
FASTbus Parameters Display ................................................................................... 25.4-5
FASTbus Congestion Parameters Display ................................................................ 25.4-5
25.6-1
25.6-2
25.6-3
Frame Stream Status Display ................................................................................... 25.6-2

Frame Stream Conguration Display ........................................................................ 25.6-3
Frame Stream Congestion Parameters Display ........................................................ 25.6-4
25.7-1
25.7-2
25.7-3
25.7-4
25.7-5
Stream DLC Status Display ...................................................................................... 25.7-2

FASTbus DLC Status Display ................................................................................... 25.7-3
Local DLC Example .................................................................................................. 25.7-5
Backplane DLC Connection Example ....................................................................... 25.7-6
FASTbus DLC Connection Example ......................................................................... 25.7-8
Table of Contents
(400)
lxvii
Table of Contents

NNP 95-2035-01-00-B
25.8-1
25.8-2
25.8-3
Card-to-card Class-of-service Conguration Example ............................................. 25.8-2

FRE Class-of-Service Conguration Example .......................................................... 25.8-2
Class-of-Service Conguration Display .................................................................... 25.8-3
25.9-1
25.9-2
Subrate Multiplexing HCM Streams ........................................................................ 25.9-11

Subrate Multiplexing DDS Streams ........................................................................ 25.9-12
25.10-1
25.10-2
25.10-3
25.10-4
25.10-5
25.10-6
25.10-7
LAPB Encapsulation Example ................................................................................ 25.10-2

Transparent HDLC Encapsulation Example ........................................................... 25.10-2
Annex G Encapsulation .......................................................................................... 25.10-3
RFC 1490 Encapsulation of LAPB Frames ............................................................. 25.10-4
Parameters for Frame Relay Encapsulation Circuits .............................................. 25.10-7
Connections for Super-rate Encapsulation Circuits .............................................. 25.10-11
Connections for Subrate Encapsulation Circuits ................................................... 25.10-12
25.11-1
25.11-2
Switched Access to Frame Relay PVCs ................................................................. 25.11-1

Switched Access over ISDN or Switched 56 Networks .......................................... 25.11-2
26.1-1
26.1-2
26.1-3
26.1-4
26.1-5
A Frame Relay SVC Network ................................................................................... 26.1-2

Frame Relay SVC Functionality ................................................................................ 26.1-3
Routing through a Frame Relay SVC Network ......................................................... 26.1-5
A Sample Frame Relay SVC Network ...................................................................... 26.1-8
A Map of Circuit-switched Connections .................................................................... 26.1-9
26.2-1
26.2-2
Default Conguration for Signalling Channel Parameters ......................................... 26.2-2

Display Screen for Signalling Channels .................................................................... 26.2-4
26.3-1
User Congurations .................................................................................................. 26.3-4
26.4-1
Connection Management Functionality .................................................................... 26.4-2
26.5-1
26.5-2
Remote Address Table .............................................................................................. 26.5-3

An Example of a Crankback ..................................................................................... 26.5-5
27.1-1
27.1-2
27.1-3
27.1-4
27.1-5
36120 MainStreet X.25 Protocol Subsystems .......................................................... 27.1-3

End-to-end Protocol .................................................................................................. 27.1-5
Direct X.25 Access ................................................................................................... 27.1-6
Encapsulated Access for Basic Rate and Super-rate Devices ................................. 27.1-7
Encapsulated Access for Subrate Devices ............................................................... 27.1-7
27.2-1
27.2-2
27.2-3
27.2-4
Internal Network Topology ........................................................................................ 27.2-2

RTP Virtual Connection ............................................................................................ 27.2-5
Mapping Virtual Circuits to VCons and PVCs ........................................................... 27.2-6
Example of No Flow Control Negotiation Where the Destination
Switch Segments and Combines Packets ........................................................ 27.2-13
Example of No Flow Control Negotiation Where the Originating
Switch Segments and Combines Packets ........................................................ 27.2-13
Example of Flow Control Negotiation at the Calling DTE Where
Packet Segmenting and Combining Does Not Occur ....................................... 27.2-15
Example of Flow Control Negotiation at the Calling DTE Where the
Originating Switch Segments and Combines Packets ..................................... 27.2-15
27.2-5
27.2-6
27.2-7
lxviii
(400)
Table of Contents

NNP 95-2035-01-00-B
27.2-8
27.2-9
27.2-10
Table of Contents
Example of Flow Control Negotiation at the Called DTE Where the

Destination Switch Segments and Combines Packets ..................................... 27.2-17
Example of Flow Control Negotiation at the Called DTE Where the
Call is Cleared .................................................................................................. 27.2-17
Example of Flow Control Negotiation Where Packet Segmenting and
Combining is Avoided ....................................................................................... 27.2-19
27.4-1
27.4-2
Main Menu for the X.25 FRE NMTI ........................................................................... 27.4-1

Mandatory X.25 Conguration Activities ................................................................... 27.4-5
27.5-1
27.5-2
X.25 Switch-wide Parameters Display ...................................................................... 27.5-2

X.25 Global Resources Display ................................................................................ 27.5-3
27.6-1
27.6-2
27.6-3
27.6-4
27.6-5
27.6-6
27.6-7
27.6-8
27.6-9
27.6-10
High-speed, Non-redundant, Fully-meshed Network Topology ................................ 27.6-2

Network Routing Topology ........................................................................................ 27.6-3
A Three-tier Routing Topology .................................................................................. 27.6-4
High-fanout, Low-volume, Non-redundant Network Topology ................................... 27.6-5
Trunk Requirement Comparison ............................................................................... 27.6-6
Redundant Network Topology ................................................................................... 27.6-8
GFR Information Frame Format .............................................................................. 27.6-11
Example of Hub Domain Dynamic Routing ............................................................ 27.6-13
Successful Routing Using Frame Reversal ............................................................. 27.6-16
GFR Parameter Conguration Display .................................................................... 27.6-17
27.7-1
27.7-2
27.7-3
27.7-4
27.7-5
27.7-6
27.7-7
27.7-8
27.7-9
27.7-10
27.7-11
27.7-12
27.7-13
27.7-14
27.7-15
Global Address Table Display ................................................................................... 27.7-2

Multiple Address Prexes on a Link .......................................................................... 27.7-5
Example of How Priorities Are Used ......................................................................... 27.7-6
Load Sharing Using Different Weights ...................................................................... 27.7-7
Route Redundancy Using Priorities .......................................................................... 27.7-8
Local Address Table Display ..................................................................................... 27.7-9
Call Routing Process at the Originating Switch: Basic and Gateway ...................... 27.7-13
Basic Routing at the Originating Switch .................................................................. 27.7-14
Basic Routing at the Destination Switch ................................................................. 27.7-15
Shared DNICs ......................................................................................................... 27.7-17
Network Migration Scenario Using Networks with Shared DNICs .......................... 27.7-18
Use of Priorities and Weights During X.75 Routing ................................................ 27.7-19
Gateway Routing at the Originating Switch ............................................................ 27.7-23
Gateway Routing at the Destination Switch ............................................................ 27.7-24
Re-routing or Retrying Calls ................................................................................... 27.7-25
27.8-1
27.8-2
CONFIG TRUNK SHOW_ALL Display ...................................................................... 27.8-2

Provisioning Backbone Trunks .................................................................................. 27.8-7
27.9-1
27.9-2
27.9-3
27.9-4
27.9-5
27.9-6
27.9-7
27.9-8
27.9-9
NUI Validation System .............................................................................................. 27.9-2

NUI Validation Process ............................................................................................. 27.9-4
Standardized NUI Format (ITU-T Recommendation X.25 1992, Appendix VI) ......... 27.9-5
Reversed NUI Format ............................................................................................... 27.9-5
Fixed-length NUI and Password Format ................................................................... 27.9-5
Bellcore NUI Format ................................................................................................. 27.9-6
NUI Validation Subsystem Components and Interfaces ........................................... 27.9-6
Redundant NUI Validation Server Interfaces ............................................................ 27.9-8
NUI Server Agent Parameters Display ..................................................................... 27.9-9
Table of Contents
(400)
lxix
Table of Contents

NNP 95-2035-01-00-B
27.10-1
27.10-2
27.10-3
27.10-4
27.10-5
27.10-6
27.10-7
27.10-8
27.10-9
Typical X.25 Accounting Application ....................................................................... 27.10-1

Components of the X.25 Accounting Subsystem ................................................... 27.10-2
Collection Intervals, Interval Reports and Usage Counts ....................................... 27.10-3
Example of an Intermediate Record ....................................................................... 27.10-4
Example of an End Record ..................................................................................... 27.10-5
Relationship Between an Intermediate Record and an End Record ...................... 27.10-6
Example of a Periodic Record ................................................................................ 27.10-7
NTP Time Initialization Display ............................................................................... 27.10-8
Accounting Generation Parameters Display ......................................................... 27.10-17
27.11-1
27.11-2
Data Collector Agent XACs and Data Collector Interface XACs ............................. 27.11-2
Data Collector Agent Parameters Display .............................................................. 27.11-5
27.12-1
Example Accounting Subsystem Conguration ...................................................... 27.12-2
27.13-1
27.13-2
27.13-3
27.13-4
27.13-5
27.13-6
27.13-7
27.13-8
27.13-9
27.13-10
27.13-11
27.13-12
27.13-13
27.13-14
Direct LAPB Access ................................................................................................ 27.13-2

Annex G Encapsulation of LAPB Frames ............................................................... 27.13-3
RFC 1490 Encapsulation of LAPB Frames ............................................................. 27.13-4
Frame Relay Encapsulation Methods ..................................................................... 27.13-5
Encapsulated Access Using a PAD/FRAD ............................................................. 27.13-5
Encapsulated Access Using the FRS Card ............................................................ 27.13-6
Encapsulated Access for Subrate Devices ............................................................. 27.13-7
Parameters for Frame Relay Encapsulation Circuits ............................................ 27.13-10
Conguring Packet and Frame Sizes for an Encapsulation Circuit ....................... 27.13-13
FRS Circuit Conguration Display ........................................................................ 27.13-15
Valid X.25 Super-rate Connections ....................................................................... 27.13-17
Connections for Super-rate Encapsulation Circuits .............................................. 27.13-18
Connections for Subrate Encapsulation Circuits ................................................... 27.13-19
Subrate Encapsulation Circuit Connection ........................................................... 27.13-20
27.14-1
27.14-2
27.14-3
27.14-4
27.14-5
27.14-6
27.14-7
Link Layer Parameters Display ............................................................................... 27.14-2

Logical Channels and Virtual Circuits ..................................................................... 27.14-9
LCN Allocation ...................................................................................................... 27.14-10
Network Layer Parameters Display ....................................................................... 27.14-13
Internal and External Address Formats ................................................................ 27.14-30
Address Translation Table Display ........................................................................ 27.14-31
Address Translation Entry Display ........................................................................ 27.14-37
27.15-1
27.15-2
27.15-3
27.15-4
27.15-5
27.15-6
27.15-7
X.121 and E.164 Address Formats ......................................................................... 27.15-1

Basic NUA Parameters Display .............................................................................. 27.15-2
Call Redirection Example ....................................................................................... 27.15-8
Charging Parameters Display ............................................................................... 27.15-10
CUG Example ....................................................................................................... 27.15-20
Closed User Group Display .................................................................................. 27.15-21
Default Flow Control and Throughput Class Display ............................................ 27.15-26
27.16-1
COPY Command NMTI Display .............................................................................. 27.16-2
27.17-1
27.17-2
X.25 PVCs SHOW_ALL Display ............................................................................. 27.17-3

X.25 PVCs Parameters Display .............................................................................. 27.17-4
lxx
(400)
Table of Contents

NNP 95-2035-01-00-B
Table of Contents
27.18-1
27.18-2
Hunt Group Addresses Display .............................................................................. 27.18-3

Hunt Group Members Display ................................................................................ 27.18-4
27.19-1
27.19-2
27.19-3
Direct X.25 Access ................................................................................................. 27.19-2

Encapsulated Access ............................................................................................. 27.19-4
Subrate Encapsulated Access ................................................................................ 27.19-7
27.20-1
27.20-2
27.20-3
27.20-4
27.20-5
27.20-6
27.20-7
27.20-8
Example of Service Interworking ............................................................................ 27.20-2

Example of Network Interworking ........................................................................... 27.20-3
End-to-end Protocol Stack ...................................................................................... 27.20-3
End-to-end Call Path ............................................................................................... 27.20-5
XFR Header Conversion ......................................................................................... 27.20-6
Example of Service Interworking Using LMI ........................................................... 27.20-8
XFR Conguration Parameters ............................................................................. 27.20-12
NUA Parameters NMTI ......................................................................................... 27.20-13
28.1-1
28.1-2
28.1-3
28.1-4
X.75 Link ................................................................................................................... 28.1-1

X.75 and X.35 Interconnection Possibilities .............................................................. 28.1-2
Use of the ICUG Mapping Table ............................................................................... 28.1-8
Rules Governing the Generation of Accounting Records for X.75 ............................ 28.1-9
28.2-1
28.2-2
X.75 Link Layer Parameters Display ......................................................................... 28.2-2

X.75 Network Layer Parameters Display .................................................................. 28.2-8
28.3-1
NUA Parameters Display .......................................................................................... 28.3-1
29.1-1
29.1-2
Basic ISDN Reference Model ................................................................................... 29.1-1

BRI S/T Card Application .......................................................................................... 29.1-2
29.3-1
29.3-2
29.3-3
Leased Line Application ............................................................................................ 29.3-1

Leased Line Connections ......................................................................................... 29.3-2
ISDN Loop Extension ............................................................................................... 29.3-3
29.4-1
29.4-2
ISDN Backup Application .......................................................................................... 29.4-1

ISDN Backup Connections ....................................................................................... 29.4-2
30.3-1
30.3-2
ISDN Backup Protection ........................................................................................... 30.3-1

D-channel Connections ............................................................................................ 30.3-2
31.1-1
31.1-2
Example of Linear Add/Drop Multiplexing and

Signal Termination Applications ......................................................................... 31.1-4
Example of a Ring Application .................................................................................. 31.1-5
31.4-1
31.4-2
31.4-3
31.4-4
31.4-5
31.4-6
31.4-7
Ring Trafc Protection mode conguration screen ................................................... 31.4-2

1+1 Trafc Protection Mode Conguration Display ................................................... 31.4-3
1+1 Trafc Protection Mode ...................................................................................... 31.4-5
1+1 Trafc protection Line Fault ................................................................................ 31.4-6
Bidirectional Switching Mode Reaction ..................................................................... 31.4-7
Unidirectional Switching Mode Reaction .................................................................. 31.4-7
Ring Mode ................................................................................................................ 31.4-9
Table of Contents
(400)
lxxi
Table of Contents

NNP 95-2035-01-00-B
31.6-1
31.6-2
31.6-3
OC-3 Card Circuit Structure ...................................................................................... 31.6-3

STM-1 Card AU-3 Mode ........................................................................................... 31.6-4
STM-1 Card AU-4 Mode ........................................................................................... 31.6-5
31.9-1
31.9-2
31.9-3
31.9-4
Circuit Connection Display ........................................................................................ 31.9-2

Simple Bidirectional Connections ............................................................................. 31.9-3
Pass -through Connection ........................................................................................ 31.9-5
UPSR Add-Drop Connection .................................................................................... 31.9-6
31.10-1
Equidistant Super-rate DS0s on TU-12 Card Narrowband Ports ............................ 31.10-3
31.12-1
31.12-2
31.12-3
One-way Trunk Conditioning (Group 1) ................................................................... 31.12-3

One-way Trunk Conditioning (Group 2) ................................................................... 31.12-4
Two-way Trunk Conditioning ................................................................................... 31.12-5
31.13-1
31.13-2
D4 Framing Format ................................................................................................. 31.13-2

ESF Framing Format .............................................................................................. 31.13-2
List of Tables
Table
Title
16.2-1
16.2-2
16.2-3
16.2-4
System Serial Ports .................................................................................................. 16.2-6

Serial Port Device Connections ................................................................................ 16.2-7
Control Card and Backplane or Bulkhead Serial Ports ............................................. 16.2-7
System Serial Port Configuration .............................................................................. 16.2-8
16.3-1
Generic Release Numbers and Long Names ........................................................... 16.3-3
16.4-1
16.4-2
Shelf, Slot, Link and Circuit Identifier Formats .......................................................... 16.4-2

Locally Controlled and Peripheral Shelf UCS Access .............................................. 16.4-9
16.5-1
16.5-2
Heading Information for Summary Display ............................................................... 16.5-3

SHOW_A Display Information .................................................................................. 16.5-5
17.1-1
17.1-2
17.1-3
Connection Types ..................................................................................................... 17.1-2

Circuit Configuration Procedures .............................................................................. 17.1-2
CONFIG CONNECT Display Symbols ..................................................................... 17.1-5
17.2-1
17.2-2
17.2-3
17.2-4
17.2-5
17.2-6
3600 MainStreet Series Bandwidth Managers Synchronization Sources ................. 17.2-2

Synchronization Status Messages ............................................................................ 17.2-6
Translation Table Default Values .............................................................................. 17.2-7
Timing and Synchronization Configuration Parameters and Options ..................... 17.2-11
Timing and Synchronization Configuration Procedures .......................................... 17.2-12
Timing Source Status ............................................................................................. 17.2-21
lxxii
(400)
Table of Contents

NNP 95-2035-01-00-B
Table of Contents
17.3-1
17.3-2
17.3-3
Control Card and Backplane or Bulkhead Serial Ports ............................................. 17.3-4

Serial Port Configuration Parameters and Options .................................................. 17.3-5
HOUSE Display field Descriptions .......................................................................... 17.3-14
17.4-1
Node Configuration Parameters and Options ........................................................... 17.4-2
17.5-1
17.5-2
17.5-3
Access Level and Password Configuration Parameters and Options ..................... 17.5-2
Suggested Access Level Definitions for Control Card Sessions .............................. 17.5-5
Suggested Access Level Definitions for FRS, FRE and PE Card Sessions ............. 17.5-6
17.6-1
17.6-2
17.6-3
17.6-4
CPSS Path Cost Values ........................................................................................... 17.6-6

CPSS Configuration Parameters and Options ........................................................ 17.6-13
CPSS Connection Configuration Procedures ......................................................... 17.6-14
CPSS Timers .......................................................................................................... 17.6-37
18.1-1
18.1-2
18.1-3
18.1-4
18.1-5
18.1-6
18.1-7
18.1-8
Control Redundancy ................................................................................................. 18.1-1

Control Redundancy Configuration Parameters and Options ................................... 18.1-2
Control Redundancy Configuration Procedures ....................................................... 18.1-3
Redundancy Modes for DS-3 II and E3 Cards ......................................................... 18.1-7
Field Descriptions for Control Redundancy .............................................................. 18.1-8
Conditions Contributing to System Demerits .......................................................... 18.1-11
DS-3 II Fast Protection Switching Options .............................................................. 18.1-15
E3 Fast Protection Switching Options .................................................................... 18.1-16
18.2-1
Protection Switching Configuration Parameters and Options ................................... 18.2-3
18.3-1
18.3-2
18.3-3
18.3-4
18.3-5
PRI Redundancy Configuration Parameter and Options .......................................... 18.3-2

PRI Redundancy Configuration Procedures ............................................................. 18.3-2
Alarms for Declaring Beginning and End of Link Faults ........................................... 18.3-5
Reason Codes for Card Activity Change Alarm ........................................................ 18.3-7
Fault Processing Demerit Points .............................................................................. 18.3-8
19.1-1
19.1-2
19.1-3
19.1-4
19.1-5
19.1-6
19.1-7
Control Card Configuration Parameters and Options ............................................... 19.1-2

Expander Card Configuration Parameter and Options ............................................. 19.1-3
Switching Card Configuration Parameters and Options ........................................... 19.1-3
Common Carrier Card Configuration Parameter and Option .................................... 19.1-3
Test Card Configuration Parameters and Options .................................................... 19.1-4
Test Module Configuration Parameters and Options ................................................ 19.1-4
GFC3 Configuration Parameters and Options .......................................................... 19.1-6
19.3-1
Expander Card Configuration Options ...................................................................... 19.3-3
20.1-1
20.1-2
20.1-3
Modules Supported by the T1, E1 and Optical Extension Cards .............................. 20.1-3
T1 PRI Card Configuration Parameters and Options ............................................... 20.1-6
E1 PRI Card and Optical Extension Card
Configuration Parameters and Options .............................................................. 20.1-9
MPA Card Configuration Parameters and Options ................................................. 20.1-12
TTC2M Card Configuration Parameters and Options ............................................. 20.1-14
X.21 and V.35 PRI Card Configuration Parameters and Options ........................... 20.1-15
DS-3 and DS-3 II Card Configuration Parameters and Options ............................. 20.1-17
E3 Card Configuration Parameters and Options .................................................... 20.1-19
20.1-4
20.1-5
20.1-6
20.1-7
20.1-8
Table of Contents
(400)
lxxiii
Table of Contents

NNP 95-2035-01-00-B
20.2-1
20.2-2
Application Modules Supported by PRI Cards .......................................................... 20.2-2

ISDN Link Default Configuration ............................................................................... 20.2-2
20.3-1
Super-rate Timeslot-to-Circuit Correlation ................................................................ 20.3-4
20.4-1
20.4-2
VCM Requirements .................................................................................................. 20.4-2

Restrictions on Transitional Signalling Connections ................................................. 20.4-7
20.6-1
20.6-2
20.6-3
20.6-4
T1 and DS-3 Card Framing Options ......................................................................... 20.6-1

E1 and E3 Card Framing Options ............................................................................. 20.6-4
Timeslot-to-Circuit Designation for E1 and E3 Cards ............................................... 20.6-5
E1 and E3 Card Super-rate Connections and Frame Types .................................... 20.6-6
20.8-1
Zero Code Suppression Options .............................................................................. 20.8-1
20.9-1
20.9-2
20.9-3
20.9-4
20.9-5
20.9-6
Aggregate Interface Card Trunk Conditioning .......................................................... 20.9-1

One-way Trunk Conditioning Link Faults .................................................................. 20.9-3
One-way Trunk Conditioning Signalling and Information Path Codes ...................... 20.9-4
Two-way Trunk Conditioning Signalling and Information Path Codes ...................... 20.9-5
Fault Class Descriptions for PRI Cards .................................................................... 20.9-9
Configuring Fault Classes for PRI Cards ................................................................ 20.9-10
20.10-1
20.10-2
Fault Signalling for PRI Cards ................................................................................ 20.10-2

Fault Signalling Codes OOS A, B and C for PRI Cards .......................................... 20.10-3
20.11-1
Fault Signalling Codes Seized and Idle for PRI Cards ........................................... 20.11-2
20.12-1
20.12-2
20.12-3
20.12-4
PRI Signalling Types .............................................................................................. 20.12-2

Compatible PRI Signalling Types ........................................................................... 20.12-3
Signalling Conversion Table for the TTC2M Card .................................................. 20.12-9
TTC2M Card Frame Format ................................................................................. 20.12-10
20.13-1
TTC2M Card Circuit Inversion Types ..................................................................... 20.13-2
20.14-1
20.14-2
20.14-3
PRI Loopback Detection ......................................................................................... 20.14-1

PRI CPSS Connections .......................................................................................... 20.14-3
CPSS Resources and Connection Types ............................................................... 20.14-3
20.17-1
20.17-2
Performance Threshold Statistics and Threshold Ranges ..................................... 20.17-5

Dual T1 and Dual T1-2 Card SES Threshold Configuration ................................... 20.17-7
20.18-1
20.18-2
20.18-3
20.18-4
20.18-5
20.18-6
20.18-7
E1 and E3 Card Parameters ................................................................................... 20.18-1

E3 NU Bits .............................................................................................................. 20.18-2
Threshold Selection ................................................................................................ 20.18-5
SA4 and BER Alarm Options .................................................................................. 20.18-7
SA4-bit Error Thresholds ........................................................................................ 20.18-8
E-bit States for CRC4 Status Indication .................................................................. 20.18-9
Usage of Bits on TS0 ............................................................................................ 20.18-12
lxxiv
(400)
Table of Contents

NNP 95-2035-01-00-B
Table of Contents
20.19-1
20.19-2
20.19-3
20.19-4
X.21 and V.35 PRI Card Parameters ...................................................................... 20.19-1

Number of Circuits .................................................................................................. 20.19-2
Number of Circuits With Signalling ......................................................................... 20.19-3
Clock Inversion Settings for the X.21 PRI Card ...................................................... 20.19-7
20.20-1
20.20-2
20.20-3
20.20-4
20.20-5
First General Procedure Tasks ............................................................................... 20.20-1

MPA Card Optional Configuration Tasks ................................................................ 20.20-2
MPA Card Control Signals in DCE/DTE Modes ................................................... 20.20-12
MPA Card Interface Control Signal Correlations .................................................. 20.20-13
Default MPA Card Control Signal Configuration (DTE) ........................................ 20.20-13
21.1-1
21.1-2
21.1-3
21.1-4
21.1-5
21.1-6
21.1-7
21.1-8
21.1-9
4WTO Line Card Configuration Parameters and Options ........................................ 21.1-2

E&M Card Configuration Parameters and Options ................................................... 21.1-3
LGE Card Configuration Parameters and Options ................................................... 21.1-4
LGS Card Configuration Parameters and Options ................................................... 21.1-5
4WDX Channel Unit Configuration Parameters and Options ................................... 21.1-6
E&M Channel Unit Configuration Parameters and Options ...................................... 21.1-7
LGE Channel Unit Configuration Parameters and Options ...................................... 21.1-8
LGS Channel Unit Configuration Parameters and Options ...................................... 21.1-9
MRD Channel Unit Configuration Parameters and Options ................................... 21.1-11
21.2-1
21.2-2
E&M Channel Unit Variants ...................................................................................... 21.2-2

LGS Channel Unit Variants ....................................................................................... 21.2-2
21.3-1
21.3-2
21.3-3
21.3-4
21.3-5
E&M Signalling ......................................................................................................... 21.3-2

E&M Signalling Options ............................................................................................ 21.3-2
LGE and LGS Signalling ........................................................................................... 21.3-5
LGE and LGS Signalling Options ............................................................................. 21.3-6
4WDX Signalling ....................................................................................................... 21.3-9
21.5-1
21.5-2
21.5-3
21.5-4
21.5-5
21.5-6
21.5-7
21.5-8
TLP Levels and Line Impedance for 4WTO Line Card ............................................. 21.5-2
TLP Levels and Line Impedance for E&M Cards ...................................................... 21.5-2
TLP Levels and Line Impedance for LGE Cards ...................................................... 21.5-3
TLP Levels and Line Impedance for LGS Cards ...................................................... 21.5-4
TLP Levels and Line Impedance for E&M Channel Units ......................................... 21.5-5
TLP Levels and Line Impedance for LGE and LGS Channel Units .......................... 21.5-5
TLP Levels and Line Impedance for the 4WDX Channel Unit .................................. 21.5-6
TLP Levels and Line Impedance for MRD Channel Units ........................................ 21.5-6
21.6-1
Line Impedance Options ........................................................................................... 21.6-1
21.7-1
Balanced Impedance for E&M/LGS Channel Units .................................................. 21.7-2
21.10-1
Loop Balance Options for the 4WDX Channel Unit ................................................ 21.10-1
21.11-1
Equalization Options for the 4WDX Channel Unit .................................................. 21.11-1
22.1-1
22.1-2
22.1-3
22.1-4
22.1-5
DNIC, 2B1Q and 27LC2 Line Card Functions .......................................................... 22.1-2

2600 MainStreet Series DTU Types ......................................................................... 22.1-2
2700 MainStreet Series DTU Types ......................................................................... 22.1-3
64 kb/s Codirectional Card Functions ....................................................................... 22.1-4
DCC and Line Card Configuration Process .............................................................. 22.1-6
Table of Contents
(400)
lxxv
Table of Contents

NNP 95-2035-01-00-B
22.1-6
22.1-7
22.1-8
22.1-9
22.1-10
22.1-11
22.1-12
DCC Configuration Parameters and Options ............................................................ 22.1-8

Line Card Configuration Parameters and Options .................................................. 22.1-12
64 kb/s Codirectional Card Configuration Parameters and Options ....................... 22.1-15
DS0-DP Channel Unit Configuration Parameters and Options .............................. 22.1-16
OCU-DP Channel Unit Configuration Parameters and Options ............................. 22.1-17
4WTO Channel Unit Configuration Parameters and Options ................................. 22.1-17
2B1Q Channel Unit Configuration Parameters and Options .................................. 22.1-18
22.3-1
22.3-2
22.3-3
22.3-4
22.3-5
22.3-6
22.3-7
22.3-8
22.3-9
22.3-10
Control Signals ......................................................................................................... 22.3-4

Control Signal Input and Output Defaults ................................................................. 22.3-6
Transmit Clock Options ............................................................................................ 22.3-9
RS-422 DCC Clocking Configurations .................................................................... 22.3-11
DCC/DTU Clocking ................................................................................................. 22.3-12
Valid Super-rate Interface Speed Rules ................................................................. 22.3-19
Super-rate Circuit Speed Configuration .................................................................. 22.3-20
Line Cards and DTUs Supporting Super-rate Connections .................................... 22.3-23
Target Circuit Connection Requirements ................................................................ 22.3-24
Port Activity Check Failures .................................................................................... 22.3-27
22.4-1
22.4-2
Data Interface Circuit Parameters and Rate Adaption .............................................. 22.4-1

Rate Adaption, SRM and Branch Channel Parameters ............................................ 22.4-2
23.1-1
23.1-2
23.1-3
23.1-4
DSP Card and IMC Applications ............................................................................... 23.1-1

DSP Card Configuration Parameter and Options ..................................................... 23.1-3
DSP Card Connection Types .................................................................................... 23.1-7
IMC Configuration Parameter and Options ............................................................... 23.1-8
23.3-1
E1 and T1 Signalling Types ...................................................................................... 23.3-2
23.6-1
23.6-2
23.6-3
23.6-4
23.6-5
23.6-6
23.6-7
23.6-8
23.6-9
23.6-10
23.6-11
23.6-12
23.6-13
23.6-14
Data Card Interface Speeds for DDS Rate Adaption ................................................ 23.6-7
X.50 Division 2 Phases and Frames ....................................................................... 23.6-12
X.50 DSP Applications ............................................................................................ 23.6-14
Transparent and HCM SRM Support ...................................................................... 23.6-22
DDS SRM Support .................................................................................................. 23.6-23
X.50 and X.50 Telco SRM Support ......................................................................... 23.6-23
Transport Bandwidth and Transport Position for
Transparent Rate Adaption .............................................................................. 23.6-38
End-to-End H-bit Signalling Configurations ............................................................ 23.6-40
HCM Interface Speeds ........................................................................................... 23.6-41
X.50 Interface Speeds ............................................................................................ 23.6-42
Valid Subframe Positions for DDS .......................................................................... 23.6-44
Valid Subframe Positions for X.50 .......................................................................... 23.6-44
Configuration Process ............................................................................................ 23.6-46
Rate Adaption and SRM Parameters ..................................................................... 23.6-47
23.7-1
Multidrop Bridge and MJU Configuration Process .................................................... 23.7-4
23.8-1
Possible Data Bandwidth Configurations .................................................................. 23.8-3
lxxvi
(400)
Table of Contents

NNP 95-2035-01-00-B
Table of Contents
23.9-1
23.9-2
23.9-3
23.9-4
SRS Display Symbol Definitions ............................................................................... 23.9-3

Configuration Process .............................................................................................. 23.9-4
Set Identifiers for DDS and X.50 ............................................................................... 23.9-5
SRS Circuit Format Conversions ............................................................................ 23.9-10
23.12-1
Applications Eligible for Use in Combined Operations ........................................... 23.12-1
24.1-1
DCP Card Configuration Parameter and Options ..................................................... 24.1-1
25.1-1
25.1-2
25.1-3
25.1-4
25.1-5
25.1-6
Frame Relay Platforms ............................................................................................. 25.1-1

FRS, FRE and PE Card DLCs and DLCIs ................................................................ 25.1-3
FRS, FRE and PE Card Congestion Thresholds ...................................................... 25.1-6
Link Management Protocols ................................................................................... 25.1-13
Additional Configurable Frame Relay Parameters ................................................. 25.1-15
FRS, FRE and PE Card Configuration Parameters and Options ........................... 25.1-15
25.3-1
Frame Switch Configuration Fields ........................................................................... 25.3-3
25.4-1
25.4-2
FASTbus Station Status Fields ................................................................................. 25.4-4

FASTbus Parameters ............................................................................................... 25.4-6
25.5-1
FRS, FRE and PE Card Bandwidth and Circuits ...................................................... 25.5-2
25.6-1
25.6-2
Frame Stream Status Fields ..................................................................................... 25.6-2

Frame Stream Notification Configuration Fields ....................................................... 25.6-4
25.7-1
25.7-2
25.7-3
25.7-4
Available DLCs and DLCIs ....................................................................................... 25.7-2

DLC Status Display Fields ........................................................................................ 25.7-3
Local DLC Connection Rules .................................................................................... 25.7-5
FASTbus DLC Connection Rules ............................................................................. 25.7-9
25.8-1
Class-of-Service Configuration Fields ...................................................................... 25.8-4
25.9-1
25.9-2
25.9-3
25.9-4
25.9-5
25.9-6
25.9-7
Subrate Speeds and Protocols ................................................................................. 25.9-1

SRIM Configurable Parameters ................................................................................ 25.9-2
Circuit Configuration Parameters .............................................................................. 25.9-6
DDS Subframe Positions .......................................................................................... 25.9-6
Stream Configuration Parameters ............................................................................ 25.9-8
Interface Speeds ....................................................................................................... 25.9-8
DDS and X.50 Subframe Positions ........................................................................... 25.9-9
25.10-1
25.10-2
25.10-3
25.10-4
Packet and Frame Sizes for Annex G .................................................................... 25.10-3

Packet and Frame Sizes for RFC 1490 .................................................................. 25.10-4
Encapsulation Circuit Information Fields ................................................................ 25.10-7
Configurable Encapsulation Circuit Parameters ..................................................... 25.10-8
25.11-1
Support for T1 Signalling Termination .................................................................... 25.11-3
26.2-1
26.2-2
Network Layer Protocol Timers ................................................................................ 26.2-6

Link Layer Timers and Counters ............................................................................... 26.2-7
26.3-1
User Screening ......................................................................................................... 26.3-5
Table of Contents
(400)
lxxvii
Table of Contents

NNP 95-2035-01-00-B
26.5-1
26.5-2
Error and Caution Messages for Routing ................................................................. 26.5-3

Cause Values for Call Clearing ................................................................................. 26.5-6
27.2-1
27.2-2
27.2-3
27.2-4
27.2-5
Rules From Table 6-1 in Recommendation X.25 .................................................... 27.2-11

Rules From Table 6-2 in Recommendation X.25 .................................................... 27.2-11
Scenarios Where the Network Avoids Segmenting and Combining Packets ......... 27.2-12
Scenarios Where the Network Segments and Combines Packets ......................... 27.2-12
Possible Packet Size Combinations When Neither DTE Subscribes to
Flow Control Negotiation .................................................................................. 27.2-14
Possible Packet Size Combinations When the Calling DTE Subscribes to
Possible Packet Size Combinations When the Called DTE Subscribes to
Possible Packet Size Combinations When Both the Calling and
Called DTEs Subscribe to Flow Control Negotiation ........................................ 27.2-20
27.2-6
27.2-7
27.2-8
27.3-1
27.3-2
27.3-3
Compliance to X.2 (1988) ......................................................................................... 27.3-1

Compliance to X.2 (1992) ......................................................................................... 27.3-3
Compliance to X.35 (1993) ....................................................................................... 27.3-7
27.4-1
27.4-2
27.4-3
27.4-4
27.4-5
27.4-6
27.4-7
27.4-8
27.4-9
27.4-10
27.4-11
27.4-12
27.4-13
PE and X.25 FRE NMTI Identifiers ........................................................................... 27.4-3

How Configuration Information is Organized ............................................................ 27.4-4
X.25 Switch-wide Parameters ................................................................................... 27.4-6
GFR Parameters ....................................................................................................... 27.4-6
Trunk Circuit Parameters .......................................................................................... 27.4-6
NUI Server Agent Parameters .................................................................................. 27.4-7
XAC Link Layer Parameters ..................................................................................... 27.4-7
XAC Network Layer Parameters ............................................................................... 27.4-7
XFR Service Interworking ......................................................................................... 27.4-9
XAC Address Translation and Screening Parameters .............................................. 27.4-9
NUA Parameters ..................................................................................................... 27.4-10
X.25 PVC Parameters ............................................................................................ 27.4-12
Hunt Group Parameters .......................................................................................... 27.4-12
27.5-1
X.25 Global Switch Resources ................................................................................. 27.5-3
27.6-1
27.6-2
27.6-3
Forwarding Table for Hub 10-0 ............................................................................... 27.6-13

GFR Address Assignment ...................................................................................... 27.6-18
Alias Assignment .................................................................................................... 27.6-21
27.7-1
Example of How Weights Are Used .......................................................................... 27.7-7
27.8-1
Packet and Frame Size Dependencies .................................................................... 27.8-2
27.10-1
27.10-2
27.10-3
X.25 and X.75 Accounting Record Fields ............................................................. 27.10-11

Time Change Record ............................................................................................ 27.10-15
Accounting Generation Parameters ...................................................................... 27.10-16
27.11-1
Data Collector Agent Parameters ........................................................................... 27.11-4
lxxviii
(400)
Table of Contents

NNP 95-2035-01-00-B
Table of Contents
27.13-1
27.13-2
27.13-3
27.13-4
Packet and Frame Sizes for Annex G .................................................................... 27.13-3

Packet and Frame Sizes for RFC 1490 .................................................................. 27.13-4
Encapsulation Circuit Information Fields .............................................................. 27.13-10
Packet and Frame Size Dependencies for Annex G ............................................ 27.13-12
27.14-1
27.14-2
27.14-3
27.14-4
27.14-5
Network Layer Timers ........................................................................................... 27.14-10

External and Internal Address Formats ................................................................ 27.14-30
Typical X.121 Address Translation Example ........................................................ 27.14-33
Examples of the Address Translation Process ..................................................... 27.14-34
Address Translation Examples ............................................................................. 27.14-36
27.16-1
Formats for Copying XAC Values ........................................................................... 27.16-1
27.17-1
Remotely-Switched PVC Configuration Example ................................................... 27.17-6
27.20-1
XFR NUA Parameters .......................................................................................... 27.20-13
28.1-1
28.1-2
28.1-3
28.1-4
28.1-5
Diagnostic Code Mapping for Clear Request Packet ............................................. 28.1-10

X.75 Link Layer Parameters ................................................................................... 28.1-11
X.75 Network Layer Parameters ............................................................................. 28.1-12
X.75 Address Translation Parameters .................................................................... 28.1-13
X.75 NUA Parameters ............................................................................................ 28.1-14
29.1-1
29.1-2
BRI S/T Card Configuration Parameters and Options for

Non-ISDN Applications ....................................................................................... 29.1-3
BRI S/T Card Configuration Parameters and Options for ISDN Applications ........... 29.1-4
29.3-1
BRI S/T Channel Connections ................................................................................ 29.3-11
30.1-1
CPC Card Configuration Parameters and Options ................................................... 30.1-1
30.4-1
CPC Index Table with Defined Hunt Groups ............................................................ 30.4-3
31.1-1
31.1-2
SONET STS-n and SDH STM-n Line Rates ............................................................. 31.1-2

VT and TU Line Rates .............................................................................................. 31.1-2
31.2-1
HSA Card Configurable Parameters ......................................................................... 31.2-1
31.4-1
31.4-2
1+1 Protection Card and Line Faults ........................................................................ 31.4-6

Protection Switching Options .................................................................................. 31.4-10
31.7-1
Signal Label Options ................................................................................................. 31.7-2
31.9-1
31.9-2
Valid Broadband Circuit Connections ....................................................................... 31.9-1

Circuit Connection Display Symbols ......................................................................... 31.9-2
31.11-1
Zero Code Suppression Options ............................................................................ 31.11-1
31.12-1
31.12-2
31.12-3
31.12-4
One-way Trunk Conditioning Link Faults ................................................................ 31.12-2

One-way Trunk Conditioning Signalling and Information Path Codes .................... 31.12-3
Two-way Trunk Conditioning Signalling and Information Path Codes .................... 31.12-4
Fault Class Descriptions for Mapper Cards ............................................................ 31.12-7
Table of Contents
(400)
lxxix
Table of Contents

NNP 95-2035-01-00-B
31.12-5
Configuring Fault Classes for Mapper Cards .......................................................... 31.12-8
31.13-1
Timeslot-to-Circuit Designation for TU-12 Cards .................................................... 31.13-3
31.14-1
31.14-2
Fault Signalling for PRI Cards ................................................................................ 31.14-1

Fault Signalling Codes OOS A, B and C for PRI Cards .......................................... 31.14-2
31.15-1
31.15-2
Mapper Card PRI Signalling Types ........................................................................ 31.15-1

Compatible Mapper and PRI Card Signalling Types .............................................. 31.15-2
31.18-1
Usage of Bits on TS0 .............................................................................................. 31.18-2
31.19-1
Fault Signalling Codes Seized and Idle for VT-1.5 and TU-12 Cards .................... 31.19-2
31.20-1
CPSS Resources and Connection Types ............................................................... 31.20-2
lxxx
(400)
Table of Contents

NNP 95-2035-01-00-B
Foreword
Foreword
The Foreword outlines the systems and services described in the 3600 MainStreet
Bandwidth Manager Family Technical Practices, and lists the software generics that
support these systems and services. It briefly describes what is contained in each
volume of the Technical Practices and the special text conventions used, and
provides a list of suggested reading material.
System Support
This release of the 3600 MainStreet Bandwidth Manager Family Technical Practices
provides information required for the installation, operation and configuration, and
maintenance of the systems and services listed in Table 1.
Table 1: System and Services Support
Release (1)
System or Service
Software Generic
3600 MainStreet Bandwidth Manager
7.0 F
1117
3600+ MainStreet Bandwidth Manager
7.0 F
S1117
3645 MainStreet High Capacity Bandwidth

Manager
7.0 F
C117/D117/H117/E117
3664 MainStreet Fractional Access

Multiplexer
7.0 F
Q117
36120 MainStreet Packet Transfer

Exchange, locally controlled system
7.0 F
1117
36120 MainStreet Packet Transfer

Exchange, switching shelf controlled
system
7.0 F
C117/D117/H117/E117
36120 MainStreetFrame Relay service
3.0 H
P412 (FRE card)

P114 (FRS card)
36120 MainStreet X.25 service
1.2 F
PA11 (X.25 FRE card)

P611 (PE card)
Notes
1. H indicates hardened product release.
F indicates field trial release.
(400)
lxxxi
Foreword

NNP 95-2035-01-00-B
Feature support
Some systems do not have all the components and features described in the
Technical Practices. The components and features that Newbridge supports are
determined by the type of system, the revision level of the installed cards, the generic
release of the installed system software, and the generic release of the Craft Interface,
4601 MainStreet Network Manager, 4601A MainStreet Auxiliary Network Manager,
4602 MainStreet Intelligent NetworkStation or MainStreetXpress 46020 Network
Manager software in use. If a feature is configured for an installed card that does not
support the feature, the card or affected circuit is busied out and a revision/feature
mismatch alarm is raised for that slot. For information on alarms, see Maintenance.
Node management
The node management procedures described in the Technical Practices are done
through a node management session initiated from any of the 4601 MainStreet
Network Manager, 4601A MainStreet Auxiliary Network Manager, 4602 MainStreet
Intelligent NetworkStation or MainStreetXpress 46020 Network Manager, the Craft
Interface node manager or an ASCII (VT100-type) terminal.
If you are using a 4601 MainStreet Network Manager, 4601A MainStreet Auxiliary
Network Manager, 4602 MainStreet Intelligent NetworkStation or MainStreetXpress
46020 Network Manager, see the appropriate documentation for instructions on
how to install and commission your network manager and how to manage your
node. The 4601 MainStreet Network Manager, 4601A MainStreet Auxiliary Network
Manager, 4602 MainStreet Intelligent NetworkStation or MainStreetXpress 46020
Network Manager documentation refers to the Technical Practices when necessary.
If you are using the Craft Interface, refer to your Craft Interface documentation for
instructions on how to install and commission your node manager. Refer to the
Technical Practices for instructions on how to manage your node.
If you are using an ASCII terminal, see Technical Overview for instructions on how to
install and commission your node management terminal. See the remainder of the
Technical Practices for instructions on managing your node.
Technical Practices Contents

The following subsections describe the contents of the Technical Practices.
Technical Overview
Technical Overview provides an introduction to the MainStreet family of bandwidth
managers.
Installation
Installation provides the procedures required to install all 3600 MainStreet series
bandwidth manager systems.
lxxxii
(400)

NNP 95-2035-01-00-B
Foreword
Operations and Configuration

Operations and Configuration provides the procedures to configure system and
interface operating parameters, one- and two-way connections, and redundancy.
Maintenance
Maintenance provides the procedures required to monitor system operation, isolate
faults, service failed components, and perform system upgrades.
Reference documents
It is recommended that you read the following documents:
MainStreet Craft Interface node manager documentation

4601 MainStreet Network Manager, 4601A MainStreet Auxiliary Network
Manager, 4602 MainStreet Intelligent NetworkStation and MainStreetXpress

46020 Network Manager documentation
2600 MainStreet series DTU and 2700 MainStreet series DTU Data Termination
Unit documentation
distribution panel installation documentation
Conventions
This section describes the text conventions used throughout the Technical Practices.
Special information
These conventions are used to draw your attention to special information:
Danger
Danger means that the described activity or situation may cause personal injury.
Warning
A warning means that the described activity or situation may or will cause
equipment damage.
(400)
lxxxiii
Foreword

NNP 95-2035-01-00-B
Caution
A caution means that the described activity or situation may or will cause service
interruption.
Note
A note provides special information.
Table entry conventions

Table 2 lists the conventions used to describe node management session operations
and procedures.
Table 2: Node Management Session Documentation Conventions
Convention
Description
Example
<Key>
Indicates a particular keyboard character.
<Esc>
<variable>
Indicates that you enter an allowable value represented by

the variable.
<sn>
<LITERAL>
Indicates that you enter the string exactly as it appears.
<CPSS>
Step procedure conventions

Step procedures provide instructions to perform a task. Step procedures may consist
of options and substeps. The following example outlines step procedure
conventions.
1.
2.
Steps are denoted by arabic numerals and describe actions that must be
performed. Complete each step in order. This step has substeps.
i.
Substeps are denoted by roman numerals and detail the actions involved
in a complex step. Complete each substep in order.
ii.
At least two substeps appear.
This step has options.

a.
lxxxiv
Options are denoted by letters and are conditional actions that depend on
your system requirements. Perform only the applicable option.
i.
Options may contain substeps.
ii.
At least two substeps appear.
(400)

NNP 95-2035-01-00-B
Foreword
Softkey tree conventions

In the Technical Practices, a series of softkey selections and keyboard entries is
shown in a tree form. The tree begins with a single line containing selections and
entries with long dashes between them. The return key is shown as . When you
have a choice between two different keys, the tree branches into a second line.
Further choices result in further branches.
Softkey tree example

CONFIG SLOT <sn> TYPE VOICE E+M
MuLaw*
ALaw
SK000002
Asterisks (*) in the tree show default values for softkeys.
(400)
lxxxv

NNP 95-2035-01-00-B
16. Getting Started

NNP 95-2035-01-00-B
16.1
16.1 How to Use Operations and Configuration

How to Use Operations and

Configuration
This chapter describes:
who should use this manual

how the manual is organized
conventions used in the manual
16.1.1
Who Should Use this Manual

This manual provides the procedures required to configure system and interface
operating parameters, one- and two-way connections and redundancy options for
the 3600 MainStreet series bandwidth managers.
This manual is intended for people responsible for system configuration and
day-to-day operation. Before using the manual, you should be:
familiar with the Technical Overview

trained to telephone company standards (or equivalent)
16.1.2
How the Manual is Organized

The manual is organized into the following volumes.
Getting Started
Explains how to use the manual, how to run a node management session and how
to display information about the system configuration.
Node Parameters
Explains how to configure parameters that apply to a node as a whole, or to all the
cards installed in the system; explains general circuit connections, CPSS
configuration and network synchronization.
Redundancy
Explains how to configure control redundancy, protection switching and PRI
redundancy.
Getting Started
(400)
16.1-1


NNP 95-2035-01-00-B
System Cards
Describes the system cards and provides configuration procedures for the Control,
Expander, Switching, Common Carrier, Test and General Facilities cards.
PRI Cards
Describes the PRI cards and explains how to configure T1, E1, MPA, TTC2M, X.21
PRI, X.21 ESI PRI, V.35 PRI, DS-3 and E3 cards.
Voice Interface Cards

Describes the voice interface cards and provides the configuration procedures for
4WTO Line card, E&M, LGE and LGS cards, and 4WDX, E&M, LGE, LGS and MRD
channel units.
Data Interface Cards

Describes super-rate and rate adaption applications and explains how to configure
DCCs, DNIC, 2B1Q and 27LC2 Line cards, 64 kb/s Codirectional cards, DS0-DP and
OCU-DP, 4WTO and 2B1Q channel units.
DSP Cards and IMCs

Describes special applications (such as voice compression, echo cancellation,
multidrop data bridges, VCBs and fax-to-voice conversion) and SRS and explains
how to configure DSP cards and IMCs.
DCP Cards
Describes DCP cards and explains how to configure them.
Frame Relay Services

Describes frame relay switching and explains how to configure the FRS, FRE and PE
cards.
36120 MainStreet X.25 Service

Describes the 36120 MainStreet X.25 service and explains how to configure the PE
and X.25 FRE cards.
BRI S/T Cards

Describes ISDN and non-ISDN applications for the card and explains how to
configure BRI S/T cards.
16.1-2
(400)
Getting Started

NNP 95-2035-01-00-B

CPCs
Describes the ISDN backup application and explains how to configure CPCs.
HSA Cards
Describes the SONET and SDH applications and explains how to configure HSA
cards.
Note
For instructions on trouble shooting, viewing alarms, using the GFC, GFC2, GFC3
and Test cards and servicing failed components, see Maintenance.
Getting Started
(400)
16.1-3

NNP 95-2035-01-00-B
16.2
16.2 Running a Node Management Session

Running a Node Management

Session
This chapter describes how to communicate with 3600 MainStreet series bandwidth
managers through a node or network management station session. It also describes
how to connect a management station to a system serial port.
16.2.1
Understanding Node Management Sessions

A node management session is the time in which you use the menu-driven user
interface to communicate with 3600 MainStreet series bandwidth managers. You can
access a session from an ASCII (VT100) terminal or a MainStreet network or node
management station connected to a MainStreet system serial port (directly or
through modems). This user interface, also called the NMTI, is used to do the
configuration, operation and maintenance procedures described in the 3600
MainStreet Bandwidth Manager Family Technical Practices.
Note
The 3645 MainStreet node supports NMTI circuit connection management through
ASCII (VT100) terminals. Prior to Release 7.0, circuit connections could only be
configured for 3645 MainStreet systems through a Craft Interface session.
All MainStreet functions are software-driven and all configurable parameters are
stored in a non-volatile configuration database. You can access all functions and
parameters during a node management session by reading from and writing to the
configuration database. A node management session is conducted using the CPSS
protocol. CPSS is Newbridges proprietary X.25-based management protocol (for
more information on CPSS, see chapter 17.6).
Figure 16.2-1 shows the nodes with which you can have a node management session.
Getting Started
(400)
16.2-1


NNP 95-2035-01-00-B
Figure 16.2-1: Node Management Session Nodes
Switching
shelf
Control card in active shelf

Control card in inactive shelf
Active Control card
Node
management
session
Locally controlled
switching shelf
Inactive Control card

FRS, FRE card
High speed
peripheral shelf
Active DS-3/E3 card

Inactive DS-3/E3 card
4759
For the purposes of node management, a node is defined as anything with a

configuration database. There are two kinds of nodes:
major nodes
minor nodes
Major nodes
The major nodes are:
Control cards
HSPS DS-3 or DS-3II cards
HSPS2 SE3 and DE3 cards
A major node is assigned a CPSS address. The configuration database of a locally
controlled, enhanced locally controlled or peripheral shelf contains all system and
card-specific parameters and functions for all cards installed in the shelf (except for
minor nodes). The configuration database of a switching shelf Control card contains
all DCS connections configured for all the peripheral shelves, HSPSs and HSPS2s
connected to it. Each HSPS and HSPS2 card configuration database contains all
system and card-specific parameters required by the card.
16.2-2
(400)
Getting Started

NNP 95-2035-01-00-B

Minor nodes
The minor nodes are:
CPC
DCC
DCP card
DSP5 and DSP5H cards
DTUs
Dual E1 card
Dual E1-2 card
Dual T1 card
Dual T1-2 card
FRE card
FRS card
MPA card
PE card
A minor node does not have a CPSS address. It is identified by the CPSS address of
the major node and by the slot it occupies in the major node. The configuration
database of a minor node includes all card-specific parameters and functions. All
general system parameters are configured through a node management session with
the major node.
Active and inactive nodes

For control-redundant switching shelves, you can initiate a node management
session with the active or inactive locally controlled or peripheral shelf Control card.
For control-redundant locally controlled, enhanced locally controlled or peripheral
shelves, you can initiate a node management session with the active or inactive
locally controlled, enhanced locally controlled or peripheral shelf Control card.
For HSPS or HSPS2 cards configured as redundant card pairs, you can initiate a
node management session with the active or inactive HSPS or HSPS2 card.
Any configuration change you make during a node management session with the
active card is applied to the system immediately. Any configuration change you
make in a session with the inactive card is applied when an activity switch occurs.
For more information on activity switches, see chapter 18.1. Configuration options
are limited for an inactive 3600+ MainStreet Control card that is in hot standby mode.
Getting Started
(400)
16.2-3

16.2.2

NNP 95-2035-01-00-B
Management Stations
You can initiate a node management session from any of the following management
stations:
4602 MainStreet Intelligent NetworkStation

MainStreetXpress 46020 Network Manager
4601 MainStreet Network Manager
Craft Interface
ASCII (VT100) terminal
You can do all configuration and operation procedures in a node management

session initiated from the 4601 MainStreet Network Manager, 4602 MainStreet
Intelligent NetworkStation, MainStreetXpress 46020 Network Manager or Craft
Interface. Node management sessions initiated from an ASCII (VT100) terminal can
not support software downloading or database backup and restore functionality.
Network managers
The network managers are the preferred tools for network management and remote
node management. The 4602 MainStreet Intelligent NetworkStation,
MainStreetXpress 46020 Network Manager and 4601 MainStreet Network Manager
are network managers. They are connected to the network to manage the network
and any node on the network.
The 4602 MainStreet Intelligent NetworkStation and MainStreetXpress 46020
Network Manager are Sun-based software programs designed for large networks.
They can configure and operate all 3600 MainStreet series bandwidth managers and
provide an advanced graphical user interface in addition to the NMTI. The graphical
user interface is used to simplify network and node configuration and operation
procedures. You can do all configuration and operation procedures through the
NMTI.
The 4601 MainStreet Network Manager is a PC-based software program designed
for small- to medium-sized networks; it can configure and operate all
3600 MainStreet series bandwidth managers. It provides a graphic user interface to
simplify connections to remote nodes. You can do all configuration and operation
procedures through the NMTI.
If you are using a network manager, see the appropriate network management
documentation to install and commission your network manager and manage your
node. The network management documentation describes how to initiate a node
management session with a node and refers you to the 3600 MainStreet Bandwidth
Manager Family Technical Practices when necessary.
Craft Interface node manager

The Craft Interface is the preferred tool for local node management. It is connected
(usually by a direct physical connection) to a single node for the purpose of
managing that node only. (When used with a switching shelf controlled system, the
Craft Interface is always connected to the switching shelf.)
16.2-4
(400)
Getting Started

NNP 95-2035-01-00-B

The Craft Interface is a PC-based software program designed for node installation
and initial configuration or on-site trouble shooting. It provides NMTI access to all
MainStreet nodes (major and minor). You can do all configuration and operation
procedures through the Craft Interface.
If you are using the Craft Interface, see your Craft Interface documentation to install
and commission your node manager and to initiate a node management session. See
the 3600 MainStreet Bandwidth Manager Family Technical Practices to manage your
node.
ASCII (VT100) terminal

Any ASCII (VT100) terminal (or PC-based terminal emulation software) can be used
to initiate a node management session with the Control, FRS, FRE or PE card. All
other nodes (major and minor) require the Craft Interface, 4601, 4602 or 46020
network manager. Node management session initiated from an ASCII (VT100)
terminal can not support software downloading or database backup and restore
functionality.
The ASCII terminal should be configured for:
eight data bits

one stop bit
no parity
no local echo
9600 baud
The 3600+ MainStreet system has the automatic baud rate matching feature enabled
by default. For information about setting the baud rate, see chapter 17.3.
Getting Started
(400)
16.2-5

16.2.3

NNP 95-2035-01-00-B
Connecting to System Serial Ports

You can connect a management station to one of two RS-232 ALAPB system serial
ports. As indicated in Table 16.2-1, the ports are accessible on the backplane or
bulkhead of all MainStreet systems and on the faceplates of some cards.
SP1 is a simple 3-wire interface that supports TxD, RxD and GND. SP2 supports the
CTS or RTS and DSR or DTR control leads, and TxD, RxD and GND.
To connect external devices to either of the system serial ports, use the DCE and DTE
connection types as listed in Table 16.2-2.
Note
Hardware flow control is supported on SP2 only. For SP1 only, RTS is connected to
CTS and DTR is connected to DSR by the backplane.
Table 16.2-1: System Serial Ports

System
SP1
SP2
Connector
Type
Figure
Class A locally controlled shelf
RJ45
16.2-2
Class A switching shelf
RJ45
16.2-3
Class B or 23-inch locally controlled shelf
DB25
(female)
16.2-4
Class B or 23-inch switching shelf
DB25
(female)
16.2-5
RJ45
16.2-9
Backplane Location
Bulkhead Location
Faceplate Location
16.2-6
Control cards
CPC
RJ45
16.2-6
DCP card
RJ45
16.2-7
DS-3 II card
RJ45
16.2-8
E3 card
RJ45
16.2-8
FRE and PE cards
RJ45
16.2-8
FRS card
RJ45
16.2-6
(400)
Getting Started

NNP 95-2035-01-00-B

Table 16.2-2: Serial Port Device Connections

Connection
Connection Type
From SP1(DCE) to device (DTE)
Normal (straight through)
From SP2 (DTE) to device (DTE)
Null modem
From SP1 (DCE) to device (DCE)
Null modem
From SP2 (DTE) to device (DCE)
Normal (straight through)
Card faceplate serial ports

You can also access SP1 from the Control card faceplate to initiate a node
management session with the active or inactive Control card. Only one of the two
serial ports (backplane or bulkhead or Control card faceplate) in a system is active at
a time.
For the 3600, 3645, 3664 and 36120 MainStreet Control cards, serial port availability
depends on the system configuration (see Table 16.2-3).
Table 16.2-3: Control Card and Backplane or Bulkhead Serial Ports
Shelf
Backplane or
Bulkhead Serial
Port 1
Single- or dual-shelf, non-control-redundant

system
Control Card
Faceplate Serial
Port
Class A
Class B
Class A
Class B
(1)
(1)
Inactive
Inactive
Active
Active
Single-shelf, control-redundant system
Active
Active
Inactive
Inactive
Shelf with the active Control card in dual-shelf,

control-redundant system
Active
Active
Inactive
Inactive
Inactive
Inactive
Active
Active
Shelf with the inactive Control card in dual-shelf,

control-redundant system)
Notes
1. In a dual-shelf, non-control-redundant system, the Control card uses the backplane or bulkhead SP1
connector of the shelf in which it is installed. The backplane or bulkhead SP1 connector of the shelf
without a Control card is not used.
Note
For an NMTI session in a dual-shelf, control-redundant system, connect the
management station to backplane or bulkhead SP1 on both shelves using a Y-cable.
This ensures a connection to the active Control card no matter which shelf is the
active shelf.
Getting Started
(400)
16.2-7


NNP 95-2035-01-00-B
For the active 3600+ MainStreet Control card, insertion of jumper W4 enables SP1 on
the faceplate while disabling SP1 on the bulkhead. See chapter 17.3 for more
information about serial ports and W4 jumper insertion. Access to the inactive
Control card faceplate serial port is available only if W4 is inserted and the node
management station is directly connected.
Several other cards provide faceplate serial ports. These serial ports act as extensions
of the system serial ports in the active shelf only. They provide an alternate
connection point for a management station. Table 16.2-1 lists the system serial ports
supported on 3600 MainStreet series bandwidth manager systems and the pinout
figure number for each.
Default configuration
System serial ports have the default configuration listed in Table 16.2-4. Only port
type, CPSS cost and baud rate are configurable (see chapter 17.3).
Table 16.2-4: System Serial Port Configuration
Serial Port
Port Type (1)
CPSS
Cost
Data
Bits
Stop
Bits
Parity
Baud
Rate (2)
Gender (3)
VT100
Normal
None
9600
DCE
CPSS_MODEM
Normal
None
1200
DTE
Notes
1. Port type is configurable only on backplane or bulkhead and Control, DS-3 II and E3 card serial ports.
For most other card faceplate serial ports, port type is CPSS. For the CPC, port type is VT100.
2. For CPC and DCP faceplate serial ports, the default baud rate for both serial ports is 9600. For all
other faceplate serial ports, the default baud rates are as shown in the table.
3. For CPC, DCP, FRS, FRE and PE card faceplate serial ports, the gender of both serial ports is DCE.
For all other faceplate serial ports, the gender is listed in the table.
Pinouts
Figures 16.2-2 through 16.2-9 show the pinouts for all system serial ports.
16.2-8
(400)
Getting Started

NNP 95-2035-01-00-B

Figure 16.2-2: Serial Port Pinouts for a Class A Locally Controlled Shelf System
SP1
P5
P6
P7
P8
P9
P10
P11
P12
SP2
CTRL A
CTRL B
Serial port 1
(DCE)
Serial port 2
(DTE)
1
2
3
4
5
6
7
8
1
2
3
4
5
6
7
8
CTS
RTS
RXD
TXD
Signal GND
DTR
DSR
Chassis GND
CTS
RTS
RXD
TXD
Signal GND
DTR
DSR
Chassis GND
4798
Note
Getting Started
(400)
16.2-9


NNP 95-2035-01-00-B
Figure 16.2-3: Serial Port Pinouts for a Class A Switching Shelf System
SP1
SP2
J29A
J29B
J30A
J30B
Serial port 1
(DCE)
Serial port 2
(DTE)
1
2
3
4
5
6
7
8
1
2
3
4
5
6
7
8
CTS
RTS
RXD
TXD
Signal GND
DTR
DSR
Chassis GND
CTS
RTS
RXD
TXD
Signal GND
DTR
DSR
Chassis GND
4799
Note
Warning
Do not make connections to pins identified as n/c in Figure 16.2-4.
16.2-10
(400)
Getting Started

NNP 95-2035-01-00-B

Figure 16.2-4: Serial Port Pinouts for a Class B or 23-inch Locally Controlled or
Peripheral Shelf System
n/c
TXD
RXD
RTS
CTS
DSR
GND
n/c
n/c
n/c
n/c
n/c
n/c
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
n/c
n/c
n/c
n/c
n/c
n/c
DTR
n/c
n/c
n/c
n/c
n/c
n/c
TXD
RXD
RTS
CTS
DSR
GND
n/c
n/c
n/c
n/c
n/c
n/c
J16 Serial port 1 (DCE)

DB25 Female connector
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
n/c
n/c
n/c
n/c
n/c
n/c
DTR
n/c
n/c
n/c
n/c
n/c
J15 Serial port 2 (DTE)

Class B locally controlled

or peripheral shelf
23-inch Locally controlled

or peripheral shelf
4790
Note
Warning
Do not make connections to pins identified as n/c in Figure 16.2-5.
Getting Started
(400)
16.2-11


NNP 95-2035-01-00-B
Figure 16.2-5: Serial Port Pinouts for a Class B or 23-inch Switching Shelf System
n/c
TXD
RXD
RTS
CTS
DSR
GND
n/c
n/c
n/c
n/c
n/c
n/c
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
n/c
n/c
n/c
n/c
n/c
n/c
DTR
n/c
n/c
n/c
n/c
n/c
n/c
TXD
RXD
RTS
CTS
DSR
GND
n/c
n/c
n/c
n/c
n/c
n/c
J16 Serial port 1 (DCE)

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
n/c
n/c
n/c
n/c
n/c
n/c
DTR
n/c
n/c
n/c
n/c
n/c
J15 Serial port 2 (DTE)

Class B switching shelf
23-inch Switching shelf

4816
Note
Warning
Do not make connections to pins identified as n/c in Figures 16.2-6 through 16.2-9.
16.2-12
(400)
Getting Started

NNP 95-2035-01-00-B

Figure 16.2-6: Serial Port Pinout for CPC and FRS Card Faceplates
Serial port 1 (DCE)
Chassis GND
+12V
n/c
Signal GND
TXD
RXD
n/c
+12V
Serial port 2 (DTE)
8
7
6
5
4
3
2
1
Chassis GND
DSR
DTR
Signal GND
TXD
RXD
+12V
n/c
8
7
6
5
4
3
2
1
8022
Figure 16.2-7: Serial Port Pinout for DCP Card Faceplates

Serial port 1 (DCE)
Chassis GND
DSR
DTR
Signal GND
TXD
RXD
RTS
+12V
Serial port 2 (DCE)
8
7
6
5
4
3
2
1
Chassis GND
+12V
n/c
Signal GND
TXD
RXD
n/c
+12V
8
7
6
5
4
3
2
1
8021
Figure 16.2-8: Serial Port Pinout for DS-3, E3, FRE and PE Card Faceplates
Serial port 1 (DCE)
Chassis GND
+12V
n/c
Signal GND
TXD
RXD
n/c
+12V
8
7
6
5
4
3
2
1
8023
Getting Started
(400)
16.2-13


NNP 95-2035-01-00-B
Figure 16.2-9: Serial Port Pinout for Control Card Faceplates
Serial port 1 (DCE)

Chassis GND
DSR
DTR
Signal GND
TXD
RXD
RTS
+12V
8
7
6
5
4
3
2
1
9698
16.2-14
(400)
Getting Started

NNP 95-2035-01-00-B
16.3
16.3 Working with Node Management Sessions

Working with Node Management

Sessions
This chapter helps you become familiar with the following elements of the node
management session user interface:
screen layout
softkeys
keyboard entries
It also provides a sample node management session and explains how to program
automatic log-off.
16.3.1
Beginning a Node Management Session

Beginning a node management session varies, depending on the management
station you use.
4601, 4602 and 46020 network managers

To initiate a node management session from a network manager, see the appropriate
network manager documentation.
Craft Interface
To initiate a node management session from a Craft Interface node manager, see
your Craft Interface documentation.
ASCII terminal
To initiate a node management session from an ASCII (VT100) terminal:
make sure that the ASCII terminal is connected to a system serial port
power on the terminal
configure the terminal to match the selected system serial port
press a few times
After you initiate it, the node management session user interface is the same for all
Newbridge nodes regardless of the management station used.
Getting Started
(400)
16.3-1

16.3.2

NNP 95-2035-01-00-B
Screen Layout
The node management session provides a screen 78 characters wide by 24 lines long;
the screen has six functional areas, as shown in Figure 16.3-1. As you make selections
or enter information, the areas of the screen change to display relevant information.
Figure 16.3-1: Header Line Fields
Product
Generic_Release
F1-CONFIG
F6-
long_name
F2-HOUSE
F7-
F3-MAINT
F8-
Alarms
F4-STATS
F9-QUIT
Date
Time
F5-ALARMS
F0-
Header line
The information displayed in the header line (from left to right) depends on the node
with which you are having a node management session.
Product
The type of node to which you are connected, for example the 3600 MainStreet node.
Generic release
The node software version number of the node to which you are connected.
Table 16.3-1 lists the software version numbers of each type of node.
Long name
This field describes which shelf you are connected to and varies depending on the
type of node to which you are connected. Table 16.3-1 lists the long names associated
with each type of node.
16.3-2
(400)
Getting Started

NNP 95-2035-01-00-B

Alarms
The number of unacknowledged alarms in the Major/Prompt alarm queue. For a
session with a major node, the number refers only to the queue of the major node.
For a session with a minor node, the number refers only to the queue of the minor
node.
Date
The date set for the shelf Control card (even for sessions with a minor node). If no
date has been set, No Date appears.
Time
The time set for the shelf Control card (even for sessions with a minor node). Time
is displayed in hours, minutes and seconds in 12- or 24-hour format (hh:mm:ssA, P or
H). If the time has not been set, the number of hours, minutes and seconds since the
last system reset is displayed (hh:mm:ssR).
Table 16.3-1: Generic Release Numbers and Long Names
Node
Generic Release
Long Name
Enhanced locally controlled shelf Control card
S1117-ab-cd
NMTI Control:s (2)
Locally controlled shelf Control card
x117-ab-cd (1)
NMTI shelf:s (2)
Switching shelf Control card
C117-ab-cd
NMTI shelf:SWs (3)
Peripheral shelf Control card
D117-ab-cd
NMTI shelf:Pns (4)
HSPS DS-3 or DS-3 II card
H117-ab-cd
NMTI shelf:Pns (4)
HSPS2 E3 card
E117-ab-cd
NMTI shelf:Pns (4)
FRS card
P114-ab-cd
node_name:sn (5)
FRE card
P412-ab-cd
node_name:sn (5)
PE card
P611-ab-cd
node_name:sn (5)
Notes
1. where x is 1 for the 3600 MainStreet node or x is Q for the 3664 MainStreet node
2. where s is the shelf identifier (A or B)
3. where s is the shelf identifier (1 or 2)
4. where n is the number of the Switching card to which this peripheral shelf or DS-3, DS-3 II or E3 card
is connected (1 to 8) and where s is the peripheral shelf or DS-3, DS-3 II or E3 card identifier (A or B)
5. where node_name is the name configured for the Control card of the major node and where sn is the
shelf and slot identifier of the slot occupied by the minor node (s = A or B; n = 1 to 8)
Data area
This area displays information associated with the current menu item.
Getting Started
(400)
16.3-3


NNP 95-2035-01-00-B
Command line
This line displays softkey selections and keyboard entries.
Diagnostics line
This line displays prompts, error messages and information about the valid range
for numeric entries.
Softkey area
This area displays softkeys associated with function keys <F1> through <F10> (or
number keys <1> to <9> and <0>).
Status line
The status line appears only when you use the Craft Interface. See your Craft
Interface documentation for a description of the information on the status line.
Refreshing the display

Refresh the screen display by pressing <Esc> <R>. Refreshing the screen is useful in
the following situations:
if you are monitoring time-sensitive displays (such as system alarms or statistics)
16.3.3
and want to update the display

if you are examining the signalling leads
if a transmission error or other event corrupts the displayed information
Softkeys
A softkey is a key that is associated with different functions (commands) at different
times. The softkeys available at any time depend on previous softkey selections.
Selecting a softkey selects the function associated with it at that time.
Softkeys are described according to the name of the function displayed for that
softkey. Function names are usually upper case (for example, HOST). They may
contain underscores (HELLO_TIME), hyphens (END-TO-END), or obliques
(RTS/CTS). In this manual, the term softkey is used to describe both the key
associated with a particular function and the function itself.
The softkey area displays the available softkeys. Each softkey is associated with a
function key (<F1> through <F10>) or number key (<1> through <9> and <0>) on
the keyboard.
In the 3600 MainStreet Bandwidth Managers Family Technical Practices, softkeys are
written as they appear on the screen.
16.3-4
(400)
Getting Started

NNP 95-2035-01-00-B

Softkey menus
A menu is a group of softkeys displayed at one time.
The main menu is the group of six softkeys displayed after you have logged on to a
node.
Selecting softkeys
There are two ways to select a softkey.
Press the function key (<F1> through <F10>) associated with the softkey.
Press the <Esc> key and then press the number key (<1> through <9> and <0>)
associated with the softkey.
Number keys <1> to <9> are associated with function keys <F1> to <F9>. Number
key <0> is associated with function key <F10>.
For example, in Figure 16.3-2, you can select the CONFIG softkey from the main
menu with either of the following key sequences:
<F1> or <Esc> <1>
Softkeys are added to the command line as you select them (exceptions are MORE,
CANCEL, QUIT, PROCEED and display-related softkeys such as SHOW_SLOTS).
Figure 16.3-2: Main Menu for the MainStreet Node
3600 MainStreet
F1-CONFIG
F6-
Getting Started
1117-H1-00
Toronto:A
F2-HOUSE
F7-
F3-MAINT
F8-
(400)
Alarms:1
11-May-1997
F4-STATS
F9-QUIT
8:35a
F5-ALARMS
F0-
16.3-5


NNP 95-2035-01-00-B
Instructions
An instruction is a sequence of softkey selections and keyboard input that results in
an action or change of state. The instruction takes effect only after the PROCEED
softkey is displayed and selected. See the subsection To execute an instruction
(PROCEED).
Toggle softkeys
You use a toggle softkey to select one of two mutually exclusive commands
associated with one softkey.
When you select a toggle softkey, the activity governed by the softkey (and the
softkey label) changes to the alternative option, usually opposite to the original.
For example, when you select MAINT DIAG, the softkey associated with function
key <F3> (DISABLE/ENABLE) is a toggle softkey. When you select DISABLE,
background diagnostic tests are disabled and the softkey changes to read ENABLE.
When you select ENABLE, background diagnostic tests are enabled and the softkey
changes to read DISABLE.
Softkey groups
Some softkeys are grouped so that you can select only one softkey in a group. The
selected function is added to the command line or displayed in the data area and
removed from the softkey area.
For example, when you select HOUSE SER_PORT_1 BAUD_RATE, five baud
rates are displayed. The sixth (currently selected) baud rate appears in the data area
but not in the softkey area. If you select a new baud rate, it is removed from the
softkey area and replaces the old baud rate displayed in the data area. The old baud
rate now appears in the softkey area.
Display-related softkeys
Some softkeys are used to display information while you are entering an instruction.
These softkeys change the display in the data area without interrupting the
instruction. Display softkeys are SHOW_A, SHOW_B, SHOW_SLOTS,
SHOW_GROUP/SHOW_CCT, SHOW_CUR and SHOW_LIST.
Undoing a selection (CANCEL)

Selecting CANCEL undoes the current part of an instruction. It removes the last
selected softkey from the command line and displays the menu as it was before that
softkey was selected. CANCEL is always associated with function key <F8>.
16.3-6
(400)
Getting Started

NNP 95-2035-01-00-B

Returning to the main menu (QUIT)

The result of selecting QUIT depends on the menu from which it is selected.
From the main menu, QUIT logs you off the node and displays the management
station main menu.

From any other menu, QUIT displays the node management session main menu.
QUIT is always associated with function key <F9>.
To execute an instruction (PROCEED)

To execute an instruction when you have finished entering it, select PROCEED.
The softkey area displays the PROCEED softkey only when you need it. The session
interface prompts you to select PROCEED with this message on the diagnostics line:
Press PROCEED to confirm change. All softkeys except CANCEL, QUIT and
PROCEED disappear. PROCEED is always associated with function key <F10>.
After you select PROCEED, all softkeys disappear briefly and the diagnostics line
displays a message indicating that the instruction is being executed.
When execution is complete, the menu that you are most likely to use for the next
operation appears. Part of the instruction remains on the command line to save you
from having to re-enter it.
To avoid repetition, PROCEED is not included in the procedures of 3600 MainStreet
Bandwidth Manager Family Technical Practices unless selecting it causes something to
occur in addition to executing the instruction.
To log off
To log off (terminate the node management session), select QUIT (<F9>) until you
see the main menu; then, from the main menu, select QUIT again.
The node management session ends and the management station main menu (if any)
appears.
Note
Depending on the configuration specified by your site planner, you may or may not
have access to all of the softkeys. For example, if a particular level of access does not
allow configuration, the CONFIG softkey on the main menu will be inaccessible. For
more information on access levels, see chapter 17.5.
Getting Started
(400)
16.3-7

16.3.4

NNP 95-2035-01-00-B
Keyboard Entries
You make keyboard entries using the alphanumeric keys on the keyboard. For
example, you must enter circuit identifiers, node names, or interface speeds. The
node management session user interface indicates that a keyboard entry is required
in three ways.
On the command line, it displays a series of question marks or periods in
quotation marks, for example ??-?? or ....

On the diagnostics line, it displays a prompt beginning with Enter; for
example, Enter the interface speed.
It removes all softkeys except CANCEL, QUIT and display-related softkeys.
As you enter information, your entry replaces the prompt on the command line. Use
the <Delete> or <Backspace> key to correct typing errors.
In this manual, keyboard entries are indicated by text in angle brackets (< >). A
description of the keyboard entry is given using italics surrounded by angle
brackets, for example <number> and <sn-cc>.
Keyboard entry formats

Most keyboard entries have specific formats for entering the information.
Sometimes the required format is indicated by the prompt on the command line or
diagnostics line.
For example, you must enter the date in the format <dd-MMM-yy>, where dd
represents the day of the month, MMM represents the first three letters of the month
and yy represents the last two digits of the year. You must also enter the hyphens.
September 30, 1997 is entered as <30-SEP-97>.
In many cases, the format is a mixture of specific letters and variable information.
For example, in a format like <Ff-Bb>, you must enter F and B as is and information
to replace variables f and b. You must also enter the hyphen. A valid entry in this
format is <F0-B7>.
To end a keyboard entry

To indicate that you have finished a keyboard entry, press .
Note
Node management stations can store up to 100 characters in a keyboard buffer,
allowing you to type in commands or other key sequences before being prompted
for them. You can clear the buffer by holding down <Control> and pressing <X>. All
unexecuted commands are cancelled when the buffer is cleared.
16.3-8
(400)
Getting Started

NNP 95-2035-01-00-B
16.3.5

Trying a Sample Session

This example shows you how to use the management station. To get the most out of
it, carry out the steps on your management station as you read.
The example shows you how to configure card slot 3 on locally controlled or
peripheral shelf A for a North American E&M card. The explanations associated
with each step include references to the display area of the node management
session screen (see Figure 16.3-1).
To configure a card slot

1.
Initiate a node management session with the locally controlled or peripheral

shelf.
a.
If you are using a network manager, see the appropriate network manager
documentation.
b.
If you are using the Craft Interface node manager, see your Craft Interface
documentation.
c.
If you are using an ASCII (VT100) terminal, make sure that the ASCII
terminal is connected to a system serial port, powered on and configured
to match the selected system serial port; then press a few times.
The system prompts for your access level.
2.
Enter the level (press one of <1> to <5>).

The system prompts for the password configured for the selected access level.
3.
Enter the password (the system is not case sensitive; you can enter the
password in upper or lower case or any combination of upper and lower case).
The default password is <mainstreet>.
The main menu appears (see Figure 16.3-2).
Note
For more information on levels and passwords, see chapter 17.5.
4.
Select CONFIG by pressing the <F1> or <1> key.

CONFIG appears on the command line and the main menu is replaced by
another menu.
5.
Select SLOT by pressing the <F1> or <1> key.

SLOT is added to the command line after CONFIG. The management station
prompts you for a keyboard entry by displaying ?? on the command line,
displaying the prompt Enter Slot Number on the diagnostics line and
removing all softkeys except display softkeys (SHOW_A and SHOW_SLOTS),
CANCEL and QUIT.
Getting Started
(400)
16.3-9

6.

NNP 95-2035-01-00-B
Enter the slot identifier for slot A3 (<A3>).

If you do not enter a shelf identifier, the management station assumes an A.
The slot identifier replaces the ??.
Note
To select CANCEL or QUIT, enter <Esc> <8> or <Esc> <9>, respectively; if you are
using function keys F8 or F9, you do not need to press <Esc> first. If you simply
entered <8> or <9>, the management station would assume that the number was
part of the slot identifier (a keyboard entry) and add it to the command line.
7.
Press to indicate the end of the keyboard entry.

Information about slot A3 appears in the data area and the menu changes.
8.
Select TYPE (press the <F1> or <1> key).

TYPE is added to the command line after 3 and the menu changes.
9.
Select VOICE (press the <F3> or <3> key).

VOICE is added to the command line after TYPE and the menu changes.
10. Select E+M (press the <F1> or <1> key).

E+M is added to the command line after VOICE and the menu changes.
11. Select MuLaw (press the <F1> or <1> key).
MuLaw is added to the command line after E+M. The PROCEED softkey
appears beside the <F10> or <0> key in the softkey area and the prompt Press
PROCEED to confirm change appears on the diagnostics line. The only other
softkeys available are CANCEL and QUIT. This indicates the end of an
instruction.
If you realize at this point that you have selected the wrong type of card, select
CANCEL to return to step 7.
12. Select PROCEED (press the <F10> or <0> key).
The message Now changing slot configuration appears on the diagnostics
line. When the change is complete, the data area is updated with the default
settings for a North American E&M card. If a card other than an E&M card is
installed in slot A3, an alarm is raised.
The command line still displays CONFIG SLOT 3 and the word OPTIONS
has appeared beside the <F3> or <3> key in the softkey area, enabling you to
configure the options for that slot.
13. To exit from this node management session, select QUIT (press the <F9> or <9>
key) until you see the main menu. From the main menu, select QUIT again.
The node management session ends and the management station main menu
(if any) appears.
16.3-10
(400)
Getting Started

NNP 95-2035-01-00-B

To configure a card slot using a tree form

CONFIG SLOT <sn> TYPE VOICE E+M
MuLaw*
ALaw
SK000003
In this manual, a series of softkey selections and keyboard entries is shown in a tree
form. The tree begins with a single line containing selections and entries with long
dashes between them. The return key is shown as . When you have a choice
between two different keys, the tree branches into a second line. Further choices
result in further branches. For example, this procedure would be shown as:
The softkey PROCEED (used to execute the instruction) is not included because the
management station prompts for it.
16.3.6
Programming Automatic Log-off

You can program the length of time after which the node management terminal logs
off if there has been no activity. This prevents an unattended terminal from being
used by unauthorized users.
Five options are available:
5_MIN for 5 min

10_MIN for 10 min
15_MIN for 15 min
30_MIN for 30 min (default)
NONE for no automatic log off
To program automatic log-off, select the shelf or card and choose SESSN_TIME. If
there is an automatic log-off programmed, the system displays it on the screen. To
select the new automatic log-off time, press the appropriate number key.
If you select NONE, the terminal stays logged on to the system until you log off
manually by selecting QUIT from the main menu.
Getting Started
(400)
16.3-11


NNP 95-2035-01-00-B
To program automatic log-off

HOUSE MORE SESSN_TIME
5_MIN
10_MIN
15_MIN
30_MIN*
NONE
SK000004
Note 1
You do not need to select MORE for FRS, FRE or PE cards.
Note 2
The automatic log-off setting is not preserved during a database backup or restore.
When the backup or restore is complete, the automatic log off time is set to the
default (30 min).
16.3-12
(400)
Getting Started

NNP 95-2035-01-00-B
16.4
16.4 Using Identifiers

Using Identifiers
This chapter describes the node management session identifiers used for shelves,
slots and links, and circuits.
16.4.1
About Identifiers
You do configuration procedures on specific items such as card slots, links, or
circuits, each of which has a specific type of identifier. Table 16.4-1 lists the
identifiers.
Getting Started
(400)
16.4-1


NNP 95-2035-01-00-B
Table 16.4-1: Shelf, Slot, Link and Circuit Identifier Formats

Slot Identifiers
Universal cards
Control card
GFCs
Expander card
HSA cards
HSA card subslots
<sn>
<CTL>
<GFC>
<EXP>
<Hn>
<Hn-ss>
<A1> <B7>
<CTL>
<GFC>
<EXP>
<H1>
<H1-A> <H1-B>
Dual T1, Dual T1-2, Dual E1 and Dual E1-2
<sn-l>
<A6-B> <B6-A>
MPA card
<sn-l>
<A6-1> <A6-2> <A6-3>

<A6-4>
T1, E1, TTC2M, X.21 PRI, X.21 ESI PRI, V.35 PRI,
4WTO, E+M, LGE, LGS, RS-232 DCC, X.21 DCC,
V.35 DCC, RS-422 DCC, 27LC2, DSP, DCP, 64 kb/s
Codirectional and Common Carrier cards
<sn-cc>
<B3-12>
4WDX, 4WTO, E+M, LGE, LGS, MRD, DS0-DP and

OCU-DP channel units
<sn-cc-1>
<A3-3-1> <B5-1-1>
2B1Q channel unit in DTU mode
<sn-cc-p>
<A2-1-A> <B3-4-B>
2B1Q channel unit in 3DS-0 or 5DS-0 mode
<sn-cc-1>
<sn-cc-2>
<sn-cc-D>
<A5-1-1> <A5-1-2>
<A2-1-D>
Dual T1, Dual T1-2, Dual E1, Dual E1-2 and MPA
<sn-l-cc>
<B3-A-5> <A8-1-7> (1)
DNIC, 2B1Q and 27LC2
<sn-cc-p>
<A3-11-A> <B3-4-B>
DSP5H, DSP5
<sn-dsp-1>
<sn-dsp-2>
<A1-4-1> <A1-4-2>
BRI S/T card 2B+D interfaces
<sn-i>
<A1-2> <A3-6>
BRI S/T card 2B+D channels
<sn-i-h>
<A1-2-1> <A1-2-2>
<A1-2-D>
Branch channels on DSP cards, DNIC, 2B1Q and

27LC2 Line cards
<sn-cc-Bbb>
<A4-3-B2>
SRMs on DCCs
<sn-Mmm>
<B1-M6> <A6-M2>
SRMs on DSP cards, DNIC,

2B1Q and 27LC2 Line cards
<sn-cc-Mmm>
<B1-3-M6>
<A6-11-M2>
VCBs on DSPs
<sn-cc-BRr>
<A1-1-BR3>
VCB Inputs on DSPs
<sn-cc-Ikk>
<B2-2-I5>
SRS on DSPs
<sn-SRS-dd>
<A3-SRS-4>
Compressed voice channels on T1 and E1 cards
<sn-Scc-vv>
<B2-S3-1>
<A3-S6-2>
Voice compressors on Dual T1 and Dual E1 cards
<sn-Xt>
<A7-X3> <B2-X5>
DS3 identifier
DS1 identifier
DS0s on DS-3 or DS-3 II cards
<DS-3>
<n>
<n-cc>
DS-3
<3>
<5-15>
Link Identifiers
16.4-2
(400)
Getting Started

NNP 95-2035-01-00-B

E3 identifier
E2 identifier
E1 identifier
DS0s on E3 cards
<E3id>
<E3id-E2id>
<E3id-E1id>
<E3id-E1id-cc>
<1>
<2-B>
<1-14>
<2-12-27>
Order Wire on GFC3
<OW>
<OW>
DS0 on GFC3
<DS0>
<DS0>
Test Port on GFC3
<TP>
<TP>
Tone Tester on GFC3
<TT-cc>
<TT-1>
BERT on GFC3
<BT-cc>
<BT-1>
<Hn-ss-pa>
<Hn-ss-AU4>
<Hn-ss-pa>
<Hn-ss-pa-gr>
<Hn-ss-pa-gr>
<Hn-ss-pa-gr-vs>
<Hn-ss-pa-gr-vs>
<Hn-ss-Vvs>
<Hn-ss-Tvs>
<H1-A-1>
<H1-A-AU-4>
<H1-A-1>
<H1-A-1-3>
<H1-A-1-3>
<H1-A-1-3-1>
<H1-A-1-1-1>
<H1-A-V1>
<H1-A-T2>
<Hn-ss-c>
<Hn-c-d>
<H1-A-5>
<H1-A-2>
<Scc>
<Scc>
<Scc>
<Fnn>
<S22>
<S22>
<S22>
<F63>
<Scc-dlci>
<Scc-dici>
<Scc-dici>
<Fnn-dici>
<S22-768>
<S22-768>
<S22-768>
<F63-2127>
<sn-cc-Ixx>
<A1-1-I2>
HSA Card Broadband Circuit Identifiers

AU3s on an STM-1 card
AU-4s on an STM-1 card
STS-1s on OC-3 cards
VT groups on OC-3 cards
TU groups on STM-1 cards
VTs on OC-3 cards
TUs on STM-1 card
VTs on VT-1.5 cards
TUs on TU-12 cards
HSA Card Narrowband Port and Circuit Identifiers
Narrowband port on VT-1.5 or TU-12 cards
Narrowband DS0 circuit on VT-1.5 or TU-12 cards
Stream Identifiers
FRS card
FRE card
PE card
FASTbus
DLC Identifiers
FRS card
FRE card
PE card
FASTbus
ISDN Index Identifiers
CPC
Getting Started
(400)
16.4-3


NNP 95-2035-01-00-B
bb = a 1- or 2-digit branch channel. Ranges:

DNIC Line cards: 1 to 6, or 12
DSPs: 1 to 6, 10 or 12
2B1Q Line card: 1 to 6
27LC2 Line card: 1 to 6
c = a VT-1.5 or TU-12 card narrowband port: 1 to 16
cc = a 1- or 2-digit circuit number. Ranges:
T1, DUAL_T1: 1 to 24
T1, DUAL_T1 on 3664 MainStreet: 1 to 12
E1, DUAL_E1: 1 to 31
E1, DUAL_E1 on 3664 MainStreet: 1 to 15, 31
X21_PRI, V35_PRI: 1 to 30
TTC2M: 1 to 30
4WTO: 1 to 12
E+M: 1 to 6
LGE: 1 to 8
LGS: 1 to 12
MPA: 1 to 30
RS-232_DCC: 1 to 6
X.21_DCC: 1 to 4 or 6
V.35_DCC: 1 to 3 or 6
RS-422_DCC: 1 to 4
DNIC: 1 to 3, 6 or 12
DSP: 1 or 2 or 6
DCP: 1 to 31
FRS: 1 to 31
2B1Q: 1 to 6
64 kb/s Codirectional: 1 to 4
Common Carrier card: 1 to 4
Channel units: 1 to 4 (except the 4WDX channel unit: 1 to 3)
FRS card circuit connected to a primary rate or data circuit: 1 to 30
FRE card circuit connected to a primary rate or data circuit: 1 to 62
PE card circuit connected to a primary rate or data circuit: 1 to 62
FASTbus stream identifier 1 to 64
Tone tester on GFC3: 1 or 2
BERT on GFC3: 1 or 2
D = the D channel in BRI or PRI interfaces, or the D+ channel in 3DS0 mode or the D+CV channel in 5DS0 mode 2B1Q channel
units.
d = a 1- or 2-digit VT-1.5 or TU-12 card DS0 number. Ranges:
VT-1.5: 1 to 24
TU-12: 1 to 31
dd = a DS0 number. Ranges:
1 to 30 (without double bandwidth)
1 to 48 (with double bandwidth)
dlci = data link connection identifier. Ranges:
16 to 1007 (local DLC cross-connections)
2000 to 3983 (FASTbus DLC cross-connections)
dsp = a DSP resource identifier (1 to 10)
E1id = a 1- or 2-digit E1 identifier (1 to 16)
E2id = a 1-character E2 identifier (A to D)
E3id = a 1-digit E3 number (1 or 2 for DE3 cards, 1 for SE3 cards)
gr = a VT-Group number (0 to 7) for an OC-3 card, TUG-2 number (1 to 7) for an STM-1 card in AU-3 or AU-4 mode
h = a BRI interface channel number (1, 2 or D)
i = a BRI S/T card interface number (1 to 4 for 4-circuit BRI S/T cards, 1 to 8 for 8-circuit BRI S/T cards)
kk = a 1- or 2-digit input number (1 to 14)
l = a link indicator: A or B on the Dual T1 and Dual E1 cards, 1 to 4 on the MPA card
16.4-4
(400)
Getting Started

NNP 95-2035-01-00-B

lxx = a CPC index. Ranges:

BRI interfaces: 1 or 2
T1 PRI interfaces: 1 to 23
E1 PRI interfaces: 1 to 30
mm = a 1- or 2-digit SRM number. Ranges:
DCCs: 1 to 3
DNIC Line cards: 1 to 6, 8 or 12
DSPs: 1 to 4, 6 or 12
2B1Q Line card: 1 to 6
n = a 1-digit slot number (1 through 8) for a switching, locally controlled or peripheral shelf
= a 1- or 2-digit number (1 to 28) for DS-3 or DS-3 II cards
= a 1-digit
= a 1-digit HSA slot number (1 to 3) for an enhanced locally controlled shelf
p = a port indicator (A or B)
pa = a broadband circuit number (1 to 3) which can indicate: an STS-1 number for an OC-3 card, a TUG-3 number for an STM-1
card in AU-4 mode, or AU-3 number for an STM-1 card in AU-3 mode
pr = a slot pair indicator (A or B)
r = a bridge number (1 to 4)
s = a shelf indicator (A or B)
ss = an HSA subslot (A or B), optional for certain parameters
t = a 1-digit compressor number, 1 to 5 for delta voice compression and 1 to 32 for transitional voice compression
vs = a VT number (1 to 4 for an OC-3 card, or 1 to 16 for a VT-1.5 card)
= a TU number (1 to 4 for an STM-1 card or 1 to 16 for a TU-12 card)
vv = a 1- or 2-digit compressed voice channel (1 to 11)
x = a shelf number (for peripheral shelf, DS-3 or E3 cards)
Notes
1. The MPA card link identifier is an integer from 1 through 4. For the Dual T1 and E1 cards, the link identifier can be either the
letter A or the letter B.
16.4.2
Shelf Identifiers
The identifiers used with switching, locally controlled or peripheral and HSPS are
determined by shelf-select jumpers set during initial installation or intershelf
connections (see Installation, Task 0500 and Task 0600).
Note
In all configurations, if you enter no shelf identifier, the management station
assumes it to be 1 for a switching shelf, or A for a locally controlled, peripheral or
HSPS card.
Switching shelf identifiers

For a single-shelf configuration, the management station identifies the switching
shelf as 1. The backplane shelf-select jumper must be in position 1.
Getting Started
(400)
16.4-5


NNP 95-2035-01-00-B
For a shelf-redundant configuration, the management station identifies the

switching shelves as switching shelf 1 and switching shelf 2 according to the
backplane shelf-select jumpers.
Locally controlled and peripheral shelf identifiers

In a single-shelf configuration, the management station identifies the locally
controlled or peripheral shelf as A. The backplane shelf-select jumper must be in
position A.
In a dual-shelf, non-control-redundant configuration, the management station
identifies the locally controlled or peripheral shelf with the Control card as A and
the other shelf as B. The shelf-select jumpers in each shelf must be set accordingly.
In a control-redundant configuration, each locally controlled or peripheral shelf has
a Control card. The management station identifies the shelves as A and B according
to the backplane shelf-select jumpers.
HSPS identifiers
HSPS cards (DS-3, DS-3 II or E3 cards) are identified as either card A or B depending
on the slot they are installed in. When installed in an odd-numbered slot (1, 3, 5 or 7),
the card is identified as card A. When installed in an even-numbered slot (2, 4, 6
or 8), the card is identified as card B.
16.4.3
Shelf Numbers
Each peripheral shelf and each HSPS card is also identified by the number of the
switching shelf slot occupied by the Switching card to which the peripheral shelf or
HSPS card is connected. For example, in Figure 16.4-1, the peripheral shelf
connected to the Switching card in switching shelf slot 1 is identified by a 1. The
HSPS2 card connected to the Switching card in switching shelf slot 5 is identified by
a 5, and so on.
This number, called the shelf number, is displayed in the NMTI header and used
when you log onto the switching shelf to configure connections; for example:
CONFIG CONNECT <x-sn-cc> TO_CIRCUIT <x-sn-cc>
where x is the shelf number (1 to 8) of a peripheral shelf or HSPS card
When you log onto a peripheral shelf or HSPS card, the shelf number is not required,
for example:
CONFIG CIRCUIT <sn-cc> NAME <name>
16.4-6
(400)
Getting Started

NNP 95-2035-01-00-B

Figure 16.4-1: Peripheral Shelf and HSPS Card Shelf Numbering

Switching shelf
3645 MainStreet
Switching
card #5
Switching
card #1
Switching
card #6
5 6
3645 MainStreet
This card is
identified as
peripheral shelf
#5.
This shelf is identified as

peripheral shelf #1.
This card is
identified as
peripheral shelf
#6.
4800
16.4.4
Slot Numbers
The card slots are numbered from left to right on the switching, locally controlled
and peripheral shelves, and HSPSs.
Getting Started
(400)
16.4-7


NNP 95-2035-01-00-B
Switching shelf
As Figure 16.4-2 shows, the use of the slots in the switching shelf is as follows:
slots 1 through 8: Switching cards

slot 9: Clock card (no configurable parameters)
slot 10: Control card (no configurable parameters)
Figure 16.4-2: Slot Numbers for the Switching Shelf
Class A
Class B
Critical Alarm
Critical Alarm
3645 MainStreet
NEWBRIDGE
3645 MainStreet
Major Alarm
Minor Alarm
PS1
5A
PS2
5A
Alarm
Alarm
Power
Power
NEWBRIDGE
Major Alarm
Minor Alarm
PS1
5A
PS2
5A
Alarm
Alarm
Power
Power
slots 1 to 8
9 10
slots 1 to 8
9 10
Switching
section
Common
Control
section
Switching
section
Common
Control
section
Class B
23-inch
3645 MainStreet
High Capacity Bandwidth Manager
Critical Alarm
Major Alarm
Minor Alarm
Power Supply
Card
0VR
-BATT
+5
-5
+12
-12
GND
Alarm
Status
Power Supply
Card
0VR
-BATT
+5
-5
+12
-12
GND
Alarm
Status
slots 1 to 8
9 10
Switching
section
Common
Control
section
5393
16.4-8
(400)
Getting Started

NNP 95-2035-01-00-B

Locally controlled and peripheral shelves

As Figure 16.4-3 shows, locally controlled or peripheral shelf slots are used as
follows.
Slots 1 through 8, called UCSs, contain any type of interface or application card.
Slot 9 contains the Control card (no configurable parameters).
Slot 10 contains the Expander card in a locally controlled shelf, or a Switching
Interface card in a peripheral shelf (no configurable parameters).

Slot 11 contains the Balanced Transceiver cards (no configurable parameters).
Slot 12 contains the GFC, GFC2 or GFC3. The GFC and GFC2 have no
configurable parameters, whereas the GFC3 is NMTI configurable. The GFC,
GFC2 and GFC3 perform maintenance functions that are controlled through the
node manager. For details, see Maintenance, chapter 36.4.
The type of Expander card or Switching Interface card in slot 10 determines which
UCSs can be configured and which offer double-bandwidth capability (as listed in
Table 16.4-2). For more information, see Technical Overview, chapters 4.7 and 4.10.
Table 16.4-2: Locally Controlled and Peripheral Shelf UCS Access
Card in Slot 10
Accessible UCSs
Double Bandwidth UCSs
No card installed
A1-A6
None
Expander 6+2
A1-A8
A7 and A8 (1)
Expander 6+6
A1-A6 and B1-B6
None
Expander 8+8
A1-A8 and B1-B8
A7, A8, B7 and B8 (1)
Expander 16+
A1-A8 and B1-B8
A1-A8 and B1-B8
Switching Interface card
A1-A8 and B1-B8
A1-A8 and B1-B8
Notes
1. All UCSs are single bandwidth if the 4602 MainStreet Intelligent NetworkStation or MainStreetXpress
46020 Network Manager is used. UCS 7 and 8 provide double bandwidth if the 4602 or 46020
network manager is not used.
Getting Started
(400)
16.4-9


NNP 95-2035-01-00-B
Figure 16.4-3: Slot Numbers for the Locally Controlled or Peripheral Shelf
Class A
Class B
Critical Alarm
Bandwidth Manager
Bandwidth Manager
PS1
5A
Major Alarm
Minor Alarm
PS2
5A
NEWBRIDGE
NEWBRIDGE
PS1
5A
PS2
5A
Alarm
Alarm
Power
Power
slots 1 to 8
9 to 12
slots 1 to 8
9 to 12
Interface
section
Common
control
section
Interface
section
Common
control
section
Class B
23-inch
Bandwidth Manager
Critical Alarm
Major Alarm
Minor Alarm
Power Supply
Card
0VR
- BATT
+5
-5
+ 12
- 12
GND
Alarm
Status
Power Supply
Card
0VR
- BATT
+5
-5
+ 12
- 12
GND
Alarm
Status
slots 1 to 8
9 to 12
Interface
section
Common
control
section
4758
HSPS
As Figure 16.4-4 shows, the use of the slots in an HSPS is as follows:
slots 1a through 4b are reserved for DS-3 or DS-3 II cards

the remaining slots are reserved for future use
16.4-10
(400)
Getting Started

NNP 95-2035-01-00-B

Figure 16.4-4: Slot Numbers for the HSPS
Critical Alarm
3645 MainStreet
Major Alarm
Minor Alarm
NEWBRIDGE
PS1
5A
PS2
5A
Alarm
Alarm
Power
Power
1a 1b 2a 2b 3a 3b 4a 4b
Switching
section
Reserved
for future
use
5343
HSPS2
As Figure 16.4-5 shows, slots 1a through 4b in the HSPS2 are reserved for SE3 and
DE3 cards.
Getting Started
(400)
16.4-11


NNP 95-2035-01-00-B
Figure 16.4-5: Slot Numbers for the HSPS2
1a
1b
E3 card
interface section
2a 2b 3a 3b
4a
4b
5390
16.4-12
(400)
Getting Started

NNP 95-2035-01-00-B
16.5
16.5 Displaying Configuration Information

Displaying Configuration
Information
This chapter explains how to display information about slots, circuit connections
and configuration.
16.5.1
Displaying Slot Information

You can display detailed information or a summary about slots and cards in the
locally controlled, enhanced locally controlled, switching, peripheral shelves and
HSPS.
Note
Table 16.4-1 in chapter 16.4 explains the formats of the identifiers in the procedures.
To view the switching shelf summary display

Select the switching shelf and enter:
CONFIG SLOT
Figure 16.5-1 shows a typical switching shelf display.
Getting Started
(400)
16.5-1


NNP 95-2035-01-00-B
Figure 16.5-1: Switching Shelf Display
3645 MainStreet
#
1
2
3
4
5
6
7
8
CTL
CLK
C117-H1-00
Configured
Toronto:SWA
Installed
SC
SC
Empty
Empty
Empty
Empty
Empty
Empty
Status
SC
SC
Empty
Empty
Empty
Empty
Empty
Empty
Control
Clock
Alarms:1
Name
Ok
Ok
Empty
Empty
Empty
Empty
Empty
Empty
Control
Clock
11-May-1997
8:35a
Options
DOUBLE_BW PS NODE 1
DOUBLE_BW PS NODE 2
Ok
Ok
CONFIG SLOT "??"

Enter Slot Number
F1F6-SHOW_SLOTS
F2F7-
F3-CONFIG_ALL
F8-CANCEL
F4F9-QUIT
F5F10-
To display the locally controlled, enhanced locally controlled, peripheral shelf

or DS-3 or E3 card summary
Select the shelf or card, and enter:
CONFIG SLOT SHOW_SLOTS
Figure 16.5-2 shows the display for a typical configuration. Table 16.5-1 lists and
describes the fields on this display.
16.5-2
(400)
Getting Started

NNP 95-2035-01-00-B

Figure 16.5-2: Summary Display for a Typical Configuration

3645 MainStreet
#
D117-H1-00
Configured
A1
A5
A3
A4
A5
A6
A7
A8
CTL
GFC
Toronto:P3A
Alarms:1
11-May-1997
8:35a
Installed
Stat
Configured
Installed
Stat
LGS Mu-Law
X.21_DCC 6
E+M Mu-Law
E+M A-Law
LGE Mu-Law
LGE A-Law
E1
DSP
LGS Mu-Law
X.21_DCC 6
E+M Mu-Law
E+M A-Law
E1
E1
DSP
Ok
Ok
Ok
OK
Prob
Prob
OOS
Ok
B1
B2
B3
B4
B5
B6
B7
B8
LGS A-Law
RS-232 DCC
-
X.21 DCC 4
X.21 DCC 6
-
Prob
Prob
Prob
Prob
-
Control
GFC
Control
GFC
Ok
Ok
CONFIG SLOT "??"
F1-SHOW_A
F6-SHOW_SLOTS
F2-SHOW_B
F7-
F3-CONFIG_ALL
F8-CANCEL
F4F9-QUIT
F5F10-PROCEED
Table 16.5-1: Heading Information for Summary Display

Heading
Getting Started
Indicates
Displays the slot identifier (CTL indicates a Control card, EXP indicates an Expander
card and GFC indicates a General Facilities card).
Configured
The type of card for which the slot has been configured through a node manager.
Installed
The type of the card that has been physically installed in the slot.
Status
The status of the card as:

OK: The installed card matches the configured card and no other problems are
apparent.
OOS: The primary rate link for the card is out of service.
: The slot is empty.
Prob: There is a problem with the card. Enter SHOW_A or SHOW_B to display more
detailed problem information.
(400)
16.5-3


NNP 95-2035-01-00-B
To display a detailed summary of a locally controlled, enhanced locally

controlled or peripheral shelf
Both SHOW_A and SHOW_B appear in the enhanced locally controlled shelf and in
locally controlled or peripheral shelves with dual-shelf configurations. Only the
SHOW_A option appears in locally controlled or peripheral shelves with
single-shelf configurations.
CONFIG SLOT
SHOW_A
SHOW_B
SK000005
Figure 16.5-3 shows a sample display for SHOW_A on a peripheral shelf.

Figure 16.5-3: SHOW_A Display
3645 MainStreet
#
1
2
3
4
5
6
7
8
CTL
SI
GFC
D117-H1-00
Configured
LGS Mu-Law
X.21_DCC 4
E+M Mu-Law
E+M A-Law
LGE Mu-Law
LGE A-Law
E1
DSP
Installed
Empty
X.21_DCC 4
Empty
T1
Empty
Empty
E1
DSP
Control
SI
GFC
Control
SI
GFC
Toronto:P3A
Alarms:1
11-May-1997
Status
Name
Empty
Ok
Empty
Wrong Card
Empty
Empty
Wrong Module
Ok
8:35a
Options
2-WIRE TYPE-I
2-WIRE TYPE-V
CAS
Ok
Ok
Ok
CONFIG SLOT "??"
F1-SHOW_A
F6-SHOW_SLOTS
F2-SHOW_B
F7-
F3-CONFIG_ALL
F8-CANCEL
F4F9-QUIT
F5F10-
Table 16.5-2 lists and describes the fields on this display.
16.5-4
(400)
Getting Started

NNP 95-2035-01-00-B

Table 16.5-2: SHOW_A Display Information

Heading
Indicates
Displays the slot identifier.
Configured
The type of card for which the slot has been configured.
Installed
The type of card installed in the slot.
Status
The status of the card as:

OK: Installed card is fault-free and matches the slot configuration.
OOS: The primary rate link for the card is out of service.
Empty: The slot is empty.
Wrong Card: The type of card installed in the slot does not match the type of card for
which the slot was configured.
Wrong F/W: A Test module is installed on a Test card that has not been upgraded.
Wrong Module: The type of module on the card does not match the type of module that
was configured.(1)
Fault On Card / Card Dead: A fault has occurred. Check the alarm queue (see
Maintenance, chapter 35.3, for details). If the problem persists, contact your Newbridge
representative.
Bad Card ID: The card is not recognized by the system. If this message appears, contact
your Newbridge representative.
Config Prob: The 3600+ MainStreet Control card cannot be used because the
Narrowband and Broadband Switching modules are configured but not installed on the
card.
Name
Displays the name assigned to the slot.
Options
Displays the configured slot options.
Notes
1. Not applicable to the Bank-B Memory module.
16.5.2
Displaying Card Information

As shown in Figures 16.5-4 and 16.5-5, you can display card information for
switching, peripheral, locally controlled and enhanced locally controlled shelf card
slots and for DS-3 and E3 cards. This information is useful when you are describing
your system to Newbridge technical support staff. For control-redundant systems,
the system demerits value for both shelves (1 and 2, or A and B) appear with the
Control card information.
To display the Switching card summary

Select the switching shelf, and enter:
MAINT ON_SLOT <n>
where n is the slot identifier of the Switching card you want to display
Getting Started
(400)
16.5-5


NNP 95-2035-01-00-B
Figure 16.5-4 shows a typical card information display. This display also describes
the status of the peripheral shelf connected to the specified Switching card.
Figure 16.5-4: Switching Card Information Display
3645 MainStreet
C117-H1-00
Card Type: SC
Card ID: $2
Card Variant ID:
Slot Status: OK
Peripheral Stat:
Configured Node:
Installed Type:
SI Cables: 1A:
1B:
2A:
2B:
F1F6-
$0
Toronto:SWA
Alarms:1
11-May-1997
8:35a
Module Type: DOUBLE_BW

Module ID: $0
Module Variant ID: $0
Peripheral In Service
1
Installed Node: 1
Peripheral Shelf
OK (Active)
Fault
---------------------
F2F7-MORE
F3F8-CANCEL
F4F9-QUIT
F5F10-
To display a locally controlled, peripheral, DS-3 or E3 card summary

Select the shelf or card, and enter:
MAINT ON_SLOT
<n>
<CTL>
<EXP>
<GFC>
SK000006
Figure 16.5-5 shows a typical card information display.
16.5-6
(400)
Getting Started

NNP 95-2035-01-00-B

Figure 16.5-5: Card Information Display

3645 MainStreet
Card
Card
Card
Slot
D117-H1-00
Type
ID
Variant ID
Status
:
:
:
:
Empty
None
None
Empty
Toronto:P3A
Alarms:1
Module Type
Module ID
Module Variant ID
:
:
:
11-May-1997
8:35a
None
None
None
MAINT ON_SLOT 1-4A
F1F6-
F2F7-
F3F8-CANCEL
F4F9-QUIT
F5F10-
To display summary information for an enhanced locally controlled shelf

MAINT ON_SLOT
<n>
<CTL>
<TIM>
SK000910
Figure 16.5-6 shows a 3600+ MainStreet Control card information display.
Getting Started
(400)
16.5-7


NNP 95-2035-01-00-B
Figure 16.5-6: 3600+ MainStreet Control Card Information Display

3600+ MainStreet
S1117-H1-00
Card Type
: Control
Card ID
: $1
Card Variant ID : $0
Active Bank
: A
Slot Status
: Ok
NarrowBand Module Status
BroadBand Module Status
Memory Module Status
Toronto:A
Alarms:1
Card Revision
Card Serial No.
Card Part No.
11-May-1997
8:35a
: 01
: 123456
: 90-0001-01-00-0000
: Ok
: Ok
: Ok
MAINT ON_SLOT CTL
1-SW_GENERIC
6-RESET_CARD
2-NBAND_MOD
7-
3-BBAND_MOD
8-CANCEL
4-MEMORY_MOD
9-QUIT
50-
DIAG_INFO
For a description of the fields in this display, see Maintenance, chapter 33.3.
To display Control card module information for an enhanced locally controlled

shelf
MAINT ON_SLOT <CTL>
NBAND_MOD
BBAND_MOD
MEMORY_MOD
SK000909
Figure 16.5-7 shows a 3600+ MainStreet Control card module information display
for the Narrowband module. The displays for the Broadband and the Bank-B
Memory modules are similar.
16.5-8
(400)
Getting Started

NNP 95-2035-01-00-B

Figure 16.5-7: Control Card Module Information Display

3600+ MainStreet
S1117-H1-00
NarrowBand Module
Module Type
Module ID
Module Variant ID
Module Revision
Module Serial No.
Module Part No.
Module Status
:
:
:
:
:
:
:
:
Toronto:A
Alarms:1
11-May-1997
8:35a
8k_X_8k_SW
$30
01
01
123456
90-0002-01-00-0000
Ok
MAINT ON_SLOT CTL NBAND_MOD
16-
27-
38-CANCEL
49-QUIT
50-
To display a circuit or connection summary

For locally controlled, enhanced locally controlled, switching or peripheral shelves,
DS-3 or E3 cards, enter:
CONFIG CONNECT <sn-cc> or <x-sn-cc> SHOW_GROUP/SHOW_CCT*
Note
To view circuit connection information for the enhanced locally controlled shelf, see
chapter 31.6.
Figure 16.5-8 shows a typical switching shelf display. If you have configured a
protecting connection, this display also appears.
Getting Started
(400)
16.5-9


NNP 95-2035-01-00-B
Figure 16.5-8: Switching Shelf Connection Display

3645 MainStreet
Circuit
C117-H1-00
Name
1-A4-01
1-A4-02
F1-SHOW_CCT
F6-PROTECTING
Toronto:SWA
Alarms:1
Type
Circuit
LGS_EC
LGS_EC
1-A7-13
1-A7-06
F2-DISCONNECT
F7-
F3-TO_CIRCUIT
F8-CANCEL
11-May-1997
Name
8:35a
Type
E1-LGE_EC
E1-LGE_EC
F4F9-QUIT
F5- PROT_BY
F10-
Figure 16.5-9 shows a typical peripheral shelf display. The circuits that are connected
appear with an asterisk. If you have configured a protecting connection, it also
appears.
Figure 16.5-9: Peripheral Shelf Connection Display
3645 MainStreet
Circuit
D117-H1-00
Name
1-A1-01
* = Active connect;
Toronto:P3A
Alarms:1
Type
Circuit
T1_SIG
3-A1-02
11-May-1997
Name
8:35a
Type
T1_SIG
! = Maintenance connect
CONFIG CONNECT A1-1
F1-SHOW_CCT
F6-PROTECTING
16.5-10
F2-DISCONNECT
F7-
F3-TO_CIRCUIT
F8-CANCEL
(400)
F4F9-QUIT
F5- PROT_BY
F10-
Getting Started

NNP 95-2035-01-00-B

To display a channel unit summary

Select the locally controlled, enhanced locally controlled or peripheral shelf and
enter:
CONFIG SLOT <sn-cc> SHOW_UNITS
Getting Started
(400)
16.5-11

NNP 95-2035-01-00-B
17. Node Parameters

NNP 95-2035-01-00-B
17.1
17.1 Circuit Connections

Circuit Connections
This chapter introduces the types of connections and explains how to do general
circuit operations. It explains how to configure the following types of connections:
17.1.1
simple bidirectional
simple unidirectional
broadcast unidirectional
TS0 NU bit
Understanding Connections
This chapter gives you an overview of the types of connections and describes basic
types that apply to many different situations. Specialized connections are described
in other sections as part of a larger topic, such as CPSS messages, voice compression,
or subrate multiplexing.
You do circuit connections from a locally controlled or switching shelf during a Craft
Interface or NMTI session. With the exception of CPSS connections, if you try to
make a circuit connection from a peripheral shelf, a warning message appears.
Note
The 3645 MainStreet node supports NMTI circuit connection management. Prior to
Release 7.0, circuit connections could only be configured for 3645 MainStreet
systems through a Craft Interface session.
The two basic types of connections are:
bidirectional connections that provide two identical paths between source and
destination devices: data and signals pass back and forth between the source and
destination devices
unidirectional connections that provide a single path between a source and
destination device: data and signals pass in a single direction only (these
connections are available on PRI cards in 3645 MainStreet peripheral shelves)
Caution
DET cards in 3645 MainStreet peripheral shelves can be configured for

unidirectional or bidirectional operation. If the mode of operation is changed, any
existing cross-connections are lost and must be reconnected.
Node Parameters
(400)
17.1-1


NNP 95-2035-01-00-B
Table 17.1-1 lists the most common types of connections.

Table 17.1-1: Connection Types
Connection Type
Chapter
Bidirectional
Simple
17.1
TS0 NU bit
17.1
Protecting (protection switching)
18.2
CPSS
17.6
Voice compression
23.3
Rate adaption and subrate multiplexing
23.6
Multidrop data bridges
23.7
Super-rate
20.15
Unidirectional
17.1.2
Simple
17.1
Broadcast
17.1
Super-rate
20.15
Configuring Basic Circuit Connections

The procedures in this chapter explain how to make basic circuit connections.
Table 17.1-2 lists the locations of the procedures.
Table 17.1-2: Circuit Configuration Procedures
Control
Card
DS-3
Card
E3
Card
E1
Card
Bidirectional connections
17.1.4
Broadcast unidirectional connections
17.1.6
Circuit copy
17.1.3
Circuit display
17.1.3
Circuit names
17.1.3
Range copy
17.1.3
TS0 cross-connections
17.1.7
Unidirectional connections
17.1.5
17.1-2
Section
Configuration Procedure
(400)
Node Parameters

NNP 95-2035-01-00-B

Note
17.1.3
Using General Circuit Operations

The general circuit operations are:
displaying connection or circuit information

naming circuits
copying circuit configuration
copying ranges
To display circuit configuration information

To display circuit configuration information from the locally controlled shelf,
peripheral shelf, DS-3 or DS-3 II card, or E3 card, you select SHOW_CCT or
SHOW_GROUP. SHOW_CCT is the default display. If you have configured a
protecting connection, it also appears. SHOW_GROUP displays a group of circuits
adjacent to the specified circuit.
CONFIG CONNECT <sn-cc> or <x-sn-cc> SHOW_GROUP/SHOW_CCT*
Figure 17.1-1 shows a display for a peripheral or locally controlled shelf.

Note
Prior to Release 7.0, 3645 MainStreet peripheral units displayed a generic switching
interface identifier (such as SI-0076) in place of the actual connected circuit.
Node Parameters
(400)
17.1-3


NNP 95-2035-01-00-B
Figure 17.1-2 shows a display for a switching shelf. Table 17.1-3 lists and describes
the symbols on these displays.
Figure 17.1-1: CONFIG CONNECT Display (Peripheral Shelf)
3600 MainStreet
Circuit
2-A1-01
1117-H1-00
Name
Toronto:A
Type
T1_SIG
* = Active connect;
Alarms:1
Circuit
3-A1-02
Name
11-May-1997
8:35a
Type
T1_SIG
Conv
! = Maintenance connect
CONFIG CONNECT A2-1

F1-SHOW_CCT
F6-PROTECTING
F2F7-
F3-TO_CIRCUIT
F8-CANCEL
F4F9-QUIT
F5- PROT_BY
F10-
Figure 17.1-2: CONFIG CONNECT Display (Switching Shelf)

3645 MainStreet
Circuit
1-B8-A-22
C117-H1-00
17.1-4
Type
DE1_Sig
Alarms:1
Circuit
-> *6-A7-B-12
<B *3-B1-4
1-B8-A-23
DE1_Sig
--1-B8-A-24
DE1_NoSig
B> *2-A1-A-1
B> 6-A7-B-13
B> *4-B3-B-7
B> *3-B1-1
<- *4-B3-B-7
1-B8-A-25
DE1_Sig
-> *5-A2-A-11
<- *6-A7-B-12
1-B8-A-26
DE1_Sig
<- *6-A7-B-12
1-B8-A-27
DE1_Sig
*5-A2-A-12
* = Active connect; ! = Maintenance connect
CONFIG CONNECT 1-B8-A-22
F1-ONE_WAY_TO
F6-
Name
Toronto:SWA
F2-BROADCAST
F7-
F3-RMV_BCAST
F8-CANCEL
(400)
Name
11-May-1997
Type
DE1_Sig
64CO_Sig
8:35a
Conv
DE1_NoSig
DE1_NoSig
DE1_NoSig
64CO_NoSig
DE1_NoSig
DE1_Sig
DE1_Sig
DE1_Sig
DE1_Sig
F4-PREV_BCAST
F9-QUIT
F5-NEXT_BCAST
F10-
Node Parameters

NNP 95-2035-01-00-B

Table 17.1-3: CONFIG CONNECT Display Symbols

Symbol
Description
blank
There is no connection or it is a bidirectional connection.
>
The circuit listed to the right of the symbol is the destination circuit in a one-way
unidirectional connection.
<
The circuit listed to the right of the symbol is the source circuit in a one-way
B>
The circuit listed to the right of the symbol is a destination circuit in a broadcast
<B
The circuit listed to the right of the symbol is the source circuit in a broadcast
The circuit is physically connected.
To name circuits
You can assign a name to any circuit in the locally controlled shelf, peripheral shelf,
DS-3 or DS-3 II card, or E3 card, using the NAME softkey. To delete a circuit name
without assigning another one, select NAME and press .
To copy circuit configuration

If you want to configure many circuits to be the same, you can configure one, then
copy its parameters (all but name and connection) to each other circuit in turn using
the COPY_TO softkey.
For circuits using transparent, HCM, DDS or X.50 rate adaption, use COPY_ADJ.
(COPY_ADJ varies in each case. See chapter 23.6 for rate adaption information.) Do
not use COPY_ADJ when you are configuring a multidrop data bridge.
For the DS-3 or DS-3 II and E3 cards, you can copy circuit parameters to more than
one other circuit in one operation, by specifying the first and last circuits of a range,
using the COPY_RANGE softkey.
CONFIG CIRCUIT <sn-cc>
NAME
COPY_TO
<name>
COPY_ADJ
<sn-cc>
COPY_RANGE
<sn-cc>
TO
<sn-cc>
SK000007
where
name is up to 8 alphanumeric characters (no spaces)
the first sn-cc is the source circuit identifier
the second sn-cc is the identifier of the destination circuit or the first circuit of the destination range
the third sn-cc is the last circuit of the destination range
Node Parameters
(400)
17.1-5


NNP 95-2035-01-00-B
Note
Do not use COPY_TO or COPY_ADJ if either circuit is connected.
17.1.4
Configuring Simple Bidirectional Connections

When no protection switching, voice compression or subrate multiplexing is
involved, do a simple bidirectional connection between primary rate circuits, voice
circuits or data circuits. Simple bidirectional connections provide two identical paths
between source and destination devices: one transmit path and one receive path.
Data and signalling (if applicable) pass back and forth between the source and
destination devices.
To connect circuits from the locally controlled or switching shelf, you select the
CONNECT softkey, enter the circuit identifier, then select TO_CIRCUIT and enter
the connecting circuit identifier. After you enter the circuit identifier, the connection
information for that circuit appears in the data area.
If the first circuit is already connected, a warning appears after you select
TO_CIRCUIT, but you can proceed. After you enter the identifier of the second
circuit, a warning appears if that circuit is already connected.
If one of the circuits in the connection is on a T1 or E1 card that has a CCM, two
softkeys appear: COMP_CONV and NO_CONV. These softkeys indicate whether or
not companding conversion should be done on that connection (the default is no
conversion or NO_CONV). The data area display indicates whether or not
companding conversion is being done for a connection by displaying Y for yes or
N for no under the heading Conv.
Select the DISCONNECT softkey. The DISCONNECT softkey appears only when
the first circuit is cross-connected to another circuit or the CPSS. Selecting
DISCONNECT breaks the existing connection without defining another one.
If the selected circuit has both a preferred and a protecting connection defined, the
softkeys PREFERRED and PROTECTION appear when you select DISCONNECT.
17.1-6
(400)
Node Parameters

NNP 95-2035-01-00-B

To configure simple bidirectional connections

CONFIG CONNECT <sn-cc > or <x-sn-cc>
DISCONNECT
TO_CIRCUIT
<sn-cc> or <x-sn-cc>
COMP_CONV
PREFERRED
PROTECTION
NO_CONV
SK000008
where
the first sn-cc or x-sn-cc is the source circuit identifier
the second sn-cc or x-sn-cc is the destination circuit identifier
17.1.5
Configuring Simple Unidirectional Connections

In 3645 MainStreet systems, cards that support simple unidirectional connections
provide a single path between a source and destination device: data and signalling
pass in one direction only. Simple unidirectional connections may be 64 kb/s or
super-rate (see chapter 20.15). Unidirectional connections cannot be protected.
A single circuit can be involved in two simple unidirectional connections at the same
time: as the source in one connection and as the destination in another. The circuit
configured as a source may be completely different from its configuration as a
destination, so one connection can be disconnected without affecting the other.
Note
You must configure the PRI card slot for unidirectional operation before you can
make unidirectional connections (see chapter 20.2). You do not need to configure the
card slot for unidirectional 64 kb/s Codirectional cards.
Node Parameters
(400)
17.1-7


NNP 95-2035-01-00-B
To configure simple unidirectional connections

CONFIG CONNECT <x-sn-cc> or <x-sn-l-cc>
MORE
DISCONNECT
ONE_WAY_TO
<x-sn-cc> or <x-sn-l-cc>
SK000009
where
the first x-sn-cc or x-sn-l-cc is the source circuit identifier
the second x-sn-cc or x-sn-l-cc is the destination circuit identifier
17.1.6
Configuring Broadcast Unidirectional Connections

In 3645 MainStreet systems, cards that support broadcast unidirectional connections
provide a single path between a source and one or more destination devices: data
and signals pass in a single direction only. A single broadcast source can be
connected to up to 250 destinations. The paths may be 64 kb/s or super-rate (see
chapter 20.15). Broadcast unidirectional connections cannot be protected.
A single circuit may be involved in a broadcast and a one-way unidirectional
connection at the same time: as source in one connection and as destination in the
other. The circuit configuration as a source may be completely different from its
configuration as a destination, so one connection can be disconnected without
affecting the other.
This means that one of the destination circuits in a broadcast connection can be
connected back to the source; it is treated as a completely separate connection.
Note
You must configure the DET card slot for unidirectional operation before you can
make unidirectional connections (see chapter 20.2). You do not need to configure the
card slot for unidirectional 64 kb/s Codirectional cards.
Select the BROADCAST softkey. After the first connection is made, the
ADD_BCAST softkey appears for further connections.
Select DISCONNECT and enter the source circuit identifier. To disconnect one of the
broadcast connections, select RMV_BCAST and enter the destination circuit
identifier.
17.1-8
(400)
Node Parameters

NNP 95-2035-01-00-B

To configure broadcast unidirectional connections

CONFIG CONNECT <x-sn-cc> or <x-sn-l-cc>
MORE
DISCONNECT
RMV_BCAST
BROADCAST/ADD_BCAST
SK000010
where
the first x-sn-cc or x-sn-l-cc is the source circuit identifier
the second x-sn-cc or sn-l-cc is the destination circuit identifier
17.1.7
Configuring TS0 Cross-connections

For Dual E1 cards (with a firmware ID of 40 or higher), TS0 can be cross-connected
to any aggregate or transparent data circuit. TS0 can only be cross-connected to
64 kb/s clear channels (channels in which all bits are available for use by user data).
Although TS0 occupies a full 64 kb/s, only NU bits 4 through 8 are transported
(reserved bits 1 through 3 are forced to zero). There are no circuit configuration
options for TS0; it can only be connected or disconnected. For more information on
NU bits, see chapter 20.18.
To configure TS0 cross-connections

The procedure for connecting TS0 is identical to any other connection process,
except that TS0 is the circuit identifier.
CONFIG CONNECT <sn-TS0> or <x-sn-TS0>
TO_CIRCUIT
DISCONNECT
SK000011
where
sn-TS0 or x-sn-TS0 is the TS0 circuit identifier
sn-cc or x-sn-cc is the destination circuit identifier
Node Parameters
(400)
17.1-9

NNP 95-2035-01-00-B
17.2
17.2 Configuring Timing and Synchronization

Configuring Timing and

Synchronization
This chapter describes timing sources and the standalone, ANS and synchronization
status messaging methods for node synchronization. This chapter describes how to
configure:
17.2.1
standalone and ANS synchronization selection

ANS node parameters
ANS link parameters
timing source parameters
Understanding Timing and Synchronization

In a 3600+ MainStreet system, synchronization is done by the Timing card. External
sources of timing can be connected to the 3600+ MainStreet enhanced locally
controlled shelf through bulkhead connectors.
In all other 3600 MainStreet series bandwidth manager systems, synchronization is
done by the SSU or ISSU. In a locally controlled system, the SSU or ISSU resides on
the Control card. External sources of timing can be connected to the SSU or ISSU
through backplane connectors on the locally controlled shelves. In a switching shelf
controlled system, the SSU or ISSU resides on both the switching shelf Control card
and peripheral shelf. External sources of timing can be connected to the SSU or ISSU
through backplane connectors on the switching shelf or on any of the peripheral
shelves connected to it.
HSPSs do not support external timing connectors. Although a peripheral shelf may
be configured to pass timing signals derived from an external source to the
switching shelf, it is still the switching shelf that processes these signals and supplies
system timing to all peripheral shelves.
17.2.2
Timing sources
The Timing card, SSU or ISSU is driven by a timing source selected from the
programmable timing sources available to the system. Each programmable timing
source can be configured as either external or derived.
If configured as external, the synchronization source is an external device connected
to the backplane or bulkhead BNC or DB-type connectors. Only one external source
may be configured for each node, but a redundant external timing source may be
configured for each 3600+ MainStreet node.
Node Parameters
(400)
17.2-1


NNP 95-2035-01-00-B
If configured as derived, the possible synchronization sources and number of

possible sources vary according to system type (see Table 17.2-1).
Table 17.2-1: 3600 MainStreet Series Bandwidth Managers Synchronization Sources
System Type
Shelf
Number of Possible
Synchronization
Sources
Possible Synchronization Sources
Locally controlled system
Locally controlled shelf
2B1Q channel unit,

64 kb/s Codirectional card,
BRI S/T card, DCC, E1 card, MPA
card, T1 card, X.21 PRI card, X.21 ESI
PRI card, V.35 PRI card
3600+ MainStreet system
Enhanced locally
controlled shelf
OC-3 card, STM-1 card,

2B1Q channel unit, BRI S/T card,
DCC, E1 card, MPA card, T1 card,
X.21 PRI card, X.21 ESI PRI card,
V.35 PRI card
Switching shelf controlled

system
Peripheral shelf
Switching shelf
4
8
2B1Q channel unit,

BRI S/T card, DCC, DS-3 card, E1
card, E3 card, MPA card, T1 card,
X.21 PRI card, X.21 ESI PRI card,
V.35 PRI card
A node can be configured to select the current source of synchronization based on a

hierarchy of preferred synchronization sources. For all 3600 MainStreet series
bandwidth managers, preferred synchronization sources can be predefined using a
class system method (class mode). For the 3600+ MainStreet Bandwidth Manager,
preferred synchronization sources can also be selected by the node using a quality
level method (status message mode).
In class mode, the node is assigned a class number (1 to 15 for a locally controlled
system, or 1 to 14 for a 3600+ MainStreet system or switching shelf in a switching
shelf controlled system). The source class is a measure of how desirable a source is:
the lower the class number, the more desirable the source.
In status message mode, a synchronization status message received by the
3600+ MainStreet node from the source defines the quality level of the source. The
current source of synchronization is selected based on the source offering the best
quality level.
In both class and status message mode, if two or more sources have the same class
number or quality level (respectively), the source with the highest priority is
selected. Priority is dictated by a source number assigned to the source (lower source
numbers have a higher priority).

You can build a table of up to four timing sources by configuring synchronization
parameters for the locally controlled shelf. Figure 17.2-1 shows an example of the
table.
17.2-2
(400)
Node Parameters

NNP 95-2035-01-00-B

Figure 17.2-1: Locally Controlled Shelf Timing Source Display

3600 MainStreet
1117-H1-00
Toronto:A
ANS:DISABLED
Alarms:1
Number
Zone ID:1
1
2
3
4
Source
Recovery
Slot A7
Slot A3
External
Slot B5
Auto
Auto
30 sec
Auto
11-May-1997
Node Class:10
Class
Current Class:1
Threshold
2
1
5
15
8:35a
Status
5
5
5
5
Ready
Current
Ready
Ready
Current source of synchronization is number 2 (A3)

External Clock Frequency: Input = 8kHz
CONFIG SYNCH
1-SRC_NUMBER
6-ANS_NODE
2-MAINT
7-
3-ANS_LINK
8-CANCEL
4-NODE_CLASS
9-QUIT
5-EXT_FREQ
0-
3600+ MainStreet enhanced locally controlled shelf

You can build a table of up to four timing sources by configuring synchronization
parameters for the enhanced locally controlled shelf. Figure 17.2-2 shows an
example of the table in status message mode.
Figure 17.2-2: Enhanced Locally Controlled Shelf Timing Source Display Status
Message Mode
3600+ MainStreet
ANS:DISABLED
Number
1
2
3
4
S1117-H1-00
Zone ID:1
Toronto:A
Alarms:1
11-May-1997
Node Class:14
Node Class:14
Threshold
Source
Recovery
Message
External-A
Slot H1
Slot H2
Slot A1-1
Manual
Manual
Manual
Manual
PRS (1)
ST2 (3)
Disabled (2)
--- (2)
5
5
5
5
8:35a
Current Class:5
Status
Current
Ready
Monitoring
Not Ready (AIS)
Current source of synchronization is number 1 (External-A)

Quality level threshold is ST3
CONFIG SYNCH
1-SRC_NUMBER
6-ANS_NODE
Node Parameters
2-MAINT
7-MORE
3-ANS_LINK
8-CANCEL
(400)
4-NODE_CLASS
9-QUIT
5-EXTERNAL
0-
17.2-3


NNP 95-2035-01-00-B
Peripheral shelf
For each peripheral shelf, you can build a table of up to four timing sources.
Figure 17.2-3 shows an example for a peripheral shelf.
Figure 17.2-3: Peripheral Shelf Timing Source Display
3645 MainStreet
Number
1
2
3
4
D117-H1-00
Toronto:P3A
Source
Status
Slot A7
Slot A3
External
Slot B5
Ready
Current
Ready
Ready
External Clock Frequency:
Alarms:1
11-May-1997
8:35a
Input = 8kHz
CONFIG SYNCH
1-SRC_NUMBER
6-
27-
38-CANCEL
49-QUIT
5-EXT_FREQ
10-
Switching shelf
For the switching shelf, you can build a table of up to eight timing sources selected
from any of the timing sources provided by the peripheral shelves. Figure 17.2-4
shows an example of the table.
17.2-4
(400)
Node Parameters

NNP 95-2035-01-00-B

Figure 17.2-4: Switching Shelf Timing Source Display

3645 MainStreet
C117-H1-00
ANS:DISABLED
Number
1
2
3
4
5
6
7
8
Toronto:SWA
Zone ID:1
Source
Recovery
PS3-1,A7
PS2-2,A3
PS4-4,A1
PS6-1,A2
PS3-2,A7
PS2-4,A3
PS4-2,A1
PS6-3,A2
Auto
Auto
Auto
Auto
Auto
Auto
Auto
Auto
Alarms:1
11-May-1997
Node Class:10
Class
5
2
5
5
5
2
5
5
8:35a
Current Class:2
Threshold
5
5
5
5
5
5
5
5
Status
Ready
Current
Ready
Ready
Ready
Ready
Ready
Ready
Current Source of Synchronization number 2 (PS2-2,A3)

External Clock Frequency: Input = 8kHz Output = 8kHz
CONFIG SYNCH
1-SRC_NUMBER
6-ANS_NODE
17.2.3
2-MAINT
7-
3-ANS_LINK
8-CANCEL
4-NODE_CLASS
9-QUIT
5-EXT_FREQ
10-
Synchronization methods
For all 3600 MainStreet series bandwidth manager systems, the programmable
timing source that drives the Timing card, SSU or ISSU can be chosen using one of
two methods: standalone synchronization or ANS.
Standalone
Normally, standalone synchronization is used when a node is used in a single-ended
or point-to-point application. When operating in standalone mode, the node uses
only those timing sources that have been configured at that node.
On all 3600 MainStreet series bandwidth manager systems, preferred standalone
synchronization sources are defined using the class method. For the
3600+ MainStreet system, preferred standalone synchronization sources are defined
using either the class or synchronization status messaging method.
Synchronization status messages are used to determine the current synchronization
source when status message mode is enabled. The timing source offering the best
quality, as indicated by its status message, is selected to be the current source.
Status messages are defined for SONET and SDH interfaces and for external timing
input and output DS1 signals in ESF format. Table 17.2-2 lists the status messages
and their SONET, SDH and DS1 descriptions.
Node Parameters
(400)
17.2-5


NNP 95-2035-01-00-B
Table 17.2-2: Synchronization Status Messages

Status Message
Quality Level
SONET Description
SDH Description
DS1 Description
PRS
Primary reference source

is traceable

traceable (as defined in
ITU-T G.811)

traceable
STU
Synchronized
traceability unknown
Synchronized
Synchronized
ST2
Traceable Stratum 2
holdover
Traceable to SDH
synchronization unit (as
defined in ITU-T G.812T)
Traceable Stratum 2
holdover
ST3
Traceable Stratum 3
holdover
Traceable to SDH
element clock (as defined
in ITU-T G.812L)
Traceable Stratum 3
holdover
SIC
Traceable SONET clock

self-timed
Traceable to synchronous
equipment timing source
(as defined in ITU-T
G.81s (1))
Traceable SONET clock

self-timed
ST4
DUS
Do not use for

synchronization
Do not use for

synchronization
Traceable Stratum 4
free run
Do not use for
synchronization
A source is initially defined as having a quality level of STU until a valid

synchronization status message is received. This means sources that do not support
or are not enabled for status message reception always have a quality level of STU.
Sources having a current quality level below a configured quality threshold are
treated as unavailable and are not used for synchronization. For example, a source
with a quality level of DUS cannot become the current synchronization source for
the node.
The default value for the quality level threshold is ST3, and the range of valid
messages is PRS to ST3. The Timing card internal Stratum 3 clock has a quality level
of ST3 and is always available regardless of the quality level threshold. The quality
level threshold cannot be set to SIC, ST4 or DUS because the Timing card internal
Stratum 3 clock would be selected as the current source before any source having
these quality levels.
If both ANS and status message modes are used for 3600+ MainStreet node
synchronization, there is no direct method to compare class and quality levels, so a
translation table is used to select the best source of timing. The translation table is
configurable through NMTI. Table 17.2-3 lists the default values for the translation
table.
17.2-6
(400)
Node Parameters

NNP 95-2035-01-00-B

Table 17.2-3: Translation Table Default Values

Quality Level
Status Message
Class
PRS
STU
ST2
11
ST3
14
SIC
ST4
DUS
As an example, assume the best standalone synchronization source has a quality

level of PRS and the best ANS source has a class rating of 3. Using the default values
listed in Table 17.2-3, PRS maps to class 5, so the selected source of synchronization
would be the ANS source that has a class 3 rating.
For definitions of the status messages listed in Table 17.2-3, see Table 17.2-2.
ANS
ANS is used to give each node access to all timing sources in the network. This lets
all nodes receive timing signals from the same source to ensure that network
synchronization is maintained.
ANS uses CPSS to transport synchronization information between ANS nodes
(CPSS is described in chapter 17.6). ANS works with CPSSv1 or CPSSv2, but is not
tied to the topology of the CPSS network. Changes in the CPSS network are
transparent to the ANS network. When the CPSS network heals itself after the failure
of a CPSS link, there is no change in synchronization sources unless the failure
affected the ANS topology.
With ANS you can configure any valid link as an ANS link regardless of the link
CPSS configuration. A valid ANS link may carry no CPSS channels, one CPSS
channel, or more than one CPSS channel.
In a system running CPSSv2, ANS takes advantage of the improved CPSS packet
transmission services that operate at the network layer. These services include better
error detection, larger packets (for higher throughput) and a new datagram service
(for better performance).
ANS nodes can be organized into independently synchronized groups, called zones,
explicitly identified by a zone identifier.
Note
The communication of ANS messages from one zone to another is not supported.
Node Parameters
(400)
17.2-7


NNP 95-2035-01-00-B
ANS links
ANS links are configured between ANS nodes that are one hop away from each
other (a hop is a point-to-point link, free of intermediate nodes, between two pieces
of network equipment).
The node at the far end of an ANS link is called an adjacent node. Each ANS link is
configured with the node number of the adjacent node. Each adjacent node
represents a potential source of synchronization.
Note
If the far end of an ANS link terminates on a switching shelf controlled system, the
adjacent node is always taken to be the switching shelf, even though the link
terminates on a peripheral shelf.
The path used to communicate with an adjacent node is determined by the CPSS
network and does not actually have to be on an ANS link. However, ANS protocol
operation is always based on the ANS network topology, so that hop counts are ANS
links and not CPSS links.
ANS nodes exchange ANS Update Messages to learn about the existence of all
potential timing sources in the network and automatically generate a map of these
timing sources. Whenever a configuration change occurs (for example, if a new node
is brought online or a timing source is reconfigured), the map is updated.
The best source of synchronization in the networkthe one with the lowest class
numberis identified as the ANS master.
Every ANS node derives synchronization from the ANS master through the
least-hop path to the ANS master. The adjacent node that constitutes the first hop
towards the ANS master is called the ANS source of the node. Every adjacent node
is not necessarily an ANS source. An adjacent node is only an ANS source when it
actively provides synchronization to a given node.
Figure 17.2-5 shows an example ANS network with Node C as a stand-alone feeder
node and Node Y as the current ANS master. Node X has two ANS links: link 1-1 to
Node A and link 2-1 to Node B. Link 3-1 is a non-ANS link to feeder Node C, which
uses stand-alone synchronization.
Nodes A and B are adjacent nodes to Node X because they are each at the far end of
a link one hop away. The path to the ANS master through Node A offers a four-hop
path to Node Y and the path through Node B offers a two-hop path. Because Node
B offers the fewer number of hops to the ANS master, Node B is the current ANS
source to Node X and it actively provides synchronization from Node Y to Node X.
Node A is only a potential source of synchronization.
17.2-8
(400)
Node Parameters

NNP 95-2035-01-00-B

Figure 17.2-5: Example of an ANS Network

Adjacent
node
1-1
C
3-1
2-1
X
Stand-alone
feeder node
ANS master
Adjacent node
and ANS source
5446
Bidirectional and unidirectional ANS links

The adjacent node must be specifically identified during configuration. A link is
unidirectional when the adjacent node at only one end of the link is specified.
Bidirectional links must be configured from both nodes. Unidirectional and
bidirectional links affect only the direction of synchronization; they do not affect
normal communications between nodes.
In the example network in Figure 17.2-5, there are three possible configurations if
you are logged onto Node X.
If the ANS link between Node X and Node B is configured only from Node X
(Node X identifies Node B as its adjacent node but Node B does not identify
Node X as its adjacent node), the link is unidirectional from Node B to Node X.
Synchronization is always incoming to Node X from Node B.
If the ANS link between Node X and Node B is configured only from Node B
(Node B identifies Node X as its adjacent node), the link is unidirectional from
Node X to Node B. Synchronization is always outgoing to Node B from Node X.
If the ANS link between Node X and Node B is configured from both Node B and
Node X (both nodes identify the other node as adjacent), the link is bidirectional.
Synchronization may be incoming from Node B or it may be outgoing to Node B
from Node X.
Whether an ANS link is unidirectional or bidirectional affects how the ANS network
topology stabilizes. For example, in Figure 17.2-5, if ANS link 2-1 is configured as
unidirectional from Node X to Node B, Node X cannot use Node B as its ANS
source. In this case, the ANS master cannot be reached from Node X through Node B
and Node X must use Node A as its ANS source.
More than one ANS master may be active at the same time. For example, if the
lowest-class number is shared by a number of sources, an ANS node selects the ANS
master that is the fewest number of hops away from it.
Node Parameters
(400)
17.2-9


NNP 95-2035-01-00-B
If an ANS node can reach an ANS master by more than one equal cost path, the node
chooses the path offered by the adjacent node with the lowest CPSS node address.
If the ANS network changes, the ANS network topology adapts to the change and
restabilizes. For example, if a better timing source becomes available or the existing
ANS master fails, a new ANS master is selected and, if necessary, ANS nodes choose
new ANS sources to reach the new ANS master.
ANS zones
Within a network it may be desirable or necessary to define zones that have
independent timing hierarchies. For example, a network that links North America to
Europe would require a North American zone and a European zone to
accommodate the differences between the two timing reference standards.
Figure 17.2-6 shows a network divided into two zones, 1 and 2. Zone 1 could be the
North American zone and Zone 2 the European zone.
Figure 17.2-6: ANS Zones
Node
I
Node
A
Node
C
Intra-zone
links
Node
H
Node
E
Intra-zone
links
Node
D
Inter-zone
link
Node
B
Node
F
Intra-zone
links
Node
J
Zone 2
Node
G
Zone 1
4447
You create zones by assigning zone identifiers to ANS nodes. All ANS nodes with
the same zone identifier belong to the same zone. ANS messages are exchanged only
on intra-zone links between nodes with like zone identifiers. ANS links cannot be
configured on inter-zone links between nodes in different zones.
Note
With CPSSv2, all nodes in a zone must be contained in a single CPSSv2 domain; an
ANS zone cannot span more than one CPSSv2 domain.
In each ANS zone, an ANS master is selected to be the current source of

synchronization for all ANS nodes within that zone. A change in the
synchronization network in one zone is transparent to all other zones.
17.2-10
(400)
Node Parameters

NNP 95-2035-01-00-B

Note
The node at the far end of an ANS link (an adjacent node) cannot be a stand-alone
synchronized node. This means a feeder node such as the 3612, 3620, 3624, 3630 and
8230 MainStreet nodes or FRS cannot be an adjacent node. A stand-alone
synchronized node can be connected to an ANS node, but not through an ANS link
(see Node C, Figure 17.2-5).
17.2.4
Configuring Timing and Synchronization

You use the procedures in this chapter to configure:
ANS node parameters

ANS links
timing sources
synchronization status messaging
Table 17.2-4 lists the ANS and timing source configuration parameters. Each
parameter has a list of options; default options are marked by an asterisk.
Note
Before configuring ANS, make sure that you have configured the CPSS node
parameters, including the CPSS node number (see chapter 17.6).
Table 17.2-4: Timing and Synchronization Configuration Parameters and Options

3600+
Control
Card
Control
Card
DS-3 and
E3 Card
Parameter
Options
ANS
ANS enable/disable
enabled
disabled*
Enabling or disabling ANS on a link
enabled
disabled
ANS zones
1 to 255
Link failure threshold
0 to 10 (* = 5)
Link failure recovery time
1 to 255 (* = 30)
SSU failure threshold
1 to 5 (* = 1)
SSU failure recovery time
1 to 255 (* = 15)
Node Parameters
(400)
17.2-11

3600+
Control
Card
Control
Card

NNP 95-2035-01-00-B
DS-3 and
E3 Card
Parameter
Options
Derived and external timing sources
external
derived
Standalone Timing Source
Timing source selection
external
derived
undefined
Timing source enable/disable
enabled
disabled*
Timing source selection
selected
deselected*
Node class number
1 to 14 for enhanced locally

controlled and switching shelves
1 to 15 for a locally controlled shelf
Source failure recovery method
auto
30 s
1 min
10 min
30 min
manual
Source failure threshold
0 to 30 (* = 5)
unlimited
Timing source class number
1 to 14 for enhanced locally

controlled and switching shelves
1 to 15 for a locally controlled shelf
External timing input
8 kHz
2 MHz
1.544 MHz
composite clock
External timing output
8 kHz
2 MHz
1.544 MHz
no clock
Table 17.2-5 lists the locations of the ANS and timing source configuration
procedures.
Table 17.2-5: Timing and Synchronization Configuration Procedures
17.2-12
Section
ANS links display
17.2.6
Timing source identification
17.2.7
Timing source display
17.2.7
(400)
Node Parameters

NNP 95-2035-01-00-B

Note
17.2.5
Configuring ANS Node Parameters

At the node level, you can:
configure the zone

enable or disable ANS
Configuring the zone
ANS nodes are organized into groups called zones. Each zone is independently
synchronized. The zone identifier (ZONE_ID_#) is used to identify the ANS zone to
which this node belongs. Each zone can contain up to 50 ANS nodes. Each locally
controlled shelf and switching shelf is counted as one node.
Note
You cannot change the zone identifier while ANS is enabled on the node. If ANS is
enabled, you must disable it before you change the zone identifier.
The communication of ANS messages from one zone to another is not supported.
To configure the zone identifier, see the procedure To enable and disable ANS on
node.
To enable and disable ANS on a node

After you have completed the link and source configuration and configured ANS
node parameters, you can enable a node for ANS operation. Disabling the ANS
option returns a node to stand-alone synchronization.
Node Parameters
(400)
17.2-13


NNP 95-2035-01-00-B
Note
When you change the method of synchronization for a node, its timing sources
remain as configured. They are not reset to default values.
CONFIG SYNCH ANS_NODE
ENABLE/DISABLE*
ZONE_ID_#
<number>
SK000012
where number is 1 to 255
17.2.6
Configuring ANS Link Parameters

You can configure an ANS link only on a slot or link that is not configured for
stand-alone synchronization. At the link level, you can:
display all the links currently enabled for ANS on an ANS node
enable or disable ANS on the link and identify the adjacent node
configure the link failure threshold and recovery time
configure the Timing card or SSU failure threshold and recovery time
Note
While a slot or link is configured for ANS:
you cannot configure the slot or link as a stand-alone

you cannot change the type configuration of the slot or link
you cannot change the device gender mode of a PRI link
For ANS link configuration, use the Craft Interface for pre-Release 6.1. For
Release 6.1 and newer releases of software, use the NMTI.
To display ANS links

CONFIG SYNCH ANS_LINK
17.2-14
(400)
Node Parameters

NNP 95-2035-01-00-B

Figure 17.2-7 shows a sample ANS link display. If there are more ANS links
configured than fit on one screen, use the PREV_PAGE and NEXT_PAGE softkeys
to scroll through the list.
Figure 17.2-7: ANS Links Display
3645 MainStreet
ANS
Link
1-A1-A
1-A1-B
1-B2
1-A2
1-A3
1-A8-A
1-A8-B
2-A1-A
3-A1-B
4-B2
5-A2
6-A1-A
7-A1-B
8-B2
CARD
Type
DUAL_T1
DUAL_T1
DUAL_T1
T1
V35_PRI
DUAL_T1
DUAL_T1
DUAL_T1
DUAL_T1
T1
DUAL_T1
DUAL_T1
DUAL_T1
DUAL_T1
D117-H1-00
Toronto:P3A
CPSS
Far End Node
2
2
3
5
32
34
31
20
59
21
24
25
62
87
Alarms:1
11-May-1997
Link Failure
Threshold
Time (min)
5
30
5
30
5
30
5
30
5
30
5
30
5
30
5
30
5
30
5
30
5
30
5
30
5
30
5
30
8:35a
SSU Failure
Threshold Time (min)
1
60
1
60
1
60
1
60
1
60
1
60
1
60
1
60
1
60
1
60
1
60
1
60
1
60
1
60
CONFIG SYNCH ANS_LINK "??-??"

Enter a Slot Number.
1-PREV_PAGE
6-
2- NEXT_PAGE
7-
38-CANCEL
49-QUIT
50-
Enabling and disabling ANS on a link

Each enhanced locally controlled, locally controlled or peripheral shelf supports up
to 32 ANS links and can be connected to up to 30 adjacent nodes. A switching shelf
controlled system with 8 peripheral shelves supports 256 ANS links. Parallel ANS
links to the same adjacent node are recommended when possible.
You can configure the following links as ANS links:
Single and Dual T1 and DS-3 or DS-3 II links (on a DS1 basis)
Single and Dual E1 and E3 links (on an E1 basis)
V.35 PRI (DTE)
X.21 PRI (DTE)
MPA card link (DTE)
OC-3 and STM-1 card links (the card must be installed in the active HSA subslot)
When ANS is enabled on a link, ANS is no longer configured on CPSS circuits.

Instead, you must identify the links that can be considered as candidates for use as
synchronization sources.
Node Parameters
(400)
17.2-15


NNP 95-2035-01-00-B
Note
ANS cannot be configured on an MPA card link configured as DCE on an X.21 PRI
or a V.35 PRI link.
To enable ANS on a link, you select ANS_LINK and enter a link identifier. The
system displays FAR_END on the command line and prompts for the CPSS address
of the adjacent node at the far end of the link. To disable a link, you enter the link
identifier and select DISABLE.
Note
You cannot use the default node number (1022) or the CPSS address of a peripheral
shelf to identify an adjacent node. If the adjacent node is a peripheral shelf, enter the
CPSS address of its switching shelf.
To enable and disable ANS on a link, see the procedure To configure ANS links.
Link failure threshold

The link failure threshold is the number of times in an hour an ANS link is allowed
to fail. If the link fails more than this number of times, the link is declared unreliable
and is taken out of service as a potential source of synchronization for the node (the
link continues to carry regular user data). An ANS Link Unreliable alarm is
generated.
You can select LINK_RECOV and FAIL_THRES, and define link failure threshold in
the range 0 to 10, or UNLIMITED. When you select UNLIMITED, the link is never
declared unreliable, regardless of the number of failures each hour.
To configure the link failure threshold, see the procedure To configure ANS links.
Link failure recovery time

The link failure recovery time is the number of minutes an out-of-service ANS link
exhibits a failure rate less than the failure threshold before the link returns to service.
You can select LINK_RECOV and FAIL_TIMED, and define link failure recovery
time in the range 1 to 255 minutes or INFINITY. When you select INFINITY, the link
remains out-of-service until manually recovered.
To configure the link failure recovery time, see the procedure To configure ANS
links.
17.2-16
(400)
Node Parameters

NNP 95-2035-01-00-B

SSU failure threshold

The SSU failure threshold is the number of times the Timing card or SSU is allowed
to fail to acquire or maintain lock on the ANS link (for example, because of excessive
jitter or a momentary loss of signal). If the Timing card or SSU fails to synchronize
to the link more than this number of times, the link is declared unreliable and is
taken out-of-service as a potential source of synchronization for the node (the link
continues to carry regular user data).
You can select SSU_RECOV and FAIL_THRES, and define the SSU failure threshold
in the range 1 to 5.
To configure the SSU failure threshold, see the procedure To configure ANS links.
SSU failure recovery time

The SSU failure recovery time is the number of minutes an ANS link remains
out-of-service after exceeding the SSU failure threshold. You can select SSU_RECOV
and FAIL_TIMED, and define SSU failure recovery time in the range 1 to 255
minutes, or INFINITY. When INFINITY is selected, the link remains out-of-service
until manually recovered.
Note
SSU failure parameters apply only when the link is the current source of
synchronization for the node.
To configure the SSU failure recovery time, see the procedure To configure ANS
links.
Node Parameters
(400)
17.2-17


NNP 95-2035-01-00-B
To configure ANS links

CONFIG SYNCH ANS_LINK <link_id>
<far-end_node>
DISABLE/ENABLE
LINK_RECOV
FAIL_THRES
<threshold>
UNLIMITED
SSU_RECOV
FAIL_TIMED
<time>
INFINITY
SK000013
where
link_id is the slot or link identifier
far-end_node is the CPSS address (1 to 999) of the adjacent node at the far end of this link
threshold is the number of times (0 to 10) the link can fail each hour (5*), or the number of times the SSU
can fail (1*)
time is the number of minutes (1 to 255) the out-of-service link must show a failure rate less than the failure
threshold before the link is returned to service (30*), or the number of minutes (1 to 255) the link remains
out-of-service after exceeding the SSU failure threshold (15*)
Note
The UNLIMITED option applies only to the LINK_RECOV parameter.
17.2.7
Configuring Timing Sources

On a locally controlled or enhanced locally controlled shelf, you can program up to
four timing sources. On each peripheral shelf, you can program up to four timing
sources for use by the switching shelf. On a switching shelf, you can program up to
eight timing sources from among the peripheral shelves.
You can configure each programmable timing source as:
external
derived
17.2-18
(400)
Node Parameters

NNP 95-2035-01-00-B

Programmable external sources

When a programmable timing source is configured as external, it can obtain a clock
from the following backplane or bulkhead connectors.
For a peripheral shelf, switching shelf, or a locally controlled shelf, a 2.048 MHz
or an 8 kHz timing source can be connected to BNC connector J13 on the

equipment backplane.
For a peripheral shelf or a locally controlled shelf, a 1.544 MHz AMI or DDS
composite clock timing source can be connected to DB15 connector J17 on the
equipment backplane. These signals can be used only if a GFC2 or GFC3 is
installed.
For a 3600+ MainStreet enhanced locally controlled shelf, a 2.048 MHz or an
8 kHz NRZ timing source can be connected to BNC connectors RXA and RXB on
the shelf bulkhead. A DS1 or composite clock timing source can be connected to
the 120 W I/O DB-25 connector on the shelf bulkhead. The 3600+ MainStreet shelf
has redundant input ports (A and B) for each timing source type.
For 3600 MainStreet series bandwidth managers, you can configure only one source
as external (EXTERNAL) for each node. For 3600+ MainStreet Bandwidth Managers,
you can configure two sources as external (EXT_PORT_A and EXT_PORT_B) for
each node. External sources may be an input to the node or an output from the node.
For more information about external timing inputs and outputs, see Installation, Task
1500: Connecting External Timing Sources and Receivers.
Programmable derived sources

When you configure a programmable timing source as derived, it can obtain a clock
from any primary rate link or synchronous data circuit (see Table 17.2-1). You can
configure any of the programmable timing sources on a node as derived.
Internal source
In addition to the programmable timing sources, the node has an internal crystal
oscillator that supplies a 2.048 MHz 25 ppm timing signal. Typically, the internal
source class is assigned the highest class number so the node can synchronize to it
only under two conditions:
when all programmable timing sources or ANS links fail

when the current source is lost (in this case, the node switches to holdover
operation and searches for an alternate source)
When synchronized to the internal source, the timing is said to be free-running or in
holdover. Only this default timing source may be internal; none of the
programmable timing sources may be configured as internal.
Identifying a timing source

Source numbers (1 to 4 on an enhanced locally controlled, locally controlled or
peripheral shelf and 1 to 8 on a switching shelf) are used to identify preferred
synchronization sources in the event that sources have the same class or quality
level.
Node Parameters
(400)
17.2-19


NNP 95-2035-01-00-B
Note
Using the timing source as a reference, the SSU creates a 2.048 MHz clock that
conforms to ITU-T recommendation G.703. This clock is available at J14 on the
equipment backplane.
For timing sources, you can:
display the timing sources

configure an external or derived source
enable and select a source
assign a class number to a timing source or a node
enable synchronization status messaging for a source
configure the source failure threshold and recovery method
specify the frequency of external timing inputs and outputs
To display the timing sources

CONFIG SYNCH
Figure 17.2-8 shows a sample display. Table 17.2-6 lists the fields on this display.
Figure 17.2-8: Timing Source Display
3600 MainStreet
1117-H1-00
ANS:ENABLED
Number
1
2
3
4
ANS
Toronto:A
Zone ID:1
Source
Slot A7
Slot A3
External
Slot B5
N/A
Recovery
Auto
Auto
30 sec
Auto
N/A
Alarms:1
11-May-1997
Node Class:10
Class
2
5
1
15
N/A
8:35a
Threshold
5
5
5
5
N/A
Current Class:1
Status
Ready
Ready
Current
Ready
Ready
Current source of synchronization is number 3 (External)

External Clock Frequency: Input = 8kHz
CONFIG SYNCH
1-SRC_NUMBER
6-ANS_NODE
17.2-20
2-MAINT
7-
3-ANS_LINK
8-CANCEL
(400)
4-NODE_CLASS
9-QUIT
5-EXT_FREQ
0-
Node Parameters

NNP 95-2035-01-00-B

Table 17.2-6: Timing Source Status

Heading
Description
Number
The number of the programmable timing source.
Source
The source from which the timing is extracted.
Recovery
The method used to resynchronize to the source when it has recovered from a failed
state.
Class
or
Message
The class configured for this source.
Threshold
The maximum number of failures each hour allowed for this source (or alternate source
on the 3600+ MainStreet Bandwidth Manager) when it is the current source of
synchronization.
Status
Displays the source status as follows:

Disabled:
The quality of the source as indicated by the received status message.
the source has been deliberately disabled (by selecting DISABLE)

the source is in the default state (never enabled)
Manual Recovery:
the source in timed recovery has failed

the system has failed to recover the source four times in a row
the source has exceeded the permissible failure rate
Not Ready: The source is not available for system timing. If the source is a primary rate
link, there is a primary rate alarm. If the source is a data circuit, the circuit is out of
synchronization.
Ready: The source is available for system timing.
Acquiring: The Timing card, SSU or ISSU is currently trying to synchronize to the source.
Current: The source is providing system timing.
Auto Rec: The source has failed as the current source of synchronization, but will be
available to the system as soon as it has recovered.
Time Rec: The source has failed as the current source of synchronization, but the
system is checking at timed intervals to see if it has recovered.
Cannot Lock: The system is presently unable to take timing from the current source. It
tries to take timing from the source again soon after this state has been entered.
Displays the alternate source as follows:
Validating: The Timing card is currently trying to synchronize to the alternate source.
Monitoring: The alternate source is providing system timing.
Node Parameters
(400)
17.2-21


NNP 95-2035-01-00-B
Timing source parameters

Using the SRC_NUMBER softkey, you can:
for 3600 MainStreet series bandwidth managers

configure a source as EXTERNAL or DERIVED
enable and select sources
specify the source CLASS number
for 3600+ MainStreet Bandwidth Managers
configure a source as EXT_PORT_A, EXT_PORT_B, or DERIVED
enable and select sources
specify the source CLASS number or enable or disable STATUS_MSG
reception for the source
Note 1
Only sources that support synchronization status messaging can be configured for
STATUS_MSG reception. Valid sources are SONET and SDH interfaces and external
timing signals in DS1 framing format. If an invalid source is configured for
STAUS_MSG, the message The specified source does not support synchronization
status messaging. is displayed.
Note 2
Both CLASS and STATUS_MSG cannot be enabled on a 3600+ MainStreet
Bandwidth Manager at the same time. Error messages are displayed indicating the
current mode selected.
For 3600 MainStreet series bandwidth managers, when you define a DERIVED
source, you must specify the slot and link identifier or the peripheral shelf and
source number where it originates. For 3600+ MainStreet Bandwidth Managers,
when you define an HSA card as a DERIVED source, the following rules apply:
If the HSA slot is configured for simplex traffic protection, the derived source
must be configured at the HSA slot or HSA subslot A level. If subslot B is

specified, the message That slot cannot be a source of system timing. is
displayed.
If the HSA slot is configured for 1+1 traffic protection, the derived source must
be configured at the HSA slot level. If subslot A or B is specified, the message
That slot is configured for 1+1 protection. Enter an HSA slot. is displayed.
If the HSA slot is configured for ring mode traffic protection, the derived source
must be configured at the HSA subslot level. If the HSA slot is specified, the
message That slot is configured for ring mode. Enter an HSA subslot. is
displayed.
You can also specify a previously defined source as UNDEFINED before redefining
it.
For a timing source to become the current (active) source, it must be enabled and
selected. The system automatically selects the source with the highest quality; this is
indicated by the lowest class number or, if status messaging is selected, it is
indicated by the received status message.
17.2-22
(400)
Node Parameters

NNP 95-2035-01-00-B

When you ENABLE a source, it becomes available to the network as a source of

timing. When an enabled source has a higher quality than the current source of
timing, it is automatically selected as the new source of timing. When you DISABLE
a source, that source becomes unavailable to the network as a source of timing.
Note
You can enable a timing source on a peripheral shelf only from the associated
switching shelf.
The SELECT and DESELECT softkeys are used for maintenance operations. When
you SELECT a source, you force the system to use this source as its current timing
source. This source remains the current source of synchronization until it fails or you
DESELECT it, even if there is another source with a higher-quality value. The status
of the source changes from Ready to Current (see Table 17.2-6). When you
DESELECT a source, normal operation begins again. The source status changes from
Current to Ready (see Table 17.2-6), and the system automatically selects the Ready
source with the highest quality as the current source.
You can assign a class number to each programmable timing source (CLASS) and to
the default internal timing source of the node (NODE_CLASS) to determine source
selection. To increase the preference for a source, assign it a low class number; to
decrease the preference for a source, assign it a high number.
The default node class number is 15 in a locally controlled system and 14 in a
enhanced locally controlled or switching shelf controlled system. A node class
number of 15 or 14 indicates a node that will not normally supply network timing.
The network looks only at the class number when determining the source
hierarchyit makes no distinction between node class numbers and source class
numbers.
Note
The system never uses a source configured with a class number higher than the node
class.
To configure the timing source parameters, see the applicable system procedure:
To configure timing sources for locally controlled shelves

To configure timing sources for switching shelves
To configure timing sources for peripheral shelves
To configure timing sources for enhanced locally controlled shelves
Timing source failures

Timing source failures can either be quality- or link-related.
Node Parameters
(400)
17.2-23


NNP 95-2035-01-00-B
Quality-related failures are caused by exceptional jitter, phase hits and frequency
deviations, causing the SSU to lose synchronization with the timing source. With
quality-related failures, the link is still active and can carry data. You can configure
a source failure threshold to disable a synchronization source when excessive
quality-related failures occur.
Link-related failures are caused by loss of clock signal, loss of frame or excessive bit
errors, causing the SSU to lose synchronization with the timing source. With
link-related failures, the link is down and does not carry data. You can configure a
source failure recovery method for synchronization sources that are disabled due to
link-related failures.
Source failure threshold
The source failure threshold is the number of times in an hour a timing source is
allowed to fail as the current synchronization source. If the source failures exceed the
threshold, the source is automatically disabled until it is manually re-enabled.
Source failure threshold is in the range of 0 to 30 failures each hour or UNLIMITED.
When you select UNLIMITED, the source is never declared disabled, regardless of
the number of failures each hour.
To configure the source failure threshold parameters, see the applicable system
procedure:

Source failure recovery method
The source failure recovery method determines how and when a previously failed
source is declared ready. These methods apply only to a source that was previously
the current source of synchronization. If a source fails while it is not the current
source of synchronization, it enters the Not ready state.
You can select one of three source failure recovery methods.
AUTO for automatic recovery: If automatic recovery is selected, a failed source
17.2-24
becomes available to the network (enters the ready state, see Table 17.2-4) as soon
as it recovers. The network tries to synchronize to the recovered source if it has a
lower class number than the current source.
30_SEC, 1_MIN, 10_MIN or 30_MIN for a timed recovery: If timed recovery is
selected, the system checks after the specified time interval up to four times to see
if the source has recovered. If the source has recovered, the source becomes
available to the network (enters the ready state) and will become the current
source if its class number is lower than that of the current source. If the source has
not recovered by the end of the fourth check, the system places the source in the
disabled state.
MANUAL for manual recovery: If manual recovery is selected, the system places
the failed source in the disabled state. The source is not used as a source of
synchronization until it is manually enabled.
(400)
Node Parameters

NNP 95-2035-01-00-B

To configure the source failure recovery method parameters, see the applicable
system procedure:

External timing frequency
The following subsections explain how to configure external timing input and
external timing output.
External timing input for 3600 MainStreet series bandwidth managers
Using the EXT_FREQ and INPUT softkeys, you can configure one external timing
input for each node as:
8_kHz if the external timing source has a frequency of 8 kHz (locally controlled,
switching, or peripheral shelf), or 64 kHz or 1.544 MHz (locally controlled or

peripheral shelf)
2_MHz if the external timing source has a frequency of 2 MHz (locally controlled,
switching or peripheral shelf)
COMP_CLOCK if the external timing source has a frequency of 64 kHz
composite clock and if the source of synchronization is an external source
accepted by the GFC2 or GFC3 (locally controlled or peripheral shelf); an ISSU
module on the Control card is required for the COMP _CLOCK functionality to
work
1.5_MHz if the external timing source has a frequency of 1.544 MHz (connected
directly to the switching shelf backplane)
To configure external timing input parameters, see the applicable system procedure:

External timing input for 3600+ MainStreet Bandwidth Managers
Using the EXTERNAL and INPUT softkeys, you can configure two external timing
inputs for each node as:
NRZ if the external timing source is connected to a bulkhead Rx BNC connector.
Node Parameters
Then, using the OPTION softkey, you can select 8_KHZ or 2048_KHZ if the
external timing source has a frequency of 8 kHz or 2.048 kHz, respectively.
DS1 if the external timing source is connected to the bulkhead 120 W connector.
Then, using the OPTION softkey, you can select D4_FRAME or ESF_FRAME if
the input signal is in D4 or ESF framing format, respectively.
COMP_CLOCK if the external timing source is connected to the bulkhead 120 W
connector and the external timing source has a frequency of 64 kHz. Then, using
the OPTION softkey, you can select FREQ_LOCK to specify that the timing
source signal is not a DDS composite clock signal or PHASE_LOCK if the signal
is a DDS composite clock signal.
(400)
17.2-25


NNP 95-2035-01-00-B
Using the OPTION softkey, you can enable or disable a bridged mode to specify that
the signal of any external input timing source is to electrically terminate on the
active Timing card (BRIDGE_OFF) or that neither the active nor inactive Timing
card is to electrically terminate the input timing signal (BRIDGE_ON).
To configure external timing input parameters, see the procedure To configure an
external input timing source for the enhanced locally controlled shelf.
External timing output for 3600 MainStreet series bandwidth managers
Using the EXT_FREQ and OUTPUT softkeys, you can configure the frequency of
one external timing output for each switching shelf as:
1.5_MHz for an output frequency of 1.544 MHz

8_kHz for an output frequency of 8 kHz
2_MHz for an output frequency of 2 MHz
NO_CLOCK for no frequency output
To configure external timing output parameters, see the procedure To configure

timing sources for switching shelves.
External timing output for 3600+ MainStreet Bandwidth Managers
Using the EXTERNAL and OUTPUT softkeys, you can configure the frequency of
two external timing outputs for each enhanced locally controlled shelf as:
NRZ_FREQ if the timing receiver is connected to a bulkhead Tx BNC connector.
Then, you can select 8_KHZ or 2048_KHZ to specify the output signal frequency.
DS1_FRAME if the timing receiver is connected to the bulkhead 120 W connector.
Then, you can select D4_FRAME or ESF_FRAME to specify the framing format
of the output DS1 signal.
PORT_A or PORT_B (or both) to specify to which port the external timing
receiver is connected. Then, you can select SYSTEM or HSA_SLOT to specify that
the source of the timing signal is the Timing card Stratum 3 clock or an OC-3 or
STM-1 card installed in an HSA slot. If HSA_SLOT is configured, the following
rules apply:
If the HSA slot is configured for simplex traffic protection, the derived
source must be configured at the HSA slot or HSA subslot A level. If subslot
B is specified, the message That slot cannot be a source of system timing.
is displayed.
If the HSA slot is configured for 1+1 traffic protection, the derived source
must be configured at the HSA slot level. If subslot A or B is specified, the
message That slot is configured for 1+1 protection. Enter an HSA slot. is
displayed.
If the HSA slot is configured for ring mode traffic protection, the derived
source must be configured at the HSA subslot level. If the HSA slot is
specified, the message That slot is configured for ring mode. Enter an HSA
subslot. is displayed.
17.2-26
(400)
Node Parameters

NNP 95-2035-01-00-B

To configure external timing output parameters, see the procedure To configure

timing output for an external timing receiver for the enhanced locally controlled
shelves.
DDS composite clock
The DDS composite clock provides synchronization for intra-office connections of
DS0 level signals. When you select COMP_CLOCK as an external timing input
source, you are configuring the system for phase lock operation. Phase lock to a
clocking source is referred to as phase or byte synchronization. Phase lock ensures
that the transmitter and the receiver achieve proper alignment by identifying the
beginning and end of a frame or byte.
Note
An ISSU module on the Control card is required for the COMP_CLOCK phase
locking operation. If you attempt to enable the COMP_CLOCK when there is no
ISSU module present on the Control card, the warning message ISSU required for
phase lock appears and a Revision Feature/Mismatch alarm is raised.
COMP_CLOCK must be configured before the external timing source becomes the
current synchronization source for a locally controlled or peripheral shelf. If you try
to configure COMP_CLOCK to enable the phase lock operation after the external
timing source has been locked, the warning message External source has already
been locked by the system appears.
Figure 17.2-9 shows a sample display of a 3600 MainStreet node configured for the
DDS composite clock (and phase lock operation).
Figure 17.2-9: DDS Composite Clock Display
3600 MainStreet
1117-H1-00
ANS:DISABLED
Number
1
2
3
4
Toronto:A
Zone ID: 1
Source
Ext-CC
Slot A2
Undefined
Undefined
Alarms:1
Node Class:15
11-May-1997
8:35a
Current Class:1
Recovery
Class
Threshold
Manual
Manual
Manual
Manual
1
2
15
15
5
5
5
5
Status
Current
Disabled
Disabled
Disabled
Current source of synchronization is number 1 Composite Clock

External Clock Frequency: Input = Composite Clock
CONFIG SYNCH EXT_FREQ INPUT
1-2_MHZ
6-
Node Parameters
27-
3-8_kHZ
8-CANCEL
(400)
49-QUIT
50-
17.2-27


NNP 95-2035-01-00-B

CONFIG SYNCH
NODE_CLASS
EXT_FREQ
<class>
INPUT
2_MHZ
8_kHZ
SRC_NUMBER
COMP_CLOCK
<source>
SELECT/
DESELECT*
CLASS
RECOVERY
<class>
AUTO 30_SEC
1_MIN
THRESHOLD
SOURCE
ENABLE/
DISABLE*
<failures> UNLIMITED
10_MIN
30_MIN
MANUAL
EXTERNAL
DERIVED UNDEFINED
<sn> or <sn-l>
SK000014
where
class is 1 to 15
source is 1 to 4
failures is the number of failures (0 to 30) each hour (5*)
sn or sn-l is the slot or slot and link identifier where the derived source of timing originates
17.2-28
(400)
Node Parameters

NNP 95-2035-01-00-B


CONFIG SYNCH
NODE_CLASS
<class>
INPUT
8_kHZ
SELECT/
DESELECT*
2_MHZ
CLASS
<class>
AUTO 30_SEC
SRC_NUMBER
EXT_FREQ
OUTPUT
1.5_MHZ
RECOVERY
NO_CLOCK
<source>
SOURCE
THRESHOLD
ENABLE/
DISABLE*
1_MIN 10_MIN 30_MIN
MANUAL
EXTERNAL
DERIVED
UNDEFINED
<p_shelf>
<s_number>
SK000015
where
class is 1 to 14 for a switching shelf
source is 1 to 8 for a switching shelf
p_shelf is the peripheral shelf where the derived source of timing originates
s_number is the source number of the derived source
Note
The NO_CLOCK option applies only to OUTPUT.
Node Parameters
(400)
17.2-29


NNP 95-2035-01-00-B

CONFIG SYNCH
2_MHZ
EXT_FREQ
SRC_NUMBER
INPUT
<source>
8_kHZ
COMP_CLOCK
EXTERNAL
SOURCE
DERIVED
UNDEFINED
<sn> or <sn-l>
SK000016
where
source is 1 to 4 for a peripheral shelf
sn or sn-l is the slot or slot and link identifier where the derived source of timing originates
17.2-30
(400)
Node Parameters

NNP 95-2035-01-00-B


CONFIG SYNCH
MORE
SELECT/
DESELECT*
CLASS
NODE_CLASS
SRC_NUMBER
<class>
<source>
<class>
STATUS_MSG
THRESHOLD
RECOVERY
SOURCE
ENABLE/
DISABLE*
DERIVED
UNDEFINED
RX_ENABLE/
RX_DISABLE
AUTO
EXT_PORT_A
30_SEC
1_MIN
10_MIN
EXT_PORT_B
30_MIN
MANUAL
<sn> or <sn-l> or <Hn> or <Hn-ss>

SK000898
where
class is 1 to 14
source is 1 to 4
sn or sn-l is the UCS slot or slot and link identifier where the derived source of timing originates
Hn or Hn-ss is the HSA slot or HSA slot and subslot identifier
Node Parameters
(400)
17.2-31


NNP 95-2035-01-00-B
To configure an external input timing source for the enhanced locally controlled
shelf
CONFIG SYNCH EXTERNAL INPUT
COMP_CLOCK
FREQ_LOCK
DS1
PHASE_LOCK
NRZ
D4_FRAME
OPTIONS
ESF_FRAME
8_KHZ
2048_KHZ
BRIDGE _ON/
BRIDGE_OFF
SK000833
To configure timing output for an external timing receiver for the enhanced
locally controlled shelf
CONFIG SYNCH EXTERNAL OUTPUT
PORT_A
SYSTEM
PORT_B
HSA_SLOT
DS1_FRAME
D4_FRAME
NRZ_FREQ
ESF_FRAME
8_KHZ
2048_KHZ
<Hn> or <Hn-ss>
SK000834
where Hn or Hn-ss is the HSA slot or HSA slot and subslot identifier
17.2.8
Configuring Synchronization Status Messaging

To configure synchronization status messaging for standalone sources, you must
first select STATUS_MSG mode. Once this mode is enabled, select QUAL_LEVEL to
specify the quality level (PRS, STU, ST2 and ST3) at which a source is deemed
unavailable for synchronization (see Table 17.2-2 for quality level descriptions).
Sources having a status message below the quality level specified cannot become the
current source of synchronization. Alternatively, you can select DISABLED from the
QUAL_LEVEL menu to specify that a source is always available as a possible current
source of synchronization regardless of its quality level.
If ANS is enabled on the node and you have selected STATUS_MSG mode, you must
configure the translation table (TRANS_TABL) to convert the quality level of the
current source of synchronization to the current class of the node (see section 17.2.3).
The node compares the quality and class values to select the current source of
synchronization.
17.2-32
(400)
Node Parameters

NNP 95-2035-01-00-B

To configure synchronization status messaging

CONFIG SYNCH MORE
QUAL_LEVEL
PRS
STU
ST2
ST3 DISABLED
MODE
CLASS
TRANS_TABL
STATUS_MSG PRS STU
ST2
ST3
SK000831
17.2.9
Configuring Synchronization Status Message

Transmission
Synchronization status messages can be transmitted on SONET and SDH output
interfaces and on the two external DS1 timing outputs generated by the Timing card.
The message transmitted depends on the quality level of the source from which the
output is derived.
If class mode is configured, STU is output on all interfaces that are configured to
drive system timing and that support the transmission of status messages. If an OC-3
or STM-1 card is the current source of synchronization, the transmitted message is
driven on the output timing port.
If status message mode is configured and the current source of synchronization
supports the transmission of status messages, the message received from that source
is transmitted on all output timing ports; otherwise, STU is transmitted. STU is also
transmitted if the current source of synchronization is an ANS link. If the node is in
holdover or free-run mode, the status message transmitted on all timing outputs is
ST3.
Messages transmitted over the two DS1 external timing ports depend on the framing
type of the DS1 signal selected for the port. If ESF framing is selected, the message is
transmitted over FDL. If D4 framing is selected, AIS is transmitted on the output
timing port when the signal from which it is deriving timing is below the configured
quality threshold.
Node Parameters
(400)
17.2-33


NNP 95-2035-01-00-B
To configure synchronization status message transmission

CONFIG SYNCH MAINT STATUS_MSG
SYSTEM
EXT_PORT_A
EXT_PORT_B
SLOT
<Hn> or <Hn-ss>
REMOVE_MSG
PRS
INJECT_MSG
STU
ST3
SIC
ST4
MORE
DUS
SK000832
where Hn or Hn-ss is the HSA slot or HSA slot and subslot identifier
17.2-34
(400)
Node Parameters

NNP 95-2035-01-00-B
17.3
17.3 Serial and Ethernet Ports

Serial and Ethernet Ports

This chapter describes the serial ports used for node management terminals and
how to configure the following serial port parameters:
type of device connected

baud rate
flow control
CPSS cost
Also documented in the chapter is the 3600+ MainStreet Bandwidth Manager

Ethernet port configuration.
17.3.1
Understanding the Ports

The node provides the following serial ports for connection to a node management
station:
backplane or bulkhead serial ports 1 and 2

Control card faceplate serial port
CPC, DCP, DS-3 II, E3, FRS, FRE and PE card faceplate serial ports
The data format for the serial ports is:
eight data bits

one stop bit
no parity
See chapter 16.2 for the location and pinouts of these system serial ports.
Location of backplane and bulkhead serial ports

Two serial ports are located on the backplane of a Class A switching shelf, locally
controlled or peripheral shelf. The location of the two serial ports on the enhanced
locally controlled shelf is on the bulkhead. The two serial ports are located on the
bulkhead of a Class B or 23-inch switching shelf, locally controlled, enhanced locally
controlled or peripheral shelf:
SP1 configured for DCE

SP2 configured for DTE (except in CPCs and FRS cards)
Hardware flow control is supported on SP2 only.
Node Parameters
(400)
17.3-1


NNP 95-2035-01-00-B
Note
For SP1 only, RTS is connected to CTS and DTR is connected to DSR by the
backplane.
In dual-shelf, control-redundant systems, the backplane serial ports are inactive in
the shelf with the inactive Control card. In single-shelf, control-redundant systems,
these ports are inactive when the jumper behind the faceplate on the Control card is
installed.
3600+ MainStreet Control card serial ports

Serial ports are used to connect node management stations to initiate node
management sessions with the active or inactive Control card. The active Control
card controls the serial ports on the shelf.
There are at least three serial ports that can be accessed. Two ports, SP1 and SP2, are
located on the bulkhead and the third serial port is located on the active Control card
faceplate.
Only two serial ports are available for use by the system at a time, but they cannot
be used simultaneously. The faceplate serial port on the active Control card is not
available unless a jumper is installed on the card, see Figure 17.3-1. Insert W4 to
disable SP1 on the bulkhead and enable SP1 on the faceplate serial port. In a
control-redundant configuration, only the active Control card faceplate serial port
can be used. Access to the inactive Control card faceplate serial port is available only
if W4 is inserted and the node management station is directly connected.
17.3-2
(400)
Node Parameters

NNP 95-2035-01-00-B

Figure 17.3-1: Jumper W4 Location on the 3600+ MainStreet Control Card
W4
W4
OR
SP1
SP1
faceplate bulkhead
on
on
Bank-B
memory
module
10043
For Control card faceplate serial port pinouts, see section 16.2.3.
3600, 3645, 3664 and 36120 MainStreet Control cards serial ports
The serial port on the Control card faceplate provides access to SP1 of any shelf type.
Only one of the two serial ports of the shelf is active at a time, depending on the shelf
configuration (see Table 17.3-1). This allows a node management session to be
initiated with the inactive Control card.
Note
For a dual-shelf, control-redundant system, connect the node management terminal
to backplane or bulkhead serial ports on both shelves using a Y cable. This ensures
a connection to the active Control card regardless of which shelf is the active shelf.
In a single-shelf, control-redundant Class B shelf, remove the jumper behind the
faceplate on the Control card to enable the faceplate port for a node management
session with the inactive card. (This action disables the backplane port.)
Node Parameters
(400)
17.3-3


NNP 95-2035-01-00-B
Table 17.3-1: Control Card and Backplane or Bulkhead Serial Ports

Shelf
Backplane or
Bulkhead Serial
Ports
Single- or dual-shelf, non-control-redundant system
Control Card
Faceplate Serial
Port
Class A
Class B
Class A
Class B
(1)
(1)
Inactive
Inactive
Active
Active
Single-shelf, control-redundant system
Active
Active
Inactive
Inactive
Shelf with the active Control card in dual-shelf,

Active
Active
Inactive
Inactive
Inactive
Inactive
Active
Active
Shelf with the inactive Control card in dual-shelf,

Notes
1. In a dual-shelf, non-control-redundant system, the Control card uses the backplane or bulkhead SP1
connector of the shelf in which it is installed. The backplane or bulkhead SP1 connector of the shelf
without a Control card is not used.
CPCs
CPCs have two serial ports on their faceplates that provide VT100 access. Both ports
are configured for DCE.
DS-3 II, E3, DCP, FRS, FRE and PE cards

DCP and FRS cards have two serial ports on the faceplate that provide ALAPB
access to the CPSS network.
The DS-3 II, FRE and PE cards have one similar serial port on their faceplates. The
FRE card (Release 2) and the PE card (Release 1) provide FASTbus CPSS
connectivity.
Ethernet port
A Dsub-15 connector located on the 3600+ MainStreet Bandwidth Manager
bulkhead provides an AUI standard, IEEE 802.3 Ethernet port. This port provides a
means to directly attach a network manager to the shelf and only CPSS data is
supported. The active Control card always controls the Ethernet port.
Note
An external MAU is required for the Ethernet port to connect to 10BaseT, 10Base2 or
10Base5 lines.
17.3.2
Configuring Serial Ports

Serial ports can be configured for device type, baud rate, flow control and CPSS cost.
17.3-4
(400)
Node Parameters

NNP 95-2035-01-00-B

Table 17.3-2 lists the serial port configuration parameters. Each parameter has a list
of options with any default option marked with an asterisk. The Control card
referenced in the table applies to all 3600 MainStreet series bandwidth managers.
Any variance in the options are highlighted in the table notes.
Note
Configuring CPSS cost is described in chapter 17.6 (see Table 17.6-1 for the CPSS
configuration parameters).
Table 17.3-2: Serial Port Configuration Parameters and Options

Control
and
DCP
Cards
CPC
DS-3 II
and E3
Cards
FRS,
FRE and
PE
Cards
Parameter
Options
Device type
VT100
printer
CPSS
CPSS modem
call logger
Baud rate
300
600
1200
2400
4800
9600
19 200
38 400 (1)
auto baud (1)
Flow control
software
hardware
none*
CPSS cost
normal*
bias against
bias toward
Notes
1. These options are only available for the 3600+ MainStreet Control card.
Note
Node Parameters
(400)
17.3-5


NNP 95-2035-01-00-B
These options are normally configured through a node management session.

Alternatively, certain device type and baud rate combinations can be configured
using the pushbutton on the GFC, GFC2, GFC3 or Control card (see Maintenance,
chapter 39.2).
Device type
Depending on the type of device connected to the port, the backplane or bulkhead
serial ports can be configured for a VT100-compatible terminal (or a personal
computer running terminal emulator software), a printer, a call logger or a computer
running Craft Interface or 4601, 4602 or 46020 network management software
connected directly or through a modem.
The DS-3 II, E3, DCP, and FRS, FRE and PE card ports can be connected to a VT100
(or emulator) or a computer running network management software. The CPC ports
can be connected only to a VT100 or emulator.
VT100-compatible terminal
A VT100-compatible ASCII terminal or VT100 terminal emulator is used for node
management sessions. It can be connected to the serial ports directly or indirectly
using auto-answer, Hayes-compatible modems. The device type is VT100.
Printer
A printer can be connected to a serial port to print alarms. The device type is Printer.
For details on printing alarms, see Maintenance, section 35.2.6.
17.3-6
(400)
Node Parameters

NNP 95-2035-01-00-B

Personal computer
A personal computer can be connected to a serial port if it is running terminal
emulation software (for installation), Craft Interface software, communications
software or network management software.
Terminal emulation software:
A computer running terminal emulation software is used during installation to

set up CPSS links. It can be connected to a serial port directly or through
auto-answer Hayes-compatible modems. The device type is VT100. See
Installation for details.
Craft Interface software:
The computer running Craft Interface software is connected to a serial port on the
switching shelf backplane, either directly or indirectly through auto-answer,
Hayes-compatible modems. The device type is VT100 if the Craft Interface is
used for terminal emulation or CPSS (direct connection) or CPSS_MODEM
(modem connection) for normal Craft Interface.
Communications software:
A computer running communications software must be connected directly to a
serial port for the node to perform configuration database activities such as
backing up, verifying and restoring (for details, see Maintenance, chapter 39.1).
The computer can also be connected to a serial port through auto-answer,
Hayes-compatible modems.
network manager software:
A computer running network manager can be connected to a serial port directly
or through Hayes-compatible modems. The port must send information to the
network manager using the CPSS protocol. The device type is CPSS if the
network manager software is connected directly or CPSS_MODEM if it is
connected through a modem.
Note
A network manager connected directly to a node can perform the configuration

database activities of backing up, verifying and restoring. A network manager
connected through a modem can back up and verify, but cannot restore. For more
details, see the appropriate network manager documentation.
From the shelf or card whose serial port you are configuring, you can select the port
and configure the device type as:
VT100 for a VT100-compatible terminal or personal computer running terminal

emulator software (default for SP1)
CPSS for a directly-connected computer running Craft Interface or network
Node Parameters
management software
CPSS_MODEM for a computer connected through a modem (default for SP2)
(400)
17.3-7


NNP 95-2035-01-00-B
To configure the device type, see the applicable card procedure:
To configure Control card ports

To configure FRS, FRE and DCP card ports
To configure FRE and PE card ports (for Release 2 FRE cards)
To configure DS-3 II card ports
Baud rate
You can configure the baud rate to match that of the device connected to the serial
port as:
300
600
1200
2400
4800
9600
19200
38400 (3600+ MainStreet only)
AUTO_BAUD (3600+ MainStreet only)
For the 3600+ MainStreet Control card, the automatic baud rate matching option is
the default baud rate for SP1. The default baud rate for SP2 is 9600 b/s. The
maximum baud rate for the 3600+ MainStreet Control card is 38 400 b/s.
The default baud rate of the serial ports on all other 3600 MainStreet series
bandwidth managers cards is 9600 b/s, except for SP2 on the Control card which has
a default baud rate of 1200 b/s. The maximum serial port baud rate is 9600 b/s,
except for the DCP, FRS, FRE and PE cards, which have a maximum serial port baud
rate of 19 200 b/s.
A change to the baud rate takes effect when you execute the instruction (PROCEED)
if the port type is VT100 or PRINTER. You must change the baud rate of the terminal,
computer or printer to match the new setting.
With auto baud, it takes approximately five seconds for the system to automatically
match the speed of the serial port to the speed of the connected device. To function
properly, the attached equipment must send characters to the enhanced locally
controlled shelf. The Control card is unable to send any characters over the serial
port while it is performing the auto baud function. If the attached device performs
auto baud and is able to send characters to the shelf, the baud rate that the two settle
on depends on the attached device. The first speed presented to the serial port that
the 3600+ MainStreet Control card can match is locked.
On a serial port that is configured as VT100 or CPSS with auto baud, the baud rate
is renegotiated whenever the Control card starts-up or whenever an NMTI or CPSS
session on that serial ports ends. The 3600+ MainStreet Control card can begin an
NMTI or CPSS session only after the serial port speed locks onto the baud rate of the
attached device.
17.3-8
(400)
Node Parameters

NNP 95-2035-01-00-B

The following restrictions apply.
Two 3600+ MainStreet bandwidth managers connected together through a serial
port cannot use the auto baud feature to set-up the baud rate of that serial port, a
fixed baud rate must be configured.
A serial port connected to a modem that does not send characters to the Control
card cannot use auto baud, a fixed baud rate must be configured.
Note
CPSS link failure can occur if a modem manages to connect to the RS-232 backplane
serial ports and negotiate a high-speed connection. It may be necessary to disable the
ARQ of the modem or lock the modem RS-232 serial port speed to a Newbridge
supported baud rate.
To configure the baud rate, see the applicable card procedure:

To configure CPC ports
Flow control
You can set bidirectional flow control for both serial ports as:
XON/XOFF for software flow control

DTR for hardware flow control
NONE for no flow control (default)
SP1 supports only software flow control. SP2 supports software and hardware flow
control.
Note
Setting the flow control has no effect on serial ports configured as port type CPSS or
CPSS_MODEM.
To configure the flow control, see the applicable card procedure:
Node Parameters

(400)
17.3-9


NNP 95-2035-01-00-B
Configuring CPSS cost on serial ports

You can configure the CPSS cost on a serial port to one of three values:
NORMAL for normal cost (default)

BIAS_AGNST for cost greater than normal
BIAS_TOWRD for cost less than normal
For more information about CPSS, see chapter 17.6.
To configure the CPSS cost on serial ports, see the applicable card procedure:


HOUSE
SER_PORT_2
SER_PORT_1
PORT_TYPE
VT100* CPSS PRINTER
300
FLOW_CTRL
BAUD_RATE
600
1200
CPSS_
MODEM
2400
4800
XON/XOFF
9600 19200
DTR
38400
NORMAL*
CPSS_COST
NONE*
AUTO_BAUD
BIAS_AGNST BIAS_TOWRD
SK000017
Note
The AUTO_BAUD feature and the baud rate 38 400 b/s are only available for the
3600+ MainStreet Control card.
17.3-10
(400)
Node Parameters

NNP 95-2035-01-00-B


CONFIG SLOT <sn> OPTIONS
SER_PORT_1
PORT_TYPE
VT100*
CPSS
SER_PORT_2
CPSS_COST
BAUD_RATE
<baud rate>
NORMAL*
BIAS_AGAINST
BIAS_TOWRD
SK000018
where baud_rate is 300, 600, 1200, 2400, 4800, 9600 or 19200 (*)
To configure FRE and PE card ports

SER_PORT_1
PORT_TYPE
VT100*
CPSS
FBCPSS1
BAUD_RATE
FBCPSS2
CPSS_COST
<baud rate>
NORMAL*
BIAS_AGAINST
BIAS_TOWRD
SK000019
where baud_rate is 300, 600, 1200, 2400, 4800, 9600 or 19200 (*). Baud rate is not available for FBCPSS1 and
FBCPSS2.
Note
This configuration applies to Release 2 FRE cards (part number 90-1673-02) only. The
FBCPSS1 and FBCPSS2 softkeys do not appear for Release 1 FRE cards (part number
90-1673-01).
Node Parameters
(400)
17.3-11


NNP 95-2035-01-00-B
To configure CPC ports

SER_PORT_1
SER_PORT_2
BAUD_RATE
<baud_rate>
SK000020
where baud_rate is 300, 600, 1200, 2400, 4800, 9600* or 19200

HOUSE SER_PORT_1
PORT_TYPE
VT100* CPSS PRINTER
300
FLOW_CTRL
BAUD_RATE
600
1200
XON/XOFF
CPSS_
MODEM
2400
CPSS_COST
NONE*
4800 9600*
NORMAL*
SK000021
where baud_rate is 300, 600, 1200, 2400, 4800 or 9600*

where baud_rate is 300, 600, 1200, 2400, 4800, 9600* or 19200
17.3.3
Configuring the Ethernet Port

The Ethernet port on the 3600+ MainStreet Bandwidth Manager has a configurable
IP address, subnet mask and default router. This port is disabled by default.
The port must be configured with a valid IP address, subnet mask and default router
IP address before being enabled. Attempting to enable the port before these
parameters are set results in the following error message: A local IP address, subnet
mask and default router must be configured first.
The IP address is the Control card IP address which is a unique 32-bit (four octet)
network layer address that uniquely identifies the node within the IP network. It is
entered in dotted decimal format
17.3-12
(400)
Node Parameters

NNP 95-2035-01-00-B

The subnet mask is a hexadecimal code used to parse an IP address into subnet ID
and host ID. You can configure it only if the network is partitioned into
subnetworks. When you configure the subnet mask, the system knows it is in a
network divided into subnets. The subnet mask is used during forwarding decisions
to determine the subnet ID of the outgoing IP frames.
The port can be connected to up to two remote IP addresses. The host remote
addresses are set using the NMTI.
Note
Disabling the Ethernet port forces CPSS paths to the two remote host addresses to
go down.
Figure 17.3-2 shows the HOUSE display for the 3600+ MainStreet Bandwidth
Manager.
Figure 17.3-2: 3600+ MainStreet Bandwidth Manager HOUSE Display
3600+ MainStreet
S1117-H1-00
Toronto:A
Port
Baud Rate
Port Type
1
2
9600
9600
VT100
VT100
Current Port
Session Time
Domain Number
Node Number
Router Version
NOC Number
Shared CPSS Cost
Level Zero Access
:
:
:
:
:
:
:
:
Alarms:1
Flow Control
8:35a
CPSS Cost
XON/XOFF
NONE
Serial port one

30 minutes
1
Unassigned
1
Unassigned
Normal
No
11-May-1997
N/A
N/A
Ethernet Port :
Local IP Addr :
Subnet Mask
:
Default Router:
Host 1 IP Addr:
Host 2 IP Addr:
MAC Address
Disabled
Unassigned
Unassigned
Unassigned
Unassigned
Unassigned
: 00.00.00.00.02.00
HOUSE ETHER_PORT DEF_ROUTER "???.???.???.???"

Enter an IP address.
16-
Node Parameters
27-
38-CANCEL
(400)
49-QUIT
50-
17.3-13


NNP 95-2035-01-00-B
Table 17.3-3: HOUSE Display field Descriptions

Field
Description
Current Port
The serial port configuration information that is currently displayed.
Default Router
The system default router IP address is the IP address of the nearest

network router. When the system receives an IP packet addressed to a
host on a different subnet, the system forwards the packet to the default
router.
The IP address of the default router must be in the same subnet as the
Control card IP address. You can disable use of the default router by
entering this address as: 0.0.0.0.
Domain Number
The CPSS domain number is the number assigned to the active Control
card that is the CPSS overall master for the shelf.
Ethernet Port
Indicates the status of the port which can be either enabled or disabled.
Host 1 IP Addr
The IP address of a connected remote host.
Host 2 IP Addr
The IP address of a connected remote host.
Level Zero Access
Indicates if the level zero password is enabled. For more information see
chapter 17.5.
Local IP Addr
This is the Control card IP address and is a unique 32-bit (four octet)
network layer address that uniquely identifies the node within the IP
network. It is entered in dotted decimal format.
MAC Address
The MAC address of the shelf.
Node Number
The system CPSS address of the major node.
NOC Number
The telephone number of the modem serving the NOC computer, which
is the computer running the network management software.
Session Time
Indicates the duration of the current node management session.
Subnet Mask
The subnet mask is a hexadecimal code used to parse an IP address into

subnet ID and host ID. You can configure it only if the network is
partitioned into subnetworks. When you configure the subnet mask, the
system knows it is in a network divided into subnets. The subnet mask is
used during forwarding decisions to determine the subnet ID of the
outgoing IP frames.
Shared CPSS cost
The configured CPSS cost for the node.
Router Version
The version number assigned to the active Control card that is the CPSS
overall master for the node.
For information about configuring CPSS parameters for the node, see chapter 17.6.
17.3-14
(400)
Node Parameters

NNP 95-2035-01-00-B

Configuring the Ethernet port

HOUSE ETHER_PORT
DISABLE*/ENABLE
LOCAL_ADDR
SUBNET
DEF_ROUTER
HOST_ADDR1
HOST_ADDR2
<IP_address>
<subnet_mask>
<IP_address>
<IP_address>
<IP_address>
SK000835
where
IP_address is in the decimal format #.#.#.# and where # is in the range 0 through 255
subnet_mask is in the decimal format #.#.#.# and where # is in the range 0 through 255
Node Parameters
(400)
17.3-15

NNP 95-2035-01-00-B
17.4
17.4 Date, Time, and Node Name

Date, Time, and Node Name

This chapter describes how to set the following parameters:
date
time
node name
17.4.1
Configuring the Date, Time, and Node Name

The date, time, and node name appear in the header line of the node management
screen. Figure 17.4-1 shows an example of the header line settings for a 3645
MainStreet switching shelf. The switching shelf sets the date for the peripheral shelf,
DS-3 or DS-3 II card, or E3 card.
Figure 17.4-1: Header Line Fields
3645 MainStreet
F1-CONFIG
F6-
D117-H1-00
Toronto:P3A
F2-HOUSE
F7-
F3-MAINT
F8-
Alarms:1
11-May-1997
F4-STATS
F9-QUIT
8:35a
F5-ALARMS
F0-
You can configure the node for the date, time, and node name. Table 17.4-1 lists the
configurable parameters.
Node Parameters
(400)
17.4-1


NNP 95-2035-01-00-B
Table 17.4-1: Node Configuration Parameters and Options

Control
Card
DS-3 Card
E3 Card
Parameter
Options
Date
<dd-MMM-yyyy>
Time
<hh:mmA or P or H>
Node name
up to 12 alphanumeric characters
(no spaces, no underscores)
To configure these parameters, see the procedure To configure the date, time, and
node name.
Note
Date
In a non control-redundant system, No Date appears in the header line until you
set the date.
In a control-redundant system, the date field indicates whether the node
management session is with the active or inactive Control card. If the programmed
date or No Date appears in the header line, the session is with the active Control
card. If OnStandby appears in the header line, it is with the inactive Control card.
To set the date, select DATE and enter the date in the form <dd-MMM-yyyy>, where:
dd = the day (two digits including a leading zero)
MMM = the month (the first three letters)
yyyy = the year (four digits)
For example, enter November 21, 1996 as <21-NOV-1996>.
Time
Until the time is set, the header line on the node manager screen displays the time
elapsed since a system reset in a 12-h format followed by the indicator R. For
example, if the header line shows 10:03R, it means that the system was reset 10 h and
3 min ago.
Real time appears in the header line in a 12-h format followed by an A or P for a.m.
or p.m. respectively. In the 24-h format, the time is followed by an H.
17.4-2
(400)
Node Parameters

NNP 95-2035-01-00-B

To set the time, select TIME and enter the time in the form <hh:mmA> or <hh:mmP>
or <hh:mmH>, where:
hh = the hour (1 or 2 digits; leading zeros are not required)
mm = the minute (2 digits)
A = a.m.
P = p.m.
H = 24-h format
For example, enter 3:17 p.m. as <3:17P> or <15:17H>. If you do not enter A, P or H,
the node assumes an A.
Node name
Until you assign a node name, the default node name appears in the header line. The
node name can have up to 12 alphanumeric characters. In Figure 17.4-1,
CHEPSTOW is the node name.
The node name is not saved as part of a configuration database backup nor is it
affected when a database is restored. When a database is loaded into a node, the
node name stays as configured to prevent two or more nodes in a network from
having the same node name.
To set the node name, select NODE_NAME and enter up to 12 alphanumeric
characters (no spaces or underscores). To delete the node name, select
NODE_NAME and press .
To configure the date, time, and node name

HOUSE
DATE
TIME
NODE_NAME
<date>
<time>
<name>
SK000023
where
date is dd-MMM-yyyy (dd is the day in 2 digits including a leading zero, MMM is the month indicated in
the first 3 characters, and yyyy is the year in 4 digits)
time is hh:mmA or hh:mmP or hh:mmH (hh is hours in 1 or 2 digits, no leading zeros; mm is minutes in 2
digits; A is a.m., P is p.m., and H is 24-h format)
name is up to 12 alphanumeric characters (no spaces or underscores)
Node Parameters
(400)
17.4-3

NNP 95-2035-01-00-B
17.5
17.5 Access Levels and Passwords

Access Levels and Passwords

This chapter introduces access levels and passwords. The chapter provides a
recommended definition for each access level, and explains how to define the access
for each level and assign passwords.
17.5.1
Understanding Access Levels and Passwords

Control cards and E3 cards have six password-protected access levels. The DS-3 and
DS-3 II cards have one access level. By using access levels and setting passwords for
each level, you allow different users to configure, operate and monitor different
functions of the node manager.
Note
In a control-redundant system configured for hot standby mode, a user running a
node management session on the inactive Control card has the following access,
regardless of the access level entered when logging on:
read and write access for alarms

read-only access for all other functions
See chapter 18.1 for a detailed description of hot standby.
17.5.2
Setting Access Levels and Passwords

You can define the access levels and set passwords.
Table 17.5-1 lists the access level and password configuration parameters.
Node Parameters
(400)
17.5-1


NNP 95-2035-01-00-B
Table 17.5-1: Access Level and Password Configuration Parameters and Options
Control
Card
DS-3 Card
E3 Card
FRS, FRE
and PE
Card
Parameter
Options
Access level 5
level 5 + password
Access levels 1 to 4
level 1 + password
level 2 + password
level 3 + password
level 4 + password
Access level definition
read and write

read only
no access
Access level 0
level 0
no level 0
Passwords
8 to 12 characters, no spaces
Note
17.5.3
Setting Access Levels

The six access levels are 0 through 5; level 5 is the highest level.
Level 5
Level 5 is for the system administrator because level 5 users have read/write access
to all node management functions. Only level 5 users can modify access level
definitions and change passwords. Level 5 cannot be redefined.
To log on as a level 5 user, enter <5> when prompted for the level during log on, then
enter the level 5 password. The default password is <mainstreet>.
You can enter a password from the start-up screen. The node manager tries to use
this password automatically when a level 5 user logs on.
If you are a level 5 user, you can define access levels 1 to 4 for each softkeys as
NO_ACCESS for no access

READ_ONLY for read-only access
READ/WRITE for read and write access
See the procedure To define access levels 1 to 4.
17.5-2
(400)
Node Parameters

NNP 95-2035-01-00-B

Levels 1 to 4
Levels 1 to 4 are defined to give users access to certain node management functions
and restrict access to other functions. Access can be defined as:
no access, which means the user has no access to the function

read-only access, which means the user can read but not make changes to the
function
read and write access, which means the user can read and make changes to the
function
To log on as a level 1 to 4 user, enter <1>, <2>, <3> or <4> when prompted for the
level during log on, then enter the appropriate password. The default password is
<mainstreet>.
Note
Only level 5 users can modify access level definitions. Levels 1 to 4 cannot be
accessed if a password was entered at the start-up menu of the node manager.
For levels 1 through 4, access can be defined for each of the softkeys listed in Table
17.5-2 (except CHNG_PSSWD) for the locally controlled or peripheral shelf. Access
can be defined for each of the softkeys listed in Table 17.5-3 for the FRE, FRS and PE
cards.
Access levels can also be defined at the main menu level, which represents the access
level immediately after logging on. If you define an access of a level for no access at
the main menu level, the user is only able to log off.
The access definition for a softkey overrides the access level of any softkeys
underneath it if the definition is more restrictive. That is, read-only overrides read
and write, and no access overrides both read-only and the read and write.
For example, on a locally controlled or peripheral shelf, assume the softkeys under
CONFIG have these access definitions: SLOT and CIRCUIT have read and write
access, and SYNCH has no access.
Case 1: If CONFIG has read and write access (the least restrictive definition), the
access definitions of the three softkeys SLOT, CIRCUIT and SYNCH will be in effect.
Case 2: If CONFIG is defined as read-only access (more restrictive), it overrides the
definitions for SLOT and CIRCUIT. Then SLOT and CIRCUIT will have read-only
access and SYNCH will have no access.
Case 3: If CONFIG is defined as no access (the most restrictive definition), it
overrides the definitions for SLOT, SYNCH and CIRCUIT and all three softkeys will
have no access.
As shown in Figure 17.5-1, the data area shows the access defined for a softkey; it
does not indicate if it is overridden by a more restrictive definition on another
softkey. The softkey that you are defining normally appears in the top left corner of
the data area (for example, CONFIG SLOT in Figure 17.5-1). If you are defining a
MORE softkey, the word MORE does not appear; for example, if you are defining
the access level for ALARMS MORE, only the word ALARMS appears.
Node Parameters
(400)
17.5-3


NNP 95-2035-01-00-B
Figure 17.5-1: CONFIG SLOT Access Level Definition

3600 MainStreet
1117-H1-00
Toronto:A
Alarms:1
11-May-1997
8:35a
CONFIGSLOT??
Level
1
2
3
4
Access Type
No Access
Read Only
Read/Write
Read/Write
CHANGE_ACCESS LEVEL_4 TO
F1-READ_ONLY
F6-
F2F7-
F3-NO_ACCESS
F8-CANCEL
F4F9-QUIT
F5F0-
Suggested definitions for levels 1 to 4

To simplify the process of defining access levels, Tables 17.5-2 and 17.5-3 provide
suggested definitions for access levels 1 through 4 for node management sessions
with the Control card and FRS, FRE and PE card, respectively. You can use these
definitions for your system or as a basis for defining your own access levels. In these
suggested level definitions, the types of user are defined as follows.
Level 1
You can use level 1 for network performance personnel whose main task is to collect
abnormal system conditions or significant events. The level 1 user can reset the
TEP-1E status indicators used to keep track of the acknowledgment and clearing of
alarms.
Level 2
You can use level 2 for the network performance operator whose main task is to
manage alarms and statistics and to perform maintenance functions such as
diagnostic tests on a circuit or slot.
Level 3
You can use level 3 for the network configuration operator whose main task is to
configure the network interfaces and the signalling or data processing applications
of the system. The level 3 user can manage the housekeeping functions related to the
serial ports and the time, and force an activity switch for hot or partitioned standby
operation or program a timed activity switch.
17.5-4
(400)
Node Parameters

NNP 95-2035-01-00-B

Level 4
You can use level 4 for the system manager who does not modify access level
definitions or change passwords. The main tasks of the level 4 users are managing
the housekeeping functions related to user access and doing maintenance functions
related to the Control card non-volatile memory.
Table 17.5-2: Suggested Access Level Definitions for Control Card Sessions
Softkeys
Access Levels
1
RO (1)
RO
R/W (2)
R/W
CIRCUIT
RO
RO
R/W
R/W
CONNECT
RO
RO
R/W
R/W
SYNCH
RO
RO
R/W
R/W
SYSTEM
RO
RO
R/W
R/W
SER_PORT_1 (3)
RO
RO
R/W
R/W
SER_PORT_2 (3)
RO
RO
R/W
R/W
DATE
RO
R/W
R/W
R/W
TIME
RO
R/W
R/W
R/W
NODE_NAME
RO
RO
RO
R/W
MORE SESSN_TIME
RO
RO
RO
R/W
n/a (4)
n/a (4)
n/a (4)
n/a (4)
MORE NODE_NUM
RO
RO
RO
R/W
MORE NOC_NUM
RO
RO
RO
R/W
DIAG
RO
R/W
R/W
R/W
DISPLAY
RO
R/W
R/W
R/W
UNDO_MAINT
RO
R/W
R/W
R/W
OW_MONITOR
RO
R/W
R/W
R/W
ON_SLOT
RO
R/W
R/W
R/W
ON_CIRCUIT
RO
R/W
R/W
R/W
MORE BACKUP
RO
RO
R/W
R/W
MORE RESTORE
RO
RO
R/W
R/W
MORE VERIFY
RO
RO
R/W
R/W
CONFIG
SLOT
HOUSE
MORE CHNG_PSSWD
MAINT
MORE VIEW_NET
n/a
MORE REDUNDANT
(5)
RO
MORE NVM_DATA
n/a
(4)
n/a
(5)
RO
n/a
(4)
n/a
(5)
RO
n/a
(4)
n/a (5)
RO
n/a (4)
STATS
Node Parameters
(400)
17.5-5


NNP 95-2035-01-00-B
Softkeys
Access Levels
1
USAGE
RO
R/W
R/W
R/W
QUALITY
RO
R/W
R/W
R/W
SYNCH
RO
R/W
R/W
R/W
MAN_CLEAR / AUTO_CLEAR
RO
R/W
R/W
R/W
MIN/DEFER (6)
RO
R/W
R/W
R/W
MAJ/PROMPT (6)
RO
R/W
R/W
R/W
RO
R/W
R/W
R/W
CONFIG
RO
R/W
R/W
R/W
EXTNL_ALRM
RO
R/W
R/W
R/W
RSET_TEP1E
R/W
R/W
R/W
R/W
MORE LOGGING
RO
R/W
R/W
R/W
ALARMS
DIAG/INSTN
(6)
Notes
1. RO = read only.
2. R/W = read and write.
3. Changing the access level of one serial port automatically changes the access level of the other
serial port to the same parameter.
4. This softkey appears for Level 5 users only.
5. By definition, these softkeys are read-only functions.
6. Changing the access level of one alarm queue automatically changes the access levels of the other
alarm queues to the same parameter.
Table 17.5-3: Suggested Access Level Definitions for FRS, FRE and PE Card Sessions
Softkeys
Access Levels
1
RO (1)
RO
R/W (2)
R/W
FASTBUS (3)
RO
R/W
R/W
R/W
STREAM
RO
R/W
R/W
R/W
CONNECT
RO
R/W
R/W
R/W
RO
R/W
R/W
R/W
CONFIG
SWITCH
HOUSE
SESSN_TIME
CHNG_PSSWD
n/a
(4)
n/a
(4)
n/a
(4)
n/a (4)
MAINT
17.5-6
ON_CARD
RO
R/W
R/W
R/W
ON_FASTBUS (3)
RO
R/W
R/W
R/W
ON_STREAM
RO
R/W
R/W
R/W
ON_CONNECT
RO
R/W
R/W
R/W
(400)
Node Parameters

NNP 95-2035-01-00-B

Softkeys
Access Levels
1
RO
R/W
R/W
R/W
MONITOR
RO
R/W
R/W
R/W
REFRESH
RO
R/W
R/W
R/W
MAJ/PROMPT (5)
RO
R/W
R/W
R/W
MIN/DEFER (5)
RO
R/W
R/W
R/W
RO
R/W
R/W
R/W
CONFIG
RO
R/W
R/W
R/W
MORE LOGGING
RO
R/W
R/W
R/W
VIEW_NET
STATS
ALARMS
DIAG/INSTN
(5)
Notes
1. RO = read only.
2. R/W = read and write.
3. This softkey appears for the FRE and PE cards only.
4. This softkey appears for Level 5 users only.
5. Changing the access level of one alarm queue automatically changes the access levels of the other
alarm queues to the same level.
Level 0
Level 0 is a read-only access level for which no password is required. You configure
level 0 access on a per-node basis or on the FRS, FRE and PE card (both serial ports
on the FRS, FRE and PE cards have the same configuration). You can configure the
serial ports with level 0 access or no level 0 access.
When a serial port is configured for level 0 access, any user can look at the NMTI
settings by entering <0> when prompted for the level during log on. The system
does not prompt for a password.
Level 0 users have access to all softkeys except PROCEED. Only level 5 users can
configure a port as level 0 (this softkey does not appear for users logged on at other
levels).
If a serial port is configured for no level 0, users have to give one of the five access
level passwords to log on to the node manager. They have the read and write
privileges defined for that level. The setting for level 0 has no effect on the settings
for levels 1 to 5. Level 0 cannot be redefined or assigned a password.
Set level 0 access for the serial port as:
LEVEL_0 for level 0 access

NO_LEVEL_0 for no level 0 access (default)
See the procedure To set level 0 access.
Node Parameters
(400)
17.5-7


NNP 95-2035-01-00-B
To define access levels 1 to 4

1.
Select the softkey that represents the level for which you want to change the
access.
For example, to define the access to card slots, select CONFIG then SLOT or
CONFIG then FASTBUS.
2.
Enter:
<Esc> <A>
Note
The access levels for the CONFIG CONNECT menu, available on a locally
controlled or switching shelf, cannot be changed.
Softkeys for the four levels appear.

3.
Select the level that you want to define:
4.
LEVEL _1
LEVEL_2
LEVEL_3
LEVEL_4
Select the access definition for this softkey:
READ/WRITE*
READ_ONLY
NO_ACCESS
To set level 0 access
HOUSE MORE LEVEL_0/NO_LEVEL_0*
17.5.4
Setting Passwords
You can configure each access level with its own password; users must enter the
password when they initiate a node management session.
The default password for levels 1 to 5 is <mainstreet>. The password for levels 1 to
5 can be changed after installation is complete. Passwords must be at least 8 and no
more than 12 alphanumeric characters with no spaces. When the system is first
commissioned, change the level 5 password on each shelf to protect the node
database. Only level 5 users can change passwords (the CHNG_PSSWD softkey
does not appear for users logged on at other levels).
17.5-8
(400)
Node Parameters

NNP 95-2035-01-00-B

The access level passwords are not saved as part of a configuration database backup.
When a database is loaded into a node, the passwords revert to the default
<mainstreet>.
When you select CHNG_PSSWD, you are prompted for the level 5 password. This
prevents unauthorized users from changing passwords if a terminal is left
unattended while logged on at level 5.
When you enter the new password, the system prompts you to enter it a second
time. Then the system enters the password into the database in encrypted form.
Note
The DS-3 and DS-3 II cards support only one access level.
To set access-level passwords

HOUSE
MORE
CHNG_PSSWD
<level_5_psswd>
LEVEL_1
LEVEL_2
LEVEL_3
LEVEL_4
LEVEL_5
<new_psswd>
<new_psswd>
SK000025
where
level_5_psswd is your level 5 password (8 to 12 characters, no spaces)
new_psswd is the new password (8 to 12 characters, no spaces)
Node Parameters
(400)
17.5-9

NNP 95-2035-01-00-B
17.6
17.6 CPSS Configuration

CPSS Configuration
This chapter introduces CPSS and explains how to configure the following
parameters:
17.6.1
node parameters
CPSS options
CPSS connections for a network manager
CPSS FASTbus connections
CPSS routing protocol
Understanding CPSS Configuration

CPSS is the Newbridge-proprietary packet-switched network management
protocol. MainStreet products use CPSS messages to exchange information.
CPSS messages carry information between nodes and network managers. CPSS
sends commands from the network manager to the nodes.
CPSS carries performance statistics, configuration status information and diagnostic
alarms from the nodes to the network manager. CPSS messages carry timing
information for synchronization between nodes that have ANS enabled. CPSS
messages also carry diagnostic and maintenance routing messages through the
CPSS network.
CPSS circuits cross-connected to aggregate link circuits, directly or through SRM,
carry messages between nodes. These circuits are supported by HDLC devices on
the Control card and the DCP card.
There are three kinds of CPSS circuit: shared, dedicated and FASTbus CPSS circuits.
Note
For information on backplane CPSS link configuration between the Control card and
DCP-based cards (CPC, DCP, FRE, FRS or PE card), see chapter 17.7.
Shared CPSS circuits

A shared CPSS circuit is provided by an HDLC device shared by several
system-related housekeeping tasks.
To provide CPSS connections between neighbour nodes, the Control card provides
one shared CPSS circuit that can be cross-connected to more than one aggregate link
circuit. The circuit identifier for a shared CPSS circuit is <CPSS>. Shared CPSS
circuits support speeds of 4, 8 or 16 kb/s.
Node Parameters
(400)
17.6-1


NNP 95-2035-01-00-B
Dedicated CPSS circuits

A dedicated CPSS circuit has exclusive use of an HDLC device and has a wider range
of speeds and configuration options (such as support for satellite delay) than shared
CPSS circuits.
The Control card provides four dedicated CPSS circuits. Each circuit can be
cross-connected to a different aggregate link (or to the same link). The circuit
identifier for a Control card dedicated CPSS circuit is <CPSS-n> where n is 1 to 4.
Control card dedicated CPSS circuits support speeds of 4, 8, 16, 48, 56 or 64 kb/s.
The DCP card provides up to 31 dedicated CPSS circuits. Each circuit can be
cross-connected to a different aggregate link (or to the same link). The circuit
identifier for a dedicated CPSS circuit on a DCP card is <sn-cc> where sn is the shelf
and slot occupied by the DCP card and cc is 1 to 31. DCP card dedicated CPSS
circuits support speeds of 4, 8, 16, 24, 32, 40, 48, 56 and 64 kb/s.
DS-3 II and E3 cards support the termination of dedicated CPSS circuits on DS-3 or
E3 links. The DS-3 II and E3 cards support one dedicated CPSS circuit and the Dual
E3 card supports two. The dedicated CPSS (identified as CPSS-1 or CPSS-2) can be
cross-connected to any DS0. Dedicated CPSS circuits on DS-3 II and E3 cards support
speeds of 8, 16, 48 and 56 kb/s.
Backplane CPSS circuits

In situations where there is heavy CPSS traffic and potential network bottlenecks,
backplane CPSS circuits provide dedicated CPSS connections to the control card for
the DCP, CPC, FRE, FRS and PE cards. These cards, which previously could only
support shared CPSS, can use a backplane connection to improve their CPSS
connection speed from 16 kb/s shared CPSS to 64 kb/s dedicated CPSS.
FASTbus CPSS circuits

FASTbus CPSS connections are supported by the FRE (Release 2, part number
90-1673-02) or PE card. CPSS connectivity for the FRE or PE card is provided by
encapsulating CPSS over frame relay over the FASTbus. The limit of FASTbus CPSS
connections is two. CPSS over frame relay connections cannot be made over
backplane circuits. FASTbus CPSS connections can be made only to the FASTbus.
The circuit identifier for a FASTbus CPSS connection is either CPSS <x> to
F<y>-CPSS or F<y>-CPSS to CPSS<x>.
Note
Only 1350 PVCs are supported on an FRE or PE card carrying FASTbus CPSS.
17.6-2
(400)
Node Parameters

NNP 95-2035-01-00-B

CPSS cross-connections
You can cross-connect CPSS circuits to:
TS0 on E1, Dual E1, Dual E1-2, MPA and X.21/V.35 PRI links
FDL on T1 and Dual T1 links using ESF framing
all or part of a 64 kb/s channel (DS0) on all primary rate or data links (that is, they
can be subrate-multiplexed)
Unlike TS0 circuits with CPSS over them on other cards, you do not have to
cross-connect the Dual E1 card TS0 to the Control card or DCP card. Since CPSS is
terminated on the Dual E1 card, the system automatically makes the connection
when you enable CPSS over TS0.
CPSS cannot be directly or indirectly (through SRMs) connected to E1 or Dual E1
circuits in 3664 MainStreet systems. However, CPSS that terminates on other nodes
can be transported over E1 circuits.
CPSS is also carried over the system serial ports (directly or through a modem) when
configured for CPSS or modem operation (see section 17.6.8).
Note
Shared and dedicated CPSS circuits cannot be cross-connected to one another.
CPSS versions
There are two versions of CPSS: CPSSv1 and CPSSv2. CPSSv1 is supported on
Release 4 and lower systems. It provides a distance vector routing algorithm (router
version 1) and basic CPSS messaging and link costing options.
CPSSv2 is the most advanced version of CPSS supported in Release 6 and newer
versions of system software. In addition to CPSSv1 capability, it provides:
a Link State routing algorithm (router version 2)

domains (subnetworking)
enhanced network layer services
enhanced CPSS link cost options
master/slave protocol (CPSS parameter configuration consistency)
Router version 2 provides higher reliability, support for bigger networks and faster
routing table updates after a CPSS link failure. Router version 1 supports Release 6
and newer versions of node software in a Release 4 network and simplifies the
upgrade from Release 4 to 6 and up.
Node Parameters
(400)
17.6-3


NNP 95-2035-01-00-B
Note
CPSSv2 nodes are designed to interoperate with CPSSv1 nodes during and after an
upgrade to Release 6 and newer versions of system software (see Upgrading to
CPSSv2 in this section).
Router version 2
Previously, all CPSSv1 nodes performed CPSS message routing using router
version 1. With the introduction of CPSSv2, all nodes support enhanced network
layer services and link cost options, but only certain nodes perform CPSS message
routing using router version 2.
In a network running Release 6 or newer versions of system software, CPSSv2 nodes
running router version 2 typically form the backbone of a network. These are the
3600 MainStreet series bandwidth managers nodes. In these nodes, there are one or
more CPSS routing elements that perform CPSS routing.
Routing elements are the Control card (switching, peripheral and locally controlled
shelf), DCP card, DS-3 II card and E3 card.
CPSSv2 nodes running router version 1 typically form the periphery of a network
and are called feeder nodes. To access the backbone CPSS network, feeder nodes
must be directly connected to a CPSSv2 backbone node, that is, not more than one
hop away. (A CPSS hop is a link between two CPSS routing elements that is free of
any intervening CPSS routing elements.) A node running router version 2 does not
forward CPSS traffic through a node running router version 1. Feeder nodes
typically form the periphery of the network and feed end user devices into the
backbone.
These nodes are the 3612, 3620, 3624, 3630 and 8230 MainStreet systems and the FRS,
FRE and PE cards.
Note
All backbone nodes in the same domain must run the same router version.
Domains
CPSSv2 lets you organize nodes into groups called domains; each domain has a
number. You can define up to 32 000 domains; this means that a large CPSS network
can be divided into smaller subnetworks. All domains are still under the control of
the same network manager, but each node knows only the topology of its own
domain. This reduces routing complexity, improves CPSS performance and
reliability and allows more than 1023 nodes to be included in the CPSS network.
17.6-4
(400)
Node Parameters

NNP 95-2035-01-00-B

Note
The communication of CPSS messages from one domain to another needs an
inter-domain router, such as MDNS on the 4602 MainStreet Intelligent
NetworkStation or MainStreetXpress 46020 Network Manager.
Enhanced network layer services

CPSSv2 provides improved CPSS packet transmission services at the network layer.
These services support:
better error detection

large (256-byte) network-layer packets for higher throughput
a new datagram service for better performance
a maintenance packet for better diagnosis of CPSS problems
CPSS link cost

The cost of a CPSS link is a user-configured weight used by the current CPSS routing
algorithm during path selection. A route with a lower cost is selected over a route
with a higher cost.
CPSS cost is defined as NORMAL, BIAS_AGNST or BIAS_TOWRD to bias CPSS
traffic away from some links and toward others. For example, you can configure a
CPSS circuit cross-connected to a satellite link as BIAS_AGNST to encourage the
current routing algorithm to use a less expensive or faster connection. Table 17.6-1
lists the numeric values associated with these three choices. These values are not
user-configurable, but are assigned according to the nature of the CPSS circuit.
CPSS routing elements within a node are classified as follows.
Primary routing element:
CPSS routing element whose purpose is to route CPSS traffic exclusively, such as
the DCP card
Secondary routing element:
CPSS routing element that can route CPSS but whose main purpose is something
else, such as the Control, FRS, FRE and PE cards and the 4602 MainStreet
Intelligent NetworkStation or MainStreetXpress 46020 Network Manager.
Primary routing elements have lower CPSS path costs than secondary routing
elements to bias CPSS traffic towards them and away from secondary routing
elements.
Node Parameters
(400)
17.6-5


NNP 95-2035-01-00-B
Table 17.6-1: CPSS Path Cost Values

Routing Element
Router Version 1
Router Version 2
Bias
Toward
Normal
Bias
Against
Bias
Toward
Normal
Bias
Against
Primary
Serial ports
1
1
1
1
2
2
1
1
5
10
50
50
Secondary
Shared CPSS circuits
Serial ports
1
1
1
1
1
1
2
4
8
1
5
1
10
25
20
50
100
200
Note 1
For switching shelf controlled systems, the CPSS cost of the CPSS link between the
switching shelf and a peripheral shelf is fixed at NORMAL (1 for router version 1
and 10 for router version 2) and is not user-configurable. For all systems, the CPSS
cost of the link between a Control card shared CPSS circuit and a minor node (DCP,
FRS, FRE or PE card) is fixed at NORMAL (7 for router version 2 or 0 for
router version 1) and is not user configurable.
Note 2
For Release 2 FRE (part number 90-1673-02) and PE cards, the default CPSS cost is
BIAS_AGAINST. When you configure for BIAS_AGAINST and a DCP card is
installed, CPSS will route through the DCP card instead of the FRE or PE CPSS link.
All displays showing CPSS information show CPSS cost as NORMAL,

BIAS_AGNST or BIAS_TOWRD (except for CPSS maintenance displays that show
the exact numeric value).
When CPSS path cost is changed for a link, the change takes effect immediately if
router version 2 is running. If router version 1 is running, the change does not take
effect until the link is restarted.
When the two ends of a connection are configured with a different path cost, router
version 2 uses the maximum of the two programmed costs. Router version 1 uses the
local programmed cost. In the example in Figure 17.6-1, the link is configured at
node A with a path cost of BIAS_AGNST and at node B with a path cost of
BIAS_TOWRD. If router version 2 is running, both node A and node B see the path
cost of this link as BIAS_AGNST. If router version 1 is running, node A sees a path
cost of BIAS_AGNST and node B sees a path cost of BIAS_TOWRD.
Figure 17.6-1: CPSS Cost Example
Bias against
Bias towards
B
8453
17.6-6
(400)
Node Parameters

NNP 95-2035-01-00-B

Master/slave protocol
The CPSS master/slave protocol ensures that key CPSS parameters are configured
consistently in all elements of a system. It also simplifies the upgrade procedure
from Release 4 to Release 6 and newer versions of system software.
As shown in Figures 17.6-2 and 17.6-3, there is an overall CPSS master element and
one or more CPSS slave elements in any system. All slave elements receive their
CPSS parameter values from the master. Some slave elements function as
intermediate masters to the slave elements below them.
CPSS parameter changes can only be made on the overall master. In a switching
shelf controlled system, user attempts to change CPSSv2 parameters on peripheral
shelves are blocked.
Any CPSS parameter change made to the overall master is immediately propagated
to all slave elements. If a slave element is added to an existing system, the overall
CPSS master automatically downloads its CPSS parameter values to the new slave
element.
Figure 17.6-2: CPSS Master/Slave Protocol - Switching Shelf Controlled System
Active
switching
shelf
Active
DS-3/E3
Inactive
switching
shelf
Active
peripheral
shelf
Inactive
peripheral
shelf
Inactive
DS-3/E3
DCP
FRE/FRS
DCP
FRE/FRS
5370
Figure 17.6-3: CPSS Master/Slave Protocol - Locally Controlled System
Active
Control
card
Inactive
Control
card
DCP
FRE/FRS
DCP
FRE/FRS
5371
Node Parameters
(400)
17.6-7


NNP 95-2035-01-00-B
For example, in a switching shelf controlled system, the active switching shelf is the
overall CPSS master and downloads its CPSS parameter values to the inactive
switching shelf and all active peripheral shelf Control cards, DS-3 II cards or E3
cards. In turn, each active peripheral shelf Control card downloads these values to
its inactive Control card and to all its UCS cards affected by CPSS parameter values.
Similarly, each active DS-3 II or E3 card downloads these values to its inactive
DS-3 II or E3 card mate.
Note
The master/slave protocol operates only within a system, not between all systems
in a network. It guarantees that all slave elements of a system are consistent with the
overall master of that system. The network manager must make sure that the overall
masters of each system in the network are consistent with one another.
Upgrading to CPSSv2
CPSSv2 nodes (both routing and feeder) provide backwards compatibility features
to support interoperability with CPSSv1 nodes and to simplify the upgrade
procedure from Release 4 to Release 6 and newer versions of system software.
Master/slave protocol and upgrades from Release 4 software
The master/slave protocol simplifies the upgrade procedure from Release 4 to
Release 6 and newer versions of system software, and ensures that the overall master
and all slave elements can be reached through the CPSS network at all times during
the upgrade.
The example in Figure 17.6-4 shows the basic steps (a through d) in the upgrade
procedure from Release 4 to Release 6 and how the master/slave protocol functions
for a dual-shelf, control-redundant locally controlled system. (This example applies
to upgrades from Release 4 to Release 6 and newer versions of system software.)
17.6-8
(400)
Node Parameters

NNP 95-2035-01-00-B

Figure 17.6-4: Example of Upgrade from Release 4

(b)
(c)
(d)
Release 4
Release 4 Master
Release 6 Master
Release 6 Master
CPSSv1
CPSSv1
CPSSv1
CPSSv1
Router 1
Router 1
CPSSv2
(a)
Router 2
Router 2
x Domain
x Domain
Release 6 Slave
Release 4
CPSSv1
CPSSv1
CPSSv1
CPSSv2
CPSSv2
Router 1
Release 4
Router 1
Router 1
Router 1
Slave
Release 6
Slave
CPSSv1
CPSSv2
Router 1
Router 1
Router 2
Router 2
1 Domain
x Domain
7176
Initially (a), both the active and inactive Control card run Release 4 and the
master/slave protocol does not exist.
The inactive Control card is upgraded (b) to Release 6 (or newer version of system
software) then restarted. The inactive Release 6 Control card identifies the active
Release 4 Control card as its master. Because the master is running CPSSv1, the
inactive Release 6 Control card enters CPSSv1 mode (this mode is not
user-selectable). The router is set to router version 1, by default, and is therefore
compatible with the master. The domain number is set to 1, by default. Now you can
change the domain number on the inactive Release 6 Control card to be ready for the
activity switch that makes the Release 6 Control card active.
When you initiate an activity switch (c), the formerly inactive Release 4 Control card
becomes active. The now-active Release 6 Control card detects that it has become the
new overall master and runs the highest version of CPSS it canCPSSv2. Domain
and router version remain on the active Release 6 Control card as configured. The
master prepares to download these parameters to the inactive Release 4 Control
card, waiting until the inactive can respond to its master/slave protocol requests.
You can then upgrade the inactive Release 4 Control card (d) to Release 6 and restart
the card. The inactive Release 6 Control card identifies the active Release 6 Control
card as its master and gets ready to receive the CPSS parameter values of the master.
The active Release 6 Control card downloads its CPSS parameters values to the
inactive Release 6 Control card.
Now the system is ready for the Router Upgrade Tool to switch the network over to
router version 2. Alternatively, you can select router version 2 manually on the CPSS
overall master (see Table 17.6-2 for the location of the configuration procedure).
Node Parameters
(400)
17.6-9


NNP 95-2035-01-00-B
Caution
As a general rule, leave CPSSv2 parameters at their default during the upgrade. The
exception is domain number (step b, in Figure 17.6-4); it should be configured to
match the domain in which the system is located. For more information on upgrades
and the Router Upgrade Tool, contact your Newbridge representative.
Router interoperability
CPSSv2 backbone nodes support router version 1 and 2 and can exchange CPSS
messages using the small packet size used by CPSSv1 or the large packet size used
by CPSSv2.
When a CPSSv2 backbone node using router version 2 is directly connected to a
CPSSv1 or CPSSv2 node running router version 1 (that is, not more than one hop
away), it automatically translates router version 2 information into router version 1
format. (Router version 1 always uses small packets; router version 2 always uses
large packets.)
CPSSv2 feeder nodes support small and large CPSS message packet sizes. The small
packets option is the default for a CPSSv2 feeder node brought on-line in a CPSSv1
network during an upgrade from Release 4 to Release 6 and newer versions of
system software.
A CPSSv2 node running router version 2 can reach a router version 1 node any
number of hops away as long as the route to the node is through router version 2
nodes only. A CPSSv2 node running router version 2 does not forward CPSS traffic
through a router version 1 node.
CPSS status information

In Release 4 products, hops and CPSS cost are equivalent. This means that a
Release 4 feeder node shows hops as costs, not as hops.
When viewed from a feeder node, the CPSS cost is always equal to 100. For the real
CPSS cost, view the CPSS cost from a backbone node.
CPSS grooming
In a network of Newbridge equipment, only one channel in each pair of adjacent
nodes must be dedicated to CPSS messages. However, if Newbridge equipment is
connected to a network of non-Newbridge equipment, the ability to connect more
than one CPSS channel to a single CPSS carrier is advantageous. This connection is
called CPSS grooming.
17.6-10
(400)
Node Parameters

NNP 95-2035-01-00-B

In Figure 17.6-5, the node on the left side is doing CPSS grooming. It is mediating
between many CPSS channels on one primary rate link and a single CPSS channel
on the other link. The system monitors the incoming CPSS channels from both links
and makes dynamic cross-connections as required. For example, if a CPSS message
addressed to 3624 MainStreet (#3) node comes in on the T1 link, the system connects
the single CPSS channel to the DS0 for 3624 MainStreet (#3) node for the message to
pass. With CPSS grooming, many CPSS channels can be funneled into a single
channel.
In Figure 17.6-5, each CPSS channel is routed separately and transparently through
the non-Newbridge network from the node doing CPSS grooming to the other
Newbridge equipment.
Channel limitations
The following channel limitations affect the PRI cards.
For the E1 card, timeslot 0 and all 30 DS0s can be configured as CPSS channels.
For E1 or Dual E1 cards in a 3664 MainStreet system, no circuits can be configured
for CPSS.
For the T1 card, the FDL and up to 23 DS0s can be configured as CPSS channels.
For the Dual T1 card, FDL cannot be used for CPSS if the host is running router
version 2.
For T1 and Dual T1 cards in a 3664 MainStreet system, the FDL and up to 12 DS0s
can be configured for CPSS.
For DS-3 II and E3 cards, only one DS0 in a card can be configured as a CPSS
channel.
For Dual E3 cards, only two DS0s in a card can be configured as CPSS channels.
There are other limitations on a system level. If a node contains only E1 or T1 cards,
the maximum number of channels (DS0s, TS0s or FDLs) that can be designated as
shared CPSS channels for slots A1 through A6 is 34. For example, if slot A1 contains
an E1 card with all 30 DS0s and TS0 designated as CPSS channels (a total of 31
channels), only three other channels for slots A2 through A6 can be designated as
CPSS channels, for a total of 34 channels.
If you configure more CPSS channels than allowed, the system raises a System
Advisory alarm with subcode 225.
Node Parameters
(400)
17.6-11


NNP 95-2035-01-00-B
Figure 17.6-5: CPSS Grooming Application
3624 MainStreet node

#1
T1

#2
T1
T1
T1
Network made up of
non-Newbridge equipment

(performing CPSS grooming)

#3
T1
Single DS0
configured for CPSS
T1

#4
Many DS0s
configured for CPSS
#5
2034
17.6.2
Configuring CPSS
Table 17.6-2 lists the CPSS configuration parameters and the cards to which they
apply. Each parameter has a list of options with any default option marked by an
asterisk.
17.6-12
(400)
Node Parameters

NNP 95-2035-01-00-B

Table 17.6-2: CPSS Configuration Parameters and Options

Control
Card
DCP
DS-3 II
and
E3
Card
FRS
Card
FRE
and
PE
Card
Parameter
Options
4 kb/s CPSS
4 kb/s
8 kb/s
16 kb/s
4 kb/s CPSS
enabled
disabled*
CPSS
connection type
shared
dedicated*
Cost of dedicated
CPSS
normal*
bias against
bias towards
Cost of shared
CPSS
normal*
bias against
bias towards
CPSS node
number
1 to 999
Domain number
1 to 32000 (* = 1)
Interface speed
4 kb/s
8 kb/s
16 kb/s
48 kb/s
56 kb/s
64 kb/s
NOC number
up to 30 characters
Router version
version 1*
version 2
Routing protocol
host router
router version 1*
Satellite delay
satellite
normal
Timers
T200
TACK
N200
T203
(1)
Notes
1. This parameter applies only to Release 2 FRE cards and PE cards.
Table 17.6-3 lists the CPSS connection configuration procedures and the cards to
which they apply. These procedures explain how to make CPSS connections.
Node Parameters
(400)
17.6-13


NNP 95-2035-01-00-B
Table 17.6-3: CPSS Connection Configuration Procedures

Control
Card
DCP
DS-3 II
and
E3
Cards
T1
Cards
E1
Cards
X.21,
V.35
and
MPA
Cards
FRE
and
PE
Cards
DNIC
and
2B1Q
Cards
FRS
Card
64 kb/s CPSS
Cost on serial ports
CPSS connection type
FASTbus CPSS connections
FDL
PSTN and modem connection to

network manager
Serial port connection to network

manager
Signalling
Subrate CPSS channels

TS0
Note
17.6.3
Configuring CPSS Node Parameters

CPSS node parameters are basic system-related CPSS parameters that apply to the
node as a whole. The CPSS node parameters you can configure are:
node number
NOC number
domain number
router version
cost of shared CPSS
Table 17.6-2 lists these parameters and indicates the cards to which they apply.
Figure 17.6-6 shows a typical CPSS node parameter display.
17.6-14
(400)
Node Parameters

NNP 95-2035-01-00-B

Figure 17.6-6: CPSS Node Parameter Display

3600 MainStreet
Port
1
2
1117-H1-00
Baud Rate
Port Type
9600
1200
Current Port
Session Time
Domain Number
Node Number
Router Version
NOC Number
Shared CPSS Cost
Level Zero Access
Toronto:A
Alarms:1
Flow Control
VT100
CPSS_MODEM
:
:
:
:
:
:
:
:
11-May-1997
NONE
NONE
8:35a
CPSS Cost
N/A
Normal
Serial port one

30 minutes
1
Unassigned
2
Unassigned
Normal
No
HOUSE CPSS
1-NODE_NUM
6-
2-NOC_NUM
7-
3-DOMAIN_NUM
8-CANCEL
4-ROUTER
9-QUIT
5-SHARE_COST
0-
Note
Node number, domain number and router version are neither backed up nor
restored. All other node parameters are backed up and overwrite the current
configuration when you do a restore procedure.
Node number
The node number (NODE_NUM) is the address used by major nodes to identify and
communicate with each other. Minor nodes (such as FRS, FRE and PE cards) are
identified by the node number of their major node and their slot.
At installation, each major node in a domain (locally controlled shelf, switching shelf
or peripheral shelf Control card and DS-3 II or E3 card) is assigned a unique node
number. Because the two Control cards in a control-redundant system (or the two
cards in a control-redundant DS-3 II or E3 card pair) act as one node, both cards must
have the same node number.
Setting and changing the node number and assigning a new node number for the
Control card, DS-3 card and E3 card are described in Installation, Task 1400:
Commissioning the Nodes.
You may need to initiate a system restart before the new (programmed) node
number takes effect or appears in the header line. In the HOUSE display, both the
programmed and current node numbers appear.
Node Parameters
(400)
17.6-15


NNP 95-2035-01-00-B
Note
The network manager and the Craft Interface node manager manuals see node
number as CPSS node ID.
To configure the node number, see the procedure To configure node parameters.
NOC number
You must set the NOC number (NOC_NUM) if the node is part of a network
controlled by network management software. The NOC is the computer running the
network management software. Normal communications with the NOC is through
primary rate links in the network. A PSTN link and modems can be used as a
back-up to the primary rate links. The NOC number is the telephone number of the
modem serving the NOC computer.
When you enter the number, include any prefix digits that would be required if the
call were dialed manually from a phone (such as the area code). The number can
include the Hayes AT modem dial modifiers (, = pause; W = wait for dial tone;
@ = wait for silence). The NOC number cannot be more than 30 characters long. For
example, to dial a long distance number from a PBX that provides a second dial tone
after the digit 9, use 9W1-613-591-3645. By default, the node instructs the modem to
dial the NOC number using dial pulsing. For the modem to dial using DTMF, you
must precede the NOC number with the characters DT.
To configure the NOC number, see the procedure To configure node parameters.
Domain number
You configure the domain number (DOMAIN_NUM) by assigning a number in the
range of 1 to 32000 to the CPSS overall master. For a switching shelf controlled
system, the overall master is the active switching shelf Control card. For a locally
controlled system, it is the active shelf. When you configure the master domain
number, CPSSv2 immediately configures the rest of the node with the same domain
number.
To configure the domain number, see the procedure To configure node
parameters.

You can configure CPSS connection type (CARD_COMM) for the DCP, FRE, FRS
and PE cards as DEDICATED or SHARED. Shared CPSS connections provide an
interface speed of 16 kb/s, while dedicated CPSS connections provide an interface
speed of 64 kb/s. Dedicated CPSS is provided across a backplane connection made
to the Control card.
To configure the CPSS connection type, see the procedure To configure CPSS
connection type.
17.6-16
(400)
Node Parameters

NNP 95-2035-01-00-B

Router version
You configure the router version by assigning a version number (VERSION_1 or
VERSION_2) to the CPSS overall master. For a switching shelf controlled system, the
active switching shelf Control card is the CPSS overall master. For a locally
controlled system, the active shelf is the CPSS overall master. When you configure
the master router version, CPSSv2 immediately configures the rest of the node to the
same router version.
To configure the router version, see the procedure To configure node parameters.
Router version 2 FRS, FRE and PE card restrictions

The two valid CPSS routing protocol options for an FRS, FRE or PE card are
ROUTER_V1 (router version 1) and HOST_RTR (host router). An FRS, FRE or PE
card configured for Host Router will run the same router version as the node Control
card. A maximum of two FRS, FRE or PE cards can be configured for HOST_RTR if
the node Control card is configured for router version 2.
If you attempt to configure more than two FRS, FRE or PE cards for HOST_RTR in a
node configured for router version 2, an error message is displayed. Any additional
FRS, FRE or PE cards must be configured for router version 1. Similarly, if you
attempt to select router version 2 as host router from the House menu while having
more than two FRS, FRE or PE cards configured for Host router, the selection will be
blocked. In order to select router version 2 in this situation, you must first ensure that
no more than two FRS, FRE or PE cards are configured for Host router. See the
procedure To configure FRS, FRE and PE card router version for additional
information on how to configure the FRS, FRE or PE card CPSS router version.
Note 1
Router version 2 cannot be used if CPSS is being carried on TS0 of a Dual E1 card or
FDL of a Dual T1 card.
Note 2
If the node is configured for router version 2, and a FRS, FRE or PE card configured
for router version 1 has a CPSS connection present on a serial port, the node at the
end of that CPSS link may not be visible to the CPSS master.
Cost of shared CPSS

You configure shared path cost (SHARE_COST) by selecting one of three
pre-defined choices:

If the node is configured for router version 1, the system does not act on a CPSS path
cost change until the link is restarted. If the node is configured for router version 2,
it acts on a cost change immediately.
Node Parameters
(400)
17.6-17


NNP 95-2035-01-00-B
To configure the cost of shared CPSS, see the procedure To configure node
parameters.
To configure node parameters

HOUSE MORE CPSS
DOMAIN_NUM
NODE_NUM
NOC_NUM
<node_num>
<noc_num> <domain_num> VERSION_1*/

VERSION_2
NORMAL*
ROUTER
BIAS_AGNST
SHARE_COST
BIAS_TOWRD
SK000026
where
node_num is 1 to 999
noc_num is the NOC telephone number with any prefix digits and modem dial codes (up to 30 characters)
domain_num is 1 to 32000 (1*)
To configure the CPSS connection type

CONFIG SLOT <sn> CARD_COMM SHARED/DEDICATED*
To configure FRS, FRE and PE card router version

ROUTER_V1/HOST_RTR
SK000029
17.6.4
Configuring CPSS Options

In addition to node parameters, you can configure these optional CPSS parameters:
cost of dedicated CPSS

interface speed
satellite delay
signalling
Table 17.6-2 lists these parameters and indicates the cards to which they apply.
17.6-18
(400)
Node Parameters

NNP 95-2035-01-00-B

Note
For information about other CPSS options, such as viewing routing tables or CPSS
connections, see Maintenance, chapter 33.8.
Dedicated CPSS cost

You can configure CPSS path cost for dedicated and shared CPSS. (Section 17.6.3
describes configuring shared CPSS cost.) The dedicated CPSS path cost value on the
Control, DCP, DS-3 II, E3, FRS, FRE or PE card can be:

To configure the dedicated CPSS cost, see the applicable card procedure:
To configure Control, DS-3 II and E3 card CPSS options

To configure DCP card CPSS options
Interface speed
On a Control card, you can configure a dedicated CPSS channel for speeds of 4, 8, 16,
48, 56 or 64 kb/s. On a DCP card, you can configure speeds of 4, 8, 16, 24, 32, 40, 48,
56 or 64 kb/s; 4 kb/s dedicated CPSS is available only on circuits 24 through 31 as a
slot option.
On a DS-3 II or E3 card, you can configure speeds of 8, 16, 48 or 56 kb/s. The larger
the bandwidth dedicated to CPSS, the faster CPSS messages are sent and received.
(The system automatically configures shared CPSS speed at connect time.)
On a Control, DS-3 II or E3 card, you configure the interface speed by selecting the
SPEED softkey.
On a DCP card, you configure the interface speed by selecting TRANSP_BW and
entering a starting bit position value from 1 to 8. Each bit position represents 8 kb/s.
For example, enter 2 for a 16 kb/s CPSS channel and 7 for a 56 kb/s channel.
To configure the interface speed, see the applicable card procedure:

Satellite delay
To transmit CPSS messages over a satellite link, you must use a Control, DCP,
DS-3 II, or E3 card dedicated CPSS circuit configured for satellite delay. To configure
satellite delay, select SATELLITE; to remove satellite delay, select NORMAL.
Node Parameters
(400)
17.6-19


NNP 95-2035-01-00-B
To configure the satellite delay, see the applicable card procedure:

Signalling Restrictions
You must configure primary rate card circuits for T1_SIG or E1_SIG signalling
before cross-connection to DCP card CPSS circuits. Table 20.1-2 lists the parameters
used to configure signalling for the PRI cards.

CONFIG CIRCUIT <CPSS-n> or <sn-cc> FUNCTION
SATELLITE/NORMAL*
SPEED
<speed>
NORMAL*
PATH_COST
SK000027
where
n is 1 to 4
speed is 4, 8, 16, 48, 56 or 64 (*)

CONFIG CIRCUIT <sn-cc> FUNCTION
TRANSP_BW
SATELLITE/NORMAL
<bw>
NORMAL*
PATH_COST
SK000030
where bw is the number of 8 kb/s elements (1 to 8)
17.6.5
Configuring 64 kb/s CPSS Channels

You can designate all or part of a 64 kb/s channel on a primary rate or data link as a
CPSS channel. A 64 kb/s channel on a T1 or E1 PRI circuit or a 64 kb/s DCC, DNIC
or 2B1Q circuit can be used as a CPSS channel by connecting the 64 kb/s channel to
a CPSS channel on a Control card or DCP card.
17.6-20
(400)
Node Parameters

NNP 95-2035-01-00-B

If the link terminates on the Dual T1 or Dual E1 card, the card only passes CPSS
transparently. If the link terminates on the Control card, a Dual T1 supports up to 24
CPSS channels; a Dual E1 card supports up to 30 on a CAS framed E1 or 31 on a CCS
or 31-channel framed E1.
You can configure the 64 kb/s CPSS channel from the perspective of the CPSS
channel or the 64 kb/s circuit.
The Dual E1-2 card does not support the termination of CPSS on the card but can
cross-connect dedicated CPSS resources. The NU bits in TS0 are used to
cross-connect CPSS information terminated on the Control card or DCP to another
Control card or DCP. See section 17.6.6 for more information.
Note
In single-shelf control-redundant systems, CPSS-4 is automatically configured to
64 kb/s and connected as the mate link. If you try to configure CPSS-4, a warning
message appears.
To connect a Control, DS-3 II or E3 card CPSS channel

You can connect a Control, DS-3 II or E3 card CPSS channel in one of two ways.
From the CPSS channel perspective, enter:
CONFIG CONNECT <CPSS> or <CPSS-n>
TO_CIRCUIT
DISC_FROM or DISCONNECT
<sn-cc> or <sn-l-cc>
SK000031
where n is 1 to 4 for a Control card, 1 or 2 for a Dual E3 card and 1 for a DS-3 II card
From the 64 kb/s circuit perspective, enter:
CONFIG CONNECT <sn-cc> or <sn-l-cc>
TO_CIRCUIT
DISCONNECT
<CPSS> or <CPSS-n>
SK000032
where n is 1 to 4 for a Control card, 1 or 2 for a Dual E3 card and 1 for a DS-3 II card
Node Parameters
(400)
17.6-21


NNP 95-2035-01-00-B
To connect a DCP card CPSS channel

You can connect a DCP card CPSS channel in one of two ways.
From the DCP channel perspective, enter:
CONFIG CONNECT <sn-cc>
TO_CIRCUIT
DISCONNECT
SK000033
where the first sn-cc is the DCP circuit configured to support a 64 kb/s circuit
From the 64 kb/s circuit perspective, enter:
CONFIG CONNECT <sn-cc> or <sn-l-cc>
TO_CIRCUIT
DISCONNECT
<sn-cc>
SK000034
where the second sn-cc is the DCP circuit configured to support a 64 kb/s circuit
17.6.6
Configuring CPSS over FDL and TS0

You can configure CPSS over FDL on the T1 and Dual T1 cards. The E1, Dual E1,
Dual E1-2, X.21, V.35 and MPA cards support CPSS over the 64 kb/s TS0
supervisory channel.
On E1, MPA, X.21 and V.35 PRI cards, you can use TS0 to terminate a CPSS channel
by cross-connecting it to a dedicated CPSS resource. Since CPSS is terminated on the
Dual E1 card, only the link TS0 option is used to enable or disable CPSS over TS0.
Dual E1-2 cards do not terminate CPSS on the card but can cross-connect dedicated
CPSS resources through the cards NU bits on TS0.
17.6-22
(400)
Node Parameters

NNP 95-2035-01-00-B

T1 cards
The FDL is a 4 kb/s channel available when ESF is configured on T1 links. (To
configure ESF, see chapter 20.6.) For the T1 card, you can use the FDL channel for
CPSS by cross-connecting it to a CPSS circuit on the Control card or the DCP card.
Both dedicated and shared CPSS circuits are supported.
When you connect a dedicated CPSS channel to the FDL, you must configure the
interface speed of the CPSS channel to 4 kb/s (see section 17.6.4). You cannot connect
FDL to a shared or dedicated CPSS circuit on a Dual T1 card, but you can enable
CPSS over FDL for the card when configuring the slot.
Note
CPSS on FDL cannot be terminated to Dual T1 cards if the host system is running
CPSSv2.
FDL is not available for CPSS connections on Dual T1-2 cards.
To configure FDL, see the procedure To enable or disable CPSS over FDL on Dual
T1 cards.
To connect a CPSS channel to the FDL, see the procedure To connect a CPSS circuit
to the T1 card FDL.
E1 cards
On E1 cards, you can use TS0 as a CPSS channel by cross-connecting it to a CPSS
circuit. In the resulting CPSS channel, only 16 kb/s of the available 64 kb/s
bandwidth is used.
When you connect a dedicated CPSS channel to TS0, you must configure the
interface speed of the CPSS channel to 16 kb/s (see section 17.6.4). For the E1 card,
connecting and disconnecting the dedicated resources CPSS channel effectively
enables and disables CPSS over TS0. The Dual E1 card terminates CPSS when the
CPSS option is enabled on the card. The CPSS option on the card can be disabled
without disconnecting the CPSS channel.
For the Dual E1-2 card, the NU bits in TS0 can be used to carry a CPSS channel from
the Control card or DCP card in one node to the Control card or DCP card in another
node. Both dedicated and shared CPSS channels are supported. A CPSSv1 or
CPSSv2 connection of either 4, 8 or 16 kb/s is allowed.
Node Parameters
(400)
17.6-23


NNP 95-2035-01-00-B
Note 1
Dual E1 and Dual E1-2 cards support three features that use the same NU bit
resources in TS0: SA4 Bit Error Rate, clear NU bits and CPSS over TS0. You can
enable only one of these three features at a time for the link. Any one of these features
can be used simultaneously with the E-bit option (see chapter 20.18).
Note 2
When an E1 HDSL module is installed on a Dual E1 card, you can use any timeslot
as a CPSS channel.
To configure TS0 on the Dual E1 card, see the procedure To enable or disable CPSS
over TS0 on Dual E1 cards.
To configure TS0 on the Dual E1-2 card, see To connect or disconnect a Control card
CPSS channel on FDL or TS0.
X.21 and V.35 PRI cards

On X.21 and V.35 PRI links, TS 0 corresponds to the supervisory channel. You can
use the X.21 or V.35 links TS0 to carry CPSS by cross-connecting it to a CPSS circuit
on the Control card or the DCP card.
The CPSS channel will occupy bit positions B7 and B6 of the supervisory channel.
You must configure the supervisory channel so that bit positions B7 and B6 are
unoccupied and not part of the HCM signalling frame. The framing bit of the HCM
frame must be in bit position B5, B3 or B6. See chapter 23.6 for more information.
Once the framing bit is in the correct position, the CPSS channel must be connected
to the X.21 or V.35 TS0 to enable CPSS.
MPA cards
The MPA card supports both shared and dedicated CPSS on each interface port. The
TS0 designated for each port must be configured seperately; however, configuration
of CPSS over TS0 is optional on a per port basis.
Either 8 kb/s or 16 kb/s CPSS can be configured on the TS0 supervisory channel. The
8 kb/s CPSS channel occupies bit position B7 of the supervisory channel and the 16
kb/s CPSS channel occupies bit positions B7 and B6. You must configure the
supervisory channel so that the required bit positions are unoccupied before
enabling CPSS on the link, for more information see chapter 20.20.
Once the framing bits are in the correct position, the speed of the CPSS channel must
be configured. To complete the CPSS circuit, the MPA card TS0 must be
cross-connected to the CPSS channel of the Control card or DCP.
If the message Not Enough Bandwidth appears when enabling CPSS for the
interface, the maximum number of channels available for data on the MPA card is
exceeded. For more information about bandwidth allocation, see chapter 20.20.
To enable 8 kb/s or 16 kb/s CPSS, see the procedure To configure CPSS over TS0
for MPA cards.
17.6-24
(400)
Node Parameters

NNP 95-2035-01-00-B

To enable or disable CPSS over FDL on Dual T1 cards

Note
Ensure that the link is configured for ESF before proceeding.
CONFIG SLOT <sn-l> OPTIONS FDL_CPSS/FDL_UNUSED*
To enable or disable CPSS over TS0 for Dual E1 cards

CONFIG SLOT <sn-l> OPTIONS TS0_OPTION CPSS_ON/CPSS_OFF*
To enable CPSS over TS0 for Dual E1-2 cards

1.
Enable CPSS over TS0 on the card, enter:

CONFIG SLOT <sn-l> OPTIONS PHYSICAL TS0_OPTION
CPSS_PIPE
2.
Connect the Dual E1-2 card link TS0 to the CPSS channel of either the
Control card or the DCP card.
a.
See To connect or disconnect a Control card CPSS channel on FDL or

TS0.
b.
See To connect or disconnect a DCP card CPSS channel on FDL or TS0.
To disable CPSS over TS0 for Dual E1-2 cards

CONFIG SLOT <sn-l> OPTIONS PHYSICAL TS0_OPTION CPSS_OFF*
To configure CPSS over TS0 for MPA cards

There are three steps to configure CPSS over TS0 for MPA cards.
1.
Move the MPA card framing and the HCM framing bits out of bit positions B7
and B6 (see section 20.20.7 for more information).
2.
Select either 8 kb/s or 16 kb/s bandwidth for CPSS transport on the link, enter:
CONFIG SLOT <sn-l> OPTIONS MORE CPSS
8K
16K
SK000692
Ensure that the speed matches the CPSS resource channel.

3.
Node Parameters
Connect the MPA card link TS0 to the CPSS channel of either the Control card
or the DCP card.
(400)
17.6-25


NNP 95-2035-01-00-B
a.

TS0.
b.
To disable CPSS over TS0 for MPA cards

CONFIG SLOT <sn-l> OPTIONS MORE CPSS DISABLE
To configure CPSS over TS0 for X.21 or V.35 cards

1.
Move the HCM framing bits out of bit positions B7 and B6 (see chapter 23.6 for
more information).
2.
Connect the link to the CPSS channel of either the Control card or the DCP card.
a.

TS0.
b.
To connect or disconnect a Control card CPSS channel on FDL or TS0

You can connect a Control card CPSS channel from the CPSS channel perspective or
from the cards FDL or TS0 perspective. This procedure is applicable to T1, E1,
Dual E1-2, MPA, X.21 and V.25 cards.
To connect or disconnect a DCP card CPSS channel on FDL or TS0

You can connect a DCP card CPSS channel from the CPSS channel perspective or
from the cards FDL or TS0 perspective. This procedure is applicable to T1, E1, Dual
E1-2, MPA, X.21 and V.25 cards.
From the CPSS channel perspective, enter:
TO_CIRCUIT
<sn-FDL> or <sn-TS0> or <sn-l-TS0>
DISCONNECT
SK000037
where sn-cc is a DCP circuit configured to support CPSS
From the FDL or TS0 perspective, enter:
17.6-26
(400)
Node Parameters

NNP 95-2035-01-00-B

CONFIG CONNECT <sn-FDL> or <sn-TS0> or <sn-l-TS0>
TO_CIRCUIT
<sn-cc>
DISCONNECT
SK000038
where sn-cc is a DCP circuit configured to support CPSS
17.6.7
Configuring Subrate CPSS Channels

In most cases, a node does not require a full 64 kb/s of bandwidth dedicated to CPSS
messages. You can configure a 64 kb/s channel on a T1, E1, or X.21 or V.35 PRI link
or a 64 kb/s DCC, DNIC or 2B1Q circuit to carry a subrate CPSS channel (less than
64 kb/s).
The Control card supports four dedicated CPSS channels that you can configure for
subrate speeds of 4, 8, 16, 48 or 56 kb/s and one shared CPSS channel that you can
configure for speeds of 4, 8 or 16 kb/s. The DCP card supports 31 dedicated CPSS
channels that you can configure for subrate speeds of 4, 8, 16, 24, 32, 40, 48 or 56 kb/s.
When you configure the DCP card to support 4 kb/s CPSS circuits, eight circuits are
set aside (circuits 24 through 31) for 4 kb/s use; the remaining 23 circuits are
available for n x 8 kb/s CPSS circuits, where n 8.
You can subrate-multiplex a subrate CPSS channel with HCV compressed voice and
data (either HCM or transparent).
You can connect subrate CPSS channels to the supervisory channel on X.21 and V.35
PRI cards. The bit positions that the CPSS channel occupies must be unoccupied and,
in the case of 8 through 48 kb/s CPSS channels, must not be part of the HCM
signalling frame. (A 56 kb/s CPSS channel is not possible on the supervisory
channel because the framing bit would have to be in bit position B0, which is not
permitted.)
Figures 17.6-7 and 17.6-8 show how the location of the framing bit affects where a
4 kb/s subrate CPSS channel occupies its five bit positions in an HCM frame. The
circuit to which the 4 kb/s CPSS channel is connected must be an HCM channel with
five empty bit positions following the framing bit. This could be a DCC circuit, DNIC
circuit, a 2B1Q circuit or an SRM. CPSS channels at 4 kb/s are supported by SRMs
on DNIC Line or 2B1Q Line cards with a DPM2 and SRMs on DSP2 and DSP3 cards.
For more information on framing bit locations, see chapter 23.6.
Node Parameters
(400)
17.6-27


NNP 95-2035-01-00-B
Figure 17.6-7: 4 kb/s CPSS Channel with Framing Bit at F0-B7

B7
B6
B5
B4
B3
B2
B1
B0
F0
F1
F2
F3
F4
F5
F6
F7
F8
F9
a = CPSS
7187

B7
B6
B5
B4
B3
B2
B1
B0
F0
F1
F2
F3
F4
F5
F6
F7
F8
F9
a = CPSS
7188
The subrate CPSS channels from 8 to 56 kb/s are transparent channels that occupy
as many of the most significant bit positions as are required, where each bit position
represents 8 kb/s. For example, a 16 kb/s subrate CPSS channel is a transparent
channel that occupies the two most significant bit positions (bit positions B7 and B6).
17.6-28
(400)
Node Parameters

NNP 95-2035-01-00-B

The circuit carrying the CPSS channel, or the SRM used to multiplex the subrate
CPSS channel with other voice or data channels, needs some preparation, depending
on whether it is a transparent or HCM SRM.
If a DCC, DNIC or 2B1Q circuit is carrying the CPSS channel, it must be
configured for transparent rate adaption and for a bandwidth equal to or greater
than the bandwidth of the CPSS channel.
If a transparent SRM is being used to subrate-multiplex the CPSS channel, the
transport bandwidth must be equal to or greater than the bandwidth of the CPSS
channel. Nothing needs to be done with the transport position.
If an HCM SRM is being used to subrate-multiplex the CPSS channel, the
bandwidth available for transparent channels must be equal to or greater than
the bandwidth of the CPSS channel. That is, the framing bit must be adjusted so
that the HCM frame does not occupy the bit position(s) that the CPSS channel
occupies.
Figures 17.6-9 and 17.6-10 show how the framing bit can be relocated for a 16 and
48 kb/s CPSS channel, respectively.
F0
B7
B6
B5
B4
B3
B2
B1
B0
F1
F2
F3
F4
F5
F6
F7
F8
F9
a = CPSS
or
a = sn-cc
a DCP
circuit
identifier
7189
Node Parameters
(400)
17.6-29


NNP 95-2035-01-00-B
Figure 17.6-10: 48 kb/s CPSS Channels with Framing Bit at F0-B6

B7
B6
B5
B4
B3
B2
B1
B0
F0
F1
F2
F3
F4
F5
F6
F7
F8
F9
a = sn-cc
7190
Note
If an SRM is carrying a CPSS channel, that SRM cannot be connected to the branch
channel of another SRM.
To configure a Control card CPSS channel

1.
Configure the DNIC or 2B1Q Line card or DSP card for subrate multiplexing
and either HCM or transparent rate adaption (see chapter 23.6).
2.
If you are connecting an 8 to 56 kb/s CPSS channel to an HCM SRM, adjust the
SRM framing bit so that it does not occupy the bit positions that the CPSS
channel will occupy (see chapter 23.6).
3.
Configure the SRM for CPSS and select the bandwidth to be dedicated to the
CPSS channel as 4_kbps, 8_kbps or 16_kbps.
When CPSS is connected to the SRM, the CPSS bandwidth is listed on the
display to the right under CPSS Speed.
CONFIG CIRCUIT <sn-cc-Mmm> FUNCTION CPSS
4_kbps
8_kbps
16_kbps*
SK000039
17.6-30
(400)
Node Parameters

NNP 95-2035-01-00-B
4.

From the switching shelf, connect an SRM to a circuit on a T1, E1 or X.21 or V.35
PRI link, a supervisory channel on an X.21 or V.35 PRI link, or a DCC, DNIC or
2B1Q circuit by entering:
CONFIG CONNECT <x-sn-Mmm> or <x-sn-cc-Mmm>
TO_CIRCUIT
DISCONNECT
SK000040
5.
Connect CPSS to the SRM (you cannot connect the SRM to CPSS).
CONFIG CONNECT <CPSS>
TO_CIRCUIT
DISC_FROM
<sn-cc-Mmm>
SK000041
The display indicates the subrate CPSS channel bandwidth.
To configure a 4 kb/s DCP card CPSS channel

1.
From the locally controlled or peripheral shelf, configure a DCP card to support
4 kb/s CPSS channels by selecting slot option 4KBPS.
CONFIG SLOT <sn> OPTIONS 4KBPS/NO_4KBPS*
2.
Connect the circuits.

TO_CIRCUIT
DISCONNECT
<sn-cc>
SK000042
where
the first sn-cc is one of the DCP circuits from 24 to 31
the second sn-cc is an SRS configured for CPSS or an SRM configured for HCM rate adaption
To configure an 8 to 56 kb/s DCP card CPSS channel (no SRMs)

1.
Node Parameters
Configure the DCP circuit for the CPSS bandwidth you want (see section 17.6.4,
Interface Speed).
(400)
17.6-31


NNP 95-2035-01-00-B
2.
Configure the DCC, DNIC or 2B1Q circuit for transparent rate adaption and
make sure that the circuits transport bandwidth is equal to that of the DCP (see
chapter 23.6).
3.
From the switching shelf, connect the DCP circuit to the DCC, DNIC or 2B1Q
circuit.
TO_CIRCUIT
DISCONNECT
<sn-cc> or <sn-cc-p>
SK000043
To configure an 8 to 56 kb/s DCP card CPSS channel (SRMs)

1.
Configure the DNIC or 2B1Q Line card or DSP card for subrate multiplexing
and either HCM or transparent rate adaption (see chapter 23.6).
2.
If you are configuring an HCM SRM, adjust the SRM framing bit so that it does
not occupy the bit positions that the CPSS channel will occupy (see
chapter 23.6).
3.
From the switching shelf, connect the SRM to a circuit on a T1, E1 or X.21 or V.35
PRI link, a supervisory channel on an X.21 or V.35 PRI link or a DCC, DNIC or
2B1Q circuit.
CONFIG CONNECT <sn-Mmm> or <sn-cc-Mmm>
TO_CIRCUIT
DISCONNECT
SK000044
4.
Connect the DCP circuit to the SRM. (You cannot connect the SRM to a DCP
circuit.)
TO_CIRCUIT
DISCONNECT
<sn-Mmm> or <sn-cc-Mmm>
SK000045
17.6-32
(400)
Node Parameters

NNP 95-2035-01-00-B
17.6.8

Network Manager CPSS Connections

A network manager can exchange CPSS messages with a node through:
the serial ports on the backplane

the serial port on a DCP card
the PSTN and modems connected to the node
any channel on primary rate or data links
Each method requires a different configuration. This section describes connecting

through serial ports or the PSTN and modems. Section 17.6.4 describes connecting
through primary rate or data links (see Table 17.6-2 for a list of relevant
configuration parameters).
Connecting to the serial ports on the backplane

If the computer running the network manager is connected to one of the serial ports
on the backplane, you must set the port type for CPSS communications (see
chapter 17.3), and set the baud rate to match the baud rate set by the network
manager. If the network manager is connecting to a DCP card serial port, you only
need to set the baud rate.
Connecting to the PSTN and modems

If the computer running the network manager is exchanging CPSS messages with
the node through modems and the PSTN, you must configure:
the port type for CPSS communications (see chapter 17.3)

the serial port baud rate to match the baud rate of the modem (see chapter 17.3)
the telephone number (NOC_NUM) of the modem connected to the network
manager (see section 17.6.3)
17.6.9
FRS Card CPSS Connections

CPSS transport over frame relay allows 3600 MainStreet bandwidth managers on
either side of a frame relay network to communicate. Encapsulated CPSS frames are
transmitted over the network. The network handles all frames transparently; that is,
the network transmits all frames end-to-end without examining the frame contents.
Before connecting a CPSS circuit to the FRS card, a circuit on the FRS card must be
configured as an encapsulation circuit. To configure frame relay encapsulation
circuits on the FRS card, see chapter 25.10.
Encapsulated cirsuits on the FRS card can either be connected to a dedicated CPSS
circuit on the DCP card or to a dedicated CPSS circuit on the Control card.
Node Parameters
(400)
17.6-33


NNP 95-2035-01-00-B
Note
The FRS card does not support shared CPSS connections.
CPSS rerouting after fault detection in a frame relay network

The NNI is the interface which allows two network devices, like two FRS cards, to
communicate. Both network devices must be configured with a link management
protocol that accommodates network device-to-network device communication.
This protocol allows network devices to monitor and relay link and PVC
information across the network.
The LMI-NNI detects unavailable links in the frame relay network and signals the
Control card. Figure 17.6-11 shows what happens when a fault is detected within the
frame relay network. The elements within the network communicate through the
LMI and notification of the faulty link is passed through the network to node A and
node B. The DCP cards are notified of the fault in the link and reroute CPSS along an
alternate path through node C.
Figure 17.6-11: CPSS Rerouting
3600 MainStreet
Node A
F
R
S
D
C
P
C
T
L
F
R
S
FRS X DCP
D
C
P
C
T
L
3600 MainStreet
Node C
FRS X DCP
LMI
NNI
LMI
NNI
Frame Relay Network
Preferred path
Alternate path
Fault
F
R
S
D
C
P
C
T
L
3600 MainStreet
Node B
FRS X DCP
10484
17.6-34
(400)
Node Parameters

NNP 95-2035-01-00-B
17.6.10

FASTbus CPSS Connections

For the FRE and PE card, CPSS connectivity is provided by encapsulating CPSS over
frame relay over the FASTbus. Figure 17.6-12 shows how two shelves can be
connected through CPSS without using TDM trunks or additional cabling. The
dotted lines indicate CPSS links between FASTbus elements.
Figure 17.6-12: FASTbus CPSS Connections
FRE
FRE
CPSS links
FRATM
FRE
FRE
FRE
FRE
FRATM
FASTbus
7620
FASTbus CPSS connections from one station to another are made in NMTI by
connecting one of the two available CPSS resources (CPSS1 or CPSS2) to a target
FASTbus station number. At the target station, a complementary connection must
be made. A special DLCI is automatically used for each frame relay CPSS link.
When you specify a FASTbus to CPSS1 link, the DLCI that is used is 1020; when you
specify a FASTbus to CPSS2 link, the DLCI used is 1021.
Two byte DLCIs are used for CPSS to prevent frame relay encapsulated CPSS from
being switched onto WAN links by FRE or PE cards. CPSS connections to WAN
DLCIs are blocked. FRE or PE cards can be configured only to switch data from
FASTbus DLCIs in the range 2000 to 3983 (see chapter 25.7).
Node Parameters
(400)
17.6-35


NNP 95-2035-01-00-B
To connect FASTbus CPSS circuits

The number of FASTbus CPSS connections is limited to two. To connect a CPSS
identifier (CPSS 1 or 2) to a FASTbus CPSS identifier, enter:
CONFIG CONNECT
CPSS<x>
F<y>-CPSS
TO_DLC F<y>-CPSS
TO_DLC CPSS<x>
SK000046
where x is 1 or 2 and y is 1 to 64
Note
FASTbus CPSS connections can only be made to FASTbus circuits.
Figure 17.6-13 shows the CONFIG CONNECT CPSSx screen used to configure
FASTbus CPSS.
Figure 17.6-13: CONFIG CONNECT CPSSx NMTI Screen
FRE
Stations:nn
P412-H1-00
From
CPSS1
Toronto:A
Status
Unknown
Alarms:1
Connected To
--
11-May-1997
Status
--
8:35a
Traffic Group
* Indicates that the CPSS link is Active and Up
CONFIG CONNECT CPSS1
16-
17.6-36
2-DISCONNECT
7-
3-TO_DLC
8-CANCEL
(400)
4-INFO_RATE
9-QUIT
50-
Node Parameters

NNP 95-2035-01-00-B

To configure CPSS timers

CONFIG MORE CPSS <CPSSx> TIMERS
T200 <value>
TACK <value>
N200 <value>
T203 <value>
SK000047
CPSS timers (available on the Release 2 FRE and PE cards only) define the
performance of the CPSS link over the FASTbus. Table 17.6-4 defines the types of
timers available.
Table 17.6-4: CPSS Timers
Timer
17.6.11
Description
T200
This is the amount of time the return ACK has for the point to point link layer
transport times. The timeout value can be between 1 and 30 s (default is 4 s).
TACK
This is the amount of time that the information frame that is received can wait for
acknowledgment. The TACK timeout value can be between 0.5 and 20 s (default
is 1 s).
N200
This establishes the number of retries that are permitted. The number of retries
that are permitted can be between 1 and 10 (default is 5).
T203
This establishes the amount of time the link can remain inactive. The timeout value
can be between 20 and 600 s (default is 30 s). T203 must be greater than twenty
times the T200 value.
CPSS Routing Protocol

CPSS routing protocol allows you to configure an FRS, FRE or PE card to run either
the DV router or the LS router. Typically, the routing protocol is used for
3600 MainStreet series bandwidth managers nodes containing one or more FRS, FRE
or PE cards in an LS routing network.
Normally, FRS, FRE or PE cards run the same router as their host Control card (the
LS router). This means that all topology changes in the network, such as CPSS link
state, are forwarded to the FRS, FRE or PE card. However, when the only CPSS
connection for the FRS, FRE or PE card is to the host Control card (these FRS, FRE or
PE cards are known as leaf nodes), there is a greater strain placed on the CPSS
resources of the Control card when providing the FRS, FRE or PE card with the LS
routing information. For this reason, you can configure the FRS, FRE or PE card to
run the DV router through the CPSS routing protocol. When it runs the DV router,
the Control card sends only the node availability information to the FRS, FRE or PE
card, thereby reducing the amount of activity on the CPSS resources of the Control
card.
Node Parameters
(400)
17.6-37


NNP 95-2035-01-00-B
There are two valid CPSS routing protocol configurations.
router version 1
This configures the card to run DV router.
host router
This configures the card to run the same routing protocol as the host Control
card.
To keep the amount of activity on the CPSS resources of the host Control card
manageable, you can configure only two FRS, FRE or PE cards as host router in an
LS routing node. The remaining FRE or FRS cards must be configured for router
version 1.
The CPSS routing protocol for an FRS, FRE or PE card can be configured through
NMTI as follows.
To configure CPSS routing protocol

ROUTER_V1*/ HOST_RTR
SK000048
Note
Do not configure an FRS, FRE or PE card for ROUTER_V1 in an LS routing node if
the card is carrying CPSS circuit or serial port connections. If you configure the FRS,
FRE or PE card for ROUTER_V1, the CPSS in the network may be disrupted.
Do not configure an FRS or FRE card for ROUTER_V1 in an LS routing node if the
card is carrying CPSS circuit or serial port connections. If you configure the FRS or
FRE card for ROUTER_V1, the CPSS in the network may be disrupted.
17.6-38
(400)
Node Parameters

NNP 95-2035-01-00-B
17.7
17.7 Backplane Card Communications

Backplane Card Communications

This chapter describes backplane card communications and fault handling.
17.7.1
Overview
Backplane card communication links connect the Control card directly to
DCP-based cards. These links provide internal CPSS communications between the
Control card and a DCP-based card without affecting the throughput of the
DCP-based card. Although backplane CPSS is not configurable, the backplane card
communication links can be configured as shared or dedicated through NMTI.
The following DCP-based cards provide configurable backplane card
communication links.
17.7.2
CPC
DCP
FRE
FRS
PE
Backplane Card Communication Types

You can configure the backplane card communication link as shared or dedicated
using the following softkeys:
SHARED to configure the link for 16 kb/s shared CPSS

DEDICATED to configure the link for 64 kb/s dedicated CPSS
Configuring the backplane card communications link to the Control card as
dedicated optimizes the data transfer performance of the card. When the backplane
card communications link is configured for dedicated CPSS, there must be a
dedicated CPSS channel available on the Control card.
For the DCP, FRE, FRS and PE cards, backplane card communications are default
configured as shared.
For CPCs the default is dedicated CPSS to handle the messaging throughput needs
of ISDN backup and channel search applications.
Node Parameters
(400)
17.7-1


NNP 95-2035-01-00-B
Caution
For CPCs, it is recommended that the backplane card communication link remain
configured for dedicated CPSS. If the link is configured for shared CPSS, it will limit
the number of D channels the CPC can process.
To configure backplane card communications

Log onto the locally controlled or peripheral shelf and enter:
CONFIG SLOT <sn> OPTIONS CARD_COMM DEDICATED/SHARED*
17.7.3
Fault Handling
The FRE and PE cards provide configurable fault handling for backplane card
communications. A card can be set to handle faults in one of two modes: standard
or enhanced.
Note
Enhanced mode is only available to FRE and PE cards that support enhanced mode.
If a packet card that does not support enhanced mode is inserted in a slot configured
for enhanced mode a revision mismatch alarm is raised. For more information,
contact your Newbridge representative.
Standard mode
Standard mode provides card database synchronization at the expense of traffic
speed. Priority is placed on maintaining database synchronization between the
Control card and the packet card, even in the event of communication difficulties. To
assure database continuity, the packet card is automatically reset when
communication difficulties are experienced.
Enhanced mode
In enhanced mode, network or system operators have more control over the action
taken by the Control card when card communications faults are detected. This
control comes at the expense of database configuration synchronization between the
Control card and the packet card. Temporary database configuration mismatches
are possible in enhanced mode, but are resolved automatically by the system once
the fault clears.
Enhanced mode introduces minor and major fault counts, database re-sends, a major
fault count reset threshold and a major fault card dead threshold.
17.7-2
(400)
Node Parameters

NNP 95-2035-01-00-B

Caution
Changing from enhanced to standard mode while a database re-send is in progress
will result in a disruption of service.
Minor fault count

A minor fault occurs when a management packet from the Control card is left
unacknowledged for a long period of time. When a minor fault occurs:
the minor fault count is increased by 100

a database re-send takes place
a Minor Fault Count Warning alarm is raised if the fault count was zero prior to
the occurrence of the fault
The minor fault count is reduced as re-sent management packets are successfully
acknowledged. When the minor fault count is reduced to zero, a Minor Fault Count
Normal alarm is raised. Minor fault alarms are considered non-service affecting and
default to the diagnostic alarms queue. If the minor fault count exceeds the
system-defined minor fault count threshold, the minor fault count is reset and the
major fault count is increased by 250. The minor fault count threshold is 500.
A card reset will reset the minor fault count.
Major fault count
A major fault occurs when the backplane card communication link goes down or
when too many minor faults occur. Two major fault counts are maintained: a current
major fault count and an overall major fault count.
When a major fault occurs:
a Card Comm Problem alarm is raised with the parameter of the alarm indicating
the cause of the problem
both the current and overall major fault counts are increased by 250
the Control card attempts to restart the link if the link is down; each failed
attempt causes the current and overall major fault count to increase by 250
if the link is successfully restarted, a database re-send takes place

After the link is restarted and the database re-send is complete, all fault counts that
are greater than zero are reduced by 20 for every 5 minutes that the backplane card
communication link remains up. When the current major fault count and overall
major fault count are both zero, a Card Comms Normal alarm is raised.
A manual card reset will reset both the major fault counts. A software-initiated card
reset will only reset the current major fault count.
Node Parameters
(400)
17.7-3


NNP 95-2035-01-00-B
Major fault count reset threshold

The major fault count reset threshold determines how many current major faults are
tolerated by the Control card before it forces a software-initiated card reset. The
major fault count reset threshold is configurable with a range of 1 to 30 000 and a
default of 5000. The major fault count reset threshold can also be configured as
unlimited.
Caution
Changes to the major fault count reset threshold take effect immediately and cause
a card reset if the current major fault count exceeds the new major fault count reset
threshold. When a card reset occurs a Card Reset alarm is raised.
Major fault card dead threshold

The major fault card dead threshold determines how many overall major faults are
tolerated before the Control card forces a packet card out of service. The major fault
card dead threshold is configurable with a range of 1 to 30 000 and a default of 500.
The major fault card dead threshold can also be configured as unlimited.
Caution
Changes to the major fault card dead threshold take effect immediately and cause a
card to be declared dead if the current major fault count exceeds the new major fault
card dead threshold. When a card is declared dead a Card Dead alarm is raised.
Database re-sends
When a link is successfully restarted after a link failure, a database re-send takes
place. The Control card uses a database re-send to attempt to re-send all database
items needed by the packet card to restore database synchronization after the card
communication difficulty.
Database re-sends are attempted as soon as the link permits and proceed slowly to
increase the chances that re-sent information will be processed successfully by a
busy packet card. As re-sent management packets are successfully acknowledged,
the major and minor fault counts are reduced.
A card receiving a database re-send has an NMTI slot status of RSND or DB Resend.
Packet card-initiated resets
If the flow of CPSS packet data stops due to a serious fault, FRE and PE cards can
initiate a self-reset. Packet card-initiated resets cannot be prevented by using
enhanced mode fault handling.
17.7-4
(400)
Node Parameters

NNP 95-2035-01-00-B

To configure fault handling

CONFIG SLOT <sn> OPTIONS CARD_COMM FLT_HNDLING
ENHANCED/STANDARD*
THRESHOLD
CARD_RESET
CARD_DEAD
<threshold>
UNLIMITED
SK000913
where threshold is in the range 1 to 30000 with a default of 500 for CARD_RESET and 5000 for
CARD_DEAD
Node Parameters
(400)
17.7-5

NNP 95-2035-01-00-B
18. Redundancy

NNP 95-2035-01-00-B
18.1
18.1 Control Redundancy

Control Redundancy
This chapter explains how to do the following tasks:
18.1.1
configure control-redundant and non control-redundant systems

configure standby modes
display system demerits
force and program activity switches
replace a redundant Control, DS-3 or E3 card while the system is in operation
Understanding Control Redundancy

Control redundancy provides backup system control to ensure continuity of service
if a system card or cable fails. Table 18.1-1 shows the cards and cables that you must
configure for redundancy in each shelf.
Table 18.1-1: Control Redundancy
Card or Cable
Enhanced
Locally
Controlled
Shelf
3600, 3645, 3664 and 36120

MainStreet Control cards
3600+ MainStreet Control card
Expander card
Locally
Controlled
Shelf
Switching
Shelf
Peripheral
Shelf
HSPS
Shelf
HSPS 2
Shelf
Clock card
Switching card
SI card
SI cable
DS-3 or DS-3 II card
DS-3 link
E3 card
E3 cable
Redundancy
(400)
18.1-1


NNP 95-2035-01-00-B
3600+ MainStreet Control card

The 3600+ MainStreet bandwidth manager has a fully operational control complex,
consisting of a Control card and an associated Timing card. Control redundancy is
the duplication of the control complex to provide service protection against single
component failures. Control complex redundancy in a 3600+ MainStreet system
requires both an active and an inactive Timing and Control card. Each Control card
must have a mate Timing card.
The control complex can be configured for simplex or redundant operation.
Redundant operation works in either partitioned mode or hot standby mode. The
control complex is configured for simplex operation by default.
18.1.2
Configuring Control Redundancy

Table 18.1-2 lists the control redundancy configuration parameters. Each parameter
has a list of options with any default option marked with an asterisk.
Table 18.1-2: Control Redundancy Configuration Parameters and Options
Control
Cards (1)
3600+ MainStreet
Control Card
DS-3 and
DS-3 II
Card
E3
Card
Activity switch (forced)
RLS_CTRL
Activity switch (programmed)
name of the day

daily
time (hh:mmA or P or H)
Automatic activity switch disable
enable
disable*
3600, 3645, 3664 and 36120

MainStreet Control cards
redundancy
simplex*
redundant
Parameter
Options
single shelf (2)

dual shelf (2)
18.1-2
(400)
Redundancy

NNP 95-2035-01-00-B
Control
Cards (1)
3600+ MainStreet
Control Card
DS-3 and
DS-3 II
Card

E3
Card
Options
3600+ MainStreet control complex

redundancy
simplex
redundant*
DS-3 and E3 card redundancy (3)
simplex (unprotected)
interface
access
Fast protection switching (3)
enable*
disable
AIS
OOF
BER
Fast protection switching
enable*
disable
alarm time
error rate
error time
Standby mode
hot
Parameter
partitioned* (warm (4))
Notes
1. These are the 3600, 3645, 3664 and 36120 MainStreet Control cards.
2. These options apply only when the Control card is configured as redundant.
3. These parameters apply only to the DS-3 II card.
4. The term warm partitioned is not used with the 3600+ MainStreet Bandwidth Manager. Partitioned and warm partitioned
have the same functionality.
Table 18.1-3 lists the locations of the control redundancy configuration procedures
for the Control, DS-3 II or E3 card.
Table 18.1-3: Control Redundancy Configuration Procedures
Redundancy
Section
Control redundancy information and SI cable

information display
18.1.3
System demerits display
18.1.5
Card replacement
18.1.9
(400)
18.1-3


NNP 95-2035-01-00-B
Note
To configure control redundancy for the HSPS equipped with DS-3 cards, you must
install jumpers for the DS-3 cards on the backplane (see Installation, Task 0500:
Setting the Redundancy Jumpers). Control redundancy can be program-configured
for DS-3 II cards.
18.1.3
Configuring Control Redundancy Parameters

A control-redundant 3600+ MainStreet bandwidth manager has two Control cards
installed on the enhanced locally controlled shelf. All other control-redundant 3600
MainStreet series bandwidth manager systems can be either a single-shelf
configuration with two Control cards or a dual-shelf configuration with a Control
card in each shelf.
Redundant DS-3 and E3 card pairs also operate with one active card and one inactive
card.
The basic functions of the Control cards in a control-redundant configuration is the
same for the 3600+ MainStreet Bandwidth Managers and all other 3600 MainStreet
series bandwidth managers. At any time, one Control card is responsible for the
operation of the system. This card is called the active Control card. The other Control
card is called the inactive Control card. The inactive Control card is always powered
up and informed of the state of the system so that it is ready to assume control if
necessary.
When a control-redundant system is powered up, the Control card that is powered
up first becomes the active Control card. After the power-up, you can distinguish the
active Control card from the inactive Control card by checking the Activity LED and
seven-segment Display LED on the cards.
The Activity LED is lit on the active Control card, DS-3 card and E3 card and is
off for the inactive card.

The Display LED flashes a number in the usual pattern for the active Control card
and displays a dash () in a 0.5 seconds on, 0. 5 seconds off pattern for the inactive
Control card.
The act of transferring control from one Control card to the other is called an activity
switch.The removal or major failure of an active Control card always causes an
activity switch regardless of the control redundancy mode. The removal or major
failure of an inactive Control card has no effect.
18.1-4
(400)
Redundancy

NNP 95-2035-01-00-B

Configuring 3600, 3645, 3664 and 36120 MainStreet Control cards for
redundancy
For the locally controlled shelf, configure the redundancy mode as:
REDUNDANT for control redundancy

DUAL_SHELF for dual-shelf redundancy
SNGL_SHELF for single-shelf redundancy
SIMPLEX if you do not want control redundancy
The system must meet these conditions before you can configure a single-shelf
system as control-redundant.
The shelf Select jumper on the backplane next to the Control card in slot 9 must
be set to position A.
An appropriate filler plate must be installed in slot 10.
The dedicated CPSS-4 circuit must be available for the mate link (if it is already
in use, disconnect it).
The Expander card slot must be configured as empty.
To configure 3600, 3645, 3664 and 36120 MainStreet Control cards for
redundancy
CONFIG SYSTEM REDUNDANT/SIMPLEX*
DUAL_SHELF
SNGL_SHELF
SK000049
Note
For more information about upgrading to single-shelf redundancy, see Maintenance,
chapter 40.3.
Configuring 3600+ MainStreet Control card redundancy

For the enhanced locally controlled shelf, configure the redundancy mode as:
REDUNDANT for control redundancy

SIMPLEX if you do not want control redundancy
The node number must be set on the active Control card (optionally set on the
inactive Control card) before performing this procedure. To set the node number, see
Installation, Task 1420: Setting the Node Number for Enhanced Locally Controlled
and Locally Controlled Shelves.
Redundancy
(400)
18.1-5


NNP 95-2035-01-00-B
In simplex mode, an inactive Control card will flash a u on its faceplate 7-segment
display to indicate that it is unavailable. If the active Control card is removed from
its slot, or if a serious card failure occurs, an activity switch occurs.
Caution
Because the databases of the inactive and active Control cards are not synchronized,
if an activity switch occurs in simplex mode a major service disruption can occur. All
current configuration information can be lost, but the node will be operational for
new configurations.
Switching from simplex mode to redundant mode

After a change from simplex mode to redundant mode, you can insert redundant
cards into the inactive Control card slot. If a card is already installed, its status will
change from unavailable to inactive.
The active card will then attempt to restart the mate link. After the mate link is up,
the Control card will perform the following checks.
Compatible software generic: the software generic of the inactive Control card
and of the active Control card are compared to make sure that they are
compatible. If the software generics are not compatible an Incompatible Mate
Generic alarm is raised.
Compatible CPSS address: the CPSS address of the inactive Control card and of
the active Control card are compared to make sure that they are compatible. If the
CPSS addresses are not the same, the mate link is brought down and a Wrong
Mate Node Number alarm is raised.
Address auto-configure: if the CPSS address of the inactive Control card is
unassigned it will be automatically configured with the CPSS address, domain
number and router version of the active Control card.
If all checks are successfully completed a Talking to Mate CTL is raised. If the mate
link is lost, a Not Talking to Mate alarm is raised and the active Control card will
continue to try to restart the mate link.
In hot standby mode, if one Control card has a Bank-B Memory module installed but
the other Control card does not, the inactive card raises a Memory Module Mismatch
alarm. See Table 35.8-17 in Maintenance.
To configure 3600+ MainStreet Control card redundancy

CONFIG SYSTEM REDUNDANT*/SIMPLEX
Configuring DS-3 II and E3 card redundancy

For DS-3 II and E3 cards, configure one of the three redundancy modes listed and
described in Table 18.1-4.
18.1-6
(400)
Redundancy

NNP 95-2035-01-00-B

Table 18.1-4: Redundancy Modes for DS-3 II and E3 Cards

Redundancy
Mode
Card/Interface
Description
Simplex
(UNPROTECTD)
DS-3 II, DE3, SE3
No redundancy is provided. Service is discontinued in the

event of an interface or link failure.
Interface
(INTFC_PROT)
DS-3 II, DE3, SE3
A second DS-3 II or E3 card protects the DS-3 II or E3

interfaces and switching interface cables, but the DS-3 II or
E3 line(s) are not protected.
Access
(ACCES_PROT)
DS-3 II, DE3, SE3
A second DS-3 II or E3 card protects the DS-3 II or E3

interfaces and switching interface cables. Parallel DS-3 or
E3 line(s) are supplied by the customer for redundancy
protection for the line(s).
To configure DS-3 II and E3 card redundancy

CONFIG SYSTEM
UNPROTECTD
NTFC_PROT
ACCES_PROT
SK000050
Note
Before you change a DS-3 II or E3 card protection mode from unprotected to accessor interface-protected, or vice versa, you must remove any card from the mate HSPS
slot. After you configure the protection mode, replace the inactive card.
To display control redundancy information

You can display control redundancy information from the switching, locally
controlled, enhanced locally controlled or the peripheral shelf, or the DS-3 II or E3
card. For switching shelves, you can also display SI cable information by selecting
ON_SLOT.
MAINT
MORE
REDUNDANT
ON_SLOT
<sn>
SK000051
Table 18.1-5 lists the fields that appear in the Control card redundancy menu.
Redundancy
(400)
18.1-7


NNP 95-2035-01-00-B
Table 18.1-5: Field Descriptions for Control Redundancy

Field
18.1.4
Description
Redundancy
No redundancy
Partitioned
Hot Standby
Protection Mode
Simplex or Access Protection or Interface Protection

The reason for the last activity switch (if logged on to an E3 card)
Time Switch
The day and time of a programmed automatic activity switch

Unassigned
Last Switch
The time of the last activity switch

No switch since reset
System Demerits
The demerit values for both Control, DS-3 or E3 cards
SI Cables
The status of the four SI cables (if logged on to a peripheral shelf, HSPS or
HSPS2)
Configuring Standby Modes

The standby mode refers to the relationship between an active Control card and an
inactive Control card or an active and inactive DS-3 or E3 card. You can configure a
control-redundant system to operate in one of two modes:
hot standby mode

partitioned (or warm) mode
All 3600 MainStreet series bandwidth managers support hot standby and
partitioned (or warm) modes.
Hot standby
In hot standby mode, the configuration databases of the two cards are the same. Any
change to the database of the active card is automatically copied to the database of
the inactive card. An activity switch occurs after a database reconcile is completed.
Activity switches only occur if failures on the inactive Control card are less severe
than those on the active Control card; otherwise the active Control card will continue
to operate.
When an activity switch occurs in a hot standby system, calls in progress are not
dropped. The output timing of the system can experience a short disturbance and
there can be a short period of corruption of data or a short burst of noise on voice
circuits. This period lasts no longer than 125 ms. Maintenance operations in progress
could be lost and configuration changes in progress could be aborted. After a hot
standby activity switch occurs, the newly inactive card restarts itself and reconciles
its database with the database of the newly active card.
18.1-8
(400)
Redundancy

NNP 95-2035-01-00-B

If the active Timing card fails or is removed in a 3600+ MainStreet system, a fast
activity switch occurs. A fast activity switch can only occur when:
the Control cards are configured for hot standby

the database is reconciled
If the active or inactive 3600+ MainStreet Control card loses timing from its
associated Timing card and a fast activity switch cannot occur, the following actions
are taken:
a Timing Failure alarm is raised against the Timing card

demerits are raised against the Timing card (see Table 18.1-6)
a CL pattern flashes on the 7-segment faceplate display of the Control card to
indicate the lack of the associated Timing card

if the active and the inactive Control cards do not detect their associated Timing
card, the Timing card is removed from service and a Card Removed alarm is
raised. If the Control card still detects its associated Timing card, a Card Dead
alarm is raised against the Timing card.
If the active Timing card is lost, the inactive 3600+ MainStreet Control card will also
raise a Timing Failure alarm and report demerits. Timing Failure alarm subcodes are
used to distinguish which of the two Control cards raised the alarm. Demerits
reported for the inactive Control card are substantially less than those reported for
the active Control card when the active Timing card is lost. See Table 18.1-6.
Note
3600+
If the active or inactive

MainStreet Control card has lost timing from an active
Timing card, all UCS and HSA cards are removed from service.
In hot standby mode, if one 3600+ MainStreet Control card has a Bank-B Memory
module installed but the other Control card does not, the inactive card raises a
Memory Module Mismatch alarm. See Table 35.8-17 in Maintenance.
Partitioned
In partitioned (or warm) mode, the active Control card does not report any changes
in the configuration of the system to the inactive Control card and the inactive
Control card does not monitor the status of the system. Since the configuration
databases of the two cards can differ, database synchronization cannot be
guaranteed in partitioned mode. Partitioned mode permits replacing and upgrading
of the software or hardware of either or both cards with minimal interruption to
service.
The 4602 MainStreet Intelligent NetworkStation or MainStreetXpress 46020
Network Manager provides backup and restore procedures that can be used to
transfer the configuration database from one card to the other in partitioned mode.
In partitioned mode, if background diagnostics are enabled for the inactive card, the
tests cycle through test 1 (program integrity), test 2 (RAM integrity) and test 3 (NV
RAM integrity). Only tests 1, 2 and 3 are available for directed diagnostic tests as
well (see Maintenance, chapter 39.1).
Redundancy
(400)
18.1-9


NNP 95-2035-01-00-B
Caution
Partitioned mode redundancy is for maintenace purposes only and is not
recommended as an operational mode.
If an activity switch occurs in partitioned mode, calls in progress are dropped, all
interface cards are reset and maintenance operations and configuration changes in
progress are lost. Changes made to the configuration database since the system was
placed in partitioned mode are also lost.
Configure standby mode as:
HOT for hot standby mode

PARTITION or WARM for partitioned (or warm) mode (default)
Note
The PARTITION option applies to the 3600+ MainStreet Bandwidth Manager, 3645
MainStreet Control cards, DS-3, DS-3 II or E3 cards.
The WARM option applies to 3600, 3664 and 36120 MainStreet Control cards.
To configure standby mode

MAINT MORE REDUNDANT
HOT
18.1.5
PARTITION* or WARM*
SK000052
Displaying System Demerits

In both hot standby and partitioned modes, the active card (Control, DS-3 II or E3
card) keeps an estimate of its operating quality and that of the inactive card. This
estimate, called the system demerits value, increases as the number of problem
conditions increases. The conditions that contribute to the system demerits are listed
in Table 18.1-6.
18.1-10
(400)
Redundancy

NNP 95-2035-01-00-B

Table 18.1-6: Conditions Contributing to System Demerits

Condition
Demerits
DS1 Circuit failure on a DS-3 card
15
Failure of 50% of circuits on an interface card
20
Adverse Control card diagnostic result
100
Any hardware diagnostic failure
100
8+ module diagnostic fault
100
Start-up diagnostic failure

Timing card diagnostic failure
100
150
(1)
Inactive Control card has lost contact with the active Timing card
(1)
200
E3 link alarm
250
Inactive Control card is not synchronized to the active shelf
275
Inactive Timing card is not synchronized to the active Timing cards (1)
275
Inactive Clock card not phase-locked to active Clock card
275
DS-3 link fault
350
Missing the Expander card
400
Missing a peripheral shelf
400
Missing a switching shelf
400
DE3 connection to switching shelf broken
400
8+ module absence
400
Activity switch that is not forced or automatic
500
Loss of Narrowband Switch module (1)
500
Loss of Broadband Switch module (1)
550
DE3 card is out of service
800
Database reconciliation in progress
1000
Control card loss of associated Timing card
(1)
2000
Missing both peripheral shelves
2500
Switching card absence
2500
Control card absence
3000
Clock card absence
3000
Loss of Control card
3500
(1)
DS-3 card absence
5500
DE3 card absence
5500
Notes
1. This condition applies only to the 3600+ MainStreet Bandwidth Manager.
Redundancy
(400)
18.1-11


NNP 95-2035-01-00-B
In hot standby mode only, an activity switch occurs if the system demerits value for
the active card is greater than the value for the inactive card. If the other Control card
is present, an activity switch is guaranteed when:
common control equipment fails

the currently active cable connected to the Switching Interface card is removed
the Switching Interface card or Clock card installed in the same shelf as the active
Control card is removed
The softkeys used to display system demerits depend on the type of shelf or card to
which you are logged on.
To display system demerits for a locally controlled or enhanced locally

controlled shelf
CONFIG SYSTEM
To display system demerits for a locally controlled, enhanced locally controlled,

switching or peripheral shelf, DS-3 II or E3 card
MAINT MORE REDUNDANT
To display system demerits for a Control card

MAINT ON_SLOT <CTL>
18.1.6
Configuring an Activity Switch

An activity switch is a transfer of system control from the active to inactive Control,
DS-3, DS-3 II or E3 card.
18.1-12
(400)
Redundancy

NNP 95-2035-01-00-B

An activity switch occurs if:
the active card loses power

the active card is removed from the system
the active Control card detects a fatal software error
the active Clock card is removed or loses power
the active Timing card is removed or loses power
the active Switching Interface card or cable is removed
the DS-3 link status on the inactive DS-3 or DS-3 II card is superior to the DS-3
link status on the active DS-3 or DS-3 II card
the active DS-3 II card detects an AIS, OOF or BER fault that is not detected by
the inactive DS-3 II card during a specified time period
the active E3 card detects an E3 fault (LOIS, LIS, AIS, Loss of Frame Alignment
or Distant Alarm) that is not detected by the inactive E3 card during a specified
time period
the detected E3 error rate (ERROR_RATE) exceeds the configured value on the
active E3 card but not on the inactive E3 card
the system demerits value for the active card is greater than the value for the
inactive card (hot standby mode only)
an activity switch is forced
the time for an automatic activity switch is reached
a node or network manager requests an activity switch
In a redundant switching shelf configuration, the active shelf does not allow an
activity switch to take place if the inactive switching shelf has lost power.
Alarms
Two alarms are raised by activity switches.
A System Restart (Active) alarm is raised by the newly active Control, DS-3,
DS-3 II or E3 card.
A System Restart (Inactive) alarm is raised by the newly inactive Control, DS-3,
DS-3 II or E3 card.
In both alarms, the first parameter is the slot of the card that lost activity. The second
parameter is the reason for the activity switch. (For more information, see
Maintenance, Table 35.8-23.)
Database reconciliation
A database reconciliation is the process of two Control, DS-3, DS-3 II or E3 cards
comparing their databases and making them the same. If differences are detected
between the two databases, the system assumes that the database of the active card
is correct and changes the database of the inactive card to match that of the active
card. A database reconciliation does not affect service.
Redundancy
(400)
18.1-13


NNP 95-2035-01-00-B
Only Control cards in a control-redundant system or DS-3, DS-3 II or E3 cards in a

redundant slot and pair configuration in hot standby mode can reconcile their
databases. They do so under two conditions:
after an activity switch (the newly inactive card restarts itself then reconciles its
database with that of the newly active card)
when the two cards begin to communicate after a period of not communicating
A fully loaded control-redundant locally controlled or enhanced locally controlled
shelf takes 20 min to reconcile the database. A fully loaded control-redundant dual
peripheral shelf takes 15 min and a switching shelf redundant configuration takes 2
min for each connected peripheral shelf for reconciliation (20 min for a fully loaded
system).
During database reconciliation, the message Reconcile in Progress and the
number of records processed appear in the data area for node management sessions
running on both the active and inactive cards. The system demerits value for the
inactive card increases by 1000 points.
An inactive Control card displays an L (for Load) on the display LED.
The inactive DS-3 or DS-3 II card cycles the faceplate LEDs as follows:
DS-3, DS1 and S1 LEDs remain off for 0.25 seconds

DS-3 LED lights for 0.25 seconds
DS-3 LED goes off and the DS1 LED lights for 0.25 seconds
DS1 LED goes off and the S1 LED lights for 0.25 seconds
The inactive E3 card cycles the faceplate LEDs as follows:
the alarm LEDs light individually from top to bottom for half a second each
after the bottom LED goes off, all alarm LEDs remain off for half a second
Refresh the screen (<Esc> <R>) to update the number of records and the demerits
value.
When the message Reconcile in Progress disappears from the screen and the
system demerits value for the inactive card decreases by 1000 points, the database
reconciliation is complete.
To force an activity switch

You can force an activity switch between a pair of Control cards, DS-3 or DS-3 II
cards, or E3 cards from the switching shelf, peripheral shelf, Control card, DS-3 or
DS-3 II card, or E3 card.
MAINT MORE REDUNDANT RLS_CTRL
Note
Do not force an activity switch during a database reconciliation.
18.1-14
(400)
Redundancy

NNP 95-2035-01-00-B
18.1.7

Configuring Fast Protection Switching

You can enable a form of activity switch called a fast protection switch, which occurs
when the active DS-3 II or E3 card detects a fault during a specified time period.
You can also configure the time over which the active card must detect the fault
before the switch occurs. If this fault time period is less than the alarm declare time,
the activity switch occurs before any alarms are declared, allowing the card pair to
restore service before applying trunk conditioning or call rerouting. (For
information on setting the alarm declare and clear time, see Maintenance,
section 35.4.1.)
Note
If the DS-3, DS-3 II or E3 card is configured for fast protection switching, an activity
switch will occur for a link fault based on increased demerits, even if the time
specified for fast protection switching has not elapsed.
Protection switching options

For both the DS-3 II and E3 cards, you can enable or disable fast protection switching
with the PROT_SWTCH softkey. If you disable fast protection switching, an activity
switch can still take place if a condition that normally causes a switch (such as card
removal) takes place.
For DS-3 II cards, you can configure the fault time for AIS, BER and OOF faults.
Table 18.1-7 lists and describes the DS-3 II card options.
Table 18.1-7: DS-3 II Fast Protection Switching Options
Option
Reason for
Activity
Switch
Description
Range
AIS
AIS fault
Sets the time over which the AIS fault must be

detected before the activity switch occurs.
500 ms
1500 ms
3000 ms
5000 ms
OOF
OOF fault
Sets the time over which the OOF fault must

be detected before the activity switch occurs.
500 ms
1000 ms
1500 ms
2000 ms
BER
Error rate
exceeded
Sets the error rate and the time over which the
error rate is integrated, before an activity
switch occurs.
10-6, 3 s
10-6, 10 s
10-4, 2 s
10-4, 6 s
Redundancy
(400)
18.1-15


NNP 95-2035-01-00-B
For E3 cards, you can configure:
a fault time to apply to all E3 faults

an E3 error rate that will trigger a fast protection switch
an error time over which the error must be integrated
Table 18.1-8 lists and describes the E3 card options.
Table 18.1-8: E3 Fast Protection Switching Options
Option
Reason for
Activity
Switch
Description
Range
ALARM_TIME
E3 fault
Sets the time over which the

E3 fault must be detected
before the activity switch
occurs.
100 ms to 30 s in 10 ms
increments (Default is 100 ms)
ERROR_RATE
ERROR_TIME
Error rate
exceeded
Sets the error rate and the

time over which the error rate
is integrated before an activity
switch occurs.
Error rate: 1 x 10-3 to 1 x 10-8 in

exponential increments
Error time: 1 to 3600 s in 1 s
increments
Default is error rate of 1 x 10-6
integrated over 3 s
18.1-16
(400)
Redundancy

NNP 95-2035-01-00-B

To configure DS-3 II fast protection switching

CONFIG SLOT <DS3> OPTIONS PROT_SWTCH
ENABLE*/DISABLE
AIS
OOF
BER
500_msec* 1500_msec 3000_msec 5000_msec 500_msec* 1000_msec 1500_msec 2000_msec
10-6_3sec*
10-6_10sec
10-4_2sec
10-4_6sec
SK000053
To configure E3 fast protection switching

CONFIG SLOT <E3id> OPTIONS PROT_SWTCH
ENABLE*/DISABLE
ALARM_TIME
ERROR_RATE
<alarm_time>
<range>
ERROR_TIME
<error_time>
SK000054
where
alarm_time is 100 ms to 30 s in 10 ms increments (100*)
range is 1E-3 to 1E-8 in exponential steps (1E-6*)
error_time is 1 to 3600 s in 1 s increments (3 s*)
18.1.8
Configuring Automatic Activity Switching

You can program a control-redundant shelf or card to do an activity switch at a
specific time each day or each week. An automatic activity switch distributes the
usage of the two Control, DS-3, DS-3 II or E3 cards and informs you of their
condition.
You can enable or disable the activity switch, and you can set the switch to occur on
a daily basis or on a specific day every week. In either case, you can set the time of
day for the automatic activity switch.
When the system time (in the case of a daily activity switch) or time and day (in the
case of a weekly activity switch) match the values entered, the active card
automatically tries to release activity to the inactive card.
Redundancy
(400)
18.1-17


NNP 95-2035-01-00-B
To configure automatic activity switching

MAINT MORE REDUNDANT TIMESWITCH
ENABLE/DISABLE*
<day>
DAY
TIME
<hh:mmA or P or H>
<DAILY>
SK000055
where
day is the name of the day
hh is the hour (1 or 2 digits)
mm is the minute (2 digits)
Note
If the system time has not been set, the node manager records the time entered here
in the format <hh:mmR>, where R represents the time elapsed since a system reset.
An automatic activity switch does not occur unless you set the system time.
For example, enter 3:17 P.M. as <3:17P> or <15:17H>. If you do not enter <A>, <P>
or <H>, the system assumes A.
18.1.9
Replacing a Control, DS-3, DS-3 II or E3 Card

This procedure minimizes disruption to service when replacing a Control, DS-3,
DS-3 II or E3 card in a control-redundant system configured for hot standby mode.
To replace a Control, DS-3, DS-3 II or E3 card

1.
Make sure that the card you want to replace is inactive. If it is active, establish
a node management session with the switching shelf, peripheral shelf, Control
card, DS-3, DS-3 II card or E3 card, then force an activity switch by entering:
MAINT MORE REDUNDANT RLS_CTRL
2.
Enter:
MAINT MORE REDUNDANT PARTITION or WARM
18.1-18
(400)
Redundancy

NNP 95-2035-01-00-B

Note
The PARTITION option applies to the 3600+ MainStreet Bandwidth Manager, 3645
MainStreet Control cards, DS-3, DS-3 II or E3 cards.
The WARM option applies only to 3600, 3664 and 36120 MainStreet Control cards.
The information is passed to the inactive card; the card is then configured for
partitioned mode.
3.
Replace the inactive card with the new card.

For instructions on removing and installing cards, see Maintenance, chapter 40.8
(for the Control card) or chapter 40.9 (for the DS-3, DS-3 II card or E3 card).
4.
Enter:
MAINT MORE REDUNDANT HOT
The cards reconcile their databases. Wait for the reconciliation to finish before
starting another procedure.
Redundancy
(400)
18.1-19

NNP 95-2035-01-00-B
18.2
18.2 Protection Switching

Protection Switching
This chapter introduces protecting connections, provides guidelines for designing
protection switching circuits and explains how to configure protecting connections.
18.2.1
Understanding Protection Switching

As shown in Figure 18.2-1, you can specify two connections for each circuit: a
preferred connection and a protecting connection.
Figure 18.2-1: Terminology for Protecting Connections
Preferred
circuit
Voice card
Preferred
connection
Control card
Primary rate
card
DX
PBX
A2-1
A1-1 (PC)
Primary
rate link
Protecting
connection
Voice card
Control card
Primary rate
card
DX
= Active connection
= Inactive connection
PC = Protected circuit
NPC = Not protected circuit
A3-1
A4-1 (NPC)
Primary
rate link
Protecting
circuit
4176
The preferred connection is the connection that a circuit uses if that circuit is
available.
The protecting connection is the connection that a circuit uses if the preferred
connection fails or cannot be completed. When this happens, the protected circuit is
connected to the protecting circuit and the data follows the alternative route. This
automatic switching from a preferred connection to a pre-configured protecting
connection is called protection switching. There is a short disruption to the data flow
when a switch to a protecting connection occurs.
In general, any two circuit types that can be used to form a preferred connection can
also be used to form a protecting connection. The exceptions are DSP circuits,
circuits connected to branch channels of SRMs and compressors and voice
compression subchannels on Dual E1 and T1 cards.
A protecting connection is made under some conditions. If the preferred connection
is configured and available, the protecting connection is not needed. If the preferred
connection is not configured or not available, the protecting connection is made, if
possible.
Redundancy
(400)
18.2-1


NNP 95-2035-01-00-B
For protection switching involving tandem nodes in an E1 and T1 environment, set

the fault signalling for each internode circuit to out-of-service type A or B. This
causes the failure of an internode link to be detected by other nodes and triggers a
switch to alternative connections.
For example, in Figure 18.2-2, each of the circuits in link E1 (1) at node (1) is
protected by a circuit in link E1 (3) and each of the circuits in link E1 (2) at node (3)
are protected by a circuit in link E1 (4).
Figure 18.2-2: Out-of-Service Signalling for Tandem Nodes
3600 MainStreet node (2)
Out-of-service
fault signalling
E1 (1)
E1 (2)
E1 (3)
E1 (4)
Phone
Phone
3600
MainStreet node (1)
Fault
3645
MainStreet node (3)
3645 MainStreet node (4)
Protecting connection
Active (and preferred) connection
7154
If link E1 (1) fails, the following will occur.
An alarm is raised at node (1) and protection switching occurs at the node (1);
protected circuits are switched to their protecting circuits on E1 (3).

The fault signalling configured at node (2) is carried on E1 (2) to node (3).
If the circuits on link E1 (1) are configured for seized or idle fault signalling at node
(2), node (3) is not informed that link E1 (1) is out of service, so the node does not
switch the circuits on link E1 (2) to their protecting circuits on link E1 (4).
By configuring the circuits on link E1 (1) for out-of-service signalling at node (2),
node (3) is informed that link E1 (1) is out of service and the node switches the
protected circuits on link E1 (2) to their protecting circuits on link E1 (4).
18.2-2
(400)
Redundancy

NNP 95-2035-01-00-B
18.2.2

Configuring Protection Circuits

Table 18.2-1 lists the protection circuit configuration parameters.
Table 18.2-1: Protection Switching Configuration Parameters and Options
Parameter
Options
Protecting connections
protect by
protecting
Protected circuit disconnection
preferred
protection
Note
Protection switching applies to all cards except DSP, circuits connected to SRM
branch channels and compressors and voice compression subchannels on Dual E1
and T1 cards.
18.2.3
Designing Protecting Circuits

The subjects discussed in this section should be considered before configuring
protecting circuits.
Automatic override
Normally, protecting circuits are not used for other applications. However, you can
set up a shared environment. In a shared environment, a connection involving a
protecting circuit can be broken at any time without warning, so that the protecting
circuit can connect to the circuit it has been configured to protect.
For example, in Figure 18.2-3, circuit A1-1 is connected to circuit A2-1 (the preferred
connection) and is configured for a protecting connection to circuit A3-1. Circuit
A4-1 is connected to circuit A3-1. When all circuits are available, the connection
between circuits A1-1 and A2-1 is active and the connection between circuits A4-1
and A3-1 is active.
Redundancy
(400)
18.2-3


NNP 95-2035-01-00-B
Figure 18.2-3: Preferred Connection Available

Preferred
circuit
Voice card
PBX
Preferred
connection
Control card
Primary rate
card
DX
A2-1
A1-1 (PC)
Primary
rate link
Protecting
connection
Voice card
Control card
Primary rate
card
DX
= Active connection
= Inactive connection
PC = Protected circuit
NPC = Not protected circuit
A3-1
A4-1 (NPC)
Primary
rate link
Protecting
circuit
4177
However, if circuit A2-1 becomes unavailable for connection, circuit A1-1 switches
to its protecting connection with A3-1 and the connection between A3-1 and A4-1 is
overridden. Circuit A1-1 switches back to its preferred connection when circuit A2-1
becomes available.
Circular protection
The node management software does not let you configure a circular protecting
connection. For example, in Figure 18.2-3, circuit A2-1 cannot act as a protecting
circuit for circuit A4-1.
However, you can establish a chain of connections. Circuit A2-1, for example, could
be protected by a fifth circuit.
Super-rate protection
When you connect a protecting super-rate circuit to an unprotected circuit, the
unprotected circuit must be a super-rate circuit running at the same speed as the
protected circuit. A protecting super-rate circuit must have the same number of DS0s
and bandwidth as the protected circuit.
Using different cards

Do not protect a circuit with a circuit located on the same card as the preferred
connection (for example, do not connect circuit A1-1 to circuit A2-1 and protect it
with A2-2). If the preferred circuit becomes unavailable for connection, it is usually
due to a card or link failure, rather than circuit failure, so the protecting circuit is also
unavailable for connection.
Compatibility
When planning protection connections, make sure that the protected circuit is
compatible with the protecting connection.
18.2-4
(400)
Redundancy

NNP 95-2035-01-00-B

Note
Only the E&M and OCU-DP channel units support protection switching. All other
channel units do not support protection switching.
For the 3645 MainStreet system, the maximum number of circuits configured for
protection switching is 375.
Activity Qualified Access

AQA lets you specify a protecting connection for a voice or data circuit using V.35
DCCs and NTUs. The V.35 circuit is connected to an NTU configured with call
set-up information. If a preferred connection goes down, AQA uses pin 108 on the
V.35 DCC to transmit DTR (high) to the NTU, at which point the NTU initiates a call
to another NTU connected to a V.35 DCC in the other node.
When the NTU detects DTR low, it drops the call and the connection switches back
to the preferred path.
Figure 18.2-4 shows a sample application.
Figure 18.2-4: Activity Qualified Access
64 kb/s
Transparent
V.35
DCC
V.35
DCC
Preferred link
E1
card
DTE/Master
(pin 108 is forced high
if preferred path fails)
E1
card
64 kb/s
Transparent
DTE/Slave
(pin 108 is forced high
always)
Switched
64 kb/s
network
NTU
V.35
DCC
E1
card
NTU
4010
V.35 circuits involved in a protecting connection must be configured for DTE and
then configured as the master circuit or the slave circuit.
The AQA master circuit forces DTR high and transmits it to the NTU if the preferred
connection goes down. The slave circuit has DTR forced high at all times. Do not
make any changes to the control leads from the control leads menu (see
Maintenance). Changing the control leads could cause a protecting call to be
dropped.
If you try to configure the V.35 circuit for AQA before configuring it for DTE, the
system displays the message AQA only applicable to circuits configured for DTE
mode. If you try to change the mode from DTE to DCE, the system displays the
message AQA is configured, PROCEED will override; if you press PROCEED,
AQA is disabled.
Redundancy
(400)
18.2-5


NNP 95-2035-01-00-B
After the protecting connection is made, the AQA configuration (master, slave or
disabled) cannot be changed. If you try to change the configuration, the system
displays the message Circuit must be disconnected before proceeding.
Chapter 22.3 describes the procedure for configuring V.35 circuits for AQA.
18.2.4
Configuring Protecting Connections

A protecting connection can be made from the perspective of the protected circuit or
the protecting circuit.
If you enter the protected circuit with the CONNECT softkey, select PROT_BY
and enter the protecting circuit identifier.
If you enter the protecting circuit with the CONNECT softkey, select
PROTECTING and enter the protected circuit identifier.
To disconnect a connection without defining another one, use the DISCONNECT
softkey, and select PREFERRED for the preferred connection or PROTECTION for
the protecting connection.
Note
If one of the circuits in the connection is on a T1 or E1 card that has a CCM, two
softkeys appear: COMP_CONV and NO_CONV. Select COMP_CONV if you want
companding conversion to be done on that connection; otherwise select NO_CONV.
The data area display indicates whether or not companding conversion is being
done for a connection by displaying Yes or No under the heading Conv.
18.2-6
(400)
Redundancy

NNP 95-2035-01-00-B

To configure protecting connections

CONFIG CONNECT <sn-cc> or <x-sn-cc>
PROT_BY
PROTECTING
COMP_CONV
DISCONNECT
PROTECTION
PREFERRED
NO_CONV
SK000056
To configure TTC2M cards as a protecting connection

CONFIG CONNECT <sn-cc> RAP+ID
PROT_BY
PROTECTING
<sn-cc>
SK000776
To disconnect the protecting TTC2M card connection

CONFIG CONNECT <sn-cc> DISCONNECT
PREFERRED
PROTECTION
SK000777
Select PROTECTION to disconnect the protecting circuit.

Select PREFERRED to disconnect the preferred circuit. This selection does not
disconnect the protecting circuit that is configured for that circuit.
Redundancy
(400)
18.2-7

NNP 95-2035-01-00-B
18.3
18.3 PRI Redundancy

PRI Redundancy
This chapter introduces PRI redundancy and explains how to do the following tasks:
18.3.1
configuring redundancy
handling failures
forcing an activity switch
handling fault processing
clearing card failures
Understanding PRI Redundancy

You can configure the system so that two primary rate cards are connected to a
single corresponding primary rate link, for example, two E1 cards to an E1 link. One
card is active (drives the primary rate line) while the other is on standby. In most
cases, the two PRI cards must be in the same locally controlled or peripheral shelf.
Two T1 cards configured as a redundant pair can be installed either on the same
shelf, or one on the A shelf and one on the B shelf.
The standby card detects the presence of incoming signals on the link, but cannot
drive the link because of a high impedance termination.
If the system detects a fault with the active card, the node management software
decides whether to switch to the standby card based on its operating rules.
Switching from the active card to the standby card causes a brief disruption in
service.
If the active card and the standby card differ in their reports of the state of the link,
the node manager starts fault processing on the card that declares the more severe
link fault. Fault processing assesses the condition of a card. If a card is determined
to be faulty, it is declared failed.
Hardware requirements
The following cards support primary rate interface redundancy:
Redundancy
E1 cards equipped with E1 LIMs

T1 cards equipped with T1 LIMs or CSU modules
X.21 PRI cards
V.35 PRI cards
(400)
18.3-1
18.3 PRI Redundancy


NNP 95-2035-01-00-B
The following cards do not support primary rate interface redundancy:
Dual E1 and Dual E1-2 cards

Dual T1 cards
T1 cards equipped with a DSX-1 module
The redundant interface card pair must be permanently connected to the primary
rate link using an external Y-connector so that faulty cards can be replaced without
disruption to service. Redundancy kits consist of faceplate connectors and Y cables
and are available for T1 links, E1 links and X.21 or V.35 PRI links. For details on
installation, see Installation, Task 1605: Connecting External Devices to Peripheral,
Enhanced Locally Controlled or Locally Controlled Shelves.
See chapter 18.1 for a description of control redundancy for DS-3 or DS-3 II and E3
cards.
18.3.2
Configuring PRI Redundancy

Table 18.3-1 lists the PRI redundancy configuration parameter.
Table 18.3-1: PRI Redundancy Configuration Parameter and Options
Parameter
Options
Redundant PRI pair
protect by
no protection*
Table 18.3-2 lists the locations of the PRI redundancy configuration procedures.
Table 18.3-2: PRI Redundancy Configuration Procedures
Section
Clear card failures
18.3.7
Clear outstanding demerit points
18.3.6
Force an activity switch
18.3.5
Note
18.3-2
(400)
Redundancy

NNP 95-2035-01-00-B
18.3.3
18.3 PRI Redundancy

Configuring PRI Redundancy Parameters

When you configure two slots as a redundant primary rate interface pair, you
designate one the master and the other the slave. The master slot configuration
parameters are automatically applied to the slave slot. All configuration of slot
attributes, circuit attributes, or connections for the redundant pair must be done
through the master slot. Access to the slave slot or its circuits is blocked, except for
the maintenance menu. If the master slot is reconfigured, the slave slot configuration
is automatically updated to match.
Note
The designations of master and slave are used only to indicate which of the
redundant pair can be configured. They are independent of which card is active.
When a slot becomes active, it stays active for as long as possible, whether it is the
master or the slave.
To configure PRI redundancy

CONFIG SLOT <sn> OPTIONS MORE
NO_PROTECT*
PROT_BY
<sn>
SK000057
where
the first sn is the identifier of the master slot
the second sn is the identifier of the slave slot
Note
When a redundant primary rate interface pair is deconfigured, the two cards operate
independently. Both cards become active and drive the line. If the Y cable still
connects the two interfaces to the same primary rate link, there is a conflict on the
line. Disconnect the cards or connect them to separate primary rate links before
deconfiguring them.
When a redundant primary rate interface pair is deconfigured, the slave slot is reset
to the default configuration settings (including no connections). The slot that was the
master retains all configuration information.
18.3.4
Handling Failures
To handle failures, you need to know the operating rules for a redundant primary
rate interface pair.
Redundancy
(400)
18.3-3
18.3 PRI Redundancy


NNP 95-2035-01-00-B
Operating rules
When you power up the system, the member of a redundant primary rate interface
pair that powers up first is designated the active card and the other member becomes
the standby card. This is independent of which card is in the master slot.
When you power down the system, any card failures are lost.
If only one member of the pair is present, it is always the active card and the system
does not try to switch to the other card regardless of the state of the active card. A
card can be absent because it has been removed or it has been declared failed.
If both members of the pair are present and one card declares the beginning or end
of a link fault (called an event), that card starts a two-second timer. If another event
occurs within those two seconds, the card restarts the two-second timer.
When two seconds have elapsed with no events, the system compares the severity
of the link faults being declared by the two primary rate cards and acts according to
the operating rules listed below (see Figure 18.3-1).
Figure 18.3-1: Operating Rules for Redundant Primary Rate Pair
Declaration
of beginning
or end of
link fault
Is the
active card
link fault more
severe?
Yes
An activity switch occurs.

Fault processing begins on this card.
If the newly active card declares a link fault,
trunk conditioning will be applied (if configured).
Yes
An activity switch does not occur.

Fault processing begins on this card.
If the active card declares a link fault,
Yes
An activity switch does not occur.

Fault processing does not occur.
If the active card declares a link fault,
No
Is the
standby card
link fault more
severe?
No
Are the
link faults
of equal
severity?
5449
Rule 1: The card that has declared the less severe link fault (including no link fault)
is designated as the active card and the card that has declared the more severe link
fault is designated as the standby card (this may require an activity switch).
Rule 2: The system begins fault processing on the card that has declared the more
severe link fault.
18.3-4
(400)
Redundancy

NNP 95-2035-01-00-B
18.3 PRI Redundancy

Rule 3: If the two link faults are equally severe, there is no activity switch and no
fault processing.
Rule 4: If the active card is still declaring a link fault, trunk conditioning is applied if
the slot is so configured.
Link faults
A link fault is a problem with a primary rate link. A card declares the beginning of a
link fault by raising one of the alarms listed in the left column of Table 18.3-3. The
faults are numbered in order of decreasing severity. Faults with the same number
have equal severity. When a card declares the end of a link fault, it raises the
corresponding alarm listed in the right column. Link fault alarms are raised for the
active card only and are listed in the alarm queue under the master slot identifier.
No alarms appear in the alarm queue under the slave slot identifier.
Table 18.3-3: Alarms for Declaring Beginning and End of Link Faults
Beginning of Link Fault Alarm
End of Link Fault Alarm
T1 link
1 Red Alarm
Red Alarm Cleared
2 Failed State
Framing Err Rate Exceeded
Failed State Cleared

Framing Err Rate Normal
3 Yellow Alarm
Yellow Alarm Cleared
E1 link
1 Framing Alarm
Incoming AIS
Framing Alarm Cleared

Incoming AIS Cleared
2 Multi-frame Alarm
Incoming TS16 AIS
Multi-frame Alarm Cleared

Incoming TS16 AIS Cleared
3 Failed State
Failed State Cleared

Framing Err Rate Normal
4 Distant Alarm
TS16 Distant Alarm
Distant Alarm Cleared

TS16 Distant Alarm Cleared
X.21 or V.35 PRI link

1 Framing Alarm
Framing Alarm Cleared
2 Distant Alarm
Distant Alarm Cleared
Fault processing cannot be initiated when the two members of a redundant interface
pair declare different link faults with the same severity (for example, Failed State
and Framing Err Rate Exceeded), because fault processing is done only on the card
declaring the more severe link fault. However, if one card declares a Yellow Alarm
and the other card a Red Alarm, the card that declared the Yellow Alarm (the less
severe alarm) becomes the active card if it is not already and fault processing starts
for the card declaring the Red Alarm.
Redundancy
(400)
18.3-5
18.3 PRI Redundancy

18.3.5

NNP 95-2035-01-00-B
Forcing an Activity Switch

An activity switch occurs when the active primary rate interface card goes on
standby and the standby primary rate card becomes active; that is, all connections
for the old active card are broken and re-established with the new active card.
Caution
Switching from the active card to the standby card causes a brief disruption in
service.
Ones density on T1 links

The CSU module provides a keep-alive signal consisting of unframed all ones (blue
alarm). If the interface transmits more than 15 consecutive zeros, or the node clock
stops, the module transmits the keep-alive signal to the network.
Caution
The all-ones density is not maintained during a switch between T1 cards equipped
with CSU modules.

To force an activity switch, select the MAKE_ACT softkey from the peripheral or
locally controlled shelf This forces the card in the slot indicated to become active if
possible; that is, if the card has not been declared failed and is not undergoing fault
processing.
MAINT ON_SLOT <sn> MAKE_ACT
Alarms
During an activity switch, the system raises a card Activity Change alarm. When you
display the alarm queue containing the card Activity Change alarm, the subcode is
the slot identifier of the new active card, the first parameter is a software
representation of the slot identifier of the new active card, and the second parameter
is the reason code for the activity switch. Table 18.3-4 lists the reason codes. Reasons
3 through 8 are the alarms that caused the activity switch (the activity switch
occurred because the active card declared the alarm listed and the standby card
declared a less severe alarm or no alarm).
For example, if the active card declares a Red Alarm and the standby card does not
do the same within two seconds, the standby card becomes the active card (an
activity switch). A card Activity Change alarm is raised with parameter 2 set to 3,
because a Red Alarm declaration caused the activity switch.
18.3-6
(400)
Redundancy

NNP 95-2035-01-00-B
18.3 PRI Redundancy

Table 18.3-4: Reason Codes for Card Activity Change Alarm

Activity
Change Code
Activity Change Reason
Requested switch (MAINT ON_SLOT MAKE_ACT) selected
Active interface card removed or interface redundancy deconfigured
Red Alarm/Framing Alarm/Incoming AIS
Multi-Frame Alarm/Incoming TS16 AIS
Failed State
Yellow Alarm/Distant Alarm
TS16 Distant Alarm
Active card has too many failed circuits
If there is an activity switch and the new active card does not declare a link fault, the
system does not invoke protection switching because the primary rate link is still in
service. Protection switching is invoked only if the link is out of service; that is, if
both members of the pair have declared a link fault and the link is configured for
two-way trunk conditioning for the class of fault being declared by the active card
(chapter 18.2 explains protection switching).
18.3.6
Handling Fault Processing

When a discrepancy occurs between the severity of link faults declared by the two
members of a redundant primary rate interface pair, fault processing is carried out
on the card that has declared the more severe link fault. This determines whether the
card should be declared failed and made unavailable to its mate. Fault processing
continues until one of the following events occurs.
The card accumulates 70 or more demerit points (the card is declared failed).
The card declares the end of the link fault.
The two cards declare link faults of equal severity, including none (fault
processing can be carried out for only one member of the pair at a time).
Fault processing is automatically carried out in two cases:
when the active card declares a more severe link fault (there is an activity switch
and fault processing begins on the old active card)

when the standby card declares a more severe link fault (there is no activity
switch and fault processing begins on the standby card)
Fault processing consists of assigning demerit points to the card that appears to be
at fault according to the schedule listed in Table 18.3-5.
Redundancy
(400)
18.3-7
18.3 PRI Redundancy


NNP 95-2035-01-00-B
Table 18.3-5: Fault Processing Demerit Points

Fault Processing Action
Demerit Points
Fault processing begins on the old active card (there is an activity switch).
12
Fault processing begins on the standby card (there is no activity switch).
Fault processing continues.
10 every 30 s
Fault processing stops before the card is declared failed.
-1 every 4 h
To clear outstanding demerit points

To clear outstanding demerit points, select CLR_FAULTS from the locally controlled
or peripheral shelf. The CLR_FAULTS softkey appears only if the card has
outstanding demerit points and has not been declared failed. You can clear
outstanding demerit points for both cards by removing and re-installing either card.
When one card fails, the demerit points for the other card are cleared.
MAINT ON_SLOT <sn> CLR_FAULTS
Example
Both members of a redundant interface pair have no outstanding link faults. The
active card declares a Red Alarm. Two seconds later, the standby card has still not
declared a link fault, so an activity switch occurs between the active card and the
standby card and fault processing starts on the old active card (12 points). The
difference still exists 30 seconds later (12 + 10 = 22 points). The Red Alarm is cleared
and fault processing stops. If there is no more fault processing on that card, the 22
demerit points are cleared in 88 hours (22 points 4 hours/point).
If the card does not clear the Red Alarm, it accumulates 72 demerit points
(12 + 10 [3/0.5] = 72) after three minutes and the node manager declares the card
failed.
18.3.7
Clearing Card Failures

If a card accumulates 70 or more demerit points or if one third or more of the circuits
on the card fail background or directed diagnostics, the card is declared failed. The
Status LED goes off and the card is no longer available for use by the system. The
card is placed in bypass to isolate it from the line. The demerit points for the mate
card (if any) are cleared and the mate card operates as if the failed card were not
present.
18.3-8
(400)
Redundancy

NNP 95-2035-01-00-B
18.3 PRI Redundancy

Alarms
When a card is declared failed, a Card Failure alarm is raised (see Maintenance,
Table 35.8-6). When you display the alarm queue containing the card Failure alarm,
the subcode is the slot identifier of the failed card (master or slave slot), the first
parameter is a software representation of the slot identifier of the failed card and the
second parameter is the reason code for the card failure, where:
1 indicates an unstable card (a card that has accumulated 70 or more demerit
points during fault processing)

2 indicates too many failed circuits
Caution
Use the loopback and bypass maintenance functions (invoked by selecting

LOOPBACK or BYPASS under the MAINT ON_SLOT menu) carefully because
they can lead to a card being declared failed.
To clear card failures

To clear the failure using the node manager, select the RET_SERV softkey. The
RET_SERV softkey appears only if the card has been declared failed. It also clears
outstanding demerit points.
MAINT ON_SLOT <sn> RET_SERV
Note
You can also clear the failure, without using the node manager, by removing and
re-installing either card of the redundant pair.
Redundancy
(400)
18.3-9

NNP 95-2035-01-00-B
19. System Cards

NNP 95-2035-01-00-B
19.1
19.1 Understanding System Card Configuration

Understanding System Card

Configuration
This chapter summarizes the configuration parameters in this part of the manual
and shows how they apply to each system card.
19.1.1
Understanding System Cards

The 3600 MainStreet series bandwidth managers support configurable system cards
as follows:
Control cards (3600 MainStreet series bandwidth managers)

Expander card (3600 MainStreet systems and locally controlled 36120 MainStreet
systems only)
Switching card (3645 MainStreet systems and switching shelf controlled 36120
MainStreet only)
Common Carrier card
Test card
GFC3
Control cards
The Control card provides all common control node management facilities for the
system.
For the 3600, 3645, 3664 and 36120 MainStreet Control cards in switching shelf
controlled systems, system control is shared between the switching and peripheral
shelf Control cards.
Expander card
The Expander card is used in locally controlled systems to increase the input and
output handling capacity of the Control card from 6 UCSs to 8, 12 or 16 UCSs,
depending on the variant you install.
Switching card
Each Switching card installed in a switching shelf increases the digital cross-connect
switching capacity of the switching shelf Control card by 64 Mb/s. Each Switching
card is connected to a peripheral shelf, DS-3 card or E3 card.
System Cards
(400)
19.1-1


NNP 95-2035-01-00-B
Common Carrier card

The Common Carrier card is installed in peripheral and locally controlled shelves to
provide four channel unit positions.
Test card
The Test card is installed in peripheral, locally controlled, and enhanced locally
controlled shelves to provide test access to voice and data circuits. The
user-installable Test module for the Test card provides analog and digital testing.
GFC3
The GFC3 is installed in peripheral and locally controlled shelves to provide analog
and digital tone tests for voice and data circuits, and BERT tests for data circuits.
19.1.2
Configuring System Cards

This section lists the configurable parameters and options for system cards.
Control card parameters and options

Table 19.1-1 lists the Control card configuration parameters.
Table 19.1-1: Control Card Configuration Parameters and Options
Parameter
Options
Card Level
Timing and synchronization
See Table 17.2-4.
Date, time, and node name
See Table 17.4-1.
Access level and password
See Table 17.5-1.
CPSS
See Table 17.6-2.
Control redundancy
See Table 18.1-2.
Slot Level
19.1-2
Card slot (3600+ MainStreet Control

card)
Narrowband Switching module

Broadband Switching module
Card slot (3600, 3645, 3664 and 36120

MainStreet Control cards)
8+ module
no module
Serial port
See Table 17.3-2.
(400)
System Cards

NNP 95-2035-01-00-B

Expander card parameters and options

Table 19.1-2 lists the Expander card configuration parameter.
Table 19.1-2: Expander Card Configuration Parameter and Options
Parameter
Options
Card slot
empty (not required)*

Expander card (6+2)
Expander card (6+6)
Expander card (8+8)
Expander card (16+)
Switching card parameters and options

Table 19.1-3 lists the Switching card configuration parameters. Each parameter has
a list of options with any default option marked by an asterisk.
Table 19.1-3: Switching Card Configuration Parameters and Options
Parameter
Options
Card slot
Switching card
Enabling or disabling the card
enabled*
disabled
Common Carrier card parameters and options

Table 19.1-4 lists the Common Carrier card configuration parameter.
Table 19.1-4: Common Carrier Card Configuration Parameter and Option
Parameter
Options
Card slot
Carrier card
Test card configuration parameters and options

Table 19.1-5 lists the Test card configuration parameters available for digital and
metallic connections. Each parameter has a list of options, with any default marked
by an asterisk.
Note
The 25-pair connector enable or disable option applies to digital and metallic access
through the card.
System Cards
(400)
19.1-3


NNP 95-2035-01-00-B
Table 19.1-6 lists the configuration parameters available for digital and analog test
connections through the user-installable Test module.
Table 19.1-5: Test Card Configuration Parameters and Options
Parameter
Options
Card Operation
Card slot
Test card
Digital DS0 Circuit Configuration

25-pair connector
enabled (faceplate connectors disabled)

disabled (faceplate connectors enabled)*
Interface speed
2.4 kb/s
4.8 kb/s
9.6 kb/s*
19.2 kb/s
56 kb/s
64 kb/s
Error correction
enabled*
disabled
Fault signalling code
a hexadecimal number: 00 to FF (1A*)
Metallic Test Access Connections

Metallic test access connections
direct monitor
high impedance monitor
split access
4-wire loopback
25-pair connector
enabled (faceplate connectors disabled)

disabled (faceplate connectors enabled)*
Table 19.1-6: Test Module Configuration Parameters and Options

Parameter
Options
Card Operation
Card modules
Test module
no module*
Tone Tester Configuration

Companding law
Mu-law*
A-law
Line impedance
600 W*
900 W
Transmission mode
2-wire*
4-wire
BERT Configuration
Rate adaption method
19.1-4
HCM*
Transparent
DDS
(400)
System Cards

NNP 95-2035-01-00-B

Parameter
Options
Transport position
B0 to B7*
Transport bandwidth
1 to 8*
Interface speed
see section 23.6.7
Signalling
enabled*
disabled
Data position
F0-B6* to F7-B0 (F0-B5*)
Tone Tester Maintenance

Tone type
single tone*
white noise
quiet tone
Analog tone test amplitude
40 to +10 dBm in 1 dBm D (0*)
Digital tone test amplitude
40 to 0 dBm* in 1 dBm D (0*)
Tone Frequency
200 to 3400 Hz in 1 Hz D (1004*)
Loopback
loopback C
Tone Tester test
enabled
disabled
Analog tone test direction
equipment*
facility
BERT Maintenance
System Cards
Inject ERR
inject an error
Inject ERR
none*
1.00E-1
1.00E-2
1.00E-3
1.00E-4
1.00E-5
1.00E-6
1.00E-7
Inject BER
n, where n is an integer corresponding to

a BERT pattern
BERT pattern
enabled
disabled
BER test
clear statistics
BERT statistics

a DDS control code
DDS control code
show status of last eight MJUs

show last eight Tx DDS codes
show last eight Rx DDS codes
DDS control code parameters
run a round trip delay measurement
Round trip delay measurement
enabled
disabled*
Audible error bell
loopback C
(400)
19.1-5


NNP 95-2035-01-00-B
GFC3 configuration parameters and options

Table 19.1-7 lists the card and maintenance level configuration parameters and
options for the GFC3. To configure maintenance level options, see Maintenance,
chapter 36.4.
Table 19.1-7: GFC3 Configuration Parameters and Options
Parameter
Options
Card Operation
Card slot
GFC
GFC type
GFC
GFC3
Companding law
Mu-law*
A-law
Ringback tone
Mu-law*
A-law
Tone generator companding law
Mu-law*
A-law
NRZ clock termination
enabled
disabled*
DS1/composite clock termination
enabled
disabled*
Order Wire Configuration

PCM companding law
Mu-law*
A-law
TLP
Tx: 3 to +4 dB in 1 dB D (0*)
Rx: 6 to +1 dB in 1 dB D (0*)
Signalling type
E1
Private Line Automatic Ringdown*
Central Battery Working
Loop Calling Disconnect Clear
Earth Calling
Remote Extension
T1
Private Line Automatic Ringdown*
Private Line Automatic Ringdown_D3
Loop Start
Loop Start to E&M Conversion
Ground Start
Ground Start to E&M Conversion
Ringing bias
48 V*
0V
Test Port Configuration

PCM companding law
19.1-6
Mu-law*
A-law
(400)
System Cards

NNP 95-2035-01-00-B

Parameter
Options
16.0 to +8.0 dB in 0.1 dB D (0*)
TLP
Tone Tester Configuration
PCM companding law
Mu-law*
A-law
Line impedance
600 W*
900 W
Transmission mode
2-wire*
4-wire
BERT Configuration
HCM*
Transparent
DDS DS0-A
Transport position
B0 to B7*
Transport bandwidth
1 to 8*
Interface speed
see section 23.6.7
Signalling
enabled*
disabled
Data position
F0-B6* to F7-B0 (F0-B5*)
Error correction for DDS rate adaption
disabled
enabled*
DS0 Port Configuration

Interface speed
2.4 kb/s
4.8 kb/s
9.6 kb/s*
19.2 kb/s
56 kb/s
64 kb/s
Error correction
enabled*
disabled
Fault signalling code
a hexadecimal number: 00 to FF (1A*)
Tone Tester Maintenance
System Cards
Tone type
single tone*
white tone
quiet tone
Analog tone test amplitude
40 to +10 dBm in 1 dBm D (0*)
Digital tone test amplitude
40 to 0 dBm in 1 dBm D (0*)
Tone Frequency
200 to 3400 Hz in 1 Hz D (1004*)
Loopback
loopback C
Tone Tester test
enabled
disabled
Analog tone test direction
equipment*
facility
(400)
19.1-7


NNP 95-2035-01-00-B
Parameter
Options
BERT Maintenance
Inject ERR
inject an error
Inject BER
none*
1.00E-1
1.00E-2
1.00E-3
1.00E-4
1.00E-5
1.00E-6
1.00E-7
BERT pattern

a BERT pattern
BER test
enable
disable
BERT statistics
clear statistics
DDS control code

a DDS control code
DDS control code parameters
show status of last eight MJUs

show last eight Tx DDS codes
show last eight Rx DDS codes
Round trip delay measurement
run a round trip delay measurement
Audible error bell
enable
disable*
Loopback
loopback C
Note
During installation, each Control card and Switching card must be assigned a
unique node number (see Installation, chapter 14.1).
19.1-8
(400)
System Cards

NNP 95-2035-01-00-B
19.2
19.2 Understanding GFC3 Card Operation

Understanding GFC3 Card

Operation
This chapter introduces the GFC3 card operation parameters and options.
19.2.1
GFC3 Card Operations

You can configure the following card parameters on the GFC3:
ringback tone companding law

RBT_MULAW for Mu-Law companding
RBT_ALAW for A-Law companding
tone generator companding law
TG_MULAW for Mu-Law companding
TG_ALAW for A-Law companding
NRZ clock termination
NRZTRM_OFF to disable NRZ clock termination
NRZTRM_ON to enable NRZ clock termination
DS1/Composite clock termination
DS1TRM_OFF to disable DS1/Composite clock termination
DS1TRM_ON to enable DS1/Composite clock termination
PCM companding law
SET_MULAW to set the companding law for all configurable parameters on
voice circuits to Mu-Law
SET_ALAW to set the companding law for all configurable parameters on

voice circuits to A-Law
System Cards
(400)
19.2-1
19.2 Understanding GFC3 Card Operation


NNP 95-2035-01-00-B
To configure GFC3 card operations

Log on to the locally controlled or peripheral shelf and enter:
CONFIG SLOT <GFC>
TYPE
OPTIONS
GFC
GFC3
SET_MULAW
SET_ALAW
RBT_MULAW*/
RBT_ALAW
TG_MULAW*/
TG_ALAW
NRZTRM_OFF*/ DS1TRM_OFF*/
NRZTRM_ON
DS1TRM_ON
SK000772
19.2-2
(400)
System Cards

NNP 95-2035-01-00-B
19.3
19.3 System Card Slots

System Card Slots

This chapter explains how to configure slots for the configurable system cards.
19.3.1
Understanding System Card Slots

The 3600 MainStreet series bandwidth managers have system cards with parameters
to configure at the slot level.
Note
To configure all slots programmed as EMPTY to the default configurations of the
cards installed in the shelf, press the CONFIG_ALL softkey and the <Esc>
simultaneously.
3600 MainStreet series bandwidth managers

You must configure a card slot for the Switching card and Common Carrier card
because they can be installed in any of the UCSs of the switching shelf or, peripheral
or locally controlled shelf. For the Switching card, you can also enable or disable the
card.
Although the Expander card is always installed in slot 10 of the locally controlled
shelf, you must configure the type of Expander card.
You do not need to configure the Control card slot, because it is always switching
shelf slot 10 or, peripheral or locally controlled shelf slot 9 (or slots 9 and 11 in
control-redundant single shelves). However, you can configure the SCC3(8+) to
provide single-shelf control redundancy with double-bandwidth switching
capacity.
You must configure the GFC slot for the type of General Facilities card installed (the
GFC3 provides more functionality than the GFC or GFC2). General Facilities cards
are installed in slot 12 of shelf A for peripheral or locally controlled shelves.
3600+ MainStreet Bandwidth Manager

There are three system cards with parameters to configure at the slot level: the
Control card, the Common Carrier card and the Test card.
System Cards
(400)
19.3-1


NNP 95-2035-01-00-B
The system automatically configures the slot location of the Control card on the
shelf, as well as the Timing card and the Alarm Panel. The Narrowband and
Broadband modules installed on the Control card must be manually configured as
present on the card. The Bank-B Memory module is automatically configured as
present on the Control card. The Test card can be configured in the MTA slot. See
section 19.3.8 for slot configuration information.
19.3.2
Configuring the SCC3(8+) Card Slot

You can configure a SCC3(8+), which provides the extra switching capacity needed
for full 8 UCS double bandwidth. The SCC3(8+) is used in a single-shelf
configuration to allow the installation of eight double-bandwidth cards and permit
single-shelf redundancy. (There is no room for an Expander card in a single-shelf
system with two Control cards.)
Configure the SCC3(8+) as:
8+_MODULE
NO_MODULE
To configure the SCC3(8+) card slot
CONFIG SLOT <CTL> OPTIONS
8+_MODULE
NO_MODULE
SK000059
Note
You must configure the Expander card as EMPTY before you can configure the
SCC3(8+).
If you have configured more than four shared CPSS connections, you must
disconnect them before configuring the SCC3(8+).
Before you select NO_MODULE, you must deconfigure slots 7 and 8 and any
double-bandwidth cards.
19.3-2
(400)
System Cards

NNP 95-2035-01-00-B
19.3.3

Configuring the Expander Card Slot

You can configure the Expander card with identifier <EXP> and the appropriate
card type. Table 19.3-1 lists various system configurations and the corresponding
Expander card types. Alternatively, you can select AS_PRESENT, to match the card
in the slot. (The AS_PRESENT softkey does not appear if the Expander card installed
in the slot matches the slot configuration.) The default configuration is EMPTY.
Table 19.3-1: Expander Card Configuration Options
System Configuration
Expander Card
Configure As
Single shelf
Not required
EMPTY*
Expanded single shelf
Expander card (6+2)
6+2
Dual shelf
Expander card (6+6)
6+6
Expanded dual shelf
Expander card (8+8)
8+8
Double bandwidth (single or dual shelf)
Expander card(16+)
16+
Warning
Configuring an Expander card while the system is in operation causes a temporary
disruption of service.
Note
The Expander card must be configured before a CONFIG_ALL operation. Otherwise
the system assumes only six slots will be configured.
To configure the Expander card slot

CONFIG SLOT <EXP>
EMPTY*
6+2
6+6
8+8
16+
SK000060
Note
If the Expander card slot is configured as anything other than EMPTY and you want
to change the slot configuration, all slots that will no longer be supported by the
Expander card must be configured to EMPTY. On the warning line, the system
displays the message Configure to EMPTY, followed by the identifiers of the slots
that need to be changed.
System Cards
(400)
19.3-3

19.3.4

NNP 95-2035-01-00-B
Configuring the Switching Card Slot

Configure the Switching card with type SC in any of slots 1 to 8 in the switching
shelf. You can also disable and enable the Switching card.
During a database restore, you must disable the Switching cards while the
peripheral shelves, DS-3 cards and E3 cards are restored. After the restore procedure
is completed, you can enable the Switching cards again. Configure the Switching
card by selecting:
ENABLE for enabled (default)

DISABLE for disabled
To configure the Switching card slot
CONFIG SLOT <n>
TYPE
SC
OPTIONS
ENABLE*/DISABLE
EMPTY*
SK000061
where n is a 1-digit slot number (1 through 8)
19.3.5
Configuring the Common Carrier Card Slot

Configure the Common Carrier card in any of slots 1 to 8 in the peripheral or locally
controlled shelf as type CARRIER. Alternatively, you can select AS_PRESENT, to
match the card in the slot.
To configure the Common Carrier card slot

CONFIG SLOT <sn>
CONFIG_ALL
TYPE
AS_PRESENT
MORE
CARRIER
SK000062
19.3-4
(400)
System Cards

NNP 95-2035-01-00-B
19.3.6

Configuring the Test Card Slot

Configure the Test card in any of slots 1 to 8 in the peripheral or locally controlled
shelf, or in the MTA slot in the enhanced locally controlled shelf, as type
TESTCARD. Alternatively, you can select AS_PRESENT, to match the card in the
slot.
If a Test module is installed on the Test card, select TESTMODULE to configure the
card slot for the Test module.
To configure the Test card slot

CONFIG SLOT <sn> or <MTA>
TYPE
AS_PRESENT
MORE
TESTCARD
SK001051
To configure the Test card for the Test module

CONFIG SLOT <sn> or <MTA> OPTIONS TESTMODULE/NO_MODULE*
19.3.7
Configuring 3600+ MainStreet Bandwidth Manager System

Card Slots
There are three system cards with parameters to configure at the slot level: the
Control card, the Common Carrier card (see section 19.3.5) and the Test card (see
section 19.3.6).
Configuring the Narrowband and Broadband Switching modules

Two modules can be configured on the Control card:
Narrowband Switching module

Broadband Switching module
Before configuring the Control card module parameters, the modules should be
physically installed. See Installation, Task 1305: Installing User-installable Card
Modules for information about installing modules.
The Narrowband Switching module is required on the Control card to enable the
system to communicate with the eight lower shelf UCS slots, or with HSA cards
installed in slots H1 and H2 on the lower shelf for narrowband communications.
System Cards
(400)
19.3-5


NNP 95-2035-01-00-B
The Broadband Switching module is required on the Control card to enable the
system to communicate with any HSA cards installed in slots H1, H2 or H3 on the
enhanced locally controlled shelf.
After the modules are physically installed, the Control card must be installed on the
shelf. If the system is configured for control redundancy, the Control cards are
installed in slots CTL-A and CTL-B. For more information about control redundancy
configurations, see chapter 18.1. For simplex system configurations, the card can be
installed in either CTL-A or CTL-B, but the preferred slot is CTL-A. For both system
configurations, the slot chosen for the Control card must be the mate to the slot
where the Timing card is installed.
Note
The Timing card must be installed before the Control card.
The system automatically acknowledges the Control card as present in the slot. In
the case of a control-redundant configuration, the first card to complete the start-up
diagnostic tests becomes the active Control card.
The system raises alarms if the Narrowband or Broadband Switching modules are
configured but not physically installed on the Control card. During this condition,
all cards that would have been available if the module was installed are held in reset
until the correct module is installed. For example, if the Narrowband Switching
module is configured but not installed, and the Broadband Switching module is also
not installed, the cards in slots H1, H2 and B1 to B8 are held in reset.
You cannot deconfigure the Narrowband or Broadband Switching modules while
cards are installed in the slots that the modules make available. The following error
message is displayed: Configure to EMPTY: <slot number>.
To configure Control card modules

CONFIG SLOT <CTL> OPTIONS
NBAND_MOD
NO_MODULE
BRAND_MOD
8k_X_8k_SW
NO_MODULE
4_X_4_SW
SK000838
19.3-6
(400)
System Cards

NNP 95-2035-01-00-B
19.3.8

Configuring the General Facilities Card Slot

Configure a GFC or GFC2 in slot 12 in the peripheral or locally controlled shelf as
type GFC. Configure a GFC3 in slot 12 in the peripheral or locally controlled shelf as
type GFC3. Alternatively, you can select AS_PRESENT, to match the card in the slot.
To configure the GFC or GFC2 slot

CONFIG SLOT <GFC> TYPE GFC
To configure the GFC3 slot

CONFIG SLOT <GFC> TYPE GFC3
System Cards
(400)
19.3-7

NNP 95-2035-01-00-B
20. Primary Rate Interface Cards

NNP 95-2035-01-00-B
20.1
20.1 Understanding PRI Card Configuration

Understanding PRI Card

Configuration
This chapter introduces the PRI cards. It provides a summary of the configuration
procedures in this part of the manual and indicates how they apply to each PRI card.
20.1.1
Understanding PRI Cards

MainStreet systems support PRI cards as follows:
Single T1, Dual T1 and Dual T1-2 cards (3600 MainStreet series bandwidth
managers)
Single E1, Dual E1 and Dual E1-2 cards (3600 MainStreet series bandwidth
managers)
Single and Dual Optical Extension cards (3600 MainStreet series bandwidth
managers)
MPA card (3600 MainStreet series bandwidth managers)
TTC2M card (3600 MainStreet series bandwidth managers)
X.21 and V.35 PRI cards (3600 MainStreet series bandwidth managers)
DS-3 and DS-3 II cards (3645 and 36120 MainStreet systems)
Single and Dual E3 cards (3645 and 36120 MainStreet systems)
T1 cards
T1 cards are used in peripheral and locally controlled shelves. They provide
24-channel DS1 digital link interfaces that conform to the relevant sections of AT&T
Channel Bank specifications Pub 43801 and Pub 62411 at 1.544 Mb/s. The Single T1
card provides one link; the Dual T1 and Dual T1-2 cards provide two. You can install
T1 cards in any UCS 1 to 8.
Warning
For shelves with a 6-UCS backplane (part numbers 90-0010-01, 90-0010-02 and
90-0010-08), the Dual T1-2 card must be installed in slots 1 to 6 only. Damage will
occur to the card if it is inserted in slot 7 or 8 (resource slots).
Primary Rate Interface Cards
(400)
20.1-1


NNP 95-2035-01-00-B
Note
In 3664 MainStreet systems, T1, Dual T1 and Dual T1-2 cards provide 12-channel
DS1 digital links.
E1 cards
E1 cards are used in peripheral and locally controlled shelves. They provide
32-channel 2.048 Mb/s DS1 digital link interfaces that conform to ITU-T G.703, G.704
and G.732 specifications at 2.048 Mb/s. The Single E1 card provides one link; the
Dual E1 and Dual E1-2 cards provide two. You can install E1 cards in any UCS 1 to 8.
Note
In 3664 MainStreet systems, E1, Dual E1 and Dual E1-2 cards provide 16-channel
DS1 digital links (or 15-channel links when configured for CAS framing).
The Dual E1-2 card can be used wherever a Dual E1 card is used; however, node
software sees the two cards as different types, so they cannot be directly
interchanged. The Dual E1-2 card provides the following additional features:
software downloading over the network, which minimizes card down time
local and remote G.821 statistics compliance
RAI configurable to meet ISDN requirements and detection of F2 and F5 states
enhanced maintenance and performance reports
Optical Extension Cards

Optical Extension cards can be installed in any enhanced locally controlled or
peripheral shelf UCS 1 to 8.
Optical Extension cards can extend transmission links beyond the range of any
device that uses current copper technology. The cards are equipped with either one
or two IOTUs, which convert electrical signals to optical signals. Each IOTU
supports up to 31 DSOs and provides a bidirectional bandwidth of 2.048 Mb/s over
a distance of up to 15 km (9 mi), using 1300nm single-mode fibre.
Although Optical Extension cards have a proprietary fibre optic interface, they are
configured using the same procedures to configure Dual E1 cards.
T1, E1 and Optical Extension card modules

Table 20.1-1 lists the modules supported by the T1, E1 and Optical Extension cards.
20.1-2
(400)

NNP 95-2035-01-00-B

Table 20.1-1: Modules Supported by the T1, E1 and Optical Extension Cards
T1 Card
E1 Card
Dual T1
Card
Dual T1-2
Card
Dual E1
Card
Dual E1-2
Card
Opt. Ext.
Cards
CSU
CSU2
CCM
DSX-1
TS24
E1 HDSL LIM
E1 LIM
Module
FT1
NTI
SAM
IHTU-C
IHTU-R
T1 LIM
TSM (1)
DRM (1)
VCM
VCM2 (2)
VCM3
IFM
Notes
1. Dual T1 cards in 3664 MainStreet systems do not support TSMs or DRMs.
2. When this document was published, the VCM2 was not available. Contact your Newbridge representative for information.
FT1 module
The FT1 module provides fractional T1 loopback support on the Dual T1-2 card. This
module generates and detects FT1 loopback activation and deactivation codes
according to Annex B ANSI T1.403. Once the code is generated, it is transmitted to
the remote end, where another FT1 module or an T1.403 compliant device detects it
and applies or removes the loopback.
Fractional T1 loopbacks are remotely initiated on individual or super-rate circuits
without taking down the entire T1 span and interrupting services. These loopbacks
allow the user to systematically test the link for faults at each successive node.
E1 HDSL LIMs and T1 IHTU modules
E1 HDSL LIMs and the T1 IHTU modules use HDSL technology to provide
repeaterless transport of service over two pairs of unconditioned copper loops.
(400)
20.1-3


NNP 95-2035-01-00-B
The IHTU-C (central/master) and IHTU-R (remote/slave) are both required to

provide HDSL transmission, which supports greater distances between midspan
repeaters in a CSA. The IHTU modules are used at both ends of a T1 HDSL link. The
IHTU-C is installed at the central-office end, and the IHTU-R is installed at the
subscriber end.
Caution
Damage to equipment may occur if T1 lines are connected to a card that has an IHTU
module installed. If you use IHTU modules in your system, you can clearly identify
those circuits using the name field on the NMTI. To name circuits, see section 17.1.3.
Two E1 HDSL LIMs are required to provide HDSL transmission. The E1 HDSL LIMs
are used at both ends of an E1 HDSL link to increase the distance between midspan
repeaters in an ETSI DLL.
To establish an E1 HDSL link, the E1 HDSL LIMs at each end of the E1 link must be
programmed to be either a master or slave; this is achieved by configuring the Dual
E1 card Transmit BNC Shield option. By default, the Dual E1 card Transmit BNC
Shield option is set to Earthed, which corresponds to the master mode on the E1
HDSL LIM. To program one of the E1 HDSL LIMs for slave mode, the Dual E1 card
Transmit BNC Shield option must be configured for Floating.
Warning 1
If the Dual E1 cards at each end of the link are programmed for the same Transmit
BNC Shield option (for example, master/master or slave/slave), the E1 HDSL LIMs
do not synchronize.
Warning 2
The Receive BNC Shield option must be configured for Earthed at all times.
Note
Once the E1 HDSL link is connected and the modules are programmed for either
master or slave mode, it takes from 40 to 120 seconds for the E1 HDSL interfaces to
synchronize. It also takes from 40 to 120 seconds for the T1 HDSL interfaces to
synchronize once the T1 HDSL link is connected.
MPA cards
The MPA card is used in peripheral and locally controlled shelves and has four
programmable ports. Each primary rate interface is software configurable to
transport data according to either RS-530-A, RS-449, X.21, X.21 ESI or V.35
specifications. Two alarm contacts on the primary rate interface indicate an
out-of-sync condition on the X.21 interface, making it X.21 ESI compatible. The
20.1-4
(400)

NNP 95-2035-01-00-B

MPA card interface can be configured as either DTE or DCE. The MPA card can
connect to a total of 60 DS0s for data transport. Each interface supports n 48, n 56
or n 64 kb/s channels (where n = 1 to 30). A supervisory channel, TS0, is required
for each port to carry signalling. Super-rate channels are supported, as well as CPSS
over TS0.
A cable connects the MPA card to the UDP, which provides the physical interface to
external devices. You can install the MPA card in any UCS 1 to 8.
TTC2M cards
TTC2M cards are used in peripheral and locally controlled shelves, providing a
channelized 2.048 Mb/s CMI interface to PBXs. The interface to the PBX conforms
with TTC Standard Vol. IV Part 1 JJ-20.11 and supports thirty 64 kb/s data or voice
channels. The interface also has a TS0 supervisory channel and an unused channel,
TS16. The channels can be cross-connected at the TTC2M card to a combination of
card and channel types, including: T1, E1, X.21, V.35, DSP, E&M, LGS PLAR, BRI,
64 kb/s Codirectional, and E3. Signalling for the connected circuit assumes the
TTC2M card signalling. You can install the TTC2M card in any UCS 1 to 8.
X.21 and V.35 PRI cards

X.21 and V.35 PRI cards are used in peripheral and locally controlled shelves. The
X.21 PRI card presents an X.21/V.11 interface and the V.35 PRI card a V.35 interface
at the customer premises that provides n x 64 kb/s, where n = 1 to 30, or 56 kb/s (for
Switched 56 service). You can install X.21 and V.35 PRI cards in any UCS 1 to 8.
DS-3 cards
DS-3 and DS-3 II cards are used in HSPSs. They provide 28 DS1 compatible channels;
each channel contains 24 DS0s for a total of 672 DS0s. The 28 DS1 channels are
bundled together into one DS3-compatible digital trunk interface that conforms to
AT&T Pub 54014, at 44.736 Mb/s. DS-3 II cards are used with Release 6 and newer
versions of 3600 MainStreet series bandwidth managers software. The slot is
configured automatically for the DS-3 or DS-3 II card.
E3 cards
E3 cards are used in HSPS2s. They provide 34.368 Mb/s E3 interfaces that provide
16 E1 DS1 channels; each channel contains 32 DS0s for a total of 512 DS0s. The SE3
card provides one link through coaxial connectors on the bulkhead. The DE3 card
provides two links.
Data interfaces
The 64 kb/s Codirectional card and the OCU-DP Channel Unit are data interfaces
that can perform some primary rate functions. See chapter 22.1 for a description of
data interfaces. See chapters 20.9, 20.10 and 20.12 for a description of the primary
rate functions of data interfaces.
(400)
20.1-5

20.1.2

NNP 95-2035-01-00-B
Configuring PRI Cards

Table 20.1-2 lists the T1 card configuration parameters. Each parameter has a list of
options, with any default option marked by an asterisk.
Note
Chapter 17.6 provides CPSS connection procedures for PRI cards.
Chapter 18.3 provides procedures for configuring PRI redundancy.
During installation, each DS-3 or DS-3 II and E3 card must be assigned a unique
node number (see Installation, Task 1415: Setting the Node Number for a Peripheral
Shelf or DS-3, DS-3 II, DE3 and SE3 Cards).
Table 20.1-2: T1 PRI Card Configuration Parameters and Options

Single
T1 Card
Dual
T1
Card
Dual
T1-2
Card
Parameter
Options
CPSS
See Table 17.6-2.
Card type
T1
Dual T1
Dual T1-2
Application module
no module
voice compression
TS24 signalling (for Dual T1 card)
DRM (for Dual T1-2 card)
FT1 module (for Dual T1-2 card)
ISDN
non-ISDN*
ISDN
CCM
conversion
no conversion*
SAM (1)
no module*
normal (installed, not used)
circuit order
timeslot order
Card Level
Slot Level
20.1-6
VCM
delta
delta G3 fax
transitional
transitional G3 fax
Timeslot 24 signalling (2)
timeslot 24 signalling
no timeslot 24 signalling
(400)

NNP 95-2035-01-00-B

Single
T1 Card
Dual
T1
Card
Dual
T1-2
Card
Parameter
Options
DS1 Framing
D4 framing format*
ESF
Line length with a DSX-1

module or T1 LIM
0 to 46 m (0 to 150 ft)*
46 to 137 m (150 to 450 ft)
137 to 200 m (450 to 655 ft)
Line length with a CSU

module
15 dB*
7.5 dB
0 dB
Zero code suppression
transparent
binary 8-zero suppression
jam bit 7*
Trunk conditioning
one-way
two-way*
Fault classes
red/frame off or on*

yellow/distant off or on*
failed off or on*
error off or on*
CSU loopback off or on*
Loopback detection
none*
through CPSS
through TS24 (3)
on fault (4)
24 DS0 super-rate circuit

protection(2)
TS24 signalling
Link availability monitoring
enabled
disabled*
Errored seconds
1 to 255 (* = 86)
Severely errored seconds
320/1544* (5)
101/487 (5)
10-3* (4)
10-4 (4)
10-5 (4)
5 x 10-5 (4)
10-6 (4)
10-7 (4)
PRI redundancy (6)
See Table 18.3-1.
Alarm Time
Declare
Clear
0.1 to 60 seconds
0.1 to 60 seconds
Circuit Level
(400)
20.1-7


NNP 95-2035-01-00-B
Single
T1 Card
Dual
T1
Card
Dual
T1-2
Card
Parameter
Options
Fault signalling
seized
idle*
OOS-A
OOS-B
OOS-C
None
Custom trunk conditioning,

ABCD bits
4-digit code, E&M (idle=0000*;

seized=1111*)
Custom trunk conditioning,

data
8-digit code, primary rate

(00000000 to 11111111*)
T1 signalling types
transparent*
clear channel
E&M
LGS LS
LGS GS
LGS PLAR
LGS PLAR D3
LGE LS
LGE GS
Terminate (7)
Robbed bit signalling
enabled*
disabled
Clear channels
NOSIG
RBS OFF
Inversion
inverted* (voice)
not inverted (data)
Super-rate formats
contiguous
non-contiguous
equidistant
Notes
1. The SAM is not required in switching shelf controlled systems.
2. These parameters do not apply to T1 cards in 3664 MainStreet systems.
3. This option does not apply to Single T1 cards.
4. These options apply only to Dual T1-2 cards.
5. These options apply only to Dual T1 cards.
6. This parameter applies only to Single T1 cards equipped with T1 LIMs or CSU modules.
7. This signalling type provides T1 termination for frame relay access to frame stream circuits (on FRS,
FRE and PE cards) and Rate Adapted circuits (on FRS cards only). See chapter 25.11 for more
information.
20.1-8
(400)

NNP 95-2035-01-00-B

Table 20.1-3 lists the E1 and Optical Extension card configuration parameters. Each
parameter has a list of options, with any default option marked by an asterisk.
Note
Optical Extension cards are configured using the same card configuration
parameters and options as the Dual E1 card.
Table 20.1-3: E1 PRI Card and Optical Extension Card

Configuration Parameters and Options
Single
E1 Card
Dual E1,
and
Opt. Ext.
Card
Dual E1-2
Card
Parameter
Options
CPSS
See Table 17.6-2.
Card type
E1
Dual E1
Dual E1-2
Application module
no module
voice compression
ISDN frame (for Dual E1)
ISDN
non-ISDN*
ISDN
RAI
on loss of frame alignment*

on BER enable
on BER disable
CCM
conversion
no conversion
SAM (1)
no module*
normal (installed, not used)
circuit order
timeslot order
Card Level
Slot Level
VCM
delta
delta G3 fax
transitional
transitional G3 fax
E1 Framing
CAS*
CCS
31 channels
X.21 NTU (for E1 card)
Trunk conditioning
one-way
two-way*
(400)
20.1-9


NNP 95-2035-01-00-B
Single
E1 Card
Dual E1,
and
Opt. Ext.
Card
Dual E1-2
Card
Fault classes

failed off or on*
error off or on*
Loopback detection
none*
through CPSS
on fault (for Dual E1-2 card)
Link monitoring
enable
disable*
Statistics type
CRC4
HDB3*
Nu bit
enabled
disabled*
Shield ground
Chassis (for Dual E1-2 card)

Signal*
Rx shield grounding*
Rx shield floating
Tx shield grounding*
Tx shield floating
Optical Extension cards:
For master operation set card to
Tx shield floating
For slave operation set card to
Tx shield grounding
For maintenance set card to
Rx sheild grounding
Severely errored
seconds
5 x 10-6
Parameter
Options
10-5
10-4
10-3*
Alarm Time
Declare
Clear
0.1 to 60 seconds
0.1 to 60 seconds
BER alarm option
enabled
disabled*
SA4 bit on
SA4 bit off*
CRC4 reframing
enabled
disabled*
E-bit
enabled
disabled*
PRI redundancy (2)
See Table 18.3-3.
Circuit Level
20.1-10
(400)

NNP 95-2035-01-00-B

Single
E1 Card
Dual E1,
and
Opt. Ext.
Card
Dual E1-2
Card
Parameter
Options
Fault signalling
seized
idle*
OOS-A
OOS-B
OOS-C
None
Custom trunk
conditioning, ABCD
bits
4-digit code, E&M (idle=0000*;

seized=1111*)
Custom trunk
conditioning, data

(00000000 to 11111111*)
E1 signalling types
transparent*
clear channel
E&M
continuous E&M
LGS RE
LGS EC
LGS PLAR
LGS PLAR D3
LGE RE
LGE EC
R2 signalling type
R2 digital signalling
T1 signalling types
transparent*
clear channel
E&M
LGS LS
LGS GS
LGS PLAR
LGS PLAR D3
LGE LS
LGE GS
Inversion
inverted* (voice)
not inverted (data)
Super-rate formats
contiguous
non-contiguous
equidistant
Notes
1. The SAM is not required in switching shelf controlled systems.
2. This parameter applies only to Single E1 cards equipped with E1 LIMs.
(400)
20.1-11


NNP 95-2035-01-00-B
Table 20.1-4: MPA Card Configuration Parameters and Options

Parameter
Options
Slot Level
Card type
MPA
Circuit Level
Alarm Time
Declare
Clear
20.1-12
0.1 to 60 seconds
0.1 to 60 seconds
Channel type
voice*
data
Control leads
(X.21, V.35, RS-449, RS-530-A)
forced on
forced off
Control lead conditioning OOS
on
off
none
Control lead initiated local loopback
enable
disable*
CPSS
disable*
8 kb/s
16 kb/s
Custom trunk conditioning, ABCD bits
4-digit code, E&M (idle=0000*; seized=1111*)
Custom trunk conditioning, data
8-digit code, primary rate (00000000 to 11111111*)
DGM Limit
1 to 60 (default = 5*)
Doppler buffer
enable
disable
E1 signalling types
transparent*
clear channel
E&M
LGS RE
LGS EC
LGS GS
LGS LS
LGS PLAR
LGE RE
LGE EC
LGE GS
LGE LS
Fault classes
frame off or on*

distant off or on*
failed off or on*
loopback off or on*
(400)

NNP 95-2035-01-00-B

Parameter
Options
Fault signalling
seized
idle*
OOS-A
OOS-B
OOS-C
None
Framing
HCM1
HCM2
HCM3*
HCM4
HCM5
Gender (clocking source)
DCE
DTE*
Interface type
RS-530-A*
RS-449/V.36
V.35
X.21
X.21 ESI
Inversion
inverted* (voice)
not inverted (data)
Loopback detection
none*
CPSS
In-band
Number of circuits
1 to 30 (48 to 1920 kb/s), default = 15*
R2 signalling type
R2 digital E+M
Slip buffer
10 to 39 frames (10*)
slip by 10 to 39 frames (10*)
SES Limit
1E-3*
1E-4
1E-5
1E-6
5E-5
SRM HCM data in TS0
unused bit positions to the right of framing bits in TS0
Super-rate formats (1)
contiguous
non-contiguous
equidistant
(400)
20.1-13


NNP 95-2035-01-00-B
Parameter
Options
Supervisory channel number of circuits

with signalling
0* to 29
Supervisory channel framing bit
any unused bit position (B7*)
T1 signalling types
transparent
clear channel
E&M
LGS LS
LGS GS
LGS PLAR
LGS PLAR D3
LGE LS
LGE GS
Transport bandwidth
48 kb/s
56 kb/s
64 kb/s*
Trunk conditioning
one-way
two-way*
Notes
1. The MPA card supports both one-way and broadcast unidirectional super-rate connections.
Table 20.1-5 lists TTC2M card configuration parameters. Each parameter has a list of
Table 20.1-5: TTC2M Card Configuration Parameters and Options
Parameter
Options
Slot Level
Card type
TTC2M
Alarm Time
Declare
Clear
0.1 to 60 seconds
0.1 to 60 seconds
Fault classes
frame off or on*

SAI off or on*
failed off or on*
error off or on*
Trunk conditioning
one-way
two-way*
Circuit Level
20.1-14
(400)

NNP 95-2035-01-00-B

Parameter
Options
Circuit inversion
none
ADI
even
magnitude inversion*
Companding conversion
none*
A law
Mu law
Fault signalling
in-use
idle*
NIS
none
Protection switching
protected by
protecting
Table 20.1-6 lists the X.21 and V.35 card configuration parameters. Each parameter
has a list of options, with any default option marked by an asterisk.
Table 20.1-6: X.21 and V.35 PRI Card Configuration Parameters and Options
Parameter
Options
Card Level
CPSS
See Table 17.6-2.
Slot Level
Card type
X.21 PRI 1
X.21 PRI 2
V.35 PRI
Framing (1)
1
2*
Trunk conditioning
one-way
two-way*
Fault classes
frame off or on*

distant off or on*
failed off or on*
Loopback detection
none*
through CPSS
Number of circuits
1 to 30* (64 to 1920 kb/s*)
Supervisory channel number of circuits

with signalling
0* to 29
Supervisory channel framing bit
B1, B3, B5, B7*
Clocking source
service provider (DCE)

the MainStreet node (DTE)*
Clock inversion (1)
invert*
normal
(400)
20.1-15


NNP 95-2035-01-00-B
Parameter
Options
Slip buffer
0.5 bits per 1 kb/s of bandwidth*

1.0 bits per 1 kb/s of bandwidth
PRI redundancy
See Table 18.3-1.
Circuit Level
Alarm Time
Declare
Clear
0.1 to 60 seconds
0.1 to 60 seconds
Fault signalling
seized
idle*
OOS-A
OOS-B
OOS-C
None
E1 signalling types
transparent*
clear channel
E&M
continuous E&M
LGS RE
LGS EC
LGS PLAR
LGE RE
LGE EC
R2 signalling type
T1 signalling types
transparent
clear channel
E&M
LGS LS
LGS GS
LGS PLAR
LGS PLAR D3
LGE LS
LGE GS
Inversion
inverted* (voice)
not inverted (data)
Super-rate formats
contiguous
non-contiguous
equidistant
(2)
Notes
1. These parameters apply only to X.21 PRI cards.
2. The X.21 and V.35 card variants that have 1 to 30 circuits available support both one-way and
broadcast unidirectional super-rate connections.
20.1-16
(400)

NNP 95-2035-01-00-B

Table 20.1-7 lists the DS-3 and DS-3 II card configuration parameters. Each
parameter has a list of options, with any default option marked by an asterisk.
Table 20.1-7: DS-3 and DS-3 II Card Configuration Parameters and Options
Parameter
Options
Card Level
See Table 17.2-4.
Node name
See Table 17.4-1.
See Table 17.5-1.
CPSS
See Table 17.6-2.
Control redundancy
See Table 18.1-2.
Slot Level
Serial ports
See Table 17.3-3.
See Table 18.1-7.
DS3 level
Line length
0 to 69 m (0 to 225 ft)*
69 to 137 m (225 to 450 ft)
DS3 Framing
transmit as received*
M13
C-bit parity
DS1 Level
DS1 Framing
D4 framing format*
ESF
transparent
jam bit 7*
Trunk conditioning
one-way
two-way*
Fault classes
red off or on*

yellow off or on*
failed off or on*
error off or on*
Circuit Level
(400)
20.1-17


NNP 95-2035-01-00-B
Parameter
Alarm Time
Declare
Clear
Options
0.1 to 60 seconds
0.1 to 60 seconds
Fault signalling
seized
idle*
OOS-A
OOS-B
OOS-C
none
T1 signalling types
transparent*
clear channel
E&M
LGS LS
LGS GS
LGS PLAR
LGS PLAR D3
LGE LS
LGE GS
Clear channels
NOSIG
RBS OFF
enabled*
disabled
Inversion
inverted* (voice)
not inverted (data)
Super-rate formats (1)
contiguous
non-contiguous
Notes
1. DS-3 II cards support both one-way and broadcast unidirectional super-rate connections.
Table 20.1-8 lists the E3 card configuration parameters. Each parameter has a list of
20.1-18
(400)

NNP 95-2035-01-00-B

Table 20.1-8: E3 Card Configuration Parameters and Options

Parameter
Options
Card Level
See Table 17.2-4.
Node name
See Table 17.4-1.
See Table 17.5-1.
CPSS
See Table 17.6-2.
Control redundancy
See Table 18.1-2.
Slot level
Card type
as present
empty
E3
Serial ports
See Table 17.3-2.
E3 Level
Alarm Time
Declare
Clear
0.1 to 60 seconds
0.1 to 60 seconds
Equalization
0 to 4 dB*
4 to 8 dB
8 to 10 dB
10 to 12 dB
NU bit
0
1*
See Table 18.1-8.
E2 Level
NU bit
0
1*
(400)
20.1-19


NNP 95-2035-01-00-B
Parameter
Options
E1 Level
E1 Framing
CAS*
CCS
31 channels
Trunk conditioning
one-way
two-way*
NU bit
0000 to 1111*
E1 link quality monitoring
CRC4 statistics
frame alignment signal statistics*
Circuit Level
20.1-20
Fault signalling
seized
idle*
OOS-A
OOS-B
OOS-C
none
E1 signalling types
transparent*
clear channel
E&M
continuous E&M
LGS RE
LGS EC
LGS PLAR
LGE RE
LGE EC
R2 signalling type
T1 signalling types
transparent
clear channel
E&M
LGS LS
LGS GS
LGS PLAR
LGS PLAR D3
LGE LS
LGE GS
Inversion
inverted* (voice)
not inverted (data)
Super-rate formats
contiguous
non-contiguous
equidistant
(400)

NNP 95-2035-01-00-B
20.2
20.2 PRI Card Slots

PRI Card Slots

This chapter explains how to configure card slots and slot options for the PRI cards.
20.2.1
PRI card type

application module type
unidirectional connections on 3645 MainStreet peripheral shelves
ISDN links
E3 cards
Understanding PRI Card Slots

You must configure a slot for each type of primary rate card slot, except the DS-3 or
DS-3 II card slot, which is automatically configured.
Configuring a slot type means programming a card slot to accept a specific card
type. When the slot type is configured, the circuits for that slot are configured with
default settings. After the slot type has been configured, you can configure or
cross-connect the circuits on the primary rate card.
20.2.2
Configuring T1, E1, Optical Extension, MPA, TTC2M, X.21

or V.35 Card Slots
cards installed in the shelf, press the CONFIG_ALL softkey and the <Esc> key
simultaneously.
Note
Select the DUAL_E1 softkey to indicate that a Single or Dual Optical Extension card
is installed.
Configure the type of application module installed on the card once you have
configured the card type for the slot. See Installation, chapter 13.38 for information
about user-installable application modules.
Table 20.2-1 lists PRI cards and the application modules they support.
(400)
20.2-1
20.2 PRI Card Slots


NNP 95-2035-01-00-B
Table 20.2-1: Application Modules Supported by PRI Cards

T1 Card
Dual T1
Card
Dual
T1-2
Card
E1 Card
Dual E1
Card
Dual
E1-2
Card
Optical
Ext.
Card
Application
Modules
CCM
DRM
IFM
FT1
SAM
TSM
VCM
You can also configure these options at the card slot level:
unidirectional connections for primary rate cards on 3645 MainStreet peripheral

shelves
ISDN for Dual T1-2, Dual E1, Dual E1-2 and Optical Extension card links
If you select ISDN for a Dual T1-2 card, the system automatically turns on B8ZS and
ESF, and turns off RBS for all circuits in the link. It also sets the signalling type to
NOSIG and sets inversion to DATA.
If you select ISDN for the Dual E1, Dual E1-2 or Optical Extension cards, the system
automatically reconfigures the link. Table 20.2-2 lists the reconfigured link options
with their default ISDN settings.
Table 20.2-2: ISDN Link Default Configuration
Link Option
Default Setting
Signalling type
CCS
Statistics
CRC4
CRC reframing
On
E-bits
On
LIM termination
Twisted pair
BNC shield grounding
Floating
Alarm declare/clear times
0.8 s
IFM
(1)
On
RAI
(2)
On resynchronization
On BER disable
Trunk conditioning (2)
Disabled
Notes
1. The ISDN framing module is only necessary on the Dual E1 and Optical Extension card.
2. Only for the Dual E1-2 card.
20.2-2
(400)

NNP 95-2035-01-00-B
20.2 PRI Card Slots

Note
The Dual E1 and Optical Extension cards require the IFM module to support ISDN
connectivity. The Dual E1-2 card provides ISDN functionality and does not require
the IFM module.
Each Dual E1 or Dual E1-2 card channel has the following options automatically
configured when ISDN is selected for the link.
NOSIG signalling type

channel type set to DATA
fault signalling set to NONE for B-channels, IDLE for D-channels
On the Dual E1-2 card, trunk conditioning is disabled automatically when ISDN is
selected. The Dual E1 card does not have the trunk conditioning automatically
turned off when ISDN is selected; however, this should be done manually. See
chapter 20.9 for more information.
The Dual E1 card can be configured for ITU G.706 compatible frame alignment when
equipped with an IFM. If you select IFM_ON for the Dual E1 card link, the statistics
type is set to CRC4 and the E bits and CRC reframing options are on.
Note
The ISDN option does not apply to 3664 MainStreet systems.
To configure PRI card slots

CONFIG SLOT <sn> TYPE
AS_PRESENT
E1
T1
DUAL_E1
PRIME_RATE
DUAL_T1
DUAL2_E1
X21_PRI_1
X21_PRI_2
DUAL2_T1 MORE
V35_PRI
MPA TTC2M
SK000063
Note
Use the AS_PRESENT softkey if the card is already installed in the slot.
(400)
20.2-3
20.2 PRI Card Slots


NNP 95-2035-01-00-B
To configure T1 and E1 card slot options

COMP_CONV/NO_CONV*
SAM
SK000064
To configure Dual T1, Dual E1, Dual E1-2 and Optical Extension card
slot options
CONFIG SLOT <sn> OPTIONS APP_MOD
VOICE_COMP
DELTA
DELTA_G3
NO_MODULE
TRANS
TS24_SIG or ISDN_FRAME
TRANS_G3
SK000065
Note
The TS24_SIG option applies only to the Dual T1 card. The ISDN_FRAME option
applies only to the Dual E1 card.
To configure Dual T1-2 card slot options

CONFIG SLOT <sn> OPTIONS APP_MOD
VOICE_COMP
DELTA
DELTA_G3
NO_MODULE
TRANS
TRANS_G3
DRM
FT1
TS24_SIG
SK000828
To configure ISDN and IFM link options for Dual E1 and Optical Extension cards
CONFIG SLOT <sn-l> OPTIONS MORE ISDN/NON_ISDN or
IFM_ON/IFM_OFF
To configure ISDN on Dual T1-2 and Dual E1-2 card links

CONFIG SLOT <sn-l> OPTIONS ISDN/NON_ISDN*
20.2-4
(400)

NNP 95-2035-01-00-B
20.2 PRI Card Slots

To configure Unidirectional cards

CONFIG SLOT <sn> or <sn-l> OPTIONS UNIDIRECT/NO_UNIDIR
20.2.3
Configuring E3 Card Slots

Slots are configured for the E3 cards on an individual E3, E2 and E1 basis, as EMPTY
or AS_PRESENT. You can configure an E2 as AS_PRESENT only if the associated E3
is configured AS_PRESENT. Similarly you can configure an E1 as AS_PRESENT
only if the associated E3 and E2 are configured AS_PRESENT.
On an E3 card, you can configure any unused E1, E2 or E3 (DE3 card only) as EMPTY
to prevent alarms from being raised. Configuring an E2 or E3 as EMPTY
automatically configures the embedded E1s and E2s as EMPTY.
You cannot configure an E1 as EMPTY if it is a source of synchronization. Similarly,
you cannot configure an E2 or E3 as EMPTY if one of the embedded E1s is a source
of synchronization. (See chapter 17.2 for a description of synchronization.)
To configure E3 card slots

CONFIG SLOT <E3id> or <E3id-E2id> or <E3id-E1id> TYPE
AS_PRESENT EMPTY
E3*
SK000066
(400)
20.2-5

NNP 95-2035-01-00-B
20.3
20.3 E1-to-T1 Conversion

E1-to-T1 Conversion
This chapter introduces E1-to-T1 conversion and explains how to do the following
tasks:
configure a CCM
configure a SAM in a 3600 MainStreet system
enable or disable companding conversion on the TTC2M card
20.3.1
Understanding E1-to-T1 Conversion

The following two E1-to-T1 conversion modules are available for T1-to-E1
conversion when T1 and E1 cards are used in a mixed T1 and E1 environment:
the CCM
the SAM (for the 3600 MainStreet system only)
Single E1 and T1 cards support either a CCM or a SAM but not both, because only
one module can be installed on a card. The TTC2M card performs companding
conversion without an application module.
When analog voice is digitized, the analog waveform is sampled. Each sample, or
pulse, is compared to a non-linear digital scale to obtain a corresponding digital
value. This technique, known as PCM, is used to transmit voice on both E1 and T1
digital links. The process of performing PCM is known as companding.
E1 and T1 companding differ in that each uses its own non-linear digital scale (or
companding law). Voice is digitized according to A-law for transmission on E1 links
and to Mu-law for transmission on T1 links.
The SAM is used to support super-rate T1-to-E1, T1-to-T1 and E1-to-E1
cross-connections. In a locally controlled system, you must configure a SAM to
support super-rate connections in:
Single T1 cards
Single E1 cards, if the super-rate circuit includes channels on either side of TS16
(timeslot 16)
(400)
20.3-1

20.3.2

NNP 95-2035-01-00-B
Configuring the CCM

When Single E1 and T1 cards are equipped with a CCM, you can configure them to
convert between A-law and Mu-law, so that E1 and T1 circuits can be
cross-connected with companding conversion occurring.
Note
When you are connecting circuits to a primary rate circuit that has been configured
with a CCM, the system prompts whether companding conversion should be
enabled on that circuit.
To enable or disable companding conversion on a T1 or E1 card

Configure companding conversion for the T1 or E1 card as:
COMP_CONV to configure the module

NO_CONV to deconfigure the module (default)
CONFIG SLOT <sn> OPTIONS COMP_CONV/NO_CONV*
Note
You cannot configure a slot with both a CCM and a SAM because only one module
can be installed on a card. If you configure a slot for a SAM, the COMP_CONV
softkey will not appear. To access the COMP_CONV softkey, you must select SAM
then NO_MODULE.
20.3.3
Configuring the SAM

For Single E1 and T1 cards in a locally controlled system, the SAM is used to support
super-rate T1-to-E1, T1-to-T1 and E1-to-E1 cross-connections. In a locally controlled
system, you must configure a SAM to support super-rate connections in:
Single T1 cards
Single E1 cards, if the super-rate circuit includes channels on either side of TS16
(timeslot 16)
Note
In a switching shelf controlled system, Single T1 and E1 cards do not need a SAM for
super-rate connections. Dual E1 and T1 cards never need a SAM for super-rate
connections.
20.3-2
(400)

NNP 95-2035-01-00-B

For the purposes of the SAM, circuits and timeslots are not synonymous.
A circuit is a device internal to the node. Single T1 and E1 cards are assigned
circuits 1 to 24 and 1 to 31, respectively.

A timeslot is a channel on the physical T1 or E1 link external to the node. T1 and
E1 links are made up of timeslots 1 to 24 and 1 to 31, respectively.
For T1 links only, circuit n always corresponds to timeslot n. For example,
timeslot 12 of a T1 link always corresponds to circuit 12 of the T1 card on which
it terminates.
For E1 links, circuit n does not always correspond to timeslot n. There is a direct
correspondence between circuit and timeslot for circuits 1 through 15. Circuits
above 15 correspond to the next highest timeslot relative to that circuit (for
example, circuit 16 corresponds to timeslot 17) with the exception of circuit 31.
When the framing type is configured as 31_Chan, circuit 31 becomes available for
use taking the place of the signalling channel S in timeslot 16 (see Table 20.3-1).
When two super-rate circuits (see chapter 20.15) are cross-connected, timeslots from
one link map onto timeslots on another. First the master circuits are cross-connected,
mapping their respective timeslots to one another. Then, each successive circuit in
one super-rate bundle is cross-connected to each successive circuit in the other
super-rate bundle, mapping their respective timeslots to one another.
Since super-rate bundles may include non-contiguous circuits and circuits do not
always correspond to timeslots in a one-to-one correspondence, delay equalization
problems can occur between respective timeslots of the two super-rate bundles that
are being connected. This delay equalization problem will prevent the super-rate
connection from functioning properly.
The SAM solves this problem by ensuring that, at cross-connect time, each circuit
that is part of a super-rate bundle has its respective timeslot mapped onto a timeslot
with equal delay.
There are three types of super-rate bundle configurations (see chapter 20.15). In the
case of contiguous super-rate bundles, delay problems are easily resolved prior to
connection time by following the recommended configuration guidelines contained
in this section. For the non-contiguous or equidistant super-rate bundles, delay
problems become subject to the particular circuit arrangement at cross-connect time
and may still exist after SAM configuration due to the numerous circuit arrangement
possibilities. In this case, it may be necessary to choose an alternate SAM
configuration or reconstruct the super-rate bundles with a different circuit ordering
to solve the delay problem.
(400)
20.3-3


NNP 95-2035-01-00-B
The following is a list of recommended SAM configurations. Configure the SAM as:
NO_MODULE if there is no SAM installed on the card (default)

NORM if a SAM is installed but not being used
CCT if the SAM is used to switch super-rate data from a T1 link to an E1 link in
circuit order (circuits 1 through 24 on a T1 link are switched to circuits 1 through

24 on an E1 link)
TS if the SAM is used to switch super-rate data from a T1 link to an E1 link in
timeslot order (circuits 1 through 24 on a T1 link are switched to timeslots 1
through 24 on an E1 link)
CONTIGUOUS if the SAM is used to switch super-rate data between two E1
links (circuits 1 through 30 on an E1 link are switched to circuits 1 through 30 on
another E1 link). Specifically, it should be used when at least one of the super-rate
bundles spans timeslot 16 and the super-rate bundles being connected are offset
by 2 or fewer circuits (notwithstanding note 3 of Table 20.3-1).
Circuits in a super-rate bundle follow the ordering outlined in Table 20.3-1. For
example, a 3 circuit contiguous super-rate bundle starting with circuit 15 on an E1
link configured for 31_Chan framing will contain, in order, circuits 15, 31 and 16.
Table 20.3-1: Super-rate Timeslot-to-Circuit Correlation
Switching Order of Circuits
Timeslot 1 2 3...15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31
Framing
Type
NORMAL SAM
(See chapter 20.15 for details.)
CCT SAM (1)
E1 Circuit 1 2 3...15 S 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 (2)
E1 Circuit 1 2 3...15 31 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30
(2)
T1 Circuit 1 2 3...15 16 17 18 19 20 21 22 23 24
CAS/CCS
31_CHAN (3)
D4/ESF
TS SAM (1)
E1 Circuit 1 2 3...15 S 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 (2)
CAS/CCS
E1 Circuit 1 2 3...15 31 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 (2)
31_CHAN (3)
T1 Circuit 1 2 3...15 16 17 18 19 20 21 22 23 24
D4/ESF
CONTIGUOUS
(4)
E1 Circuit 1 2 3...15 S 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30
CAS/CCS
E1 Circuit 1 2 3...15 31 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30
31_CHAN (3)
Notes
1. A maximum of 24 E1 circuits can be cross-connected to a T1.
2. If connecting the italicized E1 circuits to T1 links or the SAM is residing on the E1 card, the italicized
circuits can only be cross-connected on a circuit-by-circuit basis. (For example, they cannot be
connected as part of a super-rate bundle).
3. If 31_CHAN E1 framing is used, the CCT and CONTIGUOUS options will block certain super-rate
connections involving circuit 31. When the CCT option is selected, all connections involving a
super-rate bundle that includes circuit 31 will fail due to unavoidable delay problems. Similarly, when
the CONTIGUOUS option is selected, all connections involving a super-rate bundle that spans circuit
31 will fail due to unavoidable delay problems.
4. The CONTIGUOUS option is not available for SAMs on a T1 card.
20.3-4
(400)

NNP 95-2035-01-00-B

Note
A slot cannot be configured to have both a CCM and a SAM because only one
module can be installed on a card. If COMP_CONV is selected, the SAM softkey will
not appear. To access the SAM softkey, you must select NO_CONV.
To configure the SAM

CONFIG SLOT <sn> OPTIONS SAM
NO_MODULE*
NORM
TS
CCT
CONTIGUOUS
SK000067
20.3.4
Enabling or Disabling Companding Conversion on the

TTC2M Card
The TTC2M card provides companding conversion. Voice channels from the PBX
are converted to the digitized signal at the TTC2M card before being passed through
to any cross-connected T1 or E1 circuits.
To enable or disable companding conversion on the TTC2M card

CONFIG CIRCUIT <sn-cc> FUNCTION COMP_CONV
NONE*
A_LAW
MU_LAW
SK000744
(400)
20.3-5

NNP 95-2035-01-00-B
20.4
20.4 Voice Compression

Voice Compression
This chapter introduces voice compression on Dual T1, Dual T1-2, Dual E1,
Dual E1-2 and Optical Extension cards and explains how to:
configure voice compression algorithms and subframes

view connections
20.4.1
Understanding Voice Compression

The Dual T1, Dual T1-2, Dual E1, Dual E1-2 and Optical Extension cards support two
types of ADPCM voice compression.
Delta signalling carries signalling and voice information in separate channels.

Transitional signalling carries signalling and voice in the same bandwidth.
M44 (for T1 environments) and M55 (for E1 environments) are delta voice
compression algorithms that provide up to 44 or 55 full-duplex channels of 32 kb/s
ADPCM compressed voice information.
M48 (for T1) and M60 (for E1) are voice compression and signalling algorithms that
compress 64 kb/s channels into 32 kb/s ADPCM. With M48 transitional signalling,
48 DS0s can be compressed and carried on a single T1 link. With M60, a maximum
of 60 DS0s can be compressed and carried on a single E1 link. Figure 20.4-1 shows an
example of M48 transitional signalling using a Dual T1-2 card installed with a
VCM2. Figure 20.4-2 shows an example of M60 transitional signalling using a
Dual E1 card installed with a VCM3.
Figure 20.4-1: M48 Transitional Signalling
MainStreet node
24 DS-0s
24 DS-0s
Network
Dual T1-2
with
VCM2
Forty-eight 32 kb/s
ADPCM compressed
channels
5190
Note
At the time of publication, the VCM2 was not supported on the 3600 MainStreet
series bandwidth managers. Contact your local Newbridge representative for
information about availability.
(400)
20.4-1


NNP 95-2035-01-00-B
Figure 20.4-2: M60 Transitional Signalling
MainStreet node
30 DS-0s
30 DS-0s
Network
Dual E1
with
VCM3
Sixty 32 kb/s
ADPCM compressed
channels
5191
The type of VCM needed to do voice compression depends on the type of card and
the type of signalling. Table 20.4-1 lists VCM requirements. All VCMs can compress
either voice or G3 fax voice-band signals. Figures 20.4-3 and 20.4-4 show delta and
transitional signalling through compressors, subframes and sub-channels for a
Dual T1-2 card with an installed VCM.
Table 20.4-1: VCM Requirements
Card Type
Dual T1 card
For Delta Voice

Compression
For Transitional Voice

Compression
VCM or VCM3
VCM3
VCM2
VCM2
VCM or VCM3
VCM3
VCM2
VCM2
VCM or VCM3
VCM3
Dual T1-2 card

Dual E1 card
Dual E1-2 card
Optical Extension Card
20.4-2
(400)

NNP 95-2035-01-00-B

Figure 20.4-3: Delta (M44/M55) ADPCM Subframe

64k PCM
ADPCM
64k PCM
Site 1
PBX
DET
Dual Card
T1-2
Card
with
with
VCM Module
module
Site 2
Primary
Rate
Rate Card
card
Primary
Rate card
Dual T1-2
card with
VCM module
PBX
VCM Module
(Transcoder Device)
Primary
Rate
Circuit n
Primary
Rate
Circuit n1
Primary
Rate
Circuit n2
Primary
Rate
Circuit n3
Primary
Rate
Circuit n4
Primary
Rate
Circuit n5
Delta
Dual T1-2 Circuit
S1
Dual T1-2 Circuit
S2
Dual T1-2 Circuit
S3
Dual T1-2 Circuit
S4
Dual T1-2 Circuit
S5
Dual T1-2 Circuit
S6
Dual T1-2 Circuit
S7
Dual T1-2 Circuit
S8
Dual T1-2 Circuit
S9
Dual T1-2 Circuit
S10
Dual T1-2 Circuit
S11
M44 ADPCM
Sub-frame
DX connection
Primary Rate line
6638
A compressor is a logical circuit on the VCM that compresses a 64 kb/s DS0 to a

32 kb/s channel. A DS0 that carries the compressed voice channels from the
compressor to the far-end connection is called a subframe. The subframe is created
by connecting a DS0 to a compressor. The DS0 carrying the subframe cannot be
configured on the same card that performs the compression. The individual
compressed channels are called sub-channels.
A delta subframe is composed of up to eleven 32 kb/s compressed voice channels
and one 32 kb/s signalling channel, and occupies up to six contiguous DS0s. A
transitional signalling subframe is composed of two 32 kb/s compressed voice
channels, and occupies one DS0.
The M44 or M55 delta signalling provides Dual T1, Dual T1-2, Dual E1, Dual E1-2
and Optical Extension cards with access to 5 compressors. Each delta signalling
compressor can compress 11 DS0s.
(400)
20.4-3


NNP 95-2035-01-00-B
The M48 or M60 transitional signalling provides Dual T1, Dual T1-2, Dual E1, Dual
E1-2 and Optical Extension cards with access to 32 compressors. Each transitional
signalling compressor can compress 2 DS0s.
The compressed voice channels can be carried on any 64 kb/s codirectional circuit.
They are supported by: T1, Dual T1, Dual T1-2, E1, Dual E1, Dual E1-2, Optical
Extension, MPA, X.21 PRI, V.35 PRI, DS-3, DE3 and SE3 cards. M48 and M60
compressed channels can be connected to an SRS but M44 and M55 channels cannot.
Figure 20.4-4: Transitional (M48/M60) ADPCM Subframe
64k PCM
ADPCM
64k PCM
Site 2
Site 1
PBX
DET
Dual Card
T1-2
card
with
with
VCM Module
module
Primary
Rate
Rate Card
card
Primary
Rate card
Dual T1-2
card with
VCM module
PBX
VCM module
(Transcoder Device)
Dual T1-2 circuit
S1
Dual T1-2 circuit
S2
Primary
Rate
Circuit n
DX connection
M48 ADPCM
Sub-frame
Primary Rate line
6639
20.4.2
Viewing Compressor Connections

This section describes how to view compressor and sub-channel connections on
Dual T1, Dual T1-2, Dual E1, Dual E1-2 and Optical Extension cards.
To view compressor connections

CONFIG CONNECT <x-sn-Xt> SHOW_GROUP
where
X indicates compressor
t is 1 to 5 for delta voice compression or 1 to 32 for transitional signalling
20.4-4
(400)

NNP 95-2035-01-00-B

Figure 20.4-5 shows the compressor connections of a Dual T1 card configured for
transitional signalling. Displays for the Dual T1-2, Dual E1, Dual E1-2 and Optical
Extension cards are similar to the Dual T1 display.
Figure 20.4-5: Viewing Compressor Connections
3600 MainStreet
Circuit
1117-H1-00
Name
Toronto:A
Alarms:1
Status
DT1_Compressor
DT1_Compressor
DT1_Compressor
DT1_Compressor
DT1_Compressor
Connected
Configured
Configured
Configured
Configured
A1-X1
A1-X2
A1-X3
A1-X4
A1-X5
Type
11-May-1997
8:35a
CONFIG CIRCUIT 1-X1
1-SHOW_CCT
6-
2-NAME
7-
38-CANCEL
49-QUIT
50-
To view sub-channel connections

CONFIG CONNECT <x-sn-Scc-vv>
where
x-sn-Scc-vv is the compressed voice circuit you specified in creating the subframe
vv is 1 to 11 (for delta signalling) or 1 or 2 (for transitional signalling) to identify the sub-channel
Figure 20.4-6 shows the sub-channel connections of a Dual T1 card with a DS0
connected to a compressor. Displays for Dual T1-2, Dual E1, Dual E1-2 and Optical
Extension cards are similar to the Dual T1 display.
(400)
20.4-5


NNP 95-2035-01-00-B
Figure 20.4-6: Viewing Sub-channel Connections

3600 MainStreet
Circuit
Name
A1-S1-11
A1-S1-10
A1-S1-09
A1-S1-08
A1-S1-07
A1-S1-06
A1-S1-05
A1-S1-04
A1-S1-03
A1-S1-02
A1-S1-01
A1-S01-02
A1-S01-01
1117-H1-00
Toronto:A
Alarms:1
Type
Status
T1_SUBCHAN
T1_SUBCHAN
T1_SUBCHAN
T1_SUBCHAN
T1_SUBCHAN
T1_SUBCHAN
T1_SUBCHAN
T1_SUBCHAN
T1_SUBCHAN
T1_SUBCHAN
T1_SUBCHAN
T1_SUBCHAN
T1_SUBCHAN
Connected
Connected
Connected
Connected
Configured
Configured
Configured
Configured
Configured
Configured
Configured
Configured
Configured
11-May-1997
8:35a
CONFIG CIRCUIT 1-S1-1
1-SHOW_CCT
6-
20.4.3
2-NAME
7-
38-CANCEL
49-QUIT
50-
Configuring Voice Compression

There are four configuration steps to perform to configure voice compression and to
connect a voice compression channel on Dual T1, Dual T1-2, Dual E1, Dual E1-2 or
Optical Extension cards.
Voice compression general configuration procedure
1.
For transitional signalling, configure the DS0 that carries the compressed
channel with default data equal to all zeroes (eight 0s). See the procedure To
configure the DS0 that carries the compressed channels.
2.
Configure the Dual T1, Dual T1-2, Dual E1, Dual E1-2 or Optical Extension card
for delta or transitional signalling (either voice or G3 Fax voice band). This step
defines the voice compression algorithm and enables the compressors. See the
procedure To set the compressor type as delta or transitional signalling.
3.
Connect a subframe from the Dual T1, Dual T1-2, Dual E1, Dual E1-2 or Optical
Extension card compressor to a DS0 on the card that will carry the compressed
channels. See the procedure To connect the subframe to a DS0.
4.
Connect a voice channel from the Dual T1, Dual T1-2, Dual E1, Dual E1-2 or
Optical Extension card to a sub-channel on the VCM. See the procedure To
connect a voice channel to the VCM sub-channel.
Table 20.4-2 lists and describes the restrictions on transitional signalling

connections.
20.4-6
(400)

NNP 95-2035-01-00-B

Table 20.4-2: Restrictions on Transitional Signalling Connections

Restriction
Type
Description
Circuit
Protection
Circuit protection is not available for compressed channels.
Companding
Law
DS0s connected to Dual T1 compressors are treated as Mu-law.

DS0s connected to Dual E1 or Optical Extension compressors are treated as
A-law.
Companding conversion is not supported for compressed channels.
Connection
Compressors and subframes must be on different cards.

All sub-channels must be connected to circuits on the same dual card.
Robbed Bit
Signalling
RBS is automatically disabled when the subframe is created.

RBS must be disabled on all DS0s as it transits the network on M48/M60
compressed channels.
SRS
Only M48/M60 compressed channels can be connected to an SRS.

The SRS must be configured for transparent rate adaption.
Sub-channel 1 connects to bit positions B3 through B0.
Sub-channel 2 connects to bit positions B7 through B4.
Zero Code
Suppression
(T1)
Subframes configured for JB7 may experience minor delays in signalling

propagation.
To configure the DS0 that carries the compressed channels

CONFIG CIRCUIT <sn-cc> FAULT_SIG MORE CUSTOM DATA
<00000000>
To set the compressor type as delta or transitional signalling

CONFIG SLOT <sn> OPTIONS APP_MOD VOICE_COMP
DELTA
DELTA_G3
TRANS
TRANS_G3
SK000068
Note
When configured for TRANS_G3, only the compressed channels use G3 Fax voice
band lookup tables. Uncompressed circuits are not affected. When a Dual T1-2,
Dual E1, Dual E1-2 or Optical Extension card is configured for transitional
signalling, only the circuits connected to a sub-channel are compressed.
(400)
20.4-7


NNP 95-2035-01-00-B
To connect the subframe to a DS0

CONFIG CONNECT <x-sn-Xt> TO_CIRCUIT <x-sn-cc> or <x-sn-l-cc> or
<E3id-E1id-cc> or <x-sn-SRS-dd>
where
x indicates the peripheral shelf (whereas X indicates voice compression)
sn indicates the slot number
t indicates the subframe number, which can be 1 to 5 for delta voice compression or 1 to 32 for transitional
voice compression
x-sn-cc is the DS0 that will carry the subframe on an X.21/V.35 PRI, DS-3, MPA, T1 or E1 card; cc is 1 to
24 for DS-3 and T1 cards, 1 to 30 for X.21/V.35 PRI cards and 1 to 30 (CAS framing) or 31 (CCS or
31-channel framing) for E1 cards
x-sn-l-cc is the DS0 that will carry the subframe on a Dual T1, Dual E1 or Optical Extension card; cc is 1 to
24 for Dual T1 cards and 1 to 30 (CAS framing) or 31 (CCS or 31-channel framing) for Dual E1 and Optical
Extension cards
E3id-E1id-cc is the DS0 that will carry the subframe on an E3 card; cc is 1 to 30 (CAS framing) or 31 (CCS
or 31-channel framing)
x-sn-SRS-dd identifies the DS0 port for M48 or M60 connections to an SRS; dd is 1 to 30 for
single-bandwidth systems and 1 to 48 for double-bandwidth systems
Note
The circuit to which you are connecting (x-sn-cc, x-sn-l-cc, E3id-E1id-cc or
x-sn-SRS-dd) must not be on the same card as the compressor (x-sn-Xt).
To connect a voice channel to the VCM

To connect a voice channel to the VCM, enter:
CONFIG CONNECT <x-sn-l-cc> TO_CIRCUIT <x-sn-St-vv>
where
x-sn-l-cc is an uncompressed DS0 on the Dual T1, Dual E1 or Optical Extension card (for the card on which
the VCM resides)
x-sn-St-vv is the compressed voice circuit. The t indicates the subframe number, which can be 1 to 5 for
delta voice compression or 1 to 32 for transitional voice compression; vv indicates the sub-channel and
can be 1 to 11 (for delta signalling), or 1 or 2 (for transitional signalling)
For Release 6 and newer versions of system software, the sn-St in <x-sn-St-vv>
refers to the slot and compressor number of the card on which the VCM resides. For
Release 5.x, these variables refer to the slot and timeslot of the card to which the
compressor connects.
For example, assume the node in Figure 20.4-7 is a 3600 MainStreet node with a
Dual T1 card configured for transitional ADPCM in slot 2, a T1 card in slot 5 and the
subframe connection <A2-X7> TO_CIRCUIT <A5-2>. The softkey sequence for the
Link A subframe connections is as follows.
For Release 6 and newer versions of system software:
CONFIG CONNECT <A2-A-5> TO_CIRCUIT <A2-S7-1>
20.4-8
(400)

NNP 95-2035-01-00-B

For Release 5.x:

CONFIG CONNECT <A2-A-5> TO_CIRCUIT <A5-S2-1>
Figure 20.4-7: Connecting a Compressed Channel
MainStreet node
Uncompressed
voice circuit on link A
Dual T1
card
4 5 6
T1 card
VCM3
24 voice circuits
Network
24 voice circuits
1
2
3
24
voice
circuits
Network
14 15 16
Sub-frame
Compressor
Uncompressed
voice circuit on link B
Uncompressed voice circuits:

Timeslot 5 link A (DT1)
Sub-frame
Timeslot 15 link B (DT1)
Compressor:
7 (of 32)
Sub-frame:
Compressor 7 (DT1) to timeslot 2 (T1)
Sub-channels:
S2 carrying compressed timeslot 5 link A (DT1)
S1 carrying compressed timeslot 15 link B (DT1)
S2 (5)
S1 (15)
Sub-channels
5192
(400)
20.4-9

NNP 95-2035-01-00-B
20.5
20.5 Timeslot 24 Signalling

Timeslot 24 Signalling
This chapter explains how to configure timeslot 24 signalling on Dual T1 and Dual
T1-2 cards.
20.5.1
Understanding Timeslot 24 Signalling on Dual T1 and Dual

T1-2 Cards
Typical T1 connections use RBS to carry ABCD signalling. When RBS is enabled, the
least significant bit (bit 8) of every channel in frames 6 and 12 (if D4 framing is used),
or in frames 6, 12, 18 and 24 (if ESF framing is used), is overwritten with signalling
information. (Chapter 20.12 describes signalling, including RBS.)
For some applications (such as voice), the loss of these bits is undetectable. These
applications can use the full 64 kb/s of each DS0 and still use ABCD signalling.
Other applications (such as data) cannot tolerate the loss of these bits. These
applications can use only 56 kb/s of each DS0 if signalling is required. They can use
the full 64 kb/s only if signalling is disabled.
Timeslot 24 signalling provides both 64 kb/s clear channels and ABCD signalling
suitable for all applications by carrying signalling for all DS0s in a dedicated
common channel. Signalling for timeslots 1 to 23 is carried in timeslot 24 (see
Figure 20.5-1) using a form of common channel signalling called SIG24 (based on the
AT&T M44 delta channel format).
Figure 20.5-1: TSM Timeslot Assignment
T1 link
23 24
Reserved for
signalling of
circuits 1 to 23
4694
SIG24 is compatible with both ESF and D4 framing and introduces no signalling
distortion. SIG24 can pass regular voice signalling (such as off-hook and ringing),
OOS codes and any of the signalling types that can be configured for timeslots
1 to 23 (see chapter 20.11). Both standard-rate (64 kb/s) and super-rate circuits are
supported.
To support timeslot 24 signalling, the Dual T1-2 card must be equipped with a DRM
and the Dual T1 card with a TSM. As timeslot 24 signalling is a link option for the
Dual T1-2, each link can be independently configured to support timeslot 24
signalling or RBS. Timeslot 24 signalling is a slot-level option for Dual T1 cards.
(400)
20.5-1
20.5 Timeslot 24 Signalling


NNP 95-2035-01-00-B
Note
A Dual T1-2 card can be equipped with either a DRM or a VCM. A Dual T1 card can
be equipped with either a TSM or a VCM. Dual T1 cards in 3664 MainStreet systems
do not support TSMs, DRMs or timeslot 24 signalling.
20.5.2
Configuring Timeslot 24 Signalling on Dual T1 and Dual

T1-2 Cards
To configure a Dual T1 card for timeslot 24 signalling, you select the APP_MOD and
TS24_SIG softkeys. To configure the Dual T1-2 card for the parameter, you must
configure the card for a DRM, and then select the SIG_MODE and SIG24 softkeys for
each link.
Caution
T1 links using RBS and E1 links using CAS can be cross-connected to a Dual T1 with
a TSM. However, if SIG24 is enabled on a link, both ends of the link must terminate
on a Dual T1 card with a TSM.
To configure the DRM for a Dual T1-2 card

CONFIG SLOT <sn> OPTIONS APP_MOD DRM TS24_SIG
To configure a Dual T1-2 link for timeslot 24 signalling

CONFIG SLOT <sn-l> OPTIONS PHYSICAL SIG_MODE SIG24
To configure a Dual T1 card for timeslot 24 signalling

CONFIG SLOT <sn> OPTIONS APP_MOD TS24_SIG
20.5-2
(400)

NNP 95-2035-01-00-B
20.6
20.6 Framing
Framing
This chapter explains how to configure framing for PRI cards.
20.6.1
Understanding Framing for PRI Cards

Framing can be configured for:
T1, Dual T1, Dual T1-2 and DS-3 or DS-3 II cards

E1, Dual E1, Dual E1-2 and E3 cards
X.21 PRI-2 cards
MPA card
Optical Extension cards
For information on MPA card framing, see section 20.20.6.
20.6.2
Configuring Framing for T1 and DS-3 or DS-3 II Cards

You can configure one of five framing options for a T1 or a DS-3 or DS-3 II card.
Table 20.6-1 lists the framing options. Default options are marked with an asterisk.
Table 20.6-1: T1 and DS-3 Card Framing Options
T1
card
DS-3
card
Level
Framing
Option
DS3
Transmit as received
AUTO*
DS3
M13
M13
DS3
C-bit parity
C_BIT
DS1
D4
D4_FRAMING*
DS1
ESF
ESF
Transmit as received (AUTO) framing

In this mode, the DS-3 or DS-3 II card detects the format used by the node at the far
end and transmits in that format. If both ends of the link are configured in this mode,
the framing defaults to M13 format.
(400)
20.6-1
20.6 Framing

NNP 95-2035-01-00-B
M13 framing
This format is the established standard for public networks. The M13 process first
combines four DS1 lines into a DS2 bit stream at 6.312 Mb/s and adds 150 kb/s of
overhead for bit stuffing to accommodate variations in the clock rates of incoming
T1 links. Then, seven DS2 streams are combined into one DS3, with extra bits added
to bring the DS3 rate to 44.736 Mb/s.
C-bit parity framing

This format is a newer format, similar to M13, in which some of the bits are redefined
and used to carry C-bit parity information for error checking.
D4 framing
A D4 frame consists of 193 bits: 24 timeslots containing 8 bits each and one framing
bit. A D4 superframe consists of 12 frames. Figure 20.6-1 shows the D4 superframe
format.
Figure 20.6-1: D4 Framing Format
D4 Superframe
12 D4 frames
10
11
12
2316 bits
12 Framing bits
Framing pattern =
100011011100
Frame 1
Framing bit
Timeslot 1
Timeslot 2
Timeslot 24
8 bits
193 bits
D4 Format
8137
ESF framing
This framing format creates superframes consisting of 24 D4 frames. Figure 20.6-2
shows the ESF format.
20.6-2
(400)

NNP 95-2035-01-00-B
20.6 Framing
Figure 20.6-2: ESF Framing Format
Extended Super Frame

1
24 D4 frames
21
22
23
24
4632 Bits
24 bits: 6 framing (2 kb/s)
6 error checking (2 kb/s)
12 FDL (4 kb/s)
7174
Note
In 3664 MainStreet systems, connections to D4- and ESF-framed T1 cards are
restricted to the first 12 channels.
To configure the DS-3 framing format for DS-3 or DS3 II cards

CONFIG SLOT <DS3> OPTIONS TX_MODE
C_BIT
M13
AUTO*
SK000069
To configure the DS-1 framing format for T1, Dual T1 and DS-3 or DS-3 II cards
CONFIG SLOT <n> or <sn> or <sn-l> OPTIONS ESF/D4_FRAMING*
To configure the DS-1 framing format for Dual T1-2 cards

CONFIG SLOT <sn-l> OPTIONS PHYSICAL ESF/D4_FRAMING*
20.6.3
Configuring Framing for E1, E3 and Optical Extension

Cards
You can configure one of four framing options for an E1 or E3 card. Table 20.6-2 lists
the framing options.
(400)
20.6-3
20.6 Framing

NNP 95-2035-01-00-B
Note
When making super-rate connections (connections that occupy more than one
channel on a primary rate link) to an E1 link, timeslot 16 (circuit 31) is not used if
CAS or CCS is selected. Timeslots 1 through 15, then 17 through 31 are used (see
Table 20.3-1 in chapter 20.3). Timeslot 16 is used only if 31_CHAN is selected.
The framing type cannot be changed if any circuit on the card is connected.
Dual E1, Dual E1-2 and Optical Extension cards do not support the X.21 NTU
framing pattern.
Table 20.6-2: E1 and E3 Card Framing Options

E1 Card
Dual
E1,
Dual
E1-2
Cards
E3 Card
Optical
Ext.
Cards
CAS
CCS
Framing
31 channels
X.21 NTU
Option
CAS*
CCS
(1)
31_CHAN
X21_NTU
Notes
1. The 31 channel framing option is not available on E1 cards in 3664 MainStreet systems.
Table 20.6-3 shows the timeslot-to-circuit designation for these framing options. A
circuit is a device internal to the node. E1 cards are assigned circuits 1 to 31. A
timeslot is a channel on the physical E1 link external to the node. E1 links are made
up of timeslots 0 to 31, respectively.
Note
In 3664 MainStreet systems, connections to CCS- and X.21 NTU-framed E1 cards are
restricted to the first 15 channels and channel 31 (timeslot 16). Connections to
CAS-framed E1 cards are restricted to the first 15 channels.
20.6-4
(400)

NNP 95-2035-01-00-B
20.6 Framing
Table 20.6-3: Timeslot-to-Circuit Designation for E1 and E3 Cards

Switching Order of Circuits (1)
Frame Type
CAS
Timeslot
Circuit
0 1 2 3... 15 16 17... 29 30 31
F 1 2 3... 15 S 16... 28 29 30
CCS
31 Channels
X.21_NTU
Timeslot
Circuit
0 1 2 3... 15 16 17... 29 30 31
F 1 2 3... 15 31 16... 28 29 30
Notes
1. F = framing; S = signalling
Common channel signalling, 31 channels and X.21 network termination unit provide
31 configurable circuits, but they treat circuit 31 differently.
CAS framing
Timeslot 16 is used for CAS and is not user-configurable. Timeslot 0 is used for
framing. The rest of the timeslots are used for information. Timeslots 1 through 15
correspond to circuits 1 through 15 and timeslots 17 through 31 correspond to
circuits 16 through 30.
CCS framing
Timeslot 16 corresponds to circuit 31, which can be configured as an additional
64 kb/s data channel (typically for the transport of CCS messages). The rest of the
timeslots are labelled as in CAS: timeslots 1 through 15 correspond to circuits 1
through 15 and timeslots 17 through 31 correspond to circuits 16 through 30. The 31
circuits are treated equally. Timeslot 0 is used for framing.
31 channels framing
This framing pattern has the same designation of timeslots to circuits as CCS.
However, when making super-rate connections (connections that occupy more than
one channel on a primary rate link) to an E1 link, the system does not skip timeslot
16 (the 31st circuit); timeslots 1 through 31 are used consecutively (see Table 20.6-3).
Timeslot 0 is used for framing.
X.21 NTU framing

This framing pattern has the same designation of timeslots to circuits as CCS. The
X.21 NTU framing type is selected when an E1 link is connected to an X.21 NTU.
Table 20.6-4 shows an example of how the E1 channels are occupied if you connect
a 256 kb/s (4 x 64 kb/s) data circuit to circuit 15 of an E1 link.
(400)
20.6-5
20.6 Framing

NNP 95-2035-01-00-B
Table 20.6-4: E1 and E3 Card Super-rate Connections and Frame Types

Frame Type
Order
CAS
CCS
Timeslot
Circuit
15 17 18 19
15 16 17 18
31 Channels
Timeslot
Circuit
15 16 17 18
15 31 16 17
For more information on super-rate connections to primary rate interfaces, see

chapter 20.15.
To configure framing for E1 and E3 cards

Configure framing for E1 and E3 cards according to the options listed in Table 20.6-2.
CONFIG SLOT <sn> or <sn-l> or <E3id-E1id> OPTIONS FRAME_TYPE
CAS*
CCS
X.21_NTU
31_CHAN
SK000070
Note 1
You cannot select FRAME_TYPE if any circuits are connected.
Note 2
The X.21_NTU option is available only for E1 cards
To configure framing for Dual E1, Dual E1-2 and Optical Extension cards
CONFIG SLOT <sn-l> OPTIONS PHYSICAL FRAME_TYPE
CAS
CCS
31_CHAN
SK000705
20.6-6
(400)

NNP 95-2035-01-00-B
20.6.4
20.6 Framing
Configuring Framing for X.21 PRI-2 Cards

There are two variants of the X.21 PRI card.
The X.21 PRI card uses Frame 1-type framing to provide up to 30 circuits without
signalling; a supervisory channel (TS0) is not supported.

The X.21 PRI-2 card can be configured to use either:
Frame 1 type (FRAME_1) framing
Frame 2 type (FRAME_2) framing to provide 30 circuits with or without
signalling and a supervisory channel (TS0)
The X.21 PRI-2 card is normally configured for Frame 2 type framing. The Frame 1
type option is provided for backwards compatibility with older X.21 PRI cards.
To configure framing for X.21 PRI-2 cards

CONFIG SLOT <sn> OPTIONS FRAME_1/FRAME_2*
(400)
20.6-7

NNP 95-2035-01-00-B
20.7
20.7 Line Length

Line Length
This chapter explains how to configure line length for:
T1 cards with a DSX-1 module, LIM, CSU or CSU2 module

DS-3 or DS-3 II cards
20.7.1
Configuring Line Length for a T1 Card

The following subsections explain how to configure line length for the T1 card.
T1 card with a DSX-1 module or LIM

For DSX-1 or LIM equipped T1 cards, line length is the distance between the T1 card
and the external channel service unit or digital cross-connect point. You can
configure line length as:
SHORT for 0 to 46 m (0 to 150 ft) (default)

MEDIUM for 46 to 137 m (150 to 450 ft)
LONG for 137 to 200 m (450 to 655 ft)
T1 card with a CSU or CSU2 module
For a T1 card with a CSU or CSU2 module, the line length specifies the LBO. You can
configure the line length as:
SHORT for 15 dB (default)

MEDIUM for 7.5 dB
LONG for 0 dB
Note
Use 100 W RJ48C cables to connect external devices to T1 interfaces.
(400)
20.7-1
20.7 Line Length


NNP 95-2035-01-00-B
To configure the line length for a T1 card

CONFIG SLOT <n> or <sn-l>
OPTIONS
OPTIONS
PHYSICAL
LINE_LNGTH
SHORT*
MEDIUM
LONG
SK000071
20.7.2
Configuring Line Length for a DS-3 or DS-3 II Card

For the DS-3 or DS-3 II card, the line length is the distance between the card and the
digital cross-connect point. You can configure line length as:
SHORT for 0 to 69 m (0 to 225 ft) (default)

LONG for 69 to 137 m (225 to 450 ft)
To configure line length for a DS-3 or DS-3 II card
CONFIG SLOT <DS3> OPTIONS LINE_LNGTH
SHORT*
LONG
SK000072
20.7-2
(400)

NNP 95-2035-01-00-B
20.8
20.8 Zero Code Suppression

Zero Code Suppression

This chapter explains how to configure zero code suppression for T1 and DS-3 or
DS-3 II cards.
20.8.1
Understanding Zero Code Suppression

Line synchronization is lost if too many consecutive zeros are transmitted on the
link. Zero code suppression provides sufficient pulse (ones) density to ensure that
line synchronization is maintained.
Table 20.8-1 lists the types of zero code suppression supported on cards that provide
this option. The type of zero code suppression you select applies to all circuits on the
link DS1.
Table 20.8-1: Zero Code Suppression Options
T1 card
DS-3 and
DS-3 II
cards (1)
Framing
Option
Transparent
TRANSP
Binary 8 Zero suppression
B8ZS
Jam Bit 7
JB7*
Notes
1. Zero code suppression is done at the DS1 level on the DS-3 or DS-3 II card.
Caution
The same type of zero code suppression must be configured at both ends of a link.
Transparent framing
The transparent option means that the system uses no zero suppression at the slot
level. Cross-connected devices must use a protocol designed to ensure a sufficient
ones density pattern to avoid line synchronization problems.
(400)
20.8-1


NNP 95-2035-01-00-B
Caution
The transparent setting should be used with caution as network equipment could
lose synchronization if the ones density requirement is not satisfied.
Binary 8-zero suppression framing

Binary 8-zero suppression ensures a minimum one-in-eight ones density by
replacing eight consecutive zeros with a known pattern of ones with bipolar
violations. You must select B8ZS if 64 kb/s clear data channels are required (either
channels for which signalling is not passed, or channels configured for TS24S
signalling with a TSM).
Jam bit 7 framing

Jam bit 7 changes bit 7 (the next-to-least significant bit) to a 1 if all eight bits of the
word are 0. Do not select JB7 if 64 kb/s clear data channels are required (either
channels for which signalling is not passed, or channels configured for TS24
signalling when a TSM is installed).
20.8.2
Configuring Zero Code Suppression

Configure zero code suppression according to the options listed in Table 20.8-1.
To configure zero code suppression for T1 cards

CONFIG SLOT <sn> or <sn-l>
OPTIONS OPTIONS
PHYSICAL
ZERO_SUPPR
TRANSP
B8ZS
JB7*
SK000073
20.8-2
(400)

NNP 95-2035-01-00-B

To configure zero code suppression for DS-3 or DS-3 II cards

CONFIG SLOT <n> OPTIONS ZERO_SUPPR
TRANSP
JB7*
SK000074
(400)
20.8-3

NNP 95-2035-01-00-B
20.9
20.9 Trunk Conditioning

Trunk Conditioning
This chapter introduces trunk conditioning for PRI cards and explains how to
configure trunk conditioning.
20.9.1
Understanding Trunk Conditioning for PRI Cards

When an aggregate interface card link experiences a fault, trunk conditioning is
applied to all circuits on that link. The type of trunk conditioning you configure for
a link determines on which paths (information or signalling) and in which directions
(transmit or receive) fault signalling is transmitted. You can enable or disable trunk
conditioning independently for different classes of link faults. Chapter 20.10
describes fault signalling and fault classes.
For Dual T1-2, Dual E1-2 and MPA cards, you can configure trunk conditioning
independently for each link.
Each aggregate interface card circuit (bidirectional and unidirectional) is made up of
two components.
An information component thatcarries the circuit's payload, data or voice.

A signalling component that carries signalling, when signalling is enabled
Chapter 20.12 describes signalling.
Trunk conditioning direction is defined with respect to an aggregate interface card
circuit on the faulty link.
The transmit direction is defined by the transmit path from the aggregate
interface card circuit to its connected circuit.

The receive direction is defined by the receive path from the connected circuit to
its aggregate interface card circuit.
Table 20.9-1 lists the types of trunk conditioning supported. The default trunk
conditioning direction for all card types is two-way.
Table 20.9-1: Aggregate Interface Card Trunk Conditioning
Card Type
T1
Two-way
E1
(1)
Dual T1
Dual E1
MPA
Optical Extension
One-way
(400)
(1)
(1)
20.9-1


NNP 95-2035-01-00-B
Card Type
One-way
Two-way
TTC2M
X.21 and V.35 PRI
DS-3 or DS-3 II
E3
64 kb/s Codirectional card (2)
Notes
1. When configured for unidirectional circuits, PRI cards support only one-way trunk conditioning.
2. The 64 kb/s Codirectional card performs trunk conditioning when it detects a Loss of Incoming Signal
condition.
Note
Regardless of the type of trunk conditioning configured, two-way trunk
conditioning is applied to aggregate interface card circuits cross-connected to CPSS
circuits and voice compression subframes.
One-way trunk conditioning

When you configure one-way trunk conditioning, the signalling path or the
information path, or both (depending on the fault), are broken in the transmit
direction only. Transmission in the receive direction is not affected.
One-way trunk conditioning operates differently for each of three groups of link
faults. Table 20.9-2 lists the effect on the signalling and information path for each
group of link faults when one-way trunk conditioning is selected. One-way trunk
conditioning does not affect Group 3 link faults.
After breaking the signalling or information path in the transmit direction, the
aggregate interface card circuit transmits the fault signalling it was configured with,
or a special code, to the connected circuit. Table 20.9-3 lists the type of code
transmitted for each type of connected circuit. If a signalling or information path is
not broken, the aggregate interface card continues to transmit what it receives.
20.9-2
(400)

NNP 95-2035-01-00-B

Table 20.9-2: One-way Trunk Conditioning Link Faults

Card
Link Faults
Signalling Path
Information Path
Group 1 Link Faults

E1, E3
Framing Alarm
AIS
Framing Error Rate
Exceeded
Failed State
Broken in the transmit

direction

direction
64 kb/s
Codirectional
Failed State

direction

direction
T1
Red Alarm

direction

direction
TS24 Frame Alarm (1)

Framing Error Rate
Exceeded
Failed State
X.21 and V.35 PRI
Framing Alarm
Failed State

direction

direction
MPA
Framing Alarm
Failed State
Loopback Detected
Clock Speed Mismatch

direction

direction
TTC2M
Framing Alarm
Framing Error Rate
Exceeded
Failed State
LIS

direction

direction
E1, E3, 64 kb/s

Codirectional,
X.21 and V.35 PRI
Multi-frame Alarm
Incoming TS16 AIS

direction
No change
TTC2M
Multi-frame Alarm

direction
No change
Group 2 Link Faults
Group 3 Link Faults (2)

E1, E3
Distant Alarm
TS16 Distant Alarm
No change
No change
T1
Yellow Alarm
No change
No change

X.21 and V.35 PRI
Distant Alarm
No change
No change
MPA
Distant Alarm
No change
No change
TTC2M
Distant Alarm
No change
No change
Notes
1. For TSM-equipped Dual T1 or DRM-equipped Dual T1-2 only.
2. One-way trunk conditioning does not result in the information or the signalling path being broken in
either direction, because the fault lies in the aggregate interface card circuit receive path.
(400)
20.9-3


NNP 95-2035-01-00-B
Table 20.9-3: One-way Trunk Conditioning Signalling and Information Path Codes
Code
Non-Aggregate Interface Card

Connected Circuit
Aggregate Interface Card

Connected Circuit
Code Transmitted on
Signalling Path
Signalling state at time of fault
Fault signalling (1)
Code Transmitted on
Information Path
All zeros
All ones or ASC (2)
Notes
1. If the fault signalling configured for this circuit is seized, the system does not transmit an idle code
first, as is the case for two-way trunk conditioning.
2. If the connected circuit is an aggregate interface card circuit configured for DDS rate adaption, an
ASC is transmitted. If it is not configured for DDS, all ones are transmitted.
Figure 20.9-1 shows one-way trunk conditioning for Group 1 link faults.
Figure 20.9-1: One-way Trunk Conditioning (Group 1)
If primary
rate circuit
SEIZED Signalling
or IDLE
If not primary
rate circuit
Frozen
Fault
Direction of transmission
Fault
If not primary rate circuit,
all 0s.
If primary rate circuit not
carrying a circuit
using DDS, all 1s.
If primary rate circuit
carrying a circuit using
PRI card
Connected circuit
Primary rate circuit
DDS, DDS abnormal
station code (ASC).
Signalling
Information
3715
20.9-4
(400)

NNP 95-2035-01-00-B

If primary
rate circuit
SEIZED Signalling
or IDLE
If not primary
rate circuit
Frozen
Fault
Connected circuit
Signalling
PRI card
Fault
Information
3716
Two-way trunk conditioning

When you configure two-way trunk conditioning, the signalling path and
information path are broken in both the transmit and receive direction.
After breaking the signalling and information paths, the aggregate interface card
circuit transmits the fault signalling it was configured with, or a special code, both
in the transmit direction and the receive direction.
Table 20.9-4 lists the type of code transmitted in each case.
Table 20.9-4: Two-way Trunk Conditioning Signalling and Information Path Codes
Code
Non-Aggregate
Interface Card
Connected Circuit
Aggregate
Interface Card
Connected Circuit
To Far End
Code Transmitted on
Signalling Path
Code Transmitted on
Information Path
All zeros
All ones or ASC (2)
All ones or ASC (2)
Notes
1. Signalling is driven to idle for 2.5 seconds and then fault signalling is transmitted as configured. If
fault signalling is configured as Out-of-service, A, B or C signalling is not driven to idle first.
(400)
20.9-5


NNP 95-2035-01-00-B
Figure 20.9-3 shows two-way trunk conditioning.

Figure 20.9-3: Two-way Trunk Conditioning
SEIZED
or
IDLE
Signalling
Fault

all 0s.
carrying a circuit
using DDS, all 1s.
DDS, DDS abnormal Connected circuit
station code (ASC).
PRI card
Fault

All 1s
or
DDS ASC
Signalling
2.5s
SEIZED
or
IDLE
Signalling
Information
Fault
3714
Disabling trunk conditioning

For all aggregate interface cards, you can disable trunk conditioning for certain
groups of link faults called fault classes. Deselecting all the fault classes on the link
disables trunk conditioning on that link; see section 20.9.5 for information. For Dual
T1-2, Dual E1-2 and MPA cards you can disable trunk conditioning for each link
independently.
For the DS-3 or DS-3II card, you can disable trunk conditioning for all link faults, as
well as by fault class.
If you disable trunk conditioning, fault signalling is not applied to any connected
circuit, regardless of the link status; all connected circuits stay connected during the
affected link faults. If the connected circuit is protected, it does not switch to the
protecting circuit when link faults are raised; it switches only when the aggregate
interface card is physically removed.
To disable trunk conditioning for PRI cards

CONFIG CIRCUIT <sn- cc> or <E3id-E1id-cc> FAULT_SIG NONE
20.9-6
(400)

NNP 95-2035-01-00-B
20.9.2

Trunk Conditioning Configuration Overview

To enable trunk conditioning on PRI card links and circuits, three configuration
procedures are involved.
Trunk conditioning general configuration procedure
1.
Set one-way or two-way trunk conditioning for the link. See section 20.9.3.
2.
Configure the trunk conditioning fault class for the link. See section 20.9.5.
3.
Enable fault signalling for each circuit on the link. See section 20.10.2.
For all aggregate interface cards, you can enable trunk conditioning for certain
groups of link faults called fault classes. Enabling all the fault classes on the link
enables trunk conditioning on that link.
20.9.3
Configuring One-way or Two-way Trunk Conditioning

The type of trunk conditioning you select for a PRI card link determines on which
paths (information or signalling) and in which directions (transmit or receive) fault
signalling is transmitted. Configure trunk conditioning as:
ONE_WAY for one-way conditioning

TWO_WAY for two-way conditioning (default)
Caution 1
Except for Dual T1-2 and Dual E1-2 cards, changing the trunk conditioning
configuration while circuits are connected causes a service disruption.
Caution 2
To guarantee the correct propagation of OOS codes, ensure that trunk conditioning
is enabled at both ends of a TS24 signalling link.
To select one-way or two-way trunk conditioning for Dual E1-2 and

Dual T1-2 cards
CONFIG SLOT <sn-l> OPTIONS FAULT_HNDL TRUNK_COND
ONE_WAY/TWO_WAY*
To select one-way or two-way trunk conditioning for MPA cards

CONFIG SLOT <sn-l> OPTIONS MORE FAULT_HNDL TRUNK_COND
ONE_WAY/TWO_WAY*
(400)
20.9-7


NNP 95-2035-01-00-B
To set other PRI cards for one-way or two-way trunk conditioning

CONFIG SLOT <n> or <sn> or <sn-l> <E3id-E1id> OPTIONS MORE
TRUNK_COND ONE_WAY/TWO_WAY*
Note
The MORE option is not applicable for the 64 kb/s Codirectional and the
TTC2M cards.
20.9.4
Understanding Fault Class Trunk Conditioning

For T1, E1, MPA, TTC2M, X.21 and V.35 PRI, DS-3 and DS-3 II cards, link alarms are
organized into groups called fault classes. You can enable or disable trunk
conditioning independently for each fault class.
For E3 and 64 kb/s Codirectional cards, trunk conditioning is applied as configured
for all link alarms when an alarm in any fault class is raised. Chapters 20.9 and 20.11
describe trunk conditioning.
Deselecting all fault classes disables the trunk conditioning for the link. For
Dual T1-2, Dual E1-2 and MPA cards, you can disable trunk conditioning for each
link independently.
If you turn trunk conditioning off for a primary rate circuit, no trunk conditioning is
done on that circuit regardless of how the link is programmed for trunk
conditioning. That is, the voice or data circuit connected to it stays connected during
any framing or distant alarms. If the voice or data circuit has a protecting connection,
it does not switch to that connection when a link alarm is raised. It switches only
when the primary rate card is absent.
Table 20.9-5 lists the fault classes and explains the alarms in each.
Note
Optical Extension cards support the same fault class descriptions as the Dual E1
card.
20.9-8
(400)

NNP 95-2035-01-00-B

Table 20.9-5: Fault Class Descriptions for PRI Cards

Fault Classes
E1, MPA, TTC2M,

X.21 and V.35 PRI
Alarms
DS-3 and T1 Alarms
Alarm Description
Framing Alarm
Incoming AIS
Multi-frame Alarm
Incoming TS16 AIS
Red Alarm
Distant Alarm
Incoming TS16 AIS
Yellow Alarm
Failed
Failed State
Failed State
This alarm is raised when 10 Severely Errored

Seconds have occurred in a row. It is cleared when
10 non-Severely Errored Seconds have occurred in
a row.
Error
Frame Error Rate

Exceeded (4)
Frame Error Rate

Exceeded
For T1 and DS-3 cards, this alarm is raised when the

terminal framing bit (Ft) Error rate exceeds
approximately 10-3 for a period of 4 to 6 s. It is
cleared when the Ft Error rate is below
approximately 10-4 for 9 to 11 s.
For E1 cards, this alarm is raised when the FAS error
rate exceeds approximately 10-3 for a period of 4 to
6 s. It is cleared when the FAS error rate is below
approximately 4 x 10-4 for 9 to 11 s.
For the TTC2M card, this alarm is raised when the
framing error rate has exceeded 10-3 frames per
second. This alarm is cleared when the framing error
rate falls below approximately 4 x 10-4 for 10
consecutive seconds.
Loopback (5)
CPSS Loopback
activated
In-band Loopback
activated
On-fault Loopback
activated
CPSS Loopback
activated
TS24 Loopback
activated
On-fault Loopback
activated
When the card receives a framed or unframed 10000

code from the network (usually originated by the
carrier), it enters a remote loopback state. The
incoming signal is looped back at the card towards
the network and continues through to the system.
Loopback trunk conditioning is applied as
configured. The card remains in this state until a
framed or unframed 100 code is received from the
network.
Frame/Red (1)
Distant/Yellow (3)
TS24 Distant Alarm (2)
These alarms are associated with frame alignment

or multi-frame alignment. These alarms are cleared
when frame alignment or multi-frame alignment is
regained.
These alarms are received from the equipment at the
far end of the primary rate link. These alarms are
cleared when the remote equipment is no longer
transmitting the alarm.
Notes
1. For E1, MPA, TTC2M, X.21 and V.35 PRI cards, this is the Frame fault class. For DS-3 or DS-3 II and T1 cards, it is the Red
fault class.
2. TS24 alarms apply only to a Dual T1 with TSM installed or Dual T1-2 with DRM.
3. For CEPT cards, this is the Distant fault class. For NA cards, it is the Yellow fault class.
4. Supported on E1, Dual E1 and Optical Extenstion cards only.
5. Different types of loopback alarms apply to the various PRI cards depending on the card type. See chapter 20.14 for details.
(400)
20.9-9

20.9.5

NNP 95-2035-01-00-B
Enabling or Disabling Fault Classes for PRI Cards

Configure fault classes for PRI cards according to Table 20.9-6. In all cases, the
default condition is enabled.
Table 20.9-6: Configuring Fault Classes for PRI Cards
T1 Cards
E1 Cards
MPA
Cards
TTC2M
Cards
X.21 and
V.35
Cards
DS-3 and
DS-3 II
Cards
Frame/Red
Distant/Yellow
Failed
Error
CSU Loopback/Loopback
Fault Class
Disabling trunk conditioning using fault classes

To completely disable trunk conditioning on the link, turn off all of the fault classes.
For Dual T1-2, Dual E1-2 and MPA cards, you can disable trunk conditioning for
each link independently.
To set fault classes for MPA cards

CONFIG SLOT <sn-l> OPTIONS MORE FAULT_HNDL TRUNK_COND
FRAME_OFF/
FRAME_ON*
DIST_OFF/
DIST_ON*
FAILED_OFF/
FAILED_ON*
LPBK_OFF/
LPBK_ON*
SK000693
To set fault classes for TTC2M cards
CONFIG SLOT <sn> OPTIONS TRUNK_COND
FRAME_OFF/
FRAME_ON*
SAI_OFF/
SAI_ON*
FAILED_OFF/
FAILED_ON*
ERROR_OFF/
ERROR_ON*
SK000746
20.9-10
(400)

NNP 95-2035-01-00-B

To set fault classes for other PRI cards

CONFIG SLOT <sn> or <n> or <sn-l> or <sn-l> OPTIONS
MORE
FAULT_HNDL
TRUNK_COND
RED_OFF/
YELLOW_OFF/
RED_ON* or
YELLOW_ON* or
FRAME_OFF/ DISTANT_OFF/
FRAME_ON*
DISTANT_ON*
FAILED_OFF/ ERROR_OFF/ LPBK_OFF/

FAILED_ON* ERROR_ON* LPBK_ON*or
CSU_LP_OFF/
CSU_LP_ON*
SK000078
where the second sn-l indicates a Dual T1-2 or Dual E1-2 card link
(400)
20.9-11

NNP 95-2035-01-00-B
20.10

Fault Signalling
This chapter describes how to configure fault signalling for PRI cards.
20.10.1
Understanding Fault Signalling for PRI Cards

When trunk conditioning is applied to a link, the system transmits a bit pattern (or
code), called fault signalling, on each circuit cross-connected to the link.
(Chapter 20.9 describes trunk conditioning.)
As Figure 20.10-1 shows, a T1 card circuit is configured to transmit a seized
fault-signalling code to the LGE card cross-connected to it. This prevents the PBX
from trying to place a call through the T1 card until its link returns to service.
Figure 20.10-1: Fault Signalling
MainStreet node
LGE
PBX
T1
Link
fault
Network
Phone
Fault signalling
seized
5418
You can configure the type of fault signalling independently for each aggregate
interface card circuit. Table 20.10-1 lists the fault signalling types and defaults for
each aggregate interface card.
Note
The 64 kb/s Codirectional card and the DS0-DP and OCU-DP channel units support
fault signalling, and the procedures in this chapter also apply to them. Certain voice
cards and channel units also support fault signalling (see chapter 21.8).
Of the channel units, only the E&M, DS0-DP and OCU-DP channel units respond to
OOS-A.
When you program a super-rate connection for OOS A, B or C, the first DS0 (the
master circuit) detects the fault condition and transmits the appropriate OOS code
(see chapter 20.9).
When a link carrying a channel that is being compressed fails, the fault signalling
sent to the far end is always seized (regardless of the fault signalling configured).
(400)
20.10-1


NNP 95-2035-01-00-B
Table 20.10-1: Fault Signalling for PRI Cards

Seized
Idle(1)
OOS A
OOS B
OOS C (2)
None
Single T1
card
(4)
(5)
(6)
Dual T1
card
(4)
(5)
Single E1
card
(7)
(7)
(8)
Dual E1
card
Optical
Extension
card
MPA card
Card or
Channel
Unit
CMI
NIS
In-use
DATA
TTC2M
card
MOS(3)
X.21 and
V.35 PRI
card
DS-3 or
DS-3 II card
(9)
(10)
(11)
SE3 and
DE3 card
(7)
(7)
(12)
64 kb/s
Codirection
al card
(13)
(13)
DS0-DP
channel
unit
Notes
1. Idle = default.
2. Only one end of a circuit may be configured for OOS-C fault signalling.
3. MOS = default.
4. Applies to DS0s (on either D4- or ESF-framed DS1s) with RBS enabled connected to 56 kb/s (or less) data, OCU-DP or
E&M circuits.
5. Applies to DS0s (on ESF-framed DS1s only) with RBS enabled connected to 56 kb/s (or less) data, OCU-DP or E&M circuits.
6. Applies to DS0s (on either D4- or ESF-framed DS1s) with RBS enabled connected to data or any voice circuits.
7. Applies to timeslots (on CAS-framed links only) connected to data or any voice circuits.
8. Applies to timeslots (on either CCS- or 31 Channel-framed links) connected to data or any voice circuits.
9. Applies to DS0s (on either D4- or ESF-framed DS1s) connected to data or E&M circuits.
10. Applies to DS0s (on ESF-framed DS1s only) connected to data or E&M circuits.
11. Applies to DS0s (on either D4- or ESF-framed DS1s) connected to data or any voice circuits.
12. Applies to timeslots (on CAS-, CCS- or 31 Channel-framed links) connected to data or any voice circuits.
13. Not applicable for timeslots configured for R2D signalling.
20.10-2
(400)

NNP 95-2035-01-00-B

Disabling fault signalling for PRI cards

You can enable or disable fault signalling independently for each circuit. If you
disable fault signalling (configure it as NONE), the circuit stays connected during
link faults. If the connected circuit is protected, it does not switch to the protecting
circuit when a link fault is raised; it switches only when the aggregate interface card
it is connected to is physically removed.
Fault signalling codes for PRI cards

The bit pattern transmitted when you select Idle or Seized as the fault signalling
defaults to the codes used in E&M signalling for most cards. PRI fault signalling
codes are:
Idle: 0000 (ESF), 00 (D4)

Seized: 1111 (ESF), 11 (D4)
For the TTC2M card, In-use signalling is used instead of Seized signalling. When
In-use is selected as the fault signalling, the bit pattern transmitted during trunk
conditioning is 0. When the Idle code is selected, the bit pattern transmitted is 1. If
NIS is selected, 2.5 seconds of Idle code is transmitted, followed by the In-use
condition. NONE fault signalling causes the signalling bit pattern to remain at the
value it was when trunk conditioning initially occurred.
To accommodate circuits configured for other signalling types, you can also
configure custom bit patterns, see chapter 20.11.
Table 20.10-2 lists the bit patterns transmitted when OOS A, B, or C fault signalling
is selected for aggregate cards that support OOS fault signalling.
Table 20.10-2: Fault Signalling Codes OOS A, B and C for PRI Cards
Card
Single T1
OOS C (1)
OOS A
OOS B
0100(01) (2)
0110(n/a)
Yellow/Distant Alarm
(2)
0110(n/a)
Dual T1
0100(01)
Dual E1
1111
0110
Dual E1
1111
0110
X.21 and V.35 PRI
1111
0110
MPA
1111
0110
DS-3
0100(01) (2)
0110(n/a)
SE3 and DE3
1111
0110
64 kb/s Codirectional
1111
0110
Notes
1. When OOS-C is selected for a DS0 and that circuit connection becomes unavailable, a yellow alarm
is generated on the DS1 circuit for a T1 DS0; a distant alarm is generated for an E1 DS0.
2. For ESF-framed DS1s, all four ABCD signalling bits are defined. For D4-framed DS1s, only the AB
signalling bits (shown in brackets) are defined.
(400)
20.10-3


NNP 95-2035-01-00-B
3664 MainStreet E1 and T1 cards

In 3664 MainStreet systems, T1 cards provide 12-channel DS1 links and E1 cards
provide 16-channel links. This configuration results in 12 unused channels on T1
cards and 15 unused channels on E1 cards. You can use the UNUSD_FSIG softkey to
define fault signalling at once for all the unused circuits (13 through 24 on T1 links
and 16 through 30 on E1 links).
20.10.2
Configuring Fault Signalling for PRI Cards

Configure fault signalling according to the options listed in Table 20.10-1. The trunk
conditioning for each circuit is disabled when no fault signalling is selected for the
circuit.
Note
For T1 circuits, fault signalling can be transmitted only if RBS is enabled or if a TSM
or DRM is installed. If neither of these conditions is met and OOS-A or OOS-B is
selected, a warning message appears when you attempt the cross-connection.
RBS uses the least significant bit of every channel in frames 6 and 12 (if D4 framing
is used) and frames 6, 12, 18 and 24 (if ESF framing is used). Use RBS with caution
on data circuits. If 64 kb/s clear channels with signalling are required, use a TSM or
DRM.
If you configure fault signalling before the signalling type, the system offers OOS
types A, B and C. If you subsequently select an incompatible signalling type (for
example, an LGS signalling type on a circuit with OOS type A enabled), a warning
message appears.
Restrictions
For D4-framed T1 circuits connected to E&M or data circuits, you can select
SEIZED, IDLE, OOS-A or OOS-C.
For ESF-framed T1 circuits connected to E&M or data circuits, you can select
20.10-4
SEIZED, IDLE, OOS-A, OOS-B or OOS-C.

For D4- or ESF-framed T1 circuits connected to LGS or LGE circuits, you can
select SEIZED, IDLE or OOS-C.
For 64 kb/s codirectional circuits, you can select SEIZED, IDLE, OOS-A or
OOS-B.
For the TTC2M card, a circuit must be disconnected before NIS or NONE fault
signalling can be applied.
(400)

NNP 95-2035-01-00-B

To configure fault signalling for PRI cards

When you select FAULT_SIG, the screen displays only the fault signalling options
that apply to the selected circuit.
CONFIG CIRCUIT <sn-cc> or <sn-l-cc> or <n-cc> or <E3id-E1id-cc> FAULT_SIG
SEIZED
IDLE*
OOS-B
OOS-A
NONE
OOS-C
SK000075
To configure fault signalling for TTC2M cards

CONFIG CIRCUIT <sn-cc> FAULT_SIG
IDLE*
IN_USE
NIS
NONE
DATA
SK000745
To configure fault signalling for DS0-DP channel units

CONFIG CIRCUIT <sn-cc-1> FAULT_SIG
MOS*
CMI
SK000076
To configure unused channels in 3664 MainStreet T1 and E1 cards

CONFIG SLOT <n> or <sn-l>
OPTIONS
OPTIONS
PHYSICAL
UNUSD_FSIG
SEIZED
IDLE
OOS-A
OOS-B
NONE
OOS-C
SK000077
(400)
20.10-5


NNP 95-2035-01-00-B
To disable trunk conditioning on PRI card circuits

CONFIG CIRCUIT <sn-cc> or <E3id-E1id-cc> FAULT_SIG NONE
20.10-6
(400)

NNP 95-2035-01-00-B
20.11

Custom Trunk Conditioning

This chapter explains how to configure custom trunk conditioning for PRI cards.
20.11.1
Understanding Custom Trunk Conditioning

The fault signalling bit pattern (or code) that is transmitted during trunk
conditioning defaults to the codes used in E&M signalling (see chapters 20.9 and
20.10). To accommodate circuits configured for other types of signalling, configure
custom bit patterns for the T1, E1, MPA, Optical Extension, TTC2M, X.21 and V.35
PRI, E3 and 64 kb/s Codirectional cards.
As shown in Figure 20.11-1, circuits on E1 card 1 are configured with the fault
signalling codes used by LGS-LS signalling to accommodate the device to which
they are connected (PBX-2). Without custom trunk conditioning, the default E&M
fault signalling codes are unrecognizable to PBX-2.
Figure 20.11-1: Connection Path with Custom Trunk Conditioning
LGS-LS
fault signalling
LGS-LS
Link
fault
Node A
PBX-1 T1
T1
1
T1
2
T1
Node B
T1
T1
3
E1
1
LGS-LS
Node C
E1
E1
2
E1
3
E1 PBX-2
Seized: 1111
Idle: 0101
5367
For all aggregate interface card circuits (except compressed voice circuits), configure
the custom fault signalling bit patterns independently for each circuit on a link. The
following fault signalling codes are available.
CODE_1 is the code transmitted on the signalling path when the circuit is
configured to transmit idle fault signalling. The default is 0000.
configured to transmit seized fault signalling. The default is 1111.

DATA is the code transmitted on the information path. The default is 11111111.
(400)
20.11-1


NNP 95-2035-01-00-B
The CODE_1 and CODE_2 bit patterns represent the settings of the ABCD signalling
bits. For D4-framed DS1s, only the AB bits are defined. For ESF-framed DS1s, E1s
and X.21 and V.35 PRIs, all four ABCD bits are defined.
If you change framing on a DS1 from D4 to ESF after configuring CODE_1 or
CODE_2, the configured AB bits are copied into the CD bit positions (that is, ABAB
is transmitted). If you change framing on a DS1 from ESF to D4 after configuring
CODE_1 or CODE_2, only the configured AB bits are transmitted; the CD bits are
ignored.
If an E1 circuit is configured for T1 signalling, you configure only the AB bits; the C
and D bits are fixed at 0 and 1, respectively.
Caution
Never set CODE_1 (idle) and CODE_2 (seized) to all zeros. An all-zero setting can
cause multiframe problems in an E1 network.
Table 20.11-1 lists common seized and idle codes for each signalling type supported
by the system except the TTC2M card. See section 20.12.4 for information about
TTC2M card idle and in-use codes.
Table 20.11-1: Fault Signalling Codes Seized and Idle for PRI Cards
Seized Code
Idle Code
Signalling
E1, E3, MPA, Opt.
Ext., X.21 and V.35
PRI (1)
T1 and G.703
Codir (2)
DS-3 and
DS-3 II
E1, E3, MPA, Opt.

Ext., X.21 and
V.35 PRI (1)
T1 and G.703
Codir (2)
DS-3 and
DS-3 II
DPO/DPT
1111
1111
0000
0000
E&M (T1/NA)
0101
1111
11
1101
0000
00
E&M (E1/UK)
1111
0101
0000
1101
LGE_EC
0101
0101
1101
1101
LGE_GS
0000
0000
00
0101
0101
01
LGE_LCDC
0101
0101
1101
1101
LGE_LS
1111
1111
11
0101
0101
01
LGE_RE
0101
0101
1101
1101
LGS_CBW
1101
1101
1101
1101
LGS_EC
1001
1001
1101
1101
LGS_GS
0101
0101
01
1111
1111
11
LGS_LCDC
1001
1001
1101
1101
LGS_LS
0101
0101
00
0101
0101
01
LGS_PLAR
0000/0101
0000
00
0000/0101
1111
00
LGS_RE
1101
1101
1101
1101
R2D E&M
0011
0011
1011
1011
20.11-2
(400)

NNP 95-2035-01-00-B

Notes
1. When T1 signalling is configured on E1 timeslots, the last two bits (C and D) are set to 0 and 1,
respectively.
2. Codes shown are for ESF-framed DS1s (which use all four ABCD bits). For D4-framed DS1s, only
the first two bits (AB) are transmitted.
20.11.2
Configuring Custom Trunk Conditioning for PRI Cards

Configure custom trunk conditioning as:
CODE_1 for the code transmitted on the signalling path when the circuit is
configured to transmit Idle fault signalling (the default is 0000)
configured to transmit Seized fault signalling (the default is 1111)

DATA for the code transmitted on the information path (the default is 11111111)
The TTC2M card supports only DATA custom trunk conditioning.
To configure custom trunk conditioning for PRI cards

CONFIG CIRCUIT <sn-cc> or <sn-l-cc> or <E3id-E1id-cc> FAULT_SIG MORE CUSTOM
CODE_1
CODE_2
<code> <code>
DATA
<data>
SK000079
where
code is a four-digit binary code
data is an eight-digit binary code
To configure custom trunk conditioning for TTC2M cards

CONFIG CIRCUIT <sn-cc> FAULT_SIG DATA <data>
where data is an eight-digit binary code
(400)
20.11-3


NNP 95-2035-01-00-B
To configure unused channels in 3664 MainStreet T1 and E1 cards

CONFIG SLOT <n> or <sn-l> OPTIONS PHYSICAL UNUSD_FSIG
SEIZED
IDLE
OOS-A
OOS-B
NONE
OOS-C
MORE
CUSTOM
CODE_1 CODE_2
DATA
<code> <code> <data>

SK000080
where
code is a four-digit binary code
data is an eight-digit binary code
20.11-4
(400)

NNP 95-2035-01-00-B
20.12

PRI Signalling
This chapter describes the implementation of signalling for the following PRI cards:
T1 and DS-3 or DS-3 II cards

E1, MPA, Optical Extension, X.21 and V.35 PRI, E3 and 64 kb/s Codirectional
20.12.1
cards
TTC2M card
Understanding Signalling for PRI Cards

Signalling defines the codes and protocol used to communicate call setup, call tear
down and status information between two voice devices (such as PBXs)
interconnected by a primary rate link. The voice device is connected to a voice
interface (such as an LGS card or channel unit) that is cross-connected to a DS0 on a
primary rate link (such as a T1 or E1).
Signalling types for PRI cards

You can configure signalling types for the 64 kb/s Codirectional card and all
primary rate cards except the TTC2M card. The TTC2M card uses a fixed signalling
scheme: 0 for In-use (off-hook) and 1 for Idle (on-hook).
Typically, the signalling need only be configured at the voice card circuits. If you
configure the primary rate signalling type for the default, the primary rate circuit
automatically takes on the signalling type required by the end-point circuit when
you make the connection. The primary rate signalling type returns to the default
when you disconnect the connection.
If you do not configure the primary rate signalling type for the default, connection
to an end-point circuit is allowed only if the configured signalling type is compatible
with the end point circuit. The primary rate signalling type remains at its configured
setting when you disconnect the connection.
You must configure signalling for a primary rate circuit when:
primary rate circuits are cross-connected in a tandem node

An E1, Dual E1, Dual E1-2, MPA, Optical Extension, X.21 PRI, V.35 PRI, or E3
card circuit using R2 digital signalling is connected to an E&M circuit
Table 20.12-1 lists the PRI signalling types and indicates how they apply to each type
of PRI card.
(400)
20.12-1


NNP 95-2035-01-00-B
Note
Optical Extension cards use the same signalling types as the E1 cards.
Table 20.12-1: PRI Signalling Types

T1
Card
E1
Card
MPA
Card
X.21
and
V.35
Card
DS-3
and
DS-3 II
Card
E3
Card
64 kb/s
Codir
Card
Transparent
SIG
Clear channel
NoSIG
E&M
E+M
Continuous E&M
E+M_B
Signalling Type
Option
LGS Remote
Extension
LGS
REM_EXT
LGS Earth Calling
LGS EC
LGS PLAR
E1_SIG or
T1_SIG) LGS
PLAR or
PLAR_D3
LGE Remote
Extension
LGE
REM_EXT
LGE Earth Calling
LGE EC
LGS Loop Start
LGS LS
LGS Ground Start
LGS GS
LGE Loop Start
LGE LS
LGE Ground Start
LGE GS
R2D_E+M
RBS
RBS
Terminate
TERMINATE
Compatible PRI signalling types

Table 20.12-2 lists compatible signalling type combinations for connections between
different types of primary rate links. If the attempted connection is possible, the
system connects the primary rate circuits; if not, it displays an error message.
20.12-2
(400)

NNP 95-2035-01-00-B

Table 20.12-2: Compatible PRI Signalling Types

T1, Dual T1-2 and DS-3 or DS-3 II (1)
E1, Dual E1, Dual E1-2, E3, MPA, Optical

Extension and X.21 or V.35 PRI
Transparent
Transparent
Clear channel
Clear channel
E&M
E&M
Continuous E&M (2)
E&M
LGS PLAR
LGS PLAR (3) or PLAR D3 (4)
LGS Remote Extension
LGE Loop Start
LGE Remote Extension
LGS Loop Start
LGS Earth Calling
LGE Ground Start
LGE Earth Calling
LGS Ground Start
Notes
1. DE3 or SE3 to DS-3 or DS-3 II connections are supported only by NoSIG connections.
2. Continuous E&M is used to convert a proprietary signalling type to Newbridge standard E&M
signalling. Continuous E&M is supported if the E1 link is configured for CAS.
3. LGS PLAR is equivalent to D4 PLAR signalling as specified in the 1985 Addendum to PUB 43801.
4. PLAR D3 is equivalent to D3 PLAR signalling as specified in the 1982 Addendum to PUB 43801.
Figure 20.12-1 shows an example of how the signalling type for the T1 and E1 circuits
must be configured at the node before connecting them. At the London node, the T1
circuit is configured as type LGS GS (for the device connected in New York) and the
E1 circuit as type LGE EC (for the device type connected in Paris). The New York and
Paris nodes do not need to configure the signalling type.
Figure 20.12-1: Example of Signalling Type Configuration
New York
Paris
London
LGS-GS
T1
36120
MainStreet node
T1
E1
3600
MainStreet node
E1
LGE-EC
3645
MainStreet node
5419
PLAR D3 signalling
When LGS PLAR is selected, the system provides signalling according to the 1985
Addendum to PUB 43801. This Addendum specifies support for D4 channel banks
and inverts the state of the signalling bits specified in the 1982 Addendum. When
LGS PLAR_D3 is selected, the system provides signalling according to the 1982
Addendum to PUB 43801. PLAR_D3 signalling supports third-party nodes (such as
D3 channel banks) that still comply with the 1982 Addendum.
(400)
20.12-3


NNP 95-2035-01-00-B
In Figure 20.12-1, the New York node is a third-party D3 channel bank connected to
a voice interface configured for LGS PLAR. The 3645 MainStreet node in Paris is also
connected to an LGS PLAR voice interface. At the London node, the T1 is configured
for PLAR_D3 signalling (to accommodate the 1982 Addendum-compliant D3
channel bank in New York) and the E1 is configured for PLAR signalling (to
accommodate the 1985 Addendum-compliant 3645 MainStreet node in Paris).
If you are connecting an E1, Dual E1, Dual E1-2 or Optical Extension card circuit
using R2 digital signalling to an E&M circuit, you must configure the primary rate
circuit as type R2D_E+M.
RBS
You can configure RBS for T1 and DS-3 or DS-3 II cards. RBS is usually used to pass
ABCD signalling. When RBS is enabled, the least significant bit (bit 8) of every
channel in frames 6 and 12 (if D4 framing is used) or in frames 6, 12, 18 and 24 (if ESF
framing is used) is overwritten with signalling information.
You cannot use RBS under the following conditions.
If a DCC, DNIC or 2B1Q Line card circuit with a bandwidth of 64 kb/s or greater
is connected to a T1 circuit, RBS must be disabled.

When a signalling or compressed voice channel defined by a VCM-equipped
Dual E1 card is connected to a T1 circuit, RBS is automatically disabled for the T1
circuit.
Note
When you configure a Dual T1-2 card for ISDN, the system automatically turns RBS
on.
20.12-4
(400)

NNP 95-2035-01-00-B
20.12.2

Configuring Signalling forT1, DS-3 and DS-3 II Cards

Configure T1, Dual T1, Dual T1-2 and DS-3 circuits with one of the following
signalling types:
SIG for transparent, where signalling is passed without being tested for
compatibility with the signalling type at the far end (default for DS-3, DS-3 II and
T1 cards, and Dual T1 cards without TSMs or Dual T1-2 cards without DRMs)
NoSIG for clear channel, where a 64 kb/s clear channel is created without
signalling
E+M for E&M
LGS LS for LGS Loop Start
LGS GS for LGS Ground Start
LGS PLAR or PLAR_D3 for LGS PLAR
LGE LS for LGE Loop Start
LGE GS for LGE Ground Start
RBS_ON to enable RBS
RBS_OFF to disable RBS
TERMINATE for accessing a frame relay network
Note
In a T1-to-T1 tandem node, if you select NoSIG and enable RBS, the system does not
monitor the signalling of the data received and overwrites the outgoing data bits
with the default RBS pattern.
For a Dual T1 with a TSM or a Dual T1-2 with a DRM, you can create 64 kb/s clear
channels without ABCD signalling in common signalling channel timeslot 24. All of
the signalling types described here can be carried by the TSM or DRM (see
chapter 20.5).
To enable signalling for T1, DS-3 and DS-3 II cards

CONFIG CIRCUIT <sn-cc> or <n-cc> or <sn-l-cc> MORE SIG_TYPE
TERMINATE
NoSIG
SIG*
LS
E+M
PLAR
PLAR_D3
LGS
LGE
GS
LS
GS
SK000081
To enable or disable RBS for T1, DS-3 and DS-3 II cards

CONFIG CIRCUIT <sn-cc> or <sn-l-cc> FUNCTION RBS_OFF/RBS_ON*
(400)
20.12-5


NNP 95-2035-01-00-B
To create clear channels for T1 and DS-3 or DS-3 II cards

To create a 64 kb/s clear channel without signalling, select NoSIG and turn off RBS
for the T1 or DS-3 circuit.
20.12.3
Configuring Signalling for E1, MPA, Optical Extension,

X.21 and V.35 PRI, E3 and 64 kb/s Codirectional Cards
Configure E1, Dual E1, Dual E1-2, Optical Extension, X.21 and V.35 PRI, MPA, E3
and 64 kb/s Codirectional bidirectional circuits as:
E1_SIG SIG or T1_SIG SIG for transparent E1 or T1 signalling, where signalling
is passed without being tested for compatibility with the far-end signalling type
(E1_SIG SIG is the default for E1 signalling and for PRI circuits with NUM_SIG
set to a value other than 0)
E1_SIG NoSIG or T1_SIG NoSIG for clear channel E1 or T1 signalling, where a 64
kb/s clear channel is created for which signalling is not passed (default for PRI
circuits with NUM_SIG set at the default value of 0)
E1_SIG E+M E+M or T1_SIG E+M for E&M for E1 or T1 signalling, or E1_SIG
E+M E+M_B for conversion of proprietary E1 signalling to Newbridge standard
E1 signalling
E1_SIG LGS REM_EXT for LGS Remote Extension for E1 signalling
E1_SIG LGS EC for LGS Earth Calling for E1 signalling
E1_SIG LGS PLAR for LGS PLAR for E1 signalling
E1_SIG LGE REM_EXT for LGE Remote Extension for E1 signalling
E1_SIG LGE EC for LGE Earth Calling for E1 signalling
T1_SIG LGS LS for LGS Loop Start for T1 signalling
T1_SIG LGS GS for LGS Ground Start for T1 signalling
T1_SIG LGS PLAR or PLAR_D3 for LGS PLAR for T1 signalling
T1_SIG LGE LS for LGE Loop Start for T1 signalling
T1_SIG LGE GS for LGE Ground Start for T1 signalling
R2D_E+M for R2 digital signalling
Unidirectional circuits
Configure unidirectional circuits as:
E1_SIG SIG for transparent E1 signalling, where signalling is passed without
20.12-6
being tested for compatibility with the far-end signalling type

E1_SIG NoSIG for clear channel E1 signalling, where a 64 kb/s clear channel is
created without signalling
(400)

NNP 95-2035-01-00-B

64 kb/s Codirectional card bidirectional circuits

You can configure bidirectional circuits on the 64 kb/s Codirectional card with any
of the signalling types used for E1, PRI and E3 cards, but you must configure a
specific signalling type for the 64 kb/s Codirectional card when:
a T1 or Dual T1-2 circuit is connected to an E1, Dual E1, X.21 and V.35 PRI, or
64 kb/s codirectional circuit, use E1_SIG

an E1, Dual E1, Dual E1-2, Optical Extension, X.21 and V.35 PRI, or 64 kb/s
codirectional circuit using R2 digital signalling is connected to an E&M circuit,
use R2D_E+M
an E1, Dual E1, Dual E1-2, X.21 and V.35 PRI, or 64 kb/s codirectional circuit is
connected to equipment requiring T1 type signalling, use T1_SIG
If the 64 kb/s codirectional circuit is configured for OOS-A or OOS-B, it cannot be

configured for R2 digital signalling; conversely, OOS-A and OOS-B are not available
if the circuit is configured as R2 digital signalling.
64 kb/s Codirectional unidirectional circuits

Configure 64 kb/s codirectional unidirectional circuits (available on card version
90-0470-04) as one of the following signalling types:
E1_SIG SIG for transparent E1 signalling, where signalling is passed without

being tested for compatibility with the far end signalling type
E1_SIG NoSIG for clear channel E1 signalling, where a 64 kb/s clear channel is
created without signalling
MPA card signalling channels

If signalling is to be used on an MPA card circuit, a channel on the MPA card
interface must be configured for signalling. To configure the number of signalling
channels on the MPA card interface, see section 20.20.4.
(400)
20.12-7


NNP 95-2035-01-00-B
To configure signalling type for E1, MPA, X.21 and V.35 PRI, E3 and 64 kb/s
Codirectional cards
CONFIG CIRCUIT <sn-cc> or <sn-l-cc> or <E3id-E1id> MORE SIG_TYPE
E1_SIG
SIG*
T1_SIG
R2D_E+M
NoSIG
E+M
REM_EXT
LGS
E+M
LGE
E+M_B
PLAR
EC
SIG
LS
NoSIG
GS
EC
REM_EXT
E+M
PLAR
LGE
LGS
PLAR_D3
LS
TERMINATE
GS
SK000082
20.12.4
Signalling for the TTC2M Card

Signalling specifies how a call is established. For the TTC2M card, signalling is sent
as part of the TS0 supervisory channel and is not configurable.
The TTC2M card signalling is digital and only one of two states are possible: 0 for
In-use (off-hook) or 1 for Idle (on-hook). When cross-connecting PRI card channels
to the TTC2M card, the PRI card channel assumes the signalling type of the TTC2M
card. When a PRI card channel is disconnected from the TTC2M card, the channel
signalling state returns to its default value.
Note
The TTC2M card cannot connect to a circuit that has LGE signalling. All other
signalling types listed in Table 20.12-1 are compatible with the TTC2M card.
Table 20.12-3 is the signalling conversion table for the TTC2M card. The In-use state
corresponds to the signalling values that appear in that row. The TTC2M card Idle
state corresponds to the signalling values with the asterisk.
20.12-8
(400)

NNP 95-2035-01-00-B

Table 20.12-3: Signalling Conversion Table for the TTC2M Card

TTC2M Card
T1
T1 ESF
E1
E&M
In-use = 0
11
1111
1010
Idle
Idle = 1
00*
01
10
0000*
0001
0010
0011
0100
0101
0110
0111
1000
1001
1010
1011
1100
1101
1110
0000
0001
0010
0011
0100
0101
0110
0111
1000
1001
1011
1100
1101*
1110
1111
Seized*
Figure 20.12-2 shows the position of the framing and signalling bits in TS0.
Figure 20.12-2: TS0 Bits for the TTC2M Card
TS0
Bits
MF
9423
Table 20.12-4, shows the TTC2M card signalling bits in TS0 in an eight frame
multiframe.
(400)
20.12-9


NNP 95-2035-01-00-B
Table 20.12-4: TTC2M Card Frame Format

Multiframe
Number
Bits
1
A1
A2
A3
A4
A5
A6
A7
A8
A9
A10
A11
A12
A13
A14
A15
A16
A17
A18
A19
A20
A21
A22
A23
A24
A25
A26
A27
A28
A29
A30
F = 8 kHz frame alignment signal bit (first bit of TS0)

S = Alarm indication signal bit (third bit of TS0)
A1 to A30 = The signal bit associated with the corresponding TTC2M card channels.
X = Bits ignored on the receive path and are set to 0
20.12-10
(400)

NNP 95-2035-01-00-B
20.13
20.13 Inversion
Inversion
This chapter explains how to configure inversion for PRI card circuits.
20.13.1
Understanding Inversion for PRI Cards

You can configure inversion for any primary rate circuit. All information on
non-compressed circuits connected to a primary rate circuit can be either inverted
(VOICE) or not inverted (DATA).
If the connected circuits are voice circuits, the information being passed over the
primary rate circuits should be inverted when there is a requirement to convert
between the ITU-T alternate digit inversion PCM output code format (generally
used on 2.048 Mb/s E1 links) and the AT&T true-sign inverted magnitude PCM
output code format (generally used on 1.544 Mb/s T1 links).
If the connected circuits are data circuits, the information being passed over the
primary rate circuit does not normally need to be inverted.
For bypass connections (T1_SIG-to-E1_SIG or T1_NoSIG-to-E1_NoSIG), the default
changes on both circuits after you make the connection, so that the information is not
inverted. If the remote circuits are voice circuits, the information should be inverted.
20.13.2
Configuring Inversion of PRI Card Circuits

Configure inversion on a non-compressed circuit connected to a primary rate circuit
as:
Voice for inverted (default)

Data for not inverted
For the TTC2M card, the types of inversion possible on the circuit are listed and
Note
Circuits must be disconnected before changing the inversion configuration;
otherwise this error message appears That circuit is in use. Disconnect it first.
(400)
20.13-1
20.13 Inversion

NNP 95-2035-01-00-B
Table 20.13-1: TTC2M Card Circuit Inversion Types

Inversion Type
Description
Option
None
No inversion applied to the circuit.
NONE
ADI
The odd bits 1, 3, 5 and 7 are inverted. Bit 7 is the most

significant bit.
ADI
Mark
The even bits 0, 2, 4 and 6 are inverted. Bit 0 is the least

significant bit.
MARK
Magnitude
Inversion
All bits are inverted except bit 7.
MAG_INV
To configure inversion of PRI card circuits

CONFIG CIRCUIT <sn-cc> or <sn-l-cc> or <n-cc> FUNCTION DATA/VOICE*
To configure inversion of TTC2M card circuits

CONFIG CIRCUIT <sn-cc> FUNCTION INVERSION
NONE
ADI
MARK
MAG_INV*
SK000747
20.13-2
(400)

NNP 95-2035-01-00-B
20.14

Loopback Detection
This chapter explains how to configure loopback detection for PRI cards.
20.14.1
Understanding Loopback Detection for PRI Cards

A protected circuit is configured with a preferred and a protecting link to the far-end
circuit. When a fault occurs on the preferred link, the connection is switched to the
protecting link. When end-to-end connectivity is re-established over the preferred
link, the circuit is switched from the protecting link back to the preferred link.
The PSTN uses loopbacks to determine the location of the fault. The loopback
detection feature lets the node detect a loopback condition and ensures that the
connection is not switched back to the preferred link until end-to-end connectivity
has been restored.
Note
Optical Extension cards use the same types of loopback detection as the Dual E1
card.
Table 20.14-1 lists the types of loopback detection and identifies the primary rate
cards that support them.
Table 20.14-1: PRI Loopback Detection
T1 Card
Dual T1
Card
Dual T1-2
Card
Dual E1-2
Card
E1, Dual E1,

X.21 or V.35
PRI Cards
MPA Card
Type
CPSS
TS24 (1)
On-fault
In-band signature
Notes
1. This parameter is not available on Dual T1 or Dual T1-2 cards in 3664 MainStreet systems.
(400)
20.14-1


NNP 95-2035-01-00-B
Figure 20.14-1 shows loopback detection on a primary rate link.

1. During normal operation, the connection is established over the preferred path.
2. If a fault occurs, a framing alarm is generated at both ends of the connection, and
the connection is switched to the protecting path as long as trunk conditioning
is in effect.
3. The PSTN initiates loopbacks to isolate the fault. When the node detects the
loopback condition, the framing alarm is cleared and a loopback detected alarm
is raised. The node maintains the end-to-end connection over the protecting
path.
4. When the fault has been repaired, the PSTN removes the loopbacks. When the
node detects that the loopback condition has been removed and that end-to-end
connectivity has been restored, the connection is switched back to the preferred
path.
Note
If the loopback condition is removed, but end-to-end connectivity has not been
restored (the fault has not been repaired), another framing alarm is generated, and
the connection is maintained over the protecting path.
Figure 20.14-1: Loopback Detection

MainStreet
node
Preferred
path
PRI
MainStreet
node
PRI
MainStreet
node
PRI
PRI
PRI
MainStreet
node
PRI
Preferred
path
PRI
MainStreet
node
PRI
PSTN
PSTN
PRI
PRI
2.A fault occurs in the PSTN. A Framing Alarm

is raised at each end, and the circuit is
switched over the protected path.
MainStreet
node
PRI
MainStreet
node
PSTN
Protected
path
1.Normal operation.
MainStreet
node
Fault
PRI
PSTN
PRI
Framing alarm
raised
PRI
3.PSTN loops back circuits on the preferred path.

Framing Alarm condition no longer present and
loopback detected at each node.
PRI
PRI
Protected
path
4.When the fault is repaired and the loopback is
removed, the circuit is switched over the
preferred path.
5198
20.14-2
(400)

NNP 95-2035-01-00-B
20.14.2

CPSS Loopback Detection for PRI Cards

The node monitors the CPSS connection to determine when the protected circuit can
be switched from the protecting path to the preferred path. The circuit is not
switched until:
the framing alarm has been cleared

there are no loopbacks detected
CPSS connectivity has resumed
Table 20.14-2 shows how CPSS connections can be made.
Table 20.14-2: PRI CPSS Connections
Card Types
CPSS Connections
Dual E1-to-Dual E1
DS0
Dual T1-to-Dual T1
DS0
E1-to-Dual E1
DS0
E1-to-E1
TS0 or DS0
T1-to-Dual T1
DS0
T1-to-T1
FDL or DS0
V.35 PRI-to-V.35 PRI
TS0 or DS0
X.21 PRI-to-X.21 PRI
TS0 or DS0
MPA card:
X.21-to-X.21
V.35-to-V.35
RS-449-to-RS-449
RS-530-A-to-RS-530-A
TS0
TS0
TS0
TS0
Table 20.14-3 lists CPSS resources that are supported by the PRI cards and the
required connection types needed.
Table 20.14-3: CPSS Resources and Connection Types
CPSS Resources
Connection Types
Dedicated, shared
Control card
DCP
DCP CPSS connection
FRE, FRS and PE
Circuits configured for CPSS
See chapter 17.6 for more information on CPSS connections.
(400)
20.14-3


NNP 95-2035-01-00-B
Warning
CPSS connections are live circuits and must be added to an active network carefully
to avoid routing problems.
Establish a CPSS connection over each link in the end-to-end connection. The node
monitors the CPSS channel for a loopback condition if service on the link is
disrupted.
To establish CPSS loopback detection for PRI cards

1.
Establish a CPSS connection between the end cards.
2.
Configure CPSS loopback detection on the PRI cards.

Figure 20.14-2 shows the CPSS loopback detection path.
Figure 20.14-2: CPSS Loopback Detection Path
Primary rate
link
Primary rate
link
PSTN
CPSS
resource
CPSS
resource
6071
20.14.3
Establishing TS24 Loopback Detection for PRI Cards

To establish TS24 loopback detection, equip each endpoint with a DRM (Dual T1-2)
or TSM (Dual T1) and configure the endpoints for TS24 signalling. The node
monitors TS24 for a loopback condition if service on the link is disrupted.
1.
Establish a connection between the end cards.
2.
Configure TS24 loopback detection on end cards.
3.
Enable loopback detection trunk conditioning on end cards (default).

Figure 20.14-3 shows the TS24 loopback detection path using Dual T1-2 cards.
20.14-4
(400)

NNP 95-2035-01-00-B

Figure 20.14-3: TS24 Loopback Detection Path
Primary rate link
Primary rate link

PSTN
DRM
DRM
6073
Note
Tandem nodes that are physically linked together must differ in at least one of the
identification pattern elements (for example, node, slot or link number) to prevent
the false detection of loopbacks (see chapter 17.6). Loopbacks may be falsely
detected in the rare situation where both ends of a link have the same link, slot and
node numbers, but different domain numbers.
20.14.4
Establishing On-fault Loopback Detection for PRI Cards

On-fault loopback detection does not require a dedicated channel. When a fault
occurs, the node transmits an identification pattern that includes the node address,
slot number and link number. The pattern remains on the link until all faults are
cleared and no loopback is present. The node detects this pattern only when the link
is looped back.
1.
Establish a connection between the end cards.
2.
Configure on-fault loopback detection on the end cards.
3.
Enable loopback detection trunk conditioning on the end cards (default).

Figure 20.14-4 shows the on-fault loopback detection path.
Figure 20.14-4: On-fault Loopback Detection Path
Remote or local fault
Primary rate link
Identification
pattern
PSTN
Pattern
detector
Pattern
detector
Identification
pattern
6072
(400)
20.14-5


NNP 95-2035-01-00-B
Caution
If a fault occurs and a loopback is applied to the link before a Red alarm is declared,
the loopback is not detected and the circuit will not switch to the protecting link.
20.14.5
Establishing In-band Signature Loopback Detection

When in-band signature loopback detection is enabled on the MPA card, a unique
signature pattern is transmitted as part of the framing pattern in the TS0 supervisory
channel. Any loopback applied to the circuit causes the return of that signature
pattern. The MPA card recognizes the returned signature pattern in the framing and
raises an alarm. Every node in the MainStreet network must have a unique CPSS
address or else unnecessary alarms may be generated. The alarms are generated
because the signature pattern is derived from the CPSS address.
Note
In-band signature loopback detection is only available if the MPA card interface uses
HCM3, HCM4 or HCM5 framing. See chapter 20.20 for more information.
20.14.6
Configuring Loopback Detection for PRI Cards

Configure loopback detection as:
NONE
VIA_CPSS
VIA_TS24
ON_FAULT
IN_BAND
Configure fault classes for PRI cards according to Table 20.14-1. Only one method of
loopback detection can be enabled on a link at a time.
Figure 20.14-5 shows a typical loopback detection display.
20.14-6
(400)

NNP 95-2035-01-00-B

Figure 20.14-5: NMTI Display for Loopback Detection

3600 MainStreet
1117-H1-00
Installed
Status
Empty
Empty
Configured
A1-A DUAL2_T1
T1.403 messaging mode:

54016 messaging mode:
Toronto:A
Alarms:1
Name
11-May-1997
8:35a
Options
JB7 D4
DISABLED
DISABLED
Line length:
SHORT
Loopback detection:
NONE
Accept. err sec/24 hr: 86 (99.900%)
Link avail. monitoring: DISABLED
SES Limit BER Exceeding:1E-3
Link Signalling Mode:
RBS
Digital Service Level: DS0
DS1 Fault Signal:
NONE
CONFIG SLOT 1-A OPTIONS FAULT_HNDL LPBK_DETEC
16-
2-VIA_CPSS
7-
3-VIA_TS24
8-CANCEL
4-ON_FAULT
9-QUIT
50-
To configure loopback detection on the Dual E1-2 card

CONFIG SLOT <sn-l> OPTIONS FAULT_HNDL LPBK_DETEC
NONE*
VIA_CPSS
ON_FAULT
SK000707
To configure loopback detection on the MPA card

CONFIG SLOT <sn-l> OPTIONS MORE FAULT_HNDL LPBK_DETECT
NONE*
VIA_CPSS
IN_BAND
SK000694
(400)
20.14-7


NNP 95-2035-01-00-B
To configure loopback detection for other PRI cards

Warning
Disabling trunk conditioning on Dual T1 and Dual T1-2 cards links affects the TS24
and on-fault loopback detection. When trunk conditioning for loopbacks is disabled,
circuits do not switch to their alternative link even if the loopback is detected.
CONFIG SLOT <sn> or <sn-l> or <sn-l>
OPTIONS
OPTIONS
MORE
FAULT_HNDL
LPBK_DETEC
LPBK_DETEC
NONE VIA_CPSS VIA_TS24
NONE
VIA_CPSS
VIA_TS24 ON_FAULT
SK000083
where
the first sn-l indicates a Dual T1 card
the second sn-l indicates a Dual T1-2 card
Note
The VIA_CPSS and VIA_TS24 options apply only to Dual T1 and Dual T1-2 cards.
The ON_FAULT option applies only to Dual T1-2 cards.
20.14-8
(400)

NNP 95-2035-01-00-B
20.15

Super-rate Circuits
This chapter introduces super-rate circuits for PRI cards and explains how to:
20.15.1
configure and deconfigure a tandem super-rate circuit

configure and deconfigure a unidirectional super-rate circuit
connect and disconnect tandem super-rate circuits
connect and disconnect a super-rate DCC and a primary rate link
specify a super-rate protecting circuit
connect and disconnect a unidirectional super-rate broadcast circuit
Understanding Super-rate Circuits for PRI Cards

You can configure super-rate circuits for all PRI cards except the TTC2M card. The
T1 and E1 cards in certain system configurations require an SAM to support
super-rate circuits, see Technical Overview, section 5.3.4 for information.
Super-rate speeds are interface speeds that are greater than 64 kb/s. When a
super-rate circuit is connected to a primary rate link, it fills more than one DS0
(64 kb/s circuit).
Primary rate cards and X.21, V.35 and RS-422 DCC circuits support super-rate
speeds. Single T1 and E1 cards require a SAM to carry super-rate data. Dual T1 and
Dual E1 cards support super-rate speeds on link A when installed in a single
bandwidth slot, and on links A and B when the card is installed in a double
bandwidth slot.
The following connections are valid:
Super-rate circuits on T1 links can be connected to E1 links

Super-rate connections can be made between PRI cards
Super-rate connections can be made between DCC and PRI cards
The types of super-rate connection are:
bidirectional tandem
unidirectional tandem
unidirectional tandem broadcast
There are two configurable super-rate connection options:
preferred (the set of DS0s that you prefer for the data transmission)
level 2 (the set of DS0s used to protect the preferred tandem super-rate)
(400)
20.15-1


NNP 95-2035-01-00-B
Note
A DS0 may be involved in a level 2 tandem super-rate connection without being
involved in a preferred tandem super-rate connection.
Unidirectional tandem super-rate connections do not support level 2 configuration.
The DS0s used in a super-rate configuration are:
one master circuit

one or more slave circuits
The master circuit is the first DS0 used; the slave circuits are the DS0s that follow.
Contiguous super-rate circuits

A contiguous super-rate circuit uses the master circuit as a starting point and then
takes the slave circuits from DS0s that immediately follow the master circuit DS0.
When you enter the master circuit, the system reserves the required number of slave
circuits from the DS0s immediately following the master circuit.
Non-contiguous super-rate circuits

A non-contiguous super-rate circuit allows the use of non-consecutive DS0s. To
configure a non-contiguous super-rate, you make a list of circuits using the
<Return> key and a range of circuits using the colon (:) key. For example, a 512 kb/s
super-rate circuit needs a total of 8 DS0s (64 kb/s circuits) that you enter as:
<1> <3> <5:10>
You must enter the DS0s from the lowest to the highest number. If you try to enter
the circuits in a non-ascending order, the system displays the message Circuits
must be specified in ascending order.
For E1 links with 31_CHAN or X21_NTU configured, circuit 31 is between circuits
15 and 16 in time, but you still specify it at the end of the list. For example, a valid
list is:
<1> <14:15> <17> <31>
A valid list of five DS0s is:
<14:17> , which is equivalent to <14> <15> <16> <17> <31>
If circuit 31 is the master on an E1 link with 31_CHAN configured, it becomes the
only case in which the master circuit is the last, not the first, circuit in the list. Circuit
31 cannot be used for super-rate circuits on an E1 link with CCS configured.
In a unidirectional connection, a circuit can be part of one super-rate group as a
source and part of another super-rate group as a destination; you can configure the
source and destination super-rate groups for different speeds. For example, circuits
1, 3, 5 and 7 can be a source super-rate group at 256 kb/s and circuits 1 to 6 a
destination super-rate group at 384 kb/s.
20.15-2
(400)

NNP 95-2035-01-00-B

If you try to enter a circuit that is a master in another list, the system displays the
message Warning. That circuit is already a super-rate master. If you try to enter a
circuit that is a slave in another list, the system displays the message Warning. That
circuit is already a super-rate slave.
Equidistant super-rate circuits

An equidistant super-rate circuit spaces the DS0s evenly over the entire link after the
bandwidth is set. E1 and E3 cards with CAS- and CCS-framing formats support
equidistant super-rate circuits. Figure 20.15-1 shows the equidistant super-rate
format for each bandwidth.
Figure 20.15-1: Equidistant Super-rate DS0s on E1 Links
Bandwidth
(DS0s)
16
30
Bandwidth
(DS0s)
Bandwidth
(kb/s)
128
256
512
1024
1920
Bandwidth
(kb/s)
Circuit
Number
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
31 (1)
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
Timeslots
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
0
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
Note
1 Circuit 31 is only available when the link is configured for 31_CHAN, X.21_NTU or CCS framing types.
Circuit 31 cannot be involved in a super-rate configuration on CCS-configured links.
9066
(400)
20.15-3


NNP 95-2035-01-00-B
Note
E1 cards in 3664 MainStreet systems do not support equidistant super-rate circuits.
Delay equalization
The system checks delay equalization for connections between any two super-rate
types. If unequal delays exist, the connection is not allowed.
Protecting super-rate circuits

A super-rate circuit can be protected by:
a tandem super-rate connection configured as level 2

a super-rate connection running at the same speed
multiple DS0s that normally carry voice or data connections
Unidirectional connections cannot be protected, as there is no level 2 configuration.
If the super-rate circuit is protected by multiple DS0s and the preferred connection
of the super-rate circuit fails, it is connected to the protecting DS0s. The voice and
data circuits previously connected to the DS0s are disconnected, unless they are
protected by other circuits. DS0s that are part of a voice compression subframe
cannot be used as protecting circuits for super-rate circuits. This protecting
connection is blocked.
Super-rate circuits can protect voice or data connections. If the preferred connection
is broken, the entire super-rate connection is broken and the protecting DS0 is
connected to the voice or data circuit.
20.15.2
Configuring Super-rate Circuits for PRI Cards

To configure the super-rate circuit, you enter the circuit identifier of the master DS0,
select NUM_CIRCS, and configure the type of tandem super-rate as:
PREFERRED for preferred

LEVEL_2 for level 2
Then you enter the number of DS0s in the super-rate bundle. The valid range for the
number depends on which timeslot in the primary rate link is occupied by the
master DS0 in the super-rate connection. If there are not enough timeslots in the
primary rate link for the number of circuits in the super-rate connection, the system
displays a warning.
20.15-4
(400)

NNP 95-2035-01-00-B

Note
A DS0 may be involved in a preferred tandem super-rate at one speed and a level 2
tandem super-rate connection at another speed. A DS0 may be involved in a level 2
tandem super-rate connection without being involved in a preferred tandem
super-rate connection.
After you enter the number of DS0s, you must configure the super-rate format as:
CONTIGUOUS for a contiguous super-rate circuit

NON_CONTIG for non-contiguous super-rate circuit
EQUIDIST for equidistant super-rate circuits (on CAS- or CCS-framed E1 and E3
circuits only)
For non-contiguous circuits, you must enter a list of the DS0 in the super-rate
bundle.
For Dual E1 circuits, you can create a unidirectional tandem super-rate circuit by
specifying whether you a defining a source circuit (SRC_N_CIRC) or a destination
circuit (DST_N_CIRC).
After you have configured the first super-rate bundle, you must repeat the process
for the connecting tandem super-rate circuit, entering the same number of circuits as
for the first bundle.
Note
To deconfigure the super-rate bundle, enter 0 or 1 for the number of DS0s in the
circuit. (You must disconnect the circuit before you deconfigure it.)
(400)
20.15-5


NNP 95-2035-01-00-B
To configure a bidirectional tandem super-rate circuit

CONFIG CIRCUIT <sn-cc> or <sn-l-cc> or <E3id-E1id-cc> FUNCTION
NUM_CIRCS
PREFERRED
LEVEL_2
<number_ of _circuits>
CONTIGUOUS NON_CONTIG
EQUIDIST
<list _of _circuits>

SK000084
where
number_of_circuits is the number of DS0s in the super-rate bundle
list_of_circuits is a list of individual DS0s or ranges of DS0s, separated by returns (for example, <n1>
<n2> <n3:n4> specifies that the bundle includes individual DS0s n1 and n2 and the range of DS0s
between n3 and n4)
To configure a unidirectional tandem super-rate circuit

CONFIG CIRCUIT <sn-l-cc> FUNCTION MORE
SRC_N_CIRC
DST_N_CIRC
<number_of_circuits>
CONTIGUOUS
NON_CONTIG
EQUIDIST
<list_of_circuits>
SK000085
where
between n3 and n4)
20.15-6
(400)

NNP 95-2035-01-00-B
20.15.3

Connecting Tandem Super-rate Circuits

After you have configured both the tandem super-rate circuits with the same
bandwidth, you can connect them. As well as connecting two super-rate DS0s, you
can connect a super-rate DCC circuit to a primary rate link. When you connect a
super-rate circuit on a DCC to a primary rate link, you have to configure only the
number of circuits for a non-contiguous primary rate-to-DCC connection. The DCC
connections apply to bidirectional super-rate circuits and cannot be used with
unidirectional super-rate circuits. When you connect a unidirectional super-rate
bundle, you must select the ONE_WAY_TO softkey.
Circuits involved in a one-way connection must be configured in unidirectional
super-rate groups with the same bandwidth before the connection is made (see the
procedure To configure a unidirectional tandem super-rate circuit). Groups may
be contiguous, non-contiguous or equidistant. All circuits must be configured with
the same signalling type and the same fault signalling. Out-of-service fault
signalling is not supported.
You can specify a super-rate protecting connection if you have configured the
super-rate bundles as level 2 circuits. Using the PROT_BY softkey, you can enter the
first circuit in the connection as any circuit in the super-rate connection, and the
second, protecting, circuit as the master DS0 in a circuit configured as level 2.
(Alternatively, you can use the PROTECTING softkey and reverse the circuit
identifiers.)
Note
If the protecting circuit is a tandem super-rate connection, you must configure it as
a level 2 tandem super-rate connection.
When a protecting primary rate super-rate circuit is disconnected, the timeslots
involved in the protecting super-rate connection return to normal operation and the
value for the number of circuits reverts to 0. To re-establish a super-rate connection
using these timeslots, you must re-enter the configuration.
DS0s that are part of a voice compression subframe cannot be used as protecting
circuits for a super-rate circuit. The system blocks the protecting connection.
If the protecting circuit involves any DS0s used in a super-rate connection at the
preferred level, the system breaks the entire super-rate connection when you
connect the protecting circuit.
Unidirectional connections cannot be protected; there is no level 2 configuration.
To disconnect a super-rate connection, you select the DISCONNECT softkey and

specify the circuit identifier of the master DS0 in the super-rate bundle (or the source
identifier in a unidirectional E1 connection). When the super-rate circuit is
disconnected, the timeslots previously involved in the super-rate connection return
to normal operation. The number of circuits [NUM_CIRCS] reverts to 0 for
bidirectional circuits and the number of both the source circuits [SRC_CIRCS] and
the destination circuits [DST_CIRCS] reverts to 0 for unidirectional circuits. To
re-establish a super-rate connection using these timeslots, you must re-enter the
value for the number of circuits on both primary rate links.
(400)
20.15-7


NNP 95-2035-01-00-B
To connect tandem super-rate circuits

CONFIG CONNECT <x-sn-cc> or <x-sn-l-cc> or <E3id-E1id-cc>
TO_CIRCUIT
PROT_BY
PROTECTING
MORE
DISCONNECT
ONE_WAY_TO
PREFERRED PROTECTION
or <E3id-E1id-cc>
<x-sn-l-cc> or
<E3id-E1id-cc>
SK000086
where
the first x-sn-cc or x-sn-l-cc or E3id-E1id-cc is the master DS0 of the first super-rate bundle, or the source
circuit identifier in a unidirectional connection, or the super-rate DCC circuit identifier in a
DCC-to-primary rate connection
the second x-sn-cc or x-sn-l-cc or E3id-E1id-cc is the master DS0 of the second super-rate bundle, or the
destination identifier in a unidirectional connection, or the primary rate DS0 in a DCC-to-primary rate
connection
Note
If any of the circuits carry CPSS or the source and destination circuits do not have
the same amount of available bandwidth, the system displays the message Those
circuits cannot be connected.
When cross-connecting more than one super-rate circuit to a primary rate link on a
Dual T1 card, connect them in descending bandwidth size, beginning with the one
that occupies the most bandwidth.
Network Manager rerouting of some super-rate connections involving single T1 or
E1 and Dual T1 or E1 cards (single card-to-single card and single card-to-dual card
connections) may not succeed. The system is unable to perform delay equalization
and the connection is blocked. The new super-rate connection may be violating the
rule that connections be made in descending bandwidth order. The 4602 MainStreet
Intelligent NetworkStation or MainStreetXpress 46020 Network Manager puts the
path in a Waiting for Repairs state.
To configure a DCC circuit for super-rate operation, see chapter 22.3.
20.15.4
Connecting Unidirectional Super-rate Broadcast Circuits

A broadcast connection is a unidirectional connection with more than one
destination circuit, called broadcast destinations. All broadcast destinations receive
the identical signal from the broadcast source. Unidirectional super-rate broadcast
connections are supported on all PRI cards, except Dual T1 and Dual E1 Cards using
a voice compression module.
20.15-8
(400)

NNP 95-2035-01-00-B

Circuits involved in a broadcast connection must be configured in unidirectional

super-rate groups with the same bandwidth before the connection is made (see the
procedure To configure a unidirectional tandem super-rate circuit). Groups may
be contiguous, non-contiguous or equidistant. All circuits must be configured with
the same signalling type and the same fault signalling. Out-of-service fault
signalling is not supported.
Note
Unidirectional super-rate broadcast connections cannot be protected.
To connect the unidirectional super-rate broadcast source

To connect the broadcast source to the first broadcast destination, enter:
CONFIG CONNECT <x-sn-cc> or <x-sn-l-cc> or <E3id-E1id-cc> MORE
BROADCAST <x-sn-l-cc> or <E3id-E1id-cc>
where
circuit identifier in a unidirectional connection
the second x-sn-l-cc or E3id-E1id-cc the master DS0 of the second super-rate bundle, or the destination
identifier in a unidirectional connection
Note
There is no limit to the number of broadcast sources that can be configured.
To add multiple broadcast destinations to the super-rate broadcast circuit

Broadcast destinations can be added without affecting the signal being sent to the
connected broadcast destinations. Up to 250 broadcast destinations can be connected
to a single broadcast source.
Once the broadcast source is connected to the first broadcast destination, to add
more broadcast destinations enter:
ADD_BCAST <x-sn-l-cc> or <E3id-E1id-cc>
where
circuit identifier in a unidirectional connection
the second x-sn-l-cc or E3id-E1id-cc the master DS0 of the second super-rate bundle, or the destination
(400)
20.15-9


NNP 95-2035-01-00-B
To disconnect the unidirectional super-rate broadcast connection

To disconnect a super-rate broadcast connection, select the DISCONNECT softkey
and specify the circuit identifier of the master DS0 in the super-rate bundle (or the
source identifier in a unidirectional E1 connection) of the broadcast source. The
unidirectional super-rate group is dissolved.
CONFIG CONNECT <x-sn-cc> or <x-sn-l-cc> or <E3id-E1id-cc> DISCONNECT
where
x-sn-cc or x-sn-l-cc or E3id-E1id-cc is the master DS0 of the first super-rate bundle, or the source circuit
When the super-rate broadcast circuit is disconnected, the timeslots previously

involved in the super-rate connection return to normal operation. The number of
source circuits [SRC_CIRCS] and destination circuits [DST_CIRCS] reverts to 0. To
re-establish a super-rate connection using these timeslots, you must re-enter the
value for the number of circuits on both primary rate links.
To disconnect a broadcast destination from the broadcast connection

Broadcast destinations can be removed without affecting the signal being sent to the
connected broadcast destinations. If all broadcast destinations are removed from the
broadcast connection, the broadcast circuit is removed.
RMV_BCAST <x-sn-l-cc> or <E3id-E1id-cc>
where
the first x-sn-cc or x-sn-l-cc or E3id-E1id-cc is the broadcast source master DS0 of the first super-rate bundle,
or the source circuit identifier in a unidirectional connection
the second x-sn-l-cc or E3id-E1id-cc is the broadcast source master DS0 of the second super-rate bundle, or
the destination identifier in a unidirectional connection
To view all broadcast destinations

The number of actual broadcast destinations connected may exceed the number of
lines displayed on the NMTI screen. To view the broadcast destinations that are not
currently displayed on the NMTI screen, enter:
PREV_BCAST or NEXT_BCAST
where
x-sn-cc or x-sn-l-cc or E3id-E1id-cc is the master DS0 of the first super-rate bundle, or the source circuit
20.15-10
(400)

NNP 95-2035-01-00-B
20.16

24 DS0 Super-rate Circuit

Protection
This chapter introduces 24 DS0 super-rate connections for the Dual T1-2 card and
explains how to configure the parameter.
20.16.1
Understanding 24 DS0 Super-rate Circuit Protection for

Dual T1-2 Cards
A 24 DS0 super-rate circuit consists of 24 consecutive DS0s that do not carry any
signalling information. You can configure the Dual T1-2 card links to support 24 DS0
super-rate circuits.
A 24 DS0 super-rate connection can be protected by another 24 DS0 super-rate
connection. If the first connection fails, the second connection takes over. When the
original path recovers, the second circuit is disconnected and the original connection
is restored.
The Dual T1-2 card uses TS24 framing fault signalling to notify the endpoint
connections when a fault has occurred on the preferred link.
Note
Dual T1-2 cards in 3664 MainStreet systems do not support 24 DS0 super-rate
circuits.
20.16.2
TS24 Frame Fault Signalling

The following subsections describe TS24 frame fault signalling.
Normal operation
Figure 20.16-1 shows a typical connection across four nodes. During normal
operation, the connection is maintained from the access equipment, across the
tandem nodes to the network-side endpoint node.
(400)
20.16-1


NNP 95-2035-01-00-B
TS24 frame fault signalling

TS24 frame fault signalling notifies the endpoint cards when a fault occurs on the
network connection. The RAPID protection switch occurs when the endpoint 24 DS0
super-rate circuit is disconnected from the 24 DS0 super-rate circuit configured for
access in the endpoint node.
Figure 20.16-1 shows how TS24 frame fault signalling notifies the endpoint cards
when a fault occurs on the connection, and how a RAPID switch routes the 24 DS0
super-rate connection to a protecting circuit and an alternative path.
Figure 20.16-1: 24 DS0 Super-rate Connection RAPID Switch to an Alternative Path
MainStreet node 200

Trunk
conditioning
6
24 DS0
Access
equip't Normal SR
MainStreet node 300
TS24
Link failure
TS24
trunk
No trunk
TS24 framing
Trunk
1-way
conditioning TS24 Framing conditioning Red
alarm
Yellow conditioning
Alarm
alarm
1
5
4
4
3
alarm 3
24 DS0
24 DS0
24 DS0
24 DS0
24 DS0
SR
SR
SR
SR
T1
T1
24 DS0
SR
24 DS0
tandem
access
tandem
tandem
SR
tandem T1
SR Normal
Normal
2
access
Dual
Yellow Dual
T1-2
signal T1-2
link
link
7
Level 2 24 DS0
connection
SR
MainStreet node 100
Normal
Normal
T1
Normal
Alternative
Alternative
Normal
24 DS0
SR
24 DS0
SR
T1
24 DS0
SR
24 DS0
SR
Level 2
24 DS0
connection
SR
T1
MainStreet node 400
Normal
Normal
5980
Access and Tandem fault signalling

The node must be configured for either Access or Tandem fault signalling. Access
TS24 framing is used at endpoint nodes or when a change in fault is needed. Tandem
TS24 framing is used in tandem nodes to pass the incoming fault signal through
without intervention from the node. Alarms indication is needed only on the
preferred path.
The actions performed by a 24 DS0 super-rate circuit in the end-to-end connection
are determined by the location of the T1 link in relation to the fault.
20.16-2
(400)

NNP 95-2035-01-00-B

The following events are shown in Figure 20.16-1.

1. A link failure occurs in one direction, causing Node 300 to declare a Red Alarm.
2. Node 300 transmits a Yellow signal in the direction of the fault to Node 400.
Node 400 declares a Yellow Alarm.
3. Both nodes do trunk conditioning by disconnecting mate circuits.
4. TS24 Framing is transmitted out the T1 link as fault signalling to indicate OOS
alarm upstream.
Node 200 detects TS24 Framing and declares a TS24 Frame OOS alarm. No trunk
conditioning takes place because the node is configured as tandem.
TS24 Framing passes transparently through to Node 100.
5. Node 100 detects TS24 Framing and declares a TS24 Frame OOS alarm.
6. Since Node 100 is configured for access fault signalling, trunk conditioning takes
place. The node disconnects the 24 DS0 super-rate mate circuit leading to the
access equipment.
7. A RAPID switch occurs and the 24 DS0 super-rate circuit is routed to the
protecting circuit, which carries the data to an alternative path. A normal signal
(no faults) is transmitted.
Note
To do TS24 frame fault signalling, the Dual T1-2 cards on the preferred path must be
equipped with DRMs and be configured to support TS24 signalling.
Fault recovery
When the fault is repaired, the adjacent nodes raise Alarm Cleared signals, and the
affected link is put back in service. If the adjacent node is an end node, the circuit is
disconnected from the protecting connection and switched back over the preferred
connection.
The TS24 framing signal is no longer transmitted downstream. When an endpoint
node determines that the TS24 framing signal is no longer being received, a TS24
Frame OOS Cleared alarm is generated and the 24 DS0 super-rate circuit is switched
back over the preferred connection.
(400)
20.16-3

20.16.3

NNP 95-2035-01-00-B
Configuring 24 DS0 Circuit Protection for Dual T1-2 Cards

The following subsections explain how to configure 24 DS0 circuit protection.
1.
Configure the DRM for TS24 signalling.
2.
Configure the link:
3.
for RBS signalling mode (SIG_MODE RBS)

to support 24 DS0 connections (DS_LEVEL 24_DS0)
for two-way trunk conditioning (TRUNK_COND TWO_WAY)
for TS24 frame fault signalling (FAULT_SIG TS24_FRAME) and access or
tandem fault signalling
Make the connections. You connect two super-rate circuits by specifying their
master circuits (see chapter 20.15). For more information about alarm times, see
Maintenance, section 35.4.1.
Caution
All links involved in the connection must be configured for 24 DS0 super-rate
connections and two-way trunk conditioning. If one-way trunk conditioning is
configured, only one end of the network will RAPID switch and data loss will occur.
To configure the DRM for TS24 signalling

CONFIG SLOT <sn> OPTIONS APP_MOD DRM TS24_SIG
To configure the link

CONFIG SLOT <sn-l> OPTIONS
PHYSICAL
FAULT_HNDL
MORE
SIG_MODE
DS_LEVEL
RBS
DS0*/24_DS0
FAULT_SIG
TRUNK_COND
ONE_WAY/TWO_WAY*
TS24_FRAME
ACCESS
TANDEM
SK000087
20.16-4
(400)

NNP 95-2035-01-00-B

Note
Selecting 24_DS0 configures all 24 DS0s on the link with RBS off and non-inverted
data transmission on.
To connect two 24 DS0 super-rate circuits

CONFIG CONNECT <sn-l-cc> TO_CIRCUIT <sn-l-cc>
(400)
20.16-5

NNP 95-2035-01-00-B
20.17

Link Monitoring and Error

Thresholds
This chapter describes link availability performance monitoring configuration for
Dual T1, Dual T1-2 and Dual E1-2 cards, as well as errored-second checking for
Dual T1, Dual T1-2 and MPA cards. The following topics are documented in this
chapter:
enable and disable link availability monitoring

set an errored seconds threshold
view thresholds for Dual E1-2 card link monitoring
set the SES limit for the Dual T1 and Dual T1-2 cards
set the SES and DGM limits for the MPA card
To configure the SES limit for Dual E1 or Dual E1-2 cards, see section 20.18.4.
20.17.1
Understanding Link Monitoring and Error Thresholds

Link monitoring provides a mechanism to indicate when the number of errors
detected on a link has exceeded a configurable threshold. The system generates an
alarm in the diagnostics alarm queue when a threshold is exceeded.
Dual T1 and Dual T1-2 card statistics monitored on the link are checked over a 24-h
period and alarms are reported only once every 24-h period. The Dual E1-2 card can
monitor the link for threshold crossings during the current 15-min interval, over a
24-h period, or for both simultaneously. For the Dual E1-2 card, an alarm is reported
at the end of every 15-min or 24-h period that contained an exceeded threshold.
Note
The system does not automatically take the link out of service when a link
monitoring threshold is exceeded. You must determine whether the link should be
physically busied out or removed from service.
Threshold monitoring for the following statistics can be configured on each link of
the Dual T1 and Dual T1-2 card:
errored seconds
failed seconds
severely errored seconds
Monitoring of link statistics for Dual T1 and Dual T1-2 cards is enabled or disabled
for the entire link.
(400)
20.17-1


NNP 95-2035-01-00-B
The following Dual E1-2 card statistics can be configured for threshold monitoring
over the 15-min interval and the 24-h period:
errored seconds
bursty error seconds
severely errored seconds
unavailable seconds
control slip seconds
degraded minutes
You can configure the SES limit for each of the links on the Dual T1 and Dual T1-2
cards. On the MPA card, you can configure both the SES and DGM limits for each
link.
20.17.2
Configuring Link Monitoring for Dual T1 and Dual T1-2

Cards
The Dual T1 and Dual T1-2 cards monitor the link for errored second, SES and failed
seconds. An alarm is generated if any of these statistics exceed the configured
threshold during a 24-h period. The threshold can be configured from 1 to 255
errored seconds within a 24-h period.
For Dual T1 and Dual T1-2 cards, you can configure the SES threshold for the link as:
320 or 1544 error events per second (default)

101 or 487 error events per second
When link availability is enabled, the node waits 24 h before raising an alarm. The
24-h waiting period provides time for the link to stabilize after commissioning. The
node ignores error events that take place during this 24-h period.
After the initial 24-h period, the node monitors the link at 15-min intervals and
compares the total cumulative error events of the current 24-h period to the
configured threshold.
If the total cumulative error events exceeds the configured threshold, the node
generates an alarm. The node then waits another 24 h before resuming link
monitoring.
Figure 20.17-1 shows the configuration link options on a typical display. The screen
shows the current available seconds threshold and the corresponding link
availability percentage, and indicates whether the parameter is enabled or disabled.
20.17-2
(400)

NNP 95-2035-01-00-B

Figure 20.17-1: Configuration Link Options Display

3600 MainStreet
1117-H1-00
Installed
Status
Empty
Empty
Configured
A1-A DUAL2_T1
Toronto:A
Alarms:1
Name
11-May-1997
8:35a
Options
JB7 D4
T1.403 messaging mode:

54016 messaging mode:
DISABLED
DISABLED
Line length:
Loopback detection:
Accept. err sec/24 hr:
Link avail. monitoring
SES Limit BER Exceeding:
Link Signalling Mode:
Digital Service Level:
DS1 Fault Signal:
SHORT
NONE
86 (99.900)
DISABLED
1E-3
RBS
DS0
NONE
CONFIG SLOT 1-A OPTIONS
1-PHYSICAL
6-
2-THRESHOLDS
7-MORE
3-FAULT_HNDL
8-CANCEL
4-ISDN
9-QUIT
50-
Errored seconds threshold for links on Dual T1 and Dual T1-2 card
The link must meet a minimum availability percentage over a 24-h period. If the time
that the link is available drops below this percentage because of error events on the
link, you must take the link out of service until it can meet the minimum availability
percentage.
The errored second threshold is the maximum number of unavailable seconds that
the link can experience within a 24-h period and still meet the minimum availability
percentage. Figure 20.17-2 shows the errored second threshold equation.
Figure 20.17-2: Errored Second Threshold Equation
Number of seconds in 24 hours
Threshold (seconds) = 86 400
Minimum availability %
x Number of seconds in 24 hours
100
Minimum availability %
x 86 400
100
9059
The default errored second threshold is 86 seconds, corresponding to a link

availability of 99.9%.
(400)
20.17-3


NNP 95-2035-01-00-B
To configure link monitoring for Dual T1-2 cards

CONFIG SLOT <sn-l> OPTIONS THRESHOLDS
LINK_MON
ENABLE/DISABLE*
SES_LIMIT
ERR_SEC
<threshold>
1E-7
1E-6
5E-6
1E-5
1E-4
1E-3*
SK000088
where threshold is 1 to 255 (86*)
To configure link monitoring for Dual T1 cards

CONFIG SLOT <sn-l> OPTIONS MORE LINK_MON
ENABLE/DISABLE*
ERR_SEC
<threshold>
SK000089
where threshold is 1 to 255 (86*)
20.17.3
Configuring Link Monitoring for Dual E1-2 Cards

The ES, BES, SES, UAS, CSS and DM statistics can be individually enabled or
disabled for link monitoring over 15-min intervals, 24-h periods or both. The
thresholds for each of these statistics are individually configurable.
The Dual E1-2 card automatically starts monitoring the link once a statistic threshold
is entered. The configured statistic thresholds apply to both the local and remote
statistics. Remote monitoring is automatically performed if the E-bits option is
enabled on the card.
If you change the threshold value of a statistic while the Dual E1-2 card is monitoring
the link, the changed threshold value becomes effective immediately. Increasing and
decreasing threshold values during monitoring can cause multiple alarms to be
raised. For example, if you reduce a threshold value during the time period in which
it has already been exceeded, the system generates a second alarm.
20.17-4
(400)

NNP 95-2035-01-00-B

The Dual E1-2 card informs the node when a threshold is crossed and the system
raises an alarm in the diagnostics queue, see chapter 35.3 for information about the
diagnostics queue. If you configure the statistic threshold monitoring over a 15-min
interval, an alarm is raised at the end of each 15-min interval in which the statistic
threshold is exceeded. If you configure the threshold for a 24-h period, only at the
end of the 24-h period is an alarm raised.
Table 20.17-1 lists and describes the link performance monitoring statistics and the
threshold limits for the 24-h period and the current 15-min interval.
Table 20.17-1: Performance Threshold Statistics and Threshold Ranges
Link
Statistic
Description
Threshold Value
Ranges - 24 h
Threshold Value
Ranges - 15 min
ES
The number of errored seconds that must occur before

the system raises the local (or remote) Errored Second
threshold crossing alarm for the configured 15-min or
24-h time period.
1 through 32 767
1 through 900
BES
The number of bursty error seconds that must occur

before the system raises the local (or remote) Bursty
Errored Second threshold crossing alarm for the
configured 15-min or 24-h time period.
1 through 32 767
1 through 900
SES
The number of severely errored seconds that must

occur before the system raises the local (or remote)
Severely Errored Second threshold crossing alarm for
the configured 15-min or 24-h time period.
1 through 32 767
1 through 900
UAS
The number of unavailable seconds that must occur

before the system raises the local (or remote)
Unavailable Second threshold crossing alarm for the
1 through 32 767
1 through 900
CCS
The number of control slip seconds that must occur

before the system raises the local (or remote)
Controlled Slip Second threshold crossing alarm for the
1 through 32 767
1 through 900
DM
The number of degraded minutes that must occur

before the system raises the local (or remote) Degraded
Minutes threshold crossing alarm for the configured
15-min or 24-h time period.
1 through 1440
1 through 15
The system continues to collect quality statistics while performance thresholds are
monitored. The Dual E1-2 card resets the monitored threshold counts to zero if the
cards quality statistics are cleared or the card is reset. If the statistics are cleared after
an alarm has been raised because of a threshold crossing, the card raises the alarm
again when that threshold is crossed a second time.
Figure 20.17-3 shows a link monitoring performance thresholds display. The
configured threshold values for the link statistics are displayed for both the current
15-min and 24-h periods.
(400)
20.17-5


NNP 95-2035-01-00-B
Figure 20.17-3: Dual E1-2 Card Link Monitoring Performance Thresholds Display
3600 MainStreet
Link Quality:
1117-H1-00
Toronto:A
Slot:A2-A
Alarms:1
11-May-1997
8:35a
Status:In Service
Current
Errored seconds:
Bit Error Rate:
Severely errored second:
Unavailable second:
Controlled Slip second:
Degraded Minutes:
34
DISABLED
357
DISABLED
DISABLED
DISABLED
24_HR
DISABLED
DISABLED
1875
DISABLED
DISABLED
DISABLED
QUALITY 2-A OPTIONS THRESHOLDS LINK_MON

1-CURRENT
6-
2-24_HR
7-
38-
49-QUIT
50-
To view link monitoring thresholds

CONFIG <sn-l> OPTIONS THRESHOLDS LINK_MON
To configure link monitoring thresholds

CONFIG SLOT <sn-l> OPTIONS THRESHOLD LINK_ MON
CURRENT
ES_THRESH
BES_THRESH
SES_THRESH
THRESHOLD
UAS_THRESH
CCS_THRESH
24_HR
DM_THRESH
DISABLE
<threshold>
SK000685
20.17-6
(400)

NNP 95-2035-01-00-B

where
threshold is a value from 1 to 900 in all current 15-min interval statistics except degraded minutes. For
degraded minutes, enter a value from 1 to 15.
threshold is a value from 1 to 32 767 in all 24-h period statistics except degraded minutes. For degraded
minutes, enter a value from 1 to 1440.
20.17.4
Configuring SES Limit for Dual T1 and Dual T1-2 Cards

The SES limit is the bit error rate that qualifies an errored second as a severely
errored second. To provide a higher level of link sensitivity, configure the SES
threshold at the slot level for Dual T1 cards or at the link level for Dual T1-2 card.
For links configured as ESF, AT&T Pub. 54016 defines an SES to contain 320 or more
CRC6 error events, or one or more framing errors. For links configured as D4
framing, an SES is declared for 1544 BPV bit errors, or one or more framing errors.
This is equivalent to a severely errored framing event of 2 out of 4 framing bits.
Error-free seconds for T1 links configured as ESF contain no loss of framing or CRC6
error events. Error-free seconds for links configured as D4 contain no BPV error
events or loss of framing.
Table 20.17-2 lists the SES threshold configuration for the T1 links with selected bit
error rate thresholds that correspond to CRC and BPV error events for the Dual T1
and Dual T1-2 cards.
Table 20.17-2: Dual T1 and Dual T1-2 Card SES Threshold Configuration
Selected Bit
Error Rate
ESF Framing
CRC-6 Error Events
ESF Framing
ANSI T1.403 Grade
D4 Framing
BPV Bit Errors
per Second
1E-3
320
G6
1544
1E-4
101
G5
487
11
G4
15
5E-5 (1)
G3
1E-6 (2)
G2
1E-7 (2)
G1
1E-5
(1)
Notes
1. This bit error rate applies only to Dual E1-2 and Dual T1-2 cards.
2. This bit error rate applies only to Dual T1-2 cards.
To set the SES limit for Dual T1 cards

CONFIG SLOT <sn> OPTIONS MORE SES_LIMIT 320/1544* or 101/487
(400)
20.17-7

20.17.5

NNP 95-2035-01-00-B
Configuring SES and DGM Limits for the MPA card

When HCM3, HCM4 or HCM5 framing is used on the interface, full statistics are
gathered for the MPA card interface. If HCM or HCM2 is used, only partial statistics
are gathered. See Maintenance, chapter 34.1 for more information on quality statistics
gathering for the MPA card.
With full statistics gathering, the SES or DGM limit for each MPA card interface can
be set. You can configure the SES limit at the link level for the MPA card to provide
a higher level of link sensitivity.
Note
On the MPA card, changing the SES or DGM limits causes a reset of the statistics for
that interface.
To set the SES and DGM limits for MPA cards

CONFIG SLOT <sn-l> OPTIONS MORE STATS
SES_LIMIT
DGM_LIMIT
<number>
1E-6
5E-5
1E-4
1E-5
1E-3*
SK000803
20.17-8
(400)

NNP 95-2035-01-00-B
20.18

E1, E3 and Optical Extension Card

Parameters
This chapter describes the parameters that apply to E1, E3 and Optical Extension
cards and explains how to configure them.
20.18.1
Understanding E1, E3 and Optical Extension Card

Parameters
Table 20.18-1 lists the E1, E3 and Optical Extension card parameters and indicates
how they apply to each type of card.
Note
Optical Extension cards are configured using the same procedures to configure Dual
E1 cards.
Table 20.18-1: E1 and E3 Card Parameters

E1
Card
Dual E1
Card
Dual
E1-2
Card
E3
Card
Dual E3
Card
Optical
Ext.
Cards
Parameter
NU bit
Signal or chassis grounds
SES limit
BER
E-bit
CRC4 reframing
Equalization
E1 link quality monitoring
(400)
20.18-1

20.18.2

NNP 95-2035-01-00-B
Configuring the NU bit for E1, E3 and Optical Extension

Cards
E1-level NU bits are TS0 bits 4 through 8 in odd-numbered frames, which are the
frames without the FAS. The first three TS0 bits are reserved and are not
user-configurable.
For E3 cards, you can set the transmitted value of certain TS0 NU bits at the E3, E2
and E1 level.
For Dual E1 and Optical Extension cards (with a firmware ID of 40 or higher), you
cannot set NU bits, but you can cross-connect TS0 to aggregate or transparent data
circuits to allow the transparent end-to-end transport of the 5 E1-level NU bits.
Single and Dual E3 cards

NU bits can be set at the E3, E2 and E1 levels. Table 20.18-2 lists the number of NU
bits supported and their default values for each level.
Table 20.18-2: E3 NU Bits
E3 Level
Number of NU Bits
Default Value
E3
E2
E1
11111
To configure the NU bits for Single and Dual E3 cards

CONFIG SLOT <E3id> or <E3id-E2id> or <E3id-E1id> OPTIONS TX_NU_BIT or
TX_NU_BITS <bit_value>
where bit_value is 0 or 1 for E3-level or E2-level transmission, or a 5-digit binary value in the range 00000
to 11111 for E1-level transmission
To read the received NU bits for Single and Dual E3 cards

CONFIG SLOT <E3id> or <E3id-E2id> or <E3id-E1id>
The system displays the current values for the transmitted and received NU bits.
Dual E1and Dual E1-2 cards

When you enable the NU bit parameter, TS0 on each link can be independently
cross-connected to:
any aggregate interface card circuit except TS0 on Single E1 cards and the FDL on
20.18-2
Single or Dual T1 cards

TS0 on another Dual E1, Dual E1-2 or Optical Extension card
any data card circuit configured for transparent rate adaption
(400)

NNP 95-2035-01-00-B

The following conditions apply:
TS0 may only be cross-connected to a 64 kb/s clear channel (that is, a DS0 in
which all bits are available for user data). TS0 cannot be connected to CPSS for
the Dual E1 or Optical Extension card. For the Dual E1-2 card, TS0 can be
connected to CPSS only when CPSS_PIPE is enabled. TS0 cannot be connected to
SRMs, or super-rate circuits. There are no circuit configuration parameters for
TS0; it can only be connected or disconnected. TS0 can be protected by A/B
protection switching.
All five NU bits are set to 1 when trunk conditioning is applied and enabled (see
chapter 20.9).
When the NU bit or CPSS_PIPE parameter is enabled, CCS- and 31
channel-framed E1 links (chapter 20.6) are reduced from 31 to 30 circuits.
Although TS0 occupies 64 kb/s when cross-connected, only 40 kb/s (bits 4
through 8) carry user data. The other 24 kb/s (bits 1 through 3) are not
user-configurable and are forced to zero.
Note
The SA4 BER parameter (see section 20.18.5), NU bits parameter and CPSS in TS0
(see chapter 17.6) are mutually exclusive (only one of these parameters can be
enabled at one time). Any one of these three parameters can be used simultaneously
with the E-bit parameter (see section 20.18.6).
Configure the Dual E1, Dual E1-2 or Optical Extension card NU-bit parameter as:
NU5BIT_ON to enable it
NU5BIT_OFF to disable it (default)
To enable or disable NU bit cross-connections for Dual E1 cards
CONFIG SLOT <sn-l> OPTIONS TS0_OPTION NU5BIT_ON/NU5BIT_OFF*
To enable or disable NU bit cross-connections for Dual E1-2 cards

NU5BIT_ON/NU5BIT_OFF*
(400)
20.18-3

20.18.3

NNP 95-2035-01-00-B
Configuring Signal or Chassis Ground for E1 and Optical

Extension cards
Signal ground parameters for the E1, Dual E1 and Dual E1-2 cards with an E1 LIM
(75 W variant) are used to configure the receive and transmit coaxial shields as
grounded or floating. When signal ground is configured, the shield is connected to
the ground plane of the E1 card, which is connected to the signal ground on the
backplane. You can configure the receive or transmit shields as floating when the
differential between the shield potential and signal ground causes unusually high
noise problems.
The Dual E1-2 card also supports chassis ground, which connects the transmit and
receive shields to the chassis ground.
Configure the transmit and receive shields for signal ground as:
RX_EARTH for receive shield grounded (default)

TX_EARTH for transmit shield grounded (default)
RX_FLOAT for receive shield floating
TX_FLOAT for transmit shield floating
Although Optical Extension cards have a proprietary fibre optic interface, they are
configured using the same procedures to configure Dual E1 cards with a few
exceptions exceptions. In order for IOTUs to communicate, Optical Extension cards
must be configured for master and slave operation in the shield grounding mode.
Maintenance in timeslot is enabled by configuring the receive shields.
Configure transmit and receive shields as:
TX_FLOAT for master operation

TX_EARTH for slave operation
RX_EARTH for maintenance in timeslot 31
To configure signal ground for the E1 and Dual E1 cards
CONFIG SLOT <sn> or <sn-l> OPTIONS BNC_SHIELD
RX_FLOAT/RX_EARTH* TX_FLOAT/TX_EARTH*
SK000090
To configure signal or chassis ground for the Dual E1-2 card

CONFIG SLOT <sn-l> OPTIONS PHYSICAL BNC_SHIELD
RX_FLOAT/RX_EARTH*
TX_FLOAT/TX_EARTH*
CHASSIS/SIGNAL*
SK000706
20.18-4
(400)

NNP 95-2035-01-00-B
20.18.4

Configuring SES Limit for Dual E1 and Dual E1-2

For the Dual E1, Dual E1-2 and Optical Extension cards, you can configure the SES
limit for each link. The SES limit ensures that E1 links can be RAPID-switched before
the error rate on the E1 line becomes a problem for the user. A link enters the
unavailable (failed) state when ten consecutive SESs are received. If you define a
lower limit for declaring an SES, the link becomes unavailable at a lower error rate.
In Figure 20.18-1, one port of the Dual E1 or Dual E1-2 card terminates the access link
of a 3630 MainStreet node and the other port terminates a network link. Since the
access link is not RAPID-protected, the SES definition for the access link should be
less stringent than that for the network link.
Figure 20.18-1: E1 Links Used for Access and Network Termination
RAPID Alternate
Modem
3630 MainStreet
node
3600 MainStreet
node
3600 MainStreet
node
E1
E1
E1
Network
Dual E1 card
Dual E1 card
Port A Port B
Port A Port B
Telephone
E1
E1
E1
-Non-RAPID
-Standard SES limit
-RAPID primary
-Stricter SES limit
6588
Previously, a standard SES was defined as a second with 832 or more CRC4 error
events or 1400 HDB3 errors. Now you can select the SES limit from four preset
values according to your system and network configuration. Table 20.18-3 lists the
configurable SES limits and the number of CRC4 and HDB3 errors each limit
represents.
Table 20.18-3: Threshold Selection
SES Limit
CRC4 Error Events
HDB3 Error Events
10-3
832
1400
10-4
184
180
10-5
20
18
5 x 10-6
10
(400)
20.18-5


NNP 95-2035-01-00-B
To configure SES limit for the Dual E1 card

CONFIG SLOT <sn-l> OPTIONS MORE SES_LIMIT
5E-6
1E-5
1E-4
1E-3*
SK000091
To configure SES limit for the Dual E1-2 card

CONFIG SLOT <sn-l> OPTIONS THRESHOLDS SES_LIMIT
5E-6
1E-5
1E-4
1E-3*
SK000802
20.18.5
Configuring BER for Dual E1 and Dual E1-2 Cards

For Dual E1 and Dual E1-2 cards, you can use the TS0 SA4 bit to monitor the local
BER of each link. As shown in Figure 20.18-2, the SA4 bit (or N-bit) refers to bit 4 of
the TS0 in odd-numbered frames (those frames that do not carry the FAS). You can
configure the system to generate an alarm or transmit the SA4 bit to the far end, or
both, if the BER exceeds a pre-set threshold. The card automatically monitors the
far-end SA4 bit signal, and you can configure the system to generate an alarm when
it is detected.
For each link, you can configure the card to do these tasks when the BER threshold
is exceeded.
Set the SA4 bit to signal the remote end.

Generate an alarm in response to local BER or far-end SA4 bit signals.
Table 20.18-4 lists and summarizes the SA4 options.
20.18-6
(400)

NNP 95-2035-01-00-B

Figure 20.18-2: The E1 Multi-frame Showing the SA4 Bit

E1 Multiframe
Frames 0-15
0
10 11 12 13 14 15
Odd-numbered Frames*
1 2
30 31
Timeslots 0 to 31
Timeslot 0
1
Bits 1 to 8
Sa4 bit
*note:
The timeslot 0 in
even-numbered frames
carries the frame
alignment signal.
The timeslot 0 in
odd-numbered frames
does not carry the
frame alignment signal.
8102
Table 20.18-4: SA4 and BER Alarm Options

SA4_BIT
BERAlm
Actions
OFF
OFF
Do not send SA4 bit signal to far end.

Do not raise any alarms.
OFF
ON
Do not send SA4 bit signal to far end.

Raise local alarm if BER is exceeded locally.
Raise remote alarm when a change in the state of the incoming SA4 bit
is detected.
ON
OFF
Send SA4 bit signal to far end if BER is exceeded.

Do not raise local or remote alarm.
ON
ON
Send SA4 bit signal to far end if BER is exceeded.

Raise local alarm if BER is exceeded locally.
Raise remote alarm when a change in the state of the incoming SA4 bit
is detected.
Note
The SA4 BER parameter, NU bits parameter (section 20.18.2) and CPSS in TS0
(chapter 17.6) are mutually exclusive; only one of these parameters can be enabled
at any one time. Any of these three parameters can be used simultaneously with the
E-bit parameter (section 20.18.6).
(400)
20.18-7


NNP 95-2035-01-00-B
The BER of the incoming E1 link is calculated based on FAS errors if HDB3 statistics
are gathered, or on CRC4 errors if CRC4 statistics are gathered. If you turn on both
the BER alarm and SA4 options, the Dual E1 and Dual E1-2 cards monitor the BER
and also perform the following functions.
If the BER exceeds the pre-set error threshold, the card sets the transmitted SA4
bit to 0 and raises an Error Rate Exceeded alarm.

If the BER drops below the pre-set error threshold, the card sets the transmitted
SA4 bit to 1 and raises an Error Rate Normal alarm.
These events are recorded in the quality statistics for the affected link (see
Maintenance, section 34.1.3).
Table 20.18-5 lists the type of error event detected for Dual E1 and Dual E1-2 card
statistics and the corresponding pre-set error threshold that is applied when the SA4
bit parameter is enabled.
Table 20.18-5: SA4-bit Error Thresholds
Statistics Gathered
Errors Detected
Error Threshold
HDB3
FAS
10-5
CRC4
CRC4
106
To configure SA4 and BER Alarm for the Dual E1 card

CONFIG SLOT <sn-l> OPTIONS
TS0_OPTION
MORE
SA4BIT_ON/
SA4BIT_OFF*
BERAlm_ON/
BERAlm_OFF*
SK000092
To configure BER Alarm for the Dual E1-2 card

CONFIG SLOT <sn-l> OPTIONS THRESHOLDS ALARM_TIME
BER_Alm_ON/BER_Alm_OFF*
To configure the SA4 Bit for the Dual E1-2 card

SA4BIT_ON/SA4BIT_OFF*
20.18-8
(400)

NNP 95-2035-01-00-B
20.18.6

Configuring the E-bit for Dual E1 and Dual E1-2 Cards

When CRC4 statistics are being gathered for Dual E1 and Dual E1-2 cards, each link
can be configured to use the TS0 E-bit (also called the Si bit) to transmit CRC4 status
(either errored or error-free) to the far end.
As shown in Figure 20.18-3, the E1 multiframe is composed of 16 frames numbered
0 to 15. When CRC4 statistics are being gathered, the multiframe is further divided
into two sub-multiframes: SMF1 and SMF2.
One E-bit is carried in the first bit position of TS0 in each of Frames 13 and 15 of
SMF2. The Frame 13 E-bit indicates the CRC4 status of SMF1. The Frame 15 E-bit
indicates the CRC4 status of SMF2.
Table 20.18-6 shows how the E-bits indicate the CRC4 status.
Figure 20.18-3: Dual E1 and Dual E1-2 Card E-bits
E1 Multiframe
Sub-multiframe 1
0
Sub-multiframe 2
6
9 10 11 12 13 14 15
Frames 0 to 15
Frame 13
0
Frame 15
30 31
Timeslots 0 to 31
Timeslot 0
1
30 31
Timeslots 0 to 31
Timeslot 0
7
Bits 1 to 8
Bits 1 to 8
E-bit
E-bit
956
Table 20.18-6: E-bit States for CRC4 Status Indication

CRC4 Status
Frame 13 E-bit
(SMF1 Status)
Frame 15 E-bit
(SMF2 Status)
SMF1 and SMF2 are error-free
SMF1 is error-free
SMF2 is errored
SMF1 is errored
SMF2 is error-free
SMF1 and SMF2 are errored
(400)
20.18-9


NNP 95-2035-01-00-B
Configure the E-bits parameter as:
EBITS_ON to enable it
EBITS_OFF to disable it (default)
When the E-bit parameter is disabled, the E bit (Si bit) is set to 1 by default.
The E-bit option is not available for configuration unless CRC4_STATS is enabled.
Note 1
The SA4 BER parameter (see section 20.18.5), NU bits parameter (see section 20.18.2)
and CPSS in TS0 (see chapter 17.6) are mutually exclusive (only one of these
parameters can be enabled at any one time). Any of these three parameters can be
used simultaneously with the E-bit parameter.
Note 2
For ISDN links, the Dual E1-2 card can detect RAI with E-bits reporting regular CRC
block errors (ISDN state F2), or with E-bits reporting constant CRC block errors
(ISDN state F5).
To configure the E-bit for the Dual E1 card

CONFIG SLOT <sn-l> OPTIONS TS0_OPTION EBITS_ON/EBITS_OFF*
To configure the E-bit for the Dual E1-2 card

CONFIG SLOT <sn-l> OPTIONS PHYSICAL CRC4_OPTS
EBITS_ON/EBITS_OFF*
20.18.7
Configuring CRC4 Reframing for Dual E1 and Dual E1-2

Cards
CRC4 reframing can be configured for Dual E1 and Dual E1-2 card links. If CRC4
statistics are being collected and this parameter is enabled, the frame alignment is
reframed when the CRC error rate exceeds 914 errors each second. The frame
alignment is also reframed if the CRC multiframe synchronization is not achieved
within 8 ms of frame synchronization.
Select CRCREFR to enable CRC4 reframing and NO_CRCREFR to disable it.
CRC4 reframing is not available for configuration unless CRC4_STATS is enabled.
To configure CRC4 reframing for the Dual E1 card

CONFIG SLOT <sn-l> OPTIONS CRCREFR/NO_CRCREFR*
20.18-10
(400)

NNP 95-2035-01-00-B

To configure the CRC4 reframing for the Dual E1-2 card

CONFIG SLOT <sn-l> OPTIONS PHYSICAL CRC4_OPTS
CRCREFR/NO_CRCREFR*
20.18.8
Configuring Equalization for E3 Cards

The E3 cards must be configured to equalize any attenuation in the signal received
because of losses over the coaxial cable. Configure the card with the EQUALIZATN
parameter and one of the following equalization ranges:
0DB_4DB for 0 dB to 4 dB (default)

4DB_8DB for 4 dB to 8 dB
To configure equalization for E3 cards

CONFIG SLOT <E3id> OPTIONS EQUALIZATN
0DB_4DB*
4DB_8DB
8DB_10DB
10DB_12DB
SK000093
20.18.9
Configuring E1 Link Quality Monitoring for E3 Cards

You can configure E1 link quality monitoring for E3 cards, individually configuring
each E1 on the E3 cards to perform CRC4 error detection. This allows the E1 to
monitor the received signal quality over the link and transmit the status of the link
to the far end. A CRC4 error indication received from the far end has no service effect
on the DE3 or SE3 card. The link quality status is carried by TS0.
When CRC4 error detection is enabled, the DE3 and SE3 cards gather CRC4
statistics. When CRC4 error detection is not enabled, the DE3 and SE3 cards gather
FAS statistics (see Maintenance, section 34.1.3).
Table 20.18-7 shows how the signal carried in TS0 of the E1 varies in alternate
frames; one TS0 carries the FAS and the next TS0 carries the distant alarm indicator
and the NU bits. Bit position 1 of TS0 is reserved for international use (Si), except that
it carries the link quality indicator when CRC4 error detection is enabled. When
CRC4 error detection is not enabled, this bit is set to 1 by default. The bit is also used
to provide multiframe alignment. The distant alarm indicator (A) is 0 in normal
operation and set to 1 if a Distant Alarm is detected. Bits SA4 to SA8 are the NU bits.
(400)
20.18-11


NNP 95-2035-01-00-B
Table 20.18-7: Usage of Bits on TS0

Bit Position
TS0 carrying FAS
Si
TS0 not carrying FAS
Si
SA4
SA5
SA6
SA7
SA8
Configure the E3 card for CRC4 error detection or FAS statistics.
CRC4_STATS for CRC4

FAS_STATS for FAS (default)
CONFIG SLOT <E3id-E1id> OPTIONS CRC4_STATS/FAS_STATS*
20.18-12
(400)

NNP 95-2035-01-00-B
20.19

X.21 and V.35 PRI Card Parameters

This chapter describes the parameters that apply to the X.21 and V.35 PRI cards and
explains how to configure them.
20.19.1
Understanding X.21 and V.35 PRI Card Parameters

Table 20.19-1 lists the X.21 and V.35 card parameters and indicates how they apply
to each type of card.
Table 20.19-1: X.21 and V.35 PRI Card Parameters
X.21 PRI Card
V.35 PRI Card
Bandwidth utilization
Supervisory channel
Clocking source
Clock inversion
20.19.2
Parameter
Slip buffer
Configuring Bandwidth Utilization for X.21 and V.35 PRI

Cards
For X.21 and V.35 PRI cards, you must configure:
the number of circuits supported

the number of circuits that require signalling
Number of circuits for X.21 and V.35 PRI cards
Table 20.19-2 lists the default and maximum number of circuits possible for each
variant of the X.21 and V.35 PRI cards.
(400)
20.19-1


NNP 95-2035-01-00-B
Table 20.19-2: Number of Circuits

Part Number
Default
Number of
Circuits
Maximum
Number of
Circuits
Maximum
Bandwidth
Circuit
Total
Aggregate
Bandwidth
90-0669-01
30
30 (1)
64 kb/s
1920 kb/s
90-0669-03
56 kb/s
56 kb/s
90-0569-03 (2)
30
30 (1)
64 kb/s
1920 kb/s
90-0569-06 (2)
30
30 (1)
64 kb/s
1920 kb/s
90-0569-09 (2)
30
30 (1)
64 kb/s
1920 kb/s
90-0569-01 (3)
29
29
64 kb/s
1856 kb/s
90-0569-07
56 kb/s
56 kb/s
V.35 PRI Card
X.21 PRI Card
Notes
1. The last 64 kb/s of the aggregate link is referred to as the supervisory channel or TS0. The
supervisory channel is used to provide framing and signalling for the other circuits (up to 29).
Supervisory channel bandwidth not used for framing and signalling can be used to carry user data.
See also section 20.19.3.
2. X.21 PRI Type 2.
3. X.21 PRI Type 1.
Each circuit on a multi-circuit V.35 PRI or X.21 PRI card Type 2 represents a 64 kb/s
clear channel (a DS0 in which all bits are available for user data). These variants
support signalling carried in the HCM-framed supervisory channel (see
section 20.19.3).
Each circuit on the multi-circuit X.21 PRI card Type 1 also represents a 64 kb/s clear
channel, but signalling is not supported.
Single-circuit V.35 PRI and X.21 PRI cards provide a single 56 kb/s clear channel for
connection to Switched 56 services. Signalling is not supported.
Number of circuits with signalling for X.21 and V.35 PRI cards
Table 20.19-3 lists the default and maximum number of circuits that can use
signalling for each variant of the X.21 and V.35 PRI card.
20.19-2
(400)

NNP 95-2035-01-00-B

Table 20.19-3: Number of Circuits With Signalling

Part Number
Maximum Number of
Circuits
Default Circuits with

Signalling
Maximum Circuits
with Signalling
90-0669-01
30
29
90-0669-03
90-0569-03 (1)
30
29
90-0569-06 (1)
30
29
90-0569-09 (1)
30
29
90-0569-01 (2)
29
90-0569-07
V.35 PRI Card
X.21 PRI Card
Notes
1. X.21 PRI Type 2.
2. X.21 PRI Type 1 (signalling is not supported on this variant).
When you configure the number of circuits that require signalling (n), the system
supports signalling for circuits in the range 1 to (n-1). For example, if the number of
circuits that require signalling is 7, the system supports signalling on circuits 1 to 6,
inclusive.
If the total number of circuits configured for the link is x, then n must be (x -1). For
example, if the total number of circuits configured for the link is 30, the number of
circuits with signalling must be in the range 1 to 29.
Signalling information for all the circuits in this range is carried in a common
channel called the supervisory channel or TS0. The supervisory channel is carried in
the last 64 kb/s of the aggregate link. If the total number of circuits configured for
the link is x, the supervisory channel is always circuit x (see section 20.19.3).
To configure bandwidth utilization for X.21 and V.35 PRI cards

CONFIG SLOT <sn> OPTIONS NUM_CIRCS <number>
Note
The bandwidth utilization for X.21 and V.35 PRI cards cannot be changed if any
circuits are cross-connected or the slot is configured as a synchronization source.
(400)
20.19-3

20.19.3

NNP 95-2035-01-00-B
Configuring the Supervisory Channel for X.21 and V.35

PRI Cards
Each circuit on a multi-circuit V.35 PRI or X.21 PRI card Type 2 represents a 64 kb/s
clear channel (a DS0 in which all bits are available for user data). These variants
support signalling, carried in the HCM-framed supervisory channel, for all circuits
configured for signalling (see section 20.19.2).
X.21 PRI card Type 1 does not provide a supervisory channel. It uses a different
framing scheme (called Frame 1) to provide up to 29 circuits for user data. Circuits
are 64 kb/s clear channels and signalling is not supported. The X.21 PRI card Type 2
also supports Frame 1 framing for backwards compatibility. (Chapter 20.6 describes
framing formats.)
The supervisory channel is carried in the last 64 kb/s of the aggregate link. If the
total number of circuits configured for the link is x, then the supervisory channel is
always circuit x. Two signalling bits are reserved in the supervisory channel for each
circuit requiring signalling.
The supervisory channel is framed using the Newbridge proprietary HCM rate
adaption application (see chapter 23.6). The HCM framing bit is used to separate the
supervisory channel from the preceding circuits. Signalling bits are carried in the
HCM frame.
Figure 20.19-1 shows how the signalling bit pairs are automatically positioned in the
supervisory channel HCM frame, starting at the last HCM frame bit position (F9-B0).
A signalling bit pair is always placed in the same row. The HCM framing bit is
shown as F; signalling bits are shown as S.
Supervisory channel bandwidth not used for framing and signalling can be used to
carry sub-rate HCM or transparent user data, or both, including a CPSS channel (see
chapter 17.6).
Figure 20.19-1: Supervisory Channel Showing Signalling Bits
Framing bit
F0
F1
F2
F3
F4
F5
F6
F7
F8
F9
B7 B6 B5 B4 B3 B2 B1 B0
F
S
S
S
S
S
S
S
S
S
S
Bandwidth available
for transparent channels
Bandwidth available
for HCM channels
Signalling bits
for 5 channels
4228
20.19-4
(400)

NNP 95-2035-01-00-B

You can also configure the position of the HCM framing bit in the supervisory
channel (see chapter 23.6). Figure 20.19-2 illustrates the slot options display for an
X.21 PRI card Type 2. It shows the card configured for 30 circuits, 5 of which (circuits
1 to 5) require signalling.
Because signalling bit pairs (SS in Figure 20.19-2) are always placed in the same row,
the HCM frame must be 2, 4, 6 or 8 bits wide (depending on the number of circuits
configured for signalling). The framing bit (F in Figure 20.19-2) can be located in any
of columns B1, B3, B5 or B7.
Figure 20.19-2: X.21 PRI Screen Display
3600 MainStreet
1117-H1-00
Toronto:A
Configured
Installed
Status
A2
X21_PRI_2
X21_PRI_2
OOS
F0
F1
F2
F3
F4
F5
F6
F7
F8
F9
B7
B6
B5
B4
B3
S
S
B2
S
S
B1
S
S
S
B0
S
S
S
Alarms:1
11-May-1997
Name
8:35a
Options
Circuits : 30 DTE
C-CPSS
F-FRAMING BIT
S-SIGNALLING BIT
Channels with
Signalling
: 5
Framing Type
: 2
Buffering
: SHORT
Transmit Clock : NORMAL
CPSS over TS0 is DISABLED
CONFIG SLOT 2 OPTIONS

1-NUM CIRCS
6-LONG BUF
2-NUM SIG
7-MORE...
3-INVERT
8-CANCEL
4-FRAME BIT
9-QUIT
5-FRAME 1
0-
To configure the supervisory channel for X.21 and V.35 PRI cards
To configure the supervisory channel, set the number of signalling circuit
(NUM_SIG) and the width of the HCM frame (FRAME_BIT).
NUM_SIG
FRAME_BIT
<number>
<Bn>
SK000094
where
number is 0* to 29
Bn is B1, B3, B5 or B7*
(400)
20.19-5


NNP 95-2035-01-00-B
Note
You cannot change the number of signalling circuits or the HCM frame width if any
20.19.4
Configuring the Clocking Source for X.21 and V.35 PRI

Cards
You can configure the clocking source for the X.21 and V.35 PRI cards.
On PRI links, both ends of the link take their timing from the same clock. The end
configured as DCE supplies the clock to the end configured as DTE. The European
PTTs provide a clock on the PRI link. Alternatively, the system can supply the clock.
Configure the clocking source options as:
DTE to specify the PTT that provides the PRI link (default)
DCE to specify the system
To configure the clocking source for X.21 and V.35 PRI cards
CONFIG SLOT <sn> OPTIONS MORE DCE/DTE*
Note
When the interface speed of an X.21 Type 2 (see Table 20.19-3) or V.35 PRI link
configured for DTE differs from the incoming network clock speed by 3 percent,
the port is declared out-of-service and a Speed Mismatch alarm is raised (see
Maintenance, Table 35.8-22).
20.19.5
Configuring Clock Inversion for X.21 Cards

The X.21 PRI card (part number 90-0596-03 with a manufacturing code of G or
greater and 90-0569-07 with a manufacturing code of C or greater) allows you to
invert the bit clock. You can determine which edge of the bit clock is used to transmit
data (if the clock is configured as DTE) or to receive data (if the clock is configured
as DCE). To change the default bit clock edge, you can invert the clock.
Table 20.19-4 lists the distances for which clock inversion is required or not required.
20.19-6
(400)

NNP 95-2035-01-00-B

Table 20.19-4: Clock Inversion Settings for the X.21 PRI Card
Interface
Speed in
kb/s
Distance in m (ft)
No clock Inversion
Required
Distance in
m (ft)
Clock Inversion
Required
Interface
Speed
in kb/s
Distance in m (ft)
No Clock Inversion
Required
Distance in m (ft)
Clock Inversion
Required
64
0 to 50
(0 to 164)
not applicable
1024
0 to 4/44 to 50
(0 to 13.1/144.3 to 164)
4 to 44
(13.1 to 144.3)
128
0 to 50
(0 to 164)
not applicable
1088
0 to 3.5/41 to 50
(0 to 11.5/134.5 to 164)
3.5 to 41
(11.5 to 134.5)
192
0 to 50
(0 to 164)
not applicable
1152
0 to 2/37.5 to 50
(0 to 6.6/123 to 164)
2 to 37.5
(6.6 to 123)
256
0 to 50
(0 to 164)
not applicable
1216
0 to 1/34 to 50
(0 to 3.3/111.5 to 164)
1 to 34
(3.3 to 111.5)
320
0 to 48
(0 to 157.4)
48 to 50
(157.4 to 164)
1280
32 to 50
(105 to 164)
0 to 32
(0 to 105)
384
0 to 37.5
(0 to 123)
37.5 to 50
(123 to 164)
1344
29 to 50
(95.1 to 164)
0 to 29
(0 to 95.1)
448
0 to 30
(0 to 98.4)
30 to 50
(98.4 to 164)
1408
27.5 to 50
(90.2 to 164)
0 to 27.5
(0 to 90.2)
512
0 to 24
(0 to 78.7)
24 to 50
(78.7 to 164)
1472
26 to 50
(85.3 to 164)
0 to 26
(0 to 85.3)
576
0 to 19
(0 to 62.3)
19 to 50
(62.3 to 164)
1536
24 to 50
(78.7 to 164)
0 to 24
(0 to 78.7)
640
0 to 16
(0 to 52.5)
16 to 50
(52.5 to 164)
1600
22 to 50
(72.2 to 164)
0 to 22
(0 to 72.2)
704
0 to 13
(0 to 42.6)
13 to 50
(42.6 to 164)
1664
21 to 50
(68.9 to 164)
0 to 21
(0 to 68.9)
768
0 to 11
(0 to 36.1)
11 to 50
(36.1 to 164)
1728
19 to 50
(62.3 to 164)
0 to 19
(0 to 62.3)
832
0 to 8
(0 to 26.2)
8 to 50
(26.2 to 164)
1792
17.5 to 50
(57.4 to 164)
0 to 17.5
(0 to 57.4)
896
0 to 7
(0 to 23)
7 to 50
(23 to 164)
1856
17 to 50
(55.8 to 164)
0 to 17
(0 to 55.8)
960
0 to 5/48 to 50
(0 to 16.4/157.4 to 164)
5 to 48
(16.4 to 157.4)
1920
16 to 50
(52.5 to 164)
0 to 16
(0 to 52.5)
Configure clock inversion as:
INVERT to enable it (default)

NORMAL to disable it
(400)
20.19-7


NNP 95-2035-01-00-B
To configure clock inversion for X.21 cards

CONFIG SLOT <sn> OPTIONS INVERT*/NORMAL
20.19.6
Configuring the Slip Buffer for X.21 and V.35 PRI Cards
You can configure buffering for jitter and wander for the X.21 and V.35 PRI cards.
Jitter is short term variations in a bit cell with respect to its nominal value. It can be
expected when repeaters are used on the lines over which the link is transmitted.
Wander is low frequency excursions of the clock from its nominal value. It is
typically a problem with satellites because of their imperfect orbits.
Because there is only one clock on a PRI aggregate link, buffering is required in both
the transmit and receive directions. Slips are likely to happen at both the send and
receive sides at almost the same time.
For a PRI card, you can select one of two buffer sizes to accommodate jitter and
wander tolerance:
SHORT_BUF for 0.5 bits per 1 kb/s of bandwidth (default)

LONG_BUF for 1.0 bits per 1 kb/s of bandwidth
For example, if the bandwidth is 128 kb/s, selecting the short buffer sets aside
64 bits; selecting the long buffer sets aside 128 bits.
To configure the slip buffer for X.21 and V.35 PRI cards
CONFIG SLOT <sn> OPTIONS LONG_BUF/SHORT_BUF*
20.19-8
(400)

NNP 95-2035-01-00-B
20.20

MPA Card Parameters

This chapter provides an overview of the general MPA card configuration
procedure and contains configuration instructions for the following:
20.20.1
interface type
gender (DCE or DTE)
total number of channels and channel type
transport bandwidth
HCM framing and frame bit positions in TS0
SRM HCM data on TS0
control leads
lead initiated loopbacks
clock inversion
slip and doppler buffers
General Configuration Overview

To configure the MPA card and commission the communications circuits, three
general procedures are involved:
1.
Configure the operational characteristics of the MPA card interface and

channels.
2.
Connect and set up the circuits.
3.
Change defaults or set optional features.
The first general procedure is composed of the tasks required to get the MPA card
ready for communications. Table 20.20-1 lists the tasks in logical order and optional
or co-dependent tasks are indicated.
Table 20.20-1: First General Procedure Tasks
Configuration Task
Reference
Interface type
20.20.2
Device gender (DCE or DTE)
20.20.3
Total number of channels on the interface
20.20.4
Number of signalling channels
20.20.4
Transport bandwidth
20.20.5
Framing bit transport position (1)
20.20.7
(400)
20.20-1


NNP 95-2035-01-00-B
Configuration Task
Reference
17.6
CPSS over TS0 (2)

Control leads forced on/off
20.20.9
Control lead OOS conditioning
20.20.9
Lead-initiated loopbacks
20.20.9
Clock inversion
20.20.10
Notes
1. The framing bit position must be configured if CPSS over TS0 is required.
2. CPSS over TS0 is an optional feature of the MPA card.
The second general procedure involves connecting circuits to the MPA card. You can
immediately transmit information if no changes are required to any default settings
or card options. Super-rate circuit configuration is performed at this time, as
described in chapter 20.15. To configure an SRM HCM data circuit on TS0, see
section 20.20.8.
When a circuit is cross-connected on the MPA card, the system automatically sets the
following MPA card channel parameters:
signalling
channel type (voice or data)
The system uses the hardware that the MPA card is cross-connecting with to
determine the channel parameter settings. If you are connecting to hardware that
supports multiple configurations, such as T1 or E1 cards, then the default settings
are used. See chapter 20.12 to manually change the circuit signalling for the
MPA card and section 20.20.4 to change the channel type.
Tasks included in the third general procedure are those dealing with default or
optional settings that may require reconfiguration to match your specific network
requirements. Table 20.20-2 lists these options and features in alphabetical order. See
chapter 20.1 for a complete listing of configurable MPA card parameters, options
and defaults.
Table 20.20-2: MPA Card Optional Configuration Tasks
Configuration Task
Alarm Time
20.20-2
Reference
35.4
Background diagnostics
33.2.4
Custom trunk conditioning
20.11.2
Doppler buffer
20.20.11
Fault classes
20.9.5
Fault signalling
20.10.2
(400)

NNP 95-2035-01-00-B

Configuration Task
Reference
HCM framing
20.20.6
Loopback detection
20.14.1
Slip buffer
20.20.11
SES and DGM limits
20.17.5
Trunk conditioning
20.9.3
Figure 20.20-1 shows an NMTI slot display for link 1 of an MPA card installed on a
single bandwidth shelf. Two channels are configured as signalling channels.
Figure 20.20-1: Slot Display for an MPA Card Link
3600 MainStreet
#
A1-1
F0
F1
F2
F3
F4
F5
F6
F7
F8
F9
1117-H1-00
Configured
MPA
B7
A
A
A
A
A
A
A
A
A
A
B6
F
B5
Toronto:A
Installed
MPA
B4
B3
B2
Status
OOS
B1
B0
Alarms:1
Name
Configured As
Interface Type
CPSS Over TS0
Slip Buf Size
Slip By
SES_LIMIT
DGM_LIMIT
Loopback Detect
CPSS over TS0 is
Transmit Clock
11-May-1997
Options
Circuits :
8:35a
: HCM_3 - 64k - DTE

: RS530A
: DISABLE
: 10
: 10
: 1E-7
: 1E-7
: NONE
DISABLED
: NORMAL
C-CPSS F-SRM FRAMING BIT A-AGG FRAMING BIT S-SIGNALLING BIT

CONFIG SLOT 1-1 OPTIONS CIRCUIT TRANSP_BW
1-TRANSP_POS
6-
20.20.2
2-64k
7-
3-56k
8-CANCEL
4-48k
9-QUIT
50-
Configuring the Interface Type

The four ports on the MPA card are software configurable as either an X.21, X.21 ESI,
V.35, RS-449/V.36 or an RS-530-A interface.
(400)
20.20-3


NNP 95-2035-01-00-B
To configure the interface type

CONFIG SLOT <sn-l> OPTIONS I/F_TYPE
RS530A
RS449/V36
X.21
V.35
X.21 ESI
SK000689
where l is 1 to 4
20.20.3
Configuring Device Gender

You can configure the MPA card link gender as either DCE or DTE. Device gender
determines the clocking source and the wires used for data and control signals.
Data and control signals are transmitted and received on wire pairs. The device
gender determines which wires are used to send and receive the signal. A DTE
device sends data or control signals on one wire in the pair; a DCE device sends
signals on another wire. See Installation, Task 1605: Connecting External Devices to
Peripheral, Enhanced Locally Controlled or Locally Controlled Shelves for pinout
designations.
On PRI links, both ends of the link take their timing from the same clock. The end
configured as DCE supplies the clock to the end configured as DTE.
Note
The gender of the MPA card interface cannot be changed if that port is configured as
a source of synchronization.
In DTE mode, when the speed of the interface clock differs from the incoming
network clock by 3 percent, the port is declared out-of-service and a Clock Speed
Mismatch alarm is raised (see Maintenance, section 35.8.2, Table 35.8-22).
To configure the device gender

CONFIG SLOT <sn-l> OPTIONS MORE DCE/DTE*
where l is 1 to 4
20.20.4
Configuring Channels on the Interface

You can configure the total number of channels allocated to each MPA card
interface, as well as set channels to carry voice, data or signalling.
20.20-4
(400)

NNP 95-2035-01-00-B

The MPA card can connect to a total of 62 DS0 channels across the backplane, of
which 60 are available for data transport. One backplane channel per stream is
dedicated to carry CPSS over TS0 (if enabled) and another one is reserved for use by
the system. Framing information does not go out onto the backplane.
Figure 20.20-2 illustrates the default backplane channel assignments for ports 1
through 4 in a double bandwidth shelf.
Figure 20.20-2: Default Backplane Channel Assignments on a Double Bandwidth Shelf
Backplane channel 31
reserved
Channels
on the
backplane 1
32
PORT 1
15 channels
PORT 2
15 channels
CPSS
1
32
PORT 3
15 channels
PORT 4
15 channels
reserved
CPSS
9451
A channel stream represents 32 DS0 level channels on the backplane. Two channel
streams are allocated to the MPA card when it is installed in a double bandwidth
slot. Ports 1 and 2 share the same channel stream, as do ports 3 and 4. Each interface
is assigned 15 of the available 30 data channels. The last 64 kb/s of the channel
stream is reserved to carry CPSS for the first port in that stream to enable CPSS over
TS0. Channel 31 is reserved for use by the system.
If CPSS for port 1 is carried in channel 32 of the first channel stream, when CPSS over
TS0 is enabled for port 2, the highest unassigned 64 kb/s channel is automatically
selected to carry the CPSS. If all of the data channels for port 2 are unassigned, then
channel 29 is used for CPSS, leaving 14 channels available to port 2 for data. This
scenario also applies to ports 3 and 4 on the second channel stream.
All data channels on the link are assigned by default. If one of the two ports sharing
the same channel stream already has CPSS over TS0 enabled, then the message Not
Enough Bandwidth is displayed when attempting to enable CPSS for the second
port. One data channel must be made available to enable CPSS on the second port.
Figure 20.20-3 shows the default channel assignments for ports one through four on
the backplane in a single bandwidth shelf. All four ports share a single channel
stream on the backplane.
(400)
20.20-5


NNP 95-2035-01-00-B
Figure 20.20-3: Default Backplane Channel Assignments on a Single Bandwidth Shelf

reserved
Channels
on the
backplane 1
32
PORT 1
7 channels
PORT 2
7 channels
PORT 3
7 channels
PORT 4
7 channels
CPSS
9450
On a channel stream, either data or voice can be carried on the 30 channels that are
available for payload. When a circuit is cross-connected to the MPA card channel,
the system automatically sets the channel type according to the hardware being
connected. If you are connecting to hardware that supports multiple configurations,
such as T1 or E1 cards, then the system sets the channel type to the default setting
which is voice.
Any available channel on the MPA card link can be configured as a signalling
channel. When this is done, a corresponding signalling bit pair is automatically
placed in the last part of the TS0 frame, see Figure 20.20-4. Typically, any channel
that will carry voice traffic should be configured for signalling. An exception could
be if a nailed-up circuit is configured, which does not necessarily require signalling.
By default, no signalling is carried in the data portion of TS0.
Restrictions
The following restrictions apply when setting the number of channels on the MPA
card.
Before increasing the number of channels to a value greater than the default for
one port, decrease the number of channels allocated to one of the other ports
sharing the same channel stream. The maximum number of channels on a
channel stream is 30 and all are assigned to a port by default.
The number of signalling channels configurable on an interface is between 0 and
the total number of channels (n) configured on the interface minus 1 (n -1). This
is because TS0 is required for supervisory information.
Delay equalization problems may occur in a single bandwidth shelf. You can
either connect to another circuit to avoid fragmented bandwidth or reset the
MPA card to remove this problem.
To set the number of channels on the interface

CONFIG SLOT <sn-l> OPTIONS CIRCUIT NUM_CIRCS <number>
where
l is 1 to 4
number is 0 to 30
20.20-6
(400)

NNP 95-2035-01-00-B

Note
If you enter 0 for the number of channels on the port, the following message appears
Warning: Certain port configurations will be changed to default. All channels on
the port are reset to the default configuration and all connections are lost.
To set the number of signalling channels on the interface

CONFIG SLOT <sn-l> OPTIONS CIRCUIT NUM_SIG <number>
where
l is 1 to 4
number is 0 to the number of channels configured for the interface minus 1 (n-1)
To set the voice or data channel on the interface

CONFIG CIRCUIT <sn-l-cc> FUNCTION DATA/VOICE*
where l is 1 to 4
20.20.5
Configuring Transport Bandwidth

You can configure the transport bandwidth for each of the MPA card interfaces
independently as either n 48, n 56 or n 64 kb/s, where n = 1 to 30 and represents
the number of channels configured on the interface.
Note
The bandwidth cannot be changed if any channels on the MPA card interface are
cross-connected or the slot is configured as a synchronization source.
Two parameters define the total amount of bandwidth on the MPA card interface.
the transport bandwidth

the total number of channels associated with the port
See section 20.20.4 for information about configuring the number of channels on the
port.
(400)
20.20-7


NNP 95-2035-01-00-B
To set transport bandwidth

CONFIG SLOT <sn-l> OPTIONS CIRCUIT TRANSP_BW
64k*
48k
56k
SK000779
where l is 1 to 4
20.20.6
Configuring HCM Framing Type for TS0

Each of the four ports on the MPA card has its own supervisory channel, TS0, that
carries framing information in any bit position and signalling. The Newbridge
proprietary HCM framing scheme synchronizes the TS0 on the link.
The same HCM framing scheme must be used by the communicating devices at both
ends of the link; however, each of the MPA card interfaces can be configured to use
a different HCM framing scheme. There are five HCM framing schemes.
HCM1
HCM2
HCM3
HCM4
HCM5
If the MPA card is already configured for HCM2, changing the configuration of the
selected link to a single 48, 56 or 64 kb/s channel causes the system to automatically
change the framing to HCM1.
HCM2 must be used if the MPA card is connected to a 3606 MainStreet node, a
3612 MainStreet node or to the X.21 and V.35 PRI cards. If the MPA card is used in
an X.21 Transfix I node, HCM2 is not supported.
Note
The MPA card cannot be connected to an X.21 Transfix I card.
HCM3, HCM4 and HCM5 offer enhanced functionality that is not available with
HCM1 and HCM2. They provide G.821 statistics gathering, a maximum
synchronization time of 100 ms and in-band loopback signature detection.
The availability of these three framing patterns makes it possible to transport a PRI
link within a higher speed PRI link without synchronizing from the wrong
link-framing information. Service providers can choose to use either HCM4 or
HCM5 framing while HCM3 framing is for the end user.
20.20-8
(400)

NNP 95-2035-01-00-B

HCM1 and HCM2 framing use 800 b/s of bandwidth on the supervisory channel,
TS0. HCM3, HCM4 and HCM5 framing use 8 kb/s of bandwidth on TS0.
For aggregate link and frame bit position configuration, see section 20.20.7.
To configure HCM framing type for TS0

CONFIG SLOT <sn-l> OPTIONS FRAMING
HCM
HCM 2
HCM 4
HCM 3
HCM 5
SK000690
where l is 1 to 4
20.20.7
Configuring TS0 Framing Bit Positions

There are two types of framing bits in the supervisory channel: aggregate link A-bits
and the SRM HCM F-bit.
When HCM3, HCM4 or HCM5 framing is configured on the interface, both types of
framing bits are used in TS0. The A-bits consume 8 kb/s of bandwidth in the
supervisory channel, TS0, and are used to synchronize TS0 on the link. The F-bit
consumes 800 b/s of bandwidth and is used to synchronize SRM HCM data in TS0.
Since the HCM framing is independent of the aggregate link framing, the start of the
HCM frame must be flagged. The F-bit is always automatically inserted to the right
of the A-bits. The F-bit automatically moves when the A-bit position is changed.
When HCM1 or HCM2 framing is configured on the link, the F-bit is used to
synchronize both the aggregate link and the SRM HCM data in TS0. Only 800 b/s of
bandwidth in TS0 is consumed.
Figure 20.20-4 shows a TS0 frame as seen in the slot display for an MPA card link,
(see Figure 20.20-1 for an example slot display for the MPA card). The NMTI
displays the TS0 frame as a 10-row by 8-column matrix. The frame is divided into 80
elements that are transmitted at a rate of 800 elements in a second. Each element
represents one bit or 800 b/s of bandwidth. The rows are named F0 to F9; the
columns are named B7 to B0. The NMTI identifies an element by its row and column,
for example F3-B2.
Note
The default position of the framing bits are B7. Before enabling CPSS over TS0, the
framing bit position must be changed. Bit position B7 must be unoccupied to enable
8 kb/s CPSS. Bit positions B7 and B6 must be unoccupied to enable 16 kb/s CPSS.
(400)
20.20-9


NNP 95-2035-01-00-B
In Figure 20.20-4, the interface has 16 kb/s CPSS over TS0 enabled, which always
occupies bit positions B7 and B6 (see chapter 17.6 for information on enabling CPSS
over TS0). Both the A-bits and F-bit are shown, so the HCM scheme configured on
the interface is either HCM3, HCM4 or HCM5 (see section 20.20.6 for information).
Figure 20.20-4: Example TS0 Framed with HCM3, HCM4 or HCM5
MPA card
Framing bits
HCM
Framing bit
SRM
Data bit
B7
B6
B5
B4
B3
B2
B1
B0
F0
F1
F2
F3
F4
F5
F6
F7
F8
F9
Bandwidth available
for SRM HCM data
channels
Signal for five

signalling channels
CPSS over TS0
9464
Any unused bit positions to the right of the framing bits are available for SRM HCM
data and channel signalling. The NMTI represents the amount of bandwidth
allocated to an SRM HCM data channel by the number of elements containing a D,
where each D represents 800 b/s of bandwidth.
Signalling includes the clock adjustment if clocking is configured as independent.
The system reserves signalling bit positions in TS0 only if you configure a channel
as a signalling channel on the interface, see section 20.20.4. A pair of signalling bits
(S in Figure 20.20-4) is inserted in TS0 for each channel configured for signalling. The
aggregate link framing bits (the As in Figure 20.20-4) can be located in any column
except B0.
Note
You cannot change the number of signalling circuits or the HCM frame width if any
To set the aggregate link framing A-bit position

CONFIG SLOT <sn-l> OPTIONS FRAME_BIT <Bn>
where
l is 1 to 4
n in Bn is any column identifier
20.20-10
(400)

NNP 95-2035-01-00-B

To change the F-bit position on HCM1 and HCM2 framed TS0

CONFIG SLOT <sn-l> OPTIONS FRAME_BIT <Bn>
where
l is 1 to 4
n in Bn is any column identifier
20.20.8
Configuring an SRM HCM Data Circuit on TS0

Figure 20.20-4 shows an example TS0 frame as represented by the NMTI. CPSS over
TS0, framing and signalling bits can all occupy bandwidth on TS0. Any unused bit
positions to the right of the framing bit are available to be cross-connected to an SRM
HCM data channel. In this example, HCM1 or HCM2 is enabled since only the F-bit
appears in the frame (see section 20.20.7 for information). CPSS over TS0 is not
enabled, so the F-bit appears in the default position of B7.
The NMTI represents the amount of bandwidth allocated to an SRM HCM data
channel by the number of elements containing a D, where each D represents 800 b/s
of bandwidth (see Figure 20.20-5). Data and signalling can occupy any unused
bandwidth to the right of the framing F-bit. If the F-bit is moved to B5, in the case of
enabling 16 kb/s CPSS over TS0, then no data can be configured to appear to the left
of column B5. A maximum of 61.6 kb/s is available for an SRM HCM data circuit in
this example, but only 10.4 kb/s is configured.
Figure 20.20-5: Example SRM Data on TS0 Framed with HCM1 or HCM2
B7
B6
B5
B4
B3
B2
F0
F1
F2
F4
F5
F6
F7
F8
F9
B1
B0
9462
Ensure that the bandwidth of the SRM data is not larger than the unused bit
positions in TS0 so that it does not collide with signalling or framing bits (see
Figure 20.20-4). Configure the position of the SRM framing bits to match the position
of the MPA card links TS0 framing bits. See chapter 23.6 for more information on
configuring SRMs.
(400)
20.20-11


NNP 95-2035-01-00-B
Once you configure the SRM to match the TS0 on the MPA card link, connect the
SRM to the last circuit on the MPA card link. The SRM is automatically assigned to
the unused bit positions in TS0. For more information on MPA card channels, see
section 20.20.4.
20.20.9
Configuring Control Signals and Lead Initiated Loopbacks

Control signals provide the handshaking for call setup, tear-down and
synchronization. These signals are terminated on the MPA card and are not carried
across the network. To determine which of the pins on the MPA card backplane or
faceplate connector carry the various control signals, see Installation, Task 1605:
Connecting External Devices to Peripheral, Enhanced Locally Controlled or Locally
Controlled Shelves.
You can configure three control lead parameters:
forced on and forced off control lead signals

OOS conditioning
lead initiated local loopback detection
Table 20.20-3 lists the MPA card control lead signals with the direction of the signal
in both DCE and DTE mode.
Table 20.20-3: MPA Card Control Signals in DCE/DTE Modes
MPA Card Control Lead Signals
Description
Direction
Signal
DCE Mode
DTE Mode
Analog Loopback
ALB
Input
Output
Clear to Send
CTS
Output
Input
Data Carrier Detect
DCD
Output
Input
Data Set Ready
DSR
Output
Input
Data Terminal Ready
DTR
Input
Output
LL
Input
Output
RDL
Input
Output
RL
Input
Output
RTS
Input
Output
Ring Indicator
RI
Output
Input
Test Mode
TM
Output
Input
Local Loopback
Remote Digital Loopback
Remote Loopback
Request to Send
Table 20.20-4 compares the MPA card control signals with ANSI, EIA and ITU-T
standard control signals for each interface type. The direction of the signal is listed
with respect to whether the MPA card is configured as a DCE or DTE device.
20.20-12
(400)

NNP 95-2035-01-00-B

Table 20.20-4: MPA Card Interface Control Signal Correlations

Corresponding ANSI/EIA/ITU-T
Signals and Direction
MPA
Card
RS530-A
RS449
X.21
V.35
Signal
DCE/DTE
Signal
DCE/DTE
Signal
DCE/DTE
Signal (1)
DCE/DTE
ALB
Input/Output
CTS
CB
Output /Input
CS
Output/Input
Output/Input
DCD
CF
Output /Input
RR
Output/Input
Output/Input
Output/Input
DSR
CC
Output/Input
DM
Output/Input
Output/Input
DTR
CD
Input/Output
TR
Input/Output
Input/Output
LL
LL
Input/Output
LL
Input/Output
RDL
n/c
RI
n/c
RL
RL
Input/Output
RL
Input/Output
RTS
CA
Input/Output
RS
Input/Output
Input/Output
Input/Output
TM
TM
Output /Input
TM
Output/Input
Signal
Notes
1. V.35 signal references are actually pin number references. Consult the ITU-T V.35 Recommendation for the corresponding
signal names.
Control signals are configured as either forced on (transmits mark) or forced off
(transmits space). Table 20.20-5 displays the default control lead configuration for
the MPA card interface in DTE mode for the different interface types. The control
signal condition can be set for a circuit even if that circuit is configured as a source
of system synchronization. It can also be changed if a circuit is connected.
Table 20.20-5: Default MPA Card Control Signal Configuration (DTE)
Control Lead Output Signal
Condition
RS-530-A
RS499
Forced off
Forced on
DTR
Forced on
RDL
Forced off
RTS
Forced on
LL
Forced on
RL
Forced off
(400)
V.35
ALB
X.21
20.20-13


NNP 95-2035-01-00-B
The OOS condition is declared when an HCM framing synchronization is lost. This
can occur if, for example, there is a link failure. For each link on the MPA card, you
can configure the state of the output control leads during an OOS condition. One of
three states can be configured.
ON for the control lead to be forced on

OFF for the control lead to be forced off
NONE for the control lead to maintain its current state
The OOS configuration overrides the forced on or forced off setting. Once the OOS
condition clears, the state of the control leads return to the configured forced on or
forced off state.
Lead initiated local loopback is supported when the MPA card interface is
configured as a DCE device. If local loopback detection is enabled, assertion of the
LL control lead causes the MPA card to apply a line loopback with pass through, see
Maintenance, section 36.7.10 for loopback information. If local loopback detection is
disabled or there is already a line or equipment loopback applied on the card,
assertion of the LL lead is ignored.
To enable or disable the LL control lead, see the procedure To enable or disable
local loopback detection control leads.
Note
The remote MPA card automatically asserts the Test Mode lead when it applies a
loopback to the line. Once the loopback is removed, the Test Mode lead is negated.
To configure control lead signals

CONFIG SLOT <sn-l> OPTIONS MORE CTRL_ LEADS OUTPUTS
DTR
RTS
ON*/OFF
LL
RL
ON/OFF*
SK000780
where l is 1 to 4
20.20-14
(400)

NNP 95-2035-01-00-B

To configure OOS conditioning

CONFIG SLOT <sn-l> OPTIONS MORE CTRL_LEADS OUTPUTS
DTR
RTS
LL
RL
OOS
ON
OFF
NONE*
SK000781
where l is 1 to 4
To enable or disable lead-initiated local loopbacks

CONFIG SLOT <sn-l> OPTIONS CTRL_LEADS LL_ENABLE*/LL_DISABLE
where l is 1 to 4
20.20.10 Configuring Clock Inversion

An interface experiences reception problems if the received data changes state near
the interfaces sampling clock edge. You can invert the clock edge that the interface
samples to alleviate this problem. Clock edge inversion is available in both DCE and
DTE modes for all four interface types: RS530-A, RS499, X.21 and V.35.
Configure clock inversion as:
INVERT to enable it
NORMAL to disable it
The falling edge of the sampling clock is the default for the received data.
Note 1
The clock inversion feature of the MPA card is not compatible with the X.21 PRI
card. The X.21 PRI card inverts the sampling clock for transmitting data, whereas the
MPA card inverts the sampling clock for the receive data.
Note 2
Interface delay is determined by the cable length, device delays and the data rate.
(400)
20.20-15


NNP 95-2035-01-00-B
To configure clock inversion

CONFIG SLOT <sn-l> OPTIONS INVERT*/NORMAL
where l is 1 to 4
20.20.11 Configuring the Slip or Doppler Buffer

Either a slip buffer or a doppler buffer can be configured for use on each of the
MPA card interfaces.
A slip buffer is used to compensate for jitter on the line. Jitter is short term variations
in a bit cell with respect to its nominal value. It can be expected when repeaters are
used on the links. Because there is only one clock on a PRI link, buffering is required
in both the transmit and receive directions. Slips are likely to happen at both the send
and receive sides at almost the same time. Configure the slip buffer in the range of
10 to 39 frames.
The propagation delay of the MPA card with no slip buffer configured is less than
10 ms. The addition of slip buffering increases this time. With a 39 frame slip buffer
configured, the system increases the propagation delay to approximately 15 ms. A
smaller slip buffer results in a reduced amount of delay.
You can use the doppler buffer to compensate for wander. Wander is low frequency
excursions of the clock from its nominal value, a common problem with satellites
because of their imperfect orbits. The doppler buffer increases the propagation delay
to approximately 15 ms.
To configure the slip buffer size

CONFIG SLOT <sn-l> OPTIONS SLIP_BUFF BUFFER_SIZ <frames>
where
l is 1 to 4
frames is any number from 10* through 39
To set the number of slips

CONFIG SLOT <sn-l> OPTIONS SLIP_BUFF SLIP_BY <frames>
where
l is 1 to 4
frames is 10* to the configured size of the buffer
To enable or disable the doppler buffer

CONFIG SLOT <sn-l> OPTIONS SLIP_BUFF DOPPLER_EN/DOPPLER_DIS*
20.20-16
(400)

NNP 95-2035-01-00-B
21. Voice Interface Cards

NNP 95-2035-01-00-B
21.1
21.1 Understanding Voice Interface Card Configuration

Understanding Voice Interface

Card Configuration
This chapter describes the voice interface cards and summarizes the configuration
procedures and how they apply to each interface.
21.1.1
Understanding Voice Interface Cards

The 3600 MainStreet series bandwidth manager systems supports the following
voice interfaces:
4WTO Line card

E&M card
LGE card
LGS card
4WDX channel unit
E&M channel unit

LGE channel unit
LGS channel unit
MRD channel unit
You can install the 4WTO Line card in any UCS 1 to 8.

For the E&M, LGE and LGS cards, a range of variants is available to support
different TLP, line impedance and companding options. You can install these voice
cards in any UCS 1 to 8 in an enhanced locally controlled, locally controlled or
peripheral shelf.
You can install the 4WDX channel unit in any one of the first three channel unit
positions on the Common Carrier card. The 4WDX channel unit is a dual-height
channel unit which occupies two channel unit positions on the Common Carrier
card.
You can install the E&M, LGE, LGS and MRD channel units in any module position
of the Common Carrier card. Chapter 19.1 describes the Common Carrier card.
4WTO Line card

The 12-circuit 4WTO Line card provides on-premise, four-wire applications in
which there is no requirement for signalling. The audio line circuitry is configured
to match a 600 W line impedance in both transmit and receive directions. The 4WTO
Line card is commonly used for analog cellular networks.
E&M cards and channel units

E&M cards and channel units provide circuits for connection to voice equipment
using E&M signalling (E&M signalling is characterized by the use of separate paths
for control and voice signals).
(400)
21.1-1


NNP 95-2035-01-00-B
LGE cards and channel units

LGE cards and channel units interface to central office subscriber trunks or PBX
lines. These cards and channel units detect ringing current from the public exchange
on an incoming call and provide outgoing calling conditions to the public exchange.
LGS cards and channel units

LGS cards interface with PBX trunks or standard telephones. These cards and
channel units are designed for on- or off-premise applications. Each circuit emulates
an exchange line that provides a battery and ground (earth) feed and a ringing
source to the subscriber equipment (PBX or telephone). LGS cards and channel units
support DPO, FXS and MFO circuits.
4WDX channel unit

The 4WDX channel unit is a four-wire transmission line interface, which provides
on- or off-hook signalling in each direction. The channel unit interface connects to
other equipment that converts DX signalling to E&M signalling. It can also connect
to another 4WDX channel unit.
MRD channel unit

The MRD channel unit provides an on- or off-premise, single-circuit, 2-wire terminal
interface. It neither sources nor sinks dc power except during a ringing voltage
application when dc power is superimposed on the ringing voltage.
Note
The 4WTO channel unit is a data interface that can perform some of the functions
described in this chapter. The 4WTO channel unit is described primarily in
chapter 22.1.
21.1.2
Configuring Voice Interface Cards

Table 21.1-1 lists the 4WTO Line card configuration parameters. Each parameter has
a list of options, with any default option in brackets.
Table 21.1-1: 4WTO Line Card Configuration Parameters and Options
Parameter
Options
Slot Level
Card slot
4WTO
Circuit Level
TLPs
21.1-2
See Table 21.5-1.
(400)

NNP 95-2035-01-00-B

Table 21.1-2 lists the E&M card configuration parameters. Each parameter has a list
of options with any default option marked by an asterisk.
Table 21.1-2: E&M Card Configuration Parameters and Options
Parameter
Options
Slot Level
Card slot
E+M
Companding law
Mu-law
A-law
Signalling type for Mu-law cards
type I*
type II
type III
Signalling type for A-law cards
type IV
type V*
Audio wires
2-wires*
4-wires
TLPs
See Table 21.5-2.
Line impedance for Mu-law cards
900 W + 2.16 mF
600 W + 2.16 mF*
600 W
Line impedance for A-law cards
370 W + 620 W // 0.31mF

600 W*
600 W + 2.16 mF
Circuit Level
Line balance (1)
nominal*
220 W + (820 W // 115 nF)
383 W + (536 W // 220 nF)
Fault signalling
seized
idle*
Notes
1. This parameter is applicable only for A-law cards.
Table 21.1-3 lists the LGE card configuration parameters. Each parameter has a list
(400)
21.1-3


NNP 95-2035-01-00-B
Table 21.1-3: LGE Card Configuration Parameters and Options

Parameter
Options
Slot Level
Card slot
Card type
LGE
(1)
6 cct
8 cct
Companding law
Mu-law
A-law
TLPs
See Table 21.5-3.
Line impedance for 6 cct Mu-law

cards
900 W+ 2.16 mF
600 W + 2.16 mF*
600 W
Line impedance for 6 cct A-law

cards
370 W + 620 W // 0.31 mF*

600 W
Circuit Level
Signalling type for E1 signalling
remote extension
earth calling
loop calling disconnect clear (* for 6 cct A-law cards)
Signalling type for T1 signalling
loop start
ground start (* for Mu-law cards)
dial pulse terminating
Line balance
<200 W*
>200 W
Fault signalling
seized
idle*
Notes
1. This parameter is applicable only for A-law cards.
Table 21.1-4 lists the LGS card configuration parameters. Each parameter has a list
21.1-4
(400)

NNP 95-2035-01-00-B

Table 21.1-4: LGS Card Configuration Parameters and Options

Parameter
Options
Slot Level
Card slot
LGS
Card type
6 cct Mu-law
12 cct Mu-law
8 cct A-law
10 cct A-law
12 cct A-law
Companding law
Mu-law
A-law
TLPs
See Table 21.5-4.
Line impedance for 10 cct and 12 cct

Mu-law cards
600 W + 2.16 mF
900 W + 2.16 mF*
Line impedance for A-law cards
370 W + 620 W // 0.31 mF*

600 W
Circuit Level
remote extension
earth calling
loop calling disconnect clear
PLAR (2)
central battery working
loop start
ground start
loop start to E&M conversion
ground start to E&M conversion
PLAR*
PLAR with D3 framing
Line balance
nominal*
800 W // (100 W + 50 nF) (1)
Fault signalling
seized
idle*
Notes
1. This option is applicable only for Mu-law cards.
2. PLAR is the E1 default signalling type for 10 cct and 12 cct A-law cards.
Table 21.1-5 lists the 4WDX channel unit configuration parameters. Each parameter
has a list of options with any default option marked by an asterisk.
(400)
21.1-5


NNP 95-2035-01-00-B
Table 21.1-5: 4WDX Channel Unit Configuration Parameters and Options

Parameter
Options
Slot Level
Card slot
4WDX
Circuit Level
Signalling mode
normal polarity signalling*

reverse polarity signalling
fixed bias signalling*
switched bias signalling
TLPs
See Table 21.5-7.
Line impedance
150 W
600 W*
1200 W
Fault signalling
idle
seized*
Tx mute
enabled
disabled*
Loop balance
midpoint capacitor enable*/disable

build-out capacitance (1)
build-out resistance (2)
enable/disable*
loaded/non_loaded*
Transmit path equalization (3)
slope (4)
height (4)
bandwidth (4)
Notes
1. The valid range for build-out capacitance is 0 to 7 mF, step size 1 mF.
2. The valid range for build-out resistance is 1250 to 6250 W, step size 250 W.
3. The loaded, slope, height and bandwidth settings are configurable only when equalization is
enabled.
4. The valid range for slope, height and bandwidth is 0 to 15, step size 1.
Table 21.1-6 lists the E&M channel unit configuration parameters. Each parameter
has a list of options with any default option identified with an asterisk.
21.1-6
(400)

NNP 95-2035-01-00-B

Table 21.1-6: E&M Channel Unit Configuration Parameters and Options

Parameter
Options
Slot Level
Card slot
E+M
Card type
North America
Asia
Europe
other
Circuit Level
Companding law
Mu-law (1)
A-law (2)
Signalling mode
E&M*
pulse link repeater
transmission only
Signalling type for E&M mode (3)
type I (4)
type II
type III
type IV
type V (5)
type V with filter
Signalling type for PLR mode
type I
type II
Audio wires
2-wire*
4-wire
TLPs
See Table 21.5-5.
Line impedance for 2-wire mode
600 W + 2.16 mF
900 W + 2.16 mF*
Line balance
Module variant IDs (6) 01, 02, and 03
fixed, short loop*

fixed, long loop
continuous adapt
adapt and freeze
Module variant IDs 04 and 07
nominal*
alternate
continuous adapt
adapt and freeze
nominal*
continuous adapt
adapt and freeze
Fault signalling
seized
idle*
Tx mute (7)
enabled
disabled*
(400)
21.1-7


NNP 95-2035-01-00-B
Notes
1. Default companding law for module variant IDs 01, 02, 03 and 04.
2. Default companding law for module variant IDs 05, 06 and 07.
3. Signalling types IV, V, and V with filter apply only to module variant IDs 03 through 07 (see
Table 6.6-4 for the list of module variant IDs and their associated country or region).
4. Default signalling type for module variant IDs 01, 02 and 03.
5. Default signalling type for module variant IDs 04, 05, 06 and 07.
6. See Table 6.6-4 for the list of module variant IDs and their associated country or region.
7. Restrictions: Applies to all E&M channel unit variants except 90-1230-01. Applies to 2-wire mode
only. To prevent audio path singing, the Tx mute parameter must be enabled on the called circuit.
While the Tx mute parameter is enabled, on-hook line up and test procedures cannot be performed,
because on-hook transmission is disabled.
Table 21.1-7 lists the LGE channel unit configuration parameters. Each parameter
Table 21.1-7: LGE Channel Unit Configuration Parameters and Options
Parameter
Options
Slot Level
Card slot
LGE
Circuit Level

earth calling
remote extension
loop start *
ground start
dial pulse terminating
TLPs
See Table 21.5-6.
Line impedance
600 W + 2.16 mF
900 W + 2.16 mF*
Line balance
fixed, short loop*

fixed, long loop
adapt and freeze
Fault signalling
seized
idle*
Tx mute (1)
enabled
disabled*
Notes
1. Restrictions: To prevent audio path singing, Tx mute must be enabled on the called circuit. While Tx
mute is enabled, on-hook line up and test procedures cannot be performed (that is, on-hook
transmission is disabled).
21.1-8
(400)

NNP 95-2035-01-00-B

Table 21.1-8 lists the LGS channel unit configuration parameters. Each parameter
Table 21.1-8: LGS Channel Unit Configuration Parameters and Options
Parameter
Options
Slot Level
Card slot
LGS
Card type
North America
Asia
Europe
other
Circuit Level
Companding law
Mu-law (1)
A-law (2)

earth calling
remote extension
PLAR (3)
central battery working
loop start (4)

ground start
dial pulse originate
loop start to E&M conversion
ground start to E&M conversion
PLAR
PLAR with D3 framing
TLPs
See Table 21.5-6.
Line impedance
600 W + 2.16 mF
900 W + 2.16 mF*
(400)
21.1-9


NNP 95-2035-01-00-B
Parameter
Line balance
Module variant ID 02
Options
fixed, short loop*

fixed, long loop
adapt and freeze
Module variant ID 03
fixed, short loop*

fixed, long loop
continuous adaption
adapt and freeze
nominal*
alternate
continuous adaption
adapt and freeze
nominal*
continuous adaption
adapt and freeze
Fault signalling
seized
idle*
Tx mute (5)
enabled
disabled*
Notes
3. Default for module variant IDs 02 and 03 (see Table 6.8-5 for a list of module variant IDs and their
associated part numbers).
4. Default for module variant IDs 04, 05, 06 and 07 (see Table 6.8-5 for a list of module variant IDs and
their associated part numbers).
5. Restrictions: To prevent audio path singing, Tx mute must be enabled on the called circuit. While Tx
mute is enabled, on-hook line up and test procedures cannot be performed (that is, on-hook
transmission is disabled).
Table 21.1-9 lists the MRD channel unit configuration parameters. Each parameter
21.1-10
(400)

NNP 95-2035-01-00-B

Table 21.1-9: MRD Channel Unit Configuration Parameters and Options

Parameter
Options
Slot Level
Card slot
MRD
Card type
on-premise 2-wire
off-premise 2-wire
Circuit Level
TLPs (1)
See Table 21.5-8.
Line impedance
600 W + 2.16 mF
900 W + 2.16 mF*
Line balance
adapt and freeze

continuous adapt (2)
fixed, short loop*
fixed, long loop
Notes
1. For transmit TLPs between 10 and 12 dBr, the hardware rounds off the TLPs in 0.3 dB increments.
2. Continuous adapt is available only on the 90-1755-02 variant.
Note
The formats of the identifiers in the procedures are explained in Table 16.4-1 in
chapter 16.4.
Configuring TLPs and fault signalling also applies to the 4WTO channel unit.
(400)
21.1-11

NNP 95-2035-01-00-B
21.2
21.2 Voice Interface Card Slots

Voice Interface Card Slots

This chapter describes how to configure card slots for voice interface cards and
channel units.
21.2.1
Understanding Voice Interface Card Slots

You must configure card slots for the voice interface cards and channel units before
you can configure or connect circuits.
Voice interface cards

Configuring a card slot means:
configuring the slot to accept the card

configuring the circuits
selecting the companding law
Voice interface channel units
Before you configure a channel unit, you must configure the slot for a Common
Carrier card (see chapter 19.1). Then, you can configure the Common Carrier card
position for the type of channel unit.
Note 1
The dual height 4WDX channel unit occupies two slots on the Common Carrier card.
You must configure Common Carrier card slots 1, 2 or 3 for the 4WDX channel unit
(the channel unit does not fit in Common Carrier card slot 4).
Note 2
Before you configure a slot for a 4WDX channel unit, the next slot on the Common
Carrier card must be configured as empty.
Tables 21.2-1 and 21.2-2 list the relationship between the country and region
identifiers for the E&M and LGS channel units and their variant identifiers.
(400)
21.2-1


NNP 95-2035-01-00-B
Table 21.2-1: E&M Channel Unit Variants

Country or Region
Card
Identifier
Variant
Identifier
Channel Unit Designation
North America
$1C
01
E&M Version I
North America
$1C
02
E&M Version II and III
North America
$1C
03
International E&M channel unit
Japan
$C3
04
Germany
$C3
05
UK
$C3
06
France
$C3
07
Table 21.2-2: LGS Channel Unit Variants

Country or Region
Card
Identifier
Variant
Identifier
Channel Unit Designation
North America
$19
01
LGS Version I
North America
$19
02
LGS Version II and III
North America
$19
03
International LGS channel unit
Japan
$C0
04
Germany
$C0
05
UK
$C0
06
France
$C0
07
Companding laws
There are two types of companding law.
The Mu-law companding law is used most often in 1.544 Mb/s T1 environments.
The A-law companding law is typically used in 2.048 Mb/s E1 environments.
You select a companding law for each voice interface card as you configure the card
slot. For the E&M and LGS channel units, you select the companding law at the
circuit level. You do not need to select a law for the 4WTO Line card and the 4WDX,
LGE and MRD channel units, because they support only Mu-law companding.
21.2-2
(400)

NNP 95-2035-01-00-B
21.2.2

Configuring Voice Interface Cards and Channel Units

Configure the voice interface card as:
VOICE E+M for an E&M card

VOICE LGE for an LGE card
VOICE LGS for an LGS card
VOICE 4W_TO for a 4WTO Line card
Note
If you change the companding conversion algorithm for a slot configured for a voice
card, all cross-connections for the slot are disconnected. If the new slot option does
not support the configured TLP range, you must select a new TLP range (see
chapter 21.5).
After you have configured the Common Carrier card slot, define the channel unit
position as:
VOICE DX 4-WIRE for a 4WDX channel unit

VOICE E+M for an E&M channel unit
VOICE LGE for an LGE channel unit
VOICE LGS for an LGS channel unit
VOICE MRD for an MRD channel unit
Note

simultaneously.
(400)
21.2-3


NNP 95-2035-01-00-B
To configure voice interface card slots

ONFIG SLOT <sn> TYPE
AS_PRESENT
E+M
MuLaw
VOICE
LGS
LGE
ALaw
ALaw MuLaw
6_CIRCUIT
4W_TO
ALaw
MuLaw
8_CIRCUIT
6_CIRCUIT
8_CIRCUIT
12_CIRCUIT
10_CIRCUIT
12_CIRCUIT
SK000095
To configure voice interface channel unit slots

CONFIG SLOT <sn-cc> TYPE
E+M
NA
JAPAN
AS_PRESENT
VOICE
LGS
MRD
LGE
ASIA
EUROPE
OTHER GERMANY
OTHER
ON_PREM_2W
DX
4-WIRE
OFF_PREM2W
UK FRANCE OTHER
SK000096
where sn is the Common Carrier card slot number and cc is the channel unit position (1 to 4)
21.2-4
(400)

NNP 95-2035-01-00-B

Note 1
If your channel unit does not match any of the country values shown by the softkeys,
select the OTHER softkey and see the documentation provided with the unit.
Note 2
If you install an off-premise MRD in a Common Carrier card position that is
configured for an on-premise MRD, the channel unit will function as if it is an
on-premise MRD.
To configure the E&M and LGS CU companding law

CONFIG CIRCUIT <sn-cc-1> MORE MuLaw*/ALaw
where sn is the Common Carrier card slot number and cc is the channel unit position (1 to 4)
(400)
21.2-5

NNP 95-2035-01-00-B
21.3
21.3 Voice Interface Signalling

Voice Interface Signalling

This chapter describes how to configure the signalling mode for:
21.3.1
E&M channel units

E&M cards and channel units
LGE and LGS cards and channel units
4WDX channel units
Configuring E&M Signalling

For E&M cards, signalling has two aspects.
Signalling mode applies to the channel unit.

Signalling type applies to the card and channel unit.
E&M signalling mode
Configure the E&M channel unit signalling mode as:
E+M for E&M (default)

PLR for Pulse Link Repeater
TO for Transmission Only
E&M signalling type
The signalling type specifies how the signalling leads operate to establish a call.
Table 21.3-1 lists the E&M signalling types and Figure 21.3-1 shows each type.
Table 21.3-2 lists how the signalling types apply to each card and channel unit.
(400)
21.3-1


NNP 95-2035-01-00-B
Table 21.3-1: E&M Signalling

Signalling
type
Signalling leads
2-wire
PLR
4-wire
E&M Type I
Connecting Equipment
Node
On-hook
Off-hook
On-hook
Off-hook
Grounds
M lead
Provides
battery to
M lead
Opens E
lead
Grounds
E lead
E&M Type II
Opens
relay
between
M and SB
leads
Closes
relay
between
M and SB
leads
Opens
relay
between E
and SG
leads
Closes
relay
between E
and SG
leads
E&M Type III
Closes M
and SG
leads
Closes M
and SB
leads
Opens E
lead
Grounds
E lead
E&M Type IV
Same as Type II
Same as Type II except

SB is connected to
ground and M to battery
Opens E
lead
E&M Type V
Opens M
lead
E&M Type V
with filter
Same as Type V
Same as Type V except

that there is a low-pass
filter connected to the E
lead
PLR Type I
Opens E
lead
Grounds
E lead
Grounds
M lead
Provides
battery to
M lead
Opens
relay
between E
and SG
leads
Closes
relay
between E
and SG
leads
Opens
relay
between
M and SB
leads
Closes
relay
between
M and SB
leads
PLR Type II
TO
Grounds
M lead
Grounds
E lead
Signalling leads are not used
Table 21.3-2: E&M Signalling Options

Mu-law
Card (1)
A-law
Card
PLR CU
E&M CU
Type I
TYPE_I (2)
Type II
TYPE_II
Type III
TYPE_III
Type IV
TYPE_IV
Type V
TYPE_V (3)
Type V with filter
V_FILTER
Signalling Type
Option
Notes
1. Mu-law E&M card (part number 90-0079-06) supports Type IV and V signalling.
2. TYPE_I is the default for Mu-law E&M cards (except part number 90-0079-06) and channel unit
variants (part numbers90-1230-01through 03).
3. TYPE_V is the default for A-law E&M cards, Mu-law E&M card (part number 90-0079-06) and
channel units (part numbers 90-1230-04 through 07).
21.3-2
(400)

NNP 95-2035-01-00-B

Figure 21.3-1: E&M Signalling
Sensor
Sensor
48V
48V
Sensor
Sensor
48V
48V
Connecting equipment
E & M interface
E&M type I
E & M interface
E&M type V
SG
Sensor
Sensor
48V
48V
1 uf
SB
48V
M
48V
E & M interface
E&M type II
Sensor
Sensor
Sensor
E & M interface
E&M type V with Filter
48V
Sensor
48V
SG
M
Sensor
Sensor
M
48V
SB
48V
E & M interface
E & M interface
E&M type III
PLR type I
SG
SG
Sensor
48V
Sensor
48V
SB
SB
48V
Sensor
Sensor
48V
E & M interface
E&M type IV
E & M interface
PLR type II
6827
(400)
21.3-3


NNP 95-2035-01-00-B
To configure E&M card signalling

TYPE-I
TYPE-II
TYPE-III
TYPE-IV
TYPE-V
SK000097
To configure E&M channel unit signalling

CONFIG CIRCUIT <sn-cc-1> FUNCTION
TO
E+M
TYPE-I
TYPE-II
TYPE-III TYPE-IV
PLR
TYPE-V V_FILTER
TYPE-I
TYPE-II
SK000098
where sn is the Common Carrier card slot number and cc is the channel unit position number (1 to 4)
21.3.2
Configuring LGE and LGS Signalling

The signalling type specifies how the signalling leads operate to establish a call.
Table 21.3-3 lists the LGE and LGS signalling options and types and Table 21.3-4 lists
how the signalling options apply to the cards and channel units.
21.3-4
(400)

NNP 95-2035-01-00-B

Table 21.3-3: LGE and LGS Signalling

Option
Type
E1
T1
Characteristics
ABCD Bits
Idle
Seized
PLAR
Private Line
Automatic
Ringdown
Does not involve exchange. When

subscriber 1 goes off-hook,
cadenced ringing occurs at
subscriber 2. Subscriber 2 answers
call by going off-hook.
1101
0101
CBW
Remote
Extension
with Central
Battery
Working
Does not include exchange.

Subscriber 1 goes off-hook and
presses a recall button (B lead to
ground) to request ringing.
Subscriber 2 answers call by going
off-hook.
1101
0101
(ring)
LCDC
Loop Calling
Disconnect
Clear
Subscriber seizes the line by

applying loop current. When call is
terminated, exchange signals an
idle state by the absence of battery
feed for about 300 ms.
1101
0101
EC
Earth Calling

applying ground to the B lead. The
exchange acknowledges by
applying ground to the A lead.
1101
0101
REM_EXT
Remote
Extension

closing loop. Exchange signals idle
throughout the entire call and does
not provide answer supervision.
Subscriber can apply a recall signal
by connecting the B lead to earth.
1101
0101
LS
Loop Start
Subscriber applies loop current to

seize the line. Central office signals
idle throughout the entire call and
does not provide answer
supervision.
01
11
LS_EM
Loop Start to
E&M
Conversion
Similar to LS signalling but uses T1

E&M signalling in the network.
00
11
GS
Ground Start
Subscriber applies ground to ring

lead to seize line. Central office
acknowledges the seized line by
grounding the tip lead.
01
00
GS_EM
Ground
Start to E&M
Conversion
Similar to GS signalling but uses T1

E&M signalling in the network.
00
11
PLAR
Private Line
Automatic
Ringdown
Similar to E1 PLAR. Used in T1

channel banks with D4/ESF
framing.
00
11
PLAR_D3
Private Line
Automatic
Ringdown
D3
Similar to PLAR. Used in T1

channel banks with D3 framing in
which the signalling bits are
inverted from the D4 framing.
11
00
(400)
21.3-5


NNP 95-2035-01-00-B
Table 21.3-4: LGE and LGS Signalling Options

LGE Card
or CU
LGS Card
or CU
Signalling Type
Option
Central Battery Working
CBW
Dial Pulse Terminating
DPT
Earth Calling
EC
Ground Start
GS (1)
Ground Start to E&M Conversion
GS_EM
Loop Calling Disconnect Clear
LCDC (2)
Loop Start
LS (3)
Loop Start to E&M Conversion
LS_EM
PLAR
PLAR (4) or PLAR_D3
Remote Extension
REM_EXT
Notes
1. GS is the default for Mu-law LGE cards.
2. LCDC is the default for A-law LGE cards.
3. LS is the default for LGE channel units and LGS channel units (part numbers 90-1229-01 through
03).
4. PLAR is the default for LGS cards and LGS channel units (part numbers 90-1229-04 through 07).
LGE and LGS signalling types

Determine the signalling type for the LGE and LGS card or channel unit according
to Tables 21.3-3 and 21.3-4.
Note
LGS PLAR provides signalling according to the 1985 Addendum to PUB 43801. This
addendum specifies support for D4 channel banks and inverts the state of the
signalling bits specified in the 1982 Addendum. LGS PLAR_D3 provides signalling
according to the 1982 Addendum to PUB 43801. PLAR_D3 supports third-party
nodes (such as F3 channel banks) that still comply with the 1982 Addendum.
If you configure the LGS circuit for PLAR and the system contains a GFC2, there is
an audible ringback as the phone at the far end rings.
21.3-6
(400)

NNP 95-2035-01-00-B

To configure LGE signalling type

CONFIG CIRCUIT <sn-cc> or <sn-cc-1> FUNCTION
E1_SIG
REM_EXT
T1_SIG
EC
LCDC
LS
GS
DPT
SK000099
To configure LGS signalling type

CONFIG CIRCUIT <sn-cc> or <sn-cc-1> FUNCTION
T1_SIG
E1_SIG
PLAR CBW
LS_EM
LCDC
LS
EC
GS
REM_EXT
GS_EM
PLAR PLAR_D
SK000100
21.3.3
Configuring 4WDX Signalling

The 4WDX channel unit provides on- or off-hook signalling in both transmit (T) and
receive (R) directions. All signalling functions are conducted on the T and R, and T1
and R1 transmission pairs. The channel unit interface connects to other equipment
that converts 4WDX signalling to E&M signalling. Figure 21.3-2 shows a typical
4WDX signalling interface.
(400)
21.3-7


NNP 95-2035-01-00-B
Figure 21.3-2: 4WDX Signalling Interface

T
48V
Normal
A-lead
Reverse
On/off
hook
detector
B-lead
Reverse
T1
Bias
48V
R1
7623
4WDX signalling mode

Configure the 4WDX channel unit signalling mode as:
NORM_POL for normal polarity signalling (default)

REV_POL for reverse polarity signalling
FIXED_BIAS for fixed bias signalling (default)
SW_BIAS for switched bias signalling
Table 21.3-5 lists how the signalling modes apply to the 4WDX channel unit.
21.3-8
(400)

NNP 95-2035-01-00-B

Table 21.3-5: 4WDX Signalling

Option
Characteristics
NORM_POL
The A-lead is simplexed onto the T and R pair and the B-lead is simplexed onto the
T1 and R1 pair.
REV_POL
The A-lead is simplexed onto the T1 and R1 pair and the B-lead is simplexed onto
the T and R pair.
FIXED_BIAS
It applies grounding to the A-lead when the call is on-hook and nominal 48 V dc
to the A-lead conductor when the call is off-hook. It applies a constant voltage of
approximately 19 V dc to the B-lead conductor.
SW_BIAS
It applies grounding to the A-lead when the call is on-hook and nominal 48 V dc
to the A-lead conductor when the call is off-hook. It applies nominal 48 V dc to the
B-lead conductor when the call is on-hook and grounding to the B-lead conductor
when the call is off-hook.
Warning
Before connecting a Newbridge 4WDX channel unit to a non-Newbridge 4WDX
channel unit, ensure that both 4WDX channel units are configured for the same type
of bias signalling. Otherwise, damage may occur to the non-Newbridge 4WDX
channel unit.
To configure 4WDX signalling mode

CONFIGCIRCUIT <sn-cc-1> FUNCTION
NORM_POL*/REV_POL
FIXED_BIAS*/SW_BIAS
SK000676
Note 1
Signalling polarity or bias cannot be changed when the circuit is connected.
Note 2
Two 4WDX interfaces can be connected together by configuring one interface for
normal signalling and the other interface for reverse signalling.
(400)
21.3-9

NNP 95-2035-01-00-B
21.4
21.4 Audio Wires

Audio Wires
This chapter describes how to configure audio wires for E&M cards and channel
units.
21.4.1
Understanding Audio Wires for E&M Cards and Channel

Units
When an order wire is monitoring a 4-wire E&M circuit, it monitors only the traffic
transmitted by the circuit; it does not monitor received traffic.
Configure the number of audio wires for E&M cards and channel units as:
2-WIRE for two wires (default)

4-WIRE for four wires
Note
If you change the number of wires in the voice path for an E&M card slot and the
configured TLP range is not supported for the new slot option, you must select new
TLP ranges. An asterisk indicates the correct ranges when you select the
GAIN_RANGE softkey. The system also displays the warning The corresponding
gains must be selected (see chapter 21.5).
21.4.2
Configuring Audio Wires for E&M Cards and Channel

Units
You can configure audio wires for E&M cards and E&M channel units.
To configure audio wires for E&M cards

CONFIG SLOT <sn> OPTIONS 2-WIRE*/4-WIRE
To configure audio wires for E&M channel units

CONFIG CIRCUIT <sn-cc-1> FUNCTION 2-WIRE*/4-WIRE
(400)
21.4-1

NNP 95-2035-01-00-B
21.5
21.5 TLPs
TLPs
This chapter describes how to configure:
TLPs for circuits on voice interface cards and channel units

TLP ranges for voice interface cards
21.5.1
Understanding TLPs for Voice Interface Cards and

Channel Units
You can configure the TLPs for any voice interface card or channel unit, and the
4WTO channel unit.
The TLPs specify the receive and transmit levels (in decibels) of the signal from a
voice circuit with respect to the digital trunk. The receive TLP refers to the
digital-to-analog level (the difference between a and b in Figure 21.5-1); the transmit
TLP refers to the analog-to-digital level (the difference between d and c in
Figure 21.5-1).
Figure 21.5-1: Transmission Level Points
Digital
side
Analog
side
Rx
Tx
Voice circuit
7898
The TLPs are measured in dBm, which is the power of a signal relative to a signal of
1 mW.
A TLP is measured with respect to 0 dBm on the digital side. The 0 dBm value is
equal to 1 mW of power imposed on an impedance of 600 W or 900 W at a frequency
of 1004 Hz. On the digital side, 0 dBm is the digital signal power required to produce
0 dBm on the analog side of a standard digital-to-analog converter.
(400)
21.5-1
21.5 TLPs
21.5.2

NNP 95-2035-01-00-B
Configuring TLP Levels for Voice Interface Cards and

Channel Units
Tables 21.5-1 through 21.5-8 list the TLP levels for each voice interface card and
channel unit with the default values shown in brackets or marked by an asterisk.
Table 21.5-1: TLP Levels and Line Impedance for 4WTO Line Card
4WTO Line Card
Specification
Transmit TLP Range
Receive TLP Range
90-2687-01
8.5 to + 7.0 (0.0), D0.5 (1)
Line Impedance
600 W
8.5 to + 7.0 (0.0), D0.5
Notes
1. D = increment in dB.
Table 21.5-2: TLP Levels and Line Impedance for E&M Cards
E&M Card
Specification
2-Wire
Transmit TLP Range
Receive TLP Range
4-Wire
Transmit TLP Range
Receive TLP Range
Line Impedance (1)
7.5 to 0.0 (4.0), D0.5
17.5 to 10.0 (14.0), D0.5

+4.0 to +11.5 (8.0), D0.5
2W: 900 W + 2.16 mF

4W: 600 W
90-0091-06
E&M (6) 600C (4-3/0-7) U
3.5 to +4.0 (0.0), D0.5

7.5 to 0.0 (4.0), D0.5
17.5 to 10.0 (14.0), D0.5

+4.0 to +11.5 (8.0), D0.5
2W: 600 W + 2.16 mF

4W: 600 W
90-0079-03
E&M (6) ZCO (8-7/1-14) A
7 to +8.5 (0.0), D0.5

14.5 to +1 (7.0), D0.5
16 to 0.5 (7.0), D0.5

8.5 to +7 (0.0), D0.5
4W: 600 W
90-0079-04
90-0079-03
E&M (6) 600C (8-7/1-14) A
7.0 to +8.5 (0.0), D0.5

14.5 to +1.0 (7.0), D0.5
16.0 to 0.5 (7.0), D0.5

8.5 to +7.0 (0.0), D0.5
2W: 600 W
4W: 600 W
90-0079-05
90-0079-03
E&M (6) 600C (8-7/1-14) A
7.0 to +8.5 (0.0), D0.5

14.5 to +1.0 (7.0), D0.5
16.0 to 0.5 (7.0), D0.5 8.5

to +7.0 (0.0), D0.5
2W: 600 W + 2.16 mF

4W: 600 W
90-0079-06
E&M (6) 600C (8-7/1-14) U
7.0 to +8.5 (0.0), D0.5

14.5 to +1.0 (7.0), D0.5
16.0 to 0.5 (7.0), D0.5

8.5 to +7.0 (0.0), D0.5
2W: 600 W + 2.16 mF

4W: 600 W
90-0091-05
E&M (6) 900C (4-3/0-7) U
3.5 to +4.0 (0.0), D0.5 (2)
2W: 370 W + 620 W // 0.31 mF (3)
Notes
1. 2W = 2-wire; 4W = 4-wire.
3. // = in parallel with.
21.5-2
(400)

NNP 95-2035-01-00-B
21.5 TLPs
Table 21.5-3: TLP Levels and Line Impedance for LGE Cards
LGE Card
Specification
Transmit TLP Range
Receive TLP Range
Line Impedance
Companding
Law
600 W
Mu-law
4.5 to +3.0 (0.0), D.5

13.5 to +2.0 (7.0), D.5
600 W + 2.16 mF
Mu-law
6.5 to +1.0 (0.0), D.5

15.5 to 0.0 (7.0), D.5
900 W + 2.16 mF
Mu-law
90-0343-03
LGE (6) PROG (3-4/2-13) A
4.5 to +3.0 (0.0), D.5

13.5 to +2.0 (7.0), D.5
370 W + (620 W // 0.31 mF) (2)
A-law
90-0343-04
LGE (6) 600C (0-7/2-13) U
7.0 to 0.0 (3.0), D0.5

13.0 to +2.0 (6.0), D0.5
600 W + 2.16 mF
Mu-law
90-0343-05
LGE (6) 900C (0-7/1-14) U
7.0 to 0.0 (3.0), D0.5

14.0 to +1.0 (6.0), D0.5
900 W + 2.16 mF
Mu-law
90-0343-06
LGE (6) PROG (3-4/2-13) U (RDG)
4.5 to +3.0 (0.0), D.5

13.5 to +2.0 (7.0), D.5
600 W + 2.16 mF
Mu-law
6.5 to +1.0 (0.0), D.5

15.5 to 0.0 (7.0, D.5
900 W + 2.16 mF
Mu-law
90-0343-07
LGE (6) PROG (3-4/2-13) A
(REM EXT)
4.5 to +3.0 (0.0), D.5

13.5 to +2.0 (7.0), D.5
370 W + (620 W // 0.31 mF)
Mu-law
90-0343-01
LGE (6) 600R (3-4/2-13) U
4.0 to +3.0 (0.0), D1.0

3.0 to +4.0 (0.0), D1.0
600 W
Mu-law
90-0343-02
LGE (6) PROG (3-4/2-13) U
4.5 to +3.0 (0.0), D.5

13.5 to +2.0 (7.0), D.5
600 W + 2.16 mF
900 W + 2.16 mF
Mu-law
6.5 to +1.0 (0.0), D.5

15.5 to 0.0 (7.0, D.5
600 W + 2.16 mF
900 W + 2.16 mF
Mu-law
90-0343-03
LGE (6) PROG (3-4/2-13) A
4.5 to +3.0 (0.0), D.5

13.5 to +2.0 (7.0), D.5
370 W + (620 W // 0.31 mF)
A-law
90-0343-04
LGE (6) 600C (0-7/2-13) U
7.0 to 0.0 (3.0), D1.0

13.0 to +2.0 (6.0), D1.0
600 W + 2.16 mF
Mu-law
90-0343-05
LGE (6) 900C (0-7/1-14) U
7.0 to 0.0 (3.0), D1.0

14.0 to +1.0 (6.0), D1.0
900 W + 2.16 mF
Mu-law
90-0343-06
LGE (6) PROG (3-4/2-13) U (RDG)
4.5 to +3.0 (0.0), D.5

13.5 to +2.0 (7.0), D.5
600 W + 2.16 mF
900 W + 2.16 mF
Mu-law
6.5 to +1.0 (0.0), D.5

15.5 to 0.0 (7.0, D.5
600 W + 2.16 mF
900 W + 2.16 mF
Mu-law
4.5 to +3.0 (0.0), D.5

13.5 to +2.0 (7.0), D.5
370 W + (620 W // 0.31 mF)
A-law
90-0343-01
LGE (6) 600R (34-3/3-4) U
3.0 to +4.0 (0.0), D1.0 (1)
90-0343-02
LGE (6) PROG (3-4/2-13) U
90-0343-07
LGE (6) PROG (3-4/2-13) A
(REM EXT)
4.0 to +3.0 (0.0), D1.0
(400)
21.5-3
21.5 TLPs

NNP 95-2035-01-00-B
Notes
Table 21.5-4: TLP Levels and Line Impedance for LGS Cards
LGS Card
Specification
Transmit TLP Range
Receive TLP Range
Line Impedance
Companding
Law
90-0029-01
LGS (12) ZCO(4-3/1-6) A
3.0 to +4.0 (0.0), D1.0 (1)

6.0 to +1.0 (0.0), D1.0
370 W + (620 W // 0.31 mF) (2)
A-law
90-0029-02
LGS (10) ZCO(4-3/1-6) A
3.0 to + 4.0 (0.0), D1.0 6.0

to + 1.0 (0.0), D1.0
370 W + (620 W // 0.31 mF)
A-law
90-0030-01
LGS (12) 600R(4-3/1-6) U
3.0 to +4.0 (0.0), D1.0

6.0 to +1.0 (0.0), D1.0
600 W + 2.16 mF
Mu-law
90-0030-02
LGS (6) 600C(0-7/0-7) U
7.0 to 0.0 (3.0), D0.5

7.0 to 0.0 (3.0), D0.5
600 W + 2.16 mF
Mu-law
90-0030-03
LGS (6) 900C(0-7/0-7) U
7.0 to 0.0 (3.0), D0.5

7.0 to 0.0 (3.0), D0.5
900 W + 2.16 mF
Mu-law
90-0030-04
LGS (12) 900R(4-3/1-6) U
3.0 to +4.0 (0.0), D1.0

6.0 to +1.0 (0.0), D1.0
900 W + 2.16 mF
Mu-law
90-0029-05
LGS (12) 600 W A
3.0 to +4.0 (0.0), D1.0

6.0 to +1.0 (0.0), D1.0
600 W
A-law
Notes
21.5-4
(400)

NNP 95-2035-01-00-B
21.5 TLPs
Table 21.5-5: TLP Levels and Line Impedance for E&M Channel Units
E&M CU
Specification
Line Impedance (1)
2-Wire
Transmit TLP Range
Receive TLP Range
4-Wire
Transmit TLP Range
Receive TLP Range
12.0 to 0.0 (0.0), D0.1 (2)

10.0 to +6.0 (2.0), D0.1
16.0 to +7.0 (16.0), D0.1

16.0 to +7.0 (+7.0), D0.1
2W: 600 W + 2.16 mF

2W: 900 W + 2.16 mF*
4W: 600 W
90-1230-02
12.0 to 0.0 (0.0), D0.1

10.0 to +6.0 (2.0), D0.1
16.0 to +7.0 (16.0), D0.1

16.0 to +7.0 (+7.0), D0.1
2W: 600 W + 2.16 mF

2W: 900 W + 2.16 mF*
4W: 600 W
90-1230-03
12.0 to +6.0 (0.0), D0.1

10.0 to +6.0 (2.0), D0.1
16.0 to +7.0 (16.0), D0.1

16.0 to +7.0 (+7.0), D0.1
2W: 600 W + 2.16 mF

2W: 900 W + 2.16 mF*
4W: 600 W
90-1230-04
12.0 to +6.0 (0.0), D0.1

10.0 to +6.0 (2.0), D0.1
16.0 to +7.0 (0.0), D0.1

16.0 to +7.0 (0.0), D0.1
2W: 600 W + 1.0 mF

4W: 600 W
90-1230-05
12.0 to +6.0 (0.0), D0.1

10.0 to +6.0 (2.0), D0.1
16.0 to +7.0 (0.0), D0.1

16.0 to +7.0 (0.0), D0.1
2W: 220 W + 820 W // 115 nF (3)

4W: 600 W
90-1230-06
12.0 to +6.0 (+3.0), D0.1

10.0 to +6.0 (4.0), D0.1
16.0 to +7.0 (0.0), D0.1

16.0 to +7.0 (0.0), D0.1
2W: 370 W + 620 W // 310 nF

4W: 600 W
90-1230-07
12.0 to +6.0 (0.0), D0.1

10.0 to +6.0 (2.0), D0.1
16.0 to +7.0 (0.0), D0.1

16.0 to +7.0 (0.0), D0.1
2W: 180 W + 910 W // 150 nF

4W: 600 W
90-1230-01
Notes
1. 2W = 2-wire; 4W = 4-wire.
Table 21.5-6: TLP Levels and Line Impedance for LGE and LGS Channel Units
LGE and LGS CU
Specification
Transmit TLP Range
Receive TLP Range
Line Impedance
90-1229-01
LGE
12.0 to 0.0 (0.0), D0.1 (1)

10.0 to +6.0 (2.0), D0.1
600 W + 2.16 mF
900 W + 2.16 mF
90-1228-01
LGS
12.0 to +0.0 (2.0), D0.1

10.0 to +6.0 (0.0), D0.1
600 W + 2.16 mF
900 W + 2.16 mF
90-1228-02
LGS
12.0 to +0.0 (2.0), D0.1

10.0 to +6.0 (0.0), D0.1
600 W + 2.16 mF
900 W + 2.16 mF
90-1228-03
LGS
12.0 to +6.0 (2.0), D0.1

10.0 to +6.0 (0.0), D0.1
600 W + 2.16 mF
900 W + 2.16 mF
90-1228-04
LGS
12.0 to +6.0 (2.0), D0.1

10.0 to +6.0 (0.0), D0.1
600 W + 1.0 mF
(400)
21.5-5
21.5 TLPs

NNP 95-2035-01-00-B
LGE and LGS CU
Specification
Transmit TLP Range
Receive TLP Range
Line Impedance
90-1228-05
LGS
12.0 to +6.0 (0.0), D0.1

10.0 to +6.0 (2.0), D0.1
220 W + 820 W // 115 nF (2)
90-1228-06
LGS
12.0 to +6.0 (4.0), D0.1

10.0 to +6.0 (+3.0), D0.1
370 W + 620 W // 310 nF
90-1228-07
LGS
12.0 to +6.0 (2.0), D0.1

10.0 to +6.0 (0.0), D0.1
180 W + 910 W // 150 nF
Notes
Table 21.5-7: TLP Levels and Line Impedance for the 4WDX Channel Unit
4WDX CU
Specification
Transmit TLP Range
Receive TLP Range
90-2769-01
Line Impedance
150 W
600 W*
1200 W
+1.5 to -15 (0.0), D0.1 (1)

+6 to -10.5 (0.0), D0.1
Notes
Table 21.5-8: TLP Levels and Line Impedance for MRD Channel Units
MRD CU
Specification
(1)
Transmit TLP Range

Receive TLP Range
90-1755-01
12 to 0 (0.0), D0.1 (2)
Line Impedance
900 W + 2.16 mF
10 to +6 (8.0), D0.1
90-1755-02
12 to +6 (+6.0), D0.1
10 to +6 (8.0), D0.1
600 W + 2.16 mF
900 W + 2.16 mF*
Notes
1. For transmit TLPs between 10 and 12 dB, the hardware rounds off the TLPs in 0.3 increments.
For example, if you enter 10.1, it uses a transmit TLP of 10.0; if you enter 10.2, it uses a transmit
TLP of 10.3.
21.5-6
(400)

NNP 95-2035-01-00-B
21.5 TLPs
To select TLP levels for voice interface cards and channel units
CONFIG CIRCUIT <sn-cc> or <sn-cc-1> LEVELS
RX_TLP
TX_TLP
<tpl_level>
SK000101
where tlp_level is the appropriate TLP level from Tables 21.5-1 through 21.5-6 (for 4WTO channel units,
TLP level is 17.0 to +13.0 [TX_TLP] and -16.0 to +8.0 [RX_TLP] in increments of 0.1 dB)
21.5.3
Configuring TLP Ranges for Voice Interface Cards

You can configure a TLP range for each voice interface card. The cards support
different TLP ranges depending on the configuration of:
the number of audio wires (two or four) for an E&M card

the line impedance (which depends on the card variant installed)
You must configure the slot for the correct combination of line impedance and TLP
range (and audio wires for an E&M card). If the variant you install in the slot does
not match the configuration of these options, the system raises a Wrong card in
Slot alarm.
When you select GAIN_RANGE, the node manager displays all available TLP
ranges for the programmed card and indicates the TLP range required for the
current configuration with an asterisk.
Note
If you change the companding conversion algorithm for a voice card (or the number
of wires for an E&M voice card), and it no longer supports the configured TLP range,
you must select a new TLP range. An asterisk indicates the correct range when you
select the GAIN_RANGE softkey. The system also displays the following warning:
The corresponding gains must be selected.
To select a TLP range for the E&M card

CONFIG SLOT <sn> OPTIONS MORE GAIN_RANGE <number>
where number is the number corresponding to the appropriate TLP range
(400)
21.5-7
21.5 TLPs

NNP 95-2035-01-00-B
To select a TLP range for the LGE and LGS card

CONFIG SLOT <sn> OPTIONS GAIN_RANGE <number>
where number is the number corresponding to the appropriate TLP range
21.5-8
(400)

NNP 95-2035-01-00-B
21.6
21.6 Line Impedance

Line Impedance
This chapter describes how to configure line impedance for voice interface cards and
channel units.
21.6.1
Understanding Line Impedance for Voice Interface Cards

and Channel Units
You can configure line impedance for any of the voice interface cards and channel
units except the 4WTO Line card (always 600 W) and the 4-wire E&M channel unit
(always 600 W).
Table 21.6-1 lists the line impedance options and indicates how the options apply to
each card and channel unit. Tables 21.5-1 to 21.5-8 in chapter 21.5 show line
impedances for each card type and TLP range.
Note
You must configure a slot for the correct combination of line impedance (determined
by the card variant) and TLP range (and audio wires for E&M cards). If the variant
you install in the slot does not match the configuration of these options, the system
raises a Wrong card in Slot alarm.
Table 21.6-1: Line Impedance Options

E&M
A-law
Card
E&M
Mu-law
Card
LGE, LGS
A-law
Card
LGE, LGS
Mu-law
Card
4WDX
CU
E&M, LGE,
LGS, MRD
CU
Option
370 W + 620 W // 0.31 mF
370C
600 W
600
Line Impedance
600 W + 2.16 mF
600+2.1
900 W + 2.16 mF
900+2.1
600 W + 2.16 mF
600+2.16
900 W + 2.16 mF
900+2.16
150 W, 600 W or 1200 W
150
600*
1200
(400)
21.6-1
21.6 Line Impedance

21.6.2

NNP 95-2035-01-00-B
Configuring Line Impedance for Voice Interface Cards and

Channel Units
You can configure line impedance for E&M, LGE and LGS cards, and 4WDX, E&M,
LGE, LGS and MRD channel units.
Configuring line impedance for E&M cards

Configure line impedance for the E&M card as:
1 for 370 W + 620 W // 0.31 mF

2 for 600 W
3 for 600 W + 2.16 mF
4 for 900 W + 2.16 mF
Note
E&M cards programmed for four audio wires always have a line impedance of
600 W. Although you can configure line impedance for these cards, the configuration
has no effect and the node manager generates a Wrong card in Slot alarm.
To configure line impedance for E&M cards

CONFIG SLOT <sn> OPTIONS MORE LINE_IMP 1/2/3/4
Configuring line impedance for LGE and LGS cards

Configure line impedance for the LGE and LGS cards as:
370C for 370 W + 620 W // 0.31 mF

600 for 600 W
600+2.1 for 600 W + 2.16 mF
900+2.1 for 900 W + 2.16 mF
Note
If you select 900 W + 2.16 mF for a LGS Mu-law card, you introduce a 1.76 dB loss that
raises the TLP ranges by 2 dB. The system displays the warning The corresponding
gains must be selected. It rejects the card with a Wrong card in Slot message until
you select a new TLP range.
21.6-2
(400)

NNP 95-2035-01-00-B
21.6 Line Impedance

To configure line impedance for LGE and LGS cards

CONFIG SLOT <sn> OPTIONS LINE_IMP
600
600+2.1
900+2.1
370C
SK000103
Configuring line impedance for channel units

Configure line impedance for the 2-wire E&M, LGE, LGS and MRD channel units as:
600+2.16 for 600 W + 2.16 mF

900+2.16 for 900 W + 2.16 mF (default)
Note
For E&M channel units programmed for four audio wires, line impedance defaults
to 600 W and is not user-configurable. If you select LINE_IMP, the system displays
the message Invalid configuration.
To configure line impedance for channel units

CONFIG CIRCUIT <sn-cc-1> MORE LINE_IMP
600+2.16
900+2.16*
SK000104
Configuring line impedance for 4WDX channel units

Configure line impedance for the 4WDX channel unit as:
150 for 150 W

600 for 600 W (default)
1200 for 1200 W
(400)
21.6-3
21.6 Line Impedance


NNP 95-2035-01-00-B
To configure line impedance for 4WDX channel units

CONFIG CIRCUIT <sn-cc-1> MORE LINE_IMP
600*
150
1200
SK000105
21.6-4
(400)

NNP 95-2035-01-00-B
21.7
21.7 Line Balance

Line Balance
This chapter describes how to configure line balance for voice interface cards or
channel units.
21.7.1
Understanding Line Balance for Voice Interface Cards and

Channel Units
You can configure line balance for the voice interface cards or channel units except
the 4WTO Line card, 4WDX channel unit and 4-wire E&M channel unit. The line
balance option reduces echo by matching the balance impedance to the line
impedance.
21.7.2
Configuring Line Balance for Voice Interface Cards and

Channel Units
You can configure line balance for the voice interface cards or channel units except
the 4WTO Line card, 4WDX channel unit and 4-wire E&M channel unit.
To configure line balance for E&M cards

Configure line balance for E&M cards as:
1 for nominal (default)

2 for 220 W + (820 W // 115 nF)
3 for 383 W + (536 W // 220 nF)
CONFIG CIRCUIT <sn-cc> MORE LINE_BAL 1*/2/3
To configure line balance for LGE cards

Configure line balance for LGE cards as:
SHORT for < 200 W (default)

LONG for > 200 W
CONFIG CIRCUIT <sn-cc> MORE LINE_BAL LONG/SHORT*
(400)
21.7-1
21.7 Line Balance


NNP 95-2035-01-00-B
To configure line balance for LGS cards

Configure line balance for LGS cards as:
1 for nominal (default)

2 for 800 W // (100 W + 50 nF)
CONFIG CIRCUIT <sn-cc> MORE LINE_BAL 1*/2
Line balance for channel units

You can configure line balance for the 2-wire E&M, LGE, LGS and MRD channel
units as:
FIX_SHORT (North America) or NOMINAL (Japan and France) (default)

FIX_LONG (North America) or ALTERNATE (Japan and France)
CONTINUOUS
ADAPT/FRZ
Table 21.7-1 lists the fixed balanced impedances for each variant of the E&M and
LGS channel units.
Table 21.7-1: Balanced Impedance for E&M/LGS Channel Units
Country
Balanced Impedance
FIX_SHORT/NOMINAL
Variant
FIX_LONG/ALTERNATE
North America
600 W + 2.16 mF
1650 W // 100 W + 0.005 mF
01, 02, 03
North America
900 W + 2.16 mF
1650 W // 100 W + 0.005 mF
01, 02, 03
Japan
600 W + 1.00 mF
150 W + 830 W // 0.072 mF
04
Germany
220 W + 820 W // 0.115 mF
n/a
05
UK
370 W + 620 W // 0.31 mF
n/a
06
France
180 W + 910 W // 0.15 mF
600 W
07
If you choose adapt and freeze, the system provides two further options:
EXISTING for existing

RE_ADAPT for re-adapt
The EXISTING option instructs the channel unit to use the line balance coefficients
stored on it from a previous adapt and freeze. When you first change the line balance
mode to adapt and freeze, you must select EXISTING. If you do not, the system
displays the warning Invalid configuration. Must select existing coefficients before
re-adapting.
21.7-2
(400)

NNP 95-2035-01-00-B
21.7 Line Balance

After you establish existing coefficients, you can calibrate line balance to cause the
channel unit to re-adapt to its existing coefficients. During the calibration of line
balance, the re-adapt option instructs the channel unit to adapt to the line for
approximately 0.5 seconds. The channel unit retains and uses these coefficients until
you select re-adapt again or change the line balance mode. For RE-ADAPT to
operate, the system needs a GFC, GFC2 or GFC3 and a white noise source.
Note
To calibrate the line balance coefficients for the channel units, see Maintenance,
chapter 40.1.
For the MRD (variant 02) and 2-wire E&M and LGS channel units (variants 03
through 07), you can also select CONTINUOUS for continuously adapting line
balance. In this mode, the channel unit continuously adapts the transhybrid loss
optimization on the line.
To configure line balance for channel units

CONFIG CIRCUIT <sn-cc-1> MORE LINE_BAL
FIX_SHORT or FIX_LONG or CONTINUOUS ADAPT/FRZ
NOMINAL*
ALTERNATE
EXISTING
RE_ADAPT
SK000106
Note
If the E&M channel unit is configured for four audio wires and you select
LINE_BAL, the system displays the message Invalid configuration.
(400)
21.7-3

NNP 95-2035-01-00-B
21.8
21.8 Voice Interface Fault Signalling

Voice Interface Fault Signalling

This chapter describes how to configure fault signalling for voice interface cards and
channel units.
21.8.1
Understanding Fault Signalling for Voice Interface Cards

and Channel Units
Fault signalling is the signalling condition that the system applies to the interface
when its cross-connected interface is not available (out of synchronization or not
present).
You can configure fault signalling as seized or idle for any of the voice interface
cards (except the 4WTO Line card, which has no signalling capability) and channel
units (except the MRD channel unit, which is automatically configured with idle
fault signalling).
Note
Only the E&M channel unit responds to OOS-A fault signalling (see chapter 20.10).
21.8.2
Configuring Fault Signalling for Voice Interface Cards and

Channel Units
Configure fault signalling as:
SEIZED for seized

IDLE for idle
To configure fault signalling for voice interface cards and channel units
CONFIG CIRCUIT <sn-cc> or <sn-cc-1> FAULT_SIG
SEIZED
IDLE
SK000107
(400)
21.8-1

NNP 95-2035-01-00-B
21.9
21.9 Tx Mute
Tx Mute
This chapter describes how to configure the Tx Mute parameter for the 4WDX,
2-wire E&M, LGE and LGS channel units.
21.9.1
Understanding Tx Mute for Voice Interface Channel Units

When the calling telephone is off-hook and the called telephone is on-hook, an audio
loop can be created between the transmit and receive paths of the calling telephone,
as Figure 21.9-1 shows. Re-amplification of the signal as it travels through the loop
can produce an unpleasant noise called singing on 2-wire connections.
Figure 21.9-1: Audio Loop Singing
Calling phone
Voice card or
channel unit
Tx
Off-hook
Called phone
Voice
channel unit
Tx
Rx
Rx
Audio loop due to

current leakage
On-hook
8795
The Tx mute parameter prevents audio loop singing by disabling the transmit path
of the called telephone, as shown in Figure 21.9-2. When the called telephone goes
off-hook, the transmit path is enabled. Echo cancellation circuitry on the voice cards
and channel units prevents singing while both telephones are off-hook.
Figure 21.9-2: Tx Mute
Calling phone
Off-hook
Voice card or
channel unit
Called phone
Voice
channel unit
Tx
Tx
Rx
Rx
On-hook
Audio loop prevented

by Tx mute
8796
(400)
21.9-1
21.9 Tx Mute
21.9.2

NNP 95-2035-01-00-B
Enabling and disabling Tx mute for voice interface

channel units
Figure 21.9-3 shows a typical NMTI display showing the status of the TX mute
parameter.
Figure 21.9-3: Tx Mute Display
3600 MainStreet
Circuit
Name
1117-H1-00
Toronto:A
Type
Alarms:1
Function
A1-01-01
LGS_LS
Rx -2.0,Tx +0.0
Configured
RX TLP Range
TX TLP Range
Line Impedance
Line Balance
On-hook TX Mute
:
:
:
:
:
11-May-1997
8:35a
Fault
Status
IDLE
Configured
-10.0 to +6.0
-12.0 to +0.0
900 Ohms+2.16uF
Fixed Short
Enabled
CONFIG CIRCUIT A1-1-1 LEVELS

1-RX TLP
6-
2-TX TLP
7-
3-TXMUTE_OFF
8-CANCEL
49-QUIT
50-
Tx mute restrictions
To prevent audio path singing, the Tx mute parameter must be enabled on the
called circuit.
While the Tx mute parameter is enabled, you cannot do on-hook line-up and test
procedures (on-hook transmission is disabled).
To enable and disable Tx mute for voice interface channel units

CONFIG CIRCUIT <sn-cc-1> LEVELS TXMUTE_ON/TXMUTE_OFF*
21.9-2
(400)

NNP 95-2035-01-00-B
21.10
21.10 Loop Balance

Loop Balance
This chapter describes how to configure loop balance for the 4WDX channel unit.
21.10.1
Understanding Loop Balance for 4WDX Channel Units

The 4WDX channel unit operates with a maximum external loop resistance of
5000 W. This resistance is recognized by the T and R, and T1 and R1 signalling leads.
To enable the signalling circuitry to operate under all loop conditions over the full
battery voltage range and be immune to longitudinal voltages, several options are
provided to balance the signalling circuitry with the loop conditions. Table 21.10-1
lists the loop balance options.
Table 21.10-1: Loop Balance Options for the 4WDX Channel Unit
Loop Balance
Options
Definition
Range
Mid-point capacitance
This option enables or disables the mid-point capacitor

across the A and B leads to prevent reflected pulses
from falsely activating the DX circuit.
ENABLE*/DISABLE
Build-out capacitance
This option balances the capacitance of the metallic

facility and the mid-point capacitor.
0 to 7 mF, step size 1 mF (* = 4 mF)
Build-out resistance
This option balances the resistance of the metallic

facility.
1250* to 6250 W, step size 250 W (1)
Notes
1. Default setting is 1250 W. This represents an external loop resistance of 0 W.
21.10.2
Configuring Loop Balance for 4WDX Channel Units

Configure loop balance as:
MP_CAP_DIS for mid-point capacitance disabled

MP_CAP_ENA for mid-point capacitance enabled (default)
B_O_CAP for build-out capacitance
B_O_RES for build-out resistance
(400)
21.10-1
21.10 Loop Balance


NNP 95-2035-01-00-B
To configure loop balance for 4WDX channel units

CONFIG CIRCUIT <sn-cc> or <sn-cc-1> MORE LOOP_BAL
MP_CAP_DIS/MP_CAP_ENA*
B_O_CAP
B_O_RES
SK000108
21.10-2
(400)

NNP 95-2035-01-00-B
21.11
21.11 Equalization
Equalization
This chapter describes how to configure the equalization parameter for the 4WDX
channel unit.
21.11.1
Understanding Equalization for 4WDX Channel Units

Equalization is provided in the transmit path for either non-loaded or loaded cables.
It applies amplitude shaping to the voice frequency response of the channel unit
transmit path according to procedures described in AT&T BP 855-351-105.
Table 21.11-1 lists the equalization options available when equalization is enabled.
Table 21.11-1: Equalization Options for the 4WDX Channel Unit
Equalization Options
21.11.2
Description
Range
Loaded/non-loaded
This option enables operation in loaded

cable or non-loaded cable
configurations. It should be set to match
the cable being used.
LOADED/NON_LOADED
Slope
The slope option is the primary low

frequency control. If you set the slope to
0, no equalization occurs. If you set it to
15, it increases the 1 kHz gain to
+6.6 dB (loaded) or +11.4 dB
(non-loaded).
0 to 15, step size 1
Bump height
The bump height option is one of the

primary high-frequency equalization
controls. If you set the bump height to 0,
no equalization occurs. If you set it to 15,
it provides an equalization of +11 dB
gain relative to 1 kHz at 3250 Hz.
Bump bandwidth
The bump bandwidth option is one of the

primary high-frequency equalization
controls. It selects the width of the bump
at 3250 Hz. This option has no effect if
the bump height is set to zero.
Configuring Equalization for 4WDX Channel Units

Figure 21.11-1 shows a typical NMTI display, showing the options available for
equalization.
(400)
21.11-1
21.11 Equalization

NNP 95-2035-01-00-B
Figure 21.11-1: CONFIG CIRCUIT EQUALIZER NMTI Display

3600 MainStreet
Circuit
Name
1117-H1-00
Toronto:A
Alarms:1
11-May-1997
8:35a
Type
Function
Fault
A1-01-01
4W_DX
Rx 0,Tx 0
SEIZED Configured
Configured:
RX_TLP Range
:
TX_TLP Range
:
Line Impedance :
Line Balance
:
On-hook Tx Mute:
Companding Law :
Equalization
Facility
Slope
Height
Bandwidth
:
:
:
:
:
-10.5 to
-15.0 to
600 Ohms
N/A
Disabled
MuLaw
Disabled
Non-Loaded
0
0
0
Status
+6.0
+1.5
Signalling
Bias
Midpoint Cap
Build Out Cap
Build Out Res
:
:
:
:
:
Normal Polarity
Fixed
Enabled
4 uF
1250 ohms
CONFIG CIRCUIT 1-1-1 EQUALIZER
1-ENABLE
6-
2-LOADED
7-
3-SLOPE
8-CANCEL
4-HEIGHT
9-QUIT
5-BANDWIDTH
0-
To configure equalization for 4WDX channel units

Note
Equalization is disabled by default. For the facility, slope, height, and bandwidth
settings to have an effect on equalization, you must enable equalization first.
CONFIG CIRCUIT <sn-cc-1> MORE EQUALIZER
ENABLE/
DISABLE*
LOADED/
NON_LOADED*
SLOPE
HEIGHT
BANDWIDTH
SK000109
When equalization is disabled, the equalization settings do not reset to their default
values.
21.11-2
(400)

NNP 95-2035-01-00-B
22. Data Interface Cards

NNP 95-2035-01-00-B
22.1
22.1 Understanding Data Interface Card Configuration

Understanding Data Interface Card

Configuration
This chapter describes the data interface cards and provides:
the procedure for configuring the DCCs and the 2B1Q, 27LC2 and DNIC Line
22.1.1
cards
the procedure for configuring the 2B1Q, 27LC2 and DNIC Line cards for
connection to DTUs
a summary of the configuration procedures in this part of the manual, indicating
how they apply to each interface
Understanding Data Interface Cards

The 3600 MainStreet series bandwidth manager systems support the following types
of data interfaces: DCCs, 2B1Q, 27LC2 and DNIC Line cards, the 64 kb/s
Codirectional card, and four channel units. The channel units are: 2B1Q, 4WTO,
DS0-DP and OCU-DP. You can install the channel units in any module position of
the Common Carrier card. Chapter 19.1 describes the Common Carrier card.
Direct Connect cards

The DCCs are as follows.
The RS-232 DCC provides six full-duplex V.24/RS-232 interfaces that meet or
exceed TIA RS-232C and ITU-T V.24 electrical specifications.

The X.21 DCC provides four or six full-duplex interfaces that meet or exceed
ITU-T X.21 electrical specifications and meet a subset of EIA RS-449.
The V.35 DCC provides three or six interfaces that meet or exceed ITU-T V.35
electrical specifications.
The RS-422 DCC provides four full-duplex interfaces, each of which can be
independently configured as RS-530-A, RS-449 (V.36), X.21 or V.35.
You can install DCCs in any UCS 1 to 8 of a locally controlled or peripheral shelf.
(400)
22.1-1


NNP 95-2035-01-00-B
2B1Q, 27LC2 and DNIC Line cards

There are three types of line card: DNIC, 2B1Q and 27LC2 cards.
Each DNIC Line card circuit connects to three, six or twelve 2600 MainStreet
series DTUs. The DTUs can be located up to 5.8 km (3.6 mi) away, using a
standard twisted-pair wire.
Each 2B1Q Line card circuit connects to six 2700 MainStreet series DTUs. The
DTUs can be located up to 13.9 km (8.7 mi) away, using a standard twisted-pair
wire.
Each 27LC2 Line card circuit connects to six 2715 MainStreet DTUs. The DTUs
can be located up to 13.9 km (8.7 mi) away, using a standard twisted-pair wire.
You can install line cards in any UCS 1 to 8 of a locally controlled or peripheral shelf.
Table 22.1-1 lists card functions and indicates which ones apply to the DPM card
modules or variants.
Table 22.1-1: DNIC, 2B1Q and 27LC2 Line Card Functions
Line Card
Line Card and

DPM
Line Card and

DPM2
Function
Transparent/HCM rate adaption
DDS rate adaption
X.50 rate adaption
Transparent/HCM SRMs
64 kb/s random framing
DDS SRMs
X.50 SRMs
4 kb/s CPSS
Line cards connect to DTUs at the customer premises. The DTU connects to between
two and eight user data devices. Tables 22.1-2 and 22.1-3 list the 2600 MainStreet
series DTUs and 2700 MainStreet series DTUs.
Table 22.1-2: 2600 MainStreet Series DTU Types
DTU
22.1-2
Type
Device
Ports
Interface Type
2601
Synchronous or Asynchronous
V.24/RS-232
2602
Synchronous
X.21/V.11
2603
Synchronous
2606
2608
V.35
(1)
V.24/RS-232
Asynchronous
8 (1)
V.24/RS-232
(400)

NNP 95-2035-01-00-B

DTU
Type
Device
Ports
Interface Type
2610 (2)
Asynchronous CPSS PAD
2 (1)
V.24/RS-232
2611 (3)
Video termination unit
Video inputs (BNC)
2612
IBERT
V.24/RS-232
2613
Synchronous IBERT
V.35
2614
Synchronous FRAD
V.24/RS-232
Notes
1. All device ports must be configured identically.
2. The 2610 MainStreet DTU connects up to two asynchronous VT100-compatible devices to a 4602
MainStreet Intelligent NetworkStation or MainStreetXpress 46020 Network Manager over CPSS.
The 4602 MainStreet Intelligent NetworkStation or MainStreetXpress 46020 Network Manager then
supports an on-screen VT100 Terminal session.
3. On the interface, the 2611 MainStreet DTU is recognized as a 2603 MainStreet DTU
Table 22.1-3: 2700 MainStreet Series DTU Types

DTU
Type
Device Ports
Interface Type
2701
Synchronous or
Asynchronous
V.24/RS-232
2702
Synchronous
X.21/RS-449
2703
Synchronous
V.35
2704
Synchronous or
Asynchronous with V.110
Rate Adaption
V.24/RS-232
2715
Synchronous or
Asynchronous
V.24/RS-232 and V.35
2720
Fixed-link FRAD
Ethernet-attached IP
2721
Fixed-link FRAD
unlimited
Ethernet-attached IP
and/or IPX
64 kb/s Codirectional card

A 64 kb/s Co-directional card provides an interface between four full-duplex
synchronous circuits that conform to ITU-T specifications G.703 and four 64 kb/s
timeslots. You can install 64 kb/s Codirectional cards in any UCS 1 to 8 of a locally
controlled or peripheral shelf.
Table 22.1-4 lists card functions and indicates which ones apply to the card variants.
Chapters 20.9, 20.10 and 20.12 describe the primary rate functions of the card.
(400)
22.1-3


NNP 95-2035-01-00-B
Table 22.1-4: 64 kb/s Codirectional Card Functions

90-0470-01
90-0470-04
Function
Synchronization source
8 kHz timing
AIS enabling/disabling
Ability to transmit AIS
Ability to detect AIS
Trunk conditioning
Fault signalling
Custom trunk conditioning
Signalling types
Bidirectional connections
Unidirectional connections
2B1Q channel unit

The 2B1Q channel unit operates in either of two modes:
ISDN loop extension

2700 MainStreet series DTU support
In ISDN loop extension mode, the 2B1Q channel unit can operate in 3DS0 or 5DS0
transport mode, and act as line termination or network termination. In ISDN mode,
the channel unit is capable of processing the EOC in the M-channel stream according
to procedures defined in TR-TSY-000829. The channel unit also complies with T1.601
(for 2B1Q line code, electrical interface and layer 1 signalling protocol),
TR-NWT-000397 (for 3DS0 transport) and ITU-T-Q.512 (for 5DS0 transport).
In DTU support mode, the 2B1Q channel unit connects to a 2700 MainStreet series
DTU. Configuration procedures for a 2B1Q channel unit circuit in this mode are
identical to those for a line card.
22.1-4
(400)

NNP 95-2035-01-00-B

4WTO channel unit

You can use the 4WTO channel unit in any four-wire application when there is no
requirement for signalling. You can connect a 4WTO channel unit to circuits on the
following cards:
Single and Dual T1 card

Single and Dual E1 card
Test card DS0
X.21 PRI card
V.35 PRI card
four-wire E&M circuit (signalling is disabled)
4WTO Line card
4WTO channel unit
a circuit performing any type of voice compression
a circuit performing echo cancellation
a PCM multidrop input
DS0-DP channel unit

The DS0-DP channel unit provides an on-premise interface between a DS1 signal
and DS0 signal at a rate of 64 kb/s. The DS0-DP handles interface speeds of 2.4, 4.8,
9.6, 19.2, 56, and 64 kb/s. The channel unit is usually located in hub and intermediate
offices and interfaces DS1 equipment to DDS equipment.
The DS0-DP channel unit is compliant with TA-TSY-000077 and TR-TSY-000458.
OCU-DP channel unit

The OCU-DP channel unit provides a single user interface between an incoming
DS0-A stream and a four-wire synchronous digital data loop on customer premises.
It allows interconnection of customer premise DSUs or CSUs to the switched
network and handles interface speeds of 2.4, 4.8, 9.6, 19.2, 56 and 64 kb/s, with
secondary channel rates of 3.2, 6.4, 12.8, 25.6 and 72 kb/s. An interface speed of
64 kb/s does not support a corresponding secondary channel.
The OCU-DP channel unit is compatible with any DSU or CSU that meets PUB
62310, ANSI T1.403. The channel unit is compliant with TA-TSY-00077 and
TA-TSY-00083 and any switched 56 kb/s service provider-approved DSU or CSU.
Note
Of the channel units, only the DS0-DP and OCU-DP channel units respond to
OOS-A (see chapter 20.10).
(400)
22.1-5

22.1.2

NNP 95-2035-01-00-B
Configuring DCCs and Line Cards

Table 22.1-5 lists the steps to configure DCCs and line cards.
Table 22.1-5: DCC and Line Card Configuration Process
DCCs
Line Cards
Step
From the Locally Controlled or Peripheral Shelf
Configure data circuit parameters.
Configure branch channel parameters.
Configure SRM parameters.
From the Locally Controlled or Switching Shelf
22.1.3
Connect the data circuit to the SRM or a primary rate or data link.
Connect the data circuit to the branch channel or SRM.
Connect the SRM output to a primary rate circuit or another SRM.
Connecting DTUs
Most of the parameters you configure for the line cards are used to configure the
attached DTU.
Connecting 2600 and 2700 MainStreet series DTUs

To configure a DNIC Line card for connection to a 2601, 2602 or 2603 MainStreet
DTU, or to configure a 2B1Q or 27LC2 Line card or channel unit for connection to a
2701, 2702, 2703, 2704 or 2715 MainStreet DTU, you must follow these steps.
1.
Set the following parameters for the device connected to port A:
device mode and gender

transport bandwidth and
position
rate adaption method
data length, stop bits, parity
signalling, interface speed,
data position
clocking
RTS/CTS delay
multi-drop
control leads
duplex method
To configure the parameters for the DNIC, 2B1Q or 27LC2 Line cards, see
Table 22.1-7. The 2B1Q channel unit, when configured to support a 2700
MainStreet series DTU, has the same configuration parameters as do the DNIC
and 2B1Q Line cards.
22.1-6
(400)

NNP 95-2035-01-00-B

Note
For the 27LC2 line card with a firmware revision of 3 or greater, the EOC feature can
be enabled to provide loss of DTU connectivity reporting to the system.
2.
Set the same parameters for the device connected to port B.
Connecting a 2606 MainStreet DTU

To configure a DNIC Line card for connection to a 2606 MainStreet DTU, you must
follow these steps.
1.
Set the following parameters for aggregate port B (this configures aggregate
port A and all eight branch ports):

transport bandwidth and
position
interface speed and data
device mode
control leads
clocking
position
To configure the parameters for the DNIC Line cards, see Table 22.1-7.
2.
Connect aggregate port A to the DNIC Line card; port B is automatically

connected to aggregate port A.
Connecting a 2608 MainStreet DTU

follow these steps.
1.
Set the following parameters for aggregate port A:

transport bandwidth and position
interface speed and data position
2.
Set the following parameters for port B (which represents all eight branch
ports):
device mode
control leads
clocking
interface speed
(400)
22.1-7

3.

NNP 95-2035-01-00-B
Connect aggregate port A to the DNIC Line card; port B is automatically

connected to aggregate port A.
To connect 2610 MainStreet DTU CPSS PAD

follow these steps.
1.
Set the following parameters for port 1:
device mode
RTS/CTS delay
control leads
clocking
interface speed
2.
Set the same parameters for port 2.

Note

Network Manager configuration overrides branch port configuration for a 2610
MainStreet DTU. You can make connections only from the 4602 MainStreet
Intelligent NetworkStation or MainStreetXpress 46020 Network Manager.
22.1.4
Configuring Data Interface Cards

Table 22.1-6 lists the DCC configuration parameters. Each parameter has a list of
options with any default option marked by an asterisk.
Table 22.1-6: DCC Configuration Parameters and Options
RS-232
X.21
V.35
RS-422
Parameter
Options
CPSS
See Table 17.6-3.
Card type
RS-232 DCC
X.21 DCC
V.35 DCC
RS-422 DCC
Circuit number
3 circuit
4 circuit
6 circuit
Card Level
Slot Level
22.1-8
(400)

NNP 95-2035-01-00-B
RS-232
X.21
V.35
RS-422

Parameter
Options
Slip buffer module
slip buffer module

no module
Card operation
super-rate operation*
SRM operation
Interface type
RS-530-A*
RS-499/V.36
X.21
V.35
Circuit Level
Device mode
synchronous*
asynchronous
Device gender
DTE
DCE*
Duplex method
half duplex
full duplex*
RTS/CTS delay
0* to 1250 ms in 10 ms increments
RTS/CTS delay
LL and RL control leads
LL enable
LL disable
RL enable
RL disable
Control signals (gender: DCE/DTE)

DTR (I/O)
RTS (I/O)
ALB (I/O)
RDL (I/O)
DSR (O/I)
DCD (O/I)
CTS (O/I)
RI (O/I)
C (I/O)
I (O/I)
LL (I/O)
RL (I/O)
TM (O/I)
OOS signal on a data lead
mark
space
custom
OOS output control lead state
control lead is forced on

control lead is forced off
control lead maintains current state
Clocking type source (1)
internal
external
slave*
special (DCE external; slip buffer not
present)
(400)
high, low, end-to-end*

high, low (* for RS-422), end-to-end*
high (* for RS-422), low, end-to-end*
22.1-9


NNP 95-2035-01-00-B
RS-232
X.21
V.35
RS-422
Parameter
Options
Clocking source dependence (1)
independent
locked*
Receive clock inversion (1)
enabled
disabled*
Character length (2)
6 bits
7 bits
8 bits*
Stop bits (2)
1 bit*
2 bits
Parity (2)
no parity*
odd
even
mark
space
Inversion
enabled
disabled*
Slip buffer depth
0 bytes (buffer disabled)*

2 bytes
4 bytes
8 bytes
16 bytes
Control signal propagation
enable
disable*
RTS signal propagation
enable
disable
Super-rate circuit
transparent
enhanced transparent
V.35 circuit for AQA
master
slave
disabled*
Interface speed
See section 22.3.20.
Multidrop master/slave devices
master
slave
disabled*
Rate adaption methods
transparent
Multidrop Data Bridges (Circuit Level)
Rate Adaption (Circuit Level)
enhanced transparent (3)

HCM*
DDS
X.50
Transport bandwidth
1 to 8* (8 to 64 kb/s*)
Transport position
B7* to B0
22.1-10
(400)

NNP 95-2035-01-00-B

RS-232
X.21
V.35
RS-422
Parameter
Options
Signalling
switched on*
switched off
Data position for HCM
F0-B7 to F9 to B0 (* = F0-B5)
Subframe position for DDS
1 to 20 (* = 1 for 56, 9.6, 4.8, 2.4, 1.2

kb/s, or 2 for 19.2 kb/s)
Subframe position for X.50
1 to 20 (* = 1 for 0.6, 1.2, 2.4, 4.8, 9.6,

19.2 and 48 kb/s)
Interface speed (b/s) (4)

HCM sync
HCM async
150, 300, 600, 1200, 2400, 4800, 7200,

9600*, 14400, 19200 and 38400
DDS sync
1200, 2400, 4800, 9600* and 19200
DDS async
1200, 2400, 4800, 9600* and 19200
X.50 sync
1200, 2400, 4800, 9600* and 19200
800, 1200, 1600, 2400, 4000, 4800,

7200, 8000, 9600*, 12000, 14400,
16000, 16800, 19200, 24000, 28800,
32000 and 38400
40000, 48000, 56000 and 57600
56000
48000
n x m, where n = 2, 4, 6, 8, 10, 12, 14,
16, 18, 20, 22, 24, 26, 28 and 31 and m
= 64, 56, 48, 40, 32, 24, 16 and 8
Super-rates
SRM (Circuit Level)
transparent
HCM*
Transport bandwidth
1 to 8* (8 to 64 kb/s*)
HCM frame bandwidth
1 to 8* (8 kb/s to 64 kb/s*)
HCM frame bandwidth position
B7* to B0
Data position
F0-B7 to F9 to B0 (* = F0-B5)
Notes
1. This option applies only to synchronous interfaces.
2. This option applies only to asynchronous interfaces.
3. This option applies only to RS-422 DCCs.
4. In an RS-232 DCC, interface speeds greater than 38400 b/s are possible but not guaranteed. For speeds above 38400 b/s,
use V.35 or X.21 interfaces. If you try speeds above 38400 b/s for RS-232, use short-grade shielded cable.
(400)
22.1-11


NNP 95-2035-01-00-B
Table 22.1-7 lists the line card configuration parameters. Each parameter has a list of
Table 22.1-7: Line Card Configuration Parameters and Options
Parameter
Options
Slot Level
Card type
2B1Q
DNIC
Circuit number (1)
3 circuit
6 circuit
12 circuit
Module type
DPM
DPM2
none
Rate adaption method with a DPM2
HCM and transparent*

DDS
X.50
DDS Access
X.50 Telco
Hub ID (2)
2-digit octal number (00* to 77)
CPSS
See Table 17.6-2.
Circuit Level
22.1-12
Alarm suppression (3)
enabled
disabled
Device mode
synchronous*
asynchronous
Device gender
DTE
DCE*
Duplex method
half duplex
full duplex*
RTS/CTS delay
Control signals (gender: DCE/DTE)

DTR (I/O)
RTS (I/O)
ALB (I/O)
RDL (I/O)
DSR (O/I)
DCD (O/I)
CTS (O/I)
RI (O/I)

Clocking source type (4)
internal
external
slave*
Clocking source dependence (4)
independent
locked*
(400)

NNP 95-2035-01-00-B

Parameter
Options
Character length (5)
6 bits
7 bits
8 bits*
Stop bits (5)
1 bit*
2 bits
Parity (5)
no parity*
odd
even
mark
space
enable
disable*
enable
disable
Super-rate circuit
Multidrop Data Bridges (Circuit Level)

Multidrop master/slave devices
master
slave
disabled*
DTU Port Redundancy (Circuit Level) (6)

DTU port redundancy
enable
disable*
DTU mate ports
mate
no mate
DTU debounce synchronization timer
0 to 255000 ms in 1 ms increments
Node debounce synchronization timer
50 ms
250 ms
1000 ms
2000 ms
custom (0 to 300000 ms in 1 ms increments)
DTU forced activity switch
forced standby mode
Rate Adaption (Circuit Level)
transparent
HCM*
DDS
X.50
Transport bandwidth
1 to 8* (8 to 64 kb/s*)
Transport position
B7* to B0
Signalling
switched on*
switched off
(400)
22.1-13


NNP 95-2035-01-00-B
Parameter
Options
Interface speed (b/s) (7)

HCM sync
800, 1200, 1600, 2400, 4000, 4800, 7200, 8000,

9600*, 12000, 14000, 16000, 16800, 19200,
24000, 28800, 32000, 38400, 40000, 48000,
56000 and 57600
HCM async
150, 300, 600, 1200, 2400, 4800, 7200, 9600*,

14400, 19200 and 38400
DDS sync
1200, 2400, 4800, 9600*, 19200 and 56000
DDS async
1200, 2400, 4800, 9600* and 19200
X.50 sync
1200, 2400, 4800, 9600*, 19200 and 48000
Data position
F0-B7 to F9 to B0 (* = F0-B5)
Subframe position for DDS
1 to 20 (* = 1 for 56, 9.6, 4.8, 2.4, 1.2 kb/s, or 2

for 19.2 kb/s)
Subframe position for X.50
1 to 20 (* = 1 for 1.2, 2.4, 4.8, 9.6, 48 and 19.2

kb/s)
SRMs (Circuit Level)

transparent
HCM*
DDS-HCM
X.50
Transport bandwidth
1 to 8* (8 to 64 kb/s*)
HCM frame bandwidth
1 to 8* (8 to 64 kb/s*)
B7* to B0
Interface speed
See Rate adaption in this table.
Continuity checking
enabled
disabled*
Branch Channels (Circuit Level)
22.1-14
transparent
HCM*
DDS-HCM
X.50
Transport bandwidth
1 to 8* (8 to 64 kb/s*)
Transport position
B7* to B0
Signalling
switched on*
switched off
Interface speed
See Rate adaption in this table.
Data position
F0-B7 to F9 to B0 (* = F0-B5)
Composite inputs
composite
not composite*
Input specification
system*
user
(400)

NNP 95-2035-01-00-B

Parameter
Options
DDS multidrop slave branch ID
0 to 4
Embedded Operations Channel (Circuit Level) (8)

EOC
enabled
disabled*
Notes
1. This parameter applies only to DNIC cards.
2. This parameter applies only when the line card is configured for DDS or DDS access.
3. Alarm suppression is available only on the 27LC2 and six-circuit DNIC Line cards with a variant ID
of $2.
4. This option applies only to synchronous interfaces.
5. This option applies only to asynchronous interfaces.
6. These parameters apply only to a 2715 MainStreet DTU.
7. In an RS-232 DCC, interface speeds greater than 38400 b/s are possible but not guaranteed. For
speeds above 38400 b/s, use V.35 or X.21 interfaces. If you try speeds above 38400 b/s for RS-232,
use short-grade shielded cable.
8. This option applies only to the 27LC2 line card.
Table 22.1-8 lists the 64 kb/s Codirectional card configuration parameters. Each
parameter has a list of options with any default option marked with an asterisk.
Table 22.1-8: 64 kb/s Codirectional Card Configuration Parameters and Options
Parameter
Options
Slot Level
Card slot
64 kb/s Codirectional
Trunk conditioning
one-way
two-way*
Alarm time
Declare
Clear
0.1 to 60 s
0.1 to 60 s
Circuit Level
Fault signalling
seized
idle*
OOS-A
OOS-B
none
(400)
22.1-15


NNP 95-2035-01-00-B
Parameter
Options
Signalling types for E1 signalling
transparent*
clear channel
E&M
continuous E&M
LGS RE
LGS EC
LGS PLAR
LGE RE
LGE EC
Signalling types for R2 digital signalling
Signalling types for T1 signalling
transparent
clear channel
E&M
LGS LS
LGS GS
LGS PLAR
LGS PLAR D3
LGE LS
LGE GS
Terminate
8 kHz timing
generates the timing continuously, whether or not the

circuit is connected
interrupts the timing when the circuit is connected*
AIS
enabled so that it is sent when the circuit is not

connected*
disabled so that it is not sent
Table 22.1-9 lists the DS0-DP channel unit configuration parameters. Each parameter
Table 22.1-9: DS0-DP Channel Unit Configuration Parameters and Options
Parameter
Options
Slot Level
Card type
DS0-DP
Circuit Level
22.1-16
Fault signalling
MOS*
CMI
Interface speed
2.4 kb/s
4.8 kb/s
9.6 kb/s*
19.2 kb/s
56 kb/s
64 kb/s
Error correction
enabled*
disabled
(400)

NNP 95-2035-01-00-B

Table 22.1-10 lists the OCU-DP channel unit configuration parameters. Each
parameter has a list of options with any default option marked by an asterisk.
Table 22.1-10: OCU-DP Channel Unit Configuration Parameters and Options
Parameter
Options
Slot Level
Card type
OCU-DP
Circuit Level
Fault signalling
seized*
idle
Interface speed
2.4 kb/s
4.8 kb/s
9.6 kb/s*
19.2 kb/s
56 kb/s
64 kb/s
Error correction
enabled*
disabled
Secondary channel operation
enabled
disabled*
Switched 56 kb/s operation
enabled
disabled*
Table 22.1-11 lists the 4WTO channel unit configuration parameters. Each parameter
Table 22.1-11: 4WTO Channel Unit Configuration Parameters and Options
Parameter
Options
Slot Level
Card type
4WTO
TLP level
Tx TPL
Rx TPL
17.0 to +13.0 (+13.0)

16.0 to +8.0 (3.0)
Circuit Level
Sealing current
enabled
disabled*
Table 22.1-12 lists the 2B1Q channel unit configuration parameters when it is
configured for 3DS0 and 5DS0 ISDN loop extension mode. Each parameter has a list
The 2B1Q channel unit, when configured to support a 2700 MainStreet series DTU,
has the same configuration parameters as do the DNIC, 2B1Q and 27LC2 Line cards.
For a list of the configuration parameters, see Table 22.1-7.
(400)
22.1-17


NNP 95-2035-01-00-B
Table 22.1-12: 2B1Q Channel Unit Configuration Parameters and Options

Parameter
Options
Slot Level
Card slot
2B1Q
Channel unit application
DTU*
loop extension
Transport mode (1)
3DS0
5DS0
Interface mode (2)
LULT*
LUNT
Circuit Level
Performance monitoring
enabled*
disabled
Zero byte substitution (3)
enabled*
disabled
D channel mode (4)
low nibble*
high nibble
Notes
1. This parameter is available only for the channel unit loop extension application.
2. This parameter is available only for 3DS0 or 5DS0 transport modes.
3. This parameter is available only for 3DS0 transport mode.
4. This parameter is available only for 5DS0 transport mode.
Note
chapter 16.4.
22.1-18
(400)

NNP 95-2035-01-00-B
22.2
22.2 Data Interface Card Slots

Data Interface Card Slots

This chapter describes how to configure the card slots for the DCCs, line cards and
64 kb/s Codirectional cards. It also describes how to configure channel unit
positions in the Common Carrier card.
22.2.1
Understanding Data Interface Card Slots

You must configure card slots for the data interface cards and channel units before
you can configure or connect circuits. Configuring a slot type means programming
a card slot to accept a specific card type with specific card parameters. When a slot
is configured, the circuits for that slot are configured with default settings.
Note
simultaneously.
22.2.2
Configuring DCC slots

You configure all the DCCs for card type. The V.24/RS-232 DCC has no other card
slot options, but you configure the X.21 and V.35 DCCs for the number of circuits on
the card and super-rate or subrate operation. You configure the RS-422 DCC for
whether it has a Slip Buffer module.
Configure the X.21 and V.35 DCC circuit number as:
3_CIRCUIT for three V.35 circuits

4_CIRCUIT for four X.21 circuits
6_CIRCUIT for six circuits
Configure X.21 and V.35 DCC operation as:
SUPER_RATE for super-rate operation

SRM for subrate operation
Configure the RS-422 Slip Buffer module as:
BUF_MOD if there is a Slip Buffer module

NO_MODULE if there is no Slip Buffer module
(400)
22.2-1


NNP 95-2035-01-00-B
To configure DCC slots

CONFIG SLOT <sn>
TYPE
AS_PRESENT
OPTIONS
DATA
SUPER_RATE* SRM NO_MODULE* BUF_MOD
DCC
RS-232_DCC
X.21_DCC
4_CIRCUIT
V.35_DCC
6_CIRCUIT
3_CIRCUIT
RS-422_DCC
6_CIRCUIT
SK000110
Note
Use the AS_PRESENT softkey if the card is installed in the slot.
22.2.3
Configuring Line Card Slots

You configure all the line cards for card type, the number of circuits on the card and
whether it has an optional DPM.
Configure the circuit number as:
3_CIRCUIT for three DNIC circuits

6_CIRCUIT for six DNIC, 2B1Q or 27LC2 circuits
12_CIRCUIT for twelve DNIC circuits
Configure the DPM as:
DPM for the DPM module

DPM2 for the DPM2 module
NO_DPM if there is no module
22.2-2
(400)

NNP 95-2035-01-00-B

If you configure the card with DPM2, you must specify the rate adaption method
(METHOD) as:
HCM_TRANS for high-capacity multiplexing transparent

DDS for Dataphone Digital Service
X.50 for X.50 operation
DDS_ACCESS for Dataphone Digital Service access
X50_TELCO for X.50 telecom operation
If you configure the card for DDS_ACCESS, you must select VERSION_1 or
VERSION_2.
If you configure the card for DDS or DDS_ACCESS, you can set a hub identification
with the HUB_ID softkey.
If you configure the card for X.50_TELCO, you must select DIV_2 or DIV_3.
If you have a 27LC2 line card, configure the slot type as 2B1Q. When you physically
insert the 27LC2 line card into the slot, the system recognizes the correct card type.
To configure line card slots

CONFIG SLOT <sn>
TYPE
OPTIONS
AS_PRESENT
DATA
MORE
DNIC
NO_DPM*
DPM
DPM2 METHOD HUB_ID

<id>
2B1Q
HCM_TRANS* DDS X.50 DDS_ACCESS X50_TELCO
3_CIRCUIT
6_CIRCUIT
12_CIRCUIT
DIV_2
VERSION_1
DIV_3
VERSION_2
SK000111
where id is a two-digit octal code number (00* to 77)
(400)
22.2-3


NNP 95-2035-01-00-B
Note
Use the AS_PRESENT softkey if the card is installed in the slot.
22.2.4
Configuring 64 kb/s Codirectional Card Slots

You configure the 64 kb/s Codirectional card for card type and for trunk
conditioning. (For trunk conditioning, see chapter 20.9.)
To configure 64 kb/s Codirectional card slots

CONFIG SLOT <sn> TYPE DATA 64K_CODIR
22.2.5
Configuring Data Interface Channel Unit Slots

Before you configure a channel unit, you must configure the slot for a Common
Carrier card (see chapter 19.3). Then you can configure the Common Carrier card
position for the type of channel unit as:
DATA DS-0_DP for the DS0-DP channel unit

DATA OCU_DP for the OCU-DP channel unit
DATA 4W_TO for the 4WTO channel unit
DATA 2B1Q for the 2B1Q channel unit
For the 2B1Q channel unit, you must also configure the unit application as one of the
following:
DTU for 2700 MainStreet series DTU support

LOOP_EXT and 3_DS0 for 3DS0 transport ISDN loop extension
LOOP_EXT and 5_DS0 for 5DS0 transport ISDN loop extension
If you select either ISDN loop extension mode, you must specify the interface mode
of the channel unit as one of the following:
LULT for line termination

LUNT for network termination
22.2-4
(400)

NNP 95-2035-01-00-B

Note
When you change a 2B1Q channel unit application, the system removes any existing
connections to the unit. For more information on 2B1Q channel unit applications, see
section 22.3.25.
To configure data interface channel unit slots

CONFIG SLOT <sn-cc> TYPE DATA
DS-0_DP
OCU_DP
2B1Q
4W_TO
SK000112
where
sn is the Common Carrier card slot
cc is the position number of the channel unit (1 to 4)
To configure unit applications for a 2B1Q channel unit

CONFIG SLOT <sn-cc> OPTIONS
APP
DTU*
I/F_MODE
LOOP_EXT
3_DS0
LULT*
LUNT
5_DS0
SK001047
where
sn is the Common Carrier card slot
cc is the position number of the 2B1Q channel unit (1 to 4)
(400)
22.2-5

NNP 95-2035-01-00-B
22.3
22.3 Data Interface Circuits

Data Interface Circuits

This chapter describes how to configure circuits for the data interface cards.
22.3.1
Understanding Data Interface Circuit Parameters

Data interface circuits can be configured for:
22.3.2
DCCs
Line cards
64 kb/s Codirectional cards
DS0-DP channel units
OCU-DP channel units
4WTO channel units
2B1Q channel units
Configuring Interface Type

You can configure each RS-422 DCC circuit independently as any one of the
following interface types:
RS-530 for RS-530-A

RS-499/V.36 for RS-499 V.36
X.21 for X.21
V.35 for V.35
To configure interface type

CONFIG CIRCUIT <sn-cc> FUNCTION I/F_MODE I/F_TYPE
RS-530*
RS-499/V.36
X.21
V.35
SK000113
(400)
22.3-1

22.3.3

NNP 95-2035-01-00-B
Configuring Device Mode

You can configure DCC and line card circuits for synchronous or asynchronous
operation.
Asynchronous devices transmit data one character at a time. A byte (5, 6, 7, 8 or 9
bits) represents one character, with start and stop bits used to mark the beginning
and end of that character. A circuit configured for transparent rate adaption cannot
transmit asynchronous data (see chapter 22.4).
Synchronous devices transmit a continuous stream of characters. Timing signals
transmitted on separate conductors maintain synchronization between the devices.
For the 2608 MainStreet DTU, the A circuit (sn-cc-A), which configures the aggregate
port, is always synchronous and the B circuit (sn-cc-B), which configures the branch
ports, is always asynchronous.
Configure each DCC or line card circuit as:
SYNC for synchronous (default)

ASYNC for asynchronous
To configure device mode
CONFIG CIRCUIT <sn-cc> or <sn-cc-p> FUNCTION I/F_MODE
ASYNC/SYNC*
22.3.4
Configuring Device Gender

You can configure DCC and line card circuits to support one of two device genders:
DTE or DCE.
Data and control signals are transmitted and received on wire pairs. The gender of
a device indicates which wire in the pair is used to send and receive the signal. A
DTE device sends data or control signals on one wire in the pair; a DCE device sends
signals on the other wire. For example, the TXD signal indicates that data has been
transmitted by a DTE and received by a DCE; the RXD signal indicates that data has
been received by a DTE but transmitted by a DCE.
In general, terminals and printers are DTE and modems are DCE. However, there
are many exceptions. If the device owner manual indicates with words or graphics
that the TXD signal is outgoing, the device is DTE; if it is incoming, the device is
DCE. The opposite is true for RXD.
22.3-2
(400)

NNP 95-2035-01-00-B

Note
To change the gender offered by a DCC interface, you must change the cable or the
headshell or both. When the UDP is used with an RS-422 DCC, you must change the
interface module.
Configure the DCC or line card circuits as:
DTE if the connected device is DCE

DCE if the connected device is DTE (default)
To configure device gender
CONFIG CIRCUIT <sn-cc> or <sn-cc-p> FUNCTION I/F_MODE DTE/DCE*
22.3.5
Configuring Duplex Method

You can configure DCC and line card circuits to support either of two device
genders: half-duplex or full-duplex.
Half-duplex transmission uses a single transmission path, so that two connected
devices can transmit and receive, but not at the same time. If you select half duplex,
you can configure the RTS/CTS delay parameter.
Full-duplex transmission uses two independent transmission paths, one in each
direction, allowing two connected devices to transmit and receive data
simultaneously.
Configure a DCC or line card circuit as:
HALF_DPLX if the connected device is half duplex

FULL_DPLX if the connected device is full duplex (default)
To configure duplex method
CONFIG CIRCUIT <sn-cc> or <sn-cc-p> FUNCTION I/F_MODE
HALF_DPLX/FULL_DPLX*
(400)
22.3-3

22.3.6

NNP 95-2035-01-00-B
Configuring RTS/CTS Delay

RTS and CTS are control signals that regulate the direction of data flow on
half-duplex lines. When one device sends a message to another, it sends RTS. The
modem connected to the receiving device returns CTS after a time delay. This time
delay, called RTS/CTS delay, must be long enough to allow the line to be cleared of
any messages coming into the device.
For example, the RTS/CTS delay is used in multidrop data bridges to make a slave
device wait long enough to guarantee that there is a transmission path to the master
device. An RTS/CTS delay that is too short causes messages to be lost on the line. A
delay that is too long decreases response time. The optimal value depends on the
individual network.
To configure RTS/CTS delay

CONFIG CIRCUIT <sn-cc> or <sn-cc-p> FUNCTION I/F_MODE RTS/CTS
<delay_time>
where delay_time is from 0* to 1250 ms in 10 ms increments (for RS-232, X.21 and V.35 DCCs and line
cards) or 0* to 160 ms in 5 ms increments (for RS-422 DCCs)
Note
You can set the RTS/CTS delay only when a circuit is configured with half-duplex
mode (see section 22.3.5) or as a multidrop slave (see section 22.3.12).
22.3.7
Configuring Control Signals

Control signals provide the handshaking for call set-up, tear-down and
synchronization. To determine which pins of the connectors on a DCC or line card
(backplane or faceplate) carry the various control signals, see Installation, Task 1605:
Connecting External Devices to Peripheral, Enhanced Locally Controlled or Locally
Controlled Shelves.
Table 22.3-1 lists the configurable control signals and indicates the data interface
cards to which they apply.
Table 22.3-1: Control Signals
RS-232 and
V.35 DCCs
X.21
DCC
RS-422
DCC (1)
Line
Card
22.3-4
Signal
Parameter
Analog Loopback
ALB
Control
Clear to Send
CTS
Data Carrier Detect
DCD
Data Set Ready
DSR
(400)

NNP 95-2035-01-00-B
RS-232 and
V.35 DCCs
X.21
DCC

RS-422
DCC (1)
Line
Card
Signal
Parameter
Data Terminal Ready
DTR
Indication
Local Loopback
LL
Remote Digital Loopback
RDL
Ring Indicator
RI
Remote Loopback
RL
Request to Send
RTS
Test Mode
TM
Notes
1. Control signals for RS-422 DCCs depend on the interface mode selected.
If the device is DTE, the inputs are DSR, DCD, CTS and RI and the outputs are DTR,
RTS, ALB and RDL. If the device is DCE, the inputs and outputs are reversed.
You can configure three types of parameters related to control leads:
LL and RL leads (enabling or disabling them for RS-422 DCC circuits)

control signals
OOS conditioning (for RS-422 DCC circuits)
Enabling or disabling LL and RL control leads
Before you can configure LL and RL leads for RS-422 DCC circuits, you must enable
them. Configure the control leads as:
LL_ENABLE or LL_DISABLE to enable or disable the LL lead

RL_ENABLE or RL_DISABLE to enable or disable the RL lead
To enable or disable LL and RL control leads, see the procedure To configure
control signals.
Configuring control signals

You can configure control signals as high (ASSUMED_ON or FORCED_ON), low
(ASSUMED_OFF or FORCED_OFF), or end-to-end (END-TO-END). In end-to-end
configuration, the state of the local signal follows that of the signal source at the
remote end of the network.
Inputs are ASSUMED_ON or ASSUMED_OFF and outputs are FORCED_ON or
FORCED_OFF. Table 22.3-2 lists the defaults.
(400)
22.3-5


NNP 95-2035-01-00-B
Table 22.3-2: Control Signal Input and Output Defaults

Control Signal Input
Default
Control Signal
Output
Default
DCE Gender
DTR
END_TO_END
DSR
FORCED_ON
RTS
END_TO_END
DCD
END_TO_END (1)
ALB
END_TO_END
CTS
END_TO_END (1)
RDL
END_TO_END
TM
FORCED_OFF
LL
END_TO_END
END_TO_END
RL
END_TO_END
RI
FORCED_OFF
END_TO_END
DTE Gender
DSR
END_TO_END
DTR
FORCED_ON
DCD
END_TO_END (1)
RTS
END_TO_END
CTS
END_TO_END (1)
ALB
END_TO_END
TM
END_TO_END
RDL
FORCED_OFF
END_TO_END
LL
END_TO_END
RI
END_TO_END
RL
FORCED_OFF
END_TO_END
Notes
1. For HCM rate adaption, the default setting is END_TO_END. For DDS and X.50 rate adaption, the
default is FORCED_ON.
For 5 kb/s transparent channels, the system forces the value of RTS into bit position
eight when RTS is set to end-to-end. For a DNIC, 2B1Q or 27LC2 Line card, the
far-end DTU maps RTS to its own DCD lead going to DTE devices. With both DTUs
configured for end-to-end, the system maps RTS (in bit position eight) to DCD.
When a V.35 circuit is an AQA master, the system sets DTR to forced off; when it is
an AQA slave, the system sets DTR to forced on. Do not change the control leads;
any change could cause a protecting call to be dropped.
When an SRM on a DCC card carries both HCM and transparent rate adapted
circuits, the state of the RTS (for DCE) or DCD (for DTE) control signal follows that
of the transparent circuit. This will disrupt the HCM circuits unless the transparent
circuit's RTS (or DCD) signal is set to ASSUMED_ON.
For the 2602 MainStreet DTU, the system displays:
the control signal (C) as RTS if it is DTE

C as DCD if it is DCE
the indicator signal (I) as DCD if it is DTE
I as RTS if it is DCE.
The other control signals are not used.
22.3-6
(400)

NNP 95-2035-01-00-B

The 2608 MainStreet DTU B circuit (sn-cc-B), which configures the branch ports,
supports only two inputs (DTR and RTS) and two outputs (DSR and DCD). The
circuit is always DCE. This parameter is not relevant to the A circuit (sn-cc-A), which
configures the aggregate port.
The control signals parameter is the only interface parameter that you can set for a
circuit that is configured as a source of system synchronization. It is also the only
interface parameter that you can change if a circuit is connected.
Configure control signals as:
ASSUMED_ON or FORCED_ON for high

ASSUMED_OFF or FORCED_OFF for low
END-TO-END for end-to-end
To configure control signals
CONFIG CIRCUIT <sn-cc> or <sn-cc-p> FUNCTION CTRL_LEADS
INPUTS or
OUTPUTS
DTR
RTS
LL
RL
ALB
ON
RDL
RL_ENABLE/
RL_DISABLE*
LL_ENABLE/
LL_DISABLE*
OFF
DSR
DCD
CTS
TM
RI
END_TO_END
SK000114
Configuring OOS conditioning

When an HCM or enhanced transparent RS-422 DCC circuit loses HCM
synchronization (for example, because of a link failure), an OOS condition is
declared. For each of these circuits, you can configure the signal transmitted on the
output data leads during an OOS condition. You can also configure the state of each
output control lead during this condition.
To configure the signal transmitted on the data leads, select OOS_DATA and:
MARK to transmit all ones

SPACE to transmit all zeros
CUSTOM to define an eight-bit binary value for repeated transmission
Select the output control lead and configure its state during an OOS condition as:
ON for the control lead to be forced on (transmits mark)

OFF for the control lead to be forced off (transmits space)
NONE for the control lead to maintain its current state
(400)
22.3-7


NNP 95-2035-01-00-B
To configure OOS conditioning

CONFIG CIRCUIT <sn-cc> or <sn-cc-p> FUNCTION
CTRL_LEADS
MORE
OUTPUTS
DSR
DCD
CTS
OOS_DATA
DTR
RTS
ALB
RDL
TM
LL
RL
OOS
MARK
ON
OFF
NONE
SPACE
CUSTOM
<bits>
SK000115
where bits is an eight-bit binary value
22.3.8
Configuring Clocking
Clocking applies only to synchronous data interface devices. Synchronous devices
require two timing sources: a receive clock for receive data and a transmit clock for
transmit data. Transmit and receive are defined relative to the device configured as
DTE, so that the transmit clock is used by the DTE to transmit data and by the DCE
to receive data. Figure 22.3-1 illustrates transmit and receive clocks.
Figure 22.3-1: Transmit and Receive Clocks
Transmit clock
Transmit data
DTE
data
device
DCE
data
device
Receive data
Receive clock
1535
You can configure the transmit clock for all DCCs and line cards and receive clock
inversion for RS-422 DCCs.
22.3-8
(400)

NNP 95-2035-01-00-B

Transmit clock
You can configure the source of the transmit clock between a DCC or line card circuit
and the attached local device as: the attached device (external), the DCC or line card
circuit (internal), or a remote source (slave). Setting this parameter depends on the
gender of the attached device and the gender (or device mode) of the connected DCC
or line card circuit (see Table 22.3-3).
Table 22.3-3: Transmit Clock Options
Attached
Device
Gender
DTE
DCE
Circuit
Gender
DTE
Transmit
Clock
Option
Description
DCE
External
DCE external: the transmit clock is provided by the attached device (the
XCLK pin from the DTE). The receive clock is derived from the XCLK.
Internal
DCE internal: the transmit clock is provided by an internal BRG (Baud Rate
Generator) on the DCC. The BRG is locked to the system timing. This mode
is not recommended; use DCE slave instead.
Slave
DCE slave: the transmit and receive clocks are derived from the BRG locked
to the system timing.
External
DTE external: the transmit clock is provided by the attached device (the
XCLK pin from the DCE). The receive clock is derived from the BRG.
Internal
DTE internal: not always valid if the interface is in DTE mode. Use slave or
external instead.
Slave
DTE slave: the transmit clock and the receive clock are supplied by the
attached DCE device (this is the default mode).
Clock locked or independent

You can also configure the effect of the system on clocks passing through it. Clocking
can be configured as locked or independent.
Locked clocking indicates that HCM speed correction is turned off. When you
configure locked clocking on a DCE interface, the receive clock comes from the BRG,
which derives its timing from the system clock. When you configure it on a DTE
interface and select external clocking, the transmit clock comes from the BRG.
Independent clocking indicates that the data clocks are passing through the system
transparently and that HCM speed correction is enabled on receive and transmit
data streams. The DCE interface generates a receive clock from the speed-corrected
data on a PLL. If you select external clocking on a DTE interface, the system
generates a transmit clock from the speed-corrected transmit data on the PLL.
If the clocking for a circuit is independent, the system embeds clocking information
in the signalling bit of an HCM frame and passes it through the system
transparently, accommodating deviations of up to 50 b/s relative to the nominal
rate.
(400)
22.3-9


NNP 95-2035-01-00-B
Note
Data interfaces configured for external independent clocking do not support
1.2 kb/s operation (see section 22.3.20).
RS-422 DCC clocking

As Figure 22.3-2 shows, the RS-422 DCC is made up of a DRAGA and an SBM. The
DRAGA provides an internal FIFO buffer that handles data exchanges between the
serial bus and the synchronous DCC interface. The DRAGA always offers a
hardware DCE to the synchronous DCC interface (or SBM if installed).
Figure 22.3-2: RS-422 DCC Hardware Genders
Circuit Gender Interface
DCE or DTE
DRAGA
Rx FIFO
Attached
Equipment
Gender
DTE or DCE
FIFO module
DTE
DCE
Tx FIFO
DTE
Rx FIFO
Tx FIFO
3435
The SBM provides a second FIFO that handles data exchanges between the DRAGA
and the synchronous DCC interface. It is designed to accommodate slips and
Doppler effects common in satellite tail circuits and plesiochronous applications.
The SBM always offers a hardware DTE to both the DRAGA and the synchronous
DCC interface (see Technical Overview, chapter 7.3).
The configuration of the following four parameters determines which clocks are
used to clock data to and from the RS-422 DCC:
circuit interface type (RS-530, RS-449/V.36, X.21 or V.35)

circuit gender
circuit clocking mode
SBM configuration (present or not present)
Table 22.3-4 lists the configurations supported by the RS-422 DCC.

DCE external (SBM present) is also called DTE1 Mode and DTE slave (SBM present)
is also called DTE2 Mode. Special DCE external (SBM not present) is designed to
compensate for clock delays caused by long runs of wire at high speeds.
22.3-10
(400)

NNP 95-2035-01-00-B

Table 22.3-4: RS-422 DCC Clocking Configurations

Clocking Configuration (1)
Interface Type
SBM Not Present

DCE slave
RS-530, RS-449/V.36, X.21, V.35
DTE slave
RS-530, RS-449/V.36, X.21, V.35 (2)
DCE external (3)
RS-530, RS-449/V.36, X.21, V.35
DTE external
RS-530, RS-449/V.36, X.21, V.35
Special DCE external
RS-530, RS-449/V.36, V.35 (2)
DCE internal
RS-530, RS-449/V.36, X.21, V.35
DTE internal
RS-530, RS-449/V.36, X.21, V.35 (2)
SBM Present
DCE external (DTE1 Mode)
RS-530, RS-449/V.36, X.21, V.35
DTE slave (DTE2 Mode)
RS-530, RS-449/V.36, X.21, V.35
Notes
1. DCE and DTE refer to RS-422 DCC circuit gender. All configurations can be further configured as
either locked or independent.
2. This mode is incompatible with existing DCCs. The RS-422 DCC supports separate SCT and SCR
clocks for RS-530-A, RS-449/V.36 and V.35 operation.
3. This mode is compatible with existing DCCs with firmware ID $09 or higher.
Configuration limitations
The following limitations apply to configuring clocking.
If a circuit is using transparent rate adaption, you must define clocking as

external locked or slave locked.
If a DCC or line card circuit is configured as a synchronization source, you must
define the circuit with external clocking mode if it is DCE and slave clocking
mode if it is DTE.
The 2704 MainStreet DTU does not support any DTE clocking modes.
Table 22.3-5 lists some combinations of clocking options for DCCs and line cards
with DTUs for the configuration shown in Figure 22.3-3. (For more information on
clocking, ask your Newbridge representative for Configuration Note NCN305.)
(400)
22.3-11


NNP 95-2035-01-00-B
Figure 22.3-3: DCC/DTU Clocking Applications

3600 MainStreet
node
Newbridge
Network
Host
DTU2
or DCC2
(DCE)
36120
MainStreet
node
Data
Network
Modem
or NTU
Terminal
Modem
or NTU
DTU1
or DCC1
(DTE)
DTU1
or DCC1
(DCE)
Terminal
7155
Table 22.3-5: DCC/DTU Clocking

DCC/DTU1
(DCE)
DCC/DTU2
(DCE)
HCM
Transparent
Application (Figure 22.3-3)
Slave
locked
Slave
locked
Yes
Yes
Default. Used when data network is

integrated with the network.
Slave
locked
External
locked
Yes
Yes
Used when DCC2/DTU2 is configured as a

source of network timing.
Slave
independent
External
independent
Yes
No
Used when clocking is independent of the

network.
Slave
locked
Slave
locked
Yes
Yes
Default. Used when:

1. The data network is locked to the network.
2. DCC1/DTU1 is getting network timing from
the data network.
External
locked
Slave
locked
Yes
Yes
Used when the data network timing is locked

to the network timing.
Slave
independent
Slave
independent
Yes
No
Used when modems are providing the

clocking independent of the network.
Configuring transmit clock

Configure the transmit clock for a circuit as:
22.3-12
INTERNAL for an internal clock

EXTERNAL for an external clock
SLAVE for a slave clock (DCE SLAVE is the default)
SPECIAL for special RS-422 DCC clocking
(400)

NNP 95-2035-01-00-B

Configure locked or independent clocking for the circuit as:
LOCKED for locked clocking (default)

INDEPNT for independent clocking
Receive clock inversion
For RS-422 DCC circuits, you can invert the receive clock. Configure the receive
clock as:
RX_INV to invert all ones to zeros and all zeros to ones

NO_RX_INV to accept the receive clock as provided (default)
To configure clocking
CONFIG CIRCUIT <sn-cc> or <sn-cc-p> FUNCTION CLOCKING
MODE
INTERNAL
SLAVE*
INDEPNT/LOCKED*
EXTERNAL
RX_INV/
NO_RX_INV*
SPECIAL
SK000116
Note 1
The SPECIAL and RX_INV/NO_RX_INV options apply only to RS-422 DCC
circuits.
Note 2
Clocking can only be configured for DCC and line card circuits operating in
synchronous mode.
22.3.9
Configuring Character Length, Stop Bits and Parity

You can configure character length, stop bits and parity for DCC and line card
circuits operating in asynchronous mode. Character length is the number of data bits
used to transmit a character in asynchronous transmission and stop bits signify the
end of a character. Parity is an error detection method that adds an extra bit to each
transmitted character, based on the number of 0s or 1s in each character.
The sum of the start bit (always 1), the character length (6, 7 or 8), the stop bits (1 or 2)
and the parity (0 for no parity or 1 for odd, even, mark or space) must equal 8, 9, 10
or 11. For example, if the character length is set to 5 bits and the number of stop bits
is set to 1 bit, you must set the parity to odd, even, mark, or space. If the character
length is set to 8 bits and the number of stop bits is set to 2 bits, you must set parity
to none.
(400)
22.3-13


NNP 95-2035-01-00-B
Note
For the 2608 MainStreet DTU, character length, stop bits and parity can be set for the
B circuit (sn-cc-B), which configures the asynchronous branch ports. It is not relevant
to the A circuit (sn-cc-A), which configures the synchronous aggregate port.
To configure character length, stop bits and parity

CONFIG CIRCUIT <sn-cc> or <sn-cc-p> FUNCTION
STOP_BITS
CHAR_LEN
6_BITS
7_BITS
8_BITS
1_BIT*
NONE*
PARITY
2_BITS
ODD
EVEN
MARK
SPACE
SK000117
Note
Character length, stop bits and parity can only be configured for DCC and line card
circuits operating in asynchronous mode.
22.3.10
Configuring Inversion
You can configure RS-422 DCC circuits to invert data and signalling bits at the
interface. Inversion is sometimes necessary to maintain line synchronization by
ensuring a sufficient ones density.
Configure inversion as:
INVERT to cause all ones to be inverted to zeros and all zeros to ones
NORMAL to cause all bits to be transmitted and received in their normal state
(default)
To configure inversion
CONFIG CIRCUIT <sn-cc> or <sn-cc-p> FUNCTION I/F_MODE MORE
INVERT/NORMAL*
22.3-14
(400)

NNP 95-2035-01-00-B
22.3.11

Configuring SBM Depth

When the SBM is present on the RS-422 DCC, each circuit has a bidirectional FIFO
buffer. You can configure the depth of the buffer (the number of bytes buffered)
independently for each circuit as:
DISABLE for 0 bytes (default)

2_BYTES for two bytes
4_BYTES for four bytes
8_BYTES for eight bytes
16_BYTES for 16 bytes
To configure SBM depth

CONFIG CIRCUIT <sn-cc> FUNCTION MORE SLIP_BUFF
DISABLE*
2_BYTES
4_BYTES
8_BYTES
16_BYTES
SK000118
22.3.12
Configuring Multidrop Master and Slave Devices

In a multidrop data bridge, several circuits take turns using the same bandwidth to
communicate with one circuit (for example, terminals take turns communicating
with a host computer). The circuit that all the other circuits communicate with is
connected to a master device (a computer) and is designated the master; the rest of
the circuits are attached to slave devices (terminals) and are designated slaves. The
master device controls the use of the shared bandwidth by polling each slave in turn.
Chapter 23.7 describes multidrop data bridges.
You can configure:
a DCC or line card circuit as a master or slave device

a DDS circuit as a master or slave device
To configure multidrop master and slave devices
CONFIG CIRCUIT <sn-cc> or <sn-cc-p> or <sn-cc-Bbb>
FUNCTION I/F_MODE MULTI-DROP
DISABLE*
MASTER
SLAVE
SK000119
(400)
22.3-15

22.3.13

NNP 95-2035-01-00-B
Configuring Signal Propagation

DCCs and line cards let you configure:

control signal propagation
Configuring RTS propagation
You can configure RTS propagation on DCCs and Line cards that support DDS
Access and DDS Core SRMs. The RTS signal is propagated through the system to
another data device, where it is mapped onto the lead carrying the DCD signal.
RTS signals are propagated by DDS Access SRMs. If the nodes in your network are
configured for DDS Core, you can propagate RTS signals by configuring the outer
nodes of the network as DDS Access. For RTS propagation in DCC and Line card
circuits, you must configure the circuit for DDS_HCM rate adaption.
To propagate RTS
To propagate RTS, perform the following steps.
1.
Enable signalling (SIG_ON).
2.
Set RTS and DCD as END_TO_END.
3.
Set the RTS/CTS delay to greater than or equal to 30 ms.
The procedure for configuring control signals is described in section 22.3.7 and the
procedure for RTS/CTS delay is in section 22.3.6.
To disable propagation
To disable propagation, perform the following steps.
1.
Disable signalling (SIG_OFF).
2.
Set RTS as ASSUMED ON.
3.
Set DCD as FORCED ON.
The procedure for configuring control signals is described in section 22.3.7 and the
procedure for RTS/CTS delay is in section 22.3.6.
Configuring control signal propagation

You can configure control signal propagation for DCCs and line card circuits that are
connected to X.50 Telco SRMs. Control signals are propagated through the system to
another data device. The status bit is used to propagate control signals through the
network. For control signal propagation in DCC and Line card circuits, you must
configure the circuit for X.50_HCM rate adaption.
22.3-16
(400)

NNP 95-2035-01-00-B

Configure signal propagation as:
SIG_ON to enable it
SIG_OFF to disable it (default)
To configure control signal propagation
CONFIG CIRCUIT <sn-cc> or <sn-cc-p> FUNCTION RATE_ADAPT
METHOD
DDS_HCM
SIG_ON/
SIG_OFF*
X50_HCM
SK000120
22.3.14
Configuring Super-rate DCC circuits

To configure an X.21, V.35 or RS-422 DCC super-rate circuit, you must:
configure transparent rate adaption for X.21 and V.35 circuits and enhanced
transparent rate adaption for RS-422 circuits

configure the transport bandwidth
set the interface speed
configure specific clocking parameters
Transport bandwidth
The transport bandwidth must divide evenly into the interface speed. The resulting
number (the interface speed divided by the transport bandwidth) is called the
multiplier. See Figure 22.3-4.
Figure 22.3-4: Calculating the multiplier
interface speed
= multiplier
transport bandwidth
9067
The multiplier represents the number of primary rate DS0s (64 kb/s channels) the
super-rate circuit fills when it is connected. For most interface speeds, several
bandwidth and primary rate channel combinations are possible. For example, for a
448 kb/s device, the possibilities are:
56 kb/s by 8 channels
(400)
22.3-17


NNP 95-2035-01-00-B
Although you must consider the multiplier in determining the allowable interface
speeds, do not enter it. Set the transport bandwidth, then the interface speed; the
system decides whether the interface speed is valid based on these rules.
Valid interface speeds

If the subrate BRG for a circuit does not support the required speed, the super-rate
BRG for the card can be used to clock the interface. The clocks supplied by the
super-rate BRG range from 16 kb/s through 1920 kb/s (in multiples of 8 kb/s). In
particular, the super-rate BRG supports speeds of n m, where:
n = 2, 4, 6, 8, 10, 12, 14, 16, 18, 20, 22, 24, 26, 28 and 30
m = 64, 56, 48, 40, 32, 24, 16 and 8 kb/s
For all DCCs except the RS-422, all circuits on the card share the super-rate BRG.
After one circuit is synchronized to this BRG, all other circuits that require similar
clocking are restricted to the same speed. For the RS-422, the circuits on the card
support multiple odd super-rate speeds.
You can also carry a subrate circuit (with an interface speed of up to 64 kb/s) in more
than one DS0. Do this by configuring a card for a super-rate speed, then use a
combination of transport bandwidth and subrate speed that meets the multiplier
rules for valid interface speeds.
Note
DCCs use a rate adaption gate array (versions 1 and 2) to provide various interface
speeds. Configuring an odd speed (supported by DCCs with gate array revision 2)
such as 192 or 320 kb/s, on a DCC with gate array version 1, raises the error message
Invalid Speed. Installing a DCC with gate array revision 1 in a slot preconfigured
for an odd speed raises the error message Revision/Feature Mismatch. See
Maintenance, Table 32.8-20.
Table 22.3-6 lists the rules for DCC interface speeds; nx represents the multiplier,
which equals the number of DS0s assigned to DCC circuit x.
Table 22.3-7 lists how to configure the speeds for DCC super-rate circuits. The
italicized areas indicate the optimum method of achieving bit rate. Figure 22.3-5
shows the maximum super-rate interface speeds for DCCs.
22.3-18
(400)

NNP 95-2035-01-00-B

Table 22.3-6: Valid Super-rate Interface Speed Rules

DCC
six-circuit X.21, V.35
Rule
For configuring:
nx must equal 1 or an even number (DCC with gate array version 1)

nx may be 1, even or odd (DCC with gate array version 2)
n1 and n2 must be less than or equal to 30
the sum of n1 and n2 must be less than or equal to 31
For connecting:
four-circuit X.21
The sum of n1, n2, n3, n4, n5 and n6 must be less than or equal to 31
n2, n3, n4, n5 and n6 must be a power of 2 (that is, occupy 1, 2, 4, 8 or 16 DS0s) (1)
For configuring:

nx must be less than or equal to 30
For connecting:
three-circuit V.35
the sum of n1, n2, n3 and n4 must be less than or equal to 31

n2, n3 and n4 must be a power of 2 (that is, occupy 1, 2, 4, 8 or 16 DS0s) (1)
For configuring:

For connecting:
four-circuit RS-422
The sum of n1, n2 and n3 must be less than or equal to 31

n2 and n3 must be a power of 2 (that is, occupy 1, 2, 4, 8 or 16 DS0s) (1)
For configuring:

For connecting:
the sum of n1, n2, n3 and n4 must be less than or equal to 31 (for a single-bandwidth slot) or
62 (for a double-bandwidth slot)
n2, n3 and n4 must be a power of 2 (that is, occupy 1, 2, 4, 8 or 16 DS0s) (1)
(400)
22.3-19


NNP 95-2035-01-00-B
Notes
1. This rule applies when the clock mode is set to external and the circuit is configured using the 4602 MainStreet Intelligent
NetworkStation and MainStreetXpress 46020 Network Manager. It does not apply when the clock mode is external and the
circuit is configured using an NMTI session.
Table 22.3-7: Super-rate Circuit Speed Configuration

Transport
Bandwidth
Bits
per
DS0
Number of DS0s Required
10
12
14
16
18
20
22
24
26
28
30
64
128
256
384
512
640
768
896
1024
1152
1280
1408
1536
1664
1792
1920
56
112
224
336
448
560
672
784
896
1008
1120
1232
1334
1456
1568
1680
48
96
192
288
384
480
576
672
768
864
960
1056
1152
1248
1344
1440
40
32
128
192
256
320
384
448
512
576
640
704
768
832
896
960
24
16
96
128
160
192
224
256
288
320
352
384
416
448
480
80
96
112
128
144
160
176
192
208
224
240
Figure 22.3-5: Maximum Super-rate Interface Speeds

Channel
3-circuit
V.35
4-circuit
X.21
1
2
3
4
30 x 64 max
30 x 64 max
30 x 64 max
31 x 64 max
ST bus
30 x 64 max
31 x 64 max = 1984 kb/s

30 x 64 max = 1920 kb/s
16 x 64 max = 1024 kb/s
14 x 64 max = 896 kb/s
8 x 64 max = 512 kb/s
Channel
1
2
4 circuit
RS-422
3
4
31 x 64 max
31 x 64 max
31 x 64 max (single bandwidth)

62 x 64 max (double bandwidth)
31 x 64 max
ST bus
31 x 64 max
Channel
1
2
3
6-circuit
X.21,V.35
or RS-422
4
5
6
30 x 64 max
31 x 64 max
30 x 64 max
8 x 64 max
8 x 64 max
16 x 64 max
14 x 64 max
16 x 64 max
31 x 64 max
ST bus
14 x 64 max
8519
22.3-20
(400)

NNP 95-2035-01-00-B

Clocking
You can configure the transmit clock for DCC super-rate circuits as slave or external,
but always configure DCC super-rate circuits as locked.
If a super-rate circuit is configured as a source of network synchronization and the
circuit is in DCE mode, configure it for external clocking mode; if it is in DTE mode,
select slave clocking mode.
DCC circuits configured as DTE need an external clock to support interface speeds
up to 1920 kb/s. Circuits configured as DCE receive clock information from the
DCC, which supports speeds of 128, 256, 512 and 1024 kb/s, plus one additional
speed for each card from 16 to 1920 kb/s in 8 kb/s increments.
An RS-422 DCC circuit configured as DTE needs an external clock to support
interface speeds up to 1984 kb/s. Circuits in DCE mode receive clock information
from the DCC.
If the clocking for a circuit is set to external and you want to change it to slave, you
must change the interface speed of the circuit first to conform with the slave rules.
As well as the configured speeds, DCC super-rate circuits support a 64 kb/s
interface speed. The procedure for configuring clocking is in section 22.3.8.
To configure super-rate DCCs

CONFIG CIRCUIT <sn-cc> FUNCTION RATE_ADAPT
TRANSP_BW
METHOD
<bw>
TRANSPAREN
I/F_SPEED
<speed>
ENH_TRANSP
SK000121
where
bw is the number of 8 kb/s elements (1 to 8*)
speed is a valid interface speed relative to the bandwidth
(400)
22.3-21


NNP 95-2035-01-00-B
Note
If you enter the interface speed before the transport bandwidth, the system overrides
the interface speed if the transport bandwidth and interface speed combination is
not valid.
To switch back to subrate speeds, enter the interface speed equal to the transport
bandwidth.
To configure and connect super-rate circuits, see chapter 20.15.
22.3.15
Configuring Super-rate Line Card Circuits

As Figure 22.3-6 shows, you can connect external X.21 and V.35 devices running at
128 kb/s through 2602, 2603, 2613, 2702, 2703 or 2715 MainStreet DTUs to DNICs,
2B1Q or 27LC2 Line cards or 2B1Q channel units configured for DTU support. You
configure the line cards or channel units to transport 128 kb/s transparent data, and
the data is carried through the network over two DS0s.
Note
You do all DTU configuration through a node management session with the node
containing the line card or channel unit.
Figure 22.3-6: 2B1Q, 27LC2 and DNIC Line Card Super-rate Connections
2602, 2603
or 2613
MainStreet DTU*
128 kb/s
device
128 kb/s
device
MainStreet node
A
B
DNIC
Line card
A
B
2B1Q
Line card
or channel
unit
2702, 2703
or 2715
MainStreet DTU*
Common
Control
card
PRI
card
Network
128 kb/s data

on two DS0s
*only one DTU port can be involved

in a super-rate connection at a time
5722
Both ports on the DTUs can be configured for super-rate operation, but only one port
can be program-connected at a time.
Table 22.3-8 lists the line cards and the DTUs that support transparent 128 kb/s
super-rate operation.
22.3-22
(400)

NNP 95-2035-01-00-B

Table 22.3-8: Line Cards and DTUs Supporting Super-rate Connections

DTU (1)
Interface
Minimum Firmware ID
2702 MainStreet DTU
X.21
$23
2703 MainStreet DTU
V.35
$23
V.35
$23
2602 MainStreet DTU
X.21
$14
2603 MainStreet DTU
V.35
$14
2613 MainStreet DTU
V.35
$14
2B1Q Line Card
(2)
or Channel Unit
27LC2 Line Card

2715 MainStreet DTU
DNIC Line Card (2)
Notes
1. The DTU must be equipped with a Revision 2 DRAGA.
2. The 2B1Q or DNIC Line card must be equipped with a DPM or DPM2.
The 128 kb/s super-rate circuits on 2B1Q, 27LC2 and DNIC Line cards can be
connected to:
aggregate cards (DS-3, Dual E1, Dual E3, Dual T1-2, E1, E3, T1 and, X.21 and V.35
PRI cards)
data cards (RS-449 DCC, V.35 DCC, X.21 DCC and DNIC cards)
FRE and FRS cards
Configuration summary
Three steps are required to set up and connect a 128 kb/s transparent super-rate
connection between a 2602, 2603, 2613, 2702, 2703 or 2715 MainStreet DTU and an
aggregate or data card.
Setting up and connecting the DTU
1.
Configure the DTU port for transparent operation.
2.
Configure the DTU port for 128 kb/s.
3.
Connect the DTU port to the target circuit. Table 22.3-9 lists the target circuit
requirements.
(400)
22.3-23


NNP 95-2035-01-00-B
Table 22.3-9: Target Circuit Connection Requirements

Circuit Type
Connection Requirements
Aggregate card
circuit
The target circuit and the next contiguous circuit on the aggregate card must be
available.
Aggregate card
master circuit
The master and slave circuit that will carry the 128 kb/s super-rate connection
must be configured (on the aggregate card) before being connected. The
master and slave circuits do not need to be contiguous.
Data card circuit
The target circuit must be configured for 128 kb/s super-rate before being
connected.
FRE or FRS card

circuit
The target circuit must be configured for 128 kb/s before being connected.
To configure the DTU

CONFIG CIRCUIT <sn-cc-p> FUNCTION RATE_ADAPT
METHOD
TRANSPAREN
I/F_SPEED
<speed>
SK000122
where speed is 128 to configure super-rate or 64 to deconfigure super-rate
To connect the DTU to super-rate circuits

CONFIG CONNECT <sn-cc-p> TO_CIRCUIT <sn-cc> or <sn-l-cc> or
<E3id-E1id>
22.3.16
Configuring DTU Port Redundancy

When connected to a 2715 MainStreet DTU, the 27LC2 Line card supports DTU port
redundancy. DTU port redundancy is supported by having the output data ports of
two co-located 2715 MainStreet DTUs connected to CPE equipment using a Y cable.
When connected together with a Y cable, the active A port on one DTU can be
protected by a standby A port on it's mate. The same protection is provided for B
ports. Using one Y cable, you can connect to the two V.24 or V.35 ports. Using two
Y cables, you can connect to both the V.24 and V.35 interfaces. In standalone mode,
a single 2715 MainStreet DTU can be used with normal V.24 and V.35 DTU cables.
Live traffic running on the DTU links is determined based on the activity status of
the ports.
22.3-24
(400)

NNP 95-2035-01-00-B

Caution
Redundant DTU ports must have the same configuration. Otherwise, if an activity
switch occurs, data may be lost.
To configure the 2715 MainStreet DTU for redundant or standalone operation

CONFIG CIRCUIT <sn-cc-p> MORE REDUNDANT
ENABLE/DISABLE*
SK000123
To disable redundancy for the DTU port, the system checks connections on the
circuit. If the circuit is connected, the warning message That circuit is in use.
Disconnect it first. is displayed.
To configure mate settings

CONFIG CIRCUIT <sn-cc> REDUNDANT
MATE/NO MATE
<sn-cc>
SK000124
MATE settings are configurable only if two 2715 MainStreet DTUs are connected to
their corresponding 27LC2 Line cards; otherwise, the warning message The DTU
does not support this feature. is displayed.
Activity switching
Activity switching occurs due to equipment failures and disconnections or from a
manually initiated forced switch.
(400)
22.3-25


NNP 95-2035-01-00-B
Note 1
Once an activity switch occurs, traffic does not revert to the previously active port
unless a forced activity switch is initiated through NMTI or a cable is physically
disconnected.
Note 2
Active ports are configured independently from standby ports. Software checking is
not provided to ensure compatible configuration between redundant ports. In order
for an activity switch to occur properly, you must ensure that configuration is
consistent between mate DTUs. If mate DTUs are not configured through NMTI,
warning messages will be unavailable.
Debounce synchronization timer

Synchronization is monitored and debounced at both the DTU and node. When a
DTU completes debouncing after a loss of synchronization, it resets itself. When a
node completes debouncing after a loss of synchronization, it raises the appropriate
alarm, removes physical connections and clears the type and various IDs of the
attached DTU.
In a redundant configuration, if a DTU resets itself, an activity switch occurs. You
can configure the debounce synchronization timer at the 2715 MainStreet DTU end
to prevent activity switches when short-term synchronization losses occur. You can
configure the debounce synchronization timer in the range 0 to 255000 ms in 1 ms
increments. If you select 0 ms, the DTU immediately resets itself.
You can configure the debounce synchronization timer at the node end of a
DNIC-to-2600 MainStreet series DTU connection to adjust the tolerance of the DNIC
to line noise. You can configure the debounce synchronization timer for either 50 ms,
250 ms, 1000 ms, 2000 ms or in the range 0 to 300000 ms in 1 ms increments.
22.3-26
(400)

NNP 95-2035-01-00-B

To configure the debounce synchronization timer

CONFIG CIRCUIT <sn-cc> SYNC_DEB
DTU_LOSS
NODE_LOSS
<debounce time>
50_MS
250_MS
1000_MS 2000_MS CUSTOM COPY_RANGE

<debounce time> <sn-cc>
SK000125
where
the first debounce_time is in the range of 0 to 255000 ms in 1 ms increments
the second debounce_time is in the range of 0 to 300000 ms in 1 ms increments
SYNC_DEB time can be configure even though the 2715 MainStreet DTU is not physically present. Once
the 2715 MainStreet DTU is present, the port status and Y cable status are displayed as unknown if the
port is configured as standalone.
Forced activity switching

You can force an activity switch on a 2715 MainStreet DTU if it is configured for port
redundancy. If an activity switch cannot be forced (due to cable problems, line
problems, or the mate DTU of the 27LC2 Line card being out-of-service) the
previously active port is reactivated automatically. To initiate a forced activity
switch through NMTI, you must verify the DTU port activity status.
Table 22.3-10 describes the port activity status check failures that could prevent an
activity switch and their associated NMTI warning messages.
Table 22.3-10: Port Activity Check Failures
Description
NMTI Warning Message
The installed card is not a 27LC2 Line card.
The present module does not support this feature.
The DTU line is not synchronized.
The DTU is not in synch.
The 2715 MainStreet DTU port is not

configured as redundant.
The DTU port must be configured as redundant

first.
The DTU is not a 2715 MainStreet DTU.
The DTU does not support this feature.
Note
You can only force standby mode on an active DTU port. Mate DTUs must be
configured and reside on the same node to display the following warning message:
Mate DTU not present. Proceeding will result in data loss.
Figure 22.3-7 shows a typical port activity switching display.
(400)
22.3-27


NNP 95-2035-01-00-B
Figure 22.3-7: Port Activity Switching Display

3600 MainStreet
1117-H1-00
Toronto:A
Alarms:1
11-May-1997
8:35a
Port
Port Status
Y Cable Status
-----------------------------------------------------A1-01-A
Active
Present
A1-01-B
Standalone
Unknown
DTU Line Loss Of

DTU Mate
:
Installed Type :
Status
:
Sync Debounce Time: 2 secs

1-2
2715 DTU
OK
MAINT ON_CIRCUIT 1-1-A REDUNDANT
1-FRC_STNDBY
6-
27-
38-CANCEL
49-QUIT
50-

MAINT ON_CIRCUIT <sn-cc-p> MORE
REDUNDANT/ FRC_STNDBY
SK000126
22.3.17
Configuring a V.35 DCC Circuit for AQA

You can configure a V.35 DCC circuit for AQA if the circuit is also configured for
DTE mode.
To configure a V.35 DCC circuit for AQA

CONFIG CIRCUIT <sn-cc> FUNCTION MORE AQA
DISABLED*
MASTER
SLAVE
SK000127
22.3-28
(400)

NNP 95-2035-01-00-B
22.3.18

Configuring 8 kHz Timing

Each circuit on the 64 kb/s Codirectional card can generate a source of 8 kHz timing
in the data stream. Configure each circuit with:
8K_TIMING to generate the 8 kHz timing signal continuously, whether the
circuit is connected or not

NO_8K to interrupt the 8 kHz timing signal when the circuit is not connected
(default)
If card version 90-0470-04 receives an AIS, which is an all-ones signal, 8 kHz timing
is automatically interrupted until the card stops receiving AIS.
To configure 8 kHz timing

CONFIG CIRCUIT <sn-cc> FUNCTION TRUNK_COND
8K_TIMING/NO_8K*
Note
An 8 kHz clock can be derived from a 64 kb/s Codirectional card circuit for use as a
synchronization source for the system. Chapter 16.2 describes configuring
synchronization sources.
22.3.19
Configuring the AIS

The AIS is an all-ones signal in the data stream. Configure each circuit on the 64 kb/s
Codirectional card with:
AIS to enable the AIS so that it is sent when the circuit is not connected (default)
NO_AIS to disable the AIS so that it is not sent
If card version 90-0470-04 receives an AIS, the AIS enable/disable function is
automatically disabled until the card stops receiving AIS.
To configure the AIS

CONFIG CIRCUIT <sn-cc> FUNCTION TRUNK_COND AIS*/NO_AIS
22.3.20
Configuring Interface Speed

Data card interface speeds can be either subrate (less than or equal to 64 kb/s) or
super-rate (greater than 64 kb/s). For information on subrate speeds, see
chapter 23.9. For information on super-rate speeds, see chapter 20.15.
(400)
22.3-29


NNP 95-2035-01-00-B
The speed configured for a data interface card circuit must match the speed at which
the attached device is transmitting data.
For the DS0-DP and OCU-DP channel units, you can configure the interface speed
as:
2400 for 2.4 kb/s

4800 for 4.8 kb/s
9600 for 9.6 kb/s (default)
19200 for 19.2 kb/s
56000 for 56 kb/s
64000 for 64 kb/s
To configure interface speed

CONFIG CIRCUIT <sn-cc-1> FUNCTION I/F_SPEED <speed>
where speed is 2400, 4800, 9600*, 19200, 56000 or 64000 b/s
Note
1.2 kb/s operation.
22.3.21
Configuring Error Correction

The DS0-DP and OCU-DP channel units support error correction. They perform
majority vote error correction on a five-byte basis on interface speeds of 2.4, 4.8 and
9.6 kb/s and BCH (17, 9) error correction on interface speeds of 19.2, 56 and 64 kb/s.
Configure error correction as:
EC_ON to enable it (default)

EC_OFF to disable it
You cannot change the error correction configuration after the circuit is connected.
To configure error correction

CONFIG CIRCUIT <sn-cc-1> FUNCTION EC_OFF/EC_ON*
22.3-30
(400)

NNP 95-2035-01-00-B
22.3.22

Configuring a Secondary Channel Operation

The OCU-DP channel unit supports secondary channel operation. The secondary
channel operates by robbing unused control bits from the data transmission and can
be used for end-to-end error checking.
Configure secondary channel operation as:
SC_ON to enable it
SC_OFF to disable it (default)
To configure a secondary channel operation
CONFIG CIRCUIT <sn-cc-1> FUNCTION SC_ON/SC_OFF*
22.3.23
Configuring Switched 56 kb/s Operation

The OCU-DP channel unit supports switched 56 kb/s operation. Carrier services
offer this parameter to provide a full-duplex, synchronous, end-to-end connection.
The attached equipment provides the dialling, originating and answer control.
For switched 56 kb/s operation, you must configure:
a 56 kb/s data circuit configured as DCE

a T1 channel with robbed bit signalling enabled
a destination address
Switched 56 kb/s operation is available only if you have configured the OCU-DP
channel unit interface speed as 56 kb/s. See section 22.3.20.
Configure switched 56 kb/s operation as:
SW56_ON to enable it
SW56_OFF to disable it (default)
To configure switched 56 kb/s operation
CONFIG CIRCUIT <sn-cc-1> FUNCTION SW56_ON/SW56_OFF*
(400)
22.3-31

22.3.24

NNP 95-2035-01-00-B
Configuring Sealing Current

The 4WTO channel unit circuit supports a sealing current of 7 mA (minimum) at
maximum loop length. Select SEAL_CUR and then select:
ENABLE to enable it
DISABLE to disable it (default)
To configure sealing current
CONFIG CIRCUIT <sn-cc-1> MORE SEAL_CUR ENABLE/DISABLE*
22.3.25
Configuring a 2B1Q Channel Unit for ISDN Loop Extension

This section provides an overview of ISDN and describes the procedure for
configuring the 2B1Q channel unit for the loop extension application.
ISDN basics
The ISDN recommendations and standards published by the ITU-T standardize the
transport of digital voice and data over a digital network. Figure 22.3-8 shows the
reference model for basic rate access to the ISDN network. ISDN-compatible devices
can be connected directly to the network through a standard interface at an access
point called the S interface. Equipment that is not ISDN-compatible must be
connected to a TA designed specifically for that equipment, which converts its
transmission format to an ISDN-compatible format at the R interface.
At the end of the subscriber loop, the NT provides line termination for the customer
devices. In the ISDN switch, the LT represents the interface termination. The U
interface is the interface between the NT in the customer premises equipment and
the LT in the network equipment. The U interface provides a BRI of two 64 kb/s
B channels and one 16 kb/s D channel in both directions over a single twisted-pair
cable at distances of up to 5.5 km. Echo cancellation techniques permit full duplex
transmission across the same wiring. The two B channels carry user data: either
voice or data. The D channel carries signalling information. The total effective data
rate across the interface is 160 kb/s, including overhead signalling data and
synchronization words.
22.3-32
(400)

NNP 95-2035-01-00-B

Figure 22.3-8: Basic ISDN Reference Model

R
Analog
telephone
TA
Customer
premises
Non-ISDN
computer
G3
FAX
TA
TA
Network
equipment
NT
ISDN
telephone
ISDN
Network
LT
LT
LT
ISDNcompatible
computer
ISDN
U-interface
telephone
ISDN
U-interface
computer
U
6587
ISDN loop extension

The reference model shown in Figure 22.3-8 represents the simplest, ideal method of
accessing an ISDN network. But when cost or distance factors make it impractical, a
non-ISDN digital facility is used to extend the ISDN loop. Figure 22.3-9 shows an
ISDN loop extension. At either end of the loop extension, an LUNT and LULT
provide the termination for the U interface. The LULT and LUNT are very similar to
an LT and NT, respectively, but have slight differences that make them suitable for
loop extensions. In 3600 MainStreet series bandwidth manager systems, the 2B1Q
channel unit acts as a LUNT or LULT.
Figure 22.3-9: ISDN Loop Extension
Central office (remote)
Central office (local)

Interoffice
carrier
LT
LUNT
Non-ISDN
Digital
facility
LULT
LUNT
Subscriber loop
Digital
facility
LULT
NT1
Exchange
termination
ISDN BRI loop extension
6586
(400)
22.3-33


NNP 95-2035-01-00-B
3DS0 format
One loop extension scheme defined by Bellcore in TR-TSY-000397 uses three DS0
channels on a DS1 (or higher) interface to transport the basic rate traffic between the
LULT and LUNT. In the 3DS0 format, one DS0 is used for each B channel and the
third DS0 carries a D+ channel containing signalling. Figure 22.3-10 shows a typical
3DS0 loop extension application. In this example, the U-interface-compatible device
gains access to a remote ISDN network using 3DS0 transport over a T1 link. The B1,
B2 and D+ channels are treated as parts of one 192 kb/s super-rate circuit connected
to the T1 card.
Figure 22.3-10: 3DS0 ISDN Loop Extension Application
3600 MainStreet
node
NT
U
2B1Q
interface CU
T1
3600 MainStreet
node
Digital
facility
U
2B1Q
CU interface LT
LUNT
T1
LULT
ISDN
U-interface
computer
ISDN
network
DS0n
DS0n+1
B1
DS0n+2
B2
D+
192 kb/s data over 3 DS0s

6585
5DS0 format
Another transmission scheme, specified in ITU-T Q.512, carries the data stream for
two U interfaces on five DS0 channels of a digital facility. Four DS0s correspond to
the B channels from both interfaces. Two 32 kb/s D+CV channels, which consist of
D-channel bits and overhead bits, are multiplexed into the fifth DS0. Figure 22.3-11
shows a typical 5DS0 loop extension application. In this example, two
U-interface-compatible devices use 5DS0 transport over a T1 link to access a remote
ISDN network. An SRM multiplexes two D+CV channels into one DS0. The B1 and
B2 channels are connected to the T1 link directly as parts of one 128 kb/s super-rate
circuit.
22.3-34
(400)

NNP 95-2035-01-00-B

Figure 22.3-11: 5DS0 ISDN Loop Extension Application

ISDN
U-interface
telephone

2B1Q
CU
B11 B21
B11 B21 2B1Q

CU
U
interface LULT
LUNT
D1 CV1
SRM
NT
T1
Digital
facility
D1 CV1
T1
ISDN
Network
SRM
D2 CV2
D2 CV2
U
interface 2B1Q
CU
LULT
U
LT
interface
2B1Q
CU
U
LT
interface
B12 B22 LUNT
B12 B22
ISDN
U-interface
computer
DS0n
B11
DS0n+1
DS0n+2
DS0n+3
DS0n+4
B21
B12
B22
D1CV1 D2CV2
320 kb/s over 5 DS0s

6584
2B1Q channel unit circuits

In 2B1Q channel units configured for ISDN loop extension, there are three circuits.
Circuit 1 corresponds to the B1 channel, circuit 2 to the B2 channel and circuit D to
the D+ (in 3DS0 applications) or D+CV (in 5DS0 applications) channel. In
maintenance procedures, the circuits are referred to as 1, 2 and D (for example,
A1-2-1, A1-2-2 and A1-2-D).
In configuration and connection procedures, circuit identification depends on the
application. In 3DS0 applications, the B1, B2 and D channels must be synchronized
to each other, so they are configured as a super-rate group in which circuit 1 is the
master circuit and circuits 2 and D are slaves. The circuit is configured for 192 kb/s
super-rate interface speed and takes three contiguous DS0s on the backplane. This
practice allows the node software to make sure that there are no delay problems in
connections involving this circuit.
In 5DS0 applications, the D+CV channel does not carry any signalling information,
so does not need to be synchronized with the B1 and B2 channels. For this reason,
the D+CV channel can be configured independently as circuit D. Channels B1 and
B2 need to be delay-equalized, so they are configured as a super-rate group with
circuit 1 as the master. Circuit 1 is configured for 128 kb/s super-rate interface speed
and takes two contiguous DS0s on the backplane.
In DTU support mode, the 2B1Q channel unit has circuits A and B, the same as the
line cards have.
(400)
22.3-35


NNP 95-2035-01-00-B
To configure 2B1Q channel unit circuits

You can configure circuit D of the 2B1Q channel unit in 3DS0 transport mode for:
zero byte substitution

performance monitoring
In zero byte substitution, the channel unit substitutes all ones for any all-zero byte
in the data stream and sets the zero byte indicator in the D+ channel. If there is
far-end non-Newbridge equipment that is not capable of zero byte substitution, you
should turn the parameter off (ZBS_OFF).
Similarly, the performance-monitoring option allows you to turn off performance
monitoring to be compatible with non-Newbridge equipment that does not do
performance monitoring.
For a 2B1Q channel unit in 5DS0 transport mode, you can configure the D channel
to use the high or low nibble before you connect the channel to an SRM circuit.
There are no configuration procedures for circuit 1.
To configure 3DS0 circuits

CONFIG CIRCUIT <sn-cc-D> FUNCTION
ZBS_0N*/ZBS_OFF
PM_ON*/PM_OFF
SK000128
To configure 5DS0 circuits

CONFIG CIRCUIT <sn-cc-D> FUNCTION
PM_ON*/PM_OFF
LOW_NIB*/HIGH_NIB
SK000129
Connecting 2B1Q channel unit circuits

In 3DS0 applications, all three 2B1Q channel unit circuits are configured for 192 kb/s
super-rate interface speed and circuit 1, as the master, represents all three (B1, B2,
D+) channels in connections. You can connect this circuit to any circuit that can be
configured for 192 kb/s super-rate speed, including all primary rate cards and DCCs
(if the circuits on the DCC are configured for 64 kb/s transport bandwidth). You can
configure 2B1Q channel units in 3DS0 transport mode as RAPID-protecting or
RAPID-protected circuits.
22.3-36
(400)

NNP 95-2035-01-00-B

In 5DS0 applications, 2B1Q channel unit circuit D (configured for 32 kb/s interface
speed) represents the D+CV channel, which can occupy either the upper or lower
nibble in the DS0. You can multiplex two 32 kb/s D circuits from different 2B1Q
channel units into one 64 kb/s DS0 channel using SRM circuits on a DSP card or
DPM module.
Note
Two D circuits must be configured for different nibbles to be connected to the same
SRM circuit.
B1 and B2 channels in 5DS0 applications are represented by the 128 kb/s super-rate
master, circuit 1. You can connect this circuit independently to any circuit that can
be configured for 128 kb/s super-rate speed. You can configure 2B1Q channel units
in 5DS0 transport mode as RAPID-protecting or RAPID-protected circuits.
Connection example
In this example, a T1 card is configured in slot A1, a Carrier card in slot A2 and a
DSP3 card in slot A3. Two 2B1Q channel units are installed in positions 2 and 3 of
the Carrier card and configured for 5DS0 applications. Circuit A3-2-D is configured
for LOW_NIB and circuit A3-3-D is configured for HIGH_NIB.
Complying with the 5DS0 format

To comply with the 5DS0 format, you must make the following connections.
1.
Connect A2-2-1 to circuit A1-5.
2.
Connect A2-3-1 to circuit A1-7.
3.
Connect A2-2-D to circuit A3-1-M1.
4.
Connect A2-3-D to circuit A3-1-M1.
5.
Connect A3-1-M1 to circuit A1-9.
Figure 22.3-12 shows the screen displaying the resulting connections. In this
example, circuits A1-1 (master circuit) and A1-2 and A1-3 (slave circuits) on the T1
card in slot A1 are connected to circuit A2-1-1 (master) A2-1-2 and A2-1-D (slaves)
on the 2B1Q channel unit in position 1 of the carrier card in slot A2. The 2B1Q
channel unit is configured for 3DS0 application, so the super-rate circuit uses three
DS0s and carries B1, B2 and D+ data.
Channel units in positions 2 and 3 of the same carrier card are configured for 5DS0
application. The two D circuits from these channel units are connected to an SRM
circuit on the DSP card in slot A3, and that SRM is connected to circuit A1-9. The
other two circuits on the channel units (A2-2-1 and A2-3-1) are configured as
super-rate groups and use two DS0s.
The screen displays two pairs of primary rate circuits (A1-5 and A1-6, and A1-7 and
A1-8) involved in the super-rate connections.
(400)
22.3-37


NNP 95-2035-01-00-B
Figure 22.3-12: 2B1Q Channel Unit Connection Display

3600 MainStreet
Circuit
1117-H1-00
Name
Type
A1-01
A1-02
A1-03
A1-04
A1-05
A1-06
A1-07
A1-08
A1-09
A1-10
A1-11
A1-12
T1_NoSIG
T1_NoSIG
T1_NoSIG
T1_SIG
T1_NoSIG
T1_NoSIG
T1_NoSIG
T1_NoSIG
T1_NoSIG
T1_SIG
T1_SIG
T1_SIG
Toronto:A
Alarms:1
Circuit
*A2-01-01
*A2-01-02
*A2-01-0D
--*A2-02-01
*A2-02-02
*A2-03-01
*A2-03-02
*A3-01-M01
-------
Name
11-May-1997
Type
8:35a
Conv
2B1Q_B
2B1Q_B
2B1Q_D
2B1Q_B
2B1Q_B
2B1Q_B
2B1Q_B
SRM
CONFIG CONNECT 1-1
1-SHOW_CCT
6-PROTECTING
2-DISCONNECT
7-
3-TO_CIRCUIT
8-CANCEL
49-QUIT
5-PROT_BY
0-
Note
Some 2B1Q channel unit circuit connections to single E1 or T1 cards may be blocked
because of delay problems. Use a SAM on these cards to eliminate any delay
equalization problems.
22.3.26
Enabling or Disabling eoc for the 27LC2 Line Card

The 27LC2 line cards with a firmware revision of 3 or greater support ANSI
T1.601-1992 compliant eoc functionality at the DSL level. The eoc enables testing of
the ISDN U-interface when intermediate equipment is installed between the card
and a 2700 MainStreet series DTU. Loss of connectivity of the DTU is also reported
to the system when eoc is enabled. For more information about eoc, see Maintenance
chapter 31.8.
You can enable or disable the eoc feature for each circuit on the 27LC2 line card. The
eoc is disabled by default. Disabling the eoc removes all eoc maintenance tests that
are currently in progress on that circuit.
To enable or disable eoc on the 27LC2 line card

CONFIG CIRCUIT <sn-cc> EOC EOC_DIS*/EOC_ENAB
22.3-38
(400)

NNP 95-2035-01-00-B
22.4
22.4 DCC/Line Card Rate Adapted, SRM & Branch Channel

DCC/Line Card Rate Adapted, SRM

& Branch Channel
This chapter explains how to configure DCC and line card circuits for rate adaption,
SRMs and branch channels.
22.4.1
Understanding Rate Adaption, SRMs and Branch

Channels
Table 22.4-1 lists the parameters for DCC and line cards according to the rate
adaption method they support.
Table 22.4-1: Data Interface Circuit Parameters and Rate Adaption
Transparent
Enhanced
Transparent (1)
HCM
DDS_ HCM
X.50_ HCM
Parameter
Character length (async)
Clocking (sync)
Control signals
Control signal propagation (2)
Device gender
Device mode
Duplex method
Interface type(1)
Inversion (1)
Parity (async)
RTS/CTS delay
(3) (4)
(4)
Slip buffer (1)
Stop bits (async)
Super-rate circuits
(400)
V.35 circuit for AQA
22.4-1


NNP 95-2035-01-00-B
Notes
1. Valid only for RS-422 DCC circuits.
2. C bit.
3. If bandwidth is available (for a 56 kb/s circuit over a 64 kb/s clear channel), control signals are transmitted in all unused
bandwidth.
4. Valid only for DCC circuits.
Table 22.4-2 lists the configurable rate adaption, SRM and branch channel
parameters and indicates how they apply to each type of rate adaption. See
chapter 23.6 for information about rate adaption, SRMs and branch channels.
Table 22.4-2: Rate Adaption, SRM and Branch Channel Parameters
Transparent
Enhanced
Transparent (1)
HCM
DDS_HCM (2)
X.50 (2)
Transport bandwidth
Transport position (3)
Parameter
Frame bit position (4)

Data position
Signalling (3)
Interface speed (3)
Data position
Subframe position (3)
CPSS (4)
Continuity checking (4)

Multi-drop (5)
Composite (5)
User-reserved (5)
Antistreaming
Error correction
Notes
1. Valid only for RS-422 DCC circuits.
2. Not valid for DCC SRMs.
3. Not valid for SRMs.
4. Valid only for SRMs.
5. Valid only for branch channels.
22.4-2
(400)

NNP 95-2035-01-00-B
22.4.2

Configuring SRMs and Rate Adaption

Before you configure the rate adaption method or SRM, you must configure:
DCC slots for subrate multiplexing

line card slots for rate adaption
Configuring DCCs for subrate multiplexing
To configure an X.21 or V.35 DCC for subrate multiplexing, select the slot option
SRM.
To configure DCCs for subrate multiplexing

CONFIG SLOT <sn> OPTIONS SRM
Note
RS-232 DCCs are automatically configured for SRMs and their configuration cannot
be changed. RS-422 DCCs do not support on-card SRMs. To subrate multiplex an
RS-422 DCC circuit, you must connect it to a DSP-based SRM. See chapter 23.6.
Configuring Line cards for rate adaption

To configure Line cards for rate adaption, you must:
configure the card for a DPM2 module using the slot option DPM2
select the rate adaption method
(400)
22.4-3


NNP 95-2035-01-00-B
To configure Line cards for rate adaption

DPM2
HCM_TRANS*
DDS
METHOD
X.50
X50_TELCO
DIV_2
DDS_ACCESS
DIV_3
VERSION_1 VERSION_2
SK000130
Note
If there is no DPM2, or if you need multiple rate adaptions, connect the circuits to a
DSP-based SRM. (See chapter 23.6.)
To configure HCM and transparent rate adaption

Caution
Do not use the signalling bit to transmit data when signalling for the 2606 MainStreet
DTU is set to SIG_OFF.
METHOD TRANSP_BW TRANSP_POS I/F_SPEED SIG_ON*/ DATA_POSN

SIG_OFF
<bw>
HCM*
<Bn>
<speed>
<Ff-Bb>
TRANSPAREN ENH_TRANS
SK000131
22.4-4
(400)

NNP 95-2035-01-00-B

where
Bn is B7* to B0
speed depends on the rate adaption method (see section 23.6.7)
f is 0 to 9 and
b is 7 to 0 (F0-B5*)
Note
The ENH_TRANS option is applicable only for RS-422 circuits.
To configure DDS and X.50 rate adaption

ANTISTREAM METHOD
POSITION
I/F_SPEED
<pos>
<speed>
DDS_HCM
DS-0A
DS-0A_EC
SIG_ON/
SIG_OFF*
X50_HCM
DS-0B
MJU
MJU_EC
DIV_2
DIV_3
SK000132
where
pos is the subframe position (see section 23.6.9)
Note
The ANTISTREAM option is applicable only when the rate adaption method is
configured as DDS_HCM.
(400)
22.4-5


NNP 95-2035-01-00-B
To configure HCM and transparent SRMs
CONFIG CIRCUIT <sn-Mmm> or <sn-cc-Mmm> FUNCTION
METHOD TRANSP_BW
<bw>
HCM*
F_POSITION HCM_BW
<Bn>
<hcm_bw>
TRANSPAREN
SK000133
where
Bn is B7* to B0
hcm_bw is the number of columns (1 to 8*)
To configure DDS SRMs

CONFIG CIRCUIT <sn-Mmm> or <sn-cc-Mmm> FUNCTION
ANTISTREAM
METHOD
DS-0A
POSITION
I/F_SPEED
<pos>
<speed>
DS-0A_EC
DS_0B
CONT_CHK/
NO_CONT_CK*
MJU MJU_EC
SK000134
where
pos is the subframe position (see section 23.6.9)
Note
The CONTCHK/NO_CONT options appear only for DDS access SRMs.
22.4-6
(400)
Information subject to change without notice.

Newbridge, the Newbridge logo and MainStreet are registered trademarks of Newbridge Networks Corporation.
Copyright 1997 Newbridge Networks Corporation.
All rights reserved
Distributor Disclaimer
Newbridge products are intended for standard commercial uses. Without the appropriate network design engineering,
they must not be sold, licensed or otherwise distributed for use in any hazardous environments requiring fail-safe
performance, such as in the operation of nuclear facilities, aircraft navigation or communication systems, air traffic control,
direct life-support machines, or weapons systems, in which the failure of products could lead directly to death, personal
injury, or severe physical or environmental damage. The distributor hereby agrees that the use, sale, licence or other
distribution of the products for any such application without the prior written consent of Newbridge, shall be at the
distributor's sole risk. The distributor hereby agrees to defend and hold Newbridge harmless from any claims for loss, cost,
damage, expense or liability that may arise out of or in connection with the use, sale, licence or other distribution of the
products in such applications.
PRINTED ON
RECYCLED PAPER

NNP 95-2035-01-00-B
23. DSP Cards and IMCs

NNP 95-2035-01-00-B
23.1
23.1 Understanding DSP Card and IMC Configuration

Understanding DSP Card and IMC

Configuration
This chapter provides a summary of the applications and configuration procedures
and indicates to whichcards they apply.
23.1.1
Understanding DSP Cards and the IMC

The DSP cards and IMC process DSP-based applications (for example, voice
compression, rate adaption, subrate multiplexing and BONDING) for other
interface cards.
The DSP-based applications are maintained in a library and are downloaded to the
DSP links on the DSP cards and the IMC to process inputs from other interface cards.
The Control card holds the library from which the IMC, DSP, DSP2, DSP3 and DSP4
cards download the applications. The DSP5 and DSP5H cards hold their own library
of applications.
DSP modules provide additional DSP links for the cards on which they are installed.
The Fax/HCV module provides combined G3 fax and HCV voice compression
functionality on the DSP4 card.
Table 23.1-1 lists the DSP-based applications and shows which card variants support
them.
Table 23.1-1: DSP Card and IMC Applications
Application
DSP
Card (1)
DSP2
Card (1)
DSP3
Card
DSP4
Card
DSP5
Card
DSP5H
Card
IMC
Miscellaneous Applications
CPSS channels (2)
Voice conference bridging
PCM multidrop data

bridging
Subrate switching
BONDING
Voice Compression Applications
HCV
G3 Fax relay
LD-CELP
DSP Cards and IMCs
A-CELP
Super tandem operation
(3)
(400)
23.1-1

Application
DSP
Card (1)
DSP2
Card (1)

NNP 95-2035-01-00-B
DSP3
Card
DSP4
Card
DSP5
Card
DSP5H
Card
IMC
V.32 modem relay

Subrate Multiplexing Applications
Transparent rate adaption
HCM rate adaption and

multidrop data bridging
DDS rate adaption (DDS,

DDS Access, DDS Core)
X.50 rate adaption
Notes
1. This card supports echo cancellation without voice compression. For more information, see 23.4.
2. The DSP card supports 8 and 16 kb/s CPss channels. The DSP2, DSP3 and DSP4 cards support 4, 8 and 16 kb/s CPSS
channels.
3. On the DSP5 card, super tandem operation is supported only when A-CELP voice compression is enabled.
For information about DSP card, DSP module and IMC variants, see chapter 8.3 in
Technical Overview.
23.1.2
Configuring DSP Cards and IMCs

This section provides information on:
DSP card configurable parameters

DSP card connection types
IMC configurable parameters
DSP card configurable parameters
Table 23.1-2 lists the DSP card configuration parameters. Each parameter has a list
23.1-2
(400)
DSP Cards and IMCs

NNP 95-2035-01-00-B

Table 23.1-2: DSP Card Configuration Parameter and Options

DSP
DSP2
DSP3
DSP4
DSP5
DSP5H
Parameter
Options
Card Operations (Slot Level)
Card slots
DSP1
DSP2
DSP3
DSP4
DSP5
Card circuits
2 cct*
6 cct
DSP, DSP2 and DSP3

card slot operation
delta signalling* (1)
HCVD* (2)
DDS core
DSP4 card slot

operation (3)
G3 fax relay
subrate switching
G3 fax, stHCV or G3 fax/stHCV
DSP5 card slot

operation
application number
LD-CELP (5)
A-CELP (5)
DSP5H card slot

operation
application number
DSP resources
1x10 (5)
HCV/fax (4)
2x10 (4)
Hub identification
2-digit BCD octal number from

00* to 77
Signalling Type (Circuit Level)
DSP Cards and IMCs
Signalling type
E1
T1*
E1 signalling types
transparent
clear channel
E&M
continuous E&M
LGS remote extension
LGS earth calling
LGS PLAR
LGE remote extension
LGE earth calling
T1 signalling types
transparent*
clear channel
E&M
LGS loop start
LGS ground start
LGS PLAR
LGS PLAR D3
LGE loop start
LGE ground start
(400)
23.1-3

DSP
DSP2
DSP3
DSP4
DSP5
DSP5H

NNP 95-2035-01-00-B
Parameter
Options
Voice Compression (Circuit Level)
transparent*
HCM
Bit rate (6)
8 kb/s
16 kb/s*
Data bandwidth
1 (800 b/s) to 20* (16 000 b/s)
HCMbandwidth
1 (8 kb/s) to 8* (64 kb/s)
Data position for HCM
F0-B6* to F8-B1
Transport position for

HCM
B0 to B7*
Echo cancellation
enabled*
disabled
Echo cancellation return

loss threshold
See section 23.3.7.
Echo clipping
enabled
disabled*
Echo clipping threshold
10 to 50 dBm0 in 1.0 dBm0 D

(40*)
AC15 tone detection (7)
enabled
disabled*
LD-CELP post-filter (8)
enabled*
disabled
6 dB attenuation pad
enabled
disabled*
Companding law
A-law
Mu-law
automatic*
Rx and Tx gain range
12 to +12 dB in 0.1 dB D (0*)
Automatic Gain Control
enabled
disabled
Sync Loss alarm (9)
enabled
disabled*
Sync Lost alarm times
declare time: 0.5 to 60 s (* = 3 s)

clear time: 0.5 to 60 s (* = 5 s)
Super tandem (7)(10)
enabled
disabled*
Forced super tandem
enabled
disabled*
Super tandem
synchronization time (7)
0.1 to 3.1 s in 0.1 s D (* = 1 s) (11)
23.1-4
(400)
0.1 to 5.0 s in 0.1 s D (* = 1 s) (12)
DSP Cards and IMCs

NNP 95-2035-01-00-B
DSP
DSP2
DSP3
DSP4
DSP5

DSP5H
Parameter
Options
PCM Multidrop Data Bridge (Circuit Level)
PCM multidrop circuit
Master circuit
companding law
A-law
Mu-law*
Master circuit
antistreaming timer
1 to 255 s in 1 s D (20*)
Branch circuit
antistreaming
enabled
disabled*
Branch circuit ADI
enabled
disabled*
VCB circuit
VCM
Companding law
A-law
Mu-law*
automatic
Input gain
16 to +9 dB in 0.1 dB D (0*)
Output gain
16 to +9 dB in 0.1 dB D (0*)
Sidetone
enabled
disabled*
16 to 0 dB in 0.1 dB D (0*)
Listen-only mode
enabled
disabled*
Broadcast mode
enabled
disabled*
Broadcaster
enabled
disabled*
VCBs (Circuit Level)
SRMs (Circuit Level)
HCM
transparent
DDS
DDS access
X.50
X.50 Telco
HCM frame bandwidth
1 (8 kb/s) to 8 (64 kb/s)*
HCM frame bit position
B7* to B0
HCM data position
F0 to F9 and B7 to B0 (F0-B5*)
SRM Branch Channels (Circuit Level)
Composite inputs
composite
not composite*
User/system reserved
inputs
system
user*
DSP Cards and IMCs
(400)
23.1-5

DSP
DSP2
DSP3
DSP4
DSP5

NNP 95-2035-01-00-B
DSP5H
Parameter
Options
Multidrop Data Bridges and MJU (Circuit Level)

(branch channel and
circuit devices)
master
slave
disable*
Fax relay
enabled*
disabled
V32 modem relay
enabled*
disabled
Transmission rate
4800 b/s*
9600 b/s
Fax and Modem Relay (Circuit Level)
14400 b/s (* for LD-CELP) (5)
NSF frame handling

mode
all messages transmitted/received

NSF messages blocked*
Data transmit level
3 to 15 dBm0 (13 dBm0) (11)

6 to 30 dBm0 (13 dBm0) (12)
Modem rate
4800 b/s
7200 b/s (* for A-CELP)
9600 b/s
12000 b/s
14400 b/s (* for LD-CELP)
Set identifiers
See section 23.9.2.
Changing sets
previous set
next set
new set
add to set
delete from set
delete set
SRS circuit or DS0 port

transparent
HCM*
DDS
X.50
4 kb/s CPSS
Interface speeds for

DDS DS0-A
rate-adapted subrate
sets
2.4 kb/s
4.8 kb/s
9.6 kb/s*
19.2 kb/s
56 kb/s
SRS (Circuit Level)
23.1-6
(400)
DSP Cards and IMCs

NNP 95-2035-01-00-B
DSP
DSP2
DSP3
DSP4
DSP5

DSP5H
Parameter
Options

DDS DS0-B
rate-adapted subrate
sets
2.4 kb/s
4.8 kb/s
9.6 kb/s*

X.50 rate-adapted
subrate sets
2.4 kb/s
4.8 kb/s
9.6 kb/s*
19.2 kb/s
48 kb/s
HCM transport
bandwidth
1 (8 kb/s) to 8 (64 kb/s)*
HCM F-bit position
B0 to B7*
HCM bandwidth
column position (8*)
Notes
1. This option is the default if you are using pre-Release 6 software.
2. This option is the default for Release 6 and post-Release 6 software versions.
3. If a DSP4 card with a firmware ID of $9 (or less) is inserted into a slot configured to support super tandem operation, a
Revision/Feature Mismatch alarm is raised and the card is taken out of service. See section 23.11.1 for details.
4. This option is supported on DSP5H cards only.
5. This option is supported on DSP5 cards only.
6. The DSP5 card supports an 8 kb/s bit rate when A-CELP voice compression is configured and a 16 kb/s bit rate when
LD-CELP voice compression is configured.
7. This option is supported on DSP5 cards configured for A-CELP voice compression.
8. This option is supported on DSP5 cards configured for LD-CELP voice compression.
9. Synchronization is not monitored when the circuit is transporting a G3 fax call.
10. For super tandem operation, the minimum required firmware on the DSP4 card is $E.
11. This range is valid for the DSP4 card.
12. This range is valid for DSP5 and DSP5H cards.
13. For the DSP card, only the HCM and transparent options are supported.
DSP card connection types

Table 23.1-3 lists the DSP card circuit connections.
Table 23.1-3: DSP Card Connection Types
Connection Type
DSP Cards and IMCs
Section
Voice compression
23.3.9
Echo canceller
23.4.2
Master circuit for PCM multidrop data

bridges
23.4.2
Branch circuit for PCM multidrop data

bridges
23.4.2
(400)
23.1-7


NNP 95-2035-01-00-B
Connection Type
Section
VCB
23.5.3
Cascading bridge
23.5.3
SRM
23.6.12
SRS
23.9.5
Super tandem
23.11.1
IMC configurable parameters

Table 23.1-4 lists the IMC configuration parameters. Each parameter has a list of
Table 23.1-4: IMC Configuration Parameter and Options
Parameter
Options
Slot Level
Card type
IMC
BONDING Timers (Slot Level)

Calling endpoint synchronization
500 ms to 10 s (* = 1 s)
Answering endpoint synchronization
500 ms to 10 s (* = 2 s)
Calling endpoint directory number
500 ms to 10 s (* = 5 s)
Answering endpoint directory number
500 ms to 10 s (* = 5 s)
Channel setup
10 ms to 3 s (* = 150 ms)
Equalization timeout
500 ms to 10 s (* = 7 s)
BONDING (Circuit Level)
23.1-8
Mode
Mode 1
Mode 3*
Bearer rate (1)
56 kb/s
64 kb/s*
User-side interface speed
112 kb/s to 950 kb/s (* = 384 kb/s)
Synchronization alarm (2)

Declare
Clear
0 to 30 s (* = 3 s) (3)
1 to 30 s (* = 3 s)
Bond setup
enabled
disabled*
End Type (4)
calling
answering*
Directory (5)
modify one
modify all
(400)
DSP Cards and IMCs

NNP 95-2035-01-00-B

Notes
1. The bearer rate option selection automatically sets the user side interface speed, which must be a
multiple of the bearer rate. For example, if you select the 56 kb/s option for the bearer rate, the user
side interface speed automatically changes to 336 kb/s.
2. Synchronization monitoring applies to BONDING mode 3 only.
3. If the declare time is set to 0, alarms are disabled.
4. The end type parameter is available only when the bond setup parameter is enabled.
5. The directory parameter is available only when the end type parameter is configured as answering.
To make BONDING connections, see section 23.10.3.

Note
DSP Cards and IMCs
(400)
23.1-9

NNP 95-2035-01-00-B
23.2
23.2 Configuring Card Slots for DSP Cards and the IMC
Configuring Card Slots for DSP

Cards and the IMC
This chapter explains how to configure slots for the cards.
You must configure the card slot for the card before you can configure or connect
circuits. Configuring a slot type means programming a card slot to accept a specific
card type with specific card parameters. When initially configuring a slot, the system
configures that slot with default settings.
23.2.1
Configuring Card Slots for the IMC and DSP Cards

You can configure the following card slot options.
card type
number of DSP card circuits
hub identification
card applications
IMC BONDING timers
Note

simultaneously.
Card type
Configure the type of card as:
DSP Cards and IMCs
DSP1 for a DSP card

DSP2 for a DSP2 card
DSP5 for a DSP5 or DSP5H card
IMC for an IMC
(400)
23.2-1

NNP 95-2035-01-00-B
Number of DSP card circuits

For DSP, DSP2 or DSP3 cards, configure the number of DSP card circuits as:
2_CCT for two circuits

6_CCT for a card with a four-circuit DSP module, resulting in a total of six circuits
Hub identification
For DSP, DSP2 or DSP3 cards, you can set a hub identification with the HUB_ID
softkey.
DSP card applications

For DSP2 cards, you can configure:
HCVD for data applications or SRMs

DDS_CORE for DDS Core rate adaption
HCVD for HCV voice compression, data applications or SRMs

DDS_CORE for DDS Core rate adaption
SRS for subrate switching

G3_FAX for G3 fax transmission
OTHER for G3 fax, super tandem or combined fax and super tandem operation
APP_NUM to select a fixed application stored in the FLASH memory of the card
LDCELP 1x10 to select LD-CELP voice compression using one circuit per DSP
ACELP 1x10 to select A-CELP voice compression using one circuit per DSP
For DSP5H cards, you can configure:
APP_NUM to select a fixed application stored in the FLASH memory of the card
HCV_FAX 2x10 to automatically select HCV with G3 fax capability using
2 HCV circuits per DSP
23.2-2
(400)
DSP Cards and IMCs

NNP 95-2035-01-00-B
IMC BONDING timers

When you configure the card slot for an IMC, all the card circuits are automatically
configured for BONDING. You can configure the following BONDING timers.
CE_SYNC to modify the value of the calling endpoint BONDING timer. This
timer measures the time it takes for synchronization to occur on the master
channel (the default is 1 second).
AE_SYNC to modify the value of the answering endpoint BONDING timer. This
timer measures the time it takes for synchronization to occur on the master
channel (the default is 2 seconds).
CE_DIR_NUM to modify the value of the calling endpoint directory number
BONDING timer. This measures the time it takes to receive directory numbers
(the default is 5 seconds).
AE_DIR_NUM to modify the value of the answering endpoint directory number
BONDING timer. This measures the time it takes to deliver directory numbers
CHAN_SETUP to modify the value of the channel setup BONDING timer. This
calculates the timeout of the setup of all the individual branch cells (the default
is 150 ms).
EQ_TIMEOUT to modify the value of the equalization timeout BONDING timer.
This timer is used at both endpoints to measure the delay equalization process
To configure DSP card slots

To configure DSP, DSP2 and DSP3 card slots:
CONFIG SLOT <sn>
TYPE
AS_PRESENT
OPTIONS
MORE
6_CCT/
2_CCT*
HCVD*/DDS_CORE
<id>
DSP
DSP
DSP2
HUB_ID
DSP3 DSP4
IMC DSP5
SK000135
where id is a two-digit octal code number (00* to 77)
DSP Cards and IMCs
(400)
23.2-3

NNP 95-2035-01-00-B
Note 1
The HCVD and DDS_CORE options apply only to DSP2 and DSP3 cards.
Note 2
Use the AS_PRESENT softkey if there is a DSP card installed in the slot.
To configure DSP4 card slots:
CONFIG SLOT <sn>
TYPE
AS_PRESENT
OPTIONS
MORE
SRS
OTHER
MODULES
DSP
NONE
DSP
DSP2
DSP3 DSP4
G3FAX
IMC DSP5
SK000136
To configure DSP5 and DSP5H card slots:
CONFIG SLOT <sn>
TYPE
AS_PRESENT
DSP
OPTIONS
MORE
APP_NUM
HCV_FAX
LDCELP
ACELP
DSP
<app_num>
2x10
1x10
1x10
DSP2 DSP3 DSP4
IMC DSP5
SK000983
where app_num is an application number stored in the FLASH memory of the DSP card. The default is 0
(zero).
23.2-4
(400)
DSP Cards and IMCs

NNP 95-2035-01-00-B
Note 1
The HCV_FAX softkey is only available for the DSP5H card.
Note 2
The LDCELP and ACELP softkeys are only available for the DSP5 card.
To configure IMC slots

CONFIG SLOT <sn>
TYPE
OPTIONS
BONDING
AS_PRESENT MORE
DSP
CE_SYNC AE_SYNC CE_DIR_NUM AE_DIR_NUM CHAN_SETUP EQ_TIMEOUT
<timer_value>
DSP
DSP2
DSP3 DSP4
IMC DSP5
SK000137
where timer_value is 500 ms to 10 s for CE_SYNC, AE_SYNC, CE_DIR_NUM, AE_DIR_NUM and

EQ_TIMEOUT or 10 ms to 3 s for CHAN_SETUP
DSP Cards and IMCs
(400)
23.2-5

NNP 95-2035-01-00-B
23.3

Voice Compression
This chapter describes LD-CELP, A-CELP and HCV voice compression, and
explains how to configure voice compression parameters on DSP cards.
23.3.1
Understanding Voice Compression

Voice compression increases the efficiency of voice transmission by electronically
modifying a 64 kb/s PCM voice circuit to obtain a voice circuit of 32 kb/s or less;
inband signalling is used to keep the signalling and speech components of the voice
circuit together. A-CELP compresses voice circuits to 8 kb/s. LD-CELP compresses
voice circuits to 16 kb/s. HCV compresses voice circuits to either 8 or 16 kb/s.
23.3.2
Voice Compression Using DSP Cards

On 3600 MainStreet series bandwidth managers, DSP circuits on DSP cards
compress and decompress voice circuits. The DSP3, DSP4 and DSP5H cards support
HCV voice compression. The DSP5 card supports LD-CELP and A-CELP voice
compression.
The DSP3, DSP4 and DSP5H cards use one DSP circuit for each voice circuit to be
compressed. Each DSP circuit on a DSP5H card has a built-in SRM, which can
multiplex two compressed voice circuits onto a single aggregate circuit before
transmission; therefore, the DSP5H card uses one DSP circuit for either one or two
voice circuits to be compressed.
On DSP cards, compressed voice circuits can be rate adapted and multiplexed onto
a single aggregate circuit before transmission. The DSP cards support both
transparent and HCM rate adaption. For more information about rate adaption, see
chapter 23.6.
Voice compression provides a built-in echo cancellation of 8 ms. If this is not enough
echo cancellation for your application, you can disable echo cancellation and connect
a DSP circuit configured for echo cancellation into your compressed voice
connection (see chapter 23.4).
DSP Cards and IMCs
(400)
23.3-1


NNP 95-2035-01-00-B
To enable voice compression on DSP cards, you must configure the following:
23.3.3
DSP card voice compression type

signalling type
rate adaption parameters
companding law
voice compression options or voice parameters
circuit connections for voice compression
Configuring the DSP Card Voice Compression Type

The voice compression type is configured on DSP cards at the slot level. See DSP
card applications in chapter 23.2 for more information.
Note
When a DSP3 card circuit is initially configured, the HCV softkey must be selected
to configure the circuit as HCV before it can be used to configure rate adaption,
companding law or voice compression options.
CONFIG CIRCUIT <sn-cc> FUNCTION HCV HCV
23.3.4
Configuring the Signalling Type for DSP Cards

To configure signalling on a DSP card, select:
E1_SIG for E1 signalling

T1_SIG for T1 signalling
Select the E1 or T1 signalling type. Table 23.3-1 lists the softkeys and corresponding
E1 and T1 signalling types supported on the DSP cards.
Table 23.3-1: E1 and T1 Signalling Types
Softkey
Signalling Type
E1 Signalling Types
23.3-2
SIG
transparent
NoSIG
clear channel
E+M E+M
E&M
E+M E+M_B
continuous E&M
(400)
DSP Cards and IMCs

NNP 95-2035-01-00-B

Softkey
Signalling Type
LGS REM_EXT
LGS remote extension
LGS EC
LGS earth calling
LGS PLAR
LGS PLAR
LGE REM_EXT
LGE remote extension
LGE EC
LGE earth calling
T1 Signalling Types
SIG
transparent
NoSIG
clear channel
E+M E+M
E&M
LGS LS
LGS loop start
LGS GS
LGS ground start
LGS PLAR
LGS PLAR
LGS PLAR_D3
LGS PLAR D3
LGE LS
LGE loop start
LGE GS
LGS ground start
To configure signalling types

CONFIG CIRCUIT <sn-cc> or <sn-dsp-cc> MORE SIG_TYPE
T1_SIG
E1_SIG
SIG
NoSIG
E+M
REM_EXT
E+M
LGS
R2D_E+M
LGE
E+M_B
EC
PLAR
SIG*
LS
REM_EXT
NoSIG
GS
E+M
PLAR
EC
LGE
LGS
PLAR_D3
LS
TERMINATE
GS
SK000821
DSP Cards and IMCs
(400)
23.3-3

23.3.5

NNP 95-2035-01-00-B
Configuring Rate Adaption Parameters for DSP Cards

On the DSP3, DSP4, DSP5 and DSP5H cards, compressed voice circuits can be rate
adapted and multiplexed onto the same aggregate circuit before transmission. These
cards support both transparent and HCM rate adaption.
To rate-adapt compressed voice circuits, you must configure:
the rate adaption method as TRANSPAREN or HCM

the HCM bandwidth
the transport position for HCM bandwidth when you are subrate multiplexing
the HCM data with transparent data

the HCV bit rate for DSP3, DSP4 and DSP5H circuits as 8_kbps or 16_kbps
the A-CELP bit rate for DSP5 circuits as 8_kbps
the LD-CELP bit rate for DSP5 circuits as 16_kbps
the data bandwidth for DSP4, DSP5 and DSP5H circuits
the data position for HCM rate adaption

A transparently rate-adapted compressed voice channel consists of 1- or 2-bit sets
transmitted at a rate of 8000 sets in a second (1 bit per set 8000 sets per
second = 8 kb/s; 2 bits per set 8000 sets per second = 16 kb/s). Figure 23.3-1 shows
how the node manager displays 8 kb/s and 16 kb/s transparently rate-adapted
compressed voice circuits. B7 to B0 represent the eight bit positions in a DS0. The Ds
indicate the bit positions allocated for the transport of voice. An 8 kb/s compressed
voice channel can occupy any bit position. A 16 kb/s compressed voice channel can
occupy any two adjacent bit positions.
Figure 23.3-1: Transparent 8 kb/s and 16 kb/s Compressed Voice Circuits
B7
B6
B5
B4
B2
B1
B0
B2
B1
B0
a.
B7
b.
B3
B6
B5
B4
B3
7183
When you configure a transparently rate-adapted compressed voice circuit, you

must set the transport position, which defines the location of the data bit.
23.3-4
(400)
DSP Cards and IMCs

NNP 95-2035-01-00-B

HCM rate adaption

An HCM rate-adapted compressed voice circuit consists of 10- or 20-bit sets
transmitted at a rate of 800 sets per second (10 bits per set 800 sets per
second = 8 kb/s; 20 bits in a set 800 sets in a second = 16 kb/s). Figure 23.3-2 shows
how the node manager displays a 16 kb/s HCM rate-adapted compressed voice
channel. The Ds represent the bit positions allocated for the transport of voice.
Figure 23.3-2: HCM 16 kb/s Compressed Voice Circuit
B7
B6
B5
B4
B3
B2
B1
B0
F0
F1
F2
F3
F4
F5
F6
F7
F8
F9
7184
When you configure an HCM rate-adapted compressed voice circuit, you must set:
HCM bandwidth, which defines the bandwidth used by HCM

transport position, which defines the location of the frame F bit (you do not need
to change the transport position unless the circuit is being subrate-multiplexed

with transparent data)
data position, which defines the location of the first D bit
To configure the rate adaption parameters for DSP cards

Consider the following when configuring DSP cards for rate adaption.
For the DSP3 card, select the HCV softkey twice the first time you configure an
DSP Cards and IMCs
HCV function.
DATA_BW must be compatible with the HCV or data circuit bandwidth.
You cannot configure a DATA_BW of 9.6_kbps for a circuit configured with
transparent rate adaption.
(400)
23.3-5


NNP 95-2035-01-00-B
For the DSP3 card, enter:
CONFIG CIRCUIT <sn-cc> FUNCTION HCV RATE_ADAPT
METHOD
TRANSP_BW
TRANSP_POS HCV_RATE
<bw>
TRANSPAREN*
DATA_POSN
<Bn>
HCM
<Ff-Bb>
8_Kbps
16_Kbps
SK000138
where
bw is 2 to 8 for 8_kbps circuits and 3 to 8 for 16_kbps circuits
Bn is B0 to B7* for HCM and 8 kb/s transparent and B1 to B7* for 16 kb/s transparent
Ff-Bb is F0-B6* to F8-B1 for 8_kbps circuits and F0-B6* to F7-B3 for 16_kbps circuits
CONFIG CIRCUIT <sn-cc> FUNCTION HCV_DATA
RATE_ADAPT
METHOD
TRANSPAREN*
HCV_CONFIG
HCM_BW
TRANSP_POS
DATA_BW
DATA_POSN
<bw>
<Bn>
<n>
<Ff-Bb>
HCV_RATE
8_Kbps
16_Kbps
HCM
SK000816
where
bw is 2 to 8 for 8_kbps circuits and 3 to 8 for 16_kbps circuits
Bn is B0 to B7* for HCM and 8 kb/s transparent and B1 to B7* for 16 kb/s transparent
n is 1 to 20* (1 to 16 000 b/s in 800 b/s increments)
23.3-6
(400)
DSP Cards and IMCs

NNP 95-2035-01-00-B

For the DSP5H and DSP5 card, enter:
CONFIG CIRCUIT <sn-dsp-cc> FUNCTION
RATE_ADAPT
METHOD
VOICE
HCM_BW
TRANSP_POS
DATA_BW
DATA_POSN
<bw>
<Bn>
<n>
<Ff-Bb>
BIT_RATE
8_kbps
TRANSPAREN*
16_kbps*
HCM
SK000825
where
bw is 2 to 8 for 8_kbps channels and 3 to 8 for 16_kbps channels
Bn is B1 to B7* for 16 kb/s transparent and B0 to B7* for HCM and 8 kb/s transparent
Note
The DSP5 card supports the 8 kb/s compressed voice bit rate with A-CELP voice
compression and the 16 kb/s compressed voice bit rate with LD-CELP voice
compression only.
23.3.6
Configuring the Companding Law for DSP Cards

Configure the companding law for the compressed voice circuit as:
ALaw for A-law

MuLaw for Mu-law
AUTO for automatic
If you select ALaw or MuLaw, the system uses that law when the circuit is connected
and displays it as A-law Fixed or Mu-law Fixed.
DSP Cards and IMCs
(400)
23.3-7


NNP 95-2035-01-00-B
If you select AUTO, the system determines the companding law to use according to
the following rules when the compressed voice circuit is connected to its mate
circuit.
If the mate circuit is on a voice card, the system uses the companding law of the
voice card.
If the mate circuit is on a T1 or DS-3 card, the system uses Mu-law.

If the mate circuit is on an E1 card, X.21 or V.35 PRI card, or
64 kb/s Co-directional card, the system uses A-law.

If the mate circuit is also configured for AUTO, the system uses the default
companding law, which is A-law.
While a circuit configured for AUTO is unconnected, the system displays its default
companding law, which is A-law.
You cannot change the companding law if the circuit is connected.
To configure the companding law for the DSP cards

CONFIG CIRCUIT <sn-cc> FUNCTION HCV COMP_LAW
ALaw
MuLaw
AUTO*
SK000142
CONFIG CIRCUIT <sn-cc> FUNCTION HCV_DATA HCV_CONFIG

COMP_LAW
ALaw
MuLaw
AUTO*
SK000815
For the DSP5H and DSP5 cards, enter:
23.3-8
(400)
DSP Cards and IMCs

NNP 95-2035-01-00-B

CONFIG CIRCUIT <sn-dsp-cc> FUNCTION VOICE COMP_LAW
ALaw
MuLaw
AUTO*
SK000824
23.3.7
Configuring the Voice Compression Parameters

The DSP3, DSP4, DSP5 and DSP5H cards provide voice compression parameters
that need to be configured to run HCV, A-CELP or LD-CELP voice compression. The
configurable parameters are:
echo cancellation
echo cancellation return loss threshold
echo clipping
echo clipping threshold level
AC15 tone detection
LD-CELP post filter
Echo cancellation
Echo cancellation removes echo caused by delays in transmission over long distance
tail circuits. The compressed voice algorithm provides 8 ms of built-in tail circuit
echo cancellation. If this is not enough echo cancellation for your application, you
can connect a DSP configured for echo cancellation or an external echo canceller
device into your voice compression connection (see chapter 23.4).
Note
You must disable built-in echo cancellation if you are connecting the circuit to a DSP
circuit configured for echo cancellation or when using an external echo canceller.
Configure built-in echo cancellation for the voice compression channel as:
CANCEL_ON to enable it (default)

CANCEL_OFF to disable it
DSP Cards and IMCs
(400)
23.3-9


NNP 95-2035-01-00-B
Echo cancellation return loss threshold

Echo cancellation provides control on echo cancellation return loss, which enables
the echo removal on the transmission line when the echo loss is equal or greater than
the configured threshold. The default threshold is 6 dB.
You can configure the echo cancellation return loss threshold as:
RLOSS_3dB to set a threshold level of 3 dB

RLOSS_6dB to set a threshold level of 6 dB (default)
LOSS_LEVEL to configure an echo cancellation return loss threshold (ranging
from 0 dB to 12 dB) for the DSP5H or DSP5 card
Warning
The default echo cancellation return loss threshold is 6 dB. Depending on the loss
plan, or network topology, this value may not be achievable. Do not set an echo
cancellation return loss threshold to less than 6 dB if it is not essential.
Echo clipping
Echo clipping mutes transmission line signals. If echo on a transmission line occurs
outside of the 8 ms echo cancellation window, enabling echo clipping can help
suppress the echo by muting all transmission line signals when the input is below
the user-configurable echo clipping threshold level.
On the DSP5H and DSP5 card, you can configure the echo clipping threshold level
by selecting THRESHOLD and entering a threshold ranging from 10 dBm0 to
50 dBm0.
You can configure echo clipping for the voice compression channel as:
CLIP_ON to enable it
CLIP_OFF to disable it (default)
The 6 dB attenuation pad attenuates the input signal by 6 dB before it is compressed.
The resulting decompressed signal is amplified by 6 dB before it is delivered to the
output line. Attenuation and re-amplification do not affect the gain levels.
The padding operation is activated only when a 6 dB capable device is connected to
another 6 dB capable device, and both devices are enabled.
Configure the 6 dB attenuation pad as:
6dBPAD_ON to enable it
6dBPAD_OFF to disable it (default)
23.3-10
(400)
DSP Cards and IMCs

NNP 95-2035-01-00-B

Note
The 6 dB attenuation pad is only available for HCV voice compression.
AC15 tone detection

The AC15 tone detection parameter is used to allow the transport of AC15 tones. In
some PBXs, AC15 tones are used instead of signalling to indicate events such as an
off-hook condition.
LD-CELP post filter

This feature improves the quality of an LD-CELP compressed voice signal.
Note
The LD-CELP post filter is only available on DSP5 cards configured for LD-CELP
voice compression.
To configure voice compression parameters on the DSP cards

CONFIG CIRCUIT <sn-cc> FUNCTION HCV HCV_OPTION
ECHO_CANC
CLIP_ON/
CLIP_OFF*
CANCEL_ON*/CANCEL_OFF
Note
DSP3 card echo cancellation can also be configured by entering:
CONFIG CIRCUIT <sn-cc> FUNCTION ECHO_CANC
CANCEL_ON*/CANCEL_OFF
DSP Cards and IMCs
(400)
23.3-11


NNP 95-2035-01-00-B

HCV_OPTION
ECHO_CANC
CANCEL_OFF/
CANCEL_ON*
CLIP_ON/
CLIP_OFF*
AC15_ON/
AC15_OFF*
6dBPAD_ON/
6dBPAD_OFF*
RLOSS_3dB/
RLOSS_6dB*
SK000822
For the DSP5H and DSP5 card, enter:
CONFIG CIRCUIT <sn-dsp-cc> FUNCTION VOICE
OPTIONS
ECHO_CANC
ECHO_CLIP
AC15_ON/ 6dBPAD_ON/ LOSS_LEVEL CANCEL_OFF/

AC15_OFF* 6dBPAD_OFF*
CANCEL_ON*
<canc_loss>
CLIP_ON/ THRESHOLD
CLIP_OFF*
<clip_thres>
SK000823
where
canc_loss is 0 to 120 (60*)
clip_thres is 50 to 10 (40*)
Note
The 6dBPAD_ON/6dBPAD_OFF softkeys are not supported on the DSP5 card.
23.3.8
Connecting Circuits for Voice Compression

For voice compression applications, the following connections must be configured.
1. Connect an uncompressed voice circuit to a DSP circuit.
2. Optionally, connect the DSP circuit to a transparent or HCM SRM.
3. Connect the DSP circuit (or the transparent or HCM SRM output) to a primary
rate circuit.
23.3-12
(400)
DSP Cards and IMCs

NNP 95-2035-01-00-B

Caution
Both ends of an compressed voice connection configured for HCM rate adaption
must have the same framing bit position, voice bandwidth and data bandwidth to
be able to pass data calls.
Valid input connections

You can connect any of the following circuits carrying an uncompressed voice circuit
as an input to a DSP circuit configured for voice compression:
E&M, LGS and LGE circuits

primary rate circuits
external echo cancellation circuits
Note
Do not connect circuits carrying a compressed voice circuit or a data circuit as an
input to a DSP circuit configured for voice compression.
Valid output connections

You can connect the compressed output of a DSP card circuit to:
a primary rate circuit

a transparent or HCM SRM on a DSP, DSP2, DSP3 card or a DNIC DPM
DSP4 SRS
a bult-in transparent or HCM SRM on the DSP5H card
Note 1
Do not connect the output of a DSP to a voice circuit.

Note 2
Do not use a compressed voice circuit to protect another circuit.
DSP Cards and IMCs
(400)
23.3-13


NNP 95-2035-01-00-B
To connect the circuits for voice compression

To connect the circuits for voice compression, you must connect the uncompressed
circuit to the DSP and the DSP to the primary rate circuit, as follows.
CONFIG CONNECT <x-sn-cc> TO_CIRCUIT <x-sn-cc> TO <x-sn-cc>
where
the first x-sn-cc is the uncompressed voice circuit
the second x-sn-cc is the DSP circuit
the third x-sn-cc is the primary rate circuit
If you are connecting an SRM between the DSP circuit and the primary rate circuit
(as shown in Figure 23.3-4), you must make the following connections:
Connect the DSP circuit to the SRM as follows:
CONFIG CONNECT <x-sn-cc> TO_CIRCUIT <x-sn-cc> TO <x-sn-Mmm>
or <x-sn-cc-Mmm>
where
the first x-sn-cc is the uncompressed voice circuit
the second x-sn-cc is the DSP circuit
x-sn-Mmm or x-sn-cc-Mmm is the SRM circuit
Connect the SRM output to the primary rate circuit as follows:

CONFIG CONNECT <x-sn-Mmm> or <x-sn-cc-Mmm> TO_CIRCUIT <x-sn-cc>
where
x-sn-Mmm or x-sn-cc-Mmm is the SRM output
x-sn-cc is the primary rate circuit
23.3-14
(400)
DSP Cards and IMCs

NNP 95-2035-01-00-B
23.4
23.4 PCM Multidrop Data Bridges

PCM Multidrop Data Bridges

This chapter introduces PCM multidrop data bridging and explains how to
configure the following parameters:
23.4.1
PCM multidrop data bridging

antistreaming
antistreaming timeout
ADI
companding law
Understanding PCM Multidrop Data Bridges

Analog multidrop data bridging provides voice frequency multidrop data circuits
between a host processor and two or more slave devices. The PCM multidrop data
bridge provides analog bridging functions in a digital environment.
As shown in Figure 23.4-1, the PCM multidrop data bridge acts as the hub for voice
frequency data polling circuits. Each of the bridge (slave) inputs is connected
through analog modem equipment, digitally encoded into PCM samples and then
connected to the multidrop data bridge branch channels directly from a voice card
or a primary rate interface.
Branch channels (slave inputs) are either a terminal-type device connected through
a four-wire modem, or a composite input from a secondary bridge.
Figure 23.4-1: PCM Multidrop Bridges
MJU
Master connected to
cluster controller
Slaves connected to
terminals via modems
2038
As shown in Figure 23.4-2, you can create larger bridges by cascading them: the
master from the secondary bridge is connected to the branch channel of the primary
bridge. The primary bridge acts as the host processor for the secondary bridge.
DSP Cards and IMCs
(400)
23.4-1


NNP 95-2035-01-00-B
Note
Only one composite input can be connected to an SRM. Cascaded SRMs are
considered as a single SRM.
Figure 23.4-2: Cascading PCM Multidrop Data Bridges
Terminal
slave inputs
Composite
or slave
inputs
Secondary
data bridge
Primary
data bridge
To host
processor
Composite
input
2048
PCM multidrop data bridge features

The features of the PCM multidrop data bridge are:
two independent bridges in a DSP circuit

one high-speed data and one low-speed control bridge operating simultaneously
on a single bridge
10 branch channels in a DSP circuit
PCM multidrop data bridge sample application

In the sample application in Figure 23.4-3, the master device polls the slaves by
broadcasting polling information through the PCM multidrop data bridge. The
addressed slave responds to the host with the requested information. The PCM
multidrop data bridge provides the communication path between the active slave
and the master.
23.4-2
(400)
DSP Cards and IMCs

NNP 95-2035-01-00-B

Figure 23.4-3: Master and Slave Bridging Application
Modem
Local 3600 MainStreet node
Master device
Voice
Interface
card
T1
card
x
Modem
Slave device
PCM Multidrop
data bridge
Slave device
Modem
Remote
Voice
Interface
card
Modem
Slave device
T1
card
Modem
Slave device
3094
Antistreaming
Streaming occurs when a slave device does not return to the idle state after it has
finished communicating with the master device; this prevents the other slave
devices from communicating.
Antistreaming allows the system to detect streaming and disable the slave device
branch channel if the streaming does not stop after a specified amount of time. The
system then considers the disabled circuit out-of-service, but re-enables it if the
circuit stops streaming. If the branch channel is a composite output from another
bridge, antistreaming is automatically disabled.
Antistreaming timeout
Antistreaming timeout is the maximum time a device can stream before the system
disables the circuit, in the range 1 to 255 seconds.
DSP Cards and IMCs
(400)
23.4-3


NNP 95-2035-01-00-B
ADI
You can use ADI if the input contains information that has been transmitted over
more than one primary rate link and converted between two output formats (the
ITU-T alternate digit inversion PCM generally used on E1 links and the AT&T
true-sign inverted magnitude PCM generally used on T1 links). Enabling the ADI
function re-inverts the information so that it is intelligible.
Figure 23.4-4 shows an example of an ADI application. In a 3600 MainStreet series
bandwidth manager node, the connection is between the T1 cards, rather than
through the switching shelves.
Figure 23.4-4: ADI Application
Switching shelf
Switching shelf
3645 MainStreet
node
3645 MainStreet
node
T1
T1
Configured
for "data"
Configured
for "voice"
DSP
PCM Multidrop
Data Bridge
configured for
"ADI_ON"
7156
23.4.2
Configuring PCM Multidrop Data Bridges

To configure PCM multidrop data bridging, you configure:
the DSP card for PCM multidrop data bridging

the circuit as a PCM multidrop data bridge
After you have defined the circuit as a multidrop bridge, you can connect the master
and branch circuits and set the parameters for the master circuit and slave branches.
For the master circuit, you can specify:
the number of seconds for the antistreaming timer (STRM_TIMER)

the companding law as A_LAW or MU_LAW (default)
For each branch circuit, you can enable or disable:
antistreaming (STREAM_ON or STREAM_OFF)

ADI (ADI_ON or ADI_OFF)
23.4-4
(400)
DSP Cards and IMCs

NNP 95-2035-01-00-B

To configure the card for PCM multidrop

CONFIG SLOT <sn> OPTIONS HCVD
Note
HCVD is the default for DSP, DSP2 and DSP3 cards.
To configure the circuit for PCM multidrop

CONFIG CIRCUIT <sn-cc> FUNCTION SRM PCM_MDROP
To connect to the master circuit

CONFIG CONNECT <sn-cc-Mmm> TO_CIRCUIT <sn-cc>
To connect to the branch circuit

CONFIG CONNECT <sn-cc> TO_CIRCUIT <sn-cc-Bbb> TO
<sn-cc-Mmm>
To configure master circuits

CONFIG CIRCUIT <sn-cc-Mmm> FUNCTION
A_LAW/MU_LAW*
STRM_TIMER
<number_of_seconds>
SK000144
where number_of_seconds is from 1 to 255 seconds in 1 second increments (20 s*)
To configure branch circuits

CONFIG CIRCUIT <sn-cc-Bbb> FUNCTION
STREAM_ON*/
STREAM_OFF
ADI_ON/
ADI_OFF*
SK000145
DSP Cards and IMCs
(400)
23.4-5

NNP 95-2035-01-00-B
23.5
23.5 Voice Conference Bridges

Voice Conference Bridges

This chapter introduces voice conference bridging and explains how to configure the
following parameters:
23.5.1
VCBs
companding law
input and output gain
sidetone gain
listen-only mode
broadcast mode for the bridge or the input
Understanding Voice Conference Bridges

A VCB provides a simultaneous communication path between two or more voice
circuits. The two main applications for the VCB are.
conference
broadcast
In a conference VCB, each conferee in the bridge participates equally. If more than
one input has the same gain, each one can be heard. Figure 23.5-1 shows a conference
configuration.
Figure 23.5-1: VCB Conference Configuration
VCB
Cascading link
VCB
2382
In a broadcast VCB, you configure only one input as a broadcaster and all the other
inputs as listen-only. Figure 23.5-2 shows a broadcast configuration.
DSP Cards and IMCs
(400)
23.5-1


NNP 95-2035-01-00-B
Figure 23.5-2: VCB Broadcast Configuration

Broadcaster
Listen-only
Set input to
broadcaster
VCB
Cascading link
VCB
Broadcast
mode
Broadcast
mode
Listen-only
Listen-only
2381
The DSP3 card, which can have two or six DSP circuits, supports VCBs. As shown in
Figure 23.5-3, each DSP circuit supports 14 voice channel inputs, shared between
four bridges. You can connect DSPs in a daisy chain, or hierarchically to create larger
VCBs.
Figure 23.5-3: Large VCBs
Daisy chain
VCB
VCB
VCB
Hierarchical
VCB
VCB
VCB
2049
The inputs must be in a PCM format and can be any combination of:
23.5-2
voice circuits: LGS, LGE, E&M

primary rate circuits: T1, E1, Dual T1, Dual E1 and X.21 and V.35 PRI
echo cancellation circuits
64 kb/s codirectional circuits
(400)
DSP Cards and IMCs

NNP 95-2035-01-00-B

Note
An HCV circuit cannot be an input to a VCB, even if the circuit has been
decompressed. For example, if an HCV circuit is decompressed and connected to a
PCM circuit, you cannot connect the PCM circuit to a VCB.
VCB Restrictions
When you configure VCBs, the following restrictions apply.
Use only four-wire telephones on the bridge, unless:

you connect two-wire telephones to a bridge through a device (such as a
PBX) that provides proper termination if the phone goes on-hook, or

you connect two-wire telephones that are always off-hook directly to the
VCB.
There should be no closed loops or parallel paths between bridges. Figure 23.5-4
shows the invalid loop types:
two inputs on the same bridge
parallel links between two bridges
a closed loop between three or more bridges
Figure 23.5-4: Invalid Loop Types
VCB
VCB
VCB
VCB
VCB
VCB
Parallel links
between two bridges
Two inputs on
the same bridge
Closed loop between

three or more bridges
2051
23.5.2
Configuring Voice Conference Bridges

To configure VCBs, you must configure the card and the circuit for VCBs, then
configure conference or broadcast parameters.
To configure the card for VCB

CONFIG SLOT <sn> OPTIONS HCVD
DSP Cards and IMCs
(400)
23.5-3


NNP 95-2035-01-00-B
Note
HCVD is the default for DSP, DSP2 and DSP3 cards.
To configure the circuit for VCB

CONFIG CIRCUIT <sn-cc> FUNCTION SRM MORE VCB
VCB conference parameters

After you have configure the circuit for VCBs, you can configure the following
parameters for the VCB inputs:
companding law
gain
listen-only mode
Companding law
Configure the companding law for the VCB as:
ALaw for A-law

MuLaw for Mu-law
AUTO for automatic (default)
If you configure the input as automatic, the system determines the companding law
when you make the connection.
If you connect to a circuit on a voice card, the VCB input takes the law of the voice
card.
If you connect to a circuit on a T1 primary rate or DS-3 card, the VCB input is
Mu-law.
If you connect to a circuit on an E1, X.21 or V.35 PRI or 64 kb/s Codirectional
card, the VCB input is A-law.
If you connect to a circuit configured for echo cancellation, the VCB input takes
the law of the circuit.
When you connect circuits to a bridge, they can have any combination of the
companding laws.
Gain
Gain is the increase or decrease in signal power or voltage that occurs in transmitting
a signal from one point to another. The three types of gain are:
input
output
sidetone
23.5-4
(400)
DSP Cards and IMCs

NNP 95-2035-01-00-B

Figure 23.5-5 shows the three types of gain.

Figure 23.5-5: Gain Examples
Input
VCB
Sidetone
Output
2377
The input gain defines the magnitude of the increase or decrease of the signal
transmitted into the bridge. The input gain range is 16 to +9 dB in 0.1 dB steps (the
default is 0 dB).
You can change the input gain at any time, except when the circuit is configured as:
listen-only, which overrides the input gain

broadcast, when all the circuits except for the one broadcasting are forced into
listen-only mode
The output gain defines the magnitude of the increase or decrease of the signal
received from the bridge. The output gain range is 16 to +9 dB in 0.1 dB steps (the
default is 0 dB).
You can change the output gain at any time, except when the circuit is configured as
broadcast (the broadcasting circuit cannot listen to any other circuits on the bridge,
so you cannot change the output gain).
Sidetone gain is a small amount of the transmitted signal that is fed back to the
transmitter. Sidetone gain enables you to hear your own voice to determine whether
the sound needs to be louder or softer. The sidetone gain range is 16 to 0 dB in 0.1
dB steps.
Configure sidetone gain as:
ENABLE to enable it
You can change the sidetone gain at any time.
Listen-only mode
In listen-only mode, the conferee listens but does not participate in the conversation.
You cannot change the input gain in listen-only mode; the system displays
Overridden beside the Input Gain entry.
Configure listen-only mode as:
ENABLE to enable it
DSP Cards and IMCs
(400)
23.5-5


NNP 95-2035-01-00-B
To configure VCB inputs

CONFIG CIRCUIT <sn-cc-Ikk> FUNCTION
COMP_LAW
GAIN
LISTEN
ENABLE/DISABLE*
ALaw
MuLaw AUTO*
INPUT
OUTPUT
<gain>
SIDETONE
ENABLE/DISABLE*
<sidetone>
SK000146
where
sn-cc-Ikk is the VCB input
gain is 16 to +9 dB in 0.1 dB increments (0 dB*)
sidetone is 16 to 0 dB in 0.1 dB increments (0 dB*)
Broadcast mode
For broadcast mode, you configure one circuit as the broadcaster and the system
automatically forces all the other circuits in the bridge into listen-only mode. The
broadcaster cannot listen to any of the other circuits on the bridge.
Configure broadcast mode as:
ENABLE to enable it
To configure broadcast mode
CONFIG CIRCUIT <sn-cc-BRn> FUNCTION BROADCAST
ENABLE/DISABLE*
where sn-cc-BRn is the bridge and n is 1 to 4
To configure the broadcaster

After you configure the bridge for broadcast mode, you can configure one of the
inputs as the broadcaster, as follows:
CONFIG CIRCUIT <sn-cc-Ikk> FUNCTION BRD_CASTER
ENABLE/DISABLE*
23.5-6
(400)
DSP Cards and IMCs

NNP 95-2035-01-00-B

where sn-cc-Ikk is the VCB input
23.5.3
Connecting Voice Conference Bridges

You can connect VCBs individually or as cascading bridges.
Figure 23.5-6 shows an example of a VCB. The figure shows a T1 card in slot 1 and a
VCB on a DSP3 card in slot 2 of Peripheral shelf 1.
Figure 23.5-6: VCB Example
BR1
T1
I3
Slot 1
VCB
Slot 2
2375
Figure 23.5-7 shows an example of a cascading VCB. The figure shows two VCBs:
VCB1 I3 and VCB2 I4.
Figure 23.5-7: Cascading VCB Example
BR1
VCB
BR2
I3
I4
VCB
2376
To connect a VCB
To connect a VCB, connect the voice circuit to the VCB input, and the VCB input to
the voice conference bridge, as follows:
CONFIG CONNECT <sn-cc> TO_CIRCUIT <sn-cc-Ikk> TO <sn-cc-BRn>
where
sn-cc is the voice circuit
sn-cc-Ikk is the VCB input
sn-cc-BRn is the bridge
DSP Cards and IMCs
(400)
23.5-7


NNP 95-2035-01-00-B
To connect a cascading bridge

Note
If you try to connect two inputs on the same bridge, the system displays the message
A circular connection would result.
If you configure the input as a broadcaster, you must set the bridge to broadcast
mode before making the connection.
To cascade bridges, you must configure both bridges, then connect the first input to
its associated bridge, connect that bridge to the second input, and then connect the
second input to its associated bridge, as follows:
CONFIG CONNECT <sn-cc-Ikk> TO_CIRCUIT <sn-cc-BRn> TO
<sn-cc-Ikk> TO <sn-cc-BRn>
where
the first sn-cc-Ikk is the first VCB input
the first sn-cc-BRn is the first bridge
the second sn-cc-Ikk is the second VCB input
the second sn-cc-BRn is the second bridge
23.5-8
(400)
DSP Cards and IMCs

NNP 95-2035-01-00-B
23.6
23.6 Rate Adaption and SRMs

Rate Adaption and SRMs

This chapter introduces rate adaption and SRMs, and explains how to configure the
23.6.1
rate adaption and SRMs

transport bandwidth
transport position
signalling
interface speed
HCM frame bandwidth, bandwidth position and data position
subframes
CPSS
continuity checking
branch channels
SRM connections
Understanding Rate Adaption

Rate adaption is the procedure by which two or more subrate (less than 64 kb/s)
circuits are combined on a single 64 kb/s circuit. The circuit on which the subrate
circuits are combined is called an SRM.
Rate adaption is configured independently for each circuit. The rate adaption
configuration of the SRM circuit must be compatible with all the HCV circuits.
The system can do four kinds of rate adaption:
transparent or enhanced transparent

Newbridge proprietary HCM
AT&T Dataphone DDS and DDS-compatible services
X.50 Division 2 and Division 3
About transparent rate adaption

Transparent rate adaption is a method of combining multiple circuits at various
speeds on a single 64 kb/s DS0. Transparent rate adaption does not require any
framing or signalling information, so the entire DS0 is available for the transport of
the circuits (for example, four 8 kb/s HCV circuits and two 16 kb/s circuits can be
carried by a single SRM circuit).
DSP Cards and IMCs
(400)
23.6-1


NNP 95-2035-01-00-B
The following cards support transparent rate adaption:
DCCs
DNIC and 2B1Q Line cards
DSP, DSP2, DSP3, DSP4, DSP5H and DSP5 cards
There are two forms of transparent rate adaption:
transparent
enhanced transparent
Transparent
A 64 kb/s transparent channel is made of eight 8 kb/s elements named B7 through
B0. The node manager represents the amount of bandwidth allocated to a
transparent channel by the number of elements containing a D, where each D
represents 8 kb/s of bandwidth. Elements that do not contain a D represent unused
bandwidth. Figure 23.6-1 represents a 32 kb/s transparent channel.
Figure 23.6-1: Transparent Channel
B7
B6
B5
B4
B3
B2
B1
B0
7193
Enhanced transparent
Enhanced transparent rate adaption allows signalling transmission that is
transparent and synchronous for all interface speeds. This rate adaption scheme is
available only on RS-422 DCC circuits.
As shown in Figure 23.6-2, an enhanced transparent circuit is made of a 56 kb/s
supervisory circuit and, if the circuit is super-rate, one or more slave circuits. The
first three bits (24 kb/s) of the supervisory circuit are reserved for framing (bit 7) and
signalling (bits 6 and 5). The remaining 40 kb/s are free for transparent data.
23.6-2
(400)
DSP Cards and IMCs

NNP 95-2035-01-00-B

Figure 23.6-2: Enhanced Transparent Rate Adaption Supervisory Circuit

Supervisory
circuit
DS0 1
Slave
circuits
DS0 2
DS0 3
DS0 N
7 6 5 4 3 2 1 0
40 kb/s
DTR/DSR
RTS/DCD
Framing
3468
The system fills the supervisory circuit and the number of slave circuits required
based on the transport bandwidth and interface speed. The system determines
whether the free bandwidth in the supervisory channel is used (it is used if a DS0
can be saved).
As shown in Figure 23.6-3, the signalling bits are used to communicate DCD and
DSR from the DTE to the DCE in the transmit direction. In the receive direction, the
signalling bits are used to communicate RTS and DTR from the DCE to the DTE.
Figure 23.6-3: Enhanced Transparent Rate Adaption Transparent Synchronous
Signalling
Single
bidirectional
HCM link
F
RTS
DTR
HCM frame
MainStreet node
MainStreet node
F
DCD
DSR
RS-422
DTE
RS-422
DCE
Transparent data
only
3469
About HCM rate adaption

HCM rate adaption is a Newbridge proprietary rate adaption scheme. With HCM,
users can establish data channels for a wider variety of interface speeds than is
possible with other rate adaption techniques.
For the MPA card, HCM is used to frame its supervisory channel, TS0 (see chapter
20.20).
DSP Cards and IMCs
(400)
23.6-3


NNP 95-2035-01-00-B
The following cards support HCM rate adaption:
DCCs
DSP, DSP2, DSP3, DSP4, DSP5H and DSP5 cards
HCM divides a 64 kb/s channel into 80 elements that are transmitted at a rate of 800
elements in a second. Each element represents one bit or 800 b/s of bandwidth. As
shown in Figure 23.6-4, the node manager displays an HCM frame as a 10-row by
8-column matrix. The rows are named F0 to F9; the columns are named B7 to B0. The
node manager identifies an element by its row and column, for example F3-B2.
Figure 23.6-4: HCM Frame
B7
B6
B5
B4
B3
B2
B1
B0
F0
F1
F2
F3
F4
F5
F6
F7
F8
F9
7194
The node manager represents the amount of bandwidth allocated to an HCM

channel by the number of elements containing a D, where each D represents 800 b/s
of bandwidth. Because the HCM frame pattern is independent of the primary rate
framing pattern, the start of the HCM frame must be flagged by a framing bit (shown
as an F in the illustrations). The F-bit is always in the first row, but you can set its
column by configuring the transport position.
The S represents a bit position reserved for signalling when end-to-end signalling is
needed. (Signalling includes the clock adjustment if clocking is configured as
independent.) The system reserves a signalling bit position only if you turn on
signalling for the circuit.
The F and S bits each occupy one element. Any element that does not contain an F,
S or D represents unused bandwidth.
About DDS rate adaption

DDS rate adaption involves formatting data streams according to the DS0-A format
to provide basic access to DDS. DDS subrate multiplexing combines several subrate
data streams into a single DS0-B channel. The 3600 MainStreet series bandwidth
managers support fully compatible DDS rate adaption and subrate multiplexing and
can connect to DDS at the T1 level.
23.6-4
(400)
DSP Cards and IMCs

NNP 95-2035-01-00-B

The system supports multidrop circuits, loopbacks and the appropriate control
codes. DDS supports both synchronous and asynchronous interface speeds.
The system provides the following DDS applications:
DDS
DDS Access
DDS Core
Two types of cards support DDS and DDS Access SRMs:
DNIC and 2B1Q Line cards equipped with a DPM2

DSP2 and DSP3 cards
DSP2 and DSP3 cards support DDS Core SRMs.
DDS
DDS is a DSP application that provides basic DDS service. An SRM configured as
DDS supports:
DDS rate adaption

subrate multiplexing
multidrop data bridges
DDS Access
DDS Access (formerly DDS Telco) is a DSP application for standards-compliant
DS0-A, DS0-B and MJU functions used at the edges of large networks and
throughout networks with small DDS requirements. As well as the basic DDS
features, an SRM configured with DDS Access, Version 1, supports:

end-to-end continuity checking using the secondary channel (except at
19.2 kb/s)
DDS_HCM-to-DS0-A and DDS_HCM-to-DS0-B conversions
Version 2 of DDS Access, available in Release 6 of 3600 MainStreet series bandwidth

manager systems, also supports:
DSP Cards and IMCs
19.2 kb/s DS0-A, DS0-B and MJU

MJU antistreaming
BCH error correction for 19.2 kb/s DS0-A format connections
continuity checking at 19.2 kb/s
(400)
23.6-5


NNP 95-2035-01-00-B
DDS Core
DDS Core is a DSP application optimized for high-volume DS0-B and MJU functions
intended for bulk DDS processing on the backbone network. As well as the basic
DDS functions, an SRM configured as DDS Core supports RTS signal propagation
(when DDS Access is being used at the end points of the network). DDS Core is a slot
option for DSP cards (see chapter 23.2).
DS0-A and DS0-B framing and interface speed
Figure 23.6-5 shows the DS0-A and DS0-B framing options. Table 23.6-1 lists the
interface speeds supported by the data interface cards that provide DDS rate
adaption.
Figure 23.6-5: DDS DS0-A and DS0-B Frame Structure
Framing bit
User data for
56 and 64 kb/s
operation
MSB
8-bit DS0
LSB
Primary channel
- user data
- inband
maintenance
codes
Frame
1
2
3
4
5
2.4 kb/s
1 2 3 4
5 6 7 8
9 10 11 12
13 14 15 16
17 18 19 20
4.8 kb/s
1
2
3
4
5
6
7
8
9
10
Standard CSU-to-CSU
communication channel
DDS secondary channel, plus:
- end-to-end control lead propagation
- continuity checking
Switched 56 signalling channel
User data for 64 kb/s operation
9.6 kb/s
1
2
3
4
5
5 frames,
20 channels
5 frames,
10 channels
5 frames,
5 channels
DS0-A:
user data repeated
in all 20 cells
Majority vote 12/20
DS0-B:
each cell
(numbers 1 to 20)
represents a separate
2.4 kb/s channel
DS0-A:
DS0-A:
user data repeated user data repeated
in all 10 cells
in all 5 cells
Majority vote 6/10
Majority vote 3/5
DS0-B:
DS0-B:
each cell
each cell
(numbers 1 to10)
(numbers 1 to 5)
represents a
represents a
separate 4.8 kb/s
separate 9.6 kb/s
channel
channel
19.2 kb/s
1
2
3
4
5
5 frames,
1 channel
56 or 64 kb/s
1
1 frame,
1 channel
DS0-A:
DS0-A:
BCH(17,9) OFF
56 kb/s operation:
user data occupies
user data divided
between cells
framing bit plus
2 and 3
Primary Channel
Pad characters
bits (7 bits total)
64 kb/s operation:
elsewhere
(using the OCU-DP
DS0-A_EC
user data divided
Channel Unit) user
between cells
data occupies
1 and 2
framing bit, Primary
Channel bits, and
BCH code in cells
3 and 4
Secondary Channel
bit (8 bits total)
framing in cell 5
DS0-B:
BCH(17, 9) code in
second DS0
each cell
(numbers 1 to 5)
represents a separate
9.6 kb/s channel
19.2 fits onto 2 and 3
and/or 4 and 5
5964
23.6-6
(400)
DSP Cards and IMCs

NNP 95-2035-01-00-B

Table 23.6-1: Data Card Interface Speeds for DDS Rate Adaption
Interface Speed (b/s)
User Interface Type
Sync DDS Mode

1200
2400
4800
9600
19200
1200
2400
4800
9600
19200
RS-232
56000
RS-422, V.35, X.21
Async DDS Mode

1200
2400
4800
9600
19200
RS-232
1200
2400
4800
9600
19200
RS-422, V.35, X.21
DS0-A channels
A 56 kb/s channel consists of 7 data bits (D) in bit positions 1 to 7 and a network
control bit (C) in bit position 8 (see Figure 23.6-6). To meet the ones density
requirement for the T1 link:
the control bit is a logical 1 if data bits 2 through 7 contain customer data (since
there can never be more than seven consecutive 0s)

the control bit is a logical 0 if data bits 2 through 7 contain a network control code
(an all-zero network control code is invalid)
Figure 23.6-6: DS0-A Format for 56 kb/s DDS Channel
1
C
7195
You can configure a 64 kb/s channel when the OCU-DP channel unit is used. You
can configure user data to occupy all eight bit positions including the framing,
primary channel and secondary channel bits.
DS0-A for subrate speeds
In DDS, any interface speed of 48 kb/s or less is a subrate speed. A subrate DS0-A
channel consists of a logical 1 in bit position 1, six data bits (D) in positions 2 to 7 and
a network control bit (C) in bit position 8. (A composite DS0-A subrate channel with
a zero in bit position 1 is jammed high by a DDS device.) To meet the ones density
requirement for the T1 link:
the control bit is a logical 1 if the data bits contain customer data
the control bit is a logical 0 if the data bits contain a network control code
In a 64 kb/s T1 channel, 8-bit bytes are transmitted at a rate of 8000 every second.
DDS subrate speeds are adapted to the 64 kb/s channel by sending new data every:
5th T1 frame for 9.6 kb/s channels (see Figure 23.6-7)

DSP Cards and IMCs
(400)
23.6-7


NNP 95-2035-01-00-B
As each byte contains six data bits:
9.6 kb/s = (6 data bits 8000 in a second)/5

The frames that do not carry new data carry stuff bytes, which are repetitions of the
latest data byte.
Figure 23.6-7: DS0-A Format for 9.6 kb/s DDS Channel
1
Frame 1
Frame 2
STUFF BYTE
Frame 3
STUFF BYTE
Frame 4
STUFF BYTE
Frame 5
STUFF BYTE
Frame 1
Frame 2
STUFF BYTE
5-frame
pattern
D
7196

1
Frame 1
Frame 2
STUFF BYTE
Frame 3
STUFF BYTE
Frame 4
STUFF BYTE
Frame 5
STUFF BYTE
Frame 6
STUFF BYTE
Frame 7
STUFF BYTE
Frame 8
STUFF BYTE
Frame 9
STUFF BYTE
Frame 10
STUFF BYTE
Frame 1
Frame 2
STUFF BYTE
10-frame
pattern
7197
23.6-8
(400)
DSP Cards and IMCs

NNP 95-2035-01-00-B

The system supports one non-standard DDS subrate speed, 1.2 kb/s, by adapting
the 2.4 kb/s DS0-A format (see Figure 23.6-9). The 2.4 kb/s channels transmit 6
unique data bits every 20th frame; 1.2 kb/s channels transmit 3 unique data bits
every 20th frame. Each bit is repeated for a total of 6 bits in the pattern aabbcc, so a
1.2 kb/s DDS channel uses the same bandwidth as a 2.4 kb/s channel.
1
Frame 1
Frame 2
STUFF BYTE
Frame 3
STUFF BYTE
Frame 4
STUFF BYTE
Frame 5
STUFF BYTE
Frame 6
STUFF BYTE
Frame 7
STUFF BYTE
Frame 8
STUFF BYTE
Frame 9
STUFF BYTE
Frame 10
STUFF BYTE
Frame 11
STUFF BYTE
Frame 12
STUFF BYTE
Frame 13
STUFF BYTE
Frame 14
STUFF BYTE
Frame 15
STUFF BYTE
Frame 16
STUFF BYTE
Frame 17
STUFF BYTE
Frame 18
STUFF BYTE
Frame 19
STUFF BYTE
Frame 20
STUFF BYTE
Frame 1
Frame 2
STUFF BYTE
20-frame
pattern
7198
The system transmits 19.2 kb/s by adapting the 9.6 kb/s DS0-A format (see
Figure 23.6-10). Whereas 9.6 kb/s channels transmit new data every fifth frame and
stuff bytes in the intervening four frames, 19.2 kb/s channels transmit new data in
two of the frames.
Figure 23.6-10 shows DDS, DDS Access (Version 1 and Version 2), and DDS Core. In
the DDS format, the data is transmitted every first and second frame, and the other
frames are specific stuff bytes. In the DDS Access format, the data is transmitted
every second and third frame, and the other frames are specific stuff bytes. In the
DDS Access (Version 2), and DDS Core format, the data is transmitted every second
and third frame, the first frame is a ones complement of the third frame, and the
fourth and fifth frames are repeat stuff bytes of the third frame.
DSP Cards and IMCs
(400)
23.6-9


NNP 95-2035-01-00-B

a. DDS Format
1
Frame 1
DA
DA
DA
DA
Frame 2
DA
DA
DA
DA
DA
DA
DA
DA
Frame 3
Frame 4
Frame 5
Frame 1
DA
DA
DA
DA
DA
DA
Frame 2
DA
DA
DA
DA
DA
DA
5-frame
pattern
b. DDS Access Format

1
Frame 1
Frame 2
DA
DA
DA
DA
DA
DA
Frame 3
DA
DA
DA
DA
DA
DA
Frame 4
Frame 5
Frame 1
Frame 2
DA
DA
DA
DA
DA
DA
5-frame
pattern
c. DDS Access Version 2 and DDS Core Format

1
-DA
-DA
-DA
-DA
-DA
-DA
Frame 2
DA
DA
DA
DA
DA
DA
Frame 3
DA
DA
DA
DA
DA
DA
Frame 1
Frame 4
5-frame
pattern
Frame 5
Frame 1
-DA
-DA
-DA
-DA
-DA
-DA
Frame 2
DA
DA
DA
DA
DA
DA
7199
23.6-10
(400)
DSP Cards and IMCs

NNP 95-2035-01-00-B

Note
Because 1.2 kb/s is a non-standard DDS interface speed, it is not necessarily
compatible with other vendor equipment. Data interfaces configured for external
independent clocking do not support 1.2 kb/s operation. Do not connect them to
DDS SRMs at this speed (see also sections 22.3.8 and 22.3.19).
Majority vote error correction is done automatically on subrate DS0-A channels

based on a three out of five scheme. In a group of five frames that should carry
identical bytes, the bytes that occur the most often are selected as correct. For
19.2 kb/s channels, you can select error correction. There is no error correction for
56 kb/s channels.
About X.50 rate adaption

The X.50 rate adaption scheme is used for subrate data multiplexing in E1
environments. It specifies techniques for rate adaption and subrate multiplexing of
0.6, 1.2, 2.4, 4.8, 9.6 and 48 kb/s synchronous data channels. The X.50
implementation complies with:
ITU-T X.50 Division 2 and Division 3 envelope structure

ITU-T X.54 channel allocation
ITU-T X.51 bis transmission format for 48 kb/s channels
X.50 rate adaption also supports 19.2 kb/s channels (point-to-point), A-bit
operation, control lead propagation, bit-aligned framing and multidrop data
bridging.
Three types of circuits support X.50 rate adaption:
DNIC and 2B1Q Line card equipped with a DPM2

DSP2 and DSP3 cards
DCC circuits
Note
Data interfaces configured for external independent clocking do not support 1.2
kb/s operation. Do not connect them to an X.50 SRM at this speed (see also
sections 22.3.8 and 22.3.19).
ITU-T Recommendation X.50 provides a multiplexing scheme for the interface

between synchronous subrate data devices in an E1 environment. Figure 23.6-11
shows the X.50 framing options.
DSP Cards and IMCs
(400)
23.6-11


NNP 95-2035-01-00-B
Figure 23.6-11: X.50 Framing Structure

MSB
X.50 framing
and A bit
(one for each
superframe)
8-bit DS0
LSB
User data
End-to-end control
lead propagation
(X.50 Telco only)
Data channels for each phase
X.50
X.50 Telco
E1 frame 1
2
3
4
5
Phase 1
Phase 2
Phase 3
Phase 4
Phase 5
DIV 2
DIV 3
DIV 3
1 x 9.6 kb/s 1 x 9.6 kb/s 1 x 9.6 kb/s
2 x 4.8 kb/s 2 x 4.8 kb/s 2 x 4.8 kb/s
4 x 2.4 kb/s 4 x 2.4 kb/s 4 x 2.4 kb/s
8 x 1.2 kb/s 4 x 1.2 kb/s 4 x 1.2 kb/s
16 x 0.6 kb/s
2 phases can accomodate 1 x 19.2 kb/s
All 5 phases can accomodate 1 x 48 kb/s
7180
X.50 Division 2 framing pattern

X.50 Division 2 provides multiplexing for subrate data onto a 64 kb/s circuit using
an 80-frame framing pattern that continues for 80 frames and then repeats itself. The
framing pattern is divided into five phases of 16 frames each. One byte is transmitted
from each phase in succession. Table 23.6-2 shows how the phases are carried in
frames.
Table 23.6-2: X.50 Division 2 Phases and Frames
Phase
Frame
1, 6, 11, 16, 21, 26, 31, 36,41, 46, 51, 56, 61, 66, 71, 76
2, 7, 12, 17, 22, 27, 32, 37, 42, 47, 52, 57, 62, 67, 72, 77
3, 8, 13, 18, 23, 28, 33, 38, 43, 48, 53, 58, 63, 68, 73, 78
4, 9, 14, 19, 24, 29, 34, 39, 44, 49, 54, 59, 64, 69, 74, 79
5, 10, 15, 20, 25, 30, 35, 40, 45, 50, 55, 60, 65, 70, 75, 80
In a 64 kb/s E1 channel, frames are transmitted at a rate of 8000 every second, so each
frame represents 600 b/s of bandwidth ([6 data bits 8000 every second]/80). X.50
Division 2 supports interface speeds of 0.6, 2.4, 4.8, 9.6 and 48 kb/s, so each phase
can contain:
23.6-12
one 9.6 kb/s channel

two 4.8 kb/s channels
four 2.4 kb/s channels
sixteen 0.6 kb/s channels
(400)
DSP Cards and IMCs

NNP 95-2035-01-00-B

X.50 Division 3 framing pattern

X.50 Division 3 provides multiplexing for subrate data onto a 64 kb/s circuit using
a 20-frame framing pattern. As shown in Figure 23.6-12, the framing pattern
continues for 20 frames and then repeats itself. The framing pattern is divided into
five phases of four frames each. One byte is transmitted from each phase in
succession. The phases are carried in frames as follows:
phase 1 in frames 1, 6, 11 and 16

Figure 23.6-12: X.50 Division 3 Framing Pattern
1
Phase
Frame 1
Frame 2
Frame 3
Frame 4
Frame 5
Frame 6
Frame 7
Frame 8
Frame 9
Frame 10
Frame 11
Frame 12
Frame 13
Frame 14
Frame 15
Frame 16
Frame 17
Frame 18
Frame 19
Frame 20
7200
The framing pattern (the pattern of bits located in bit position 1 of every byte)
enables the receiver to identify and retrieve the individual subrate channels. The first
framing bit (A) of the 20-frame sequence indicates distant alarms, where 1 means no
alarm and 0 means an alarm.
DSP Cards and IMCs
(400)
23.6-13


NNP 95-2035-01-00-B
In a 64 kb/s E1 channel, frames are transmitted at a rate of 8000 every second, so each
frame represents 2.4 kb/s of bandwidth ([6 data bits 8000 every a second]/20). X.50
Division 3 supports interface speeds of 2.4, 4.8, 9.6 and 48 kb/s, so each phase can
contain:
one 9.6 kb/s channel

two 4.8 kb/s channels
four 2.4 kb/s channels
X.50 applications
Table 23.6-3 describes the X.50 DSP applications the system supports.
Both the X.50 and X.50 Telco applications use all DSP resources located on DPM2s,
or pairs of DSP resources located on DSP2 or DSP3 cards. Propagation delay through
an X.50 or X.50 Telco SRM is 1.5 ms independent of data rate.
Table 23.6-3: X.50 DSP Applications
Application
Divisions Supported
X.50 Telco
Basic X.50
Division 2
Division 3
Division 3
Framing Pattern
80 frame pattern:
5 phases of 16
frames each
20 frame pattern:
5 phases of 4
frames each
20 frame pattern:
5 phases of 4
frames each
Subrate Channels
Supported for each phase
1 x 9.6 kb/s
2 x 4.8 kb/s
4 x 2.4 kb/s
8 x 1.2 kb/s(1) or
16 x 0.6 kb/s(1)
1 x 9.6 kb/s
2 x 4.8 kb/s
4 x 2.4 kb/s(2) or
4 x 1.2 kb/s(2)
1 x 9.6 kb/s
2 x 4.8 kb/s
4 x 2.4 kb/s(2) or
4 x 1.2 kb/s(2)
Subrate Channels
supported for 2 phases
1 x 19.2 kb/s
1 x 19.2 kb/s
1 x 19.2 kb/s
Subrate Channels
supported for 5 phases
1 x 48 kb/s
1 x 48 kb/s
1 x 48 kb/s
12
(4)
(4)
Number of SRM inputs (3)

A-bit Support
Control Lead Propagation

Bit Aligned Framing
Multidrop Data Bridging (5)
Subrate Switching
Notes
1. The 1.2 and 0.6 kb/s channels occupy exactly 1.2 and 0.6 kb/s of bandwidth, respectively.
2. Each 1.2 kb/s channel connected to an X.50 or X.50 Telco Division 3 SRM is rate adapted by the
X.50 application into 2.4 kb/s of bandwidth for transport across the network (each 1.2 kb/s channel
is made of three data bits repeated as aabbcc to occupy six bits of bandwidth).
3. One input for each X.50 SRM can be an X.50 DS0 aggregate.
4. When the X.50 Telco SRM loses synchronization with the incoming signal, it sets the A bit in the
transmit direction.
5. Only MDDBs at channel speeds less than 19.2 kb/s are supported.
23.6-14
(400)
DSP Cards and IMCs

NNP 95-2035-01-00-B

X.50 Telco
X.50 Telco is an enhanced version of basic X.50 that allows added functions, such as
control lead propagation and loopbacks. X.50 Telco supports ITU-T
Recommendation X.50 Divisions 2 and 3 multiplexing.
Both divisions support a bit-aligned framing pattern that consists of a framing bit
(A) in any bit position, followed by 6 data bits (D) and a status bit (S) in the eighth
position. The status bit, in conjunction with the data bits, conveys call control
information. Bit-aligned framing is used to re-align non-byte protocols.
The framing pattern (the pattern of bits located in the same bit position of every byte)
enables the receiver to identify and retrieve the individual subrate channels. The A
framing bit indicates distant alarms, where 1 means no alarm and 0 means an alarm.
You can configure an SRM as an X.50 Telco SRM; this means that the SRM supports:
X.50 rate adaption

subrate multiplexing
multidrop data bridges
control signal propagation
bit-aligned framing
The 3600 MainStreet series bandwidth managers systems also support two
non-standard X.50 interface speeds (1.2 and 19.2 kb/s) that can make the speeds
incompatible with the speeds of non-Newbridge equipment.
You can multiplex subrate channels together in any combination for a total of
48 kb/s. A 48 kb/s channel takes up all five phases, a 19.2 kb/s channel takes up two
phases and eight non-standard 1.2 kb/s channels take up one phase. You can
program the same or multiple speeds in the same 12.8 kb/s frame when you are
connecting between Newbridge systems. For other systems, you may need to
program the same speed in the 12.8 kb/s frame.
Basic X.50
Basic X.50 supports ITU-T Recommendation X.50 Division 3 multiplexing. As shown
in Figure 23.6-11, basic X.50 consists of a framing bit (A) in bit position 1, 6 data bits
(D) in positions 2 to 7 and a status bit (S) in bit position 8. The status bit, in
conjunction with the data bits, conveys call control information. The node manager
does not display the frame shown in Figure 23.6-1; it uses the bit numbering
convention used for a primary rate channel (shown in Figure 23.6-39).
You can configure an SRM and circuit as basic X.50 so that rate adaption, subrate
multiplexing and multidrop data bridge configurations are supported.
The system also supports two non-standard X.50 interface speeds (1.2 and 19.2 kb/s)
that can make the speeds incompatible with the speeds of non-Newbridge
equipment. Subrate channels can be multiplexed together in any combination for a
total of 48 kb/s.
DSP Cards and IMCs
(400)
23.6-15


NNP 95-2035-01-00-B
For 1.2 kb/s circuits, a frame contains three data bits repeated in the pattern aabbcc,
using the same bandwidth as a 2.4 kb/s circuit. Four non-standard 1.2 kb/s channels
take up one phase. A 48 kb/s channel takes up all five phases, and a 19.2 kb/s
channel takes up two phases. As with X.50 Telco, you can program the same or
multiple speeds in the same 12.8 kb/s frame when you are connecting between
Newbridge systems.
23.6.2
Understanding SRMs
An SRM is an entity that processes bit streams from one or more circuits. It enables
several subrate circuits (voice or data) to be transmitted over a single 64 kb/s
channel.
As shown in Figure 23.6-13, an SRM acts as a two-way funnel: it merges the bit
streams received from branch channels and delivers the resulting bit stream to an
aggregate channel. An SRM also accepts the bit stream from an aggregate channel
and distributes it among branch channels.
The term branch channels refers to the channels on the distributed side of an SRM.
The term aggregate channel refers to the channel on the merged side of an SRM. The
number of branch channels in an SRM varies, but there is always only one aggregate
channel.
Figure 23.6-13: Branch Channels and Aggregate Channels
Merging
Branch
channels
Aggregate
SRM
channels
Distributing
3120
Transparent SRMs
For a transparent SRM, all the circuits connected to the branch channels must use
transparent rate adaption. You need to configure only one parameter for transparent
SRMs: the bandwidth of the aggregate channel.
As shown in Figure 23.6-14, the system displays the configuration of a transparent
SRM using a transparent channel. The Ts represent the elements allocated to
transparent channels. There are no blank elements allocated in this example.
23.6-16
(400)
DSP Cards and IMCs

NNP 95-2035-01-00-B

Figure 23.6-14: Transparent SRM Default Configuration
B7
B6
B5
B4
B3
B2
B1
B0
Transport bandwidth = 64 kb/s (8 bit positions)

7201
Figure 23.6-15 illustrates other configurations of transparent SRMs.

Figure 23.6-15: Transparent SRM Configuration Examples
B7
B6
B5
B4
B3
B2
B1
B0

B7
B6
B5
B4
B3
B2
B1
B0
Transport bandwidth = 8 kb/s (1 bit position)

7202
HCM SRMs
For an HCM SRM, the circuits connected to the branch channels can use either HCM
or transparent rate adaption. Before you connect any circuits to the branch or
aggregate channels of an HCM SRM, you must indicate which portion of the
bandwidth of the SRM is to be used for HCM data. The rest of the bandwidth is by
default available for transparent data.
You must configure three parameters:
the bandwidth of the aggregate channel

the amount of bandwidth allocated to HCM circuits
the location of the bandwidth allocated to HCM circuits
The system displays the configuration of an HCM SRM using only the F0 row.
Figure 23.6-16 shows the default configuration of an HCM SRM. Figure 23.6-17
shows alternative ways (a, b and c) of configuring SRM bandwidth.
In the displays, the F represents the framing bit for the HCM frame, the dashes ()
represent the columns allocated to the HCM frame and the Ts represent the columns
allocated to transparent channels. There are no blank columns allocated in
Figure 23.6-16.
DSP Cards and IMCs
(400)
23.6-17


NNP 95-2035-01-00-B
Figure 23.6-16: HCM SRM Default Configuration
B7
B6
B5
B4
B3
B2
B1
B0

Framing position (F) = B7
HCM bandwidth = 64 kb/s (8 bit positions)
7203
Figure 23.6-17: HCM SRM Configuration Examples
B7
B6
B5
B4
B3
B2
B1
B0
B1
B0
B0

Framing position = B7
B7
B6
B5
B4
B3
B2
F = framing bit
= HCM bit position
T = transparent bit
B7
B6
B5
B4
B3
B2
B1

7204
Note
When an SRM on a DCC card carries both HCM and transparent rate adapted
circuits, the state of the RTS (for DCE) or DCD (for DTE) control signal follows that
of the transparent circuit. This will disrupt the HCM circuits unless the transparent
23.6-18
(400)
DSP Cards and IMCs

NNP 95-2035-01-00-B

DDS SRMs
A DDS DS0-B SRM multiplexes several subrate DS0-A or HCM channels onto a
single aggregate channel that you can cross-connect to a DS0 on a primary rate
interface card. DS0-B SRMs increase bandwidth use by eliminating the redundant
stuff bytes in DS0-A channels.
The number of subrate channels you can multiplex together depends on their
interface speed: a maximum of five 9.6 kb/s channels, two 19.2 kb/s channels, ten
4.8 kb/s channels, or twenty 2.4 kb/s channels. Figures 23.6-18 through 23.6-21 show
the DS0-B framing structure for various speeds.
DS0-B channels can have one of three multiplexing schemes:
a 5-frame pattern containing five 9.6 kb/s channels (Figure 23.6-18), or two 19.2
kb/s channels and one 9.6 kb/s (or lower) channel (Figure 23.6-21)
a 10-frame pattern containing ten 4.8 kb/s channels (Figure 23.6-19)
a 20-frame pattern containing twenty 2.4 kb/s channels (Figure 23.6-20)
Each frame contains one byte from each subrate input channel in a fixed order. The
length of the pattern corresponds to the maximum number of subrate channels that
can be multiplexed at the indicated rate.
A subrate framing pattern (the pattern of bits located in bit position 1 of every byte)
is required for the receiver to identify and retrieve the individual subrate channels.
The framing pattern is different for each DS0-B frame length.
Figure 23.6-18: DS0-B Format for 9.6 kb/s and 19.2 kb/s DDS Channels
1
Frame 2
Frame 3
Frame 4
Frame 5
Frame 1
Frame 2
Frame 1
5 - frame
pattern
7205
DSP Cards and IMCs
(400)
23.6-19


NNP 95-2035-01-00-B
Figure 23.6-19: DS0-B Format for 4.8 kb/s DDS Channel

1
Frame 2
Frame 3
Frame 4
Frame 5
Frame 6
Frame 7
Frame 8
Frame 9
Frame 10
Frame 1
Frame 2
Frame 1
10-frame
pattern
7206
You can multiplex DDS subrate channels with lower speeds onto a DS0-B channel
designated for a higher speed, but you cannot multiplex DDS subrate channels with
higher speeds onto a DS0-B channel designated for a lower speed. You should
always select the DS0-B multiplexing scheme to match the highest interface speed
that will be multiplexed onto the DS0-B channel.
For example, if you are multiplexing 9.6, 4.8 and 2.4 kb/s subrate channels,
configure the SRM for DS0-B operation with an interface speed of 9.6 kb/s. When the
4.8 kb/s DDS channel is connected to a branch channel, a new byte appears half as
often. The other frame contains a stuff byte (a repetition of the latest data). Similarly,
each byte of a 2.4 kb/s branch channel appears in four consecutive patterns (1 new
data byte and 3 stuff bytes).
There is an exception to the rule that the DDS channel must be configured for the
same or higher interface speed than that of the branch channel. DDS Core and DDS
Access (Version 2) support the 19.2 kb/s format directly, as shown in Figure 23.6-18.
For DDS and DDS Access (Version 1), you can use a DS0-B 9.6 SRM to multiplex
19.2 kb/s subrate channels, as shown in Figure 23.6-21. The 9.6 kb/s DS0-B SRM
multiplexes the first 19.2 kb/s channel (data byte A) in frames 2 and 3, and the
second (data byte B) in frames 4 and 5.
23.6-20
(400)
DSP Cards and IMCs

NNP 95-2035-01-00-B

Figure 23.6-20: DS0-B Format for 2.4 kb/s DDS Channel

1
Frame 2
Frame 3
Frame 4
Frame 5
Frame 6
Frame 7
Frame 8
Frame 9
Frame 1
Frame 10
Frame 11
Frame 12
Frame 13
Frame 14
Frame 15
Frame 16
Frame 17
Frame 18
Frame 19
Frame 20
Frame 1
Frame 2
20-frame
pattern
7207
Figure 23.6-21: 19.2 kb/s Channels on a DS0-B_9.6 SRM

1
Frame 1
Empty or 9.6 kb/s channel
Frame 2
DA
DA
DA
DA
DA
DA
Frame 3
DA
DA
DA
DA
DA
DA
Frame 4
DB
DB
DB
DB
DB
DB
Frame 5
DB
DB
DB
DB
DB
DB
DA
DA
DA
Frame 1
Frame 2
First 19.2 kb/s

sub-channel
Second
19.2 kb/s
sub-channel
Empty or 9.6 kb/s channel

DA
DA
DA
5-frame
pattern
7185
DSP Cards and IMCs
(400)
23.6-21


NNP 95-2035-01-00-B
After you configure the card for DDS operation, you can configure the SRMs on the
card for DS0-A formatting or one of the three DS0-B multiplexing schemes. For
SRMs configured as DS0-A, the interface speed selects the formatting pattern. If the
SRM has any connections (branches or aggregates), you cannot change the SRM
function.
Cards supporting SRMs

The following cards support transparent and HCM SRMs:
DCCs
DSP, DSP2, DSP3, DSP5H and DSP5 cards
Table 23.6-4 lists the cards that support transparent and HCM SRMs and the total
number of SRMs and branch channels associated with each card.
Note
DSP2 and DSP3 cards support a total maximum of 50 aggregate and branch
channels.
Table 23.6-4: Transparent and HCM SRM Support

Card Type
Total Number
of SRMs
Number of Branch
Channels for Each DSP
DCC (1)
DNIC with DPM1 or DPM2
12
2B1Q with DPM2
12
DSP, DSP2 or DSP3
12
DSP, DSP2 or DSP3 with a DSP module
24
10
(2)
10
DSP5H and DSP5
Notes
1. The RS-422 DCC does not support on-card SRMs.
2. DSP5H and DSP5 card SRMs are only intended for HCV circuits on the same DSP.
Two types of cards support DDS, DDS Access and X.50 SRMs:
DNIC and 2B1Q Line cards equipped with a DPM2

DSP2 and DSP3 cards
DSP2 and DSP3 cards support DDS Core SRMs.
Table 23.6-5 lists the cards that support DDS, DDS Access and DDS Core SRMs and
the total number of SRMs and branch channels associated with each card.
23.6-22
(400)
DSP Cards and IMCs

NNP 95-2035-01-00-B

Table 23.6-5: DDS SRM Support

Card Type
Number of
SRMs in a
Card
Number of Branch
Channels in a Card
DDS SRM
DNIC with DPM2
12
12
2B1Q with DPM2
12
12
DSP2 or DSP3
12
12
DSP2 or DSP3 with a DSP module
36
36
DNIC with DPM2
4 or 6 (1)
4 or 6 (1)
2B1Q with DPM2
4 or 6 (1)
4 or 6 (1)
DSP2 or DSP3
4 or 6 (1)
4 or 6 (1)
12 or 18 (2)
12 or 18 (2)
DSP2 or DSP3
20
12
60
DDS Access SRM
DDS Core SRM
Notes
1. DDS Access (Version 1) supports six SRMs or branch channels; DDS Access (Version 2) supports
four of each.
2. DDS Access (Version 1) supports 18 SRMs or branch channels; DDS Access (Version 2) supports
12 of each.
Table 23.6-6 lists the cards that support X.50 and X.50 Telco SRMs.
Table 23.6-6: X.50 and X.50 Telco SRM Support
Card Type
Number
of SRMs
in a Card
Number of Branch
Channels in a Card
DNIC with DPM2
12
12
2B1Q with DPM2
12
12
DSP2 or DSP3
12
12
DSP2 or DSP3 with DSP module
36
36
DNIC with DPM2
2B1Q with DPM2
DSP2 or DSP3
18
18
X.50 SRM
X.50 Telco SRM
DSP Cards and IMCs
(400)
23.6-23


NNP 95-2035-01-00-B
Direct Connect cards

As shown in Figure 23.6-22, RS-232, X.21 and V.35 DCCs support three transparent
or HCM SRMs each. RS-422 DCCs do not support on-card SRM, but you can connect
an RS-422 DCC circuit to an SRM on another card that supports SRMs.
Figure 23.6-22: Transparent or HCM SRMs on a DCC
DCC
circuit 1
M01 M02 M03
4182
Line cards
A DNIC or 2B1Q Line card has either a DPM or a DPM2 installed. As shown in
Figure 23.6-23, a line card supports eight transparent or HCM SRMs. Each DPM
contains two DSPs and each DSP supports four SRMs.
Figure 23.6-23: Transparent or HCM SRMs on a Line Card
DNIC/2B1Q Line card

circuit 1
M01 M02 M03 M04
circuit 2
M01 M02 M03 M04
4183
Each line card with a DPM2 supports twelve DDS or X.50 SRMs, or four (DDS Access
Version 2) or six DDS Access SRMs, or six X.50 Telco SRMs (see Figures 23.6-24 and
23.6-25).
Figure 23.6-24: DDS or X.50 SRMs on a Line Card
DNIC/2B1Q Line card

circuit 1
M01 M02 M03 M04 M05 M06
circuit 2
M07 M08 M09 M10 M11 M12
4187
23.6-24
(400)
DSP Cards and IMCs

NNP 95-2035-01-00-B

Figure 23.6-25: DDS Access or X.50 Telco SRMs on a Line Card
DNIC/2B1Q Line card

circuit 1
M01 M02 M03 M04 M05 M06
circuit 2
4188
DSP cards
For the DSP, DSP2 and DSP3 cards, the number of transparent or HCM SRMs
available on the card depends on how many DSPs are on the card. Each DSP
supports four transparent SRMs. In Figure 23.6-26, all the DSPs are configured to
support SRMs.
Note
The DSP5H and DSP5 cards provide one non-configurable SRM for each of their 10
DSPs.
Figure 23.6-26: Transparent or HCM SRMs on a DSP Card
DSP card
circuit 1
M01 M02 M03 M04
circuit 2
M01 M02 M03 M04
circuit 3
M01 M02 M03 M04
circuit 4
M01 M02 M03 M04
circuit 5
M01 M02 M03 M04
circuit 6
M01 M02 M03 M04
Circuit is available only if DSP card has 6 DSPs.

3111
DSP Cards and IMCs
(400)
23.6-25


NNP 95-2035-01-00-B
The number of DDS or X.50 SRMs supported on DSP2 and DSP3 card depends on
the DDS or X.50 application selected.
DDS or X.50:
Each odd-numbered DSP circuit supports 12 SRMs, using its even-numbered

mate circuit. In Figure 23.6-27, circuit 3 is configured to support SRMs and circuit
4 is not available.
DDS Access or X.50 Telco:
Each odd-numbered DSP circuit supports four (DDS Access Version 2) or six
SRMs, using its even-numbered mate circuit. In Figure 23.6-27, circuits 1 and 5
are configured to support SRMs and circuits 4 and 6 are not available.
DDS Core:
Each DSP circuit supports two SRMs. (DDS_CORE is a card slot option, so all
SRMs on a DSP card configured for DDS_CORE are DDS Core SRMs.)
Figure 23.6-27: DDS or X.50 SRMs on a DSP Card
DSP card
circuit 1
M01 M02 M03 M04 M05 M06
DDS access
SRMs
circuit 2
circuit 3
M01 M02 M03 M04 M05 M06
circuit 4
M07 M08 M09 M10 M11 M12
DDS SRMs
circuit 5
M01 M02 M03 M04 M05 M06
circuit 6
DDS access
SRMs

7175
23.6.3
Understanding Branch Channels

Branch channels are the channels on the distributed side of an SRM. You can
configure branch channels on:

DSP, DSP2 and DSP3 cards
If you are going to subrate-multiplex the branch channels, you must position the
data for each circuit so that it does not occupy any of the same elements as the data
from any other multiplexed circuit. The data for each circuit must occupy unique
elements.
23.6-26
(400)
DSP Cards and IMCs

NNP 95-2035-01-00-B

If you are configuring the branch channels as part of a multidrop data bridge, you
must position the data for each circuit so that exactly the same elements are
occupied. Chapter 23.7 describes multidrop data bridges.
Composite inputs
You can connect circuits that may contain multiplexed data (such as a primary rate
channel or an SRM aggregate channel) to an SRM. You define the channels as
COMPOSITE and the node manager lists them under the aggregate channel display
as composite inputs.
If you are connecting a primary rate circuit to a transparent or HCM SRM, you can
configure the type of channel it is carrying as transparent or HCM to indicate to the
system in which section of the SRM (transparent or HCM) to carry the composite
input.
The system shows no elements in the display because it has no way of determining
the occupied elements. You must determine the occupied elements from the
originating circuits and make sure that the elements do not conflict with the
elements of local circuits (in the case of subrate multiplexing), or that they match
exactly (in the case of a multidrop data bridge). If you configure composite inputs to
overlap non-multidrop circuits, data is corrupted.
Note
Only one composite input can be connected to an SRM. Cascaded SRMs are
considered as a single SRM.
If you are connecting a primary rate circuit to an SRM, you can indicate that it is
carrying a DDS channel and, if it is DS0-A, specify some of its characteristics.
If the channel is a DS0-B channel, you must determine the occupied positions from
the originating circuits and make sure that their positions do not conflict with the
positions of local circuits or that the positions match exactly for multidrop data
bridges.
User-reserved branch channels

If you are allowing the system to automatically select the branch channels for an
SRM and you want to save some for a specific future use, you must prevent the
system from using them by reserving them for the user (USER).
DSP Cards and IMCs
(400)
23.6-27


NNP 95-2035-01-00-B
Line cards
For transparent or HCM SRMs on a line card, you can connect the following circuits
to branch channels:
DCC circuits (transparent or HCM rate adapted)

DNIC circuits (transparent or HCM rate adapted)
2B1Q circuits (transparent or HCM rate adapted)
SRM aggregate channels (from DCC, DNIC or DSP SRMs configured as
transparent or HCM)
primary rate channels
HCV compressed voice channels
subrate CPSS channels
DCP circuits
Each DSP on a line card DPM or DPM2 has 12 branch channels that you can allocate
to the 4 SRMs supported by that DSP in any combination, including all 12 to the
same SRM. Figure 23.6-28 shows branch channels and aggregate channels for
transparent or HCM SRMs on a line card DPM.
Before you connect circuits to a branch channel, you must specify what portion of
the 64 kb/s channel the data for each circuit will occupy. If you configure
subrate-multiplexing for the circuits, the data must not occupy the same elements. If
you are joining the circuits in a multidrop data bridge, the data must occupy the
same elements.
Figure 23.6-28: Channels on Line Card Transparent and HCM SRMs
DNIC/2B1Q Line card

12 branch
channels
circuit 1
M01 M02 M03 M04 M05 M06
4 aggregate
channels
12 branch
channels
circuit 2
M01 M02 M03 M04 M05 M06
4 aggregate
channels
4184
For DDS or X.50 SRMs on a line card, you can connect the following circuits to
branch channels:
DCC circuits
DNIC circuits
2B1Q circuits
SRM aggregate channels
For X.50 SRMs, you can also connect 64 kb/s codirectional circuits.
23.6-28
(400)
DSP Cards and IMCs

NNP 95-2035-01-00-B

DDS or X.50
As shown in Figure 23.6-29, each DDS or X.50 DPM2 has 12 branch channels that you
can allocate to the 12 SRMs in any combination, including all 12 to the same SRM. If
you connect a circuit with an interface speed of 19.2 kb/s to a DDS DPM2, the
number of branch channels available is reduced to nine.
Figure 23.6-29: Channels on Line Card DDS or X.50 SRMs
DNIC/2B1Q Line card

circuit 1
M01 M02 M03 M04 M05 M06
12 branch
channels
12 aggregate
channels
circuit 2
M07 M08 M09 M10 M11 M12
4189
DDS Access or X.50 Telco

As shown in Figure 23.6-30, each DDS Access or X.50 Telco DPM2 has four (DDS
Access Version 2) or six branch channels that you can allocate to the four or six SRMs
in any combination.
Figure 23.6-30: Channels on Line Card DDS Access or X.50 Telco SRMs
DNIC/2B1Q Line card

4 or 6
branch
channels
circuit 1
M01 M02 M03 M04 M05 M06
circuit 2
4 or 6
aggregate
channels
4190
DSP cards
For transparent or HCM SRMs on a DSP card, you can connect the following circuits
to branch channels:
DSP Cards and IMCs
DCC circuits (transparent or HCM rate adapted)

DNIC circuits (transparent or HCM rate adapted)
2B1Q circuits (transparent or HCM rate adapted)
SRM aggregate channels (from DNIC, DCC or DSP SRMs configured as
transparent or HCM)
compressed voice channels
subrate CPSS channels
DCP circuits
(400)
23.6-29


NNP 95-2035-01-00-B
Transparent and HCM rate adaption

For the DSP, DSP2 and DSP3 cards, the number of branch channels for each circuit
depends on whether a DSP module is installed on the card.
If no DSP module is installed, each DSP circuit configured for transparent or HCM
SRMs has 12 branch channels that you can allocate to the four SRMs supported by
that circuit in any combination. Figure 23.6-31 shows branch channels and aggregate
channels for a circuit on a two-circuit DSP card.
Figure 23.6-31: Channels on Two-circuit DSP Card Transparent and HCM SRMs
DSP card
12 branch
channels
circuit 1
M01 M02 M03 M04 M05 M06
4 aggregate
channels
12 branch
channels
circuit 2
M01 M02 M03 M04 M05 M06
4 aggregate
channels
4186
If a DSP module is installed, each DSP circuit configured for transparent or HCM
SRMs has 10 branch channels that you can allocate to the four SRMs supported by
that circuit in any combination. Figure 23.6-32 shows branch channels and aggregate
channels for a circuit on a six-circuit DSP card.
Note
DSP2 and DSP3 cards support a combined maximum of 50 aggregate and branch
channels.
23.6-30
(400)
DSP Cards and IMCs

NNP 95-2035-01-00-B

Figure 23.6-32: Channels on Six-circuit DSP Card Transparent and HCM SRMs
DSP card
10 branch
channels
circuit 1
M01 M02 M03 M04
4 aggregate
channels
10 branch
channels
circuit 2
M01 M02 M03 M04
4 aggregate
channels
10 branch
channels
circuit 3
M01 M02 M03 M04
4 aggregate
channels
10 branch
channels
circuit 4
M01 M02 M03 M04
4 aggregate
channels
10 branch
channels
circuit 5
M01 M02 M03 M04
4 aggregate
channels
10 branch
channels
circuit 6
M01 M02 M03 M04
4 aggregate
channels
Circuit is available only if DSP Card has 6 DSPs.

4185
The DSP5H and DSP5 card provides one SRM for each of their 10 DSPs. DSP5H
SRMs provide two branch channels for HCV functionality. DSP5 SRMs provide one
branch channels for LD-CELP or A-CELP compressed voice functionality.
Note
The branch channels on the DSP5H and DSP5 cards are not configurable.
Figure 23.6-33 shows branch channels and aggregate channels for DSPs on the
DSP5H card.
DSP Cards and IMCs
(400)
23.6-31


NNP 95-2035-01-00-B
Figure 23.6-33: Channels on DSP5H Card Transparent and HCM SRMs
DSP5H Card
DSP Resource #1
input
input
circuit 1
circuit 2
HCV circuit
branch
input
HCV circuit
branch
input
M1
1 aggregate
channel
M1
1 aggregate
channel
M1
1 aggregate
channel
DSP Resource #2
input
input
circuit 3
circuit 4
HCV circuit
HCV circuit
branch
input
branch
input
DSP Resource #10

input
input
circuit 19
circuit 20
HCV circuit
HCV circuit
branch
input
branch
input
9591
DDS and X.50 rate adaption

The number of SRMs available on a card depends on how many DSPs are on the
card.
As shown in Figure 23.6-34, each pair of DDS or X.50 DSP circuits on a DSP2 or DSP3
card has 12 branch channels that you can allocate to the 12 SRMs in any combination.
If you connect a circuit with an interface speed of 19.2 kb/s to the pair of DDS
circuits, the number of branch channels available is reduced to nine.
23.6-32
(400)
DSP Cards and IMCs

NNP 95-2035-01-00-B

Figure 23.6-34: Channels on Two-circuit DSP Card DDS or X.50 SRMs
DSP card
12 branch
channels
circuit 1
M01 M02 M03 M04 M05 M06
4 aggregate
channels
12 branch
channels
circuit 2
M01 M02 M03 M04 M05 M06
4 aggregate
channels
4186
As shown in Figure 23.6-35, each pair of DDS Access or X.50 Telco DSP circuits on a
DSP2 or DSP3 card has four (DDS Access Version 2) or six branch channels that you
can allocate to the four or six SRMs in any combination.
Figure 23.6-35: Channels on Six-circuit DSP Card DDS Access or X.50 Telco SRMs
DSP card
4 or 6
branch
channels
4 or 6
branch
channels
4 or 6
branch
channels
circuit 1
circuit 2
circuit 3
circuit 4
circuit 5
circuit 6
M01 M02 M03 M04 M05 M06

M01 M02 M03 M04 M05 M06
M01 M02 M03 M04 M05 M06
4 or 6
aggregate
channels
4 or 6
aggregate
channels
4 or 6
aggregate
channels

4192
As shown in Figure 23.6-36, each DDS Core DSP circuit on a DSP2 or DSP3 card has
10 branch channels that you can allocate to the two SRMs in any combination.
DSP Cards and IMCs
(400)
23.6-33


NNP 95-2035-01-00-B
Figure 23.6-36: Channels on Six-circuit DSP Card DDS Core SRMs
DSP card
10 branch
channels
circuit 1
M01 M02
2 aggregate
channels
10 branch
channels
circuit 2
M01 M02
2 aggregate
channels
10 branch
channels
circuit 3
M01 M02
2 aggregate
channels
10 branch
channels
circuit 4
M01 M02
2 aggregate
channels
10 branch
channels
circuit 5
M01 M02
2 aggregate
channels
10 branch
channels
circuit 6
M01 M02
2 aggregate
channels

4193
23.6.4
Understanding Transport Bandwidth

You can configure transport bandwidth for transparent and HCM rate adaption
methods.

The transport bandwidth is the bandwidth allocated to the data device. For
transparent rate adaption, setting the transport bandwidth establishes a channel for
a data device with a interface speed that is a multiple of 8 kb/s up to 64 kb/s. Setting
the transport bandwidth establishes both the width of a 64 kb/s channel that is used
and the interface speed of the device.
Note
Data rates of less than 64 kb/s are subrate; interface speeds of greater than 64 kb/s
are super-rate.
1.2 kb/s operation. Do not connect them to a transparent SRM at this speed (see
sections 22.3.8 and 22.3.19).
23.6-34
(400)
DSP Cards and IMCs

NNP 95-2035-01-00-B

On the node manager screen, each element of a transparent channel represents 1 bit
transmitted at a rate of 8000 b/s, or 8 kb/s of bandwidth (1 bit 8000 b/s in 8 kb/s).
You set the transport bandwidth by entering the number of elements (1 through 8)
available to the device, so that the transport bandwidth equals the number of
elements times 8 kb/s. For example, you can establish an 8 kb/s channel by entering
1, or a 16 kb/s channel by entering 2. The default is eight elements or 64 kb/s.
The node manager displays transport bandwidth by placing a D in each allocated
bandwidth element position (B7 to B0). The node manager also lists the bandwidth
on the right side of the screen under Rate Adaption.
For example, in Figure 23.6-37, (a) shows a transparent channel with a transport
bandwidth of 16 kb/s (two elements) and (b) shows a transparent channel with a
transport bandwidth of 48 kb/s (six elements). In (a), the transport position is at B7;
in (b), it is at B5. Section 23.6.5 describes transport position.
Figure 23.6-37: Transparent Transport Bandwidth
B7
B6
B5
B4
B3
B2
B1
B0
B7
B6
B5
B4
B3
B2
B1
B0
D
7209
HCM rate adaption

As with transparent rate adaption, the HCM transport bandwidth sets the number
of elements available to the data device. It establishes the maximum allowable
interface speed for the data device, but for HCM, setting the transport bandwidth
does not set the interface speed. You must set interface speed separately.
The default setting for transport bandwidth is 64 kb/s. You do not need to reduce
the transport bandwidth unless the HCM channel is going to be subrate-multiplexed
with transparent channels, or transported on a primary rate channel in which some
of the bit positions are not available for data (such as a T1 link that uses RBS).
Figure 23.6-38 shows a transport bandwidth of 48 kb/s (six elements).
DSP Cards and IMCs
(400)
23.6-35


NNP 95-2035-01-00-B
Figure 23.6-38: HCM Transport Bandwidth

B7
B6
B5
B4
B3
B2
B1
B0
F0
F1
F2
F3
F4
F5
F6
F7
F8
F9
7210
Available data bandwidth

The maximum bandwidth available to the data device is 63.2 kb/s (64 kb/s minus
800 b/s for the framing bit). If signalling is on for the circuit, the signalling bit stream
takes up an additional 800 b/s, leaving 62.4 kb/s of bandwidth available for data.
Pointers for setting transport bandwidth

If you are connecting a transparent or HCM data circuit to a channel on a T1 card
that has JB7 or RBS enabled, you must consider the effect on the usable transport
bandwidth. Figure 23.6-39 shows how the element numbering for a data channel
corresponds to the bit numbering of a T1 channel.
Figure 23.6-39: Bit Numbering Conventions
Data Channel
T1 Channel
B7
B6
B5
B4
B3
B2
B1
B0
1 is the most significant bit

7 is the JB7
8 is the least significant or RBS
7211
23.6-36
(400)
DSP Cards and IMCs

NNP 95-2035-01-00-B

The following examples show some of the effects of connecting a data circuit to a T1
channel. In the examples, the bit number refers to the T1 channel and the data
channel element number is in brackets. It is assumed that the transport position is
always B7.
If the transport bandwidth is 64 kb/s (eight elements) and the customer data
23.6.5
protocol ensures an adequate ones density, JB7 does not alter bit 7 (B1).
If the transport bandwidth of the channel is 56 kb/s (seven elements), the system
automatically sets bit 8 (B0) to 1, ensuring an adequate ones density. JB7 does not
alter bit 7 (B1).
The RTS control lead signal is transported over all unused bandwidth in a
transparent circuit and over the signalling bit (S) in an HCM circuit. If RTS goes
low, bit 8 (B0) or S is changed to 0. To ensure ones density, you must configure
RTS to be high or on.
If the customer data protocol does not ensure an adequate ones density and bit 8
(B0) is altered (for example, by RBS or RTS signalling), JB7 may alter bit 7 (B1) and
make B1 unavailable for data. To prevent data errors, you must set the transport
bandwidth to 48 kb/s (six elements) or less.
If you are connecting a data circuit with a transport bandwidth of 64 kb/s (eight
elements) to a T1 channel with RBS enabled, you must turn off RBS or reduce the
transport bandwidth to 56 kb/s or seven elements so that bit 8 (B0) is not used.
Selecting B8ZS ensures an adequate ones density in the data stream and disabling
RBS allows you to use 64 kb/s of bandwidth (see chapter 20.8).
Understanding Transport Position

Configuring the transport position differs, depending on whether the rate adaption
method is transparent or HCM.

When you set the transport bandwidth, the system automatically starts with element
B7 and fills to the right until the required bandwidth is allocated. If you want to
assign more than one subrate transparent channel to the same 64 kb/s channel
(subrate multiplexing), you must arrange the starting elements and the transport
bandwidth so that the data channels from different devices do not occupy the same
element. If you want to configure a number of circuits as a multidrop data bridge,
you must arrange the starting elements and the transport bandwidth to be the same.
The transport position lets you redefine the starting element from the default of B7.
Table 23.6-7 indicates the allowable transport positions as determined by the
transport bandwidth.
DSP Cards and IMCs
(400)
23.6-37


NNP 95-2035-01-00-B
Table 23.6-7: Transport Bandwidth and Transport Position for Transparent Rate
Adaption
Transport Bandwidth
Transport Position
64 kb/s (n = 8)
B7 only
56 kb/s (n = 7)
B7 or B6
48 kb/s (n = 6)
B7, B6, B5
40 kb/s (n = 5)
B7 to B4
32 kb/s (n = 4)
B7 to B3
24 kb/s (n = 3)
B7 to B2
16 kb/s (n = 2)
B7 to B1
8 kb/s (n = 1)
B7 to B0
Set the transport position by entering Bn to define the starting element. The node
manager displays the transport position by the position of the left-most D. The node
manager also lists the bandwidth position on the right side of the screen under
Transport Posn. For example, in Figure 23.6-37, the transport position at (a) shows
B7 and (b) shows it at B5. The default transport position is B7.
The system gives priority to transport position over transport bandwidth, so that if
you change the transport position, you may also be changing the transport
bandwidth. If there are not enough elements to the right of the transport position,
the node manager reduces the transport bandwidth to the available amount, even if
you have configured it for more. To increase the transport bandwidth, you may need
to change the transport position first.
HCM rate adaption

In HCM rate adaption, transport position defines the column in which the F-bit is
located. The F-bit is always in the first row (F0). Set the transport position by
entering the column or element position in the form Bn, where n is the column
number (0 through 7). The default is B7.
You do not need to change the transport position unless the subrate circuit is being
multiplexed with transparent data. Then you must move the F-bit so that the
columns to be occupied by the transparent channel are not included in the HCM
circuit's transport bandwidth. The F-bit must be in the same column as the framing
bit in the SRM being used to configure subrate circuits for multiplexing.
23.6.6
Understanding Signalling
The signalling parameter determines whether the DTU or DCC data in the HCM
frame includes a signalling bit stream (the S in Figure 23.6-38). Turning signalling off
means that no bandwidth is used for signalling.
23.6-38
(400)
DSP Cards and IMCs

NNP 95-2035-01-00-B

S-bit signalling
S-bit signalling propagates all leads through the network. It is available in both
synchronous and asynchronous modes and uses 800 b/s of bandwidth within the
HCM frame. It cannot be provided in a pure transparent frame. S-bit signalling is
configured as:
SIG_ON to enable it (default)

SIG_OFF to disable it
Caution
Do not use the signalling bit to transmit data when signalling for the 2606 MainStreet
DTU is set to SIG_OFF.
H-bit Signalling
H-bit signalling propagates only DCD and RTS leads through the network. It
provides end-to-end signalling between a master and slave device in a multidrop
data bridge application (see chapter 23.7). H-bit signalling is available in both
synchronous and asynchronous modes and uses 800 b/s of bandwidth within the
HCM frame. It cannot be provided in a pure transparent frame.
Viewing H-bit signalling configurations
The 3600 and 3645 MainStreet units do not currently show support of H-bit
signalling. However, when you enable both S-bit signalling and multidrop data
bridging with a 3600 and 3645 MainStreet unit, in effect you are enabling H-bit
signalling.
For example, Figure 23.6-40 shows the setting, the NMTI display and the actual
HCM frame data bit positions for a 3600 and 3645 MainStreet unit with the 2612,
2613 and 2715 MainStreet DTUs. In case 4 of the figure, both S-bit and multidrop
data bridging are enabled. The NMTI display (middle column) for case 4 does not
indicate H-bit (H) in B3, even though the actual HCM frame does include the H-bit
in position B3 (far right column).
Figure 23.6-40: H-bit Signalling Results for 2612, 2613 and 2715 MainStreet DTUs
Setting
Case
H-Bit
S-Bit
NMTI Display for HCM Frame

Data Bit Positions
Actual HCM Frame

Data Bit Positions
MDDB B7 B6 B5 B4 B3 B2 B1 B0 B7 B6 B5 B4 B3 B2 B1 B0
D D D
D D D
S D D D
S D D D
D D D
D D D
S D D D
D D D H
9621
DSP Cards and IMCs
(400)
23.6-39


NNP 95-2035-01-00-B
In case 4, the data within the HCM frame is shifted automatically left by one bit,
which means that there must be a free bit for the data to move into. For example, if
the HCM frame format is F_DDD and H-bit signalling is enabled, the frame changes
to FDDDH.
For circuits with H-bit signalling on, the handshake signals should be configured as
end-to-end. Table 23.6-8 shows the possible end-to-end signalling for various RS-232
and V.35 configurations, as well as the pin on which the signal is carried.
Table 23.6-8: End-to-End H-bit Signalling Configurations
From/To
DTU (DTE)
DTU (DCE)
DTU (DTE)
DCD RTS
pin 8 pin 4
DCD DCD
pin 8 pin 8
DTU (DCE)
RTS RTS
pin 4 pin 4
RTS DCD
pin 4 pin 8
You can disable H-bit signalling by disabling either multidrop data bridging or
signalling.
23.6.7
Understanding Interface Speed

Configuring the interface speed differs, depending on whether the rate adaption
method is transparent or HCM.

For subrate transparent channels, the interface speed is determined by setting the
transport bandwidth. For super-rate transparent channels, the interface speed is set
separately (see chapter 20.15).
HCM rate adaption

Interface speed is the rate at which the device transmits data. Table 23.6-9 lists the
interface speeds supported by the data interface cards that provide HCM rate
adaption. (HCM supports only subrate speeds.) Interface speed is indicated by the
number of elements in the HCM frame; each element represents 800 b/s. For
interface speeds of 2.4 kb/s or less, allocate 2.4 kb/s of bandwidth, or three elements.
The default is 9600 b/s.
23.6-40
(400)
DSP Cards and IMCs

NNP 95-2035-01-00-B

Note
For asynchronous devices, the tolerance for over-speed and under-speed is 2.5% of
the nominal data rate.
1.2 kb/s operation. Do not connect them to an HCM SRM at this speed (see
sections 22.3.8 and 22.3.19).
Table 23.6-9: HCM Interface Speeds

User Interface Type
Sync HCM
150 (1)
1600
8000
16800
300 (1)
2400
9600
19200
600 (1)
800
4800
14400
28800
1200
7200
16000
32000
RS-232
4000
12000
24000
300 (1)
2400
9600
19200
40000
600 (1)
4000
12000
24000
48000
800
4800
14400
28800
56000
1200
7200
16000
32000
57600
RS-422, V.35, X.21
300
7200
600
9600
1200
14400
2400
19200
RS-232, RS-422, V.35,

X.21
38400 (2)
150 (1)
1600
8000
16800
38400
Async HCM (3)
150
4800
38400
Notes
1. Supported by DCCs with gate array version 1 only.
2. RS-232 operation at interface speeds above 38.4 kb/s is not guaranteed (for speeds above
38.4 kb/s, V.35 or X.21 interfaces should be used). If RS-232 speeds above 38.4 kb/s are required,
use short high-grade shielded cable.
3. The 2606 MainStreet DTU or 2610 MainStreet DTU async DTU ports do not support 14400 b/s.
Oversampling
For HCM circuits, asynchronous rates of up to 2400 b/s that are not listed in
Table 23.6-9 can be supported by oversampling. To oversample, set the interface
mode to synchronous. Then, multiply the asynchronous rate you want to support by
16. Enter the next highest synchronous interface speed listed in Table 23.6-9.
For example, to support 110 b/s (asynchronous), set the interface mode to
synchronous. Set the interface speed to 2400 b/s (16 110 b/s = 1760 b/s and
2400 b/s is the next highest synchronous rate supported).
DSP Cards and IMCs
(400)
23.6-41


NNP 95-2035-01-00-B
DDS/X.50 rate adaption

You can configure DCC and line card circuits to do DDS or X.50 rate adaption
independently of whether DDS or X.50 has been selected for the slot. (The slot
options configure the SRMs on the card, not the circuits.) A DCC or line card circuit
configured for DDS rate adaption can be configured for all the DDS interface
parameters.
For DDS, the valid interface speeds are 1200, 2400, 4800, 9600, 19200, 56000 and
64000 b/s. The default is 9600 b/s. Table 23.6-10 lists the interface speeds supported
by the data interface cards that provide X.50 rate adaption.
Table 23.6-10: X.50 Interface Speeds
User Interface Type
Sync X.50 Mode

1200
2400
4800
9600
19200
RS-232
1200
48000
2400
4800
9600
19200
RS-422, V.35, X.21
The basic X.50 and X.50 Telco Division 3 applications support interface speeds of
48000, 19200, 9600, 4800, 2400 and 1200 b/s. The X.50 Telco Division 2 application
supports interface speeds of 48000, 19200, 9600, 4800, 2400, 1200 and 600 b/s. The
default is 9600 b/s.
23.6.8
Understanding HCM Parameters

You can configure the DSP card SRM for:
HCM frame bandwidth

HCM data position
You can configure branch channels for HCM data position only.
Setting the HCM frame bandwidth

You can set the bandwidth allocated to the HCM frame to 8, 16, 24, 32, 40, 48, 56 or
64 kb/s. Enter the bandwidth as a number of columns (1 through 8), where each
column is 8 kb/s. The default is 8 columns or 64 kb/s. As shown in Figure 23.6-38,
the node manager displays the bandwidth allocated to the HCM frame as columns
containing Fs and dashes (). Any HCM rate-adapted circuit connected to the SRM
must have the same transport bandwidth as the SRM HCM frame bandwidth.
23.6-42
(400)
DSP Cards and IMCs

NNP 95-2035-01-00-B

The HCM bandwidth must be less than or equal to the aggregate channel
bandwidth. If you try to set the HCM bandwidth greater than the aggregate channel
bandwidth, the system displays the error message HCM bandwidth and transport
bandwidth conflict.
If the HCM frame bandwidth is less than the aggregate bandwidth, the system
automatically allocates the rest of the bandwidth to transparent data (indicated by
columns containing Ts).
Placing the HCM frame bandwidth

You set the location of the bandwidth allocated to HCM circuits by placing the
framing bit in any of the eight columns (B7 through B0). The default is B7. As shown
in Figure 23.6-38, the node manager displays the HCM framing bit as an F. All HCM
rate adapted circuits connected to the SRM must have their framing bits in the same
column as the framing bit of the SRM HCM frame.
The framing bit determines the first column allocated to the HCM frame. The HCM
frame then occupies as many columns as needed for the HCM bandwidth. If you
move the framing bit so that not enough bandwidth remains, the system reduces the
bandwidth. If you then move the framing bit, the bandwidth remains at the reduced
amount. If it is insufficient, you must reconfigure the bandwidth.
Setting the HCM data position

Specify the data position by entering the location of the first element in the form
Ff-Bn, where f is the row number (0 through 9) and n is the column number (0
through 7). The default is F0-B5.
You must change the data position in two circumstances.
If you change the transport position or transport bandwidth so that the data
position is no longer located in the HCM frame.

If you subrate-multiplex the HCM rate adapted circuit with another HCM rate
adapted circuit, you must change the data position so that the D bits do not
occupy the same elements.
Note
The node manager automatically fills in the signalling bit to the left of the data
position if signalling is on (see section 23.6.6).
23.6.9
Understanding Subframe Position

You must give each DDS and X.50 circuit to be subrate-multiplexed a unique
position number so that the data from more than one circuit does not occupy the
same frame. The valid multiplexing positions depend on the interface speed you
select for the circuit.
DSP Cards and IMCs
(400)
23.6-43


NNP 95-2035-01-00-B
Table 23.6-11 gives the valid DDS positions. For DDS, the default is 1 for 56, 9.6, 4.8,
2.4 and 1.2 kb/s channels and 2 for 19.2 kb/s channels.
Table 23.6-11: Valid Subframe Positions for DDS
Interface Speed (kb/s)
Valid Positions
56
19.2
2, 4
9.6
1 to 5
4.8
1 to 10
2.4
1 to 20
1.2
1 to 20
Table 23.6-12 lists valid X.50 positions. For X.50, the default is 1 for each interface
speed. Position 1 represents phase 1, position 5 phase 2, position 9 phase 3, position
13 phase 4 and position 17 phase 5. In each case, these numbers represent the first
channel in the phase. The numbers between two phases represent the other
channels.
Table 23.6-12: Valid Subframe Positions for X.50
Interface
Speed
(kb/s)
Basic X.50
X.50 Telco Division 2
X.50 Telco Division 3
48
19.2
1, 9 or 5, 13
1 and 33 or 17 and 49
1, 9 or 5, 13
9.6
1, 5, 9, 13, 17
1, 17, 33, 49, 65
1, 5, 9, 13, 17
4.8
1, 3, 5, 7, 9, 11, 13, 15,

17, 19
1, 9, 17, 25, 33, 41, 49, 57,

65, 73
1, 3, 5, 7, 9, 11, 13, 15,

17, 19
2.4
1 to 20
1, 5, 9, 13, 17, 21, 25, 29,

33, 37, 41, 45, 49, 53, 57,
61, 65, 69, 73, 77
1 to 20
1.2
1 to 20
odd numbered positions
1 to 20
0.6
1 to 80
Note
When you change the interface speed, the subframe position reverts to the default
for the new speed. You cannot change the subframe position if the circuit is
connected.
23.6-44
(400)
DSP Cards and IMCs

NNP 95-2035-01-00-B
23.6.10

Understanding Continuity Checking

You can configure the secondary channel for checking end-to-end continuity from
one DDS Access SRM to another. Continuity checking is available for the branch
channel of a DS0-A SRM and every branch channel of the DS0-B SRM. Continuity
checking is available for 19.2 kb/s only in DDS Access Version 2 SRMs.
When the DDS SRM at both ends is configured for continuity checking and
connected to the network, a Continuity Lost alarm is raised if LOS is detected. When
synchronization is lost, the alarm is raised at those points in the network where a
circuit is connected to a DS0-B or DS0-A SRM, including composite inputs.
When you have one SRM feeding into another, the following rules apply.
Any DS0-B SRM can be configured for continuity checking.

Continuity checking is done on local circuits only. In Figure 23.6-41, continuity
checking is carried out on three circuits at DS0-B #1 and on two circuits at

DS0-B #2.
A DS0-A SRM or an MJU can be configured for continuity checking only if it
feeds into the DDS network and not into another SRM or MJU (see
Figure 23.6-42).
Configure continuity checking as:
CONT_CHK to enable it
NO_CONT_CK to disable it (default)
Figure 23.6-41: Continuity Checking on DS0-B SRMs
#1
Data devices
(9.6 kb/s)
SRM#1 performs
continuity checking
on these data devices
#2
DS0-B-9.6
SRM
Data devices
(9.6 kb/s)
DDS
network
DS0-B-9.6
SRM
SRM#2 performs continuity

checking on these data devices
7157
DSP Cards and IMCs
(400)
23.6-45


NNP 95-2035-01-00-B
Figure 23.6-42: Continuity Checking on DS0-A SRMs and MJUs
#1
Data devices
(9.6 kb/s)
#2
DS0-A
SRMs or MJUs
Continuity checking
cannot be performed
Data devices
(9.6 kb/s)
DDS
network
DS0-A
SRMs or MJUs
SRM#2 can be configured

to perform continuity checking
7158
23.6.11
Configuring Rate Adaption and SRMs

Table 23.6-13 lists the steps in the overall configuration process for rate adaption and
SRMs. Table 23.6-14 lists the rate adaption and SRM parameters according to the rate
adaption method they support.
Table 23.6-13: Configuration Process
Rate Adaption Method
Transparent
or HCM
Step
DDS or X.50
Prepare the card to support SRMs.
(1)
Configure the data circuit for the rate adaption method.
Configure the branch channel to support rate adaption. The branch

channel must be on the same card as the SRM.
Configure the SRM for rate adaption.
From the Switching Shelf
Connect the data circuit to the branch channel and the branch
channel to the SRM.
Notes
1. = Optional
23.6-46
(400)
DSP Cards and IMCs

NNP 95-2035-01-00-B

Table 23.6-14: Rate Adaption and SRM Parameters

Transparent
HCM
Parameter
DDS
X.50
Continuity checking
(Telco)
Data position
Frame bit position
HCM bandwidth
Interface speed
Signalling
Subframe position
Subrate multiplexing
Transport bandwidth
Transport position
To configure the card for rate adaption and SRMs

CONFIG SLOT <sn> OPTIONS DDS_CORE
To configure the rate adaption method

CONFIG CIRCUIT <sn -cc> FUNCTION SRM
HCM_TRANS
DDS
X.50
DDS_ACCESS
VERSION_1
X50_TELCO
VERSION_2
DIV_2
DIV_3
SK000148
Note
DDS Access VERSION_1 specifies pre-Release 6.0 versions of the 3600 MainStreet
series bandwidth manager systems.
DSP Cards and IMCs
(400)
23.6-47


NNP 95-2035-01-00-B
To configure HCM and transparent SRMs

METHOD
HCM
TRANP_BW
F_POSITION
<bw>
<Bn>
HCM_BW
<hcm_bw>
TRANSPAREN
SK000149
where
Bn is B7* to B0
hcm_bw is the number of columns (1 to 8*)
To configure DDS SRMs

METHOD
DS-0A
POSITION
I/F_SPEED
<position>
<speed>
DS-0A_EC
DS-0B
MJU
CONT_CHK/
NO_CONT_CK*
MJU_EC
SK000150
where
position is a valid subframe position (see Tables 23.6-11 and 23.6-12)
Note
If you select DS0A_EC or MJU_EC for BCH error correction, the system
automatically sets the interface speed to 19.2 kb/s. Error correction should be used
for point-to-point connections, so if you select error correction for one end of a
connection, you should also select it for the other end.
For information on MJUs, see chapter 23.7.
23.6-48
(400)
DSP Cards and IMCs

NNP 95-2035-01-00-B

To configure HCM and transparent branch channels

COMPOSITE/
NO_COMP*
METHOD
TRANSP_BW TRANSP_POS SIG_ON/ I/F_SPEED DATA_POSN

SIG_OFF
<bw>
HCM
USER/SYSTEM* RATE_ADAPT
<Bn>
<speed>
<Ff-Bb>
TRANSPAREN
SK000151
where
Bn is B7* to B0
Ff-Bb is F0 to F9 and B7 to B0 (F0-B5*)
To configure DDS and X.50 branch channels

COMPOSITE/NO_COMP*
METHOD
USER/SYSTEM*
POSITION
SIG_ON/SIG_OFF*
<position>
HCM
TRANSPAREN
RATE_ADAPT
I/F_SPEED
<speed>
DDS_HCM or DDS
DS-0A DS-0A_EC DS-0B MJU MJU_EC
X50_HCM or X.50
DIV_2
DIV_3
SK000152
where
position is a valid subframe position (see Tables 23.6-11 and 23.6-12)
DSP Cards and IMCs
(400)
23.6-49

23.6.12

NNP 95-2035-01-00-B
Making SRM Connections

For an SRM on either a DCC (RS-232, X.21 or V.35), a Line card or a DSP card, you
can connect an aggregate channel to:
DCC circuits (RS-232, X.21, V.35)

DNIC circuits
2B1Q circuits
SRM branch channels on line cards or DSP cards
the supervisory channel on an X.21 or V.35 PRI card
DDS rules
When you are making connections to DDS rate adapted SRMs, the following rules
apply.
You can connect a data circuit configured for DDS only to an SRM configured for
DDS.
You cannot connect a data circuit to a DS0-B SRM with a lower interface speed.
23.6-50
For example, you cannot connect a line card or DCC circuit at 9.6 kb/s to an SRM
configured for the DS0-B_4.8 or DS0-B_2.4 multiplexing scheme. The exception
to this rule is that you can connect a 19.2 kb/s circuit to a DS0-B_9.6 SRM.
The position of a DDS rate adapted circuit must be valid for the multiplexing
scheme of the SRM to which you are connecting it. For example, you cannot
connect a DCC or line card circuit with an interface speed of 2.4 kb/s and a
position of six to an SRM configured for the DS0-B_9.6 multiplexing scheme,
because the valid positions for that scheme are one through five.
The system does not automatically override connections. For example, if a data
circuit is connected to a DS0-A SRM, you cannot connect a different circuit to the
same SRM without explicitly disconnecting the first circuit.
Circuits connected to branch channels of DDS SRMs cannot be protected.
Branch channels should be configured with the same DDS format as the SRM,
except for DS0-A and DS0-A_EC, which are interchangeable, and MJU and
MJU_EC, which are also interchangeable.
(400)
DSP Cards and IMCs

NNP 95-2035-01-00-B

X.50 rules
When you are making connections to X.50 rate adapted SRMs, the following rules
apply.
You can connect a data circuit configured for X.50 only to an X.50 SRM.
A data circuit you are connecting to an SRM cannot overlap any occupied
positions. For example, you cannot connect a DCC circuit with an interface speed
of 4.8 kb/s and a position of 3 to an SRM that is already connected to a 9.6 kb/s
circuit with a position of 1, because the 9.6 kb/s circuit occupies positions 1
through 4.
The system does not automatically override connections. For example, if a data
circuit is connected to an X.50 SRM, you cannot connect a different circuit to the
same position without disconnecting the first circuit.
Circuits connected to branch channels of X.50 SRMs cannot be protected.
The system assumes that circuits other than data circuits connected to SRMs
configured as X.50 are carrying X.50-formatted data in the correct format and
position for the configured multiplexing scheme. If this is not true, the data on
the connected circuit may be corrupted.
Making SRM connections

You can make the connections by selecting the branch channel manually or letting
the system select it automatically. If you choose the automatic method, the system
automatically selects an unused and unreserved branch channel, copies the data
circuit configuration to the branch channel, connects the data circuit to the branch
channel and then connects the branch channel to the SRM.
If you want to make the connection manually, you must specify a branch channel
and an SRM on the same DSP. If you try to connect a branch channel to an SRM that
is not on the same DSP, the system displays the message BRANCH and SRM
circuits must be on the same DSP.
To make SRM connections automatically

CONFIG CONNECT <sn-cc> or <sn-cc-p> or <x-sn-cc> or <x-sn-cc-p> TO_CIRCUIT
<sn-Mmm> or <sn-cc-Mmm> or <x-sn-Mmm> or <x-sn-cc-Mmm>
To make SRM connections manually

CONFIG CONNECT <sn-cc-p> or <x-sn-cc-p> TO_CIRCUIT <sn-cc-Bbb> or
<x-sn-cc-Bbb> TO <sn-cc-Mmm> or <sn-Mmm> or <x-sn-cc-Mmm> or <x-sn-Mmm>
Note
When an SRM on a DCC carries both HCM and transparent rate adapted circuits, the
state of the RTS (for DCE) or DCD (for DTE) control signal follows that of the
transparent circuit. This will disrupt the HCM circuits unless the transparent
DSP Cards and IMCs
(400)
23.6-51

NNP 95-2035-01-00-B
23.7
23.7 Multidrop Data Bridges and MJUs

Multidrop Data Bridges and MJUs

This chapter introduces voice conference bridging and explains how to configure the
23.7.1
a master device
a slave device
an MJU
MJU antistreaming
Understanding Multidrop Data Bridges and MJUs

This section describes multidrop data bridges and MJUs.
Multidrop Data Bridges

In a multidrop data bridge, several circuits take turns using the same bandwidth to
communicate with one circuit. Each slave device transmits data in that bandwidth
when requested by the master device. The master device sends polling messages to,
and looks for data from, the slave devices in that bandwidth. The end-to-end signal
between the master and the slave in a multidrop data bridge application is called
H-bit signalling (see section 23.6.6).
One example of a multidrop data bridge is several terminals taking turns to
communicate with a host computer. The circuit that all the other circuits
communicate with is connected to a master device (a computer) and is designated
the master; the rest of the circuits are connected to slave devices (terminals) and are
designated slaves. As shown in Figure 23.7-1, the master device controls the use of
the shared bandwidth by polling each slave in turn.
Figure 23.7-1: SRM Creating a Multidrop Data Bridge
Responding
Slave
devices
Branch
channels
Aggregate
SRM
channels
Master device
Polling
3118
DSP Cards and IMCs
(400)
23.7-1


NNP 95-2035-01-00-B
Circuit configuration
The data for each circuit in a multidrop data bridge must be positioned so that it
occupies the same elements. Each slave device transmits data in those elements at a
different time. The system automatically sets the configuration of the circuits
involved to half duplex and signalling off.
The master device communicates with the slave devices in the configured elements.
The system automatically sets the configuration of the master circuit to full duplex
and signalling off.
Caution
HCM multidrop data bridges do not support signal propagation. Do not configure
signalling on.
For circuits in an HCM or X.50 multidrop data bridge, the DCD control signal (if the
circuit is configured as gender DCE) or the RTS control signal (if the circuit is
configured as gender DTE) must be forced on (see section 22.3.7), unless H-bit
signalling is in use (see section 23.6.6).
If you are using the SRM for more than one data bridge or for subrate multiplexing,
the aggregate channel must be distributed at the far end before you can connect it to
the circuit carrying data for the master device.
Because certain circuits have been designated as slaves, the system connects those
circuits to the branch channels of the same SRM even though their data occupies the
same elements. The system does not connect circuits with overlapping data to the
branch channels of the same SRM unless they are designated as slaves.
Note
Do not use the copy adjust function in configuring a multidrop data bridge.
DDS SRMs
Any DDS SRM can support a multidrop data bridge configuration. If you want to
assign branch numbers to the DDS slave circuits, you must configure the SRM as:
DS0-A or DS0-A_EC
MJU or MJU_EC
Note
DS0-A_EC and MJU_EC configure the circuit for BCH error correction and set the
interface speed to 19.2 kb/s. For more information, see chapter 23.6.
23.7-2
(400)
DSP Cards and IMCs

NNP 95-2035-01-00-B

MJUs
You can configure a DDS, DDS Access or DDS Core SRM as an MJU. Chapter 23.6
describes DDS rate adaption.
As shown in Figure 23.7-2, you can assign a unique identification number (1 to 4) to
up to four branch channels for each MJU.
Figure 23.7-2: Multijunction Units and Branch Identification Numbers
Branch
channels 1
2
3
MJU
Aggregate
Channel
Aggregate
MJU
Channel
Master
device
Slave
devices
Branch
identification numbers
8797
These branch identification numbers enable the network to send individual

maintenance messages to the branch channels. Any other branch channels are given
a branch identification number of 0; this means they are unidentified and do not
respond to control codes.
You can also give an MJU a branch identification number that enables its aggregate
channel to be connected to a branch channel of another MJU as a multidrop slave.
Antistreaming
If you select antistreaming for an DDS Access (Version 2) or DDS Core MJU, the
system monitors the MJU branches and disables any branch that streams for longer
than the time you specify.
23.7.2
Configuring Multidrop Data Bridges

Table 23.7-1 lists the steps in configuring a multidrop data bridge. The procedures
for configuring SRMs are in chapter 23.6. For data circuit configuration, see
chapter 23.6; for PCM voice circuit configuration, see chapter 23.4.
DSP Cards and IMCs
(400)
23.7-3


NNP 95-2035-01-00-B
Table 23.7-1: Multidrop Bridge and MJU Configuration Process

Transparent
or HCM
DDS
DDS
Core
Step
X.50
1. Configure the card to support SRMs and assign the

appropriate type of rate adaption.
If you configure the SRM as DDS, the branch channel is
automatically configured as a composite DDS MJU
(DS-0A).
2. Configure the data or PCM voice circuits to support

SRMs.
Make sure the interface speeds and positions are the

same.
If you are connecting the circuits to a DS-0A SRM, the
positions must be the default for the interface speed.
()
(1)
()
If you want RTS signal propagation on a DDS master

circuit, see section 22.3.13.
Configure the branch channels for the appropriate type of

rate adaption.
()
If you want an MJU, configure the SRM as an MJU.
()
Configure MJU antistreaming.
()
()
Assign branch identification numbers.
Configure the SRMs.
3. Make the SRM connections from the switching shelf.
Notes
1. () = optional
To configure multidrop data bridges

CONFIG CIRCUIT <sn-cc> or <sn-cc-p> or <sn-Bbb> or <sn-cc-Bbb>
FUNCTION I/F_MODE MULTIDROP
MASTER
SLAVE
DISABLE*
SK000153
23.7.3
Configuring MJUs
An MJU combines up to four DS0-A or DDS_HCM inputs to produce a composite
DS0-A signal that you can apply to a second MJU, multiplex into a DS0-B signal or
multiplex directly into a DS1 timeslot. Table 23.7-1 lists the process for configuring
an MJU.
23.7-4
(400)
DSP Cards and IMCs

NNP 95-2035-01-00-B

To configure the card for SRMs

CONFIG SLOT <sn> OPTIONS DDS_CORE
To configure the circuit for SRMs

CONFIG CIRCUIT <sn-cc> FUNCTION SRM
DDS
DDS_ACCESS
VERSION_1
VERSION_2
SK000155
To configure the composite branch channel

1.
Configure the branch as a composite input.

CONFIG CIRCUIT <sn-cc-Bbb> FUNCTION COMPOSITE
2.
Configure the rate adaption method.

CONFIG CIRCUIT <sn-cc-Bbb> FUNCTION RATE_ADAPT
METHOD DDS
DS-0A
DS-0A_EC
MJU
MJU_EC
SK000156
To configure the SRM

METHOD
BRANCH_ID
<number>
MJU
MJU_EC
SK000157
where number is 0 (unidentified) through 4
DSP Cards and IMCs
(400)
23.7-5


NNP 95-2035-01-00-B
Note
If you select MJU_EC, the system selects BCH error checking and sets the interface
speed to 19.2 kb/s. For more information, see chapter 23.6.
23.7.4
Configuring MJU Antistreaming

To configure antistreaming parameters for an MJU, you can:
enable or disable antistreaming

define the time after which the system considers the branch streaming
(DECL_TIME) in the range of 0.5 to 6553.5 seconds in 0.5 second increments

define the time after which the system considers the branch idle (IDLE_TIME) in
the range of 5 to 255 ms in 5 ms increments
select data monitoring (DATA_MON), in which the system monitors the DDS
data bits
select control monitoring (CTL_MON), in which the system monitors the DDS
control bit (or the RTS lead in an HCM branch).
The MJU branches inherit their antistreaming parameters from the MJU, but you can
enable and disable antistreaming for each branch.
You must configure antistreaming on the MJU before the system will monitor the
branches, but you must configure the branches before you make the connections.
This means that the branches may be enabled for antistreaming, but no monitoring
takes place until you enable the MJU for antistreaming.
Note
When you are connecting a composite input into an MJU, you must configure
antistreaming on the input branch. If the input branch is a primary rate circuit, you
must configure it as a composite (see section 23.6.3).
23.7-6
(400)
DSP Cards and IMCs

NNP 95-2035-01-00-B

To configure antistreaming parameters

CONFIG CIRCUIT <sn-cc-Mmm> FUNCTION ANTISTREAM
ENABLED*/
DISABLED
DATA_MON/
CTL_MON*
DECL_TIME
IDLE_TIME
<decl_time>
<idle_time>
SK000158
where
decl_time is from 0.5 to 6553.5 s in 0.5 s increments (15 s*)
idle_time is from 5 to 255 ms in 5 ms increments (5 ms*)
To enable and disable an MJU branch

CONFIG CIRCUIT <sn-cc-Bbb> FUNCTION RATE_ADAPT ANTISTREAM
AS_PER_MJU/DISABLE
DSP Cards and IMCs
(400)
23.7-7

NNP 95-2035-01-00-B
23.8
23.8 Fax and Modem Data Transmission

Fax and Modem Data Transmission

This chapter explains how to configure the DSP4, DSP5H and DSP5 cards for G3 fax
relay and V.32 modem relay (collectively referred to in this chapter as data
transmission).
The DSP4, DSP5H and DSP5 cards modulate and demodulate G3 fax baseband data.
These cards provide G3 fax interfaces compliant with ITU G3 specifications T.4, T.30,
V.29, V.27 and V.21 (channel 2).
The DSP5 card also modulates and demodulates modem baseband data that is
compliant with ITU specifications V.32 and V.32bis.
23.8.1
Configuring DSP Cards for Fax and Modem Data

Transmission
For the DSP4 card, data transmission options are configured at the card slot level
(see chapter 23.2 for more information). The DSP5 and DSP5H cards are preset to
support data transmission; no configuration is required at the card slot level.
23.8.2
Configuring DSP Circuits for Data Transmission

You can configure the following fax and modem data transmission parameters on
the DSP4, DSP5 and DSP5H cards.
G3 fax relay
V.32 modem relay (DSP5 card only)
data transmission rate
data bandwidth
NSF frame handling mode
data transmit level
Enabling and disabling G3 fax relay

For the DSP4, DSP5H and DSP5 cards, you can select the following options for G3
fax relay:
FAX_ENABLE to enable G3 fax relay

FAX_DISABL to disable G3 fax relay
DSP Cards and IMCs
(400)
23.8-1


NNP 95-2035-01-00-B
Enabling and disabling V.32 modem relay

For the DSP5 cards, you can select the following options for V.32 modem relay:
V32_ENABLE to enable V.32 modem relay

V32_DISABL to disable V.32 modem relay
Note
V.32 modem relay is not supported on leased line circuits that omit the V.25 answer
tone outlined in the V.32 and V.32bis ITU standards.
Data transmission rate

In G3 fax relay mode, you can configure the DSP4 and DSP5H cards for a maximum
transmission rate of 4800 or 9600 b/s. The DSP5 card supports a maximum rate of
4800, 9600 or 14400 b/s.
Set the FAX_RATE to:
4800 for 4800 b/s

9600 for 9600 b/s
14400 for 14 400 b/s (available on DSP5 cards only)
The DSP4 and DSP5H cards have a default maximum transmission rate of 9600 b/s.
The DSP5 card has a default maximum rate of 4800 b/s for A-CELP circuits and
14400 b/s for LD-CELP circuits.
In V.32 modem mode, you can configure the DSP5 card for a maximum transmission
rate of 4800, 7200, 9600, 12000 or 14400 b/s.
Set the MODEM_RATE to:
4800 for 4800 b/s

7200 for 7200 b/s
9600 for 9600 b/s
12000 for 12 000 b/s
14400 for 14 400 b/s
The DSP5 card has a default maximum V.32 modem transmission rate of 7200 b/s
for A-CELP circuits and 14400 b/s for LD-CELP circuits.
If the data device at the far-end does not support the configured transmission rate,
the circuit automatically attempts to negotiate a data connection at a lower rate.
23.8-2
(400)
DSP Cards and IMCs

NNP 95-2035-01-00-B

Data bandwidth
Set the data bandwidth to a transmission rate that accommodates both the data
transmission rate and the compressed voice transmission rate. For example, if the
data rate is 4.8 kb/s and the compressed voice rate is 16 kb/s, the data bandwidth
must be set to 16 kb/s. Table 23.8-1 lists the possible data bandwidth configurations
which depend on voice compression, fax and modem rates and the rate adaption
method used.
Table 23.8-1: Possible Data Bandwidth Configurations
Data Bandwidth
Voice
Compression
Bandwidth
Fax Rate
Modem Rate
Rate Adaption
Method
8 kb/s
8 kb/s
4.8 kb/s
7.2 kb/s
Transparent /
HCM
9.6 kb/s
8 kb/s
9.6 kb/s
7.2 kb/s
HCM
10.4 kb/s
8 kb/s
9.6 kb/s
9.6 kb/s
HCM
12.8 kb/s
8 kb/s
9.6 kb/s
12 kb/s
HCM
14.4 kb/s
8 kb/s
14.4 kb/s
12 kb/s
HCM
15.2 kb/s
8 kb/s
14.4 kb/s
14.4 kb/s
HCM
16 kb/s
8 kb/s
14.4 kb/s
14.4 kb/s
Transparent /
HCM
16 kb/s
16 kb/s
14.4 kb/s
14.4 kb/s
Transparent /
HCM
Use the DATA_BW softkey to select a value from 1 to 20 (1 to 16 000 b/s in 800 b/s
increments).
NSF frame handling mode

You can configure the NSF frame handling mode for each circuit on a card.
Data devices exchange NSF frames to negotiate the use of functions they support
that are not specified by the G3 fax standard. Such features include encryption,
compression and high-quality (fine) transmission modes.
Configure NSF frame handling as:
NSF_TRANSP so that the DSP card forwards but does not process the contents
of the NSF frame; this allows the data devices to negotiate and use non-standard
features
Caution
Configuring NSF_TRANSP could result in the failure of a fax call.
NSF_BLOCK so that the DSP card does not forward NSF frames and the data
devices do not negotiate or use non-standard features
DSP Cards and IMCs
(400)
23.8-3


NNP 95-2035-01-00-B
Data transmit level

The data transmit level is the maximum allowable power of the data signal after
re-modulation. You can configure the data transmit level for each circuit on a DSP
card.
To set the data transmit level for the DSP4 card, select DATA_CONFIG and enter a
value from 3 to 15 dBm0. For the DSP5 and DSP5H cards, select DATA_TXLVL
and enter a value from 30 to 6 dBm0. The default transmit level for all DSP cards
is 13 dBm0.
To adjust transmit and receive gain levels for compressed voice circuits and data
transmission the DSP5H and DSP5 cards, select:
RX_GAIN to apply gain when a PCM-to-linear conversion is performed before
voice compression and data demodulation

TX_GAIN to apply gain when a linear-to-PCM conversion is performed after
voice decompression and data modulation
The configurable range for transmit and receive gain levels is from 12 to +12 dB in
increments of 0.1 dB. The default setting for transmit and receive gain levels is 0 dB.
Note
Transmit and Receive gain levels are independent of the data transmit level. The
transmit gain level must be taken into account when specifying the data transmit
level, as it is added to the data transmit level.
Automatic gain control

Automatic gain control allows voice compression circuits to control the gain applied
to incoming signals. When automatic gain control is enabled, the incoming signal is
either attenuated, amplified or untouched, depending on the level of the signal and
the optimal level for compression. Automatic gain control is applied after Receive
gain is applied, but before voice compression.
If automatic gain control is enabled, then the Receive gain must be set to 0 (zero),
otherwise, the signal may be attenuated to a point at which the automatic gain
control cannot detect the signal.
Select AGC_ON to enable automatic gain control, or AGC_OFF to disable it.
23.8-4
(400)
DSP Cards and IMCs

NNP 95-2035-01-00-B

To configure data transmission parameters for the DSP4 card

CONFIG CIRCUIT <sn-cc> FUNCTION HCV_DATA
DATA_CFG
RATE_ADAPT
DATA_TXLVL
DATA_BW
<level>
<n>
FAX_CONFIG
FAX_ENABLE*/ FAX_RATE
FAX_DISABL
NSF_HANDLG
NSF_TRANSP
4800
NSF_BLOCK*
9600*
SK000160
where
level is 15 to 3 dBm0 (* = 13 dBm0)
To configure data transmission parameters for the DSP5 card

RATE_ADAPT
DATA_BW
<n>
FAX/MODEM
FAX_DISABLE/
FAX_ENABLE*
LEVELS
FAX_RATE
MODEM_RATE
4800 9600 14400
4800 7200 9600 12000 14400
V32_DISABLE/
V32_ENABLE*
FAX_HANDLG
NSF_TRANSP
RX_TLP TX_TLP DATA_TXLVL AGC_ON/

AGC_OFF
NSF_BLOCK*
<tlp>
<data_tx>
SK001046
where
tlp is 120 to +120 (0*)
data_tx is 30 to 6 dBm0 (* = 13 dBm0)
DSP Cards and IMCs
(400)
23.8-5


NNP 95-2035-01-00-B
Note
The default FAX_RATE is 4800 for A-CELP circuits and 14400 for LD-CELP circuits.
The default MODEM_RATE is 7200 for A-CELP circuits and 14400 for LD-CELP
circuits.
To configure data transmission parameters for the DSP5H card

RATE_ADAPT
DATA_BW
<n>
FAX/MODEM
FAX_DISABLE/
FAX_ENABLE*
FAX_RATE
4800
LEVELS
FAX_HANDLG
RX_TLP TX_TLP DATA_TXLVL AGC_ON/

AGC_OFF
<tlp>
9600*
NSF_TRANSP
<data_tx>
NSF_BLOCK*
SK000820
where
tlp is 120 to +120 (0*)
data_tx is 30 to 6 dBm0 (* = 13 dBm0)
23.8-6
(400)
DSP Cards and IMCs

NNP 95-2035-01-00-B
23.9
23.9 Subrate Switching

Subrate Switching
This chapter introduces SRS on the DSP4 card and explains how to configure subrate
switching, create a subrate set, configure DS0 ports for SRS, and make SRS
connections.
23.9.1
Understanding SRS
An SRS lets you switch data at rates down to 800 b/s. You can group individual bits
together in subrate sets that then operate as a single entity.
As shown in Figure 23.9-1, there are three components in an SRS connection:
source and destination devices (primary rate or data circuits)

DS0 port on the SRS
internal SRS connection
DSP Cards and IMCs
(400)
23.9-1


NNP 95-2035-01-00-B
Figure 23.9-1: SRS Connections

Data on
a T1 SRM
F
a b
a
b
b
Data on a
DNIC SRM
F a a
64 kb/s connections
DSP4 card
DS-0
Port
Source and
destination
devices
SRS
Data on a
DCC SRM
c F
c
c
c
Data on an
E1 SRM
c F b
c
b
64 kb/s connections
c
c
b
3093
A switching shelf controlled system supports a total of 48 DSP4 cards configured for
SRS, with a maximum of eight DSP4 cards configured for SRS in any one peripheral
shelf. A locally controlled system supports a total of eight DSP4 cards configured for
SRS.
In a single-bandwidth slot, the DSP4 card supports fully non-blocking, full-duplex
SRSs for up to 30 DS0 (64 kb/s) ports; in a double-bandwidth slot, it supports up to
48 DS0 (64 kb/s) ports.
Use the 4602 MainStreet Intelligent NetworkStation or MainStreetXpress 46020
Network Manager for full subrate switching functionality.
SRS display
Figure 23.9-2 shows a partially filled SRS and Table 23.9-1 describes the symbols in
the display.
23.9-2
(400)
DSP Cards and IMCs

NNP 95-2035-01-00-B

Figure 23.9-2: HCM SRS Display Example

B7
B6
B5
B4
B3
B2
B1
B0
F0
F1
F2
F3
F4
F5
F6
F7
F8
F9
7269
Table 23.9-1: SRS Display Symbol Definitions

Symbol
Definition
Framing bit
Current subrate set
Bit is programmed connected
Bit is looped back
Bit is in a subrate set, but not connected
Bit is neither programmed connected, nor in any subrate set
When you are scrolling between transparent or HCM sets, ungrouped bits are
skipped over unless they are program-connected. If the current group is the first
group and you try to move to a previous group, the system displays the message
Showing first set. If the current group is the last group and you try to move to the
next group, the system displays the message Showing last set.
23.9.2
Configuring SRS
Table 23.9-2 lists the steps in the SRS configuration process. The steps followed
depend on whether you are configuring an SRS set using transparent, HCM or X.50
data bits, DDS data bits, or 4 kb/s CPSS.
DSP Cards and IMCs
(400)
23.9-3


NNP 95-2035-01-00-B
Table 23.9-2: Configuration Process

Transparent
HCM, X.50
DDS
Step
CPSS
Configure the DS0 ports.
Set up the subrate sets in the source and destination

ports.
Select a subframe from each of the two DS0 ports in

the connection.
Create an SRS that uses the five bit positions after

the F bit (F0-B6 to F0-B2).
Configure another DS0 for 4 kb/s CPSS.
From the Switching Shelf
Connect the two subrate sets.
Connect the two subframes.
Connect the SRS to the 4 kb/s CPSS DS0.
To specify set identifiers

Specify set identifiers for transparent SRS in the format <sn-SRS-dd-Bn> and for
HCM SRS in the format <sn-SRS-dd-FfBn>. For example:
CONFIG CONNECT <sn-SRS-dd-Bn> or <sn-SRS-dd-FfBn>
where
sn = slot number
SRS = subrate switch
dd = DS0 port: 1 to 30 without double bandwidth or 1 to 48 with double bandwidth
Bn = column number B7 to B0
FfBn = row number, column number F0B7 to F9B0
Specify set identifiers for DDS and X.50 in the format <sn-SRS-dd-set_id>. For
example:
CONFIG CONNECT <sn-SRS-dd-set_id>
where
sn = slot number
SRS = subrate switch
dd = DS0 port: 1 to 30 without double bandwidth or 1 to 48 with double bandwidth
set_id = see Table 23.9-3
23.9-4
(400)
DSP Cards and IMCs

NNP 95-2035-01-00-B

Table 23.9-3: Set Identifiers for DDS and X.50

Framing Type and Interface Speed
Valid Set Identifiers
DS0-A
DS0-B 2.4 kb/s
1 to 20
DS0-B 4.8 kb/s
1 to 10
DS0-B 9.6 kb/s
1 to 5
X.50 2.4 kb/s
1 to 20
X.50 4.8 kb/s
1, 3, 5, 7, 9, 11, 13, 15, 17, 19
X.50 9.6 kb/s
1, 5, 9, 13, 17
X.50 19.2 kb/s
5, 13 or 1, 9
X.50 48 kb/s
To configure a DSP4 card for subrate switching

CONFIG SLOT <sn>
TYPE
OPTIONS
OTHER
SRS
DSP
DSP4
SK000161
To copy and change sets

CONFIG CIRCUIT <sn-SRS-dd>
COPY_TO
FUNCTION
<sn-SRS-dd>
CHG_SET
PREV_SET NEXT_SET
NEW_SET ADD_TO_SET
DEL_FR_SET DEL_SET
SK000162
DSP Cards and IMCs
(400)
23.9-5

23.9.3

NNP 95-2035-01-00-B
Creating Subrate Sets

This section describes how to create transparent, HCM, DDS, X.50 and CPSS subrate
sets.
Transparent and HCM sets

The SRS switches data down to 800 b/s. For HCM data, this means that each bit can
be switched independently. Because most applications use data rates greater than
800 b/s, you can configure the associated bits together as a subrate set and switch
the set as a single entity.
For HCM data, you can create any number of contiguous or non-contiguous subrate
sets from any of the available 79 bits. The positions of the bit sets must match the bit
positions of the source or destination HCM frame.
For transparent data, you can create sets by grouping the 8 kb/s transparent
columns.
Subrate set restrictions
When you are creating transparent and HCM subrate sets, these restrictions apply.
Bits in the same set must use the same rate adaption method.
Bits in the same set must lie in the same DS0 switch.
Each bit belongs to one subrate set only.
A single bit is classified as a subrate set only if it is program-connected.
Creating sets
A subrate set is identified by the starting bit (the set identifier). The order of
transparent and HCM bits is assigned from the top left (F0B7) of the HCM map
(Figure 23.9-2) across to the bottom right (F9B0).
When you are creating a new set, or adding or deleting bits from an existing set, you
must enter a set identification number. After you enter the set identification number,
the node manager gives you the option of listing multiple bits.
For transparent rate adaption, enter the list in the form Bb1:Bb2, where Bb1 is the
column number of the first bit in the set and Bb2 is the column number of the last bit
in the set. For example, B7:B2 means that the bits are in columns B7 to B2. If you are
specifying a single bit position, enter only Bb1.
For HCM rate adaption, enter the list in the form Ff1Bb1:Ff2Bb2, where Ff1Bb1 is the
location of the first bit in the set and Ff2Bb2 is the location of the last bit in the set. For
example, F1B6:F1B1 means that the first bit in the set is located in position F1B6 and
the last bit in the set is located in position F1B1. If you are specifying a single bit
position, enter only Ff1Bb1.
If you try to enter a bit or set position that includes the location of the F-bit, the
system displays the message WARNING: Cannot select the F-Bit.
23.9-6
(400)
DSP Cards and IMCs

NNP 95-2035-01-00-B

If you try to enter a bit or set position incorporating a bit position that is already in
another set, the system displays the message WARNING: Proceed will destroy
connections and configuration.
If you try to create a new set that contains bits of different rate adaption methods,
the system displays the message Illegal list bits have mixed data format.
DDS and X.50 sets

For DDS DS0-A data, you do not need to create subrate sets. For DDS DS0-B data,
you create subrate sets by entering the interface speed.
For X.50, you configure the subrate set by entering the interface speed and a
sub-frame position.
A subrate set is identified by the starting bit (the set identifier). For X.50 and DDS,
the lowest sub-frame position is used as the set identifier.
For a DDS subrate set, you must configure the rate adaption method as DDS and
define the interface speed.
DDS DS0-A rate adaption for subrate sets supports five interface speeds:
2.4 kb/s
4.8 kb/s
9.6 kb/s (default)
19.2 kb/s
56 kb/s
DDS DS0-B rate adaption for subrate sets supports three interface speeds:
2.4 kb/s
4.8 kb/s
9.6 kb/s (default)
For an X.50 subrate set, you must configure the rate adaption method as X.50 and set
the interface speed as one of:
2.4 kb/s
4.8 kb/s
9.6 kb/s (default)
19.2 kb/s
48 kb/s
For an X.50 subrate set, you must define a sub-frame position. The number is a
subset of the 20 sub-frame positions. Table 23.6-12 lists valid sub-frame positions (set
identifiers) for each interface speed.
CPSS sets
An SRS cannot terminate CPSS data. You must connect a DCP circuit (with ANS
disabled) to one of the circuits on the switch with which CPSS data is switched.
DSP Cards and IMCs
(400)
23.9-7


NNP 95-2035-01-00-B
The SRS can rate-adapt 4 kb/s HCM CPSS into a format usable by a DCP circuit. In
the case where composite data is carrying CPSS, the SRS extracts the 4 kb/s CPSS
data from the circuit, rate adapts it and switches it to the destination circuit where a
DCP circuit is connected.
When you configure a circuit for 4 kb/s CPSS, the entire DS0 is used to carry the
CPSS.
For other CPSS speeds (such as 8, 16, 48 and 56 kb/s), you must configure the SRS as
transparent and use the bit positions beginning at B7 to be compatible with the DCP
cards.
To create sets
CONFIG CIRCUIT <sn-SRS-dd> FUNCTION
METHOD
TRANSP_BW
F_POSITION
HCM_BW
<bw>
<Bn>
<hcm_bw>
I/F_SPEED CHG_SET
<speed>
<position>
HCM*
TRANSPAREN X.50
DDS
DS-0A
CPSS_4K
DS-0B
PREV_SET NEXT_SET NEW_SET
ADD_TO_SET
<Bb1:Bb2> or
<Ff1Bb1:Ff2:Bb2>
DEL_FR_SET
DEL_SET
<set_id>
<Bb1:Bb2> or <Ff1Bb1:Ff2:Bb2>
SK000163
where
Bn is B7* to B0
hcm_bw is the column position (8*)
speed is in b/s to indicate the speed for a DDS or X.50 set (9600 b/s*)
position is the subrate position for an X.50 set (see Table 23.6-12)
set_id is the set identifier (see Table 23.9-3)
Bb1:Bb2 and Ff1Bb1:Ff2:Bb2 specify the locations of the first and last bits in a transparent and HCM set,
respectively
23.9-8
(400)
DSP Cards and IMCs

NNP 95-2035-01-00-B
23.9.4

Configuring DS0 Ports

For the SRS DS0 ports, you can configure:
rate adaption method (transparent, HCM, DDS, X.50 or 4 kb/s CPSS)

HCM bandwidth (for HCM)
transport bandwidth (for HCM)
F-bit position (for HCM)
interface speed (for DDS or X.50)
The X.50 interface speed configuration sets up the subrate sets of the X.50 frame.
If you try to configure a parameter that is not applicable to the rate adaption method,
the system displays the message Function key not valid with rate adaption
method.
To configure these parameters, see chapter 23.6. Table 23.1-2 provides the locations
of the configuration procedures.
Copying circuit configuration

You can copy the configuration of one DS0 port to another as long as they are on
subrate switches in the same locally controlled or peripheral shelf. The system copies
the configurable parameters (rate adaption method, HCM bandwidth, transport
bandwidth, F position and interface speed).
23.9.5
Making SRS Connections

You must make a 64 kb/s connection between a source device and one of the DS0
ports on the SRS.
The circuit types that you can connect to an SRS DS0 port are:
primary rate circuits

data circuits
output of an SRM
HCV compressed voice circuits
transitional signalling ADPCM compressed voice circuits
DCP circuits
any circuit on a subrate switch
The circuit types that you cannot connect to an SRS DS0 port are:
voice circuits
delta signalling ADPCM compressed voice circuits
DSP Cards and IMCs
(400)
23.9-9


NNP 95-2035-01-00-B
Making SRS connections

When you make an internal SRS connection, the source set identifier (the first bit in
the set) and the destination set identifier must be specified. If you try to make a
connection and do not enter the destination set identifier, the system displays the
message Bit is not set identifier.
Table 23.9-4 lists valid format conversions. For example, you could connect a DS0-A
SRS circuit to a DS0-B SRS circuit, or an HCM SRS circuit to a transparent SRS circuit.
Table 23.9-4: SRS Circuit Format Conversions
Rate Adaption Method for Source
DS0 Port
Rate Adaption Method for

Destination DS0 Port
Transparent or HCM
Transparent or HCM
DDS (DS0A/DS0B)
DDS (DS0A/DS0B)
X.50
X.50
HCM
CPSS
If you try to make a connection and the rate adaption methods are not the same, the
system displays the message Rate adaption modes do not match.
Caution
If you change any attribute of a circuit, the system destroys all connections and the
subrate set configuration associated with it.
To connect to an SRS DS0 port

CONFIG CONNECT <x-sn-cc> or <x-sn-cc-p> TO_CIRCUIT <x-sn-SRS-dd>
where x-sn-SRS-dd is the DS0 port number
Note
A data device connected to a DS0 port must have a rate adaption method compatible
with the configuration of the DS0 port.
To connect a transparent set

CONFIG CONNECT <x-sn-SRS-dd-Bn> TO_CIRCUIT <x-sn-SRS-dd-Bn>
To connect an HCM set

CONFIG CONNECT <x-sn-SRS-dd-FfBn> TO_CIRCUIT <x-sn-SRS-dd-FfBn>
23.9-10
(400)
DSP Cards and IMCs

NNP 95-2035-01-00-B

To connect a DDS or X.50 set

CONFIG CONNECT <x-sn-SRS-dd-set_id> TO_CIRCUIT <x-sn-SRS-dd-set_id>
where set_id is defined in Table 23.9-3
To connect a 4 kb/s CPSS circuit

CONFIG CONNECT <x-sn-SRS-dd-F0B6> TO_CIRCUIT <x-sn-SRS-dd-CPSS>
DSP Cards and IMCs
(400)
23.9-11

NNP 95-2035-01-00-B
23.10
23.10 BONDING
BONDING
This chapter introduces how to configure BONDING and make BONDING
connections.
23.10.1
Understanding BONDING
BONDING is a method of inversely multiplexing an n 56 kb/s or n 64 kb/s call
and transmitting it over networks in which the differential delay is unknown. The
BONDING protocol communicates with the remote end to set up the appropriate
number of channels. It enables the receivers to calculate the amount of delay needed
to make sure that the data is received in the same order in which it was transmitted.
As Figure 23.10-1 shows, the data stream may become delayed as it is inversely
multiplexed and then sent over channels with varying delays.
Figure 23.10-1: Data Transmission without BONDING
64 kb/s
network
ABC
A Channel 1
B Channel 2
C Channel 3
? ? ?
A Channel 1
B Channel 2
C Channel 3
6615
Figure 23.10-2 shows the same data stream with the BONDING function providing
delays for the quicker 64 kb/s lines, allowing the order of the data stream to remain
intact.
DSP Cards and IMCs
(400)
23.10-1
23.10 BONDING

NNP 95-2035-01-00-B
Figure 23.10-2: Data Transmission with BONDING
ABC
64 kb/s
Network
BONDING
BONDING
ABC
n x 64 kb/s
n x 64 kb/s
A Channel 1
A Channel 1
B Channel 2
B Channel 2
C Channel 3
C Channel 3
6616
Using BONDING
Typically, BONDING is used when inversely multiplexed 56 kb/s or 64 kb/s links
need to go over ISDN or different T1 or E1 streams to reach the remote end. This
practice results in an unpredictable delay between the channels, so BONDING is
used to equalize the delays and maintain data integrity.
Figure 23.10-3 shows a typical leased application in which two communicating data
devices (in 3600 MainStreet nodes #1 and #3) do not have enough bandwidth for
direct connection. The network manager takes the available three 64 kb/s timeslots
between 3600 MainStreet node #1 and 3600 MainStreet node #3 and three timeslots
between 3600 Mainstreet node #1 and 3600 MainStreet node #2 (and then the three
64 kb/s links between 3600 MainStreet node #2 and 3600 MainStreet node #3). Since
the delay is unpredictable, BONDING resources on 3600 MainStreet node #1 and
3600 MainStreet node #3 negotiate and equalize the delay.
Figure 23.10-3: BONDING Application
3600 MainStreet node #1
with BONDING

with BONDING
3 x 64 kb/s
Data device #2
(384 kb/s)
Data device #1
(384 kb/s)
3 x 64 kb/s
3 x 64 kb/s

6618
23.10-2
(400)
DSP Cards and IMCs

NNP 95-2035-01-00-B
23.10 BONDING
BONDING operation
The BONDING protocol begins with the two endpoints transmitting data over the
channels to exchange channel identifiers. This practice makes sure that each end has
the same channel identifiers. Then the endpoints transmit synchronization data over
the channels to allow the receivers at each end to determine the appropriate delays
to add to each frame so that the data stream is equalized. When delay equalization
is finished, the communications path is opened and data transfer can begin. Each
BONDING resource inversely multiplexes the n 56 kb/s or n 64 kb/s link into n
or n+1 separate 56 kb/s or 64 kb/s channels.
As Figure 23.10-4 shows, the side supplying the n 56 kb/s or n 64 kb/s data
stream is called the user side, and the side with the inversely multiplexed channels
is called the network side. During the call setup phase, the BONDING resource
determines the delay. When data is received from the network side during the data
transfer phase of the call, the BONDING resource applies the predetermined delay
to the 56 kb/s or 64 kb/s channels as appropriate and then sends the n 56 kb/s or
n 64 kb/s data stream to the user side. Until the data transfer begins, the user side
receives a continuous stream of ones from the BONDING resource.
Figure 23.10-4: BONDING in the 3600 MainStreet System
BONDING
User side
Network side
56 or 64 kb/s
1
2
n x 56 or 64 kb/s
IMC
n or n + 1
6617
The 3600 MainStreet system supports two BONDING modes: mode 1 and mode 3.
Mode 1 does the channel setup and then the delay equalization. Mode 3 BONDING
does the same as mode 1, and monitors the synchronization during the data transfer
phase of the call. Mode 3 operation uses an extra channel between the BONDING
resource and the network side for framing information resulting from this
monitoring.
A BONDING resource is a DSP circuit on an IMC. There are six DSP circuits on each
IMC. The user side can be any interface card capable of making super-rate
connections (any primary rate card and some DCCs). The network side can be any
of the E1, T1, E3, DS-3, BRI or 64 kb/s Codirectional cards or the 2B1Q channel unit,
or ISDN indices on the CPC.
DSP Cards and IMCs
(400)
23.10-3
23.10 BONDING
23.10.2

NNP 95-2035-01-00-B
Configuring BONDING
You can configure four BONDING parameters on the IMC:
mode (MODE)
bearer rate (BEARERRATE)
user side interface speed (I/F_SPEED)
synchronization alarm (see Maintenance, section 35.4.1).
To configure the BONDING mode, select:
MODE_1 for mode 1 operation

MODE_3 for mode 3 operation
To configure the bearer rate, select:
56k for 56 kb/s operation

64k for 64 kb/s operation
If you change the bearer rate, the system automatically makes sure that the interface
speed reflects the change. For example, if the bearer rate and interface speed are set
to 64 kb/s and 384 kb/s, respectively, and you change the bearer rate to 56 kb/s, the
system changes the interface speed to 336 kb/s.
To configure BONDING
MODE
BEARERRATE
I/F_SPEED
<speed>
MODE_1
MODE_3*
56k
64k*
SK000164
where speed is the user side interface speed in terms of kb/s; it must be a multiple of the bearer rate
Configuring BONDING call setup

When you configure the slot for an IMC, the system automatically sets the variable
parameters as follows:
23.10-4
BONDING mode to MODE_3

interface speed to 384 kb/s
bearer rate to 64 kb/s
synchronization alarm declare and clear time to three seconds
bond setup to OFF
end type to ANSWERING
(400)
DSP Cards and IMCs

NNP 95-2035-01-00-B
23.10 BONDING
Note
Bond setup allows you to change the BONDING call setup. If bond setup is set to
ON, the end type is configurable. If the end type is set to ANSWERING, you are able
to view and change the values of the directory numbers.
The mode, bearer rate, interface speed and synchronization alarm softkeys are the
same for the BONDING call setup configuration as they are for the BONDING
configuration (see above). The following shows the softkeys available for bond
setup, end type and directory.
To configure BONDING call setup

BOND_SETUP
END_TYPE
DIRERCTORY
ON/OFF*
ANSWERING* CALLING
MODIFY_ONE
MODIFY_ALL
SK000165
Figure 23.10-5 shows the NMTI screen for IMC circuits with BONDING call setup
enabled.
DSP Cards and IMCs
(400)
23.10-5
23.10 BONDING

NNP 95-2035-01-00-B
Figure 23.10-5: IMC BONDING Display

3600 MainStreet
1117-H1-00
DSP CCT: A1-01
Toronto:A
Alarms:1
11-May-1997
8:35a
NAME:
B7 B6 B5 B4 B3 B2 B1 B0
D D D D D D D D
Configured As
:
Rate Adaption
:
Interface Speed
:
Bearer Channel Rate:
Number of Branches :
Alarm Declare time :
Alarm Clear time
:
BOND Setup
:
End Type
:
BOND_MODE_3
BONDING - MODE_3
384 kbps
64 kbps
7
3 seconds
3 seconds
ON
Answering
D = DATA
CONFIG CIRCUIT 1-1 FUNCTION
1-MODE
6-
23.10.3
27-
38-CANCEL
49-QUIT
5-BOND_SETUP
0-
Making BONDING Connections

To make a BONDING connection, you must:
make the super-rate connection between the user side circuit and the DSP on the
IMC
connect the DSP branch channels to the network side circuit
To connect the user side to the DSP

CONFIG CONNECT <sn-cc> TO_CIRCUIT <sn-cc>
where the first sn-cc identifies the user side card slot and circuit and the second sn-cc identifies the IMC
slot and the DSP
To connect the DSP to the network side

CONFIG CONNECT <sn-cc-Bbb> TO_CIRCUIT <sn-cc>
where
sn-cc-Bbb identifies the branch channel on the DSP (1 to 15 in mode 1; 1 to 14 in mode 3) and sn-cc identifies
the network side card slot and circuit
for a DSP circuit running at n 56 kb/s or n 64 kb/s only n branches are allowed for mode 1 operation
or n+1 for mode 3 operation
23.10-6
(400)
DSP Cards and IMCs

NNP 95-2035-01-00-B
23.10 BONDING
Note
Although there are six DSP circuits on the IMC, the total number of backplane
channels is 60. With each BONDING channel using one channel for the user side
connection and one channel for the network side connection, the maximum number
of 64 kb/s links using BONDING on each IMC is 30. When mode 3 BONDING is
selected, this number is smaller because n+1 connections between the DSP and the
network side are needed for n connections between the user side and the DSP.
Because the DSP has only one bidirectional serial port, the interface with the
processor is limited to 32 links of 64 kb/s each. Two of these links are used for
message exchanges. As each BONDING channel needs one channel for the user side
connection and one for the network side connection, the maximum number of
56 kb/s or 64 kb/s links that can be used for BONDING on each DSP is 15.
DSP Cards and IMCs
(400)
23.10-7

NNP 95-2035-01-00-B
23.11

Super Tandem Operation

This chapter describes super tandem voice compression and explains how to
configure super tandem operation on DSP cards.
23.11.1
Understanding Super Tandem Operation

The super tandem voice compression algorithm compresses 64 kb/s voice circuits to
8 kb/s or 16 kb/s (16 kb/s provides higher quality voice reproduction). The voice
compression protocol allows compressed voice circuits to pass transparently
through any digital PABX without loss of voice quality. Calls are cross-connected
through the PABX as compressed voice circuits, eliminating the need to decompress
and recompress them. If there are any analog PBXs in the network, the system
reverts to standard (default) voice compression.
The following conditions must be met for super tandem operation to function:
The connection circuit of the PBX must be a clear 64 kb/s circuit.

Both ends of the connection must be configured with the same voice compression
algorithm, bit rate and data bandwidth.
The DSP4 and DSP5H cards support super tandem operation. The DSP5 card
supports super tandem operation when it is configured for A-CELP voice
compression.
Caution
On the DSP4 card, the minimum firmware required to support super tandem
operation is $E.
If a DSP4 card with $9 (or less) firmware is inserted into a slot configured to support
super tandem operation, a Revision/Feature Mismatch alarm is raised and the card
is taken out of service. To rectify this, disable all circuits on the card that are
configured for super tandem operation and reset the DSP4 card using
MAINT ON_SLOT <sn> RESET_CARD PROCEED.
DSP Cards and IMCs
(400)
23.11-1

23.11.2

NNP 95-2035-01-00-B
Configuring Super Tandem Operation for DSP Cards

The following lists the steps necessary to enable super tandem operation.
enable or disable super tandem operation

enable or disable forced super tandem operation
set the super tandem synchronization time
connect the super tandem circuits
To enable or disable super tandem operation select:
stHCV_EN or stHCV_DIS for the DSP4 card

ENABLE or DISABLE for the DSP5H and DSP5 cards
Both the local and remote voice compression circuit must be enabled for super
tandem operation. If either end is not capable of operating in super tandem mode,
transmission reverts to the standard (default) voice compression protocol for the
card.
With forced super tandem operation, you can use the super tandem protocol on
unidirectional connections, for example, on VCBs set for redundant mode. To enable
forced super tandem operation, select:
FORCE_ON to enable forced super tandem operation

FORCE_OFF to disable forced super tandem operation
Note 1
If you disable super tandem voice compression, forced super tandem operation is
automatically set to FORCE_OFF.
Note 2
Forced super tandem operation is not supported on circuits configured for A-CELP
voice compression.
The super tandem synchronization time is the amount of time it takes for the super
tandem circuit to determine whether the remote circuit has super tandem operation
enabled. For the DSP4 card this value can range from 0.1 to 3.1 seconds in 0.1 second
increments. The synchronization time range for the DSP5H and DSP5 card is from
0.1 to 5.0 seconds in 0.1 second increments.
You connect super tandem circuits the same way as HCV and A-CELP circuits (see
chapter 23.3).
23.11-2
(400)
DSP Cards and IMCs

NNP 95-2035-01-00-B

To configure super tandem parameters on the DSP4 card

stHCV
stHCV_DIS/
stHCV_EN*
FORCE_ON/FORCE_OFF*
SYNC_TIME
<sync>
SK000819
where sync is 0.1 to 3.1 seconds in 0.1 second increments (* = 1 second)
To configure super tandem parameters on the DSP5H and DSP5 cards

SUPER_TAND
DISABLE/ENABLE*
FORCE_ON/FORCE_OFF*
SYNC_TIME
<sync>
SK000818
where sync is 0.1 to 5.0 seconds in 0.1 second increments (* = 1 second)
DSP Cards and IMCs
(400)
23.11-3

NNP 95-2035-01-00-B
23.12

Combined Voice Compression, Fax

and Modem Operations
This chapter describes combined voice compression, G3 fax relay and V.32 modem
relay operations and explains how to configure these combined operations on DSP
cards.
23.12.1
Understanding Combined Operations

On DSP cards, data (fax and modem) and voice signals can be transported on the
same circuit. A combined operation circuit has two modes: voice and data. Voice
mode is the default mode. When the DSP detects fax or modem signals, it switches
from voice to data mode; when it detects no fax or modem signals, the DSP switches
back to voice mode. While in voice mode, the circuit behaves as a normal
compressed voice connection.
Table 23.12-1 lists the applications that can be used in combined operations and the
DSP cards that support these applications.
Table 23.12-1: Applications Eligible for Use in Combined Operations
Card
DSP4
HCV
LD-CELP
DSP5
DSP5H
A-CELP
Super
Tandem
G3 Fax Relay
V.32 Modem
Relay
Notes
1. For DSP5 cards, super tandem operation is supported only on circuits configured for A-CELP voice compression.
Figure 23.12-1 shows a DSP4 card equipped with a fax/HCV module, which is
connected to an analog voice interface (LGE card or channel unit) for input and an
aggregate interface (T1 card) for output. By automatically switching between data
and voice mode, the voice compression data application allows both data and voice
to share the same aggregate bandwidth.
DSP Cards and IMCs
(400)
23.12-1


NNP 95-2035-01-00-B
Figure 23.12-1: G3 Fax Example
MainStreet node
Phone
LGE
PBX-1
DSP4
fax/HCV
module
T1
Network
FAX
5368
From the access side, the card accepts a PCM-encoded stream representing a
voiceband signal. The card then decides whether the signal is modulated data or
voice and processes it in data or voice mode accordingly.
In data mode, the card demodulates the signal and transports this digital data over
the network. The DSP4 and DSP5H cards can operate at either 4800 or 9600 b/s. The
DSP5 card can operate at either 4800, 9600 or 14 400 b/s for fax transmissions, or at
either 4800, 7200, 9600, 12000 or 14 400 b/s for V.32 modem transmissions.
The transmission mode changes from data to voice if the card detects any of the
following conditions:
ABCD signalling change

DCN message sent from a fax machine
time-out in the fax protocol
loss of communication with the far end device
loss of HCM sync
In voice mode, the card which is using A-law or Mu-law companding (as
configured), compresses the PCM voice samples to either 8 or 16 kb/s using voice
compression and transports this data over the network. The transmission mode
changes from voice to data mode if the card:
detects fax or modem modulation

receives a message from a far end device
From the network side, the DSP4, DSP5 and DSP5H cards accept unmodulated data
or compressed voice, reconstruct the original modulated data or voice signal, then
delivers a PCM stream to the system.
23.12.2
Configuring Combined Operations

The DSP4, DSP5H and DSP5 cards offer combined G3 fax relay and compressed
voice operations. These combined operations provides the same G3 fax transmission
capabilities as in ordinary fax transmission. The DSP4 card must be configured for
combined mode. The DSP5 and DSP5H are preset to support combined mode.
Chapter 23.8 describes G3 fax transmission.
23.12-2
(400)
DSP Cards and IMCs

NNP 95-2035-01-00-B

The DSP5 card also offers combined V.32 modem relay and compressed voice
functionality. These combined operations provide the same modem relay
capabilities as for ordinary modem relay. Chapter 23.8 describes V.32 modem relay.
You can connect the same types of circuits to the data and super tandem circuit as
those you connect to a standard HCV or A-CELP circuit. (Chapter 23.3 describes
voice compression circuit connections). These circuits can support data bandwidths
of 8, 9.6 and 16 kb/s for HCM rate adapted channels, and 8 and 16 kb/s for
transparent channels.
The 8 kb/s configuration allows data rates up to 4.8 kb/s and voice compression at
8 kb/s. The 9.6 kb/s configuration allows data rates up to 9.6 kb/s and voice
compression at 8 kb/s. The 16 kb/s configuration allows data rates up to 9.6 kb/s
and voice compression at 8 or 16 kb/s. For a complete list of possible data bandwidth
configurations, see section 23.8.2.
To enable combinedoperations, configure the following:
combined operation on the DSP4 card

rate adaption parameters (see section 23.3.5)
data transmission parameters (see section 23.8.1)
data transmit level (see section 23.8.2)
super tandem operation (see chapter 23.11)
To configure the DSP4 card for combined operation

CONFIG SLOT <sn> OPTIONS OTHER
DSP Cards and IMCs
(400)
23.12-3
3600 MainStreet series bandwidth managers

NNP 95-2035-01-00-B
24. DCP Cards

NNP 95-2035-01-00-B
24.1
24.1 Understanding DCP Card Configuration

Understanding DCP Card

Configuration
This chapter introduces the DCP card and provides a summary of the configuration
procedures in this part of the manual.
24.1.1
Understanding DCP Cards

The DCP card provides high-speed CPSS routing, using its own switching table, to
remove most of the CPSS messaging burden from the Control card. The DCP card is
typically used in large networks. It is used in nodes with high CPSS traffic, in
networks with large numbers of 3612 MainStreet systems (4 kb/s CPSS), and for
CPSS over satellite links. You can install the DCP card in any UCS 1 to 8.
24.1.2
Configuring DCP Cards

Table 24.1-1 lists the basic DCP card configuration parameters. Each parameter has
a list of options with any default value marked by an asterisk. See chapter 17.6 for
the CPSS functions of the DCP card.
Table 24.1-1: DCP Card Configuration Parameter and Options
Parameter
Options
Card Level
CPSS
See Table 17.6-2.
Slot Level
DCP Cards
Card slot
DCP
4 kb/s CPSS
4 kb/s CPSS
no 4 kb/s CPSS
Backplane communications
dedicated
shared*
Serial port
See Table 17.3-2.
(400)
24.1-1

NNP 95-2035-01-00-B
24.2
24.2 DCP Card Slots

DCP Card Slots

This chapter explains how to configure DCP card slots.
24.2.1
Understanding DCP Card Slots

You must configure card slots for the DCP cards before you can configure or connect
card type with specific card parameters. When you configure a slot, the system
configures the circuits for that slot with default settings.
In addition to configuring the card slot for the DCP card, you can also configure the
backplane communications link from the DCP card to the Control card. For
information on backplane card communications, see chapter 17.7.
24.2.2
Configuring DCP Card Slots

Configure the DCP card for its card slot and to carry 4 kb/s CPSS. This configures
circuits 24 to 31 on the DCP card to carry CPSS.
DCP Cards
(400)
24.2-1
24.2 DCP Card Slots


NNP 95-2035-01-00-B
To configure DCP card slots

CONFIG SLOT <sn>
TYPE
OPTIONS
4KBPS/NO_4KBPS*
AS_PRESENT
PACKET
DCP
SK000167
Note
Use the AS_PRESENT softkey if there is a DCP card installed in the slot.
cards installed in the shelf, press the CONFIG_ALL softkey and the <Esc>
simultaneously.
24.2-2
(400)
DCP Cards

NNP 95-2035-01-00-B
25. Frame Relay Services

NNP 95-2035-01-00-B
25.1
25.1 Understanding Frame Relay Configuration

Understanding Frame Relay

Configuration
This chapter describes the frame relay services available on the FRS, FRE, X.25 FRE
and PE cards, and provides a summary of the configuration procedures.
Note
An X.25 FRE card is an FRE card loaded with MainStreet X.25 software; it has the
same frame relay features and configuration requirements as the standard FRE card.
All information about the FRE card also applies to the X.25 FRE card.
To configure X.25 services on the PE and X.25 FRE cards, see chapter 27.4.
25.1.1
Understanding Frame Relay on FRS, FRE and PE Cards

The frame relay services described in this document are supported on the platforms
listed in Table 25.1-1.
Table 25.1-1: Frame Relay Platforms
Card
Part Number
Generic
FRS Dual 1 Mbyte Flash

FRS Dual 1 Mbyte Flash with SRIM
90-1459-03 or 04
90-3259-01
P114
FRE
90-1638-10 or 11
P413
X.25 FRE
90-1638-13 or 14
PA11 F2
PE
90-2311-01 or 12
P611 F2
The FRS, FRE and PE cards give the node the ability to switch the output of the frame
relay interfaces offered by user devices over any primary rate or data link. The FRS
card provides a maximum sustained throughput of 2000 fps, which is 64-byte frames
over a 1920 kb/s frame stream. The FRE card provides a maximum sustained
throughput of 10 000 fps, which is 64-byte frames over two 1536 kb/s frame streams.
(400)
25.1-1


NNP 95-2035-01-00-B
For frame relay switching, the FRS, FRE and PE cards comply to the relevant sections
of the following standards:
ANSI T1.618
ITU-T Q.922 Annex A
Addendum to ANSI T1.606
ANSI T1.617a Annex D (1994)
ITU-T Q.933 Annex A (1994)
Frame Relay Forum document number 001-208966
The FRS card is designed for small to medium frame relay switching requirements.
FRS cards are typically used independently, although FRS-to-FRS card connections
are supported using the circuit-switched backplane bus. FRS cards also support
HDLC encapsulation services that allow them to function as feeder nodes for X.25
subrate or super-rate access to PE or X.25 FRE cards.
The FRE and PE cards are designed for high-capacity frame relay switching
requirements. Up to 64 FRE or PE cards can be used in a 36120 MainStreet system.
FRE and PE cards access both the circuit-switched backplane bus and a 100 Mb/s
packet-switched bus called the FASTbus to provide high-speed connections
between the cards.
Frame streams
A frame stream specifies the bandwidth over which frame relay connections
operate. You can configure a frame stream on any primary rate or data link. On a
primary rate link, you can configure a frame stream on any part of the link, allowing
both frame-relay and circuit-switched service on the same link.
The FRS card supports up to 31 frame streams with a combined bandwidth of
1984 kb/s. Any one frame stream can have a bandwidth of up to 1920 kb/s.
The FRE and PE cards supports up to 62 frame streams with a combined bandwidth
of 3968 kb/s. Bandwidth is split between two backplane buses, each of which
supports a bandwidth of up to 1984 kb/s or 31 channels of 64 kb/s each. Any one
frame stream can have a bandwidth of up to 1984 kb/s. Each FRE and PE card also
has access to the FASTbus.
Data link connections

DLCs join one logical data link to another. Table 25.1-2 lists the maximum number
of DLCs and the DLCIs used on FRS, FRE and PE cards. Each DLC can terminate on
a different user device. All DLCs are bidirectional (full duplex).
25.1-2
(400)

NNP 95-2035-01-00-B

Table 25.1-2: FRS, FRE and PE Card DLCs and DLCIs

Card, Interface or Stream
Total DLCs
DLCI Range
For each FRS card
1024
16 to 1007
For each FRE or PE card
1984
16 to 1007, and
2000 to 3983
For each frame stream
992
16 to 1007
For each FASTbus interface on any

FRE or PE card
1984
2000 to 3983
Permanent virtual circuits

Each DLC on a frame stream represents a virtual circuit segment. DLC
cross-connections configured on FRS, FRE and PE cards connect these virtual circuit
segments together to form a virtual end-to-end connection, or PVC between two
user devices. For example, in Figure 25.1-1, FRE 1 has been configured to
cross-connect DLCs S2-875 and S12-875.
Figure 25.1-1 shows a frame relay network using FRE cards to interconnect three
8230 MainStreet Ethernet Little Bridges configured with frame relay interfaces.
There are two PVCs configured, one connecting an 8230 MainStreet Ethernet Little
Bridge (A) to an 8230 MainStreet Ethernet Little Bridge (B) and the other connecting
an 8230 MainStreet Ethernet Little Bridge (A) to an 8230 MainStreet Ethernet Little
Bridge (C).
Bandwidth use
In a frame relay network, idle DLCs do not consume any bandwidth. DLCs share the
frame stream bandwidth, which the system allocates on demand.
In Figure 25.1-1, when FRE 1 needs to transmit a frame on DLC 876, the system
allocates all the bandwidth configured for frame stream S12 to the transmission.
While DLC 875 is idle, it consumes no bandwidth.
(400)
25.1-3


NNP 95-2035-01-00-B
Figure 25.1-1: Frame Relay Network Example

8230
MainStreet bridge B
S9-875
PVC 1 (DLC 875)

PVC 2 (DLC 876)
S9
S12-875 X S9-875
S12-876 X S7-876
FRE
2
S12
S7
36120
MainStreet
S2-875
S2-876
S9
S2
S9-876
FRE
8230
1
MainStreet bridge
A
36120 MainStreet bridge
S2-875 X S12-875
S2-876 X S12-876
FRE
3
8230
MainStreet bridge C
36120 MainStreet bridge
S7-876 X S9-876
4076
Class-of-service parameters
The bandwidth allocated to its frame stream limits a DLC maximum throughput (or
access rate). You can configure class-of-service parameters for each DLC
individually to define the maximum throughput and burst size allowed on the DLC.
This practice lets you control the amount of bandwidth consumed by one DLC and
prevents a large burst of traffic on one DLC from depriving others of the bandwidth
they share.
The four class-of-service parameters are:
CIR:
25.1-4
Specifies the rate of user data transfer that the network commits to transfer under
normal conditions.
Bc:
Specifies the maximum number of bits of user data that the network commits to
transfer over the committed rate measurement interval (Tc) under normal
conditions.
Be:
Specifies the maximum number of bits of uncommitted user data in excess of Bc
that the network attempts to transfer over the committed rate measurement
interval (Tc).
Tc:
Defines the time interval over which the user may transfer Bc bits of committed
or Bc+Be bits of uncommitted data. Tc is not a periodic measurement interval, but
a sliding window used to measure the rate of incoming data. Tc is not
user-configurable. When CIR and Bc are > 0, Tc is calculated as Bc/CIR. When
CIR and Bc = 0, Tc is calculated as Be/Access Rate.
(400)

NNP 95-2035-01-00-B

A DLC may transmit a maximum of Bc bits over a time interval of Tc seconds,

defining the CIR for the DLC. Under normal conditions, the DLC is guaranteed this
rate of throughput.
A DLC may transmit a burst in excess of its CIR, provided that the total number of
bits transmitted over a time interval of Tc seconds is not more than Be + Bc. The card
sets the DE bit in frames transmitted in this range to allow a frame relay switch
experiencing congestion to discard the frames.
If a DLC tries to transmit more than Be + Bc bits over Tc seconds, the system discards
all frames in this range before transmission.
Figure 25.1-2 shows the relationship between Bc, Be, CIR and Tc.
ss
ra
te
Figure 25.1-2: Class-of-service Parameters
Ac
ce
Discard
all frames
Be + Bc
t
urs
rat
.b
x
Ma
Bc
Send frames
as discard eligible
CIR
Send frames
as received
To
To + Tc
2832
Congestion management
The FRS, FRE and PE card congestion management mechanisms use class-of-service
parameters to avoid and recover from switch, FASTbus and frame stream
congestion.
Note
When an FRS, FRE or PE card becomes congested, the congestion affects only that
card. It does not affect other FRS, FRE or PE cards or the Control card.
The FRS, FRE and PE cards respond to congestion indicators in a private frame relay
network made up of FRS, FRE and PE cards, and when connected to a public frame
relay network or customer premise equipment.
(400)
25.1-5


NNP 95-2035-01-00-B
An FRS, FRE or PE card becomes congested when the applied traffic load exceeds its
capacity. Under these conditions, the card buffers frames. The system measures the
degree of congestion in terms of buffer use: the higher the use, the greater the
congestion. The system measures buffer use against user-configured congestion
thresholds.
CPU congestion occurs when the switching capacity of the card CPU is exceeded.
When this capacity is exceeded, a CPU Congested alarm is raised.
This chapter describes the following congestion management aspects:
congestion thresholds
congestion notification parameters (FRE and PE only)
congestion avoidance
congestion recovery
Congestion thresholds
For the FRS card, you can configure congestion thresholds for the switch and for
each frame stream. For the FRE and PE cards, you can configure congestion
thresholds for the switch, FASTbus interface and each frame stream. Table 25.1-3
summarizes the congestion threshold options available for the cards.
Table 25.1-3: FRS, FRE and PE Card Congestion Thresholds
Card
ACT
SCT
MCT
Switch
FRE and PE
1500 kbyte (1)
0 to 100% of ACT
0 to 100% of ACT
(MCT SCT)
FRS
64 kbyte (1)
0 to 100% of ACT
0 to 100% of ACT
(MCT SCT)
FRE and PE
10 to 1000 kbyte (2)
0 to 100% of ACT
0 to 100% of ACT
(MCT SCT)
FRS
FRE and PE
1 to 1500 kbyte (3)
0 to 100% of ACT
0 to 100% of ACT
(MCT SCT)
FRS
1 to 64 kbyte (3)
0 to 100% of ACT
0 to 100% of ACT
(MCT SCT)
FASTbus
Stream
Notes
1. This is the amount of buffer space available for buffering frames as they are switched from one DLC
to another. For the switch, ACT is not user-configurable.
2. This is the amount of buffer space available for use as transmit queues to buffer frames transmitted
on the FASTbus.
3. This is the amount of buffer space available for use as transmit queues to buffer frames transmitted
on the network. You can configure ACT for each stream, to control the amount of buffer space
consumed by any one frame stream and prevent one severely congested frame stream from
consuming all frame stream buffer resources.
25.1-6
(400)

NNP 95-2035-01-00-B

Figure 25.1-3 illustrates the relationship between ACT, SCT and MCT. The system
measures SCT and MCT congestion thresholds as a utilization percentage of total
buffer space available (ACT).
Figure 25.1-3: Congestion Thresholds
ACT
Severely
Congested
(Red)
SCT
Mildly
Congested
(Yellow)
Buffer Space
Consumed
MCT
Not
Congested
(Green)
Buffer Space
2689
The level of congestion (Red, Yellow or Green state) determines when the card
initiates congestion avoidance and recovery procedures.
Congestion notification parameters
On FRE and PE cards, you can configure the following frame relay parameters for a
frame relay switch, stream or FASTbus resources:
filtering/non-filtering
congestion raise time
congestion clear time
report type
Filtering debounces the transition of the switch, stream or FASTbus buffer use
between the threshold states. As shown in Figure 25.1-4, when filtering is enabled, a
smooth contiguous transition occurs between the states. When the SCT is exceeded,
the filter delays the raising of a congestion alarm by filtering out the temporary
spikes in congestion, giving a long-term congestion average. On the FRE and PE
cards, filtering can be disabled; in this case, the transition consists of sharp spikes,
allowing alarms to be raised more frequently and giving short-term statistics on
actual buffer space utilization.
(400)
25.1-7


NNP 95-2035-01-00-B
Note
Filtering is enabled by default and cannot be disabled on the FRS card.
Figure 25.1-4: Congestion Filtering
Enters
Red state
Leaves
Red state
Buffer space usage
ACT
Red state
SCT
Yellow state
MCT
Green state
Time
ECN signalling procedures
Frame discard using DE bit
Unfiltered or actual buffer space utilization
Filtered buffer space utilization
3873
The congestion raise time is the length of time that the resource remains in the Red
state before a congestion alarm is raised. The raise time can be configured on the FRE
and PE cards but is fixed at 5 seconds for the FRS card.
The congestion clear time is the length of time that a previously congested resource
remains out of the Red state before a congestion cleared alarm is raised. The clear
time can be configured on the FRE and PE cards but is fixed at 10 seconds for the FRS
card.
The report type is used to determine whether the node reports congestion
information as alarms or network management events (which include alarm
reports).
Congestion avoidance
The card begins congestion avoidance procedures when the switch, FASTbus
interface, or a frame stream enters the Mildly Congested (yellow) state. The card sets
FECN and BECN bits to communicate congestion information to user devices at
either end of a PVC (forward and backward with respect to the congested card).
25.1-8
(400)

NNP 95-2035-01-00-B

Note
The FRS, FRE or PE card sets FECN and BECN bits but does not respond in any way
to frames received with FECN or BECN bits set. The card never clears the FECN or
BECN bits of a received frame. The FRS, FRE and PE cards do not support CLLMs.
When the card sets only the FECN bit in a frame, it means that the frame was
transmitted on a frame stream in the yellow or red state, telling other network
devices to avoid this frame stream.
When the card sets only the BECN bit, it means that the frame was transmitted on
an uncongested frame stream, but the frame encountered a congested frame stream
earlier in its trip. This condition tells other network devices that this frame stream is
not congested but frames sent on it in reply are likely to encounter congestion.
When the card sets both the FECN and BECN bits, it means that the frame was
transmitted by a switch in the yellow or red state, or that the frame was transmitted
on a congested frame stream and has encountered other congested resources earlier
in its trip. This condition tells other network devices that a frame sent in reply on this
frame stream will encounter heavy congestion.
For example, in Figure 25.1-5, DLC S2-456 on FRE 2 is connected to DLC S12-789.
Buffer depletion on FRE 2 has exceeded the MCT configured for frame stream S12
and it has entered the yellow state.
When FRE 1 transmits Frame A on S2, the Frame A FECN and BECN bits are zero,
because FRE 1 is experiencing neither switch congestion nor frame stream
congestion on S2. When FRE 2 receives Frame A and transmits it on S12, FRE 2 sets
the FECN bit to 1 because Frame A is transmitted on congested resource S12.
When FRE 3 transmits Frame B on S12, the Frame B FECN and BECN bits are also
zero: like FRE 1, FRE 3 is experiencing neither switch congestion nor frame stream
congestion on S12. When FRE 2 receives Frame B and transmits it on S2, FRE 2 sets
the BECN bit to 1 because this frame has encountered congested resource S12,
although it is transmitted on uncongested resource S2.
If the FRE 2 switch enters the yellow or red state, or if both frame streams S2 and S12
enter the yellow or red state, FRE 2 sets both the FECN and BECN bits in both Frame
A and B.
When a user device receives a frame with the FECN or BECN bits set, it may initiate
some form of flow control to reduce the load on the affected switch or stream.
(400)
25.1-9


NNP 95-2035-01-00-B
Figure 25.1-5: FECN and BECN Bits

Frame B
Frame B
FECN
FECN
BECN
BECN
FRE 1
DLC 456
S2
Frame A
FECN
BECN
FRE 2
FRE 3
S12
Congestion
Frame A
FECN
BECN
DLC 789
4078
Congestion recovery
The card continues congestion avoidance and initiates congestion recovery
procedures when the switch, FASTbus or stream enters the Severely Congested
(Red) state.
When consumed buffer space is less than the ACT configured for the switch,
FASTbus, or stream, the card discards all frames with the DE bit set. Discarding
continues until the switch, FASTbus or stream leaves the Severely Congested state.
A user device sets the DE bit in all frames transmitted beyond its allowable
information transmission rate. The card sets the DE bit at the ingress point of a DLC
when rate enforcement is enabled (see chapter 25.8).
When consumed buffer space equals the ACT, the card stops buffering and discards
all newly arriving frames (regardless of the DE bit setting) until consumed buffer
space is less than the ACT. Figure 25.1-6 summarizes frame relay congestion
avoidance and recovery procedures.
25.1-10
(400)

NNP 95-2035-01-00-B

Figure 25.1-6: Congestion Avoidance and Recovery Procedures

Discard all newly
arriving frames.
Set FECN and/or
BECN bits.
BS < ACT
RED
BS = ACT
Discard all
DE frames
Set FECN and/or
BECN bits.
BS < SCT
RED
BS >= SCT
Set FECN and/or

BECN bits.
YELLOW
BS >= MCT
BS < MCT
Normal
GREEN
BS = Buffer Space consumed
2691
Link management protocol support

Link management protocols notify adjacent nodes of the addition, removal, or
failure of DLCs and monitor link integrity status (status of the entire end-to-end
PVC). The protocol notifies the user of all DLC and logical link status changes (see
chapter 34.3 in Maintenance).
You can configure each frame stream independently with a different link
management protocol to accommodate the device at the far end. The link
management protocol can be configured automatically (using the PVC management
auto discovery protocol) or manually (by selecting the protocol type which matches
the user device). If the far-end device does not support link management protocols,
you can disable all link management protocol operations on the frame stream.
The frame relay link management model is built around the UNI and the NNI, as
shown in Figure 25.1-7.
The UNI is the interface between a user device (such as the 8230 MainStreet Ethernet
Little Bridge) and a network device (such as the FRS, FRE or PE card). A user device
typically supports only a user device-specific portion of a link management protocol
(called the user mode). To communicate with the user device, a network device must
be configured with the complementary network device-specific portion of the link
management protocol (called the Network or Network Extended mode). The
complementary configuration allows a user device to request information about its
links and PVCs, and the attached network device. When the network device receives
the request, it responds with the required information. All link management
protocols support communication across the UNI.
(400)
25.1-11


NNP 95-2035-01-00-B
Figure 25.1-7: Link Management Protocol Support

8230
MainStreet bridge
User
mode
A
UNI
Network
mode
36120
MainStreet
node
FRE
1
Bidirectional
mode
Bidirectional
mode
NNI
NNI
Bidirectional
mode
User Network
mode
mode
8230
MainStreet
bridge
FRE
2
36120
MainStreet node
Bidirectional
mode
Public
frame relay
network
Network User
mode mode
8230
MainStreet
bridge
9564
The NNI is the interface between two network devices (such as two FRE cards). To
communicate with one another, both network devices must be configured with a
portion of a link management protocol (called the bidirectional mode) that
accommodates network device-to-network device communication. This protocol
allows network devices to monitor and relay link and PVC information across the
network. The Annex D and Annex A link management protocols support
communication across the NNI; the LMI protocol does not.
At another vendors network interface (or the public frame relay network interface),
the Bidirectional mode can be configured if the other end supports it.
Table 25.1-4 summarizes the link management protocol options available on the
FRS, FRE and PE cards.
25.1-12
(400)

NNP 95-2035-01-00-B

Table 25.1-4: Link Management Protocols

Communication over the UNI
Link
Management
Protocol
End-user
Device Mode
Network
Device Mode
Communication
over the NNI
Dedicated Link
Network Device
Mode
Management
Protocol DLCI (1)
LMI (Joint Spec.)
User
Network
Extended (2)
(3)
1023
ANSI T1.617
Annex D (1994)
User
Network
Bidirectional
ITU-T Q.933
Annex A (1994)
User
Network
Bidirectional
No Protocol (4)
Notes
1. When a link management protocol is selected, link management messages are transmitted and
received on this DLCI. The choice of DLCI is not user-configurable.
2. LMI Network Extended is the same as LMI Network except that asynchronous update messages are
supported.
3. The LMI protocol does not support communication over the NNI between two network devices.
4. No Protocol is selected when the frame stream terminates on a device that does not support link
management protocols.
You can configure the FRS, FRE and PE cards to accommodate both user devices and
network devices. In Figure 25.1-7, FRE 1 is configured for:
Network Mode on frame stream A to accommodate a user device

Bidirectional Mode on frame stream B to accommodate a network device
Bidirectional Mode on frame stream C to accommodate a foreign frame relay
switch in a public frame relay network that supports Bidirectional Mode
Link management protocols operate across the UNI as follows.
A user device polls an attached network device at regular intervals (defined by
the heartbeat parameter, chapter 25.6) by sending a status enquiry message with
a report type of sequence only. The network device responds with a status
message of the same report type. This exchange ensures that both user and
network devices are operating properly and the link between them is reliable.
After a set number of status enquiry messages (defined by the status rate
parameter, chapter 25.6), the user device sends a status enquiry message with a
report type of full status update. The network device responds with a status
message of the same report type that details the status of all PVCs configured on
that stream.
Link management protocols operate across the NNI as if each side of the NNI were
configured as a user and network device in parallel.
(400)
25.1-13


NNP 95-2035-01-00-B
Note
In accordance with ANSI T1.617a Annex D (1994) and ITU-T Q.933 (1994) standards,
the 36120 MainStreet system supports D-bit asynchronous transmission, notifying
the end-user device when a PVC is disconnected. However, when the
MainStreetXpress 46020 Network Manager reroutes a PVC, the D-bit asynchronous
transmission is suppressed and is not sent to the user-device.
PVC management auto discovery protocol

The auto discovery protocol is an extension of the link management services
operating over a UNI and is configured on a network device through a node
management session. It has two applications.
The auto discovery protocol automatically configures the protocol type and
timeout (T2) value of a network device to match the protocol type and timeout
value of the user device at the other end of the frame stream.
If the protocol type of the network device is set manually, the auto discovery
protocol detects any protocol type mismatch that might occur between the
network device and the user device, and displays an error status.
If the stream goes OOS for any reason, the protocol status field on the NMTI display
is updated.
Automatic protocol type and timeout detection
The auto discovery protocol detects the protocol type of the status enquiry messages
sent by the user device to the network device. When the auto discovery option is
selected, the protocol type of the user device is detected from the first correctly
received status enquiry message. The network device is automatically configured to
match the user device and the enquiry message is processed normally.
The auto discovery protocol detects the protocol type of a remote user device that
is, LMI, Annex A or Annex D and sets the protocol mode of the local interface as
Network for Annex A or Annex D, and Network Extended for LMI.
The timeout value of the user device is calculated from the interval between the first
two correctly received status messages rounded up to the nearest five seconds,
within a range of 5 to 30 seconds. For example, a measured interval of 16 seconds is
rounded up to 20 seconds.
Mismatch detection
When a specific protocol type other than auto discovery is configured on the
network device, the auto discovery protocol enables the card to detect possible
protocol type mismatches that occur between the local and remote ends. If a
mismatch causes the stream to go OOS, an OOS alarm is raised, indicating the type
of protocol detected on the user device. In this case, neither the protocol type nor the
timeout value are configured automatically.
25.1-14
(400)

NNP 95-2035-01-00-B
25.1.2

Configuration Overview
You configure the FRS, FRE and PE cards from two node management interfaces.
During a node management session with the Control card:

configure the card slot
create frame streams or encapsulation circuits
During a node management session with the FRS, FRE or PE card, configure:
FASTbus parameters (FRE and PE cards)
switch thresholds
frame stream or encapsulation circuit parameters
DLCs and class-of-service parameters
Table 25.1-5 shows where you can find additional information relating to
configurable frame relay parameters.
Table 25.1-5: Additional Configurable Frame Relay Parameters
Parameter
Location
CPSS
chapter 17.6
Backplane CPSS communication
chapter 17.7
SRIM
section 25.9.1
Table 25.1-6 lists the configurable frame relay parameters according to the card type.
Note
The formats of the identifiers in the corresponding procedures are explained in
Table 16.4-1 in chapter 16.4.
Table 25.1-6: FRS, FRE and PE Card Configuration Parameters and Options
Card type
Parameter
Options
Card
FRS, FRE and PE
Card slot
FRS
FRE
PE
FRS
Card application
SRIM
no module*
FRS, FRE and PE
Backplane communications
dedicated
shared*
FRS, FRE and PE
Fault handling mode
enhanced
standard*
(400)
25.1-15

Card type

NNP 95-2035-01-00-B
Parameter
Options
FRS, FRE and PE
Major fault card dead threshold
1 to 30000 (5000*)
unlimited
FRS, FRE and PE
Major fault count reset threshold
1 to 30000 (500*)
unlimited
FRS, FRE and PE
Serial port baud rate
300 b/s
600 b/s
1200 b/s
2400 b/s
4800 b/s
9600 b/s*
19200 b/s
FRS, FRE and PE
Serial port type
CPSS
VT100*
FRS
CPSS Router Version
Router version 1*
Host router
FRS, FRE and PE
Serial port CPSS cost
Normal*
Bias against
Bias toward
FRE and PE
FASTbus CPSS
CPSS1
CPSS2
FRE and PE
Congestion filtering
enable*
disable
FRE and PE
Congestion clear time
1 to 1440 min (* = 15)
FRE and PE
Congestion raise time
0 to 240 s (2)
FRE and PE
Report type
Alarm*
Network management events
FRS, FRE and PE
SCT
0 to 100% (* = 80)
FRS, FRE and PE
MCT
0 to 100% (* = 50)
FRE and PE
enable*
disable
FRE and PE
1 to 1440 min (* = 15)
FRE and PE
0 to 240 s (2)
FRE and PE
Report type
Alarm*
FRE and PE
36120 identifier
1 to 32767 (* = 0)
FRE and PE
Station identifier
1 to 64 (* = 0)
FRE and PE
Cable name
1 to 15 alphanumeric characters, no
spaces
FRE and PE
ACT
10 to 1000 kbytes (* =100)
FRE and PE
SCT
0 to 100% (* = 80)
Switch (1)
FASTbus Interface
25.1-16
(400)

NNP 95-2035-01-00-B

Card type
FRE and PE
Parameter
Options
MCT
0 to 100% (* = 50)
Circuit application
Stream*
Circuit
FRS, FRE and PE
Rate adaption (4)

Encapsulation (3)
FRS, FRE and PE
Transport bandwidth
1 to 8 (8 kb/s to 64 kb/s) (* = 8)
FRS, FRE and PE
Interface speed
8 to 1920 kb/s (* = 64) for FRS cards

8 to 1984 kb/s (* = 64) for FRE and PE
cards
FRS, FRE and PE
Frame stream name
0 to 8 alphanumeric characters, no
spaces
FRE and PE
enable*
disable
FRE and PE
1 to 1440 min (* = 15)
FRE and PE
0 to 240 s (2)
FRE and PE
Report type
Alarm*
FRS, FRE and PE
Maximum frame size
16 to 4472 octets (* = 1600)
FRS, FRE and PE
ACT
1 to 64 kbytes (* = 4) for FRS cards

1 to 1500 kbytes (* = 10) for FRE and
PE cards
FRS, FRE and PE
SCT
0 to 100% (* = 80)
FRS, FRE and PE
MCT
0 to 100% (* = 50)
FRE and PE
Flags between frames
1* to 10
FRS, FRE and PE
Protocol type
LMI User, Network, Network Extended

ANSI T1.617 Annex D User, Network,
Bidirectional
ITU-T Q.933 Annex A User, Network,
Bidirectional (* = Annex A Network)
No Protocol
Frame Stream
Auto discovery (Network mode) (5)

FRS, FRE and PE
Heartbeat polling interval
5 to 30 s (* =10)
FRS, FRE and PE
Status message rate
1 to 255 (* = 6)
FRS, FRE and PE
Status enquiry message timeout
5 to 30 s (* = 15) (6)
Encapsulation Circuit
FRS
Encapsulation type
LAPB RFC 1490

LAPB Annex G*
Transparent HDLC
FRS
Encapsulated protocol maximum

frame size
16 to 4472 octets (* = 512 for LAPB,

1600 for HDLC)
FRS
ACT
1 to 64 kbytes (* = 4)
FRS
SCT
0 to 100% (* = 80)
(400)
25.1-17

Card type
FRS

NNP 95-2035-01-00-B
Parameter
MCT
Options
0 to 100% (* = 50)
DLC Class-of-service
FRS, FRE and PE
Class-of-service rate enforcement
enable
disable
FRS, FRE and PE
CIR
0* to 1920 kb/s for FRS cards

0* to 1984 kb/s for FRE and PE cards
FRS, FRE and PE
Bc
0* to 1920 kb for FRS cards

0* to 1984 kb for FRE and PE cards
FRS, FRE and PE
Be
0* to 1920 kb for FRS cards

0* to 1984 kb for FRE and PE cards
Notes
1. The card CPU takes the same congestion clear time and congestion raise time values as those
configured for the switch. Congestion filtering is always enabled on the CPU, regardless of the
configuration for the switch.
2. When congestion filtering is enabled, the default is 5 seconds. When congestion filtering is disabled,
the default is 0 seconds.
3. This option applies only to FRS cards equipped with a SRIM.
4. This option applies only to FRS cards.
5. The auto discovery option sets the auto discovery protocol through the protocol type parameter, even
though the auto discovery protocol is not a link management protocol. See Protocol type in
chapter 25.6.
6. This option is not configurable if the auto discovery protocol is used.
25.1-18
(400)

NNP 95-2035-01-00-B
25.2
25.2 FRS, FRE and PE Card Slots

FRS, FRE and PE Card Slots

This chapter explains how to configure FRS, FRE and PE card slots.
25.2.1
Understanding FRS, FRE and PE Card Slots

You must configure card slots for the FRS, FRE and PE cards before you can
configure or connect circuits. Configuring a slot type means programming a card
slot to accept a specific card type with specific card parameters. When you configure
a slot, the system configures the circuits for that slot with default settings.
In addition to configuring the card slot for the FRS, FRE or PE card, you can also
configure the backplane communications link between the card and the Control
card. For information on backplane card communications, see chapter 17.7.
25.2.2
Configuring FRS, FRE and PE Slots

To configure a card slot for an FRS, FRE or PE card, select PACKET and the card
type. If the FRS card has a SRIM, select the SRIM card slot option.
(400)
25.2-1
25.2 FRS, FRE and PE Card Slots


NNP 95-2035-01-00-B
To configure FRS, FRE and PE slots

CONFIG SLOT <sn>
TYPE
OPTIONS
SRIM/NO_MODULE
AS_PRESENT
PACKET
FRS
FRE
PE
SK000677
Note
Use the AS_PRESENT softkey if the card is already installed in the slot.
Select the CONFIG_ALL softkey to configure all slots programmed as EMPTY to the
default configurations of the cards installed in the shelf.
25.2-2
(400)

NNP 95-2035-01-00-B
25.3
25.3 Frame Relay Switch Congestion Parameters

Frame Relay Switch Congestion

Parameters
This chapter explains how to configure switch congestion parameters.
25.3.1
Understanding Frame Relay Switch Congestion

The FRS, FRE and PE card switch is a fully non-blocking, cross-connect matrix that
connects one DLC to another, according to user-configured DLC cross-connections
(see chapter 25.7). All DLCs are bidirectional (full duplex).
You can configure the following for a frame relay switch:
switch congestion thresholds

switch congestion notification parameters (FRE and PE only)
The switch congestion notification parameters include filtering, congestion clear
time, congestion raise time and report type.
25.3.2
Configuring Frame Relay Switch Congestion Parameters

By selecting the CONFIG SWITCH softkeys, you can configure the parameters for
frame relay switch congestion. Figure 25.3-1 shows the display for the switch
congestion thresholds. Figure 25.3-2 shows the display for the switch congestion
notification parameters, which can be set on the FRE and PE cards. Table 25.3-1
summarizes the fields and parameters on these displays.
(400)
25.3-1


NNP 95-2035-01-00-B
Figure 25.3-1: Switch Congestion Thresholds Display

FRE
Stations:nn
P412-H1-00
Toronto:A
Alarms:1
11-May-1997
SWITCH THRESHOLDS
Absolute Congestion Threshold (ACT)
Severe Congestion Threshold (SCT)
Mild Congestion Threshold (MCT)
:1500 Kbytes
:80%
:50%
Switch Congestion Status

CPU Congestion Status
:GREEN
:GREEN
8:35a
CONFIG SWITCH THRESHOLDS

F1F6-
F2-SCT
F7-
F3-MCT
F8-CANCEL
F4F9-QUIT
F5F10-
Figure 25.3-2: Switch Congestion Notification Parameters Display

FRE
Stations:nn
P412-H1-00
Toronto:A
Alarms:1
Filtering Algorithm:
ENABLED
Clear Time:
15 mins
Report Type:
ALARMS
Raise Time:
5 secs
11-May-1997
8:35a
CONFIG SWITCH CONGESTION
1-FILTERING
6-
25.3-2
2-CLEAR_TIME
7-
3-RPT_TYPE
8-CANCEL
(400)
4-RAISE_TIME
5-QUIT
50-

NNP 95-2035-01-00-B

Table 25.3-1: Frame Switch Configuration Fields

Fields
Description
ACT
The ACT is the total system buffer space available for switching
frames. It is not user-configurable.
SCT
SCT configured as a percentage of ACT (where SCT MCT).
MCT
MCT configured as a percentage of ACT (where MCT SCT).
Switch Congestion Status (1)
The current congestion state of the switch or CPU.

GREEN: Congestion is the MCT threshold configured.
YELLOW: Congestion is > the MCT threshold but the SCT
threshold configured.
RED: Congestion is > the SCT configured.
CPU Congestion Status
Filtering Algorithm
The congestion filter is enabled or disabled.
Clear Time (2)
A time interval in the range of 1 to 1440 min.
Report Type
The format in which congestion information is reported. Report Type

can be set to report alarms or network management events.
Raise Time (2)
A time interval in the range of 0 to 240 s.
Notes
1. When filtering is enabled, the indication of a Congestion Status change is temporarily delayed. You
cannot disable filtering on the CPU.
2. The card CPU takes the same congestion clear time and congestion raise time values as those
configured for the switch. Congestion filtering is always enabled on the CPU, regardless of the
configuration for the switch.
Frame switch congestion thresholds

You can configure congestion thresholds for the FRS, FRE or PE card switch. The
ACT for the FRE and PE card switch is fixed at 1500 kbytes and for the FRS card at
64 kbytes. These values are the total amount of buffer space available for buffering
frames as they are switched from one DLC to another.
SCT
Enter the SCT as a percentage of ACT (0 to 100%). The default is 80%.
MCT
Enter the MCT as a percentage of ACT (0 to 100%). The MCT must be less than or
equal to SCT. The default is 50%.
Filtering
A filter is available to debounce the transition through congestion states. Filtering is
always enabled on the FRS card, and can be disabled on FRE and PE cards.
(400)
25.3-3


NNP 95-2035-01-00-B
Options
Configure filtering as one of the following.
Enable:
When filtering is enabled, a smooth contiguous transition occurs through the

congestion states. When the SCT is exceeded, the filter delays the raising of a
Switch or CPU Congested alarm by filtering out the temporary spikes in
congestion, giving a long-term congestion average.
Disable:
When filtering is disabled, the transition consists of sharp spikes, allowing the
alarms to be raised more frequently and giving short-term statistics on buffer
space utilization.
Default
Enable
Clear time
The clear time is the length of time that a previously congested switch remains below
the Red state before a Switch or CPU Congestion Cleared alarm is raised. For
example, if you configure the clear time to be 20 min, the clearing alarm is raised
20 min after the switch has left the Red state. The clear time can be configured on
FRE and PE cards, and is fixed at 10 s for the FRS card.
Range
1 to 1440 min (1 min to 24 h)
Default
15 min
Raise time
The raise time is the length of time that the switch remains in the Red state before a
Switch or CPU Congested alarm is raised. For example, if you configure the raise
time to be 10 s, an alarm is raised only after the switch has remained in the Red state
for 10 s. The raise time can be configured on FRE and PE cards, and is fixed at 5 s for
the FRS card.
Range
0 to 240 seconds
Default
When filtering is disabled, the default is 0 s. When filtering is enabled, the default is
5 seconds.
25.3-4
(400)

NNP 95-2035-01-00-B

Report type
The report type specifies whether the node reports congestion information as alarms
or network management events (which include alarm reports).
Options
Configure the report type as one of the following.
Alarms
Default
Alarms
To configure switch congestion parameters

CONFIG SWITCH
THRESHOLDS
MORE
CONGESTION
SCT
MCT
<sct>
<mct>
FILTERING
CLEAR_TIME
RAISE_TIME
ENABLE*/DISABLE
<ct>
<rt>
RPT_TYPE
ALARMS*
MGT_EVENTS
SK000932
where
sct is 0 to 100 (80*)
mct is 0 to 100 (50*)
ct is 1 to 1440 min (15*)
rt is 0 to 240 s (5*)
(400)
25.3-5

NNP 95-2035-01-00-B
25.4
25.4 FASTbus Configuration

FASTbus Configuration
This chapter introduces the FASTbus and explains how to configure the FASTbus.
25.4.1
Understanding FASTbus Configuration

This section introduces the FASTbus and explains how to view FASTbus status
fields.
The FASTbus provides each FRE and PE card with a 100 Mb/s frame stream to every
other FRE and PE card on a 36120 MainStreet system.
FASTbus topology
The FASTbus uses a dual counter-rotating ring topology based on a token-passing
access method, as shown in Figure 25.4-1. Each FASTbus interface is made of one
MAC layer and two PHY layers, port A and port B. The MAC layer is responsible for
ring operation, and the transmission and reception of frames on the FASTbus. The
dual physical layers provide an FIP with a high degree of fault tolerance by allowing
FRE and PE cards to bypass (or wrap around) the failure of an FRE or PE card or
card-to-FIP cable.
Under normal operating conditions, port A receives and port B transmits on the
primary ring (this state is referred to as THRU_A). The secondary ring remains idle
in a stand-by mode.
To communicate with each other over the FASTbus, all FRE or PE cards must belong
to the same 36120 MainStreet system. In the FASTbus configuration shown in
Figure 25.4-1, the FRE cards can be installed in the same 36120 MainStreet shelf or in
different shelves, but all the FRE cards belong to the same 36120 MainStreet system.
Figure 25.4-1: FASTbus Topology
FRE card 4
Normal
Normal
Normal
A
MAC
PHY
MAC
PHY
MAC
PHY
A
PHY
MAC
PHY
PHY
FRE card 3
PHY
FRE card 2
PHY
FRE card 1
Normal
Secondary ring
Primary ring
4074
(400)
25.4-1


NNP 95-2035-01-00-B
FASTbus fault tolerance

If a cascade or bypass module or cascade cable is removed, or if an FRE or PE card
fails, the cards adjacent to the failure perform a wrapping function to bypass the
fault and maintain the integrity of the ring. All other FRE or PE cards are unaffected.
In Figure 25.4-2, FRE card 3 has failed. FRE card 2 detects the failure on its A port
and wraps the primary ring onto the stand-by secondary ring using its B port (this
state is referred to as WRAP_B). FRE card 4 detects the failure on its B port and
wraps the primary ring onto the stand-by secondary ring using its A port (this state
is referred to as WRAP_A).
FRE card 3
FRE card 4
PHY
PHY
PHY
Normal
WRAP-B
MAC
Card or cable
failure
MAC
PHY
MAC
PHY
MAC
PHY
FRE card 2
PHY
FRE card 1
PHY
Figure 25.4-2: FASTbus Fault Recovery
WRAP-A
4075
If more than one FRE or PE card or cable fails, the FASTbus attempts to heal itself
into multiple isolated rings. For example, if FRE card 4 were to fail, FRE card 1 and
2 (and any FRE or PE cards between them) would continue to communicate.
However, these cards would be isolated from any other FRE or PE cards on the ring
(for example, between FRE card 3 and 4).
Each FRE and PE card maintains a logical map of the FASTbus ring. FASTbus
protocols ensure that the maps are kept up to date under all conditions. The map is
updated within 4 seconds of the addition of a new card to the FASTbus and within
20 seconds of the removal of a card. Wrapping occurs almost instantaneously.
Note
If an FRE or PE card is disconnected from the FASTbus by a cable failure, only
communication between this card and all other FRE and PE cards on the FASTbus is
interrupted. The card continues to switch all local DLCs (see also chapter 25.7).
25.4-2
(400)

NNP 95-2035-01-00-B

Viewing FASTbus station status

When you select the SHOW_STNS softkey, the screen displays the FASTbus station
status display with all FRE and PE cards, or stations, connected to the FASTbus for
the 36120 MainStreet system. Any DLC on any of these cards can be connected to any
other DLC through a FASTbus circuit. Figure 25.4-3 shows a typical FASTbus station
status display. Table 25.4-1 summarizes the fields shown on this display.
If 14 or more stations are configured, the NEXT and PREVIOUS softkeys move
forward and backward through the list, one screen at a time.
Note
You cannot reach any stations from an FRE or PE card until you configure the 36120
ID and station ID parameters for the card.
Figure 25.4-3: FASTbus Station Status Display

FRE
Stations:nn
Station
------1
2
3
4
5
6
7
8
9
10
11
12
CONFIG FASTBUS
F1-PREVIOUS
F6-
P412-H1-00
Connections
----------129
12
52
52
12
11
54
11
62
52
52
Toronto:A
Alarms:1
Node Name:Slot
--------------Toronto A4
Toronto A2
Toronto A8
Calgary A2
Calgary A4
Calgary A6
Calgary A8
Charlo :A1
Bronx :A5
Queens :A3
LA
:A2
LA
:A4
11-May-1997
8:35a
Status
-----Reachable
Self
Reachable
Reachable
Reachable
Reachable
Reachable
Reachable
Reachable
Reachable
Non-reachable
Non-reachable
SHOW_STNS
F2-NEXT
F7-
F4F8-CANCEL
(400)
F4F9-QUIT
F5F10-
25.4-3


NNP 95-2035-01-00-B
Table 25.4-1: FASTbus Station Status Fields

Field
25.4.2
Description
Station
The identifier of the FASTbus circuit used to access the FRE or PE card with
the corresponding station identifier.
Connections
The number of FASTbus DLCs configured on this FASTbus circuit.
Node Name:Slot
If a remote FRE or PE card with this station identifier is installed in a node and
connected to the FASTbus, the name of the remote FRE or PE card node
(36120 MainStreet shelf in which it is installed) and the slot occupied by the
remote card appear in this field. If no FRE or PE card with this station identifier
is installed and connected to the FASTbus, Unknown appears in this field.
Status
The current state of the remote station.

Reachable: The remote station is connected to the FASTbus and can be
accessed from this FRE or PE card.
Non-reachable: The remote station is not connected to the FASTbus and
cannot be accessed from this FRE or PE card.
Self: Identifies the station that corresponds to the FRE or PE card you are
logged onto.
Configuring the FASTbus

To configure the FASTbus, you must configure the:
cable name
36120 identifier
station identifier
FASTbus congestion thresholds
FASTbus congestion notification parameters
During this process, you can check FASTbus configuration and parameters using the
FASTbus status display and the FASTbus station status display.
The switch congestion notification parameters include filtering, congestion clear
time, congestion raise time and report type.
Viewing FASTbus parameters

When you select the CONFIG FASTBUS softkeys, the screen displays the
FASTbus status display. The screen shows the current values of the configurable
FASTbus interface parameters for the FRE or PE card you are logged onto. Figure
25.4-4 shows the FASTbus parameters display. Figure 25.4-5 shows the FASTbus
congestion notification parameters display. Table 25.4-2 lists the fields on these
displays.
25.4-4
(400)

NNP 95-2035-01-00-B

Figure 25.4-4: FASTbus Parameters Display

FRE
Stations:nn
P412-H1-00
Toronto:A
Cable Name
36120 ID
Station ID
Interface Address
Status
Congestion Status
Interconnection
Alarms:1
11-May-1997
8:35a
:FH3-Port8
:542
:27
:00-80-21-01-02-03
:In Service
:GREEN
:100 Kbytes
:80%
:50%
:FASThub
CONFIG FASTBUS
F1-SHOW_STNS
F6-STATION_ID
F2-THRESHOLDS
F7-MORE
F4-CABLE_NAME
F8-CANCEL
F4-SHOW_CONS
F9-QUIT
F5-36120_ID
F10-
Figure 25.4-5: FASTbus Congestion Parameters Display

FRE
Stations:nn
P412-H1-00
Toronto:A
Alarms:1
ENABLED
Clear Time:
15 mins
Report Type:
ALARMS
Raise Time:
5 secs
11-May-1997
8:35a
1-FILTERING
6-
2-CLEAR_TIME
7-
3-RPT_TYPE
8-CANCEL
(400)
4-RAISE_TIME
9-QUIT
50-
25.4-5


NNP 95-2035-01-00-B
Table 25.4-2: FASTbus Parameters

Field
Description
Cable Name
A name of up to 15 characters describing the wiring arrangement (for

example, the FIP number and FIP port number used to connect this FRE or
PE card to the FASTbus).
36120 ID
A value between 1 and 32767 uniquely identifying this 36120 MainStreet

system in the network. All FRE or PE cards connected to the FASTbus of one
36120 MainStreet system have the same 36120 ID.
Station ID
A value between 1 and 64 uniquely identifying this FRE or PE card on the

FASTbus. Each FRE or PE card connected to the FASTbus of a 36120
MainStreet system has a different station ID.
Interface Address
The MAC layer address assigned to the FRE or PE card at the time of
manufacture. Every card has a unique MAC address consisting of a 3-byte
manufacturer designator (mm-mm-mm) followed by a 3-byte MAC address
(aa-aa-aa) displayed in 12-digit hexadecimal format, hyphenated by octet
(1 octet = 8 bits).
Status
The current operating state of this FRE or PE card FASTbus interface.

In Service: The normal operating state. Port A connects the FRE or PE card
to the FASTbus and Port B is in stand-by.
In Service Trouble: Either Port A or Port B has failed. In this state, there is no
backup in case of a further FASTbus failure.
Out of Service: Both Port A and Port B have failed or the user has applied a
FASTbus busy out (see Maintenance). The FRE or PE card continues
switching all local DLCs, but drops all frames transmitted on FASTbus DLCs
to or from this FRE or PE card.
Congestion Status (1)
The current congestion state of the FASTbus.

YELLOW: Congestion is > the MCT threshold but the SCT threshold
configured.
RED: Congestion is > the SCT configured.
ACT
The total amount of buffer memory configured for use by the FASTbus.
SCT
A utilization percentage of total buffer space available (ACT).
MCT
A utilization percentage of total buffer space available (ACT).
Filtering Algorithm
Clear Time
Report Type
The format in which congestion information is reported. Report Type can be

set to report alarms or network management events.
Raise Time
Notes
1. When filtering is enabled, the indication of a Congestion Status change is temporarily delayed.
Cable name
You can configure a name of up to 15 alphanumeric characters (no spaces) to identify
the cable connecting the FRE or PE card to its FIP. For example, a cable name might
be made of the FIP number and FIP port number, as in FB3-Port8 (port 8 on FIP 3).
To delete a cable name, select CABLE_NAME and press .
25.4-6
(400)

NNP 95-2035-01-00-B

36120 ID
You must assign a unique 36120 ID in the range 0 to 32767 to each 36120 MainStreet
shelf in the network. You must configure all the FRE and PE cards connected to the
FASTbus of a given 36120 MainStreet system with the same 36120 ID number.
The 36120 ID identifies cabling faults that allow an FRE or PE card from one 36120
MainStreet shelf to be connected to the FASTbus of another 36120 MainStreet shelf.
The FASTbus supports up to 64 FRE and PE cards belonging to the same 36120
MainStreet system.
If you configure an FRE or PE card with the wrong 36120 ID or connect it to the
wrong FASTbus, the FASTbus station status display shows only the offending card.
No other FASTbus stations are visible until you configure the offending card with
the correct 36120 ID.
Caution
If the 36120 ID is changed, the system disconnects all FASTbus DLCs and FASTbus
CPSS connections.
Station ID
The station ID distinguishes one FRE or PE card from another on the FASTbus and
associates each card with a FASTbus circuit. You must assign a unique station ID in
the range 0 to 64 to each FRE or PE card in a 36120 MainStreet system. After an FRE
or PE card is configured with station ID nn, it can be reached by making DLC
cross-connections to FASTbus circuit Fnn (see chapter 25.7).
If you configure an FRE or PE card with a station ID already used by another FRE or
PE card, the FASTbus station status display shows only the incorrect card. No other
FASTbus stations are visible until you configure the incorrect card with a unique
station ID.
Caution
If the station ID is changed, the system disconnects all FASTbus DLCs and FASTbus
CPSS connections.
FASTbus congestion thresholds

You can configure congestion thresholds for the FASTbus interface of an FRE or PE
card.
ACT
The total amount of buffer memory configured for use by the FASTbus in the range
10 to 1000 kbytes. Configure the ACT for the FASTbus between 10 and 1000
kilobytes. This is the amount of buffer space available as transmit queues to buffer
frames transmitted on the FASTbus.
(400)
25.4-7


NNP 95-2035-01-00-B
SCT
A utilization percentage of total buffer space available (ACT). The FASTbus is
considered severely congested when buffer utilization is > SCT. Enter the SCT as a
percentage of ACT (0 to 100%).
MCT
A utilization percentage of total buffer space available (ACT). The FASTbus is
considered mildly congested when buffer utilization is > MCT and SCT. Enter the
MCT as a percentage of ACT (0 to 100%). MCT must be less than or equal to SCT.
Filtering
A filter is available to debounce the transition through congestion states. Filtering
can be enabled or disabled.
Options
Enable:

congestion alarm by filtering out the temporary spikes in congestion, giving a
long-term congestion average.
Disable:
When filtering is disabled, the transition consists of sharp spikes, allowing
space utilization.
Default
Enable
Clear time
The clear time is the length of time that a previously congested FASTbus remains
below the Red state before a FASTBUS Congestion Cleared alarm is raised. For
example, if you configure the clear time to be 20 min, the clearing alarm is raised 20
min after the FASTbus has left the Red state.
Range
1 to 1440 min (1 min to 24 h)
Default
15 min
25.4-8
(400)

NNP 95-2035-01-00-B

Raise time
The raise time is the length of time that the FASTbus remains in the Red state before
a FASTbus Congested alarm is raised. For example, if you configure the raise time
to be 10 seconds, the alarm is raised only after the FASTbus has remained in the Red
state for 10 seconds.
Range
0 to 240 seconds
Default
When filtering is disabled, the default is 0 s. When filtering is enabled, the default is
5 seconds.
Report type
Options
Alarms
Default
Alarms
(400)
25.4-9


NNP 95-2035-01-00-B
To configure the FASTbus parameters

CONFIG FASTBUS
SHOW_STNS
THRESHOLDS
CABLE_NAME
<name>
NEXT
36120_ID
<36120_id>
STATION_ID
MORE
<station_id>
CONGESTION
PREVIOUS
FILTERING
ACT
SCT
CLEAR_TIME
RAISE_TIME
<ct>
<rt>
MCT
<act> <sct> <mct>
ENABLE*/
DISABLE
RPT_TYPE
ALARMS*
MGT_EVENTS
SK000933
where
36120_id is 0 to 32767
station_id is 0 to 64
name is a 15-character alphanumeric identifier
act is 10 to 1000 kbytes in 1 kbyte increments (100*)
sct is 0 to 100 (80*)
mct is 0 to 100 (50*)
ct is 1 to 1440 min (15*)
rt is 0 to 240 s (5*)
25.4-10
(400)

NNP 95-2035-01-00-B
25.5
25.5 Creating Frame Streams

Creating Frame Streams

This chapter describes frame streams and explains how to create and connect a
frame stream.
25.5.1
Understanding Frame Stream Creation

You can create two types of frame streams.
A local frame stream connects an FRS, FRE or PE card circuit and a primary rate
or data circuit to provide connections to the network.

A card-to-card frame stream connects any two FRS, FRE or PE cards in the same
node, or any two FRE or PE cards in the same 36120 MainStreet system, and
provides direct connections between the cards.
Local frame stream

You create a local frame stream by configuring an FRS, FRE or PE card circuit and
connecting it to a primary rate or data circuit. You identify the frame stream by the
FRS, FRE or PE card circuit identifier (for example, circuit 23 creates frame stream
S23). For primary rate links, you can configure a frame stream on any part of the link
to allow both frame relay and circuit-switched service on the same link.
Card-to-card frame stream

You can create a card-to-card frame stream by configuring and connecting a circuit
on one FRS, FRE or PE card to a similarly configured circuit on another FRS, FRE or
PE card in the same node.
For FRE and PE cards in a 36120 MainStreet system, the FASTbus automatically
creates a card-to-card frame stream between every card. Each FRE and PE card has
63 FASTbus circuits, one for each FRE or PE card in a 36120 MainStreet system (the
FASTbus circuit that corresponds to the station identifier of an FRE card is not valid).
FASTbus circuits provide FRE and PE cards with a 100 Mb/s frame stream to every
other FRE or PE card in a 36120 MainStreet system. The 100 Mb/s bandwidth is
available regardless of the number and size of local frame streams configured (see
chapter 25.4).
Table 25.5-1 lists the bandwidth and frame stream options available on the FRS, FRE
and PE cards.
(400)
25.5-1


NNP 95-2035-01-00-B
Table 25.5-1: FRS, FRE and PE Card Bandwidth and Circuits

Bandwidth / Card
Type
Total
Bandwidth
Available
Circuits
(Frame Streams)
Maximum
Bandwidth
per Frame
Stream
Single Bandwidth
FRE and PE
1984 kb/s
1 to 31 (S1 to S31)
1984 kb/s
Single Bandwidth
FRS
1984 kb/s
1 to 31 (S1 to S31)
1920 kb/s
3968 kb/s (2)
1 to 62 (S1 to S62)
1984 kb/s
Double Bandwidth (1)

FRE and PE
Double Bandwidth
FRS
Notes
1. Double bandwidth is always available in UCS 7 and 8. It is available in all UCSs in a 3645 MainStreet
system or Switching shelf controlled 36120 MainStreet system. It is available in all UCSs when an
Expander card (16+) is installed in a 3600 MainStreet system or locally controlled 36120 MainStreet
system.
2. Total bandwidth available is based on two bundles of 1984 kb/s each.
Creating a frame stream involves two main activities:
configuring an FRS, FRE or PE card circuit for frame relay

connecting the configured circuit to a primary rate or data circuit, or to a similarly
configured circuit on another FRS, FRE or PE card in the same node
25.5.2
Configuring FRS, FRE and PE Circuits as Streams

You configure FRS, FRE and PE card circuits during a node management session
with the Control card. To configure a circuit, you must:
configure an FRS, FRE or PE card circuit for the frame stream application
configure the transport bandwidth for the circuit
configure the interface speed for the circuit
Note
You can configure FRS, FRE and PE card circuits <sn-cc> and frame streams <Scc>
before the circuits are connected to primary rate or data interface circuits.
The following subsections describe the configurable parameters.
25.5-2
(400)

NNP 95-2035-01-00-B

Application
The circuit application type determines how the circuit is used. To use an FRS, FRE
or PE card circuit as a frame stream, configure the application as STREAM.
To configure an FRS card circuit for frame relay encapsulation, see section 25.10.2.
To configure an FRE or PE card circuit as a direct circuit, see section 27.13.2.
Caution
When you change the FRS, FRE or PE card circuit application from STREAM to
another application, the system deletes the frame stream associated with the circuit
and loses all frame stream configuration for that frame stream (including DLCs).
Transport bandwidth
The transport bandwidth establishes the maximum allowable data rate for the frame
stream, or its access rate. You set the transport bandwidth by entering the number
of elements (1 through 8) available to the frame stream. The transport bandwidth
equals the number of elements times 8 kb/s, so you can establish an 8 kb/s frame
stream by entering 1, a 16 kb/s frame stream by entering 2 and so on. The default is
8, which specifies a 64 kb/s frame stream.
The transport bandwidth of the FRS, FRE or PE card circuit must match that of the
circuit to which it connects.
Interface speed
You can configure each FRS, FRE or PE card circuit with an interface speed between
8 and 1984 kb/s (in 8 kb/s increments), provided that the sum of the interface speeds
of all configured FRS, FRE or PE card circuits does not exceed the total bandwidth
available (see Table 25.5-1).
Note
Double bandwidth configurations (available only on the FRE and PE cards) provide
access to 62 DS0s (3968 kb/s of bandwidth). The 62 DS0s are divided into two
bundles of 31 DS0s, each providing 1984 kb/s of bandwidth.
When configuring super-rate connections, you cannot configure circuits across
bundles. The bundles are independent and cannot be combined to provide a
super-rate connection. For example, if you want to configure three super-rate
connections of 1280, 1600 and 1088 kb/s (which, combined, is equivalent to 62 DS0s),
the first connection requires 20 DS0s on the Data stream, leaving 11 DS0s. The
second connection requires 25 DS0s on the Control B stream, leaving 6 DS0s. The
third connection, which requires 17 DS0s, cannot be configured because the
remaining DS0s span both bundles.
(400)
25.5-3


NNP 95-2035-01-00-B
If you are connecting the FRS, FRE or PE card circuit to a primary rate circuit, you
must calculate the interface speed using the following formula:
m n 8 kb/s
where
m represents the number of channels needed to carry the interface speed you want
(m = 1 to 31 for both single and double bandwidth)
n 8 kb/s represents the allowable transport bandwidth in any channel (n = 1 to 8)
If you are connecting the FRS, FRE or PE card circuit to a data circuit, you can enter
the interface speed directly as the amount of bandwidth available to the link (in
increments of 8 kb/s).
To configure an FRS, FRE or PE circuit as a stream

Configure the circuit from the Control card NMTI.
APPLI
TRANSP_BW
I/F_SPEED
STREAM*
<bw>
<speed>
SK000171
where
speed is 8 to 1920 for FRS cards and 8 to 1984 for FRE and PE cards
Note
See 25.9.3 to configure circuits for rate adaption and section 25.10.2 to configure
circuits for encapsulation.
25.5.3
Connecting Frame Streams

When you connect an FRS, FRE or PE card circuit (configured for the STREAM
application) to a primary rate or data circuit, the bandwidth is associated with a
frame stream identified by the FRS, FRE or PE card circuit number. For example, if
FRE card circuit 23 is connected, the bandwidth is associated with frame stream S23.
25.5-4
(400)

NNP 95-2035-01-00-B

When you disconnect an FRS, FRE or PE card circuit, the frame stream associated
with it is disassociated from the bandwidth. After disconnection, the system retains
all existing configuration information unchanged for both the circuit and the
associated frame stream. You can reconfigure or reconnect the FRS, FRE or PE card
circuit and frame stream again (to the same or a different primary rate or data circuit)
to recreate the frame stream with all its configuration intact.
You can connect an FRS, FRE or PE card circuit to any primary rate or data circuit
(for example, T1, E1, X.21, V.35, RS-232, RS-422) including super-rate circuits,
subrate circuits and transparent subrate connections to SRMs and SRSs.
You can connect an FRS, FRE or PE card circuit to another FRS, FRE or PE card circuit
in the same node, as long as the two circuits have the same configuration. After they
are connected, you can connect any DLC on any frame stream of one of the cards to
any DLC on the other card.
Note
Ensure that your primary rate service provider will guarantee temporal order before
cross-connecting an FRS, FRE or PE card circuit to a primary rate super-rate circuit.
Connections on an FRE or PE card should be made in descending bandwidth order.
For more information on subrate and super-rate circuits, see chapters 23.9 and 20.15.
To configure an FRS card for subrate switching, see chapter 25.9.
The FRS, FRE and PE cards support protection switching. See chapter 18.2.
To connect a frame stream to a primary rate or data circuit

TO_CIRCUIT
DISCONNECT
<sn-cc>
SK000172
where
the first sn-cc is a primary rate or data circuit
the second sn-cc is an FRS, FRE or PE card circuit
(400)
25.5-5


NNP 95-2035-01-00-B
To connect two frame stream circuits in the same node

TO_CIRCUIT
DISCONNECT
<sn-cc>
SK000172
where
the first sn-cc is a circuit on one FRS, FRE or PE card
the second sn-cc is a circuit on another FRS, FRE or PE card in the same node
25.5-6
(400)

NNP 95-2035-01-00-B
25.6
25.6 Frame Stream Configuration

Frame Stream Configuration

This chapter explains how to configure frame stream parameters on the FRS, FRE
and PE cards.
25.6.1
Understanding Frame Stream Configuration

To configure frame streams, you must configure the following parameters from the
FRS, FRE or PE cards:
frame size
flags between frames (FRE and PE only)
the auto discovery protocol option (FRE and PE only) or the specific link
management protocol type

heartbeat polling interval
status message rate
status enquiry message timeout
frame stream congestion thresholds
frame stream congestion notification parameters (FRE and PE only)
During the configuration process, you can check frame stream configuration and
parameters using the frame stream status display and the frame stream
configuration display.
The frame stream congestion notification parameters include filtering, congestion
clear time, congestion raise time and report type.
For a description of the frame stream circuit parameters that are configured from the
Control card NMTI, see chapter 25.5.
Note
You can configure FRS, FRE and PE card circuits (sn-cc) and frame streams (Scc)
before the circuits are connected to primary rate or data interface circuits.
Viewing frame stream status information

Figure 25.6-1 shows an example frame stream status display for FRE cards. Table
25.6-1 summarizes the fields shown on this display.
(400)
25.6-1


NNP 95-2035-01-00-B
Figure 25.6-1: Frame Stream Status Display

FRE
Stations:5
Circuit
------A1-1
A1-2
A1-3
A1-4
A1-5
A1-6
A1-7
A1-8
A1-9
A1-10
A1-11
A1-12
A1-13
P413-H0-00
Toronto:A5
Stream
----------S1
S2
S3
S4
S5
S6
S7
S8
S9
S10
S11
S12
S13
Alarms: 21
Application
-------------STREAM
STREAM
STREAM
STREAM
STREAM
STREAM
STREAM
STREAM
STREAM
STREAM
STREAM
STREAM
STREAM
Speed
--------256000 bps
64000 bps
64000 bps
64000 bps
64000 bps
56000 bps
64000 bps
64000 bps
56000 bps
64000 bps
64000 bps
64000 bps
64000 bps
24-Feb-97 9:40A
Status
------OOS-LMI
In Service
OOS-Idle
In Service
OOS-LMI
OOS-Mismatch
In Service
OOS-Disconnected
In Service
In Service
In Service
In Service
In Service
CONFIG STREAM SHOW_ALL

1-NEXT
6-
2-PREVIOUS
7-
38-CANCEL
49-QUIT
50-
Table 25.6-1: Frame Stream Status Fields

Field
Indicates
Circuit
Frame stream (Scc) or FRS, FRE or PE card circuit (cc) identifier in the range 1 to
31 (for single bandwidth) or 1 to 62 (for double bandwidth).
Stream
The frame stream identifier.
Application
The type of application configured for this circuit.
Speed
The interface speed configured for this circuit in b/s.
Status
The current state of this circuit.

In service: The card transmits and receives frames on this frame stream. (1)
OOS-Idle: The auto discovery option has been configured but the user device
protocol type has not been discovered because the user device is either not using
any protocol or has not sent any messages (there is no user device or it is
configured as Network). The card does not transmit or receive data frames on this
frame stream.
OOS-LMI: LMI protocol has declared the frame stream out of service, indicating a
protocol, sequence or timeout error. The card does not transmit or receive data
frames on this frame stream.
OOS-Mismatch: The operator has specified a protocol type, but the auto discovery
protocol has detected a protocol type mismatch between the user and network
devices. The card does not transmit or receive data frames on this frame stream.
OOS-Disconnected: The user has disconnected the circuit corresponding to this
frame stream. The card does not transmit or receive data frames on this frame
stream.
Busy Out: The card drops all frames arriving on this frame stream. You can put a
frame stream in this state by busying-out the frame stream.
Notes
1. If the local device is set for Network mode or auto discovery protocol, and the remote device is set
for Bidirectional mode, the NMTI shows the status of the frame stream on the local end is In Service,
while the status at the remote end is OOS. The frame stream cannot come into service.
25.6-2
(400)

NNP 95-2035-01-00-B

To view frame stream status information

When you select the SWITCH and SHOW_ALL softkeys, the screen displays the
frame stream status display with all the frame streams configured on an FRS or FRE
card.
If 14 or more frame streams are configured, the NEXT and PREVIOUS softkeys move
forwards and backwards through the list, one screen of information at a time.
CONFIG SWITCH SHOW_ALL
NEXT
PREVIOUS
SK000173
25.6.2
Configuring Frame Stream Parameters

When you select the STREAM softkey, the screen displays the frame stream
configuration display. The screen shows the configurable parameters for a frame
stream, including frame stream status and congestion status. Figure 25.6-2 shows a
frame stream configuration display. Figure 25.6-3 shows the frame stream
congestion notification parameters display. Table 25.6-2 summarizes the fields and
parameters on these displays.
Figure 25.6-2: Frame Stream Configuration Display
FRE
Stations:0
P413-H0-00
36120-A1
Frame Stream S1
Status
Using Circuit
Interface Speed
Congestion Status
Maximum Frame Size
Number Of Connections
Flags Between Frames
Protocol Type
Timeout
Alarms:1
24-FEB-97
1:31A
:OOS-Disconnected
:A1-1
:0 bps
:GREEN
:10 Kbytes
:80 %
:50 %
:1600 Octets
:0
:1
:Annex A Network
:15 secs
CONFIG STREAM S1
1-FRAME_SIZE
6-
2-THRESHOLDS
7-MORE
3-NUM_FLAGS
8-CANCEL
(400)
4-SHOW_CONS
9-QUIT
5-PROTOCOL
0-
25.6-3


NNP 95-2035-01-00-B
Figure 25.6-3: Frame Stream Congestion Parameters Display

FRE
Stations:0
P413-H0-00
36120-A1
Alarms:1
ENABLED
Clear Time:
15 mins
Report Type:
ALARMS
Raise Time:
5 secs
24-Feb-97
9:31A

1-FILTERING
6-
2-CLEAR_TIME
7-
3-RPT_TYPE
8-CANCEL
4-RAISE_TIME
9-QUIT
50-
Table 25.6-2: Frame Stream Notification Configuration Fields

Field
25.6-4
Description
Frame Stream
Frame stream name (if configured).
Status
The current operating state of the frame stream. The following status values are
In Service: Active state.
OOS-Idle: Inactive state.
OOS-LMI: Inactive state.
OOS-Mismatch: Inactive state.
OOS-Disconnected: Inactive state.
Busy Out: Inactive state.
Interface Speed
The interface speed configured for this frame stream in b/s.
Congestion
Status (1)
The current congestion state of the frame stream.

configured.
RED: Congestion is > the SCT threshold configured.
ACT
ACT configured for this frame stream in kilobytes.
SCT
SCT configured as a percentage of ACT (where SCT MCT).
MCT
MCT configured as a percentage of ACT (where MCT SCT).
Maximum Frame
Size
The maximum frame size allowed on this frame stream, in octets.
Number of
Connections
The total number of DLCs configured on this frame stream (this includes both
local and FASTbus DLCs).
Flags Between
Frames
The number of inter-frame flags transmitted between frames. This parameter

applies to FRE and PE cards only.
Protocol Type
The auto discovery protocol or the type of link management protocol configured
for the local end of this frame stream.
(400)

NNP 95-2035-01-00-B

Field
Description
Heartbeat
This parameter is configurable only if the protocol type is LMI User, Annex D
User or Bidirectional, or Annex A User or Bidirectional. It specifies the number
of seconds between each sequence only status enquiry message.
Status Rate
This parameter is configurable only if the protocol type is LMI User, Annex D
User or Bidirectional, or Annex A User or Bidirectional. It specifies the number
of heartbeat polling intervals between full status update status enquiry
messages.
Timeout
This parameter appears and is configurable only when the link management
protocol type is LMI Network or Network Extended, Annex D Network or
Bidirectional, or Annex A Network or Bidirectional. A time interval in the range of
5 to 30 s.
Filtering
Algorithm
Clear Time
Report Type
The format in which congestion information is reported. Report Type can be set
to report alarms or network management events.
Raise Time
Notes
1. When filtering is enabled, the indication of a Congestion Status change is temporarily delayed.
Frame stream congestion thresholds

The ACT, MCT and SCT parameters allow you to configure congestion thresholds
for each frame stream of an FRS, FRE or PE card.
ACT
The ACT allows you to control the amount of buffer space consumed by any one
frame stream and prevents one severely congested frame stream from consuming all
frame stream buffer resources. This value specifies the total amount of buffer space
available (transmit and receive queues) to buffer any frames transmitted on and
received from the network.
On the FRS card, the ACT range for a frame stream is 1 to 64 kbytes.
On the FRE and PE cards, the ACT range is 1 to 1500 kbytes.
SCT
Enter the SCT as a percentage of ACT (0 to 100%). The default is 80%.
MCT
Enter the MCT as a percentage of ACT (0 to 100%). The MCT must be less than or
equal to SCT. The default is 50%.
(400)
25.6-5


NNP 95-2035-01-00-B
Maximum frame size

This parameter specifies the maximum frame size allowed on the frame stream.
Frame size represents the number of octets contained in the information field of a
frame-relay frame. The card discards any frames it receives that exceed the
configured frame size.
Range
16 to 4472 octets (1 octet = 8 bits)
Default
1600 octets
Flags between frames

Flags are empty frames transmitted between data-bearing frames to allow frame
relay switches enough inter-frame processing time. The frame relay standard
requires a minimum inter-frame fill of one flag. The FRE and PE cards support 100%
utilization of all frame streams with single flags between frames (at a frame size of
16 octets or 128 bytes). This parameter is not configurable on FRS cards.
Range
1 to 10
Default
1
Protocol type
This parameter specifies the auto discovery protocol or the type of link management
protocol configured for the local end of this frame stream. You can configure each
frame stream with either the auto discovery option or a specific link management
protocol. You can also disable link management protocol support.
Note
Do not select the auto discovery option when a Bidirectional or a User mode protocol
is required.
25.6-6
(400)

NNP 95-2035-01-00-B

Options
Configure the protocol type parameter as one of the following.
Auto discovery:
After the auto discovery option is selected, the protocol type field is set to
Auto-Unknown Network and the stream status shows OOS-Idle. After the user
device protocol is discovered, the status field changes to In Service and the
protocol type field value changes to one of the following:
Auto-LMI Network (extended)
Auto-Annex D Network
Auto-Annex A Network
LMI:
The Local Management Interface protocol defined by the Frame Relay Forum
supports User, Network and Network Extended mode for operation over the
User-Network Interface only.
Annex D:
The link management protocol defined by ANSI T1.617 Annex D supports User
and Network modes for operation over the User-Network Interface and
Bidirectional mode for operation over the Network-Network Interface.
Annex A:
The link management protocol defined by ITU-T Q.933 Annex A supports User
and Network modes for operation over the User-Network Interface and
Bidirectional mode for operation over the Network-Network Interface.
No Protocol:
The No Protocol option disables protocol support, and protocol information from
the remote user (or network) device is ignored.
Default
Annex A Network
Heartbeat
The heartbeat polling interval specifies the number of seconds between each
sequence-only status enquiry message. The user device sends a status enquiry
message to the attached network device every heartbeat polling interval and expects
a status message in reply.
This parameter appears only when the link management protocol type is LMI User,
Annex D User or Bidirectional, or Annex A User or Bidirectional.
When the auto discovery protocol is configured and the streams are connected, the
network side monitors the user-side heartbeat value in order to calculate the
network timeout value. This calculation is made whenever the frame stream is OOS,
including the initial startup (which occurs at the time when the streams are
connected or the protocol type is changed). After the initial calculation, if the
network stream goes OOS, the heartbeat value is recalculated. The network stream
can go OOS if the heartbeat value on the user side is increased above the network
timeout value, causing timeout errors.
(400)
25.6-7


NNP 95-2035-01-00-B
Range
5 to 30 seconds in 5 second increments
Default
10 seconds
Status rate
The status message rate specifies the number of heartbeat polling intervals between
full status update status enquiry messages. A user device sends a full status update
status enquiry message at this number of intervals and expects a full status update
in reply from the attached network device.
This parameter appears only when the link management protocol type is LMI User,
Annex D User or Bidirectional, or Annex A User or Bidirectional.
Range
1 to 255
Default
6
Timeout
The status enquiry message timeout specifies the timeout period for the receipt of a
status enquiry message at the network side. The network device expects either a
sequence-only or a full status update status enquiry message from the attached user
device within this interval.
This parameter appears only when the link management protocol type is LMI
Network or Network Extended, Annex D Network or Bidirectional, or Annex A
Network or Bidirectional.
If the auto discovery protocol is configured on the network device, the timeout
parameter is not user configurable. The timeout value is initially set to 30 seconds
and then calculated automatically by the auto discovery protocol, according to the
user device heartbeat polling interval.
The timeout value is not recalculated automatically when the user-side heartbeat
value is changed. It is recalculated only if the change causes the frame stream to go
out of service.
25.6-8
(400)

NNP 95-2035-01-00-B

Range
5 to 30 seconds in 1 second increments
Default
15 seconds
Filtering
A filter is available to debounce the transition through congestion states. Filtering is
always enabled on the FRS card, and can be disabled on FRE and PE cards.
Options
Enable:

congestion alarm by filtering out the temporary spikes in congestion, giving a
long-term congestion average.
Disable:
When filtering is disabled, the transition consists of sharp spikes, allowing
space utilization.
Default
Enable
Clear time
The clear time is the length of time that a previously congested frame stream remains
below the Red state before a Stream Congestion Clear alarm is raised. For example,
if you configure the clear time to be 20 min, the clearing alarm is raised 20 min after
the frame stream has left the Red state. The clear time can be configured on FRE and
PE cards, and is fixed at 10 seconds for the FRS card.
Range
1 to 1440 min (1 min to 24 h)
Default
15 min
(400)
25.6-9


NNP 95-2035-01-00-B
Raise time
The raise time is the length of time that the frame stream remains in the Red state
before a Stream Congested alarm is raised. For example, if you configure the raise
time to be 10 s, an alarm is raised only after the frame stream has remained in the
Red state for 10 s. The raise time can be configured on FRE and PE cards, and is fixed
at 5 s for the FRS card.
Range
0 to 240 seconds
Default
When filtering is disabled, the default is 0 seconds. When filtering is enabled, the
default is 5 seconds.
Report type
Options
Alarms
Default
Alarms
25.6-10
(400)

NNP 95-2035-01-00-B

To configure frame stream parameters

CONFIG STREAM <Scc>
FRAME_SIZE THRESHOLDS NUM_FLAGS PROTOCOL

<size>
<flags>
ACT
SCT
CONGESTION
MCT
FILTERING CLEAR_TIME RAISE_TIME
<act> <sct> <mct>
TYPE
ENABLE*/
DISABLE
HEARTBEAT
<interval>
LMI
USER
MORE
STATUS_RATE TIME_OUT
<rate>
NOPROTOCOL ANNEX_D
NETWORK
NETEXT
<ct>
RPT_TYPE
<rt>
ALARMS*
MGT_EVENTS
<time>
ANNEX_A
AUTO
USER NETWORK BIDIRECT

SK000934
where
size is the number of octets (16 to 4472, 1600*)
flags is the number of inter-frame flags (1 to 10, 1*), not configurable on FRS cards
act is 1 to 64 kbytes on the FRS and 1 to 1500 kbytes on the FRE and PE in 1 kbyte increments (10*)
sct is 0 to 100 (80*)
mct is 0 to 100 (50*)
interval is 5 to 30 seconds in 5 second increments (10*)
rate is 1 to 255 (6*)
time is 5 to 30 seconds in 1 second increments (15*)
ct is 1 to 1440 min (15*)
rt is 0 to 240 seconds (5*)
(400)
25.6-11

NNP 95-2035-01-00-B
25.7
25.7 Data Link Connections

Data Link Connections

This chapter introduces DLCs and explains how to do the following:
25.7.1
view DLC status by frame stream

view FASTbus DLC status
connect a local DLC
connect a DLC between FRS, FRE or PE cards
connect a FASTbus DLC
Understanding Data Link Connections

DLCs join one logical data link to another. All DLCs are bidirectional (full duplex).
You can configure three types of DLCs:
local DLCs
card-to-card DLCs across the backplane
card-to-card DLCs over the FASTbus
You configure a local DLC between two frame stream-DLCIs on the same card,
using DLCIs in the range 16 to 1007. DLCIs must be unique on each frame stream
(the same DLCI can be used on different frame streams). You can connect a DLCI to
only one other DLCI at a time; point-to-multipoint circuits or multicast circuits are
not supported.
You configure a card-to-card DLC between a frame stream-DLCI on one card and a
frame stream-DLCI on another card in the same node over an intermediate frame
stream created between the two cards.
For frame stream connections across the backplane, the intermediate frame stream
uses the 64 Mb/s circuit-switched backplane bus. You configure card-to-card DLCs
using DLCIs in the range 16 to 1007, as for local DLCs.
For FRE and PE cards on a 36120 MainStreet system, the intermediate frame stream
uses the 100 Mb/s packet-switched FASTbus and the connections are called
FASTbus DLCs. You configure FASTbus DLCs using DLCIs in the range 2000 to
3983. You can use a DLCI in this range to identify only a single connection between
two frame stream-DLCIs (multicast circuits are not supported).
Table 25.7-1 lists the maximum number of DLCs and DLCIs available on the FRS,
FRE and PE cards. You can configure class-of-service parameters (CIR, Bc and Be)
for each DLC (see chapter 25.8).
(400)
25.7-1


NNP 95-2035-01-00-B
Table 25.7-1: Available DLCs and DLCIs

Resource
Total DLCs
DLCI Range
FRS card
1024
16 to 1007
FRE or PE card
1984
16 to 1007 and
2000 to 3983
Frame Stream
992
16 to 1007
FASTbus interface
on any FRE or PE
card
1984
2000 to 3983
Note
You must configure the 36120 ID and station ID on FRE and PE cards before you can
configure DLCs over the FASTbus (see chapter 25.4).
25.7.2
Viewing DLC Status Information

You can view DLC status information for frame streams or FASTbus stations. Figure
25.7-1 shows an example DLC status display for a frame stream, and Figure 25.7-2
shows an example DLC status display for a FASTbus station.
Table 25.7-2 summarizes the fields in the displays.
Figure 25.7-1: Stream DLC Status Display
FRE
CONFIG
Cards:5
NewYork:A5
Alarms: 21
24-Feb-97
From
Status
Connected To
Status
2-26
2-27
2-100
2-128
2-344
2-472
Loopback
Active
Active
Active
Busy Out
Active
3-128
4-512
5-1000
12-14
22-54
8-472
Loopback
Active
Active
Active
Busy Out
Active
STREAM
1-PREVIOUS
6-
25.7-2
P413-H0-00
S2
9:40A
SHOW_CONNS
2-NEXT
7-
3-START_DLCI
8-CANCEL
(400)
49-QUIT
50

NNP 95-2035-01-00-B

Figure 25.7-2: FASTbus DLC Status Display

FRE
Cards: 4
P413-H0-00
NewYork:A5
Alarms: 21
24-Feb-93
From
Status
Connected To
Status
F5-2006
F5-2700
F5-2477
F5-3600
F5-3784
F5-3878
Loopback
Active
Busy Out
Active
Active
Active
S3-128
S4-512
S5-1000
S21-14
S9-54
S31-472
Loopback
Out Of Service
Busy Out
Active
Active
Active
CONFIG
9:40A
FASTBUS SHOW_CONNS F5
1-PREVIOUS
6-
2-NEXT
7-
3-START_DLCI
8-CANCEL
49-QUIT
50-
Table 25.7-2: DLC Status Display Fields

Field
Indicates
From
A list of the DLCs configured on the selected frame stream.
Connected To
A list of the DLCs connected to the DLCs in the From column.
Status
The current state of the DLC.

Active: Active state; the FRS, FRE or PE card transmits and receives frames
on this DLC.
Inactive: Inactive state: the link management protocol has reported this DLC
deleted or down.
Busy Out: Inactive state; the card drops all frames arriving on this DLC. You
can put a DLC in this state by busying out the DLC (see Maintenance).
Loopback: Active state; the card transmits all frames arriving on this DLC on
the same stream with the DLCI unchanged. You can put a DLC in this state
by applying a DLC loopback to either end of a DLC connection.
To view DLC status by frame stream

When you select the STREAM and SHOW_CONNS softkeys, the screen displays the
status of all local and FASTbus DLCs configured on any frame stream on this FRS,
FRE or PE card. You can specify a particular DLCI to start the display with the
START_DLCI softkey.
(400)
25.7-3


NNP 95-2035-01-00-B
If there are more than 14 DLCs configured, the NEXT and PREVIOUS softkeys move
forward and backward through the list, one screen at a time.
CONFIG STREAM <Scc> SHOW_CONNS
START_DLCI
NEXT
PREVIOUS
<dlci>
SK000175
where dlci is 16 to 1007
To view FASTbus DLC status

When you select the FASTBUS and SHOW_CONNS softkeys on an FRE or PE card,
the screen displays all the FASTbus DLCs configured on any FASTbus station
(except the station you are logged onto). You can specify a particular DLCI to start
the display with the START_DLCI softkey. If there are more than 14 DLCs
configured, the NEXT and PREVIOUS softkeys move forward and backward
through the list, one screen at a time.
CONFIG FASTBUS SHOW_CONNS <station>
START_DLCI
NEXT
PREVIOUS
<dlci>
SK000176
where
station is the station identifier (1 to 64, excluding the FRE or PE card running the NMTI session)
dlci is 2000 to 3983
25.7.3
Configuring Data Link Connections

This section describes how to configure and connect the following DLC types:
local DLCs
card-to-card DLCs across the backplane
card-to-card DLCs over the FASTbus
25.7-4
(400)

NNP 95-2035-01-00-B

Configuring local DLCs

Figure 25.7-3 shows an example of a local DLC in which S9-123 on the FRE card with
station ID 23 cross-connected to S8-201 on the same FRE card. A frame arriving from
the network on S9-123 is transmitted on S8-201. To connect a DLC on FRE 23 frame
stream S9 to a DLC on FRE 42 frame stream S12, you must configure a FASTbus DLC
connection.
Figure 25.7-3: Local DLC Example
36120 ID 17
36120 MainStreet system
36120 ID 17
S9
S8
S12
FASTbus
FRE
23
36120
MainStreet node
FRE
42
36120
MainStreet node
S9-123 X S8-201
4069
Table 25.7-3 summarizes the rules for configuring local DLCs.

Table 25.7-3: Local DLC Connection Rules
Rule
Example
Configure only one connection for a DLC. Multicast

connections are not supported.
Invalid:
S1-876 x S2-42
S1-876 x S3-19
Assign unique DLCIs only on a single frame stream.
Valid:
S1-876 x S2-876
Do not connect a DLC on a frame stream to itself. (1)
Invalid:
S1-876 x S1-876
You can connect different DLCs on the same frame

stream.
Valid:
S1-456 x S1-789
Notes
1. Unless a DLC loopback is initiated. See Maintenance.
(400)
25.7-5


NNP 95-2035-01-00-B
To connect local DLCs

CONFIG CONNECT <Scc-dlci>
TO_DLC
DISCONNECT
<Scc-dlci>
SK000177
where
Scc is a frame stream identifier (1 to 31 for FRS cards, 1 to 62 for FRE and PE cards)
dlci is 16 to 1007
Configuring card-to-card DLCs across the backplane

You configure backplane DLCs in two steps. In the example in Figure 25.7-4, S12-147
on FRS 1 is cross-connected to S18-236 on FRE 2. Both cards need not be installed in
the same shelf, but they must be installed in the same large multiplexer system. A
frame stream has been created between FRS 1 and FRE 2 by connecting circuit 3 on
FRS 1 to circuit 5 on FRE 2. FRS 1 sees this frame stream as S3; FRE 2 sees frame
stream S5.
Figure 25.7-4: Backplane DLC Connection Example
S12-147
S12
S13
FRS 1
S12-147 X S3-452
FRE 2
S5-452 X S18-236
S3
S5
S17
S18-236
S18
5448
At FRS 1, the first frame stream-DLCI (S12-147) is connected to a frame stream-DLCI

(S3-452) on the intermediate frame stream. The DLCI used on the intermediate frame
stream is chosen from the range 16 to 1007.
At FRE 2, the second frame stream-DLCI (S18-236) is connected to a frame
stream-DLCI (S5-452) on the intermediate frame stream. The same DLCI (452) is
used.
25.7-6
(400)

NNP 95-2035-01-00-B

The same DLCI (452) must be used at both ends of the intermediate connection to
uniquely identify this particular connection between the two cards. The same DLCI
cannot be used in any other connections between these two cards, but it can be used
in connections between other FRS and FRE cards; for example, between FRS 1 and
any other FRS or FRE card except FRE 2.
The same configuration rules apply to card-to-card DLCs across the backplane as
apply to local DLCs (see Table 25.7-3).
To connect card-to-card DLCs across the backplane

1.
Log on to the first card and enter:

CONFIG CONNECT <Scc-dlci1>
TO_DLC
DISCONNECT
<Scc-dlci2>
SK000178
where
Scc-dlci1 is the frame stream and DLCI (16 to 1007) for the first card
Scc-dlci2 is the frame stream and DLCI (16 to 1007) for the frame stream between cards
2.
Log on to the second card and enter:

TO_DLC
DISCONNECT
<Scc-dlci3>
SK000179
where
Scc-dlci2 is the frame stream and DLCI (16 to 1007) for the frame stream between cards
Scc-dlci3 is the frame stream and DLCI (16 to 1007) for the second card
Configuring FASTbus DLCs

You configure a FASTbus DLC in two steps. In the example in Figure 25.7-5, S9-345
on the FRE card with station ID 23 is cross-connected to S12-124 on the PE card with
station ID 42. Both cards need not be installed in the same shelf, but they must both
belong to the same 36120 MainStreet system (both the FRE and PE card must have
the same 36120 ID; see chapter 25.4).
(400)
25.7-7


NNP 95-2035-01-00-B
Figure 25.7-5: FASTbus DLC Connection Example
36120 ID 17
36120 ID 17
S9
S7
S12
FASTbus
FRE
23
PE
42
36120
MainStreet node
36120
MainStreet node
S9-345 X F42-2013
F23-2013 X S12-124
S9-345 X S7-678
4070
At FRE 23, the first frame-stream DLCI (S9-345) is cross-connected to a FASTbus

circuit-DLCI. The FASTbus circuit used (F42) corresponds to the station ID of the PE
card at the far end of this connection. FASTbus DLCIs can be chosen from the range
2000 to 3983. The same FASTbus DLCI (2013) must be used at both ends of the
FASTbus DLC.
At PE 42, the second frame stream-DLCI (S12-124) is also connected to a FASTbus
circuit-DLCI pair. The FASTbus circuit chosen at this end of the connection (F23)
corresponds to the station ID of the FRE card. The same FASTbus DLCI (2013) must
be used. A frame arriving from the network on S9-345 is transmitted on the FASTbus
with a destination address of F42-2013. When FRE 42 sees this frame, it receives it
and forwards the frame on the DLC (S12-124) corresponding to the FASTbus DLCI
(2013) of the frame.
The FASTbus DLCI uniquely identifies the particular connection between the two
cards connected to the FASTbus. The same FASTbus DLCI cannot be used in any
other FASTbus connections between these two cards, but it can be used in FASTbus
connections between other FRE or PE cards; for example, between FRE 23 and any
other FRE or PE card except PE 42.
25.7-8
(400)

NNP 95-2035-01-00-B

Table 25.7-4 summarizes the rules for configuring FASTbus DLCs.

Table 25.7-4: FASTbus DLC Connection Rules
Rule
Example
Use a FASTbus DLCI to connect only a single

pair of frame stream-DLCIs. Multicast
connections are not supported.
Invalid:
F1-2876 x S2-42 (Station ID = 2)

F1-2876 x S3-19 (Station ID = 2)
Use the same FASTbus DLCI at either end of a

FASTbus DLC connection between two FRE or
PE cards. Do not use this DLCI in any other
FASTbus DLC connection between these two
cards (you can use it in FASTbus DLCs between
any other two FRE or PE cards).
Valid:
F1-2876 x S2-42 (Station ID = 2)

F2-2876 x S3-19 (Station ID = 1)
F3-2876 x S2-43 (Station ID = 2)
F2-2876 x S3-19 (Station ID = 3)
Invalid:
F1-2876 x S2-42 (Station ID = 2)

F2-2876 x S3-19 (Station ID = 1)
F1-2876 x S2-43 (Station ID = 2)
F2-2876 x S3-19 (Station ID = 3)
Do not connect a FASTbus DLC to itself. (1)
Invalid:
F2-2876 x F2-2876
Do not connect two different FASTbus DLCs.
Invalid:
F1-456 x F2-789
An FRE or PE card cannot use the FASTbus

circuit whose ID matches the card station ID (the
self circuit).
Invalid:
F2-2876 x S2-42
Notes
1. Unless a DLC loopback is initiated. See Maintenance.
Note
For the configuration and maintenance procedures, a FASTbus DLC connection can
be identified by either its frame-stream-DLCI (S9-345 in Figure 25.7-5) or the
FASTbus circuit-DLCI it is connected to (F42-2013 in Figure 25.7-5).
(400)
25.7-9


NNP 95-2035-01-00-B
To connect FASTbus DLCs

1.
Log on to the first FRE or PE card and enter:

TO_DLC
DISCONNECT
<Fnn-dlci2>
SK000180
where
Scc-dlci1 is the frame stream and DLCI (16 to 1007) identifier on this FRE or PE card
Fnn-dlci2 is the FASTbus circuit (nn is the station id of the FRE or PE card you want to connect to)
and the connecting DLCI (2000 to 3983) identifier for the frame stream between cards
2.
Log on to the second FRE or PE card and enter:

CONFIG CONNECT <Fnn-dlci2>
TO_DLC
DISCONNECT
<Scc-dlci3>
SK000181
where
Fnn-dlci2 is the FASTbus circuit (nn is the station id of the FRE or PE card you are connecting to)
and the connecting DLCI (2000 to 3983) identifier for the frame stream between cards
Scc-dlci3 is the frame stream and DLCI (16 to 1007) identifier on this FRE or PE card
For example, the connections in Figure 25.7-5 are:
CONFIG CONNECT S9-345 TO_DLC F42-2013
CONFIG CONNECT F23-2013 TO_DLC S12-124
25.7-10
(400)

NNP 95-2035-01-00-B
25.8
25.8 Class-of-service Parameters

Class-of-service Parameters
This chapter explains how to configure the class-of-service parameters and enable or
disable of class-of-service enforcement.
25.8.1
Understanding Class-of-service Parameters

You can configure class-of-service parameters for each DLC cross-connection,
applying values to each frame stream-DLCI endpoint of the connection (the points
at which frames enter from or exit to the network). You can enable or disable the
enforcement of class-of-service parameters independently at each frame
stream-DLCI endpoint.
You cannot configure class-of-service for DLCs over the FASTbus.
Symmetric and asymmetric class-of-service

Class-of-service parameters may be adjusted in such a way that the CIR, Be and Bc
are different (asymmetric class-of-service), or the same (symmetric class-of-service)
for each direction on the DLC cross-connection.
Card-to-card DLCs
In Figure 25.8-1, a PVC is created by a card-to-card configuration in which S12-147
on FRS 1 is cross-connected to S18-236 on FRE 2. This PVC is composed of two DLC
cross-connections.
The first DLC cross-connection in this PVC is S12-147 X S3-452 on FRS 1. The second
DLC cross-connection in this PVC is S5-452 X S18-236 on FRE 2.
Class-of-service parameters are independently configured for each
cross-connection. Traffic entering or exiting the network at S12-147 is subject to the
class-of-service you configure for the DLC S12-147 X S3-452.
Class-of-service configuration can be applied to traffic entering or exiting the
intermediate frame stream between the two cards, at S12-147 X S3-452. If
class-of-service is enabled on the DLC, all data that crosses this connection is subject
to the class-of-service that you configure at this connection, regardless of the
class-of-service configured on previous or later cross-connections. If you want a
consistent class-of-service enforcement across the entire PVC, you must configure
the same parameter values at each DLC cross-connection.
For example, if you configure S12-147 X S3-452 with a CIR of 128 kb/s, and S5-452 X
S18-234 with a CIR of 32 kb/s, the prevailing CIR over that PVC will be 32 kb/s
when class-of-service is enabled on each DLC.
(400)
25.8-1


NNP 95-2035-01-00-B
After you configure class-of-service parameters, you can enable or disable the
enforcement of these parameters independently at each DLC for each direction of
traffic.
Figure 25.8-1: Card-to-card Class-of-service Configuration Example
S12-147
S12
S13
FRS 1
S12-147 X S3-452
FRE 2
S5-452 X S18-236
S3
S5
S17
S18-236
S18
5448
DLCs over the FASTbus

Figure 25.8-2 shows a FASTbus configuration in which S9-345 on FRE 23 is
cross-connected to S12-124 on the PE card with station ID 42. Class-of-service
parameters can be configured to apply to S9-345 and S12-124. Traffic entering from
or exiting to the network at S9-345 or S12-124 is subject to the class-of-service
configured. Class-of-service configuration does not apply to traffic entering or
exiting the FASTbus (it does not apply to FASTbus DLCs F42-2013 and F23-2013).
Figure 25.8-2: FRE Class-of-Service Configuration Example
36120 ID 17
36120 ID 17
S9
S7
S12
FASTbus
FRE
23
PE
42
36120
MainStreet node
36120
MainStreet node
S9-345 X F42-2013
F23-2013 X S12-124
S9-345 X S7-678
4070
After you configure class-of-service parameters, you can enable or disable the
enforcement of these parameters independently at each frame stream-DLCI
endpoint (S9-345 and S12-124 in Figure 25.8-2) exiting the FASTbus.
25.8-2
(400)

NNP 95-2035-01-00-B
25.8.2

Configuring Class-of-service Parameters and Rate

Enforcement
This section describes how to configure class-of-service parameters for DLCs.
Use the INFO_RATE softkey to configure the CIR, Bc and Be in both directions at
each frame stream-DLCI endpoint on FRS, FRE or PE cards.
You can also enable or disable enforcement of the configured class-of-service
parameters independently at each frame stream-DLCI endpoint of a DLC, for each
direction of traffic. The default is disabled.
As shown in Figure 25.8-1, you can configure the class-of-service values for
connection S12-147 X S3-345. The class-of-service values for each direction on that
link are configured independently. The CIR does not have to be identical for each
direction on the link.
If you wish to configure the class-of-service in the direction S12-147 (endpoint 1) to
S3-452 (endpoint 2), you select FROM_1->2 from the screen, and then change the
existing CIR value. If you wish to configure the CIR in the opposite direction on that
path, select FROM_2->1, and then change the existing class-of-service values.
Class-of-service display
Figure 25.8-3 shows an example class-of-service configuration display. Table 25.8-1
summarizes the fields on this display.
Figure 25.8-3: Class-of-Service Configuration Display
FRE
Stations:nn
P412-H1-00
Toronto:A
ENDPOINT 1: S12-147
S3-452
Alarms:1
8:35a
Connected To
ENDPOINT 2:
FROM_1->2
FROM_2->1
DISABLED
DISABLED
Rate Enforcement State

Committed Information Rate (CIR)
Committed Burst Size (BC)
Excess Burst Size (BE)
11-May-1997
:512000 bps
:512000 bits
:1984000 bits
:64000 bps
:64000 bits
:1984000 bits
CONFIG CONNECT S11-234 INFO_RATE FROM_1->2
1-CIR
6-
2-BE
7-
3-BC
8-CANCEL
(400)
4-ENABLE
9-QUIT
5-DISABLE
0-
25.8-3


NNP 95-2035-01-00-B
You select FROM_1->2 to configure the CIR, Be and Bc for data originating at
ENDPOINT 1 (S12-147) being sent to ENDPOINT 2 (S3-452). You select FROM_2->1
to configure the CIR, Be and Bc for data flowing in the opposite direction through
that DLC.
Table 25.8-1: Class-of-Service Configuration Fields
Field
Indicates
ENDPOINT 1
One endpoint of a DLC.
ENDPOINT 2
The other endpoint of the DLC referred to by ENDPOINT 1.
FROM_1->2
Indicates that the rate enforcement state and class-of-service

parameters below apply to data transmitted through the DLC from
ENDPOINT 1 to ENDPOINT 2.
FROM_2->1
Indicates that the rate enforcement state and class-of-service

parameters below apply to data transmitted through the DLC from
ENDPOINT 2 to ENDPOINT 1.
The currently configured class-of-service enforcement state.

Configurable only for an FRS, FRE or PE Card-stream DLCI (not
applicable to a FASTbus stream-DLCI).
Enabled: The switch enforces the configured class-of-service
parameters.
Disabled: Class-of-service parameters remain as configured but are
never enforced.
Committed Information
Rate (CIR)
The CIR configured for this DLC, in the range 0 to 1984000 b/s.
Committed Burst Size

(BC)
The Bc configured for this DLC, in the range 0 to 1984000 bits.
Excess Burst Size (BE)
The Be configured for this DLC, in the range 0 to 1984000 bits.
Rate enforcement state

This parameter specifies whether the switch enforces the configured class-of-service
values for one or both directions of traffic. The options are Enabled or Disabled.
Enabled
This option specifies that the switch enforces the configured class-of-service values.
The following class-of-service restrictions apply.
A DLC may transmit a maximum of Bc bits over a time interval of Tc seconds.
25.8-4
This defines the CIR for the DLC. Under normal conditions, the DLC is
guaranteed this throughput.
A DLC may transmit a burst in excess of its CIR provided the total number of bits
transmitted over a time interval of Tc seconds is not more than Be + Bc. The DE
bit is set in frames transmitted in this range.
If a DLC attempts to transmit a burst in excess of its CIR, where the total number
of bits transmitted over a time interval of Tc seconds is more than Be + Bc, the
card discards all frames queued for transmission in this range.
(400)

NNP 95-2035-01-00-B

Note
On FRE and PE cards, class-of-service enforcement can be enabled only for a frame
stream-DLCI. If either DLCI endpoint corresponds to a FASTbus circuit-DLCI, the
system does not allow the selection and issues a warning message.
Disabled
This option specifies that class-of-service parameters remain as configured but are
never enforced. The DE bit is never set in any frame and frames are never discarded
regardless of how much a DLC attempts to transmit.
Caution
Disabling class-of-service enforcement may lead to serious network congestion.
Committed information rate

Configure the CIR in the range 0 to 1984000 b/s. The default is 0 b/s.
Committed burst size

Configure the Bc in the range 0 to 1984000 bits in 1 bit increments. The default is
0 bits.
Excess burst size

Configure the Be in the range 0 to 1984000 bits in 1 bit increments. The default is
1984000 bits.
(400)
25.8-5


NNP 95-2035-01-00-B
To configure class-of-service parameters and rate enforcement

CONFIG CONNECT <Scc-dlci> or <Fnn-dlci> INFO_RATE
FROM_1->2
CIR
BC
BE
<cir>
<bc>
<be>
FROM_1->2
ENABLE
DISABLE
SK000182
where
Scc-dlci is the frame stream (1 to 31 or 1 to 62) and DLCI (16 to 1007)
Fnn-dlci is the FASTbus circuit (nn is the station identifier) and dlci (2000 to 3983)
cir is 0 to 1984000 b/s
bc and be are 0 to 1984000 bits
Note
The FASTbus circuit-DLCI (Fnn-dlci) merely identifies a FASTbus DLC. The
class-of-service parameters configured apply only to the FRE or PE Card frame
stream-DLCI (Scc-dlci) endpoints even if you use the FASTbus circuit-DLCI.
25.8-6
(400)

NNP 95-2035-01-00-B
25.9
25.9 FRS Subrate Multiplexing

FRS Subrate Multiplexing

This chapter explains how to configure subrate multiplexing using the SRIM on the
FRS card.
25.9.1
Understanding Subrate Multiplexing on the FRS Card

The SRIM is an optional module that can be installed on the FRS card to provide
subrate multiplexing. Although normal FRS card circuits support subrate speeds,
the speeds must be multiples of 8 kb/s. With the SRIM, the FRS card can process
data at subrate speeds that are not limited to 8 kb/s multiples.
Interface speeds and protocols

The SRIM allows you to multiplex subrate streams on a single aggregate circuit,
using HCM, DDS or X.50 rate adaption methods. Table 25.9-1 lists the subrate
protocols and speeds supported by the SRIM.
Table 25.9-1: Subrate Speeds and Protocols
HCM (kb/s)
DDS (kb/s)
X.50 (kb/s)
DS0-A
DS0-B
DIV_2
DIV_3/DIV_5 (1)
1.2
2.4
2.4
2.4
2.4
2.4
4.8
4.8
4.8
4.8
4.8
9.6
9.6
9.6
9.6
9.6
19.2
19.2
19.2
14.4
56
48 (2)
48 (2)
19.2
38.4
Notes
1. X.50 Div. 2, X.50 Div. 3 and HCM are X.50 Div. 5-compliant and can do random framing at all speed
rates.
2. At 48 kb/s, X.50 Div. 2 and X.50 Div. 3 are called X.50 bis.
(400)
25.9-1


NNP 95-2035-01-00-B
Connections
SRIM aggregate circuits can be connected to:
2B1Q and DNIC Line cards and the OCU-DP channel unit
all aggregate primary rate cards
all DCCs and the 64 kb/s Codirectional card
SRMs or MJUs on DSP cards
SRSs on DSP4 cards
SRIM configurable parameters

Slot options affect all circuits or streams on an FRS card configured with a SRIM.
Circuit options affect the specified aggregate circuit. Subrate stream options affect
the specified subrate stream.
Table 25.9-2 lists the configurable parameters for the SRIM at the slot, circuit and
subrate stream levels.
Note
For SRIM-mode rate adaption, DS-0A is always in the first position.
Table 25.9-2: SRIM Configurable Parameters

Parameter
Options
Restrictions
Slot
Module Type
No module
SRIM
Rate Adaption Mode
X.50 or HCM
DDS or HCM
Module type: SRIM
Speed Range
1.2 to 56 kb/s
A-bit Handling
Non-standard
Standard
SRIM mode: X.50 or HCM
Loopback Detection
On
Off
SRIM mode:
DDS or HCM
X.50 or HCM
Aggregate Circuit Mode
Stream
Rate adaption
Encapsulation
Rate Adaption
HCM
DDS
X.50
SRIM mode: DDS or HCM
Circuit
25.9-2
(400)

NNP 95-2035-01-00-B

Parameter
Options
Restrictions
Interface Speed
2400 b/s
4800 b/s
9600 b/s
19200 b/s
56000 b/s

Rate adaption: DDS
DDS Method
DS-0A and DS-0B:

2.4 kb/s
4.8 kb/s
9.6 kb/s
19.2 kb/s
56 kb/s (DS-0A only)
Rate adaption: DDS
DDS Subframe Position
1 to 20 at 2400 b/s
1 to 10 at 4800 b/s
1 to 5 at 9600 b/s
2 or 4 at 19200 b/s
1 at 56000 b/s (DS-0A only)

Rate adaption: DDS
DDS method: DS-0B
Framing Bit Position
B7* to B0
Rate adaption: HCM
Transport Bandwidth
1 to 8 (x 8 kb/s)
Rate adaption: HCM (1)
X.50 Method
Div. 2
Div. 3
Data Position
F0-B7 to F9-B0
Rate adaption: HCM
DS-0A Interface Speed
2400 b/s
4800 b/s
9600 b/s
19200 b/s
56000 b/s

Rate adaption: DDS
DDS method: DS-0A
DS-0B Interface Speed
2400 b/s
4800 b/s
9600 b/s
19200 b/s
Rate adaption: DDS

DDS method: DS-0B
X.50 Div. 2, 3 or 5 Interface

Speed
2400 b/s
4800 b/s
9600 b/s
19200 b/s

Rate adaption: X.50 Div. 2, 3 or 5
X.50 Bis
48000 b/s
SRIM mode: X.50

Rate adaption: X.50 Bis
Rate Adaption
DDS
HCM
X.50
Signalling
On
Off
Rate adaption: HCM
Subrate Stream
(400)
25.9-3


NNP 95-2035-01-00-B
Parameter
Options
Restrictions
X.50 Div. 2 Subframe Position
at 2.4 kb/s:
1 5 9 13 17 21 25 29 33 37 41
45 49 53 57 61 65 69 73 77
at 4.8 kb/s:
1 9 17 25 33 41 49 57 65 73
at 9.6 kb/s:
17 33 49 65
at 19.2 kb/s:
1 17 33 49

Rate adaption: X.50 Div. 2
X.50 Div. 3 Subframe Position
at 2.4 kb/s:
1 to 20
at 4.8 kb/s:
1 3 5 7 9 11 13 15 17 19
at 9.6 kb/s:
1 5 9 13 17
at 19.2 kb/s:
1 5 9 13

Rate adaption: X.50 Div. 3
X.50 Bis Subframe Position
48 kb/s
1

Rate adaption: X.50 bis
Transport Bandwidth
1 to 8 (x 8 kb/s)
Rate adaption: HCM (1)
Transport Position
B7 to B0
Rate adaption: HCM
Notes
1. There are no restrictions when transport bandwidth is configured at the subrate stream level.
25.9.2
Configuring SRIM Card Options

To begin configuring subrate multiplexing on the FRS card, you must configure the
card for the SRIM and select the card slot options. These options are:
rate adaption mode

speed range
loopback detection
A-bit handling
Rate adaption
To select the rate adaption mode for the card, choose X50_OR_HCM or
DDS_OR_HCM.
25.9-4
(400)

NNP 95-2035-01-00-B

Speed range
Table 25.9-1 lists the interface speeds available for each rate adaption method. For
X50_OR_HCM rate adaption mode, you can use the SPEED_RANG softkey to select
an interface speed range of:
1.2 to 4.8 kb/s

2.4 to 19.2 kb/s
4.8 to 38.4 kb/s
48 kb/s
For DDS_OR_HCM rate adaption mode, you can select a range of:
1.2 to 4.8 kb/s

2.4 to 19.2 kb/s
4.8 to 38.4 kb/s
56 kb/s
Loopback detection
The SRIM does alternating loopback detection on DDS and latching loopback
detection on X.50 subrate streams. The SRIM cannot initiate loopbacks, but can
respond to loopback requests from the network. To enable loopback detection, select
LP_DET_ON; to disable it, select LP_DET_OFF.
A-bit handling
In X50_OR_HCM rate adaption mode, you can configure the card for standard or
non-standard A-bit handling by selecting A_STD_ON or A_STD_OFF.
To configure the SRIM card options

CONFIG SLOT <sn> OPTIONS MODULE
SRIM/NO_MODULE
X50_OR_HCM/
DDS_OR_HCM
1.2/4.8_K
SPEED_RANG
2.4/1.9_K
FUNCTION
LP_DET_ON/
LP_DET_OFF
4.8/38.4_K
48_K
A_STD_ON/
A_STD_OFF
56_K
SK000183
(400)
25.9-5

25.9.3

NNP 95-2035-01-00-B
Configuring Rate Adaption Circuits

After you have configured the card slot options, you can configure the rate adaption
method and parameters for SRIM circuits. Table 25.9-3 lists the parameters you can
configure for HCM, DDS and X.50 rate-adapted circuits.
Table 25.9-3: Circuit Configuration Parameters
HCM
DDS
X.50
Parameter
DDS method
Interface speed
Subframe position
Transport bandwidth
Framing bit position
Chapter 23.6 describes the rate adaption methods and their parameters. Table 25.9-4
lists the valid DDS DS0-B subframe positions for each interface speed.
Table 25.9-4: DDS Subframe Positions
25.9-6
Subframe Position Range
2400
1 to 20
4800
1 to 10
9600
1 to 5
19200
2 to 4
56000
(400)

NNP 95-2035-01-00-B


CONFIG CIRCUIT <sn-cc> FUNCTION APPLI
HCM
DDS
X.50
DIV_2
DIV_3
SK000184
To configure HCM circuits

TRANSP_BW
F_POSITION
<bw>
<Bn>
SK000185
where
bw is the number of 8 kb/s elements (1 to 8)
Bn is B7 to B0
To configure DDS circuits

METHOD
DS-0A
POSITION
I/F_SPEED
<pos>
<speed>
DS-0B_9.6
DS-0B_4.8
DS-0B_2.4
SK000186
where
pos is a valid subframe position for the selected interface speed (see Table 25.9-4)
speed is 2400, 4800, 9600, 19200 or 56000
Note
The POSITION softkey applies only to DS0-B circuits.
(400)
25.9-7

25.9.4

NNP 95-2035-01-00-B
Configuring Subrate Circuits

The rate adaption parameters you can configure for subrate streams are the same as
those for subrate circuits, with a few exceptions. Table 25.9-5 lists the parameters you
can configure for HCM, DDS and X.50 rate-adapted circuits.
Subrate streams are identified as SR1 to SR31.
Table 25.9-5: Stream Configuration Parameters
HCM
DDS
X.50
Parameter
Interface speed
Subframe position
Signalling option
Data position
Transport bandwidth
Framing bit position
Chapter 23.6 describes the rate adaption methods and their parameters. Table 25.9-6
lists the valid interface speeds for each rate adaption method, and Table 25.9-7 lists
valid DDS and X.50 subframe positions.
Table 25.9-6: Interface Speeds
HCM (b/s)
25.9-8
DDS (b/s)
X.50 (b/s)
DS0-A
DS0-B
DIV_2
DIV_3/DIV_5
1200
2400
2400
2400
2400
2400
4800
4800
4800
4800
4800
9600
9600
9600
9600
9600
14400
19200
19200
19200
19200
38400
48000
48000
56000
(400)

NNP 95-2035-01-00-B

Table 25.9-7: DDS and X.50 Subframe Positions

Interface
Speed (b/s)
DDS Subframe
Position Range
X.50 DIV_2 Subframe

Position
X.50 DIV_3 Subframe

Position
2400
1 to 20
1 5 9 13
17 21 25 29
33 37 41 45
49 53 57 61
65 69 73 77
1 to 20
4800
1 to 10
1 9 17 25
33 41 49 57
65 73
1357
9 11 13 15
17 19
9600
1 to 5
1 17 33 49
65
1 5 9 13
17
19200
2 to 4
48000
56000

CONFIG CIRCUIT <sn-SRcc> FUNCTION RATE_ADAPT METHOD
HCM
DDS
X..50
DIV_2
DIV_3
SK000187
To configure HCM streams

CONFIG CIRCUIT <sn-SRcc> FUNCTION RATE_ADAPT
TRANSP_BW
TRANSP_POS
I/F_SPEED
<bw>
<Bn>
<speed>
SIG_ON/
SIG_OFF
DATA_POSN
<Ff-Bb>
SK000188
where
bw is the number of 8 kb/s elements (1 to 8)
Bn is B7 to B0
speed is a valid speed from Table 25.9-6
Ff-Bb is F0 to F9 and B7 to B0
(400)
25.9-9


NNP 95-2035-01-00-B
To configure DDS and X.50 streams

I/F_SPEED
POSITION
<speed>
<position>
SK000189
where
speed is a valid speed from Table 25.9-6
position is a valid subframe position from Table 25.9-7
To configure the circuit application

CONFIG CIRCUIT <sn-SRcc> FUNCTION APPL STREAM*/FR_ENCAP
25.9.5
Connecting Subrate Streams

You can multiplex subrate streams to an aggregate circuit on the same card, as long
as:
the streams are the same rate adaption type

the aggregate circuit is configured for rate adaption before you make the
connection
the combined bandwidth of the subrate streams does not exceed the bandwidth
of the aggregate circuit
Note
See section 25.10.5 to connect subrate encapsulation circuits.
25.9-10
(400)

NNP 95-2035-01-00-B

To connect subrate streams

CONFIG CONNECT <sn-SRcc>
TO_CIRCUIT
DISCONNECT
<sn-cc>
SK000190
where
sn-SRcc is the subrate stream identifier
sn-cc is the aggregate circuit identifier
Figure 25.9-1 shows the NMTI screen for subrate multiplexing two HCM streams on
an aggregate circuit.
Figure 25.9-1: Subrate Multiplexing HCM Streams
3600 MainStreet
1117-H1-00
SRI Module: A1-01:HCM
F0
F1
F2
F3
F4
F5
F6
F7
F8
F9
B7
F
b
b
-
B6
a
b
b
-
B5
a
b
-
B4
a
b
-
B3
a
b
-
B2
b
b
-
Toronto:A
Alarms:1
NAME:
B1
b
b
-
B0
b
b
-
11-May-1997
8:35a
Connected To: None
Asterisks indicate current connections.

a =
A1-SR01;
b =
A1-SR02;
Composite Inputs: [None]

CONFIG CONNECT 1-SR2
1-SHOW_GROUP
6-
2-DISCONNECT
7-
3-TO_CIRCUIT
8-CANCEL
49-QUIT
50-
Figure 25.9-2 shows the NMTI screen for subrate multiplexing two DDS streams on
an aggregate circuit.
(400)
25.9-11


NNP 95-2035-01-00-B
Figure 25.9-2: Subrate Multiplexing DDS Streams

3600 MainStreet
1117-H1-00
Toronto:A
SRI Module: A1-02:DS-0B_4.8
NAME:
Alarms:1
11-May-1997
8:35a
Connected To: None
Asterisks indicate current connections.

1 =
A1-SR04;
2 =
A1-SR03;
Composite Inputs: [None]

CONFIG CONNECT 1-2
1-SHOW_GROUP
6-PROTECTING
25.9-12
27-
3-TO_CIRCUIT
8-CANCEL
(400)
49-QUIT
5-PROT_BY
0-

NNP 95-2035-01-00-B
25.10

Frame Relay Encapsulation

This chapter describes how to create, configure and connect circuits that perform
frame relay encapsulation on the FRS card.
Note
The PE and X.25 FRE cards also perform encapsulation and decapsulation, but only
on LAPB frames entering and exiting a 36120 MainStreet X.25 network. See section
27.13.1.
25.10.1
Understanding Frame Relay Encapsulation

Frame relay encapsulation is a service that allows frames from various HDLC-based
protocols to be encapsulated in frame relay T1.618 frames for transmission over
frame relay networks. Frame relay encapsulation provides point-to-point
connections over frame relay PVCs for protocols such as:
LAP
LAPB
LAPD
LAPM
SDLC
DSP
Appletalk
SS7
proprietary HDLC protocols, including CPSS
On the FRS card, encapsulation circuits terminate subrate or super-rate HDLC data
streams. When the FRS card receives frames from the HDLC devices, the frame
feeder subsystem encapsulates the HDLC frames in frame relay frames and inserts
the DLCI for the appropriate PVC. The switch routes the frame relay frames to their
destination over the frame relay network.
The destination device may be another FRS card, or customer-premise equipment
that supports Annex G or RFC 1490 encapsulation methods. The destination device
extracts, or decapsulates, the HDLC frames, and delivers them to the remote HDLC
devices.
The FRS card supports encapsulation and decapsulation according to the following
methods and standards:
ANSI T1.617a Annex G, Encapsulation of ITU-T X.25/X.75 over Frame Relay

RFC 1490, and ANSI T1.617a Annex F, Multiprotocol Encapsulation over Frame
Relay, (for LAPB only)
Transparent HDLC
(400)
25.10-1


NNP 95-2035-01-00-B
FRS cards must be equipped with a SRIM to provide encapsulation for subrate
HDLC data streams using HCM, DDS or X.50 rate adaption.
Figure 25.10-1 shows an example of using encapsulation to provide LAPB access to
a 36120 MainStreet X.25 network over frame relay.
Figure 25.10-1: LAPB Encapsulation Example
X.25
X.25
FRE
or
FRE
PECard
card
FRS card
LAPB
DTE
Annex G
or
RFC 1490
Annex G
or
RFC 1490
Frame relay
Encapsulation
Encapsulation
X.25
network
Decapsulation
LAPB
DTE
Annex G
or
RFC 1490
Decapsulation
Frame relay
Annex G
or
RFC 1490
PAD/FRAD
7550
Figure 25.10-2 shows an example of using the Transparent HDLC encapsulation

service to implement end-to-end connections for HDLC devices over frame relay.
The possible HDLC device types include terminals, hosts, front-end processors,
PBXs, and signalling nodes.
Figure 25.10-2: Transparent HDLC Encapsulation Example
FRS card
HDLC
FRS card
Frame
relay
network
Transparent
HDLC
Transparent
HDLC
HDLC
HDLC device
HDLC device
8036
LAPB Annex G encapsulation

Annex G encapsulation provides a means to encapsulate LAPB frames using a
2-byte header. In a Newbridge network, this method is typically used to provide
X.25 access from an FRS card to a PE or X.25 FRE card over frame relay. When X.25
devices require subrate access to PE or X.25 FRE cards, the subrate data streams must
be encapsulated in frame relay. LAPB Annex G encapsulation is the preferred
method for subrate X.25 access.
25.10-2
(400)

NNP 95-2035-01-00-B

When you configure an FRS circuit for LAPB Annex G encapsulation, you must
specify the maximum size of the X.25 packets that use the circuit. The size of the
LAPB frames is derived using the algorithms described in Appendix II of
Recommendation X.25; for packet sizes greater than 128 bytes, 9-bytes are added to
the X.25 packet size. The Annex G encapsulation method adds a 2-byte header. The
switch calculates the resulting frame relay T1.618 frame size as shown in
Table 25.10-1.
Table 25.10-1: Packet and Frame Sizes for Annex G
X.25 Packet Size
Frame Relay Frame Size
16, 32, 64 or 128
266
256
267
512
523
1024
1035
2048
2059
4096
4107
Figure 25.10-3 shows the frame format.

Figure 25.10-3: Annex G Encapsulation
0
EA
Data Link
Connection
Identifier
(DLCI)
LAPB address field
LAPB address field
LAPB control field
LAPB control field
LAPB information field

(X.25 - X.75)

(X.25 - X.75)
LAPB frame
T1.618 frame
Check sequence
Check sequence
EA
Flag
1 1
Flag
1 1
DE
BECN
LAPB frame
FECN
C/R
Annex G encapsulation
of a LAPB frame
Frame relay
information
field
7968
LAPB RFC 1490 encapsulation

Although RFC 1490 defines a multiprotocol encapsulation method, the FRS card
implementation currently supports only LAPB frames. In a Newbridge network,
this method can be used to provide X.25 access from an FRS card to a PE or X.25 FRE
card over frame relay, although this is not the preferred method.
(400)
25.10-3


NNP 95-2035-01-00-B
When you configure an FRS circuit for LAPB RFC 1490 encapsulation, you must
specify the maximum size of the X.25 packets that use the circuit. The LAPB frame
size is derived according to Appendix II of Recommendation X.25; for packet sizes
greater than 128 bytes, 9-bytes are added to the X.25 packet size. The RFC 1490
encapsulation method adds an 8-byte header. The switch calculates the resulting
frame relay T1.618 frame size as shown in Table 25.10-2.
Table 25.10-2: Packet and Frame Sizes for RFC 1490
X.25 Packet Size
16, 32, 64 or 128
272
256
273
512
529
1024
1041
2048
2065
4096
4113
Figure 25.10-4 shows the frame format using LAPB as the encapsulated protocol.
Figure 25.10-4: RFC 1490 Encapsulation of LAPB Frames
0
EA
Data Link
Connection
Identifier
(DLCI)
0
EA
Flag
1 1
DE
BECN
FECN
C/R
RFC 1490 encapsulation

of a LAPB frame
Control 0 x 03
NLPID 0 x 08
0 x 46
LAPB frame
Flag
1 1
0 x 81
0 x 66
0 x 80
LAPB Address Field
LAPB Address Field
LAPB Control Field
LAPB Control Field
LAPB Information Field

(X.25 - X.75)

(X.25 - X.75)
LAPB Frame
T1.618 Frame
Check Sequence
Check Sequence
Layer 2
protocol
ID
Layer 3
protocol
ID
Frame relay
information
field
7967
25.10-4
(400)

NNP 95-2035-01-00-B

Transparent HDLC encapsulation

The Transparent HDLC encapsulation service allows any HDLC-based, protocols,
including CPSS, to be encapsulated in frame relay T1.618 frames and transmitted
over a frame relay network. The network handles all frames transparently; that is, it
passes each frame end-to-end without examining the contents of the frame.
For more information on transparent CPSS encapsulation over frame relay networks
and FRS card CPSS connections, see chapter 17.6.
When you configure an FRS circuit for Transparent HDLC encapsulation, you must
specify the maximum size of the HDLC frames that use the circuit. The
encapsulation process adds a 2-byte header to the HDLC frame size.
The frame format is identical to that used for Annex G encapsulation (see
Figure 25.10-3). This format applies to all HDLC-based protocols.
Using Transparent HDLC encapsulation, a wide range of existing applications and
networks can be migrated onto a common frame relay backbone network, providing
bandwidth consolidation, centralized network management, and reduced support
costs. In addition, point-to-point HDLC connections can be moved from leased lines
to frame relay connections to take advantage of the bandwidth and cost efficiencies
of frame relay.
25.10.2
Creating Frame Relay Encapsulation Circuits

FRS circuits can be configured to perform frame relay encapsulation for basic rate,
super-rate, and transparent subrate devices. On FRS cards equipped with a SRIM,
FRS subrate circuits can be configured to perform encapsulation for subrate devices
using HCM, DDS and X.50 rate adaption methods.
To create frame relay encapsulation circuits

You create frame relay encapsulation circuits on FRS cards from the Control card
NMTI. These circuits provide frame relay network access to HDLC-based protocols
running at m n 8 kb/s.
APPLI
TRANSP_BW
I/F_SPEED
FR_ENCAP
<bandwidth>
<speed>
SK000191
where
bandwidth is n 8 kb/s, where n is 1 to 8
speed is 8 to1984 kb/s in multiples of 8, and must match the interface speed set for the primary rate or data
interface circuit
(400)
25.10-5


NNP 95-2035-01-00-B
Note
Configure the application as FR_ENCAP before configuring the interface speed or
transport bandwidth. The interface speed for the frame relay encapsulation circuit
must be configured to match the speed of the primary rate or data interface circuit
to which it connects.
To create subrate frame relay encapsulation circuits

From the Control card NMTI, you create subrate frame relay encapsulation circuits
on FRS cards equipped with a SRIM. These circuits provide frame relay network
access to HDLC-based protocols running at non-transparent subrate speeds (for
example, 9.6, 14.4, and 19.2 kb/s).
Note
Before configuring a subrate circuit for frame relay encapsulation, configure the rate
adaption parameters for that subrate circuit. See chapter 25.9 for more information.
CONFIG CIRCUIT <sn-SRcc> FUNCTION
RATE_ADAPT
APPLI
(see note)
FR_ENCAP
SK000192
where sn-SRcc is the slot number and subrate circuit number on the FRS card
25.10.3
Viewing Encapsulation Circuit Parameters

Figure 25.10-5 shows the NMTI display for the frame relay encapsulation
parameters. The non-configurable information fields are described in Table 25.10-3.
The configurable parameters are described in Table 25.10-4.
25.10-6
(400)

NNP 95-2035-01-00-B

Figure 25.10-5: Parameters for Frame Relay Encapsulation Circuits

FRS
P114-F0-00
NMTI Shelves
Alarms:4
ENCAP_CCT SR1
Status
Using Circuit
Interface Speed
Congestion Status
Encapsulated Protocol Max Frame Size
Required Frame Relay Frame Size
Connected To
Encapsulation type
19-AUG-94
8:35A
:OOS-Disconnected
:A1-2
:9600 bps
:GREEN
:4 Kbytes
:80%
:50%
:512 Octets
:529 Octets
:S1-100
:LAPB RFC 1490
CONFIG ENCAP CCT SR1

F1-FRAME_SIZE
F6-ENCAP_TYPE
F2-THRESHOLDS
F7-
F3F8-CANCEL
F4F9-QUIT
F5F10-
Table 25.10-3: Encapsulation Circuit Information Fields

Field
Description
Status
The current operating state of the circuit.

In Service: Active state; the circuit is configured as connected and is capable of
carrying traffic.
OOS-Disconnected: Inactive state; the circuit is not configured as connected.
Busy Out: Inactive state; the circuit is configured, connected and busied out for
maintenance.
Using Circuit
Shows the actual FRS circuit selected, or, if a subrate FRS circuit is selected, the
rate adapted FRS circuit to which the subrate encapsulation circuit is connected.
Interface Speed
Congestion Status
The current congestion state of the circuit.

YELLOW: Congestion is > the MCT threshold but the SCT threshold configured.
Required Frame
Relay Frame Size
The size of the frame relay T1.618 frame after the source protocol frame is
encapsulated. This is a readable value that is calculated based on the value of the
Encapsulated Protocol Max Frame Size parameter. The value of this field must
be less than the Maximum Frame Size parameter for the frame stream to which
this circuit is connected.
Connected to
The frame stream-DLCI to which the circuit is connected.
(400)
25.10-7


NNP 95-2035-01-00-B
Table 25.10-4: Configurable Encapsulation Circuit Parameters

Parameter
Options
Description
Absolute Congestion
Threshold (ACT)
1 64 kbytes in
1-kbyte increments
(* = 4)
The buffer size allocated to this circuit.
Severe Congestion Threshold

(SCT)
1 100% (* = 80%)
The SCT as a percentage of ACT (where

SCT > MCT).
Mild Congestion Threshold

(MCT)
1 100% (* = 50%)
The MCT as a percentage of ACT (where

MCT SCT).
Encapsulated Protocol
Maximum Frame Size
16 4472 bytes for

HDLC (* = 1600)
16, 32, 64, 128, 256,
512, 1024, 2048, or
4096 for LAPB
(* = 512)
The maximum frame size that can be

transmitted on this circuit. This value can
specify either an X.25 packet size or an
HDLC frame size.
Encapsulation Type
LAPB RFC 1490

LAPB Annex G*
Transparent HDLC
The encapsulation method used on the

circuit.
To view encapsulation circuit parameters

CONFIG ENCAP_CCT <cc> or <SRcc>
25.10.4
Configuring Encapsulation Circuit Parameters

When FRS circuits and FRS subrate circuits are configured to perform frame relay
encapsulation, you can configure the following parameters from the FRS NMTI:
frame size
number of flags between frames
encapsulation type
The parameters and allowable values are the same for subrate and super-rate
circuits.
Encapsulation circuit congestion thresholds

The ranges and default values for the ACT, MCT and SCT parameters are identical
to those for frame streams on FRS cards. See the subsection Frame stream
congestion thresholds in chapter 25.6 for information. The required values are
generally determined by the type of protocol being encapsulated.
25.10-8
(400)

NNP 95-2035-01-00-B

Encapsulating LAPB frames

For most X.25 access lines, Newbridge recommends the default values for the ACT,
MCT and SCT parameters. For high-speed access lines (>64 kb/s), you may have to
increase the buffer size (ACT) if statistics indicate that the circuit is frequently
congested.
Encapsulated protocol maximum frame size

This parameter specifies the maximum allowable size of packets or frames from the
source protocol. You specify either an X.25 packet size or an HDLC frame size.
When the encapsulation type is LAPB RFC 1490 or LAPB Annex G, you must specify
an X.25 packet size. The X.25 packet size value must be equal to or greater than the
maximum value of the Allowable Packet Size (N1) parameter for the X.25 access line
that uses the encapsulation circuit.
When the encapsulation type is Transparent HDLC, you must specify an HDLC
frame size.
Once you configure an X.25 packet size or an HDLC frame size, the Required Frame
Relay Frame Size field displays the size of the frame relay frames after
encapsulation. This field indicates the minimum value required for the Maximum
Frame Size parameter for the frame stream circuit to which the encapsulation circuit
connects.
Encapsulation type
This parameter specifies the encapsulation method, either LAPB RFC 1490, LAPB
Annex G or Transparent HDLC. When you select LAPB Annex G or Transparent
HDLC, the switch adds a 2-byte header to each frame being encapsulated. When you
select LAPB RFC 1490, the switch adds an 8-byte multiprotocol header to each LAPB
frame being encapsulated.
For encapsulating X.25 packets for transmission to a PE or X.25 FRE card,
Newbridge recommends that you select LAPB Annex G.
(400)
25.10-9


NNP 95-2035-01-00-B
To configure encapsulation circuit parameters

FRAME_SIZE
ENCAP_TYPE
THRESHOLDS
X.25_PKT_SZ
T_HDLC
<pkt_size>
<frame_size>
LAPB_1490 LAPB_ANNXG T_HDLC
ACT
SCT
MCT
<act>
<sct>
<mct>
SK000193
where
pkt_size is the number of octets (16, 32, 64, 128, 256, 512*, 1024, 2048 or 4096)
frame_size is the number of octets (16 to 4472)
act is 1 to 64 kbytes (4*)
sct is 1 to 100% (80*)
mct is 1 to 100% (50*)
25.10.5
Connecting Encapsulation Circuits

The required connections depend on whether the encapsulation circuit is a
super-rate or subrate circuit.
To connect super-rate encapsulation circuits

You connect super-rate encapsulation circuits in two steps, as shown in
Figure 25.10-6. The numbers in the figure correspond to the steps in the procedure.
25.10-10
(400)

NNP 95-2035-01-00-B

Figure 25.10-6: Connections for Super-rate Encapsulation Circuits

36XX MainStreet shelf
DCC or
PRI card
FRS card
Frame
relay
network
m x n x 8 kb/s
1
HDLC device
= Frame stream circuit
= Data link connection identifier
= Data or primary rate interface circuit
= Number of DS0s (1 to 31)
= Frame relay encapsulation circuit
= Transport bandwidth (1 to 8)
8037
1.
From the Control card NMTI, connect the super-rate encapsulation circuit to a
data or primary rate interface circuit:
CONFIG CONNECT <sn-ccl> TO_CIRCUIT <sn-cc2> PROCEED
where
sn-cc1 is the FRS slot number and encapsulation circuit number
sn-cc2 is the data or primary rate card slot number and circuit number
2.
From the FRS NMTI, connect the super-rate encapsulation circuit to a frame
stream-DLCI:
CONFIG CONNECT <cc> or <Scc-dlci> TO <cc> or <Scc-dlci>
where
cc is the encapsulation circuit
Scc-dlci is the frame stream circuit (1 to 31) and a DLCI (16 to 1007)
Note
See section 25.8.2 for information about setting the class-of-service parameters for
DLCs.
To connect subrate encapsulation circuits

You connect subrate encapsulation circuits in three steps, as shown in
Figure 25.10-7. The numbers in the figure correspond to the steps in the procedure.
(400)
25.10-11


NNP 95-2035-01-00-B
Figure 25.10-7: Connections for Subrate Encapsulation Circuits

DCC or
DNIC
FRS card
Frame
relay
network
3
1.2 to 56 kb/s
1
2
HDLC device
= Data interface circuit

= Rate adapted circuit
8038
1.
From the Control card NMTI, connect the subrate encapsulation circuit to a rate
adaption circuit:
CONFIG CONNECT <sn-SRcc> TO_CIRCUIT <sn-cc> PROCEED
where
sn-SRcc is the FRS slot number and subrate encapsulation circuit number
sn-cc is the FRS slot number and rate adaption circuit number
2.
From the Control card NMTI, connect the rate adaption circuit to a data
interface circuit:
CONFIG CONNECT <sn-ccl> TO_CIRCUIT <sn-cc2> PROCEED
where
sn-cc1 is the FRS slot number and rate adaption circuit number
sn-cc2 is the data interface slot and circuit number
3.
From the FRS NMTI, connect the subrate encapsulation circuit to a frame
stream-DLCI:
CONFIG CONNECT <SRcc> TO <Scc-dlci>
where
SRcc is the subrate encapsulation circuit
25.10-12
(400)

NNP 95-2035-01-00-B

Note
DLCs.
(400)
25.10-13

NNP 95-2035-01-00-B
25.11

Switched Access to Frame Relay

PVCs
This chapter describes how to configure switched access to frame relay PVCs using
the T1 signalling termination feature.
25.11.1
Understanding Switched Access to Frame Relay PVCs

Support for switched access to frame relay PVCs allows service providers to bridge
their ISDN and switched 56 networks to a Newbridge frame relay network (see
Figure 25.11-1). The 36120 MainStreet system provides an interworking function
between the frame relay network and Nortel DMS-100 or AT&T 5ESS CO switches,
which support ISDN and switched 56 access.
Figure 25.11-1: Switched Access to Frame Relay PVCs
AB Digital
Signalling
ISDN
Central office
(DMS-100 or
5ESS) switch
T1 card
(single/dual)
FRE card
Public
Frame Relay
Network
SDS-56
36120 MainStreet
Interworking Function
7976
In the case of ISDN access, data terminals use Q.931 signalling to access the CO
switch. The maximum user information rate per access channel for interfacing to the
ISDN network is 64 kb/s. The CO switch terminates the Q.931 signalling, and based
on the called number, selects a T1 DS0 on the trunk from its hunt group. The switch
initiates a call on the T1 DS0 using E&M signalling.
The 36120 MainStreet system terminates the T1 E&M signalling at a T1, Dual T1 or
Dual T1-2 card, and returns signalling to the CO switch to indicate that the trunk is
in use. The T1 DS0 is cross-connected to a frame stream on an FRS, FRE or PE card.
The frame stream is configured to support all PVCs required to allow frame relay
traffic to access the remote host.
(400)
25.11-1


NNP 95-2035-01-00-B
Example configuration
Figure 25.11-2 shows an example configuration. The interface speed between the CO
switch and the 36120 MainStreet interworking function is in increments of n 8 kb/s
(where n is 1 to 7), up to 1.536 Mb/s. Since the interface is a channelized 1.544 Mb/s
voice trunk, the number of hunt groups supported is dependent upon the
capabilities of the CO switch. This number can range from 1 DS0 to 24 DS0s per T1
link, or 24 n, where n is the number of T1 links.
Figure 25.11-2: Switched Access over ISDN or Switched 56 Networks
T/A or
SDS-56 DSU
CPE
device
T1_CSU
Router
RS-232
BRI or
switched 56
ISDN
or SDS-56
network
Public
frame relay
network
T1 D4_JB7
36120 MainStreet
node
Interworking
function
D
T
1
F
R
E
A1 A3
T
1
T1 ESF_B8ZS
A7
D F
T R
1 E
A1 A2
D
T
1
A8
Public
frame relay
network
Router
T1_CSU
7975
At point A in the figure, the frame streams are configured to run LMI Network
protocol. In the frame relay backbone network (between points B and C), the frame
streams use Annex D Bidirectional.
At point A, DLCIs are configured to match the DLCIs transmitted over the access
lines. Each of the access lines must use an identical DLCI to represent each distinct
host to simplify the end terminal configuration. PVCs are configured from each
access DS0 to all allowed hosts.
25.11-2
(400)

NNP 95-2035-01-00-B

T1 Signalling Termination
Newbridge support for switched access to frame relay PVCs is implemented
through a feature called T1 Signalling Termination. This feature enables T1, Dual T1,
and Dual T1-2 Line Interface modules to support AB (for D4 framing) and ABCD (for
ESF Framing) voice signalling response codes utilizing robbed bit signalling on a
DS0 basis.
This signalling option provides T1 termination for frame relay access to frame
stream circuits (on FRS, FRE and PE cards) and rate adaption circuits (on FRS cards
only). When configured for signalling termination, T1, Dual T1 and Dual T1-2 card
circuits respond to E&M signals by sending on- and off-hook signalling to the switch
that originated the E&M signals (for example, a DMS-100 or 5ESS).
Newbridge system support

Table 25.11-1 lists the systems and applications required to support T1 Signalling
Termination.
Table 25.11-1: Support for T1 Signalling Termination
System or Application
Release
Comments
1115-H2 or higher
D115-H2 or higher
Q115-H2 or higher
Supports only FRS cards
Craft Interface
PBB116F2.00 or
higher
PC version
Craft Interface
SBB116F2.01 or
higher
Sun version available with 4602 MainStreet

Intelligent NetworkStation Release
SAE315-H1-00 or higher
Central office switch requirements

Newbridge supports switched access to frame relay PVCs from DMS-100 and 5ESS
CO switches. The CO switches must meet the following criteria.
The T1 digital interface between the DMS-100 or 5ESS and the Newbridge IWF
must support the E&M protocol using AB(CD) bits, as documented in the
signalling specification AT&T Publication #43801. Only the A bit is monitored for
status, but the CD bits match the AB values for ESF T1 lines.
The DMS-100 or 5ESS must perform all ISDN protocol requirements, hunt group
functionality, call blocking, screening and security if required, and PVC
validation and authentication.
The DMS-100 or 5ESS must provide the protocol conversion required to connect
ISDN or switched 56 access lines to T1 digital trunks.
(400)
25.11-3


NNP 95-2035-01-00-B
Limitations and restrictions

The following limitations and restrictions apply.
T1 signalling termination is not supported on DS1 circuits running on DS-3 cards
25.11.2
on 3645 MainStreet systems.

Signalling termination is not supported on E1 cards.
Timeouts for call clearing on access DS0s are not supported.
Authentication prior to call request acceptance is not supported. Call blocking,
screening and security must be performed by the CO switch. The 36120
MainStreet system assumes that if the proper voice signalling protocol is
observed, the calling party is authorized to seize the trunk, and the DLCI
programmed into the calling party's frame relay device determines the endpoint
of the connection.
Hunt group capability is only supported on the CO switch. The hunt groups
supported on the CO switch block calls to DS0s when the calling party is not
authorized to call the number. Each DS0 in the hunt group can have multiple
DLCIs with different endpoints to various applications. The calling party's
programmed DLCI determines which endpoint application they access (Internet,
campus LAN, and so forth). The PVCs are all nailed up in the 36120 MainStreet
system, and connect to nailed-up PVC connections in the public frame relay
network.
PVC validation and security is not supported. To maximize the security of the
customer's connection, all authentication mechanisms must be implemented at
network ingress on the CO switches. This approach is the only network
architecture that delivers consistent and predictable performance.
Suppressing LMI alarms on a frame stream basis is not supported. LMI alarms
resulting from user disconnects can be suppressed by suppressing all PVC
alarms or setting the protocol on the frame stream to None. In the latter case,
management of the link is lost while the call is in progress.
Protocol conversion for circuit-mode data to frame relay interworking is not
supported. The 36120 MainStreet system does not support protocol conversion
for circuit-mode data to frame relay interworking. This can be accomplished
using the Newbridge access devices to interface to the 36120 MainStreet system.
Interaction between digital switching and the PVC status is not supported. A
user connected to a PVC that becomes inactive is notified; however, the resources
affiliated with that PVC may not be automatically freed up by the CPE. In
addition, other users may be assigned the inactive PVC.
Configuring Switched Access to Frame Relay PVCs

This section describes the configuration steps you must perform at the 36120
MainStreet system.
25.11-4
(400)

NNP 95-2035-01-00-B

To provision switched access

1.
Configure a slot for a T1 card and set up the T1 link.

CONFIG SLOT <sn> TYPE PRIME_RATE
T1
DUAL_T1
DUAL2_T1
SK000194
2.
Configure a T1 circuit for signalling termination and ensure RBS is on.

CONFIG CIRCUIT <sn-[link]-cc>
FUNCTION
MORE
RBS_ON
SIG_TYPE
TERMINATE
PROCEED
SK000195
Note
For a super-rate bundle (multiple DS0s), configure the master (primary) circuit for
signalling termination and RBS. Signalling information is carried on this circuit.
3.
Configure the interface speed and transport bandwidth on a frame stream

circuit to match that of the T1 circuit or super-rate bundle.
I/F_SPEED
TRANSP_BW
<speed>
<bandwidth>
SK000196
where
speed is 8 to 1536 kb/s
bandwidth is 1 to 7
(400)
25.11-5


NNP 95-2035-01-00-B
Note
Calculate the interface speed using the formula m n 8 kb/s, where m is the
number of DS0s and n is the transport bandwidth.
4.
Connect the T1 circuit to the frame stream circuit.

CONFIG CONNECT <sn-[link]-cc> TO_CIRCUIT <sn-cc>
PROCEED
Note
T1 circuits configured for signalling termination can be connected only to frame

stream circuits. All other connections are blocked.
5.
Configure the required frame relay PVCs.

Note
The DLCIs and LMI parameters configured on the frame stream used in step 3 must
match those configured at the user devices.
25.11-6
(400)

NNP 95-2035-01-00-B
26. Frame Relay SVC Service

NNP 95-2035-01-00-B
26.1
26.1 Frame Relay Switched Virtual Circuits

Frame Relay Switched Virtual

Circuits
This chapter provides an overview of frame relay SVC functionality, and a
configuration summary with a configuration example.
26.1.1
Overview of Frame Relay SVCs

SVCs on the FRE card of the 36120 MainStreet PTX establish and release frame relay
connections across a network on demand through signalling. SVCs bring
cost-effective frame relay support to those users who require connections on
demand.
Figure 26.1-1 shows an example of a frame relay SVC network. The FRE card
communicates with the user and network through E1 or T1 cards. Frame streams
link the DTE to the FRE card which is part of the frame relay network. An FRE card
supports a maximum of 62 frame streams.
The UNI protocol allows for establishing, maintaining and clearing of network calls
at the user-network interface. The NNI protocol allows for establishing, maintaining
and clearing of network calls at the network-network interface. Both protocols
ensure that all of the network equipment can communicate effectively using frame
relay SVCs, passing signalling information from DTE to an FRE switch, from an FRE
switch to an FRE switch, and from network to network.
Figure 26.1-1 also shows a logical view of frame relay SVCs within a network. Each
frame stream carries one signalling channel and multiple data channels. The
signalling channel carries the signalling messages that are used to establish,
maintain and tear down SVC calls.
Frame Relay SVC Service
(400)
26.1-1


NNP 95-2035-01-00-B
Figure 26.1-1: A Frame Relay SVC Network

36120 MainStreet PTX
DTE
UNI
User 1
DTE
Frame relay
SVC
access
device
T1 or
E1 card
Frame relay
SVC
access
device
User 2
SVC
signalling
channel
Frame
streams
SVC
data
channels
FRE card
T1 or E1 card
NNI
Frame relay
network
9875
Physical requirements
Frame relay SVCs require a physical configuration as shown in Figure 26.1-1. The
user device requires a physical connection to a frame relay SVC access device or a
router that manages frame relay SVC connections. The frame relay SVC access
device requires a physical connection to an interface card, such as an E1 or T1 card,
with the same physical and electrical characteristics as the frame relay SVC access
device or router. The 36120 MainStreet PTX requires at least one FRE card with SVC
software installed.
Call processing
Figure 26.1-2 summarizes the functionality of frame relay SVC on an FRE card. Each
user communicates with its DTE (a router or another frame relay SVC access device).
The DTE communicates with the FRE card on a frame stream through the E1 or T1
card. The FRE card processes each call based on the functionality incorporated in its
software.
26.1-2
(400)

NNP 95-2035-01-00-B

Figure 26.1-2: Frame Relay SVC Functionality
36120 MainStreet PTX

User 1
(1-613-591-3601)
User 4
(1-613-591-3606)
DTE
S1
T1 or E1
card
T1 or E1
card
S2
DTE
FRE
Signalling channels
User management
Routing
Connection management
Diagnostics
User 2
(1-613-591-3602)
User 3
(3020-26661010)
S3
DTE
T1 or E1
card
Legend:
S
SVC data channel
Signalling channel
Frame stream
9882
Signalling channel management defines the operations performed at the UNI and
NNI. Signalling channel management includes addressing according to E.164 and
X.121 (national and/or international) numbering plan format and a set of attributes
that control the condition and configuration of the signalling channel. Chapter 26.2
provides the details on signalling channel management.
Call statistics can be collected with each signalling channel. Chapter 34.4 provides
details on the statistics collected.
(400)
26.1-3


NNP 95-2035-01-00-B
User management defines the characteristics of a user device for which a subscribed
service is provided. The characteristics of the user, such as an address, are recorded
in a local user table on the FRE card. User screening ensures that every call received
is associated with a user recorded in the table. Chapter 26.3 provides the details of
user management.
Connection management software controls the method in which data connections
are established and released when SVC calls are processed. Chapter 26.4 provides
the details of connection management.
The routing function routes calls by selecting the path through the network. Calls
can be routed to a local user over a UNI or to a remote user over an NNI. The routing
function uses a static routing table which consists of a local user table and a remote
address table, both maintained by the administrator.
The remote address table consists of switch prefix addresses, and primary and
alternate routes to the destination address of the route user. The table is used to route
calls over a frame relay SVC network. Figure 26.1-3 shows a large network.
Nodes with the same address prefix cluster together inside a group. For example,
nodes with the user prefix of e1614 reside in group A. Each node has a local address
table and an associated remote address table.
User 1 places a call to user 2 with a destination address of e131522. The FRE at node
A1 looks first in its local user table. If the node does not find a match, it looks at its
remote address table and finds a best address match of e1315 using S1 as the primary
path and S2 as the alternate path. The call is routed to node A3, which has a remote
address table similar to A1. The best address match is over primary path S1(N) to
group D. Similar actions take place at D1. When the call arrives at D2, it finds a best
match in its local user table and forwards the call to user 2.
If the call was not successfully routed to user 2, the routing function could
implement alternate path routing, crankback or call clearing. Chapter 26.5 describes
these functions and routing in more detail.
Diagnostic tools, such as route tracing, frame relay ping and a message traffic
recorder are available through NMTI. Chapter 33.6 describes these diagnostic tools.
26.1-4
(400)

NNP 95-2035-01-00-B

FRE
FRE
FRE
Figure 26.1-3: Routing through a Frame Relay SVC Network
Node B3
Node B4
Node D3
S2
S3
S1
FRE
FRE
FRE
FRE
e13152
Node B2
Node B1
Node D1
Node D2
Group
B
Group
D
S1
S1(N)
e1613
e1315
S2(N)
User 2
e131522
e16141
S3
FRE
Node A3
S1
FRE
FRE
e16143
Node C4
Node C3
e16142
FRE
FRE
FRE
FRE
S2
Node A1
Node A2
Node C1
Node C2
Group
A
Group
C
e1614
e1504
User 1
Local User Table for Node D2
Remote Address Table for Node A1

Address
e1504
e1315
e1613
e16143
e16142
Primary Alternate
Route
Route
S2
S1
S2
S1
S2
S1
S2
S1
S2
S1
Name
Address
Frame
Stream
User 1
User 2
User 3
e131521
e131522
e131523
S1
S1
S2
9881
(400)
26.1-5

26.1.2

NNP 95-2035-01-00-B
Configuration Summary
This section describes the general process for setting up SVC calls for nodes at the
edge of the network and nodes within the network. Section 26.1.3 provides a
configuration example using this general process.
Setting up nodes at the edge of the network

On the Control card:
Insert and configure the card types.

Configure the transport circuit parameters where necessary for an aggregate
card.
Cross-connect the frame streams to the aggregate circuits.
On the FRE card:
Assign the node prefix.

Configure the new users.
Create an address.
Assign a frame stream for data communication.
Configure a remote address.
Create an entry in the remote address table.
Assign a primary and an alternate route.
Configure the signalling.
Configure the UNI protocol on a profile.
Assign a profile to the UNI stream.
Connect and enable a signalling channel on the UNI frame stream.
Configure the NNI protocol on a profile.
Select a profile for the NNI frame stream.
Connect and enable a signalling channel on the NNI frame stream.
Setting up nodes within the network
On the Control card:
Insert and configure the card types.

Configure the transport circuit parameters where necessary for an aggregate
card.
Cross-connect the frame streams.
26.1-6
(400)

NNP 95-2035-01-00-B

On the FRE card:
Assign the node prefix.

Create an entry in the remote address table.
Assign a primary and an alternate route.
Configure the signalling.
Configure a profile for the NNI protocol.
Select a profile for the NNI frame stream.
Connect and enable a signalling channel on the NNI frame stream.
26.1.3
Frame Relay SVC Configuration Example

The sample network, shown in Figure 26.1-4, is used to illustrate the configuration
necessary to allow user A to call user B. The illustration shows the dynamic
connections within the frame relay network.
Each set of cards represents a card configuration in a 36120 MainStreet node.
(400)
26.1-7


NNP 95-2035-01-00-B
Figure 26.1-4: A Sample Frame Relay SVC Network
FRAD
e1594
DT1
RS-232
FRE
DT1
User A
Address
6135913601
e1416
User B
Address
4162321415
Primary ro
B
route to
Alternate
443
from e1
ute to B fr
ary
from route
e14 to B
43
Prim
Router
FRE
DT1
DE1
FRE
B T1 or E1
to
ute 3
ro
te 161
e
na
ter rom
f
Al
e1443
RS-232
DT1
DE1
T1 T1
or E1
FRE
V.35
e1613
T1 or E1
Router
UNI
om e180
Pr
UNI
Primary route to B
from e1594
e to B
Alternate rout
from e1594
im
ar
fro y rou
m
e1 te to
61
3 B
NNI
DE1
FRE
T1 or E1
e1809
9993
Figure 26.1-5 provides a map of the circuit-switched connections for the network in
Figure 26.1-4.
26.1-8
(400)

NNP 95-2035-01-00-B

Figure 26.1-5: A Map of Circuit-switched Connections
A-2 1
1
B-1 2
2
User A
e1594
Slot
DT1
e1613
FRE
A-1
DT1
2
2
RS-232
1
2
User B
A-1
1
1
A-1
Slot
1
2
A-1
B-1
DT1
FRE
2
e1443
DE1
T1 or E1
1
A-1
Slot
FRE
DE1
4
RS-232
T1 or E1
T1 or E1
FRE
e1416
B-1
DT1
V.35
Slot
2
2
B-1
1
1
1 , 2 , 3 , 4 = frame streams
A-1
B-1
FRE
e1809
DE1
T1 or E1
Slot
5
9992
(400)
26.1-9


NNP 95-2035-01-00-B
The following procedures provide the steps to set up the SVC calls for nodes e1613,
e1594 and e1416, using the information in the previous illustrations.
To configure the parameters for node e1613 through the Control card
1.
Configure the cards as present.
2.

i.
1-1 to 2-1 (V.35 to FRE).
ii.
2-2 to 3-2 (FRE to T1).
iii. 2-3 to 4-A-1 (FRE to DE1).

iv.
2-4 to 4-B-1 (FRE to DE1).
To configure the parameters for node e1613 through the FRE card
1.
Configure the node prefix to e1613. See section 26.3.2.
2.
Configure a new user with the name of A. See section 26.3.3 for details.
3.
i.
Create a local address of e+5913601.
ii.
Assign user A to frame stream 1.
Configure a remote address. See section 26.5.2.

i.
Create a destination address of e1416 (that of user B).
ii.
Assign a primary route of stream 2 to user B.
iii. Assign an alternate route of stream 3 to user B.
26.1-10
(400)

NNP 95-2035-01-00-B
4.

Establish the signalling channels.

i.
Ensure the profile for FRF.4 is configured. See section 26.2.4.
ii.
Connect a signalling channel on UNI frame stream 1. See section 26.2.2.
iii. Select profile 1 for frame stream 1.

iv.
Enable the administrative status of the signalling channel for frame

stream 1. See section 26.2.3.
v.
Configure profile 2 to use protocol X.76.
vi.
Connect a signalling channel on NNI frame stream 2.
vii. Select profile 2 for frame stream 2. See section 26.2.3.

viii. Enable the administrative status of the signalling channel for frame
stream 2.
ix.
x.
Select profile 2 for frame stream 3.
xi.

stream 3.
xii. Connect a signalling channel on NNI frame stream 4.

xiii. Select profile 2 for frame stream 4.
xiv. Enable the administrative status of the signalling channel for frame
stream 4.
1.
2.

i.
1-A-2 to 2-1 (DT1 to FRE).
ii.
1-B-1 to 2-2 (DT1 to FRE).
iii. 2-3 to 4-1 (RS-232 to FRE).

iv.
2-4 to 5-A-1 (FRE to DT1).
1.
Configure the node prefix to e1594.
(400)
26.1-11

2.

NNP 95-2035-01-00-B

i.
Create a destination address of e1416 (that of user B).
ii.

iv.
Create a destination address of e16135913601 (that of user A).
v.
Assign a primary route of stream 1 to user A.
vi.
Assign an alternate route of stream 4 to user A.
3.
4.

i.
ii.

stream 1.
iii. Connect a signalling channel on NNI frame stream 2.

iv.
Select profile 2 for NNI frame stream 2.
v.

stream 2.
vi.
Connect a signalling channel on frame stream 3.
vii. Select profile 2 for frame stream 3.

stream 3.
ix.
x.
xi.

stream 4.
1.
2.

i.
1-A-1 to 5-3 (DT1 to FRE).
ii.
1-B-1 to 5-4 (DT1 to FRE).
iii. 2-1 to 5-2 (E1 to FRE).

iv.
26.1-12
4-1 to 5-1 (RS-232 to FRE).
(400)

NNP 95-2035-01-00-B

1.
Configure the node prefix to e1416.
2.
Configure a new user with the name of B.
3.
i.
Create a local address of e+2321415.
ii.
Assign user B to frame stream 1.

i.
Create a destination address of e1613 (that of user A).
ii.

4.

i.
Ensure the profile for FRF.4 is configured.
ii.
iii. Connect a signalling channel on UNI frame stream 1.

iv.

stream 1.
v.
vi.
vii. Select profile 2 for frame stream 2.

stream 2.
ix.
x.
xi.

stream 3.
xii. Connect a signalling channel on NNI frame stream 4.

xiii. Select profile 2 for frame stream 4.
xiv. Enable the administrative status of the signalling channel for frame
stream 4.
The other nodes in the network are configured in a similar manner to complete the
alternate routing path from user A to user B, if the primary route cannot be used.
(400)
26.1-13

NNP 95-2035-01-00-B
26.2
26.2 SVC Signalling Channel Management

SVC Signalling Channel

Management
This chapter describes SVC signalling channel management including signalling
profiles and protocols, the signalling channel attributes and signalling channel
establishment.
26.2.1
Understanding Signalling Channel Management

A signalling channel is a frame relay data link connection which carries SVC
signalling messages between a DTE and a 36120 MainStreet PTX, or between two
36120 MainStreet nodes in a network. The signalling messages establish, manage,
and tear down SVC calls in the frame stream in which the signalling channel is
carried.
Only one signalling channel is available for each frame stream in a UNI or an NNI
in a frame relay SVC network. Each signalling channel has a signalling profile
assigned to it. The signalling profile governs the exchange of messages over the
signalling channel.
Before a signalling channel and its associated frame stream can come into service,
the signalling channel must be connected to the SVC software component of the FRE
card.
26.2.2
Signalling Channel Connection and Disconnection

A signalling channel and its associated frame stream can be configured and used
once the signalling channel is connected to the SVC software component on the
switch. This indicates that the frame stream can only be used for SVCs and not PVCs.
The software automatically designates DLCI 0 to establish the connection.
Note
SVCs and PVCs cannot be mixed on the same frame stream.
Figure 26.2-1 shows the default configuration for the parameters when a signalling
channel is first connected. See section 26.2.3 to change any of the signalling channel
parameters from the defaults. The parameters for the message traffic recorder are
described in section 33.6.2. CIR and the booking factor are described in section 26.4.3.
(400)
26.2-1


NNP 95-2035-01-00-B
Figure 26.2-1: Default Configuration for Signalling Channel Parameters

FRE
Stations:nn
P412-H1-00
Toronto:A
Alarms:1
11-May-1997
8:35a
Signalling Channel on Frame stream : Backplane stream 1

-----------------------------------------------------------------------------Signalling Channel Name
:
Signalling Profile #
: 1
Signalling Profile Name
:
Committed Information Rate (bps)
: 0
Booking Factor (%)
: 100%
Administrative Status
: Disabled
Operational Status
: Down
Strip Switch Prefix
: No
DLCI values are
: taken from the low end
Message Traffic Recorder (MTR)
: not connected
MTR recording method
: Fixed
MTR messages recorded
: No messages
CONFIG SVC SIGNALLING CHANNEL S1

1-SHOW_LIST
6-CHG_NAME
2-CONNECT
7-MORE...
3-DISCONNECT
8-CANCEL
4-ADMIN_STAT
9-QUIT
5-SIG_PROFIL
0-
Signalling channels can be disconnected from the SVC software component. Upon
disconnection, the following events occur.
All calls on the frame stream associated with the signalling channel are cleared.
All statistical counters relating to the signalling channel are cleared.
Note
When the SVC software component is connected, the LMI protocol automatically
changes to no protocol.
To view and connect or disconnect a signalling channel

CONFIG MORE SVC SIGNALLING CHANNEL <Scc>
CONNECT
DISCONNECT
SK000942
where Scc is a frame stream circuit between S1 and S62
26.2-2
(400)

NNP 95-2035-01-00-B
26.2.3

Signalling Channel Parameters

The signalling channel parameters define the configuration of the signalling
channel. The parameters indicate the current status of the signalling channel and the
associated call statistics. Section 34.4.1 provides information on the statistics
collected.
The following sections describe the parameters of the signalling channel.
Name
The signalling channel can be assigned a name of 0 to 25 characters, including A to
Z, a to z, 0 to 9, - (hyphen), +, &, /, %, and : (colon).
Signalling channel administrative status

The administrative status indicates the state of the signalling channel as enabled or
disabled. If the status is set to enabled, and the operational status is up, then the
signalling channel is ready to transmit and receive signals.
If the administrative status is set to disabled, the switch brings the operational status
of the signalling channel to down. Any calls associated with the signalling channel
are cleared.
Signalling channel operational status

The operational status indicates the operating state of the signalling channel as
either up or down. If the status is up, the physical, link and network layers are
operational; they can send and receive signalling messages if administrative status
is enabled. If the status is down, one or more of the physical, link, or network layers
are not operational and cannot send or receive signalling messages.
The operational status is read-only; it cannot be set.
Caution
If the operational status changes to down, the switch automatically clears all calls on
the associated frame stream.
Associated signalling profile attribute

The associated signalling profile attribute indicates which signalling profile is to be
used by the signalling channel. The number of profiles ranges from 1 to 10 with a
default of 1.
(400)
26.2-3


NNP 95-2035-01-00-B
When the administrator changes an associated signalling profile number, the switch
performs the following actions:
1. All existing SVC calls are cleared.
2. The operational status changes to down.
3. The signalling profile changes.
4. The operational status changes to up.
Prefix passing or stripping

The switch prefix, which is the address of the FRE card, can be passed or stripped
from the called party numbers that are presented to the DTE connected to the frame
stream.
Figure 26.2-2 shows the configuration and status information for all currently
connected signalling channels. The PAGE_UP and PAGE_DOWN softkeys allow
navigation through the frame streams in decreasing and increasing order,
respectively.
Figure 26.2-2: Display Screen for Signalling Channels
FRE
Stations:nn
FS
Name
P412-H1-00
Toronto:A
Alarms:1
11-May-1997
8:35a
Admin
Oper
Profile MTR
Status
Status
#
--------------------------------------------------------------------S1
Disabled Down
1
S2
not connected
S3
not connected
S4
not connected
S5
not connected
S6
not connected
S7
not connected
S8
not connected
S9
not connected
S10
not connected
CONFIG SVC SIGNALLING CHANNEL 1
1-PAGE_UP
6-
26.2-4
2-PAGE_DOWN
7-
38-CANCEL
(400)
49-QUIT
50-

NNP 95-2035-01-00-B

To set the signalling channel parameters

CONFIG MORE SVC SIGNALLING CHANNEL <Scc>
SHOW_LIST
PAGE_UP
ADMIN_STAT
PAGE_DOWN
SIG_PROFIL
CHG_NAME
<profile_no.>
<name>
MORE
ADMIN_UP ADMIN_DOWN*
STRIP_PREF
PASS_PREF*
SK000941
where
Scc is a frame stream circuit between S1 and S62
profile_no. is a number from 1 to 10, inclusive
name is 0 to 25 characters, including A to Z, a to z, 0 to 9, - (hyphen), +, &, /, %, and : (colon)
26.2.4
Signalling Profiles
A set of attributes forms the signalling profile. These attributes govern the exchange
of messages within the signalling channel.
Each switch contains a maximum of 10 profiles; each profile can be used by one or
more signalling channels. The following sections provide a description of the
attributes.
Profile name
Each profile can be assigned a name consisting of 0 to 25 characters, including A to
Z, a to z, 0 to 9, - (hyphen), +, &, /, %, and : (colon). The characters assigned to the
profile need not be unique because the profile name is only an aid to the network
administrator and has no intrinsic meaning to the switch.
Signalling protocol attribute

The signalling protocol defines the types of signalling messages that control the
establishment, management and tear down of SVC calls.
The signalling protocols are ITU-T X.36, FRF.4 or ITU-T X.76. UNI uses either the
X.36 or FRF.4 protocol. NNI uses the X.76 protocol. The default is FRF.4.
(400)
26.2-5


NNP 95-2035-01-00-B
To set the profile name and its protocol

CONFIG MORE SVC SIGNALLING PROFILES <profile_no.>
NAME
PROTOCOLS
<name>
X.36
FRF.4*
X.76
SK000938
where
profile_no. is a number between 1 and 10, inclusive
name is 0 to 25 characters, including A to Z, a to z, 0 to 9, - (hyphen), +, &, /, %, and : (colon)
Network layer protocol timers

Each signalling protocol has timers that govern the performance of the network
layer (layer 3). Table 26.2-1 lists each timer with a description, its valid range, a
default time, and the protocol to which the timer applies.
Table 26.2-1: Network Layer Protocol Timers
Timer
Description
Range
Default
Protocol
T303
Retry timer for a setup message.
1 to 500 s
4s
X.36, FRF.4, X.76
T305
Retry timer for a disconnect message.
1 to 500 s
30 s
X.36, FRF.4
T308
Retry timer for a release message.
1 to 500 s
4s
X.36, FRF.4, X.76
T310
Retry timer for a call proceeding

message.
1 to 500 s
35 s
X.36, FRF.4, X.76
T316
Retry timer for a restart message.
1 to 500 s
120 s
X.36, X.76
To set the network layer timers

CONFIG MORE SVC SIGNALLING PROFILES <profile_no.> LAYER_3
T303
T305
T308
T310
T316
<time>
SK000939
where
profile_no. is a number from 1 to 10, inclusive
time is a value from 1 to 500 s
26.2-6
(400)

NNP 95-2035-01-00-B

Q.922 link layer protocol parameters

The Q.922 link layer (layer 2) parameters govern the message transfer. Table 26.2-2
lists the timers and counters with valid ranges and defaults.
Table 26.2-2: Link Layer Timers and Counters
Parameter
Description
Range
Default
Timer T200
The duration before retransmission of

the message occurs.
1 to 30000 ms
1500 ms
Timer T203
The maximum duration allowed without

frames being exchanged.
1 to 500 s
30 s
Counter N200
Counts the number of retransmissions

for T200.
1 to 30
Counter N201
Counts the maximum number of octets

in an information field.
16 to 4472 octets
1600 octets
To set the link layer timers and counters

CONFIG MORE SVC SIGNALLING PROFILES <profile_no.> LAYER_2
T200
N200
N201
T203
<time1>
<count>
<octets>
<time2>
SK000940
where
time1 is from 1 to 30000 ms
count is a number from 1 to 30
octets is from 16 and 4472 octets
time2 is from 1 to 500 s
(400)
26.2-7

NNP 95-2035-01-00-B
26.3
26.3 SVC User Management

SVC User Management

This chapter describes user management including the switch address prefix, user
parameters and user screening.
26.3.1
Understanding User Management

A user refers to a user device for which the 36120 MainStreet PTX is providing a
subscribed service.
Switch address prefix identifies each FRE card in a network. A user configuration
identifies each local user attached to the FRE card and provides a point of access.
User screening determines the admissibility of a call.
26.3.2
Switch Address Prefix Management

Switch address prefix management assigns common address prefixes to a switch
such as an FRE card, for reference by a user configuration.
Address prefix management allows for one E.164 and one X.121 address prefix to be
set independently for each FRE card. It is the responsibility of the administrator to
ensure that both prefixes are in international format which guarantees proper
routing of SVC calls.
Absolute and relative addresses

Addresses using a prefix are relative addresses. Those without a prefix are absolute
addresses.
Relative address format is the preferred format because all addresses dependent on
a prefix are adjusted automatically when the switch prefix is changed.
Any addresses in absolute address format are used in special cases and do not
change when a switch prefix is changed.
(400)
26.3-1


NNP 95-2035-01-00-B
Prefix types
The two switch address prefixes are:
E.164, an addressing plan for PSTN and ISDN
The value is a string of 1 to 11 digits preceded by an e, with a default of E1.

X.121, the public data network addressing plan
The value is a string of 1 to 11 digits preceded by an x, with a default of X2.
When a switch address prefix is changed from one value to another value, relative
addresses change to the new value. Calls currently using the old value remain
connected using the old value until the call is cleared by the calling DTE.
To assign and view the prefix value

CONFIG MORE SVC SYSTEM PREFIX_MGT
E.164
X121
<value>
SK000943
where value is between 1 and 11 digits, preceded by an x for X.121 and an e for E.164
26.3.3
User Configuration
A user configuration contains a number of attributes which define a set of privileges
and restrictions, and the identity and access point of each attached user device. A
user configuration can assist in the diagnosis of problems in a network. The
administrator creates and can view, add or delete user configurations. All user
configurations, up to a maximum of 200, are stored in software in a local user table.
The local user table contains information, such as the user name, address and
associated frame stream, that assists in user screening and in route determination.
Name
Each user can be identified by a name. It can be from 0 to 25 characters, including
A to Z, a to z, 0 to 9, - (hyphen), +, &, /, % and : (colon). The default is blank.
26.3-2
(400)

NNP 95-2035-01-00-B

User address
Each user can be identified by an address. An address may be an absolute or a
relative address. The default is derived from the CPSS address of the FRE card.
Absolute addresses have a numbering plan identification (e for E.164 or x for X.121)
plus a numerical portion of 1 to 19 digits where each digit is in the range of 0 to 9.
Example addresses are e16135913601 and x3104203981.
Relative addresses are only complete when the assigned switch prefix is substituted
for the switch prefix representation of e+ and x+. The resulting address must be at
least 1 digit and not greater than 19 digits after the switch prefix. The address must
be assigned in international format. For example, if the switch prefix is e1613591 for
E.164 and x3104 for X.121, e+3601 (a total of 11 digits) and x+213981 (a total of 10
digits) are valid addresses.
Physical access (frame stream)

The physical access identifies the frame stream through which the user is reached. A
user configuration references only one frame stream; however, a frame stream may
have multiple user configurations referencing it.
When multiple user configurations reference a common frame stream, each user
configuration must have a unique and complete address to avoid ambiguity in
identifying individual user configurations.
The physical access can be a frame stream from S1 to S62, with a default of unknown.
Default user
The administrator can assign a default user to each frame stream on the FRE card
when multiple user configurations reference the same frame stream. The default
user is used when no calling party IE is present in the setup message or when the
setup message provides a calling address which is not configured in the local
address table.
User administrative status

An administrative status can be assigned to each user configuration. The status can
be enabled (the default) or disabled. If the status is changed from enabled to disabled
on a user configuration with active calls, the calls are cleared.
User operational status

The operational status reflects the state of the frame stream used by the user. The
operational status can be up or down (the default) and is not configurable.
The operational status of a user changes to up if its administrative status is enabled
and the operational status of the associated signalling channel is up. The operational
status of a user is down if its administrative status is disabled and/or the operational
status of the associated signalling channel is down.
Figure 26.3-1 shows an example of several user configurations.
(400)
26.3-3


NNP 95-2035-01-00-B
Figure 26.3-1: User Configurations

FRE
Stations:nn
P412-H1-00
E.164 Prefix: E1102301
X.121 Prefix: X2102301
Toronto:A
Alarms:1
11-May-1997
8:35a
Frame
Admin/Op
Is
# Address
User Data
Stream
Status
Default?
------------------------------------------------------------------------------1 E1102301
E.164_Prefix
2 E+1234
Vancouver-10
S43
Enabled
No
3 E+3601
Vancouver-5
S11
Disabled
No
4 X2102301
X.121_Prefix
5 X+416284
User-A
S2
Enabled
No
CONFIG SVC USER SHOW_LIST
1-PAGE_UP
6-
2-PAGE_DOWN
7-
3-SHOW_ENTRY
8-CANCEL
49-QUIT
50-
To view one or all user configurations

CONFIG MORE SVC USER <Esc> SHOW_GROUP
PAGE_UP
PAGE_DOWN
SHOW_ENTRY
<entry_#>
SK000952
where entry_# is a number from the # column on the NMTI screen
26.3-4
(400)

NNP 95-2035-01-00-B

To set the user configuration parameters

CONFIG MORE SVC USER <address>
SHOW_LIST
STREAM
CHG_STATUS
NAME
<Scc>
MORE
<name>
ADMIN_UP
ADMIN_DOWN*
DELETE
DEFALT_ON
DEFALT_OFF
SK000951
where
address is an E.164 or X.121 address
Scc is a frame stream circuit from S1 to S62
name is from 0 to 25 characters, including A to Z, a to z, 0 to 9, - (hyphen), +, &, /, and : (colon)
26.3.4
User Screening
User screening ensures that every call request is associated with a user configuration
or a default user. When an incoming call request is received, the calling party IE is
checked against the local user table to determine the call admissibility.
Table 26.3-1 summarizes the user screening functionality.
Table 26.3-1: User Screening
Calling
Party IE
User
Configuration
Default User
Configured
No
n/a
Yes
A calling party IE is inserted into the setup message

with the address of the default user. The screening
indicator is set to Network Provided.
No
n/a
No
The call is rejected with cause value 21, Call Rejected.
Yes
No
Yes
The calling party IE is replaced with the default user

address. The screening indicator is set to Network
Provided.
Yes
No
No
The call is rejected with cause value 21, Call Rejected.
Newbridge
enhancement
Yes
Yes
n/a
The calling party IE of the incoming setup message is

passed with a screening indication of User Provided,
Verified and Passed.
Yes
Action
(400)
Standards
Compliant
Yes
Newbridge
enhancement
Yes
26.3-5

NNP 95-2035-01-00-B
26.4
26.4 SVC Connection Management

SVC Connection Management

This chapter describes how data connections are established and released when SVC
calls are processed.
26.4.1
Understanding Connection Management

Administrators use connection management software (referred to as the connection
manager) to control the way data connections are established and released when
SVC calls are processed. Figure 26.4-1 shows the various functions of connection
management and the following steps describe how each function operates.
1. On frame stream S1, a setup message is received. The routing algorithm of the
FRE decides that the message must be forwarded to frame stream S2.
2. Before the setup message is forwarded, the connection manager applies
connection admission control to determine if the requested data channel across
S1 and S2 can be established without affecting the quality of service on both
streams; allocates a DLCI for the data channel that crosses S2; and allocates a call
reference for the outgoing setup message.
3. On S2, a connect message is received. The connection manager establishes a data
channel across S1 and S2, and the FRE forwards the connect message to the
calling network.
4. On S1, the calling network decides to release the call by sending a release
message. The connection manager releases the data channel and the FRE
forwards the release message to the called network.
(400)
26.4-1


NNP 95-2035-01-00-B
Figure 26.4-1: Connection Management Functionality
User 1
S1
Frame
relay
SVC
access
device
Setup message
DLCI allocation
call reference allocation,
CAC
S1
Connect message
S2
FRE
Setup message
S2
FRE
Data cross-connection
S1
Connect message
S2
FRE
X
Release message
Legend:
Data disconnection
Release message
SVC data channel
Frame relay network
Signalling channel
Frame stream
Frame
relay
SVC
access
device
User 2
9876
In general, the process proceeds as follows.

1. Upon receiving a setup message, the connection manager determines if the data
connection requested by the user is acceptable.
2. If the connection is permitted, the software reserves DLCIs and frame stream
bandwidth for the requested CIR values.
3. Upon receiving a connect message, the software checks the frame size, CIR, Be
and Bc values in the connect message and compares them with the values in the
setup message.
If the values in the connect message exceed those in the setup message, the call
is released. If the values are equal or smaller, the call proceeds.
4. Upon receiving a disconnect or release message, the data channel for the call
disconnects.
26.4-2
(400)

NNP 95-2035-01-00-B

If the FRE card is reset, all SVC connections are released. If the operational status of
the signalling channel on a particular frame stream goes down, all calls that cross
that stream are disconnected.
The following sections describe connection management in more detail.
26.4.2
Allocation of Signalling Identifiers

After a setup message has been received by the FRE, signalling identifiers for the
DLCI, call reference and call identification must be allocated before the setup
message can be forwarded.
DLCI allocation
The connection manager allocates a DLCI to the incoming stream when a setup
message is received from a calling DTE.
The connection manager allocates a DLCI for the outgoing stream before the setup
message is forwarded. The connection manager keeps track of the used and unused
DLCIs within the available ranges. The range of DLCI values is 16 to 1007 for
backplane frame streams.
When a signalling channel carried over an NNI link has its administrative status
enabled, an automatic negotiation occurs between the FREs on either end of the link.
The negotiation determines which end allocates DLCIs for calls beginning at the
high end of the allowable range, and which end allocates DLCIs at the low end.
The negotiated allocation method used depends on the signalling protocol assigned
to the frame stream. For the X.36 and FRF.4 protocols, the default is to use the DLCI
values starting at the low end of the range. For the X.76 protocol, the default is to use
the negotiated DLCI. If the protocol is changed to X.76, the DLCI used is taken from
what was previously the default before the change was made.
The administrator can override the default allocation for each protocol. The options
are:
negotiated
The FRE uses the end of the DLCI range assigned to the signalling channel during
the negotiation process. This applies only to the X.76 protocol.
low
The FRE assigns DLCIs from the low end of the allowable range.
high
The FRE assigns DLCIs from the high end of the allowable range.
If the administrator changes the value from low or high to negotiated while the
signalling channel is in use, the FRE begins assigning DLCIs from the end of the
range assigned after the signalling channel was last enabled.
(400)
26.4-3


NNP 95-2035-01-00-B
Call reference allocation

Every setup message carries a call reference value that identifies to which SVC call
the message applies. A value is allocated by the software for every setup message
that is sent to a DTE or DCE.
Call identification allocation

When an FRE forwards a setup message from a UNI to an NNI link, it inserts a
unique call identification IE into the message. The call identification number is four
octets in length and is generated from:
the CPSS major number of the FRE card (10 bits)

the slot number of the FRE card (6 bits)
a 16-bit running counter which represents an intra-node call identifier
To allocate the signalling identifiers
CONFIG MORE SVC SIGNALLING CHANNEL <Scc> MORE DLCI_RANGE
NEGOTIATED
HIGH
LOW
SK000953
where Scc is a frame stream circuit from S1 to S62
26.4.3
CIR and Booking Factor

The connection manager uses CIR and the booking factor in establishing and
releasing data connections.
CIR
CIR is the committed information rate associated with the signalling channel. It is
not enforced on the signalling channel but it is used by connection management for
connection admission control. The range varies from 0 to 1984000 b/s with a default
of 0 b/s.
Booking factor
The booking factor overbooks or underbooks a frame stream. The values range from
1 to 2000% of the interface speed. The default of 100% implies no overbooking or
underbooking. The booking factor is set on the signalling channel controlling the
frame stream.
26.4-4
(400)

NNP 95-2035-01-00-B

The interface speed for a backplane frame stream is the same as the bandwidth of the
backplane frame stream configured by the administrator.
Any changes made to the booking factor take effect on new call admissions but not
on calls already established on a frame stream.
To set CIR and the booking factor

CONFIG MORE SVC SIGNALLING CHANNEL <Scc> MORE
CIR
BOOKING
<cir>
<%>
SK001021
where
Scc is a frame stream circuit from S1 to S62
cir is between 0 and 1984000 b/s
% is between 1 and 2000%
26.4.4
Connection Admission Control

CAC determines whether a data connection across two frame streams can be made.
The new connection must satisfy the following conditions.
The operational status of the signalling channel on both streams is up.

A DLCI number is provided or available on both streams.
A call reference number is available on the outgoing stream.
The chosen COS guarantee is satisfied.
Class-of-service guarantee
COS guarantee determines whether the admission of a new connection maintains
the class of service for all existing connections, rejecting the connection if congestion
is anticipated.
(400)
26.4-5


NNP 95-2035-01-00-B
COS guarantee can be either no COS guarantee or COS guarantee 1. With the former
choice, every call is accepted. With the latter choice, a call is accepted if the
connection manager finds the following three conditions are satisfied.
The requested frame sizes are acceptable.
This condition is satisfied if the higher of the two requested frame sizes does not
exceed the maximum frame size supported by the two frame streams that the call
crosses.
The requested CIR values are acceptable.
This condition is satisfied if either case 1 or case 2 is valid.
Case 1 - Requested CIR
This information applies to both the incoming and outgoing streams. In the
formulas below, Current CIRs are the CIRs for a particular direction of all
SVC calls currently in progress on a stream. ReqCIR is the requested CIR for
a particular direction in the setup message.
For the backplane stream, the following must be valid:
1. ReqCIR Interface Speed
2. ReqCIR (Booking Factor/100) Interface Speed SCurrentCIRs
Case 2 - Suggested CIR

If statement 1 or 2 in case 1 cannot be satisfied, the suggested CIR value is
calculated.
For the backplane stream:
SugCIR = (Booking Factor/100) Interface Speed SCurrentCIRs
If SugCIR > Interface Speed, then SugCIR = Interface Speed
The requested Bc and Be values are acceptable.

This condition is satisfied if, for each direction:
Interface speed > [(ReqBc + ReqBe)/ReqBc] CIR
where CIR is ReqCIR or SugCIR depending on the outcome of condition two.
If the COS guarantee is changed, a message appears stating that the change affects
all new SVC calls. The connection manager uses the change in COS guarantee to
determine the admissibility of all new calls.
To set the COS guarantee

CONFIG MORE SVC SYSTEM COS
NO_GUARNT*
GUARNT_1
SK000944
26.4-6
(400)

NNP 95-2035-01-00-B
26.5
26.5 SVC Routing

SVC Routing
This chapter describes SVC routing, including the remote address table and route
failure handling.
26.5.1
Understanding SVC Routing

SVC routing selects a path through the network for each received SVC setup. These
requests can be routed to a local user over a UNI or to a remote user over an NNI.
SVC routing uses a static routing table, manually configured by the administrator,
to forward calls to users. The table consists of the local user table and a remote
address table. The local user table consists of user configurations supported locally
by the FRE. The remote address table consists of switch prefix addresses, and
primary and alternate routes to other FREs within the SVC network.
The routing function does a best address match of the called party inside the local
user table before checking for the address in the remote address table. The calls are
routed according to the address match.
Users may place SVC calls to themselves only through the local node. SVC routing
ensures that the call request has not been looped back to the DTE that originated the
call. Any failures in routing the call are handled by alternate path routing, crankback
and call clearing.
(400)
26.5-1
26.5 SVC Routing

26.5.2

NNP 95-2035-01-00-B
Remote Address Table

The remote address table associates remote destination addresses with frame
streams attached to the FRE. The maximum number of entries in the table is 100.
Entries can be created, changed and deleted. The administrator records the
following parameters for each entry in the table.
destination address
The format of the address is either an E.164 or X.121 address in international

format. The address must be unique and cannot be the same as the host switch
prefix address or the address of the user configuration in the local user table.
The address consists of 1 to 19 digits, using 0 to 9, with a prefix of e for E.164 or
a prefix of x for X.121.
If a destination address is modified, all call setups in progress are cleared without
releasing any existing SVC connections.
route list name
The name is optional and does not need to be unique. It can be from 0 to 25
characters, including A to Z, a to z, 0 to 9, - (hyphen), +, &, /, % and : (colon).
If a route list name is modified, there is no effect on any call setups in progress or
existing SVC connections to the destination.
primary and alternate routes
Each table entry contains at least a primary and, optionally, an alternate route to
a destination address. A route consists of a frame stream of an NNI link to an
attached FRE. The identifier must uniquely identify the link to the attached FRE.
An alternate route uses a new route after an attempt to set up a connection along
a primary route fails.
The frame stream identifier for the route can be from S1 to S62 for the FRE.
If a route is modified, any call setups in progress are cleared without releasing
any existing SVC connections.
Figure 26.5-1 provides an example of a remote address table.
26.5-2
(400)

NNP 95-2035-01-00-B
26.5 SVC Routing

Figure 26.5-1: Remote Address Table

FRE
#
Stations:nn
P412-H1-00
Toronto:A
Alarms:1
11-May-1997
8:35a
Address
Route List
Primary
Alternate
Name
Route
Route
--------------------------------------------------------------------1 e15195726941
Toronto-10
S1
S2
2 e15105183472
Toronto-20
S2
S3
3 e16047232157
Vancouver-2
S2
S1
4 x3245641280
Vancouver-5
S2
S1
5 x345641279
Vancouver-10
S2
S1
CONFIG SVC ROUTING

1-PAGE_UP
6-
2-PAGE_DOWN
7-
3-SHOW_ENTRY
8-CANCEL
4-NEW_ENTRY
9-QUIT
5-DELETE
0-
Table 26.5-1 lists and explains the error and caution messages for routing.
Table 26.5-1: Error and Caution Messages for Routing
Message Type
Error
Caution
Message
Explanation
On first page.
On last page.
The screen is already at the top or

bottom of the stored records.
Invalid entry number selected.
The entered value is incorrect or outside

the valid range.
Route list name exceeds 25

characters.
Self-explanatory.
Invalid route list name.
The characters used in the name are not

valid.
Invalid stream id: the range is 1-62,

e.g. S44.
The stream value is outside the range.
Addresses must start with an E or

an X.
The address does not contain an e or x

address.
This will release call setup attempts

to this destination address.
PROCEED to continue.
If a destination address is being

removed from the remote address table,
any call setup using the address is
released if PROCEED is selected.
(400)
26.5-3
26.5 SVC Routing


NNP 95-2035-01-00-B
To create or change a remote address table

CONFIG MORE SVC ROUTING
PAGE_UP
PAGE_DOWN
SHOW_ENTRY
NEW_ENTRY
DELETE
<entry_no.>
<address>
<entry_no.>
CHG_NAME
CHG_PRI
CHG_ALT
<name>
<Scc>
<Scc>
SK000948
where
entry_no. is a number from the number column on screen
address is the switch prefix number in international format
name is from 0 to 25 characters, including A to Z, a to z, 0 to 9, - (hyphen), +, &, /, % and : (colon)
Scc is a frame stream circuit between S1 and S62
26.5.3
Route Selection for a Call Setup

A node uses the following general rules when selecting a route for a call setup.
If the called party is a local user, the call is routed on the link which provides the
best address match inside the local user table.
If the called party is a remote user, the call is routed on the link which provides
the best address match inside the remote address table.

If the call is forwarded over an NNI, the hop limit of the call setup message has
not been exceeded. A call setup path can include at most 10 network FREs before
the routing software releases the call back to the calling party.
If the call request cannot be routed, then route failure handling is invoked; see
section 26.5.4.
26.5.4
Route Failure Handling

If a node, through its SVC routing function, determines that a call setup cannot be
forwarded to the destination address, route failure handling is invoked. A link
failure, congestion or a destination address missing from the remote address table
can be the cause for a failure in routing.
26.5-4
(400)

NNP 95-2035-01-00-B
26.5 SVC Routing

The routing function checks each setup message to determine if the message has
been looped back on the call setup route. If the call is looped back to the calling node,
either crankback or call clearing is invoked.
Routing failures of remote user calls are handled either through alternate path
routing or crankback. Routing failures of local user calls are handled through call
clearing.
Crankback
Crankback is an indication in the IE of the setup message and provides a mechanism
to partially release a connection setup in progress that has encountered a failure.
Crankback releases the call to previous FREs in the call setup path when a call
request cannot be forwarded over an NNI on either a primary or alternate route.
Figure 26.5-2 shows an example of crankback being used. User 1 attempts a call to
user 2. At node A, the primary route to user 2 is through node B with an alternate
route through node C. At node B, the primary route is to node D with an alternate
route to node A over a different frame stream. The link to node D is down. Node B
cannot route the call on its alternate route as this would loop the call on the same
frame stream as it arrived on. Node B invokes a crankback to clear the call request to
node A, which routes the call on its alternate route.
Figure 26.5-2: An Example of a Crankback
User 1
User 2
FRE
DTE
Node D
FRE
Node B
FRE
Node A
DTE
Node C
Primary route to User 2
FRE
Alternate route to User 2

Crankback
9880
Alternate path routing

Alternate path routing is invoked under one of the following conditions.
A release message has been received with a crankback indication.

The primary route is unavailable due to a link failure or frame congestion.
(400)
26.5-5
26.5 SVC Routing


NNP 95-2035-01-00-B
Call clearing
The node releases the call back to the calling party by sending a release message
using the cause values in Table 26.5-2.
Table 26.5-2: Cause Values for Call Clearing
Failure Condition
26.5-6
Cause Value
The called address does not match an entry in the

remote address table.
The call is rejected with cause value 1,

Unassigned Number.
The hop limit of the setup message has been

exceeded.
The call is rejected with cause value 3, No

Route to Destination.
The SVC setup message has been routed across

the network back to the calling FRE.
The call is rejected with cause value 3, No

Route to Destination.
(400)

NNP 95-2035-01-00-B
27. X.25 Service

NNP 95-2035-01-00-B
27.1
27.1 Understanding the 36120 MainStreet X.25 Service

Understanding the 36120

MainStreet X.25 Service
This chapter provides an overview of the features and functionality of the 36120
MainStreet X.25 service, Release 1.2.
27.1.1
X.25 Protocol Overview

X.25 is an internationally accepted ITU-T standard that defines the interface between
data terminal devices and packet-switched data networks. The X.25 protocol
facilitates the interworking of packet-switched data services across geographically
dispersed public and private networks.
X.25 is a virtual call service that allows network users to establish calls using
standard X.121 and E.164 addresses. Given sufficient access privileges, any X.25
network user can call another network user by signalling the appropriate
destination address in a call request. The protocol allows called users to accept or
clear a call, or redirect it to a third party.
X.25 devices establish calls over virtual circuits, which are logical connections
between two network endpoints. Through the use of statistical multiplexing
methods, X.25 can support multiple virtual circuits over a single physical circuit.
X.25 implements various error correction and flow control techniques to ensure the
reliable transfer of data across the network. Call subscription options and facilities
allow network users to individually customize their service based on the application
requirements.
See ITU-T Recommendation X.25 for information about the X.25 protocol.
27.1.2
36120 MainStreet X.25 Overview

The 36120 MainStreet X.25 service is a complete, standards-compliant X.25
switching product suitable for public switched data networks, large service provider
networks, and corporate data networks. The 36120 MainStreet X.25 software
operates on either the Newbridge PE or FRE card, both of which can be installed in
3600 MainStreet, 3645 MainStreet, and 36120 MainStreet systems. An FRE card
running 36120 MainStreet X.25 software is called an X.25 FRE card.
User access to the network is supported at subrate and super-rate speeds using
existing Newbridge primary rate and data interface cards, and the FRS card. The
high-speed internal network consists of PE or X.25 FRE cards interconnected by
frame relay PVCs.
X.25 Service
(400)
27.1-1


NNP 95-2035-01-00-B
36120 MainStreet X.25 basic functional components

A 36120 MainStreet X.25 network consists of three basic functional components: X.25
switches, backbone trunks, and X.25 access lines.
36120 MainStreet X.25 switches
Every PE and X.25 FRE card is a fully functional X.25 switch. While the terms card
and switch can often be used interchangeably, the term switch generally refers to the
X.25-specific features and functionality provided on the cards.
In the context of a 3600 MainStreet series bandwidth manager system, a PE or X.25
FRE card is a minor node, similar to the FRE and FRS cards. The Control card is a
major node, since it is assigned a CPSS address.
Backbone trunks
A backbone trunk is a type of frame relay PVC established between two 36120
MainStreet switches. To route X.25 traffic between switches, the originating switch
encapsulates the X.25 packets in frame relay frames and sends the frames over the
appropriate backbone trunk.
X.25 access lines
X.25 access lines are the physical and logical connections between the network users
and the switches, or between a switch and a remote network. From the perspective
of the protocol, an access line is a connection between a DTE (typically the user
equipment) and the DCE (typically the network equipment).
36120 MainStreet X.25 terminology

In addition to the basic functional components, you should be familiar with the
following terms and concepts before reading this document.
X.25 access circuit
An XAC is a logical port on the X.25 switch that terminates a physically connected
X.25 access line. An XAC runs the X.25 protocol and is configured with the link layer,
network layer, X.121 or E.164 address, and call subscription option parameters.
There is one XAC configured for every X.25 device connected to the switch.
Network user address
An NUA is an X.121 or E.164 address and the call subscription options associated
with that address. NUAs are assigned to XACs and are used to set up virtual calls.
27.1-2
(400)
X.25 Serivce

NNP 95-2035-01-00-B

PE or X.25 FRE card

The PE and X.25 FRE cards are Newbridge UCS cards that support the 36120
MainStreet X.25 service and all of the frame relay capabilities of the standard FRE
card. Although the terms PE and X.25 FRE are essentially synonymous with the term
X.25 switch, this document uses PE and X.25 FRE when referring to the physical
cards and the NMTI for the cards.
27.1.3
36120 MainStreet X.25 Protocol Subsystems

The 36120 MainStreet X.25 protocol consists of layered subsystems as shown in
Figure 27.1-1. The following subsections describe each of the protocol subsystems.
Figure 27.1-1: 36120 MainStreet X.25 Protocol Subsystems
X.25 Network Layer
X.25
Link Layer
Reliable
Transfer Protocol
Generic
Frame Router
7354
Link layer
The link layer of 36120 MainStreet X.25 fully supports the 1984, 1988, and 1992
versions of ITU-T Recommendation X.25. The link layer provides X.25 DTEs with
direct X.25 access and frame relay encapsulated access to the switch.
See section 27.14.3 for more information about the link layer.
Network layer
The network layer of 36120 MainStreet X.25 fully supports the 1984, 1988, and 1992
versions of ITU-T Recommendation X.25, as well as some non-standard facilities.
The DCE network layer is a full-featured X.25 packet switch that supports local
switching, and handles all aspects of call setup, routing, and clearing. The network
layer interfaces to the link layer (for traffic to and from X.25 access lines), and the
RTP (for traffic to and from backbone trunks). The network layer reacts to congestion
notifications from both the link layer and RTP subsystems, and implements flow
control mechanisms when required.
See section 27.14.6 for more information about the network layer.
X.25 Service
(400)
27.1-3


NNP 95-2035-01-00-B
Reliable Transfer Protocol

The RTP is an implementation of ITU-T Recommendation Q.2110, with
enhancements for congestion control. It is the protocol responsible for the reliable
transfer of frames between end-point X.25 switches. The RTP uses a
connection-oriented approach that assures the transfer of data by implementing
selective retransmission, ensuring sequence integrity, and handling duplicate data.
The RTP interconnects all X.25 switches in the network using virtual connections
called RTP VCons. The RTP VCons are fully meshed in the network; packets do not
transit from one VCon to another. The RTP reacts to congestion indications from the
GFR subsystem, and implements flow control mechanisms when required.
See section 27.2.2 for more information about the RTP.
Generic Frame Router

The GFR is a direct link router and internal FRAD. The GFR encapsulates X.25
packets in frame relay frames and provides a connectionless routing service to
deliver frames between switches. As a datagram router, the GFR does not guarantee
the delivery of frames to the destination switches; rather, it relies on the RTP for this
function. The GFR uses frame relay PVCs as its transmission medium (backbone
trunks), and passes frame relay congestion indications to the RTP. A keep-alive
protocol provides rapid detection of trunk failures.
The GFR accepts packets from the RTP, encapsulates the packets in frame relay
frames using a proprietary, lightweight encapsulation method, and routes the
frames to remote switches. The encapsulation process occurs only at the originating
switch; at intermediate transit switches, the GFR routes each frame based on a
routing header that contains the address of the destination switch. At the destination
switch, the GFR decapsulates the packet and delivers it to the RTP.
See chapter 27.6 for more information about the GFR.
End-to-end function of the protocol subsystems

Figure 27.1-2 shows the relationship between the protocol subsystems and the OSI
protocol stack. The figure shows how the subsystems function along the path of a
virtual call established between two X.25 DTEs. The DTE on the left is connected to
the PE card using frame relay encapsulation techniques performed on the FRS card.
The DTE on the right is connected directly to the PE card over a basic rate or
super-rate TDM circuit.
27.1-4
(400)
X.25 Serivce

NNP 95-2035-01-00-B

Figure 27.1-2: End-to-end Protocol
DTE
Network Network
Layer
DCE
Network
Layer
DCE
Network
Layer
RTP
Link
LAPB
LAPB
Encapsulator
Physical Physical
DTE
RTP
LAPB
LAPB
GFR
FR
DTE
Network
Layer
GFR
LAPB
GFR
LAPB
Encapsulator FR or
FR or
FR or
FASTbus FASTbus FASTbus
Physical
FR
Physical
Physical
Physical
Physical
FRS
PE
Transit PE
PE
DTE
7322
27.1.4
User Access to the Network

X.25 user devices can access an X.25 switch directly over LAPB, or over frame relay
using standards-based encapsulation methods. Basic rate and super-rate devices can
use either access method, while subrate devices must use the encapsulated access
method.
Direct X.25 access

With the direct access method, LAPB data streams are connected to a PE or X.25 FRE
card over a data interface or primary rate interface circuit, as shown in Figure 27.1-3.
X.25 Service
(400)
27.1-5


NNP 95-2035-01-00-B
Figure 27.1-3: Direct X.25 Access

X.25 site
DCC
or
DNIC
m x n x 8 kb/s
LAPB
X.25
switch
DTE
64 x m kb/s
LAPB
TDM
network
PRI link
PRI
card
X.25
backbone
network
DTE
m
7296
Encapsulated access over frame relay

Encapsulated access is a method by which LAPB frames are transmitted to an X.25
switch over frame relay PVCs. 36120 MainStreet X.25 supports frame relay
encapsulation according to standards:
RFC 1490 and ANSI T1.617a Annex F Multiprotocol Encapsulation over Frame Relay
ANSI T1.617a Annex G Encapsulation of ITU-T X.25/X.75 over Frame Relay
Encapsulation can be performed by a standards-compliant PAD or FRAD at the user
premises, or by the FRS card on a 3600 MainStreet series bandwidth manager
system. The FRS encapsulates LAPB frames in frame relay frames according to the
multiprotocol encapsulation methods defined in RFC 1490 and ANSI T1.617a Annex
F.
Encapsulated access for basic rate and super-rate devices

For X.25 devices running at basic rate, super-rate, and n 8 kb/s subrate speeds, the
FRS card encapsulates LAPB frames for transmission over frame relay PVCs to local
or remote X.25 switches. Figure 27.1-4 shows this access method.
27.1-6
(400)
X.25 Serivce

NNP 95-2035-01-00-B

Figure 27.1-4: Encapsulated Access for Basic Rate and Super-rate Devices
Frame relay site
X.25 site
Frame relay
connection
DCC
or
DNIC
m x n x 8 kb/s LAPB
DTE
DTE
FRS
card
PRI
card
Encapsulated LAPB
PRI
card
X.25
switch
PRI
card
64 x m kb/s
LAPB
X.25
backbone
network
TDM
network
m = Number of DS0s (1 to 31)

n = Transport bandwidth (1 to 8)
8544
Encapsulated access for subrate devices

For X.25 devices running at subrate speeds other than n 8 kb/s, the FRS card
provides LAPB frame encapsulation and multiplexing of the subrate frame streams
onto high-speed frame relay PVCs. Figure 27.1-5 shows this access method.
Figure 27.1-5: Encapsulated Access for Subrate Devices
Frame relay / X.25 site
DNIC
FRS
card
X.25
switch
1.2 56 kb/s LAPB

DTE
DTU
X.25
backbone
network
8545
X.25 Service
(400)
27.1-7

NNP 95-2035-01-00-B
27.2
27.2 Internal Network Operation

Internal Network Operation

This chapter describes the architecture and operation of the internal 36120
MainStreet X.25 network.
27.2.1
Internal Network Architecture

Figure 27.2-1 shows the four topology layers that make up the internal 36120
MainStreet X.25 network. The layers function as follows.
1. Primary rate links (E1, T1, V.35) form the lower part of the physical layer. They
provide the underlying physical connectivity between the PE and X.25 FRE
cards.
2. Frame relay links form the upper part of the physical layer. They provide
high-speed data links between switches.
3. Frame relay PVCs are the backbone trunks that carry encapsulated X.25 packets
between switches. They can be established on frame streams over primary rate
links, or over FASTbus circuits.
4. RTP VCons are logical connections between all the switches in a network. The
RTP VCons originate and terminate only on the endpoint switches involved in a
virtual call, and ensure reliable packet transfer between the switches.
The RTP and GFR subsystems are jointly responsible for managing the exchange of
packets between switches in a 36120 MainStreet X.25 network. Unlike the traditional
connection-oriented approach where X.25 calls are set up at each switch along the
path between DCEs, 36120 MainStreet X.25 optimizes internal network performance
by providing the benefits of a reliable connection-oriented packet transfer
mechanism (RTP) and a connectionless routing system (GFR). With the 36120
MainStreet X.25 internal network protocols, X.25 virtual circuits are anchored only
to the endpoint switches, and not to intermediate transit switches.
The following section describes the RTP subsystem. See chapter 27.6 for information
about the GFR subsystem.
X.25 Service
(400)
27.2-1


NNP 95-2035-01-00-B
Figure 27.2-1: Internal Network Topology

Virtual
connection
PE B
PE A
PE C
Reliable
Transfer
Protocol
PE D
o
g
w
et
lN
a
ic
o
rk
T
o
p
o
lo
g
y
Backbone trunk
(Frame relay PVC)
PE B
PE A
PE C
Generic
Frame
Router
kb
ac
PE D
lo
T
Frame
relay link
PE B
Public
Frame Relay
Network
PE A
PE C
PE D
ra
F
e
FRE A
ay
el
R
y
g
lo
T
PE B
T1
36XX
MainStreet
PE A
X
36
T1
36XX
MainStreet
Public
Frame Relay
Network
V.
35
PE C
PE D
E1
E1
FRE A
36XX
MainStreet
ee
tr
ai
36XX
MainStreet
k
n
ru
T
y
lo
o
p
o
36XX
MainStreet
732
27.2-2
(400)
X.25 Serivce

NNP 95-2035-01-00-B
27.2.2

Understanding the Reliable Transfer Protocol

The RTP is a standards-based data transfer protocol that provides reliable packet
transmission between the originating and destination switches involved in a call.
Because data travels in both directions, originating and destination switches are
referred to as transmitter and receiver switches when discussing the RTP.
The RTP enforces a virtual connection management service that:
guarantees the delivery of frames in sequence, error free and without duplication
selectively retransmits lost frames
implements flow control between the transmitter and receiver X.25 switches
Note
RTP parameter values are not configurable. The default values are optimized for
most network implementations.
Implementation of Q.2110 functions in the RTP

The RTP is based on ITU-T Recommendation Q.2110. The Q.2110 standard provides
a means to establish and release Q.2110 connections, and transfer Q.2110 SDUs on
point-to-point connections. Q.2110 supports the transparent transfer of octet-aligned
SDUs; it does not restrict the content, coding, or format of the information, nor does
it interpret the structure or meaning of the information.
The RTP implements most of the functions of Q.2110, and introduces enhancements
for efficiency and congestion control purposes.
Sequence integrity
This function preserves the order of SDUs that were submitted for transfer.
Error correction by retransmission
Through a sequencing mechanism, the receiving switch detects missing SDUs. This
function corrects sequence errors through multiple, selective frame retransmissions.
Flow control
This function allows a receiver switch to control the rate at which the peer
transmitter switch can send information. Flow control allows the transmitter to
adjust its transmit window size based on notification of congestion experienced en
route to the receiver, and retransmissions due to the detection of lost packets. It also
allows the receiver to flow control back to the originator of the traffic when transmit
queue thresholds are exceeded.
X.25 Service
(400)
27.2-3


NNP 95-2035-01-00-B
Keep alive
This function assures that the two peer entities participating in a connection remain
in a link connection-established state even in the case of prolonged absence of data
transfer.
Transfer of user data
This function conveys user-data between users of the service.
Noisy links
RTP handles noisy (high bit error) links effectively through the use of selective
retransmissions. A single retransmission causes the transmit window size to be
reduced: the window size is reduced due to a single, isolated frame loss which is
more likely to occur due to a noisy link rather than frame relay switch congestion but
recovers back to its original size within a short period of time.
Multiple retransmissions can occur during a burst of errors that cause the window
size to be reduced continuously for every retransmitted frame. This effectively
reduces the window to a minimum size of one, and disallows retransmission of any
new traffic until it has recovered from the burst of errors.
RTP virtual connections

An RTP VCon is a point-to-point logical connection between two instances of the
RTP running on different X.25 switches. It represents a logical connection between
transmitter and receiver switches, which are called peer switches. This logical
connection may span multiple intermediate switches, and therefore encompass
multiple backbone trunks.
The RTP establishes and manages VCons between peer X.25 switches so that data
can be reliably transferred between them. The RTP does not perform the actual
routing of individual frames; rather, it relies on the GFR to route frames between
X.25 switches. The function of the RTP is strictly to ensure reliable data transfer
between the switches.
A VCon is established dynamically between two switches upon receipt of the first
X.25 call request between the two switches. The VCon originates and terminates on
the endpoint switches only, even though intermediate switches may be involved in
routing frames. Once a VCon is established between two switches, it carries all
subsequent X.25 calls between those switches. Figure 27.2-2 shows a VCon in the
context of an X.25 virtual circuit.
27.2-4
(400)
X.25 Serivce

NNP 95-2035-01-00-B

Figure 27.2-2: RTP Virtual Connection

X.25 virtual circuit
Logical
channel
DTE
Switch A
Switch E
Network layer
Network layer
Link
layer
RTP
RTP VCon
GFR
RTP
GFR
Link
layer
Logical
channel
DTE
Frame
relay
PVCs
Switch B
Switch D
Switch C
7549
A VCon is taken down after the last X.25 call is cleared to the remote switch. This
happens only after a fixed-value timer of eight minutes has expired. When the timer
expires, the resources are returned to the switch. If another call is made within the
eight-minute period, the VCon remains established, and the timer is reset after the
last call has cleared. The VCon then has another eight minutes before it is either
terminated, or another call is established.
Figure 27.2-3 shows the mapping between an X.25 virtual circuit, an RTP VCon, and
a frame relay PVC. The following subsections describe how the mapping occurs in
two virtual call setup scenarios.
X.25 Service
(400)
27.2-5


NNP 95-2035-01-00-B
Figure 27.2-3: Mapping Virtual Circuits to VCons and PVCs

Switch B
VC y
DTE
Switch C
DCE
VC x
B2
B1
FR
PVC 3
C4
FR
PVC 2
C1
DTE
Switch D
RTP
VCon
A<- ->C
FR
PVC 1
VC z
VC x
DCE
DTE
C2
VC z
FR
PVC 4
C4 C3 C2 C1 B2 B1
RTP
VCon
A<- ->B
VC = virtual circuit
DCE
Transit frame
relay switch F
Switch E
VC y
DTE
Switch A
FR = frame relay
8556
Example 1, switch A to switch B

Packets are transmitted from switch A to B as follows.
1. The DTEs connected to switch A send call requests using virtual circuits VC x
and VC y. Both VC x and VC y use VCon A<-->B to reach the DTE at switch B.
This is done by using the called DTE X.121 or E.164 address sent on VC x and VC
y and looking up the internal link to use in the GAT. The internal link number is
a one-to-one mapping to VCon A<-->B, which is established dynamically.
2. At originating switch A: The RTP adds to the call setup packet a routing header
containing the destination switch number and passes it to the GFR. The GFR
then finds switch B in its routing table and uses frame relay PVC 1 as its first hop
towards destination switch B. The packet is encapsulated in a frame relay frame
and queued for transmission.
3. At transit switch D: The frame relay switch passes the frame to the GFR (FR PVC
1 terminates at switch D). The GFR does a lookup in its routing table and finds
FR PVC 2 as its next hop towards destination switch B. The frame, with a new
DLCI in the frame relay header, is passed to the frame relay switch at switch D.
4. At transit switch E: The frame relay switch passes the frame to the GFR (FR PVC
2 terminates at switch E). The GFR does a lookup and finds FR PVC 3 as its next
hop towards destination switch B. The frame, with a new DLCI in the frame
relay header, is passed to the frame relay switch at switch E.
5. At destination switch B: The frame relay switch passes the frame to the GFR (FR
PVC 3 terminates at switch B). The GFR determines that the frame has reached
its destination, decapsulates the frame from frame relay format, and passes the
frame to the RTP. The acknowledgment frame from the RTP at switch B is sent
back to the RTP at originating switch A using the same mechanism as described
above, and VCon A<-->B is thus established. All subsequent X.25 packets on VC
x and VC y follow this route.
27.2-6
(400)
X.25 Serivce

NNP 95-2035-01-00-B

Note that the frames B2 and B1 on FR PVC 3 at switch B arrive out of order. The RTP
managing VCon A<-->B ensures that the frames are given in order (B1, B2) to the
DCE at switch B.
Example 2, switch A to switch C
Packets are transmitted from switch A to C as follows.
1. A DTE connected to switch A sends a call request using virtual circuit VC z, and
uses VCon A<-->C to reach the DTE at switch C. The same mechanism is
followed as described above to reach transit switch D.
2. At transit switch D: The GFR uses FR PVC 4 as its next hop towards destination
switch C. Note that FR PVC 4 terminates on switches D and C.
3. At transit frame relay switch F: On PVC 4, the frame is only switched by the
frame relay switch en route to its destination at switch C because FR PVC 4 does
not terminate at this switch. This transit frame relay switch could be Newbridge
or other vendor equipment.
4. At destination switch C: The frame relay switch passes the frame to the GFR (FR
PVC 4 terminates at switch C). The GFR determines that the frame has reached
its destination, decapsulates the frame from frame relay format, and passes the
frame to the RTP. The acknowledgment frame from the RTP at switch C is sent
back to the RTP at source switch A using the same mechanism as described
above, and VCon A<-->C is thus established. All subsequent X.25 packets on VC
z follow this route.
Note that frames C1, C2 and C4 on FR PVC 4 arrive at switch B with frame C3
missing. The RTP managing VCon A<-->C ensures that frame C3 is selectively
retransmitted and all four frames (C1, C2, C3, C4) are delivered to switch C in the
correct order.
Congestion management
Because a VCon may physically span one or more intermediate switches, there is a
possibility of delays and congestion within the network switches along the VCon
path. The RTP provides a congestion control mechanism so that the X.25 network
layer protocol is relieved of this responsibility. The X.25 network layer views the
VCon as a normal physical point-to-point link.
BECN bit congestion handling
Congestion between peer RTP endpoints controlled by reacting to frames having the
BECN bit set is not supported but will be available in future releases. When the RTP
receives packets with BECN bit set, it uses them as a means of congestion avoidance.
BECN bits indicate to the receiver that the packets it transmits may encounter
congested resources. This triggers source-controlled transmitter rate adjustment,
whereby the source reduces the transmit window size.
X.25 Service
(400)
27.2-7


NNP 95-2035-01-00-B
Implicit congestion handling

Retransmission of frames on a VCon by the RTP because of frame loss implicitly
indicates that congestion is being experienced along the path to the destination.
Some networks may be unable to provide BECN indications to the transmitting
switch, making implicit judgments of congestion valuable.
In such cases, the transmitting side detects congestion by frame loss within the
network. The frame loss is most likely to occur as a result of the network discarding
frames, rather than transmission errors. When the transmitting switch detects
excessive frame loss in the network, an implicit congestion condition is declared,
and RTP acts to lift the congestion.
Credit system
Peer RTP switches implement a credit system whereby credit is granted from the
receiver to the transmitter. The credit calculated at the receiver is based on the
number of PDUs that can be received (system buffer pool resources) and on the level
of congestion experienced en route to the receiver. The transmitter receives this
credit and thus has a window of sequence numbers within which it may transmit.
This is known as the credit window.
Transmit queue congestion detection
The RTP detects local congestion by monitoring the transmit queue of the VCon and
notifying the network layer when it grows above a certain threshold. Congestion
occurs when the available space left in the transmit queue falls below a pre-set lower
threshold. The RTP reacts by generating a flow control on indication. When
congestion drops below the threshold, the RTP provides the network layer with a
flow control off indication.
RTP dynamic window adaptation
The RTP has its own transmit window which it controls on a per virtual connection
basis. The dynamic adaptation of the transmit window size is such that it tries to
keep the window size large enough during congestion so as to make full use of the
bandwidth available to it on the virtual connection. This is known as the working
window. The RTP uses the minimum of the working window size and credit
window size.
The RTP supports an aggressive strategy for adapting the transmit rate. Aggressive
window size adaptation means that initially the window size is set to the maximum
size and it is adjusted downwards on receipt of congestion notification from frame
relay. This approach attempts to always maximize the RTP throughput, even to the
potential detriment of other frame relay users.
27.2-8
(400)
X.25 Serivce

NNP 95-2035-01-00-B

Flow control
The switch uses the following mechanisms to regulate flow control when congestion
is detected.
1. The RTP monitors frames received from a particular backbone trunk over a
pre-set congestion monitoring period. When more than a pre-determined
percentage of all frames receive have the BECN bit set, the transmitter reduces
the size of the transmit window. The transmit window size is increased again
when the percentage of frames with the BECN bit set is less than the
pre-determined threshold. This is done for each VCon.
2. If resources (the system buffer pool) fall below 50%, then no new virtual
connections are allowed. If the system buffer pool availability falls below 10%,
the network layer is put in flow control state. If system buffer pool depletion is
detected by the receiver, then less credit is granted to the transmitter.
3. If frames are retransmitted by the RTP (implicit congestion detection) or BECN
bits are set, the RTP reduces the transmit window size and then gradually
increases the window size as it receives credits. This is done for each VCon.
4. When the transmit queue for the VCon grows above a certain threshold, each
DTE using the VCon is flow controlled. In this condition, the switch disallows
new calls to the destination switch and flow controls the virtual circuits using the
VCon (actively using RNR packets, or passively by not transmitting any RRs
back).
5. When all of the above mechanisms have failed to alleviate the congestion
situation, the VCon becomes absolutely congested (a very remote possibility).
This causes the VCon to go down and send a disconnect indication to the
network layer, which clears all virtual circuits and resets all PVCs that use the
affected VCon.
GFR load balancing support

Load balancing is used to split traffic among trunks when there are two or three
parallel trunks available between switches. This provides a cost effective use of the
available bandwidth.
When load balancing is enabled, frames sent on multiple trunks may arrive at a
destination switch out of sequence. The RTP at a receiving switch buffers a number
of frames and re-sequences them if necessary. The size of this buffer is referred as the
RTP window.
When load balancing is not enabled and a missing frame is detected, the RTP
requests an immediate retransmission of the missing frame. When load balancing is
enabled, the RTP needs to ascertain whether a missing frame is delayed because of
the route followed. To determine if frames are missing when they are received out
of sequence, the RTP waits until either the window is full or the 750 ms frame loss
timer expires. It then requests missing frames to be resent.
X.25 Service
(400)
27.2-9


NNP 95-2035-01-00-B
Caution
The decision to use a load balancing topology should be carefully considered for the
following reasons:
To employ load balancing, it must be enabled on every switch across the entire
network.
The GFR load balancing support may adversely affect RTP performance on
27.2.3
non-load balanced links by delaying retransmission requests when frame loss

occurs.
If load balancing is employed on parallel GFR trunks of unequal speeds,
transmission delays on the slower trunk may degrade performance by causing
excessive RTP retransmission requests.
Packet Segmenting and Combining

The packet segmenting and combining feature enables the switch to segment data
packets into smaller sizes and combine data packets to form larger packets. This
feature provides two major advantages in an X.25 network.
The network can segment and combine packets to establish calls between DTEs
that would otherwise not be able to communicate.

In cases where the calling and called DTEs do not subscribe to flow control
negotiation and their default packet sizes differ, the network may be able to
use a common packet size in the internal network, while segmenting and
combining packets to accommodate the default packet sizes configured at
the interfaces.
When one or both of the calling and called DTEs subscribe to flow control
negotiation, the network may segment and combine packets if a common
packet size cannot be negotiated for the two interfaces. When the restrictions
imposed by the Allowable Packet Sizes parameter configured at the
interfaces preclude successful negotiation, the network may be able to use a
common packet size in the internal network, while allowing the DTEs to use
the requested packet sizes on the access lines.
When packet segmenting and combining occurs, the network generally uses an
optimum packet size between switches, providing highly efficient packet
transfer. The optimum packet size is always the largest packet size supported by
one of the interfaces.
Restrictions for packet segmenting and combining

The switch can only combine packets when the M-bit is set and the call satisfies the
conditions in Table 4-1 of Recommendation X.25 (1992). When a packet does not
have the M-bit set, the switch cannot wait for additional packets to combine into a
larger packet.
The switch never segments or combines packets on D-bit calls. If the switch
determines that packet segmenting and combining is required and the D-bit is set,
the call is cleared.
27.2-10
(400)
X.25 Serivce

NNP 95-2035-01-00-B

The switch never segments or combines packets across the 128 byte boundary.
Segmenting and combining can occur between any packet size combinations
between 16 and 128 bytes, and between 128 and 4096 bytes; however, segmenting
and combining cannot occur, for example, between 16 and 256 bytes.
Tables 6-1 and 6-2 of Recommendation X.25

The 1992 version of ITU-T Recommendation X.25 contains rules for packet size
negotiation in Tables 6-1 and 6-2. While the 36120 MainStreet X.25 network may
violate these rules when segmenting and combining packets across the internal
network, it never violates the rules when transmitting packets to the access lines.
Tables 27.2-1 and 27.2-2 show the flow control negotiation rules.
Note
Although the rules in Table 27.2-1 determine the values the called DTE can insert
into the Call Accepted packet, they do not affect how the switch segments and
combines packets.
Table 27.2-1: Rules From Table 6-1 in Recommendation X.25

Facility Indication
Valid Facility Request
P (indicated) 128
P (indicated P (requested) 128
P (indicated) < 128
128 P (requested) P (indicated)
Table 27.2-2: Rules From Table 6-2 in Recommendation X.25

Facility Indication
Valid Facility Request
P (requested) 128
P (requested) P (indicated) 128
P (requested) < 128
128 P (indicated) P (requested)
Conditions for packet segmenting and combining

Table 27.2-3 lists the flow control negotiation combinations and conditions that
preclude packet segmenting and combining. Table 27.2-4 describes the conditions
that allow packet segmenting and combining. The information in the tables is based
on the premise that the network allows all possible packet sizes to be sent to and
received from the access lines.
X.25 Service
(400)
27.2-11


NNP 95-2035-01-00-B
Table 27.2-3: Scenarios Where the Network Avoids Segmenting and Combining Packets
Flow Control
Negotiation at
Calling End
Flow Control
Negotiation at
Called End
Conditions that Preclude Segmenting or

Combining Packets
Comments
On
On
The called DTE accepts the proposed packet

size, or the two DTEs can agree on a
common packet size.
The negotiated packet size is used

end-to-end.
On
Off
a. At the destination switch, the packet size

proposed by the calling DTE matches the
default packet size of the called DTE, or the
sizes differ but satisfy Table 6-2.
b. At the originating switch, the default packet
size of the called DTE is allowed at the calling
interface, and the two values satisfy Table
6-2.
In case a, the default packet size of

the called DTE is sent to the
originating switch.
In case b, the default packet size of
the called DTE is subsequently used
end-to-end.
Off
On
The called DTE accepts the default packet

size of the calling DTE.
The default packet size of the calling

DTE is used end-to-end.
Off
Off
The calling and called DTEs have the same

default packet sizes.
The default packet size is used

end-to-end.
Table 27.2-4: Scenarios Where the Network Segments and Combines Packets
Flow Control
Negotiation at
Calling End
Flow Control
Negotiation at
Called End
Conditions that Allow Packet Segmenting

or Combining
On
On
The allowable packet sizes on the two

interfaces are mutually exclusive even though
they satisfy Tables 6-1 and 6-2.
The switch must segment and

combine packets to allow the DTEs
to communicate.
On
Off
a. At the destination switch, the packet size

proposed by the calling DTE is different than
the default packet size of the called DTE, and
the two values violate Table 6-2.
b. At the originating switch, the default packet
size of the called DTE is not allowed at the
calling interface, even though the two values
violate Table 6-2.
In case a, the destination switch

always returns the larger packet size
to the originating switch.
In case b, the originating switch
segments and combines packets and
transmits the originally proposed
packet size to the calling DTE.
Off
On
The requested packet size from the called

DTE differs from the default packet size of the
calling DTE.
The destination switch always

returns the larger packet size to the
originating switch, and packet
segmenting and combining is
performed at the switch where the
interface supports the smaller packet
size.
Off
Off
The calling and called DTEs have different

default packet sizes.
The switch must segment and

combine packets to allow the DTEs
to communicate. The larger of the
default packet sizes is transmitted
across the network, and packet
segmenting and combining is
performed at the switch that supports
the interface with the smaller default
packet size.
27.2-12
(400)
Comments
X.25 Serivce

NNP 95-2035-01-00-B

No flow control negotiation subscription at the calling and called DTEs

When neither the calling nor called DTEs subscribe to flow control negotiation, the
default packet sizes are used on each interface.
Figure 27.2-4 shows a case where neither the calling nor called DTEs subscribe to
flow control negotiation and their default packet sizes differ. The larger of the
default packet sizes is transmitted in the internal network, and the destination
switch segments and combines packets.
Figure 27.2-4: Example of No Flow Control Negotiation Where the Destination Switch
Segments and Combines Packets
Segment and
combine at
destination switch
256
CR(-)
Originating
switch
FC neg = No
Def PS = 256
IC (256)
CC (256)
Use 256
internally
Destination
switch
128
IC(-)
FC neg = No
Def PS = 128
CC(-)
CA(-)
CG DTE
CD DTE
8731
In Figure 27.2-5, the originating switch segments and combines packets because it
supports the interface with the smaller default packet size.
Figure 27.2-5: Example of No Flow Control Negotiation Where the Originating Switch
Segments and Combines Packets
Segment and
combine at
originating switch
256
CR(-)
Originating
switch
FC neg = No
Def PS = 256
IC (256)
CC (2048)
Use 2048
internally
CC(-)
Destination
switch
2048
IC(-)
FC neg = No
Def PS = 2048
CA(-)
CG DTE
CD DTE
8732
X.25 Service
(400)
27.2-13


NNP 95-2035-01-00-B
Table 27.2-5 is a matrix that shows all the packet size combinations that are possible
when neither the calling nor called DTEs subscribe to flow control negotiation. The
calling DTE column and called DTE row show the default packet sizes configured
for the calling and called DTEs. The subordinate cells in the matrix indicate the
packet size transmitted across the internal network. The symbol indicates that
the call is cleared because packet segmenting and combining cannot occur across the
128 byte boundary.
Table 27.2-5: Possible Packet Size Combinations When Neither DTE Subscribes to
Flow Control Negotiation
Called DTE Default Size
Calling DTE
Default Size
16
32
64
128
256
512
1024
2048
4096
16
16
32
64
128
32
32
32
64
128
64
64
64
64
128
128
128
128
128
128
256
512
1024
2048
4096
256
256
256
512
1024
2048
4096
512
512
512
512
1024
2048
4096
1024
1024
1024
1024
1024
2048
4096
2048
2048
2048
2048
2048
2048
4096
4096
4096
4096
4096
4096
4096
4096
Flow control negotiation subscription only at the calling DTE

When only the calling DTE subscribes to flow control negotiation, and requests flow
control parameters in the Call Request packet, the network observes the rules in
Table 6-2 of Recommendation X.25 to determine the packet sizes.
Figure 27.2-6 shows a case where the destination switch determines that the
proposed packet size (256) and the default packet size of the called DTE (128) comply
with the rules in Table 6-2, and therefore transmits the default packet size of the
called DTE to the originating switch. Since 128 is an allowable packet size for the
calling DTE, both DTEs use this value, and neither switch segments or combines
packets.
27.2-14
(400)
X.25 Serivce

NNP 95-2035-01-00-B

Figure 27.2-6: Example of Flow Control Negotiation at the Calling DTE Where Packet
Segmenting and Combining Does Not Occur
No segmenting
or combining at
at either switch
128
CR(256)
Originating
switch
FC neg = Yes
Def PS = XXX
IC (256)
CC (128)
Use 128
internally
Destination
switch
128
IC(-)
FC neg = No
Def PS = 128
CA(-)
CC(128)
CG DTE
CD DTE
8733
Figure 27.2-7 shows a case where the destination switch determines that the
proposed packet size (256) and default packet size of the called DTE (2048) violate
the rules in Table 6-2, and therefore transmits the largest packet size to the
originating switch. Although 2048 may be an allowable packet size for the calling
DTE, it violates the rules in Table 6-2, so the originally proposed values are sent in
the Call Connected packet to the calling DTE. The originating switch subsequently
segments and combines packets.
Figure 27.2-7: Example of Flow Control Negotiation at the Calling DTE Where the
Originating Switch Segments and Combines Packets
Segment and
combine at
originating switch
256
CR(256)
Originating
switch
FC neg = Yes
Def PS = XXX
IC (256)
CC (2048)
Use 2048
internally
CC(256)
Destination
switch
2048
IC(-)
FC neg = No
Def PS = 2048
CA(-)
CG DTE
CD DTE
8734
Table 27.2-6 lists all the packet size combinations that are possible when the calling
DTE subscribes to flow control negotiation, but the called DTE does not. The calling
DTE columns can show two packet sizes: the first value (in parentheses) indicates
the packet size proposed by the calling DTE in the Call Request packet; the second
value indicates the packet size returned by the switch in the Call Connected packet.
The called DTE columns show the default packet sizes configured for the called DTE.
X.25 Service
(400)
27.2-15


NNP 95-2035-01-00-B
The internal network columns indicate the packet size transmitted across the
internal network. The table assumes that all packet sizes received by the originating
switch are allowed for the calling DTE. The symbol indicates that the call is
cleared because packet segmenting and combining cannot occur across the 128 byte
boundary.
Table 27.2-6: Possible Packet Size Combinations When the Calling DTE Subscribes to Flow Control
Negotiation
Calling DTE
Internal
Network
Called
DTE
16
16
16
(16) 32
32
(16) 64
Internal
Network
Called
DTE
Internal
Network
Called
DTE
(32) 32
32
16
(64) 64
64
16
32
(32) 32
32
32
(64) 64
64
32
64
64
(32) 64
64
64
(64) 64
64
64
(16) 128
128
128
(32) 128
128
128
(64) 128
128
128
16
256
32
256
64
256
16
512
32
512
64
512
16
1024
32
1024
64
1024
16
2048
32
2048
64
2048
16
4096
32
4096
64
4096
(128) 128
128
16
256
16
512
16
(128) 128
128
32
256
32
512
32
(128) 128
128
64
256
64
512
64
(128) 128
128
128
(256) 128
128
128
(512) 128
128
128
(128) 128
256
256
(256) 256
256
256
(512) 256
256
256
(128) 128
512
512
(256) 256
512
512
(512) 512
512
512
(128) 128
1024
1024
(256) 256
1024
1024
(512) 512
1024
1024
(128) 128
2048
2048
(256) 256
2048
2048
(512) 512
2048
2048
(128) 128
4096
4096
(256) 256
4096
4096
(512) 512
4096
4096
1024
16
2048
16
4096
16
1024
32
2048
32
4096
32
1024
64
2048
64
4096
64
(1024) 128
128
128
(2048) 128
128
128
(4096) 128
128
128
(1024) 256
256
256
(2048) 256
256
256
(4096) 256
256
256
(1024) 512
512
512
(2048) 512
512
512
(4096) 512
512
512
(1024) 1024
1024
1024
(2048) 1024
1024
1024
(4096) 1024
1024
1024
(1024) 1024
2048
2048
(2048) 2048
2048
2048
(4096) 2048
2048
2048
(1024) 1024
4096
4096
(2048) 2048
4096
4096
(4096) 4096
4096
4096
27.2-16
Calling DTE
(400)
Calling DTE
X.25 Serivce

NNP 95-2035-01-00-B

Flow control negotiation subscription only at the called DTE

When only the called DTE subscribes to flow control negotiation, and requests flow
control parameters in the Call Accepted packet, the network observes the rules in
Table 6-1 of Recommendation X.25 to determine the packet sizes. Packet segmenting
and combining must be performed when the packet sizes differ and the calling DTE
does not subscribe to flow control negotiation.
Figure 27.2-8 shows a case where the destination switch determines that the default
packet size of the calling DTE (256) and the proposed packet size from the called
DTE (128) differ, but comply with the rules in Table 6-1. The destination switch
transmits the largest packet size to the originating switch, and subsequently
segments and combines packets.
Figure 27.2-8: Example of Flow Control Negotiation at the Called DTE Where the
Destination Switch Segments and Combines Packets
Segment and
combine at
destination switch
256
CR(-)
Originating
switch
FC neg = No
Def PS = 256
IC (256)
CC (256)
Use 256
internally
Destination
switch
128
IC(256)
FC neg = Yes
Def PS = XXX
CC(-)
CA(128)
CG DTE
CD DTE
8735
Figure 27.2-9 shows a case where the network clears the call because the packet size
indicated in the Incoming Call packet and the packet size requested by the called
DTE violate Table 6-1.
Figure 27.2-9: Example of Flow Control Negotiation at the Called DTE Where the Call is
Cleared
Call cleared
256
CR(-)
Originating
switch
FC neg = No
Def PS = 256
IC (256)
Clear
Destination
switch
2048
IC(256)
FC neg = Yes
Def PS = XXX
Clear
CA(2048)
CG DTE
CD DTE
8736
X.25 Service
(400)
27.2-17


NNP 95-2035-01-00-B
Table 27.2-7 is a matrix that shows all the packet size combinations that are possible
when the called DTE subscribes to flow control negotiation, but the calling DTE does
not. The calling DTE column shows the default packet sizes configured for the
calling DTE, and the called DTE row shows the packet sizes sent to and returned
from the called DTE. The subordinate cells in the matrix indicate the packet sizes
transmitted across the internal network.
In cases where the called DTE packet size values differ from the values received from
the originating switch, the discrepancies result from allowable packet size
restrictions. The table assumes that not all packet sizes received from the originating
switch are allowed for the called DTE. The symbol indicates that the call is
cleared because packet segmenting and combining cannot occur across the 128 byte
boundary.
Table 27.2-7: Possible Packet Size Combinations When the Called DTE Subscribes to
Called DTE Negotiated Size
Calling DTE
Default Size
16
32
64
128
256
512
1024
2048
4096
16
16
32
64
128
32
32
32
64
128
64
64
64
64
128
128
128
128
128
128
256
512
1024
2048
4096
256
256
256
512
1024
2048
4096
512
512
512
512
1024
2048
4096
1024
1024
1024
1024
1024
2048
4096
2048
2048
2048
2048
2048
2048
4096
4096
4096
4096
4096
4096
4096
4096
Flow control negotiation subscription at called DTEs

When both the calling and called DTEs subscribe to flow control negotiation, and
request flow control parameters in the call setup packets, the network observes the
rules in Tables 6-1 and 6-2 of Recommendation X.25 to determine the packet sizes.
Figure 27.2-10 shows a case where the called DTEs negotiates a common packet size
so that packet segmenting and combining is avoided.
27.2-18
(400)
X.25 Serivce

NNP 95-2035-01-00-B

Figure 27.2-10: Example of Flow Control Negotiation Where Packet Segmenting and
Combining is Avoided
No segmenting
or combining at
either switch
256
CR(512)
Originating
switch
FC neg = Yes
Def PS = XXX
IC (512)
CC (256)
Use 256
internally
CC(256)
Destination
switch
256
IC(512)
FC neg = Yes
Def PS = XXX
CA(256)
CG DTE
CD DTE
8737
Table 27.2-8 lists all the packet size combinations that are possible when both the
calling and called DTEs subscribe to flow control negotiation. The calling DTE
columns can show two packet sizes: the first value (in parentheses) indicates the
packet size proposed by the calling DTE in the Call Request packet; the second value
indicates the packet size returned by the switch in the Call Connected packet. The
called DTE columns show the packet sizes sent to and returned from the called DTE.
In cases where the called DTE values differ from the values received from the
originating switch, the discrepancies result from allowable packet size restrictions.
The internal network columns indicate the packet size transmitted across the
internal network.
The table assumes that all packet sizes received by the originating switch are
allowed for the calling DTE. The symbol indicates that the call is cleared
because packet segmenting and combining cannot occur across the 128 byte
boundary.
X.25 Service
(400)
27.2-19


NNP 95-2035-01-00-B
Table 27.2-8: Possible Packet Size Combinations When Both the Calling and Called DTEs Subscribe to
Calling DTE
Internal
Network
Called
DTE
(16) 16
16
16
(16) 32
32
(16) 64
Internal
Network
Called
DTE
Internal
Network
Called
DTE
(32) 32
32
16
(64) 64
64
16
32
(32)32
32
32
(64) 64
64
32
64
64
(32) 64
64
64
(64) 64
64
64
(16) 128
128
128
(32) 128
128
128
(64) 128
128
128
16
256
32
256
64
256
16
512
32
512
64
512
16
1024
32
1024
64
1024
16
2048
32
2048
64
2048
16
4096
32
4096
64
4096
(128) 128
128
16
256
16
512
16
(128) 128
128
32
256
32
512
32
(128) 128
128
64
256
64
512
64
(128) 128
128
128
(256) 128
128
128
(512) 128
128
128
(128) 128
256
256
(256) 256
256
256
(512) 256
256
256
(128) 128
512
512
(256) 256
512
512
(512) 512
512
512
(128) 128
1024
1024
(256) 256
1024
1024
(512) 512
1024
1024
(128) 128
2048
2048
(256) 256
2048
2048
(512) 512
2048
2048
(128) 128
4096
4096
(256) 256
4096
4096
(512) 512
4096
4096
1024
16
2048
16
4095
16
1024
32
2048
32
4096
32
1024
64
2048
64
4096
64
(1024) 128
128
128
(2048) 128
128
128
(4096) 128
128
128
(1024) 256
256
256
(2048) 256
256
256
(4096) 256
256
256
(1024) 512
512
512
(2048) 512
512
512
(4096) 512
512
512
(1024) 1024
1024
1024
(2048) 1024
1024
1024
(4096) 1024
1024
1024
(1024) 1024
2048
2048
(2048) 2048
2048
2048
(4096) 2048
2048
2048
1024) 1024
4096
4096
(2048) 2048
4096
4096
(4096) 4096
4096
4096
27.2-20
Calling DTE
(400)
Calling DTE
X.25 Serivce

NNP 95-2035-01-00-B
27.3
27.3 Standards Compliance

Standards Compliance
This chapter provides information about 36120 MainStreet X.25 standards
compliance.
27.3.1
36120 MainStreet X.25 Compliance to ITU-T

Recommendation X.2 (1988)
Table 27.3-1 shows 36120 MainStreet X.25 compliance to the 1988 version of ITU-T
Recommendation X.2. The numbers used for each optional user facility correspond
to the paragraph numbers in the 1988 version of Recommendation X.2.
Table 27.3-1: Compliance to X.2 (1988)
Optional User Facility
User Class of
Service 8-11 and
13 (X.25) (1)
VC
PVC
Newbridge
Support
VC
PVC
1.
Optional user facilities assigned for an agreed contractual period
1.1
Extended frame sequence numbering (modulo 128)
Yes
Yes
1.2
Multilink procedure
No
No
No
1.3
On-line facility registration
1.4
Extended packet sequence numbering (modulo 128)
Yes
Yes
1.5
D-bit modification
No
No
1.6
Packet retransmission
No
No
1.7
Incoming calls barred
Yes
1.8
Outgoing calls barred
Yes
1.9
One-way logical channel outgoing
Yes
1.10
One-way logical channel incoming
Yes
1.11
Non-standard default packet sizes 16, 32, 64, 256, 1024, 2048, 4096
Yes
Yes
1.12
Non-standard default window sizes
Yes
Yes
1.13
Default throughput class assignment (3)
Yes
Yes
1.14
Flow control parameter negotiation
Yes
1.15
Throughput class negotiation (3)
Yes
1.16
Closed user group
Yes
1.17
CUG with outgoing access
Yes
1.18
CUG with incoming access
Yes
1.19
Incoming calls barred within a CUG
Yes
X.25 Service
(2)
(400)
27.3-1


NNP 95-2035-01-00-B
User Class of
Service 8-11 and
13 (X.25) (1)
VC
PVC
Newbridge
Support
VC
PVC
1.20
Outgoing calls barred within a CUG
Yes
1.21
Bilateral CUG
No
1.22
Bilateral CUG with outgoing access
No
1.23
Fast select acceptance
Yes
1.24
Reverse charging acceptance
Yes
1.25
Local charging prevention
Yes
1.26
Network user identification subscription
Yes
1.27
NUI Override (4)
Yes
1.28
Charging Information (5)
No
1.29
RPOA subscription
No
1.30
Hunt Group
Yes
1.31
Call Redirection
Yes
1.32
Call Deflection subscription
No
FS
Yes
FS
No
1.33
TOA/NPI address subscription
1.34
Direct Call
2.
Optional user facilities on a per-call basis
2.1
Yes
2.2
Throughput class negotiation (3)
Yes
2.3
Closed user group selection (7)
Yes
2.4
CUG with outgoing access selection (7)
Yes
2.5
Bilateral closed user group selection
No
2.6
Reverse charging
Yes
2.7
Fast select
Yes
2.8
NUI selection
Yes
No
(6)
2.9
Charging information
2.10
RPOA selection
No
2.11
Call deflection selection
No
2.12
Call redirection notification
Yes
2.13
Called line address modified notification
Yes
2.14
Transit delay selection and indication
Yes
FS
No
2.15
27.3-2
(4)(5)
Abbreviated address calling
(8)
(400)
X.25 Service

NNP 95-2035-01-00-B

Notes
1. = Not applicable
A = Additional (optional)
E = Essential (mandatory)
FS = Further study (not yet defined)
2. On-line registration procedures have been agreed to be deleted from X.25 in the next (1996) version.
3. All throughput class values up to 192 kb/s are supported (new values for 128 kb/s and 192 kb/s are included in the 1992
version of ITU-T Recommendation X.25).
4. NUI Override is supported in Release 1 of 36120 MainStreet X.25, but the full range of parameters in X.25 Annex H is not
supported.
5. Charging Information procedures, Charging Information Request, and coding for the Time Duration and Segment Count
facilities will be supported in Release 1.1 of 36120 MainStreet X.25.
6. TOA/NPI address was not fully defined in 1988 versions of ITU-T Recommendations X.2 and X.25. It was still labelled FS
in 1992 versions of ITU-T Recommendations X.2 and X.25 (1992). Note that the TOA/NPI address facility was substantially
changed in the 1992 version of X.25 and further changes have been agreed for the 1996 version of X.25.
7. Extended format of CUG Selection facility is not supported.
8. These facilities will be supported in future releases of 36120 MainStreet X.25.
27.3.2

Table 27.3-2 shows 36120 MainStreet X.25 compliance to the 1992 version of ITU-T
Recommendation X.2. The numbers used for each optional user facility correspond
to the paragraph numbers in the 1992 version of Recommendation X.2.
User Class of
Service 8-11 and
13 (X.25) (1)
VC
PVC
Newbridge
Support
VC
PVC
1.
1.1
Extended frame sequence numbering (modulo 128)
Yes
Yes
1.2
Multilink procedure
No
No
No
1.3
On-line facility registration
1.4
Extended packet sequence numbering (modulo 128)
Yes
Yes
1.5
D-bit modification
No
No
1.6
Packet retransmission
No
No
1.7
Incoming calls barred
Yes
1.8
Outgoing calls barred
Yes
1.9
One-way logical channel outgoing
Yes
1.10
One-way logical channel incoming
Yes
1.11
Non-standard default packet sizes 16, 32, 64, 256, 1024, 2048,
4096
Yes
Yes
1.12
Non-standard default window sizes
Yes
Yes
X.25 Service
(2)
(400)
27.3-3


NNP 95-2035-01-00-B
User Class of
Service 8-11 and
13 (X.25) (1)
VC
PVC
Newbridge
Support
VC
PVC
1.13
Default throughput class assignment (3)
Yes
Yes
1.14
Yes
Yes
1.15
Throughput class negotiation (Basic)
1.16
Throughput class negotiation (Extended)
Yes
1.17
Closed User Group
Yes
1.18
Closed User Group with outgoing access
Yes
1.19
Closed User Group with incoming access
Yes
1.20
Incoming calls barred within a CUG
Yes
1.21
Outgoing calls barred within a CUG
Yes
1.22
Bilateral CUG
No
1.23
Bilateral CUG with outgoing access
No
1.24
Fast select acceptance
Yes
1.25
Reverse charging acceptance
Yes
1.26
Local charging prevention
Yes
1.27
Network user identification subscription
Yes
Yes
(3)
1.28
NUI Override
1.29
Charging Information (5)
No
1.30
RPOA subscription
No
1.31
Hunt Group
Yes
1.32
Call Redirection
Yes
1.33
Call Deflection subscription
No
1.34
TOA/NPI address subscription (6)
FS
Yes
1.35
Direct Call
FS
No
1.
1.36
ICRD Prevention subscription
No
1.37
Global Alternative Address registration
No
1.38
Interface Specific Alternative Address registration
No
1.39
Alternative Address Usage subscription
No
2.
Optional user facilities on a per-call basis
2.1
Yes
2.2
Throughput class negotiation (Basic) (3)
Yes
2.3
Throughput class negotiation (Extended)
Yes
Yes
Yes
No
2.4
(4)
Closed user group selection
(7)
2.5
CUG with outgoing access selection
2.6
Bilateral closed user group selection
27.3-4
(7)
(400)
X.25 Service

NNP 95-2035-01-00-B

User Class of
Service 8-11 and
13 (X.25) (1)
VC
PVC
Newbridge
Support
VC
PVC
2.7
Reverse charging
Yes
2.8
Fast select
Yes
2.9
NUI selection
Yes
2.10
Charging information (4)(5)
No
2.11
RPOA selection
No
2.12
Call deflection selection
No
2.13
Call redirection notification
Yes
2.14
Called line address modified notification
Yes
2.15
Transit delay selection and indication
Yes
FS
No
2.16
Abbreviated address calling
2.17
ICRD selection
No
2.18
Alternative address selection
No
(8)
Notes
1. = Not applicable
A = Additional (optional)
E = Essential (mandatory)
FS = Further study (not yet defined)
2. On-line registration procedures have been agreed to be deleted from X.25 in the next (1996) version.
3. All throughput class values up to 192 kb/s are supported.
4. NUI Override is supported in Release 1 of 36120 MainStreet X.25, but the full range of parameters in X.25 Annex H is not
supported.
5. Charging Information procedures, Charging Information Request, and coding for the Time Duration and Segment Count
facilities will be supported in Release 1.1 of 36120 MainStreet X.25.
6. TOA/NPI address was labelled FS in 1992 versions of ITU-T Recommendations X.2 and X.25 (1992). Note that further
changes to the TOA/NPI address facility have been agreed for the 1996 version of X.25.
7. Extended format of CUG Selection facility is not supported.
8. These facilities will be supported in future releases of 36120 MainStreet X.25.
27.3.3

Recommendation X.35 defines an interface between a PSPDN and a private PSDN
which is based on X.25 procedures and enhancements to define a gateway function
that is provided in the PSPDN.
X.25 Service
(400)
27.3-5


NNP 95-2035-01-00-B
Compliance to sections 0 and 1

36120 MainStreet X.25 may be used either as a public X.25 network or as a private
X.25 network. As a result, the X.35 gateway function may be located either in the
public or private network.
Conformance
Conformance to Recommendation X.35 can be stated in one of two ways. The first is
the case where the PSPDN is providing the DTE-like interface to the private PSDN.
In this case, to conform to this recommendation it is necessary that the PSPDN
provide a full set of capabilities as described, including an addressing alternative,
routing functionality, an interworking unit or interworking function, or both, and a
complete set of procedures for restart, reset, setup, clearing, interrupt, facility
handling, and flow control.
The second is the case where the PSPDN is providing a DCE interface to the private
PSDN. To conform, the PSPDN must provide the capabilities described in the
relevant sections of the recommendation.
Table 27.3-3 shows 36120 MainStreet X.25 conformance to the relevant sections of
ITU-T Recommendation X.35.
27.3-6
(400)
X.25 Service

NNP 95-2035-01-00-B


X.35 Section
X.25 Service
Description
Conformance
Requirements
36120 MainStreet X.25

Conformance
Clause 6
Topologies
Must support at least one of

the topologies in Figure 5
All six topologies are

supported
Clause 7
Addressing
Must support item a), with

items b) and c) being
optional
All three items are

supported
Subclause
7.1
Sharing of PSPDN
address space with
private PSDN
Must support either 7.1.1 or

7.1.2
Both 7.1.1 and 7.1.2 are

supported
Subclause
7.2
Address assignment
for the
PSPDN/private
PSDN interworking
function
Optional
Mapping or substitution of
an address contained in the
address extension facility is
not supported
Subclause
7.3
Independent private
PSDN address space
Optional
Both options 7.3.1 and

7.3.2 are supported
Clause 10
General
considerations
Optional
Fully supported
Clause 11
Restart procedures
Optional
Fully supported
Subclause
12.1
Call setup
procedures
Optional
Supported
Subclause
12.2
Call clearing
procedures
While this subclause must

be supported, the clearing
procedures corresponding
to the PSPDN interworking
function operating as DTE
are optional
Supported
Clause 13
Data interrupt
procedures
Optional
Supported
Clause 14
Flow control
procedures
Must be supported
Supported
Clause 15
Reset procedures
While this clause must be

supported, the reset
procedures corresponding
to the PSPDN interworking
function operating as a DTE
are optional
Supported
Clause 16
Optional user
facilities
Optional
Supported with the

exception of specific X.25
facilities not implemented
(400)
27.3-7

NNP 95-2035-01-00-B
27.4
27.4 X.25 Configuration Overview

X.25 Configuration Overview

This chapter provides an overview of the operations and configuration information
for the 36120 MainStreet X.25.
27.4.1
Understanding X.25 Configuration

Both the PE and X.25 FRE cards maintain a local configuration database and provide
support for an integral NMTI session. The configuration database resides in NVM
on the card, and stores X.25-specific configuration information.
Node management terminal interface

The integral NMTI allows a network operator to establish a node management
session with the PE or X.25 FRE cards. The NMTI is used to configure X.25 switch
parameters, provision user access and backbone trunks, and configure frame relay
switch components. Figure 27.4-1 shows the NMTI main menu for an X.25 FRE card.
It is identified by the string X25FRE displayed in the upper left corner of the display.
Figure 27.4-1: Main Menu for the X.25 FRE NMTI
X25FRE Stations:nn
F1-CONFIG
F5-ALARMS
F6-
X.25 Service
PA11-H1-00
Toronto:A
Alarms:1
11-May-1997
F2-HOUSE
F3-MAINT
F4-STATISTICS
F7-
F8-
F9-QUIT
(400)
8:35a
F10-
27.4-1


NNP 95-2035-01-00-B
In addition to using the PE and X.25 FRE NMTIs, network operators must also
establish node management sessions with the Control card and the FRS card as part
of the X.25 configuration activities.
Using the node management interfaces

You perform X.25 configuration activities at three different node management
interfaces:
Control card NMTI

PE or X.25 FRE NMTI
FRS NMTI
Control card NMTI
Use the Control card NMTI to perform the following X.25-specific configuration
activities:
configure PE and X.25 FRE card circuits for direct X.25 access
configure FRS circuits and FRS subrate circuits for frame relay encapsulation
connect data interface circuits and primary rate interface circuits to direct circuits
on the PE or X.25 FRE cards
Additionally, perform the following non-X.25 specific activities at the Control card
NMTI:
configure the data interface circuits and primary rate interface circuits
configure and connect frame streams between PE or X.25 FRE cards and FRS
cards
configure FRS circuits for rate adaption

PE and X.25 FRE NMTI
Use the PE and X.25 FRE NMTI to perform the following configuration activities:
27.4-2
configure X.25 switch-wide parameters

configure the parameters for frame stream circuits
configure XACs
connect XACs to direct circuits or frame stream-DLCIs
configure and connect trunk circuits
(400)
X.25 Service

NNP 95-2035-01-00-B

FRS NMTI
Use the FRS NMTI to perform the following X.25-specific configuration activities:
configure the parameters for encapsulation circuits and subrate encapsulation
27.4.2
circuits
configure the parameters for frame stream circuits
connect encapsulation circuits to frame stream-DLCIs
Understanding Identifiers and Entering Data

Table 27.4-1 lists the letters that are used on the PE and X.25 FRE NMTI to identify
particular objects.
Table 27.4-1: PE and X.25 FRE NMTI Identifiers
Identifier
Object
NPI for a digital E.164 address
International TOA
FASTbus station
NPI for an analog E.164 address
National TOA
Frame stream
Trunk circuit
X (1)
XAC
Xnnnn
XAC number
Xnnnn.Xnnnn
A range of XAC numbers
NPI for an X.121 address
Xnnnn...
An X.121 NUA number
xaaa,xbbb,xddd
A set of X.121 NUA numbers
xaaa.Xnnnn
A range of X.121 NUA numbers
Notes
1. The identifier used for XACs (X) is always displayed in upper case to differentiate it from the NPI
identifier for X.121 addresses (x), which is always displayed in lower case. This convention is used
for display only; it is not necessary to specifically use upper or lower case when entering data.
X.25 Service
(400)
27.4-3


NNP 95-2035-01-00-B
In some cases, the identifiers are context sensitive and do not have to be entered. For
example, if you omit the identifier after being prompted for a FASTbus station
number, a frame stream number, or an XAC number, the NMTI interprets the
meaning of the number based on the current menu function. However, some NMTI
menus require you to enter the letter before the number to clarify whether the
number represents a frame stream number, a FASTbus station number, an XAC
number or a trunk circuit number.
27.4.3
How to Use Configuration Information

X.25 configuration tasks can be divided into two major areas of activity:
tasks that are performed to commission the switch and make it operational in the
network
tasks that are performed to provide user access to the switch

The Operations and Configuration volume organizes the configuration information
along these lines. Table 27.4-2 lists the chapters according to the information they
provide.
Table 27.4-2: How Configuration Information is Organized
Switch-wide and Network-level
Configuration Information
27.5 X.25 Switch-wide Parameters
27.6 GFR Parameters
27.13 Circuits for X.25 Access Lines (1)
(1)
27.7 Call Routing Tables
X.25 User Access Configuration Information
27.14 XAC Parameters (1)

(1)
27.15 NUA Parameters(1)

27.17 X.25 PVCs
27.18 Hunt Groups
(1)
27.8 Trunk Circuits

27.9 NUI Validation Subsystem
27.19 Provisioning X.25 User Access (1)

27.4.4 X.25 to Frame Relay Service Interworking
Notes
1. Mandatory configuration activities.
As indicated in the table, certain configuration activities must be performed on every

switch in the network, while other activities are optional, based on the network
requirements. Figure 27.4-2 shows the mandatory configuration activities in a flow
diagram.
27.4-4
(400)
X.25 Service

NNP 95-2035-01-00-B

Figure 27.4-2: Mandatory X.25 Configuration Activities
Configure the
GFR address
Configure
the GAT
Configure
the Switch
Configure
and connect
backbone trunks
Configure
and connect
circuits for X.25
access lines
Configure the
XAC interface parameters
(link layer, network layer,
address translation table)
Configure
User Access
Configure NUAs
and assign
to XACs
Configure
subscription options
and facilities
7523
X.25 Service
(400)
27.4-5

27.4.4

NNP 95-2035-01-00-B
Summary of X.25 Configurable Parameters

Tables 27.4-3 to 27.4-13 list all the configurable X.25 parameters.
Table 27.4-3: X.25 Switch-wide Parameters
Parameter
Options
Default
Number of XACs
1 512 (PE)
1 128 (X.25 FRE)
128 (both cards)
Number of Trunk Circuits
1 128 (both cards)
128 (PE)
32 (X.25 FRE)
Table 27.4-4: GFR Parameters

Parameter
Options
Default
GFR Address
hub-leaf
None
Redundant Routing
Disabled
Enabled
Disabled
Load Balancing
Disabled
Enabled
Disabled
Hub Domain Dynamic Routing
Disabled
Enabled
Disabled
Delta Value
0 256
List of Aliases
0 9 aliases in the format

hub-leaf
None
Disabled
Enabled
Disabled
Aggregate Committed Information

Rate
0 8 Mb/s
Aggregate Committed Burst Size
0 40 Mb
Table 27.4-5: Trunk Circuit Parameters

Parameter
27.4-6
Options
Default
Trunk Circuit
1 128
None
Cost
1 255
50
Poll Timer
0 127 500 ms
(400)
X.25 Service

NNP 95-2035-01-00-B

Table 27.4-6: NUI Server Agent Parameters

Parameter
Options
Default
Primary NUI Server Address
NPI and 1 19 digits in X.121

or E.164 address format
None
Secondary NUI Server Address
NPI and 1 19 digits in X.121

None
Maximum Allowed Validation Period
0 500 s
10 s
Table 27.4-7: XAC Link Layer Parameters

Parameter
Options
Default
Link Layer Interface Type
DTE
DCE
DCE
Frame Sequence Numbering
8
128
Maximum Frame Window Size (k)
1 7 (modulo 8)
1 127 (modulo 128)
Retransmission Count (N2)
1 20
10
Frame Response Timer (T1)
10 120 000 ms in multiples

of 10 ms
3000 ms
Response Delay Timer (T2)
0 3000 ms in multiples of
100 ms
200 ms
Inactivity Timer (T3)
0 120 000 ms in multiples of

10 ms
60 000 ms
Congestion Timer
10 120 000 ms in multiples

of 10 ms
3000 ms
Maximum Information Frame Size (N1)
263 4105 bytes
519 bytes
Table 27.4-8: XAC Network Layer Parameters

Parameter
X.25 Service
Options
Default
Service Type
X.25
X.25 Gateway
NUI Agent
Accounting Agent
XFR
x.75 Gateway
X.25
Packet Layer Interface Type
DTE DCE
DCE
X.25 Version
1984/1988
1992
1984/1988
Packet Sequence Numbering
8
128
Base LCN
1 4095
1 for XFR
(400)
27.4-7


NNP 95-2035-01-00-B
Parameter
27.4-8
Options
Default
Number of LCNs
1 4095
1 for XFR
32
1 for XFR
Number of PVCs
0 4095
0 1 for XFR
Number of Outgoing SVCs
0 4095
0 for XFR
0
0 for XFR
Two Way SVCs
0 4095
32
Number of Incoming SVCs
0 4095
0 1 for XFR
0
0 for XFR
Packet Layer Restart Timer (T10/T20)
0 630 s
180 s
Packet Layer Call Timer (T11/T21)
0 630 s
200 s
Reset Timer (T12/T22)
0 630 s
180 s
Clear Timer (T13/T23)
0 630 s
180 s
Window Timer (T24)
0 630 s
60 s
Inactivity Timer
0 630 s
0s
Flow Control Timer
1 180 s
1s
Incoming Maximum Address Length

Allowed
1 19 digits
19
Suppress Called Address
Yes
No
No
Suppress Calling Address
Yes
No
No
Local Address Validation
Yes
No
Yes
Default NPI
X.121
E.164 Analog
E.164 Digital
X.121
Address Translation Table Entry
See Table 27.4-10
Allowable Packet Sizes
16, 32, 64, 128, 256, 512,

1024, 2048, and 4096 bytes
128, 256, and 512 bytes
Yes
No
No
Throughput Class Negotiation
Yes
No
No
Throughput Class Negotiation Format
Basic
Extended
Basic
Generate Cause Codes in DTE Format
Yes
No
No
Enhanced Diagnostic Codes
Yes
No
Yes
Generate Alarms
Yes
No
No
(400)
X.25 Service

NNP 95-2035-01-00-B

Table 27.4-9: XFR Service Interworking

Parameter
Options
Default
ACT (packets)
10 128
10
SCT
0 100%
80%
MCT
0 100%
0%
Frame Relay Reconnect Timer
0 500 999 sec
120 sec
Table 27.4-10: XAC Address Translation and Screening Parameters

Parameter
X.25 Service
Options
Default
Entry Number
1 256
None
External Translation Prefix
TOA and NPI plus 1 19

digits or wildcards
ix
Internal Translation Prefix
TOA and NPI plus 1 19

digits or wildcards
ix
Direction
Incoming
Outgoing
Both
Both
Which Address
Calling
Called
Both
Both
Trap Incoming Calling
Yes
No
No
Trap Incoming Called
Yes
No
No
Trap Outgoing Calling
Yes
No
No
Trap Outgoing Called
Yes
No
No
Trap Action Clear Call
Yes
No
No
Trap Action Cause Alarm
Yes
No
No
(400)
27.4-9


NNP 95-2035-01-00-B
Table 27.4-11: NUA Parameters

Parameter
27.4-10
Options
Default
Network User Address
NPI plus 1 19 digits in X.121

None
Allocated XAC Number
1 512 (PE cards)

1 128 (X.25 FRE cards)
None
User Defined Data
0 24 alphanumeric
characters
None
Accounting Activation
Yes
No
No
Periodic Accounting Activation
Yes
No
No
Hot Billing
Yes
No
No
Reverse Charge Acceptance
Yes
No
No
Local Charge Prevention
Yes
No
No
Charging Information Subscription
Yes
No
No
Charging Information Request Allowed
Yes
No
No
Incoming Fast Select Acceptance
Yes
No
No
Outgoing Restricted Fast Select

Allowed
Yes
No
No
Outgoing Unrestricted Fast Select

Allowed
Yes
No
No
Default NUA
Yes
No
Yes, if it is the first NUA

allocated; otherwise No
TOA/NPI Address Format
Yes
No
No
Clear on Calling Address Failure
Yes
No
No
Redirection Address
1 19 digits in X.121 or E.164

address format
None
Signal CRN
Yes
No
Yes
Signal CLAMN
Yes
No
Yes
Call Deflection
Yes
No
No
NUI Subscription
Yes
No
No
(400)
X.25 Service

NNP 95-2035-01-00-B

Parameter
X.25 Service
Options
Default
NUI Validation Required
Yes
No
Yes
Default NUI Format
Standard
Non Standard
Non Standard
Non-standard NUI Coding Method
IA5
BCD
IA5
Non-standard NUI First Subfield
NUI Password
NUI

Length
1 21
CUG Index
0 99
None
Interlock Code
0 65 535
None
Barring
Incoming Calls Barred

Outgoing Calls Barred
No Barring
No Barring
Preferential CUG
Yes
No
No
CUG With Incoming Access
Yes
No
No
CUG With Outgoing Access
Yes
No
No
Signal Preferential CUG
Yes
No
No
Default Receive Packet Size

Default Send Packet Size
16, 32, 64, 128, 256, 512,

1024, 2048, or 4096 bytes
128 bytes
Default Receive Window Size

Default Send Window Size
1 7 (modulo 8)
1 127 (modulo 128)
Default Receive Throughput Class

Default Send Throughput Class
75 150 300 600 1200

2400 4800 9600 19 200
48 000 64 000 128 000
192 000 256 000 320 000
384 000 448 000 512 000
576 000 640 000 704 000
768 000 832 000 896 000
960 000 1 024 000
1 088 000 1 152 000
1 216 000 1 280 000
1 344 000 1 408 000
1 472 000 1 536 000
1 600 000 1 728 000
1 792 000 1 856 000
1 920 000 1 984 000
2 048 000 b/s
64 000 b/s
(400)
27.4-11


NNP 95-2035-01-00-B
Table 27.4-12: X.25 PVC Parameters

Parameter
Options
Default
Local Address
NPI and 1 to 19 digits
None
Local LCN
1 to 4095
None
Remote Address
None
Remote LCN
1 to 4095
None
Yes
No
No
Yes
No
No
D-Bit Allowed
Yes
No
No
Local Send Packet Size

Local Receive Packet Size
Remote Send Packet Size
Remote Receive Packet Size
16, 32, 64, 128, 256, 512,

1024, 2048, or 4096 bytes
128 bytes
Send Window Size

Receive Window Size
1 to 127
Send Throughput Class

Receive Throughput Class
75 150 300 600 1200

2400 4800 9600 19 200
48 000 64 000 128 000
192 000 256 000 320 000
384 000 448 000 512 000
576 000 640 000 704 000
768 000 832 000 896 000
960 000 1 024 000
1 088 000 1 152 000
1 216 000 1 280 000
1 344 000 1 408 000
1 472 000 1 536 000
1 600 000 1 728 000
1 792 000 1 856 000
1 920 000 1 984 000
2 048 000 b/s
64 000 b/s
Originating End
Local
Remote
Local, if a local PVC;

otherwise None
Table 27.4-13: Hunt Group Parameters

Parameter
27.4-12
Options
Default
Hunt Group Address
None
Redirection Address
None
Hunt Group Member NUA
None
(400)
X.25 Service

NNP 95-2035-01-00-B
27.5

X.25 Switch-wide Parameters

This chapter describes how to configure the parameters that define the maximum
number of XACs and trunk circuits on the switch.
27.5.1
Understanding X.25 Switch-wide Parameters

As part of the commissioning process for a 36120 MainStreet X.25 switch, you can
configure parameters that define the maximum number of XACs and trunk circuits
supported on the switch.
These parameters are used to control the amount of memory allocated to the various
subsystems on the X.25 cards. The values should be set as low as possible to
accommodate the required number of subscribers on the switch, yet allow for
reasonable network growth.
These parameters are normally configured once, when the switch is commissioned,
though they may be changed at any time with no disruption of service.
Global switch resources

While you can configure the maximum number of XACs and trunk circuits
supported on the switch, limits for other resources are not configurable. The Global
Resources display provides support limits and usage values for these resources. This
information is useful for switch performance monitoring and network planning and
engineering.
27.5.2
Viewing X.25 Switch-wide Parameters

Figure 27.5-1 shows the NMTI display for the X.25 switch-wide parameters. The
Maximum column indicates the values that are currently configured, while the
Highest In Use column shows the resources currently being used on the switch.
Values in the Highest In Use column can never exceed values in the Maximum
column.
X.25 Service
(400)
27.5-1


NNP 95-2035-01-00-B
Figure 27.5-1: X.25 Switch-wide Parameters Display

X25FRE Stations:nn
PA11-H1-00
Toronto:A
Alarms:1
11-May-1997
8:35a
Global Parameters
----------------Number of
--------XACs
Maximum
------:128
Highest In Use
-------------:112
Trunk Circuits
:128
:64
CONFIG SWITCH X25 GLOBALS PARAMS

F1-XACS
F6-
F2-TRUNK_CCTS
F7-
F3F8-CANCEL
F4F9-QUIT
F5F10-PROCEED
Viewing global switch resources

Figure 27.5-2 shows the NMTI display for the switch-wide resources that are not
configurable. The Maximum column indicates the values that are hard-coded in the
switch, while the In Use column shows the resources currently being used on the
switch. Table 27.5-1 describes the fields.
Note
The hard-coded maximum values are subject to change in maintenance releases of
36120 MainStreet X.25.
27.5-2
(400)
X.25 Serivce

NNP 95-2035-01-00-B

Figure 27.5-2: X.25 Global Resources Display

X25FRE Stations:nn
PA11-H1-00
Toronto:A
Alarms:1
11-May-1997
Global Resources
---------------Number of
Maximum
----------------PEs pr Network
:1024
NUAs
:512
CUGs
:5120
ICUGs
:2048
Hunt Groups
:64
Address Translations
:2560
Configured LCN Pages
:4096
Aliases
:3
Accounting Record Intervals
:2
Collection Intervals per Intermediate
Intermediate Record
:4
Configured PVCs
--CUGs per NUA
:20
Members per Hunt Group
:16
8:35a
In Use
-----:3
:85
:100
:100
:8
:43
:127
:3
:2
:1
:12
CONFIG SWITCH X25 GLOBALS SHOW_RES

F1F6-
F2F7-
F3F8-CANCEL
F4F9-QUIT
F5F10-
Table 27.5-1: X.25 Global Switch Resources

Field Name
X.25 Service
Description
Number of NUAs
The maximum number of NUAs that can be

configured on the switch, and the number currently in
use. This value determines the maximum size of the
LAT.
Number of CUGs
The maximum number of CUGs supported by the

switch, and the number currently in use. The value
determines the total number of unique interlock
codes that can be configured.
Number of Hunt Groups
The maximum number of hunt group addresses that

can be configured on the switch, and the number
currently in use.
Number of Address Translations
The maximum number of address translation table

entries that can exist on the switch, and the number
currently in use. This is the total number of entries for
all XACs.
Number of Configured LCN Pages
The maximum number of LCN pages that can be

configured on the switch, and the number currently in
use. An LCN page consists of 128 LCNs.
(400)
27.5-3


NNP 95-2035-01-00-B
Field Name
Description
Number of Aliases
The maximum number of aliases that can be

assigned to the GFR, and the number currently in
use.
Number of Accounting Record Intervals
The maximum number of intervals that can be

configured for accounting purposes, and the number
currently in use.
Number of Virtual Circuits
The maximum number of virtual circuits that can be

active on the switch at the same time, and the
number currently in use.
Number of CUGs per NUA
The maximum number of CUGs to which an NUA can

belong.
Number of Members per Hunt Group
The maximum number of NUAs that can belong to a

particular hunt group. This value does not include the
hunt group redirection address.
To view X.25 switch-wide parameters

To view global switch resources

CONFIG SWITCH X25 GLOBALS SHOW_RES
27.5.3
Configuring the X.25 Switch-wide Parameters

This section describes the X.25 switch-wide parameters and provides configuration
guidelines. The parameters are ordered as they appear on the NMTI display.
Number of XACs
This parameter specifies the maximum number of XACs supported by the switch.
This includes XACs for subrate, basic rate, and super-rate X.25 access lines. The
value cannot be set lower than the value displayed in the Highest In Use field.
Range
1 to 128 for X.25 FRE cards
1 to 512 for PE cards
Default
128
27.5-4
(400)
X.25 Serivce

NNP 95-2035-01-00-B

Number of Trunk Circuits

This parameter specifies the maximum number of trunk circuits supported by the
switch. The value cannot be set lower than the value displayed in the Highest In Use
field.
Range
1 to 128
Default
32 for X.25 FRE cards
128 for PE cards
Restrictions and interdependencies

You cannot change maximum values to be less than the in-use values.
Change impact and activation

You can change the values of the X.25 switch-wide parameters at any time with no
disruption of service. The changes are effective immediately.
To configure the X.25 switch-wide parameters

XACS
TRUNK_CCTS
<xac>
<trunk_cct>
SK000403
where
xac is 1 to 512 for PE cards and 1 to 128 for X.25 FRE cards, 128*
trunk_cct is 1 to 128 (128* for PE cards and 32* for X.25 FRE cards)
X.25 Service
(400)
27.5-5

NNP 95-2035-01-00-B
27.6
27.6 GFR Configuration

GFR Configuration
This chapter describes how to configure the GFR parameters to enable the operation
of the connectionless routing system. These parameters specify how a 36120
MainStreet X.25 switch routes frames to, and receives frames from, other switches
across the backbone network.
This chapter does not describe the X.25 call routing process. For information about
how X.25 calls are established using destination addresses, see chapter 25.7.
27.6.1
Understanding Network Topologies

The switches in a 36120 MainStreet X.25 network are interconnected by backbone
trunks. These backbone trunks are frame relay PVCs. When X.25 traffic is routed
between switches, the originating switch encapsulates the X.25 packets in frame
relay frames and routes the frames to their destination using the connectionless
routing system. See section 27.8.1 Understanding Backbone Trunks for a full
explanation.
Network routing domains

To route frames efficiently between switches, the network is organized into a
two-level hierarchy of domains called hub domains and leaf domains. The hub
domain may be subdivided into direct link and dynamic routing segments to
effectively produce a three-level hierarchy.
Leaf domains
A leaf domain is the lower level of the routing hierarchy. A leaf domain consists of
1 to 245 leaf switches directly connected to one or more centralized hub switches.
Leaf switches may also have direct trunks to other leaf switches. Figure 27.6-1 shows
an example of a fully-meshed network of leaf switches. While this topology provides
high-speed operation, there is no redundancy and no rerouting capability.
X.25 Service
(400)
27.6-1


NNP 95-2035-01-00-B
Figure 27.6-1: High-speed, Non-redundant, Fully-meshed Network Topology
10-10
10-11
10-12
10-13
7527
Hub domains
The hub domain is the upper level of the routing hierarchy and is made up of
1 to 245 hub switches interconnected by trunks that may or may not be fully
meshed. The hub domain interconnects all of the leaf domains. Figure 27.6-2 shows
an example of X.25 switches organized into domains.
27.6-2
(400)
X.25 Serivce

NNP 95-2035-01-00-B

Figure 27.6-2: Network Routing Topology
Leaf Domain
PE
PE
PE
PE
FRS
PE
FRS
PE
Leaf Domain
Hub
Domain
PE
PE
PE
Leaf Domain
FRS
PE
FRS
PE
PE
PE
PE
PE
PE
Hub switch
PE
PE
FRS
FRS
FRS
PE
Leaf switch
FRS
FRS
Leaf
Domain
FRS
Feeder switch
7519
The topology of large networks can be designed with a combination of direct link
and dynamic routing sectors in the hub domain. The hub domain may thus be
divided into two tiers. These consist of a dynamic routing core and clusters of feeder
hubs employing direct link routing. These, with the leaf domain, form a three-tier
routing topology.
The dynamic routing sector is a core of hubs which need not be fully meshed. The
direct link routing sector is made up of hub clusters. Each hub in a cluster is directly
linked to a switch in the hub domain dynamic routing sector. In this three-tier
topology, shown in Figure 27.6-3, there are leaves, direct link hub clusters and
dynamic hubs. In the diagram, the hubs and leaves are all shown as X.25 PE switches
but may also be X.25 FRE switches. The shaded hubs are in directly linked clusters
and the dynamic routing hubs are unshaded.
This topology significantly reduces dynamic routing network overhead while still
offering the advantages of dynamic routing in the network core.
X.25 Service
(400)
27.6-3


NNP 95-2035-01-00-B
Figure 27.6-3: A Three-tier Routing Topology
11
Hub
cluster
PE
PE
PE
PE
Leaf
domain
PE
PE
A
PE 02
Dynamic
routing
sector
05
E
PE 04
PE
Leaf
domain
PE
PE
Direct link
routing sector
Hub domain
01
PE
PE
Hub
cluster
F
PE
PE
PE
Leaf
PE
domain
PE
PE
Three tier network with dynamic
routing hubs and fully meshed hub
clusters serving the leaf domains
PE Leafs
PE
Hub 21
cluster
PE Direct Link Hubs

PE Dynamic Hubs
10428
Inter-domain and intra-domain routing

The difference between hub switches and leaf switches is that hub switches serve as
intermediate switches for network routing but leaf switches cannot be intermediate
switches. A hub switch can pass traffic between switches, but a leaf switch cannot
forward traffic to another leaf switch unless it originated the traffic. Leaf switches
can reroute traffic only in cases where reversed frames are returned to the
originating leaf switch.
Routing within a leaf domain is called intra-domain routing, and routing between
leaf domains is called inter-domain routing. Normally, switches in a leaf domain try
to route all traffic directly to the destination leaf switch if trunks are available
between the switches. If trunks between switches are not available, traffic is routed
to a hub switch that in turn routes the traffic to a destination switch in the leaf
domain, or to a destination switch in a different leaf domain.
Figure 27.6-4 shows an example of a network that has two leaf domains. This
topology provides high fanout but no redundancy and is suited to low-volume,
high-access requirements.
27.6-4
(400)
X.25 Serivce

NNP 95-2035-01-00-B

Figure 27.6-4: High-fanout, Low-volume, Non-redundant Network Topology
10-10
11-11
10-11
11-10
10-15
11-12
10-11
10-11
10-14
11-13
10-13
10-12
11-15
11-14
7528
Leaf domains are mainly used for routing traffic within a collection of switches
collocated on a 3600 MainStreet network. Routing between hub switches is
appropriate for traffic destined for remote switches across the backbone network.
GFR routing concepts

Two types of datagram routing, direct link routing and dynamic routing, are
performed in a 36120 MainStreet X.25 network. Each routing type has different
characteristics and capabilities. It is necessary to understand the principles applied
in each type of routing.
Direct link routing
Direct link routing is used between directly connected adjacent switches or a source
leaf switch through a hub switch to a destination switch. Direct link routing in the
hub domain requires all the hubs to be fully meshed. This means that each hub
switch must have at least one trunk directly connected to every other hub switch.
Direct link routing is always used in the leaf domain. In the hub domain it can be
used exclusively, in conjunction with dynamic routing or not at all.
When direct link routing is used, a route is defined as the trunk from a source switch
to an adjacent switch. The adjacent switch may be the destination switch or a hub
switch through which the destination switch can be reached.
Dynamic routing
Dynamic routing can be performed only in the hub domain. Its purpose is to
economize on trunk requirements because full meshing is not required. Dynamic
routing allows frames to be routed across the hub domain through transit switches.
When dynamic routing is used, redundancy is provided by the use of alternative
routes around failed trunks. When dynamic routing is used, a route is defined as an
end-to-end path between entry and exit hub switches.
X.25 Service
(400)
27.6-5


NNP 95-2035-01-00-B
Trunk and route costs

To prioritize route selection, each trunk is assigned a cost value. In the direct link
environment, route and trunk costs are synonymous.
In hub domain dynamic routing, switches are also assigned transit costs. Route costs
across those switches are the sum of the trunk costs and transit costs from the entry
switch to the exit switch in the hub domain.
For example, in Figure 27.6-3, for traffic from Switch 11 to Switch 21, the route cost
for Switch 11 is the trunk cost to Switch 01. The route cost from Switch 01 to Switch
21 is the sum of trunk A, Switch 03 transit cost and the trunk cost from Switch 03 to
Switch 21. If trunk A is unavailable, the route cost through trunks B and C, is the sum
of trunk costs B and C, the transit costs of switches 02 and 03 and the trunk cost from
Switch 03 to Switch 21.
It is important to understand that trunk costs are unidirectional and apply only to
traffic being transmitted to the trunk. The switches at either end of a trunk may be
configured with different costs for the same backbone trunk. Hence, traffic may take
different routes depending on the direction of the call.
See Cost in section 27.8.3 for more information.
Hub domain dynamic routing

Dynamic routing in the hub domain allows more efficient utilization of trunk
resources and provides routing around failed trunks. Routes between dynamic
routing hub switches are calculated by each dynamic routing hub switch. Using
dynamic routing a hub domain need not be fully meshed, allowing frames to be
routed through a number of transit hubs. Dynamic routing also allows alternative
paths to be utilized for instantaneous routing around failed trunks. Figure 27.6-5
shows this concept by comparing a fully meshed network with a non-meshed
network using dynamic routing. In the diagram, the hubs are all shown as X.25 PE
switches but may also be X.25 FRE switches.
Figure 27.6-5: Trunk Requirement Comparison
PE
PE
PE
PE
PE
PE
PE
PE
PE
PE
Fully meshed direct link hub domain

requiring 10 trunks
Dynamic routing hub domain

using 6 trunks
10429
Because switch access is not dependent on fully meshed trunks, the number of hub
nodes in a network hub domain can be increased without consuming a large number
of frame relay PVC connection resources on a switch.
27.6-6
(400)
X.25 Serivce

NNP 95-2035-01-00-B

The major advantages of dynamic routing are trunk economy, scaling and
instantaneous rerouting. However, there is a compromise between these advantages
and the increase in network traffic overhead caused by the distribution of dynamic
routing status updates. When topology status changes occur, all the dynamic
routing hubs in the network broadcast the new routing data. In addition, each
dynamic routing hub periodically broadcasts its entire topology status database. The
size of the dynamic routing hub domain also has an effect on GFR memory
resources.
GFR addresses
As part of the initial commissioning process, the network operator assigns a hub
number and a leaf number to every switch in a 36120 MainStreet X.25 network. This
pair of numbers, called the GFR address, identifies the switch as a hub switch or a
leaf switch and provides it with a unique routing address in the network.
Hub switches have hub numbers from 10 to 255 and leaf number 0; for example
110-0. Leaf switches have hub numbers from 10 to 255 and leaf numbers 10 to 255;
for example, 110-55.
When packets are routed between switches, the originating switch adds a routing
header to each packet. This routing header contains the GFR address that identifies
the switch to which the packet is destined. Once a call is established, this routing
header is added to every packet associated with that call, allowing each packet to be
routed independently through the network.
Aliases
Hub switches can be configured to re-route packets to and from leaf domains other
than their own. An alias is a GFR address that a hub switch assumes in order to route
traffic for another hub switch.
When a particular hub is out of service or is unreachable, the forwarding switch
routes frames to the alias instead. The alias switch then attempts to forward the
frames to their destination. This is achieved using alias GFR addresses.
Only hub switches can be aliases. You configure an alias in the same format as a GFR
address, but the ranges are:
hub number from 10 to 255

leaf number from 1 to 9
Though the range for alias leaf numbers is from 1 to 9, only three alias GFR addresses
may be configured on any one hub switch.
Redundancy using aliases
When a hub switch is out of service, intra-domain routing between unconnected leaf
switches and inter-domain routing between leaf domains is not possible. In such
cases, aliases allow leaf switches to route traffic to a hub switch of another leaf
domain. The hub switch acting as an alias for the affected domain can then route
traffic within the originating domain or to other domains. This is also true for
incoming traffic.
X.25 Service
(400)
27.6-7


NNP 95-2035-01-00-B
Figure 27.6-6 is an example of a redundant network topology. This example shows

the following:
Hub switch 120-00 is configured as an alias for switch 100-00 using alias 100-01.
This means that if switch 100-00 fails, switch 120-00 performs the task of routing
packets to and from the leaf switches in domain 100. Note that every leaf switch
has direct trunks to both its hub switch and the alias hub switch.
Hub switch 100-00 is configured as an alias for switches 120-00 and 131-00 using
aliases 120-01 and 131-01, respectively. This means that if either switch 120-00 or
131-00 fails, switch 100-00 performs the task of routing packets to and from the
leaf switches in domains 120 and 131.
Due to the GFR forwarding rules, switch 100-00 will always be used to route
frames from 120-10 and 120-11 to leaf nodes in leaf domain 131-00 (for example,
leaf 131-10).
Figure 27.6-6: Redundant Network Topology
110-10
131-10
110-00
(120-02)
120-10
120-11
131-00
120-00
100-00
(100-01)
(110-01)
(131-01)
(120-01)
100-10
100-11
131-11
100-12
100-13
7518
Load balancing
The GFR can load balance over two or three trunks between two switches. However,
load balancing should not be permitted over routes that include intermediate hops.
Furthermore, GFR load balancing is not performed over alias switches if the normal
route is functional.
Load balancing is a network wide feature. It is the network operators responsibility
to decide whether or not to employ load balancing. When enabled, every switch in
the network must be configured for load balancing, even though it is ineffective on
routes with only one trunk.
The GFR splits the traffic when the cost difference between alternate routes is less
than or equal to a configurable parameter, delta (D).
27.6-8
(400)
X.25 Serivce

NNP 95-2035-01-00-B

Splitting traffic by using load balancing means that frames from a given call follow
different paths to the destination. Because of possible unequal delays on the
different routes, frames may arrive at the receiving switch out of sequence. The RTP
buffers frames while it waits for delayed frames to arrive. The greater the difference
between delays on different routes, the more buffering is required to re-sequence the
frames. Hence, load balancing is most efficient when the network is engineered so
that frames belonging to one call are transmitted on identical or very similar trunks.
Load balancing is intended for use on parallel trunks between two switches.
Automatic FASTbus trunks

When a PE or X.25 FRE card is connected to a FASTbus, the card automatically
establishes backbone trunks to all the other PE and X.25 FRE cards on the FASTbus
ring, which share the same 36120 ID and have the GFR address and Station ID
configured.
You can configure aggregate class-of-service parameters for the automatic FASTbus
trunks. The class-of-service parameters specify the amount of FASTbus bandwidth
that is dedicated to, and shared among, the automatic FASTbus trunks on a
particular card. This bandwidth is subtracted from the total amount of FASTbus
bandwidth available for regular frame relay circuits.
FASTbus trunk costs cannot be configured. A FASTbus trunk cost is always 10.
27.6.2
Understanding the Generic Frame Router

The GFR is a datagram router that provides connectionless routing and automatic
re-routing between X.25 switches. The GFR available with X.25 Release 1.2 supports
two types of routing algorithms; direct link routing and dynamic routing. The GFR
consists of two sub-components, the route builder and the forwarding functions.
Route builder
The route builder uses direct link and dynamic routing algorithms to build a
forwarding table that is later used to forward frames during data switching. The
route builder uses a least-cost algorithm in selecting the best routes when generating
the forwarding table. This lists available trunks to all connected destinations
through adjacent switches, together with their associated costs. Once established,
the forwarding table changes only when trunk status or topology changes occur.
In the hub domain dynamic routing sector, GFRs use a link state routing protocol to
exchange topology information with each other. This information is used to build a
link state database that describes the entire dynamic routing topology. A link state
database is built on every dynamic routing switch.
X.25 Service
(400)
27.6-9


NNP 95-2035-01-00-B
On hubs configured for dynamic routing, the topology information includes data
relating to all the dynamic routing hubs in the network. The constructed routing
tables are maps of the entire dynamic routing domain. They contain first choice and
up to two alternate choices of trunk for all reachable destinations. Dynamic routing
tables are amended when topology changes occur. Such changes include the
addition or removal of trunks and switches, switch or trunk failures and the
resumption of operations when faults have been rectified. Dynamic routing status
changes are not broadcast to hub clusters. This means that the exchange of routing
status changes can be confined to the dynamic routing sector.
In the case of a local trunk failure, the forwarding table is updated immediately by
the route builder. Routes are also re-calculated immediately and the status change
distributed to the other switches.
When a switch receives a dynamic routing status update from another dynamic
routing switch, it updates its own forwarding table immediately.
Debouncing is applied to bursts of status updates to prevent excessive updates being
exchanged.
Forwarding function
The forwarding function uses the forwarding table, constructed by the route builder
to check the frame routing header for the destination GFR address and forwards the
frame to the appropriate trunk circuit. The route builder updates the forwarding
tables when link state or topology changes occur in the network.
The complex routing calculations are performed off-line by the route builder. The
forwarding table is the result of these calculations. Thus forwarding becomes a
highly efficient operation which takes place in the data path.
Forwarding functions on source and destination switches perform frame relay
encapsulation and decapsulation. Forwarding functions on intermediate switches
transmit the frames between the consecutive trunks. The forwarding function on a
destination switch detects that the frame is addressed to its own GFR address and
delivers the frame to X.25 running on this switch.
Frame relay encapsulation

The 36120 MainStreet X.25 switch uses a proprietary encapsulation technique that
adds a minimum of overhead to the packet (see Figure 27.6-7).
27.6-10
(400)
X.25 Serivce

NNP 95-2035-01-00-B

Red
Time
to live
0
EA
0
EA
Data Link
Connection
Identifier
(DLCI)
DE
Flag
1 1
BECN
FR type FECN
C/R
Figure 27.6-7: GFR Information Frame Format
Frame relay header

(Note: 3 bytes
if sent over
FASTbus)
Application
Destination
Hub #
GFR header
Destination
Leaf #
FR type
FECN
BECN
Spare
Spare Remote
RTP header
VCon ID
GFI
Q D 0
LC group
number
LCN
X.25 packet
P(R)
P(S)
User data
(variable)
Q.2110
SD
RTP trailer
PDU
TI.618 Frame
Check Sequence
8673
X.25 Service
(400)
27.6-11


NNP 95-2035-01-00-B
How the GFR routes frames

The GFR is configured for either direct link routing or dynamic routing.
How the GFR applies direct link routing
When direct link routing is applied the forwarding table indicates the adjacent
switch and the trunk to which a frame should be forwarded for a given destination.
Every adjacent switch to which the GFR is connected is listed in the forwarding
table, together with the connecting trunks and their costs.
How the GFR applies dynamic routing
Dynamic routing is used between hub nodes in networks where the hubs are not
fully meshed. The routing tables of hubs configured for dynamic routing form a
network trunk state database. The database is dynamically maintained and lists all
the hubs and trunks in the dynamic sector of the network.
Each hub node trunk state database contains topology information supplied by
nodes adjacent to it. Information supplied by an adjacent hub includes information
on the adjacent nodes. In this way the route builder constructs routing tables for the
active dynamic routing domain. When the connection status of a hub changes due
to trunk or node failure, it broadcasts the new information to its adjacent hubs. This
is disseminated throughout the dynamic routing domain within a short period. The
forwarding table to be used during data switching is constructed by combining
dynamic routing table information with direct link routing table information. Figure
27.6-8 shows a network with four hubs and a forwarding table which would be
generated by the GFR route builder on hub 10-0. In the example, hub 10-0 is
configured with a D value of 1.
The forwarding table in a GFR lists reachable hub switches and adjacent leaf
switches and indicates the trunks to be used to reach them (see Table 27.6-1). When
more than one trunk is available to a reachable switch, it lists up to three trunks in
order of preference. To destinations accessed through intermediate switches, when
more than one adjacent switch can provide a route, it lists trunks for up to three
adjacent switches, in order of preference. It also indicates route costs. A route is the
path from an entry hub switch through a number of intermediate hubs to an exit hub
switch.
A least-cost algorithm is applied to select the best route.
When topology, configuration and status changes occur, all the dynamic routing
hubs in the network broadcast the new information. The changes are automatically
reflected in the trunk state database and then applied to the forwarding tables.
27.6-12
(400)
X.25 Serivce

NNP 95-2035-01-00-B

Figure 27.6-8: Example of Hub Domain Dynamic Routing

40-10
1
30-10
3
Hub
40-0
Hub
30-0
30-11
Trunk ID
Trunk cost
1
20-10
Hub 2
20-0 3
4
1
1
4
Hub
2 10-0 5
7
6
1
10-nn
10-12
20-11
10-10
1
10-11
10432
Table 27.6-1: Forwarding Table for Hub 10-0

GFR
Trunk
Cost
Load
Balancing
!st choice
Alternate Routes
2nd Choice
Cost
3rd Choice
Cost
10-10
T7
No
10-11
T6
No
10-12
T5
No
10-nn
T4
No
20-0
T2
Yes
T1
T3
30-0
T3
Yes
T2
T1
40-0
T2
Yes
T1
T3
Forwarding principles
The forwarding principles encompass routing system characteristics and specific
forwarding rules.
X.25 Service
(400)
27.6-13


NNP 95-2035-01-00-B
Routing system characteristics

The GFR has the following set of routing system characteristics.
The GFR always selects the lowest cost route according to the costs assigned to
the trunks which make up the route and the transit costs of switches on the route.
Frames can be forwarded a maximum of seven times.
Hub switches perform routing within and between leaf domains. Leaf number 0
identifies the actual hub switch, while leaf numbers 1 to 9 identify the hub switch
aliases.
Only hub switches can function as transit switches. Leaf switches can only route
traffic they originate, as well as retransmitting reversed frames.
When forwarding frames the GFR applies the rules detailed below. The GFR applies
the rules in ascending order. For example, if Rule 1 cannot be applied, the GFR
attempts to apply Rule 2.
Although the route selection process is performed for each frame, frames
transmitted between two switches normally follow the same path, except when load
balancing is enabled. In the absence of load balancing, the transmission path changes
only when the network topology changes, a trunk failure occurs, or a node goes out
of service. When load balancing is enabled, X.25 packets associated with the same
virtual call may be transmitted over different backbone trunks to their destination.
Direct link forwarding rules
The following forwarding rules are applied for direct link routing.
1. Select the lowest cost trunk directly connected to the destination switch.
2. Select the lowest cost trunk to the hub of the destination leaf switch.
3. Select the lowest cost trunk to the alias with the lowest leaf number for the
destination leaf domain.
4. If the source switch is a leaf switch, forward the frames on the lowest cost trunk
to its own hub switch.
If the switch is a hub switch, other than the destination hub switch, forward the
frames on the lowest cost trunk to a hub switch participating in dynamic routing.
5. Select the lowest cost trunk to the alias of the forwarding hub switch.
Hub domain dynamic routing forwarding rules
The following forwarding rules are applied for hub domain dynamic routing.
1. Select the lowest cost trunk connected to the destination leaf switch.
2. Select the lowest cost route to the hub of the destination leaf domain.
3. Select the lowest cost route to the alias with the lowest leaf number for the
destination leaf domain.
4. Select the lowest cost route to the alias of the forwarding hub switch.
27.6-14
(400)
X.25 Serivce

NNP 95-2035-01-00-B

Load balancing forwarding rule

This rule applies to each forwarding switch which has load balancing enabled and
two or three trunks providing routes to a destination where the route costs fall
within the D cost of the forwarding switch.
Forward frames in equal proportion on these trunks.
Redundant routing
Routing redundancy is achieved by providing alternative routes or by reversing
frames when they cannot be forwarded, thus routing around out of service switches
or trunks.
Redundant routing principles
To provide redundancy in network routing, alternate paths must be available
between switches. The three methods of providing redundancy are listed below.
Trunk redundancy
Leaf switches may have multiple trunks to their hub switch.

Switch redundancy
Every hub switch can have an alias to assume its routing responsibilities in case
of failure.
Dynamic routing redundancy
Establish a dynamic routing topology to re-route around failed trunks.
The GFR also provides a redundant routing function that physically reverses frames.
Frame reversal
The GFR provides a routing redundancy mechanism that physically reverses frames
when routes to a particular switch are not available.
Frame reversal occurs when a hub switch cannot find a route to the destination
switch because of a trunk failure or an out-of-service node. This GFR sends the frame
back along the trunk to the previous switch and sets a redundancy flag. A reversed
frame can only be returned along the trunk on which it was received, since the
switch has no record of the origin for the frame.
When a switch receives a reversed frame with the redundancy bit set, it attempts to
find a route to the destination switch other than the trunk to the switch which
reversed the frame. If an alternative route is available, the GFR resets the
redundancy bit and forwards the frame. If no alternative route is available, the
switch discards the frame. A frame may transmitted up to seven times, after which
it is discarded. This implies that a frame may only be reversed three times before it
is discarded.
Figure 27.6-9 shows an example of frames that are successfully routed to the
destination switch using frame reversal.
X.25 Service
(400)
27.6-15


NNP 95-2035-01-00-B
Figure 27.6-9: Successful Routing Using Frame Reversal

1
10-10
10-0
12-0
12-0
3
4
1
2
3
4
5
Forwarding rule 2
Forwarding rule 2
Redundant forwarding rule 1
Forwarding rule 3
Forwarding rule 1
14-0
(12-1)
10430
Redundant routing forwarding rules

When redundant routing is enabled, a switch may reverse a frame that it cannot
deliver.
These rules apply to switches on which redundant routing is enabled.
1. A switch receiving a frame which it cannot forward sets a redundancy flag in the
frame and returns the frame on the receiving trunk.
2. A switch receiving a frame with the redundancy flag set resets the redundancy
flag and applies the forwarding rules, ignoring trunks directly connected to the
switch which reversed the frame.
How the switch handles trunk failures

The following sequence describes how a 36120 MainStreet X.25 switch handles trunk
failures.
1. If a TDM trunk fails, the 3600 node initially attempts to use RAP+ID protection.
2. The 46020 is able to reroute a frame relay PVC that is used for an X.25 backbone
trunk.
3. If all direct trunks to the destination switch fail, the switch routes the frames
according to the forwarding rules, using aliases.
4. In the dynamic routing sector each switch broadcasts trunk state updates to
enable dynamic routing around failures.
27.6-16
(400)
X.25 Serivce

NNP 95-2035-01-00-B
27.6.3

Viewing the GFR Parameters

Figure 27.6-10 shows the NMTI display for the GFR parameters.
Figure 27.6-10: GFR Parameter Configuration Display
X25FRE Stations:nn
PA11-H1-00
Toronto:A
Alarms:1
11-May-1997
8:35a
GFR PARAMETERS
-------------GFR Address
:23-0
Redundant Routing
:Disabled
Load Balancing
:Disabled
Hub Domain Dynamic Routing :No
Delta Value
:0
List of Aliases
:90-2
80-1
12-7
CONFIG SWITCH GFR

F1-GFR_ADDR
F6-
F2-ROUTING
F7-
F3-ALIAS
F8-CANCEL
F4-FASTBUS
F9-QUIT
F5F10-PROCEED
To view GFR parameters

CONFIG SWITCH GFR [FASTBUS]
27.6.4
Configuring the GFR Parameters

This section describes the GFR parameters and provides configuration guidelines.
The parameters are ordered as they appear on the NMTI display.
GFR address
You must assign a GFR address to every 36120 MainStreet X.25 switch. The GFR
address designates the switch as a hub or leaf switch and provides it with a unique
routing address in the network. The hub number identifies the switch as a member
of a particular leaf domain, while the leaf number identifies the switch as either a
hub or leaf switch in that domain.
A hub switch has a hub number from 10 to 255, and a leaf number as 0; for example,
110-0. A leaf switch has a hub number from 10 to 255 and a leaf number from 10 to
255, for example, 110-11.
X.25 Service
(400)
27.6-17


NNP 95-2035-01-00-B
Caution
When you change the value of this parameter, the switch resets and rebuilds the
routing table, during which time all trunks are out of service. Once the switch is
operational, change the value only during periods of minimal network activity.
Range
Table 27.6-2 summarizes the allowable values for configuring GFR addresses.
Table 27.6-2: GFR Address Assignment
Hub Switch
Leaf Switch
Hub Number Range
Leaf Number Range
Hub Number Range
Leaf Number Range
10 to 255
10 to 255
10 to 255
Default
None
Redundant routing
This parameter specifies whether the GFR on the card performs frame reversal
during routing. When redundant routing is enabled, the GFR physically reverses
those frames that cannot be forwarded due to a trunk failure or an out-of-service
switch. A reversed frame returns to the last switch from which it came, where the
GFR attempts to find an alternate route to the destination switch. If no alternate
route is available, the switch discards the frame.
Caution
When you change the value of this parameter, the switch rebuilds the routing table,
during which time all trunks are out of service.
Options
Enabled or Disabled
Default
Disabled
27.6-18
(400)
X.25 Serivce

NNP 95-2035-01-00-B

Load balancing
Trunk loads can be balanced using the load balancing techniques. It is a cost effective
method of bandwidth utilization when there are two or three parallel routes
between switches.
Caution
The decision to use a load balancing topology should be carefully considered for the
following reasons:
To employ load balancing, it must be enabled on every switch across the entire
network.
It may adversely affect RTP performance on non-load balanced links by delaying
retransmission requests when frame loss occurs.
If load balancing is employed on parallel GFR trunks of unequal speeds,
transmission delays on the slower trunk may degrade performance by causing
excessive RTP retransmission requests.
Options
Enabled or Disabled
Default
Disabled

Dynamic routing is applied between hub nodes in networks where the hubs are not
fully meshed. There may be a core of hubs configured for dynamic routing with the
remainder of the hub domain made up of fully meshed hub clusters.
Caution
When you change the value of this parameter, the switch rebuilds the routing table,
Options
Yes or No
Default
No
X.25 Service
(400)
27.6-19


NNP 95-2035-01-00-B
Delta value
The Delta Value (D) is a management device which prevents the GFR from using
unacceptable alternative routes. Network operators can restrict balancing on certain
routes based on trunk cost aggregates. The D value is the maximum aggregate cost
difference permitted between two alternative routes used for load balancing. A
route may be utilized if its cost does not exceed the preferred route cost plus the D
value.
For example assume a destination can be reached by a preferred route and two
alternatives. The first choice route cost is 5, the second choice route cost is 7 and the
third choice route cost is 8. A D value of 2 allows the first choice and second choice
routes to be used but precludes the use of the third choice.
Range
0 to 255
Default
0
List of aliases
An alias is a GFR address that a hub switch assumes in order to route traffic on
behalf of another hub switch. Each alias is an alternate GFR address for another hub
switch.
Only hub switches can be assigned aliases. Assigning an alias is similar to assigning
a GFR address but the leaf number must be from 1 to 9.
Cards functioning as hub switches can have a maximum of three aliases. This means
a switch can assume the task of routing traffic in four different leaf domains,
including its own.
Caution
When you add or delete an alias, the GFR rebuilds the routing table, during which
time all trunks are out of service.
Range
Table 27.6-3 summarizes the allowable values for configuring aliases.
27.6-20
(400)
X.25 Serivce

NNP 95-2035-01-00-B

Table 27.6-3: Alias Assignment

Card Type
Alias Format
Hub Number Range
Leaf Number Range
PE
10 to 255
1 to 9
X.25 FRE
10 to 255
1 to 9
Default
None
GFR transit cost

The GFR transit cost forms part of an overall route cost in the dynamic hub domain.
This parameter is only displayed if Hub Domain Dynamic Routing is set to Yes.
Range
0 - 255
Default
0
Rate enforcement state

This parameter specifies whether the switch enforces the class-of-service values for
FASTbus trunks. This parameter cannot be configured on Release 1.2 and is
permanently disabled. This parameter will be enabled in a future release.
Aggregate committed information rate

This parameter specifies the aggregate CIR for all FASTbus trunks. The parameter is
not supported on Release 1.2.
Aggregate committed burst size

This parameter specifies the aggregate Bc for all FASTbus trunks. The parameter is
not supported on Release 1.2.
X.25 Service
(400)
27.6-21


NNP 95-2035-01-00-B
Restrictions and limitations

Observe the following restrictions and limitations when configuring the GFR
parameters.
Hub switches must have a leaf number of 0.

Only hub switches can have aliases.
Leaf numbers 1 to 9 are reserved for aliases. A maximum of three aliases may be
configured on one hub switch.

A hub cannot be an alias of itself.
A hub can only be an alias of another hub.
A GFR address cannot be changed if either the current or the new address prefix
is defined as GAT.

Once you configure the GFR address on PE or X.25 FRE cards connected to a
FASTbus, if the other parameters are also configured, the automatic FASTbus trunks
go in service.
Caution
When you change the GFR address, the switch resets and rebuilds the routing table,
When you change the values of the following parameters, the switch does not reset
but rebuilds the routing table and all trunks are out of service for a short time.
Redundant routing
Aliases
Configuring a GFR for dynamic routing increases the network overhead when
trunks state changes occur.
Configuring the network for load balancing may degrade the performance of
non-load balanced routes when frames are dropped.
You can change the values of the following parameters at any time with no
27.6-22
Rate Enforcement
Aggregate CIR
Aggregate Bc
Transit cost
Delta cost
(400)
X.25 Serivce

NNP 95-2035-01-00-B

To configure the GFR parameters

CONFIG SWITCH GFR
GFR_ADDR
ROUTING
ALIAS
FASTBUS
<hub-leaf>
ADD
DELETE
<alias_id>
DELTA REDUNDANCY
LOAD_BAL
<delta>
ENABLED/DISABLED
CIR
BC
<cir>
<bc>
RATE_ENF
ENABLED/DISABLED
SK000404
where
hub-leaf is the GFR address in the format nnn-nnn
delta is 0 to 256
alias_id is alias for the hub in the format nnn-n
cir is 0* to 8 Mb/s
bc is 0* to 40 Mb
X.25 Service
(400)
27.6-23

NNP 95-2035-01-00-B
27.7
27.7 Call Routing

Call Routing
This chapter describes how to configure the call routing functionality for a 36120
MainStreet X.25 switch.
For information about configuring the connectionless routing system on the switch,
see chapter 27.6.
27.7.1
Understanding Call Routing

Call routing is the process by which calls are routed through the network based on
the addresses of the destination X.25 devices. 36120 MainStreet X.25 supports
flexible address assignment and numbering plan usage to provide the following call
routing capabilities.
A network can support both E.164 and X.121 address formats simultaneously.
Calls can be made to the network using either of the address formats.
Multiple networks can share the same X.121 DNIC. The digits following the
DNIC are used to differentiate among the networks.

A network can have multiple X.121 DNICs. Calls can be made to a network using
any of the DNICs for that network.
A network can support multiple links to another network.
A 36120 MainStreet X.25 network supports three variations of call routing: basic
routing, gateway and network-wide hunt group routing. The GAT configured on
the switch determines which type is used for each call.
Global Address Table

When a Call Request packet arrives at an originating X.25 switch, the switch consults
the GAT to determine the destination switch for the call and the type of call routing
required. As shown in Figure 27.7-1, the GAT consists of the following fields:
Address Prefix
GFR Address
XAC
Type
Priority
Weight
Link Status
The network operator configures the GAT on every 36120 MainStreet X.25 switch
manually or by using the MainStreetXpress 46020 Network Manager. The GATs
must be identical on all switches in a network.
X.25 Service
(400)
27.7-1
27.7 Call Routing


NNP 95-2035-01-00-B
Figure 27.7-1: Global Address Table Display

X25FRE Stations:nn
PA11-H1-00
Toronto:A
Alarms:1
11-May-1997
8:35a
GLOBAL ADDRESS TABLE

Address Prefix
GFR Addr
XAC
Type
Priority
Weight Link Status
-------------------------------------------------------------------------------x30222
23-32
0
X.25
------x302221
23-32
6
X.25 Gateway
8
4
Down
x30223
25-10
8
X.25 Gateway
9
1
Up
x3353
30-0
10
X.75 Gateway
1
8
Down
e4169671111
35-10
15
Hunt Group
1
5
Down
e613730
38-0
0
X.25
-------
CONFIG SWITCH ADR_PREFIX "?-?"

Enter GFR address, (hub-leaf) or address prefix ([npi]nnn...)
F1-PREVIOUS
F2-NEXT
F3-DELETE_ALL
F4F6F7F8-CANCEL
F9-QUIT
F5F10-
Every entry in the GAT has an address prefix, a GFR address, and address prefix
type. The address prefix type field determines whether the switch uses the basic
routing, hunt group or gateway routing method to route calls. If the address prefix
type is X.25, the switch uses basic routing. If the address prefix type is X.25 gateway,
X.75 gateway or hunt group, gateway routing is used. Gateway routing requires that
an XAC be specified in the GAT entry. An XAC configured as an X.25 or X.75
gateway can have multiple address prefixes associated with it, but only one NUA.
Address prefixes and GFR addresses
Address prefixes are variable-length strings that consist of the first n digits of a range
of addresses. In the case of basic routing, the GAT maps each address prefix to a GFR
address that represents the destination switch for addresses that match the address
prefix. For each gateway address prefix, the GAT contains the set of GFR addresses
and XAC number that support the specified address prefix. The number of address
prefixes required depends on the size of the network.
When an originating X.25 switch routes a call, the switch selects the address prefix
that most closely matches the called address, and forwards the Incoming Call packet
to the switch with the corresponding GFR address. This can be the local switch or a
remote switch. While address prefixes can overlap, the switch always chooses the
address prefix that matches the largest number of digits in the called address.
Address prefixes can be configured for multiple routing. Each route has an
associated address prefix type, priority and weight that are used to determine the
call path. For every call, the priority and weight of each available destination link
address prefix is evaluated to select the next route.
27.7-2
(400)
X.25 Serivce

NNP 95-2035-01-00-B
27.7 Call Routing

Address prefixes are entered in the GAT in X.121 international data number format
(DNIC+NTN) or E.164 international telephony number format (CC+NSN), and are
1 to 19 digits in length. Because a called address is processed according to the
address translation table for the XAC before it is sent to the GAT, the switch always
searches the GAT using the internal address format. See section 27.14.9 for
information about the address translation table and internal address formats.
The entries in the GAT are sorted in ascending numerical order by the address prefix
and GFR address respectively.
The following GAT example shows the use of address prefixes and GFR addresses:
all calls destined for addresses beginning with 1234 are routed to switch 15-11, with
the exception of calls to addresses beginning with 12345, which are routed to switch
15-22.
Address Prefix
GFR Address
XAC
Type
Priority
Weight
----------x1234
15-11
X.25
---
---
x12345
15-22
X.25
---
---
Using the wildcard character in GAT address prefixes

A wildcard character (?) can be used to modify address prefixes and create more
flexible routing schemes. There are no restrictions on the position and number of
occurrences of the wildcard character in the address prefix.
The following examples show the use of the wildcard character. The example below
is similar to the previous example, except that a minimum of five digits are required
to match the address prefix 1234?. Calls destined for addresses beginning with 12345
are routed to switch 15-22. All other calls with a destination of 1234x (for example,
12341, 12342, 12343, 12344, 12346...) are routed through 15-11, but the 4-digit address
1234 is not routed.
Address Prefix
GFR Address
XAC
Type
Priority
Weight
-----------
X.25 Service
x1234?
15-11
X.25
---
---
x12345
15-22
X.25
---
---
(400)
27.7-3
27.7 Call Routing


NNP 95-2035-01-00-B
In the example below, all calls destined for addresses beginning with 1111 are routed
to switch 15-31, while addresses 1011, 1211, 1311,...1911 are routed to switch 15-42.
Address Prefix
GFR Address
XAC
Type
Priority
Weight
----------x1111
15-31
X.25
---
---
x1?11
15-42
X.25
---
---
In the example below, all calls destined to addresses beginning with 444 are routed
to switch 15-17, while all other addresses beginning with 44 are routed to switch
10-11.
Address Prefix
GFR Address
XAC
Type
Priority
Weight
-----------x44?
10-11
X.25
---
---
x444?
15-17
X.25
---
---
Address prefix types and XACs

The Type field specifies whether a particular GAT entry is used to route calls to an
X.25 access line, an X.25 gateway link, an X.75 gateway link or a network-wide hunt
group.
By setting the address prefix type to Hunt Group, it is defined as a member of a
network-wide hunt group. The XAC itself is not a a network-wide hunt group. For
switch-wide hunt groups, all members are limited to a single switch. When the
address prefix is X.25, the switch performs basic routing: addresses matching the
address prefix are routed to the switch with the corresponding GFR address, at
which point local switching occurs. Local switching is done according to the LAT
configured on the destination switch. The subsection Local Address Table
describes the LAT in more detail.
When the address prefix type address prefix is X.25 gateway, X.75 gateway or hunt
group, an XAC is specified to allow the switch to perform gateway routing:
addresses matching the address prefix are routed to the switch with the
corresponding GFR address, at which point the call is routed to the specified XAC.
Section 27.7.3 describes gateway routing in more detail.
27.7-4
(400)
X.25 Serivce

NNP 95-2035-01-00-B
27.7 Call Routing

Shared gateway links

By assigning different address prefixes to the same XAC, you can configure gateway
links that support multiple DNICs. Figure 27.7-2 and the following GAT example
show this scenario.
Address Prefix
GFR Address
XAC
Type
Priority
Weight
-----------x3110
10-10
X.25
---
---
x1000
10-10
15
X.75
x2000
10-10
15
X.75
x3000
10-10
15
X.75
x4000
10-10
15
X.75
Figure 27.7-2: Multiple Address Prefixes on a Link
Network
P
x3000
Network
X
Network
Y
x3110
Network
Q
x4000
x2000
Network
R
x1000
9477
The GAT at the gateway switch for network X is configured such that calls to
networks Y, P, Q and R are routed to XAC 15, which supports link A.
Priorities and weights
The use of priorities and weights enables load sharing, redundancy and link
prioritization in gateway routing. When the same address prefix is assigned to
multiple links, the switch uses the configured priorities and weights to determine
the route.
X.25 Service
(400)
27.7-5
27.7 Call Routing


NNP 95-2035-01-00-B
When duplicate address prefixes are configured in the GAT, the switch selects the
preferred route in the following order.
the link with the highest priority is chosen (1>15)

if the priorities are equal, the calls are assigned in a round robin fashion, starting
with the lowest local XAC number and taking the weights into account. See the
example in Table 27.7-1
The priority field is used to prioritize links when more than one link supports the
same address prefix. The switch supports priorities ranging from 1 to 15, where 1 is
the highest priority. Figure 27.7-3 shows the use of priorities during gateway routing
between non-adjacent X.75 networks. Based on the assigned priorities, calls from
network A to network D are routed through network C.
Calls are always routed to links of a higher priority unless those links are
unavailable. For example, if link A-C is assigned priority 1 and link A- B is assigned
priority 2, only link A-C is used to route calls to D; link A-B is used only if link A-C
is unavailable.
Figure 27.7-3: Example of How Priorities Are Used
Network
D
Network
C
Network
B
Network
A
(Newbridge)
Priority 2
Priority 1
(low cost route)
9454
The weight field is used to specify the relative number of calls routed to links with
the same priority. The switch supports weights ranging from 1 to 15, where the
higher the number, the greater the number of calls on the link. The weight field has
significance only when two or more links support the same address prefix and have
the same priority. For example, if links A and B are both priority 1 links for address
prefix 2045, and the weights are 2 and 1 respectively, link A receives two calls for
every one call routed to link B; however, if link A has a priority of 1 and link B has a
priority of 2, the weight field has no significance.
Table 27.7-1 shows how weights work. Links A, C and D are the preferred links for
address prefix 3022; links B and E are used only if all the preferred links are
unavailable. The weight field specifies how calls are distributed across the preferred
links: for every ten calls routed to address prefix 3022, six calls go to link A, three
calls go to link C and one call goes to link D. Link A receives calls 1, 4, 6, 8, 9 and 10;
link C receives calls 2, 5 and 7; and link D receives call 3. The eleventh call is sent to
link A and the cycle repeats.
27.7-6
(400)
X.25 Serivce

NNP 95-2035-01-00-B
27.7 Call Routing

Table 27.7-1: Example of How Weights Are Used

Link
Address Prefix
Priority
Weight
Comments
x3022
A preferred link with the highest weight;

receives 60% of all calls.
x3022
Used only when links A, C and D are

unavailable.
x3022
A preferred link with the second-highest

weight; receives 30% of all calls.
x3022
A preferred link with the lowest weight;

receives 10% of all calls.
x3022
Used only when links A, C and D are

unavailable.
Load sharing
Figure 27.7-4 shows an example of load sharing using weights. The GAT at the
gateway switch for network X is configured as follows.
Address Prefix
GFR Address
XAC
Type
Priority
Weight
----------x3110
10-0
X.25
---
---
x3115
10-0
11
X.75
x3115
10-0
22
X.75
XAC 11 supports link A and XAC 22 supports link B. While both links have equal
priorities (1), they have different weights (2 and 1 respectively). When calls are
established from network X to network Y, both links are used, but link A receives
twice as many calls as link B.
Figure 27.7-4: Load Sharing Using Different Weights
Network
X
x3110
Network
Y
x3115
9476
X.25 Service
(400)
27.7-7
27.7 Call Routing


NNP 95-2035-01-00-B
Link redundancy
Figure 27.7-5 shows how link redundancy is used with X.75 gateways to route traffic
across a primary transit network, while using a secondary transit network for
backup. The GAT at the gateway switch for network W is configured as follows (the
links supported by the XACs are shown in parentheses).
Address Prefix
GFR Address
XAC
Type
Priority
Weight
-----------x3020
20-0
x3022
20-0
x3022
X.25
---
---
10 (A)
X.75
20-0
20 (B)
X.75
x4204
20-0
10 (A)
X.75
x4204
20-0
20 (B)
X.75
x4624
20-0
10 (A)
X.75
x4624
20-0
20 (B)
X.75
The links configured as priority 1 receive all internetwork calls unless the links fail,
in which case priority 2 links are used. Using this configuration, network W has
redundant routes to networks X, Z and Y. Link A is used for all calls to networks X
and Z, and as a backup to network Y. Link B is used for all calls to network Y, and
as a backup to networks X and Z.
Figure 27.7-5: Route Redundancy Using Priorities
Network
Z
x4624
C
Network
X
x3022
Network
Y
x4204
A
Network
W
x3020
9274
Link status updates

Automatic link status updates are provided for all gateway links in the network. All
gateway links are monitored and all switches in the network are notified when the
status of any link changes. Based on this information, originating switches can avoid
routing calls to links that are out of service.
27.7-8
(400)
X.25 Serivce

NNP 95-2035-01-00-B
27.7 Call Routing

Normally, calls are routed according to the priorities and weights assigned to links:
higher priority links are preferred, and calls are distributed to links of the same
priority based on weights. However, if a link is out of service, information is sent to
each switch indicating that the link is down, and the originating switches select the
next best route.
Calls may be routed to a link that is out of service. This can occur if an originating
switch routes a call to link for which it has not yet received an out-of-service status
indication, the selected link is under flow control, or all LCNs on the link are in use.
In these cases, the destination switch clears the call back to the originating switch,
and the originating switch attempts to reroute the call to a maximum of two
alternative links. This re-routing process is transparent to the network user; the X.25
DTEs do not receive call clears. The link status can be either up or down and is
displayed on the GAT screen on the NMTI.
A status change has to remain in effect for a minimum period of time before it is
distributed to other switches. This is achieved by status filtering at the local switch.
This is to avoid flooding the network with update messages when a link frequently
goes in and out of service.
Local Address Table

The LAT is used in the basic routing process to route calls within a destination
switch. When a call arrives at its destination X.25 switch, the switch consults the LAT
to determine the destination XAC. As shown in Figure 27.7-6, the LAT maps
addresses in internal format (NUAs) to XAC numbers. The switch searches the LAT
for an entry that most closely matches the called address, and sends the call setup
packet to the corresponding X.25 access line.
Figure 27.7-6: Local Address Table Display
X25FRE Stations:nn
PA11-H1-00
Toronto:A
Alarms:1
11-May-1997
8:35a
LOCAL ADDRESS TABLE

-------------------
NUA
XAC
NUA
XAC
NUA
XAC
---------------------------------------------------------------------------------x302011888801
10
x30201187277960 160
x302011888811
23
x30201187277961 161
x302011888822
25
x30201187277962 162
x302011888833
26
x30201187277963 163
x302011888844
27
x30201187277964 164
x302011888855
28
x302011888866
29
x302011888872
33
x302011888873
35
x302011888875
37
x302011888878
39
CONFIG X25_ACCESS NUA "??"
Enter network user address. ([npi]nnn...)
F1-PREVIOUS
F2-NEXT
F3F6F7F8-CANCEL
X.25 Service
(400)
F4F9-QUIT
F5F10-
27.7-9
27.7 Call Routing


NNP 95-2035-01-00-B
The LAT is built dynamically when NUAs are assigned to XACs (see chapter 27.15).
The LAT can contain full or partial addresses. In most cases, the full address of the
user device is defined and assigned to the XAC. However, partial addresses allow
network operators to use the basic routing process, rather than the gateway routing
process, to route calls to X.25 gateway links. In such cases, the network is configured
to route X.25 gateway calls exactly like DTE-to-DTE calls. At the XAC that serves as
the gateway interface, a partial address is used, since it may be impossible to define
every possible called address on the interface. The partial address, similar to the
address prefix used in the GAT, allows the switch to route gateway calls
appropriately.
The following example of a LAT shows a routing scenario where two X.25 gateway
links are configured on the switch. All calls destined for remote network addresses
beginning with 3020111 are routed to XAC 17, while all calls to addresses beginning
with 3020222 are routed to XAC 39.
LOCAL ADDRESS TABLE
NUA
XAC
NUA
XAC
--------------------------------------------------------x3020111
17
x3020222
39
Note
The LAT is never used by the gateway routing process. Both the originating and
destination switches use the GAT exclusively to perform gateway routing.
X.75 interface addresses in the LAT

The LAT displays every NUA-to-XAC assignment on the switch. This includes the
NUAs that are configured and assigned to X.75 interfaces (that is, XACs with a
service type of X.75 gateway). Although these LAT entries are not used in the call
routing process, they are required because the NUA functions as the remote end of
an IPVC. See chapter 28.1 for information about IPVCs.
27.7.2
Basic Routing
Basic routing occurs as follows at the originating and destination switches.
1. The originating switch matches the called address to an entry in the GAT,
determines the destination switch, and routes the Call Request packet
accordingly. This is referred to as remote switching.
2. The destination switch matches the called address to an entry in the LAT,
determines the destination access line, and routes the Incoming Call packet
accordingly. This is referred to as local switching.
27.7-10
(400)
X.25 Serivce

NNP 95-2035-01-00-B
27.7 Call Routing

With basic routing, GAT consultation occurs only at originating switches, while LAT
consultation occurs only at destination switches. For calls that originate and
terminate on the same X.25 switch, the two tables are consulted locally before the
calls are routed to the appropriate X.25 access line. Alternatively, calls that originate
and terminate on different X.25 switches are routed over backbone trunks (GFR
trunks), and may traverse several intermediate switches before reaching the
destination switch where they are locally switched.
The basic routing mechanism is used to route calls to switch-wide hunt groups. Once
the LAT has been consulted and it has been determined that the called address refers
to a switch-wide hunt group, the appropriate member is selected. Calls are allocated
to switch-wide hunt group members in a round-robin fashion.
X.25 Service
(400)
27.7-11
27.7 Call Routing


NNP 95-2035-01-00-B
How basic routing occurs in a virtual call setup

The following sequence describes the basic call routing process during the setup
phase for a virtual call.
1. The originating X.25 switch receives a Call Request packet from an X.25 line. The
called and calling addresses are converted to internal format according to the
address translation table for the XAC.
2. The switch matches the first n digits of the called address with an address prefix
in the GAT. The GAT entry indicates that basic routing is used (the address
prefix type is X.25) and specifies the X.25 switch that supports the called address.
a. If the called address is on the same X.25 switch, the packet is routed locally (go
to step 6).
b. If the called address is on a remote X.25 switch, the switch adds a routing
header containing the GFR address to the packet and sends the packet to the
GFR for routing (go to step 3).
c. If the called address does not match an entry in the GAT, the switch clears the
call.
3. The GFR consults its routing table to determine the best backbone trunk,
encapsulates the packet in a frame relay frame, and queues the frame on the
appropriate backbone trunk for transmission.
4. The GFR at the other end of the backbone trunk receives the frame and searches
its routing table using the GFR address to determine where to send the packet.
a. If the GFR address matches its own address, the frame is routed locally (go to
steps 5).
b. If the GFR address matches a remote switch, the frame is routed as in step 3.
5. At the destination switch, the frame is decapsulated and the routing header is
stripped off.
6. The destination switch consults the LAT to determine which XAC receives the
Call Request or Incoming Call packet.
a. If the called address is in the LAT, the call is routed based on the configured
parameters of the address and XAC (go to step 7). For example, if the called
address is a hunt group address, the switch chooses the access line based on the
hunt group configuration. If the access line is down, the call may be redirected if
the Call Redirection facility is configured.
b. If the called address is not in the LAT and the address prefix type is X.25
shared (not supported in Release 1.2), the switch consults the GAT for the
alternative route. The process repeats as in step 2.
c. If the called address is not in the LAT and the address prefix type is X.25, the
switch clears the call.
7. The switch validates the selected call options. The called and calling addresses
are converted to external format and the call is forwarded to the appropriate
X.25 access line.
In the reverse direction, the destination switch knows the GFR address of the
originating switch, so the Call Accepted packet is sent directly back to the
originating switch without routing on the X.121 or E.164 address. When the Call
Accepted packet reaches the originating switch, both switches know the GFR
address of the other switch. These are the routing addresses that are subsequently
used to route all packets associated with the call.
27.7-12
(400)
X.25 Serivce

NNP 95-2035-01-00-B
27.7 Call Routing

Figure 27.7-7 shows the call routing logic that is common to both basic and gateway
routing at the originating switch; these activities occur before the switch determines
whether to use basic or gateway routing. Figures 27.7-8 and 27.7-9 show the
subsequent basic routing logic at the originating and destination switches.
Figure 27.7-7: Call Routing Process at the Originating Switch: Basic and Gateway
START
Receive Call Request packet
Convert addresses to internal format
Address translation
YES
Call intercept required?

(NUI, mnemonic addressing)
Send to validation server
NO
Process facilities/utilities
Search GAT for matching address

prefix (local or remote entries can
be returned)
NO
Entry found in GAT?
Send clear packet to DTE/STE
YES
Gateway
routing required?
NO
B1
YES
C
9455
X.25 Service
(400)
27.7-13
27.7 Call Routing


NNP 95-2035-01-00-B
Figure 27.7-8: Basic Routing at the Originating Switch
B1
Local address prefix?
YES
NO
Route available to
remote switch?
Called address
in LAT?
YES
NO
NO
Send clear packet

to DTE/STE
YES
Send/process
Incoming
Call packet
B2
9461
27.7-14
(400)
X.25 Serivce

NNP 95-2035-01-00-B
27.7 Call Routing

Figure 27.7-9: Basic Routing at the Destination Switch
NO
DTE link down,
busy or line refused?
B2
YES
Get next member
Hunt group call?

NO
YES
Substitute called address with

redirection address
Member found?
NO
NO
YES
Maximum
redirections exceeded?
YES
Call redirection
configured?
NO
Clear call
YES
DTE link down,

NO
Insert facilities/utilities
Address translation
Convert address to
external format
Send Incoming Call

packet to X.25 access line
END
9456
X.25 Service
(400)
27.7-15
27.7 Call Routing

27.7.3

NNP 95-2035-01-00-B
Gateway Routing
The 36120 MainStreet X.25 gateway routing feature provides versatile and flexible
routing and addressing capabilities.
Multiple X.75 gateways with the same address prefix within a network can be
used to route calls to the same destination. This functionality:

provides load sharing; calls to a remote network can be routed over multiple
links as opposed to a single link
provides link redundancy; if a link is down, other links are available to route
the call
dynamic status updates are provided for gateway and network-wide hunt group
links. This allows the routing system to avoid links that are out of service.
The network can reroute a call if the call is cleared on one link and another link
with the same address prefix is available. Only certain clear cause and diagnostic
codes will result in call re-routing.
Network-wide hunt groups

Network-wide hunt groups use the gateway routing method. A configuration
option selects whether hunt group address or the member address is signalled as the
called address on the destination X.25 interface. If a clear is received from an X.25
and X.75 gateway link, the call is rerouted depending on the cause and diagnostic
codes. For example, a Network Congestion clear cause code results in call re-routing.
Unlike routing to X.25 and X.75 gateway links, when a DTE clear cause code is
received from a network-wide hunt group member, the call will be rerouted,
provided it is not a fast select with restriction on response call.
The status of network-wide hunt group links is distributed to all switches in the
network through link status updates. This allows switches to avoid routing calls to
links that are out of service.
The number of members in a network-wide hunt group is restricted only by the
number of entries allowed in the GAT (128 for both PE and FRE cards).
Network-wide hunt groups and switch-wide hunt groups cannot be combined.
Gateway routing examples

Figure 27.7-10 shows the flexibility of the gateway addressing and routing scheme.
The DNIC 6550 is shared by networks A, B, F and E.
The Newbridge public network A:
27.7-16
has a direct X.75 link to public network C

routes calls to public network D via network C
has an X.35 gateway link to private network E
has an X.75 gateway link to private network F
has both an X.75 and an X.25 link to private network B, which supports both the
65501 and 65503 address prefixes
(400)
X.25 Serivce

NNP 95-2035-01-00-B
27.7 Call Routing

The two links to network B have to be of different priorities. Network A selects a

route to network B based on the priorities and then acts as a transit or destination
network according to the address prefix type of selected link. For example, if
network A receives an X.75 call from a DTE in network C to a DTE in network B,
network A needs to determine whether it should act as a transit network or as a
destination network. If it uses the X.25 link, it performs the role of the destination
network.
Figure 27.7-10: Shared DNICs
DNIC = 3110
Public network
C
DNIC = 3115
Public network
D
X.75
X.75
DNIC = 6550
Newbridge public
network
A
X.35
DNIC = 655040
Private network
E
X.75
X.35
DNIC = 65501/3
Private network
B
X.75
DNIC = 65502
Private network
F
9161
In the case where two networks share the same DNIC value and use X.75 for
interconnection, the user can specify that the TNIC should not be inserted in transit
calls. This scenario is shown in Figure 27.7-11.
X.25 Service
(400)
27.7-17
27.7 Call Routing


NNP 95-2035-01-00-B
Figure 27.7-11: Network Migration Scenario Using Networks with Shared DNICs
Network C
TNIC = 3410
Network D
TNIC = 2440
Network A
X.75
X.75
TNIC = 2310
Newbridge network
Does not insert TNIC
in transit calls
X.75
Network B
TNIC = 2310
9188
Figure 27.7-12 shows how priorities and weights provide load sharing and
redundancy for X.75 gateway links.
DTEs in network A need to call DTEs in the network D. Network A has two switches
(FRE 1 and FRE 2) with X.75 gateway links. FRE 1 has direct links to networks B and
C, and address prefix 3115 is configured on both links. The link from FRE 1 to
network B has a lower priority than the link from FRE 1 to network C, because the
route from network B to network D has more transit networks.
The two links on FRE 2 have the same priority, but the direct link to network D has
a higher weight. As a result, when calls are made from DTE X to DTE Y, 3 calls are
routed to FRE 2 for every one call that is routed to FRE 1. The priority 2 link on FRE
1 will only be used if all three priority 1 links are down or unavailable.
27.7-18
(400)
X.25 Serivce

NNP 95-2035-01-00-B
27.7 Call Routing

Figure 27.7-12: Use of Priorities and Weights During X.75 Routing
Network C
DNIC = 3110
Network D
DNIC = 3115
X.75
X.75
Network B
DNIC = 2440
X.75
wt =1
pr =1
DTE Y
X.25
X.75
wt =1
pr =1
wt =2
pr =1
X.75
wt =1
pr =2
X.75
FRE 1
FRE 2
FRE 3
Network A
DNIC = 6550
DTE X
wt = weight
pr = priority
9160
Gateway routing process

Gateway routing occurs as follows at the originating and destination switches.
1. The originating switch matches the called address to an entry in the GAT,
determines the destination switch based on the configured priorities and
weights, and routes the Call Request packet accordingly.
2. The destination switch matches the called address to an entry in the GAT,
determines the destination interface based on the configured priorities and
weights, and routes the Incoming Call packet accordingly.
Unlike basic routing, gateway routing requires GAT consultation at both the
originating and destination switches. For calls that originate and terminate on the
same X.25 switch, a single GAT lookup occurs locally before the calls are routed to
the appropriate interface.
X.25 Service
(400)
27.7-19
27.7 Call Routing


NNP 95-2035-01-00-B
Retrying calls
Gateway routing enables calls in the connecting state to be retried when a clear
packet is received at the destination switch. Calls are retried when the switch selects
a route that is unavailable (for example, when the ATB status update is delayed so
that the switch is unaware the link is down), and one of the following conditions
applies:
the call is cleared by a network-wide hunt group DTE

the call is cleared by a gateway with a non-DTE-originated clear cause
Calls are retried up to three times per gateway switch before the call is cleared back
to the originating switch for further re-routing. If a switch is not the originating
switch, it only reroutes within the priority specified by the originating switch.
27.7-20
(400)
X.25 Serivce

NNP 95-2035-01-00-B
27.7 Call Routing

How gateway routing occurs in a virtual call setup

The following sequence describes the gateway call routing process during the setup
phase for a virtual call.
1. The originating X.25 switch receives a Call Request packet from an access line.
The called and calling addresses are converted to internal format according to
the address translation table for the XAC.
2. The switch matches the first n digits of the called address with an address prefix
in the GAT. The GAT entry indicates that gateway routing is used (the address
prefix type is X.25 gateway, X.75 gateway or hunt group), and specifies the X.25
switch and XAC that support the called address.
a. If multiple links support the same address prefix, the switch selects the link
based on the priorities and weights configured.
b. If the called address does not match an entry in the GAT, the switch clears the
call.
3. Based on link status updates, the switch determines if the selected link is
available.
a. If the link is in service and the called address is on the same X.25 switch, the
switch routes the call to the selected link (go to step 9).
b. If the link is in service and the called address is on a remote X.25 switch, the
switch inserts routing information into the call setup packet (priority, weight,
address prefix type), adds a routing header containing the GFR address to the
packet, and sends the packet to the GFR for routing (go to step 4).
c. If the link is out of service, the switch consults the GAT as in step 2 to find an
alternate link. If the maximum number of retries has occurred and no alternate
link exists, the call is cleared.
4. The GFR consults its routing table to determine the best backbone trunk,
encapsulates the packet in a frame relay frame, and queues the frame on the
appropriate backbone trunk for transmission.
5. The GFR at the other end of the backbone trunk receives the frame and searches
its routing table using the GFR address to determine where to send the packet.
a. If the GFR address matches its own address, the switch attempts to route the
call locally (go to step 6).
b. If the GFR address matches a remote switch, the frame is routed as in
number 4.
6. At the destination switch, the frame is decapsulated and the routing header is
stripped off.
7. The destination switch determines if the selected link is available (the GAT is
used). Although the originating switch flagged the link as in service, the link
may now be unavailable as a result of a delayed link status update, congestion,
or all LCNs being in use.
a. If the link is in service, the switch routes the call locally (go to step 9).
b. If the link is out of service, the switch consults the GAT to find an alternate
link. If the maximum number of retries has occurred and no alternate link exists,
the call is cleared.
8. When the GAT contains alternate links, the switch tries to route the call to local
links of the priority specified in the call setup packet.
a. If a local link with the same priority is available, the switch routes the call
X.25 Service
(400)
27.7-21
27.7 Call Routing


NNP 95-2035-01-00-B
locally (go to step 9).

b. If there is no alternate local link with the same priority, the switch clears the
call back to the originating switch and the process repeats from step 2.
9. The switch validates the selected call options. The called and calling addresses
are converted to external format and the call is forwarded to the appropriate
X.25 access line.
In the reverse direction, the destination switch knows the GFR address of the
originating switch, so the Call Accepted packet is sent directly back to the
originating switch without routing on the X.121 or E.164 address. When the Call
Accepted packet reaches the originating switch, both switches know each other's
GFR addresses. These are the routing addresses that are subsequently used to route
all packets associated with the call.
Figure 27.7-7 shows the call routing logic that is common to both basic and gateway
routing at the originating switch; these activities occur before the switch determines
whether to use basic or gateway routing. Figures 27.7-13 and 27.7-14 show the
subsequent gateway routing logic at the originating and destination switches.
Figure 27.7-15 shows what happens when a clear packet is received at the
destination switch while the call is in the connecting state. The call can be retried.
27.7-22
(400)
X.25 Serivce

NNP 95-2035-01-00-B
27.7 Call Routing

Figure 27.7-13: Gateway Routing at the Originating Switch
C
NO
Entry found?
YES
Check ATB status for

selected link
Get next entry from GAT
(local or remote entries can
be returned)
NO
Maximum
number of reroutings
or retries
exceeded?
YES
Link down, busy or line

refused?
NO
YES
YES
Clear call
Remote link?
NO
Address translation
Convert address to
external format
Send/process Incoming
Call packet
D
9458
X.25 Service
(400)
27.7-23
27.7 Call Routing


NNP 95-2035-01-00-B
Figure 27.7-14: Gateway Routing at the Destination Switch
D
NO
Entry found?
YES
Process Incoming Call packet

from originating switch
Get next local entry
from GAT at destination switch
NO
Maximum
number of reroutings
exceeded?
YES
Link down,
NO
YES
Send clear packet to

originating switch
Address translation
Convert address to
external format
Send Incoming
Call packet to X.25/X.75 link
END
9457
27.7-24
(400)
X.25 Serivce

NNP 95-2035-01-00-B
27.7 Call Routing

Figure 27.7-15: Re-routing or Retrying Calls
Receive clear packet
YES
From a DTE?
NO
Hunt group call?
NO
YES
YES
YES
From an X.25 or
or X.75 gateway?
Received at originating
switch?
NO
NO
D
Process facilities/utilities in clear

packet from trunk
Clear
call
END
NO
Clear
call
Retry or reroute
call?
YES
END
C
9460
27.7.4
Viewing Call Routing Tables

From the PE or X.25 FRE NMTI, you can view all entries or a range of entries in the
GAT and the LAT. Figure 27.7-1 shows an example of the GAT. Figure 27.7-6 shows
an example of the LAT.
To view the GAT

CONFIG SWITCH ADDR_PREFX
<hub-leaf>
SHOW_ALL
SHOW_GROUP
SK000405
where hub-leaf is a valid GFR address in the format nnn-nnn
X.25 Service
(400)
27.7-25
27.7 Call Routing


NNP 95-2035-01-00-B
To view the LAT

CONFIG X25_ACCESS NUA
<nua>
SHOW_ALL
SHOW_GROUP
SK000406
where nua is a valid NUA (1 to 19 digits)
27.7.5
Configuring the GAT

The GAT provides each switch with the information required to route calls
anywhere in the network, or to a remote network. Every valid X.25 address and
gateway address in the network must have a corresponding address prefix in the
GAT when configured using the NMTI. The GAT must be updated whenever new
address prefixes are configured on any switch in the network.
The network operator must manually configure the GAT on each switch using the
NMTI. To ensure consistent routing throughout the network, the GAT on every
switch must contain exactly the same entries.
This section describes the GAT parameters and provides configuration guidelines.
Address prefix
This field defines a string of address digits for which the GAT entry applies. When
the switch consults the GAT, it compares the called address to the address prefixes
and selects the closest match.
An address prefix can be entered multiple times in the GAT if the address prefix type
is X.25 Gateway, X.75 Gateway or Hunt Group and the combination of the GFR
address and XAC number is different for each instance of the address prefix.
Address prefixes with the X.25 address prefix type cannot have multiple entries in
the GAT.
Range
1 to 19 digits or wildcards in international X.121 or E.164 address format
Default
None
27.7-26
(400)
X.25 Serivce

NNP 95-2035-01-00-B
27.7 Call Routing

GFR address
This field specifies the GFR address of the switch that supports the corresponding
address prefix. A call is routed to this GFR address when the called address matches
the address prefix. A GFR address can be entered multiple times in the GAT.
Range
hub-leaf in the format nnn-nnn
Default
None
XAC
This field specifies the XAC to which a call is routed when the called address
matches the address prefix. This parameter is not configurable for entries that are
configured with the X.25 address prefix type, because the LAT on the destination
switch specifies the XAC used to route the call. For address prefix types other than
X.25, an XAC must be defined because LATs are not used for gateway routing and
the various XACs supporting the address prefix must be identified.
Range
Default
None
Type
This field specifies the address prefix type that applies to the corresponding address
prefix. If the address prefix type is X.25, the switch uses basic routing. If the address
prefix type is X.25 gateway, X.75 gateway or hunt group, the switch uses gateway
routing and tries to route calls to the specified XAC.
Options
X.25, X.25 Gateway, X.75 Gateway, Hunt Group
Default
None
X.25 Service
(400)
27.7-27
27.7 Call Routing


NNP 95-2035-01-00-B
Priority
This field specifies the priority assigned to the link (switch and XAC) that supports
the corresponding address prefix. This parameter is not configurable for entries that
are configured with the X.25 address prefix type.
Range
1 to 15
Default
1
--- for X.25
Weight
This field specifies the weight assigned to the link (switch and XAC) that supports
the corresponding address prefix. When multiple links have the same address prefix
and priority, calls are distributed among the links based on the relative weights.
This parameter is not configurable for entries that are configured with the X.25
address prefix type.
Range
1 to 15
Default
1
--- for X.25
27.7-28
(400)
X.25 Serivce

NNP 95-2035-01-00-B
27.7 Call Routing


Observe the following restrictions and limitations when configuring address
prefixes.
The operator is prevented from entering address prefixes or making trunk circuit
connections if the GFR address of the switch is not configured (the hub or leaf is
required before any local or remote switching can occur).
The maximum number of extended address prefix entries may not exceed the
value of the maximum number of address prefixes per network (1024 for FRE
and 4096 for PE).
The GFR address for a switch cannot be changed if either the old or the new GFR
address has address prefixes defined.
For an existing extended address prefix entry, only the priority and weight
parameters can be changed. To change any other parameter the entry must be
deleted and re-added.
A maximum of 128 XACs per switch can be configured with extended address
prefixes of type X.25 gateway, X.75 gateway or hunt group.
When configuring an address prefix for local switch the address prefix type must
match the service type of the XAC number if either of them are X.25 or X.75
gateway.
The service type of an XAC cannot be changed to or from X.25 or X.75 gateway if
there are extended address prefixes for that XAC.
If the address prefix type of an extended address prefix entry is X.25 or X.75
gateway, duplicate address prefixes which share the same priority must have the
same address prefix type throughout the network.
In addition to the general dependencies described for configuring address prefixes

for gateway routing, the following dependencies are enforced by network
management when configuring network-wide hunt groups.
The service type of an XAC cannot be changed to or from hunt group if there are
extended address prefixes for that XAC.

If the address prefix type of an extended address prefix entries hunt group, then
duplicate address prefixes which share the same priority must have the same
address prefix type throughout the network.
If the address prefix type of an extended address prefix entry for the local switch
is hunt group, then the service type of the XAC can only be X.25 or XFR.

You can add entries to or delete entries from the GAT at any time with no disruption
of service. The changes are effective for the next call.
X.25 Service
(400)
27.7-29
27.7 Call Routing


NNP 95-2035-01-00-B
To configure the GAT

CONFIG SWITCH ADDR_PREFX <hub-leaf> or <addr_prefix>
<Xnnn>
DELETE
X25
TYPE
PRIORITY
WEIGHT
<pr>
<wt>
X25_GATEW X75_GATEW HUNT_GROUP

SK000743
where
addr_prefix is the address prefix (1 to 19 digits or wildcards)
hub-leaf is the GFR address (nnn-nnn)
Xnnn is the XAC number
pr is 0, 1* 15
wt is 0, 1* 15
27.7-30
(400)
X.25 Serivce

NNP 95-2035-01-00-B
27.8
27.8 Trunk Circuits

Trunk Circuits
This chapter describes how to configure and connect the backbone trunk circuits that
carry traffic between X.25 switches.
27.8.1
Understanding Backbone Trunks

Backbone trunks are frame relay PVCs that connect X.25 switches. When X.25 traffic
is routed between switches, the originating switch encapsulates the X.25 packets in
frame relay frames, and routes the frames to a remote switch over backbone trunks.
The remote switch may be the destination switch or a transit switch that forwards
the frames to other backbone trunks.
Backbone trunks may be provisioned or automatically established.
You can provision backbone trunks on either frame streams (frame relay over
TDM circuits) or FASTbus circuits (frame relay over FDDI circuits). Provisioned
backbone trunks are frame relay PVCs with an associated routing metric or cost.
When a PE or X.25 FRE card is connected to a FASTbus, the card automatically
establishes backbone trunks to the other PE and X.25 FRE cards on the FASTbus
ring once the GFR address is configured. See chapter 25.6 for more information
about automatic FASTbus trunks.
Normally, cards residing on the same 36120 MainStreet system use automatic
FASTbus trunks rather than provisioned backbone trunks, although both methods
are possible.
Trunk circuits
Trunk circuits are virtual GFR ports that terminate backbone trunks. Each trunk
circuit has a configurable cost and poll timer. The PE and X.25 FRE cards support a
maximum of 128 trunk circuits. The actual number supported on a particular switch
is specified by the Number of Trunk Circuits parameter (see chapter 25.5).
Packet size considerations

Before connecting trunk circuits, ensure that the frame streams can support the
maximum possible X.25 packet size. For example, if you configure XACs on the
switch to support packet sizes of 2048 bytes, the Maximum Frame Size parameter on
the frame streams that support backbone trunks must be set to at least 2063 bytes.
Table 27.8-1 shows the dependencies.
X.25 Service
(400)
27.8-1
27.8 Trunk Circuits


NNP 95-2035-01-00-B
Table 27.8-1: Packet and Frame Size Dependencies
27.8.2
Maximum Allowable Packet Size

Configured for XACs on Switch
Required Minimum Frame Size

Supported on the Frame Stream
16 or 32
47
64
79
128
143
256
271
512
527
1024
1039
2048
2063
4096
4111
Viewing Trunk Circuit Configuration Information

From the PE or X.25 FRE NMTI, you can view all the configured trunk circuits, or
view a group of 13 trunks. Figure 27.8-1 shows an example NMTI screen displaying
trunk circuit configuration information.
Figure 27.8-1: CONFIG TRUNK SHOW_ALL Display
X25FRE Stations:nn
PA11-H1-00
Toronto:A
Alarms:1
11-May-1997
8:35a
Trunk Circuit
Cost
Poll Timer
-------------------------------------T1
50
0
T2
10
0
T3
1
1000
T4
15
1000
T5
50
0
T6
5
0
T7
50
0
T8
50
0
T9
255
1500
T10
15
0
T11
15
0
T12
15
0
T13
255
5000
CONFIG TRUNK "?-?"
Enter trunk circuit number. (Tnnn)
F1-PREVIOUS
F2-NEXT
F6F7-
27.8-2
(400)
F3F8-CANCEL
F4F9-QUIT
F5F10-
X.25 Serivce

NNP 95-2035-01-00-B
27.8 Trunk Circuits

To view trunk circuit configuration information

CONFIG TRUNK
<Tnnn>
SHOW_ALL
SHOW_GROUP
SK000408
where Tnnn is 1 to 128
27.8.3
Configuring Trunk Circuits

From the PE or X.25 FRE NMTI, you configure trunk circuits by selecting a trunk
circuit number and configuring the Cost and Poll Timer parameters.
Cost
This parameter specifies the cost, or routing metric, of the trunk in the outgoing
direction. You assign costs to allow the GFR to prioritize routes and perform load
balancing when more than one trunk connects two switches or when dynamic
routing is enabled.
The GFR assigns priority to trunk routes by evaluating the cost associated with each
trunk. When multiple trunks connect to the same remote switch, the GFR normally
selects the lowest-cost trunk to route frames. Higher-cost trunks are used only when
the preferred trunk fails.
When dynamic routing is enabled on switches in the hub domain, each switch has a
transit cost specified. In this case the GFR assigns priority based on the whole route
cost. This is a cumulative calculation which includes the total trunk costs of all the
hops, plus the transit cost of each hub switch.
When load balancing is enabled on the switch, the GFR distributes traffic equally
between parallel trunks when the differences in costs fall within the delta value
configured for the switch. For example, if trunk A has a cost of 50, trunk B has a cost
of 70, trunk C has a cost of 100, and the delta value is 25, load balancing only occurs
over trunks A and B. In a dynamic routing environment, the load balancing metric
is based on the route cost, which is the cumulative trunk and transit switch costs.
Because the cost applies only in the outgoing direction, trunks can have different
costs for each direction of traffic.
X.25 Service
(400)
27.8-3
27.8 Trunk Circuits


NNP 95-2035-01-00-B
Consider the following factors when determining the cost of a trunk:
financial cost of the trunk traffic if a different service provider is used

bandwidth of the trunk
delay on the trunk
number of intermediate frame relay hops
Range
1 to 255. The value of 255 is infinite, meaning that the GFR never routes traffic to the
trunk.
Default
50
Poll Timer
This parameter specifies the time interval between keep-alive messages sent by the
GFR over an idle trunk. The keep-alive messages, or heartbeats, provide a way for
the switch to detect when a trunk goes down.
When the poll timer value is different at the two ends of the trunk, the endpoint
nodes use the higher of the two values.
Range
0 to 127 500 ms in increments of 500 ms. A value of 0 disables the timer.
Default
0

None

You can change the values of the trunk circuit parameters at any time with no
27.8-4
(400)
X.25 Serivce

NNP 95-2035-01-00-B
27.8 Trunk Circuits

To configure trunk circuits

CONFIG TRUNK <Tnnn>
COST
POLL_TIMER
<cost>
<time>
SK000409
where
Tnnn is the trunk circuit (1 to 128)
cost is 1 to 255 (50*)
time is 0* to 127 500
27.8.4
Connecting Trunk Circuits

From the PE or X.25 FRE NMTI, you can connect trunk circuits to either frame
stream-DLCIs or FASTbus circuit-DLCIs. Both types of connections can be made in
both directions. Existing connections can be disconnected.
To connect trunk circuits to frame stream-DLCIs

A connection to a frame stream-DLCI is normally used to establish a backbone trunk
over a primary rate link to a remote X.25 node.
CONFIG CONNECT <Tnnn>
TO
<Scc-dlci>
DISCONNECT
SK000410
where
Scc-dlci is the frame stream that connects to the primary rate circuit (1 to 62) and the DLCI for the frame
relay PVC between the nodes (16 to 1007)
X.25 Service
(400)
27.8-5
27.8 Trunk Circuits


NNP 95-2035-01-00-B
To connect trunk circuits to FASTbus circuit-DLCIs

A connection to a FASTbus circuit-DLCI is used to establish a backbone trunk
between two X.25 switches located on the same 36120 MainStreet system.
CONFIG CONNECT <Tnnn>
TO
DISCONNECT
<Fnn-dlci>
SK000411
where
Fnn-dlci is the station ID of the PE or X.25 FRE card you are connecting to (1 to 62), and the DLCI for the
frame relay PVC between the cards (2000 to 3983)
27.8.5
Provisioning Backbone Trunks

This section puts the information about configuring and connecting trunk circuits in
the context of step-by-step procedures. These procedures describe all the steps
necessary to provision backbone trunks between 36120 MainStreet X.25 switches.
To provision backbone trunks between two X.25 switches over a primary rate link,
you must:
1.
Establish a physical link between the 3600 MainStreet series bandwidth

manager nodes.
2.
Set up a frame stream between the X.25 switches.
3.
Connect the trunk circuits to frame stream-DLCIs.
Figure 27.8-2 shows the circuits and connections that must be configured. The
numbers in the illustration correspond to the step numbers in the detailed procedure
that follows.
27.8-6
(400)
X.25 Serivce

NNP 95-2035-01-00-B
27.8 Trunk Circuits

Figure 27.8-2: Provisioning Backbone Trunks
36XX MainStreet Shelf
PRI card
X.25 FRE or
PE card
64 to 2.048 kb/s
To
remote
node
= Trunk circuit
= Primary rate interface circuit

7552
To provision backbone trunks over primary rate links

The following procedure describes how to provision trunks between two switches
over a primary rate link.
Note
The following steps must be performed at the two switches on which the trunk
terminates.
At the Control card NMTI

1.
Configure a circuit on the primary rate interface card that terminates the link to
the remote node. Note the circuit number; it must be used when configuring the
other end of the primary rate link.
2.
Configure a PE or X.25 FRE circuit as a frame stream.
3.
Connect the frame stream circuit to the primary rate circuit.
At the PE or X.25 FRE NMTI

4.
X.25 Service
Configure the frame stream parameters (see chapter 24.6).
(400)
27.8-7
27.8 Trunk Circuits


NNP 95-2035-01-00-B
Note
Ensure that the Maximum Frame Size parameter for the stream is set to
accommodate the maximum X.25 packet size.
5.
Configure a trunk circuit (see section 27.8.3).
6.
Connect the trunk circuit to the frame stream-DLCI (see the subsection To
connect trunk circuits to frame stream-DLCIs). Note the DLCI number; it must
be used when configuring the other end of the frame relay DLC.
7.
At the remote end, repeat the above steps.
To provision backbone trunks over the FASTbus

The following procedure describes how to provision trunks between two X.25
switches over the FASTbus. This type of trunk is used when the switches are located
in the same 36120 MainStreet system.
Note
The following steps must be performed at the two switches on which the trunk
terminates.
At the PE or X.25 FRE NMTI
27.8-8
1.
Configure the FASTbus to support the PE or X.25 FRE cards (see chapter 24.4).
2.
Configure a trunk circuit (see section 27.8.3).
3.
Connect the trunk circuit to the FASTbus circuit-DLCI (see the subsection To
connect trunk circuits to FASTbus circuit-DLCIs). Note the DLCI number; it
must be used when configuring the other end of the frame relay DLC.
4.
At the other PE or X.25 FRE, repeat the above steps.
(400)
X.25 Serivce

NNP 95-2035-01-00-B
27.9

NUI Validation Subsystem

This chapter describes how to configure the parameters that enable the operation of
the NUI validation subsystem on the switch.
Note
See the Nexus PASS documentation for information about installing, configuring
and maintaining the NUI validation servers.
27.9.1
Understanding NUIs
NUIs provide a mechanism for identifying network users independently of their
X.121 or E.164 addresses. NUIs ensure secure access to the network and provide a
third billing option, in addition to normal and reverse charging. It is also possible to
associate certain network options, such as CUGs and addresses, with a NUI.
NUIs and passwords are commonly used to facilitate secure dial-in access to X.25
networks. In such cases, the NUI and password not only uniquely identify the user,
but also provide a means to bill the user based on their NUI rather than the calling
address. Because the NUI validation server provides a centralized service to the
entire network, the same validation services are available to users regardless of the
port used for dialling into the network.
NUI validation servers

36120 MainStreet X.25 operates with Nexus PASS NUI validation servers. The Nexus
PASS system provides:
authentication of user access to the network based on a secure database
containing NUIs, passwords, and associated options

centralized validation information for any network user from any port in the
network
administration functions for password changes, NUI cancellation, and
indications of usage
As shown in Figure 27.9-1, every 36120 MainStreet X.25 switch requiring access to
NUI validation services can be optionally configured with a redundant pair of SVC
connections to the NUI validation servers. These communication paths are used for
exchanging validation requests between the switch and the server.
X.25 Service
(400)
27.9-1


NNP 95-2035-01-00-B
Figure 27.9-1: NUI Validation System

NUI
validation server
PE
PE
FRE
NUI
validation server
PE
FRE
FRE
PE
FRE
X.25 network
Primary NUI validation X.25 SVC
Secondary NUI validation X.25 SVC
7323
NUI subscription
Access to NUI validation for subscribers is implemented using the NUI Subscription
facility, which is a configurable NUA parameter. This facility allows a DTE to
include the NUI Selection facility in Call Request packets. The NUI Selection facility
enables the DTE to specify which NUI and password it is using for a particular call.
NUI override
DTEs that subscribe to the NUI Subscription facility are implicitly assigned the NUI
Override facility. This facility allows the subscriber to use the NUI Selection facility
to substitute a set of subscription options that differs from the subscription options
configured for the interface. The Nexus PASS system supports the insertion and
substitution of CUG facilities and calling and called addresses.
CUG insertion and override
In the case of CUGs, the switch either inserts or substitutes information provided by
the NUI validation server. If the Call Request packet contains a CUG facility, the
switch overrides the original interlock code with the interlock code from the NUI
validation server. If no CUG facility is signalled in the Call Request packet, the
switch inserts the interlock code and indicates whether the CUG or CUGOA facility
applies.
Address substitution
The Nexus PASS system can be configured to provide substitute calling and called
addresses. This allows for flexible dial-in access functionality whereby the calling
address does not have to be configured on the XAC. In such cases, the substitute
calling address uses the NUA subscription options of the default NUA assigned to
the XAC.
Called address substitution is a straightforward substitution of the original called
address with the called address received from the NUI validation server.
27.9-2
(400)
X.25 Serivce

NNP 95-2035-01-00-B

How the switch handles NUIs

When a DTE subscribes to the NUI Subscription facility, it may or may not signal the
NUI Selection facility; the network does not absolutely require a NUI to be included.
If a DTE does not subscribe to the NUI Subscription facility but chooses to signal the
NUI Selection facility, the switch clears the call.
When the switch receives a call setup packet that contains a valid NUI Selection
facility, the switch checks the NUI Validation parameter for the calling NUA to
determine whether validation is required.
If NUI validation is required, the switch suspends the call setup process and sends
an encrypted NUI validation request in a data packet to the validation server. If the
server confirms that the NUI and password are valid, the switch proceeds to set up
the call. If the NUI and password are invalid, the switch clears the call.
If NUI validation is not required, the switch assumes that validation should be
performed in another network. The switch extracts the NUI and password from the
NUI Selection facility field and inserts them in an internal facility field in the
Incoming Call packet. The switch then forwards the Incoming Call packet to the
remote XAC. Normally, the remote XAC is an interface to a gateway link.
At the interface of the gateway link, the switch determines whether the NUI and
password can be forwarded to the remote network.
If the service type is not X.25 gateway or the NUA does not subscribe to the NUI
Subscription facility, the switch clears the call.
If the Service Type parameter for the XAC is X.25 gateway and the NUA does
subscribe to the NUI Subscription facility, the switch extracts the NUI and password
from the internal facility field, and inserts them in the NUI Selection facility field in
the format specified by the Default NUI Format parameter for the gateway XAC. The
switch forwards the call setup packet over the gateway link to the remote network,
where the NUI and password are validated. Whether the call is set up or not
depends on successful validation by the remote network.
Figure 27.9-2 shows the process in a flow diagram.
X.25 Service
(400)
27.9-3


NNP 95-2035-01-00-B
Figure 27.9-2: NUI Validation Process

DTE signals NUI
in Call Request packet
NUI Subscription
facility assigned?
NO
Clear call
YES
NUI validation
required?
Insert NUI in
internal facility field
of Incoming Call packet
NO
YES
Suspend call setup
and send validation
request to server
Valid NUI
and password?
Send Incoming Call

packet to remote XAC
NO
Clear call
NO
NUI Subscription
facility assigned?
YES
YES
Proced with
call setup
NO
XAC service type

is X.25 gateway?
YES
Insert NUI in NUI
Selection facility field using
default NUI format
Send Call Request

packet to gateway link
Set up or clear call based on

validation response from remote network
8659
NUI formats
For every DTE that requires NUI validation, you can specify the NUI format as an
NUA option. DTEs can be individually configured to support the standardized NUI
format as defined in Appendix VI of ITU-T Recommendation X.25, and one other
format.
When NUI validation is performed within the 36120 MainStreet X.25 network, the
switch encrypts the password, and converts the NUI format to a standardized
internal format before forwarding the NUI validation request to the validation
server. If the NUI format does not match the format configured for the NUA, the
switch clears the call.
27.9-4
(400)
X.25 Serivce

NNP 95-2035-01-00-B

Figures 27.9-3 to 27.9-6 show example NUI formats and provide the parameter
settings required to define each format. The NUI format parameters are NUA
subscription options (see section 27.15.7).
Figure 27.9-3: Standardized NUI Format (ITU-T Recommendation X.25 1992,
Appendix VI)
8
Control
+
8
Type
Subfield length
NUI
+
8
Type
Subfield length
Password
Parameters:
Default NUI Format = Standard
8662
Figure 27.9-4: Reversed NUI Format

Password
(6 digits)
NUI
(6-8 IA5)
Parameters:
Default NUI Format = Non Standard
Non-standard NUI Coding Method = IA5
Non-standard NUI First Subfield = Password
Non-standard NUI First Subfield Length = 6
8663
Figure 27.9-5: Fixed-length NUI and Password Format

NUI
(IA5)
Password
(IA5)
Parameters:
Non-standard NUI Coding Method = IA5
Non-standard NUI First Subfield = NUI
8664
X.25 Service
(400)
27.9-5


NNP 95-2035-01-00-B
Figure 27.9-6: Bellcore NUI Format

NUI
(10 BCD digits)
Password
(4 BCD digits)
Parameters:
Non-standard NUI Coding Method = BCD
Non-standard NUI First Subfield = NUI
8665
27.9.2
Understanding the NUI Validation Subsystem

On a 36120 MainStreet X.25 switch, the NUI validation subsystem handles the
exchange of NUI validation requests between the switch and the NUI validation
server. The NUI validation subsystem consists of two components: the NUI server
agent and the NUI server agent XAC. You configure both of these components on
every X.25 switch that supports NUI validation. You also configure XACs to
interface with the NUI validation servers.
Figure 27.9-7 shows the components and interfaces.
Figure 27.9-7: NUI Validation Subsystem Components and Interfaces
NUI
server agent
NUI
agent
XAC
Internal
X.25
network
Validation
server
XAC
Nexus PASS
validation server
8660
NUI server agent and XAC

The NUI server agent is an internal DTE that establishes virtual calls to the NUI
validation server, and sends validation requests to the server when required. The
NUI server agent uses the NUI agent XAC as its interface to the network.
The NUI server agent parameters specify the addresses of the primary and
secondary NUI validation servers, and a timeout value for NUI validation requests.
27.9-6
(400)
X.25 Serivce

NNP 95-2035-01-00-B

The NUI agent XAC is the virtual port that provides access to the network for the
NUI server agent. Although the NUI agent XAC has the same configuration options
as a regular XAC, the following exceptions apply.
The XAC operates internally. It has no link layer interface, and the link layer
parameters are not configurable.
The NUA assigned to the NUI agent XAC is the calling address of the NUI server
agent, but is essentially a dummy address; it can never be a called address.

Address translation is not required since the primary and secondary NUI server
addresses are defined in internal address format.
See the subsection CUG considerations for information about CUG membership
requirements for the NUI server agent.
XACs for the validation servers

The NUI validation servers are X.25 DTEs. While the XACs that interface to the NUI
validation servers have the same configuration options as regular XACs, they
generally use the default XAC and NUA parameter values, with the exception of the
CUG membership requirements described below.
As shown in Figure 27.9-8, a fully redundant NUI validation subsystem has four
physical interfaces, and therefore four XACs: two to the primary NUI server, and
two to the secondary NUI server. The primary and secondary servers are always
physically connected to different switches. On each switch, the optional redundant
link is activated using a redirection address. The redundant link is used only if the
principle link is out of service.
X.25 Service
(400)
27.9-7


NNP 95-2035-01-00-B
Figure 27.9-8: Redundant NUI Validation Server Interfaces

Switch 11
NUI server agent

Pri address = 1234
Sec address = 5678
NUI agent XAC

NUA = 11xxxx
Switch 22
Switch 33
NUI server agent

Pri address = 1234
Sec address = 5678
NUI server agent

Pri address = 1234
Sec address = 5678
NUI agent XAC

NUA = 22xxxx
NUI agent XAC

NUA = 33xxxx
Internal
X.25
network
Validation server XAC

NUA = 1234
Redirection
address = 2345
Link
address
= 1234
Validation server XAC

NUA = 5678
Redirection
address = 6789
Link
address
= 2345
Link
address
= 5678
Link
address
= 6789
Primary SVC connections

Secondary SVC connections
Redundant physical links
8661
CUG considerations
To ensure secure access to the NUI validation server, Newbridge recommends that
the NUI server agents and the validation servers belong to the same CUG, which is
used only for this application.
Configure the NUA for the NUI agent so that the NUI agent can establish calls only
to the validation server, and never receive incoming calls. Set the CUG parameters
to:
Preferential CUG = Yes

Incoming Calls Barred = Yes
Signal Preferential CUG = No
27.9-8
(400)
X.25 Serivce

NNP 95-2035-01-00-B

Configure the NUAs for the validation servers so that the validation servers can
receive calls only from the NUI agent, but never establish calls to the NUI server
agent. Set the CUG parameters to:

Outgoing Calls Barred = Yes
27.9.3
Viewing the NUI Server Agent Parameters

Figure 27.9-9 shows the NMTI display for the NUI server agent parameters. To view
the parameters for the NUI agent XAC, see section 27.14.7.
Figure 27.9-9: NUI Server Agent Parameters Display
X25FRE Stations:nn
PA11-H1-00
Toronto:A
Alarms:1
11-May-1997
8:35a
NUI Server Agent

---------------Primary NUI Server Address
:x30204561789
:x30204561799
:10 secs
CONFIG SWITCH X25 AGENTS NUI_SERVER

F1-PRI_ADDR
F6F10-PROCEED
F2-SEC_ADDR
F7-
F3-MAX_PERIOD
F8-CANCEL
F4F9-QUIT
F5-
To view NUI server agent parameters

X.25 Service
(400)
27.9-9

27.9.4

NNP 95-2035-01-00-B
Configuring the NUI Server Agent Parameters

This section describes the NUI server agent parameters and provides configuration
Primary NUI Server Address

This parameter specifies the X.121 or E.164 address of the primary NUI server. Once
this address is activated, the switch attempts to establish an SVC from the NUI agent
XAC to the NUI server over which it sends NUI validation requests. The primary
address is the preferred address and is used whenever it is reachable. The switch
uses the primary server exclusively, unless it fails or is congested, at which point the
switch uses the secondary server.
If you change this address, the NUI agent completes all outstanding transactions
before clearing the SVC and establishing an SVC to the new address. While the new
call is being established, the switch sends NUI validation requests to the secondary
NUI server.
You define the server address by specifying the NPI and entering the address in
international format. See chapter 27.15 for information about valid address formats.
Because the switch does not automatically check the server address against the GAT,
you must ensure that the GAT contains an entry that corresponds to this address.
Range
NPI (x, e, or m) and 1 to 19 digits in international address format (normally 15 digits
or less)
Default
None

This optional parameter specifies the X.121 or E.164 address of the secondary NUI
server. Once this parameter is activated, the switch attempts to set up an SVC to this
address. If the switch cannot establish communication with the primary server
address, it uses this SVC to send NUI validation requests.
Enter the address in the same format as the Primary NUI Server Address parameter.
Because the switch does not automatically check the server address against the GAT,
you must ensure that the GAT contains an entry that corresponds to this address.
Range
NPI (x, e, or m) and 1 to 19 digits in international address format
27.9-10
(400)
X.25 Serivce

NNP 95-2035-01-00-B

Default
None

This parameter specifies the maximum time allowed for NUI validation. If this
period is exceeded, the switch clears the call that requested NUI validation. A value
of 0 disables the timer, in which case the validation period lasts until the call times
out.
The value of this attribute should be less than the Packet Layer Call Timer (T11/T21)
configured for XACs that require NUI validation.
Range
0 to 500 seconds
Default
10 seconds

Observe the following restrictions and interdependencies when configuring the
parameters.
For every switch that requires NUI validation services, you must configure the
NUI server agent parameters and the NUI agent XAC.

In order for the switch to establish calls to the NUI validation servers, the GAT
must contain entries that correspond to the primary and secondary server
addresses.
The NUAs assigned to the NUI server agents and the NUI validation servers
should belong to an exclusive CUG.
The Maximum Allowed Validation Period parameter should be less than the
Packet Layer Call Timer (T11/T21) configured for XACs that use NUI validation
services.

If you change the Primary NUI Server Address parameter, the switch sends NUI
validation requests to the secondary validation server while establishing a call to the
new address.
You can change the value of the Maximum Allowed Validation Period parameter at
any time with no disruption of service. The change is effective for the next call that
requests NUI validation.
X.25 Service
(400)
27.9-11


NNP 95-2035-01-00-B
To configure the NUI server agent parameters

PRI_ADDR
SEC_ADDR
MAX_PERIOD
<address>
<address>
<seconds>
SK000412
where
address is the NPI and 1 to 19 digits in X.121 or E.164 address format
seconds is 1 to 500 (*10)
To configure a NUI agent XAC

1.
Select an XAC and set the Service Type parameter to NUI Agent.
CONFIG X25_ACCESS XAC <xac> NET_LAYER SERVICE AGENT
NUI PROCEED
CONFIG X25_ACCESS NUA <address> SUBS_OPT CUG <index>
INTERLOCK
BARRING
PREF
<code>
INC_BAR
YES
SK000413
where xac is a valid XAC
Note
You can accept the default values for all other XAC parameters.
2.
Configure an NUA and assign it to the XAC configured in step 1.

CONFIG X25_ACCESS NUA <address> ASSIGN_TO <xac> PROCEED
where
xac is the XAC configured in step 1
Note
You can accept the default values for all other NUA parameters.
3.
27.9-12
Configure the CUG parameters for the NUA configured in step 2.
(400)
X.25 Serivce

NNP 95-2035-01-00-B

where
address is the NUA configured in step 2
index is the CUG index (0 to 99)
code is the CUG interlock code (1 to 65 535)
Note
You can accept the default values for all other CUG parameters.
X.25 Service
(400)
27.9-13

NNP 95-2035-01-00-B
27.10

Accounting Generation Subsystem

This chapter describes the generation of X.25 accounting records. For information on
the transfer of records to the data collector, see chapter 27.11.
27.10.1
Understanding Virtual Circuit Accounting

A 36120 MainStreet X.25 switch generates and delivers accounting data to the data
collector. Accounting information is maintained in sufficient detail to allow the
allocation of network usage costs to subscribers. This information also provides an
audit trail for use in the investigation of subscriber inquiries. Figure 27.10-1 shows a
typical X.25 accounting application.
Figure 27.10-1: Typical X.25 Accounting Application
Primary
Data
Collector
X.25 PE
X.25 DTE
X.25
Network
User
X.25 Vcs
X.25 FRE
NTP
Server
X.25 FRE
Secondary
Data
Collector
X.25 DTE
Accounting
Records
NTP Time
Updates
10619
X.25 Service
(400)
27.10-1


NNP 95-2035-01-00-B
X.25 accounting has two basic components (see Figure 27.10-2).
Accounting generation subsystem: The accounting generation subsystem
generates accounting records and stores them in NVM.

Data collector agent subsystem: The data collector agent establishes and
maintains SVCs to the data collector, and manages the transfer of accounting
records from NVM to the data collector. The data collector agent XAC is an
internal XAC (with service type set to data collector agent) used to communicate
with the data collector interface XAC.
Note
In Figure 27.10-2, one X.25 switch connects physically to the data collector, and other
X.25 switches in the network connect logically to the data collector.
Figure 27.10-2: Components of the X.25 Accounting Subsystem

X.25 switch
Accounting
generation subsystem
Data collector agent
Logical connection
Data collector
agent XAC
Data collector
Network
Network
Physical connection
Data collector
interface XAC
9147
Accounting segments
The accounting generation subsystem counts data in accounting segments. The
number of bytes in each segment is a configurable switch-wide parameter.
Transmitted segments and received segments for each VC are counted separately.
The segment counter increments whenever a segment sized number of bytes is
counted, or when the end of the packet is reached.
27.10-2
(400)
X.25 Serivce

NNP 95-2035-01-00-B

Collection intervals
Along with an ability to accurately count transmitted and received data, the
accounting generation subsystem needs to keep track of network usage for different
times of the day. This capability allows clients to charge for network use based on
the time of day in which the network was used. To address this need, the accounting
generation subsystem groups segments according to the span of time during the day
in which the VC was active. These spans of time are called collection intervals. The
duration of a collection interval is a configurable switch-wide parameter. A
collection interval of 6 h starts at midnight, 6:00 a.m., noon and 6:00 p.m., whereas a
collection interval of 1 h starts every hour on the hour.
The transmit usage count is the number of transmitted segments counted during a
collection interval. The receive usage count is the number of received segments
counted during a collection interval. An interval report is composed of the transmit
usage count and the receive usage count. Figure 27.10-3 shows collection intervals,
interval reports and usage counts.
Figure 27.10-3: Collection Intervals, Interval Reports and Usage Counts
20 x 64 byte & 1 x 256 bytes pkts transmitted
3 x 256 byte pkts received
00:00 GMT
Collection
interval 3
Collection
interval 0
18:00
6:00
Collection
interval 2
Collection
interval 1
Interval Report
TX usage RX usage
count
count
22
12:00
Parameters:
Intermediate Record Interval = 24 h
Collection Interval = 6 h
Number of Collection Intervals = 4
Accounting Segment Size = 128 bytes
9108
Accounting records
Interval reports from successive collection intervals are combined with header
information, such as SVC start time and SVC duration, to form accounting records.
Accounting records are transmitted by the X.25 switch to the data collector for
storage.
Accounting records are produced at one of the two XACs involved in each VC. For
SVCs, accounting records are normally produced at the calling side, although in the
case of a reverse charge SVC the records are produced at the called side.
X.25 Service
(400)
27.10-3


NNP 95-2035-01-00-B
Four different types of accounting records can be generated:
intermediate records
end records
periodic records
time-change records
Intermediate records
An intermediate record is a combination of interval reports and header information.
The time period over which interval reports are collected to produce an intermediate
record is called an intermediate record interval. The intermediate record interval
duration divided by the collection interval duration must be an integer, and cannot
exceed 4 for the X.25 FRE card and 24 for the PE card.
The intermediate record interval is a configurable switch-wide parameter.
Figure 27.10-4 shows the relationship between collection intervals and intermediate
record intervals. In Figure 27.10-4, there are four collection intervals for each
intermediate record interval. The VC must be active during four collection intervals,
but not for the total duration of four collection intervals. In this case, the
intermediate record is generated after the VC is active for part of collection interval
0, plus all of collection intervals 1, 2 and 3.
Figure 27.10-4: Example of an Intermediate Record
24:00
Collection
interval 2
Collection
interval 3
18:00
6:00
Collection
interval 1
Collection
interval 0
Intermediate
record
Interval reports
12:00
Call start
time
Parameters:
Periodic Record Interval = 0 (off)
Complete interval report
9110
27.10-4
(400)
X.25 Serivce

NNP 95-2035-01-00-B

End records
The accounting generation subsystem produces an end record when an SVC is
cleared or a PVC is deleted or disabled. If the SVC duration is shorter than the
intermediate record interval and the periodic record interval, the end interval is the
only record produced. Figure 27.10-5 shows the generation of an end record for an
SVC. Figure 27.10-6 shows the relationship between an intermediate record and an
end record for an SVC.
Figure 27.10-5: Example of an End Record
End
record
24:00
Call clear
time
Call set-up
time
Collection
interval 0
Interval reports
Collection
interval 1
18:00
6:00
Collection
interval 3
Collection
interval 2
12:00
Parameters:
9109
X.25 Service
(400)
27.10-5


NNP 95-2035-01-00-B
Figure 27.10-6: Relationship Between an Intermediate Record and an End Record
24:00
Collection
interval 2
Collection
interval 3
18:00
Intermediate
record
6:00
Collection
interval 1
Collection
interval 0
Interval reports
Call clear
time
12:00
End
record
Call setup
time
Interval report
Parameters:
Number of Collection Intervals= 4
9111
Periodic records
The periodic record provides redundancy in the collection of usage data. It is a
snapshot of the intermediate record for the current intermediate record interval. As
the VC progresses, periodic records accumulate interval reports but these interval
reports are discarded once the corresponding intermediate record is generated.
Figure 27.10-7 shows the generation of a periodic record for an SVC.
27.10-6
(400)
X.25 Serivce

NNP 95-2035-01-00-B

Figure 27.10-7: Example of a Periodic Record

Periodic
record
Interval reports
Periodic
record
24:00
Interval reports
Collection
interval 2
Collection
interval 3
18:00
Intermediate
record
6:00
Collection
interval 1
Collection
interval 0
Interval reports
Call clear
time
12:00
Periodic
record
End
record
Interval reports
Call setup
time
Interval report
Parameters:
Intermediate record Interval = 24 h
Periodic Record Interval = 6 h

Partially complete interval report
9112
Time synchronization
The real-time clocks on X.25 switches and data collectors can be synchronized, using
the Internet time synchronization Network Time Protocol, to an accuracy of plus or
minus 1 second.
The data collector operates as an NTP server and synchronizes the switch, which
operates as a NTP client. The data collector also operates as an NTP client for
synchronizing itself with other data collectors and a common clock source.
The data collector can derive its clock source from any of the following references:
another data collector

public Internet NTP clock source
radio clock
NTP messages use the same SVC connection and are encapsulated in the Newbridge
proprietary protocol that is used for transferring usage records.
X.25 Service
(400)
27.10-7


NNP 95-2035-01-00-B
Figure 27.10-8: NTP Time Initialization Display

X25FRE Stations:nn
PA11-H1-00
Toronto:A
Alarms:1
11-May-1997
8:35a
Time Synchronization Service Status

----------------------------------NTP Client Current Time
:02-Jan-1970 03:54:27.89
NTP Client Status
:not Synchronized
MAINT ON_X25 NTP

16-
27-
38-CANCEL
49-QUIT
50-
NTP time initialization

Prior to NTP synchronization, the switch uses the following strategies to obtain its
first best estimate of network time:
If the control card time is not configured, the switch uses time 0 (January 1 1970)
as its first estimate.

If the control card time is configured and NTP has not previously calculated the
switch offset from control card time, then control card time is used as the best
estimate.
If the control card time is configured and NTP has previously calculated the
switch offset from the control card time, then control card time adjusted by the
previous offset is used as the best estimate.
NTP then adjusts time from the best estimate towards central network time on the
data collector.
Time-change records
Time-change records are generated each time a network time adjustment greater
than or equal to 2 seconds is made by the time synchronization service. The
time-change record contains the current and previous time for which the time
change occurred.
27.10-8
(400)
X.25 Serivce

NNP 95-2035-01-00-B

A time adjustment never changes the duration of the current collection interval.
Time changes are handled as follows.
A negative time adjustment (clock turned back) extends the next interval.
For example, assume that collection intervals are due every hour on the hour,
that it is 12:00 midnight and the clocks are automatically turned back to 11:45. If
the next collection interval is due to be complete at 1:00 a.m., it will have a
duration of 1 h and 15 min.
A positive time adjustment (clock turned forward) reduces the next interval.
For example, assume that collection intervals are due every hour on the hour,
that it is 12:00 midnight and the clocks are automatically turned forward to 12:15.
If the next collection interval is due to be complete at 1:00 a.m., it will have a
duration of 45 min.
Paced generation of accounting records

Resource usage peaks occur when the X.25 switch generates large numbers of
accounting records simultaneously. Before assembling records into transfer blocks
in NVM, the switch uses a number of strategies to pace the generation of accounting
records in order to limit resource usage peaks. The pacing strategies do not
compromise the correct time stamping of record-interval start times, record-interval
elapsed times and VC end times.
The following pacing strategies are used.
The length of the first intermediate record interval is varied for each VC. This
X.25 Service
helps to prevent resource usage peaks when intermediate records are generated
for many VCs which start within the same collection interval. The length of each
first intermediate record interval is varied by up to three collection intervals less
than the intermediate record interval on the PE card and by up to two collection
intervals less on the X.25 FRE card. The result of this is that the actual number of
interval reports in the first intermediate record for each VC may be less than the
intermediate record interval divided by the collection interval.
The generation of intermediate records is paced over the first two thirds of each
collection interval. This pacing is subject to a minimum rate of two records per
second. A possible result of this pacing is that, if a VC ends before an
intermediate record is generated, then the intermediate record is replaced by an
end record which may contain one more interval report than the maximum
number of interval reports allowed in an intermediate record.
The generation of end records is paced at a minimum rate of 40 records per
second.
The length of the first periodic record interval for each SVC is varied. This helps
to prevent resource usage peaks when periodic records are generated for many
VCs which start almost simultaneously. They are varied over a 3 min interval on
the PE card and a 7.5 min interval on the X.25 FRE card.
The generation of periodic records is paced over 1 min for the PE card and
2.5 min for the X.25 FRE card.
(400)
27.10-9


NNP 95-2035-01-00-B
Accounting record storage in NVM

After generating accounting records, the switch assembles the records into TBs
(transfer blocks), which are stored in NVM. Records are added to a TB until the
preconfigured transfer block size is reached or the preconfigured maximum time
between transfers is exceeded, at which time the TB is transferred to the data
collector.
Transfer of accounting records to the data collector

The switch transfers TBs from NVM to the external data collector using the
Newbridge proprietary GDI protocol. The GDI protocol is outlined in the
Newbridge Technical Reference, NTR0046.
Reliability of the transfer process is ensured because the data collector sends an
acknowledgment to the switch only when the TB has been saved to disk. Once the
transfer acknowledgment has been received by the switch, the TB is deleted from
NVM.
To further increase data transfer reliability, two data collectors, designated the
primary and secondary data collectors, can be used. Transfer of accounting records
is switched to the secondary data collector if the connection to the primary data
collector fails. When the primary data collector is reconnected the data collection
system consolidates all records in the primary data collector and ensures that no
records are lost or duplicated.
Note
Each accounting record contains a reference number consisting of the GFR address
and a 24 bit call reference. The call reference is a counter that starts at zero when the
card is first configured and increments with each new SVC or PVC. The same
reference number is used in all accounting records generated for one SVC or PVC.
This reference number allows all records belonging to the same VC to be matched.
The reference number is not reset when the card is reset.
27.10-10
(400)
X.25 Serivce

NNP 95-2035-01-00-B

Table 27.10-1: X.25 and X.75 Accounting Record Fields

Field Name
Description
Range
Field Size
Mandatory
or Optional
Header Fields
Data Type
0 = originating
recording interface
accounting
12 bits
Mandatory
Data Record Type
0 = intermediate
1 = end
2 = periodic
4 bits
Mandatory
Unique Record Identifier
The Unique Record Identifier field

depends on the Service Type. It
uniquely identifies a VC within the
network.
Byte offset:
byte 0 = network
domain identifier
byte 1 = hub identifier
byte 2 = leaf identifier
bytes 3 to 5 = call
identifier
bytes 6 to 9 = unused
10 bytes
Mandatory
Usage Record Start Time

(integer part)
The start time in UTC to the nearest

second.
0x0 to xFFFFFFFF
4 bytes
Mandatory
Usage Record Start Time

(fraction part)
The fraction part of the start time in

10 ms units.
0 to 99
1 byte
Mandatory
Usage Record Elapsed

Time
The elapsed time in 10 ms units.
0x0 to xFFFFFFFF
3 bytes
Mandatory
Local time offset
The local time offset can range from

12 to +12 h, in 15 min increments.
48 = 12:00
47 = 11:45
...
1 = 00:15
0 = 0 (GMT)
1 = +00:15
...
48 = +12:00
1 byte
Mandatory
Collection Interval Length
The smallest time period over which

the data volume is measured for a
connection.
1 = 15 min
2 = 30 min
3 = 45 min
4 = 60 min
5 = 120 min
6 = 180 min
7 = 240 min
8 = 360 min
9 = 480 min
A = 720 min
B = 1440 min
1 byte
Mandatory
Local XAC
The local XAC number for the VC.
1 to 512
2 bytes
Mandatory
Local LCN
The local logical channel number for

the VC.
1 to 4095
2 bytes
Mandatory
Remote Domain Identifier
The Remote GFR address domain

routing identifier.
1 to 245
1 byte
Mandatory
Remote Hub Identifier
The Remote GFR address hub

routing identifier.
1 to 245
1 byte
Mandatory
Remote Leaf Identifier
The Remote GFR address leaf

routing identifier.
1 to 245
1 byte
Mandatory
Virtual Circuit Data Fields
X.25 Service
(400)
27.10-11

Field Name

NNP 95-2035-01-00-B
Description
Range
Field Size
Mandatory
or Optional
Remote XAC
The Remote XAC number for the

VC.
1 to 512
2 bytes
Mandatory
Remote LCN
The Remote logical channel number

for the VC.
1 to 4095
2 bytes
Mandatory
Cause Code
The Cause code used in the Clear or

Reset Packet
0 to 255
1 byte
Mandatory
Diagnostic Code
The Diagnostic code used in the

Clear or Reset packet
0 to 255
1 byte
Mandatory
Receive Throughput
Class
The Receive Throughput Class used

for VC after flow control negotiation.
3 to 44
(75, 150, 300, 600,
1 200, 2 400, 4 800,
9 600, 19 200, 48 000,
64 000, 128 000,
192 000, 256 000,
320 000, 384 000,
448 000, 512 000,
576 000, 640 000,
704 000, 768 000,
832 000, 896 000,
960 000, 1 024 000,
1 088 000, 1 152 000
1 216 000, 1 280 000
1 344 000, 1 408 000,
1 472 000, 1 536 000
1 600 000, 1 664 000,
1 728 000 1 792 000,
1 856 000 1 920 000,
1 984 000 2 048 000
b/s)
1 byte
Mandatory
Transmit Throughput
Class
The Transmit Throughput Class

used for VC after flow control
negotiation.
3 to 44
(75, 150, 300, 600,
1 200, 2 400, 4 800,
9 600, 19 200, 48 000,
64 000, 128 000,
192 000, 256 000,
320 000, 384 000,
448 000, 512 000,
576 000, 640 000,
704 000, 768 000,
832 000, 896 000,
960 000, 1 024 000,
1 088 000, 1 152 000
1 216 000, 1 280 000
1 344 000, 1 408 000,
1 472 000, 1 536 000
1 600 000, 1 664 000,
1 728 000 1 792 000,
1 856 000 1 920 000,
1 984 000 2 048 000
b/s)
1 byte
Mandatory
Receive Window Size
The number of packets that a

receiving switch may receive before
sending an acknowledgment to the
sending switch.
1 to 127
1 byte
Mandatory
Transmit Window Size
The number of packets that a DCE

may transmit before requiring an
acknowledgment from the
destination switch.
1 to 127
1 byte
Mandatory
27.10-12
(400)
X.25 Serivce

NNP 95-2035-01-00-B
Field Name

Description
Range
Field Size
Mandatory
or Optional
Receive Packet Size
The packet size that a switch may

receive.
4 = 16
5 = 32
6 = 64
7 = 128
8 = 256
9 = 512
10 = 1024
11 = 2048
12 = 4096 bytes
4 bits
Mandatory
Transmit Packet Size
The packet size that a switch may

transmit.
4 = 16
5 = 32
6 = 64
7 = 128
8 = 256
9 = 512
10 = 1024
11 = 2048
12 = 4096 bytes
4 bits
Mandatory
PVC Indication
Indicates whether or not this VC was

a PVC.
1 = Yes
0 = No
1 bit
Mandatory
CUG Indication
Indicates whether or not this was a

closed user group call.
1 = Yes
0 = No
1 bit
Mandatory
Reverse Charging
Indication
Indicates whether or not charges

were reversed for this VC.
1 = Yes
0 = No
1 bit
Mandatory
Fast Select Indication
Indicates whether or not fast select

was used for this call.
1 = Yes
0 = No
1 bit
Mandatory
Call Redirection Indication
Indicates whether the call was

redirected.
1 = Yes
0 = No
1 bit
Mandatory
Hot Billing Indication
Indicates whether the hot billing

NUA parameter is selected on the
local XAC. This feature allows for
expedited processing of accounting
records by down stream data
processing.
1 = Yes
0 = No
1 bit
Mandatory
Hunted Indication
Indicates whether this is a hunt

group call.
1 = Yes
0 = No
1 bit
Mandatory
Call Reached Data

Transfer Indication
Indicates whether the call reached

data transfer state.
1 = Yes
0 = No
1 bit
Mandatory
Local Service Type
The service type of the local XAC.

The local XAC is the XAC generating
the accounting record.
1 = X.25
2 = X.25 gateway
3 = X.75 gateway
4 = Traffic generator
5 = NUI agent
6 = data collector agent
7 = X.25 to FR
interworking agent
4 bits
Mandatory
Remote Service Type
The service type of the remote XAC.
1 = X.25
2 = X.25 gateway
3 = X.75 gateway
4 = Traffic generator
5 = NUI agent
6 = data collector agent
7 = X.25 to FR
interworking agent
4 bits
Mandatory
Called Party Address

Fields
X.25 Service
(400)
27.10-13

Field Name

NNP 95-2035-01-00-B
Description
Range
Field Size
Mandatory
or Optional
Type of Address
Specifies the type of address.
1 = International
3 bits
Mandatory
Numbering Plan Indicator
Defines the format of the address.
1 = E.164 digital
2 = E.164 analog
3 = X.121
4 bits
Mandatory

Length
Defines the called party address in

international format.
1 to 19 BCD digits
1 byte
Mandatory

Digits
The address of the called party.
1 to 19 BCD address
digits
1 to 32
bytes
Mandatory
Type of Address
Specifies the type of address.
1 = International
3 bits
Mandatory
Numbering Plan Indicator
Defines the format of the address.
1 = E.164 digital
2 = E.164 analog
3 = X.121
4 bits
Mandatory
Calling Party Address

Length
Defines the called party address in

1 to 19 BCD digits
1 byte
Mandatory

Digits
The address of the calling party.
1 to 19 BCD address
digits
1 to 10
bytes
Mandatory
A unique code that identifies the call.
0 to 16777215
3 bytes
Optional
The DNIC of the ICUG.
0000 to 9999 BCD
2 bytes
Optional
The interlock code of the ICUG.
0 to 65535
2 bytes
Optional
The DNIC of the network that

cleared the call.
0001 to 9999 BCD
2 bytes
Optional
Between 1 and 5 TNICs are

supported.
0000 to 9999 BCD
2 bytes
Optional
This field contains the user defined

data parameter configured on the
charging XAC. The number of
characters of user defined data is
determined by the optional User
Defined Data Length switch
parameter.
IA5
1 to 24
bytes
Optional
This field provides the NUI signalled

in the call request packet. The
password is not included. The NUI is
not present in the case of a PVC.
x.00 to x.FF
1 to 21
bytes
Optional
Receive segment counter
This field contains the receive

segment counter.
x00000000 to
xFFFFFFFF
4 bytes
Mandatory
Transmit segment counter
This field contains the transmit

segment counter.
x00000000 to
xFFFFFFFF
4 bytes
Mandatory

Fields
X.75 Fields
X.75 Call Identifier
(1)
International Closed User

Group DNIC
(1)
International Closed User

Group Interlock Code
(1)
Clearing network identifier

(1)(2)
Transit Network Identifiers

Other Fields
User Defined Data
(2)
Network User Identifier
Interval Counts
27.10-14
(400)
X.25 Serivce

NNP 95-2035-01-00-B

Notes
1. These items only appear in X.75 records.
2. These fields are not present in the case of a PVC.
Table 27.10-2: Time Change Record

Field Name
27.10.2
Description
Range
Field Size
Time Before Change

in UTC (integer part)
The time before the

time change in UTC
(to the nearest
second).
0x0 to xFFFFFFFFFF
4 bytes
Time Before Change

in UTC (fraction part)
The fraction part of the

time before the time
change (in 10 ms
units).
0 to 99
1 byte
Time After Change in

UTC (integer part)
The time after the time

change in UTC (to the
nearest second).
0x0 to xFFFFFFFFFF
4 bytes
Time After Change in

UTC (fraction part)
The fraction part of the

time after the time
change (in 10 ms
units).
0 to 99
1 byte
Understanding Accounting Generation Parameters

The accounting generation parameters include parameters that define how the
switch generates accounting records.
While all these parameters apply to the switch, the generation of accounting records
for individual subscribers is controlled on a per-NUA or per-PVC basis. For
information on NUA-related parameters, see chapter 2.12; for PVC-related
accounting parameters, see chapter 2.14. Table 27.10-3 lists the accounting
generation parameters.
X.25 Service
(400)
27.10-15


NNP 95-2035-01-00-B
Table 27.10-3: Accounting Generation Parameters

Parameter Name
Option or Range
Default
Generate Accounting Records
Yes
No
No
Generate Accounting Records on

Unsuccessful Calls
Generate
Dont Generate
Dont Generate
Accounting Segment Size
1, 2, 4, 8, 16, 32, 64, 128,

256, 512, 1024, 2048 or
4096 bytes
64 bytes
Collection Interval
15, 30, 45 min, 1, 2, 3, 4, 6, 8,

12 and 24 h
24 h
Intermediate Record Interval
15, 30, 45 min, 1, 2, 3, 4, 6, 8,

12 and 24 h
24 h
Periodic Record Interval
0, 5, 10, 15, 30, 45 min, 1, 2,

3, 4, 6, 8 and 12 h
0 min
Optional User Defined Data Length
0 to 24 characters
Time Zone
12:00 to 12:00 (hh:mm) in

15 min increments
00:00 (which is GMT)
Accounting NVM Buffer Size
0, 1, 2, 4, 16, 32, 64, 128,

256, 512, 768 kbytes
512 kbytes for the PE

card
128 kbytes for the X.25
FRE card
For a description of the following accounting-related X.25 NUA parameters, see

chapter 2.12:
27.10-16
Hot Billing
(400)
X.25 Serivce

NNP 95-2035-01-00-B
27.10.3

Viewing the Accounting Generation Parameters

Figure 27.10-9 shows the NMTI display for the accounting generation parameters.
Figure 27.10-9: Accounting Generation Parameters Display
X25FRE Stations:nn
PA11-H1-00
Toronto:A
Alarms:1
11-May-1997
8:35a
Accounting
---------------Generate Accounting Records
Generate Accounting Records on Unsuccessful Calls
Collection Interval
Intermediate Record Interval :24 hrs
Time Zone
CONFIG SWITCH X25 ACCOUNTING

F1-GENERATE
F2-FAILD_CALL
F6-TIME_ZONE
F7-
F3-SEG_SIZE
F8-CANCEL
:Yes
:Yes
:64
:24 hrs
:0 hrs
:0 bytes
:-5:00 hrs
F4-INTERVALS
F9-QUIT
F5-USRDAT_LEN
F10-PROCEED
To view accounting generation parameters

27.10.4
Configuring the Accounting Generation Parameters

This section describes the accounting generation parameters and provides
configuration guidelines. The parameters are ordered as they appear on the NMTI
display.
Caution
When you change the value of certain accounting generation parameters, the PE or
X.25 FRE card restarts automatically to activate the changes. A card restart causes
the switch to clear all calls. Once the switch is operational, change these parameters
only during periods of minimal network activity.
X.25 Service
(400)
27.10-17


NNP 95-2035-01-00-B
Generate Accounting Records

When this parameter is set to Yes, the ability of the switch to generate accounting
records and transfer them to the data collector is enabled.
When this parameter is set to No, the ability of the switch to generate accounting
records, is disabled. Generation of accounting records is also determined by:
the NUA-related accounting parameter Accounting Activation (see

section 2.12.4).
the PVC-related accounting parameter Accounting Activation (see

section 2.14.3).
When the Generate Accounting Records parameter is changed from No to Yes, the
switch starts collecting accounting information immediately and generates
accounting records as soon as they are required.
When the Generate Accounting Records parameter is changed from Yes to No, the
switch ceases to generate periodic, intermediate or end records.
Options
Yes or No
Default
No
Generate Accounting Records on Unsuccessful Calls

An unsuccessful call is an SVC that does not reach the data transfer state because it
is cleared by the network or the DTE due to a user protocol error or network
problem.
When accounting is activated for the switch and this parameter is set to Generate,
accounting records are generated for unsuccessful SVC calls.
When accounting is activated for the switch and this parameter is set to Dont
Generate, accounting records are not generated for unsuccessful SVC calls.
Accounting records for unsuccessful SVC calls are end records that contain no
interval reports and are normally used for statistics purposes only (external billing
systems can filter these records).
27.10-18
(400)
X.25 Serivce

NNP 95-2035-01-00-B

Accounting records for unsuccessful SVC calls are generated:
if this parameter is set to Generate and the clear cause code is:
DTE originated cause code (hex 00)(dec 0)
Remote Procedure Error (hex 11)(dec 17)
Local Procedure Error (hex 13)(dec 19)
Number Busy (hex 01)(dec 1)
Out of Order (hex 09)(dec 9)
Incompatible Destination (hex 21)(dec 33)
Fast Select Acceptance Not Subscribed (hex 29)(dec 41)
Invalid Facility Request (hex 03)(dec 3)
Access Barred (hex 0B)(dec 11)
when the clear cause code is Network Congestion (hex 05) (dec 5) or Not
Obtainable (hex 0D)(dec 13)

for unsuccessful fast select calls unless the Unsuccessful Calls parameter is set to
Dont Generate and the call is cleared with cause code Fast Select Acceptance Not
Subscribed
Accounting records for unsuccessful SVC calls are not generated:
when the parameter is set to Dont Generate

when the X.25 Switch Maintenance state is set to Disable
when a call is cleared due to protocol error; for example, The call request packet
does not contain any address.
Options
Yes or No
Default
No

This parameter specifies the number of bytes that constitute an accounting segment.
Subscribers are charged for the number of segments transmitted and received. The
segment counter increments whenever a segment-sized number of bytes is counted,
or when the end of the packet is reached.
The value of this attribute should be the same on every switch in the network.
Switches that differ with respect to this parameter generate accounting records that
do not reflect the same rate of data sampling.
A change in this parameter causes a switch restart. If accounting is activated and a
data collector is not available when the change is made, accounting records for active
SVCs may be lost.
Options
1, 2, 4, 8, 16, 32, 64, 128, 256, 512, 1024, 2048 or 4096 bytes
X.25 Service
(400)
27.10-19


NNP 95-2035-01-00-B
Default
64 bytes
Collection Interval
This parameter specifies the time duration of a collection interval. A collection
interval is the period of time at the end of which an interval report is produced.
An interval report contains the transmit usage count and the receive usage count for
a single collection interval. Collection intervals are discussed in more detail at the
beginning of this chapter.
The value of the Intermediate Record Interval divided by the value for the collection
interval, must:
not produce a fractional value (for example, if the Intermediate Record Interval
parameter is set to 45 min, the collection interval can be set to 15 min [45 15 = 3],
but cannot be set to 30 min [45 30 = 1.5])
be less than or equal to 4 for the X.25 FRE card, and less than or equal to 24 for
the PE card

SVCs may be lost.
Options
15, 30, 45 min, 1, 2, 3, 4, 6, 8, 12 and 24 h
Default
24 h
Intermediate Record Interval

This parameter specifies the time duration of an intermediate record interval. An
intermediate record interval is the period of time at the end of which an intermediate
record is produced.
An intermediate record is composed of interval reports. The number of interval
reports in an intermediate record is defined by the intermediate record interval
divided by the collection interval. Intermediate record intervals are discussed in
more detail in Section 27.10.1 of this chapter.
The value of this parameter, divided by the collection interval value, must:
not produce a fractional value (for example, if the Intermediate Record Interval
27.10-20
parameter is set to 45 min, the collection interval can be set to 15 min [45 15 = 3],
but cannot be set to 30 min [45 30 = 1.5])
be less than or equal to 4 for the X.25 FRE card, and less than or equal to 24 for
the PE card
(400)
X.25 Serivce

NNP 95-2035-01-00-B


SVCs may be lost.
Options
15, 30, 45 min, 1, 2, 3, 4, 6, 8, 12 and 24 h
Default
24 h

This parameter specifies the time duration of a periodic record interval. A periodic
record interval is the period of time at the end of which a periodic record is
produced.
These records prevent data loss between the generation of intermediate accounting
records. If the switch fails, the only information lost is the data collected since the last
periodic interval. Collection intervals are discussed in more detail in Section 27.10.1
of this chapter.
The value of this parameter must be less than the Intermediate Record Interval
value. The default value of 0 means the switch does not generate periodic accounting
records. A change in this parameter takes effect after the current periodic record
interval expires.
Options
0, 5, 10, 15, 30, 45 min, 1, 2, 3, 4, 6, 8 and 12 h
Default
0 min

This parameter specifies the maximum length of the optional User Defined Data
parameter that can be configured for each NUA. The User Defined Data parameter
provides additional information about the subscriber. To ensure that the
user-defined data remains unique, the user-defined data length must be long
enough such that it does not cause truncation of the data set by the user.
The default value of 0 means that the User Defined Data parameter cannot be used.
A change in this parameter takes effect at the beginning of the next VC.
Range
0 to 24 characters
X.25 Service
(400)
27.10-21


NNP 95-2035-01-00-B
Default
0
Time Zone
This parameter specifies the time zone in which this switch is located. The parameter
specifies the time zone in 15 min interval offsets from GMT.
Network operators are responsible for manually changing and synchronizing the
Time Zone parameter. The network cannot automatically change and synchronize
time zone settings.
A change in this parameter takes effect when the next accounting record is
generated.
Range
12:00 to 12:00 (hh:mm) in 15 min increments
Default
00:00 (which is GMT)
Accounting NVM Buffer Size

This parameter specifies the size of NVM used for reliable account record buffering.
The remaining NVM is used for the NVM database.
Note
The Accounting NVM Buffer Size parameter value is fixed to the default for Releases
1.1 and 1.2 of the PE card and X.25 FRE card.
Range
0, 1, 2, 4, 16, 32, 64, 128, 256, 512, 768 kbytes
Default
512 kbytes for the PE card
256 kbytes for the X.25 FRE card

When configuring the accounting generation parameters across multiple switches it
is important to make sure that the segment size is the same for all switches.
Newbridge recommends that the collection interval be the same for each switch.
27.10-22
(400)
X.25 Serivce

NNP 95-2035-01-00-B


When you change the value of certain accounting generation parameters, the PE or
X.25 FRE card restarts automatically to activate the changes. A card restart causes
the switch to clear all calls. Once the switch is operational, change these parameters
only during periods of minimal network activity.
To configure the accounting generation parameters

GENERATE FAILED_CALL SEG_SIZE
USRDAT_LEN TIME_ZONE
INTERVALS
YES/NO
YES/NO
<length>
<segment>
<zone>
COLLECTION INTERMEDT PERIODIC

<collect>
<inter>
<period>
SK000684
where
segment is 1, 2, 4, 8, 16, 32, 64*, 128, 256, 512, 1024, 2048 or 4096 bytes
length is 0 to 24 characters
zone is 12:00 to 12:00 (hh:mm) in 15 min increments, 0*
collect is 15, 30, 45 min, 1, 2, 3, 4, 6, 8, 12 and 24 h*
inter is 15, 30, 45 min, 1, 2, 3, 4, 6, 8, 12 and 24 h*
period is 0*, 5, 10, 15, 30, 45 min, 1, 2, 3, 4, 6, 8 and 12 h
* is the default
X.25 Service
(400)
27.10-23

NNP 95-2035-01-00-B
27.11

Data Collector Agent Subsystem

This chapter describes how to configure the data collector agent parameters. For
information on how to configure the data collector, see the MainStreetData Collector
guide.
27.11.1
Understanding the Data Collector Agent

To understand the data collector agent, the following system components must be
understood:
accounting generation subsystem

data collector agent
data collector agent XAC
data collector interface XAC
data collector
GDI protocol
Accounting generation subsystem

The accounting generation subsystem is located on the X.25 switch. It generates
accounting records and stores transfer blocks in NVM. The transfer block is a
variable-length string of bytes consisting of a number of accounting records or
control records. The accounting generation subsystem attempts to bundle multiple
accounting records into a single transfer block before sending it to the data collector.
Data collector agent

The data collector agent is located on each X.25 switch. It initiates SVCs between the
X.25 switch and the data collector, and manages the transfer of transfer blocks from
NVM to the data collector.
Data collector agent XAC

The data collector agent XAC resides on each X.25 switch. It is internal to the
network (it has no link layer) and is configured with the data collector agent service
type. Multiple data collector agent XACs interface over virtual circuits, with a single
XAC that interfaces with the primary data collector and a single XAC that interfaces
with the secondary data collector (see Figure 27.11-1).
The dummy NUA of each data collector agent XAC belongs to the same CUG as the
NUA for the data collector.
X.25 Service
(400)
27.11-1


NNP 95-2035-01-00-B
Figure 27.11-1: Data Collector Agent XACs and Data Collector Interface XACs
Primary Data Collector
Secondary Data Collector
PE or
FRE
PE or
FRE
PE or
FRE
PE or
FRE
PE or
FRE
PE or
FRE
PE or
FRE
PE or
FRE
X.25 Network
Primary Data Collector SVC
Secondary Data Collector SVC
Data Collector Interface XAC
Data Collector Agent XAC
Physical link
9149
Data collector interface XACs

The X.25 network uses two XACs to interface with the data collector. One provides
the physical interface to the primary data collector and the other provides the
physical interface to the secondary data collector (see Figure 27.11-1). For
information on how to configure the data collector interface XAC, see chapter 27.14.
The Newbridge data collector is designed to run using the default link layer and
network layer parameters.
The data collectors are X.25 DTEs. While the XACs that interface to the data
collectors have the same configuration options as regular XACs, they generally use
the default XAC and NUA parameter values, with the exception of the CUG
membership requirements described below.
CUG considerations
To ensure secure access to the data collector, Newbridge recommends that the data
collector agents and the data collectors belong to the same CUG, which is only used
for this application.
27.11-2
(400)
X.25 Serivce

NNP 95-2035-01-00-B

Configure the NUA for the data collector agent so that the data collector agent can
establish calls only to the data collector and never receive incoming calls. Set the
CUG parameters to:

Incoming Calls Barred = Yes
Configure the NUAs for the data collectors so that the data collectors can receive
calls only from the data collector agent, but never establish calls to the data collector
agent. Set CUG parameters to:

Outgoing Calls Barred = Yes
Data collector
The data collector is a workstation that is linked to the X.25 network. The data
collector:
provides secure storage of X.25 SVC and PVC accounting data

allows users to generate invoices and business planning reports as well as
analyse network traffic

provides time synchronization between the data collector and the X.25 switch
using the NTP
The output from the data collector can be connected to a data processing computer
or to another data collector called a data server, through a TCP/IP connection
running over X.25, Ethernet or ATM.
GDI protocol
The GDI protocol controls the reliable transfer of transfer blocks between the NVM
of the accounting generation subsystem and the hard disk of the data collector. For
blocks to be transferred, an SVC is established from the data collector agent to the
primary and secondary data collectors. In the event of a primary data collector
failure, transfer blocks are sent to the secondary data collector and no data is lost.
When the primary data collector is running again, it receives the missing data from
the secondary data collector.
The data collector agent initiates a transfer when a transfer block is filled or after the
expiration of a configurable timer called the Maximum Time Between Transfers
Timer. This timer ensures that accounting data is transferred to a collector within a
certain period of time.
When the data collector has received a transfer block and has saved it successfully
to disk, the data collector sends an acknowledgment message to the data collector
agent. Upon receipt of this message, the accounting generation subsystem erases its
copy of the transfer block from NVM, and the data collector agent begins
transferring the next block if one is ready for sending.
X.25 Service
(400)
27.11-3


NNP 95-2035-01-00-B
The transfer block is re-sent if the data collector agent does not complete
transmission of the transfer block or it does not receive an acknowledgment message
within the time period specified by the configurable Transfer Block Retransmission
Timer. Before resending the transfer block, the data collector agent first clears the
existing SVC and attempts to re-establish one to the collector. This sequence is
repeated a configurable Maximum Retransmission Count number of times before
the primary data collector is declared out of service and the transfer block is sent to
the secondary data collector.
If the NVM of the accounting generation subsystem becomes full to the point that it
exceeds a 75% threshold, the data collector agent does not wait a full Maximum
Retransmission Count number of times before sending the transfer block to the
secondary data collector. When the Maximum Retransmission Count is set to zero
the switch attempts to send the transfer block to the secondary collector immediately
after the Transfer Block Retransmission Timer expires.
When transfer blocks are being sent to the secondary data collector, the switch
periodically tries to call the primary data collector. When the call is finally
re-established to the primary data collector, the transfer in progress to the secondary
data collector stops, and transfer to the primary data collector begins. If transfer to
both the primary and secondary data collector is unsuccessful, the switch continues
to try both collectors indefinitely.
27.11.2
Data Collector Agent Parameters

Table 27.11-1 lists the data collector agent parameters.
Table 27.11-1: Data Collector Agent Parameters
Parameter Name
27.11-4
Option or Range
Default
Primary Data Collector Address
NPI and 1 19 digits
None
Secondary Data Collector Address
NPI and 1 19 digits
None
Transfer Block Size
1, 2, 4, 8, 16, 32 or 64 kbytes
64 kbytes for PE card

16 kbytes for X.25 FRE
card
Maximum Time Between Transfers
0, 15, 30, 45 mins, 1, 2, 3, 4,

6, 8, 12 and 24 h.
24 h
Transfer Block Retransmission Count
0 10
Transfer Block Retransmission Timer
0 900 s in 5 s increments
60 s
Secondary Data Collector

Maintenance
Enable
Disable
Enable
(400)
X.25 Serivce

NNP 95-2035-01-00-B
27.11.3

Viewing the Data Collector Agent Parameters

Figure 27.11-2 shows the NMTI display for the data collector agent parameters.
Figure 27.11-2: Data Collector Agent Parameters Display
X25FRE Stations:nn
PA11-H1-00
Toronto:A
Alarms:1
11-May-1997
8:35a
Data Collector
---------------Primary Data Collector Address
Transfer Block Size
:x30201002341001
:x30201002342002
:64 Kbytes
:24 hrs
:60 secs
:1
CONFIG SWITCH X25 AGENTS COLLECTOR
F1-PRI_ADDR
F6-RETR_COUNT
F2-SEC_ADDR
F7-
F3-BLOCK_SIZE
F8-CANCEL
F4-MAX_TIME
F9-QUIT
F5-RETR_TIMER
F10-PROCEED
To view data collector agent parameters

CONFIG SWITCH X25 AGENTS COLLECTOR
27.11.4
Configuring the Data Collector Agent Parameters

This section describes the data collector agent parameters and provides
configuration guidelines.
Primary Data Collector Address

This parameter specifies the address of the primary data collector.
The address can be changed at any time with no disruption of service. When an
address change is made while the data collector is active, the data collector agent
completes all outstanding transactions before clearing the SVC and establishing an
SVC to the new address.
X.25 Service
(400)
27.11-5


NNP 95-2035-01-00-B
Range
TOA (i for international or n for national), NPI (x for X.121, e for E.164 digital, or m
for E.164 analog) and 1 to 19 address digits or wildcard characters (?).
Default
None

This parameter specifies the address of the secondary data collector.
The result of changing a value depends on the following scenarios:
The change occurs while the primary data collector is active: In this case the data
collector agent immediately polls the secondary data collector at the new address
to make sure it can be reached.
The change occurs while the secondary data collector is active and a connection
to the primary data collector cannot be made: In this case, if there is an
unacknowledged transfer block outstanding, it is processed before activation of
the new address. When the new address is activated, the data collector agent
immediately tries to transfer data to it.
Range
for E.164 analog) and 1 to 19 address digits or wildcard characters (?).
Default
None
Transfer Block Size

The data collector agent transfers accounting and time change information to the
data collector in units called transfer blocks. This parameter specifies the maximum
size of the transfer block.
The parameter is activated as soon as it is set or changed.
Options
1, 2, 4, 8, 16, 32 or 64 kbytes
Default
64 kbytes for the PE card
16 kbytes for the X.25 FRE card
27.11-6
(400)
X.25 Serivce

NNP 95-2035-01-00-B


This parameter specifies the maximum amount of time that can elapse between the
sending of consecutive transfer blocks. The data collector agent initiates a transfer
when a transfer block is full, or upon expiry of this timer, whichever occurs first. This
timer ensures that accounting data is transferred to the data collector within a certain
period of time.
Options
15, 30, 45 min, 1, 2, 3, 4, 6, 8, 12 and 24 h
Default
24 h

This parameter specifies the time period within which the data collector agent must
receive an acknowledgment message from the data collector. If this timer expires
before the data collector acknowledges receipt of a transfer block, the data collector
agent resends the transfer block. Before resending the transfer block, the data
collector agent clears the existing SVC and attempts to establish a new SVC to the
data collector.
Options
5 to 900 seconds in 5-second increments
Default
60 seconds

This attribute specifies the number of times the data collector agent can
unsuccessfully re-send a transfer block before declaring the data collector out of
service.
Range
0 to 10
X.25 Service
(400)
27.11-7


NNP 95-2035-01-00-B
Default
1

parameters.
For every switch that requires data collector services, you must configure the
data collector agent parameters and the data collector agent XAC.
In order for the switch to establish calls to the data collectors, the GAT must
contain entries that correspond to the primary and secondary data collector
addresses.
The NUAs assigned to the data collector agents and the data collectors should
belong to an exclusive CUG.

These parameters can be changed at any time with no disruption of service. When a
change is made while the data collector is active, the data collector agent completes
all outstanding transactions before clearing the SVC and activating the parameter.
To configure the data collector agent parameters

CONFIG SWITCHAGENTS COLLECTOR
PRI_ADDR SEC_ADDR
<address>
<address>
BLOCK_SIZE
<kbytes>
MAX_TIME RETR_TIMER RETR_COUNT

<time>
<seconds>
<count>
SK000683
where
address is the NPI and 1 to 19 digits in X.121 or E.164 address format, none*
kbytes is 1, 2, 4, 16, 32 and 64, 64* kbytes for the PE card, 16* kbytes for the X.25 FRE card
time is 15, 30, 45 min, 1, 2, 3, 4, 6, 8, 12 and 24 h*
seconds is 0 to 900 s, 60*
count is 1 to 10, 1*
* is the default
Note
You can accept the default values for all other XAC parameters.
27.11-8
(400)
X.25 Serivce

NNP 95-2035-01-00-B

To configure a data collector agent XAC

1.
Select an XAC and set the Service Type parameter to Data Collector Agent.
CONFIG X25_ACCESS XAC <xac> NET_LAYER SERVICE AGENT
COLLECTOR PROCEED
where xac is a valid XAC
2.
Configure an NUA and assign it to the XAC configured in step 1.

CONFIG X25_ACCESS NUA <address> ASSIGN_TO <xac> PROCEED
where
xac is the XAC configured in step 1
3.
Configure the CUG parameters for the NUA configured in step 2.

For information on why the CUG must be set, see section 27.11.1.
CONFIG X25_ACCESS NUA <address> SUBS_OPT CUG <index>
INTERLOCK <code>
where
address is the NUA configured in step 2
code is the CUG interlock code (1 to 65 535)
X.25 Service
(400)
27.11-9

NNP 95-2035-01-00-B
27.12

Accounting Subsystem
Configuration
This chapter provides a procedure describing the configuration of the X.25
accounting generation subsystem. For information on how to configure the data
collector, see the MainStreet Data Collector guide.
27.12.1
The following general procedure describes how to set up the accounting subsystem,
including:
accounting generation parameters

data collector agent parameters
data collector agent XAC
circuits for access lines to data collectors
interface XACs
Figure 27.12-1 shows an example accounting subsystem configuration.
X.25 Service
(400)
27.12-1


NNP 95-2035-01-00-B
Figure 27.12-1: Example Accounting Subsystem Configuration

Switch 11
DC agent
Pri address = 1234
Sec address = 5678
DC agent XAC
NUA = 11xxxx
Switch 22
Switch 33
DC agent
Pri address = 1234
Sec address = 5678
DC agent
Pri address = 1234
Sec address = 5678
DC agent XAC
NUA = 22xxxx
DC agent XAC
NUA = 33xxxx
Internal
X.25
network
DC interface XAC
NUA = 1234
Redirection
address = 2345
Link
address
= 1234
DC interface XAC
NUA = 5678
Redirection
address = 6789
Link
address
= 2345
Link
address
= 5678
Link
address
= 6789
Primary SVC connections

Secondary SVC connections
Redundant physical links
Data Collector
Data Collector
9810
1.
Configure accounting generation parameters on all switches that require the

generation of accounting records. See section 27.10.4.
When configuring the accounting generation parameters across multiple
switches, it is important to make sure that the segment size is the same for all
switches. Newbridge recommends that the collection interval be the same for
each switch.
2.
Configure the data collector agent parameters on all switches that require the
generation of accounting records. See section 27.11.4.
The primary and secondary addresses are the same for each switch. For
example, in Figure 27.12-1 the primary address is 1234 and the secondary
address is 5678. Note the addresses as they will be used in step 4.
27.12-2
(400)
X.25 Serivce

NNP 95-2035-01-00-B
3.

Configure the data collector agent XAC on all switches that require the
generation of accounting records. See the procedure To configure a data
collector agent XAC in section 27.11.4.
As shown in Figure 27.12-1, each data collector agent XAC has a dummy NUA.
For example, switch 22 has an NUA of 22xxxx.
Note
The dummy NUA of each data collector agent XAC belongs to the same CUG as the
NUA for the data collector.
4.
Configure the circuits for the access lines that physically connect the switches
to the data collectors. See chapter 27.13.
Newbridge recommends that you use different switches to connect each data
collector.
5.
Configure an interface XAC for the link to the primary data collector.
You can use the default XAC and NUA parameters (with the exception of the
CUG parameters in step 3). The NUA you assign to this XAC is the primary
data collector address configured in step 2.
As shown in Figure 27.12-1, the NUA for the interface XAC on switch 22 is 1234.
6.
Configure an interface XAC for the link to the secondary data collector.
You can use the default XAC and NUA parameters (with the exception of the
CUG parameters in step 3). The NUA you assign to this XAC is the secondary
data collector address configured in step 2.
7.
X.25 Service
For every interface that requires accounting record generation, ensure that
accounting generation is enabled.
a.
For NUAs, set the Accounting Activation parameter to Yes (see section
27.15.4).
b.
For PVCs, set the Accounting Activation parameter to Yes (see section
27.17.3).
c.
For X.75, set the Accounting Activation parameter to Yes (see section
27.10.4).
(400)
27.12-3

NNP 95-2035-01-00-B
27.13

Circuits for X.25 Access Lines

This chapter describes how to configure and connect circuits that carry traffic to and
from X.25 access lines. These circuits provide user access to the X.25 switch.
See chapter 27.8 for information about configuring and connecting circuits for
backbone trunks.
See chapters 27.14 and 27.15 for information about configuring the link layer,
network layer, NUAs and subscription options for X.25 access lines.
27.13.1
Understanding X.25 Access Methods

Network users connect to a 36120 MainStreet X.25 switch using:
direct LAPB access

encapsulated access over frame relay
Devices accessing the switch at basic rate (64 kb/s), super-rate (64 x n kb/s), and
transparent subrate (n x 8 kb/s) speeds can use either access method. Devices that
operate at subrate speeds other than n x 8 kb/s (for example, 9.6 and 19.2 kb/s) must
use encapsulated access.
Direct LAPB access

You can connect LAPB data streams directly to the switch over data or primary rate
interface circuits. Each direct LAPB connection requires an X.25 switch circuit
configured as a direct circuit.
An X.25 switch supports up to 62 direct connections at 64 kb/s, with a total
combined bandwidth of 3968 kb/s. Each direct circuit supports interface speeds
between 8 and 1984 kb/s, in 8 kb/s increments. A single direct circuit can use up to
1984 kb/s of bandwidth.
Note
Although direct circuits support super-rate applications, more efficient bandwidth
utilization may be realized by using frame relay encapsulation for high-speed
devices.
Figure 27.13-1 shows an example of direct LAPB access.
X.25 Service
(400)
27.13-1


NNP 95-2035-01-00-B
Figure 27.13-1: Direct LAPB Access

X.25 site
DCC
or
DNIC
m x n x 8 kb/s
LAPB
X.25
switch
DTE
64 x m kb/s
LAPB
TDM
network
PRI link
PRI
card
X.25
backbone
network
DTE
m
7296
Encapsulated access over frame relay

Encapsulated access is a method by which LAPB frames are transmitted to and from
the X.25 switch over frame relay PVCs. The encapsulation techniques maintain the
integrity of the X.25 link layer connection; the LAPB link traverses a frame relay link
and terminates at the X.25 switch. While both the X.25 switch and the FRS card
perform frame relay encapsulation/decapsulation functions, only X.25 switch can
terminate LAPB.
The encapsulated access method can be used to connect X.25 devices running at
basic rate, super-rate, and subrate speeds. X.25 devices that require subrate access to
the network at non-transparent speeds must use the encapsulated access method.
For LAPB access, the FRScard and the X.25 switch performs encapsulation and
decapsulation according to the following standards:
RFC 1490, and ANSI T1.617a Annex F Multiprotocol Encapsulation over Frame Relay
ANSI T1.617a Annex G Encapsulation of ITU-T X.25/X.75 over Frame Relay
LAPB Annex G encapsulation
Annex G encapsulation provides a means to encapsulate LAPB frames using a
2-byte header. Because of the low overhead, this is the preferred encapsulation
method for access to the X.25 switch.
When you configure an FRS circuit for LAPB Annex G encapsulation, you must
specify the maximum size of the X.25 packets that use the circuit. The size of the
LAPB frames is derived using the algorithms described in Appendix VI of
Recommendation X.25; for packet sizes greater than 128 bytes, 9 bytes are added to
the X.25 packet size. The Annex G encapsulation method adds a 2-byte header. The
switch calculates the resulting frame relay T1.618 frame size as shown in
Table 27.13-1.
27.13-2
(400)
X.25 Serivce

NNP 95-2035-01-00-B

Table 27.13-1: Packet and Frame Sizes for Annex G

X.25 Packet Size
16, 32, 64, or 128
266
256
267
512
523
1024
1035
2048
2059
4096
4107
Figure 27.13-2 shows the frame format.

Figure 27.13-2: Annex G Encapsulation of LAPB Frames
0
EA
Data Link
Connection
Identifier
(DLCI)
LAPB address field
LAPB address field
LAPB control field
LAPB control field

(X.25 - X.75)

(X.25 - X.75)
LAPB frame
T1.618 frame
Check sequence
Check sequence
EA
Flag
1 1
DE
Flag
1 1
BECN
LAPB frame
FECN
C/R
Annex G encapsulation
of a LAPB frame
Frame relay
information
field
7968
LAPB RFC 1490 encapsulation

Although RFC 1490 defines a multiprotocol encapsulation method, the FRS card
implementation currently supports only LAPB frames. This method adds an 8-byte
multiprotocol header to the LAPB frame. Because of the higher overhead, this is not
the preferred encapsulation method for access to the X.25 switch.
When you configure an FRS circuit for LAPB RFC 1490 encapsulation, you must
specify the maximum size of the X.25 packets that use the circuit. The LAPB frame
size is derived according to Appendix VI of Recommendation X.25; for packet sizes
greater than 128 bytes, 9 bytes are added to the X.25 packet size. The RFC 1490
encapsulation method adds an 8-byte header. The switch calculates the resulting
frame relay T1.618 frame size as shown in Table 27.13-2.
X.25 Service
(400)
27.13-3


NNP 95-2035-01-00-B
Table 27.13-2: Packet and Frame Sizes for RFC 1490

X.25 Packet Size
16, 32, 64, or 128
272
256
273
512
529
1024
1041
2048
2065
4096
4113
Figure 27.13-3 shows the frame format using LAPB as the encapsulated protocol.
Figure 27.13-3: RFC 1490 Encapsulation of LAPB Frames
0
EA
Data Link
Connection
Identifier
(DLCI)
0
EA
Flag
1 1
DE
BECN
FECN
C/R
RFC 1490 encapsulation

of a LAPB frame
Control 0 x 03
NLPID 0 x 08
0 x 46
LAPB frame
Flag
1 1
0 x 81
0 x 66
0 x 80
LAPB Address Field
LAPB Address Field
LAPB Control Field
LAPB Control Field

(X.25 - X.75)

(X.25 - X.75)
LAPB Frame
T1.618 Frame
Check Sequence
Check Sequence
Layer 2
protocol
ID
Layer 3
protocol
ID
Frame relay
information
field
7967
Frame relay encapsulation on the X.25 switch

An X.25 switch can terminate frame relay PVCs carrying encapsulated LAPB data
from a standards-compliant PAD or FRAD, or from the FRS card. Figure 27.13-4
shows both methods of encapsulated access.
27.13-4
(400)
X.25 Serivce

NNP 95-2035-01-00-B

Figure 27.13-4: Frame Relay Encapsulation Methods

X.25
X.25
FRE
or
FRE
PECard
card
FRS card
Annex G
or
RFC 1490
LAPB
DTE
Annex G
or
RFC 1490
Frame relay
Encapsulation
Encapsulation
X.25
network
Decapsulation
LAPB
DTE
Annex G
or
RFC 1490
Decapsulation
Frame relay
Annex G
or
RFC 1490
PAD/FRAD
7550
The X.25 switch performs the encapsulation/decapsulation function at the network

interface; it encapsulates LAPB frames coming from the X.25 network for
transmission to user devices over frame relay, and decapsulates frames transmitted
to the switch over frame relay.
When a PAD or FRAD is used to perform the LAPB encapsulation, it must comply
with the encapsulation standards defined in RFC 1490 or ANSI T1.617a Annex G.
Figure 27.13-5 shows encapsulated access using a standards-compliant PAD/FRAD.
Figure 27.13-5: Encapsulated Access Using a PAD/FRAD
X.25 site
LAPB
Frame
relay
DCC
or
DNIC
or
PRI
card
Frame relay
network
DTE
X.25
switch
X.25
backbone
network
LAPB-encapsulating
PAD/FRAD
7551
X.25 Service
(400)
27.13-5


NNP 95-2035-01-00-B
Frame relay encapsulation on the FRS card

On the 3600 MainStreet series bandwidth managers, the Release 4.0 FRS card
performs the encapsulation/decapsulation function on the access side of the X.25
network; the FRS encapsulates LAPB frames for transmission to the X.25 network
over frame relay, and decapsulates frames coming from the X.25 network over frame
relay and transmits them to the X.25 devices.
X.25 access lines connect to encapsulation circuits on the FRS card. When the FRS
receives frames from the X.25 devices, the frame feeder subsystem encapsulates the
LAPB frames in frame relay frames and inserts the DLCI for the appropriate PVC.
The FRS routes the frame relay frames to the X.25 switch over the frame relay
network. At the X.25 switch, the LAPB frames are decapsulated and processed by
the X.25 layer 2 and 3 protocols.
FRS cards must be equipped with a SRIM to provide encapsulation for
non-transparent subrate data streams using HCM, DDS, or X.50 rate adaption.
Basic rate and super-rate encapsulated access
For X.25 devices running at basic rate, super-rate, and transparent subrate speeds,
the FRS can encapsulate LAPB frames for transmission to local or remote X.25
switches. This method of X.25 access is used in two network scenarios. The first
allows X.25 devices to access X.25 switches over frame relay networks. In this case,
the FRS card is a remote feeder node that provides a high-speed connection to an
X.25 switch. Figure 27.13-6 shows an example.
Figure 27.13-6: Encapsulated Access Using the FRS Card
Frame relay site
X.25 site
Frame relay
connection
m x n x 8 kb/s LAPB
DTE
DTE
DCC
or
DNIC
FRS
card
PRI
card
PRI
card
64 x m kb/s
LAPB
Encapsulated LAPB
PRI
card
X.25
switch
X.25
backbone
network
TDM
network
m = Number of DS0s (1 to 31)

n = Transport bandwidth (1 to 8)
8544
In the second scenario, encapsulation is used within the 3600 MainStreet series
bandwidth manager system to increase the number of 64 x n kb/s connections to the
X.25 switch. While the X.25 switch provides a maximum of 62 circuits for direct
connections, the use of frame streams and DLCs allows multiple 64 x n kb/s devices
to access the switch through a single circuit on the card. The number of basic rate and
super-rate X.25 device connections can thus be substantially increased, depending
on engineering limitations.
27.13-6
(400)
X.25 Serivce

NNP 95-2035-01-00-B

Subrate encapsulated access

For X.25 devices running at subrate speeds, the FRS encapsulates the LAPB frames
and multiplexes the subrate frame streams onto high-speed frame relay PVCs. The
encapsulated frames are then sent directly to an X.25 switch on the same 3600
MainStreet node (see Figure 27.13-7), or routed over a frame relay network to an X.25
switch on a remote node.
The SRIM is an optional module on the FRS card that provides subrate multiplexing
using HCM, DDS, and X.50 rate adaption methods. While FRS cards without a SRIM
support subrate speeds, the speeds must be multiples of 8 kb/s. The SRIM allows the
FRS card to support encapsulation of subrate data streams that are not limited to
multiples of 8 kb/s.
Figure 27.13-7: Encapsulated Access for Subrate Devices
Frame relay / X.25 site
DNIC
FRS
card
X.25
switch
1.2 56 kb/s LAPB

DTE
X.25
backbone
network
DTU
8545
27.13.2
Configuring Direct Circuits

From the Control card NMTI, configure X.25 switch circuits as direct circuits
(DIRECT_CCT) to provide direct LAPB access to the switch. This type of
configuration is used for X.25 devices running at basic or super-rate speeds, or for
subrate devices using transparent rate adaption.
Note
You cannot use direct circuits for X.25 access lines running at non-transparent
subrate speeds such as 9.6, 14.4, and 19.2 kb/s. These lines must use encapsulated
access.
X.25 Service
(400)
27.13-7


NNP 95-2035-01-00-B
To configure direct circuits

Configure the application as DIRECT_CCT before configuring the interface speed or
transport bandwidth. The interface speed for the direct circuit must match the speed
of the interface circuit to which it connects.
APPLI
I/F_SPEED
TRANSP_BW
DIRECT_CCT
<speed>
<bandwidth>
SK000416
where
sn-cc is the slot number and circuit number on the card
speed is 8 to 1984 kb/s in multiples of 8, and must match the interface speed of the primary rate or data
interface circuit
bandwidth is n x 8 kb/s, where n is 1 to 8
27.13.3
Configuring Frame Relay Encapsulation Circuits

FRS circuits can be configured to perform frame relay encapsulation for basic rate,
super-rate, and transparent subrate devices. On FRS cards equipped with a SRIM,
FRS subrate circuits can be configured to perform encapsulation for subrate devices
using HCM, DDS, and X.50 rate adaption methods.
To create frame relay encapsulation circuits

Create frame relay encapsulation circuits on FRS cards from the Control card NMTI.
These circuits provide frame relay network access to X.25 devices running at
m x n x 8 kb/s, where m is the number of DS0s (1 to 31), and n is the transport
bandwidth (1 to 8).
APPLI
I/F_SPEED
TRANSP_BW
FR_ENCAP
<speed>
<bandwidth>
SK000417
where
sn-cc is the slot number and circuit number on the card
speed is 8 to 1984 kb/s in multiples of 8, and must match the interface speed of the primary rate or data
interface circuit
bandwidth is n x 8 kb/s, where n is 1 to 8
27.13-8
(400)
X.25 Serivce

NNP 95-2035-01-00-B

Note
Configure the application as FR_ENCAP before configuring the interface speed or
transport bandwidth. The interface speed for the frame relay encapsulation circuit
must match the speed of the primary rate or data interface circuit to which it
connects.
To create subrate frame relay encapsulation circuits

From the Control card NMTI, create subrate frame relay encapsulation circuits on
FRS cards equipped with a SRIM. These circuits provide frame relay network access
to X.25 devices running at non-transparent subrate speeds (for example, 9.6, 14.4,
and 19.2 kb/s).
Note
Before configuring a subrate circuit for frame relay encapsulation, configure the rate
adaption parameters for that subrate circuit. See chapter 25.9.
CONFIG CIRCUIT <sn-SRcc> FUNCTION
RATE_ADAPT
APPLI
(see Note)
FR_ENCAP
SK000418
where sn-SRcc is the slot number and subrate circuit number on the FRS card
Configuring the parameters for encapsulation circuits

When FRS circuits and FRS subrate circuits are configured to perform frame relay
encapsulation, you can configure the following parameters from the FRS NMTI:
frame size
encapsulation type
The parameters and allowable values are the same for subrate and super-rate
circuits.
Figure 27.13-8 shows the NMTI display for configuring the frame relay
encapsulation parameters. The non-configurable information fields are described in
Table 27.13-3. The configurable parameters are described in the subsections
following the table.
X.25 Service
(400)
27.13-9


NNP 95-2035-01-00-B
Figure 27.13-8: Parameters for Frame Relay Encapsulation Circuits

FRS
Stations:nn
P412-H1-00
Toronto:A
Alarms:1
ENCAP_CCT SR1
Status
Using Circuit
Interface Speed
Congestion Status
Connected To
Encapsulation type
11-May-1997
8:35a
:OOS-Disconnected
:A1-2
:9600 bps
:GREEN
:4 Kbytes
:80%
:50%
:512 Octets
:529 Octets
:S1-100
:LAPB RFC 1490
CONFIG ENCAP CCT SR1

F1-FRAME_SIZE
F6-ENCAP_TYPE
F2-THRESHOLDS
F7-
F3F8-CANCEL
F4F9-QUIT
F5F10-
Table 27.13-3: Encapsulation Circuit Information Fields

Field
27.13-10
Description
Status
The current operating state of the circuit.

In Service: Active state; the circuit is configured as connected and is capable of
carrying traffic.
OOS-Disconnected: Inactive state; the circuit is not connected.
Busy Out: Inactive state; the circuit is configured, connected and busied out for
maintenance.
Using Circuit
Shows the actual FRS circuit selected, or, if a subrate FRS circuit is selected,
the rate adapted FRS circuit to which the subrate encapsulation circuit is
connected.
Interface Speed
Congestion Status
The current congestion state of the frame stream.

configured.
Required Frame
Relay Frame Size
The size of the frame relay T1.618 frame after the LAPB frame is encapsulated.
This is a readable value that is calculated based on the value of the
Encapsulated Protocol Tax Frame Size parameter. The value of this field must
be less than the Maximum Frame Size parameter for the frame stream to which
this circuit is connected.
Connected To
The frame stream-DLCI or FASTbus circuit-DLCI to which the circuit is

connected.
(400)
X.25 Serivce

NNP 95-2035-01-00-B

Encapsulation circuit congestion thresholds

The ranges and default values for the ACT, MCT and SCT parameters are identical
to those for frame streams on FRS cards. See section 25.6.2.
For most X.25 access lines, Newbridge recommends the default values for the ACT,
MCT and SCT parameters. For high-speed access lines (>64 kb/s), you may have to
increase the buffer size (ACT) if statistics indicate that the circuit is frequently
congested.
Encapsulated Protocol Maximum Frame Size

This parameter specifies the maximum allowable size of X.25 packets that can be
transmitted on the circuit.
When the encapsulation type is LAPB RFC 1490 or LAPB Annex G, you must specify
an X.25 packet size value equal to or greater than the maximum value of the
Allowable Packet Size (N1) parameter for the X.25 access line that uses the
encapsulation circuit.
Once you configure an X.25 packet size, the Required Frame Relay Frame Size field
displays the size of the frame relay frames after encapsulation. This field indicates
the minimum value required for the Maximum Frame Size parameter for the frame
stream circuit to which the encapsulation circuit connects.
Options
16, 32, 64, 128, 256, 512, 1024, 2048, or 4096 bytes
Default
512
Encapsulation type
This parameter specifies the encapsulation method as either LAPB RFC 1490 or
LAPB Annex G. Transparent HDLC is not recommended. When you select LAPB
Annex G, the switch adds a 2-byte header to each frame being encapsulated. When
you select LAPB RFC 1490, the switch adds an 8-byte multiprotocol header to each
LAPB frame being encapsulated.
For encapsulating X.25 packets for transmission to an X.25 switch, you should select
LAPB Annex G.
Options
LAPB RFC 1490 or LAPB Annex G
Default
LAPB Annex G
X.25 Service
(400)
27.13-11


NNP 95-2035-01-00-B

You must configure the X.25 packet size so that the value is equal to or greater than
the value of the maximum Allowable Packet Size parameter for the XAC that uses
the encapsulation circuit. The Required Frame Relay Frame Size parameter indicates
the minimum value required for the Maximum Frame Size parameter for the frame
stream circuits to which the encapsulation circuit connects.
Table 27.13-4 shows the dependencies between the packet and frame size
parameters using Annex G encapsulation. Note that the default values are
acceptable unless you configure the Allowable Packet Size parameter to greater than
512.
Table 27.13-4: Packet and Frame Size Dependencies for Annex G
X.25 Switch NMTI
FRS NMTI
X.25 Switch NMTI
The Maximum Allowable

Packet Size for the XAC
is Configured to:
The X.25 Packet Size

Configured for the
ENCAP_CCT Must be at
Least:
The Required Frame

Relay Frame Size for the
ENCAP_CCT is
Automatically Set to:
The Maximum Frame Size

Configured for the Frame
Stream Must be at Least:
16, 32, 64, or 128
16, 32, 64, or 128
266
266
256
256
267
267
512*
512*
523*
523 (1600*)
1024
1024
1035
1035
2048
2048
2059
2059
4096
4096
4107
4107
Notes
1. Asterisks (?) indicate the default values.
Figure 27.13-9 shows the relevant NMTI screens and the packet and frame size
dependencies.
27.13-12
(400)
X.25 Serivce

NNP 95-2035-01-00-B

Figure 27.13-9: Configuring Packet and Frame Sizes for an Encapsulation Circuit
X25FRE Stations:5
PA11-H0-01
OTTAWA:A2
Alarms:4
07-Jun-96
9:17A
NETWORK LAYER
-----------------------Packet Size
Allowed
-----------------------16
No
32
No
64
No
128
Yes
256
Yes
512
Yes
1024
No
2048
No
4096
No
CONFIG X25_ACCESS XAC 112 NET_LAYER PACKETS
F1-ADD
F6-
F2-REMOVE
F7-
FRS MainStreet
P114-H0-00
F3F8-
F4F9-QUIT/SAVE
OTTAWA:A2
Alarms:4
ENCAP_CCT SR1
Status
Using Circuit
Interface Speed
Congestion Status
Connected to
Encapsulation type
F5F10-CONTINUE
07-Jun-96
9:17A
:OOS-Disconnected
:A1-2
:9600 bps
:GREEN
:4 Kbytes
:80%
:50%
:512 Octets
:529 Octets
:S1-100
:LAPB RFC 1490
CONFIG ENCAP_CCT SR1

F1-FRAME_SIZE
F6-ENCAP_TYPE
F2-THRESHOLDS
F7-
X25FRE Stations:5
F3F8-CANCEL
PA11-H0-01
F4F9-QUIT
OTTAWA:A2
Frame Stream S1
Status
Using Circuit
Interface Speed
Congestion Status
Maximum Frame Size
Number of Connections
Flags Between Frames
Protocol Type
Timeout
CONFIG
Alarms:4
F5F1007-Jun-96
9:17A
:OOS-Disconnected
:A1-1
:256000 bps
:GREEN
:10 Kbytes
:80%
:50%
:1600 bytes
:0
:1
:Annex D Bidirectional
:15 secs
STREAM S1
F1-FRAME_SIZE
F6-
F2-THRESHOLDS
F7-
F3-NUM_FLAGS
F8-CANCEL
F4-SHOW_CONNS
F9-QUIT
F5-PROTOCOL
F107520
X.25 Service
(400)
27.13-13


NNP 95-2035-01-00-B
To configure encapsulation circuit parameters

FRAME_SIZE
THRESHOLDS
ENCAP_TYPE
X.25_PKT_SZ
LAPB_1490
LAPB_ANNXG
<pkt_size>
ACT
SCT
MCT
<act>
<sct>
<mct>
SK000419
where
pawkiest is the number of octets (16, 32, 64, 128, 256, 512*, 1024, 2048, or 4096)
act is 1 to 64 kbytes, 4*
sct is 1 to 100%, 80*
mct is 1 to 100%, 50*
Viewing FRS circuit information

From the FRS NMTI, you can view the configuration and status of all FRS circuits by
entering:
Figure 27.13-10 shows an example NMTI display. The Circuit and Application fields
show each FRS circuit configured as one of the following:
STREAM
ENCAP_CCT
CPSS
RATE_ADAPT
Although FRS subrate circuits can be configured as STREAM or ENCAP_CCT, they

are not displayed in the Circuit or Application fields, but appear in the Stream/CCT
field when they are connected to a rate adapted circuit.
27.13-14
(400)
X.25 Serivce

NNP 95-2035-01-00-B

Figure 27.13-10: FRS Circuit Configuration Display

FRS
Stations:nn
Circuit
--------A1-1
A1-2
A1-3
A1-3
A1-4
A1-5
A1-6
A1-7
A1-8
A1-9
A1-10
A1-11
A1-12
A1-13
A1-14
A1-15
P412-H1-00
Toronto:A
Stream/act
----------S1
2
SR2
SR3
SR4
n/a
SR29
7
S8
9
S10
S11
S12
S13
S14
---
Alarms:1
Application
------------STREAM
ENCAP_CCT
RATE_ADAPT
RATE_ADAPT
RATE_ADAPT
CPSS
RATE_ADAPT
ENCAP_CCT
STREAM
ENCAP_CCT
STREAM
STREAM
STREAM
STREAM
STREAM
RATE_ADAPT
11-May-1997
Speed
-------256000bps
9600bps
9600bps
9600bps
9600bps
56000bps
9600bps
2400bps
56000bps
8000bps
64000bps
64000bps
64000bps
64000bps
64000bps
64000bps
8:35a
Status
-------OOS-LMI
In Service
In Service
In Service
OOS-LMI
In Service
In Service
OOS-Disconnected
In Service
In Service
In Service
In Service
In Service
In Service
In Service
OOS-Disconnected

1-NEXT
6-
27.13.4
2-PREVIOUS
7-
38-CANCEL
49-QUIT
510-
Configuring the Parameters for Frame Stream Circuits

You must configure and connect frame stream circuits to carry encapsulated LAPB
frames between the FRS and the X.25 switch. Configure these circuits as normal
frame relay circuits, but observe the recommendations in the following subsections.
For more information, see chapter 25.6.
Maximum frame size

The Maximum Frame Size parameter must be equal to or greater than the value of
the Required Frame Relay Size parameter for the encapsulation circuits (see
Figure 27.13-9).
Congestion thresholds
On the FRS card, set the ACT to 32 kbytes. Accept the default values for MCT and
SCT.
On the X.25 switch, set the ACT to 100 kbytes. Accept the default values for MCT and
SCT.
X.25 Service
(400)
27.13-15


NNP 95-2035-01-00-B
Link protocol type

Set the link management protocol to one of the bidirectional variants.
27.13.5
Configuring Connections for X.25 Access Lines

Figure 27.13-11 shows the five types of connections that provide X.25 access to the
X.25 switch. All connections can be made in either direction.
A frame stream circuit on the X.25 FRE card (FRE_STREAM) is connected to a
27.13-16
frame stream circuit on an FRS card (FRS_STREAM). This provides frame relay
encapsulated access to the X.25 switch when the FRS and X.25 FRE cards are
located on the same node.
A frame stream circuit on the X.25 FRE card (FRE_STREAM) is connected to a
primary rate interface circuit on an E1 card (E1_NOSIG). This provides frame
relay encapsulated access to the X.25 switch over a primary rate link when the
FRS and X.25 FRE cards are located on different nodes.
A direct circuit (FRE_DIRCCT) is connected to a data interface circuit on a V.35
card (V.35_DCC). This provides direct LAPB access to the X.25 switch from the
data interface card.
A direct circuit (FRE_DIRCCT) is connected to a primary rate interface circuit on
an E1 card (E1_NOSIG). This provides direct LAPB access to the X.25 switch over
a primary rate link.
A direct circuit is connected to another direct circuit for testing circuits within the
X.25 switch.
(400)
X.25 Serivce

NNP 95-2035-01-00-B

Figure 27.13-11: Valid X.25 Super-rate Connections

3600 MainStreet
Circuit
A5-01
A5-02
A5-03
A5-04
A5-05
A5-06
A5-07
A5-08
A5-09
A5-10
A5-11
A5-12
1117-H1-00
Name
Toronto:A
Type
FRE_STREAM
FRE_STREAM
FRE_DIRCCT
FRE_DIRCCT
FRE_DIRCCT
FRE_STREAM
FRE_STREAM
FRE_STREAM
FRE_STREAM
FRE_DIRCCT
FRE_DIRCCT
FRE_DIRCCT
Alarms:1
Circuit
*A3-01
*A6-02
*A7-03
*A6-12
*A5-10
--------*A5-05
-----
Name
11-May-1997
8:35a
Type
FRS_STREAM
E1_NOSIG
V.35_DCC
E1_NO_SIG
FRE_DIRCCT
Conv
FRE_DIRCCT
"*" show current connections; "!" show connections under maintenance.

CONFIG CONNECT 5-1
1-SHOW_CCT
6-PROTECTING
27.13.6
2-DISCONNECT
7-
3-TO_CIRCUIT
8-CANCEL
49-QUIT
5-PROT_BY
0-
Connecting Direct Circuits

Direct circuits connect to data interface circuits or primary rate interface circuits to
provides direct LAPB access to the X.25 switch.
To connect direct circuits

From the Control card NMTI, connect the direct circuit to a data or primary rate
interface circuit.
CONFIG CONNECT <sn-cc> TO_CIRCUIT <sn-cc> PROCEED
where sn-cc is the slot number and circuit number on the card
27.13.7
Connecting Encapsulation Circuits

The connections required for encapsulation circuits depend on whether the
encapsulation circuit is a super-rate or subrate circuit. While both encapsulation
circuit types connect to frame stream-DLCIs to allow encapsulated frames to be
transmitted over a frame relay PVC, subrate encapsulation circuits also require
connections to rate adapted circuits.
X.25 Service
(400)
27.13-17


NNP 95-2035-01-00-B
The DLCI connection is the same for both subrate and super-rate circuits.
Connections are allowed both ways; that is, you can connect an encapsulation circuit
to a DLC, or a DLC to an encapsulation circuit.
Class-of-service parameters can be set for the connections. Class-of-service
enforcement can be enabled only for the DLCI side of the connection, not for the
ENCAP_CCT side. For more information about class-of-service parameters, see
chapter 25.8.
Caution
If you change the values for the class-of-service parameters, the parameters must
also be configured at the X.25 switch end of the connection (the stream-DLCI to
which the XAC connects). The values must match at both ends of the connection.
Super-rate encapsulation circuits

You connect super-rate encapsulation circuits in two steps, as shown in
Figure 27.13-12. The numbers in the figure correspond to the steps in the following
procedure.
Figure 27.13-12: Connections for Super-rate Encapsulation Circuits

DCC or
PRI card
FRS card
Frame
relay
network
m x n x 8 kb/s
1
HDLC device
= Data or primary rate interface circuit
8037
To connect super-rate encapsulation circuits

1.
27.13-18
From the Control card NMTI, connect the super-rate encapsulation circuit to a
data or primary rate interface circuit.
(400)
X.25 Serivce

NNP 95-2035-01-00-B

CONFIG CONNECT <sn-cc1> TO_CIRCUIT <sn-cc2> PROCEED

where
sn-cc1 is the FRS slot number and encapsulation circuit number
sn-cc2 is the data or primary rate card slot number and circuit number
2.
From the FRS NMTI, connect the super-rate encapsulation circuit to a frame
stream-DLCI.
CONFIG CONNECT <cc> or <Scc-dlci> TO <cc> or <Scc-dlci>
where
cc is the encapsulation circuit
Note
DLCs.
Subrate encapsulation circuits

You connect subrate encapsulation circuits in three steps, as shown in
Figure 27.13-13. The numbers in the figure correspond to the steps in the following
procedure.
Figure 27.13-13: Connections for Subrate Encapsulation Circuits
DCC or
DNIC
FRS card
Frame
relay
network
3
1.2 to 56 kb/s
1
2
HDLC device

8038
X.25 Service
(400)
27.13-19


NNP 95-2035-01-00-B
Subrate encapsulation circuits on the FRS card can be connected only to FRS circuits
configured for rate adaption. The rate-adapted circuit is typically an aggregate
circuit which carries X.25 traffic to and from X.25 access lines. As shown in
Figure 27.13-14, the connection must be made from the subrate encapsulation circuit
to the rate adapted circuit.
Figure 27.13-14: Subrate Encapsulation Circuit Connection
3600 MainStreet
Circuit
1117-H1-00
Name
Toronto:A
Type
A3-SR01
A3-SR02
A3-SR03
A3-SR04
A3-SR05
A3-SR06
A3-SR07
A3-SR08
A3-SR09
A3-SR10
A3-SR11
Alarms:1
Circuit
FRS_SBRENC
FRS_SBRENC
FRS_SBRENC
FRS_SBRSTR
FRS_SBRENC
FRS_SBRENC
FRS_SBRENC
FRS_SBRENC
FRS_SBRSTR
FRS_SBRENC
FRS_SBRENC
11-May-1997
Name
*A8-B01/3
---------------------
Type
8:35a
Conv
FRS_RATEAD
"*" show current connections; "!" show connections under maintenance.

CONFIG CONNECT 3-SR1
1-SHOW_CCT
6-
27-
3-TO_CIRCUIT
8-CANCEL
49-QUIT
50-
To connect subrate encapsulation circuits

1.
From the Control card NMTI, connect the subrate encapsulation circuit to a rate
adaption circuit:
where
sn-SRcc is the FRS slot number and subrate encapsulation circuit number
sn-cc is the FRS slot number and rate adaption circuit number
2.
From the Control card NMTI, connect the rate adaption circuit to a data
interface circuit:
CONFIG CONNECT <sn-cc1> TO_CIRCUIT <sn-cc2> PROCEED
where
sn-cc1 is the FRS slot number and rate adaption circuit number
sn-cc2 is the data interface slot and circuit number
3.
From the FRS NMTI, connect the subrate encapsulation circuit to a frame
stream-DLCI:
CONFIG CONNECT <SRcc> TO <Scc-dlci>
27.13-20
(400)
X.25 Serivce

NNP 95-2035-01-00-B

where
SRcc is the subrate encapsulation circuit
Note
DLCs.
27.13.8
Connecting XACs
An XAC is a virtual port that terminates an X.25 access line on the switch. From the
X.25 switch NMTI, you connect XACs to direct circuits for direct LAPB access, or to
frame-stream-DLCIs (Scc-DLCI) or FASTbus station-DLCIs (Fnn-DLCI) for
encapsulated access. You do not have to set any parameters for
XAC-to-DIRECT_CCT connections. For connections between an XAC and an
Scc-DLCI or Fnn-DLCI, you must select the encapsulation method (RFC 1490 or
Annex G), and optionally configure the class-of-service parameters.
To connect XACs to direct circuits

CONFIG CONNECT <Xxac> TO <dir_cct>
where
Xxac is a valid XAC
dir_cct is a valid direct circuit (1 to 62)
To connect XACs to frame stream-DLCIs or FASTbus station-DLCIs

CONFIG CONNECT <Xxac> TO <Scc-dlci or Fnn-dlci> [ANNEX_G]
PROCEED INFO_RATE
CIR
BC
BE
ENABLE
<cir>
<bc>
<be>
FROM_DLCI
DISABLE
TO_DLCI
SK000420
where
Xxac is a valid XAC
Scc-dlci is a frame stream circuit and DLCI
Fnn-dlci is a FASTbus station and DLCI
cir is the committed information rate (0 to 1984 kb/s)
bc and be are the committed burst size and excess burst size (0 to 1984 kb)
X.25 Service
(400)
27.13-21

27.13.9

NNP 95-2035-01-00-B
Configuring Class-of-service Parameters for

Encapsulated Access
This section provides high-level guidelines for configuring class-of-service
parameters on ENCAP circuit-to-DLCI and XAC-to-DLCI connections. Because
many factors must be considered when engineering frame relay links, these
guidelines should not be viewed as recommendations, but rather suggestions.
Consider this information to be a starting point from which you can begin to
engineer the network for optimum performance.
You can set the class-of-service parameters according to TDM principles or statistical
multiplexing principles.
Non-statistical multiplexing approach

This approach applies TDM principles rather than taking advantage of the statistical
multiplexing capabilities of frame relay. Consider this approach as a conservative
method that provides maximum throughput performance, but does not make the
best use of available bandwidth. Use the following guidelines to configure the class
of service parameters for each frame relay PVC, and to determine the required frame
stream bandwidth.
CIR
Set the CIR equal to the interface speed of the X.25 access line. Since the CIR is
configured in 1 kb/s increments, always round up to the nearest value. For example,
if the access line speed is 9.6 kb/s, set the CIR to 10 kb/s.
Bc
Set the Bc equal to the CIR.
Be
Set the Be to 0.
Frame stream bandwidth
Calculate the bandwidth required for the frame stream by adding all of the CIRs of
the access lines. For example, if the FRS is supporting six X.25 access lines running
at 9.6 kb/s, the frame stream bandwidth must be 64 kb/s (6 9.6 = 57.6).
Statistical multiplexing approach

This approach applies statistical multiplexing principles to optimize bandwidth
usage. With this method, the bandwidth of the frame stream can be substantially less
than the sum of the X.25 access line speeds. The guidelines are based on the
following assumptions:
all the access lines do not transmit bursts of data at the same time
all the access lines do not burst at 100% of the interface speeds
27.13-22
(400)
X.25 Serivce

NNP 95-2035-01-00-B

Use the following guidelines to configure the class of service parameters for each
frame relay PVC, and to determine the required frame stream bandwidth.
CIR
Set the CIR to 75% of the peak load on the access line. Since the CIR is configured in
1 kb/s increments, always round up to the nearest value. For example, if the peak
load on a 9.6 kb/s access line is 50%, the CIR is calculated as follows:
9.6 0.5 0.75 = 3.6, therefore the CIR = 4 kb/s
Bc
The Bc must be greater than the maximum frame size and greater than the maximum
burst size, if known. If not, set the Bc to 4 CIR or 10 maximum frame size,
whichever is greater. As above, round up to the nearest value. For example, if the
maximum X.25 packet size on an access line is 256 bytes, the maximum frame size is
273 bytes (allowing for RFC 1490 encapsulation overhead), and the Bc is calculated
as follows:
273 8 (bits) 10 = 21 840, therefore the Bc = 22 kb
Be
Set the Be by determining the values of Tc and EIR, and calculating the Be value.
Determine the value of Tc using the CIR and Bc values:
Bc
CIR
Tc=
Determine the value of the EIR using the access line speed and the CIR value:
EIR = speed CIR
Calculate the Be using the values of Tc and EIR:
Be = Tc EIR
For example, for a 9.6 kb/s access line with a CIR of 4 kb/s and a Bc of 22, the above
formulae generate the following:
Tc = 5.5 s
EIR = 5600 b/s
Tc EIR = 30 800; therefore the Be = 31 kb
X.25 Service
(400)
27.13-23


NNP 95-2035-01-00-B
Frame stream bandwidth

Calculate the bandwidth required for the frame stream by adding all of the CIR
values of the access lines. For example, if the FRS is supporting six X.25 access lines
with CIR values set to 4 kb/s, the frame stream bandwidth must be 24 kb/s.
Note
You can configure frame streams to increase the booking factor above 100%. While
this increases the statistical gain, it negates the class-of-service parameters (the CIR
might not be achieved and the service essentially becomes best effort). It is therefore
advisable to leave the booking factor at its default value unless you have extensive
knowledge of the traffic profiles within the network.
27.13-24
(400)
X.25 Serivce

NNP 95-2035-01-00-B
27.14

XAC Parameters
This chapter describes how to configure the XAC interface parameters.
27.14.1
Understanding XACs
An XAC is a virtual port that terminates an X.25 access line on the switch. XACs
define the link layer, network layer, NUAs, and facilities for physically connected
X.25 devices. One XAC is configured for each X.25 device connected to the switch.
Typically, an XAC identifies an X.25 interface to a subrate or super-rate DTE or an
internal DTE; however, XACs are also used to connect other X.25 switches, in the
case of gateways, and to connect functional subsystems such as the NUI validation
servers.
From a configuration point of view, the term XAC refers to the collection of
parameters that define the link and network layer operation, addresses, and call
subscription options for an X.25 device. Once an NUA is assigned to an XAC
interface, the XAC is considered active.
The PE card supports up to 992 XACs, while the X.25 FRE card supports a maximum
of 128 XACs. The actual number supported on a particular switch is determined by
engineering constraints; the maximum theoretical limit is specified by the Number
of XACs parameter (see chapter 27.5).
27.14.2
Configuration overview
Typically, you perform the following steps to fully configure an XAC.
1.
Configure the XAC interface parameters:
link layer parameters (see section 27.14.5)

network layer parameters (see section 27.14.8)
address translations and screening options (see section 27.14.11)
X.25 Service
2.
Configure the X.121 or E.164 address and assign it to an XAC. See section
27.15.4.
3.
Configure the NUA subscription options (facilities). See section 27.15.7.
(400)
27.14-1


NNP 95-2035-01-00-B
You can also use the COPY command to copy the configuration parameters of an
XAC to one or more XACs. See chapter 27.16.
27.14.3
Understanding Link Layer Parameters

LAPB, which operates at the data link level (layer 2) of X.25, defines the link
initialization procedure that establishes and maintains communications between a
DTE and the DCE. LAPB is a point-to-point protocol that transmits data in units
called frames.
For XACs, you can configure the following link layer parameters:
interface type (DCE or DTE)

modulus (modulo 8 or modulo 128)
LAPB timers (T1, T2, T3, Congestion)
LAPB counters (N2 and k)
Link layer parameters are not configurable for NUI server agent and accounting
agent XACs. Both of these service types operate internally and have no link layer
interface.
27.14.4
Viewing Link Layer Parameters

Figure 27.14-1 shows the NMTI display for the link layer parameters.
Figure 27.14-1: Link Layer Parameters Display
X25FRE Stations:nn
PA11-H1-00
Toronto:A
Alarms:1
11-May-1997
LINK LAYER
---------Link Layer Interface Type
Maximum Frame Window Size
Congestion Timer
:DCE
:8
:7
:10
:3000 ms
:200 ms
:60000 ms
:3000 ms
:517
8:35a
CONFIG X25_ACCESS XAC 112 LINK_LAYER

F1-DTE/DCE
F6-
27.14-2
F2-SEQ_NUMBER
F7-
(400)
F3-WIN_SIZE
F8-CANCEL
F4-N2
F9-QUIT
F5-TIMERS
F10-
X.25 Serivce

NNP 95-2035-01-00-B

To view link layer parameters

CONFIG X25_ACCESS XAC <xac> LINK_LAYER
where xac is 1 to 128 for X.25 FRE cards and 1 to 992 for PE cards
27.14.5
Configuring Link Layer Parameters

This section describes the link layer parameters and provides configuration
Note
For most X.25 access lines, the link layer default values are acceptable. However,
ensure that the link layer interface type is set to DCE on one end of the link and DTE
on the other end.
Link Layer Interface Type

This parameter specifies the type of link layer interface supported by the switch on
this XAC. Normally, DTE specifies user devices, and DCE specifies network
equipment. However, network equipment can be defined as DTE; for example, in
the case of a private network connecting to a public network.
This parameter must be set to DCE on one end of the link and DTE on the other end.
Either end can be set to DTE or DCE, as long as the two ends are different.
The Link Layer Interface Type does not have to match the Packet Layer Interface
Type, although these parameters normally match.
Caution
When you change the value of this parameter for an active XAC, the switch clears all
calls on the access line and restarts the link.
Options
DTE or DCE
Default
DCE
X.25 Service
(400)
27.14-3


NNP 95-2035-01-00-B

This parameter specifies the link modulo used to control frame sequence numbers
for the LAPB link. Enter 8 for modulo 8 operation (normal), or 128 for modulo 128
operation (extended).
Options
8 or 128
Default
8

This parameter specifies the maximum number of I-frames that can be outstanding
or unacknowledged at any given time. Enter a number from 1 to 7 if the Frame
Sequence Numbering parameter is set to 8, or a number from 1 to 127 if it is set to 128.
Range
1 to 7 (modulo 8) or 1 to 127 (modulo 128)
Default
7

This parameter specifies the maximum number of attempts to complete a successful
transmission of a command frame on the link. Since this value includes the initial
transmission, the number of retransmissions is actually N2 minus 1.
Range
1 to 20
Default
10

This parameter specifies the maximum amount of time that can elapse before a
window of frames, as specified by the Maximum Frame Window Size parameter,
must be acknowledged by the receiver of the frames. If the frames are not
acknowledged within the T1 time period, the sender retransmits the frames. (The
number of retries is specified by the N2 parameter).
27.14-4
(400)
X.25 Serivce

NNP 95-2035-01-00-B

The value of T1 must be greater than T2 and less than T3 (T3 > T1 > T2).
Range
10 to 120 000 ms in multiples of 10 ms
Default
3000 ms

This parameter specifies the maximum amount of time a receiving device can wait
before generating a response or acknowledgment frame. This parameter is used to
encourage piggybacking of acknowledgments in data packets. The value of T2 must
be less than T1 (T2 < T1).
Range
0 to 3000 ms in multiples of 100 ms
Default
200 ms

This parameter specifies the time interval between the sending of RR frames on an
idle link (no I-frames). When this timer is enabled, the switch generates RR frames
every T3 ms. If there is no response, the link is taken down. When this timer is
disabled, there is no indication if the link goes down.
The value of T3 must be sufficiently greater than the value of T1 so that the
expiration of T3 is a valid indication that the link is in a non-active state (T3 > T1).
This timer should always be set for XACs that belong to hunt groups (see
chapter 27.18).
Range
Default
60 000 ms
X.25 Service
(400)
27.14-5


NNP 95-2035-01-00-B
Congestion Timer
This parameter specifies the maximum time to wait for a congested LAPB link to
become uncongested. This timer starts when the LAPB transmit queue exceeds a
pre-determined threshold. If the timer expires before the transmit queue falls below
the threshold, the link is brought down. This prevents one link from using a
disproportionate amount of resources on the switch. Avoid setting this value too
small for links that experience bandwidth bottlenecks or large volumes of bursty
traffic.
Range
Default
3000 ms
Maximum Information Frame Size

This non-configurable field displays the value of N1. It is derived from the highest
allowable packet size value.

Observe the following restrictions and interdependencies when configuring the link
layer parameters.
expiration of T3 is a valid indication that the link is in a non-active state.

The value of T2 must be less than T1.
You cannot configure link layer parameters for NUI server agent and accounting
agent XACs.

When you change the Link Layer Interface Type parameter for an active XAC, the
switch automatically disables and then re-enables the XAC to activate the change.
The switch clears all calls on the access line and the link restarts. The change is
effective once the link restarts.
27.14-6
(400)
X.25 Serivce

NNP 95-2035-01-00-B

Changing the value of the Inactivity Timer (T3) for an in-service link has the
following results.
When timer T3 is changed from 0 to some other value, the timer starts only when
the link is restarted or when a frame is sent or received over the link. For example,
if the remote DTE is running an idle timer, timer T3 starts when the DTE timer
expires and the DTE transmits an RR frame.
When timer T3 is enabled (not 0) and the value is changed, the current timeout
value is allowed to expire before the new value takes effect. For example, if the
timer is set to 30 seconds and then changed to 1 second, the timer may take up to
30 seconds to expire before 1-second timeouts occur.
You can change the values of all other link layer parameters at any time with no
To configure link layer parameters

DTE/DCE
SEQ_NUMBER
WIN_SIZE
N2
<DTE/DCE>
<seq_number>
<k>
<n2>
T1
<t1>
T2
TIMERS
T3
<t2> <t3>
CONGST_TMR
<congst_tmr>
SK000421
where
xac is a valid XAC
seq_number is 8* for sequence numbers 1 to 7 or 128 for sequence numbers 1 to 127
k is 1 to 7* if SEQ_NUMBER is set to 8, or 1 to 127 if it is set to 128
n2 is 1 to 20, 10*
t1 is 10 to 120 000 ms in multiples of 10 ms, 3000*
t2 is 0 to 3000 ms in multiples of 100 ms, 200*
t3 is 0 to 120 000 ms in multiples of 10 ms, 60 000*
congst_tmr is 10 to 120 000 ms in multiples of 10 ms, 3000*
27.14.6
Understanding Network Layer Parameters

The network layer of X.25, also called the packet layer, defines the procedures that
establish and clear calls, transfer data, and handle error correction over the network.
X.25 Service
(400)
27.14-7


NNP 95-2035-01-00-B
Packet sequence numbering

During X.25 calls, packets are numbered sequentially for each direction of
transmission to protect against packet duplication, loss, or corruption, and to ensure
packets arrive in the correct order. For modulo 8 (basic) sequencing, the numbers
cycle through 0 to 7. For modulo 128 (extended) sequencing, the numbers cycle
through 0 to 127. Modulo 128 is typically used to attain the high throughput required
on satellite or LAN connections. In these types of network applications, sequence
numbers 0 to 7 can be exhausted by the transmitting device before the receiving
device has an opportunity to acknowledge the packets.
XACs that subscribe to modulo 128 sequencing also support modulo 8 sequencing.
The virtual circuit, rather than the interface, determines the type of sequencing to
use.
Virtual circuits and logical channels

An X.25 call is referred to as a virtual call because no dedicated physical connection
exists between the calling and called DTEs. Virtual circuits and logical channels are
the means by which virtual calls are made possible. On the X.25 links, multiple calls
can be established over a single physical circuit. Within the network, data packets
may be transmitted over different physical paths, even though there is a single
virtual connection between two or more nodes.
To allow multiple simultaneous virtual calls to share a single physical X.25 link, the
link is divided into LCs that are assigned identifiers, or LCNs. An LC is the local
connection path between the DTE and the DCE. LCNs allow multiple calls to be
statistically multiplexed on a single physical circuit. LCNs are assigned according to
the functionality the LC performs. You can designate LCs for two-way calling, for
incoming calls only, or for outgoing calls only.
A virtual circuit is a logical connection between two endpoints on a network; there
is no dedicated physical connection between the endpoints. In fact, virtual circuits
normally span multiple physical circuits. Virtual circuits can be switched (SVC) or
permanent (PVC).
SVCs are temporary, bidirectional communication paths between DTEs. SVCs are
established as needed and exist only for the duration of the call. PVCs are dedicated,
bidirectional fixed paths between endpoints; PVCs are provisioned by the network
operator, and remain established regardless of data transfer activity. In an X.25
network, a PVC is the equivalent of a leased line.
The network establishes an SVC by associating the logical channels used at each end
of the connection. Figure 27.14-2 shows the relationship between logical channels
and virtual circuits. RTP virtual connections, which are the logical links between
source and destination switches, are discussed in chapter 27.1.
27.14-8
(400)
X.25 Serivce

NNP 95-2035-01-00-B

Figure 27.14-2: Logical Channels and Virtual Circuits

Virtual circuit
Virtual connection
Logical channel
Logical channel
X.25
network
DCE
DCE
DTE
DTE
7299
During the call setup phase, the calling DTE selects the logical channel on its X.25
link when it sends a Call Request. The destination DCE selects a logical channel on
the link to the called DTE, on which it transmits the Incoming Call packet. To
minimize the risk of call collision, the calling DTE always selects the highest
available LCN for a call request, while the destination DCE always selects the lowest
available LCN.
By default, each XAC supports 32 two-way SVC LCs. Outgoing SVC LCs and
incoming SVC LCs can be assigned to provide the One-way Logical Channel
Outgoing and One-way Logical Channel Incoming facilities as defined in X.25.
To change the default logical channel assignment, you must define the total number
of LCs required, the base LCN, and the number of channels required for each LC
type. The switch then allocates LCNs according to the type of LC. The number of
two-way SVC LCs is the difference between the total number of LCs and the number
of PVC LCs, incoming SVC LCs, outgoing SVC LCs. That is:
Two-way SVCs = LCNs (PVCs + SVCsout + SVCsin)
Figure 27.14-3 shows how LCNs are allocated.
X.25 Service
(400)
27.14-9


NNP 95-2035-01-00-B
Figure 27.14-3: LCN Allocation

LCN
Assignments
HOC
Outgoing LCs
LOC
Number
of LCs
(1 to 4095)
HTC
Two-way LCs
SVC LCs
LTC
HIC
Legend
HOC: highest outgoing
channel
LOC: lowest outgoing
channel
HTC: highest two-way
channel
LTC: lowest two-way
channel
HIC: highest incoming
channel
LIC: lowest incoming
channel
Incoming LCs
LIC
PVC LCs
Base LCN
Reserved
7297
Network layer timers

X.25 network layer timers ensure that the DTE-DCE network interfaces are
functioning normally. The triggers that start and stop the timers and the default
values for the timers are listed in Table 27.14-1.
Table 27.14-1: Network Layer Timers
Timer
27.14-10
Start Trigger
Stop Trigger
Default
T10
The DCE issues a Restart

Indication.
The DCE receives a Restart

Confirmation or Request (collision).
180 s
T11
The DCE issues an Incoming Call.
The DCE receives a Call Accept or Call

Clear.
200 s
T12
The DCE issues a Reset

Indication.
The DCE receives a Reset

Confirmation or Request (collision).
180 s
T13
The DCE issues a Clear Indication.
The DCE receives a Clear Confirmation

or Request (collision).
180 s
T20
The DTE issues a Restart

Request.
The DTE receives a Restart

Confirmation or Indication (collision).
180 s
T21
The DTE issues a Call Request.
The DTE receives a Call Connect or

Call Clear.
200 s
(400)
X.25 Serivce

NNP 95-2035-01-00-B
Timer

Start Trigger
Stop Trigger
Default
T22
The DTE issues a Reset Request.
The DTE receives a Reset

Confirmation or Indication (collision).
180 s
T23
The DTE issues a Clear Request.
The DTE receives a Clear Confirmation

or Indication (collision).
180 s
T24
The DTE receives a data packet

and the timer is not already
running; or, the DCE receives a
data packet, the timer is not
already running, and the window is
not half full.
The DTE transmits an RR or RNR; or,

the DCE transmits an RR, RNR, or data
packet with a piggybacked P(R).
60 s
Inactivity
The transmit queue is full and the

window closes.
The transmit window opens.
0s
Flow
Control
A complete data packet is received

from the link and the buffers are
below the upper threshold.
A complete data packet is received

from the link and the buffers are greater
than or equal to the upper threshold.
1s
Negotiation facilities
Flow Control and Throughput Class Negotiation facilities are assigned to XACs to
permit the calling and called DTEs and the calling and called DCEs to negotiate the
packet size, window size, and throughput class to be used for each virtual call.
Negotiation occurs during the call setup phase and applies to both directions of data
transmission.
Flow control allows the data receiver to limit the rate at which it accepts data by
restricting the number of unacknowledged packets (window size) and the
maximum size of the packets on a virtual call basis. The throughput class, or rate at
which data is transmitted (in b/s), is similarly negotiable on a virtual call basis.
Negotiation occurs at the three functional interfaces in the call request path: local
DCE, remote DCE, and remote DTE. When a DTE issues a Call Request packet with
a negotiation facility, each functional interface can:
agree to the facilities or options signalled in the Call Request packet

negotiate the parameters down to a level that is supported
clear the call if negotiation is not permitted or is unsuccessful
Addressing options
Addressing options include subaddressing and address suppression.
Subaddressing
The Maximum Address Length parameter is used to specify the maximum address
length permitted after translation. This allows the network administrator to control
the number of subaddress digits used by a subscriber.
X.25 Service
(400)
27.14-11


NNP 95-2035-01-00-B
For the following address types, the address length after translation must be less
than or equal to the Maximum Address Length parameter:
the called address contained in the call setup and clearing packets to the DTE
the calling address contained in call setup and clearing packets from the DTE
The difference between the Maximum Address Length and the length of the address
assigned to the DTE is the number of subaddress digits allowed.
Address suppression
The calling and called addresses can be optionally suppressed on a per-XAC basis to
meet compatibility requirements of specific DTEs and networks.
Maximum packet size

The 36120 MainStreet X.25 switch supports nine discrete packet sizes. The highest
allowable packet size assigned to the XAC determines the value of the Maximum
Information Frame Size (N1) parameter.
When you provision X.25 access lines that access the X.25 switch through
encapsulation circuits on the FRS card, you must ensure that the highest value set for
the Allowable Packet Sizes parameter is compatible with the Encapsulated Protocol
Maximum Frame Size parameter on the encapsulation circuit.
To ensure packet and frame size compatibility

1.
Set the Allowable Packet Sizes parameter for the XAC interface, and note the
maximum packet size:
CONFIG X25_ACCESS XAC <xac> NET_LAYER MORE PACKETS
ADD <pkt_size>
2.
If the X.25 device is accessing the switch through a frame relay encapsulation
circuit, determine which FRS card and circuit number support the device.
3.
Log on to the FRS NMTI.
4.
Check the value of the Encapsulated Protocol Maximum Frame Size parameter
for the encapsulation circuit:
5.
27.14-12
Ensure that the Encapsulated Protocol Maximum Frame Size parameter for the
encapsulation circuit is equal to or greater than the highest allowable packet
size value for the XAC interface.
(400)
X.25 Serivce

NNP 95-2035-01-00-B
27.14.7

Viewing Network Layer Parameters

Figure 27.14-4 shows the NMTI display for the network layer parameters.
Figure 27.14-4: Network Layer Parameters Display
X25FRE Stations:nn
PA11-H1-00
Toronto:A
Alarms:1
11-May-1997
8:35a
NETWORK LAYER
--------------:X.25
:DCE
:1984/1988
:8
Service Type
Version

Window Timer (T24)
Inactivity Timer
Flow Control Timer
:180 s
:200 s
:180 s
:180 s
:60 s
:0 s
:1 s
Base LCN
Number of LCNs
Number of PVCs
(Two Way SVCs)
:1
:32
:0
:0
:32
:0
CONFIG X25_ACCESS XAC 112 NET_LAYER

F1-SERVICE
F2-INTF_TYPE
F6-ADDRESSING F7-MORE
F3-SEQ_NUMBER
F8-CANCEL
F4-LCN_ALLOC
F9-QUIT
F5-TIMERS
F10-
To view network layer parameters

CONFIG X25_ACCESS XAC <xac> NET_LAYER
27.14.8
Configuring Network Layer Parameters

This section describes the network layer parameters that can be configured for each
XAC. The parameters are ordered as they appear on the NMTI display.
Note
For most X.25 access lines, the network layer default values are acceptable.
However, ensure that the following parameters are set correctly.
The Packet Layer Interface Type parameter must be set to DCE on one end of the
X.25 Service
link and DTE on the other end.

LCN allocations must correspond between the DTE and DCE. The range of LCNs
allocated to the DTE must be a subset of the range of LCNs allocated to the DCE.
(400)
27.14-13


NNP 95-2035-01-00-B
Service Type
This parameter specifies the type of service supported by the X.25 access line. Select
AGENT to specify the service type as one of the following internal DTE agents: NUI,
accounting, or traffic generator.
Only one XAC per switch can be configured as a NUI agent, accounting agent, or
traffic generator. XACs that are configured for these service types can be assigned
only one NUA; multi-NUA support does not apply to NUI agents, accounting
agents, or traffic generators.
You cannot change the service type if the XAC is connected to a direct circuit or
frame stream-DLCI. Disconnect the XAC first.
Options
X.25, X.25 Gateway, NUI Agent, Accounting Agent, Traffic Generator, or XFR.
Default
X.25

This parameter specifies the type of network layer interface supported by the switch
on this XAC.
This parameter must be set to DCE on one end of the link and DTE on the other end.
Either end can be set to DTE or DCE, as long as the two ends are different.
The packet layer interface type does not have to match the link layer interface type,
although these parameters normally match.
Options
DTE or DCE
Default
DCE
X.25 Version
This parameter specifies the version of X.25 protocol supported by the DTE. The
length of the facility field is greater in the 1992 version.
Options
1984/1988 or 1992
27.14-14
(400)
X.25 Serivce

NNP 95-2035-01-00-B

Default
1984/1988

This parameter specifies the packet modulo used to control packet sequence
numbers for the link. Enter 8 for modulo 8 operation (normal), or 128 for modulo 128
operation (extended). XACs assigned modulo 128 also support modulo 8. The
virtual circuit, rather than the interface, determines the type of sequencing to use. A
call is cleared if the called and calling DTEs are incompatible and it is a D-bit call.
The Packet Sequence Numbering value configured for an XAC must be greater than
the Default Send Window Size and Default Receive Window Size values for NUAs
and PVCs associated with the XAC. For example, if an XAC uses modulo 8
sequencing, then any NUA assigned to that XAC is restricted to default send and
receive window sizes of 1 to 7.
For an active XAC, you cannot change the value from 128 to 8 if NUAs or PVCs
associated with the XAC have default send and receive window size values of
greater than 7.
Options
8 or 128
Default
8
Base LCN
This parameter specifies the LCN of the first logical channel supported on the
interface.
Range
1 to 4095
1 for XFR service interworking
Default
1
Number of LCNs
This parameter specifies the total number of logical channels supported on the
interface. This value must be greater than or equal to the number of PVCs + the
number of incoming SVCs + the number of outgoing SVCs.
X.25 Service
(400)
27.14-15


NNP 95-2035-01-00-B
Range
1 to 4095
Default
32
Number of PVCs
This parameter specifies the number of logical channels on the interface that support
PVCs. The number of PVCs + the number of incoming SVCs + the number of
outgoing SVCs must be less than or equal to the number of LCNs.
Range
0 to 4095
0 to 1 for XFR service interworking
Default
0

outgoing SVCs. The number of outgoing SVCs + the number of incoming SVCs + the
number of PVCs must be less than or equal to the number of LCNs.
Outgoing SVCs can be assigned to provide the One-way Logical Channel Outgoing
facility as defined in Recommendation X.25.
Range
0 to 4095
Default
0
27.14-16
(400)
X.25 Serivce

NNP 95-2035-01-00-B

Two-way SVCs
both incoming and outgoing SVCs. This parameter is not directly configurable; the
value is determined as follows:
n = LCNs (PVCs + SVCsout + SVCsin)
where
n = Number of Two-way SVCs
LCNs = Number of LCNs
PVCs = Number of PVCs
SVCsout = Number of Outgoing SVCs
SVCsin = Number of Incoming SVCs
Range
1 to 4095
0 to 1 for XFR
Default
32

incoming SVCs. The number of incoming SVCs + the number of outgoing SVCs +
the number of PVCs must be less than or equal to the number of LCNs.
Incoming SVCs can be assigned to provide the One-way Logical Channel Incoming
facility as defined in Recommendation X.25.
Range
1 to 4095
Default
0
X.25 Service
(400)
27.14-17


NNP 95-2035-01-00-B

This parameter specifies the maximum time to wait for a response to a Restart
Indication packet, if the interface is DCE, or a Restart Request packet, if the interface
type is DTE. Enter 0 to disable this timer.
Range
0 to 630 seconds
Default
180 seconds

This parameter specifies the maximum time to wait for a response to an Incoming
Call packet, if the interface type is DCE, or a Call Request packet, if the interface type
is DTE. Enter 0 to disable this timer.
Range
0 to 630 seconds
Default
200 seconds

This parameter specifies the maximum time to wait for a response to a Reset
Indication packet, if the interface type is DCE, or a Reset Request packet if the
interface type is DTE. Enter 0 to disable this timer.
Range
0 to 630 seconds
Default
180 seconds

This parameter specifies the maximum time to wait for a response to a Clear
Indication packet, if the interface type is DCE, or a Clear Request packet, if the
interface type is DTE. Enter 0 to disable this timer.
27.14-18
(400)
X.25 Serivce

NNP 95-2035-01-00-B

Range
0 to 630 seconds
Default
180 seconds
Window Timer (T24)

This parameter controls the sending of acknowledgments to the DTE. The timer
allows the switch to send an RR frame for every half window of packets received,
rather than for every packet received. When the switch receives half a window of
packets, it transmits an RR, otherwise the T24 timer starts and the RR is sent only
when the timer expires, unless flow control conditions apply.
The timer stops when the switch transmits a data packet with a piggybacked P(R).
During flow control conditions, the switch stops piggybacking in order to try to
close the packet window; data packets are transmitted with the last P(R), not the
current P(R).
Range
0 to 630 seconds
Default
60 seconds
Inactivity Timer
The network layer inactivity timer starts when the transmit queue is full and stops
when the transmit window opens. When the timer expires, the virtual circuit is reset,
thereby preventing deadlock on the virtual circuit. The default (0) disables this
timer.
Range
0 to 630 seconds
Default
0 seconds
X.25 Service
(400)
27.14-19


NNP 95-2035-01-00-B
Flow Control Timer

The flow control timer is used when the switch enters the flow control state. This
occurs if:
memory resources drop below a preset lower threshold

the transmit queue size is greater than 2 and one of the following conditions is
met:
the packet window is closed

a packet layer RNR is received
the link layer is in the flow control state
The flow control timer starts when a complete data packet is received from the access
line and the switch is in flow control state. The switch responds by withholding RRs,
and piggybacking the previous P(R) rather than the current P(R). Under flow control
conditions, the switch avoids sending RNRs whenever possible. The switch send
RNRs only if the transmit queue exceeds n, where n is based on the configured
throughput class values.
When the timer expires, the switch checks the available resources. If the buffers are
above the upper threshold, the switch sends an RR if an RNR was not received from
the other end of the access line, and exits flow control. If the buffers are still below
the upper threshold when the timer expires, the switch restarts the timer.
Range
1 to 180 seconds
Default
1 second
Incoming Maximum Address Length Allowed

This parameter specifies the maximum number of address digits allowed in call
setup and clearing packets sent to the link. The parameter is used to control the
number of subaddress digits used by a subscriber. The difference between the value
of this parameter and the length of the address assigned to the DTE is the number of
subaddress digits:
n = <max_length> <NUA_length>
where
n = number of subaddress digits permitted
max_length = Incoming Maximum Address Length Allowed
NUA_length = length of configured NUA
27.14-20
(400)
X.25 Serivce

NNP 95-2035-01-00-B

Range
1 to 19 digits
Default
19 digits

This parameter specifies whether the called address appears in certain call setup and
clearing packets. The default (No) allows insertion of the called address in the
Incoming Call, Call Connected, and Clear Indication packets for DCE interfaces, and
the Call Accepted and Clear Request packets for DTE interfaces.
Select Yes to suppress the called address in these packets. When this parameter is set
to Yes, the Signal CLAMN parameter for the corresponding NUA should be set to
No.
The called address is always present in the Call Request packet regardless of the
value of this parameter.
Options
Yes or No
Default
No

This parameter specifies whether the calling address appears in call setup packets.
The default (No) allows insertion of the calling address in the Incoming Call and Call
Connected packets for DCE interfaces, and the Call Request and Call Accepted
packets for DTE interfaces. Select Yes to suppress the calling address.
Options
Yes or No
Default
No
X.25 Service
(400)
27.14-21


NNP 95-2035-01-00-B

This parameter specifies whether the switch validates addresses in call setup and
clearing packets. Validation means that the switch ensures that the signalled address
matches either one of the addresses assigned to the XAC, or the address originally
signalled from the switch. Validation applies to the calling address in Call Request
packets, and both the calling and called addresses in Call Accepted and call clearing
packets. Validation occurs after the addresses are translated.
When this parameter is set to Yes, the switch validates addresses as follows.
The switch checks the calling address in Call Request packets against the list of
NUAs configured for the XAC. A match indicates a valid calling address. If there
is no match, and this parameter is set to Yes for the default NUA, the call is
cleared.
In Call Accepted packets, the switch validates the complete calling address.
In Call Accepted packets without the CLAMN facility, the switch validates the
complete called address.
In Call Accepted packets with the CLAMN facility present, the switch validates
the called address, but the subaddress digits of the called address may be
modified. Subaddress digits can differ only when the CLAMN facility is present.
In call clearing packets, the switch validates the called address when the CLAMN
facility is present. Only the subaddresses digits may be modified, otherwise the
call is cleared.
In call clearing packets, when the called DTE inserts the calling address (cases
where the CLAMN facility is present), the switch validates the calling address
even though the address is not passed to the calling DTE.
When this parameter is set to No, the switch handles addresses as follows.
If present in call setup packets, both the calling and called addresses are passed
transparently.
In call clearing packets, the called address is passed transparently if the CLAMN
facility is present. The calling address is forced to 0.
Disabling validation has the effect of allowing any calling address to be accepted as
valid. Generally, this parameter should be set to No only for interfaces that function
as internetwork X.25 gateways.
Options
Yes or No
Default
Yes
Default NPI
This parameter specifies the default NPI to use if the DTE does not subscribe to the
TOA/NPI Address Format option.
27.14-22
(400)
X.25 Serivce

NNP 95-2035-01-00-B

Options
X.121, E.164 digital, or E.164 analog
Default
X.121


This parameter specifies the packet sizes supported by the interface. The maximum
packet size determines the value of the LAPB Maximum Frame Length (N1)
parameter.
The allowable packet sizes configured for an XAC must include the Default Send
Packet Size and Default Receive Packet Size values for NUAs and PVCs associated
with the XAC. For example, if an XAC uses the default allowable packet sizes (128,
256, and 512), then any NUA assigned to that XAC is restricted to default send and
receive packet sizes of 128, 256, and 512.
For an active XAC, you cannot remove allowable packet sizes that are used by NUAs
or PVCs associated with the XAC.
Options
16, 32, 64, 128, 256, 512, 1024, 2048, and 4096 bytes
Default
128, 256, and 512 bytes

This parameter specifies whether the DTE subscribes to the Flow Control
Negotiation facility. Select Yes to permit the DTE to negotiate the flow control
parameters (packet and window sizes) on a per call basis at the DTE/DCE interface
for both directions of transmission. Otherwise, the default packet sizes and default
window sizes are used.
Options
Yes or No
Default
No
X.25 Service
(400)
27.14-23


NNP 95-2035-01-00-B

This parameter specifies whether the DTE subscribes to the Throughput Class
Negotiation facility. Select Yes to permit the DTE to negotiate the throughput classes
(in b/s) on a per call basis for both directions of transmission. Otherwise, the default
throughput classes are used.
When a DTE inserts the Throughput Class Negotiation facility, the proposed values
must be less than the default throughput class values configured for the associated
NUA or PVC (see chapter 27.17).
Options
Yes or No
Default
No

This parameter specifies the format of the Throughput Class Negotiation facility
signalled in both directions at the DTE/DCE interface. Enter Extended to permit the
DTE to explicitly negotiate throughput class values higher than 192 000 b/s.
Options
Basic or Extended
Default
Basic

This parameter applies only if the packet layer interface type is DTE. The default
(No) specifies that only an all-zero cause code is generated. When this parameter is
set to Yes, bit 8 of the cause code is set to 1 for non-zero clear cause codes in clear and
reset packets sent to the DCE link. Bit 8 is not set to 1 when the clear code is zero.
Options
Yes or No
Default
No
27.14-24
(400)
X.25 Serivce

NNP 95-2035-01-00-B

Enhanced Diagnostics Codes

This parameter specifies whether the switch generates enhanced diagnostic codes or
the standard diagnostic codes for the XAC. The enhanced diagnostic codes are
proprietary codes that describe the reasons for clear or reset requests in more detail.
Newbridge recommends that this parameter be set to Yes to improve problem
diagnostics.
Options
Yes or No
Default
Yes
Generate Alarms
This parameter specifies whether the switch generates alarms for this XAC to
indicate that the link layer or network layer is down.
Options
Yes or No
Default
No

Observe the following restrictions and interdependencies when configuring
Service Type
Only one XAC per switch can be configured as a NUI agent, accounting agent, or
traffic generator. Multi-NUA support does not apply to NUI server agents,
accounting agents, or traffic generators.
frame stream-DLCI.
LCNs
If an XAC supports PVCs, you cannot change the Base LCN or Number of PVCs
parameters such that the PVC LCNs are removed.
X.25 Service
(400)
27.14-25


NNP 95-2035-01-00-B

The maximum value for the Allowable Packet Sizes parameter must be equal to or
less than the value of the Maximum X.25 Packet Size configured for the
ENCAP_CCT, if an encapsulated circuit is used for link access.
The allowable packet sizes configured for an XAC must include the Default Send
Packet Size and Default Receive Packet Size values for NUAs and PVCs associated
with the XAC. For an active XAC, you cannot remove allowable packet sizes that are
used by NUAs or PVCs associated with the XAC.
The Packet Sequence Numbering value configured for an XAC must be greater than
the Default Send Window Size and Default Receive Window Size values for NUAs
and PVCs associated with the XAC. For an active XAC, you cannot change the value
from 128 to 8 if NUAs or PVCs associated with the XAC have default send or receive
window size values of greater than 7.

Before you can change the Service Type parameter, you must disconnect the XAC
from the direct circuit or frame stream-DLCI.
When you change the following network layer parameters for an active XAC, the
switch automatically disables and immediately re-enables the XAC to activate the
change. The switch clears all calls on the access line and restarts the link. The changes
are effective once the link restarts.
27.14-26

Base LCN
Number of LCNs
Number of PVCs
Number of Two-way SVCs
(400)
X.25 Serivce

NNP 95-2035-01-00-B

You can change the following network layer parameters at any time with no
disruption of service. The changes are effective for the next call.

X.25 Version
Default NPI
X.25 Service

Inactivity Timer
Flow Control Timer
Window Timer (T24)
Enhanced Diagnostic Codes
Generate Alarms
(400)
27.14-27


NNP 95-2035-01-00-B
To configure network layer parameters

SERVICE
SEQ_NUMBER LCN_ALLOC
INTF_TYPE
TIMERS
ADDRESSING
MORE
<seq_number>
DTE/DCE
VERSION
<version>
X25
X25_GATEW
NUI
AGENT
ACCOUNTING
BASE_LCN
NUM_LCN
TRAFFC_GEN
NUM_PVC
NUM_O_SVC
NUM_I_SVC
<number>
T10T20RST
T11T21CALL
T12T22RES
T13T23CLR
T24WIN
INACTIVITY
MORE
FLOW_CNTL
<seconds>
MAX_LENGTH
SUPRESS_CD SUPRESS_CG
LOCAL_VAL
DEF_NPI
<max_length>
YES/NO
TRANSLATE
(see address
translation section)
PACKETS
ADD
E164_ANA
NEGOTIATE
E164_DIG
CAUSE_CODE
DTE_CAUSE
REMOVE
X121
ALARMS
DIAGNOSTIC
<pkt_size>
YES/NO
FLOW_CNTL
THRU_PUT
TPUT_FORMT
BASIC/EXTENDED
YES/NO
SK000422
27.14-28
(400)
X.25 Serivce

NNP 95-2035-01-00-B

where
xac is a valid XAC
version is the version of X.25 protocol (1984/1988* or 1992)
seq_number is 8* for modulo 8 (normal) or 128 for modulo 128 (extended) operation
number is 1 to 4095, 10* for NUM_LCN
seconds is 1 to 180 for the flow control timer (1*), and 1 to 630 for all other timers
max_length is 1 to 19* digits
pkt_size is one or more of the values 16, 32, 64, 128, 256, 512*, 1024, 2048, or 4096
27.14.9
Understanding Address Translation and Screening

Parameters
Address translation is the process of modifying address digits to facilitate screening
and call routing. Screening is the process of determining the route or treatment of a
call based on pre-defined attributes. The output of address translation is the input to
the screening and call routing processes.
This section describes the address translation and screening parameters, explains the
translation process, and describes how to configure the address translation table. See
chapter 27.7 for information about entering call routing data for the switch.
How addressing works in a 36120 MainStreet X.25 network

MainStreet X.25 supports addressing according to the ITU-T X.121 and E.164
numbering plans. X.121 or E.164 addresses are assigned to every entity to which calls
can be routed. This includes XACs, hunt groups, and the NUI, accounting, and
traffic generator agents. Generally, each address is unique in the network.
In a 36120 MainStreet X.25 network, the X.121 and E.164 addresses and their
associated call subscription options are referred to as NUAs. An active XAC has one
or more NUAs assigned to it. Since call subscription options are associated with the
address rather than the XAC, the multi-NUA feature allows a network user to
subscribe to different call subscription options based on the address signalled in the
call setup packets.
Although hunt groups also have X.121 or E.164 addresses, the addresses are not
assigned call subscription options. Instead, the call subscription options of the
hunted NUA are used to validate the call request.
The X.25 switch establishes virtual calls using external and internal address formats.
The external address format refers to the structure of addresses contained in X.25 call
setup and clearing packets traversing an X.25 access line; that is, the addresses
signalled to or from the X.25 access line are in external format. The internal address
format refers to the address structure used to route calls within the network. Figure
27.14-5 illustrates the function of the two address formats.
X.25 Service
(400)
27.14-29


NNP 95-2035-01-00-B
Figure 27.14-5: Internal and External Address Formats
X.25
network
External
address
format
Internal
address
format
DCE
DCE
External
address
format
DTE
DTE
7298
The valid external and internal address formats are listed in Table 27.14-2.
Table 27.14-2: External and Internal Address Formats
External Address Format (Signalled on Link)
Internal Address Format (NPI, Address)
SS
x, DNIC+NTN+SS
NTN
x, DNIC+NTN
NTN+SS
x, DNIC+NTN+SS
DNIC+NTN
x, DNIC+NTN
DNIC+NTN+SS
x, DNIC+NTN+SS
P+DNIC+NTN
x, DNIC+NTN
P+DNIC+NTN+SS
x, DNIC+NTN+SS
SN
e or m, CC+NSN
1+NSN
e or m, CC+NSN
011+CC+NSN
e or m, CC+NSN
Legend:
CC = E.164 country code
DNIC = Data network interface code
e = NPI value designating a digital E.164 address
m = NPI value designating an analog E.164 address
NSN = National significant number (NDC + SN)
NTN = National terminal number
P = International prefix digit. (0 to 9)
SN = Subscriber number (local number, for example, 7 digits in North America)
SS = Subaddress digits
x = NPI value designating an X.121 address
+ indicates that two strings are concatenated
, indicates the separation of the NPI and address fields
Address translation
The purpose of address translation is to convert addresses signalled on X.25 access
lines to a normalized internal address format. This is done by inserting, removing or
modifying address digits. The internal format allows calls to be effectively screened
and routed using compact and manageable tables.
27.14-30
(400)
X.25 Serivce

NNP 95-2035-01-00-B

When addresses are transmitted over X.25 access lines, they are converted between
external and internal address formats. At the switch, incoming external addresses
are converted to a common internal address format used to route calls through the
network. Outgoing internal addresses are converted to an external format
recognized by the device to which the call is being established. The process of
conversion between the two formats is referred to as address translation.
Address translation tables
Each XAC has an address translation table that describes how to process addresses
exchanged on the access line. The table contains a variable number of translation
entries which allow each access line to be configured individually to handle specific
address formats. Figure 27.14-6 shows an example of the address translation table.
Figure 27.14-6: Address Translation Table Display
X25FRE Stations:nn
PA11-H1-00
Toronto:A
Alarms:1
11-May-1997
8:35a
ADDRESS TRANSLATION TABLE

-------------------------
No.
Direction
Which
Addr
Ext
Prefix
Traps
IOCCCA
NUGDLL
T RM
Int
Prefix
-----------------------------------------------------------------------------------1
Both
Both
ix
<-->
ix
CONFIG X25_ACCESS XAC 1 NET_LAYER TRANSLATE "?"

Enter address translation table entry number.
F1-PREVIOUS
F2-NEXT
F3-NEW_ENTRY
F6F7F8-CANCEL
X.25 Service
(400)
F4F9-QUIT
F5F10-
27.14-31


NNP 95-2035-01-00-B
Every entry in the address translation table contains two configurable prefix strings
for address digit translation, the External Prefix and Internal Prefix. The direction of
the call determines whether addresses are modified according to the two prefixes.
The Direction field and the corresponding arrows indicate how translation is
performed on the call setup and clearing packets.
Incoming (-->) refers to calls originating on the access line. These translation
entries apply only when the interface originates a call. The switch translates all
call setup and clearing packets received from and sent to the access line.
Outgoing (<--) refers to calls sent to the access line. These translation entries
apply only when the interface is the destination for a call. The switch translates
call setup and clearing packets sent to and received from the access line, with the
exception of calling addresses received from the access line. The switch never
translates calling addresses received from a destination access line, but rather
inserts the original internal calling address when transmitting call setup or
clearing packets to the originating interface.
Both (<-->) refers to calls that either originate on or are sent to the access line.
These translation entries apply whether the interface originates a call or is the
destination for a call. The switch translates call setup and clearing packets sent to
and received from the access line, with the exception of calling addresses in
packets received from the access line.
When the switch receives call setup or clearing packets from an X.25 access line,
addresses contained in the packets are compared to the External Prefix entries in the
address translation table. If a match occurs, the addresses are translated by replacing
the digits that match the External Prefix string with the corresponding Internal
Prefix digits. Translation is performed from left to right of the table.
When the switch sends call setup or clearing packets to an access line, addresses are
compared to the Internal Prefix entries in the table. On a successful match, the digits
matching the Internal Prefix string are replaced by the corresponding External Prefix
digits. Translation is performed from right to left of the table. In both cases, both the
calling and called addresses can be modified.
Address translation is performed in two stages. The first stage involves a
digit-by-digit comparison of an address contained in a packet against an input
pattern in the address translation table. The input pattern is the Internal or External
prefix, depending on the direction of the packet.
In the second stage, the output pattern is substituted for the portion of the address
(the prefix digits) that matched the input pattern. The parsing process compares
digits starting with the first digit of the address and moves from left to right. The
translation entry matching the most number of digits is selected.
Typically, an XAC with an X.121 address would be configured with external and
internal prefixes as shown in Table 27.14-3. The direction arrows indicate that the
entries are valid for both calls originating on and sent to the access line.
27.14-32
(400)
X.25 Serivce

NNP 95-2035-01-00-B

Table 27.14-3: Typical X.121 Address Translation Example

External
Prefix
Air
Internal
Prefix
Result
no
< >
ix3020
Insert DNIC 3020 in addresses received from the access

line. Remove DNIC 3020 from addresses sent to the
access line.
ix0
< >
ix
Remove the international prefix digit (0) from addresses

received from the access line. Insert the prefix digit in
addresses sent to the access line.
In this example, the null entry (ix) is used to either insert or remove digits. Calls to
addresses specified in national format do not begin with 0 and a match on the first
entry occurs. As a result, the switch inserts or removes the DNIC. International calls
match the second entry, in which case the switch inserts or removes the international
prefix digit.
The entries in the above example execute the following functions:
convert external addresses signalled from the access line to the internal address
format, and convert the internal address format to external address format
define the international prefix of the subscriber to be 0
define the DNIC of the subscriber to be 3020
allow the subscriber to signal addresses in two formats:
in national format, where only the NTN is signalled
in international format, where 0+DNIC+NTN is signalled
The Address Translation Table contains parameters that specify whether the calling
address, called address, or both addresses are translated, and for which direction of
the call. In order to be translated, an address must match one of the prefix strings,
and must also be eligible for translation according to its address type (calling or
called) and call direction (incoming or outgoing). For example, for translation to
occur on a called address in a call setup packet originating from an access line, the
address must match an External Prefix string, the Which_Addr field must be set to
Called or Both, and the Direction field must be set to Incoming or Both.
Table 27.14-4 lists examples of how external addresses are converted to internal
format by the address translation process.
X.25 Service
(400)
27.14-33


NNP 95-2035-01-00-B
Table 27.14-4: Examples of the Address Translation Process

Signalling Method
External Address
Format Signalled on
Link
(before translation)
Address
Translation Table
Entry
Internal Address
Format
(after translation)
XAC configured with an X.121 address (native X.121 format)

Standard
SS
NTN
NTN+SS (1)
DNIC+NTN
DNIC+NTN+SS
P+DNIC+NTN
P+DNIC+NTN+SS
27.14-34
x <--> xDNIC+NTN
x <--> xDNIC
x <--> xDNIC
none required
none required
xP <--> x
xP <--> x
x, DNIC+NTN+SS
x, DNIC+NTN
x, DNIC+NTN+SS
x, DNIC+NTN
x, DNIC+NTN+SS
x, DNIC+NTN
x, DNIC+NTN+SS
Escape to E.164
P+0+CC+NSN (E.164
Digital)
P+9+CC+NSN (E.164
Analog)
xP0 <--> e
xP9 <--> m
e, CC+NSN
m, CC+NSN
Non-standard escape to
ISDN or X.32
P+77+NSN
xP+77 <--> e+CC
e, CC+NSN
(400)
X.25 Serivce

NNP 95-2035-01-00-B
Signalling Method

External Address
Format Signalled on
Link
(before translation)
Address
Translation Table
Entry
Internal Address
Format
(after translation)
XAC configured with an E.164 (digital) address (2)

Standard
SN
1+NSN
011+CC+NSN
e <--> eCC+NDC
e1 <--> eCC
e011 <--> e
e, CC+NSN
e, CC+NSN
e, CC+NSN
Escape to X.121
0+DNIC+NTN
e0 <--> x
x, DNIC+NTN
Non-standard examples
75+NSN
76+CC+NSN
8+NTN (X.121)
e75 <--> eCC

e76 <--> e
e8 <--> xDNIC
e, CC+NSN
e, CC+NSN
x, DNIC+NTN
Notes
1. In this case a length of up to 14 address digits is permitted for the NTN+SS.
2. Up to 12 address digits are permitted. This increases to 15 digits after December 31, 1996.
Wildcard characters
The wildcard character (?) is used in External and Internal Prefix strings to facilitate
digit manipulation. In most cases, the number of wildcard characters in the External
Prefix and Internal Prefix strings must be the same. The one exception allows
wildcard characters to appear only in the Internal Prefix string, but the type of
address must be calling and the direction must be outgoing. This configuration is
typically used for gateway links.
When wildcard characters appear in a translation entry, the switch translates calls
according to the following method: replace the nth wildcard digit in the output
pattern with the packet address digit that is in the same position as the nth wildcard
digit in the input pattern.
Table 27.14-5 shows examples of digit substitution and removal.
X.25 Service
(400)
27.14-35


NNP 95-2035-01-00-B
Table 27.14-5: Address Translation Examples

Translation Entry
External
Prefix
Direction
Internal
Prefix
Result
Address
Type
Input Address
From Link
Resulting
Output
Address
Comments
x1?34
<-->
x1?99
Called
x12345678
x12995678
input digits 34 replaced

by 99
x1?34
-->
x199
Both
x12345678
x1995678
input digit 2 removed,

input digits 34 replaced
by 99
x1?3?5
<-->
x1?3?9
Called
x12345678
x12349678
input digit 5 replaced

by 9
x1?
<-->
x1
Both
x12345678
invalid use of wildcard

characters
x01
<--
x????
Calling
x12345678
translation is not
performed on calling
addresses received
from a destination link
Call screening
The address translation table also contains parameters that permit call screening
options to be set. The call trap function provides a means of clearing a call, raising
an alarm or both when an address in a call setup or clearing packet matches a table
entry. There is one trap parameter for each address type and direction combination:
Trap Incoming Called, Trap Incoming Calling, Trap Outgoing Called, and Trap
Outgoing Calling. The Trap Action parameter specifies the action to take, also called
a treatment.
The trap parameters can be used to assign the Incoming Calls Barred and Outgoing
Calls Barred facilities to access lines, and to provide network security by restricting
calls to and from particular addresses or ranges of addresses.
27.14.10
Viewing Address Translation and Screening Parameters

Figure 27.14-6 shows an example of the address translation table for an XAC.
Figure 27.14-7 shows the NMTI screen for configuring address translation table
entries.
27.14-36
(400)
X.25 Serivce

NNP 95-2035-01-00-B

Figure 27.14-7: Address Translation Entry Display

X25FRE Stations:nn
PA11-H1-00
Toronto:A
Alarms:1
11-May-1997
8:35a
ADDRESS TRANSLATION ENTRY

-------------------------
Entry Number
External Prefix
Internal Prefix
Direction
Which Address
Trap Incoming
Trap Outgoing
Trap Action
:1
:ix
:ix
:Both
:Both
Calling
Calling
Clear Call
:No
:No
:No
Called
Called
Cause Alarm
:No
:No
:No
CONFIG X25_ACCESS XAC 1 NET_LAYER TRANSLATE 1
F1-EXT_PREFIX
F5-SCREENING
F6-DELETE
F2-INT_PREFIX
F3-DIRECTION
F4-WHICH_ADDR
F7-MORE
F8-CANCEL
F9-QUIT
F10-
To view the address translation table

CONFIG X25_ACCESS XAC <xac> NET_LAYER TRANSLATE
SHOW_ALL
To view address translation and screening parameters

CONFIG X25_ACCESS XAC <xac> NET_LAYER TRANSLATE <entry>
where
xac is 1 to 128 for X.25 FRE cards and 1 to 992 for PE cards
entry is 1 to 256
27.14.11
Configuring Address Translation and Screening

Parameters
This section describes the address translation and screening parameters and
provides configuration guidelines. The parameters are ordered as they appear on
the NMTI display.
X.25 Service
(400)
27.14-37


NNP 95-2035-01-00-B
Entry Number
The entry in the address translation table.
Range
1 to 256
Default
None

This parameter specifies the external translation prefix string for this Address
Translation Table entry. When calls match the direction criteria, addresses received
from an X.25 access line are compared to the external translation prefixes in the table.
If a match occurs, the addresses are translated by replacing the digits that match the
external translation prefix string with the corresponding internal translation prefix
digits. Translation is performed from left to right of the table.
Range
for E.164 analog), and 1 to 19 address digits or wildcard characters (?)
Default
ix

This parameter specifies the internal translation prefix string for this Address
Translation Table entry. When calls match the direction criteria, addresses being
sent to an X.25 access line are compared to the internal translation prefixes in the
table. If a match occurs, the addresses are translated by replacing the digits that
match the internal translation prefix string with the corresponding external
translation prefix digits. Translation is performed from left to right of the table.
Options
Default
ix
27.14-38
(400)
X.25 Serivce

NNP 95-2035-01-00-B

Direction
This parameter specifies whether the switch attempts address matching on calls
originated by the access line, sent to the access line, or both. For an address to be
translated according to the table entry, the call direction must match the Direction
parameter, and the address must match a prefix string.
Incoming specifies that the entry applies only to calls originated by the access line.
The switch performs address matching on all call setup and clearing packets sent to
and received from the access line.
Outgoing specifies that the entry applies only to calls sent to the access line. The
switch performs address matching on all call setup and clearing packets sent to the
access line, and on called addresses received from the access line. The switch does
not perform address matching on calling addresses received from the access line.
Both specifies that the entry applies to calls originated by and sent to the access line.
Options
Incoming, Outgoing or Both
Default
Both
Which Address
This parameter specifies whether the switch attempts address matching on the
calling address, called address, or both addresses contained in call setup and
clearing packets. An address must match both the prefix string and the Which
Address parameter in a table entry in order to be translated according to that table
entry.
Called specifies that the entry applies only to called addresses.
Calling specifies that the entry applies only to calling addresses.
Both specifies that the entry applies to both called and calling addresses.
Options
Called, Calling or Both
Default
Both
X.25 Service
(400)
27.14-39


NNP 95-2035-01-00-B

This parameter specifies whether to take screening action when a calling address
received from or sent to an originating access line matches the corresponding
External Translation Prefix string. When this parameter is set to Yes and a match
occurs, the call is trapped and treated according to the action specified by the Trap
Action parameters. The Direction and Which Address parameters affect the
operation of this parameter.
Options
Yes or No
Default
No

This parameter specifies whether to take screening action when a called address
received from or sent to an originating access line matches the corresponding
External Translation Prefix string. When this parameter is set to Yes and a match
occurs, the call is trapped and treated according to the action specified by the Trap
Action parameters. The Direction and Which Address parameters affect the
operation of this parameter.
Options
Yes or No
Default
No

sent to a destination access line matches the corresponding Internal Translation
Prefix string. When this parameter is set to Yes and a match occurs, the call is
trapped and treated according to the action specified by the Trap Action parameters.
The Direction and Which Address parameters affect the operation of this parameter.
Note
Calling addresses received from a destination access line are not translated, and
cannot be trapped.
27.14-40
(400)
X.25 Serivce

NNP 95-2035-01-00-B

Options
Yes or No
Default
No

This parameter specifies whether to take screening action when a called address sent
to or received from a destination access line matches the corresponding Internal
Translation Prefix string. When this parameter is set to Yes and a match occurs, the
call is trapped and treated according to the action specified by the Trap Action
parameters. The Direction and Which Address parameters affect the operation of
this parameter.
Options
Yes or No
Default
No
Trap Action Clear Call

This parameter specifies whether the switch clears the call when a trap occurs. If any
of the screening parameters are set to Yes, either this parameter or the Trap Action
Cause Alarm parameter must be set to Yes. If all the screening parameters are set to
No, this parameter is automatically set to No and cannot be set to Yes.
Options
Yes or No
Default
No
Trap Action Cause Alarm

The current release of 36120 MainStreet X.25 (1.2) does not support trap alarms.

Observe the following restrictions and interdependencies when configuring address
translation and screening parameters.
X.25 Service
(400)
27.14-41


NNP 95-2035-01-00-B
External and internal translation prefixes

An internal prefix cannot appear more than once with the same combination of
Direction and Which Address parameter settings. Because there are four
combinations of the Direction and Which Address parameters, an internal prefix can
appear no more than four times. For example, the following entries are valid, but the
internal prefix ix2624 cannot appear again in the table.
DirecNo. tion
Which
Ext
Int
Addr
Prefix
Prefix
------------------------------------------------------------1
Incoming
Called
ix3022
-->
ix2624
Incoming
Calling
ix3023
-->
ix2624
Outgoing
Called
ix3024
<--
ix2624
Outgoing
Calling
ix3025
<--
ix2624
An external prefix can appear only once for each direction when the address type is
called. For example, the following entries are valid, but the external prefix ix3022
cannot appear again in the table.
DirecNo. tion
Which
Ext
Int
Addr
Prefix
Prefix
------------------------------------------------------------1
Incoming
Called
ix3022
-->
ix5555
Outgoing
Called
ix3022
<--
ix6666
An external prefix cannot appear more than once when the address type is calling
and the direction is incoming, but can appear multiple times when the address type
is calling and the direction is outgoing. This is permitted because the switch never
translates calling address received from destination access lines. For example, all of
the following entries are valid.
DirecNo. tion
Which
Ext
Int
Addr
Prefix
Prefix
-------------------------------------------------------------
27.14-42
Incoming
Calling
ix3022
-->
ix5555
Outgoing
Calling
ix3022
<--
ix6666
Outgoing
Calling
ix3022
<--
ix7777
Outgoing
Calling
ix3022
<--
ix8888
(400)
X.25 Serivce

NNP 95-2035-01-00-B

Use of wildcards
The number of wildcard characters in the External Prefix and Internal Prefix strings
must be the same. The one exception is when the address type is calling and the
direction is outgoing, wildcard digits may appear in the internal prefix only.
Call screening parameters
At least one of the Trap Action parameters must be set to Yes if any of the following
parameters are set to Yes:


You can change the address translation and screening parameters at any time with
no disruption of service. The changes are effective for the next call.
X.25 Service
(400)
27.14-43


NNP 95-2035-01-00-B
To configure address translation and screening parameters

CONFIG X25_ACCESS XAC <xac> NET_LAYER MORE TRANSLATE
<entry_no.>
EXT_PREFIX INT_PREFIX DIRECTION WHICH_ADDR SCREENING

<addr_prefix>
MORE
TRAP_ACTN
<addr_prefix>
INCOMING OUTGOING
NEW_ENTRY
CLEAR_CALL ALARM
BOTH
YES/NO
CALLING
TRP_INC_CD
CALLED
BOTH
TRP_INC_CG
TRP_OUT_CD TRP_OUT_CG
YES/NO
SK000423
where
xac is 1 to 128 for X.25 FRE cards or 1 to 992 for PE cards
entry_no. is an address translation table entry number (1 to 256)
addr_prefix is the translation prefix string (i or n, x, e, or m, and 0 to 19 digits or wildcard characters [?])
27.14.12
Resetting XACs
The reset command allows you to reset an XAC to the default configuration values.
All NUAs assigned to the XAC are deleted, and the XAC maintenance state resets to
enabled.
To reset an XAC
CONFIG X25_ACCESS XAC <xac> RESET
27.14-44
(400)
X.25 Serivce

NNP 95-2035-01-00-B
27.15

NUA Parameters
This chapter describes how to configure NUAs.
27.15.1
Understanding NUAs
An NUA is an X.121 or E.164 address and the call subscription options associated
with that address. You define X.121 addresses in international data number format
(DNIC+NTN), and E.164 addresses in international E.164 number format
(CC+NSN). Both of these formats correspond to the internal address format used in
the address translation table for the XACs. Figure 27.15-1 shows the formats.
Figure 27.15-1: X.121 and E.164 Address Formats
International data number format
DNIC
ZXXX
NTN
Up to 10 digits
DNIC is the data network interface code

NTN is the network terminal number
X is 0 to 9
Z is 2 to 7
International E.164 number format
CC
NSN
+
NDC
SN
CC is the country code

NDC is the national destination code (equivalent to the area code)
NSN is the national significant number
SN is the subscriber number (local number)
7913
Once you define an NUA, you must assign it to an XAC interface; NUAs cannot exist
independently in the database. The first NUA assigned to an XAC is the default
NUA for the access line; the switch uses the parameters of the default NUA when
the DTE does not signal a calling address in call setup packets. If the XAC supports
multiple NUAs, you can change the default NUA at any time simply by identifying
a different NUA as the default.
X.25 Service
(400)
27.15-1

27.15.2

NNP 95-2035-01-00-B
To completely configure an NUA, you must do the following:
1.
Define an X.121 or E.164 address in international format. See section 27.15.4.
2.
Assign the address to an XAC interface. See section 27.15.4.
3.
Configure the call subscription options and facilities for the NUA, including:
standard ITU-T facilities and Newbridge-proprietary options (see
27.15.3
section 27.15.7)
CUG-related parameters, if CUG subscription is required (see
section 27.15.10)
default flow control and throughput class values (see section 27.15.13)
Viewing Basic NUA Parameters

Figure 27.15-2 shows the NMTI display for the basic NUA parameters.
Figure 27.15-2: Basic NUA Parameters Display
X25FRE Stations:nn
PA11-H1-00
Toronto:A
Alarms:1
11-May-1997
8:35a
NUA Subscription Options

-----------------------Network User Address
XAC Service Type
User Defined Data
CONFIG X25_ACCESS NUA x302011888866

F1-X25
F2-X25_GATEW
F3-X75_GATEW
F6F7F8-CANCEL
27.15-2
(400)
:x302011888866 (default)
:--:--:
:No
F4-AGENTS
F9-QUIT
F5F10-
X.25 Serivce

NNP 95-2035-01-00-B

To view basic NUA parameters

CONFIG X25_ACCESS NUA <nua>
where nua is 1 to 19 digits in X.121 or E.164 address format
27.15.4
Configuring Basic NUA Parameters

This section describes the basic NUA parameters and provides configuration

This parameter specifies a valid X.121 or E.164 address that is unique in the network.
Before you can define an NUA, you must ensure that the GAT entries for the switch
contain an address prefix that corresponds to the NUA. See chapter 27.7 for
information about configuring the GAT.
You define NUAs by specifying the NPI and entering the address in international
format.
To define an X.121 address, enter x (optional) and 1 to 19 digits in international
data number format (DNIC+NTN). The first digit of an X.121 address cannot be
0 or 9.
To define a digital E.164 address, enter e and 1 to 19 digits in international E.164
number format (CC+NSN).
To define an analog E.164 address, enter m and 1 to 19 digits in international
E.164 number format (CC+NSN).
Range
Default
None

This parameter specifies the XAC to which the NUA is assigned. The NUA cannot
already be assigned to an XAC.
When you assign an XAC its first NUA, the XAC becomes active; if the XAC is
connected to a frame stream-DLCI or direct circuit, the access line goes in service.
Every NUA-to-XAC assignment appears as an entry in the LAT. The switch consults
the LAT during the call routing process to determine the destination access line.
X.25 Service
(400)
27.15-3


NNP 95-2035-01-00-B
The first NUA assigned to an XAC is the default NUA. See the subsection Default
NUA for more information.
Range
Default
None
User Defined Data

This parameter defines a user-specific identifier, such as a name or a unique
customer code, that is associated with the NUA. The switch includes this identifier
in the accounting records to allow the accounting system to identify the subscriber.
Note
You must assign the NUA to an XAC before you can configure this parameter.
Range
0 to n alphanumeric characters, where n is the value of the accounting parameter,
Optional User Defined Data Length (see section 27.10.4 for information).
Default
None
This parameter specifies whether the switch generates accounting records for all
SVCs associated with this NUA.
The switch-wide accounting parameters Intermediate Record Interval and
Collection Interval determine how often the switch generates accounting records.
Options
Yes or No
Default
No
27.15-4
(400)
X.25 Serivce

NNP 95-2035-01-00-B


This parameter specifies whether the switch generates periodic accounting records
for SVCs associated with this NUA, in addition to the intermediate and end records
that are generated by default. Periodic accounting records provide data security
between the generation of intermediate accounting records. If the switch fails, the
only data lost is that collected since the last periodic interval.
The switch-wide accounting parameter Periodic Record Interval determines how
often the switch generates periodic accounting records.
Options
Yes or No
Default
No
Hot Billing
This parameter specifies whether the switch sets a hot billing flag on accounting
records generated for this NUA. The data collector and billing system provide
expedited processing for records that have the hot billing flag set.
Options
Yes or No
Default
No

basic NUA parameters.
You cannot change an address after the NUA is assigned to an XAC. You must
X.25 Service
delete the NUA, redefine the address, and assign it to the XAC.
NUAs cannot exist in the database unless they are assigned to XACs. You cannot
define a block of NUAs and assign them at a later date.
An NUA cannot be a hunt group address or hunt group redirection address.
(400)
27.15-5


NNP 95-2035-01-00-B

You can change the values of the basic NUA parameters at any time with no
To define basic NUA parameters

CONFIG X25_ACCESS NUA <address>
ASSIGN_TO
USER_DATA
<xac>
<user_string>
ACCOUNTING
ACTIVATE
PERIODIC HOT_BILLING
YES/NO
SK000424
where
address is the NPI and 1 to 19 digits in X.121 or E.164 format
xac is a valid XAC
user_string is 0 to 24 alphanumeric characters
27.15-6
(400)
X.25 Serivce

NNP 95-2035-01-00-B
27.15.5

Understanding NUA Subscription Options

Once an address is defined for the NUA, you can assign it call subscription options.
The NUA subscription options include the following ITU-T-compliant X.25
facilities:
Reverse Charging Acceptance

Local Charging Prevention
Charging Information
Fast Select (restricted or unrestricted)
Fast Select Acceptance
Call Redirection
Call Redirection Notification
Called Line Address Modified Notification
NUI Subscription
Closed User Group and Preferential CUG
CUG with Incoming Access
CUG with Outgoing Access
Incoming Calls Barred within a CUG
Outgoing Calls Barred within a CUG
CUG Selection
CUG with Outgoing Access Selection
Non-standard Default Packet Sizes
Non-standard Default Window Sizes
Default Throughput Classes Assignment
For information about CUGs and CUG-related facilities, see section 27.15.8.
Charging facilities
Charging facilities are used to permit or restrict reverse charging and local charging,
and to allow DTEs to request and receive charging information.
Fast Select and Fast Select Acceptance facilities

The Fast Select facility allows up to 128 octets of user data in X.25 call setup and
clearing packets. DTEs can request the facility on a per call basis.
Fast Select is assigned in restricted mode or unrestricted mode. In restricted mode,
the call request must be immediately cleared so that only the data in the packets
associated with call setup and clearing is exchanged. The unrestricted mode allows
the called party to accept the call request and continue to exchange data packets.
The called party must subscribe to the Fast Select Acceptance facility to receive
incoming fast select calls; otherwise, the call is cleared.
X.25 Service
(400)
27.15-7


NNP 95-2035-01-00-B
Call Redirection facility

The Call Redirection facility permits calls to be routed to an alternate address when
the original called address is either busy or out of service. The alternate address can
reside anywhere in the network. Call Redirection applies only during the call setup
and does not affect established calls. The original destination DTE does not receive
an Incoming Call packet.
Each NUA requiring Call Redirection is configured with a single redirect address to
which calls are re-routed when the destination DTE is unavailable; that is, when all
LCNs to the destination DTE are engaged or when the link is out of service. In either
case, the original destination switch modifies the Call Request packet so that the
original called address is replaced with the redirection address. The modified packet
is then forwarded to the new address. If the alternate DTE is available, the call is sent
to the that DTE. When the alternate DTE subscribes to the CRN facility and the
Suppress Called Address parameter is set to No, the CRN facility is included in the
Incoming Call packet.
If the alternate DTE accepts the call, the Call Accept packet is routed back to the
original destination switch which returns the call to the originating switch. This
route through the network becomes the route used by all subsequent data packets
for the duration of the call or until the trunk topology changes.
Figure 27.15-3 shows an example of call redirection where switch 2 redirects the call
to switch 3 because the access line for DTE B is out of service. Switch 3 routes the call
to DTE C.
Figure 27.15-3: Call Redirection Example
B
Switch
1
Switch
2
Switch
3
7526
The CLAMN facility provides notification when a successful call redirection occurs.
When a calling DTE subscribes to this facility, the originating switch provides the
calling DTE with a Call Connected or Clear Indication packet containing the reason
why the called address in the packet is different from that signalled by the calling
DTE.
27.15-8
(400)
X.25 Serivce

NNP 95-2035-01-00-B

The Call Redirection facility preserves subaddress digits in the called address and
allows for cases where the configured called address and redirection address are
different lengths. The following example describes how addresses are substituted:
Configured destination address: 1222
Configured redirected address: 133
Actual called address: 12225 (5 is a subaddress digit)
Result after redirection: 1335
The Call Redirection facility operates according to the following rules.
The Call Redirection facility does not violate the integrity of the CUG facility. The
27.15.6
switch always checks the CUG subscription options of the originally called DTE,
and allows redirection only if the CUG subscription options would have allowed
the incoming call. When a redirected call reaches the alternate DTE, the CUG
subscription options of that DTE are also checked, and the call is accepted or
cleared based on those options. The switch performs these checks regardless of
whether the originally called DTE and alternate DTE are on the same switch or
different switches.
A call can be redirected only once.
Call redirection indication is included in the accounting record.
Call redirection addresses are configured and displayed in the internal address
format.
Viewing NUA Subscription Options

Each of the following groupings of NUA subscription options has a distinct NMTI
display:
charging facilities
fast select facilities
TOA/NPI options
call redirection and notification facilities
NUI subscription options
Figure 27.15-4 shows the NMTI display for the charging facilities.
X.25 Service
(400)
27.15-9


NNP 95-2035-01-00-B
Figure 27.15-4: Charging Parameters Display

X25FRE Stations:nn
PA11-H1-00
Toronto:A
Alarms:1
11-May-1997
8:35a
NUA SUBSCRIPTION OPTIONS

-----------------------Reverse Charge Acceptance
Local Charging Prevention
:No
:No
:No
:No
CONFIG X25_ACCESS NUA x302011888866 SUBS_OPT CHARGING

F1-REV_ACCEPT
F2-LOC_PRVENT
F3-INFO
F4-INFO_REQ
F6F7F8F9-QUIT/SAVE
F5F10-CONTINUE
To view NUA subscription options

CONFIG X25_ACCESS NUA <address> X25 SUBS_OPT
where address is the NPI and 1 to 19 digits in X.121 or E.164 format
27.15.7
Configuring NUA Subscription Options

This section describes the NUA subscription options and provides configuration
The subscription options associated with CUGs are described in section 27.15.10.

This parameter specifies whether the Reverse Charging Acceptance facility is
enabled for the NUA. This facility authorizes the DCE to transmit to the DTE
incoming calls that request the Reverse Charging facility. The default (No) restricts
the DCE from transmitting such calls to the DTE.
You cannot set this parameter to Yes when Local Charge Prevention is set to Yes.
27.15-10
(400)
X.25 Serivce

NNP 95-2035-01-00-B

Options
Yes or No
Default
No

This parameter specifies whether the Local Charging Prevention facility is enabled
for the NUA. This facility prevents the DCE from establishing virtual calls for which
the DTE must pay. The DCE ensures that incoming calls that request the Reverse
Charging facility are not accepted, and outgoing calls are charged to another party
(for example, a NUI). Accept the default to allow local charging.
You cannot set this parameter to Yes when Reverse Charge Acceptance is set to Yes.
Options
Yes or No
Default
No

This parameter specifies whether the Charging Information facility is enabled for the
NUA. This facility instructs the DCE to send the DTE information about the charge
for a call. The charging information is contained in the Clear Indication or DCE Clear
Confirmation packets, and consists of the call duration and the volume of data sent
and received. Accept the default (No) if the facility is not required.
Options
Yes or No
Default
No

This parameter specifies whether the DTE is allowed to request charging
information on a per-call basis using a facility request in a Call Request or Call
Accepted packet. Accept the default (No) to disallow charging information requests.
X.25 Service
(400)
27.15-11


NNP 95-2035-01-00-B
Options
Yes or No
Default
No
Incoming Fast Select Acceptance

This parameter specifies whether the Incoming Fast Select Acceptance facility is
enabled for the NUA. This facility authorizes the DCE to transmit to the DTE
incoming calls that request the Fast Select facility. The default (No) restricts the DCE
from transmitting incoming calls that request the Fast Select facility.
Options
Yes or No
Default
No
Outgoing Restricted Fast Select Allowed

This parameter specifies whether the DTE can request the Fast Select facility with a
restricted response on a per call basis. This facility allows a DTE to include a call user
data field of up to 128 octets in the Call Request packet for transmission to a called
DTE that subscribes to the Fast Select Acceptance facility. The called DTE must clear
the call, but can include up to 128 bytes of user data in the Clear Request packet.
Accept the default (No) if the facility is not required.
Options
Yes or No
Default
No
Outgoing Unrestricted Fast Select Allowed

This parameter specifies whether the DTE can request the Fast Select facility with an
unrestricted response on a per call basis. This facility allows a calling DTE to include
a call user data field of up to 128 octets in the Call Request packet for transmission
to a DTE that subscribes to the Fast Select Acceptance facility; if the call is connected,
the calling DTE can subsequently transmit a Clear Request packet with a clear user
data field of up to 128 octets.
27.15-12
(400)
X.25 Serivce

NNP 95-2035-01-00-B

The called DTE can respond with a Call Accepted or Clear Request packet
containing a called or clear user data field, respectively, of up to 128 octets. If the call
is connected, the called DTE can subsequently transmit a Clear Request packet with
a clear user data field of up to 128 octets.
The DCE mediates by transmitting the called or clear user data fields in Call
Connected and Clear Indication packets, respectively.
Accept the default (No) if the facility is not required.
Options
Yes or No
Default
No
Default NUA
This parameter specifies whether this NUA is the default NUA for the XAC. When
a subscriber does not specify the calling address in a Call Request packet, the switch
inserts the default NUA as the calling address.
You can only designate one NUA as the default. The first NUA assigned to an XAC
automatically becomes the default NUA. If you subsequently configure another
NUA as the default, the switch automatically changes the configuration of the
previous default NUA so that it is no longer the default.
Options
Yes or Undo
Default
None

This parameter specifies whether the TOA/NPI Address Subscription facility is
enabled for the NUA. When this facility is enabled, the DTE and DCE must transmit
call setup and clearing packets using the TOA/NPI address format. The TOA/NPI
address format accommodates addresses whose length is greater than 15 digits and
contains fields that specify the TOA and NPI.
Options
Yes or No
X.25 Service
(400)
27.15-13


NNP 95-2035-01-00-B
Default
No

This parameter specifies whether the switch clears a call when the calling address
cannot be converted because the DTE does not subscribe to the TOA/NPI address
format and the address is too long. If the calling address is too long and this
parameter is set to No, the calling address is omitted.
Options
Yes or No
Default
No
Redirection Address
This parameter specifies a valid X.121 or E.164 address used for call redirection.
Once you define a redirection address, the Call Redirection facility is enabled and
incoming calls for this NUA are redirected to the alternate address when the NUA
is busy or out of service. If no redirection address is defined, the Call Redirection
facility is disabled and call redirection is never performed.
You define a redirection address by specifying the NPI and entering the address in
international format. See the subsection Network User Address in section 27.15.4
for information about address formats.
The redirection address can be either another NUA or a hunt group address, and can
be on the same switch or a remote switch. An X.121 NUA can have an E.164
redirection address, and an E.164 NUA can have an X.121 redirection address.
Unlike an NUA, the switch does not automatically check the GAT to determine if an
address prefix exists for the redirection address. You must ensure that the GAT
contains an entry that corresponds to the redirection address.
Range
NPI (x, e, or m) and 1 to 19 digits in X.121 or E.164 address format
Default
None
Signal CRN
This parameter specifies whether to signal the Call Redirection Notification facility
when a call is redirected. This facility indicates to the alternate DTE that the call has
been redirected, the reason for the redirection, and the original called DTE address.
27.15-14
(400)
X.25 Serivce

NNP 95-2035-01-00-B

If the Packet Layer Interface Type is DCE, the CRN facility is included in the
Incoming Call packet. If the Packet Layer Interface Type is DTE, the CRN facility is
included in the Call Request packet; this can occur when the calling DTE is a private
X.25 network.
If the Packet Layer Interface Type is DCE and the parameter Suppress Called
Address is set to Yes, CRN is disabled regardless of whether this parameter is set to
Yes or No.
Options
Yes or No
Default
No
Signal CLAMN
This parameter specifies whether to signal the Called Line Address Modification
Notification facility when a call is redirected. This facility indicates to the calling
DTE why the called address is different from the one originally signalled by the
calling DTE.
If the Packet Layer Interface Type is DCE, the CLAMN facility is included in the Call
Connected or Clear Indication packet. If the Packet Layer Interface Type is DTE, the
CLAMN facility is included in the Call Accepted or Clear Request packet.
When the Suppress Called Address parameter is set to Yes for the network layer,
CLAMN is disabled regardless of whether this parameter is set to Yes or No.
Options
Yes or No
Default
No
Call Deflection
This release of MainStreet X.25 does not support call deflection.
NUI Subscription
This parameter specifies whether the NUI Subscription facility is enabled for the
NUA. This facility allows a DTE to include the NUI Selection facility in Call Request
packets. The NUI Selection facility enables the DTE to specify which NUI and
password it is using for a particular call.
X.25 Service
(400)
27.15-15


NNP 95-2035-01-00-B
When this parameter is set to Yes, the calling DTE has the option of signalling the
NUI Selection facility in the Call Request packet, the network does not absolutely
require the facility to be present.
If this parameter is set to No and the calling DTE does signal the NUI Selection
facility, the switch clears the call.
Options
Yes or No
Default
No
NUI Validation Required

This parameter specifies whether the network performs validation of the NUI and
password contained in the Call Request packet from the DTE.
When this parameter is set to Yes and the DTE signals the NUI Selection facility in
the Call Request packet, the switch suspends the call setup process and sends a NUI
validation request in a data packet to the validation server. If the server confirms that
the NUI and password are valid, the switch proceeds to set up the call; if the
Accounting Activation parameter is set to Yes for the NUA, the NUI is placed in the
accounting records. If the NUI and password are invalid, the switch clears the call.
When this parameter is set to No, the switch assumes that validation should be
performed in another network. The switch extracts the NUI and password from the
NUI Selection facility field and inserts them in an internal facility field in the
Incoming Call packet. The switch then forwards the Incoming Call packet to the
remote XAC, which is typically an interface to a gateway link.
Options
Yes or No
Default
Yes
Default NUI Format

This parameter specifies the NUI format used in an Incoming Call packet to the DTE.
The standard format refers to the format defined in Appendix VI of the 1992 version
of Recommendation X.25. You can define a non-standard format using the following
parameters:

Non-standard NUI First Subfield Length
27.15-16
(400)
X.25 Serivce

NNP 95-2035-01-00-B

See Figures 27.9-3 to 27.9-6 for example NUI formats.

Options
Standard or Non Standard
Default
Non Standard

This parameter specifies the coding method of the NUI and password.
Options
IA5 (ASCII) or BCD
Default
IA5

This parameter specifies whether the NUI or password field occurs first.
Options
NUI or Password
Default
NUI
Non-standard NUI First Subfield Length

This parameter specifies the number of characters in the first subfield.
Range
1 to 21
Default
6
X.25 Service
(400)
27.15-17


NNP 95-2035-01-00-B

Observe the following restrictions and interdependencies when configuring NUA
subscription options.
Set the Signal CLAMN parameter to No when the network layer parameter
Suppress Called Address is set to Yes.
The Call Redirection facility does not violate the integrity of the CUG facility.
You can change the values of NUA subscription option parameters at any time with
no disruption of service. The changes are effective for the next call.
27.15-18
(400)
X.25 Serivce

NNP 95-2035-01-00-B

To configure NUA subscription options

CONFIG X25_ACCESS NUA <address> SUBS_OPT
CHARGING
FAST_SEL
CUG
CUG_OPT ADDRESSING
REDIRECTN
MORE
NUI
(see CUG section)
DEFLT_NUA TOA_NPI
CL_ON_FAIL
YES
YES/NO
RED_ADR
DELETE_RED
SIG_CRN
SIG_CLAMN DEFLECTION
<crd_address>
YES/NO
INC_ACCEPT
RESTRICT
UNRESTRICT
YES/NO
SUBSCRIPTN
DEF_FORMAT
VALIDATN
NON_STANDD
STANDARD/NON_STANDD
YES/NO
REV_ACCEPT
LOC_PRVENT
INFO
CODING
1ST_FIELD
1ST_LENGTH
IA5/BCD
NUI/PASSWORD
<length>
INFO_REQ
YES/NO
SK000425
where
address is a valid X.121 or E.164 address (1 to 19 digits)
crd_address is the address to which a redirected call is sent (1 to 19 digits)
length is 1 to 21 characters
X.25 Service
(400)
27.15-19

27.15.8

NNP 95-2035-01-00-B
Understanding CUGs
A CUG is a specific set of NUAs to, from, or to and from which access is restricted.
CUG-related facilities provide a way to create multiple virtual private networks
within an X.25 network. Different combinations of access restrictions can be used to
control communication between members and non-members.
Each CUG to which an NUA belongs is identified by a CUG index number, which
ranges from 0 to 99. When a CUG member originates a call, the subscriber uses the
index number to signal the destination CUG. At the switch, the index number is
mapped to an interlock code which uniquely identifies the CUG in the network. This
allows different subscribers to use different index numbers to identify the same
CUG.
Figure 27.15-5 shows how different DTEs can use different index numbers to signal
the same CUG. For example, DTE A and DTE C use index number 2 to signal CUG
X, which is identified by interlock code 100, while DTE B uses index number 5 to
signal the same CUG. DTEs D, E, and F use index numbers 99, 1, and 55 respectively
to signal CUG Z. DTEs A and F use index numbers 6 and 42 respectively to signal
CUG Y.
Figure 27.15-5: CUG Example
DTE A
DTE B
Index
I/L Code
I/L Code
Index
2
6
100
200
100
CUG Y
Interlock code 200
Members = DTE A
DTE F
I/L Code
Index
100
CUG X
Interlock code 100
Members = DTE A
DTE B
DTE C
DTE C
DTE D
CUG Z
Interlock code 1234
Members = DTE D
DTE E
DTE F
DTE F
Index
I/L Code
42
55
200
1234
I/L Code
Index
1234
99
DTE E
I/L Code
Index
1234
1
8666
An NUA can belong to a maximum of 20 CUGs. PE cards support up to 4096 CUGs

and up to 1024 configured LCN pages. X.25 FRE cards support a maximum of 640
CUGs and up to 128 configured LCN pages.
27.15-20
(400)
X.25 Serivce

NNP 95-2035-01-00-B

MainStreet X.25 supports basic CUG membership and the following CUG-related
facilities and options:
preferential CUG
incoming or outgoing calls barred within a CUG
CUG with outgoing access and CUG with incoming access
The basic CUG facility permits members to communicate with each other, but
precludes communication with non-members. Users that subscribe to the basic CUG
facility are implicitly assigned the CUG Selection facility, which permits the calling
DTE to specify the CUG selected for a virtual call.
27.15.9
Viewing CUG Parameters

Figure 27.15-6 shows the NMTI display for configuring CUGs.
Figure 27.15-6: Closed User Group Display
X25FRE Stations:nn
PA11-H1-00
Toronto:A
Alarms:1
11-May-1997
8:35a
NUA SUBSCRIPTION OPTIONS - CLOSED USER GROUPS

--------------------------------------------Index
Interlock Code
Barring
---------------------------------------1
31245
No Barring
CONFIG X25_ACCESS NUA x302011888866 SUBS_OPT CUG 1

F1-INTERLOCK
F6-
X.25 Service
F2-BARRING
F7-
F3-PREF
F8-CANCEL
(400)
F4-DELETE
F9-QUIT
F5F10-PROCEED
27.15-21


NNP 95-2035-01-00-B
To view CUG parameters

CONFIG X25 ACCESS NUA <nua> X25 SUBS_OPT
CUG
CUG_OPT
SK000426
where nua is a valid NUA (1 to 19 digits)
27.15.10
Configuring CUGs
Membership in a CUG is established by associating the NUA with a CUG index, and
configuring the subscription options.
The parameters CUG With Incoming Access, CUG With Outgoing Access, and
Signal Preferential CUG are configured once for each NUA requiring CUG
membership. The other parameters must be configured for every CUG to which an
NUA belongs.
This section describes the CUG parameters and provides configuration guidelines.
The parameters are ordered as they appear on the NMTI display.
CUG Index
This parameter specifies the index number associated with a particular CUG
interlock code. Each CUG to which a NUA belongs is identified by a CUG index
number, which is a number ranging from 0 to 99. The CUG index number is in turn
mapped to an interlock code which uniquely identifies the CUG in the network.
When a CUG member originates a call, the subscriber uses the index number to
signal the destination CUG, rather than the interlock code.
Range
0 to 99
Default
None
Interlock Code
This parameter specifies the network-wide interlock code that uniquely identifies
the CUG.
27.15-22
(400)
X.25 Serivce

NNP 95-2035-01-00-B

Range
0 to 65 535
Default
None
Barring
This parameter specifies the call barring facilities that apply to the NUA within the
CUG. No barring specifies that the DTE can originate calls to, and receive calls from,
other DTEs in this CUG.
Select Incoming Calls Barred to enable the Incoming Calls Barred Within a CUG
facility, which prevents the DTE from receiving incoming calls from other DTEs in
this CUG.
Select Outgoing Calls Barred to enable the Outgoing Calls Barred Within a CUG
facility, which prevents the DTE from originating calls to other DTEs in this CUG.
Options
Incoming Calls Barred, Outgoing Calls Barred, or No Barring
Default
No Barring
Preferential CUG
This parameter specifies whether this CUG is the preferential CUG. The preferential
CUG is used as the default when a specific CUG is not signalled through one of the
selection facilities. When the DTE places a call request, the preferential CUG is
selected automatically if the DTE does not request a particular CUG.
When an NUA belongs to a CUG but does not subscribe to either the CUG with
Incoming Access or CUG with Outgoing Access facility, a preferential CUG must be
assigned.
Options
Yes or No
Default
No
X.25 Service
(400)
27.15-23


NNP 95-2035-01-00-B
CUG with Incoming Access

This parameter specifies whether the CUG with Incoming Access facility is enabled
for the NUA. This facility permits members to:
originate calls to, and receive calls from, other members of the same CUG
receive calls from DTEs that do not belong to any CUG
receive calls from DTEs that belong to other CUGs and subscribe to the CUG with
Outgoing Access facility
When this parameter is set to No, the DTE can communicate only with members of
the same CUG.
Options
Yes or No
Default
No
CUG with Outgoing Access

This parameter specifies whether the CUG with Outgoing Access facility is enabled
for the NUA. This facility permits members to:
originate calls to, and receive calls from, other members of the same CUG
originate calls to DTEs that do not belong to any CUG
originate calls to DTEs that belong to other CUGs and subscribe to the CUG with
Incoming Access facility
Users that subscribe to the CUG with Outgoing Access facility are implicitly
assigned the CUGOA Selection facility, which permits the calling DTE to specify the
CUG selected for a virtual call.
When this parameter is set to No, the DTE can communicate only with members of
the same CUG.
Options
Yes or No
Default
No
Signal Preferential CUG

This parameter specifies whether the DCE inserts the preferential CUG index in the
Incoming Call packet to the X.25 access line.
27.15-24
(400)
X.25 Serivce

NNP 95-2035-01-00-B

Options
Yes or No
Default
No

If an NUA belongs to a CUG but does not subscribe to either the CUG with Incoming
Access facility or CUG with Outgoing Access facility, then the NUA must be
assigned a preferential CUG.

You can change the values of the CUG parameters at any time with no disruption of
service. The changes are effective for the next call.
To configure CUGs
CONFIG X25 ACCESS NUA <address> X25 SUBS_OPT
CUG
CUG_OPT
<index>
INC_ACCESS
OUT_ACCESS
SGNAL_PREF
YES/NO
INTERLOCK
BARRING
<code>
INC_BAR
PREF
DELETE
YES/NO
OUT_BAR
NO_BAR
SK000427
where
address is a valid NUA (1 to 19 digits)
code is the interlock code assigned to the CUG (0 to 65 535)
X.25 Service
(400)
27.15-25


NNP 95-2035-01-00-B
27.15.11 Understanding Flow Control and Throughput Class

Parameters
Flow control parameters specify the packet size (in bytes) and window size (in
number of packets) for each direction of data transmission. Throughput classes,
which specify the rate at which data is transmitted (in b/s), are also defined for each
direction of transmission. These default values are used when Flow Control
Parameter Negotiation and Throughput Class Negotiation facilities are not
requested.
Because throughput class values include only the user data bits and not the protocol
overhead, the maximum achievable throughput is always less than the access line
speed.
27.15.12
Viewing Flow Control and Throughput Class Parameters

Figure 27.15-7 shows the NMTI display for configuring flow control and throughput
class parameters.
Figure 27.15-7: Default Flow Control and Throughput Class Display
X25FRE Stations:nn
PA11-H1-00
Toronto:A
Alarms:1
11-May-1997
8:35a
NUA Subscription Options

--------------------------------Receive
-------
Send
----
Default Packet Sizes
:128
:128
Default Window Sizes
:2
:2
Default Throughput Classes
:64000
:64000
CONFIG X25_ACCESS NUA x302011888866 DEFAULTS

F1-PKT_SIZE
F6-
27.15-26
F2-WIN_SIZE
F7-
F3-THRU_PUT
F8-
(400)
F4F9-QUIT/SAVE
F5F10-CONTINUE
X.25 Serivce

NNP 95-2035-01-00-B

To view flow control and throughput class parameters

CONFIG X25_ACCESS NUA <address> X25 DEFAULTS
where address is a valid NUA (1 to 19 digits)
27.15.13
Configuring Flow Control and Throughput Class

Parameters
This section describes the flow control and throughput class parameters and
provides configuration guidelines. The parameters are ordered as they appear on
the NMTI display.

This parameter specifies the maximum packet size that can be received by the DTE.
This value is used in the absence of the Flow Control Negotiation facility.
The value of this parameter must match one of the allowable packet sizes configured
for the XAC to which the NUA is assigned (see the subsection Allowable Packet
Sizes in section 27.14.8). For example, if the XAC uses the default allowable packet
sizes (128, 256, and 512), then this parameter is restricted to values of 128, 256, or 512.
Range
16, 32, 64, 128, 256, 512, 1024, 2048, or 4096 bytes
Default
128 bytes

This parameter specifies the maximum packet size that can be transmitted by the
DTE. This value is used in the absence of the Flow Control Negotiation facility.
The value of this parameter must match one of the allowable packet sizes configured
for the XAC to which the NUA is assigned (see the subsection Allowable Packet
Sizes in section 27.14.8). For example, if the XAC uses the default allowable packet
sizes (128, 256, and 512), then this parameter is restricted to values of 128, 256, or 512.
Range
16, 32, 64, 128, 256, 512, 1024, 2048, or 4096 bytes
X.25 Service
(400)
27.15-27


NNP 95-2035-01-00-B
Default
128 bytes

This parameter specifies the maximum number of packets that can be transmitted
from the DCE to the DTE before an acknowledgment is returned to the sender. This
value is used in the absence of the Flow Control Parameter Negotiation facility.
The value of this parameter must be less than the Packet Sequence Numbering value
configured for the XAC to which the NUA is assigned (see the subsection Packet
Sequence Numbering in section 27.14.8). For example, if an XAC uses modulo 8
sequencing, then the value of this parameter must be 1 to 7. Enter 1 to 7 if the Packet
Sequence Numbering parameter is set to 8, or 1 to 127 if it is set to 128.
Range
Default
2

This parameter specifies the maximum number of packets that can be transmitted
from the DTE to the DCE before an acknowledgment is returned to the sender. This
value is used in the absence of the Flow Control Parameter Negotiation facility.
configured for the XAC to which the NUA is assigned (see the subsection Packet
Sequence Numbering in section 27.14.8). For example, if an XAC uses modulo 8
sequencing, then the value of this parameter must be 1 to 7. Enter 1 to 7 if the Packet
Sequence Numbering parameter is set to 8, or 1 to 127 if it is set to 128.
Range
Default
2

This parameter specifies the maximum amount of user data, in b/s, that can be
transmitted from the DCE to the DTE. This value is used in the absence of the
Throughput Class Negotiation facility; however, when a DTE inserts the
Throughput Class Negotiation facility, the proposed values must be less than the
default values.
27.15-28
(400)
X.25 Serivce

NNP 95-2035-01-00-B

Values greater than 192 000 b/s are permitted only when the Throughput Class
Negotiation Format parameter is set to Extended.
Options
75, 150, 300, 600, 1200, 2400, 4800, 9600, 19 200, 48 000, 64 000, 128 000, 192 000,
256 000, 320 000, 384 000, 448 000, 512 000, 576 000, 640 000, 704 000, 768 000, 832 000,
896 000, 960 000, 1 024 000, 1 088 000, 1 152 000, 1 216 000, 1 280 000, 1 344 000,
1 408 000, 1 472 000, 1 536 000, 1 600 000, 1 728 000, 1 792 000, 1 856 000, 1 920 000,
1 984 000, 2 048 000 b/s
Default
64 000 b/s

transmitted from the DTE to the DCE. This value is used in the absence of the
Throughput Class Negotiation facility. When a DTE inserts the Throughput Class
Negotiation facility, the proposed values must be less than the default values. Values
greater than 192 000 b/s are permitted only when the Throughput Class Negotiation
Format parameter is set to Extended.
Options
75, 150, 300, 600, 1200, 2400, 4800, 9600, 19 200, 48 000, 64 000, 128 000, 192 000,
256 000, 320 000, 384 000, 448 000, 512 000, 576 000, 640 000, 704 000, 768 000, 832 000,
896 000, 960 000, 1 024 000, 1 088 000, 1 152 000, 1 216 000, 1 280 000, 1 344 000,
1 408 000, 1 472 000, 1 536 000, 1 600 000, 1 728 000, 1 792 000, 1 856 000, 1 920 000,
1 984 000, 2 048 000 b/s
Default
64 000 b/s

Observe the following restrictions and interdependencies when configuring flow
control and throughput class default values.
Default Throughput Class values greater than 192 000 b/s are permitted only
X.25 Service
when the Throughput Class Negotiation Format parameter is set to extended. See
section 27.14.8.
The values of the default send and receive packet size parameters must match
one of the allowable packet sizes configured for the XAC to which the NUA is
assigned.
The values of the default send and receive window size parameters must be less
than the Packet Sequence Numbering value configured for the XAC to which the
NUA is assigned.
(400)
27.15-29


NNP 95-2035-01-00-B

You can change the values of flow control and throughput class parameters at any
time with no disruption of service. The changes are effective for the next call.
To configure flow control and throughput class parameters

CONFIG X25 ACCESS NUA <address> X25 DEFAULTS
PKT_SIZE
RECV
SEND
<pkt_size>
WIN_SIZE
RECV
SEND
<win_size>
THRU_PUT
RECV
SEND
<tput_class>
SK000428
where
address is a valid NUA (1 to 19 digits)
pkt_size specifies the default packet sizes (16, 32, 64, 128*, 256*, 512*, 1024, 2048, or 4096 bytes)
win_size specifies the default window sizes (1 to 127, 7*)
tput_class specifies the default throughput classes (75 to 215 b/s, 64 000*)
27.15-30
(400)
X.25 Serivce

NNP 95-2035-01-00-B
27.16

Copying XAC Configurations

This chapter describes how to copy the values configured for one XAC to one or
more XACs.
27.16.1
Understanding the Copy Capability

The COPY command allows you to copy the values configured for an XAC to one or
more XACs. The XAC from which you copy the values is called the source XAC. The
XAC to which you copy the values is called the target XAC. The source XAC may or
may not be active; that is, it may or may not have an assigned NUA. In either case,
using the copy capability does not affect the status of the source XAC; if it is active,
there is no service disruption.
If the source XAC has an NUA assigned to it, you must enter a new NUA for each
target XAC. The new NUA inherits the same subscription options and parameter
values that were configured for the NUA assigned to the source XAC. As with the
ASSIGN_TO command, when you assign NUAs to XACs using the COPY
command, the target XAC is activated and the access line goes in service.
If the source XAC does not have an NUA assigned to it, you do not assign NUAs to
the target XACs as part of the copy process.
You can also use the COPY command to reconfigure XACs that are already in
service. If a target XAC has an NUA assigned to it, the existing NUA is deleted, and
a new NUA must be assigned. All of the original configured values are overwritten.
27.16.2
Using the Copy Capability

The target XAC can be a single XAC, a set of XACs, or a range of XACs. Table 27.16-1
shows the type of entry and the format for entering the XACs.
Table 27.16-1: Formats for Copying XAC Values
Requirement
X.25 Service
Copy Format
Example
Single XAC
Copy Xnnnn to Xnnnn
X1 TO X3
Set of XACs
Copy Xnnnn to Xaa, Xbb, Xdd,...
X1 TO X2, X3, X8, X11
Range of XACs
Copy Xnnnn to Xnnnn..Xnnnn
X1 TO X7..X15
(400)
27.16-1


NNP 95-2035-01-00-B
Figure 27.16-1 shows an NMTI display in which the configured values for source
XAC 123 are copied to target XACs 124, 127, and 135. Because the source XAC had
an assigned NUA, each of the target XACs must be assigned an NUA.
Figure 27.16-1: COPY Command NMTI Display
X25FRE Stations:nn
PA11-H1-00
Toronto:A
Alarms:1
11-May-1997
8:35a
COPY From X123:

To:
----------------------------------------------------------------------Assigned NUA
XAC
Assigned NUA
X22
---
CONFIG X25_ACCESS COPY X123 TO X22

F1F6-
F2F7-
F3F8-CANCEL
F4F9-QUIT
F5F10-

Observe the following restrictions and interdependencies when using the COPY
command.
If a target XAC has an NUA assigned to it that is a member of a hunt group, the
NUA cannot be deleted. The copy process aborts at this point.
The redirection addresses configured for source XACs are not copied to the target
XACs.
27.16-2
(400)
X.25 Serivce

NNP 95-2035-01-00-B


When you assign NUAs to XACs using the COPY command, the target XAC is
activated and the access line goes in service.
To use the COPY command

CONFIG X25_ACCESS COPY <source_xac> TO <target_xac> <new_nua>
PROCEED
where
source_xac is the XAC from which you want to copy the configuration parameters
target_xac is the XAC to which you want to copy
new_nua is the NUA you want to assign to the newly configured XAC, required only when the source
XAC has an assigned NUA
X.25 Service
(400)
27.16-3

NNP 95-2035-01-00-B
27.17
27.17 X.25 PVCs

X.25 PVCs
This chapter describes how to configure X.25 PVCs.
27.17.1
Understanding X.25 PVCs

An X.25 PVC is a permanently established, end-to-end connection between a logical
channel on one DTE and a logical channel on another DTE. Because the path
between the DTEs is fixed, a PVC is analogous to a leased line in a telephone
network. PVCs are commonly used for DTEs that do not have the signalling
capabilities required for SVCs, and for high-data volume applications to avoid the
usage tariffs associated with SVCs.
PVCs are provisioned by the network operator and require no call setup or clearing
procedures. As soon as both DTEs connect to the network, the PVC becomes active
and the users can transfer X.25 data. Once a PVC is established, it remains
established regardless of data transfer activity; the logical channels are continually
in data transfer state. A PVC cannot be cleared by either of its participating DTEs.
Every PVC has a local end and a remote end. When both ends are supported by the
same switch, the PVC is referred to as a local PVC. When the ends are supported by
different switches, the PVC is called a remotely switched PVC.
How the network establishes PVCs

In the internal network, MainStreet X.25 establishes PVCs using call setup
procedures similar to those used with SVCs. All logical channels in the internal
network are defined as two-way logical channels; these are used by both PVCs and
SVCs. The switches dynamically establish PVCs across the network without the
need for pre-configured PVC LCNs between switches. This is accomplished using an
internal PVC call setup packet, based on the PVC configuration parameters.
As part of the PVC configuration procedure, the network operator specifies which
end of the PVC is the originator. While both ends of the PVC are equally responsible
for its initial establishment, the originating end:
retries the PVC establishment procedure if the first attempt fails

establishes the PVC when call collision occurs between the endpoint switches
generates the accounting records
Either the local or remote end can be designated the originator; however, if you
configure both ends as the originator, the PVC does not go in service.
X.25 Service
(400)
27.17-1
27.17 X.25 PVCs


NNP 95-2035-01-00-B
The following sequence describes how a 36120 MainStreet X.25 network establishes
a PVC for DTEs supported by different switches.
1. When an XAC that supports PVCs goes in service, the switch generates an
internal PVC call setup packet and sends it to the destination switch.
2. Upon receipt of the internal call setup packet, the destination switch determines
if the destination access line is in service.
a. If the destination access line is in service, the switch generates an internal PVC
call accept packet and sends it to the originating switch. The switch also sends a
Reset Indication packet to the destination DTE with reset cause 09h Remote DTE
Operational. Go to number 4.
b. If the destination access line is not in service, the switch generates an internal
clear request and sends it to the originating switch.
3. The switch that supports the PVC originator retries the PVC establishment
procedure three times at 15-second intervals, after which it retries continually at
60 second intervals. This process prevents the originating switch from flooding
the network with call setup packets when the destination access line is out of
service.
4. When the originating switch receives the internal call accept packet, it sends a
Reset Indication packet to the local DTE with reset cause 09h Remote DTE
Operational. The PVC is now established.
In the case of a local PVC, where the same switch serves both DTEs, the switch does
not use call setup packets. However, the network layer follows the same process
described in number 3 if the destination access line is down.
Packet size dependencies

Although packet sizes are configured for each direction of transmission and for each
end of the link, the endpoint DTEs do not have to support the same packet sizes
unless the PVC is configured to support D-bit calls. If the supported packet sizes
differ at the two ends, the switch segments and combines packets internally to allow
packets to be transmitted end to end. This feature also ensures that the largest
allowable packet size is transmitted across DCE links. On D-bit PVCs, the packet
sizes must match.
During configuration, the NMTI checks that the packet sizes set for the PVC are
within the range specified by the Allowable Packet Sizes parameter for the
associated XAC.
Packet sequence numbering

The switch automatically detects the packet sequence numbering to use on a PVC. If
one or both of the configured window sizes for the PVC are greater than 7, modulo
128 is used; otherwise, modulo 8 is used. The window sizes do not have to match at
the two endpoints, unless the PVC is configured to support D-bit calls.
27.17-2
(400)
X.25 Serivce

NNP 95-2035-01-00-B
27.17.2
27.17 X.25 PVCs

Viewing X.25 PVCs

You can view a list of all the PVCs configured on the switch, a group of PVCs, or the
configuration information for a particular PVC.
Viewing all PVCs or a group of PVCs

When you view the list of all PVCs configured on the switch, the switch sorts the
PVCs in ascending numerical order of the address and the LCN. You can specify
whether the switch sorts by local address or remote address.
Figure 27.17-1 shows the NMTI SHOW_ALL display for X.25 PVCs listed by local
address.
Figure 27.17-1: X.25 PVCs SHOW_ALL Display
X25FRE Stations:nn
PA11-H1-00
Toronto:A
Alarms:1
11-May-1997
8:35a
X.25 PVCs
Local Address
Local LCN
Remote Address
Remote LCN
---------------------------------------------------------------------x30220110002
1
x30220330001
1
CONFIG SWITCH X25 PVC "??"

Enter PVC local address. ([npi]nnn...)
F1-PREVIOUS
F2-NEXT
F3-SORT_REMOT
F6F7F8-CANCEL
X.25 Service
(400)
F4F9-QUIT
F5F10-
27.17-3
27.17 X.25 PVCs


NNP 95-2035-01-00-B
To view all PVCs or a group of PVCs

CONFIG SWITCH X25 PVC
SHOW_ALL
<local_nua>
SHOW_GROUP
PREVIOUS
NEXT
SORT_LOCAL/
SORT_REMOT
SK000429
where local_nua is a valid NUA (1 to 19 digits)
Viewing PVC parameters

To view the parameters configured for a particular PVC, you must specify a valid
NUA and LCN. Figure 27.17-2 shows the NMTI display for the X.25 PVC
parameters.
Figure 27.17-2: X.25 PVCs Parameters Display
X25FRE Stations:nn
PA11-H1-00
Toronto:A
Alarms:1
11-May-1997
8:35a
X.25 PVC
--------------------------------------------------------------Local Address
:x3020441201
(Originator)
Local LCN
:4
Remote Address
:x3020457205
Remote LCN
:32
:No
:No
D-Bit Allowed
:No
Send
---:128
:128
:2
:64000
Local Packet Size

Remote Packet Size
Window Size
Throughput Class
Receive
------:128
:128
:2
:64000
CONFIG SWITCH X25 PVC x3020441201 LOCAL_LCN 4
F1-REMOTE_ADR
F6-DELETE
27.17-4
F2-REMOTE_LCN
F7-MORE...
(400)
F3-PKT_SIZE
F8-CANCEL
F4-WIN_SIZE
F9-QUIT
F5-THRU_PUT
F10-
X.25 Serivce

NNP 95-2035-01-00-B
27.17 X.25 PVCs

To view X.25 PVC parameters

CONFIG SWITCH X25 PVC <local_nua> LOCAL_LCN <local_lcn>
where
local_nua is a valid NUA (1 to 19 digits)
local_lcn is a valid PVC LCN
27.17.3
Configuring X.25 PVCs

Before you can configure a PVC, you must ensure that the NUAs exist and the XACs
support PVC LCNs.
To prepare XACs for PVCs

1.
Configure the XAC interface parameters. The following network layer

parameters affect the operation of PVCs.
The Number of PVCs parameter must be set to accommodate the required

number of PVC logical channels.
The Packet Sequence Numbering parameter must be greater than the send
and receive window sizes configured for the PVC.
The send and receive packet sizes configured for the PVC must be in the
range of the Allowable Packet Sizes parameter.

The Throughput Class Negotiation Format parameter must be set to
extended to allow PVCs to use throughput class values greater than 192 000
b/s.
2.
Configure the NUAs.
3.
Assign the NUAs to the XACs.
4.
Configure the PVC parameters.

a.
If both ends of the PVC are on the same switch, configure the parameters
once.
b.
If the local and remote ends are on different switches, configure the
parameters at each switch.
Table 27.17-1 shows an example of the PVC parameters that must agree when the
local and remote ends are on different switches, and the PVC does not support D-bit
packets.
X.25 Service
(400)
27.17-5
27.17 X.25 PVCs


NNP 95-2035-01-00-B
Table 27.17-1: Remotely-Switched PVC Configuration Example

Parameter
Endpoint A
Endpoint B
Local Address
x1111
x2222
Local LCN
10
20
Remote Address
x2222
x1111
Remote LCN
20
10
Originating End
Local
Remote
The following subsections describe the X.25 PVC parameters and provide
configuration guidelines. The parameters are ordered as they appear on the NMTI
display.
Local Address
This parameter specifies the NUA of the DTE that is the local end of the PVC. The
NUA must already be configured on the switch.
Range
NPI plus 1 to 19 digits in X.121 or E.164 address format
Default
None
Local LCN
This parameter specifies the LCN used on the local access line to set up the PVC. This
LCN must be in the range specified by the Number of PVCs parameter at the
network layer of the associated XAC. The LCN cannot already be in use.
When the endpoint DTEs are on different switches, the Local LCN parameter
configured for the local end must match the Remote LCN parameter configured at
the remote end. For example:
endpoint A: Local LCN = 10

endpoint B: Remote LCN = 10
Range
1 to 4095
Default
None
27.17-6
(400)
X.25 Serivce

NNP 95-2035-01-00-B
27.17 X.25 PVCs

Remote Address
This parameter specifies the NUA of the DTE that is the remote end of the PVC. If
the endpoint DTEs are on the same switch, the NUA must already be configured on
the switch.
Range
NPI plus 1 to 19 digits in X.121 or E.164 address format
Default
None
Remote LCN
This parameter specifies the LCN used on the remote access line to set up the PVC.
This LCN must be in the range specified by the Number of PVCs parameter at the
network layer of the remote XAC. The LCN cannot already be in use.
When the endpoint DTEs are on different switches, the Remote LCN parameter
configured for the local end must match the Local LCN parameter configured at the
remote end. For example:
endpoint A: Remote LCN = 12

endpoint B: Local LCN = 12
Range
1 to 4095
Default
None
This parameter specifies whether the switch generates accounting records for the
PVC. The frequency and type of accounting record is determined by the switch-wide
accounting parameters rather than the NUA accounting parameters.
This parameter overrides the Accounting Activation parameter configured for the
NUA.
Range
Yes or No
X.25 Service
(400)
27.17-7
27.17 X.25 PVCs


NNP 95-2035-01-00-B
Default
No

for the PVC. The frequency of the periodic records is determined by the switch-wide
accounting parameters rather than the NUA accounting parameters.
This parameter overrides the Periodic Accounting Activation parameter configured
for the NUA.
Range
Yes or No
Default
No
D-Bit Allowed
This parameter specifies whether the PVC supports D-bit calls. When you set this
parameter to Yes at one or both ends of the PVC, both DTEs can send data packets
with the D-bit set.
Even after a PVC is configured to support D-bit calls, the switch continues to
recognize the significance of the D-bit in the GFI; data packets with the D-bit set are
acknowledged end-to-end after being acknowledged by the receiving DTE.
Range
Yes or No
Default
No
Local Send Packet Size

local DTE over the PVC. This value must be one of the allowable packet sizes
configured for the associated XAC.
If the D-bit Allowed parameter is set to Yes, the packet sizes at the local and remote
ends must match.
This parameter overrides the Default Send Packet Size parameter configured for the
local NUA.
27.17-8
(400)
X.25 Serivce

NNP 95-2035-01-00-B
27.17 X.25 PVCs

Options
16, 32, 64, 128, 256, 512, 1024, 2048, or 4096 bytes
Default
128 bytes
Local Receive Packet Size

This parameter specifies the maximum packet size that can be received by the local
DTE over the PVC. This value must be one of the allowable packet sizes configured
for the associated XAC.
ends must match.
This parameter overrides the Default Receive Packet Size parameter configured for
the local NUA.
Options
16, 32, 64, 128, 256, 512, 1024, 2048, or 4096 bytes
Default
128 bytes
Remote Send Packet Size

remote DTE over the PVC. This value must be one of the allowable packet sizes
ends must match.
the remote NUA.
Options
16, 32, 64, 128, 256, 512, 1024, 2048, or 4096 bytes
Default
128 bytes
X.25 Service
(400)
27.17-9
27.17 X.25 PVCs


NNP 95-2035-01-00-B
Remote Receive Packet Size

This parameter specifies the maximum packet size that can be received by the
remote DTE over the PVC. This value must be one of the allowable packet sizes
ends must match.
the remote NUA.
Options
16, 32, 64, 128, 256, 512, 1024, 2048, or 4096 bytes
Default
128 bytes
Send Window Size

This parameter specifies the maximum number of unacknowledged packets that can
be transmitted from the local DTE to the remote DTE over the PVC. This value must
be less than the Packet Sequence Numbering value configured for the associated
XAC.
If the D-bit Allowed parameter is set to Yes, the window sizes at the local and remote
ends must match.
This parameter overrides the Default Send Window Size parameter configured for
the local NUA.
Range
1 to 7 (if the Packet Sequence Numbering parameter is set to 8) or 1 to 127 (if the
Packet Sequence Numbering parameter is set to 128)
Default
2
Receive Window Size

This parameter specifies the maximum number of unacknowledged packets that can
be transmitted from the remote DTE to the local DTE over the PVC. This value must
be less than the Packet Sequence Numbering value configured for the associated
XAC.
If the D-bit Allowed parameter is set to Yes, the window sizes at the local and remote
ends must match.
27.17-10
(400)
X.25 Serivce

NNP 95-2035-01-00-B
27.17 X.25 PVCs

This parameter overrides the Default Receive Window Size parameter configured
for the local NUA.
Range
1 to 7 (if the Packet Sequence Numbering parameter is set to 8) or 1 to 127 (if the
Packet Sequence Numbering parameter is set to 128)
Default
2
Send Throughput Class

This parameter specifies the maximum rate of user data, in bits per second, that can
be transmitted by the local DTE over the PVC. Values greater than 192 000 b/s are
permitted only when the Throughput Class Negotiation Format parameter for the
associated XAC is set to extended.
This parameter overrides the Default Send Throughput Class parameter configured
for the local NUA.
Options
75, 150, 300, 600, 1200, 2400, 4800, 9600, 19 200, 48 000, 64 000, 128 000, 192 000,
256 000, 320 000, 384 000, 448 000, 512 000, 576 000, 640 000, 704 000, 768 000, 832 000,
896 000, 960 000, 1 024 000, 1 088 000, 1 152 000, 1 216 000, 1 280 000, 1 344 000,
1 408 000, 1 472 000, 1 536 000, 1 600 000, 1 728 000, 1 792 000, 1 856 000, 1 920 000,
1 984 000, 2 048 000 b/s
Default
64 000 b/s
Receive Throughput Class

This parameter specifies the maximum rate of user data, in bits per second, that can
be received by the local DTE over the PVC. Values greater than 192 000 b/s are
permitted only when the Throughput Class Negotiation Format parameter for the
associated XAC is set to extended.
This parameter overrides the Default Receive Throughput Class parameter
configured for the local NUA.
Options
75, 150, 300, 600, 1200, 2400, 4800, 9600, 19 200, 48 000, 64 000, 128 000, 192 000,
256 000, 320 000, 384 000, 448 000, 512 000, 576 000, 640 000, 704 000, 768 000, 832 000,
896 000, 960 000, 1 024 000, 1 088 000, 1 152 000, 1 216 000, 1 280 000, 1 344 000,
1 408 000, 1 472 000, 1 536 000, 1 600 000, 1 728 000, 1 792 000, 1 856 000, 1 920 000,
1 984 000, 2 048 000 b/s
X.25 Service
(400)
27.17-11
27.17 X.25 PVCs


NNP 95-2035-01-00-B
Default
64 000 b/s
Originating End
This parameter specifies which end of the PVC (local or remote) is the originator.
The originator is responsible for retrying the establishment of a PVC, resolving call
collisions, and generating accounting records. If the local and remote DTEs reside on
the same switch, the local address is automatically the originator; the originator is
meaningful only for the purposes of call accounting. If the local and remote DTEs
reside on different switches, then this field must be set differently at each end.
Options
Local or Remote
Default
None

Observe the following restrictions and interdependencies when configuring the X.25
PVC parameters.
Before you configure a local PVC, you must configure both NUAs on the switch.
Although the switch permits you to specify a remote NUA that does not exist on
the switch (to allow for remotely switched PVCs), the switch establishes local
PVCs only if the NUAs exist before the PVC is configured.
The values of the send and receive packet size parameters must match one of the
allowable packet sizes configured for the associated XAC.
Send and receive throughput class values greater than 192 000 b/s are permitted
only when the Throughput Class Negotiation Format parameter for the
associated XAC is set to extended. See section 27.14.8.
The values of the send and receive window size parameters must be less than the
Packet Sequence Numbering value configured for the associated XAC.
If the D-bit Allowed parameter is set to Yes, the packet and window sizes at the
local and remote ends must match.
Call redirection does not apply to PVCs. The call redirection address configured
for an NUA is ignored when a PVC is established.

Once the PVC is established, you cannot change the local or remote addresses or
LCNs. To change an address or LCN, delete and reconfigure the PVC.
You can change any of the other PVC parameters after the PVC is established; the
switch resets and re-establishes the PVC to activate the new values.
27.17-12
(400)
X.25 Serivce

NNP 95-2035-01-00-B
27.17 X.25 PVCs

Note
To optimize switch resources, routinely delete any PVC configurations that are not
required. When the access line is in service, the switch continually attempts to
establish a configured PVC.
To configure the X.25 PVC parameters

REMOTE_ADR
REMOTE_LCN
<remote_nua>
<remote_lcn>
PKT_SIZE
WIN_SIZE
SEND
THRU_PUT
RECV
<win_size>
LOCAL_RCV
LOCAL_SND
SEND
MORE
RECV
<tput>
REMOTE_RCV REMOTE_SND
<pkt_size>
ACCOUNTING
ACTIVATE
PERIODIC
YES/NO
ORIGINATE
DBIT
LOCAL/
REMOTE
YES/NO
SK000430
where
remote_nua is the NPI and 1 to 19 digits
remote_lcn is a valid PVC LCN
pkt_size specifies the default packet sizes (16, 32, 64, 128*, 256*, 512*, 1024, 2048, or 4096 bytes)
win_size specifies the default window sizes (1 to 127, 7*)
tput specifies the default throughput classes (75 to 215 b/s, 64 000*)
X.25 Service
(400)
27.17-13
27.17 X.25 PVCs


NNP 95-2035-01-00-B
To delete X.25 PVCs

When both ends of the PVC are on the same switch, you specify the local NUA and
LCN, and delete the PVC. When the two ends are supported by different switches,
you must delete the PVC from each switch.
DELETE
where
27.17-14
(400)
X.25 Serivce

NNP 95-2035-01-00-B
27.18
27.18 Hunt Groups

Hunt Groups
This chapter describes switch-wide hunt groups and how to configure them.
Although the notion of network-wide hunt groups is introduced in this chapter,
section 27.7.3 provides detailed network-wide hunt group information.
27.18.1
Understanding Hunt Groups

A hunt group is a group of NUAs that can be signalled using one or more called
addresses configured for the group. While each hunt group member also has a
unique NUA, the hunt group address provides a means to transparently and
equitably distribute incoming calls among the members. Two types of hunt groups
exist: switch-wide and network-wide.
In X.25 networks, the access lines associated with a hunt group typically provide
access to multiple ports on a front-end processor or server. These ports generally
provide common resources to users. Multiple users can access the required
resources by calling the hunt group address, rather than the address of each
individual port.
The MainStreet X.25 switch uses the round-robin method of hunting, based on the
chronological order in which members are added to the hunt group. For example, if
a network operator adds NUAs 3333, 2222 and 1111 to a hunt group in that order,
calls are routed in the order 3333, 2222 and 1111. The switch keeps track of the NUA
to which the last incoming virtual call was delivered, and attempts to deliver the
next incoming call to the next NUA on the hunt list. If the selected NUA is not
available (all logical channels are busy or out of service), the switch checks the next
NUA on the list for available channels. If all the NUAs are busy, two results are
possible.
If the hunt group has a redirection address, the switch routes the call to that
address.
If no redirection address exists, the switch clears the call.

MainStreet X.25 supports a maximum of 32 hunt groups per switch. PE cards
support a maximum of 24 members per hunt group, and X.25 FRE cards support up
to 12 members per hunt group. Because all members of a hunt group must be
supported by the same switch, an NUA can belong to a maximum of 32 hunt groups.
Switch-wide hunt groups

A switch-wide hunt group is a group of NUAs that can be signalled that span across
a single switch.
X.25 Service
(400)
27.18-1
27.18 Hunt Groups


NNP 95-2035-01-00-B
Network-wide hunt groups

A network-wide hunt group is a group of XACs that can be signalled from any
switch in the network using a common address. Compared to switch-wide hunt
groups, network-wide hunt groups support members that span more than one
switch, and offer greater redundancy and protection in the event of a switch or trunk
failure. Network-wide hunt group calls can be routed to alternate switches when a
selected switch or route is not available.
Hunt group addresses

Every hunt group is assigned a unique X.121 or E.164 address. Hunt group members
are identified in the group by their individual NUAs. The address assigned to the
hunt group does not have call subscription options, nor does it have its own XAC
interface parameters. Calls to a hunt group address are processed according to the
call subscription options and XAC interface parameters of the member NUAs.
When a call is established to a hunt group member, the hunt group address always
appears in the called address field of the Call Request, Incoming Call and Call
Connected packets. There is no translation between the hunt group address and the
member address.
Redirection addresses
You can assign a single redirection address to each hunt group. The redirection
address specifies an alternate address on another switch to which calls are routed
when all of the hunt group members are engaged. The redirection address can be
either an NUA or a hunt group address, but it cannot be a local address; that is, the
redirection address must be served by a remote switch.
For calls to a hunt group address, redirection can occur only to the hunt group
redirection address; the switch does not permit redirection from a hunt group
member NUA. While individual member NUAs can be assigned the Call
Redirection facility, the NUA redirection address is used only when the original
called address is that of the NUA.
Internodal hunting
The redirection address provides a means to achieve hunting between switches. If
all the members of the originally called hunt group are engaged, the local switch
redirects the call to the redirection address on the remote switch. Hunting across
switches is limited to two switches because calls can be redirected only once. When
the redirection address is a hunt group address, hunt group membership is
effectively extended beyond the limit of the card.
27.18-2
(400)
X.25 Serivce

NNP 95-2035-01-00-B
27.18 Hunt Groups

Extended hunt groups

Although a hunt group can have a maximum of 16 or 24 members, depending on the
card type, you can extend the membership of a hunt group by assigning it a
redirection address that is itself a hunt group address. Using this approach, you can
create two hunt groups that function as a single virtual hunt group with up to 48
members, 24 on each switch.
27.18.2
Viewing Hunt Group Information

You can view all of the hunt group addresses configured on the switch, and all the
member NUAs of a particular hunt group. On both displays, the NUAs are sorted in
ascending numerical order.
Figure 27.18-1 is an example NMTI display showing the hunt group addresses for a
switch.
Figure 27.18-1: Hunt Group Addresses Display
X25FRE Stations:nn
PA11-H1-00
Toronto:A
Alarms:1
11-May-1997
8:35a
HUNT GROUP ADDRESSES

-------------------x3020447800
CONFIG SWITCH X25 HUNT_GROUP ??

Enter hunt group address. ([npi]nnn...)
F1-PREVIOUS
F2-NEXT
F3F6F7F8-CANCEL
F4F9-QUIT
F5F10-
Figure 27.18-2 shows all the members belonging to the hunt group identified by
address x3020447800.
X.25 Service
(400)
27.18-3
27.18 Hunt Groups


NNP 95-2035-01-00-B
Figure 27.18-2: Hunt Group Members Display

X25FRE Stations:nn
PA11-H1-00
Toronto:A
Redirection Address
Alarms:1
11-May-1997
8:35a
:---
HUNT GROUP MEMBERS

------------------
CONFIG SWITCH X25 HUNT_GROUP x3020447800

F1-ADD_MEMB
F6-
F2-DEL_MEMB
F7-
F3-DELETE
F8-CANCEL
F4-REDIRECTN
F9-QUIT
F5F10-
To view hunt group information

CONFIG SWITCH X25 HUNT_GROUP
SHOW_ALL
<address>
SHOW_MEMB
SK000431
where address is the X.121 or E.164 address that identifies the hunt group
27.18.3
Configuring Hunt Groups

The process of configuring a hunt group involves defining a hunt group address in
E.164 or X.121 format, and adding members to the hunt group. Hunt group members
are identified by their NUAs.
Hunt group configuration overview
27.18-4
1.
Configure the hunt group address as described in the procedure To add and
delete hunt group addresses.
2.
Configure the parameters for an XAC. See chapter 27.14.
3.
Configure an NUA and assign it to the XAC. See chapter 27.15.
(400)
X.25 Serivce

NNP 95-2035-01-00-B
4.
27.18 Hunt Groups

Add the NUA to the hunt group as described in the procedure To add and
delete hunt group members.
The following subsections describe the hunt group parameters and provide
configuration guidelines.
Hunt Group Address

This parameter specifies the X.121 or E.164 address for the hunt group.
You define a hunt group address by specifying the NPI and entering the address in
0 or 9.
Range
NPI (x, e, or m) and 1 to 19 digits in X.121 or E.164 address format
Default
None
Redirection Address
This parameter specifies an X.121 or E.164 address to which calls are redirected
when none of the hunt group members are available. The redirection address cannot
exist on the same switch, it must be either an NUA or hunt group address on another
switch.
Range
NPI (x, e, or m) plus 1 to 19 digits in X.121 or E.164 address format
Default
None
Hunt Group Member NUA

This parameter defines an NUA as a member of the hunt group. The NUA must
already be configured on the same switch as the hunt group address.
X.25 Service
(400)
27.18-5
27.18 Hunt Groups


NNP 95-2035-01-00-B
Range
NPI (x, e, or m) plus 1 to 19 digits in X.121 or E.164 address format
Default
None

Observe the following restrictions and interdependencies when configuring hunt
groups.
The switch supports a maximum of 32 hunt groups.

A hunt group can have a maximum of 16 members on X.25 FRE cards, and 24
members on PE cards.
The redirection address cannot be an NUA or hunt group address on the same
switch.
A call to a hunt group address can be redirected only to the hunt group
redirection address, and can be redirected only once.
The Link Layer Inactivity Timer (T3) should be set appropriately for all XACs
that have NUAs belonging to hunt groups. The optimum value of T3 depends on
the interface speed of the link and the need for quick detection when the link goes
down. For example, for a critical application running over a high-speed link, the
timer should be set to a relatively low value. See chapter 27.14 for information
about configuring link layer timers.

You can change the redirection address for a hunt group at any time with no
disruption of service. The change is effective for the next call.
To add and delete hunt group addresses

CONFIG SWITCH X25 HUNT_GROUP <address>
PROCEED
REDIRECT
DELETE
<rd_address>
PROCEED
SK000432
where
address is the X.121 or E.164 address that identifies the hunt group (NPI plus 1 to 19 digits in international
format)
rd_address is an X.121 or E.164 address for call redirection (NPI plus 1 to 19 digits in international format)
27.18-6
(400)
X.25 Serivce

NNP 95-2035-01-00-B
27.18 Hunt Groups

To add and delete hunt group members

CONFIG SWITCH X25 HUNT_GROUP <address>
ADD_MEMB
DEL_MEMB
<member_nua>
<member_nua>
SK000433
where
address is the address that identifies the hunt group (1 to 19 digits in E.164 or X.121 format)
member_nua is a valid NUA configured on the switch (1 to 19 digits in E.164 or X.121 format)
X.25 Service
(400)
27.18-7

NNP 95-2035-01-00-B
27.19

Provisioning X.25 User Access

This chapter describes the configuration activities a network operator must perform
to provide user access to a 36120 MainStreet X.25 switch. This chapter puts the
information from chapters 27.13, 27.14, and 27.15 in the context of step-by-step
procedures. The chapter contains procedures to provision service for:
devices connected directly to the X.25 switch

devices connected to the switch over frame relay
subrate devices connected to the switch over frame relay
Note 1
The examples in this chapter assume that the user device is configured as an X.25
DTE and the XAC is DCE; however, the procedures are identical regardless of how
the interfaces are defined.
Note 2
The softkey trees in the following procedures show only the softkeys and variables
that are critical to the configuration process. For complete configuration
information, see the appropriate sections in this document.
27.19.1
Direct X.25 Access

X.25 devices running at basic rate, super-rate, and transparent subrate speeds can be
connected directly from a data interface card or PRI card to the X.25 switch.
To provision direct access lines

The following procedure shows how to provision service for basic rate, super-rate,
and n 8 kb/s subrate X.25 devices that require direct access to the X.25 switch.
Figure 27.19-1 shows the circuits and connections that must be configured. The
numbers in the illustration correspond to the step numbers in the procedure that
follows.
X.25 Service
(400)
27.19-1


NNP 95-2035-01-00-B
Figure 27.19-1: Direct X.25 Access

Backplane
DCC
X.25 FRE
or PE card
2
m x n x 8 kb/s
3
1
X.25 DTE
= 1 to 31
= X.25 access circuit
= 1 to 8
= Direct circuit
7525

1.
Configure the circuit on the data interface card or PRI card to which the X.25
device is connected.
2.
Configure an X.25 switch circuit as a direct circuit.

APPLI
I/F_SPEED
TRANSP_BW
DIRECT_CCT
<speed>
<bandwidth>
SK000434
where speed and bandwidth must match the interface speed configured in step 1 (m n 8 kb/s)
See section 27.13.2 for more information.

3.
Connect the data interface circuit or PRI circuit to the direct circuit.
27.19-2
(400)
X.25 Serivce

NNP 95-2035-01-00-B

At the X.25 switch NMTI

4.
Configure an XAC.
i.
Configure the link and network layer parameters, and the address
translation table for the XAC. See chapter 27.14.
ii.
Configure the NUA and assign it to the XAC. See section 27.15.4.
iii. Configure the NUA subscription options and facilities. See section 27.15.7.
5.
Connect the XAC to the direct circuit.

CONFIG CONNECT <Xxac> TO <dir_cct>
where
Xxac is the XAC configured in step 4
dir_cct is the X.25 direct circuit configured in step 2
27.19.2
Encapsulated Access
Devices running at basic rate, super-rate, and n 8 kb/s subrate speeds can be
connected using the FRS card or a standards-compliant PAD/FRAD. Devices
running at subrate speeds other than n 8 kb/s must access the switch through the
FRS card.
To provision encapsulated access to the X.25 switch

The following procedure shows how to provision service for basic rate, super-rate,
and n 8 kb/s subrate X.25 devices that require encapsulated access to the X.25
switch through the FRS card. Connections are made to the FRS, where frame relay
encapsulation is performed, then to the X.25 switch. The connection from the FRS to
the X.25 switch can be made within the node or to a remote node. In the latter case,
primary rate links must also be configured and connected between the nodes.
Figure 27.19-2 shows the circuits and connections that must be configured when the
FRS and X.25 switch are on the same node. The numbers in the illustration
correspond to the step numbers in the procedure that follows.
X.25 Service
(400)
27.19-3


NNP 95-2035-01-00-B
Figure 27.19-2: Encapsulated Access

Backplane
DCC
FRS card
X.25 FRE
or PE card
4
5
6
12
m x n x 8 kb/s
9
11
1
2
3
X.25 DTE
= 1 to 31
= 1 to 8

7116

1.
2.
Configure an FRS circuit for frame relay encapsulation.

APPLI
I/F_SPEED
TRANSP_BW
FR_ENCAP
<speed>
<bandwidth>
SK000435
where speed and bandwidth must match the interface speed configured in step 1
(m n 8 kb/s)
3.
Connect the data interface or PRI circuit to the FRS encapsulation circuit.
27.19-4
(400)
X.25 Serivce

NNP 95-2035-01-00-B
4.

Configure an FRS circuit as a frame stream.

APPLI
I/F_SPEED
STREAM
<speed>
SK000436
where speed must be at least the interface speed configured in step 1 (m n 8 kb/s)
5.
Configure a X.25 switch circuit as a frame stream, and set the interface speed
equal to the speed configured in step 4 (m n 8 kb/s).
6.
Connect the two frame stream circuits to set up the frame stream.
CONFIG CONNECT <frs_sn-cc> TO_CIRCUIT <fre_sn-cc> PROCEED
where
frs_sn-cc is the FRS circuit configured in step 4
fre_sn-cc is the X.25 FRE circuit configured in step 5
At the FRS NMTI

7.
Configure the parameters for the encapsulation circuit.

CONFIG ENCAP_CCT <cc>
FRAME_SIZE
THRESHOLDS
X25_PKT_SZ
SK000437
where cc is the encapsulation circuit configured in step 2
See the subsection Configuring the parameters for encapsulation circuits in

section 27.13.3 for more information.
8.
Configure the frame stream parameters.

CONFIG STREAM <Scc>
FRAME_SIZE
THRESHOLDS
PROTOCOL
SK000438
where Scc is the frame stream circuit configured in step 4
X.25 Service
(400)
27.19-5

9.

NNP 95-2035-01-00-B
Connect the encapsulation circuit to a DLCI on the frame stream circuit and set
the class of service parameters.
CONFIG CONNECT <cc> or <Scc-dlci>
TO_DLC
INFO_RATE
<cc> or <Scc-dlci>
SK000439
where
cc is the frame relay encapsulation circuit configured in steps 2 and 7 (0 31)
Scc-dlci is the frame stream circuit configured in steps 4 and 8, and a DLCI (16 to 1007)

10. Configure the frame stream parameters.
CONFIG STREAM <Scc>
FRAME_SIZE
THRESHOLDS
NUM_FLAGS
PROTOCOL
SK000440

11. Configure an XAC.
i.
ii.
12. Connect the XAC to the stream-DLCI, and set the class-of-service parameters.
CONFIG CONNECT <Xxac> TO <Scc-dlci> PROCEED
where
Scc-dlci is the frame stream circuit configured in steps 5 and 10, and the DLCI used in step 9
See sections 27.13.8 and 27.13.9 for more information.
To provision subrate encapsulated access to the X.25 switch

X.25 devices running at subrate speeds other than n 8 kb/s are connected from a
data interface card or PRI card to an FRS card equipped with a SRIM, where LAPB
frames are encapsulated in frame relay frames; the frame relay frames are then sent
to the X.25 switch.
27.19-6
(400)
X.25 Serivce

NNP 95-2035-01-00-B

The following procedure shows how to provision encapsulated access for subrate
X.25 devices. Connections are made to the FRS for frame relay encapsulation, then
to the X.25 switch for call processing and routing. The connection from the FRS to
the X.25 switch can be made within the node or to a remote node. In the latter case,
primary rate links must also be configured and connected between the nodes.
Figure 27.19-3 shows the circuits and connections that must be configured when the
FRS and X.25 switch are located on the same node. The numbers in the illustration
correspond to the step numbers in the procedure that follows.
Figure 27.19-3: Subrate Encapsulated Access

Backplane
DCC
FRS card
X.25 FRE
or PE card
7
8
9
12
15
1.2 to 56 kb/s
2
1
14
6
X.25 DTE

7524

1.
2.
Configure an FRS subrate circuit for rate adaption.

where sn-SRcc is the slot number and subrate circuit number on the FRS
3.
Configure the same FRS subrate circuit for frame relay encapsulation.
CONFIG CIRCUIT <sn-SRcc> FUNCTION APPLI FR_ENCAP
where sn-SRcc is the slot number and subrate circuit number used in step 2
X.25 Service
(400)
27.19-7

4.

NNP 95-2035-01-00-B
Configure an FRS circuit for rate adaption.

CONFIG CIRCUIT <sn-cc> FUNCTION APPLI RATE_ADAPT
HCM
DDS
X.50
SK000441
5.
Connect the subrate encapsulation circuit to the rate adapted circuit.

where
sn-SRcc is the slot number and subrate circuit number configured in steps 2 and 3
sn-cc is the slot number and circuit number configured in step 4
6.
Connect the rate adapted circuit to the data interface or PRI circuit.
CONFIG CONNECT <ra_sn-cc> TO_CIRCUIT <sn-cc> PROCEED
where
ra_sn-cc is the slot number and circuit number configured in step 4
sn-cc is the slot number and circuit number configured in step 1
7.
Configure an FRS circuit as a frame stream.

APPLI
I/F_SPEED
STREAM
<speed>
SK000436
where speed is 8 to 1984 kb/s
8.
Configure an X.25 switch circuit as a frame stream, and set the interface speed
equal to the speed configured in step 7.
9.
Connect the two frame stream circuits to set up the frame stream.
CONFIG CONNECT <frs_sn-cc> TO_CIRCUIT <fre_sn-cc> PROCEED
where
frs_sn-cc is the FRS circuit configured in step 7
fre_sn-cc is the X.25 FRE circuit configured in step 8
27.19-8
(400)
X.25 Serivce

NNP 95-2035-01-00-B

At the FRS NMTI

10. Configure the parameters for the subrate encapsulation circuit.
CONFIG ENCAP_CCT <cc>
FRAME_SIZE
THRESHOLDS
X25_PKT_SZ
SK000437
where SRcc is the subrate encapsulation circuit configured in steps 2 and 3
See the subsection Configuring the parameters for encapsulation circuits in

section 27.13.3 for more information.
CONFIG STREAM <Scc>
FRAME_SIZE
THRESHOLDS
PROTOCOL
SK000438

12. Connect the subrate encapsulation circuit to a DLCI on the frame stream circuit
and set the class of service parameters.
CONFIG CONNECT <SRcc> or <Scc-dlci>
TO_DLC
INFO_RATE
<SRcc> or <Scc-dlci>
SK000445
where
SRcc is the subrate encapsulation circuit configured in steps 2, 3 and 10 (0 to 31)
Scc-dlci is the frame stream circuit configured in steps 7 and 11, and a DLCI (16 to 1007)

CONFIG STREAM <Scc>
FRAME_SIZE
THRESHOLDS
NUM_FLAGS
PROTOCOL
SK000440
X.25 Service
(400)
27.19-9


NNP 95-2035-01-00-B

14. Configure an XAC.
i.
ii.
15. Connect the XAC to the stream-DLCI, and set the class of service parameters.
CONFIG CONNECT <Xxac> TO <Scc-dlci> PROCEED
where
Scc-dlci is the frame stream circuit configured in steps 8 and 13, and the DLCI used in step 12
See sections 27.13.8 and 27.13.9 for more information.
27.19-10
(400)
X.25 Serivce

NNP 95-2035-01-00-B
27.20

X.25 to Frame Relay Service

Interworking
This chapter describes how to configure the parameters and enable X.25 to frame
relay service interworking on a PE or X.25 FRE card.
27.20.1
Understanding the X.25 to frame relay service

interworking
X.25 to frame relay service interworking allows X.25 service users to communicate
directly with frame relay service users. This service interworking function makes it
possible for the following service users to communicate on a single common
network:
X.25 users and frame relay users on the same network

X.25 users and frame relay users on different networks (for example, between an
existing X.25 network user and a new user of the 36120 MainStreet frame relay
network.
users on a non-36120 MainStreet X.25 network and 36120 MainStreet frame relay
users
X.25 to frame relay service interworking also allows new frame relay services to be
introduced into an existing X.25 network.
Service interworking
X.25 to frame relay service interworking allows devices running two different
protocols (X.25 and frame relay) to communicate with each other. To accomplish
data transfer, X.25 data packets are converted into frame relay frames when data is
transmitted from an X.25 DTE to a frame relay device. Conversely, frame relay
frames are converted into X.25 packets when data is transmitted from a frame relay
device to an X.25 DTE.
Figure 27.20-1 shows an example of a X.25 to frame relay service interworking
application.
X.25 Service
(400)
27.20-1


NNP 95-2035-01-00-B
Figure 27.20-1: Example of Service Interworking
SVC
X.25
XAC
X.25
network
XFR
Frame relay
network
Frame
relay
link
XFR
X.25 SVC
Frame relay
PVC
9987
The figure shows the types of connections that are available on the two ends of the
service interworking virtual circuit. It is also possible to have an X.25 PVC connected
on the X.25 side. However, only one type of connection (either X.25 SVC or X.25
PVC) can be made to a service interworking circuit.
Network interworking
Service interworking should not be confused with network interworking
(encapsulation). Network interworking provides a method for communication
between two X.25 DTEs over a frame relay network. The entire packet (LAPB+data)
being transmitted is encapsulated by a frame relay header (using Annex G
encapsulation) and then transmitted over the frame relay network. Encapsulated
frames received by the destination device are decapsulated and the original packet
is delivered. See section 27.13.1 for detailed information on encapsulation.
Figure shows an example of encapsulated access using a PAD/FRAD.
27.20-2
(400)
X.25 Serivce

NNP 95-2035-01-00-B

Figure 27.20-2: Example of Network Interworking

X.25 site
Frame
relay
LAPB
DCC
or
DNIC
or
PRI
card
X.25
switch
X.25
backbone
network
Frame relay
network
DTE
LAPB-encapsulating
PAD/FRAD
7551
End-to-end protocol stack

One level above the X.25 and a frame relay protocol stack, the XFR may be viewed
as an internal virtual X.25 PAD on the X.25 switch. The complete end-to-end
protocol stack is shown in Figure 27.20-3.
Figure 27.20-3: End-to-end Protocol Stack
XFR
X.25
X.25
LAPB
X.25
trunks
LAPB
X.25 DTE
PE
X.25
Frame
relay
X.25
trunks
PE
X.25 SVC/PVC
Frame
relay
Frame
relay
FRE
Frame relay device
Frame relay PVC

9856
The X.25 network layer running on the X.25 switch acts as the interface for XFR
connection. For information on how to configure an XAC for XFR operation, see
section 27.20.6.
Frame loss
Packets arriving at the XFR XAC (for a definition, see section X.25 to frame relay
service interworking XAC) are processed and transmitted directly to the frame
relay PVC as frames. These frame relay frames are treated like any other data frames
within the frame relay network and may be subject to discard during congestion. To
handle frame discards, higher layer protocols between the X.25 and frame relay
devices are responsible for frame recovery.
X.25 Service
(400)
27.20-3

27.20.2

NNP 95-2035-01-00-B
X.25 to Frame Relay Service Interworking Components

X.25 to frame relay service interworking is comprised of a standard X.25 XAC
running XFR software, a frame relay PVC and an X.25 virtual circuit (SVC or PVC).
An X.25 XAC configured for service interworking is referred to as an XFR XAC.
X.25 to frame relay service interworking XAC

X.25 to frame relay service interworking can be configured on standard X.25 XACs
by setting the Service Type to XFR and assigning a unique X.121 or E.164 address to
the XAC. All XACs configured for XFR operation support standard X.25 XAC
functionality unless stated otherwise in this chapter.
PE cards support up to 512 XFR XACs with full functionality. Each XFR XAC can
support only one X.25 SVC or PVC connection and one frame relay PVC connection.
Since XFR XACs can be configured anywhere in a network, network operators may
locate them strategically with respect to line quality, types of protocol and
application.
Frame relay permanent virtual circuit connection

An XFR XAC is connected to the frame relay device over a frame relay PVC in the
form of a standard stream-DLCI pair. The frame relay PVC is configured during
XAC setup using the method described in chapter 27.17.
The X.25 SVC clears or the X.25 PVC resets if a frame relay link failure occurs.
Subsequent SVCs are either cleared or redirected if Call Redirection functionality is
enabled.
X.25 virtual circuits

Two types of X.25 virtual circuit configurations may be used to connect an XFR XAC
to an X.25 network either with switched virtual circuits or permanent virtual
circuits. Only one of the configurations is supported per XFR XAC.
SVC connections
An X.25 SVC connection is established when an X.25 DTE places a call request by
calling the address of the XFR XAC. The XFR XAC maps the call to the frame relay
PVC to create an X.25 to frame relay end-to-end connection.
The X.25 SVC connection remains established until data transfer is complete and a
Clear Call request is made by the X.25 DTE, or until the frame relay PVC link is lost.
PVC connections
An X.25 PVC provides a permanent end-to-end connection between a logical
channel number on the calling DTE and the XFR XAC. PVCs are provisioned by the
network operator and require no call setup or clearing procedures. See chapter 27.17
for detailed configuration information about X.25 PVCs.
27.20-4
(400)
X.25 Serivce

NNP 95-2035-01-00-B

The X.25 PVC connection remains established until it is deleted from the
configuration. If the frame relay PVC is deleted or lost, a reset request is made.
27.20.3
Call Management
An XFR XAC provides call setup and routing, data transfer, and call clearing
management for the duration of the call. Data transfer is terminated when the X.25
SVC is cleared, the X.25 PVC is reset or the frame relay PVC goes out of service.
Call setup
To set up an X.25 SVC to frame relay PVC call, the frame relay PVC connection must
be made before the X.25 SVC connection can be established. To set up an X.25 PVC
to frame relay PVC call, it does not matter which connection is established first. Data
transfer is initiated when the complete call path has been established.
An XFR XAC can be set up anywhere within a network as shown in Figure 27.20-4
does not necessarily have to reside on the same PE or FRE card as the DCE circuit.
Figure 27.20-4 shows an example of the call path from an X.25 DTE to a frame relay
device. XAC1 is configured for X.25 service type and has an NUA of X.121 111111.
XAC2 is configured for XFR service type and has an NUA of X.121 222222. The X.25
DTE establishes communication with the frame relay device by placing a call request
to the XFR. A call request with called address X.121 222222 arriving at XAC1 is
routed to XAC2 (XFR) using standard X.25 call routing techniques. When the call
arrives at the XFR, it is mapped to the frame relay device over the already connected
frame relay PVC. The XFR is now ready to transfer data between the two users.
Figure 27.20-4: End-to-end Call Path
XAC1
(X.25)
Frame
relay
X.25 DTE
Frame relay
device
XAC2 (XFR)
9883
X.25 Service
(400)
27.20-5


NNP 95-2035-01-00-B
Call routing
An SVC session is established by either calling the address of the XFR or the hunt
group to which the XFR belongs. X.25 calls may be distributed across multiple XFR
XACs through the use of switch-wide or network-wide hunt groups. The XFR maps
an allocated LCN to the stream-DLCI pair and the session remains established until
the call is cleared by the remote DTE or the XFR XAC is disabled.
The XFR generates a request to tear down the X.25 SVC when the frame relay PVC
connection is lost.
Data transfer
Data packet transfer between an X.25 DTE and a frame relay device is performed by
removing the X.25 header from the data packet and inserting a frame relay header
when transmitting data from X.25 to frame relay. Conversely, the frame relay header
is removed and the X.25 header is inserted when transmitting data from frame relay
to X.25. The content of the data portion of the frame is not inspected and remains
unaltered. Figure 27.20-5 shows bidirectional XFR header conversion.
Figure 27.20-5: XFR Header Conversion
Flag
1 1
Flag
1 1
LCGN
DLCI
(low)
LCN
FECN
GFI
BECN
DLCI (high)
XFR
0
EA
X.25 to FR
service
interworking
PTI
EA
LAPB control field
DE
C/R
LAPB address field
Data
Data
CRC
Flag
CRC
Frame relay frame
Flag
X.25 data packet
9857
27.20-6
(400)
X.25 Serivce

NNP 95-2035-01-00-B

Note
Ensure that the frame size is greater than the data packet size. When data is being
transferred from a frame relay device to an X.25 DTE, the data is segmented and
poses no problem. However, when data is transferred in the opposite direction if the
frame size is not greater than the user data size the frames are discarded.
X.25 to frame relay transmission

Packets arriving at the XFR XAC from an X.25 SVC or PVC are converted to frames
and transmitted directly to the frame relay PVC.
Frame relay to XFR transmission
An established and active X.25 SVC or PVC is required to process frames transmitted
by the frame relay device. The frames are processed and transmitted directly on the
X.25 SVC or PVC unless the virtual circuit is flow controlled. If a virtual circuit is
flow controlled, the frames are queued in the To_X.25_Holding queue.
Connection management
Connection management between an X.25 virtual circuit and a frame relay PVC is
handled by responding to messages received from the LMI implemented on the
frame relay network. It is capable of handling any frame relay PVC status and
configuration change, as well as any required frame relay link rerouting in the event
the connection becomes unavailable.
Link Management Interface

The LMI status for the frame relay PVC is directly connected to and maintained by
the XFR XAC, and is X.25 connection dependant. If the X.25 DTE clears the call, the
XFR XAC changes the status of the frame relay PVC from active to inactive. This
message is propagated to the frame relay end-user device.
The LMI protocol implemented in the frame relay network provides frame relay
PVC status change information. Figure 27.20-6 shows an example of service
interworking using LMI.
X.25 Service
(400)
27.20-7


NNP 95-2035-01-00-B
Figure 27.20-6: Example of Service Interworking Using LMI

XAC1
Link 1
Link 2
FRAD
NNI
NNI
8230 MainStreet
X.25 DTE
XAC2
(XFR)
Frame Relay PVC

10550
Within the example network, frame relay links 1 and 2 are configured with NNI
protocol. This configuration provides bidirectional status messaging capability
within the frame relay portion of the network.
If link 2 is lost while a call is active, a status change message is propagated towards
the XFR. When this message reaches the XFR XAC, a Frame Relay Reconnect
Timer is started.
If link 2 becomes available before the timer expires, the call status goes back to
Data Transfer and the timer is reset. If link 2 does not become available before the
timer expires, the PVC is deemed to be permanently lost and the call is cleared.
When the timer expires, a Frame Relay Link Not Available cause code message is
sent to clear the X.25 SVC or reset the X.25 PVC.
The frame relay PVC may be configured for rerouting by the MainStreetXpress
46020 Network Manager. In such cases, if the frame relay path is lost during data
transfer, the call is directed to the destination using an alternate path. If the call is
re-established prior to timer expiry, the timer is reset and normal network
operation continues. The call is cleared if the timer expires before alternate path
routing occurs.
Flow control
Flow control is applied only when data is being transferred from the XFR to an
X.25 DTE. It consists of frames being buffered in the To_X.25_Holding queue and
a frame relay flow control notification (BECN) bit being set on frames sent to the
frame relay device.
The closure of the X.25 window triggers flow control or the network layer is flow
controlled by the RTP. Frame relay frames arriving at a congested XFR are placed
in the To_X.25_Holding queue and labelled as frames waiting to be delivered. An
XFR will stay in a congested state until all packets in the holding queue are
delivered. The BECN bit is set on all frames transmitted back to the frame relay
device while the XFR is in a congested state.
Congestion level monitoring

The congestion level of the XFR XAC is monitored against a set of preconfigured
congestion threshold parameters: MCT, SCT and ACT. See 27.20.4 for details about
these parameters. These threshold parameters are also responsible for raising and
clearing XFR congestion alarms.
27.20-8
(400)
X.25 Serivce

NNP 95-2035-01-00-B

Alarm raising
Service interworking congestion alarming is monitored against a preconfigured SCT
value. Congestion analysis is performed each time a frame is added to or removed
from the congestion queue. An XFR Congested alarm is raised when the SCT value
is met or exceeded.
Alarm clearing
The XFR Congested alarm remains raised until the congestion level falls below a
preconfigured MCT value or until all of the frames with a set DE bit have been
de-queued or discarded. When the congestion is cleared, the XFR Congestion
Cleared alarm is raised.
Accounting
Accounting records are produced at one of the two XACs involved the X.25 virtual
circuit. The records are normally created at the calling end, although records are
produced at the called XAC (XFR XAC) in the case of a reverse charge call.
Accounting records for service interworking connections are generated using the
same methods as is done for normal X.25 calls. For service interworking calls, either
the local or remote Service Type field contained in the accounting record indicates
that an XFR XAC is being used. See chapter 27.10 for details about X.25 accounting.
X.25 to frame relay service interworking features

The following list of standard 36120 MainStreet X.25 Service facilities and features
can be used on calls involving service interworking:
X.25 Service
basic and gateway routing

XFR XAC switch-wide and network-wide hunt group membership
CUG and ICUG
interworking between X.25 or X.75 PVC and FR PVC
interworking between X.25 or X.75 SVC and FR PVC
NUI validation
link and network layer maintenance and statistics
normal and reverse charging
flow control negotiation
packet segmentation and recombination
accounting record generation
address translation or XAC to XFR XAC calling
guaranteed delivery to XFR using D-bit operation
switch-wide XFR redundancy through call redirection
(400)
27.20-9


NNP 95-2035-01-00-B
X.25 to frame relay service interworking restrictions

The following list of standard 36120 MainStreet X.25 Service facilities and features
are either not supported or have restricted functionality for this release:
27.20.4
Fast select with and without restricted response

Address translation on XFR XAC
multi NUA on the XFR XAC
congestion control for frames travelling from X.25 to a frame relay device
multiple FR PVC and X.25 virtual circuit support per XFR XAC
FECN and BECN statistics gathering.
X.25 to Frame Relay Service Interworking Parameters

To configure an XAC for service interworking, you must first set the service type
parameter to XFR. Each XAC configured for service interworking maintains three
congestion parameters (MCT, SCT and ACT) and a frame relay reconnect timer.
Mild congestion threshold

The MCT parameter specifies the point at which the XFR becomes mildly congested.
When an XFR reaches the MCT value, the BECN bit is set on frames transmitted back
toward the frame relay device. The default MCT value is set at 50% of the ACT value
and is expressed as a percentage of ACT. This is a configurable parameter that is
expressed as a percentage of the ACT value.
Range
0% to 100%
Default
50%
Severe congestion threshold

The SCT parameter specifies the point at which the XFR becomes severely
congested. When the XFR reaches the SCT value, it continues to set the BECN bit on
frames transmitted back toward the frame relay device and raises the XFR
Congested alarm. In addition, any frame transmitted toward the X.25 DTE that has
its DE bit set is discarded. The default SCT value is set at 80% of the ACT value and
is expressed as a percentage of ACT. This is a configurable parameter that is
expressed as a percentage of the ACT value.
27.20-10
(400)
X.25 Serivce

NNP 95-2035-01-00-B

Range
0% to 100%
Default
80%
Absolute congestion threshold (ACT)

This parameter specifies the maximum number of packets that may be queued on
the XFR when transmission is directed towards an X.25 DTE. When the XFR reaches
the ACT value, all received frames are discarded until the congestion level falls
below the ACT value. The ACT value represents the maximum number of packets
than can be queued and is expressed in number of packets.
An ACT value of 0 indicates that no queuing occurs.
Ranges
0 to 128 packets
Default
10
Frame relay reconnect timer

This parameter specifies the maximum allowable time for the XFR to reconnect to a
frame relay PVC that has become unavailable. If the time expires, the frame relay
PVC is deemed permanently disconnected and the X.25 SVC is cleared or the X.25
PVC is reset.
This timer has two special values associated with it, 0 and 999. If the timer is set to a
value of zero, the X.25 virtual circuit is cleared or reset immediately. If the timer is
set to a value of 999, the X.25 virtual circuit is never cleared.
Range
0 to 500 seconds
Default
120 seconds
Viewing service interworking parameters

Figure 27.20-7 shows the XFR configuration parameters.
X.25 Service
(400)
27.20-11


NNP 95-2035-01-00-B
Figure 27.20-7: XFR Configuration Parameters

X25FRE Stations:nn
PA11-H1-00
Toronto:A
Alarms:1
Absolute Congestion Threshold

Frame Relay Reconnect Timer
11-May-1997
8:35a
:10
:80 %
:50 %
:120 sec
CONFIG X.25_ACCESS XAC 112 XFR_PARAMS

F1-ACT
F6-
F2-SCT
F7-
F3-MCT
F8-CANCEL
F4-FR-RCN_TMR F5F9-QUIT
F10-
To view service interworking parameters

CONFIG X25_ACCESS XAC <xac> XFR_PARAMS
where xac is a valid XAC.
27.20.5
Network User Address Parameters

XACs that are configured for service interworking must be assigned an NUA. The
NUA parameters uniquely define the XAC for calling and statistical purposes. For a
complete list of NUA parameters, see Chapter 27.15.
Typically, the standard X.25 NUA parameter ranges and default values provided in
Section 27.15.4 can be used. Table 27.20-1 lists the exceptions.
27.20-12
(400)
X.25 Serivce

NNP 95-2035-01-00-B

Table 27.20-1: XFR NUA Parameters

Parameter
Range
Default
Allocated XAC
number
1128
no default
TOA/NPI
address format
NO
YES
Clear on calling
address failure
NO
YES
YES
Default NUA
NO
YES
YES
Figure 27.20-8 provides an example of the XFR NUA parameters NMTI screen.
Figure 27.20-8: NUA Parameters NMTI
X25FRE Stations:nn
PA11-H1-00
Toronto:A
Alarms:1
11-May-1997
8:35a
NUA Subscrption Options

_______________________

Service type
Allocated XAC Number:
User Defined Data
:x302011888866 (default)
:XFR
:7
:
:Yes
CONFIG X.25_ACCESS NUA x302033888651

F1-SHOW_GROUP
F6-FLOW_CNTRL
F2-ASSIGN_TO
F7-MORE
F3-DELETE
F8-CANCEL
F4-USER_DATA F5-SUBS_OPT
F9-QUIT
F10-PROCEED
To view NUA parameters

where address is a valid NUA (1 to 19 digits)
X.25 Service
(400)
27.20-13

27.20.6

NNP 95-2035-01-00-B
Configuring X.25 to frame relay service interworking

This section describes the parameters and process to configure an XAC for X.25 to
frame relay service interworking.
Note
For the most part, the XAC network layer default values shown in section 27.14.8 are
acceptable. However, ensure that the following XFR specific parameters are also
properly configured.

frame relay reconnect timer
To configure X.25 to frame relay service interworking

1.
Configure the XAC for XFR service type. See Section 27.14.8.
2.
Configure network layer parameters. See section 27.14.8.
3.
Configure the NUA parameters outlined in Section 27.20.6.
4.
Configure all other NUA parameters using the following method.

a.
Define an X.121 or E.164 address in international format. See Section

27.15.4.
b.
Assign a service type to the XAC.

CONFIG X25_ACCESS NUA <address> AGENTS XFR
c.
Assign the NUA parameters to the XFR XAC defined in step 1.

CONFIG X25_ACCESS NUA <address> ASSIGN_TO <xac>
where
address is the NPI and 1 to 19 digits in X.121 or E.164 format
<xac> is 1 to 128 for FRE cards and 1 to 512 of PE cards
d.
Configure the accounting parameters.

CONFIG X25_ACCESS NUA <address> MORE ACCOUNTING
ACTIVATE
27.20-14
(400)
X.25 Serivce

NNP 95-2035-01-00-B

5.
Configure the XFR congestion parameters. See Section 27.20.4.
6.
Configure all accounting parameters. See 27.12.
7.
Configure the frame relay PVC connection.

CONFIG SWITCH <stream-id>
where stream-id is 1- 62
8.
Configure the stream-DLCI to XFR XAC connection.

CONFIG CONNECT <stream-DLCI> TO <xac>
where
stream-DLCI is in the form Sx-nnnn
xac is the XAC number for the XFR XAC
X.25 Service
(400)
27.20-15

NNP 95-2035-01-00-B
28. X.75 Gateway Service

NNP 95-2035-01-00-B
28.1
28.1 Understanding the X.75 Gateway Service

Understanding the X.75 Gateway

Service
This chapter provides an overview of the features and functionality of the X.75
gateway service.
28.1.1
Overview of the X.75 Gateway Service

The X.75 gateway service supports the standardized internetwork connection
arrangements between public packet-switched data transmission networks (X.25
networks), according to the ITU-T Recommendation X.75.
The X.75 gateway feature:
fully complies with the 1984, 1988, 1992 and 1996 versions of ITU-T
28.1.2
Recommendation X.75, and is backwards compatible with the 1980 version of

Recommendation X.75
supports extended routing
Understanding X.75
The X.75 protocol defines the characteristics and operation of links between
packet-switched (X.25) public networks (see Figure 28.1-1). Each internetwork link
comprises two directly connected signalling terminals (referred to as STEs) each
within a public network.
Figure 28.1-1: X.75 Link
Public
X.25
network
STE
DTE
X.75
STE
Public
X.25
network
DTE
9299
X.75 Gateway Service
(400)
28.1-1


NNP 95-2035-01-00-B
X.75 gateway links can:
interconnect two public networks

interconnect public and private networks when X.25 cannot be used
be used in combination with X.25 gateway (X.35) links (see Figure 28.1-2)
Figure 28.1-2: X.75 and X.35 Interconnection Possibilities
public
network
X.75
public
network
X.35
X.75
X.75
X.75
Private
network
Public
network
Newbridge
public
network
X.35
X.35
X.75
Private
network
Private
network
9152
28.1.3
X.75 Utilities
The following X.75 utilities are supported and carried in the X.75 utility field in Call
Request, Call Connected and Clear Request packets.
Call identifier
The call identifier utility is used in conjunction with the calling address to identify
the call. The call identifier is always present in a Call Request packet. If a Call
Request packet is received on an X.75 link and the call identifier utility is not present,
the call is cleared. The call identifier is only present in Call Request packets.
Throughput class indication

The throughput class indication utility is used to specify which throughput class will
apply to the call. Each STE has an opportunity to modify the throughput class
indication request.
28.1-2
(400)

NNP 95-2035-01-00-B

Through a negotiation process in which each X.75 STE may reduce, but not raise, the
requested throughput class value, either X.75 STE is able to request the throughput
class to be used.
If the originating DTE did not request a specific throughput class, each X.75 STE
requests the default throughput class value agreed upon by the network
administrations.
When the called DTE has accepted the call, the STE of the called network confirms
the negotiated throughput class value in the throughput class indication utility of
the Call Connected packet.
If a throughput class value is not explicitly confirmed, the STE of the called network
is assumed to confirm the lowest throughput class value between the default and the
originally requested throughput class value.
Window size indication

Window size is the maximum number of unacknowledged packets that may exist at
any one time.
The window size indication utility in the Call Request packet, allows the calling X.75
STEs to specify the requested window size for each direction.
If specific window sizes are not requested, the calling X.75 STE requests the default
window size for the call (usually a window size of 2).
To confirm the window size that will apply to the call, the called X.75 STE uses the
window size indication utility in the Call Connected packet.
If specific window sizes are specified in the Call Connected packet, the default
window size is assumed.
Packet size indication

The packet size is the maximum number of octets of data that may be carried in a
data packet.
The packet size indication utility allows STEs to specify the data packet size that
apply to each direction of data transmission for the call.
The calling X.75 STE uses the packet size indication utility in the Call Request packet
to request the packet size to be used for each direction.
If specific data packet sizes are not requested, the calling X.75 STE is assumed to
request the default value for the call (usually 128 octets).
The called X.75 STE uses the packet size indication utility in the Call Connected
packet to confirm the packet size to be used for the call.
If specific packet sizes are not specified in the Call Connected packet, the default
packet size is assumed.
(400)
28.1-3


NNP 95-2035-01-00-B
Fast select indication

The fast select utility allows the user data field in the initial Call Request packet and
subsequent Call Connected and Clear Request packets to contain up to 128 octets of
data.
The fast select indication utility is used to indicate that fast select applies to a call.
Two types of fast select can be indicated, fast select with restricted response and fast
select with unrestricted response.
When fast select with restricted response is indicated in the Call Request, the called
X.75 STE must respond by transmitting a Clear Request packet which may contain
128 octets of data. In this case, the called X.75 STE is not permitted to send a Call
Connected packet.
When fast select with unrestricted response is indicated in the Call Request packet,
the called X.75 STE may respond with either a Call Connected packet or a Clear
Request packet, also with up to 128 octet of data.
Reverse charge indication

The reverse charge indication is used to signal that charges for the call should be
reversed.
When using the reverse charge indication utility in the Call Request packet, the
calling X.75 STE indicates a request for reverse charge to apply to the call.
When the reverse charge indication utility is absent, the calling X.75 STE requests a
normal charged call.
The reverse charge indication utility is not present in the Call Connected or Clear
Request packets.
Called line address modification notification

When a call is redirected from its original destination, the called address in the Call
Connected or Clear Request packets differs from the address that was specified in
the original Call Request packet.
The CLAMN utility indicates the reason why the call address was changed. The
following reasons can be indicated:
call distribution within a hunt group

call redirection due to originally called DTE out of order
call redirection due to originally called DTE busy
call redirection due to prior request from the originally called DTE for systematic
call redirection
called DTE originated
call deflection by the originally called DTE
The CLAMN utility is present in the Call Connected packet and the Clear Request
packet when the called DTE address is different from that specified in the initial Call
Request packet.
28.1-4
(400)

NNP 95-2035-01-00-B

The CLAMN utility is not present in a Call Request packet, nor is it present in the
Clear Request packet sent after the call is connected.
Transit network identification code

The TNIC identifies the transit networks through which the call has passed. A TNIC
is inserted into the Call Request packet for each transit network that is traversed by
a call. When the call traverses more than one transit network, the TNICs are listed in
the order in which the transit networks were traversed.
All TNICs are present in the Call Connected packet to identify the complete path of
an internetwork call. TNICs contained in the Call Connected packet are recorded in
the call accounting record in the order in which the transit networks were traversed.
Clearing network identification code

The CNIC identifies the network that cleared the call and is only present if a network
clears the call. The CNIC is present only in the Clear Request packet. The signalling
of a CNIC is controlled by a configuration option. CNICs are recorded in the call
accounting record.
Internetwork closed user group indication

An ICUG is a CUG in which some members are located on X.25 networks that are
separated by an X.75 link.
The ICUG indication utility in the X.75 Call Request packet indicates that the calling
DTE is requesting a call to a member of the indicated ICUG.
The ICUG utility contains the ICUG interlock code applicable to the call.
Internetwork closed user group with outgoing access indication

The ICUGOA indication utility in the X.75 Call Request packet indicates that the
calling DTE has open access. That is, it can make outgoing calls to DTEs belonging
to the same ICUG or to DTEs in the open part of the network. The ICUGOA utility
contains the ICUGOA interlock code applicable to the call.
28.1.4
X.75 Gateway Call Routing

Call routing for the X.75 gateway service is based on the gateway routing
functionality as described in chapter 27.7. The X.75 gateways can be configured to
support routing capabilities such as link redundancy, load sharing, and multiple
and shared address prefixes.
(400)
28.1-5

28.1.5

NNP 95-2035-01-00-B
IPVCs
The remote address of the IPVC is configured as the NUA of the X.75 gateway link
to be used for the IPVC. That is, it is not the remote DNIC that is configured as the
remote address. The use of the NUA allows one to specify the link to use on the PVC
in the case where multiple links support the same address prefixes. The same applies
to the local address. For information on how to configure PVCs, see chapter 27.17.
28.1.6
Internetwork Closed User Groups

ICUG tables are implemented on network-wide basis and the same table is located
at each X.75 gateway. ICUG tables are configured at the NMTI and using the
MainStreetXpress 46020 Network Manager.
ICUG tables are located at each X.75 gateway and are used to map the internal
interlock code to the complete ICUG (DNIC or INIC plus international interlock
code). The international interlock code may be the same as the national interlock
code. An internal CUG call remains an X.75 CUG call and an internal CUGOA call
remains an X.75 CUGOA call.
For each ICUG, a specific network is designated as its ICUG administrator. It is that
network DNIC that is signalled in the first part of the ICUG; this DNIC may or may
not be the same as the DNIC in the CD address. Networks A, B, C and D all use ICUG
code X across internetwork X.75 links and may signal whatever they like internally.
For example, if DTEs in networks A, B and C are using ICUG X and the
administrating network for ICUG X is network C, then calls between DTEs in
networks A and B signal the X.75 ICUG X containing the DNIC of network C plus
the CUG interlock code.
ICUG signalling is the same for X.121 and E.164 addressing. X.75 has the concept of
an INIC for use in ICUGs administrated by an ISDN using E.164 addressing. An
INIC is always 4 digits consisting of 0 or 9 followed by the E.164 country code and
additional digits as needed allocated by the E.164 country or region.
Mode of operation
Three modes of operation are possible:
outgoing calls to X.75

incoming calls from X.75
transit X.75 calls
Outgoing calls to X.75
The internal CUG interlock code is signalled through the network to the X.75
gateway. Successful table lookup results in X.75 ICUG (DNIC + CUG code)
signalling in the utility field. Unsuccessful table lookup results in call clearing by the
X.75 gateway with a specific ICUG mapping-related diagnostic code.
28.1-6
(400)

NNP 95-2035-01-00-B

Incoming calls from X.75

The X.75 ICUG (DNIC + CUG code) is mapped onto an internal CUG interlock code.
If successful, the internal interlock code is signalled in the network to the CD DTE in
the facility field. Normal CUG checks are performed at the CD DTE. Unsuccessful
table lookup causes the call to be cleared.
Transit X.75 calls
Since the source X.75 gateway switch can determine that the destination address is
another X.75 network (based on the GAT), no ICUG utility processing is performed.
The packet is routed to the destination gateway, where the packet is transmitted to
the destination network. This allows the following scenario: networks A and C
support ICUG X, but network B does not. A call from a DTE in network A to a DTE
in network C is routed via network B. Since network B does not perform any ICUG
processing on transit calls, the call is allowed to proceed.
ICUG mapping tables

A network-wide ICUG table is configured at the NMTI. It contains the mapping
between 16 bit binary coded CUG codes and the 4 digit BCD-coded DNIC/INICs
plus the 16 bit binary coded CUG codes. The maximum number of ICUGs per ICUG
table when configured for an X.75 gateway of the X.25 FRE card is 1024. The
maximum number of ICUGs per ICUG table on the PE card is 2048. If an X.75
gateway on both X.25 FRE and PE cards are present in the network, the lower ICUG
capacity (1024) is applicable. Figure 28.1-3 shows the use of the ICUG mapping table.
(400)
28.1-7


NNP 95-2035-01-00-B
Figure 28.1-3: Use of the ICUG Mapping Table

CUG index = 7, nat.IC 3
nat.
IC
Network B
DNIC = 3160
ICUG
3110
400
3110
401
2440
1004
DTE 2
ICUG = 2440 1004
nat.
IC
ICUG
400
3110
400
401
3110
401
Network C
DNIC = 2440
Network D
DNIC = 3110
ICUG = 2440 1004
nat.
IC
ICUG
200
2440
1004
301
2160
30
350 3110
400
351 3110
401
DTE 1
Network A
DNIC = 2160
CUG index = 5, nat.IC 200

9163
DTE 1 in network A makes a CUG call to DTE 2 in network B. It uses CUG index 5,
which maps onto national interlock code 200. At the X.75 switch, the national
interlock code is mapped onto ICUG 2440 1004. That is, the ICUG is administrated
by network C, which has DNIC 2440. The call is routed via transit network D, which
does not support this ICUG. Since it is a transit network, it merely passes the call to
the next network. Network B maps the ICUG onto national interlock code 3. At the
destination switch, the national interlock code is mapped onto CUG index 7 of the
destination DTE link.
28.1.7
X.75 Accounting
By default, accounting records are generated for X.75. These records allow the
network manager to maintain records of all internetwork calls.
28.1-8
(400)

NNP 95-2035-01-00-B

For outgoing X.75 calls, accounting records are generated at the source switch. If
reverse charging applies, the accounting record is generated at the X.75 XAC of the
source network.
For incoming X.75 calls, accounting records are generated at the incoming X.75 XAC.
If reverse charging applies, the accounting record is generated at the destination
XAC.
For transit calls, accounting records are generated at the X.75 XAC where a
non-reverse charge call enters the network and at the X.75 XAC where a reverse
charge call exits the network.
The party to be charged is identified by the reverse charging field in the accounting
record. If the reverse charging field is not set, the calling DTE is charged, otherwise
the called DTE is charged.
Figure 28.1-4: Rules Governing the Generation of Accounting Records for X.75
DTE Y
DTE X
Switch
1
Switch
2
Switch
3
Switch
4
Network
B
Network
A
Switch Switch
5
6
Network
C
Call Direction
Call Direction
No reverse charge
Reverse charge
Incoming from DTEX

to Network A
Accounting records
generated at
Switch 1
Accounting records
generated at
Switch 2
Incoming from
Network B
to Network C
Accounting records
generated at
Switch 5
Accounting records
generated at
Switch 6
Incoming from
Network A
to Network B
Accounting records
Accounting records
generated at Switch 3. generated at Switch 4.
9438
28.1.8
Diagnostic Code Mapping

Diagnostic code mapping deals with the ability of a calling DTE to distinguish
between problems occurring at the gateway link and those occurring within the
remote network.
(400)
28.1-9


NNP 95-2035-01-00-B
If the Diagnostic Code Mapping parameter is set to Yes and the cause code for a
cleared call is Network Congestion, the calling DTE is informed whether the
problem occurred at the X.75 STE X/Y interface or within the remote network. If this
parameter is set to No, the calling DTE will not be able to distinguish between
problems occurring at the gateway link and those occurring within the remote
network.
Also, if this parameter is set to no, proprietary enhanced diagnostic codes are passed
across the STE X/Y interface for all cause code values. This is because it is expected
that diagnostic code mapping would only be disabled in cases where there is a
Newbridge to Newbridge equipment STE X/Y interface.
Diagnostic codes are mapped according to Table 28.1-1. For information on specific
diagnostic codes see Maintenance, chapter 37.1.
Table 28.1-1: Diagnostic Code Mapping for Clear Request Packet
28.1.9
Decimal Value Originally Generated
Decimal Value Passed
Same
1 to 111
114
112 to 127
Same
128 to 255
113
X.75 Gateway Service Configuration Overview

To set up the X.75 service:
1.
Set the GFR address in the GAT to that of the switch in the calling network.
2.
Set the address prefix in the GAT to the DNIC of the destination network.
3.
Set the XAC number in the GAT to that of the XAC linked to the destination
network.
4.
Set the service type for the gateway XAC to X.75 gateway or X.25 gateway.
5.
Configure the gateway NUA and set the service type to X.75 gateway or X.25
gateway.
It is important to note that only one NUA can be associated with a gateway link.
The NUA for the gateway XAC is only used to set up PVCs to the destination
network. The NUA must be an address that is reachable by call routing within
the calling network. It must not be prefixed with the DNIC of the destination
network because the internal call attempt will be treated as an X.75 call. For
example, supposing the calling network has a DNIC of 3220, and the called
network has a DNIC of 6550, the GAT entry would be an X.75 GW prefix of
6550. The NUA could have an internal address of 3220300001001 which is
reachable by normal X.25 call routing.
28.1-10
(400)

NNP 95-2035-01-00-B
28.1.10

6.
Set the LAPB address assignment parameter (01 or 03) to the opposite of the
setting in the destination network.
7.
Set the X.75 LCN selection parameter (ascending or descending) to the opposite
of the setting in the destination network.
8.
Set the TNIC/CNIC parameter for the link (it is normally the same as the DNIC
for the calling network).
9.
Set the other parameters as desired.
Summary of X.75 Configurable Parameters

The tables in this section summarize the X.75 configurable parameters.
Table 28.1-2: X.75 Link Layer Parameters
Parameter Name
Option or Range
Default
LAPB Address Assignment
03
01
03
Modulo 8
Modulo 128
Modulo 8
1 to 7 (Modulo 8)
1 to 127 (Modulo 128)
1 to 20
10
10 to 120 000 ms
increments of 10
3000 ms
0 to 3000 ms
increments of 10
200 ms
0 to 120 000 ms
increments of 10
60 000 ms
Congestion Timer
10 to 120 000 ms
increments of 10
3000 ms
Not configurable
None
(400)
28.1-11


NNP 95-2035-01-00-B
Table 28.1-3: X.75 Network Layer Parameters
28.1-12
Parameter Name
Option or Range
Default
Service Type
X.75 gateway
X.75
X75 LCN Selection
Ascending
Descending
Ascending
Version
1984/1988
1992/1996
1984/1988
Modulo 8
Modulo 128
Modulo 8
Base LCN
1 to 4095
Number of LCNs
1 to 4095
32
Number of PVCs
0 to 4095
0 to 4095
Two-way SVC
1 to 4095
32
0 to 4095
Restart Timer (T30)
0,1 to 500 s
180 s
Call Request Timer (T31)
0,1 to 500 s
200 s
Reset Timer (T32)
0,1 to 500 s
180 s
Clear Timer (T33)
0,1 to 500 s
180 s
Window Timer
0,1 to 500 s
Inactivity Timer
0,1 to 500 s
Flow Control Timer
1 to 180 s
Incoming Maximum address Length

Allowed
1 to 19
19
Default NPI
E.164 digital
E.164 analog
X.121
X.121
16 bytes
32 bytes
64 bytes
128 bytes
256 bytes
512 bytes
1024 bytes
2048 bytes
4096 bytes
128 bytes
256 bytes
512 bytes
Incoming Transit Calls Allowed
Yes or No
Yes
Basic
Extended
Basic
(400)

NNP 95-2035-01-00-B

Parameter Name
Option or Range
Default
Yes or No
Yes
Generate Alarms
Yes or No
Yes
Status Monitoring
Yes or No
Yes
Gateway TNIC/CNIC
4 BCD digits
None
Insert TNIC
Yes or No
Yes
Signal TNIC
Yes or No
Yes
Signal CNIC
Yes or No
Yes
Table 28.1-4: X.75 Address Translation Parameters
Parameter Name
Option or Range
Default
NPI (x, e, or m) and 1 to 19

digits in international
address format
None

address format
None
Translate Calling Address
Yes or No
No
Translate Called Address
Yes or No
No
Translate Incoming Packets
Yes or No
No
Translate Outgoing Packets
Yes or No
No
Yes or No
No
Yes or No
No
Yes or No
No
Yes or No
No
Trap Action: Clear Call
Yes or No
No
Trap Action: Cause Alarm
Yes or No
No
(400)
28.1-13


NNP 95-2035-01-00-B
Table 28.1-5: X.75 NUA Parameters
28.1-14
Parameter Name
Option or Range
Default

address format
None
1 to 512 for PE
1 to 128 for X.25 FRE
None
Yes or No
Yes
Signal CLAMN
Yes or No
Yes
Signal CRN
Yes or No
Yes
Yes or No
Yes
1 to 7 (Modulo 8)
1 to 127 (Modulo 128)
1 to 7 (Modulo 8)
1 to 127 (Modulo 128)
75 b/s to 2 Mb/s
64 kb/s
75 b/s to 2 Mb/s
64 kb/s
16 to 4096 bytes
128
16 to 4096 bytes
128
Outgoing Fast Select Allowed
Yes or No
No
Incoming Restricted Fast Select Allowed
Yes or No
No
Incoming Unrestricted Fast Select

Allowed
Yes or No
No
Yes or No
No
Yes or No
Yes
Yes or No
No
(400)

NNP 95-2035-01-00-B
28.2
28.2 X.75 XAC Parameters

X.75 XAC Parameters

This chapter provides an explanation of the X.75 link layer, network layer and
address translation parameters.
28.2.1
X.75 Access Circuit Configuration Overview

To configure X.75 XACs the following parameter groups must be configured:
28.2.2
link layer parameters

network layer parameters
address translation parameters
NUA parameters (see chapter 28.3)
X.75 Link Layer Parameters

There is no concept of a DCE/DTE interface on X.75 gateway links. Instead, the
Recommendation X.75 refers to STE X and STE Y. The station addresses to be used
are agreed bilaterally. If the LAPB address of one STE is 01, the LAPB address of the
STE in the opposite network must be 03.
Figure 28.2-1 shows the NMTI display for the X.75 link layer parameters.
(400)
28.2-1


NNP 95-2035-01-00-B
Figure 28.2-1: X.75 Link Layer Parameters Display

X25PE
Stations:5
P611-F1-01
OTTAWA:A2
Alarms:4
07-Feb-97
9:17:20A
LINK LAYER
--------------------LAPB Address Assignment
:01
:8
:7
Re-transmission Count (N2)
:10
:3000 ms
:200 ms
:6000 ms
Congestion Timer
:3000 ms
Maximum Information Frame Size(N1):259
CONFIG X25_ACCESS XAC 112 LINK_LAYER
F1-LAPB_ADDR
F6-
F2-SEQ_NUMBER
F7-
F3-WIN_SIZE
F8-CANCEL
F4-N2
F9-QUIT
F5-TIMERS
F10-PROCEED
To view X.75 link layer parameters

where
xac is an XAC with service type X.75
28.2.3
Configuring X.75 Link Layer Parameters

This section describes and provides configuration guidelines for the X.75 link layer
parameters.
LAPB Address Assignment

This parameter specifies the link layer address assignment of the X.75 STE.
If this parameter is set to 03, all command frames are transmitted using the 03 station
address and all responses are transmitted using the 01 station address. When
configuring this parameter, it is important that one end of the X.75 link is set to 01
and the other end be set to 03.
Options
03 and 01
28.2-2
(400)

NNP 95-2035-01-00-B

Default
03

This parameter specifies the link modulo used to control frame sequence numbers
for the X.75 link. Enter 8 for modulo 8 operation (normal), or 128 for modulo 128
operation (extended).
Options
Modulo 8
Modulo 128
Default
Modulo 8

This parameter specifies the maximum number of I-frames that can be outstanding
or unacknowledged on the X.75 link at any given time. Enter a number from 1 to 7 if
the Frame Sequence Numbering parameter is set to 8, or a number from 1 to 127 if it
is set to 128.
Ranges
1 to 7 (Modulo 8)
1 to 127 (Modulo 128)
Default
7

This parameter specifies the maximum number of attempts to complete a successful
transmission of a frame on the X.75 link.
Range
1 to 20
Default
10
(400)
28.2-3


NNP 95-2035-01-00-B

This parameter specifies the maximum amount of time that can elapse before a
window of frames, as specified by the Maximum Frame Window Size parameter,
must be acknowledged by the connected X.75 STE. If the frames are not
acknowledged within the T1 time period, the sender retransmits the frames. (The
number of retries is specified by the N2 parameter.)
Range
10 to 120 000 ms (increments of 10 ms)
Default
3000 ms

This parameter specifies the maximum amount of time the X.75 STE can wait before
generating a response or acknowledgment frame. This parameter is used to
encourage piggybacking of acknowledgments in data packets. The value of T2 must
be less than T1.
Range
0 to 3000 ms (increments of 10 ms)
Default
200 ms

This parameter specifies the time interval between the sending of RR frames on an
idle link (no I-frames). When this timer is enabled, the X.75 STE generates RR frames
every T3 ms. If there is no response, the X.75 link is taken down. When this timer is
disabled, there is no indication if the link goes down.
A value of 0 has the effect of turning the T3 timer off.
Range
0 to 120 000 ms (increments of 10 ms)
Default
60 000 ms
28.2-4
(400)

NNP 95-2035-01-00-B

Congestion Timer
This parameter specifies the maximum time to wait for a congested X.75 link to
become uncongested. This timer starts when the link transmit queue exceeds a
pre-determined threshold. If the timer expires before the transmit queue falls below
the threshold, the link is brought down. This prevents one link from using a
disproportionate amount of resources on the switch. Avoid setting this value too
small for links that experience bandwidth bottlenecks or large volumes of bursty
traffic.
Range
10 - 120 000 ms (increments of 10 ms)
Default
3000 ms

This field shows the maximum number of bytes in an information frame.This
non-configurable field displays the value of N1. It is derived from the highest
allowable packet size value.

Observe the following restrictions and interdependencies when configuring the link
layer parameters.
The value of T2 must be less than T1.

When you change the LAPB Address Assignment parameter for an active X.75 XAC,
the switch automatically disables and then re-enables the X.75 XAC to activate the
change. The switch clears all calls on the access line and the link restarts. The change
is effective once the link restarts.
Changing the value of the Inactivity Timer (T3) for an in-service link has the
following results.
When timer T3 is changed from 0 to some other value, the timer starts only when
the link is restarted or when a frame is sent or received over the link. For example,
if the remote STE is running an idle timer, timer T3 starts when the STE timer
expires and the STE transmits an RR frame.
When timer T3 is enabled (not 0) and the value is changed, the current timeout
value is allowed to expire before the new value takes effect. For example, if the
timer is set to 30 seconds and then changed to 1 second, the timer may take up to
30 seconds to expire before 1-second timeouts occur.
(400)
28.2-5


NNP 95-2035-01-00-B
You can change the values of all other link layer parameters at any time with no
To configure X.75 link layer parameters

LAPB_ADDR
SEQ_NUMBER
WIN_SIZE
N2
<01 or 03>
<seq_number>
<k>
<n2>
TIMERS
T1
<t1>
T2
T3
<t2> <t3>
CONGST_TMR
<congst_tmr>
SK000680
where
xac is a valid XAC with service type X.75
seq_number is 8* for sequence numbers 1 to 7 or 128 for sequence numbers 1 to 127
k is 1 to 7* if SEQ_NUMBER is set to 8, or 1 to 127 if it is set to 128
n2 is 1 to 20, 10*
t1 is 10 to 120 000 ms in multiples of 10 ms, 3000*
t2 is 0 to 3000 ms in multiples of 100 ms, 200*
t3 is 0 to 120 000 ms in multiples of 10 ms, 60 000*
congst_tmr is 10 to 120 000 ms in multiples of 10 ms, 3000*
* indicates the default
28.2-6
(400)

NNP 95-2035-01-00-B
28.2.4

X.75 Network Layer Parameters

X.75 network layer parameters differ from X.25 network layer parameters in the
following ways.
Each of the X.75 parameters are explained with respect to the STE X/Y interface
and do not apply the X.25 DTE/DCE interface.

The X.75 Logical Channel Number Selection parameter replaces the X.25 Packet
Layer Interface Type parameter.
The X.75 T30, T31, T32 and T33 timer parameters replace the X.25 T10/T20,
T11/T21, T12/T22 and T13/T23 timer parameters.
The following X.25 parameters do not apply to X.75:
The following X.75 parameters do not apply to X.25:
Status Monitoring
Gateway TNIC/CNIC
Insert TNIC
Signal TNIC
Signal CNIC
Figure 28.2-2 shows the NMTI display for the X.75 network layer parameters.
(400)
28.2-7


NNP 95-2035-01-00-B
Figure 28.2-2: X.75 Network Layer Parameters Display

X25PE
Stations:5
P611-F1-01
OTTAWA:A2
Alarms:4
07-Feb-97
9:17:20A
NETWORK LAYER
------------------------Service Type
:X.75 Gateway
X.75 LCN Selection
:ASCENDING
Version
:1984/1988
:8
Packet Layer Restart Timer (T30) :180 s
Base LCN
:1
Packet Layer Call Timer (T31)
:200 s
Number of LCNs
:32
Reset Timer (T32)
:180 s
Number of PVCs
:0
Clear Timer (T33)
:180 s
Number of Incoming SVCs :0
Window Timer
:60 s
(Two Way SVCs)
:32
Inactivity Timer
:180 s
Number of Outgoing SVCs :0
Flow Control Timer
:1 s
CONFIG X25_ACCESS XAC NET_LAYER

F1-SERVICE
F2-X75_INTF
F6-ADDRESSING
F7-MORE
F3-SEQ_NUMBER
F8-CANCEL
F4-LCN_ALLOC
F9-QUIT
F5-TIMERS
F10-
To view X.75 network layer parameters

where
xac is an XAC with service type X.75
28.2.5
Configuring X.75 Network Layer Parameters

This section describes and provides configuration guidelines for the X.75 network
layer parameters.
Service Type
The service type specifies the type of service with which the XAC is associated. For
an XAC to be used in X.75 gateway service, the service type parameter must be set
to X.75 gateway.
frame stream-DLCI.
You cannot change the service type if there are any NUAs attached to the X.75 XAC
that are members of hunt groups or that have PVCs defined.
28.2-8
(400)

NNP 95-2035-01-00-B

Options
X.75 Gateway
Default
None
X.75 Logical Channel Number Selection

This parameter determines whether LCNs are selected in ascending or descending
order.
The setting of this parameter must be coordinated with the LCN selection parameter
setting of the adjacent network, such that the connected X.75 STE is assigned the
opposite option. That is, if STE-X is assigned the option Ascending, then STE-Y must
be assigned the option Descending. This ensures that each X.75 STE selects the next
free LCN from the opposite end of the LCN range.
Options
Ascending or Descending
Default
Ascending
Version
This parameter specifies the version of the ITU-T Recommendation X.75 service
supported by the X.75 STE. The difference in operation between the two options is
the control of the X.75 utility field length. In the 1984 and 1988 versions, the utility
field is a maximum of 63 bytes in length. In the 1992 and 1996 versions, an overall
maximum packet length applies with no maximum utility field length.
Options
1984/1988 or 1992/1996
Default
1984/1988

This parameter specifies the packet modulo used to control packet sequence
numbers on the X.75 STE X/Y interface. Enter 8 for modulo 8 operation (normal), or
128 for modulo 128 operation (extended). X.75 XACs assigned modulo 128 also
support modulo 8. The internal virtual circuit, rather than the interface, determines
the type of sequencing to use. A call is cleared if the called and calling DTEs or X.75
interfaces are incompatible, and it is a D-bit call.
(400)
28.2-9


NNP 95-2035-01-00-B
The Packet Sequence Numbering value configured for an X.75 XAC must be greater
than the Default Send Window Size and Default Receive Window Size values for
SVCs and PVCs associated with the X.75 XAC. For example, if an X.75 XAC uses
modulo 8 sequencing, then any SVC assigned to that X.75 XAC is restricted to
default send and receive window sizes of 1 to 7.
For an active X.75 XAC, you cannot change the value from 128 to 8 if SVCs or PVCs
associated with the X.75 XAC have default send and receive window size values of
greater than 7.
Options
Modulo 8 or Modulo 128
Default
Modulo 8
Base LCN
This parameter specifies the LCN of the first logical channel supported on the X.75
interface.
Range
1 to 4095
Default
1
Number of LCNs
This parameter specifies the total number of logical channels supported on the
interface. This value must be greater than or equal to the number of PVCs + the
number of incoming SVCs + the number of outgoing SVCs.
Range
1 to 4095
Default
32
Number of PVCs
PVCs. The number of PVCs + the number of incoming SVCs + the number of
outgoing SVCs must be less than or equal to the number of LCNs.
28.2-10
(400)

NNP 95-2035-01-00-B

Range
0 to 4095
Default
0

outgoing SVCs. The number of outgoing SVCs + the number of incoming SVCs + the
number of PVCs must be less than or equal to the number of LCNs.
Outgoing SVCs can be assigned to provide the One-way Logical Channel Outgoing
facility as defined in Recommendation X.25, for use at the X.75 interface.
Range
0 to 4095
Default
0
Two-way SVCs
This parameter specifies the number of logical channels on the X.75 interface that
support both incoming and outgoing SVCs. This parameter is not directly
configurable; the value is determined as follows:
n = LCNs (PVCs + SVCsout + SVCsin)
where
n is Number of Two-way SVCs
LCNs is Number of LCNs
PVCs is Number of PVCs
SVCsout is Number of Outgoing SVCs
SVCsin is Number of Incoming SVCs
(400)
28.2-11


NNP 95-2035-01-00-B
Note
The most common arrangement for logical channels at an X.75 STE X/Y interface is
for all LCNs to be two-way SVCs, with a range of LCNs assigned for IPVCs, if the
two networks agree to support inter-network PVCs.
Range
1 to 4095
Default
32

incoming SVCs. The number of incoming SVCs + the number of outgoing SVCs +
the number of PVCs must be less than or equal to the number of LCNs.
Incoming SVCs can be assigned to provide the One-way Logical Channel Incoming
facility as defined in Recommendation X.25, for use at the X.75 interface.
Range
0 to 4095
Default
0
Restart Timer (T30)

This parameter specifies the maximum time the X.75 STE waits for an X.75 restart
request packet.
This parameter is the same as the Restart Timer for X.25, except that the X.75 timer
number is T30.
Enter 0 to disable this timer.
Range
0 or 1 to 500 seconds
Default
180 seconds
28.2-12
(400)

NNP 95-2035-01-00-B


This parameter specifies the maximum time the X.75 STE will wait for a response to
an X.75 Call Request packet.
This parameter is the same as the Call Timer for X.25, except that the X.75 timer
number is T31.
Range
Default
200 seconds
Reset Timer (T32)

This parameter specifies the maximum time the X.75 STE waits for a response to an
X.75 Reset Request packet.
This parameter is the same as the Reset Timer for X.25, except that the X.75 timer
number is T32.
Range
Default
180 seconds
Clear Timer (T33)

This parameter specifies the maximum time the X.75 STE waits for a response to an
X.75 Clear Request packet.
This parameter is the same as the Clear Timer for X.25, except that the X.75 timer
number is T33.
Range
(400)
28.2-13


NNP 95-2035-01-00-B
Default
180 seconds
Window Timer (T24)

This parameter controls the sending of RR acknowledgment packets to an STE. If the
timer is set to zero, the switch sends an RR packet for every data packet received. If
the timer is set to a non-zero value, the switch sends an RR packet either if the
window timer expires or a half window of unacknowledged data packets is
received.
Acknowledgments are also sent when data packets are transmitted with a
piggybacked P(R).
The window timer is started or restarted every time a data packet is received and
stopped when a RR or piggybacked P(R) acknowledges all data packets received.
During flow control conditions, the switch stops acknowledging received data
packets in order to try to close the packet window. This is done by holding off RR
packets and transmitting data packets with the P(R) set to that used in the last RR
packet transmitted.
Range
Default
60 seconds
Inactivity Timer
The network layer inactivity timer starts when the transmit queue is full and stops
when the transmit window opens. When the timer expires, the virtual circuit is reset,
thereby preventing deadlock on the virtual circuit. The default (0) disables this
timer.
Range
Default
0 seconds
28.2-14
(400)

NNP 95-2035-01-00-B

Flow Control Timer

The flow control timer is used when the X.75 STE enters the flow control state. This
occurs if:
memory resources drop below a preset lower threshold

the transmit queue size is greater than 2 and one of the following conditions is
met:
the X.75 packet window is closed

a X.75 packet layer RNR is received
the X.75 link layer is in the flow control state
The flow control timer starts when a complete data packet is received from the X.75
interface and the switch is in flow control state. The X.75 STE responds by
withholding RRs on the X.75 interface, and piggybacking the previous P(R) rather
than the current P(R). Under flow control conditions, the X.75 STE avoids sending
RNRs whenever possible. The X.75 STE send RNRs only if the transmit queue
exceeds n, where n is based on the configured X.75 throughput class values.
When the timer expires, the X.75 STE checks the available resources. If the buffers
are above the upper threshold, the X.75 STE sends an RR if an RNR was not received
from the other end of the X.75 interface, and exits flow control. If the buffers are still
below the upper threshold when the timer expires, the X.75 STE restarts the timer.
Range
1 to 180 seconds
Default
1 second

The Incoming Maximum Address Length Allowed applies to addresses in an X.75
Call Request packet. In the case of an X.75 Call Request received by the X.75 STE, the
internal translated calling address length is checked against the Maximum Address
Length Allowed parameter. If the check fails the call is cleared with diagnostic
invalid calling address.
In the case of an X.75 Call Request sent by the X.75 STE, the internal translated called
address length is checked against the Maximum Address Length Allowed
parameter. If the check fails the call is cleared with diagnostic invalid called
address.This parameter is used to control the maximum called address length
signalled in X.75 Call Request packet from the X.75 STE.
Range
1 to 19
(400)
28.2-15


NNP 95-2035-01-00-B
Default
19
Default NPI
This parameter specifies the default NPI value applicable to the X.75 STE, if the
TOA/NPI address format is not used.
The setting of this parameter must be the same as that of the connected X.75 STE. The
default value (X.121) applies when both X.75 STEs are in public data networks
according to ITU-T Recommendation X.75.
Options
E.164 digital
E.164 analog
X.121
Default
X.121

This parameter specifies the packet sizes supported by the X.75 interface. The
maximum packet size determines the value of the X.75 LAPB Maximum Frame
Length (N1) parameter.
The allowable packet sizes configured for an X.75 XAC must include the Default
Send Packet Size and Default Receive Packet Size values for NUAs and PVCs
associated with the X.75 STE. For example, if an X.75 XAC uses the default allowable
packet sizes (128, 256 and 512), then any NUA assigned to that X.75 XAC is restricted
to default send and receive packet sizes of 128, 256 and 512.
For an active X.75 XAC, you cannot remove allowable packet sizes that are used by
NUAs or PVCs associated with the X.75 XAC.
Options
16, 32, 64, 128, 256, 512, 1024, 2048, 4096 bytes
Default
128, 256, 512 bytes
28.2-16
(400)

NNP 95-2035-01-00-B


If this parameter is set to No for an X.75 XAC, then incoming transit X.75 calls
arriving at the X.75 XAC are cleared. Outgoing transit X.75 calls are still allowed on
the X.75 XAC. If this parameter is set to Yes, incoming and outgoing transit calls are
allowed on the X.75 XAC.
Options
Yes or No
Default
Yes

This parameter specifies the format of the Throughput Class Negotiation facility
signalled in both directions at the X.75 STE X/Y interface. Enter Extended to permit
the X.75 STE to explicitly negotiate throughput class values higher than 192 000 b/s.
Options
Basic or Extended
Default
Basic

This parameter may be used to disable mapping of diagnostic codes for clear
requests, which are not generated at the local STE X/Y interface and have a cause
code that indicates Network Congestion as specified in Table 28.1-1.
If this parameter is set to Yes and the cause code for a cleared call is Network
Congestion, the calling DTE is informed whether the problem occurred at the X.75
STE X/Y interface or within the remote network. If this parameter is set to No, the
calling DTE will not be able to distinguish between problems occurring at the
gateway link and those occurring within the remote network. Also, if this parameter
is set to No, proprietary enhanced diagnostic codes are passed across the STE X/Y
interface for all cause code values. This is because it is expected that diagnostic code
mapping would only be disabled in cases where there is a Newbridge-to-Newbridge
equipment STE X/Y interface.
Options
Yes or No
(400)
28.2-17


NNP 95-2035-01-00-B
Default
Yes
Generate Alarms
This parameter specifies whether the switch generates alarms for this X.75 STE to
indicate that the link layer or network layer is down.
Options
Yes or No
Default
Yes
Status Monitoring
If this parameter is set to Yes, the MainStreetXpress 46020 Network Manager is
notified as to whether or not the X.75 gateway is in operation. If this parameter is set
to No, the MainStreetXpress 46020 Network Manager is not notified as to whether
or not the X.75 gateway is in operation.
Options
Yes or No
Default
Yes
Gateway TNIC/CNIC
This parameter contains the TNIC/CNIC value associated with this X.75 STE and is
inserted, if not prohibited by the parameters controlling the insertion and signalling.
Options
4 BCD digits
Default
None
28.2-18
(400)

NNP 95-2035-01-00-B

Insert TNIC
This parameter controls whether a TNIC value is inserted in an X.75 call request
signalled by the X.75 STE link. TNIC insertion only occurs for transit X.75 calls,
which is when the call enters and exits the network via X.75 interfaces. When set to
Yes, the TNIC value is inserted if it is not already present (duplicate TNIC values are
not allowed). This method of TNIC insertion control is relevant to cases involving
network migration when there are two parallel networks sharing the same TNIC
value and interconnected by X.75.
Options
Yes or No
Default
Yes
Signal TNIC
This parameter controls whether or not any TNICs are signalled in an X.75 call
request, call connect or clear request transmitted by the X.75 STE. This option is
useful for the unusual case where X.75 is used to connect public and private
networks and no TNICs are to be signalled to the private network.
Options
Yes or No
Default
Yes
Signal CNIC
Since the support of a CNIC is optional, this parameter is used to control whether
the X.75 STE signals a CNIC utility in a Clear Request packet so that it is not sent to
an adjacent network that does not support it.
Options
Yes or No
Default
Yes
(400)
28.2-19


NNP 95-2035-01-00-B

Observe the following restrictions and interdependencies when configuring
Gateway TNIC/CNIC
You cannot attach an NUA if the Gateway TNIC/CNIC is not configured and at least
one of Insert TNIC, Signal TNIC or Signal CNIC are set to Yes.
Insert TNIC/Signal TNIC
You cannot configure Insert TNIC to Yes if Signal TNIC is set to No.
Service Type
frame stream-DLCI.
You cannot change the service type if there are any NUAs attached to the X.75 XAC
that are members of hunt groups or that have PVCs defined.
The maximum value for the Allowable Packet Sizes parameter must be equal to or
less than the value of the Maximum X.25 Packet Size configured for the
ENCAP_CCT, if an encapsulated circuit is used for link access.
The allowable packet sizes configured for an X.75 XAC must include the Default
Send Packet Size and Default Receive Packet Size values for the NUA and PVCs
associated with the X.75 XAC. For an active X.75 XAC, you cannot remove allowable
packet sizes that are used by the NUA or PVCs associated with the XAC.
The Packet Sequence Numbering value configured for an X.75 XAC must be greater
than the Default Send Window Size and Default Receive Window Size values for the
NUA and PVCs associated with the X.75 XAC. For an active X.75 XAC, you cannot
change the value from 128 to 8 if the NUA or PVCs associated with the X.75 XAC
have default send or receive window size values of greater than 7.

Before you can change the Service Type parameter, you must disconnect the XAC
from the direct circuit or frame stream-DLCI.
When the last X.75 XAC is changed to another service type all ICUGs are
automatically deleted.
28.2-20
(400)

NNP 95-2035-01-00-B

When you change the following network layer parameters for an active XAC, the
switch automatically disables and immediately re-enables the XAC to activate the
change. The switch clears all calls on the access line and restarts the link. The changes
are effective once the link restarts.
X.75 LCN Selection

Base LCN
Number of LCNs
Number of PVCs
Number of Two-way SVCs

X.25 Version
Default NPI
Status Monitoring
Insert TNIC
Signal TNIC
TNIC/CNIC
Restart Timer (T30)

Reset Timer (T32)
Clear Timer (T33)
Inactivity Timer
Flow Control Timer
Window Timer
Generate Alarms
Signal CNIC
(400)
28.2-21


NNP 95-2035-01-00-B
To configure X.75 network layer parameters

SERVICE
X75_INTF
SEQ_NUMBER LCN_ALLOC
ADDRESSING
MORE
<seq_number>
X75_GATEW
VERSION
LCN_SELECT
<version>
ASCEND/DESCEND
BASE_LCN
TIMERS
NUM_LCN
NUM_PVC
NUM_O_SVC
NUM_I_SVC
<number>
T30RST
T31CALL
T32RES
T33CLR
<seconds>
<seconds>
<seconds>
<seconds>
<seconds>
INACTIVITY
FLOW_CNTL
<seconds>
<seconds>
MAX_LENGTH
<max_length>
PACKETS
ADD
MORE
DEF_NPI
X121
E164_DIG
E164_AN
NEGOTIATE
CAUSE_CODE
TPUT_FORMT
DIAGNOSTIC
ALARMS
EVENT_MON
BASIC/EXTENDED
YES/NO
YES/NO
YES/NO
REMOVE
<pkt_size>
WIN_TIMER
REPORTS
X75_OPTION
X75CALLS
TNIC_CNIC
INSERT_TNIC
SIGNAL_TNIC
SIGNAL_CNIC
YES/NO
<tnic or cnic>
YES/NO
YES/NO
YES/NO
SK000681
28.2-22
(400)

NNP 95-2035-01-00-B

where
xac is a valid XAC with service type X.75
version is the version of X.75 protocol (1984/1988* or 1992/1996)
seq_number is 8* for modulo 8 (normal) or 128 for modulo 128 (extended) operation
tnic or cnic is 0000 to 9999
number is 1 to 4095, 32* for NUM_LCN
seconds is 1 to 180 for the flow control timer (1*), and 1 to 630 for all other timers
max_length is 1 to 19* digits
pkt_size is one or more of the values 16, 32, 64, 128*, 256*, 512*, 1024, 2048, or 4096
* is the default
28.2.6
Configuring X.75 Address Translation Parameters

This section describes and provides configuration guidelines for the X.75 address
translation parameters.

This parameter specifies the external translation prefix string for this Address
Translation Table entry. When calls match the direction criteria, addresses signalled
from an X.75 interface are compared to the external translation prefixes in the
address translation table. If a match occurs, the addresses are translated by replacing
the digits in the address that match the external translation prefix string with the
corresponding internal translation prefix digits (if any).
Range
Default
ix

This parameter specifies the internal translation prefix string for this Address
Translation Table entry. When calls match the direction criteria, addresses signalled
to an X.75 interface are compared to the internal translation prefixes in the table. If a
match occurs, the addresses are translated by replacing the digits in the address that
match the internal translation prefix string with the corresponding external
translation prefix digits (if any).
Range
(400)
28.2-23


NNP 95-2035-01-00-B
Default
ix
Translate Calling Address

The X.75 calling address is in international format, and as such it conforms to the
internal format used in the Newbridge network; therefore, translation is only likely
to be required for access control, which is the exception, not the rule. As a result
translation is not performed by default.
Options
Yes or No
Default
No
Translate Called Address

The X.75 called address is in international format, and as such it conforms to the
internal format used in the Newbridge network; therefore, translation is only likely
to be required for access control, which is the exception, not the rule. As a result
translation is not performed by default.
Options
Yes or No
Default
No
Translate Incoming Packets

This option controls whether or not address translation is applied to call set-up and
clearing packets received by the X.75 STE from the X.75 interface.
Options
Yes or No
Default
No
28.2-24
(400)

NNP 95-2035-01-00-B

Translate Outgoing Packets

This option controls whether or not address translation is applied to call set-up and
clearing packets transmitted by the X.75 STE from the X.75 interface.
Options
Yes or No
Default
No

received from or sent to an X.75 interface matches the corresponding External
this parameter.
Options
Yes or No
Default
No

This parameter specifies whether to take screening action when a called address
received from or sent to an X.75 interface matches the corresponding External
this parameter.
Options
Yes or No
Default
No
(400)
28.2-25


NNP 95-2035-01-00-B

sent to an X.75 interface matches the corresponding Internal Translation Prefix
string. When this parameter is set to Yes and a match occurs, the call is trapped and
treated according to the action specified by the Trap Action parameters. The
Direction and Which Address parameters affect the operation of this parameter.
Note
Calling addresses received from an X.75 interface are generally not translated, and
cannot be trapped.
Options
Yes or No
Default
No

This parameter specifies whether to take screening action when a called address sent
to or received from an X.75 interface matches the corresponding Internal Translation
Prefix string. When this parameter is set to Yes and a match occurs, the call is
trapped and treated according to the action specified by the Trap Action parameters.
The Direction and Which Address parameters affect the operation of this parameter.
Options
Yes or No
Default
No
Trap Action: Clear Call

This parameter specifies whether the switch clears the X.75 call when a trap occurs.
If any of the screening parameters are set to Yes, either this parameter or the Trap
Action Cause Alarm parameter must be set to Yes. If all the screening parameters are
set to No, this parameter is automatically set to No and cannot be set to Yes.
Options
Yes or No
28.2-26
(400)

NNP 95-2035-01-00-B

Default
No


To configure X.75 address translation parameters

CONFIG X25_ACCESS XAC <xac> NET_LAYER MORE TRANSLATE
<entry_no.>
EXT_PREFIX INT_PREFIX DIRECTION WHICH_ADDR SCREENING

<addr_prefix>
MORE
TRAP_ACTN
<addr_prefix>
INCOMING OUTGOING
NEW_ENTRY
CLEAR_CALL ALARM
BOTH
YES/NO
CALLING
TRP_INC_CD
CALLED
BOTH
TRP_INC_CG
TRP_OUT_CD TRP_OUT_CG
YES/NO
SK000423
where
xac is 1 to 128 for X.25 FRE cards or 1 to 512 for PE cards
entry_no. is an address translation table entry number (1 to 256)
addr_prefix is the translation prefix string (i or n, x, e, or m, and 0 to 19 digits or wildcard characters [?])
(400)
28.2-27

NNP 95-2035-01-00-B
28.3
28.3 X.75 NUA Parameters

X.75 NUA Parameters

This chapter provides an explanation for the X.75 NUA parameters.
28.3.1
Understanding NUAs
For an explanation of NUAs, see chapter 27.15.
The NUA of an X.75 gateway link is the remote address for an IPVC. That is, it is not
the DNIC of the remote network that is configured as the remote address. The use of
the NUA allows one to specify the link to use on the IPVC in the case where multiple
links support the same address prefixes.
28.3.2
Viewing X.75 NUA Parameters

Figure 28.3-1 shows the NMTI display for the X.75 NUA parameters.
Figure 28.3-1: NUA Parameters Display
X25PE
Stations:5
P611-F1-01
OTTAWA:A2
Alarms:4
07-Feb-97
9:17:20A
NUA SUBSCRIPTION OPTIONS

-------------------------------------Network User Address
XAC Service Type
User Defined Data
:x3011888866
:--:--:
:Yes
CONFIG X25_ACCESS NUA x302011888866

Select the XAC service type.
F1-X25
F2-X75_GATEW
F6-TRAFFC_GEN
F7-
(400)
F3-NUI
F8-
(default)
F4-COLLECTOR
F9-
F5-XFR
F10-
28.3-1


NNP 95-2035-01-00-B
To view X.75 NUA parameters

where address is the NPI and 1 to 19 digits in X.121 or E.164 address format
28.3.3
Configuring X.75 NUA Parameters

This section describes and provides configuration guidelines for the X.75 NUA
parameters.

This parameter specifies a valid X.121 or E.164 address that is unique in the network.
Before you can define an NUA, you must ensure that the GAT entries for the switch
contain an address prefix that corresponds to the NUA. See chapter 27.7 for
information about configuring the GAT.
You define NUAs by specifying the NPI and entering the address in international
format.
0 or 9.
Range
Default
None

This parameter specifies the X.75 XAC to which the NUA is assigned. The NUA
cannot already be assigned to an X.75 XAC. An X.75 XAC can have no more than one
NUA assigned to it.
When you assign an X.75 XAC its NUA, the X.75 XAC becomes active; if the X.75
XAC is connected to a frame stream-DLCI or direct circuit, the access line goes in
service.
28.3-2
(400)

NNP 95-2035-01-00-B

If an NUA is moved from one XAC to another of the same service type, the NUA is
automatically deleted from the current XAC and added to the new XAC.
It is not possible to delete the NUA assigned as the Default NUA, nor is it possible
to move to another XAC, unless it is the only XAC.
Range
1 to 512
Default
None
Accounting is activated by default, since accounting records are always generated
for X.75 calls. This parameter applies to transit calls and call attempts at the X.75
interface. Accounting records are generated at the source and destination switches
in the case of other X.75 calls.
Options
Yes or No
Default
Yes
Signal CLAMN
This parameter specifies whether to signal the Called Line Address Modification
Notification utility across the X.75 interface in the Call Connected or Clear Request
packets when a call is redirected. This utility indicates to the calling network why
the called address is different from the one originally signalled by the network.
If this option is set to Yes, the CLAMN utility will be signalled. If this option is set to
No, the CLAMN utility will be omitted from the Call Connected and Clear Request
packets.
Options
Yes or No
Default
Yes
(400)
28.3-3


NNP 95-2035-01-00-B
Signal CRN
Incoming calls that signal the CRN utility are cleared. If redirection occurs within the
Newbridge network and the call is redirected to an X.75 Gateway, then the CRN is
not inserted, but the call is allowed to leave the network.
Options
Yes or No
Default
Yes

This parameter specifies whether the X.75 STE may transmit Call Requests, which
contain the reverse charging utility, to the X.75 interface.
If the parameter is set to No, calls that include the reverse charging utility will be
cleared by the X.75 STE.
Options
Yes or No
Default
Yes

This parameter specifies the maximum number of packets that can be received from
the X.75 STE to the X.75 interface before an acknowledgment is received. This value
is used in the absence of the Window Size Negotiation utility.
configured for the X.75 XAC.
Range
1 to 7 (Modulo 8)
1 to 127 (Modulo 128)
Default
2
28.3-4
(400)

NNP 95-2035-01-00-B


This parameter specifies the maximum number of packets that can be transmitted by
the X.75 STE from the X.75 interface before an acknowledgment is received. This
value is used in the absence of the Window Size Negotiation utility.
configured for the X.75 XAC.
Range
1 to 7 (Modulo 8)
1 to 127 (Modulo 128)
Default
2

received from the X.75 STE to the X.75 STE interface. This value is used in the
absence of the Throughput Class Negotiation facility; however, when an X.75 STE
inserts the Throughput Class Negotiation facility, the proposed values must be less
than the default values.
Values greater than 192 000 b/s are permitted only when the Throughput Class
Negotiation Format parameter is set to Extended.
Options
75, 150, 300, 600, 1200, 2400, 4800, 9600, 19 200, 48 000, 64 000, 128 000, 192 000,
256 000, 320 000, 384 000, 448 000, 512 000, 576 000, 640 000, 704 000, 768 000, 832 000,
896 000, 960 000, 1 024 000, 1 088 000, 1 152 000, 1 216 000, 1 280 000, 1 344 000,
1 408 000, 1 472 000, 1 536 000, 1 600 000, 1 728 000, 1 792 000, 1 856 000, 1 920 000,
1 984 000, 2 048 000 b/s
Default
64 000 b/s

transmitted from the X.75 STE to the X.75 STE interface. This value is used in the
absence of the Throughput Class Negotiation facility. When an X.75 STE inserts the
Throughput Class Negotiation facility, the proposed values must be less than the
default values. Values greater than 192 000 b/s are permitted only when the
Throughput Class Negotiation Format parameter is set to Extended.
(400)
28.3-5


NNP 95-2035-01-00-B
Options
75, 150, 300, 600, 1200, 2400, 4800, 9600, 19 200, 48 000, 64 000, 128 000, 192 000,
256 000, 320 000, 384 000, 448 000, 512 000, 576 000, 640 000, 704 000, 768 000, 832 000,
896 000, 960 000, 1 024 000, 1 088 000, 1 152 000, 1 216 000, 1 280 000, 1 344 000,
1 408 000, 1 472 000, 1 536 000, 1 600 000, 1 728 000, 1 792 000, 1 856 000, 1 920 000,
1 984 000, 2 048 000 b/s
Default
64 000 b/s

This parameter is used in a Call Request or Call Connected packet to indicate the
packet sizes applicable to the call when no packet size request was received.
Range
16, 32, 64, 128, 256, 512, 1024, 2048, or 4096 bytes
Default
128 bytes

This parameter is used in a Call Request or Call Connected packet to indicate the
packet sizes applicable to the call when no packet size request was received.
Range
16, 32, 64, 128, 256, 512, 1024, 2048, or 4096 bytes
Default
128 bytes
Outgoing Fast Select Allowed

This parameter specifies whether the X.75 STE may transmit to the connected X.75
STE, Call Requests that include a fast select utility and a user data field of up to 128
octets. The default (No) restricts the X.75 STE from transmitting Call Requests that
include the fast select utility.
Options
Yes or No
28.3-6
(400)

NNP 95-2035-01-00-B

Default
No

This parameter specifies whether the X.75 STE may receive Call Requests that
include a restricted fast select utility from the connected X.75 STE. The only valid
response from the X.75 STE is a Clear Request with a user data field of up to 128
octets.
The default (No) restricts the X.75 STE from receiving Call Requests containing the
restricted fast select utility.
Options
Yes or No
Default
No
Incoming Unrestricted Fast Select Allowed

This parameter specifies whether the X.75 STE may receive Call Requests that
include an unrestricted fast select utility from the connected X.75 STE. Valid
responses from the X.75 STE are a Call Connected packet or a Clear Request packet
with a user data field of up to 128 octets in either packet.
The default (No) restricts the X.75 STE from receiving Call Requests containing the
unrestricted fast select utility.
Options
Yes or No
Default
No

This parameter specifies whether the TOA/NPI Address Subscription facility is
enabled for the X.75 interface. When this facility is enabled, all call setup and
clearing packets in both directions must use the TOA/NPI address format. The
TOA/NPI address format accommodates addresses whose length is greater than 15
digits and contains fields that specify the TOA and NPI.
This parameter must be set in agreement with the adjacent network to the same
value at both X.75 STEs, since it applies to all call setup and clearing packets.
(400)
28.3-7


NNP 95-2035-01-00-B
Options
Yes or No
Default
No
Clear On Calling Address Failure

This parameter specifies whether the switch clears a call when the calling address
cannot be converted because the X.75 STE does not subscribe to the TOA/NPI
address format and the address is too long. If the calling address is too long and this
parameter is set to No, the calling address is omitted.
Options
Yes or No
Default
Yes

for the X.75 internetwork PVCs. The frequency of the periodic records is determined
by the switch-wide accounting parameters rather than the NUA accounting
parameters.
Options
Yes or No
Default
No

For NUAs and PVCs, accounting activation cannot be set to No if periodic
accounting activation or charging information subscription is set to Yes. Nor can
accounting activation be set to Yes if periodic accounting activation or charging
information subscription is set to No.
There can only be one NUA attached to an XAC with a service type of X.75 Gateway.
For an XAC of service type X.75, it is not possible to attach an NUA if the Gateway
TNIC/CNIC is not configured and at least one of Insert TNIC, Signal TNIC or Signal
CNIC are set to Yes.
28.3-8
(400)

NNP 95-2035-01-00-B

It is not possible to delete the NUA assigned as the Default NUA, nor is it possible
to move to another XAC, unless it is the only XAC.
You cannot change an address after the NUA is assigned to an XAC. You must delete
the NUA, redefine the address, and assign it to the XAC.
NUAs cannot exist in the database unless they are assigned to XACs. You cannot
define a block of NUAs and assign them at a later date.
An NUA cannot be a hunt group address or hunt group redirection address.
Default Throughput Class values greater than 192 000 b/s are permitted only when
the Throughput Class Negotiation Format parameter is set to Extended. See
section 27.14.8.
The values of the default send and receive packet size parameters must match one
of the allowable packet sizes configured for the XAC to which the NUA is assigned.
The values of the default send and receive window size parameters must be less than
the Packet Sequence Numbering value configured for the XAC to which the NUA is
assigned.

If an NUA is moved from one XAC to another of the same service type, the NUA is
automatically deleted from the current XAC and added to the new XAC.
Except for the Network User Address parameter, you can change the values of the
NUA parameters at any time with no disruption of service. The changes are effective
for the next call.
(400)
28.3-9


NNP 95-2035-01-00-B
To configure X.75 NUA parameters

CONFIG X25_ACCESS NUA <address> X75_GATEW
SUBS_OPT
CHARGING
ADDRESSING
REV_ACCEPT
REDIRECTN
SIG_CRN
YES/NO
SIG_CLAMN
YES/NO
TOA_NPI
CL_ON_FAIL
YES/NO
DEFAULTS
MORE
THRU_PUT
WIN_SIZE
RECV
PKT_SIZE
SEND
RECV
SEND
ACCOUNTING
<thru_put>
<win_size>
RECV
SEND
ACTIVATE
PERIODIC
HOT_BILLING
YES/NO
<pkt_size>
SK000679
where
address is the NUA
pkt_size is 16, 32, 64, ... , 4096 bytes
win_size is 1 to 7 for Modulo 7 and 1 to 127 for Modulo 128
thru_put is 75, 150, ... , 2048000 b/s
28.3-10
(400)

NNP 95-2035-01-00-B
29. BRI S/T Cards

NNP 95-2035-01-00-B
29.1
29.1 Understanding BRI S/T Card Configuration

Understanding BRI S/T Card

Configuration
This chapter introduces the BRI S/T card and provides a summary of the
configuration procedures.
29.1.1
Understanding BRI S/T Cards

The BRI S/T card provides basic rate termination in ISDN networks.
ISDN basics
The ISDN recommendations and standards published by the ITU-T standardize the
transport of digital voice and data over a digital network. Figure 29.1-1 illustrates the
reference model for basic rate access to the ISDN network. ISDN-compatible devices
can be connected directly to the network through a standard interface at an access
point known as the S/T interface. Equipment that is not ISDN compatible must be
connected to a TA designed specifically for that equipment, which converts its
transmission format to an ISDN-compatible format at the S/T interface.
Figure 29.1-1: Basic ISDN Reference Model
Analog
telephone
TA
Customer
premises
Non-ISDN
computer
G3
FAX
ISDN
telephone
ISDNcompatible
computer
TA
TA
Network
equipment
NT1
U
interface
ISDN
Network
S
6888
BRI S/T Cards
(400)
29.1-1


NNP 95-2035-01-00-B
At the end of the subscriber loop, the S/T interface provides line termination for the
customer devices. In Europe and Japan, the S/T interface connects directly to the
ISDN network. In North America, the NT1 provides a further interface between the
S/T reference point and the network. The reference point on the network side of the
NT1 is called the U interface.
ISDN application
The ISDN application differs slightly from the basic model. Figure 29.1-2 shows a
typical application, in which a non-ISDN data device accesses the ISDN network
through a 3600 MainStreet series bandwidth manager node. Although the 3600
MainStreet series bandwidth manager node is not acting as a TA (it does not
translate signalling between the R and S reference points), it passes signalling
generated by the CPC on the S interface. Chapter 29.4 describes ISDN applications
for the BRI S/T card.
Figure 29.1-2: BRI S/T Card Application
Non-ISDN
computer
BRI
S/T
DCC
S
NT
U
interface
ISDN
network
CPC
6889
BRI S/T cards

In 3600 MainStreet series bandwidth managers, the BRI S/T card is the termination
for the customer premises loop at the S/T interface.
There are two types of BRI S/T card. One provides four 2B+D basic rate interfaces
and the other provides eight. Each interface provides two 64 kb/s B channels and
one 16 kb/s D channel. With local overhead added, the interface line rate is 192 kb/s.
The BRI S/T card mounts in any UCS slot.
Applications
In 3600 MainStreet series bandwidth managers, the BRI S/T card is used in both
ISDN and non-ISDN applications. In ISDN applications, the 3600 MainStreet series
bandwidth manager node processes the ISDN signalling carried in the D channel. In
non-ISDN applications, the system may or may not carry ISDN signalling,
depending on the individual situation. If it does, the signalling passes transparently
to the network. The ISDN applications are ISDN leased line backup and the channel
search facility. The non-ISDN applications are leased lines and ISDN loop extension.
29.1-2
(400)
BRI S/T Cards

NNP 95-2035-01-00-B
29.1.2

Configuring BRI S/T Cards

Table 29.1-1 lists the BRI S/T card configuration parameters for non-ISDN
applications. Table 29.1-2 lists the BRI S/T card configuration parameters for ISDN
applications. Each parameter has a list of options with any default option marked by
an asterisk.
Table 29.1-1: BRI S/T Card Configuration Parameters and Options for
Parameter
Options
Slot level
Card type
4-circuit card
8-circuit card
Interface type
ISDN
non-ISDN*
Interface mode
TE*
NT
Layer 1 standard (1)
I.430*
ETSI
T3 timer (2)
1 to 30 s in 1 s increments (15*)
Bus configuration (2)
point-to-point*
point-to-multipoint
short bus
extended bus
Circuit level
B-channel inversion type
no inversion*
Mu-law
A-law
Number of tandem super-rate circuits

(Preferred or Level 2) (3)
B1*
B2* (4)
B1 and B2
B1 and D
B2 and D (4)
B1, B2 and D
BRI S/T Cards
D-channel 3DS0 transport mode
3DS0 enabled
3DS0 disabled*
D-channel transport position
B1 to B7 (5)
Automatic loopback on physically

unconnected BRI circuits (6)
enabled
disabled
(400)
29.1-3


NNP 95-2035-01-00-B
Notes
1. This parameter applies only to the TE interface mode.
2. This parameter applies only to the NT interface mode.
3. The B1 channel should be configured as the master circuit, unless there is no B1 channel in the
super-rate bundle. In this case, the B2 channel must be configured as the master circuit, because
the D channel can never be the master circuit.
4. This is the only option that applies when configuring B2 channels; this and all other options apply
when configuring B1 channels.
5. By default, the two D-channel bits are placed in positions B7 and B6, but you can place them in any
two contiguous positions from B1 to B7 by entering the starting bit position.
6. This parameter is supported in Release 6.1 (X116-H1-30 software maintenance load) and newer
releases of software.
To make BRI channel connections for non-ISDN applications, see section 29.3.4.
Table 29.1-2: BRI S/T Card Configuration Parameters and Options for ISDN
Applications
Parameter
Options
Slot level
Card type
4-circuit card
8-circuit card
Interface type
ISDN
non-ISDN*
Interface mode
TE*
NT (1)
Layer 1 standard (2)
I.430*
ETSI
T3 timer (2)
1 to 30 s in 1 s increments (15*)
Forced activation
enabled
disabled*
Notes
1. This option applies only to non-ISDN applications.
2. This parameter applies only to the TE interface mode.
To configure BRI S/T circuits for ISDN applications, see section 29.4.4.
Note
For ISDN index configuration, see chapter 30.4.
chapter 16.4.
29.1-4
(400)
BRI S/T Cards

NNP 95-2035-01-00-B
29.2
29.2 BRI S/T Card Slots

BRI S/T Card Slots

This chapter explains how to configure BRI S/T card slots.
29.2.1
Understanding BRI S/T Card Slots

You must configure card slots for the BRI S/T cards before you can configure or
connect interfaces or circuits. Configuring a slot type means programming a card
slot to accept a specific card type with specific card parameters. When you configure
a slot, the system configures the circuits for that slot with default settings.
29.2.2
Configuring BRI S/T Card Slots

Configure the BRI S/T cards as:
BRI_ST_4 for a 4-circuit card

BRI_ST_8 for an 8-circuit card
To configure BRI S/T card slots
CONFIG SLOT <sn> TYPE MORE BASIC_RATE
BRI_ST_4
BRI_ST_8
SK000197
Note
simultaneously.
BRI S/T Cards
(400)
29.2-1

NNP 95-2035-01-00-B
29.3
29.3 Non-ISDN Applications

This chapter describes non-ISDN applications and explains how to configure
BRI S/T card interfaces and circuits for these applications.
29.3.1
Understanding Non-ISDN Applications

The BRI S/T card is used in two non-ISDN applications: leased lines and ISDN loop
extension.
Leased lines
This application allows non-ISDN devices to access the 2B+D bandwidth for
leased-line applications when there is not enough traffic to warrant an E1 link. In this
non-ISDN application, there is no need for D-channel processing, and the BRI B and
D channels are passed transparently through the node.
Typically, the physical interface of a leased-line application complies with ITU-T
I.430 standards and the interface is called a BRI interface without D-channel
processing. In MainStreet large multiplexer systems, these interfaces are configured
as NON_ISDN.
Figure 29.3-1 illustrates a typical 2B+D leased line application. In this example, the
3600 MainStreet system is used in a private network to access a 2B+D leased line
network. The 2B+D leased line is carrying six 8 kb/s compressed voice calls, three D
channels with the signalling for the voice calls, three 9.6 kb/s X.21 data calls and a
4 kb/s CPSS channel. (The X.21 data calls are connected to an X.21 DCC in the 3600
MainStreet system.) The 3600 MainStreet system passes the D channels
transparently to the network.
Figure 29.3-1: Leased Line Application
ISDN
PBX
D3
9.6 kb/s
X.21
D
D2
Voice 6
B2
Voice 3
Voice 4
Voice 5
4 kb/s
CPSS
and 2 x
9.6 kb/s
X.21
Voice 1
D1
Voice 2
B1
Front end
processor or
mainframe
9.6 kb/s
2B+D
BRI
S/T
2B+D
BRI
S/T
2B+D
Leased
Line network
3600
MainStreet node
6739
BRI S/T Cards
(400)
29.3-1


NNP 95-2035-01-00-B
Figure 29.3-2 shows the connections needed in the 3600 MainStreet system for the
leased line application. For more information on subrate multiplexing, see
chapter 23.6.
Figure 29.3-2: Leased Line Connections
4 kb/s CPSS
9.6 kb/s X.21
9.6 kb/s X.21
B1
B2
D
Faaabccd
aa - - bccd
- - - - bccd
eeeebccd
eeeebccd
eeeebccd
- - - - bccd
f f f f bccd
f f f f bccd
f f f f bccd
a
e
f
SRM
b
d
c
DSP circuits doing

voice compression
to 8 kb/s
9.6 kb/s X.21

B1
B2
D
B1
B2
B1
gh i F j kk l
gh i j j kk l
gh i j j kk l
gh i j j kk l
gh i j j kk l
gh i j j kk l
gh i j - kk l
gh i - - kk l
gh i - - kk l
gh i - - kk l
j
g
h
SRM
B2
i
l
D
7899
When the BRI S/T card is in non-ISDN mode, you can cross-connect individual
B channels to most other types of circuits (with a few exceptions, such as analog
voice circuits that need signalling). Connections are nailed up, providing a 64 kb/s
clear channel over the 2B+D link.
You can cross-connect D channels to DS0s on a primary rate link, to other 2B+D
non-ISDN interface channels or to SRS or SRM inputs. These connections allow loop
extensions for local ISDN devices to access a remote ISDN network.
29.3-2
(400)
BRI S/T Cards

NNP 95-2035-01-00-B

ISDN loop extension

The reference model shown in Figure 29.3-1 represents the simplest, ideal method of
accessing an ISDN network. But when cost or distance factors make it impractical, a
non-ISDN digital facility is used to extend the ISDN loop. Figure29.3-3 shows an
ISDN loop extension. At either end of the loop extension, a BRI S/T card provides
the 2B+D interface. At the customer premises end of the loop, the BRI S/T card
operates in NT mode. At the network end, it operates in TE mode.
Figure 29.3-3: ISDN Loop Extension
3600 MainStreet
node
Non-ISDN
digital
facility
ISDN
device
TE
2B+D
format
BRI
S/T
3600 MainStreet
node
E1
E1
(NT)
BRI
S/T
2B+D
format
NT1
ISDN
network
(TE)
1st DS0
2nd DS0
3rd DS0
B1
B2
11001 D 1
3DS0 format
6741
The loop extension scheme uses three DS0 channels on a DS1 interface to transport
the basic rate traffic between the two 3600 MainStreet systems. One DS0 is used for
each B channel and the third DS0 carries a D channel containing signalling. In
Figure 29.3-3, an ISDN device gains access to a remote ISDN network using 3DS0
transport over an E1 link. If the application needs delay equalization, you can
configure the B1, B2 and D channels as a super-rate group. Otherwise, you can
connect each channel individually.
Note
Section 22.3.25 describes ISDN loop extensions that use the 2B1Q channel unit as the
line or network termination at the U interface. In North America and France, you can
use either a 2B1Q channel unit (up to four interfaces) or a BRI S/T card (up to eight
interfaces) in an ISDN loop extension application. In Europe or Japan, the BRI S/T
card is used.
BRI S/T Cards
(400)
29.3-3

29.3.2

NNP 95-2035-01-00-B
Configuring BRI S/T Interfaces in a Non-ISDN Application

In a non-ISDN application, you can configure each of the four or eight BRI S/T card
circuits for:
interface type
interface mode
layer 1 standard
T3 timer
bus configuration
Interface type
The interface type determines whether the interface is used for ISDN or non-ISDN
purposes. For leased line and ISDN loop extension applications, configure the
interface as NON_ISDN.
To configure the interface type, see the procedure To configure BRI S/T interfaces
in a non-ISDN application.
Interface mode
The interface mode defines the BRI S/T card interface as either NT or TE. In NT
mode, the interface provides timing to the far end; in TE mode, the interface receives
its timing from the line.
In a non-ISDN application, you select the interface mode depending on the role of
the BRI S/T card in the network. When the card acts as an NT, terminating customer
premises TEs, you configure it with NT interface mode. When the card acts as a TE,
with its output connected to an NT, you configure it with TE interface mode. For
example, in the loop extension application in Figure 29.3-3, the BRI S/T card at the
user end is configured as NT, and the one at the network end is configured as TE.
Similarly, in Figure 29.3-1, the BRI S/T card connected to the PBX is configured as
NT, and the card at the network end is configured as TE.
To configure the interface mode, see the procedure To configure BRI S/T interfaces
in a non-ISDN application.
Layer 1 standard
The L1_TYPE softkey allows you to select the layer 1 standard used in the network.
Type I.430 corresponds to the ISDN network protocols used in North America and
Japan. Type ETSI corresponds to European network protocols. The only difference
between the two layer 1 types is a minor difference in the use of the T3 timer.
To configure the layer 1 standard, see the procedure To configure BRI S/T
interfaces in a non-ISDN application.
29.3-4
(400)
BRI S/T Cards

NNP 95-2035-01-00-B

T3 timer
The T3 timer is used when the interface is trying to become active. If there is no
response from the NT during the activation sequence, the interface continues its
attempts until the time specified for the T3 timer has elapsed. You can set the time
to any value between 1 second and 30 seconds, in 1 second increments.
To configure the T3 timer, see the procedure To configure BRI S/T interfaces in a
non-ISDN application.
Bus configuration
For a non-ISDN BRI S/T card in NT mode, you must specify the configuration of the
bus between the TEs and the BRI S/T card. The TEs are connected to the network
termination by either of two types of bus: point-to-point or point-to-multipoint. A
BRI S/T card in TE mode can be configured only with a point-to-point bus.
In the point-to-point configuration (PT_TO_PT), a single TE is connected to the
network termination over a bus of up to approximately 1 km.
In a point-to-multipoint (or passive) bus, up to eight TEs can be connected to the
network termination. In a short passive bus configuration (SHORT_BUS), the TEs
are placed at points on a bus of 100 m to 200 m. In an extended bus configuration
(EXTEND_BUS), the TEs are grouped together at the far end of the transmission
cable. In this configuration the bus from the network termination to the first TE can
be up to several hundred metres.
To configure the bus configuration, see the procedure To configure BRI S/T
interfaces in a non-ISDN application.
Note
The BRI S/T card must be the only TE device on the bus.
BRI S/T Cards
(400)
29.3-5


NNP 95-2035-01-00-B
To configure BRI S/T interfaces in a non-ISDN application

CONFIG SLOT <sn-i> OPTIONS
I/F_MODE
T3_TIMER BUS_CONFIG
L1_TYPE
ISDN/
NON_ISDN*
<time>
I_430*
TE*
NT
PT_TO_PT*
ETSI
MULTIPOINT
SHORT_BUS
EXTEND_BUS
SK000198
where time is 1 to 30 seconds in 1 second increments (15 s*)
29.3.3
Configuring BRI S/T Circuits in a Non-ISDN Application

When you configure the BRI S/T circuits, you are actually configuring the B and D
channels of each interface. The channels are identified by their slot and interface
numbers, and a 1 for channel B1, a 2 for channel B2 or a D for the D channel.
You can configure the B channels for:
inversion
tandem super-rate
You can configure the D channel for:
3DS0 transport
transport position
You can configure both the B and D channels for an automatic loopback on
physically unconnected BRI circuits.
B-channel inversion type

The system automatically sets the inversion type for a channel when the channel is
connected, depending on the inversion type of the connected circuit. For example, if
a B channel is connected to a voice circuit with A-law voice encoding, its inversion
type is automatically set to A-law; if it is connected to a Mu-law voice circuit, its
inversion type is set to Mu-law. If the channel is connected to a DCC circuit, another
B channel or an E1 or T1 channel, both channels are set for no inversion. The E1 or
T1 is actually configured for DATA, which means no inversion is done.
29.3-6
(400)
BRI S/T Cards

NNP 95-2035-01-00-B

You can override the automatic setting after connection, by configuring:
NO_INVER for no inversion of the B-channel bits

MuLaw_INV for full inversion of every bit
ALaw_INV for inversion of every other bit
If you manually change the configuration of a B channel to NO_INVER, you must
change a connected E1 or T1 channel to VOICE. On an E1, VOICE means that ADI
inversion is selected; on a T1, VOICE means that full inversion is selected.
To change the inversion type on a B1 channel, see the procedure To configure B1
channels.
To change the inversion type on a B2 channel, see the procedure To configure B2
channels.
Note
Use the COPY_TO softkey to copy the selected inversion type to other B channels.
COPY_TO copies only the inversion parameter.
Tandem super-rate
You can configure a preferred or level 2 tandem super-rate bundle from the B1, B2
and D channels in a non-ISDN BRI interface. Configuring BRI channels into
super-rate groups is similar to configuring primary rate DS0s into super-rate groups,
except that the BRI interface has only three channels. For more information on
configuring primary rate super-rate groups, see chapter 20.15.
You create a BRI super-rate bundle by configuring the master circuit, which is the
lowest-numbered in the group. The B1 channel is the lowest-numbered in a BRI
interface and the D channel is the highest. The B2 channel is the master circuit only
when the B1 channel is not part of the super-rate bundle; the D channel is never the
master circuit.
Using the NUM_CIRCS softkey, configure the super-rate bundle as:
B1+B2+D to include all three channels

B1+B2 to include the two B channels
B1+D to include the B1 and D channels
B2+D to include the B2 and D channels
When you subsequently make a connection to the master circuit of the resulting
super-rate group, the connection is made to the entire group, and you cannot make
a separate connection to any other member of the group. However, any channel
omitted from the group can be treated normally as an individual channel.
To de-configure the super-rate group, select B1_ONLY (if the B1 channel is the
master circuit) or B2_ONLY.
BRI S/T Cards
(400)
29.3-7


NNP 95-2035-01-00-B
Note
If you disconnect a super-rate master circuit, the super-rate group is automatically
deconfigured.
For a super-rate connection between a BRI interface and a super-rate DCC (up to
128 kb/s), you only need to connect the DCC circuit to the B1 channel. The system
automatically creates a super-rate bundle consisting of the B1 and B2 channels and
cross-connects both channels appropriately. A super-rate connection to a DCC
circuit can include only the B1 and B2 channels.
To configure a preferred or level 2 tandem super-rate bundle from the B1, see the
procedure To configure B1 channels.
To configure a preferred or level 2 tandem super-rate bundle from the B2, see the
procedure To configure B2 channels.
Automatic loopback on physically unconnected BRI circuits

When this parameter is enabled, the BRI circuit is looped back toward the BRI
interface if the circuit is not physically connected. Loopbacks C (on a 3600
MainStreet shelf) and D (on a 3645 MainStreet peripheral shelf) cannot be initiated if
an automatic loopback is in progress. Similarly, attempts to initiate an automatic
loopback are blocked when a loopback C or D is in progress, and the message
Circuit Already Looped Back - Remove Maintenance Loopback First is displayed.
Loopbacks A, B and E can be initiated or removed while an automatic loopback is in
progress. For more information about automatic loopbacks, see section 36.7.7 in
Maintenance.
The automatic loopback parameter can be enabled on both B and D channels.
To configure an automatic loopback on a B1 channel, see the procedure
To configure B1 channels.
To configure an automatic loopback on a B2 channel, see the procedure
To configure B2 channels.
To configure an automatic loopback on a D channel, see the procedure To configure
D channels.
29.3-8
(400)
BRI S/T Cards

NNP 95-2035-01-00-B

To configure B1 channels
CONFIG CIRCUIT <sn-i-1>
COPY_TO
FUNCTION
INVERSION
NO_INVER*
AUTO_LPBK
NUM_CIRCS
MuLaw_INV
ALaw_INV
ENABLE
PREFERRED
B1_ONLY*
B1+B2
B1+D
DISABLE*
LEVEL_2
B1+B2+D
SK000199
To configure B2 channels
CONFIG CIRCUIT <sn-i-2>
COPY_TO
FUNCTION
INVERSION
NO_INVER*
NUM_CIRCS
MuLaw_INV
ALaw_INV
PREFERRED
B2_ONLY*
AUTO_LPBK
ENABLE
DISABLE*
LEVEL_2
B2+D
SK000200
D-channel 3DS0 transport

You can configure the D channel in a BRI interface for 3DS0 transport in an ISDN
loop extension application.
If you select 3DS0_ENAB, the system formats the 64 kb/s DS0 channel from the BRI
card to comply with 3DS0 transport standards. The 16 kb/s D channel is placed in
the second and third least significant bits of the 64 kb/s DS0 leaving the card. These
bits are called B2 and B1 in the 3600 MainStreet system and bits 6 and 7 in 3DS0
specifications.
BRI S/T Cards
(400)
29.3-9


NNP 95-2035-01-00-B
Note
Because the 3DS0 specifications are intended for the U interface, rather than the S/T
interface, the 3DS0 transport scheme in the 3600 MainStreet system does not comply
with 3DS0 specifications in all respects. Bits 3 and 4 of the DS0 channel, which are
the ZBS bits, are always set to zero, and bit 5, which transports the DSL overhead and
maintenance bits, is always set to one.
To configure the D channel for 3DS0 transport, see the procedure To configure
D channels.
D-channel transport position

In a non-ISDN leased line application, you can define the position of the D channel
in the 64 kb/s DS0 leaving the BRI S/T card. By default, the two D-channel bits are
placed in B7 and B6, but you can place them at any contiguous two positions
between B1 and B7 by entering the starting bit position. For example, to place the
channel at bits B3 and B4, enter B4.
To configure the D-channel transport position, see the procedure To configure
D channels.
To configure D channels
CONFIG CIRCUIT <sn-i-D>
COPY_TO
<sn-i-D>
3DS0_ENAB/3DS0_DISAB*
FUNCTION
TRANSP_POS
AUTO_LPBK
<Bn>
ENABLE
DISABLE*
SK000201
where n is 1 to 7 (B7* and B6*)
Note
The 3DS0 setting, the transport position and the automatic loopback setting can be
copied from one D channel to another using the COPY_TO softkey.
29.3-10
(400)
BRI S/T Cards

NNP 95-2035-01-00-B
29.3.4

Making BRI Connections

You can cross-connect individual B and D channels to:
E1 or T1 channels (including channels on a DS-3 or E3 interface)

V.35 or X.21 PRI channels
other BRI channels
SRMs and SRS DS0s
ISDN indices
DCC and DNIC circuits
outputs of HCV voice compressors on DSPs
DCP CPSS circuits
You can also connect B channels (but not D channels) to:
voice circuits that do not require signalling

inputs to HCV voice compressors on DSPs
DSP circuits configured for echo cancellation
OCU-DP and DS0-DP
voice conference bridges and PCM data bridges
BRI channel connections

When you are making BRI connections to other interfaces, some restrictions apply.
Table 29.3-1 lists the restrictions for each type of connecting interface.
Table 29.3-1: BRI S/T Channel Connections
Connecting Interface
BRI S/T Cards
Restrictions
T1 channels
Configure the T1 signalling type for NoSIG or leave it at the default SIG
(if it is SIG, the system automatically changes it to when it makes the
connection).
If the data carried on the BRI channel could be corrupted by RBS
signalling on the T1 channel, turn RBS off.
E1 channels
If the E1 circuit is configured for CAS framing, configure it for signalling

type NoSIG or the default SIG (if it is SIG, the system automatically
changes it to NoSIG when it makes the connection).
X.21 or V.35 PRI and 64

kb/s codirectional
channels
Configure the signalling type to NoSIG or the default SIG (if it is SIG, the
system automatically changes it to NoSIG when it makes the
connection).
Other BRI channels
Configure both interfaces as NON_ISDN.
(400)
29.3-11


NNP 95-2035-01-00-B
Connecting Interface
Restrictions
DCC or DNIC circuits
Configure the DCC or DNIC circuits connected to B channels for an

interface speed of not more than 128 kb/s.
Configure the DCC or DNIC circuits connected to D channels for an
The transport position and transport bandwidth of the data in the DCC or
DNIC circuit must match the D-channel bit positions.
FRS or FRE
Configure the FRS or FRE circuits connected to D channels for an

The transport position and transport bandwidth of the data in the FRS or
FRE circuit must match the D-channel bit positions.
Voice circuits
In B channels connected to E&M or LGS_PLAR circuits, line signalling is

not passed.
CPSS
You can connect only DCP CPSS circuits directly to B or D channels.

Control card CPSS (shared or dedicated) can be carried over BRI
channels only if it is connected through an SRM.
VCBs
Configure the VCB companding law manually.
Note
It is recommended that you use B8ZS for zero suppression on a T1 interface (or B3ZS
on a DS-3).
Most connections between BRI interfaces and ADPCM circuits are not supported.
However, you can connect M48 DS0 outputs to BRI B channels.
To make connections
CONFIG CONNECT <sn-i-h> TO_CIRCUIT <sn-cc>
where
sn-i-h is the BRI interface and channel (i = 1 to 8; h = 1, 2 or D)
sn-cc is the connecting circuit
29.3-12
(400)
BRI S/T Cards

NNP 95-2035-01-00-B
29.4
29.4 ISDN Applications

ISDN Applications
This chapter describes the ISDN backup and channel search applications, and
explains how to configure BRI S/T card interfaces and circuits for the applications.
29.4.1
Understanding the ISDN Backup Application

The ISDN backup application provides RAPID-like protection of leased lines using
non-dedicated connections through the PSTN. In situations in which out-of-band
signalling is not needed and the backup connection does not need to be extremely
fast, ISDN B channel backup is more cost-effective than standard RAPID.
In these backup applications, a protected channel normally transported by a leased
line uses a BRI interface as its alternative path. Normally a one-to-one mapping of
channels from preferred to alternative paths is used. If a particular application needs
one ISDN interface to back up many channels, the network manager can program
ISDN backup using AAR. In these cases, the ISDN backup connection is
programmed as a preferred connection.
When a failure is detected at one end-point node, the node immediately switches the
leased circuits to a BRI with the appropriate pre-programmed dialling information.
You can program a variable delay setting to prevent simultaneous dialling by both
end-points when there is a failure at both nodes.
When it answers an incoming BRI call, the answering node disconnects the specified
channel from its preferred path and connects it to the B channel specified by the
network.
Figure 29.4-1 shows a typical application. A channel is connected from 3600
MainStreet node #1 to 3600 MainStreet node #2 through intermediate nodes A and B
on a leased line. If a failure is detected by 3600 MainStreet node #1, it initiates an
ISDN call through the PSTN to 3600 MainStreet node #2. Each node then connects
the backed-up channel to the ISDN B channel.
Figure 29.4-1: ISDN Backup Application
Preferred connection

Node
A
Node
B
Backup
Backup
PSTN
6745
BRI S/T Cards
(400)
29.4-1


NNP 95-2035-01-00-B
On MainStreet large multiplexer systems, ISDN is used to set up bandwidth

between two points and information on that bandwidth is transported
transparently. For this reason, a signalling protocol such as LGS that uses
out-of-band signalling cannot be transported by ISDN.
If the PSTN supports delay-equalized connections, you can also back up super-rate
connections with ISDN. If it does not, you can program the rate using the bonding
feature (see chapter 23.10). Another application for ISDN is a situation in which there
is not enough leased-line bandwidth available. In this case, you can set up a link for
a few hours in an overflow situation or for several weeks until more leased lines can
be installed.
Figure 29.4-2 shows the connections needed in the 3600 MainStreet node for the
ISDN backup application. The D channel for each interface used for ISDN signalling
must be connected to an HDLC circuit on the CPC through the switching matrix. Up
to 31 D channels can be connected to each CPC. The B channels are not connected
until the need for backup occurs or a preferred connection is programmed.
Figure 29.4-2: ISDN Backup Connections
BRI
CPC
D channel
HDLC
2B
D channel
2B
B channels are unconnected,
except when a call is in progress
Connected through
switching matrix
6742
29.4.2
Understanding the ISDN Channel Search Facility

The channel search facility allows multiple circuits within an ISDN interface to have
the same directory number. This feature is useful in applications where many calls
are made to the same number (for example, 1-800 services such as credit card
authorization).
As with the ISDN backup feature, the D channel for each BRI interface must be
connected to an HDLC circuit on the CPC. Unlike the backup feature, each circuit
connection does not have to contain a unique directory number.
Circuits with the same directory number are part of the same hunt group. When a
call is received, the node searches the group that contains the specified number, and
connects the incoming B channel to the first available tail circuit.
For detailed information on setting up hunt groups, see section 30.4.2.
29.4-2
(400)
BRI S/T Cards

NNP 95-2035-01-00-B
29.4.3

Configuring BRI S/T Interfaces in an ISDN Application

In an ISDN application, you can configure each of the four or eight BRI S/T circuits
for:
interface type
interface mode
layer 1 standard
T3 timer
forced activation
The BRI S/T circuits are configured the same way for both the ISDN backup
application and the channel search facility.
Interface type
The interface type determines whether the interface is used for ISDN or non-ISDN
purposes. Configure the interface as ISDN for ISDN backup or channel search
applications.
To configure the interface type, see the procedure To configure BRI S/T interfaces
in an ISDN application.
Interface mode
For the ISDN applications, you must define the interface mode as TE.
To configure the interface mode, see the procedure To configure BRI S/T interfaces
in an ISDN application.
Layer 1 standard
The L1_TYPE softkey allows you to select the layer 1 standard used in the network.
Type I.430/ANSI corresponds to the ISDN network protocols used in North
America and Japan. Type ETSI corresponds to European network protocols. The
only difference between the two layer 1 types is a minor difference in the use of the
T3 timer.
To configure the layer 1 standard, see the procedure To configure BRI S/T
interfaces in an ISDN application.
T3 timer
The T3 timer is used when the interface is trying to become active. If there is no
response from the NT during the activation sequence, the interface continues its
attempts until the time specified for the T3 timer has elapsed. You can set the time
to any value between 1 and 30 seconds, in 1 second increments.
To configure the T3 timer, see the procedure To configure BRI S/T interfaces in an
ISDN application.
BRI S/T Cards
(400)
29.4-3


NNP 95-2035-01-00-B
Forced activation
You can use the FRC_ACTIVATE softkey to configure a BRI interface for forced
activation. In this state, the system automatically tries to re-activate the interface
after a short pause (about 2 s) if it is de-activated by the network. Forced activation
is useful when the BRI interface is a source of synchronization for the node.
To configure the forced activation, see the procedure To configure BRI S/T
interfaces in an ISDN application.
To configure BRI S/T interfaces in an ISDN application

CONFIG SLOT <sn-i> OPTIONS
T3_TIMER
I/F_MODE
FRC_ACTIVE
L1_TYPE
ISDN/
NON_ISDN*
<time>
TE*
NT
ETSI
I_430*
ENABLE
DISABLE*
SK000202
where time is 1 to 30 seconds in 1 second increments (15*)
29.4.4
Configuring BRI S/T Circuits in an ISDN Application

In the ISDN backup application, each BRI interface can be used to back up two
64 kb/s B channels. Due to the way ISDN B channel allocation is handled by the
PSTN, it is not possible to directly correlate each channel to be protected with a
specific B channel. For this reason, the 3600 MainStreet system uses the concept of a
data index on the CPC, which handles layer 2 and 3 processing. You enter the ISDN
data against a CPC circuit and index directly on the CPC, and the system uses this
index to reference the ISDN data.
The data index is also used to set up hunt groups for the channel search facility.
Chapter 30.1 explains how to configure CPC circuits and how to make connections
between BRI S/T cards and CPCs.
29.4-4
(400)
BRI S/T Cards

NNP 95-2035-01-00-B
30. CPCs

NNP 95-2035-01-00-B
30.1
30.1 Understanding CPC Configuration

Understanding CPC Configuration

This chapter introduces the CPC and provides a summary of the configuration
parameters.
30.1.1
Understanding CPCs
The CPC provides ISDN layer 2 and 3 processing for the ISDN backup application
and the channel search facility. You can install the CPC in any UCS 1 to 8.
Note
As well as backup connections, you can also set up preferred ISDN connections
through the CPC.
30.1.2
Configuring CPCs
Table 30.1-1 lists the CPC configuration parameters. Each parameter has a list of
options with any default value marked by an asterisk.
Table 30.1-1: CPC Card Configuration Parameters and Options
Parameter
Options
Slot Level
Card type
CPC
Backplane communications link
shared
dedicated*
Serial port interface speed
See Table 17.3-2.
ISDN Backup and Channel Search Facility (Circuit Level)

Interface type
BRI
E1 PRI
T1 PRI
none
Interface standard
NTT (1)
EUROISDN (2)
NI-1 (3)
NI-2 (4)
CPCs
(400)
30.1-1


NNP 95-2035-01-00-B
Parameter
Options
Number of B channels (circuit)

BRI
T1 PRI
E1 PRI
1 or 2
1 to 23
1 to 30
B-channel search order
channel search high*

channel search low
PCM encoding
A-law
Mu-law
auto*
Call status information reporting
report off
report on*
Bearer service
H0 enable
H0 disable*
Nx64 enable
Nx64 disable*
BRI initialization
fixed TEI (0 to 63)

auto TEI*
SPID 1 (3 to 20 digits)
SPID 2 (3 to 20 digits)
bus configuration
Bus configuration
point-to-point*
point-to-multipoint
ISDN Indices (Circuit Level)

Local number
Directory number
none
local
network specific
national
international
unknown
Subaddress
none
1 to 7 characters
Remote number
Directory number
1 to 25 digits
Subaddress
none
1 to 7 characters
Bearer capability
30.1-2
speech
clear 64 kb/s*
rate adaption (56 kb/s)
3.1 kHz
(400)
CPCs

NNP 95-2035-01-00-B

Parameter
Options
Verification
enabled*
disabled
Number of retries
0 to 10 (* = 2)
infinite
Dial or non-dial
enable*
disable
Dial delay
first (0 to 60 s [0 s*])
subsequent (5 to 60 s, D 5 [10 s*])
Number of channels (index)
1 to 30
auto*
Notes
1. This option complies with Japan standards JT-Q931 and JT-Q921.
2. This option complies with European ETSI standards ETS 300 120-1 and ETS 300 104.
3. This option complies with North American BRI National ISDN-1 standards TR-TSY-268 and
SR-NWT-1953. Select this option only if the interface type is BRI; assign two SPIDs.
4. This option complies with North American National ISDN-2 standards TR-TSY-268, TR-NWT-1203,
SR-NWT-2343, SR-NWT-1953 and TR-NWT-1268.
To configure CPC circuits for the ISDN backup application and channel search
facility, see section 30.3.3.
To make CPC connections involved in the ISDN applications, see chapter 30.5.
Note
chapter 16.4.
CPCs
(400)
30.1-3

NNP 95-2035-01-00-B
30.2
30.2 CPC Card Slots

CPC Card Slots

This chapter explains how to configure CPC card slots.
30.2.1
Understanding CPC Card Slots

You must configure card slots for the CPCs before you can configure or connect
card type with specific card parameters. When you configure a slot, the system
configures the circuits for that slot with default settings.
In addition to configuring the card slot for the CPC, you can also configure the
backplane communications link between the CPC and the Control card. For
information on backplane card communications, see chapter 17.7.
To configure CPC slots

CONFIG SLOT <sn> TYPE PACKET CPC
Note
simultaneously.
CPCs
(400)
30.2-1

NNP 95-2035-01-00-B
30.3
30.3 CPC Circuit Configuration

CPC Circuit Configuration

This chapter explains how to configure CPC circuits for the ISDN backup and
channel search applications.
30.3.1
Understanding ISDN Backup

The ISDN backup application provides RAPID-like protection of leased lines using
non-dedicated connections through the PSTN. The leased lines can be protected by
either 2B+D lines terminating on BRI S/T cards, 23B+D lines terminating on Dual
T1-2 cards or 30B+D lines terminating on Dual E1 cards. Chapter 29.4 describes
ISDN backup using BRI S/T cards. The PRI implementation is virtually identical.
Figure 30.3-1 shows a typical application. In the figure, the preferred leased-line
connection is from data card circuit A1-1 to Dual T1 card circuit A2-A-1. The
protecting card for the preferred circuit is link (or interface) A on the
ISDN-configured Dual T1-2 card, A3. Because the B channels on the Dual T1-2 card
are not assigned until the back-up connection is made, the protecting connection is
programmed to index 1 in CPC circuit 5-2. The D-channel connection between CPC
Circuit 5-2 and Dual T1-2 card interface A3-A is programmed, and when the need
for backup occurs, the preferred connection is switched to the A3-A B channel
associated with the protecting index, CPC 5-2-I1, after negotiation with the PSTN.
Figure 30.3-1: ISDN Backup Protection
PBX
Preferred
connection
Data
card
Control
card
A1-1
DX
Dual T1
card
Primary
rate link
A2-1
Physical
protecting
connection
CPC
Programmed
protecting
connection
5-1-I1
Dual T1-2
card
B
A3-A
D
Primary
rate link
6803
Figure 30.3-2 shows the D-channel connections between a Dual T1-2 card and the
CPC. Up to 31 D channels can be connected to each CPC.
CPCs
(400)
30.3-1


NNP 95-2035-01-00-B
Figure 30.3-2: D-channel Connections

Dual T1-2
CPC
HDLC
D-channel
23B
D-channel
23B
B-channels are unconnected
except when a call is in progress
Connected through
switching matrix
6802
30.3.2
Understanding ISDN Channel Search

The channel search facility allows multiple circuits within an ISDN interface to have
the same directory number. This allows the ISDN line to be used for applications
such as credit card authorization, where many, short-duration calls are made to the
same number.
Connections are made from the D channel for the ISDN interface (BRI or PRI) to an
HDLC circuit on the CPC. Directory numbers are entered as part of the call data for
the CPC circuit index. Circuits that contain the same directory number are part of the
same hunt group. When a call is received, the node searches the group that contains
the specified number, and connects the incoming B channel to the first available tail
circuit.
For detailed information on configuring the CPC index, see chapter 30.4.
30.3.3
Configuration Process for the ISDN Backup and Channel

Search Applications
The following subsections describe the configuration process for the ISDN backup
and channel search applications.
To configure the ISDN applications

There are five steps in configuring the ISDN applications:
30.3-2
1.
Configure the BRI S/T card, Dual T1-2 card or Dual E1 card interface for ISDN.
See chapter 29.1 for the BRI S/T card and chapter 20.2 for the primary rate
cards.
2.
Configure the CPC circuit ISDN parameters (see section 30.3.4).
3.
Connect the D channel of the BRI or PRI to a CPC circuit (see chapter 30.5).
(400)
CPCs

NNP 95-2035-01-00-B

4.
Configure the ISDN call data on the CPC circuit index (see chapter 30.4).
5.
For ISDN backup, configure the CPC circuit and index as the protecting circuit
for the preferred connection. For the channel search application, set up the
preferred connection to the CPC circuit and index (see chapter 30.5).
Note
ISDN is supported on the BRI S/T card, but not on the T1 or E1 PRI card, in the 3664
MainStreet system.
Interface and channel numbering

The ISDN backup and channel search applications can be used for a basic rate or
primary rate interface on the BRI S/T card, the Dual T1-2 card or the Dual E1 card.
Each BRI S/T card has four or eight interfaces, which you refer to by their slot and
interface number (for example, A1-1 is slot A1, interface 1). Each interface has two
B channels and a D channel, which you refer to by their slot, interface and channel
number. The channel numbers are 1, 2 and D (for example, A1-1-2 is slot A1,
interface 1, channel 2, and A1-3-D is slot A1, interface 3, channel D).
You refer to each Dual T1-2 and Dual E1 interface (or link) as A or B, as in other T1
and E1 applications. You also refer to the channels, or timeslots, on the links in the
same way as in other applications, except for the D channel. On Dual T1-2 links, the
D channel is timeslot 24. For example, A1-A-12 is slot A1, link A, channel 12, and
A1-B-D is slot A1, link B, channel D (or timeslot 24). On E1 links, the D channel is
timeslot 16 (which is number 16 on the interface, but numbered 31 on the NMTI). On
E1 interfaces, timeslots 17 to 31 are numbered 16 to 30 on the NMTI. For example,
A1-A-20 on the NMTI is slot A1, link A, timeslot 19, and A1-B-D is slot A1, link B,
channel D (or timeslot 16).
30.3.4
Configuring CPC Circuits

For each CPC circuit (up to 31), you must configure the interface type and standard
before you configure any other parameters. After these parameters are defined, you
can configure the following parameters:
number of B channels
channel search order
PCM encoding
call status reporting
For PRI interfaces only, you can also configure the bearer service.
CPCs
(400)
30.3-3


NNP 95-2035-01-00-B
For BRI interfaces only, you can also configure:
BRI initialization parameters

bus configuration
Interface type
To define the interface type, configure I/F_TYPE as:
BRI for a BRI interface

T1_PRI for a T1 PRI interface (typically North American or Japanese)
E1_PRI for an E1 PRI interface (typically European)
NONE to remove a previously programmed interface type (to conserve memory,
this practice is recommended when a CPC circuit is not in use)
You cannot change the interface type after the circuit is program connected, unless
you disconnect the circuit first.
To configure the interface type, see the procedure To configure CPC circuits.
Interface standard
Use the I/F_STNDRD softkey to define the ISDN signalling protocol used on the
interface as:
NTT for the protocol conforming to Japanese standards JT-Q931 and JT-Q921
EUROISDN for the protocol conforming to European ETSI standards ETS 300
102-1 and ETS 300 104

NI_1 for the protocol conforming to North American BRI National ISDN-1
standards TR-TSY-268, SR-NWT-1953 and SR-NWT-2661 (you can select NI-1
only if the interface type is BRI)
NI_2 for the protocol conforming to North American National ISDN-2 standards
TR-TSY-268, TR-NWT-1203, SR-NWT-2343, SR-NWT-1953, TR-NWT-1268 and
SR-NWT-2361
You must assign two SPIDs if you select NI-1 (see the subsection BRI
initialization).
To configure the interface standard, see the procedure To configure CPC circuits.
Number of B channels
If the subscriber needs less than the maximum number of B channels, use the
NUM_B_CHAN key to specify the number of B channels subscribed. The default
value is the maximum number of B channels for the interface (2 for a BRI interface,
23 for a T1 interface and 30 for an E1 interface).
To configure the number of B channels, see the procedure To configure CPC
circuits.
30.3-4
(400)
CPCs

NNP 95-2035-01-00-B

B-channel search order

When the node switches a call to the protecting circuit, it searches the B channels in
the interface until it finds an idle channel. You can use the
CH_SEARCH_HI/CH_SEARCH_LO key to determine whether the node should
start the search at the lowest-numbered or highest-numbered channel. The default
is CH_SEARCH_HI because the node and the central office should start at opposite
ends, and central offices normally start at the low end.
To configure the B-channel search order, see the procedure To configure CPC
circuits.
PCM encoding
Use the PCM_ENCODE softkey to specify the type of encoding indicated for calls on
the interface as:
ALaw for A-law encoding

MuLaw for Mu-law encoding
AUTO to indicate that the node determines the type of encoding
For both BRI and PRI interfaces, AUTO is the normal setting. However, in a country
that does not use standard encoding (Mu-law on a T1 circuit and A-law on an E1
circuit), you should specify the type of encoding in use.
To configure the PCM encoding, see the procedure To configure CPC circuits.
Call status information reporting

The REPORT_ON/OFF key enables or disables the reporting of ISDN call status
information to the network manager. If the CPC circuit is used in the channel search
application, where many, short-duration calls are made (calls are connected and
disconnected frequently), call status reporting should be disabled.
If the circuit is used in the ISDN backup application, call status reporting should be
enabled (default).
If the call status reporting feature is not supported on the CPC, and you turn
reporting off, all call connections and disconnections are still reported to the
network manager. An alarm is raised when the CPC is initialized.
To enable or disable call status reporting, see the procedure To configure CPC
circuits.
Bearer service
You can use the BEARER_SVC softkey to enable and disable support for super-rate
connection backup on PRI interfaces. You select H0_ENABLE if the CPC circuit will
be connected to a network supporting H0, or N64_ENAB if the connecting network
supports n 64 calls. Currently, only NI-2 networks support n 64.
To configure the bearer service, see the procedure To configure CPC circuits.
CPCs
(400)
30.3-5


NNP 95-2035-01-00-B
BRI initialization
Because there can be more than one interface, or terminal, on a BRI line, ISDN
standards include methods of distinguishing the terminals from each other.
One method is to assign a TEI to each terminal. You can configure TEI assignment
as automatic or fixed. If you select the default value, AUTO_TEI, the network
assigns a TEI automatically when the terminal initializes.
Some standards do not support automatic TEI assignment. When you select
FIXED_TEI in these cases, the system prompts you for the TEI value (0 to 63).
The SPID uniquely identifies the BRI terminals set of subscription parameters,
allowing the telephone company to assign different subscription parameters to
different SPIDs on the same interface. The SPID is normally the 10-digit directory
number and a code that indicates the terminals characteristics (for example, data
device, ISDN phone, fax).
You should assign a SPID only if the central office needs this function. Currently,
only the NI-1 and NI-2 standards support SPIDs. For the NI-1 protocol to work
properly with two simultaneous calls on the interface, you must configure SPID_1
and SPID_2. For NI-2, configure SPID_1 only. The SPID values are provided by the
telephone company.
To configure the BRI initialization, see the procedure To configure CPC circuits.
Bus configuration
The BUS_CONFIG softkey indicates whether the BRI interface has been configured
as a point-to-point or point-to-multipoint bus. In a CPC circuit, this information is
used for layer 3 configuration, and it must match the hardware configuration of the
interface (for an explanation of BRI bus configuration, see the subsection BRI bus
configuration).
To configure the bus configuration, see the procedure To configure CPC circuits.
30.3-6
(400)
CPCs

NNP 95-2035-01-00-B

To configure CPC circuits

I/F_TYPE
NONE
BRI
I/F_STNDRD
E1_PRI
BEARER_SVC
T1_PRI
NTT
MORE
EUROISDN NI_1 NI_2
NUM_B_CHAN CH_SRCH_HI*/
CH_SRCH_LO
BRI_INIT
REPORT_ON*/
REPORT_OFF
PCM_ENCODE
<n>
H0_DISABLE*/
H0_ENABLE
NX64_DISAB*/
NX64_ENAB
AUTO_TEI*
FIXED_TEI
<tei>
SPID_1
SPID_2
BUS_CONFIG
<spid>
PT_TO_PT*
MULTIPOINT
ALaw
MuLaw
AUTO*
SK000204
where
n is 1 or 2* for BRI interfaces, 1 to 23* for T1 PRI interfaces and 1 to 30* for E1 PRI interfaces
tei is 0 to 63
spid is 3 to 20 digits
CPCs
(400)
30.3-7

NNP 95-2035-01-00-B
30.4
30.4 ISDN Indices

ISDN Indices
This chapter explains how to configure ISDN indices on CPC circuits.
30.4.1
Understanding ISDN Indices on CPC Circuits

In the ISDN backup application, each ISDN interface can be used to back up 2, 23 or
30 64 kb/s B channels, depending on whether the interface is basic rate, T1 primary
rate or E1 primary rate. Because the network does not allocate a B channel until the
call takes place, it is not possible to directly correlate each channel to be protected
with a specific B channel. For this reason, the 3600 MainStreet system uses the
concept of a data index on the CPC. You enter the ISDN call data against a CPC
circuit and index, and the network assigns the index to a particular B channel when
the call is processed.
The data index is also used to set up hunt groups for the channel search facility.
The range of indices on the circuit is the same as the maximum number of B channels
for the type of interface: 2 for BRI interfaces, 23 for T1 PRI interfaces and 30 for
E1 PRI interfaces. You refer to an index by its slot number, circuit number and index
number; for example, A1-1-I2 is slot number A1, circuit number 1, index 2.
30.4.2
Configuring Indices on CPC Circuits

To configure an ISDN index, you need to configure the following parameters:
directory number
bearer capability
verification mode
number of retries
dial or non-dial
number of channels
Directory number
You can assign a directory number for both an outgoing call and incoming call.
CPCs
(400)
30.4-1
30.4 ISDN Indices


NNP 95-2035-01-00-B
Outgoing call
When the system initiates an outgoing ISDN call, it creates a SETUP message
containing the call data and sends it out on the D channel. The call data includes the
REMOTE_NUM you configure for the index associated with the call. In the SETUP
message, this is known as the called party number.
To configure the REMOTE_NUM, you can assign a directory number (DIR_NUM)
and an optional subaddress (SUB_ADDR). Depending on the network,
subaddressing may be used for extension numbers to a main directory number.
Depending on the network and the subscription parameters, the SETUP message
may also contain the directory number and subaddress of the call originator. These
numbers are taken from the configured LOCAL_NUM, and are known as the calling
party number and subaddress in the SETUP message.
You define the local directory number (DIR_NUM) by selecting the format of the
number and then entering the number. The directory number formats are:
LOCAL for a local numbering scheme

NET_SPF for a network-specific numbering scheme
NATIONAL for a national numbering scheme
INTERNAT for an international numbering scheme
UNKNOWN for an unknown numbering scheme
In a National ISDN-1 or National ISDN-2 network, you may need to specify the
format as LOCAL, NATIONAL or INTERNAT. For other networks, use
UNKNOWN.
There are some restrictions in entering directory and subaddress numbers.
Directory numbers can contain only digits and hyphens; other characters are not
allowed.
In subaddresses, digits and standard characters are allowed.

For a local directory number, do not include prefixes when you enter a national
or international number for the DIR_NUM; the network automatically adds or

removes the prefix during call processing.
For a remote number, include any prefixes.
To configure the remote directory number and the local directory number, see the
procedure To configure indices on CPC circuits.
Incoming call
When the 3600 MainStreet system receives an ISDN call, it checks the incoming
SETUP message for the directory number and subaddress to determine the calls
related index. The system compares the called party number and subaddress in the
SETUP message with the configured LOCAL_NUM directory number and
subaddress until there is a match.
30.4-2
(400)
CPCs

NNP 95-2035-01-00-B
30.4 ISDN Indices

If subaddresses are used, they must match exactly. If directory numbers are used, it
may not be possible to do an exact match. The network may transmit a national
number when the user has stored only local numbers, or the network may only
transmit the last few digits of the number. For this reason, the matching is done in
reverse order with the shorter of the two numbers. If your network only transmits
one or two digits, you must make sure that all the directory numbers used on the
interface have unique last digits.
Note
You can use the NONE softkey to remove a previously programmed number. There
is no NONE softkey for the remote directory number, since it is mandatory.
For the ISDN backup application, all index entries must have a unique directory
number.
Hunt groups (channel search facility)
The channel search facility supports a hunt group feature that allows you to use the
same directory number on multiple index entries. When you enter a duplicate
directory number, a warning message is displayed; however, you can ignore it and
proceed with the entry.
There is no restriction on the number of directory numbers in a hunt group, or on the
number of hunt groups defined on the CPC, up to a maximum of 2 (BRI), 23 (T1) or
30 (E1) index entries per D channel, and up to 31 D channels per CPC. Duplicate
directory numbers do not have to be entered consecutively for a D channel. Multiple
hunt groups can be defined for a single D channel, and the same directory number
can be used for more than one D channel.
Table 30.4-1 shows an example of an index table with duplicate directory numbers.
Table 30.4-1: CPC Index Table with Defined Hunt Groups
CPCs
D channel
Entry
0800 1111111
0800 1111111
0800 2222222
0800 1111111
0800 2222222
0800 2222222
0800 1111111
0800 1111111
0800 3333333
0800 3333333
(400)
Directory number
30.4-3
30.4 ISDN Indices


NNP 95-2035-01-00-B
Hunt groups can be defined across multiple CPCs in a 3600 MainStreet system, but
because each CPC operates independently, it is not possible to share available
connections between cards.
Bearer capability
Bearer capability is used to indicate the transmission capacity of the device
connected to the ISDN interface. When the system receives an incoming call, it
compares the requested bearer capability in the SETUP message to that stored in the
index associated with the call. If the two values do not match, the system rejects the
call. You can assign one of four bearer capability.
SPEECH
Used for normal voice connections, this bearer capability does not normally occur on
the 3600 MainStreet system, as any associated signalling cannot be transmitted. This
softkey does not affect PCM encoding; it must be programmed separately for the
circuit (see the subsection PCM encoding). If a PCM encoding method is not
specified for the CPC circuit, the method in use at the far end of the connection is
applied. Do not use SPEECH for compressed voice.
CLEAR_64K
CLEAR_64K is used for unrestricted, transparent digital data transmission across
the network at 64 kb/s, and is the most commonly used in the 3600 MainStreet
system. It is used for compressed voice, super-rate connections and all data
connections that do not conform to V.110 rate adaption.
RATE_AD/56
RATE_AD/56 is used for unrestricted 64 kb/s digital data rate-adapted from
56 kb/s and can be applied to all data circuits that conform to V.110 56 kb/s rate
adaption. It is typically used when a network does not support 64 kb/s connections,
or in a network that interworks with non-ISDN switched 56 kb/s facilities. In V.110
56 kb/s rate adaption, the low order bit in each octet is set to 1 at all times.
3.1KHZ
Used for 3.1 kHz audio information, this bearer capability is another form of
SPEECH. It is typically used when the bearer capability of a call is unknown; for
example, when the network is interworking with non-ISDN facilities. PCM
encoding is handled the same way as it is for SPEECH.
To configure bearer capability, see the procedure To configure indices on CPC
circuits.
30.4-4
(400)
CPCs

NNP 95-2035-01-00-B
30.4 ISDN Indices

Verification
Use the VERIFY/NON_VERIFY softkey to determine whether the node should
verify the originating number of an incoming call. Normally, the system matches the
called party number or subaddress in the incoming SETUP message to the stored
LOCAL_NUM. If you select VERIFY, the system also compares the calling party
number or subaddress in the SETUP message to the REMOTE_NUM data stored for
the index. The system checks the subaddress if there is one in the message, or
otherwise the directory number, and rejects the call in the following circumstances:
when there is no calling party number or subaddress in the SETUP message

when there is a remote SUB_ADDR stored for the index and the subaddress in
the SETUP calling party number is wrong or non-existent

when there is no subaddress, and the calling party number in the SETUP message
does not match the remote DIR_NUM for the index (the shorter string of digits is
compared in reverse order, in case there are prefix digits in the stored DIR_NUM)
To configure verification, see the procedure To configure indices on CPC circuits.
Number of retries
Use the RETRIES softkey to specify the number of times the node should try to make
the connection if the first call setup fails. You can enter a value between 0 and 10, or
select INFINITE to cause the node to continue trying indefinitely (as long as there is
no failure that makes the call impossible to set up).
To configure the number of retries, see the procedure To configure indices on CPC
circuits.
Dial or non-dial
Use the DIAL/NON_DIAL softkey to determine whether the node should dial the
call or wait for an incoming call. If you select NON_DIAL, the interface at this end
of the connection will not originate a call in a failure condition; the far end is
expected to detect the error and originate the call. Setting the index to NON_DIAL
makes sure that a glare condition (when both ends try to originate a call
simultaneously) does not occur. If you select NON_DIAL, the BEARER_CAP and
DIAL_DELAY softkeys are not applicable to the index.
If using the channel search facility, select non-dial mode.
To configure dial or non-dial, see the procedure To configure indices on CPC
circuits.
Dial delay
If you select DIAL, you can configure DIAL_DELAY, which is the time the node
should wait before trying an ISDN call. With the FIRST softkey, you can specify the
time (0 to 60 seconds) before the first call attempt; with the SUBSEQUENT key, you
can specify the time (5 to 60 seconds in 5-second increments) between subsequent
attempts if the first call setup fails. If both ends of a call are set to DIAL, the FIRST
timer should be set with several seconds difference at each end to avoid a glare
condition.
CPCs
(400)
30.4-5
30.4 ISDN Indices


NNP 95-2035-01-00-B
To configure dial delay, see the procedure To configure indices on CPC circuits.
Number of channels
The NUM_CHANS softkey can be used to specify the number of B channels needed
for the call. Under normal conditions, you should accept the default value of AUTO,
which means that the node automatically calculates number of channels at
connection time. This softkey is typically used for testing.
To configure the number of B channels, see the procedure To configure indices on
CPC circuits.
30.4-6
(400)
CPCs

NNP 95-2035-01-00-B
30.4 ISDN Indices

To configure indices on CPC circuits

CONFIG CIRCUIT <sn-cc-Ixx>
COPY_TO
LOCAL_NUM
REMOTE_NUM
DIR_NUM
BEARER_CAP
SUB_ADDR
<number>
<subaddress>
NONE
SUB_ADDR
DIR_NUM
NONE
MORE
LOCAL NET_SPF NATIONAL INTERNAT UNKNOWN
<number>
<subaddress>
NONE
SPEECH
VERIFY*/
NON_VERIFY
CLEAR_64K*
DELETE
RETRIES DIAL/
NON_DIAL
<tries>
INFINITE
RATE_AD/56
DIAL_DELAY
FIRST
<first_time>
ENABLE*
DISABLE
3.1KHZ
NUM_CHANS
SUBSEQUENT
<sub_time>
<nn>
AUTO*
SK000205
where
number is 1 to 15 digits for local numbers and 1 to 25 for remote numbers (digits and hyphens only)
subaddress is 1 to 7 characters
tries is 0 to 10 (2*)
first_time is 0 to 60 seconds
sub_time is 5 to 60 seconds in 5 second increments
nn is 1 to 30
CPCs
(400)
30.4-7
30.4 ISDN Indices


NNP 95-2035-01-00-B
Note
Use COPY_TO to copy data from one index to another. Directory numbers and
subaddresses are not copied.
Use DELETE to delete all data associated with the index.
30.4-8
(400)
CPCs

NNP 95-2035-01-00-B
30.5
30.5 CPC Connections

CPC Connections
This chapter explains how to make the connections involved in the ISDN backup
and channel search applications.
30.5.1
Understanding CPC Connections for the ISDN

Applications
The type of connections you can make for the ISDN backup and channel search
applications fall into three categories:
CPSS
super-rate
non super-rate
CPSS
You can back up 64 kb/s standard CPSS connections to a DCP and dedicated CPSS
connections to a Control card, but neither 4 kb/s CPSS over FDL nor shared CPSS is
supported.
Normally, you should not use the FDL on an ISDN PRI interface for CPSS, because
an ISDN interface is usually connected to the public network.
Super-rate
The ISDN applications support two types of super-rate connections: H0 and n 64.
You can configure H0 or n 64 operation for a CPC circuit configured for T1 or E1.
If the H0 capability is available on the network, you can connect six super-rate
channels totalling 384 kb/s by configuring the interface for the H0 bearer service.
You program the connection against the first channel in the super-rate bundle, and
the system assigns five more contiguous channels and sets up a single call when the
need for backup occurs. Because H0 connections need six contiguous channels with
the first channel number 1, 7, 13, 19 or 25 (E1 only), you should not use an H0 PRI
interface for any other types of connections, in case the system cannot find the right
channels at connection time.
The n 64 bearer service operates in the same manner as the H0 capability. The
maximum size super-rate connection is 23 64 for T1 PRI interfaces and 30 64 for
E1 PRI interfaces.
CPCs
(400)
30.5-1


NNP 95-2035-01-00-B
Non super-rate
You can connect any of the following non super-rate circuits to an ISDN index:
T1 or E1 channels (including channels on a DS-3 or E3 interface)

X.21 or V.35 channels
non-ISDN BRI B and D channels
SRMs and SRS DS0s
DCC and DNIC circuits
FRS or FRE packet circuits
voice circuits that do not need signalling
OCU-DP circuits
DSP circuits configured for BONDING
Some restrictions may apply to some of these connections (see Table 29.3-1).
30.5.2
Making the Connections to Set Up the ISDN Applications

To set up the ISDN backup and channel search applications, you must:
make the connection between the D channel of the BRI or PRI interface and the
CPC circuit
configure the protecting connection (ISDN backup only) or the preferred

connection (after the CPC index data is configured)
To connect D channels
CONFIG CONNECT <sn-i-D> TO_CIRCUIT <sn-cc>
where
sn-i-D is the D channel on the BRI or PRI interface
sn-cc is the CPC circuit (1 to 31)
To configure preferred connections

Set up the preferred connection (including connections for the channel search
facility) to the ISDN index by connecting the D channels and then entering:
CONFIG CONNECT <sn-cc> or <sn-l-cc> TO_CIRCUIT <sn-cc-Ixx>
To connect protecting connection

CONFIG CONNECT <sn-cc> or <sn-l-cc> PROT_BY <sn-cc-Ixx>
30.5-2
(400)
CPCs

NNP 95-2035-01-00-B

where
sn-cc or sn-l-cc is the circuit to be protected
sn-cc-Ixx is the CPC circuit and index (cc is 1 to 31; xx is 1 to the number of B channels (NUM_B_CHAN)
configured for the index)
CPCs
(400)
30.5-3

NNP 95-2035-01-00-B
31. HSA Cards

NNP 95-2035-01-00-B
31.1
31.1 SONET/SDH and 3600+ MainStreet System Applications

SONET/SDH and 3600+ MainStreet

System Applications
This chapter describes basic principles of SONET and SDH and the applications
supported on the 3600+ MainStreet Bandwidth Manager.
31.1.1
Understanding SONET and SDH Basics

SONET and SDH are standards for signalling in fibre optic networks in North
America and Europe, respectively. The SONET and SDH standards define the
format, optical line rate, wavelength, power levels, pulse shape and coding for
optical networks. The creation of these standards ensures a long-term solution for
inter-vendor development of interfaces that allow the transport of existing digital
services over fibre optic networks. The 3600+ MainStreet supports OC-3 SONET
level through the OC-3 card, and the STM-1 SDH level through the STM-1 card.
Since SONET and SDH networks are synchronous, only single-stage multiplexing
and demultiplexing is required; there is no requirement, as there is in asynchronous
networks, for multi-stage multiplexing. Single-stage multiplexing and
demultiplexing eliminates the need for back-to-back multiplexing while inserting
data into or extracting data from a network. Data can be added to or dropped from
a SONET or SDH signal without demultiplexing and remultiplexing the entire
SONET or SDH signal. This makes SONET and SDH equipment compact and
efficient.
SONET and SDH Data Transmission Rates and Structures

A SONET or SDH signal is bandwidth-flexible and can support transmission of a
combination of services including broadband data switching, high-speed
packet-switching and video conferencing. A basic SONET or SDH signal is a
structured frame that is divided into overhead layers and a payload envelope. The
overhead layers contain transport and payload information and can be used for
maintenance operations. The payload carries signals that have been mapped into a
payload envelope.
SONET frames are called STS-n frames; SDH frames are called STM-n frames. In
STS-n, n represents the number of STS-1 signals that are combined to form an STS-n
frame. In STM-n, n represents the number of STM-1 signals that are combined to
form an STM-n frame. Each STS-n and STM-n frame has an associated line rate that
increases by 51.840 Mb/s and 155.520 Mb/s respectively each time that n increases
by one. Table 31.1-1 lists and compares STS-n and STM-n frame line rates.
HSA Cards
(400)
31.1-1


NNP 95-2035-01-00-B
Table 31.1-1: SONET STS-n and SDH STM-n Line Rates

SONET STS-n Frame
SDH STM-n Frame
Line Rate
STS-1
51.840 Mb/s
STS-3
STM-1
155.520 Mb/s
STS-9
STM-3
466.560 Mb/s
STS-12
STM-4
622.080 Mb/s
STS-18
STM-6
933.120 Mb/s
STS-24
STM-8
1.244 Gb/s
STS-48
STM-16
2.488 Gb/s
The flexibility of the SONET and SDH frame formats allows for efficient mapping of
network services into payload envelopes. For example, an STS-1 can accommodate
one DS3 or a combination of sub-DS3 signals, and an STM-1 can accommodate one
DS1E or a combination of sub-DS1E signals.
In a SONET payload envelope, sub-DS3 signals are carried in VTs; in an SDH
payload envelope, DS1E and sub-DS1E signals are carried in TUs. There are different
VT and TU types, and they can be distinguished from one another by their line rates.
Table 31.1-2 lists the typical standard signals that can be carried on VTs and TUs.
Table 31.1-2: VT and TU Line Rates
VT or TU Type
Line Rate
Standard Signal
Connection
VT-1.5
1.728 Mb/s
DS1 (T1)
VT-2
2.304 Mb/s
CEPT-1
VT-3
3.456 Mb/s
DS1C
VT-6
6.912 Mb/s
DS2
TU-11
1.728 Mb/s
DS1E
TU-12
2.304 Mb/s
E1
TU-2
6.912 Mb/s
DS2
TU-3
48.384 Mb/s
DS3 or E3
Multiplexing
In a SONET network, individual VTs are combined and mapped to higher-order
structures called VT groups. Any combination of VT types can be used to fill the
payload envelope of an STS-1 frame, but only one type of VT is configurable in each
VT group. STS-1 frames are further combined and mapped to higher-order STS-n
frames. For example, the STS-3 frame, the next higher-order frame relative to the
STS-1, accommodates three STS-1 frames.
31.1-2
(400)
HSA Cards


NNP 95-2035-01-00-B
In an SDH network, broadband data is mapped onto individual VCs, which are in
turn changed into TUs. Individual TUs are combined into TUG-2 or TUG-3 groups,
which are combined into AU-3 or AU-4 structures. An STM-1 frame is composed of
one AU-4 structure in AU-4 mode, and three AU-3 structures in AU-3 mode. The
STM-1 card multiplexes TUs into an STM-1 signal through the following processes.
1. Lower-order VCs are assigned TU pointers that indicate their position relative
to the start of the higher-order VC frame. Once a pointer is assigned to a VC, a
TU is formed.
2. One or more TUs is mapped to a TUG, which allocates for the TU or TUs a fixed
position within the higher-order VC frame.
3. TUGs are assigned AU pointers that indicate their position relative to the start
of the STM-1 frame. Once a pointer is assigned to a TUG, an AU is formed.
4. One or more AUs is mapped to a AUG, which allocates for the AU or AUs a fixed
position within the STM-1 frame.
As with STS-1s, STM-1 frames can be further multiplexed into higher-order STM-n
frames.
For information about SONET and SDH broadband circuit configuration, see
chapter 31.6.
31.1.2
3600+ MainStreet Bandwidth Manager Applications

The 3600+ MainStreet Bandwidth Manager can be set up to support four basic
applications: high-density time-division multiplexing, linear add/drop
multiplexing, signal termination, and ring multiplexing. Traffic protection is
supported in all shelf configurations. For information on how to set up a
3600+ MainStreet enhanced locally controlled shelf to support these applications, see
chapter 31.2.
High-density time-division multiplexing

The enhanced locally controlled shelf can be set up to support time-division
multiplexing. The basic shelf configuration provides access to 8 UCSs; if a
Narrowband module is installed on the Control card, access to 16 UCSs is provided.
In this application, no HSA cards are installed, therefore, no SONET or SDH
functionality is supported. Future enhancements to this shelf configuration include
support for Octal T1 and E1 cards.
Linear add/drop multiplexing and signal termination

For this application, a series of enhanced locally controlled shelves are set up to
support the adding and dropping of data in a linear network. The shelves at either
end of the linear network provide signal termination. HSA cards can be used in these
applications, providing SONET or SDH functionality. Traffic protection is
supported on a link level.
HSA Cards
(400)
31.1-3


NNP 95-2035-01-00-B
Figure 31.1-1 shows an example of how enhanced locally controlled shelves are used
in linear add/drop multiplexing and signal termination applications.
Figure 31.1-1: Example of Linear Add/Drop Multiplexing and Signal Termination
Applications
Linear broadband network
3600+ MainStreet
Narrowband
and broadband
signal termination
3600+ MainStreet
3600+ MainStreet
Narrowband
and broadband
signal termination
9770
Ring multiplexing
The ring topology consists of a minimum of three enhanced locally controlled
shelves. The advantages of ring multiplexing include support for linear add/drop
multiplexing and signal termination applications and traffic protection at the circuit
level which allows for quick recovery of service in the event of a failure.
Figure 31.1-2 shows an example of how enhanced locally controlled shelves are set
up in a ring.
31.1-4
(400)
HSA Cards

NNP 95-2035-01-00-B

Figure 31.1-2: Example of a Ring Application
3600+ MainStreet
Corporate
PBX
3600+ MainStreet
3600+MainStreet
3600+ MainStreet
3600+ MainStreet
Linear add/drop
3600+ MainStreet
DS3
POTS
Public
Network
9771
HSA Cards
(400)
31.1-5

NNP 95-2035-01-00-B
31.2
31.2 Understanding High-speed Aggregate Card Configuration

Understanding High-speed
Aggregate Card Configuration
This chapter introduces high-speed aggregate cards.
31.2.1
Understanding High-speed Aggregate Cards

The 3600+ MainStreet system supports the following high-speed aggregate cards:
OC-3 cards
STM-1 cards
VT 1.5 mapper cards
TU-12 mapper cards
The above HSA cards are installed in 3600+ MainStreet system HSA card slots. The
OC-3 and STM-1 cards provide a 155 Mb/s bidirectional optical interface.
OC-3 and VT-1.5 cards are used in SONET applications. The OC-3 card connects
directly to a SONET network, and the VT-1.5 card maps narrowband data onto the
OC-3 card broadband circuits.
STM-1 and TU-12 cards are used in SDH applications. The STM-1 card connects
directly to a SDH network, and the TU-12 card maps narrowband data onto the
STM-1 card broadband circuits.
HSA card configurable parameters

Table 31.2-1 shows the configurable parameters.
Table 31.2-1: HSA Card Configurable Parameters
OC-3
STM-1
VT-1.5
TU-12
Parameter
Option
See Section
Card
Card type
OC-3
STM-1
VT-1.5
TU-12
Traffic protection mode
HSA Cards
31.3.2
31.4.2
1+1*
simplex
ring
Card name
0 to 8 characters
(400)
31.3.2
31.2-1

OC-3
STM-1
VT-1.5
TU-12

NNP 95-2035-01-00-B
Parameter
Option
See Section
1+1 operating mode (1)
unidirectional*
bidirectional
31.4.2
1+1 switching type (1)
non-revertive*
revertive
31.4.2
1+1 WTR timer (1)
0 to 60 min, D = 1 min
(* = 5 min)
31.4.2
1+1 working card (1)
subslot A* or B
31.4.2
Broadband Port
Alarm declare and clear time
0.1 to 60 s, D = 0.1 s
35.4.2
Signal degrade threshold
1 E-5
1 E-6*
1 E-7
1 E-8
1 E-9
disabled
33.10.3
AIS insertion on EBER response
enabled
disabled*
33.10.3
AIS local alarm
enabled*
disabled
33.10.3
RFI remote alarm
enabled*
disabled
33.10.3
APS remote alarm
enabled*
disabled
33.10.3
SES threshold
1 to 65535
(* = 2500)
33.10.2
Near- and far-end TCA thresholds
See chapter 33.10
33.10.2
Section trace
trace*
section ID
36.10.1
OC-3 outgoing section trace

message
0 to 255
36.10.1
STM-1 section trace expected

received message
as present*
16 or 64 alphanumeric
characters
36.10.1
STM-1 section trace Tx message*
16 or 64 alphanumeric
characters
36.10.1
STM-1 section trace message

length
16 byte*
64 byte
36.10.1
SDH format
AU-3
AU-4*
31.6.3
DCC (2)
enabled
disabled*
31.8.1
Synchronization
system*
self
through
31.5.1
31.2-2
(400)
HSA Cards

NNP 95-2035-01-00-B
OC-3
STM-1
VT-1.5
TU-12

Parameter
Option
See Section
Broadband Circuit
Circuit name
0 to 8 characters
31.6.5
0.1 to 60 s,
(* = 10 s)
35.4.2
Signal degrade threshold
1 E-5
1 E-6*
1 E-7
1 E-8
1 E-9
disabled
33.10.3
AIS insertion on EBER
enabled*
disabled
33.10.3
AIS local alarm
enabled*
disabled
33.10.3
RFI remote alarm
enabled*
disabled
33.10.3
TIM local alarm
enabled*
disabled
33.10.3
Broadband circuit SES threshold
0 to 65535 (* = 2400)
33.10.2
Near- and far-end TCA thresholds
See chapter 33.10
33.10.2
STS-1 function
VT group*
bulk payload
31.6.2
STS-1 signal label (3)
non-specific
VT structured
31.7.2
AU-3 function
TUG-2*
C3
31.6.3
TUG-3 function
TUG-2*
TU3
31.6.3
AU-3 or AU-4 signal label (3)
non-specific
TU group structured*
31.7.2
OC-3 path trace Tx message (3)
0 to 62 alphanumeric
characters
36.10.1
STM-1 path trace message length
16* or 64 alphanumeric
characters
36.10.1
(3)
STM-1 path trace expected

receive message (3)
as present
characters
36.10.1
STM-1 path trace Tx message (3)
characters
36.10.1
Path trace message change

alarm (3)
enabled*
disabled
36.10.1
Path protection WTR timer (4)
0 to 60 min, D = 0.1 s
(* = 0 s)
31.4.2
HSA Cards
(400)
31.2-3

VT-1.5
TU-12

NNP 95-2035-01-00-B
OC-3
STM-1
Path protection hold-off timer (4)
0 to 10 s, D = 0.1s
(* = 0 s)
31.4.2
Working circuit (4)
subslot A circuit*
subslot B circuit
31.4.2
STS-1 VT group configuration (5)
VT-1.5*
VT-2
VT-3
VT-6
31.6.2
TUG-2 configuration (6)
TU-11*
TU-12
TU-2
31.6.3
Circuit provisioning
enabled*
disabled
31.6.4
VT-1.5 signal label
equipped nonspecific
asynchronously mapped
DS-1*
31.7.2
TU-12 signal label
equipped nonspecific
asynchronously mapped
E1*
31.7.2
0.1 to 60 s
35.4.2
DS1 Framing
D4*
ESF
31.13.2
E1 Framing
CAS*
CCS
31 channels
31.13.3
Trunk conditioning
one-way
two-way*
31.12.3
Fault classes

failed off or on*
error off or on*
31.12.5
Loopback detection
none
through CPSS
31.20.2
CRC stats collection
CRC errors
framing bit errors*
31.18.3
CRC re-framing
enabled
disabled*
31.18.2
transparent
jam bit 7*
31.11.1
NU bits
0000 to 1111*
31.17.1
Inversion
inverted* (voice)
not inverted (data)
31.16.2
Parameter
Option
See Section
Narrowband DS1 or E1 Ports
Narrowband DS0 circuits
31.2-4
(400)
HSA Cards

NNP 95-2035-01-00-B
OC-3
HSA Cards
STM-1

VT-1.5
TU-12
Parameter
Super-rate formats
contiguous
non-contiguous
equidistant
31.10.1
Fault signalling
seized
idle*
OOS-A
OOS-B
OOS-C
None
31.14.2
Custom trunk conditioning, ABCD

bits
2- or 4-digit code, E&M

(idle=0000*; seized=1111*)
31.19.2

(00000000 to 11111111*)
31.19.2
enabled*
disabled
31.15.1
Clear channels
NOSIG
RBS OFF
31.15.1
T1 signalling types
transparent*
clear channel
E&M
LGS LS
LGS GS
LGS PLAR
LGS PLAR D3
LGE LS
LGE GS
Terminate
31.15.2
E1 signalling types
transparent*
clear channel
E&M
LGS RE
LGS EC
LGS PLAR
LGS PLAR D3
LGE RE
LGE EC
31.15.3
T1 signalling types
transparent*
clear channel
E&M
LGS LS
LGS GS
LGS PLAR
LGS PLAR D3
LGE LS
LGE GS
31.15.3
(400)
Option
See Section
31.2-5


NNP 95-2035-01-00-B
Notes
1. The card must be configured for 1+1 traffic protection.
2. The 3600+ MainStreet system NET address must be configured before the DCC can be enabled.
3. This option is only available for STS-1, AU-3 and TUG-3 links.
4. This option is only available for STS-1, AU-3, TUG-3, VT and TU circuits in ring mode.
5. This option is only available for STS-1 links.
6. This option is only available for AU-3 and TUG-3 links.
31.2.2
SONET or SDH Service Configuration

The following procedure explains how to connect narrowband DS0 data from UCS
cards to a broadband SONET or SDH network. A typical configuration requires one
pair of OC-3 or STM-1 cards, and one set of TU-12 or VT-1.5 mapper cards.
Narrowband data can be connected to the mapper cards by connecting mapper card
narrowband circuits to circuits on a UCS card.
The OC-3 or STM-1 cards connect directly into a SONET or SDH UPSR ring or
terminal add-drop network. The mapper cards are used to map narrowband UCS
primary rate signals (DS0s), onto mapper card broadband circuits that can be
connected to OC-3 and STM-1 card VT or TU circuits.
In 1+1 traffic protection mode, all parameters are configured on an HSA slot basis
except circuit name. For example, configure parameters by identifying the circuit as
H1-1 if you wish to configure the first STS-1 in HSA slot 1.
In ring mode, configuration can be done on either the slot or subslot level. Subslot
configurations apply only to the selected subslot, and slot level configurations apply
to both subslots.
In simplex traffic protection mode, you can select the circuit by the HSA slot or
subslot identifier. For example, use H1-A-1 or H1-1 to identify the first STS-1 in
subslot A of HSA slot 1. In simplex mode, you cannot communicate with a card that
is inserted into subslot B of any HSA subslot.
1.
Insert the cards into the card slots. If a ring configuration is to be configured on
the OC-3 or STM-1 cards, insert the OC-3 or STM-1 cards into HSA slot H1.
2.
Configure the traffic protection mode for the HSA slots as simplex, ring or 1+1
mode. If you configure a slot for 1+1 protection, configure the 1+1 switching
options now. If you configure a slot for ring mode, path protection options must
be configured for each circuit. If ring mode is configured, and slot H2 is used to
add or drop broadband data to the ring, you must allocate UCS bandwidth to
slot H2. To allocate bandwidth to H2, enter:
CONFIG SYSTEM UCS_BB_BUS TO_H2
When UCS bandwidth is allocated to H2, you cannot configure an STS-1, TU-3
or AU-3 as a circuit on a card in H2. Only VT and TU circuits are allowed.
3.
31.2-6
Connect the Tx and Rx fibre optic cables from the SONET or SDH network to
the OC-3 or STM-1 cards.
(400)
HSA Cards

NNP 95-2035-01-00-B
HSA Cards

4.
Configure the broadband port and circuit parameters on the OC-3 or STM-1
card.
5.
Configure broadband circuit, narrowband port and narrowband circuit

parameters on the mapper card.
6.
Configure broadband connections between the OC-3 or STM-1 cards and the
SONET or SDH network.
7.
Configure connections between the UCS card primary rate signals and the
mapper card narrowband circuits.
8.
Configure connections between the mapper card broadband VT or TU circuits

and the VT or TU circuits on the OC-3 or STM-1 cards.
(400)
31.2-7

NNP 95-2035-01-00-B
31.3
31.3 HSA Card Slots

HSA Card Slots

This chapter introduces HSA card slot configuration and explains how to program
HSA card slots to accept the inserted card.
31.3.1
Understanding HSA Card Slots

An HSA card slot contains two subslots used for card redundancy through traffic
protection: subslot A and subslot B. Each subslot accepts an HSA card.
You must configure HSA card slots for the inserted card before you can configure
connections or card parameters.
After the slot is configured, the circuits associated with that slot are configured with
the default settings appropriate for that card.
31.3.2
Configuring HSA Card Slots

You can configure an HSA card slot for the following cards:
STM-1
OC-3
VT-1.5 mapper
TU-12 mapper
Each HSA slot can be configured with a card type, and each HSA card in each subslot
can be configured with a card name.
OC-3 and VT-1.5 mapper cards are used for OC-3 SONET applications, and STM-1
and TU-12 mapper cards are used for STM-1 SDH applications.
When the slot is configured, you should configure traffic protection options before
configuring or connecting any HSA card circuits. See chapter 31.4 for information.
Warning
If traffic protection mode is changed after circuit connections are made, all
connections may be lost.
HSA Cards
(400)
31.3-1
31.3 HSA Card Slots


NNP 95-2035-01-00-B
Note
A Revision/Feature Mismatch alarm occurs if VT-1.5 cards (revision 87-1034-03-1A
and earlier) or TU-12 cards (revision 87-1034-04-1A and earlier) are inserted in an
HSA slot. The card is not operational, and must be replaced by a newer revision.
Contact Newbridge support for information.
To configure an HSA slot card type

CONFIG SLOT <Hn>
TYPE
MAPPER
SONET
SDH
OC-3
STM-1
AS_PRESENT
TU-12
VT-1.5
16_PORT
16_PORT
SK000900
where
Hn is the HSA slot number used to configure card type
To configure HSA card name

CONFIG SLOT <Hn-ss> NAME <name>
where
Hn-ss is the card slot and subslot identifier
name is a card name up to eight characters in length
31.3-2
(400)
HSA Cards

NNP 95-2035-01-00-B
31.4
31.4 HSA Card Traffic Protection

HSA Card Traffic Protection

This chapter describes traffic protection modes, options and protection switching
commands.
31.4.1
Understanding Traffic Protection

Traffic protection provides an alternate line or path if the working line or circuit fails
or is highly errored. After the traffic protection mode is configured, protection
switching options can be configured.
Traffic protection mode

There are two types of traffic protection: line protection and path protection. The
OC-3 and STM-1 card support the following three modes of traffic protection:
simplex
1+1
ring
Mapper cards support the following two modes of traffic protection:
Simplex
1+1
Line protection is provided by 1+1 mode, and path protection is provided by ring
mode. These modes require that the HSA slot has a card inserted in each subslot.
Ring mode
Ring traffic protection mode can only be configured on HSA slot H1. In ring mode,
fiber optic cables are connected between opposite OC-3 or STM-1 card subslots. For
ring mode, connect fiber optic cables from subslot A on one node to subslot B on the
next node, and continue throughout the ring as seen in Figure 31.4-7.
1+1 mode
For OC-3 and STM-1 cards in 1+1 traffic protection mode, fibre optic lines must be
connected between each subslot on the cards in each node. When 1+1 connected
cards on different nodes are connected by fiber optic cables, connect subslot A on
one node to subslot A on the other node, and subslot B on one node to subslot B on
the other node, as seen in Figure 31.4-2.
Mapper cards do not require any special physical connections because mapper card
circuits connect to other circuits through backplane connections.
HSA Cards
(400)
31.4-1


NNP 95-2035-01-00-B
Simplex mode
Simplex mode does not provide traffic protection. To support simplex traffic
protection on a card, it must be inserted in subslot A of an HSA card slot. Subslot B
registers as empty.
Caution
Any change from 1+1 to ring mode or ring mode to 1+1 traffic protection mode
results in a loss of all configured connections. A change from simplex to ring, or from
ring to simplex mode results in a loss of all configured connections.
A change from 1+1 to simplex mode results in a protection switch if subslot B is the
active card. Data is lost during the protection switch.
Protection switching options

Protection switching options control protection switching behavior for 1+1 and ring
modes.
Figure 31.4-1 shows a ring traffic protection configuration screen.
Figure 31.4-1: Ring Traffic Protection mode configuration screen
3600+ MainStreet
Circuit
H1-01
S1117-H1-00
Name
Circuit7
Switching
Working Circuit
WTR Timer
Hold Off Timer
Toronto:A
Type
STS-1
:
:
:
:
Alarms:1
11-May-1997
8:35a
Function
Bulk Payload
Non-Revertive
H1-B-01
5 minutes
0.0 seconds
CONFIG CIRCUIT H1-1 FUNCTION PATH_PROT

1-REVERTIVE
6-
2-WORKING_A
7-
3-WTR_TIMER
8-CANCEL
4-HOLD_OFF
9-QUIT
50-
Figure 31.4-2 shows a 1+1 traffic protection configuration screen.
31.4-2
(400)
HSA Cards

NNP 95-2035-01-00-B

Figure 31.4-2: 1+1 Traffic Protection Mode Configuration Display

3600+ MainStreet
#
H1-A
H1-B
Configured
OC-3
OC-3
S1117-H1-00
Toronto:A
Installed
OC-3
OC-3
Operating Mode
Switching
WTR Timer
Working Card
:
:
:
:
Status
OK
OK
Alarms:1
Name
MUX3-A
MUX3-B
11-May-1997
8:35a
Options
1+1
1+1
Unidirectional
Non-Revertive
5 minutes
H1-A
CONFIG SLOT H1 OPTIONS PROTECTION 1+1 SWITCH

1-BIDIRECT
6-
2-REVERTIVE
7-
3-WTR_TIMER
8-CANCEL
4-WORKING
9-QUIT
50-
Working card
The working card option allows you to designate a working line and a protection
line for a connection between two nodes. The working line is the preferred line for
active data, and the protection line is used as a protection in case of a failure on the
working line. The configuration of working card is only important if revertive
switching is configured.
The active line is the line connected to the active card. The active card is determined
by the severity of card or line faults, and the configured switching type. Until card
or line faults cause a protection switch to the protection line, the working line carries
all the active data traffic.
Working circuit
The working circuit option allows you to designate a working ring and a protection
ring for a UPSR circuit connection. The working ring and associated circuit are the
preferred path for data traffic. The protection ring and associated circuit are used
when the quality of the circuit on the working ring degrades. The configuration of
the working circuit is only important when revertive switching is configured.
The active ring is the ring that is connected to the card that contains the active circuit.
The active circuit is determined by path quality and the configured switching type.
Until the path quality of the circuit associated with the working ring degrades, the
working ring carries all of the active data traffic.
HSA Cards
(400)
31.4-3


NNP 95-2035-01-00-B
Switching type
Switching type can be configured as:
revertive
non-revertive
For 1+1 protected cards, protection switching occurs on the basis of line quality
determined by card or line faults. For ring protected cards, protection switching
occurs on the basis of path quality.
If the revertive switching type is selected, there is a switching bias toward the
working line or working ring circuit. The node selects traffic from the working line
or ring circuit until the line quality of the working line falls below the line quality of
the protection line. When line quality is equal, traffic is selected from the working
line, because the card in the working subslot reverts to being the active card.
If the non-revertive switching type is selected, there is no switching bias toward
either line or ring circuit. The inactive or active card or circuit is determined by the
number of line or card faults on each card, or path quality. A protection switch does
not occur in non-revertive mode until one card has fewer card or line faults than the
other card, or one ring circuit has better path quality than the other ring circuit.
Operating mode
The following protection switching modes are available for 1+1 protected OC-3 and
STM-1 cards:
unidirectional
bidirectional
When bidirectional switching is configured on an HSA card slot, it mimics every
protection switch that takes place on a connected card. In this way, each subslot of
an HSA slot that is configured for bidirectional switching has the same status (active
or inactive) as the connected card.
When unidirectional switching is configured, the status of connected cards can
differ, because the card configured for unidirectional switching does not mimic a
protection switch performed by a connected card.
WTR and hold-off timers
The WTR and hold-off timers delay protection switching to ensure that the change
in card faults or path quality that prompted the system request for a protection
switch are valid, and not merely intermittent.
The WTR timer controls the delay that occurs before a protection switch back to the
working line or ring circuit occurs. The WTR timer starts when a request for a
protection switch to the working line or ring circuit occurs. At the end of the WTR
count, the system checks to see if the conditions that caused the request still exist. If
the conditions do exist, a protection switch occurs. If the conditions do not exist, a
protection switch back to the working line or ring circuit does not occur.
31.4-4
(400)
HSA Cards

NNP 95-2035-01-00-B

The hold-off timer controls the delay that occurs before a protection switch to the
protection ring occurs. The hold-off timer starts when a request for a protection
switch occurs. At the end of the hold-off timer count, the system checks to see if the
conditions that caused the request still exist. If the conditions do exist, a protection
switch occurs. If the conditions do not exist, a protection switch to the protection ring
circuit does not occur.
1+1 mode line protection switching

1+1 mode provides line protection to an HSA card slot by providing two sets of lines
to another HSA card slot on the local or remote node. If one set of lines degrades or
fails, the other set of lines are used as alternates.
Figure 31.4-3 shows a connection between two sets of 1+1 protected HSA cards on
different nodes. Each of the two HSA slots involved in the connection contain two
HSA cards. One card is in HSA subslot A, and the other card is in subslot B. Two sets
of fibre optic lines connect each corresponding subslot, connecting the Tx and Rx
connectors of the cards in subslots A and B. This configuration provides two Tx lines
and two Rx lines for a single connection. If one line degrades or fails, the other line
is used as an alternate.
Figure 31.4-3: 1+1 Traffic Protection Mode
Node A
Node B
subslot A
(active)
Tx
subslot A
(active)
Rx
Working
Rx
Tx
subslot B
(inactive)
Tx
Protection
Rx
subslot B
(active)
Rx
Tx
9730
In this example, the connection between the two sets of HSA cards is carried by a
working line and a protection line. The working line is the preferred line, and is
configured as the line between A subslots. The protection line is configured between
B subslots.
The active card selects traffic from a connected HSA card. The inactive card
transmits the same data as the active card, and is ready to select traffic from the
protection path when a protection switch occurs. The active card in subslot A of
node B selects data traffic from the working line until a line or card fault occurs, as
seen in Figure 31.4-4.
The control card monitors HSA cards for card and line faults, and determines the
active card based on those faults, listed in order of priority in Table 31.4-1.
HSA Cards
(400)
31.4-5


NNP 95-2035-01-00-B
Table 31.4-1: 1+1 Protection Card and Line Faults

Priority
Fault
OC-3 and
STM-1
Mapper
card lockout
forced switch
card dead
signal failure:
LOP, AIS,
UNEQ, TIM(1)
EBER
SD
manual switch
card failure
WTR
Notes
1. Line TIM applies only to OC-3 cards
A line or card fault drives a card toward being the inactive card. For example, if the
HSA card in subslot A registers an EBER, and the mate card in subslot B registers an
SD, the card in subslot B becomes the active card. The card in subslot A does not
become the active card until it registers a lower priority fault.
Figure 31.4-4: 1+1 Traffic protection Line Fault
Node X
Node Y
subslot A
(active)
Tx
subslot A
(active)
Rx
Working
Rx
RDI
subslot B
(inactive)
Tx
Protection
Rx
AIS
Tx
subslot B
(inactive)
Rx
Tx
9731
When the severity of faults on the card on node Y exceeds the severity of faults on
the mate card in subslot B, a protection switch occurs and the card in subslot B
becomes the active card, and the card in subslot A of node Y becomes the inactive
card. Figures 31.4-5 and 31.4-6 show how the switching type affects activity
switches.
31.4-6
(400)
HSA Cards

NNP 95-2035-01-00-B

If the bidirectional operating mode is configured on node X, this protection switch

is also performed by node X. If unidirectional operating mode is configured, node X
remains in the original state until card or line faults force it to switch activity. If
revertive switching mode is configured on the cards in node Y, when the card or line
faults on the card in subslot A are equal or less than the card or line faults of the card
in subslot B, card activity switches back to the original state shown in Figure 31.4-2
after the WTR timer starts and expires. If non-revertive switching mode is
configured, the original activity states do not occur until the card connected to the
working line has fewer card or line faults than the card connected to the protection
line.
Figure 31.4-5: Bidirectional Switching Mode Reaction
Node X
Bidirectional
switching mode
Node Y
subslot A
(inactive)
Tx
Working
subslot A
(inactive)
Rx
Protection
subslot B
(active)
Rx
Rx
Tx
subslot B
( active)
Tx
Rx
Tx
9732
Figure 31.4-6: Unidirectional Switching Mode Reaction
Unidirectional
switching mode
Node X
Node Y
subslot A
(active)
Tx
Rx
subslot A
(inactive)
Rx
Working
Tx
subslot B
(inactive)
Tx
Rx
Protection
subslot B
(active)
Rx
Tx
9733
HSA Cards
(400)
31.4-7


NNP 95-2035-01-00-B
Ring mode path protection switching

Ring mode protection protects each circuit on the card, and causes circuit protection
switches based on the path quality of individual circuits. In ring mode, three or more
nodes are connected as shown in Figure 31.4-7. One ring transmits data in one
direction, while the other ring transmits in the opposite direction. Each card
transmits on one ring, and receives on the other.
The node B working circuit is configured to be terminated on the card in subslot B.
The working circuit H1-B-1 receives data and passes it on to the next node. Circuit
H1-A-1 is the protection circuit.
If the quality of the path associated with circuit H1-B-1 degrades, an alternate path
is provided because the same data is actually being broadcast in both directions by
the inner and outer ring. Instead of accepting data from the circuit that has inferior
path quality, circuit H1-A-1 becomes the active circuit, and receives data from the
alternate path.
If revertive switching is selected, when the quality of the working circuit path is
equal or better than that of the protection path, H1-B-1 becomes the active circuit. If
non-revertive switching is configured, path H1-B-1 does not become the active
circuit until its path quality is better than the protection path.
31.4-8
(400)
HSA Cards

NNP 95-2035-01-00-B

Figure 31.4-7: Ring Mode

Node A
A
Tx
Rx
Rx
Tx
Rx
Tx
A
Node C
B
Tx
Tx
Rx
Rx
Tx
Rx
Node B working circuit: H1B1

Node B active circuit: H1B1
Node B
Node A
A
Tx
Rx
Rx
Tx
Rx
Tx
A
Node C
Tx
Tx
Rx
Rx
Tx
Rx
X = line or card fault

(excessive path quality statistics)
Node B working circuit: H1B1

Node B active circuit: H1A1
Node B
9729
HSA Cards
(400)
31.4-9

31.4.2

NNP 95-2035-01-00-B
Configuring Traffic Protection Switching Options

Protection switching options are used to configure how traffic protection switching
operates in 1+1 and ring traffic protection modes.
Protection switching options for 1+1 and ring modes

1+1 and ring traffic protection modes are configured with default protection
switching options. After the traffic protection mode is selected, protection switching
options can be configured. Table 31.4-2 shows the options for each card and traffic
protection mode.
Table 31.4-2: Protection Switching Options
Options
OC-3 or STM-1
Ring Mode
Mapper Card
1+1 Mode
Operation mode
switching type
OC-3 or STM-1
1+1 Mode
working card
working circuit
WTR timer
hold off timer
Traffic protection options are configured on the slot level for 1+1 protection, and on
the circuit level for ring traffic protection.
Working card
The working line is configured by selecting a card in a subslot as the working card.
The protection line is the line that is connected to the card in the other subslot. When
working card is configured in 1+1 mode, you should configure opposing subslots to
both be working subslots or protection subslots. For example, if you want to
configure subslot A of one card as the working line, you should also configure
subslot A of the connected card as the working card. A protection line is provided
by the card that is not selected to be the working card.
Working circuit
The working ring is selected by configuring the working circuit to be contained on
either the subslot A card or the subslot B card. The working ring connects to the Rx
connector of the card that contains the working circuit. The protection ring is the ring
that is connected to the Rx connector of card that does not contain the working
circuit. When the working ring is configured, you should configure opposing
subslots to both be working subslots or protection subslots. For example, if you want
to configure the ring connected to the Rx connector of subslot A to be the working
ring, you should configure each circuit to use subslot A to contain the working
circuit. The protection ring is connected to the Rx connector of the card that is not
selected to contain the working circuit.
31.4-10
(400)
HSA Cards

NNP 95-2035-01-00-B

Switching type
Switching type should be configured as either revertive or non-revertive for each
span between destination nodes. This provides a consistent working line and
protection line throughout a network.
Select revertive switching when the working line or ring is required to be the active
line or ring. In revertive mode, unless there is a problem on the working line, it is
usually receiving active data. The protection line or ring is only active when a fault
exists on the working line or ring.
Select non-revertive switching if there is no need to keep active data on the working
line. When non-revertive switching type is configured, the configuration of working
and protection lines are meaningless, because active data is received by the line or
ring that has the best line or path quality. There is no switching bias toward either
the working or protection line or ring.
Operation mode
Both HSA slots involved in a connection should be configured with the same
operation mode. If the cards in an HSA slot one node are configured for a particular
operation mode, the connected cards should also be configured for that mode.
WTR and HOLD_OFF timers
If the WTR or HOLD_OFF timer has started, it cannot be reconfigured with a new
timer value until it has completed its count and completed the protection switch. A
new configured value will be accepted, but will not take affect until the timer is next
started.
To configure HSA card traffic protection mode

CONFIG SLOT <Hn> PROTECTION
1+1
SIMPLEX
RING
SK000920
where Hn is the HSA card slot
To configure 1+1 traffic protection options

CONFIG SLOT <Hn> PROTECTION 1+1_SWITCH
UNIDIRECT/BIDIRECT*
NONREVERT*/REVERT
WORKING
WTR_TIME
<value>
SUBSLOT_A
SUBSLOT_B
SK000918
where value is a number between 0 and 60 min in increments of 1 min
HSA Cards
(400)
31.4-11


NNP 95-2035-01-00-B
To configure ring traffic protection options

CONFIG CIRCUIT <circuit> FUNCTION PATH_PROT
NONREVERT*/REVERT
WORKING_A*/WORKING_B
WTR_TIMER
HOLD_OFF
<value_1>
<value_2>
SK000919
where
circuit is a broadband ring circuit in the format Hn-pa or Hn-pa-gr-vs
value_1 is from 0 to 10 s in increments of 0.1 s
value_2 is a number between 0 and 60 min in increments of 1 min
31.4.3
Protection Switching Commands

Protection switching commands are used to force card and circuit protection
switches. All protection switching commands survive control card activity switches,
and card resets.
You can place up to three protection switch commands against a circuit pair or card:
one on each circuit or card, and one outstanding command. If the outstanding
command is a lower priority command than the one currently in place, it will be
refused in preference of the higher priority command.
If the card undergoes a system initiated protection switch, the card does revert to an
outstanding protection switch command when the event that caused the system
switch has ended.
In 1+1 mode, protection switching commands are issued against cards. In ring
mode, protection switch commands are issued against circuits.
Card or circuit lockout

Card or circuit lockout prevents traffic from being received from the selected card or
circuit. This command is refused if the mate card or circuit is already locked out.
Forced switch
In 1+1 protection mode, a forced switch command prevents traffic from being
received from the selected card unless the mate card is already locked out. If this
command is issued against the working card, the request is blocked if the protection
card is under failure conditions.
In ring protection mode, this command prevents traffic from being selected from the
selected circuit, unless the mate circuit is locked out.
31.4-12
(400)
HSA Cards

NNP 95-2035-01-00-B

Manual switch
This command prevents traffic received on the selected card or circuit from being
selected, unless:
the card or circuit is locked out

the received traffic was previously being selected as the result of a force switch
command against a mate ring circuit

the mate ring circuit is in SF or SD
Clear command
A clear protection switch command clears all protection switch commands that are
in place against a card or circuit.
To issue protection switching commands

MAINT
ON_SLOT
ON_CIRCUIT
<Hn-ss>
<circuit>
PROTECTION
PROTECTION
LOCK_OUT
FORCED_SW
MANUAL_SW
CLEAR
SK000921
where
Hn-ss is the HSA slot and sub-slot
circuit is the selected circuit
HSA Cards
(400)
31.4-13

NNP 95-2035-01-00-B
31.5
31.5 OC-3 and STM-1 Card Port Synchronization

OC-3 and STM-1 Card Port

Synchronization
This chapter explains how to configure OC-3 and STM-1 card port synchronization.
31.5.1
Understanding OC-3 or STM-1 Card Port Synchronization

You can configure an OC-3 or STM-1 card to use one of three different port
synchronization modes to synchronize its Tx line: system, self or through.
Synchronization sources
System mode selects the 19.44 MHz system timing source to synchronize the port Tx
line.
Self mode selects an internal timing loop, where the card uses its recovered Rx line
signal to synchronize the port Tx line.
Through mode allows an OC-3 or STM-1 card to synchronize its Tx line to the
recovered clock signal of another HSA card. Any OC-3 or STM-1 card slot can be
selected as a timing source.
Slot options for port synchronization

If an HSA slot is configured for simplex or 1+1 traffic protection, port
synchronization is configured on the slot level, affecting the card in each subslot. For
example, enter <H1> if you want to configure port synchronization on a card in
HSA slot 1 that is configured for 1+1 or simplex mode.
If an HSA slot is configured for ring traffic protection, port synchronization is
configured on the slot level or subslot level. For example, enter <H1> if you want
to configure port synchronization on both cards in HSA slot 1. Enter <H1-A> if you
want to configure port synchronization on the card in subslot A of HSA slot 1.
If through mode is being configured, the synchronization source is selected on the
basis of slot identifier if the source is 1+1 or simplex-protected. If the source is
ring-protected, the subslot identifier is selected. If the source subslot is 1+1
protected, synchronization is provided by the active card.
If through mode is configured on a ring-protected card, it synchronizes to the signal
recovered from the card in the other subslot. You cannot select another HSA slot as
a synchronization source.
HSA Cards
(400)
31.5-1
31.5 OC-3 and STM-1 Card Port Synchronization


NNP 95-2035-01-00-B
To configure OC-3 or STM-1 card port synchronization

CONFIG SLOT <Hn> or <Hn-ss> OPTIONS PORT SYNCH
SYSTEM
SELF
THROUGH
<Hn> or <Hn-ss>
SK000901
31.5-2
(400)
HSA Cards

NNP 95-2035-01-00-B
31.6
31.6 Broadband Circuits

Broadband Circuits
This chapter explains how to:
configure broadband circuit structure

how to provision mapper card broadband circuits
how to copy and name circuits
31.6.1
Understanding Broadband Circuits

You can configure broadband circuits on the following cards:
OC-3
STM-1
VT-1.5 mapper
TU-12 mapper
OC-3 and STM-1 card broadband circuits

OC-3 and STM-1 card broadband circuits can be configured to have different
broadband structures and sub-structures by dividing the bandwidth of large
broadband circuits into smaller broadband circuits.
On the OC-3 card, smaller circuits are contained and configured on STS-1 structures.
On the STM-1 card, smaller circuits are contained and configured on AU-3
structures if the card is configured for AU-3 mode, or on an AU-4 structure if the
card is configured for AU-4 mode.
STS-1 structures can be configured to contain VT groups, and AU-3 and AU-4
structures can be configured to contain TUG-2s. A VT group structure can be
configured to contain VT-1.5, VT-2, VT-3 or VT-6 circuits, which can be connected to
compatible broadband circuits. AU-3 or AU-4 structures can be configured to
contain TUG-2s. A TUG-2 can be configured to contain TU-11, TU-12 or TU-2
circuits, which can be connected to compatible broadband circuits.
Warning
When VT or TU structure is changed, the statistics for the circuits in the new VT or
TU structure are set to zero. All statistics relating to the previously existing circuits
are permanently erased. They cannot be viewed by reverting to the previous VT or
TU structure.
HSA Cards
(400)
31.6-1


NNP 95-2035-01-00-B
VT-1.5 and TU-12 mapper card broadband circuits

Circuit provisioning is the only configurable option for mapper card broadband
circuits. VT-1.5 mapper cards contain VT-1.5 broadband circuits, and TU-12 mapper
cards contain TU-12 broadband circuits.
Each mapper card broadband circuit has a fixed connection to an associated
narrowband port on the same mapper card. When mapper card broadband circuits
are connected to broadband circuits on OC-3 or STM-1 cards, mapper cards
transport narrowband DS0 based data and voice from circuits connected to the
narrowband port to a SONET or SDH network.
31.6.2
Configuring OC-3 Card Circuit Structure

Each OC-3 card contains three STS-1 structures, which are the largest structures
available on OC-3 cards.
An STS-1 structure can be further configured as a bulk payload or VT group
sub-structure. If it is configured as a bulk payload substructure, it is considered to
be an STS-1 circuit. If it is configured as VT group structured, it is considered to be
an STS-1 link.
An STS-1 link is divided into seven VT groups. The VT groups are further divided
into connectable VT circuits. Each VT group can be configured to accommodate one
of the following configurations:
four VT 1.5s
three VT-2s
two VT-3s
one VT-6
Each different VT type has a different bandwidth capability.

Figure 31.6-1 shows the structure of the circuits for an OC-3 card.
31.6-2
(400)
HSA Cards

NNP 95-2035-01-00-B

Figure 31.6-1: OC-3 Card Circuit Structure
VT - 1.5
or
VT - 2
x4
x3
or
or
VT - 3
x2
VT - 6
x1
VT group
x7
STS - 1 link
or
x3
STS - 1 circuit
x3
OC - 3
9627
To configure an STS-1 as a link or circuit

CONFIG CIRCUIT <Hn-ss-pa> VT_GROUP*/ BULK_PAYLOAD
where
selecting VT_GROUP configures the STS-1 as a link
selecting BULK_PAYLOAD configures the STS-1 as a circuit
To configure STS-1 link VT structure

CONFIG SLOT <Hn-ss-pa> FUNCTION VTG_CONFIG
<vtgnum>
VT_1.5*
VT_2
VT_3
VT_6
SK000922
where vtgnum is a VT group number between 1 and 7
HSA Cards
(400)
31.6-3

31.6.3

NNP 95-2035-01-00-B
Configuring STM-1 Card Circuit Structure

An STM-1 card can be configured for either AU-3 or AU-4 mode. Each mode
provides different internal circuit structure options.
When the SDH mode is changed from AU-3 to AU-4, or AU-4 to AU-3, the card
resets, and all programmed connections for the card are lost.
In AU-3 mode, the STM-1 card contains three AU-3 structures, which are the
primary AU-3 mode SDH circuits. An STM-1 card that is configured for AU-4 mode
contains a single AU-4 structure, which is the largest AU-4 mode SDH structure.
An AU-3 can be configured as C3 or TUG-2 sub-structure. If an AU-3 is configured
as a C3 sub-structure, it is considered to be circuit. If an AU-3 is configured as a
TUG-2 sub-structure, it is considered to be a link.
An AU-3 link is divided into seven TUG-2s which contain connectable TU circuits.
Figure 31.6-2 shows the circuit structure for AU-3 mode.
Figure 31.6-2: STM-1 Card AU-3 Mode
TU-11
or
TU-12
x4
x3
or
TU-2
x2
TUG-2
x7
AU-3 link
x3
or
AU-3 circuit
x3
STM-1
9628
The STM-1 card AU-4 link contains three TUG-3s. Each TUG-3 has the same
bandwidth as an AU-3, and like an AU-3, can be configured as a link or as a circuit.
A TUG-3 can be configured to accommodate:
seven TUG-2s (TUG-3 link)

one TU-3 (TUG-3 circuit)
Figure 31.6-3 shows the circuit structure for AU-4 mode.
31.6-4
(400)
HSA Cards

NNP 95-2035-01-00-B

Figure 31.6-3: STM-1 Card AU-4 Mode
TU-11
TU-12
x4
TU-2
x3
x1
TUG-2
or
x7
TU-3
x1
TUG-3
x3
AU-4 link
STM-1
9629
TUG-2s are available on AU-3 and TUG-3 links. In either mode, a TUG-2 can
accommodate one of the following configurations:
four TU-11s
three TU-12s
one TU-2
In AU-4 mode, an AU-4 is divided into three TUG-3 structures. Each of the three
TUG-3 structures can be configured as TUG-2 structured, or TU-3 structured. TUG-2
mode must be selected before TUG-2 sub-structure is configured. If TU-3 structure
is selected, the TUG-3 is mapped as a TU-3 circuit.
HSA Cards
(400)
31.6-5


NNP 95-2035-01-00-B
To configure SDH mode

Warning
When the SDH mode is changed from AU-3 to AU-4, or AU-4 to AU-3, the card
resets, and all programmed connections for that STM-1 card are lost.
CONFIG SLOT <Hn-ss> OPTIONS PORT SDH_FORMAT AU-4* or AU-3
To configure an AU-3 as a link or circuit

CONFIG CIRCUIT <Hn-ss-pa> FUNCTION TUG2*/ C3
where
selecting TUG2 configures the AU-3 as a link
selecting C3 configures the AU-3 as a circuit
To configure TUG-3 structure

CONFIG CIRCUIT <Hn-ss-pa> FUNCTION TUG-2*/ TU3
where
Hn-ss-pa is a TUG-3
selecting TUG-2 configures the TUG-3 as a link
selecting TU3 configures the TUG-3 a circuit
To configure TUG-3 or AU-3 TUG-2 structure

CONFIG SLOT <Hn-ss-pa> FUNCTION TUG-2_CFG
<tugnum>
TU2
TU11
TU12*
SK000894
where
Hn-ss-pa is an AU-3 or TUG-3 identifier
tugnum is a TUG-2 number between 1 and 7
31.6-6
(400)
HSA Cards

NNP 95-2035-01-00-B
31.6.4

Configuring Mapper Card Broadband Circuits

Mapper cards do not provide a varied broadband circuit structure. The VT-1.5 card
contains only VT-1.5 circuits, and the TU-12 card contains only TU-12 circuits.
Broadband circuit provisioning is the only configurable functional parameter for
mapper card broadband circuits.
Configuring broadband circuit provisioning

A broadband circuit can be provisioned as either enabled or disabled.
All unconnected mapper card broadband circuits should be configured with
provisioning disabled, or the associated narrowband port constantly raises AIS
alarms. A broadband circuit that is configured with provisioning disabled cannot be
connected to another circuit until provisioning is configured as enabled.
You can configure broadband circuit provisioning as disabled if:
the circuit is not connected

none of the circuits on the associated narrowband port are connected
To configure mapper card broadband circuit provisioning
Note
If a circuit is provisioned as disabled, all statistics for that circuit are reset, and any
stored statistics from previous intervals are permanently erased.
CONFIG CIRCUIT <Hn-Vvs> or <Hn-Tvs> FUNCTION PROVISION

ENABLE*/DISABLE
where Hn-Vvs is a VT-1.5 circuit and Hn-Tvs is a TU-12 circuit
31.6.5
Copying and Naming Circuits

After broadband circuits have been configured, you can copy their configuration to
other circuits, and provide each circuit with a name for the purpose of identification.
Copying and naming circuits

If you want to configure many circuits to be the same, you can configure one, then
copy all parameters except the name and connection to each other circuit in turn
using the COPY_TO softkey.
HSA Cards
(400)
31.6-7


NNP 95-2035-01-00-B
All destination circuits must be of the same type as the source circuit, or the
operation will be blocked. You can copy the configuration information of a link to a
circuit, but the destination will change configuration to become a link.
You can assign a name to any broadband circuit, using the NAME softkey. To delete
a circuit name without assigning another one, select NAME and press .
To copy or name circuits

CONFIG CIRCUIT <circuit>
NAME
COPY_TO
COPY_RANGE
<name>
<circuit>
<circuit>
TO
<circuit>
SK000917
where
name is up to 8 alphanumeric characters
the first circuit is the source circuit identifier
the second circuit is the identifier of the destination circuit or the first circuit of the destination range
the third circuit is the last circuit of the destination range
31.6-8
(400)
HSA Cards

NNP 95-2035-01-00-B
31.7
31.7 Broadband Signal Labels

Broadband Signal Labels

This chapter explains how to configure broadband signal labels.
31.7.1
Understanding Broadband Signal Labels

A broadband signal label tells the receiving device what type of payload is contained
in the incoming broadband signal. If the signal label is configured incorrectly, the
receiving device may not be able to demultiplex or decode the signal for the purpose
of dropping data onto an access node.
You can configure broadband signal labels on the following HSA card links and
circuits:
31.7.2
OC-3 card STS-1 links

STM-1 card AU-3 and AU-4 links
VT-1.5 card VT-1.5 circuits
TU-12 card TU-12 circuits
Configuring Broadband Signal Labels

A broadband signal label code can be:
unequipped
equipped, non-specific payload
equipped with a specific payload indicated
An unequipped signal label indicates a signal that contains no data. The signal is
routed to the destination device, but the device does not interpret or pass data from
the signal. You cannot configure a OC-3 or STM-1 card broadband signal label as
unequipped.
An equipped signal label indicates a signal that is expected to contain data. If a link
or circuit with an equipped signal is connected to a distant node, the signal label tells
the node that data is present in the payload, and specifies the format of the data.
An equipped-nonspecific payload is used to pass data to a node that does not
support payload-specific signal labels.
Table 31.7-1 shows the signal label options for the applicable cards and circuits.
HSA Cards
(400)
31.7-1
31.7 Broadband Signal Labels


NNP 95-2035-01-00-B
Table 31.7-1: Signal Label Options

Card
Link or Circuit
Signal Label
Option
OC-3
STS-1 link
equipped-nonspecific payload
equipped-VT-structured
NON_SPECIF
VT_STRUCT
STM-1
AU-3 or AU-4 link
equipped-TUG structured
NON_SPECIF
TUG_STRUCT
VT-1.5
VT-1.5 circuit
equipped-asynchronously mapped DS1
NON_SPECIF
ASYNC_DS1
TU-12
TU-12 circuit
equipped-asynchronously mapped E1
NON_SPECIF
ASYNC_E1
To configure the OC-3 card STS-1 signal label

CONFIG CIRCUIT <Hn-ss-pa> FUNCTION SIG_LABEL NON_SPECIF or
VT_STRUCT
To configure the STM-1 card AU-3 signal label

CONFIG CIRCUIT <Hn-ss-pa> FUNCTION SIG_LABEL NON_SPECIF or
TUG_STRUCT
To configure the STM-1 card AU-4 signal label

CONFIG CIRCUIT <HnAU4> FUNCTION SIG_LABEL NON_SPECIF or
TUG_STRUCT
To configure a VT-1.5 card VT- 1.5 circuit signal label

CONFIG CIRCUIT <Hn-Vvs> FUNCTION SIG_LABEL NON_SPECIF or
ASYNC_DS1
To configure a TU-12 card TU-12 circuit signal label

CONFIG CIRCUIT <Hn-Tvs> FUNCTION SIG_LABEL NON_SPECIF or
ASYNC_E1
31.7-2
(400)
HSA Cards

NNP 95-2035-01-00-B
31.8
31.8 SONET and SDH Data Communication Channels

SONET and SDH Data

Communication Channels
This chapter explains how to configure the section DCC on OC-3 and STM-1 cards.
31.8.1
Configuring the OC-3 or STM-1 Card Section DCC

An OC-3 or STM-1 card DCC is a data communications channel that is used to
provide level 1 intermediate system OSI routing in accordance with the
GR-255-CORE SONET standard and the ITU-T G.784 SDH standard. When the DCC
is enabled, the 3600+ MainStreet system routes OSI messages from other SONET or
SDH networks to appropriate destination nodes.
The OC-3 and STM-1 cards both support a reserved DCC bandwidth of 192 kb/s.
Before configuring the DCC on OC-3 and STM-1 cards, you must first configure the
3600+ MainStreet NET address.
On the OC-3 card, you can enable the section DCC, and on the STM-1 card you can
enable the regenerator section DCC. When the DCC is enabled, the system assigns
three HDLC resources to the DCC. If three HDLC resources are not available, the
system will block any attempt to enable the DCC.
The OC-3 and STM-1 card DCCs are not protected if the card is in simplex traffic
protection mode. For DCC protection, you must configure the card for 1+1 or ring
traffic protection mode.
To configure the OC-3 card DCC

CONFIG SLOT <Hn-ss> PORT DCC ENABLE/DISABLE*
To configure the STM-1 card DCC

CONFIG SLOT <Hn-ss> PORT RS_DCC ENABLE/DISABLE*
HSA Cards
(400)
31.8-1

NNP 95-2035-01-00-B
31.9
31.9 Broadband Circuit Connections

Broadband Circuit Connections

This chapter gives you an overview of:
the types of broadband circuit connections

how to view broadband circuit connections
how to configure broadband circuit connections
31.9.1
Understanding Broadband Connections

The three types of broadband connections are:
bidirectional
pass-through
UPSR add-drop
Broadband circuit connections are connections between two or more broadband
circuits.
Broadband circuits can be connected to other broadband circuits of equal
bandwidth. Table 31.9-1 shows the valid circuit connections for HSA cards.
Table 31.9-1: Valid Broadband Circuit Connections
Circuit Type
HSA Cards
Valid Connected Circuit
AU-3 (C3)
AU-3 (C3), TU-3 and STS-1
TU-3
AU-3 (C3), TU-3 and STS-1
TU-2
TU-2, VT-6
TU-12
TU-12, VT-2
TU-11
TU-11, VT-1.5
STS-1
STS-1, AU-3 (C3), TU-3
VT-6
VT-6, TU-2
VT-3
VT-3
VT-2
VT-2, TU-12
VT-1.5
VT1.5, TU-11
(400)
31.9-1


NNP 95-2035-01-00-B
Viewing circuit connections

To view circuit connection information from a card, select SHOW_CCT or
SHOW_GROUP. If you have configured a protecting connection, it also appears.
SHOW_GROUP displays a group of circuits adjacent to the specified circuit.
Figure 31.9-1 shows a typical display for a 3600+ MainStreet system. Table 31.9-2
lists and describes the symbols on these displays.
Figure 31.9-1: Circuit Connection Display
3600+ MainStreet
Circuit
S1117-H1-00
Name
Toronto:A
Type
H2-V01
VT-1.5
UPSR Add/Drop Protected By
Alarms:1
Circuit
<->
->
H1-A-1-1-01
H1-B-1-1-01
11-May-1997
8:35a
Name
Type
Mode
NbrigeA
VT-1.5
VT-1.5
Work
Prot
* = Active connect; ! = Maintenance connect

CONFIG CONNECT H2-V1
1-SHOW_GROUP
6-UPSR
2-DISCONNECT
7-
3-TO_CIRCUIT
8-CANCEL
4-PASS_THRU
9-QUIT
5-RAP+ID
0-
Table 31.9-2: Circuit Connection Display Symbols

Symbol
31.9-2
Description
blank
There is no connection.
<>
Indicates a bidirectional connection. If the bidirectional connection is UPSR

protected, the protection circuit is indicated beneath as a unidirectional
connection.
>
The circuit listed to the right of the symbol is the protection circuit in a UPSR
protected connection.
The circuit is under maintenance.

*
The circuit is physically connected.
(400)
HSA Cards

NNP 95-2035-01-00-B

To view circuit connection information

CONFIG CONNECT <circuit> SHOW_GROUP/SHOW_CCT*
where circuit is a broadband circuit
31.9.2
Bidirectional Broadband Circuit Connections

Bidirectional connections provide two paths between source and destination
devices: one transmit path and one receive path. Data and signalling pass back and
forth between the source and destination devices. Bidirectional connections can be
used to connect any broadband circuit to another broadband circuit, regardless of
what traffic protection mode is configured on either card.
Two types of bidirectional broadband connections are supported by the
3600+ MainStreet system:
simple bidirectional connections

terminal add-drop connections
A simple bidirectional connection is a bidirectional connection between any two
circuits on non-ring protected cards. When a bidirectional connection is made
between a circuit on a ring protected card and a non ring protected card, the
connection is called a terminal add-drop connection. Both types of bidirectional
connections are configured in the same way.
Figure 31.9-2 demonstrates a bidirectional connection between two VT-1.5 circuits.
Figure 31.9-2: Simple Bidirectional Connections
First
STS-1
VTG-1
VTG-2
VTG-3
Second
STS-1
First
VT1.5
VTG-1
Second
VT1.5
Second
VT1.5
VTG-3
VTG-4
VTG-5
Third
STS-1
First
VT1.5
VTG-6
VTG-7
VTG-2
VTG-4
Third
VT1.5
Third
VT1.5
Fourth
VT1.5
Fourth
VT1.5
to
H1 OC-3 card
H1-A-1-1-1
First
STS-1
Second
STS-1
VTG-5
VTG-6
Third
STS-1
VTG-7
H2 OC-3 card
H2-A-3-3-2
9425
Use the following softkey sequence to connect a simple bidirectional or terminal

add-drop connection.
HSA Cards
(400)
31.9-3


NNP 95-2035-01-00-B
To configure simple bidirectional or terminal add-drop connections

CONFIG CONNECT <circuit_1> TO_CIRCUIT <circuit_2> PROCEED
where
circuit_1 is Hn-gr, Hn-gr-vs-pa, Hn-Vvs or Hn-Tvs
circuit_2 is the broadband circuit to be connected to circuit_1
Note
If the first circuit is already connected, a warning appears after you select
TO_CIRCUIT, but you can proceed. If you proceed, the previous connection is
broken. After you enter the identifier of the second circuit, a warning appears and
the connection is broken if that circuit is already connected.
To disconnect a bidirectional circuit

Bidirectional connections can be disconnected in one of the following two ways:
manual disconnection
configuring a new connection
A manual disconnection severs the existing connection, leaving the two circuits
disconnected. If two broadband circuits are connected, and a new connection is
configured for one of the circuits, the new connection is made, and the previous
connection is severed.
CONFIG CONNECT <circuit> DISCONNECT PROCEED
where circuit is a connected broadband circuits
31.9.3
Pass-through Connections
A pass-through connection is used to cross connect circuits on two distant nodes by
passing the connection transparently through an intermediate node. No data
dropping or adding occurs on the intermediate node.
A pass-through connection connects two circuits that appear in the same bandwidth
position on each ring. For example, a pass-through connection is made from the first
VT-1.5 to the first VT-1.5 on the mate card.
A pass-through connection made between two VT-1.5 circuits is shown in
Figure 31.9-3.
31.9-4
(400)
HSA Cards

NNP 95-2035-01-00-B

Figure 31.9-3: Pass -through Connection
First
STS-1
VTG-1
VTG-2
VTG-3
Second
STS-1
First
VT1.5
VTG-1
Second
VT1.5
Second
VT1.5
VTG-3
VTG-4
VTG-5
Third
STS-1
First
VT1.5
VTG-6
VTG-7
VTG-2
VTG-4
Third
VT1.5
Third
VT1.5
Fourth
VT1.5
Fourth
VT1.5
to
H1-A OC-3 card

H1-A-1-1-1
First
STS-1
Second
STS-1
VTG-5
VTG-6
Third
STS-1
VTG-7
H2-B OC-3 card
H1-B-1-1-1
9427
Note
A pass-through connection involving STS-1, TU-3 or AU-3 circuits is switched
through leaving the higher order path labels unaltered.
To configure a pass-through connection

A pass-through connection automatically connects a specified circuit on one subslot
to the corresponding circuit on the mate subslot.
CONFIG CONNECT <circuit> PASS_THRU
where circuit is one of two broadband circuits to be connected
To disconnect a pass-through connection

CONFIG CONNECT <circuit> DISCONNECT
where circuit can be either of the circuits to be disconnected
31.9.4
UPSR add-drop connections

A UPSR add-drop connection allows a mapper card add-drop circuit to select data
from both rings. This connection type connects an add-drop circuit to the working
ring circuit and the protection ring circuit in ring mode. The mapper card
Figure 31.9-4 shows a typical connection.
HSA Cards
(400)
31.9-5


NNP 95-2035-01-00-B
Figure 31.9-4: UPSR Add-Drop Connection
First
STS-1
VTG-1
VTG-2
VTG-3
Second
STS-1
First
VT1.5
VTG-1
Second
VT1.5
Second
VT1.5
VTG-3
VTG-2
VTG-4
VTG-5
Third
STS-1
First
VT1.5
VTG-6
VTG-7
VTG-4
Third
VT1.5
Third
VT1.5
Fourth
VT1.5
Fourth
VT1.5
H1-A OC-3 card

First STS-1
First VT group
First VT1.5
VT1.5
First
STS-1
Second
STS-1
VTG-5
VTG-6
Third
STS-1
VTG-7
H2-B OC-3 card
First STS-1
First VT group
First VT1.5
(Add/Drop Circuit)
H3 Mapper card
First VT1.5
9428
To configure a UPSR add-drop connection

Use the following softkey sequence to configure a UPSR add-drop connection:
1.
Make a terminal add-drop connection between a mapper card circuit and a ring
circuit.
2.
Configure the connection as UPSR protected by entering:

CONFIG CONNECT <circuit> UPSR
where circuit is one of the circuits in the terminal add-drop connection
To disconnect all circuits in a UPSR add-drop connection

CONFIG CONNECT <add_drop > DISCONNECT ALL
where add_drop is the add-drop circuit to be disconnected
To disconnect a UPSR add-drop connection from a single ring

To disconnect at the ring circuit, enter:
CONFIG CONNECT <circuit> DISCONNECT
To disconnect at the add-drop circuit:

1.
Indicate the add-drop circuit by entering:

CONFIG CONNECT <Hn-Vvs> or <Hn-Tvs> DISCONNECT
31.9-6
(400)
HSA Cards

NNP 95-2035-01-00-B
2.
HSA Cards

Indicate the ring to be disconnected from as follows:

a.
To disconnect from a ring terminated on subslot A (non-revertive

switching), select RING_A.
b.
To disconnect from a ring terminated on subslot B (non-revertive

switching), select RING_B.
c.
To disconnect from a ring terminated on the working subslot (revertive

switching), select WORKING.
d.
To disconnect from a ring terminated on the protection subslot (revertive

switching), select PROTECTION.
(400)
31.9-7

NNP 95-2035-01-00-B
31.10

Mapper Card Super-rate Circuits

This chapter introduces super-rate circuits for VT-1.5 and TU-12 mapper cards.
31.10.1
Understanding Super-rate Circuits for Mapper Cards

You can configure super-rate circuits on mapper card narrowband ports. Super-rate
speeds are interface speeds that are greater than 64 kb/s. Super-rate circuits occupy
more than one DS0.
Super-rate configuration requires one master circuit and one or more slave circuits.
The master circuit is the first DS0 used; the slave circuits are the DS0s that follow.
Note
A circuit must be disconnected before it can be configured for super-rate operation,
and super-rate configuration cannot overlap connected circuits. You must first
disconnect any circuits that are required for super-rate operation.
Super-rate configuration can be done at two levels:
preferred (the set of DS0s that you prefer for the data transmission)
level 2 (the set of DS0s used to protect the preferred super-rate)
Note
A DS0 may be involved in a level 2 super-rate connection without being involved in
a preferred super-rate connection.
Contiguous super-rate circuits

A contiguous super-rate circuit uses the master circuit as a starting point and then
takes the slave circuits from DS0s that immediately follow the master circuit DS0.
When you enter the master circuit, the system reserves the required number of slave
circuits from the DS0s immediately following the master circuit.
HSA Cards
(400)
31.10-1


NNP 95-2035-01-00-B
Non-contiguous super-rate circuits

A non-contiguous super-rate circuit allows the use of non-consecutive DS0s. To
configure a non-contiguous super-rate, you make a list of circuits using the
<Return> key and a range of circuits using the colon (:) key. For example, a 512 kb/s
super-rate circuit needs a total of 8 DS0s (64 kb/s circuits) that you enter as:
<1> <3> <5:10>
You must enter the DS0s from the lowest to the highest number. If you try to enter
the circuits in a non-ascending order, the system displays the message Circuits
must be specified in ascending order.
For TU-12 card narrowband ports with 31_CHAN configured, circuit 31 is between
circuits 15 and 16 in time, but you still specify it at the end of the list. For example, a
valid list is:
<1> <14:15> <17> <31>
A valid list of five DS0s is:
<14:17> , which is equivalent to <14> <15> <16> <17> <31>
If circuit 31 is the master on an TU-12 card narrowband port with 31_CHAN
configured, it becomes the only case in which the master circuit is the last, not the
first, circuit in the list. Circuit 31 cannot be used for super-rate circuits on an TU-12
card narrowband port with CCS configured.
In a unidirectional connection, a circuit can be part of one super-rate group as a
source and part of another super-rate group as a destination; you can configure the
source and destination super-rate groups for different speeds. For example, circuits
1, 3, 5 and 7 can be a source super-rate group at 256 kb/s and circuits 1 to 6 a
destination super-rate group at 384 kb/s.
If you try to enter a circuit that is a master in another list, the system displays the
message Warning. That circuit is already a super-rate master. If you try to enter a
circuit that is a slave in another list, the system displays the message Warning. That
circuit is already a super-rate slave.
Equidistant super-rate circuits

An equidistant super-rate circuit spaces the DS0s evenly over the entire link after the
bandwidth is set. TU-12 card narrowband ports configured for CAS- and
CCS-framing formats support equidistant super-rate circuits. Figure 31.10-1 shows
the equidistant super-rate format for each bandwidth.
31.10-2
(400)
HSA Cards

NNP 95-2035-01-00-B

Figure 31.10-1: Equidistant Super-rate DS0s on TU-12 Card Narrowband Ports

Bandwidth
(DS0s)
16
30
Bandwidth
(DS0s)
Bandwidth
(kb/s)
128
256
512
1024
1920
Bandwidth
(kb/s)
Circuit
Number
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
31 (1)
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
Timeslots
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
0
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
Note
Circuit 31 is only available when the narrowband E1 port is configured for
31_CHAN or CCS framing types, and cannot be involved in a super-rate
configuration on CCS configured links.
Protecting super-rate circuits

A super-rate circuit can be protected by another circuit configured for the same
speed at level 2.
If the protecting circuit is involved in a preferred connection, and the protecting
circuit fails, the connection with the protecting circuit is torn down. DS0s that are
part of a voice compression subframe cannot be used as protecting circuits for
super-rate circuits. This protecting connection is blocked.
HSA Cards
(400)
31.10-3


NNP 95-2035-01-00-B
Super-rate circuits can protect voice or data connections. If the preferred connection
is broken, the entire super-rate connection is broken and the protecting DS0 is
connected to the voice or data circuit.
31.10.2
Configuring Super-rate Circuits for Mapper Cards

1.
To configure the super-rate circuit, enter the circuit identifier of the master DS0,
select NUM_CIRCS, and configure the super-rate circuit at the connection level
as:
PREFERRED for preferred

LEVEL_2 for level 2
2.
Enter the number of DS0s in the super-rate bundle. The valid range for the
number of the DS0 depends on which timeslot in the narrowband port is
occupied by the master DS0 in the super-rate connection. If there are not
enough timeslots in the primary rate link for the number of circuits in the
super-rate connection, the system displays an error message.
3.
After you enter the number of DS0s, configure the super-rate format as:
CONTIGUOUS for a contiguous super-rate circuit

NON_CONTIG for non-contiguous super-rate circuit
EQUIDIST for equidistant super-rate circuits (on TU-12 card CAS- or
CCS-framed circuits only)
For non-contiguous circuits, enter a list of the DS0s in the super-rate bundle.
4.
After you have configured the first super-rate bundle, repeat the process for the
connecting super-rate circuit, and enter the same number of circuits as for the
first bundle.
Note
A single DS0 may be configured for both a preferred super-rate connection at one
speed and a level 2 super-rate connection at another speed. A DS0 may be involved
in a level 2 super-rate connection without being involved in a preferred super-rate
connection.
31.10-4
(400)
HSA Cards

NNP 95-2035-01-00-B

To configure a tandem super-rate circuit

CONFIG SYNCH
MORE
SELECT/
DESELECT*
CLASS
NODE_CLASS
SRC_NUMBER
<class>
<source>
<class>
STATUS_MSG
THRESHOLD
RECOVERY
SOURCE
ENABLE/
DISABLE*
DERIVED
UNDEFINED
RX_ENABLE/
RX_DISABLE
AUTO
EXT_PORT_A
30_SEC
1_MIN
10_MIN
EXT_PORT_B
30_MIN
MANUAL
<sn> or <sn-l> or <Hn> or <Hn-ss>

SK000898
where
between n3 and n4)
To deconfigure a super-rate bundle

To deconfigure the super-rate bundle, enter 0 or 1 for the number of DS0s in the
circuit. You must disconnect the circuit before you deconfigure it.
HSA Cards
(400)
31.10-5

NNP 95-2035-01-00-B
31.11

Zero Code Suppression for

Narrowband Ports
This chapter explains how to configure zero code suppression for VT-1.5 card
narrowband T1 ports.
31.11.1
Understanding Zero Code Suppression for VT-1.5 Card

Narrowband T1 Ports
Line synchronization is lost if too many consecutive zeros are transmitted on the
link. Zero code suppression provides sufficient ones density to ensure that line
synchronization is maintained. Table 31.11-1 lists the types of zero code suppression
supported on cards that provide this option. The type of zero code suppression you
select applies to all circuits on a narrowband T1 port.
Table 31.11-1: Zero Code Suppression Options
Framing
Option
Transparent
TRANSP
Jam Bit 7
JB7*
Caution
The same type of zero code suppression must be configured at both ends of a
narrowband T1 port.
Transparent framing
The transparent option means that the system does not perform zero suppression.
Devices cross-connected to this narrowband T1 port must use a protocol designed to
ensure a sufficient ones density pattern to avoid line synchronization problems.
Caution
The transparent setting should be used with caution as network equipment could
lose synchronization if the ones density requirement is not satisfied.
HSA Cards
(400)
31.11-1


NNP 95-2035-01-00-B
Jam Bit 7 framing

Jam Bit 7 changes bit 7 (the next-to-least significant bit) to a 1 if all eight bits of the
word are 0. Do not select JB7 if 64 kb/s clear data channels are required (either
channels for which signalling is not passed, or channels configured for TS24
signalling).
To configure zero code suppression for narrowband DS1 ports

CONFIG SLOT <Hn-c> OPTIONS ZERO_SUPPR
TRANSP
JB7*
SK000862
31.11-2
(400)
HSA Cards

NNP 95-2035-01-00-B
31.12

Narrowband Port Trunk

Conditioning
This chapter introduces trunk conditioning for mapper card narrowband ports and
explains how to configure trunk conditioning.
31.12.1
Understanding Trunk Conditioning for Mapper Cards

When a mapper card narrowband port experiences a fault, trunk conditioning is
applied to all circuits on that narrowband port. The type of trunk conditioning you
configure for a narrowband port determines on which paths (information or
signalling) and in which directions (transmit or receive) fault signalling is
transmitted. You can enable or disable trunk conditioning independently for
different classes of link faults, and you can configure trunk conditioning
independently for each narrowband port.
Each narrowband port is made up of two components:
an information component that carries the circuit's payload, data or voice

a signalling component that carries signalling, when signalling is enabled
Trunk conditioning direction is defined with respect to a circuit on the faulty link.
The transmit direction is defined by the transmit path from the circuit to its
connected circuit.
The receive direction is defined by the receive path from the connected circuit to
its circuit.
Mapper cards support one-way and two-way trunk conditioning. The default trunk
conditioning direction is two-way.
Note
Regardless of the type of trunk conditioning configured, two-way trunk
conditioning is applied to circuits that are cross-connected to CPSS circuits and voice
compression subframes.
HSA Cards
(400)
31.12-1


NNP 95-2035-01-00-B
One-way trunk conditioning

When you configure one-way trunk conditioning, the signalling path or the
information path, or both (depending on the fault), are broken in the transmit
direction only. Transmission in the receive direction is not affected.
One-way trunk conditioning operates differently for each of three groups of link
faults. Table 31.12-1 lists the effect on the signalling and information path for each
group of link faults when one-way trunk conditioning is selected. One-way trunk
conditioning does not affect Group 3 link faults.
After breaking the signalling or information path in the transmit direction, the
aggregate interface card circuit transmits the fault signalling it was configured with,
or a special code, to the connected circuit. Table 31.12-1 lists the type of code
transmitted for each type of connected circuit. If a signalling or information path is
not broken, the aggregate interface card continues to transmit what it receives.
Table 31.12-1: One-way Trunk Conditioning Link Faults
Card
Link Faults
Signalling Path
Information Path
Group 1 Link Faults

TU-12
Framing Alarm
AIS
Framing Error Rate
Exceeded
Failed State

direction

direction
VT-1.5
Red Alarm
Framing Error Rate
Exceeded
Failed State

direction

direction
Multi-frame Alarm
Incoming TS16 AIS

direction
No change
TU-12
Distant Alarm
TS16 Distant Alarm
No change
No change
VT-1.5
Yellow Alarm
No change
No change
Group 2 Link Faults

TU-12
Group 3 Link Faults
Note
One-way trunk conditioning does not result in the information or the signalling path
being broken in either direction, because the fault lies in the narrowband port circuit
receive path.
31.12-2
(400)
HSA Cards

NNP 95-2035-01-00-B

Table 31.12-2: One-way Trunk Conditioning Signalling and Information Path Codes
Code
Non-Aggregate Interface Card

Connected Circuit
Aggregate Interface Card

Connected Circuit
Code Transmitted on
Signalling Path
Signalling state at time of fault
Code Transmitted on
Information Path
All zeros
All ones or ASC (2)
Notes
1. If the fault signalling configured for this circuit is seized, the system does not transmit an idle code
first, as is the case for two-way trunk conditioning.
If primary
rate circuit
SEIZED Signalling
or IDLE
If not primary
rate circuit
Frozen
Fault
Fault
all 0s.
carrying a circuit
using DDS, all 1s.
VT-1.5 or
Connected circuit
Narrowband port
DDS, DDS abnormal
TU-12 card
station code (ASC).
Signalling
Information
9736
HSA Cards
(400)
31.12-3


NNP 95-2035-01-00-B
If primary
rate circuit
SEIZED Signalling
or IDLE
If not primary
rate circuit
Frozen
Fault
Connected circuit
Signalling
VT-1.5 or
TU-12 card
Fault
Narrowband port
Information
9737
Two-way trunk conditioning

When you configure two-way trunk conditioning, the signalling path and
information path are broken in both the transmit and receive direction.
After breaking the signalling and information paths, the circuit transmits the fault
signalling it was configured with, or a special code, both in the transmit direction
and the receive direction.
Table 31.12-3 lists the type of code transmitted in each case.
Table 31.12-3: Two-way Trunk Conditioning Signalling and Information Path Codes
Code
Non-Aggregate
Interface Card
Connected Circuit
Aggregate
Interface Card
Connected Circuit
To Far End
Code Transmitted on
Signalling Path
Code Transmitted on
Information Path
All zeros
All ones or ASC (2)
All ones or ASC (2)
Notes
1. Signalling is driven to idle for 2.5 seconds and then fault signalling is transmitted as configured. If
fault signalling is configured as Out-of-service, A, B or C signalling is not driven to idle first.
31.12-4
(400)
HSA Cards

NNP 95-2035-01-00-B

Figure 31.12-3 shows two-way trunk conditioning.

Figure 31.12-3: Two-way Trunk Conditioning
SEIZED
or
IDLE
Signalling
Fault

all 0s.
carrying a circuit
using DDS, all 1s.
DDS, DDS abnormal Connected circuit
station code (ASC).
VT-1.5 or
TU-12 card
Fault
Narrowband port
All 1s
or
DDS ASC
Signalling
2.5s
SEIZED
or
IDLE
Signalling
Information
Fault
9735
Disabling trunk conditioning

You can disable trunk conditioning for certain groups of link faults called fault
classes. Deselecting all the fault classes on the link disables trunk conditioning on
that link, see section 31.12.5 for information. You can disable trunk conditioning for
each narrowband port independently.
You can disable trunk conditioning for all link faults, as well as by fault class.
If you disable trunk conditioning, fault signalling is not applied to any connected
circuit, regardless of the link status; all connected circuits stay connected during the
affected link faults. If the connected circuit is protected, it does not switch to the
protecting circuit when link faults are raised; it switches only when the card is
physically removed.
HSA Cards
(400)
31.12-5

31.12.2

NNP 95-2035-01-00-B
Trunk Conditioning Configuration Overview

To enable trunk conditioning on mapper card narrowband ports and circuits, three
configuration steps are involved.
1.
Set one-way or two-way trunk conditioning for the narrowband port. See
section 31.12.3.
2.
Configure the trunk conditioning fault class for the narrowband port. See
section 31.12.5.
3.
Enable fault signalling for each circuit on the narrowband port.
You can enable trunk conditioning for certain groups of link faults called fault
classes. Enabling all the fault classes on the narrowband enables trunk conditioning
on that narrowband port.
31.12.3
Configuring One-way or Two-way Trunk Conditioning

The type of trunk conditioning you select for a narrowband port determines on
which paths (information or signalling) and in which directions (transmit or receive)
fault signalling is transmitted. Configure trunk conditioning as:
ONE_WAY for one-way conditioning

TWO_WAY for two-way conditioning (default)
To select one-way or two-way trunk conditioning for mapper cards
CONFIG SLOT <Hn-c> OPTIONS TRUNK_COND ONE_WAY/TWO_WAY*
31.12.4
Understanding Fault Class Trunk Conditioning

Link alarms are organized into groups called fault classes. You can enable or disable
trunk conditioning independently for each fault class.
Deselecting all fault classes disables the trunk conditioning for the link. You can
disable trunk conditioning in this way for each narrowband port independently.
If you turn trunk conditioning off for a primary rate circuit, no trunk conditioning is
done on that circuit regardless of how the link is programmed for trunk
conditioning. That is, the voice or data circuit connected to it stays connected during
any framing or distant alarms. If the voice or data circuit has a protecting connection,
it does not switch to that connection when a link alarm is raised. It switches only
when the primary rate card is absent.
31.12-6
(400)
HSA Cards

NNP 95-2035-01-00-B

Table 31.12-4 lists the fault classes and explains the alarms in each.
Table 31.12-4: Fault Class Descriptions for Mapper Cards
Fault Classes
TU-12
VT-1.5
Alarm Description
Frame/Red (1)
Framing Alarm
Incoming AIS
Multi-frame Alarm
Incoming TS16 AIS
Red Alarm
These alarms are associated with frame alignment

or multi-frame alignment. These alarms are cleared
when frame alignment or multi-frame alignment is
regained.
Distant/Yellow
Distant Alarm
Incoming TS16 AIS
Yellow Alarm
These alarms are received from the equipment at the

far end of the primary rate link. These alarms are
cleared when the remote equipment is no longer
transmitting the alarm.
Failed
Failed State
Failed State
This alarm is raised when 10 Severely Errored

Seconds in a row have occurred. It is cleared when
10 non-Severely Errored Seconds have occurred in
a row.
Error
Frame Error Rate

Exceeded
Frame Error Rate

Exceeded
For VT-1.5 cards, this alarm is raised when the

terminal framing bit (Ft) Error rate exceeds
approximately 10-3 for a period of 4 to 6 s. It is
cleared when the Ft Error rate is below
approximately 10-4 for 9 to 11 s.
For TU-12 cards, this alarm is raised when the FAS
error rate exceeds approximately 10-3 for a period of
4 to 6 s. It is cleared when the FAS error rate is below
approximately 4 x 10-4 for 9 to 11 s.
Loopback
CPSS Loopback
activated
In-band Loopback
activated
On-fault Loopback
activated
CPSS Loopback
activated
On-fault Loopback
activated
When the card receives a framed or unframed 10000

code from the network (usually originated by the
carrier), it enters a remote loopback state. The
incoming signal is looped back at the card towards
the network and continues through to the system.
Loopback trunk conditioning is applied as
configured. The card remains in this state until a
framed or unframed 100 code is received from the
network.
Notes
1. For TU-12 cards, this is the Frame fault class. For VT-1.5 cards, it is the Red fault class.
HSA Cards
(400)
31.12-7

31.12.5

NNP 95-2035-01-00-B
Enabling or Disabling Fault Classes for Mapper Cards

Configure fault classes for VT-1.5 and TU-12 cards according to Table 31.12-5. In all
cases, the default condition is enabled.
Table 31.12-5: Configuring Fault Classes for Mapper Cards
VT-1.5 Card
TU-12 Card
Frame/Red
Distant/Yellow
Failed
Error
Fault Class
Loopback
Disabling trunk conditioning using fault classes

To completely disable trunk conditioning on the link, turn off all of the fault classes.
For mapper cards, you can disable trunk conditioning for each narrowband port
independently.
To set mapper card fault classes

CONFIG SLOT <Hn-c> OPTIONS
MORE
FAULT_HNDL
TRUNK_COND
RED_OFF/
YELLOW_OFF/
RED_ON* or
YELLOW_ON* or
FRAME_OFF/ DISTANT_OFF/
FRAME_ON*
DISTANT_ON*
FAILED_OFF/
FAILED_ON*
ERROR_OFF/
ERROR_ON*
LPBK_OFF/
LPBK_ON*
SK000864
31.12-8
(400)
HSA Cards

NNP 95-2035-01-00-B
31.13

Narrowband Port Framing

This chapter explains how to configure framing for mapper card narrowband ports.
31.13.1
Understanding Framing for Narrowband Ports

Narrowband port framing type can be configured for the following mapper cards:
VT-1.5 card
TU-12 card
The mapper cards each contain 16 narrowband ports. Framing is configured on
individual narrowband T1 and E1 ports.
31.13.2
Configuring Framing for VT-1.5 Cards

You can configure one of the two following framing options for a VT-1.5 card
narrowband T1 port:
D4
ESF
If the framing type is changed from one setting to another, a RED alarm is declared.
This alarm state does not clear until framing is achieved, and the alarm clear time
has passed.
If you attempt to change the framing type from ESF to D4 while one of the T1 circuits
on the port is configured for OOS-B signalling, the attempt is blocked and the
message Cannot change to D4. Some circuits are using OOS-B fault signalling is
displayed.
D4 framing
A D4 frame consists of 193 bits: 24 timeslots containing 8 bits each and one framing
bit. A D4 superframe consists of 12 frames. Figure 31.13-1 shows the D4 framing
format within D4 superframe format.
HSA Cards
(400)
31.13-1


NNP 95-2035-01-00-B
Figure 31.13-1: D4 Framing Format

D4 Superframe
12 D4 frames
10
11
12
2316 bits
12 Framing bits
Framing pattern =
100011011100
Frame 1
Framing bit
Timeslot 1
Timeslot 2
Timeslot 24
8 bits
193 bits
D4 Format
8137
ESF framing
This framing format creates superframes consisting of 24 D4 frames. Figure 31.13-2
shows the ESF format.
Figure 31.13-2: ESF Framing Format
Extended Super Frame

1
24 D4 frames
21
22
23
24
4632 Bits
24 bits: 6 framing (2 kb/s)
6 error checking (2 kb/s)
9755
To configure framing format on the narrowband DS-1 port

CONFIG SLOT <Hn-c> OPTIONS ESF/D4_FRAMING*
31.13-2
(400)
HSA Cards

NNP 95-2035-01-00-B
31.13.3

Configuring Framing for TU-12 Cards

You can configure one of three framing options for a TU-12 card narrowband port.
Table 31.13-1 lists the framing options.
CAS*
CCS
31_CHAN
Table 31.13-1 shows the timeslot-to-circuit designation for these framing options. A
circuit is a device internal to the node. Narrowband E1 ports are assigned circuits 1
to 31. A timeslot is a channel on the physical narrowband E1 port external to the
node. Narrowband E1 ports are made up of timeslots 0 to 31.
Table 31.13-1: Timeslot-to-Circuit Designation for TU-12 Cards
Switching Order of Circuits (1)
Frame Type
CAS
Timeslot
Circuit
0 1 2 3... 15 16 17... 29 30 31
F 1 2 3... 15 S 16... 28 29 30
CCS and
31 channels
Timeslot
Circuit
0 1 2 3... 15 16 17... 29 30 31
F 1 2 3... 15 31 16... 28 29 30
Notes
1. F = framing; S = signalling
Common channel signalling and 31 channels provide 31 configurable circuits, but

they treat circuit 31 differently.
If you change the framing type of a port, the Framing Alarm is raised until framing
is achieved, and the alarm clear time has passed.
Note
The port framing type cannot be changed if any of the circuits associated with the
port are connected. Any attempt to do so is blocked with the message That port has
one or more circuits in use. Disconnect them first.
CAS framing
Timeslot 16 is used for CAS and is not user-configurable. Timeslot 0 is used for
framing. The rest of the timeslots are used for information. Timeslots 1 through 15
correspond to circuits 1 through 15 and timeslots 17 through 31 correspond to
circuits 16 through 30.
HSA Cards
(400)
31.13-3


NNP 95-2035-01-00-B
CCS framing
Timeslot 16 corresponds to circuit 31, which can be configured as an additional
64 kb/s data channel (typically for the transport of CCS messages). The rest of the
timeslots are labeled as in CAS: timeslots 1 through 15 correspond to circuits 1
through 15 and timeslots 17 through 31 correspond to circuits 16 through 30. The 31
circuits are treated equally. Timeslot 0 is used for framing.
31 channels framing
This framing pattern has the same designation of timeslots to circuits as CCS.
However, when making super-rate connections (connections that occupy more than
one channel on a primary rate link) to an E1 link, the system does not skip timeslot
16 (the 31st circuit); timeslots 1 through 31 are used consecutively (see Table 31.13-1).
To configure framing for TU-12 card narrowband ports

CONFIG SLOT <Hn-c> OPTIONS FRAME_TYPE
CAS*
31_CHAN
CCS
SK000899
31.13-4
(400)
HSA Cards

NNP 95-2035-01-00-B
31.14

Narrowband Circuit Fault

Signalling
This chapter describes how to configure fault signalling for VT-1.5 and TU-12 card
primary rate circuit.
31.14.1
Understanding Fault Signalling for Mapper Cards

When trunk conditioning is applied to a narrowband port, the system transmits a bit
pattern (or code), called fault signalling, on each circuit cross-connected to the link.
If a VT-1.5 or TU-12 card circuit is configured to transmit a seized fault-signalling
code to the LGE card cross-connected to it, a connected PBX is prevented from trying
to place a call through the VT-1.5 or TU-12 card until its narrowband port returns to
service.
You can configure the type of fault signalling independently for each primary port
primary rate circuit. Table 31.14-1 lists the fault signalling types and defaults for
each card.
When you program a super-rate connection for OOS A, B or C, the first DS0 (the
master circuit) detects the fault condition and transmits the appropriate OOS code.
When a narrowband port carrying a channel that is being compressed fails, the fault
signalling sent to the far end is always seized (regardless of the fault signalling
configured).
Table 31.14-1: Fault Signalling for PRI Cards
Seized
Idle (1)
OOS A
OOS B
OOS C (3)
None
VT-1.5 card
(1)
(2)
(3)
TU-12 card
(4)
(5)
(6)
Card
Notes
1. Applies to DS0s (on either D4- or ESF-framed DS1s) with RBS enabled connected to 56 kb/s (or less) data, OCU-DP or
E&M circuits.
2. Applies to DS0s (on ESF-framed DS1s only) with RBS enabled connected to 56 kb/s (or less) data, OCU-DP or E&M circuits.
3. Applies to DS0s (on either D4- or ESF-framed DS1s) with RBS enabled connected to data or any voice circuits.
4. Applies to timeslots (on CAS-framed links only) connected to data or any voice circuits.
5. Applies to timeslots (on either CCS- or 31 Channel-framed links) connected to data or any voice circuits.
6. Applies to DS0s (on either D4- or ESF-framed DS1s) connected to data or E&M circuits.
HSA Cards
(400)
31.14-1


NNP 95-2035-01-00-B
Disabling fault signalling for mapper cards

You can enable or disable fault signalling independently for each circuit. If you
disable fault signalling (configure it as NONE), the circuit stays connected during
link faults. If the connected circuit is protected, it does not switch to the protecting
circuit when a link fault is raised; it switches only when the aggregate interface card
it is connected to is physically removed.
Fault signalling codes for mapper cards

The bit pattern transmitted when you select Idle or Seized as the fault signalling
defaults to the codes used in E&M signalling.
Idle: 0000 (ESF), 00 (D4)

Seized: 1111 (ESF), 11 (D4)
To accommodate circuits configured for other signalling types, you can also
configure custom bit patterns, see chapter 31.19.
Table 31.14-2 lists the bit patterns transmitted when OOS A, B, or C fault signalling
is selected for aggregate cards that support OOS fault signalling.
Table 31.14-2: Fault Signalling Codes OOS A, B and C for PRI Cards
Card
OOS C (1)
OOS A
OOS B
VT-1.5
0100(01) (2)
0110(n/a)
TU-12
1111
0110
Notes
1. When OOS-C is selected for a DS0 and that circuit connection becomes unavailable, a yellow alarm
is generated on the DS1 circuit for a T1 DS0; a distant alarm is generated for an E1 DS0.
2. For ESF-framed DS1s, all four ABCD signalling bits are defined. For D4-framed DS1s, only the AB
signalling bits (shown in brackets) are defined.
31.14.2
Configuring Fault Signalling for Mapper Cards

Configure fault signalling according to the options listed in Table 31.14-1. The trunk
conditioning for each circuit is disabled when no fault signalling is selected for the
circuit.
31.14-2
(400)
HSA Cards

NNP 95-2035-01-00-B

Note
For VT-1.5 card T1 circuits, fault signalling can be transmitted only if RBS is enabled.
If this condition is not met and OOS-A or OOS-B is selected, a warning message
appears when you attempt the cross-connection.
RBS uses the least significant bit of every channel in frames 6 and 12 (if D4 framing
is used) and frames 6, 12, 18 and 24 (if ESF framing is used). Use RBS with caution
on data circuits.
If you configure fault signalling before the signalling type, the system offers OOS
types A, B and C. If you subsequently select an incompatible signalling type (for
example, an LGS signalling type on a circuit with OOS type A enabled), a warning
message appears.
Restrictions
For D4-framed T1 circuits connected to E&M or data circuits, you can select
SEIZED, IDLE, OOS-A or OOS-C.

For ESF-framed T1 circuits connected to E&M or data circuits, you can select
SEIZED, IDLE, OOS-A, OOS-B or OOS-C.
For D4- or ESF-framed T1 circuits connected to LGS or LGE circuits, you can
select SEIZED, IDLE or OOS-C.
For T1 circuits, OOS-B fault signalling is only available if the associated port is
configured for ESF framing.
For T1 circuits, before you select either OOS-A or OOS-B fault signalling, the
circuit must be configured for one of the following signal types: T1_SIG,
T1_NOSIG, TI_E+M or T1_ TERM.
For an E1 circuit, OOC-A or OOS-B cannot be selected if the circuit is configured
for R2_E&M.
To configure fault signalling for mapper cardprimary rate circuits

CONFIG CIRCUIT <Hn-c-d> FAULT_SIG
OOSA
OOSB
OOSC
SEIZED
IDLE
SK000928
HSA Cards
(400)
31.14-3

NNP 95-2035-01-00-B
31.15

Mapper Card PRI Signalling

This chapter describes the implementation of signalling for mapper cards.
31.15.1
Understanding Signalling for mapper cards

Signalling defines the codes and protocol used to communicate call setup, call tear
down and status information between two voice devices (such as PBXs)
interconnected by a primary rate link. The voice device is connected to a voice
interface (such as an LGS card or channel unit) that is cross-connected to a DS0 on a
narrowband port on a mapper card.
Signalling types for mapper cards

Typically, the signalling need only be configured at the voice card circuits. If you
configure the primary rate signalling type for the default, the primary rate circuit
automatically takes on the signalling type required by the end-point circuit when
you make the connection. The primary rate signalling type returns to the default
when you disconnect the connection.
If you do not configure the primary rate signalling type for the default, connection
to an end-point circuit is allowed only if the configured signalling type is compatible
with the end point circuit. The primary rate signalling type remains at its configured
setting when you disconnect the connection.
You must configure signalling for a narrowband port DS0 circuit when:
primary rate circuits are cross-connected in a tandem node

a TU-12 card narrowband port DS0 circuit using R2 digital signalling is
connected to an E&M circuit
Table 31.15-1 lists the mapper card PRI signalling types and indicates how they
apply to the two types of mapper cards.
Table 31.15-1: Mapper Card PRI Signalling Types
HSA Cards
VT-1.5 Card
TU-12 Card
Signalling Type
Transparent
SIG
Clear channel
NoSIG
E&M
E+M
Continuous E&M
E+M_B
LGS REM_EXT
LGS Earth Calling
LGS EC
(400)
Option
31.15-1


NNP 95-2035-01-00-B
VT-1.5 Card
TU-12 Card
Signalling Type
Option
LGS PLAR
E1_SIG or T1_SIG) LGS

PLAR or PLAR_D3
LGE REM_EXT
LGE Earth Calling
LGE EC
LGS Loop Start
LGS LS
LGS Ground Start
LGS GS
LGE Loop Start
LGE LS
LGE Ground Start
LGE GS
R2D_E+M
RBS
RBS
Terminate
TERMINATE
Compatible mapper and PRI card signalling types

Table 31.15-2 lists compatible signalling type combinations for connections between
different types of primary rate links and narrowband ports. If the attempted
connection is possible, the system connects the primary rate circuits; if not, it
displays an error message.
Table 31.15-2: Compatible Mapper and PRI Card Signalling Types
TU-12 Mapper, E1, Dual E1, Dual E1-2, E3, MPA
and X.21 or V.35 PRI , Card
VT-1.5 Mapper, T1, Dual T1-2 and DS-3 or

DS-3 II (1)
Transparent
Transparent
Clear channel
Clear channel
E&M
E&M
Continuous E&M (2)
E&M
LGS PLAR
LGS PLAR (3) or PLAR D3 (4)
LGE Loop Start
LGS Loop Start
LGS Earth Calling
LGE Ground Start
LGE Earth Calling
LGS Ground Start
Notes
1. DE3 or SE3 to DS-3 or DS-3 II connections are supported only by NoSIG connections.
2. Continuous E&M is used to convert a proprietary signalling type to Newbridge standard E&M
signalling. Continuous E&M is supported if the E1 link is configured for CAS.
3. LGS PLAR is equivalent to D4 PLAR signalling as specified in the 1985 Addendum to PUB 43801.
4. PLAR D3 is equivalent to D3 PLAR signalling as specified in the 1982 Addendum to PUB 43801.
31.15-2
(400)
HSA Cards

NNP 95-2035-01-00-B

PLAR D3 signalling
When LGS PLAR is selected, the system provides signalling according to the 1985
Addendum to PUB 43801. This Addendum specifies support for D4 channel banks
and inverts the state of the signalling bits specified in the 1982 Addendum. When
LGS PLAR_D3 is selected, the system provides signalling according to the 1982
Addendum to PUB 43801. PLAR_D3 signalling supports third-party nodes (such as
D3 channel banks) that still comply with the 1982 Addendum.
If you are connecting a TU-12 card narrowband circuit using R2 digital signalling to
an E&M circuit, you must configure the primary rate circuit as type R2D_E+M.
RBS
RBS is usually used to pass ABCD signalling. When RBS is enabled, the least
significant bit (bit 8) of every channel in frames 6 and 12 (if D4 framing is used) or in
frames 6, 12, 18 and 24 (if ESF framing is used) is overwritten with signalling
information.
You cannot use RBS under the following conditions.
If a DCC, DNIC or 2B1Q Line card circuit with a bandwidth of 64 kb/s or greater
HSA Cards
is connected to a VT-1.5 card narrowband port circuit, RBS must be disabled.

When a signalling or compressed voice channel defined by a VCM-equipped
Dual E1 card is connected to a narrowband port DS0 circuit, RBS is automatically
disabled for the DS0 circuit.
(400)
31.15-3

31.15.2

NNP 95-2035-01-00-B
Configuring Signalling for VT-1.5 Cards

Configure VT-1.5 card narrowband port circuits with one of the following signalling
types:
SIG for transparent, where signalling is passed without being tested for
compatibility with the signalling type at the far end

NoSIG for clear channel, where a 64 kb/s clear channel is created without
signalling
E+M for E&M
LGS LS for LGS Loop Start
LGS GS for LGS Ground Start
LGS PLAR or PLAR_D3 for LGS PLAR
LGE LS for LGE Loop Start
LGE GS for LGE Ground Start
RBS_ON to enable RBS
RBS_OFF to disable RBS
TERMINATE for accessing a frame relay network
Note
In a T1-to-T1 tandem node, if you select NoSIG and enable RBS, the system does not
monitor the signalling of the data received and overwrites the outgoing data bits
with the default RBS pattern.
To enable signalling for VT-1.5 card narrowband port circuits

CONFIG CIRCUIT <Hn-c-d> MORE SIG_TYPE
TERMINATE
NoSIG
SIG*
LS
PLAR
E+M
PLAR_D3
LGS
LGE
GS
LS
GS
SK000866
To enable or disable VT-1.5 card narrowband port circuits

CONFIG CIRCUIT <Hn-c-d> FUNCTION RBS_OFF/RBS_ON*
31.15-4
(400)
HSA Cards

NNP 95-2035-01-00-B

To create clear channels on VT-1.5 card narrowband ports

To create a 64 kb/s clear channel without signalling, select NoSIG and turn off RBS
for the selected circuit.
31.15.3
Configuring Signalling for TU-12 Card Circuits

Configure TU-12 card narrowband port circuits as:
E1_SIG SIG or T1_SIG SIG for transparent E1 or T1 signalling, where signalling
HSA Cards
is passed without being tested for compatibility with the far-end signalling type
(E1_SIG SIG is the default for E1 signalling and for PRI circuits with NUM_SIG
set to a value other than 0)
E1_SIG NoSIG or T1_SIG NoSIG for clear channel E1 or T1 signalling, where a 64
kb/s clear channel is created for which signalling is not passed (default for PRI
circuits with NUM_SIG set at the default value of 0)
E1_SIG E+M E+M or T1_SIG E+M for E&M for E1 or T1 signalling, or E1_SIG
E+M E+M_B for conversion of proprietary E1 signalling to Newbridge standard
E1 signalling
E1_SIG LGS REM_EXT for LGS Remote Extension for E1 signalling
E1_SIG LGS EC for LGS Earth Calling for E1 signalling
E1_SIG LGS PLAR for LGS PLAR for E1 signalling
E1_SIG LGE REM_EXT for LGE Remote Extension for E1 signalling
E1_SIG LGE EC for LGE Earth Calling for E1 signalling
T1_SIG LGS LS for LGS Loop Start for T1 signalling
T1_SIG LGS GS for LGS Ground Start for T1 signalling
T1_SIG LGS PLAR or PLAR_D3 for LGS PLAR for T1 signalling
T1_SIG LGE LS for LGE Loop Start for T1 signalling
T1_SIG LGE GS for LGE Ground Start for T1 signalling
(400)
31.15-5


NNP 95-2035-01-00-B
To configure signalling type for TU-12 cards

CONFIG CIRCUIT <Hn-c-d> MORE SIG_TYPE
E1_SIG
SIG*
T1_SIG
R2D_E+M
NoSIG
E+M
REM_EXT
LGS
E+M
LGE
E+M_B
PLAR
EC
SIG
LS
NoSIG
GS
EC
REM_EXT
E+M
PLAR
LGE
LGS
PLAR_D3
LS
TERMINATE
GS
SK000867
31.15-6
(400)
HSA Cards

NNP 95-2035-01-00-B
31.16
31.16 Mapper Card Narrowband Circuit Inversion

Mapper Card Narrowband Circuit

Inversion
This chapter explains how to configure inversion for mapper card primary rate
circuits.
31.16.1
Understanding Inversion for VT-1.5 and TU-12 Cards

You can configure inversion for any narrowband port primary rate circuit (DS0). All
information on non-compressed circuits connected to a primary rate circuit can be
either inverted (VOICE) or not inverted (DATA).
If the connected circuits are voice circuits, the information being passed over the
primary rate circuits should be inverted when there is a requirement to convert
between the ITU-T alternate digit inversion PCM output code format (generally
used on 2.048 Mb/s E1 links) and the AT&T true-sign inverted magnitude PCM
output code format (generally used on 1.544 Mb/s T1 links).
If the connected circuits are data circuits, the information being passed over the
primary rate circuit does not normally need to be inverted.
For bypass connections (T1_SIG-to-E1_SIG or T1_NoSIG-to-E1_NoSIG), the default
setting changes on both circuits after you make the connection so that the
information is not inverted. If the remote circuits are voice circuits, the information
should be inverted.
31.16.2
Configuring Inversion for Card Narrowband Port Circuits

Configure inversion on a non-compressed circuit connected to a primary rate circuit
as:
voice for inverted (default)

data for not inverted
To configure inversion for mapper card narrowband port circuits
CONFIG CIRCUIT <Hn-c-d> FUNCTION DATA/VOICE*
HSA Cards
(400)
31.16-1

NNP 95-2035-01-00-B
31.17
31.17 TU-12 Card NU Bits Configuration

TU-12 Card NU Bits Configuration

This chapter describes the NU bits options that apply to TU-12 card narrowband E1
ports, and explains how to configure them.
31.17.1
Configuring the NU bits for TU-12 Cards

E1-level NU bits are TS0 bits 4 through 8 in odd-numbered frames, which are the
frames without the FAS. The first three TS0 bits are reserved and not
user-configurable.
NU bits should only be configured for use in customized applications where the NU
bits are used for alarm signalling.
For TU-12 cards, you can set the transmitted value of certain TS0 NU bits at the E1
level. The default setting is 11111.
To configure NU bits for TU-12 cards

CONFIG SLOT <Hn-c> OPTIONS TX_NU_BIT <bit_value>
where bit_value is a 5-digit binary value in the range 00000 to 11111 for E1-level transmission
To view the received NU bits for TU-12 cards

CONFIG SLOT <Hn-c> OPTIONS
The system displays the current values for the transmitted and received NU bits.
HSA Cards
(400)
31.17-1

NNP 95-2035-01-00-B
31.18

TU-12 Card CRC-4 Reframing and

Link Quality Monitoring
This chapter describes the CRC-4 options that apply to TU-12 card narrowband E1
ports, and explains how to configure them.
31.18.1
Understanding CRC-4 Reframing and Link Quality

Monitoring
The following CRC-4 options are available for TU-12 card narrowband E1 ports
CRC-4 reframing
link quality monitoring (CRC-4 or FAS)
31.18.2
Configuring CRC-4 Reframing

CRC-4 reframing can be configured for TU-12 card narrowband E1 ports. CRC-4
reframing is not available for configuration unless CRC4_STATS is enabled. The
frame alignment is reframed when the CRC error rate exceeds 914 errors each
second. The frame alignment is also reframed if the CRC multiframe
synchronization is not achieved within 8 ms of frame synchronization.
Select CRCRFRM to enable CRC-4 reframing and NO_CRCRFRM to disable it.
To configure narrowband E1 port CRC-4 reframing

CONFIG SLOT <Hn-c> OPTIONS CRCRFRM/NO_CRCRFRM*
HSA Cards
(400)
31.18-1

31.18.3

NNP 95-2035-01-00-B
Configuring CRC-4 or FAS Link Quality Monitoring

You can configure each port to monitor the quality of a narrowband E1 port using
CRC-4 or FAS statistics. This allows the card to monitor the received signal quality
over the link and transmit the status of the link to the far end. A CRC-4 error
indication received from the far end does not affect service on the card. The link
quality status is carried by TS0.
When CRC-4 error detection is enabled, the card gathers CRC-4 statistics. When
CRC-4 error detection is not enabled, the card gathers FAS statistics (see
Maintenance, section 34.1.3).
Table 31.18-1 shows how the signal carried in TS0 of the narrowband E1 port varies
in alternate frames; one TS0 carries the FAS and the next TS0 carries the distant
alarm indicator and the NU bits. Bit position 1 of TS0 is reserved for international
use (Si), except that it carries the link quality indicator when CRC-4 error detection
is enabled. When CRC-4 error detection is not enabled, this bit is set to 1 by default.
The bit is also used to provide multiframe alignment. The distant alarm indicator (A)
is 0 in normal operation and set to 1 if a Distant Alarm is detected. Bits SA4 to SA8
are the NU bits.
Table 31.18-1: Usage of Bits on TS0
Frame
Bit
1
Bit
2
Bit
3
Bit
4
Bit
5
Bit
6
Bit
7
Bit
8
TS0 carrying FAS
Si
TS0 not carrying FAS
Si
SA4
SA5
SA6
SA7
SA8
Configure the TU-12 card for CRC-4 error detection or FAS statistics:
CRC4_STATS for CRC4

FAS_STATS for FAS (default)
To select CRC-4 or FAS error detection
CONFIG SLOT <Hn-c> OPTIONS CRC4_STATS/FAS_STATS*
31.18-2
(400)
HSA Cards

NNP 95-2035-01-00-B
31.19

Narrowband Circuit Custom Trunk

Conditioning
This chapter explains how to configure custom trunk conditioning for mapper card
circuits.
31.19.1
Understanding Custom Trunk Conditioning

The fault signalling bit pattern (or code) that is transmitted during trunk
conditioning defaults to the codes used in E&M signalling. To accommodate circuits
configured for other types of signalling, configure custom bit patterns.
For all mapper card circuits(except compressed voice circuits), configure the custom
fault signalling bit patterns independently for each circuit on a link. The following
fault signalling codes are available.
configured to transmit idle fault signalling. The default is 0000.

configured to transmit seized fault signalling. The default is 1111.
DATA is the code transmitted on the information path. The default is 11111111.
The CODE_1 and CODE_2 bit patterns represent the settings of the ABCD signalling
bits. For D4-framed DS1s, only the AB bits are defined. For ESF-framed T1s and E1s,
all four ABCD bits are defined.
If you change framing on a narrowband from D4 to ESF after configuring CODE_1
or CODE_2, the configured AB bits are copied into the CD bit positions (that is,
ABAB is transmitted).
If an E1 circuit is configured for T1 signalling, you configure only the AB bits; the C
and D bits are fixed at 0 and 1, respectively.
Caution
Never set CODE_1 (idle) and CODE_2 (seized) to all zeros. An all-zero setting can
cause multiframe problems in an E1 network.
Table 31.19-1 lists common seized and idle codes for each signalling type supported
by the system.
HSA Cards
(400)
31.19-1


NNP 95-2035-01-00-B
Table 31.19-1: Fault Signalling Codes Seized and Idle for VT-1.5 and TU-12 Cards
Seized Code
Idle Code
Signalling
TU-12 (1)
VT-1.5(2)
TU-12 (1)
VT-1.5 (2)
DPO/DPT
1111
1111
0000
0000
E&M (T1/NA)
0101
1111
1101
0000
E&M (E1/UK)
1111
0101
0000
1101
LGE_EC
0101
0101
1101
1101
LGE_GS
0000
0000
0101
0101
LGE_LCDC
0101
0101
1101
1101
LGE_LS
1111
1111
0101
0101
LGE_RE
0101
0101
1101
1101
LGS_CBW
1101
1101
1101
1101
LGS_EC
1001
1001
1101
1101
LGS_GS
0101
0101
1111
1111
LGS_LCDC
1001
1001
1101
1101
LGS_LS
0101
0101
0101
0101
LGS_PLAR
0000/0101
0000
0000/0101
1111
LGS_RE
1101
1101
1101
1101
R2D E&M
0011
0011
1011
1011
Notes
1. When T1 signalling is configured on E1 timeslots, the last two bits (C and D) are set to 0 and 1,
respectively.
2. Codes shown are for ESF-framed T1s (which use all four ABCD bits). For D4-framed T1s, only the
first two bits (AB) are transmitted.
31.19.2
Configuring Custom Trunk Conditioning for Mapper Cards

Configure custom trunk conditioning as:
configured to transmit Idle fault signalling (the default is 0000)
31.19-2
configured to transmit Seized fault signalling (the default is 1111)

DATA for the code transmitted on the information path (the default is 11111111)
(400)
HSA Cards

NNP 95-2035-01-00-B

To configure custom trunk conditioning for mapper cards

CONFIG CIRCUIT <Hn-c-d> FAULT_SIG MORE CUSTOM
CODE_1
CODE_2
<code> <code>
DATA
<data>
SK000865
where
code is a 2- or 4-digit binary code
data is an 8-digit binary code
HSA Cards
(400)
31.19-3

NNP 95-2035-01-00-B
31.20

Mapper Card Narrowband Port

Loopback Detection
This chapter explains how to configure loopback detection for mapper cards.
31.20.1
Understanding Loopback Detection for Mapper Cards

A protected circuit is configured with both a preferred and a protecting link to the
far-end circuit. When a fault occurs on the preferred link, the system switches the
circuit to the protecting link. The network operator uses loopbacks to determine the
location of the fault. The loopback detection feature lets the node detect a loopback
condition and ensures that the connection is not switched back to the preferred link
until end-to-end connectivity has been restored. Mapper cards can be configured to
detect narrowband port loopbacks only through CPSS.
The node monitors the CPSS channel for a loopback condition if service on the link
is disrupted.
Loopback detection operates as follows:
1. During normal operation, the connection is established over a preferred link.
2. When a fault occurs, a framing alarm is generated at both ends of the connection,
and the connection is switched to the protecting link as long as trunk
conditioning is enabled.
3. Loopbacks are initiated by the network operator to isolate the fault. When the
node detects the loopback condition, the framing alarm is cleared and a
loopback detected alarm is raised.
4. When the fault has been repaired, the network operator removes the loopbacks.
When the node detects that the loopback condition has been removed, the circuit
is switched back to the preferred link.
Note
Loopbacks initiated by the network operator are removed when the fault has been
repaired. If the loopback condition is removed before the fault is repaired, another
framing alarm is generated, and the connection is maintained over the protecting
link.
HSA Cards
(400)
31.20-1

31.20.2

NNP 95-2035-01-00-B
CPSS Loopback Detection for Mapper Cards

Table 31.20-1 lists CPSS resources supported by the mapper cards and the required
connection types.
Table 31.20-1: CPSS Resources and Connection Types
CPSS Resources
Connection Types
Dedicated, shared
Control card
DCP card
DCP CPSS connection
FRE, FRS and PE cards
Circuits configured for CPSS
See chapter 17.6 for more information on CPSS connections.

Warning
CPSS connections are live circuits and must be added to an active network carefully
to avoid routing problems.
Mapper card loopback detection can be configured as:
NONE (default)
VIA_CPSS
31.20.3
Establishing CPSS Loopback Detection for Mapper Cards

1.
Establish a CPSS connection between the end cards.
2.
Configure CPSS loopback detection on the mapper card. A CPSS connection

can be carried over any timeslot on a narrowband port.
To configure loopback detection on mapper cards

CONFIG SLOT <Hn-c> OPTIONS LPBK_DETEC NONE* or VIA_CPSS
31.20-2
(400)
HSA Cards

NNP 95-2033-01-00-B
Index

NNP 95-2035-01-00-B
Index
Index
1_BIT, 22.3-14
1200, 21.6-3
150, 21.6-3
16+, 19.3-3
2_BITS, 22.3-14
24_DS0, 20.16-4
2601 MainStreet DTU, 22.1-6
2600 MainStreet series DTUs, 3.12-2
forced activity switching, 22.3-27
27LC2 line card, 22.1-2
link quality statistics, 34.1-27
BER threshold, 34.1-29
reset, 34.1-29
view, 34.1-29
2700 MainStreet series DTUs, 3.12-4
2B1Q, 22.2-2, 22.2-4
2B1Q Channel Unit
3DS-0 transmission format, 22.3-34
configuring, 22.1-8
connections, 22.3-36
diagnostics, 7.5-5
faceplate, 7.5-4
functional description, 7.5-2
functions, 22.1-4
ISDN basics, 22.3-32
ISDN loop extension, 22.3-33
loopbacks, 7.5-5
overview, 7.5-1
performance monitoring, 22.3-36
pinout, 14.10-10
quality statistics, 34.1-29
slot configuration, 22.2-4
specifications
physical, 7.5-6
zero byte substitution, 22.3-36
2B1Q Line card, 22.1-2
DTU activity switching, 22.3-25
pinout, 14.10-1, 14.10-11
2-second timer, 18.3-4
2-WIRE, 21.4-1
3.1KHZ, 30.4-4
3_DS0, 22.2-4
31 channels, 20.6-5
3600 MainStreet, 1.2-1
3600+ MainStreet, 1.2-3
alarms
alarm panel, 3.13-1
architecture, 2.2-3
cooling: blower unit, 3.9-7
power feeds, 3.7-4
power supply cards, 3.7-2
LEDs, 3.7-13
slot locations, 3.7-5
redundancy
types, 2.1-12
ringing generators: external, 3.8-6
connectors, 3.8-11
connector pinout, 3.8-10
system configuration, 2.3-4
timing and synchronization, 2.1-9
36120_ID, 25.4-7
3DS-0 transmission format, 22.3-34, 29.3-3
3DS-0 transport, 29.3-9, 29.3-10
3DS0_ENAB/DISAB, 29.3-9
4 kb/s CPSS channels, 17.6-27
4601 MainStreet Network Manager, 16.2-4
4602 MainStreet Intelligent NetworkStation,
16.2-4
MainStreetXpress 46020 Network Manager,
16.2-4
4KPBS, 24.2-2
4W_TO, 21.2-3, 22.2-4
4WDX Channel Unit, 21.1-1
diagnostics, 6.5-4
equalization, 21.11-1
faceplate, 6.5-3
IN-1
Index

LEDs, 6.5-3
loop balance, 21.10-1
loopbacks, 6.5-4
overview, 6.5-1
pinout, 14.10-1, 14.10-12
signalling leads, 6.5-4
signalling modes, 21.3-8
signalling types, 21.3-7
specifications, 6.5-5
4-WIRE, 21.4-1
4-wire loopback metallic connection, 36.3-7
4WTO Channel Unit
configuring, 22.1-8
faceplate, 7.6-3
functions, 22.1-5
installation, 13.43-1
loopbacks, 7.6-4
overview, 7.6-1
pinout, 14.10-1
sealing current, 22.3-32
TLPs, 21.5-1
versions, 7.6-2
voice capabilities, 21.1-2
4WTO Line card, 21.1-1
card versions, 6.1-2
faceplate, 6.1-3
LEDs, 6.1-4
loopbacks, 6.1-4
Overview, 6.1-1
pinout, 14.10-1, 14.10-13
5_BITS, 22.3-14
5_DS0, 22.2-4
5ESS, 25.11-1
6 dB attenuation pad, 23.3-10
6+2, 19.3-3
6+6, 19.3-3
6_BITS, 22.3-14
600, 21.6-2, 21.6-3
600+2.1, 21.6-2
600+2.16, 21.6-3
8 kHz timing, 22.3-29
AIS, 22.3-29
alarm declare/clear times, 7.1-3
configuring, 22.1-8
IN-2

NNP 95-2035-01-00-B
custom trunk conditioning, 20.11-1

faceplate, 7.1-1
faceplate test access ports, 36.1-6
fault signalling, 20.10-1
functions, 22.1-3
loopbacks, 7.1-3
overview, 7.1-1
pinout, 14.10-1, 14.10-15
synchronization source, 7.1-3
test access ports, 7.1-3
unidirectional signalling types, 20.12-7
64 kb/s CPSS channels, 17.6-20
64K_CODIR, 22.2-4
7_BITS, 22.3-14
8 kHz timing, 22.3-29
8 to 56 kb/s CPSS channels, 17.6-29
8+_MODULE, 19.3-2
8+8, 19.3-3
8_BITS, 22.3-14
8K_TIMING, 22.3-29
900+2.1, 21.6-2
900+2.16, 21.6-3
A
A_LAW, 23.4-4
A_STD_ON/OFF, 25.9-5
absent card, 18.3-4
absolute address, 26.3-1
Absolute Congestion Threshold
configuring for encapsulation circuits,
25.10-8, 27.13-9
configuring for frame stream circuits,
27.13-15
ac power feeds
ac power cable connections, 13.29-1
Class A peripheral shelf
ac power cable connection, 13.29-1
Class B locally controlled shelf
Class B peripheral shelf
HSPS

NNP 95-2035-01-00-B
ac power supplies
input specifications, 3.7-6
power cables, 3.7-8
upgrade kits, 3.7-7
variants, 3.7-7
AC15 tone detection, 23.3-11
ACCES_PROT, 18.1-6
ACCESS, 20.16-4
access
direct, 27.13-1
encapsulated, 27.13-2
subrate, 27.13-7
super-rate, 27.13-1
access levels, 17.5-1
and control redundancy, 17.5-1
configuring, 17.5-1
defining, 17.5-4
access rate, 25.1-4, 25.5-3
accounting
accounting agent, 38.1-11
accounting generation subsystem, 27.11-1
accounting NVM buffer size parameter,
27.10-22
accounting segments, 27.10-2
accounting segment size parameter,
27.10-19
accounting activation parameter, 27.15-4,
28.3-3
accounting parameters, 27.10-15
collection intervals, 27.10-3
configuration, 27.12-1
description, 27.10-1
end records, 27.10-5
intermediate records, 27.10-4
periodic records, 27.10-6
records, 27.10-3
statistics, 34.5-11
status, 33.11-5
time synchronisation, 27.10-7
time-change records, 27.10-8
accounting records
NVM storage, 27.10-10
paced generation of, 27.10-9
transfer to the data collector, 27.10-10
ACO pushbutton, 33.1-16
ACT, 25.4-7
active card, 18.3-1, 18.3-4
Activity LED
DS-3 card, 18.1-4
E3 card, 18.1-4
Index
Activity Qualified Access, 22.3-28

activity switch, 5.1-9, 5.2-6, 18.1-4, 18.1-12,
18.3-1, 18.3-6, 33.4-1
alarms, 18.1-13, 18.3-6
causes, 18.1-13
fast protection switching, 18.1-15
forcing, 18.1-14, 18.3-6
partitioned mode, 18.1-9
preventing, 33.4-4
programming, 18.1-17
ADAPT/FRZ, 21.7-3
ADD_TO_SET, 23.9-8
address translation
process, 27.14-30
addresses
formats, 27.14-29
hunt group, 27.18-2
supression, 27.14-12
trapping, 27.14-40
validation, 27.14-22
ADI, 23.4-4
ADI_ON/OFF, 23.4-4
adjacent node, 17.2-8
administrative status, 26.2-3, 26.3-3
agents
accounting agent, 38.1-11
NUI server, 27.9-6
NUI server agent, 38.1-11
types, 27.14-14
Aggregate Committed Burst Size parameter,
27.6-21
Aggregate Committed Information Rate
parameter, 27.6-21
AIS, 18.1-15, 22.3-29
Alarm Defeat plug, 13.24-3, 13.25-1
Alarm Indication Signal, 22.3-29
alarm management modes, 35.1-2, 35.2-1
Alarm module, 4.8-9
alarm panel lamp test, 33.1-16
alarm queue overflow handling, 35.2-2
ALARM_TIME, 20.16-4, 35.4-3
ALARM_TIME OC C1-, 18.1-16
alarms
acknowledging alarms, 35.3-6
activity switch, 18.1-13
alarm queue maintenance, 35.1-4
blue alarm, 18.3-6
bus, 3.6-14
Card Activity Change, 18.3-6
Card Failure, 18.3-9
classifications, 35.2-3
IN-3
Index
clear time, 35.4-1

clear yellow alarm, 35.5-3
clearing outstanding alarms, 35.3-9
alarm codes, 35.8-1
frame relay, 35.8-37
system, shelf and card, 35.8-1
X.25, 35.8-45
declare time, 35.4-1
declare/clear times
64 kb/s Codirectional card, 7.1-3
DS-3 card, 5.1-11
DS-3 II card, 5.1-11
E1 card, 5.3-21
E3 card, 5.2-8
MPA card, 5.5-7
T1 card, 5.3-21
TTC2M card, 5.6-8
X.21/V.35 PRI cards, 5.4-7
deleting alarms, 35.3-11
display, 35.3-1
external alarm configuration, 35.7-1
fan alarm reporting, 35.6-1
link status, 35.1-6
non-prioritized, 35.1-7
prioritized, 35.1-7
logging, 35.1-9, 35.2-13
major alarm output, 35.6-4
overview, 35.1-1
power monitoring alarms, 35.6-4
prioritized logging, 35.1-9
remote alarm logging, 35.2-13
ringing generator alarm reporting, 35.6-3
suppression, 7.4-5, 35.2-9
System Restart, 18.1-13
T1 yellow alarm clearing method, 35.5-3
TEP-1 (E) alarm interface
reset indicators, 35.7-5
Wrong Card in Slot, 21.5-7, 21.6-1
ALARMS_CONFIG_QUEUE, 35.2-3
ALAW, 30.3-5
ALaw, 23.3-7, 23.5-4
A-law, 21.2-2
ALaw_INV, 29.3-6
ALB, 20.20-12, 22.3-7
aliases
configuring, 27.6-20
definition, 27.6-7
Allocated XAC Number parameter, 27.15-3,
28.3-2
Allowable Packet Sizes parameter, 27.14-23,
28.2-16
IN-4

NNP 95-2035-01-00-B
ALTERNATE, 21.7-3
Alternate Mark Inversion, 10.6-8
alternate path routing, 26.5-5
alternate route, 26.5-2
AMI, 10.6-8, 10.6-11, 10.6-19, 10.6-22
analog and digital tone tests
GFC3, 36.4-14
Annex F encapsulation, 25.10-3, 27.13-3
Annex G encapsulation, 25.10-2, 27.13-2
ANS
ANS master, 17.2-8, 17.2-9
ANS reachable, 17.2-9
ANS source, 17.2-8, 17.2-10
CPSS, 17.2-7
definition, 33.9-1
displaying links, 17.2-14
enabling, 17.2-13
links, 17.2-8
bidirectional, 17.2-9
disabling ANS, 17.2-15
enabling ANS, 17.2-15
link failure recovery time, 17.2-16
link failure threshold, 17.2-16
SSU failure recovery time, 17.2-17
SSU failure threshold, 17.2-17
unidirectional, 17.2-9
valid, 17.2-15
programmable derived source, 17.2-19
programmable external source, 17.2-19
transport layer, 17.2-7
viewing basic node information, 33.9-2
viewing network topology information,
33.9-4
zones, 17.2-10
ANS v2, 2.1-11
ISSU, 2.1-11
link recovery, 33.9-13
source
derived, 2.1-10
external, 2.1-10
internal, 2.1-10
SSU, 2.1-11
synchronization information
links, 33.9-10
sources, 33.9-7
statistics, 33.9-13, 33.9-15
ANSI, 29.3-4, 29.4-3

NNP 95-2035-01-00-B
ANSI T1.617a
Annex F, 27.13-2
Annex G, 27.13-2
anti-static precautions, 10.8-7, 12.1-2
antistatic strap, 13.1-2
ANTISTREAM, 23.7-7
antistreaming, 23.4-3, 23.7-3
APP_MOD, 20.5-2, 20.16-4
APPLI, 25.9-7
APPLIC, 25.5-3
application cards, 3.14-5
Application module
ID, 33.3-1
revision, 33.3-1
type, 33.3-1
variant ID, 33.3-1
AQA, 18.2-5, 22.3-28
AS_PER_MJU, 23.7-7
ASCII (VT100) terminal, 16.2-5
ASIA, 21.2-4
associated signalling profile, 26.2-3
ASSUMED_ON/OFF, 22.3-7, 22.3-16
ASYNC, 22.3-2
asynchronous device mode, 22.3-2
audio wires, 21.4-1
AUTO, 20.6-3, 23.3-7, 23.5-4, 30.3-5
AUTO_TEI, 30.3-6
automatic log-off, 16.3-11
Automatic Network Synchronization, 17.2-1
B
B channels, 22.3-32, 29.1-2
B1+B2, 29.3-7
B1+B2+D, 29.3-7
B1+D, 29.3-7
B1_ONLY, 29.3-7
B2+D, 29.3-7
B2_ONLY, 29.3-7
B8ZS, 20.8-2
backbone trunks
cost, 27.8-3
definition, 27.1-2
description, 27.8-1
poll timer, 27.8-4
provisioning, 27.8-6
Background diagnostic tests
restart, 33.2-17
sequencing, 33.2-12
viewing, enabling or disabling, 33.2-13
backplanes, 3.6-22
architecture, 3.6-6
Index
HSPS, 3.6-15
HSPS architecture, 3.6-18
HSPS2, 3.6-17
HSPS2 architecture, 3.6-20
locally controlled/peripheral shelf, 3.6-9
switching shelf, 3.6-2
Balanced Transceiver card
faceplate, 4.1-3
LEDs, 4.1-3
overview, 4.1-1
Balanced Transceiver cards and cables, 40.10-1
bandwidth, 25.1-3
bandwidth utilization, 20.19-1
FRE card, 8.4-3
FRS card, 8.5-2
MPA card, 20.20-1, 20.20-7, 20.20-8
barring
within CUGs, 27.15-23
Base LCN parameter, 27.14-15, 28.2-10
Basic Rate Interface, 22.3-32
BASIC_RATE, 29.2-1
baud rate, 17.3-8
baud rate generator, 22.3-9
BAUD_RATE, 17.3-8
Bc, 25.1-4, 25.8-5
B-channel search order, 30.3-5
Be, 25.1-4, 25.8-5
bearer capability, 30.4-4
bearer service, 30.3-5
BEARER_SVC, 30.3-5
BER, 18.1-15, 20.18-6
BERT, 4.6-6
audible error bell, 36.5-6
bit error injection, 36.5-7
bit error insertion rate, 36.5-6
bit patterns, 36.5-7
clearing statistics, 36.5-9
DDS control codes, 36.5-9
GFC3, 4.8-12
overview, 36.5-1
round trip delay measurement, 36.5-11
statistics, 36.5-13
Test card, 36.3-1
test functions, 36.5-6
BERT statistics
clearing statistics, 36.5-16
BIAS_AGNST, 17.3-10, 17.6-17, 17.6-19
BIAS_TOWRD, 17.3-10, 17.6-17, 17.6-19
Bit Error Rate, 20.18-6
IN-5
Index
bit numbering conventions, 23.6-36

blank tab removal
modules, 13.38-1
blue alarm, 18.3-6
bonding
channel identifiers, 23.10-3
inverse multiplexing, 23.10-1
mode 1, 23.10-3
mode 3, 23.10-3
network-side connections, 23.10-6
user-side connections, 23.10-6
booking factor, 26.4-4
BootPROM Generic, 33.3-17
branch channels, 22.4-1
composite input, 23.6-27
DSP card, 23.6-29
line cards, 23.6-28, 23.6-29
user-reserved, 23.6-27
branch identification numbers, 23.7-3
BRANCH_ID, 23.7-5
BRG, 22.3-9
BRI, 22.3-32, 29.1-1, 30.3-4
BRI initialization, 30.3-6
BRI S/T card
3DS-0 transport, 29.3-9
bus configuration, 29.3-5
distribution panel, 3.10-10
diagnostics, 7.2-5
faceplate, 7.2-3
forced activation, 29.4-4
interface mode, 29.3-4, 29.4-3
interface type, 29.3-4, 29.4-3
inversion, 29.3-6
ISDN backup, 29.4-1
ISDN basics, 29.1-1
ISDN channel search, 29.4-2
ISDN loop extension, 29.3-3
layer 1 standard, 29.3-4, 29.4-3
leased lines, 29.3-1
loopbacks, 7.2-5
overview, 7.2-1
pinout, 14.10-1, 14.10-16
power-up LED activity, 33.1-12
transmission, 7.5-6
synchronization, 7.2-5
T3 timer, 29.4-3
T3_TIMER, 29.3-5
IN-6

NNP 95-2035-01-00-B
tandem super-rate configuration, 29.3-7

transport position, 29.3-10
BRI_INIT, 30.3-6
BRI_ST_4/8, 29.2-1
broadband circuits
connections, 31.9-1
BROADCAST, 23.5-6
broadcast mode, 23.5-6
BUF_MOD, 22.2-1
bus configuration, 29.3-5
BUS_CONFIG, 29.3-5, 30.3-6
buses
alarm, 3.6-14
clock bus, 3.6-8
DS-3 card serial bus, 3.6-19
DS-3 card signal bus, 3.6-19
E3 signal buses, 3.6-21
interface bus, 3.6-14
mate E3 card serial bus, 3.6-21
MX interface bus, 3.6-8
power rails, 3.6-8, 3.6-14, 3.6-19, 3.6-21
serial bus, 3.6-7, 3.6-13
system control bus, 3.6-14
Busy LED, 33.1-3
Busy outs
stream and DLCI identifiers, 38.1-5
trunk circuits, 38.1-10
types, 38.1-1
XACs, 38.1-7, 38.1-8
C
C, 22.3-7
C_BIT, 20.6-3
cabinets, 3.5-10
cable exit cover, 13.16-11
cable requirements, 12.1-2
CABLE_NAME, 25.4-6
cables
Class A intershelf, 40.10-1
cabling
DTUs, 10.4-3
external equipment, 10.4-2
CAC, 26.4-5
cadence, 3.8-1, 6.4-1
MRD Channel Unit, 6.9-2
call clearing, 26.5-6
Call Deflection parameter, 27.15-15
call identification allocation, 26.4-4
Call Redirection facility, 27.15-8
call reference allocation, 26.4-4

NNP 95-2035-01-00-B
call routing
definition, 27.7-1
process, 27.7-12
call screening
process, 27.14-36
CALL_LOG, 17.3-7
Called Line Address Modification Notification
facility, 27.15-8
called party number, 30.4-2
CANCEL, 16.3-6
CANCEL_ON/OFF, 23.3-9
card, 16.5-1
failures, 18.3-8
alarm, 18.3-9
ID, 33.3-1, 16.5-5
loopbacks, 36.7-14
power-up diagnostics tests, 33.2-2
reset, 8.6-4, 36.11-1
FRE card, 8.4-7
FRS card, 8.5-8
revision, 33.3-1
type, 33.3-1
display, 16.5-5
variant ID, 33.3-1
view, 33.3-2
Card Activity Change alarm, 18.3-6
CARD_COMM, 30.2-1
CARRIER, 19.3-4
CAS, 20.6-5
Cascade A Insert LED, 33.1-3
Cascade B Insert LED, 33.1-3
Cascade Module
FIP connection, 14.15-1
cause codes, 34.4-1
format, 27.14-24
viewing and resetting, 34.4-4
C-bit parity, 20.6-2
CBW, 21.3-7
CC, 27.15-1
CCITT X.50,, 23.6-11
CCITT X.51,, 23.6-11
CCITT X.54,, 23.6-11
CCM, 5.3-9, 17.1-6, 18.2-6, 20.1-2, 20.3-2
CCS, 20.6-5
CCT, 20.3-3
CH_SRCH_HI/LO, 30.3-5
channel identifiers, 16.4-1
channel search facility
hunt groups, 30.4-3
Channel Service Unit Module, 5.3-11
Index
Channel unit
line balance calibration, 40.1-1
power-up diagnostics tests, 33.2-2
channel-associated signalling, 20.6-5
CHAR_LEN, 22.3-14
character length, 22.3-13
charging facilities, 27.15-7
parameter, 27.15-11
Charging Information Subscription parameter,
27.15-11
chassis ground, 3.5-9, 10.8-1, 20.18-4
CHG_SET, 23.9-2, 23.9-5, 23.9-8
CI, 16.2-4
CIR, 25.1-4
CIR, for connection management, 26.4-4
circuit configuration
copying, 17.1-5
displaying, 17.1-3
naming, 17.1-5
circuit connections, 17.1-1
add-drop, 31.9-1
broadcast unidirectional, 17.1-8
configuring, 17.1-2
pass-through, 31.9-1
simple bidirectional, 17.1-6
simple unidirectional, 17.1-7
TS0, 17.1-9
types, 17.1-1
UPSR, 31.9-1
circuit identifiers, 16.4-1
Circuit LED, 33.1-3
circuit protection, 20.16-1
24 DS-0 super-rate, 20.16-1
CPSS connections, 20.14-3
circuits connections
HCV voice compression, 23.3-12
CLAMN, 27.15-8
CLASS, 17.2-23
class
node, 17.2-23
timing sources, 17.2-23
class-of-service parameters
configuring for encapsulated access,
27.13-22
configuring for FASTbus trunks, 27.6-21
guarantee, 26.4-5
parameters, 25.1-4, 25.8-5
clear cause codes, 37.1-2
clear channels, 20.12-6
Clear On Calling Address Failure parameter,
28.3-8
IN-7
Index
clear time, 35.4-1

Clear Timer (T33) parameter, 28.2-13
Clear Timer parameter, 27.14-18
CLEAR_64K, 30.4-4
CLEAR_TIME, 25.4-8
clearing demerit points, 18.3-8
CLIP_ON/OFF, 23.3-10
CLLM, 25.1-7
clock bus, 3.6-8
Clock card
diagnostics, 4.2-5
faceplate, 4.2-4
high-impedance jumper, 13.40-1
LEDs, 4.2-5
modules, 4.2-4
overview, 4.2-1
test points, 4.2-5
clock inversion, 20.19-6, 20.20-1, 20.20-15
clocking, 22.3-8, 22.3-21
DCCs, 10.5-7
clocking source, 20.19-6, 20.20-4
closed user group
parameters, 27.15-22
CLR_FAULTS, 18.3-8
CMI, 20.10-4
CODE_1, 20.11-3
CODE_2, 20.11-3
Collection Interval parameter, 27.10-20
combining packets, 27.2-10
commissioning the nodes, 14.1-1
Committed Burst Size, 25.1-4
committed burst size
27.13-22
committed information rate
27.13-22
description, 25.1-4
Committed Rate Measurement Interval, 25.1-4
Common Carrier card
backplane interface, 4.4-2
channel unit installation, 13.43-1
channel unit interface, 4.4-3
code A
code B
code C
front-secured, 13.42-1
IN-8

NNP 95-2035-01-00-B

LEDs, 4.4-3
overview, 4.4-1
Common Carrier card, 19.3-4
common channel signalling, 20.6-5
COMP_CONV, 18.2-6
COMP_CONV OC E3-, 20.3-2
COMP_CONV/NO_CONV, 20.2-4
COMP_LAW, 23.5-4, 23.11-3
Companding Conversion Module, 5.3-9, 17.1-6
companding law, 23.3-7, 23.4-4, 23.5-4
TTC2M card, 20.3-5
voice interface cards, 21.2-2
compliance
to frame relay encapsulation standards,
8.5-1, 27.13-2
to Recommendation X.2, 27.3-1
to Recommendation X.35, 27.3-5
COMPOSITE, 23.6-49, 23.7-5
composite input, 23.6-27
compressor connections, 20.4-4
CON_DIGITL, 36.6-8
configuration
example, 26.1-7
summary, 26.1-6
configuring
1+1 protection switching options, 31.4-10
broadband circuits, 31.6-1
HSA card port synchronization, 31.5-1
HSA card type, 31.3-1
OC-3 and STM-1 card DCC, 31.8-1
operation mode, 31.4-11
switching type, 31.4-11
traffic protection, 31.4-1
TU-12 card NU bits, 31.17-1
working card, 31.4-10
working circuit, 31.4-10
WTR and hold off timers, 31.4-11
configuring circuits
direct, 27.13-7
encapsulation, 25.10-5, 27.13-8
trunks, 27.8-3
configuring the data collector XAC, 27.11-9
congestion
filtering, 25.3-3, 25.6-9
handling by the RTP, 27.2-7
thresholds, 25.4-7
25.10-8, 27.13-9
27.13-15

NNP 95-2035-01-00-B
Congestion Timer parameter, 27.14-6, 28.2-5

connection admission control, 26.4-5
Connection maintenance
active and inactive connections, 36.6-6
bidirectional and unidirectional
connections, 36.6-6, 36.6-8
display, 36.6-10
monitor, 36.6-2
overview, 36.6-1
preferred and protecting, 36.6-6
restrictions, 36.6-7
split-back, 36.6-4
split-through, 36.6-3
terminate and leave, 36.6-5
warning messages, 36.6-8
connection management
definition, 26.1-4
process, 26.4-1
setting parameters, 26.4-4
connections
24 DS-0 super-rate circuits, 20.16-5
2B1Q channel unit, 22.3-36
3DS-0 format, 22.3-36
5DS-0 format, 22.3-36
B channels, 29.3-11
bidirectional, 2.1-14
bonding, 23.10-6
BRI S/T card, 29.3-11
cascading VCBs, 23.5-8
compressor, 20.4-4
CPSS, 17.6-20, 17.6-23, 17.6-33
D channels, 29.3-11, 30.5-2
DLC, 25.7-1
external devices, 14.10-1
FASTbus DLCs, 25.7-7
frame streams, 25.5-4
FRS/FRE circuits, 25.5-4
FRS-to-FRS card DLCs, 25.7-6
local DLCs, 25.7-5
protecting, 18.2-1, 18.2-6
SRMs, 23.6-50
SRS circuits, 23.9-9
subrate FRS streams, 25.9-10
super-rate, 20.15-7
Test card, 4.11-8
unidirectional, 2.1-14
VCBs, 23.5-7
voice compression circuits, 23.3-14
Consolidated Link Layer Management
Messages, 25.1-7
CONT_CHK, 23.6-45, 23.6-48
CONTCHK, 22.4-6
Index
CONTIGUOUS, 20.3-3, 20.15-4

continuity checking, 23.6-45
LEDs
power-up sequence, 14.2-1
serial ports, 4.6-5
software upgrading, 4.6-7
Control card
8+ module, 19.3-2
active and inactive, 18.1-4
database reset, 4.5-7, 4.6-5
diagnostics, 4.5-8, 4.6-6
Downloadable Memory Module, 4.5-6
external synchronization source defaults,
39.2-9
faceplate, 4.5-6, 4.6-4
functional description, 4.5-1, 4.6-2
ISSU Module, 4.5-5
LEDs, 4.5-7
locally controlled shelf default
configuration database, 39.2-10
Memory Module 2, 4.5-5
overview, 4.5-1
Peripheral shelf default configuration
database, 39.2-10
power-up LED activtiy, 33.1-11
removal, 14.3-1, 14.4-1
replace an inactive, 40.8-1
replacing, 18.1-18
reset database, 39.2-4
serial ports, 4.5-6, 17.3-2, 17.3-3
SSU Module, 4.5-5
Switching shelf default configuration
database, 39.2-10
Y-cable connection, 17.3-3
Control Packet Switching System (see CPSS),
17.6-1
control redundancy
and access levels, 17.5-1
configuring, 18.1-2
single-shelf, 18.1-5
control signals, 5.5-6, 20.20-12, 20.20-14, 22.3-4
enable/disable LL, 20.20-15
enable/disable LL or RL, 22.3-5
OOS conditioning, 20.20-1, 20.20-12,
20.20-14, 20.20-15, 22.3-7
propagation, 22.3-16
IN-9
Index
convection, 3.9-1
cooling
convection, 3.9-1
DTU heat dissipation, 10.2-10
equipment, 3.9-1
fan trays, 3.9-4
forced air, 3.9-1
FRE card, 10.2-5
guidelines, 10.2-1
heat deflection, 3.9-1
heat deflectors, 3.9-2
heat dissipation, 10.2-6
high speed peripheral shelf, 10.2-4
J24R/J24, 3.9-5
methods, 3.9-1, 10.2-3
PE card, 10.2-6
peripheral shelf, 10.2-4
requirements, 3.9-1, 10.2-3
Switching shelf, 10.2-3, 10.2-4
COPY XAC parameters, 27.16-1
COPY_ADJ, 17.1-5
COPY_TO, 17.1-5
COS guarantee, 26.4-5
setting, 26.4-5
cost, 17.6-5
Cost parameter, 27.8-3
counters, 26.2-7
CPC, 30.2-1
B-channel search order, 30.3-5
bearer capability, 30.4-4
bearer service, 30.3-5
BRI initialization, 30.3-6
call status information reporting, 30.3-5
called party number, 30.4-2
configuration procedure locations, 30.1-1
diagnostics, 8.1-4
dial delay, 30.4-5
dial or non-dial, 30.4-5
directory number, 30.4-1
duplicate, 30.4-3
directory number format, 30.4-2
faceplate, 8.1-2, 9.1-3
functional description, 8.1-1, 9.2-3
interface standard, 30.3-4
interface type, 30.3-4
ISDN backup, 30.3-1, 30.4-1
ISDN channel search, 30.3-2, 30.4-1
ISDN indices, 30.4-1
ISDN Layer 2 and Layer 3 message tracing,
33.7-3
ISDN Layer 2 status display, 33.7-6
ISDN protocol trace status display, 33.7-6
IN-10

NNP 95-2035-01-00-B
ISDN protocol tracing, 33.7-3

LEDs, 8.1-2
number of B channels, 30.3-4
number of channels, 30.4-6
number of retries, 30.4-5
overview, 8.1-1, 31.2-1
PCM encoding, 30.3-5
pinout, 14.10-17
serial ports, 8.1-4, 17.3-4
SETUP message, 30.4-2, 30.4-5
trace buffer, 33.7-2
verification, 30.4-5
CPC card
pinout, 14.10-1
CPSS, 17.2-7, 17.3-7, 17.6-1
4 kb/s channels, 17.6-27
64 kb/s channels, 17.6-20
8 to 56 kb/s channels, 17.6-29
ANS, 17.2-7
backplane, 17.6-2
configuring CPSS timers, 17.6-37
connection type, 17.6-16
connections, 17.6-3
connections to FRS cards, 17.6-33
cost, 17.6-5
CPSS routing protocol, 17.6-37
dedicated, 17.6-2
dedicated cost, 17.6-19
definition, 33.8-1
domain number, 17.6-16
domains, 17.6-4
FASTbus CPSS circuits, 17.6-2
FASTbus CPSS connections, 17.6-35
grooming, 17.6-10
in FDL, 17.6-23
in TS0, 17.6-23, 20.20-4, 20.20-9
interface speed, 17.6-19
master/slave protocol, 17.6-7
messages, 17.6-1
MPA card, 20.20-4, 20.20-9
network layer services, 17.6-5
NOC number, 17.6-16
node number, 17.6-15
node parameters, 17.6-14
options, 17.6-18
PAD, 22.1-8

NNP 95-2035-01-00-B
PRI cards
channel limitations, 17.6-11
router version, 17.6-4, 17.6-17
satellite delay, 17.6-19
serial ports, 17.3-10
shared, 17.6-1
shared cost, 17.6-17
status information, 17.6-10
subrate channels, 17.6-27
subrate sets, 23.9-7
systems supporting, 1.2-1
v1, 17.6-3
v2, 17.6-3
versions, 17.6-3
viewing nodes, 33.8-1
CPSS Loopback Detected alarm
logging restrictions, 35.1-9
CPSS_4K, 23.9-7
CPSS_COST, 17.3-10
CPSS_MODEM, 17.3-7
CPSSv2
node information display descriptions,
33.8-6
viewing links
all, 33.8-9, 33.8-10
Craft Interface, 16.2-4
crankback, 26.5-5
CRC4 reframing, 20.18-10
CRC4_STATS, 20.18-11
CRCREFR OC E18-, 20.18-10
Critical Alarm LED, 33.1-3
CRN, 27.15-8
CSU, 20.1-2
CSU Loopback Activated alarm
CSU Module, 5.3-11
CSU module, 18.3-6
CTL, 19.3-2
CTL_MON, 23.7-7
CTS, 20.20-12, 22.3-7
CUG index, 27.15-20
CUGIA, 27.15-24
CUGOA, 27.15-24
CUSTOM, 20.11-3, 22.3-7
D
D channel, 22.3-32, 29.1-2
D+ channel, 22.3-34
D+CV channel, 22.3-34
D4, 20.6-3
Index
D4 framing, 20.6-2, 20.6-3

DAILY_ON/DAILY_OFF, 34.1-34, 34.1-41
DATA, 20.11-3, 20.13-1, 22.2-1, 22.2-2, 22.2-4
data collector, 27.11-3
data collector agent, 27.11-1
statistics, 34.5-12
data collector agent parameters, 27.11-4
data collector agent XAC, 27.11-1
Data Communications Equipment, 22.3-2
Data interface cards
circuit parameters, 22.3-1
data interface cards, 3.14-4, 22.1-1
configuring, 22.1-8
slots, 22.2-1
data interface clocking, 10.5-11
asynchronous, 10.5-1
clock independence, 10.5-5
clock source, 10.5-2
clock source options, 10.5-4
clocking mode, 10.5-3
DCE, 10.5-2
DTE, 10.5-2
external, 10.5-5
independent, 10.5-5
internal, 10.5-5
limitations, 10.5-6
locked, 10.5-5
overview, 10.5-1
rate adaption, 10.5-6
RS-422 DCC, 10.5-7
slave, 10.5-4
super-rate, 10.5-6
synchronous, 10.5-1
terminology, 10.5-4
data interface connections, 10.4-3
27LC2, 10.4-3
2B1Q, 10.4-3
2B1Q Channel Unit, 10.4-3
4WTO Channel Unit, 10.4-4
DCC, 10.4-3
DNIC, 10.4-3
DS0-DP Channel Unit, 10.4-4
OCU-DP Channel Unit, 10.4-4
data interfaces, 20.1-1
Data LED, 33.1-3
Data Link Connections, 8.5-2
data link connections, 25.1-2
data position, 23.6-43
Data Termination Equipment, 22.3-2
IN-11
Index
Data Termination Units

cabling, 10.4-3
Data Termination Units (see also DTUs), 3.12-1,
22.1-6
DATA_BW, 23.11-3
DATA_CFG, 23.8-5
DATA_MON, 23.7-7
DATA_POSN, 22.4-4, 23.6-49, 23.11-3, 25.9-9
DATA_TXLVL, 23.8-5, 23.11-3
Database management
activity switches, 39.1-12
backing up a major or minor node, 39.1-5
NVM checking and resetting, 39.1-3
reconcile, 39.1-1
reconcile minor node card, 39.1-21
restore, 39.1-10
LED activity, 39.1-16
messages, 39.1-16
summary, 39.1-13
switching cards, 39.1-12
restore Switching shelf controlled system,
39.1-17
verify, 39.1-1, 39.1-8
database reconciliation, 18.1-13
Database reset
FRE card, 39.2-7
database reset, 4.5-7, 4.6-5, 39.2-1
Database verification, 39.1-8
DATE, 17.4-2
date, 17.4-2
D-bit on PVCs, 27.17-8
dc power feeds
23-Inch locally controlled shelf
dc power feed connections, 13.33-1
23-Inch peripheral shelf
23-Inch switching shelf
cable clamp, 13.30-1
cable clamp, 13.31-2, 13.32-1
dc distribution box terminal block,
13.31-2, 13.32-1
dc power feed connections, 13.31-2,
13.32-1
IN-12

NNP 95-2035-01-00-B

cable clamp, 13.31-2, 13.32-1
13.31-2, 13.32-1
13.32-1
HSPS
dc power supplies
input specifications, 3.7-8
power cables, 3.7-10
dc terminal block jumpers
23-Inch locally controlled shelf
illustr., 13.33-1
23-Inch peripheral shelf
illustr., 13.33-1
23-Inch switching shelf
illustr., 13.33-1
illustr., 13.30-1
illustr., 13.30-1
illustr., 13.30-1
illustr., 13.31-2, 13.32-1
illustr., 13.31-2, 13.32-1
illustr., 13.31-2, 13.32-1
HSPS
illustr., 13.30-1
DCC card
DCCs
clocking, 10.5-7, 22.3-8
limitations, 10.5-6
configuring, 22.1-6, 22.1-8
connectors, 7.3-6
control signal propagation, 22.3-16
control signals, 22.3-4
DCE, 22.3-2
device mode, 22.3-2
distribution panels, 3.10-1
DTE, 22.3-2
DTE1 mode
to set, 10.5-8
duplex method, 22.3-3
faceplate, 7.3-5

NNP 95-2035-01-00-B
loopbacks, 7.3-6
multidrop data bridges, 22.3-15
overview, 7.3-1
parity, 22.3-13
RTS signal propagation, 22.3-16
RTS/CTS delay, 22.3-4
Special mode
to set, 10.5-11
SRMs, 23.6-24
stop bits, 22.3-13
synchronous, 22.3-2
DCD, 20.20-12, 22.3-7
DCE, 20.19-6, 20.20-1, 20.20-4, 22.3-2
DCP, 24.2-2
DCP card
faceplate, 8.2-2
overview, 8.2-1
pinout, 14.10-1, 14.10-18
serial ports, 8.2-3, 17.3-4, 17.6-33
DDS, 22.2-2, 23.6-47, 23.6-49, 23.9-7, 23.9-8,
25.9-7, 25.9-10
DDS Access, 23.6-5
DDS Core, 23.6-6
DDS loopbacks, 36.7-6
DDS rate adaption
cards supporting, 23.6-4
continuity checking, 23.6-45
DDS Access, 23.6-5
DDS Core, 23.6-6
formatting, 23.6-4
MJUs, 23.7-3
multi-drop data bridges, 23.7-2
secondary channel, 23.6-45
SRMs, 23.6-19
subframe position, 23.6-43
DDS Telco, 23.6-5
DDS_ACCESS, 22.2-2, 23.6-47, 23.7-5
DDS_CORE, 23.6-47, 23.7-5
DDS_HCM, 22.3-17, 22.4-5, 23.7-5
DDS_OR_HCM, 25.9-4
DE3 card, 20.1-1
LEDs, 14.2-1
Index
DE3 card
alarm LED numeric value, 39.2-6
default configuration database, 39.2-12
loopbacks, 36.7-26
DECL_TIME, 23.7-7
DEDICATED, 30.2-1
dedicated cost, 17.6-5, 17.6-19
Default NPI parameter, 27.14-22, 28.2-16
Default NUA parameter, 27.15-13
Default NUI Format parameter, 27.15-16
Default Receive Packet Size parameter, 28.3-6
Default Receive Throughput Class parameter,
28.3-5
Default Receive Window Size parameter,
28.3-4
Default Send Packet Size parameter, 28.3-6
Default Send Throughput Class parameter,
28.3-5
Default Send Window Size parameter, 28.3-5
default user, 26.3-3
defaults
flow control, 27.15-26
NPI, 27.14-22
throughput class, 27.15-26
deflection, 27.15-15
DEL_FR_SET, 23.9-8
DEL_SET, 23.9-8
delay equalization, 5.5-4, 20.15-4, 23.10-2
DELTA, 20.4-7
delta signalling, 20.4-1
Delta Value parameter, 27.6-20
DELTA_G3, 20.4-7
Demerit
system monitoring, 33.4-2
demerit points, 18.3-8
demerits, 33.4-1
activity switch caution, 33.4-4
DERIVED, 17.2-19, 17.2-22
derived timing source, 17.2-1
DESELECT, 17.2-23
DEST, 25.8-3
destination address, 26.5-2
device gender, 20.20-1, 20.20-4, 22.3-2
device mode, 22.3-2
device type, 17.3-6
device types
personal computer, 17.3-7
printer, 17.3-6
VT100 terminal, 17.3-6
DGM, 20.17-1
IN-13
Index
diagnoistic tests
General Facilities cards, 4.8-16
Diagnostic Code Mapping parameter, 28.2-17
Diagnostic code mapping parameter, 28.1-9
diagnostic codes, 37.1-3
enhanced, 27.14-25
diagnostics
background and directed, 33.2-9
background on inactive card, 33.2-13
BRI S/T card, 7.2-5
cicuit level, 33.2-15
Clock card, 4.2-5
Control card, 4.6-6
Control card, 4.5-8
CPC, 8.1-4
directed, 33.2-17, 33.2-18
DS-0 DP Channel Unit, 7.7-4
DS-3 card, 5.1-10
E&M card, 6.2-5
E&M Channel Unit, 6.6-4
E1 card, 5.3-19
E3 card, 5.2-7
failures, 33.2-16
forced at power-up, 33.2-19
HSA card directed, 33.2-18
LGE card, 6.3-5
LGE Channel Unit, 6.7-4
LGS card, 6.4-5
LGS Channel Unit, 6.8-4
partitioned mode, 18.1-9
Switching card, 4.9-4
Switching Interface card, 4.10-5
system, 33.2-1
system-wide, 33.2-15
T1 card, 5.3-19
Test card, 4.11-7
TTC2M card, 5.6-6
DIAL, 30.4-5
dial delay, 30.4-5
dial or non-dial, 30.4-5
DIAL_DELAY, 30.4-5
Digital Signal Cross-connect Module, 5.3-11
Digital Signal Processor card, 23.1-1
DIR_NUM, 30.4-2
direct access
IN-14

NNP 95-2035-01-00-B
direct circuit
direct circuits
Direct Connect cards, 22.1-1
directory number, 30.4-1
duplicate, 30.4-3
directory number format, 30.4-2
DISCONNECT, 17.1-6
display, 16.3-4
Display LED, 33.1-3
displaying information, 16.5-1
disruption in service, 18.3-1
dissipation
power and heat dissipation, 10.2-7
Distant Error Rate Exceeded alarm
DISTANT_OFF/ON, 20.9-10
distribution box
ac distribution box, 13.26-1
dc distribution box, 13.26-1
ac distribution box connections,
13.26-1
dc distribution box connections,
13.26-1
ac distribution box, 13.24-3, 13.25-1
ac power supply connections, 13.24-3,
13.25-1
backplane connections, 13.24-3, 13.25-1
dc distribution box, 13.24-3, 13.25-1
dc power supply connections, 13.24-3,
13.25-1
power supply connections, 13.24-3,
13.25-1
Class B
backplane connections, 13.27-1
ac power supply connections, 13.27-1
dc power supply connections, 13.27-1

NNP 95-2035-01-00-B

HSPS
13.25-1
backplane connections, 13.24-3, 13.25-1
13.25-1
DCCs, 3.10-1
overview, 3.10-1
PRI RJ45, 3.10-10
RS-232, 3.10-2
S/T BRI, 3.10-10
universal distribution panel, 3.10-7, 5.5-4
V.35, 3.10-6
X.21, 3.10-3
DIV_2, 22.4-5, 23.6-47
DIV_3, 22.4-5, 23.6-47
DLC class of service, 25.8-1
DLC connections
FASTbus, 25.7-7
FRS-to-FRS card, 25.7-6
local, 25.7-5
status, 25.7-3
types, 25.7-1
DLC identifiers, 16.4-1
DLCI allocation, 26.4-3
DLCs
FRE card, 8.4-2
FRS card, 8.5-2
DMS-100, 25.11-1
DNIC, 22.2-2, 27.15-1
DNIC Line card, 22.1-2
pinout, 14.10-1, 14.10-19
DNIC Line card
DOMAIN_NUM, 17.6-16
domains, 17.6-4, 17.6-16
doppler buffer, 20.20-1, 20.20-16
double bandwidth, 19.3-2
DPM, 22.2-2
DPM2, 22.2-2, 22.4-3
DPT, 21.3-7
DRAGA, 22.3-10
DRM, 5.3-10, 20.1-2, 20.5-2, 20.16-4
DS_LEVEL, 20.16-4
Index
DS-0 DP Channel Unit

diagnostics, 7.7-4
faceplate, 7.7-3
LEDs, 7.7-3
loopbacks, 7.7-4
overview, 7.7-1
signalling codes, 7.7-4
DS0 Port connectors
GFC3, 4.8-15
DS0 Rx/Tx Clock connectors
GFC3, 4.8-15
DS-0A, 22.4-5, 22.4-6, 23.6-48, 23.6-49, 23.7-5,
23.9-7, 23.9-8, 25.9-7
DS-0A_EC, 22.4-5, 22.4-6, 23.6-48, 23.6-49,
23.7-5, 23.9-8
DS-0B, 22.4-5, 22.4-6, 23.6-48, 23.6-49, 23.9-7,
23.9-8
DS-0B_2.4, 25.9-7
DS-0B_4.8, 25.9-7
DS-0B_9.6, 25.9-7
DS0-DP Channel Unit
configuring, 22.1-8
functions, 22.1-5
pinout, 14.10-34
DS0-DP channel unit
error correction, 22.3-30
DS-1 framing, 20.6-3
DS-3 Alm LED, 33.1-3
DS-3 card, 20.1-1
Activity LED, 18.1-4
diagnostics, 5.1-10
fault classes, 20.9-8
framing, 20.6-1
LED power-up sequence, 14.2-1
LEDs, 5.1-7, 14.2-1
line length, 20.7-2
loopbacks, 5.1-10, 36.7-26
modules, 5.1-5
overview, 5.1-1
protection switching, 18.1-15
RBS, 20.12-4, 31.15-3
redundancy, 5.1-9
replacing, 18.1-18
serial bus, 3.6-19
IN-15
Index
signal bus, 3.6-19

statistics, 5.1-11
zero code suppression, 20.8-1
JB7, 20.8-2
transparent, 20.8-1
DS-3 card
DS-3 framing, 20.6-3
DS-3 II card
diagnostics, 5.1-10
loopbacks, 5.1-10, 36.7-26
modules, 5.1-5
overview, 5.1-1
redundancy, 5.1-9
statistics, 5.1-11
DS-3 II card
reset database, 39.2-5
DSP card
configuration features and options, 23.1-2
connecting SRS circuits, 23.9-9
multi-drop data bridges, 23.7-2
PCM multi-drop data bridges, 23.4-5
SRM branch channels, 23.6-29
SRM connections, 23.6-51
SRMs, 23.6-25
VCB, 23.5-1
DSP cards
DSP3, DSP4 and DSP5H card
HCV alarm declare/clear times, 8.3-4
DSP cards and IMC
6 dB attenuation pad, 23.3-10
AC15 tone detection, 23.3-11
HCV alarm declare/clear times, 8.3-4
fax, 23.8-123.8-5, 23.8-6
stHCV and fax, 23.11-1
DSP5 and DSP5H card
overview, 8.3-1
IN-16

NNP 95-2035-01-00-B
echo cancellation, 23.3-9

echo cancellation return loss threshold,
23.3-10
echo clipping, 23.3-10
echo clipping threshold level, 23.3-10
faceplate, 8.3-3
HCV signalling types, 23.3-2
HCV voice compression connections,
23.3-12
IMC BONDING timers, 23.2-3
LD-CELP post filter, 23.3-11
loopbacks, 8.3-4
overview, 8.3-1
rate adaption
types, 23.6-1
SRMs, 23.6-16
DSP2 card, 23.1-1
DSP3 card, 23.1-1
DSP4 card, 23.1-1
loopbacks, 36.7-11
DSP4 card
DSP5H
DSP resource reset, 36.11-2
DSR, 20.20-12, 22.3-7
DST_N_CIRC, 20.15-4
DSX, 20.1-2
DSX-1 Module, 5.3-11
DTE, 20.19-6, 20.20-1, 20.20-4, 22.3-2
DTE1 mode, 10.5-8
DCCs
to set, 10.5-8
DTR, 17.3-9, 20.20-12
DTU
debounce synchronization timer
DTUs, 22.2-4
2610 MainStreet CPSS PAD, 22.1-8
26XX MainStreet, 3.12-2

NNP 95-2035-01-00-B

27XX MainStreet, 3.12-4
activity switching, 22.3-25
and line cards, 22.1-2
cabling, 10.4-3
connecting, 22.1-6
heat dissipation, 10.2-10
loopbacks, 36.7-21
mate port configuration, 22.3-25
overview, 3.12-1
port redundancy
Line cards, 7.4-5, 22.3-24
super-rate circuits, 22.3-22
Dual E1 card, 20.1-1
BER, 20.18-6
E-bit option, 20.18-9
framing, 20.6-1
ground, 20.18-4
ISDN backup, 30.3-1
NU bit, 20.18-2
overview, 5.7-1
pinout, 14.10-1, 14.10-20, 14.10-21
HDSL module, 14.10-22, 14.10-23
SES, 20.18-5
unidirectional signalling types, 20.12-6
voice compression, 20.4-1
Dual E1 card
faceplate, 5.3-17
LEDs, 5.3-18
loopbacks, 5.3-19
modules, 5.3-8
overview, 5.3-1
SES limit, 20.17-7
split/monitor connections, 5.3-21
Dual E1 card (Wire-wrap adapter)
pinout, 14.10-25
HDSL module, 14.10-23
Dual E1-2 card
trunk conditioning, 20.9-1
Dual E1-2 card
alarm declare/clear times, 35.4-1, 35.4-3
ANS, 17.2-14
BER, 20.18-6, 20.18-8
card slot, 20.2-1
CPSS, 17.6-3, 17.6-20, 17.6-22
Index

E-bits, 20.18-9
faceplate, 5.3-17
fault signalling, 20.10-1, 20.10-4
framing, 20.6-1
ground, 20.18-4
ISDN, 20.2-1, 20.2-4
LEDs, 5.3-18
link monitoring, 20.17-1, 20.17-4
loopbacks, 5.3-19, 36.7-26
modules, 5.3-8, 20.2-1
NU bit, 20.18-2
overview, 5.3-1
pinout
backplane and bulkhead, 14.10-24
faceplate, 14.10-26
wire-wrap adapter, 14.10-25
power-up diagnostic tests, 33.2-1
quality statistics
clear local and remote, 34.1-36
display local and remote, 34.1-36
printing, 34.1-38
reset, 36.11-1
SA4 bit, 20.18-6, 20.18-8
SES, 20.18-5
SES limit, 20.17-7
statistics, 5.3-21
trunk conditioning - custom, 20.11-3
Dual E3 card, 20.1-1
Dual Optical Extension card, 5.7-1, 20.1-1,
20.1-2
Dual Optical Extension card pinout, 14.10-1
Dual Rate Adaption Gate Array, 10.5-7, 22.3-10
Dual T1 card
framing, 20.6-1
pinout, 14.10-1, 14.10-27, 14.10-28
HDSL module, 14.10-30, 14.10-31,
14.10-33
timeslot 24 signalling, 20.5-1
TS24 loopback detection, 20.14-4
Dual T1 card, 20.1-1
faceplate, 5.3-14
IN-17
Index
LEDs, 5.3-16
loopbacks, 5.3-19
modules, 5.3-8
overview, 5.3-1
SES limit, 20.17-7
Dual T1 card (Wire-wrap adapter)
pinout, 14.10-28
Dual T1-2 card, 20.1-1
framing, 20.6-1
ISDN backup, 30.3-1
trunk conditioning, 20.9-1, 20.9-7
Dual T1-2 card
24 DS-0 connection, 20.16-5
errored seconds, 20.17-2
faceplate, 5.3-14
LEDs, 5.3-16
link monitoring, 20.17-1, 20.17-2
loopbacks, 5.3-19, 36.7-45
maintenance facilities, 36.1-2
modules, 5.3-8
on-fault loopback detection, 20.14-5
overview, 5.3-1
pinout, 14.10-32
quality statistics
clear all, 34.1-33, 34.1-37
clear error events, 34.1-33, 34.1-37
print options, 34.1-34, 34.1-41
print time, 34.1-35, 34.1-42
printing, 34.1-35, 34.1-42
statistics supported, 34.1-31
stop printing, 34.1-35, 34.1-42
view, 34.1-33
SES limit, 20.17-7
statistics, 5.3-21
sub-channels, 20.4-5
super-rate protecting connections, 20.16-1
DUAL_SHELF, 18.1-5
full, 22.3-3
half, 22.3-3
IN-18

NNP 95-2035-01-00-B
E
E&M card, 21.1-1
audio wires, 21.4-1
diagnostics, 6.2-5
faceplate, 6.2-3
line balance, 21.7-1
line impedance, 21.6-2
loopbacks, 6.2-5, 36.7-48
overview, 6.2-1
pinout
A-law, 14.10-35
Mu-law, 14.10-36
signalling leads, 6.2-5, 36.2-1
signalling type, 21.3-1
statistics, 6.2-5
TLP ranges, 21.5-8
audio wires, 21.4-1
diagnostics, 6.6-4
faceplate, 6.6-3
LEDs, 6.6-3
loopbacks, 6.6-5
overview, 6.6-1
pinout, 14.10-37, 14.10-38, 14.10-39
signalling modes, 21.3-1
signalling states, 6.6-5
statistics, 6.6-5
variants, 6.6-2
E&M signalling mode, 21.3-1
E+M, 20.12-5, 20.12-8, 21.2-3, 21.3-4
E.164, 26.3-2
E.164 address format, 27.15-1
E-1 Alarm 1 LED, 33.1-4
E-1 Alarm 2 LED, 33.1-4
E-1 Alarm LED, 33.1-4
E1 card, 20.1-1
CCM, 20.3-2
E1/T1 Conversion Modules, 20.3-1
faceplate connectors, 5.7-5
framing, 20.6-3
LEDs, 5.7-5

NNP 95-2035-01-00-B
loopbacks, 36.7-26
NU bit, 20.18-2
options, 20.18-1
pinout, 14.10-40, 14.10-41
SAM, 20.3-2
signal ground, 20.18-4
E1 card
diagnostics, 5.3-19
faceplate, 5.3-17
interface redundancy, 5.3-19
LEDs, 5.3-18
loopbacks, 5.3-19
modules, 5.3-8
overview, 5.3-1
E1 HDSL LIM, 5.3-12
E1 Line Interface module, 5.3-13
E1 link quality monitoring, 20.18-11
E1_HDSL, 20.1-2
E1_LIM, 20.1-2
E1_PRI, 30.3-4
E1_SIG, 20.12-8, 21.3-7
E3 card, 20.1-1
circuit hierarchy, 5.2-2
diagnostics, 5.2-7
E1 link quality monitoring, 20.18-11
E1id, 5.2-2
E2id, 5.2-2
E3id, 5.2-2
faceplate, 5.2-3
FIC card slot configuration, 20.2-5
framing, 20.6-3
LEDs, 5.2-4
loopbacks, 5.2-7
modules, 5.2-3
NU bit, 20.18-2
options, 20.18-1
overview, 5.2-1
redundancy, 5.2-6
replacing, 18.1-18
signal buses, 3.6-21
Index

statistics, 5.2-8
EC, 20.12-8, 21.3-7
EC_ON/OFF, 22.3-30
with HCV, 23.3-9
echo cancellation return loss threshold, 23.3-10
echo clipping, 23.3-10
echo clipping threshold level, 23.3-10
Electrostatic Discharge (ESD) precautions,
10.8-7
EMPTY, 19.3-3
encapsulated access
circuits
configuring class-of-service parameters,
27.13-22
configuring frame stream bandwidth,
27.13-22
FRAD, 27.13-4
encapsulation
circuits
connecting, 27.13-17
of LAPB frames, 8.5-1, 27.13-2
over backbone trunks, 27.6-1
encapsulation circuits
connecting, 25.10-10
creating, 25.10-5
FRS card, 8.5-3
viewing, 25.10-6
END_TO_END, 22.3-7, 22.3-16
ENH_TRANSP, 22.3-21
Enhanced Diagnostic Codes parameter,
27.14-25
Enhanced locally controlled shelf
applications, 2.1-1
architecture, 2.2-3
backplane, 3.6-15
interface and application cards, 2.1-5
overview, 1.3-1
shelf frame, 3.5-6
shelf organization, 3.4-1
system cards, 2.1-2
enhanced transparent rate adaption, 23.6-2
environmental requirements, 10.2-1
IN-19
Index
eoc, 7.4-4, 36.8-1

Equalization, 21.11-1
EQUALIZATN, 20.18-11
EQUIDIST, 20.15-4
Error LED, 33.1-4
Error Rate Exceeded alarm
ERROR_OFF/ON, 20.9-10
ERROR_RATE, 18.1-16
ERROR_TIME, 18.1-16
errored seconds, 20.17-2
Escape R, 16.3-4
ESF, 20.6-2, 20.6-3
Ethernet ports, 17.3-1, 17.3-4
ETSI, 29.3-4, 29.4-3
EUROISDN, 30.3-4
EUROPE, 21.2-4
EVEN, 22.3-14
Event Monitored XAC Status parameter,
28.2-18
Excess Burst Size, 25.1-4
excess burst size
27.13-22
EXISTING, 21.7-3
EXP, 19.3-3
Expander card, 16.4-9
faceplate, 4.7-3
LEDs, 4.7-3
modules, 4.7-2
overview, 4.7-1
EXT_FREQ, 17.2-25
EXTEND_BUS, 29.3-5
extended superframe format, 20.6-2
EXTERNAL, 17.2-19, 17.2-22, 22.3-12
external address format, 27.14-29
external alar ms
dual shelf configurations, 10.7-3
external alarm connector pinouts, 14.14-1
external alarms, 10.7-1, 35.7-1
Fuse and Alarm Panel, 10.7-1
input and output external alarms, 10.7-2
inputs, 10.7-1
J18 on 23-Inch locally controlled shelf (Alm
Mod 1), 14.14-16
IN-20

NNP 95-2035-01-00-B
J18 on 23-Inch locally controlled shelf (Alm

Mod 2), 14.14-17
J18 on 23-Inch peripheral shelf (Alm Mod
1), 14.14-12
J18 on 23-Inch peripheral shelf (Alm Mod
2), 14.14-13
J18 on 23-Inch switching shelf (Alm Mod
1), 14.14-8
J18 on 23-Inch switching shelf (Alm Mod
2), 14.14-9
J18 on Class A locally controlled shelf (Alm
Mod 1), 14.14-14
J18 on Class A peripheral shelf (Alm Mod
1), 14.14-10
J18 on Class A peripheral shelf (Alm Mod
2), 14.14-11
J18 on Class A switching shelf (Alm Mod
2), 14.14-8
J18 on Class B locally controlled shelf (Alm
Mod 1), 14.14-16
J18 on Class B locally controlled shelf (Alm
Mod 2), 14.14-17
J18 on Class B peripheral shelf (Alm Mod
1), 14.14-12
J18 on Class B peripheral shelf (Alm Mod
2), 14.14-13
J18 on Class B switching shelf (Alm Mod 1),
14.14-8
J18 on Class B switching shelf (Alm Mod 2),
14.14-9
J19, 10.7-3
outputs, 10.7-1
overview, 10.7-1
TEP-1(E) equivalence, 10.7-1, 10.7-3
external equipment
cabling, 10.4-2
external prefix, 27.14-38
external timing, 10.6-1
connectors, 10.6-2, 10.6-12
inputs
1.544 Mb/s AMI, 10.6-8, 10.6-19
2.048 MHz, 10.6-7, 10.6-17
8 kHz, 10.6-7, 10.6-17
DDS composite clock, 10.6-8, 10.6-19
J13, 10.6-7, 10.6-17
J14, 10.6-10, 10.6-21
J17, 10.6-8, 10.6-11, 10.6-19, 10.6-22
J20, 10.6-17
J21, 10.6-21

NNP 95-2035-01-00-B
outputs
1.544 MHz, 10.6-10, 10.6-21
2.048 MHz, 10.6-10, 10.6-21
8 kHz, 10.6-10, 10.6-21
overview, 10.6-1
receivers, 10.6-2, 10.6-12
sources, 10.6-2, 10.6-12
external timing source
J13, 14.7-3
J17, 14.7-3
J13, 14.7-3
J17, 14.7-3
J17, 14.7-3
external timing source OC B2-, 17.2-1
External Translation Prefix parameter, 28.2-23
F
F.SYNC LED, 33.1-4
F_POSITION, 22.4-6, 23.6-48, 23.9-8, 25.9-7
Faceplate LEDs, 33.1-4
facilities
Call Redirection, 27.15-8
Called Line Address Modification
Notification, 27.15-8
charging, 27.15-7
Charging Information, 27.15-11
closed user group, 27.15-20
CUG Selection, 27.15-21
CUGIA, 27.15-24
CUGOA, 27.15-24
Fast Select, 27.15-7
Fast Select Acceptance, 27.15-7
Local Charging Prevention, 27.15-11
negotiation, 27.14-11
NUI Override, 27.9-2
NUI Subscription, 27.15-15
Reverse Charge Acceptance, 27.15-10
Facility Data Link, 17.6-23
FAIL_THRES, 17.2-16, 17.2-17
FAIL_TIMED, 17.2-16
failed circuits, 18.3-9
Failed State alarm
FAILED_OFF/ON, 20.9-10
fan alarm reporting, 35.6-1
Index
fan tray
power connector
23-inch shelf, 13.4-5
Class A shelf, 13.4-2
Class B shelf, 13.4-3
fan trays, 3.9-4
FAS_STATS, 20.18-11
Fast Select Acceptance facility, 27.15-7
Fast Select facility, 27.15-7
FASTbus
36120 ID, 25.4-7
congestion thresholds, 25.4-7
CPSS, 17.6-2
interface, 8.4-3
MAC, 25.4-1
NORMAL, 25.4-2
overview, 8.4-3
PHY, 25.4-1
port A, 25.4-1
port B, 25.4-1
station ID, 25.4-7
station status, 25.4-3
status, 25.4-4
used for backbone trunks, 27.8-8
WRAP_A, 25.4-2
WRAP_B, 25.4-2
FASTbus CPSS
FRE card, 8.4-4
FASTbus Interconnect Panel, 13.8-1
Bypass modules, 3.11-1
Cascade modules, 3.11-1
components, 3.11-1
FASTbus modules, 3.11-1
FASTbus protocol statistics, 34.3-7, 34.3-21
Fault classes, 35.2-3
Distant/Yellow, 35.2-3, 35.4-1
Error, 35.2-3
Failed, 35.2-3
Frame/Red, 35.2-3, 35.4-1
Fault LED, 33.1-4
fault processing, 18.3-1, 18.3-7
fault signalling, 20.10-1, 20.16-1, 21.8-1
configuring, 21.8-1
FAULT_HNDL, 20.9-7, 20.9-10, 20.14-6, 20.16-4
FAULT_SIG, 20.4-7, 20.9-7, 20.10-4, 20.11-3,
20.16-4, 36.3-4
fax
data bandwidth, 23.8-2
DSP4, DSP5 and DSP5H card, 23.8-1
fax transmission level, 23.8-4
NSF frame handling, 23.8-3
IN-21
Index
transmission level, 23.8-4

transmission rate, 23.8-2
FAX_CONFIG, 23.8-5
FAX_EN/DIS, 23.11-3
FAX_ENABLE/DISABL, 23.8-1, 23.8-2
FAX_RATE, 23.8-2, 23.11-3
FCC compliance
shelves, 1.3-4
FDL, 17.6-23
Features
100 Mb/s Packet Switched FASTbus, 1.2-5
2B+D Interfaces
2B1Q, 1.2-1
BRI S/T, 1.2-1
DNIC, 1.2-1
512 kb/s DCS, 1.2-4, 1.2-5
64 Mb/s DCS, 1.2-1
ADPCM, 1.2-1
ANS, 1.2-1
CCITT X.50, 1.2-1
CPSS Routing, 1.2-1
Data Interfaces
4WTO, 1.2-1
64 kb/s Codirectional, 1.2-1
DS0-DP, 1.2-1
OCU-DP, 1.2-1
RS-422 (RS-449, RS-530-A, V.36), 1.2-1
V.24/RS-232, 1.2-1
V.35, 1.2-1
X.21/V.11, 1.2-1
DDS (Digital Data Service), 1.2-1
Diagnostics, 1.2-1
Diagnostics and Split/Monitor
Connections, 1.2-4
Digital and Metallic Test Access, 1.2-1
Echo Cancellation, 1.2-1
FAST Frame Relay Switching, 1.2-1
G3 FAX Demodulation/Modulation, 1.2-1
HCM, 1.2-1
HCV Compression, 1.2-1
I.460 (n*8 kb/s transparent), 1.2-1
International Voice Signalling Conversion,
1.2-1
ISDN Channel Search, 1.2-1
ISDN ISDN Loop Extension, 1.2-1
ISDN Leased Line Backup, 1.2-1
LAN interfaces and bridges
8230 MainStreet Ethernet Little Bridge,
1.2-1
Token Ring/802.5, 1.2-1
IN-22

NNP 95-2035-01-00-B
Multi-drop Data Bridging, 1.2-1

PCM Bridging, 1.2-1
Primary Rate Interfaces
1.544 Mb/s T1, 1.2-1
1.544 Mb/s T1-2, 1.2-1
2.048 Mb/s E1, 1.2-1
2.048 Mb/s TTC2M, 1.2-1
34.368 Mb/s E3, 1.2-4, 1.2-5
44.736 Mb/s DS-3, 1.2-4, 1.2-5
56 and n*64 kb/s V.35 PRI, 1.2-1
56 and n*64 kb/s X.21 ESI PRI, 1.2-1
56 and n*64 kb/s X.21 PRI, 1.2-1
RAP+ID (Reserved Alternate Path with
Immediate Diversion), 1.2-1
SRM, 1.2-1
SRS, 1.2-1
Voice Conference Bridging (Hoot n
Holler), 1.2-1
Voice Interfaces
4WDX, 1.2-1
E&M, 1.2-1
LGE (FXO), 1.2-1
LGS (FXS), 1.2-1
MRD, 1.2-1
X.25 Encapsulation and Decapsulation,
1.2-1
X.25 Switching, 1.2-1
ferrite core
Class A Peripheral A peripheral shelf
Class A Switching A peripheral shelf
HSPS
FIC card
FILTERING, 25.4-8
FIP
Cascade Module connection, 14.15-1
chassis ground, 13.10-11
chassis ground point, 13.10-11
FRE card connections
Class A Shelves, 14.15-1
Class B Shelves, 14.15-1
LEDs, 14.15-1
module installation, 13.39-1
module positions, 13.39-1, 14.15-1
Firmware Generic, 33.3-17
Firmware ID, 33.3-1

NNP 95-2035-01-00-B
FIX_LONG, 21.7-3
FIX_SHORT, 21.7-3
FIXED TEI, 30.3-6
FIXED_BIAS, 21.3-9
FIXED_BIAS signalling mode, 21.3-8
defaults, 27.15-26
Flow Control Negotiation facility, 27.14-11
Flow Control Negotiation parameter, 27.14-23
Flow Control Timer parameter, 28.2-15
FLOW_CTRL, 17.3-9
force boot, 36.11-2
FORCE_ON/OFF, 23.11-2
forced activation, 29.4-4
forced activity switching, 22.3-27
FORCED_ON/OFF, 22.3-7, 22.3-16
Fractional T1, 20.1-2
loopbacks, 36.7-45
module, 20.1-3
frame, 3.5-1
frame bandwidth, 23.6-42
frame bandwidth location, 23.6-43
frame relay
encapsulation, 25.10-1
interface to 5ESS, 25.11-1
interface to DMS-100, 25.11-1
SVC call display, 33.6-1
switched access, 25.11-1
frame relay encapsulation, 27.13-2
frame relay ping, 33.6-8
frame relay SVC
functionality, 26.1-2
overview, 26.1-1
physical requirements, 26.1-2
Frame Response Timer (T1) parameter, 28.2-4
Frame Response Timer parameter, 27.14-4
frame reversal
frame routing rules, 27.6-14
Frame Sequence Numbering parameter,
27.14-4, 28.2-3
frame size
27.13-15
Frame stream, 25.6-1
frame stream, 25.5-1
frame streams
FRE card, 8.4-2
FRS card, 8.5-2
Index
Frame switch congestion, 25.3-1

FRAME_1, 20.6-7
FRAME_2, 20.6-7
FRAME_BIT, 20.19-4
FRAME_OFF/ON, 20.9-10
FRAME_SIZE, 25.6-6
FRAME_TYPE, 20.6-6
frames
Class A rear-entry, 3.5-2
Class A side-entry, 3.5-2
Class B rear-entry, 3.5-3
HSPS rear-entry, 3.5-5
HSPS2 rear-entry, 3.5-5
rack mounting brackets, 3.5-8
Telco rear-entry, 3.5-4
Type I, 3.5-2
Type II, 3.5-2
framing, 20.6-1
31 channels, 20.6-5
CAS, 20.6-5
C-bit parity, 20.6-2
CCS, 20.6-5
D4 framing, 20.6-2
DS-3 card, 20.6-3
ESF framing, 20.6-2
HCM, 20.20-1, 20.20-8
M13, 20.6-2
MPA card, 5.5-1, 20.20-1, 20.20-8, 20.20-9
super-rate connections and frame types
(E1), 20.6-5
transmit as received, 20.6-1
X.21 NTU, 20.6-5
X.21 PRI card, 20.6-7
Framing Error Rate Exceeded alarm
FRANCE, 21.2-4
FRC_ACTIVATE, 29.4-4
FRC_STNDBY, 22.3-28
FRE, 25.2-1
FASTbus CPSS connections, 17.6-35
FRE card, 25.1-1
36120 ID, 25.4-7
cable name, 25.4-6
card reset, 8.4-7
cooling guidelines, 10.2-5
CPSS timers, 17.6-37
DLCs, 8.4-2
faceplate, 8.4-5
FASTbus, 8.4-3
FASTbus congestion thresholds, 25.4-7
FASTbus CPSS, 8.4-4
IN-23
Index
FASTbus DLC, 8.4-2

FASTbus overview, 25.4-1
FIP connections
local DLC, 8.4-2
loopbacks, 8.4-8
overview, 8.4-1
pinout, 14.10-42
PVCs, 8.4-3
serial port, 8.4-7
station ID, 25.4-7
FRE card
busy out, 38.1-1, 38.3-1
CPSS circuit statistics, 34.3-21
database reset, 39.2-7
detail statistics, 34.3-16
loopbacks, 36.7-24
NVM, 33.3-26
protocol statistics, 34.3-7
removal, 38.3-1
statistics, 34.3-11
FRF.4, 26.2-5
FRS, 25.2-1
FRS card, 25.1-1
card reset, 8.5-8
CPSS connections, 17.6-33
DLCs, 8.5-2
encapsulation circuits, 8.5-3
faceplate, 8.5-6
loopbacks, 8.5-8
modules, 8.5-4
overview, 8.5-1
pinout, 14.10-42
PVCs, 8.5-2
serial ports, 8.5-7, 17.3-4
FRS card
and LAPB encapsulation, 27.13-6
busy out, 38.1-1
CPSS circuit statistics, 34.3-9, 34.3-11
discards statistics, 34.3-4
IN-24

NNP 95-2035-01-00-B
loopbacks, 36.7-24
NVM, 33.3-28
statistics, 34.1-35, 34.1-42
view, 34.3-9
stream and station protocol statistics,
34.3-7, 34.3-9
FRS circuits
viewing, 27.13-14
FRS/FRE cards
access rate, 25.1-4, 25.5-3
application, 25.5-3
bandwidth, 25.1-3
Bc, 25.1-4, 25.8-5
Be, 25.1-4, 25.8-5
CIR, 25.1-4, 25.8-5
class-of-service parameters, 25.1-4
configuration overview, 25.1-15
configuration procedure options, 25.1-15
congestion management, 25.1-5
congestion thresholds, 25.3-3, 25.6-5
connections, 25.5-4
data link connections, 25.1-2
DLC class of service, 25.8-1
DLC connections, 25.7-1
DLC status, 25.7-3
FASTbus DLCs, 25.7-7
FRS-to-FRS card DLCs, 25.7-6
heartbeat polling interval, 25.6-7
inter-frame flags, 25.6-6
link management protocol, 25.1-11, 25.6-6
local DLCs, 25.7-5
PVC, 25.1-3
PVC management auto discovery protocol,
25.1-14
status enquiry message timeout, 25.6-8
status message rate, 25.6-8
stream, 25.5-1
subrate multiplexing, 25.9-1
Tc, 25.1-4
transport bandwidth, 25.5-3
FULL_DPLX, 22.3-3
full-duplex, 22.3-3
Fuse and Alarm Panel, 10.7-1
Fuses
23-inch shelves, 40.14-1
DC powered Class B shelves, 40.13-1
inline fuse, 40.12-1

NNP 95-2035-01-00-B
G
G3_FAX, 23.12-2
GAIN, 23.5-4
GAIN_RANGE, 21.5-7
gateway call routing
process, 27.7-21
gateway routing
definition, 27.7-10, 27.7-19
Gateway TNIC/CNIC parameter, 28.2-18
GDI protocol, 27.11-3
General Facilites cards
pushbuttons, 4.8-15
Alarm module, 4.8-9
BERT, 4.8-12
components, 4.8-7
diagnostic tests, 4.8-16
DS0 Test Access unit, 4.8-11
faceplate, 4.8-13
GFC
GFC3
analog and digital tone tests, 36.4-14
card operation parameters and
options, 19.2-1
DS0 port, 36.4-12
DS0 Port connectors, 4.8-15
Metallic Test Access connections,
36.4-14
MTA connectors, 4.8-15
Rx and Tx DS0 clock connectors, 4.8-15
LEDs, 4.8-14
Metallic Test Access unit, 4.8-10
order wire, 4.8-7, 36.4-1, 36.4-2
Order Wire connectors, 4.8-15
overview, 4.8-1
power rail test points, 4.8-15, 36.1-4
synchronization clock, 4.8-9
TEP-1(E) equivalence, 4.8-15
test port, 4.8-8, 36.4-1
Test Port connectors, 4.8-15
tone generator, 36.4-1
tone generator and test port, 36.4-7
Tone Test unit, 4.8-11
Generate Accounting Records on Unsuccessful
Calls parameter, 27.10-18
Generate Accounting Records parameter,
27.10-18
Generate Alarms parameter, 28.2-18
Index

parameter, 27.14-24
Generic Frame Router
description, 27.6-9
statistics, 34.5-4
GERMANY, 21.2-4
GFC/GFC2
E1 on the GFC2, 13.40-1
J3 on the GFC, 13.40-1
GFC3
metallic test access, 36.3-4
GFR address
definition, 27.6-7
GFR Address parameter, 27.6-17
Global Address Table
description, 27.7-1
example entries, 27.7-3
viewing, 27.7-25
wildcard entries, 27.7-3
global routing
definition, 27.7-1
process, 27.7-2
ground
chassis
23-Inch Shelves, 13.10-4
Class A Shelf, 13.10-11
connection points, 13.10-11
HSPS2, 13.10-4
signal
23-Inch Shelves, 13.10-4
connection points, 13.10-2
HSPS2, 13.10-4
grounding
anti-static precautions, 10.8-7
chassis, 10.8-1
Electrostatic Discharge (ESD) precautions,
10.8-7
overview, 10.8-1
racks and cabinets, 10.8-2
shelves, 10.8-2
shield, 10.8-1
signal, 10.8-1
GS, 20.12-5, 20.12-8, 21.3-7
GS_EM, 21.3-7
IN-25
Index
H
HALF_DPLX, 22.3-3
half-duplex, 22.3-3
HCM, 5.5-1, 20.20-1, 20.20-8, 22.4-4, 22.4-6,
23.6-48, 23.6-49, 23.9-8, 23.11-3, 25.9-7, 25.9-9
HCM rate adaption, 23.3-5, 23.6-3, 23.6-17
data position, 23.6-43
frame bandwidth, 23.6-42
frame bandwidth location, 23.6-43
signalling, 23.6-38
HCM_BW, 22.4-6, 23.6-48, 23.9-8
HCM_TRANS, 22.2-2, 22.4-3, 23.6-47
HCV, 23.8-5
HCV alarm declare and clear times
DSP3 and DSP4, 8.3-4
HCV signalling types
DSP3, DSP4 and DSP5H cards, 23.3-2
companding law, 23.3-7
connecting circuits, 23.3-14
HCM rate adaption, 23.3-5
rate adaption parameters, 23.3-4
transparent rate adaption, 23.3-4
HCV_CONFIG, 23.11-2
HCV_OPTION, 23.11-3
HCV_RATE, 23.11-3
HCVD, 23.4-5, 23.5-3, 23.6-47, 23.7-5
HDLC encapsulation, 25.10-1
HEARTBEAT, 25.6-7
heartbeat polling interval, 25.6-7
heat dissipation, 10.2-6, 10.2-7
High Capacity Voice, 23.3-1
High impedance monitor metallic connection,
36.3-7
High speed peripheral shelf
HOT, 18.1-10
Hot Billing parameter, 27.15-5
hot standby, 5.2-6
HSA card
loopbacks, 36.7-51
power-up LED, 33.1-16
IN-26

NNP 95-2035-01-00-B

HSA cards, 3.14-6
broadband circuit connections, 31.9-1
broadband circuits, 31.6-1
HSPS
13.25-1
chassis ground jumpers, 14.12-1
Class A
dc terminal block jumpers, 13.30-1
ferrite core installation, 13.30-1
13.25-1
distribution box to backplane connections,
13.24-3, 13.25-1
non redundant Switching to HSPS, 13.16-5
redundant Switching to HSPS, 13.16-5
HSPS2
backplane BNC connectors, 14.13-1
backplane coax connector pinouts, 14.13-1
coax connector ground option
ground option configuration, 14.13-1
ground points, 13.10-4
non redundant Switching to HSPS2,
13.16-7
Power Supply card faceplate test points,
36.1-7
Power Supply card installation, 13.22-4
redundant Switching to HSPS2, 13.16-7
signal ground point, 13.10-2
hub domains, 27.6-2
hub switch
definition, 27.6-4
HUB_ID, 22.2-2
hunt group
addresses, 27.18-2
redirection address, 27.18-2
hunt groups, 30.4-3

NNP 95-2035-01-00-B
I
I, 22.3-7
I.430/ANSI, 29.3-4, 29.4-3
I/F_MODE, 22.3-2, 29.3-4, 29.4-3
I/F_SPEED, 22.3-21, 22.3-24, 22.3-29, 22.4-4,
22.4-5, 22.4-6, 23.6-48, 23.6-49, 23.9-8, 25.9-7,
25.9-9, 25.9-10, 36.3-3
I/F_TYPE, 22.3-1
Identifiers, 32.2-1
circuit, 32.2-1
circuit group, 32.2-1
Data Link Connection (DLC), 32.2-1
link, 32.2-1
peripheral shelf (s), 32.2-7
Permenant Virtual Circuit (PVC), 32.2-1
shelf, 32.2-1
shelf-select jumper, 32.2-6
slot, 32.2-1
stream, 32.2-1
switching shelf (w), 32.2-6
identifiers, 16.4-1
channel, 16.4-1
circuit, 16.4-1
circuit group, 16.4-1
DLC, 16.4-1
HSPS, 16.4-6
HSPS numbers (x), 16.4-6
ISDN index OC A4-, 16.4-1
link, 16.4-1
locally controlled shelf (s), 16.4-6
peripheral shelf (s), 16.4-6
peripheral shelf numbers (x), 16.4-6
shelf, 16.4-1
shelf numbers, 16.4-6
shelf-select jumper, 16.4-5
slot, 16.4-1
stream, 16.4-1
switching shelf (w), 16.4-5
IDLE, 20.10-4, 21.8-1
IDLE_TIME, 23.7-7
IFM, 5.3-14, 20.1-2
IHTU modules, 5.3-12
IMC
bonding, 23.10-1
BONDING timers, 23.2-3
configuration features and options, 23.1-8
IN_BAND, 20.14-6
Inactivity Timer parameter, 28.2-4, 28.2-14
Inactivity Timer parameter (link layer), 27.14-5
Index
Inactivity Timer parameter (network layer),

27.14-19
in-band loopback detection, 20.14-6
Incoming Fast Select Acceptance parameter,
27.15-12
parameter, 27.14-20, 28.2-15
parameter, 28.3-7
Incoming Transit Calls Allowed, 28.2-17
Incoming Unrestricted Fast Select Allowed
parameter, 28.3-7
INDEPNT, 22.3-13
INFINITE, 30.4-5
INFO_RATE, 25.8-3
information display, 16.5-1
input gain, 23.5-4
Insert TNIC parameter, 28.2-19
installation
ac power source fluctuations, 10.2-2
altitude, 10.2-1
antistatic precautions, 12.1-2
anti-static strap, 10.2-2
cable requirements, 12.1-2
checklists, 12.3-1
common procedures, 11.1-2
Electrostatic Discharge, 10.2-2
grounds, 10.2-2
location, 10.2-1
post-installation procedures, 11.1-2
power, 10.2-2
pre-installation procedures, 11.1-1
procedures, 11.1-1
temperature and humidity, 10.2-1
tool requirements, 12.1-2
working space, 10.2-2
installing modules, channel units and cards
overview, 13.37-1
Intelligent System Synchronization Unit (ISSU)
Module, 4.5-5
Interface module
ID, 33.3-1
revision, 33.3-1
type, 33.3-1
variant ID, 33.3-1
interface speed
CPSS, 17.6-19
DDS rate adaption, 23.6-42
FRS/FRE cards, 25.5-3
OCU-DP channel unit, 22.3-29
IN-27
Index
super-rate DCC circuits, 22.3-18

super-rate Line card circuits, 22.3-22
X.50 rate adaption, 23.6-42
interface standard, 30.3-4
interface type, 22.3-1, 29.3-4, 29.4-3, 30.3-4
inter-frame flags, 25.6-6
interlock code, 27.15-20
Intermediate Record Interval parameter,
27.10-20
intermediate records, 27.10-4
INTERNAL, 22.3-12
internal address format, 27.14-29
internal prefix, 27.14-38
internal timing source, 17.2-1
Internal Translation Prefix parameter, 28.2-23
internodal hunting C15-, 27.18-2
intershelf cables
23-Inch locally controlled shelf, 13.14-1
23-Inch peripheral shelf, 13.14-1
Class A
removal, 40.10-1
Class A locally controlled shelf, 13.14-5
Class A peripheral shelf, 13.14-5
Class A switching shelf, 13.13-1
Class B locally controlled shelf, 13.14-1
Class B peripheral shelf, 13.14-1
Class B switching shelf, 13.13-1
intershelf connections, 3.6-8, 3.6-14, 3.6-20,
3.6-21
interval reports list, 33.11-31
INTFC_PROT, 18.1-6
Inverse Multiplexer card, 23.1-1
INVERSION, 29.3-6
inversion
PRI cards, 20.13-1
RS-422 DCCs, 22.3-14
INVERT, 20.19-6, 20.20-15, 22.3-14
ISDN, 20.2-1, 29.3-4, 29.4-3
access to frame relay, 25.11-1
call status information reporting, 30.3-5
ISDN backup, 29.4-1, 30.3-1, 30.4-1
ISDN basics, 22.3-32, 29.1-1
ISDN channel search, 29.4-2, 30.3-2, 30.4-1
hunt groups, 29.4-2, 30.4-3
ISDN index identifiers, 16.4-1
ISDN indices, 30.4-1
ISDN Layer 2 status display, 33.7-6
ISDN loop extension, 22.3-33, 29.3-3
IN-28

NNP 95-2035-01-00-B
ISDN protocol tracing

buffer configuration, 33.7-2
disable, 33.7-3
enable, 33.7-3
message display, 33.7-3
status display, 33.7-6
ISDN/NON_ISDN, 20.2-4, 20.2-5
ISSU Module, 2.1-11, 4.5-5
J
J2, 3.8-3, 3.8-8
J24F, 3.8-3, 3.8-5
J24R, 3.8-8, 3.8-10
J30, 3.8-8, 3.8-11
JAPAN, 21.2-4
JB7, 20.8-2
jitter, 20.19-8, 20.20-16
K
k parameter, 27.14-4
L
L1 LED, 33.1-5
L1_TYPE, 29.3-4, 29.4-3
L2 LED, 33.1-5
LAPB, 27.14-2
LAPB Address Assignment parameter, 28.1-9,
28.2-2, 28.2-3, 28.2-4, 28.2-5, 28.2-8, 28.2-9,
28.2-10, 28.2-11, 28.2-12, 28.2-13, 28.2-14,
28.2-15, 28.2-16, 28.2-17, 28.2-18, 28.2-19,
28.2-23, 28.2-24, 28.2-25, 28.2-26, 28.3-2,
28.3-3, 28.3-4, 28.3-5, 28.3-6, 28.3-7, 28.3-8
Large multiplexer systems
applications, 2.1-1
MainStreet large multiplexers
description, 1.2-1
shelf requirements, 1.3-2
layer 1 standard, 29.3-4, 29.4-3
LCDC, 21.3-7
LD-CELP post filter, 23.3-11
leaf domains, 27.6-1
leaf switch
definition, 27.6-4

NNP 95-2035-01-00-B
leased line connections

fibre optic, 10.3-4
metallic, 10.3-2
overview, 10.3-1
leased lines, 29.3-1
LED, 33.1-5
normal activity, 33.1-1
power-up activity, 33.1-10
level 0, 17.5-7
level 1 through 4 access, 17.5-3
level 5 access, 17.5-2
LEVEL_0, 17.5-7
LEVEL_1, 17.5-8
LEVEL_2, 17.5-8, 20.15-4, 29.3-7
LEVEL_3, 17.5-8
LEVEL_4, 17.5-8
LEVELS, 21.5-7, 21.9-2
LGE, 20.12-5, 20.12-8
LGE card, 21.1-1
card variants, 6.3-2
diagnostics, 6.3-5
faceplate, 6.3-3
loopbacks, 6.3-5
overview, 6.3-1
pinout, 14.10-43
statistics, 6.3-6
LGE card
loopbacks, 36.7-48
channel unit variant, 6.7-2
diagnostics, 6.7-4
faceplate, 6.7-3
LEDs, 6.7-3
loopbacks, 6.7-4
overview, 6.7-1
pinout, 14.10-44
statistics, 6.7-5
LGE/LGS card, 21.1-1
LGE/LGS cards
TLP ranges, 21.5-8
Index
LGS, 20.12-5, 20.12-8

LGS card, 21.1-1
cadence, 6.4-1
card variants, 6.4-3
diagnostics, 6.4-5
faceplate, 6.4-3
loopbacks, 6.4-5
overview, 6.4-1
pinout, 14.10-45
statistics, 6.4-5
LGS card
loopbacks, 36.7-48
diagnostics, 6.8-4
faceplate, 6.8-3
loopbacks, 6.8-5
overview, 6.8-1
pinout, 14.10-46
statistics, 6.8-5
variants, 6.8-3
LGS Channel Unit specifications, 6.8-5
LIM, 5.3-11, 5.3-13
configuring, 21.7-1
Line cards
alarm suppression, 7.4-5
and DTUs, 22.1-2
clocking, 22.3-8
control signal propagation, 22.3-16
control signals, 22.3-4
device gender, 22.3-2
device mode, 22.3-2
DTU port redundancy, 7.4-5
eoc, 7.4-4, 22.3-38, 36.8-1
faceplate, 7.4-3
functions, 22.1-2
link quality statistics, 7.4-5
loopbacks, 7.4-4
modules, 7.4-2
IN-29
Index

overview, 7.4-1
parity, 22.3-13
SRMs, 22.4-1
stop bits, 22.3-13
synchronous, 22.3-2
line cards
DPM, 23.6-24
DPM2, 23.6-24
SRM branch channels, 23.6-28, 23.6-29
SRMs, 23.6-24
configuring, 21.6-2
Line Interface Module, 5.3-11
Line LED, 33.1-5
LINE_BAL, 21.7-1
LINE_IMP, 21.6-2
LINE_LNGTH, 20.7-2
link fault, 18.3-5
link identifiers, 16.4-1
link layer
parameters, 27.14-2
timers, 27.14-4
Link Layer Interface Type parameter, 27.14-3
link layer protocol timers and counters, 26.2-7
link management protocol, 25.6-6
link monitoring, 20.17-1, 20.17-2, 20.17-4
link quality monitoring, 20.18-11
Link quality statistics
Line cards, 7.4-5
Link status alarms
non-prioritized, 35.1-7
non-prioritized alarm logging, 35.1-9
prioritized, 35.1-7
prioritized alarm logging, 35.1-9
LINK_RECOV, 17.2-16
links, 17.2-8
LIS LED, 33.1-5
listen-only mode, 23.5-5
LL, 20.20-12, 22.3-7
LL_ENABLE/DISABLE, 22.3-5
LLCP, for route trace, 33.6-6
Load Balancing parameter, 27.6-19
Load sharing and link redundancy, 27.7-18
IN-30

NNP 95-2035-01-00-B
Local Address Table

description, 27.7-9
example entries, 27.7-10
viewing, 27.7-26
Local Address Validation parameter, 27.14-22
Local Charge Prevention parameter, 27.15-11
local routing
definition, 27.7-1
process, 27.7-9
LOCAL_NUM, 30.4-2, 30.4-5
23-Inch
25-pair connectors, 14.10-1
chassis ground points, 13.10-11
external alarm connector J18 (Alm
Mod 1), 14.14-16
Mod 2), 14.14-17
intershelf cable connection, 13.14-1
J13 ground option, 14.7-3
J14, 14.8-1
redundancy jumpers, 13.11-1
signal ground points, 13.10-2
23-inch
dc fuse replacement, 40.14-1
Power Supply card faceplate test
points, 36.1-8
Class A
13.26-1
dc terminal block/cable harness,
13.30-1
Mod 1), 14.14-14
Mod 2), 14.14-14
external alarm connector J19, 14.14-15
J14, 14.8-1

NNP 95-2035-01-00-B
redundancy jumpers., 13.11-1

Class B
cable clamp, 13.31-2, 13.32-1
13.31-2, 13.32-1
13.32-1
dc terminal block jumpers, 13.31-2,
13.32-1
distribution box to backplane
Mod 1), 14.14-16
Mod 2), 14.14-17
J14, 14.8-1
Locally controlled system
system cards, 2.1-3
LOCKED, 22.3-13
logical channel
allocation rules, 27.14-9
selection rules, 27.14-9
log-off, 16.3-7, 16.3-11
LONG, 20.7-2, 21.7-1, 21.7-2
LONG_BUF, 20.19-8
Loop balance
LOOP_EXT, 22.2-4
loopback
Test card, 4.11-8
loopback detection
CPSS loopback detection, 20.14-3
Index
Loopback LED, 33.1-5

loopbacks
alternating, 36.7-7
BRI S/T card, 7.2-5
circuit and slot, 36.7-1
Common Control card, 36.7-2
data interface cards, 36.7-14
DCCs, 7.3-6
DDS, 36.7-6
digital cross-connect, 36.7-2
disable, 36.7-11
DS-0 DP Channel Unit, 7.7-4
DS-3 card, 5.1-10
DSP cards and IMC, 8.3-4
DSP4 and Test card, 36.7-11
DTUs, 36.7-21
E&M card, 6.2-5
E1 card, 5.3-19
E3 card, 5.2-7
FRE card, 8.4-8
FRE card, 36.7-24
FRS card, 8.5-8
FRS card, 36.7-24
HSA card, 36.7-51
latching, 36.7-6
LGE card, 6.3-5
LGS card, 6.4-5
Line cards, 7.4-4
MPA card, 5.5-6, 20.20-1, 20.20-12
node management session initiated, 36.7-3
overview, 36.7-1
Packet card, 36.7-24
PE card, 8.6-4
primary rate, 36.7-26
fractional T1, 36.7-45
super-rate, 36.7-2
support, 36.7-3
T1 card, 5.3-19
TTC2M card, 5.6-7
types, 36.7-5
viewing loopbacks, 36.7-9
IN-31
Index
voice cards, 36.7-48

X.21/V.35 PRI cards, 5.4-6
Los Clock A LED, 33.1-5
Los Clock B LED, 33.1-5
LoSync LED, 33.1-5
LOW_NIB/HIGH_NIB, 22.3-36
LP_DET_ON/OFF, 25.9-5
LPBK_DETEC, 20.14-6
LPBK_OFF/ON, 20.9-10
LS, 20.12-5, 20.12-8, 21.3-7
LS_EM, 21.3-7
LT, 22.3-33
LULT, 22.2-4, 22.3-33
LUNT, 22.2-4, 22.3-33
M
M.SYNC LED, 33.1-7
M13, 20.6-2, 20.6-3
M44 voice compression, 20.4-1
MAC, 25.4-1
MainStreet X.25
configuration summary, 27.4-4
protocols A1-, 27.1-3
switch, 27.1-2
MainStreetXpress 36130
system description, 1.2-1
maintenance commands
undoing, 38.1-12
Maintenance Connections (see Connection
maintenance)
, 36.6-12
Major Alarm LED, 33.1-7
major nodes, 16.2-2
MAKE_ACT, 18.3-6
Mapper card
CRC-4, 31.18-1
Mapper card narrowband circuit
framing, 31.13-1
inversion, 31.16-1
MARK, 22.3-7, 22.3-14
MASTER, 22.3-28, 23.7-3
master and slave designations, 18.3-3
mate E3 card serial bus, 3.6-21
MATE/NO_MATE, 22.3-25
parameter, 27.9-11
IN-32

NNP 95-2035-01-00-B
Maximum Frame Window Size parameter,

27.14-4, 28.2-3
Maximum Information Frame Size parameter,
27.14-6, 28.2-5
Maximum Time Between Transfers parameter,
27.11-7
MCT, 25.4-7
MEDIUM, 20.7-2
message traffic recorder, see MTR, 33.6-2
messages, 17.6-1
Metallic Test Access connections
GFC3, 36.4-14
METHOD, 22.2-2, 22.3-17, 22.3-21, 22.3-24,
22.4-3, 22.4-4, 22.4-5, 22.4-6, 23.6-48, 23.6-49,
23.7-5, 23.9-8, 23.11-3, 25.9-7, 25.9-9
25.10-8, 27.13-9
27.13-15
Minor Alarm LED, 33.1-7
minor nodes, 16.2-3
MJU, 22.4-5, 22.4-6, 23.6-48, 23.6-49, 23.7-5
MJU antistreaming, 23.7-3
MJU_EC, 22.4-5, 22.4-6, 23.6-48, 23.6-49, 23.7-5
Mode LED, 33.1-7
MODEM, 23.12-3
module
view, 33.3-2
modules
blank tab removal, 13.38-1
ID, 16.5-5
type, 16.5-5
user-installable modules, 13.38-1
MORE, 22.3-28
MORE_DISPLAY, 35.3-5
MOS, 20.10-4
MPA card, 20.1-1
MPA card
A-bit, 20.20-9, 20.20-10
alarm declare and clear times, 5.5-7
ANS, 17.2-14
bandwidth, 20.20-1, 20.20-7, 20.20-8
card slot, 20.2-1
channels, 20.20-1, 20.20-4, 20.20-6, 20.20-7
clock inversion, 20.20-1, 20.20-15
clocking source, 20.20-4
connectors, 5.5-4, 5.5-5

NNP 95-2035-01-00-B
control signals, 5.5-6, 20.20-1, 20.20-12,

20.20-14
CPSS, 17.6-3, 17.6-20, 17.6-22, 20.20-4,
20.20-9
DCE/DTE, 20.20-1, 20.20-4
delay equalization, 20.20-4
DGM limit, 20.17-1
faceplate, 5.5-4
F-bit, 20.20-9, 20.20-11
framing, 20.6-1
HCM framing, 5.5-1, 20.20-1, 20.20-8,
20.20-9
interface type, 20.20-1, 20.20-3, 20.20-4
lead initiated loopbacks, 20.20-1, 20.20-12,
20.20-15
LEDs, 5.5-5
loopbacks, 5.5-6, 36.7-26
OOS conditioning, 20.20-1, 20.20-12,
20.20-15
overview, 5.5-1
pinout
RS-449/V.36 (DCE) backplane and
bulkhead, 14.10-47
RS-449/V.36 (DTE) backplane and
bulkhead, 14.10-49
RS-449/V.36 (DTE) faceplate, 14.10-50
RS-530-A (DCE) backplane and
bulkhead, 14.10-51
RS-530-A (DCE) faceplate, 14.10-52
RS-530-A (DTE) backplane and
bulkhead, 14.10-53
RS-530-A (DTE) faceplate, 14.10-54
V.35 (DCE) backplane and bulkhead,
14.10-55
V.35 (DCE) faceplate, 14.10-56
V.35 (DTE) backplane and bulkhead,
14.10-57
V.35 (DTE) faceplate, 14.10-58
X.21 (DCE) backplane and bulkhead,
14.10-59
X.21 (DCE) faceplate, 14.10-60
X.21 (DTE) backplane and bulkhead,
14.10-61
X.21 (DTE) faceplate, 14.10-62
reset, 36.11-1
RS-449/V.36 (DCE) faceplate, 14.10-48
Index
SES and DGM limits, 20.17-8

SES limit, 20.17-1
signalling channels, 20.20-1, 20.20-4,
20.20-7
signalling types, 20.12-1, 20.12-6
slip/doppler buffer, 20.20-1, 20.20-16
SRM, 20.20-1, 20.20-9, 20.20-11
supervisory channel, 5.5-1
trunk conditioning - custom, 20.11-1,
20.11-3
TS0, 20.20-9, 20.20-11
universal distribution panel, 3.10-7, 5.5-4
cadence, 6.9-2
diagnostics, 6.9-4
faceplate, 6.9-3
loopbacks, 6.9-4
overview, 6.9-1
pinout, 14.10-63
MTA connectors
GFC3, 4.8-15
MTR
connection and disconnection, 33.6-3
definition, 33.6-2
message deletion, 33.6-4
message type, 33.6-3
recording method, 33.6-3
MU_LAW, 23.4-4
MuLAW, 30.3-5
MuLaw, 21.2-2, 23.3-7, 23.5-4
MuLaw_INV, 29.3-6
MULTI-DROP, 23.7-3
multi-drop data bridges
ADI, 23.4-4
circuits, 23.7-2
DDS rate adaption, 23.7-2
PCM, 23.4-1
PCM antistreaming, 23.4-3
Multi-junction Unit, 23.7-3
MULTIPOINT, 29.3-5, 30.3-6
multiprotocol encapsulation, 8.5-1, 27.13-2
MX interface bus, 3.6-8
IN-33
Index
N
N1, 27.14-6
N2, 27.14-4
name
of signalling channel, 26.2-3
of user configuration, 26.3-2
negotiation facilities, 27.14-11
network layer
parameters, 27.14-7
sequence numbering, 27.14-8
status information, 33.11-22, 33.11-24,
33.11-26
timers, 27.14-10
network layer protocol timers, 26.2-6
network layer services, 17.6-5
Network Operations Center, 17.6-16
Network Termination Interface module, 5.3-13
network user address
definition, 27.1-2
Network User Address parameter, 27.15-3,
28.3-2
Network-wide hunt groups, 27.7-16
NEW_SET, 23.9-8
NEXT_SET, 23.9-2, 23.9-5
Nexus PASS, 27.9-1
NI_1, 30.3-4
NI_2, 30.3-4
NMTI, 16.2-1
No Date, 17.4-2
NO_4KPBS, 24.2-2
NO_8K, 22.3-29
NO_ACCESS, 17.5-2
NO_AIS, 22.3-29
NO_COMP, 23.6-49
NO_CONT, 22.4-6
NO_CONT_CK, 23.6-45, 23.6-48
NO_CONV, 18.2-6, 20.2-4
NO_CONV OC E3-, 20.3-2
NO_CRCREFR OC E18-, 20.18-10
NO_INVER, 29.3-6
NO_LEVEL_0, 17.5-7
NO_MODULE, 20.3-3
NO_PROTECT, 18.3-3
NO_RX_INV, 22.3-13
NOC_NUM, 17.6-16
node management sessions
active/inactive nodes, 16.2-3
IN-34

NNP 95-2035-01-00-B
ASCII (VT100) terminal, 16.2-5

CI, 16.2-4
command line, 16.3-4
connection to active Control card, 17.3-3
data area, 16.3-3
diagnostics line, 16.3-4
example, 16.3-9
executing, 16.3-7
function keys, 16.3-4
header line, 16.3-2
identifiers, 16.4-1, 32.2-1
keyboard entries, 16.3-8
logging off, 16.3-7
major nodes, 16.2-2
management stations, 16.2-4
minor nodes, 16.2-3
quitting, 16.3-7
screen layout, 16.3-2
softkey area, 16.3-4
softkeys, 16.3-4
display, 16.3-6
groups, 16.3-6
instructions, 16.3-6
menus, 16.3-5
Return softkey, 16.3-8
selection, 16.3-5
toggle, 16.3-6
status line, 16.3-4
undoing, 16.3-6
Node Management Terminal Interface, 16.2-1
node name, 17.4-3
node number, 17.6-15
NODE_CLASS, 17.2-23
NODE_NUM, 17.6-15
nodes
major, 16.2-2
minor, 16.2-3
NOMINAL, 21.7-3
NON_CONTIG, 20.15-4
NON_DIAL, 30.4-5
NON_ISDN, 29.3-4
NON_VERIFY, 30.4-5
NONE (flow control), 17.3-9
Non-Volatile Memory (see NVM), 33.3-26
NORM_POL, 21.3-9
NORM_POL signalling mode, 21.3-8
NORMAL, 17.3-10, 17.6-17, 17.6-19, 20.3-3
NOSIG, 20.12-5, 20.12-6, 20.12-8
NSF frame handling, 23.8-3
NSF_BLOCK/TRANSP, 23.8-3

NNP 95-2035-01-00-B
NSF_HANDLG, 23.8-3, 23.11-3

NSN, 27.15-1
NT, 22.3-33, 29.3-4
NT1, 29.1-1
NTI, 20.1-2
NTI Module, 5.3-13
NTN, 27.15-1
NTT, 30.3-4
NU bit, 20.18-2
NUI formats
description, 27.9-4
examples, 27.9-4
description, 27.9-6
NUI Subscription parameter, 27.15-15
NUI Validation parameter, 27.15-16
NUI validation servers, 27.9-1
NUM_B_CHAN, 30.3-4
NUM_CHANS, 30.4-6
NUM_CIRCS, 20.19-3, 29.3-7
NUM_FLAGS, 25.6-6
NUM_SIG, 20.19-4
number of B channels, 30.3-4
number of channels, 30.4-6
Number of Incoming SVCs parameter,
27.14-17, 28.2-12
Number of LCNs parameter, 27.14-15, 28.2-10
Number of Outgoing SVCs parameter,
27.14-16, 28.2-11
Number of PVCs parameter, 27.14-16, 28.2-10
number of retries, 30.4-5
NVM
view, 33.3-26, 33.3-28
nx56 kb/s call, 23.10-1
nx64 kb/s call, 23.10-1
O
OCU_DP, 22.2-4
OCU-DP Channel Unit
configuring, 22.1-8
diagnostics, 7.8-4
faceplate, 7.8-3
functions, 22.1-5
loopbacks, 7.8-5
overview, 7.8-1
pinout, 14.10-64
Index
OCU-DP channel unit
switched 56 kb/s operation, 22.3-31
ODD, 22.3-14
ON_FAULT, 20.14-6
ONE_WAY, 20.9-7
ONE_WAY/TWO_WAY, 20.16-4
ONE_WAY_TO, 20.15-7
ones density, 18.3-6
OnStandby, 17.4-2
OOF, 18.1-15
OOS_A, 20.10-4
OOS_B, 20.10-4
OOS_C, 20.10-4
operational status, 26.2-3, 26.3-3
Optical Extension card, 20.1-1, 20.1-2
connections, 5.7-2
faceplate features, 5.7-4
framing, 20.6-1
functions, 5.7-2
ground, 20.18-4
loopbacks, 36.7-26
modules, 5.7-4
options, 20.18-1
overview, 5.7-1
SES, 20.18-5
Optical Extension card.pinout, 14.10-1
Optical Extension cards, 33.1-14
NUbit, 20.18-2
Optional User Defined Data Length parameter,
27.10-21
order wire, 4.8-7
Order Wire connectors
originator of PVC, 27.17-12
Outgoing Fast Select Allowed parameter,
28.3-6
Outgoing Restricted Fast Select Allowed
parameter, 27.15-12
Outgoing Unrestricted Fast Select Allowed
parameter, 27.15-12
out-of-service type A, 20.10-4
IN-35
Index
out-of-service type B, 20.10-4

out-of-service type C, 20.10-4
output gain, 23.5-4
P
PACKET, 24.2-2, 25.2-1, 30.2-1
Packet card
loopbacks, 36.7-24
Packet Engine card
definition, 27.1-3
Packet Layer Call Timer (T31) parameter,
28.2-13
Packet Layer Call Timer parameter, 27.14-18
Packet Layer Interface Type parameter,
27.14-14
Packet Layer Restart Timer (T30) parameter,
28.2-12
Packet Layer Restart Timer parameter, 27.14-18
packet segmenting and combining, 27.2-10
Packet Sequence Numbering parameter,
27.14-15, 28.2-9
packet size
25.10-8, 27.13-9
defaults, 27.15-27
parameter descriptions
Accounting Activation, 27.15-4, 28.3-3
Accounting NVM Buffer Size, 27.10-22
Accounting Segment Size, 27.10-19
ACT, 27.13-11
address translation and screening, 27.14-37
Aggregate Committed Burst Size, 27.6-21
Aggregate Committed Information Rate,
27.6-21
Alias, 27.6-20
Allocated XAC Number, 27.15-3, 28.3-2
Allowable Packet Sizes, 27.14-23, 28.2-16
Base LCN, 27.14-15, 28.2-10
Bc, 27.13-22
Be, 27.13-22
Call Deflection, 27.15-15
Charging Information Request Allowed,
27.15-11
Charging Information Subscription,
27.15-11
CIR, 27.13-22
Clear On Calling Address Failure, 28.3-8
Clear Timer, 27.14-18
Clear Timer (T33), 28.2-13
closed user group, 27.15-22
Collection Interval, 27.10-20
IN-36

NNP 95-2035-01-00-B
Congestion Timer, 27.14-6, 28.2-5

Cost, 27.8-3
Default NPI, 27.14-22, 28.2-16
Default NUA, 27.15-13
Default NUI Format, 27.15-16
Default Receive Packet Size, 28.3-6
Default Receive Throughput Class, 28.3-5
Default Receive Window Size, 28.3-4
Default Send Packet Size, 28.3-6
Default Send Throughput Class, 28.3-5
Default Send Window Size, 28.3-5
Delta Value, 27.6-20
Diagnostic Code Mapping, 28.2-17
Encapsulated Protocol Maximum Frame
Size, 27.13-11
Encapsulated protocol maximum frame
size, 25.10-9
Encapsulation type, 25.10-9, 27.13-11
Enhanced Diagnostic Codes, 27.14-25
Event Monitored XAC Status, 28.2-18
External Translation Prefix, 28.2-23
flow control defaults, 27.15-27
Flow Control Negotiation, 27.14-23
Flow Control Timer, 28.2-15
Frame Response Timer, 27.14-4
Frame Response Timer (T1), 28.2-4
Frame Sequence Numbering, 27.14-4,
28.2-3
Gateway TNIC/CNIC, 28.2-18
Generate Accounting Records, 27.10-18
Generate Accounting Records on
Unsuccessful Calls, 27.10-18
Generate Alarms, 28.2-18
Generate Cause Codes in DTE Format,
27.14-24
GFR Address, 27.6-17
Hot Billing, 27.15-5
Inactivity Timer, 28.2-4, 28.2-14
Inactivity Timer (link layer), 27.14-5
Inactivity Timer (network layer), 27.14-19
Incoming Fast Select Acceptance, 27.15-12
Incoming Maximum Address Length
Allowed, 27.14-20, 28.2-15
Incoming Transit Calls Allowed, 28.2-17
Insert TNIC, 28.2-19
Intermediate Record Interval, 27.10-20
Internal Translation Prefix, 28.2-23
LAPB Address Assignment, 28.2-2
link layer, 27.14-2
Link Layer Interface Type, 27.14-3
Load Balancing, 27.6-19
Local Address Validation, 27.14-22

NNP 95-2035-01-00-B
Local Charge Prevention, 27.15-11

Maximum Allowed Validation Period,
27.9-11
Maximum Frame Window Size, 27.14-4,
28.2-3
Maximum Information Frame Size,
27.14-6, 28.2-5
Maximum Time Between Transfers,
27.11-7
MCT, 27.13-11
N1, 28.2-5
network layer, 27.14-7
Network User Address, 27.15-3, 28.3-2
NUA subscription options, 27.15-10
NUI Subscription, 27.15-15
NUI Validation Required, 27.15-16
Number of Incoming SVCs, 27.14-17,
28.2-12
Number of LCNs, 27.14-15, 28.2-10
Number of Outgoing SVCs, 27.14-16,
28.2-11
Number of PVCs, 27.14-16, 28.2-10
Optional User Defined Data Length,
27.10-21
Outgoing Restricted Fast Select Allowed,
27.15-12
Outgoing Unrestricted Fast Select
Allowed, 27.15-12
Packet Layer Call Timer, 27.14-18
Packet Layer Call Timer (T31), 28.2-13
Packet Layer Interface Type, 27.14-14
Packet Layer Restart Timer, 27.14-18
Packet Layer Restart Timer (T30), 28.2-12
Packet Sequence Numbering, 27.14-15,
28.2-9
Periodic Accounting Activation, 27.15-5,
28.3-8
Periodic Record Interval, 27.10-21
Poll Timer, 27.8-4
Primary Data Collector Address, 27.11-5
Primary NUI Server Address, 27.9-10
Rate Enforcement State, 27.6-21
Redirection Address, 27.15-14
Redundant Routing, 27.6-18
Reset Timer, 27.14-18
Reset Timer (T32), 28.2-13
Response Delay Timer, 27.14-5, 28.2-4
Retransmission Count, 27.14-4
Index
Retransmission Count (N2), 28.2-3

Reverse Charge Acceptance, 27.15-10,
28.3-4
SCT, 27.13-11
Secondary Data Collector Address, 27.11-6
Secondary NUI Server Address, 27.9-10
Service Type, 27.14-14, 28.2-8
Signal CLAMN, 27.15-15, 28.3-3
Signal CNIC, 28.2-19
Signal CRN, 27.15-14, 28.3-4
Signal TNIC, 28.2-19
Suppress Called Address, 27.14-21
Suppress Calling Address, 27.14-21
throughput class defaults, 27.15-27
Throughput Class Negotiation, 27.14-24
Throughput Class Negotiation Format,
27.14-24, 28.2-17
Time Zone, 27.10-22
TOA/NPI Address Format, 27.15-13,
28.3-7
Transfer Block Retransmission Count,
27.11-7
Transfer Block Size, 27.11-6
Translate Called Address, 28.2-24
Translate Calling Address, 28.2-24
Translate Incoming Packets, 28.2-24
Translate Outgoing Packets, 28.2-25
Trap Action - Clear Call, 28.2-26
Trap Incoming Called, 28.2-25
Trap Incoming Calling, 28.2-25
Trap Outgoing Called, 28.2-26
Trap Outgoing Calling, 28.2-26
Two-way SVCs, 27.14-17
User Defined Data, 27.15-4
Version, 28.2-9
Window Timer, 27.14-19, 27.14-20, 28.2-14
X.25 Version, 27.14-14
X.75 LCN Selection, 28.2-9
PARITY, 22.3-14
parity, 22.3-13
PARTITION, 18.1-10
partitioned standby, 5.2-6
passwords, 17.5-1, 17.5-8
configuring, 17.5-1
PATH_COST, 17.6-19
PCM encoding, 30.3-5
PCM_ENCODE, 30.3-5
pe, 20.20-3
IN-37
Index
PE card
card reset, 8.6-4
faceplate, 8.6-3
LEDs, 8.6-3
loopbacks, 8.6-4
pinout, 14.10-42
performance monitoring, 22.3-36
Periodic Accounting Activation parameter,
27.15-5, 28.3-8
Periodic Record Interval parameter, 27.10-21
Peripheral shelf
23-Inch
Mod 1), 14.14-12
Mod 2), 14.14-13
J14, 14.8-1
Power Supply card, 13.22-1
Class A
13.26-1
dc distribution box connections Class
A dc distribution box connections,
13.26-1
dc terminal block/cable harness,
13.30-1
Mod 1), 14.14-10
J14, 14.8-1
J17, 14.8-1
IN-38

NNP 95-2035-01-00-B
power supply, 40.5-1

Class B
cable clamp, 13.31-2, 13.32-1
13.31-2, 13.32-1
13.32-1
13.32-1
Mod 1), 14.14-12
Mod 2), 14.14-13
J14, 14.8-1
Permanent Virtual Circuits, 8.5-2, 25.1-3
permanent virtual circuits, 27.17-1
PHY, 25.4-1
physical access, 26.3-3
physical requirements, 26.1-2
ping
definition, 33.6-8
error messages, 33.6-9
initiating, 33.6-9
pinout illustrations, 14.10-6
PLAR, 20.12-3, 20.12-5, 20.12-8, 21.3-7
PLAR_D3, 20.12-3, 20.12-5, 20.12-8, 21.3-7
PLR, 21.3-4
PLR signalling mode, 21.3-1
PM_ON/OFF, 22.3-36
Poll Timer parameter, 27.8-4
Port A LED, 33.1-7

NNP 95-2035-01-00-B
Port B LED, 33.1-7

POSITION, 22.4-5, 22.4-6, 23.6-43, 23.6-48,
23.6-49, 25.9-7, 25.9-10
power dissipation, 10.2-7
power feeds, 13.29-1
Power LED, 33.1-7
power monitoring alarms, 35.6-4
power rail test points, 4.8-15
power rails, 3.6-8, 3.6-14, 3.6-19, 3.6-21
power supplies, 3.7-1
ac, 3.7-6
dc, 3.7-8
input specifications, 3.7-6, 3.7-8
LEDs, 3.7-10
power cables, 3.7-8, 3.7-10
power cards, 3.7-2
power shelf, 3.7-1
upgrade kits, 3.7-7
variants, 3.7-7
Power Supply card
23-Inch Shelves
illustr., 13.22-1
Power Supply cards
in 23-inch shelf, 40.4-1
in HSPS2, 40.4-2
Power supply replacement, 40.5-1
Power-up
diagnostic tests, 33.2-1
forced diagnostics, 33.2-19
LED activity, 33.1-10
Preferential CUG parameter, 27.15-23
PREFERRED, 18.2-6, 20.15-4
preferred connection, 18.2-1
PREFERRED OC K3-, 29.3-7
prefix
passing or striping, 26.2-4
PREV_SET, 23.9-2, 23.9-5
PRI cards
configuring, 20.1-6
framing, 20.6-1
inversion, 20.13-1
loopback detection, 20.14-1
loopbacks, 36.7-26
overview, 20.1-1
signalling, 20.12-1
super-rate circuits, 20.15-1, 31.10-1
Index
one-way, 20.9-2, 31.12-2

two-way, 20.9-5, 31.12-4
PRI redundancy, 18.3-1
active and standby cards, 18.3-1
card failures, 18.3-8
configuring, 18.3-2
fault processing, 18.3-7
handling failures, 18.3-3
hardware requirements, 18.3-1
kits, 18.3-2
master and slave designations, 18.3-3
operating rules, 18.3-1, 18.3-4
Primary Data Collector Address parameter,
27.11-5
Primary NUI Server Address parameter,
27.9-10
Primary Rate Interface cards, 3.14-2
Primary rate link
bypass, 38.2-1, 38.2-4
clear time, 35.4-1
Primary rate loopbacks, 36.7-26, 36.7-45
primary route, 26.5-2
PRINT CONTENTS, 34.1-34, 34.1-41
PRINTER, 17.3-7
PROCEED, 16.3-7
Processor LED, 33.1-7
profile name, 26.2-5
PROT_BY, 18.2-6, 18.3-3, 20.15-7
PROT_SWTCH, 18.1-15
PROTECTING, 18.2-6, 20.15-7
protecting connections, 18.2-1
24 DS-0 super-rate, 20.16-1
AQA, 18.2-5
automatic override, 18.2-3
circular protection, 18.2-4
compatibility, 18.2-4
for different cards, 18.2-4
for super-rate circuits, 18.2-4
pointers, 18.2-3
super-rate circuits, 20.15-4, 31.10-3
PROTECTION, 18.2-6
protection switching, 18.1-15, 18.2-1
24 DS-0 fault recovery, 20.16-3
configuring, 18.2-3
RAP+ID, 20.16-2
protection switching commands
forced switch, 31.4-12
lockout, 31.4-12
manual switch, 31.4-13
IN-39
Index
PROTOCOL, 25.6-6
Protocol
CPSS, 1.2-1
protocol
27.13-16
X.25 version, 27.14-14
provisioning
backbone trunks, 27.8-6
user access
direct, 27.19-1
encapsulated, 27.19-3
subrate encapsulated, 27.19-6
PT_TO_PT, 30.3-6
PUB 43801, 20.12-3
Pushbutton S1, 4.2-5, 4.5-7, 4.6-5, 5.2-5
Pushbutton S1 TO E1-, 5.1-7
Pushbuttons
PVC, 25.1-3
PVC identifiers, 16.4-1
PVCs
FRE card, 8.4-3
FRS card, 8.5-2
Q
Q.2110, 27.2-3
Q.922 link layer, 26.2-7
Quality statistics, 34.1-3
clear statistics, 34.1-10
DE1-2 card, 34.1-36
display, 34.1-9
DT1-2 card, 34.1-31
MPA card, 5.5-7
print-out options, 34.1-34, 34.1-41
reset error events, 34.1-10
TTC2M card, 5.6-7
type (E1 only), 34.1-9
X.21/V.35 PRI cards, 5.4-6
QUIT, 16.3-7
R
R2 digital signalling, 20.12-4, 31.15-3
R2D_E+M, 20.12-8
rack mounting brackets
48 cm (19 in) rack, 3.5-8
58 cm (23 in) rack, 3.5-8
TEP-1(E) or 11B rack, 3.5-8
racks
48 cm (19 in), 3.5-8
58 cm (23 in), 3.5-8
IN-40

NNP 95-2035-01-00-B
dimensions, 3.5-9
TEP-1(E) or 11B, 3.5-8, 3.5-9
RAP+ID, 29.4-1
RAP+ID protection switching, 20.16-2
rate adaption
configuring, 22.4-3
DCCs, 22.4-1
DDS, 23.6-4, 25.9-7, 25.9-10
DDS Access, 23.6-5
DDS Core, 23.6-6
enhanced transparent, 23.6-2
HCM, 23.6-3, 25.9-7, 25.9-9
HCV voice compression for DSP cards and
IMC, 23.3-4
Line cards, 22.4-1
subrate FRS circuits, 25.9-6
subrate FRS streams, 25.9-8
transparent, 23.6-1
types
DSP cards, 23.6-1
X.50, 23.6-11
X.50 Basic, 23.6-15
X.50 Telco, 23.6-15
Rate Enforcement State parameter, 27.6-21
RATE_AD/56, 30.4-4
RATE_ADAPT, 22.3-17, 22.3-21, 22.3-24,
23.6-49, 23.7-5, 23.11-3, 25.9-9, 25.9-10
RBS, 20.12-4, 20.12-5, 20.16-4, 31.15-3
RDL, 20.20-12, 22.3-7
READ/WRITE, 17.5-2
READ_ONLY, 17.5-2
Ready LED, 33.1-8
Rec. Att. LED, 33.1-8
Receive Attention pushbutton, 4.8-15
Recommendation X.2
compliance to, 27.3-1
Recommendation X.35
compliance to, 27.3-5
Reconcile in Progress, 18.1-14
RECOVERY, 17.2-24
Red Alarm LED, 33.1-8
RED_OFF/ON, 20.9-10
Redirection Address parameter, 27.15-14
redirection addresses
hunt group, 27.18-2
NUA, 27.15-14
redundancy, 2.1-12
access, 5.1-10
DS-3 card, 5.1-9
DS-3 II card, 5.1-9
E3 card, 5.2-6
hot standby, 5.2-6

NNP 95-2035-01-00-B
interface, 5.1-10
partitioned standby, 5.2-6
primary rate interface, 18.3-1
single-shelf, 18.1-5
redundancy jumpers
23-Inch locally controlled shelf, 13.11-1
23-Inch peripheral shelf, 13.11-1
23-Inch switching shelf, 13.11-1
Class A locally controlled shelf, 13.11-1
Class A peripheral shelf, 13.11-1
Class A switching shelf, 13.11-1
Class B locally controlled shelf, 13.11-1
Class B peripheral shelf, 13.11-1
Class B switching shelf, 13.11-1
REDUNDANT, 18.1-5, 22.3-25, 22.3-28
Redundant Routing parameter, 27.6-18
refreshing the display, 16.3-4
relative address, 26.3-1
Reliable Transfer Protocol
description, 27.2-3
Reliable Transfer Protocol (RTP)
statistics, 34.5-7
REM_EXT, 20.12-8, 21.3-7
remote address table
creating and changing, 26.5-4
error and caution messages, 26.5-3
parameters, 26.5-2
remote alarm indication, 35.5-1
REMOTE_NUM, 30.4-2, 30.4-5
REPORT_ON/OFF, 30.3-5
reset cause codes, 37.1-2
Reset Timer (T32) parameter, 28.2-13
Reset Timer parameter, 27.14-18
Response Delay Timer (T2) parameter, 28.2-4
Response Delay Timer parameter, 27.14-5
RET_SERV, 18.3-9
Retransmission Count (N2) parameter, 28.2-3
Retransmission Count parameter, 27.14-4
RETRIES, 30.4-5
Return softkey, 16.3-8
REV_POL, 21.3-9
REV_POL signalling mode, 21.3-8
Reverse Charge Acceptance parameter,
27.15-10, 28.3-4
RFC 1490 encapsulation, 25.10-3, 27.13-3
RI, 20.20-12, 22.3-7
ring terminal, 13.1-2
ringing generator
external
ringing generator alarm reporting, 35.6-3
Index
ringing generators
connections, 3.8-3, 3.8-8
external, 3.8-6, 40.7-1
external configurations, 3.8-7
internal, 3.8-2, 40.6-1
distribution box connections, 13.20-2,
13.20-3, 13.21-2
J2, 3.8-3, 3.8-8
J24F, 3.8-3, 3.8-5
J24R, 3.8-8, 3.8-10
J30, 3.8-8, 3.8-11
Newbridge, 3.8-1
non-Newbridge, 3.8-1
redundancy, 3.8-7
ringing voltage, 3.8-1
variants, 3.8-3, 3.8-7
Ringing LED, 33.1-8
RL, 20.20-12, 22.3-7
RL_ENABLE/DISABLE, 22.3-5
RLS_CTRL, 18.1-14
robbed bit signalling, 20.12-4, 31.15-3
route failure handling, 26.5-4
route list name, 26.5-2
route trace
characteristics, 33.6-4
error messages, 33.6-6
indication types, 33.6-5
LLCP, 33.6-6
setting LLCP, 33.6-8
starting, 33.6-8
router version, 17.6-4, 17.6-17
routing
definition, 26.1-4
in large network, 26.1-4
overview, 26.5-1
remote address table, 26.5-2
selection, 26.5-4
routing domains, 27.6-1
routing system characteristics, 27.6-12
RPT_TYPE, 25.4-9, 25.6-10
RS-232 DCC, 22.1-1
RS-232 Direct Connect card, 22.1-1
backplane or bulkhead
, 14.10-67
pinout
backplane or bulkhead, 14.10-65
faceplate, 14.10-66, 14.10-68
RS-232_DCC, 22.2-1
RS-422 DCC, 22.1-1
clocking, 10.5-7, 22.3-10
DCE external (Slip Buffer present), 10.5-8
IN-41
Index
DTE slave (Slip Buffer present), 10.5-10

inversion, 22.3-14
Slip Buffer Module depth, 22.3-15
Special DCE external (no Slip Buffer),
10.5-11
RS-422 Direct Connect card, 22.1-1
faceplate pinout
IN 1505-, 14.10-70
pinout
RS-499/V.36 backplane or bulkhead,
14.10-69
RS-499/V.36 faceplate, 14.10-72
RS-499/V6 backplane or bulkhead,
14.10-71
RS-530-A backplane or bulkhead,
14.10-73, 14.10-75
RS-530-A faceplate, 14.10-74, 14.10-76
V.35 backplane or bulkhead, 14.10-77,
14.10-79
V.35 faceplate, 14.10-78, 14.10-80
X.21 backplane or bulkhead, 14.10-81,
14.10-83
X.21 faceplate, 14.10-82, 14.10-84
RS-422_DCC, 22.2-1
RS-499/V.36, 22.3-1
RS-530, 22.3-1
RTP virtual connections, 27.2-4
RTS, 20.20-12, 22.3-7
RTS/CTS, 22.3-4
RX_INV, 22.3-13
RX_TLP, 21.5-7
S
S/T interface K1-, 29.1-1
S1 pushbutton, 4.8-15
SA4 BER, 20.18-6
SAI LED, 33.1-8
SAM, 5.3-9, 20.1-2, 20.2-4, 20.3-2
SATELLITE, 17.6-19
satellite delay, 20.20-16
SC, 19.3-4
SC_ON/OFF, 22.3-31
SCT, 25.4-7
SE3 card, 20.1-1
alarm LED numeric value, 39.2-6
LEDs, 14.2-1
loopbacks, 36.7-26
power-up LED activity, 14.2-1, 33.1-14
IN-42

NNP 95-2035-01-00-B
SEAL_CUR, 22.3-32
sealing current, 22.3-32
Secondary Data Collector Address parameter,
27.11-6
Secondary NUI Server Address parameter,
27.9-10
segmenting packets, 27.2-10
SEIZED, 20.10-4, 21.8-1
SELECT, 17.2-23
sequence numbering, 27.14-8
serial bus, 3.6-7, 3.6-13
backplane, 3.6-21
baud rate, 17.3-8
card faceplate serial ports, 16.2-7
configuring, 17.3-4
Control card, 17.3-2, 17.3-3
CPC, 8.1-4
CPCs, 17.3-4
CPSS cost, 17.3-10
DCP card, 8.2-3, 17.3-4
default configuration, 16.2-8
device type, 17.3-6
for 4600, 17.6-33
FRE card, 8.4-7, 17.3-4
FRS card, 8.5-7, 17.3-4
PE card, 17.3-4
pinouts, 16.2-8
SP1, 16.2-6
SP2, 16.2-6
Serial Telecom bus, 3.6-7, 3.6-13
Service Type parameter, 27.14-14, 28.2-8
SES, 20.17-1, 20.18-5
SESSN_TIME, 16.3-11
SETUP message, 30.4-2, 30.4-5
25.10-8, 27.13-9
27.13-15
severely errorred seconds, 20.18-5
SHARE_COST, 17.6-17
SHARED, 30.2-1
shared cost, 17.6-5, 17.6-17
shelf
description, 1.3-1
FCC compliance, 1.3-4
identifiers, 16.4-1, 16.4-5
numbers, 16.4-6

NNP 95-2035-01-00-B
requirements for large multiplexers, 1.3-2

types, 1.3-1
variants, 1.3-4
shelf frame, 3.5-1
Shelf-select jumper, 32.2-6
shelf-select jumper, 3.6-8, 3.6-15, 16.4-5
shelves
HSPS, 3.3-1
equipment interface area, 3.3-2
interface section, 3.3-2
power section, 3.3-2
visual alarm indicators, 3.3-4
HSPS2, 3.3-3
interface section, 3.3-3
locally controlled/peripheral shelf, 3.2-1,
3.2-4, 3.2-6
common control section, 3.2-2, 3.2-4,
3.4-2
equipment interface area, 3.2-3, 3.2-5,
3.4-4
interface section, 3.2-3, 3.2-5, 3.4-3
power section, 3.2-3, 3.2-5, 3.2-6, 3.4-4
visual alarm indicators, 3.2-7, 3.4-4
switching shelf
Class A, 3.1-1
common control section, 3.1-2
power section, 3.1-2, 3.1-4
Switching section, 3.1-2
Telco, 3.1-4
shield ground, 10.8-1
SHORT, 20.7-2, 21.7-1, 21.7-2
SHORT_BUF, 20.19-8
SHORT_BUS, 29.3-5
SHOW NTWK/SHOW CUST, 34.1-30
SHOW_A, 16.5-4
SHOW_ALL, 25.6-3
SHOW_CCT, 16.5-6
SHOW_CONNS, 25.7-3, 25.7-4
SHOW_STNS, 25.4-3
SHOW_UNITS, 16.5-6
SI Alarm LED, 33.1-8
SI Loss LED, 33.1-8
sidetone gain, 23.5-4
SIG, 20.12-5, 20.12-8
SIG_MODE, 20.5-2, 20.16-4
SIG_ON, 22.3-17
Index
SIG_ON/OFF, 22.3-16, 22.4-4, 22.4-5, 23.6-49,

25.9-9
SIG_TYPE, 20.12-5, 20.12-8
SIG24, 20.5-2
Signal CLAMN parameter, 27.15-15, 28.3-3
Signal CNIC parameter, 28.2-19
Signal CRN parameter, 27.15-14, 28.3-4
signal ground, 10.8-1, 20.18-4
signal propagation, 22.3-16
Signal TNIC parameter, 28.2-19
signalling
4WDX Channel Unit, 21.3-7, 21.3-8
E&M cards, 21.3-1
LGE/LGS cards, 21.3-4
TTC2M cards, 20.12-8
Signalling bits, 36.2-1
signalling channel
administrative status, 26.2-3
associated signalling profile, 26.2-3
connecting, 26.2-1
disconnecting, 26.2-2
management, 26.1-3
MPA card, 20.20-4
name, 26.2-3
operational status, 26.2-3
statistics, 34.4-1
switch prefix, 26.2-4
Signalling leads, 36.2-1
availability, 36.2-1
Line cards, 7.4-4
signalling leads
changing outgoing leads, 36.2-5
DS-3 card, 5.1-10
E&M card, 6.2-5
E1 card, 5.3-19
E3 card, 5.2-7
T1 card, 5.3-19
TTC2M card, 5.6-7
viewing incoming and outgoing status,
36.2-2
X.21/V.35 PRI cards, 5.4-6
signalling modes
E&M, 21.3-1
FIXED_BIAS, 21.3-8
NORM_POL, 21.3-8
PLR, 21.3-1
IN-43
Index
REV_POL, 21.3-8
SW_BIAS, 21.3-8
TO, 21.3-1
signalling profile
definition, 26.2-5
signalling protocol, 26.2-5
signalling states
LGE card, 6.3-5
LGS card, 6.4-5
signalling types
clear channels, 20.12-6
compatibility, 20.12-2
DS-3 card, 20.12-5
HCV signalling for DSP3, DSP4 and
DSP5H cards, 23.3-2
PLAR D3 signalling, 20.12-3
PRI cards, 20.12-1
R2 digital signalling, 20.12-4, 31.15-3
RBS, 20.12-4, 31.15-3
T1 card, 20.12-5
SIMPLEX, 18.1-5
Singing, 21.9-1
single and double bandwidth, 2.1-7
Single E3 card, 20.1-1
Single Optical Extension card, 5.7-1, 20.1-1,
20.1-2
Single Optical Extension card pinout, 14.10-1
Single shelf redundancy, 40.3-1
dual shelf to single shelf redundancy,
40.3-6
simplex to single shelf redundancy, 40.3-2
single shelf to dual shelf redundancy,
40.3-9
site planning
commissioning, 10.1-2
overview, 10.1-1
site requirements, 10.1-1
system requirements, 10.1-1
site requirements, 10.2-1, 12.1-1
ac power source fluctuations, 10.2-2
altitude, 10.2-1
anti-static strap, 10.2-2
cooling, 10.2-3
Electrostatic Discharge, 10.2-2
grounds, 10.2-2
location, 10.2-1
power, 10.2-2
IN-44

NNP 95-2035-01-00-B
temperature and humidity, 10.2-1

working space, 10.2-2
SLAVE, 22.3-12, 22.3-28, 23.7-3
slip buffer, 20.19-8
MPA card, 20.20-1, 20.20-16
Slip Buffer Module depth, 22.3-15
SLIP_BUFF, 22.3-15
slot, 16.5-1
status, 33.3-1
slot configuration
2B1Q channel unit, 22.2-4
4WT0 channel unit, 22.2-4
BRI S/T card, 29.2-1
CPC card, 30.2-1
DCCs, 22.2-1
DCP card, 24.2-1
DSP cards, 23.2-1
FIC card, 20.2-5
IMC, 23.2-1
line cards, 22.2-2
OCU-DP channel unit, 22.2-4
PRI cards, 20.2-1
system cards, 19.3-1
voice interface channel units, 21.2-1
slot identifiers, 16.4-1
slot numbers (n), 16.4-7
HSPS, 16.4-10, 16.4-11
slot status, 16.5-5
SNGL_SHELF, 18.1-5
software downgrading, 40.2-1
limitations, 40.2-13
Software downloading
dual shelf redundant node, 40.2-25
memory bank, 40.2-13
single shelf redundant nodes, 40.2-25
software downloader, 40.2-23
Control card, 4.6-7
Control card, 4.5-9
CPC, 8.1-4
DS-3 card, 5.1-11
E3 card, 5.2-8
FRE card, 8.4-8
FRS card, 8.5-8
limitations, 40.2-13
PE card, 8.6-5
upgradable cards, 40.2-2

NNP 95-2035-01-00-B
SOURCE, 25.8-3
source, 17.2-23
SPACE, 22.3-7, 22.3-14
SPECIAL, 22.3-12
Special mode, 10.5-11
DCCs
to set, 10.5-11
Specifications
Line cards, 7.4-5
specifications
Balanced Transceiver card, 4.1-4
BRI S/T card, 7.2-6
Clock card, 4.2-6
Control card, 4.6-7
Control card, 4.5-9
CPC, 8.1-4
DCCs, 7.3-6
DCP card, 8.2-4
DS-3 card, 5.1-11
DS-O DP Channel Unit, 7.7-4
DSP cards and IMC, 8.3-5
E&M card, 6.2-5
E1 card, 5.3-21
E3 card, 5.2-8
FRE card, 8.4-8
FRS card, 8.5-8
LGE card, 6.3-6
LGS card, 6.4-6
MPA card, 5.5-7
PE card, 8.6-5
physical
T1 card, 5.3-21
Test card, 4.11-8
Timing card, 4.3-5
transmission
Index
TTC2M card, 5.6-8

X.21 ESI PRI card, 5.4-7
X.21 PRI card, 5.4-7
SPEECH, 30.4-4
SPEED, 17.6-19
SPEED_RANG, 25.9-5
SPID, 30.3-6
Split access metallic connection, 36.3-7
split/monitor connections, 5.3-21
SRC_N_CIRC, 20.15-4
SRIM, 25.2-1, 25.9-1
SRM, 22.2-1, 23.5-4, 23.6-47, 23.7-5
SRMs, 22.4-1
aggregate channels, 23.6-16
branch channels, 23.6-16, 23.6-26
cards supporting DDS SRMs, 23.6-22
cards supporting HCM SRMs, 23.6-22
cards supporting transparent SRMs,
23.6-22
cards supporting X.50 SRMs, 23.6-22
configuring, 22.4-3
DCCs, 23.6-24
DDS, 23.6-19
DSP cards, 23.6-25
HCM, 23.6-17
line cards, 23.6-24
MPA card, 20.20-1, 20.20-11
rate adaption method, 23.6-47
transparent, 23.6-16
SRS, 23.9-5
connecting circuits, 23.9-9
display, 23.9-2
DS-0 port configuration, 23.9-9
set identifiers, 23.9-4
SSRA card, 18.1-5
SSU Module, 2.1-11, 4.5-5
SSU/ISSU, 17.2-1
SSU_RECOV, 17.2-17
ST bus, 3.6-7, 3.6-13
stand-alone synchronization, 2.1-11, 17.2-5
standards compliance, 27.3-1
standby card, 18.3-1, 18.3-4
standby mode
partitioned, 18.1-9
standby modes, 18.1-8
hot standby, 18.1-8
START_DLCI, 25.7-4
station protocol statistics, 34.3-7
STATION_ID, 25.4-7
statistical counters
IN-45
Index
types, 34.4-1
viewing and resetting, 34.4-4
statistics
ATB, 34.5-3
automatically clear, 34.1-26
BERT statistics, 36.5-13
FASTbus protocol, 34.3-7, 34.3-21
frame relay and X.25, 34.2-1
accumulation periods, 34.2-3
manually clear, 34.2-2
refresh automatically, 34.2-1
FRE card, 34.2-1
FRE cards, 34.3-11
switch
FRS card, 34.2-1
GFR, 34.5-4
HSA card quality statistics, 34.1-10
internodal traffic, 34.5-7
link layer
detailed, 34.5-16
summary, 34.5-15
network layer
invalid packets, 34.5-23
PE card, 34.2-1
protocol, 34.3-7
remote switch, 34.5-7
RTP, 34.5-7
switch level, 34.5-1
synchronization statistics, 34.1-25
usage statistics, 34.1-1
XFR, 34.5-25
statistics on signalling channel, 34.4-1
STATS AUTO_CLEAR, 34.1-27
status information
direct circuits, 33.11-15
RTP, 33.11-12
switch, 33.11-1
trunk circuits, 33.11-9
virtual circuit, 33.11-26
XAC link layer, 33.11-20
XAC network layer, 33.11-22, 33.11-24
XACs, 33.11-16
Status LED, 33.1-8
status message rate, 25.6-8
STATUS_RATE, 25.6-8
stHCV, 23.11-3
forcing super tandem, 23.11-2
stHCV and fax operation
IN-46

NNP 95-2035-01-00-B
understanding, 23.11-1
stHCV_EN/DIS, 23.11-2
STM-1 card
loopbacks, 36.7-51
stop bits, 22.3-13
STOP_BITS, 22.3-14
STREAM, 25.5-3, 25.6-3, 25.7-3
stream, 25.5-1, 25.6-1
stream identifiers, 16.4-1
stream protocol statistics, 34.3-7
STREAM_ON/OFF, 23.4-4
STRM_TIMER, 23.4-4
SUB_ADDR, 30.4-2, 30.4-5
subaddressing, 27.14-11
subrate access, 27.13-7
subrate CPSS channels, 17.6-27
subrate multiplexing, 25.9-1
CPSS, 23.9-7
DDS, 23.9-7
X.50, 23.9-7
subrate switching, 23.9-1
subscription options, 27.15-7
summary display, 16.5-2
SUPER_RATE, 22.2-1
super-rate access, 27.13-1
Super-rate Adapter Module, 5.3-9, 20.3-2
24 DS-0 fault recovery, 20.16-3
circuit order, 20.3-2
contiguous, 20.3-2
contiugous, 20.15-2, 31.10-1
DCCs, 22.3-17
clocking, 22.3-21
delay equalization, 20.15-4
equidistant, 20.15-3, 31.10-2
Line cards, 22.3-22
non-contiugous, 20.15-2, 31.10-2
protecting, 20.15-4, 31.10-3
timeslot order, 20.3-2
unidirectional broadcast circuits, 20.15-8
unidirectional tandem, 20.15-7
supervisory channel, 5.5-1, 20.19-4, 20.20-1,
20.20-9
Suppress Called Address parameter, 27.14-21
Suppress Calling Address parameter, 27.14-21
SVC call display, 33.6-1

NNP 95-2035-01-00-B
SVC calls
clearing and viewing, 33.6-2
SVC routing
see routing, 26.5-1
SVCs
signalling channel management, 26.2-1
SW_BIAS, 21.3-9
SW_BIAS signalling mode, 21.3-8
SW56_ON/OFF, 22.3-31
switch prefix
address, 26.3-1
passing or stripping, 26.2-4
setting, 26.2-5
types, 26.3-2
Switched 56
access to frame relay, 25.11-1
switched 56 kb/s operation, 22.3-31
switched access
to frame relay, 25.11-1
switched virtual circuit, 27.14-8
Switching card
diagnostics, 4.9-4
disable, 39.1-12
enable, 39.1-12
faceplate, 4.9-2
LEDs, 4.9-3
overview, 4.9-1
switching interface cables
Class A
non redundant Switching to
Peripheral, 13.16-2
HSPS2
13.17-12
redundant Switching to HSPS2,
13.17-12
diagnostics, 4.10-5
faceplate, 4.10-3
LEDs, 4.10-4
modules, 4.10-3
overview, 4.10-1
Switching shelf
23-Inch
Index

Mod 1), 14.14-8
Mod 2), 14.14-9
J14, 14.8-1
Power Supply card, 13.22-1
Power Supply card installation, 13.22-1
Class A
13.25-1
13.25-1
Mod 1), 14.14-6
Mod 2), 14.14-8
intershelf cables, 13.13-1
J21, 14.8-1
13.16-7
non redundant Switching to
Peripheral, 13.16-2
non redundant to HSPS, 13.16-5
power supply connections, 13.24-3,
13.25-1
redundant Switching to HSPS, 13.16-5
Class B
cable clamp, 13.31-2, 13.32-1
13.31-2, 13.32-1
IN-47
Index

13.32-1
13.32-1
Mod 1), 14.14-8
Mod 2), 14.14-9
ferrite bead, 13.31-2, 13.32-1
intershelf cables, 13.13-1
J14, 14.8-1
redundant to HSPS2, 13.16-7
Switching shelf
cooling guidelines, 10.2-3, 10.2-4
switching shelf controlled system
system cards, 2.1-4
SYNC, 22.3-2
SYNC ALARM, 23.11-3
SYNC_DEB, 22.3-25
SYNC_TIME, 23.11-2
Synch LED, 33.1-8
synchronization
ANS, 17.2-7
BRI S/T card, 7.2-5
stand-alone, 17.2-5
synchronization clock, 4.8-9
synchronization source
64 kb/s Codirectional, 7.1-3
Synchronization statistics, 34.1-25
manually clear, 34.1-26
view, 34.1-26
synchronization status messaging, 17.2-32
synchronous device mode, 22.3-2
SYSTEM, 23.6-49
system
diagnostics, 33.2-1, 33.2-15
System Advisory alarm, 17.6-11
system cards, 2.1-2, 3.14-1
configuring, 19.1-2
Control card, 19.1-1
IN-48

NNP 95-2035-01-00-B

GFC3, 19.1-2
in Locally controlled systems, 2.1-3
in switching shelf controlled systems, 2.1-4
Test card, 19.1-2
understanding, 19.1-1
system control bus, 3.6-14
system demerits, 16.5-5, 18.1-10
System Restart alarm, 18.1-13
System Synchronization Unit (SSU) Module,
4.5-5
systems
3600 MainStreet
architecture, 2.2-1
configurations, 2.3-1
36120 MainStreet
architecture, 2.2-7, 2.2-9
architecture, 2.2-4
3664 MainStreet
architecture, 2.2-7
application cards, 2.1-5
HSPS, 2.2-6
interface cards, 2.1-5
Peripheral shelf, 2.2-6
redundancy, 2.1-12
single and double bandwidth, 2.1-7
Switching shelf, 2.2-5
timing and synchronization, 2.1-9
upgrades, 2.2-1, 2.2-6, 2.2-7, 2.2-10
T
T1 card, 20.1-1
CCM, 20.3-2
faceplate monitor jacks, 36.1-1
line length, 20.7-1
pinout, 14.10-85, 14.10-86
HDSL module, 14.10-87, 14.10-88
RBS, 20.12-4, 31.15-3
SAM, 20.3-2
B8ZS, 20.8-2
JB7, 20.8-2

NNP 95-2035-01-00-B
transparent, 20.8-1
T1 card
bypass connector, 5.3-15
diagnostics, 5.3-19
faceplate, 5.3-14
LEDs, 5.3-16
loopbacks, 5.3-19
modules, 5.3-8
monitor jacks, 5.3-15
overview, 5.3-1
statistics, 5.3-21
T1 card (Wire-wrap adapter)
pinout, 14.10-86
T1 HDSL, 20.1-2
T1 IHTU, 5.3-12
T1 LIM, 20.1-2
T1 signalling termination, 25.11-3
T1 timer, 27.14-4
T1 yellow alarm clearing method, 35.5-3
T1_PRI, 30.3-4
T1_SIG, 20.12-8, 21.3-7
T10/T20 timer, 27.14-18
T11/T21 timer, 27.14-18
T12/T22 timer, 27.14-18
T13/T23 timer, 27.14-18
T2 timer, 27.14-5
T24 timer, 27.14-19
T3 timer, 27.14-5, 29.3-5
T3_TIMER, 29.4-3
tables 6-1 and 6-2 in X.25, 27.2-11
TANDEM, 20.16-4
tandem super-rate configuration, 29.3-7
Tc, 25.1-4
TE, 29.3-4, 29.4-3
TEP-1 (E) alarm interface, 35.7-5
TEP-1(E) equivalence
Test card
clock connectors, 4.11-6
digital test access, 4.11-3
DS-0 connector, 4.11-6
facilities and equipment connectors, 4.11-6
LEDs, 4.11-6
Index
pinout, 14.10-89, 14.10-90

Test card, 19.3-5
25-pair pinouts, 36.3-11
diagnostics, 4.11-7
DS0 connections, 36.3-2
faceplate, 36.3-9
faceplate features, 4.11-6
functional descriptions, 4.11-2
functionality, 36.3-1
loopbacks, 4.11-8
maintenace connections, 4.11-8
metallic connections supported, 36.3-7
overview, 4.11-1, 36.3-1
Test module
overview, 4.11-1
test module
Test points
T1 card monitor jack, 36.1-1
test port, 4.8-8
Test Port connectors
TESTCARD, 19.3-5
The, 33.2-1
THRESHOLD, 17.2-24
threshold bit error rates, 20.17-2
THRESHOLDS, 25.4-7, 25.4-9
thresholds
25.10-8, 27.13-9
27.13-15
throughput class
defaults, 27.15-27
definition, 27.15-26
Throughput Class Negotiation facility, 27.14-11
parameter, 27.14-24, 28.2-17
Throughput Class Negotiation parameter,
27.14-24
TIME, 17.4-2
time, 17.4-2
time out, 25.6-8
time synchronization record
statistics, 34.5-14
Time Zone parameter, 27.10-22
TIME_OUT, 25.6-8
IN-49
Index
timers
congestion, 27.14-6
link layer, 26.2-7, 27.14-4
link layer inactivity, 27.14-5
network layer, 27.14-10
network layer inactivity, 27.14-19
network layer protocol, 26.2-6
T1, 27.14-4
T10/T20, 27.14-18
T11/T21, 27.14-18
T12/T22, 27.14-18
T13/T23, 27.14-18
T2, 27.14-5
T24, 27.14-19
T3, 27.14-5
window, 27.14-19
timeslot 24 signalling, 20.5-1
timeslot zero, 20.19-4
timing and synchronization, 2.1-9, 10.6-1
automatic, 17.2-1
methods, 17.2-5
sources, 17.2-1
stand-alone, 17.2-1
Timing card
microcontroller, 4.3-2
overview, 4.3-1
system timing unit, 4.3-2
Timing cards
faceplate LEDs, 4.3-3
timing connectors, 10.6-2, 10.6-12
J13, 10.6-7, 10.6-17
J14, 10.6-10, 10.6-21
J17, 10.6-8, 10.6-11, 10.6-19, 10.6-22
J20, 10.6-17
J21, 10.6-10, 10.6-21
timing inputs
1.544 Mb/s AMI, 10.6-8, 10.6-19
2.048 MHz, 10.6-7, 10.6-17
6DDS composite clock, 10.6-8
8 kHz, 10.6-7, 10.6-17
DDS composite clock, 10.6-19
timing outputs
1.544 MHz, 10.6-10, 10.6-21
2.048 MHz, 10.6-10, 10.6-21
8 kHz, 10.6-10, 10.6-21
timing receivers, 10.6-2, 10.6-12
IN-50

NNP 95-2035-01-00-B
timing sources, 10.6-2, 10.6-12

class, 17.2-23
configuring source type, 17.2-19
DDS composite clock, 17.2-27
derived, 2.1-10, 17.2-1
external, 2.1-10, 17.2-1
failure recovery method, 17.2-24
failure threshold, 17.2-24
input frequency, 17.2-25
internal, 2.1-10, 17.2-1
locally controlled shelf, 17.2-2
numbers, 17.2-19
output frequency, 17.2-25
source and node class, 17.2-23
TLPs, 21.5-1
levels, 21.5-2
ranges, 21.5-7
TM, 20.20-12, 22.3-7
TO, 21.3-4
TO signalling mode, 21.3-1
TOA/NPI Address Format parameter,
27.15-13, 28.3-7
tool requirements, 12.1-2
TRANS, 20.4-7
TRANS_G3, 20.4-7
parameter, 27.11-7
Transfer Block Size parameter, 27.11-6
transfer blocks, 27.11-3
transferring records to the data collector,
27.11-3
transitional signalling, 20.4-1
connection restrictions, 20.4-6
sub-channels, 20.4-5
Translate Called Address parameter, 28.2-24
Translate Calling Address parameter, 28.2-24
Translate Incoming Packets parameter, 28.2-24
Translate Outgoing Packets parameter, 28.2-25
transmission level points, 21.5-1
transmit as received, 20.6-1
TRANSP, 20.8-2
TRANSP_BW, 17.6-19, 22.3-21, 22.4-4, 22.4-6,
23.6-48, 23.6-49, 23.9-8, 23.11-3, 25.5-3, 25.9-7,
25.9-9
TRANSP_POS, 22.4-4, 23.6-49, 23.11-3, 25.9-9,
29.3-10
TRANSPAREN, 22.3-21, 22.3-24, 22.4-4, 22.4-6,
23.6-48, 23.6-49, 23.9-8, 23.11-3
transparent HDLC encapsulation, 25.10-5

NNP 95-2035-01-00-B
transparent rate adaption, 23.3-4, 23.6-1,

23.6-16
super-rate DCC circuits, 22.3-17
transport layer, 17.2-7
transport position
3DS-0, 29.3-10
Trap Action - Clear Call parameter, 28.2-26
Trap Incoming Called parameter, 28.2-25
Trap Incoming Calling parameter, 28.2-25
Trap Outgoing Called parameter, 28.2-26
Trap Outgoing Calling parameter, 28.2-26
trunk circuits
busying out, 38.1-10
configuring, 27.8-3
connecting, 27.8-5
description, 27.8-1
disabling, 38.1-10
enabling, 38.1-10
viewing, 27.8-2
configuring, 20.9-7
one-way, 20.9-2, 31.12-2
two-way, 20.9-5, 31.12-4
trunk failures, 27.6-16
TRUNK_COND, 20.9-7, 20.9-10, 20.16-4
TS, 20.3-3
TS0, 5.5-1, 17.6-23, 20.20-1
TS24
frame fault signalling, 20.16-1
TS24_FRAME, 20.16-4
TS24_SIG, 20.5-2, 20.16-4
TSM, 5.3-10, 20.1-2
TTC2M card
card slot, 20.2-1
companding conversion, 20.3-5
connections, 5.6-1
connectors, 5.6-5
Index
diagnostics, 5.6-6
E1/T1 conversion, 20.3-5
faceplate, 5.6-4
LEDs, 5.6-5
loopbacks, 5.6-7, 36.7-26
overview, 5.6-1
pinout
faceplate, 14.10-92
reset, 36.11-1
set and show signalling, 36.2-1
signalling, 5.6-2
software downloading, 5.6-6
trunk conditioning - custom, 20.11-1,
20.11-3
TU-12 mapper card
loopbacks, 36.7-51
TWO_WAY, 20.9-7
Two-way SVCs parameter, 27.14-17
Tx mute, 21.9-1
TX_MODE, 20.6-3
TX_TLP, 21.5-7
TXMUTE_ON/OFF, 21.9-2
TYPE, 19.3-4
TYPE I, 21.3-4
TYPE II, 21.3-4
TYPE III, 21.3-4
TYPE IV, 21.3-4
TYPE V, 21.3-4
U
UDP, 3.10-7, 5.5-4
UK, 21.2-4
UNDO_MAINT
on circuits, 38.1-12
UNIDIR/NO_UNIDIR, 22.2-4
Universal Distribution Panel, 3.10-7, 5.5-4
UNPROTECTD, 18.1-6
unstable card, 18.3-9
UNUSD_FSIG, 20.10-5, 20.11-3
IN-51
Index
Usage statistics, 34.1-1

clearing statistics manually, 34.1-3
display, 34.1-3, 36.5-15
USER, 23.6-49
user configuration
address, 26.3-3
administrative status, 26.3-3
default user, 26.3-3
definition, 26.3-2
name, 26.3-2
operational status, 26.3-3
User Defined Data parameter, 27.15-4
user management, 26.1-4
user screening, 26.3-5
user-installable modules, 13.38-1
user-reserved branch channels, 23.6-27
V
V.35, 22.3-1
V.35 DCC, 22.1-1
V.35 Direct Connect card, 22.1-1
pinout
backplane or bulkhead, 14.10-93,
14.10-95
faceplate, 14.10-94, 14.10-96
V.35 PRI card, 20.1-1
overview, 5.4-1
pinout
faceplate, 14.10-98
V.35_DCC, 22.2-1
V_FILTER, 21.3-4
variant ID, 16.5-5
VCB, 23.5-4
applications, 23.5-1
broadcast mode, 23.5-6
circuit, 23.5-4
input gain, 23.5-4
listen-only mode, 23.5-5
output gain, 23.5-4
sidetone gain, 23.5-4
VCM, 5.3-9, 5.3-10, 20.1-2, 20.4-1
VCon
description, 27.2-4
IN-52

NNP 95-2035-01-00-B
verification, 30.4-5
VERIFY, 30.4-5
Verify configuration database, 39.1-8
verifying power connections and LED
operation, 13.36-1
verifying the shipment, 12.2-1
version of X.25, 27.14-14
Version parameter, 28.2-9
VERSION_1, 17.6-17, 23.6-47, 23.7-5
VERSION_2, 17.6-17, 23.6-47, 23.7-5
VIA_CPSS, 20.14-6
VIA_TS24, 20.14-6
View
available and active diagnostics, 33.2-14
virtual call
routing process, 27.7-21
setup process, 27.7-12
virtual circuit
virtual circuit accounting, 27.10-1
VOICE, 20.13-1, 21.2-3
voice and data connections
overview, 10.4-1
voice and data interface connections, 10.4-1
Voice card loopbacks, 36.7-48
voice compression
configuring, 20.4-6
Voice Compression Module, 5.3-9, 5.3-10,
20.4-1
voice conference bridge, 23.5-1
voice interface card
Voice interface cards
configuring loop balance, 21.10-1
loop balance, 21.10-1
configuring, 21.1-2
TLPs, 21.5-1
voice interface channel unit
voice interface channel units, 21.1-1

NNP 95-2035-01-00-B

Tx mute, 21.9-1
voice interface connections, 10.4-2
VT-1.5 mapper card
loopbacks, 36.7-51
VT100, 17.3-7
VT100 terminal, 16.2-5
W
wander, 20.19-8, 20.20-16
WII jumper, 18.1-5
wildcard characters
in the address translation table, 27.14-35
in the Global Address Table, 27.7-3
Window Timer parameter, 27.14-19, 27.14-20,
28.2-14
wire-wrap adapters
WRAP_A, 25.4-2
WRAP_B, 25.4-2
Wrong Card in Slot alarm, 21.5-7, 21.6-1
X
X.121, 26.3-2
X.121 address format, 27.15-1
X.2, 27.3-1
X.21, 22.3-1
X.21 DCC, 22.1-1
X.21 DCC card
pinout
faceplate, 14.10-100, 14.10-102
X.21 Direct Connect card, 22.1-1
pinout
backplane or bulkhead, 14.10-99,
14.10-101
X.21 ESI PRI card
overview, 5.4-1
X.21 network termination unit, 20.6-5
X.21 NTU, 20.6-5
X.21 PRI card, 20.1-1
framing, 20.6-7
overview, 5.4-1
pinout
faceplate, 14.10-104
Index
X.21/V.35 PRI cards, 20.1-1

clock inversion, 20.19-6
clocking source, 20.19-6
faceplate, 5.4-4
jitter and wander, 20.19-8
LEDs, 5.4-5
loopbacks, 5.4-6
options, 20.19-1
slip buffer, 20.19-8
supervisory channel, 20.19-4
timeslot zero, 20.19-4
X.21_DCC, 22.2-1
X.25
definition, 27.1-1
X.25 access circuits
busying out, 38.1-8
copying configurations, 27.16-1
disabling, 38.1-7
enabling, 38.1-7
reset, 27.14-44
service types, 27.14-14
statistics, 34.5-25
status information, 33.11-1, 33.11-3,
33.11-16
X.25 access line
access methods, 27.13-1
definition, 27.1-2
X.25 accounting
statistics, 34.5-11
status, 33.11-5
X.25 encapsulation, 8.5-1, 27.13-2
X.25 FRE card, 25.1-1
X.25 FRE card
definition, 27.1-3
X.25 PVCs, 27.17-1
X.25 Version parameter, 27.14-14
X.35, 27.3-5
X.36, 26.2-5
X.50, 22.2-2, 22.3-17, 23.6-47, 23.6-49, 23.9-7,
23.9-8
X.50 rate adaption
IN-53
Index
Basic, 23.6-15
Division 2, 23.6-14
Division 2 framing pattern, 23.6-12
Division 3, 23.6-14
Division 3 framing pattern, 23.6-13
Telco, 23.6-15
X.50 Telco, 23.6-15
X.50_HCM, 22.4-5
X.50_TELCO, 22.2-2
X.75
interconnection possibilities, 28.1-1
IPVCs, 28.1-6
Overview, 28.1-1, 28.2-1, 28.3-1
overview, 28.1-1, 28.2-1, 28.3-1
Routing examples, 27.7-16
Statistics, 34.5-14
utilities, 28.1-2
Weights and priorities, 27.7-18
X.75 accounting, 28.1-8
X.75 LCN Selection parameter, 28.2-9
X.75 parameters overview, 28.2-1
X.76, 26.2-5
X50, 25.9-7, 25.9-10
X50_OR_HCM, 25.9-4
X50_TELCO, 23.6-47
IN-54

NNP 95-2035-01-00-B
XACs
busy out, 38.1-7, 38.1-8
disable, 38.1-7
enable, 38.1-7
link layer status, 33.11-20
network layer status, 33.11-22
XCLK pin, 22.3-9
XON/XOFF, 17.3-9
Y
Y-cable connector, 18.3-2
Yel. Alarm LED, 33.1-8
YELLOW_OFF/ON, 20.9-10
Z
ZBS_ON/OFF, 22.3-36
ZCO, 21.6-2
zero byte substitution, 22.3-36
B8ZS, 20.8-2
JB7, 20.8-2
transparent, 20.8-1
ZERO_SUPPR, 20.8-2
ZONE_ID, 17.2-13
zones, 17.2-10
CORPORATE
HEADQUARTERS
Newbridge Networks
Corporation
600 March Road
P.O. Box 13600
Kanata, Ontario
Canada K2K 2E6
Tel. 613 591-3600
FAX 613 591-3680
http://www.newbridge.com
North and
South America
Europe, Middle East

and Africa
Asia Pacific
Newbridge Networks Inc.

593 Herndon Parkway
Herndon, Virginia
U.S.A. 22070-5241
Tel. 1 800 343-3600
703 834-3600
FAX 703 471-7080
Newbridge Networks
Limited
Coldra Woods
Chepstow Road
Newport, Gwent
NP6 1JB U.K.
Tel. +44 (0) 1633 413600
FAX +44 (0) 1633 413680
Newbridge Networks
Corporation
600 March Road
P.O. Box 13600
Kanata, Ontario
Canada K2K 2E6
Tel. 613 591-6300
FAX 613 591-3201
Printed in Canada
95-2035-01-00-B

Manual Serie 3600 Newbridge

Загружено:

Сведения о документе

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Manual Serie 3600 Newbridge

Загружено:

Авторское право:

Доступные форматы

Information subject to change without notice.

Customer Documentation and Product Support

By providing up-to-date information, TechInfo.NOW can help customers increase

North and South America

Asia Pacific and the former Soviet

0 1633 413 666

852 2807 3600

+81 45661 3612

7 095 723 6375

3600 MainStreet Series Bandwidth Managers

16. Getting Started

How to Use Operations and Configuration

Who Should Use this Manual ...................................................................... 16.1-1

Running a Node Management Session

Understanding Node Management Sessions .............................................. 16.2-1

Working with Node Management Sessions

Beginning a Node Management Session .................................................... 16.3-1

3600 MainStreet Series Bandwidth Managers

About Identifiers ........................................................................................... 16.4-1

3600 MainStreet Series Bandwidth Managers

Displaying Configuration Information

Displaying Slot Information .......................................................................... 16.5-1

17. Node Parameters

Understanding Connections ........................................................................ 17.1-1

Configuring Timing and Synchronization

Understanding Timing and Synchronization ................................................ 17.2-1

Configuring ANS Node Parameters ........................................................... 17.2-13

Serial and Ethernet Ports

3600 MainStreet Series Bandwidth Managers

Understanding the Ports .............................................................................. 17.3-1

3600 MainStreet Series Bandwidth Managers

Configuring Serial Ports ............................................................................... 17.3-4

Date, Time, and Node Name

Configuring the Date, Time, and Node Name .............................................. 17.4-1

Access Levels and Passwords

Understanding Access Levels and Passwords ............................................ 17.5-1

3600 MainStreet Series Bandwidth Managers

Understanding CPSS Configuration ............................................................ 17.6-1

3600 MainStreet Series Bandwidth Managers

Configuring CPSS over FDL and TS0 ....................................................... 17.6-22

Backplane Card Communications

Overview ...................................................................................................... 17.7-1

Understanding Control Redundancy ............................................................ 18.1-1

Configuring Control Redundancy Parameters ............................................. 18.1-4

3600 MainStreet Series Bandwidth Managers

Understanding Protection Switching ............................................................ 18.2-1

3600 MainStreet Series Bandwidth Managers

Understanding PRI Redundancy ................................................................. 18.3-1

19. System Cards

Understanding System Card Configuration

Understanding System Cards ...................................................................... 19.1-1

Understanding GFC3 Card Operation

GFC3 Card Operations ................................................................................ 19.2-1

3600 MainStreet Series Bandwidth Managers

System Card Slots

Understanding System Card Slots ............................................................... 19.3-1

20. Primary Rate Interface Cards

Understanding PRI Card Configuration

Understanding PRI Cards ............................................................................ 20.1-1

3600 MainStreet Series Bandwidth Managers

PRI Card Slots

Understanding E1-to-T1 Conversion ........................................................... 20.3-1

Understanding PRI Card Slots ..................................................................... 20.2-1

Understanding Voice Compression ............................................................. 20.4-1