JDS Uniphase CT-650 Reference Manual

CT-650 Wideband Test Unit

Release 9.4

Command-Line Reference Guide

CT-650 Wideband Test Unit

Release 9.4

Command-Line Reference Guide

Notice

Every effort was made to ensure that the information in this docu ment
was accurate at the time of printing. However, information is subject to
change without notice, and JDSU reserves the right to provide an
addendum to this document with information not available at the time
that this document was created.

Copyright

Trademarks

Ordering Information

© Copyright 2011, JDSU. All rights reserved. JDSU, Test and
Measurement Solutions, and its logo are trademarks of JDSU. All
other trademarks and registered trademarks are the property of their
respective owners. No part of this guide may be reproduced or trans­mitted electronically or otherwise without written pe rmission of the
publisher.

JDSU, CT-650 and CT -6 50s are trademarks or registered trademarks
of JDSU in the United States and/or other countries.

UNIX is a trademark or registered trademark of The Open Group in the
United Sta tes and/or other countries.

SLC 96 is a trademark of Lucent Technologies, Inc.
Specifications, terms, and conditions are subject to change without

notice. All trademarks and registered trademarks are the proper ty of
their respective companies.

This guide is a product of JDSU's Technical Information Development
Department, issued as part of the CT-650 Documentation Release
CD. This CD is available as part of the CT-650 System Software,
ordering number CT650-REV-9.4-U1.

CT-650 Command-Line Reference Guide Release 9.4 v

Important safety instructions

The following table defines safety terms. Failure to observe these
precautions while using the CT-650, violates the intended use of this
product.

Safety definitions

Term Description

DANGER Indicates an imminently hazardous situation which, if

not avoided, will result in death or serious injury.

WARNING Indicates a potentially hazardous situation which, if

not avoided, could result in death or serious injury.

CAUTION Indicates a potentially hazardous situation which, if

not avoided, may result in minor or moderate injury. It
may also be used to alert against unsafe practices.

When using this product, always follow basic safety precautions to
reduce the risk of fire, shock, and injury to persons. Basic safety
precautions are as follows:

1 Read and follow all warning notices and instructions marked on

the product and included in the manual.

2 Avoid using this product during an electrical storm. There may be

a remote risk of electric shock from lightning.

3 Do not use this product in the vicinity of a gas leak or in any explo-

sive environment.

4 Do not attempt to service this product yourself, as opening or

removing covers may expose you to dangerous, high voltage
points and other hazards. Refer all servicing to qualified service
personnel.

5 All connections to the CT-650 are intrabuilding and must not be

connected directly to outside plant leads.

Save these instructions

vi CT-650 Command-Line Reference Guide Release 9.4

Symbols

The following safety symbols are used on the CT-650. All safety
precautions must be observed when operating, servicing, or repairing
the CT-650. Failure to comply with the following safety precautions or
with hazard cautions and warnings used throughout this manual
violates the intended use of this instrument.

GENERAL HAZARD

This icon represents a general warning or caution.

CAUTION: HIGH VOLTAGE

This icon represents a caution, risk of electrical shock.

CT-650 Command-Line Reference Guide Release 9.4 vii

Compliance information

The CT-650s complies with the following standards:

Federal

Communications

Commission (FCC)

Notice

Industry Canada

Requirements

This product was tested and found to comply with the limits for a Class
A digital device, pursuant to Part 15 of the FCC Rules. These limits are
designed to provide reasonable protection against harmful interfer­ence when the equipment is operated in a commercial environment.
This product generates, uses, and ca n radiate radio frequency ener gy
and, if not installed and used in accordance with the instruction
manual, may cause harmful interference to radio communications.
Operation of this product in a residential area is likely to cause harmful
interference, in which case you will be required to correct the interfer­ence at your own expense.

The authority to operate this product is conditioned by the require­ments that no modifications be made to the equipment unless the
changes or modifications are expressly approved by JDSU.

This Class A digital apparatus complies with Canadian ICES-003.
Cet appareil numérique de la classe A est conforme à la norme NM B-

003 du Canada.

viii CT-650 Command-Line Reference Guide Release 9.4

Contents

About This Guide xxiii

Purpose and scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxiv

Assumptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxiv

Related information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxiv

Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxiv

Chapter 1 Getting Started 1

About the new USPII processor module . . . . . . . . . . . . . . . . . . . . . . 2

About the new RTU cards. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Logging on . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Understanding the CT-650 screens . . . . . . . . . . . . . . . . . . . . . . . . . 6

Menu screens. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Supervisor screens. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Command screens . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Confirmation screens . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Results screens . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Loopback status line. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Information screens . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Entering commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Editing commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Abbreviating command entry . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Control characters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

CT-650 Command-Line Reference Guide Release 9.4 ix

Contents

Sample test procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Step 1: Initiate the test. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Step 2: Split the circuit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Step 3: Loop up the circuit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Step 4: Measure test results . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Step 5: Loop down the circuit . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Step 6: Disconnect the test . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Logging off. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Chapter 2 Auxiliary and Common Commands 21

Auxiliary commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Batch_Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Syntax. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Remarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Choose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Syntax. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Remarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Daytime. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Syntax. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

DCS_Direct . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Syntax. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Remarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Delete_Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Syntax. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Remarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Email. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Syntax. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Remarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Error_Rate. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Syntax. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Remarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Examine_Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Syntax. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Remarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Exit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Remark. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Files_List. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Syntax. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Remarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

x CT-650 Command-Line Reference Guide Release 9.4

Contents

Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Remarks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Inject_Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Remarks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Line_Coding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Remarks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Logout. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Remark. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Loopback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Remark. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Main_Exit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

OS_Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Remark. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Port_Connect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Remarks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Printer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Prog_Loop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Remarks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Record . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Remarks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Release. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Remarks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Restart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Remark. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

CT-650 Command-Line Reference Guide Release 9.4

xi

Contents

Screen_Refresh . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Syntax. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Self_Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Syntax. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Remarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Supervisor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Syntax. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Remark. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

TAP_Loopback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Syntax. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Remarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Text_Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Syntax. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Remark. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

User_Pattern. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Syntax. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Remarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Syntax. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

View_Results. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Syntax. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Remark. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Who. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Syntax. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Remarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Write . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Syntax. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Remarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

! (History). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Syntax. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Remark. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Common test commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Abort . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Syntax. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Remarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Disconnect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Syntax. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Remarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

xii CT-650 Command-Line Reference Guide Release 9.4

Contents

Report. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Remark. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Select_Test. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Remark. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Chapter 3 DS3 Test Commands 41

Description of DS3 test commands. . . . . . . . . . . . . . . . . . . . . . . . . 42

DS3_Measure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Remarks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

DS3_Split . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Remarks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

FEAC_Alarm. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Remark. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Remarks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

Tx_X_Bit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

Remarks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

Example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

Chapter 4 DS1 Test Commands 45

Description of DS1 test commands. . . . . . . . . . . . . . . . . . . . . . . . . 46

DI_Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Remark. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

DS1_DI_Measure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Remarks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

CT-650 Command-Line Reference Guide Release 9.4

xiii

Contents

DS1_DI_Split. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Syntax. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Remark. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

DS1_Measure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Syntax. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Remarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Check_

Pre-existing_Loop. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Syntax. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Remark. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

DS1_Split . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Syntax. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Remarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Log_Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Syntax. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Remarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Syntax. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Remarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

UF_Split. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Syntax. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Remark. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Yellow_Alarm. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Syntax. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Considerations for SLC-96 testing. . . . . . . . . . . . . . . . . . . . . . . . . . 50

Chapter 5 FT1 Test Commands 53

Description of FT1 test commands . . . . . . . . . . . . . . . . . . . . . . . . . 54

DI_Monitor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

Syntax. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

Remark. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

FT1_DI_Measure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

Syntax. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

Remarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

xiv CT-650 Command-Line Reference Guide Release 9.4

Contents

FT1_DI_Split. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

Remark. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

FT1_Measure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Remarks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

FT1_Split . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Remark. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Log_Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Remarks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Remark. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Shared_Split. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Remark. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

UF_Split . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Remarks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Chapter 6 DS0 DDS Test Commands 59

Description of DDS test commands . . . . . . . . . . . . . . . . . . . . . . . . 60

DDS_DI_Measure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

Remarks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

DDS_DI_Split . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

Remarks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

DDS_Measure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

Remarks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

DDS_Split. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Remarks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

DI_Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Remarks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

CT-650 Command-Line Reference Guide Release 9.4

xv

Contents

MJU. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

Syntax. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

Remarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Syntax. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Remarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Log_Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

Syntax. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

Remarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

Chapter 7 DS0 VF Test Commands 65

Trunk types and seizure sequences . . . . . . . . . . . . . . . . . . . . . . . . 66

Description of VF test commands . . . . . . . . . . . . . . . . . . . . . . . . . . 66

Answer_Call . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

Syntax. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

Remarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

DI_Monitor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

Syntax. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

Dial_Out . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

Syntax. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

Remarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

Hangup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

Syntax. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

Remarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

Listen. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

Syntax. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

Remarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

Loopback. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

Syntax. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

Remarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

Syntax. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

Remark. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

Talk/Listen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

Syntax. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

Remarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

xvi CT-650 Command-Line Reference Guide Release 9.4

Contents

TLHangup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

Remark. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

TLStatus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

Remarks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

VF_DI_Measure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

Available measure tests. . . . . . . . . . . . . . . . . . . . . . . . . . . 71

Remarks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

VF_DI_Split. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

Remarks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

VF_Measure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

Remarks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

VF_Split . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

Remarks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

Chapter 8 Batch Files 79

Creating and running batch files . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

Available commands for batch files. . . . . . . . . . . . . . . . . . . . . . . . . 80

Unavailable commands for batch files . . . . . . . . . . . . . . . . . . . . . . 81

Chapter 9 Supervisor Commands 83

Descriptions of supervisory commands . . . . . . . . . . . . . . . . . . . . . 84

Accounts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

Backup_Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

CT-650 Command-Line Reference Guide Release 9.4

xvii

Contents

Configure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

Adding and modifying configurations . . . . . . . . . . . . . . . . . 86

Deleting configurations. . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

Configure DCS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

Configuring RTUs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90

Configuring DT3 RTUs . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90

Configuring DT1 RTUs . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

Configuring DTU RTUs. . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

Configuring STS-1 RTUs . . . . . . . . . . . . . . . . . . . . . . . . . . 95

Configure Defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

Configure Misc.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

Configure Node. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

Configure Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

Configure Trunk_Types . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

Configure Answer_Seq. . . . . . . . . . . . . . . . . . . . . . . . . . . . 98

Configure Dial_Seq. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98

Reboot. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98

Syntax. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98

Remarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98

Release. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

Syntax. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

Restore_Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

Remarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

Shutdown . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

Syntax. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

Remarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

Auxiliary supervisor commands. . . . . . . . . . . . . . . . . . . . . . . . . . . 100

Clear_Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100

Syntax. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100

Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100

Examine_Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100

Syntax. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100

LUP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100

Syntax. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100

Remarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100

Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

Syntax. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

Remarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

Set_Date. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

Syntax. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

xviii CT-650 Command-Line Reference Guide Release 9.4

Contents

System_Test. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102

Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102

Example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102

Appendix A Test Results Definitions 103

Information results. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104

Alarms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104

Configure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104

Ports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104

DCS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

RTU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

Defaults DS3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

Defaults DS1/FT1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110

Defaults DS0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111

Miscellaneous . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111

Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113

Trunk_Types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114

Answer_Seq. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115

Dial_Seq. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115

CRS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116

Slots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116

Tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117

Talk/Listen. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118

TAPS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120

DS3 results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121

Header . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121

Bipolar violations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125

C-Bit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126

Frame . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127

Logic. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128

Line status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129

Parity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131

Signal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133

Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133

DS1 results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134

Header . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134

Bipolar violations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138

Channel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138

Frame . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139

G.821 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140

Line status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141

Logic. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143

CT-650 Command-Line Reference Guide Release 9.4

xix

Contents

Signal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144

Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144

FT1 results. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145

Header . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145

Channel. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149

G.821. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151

Line status. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152

Logic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153

Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154

DS0 DDS results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154

Header . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154

Channel. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158

G.821. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160

Line status. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160

Logic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161

Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162

DS0 VF results. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163

Header . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163

Answer Call. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165

Dial Out. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165

Channel. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165

Terse . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166

Verbose. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166

Listen. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166

VF_DI_Measure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167

Supervisor results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169

System_Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169

Loopback status information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170

Appendix B Command Parameter Definitions 173

Parameter listing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174

Specifying digroup numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187

FEAC alarm messages and loop codes . . . . . . . . . . . . . . . . . . . . 188

Appendix C Test Patterns and Loop Codes 191

Test patterns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192

Bridgetap/Multipat patterns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198

LUP option test patterns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199

Loop codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206

xx CT-650 Command-Line Reference Guide Release 9.4

Contents

Appendix D Customer Services and Support 209

About our services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210

Standard support services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210

Instrument repair and calibration services . . . . . . . . . . . . . . . 210

Technical assistance (business hour). . . . . . . . . . . . . . . . . . . 211

Warranty information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211

Product documentation library . . . . . . . . . . . . . . . . . . . . . . . . 211

Add-on services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211

Extended product and systems support services. . . . . . . . . . 212

Professional and consulting services . . . . . . . . . . . . . . . . . . . 213

Managed services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213

Training options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213

Index 215

CT-650 Command-Line Reference Guide Release 9.4

xxi

Contents

xxii CT-650 Command-Line Reference Guide Release 9.4

About This Guide

– “Purpose and scope” on page xxiv
– “Assumptions” on page xxiv
– “Related information” on page xxiv
– “Conventions” on page xxiv

CT-650 Command-Line Reference Guide Release 9.4 xxiii

About This Guide

Purpose and scope

Purpose and scope

The purpose of this guide is to help you successfully use the features
and capabilities of the CT-650 as part of your network service fulfill­ment and assurance solution. This reference guide contains concise
information on the command-line interface provided by terminals
connected to the CT-650, as well as test results and configuration
information.

Assumptions

This guide is intended for users who are experienced with the
command-line interface provided by the CT-650 and a VT-100
compatible terminal. We assume you have basic knowledge of the
UNIX operating system, and are familiar with basic telecommunica­tions concepts and terminology.

Related information

For installation and administrative tasks, refer to the CT-650 Installa­tion and Maintenance Guide. Users who are new to the CT-650, or
who prefer to work with NetAnalyst, can use the CT -650 User’s Guide.

Conventions

This guide uses naming conventions, as described in the following
tables.

Typographical conventions

Description Example

Commands appear in this type-

face.

Switches that you press on a unit
appear in this

xxiv CT-650 Command-Line Reference Guide Release 9.4

TYPEFACE.

On the Status bar, click Start.

Press the AUX switch.

Typographical conventions (Continued)

Description Example

About This Guide

Conventions

Code and output messages

All results okay

appear in this typeface.
Text you must enter exactly as

shown appears in this typeface.

Type: a:\set.exe in the dialog

box
V ariables appear in this typeface. Type the new hostname.
A vertical bar | means “or”: only

platform [a|b|e]

one option can appear in a single
command.

Square brackets [ ] indicate an

login [platform name]

optional argument.
Slanted brackets < > group

<password>
required arguments.

CT-650 Command-Line Reference Guide Release 9.4

xxv

About This Guide

Conventions

Keyboard and menu conventions

Description Example

A plus sign + indicates simulta­neous keystrokes.

A comma indicates consecutive
key strokes.

A slanted bracket indicates choos­ing a submenu from menu.

Press Ctrl+s

Press Alt+f,s

On the menu bar, click

Start > Program Files.

xxvi CT-650 Command-Line Reference Guide Release 9.4

Chapter1

Getting Started

1

This chapter presents basic information on operating the CT -650 using
the command-line interface. Topics discussed in this chapter are as
follows:

– “About the new USPII processor module” on page 2
– “About the new RTU cards” on page 2
– “Logging on” on page 5
– “Understanding the CT-650 screens” on page 6
– “Entering commands” on page 11
– “Sample test procedure” on page 13
– “Logging off” on page 20

CT-650 Command-Line Reference Guide Release 9.4 1

Chapter 1 Getting Started

About the new USPII processor module

About the new USPII processor module

A new USPII main processor module has been developed to replace
the processor module previously used in the CT-650 and CT-650s
products. It has been designed as a drop-in replacement for th e old
processor module. Key differences between the new an d old
processor module are listed in the following table:

Previous processor module New USPII processor module

Provided processor speeds up to
100MHz and memory sizes up to
64 Megabytes.

Provided up to 12 serial ports. Provides four serial ports.
Provided an internal modem. Does not provide an internal

Supported any version of Solaris
supplied on any testhead CD.

Provided one external SCSI inter­face with a 68 pin female D-shell
for connection to an external CD­ROM drive.

Ethernet devices were named
hme0 and hme1.

The CT-650 required a separate
SCSI hard disk module; the CT­650s used an internal SCSI hard
disk.

Provides 550MHz processor
speed and 256 Megabytes of
memory.

modem.
Only supports Solaris version

8 2/02, supplied on testhead CD
versions 8.0 or higher.

Provides two external SCSI inter­faces (A and B), each with a 68
pin mini connector. Connector A
must be used when connecting to
an external CD-ROM drive.

Ethernet devices are named eri0
and eri1.

Provides a solid state storage
media for both the CT-650 and
CT-650s. No SCSI hard disk
module is required.

About the new RTU cards

Due to part obsolescence of the existing DT1, DTU, and DT3 RTU
cards distributed with the CT -650 product line prior to release 9.0, new
RTU cards have been developed. They are referred to as follows:

2 CT-650 Command-Line Reference Guide Release 9.4

Chapter 1 Getting Started

About the new RTU cards

–DT1-R2
–DTU-R2
–DT3-R2

The new cards are compatible with the old cards, therefore th ese new
RTUs can be installed in a system wi th old RTU cards. This allows the
flexibility to mix old and new RTUs in the same system. In addition,
these new RTU cards are drop-in replacements for the existing RTU
cards and function the same as the old RTU cards except for a few
exceptions, as detailed in Table 1.

Table 1 Differences in functionality between older RTU card s

and ‘R2’ RTU cards

Old RTU cards Rev2 RTU cards

Compatible with any CT-650 soft­ware version.

DTU supports 2 or 4 wire Talk/Lis­ten ports.

DTU supports GSM testing. DTU-R2 does not support GSM

DT1, DTU, and DT3 have one
green front panel LED to indicate
test progress.

Compatible with CT-650 software
version 9.0 or newer only. If the
new RTU is installed in a system
that uses a software version older
than 9.0, the two green front
panel test LEDs will alternately
blink, indicating that the currently
installed software version is not
compatible with the new RTU.

DTU-R2 supports only 2 wire
Talk/Listen ports.

testing.
DT1-R2, DTU-R2, and DT3-R2

have two green front panel LEDs
to indicate test progress, one for
side A and one for side B. (See

Figure 1 on page 4 and Figure 2
on page 5 for a visual representa-

tion of the differences.)

Table 2 on page 4 shows the CLEI (Common Language Equipment

Identifier) codes for the old and new RTU cards that appear on the
front panel label. Y ou can refer to this table to verify which R TU(s) and
RTU version(s) you have.

CT-650 Command-Line Reference Guide Release 9.4

3

Chapter 1 Getting Started

About the new RTU cards

Table 2 Part numbers and CLEI codes for the old and new

RTU cards

Old RTU cards R2 RTU cards
Card CLEI Code Card CLEI Code
For CT-650 For CT-650

DT1 T3TEAAB4AA DT1-R2 T3TEAAB4AB
DTU T3TEAAC4AA DTU-R2 T3TEAAC4AB
DT3 T3TELP94AA DT3-R2 T3TELP94AB

For CT-650s For CT-650s

DT1 SUCPKNMAAA DT1-R2 SUCPKNMAAB
DTU SUCPMPMAAA DTU-R2 SUCPMPMAAB
DT3 SUCPLNMAAA DT3-R2 SUCPLNMAAB

Figure 1 shows the difference in LED configuration on the front panel

of the R2 RTUs for CT-650 versus that of the old RTUs.

Figure 1 Front panel LEDs for R2 RTUs versus old

RTUs, for CT-650

4 CT-650 Command-Line Reference Guide Release 9.4

Chapter 1 Getting Started

Logging on

Figure 2 shows the difference in LED configuration on the front panel

of the R2 RTUs for CT-650s versus that of the old RTUs.

Figure 2 Front panel LEDs for R2 RTUs versus old

RTUs, for CT-650s

Logging on

To start a session with the CT-650, you need to log on with a user
name and password.

To log onto the CT-650
1 At the system prompt, log on using your user name and password.

The CT-650 displays a welcome banner.

2 If you’re logging on to an account for the first time, the CT-650

prompts you to type a new password. Type the new password

twice to complete the logon process.
3 Press any key to continue to the main menu.
The Main Menu provides access to various commands, and will vary

depending on the installed features and o ptions. A sample Main Menu
is shown in Figure 3.

CT-650 Command-Line Reference Guide Release 9.4

5

Chapter 1 Getting Started

*** ct14 **************************CT-650**********************Version 7.4V1****

Main Menu
User: maint11 Test:

Enter the circuit type to be tested.

DS3 DS1 FT1 DS0 Logout
_______________________________________________________________________________
Batch_Command Choose Daytime DCS_Direct Delete_Log
Email Examine_Log Files_List Help Information
Main_Exit OS_Command Password Port_Connect Printer
Record Release Screen_Refresh Self_Test Text_Editor
View Results Version Who Write !(History)

===============================================================================
MAIN>

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

Banner

Test
Commands

Auxiliary
Commands

Understanding the CT-650 screens

Figure 3 CT-650 main menu

For an explanation of this screen, refer to “Understanding the CT-650

screens” on page 6.

Understanding the CT-650 screens

6 CT-650 Command-Line Reference Guide Release 9.4

The CT-650 displays different types of screens for displaying menus,
commands, results, and system information. The following sections
describe these screens.

Menu screens

Menu screens display the commands available for testing or
displaying system information. Figure 3 on page 6 is an example of a
menu screen.

– The banner displays the name of the CT-650, the software

version, your user name, and the name of the current foreground
test.

– Available test commands appear in the middle portion of the

screen. These commands change as you navigate through the
different menu screens.

Chapter 1 Getting Started

*** ct14 ***********************CT-650********************Version 7.4V1****

Supervisor Menu
User: super Test:

Enter one of the following SUPERVISOR commands:

Accounts Backup_Files Configure Exit Reboot
Restore_Files Shutdown
___________________________________________________________________________
Batch_Command Choose Clear_Alarm Daytime DCS_Direct
Delete_Log Disconnect Email Examine_Log Files_List
Help Information LUP Main_Exit OS_Command
Password Port_Connect Printer Record Report
Screen_Refresh Self_Test Set_Date System_Test Text_Editor
TLStatus Version Who Write
! History
===========================================================================
SUPER>_

Supervisor com­mands

Understanding the CT-650 screens

– Auxiliary commands appear in the bottom portion of the screen.

The available auxiliary commands change depending on the type

of test you are performing, as well as the features installed on your

CT-650.

Supervisor

screens

Another type of menu screen is the Supervisor Menu, which is avail­able when you log onto the CT-650 as super (Figur e 4 on page 7).
The menu displays additional commands available to supervisors. Y ou
can use these commands to manage user accounts, ar chive or restore
system files, and restart the CT-650.

Figure 4 Supervisor menu

For a detailed listing of supervisory commands, see “Supervisor

Commands” starting on page 83.

CT-650 Command-Line Reference Guide Release 9.4

7

Chapter 1 Getting Started

*** ct14 **************************CT-650**********************Version 7.4V1****

DS3 Menu
User: maint11 Test:

Enter the system/DT3 name:

3ECS3 6ECS3 7ECS3

================================================================================
DS3>monitor _

*** ct14 **************************CT-650**********************Version 7.4V1****

DS3 MONITOR:

System/RTU Name = Psuedo3
Test Name = 1test
Digroup = 345
Test Port Type = Dual DS3 Fad
Framing = Auto
Test Duration = Continuous
Log File = 1test.log
Do you want to EXECUTE this command? (Y/N) _

===============================================================================
DS3>monitor psuedo3 345 1test 1test auto continuous

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

Understanding the CT-650 screens

Command

screens

Confirmation

screens

A command screen displays the available parameter values for a
command. For example, in Figure 5, the command screen lists the
values 3ECS3, 6ECS3, and 7ECS3, which are valid for the Monitor
command. The command screens change each time you press Sp ace
after a parameter.

Figure 5 Command screen for Monitor command

After you specify all the parameters required for a test, the CT-650
displays a confirmation screen (see Figure 6).

8 CT-650 Command-Line Reference Guide Release 9.4

Figure 6 Confirmation screen for a Monitor command

To proceed with the command, press Y and then Enter. To return to
the previous screen without executing the command, press N and then

Enter.

Chapter 1 Getting Started

*** ct14 **************************CT-650**********************Version 7.4V1****

TEST: 1test DG: 43 SIG SRC: RCVD T3 RTU: 1_4A
SYS: 1st_dcs TP: 4 TYPE: MONITOR SIDE: SEL
TX FRM: CBIT TX PAT: UNMUXED 2^23-1 E. TIME: 00:00:23
RX FRM: CBIT TIM SRC: INTERNAL
SYNC STATUS: DS3 FRAME SYNC SPLIT TYPE: N/A
SUMMARY:

ALL RESULTS OK

-------------------------------------------------------------------------------­<L-Logic> <B-BPV> <F-Frame> <P-Parity> <C-CBit> <S-Signal> <T-Time>
<I-Line Status> <Q-to quit> <^O-Other side>

Header

Results

Hotkeys

Understanding the CT-650 screens

Results screens

The CT-650 displays test results in a results screen (see Figure 7).

Figure 7 Test results screen

The following sections appear in a results screen:
– A header, which displays system information and general test

results.
– A results section, which displays results for a specific test cate-

gory.
– A hotkeys list, which indicates how to display different results for

different test categories.

CT-650 Command-Line Reference Guide Release 9.4

9

Chapter 1 Getting Started

***<System_name>*******************CT-650**********************Version x.xx ***

DS1 Test Menu
User: maint11 Test: test234

Enter one of the following:

Abort DS1_Measure Report Restart Inject_Errors
Loopback Monitor Select_Test Exit
_______________________________________________________________________________
Batch_Command Daytime DCS_Direct Delete_Log Disconnect
Email Error_Rate Examine_Log Help Information
Line_Coding List_Files Log_Errors Main_Exit Password
Port_Connect Printer Prog_Loop Record Screen_Refresh
Self_Test Text_Editor User_Pattern Version Who
Write Yellow_Alarm !(History)
===============================================================================
DS1_TST>

-------------------------------------------------------------------------------­Test test234 : DTMF_LPBK Loop Up SEL: Sent CON: Sent

Test name

Loop type

Loop direction

Circuit side and loop status

Understanding the CT-650 screens

Loopback status

line

The loopback status line appears after starting a loopback test
(Figure 8).

Figure 8 Loopback status line

For definitions of the fields appearing in the loopback status line, see

10 CT-650 Command-Line Reference Guide Release 9.4

page 170.

Chapter 1 Getting Started

*** ct14 **************************CT-650**********************Version 7.4V1****

RTU ALARMS:

SHELF RTU SYSTEM/RTU RTU SIGNAL
NO. NO. NAME STATUS MISSING

----- --- -------------------- ---------- -------
1 4A 1st_dcs INUSE N
1 4B 1st_dcs INUSE N
1 6A N/A NOT CONFIG N/A
1 6B N/A NOT CONFIG N/A
1 9A 2nd_dcs INUSE N
1 9B 2nd_dcs INUSE N
1 11A N/A NOT CONFIG N/A
1 11B N/A NOT CONFIG N/A
1 12A 3rd_dcs INUSE N
1 12B 3rd_dcs INUSE N
1 14A N/A NOT CONFIG N/A

---------- Type any character for next screen ----------

Entering commands

Information

screens

Information screens, such as the one in Figure 9, display a variety of
system and test information. You can open the information screens
with the Information command, which is described starting on

page 26.

Figure 9 Information screen

Entering commands

The general form of a command is

command_name parameter1 parameter2 ... parameter(n)

Each time you press Space, the CT-650 prompts you with the next
parameter to type as well as the available values. Se e Appendix B for
a detailed listing and definitions of all parameters.

If you press Enter before entering all the parameter values required for
a command, the CT-650 automatically uses the available default
value.

CT-650 Command-Line Reference Guide Release 9.4

11

Chapter 1 Getting Started

Entering commands

Editing

commands

Abbreviating

command entry

Control

characters

If you need to make changes to a command, press Backspace or
Delete (depending on your terminal). You can also retype and edit

previous commands by using the history command; see page 37 for
details.

You can enter commands by typing enough characters required to
uniquely identify the intended command or parameter value. For
example, the following commands all execute the Daytime
command:

MAIN> da
MAIN> day
MAIN> daytime

If you type d and press Enter, the CT-650 displays an error message
Ambiguous command entered, because the commands Daytime,
DCS_Direct and Delete_Log all start with the letter d.

Table 3 lists the available control characters to quickly type commands

from specific screens.

Table 3 Control characters

Key Function

Ctrl+D Execute the last command entered.
Ctrl+P Displays the last command entered but does not execute it.
Ctrl+R Restarts a test. Available from the test results screen.
Ctrl+I Injects a single bit error into the transmitted signal. Avail-

able from the test results screen.

Ctrl+O Selects the other side (selected or connected) of a dual

FAD test. Available from the test results screen.

12 CT-650 Command-Line Reference Guide Release 9.4

Depending on the installed options, additional hotkeys are available.

NOTE:

If you use the CT-650 through an X.25 network, the Ctrl key may
not function properly. In these environments, use the period . for
the Ctrl key.

Sample test procedure

A typical test scenario requires the following steps:

1 Initiate a test by issuing a Monitor command.
2 Split the circuit.
3 Loop up the circuit to start recording results.
4 Measure the test results
5 Loop down the circuit to release it.

Chapter 1 Getting Started

Sample test procedure

6 Disconnect the test.
The following example shows how to test a DS3 circuit through a 3/3

DCS.

CT-650 Command-Line Reference Guide Release 9.4

13

Chapter 1 Getting Started

*** ct14 **************************CT-650**********************Version 7.4V1****

DS3 Menu
User: maint11 Test:

Enter one of the following:

Exit Monitor
_______________________________________________________________________________
Batch_Command Daytime DCS_Direct Delete_Log Email
Examine_Log Help Information Files_List Main_Exit
Password Port_Connect Printer Record Screen_Refresh
Self_Test TAP_Loopback Text_Editor Version Who
Write !(History)

===============================================================================
DS3> _

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

*** ct14 **************************CT-650**********************Version 7.4V1****

DS3 Menu
User: maint11 Test:

Enter the system/DT3 name:

1st_dcs 2nd_dcs 3rd_dcs

===============================================================================
DS3>monitor _

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

Sample test procedure

Step 1: Initiate the

test

1 From the main menu, type DS3. The DS3 Menu appears.

2 Type Monitor and press Space. The first command screen

appears, listing the names of available 3/3 DCS devices.

14 CT-650 Command-Line Reference Guide Release 9.4

Chapter 1 Getting Started

*** ct14 **************************CT-650**********************Version 7.4V1****

DS3 Menu
User: maint11 Test:

Enter the digroup number to be monitored:

===============================================================================
DS3>monitor 1st_dcs _

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

*** ct14 **************************CT-650**********************Version 7.4V1****

DS3 Menu
User: maint11 Test:

Enter the test name:

================================================================================
DS3>monitor 1st_dcs 25 _

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

Sample test procedure

3 Type the name of your 3/3 device and press Space. The next

command screen prompts for the digroup.

4 Type an appropriate digroup number and press Space. The next

command screen asks for a test name.

CT-650 Command-Line Reference Guide Release 9.4

15

Chapter 1 Getting Started

*** ct14 **************************CT-650**********************Version 7.4V1****

DS3 Menu
User: maint11 Test:

Select or enter a log file name or hit return for the default log file:

maint11 test234 3test

===============================================================================
DS3>monitor 1st_dcs 25 1test _

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

*** ct14 ****************************CT-650********************Version 7.4V1****

DS3 Menu
User: maint11 Test:

Enter one of the following or hit return for the default:

Auto C-Bit M-13 Unframed

===============================================================================
MAIN>ds3
DS3>monitor 1st_dcs 25 1test 1test _

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

Sample test procedure

5 Type a name for the test and press Space. The next screen

prompts for a log file name.

6 Type a name for the log file, and then press Space. The next

screen prompts for the framing mode.

16 CT-650 Command-Line Reference Guide Release 9.4

Chapter 1 Getting Started

*** ct14 **************************CT-650**********************Version 7.4V1****

DS3 Menu
User: maint11 Test:

Enter <return> for the default test length of Continuous,

Continuous
or
the test duration (format is <hhh-mm-ss>)

================================================================================
DS3>monitor 1st_dcs 25 1test 1test auto _

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

*** ct14 **************************CT-650**********************Version 7.4V1****

DS3 Menu
User: maint11 Test:

Press <return> to enter command.

================================================================================
DS3>monitor 1st_dcs 25 1test 1test auto 24-30-00 _

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

Sample test procedure

7 Type auto and press Space to use automatic framing. The next

screen prompts for the test’s duration.

8 Type 24-30-00 and press Space. The next screen prompts you

to press Enter, indicating the command is fully specified.

CT-650 Command-Line Reference Guide Release 9.4

17

Chapter 1 Getting Started

*** ct14 **************************CT-650**********************Version 7.4V1****

DS3 MONITOR:

System/RTU Name = 1st_dcs
Test Name = 1test
Digroup = 25
Test Port Type = Dual DS3 Fad
Framing = Auto
Test Duration = 24-30-00
Log File = 1test.log
Do you want to EXECUTE this command? (Y/N) _

===============================================================================
DS3>monitor 1st_dcs 25 1test 1test auto 24-30-00

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

*** ct14 **************************CT-650**********************Version 7.4V1****

TEST: 1test DG: 25 SIG SRC: EXT RTU: 1_4A
SYS: 1st_dcs TP: 4 TYPE: MONITOR SIDE: SEL
TX FRM: CBIT TX PAT: LIVE E. TIME: 00:00:23
RX FRM: CBIT TIM SRC: INTERNAL
SYNC STATUS: DS3 FRAME SYNC SPLIT TYPE: N/A
SUMMARY:

ALL RESULTS OK

-------------------------------------------------------------------------------­<L-Logic> <B-BPV> <F-Frame> <P-Parity> <C-CBit> <S-Signal> <T-Time>
<I-Line Status> <Q-to quit> <^O-Other side>

Sample test procedure

9 Press Enter. The confirmation screen lists the parameters

entered, and prompts for a confirmation to proceed with the test

10 T ype your confirmation by pressing Y and Enter. The CT-650 runs

the test, and then displays summary results.

11 To view other test results, press the hotkeys listed at the bottom of

the screen.

18 CT-650 Command-Line Reference Guide Release 9.4

Chapter 1 Getting Started

*** ct14 **************************CT-650**********************Version 7.4V1****

DS3 Monitor Menu
User: maint11 Test: 1test

Enter one of the following:

DS3_Split Abort Report Restart Monitor
Select_Test Exit
_______________________________________________________________________________
Batch_Command Choose Daytime DCS_Direct Delete_Log
Email Examine_Log Files_List Help Information
Main_Exit OS_Command Password Port_Connect Printer
Record Release Screen_Refresh Self_Test TAP_Loopback
Text_Editor Version View_Results Who Write
!(History)

===============================================================================
DS3_MON> _

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

Sample test procedure

12 To display the DS3 Monitor menu, press Q. The DS3 Monitor

menu appears. The test continues to run.

Step 2: Split the

circuit

At the DS3_MON> prompt, type the command DS3_Split. This splits
the circuit using default values for the split mode and signal flow. Type
your confirmation by pressing Y.

Step 3: Loop up

the circuit

At the DS3_TST> prompt, type the command Loopback Connected
DS3 up FEAC. This loops the connected side of the circuit and

prepares it for measuring test results.

Step 4: Measure

test results

Step 5: Loop

down the circuit

At the DS3_TST> prompt, type the command DS3_Measure
Connected Unmuxed 1010 continuous. This measures the

response from the connected side of the circuit to an alte rnating 1010
test pattern. Since you used the continuous value for test duration,
the test runs until you disconnect it.

At the DS3_TST> prompt, type the command Loopback Connected
DS3 down. This restores the circuit to its original state before it was
looped up.

CT-650 Command-Line Reference Guide Release 9.4

19

Chapter 1 Getting Started

Logging off

Step 6:

Disconnect the

Logging off

At the DS3_TST> prompt, type the command Disconnect
Release_Test No. This disconnects the test from the circuit.

test

Be sure to log off the CT-650 when you are not performing any tests
or before leaving the terminal unattended. This precaution prevents
unauthorized access to the CT-650.

To log off the CT-650
1 Stop any tests using the Disconnect command (see page 38).
2 Type Main_Exit. The Main Menu appears.
3 Type Logout.

The CT-650 terminates your session, and the system prompt appears.

20 CT-650 Command-Line Reference Guide Release 9.4

Chapter2

Auxiliary and Common
Commands

2

There are many commands that do not pertain directly to testing.
Auxiliary commands provide information on the test environment, as
well as access to the operating system and connected DCS units.
Common commands provide additional functions after you initiate a
test. The definitions for command parameters appear in Appendix B
starting on page 173. Topics discussed in this chapter are as follows:

– “Auxiliary commands” on page 22
– “Common test commands” on page 37

CT-650 Command-Line Reference Guide Release 9.4 21

Chapter 2 Auxiliary and Common Commands

Auxiliary commands

Auxiliary commands

This section describes the auxiliary commands.

Batch_Command

Syntax

Remarks

Choose

Syntax

Executes a batch file. You can use a batch file to automate testing or
other repetitive processes.

Batch_Command <file_name> <directory> <test_mode>
<

digroup_side> <channel>

–See Chapter 8 for more information about the commands avail-

able for use in batch.

–Use the Files_List command (page 25) to display a list of

batch files.

–See page 32 for information on recording commands into a batch

file.

Identifies and activates a resource to be allocated for the next test.

Choose Rtu <shelf>_<slot><side>

Choose Talk/Listen

Choose Cancel
Cancels any associations made with previous Choose commands.

Remarks

22 CT-650 Command-Line Reference Guide Release 9.4

– Test commands, such as Monitor, use the resources specified

by the Choose command.
– You must perform the next command immediately after Choose.
– You can issue several consecutive Choose commands to specify

more than one resource, and the next Monitor command will use

all those resources.

Chapter 2 Auxiliary and Common Commands

Auxiliary commands

Example

Daytime

Syntax

DCS_Direct

Syntax

Remarks

The following commands allocate the RTU in shelf 1, slot 10, side A,
to the subsequent monitor test.

Choose RTU 1_10A

Monitor CT14 11 1 mytest mylog auto continuous

Displays the current system date and time.

Daytime

Issues a command to an attached DCS.

DCS_Direct <system_name> <dcs_command>

– Refer to your DCS operating manuals for information on issuing

commands to a DCS.

– If a command requires multiple parameters, press Space after

each parameter.

Example

Delete_Log

Syntax

The following command queries a Cisco 15454 DCS for the equipment
list.

dcs_direct CISCO15454 rtrv-eqpt::slot-all:@;

Deletes log files.

Delete_Log <log_file>

CT-650 Command-Line Reference Guide Release 9.4

23

Chapter 2 Auxiliary and Common Commands

Auxiliary commands

Remarks

Example

Email

Syntax

– If you do not specify a log_file, the CT-650 deletes all the log

files created under your account ID.
– If you want to delete a log file associated with an active test, first

terminate the test by issuing the Disconnect command.

The following procedure deletes the log file named root.

1 At the prompt, type Delete_Log root.
2 Press Y to confirm.

Sends and receives electronic mail to and from any user account.

Email Read

Displays the contents of the most recent email message and displays
a prompt for additional commands. For help on reading email, type ?
at the prompt.

Email Send <

user_name>

Sends a message to <

user_name>. When the email message screen

appears, type in the desired message. When finishe d, press Enter to

Remarks

place the cursor on a blank line. Press .

– To send an interactive message to another user, use the Write

+Enter to send the message.

command (page 36).
– To find a list of users available to receive emails, use the Who

command (page 36).

Error_Rate

Sets the rate for the bit errors and BPVs injected with the
Inject_Errors command (page 28). This command overrides the
default error rate.

Syntax

Error_Rate <1E-y>

24 CT-650 Command-Line Reference Guide Release 9.4

Chapter 2 Auxiliary and Common Commands

Auxiliary commands

Remarks

Examine_Log

Syntax

Remarks

– You can specify an error rate from 1E-2 to 1E-9.
– You can view the default error rate by typing the command

Information Configure Defaults <

circuit_type>.

– This command is available only after successfully starting a

Split command with local loopback.

Displays a user’s log file.

Examine_Log <log_file>

– If you do not specify log_file, the CT-650 displays the system

log file.

–Use the Files_List command (page 25) to list all files within a

user account, including the log files.

– When the CT-650 displays a log file, function keys appear at the

bottom of the screen. You can use these function keys to navigate
through the file.

Exit

Remark

Files_List

Syntax

Remarks

Exit

Returns you to the previous menu.

Use the Main_Exit command (page 30) to return to the main menu.

Lists all files in the current directory or in a specified directory.

Files_List <directory>

– If you don’t specify directory, the CT-650 displays files in the

current directory.

CT-650 Command-Line Reference Guide Release 9.4

25

Chapter 2 Auxiliary and Common Commands

Auxiliary commands

– The batch files for the user account are found in the /ttc/

<

user_name> directory. Log files are listed under the /ttc/

<

user_name>/log directory.

Help

Syntax

Remarks

Information

Displays information on a command.

Help <command_name>

If you don’t specify command_name, the CT-650 displays the main
help screen.

Displays information on account names, alarms, CT-650 configura­tion, communication ports, and status of active tests and slots.

Information Accounts

Displays list of user accounts. If you have supervisor access, the
CT-650 displays add itional information about password agin g and the
date the account was last modified.

Information Alarms Fans

Displays the status of system fans.

Information Alarms RTU

Displays the status of each configured RTU.

Information Configure Ports

Displays the communication configuration for each port.

Information Configure DCS <

transport_type>

Displays the current DCS configurations. transport_type defaults
to All.

26 CT-650 Command-Line Reference Guide Release 9.4

Chapter 2 Auxiliary and Common Commands

Auxiliary commands

Information Configure RTU <

rtu_type>

Displays the configuration for the rtu_type.

Information Configure Defaults <

test_type>

Displays default parameter values for the specified test_type.

Information Configure Misc.

Displays various miscellaneous system parameters.

Information Configure Security

Displays settings for system security. Users with supervisor-level
access can modify the security settings.

Information Configure Trunk_Types

Displays on-hook and off-hook settings for each connected trunk.

Information Configure Answer_Seq

Displays the configured answer sequences for VF circuits.

Information Configure Dial_Seq

Displays the configured dial sequences for VF circuits.

Information CRS <System | Test_Name | User | All>

Displays degroomed/ungroomed cross-connect information for
Universal FAD and Shared FT1 tests.

Information Slots

Displays information about the type and status of cards in each slot,
and if the slot is available or configured.

Information Tests <System <
<

test_name> | User <user_name> | All>

CT-650 Command-Line Reference Guide Release 9.4

system_name> | Test_Name

27

Chapter 2 Auxiliary and Common Commands

Auxiliary commands

Displays information about tests, including the test state and RTU for
each side of a dual FAD test.

Inject_Errors

Syntax

Remarks

Information Talk/Listen <System <
Test_Name <

test_name> | User <user_name> | All>

system_name> |

Displays all current talk/listen settings associated with a specified
system, test name, user, or all tests.

Information Taps <System <
<

test_name> | User <user_name> | All>

system_name> | Test_Name

Displays information about the test acces s por ts associ at ed with a
specified system.

Injects bit or BPV errors into a tested circuit.

Inject_Errors <digroup_side> <error_type>
<

test_duration>

– This command is available only after successfully starting a

Measure command.
– test_duration defaults to Single.

Example

The following procedure configures and injects bit errors at a 1E-3
error rate from the DS3 test menu.

1 At the DS3 menu prompt, type Error_Rate 1E-3.

The DS3 test menu appears.

2 Type inject_errors both bit continuous
3 Confirm executing the test by pressing Y. The CT-650 continu-

ously injects bit errors at a rate of 10E

-3

.

28 CT-650 Command-Line Reference Guide Release 9.4

Chapter 2 Auxiliary and Common Commands

Auxiliary commands

Line_Coding

Syntax

Remarks

Logout

Syntax

Remark

Loopback

Sets the line coding of the transmitted signal.

Line_Coding {AMI | B8ZS}

– Use this command to override the default line coding for an indi-

vidual test.

–Use the Information Configure Default command to view

the default line coding.

Logs off the system and returns the system prompt.

Logout

Before logging out, be sure to terminate any existing tests using the
Disconnect command (page 38).

Transmits latching loop-up and loop-down codes.

Syntax

Remark

Loopback <digroup_side> Up|Down <loop_code>
num_repeaters <

Loopback <
<

channel>

channel>

digroup_side> DS1 {Up Down} <ds1_device>

Sends the DS1 loop-up or loop-down codes (in-b and or FEAC) for the
desired ds1_device and channel on the chosen digroup side.

Loopback <

digroup_side> DS3 {Up Down} <ds3_device>

Sends the DS3 FEAC loop-up or loop-down codes on the chosen
digroup side.

– This command is available only after executing a Measure

command.

CT-650 Command-Line Reference Guide Release 9.4

29

Chapter 2 Auxiliary and Common Commands

Auxiliary commands

– The parameters num_repeaters and channel are required

depending on the type of circuit and loop code.
– The last two forms of the command are for DS3 tests.
– After executing a loop up or loop down, issue a Restart

command to re-initiate the Measure test.
– For the syntax to loop VF circuits, see “Loopback” on page 68.
– The loop status indicator, appearing on the status line at the

bottom of the screen, gives information on the state of a loopback

operation. For information on reading the status line, see

page 170.

Main_Exit

Syntax

OS_Command

Syntax

Password

Syntax

Remark

Displays the main menu.

Main_Exit

Issues a UNIX (Solaris) shell-level operating system command.

OS_Command <UNIX_shell_level_command>

Changes the user’s current password.

Password

– Passwords must include at least six characters with at least one

digit and two alphabetical characters.
– Passwords are case sensitive.

30 CT-650 Command-Line Reference Guide Release 9.4

Chapter 2 Auxiliary and Common Commands

Auxiliary commands

Port_Connect

Syntax

Remarks

Printer

Syntax

Establishes a link between any unconfigured TTY comm u n ic at ion s
port and your current TTY communications port. This command
enables communication with a remote test device, such as a T -BERD

310.

Port_Connect <port_number> <data_rate> <parity>
<

data_bits>

– Press ~+.+Ctrl+C to terminate the port connection.
– You can view the configuration of a port by issuing the Informa-

tion Configure Ports command (see page 26).

– The data rate, parity, and data bits default to 9600, none, and 8,

respectively.

Star ts or stops sending the current active log file to the printer.

Printer {On Off}

Prog_Loop

Syntax

Remarks

Sets a programmable 3- to 8-bit in-band loop-up and loop-down
codes.

Prog_Loop <loop_up_code> <loop_down_code>

– This command is available only from a test menu.
– Type the bit pattern as ones and zeros.
– The CT-650 transmits the loop code left to right after entering a

Loopback command.

– You can set default loop-up and loop-down codes using the

Configure Defaults DS3 or Configure Defaults DS1/
FT1 commands.

CT-650 Command-Line Reference Guide Release 9.4

31

Chapter 2 Auxiliary and Common Commands

Auxiliary commands

Example

Record

Syntax

Remarks

Example

The following command defines a loop-up code of 1001 and a loop­down code of 1000.

Prog_Loop 1001 1000

Starts or stops recor ding co mm a nd s to a log file.

Record On <file_name>

Record Off

– You can edit a log file with the UNIX vi text editor.
– When you type Record Off, the CT -650 asks if you want to save

a copy of the batch file in the common system directory. This

allows any user to execute the batch file.
– If you record to an existing file, the CT-650 appends the subse-

quent commands to those already saved in the file.

The following procedure records a command sequence into a batch
file named mon33.

1 Type Record On mon33.

The following message appears: Keyboard recording is

ON. Commands are recorded to file mon33.

2 Press any key to return to the Main Menu.
3 Type a co mmand to be recorded.
4 Type Record Off, and press Enter.
5 At the prompt, press Y to save the batc h file in a com m o n dir ec-

tory.
6 Press any key to return to the Main Menu.

The message appears Keyboard recording is OFF.

32 CT-650 Command-Line Reference Guide Release 9.4

Chapter 2 Auxiliary and Common Commands

Auxiliary commands

Release

Syntax

Remarks

Restart

Syntax

Remark

Releases one or all currently running tests.

Release <user_name> All|<test_name> Yes|No

– user_name defaults to your logon ID.
– If you type Yes, the CT-650 releases test s even if the DCS denies

the operation. If you type No, the test continues running even if the
DCS denies the operation.

– Supervisors can release all tests for any user as long as th e corre-

sponding DCS is still online.

Restart the current foreground test on the specified digro up.

Restart <digroup_side>

This command clears all counters, test results, and restarts the test
timer.

Screen_Refresh

Syntax

Self_Test

Syntax

Remarks

Refreshes the terminal screen.

Screen_Refresh

Initiates a selftest on a specified RTU and saves the results in a spec­ified log file.

Self_Test <rtu_number> <log_file>

– This command places the RTU into an internal loopback with a

specified framing format and pattern, and then displays a results
screen. The test runs for 2 minutes, but can be ab or te d by
pressing Q.

CT-650 Command-Line Reference Guide Release 9.4

33

Chapter 2 Auxiliary and Common Commands

Auxiliary commands

– When you issue this command, the CT-650 aborts any tests

started with the Monitor or Measure commands. After the self-

test completes, you can select the aborted test with the

Select_Test command and then issue the Restart command.
– The CT-650 stores the selftest log file under the user’s account.

Example

Supervisor

Syntax

Remark

TAP_Loopback

Syntax

The following procedure performs a selftest on an RTU at location
1_3A, and stores the resulting log file in test4.log.

1 Type Self_Test 1_3A test4.log.
2 Confirm the selftest by pressing Y.

Displays commands available to users with supervisor-level access.
This command appears only when you sign on with supervisor privi­leges.

Supervisor

See Chapter 9 for detailed information about the supervisor
commands.

Tests the interface between an idle RTU and DCS FAD.

TAP_Loopback <system_name> <tad/fad_number> <fad_type>
<

test_name> <log_file>

This syntax is available for DS3, DS1, and FT1 circuits.

TAP_Loopback <
<

test_name> <log_file>

system_name> <tad_number> <tap_number>

This syntax is available for DS0 circuits.

34 CT-650 Command-Line Reference Guide Release 9.4

Chapter 2 Auxiliary and Common Commands

Auxiliary commands

Remarks

Example

Text_Editor

–The fad_type parameter is available only for DCSs configured

for single or dual FAD testing.
– Release the loopback with the Disconnect command.
– Some DCSs require a port to be provisioned as out-of-service

when performing a TAP loopback. Refer to the DCS documenta-

tion to verify this requirement.

Test FAD number 1 on the DCS names 3ECS3. Assig n the name
test123 to the test, and save the results in a log file called test123.

1 Type tap_loopback 3ecs3 1 test123 test123.
2 Confirm the test by pressing Y.

The TAP loopback is established; the DS3 Test Menu appears.

3 Type DS3_Measure to test the FAD.
4 Type Disconnect to release the loopback.

Runs the text editor and opens a file with the indicated file name.

Syntax

Remark

User_Pattern

Syntax

Remarks

Text_Editor <file_name>

The CT-650 text editor operates the same as the standard UNIX vi
editor.

Defines a user-programmable 3- to 24-bit test pattern.

User_Pattern {User1 | User2} <test_pattern>

– This command is available only after splitting a circuit.
– Type the test_pattern as a series of ones and zeros.
– You can use the test pattern with the DS1_Measure command.

CT-650 Command-Line Reference Guide Release 9.4

35

Chapter 2 Auxiliary and Common Commands

Auxiliary commands

– To display the default user-programmable test patterns for

different circuits, use the command Information Configure
Default.

Example

Version

Syntax

View_Results

Syntax

Remark

Who

Define a user1 test pattern equal to 28-1.

User_Pattern User1 1111111

Displays the version of the CT-650 software and Solaris operating
system installed on your system.

Version

Displays results of a currently running test.

View_Results <logon_id> <test_name>

logon_id defaults to your own logon ID, and test_name defaults to

the last test selected with the Select_Test command.

Lists the currently logged on users, and the date and time the user
logged on.

Syntax

Remarks

Write

Syntax

36 CT-650 Command-Line Reference Guide Release 9.4

Who

This command does not list NetAnalyst users.

Sends a message to another user.

Write <user_name>

Chapter 2 Auxiliary and Common Commands

Common test commands

Remarks

! (History)

Syntax

Remark

– The message appears on the target user’s prompt line.
– A message is transmitted each time you press Enter.
– To end the session, press Ctrl+n.
– You can also send messages using the Email command (see

page 24).

Displays or executes previously entered commands.

! <command_digit>

Executes the command associated with the command_digit. If you
do not specify command_digit, the CT-650 displays a list of the last
20 commands you entered.

<

digroup_side>!!

Executes the last command entered.

If you press Esc after typing the command_digit, th e CT-650 displays
the command so you can edit it.

Common test commands

This section describes common test commands. These commands
are available after you start a test.

Abort

Syntax

Remarks

Terminates the current foreground test.

Abort <digroup_side>

– The parameter digroup_side is required only for dual FAD

tests.

CT-650 Command-Line Reference Guide Release 9.4

37

Chapter 2 Auxiliary and Common Commands

Common test commands

– After execution, the connected RTU remains allocated and the

DCS connection remains unchanged.

– Y ou can view the test results accumulated until issuing the Abort

command. The results are available until you Restart the test,
start a new Measure test, or Disconnect the circuit.

– The transmitter continues to send the pattern selected for the

Measure command.

Disconnect

Syntax

Remarks

Disconnects a circuit under test, and removes an existing split.

Disconnect All <dcs_disconnect>

Releases all tests performed under the current user account.

Disconnect System <

system_name> <dcs_disconnect>

Releases all of the tests running on the indicated system_name.

Disconnect Test_Name <

test_name> <dcs_disconnect>

Releases the test identified by test_name.

Disconnect {Release_Test To_Monitor} <

dcs_disconnect>

Releases the foreground test. This form of the command is available
only from a test menu.

– If the circuit being disconnected is looped back, a warning

appears in the confirmation screen to indicate the loopback is still
present. When the circuit is disconnected, the circuit remains
looped back. Loop down the circuit before disconnecting.

– This command returns you to the monitor state or to the released

state (tells the DCS to release the tested circuit and reallocates
the RTUs). The RTU enters a disconnected state by transmitting a
framed idle signal or thru mode depending on the default idle
condition specified in the RTU configuration.

38 CT-650 Command-Line Reference Guide Release 9.4

Chapter 2 Auxiliary and Common Commands

Common test commands

Example

Report

Syntax

Remark

Select_T est

Syntax

Remark

The following procedure disconnects all tests that are currently
running:

1 At the command prompt, type Disconnect All.
2 Type Y to confirm disconnect

Displays results of a specified test.

Report <test_name>

test_name defaults to the current foreground test.

Brings a background test to the foreground.

Select_Test <test_name>

When you select a test, the CT-650 displays the commands available
for the test.

CT-650 Command-Line Reference Guide Release 9.4

39

Chapter 2 Auxiliary and Common Commands

Common test commands

40 CT-650 Command-Line Reference Guide Release 9.4

Chapter3

DS3 Test Commands

3

This chapter describes the commands available for testing DS3
circuits. These commands are available if you configure d a 3/3 or 3/1
DCS to the CT-650. The definitions for command parameters appear
in Appendix B starting on page 173. Topics discussed in this chapter
are as follows:

– “Description of DS3 test commands” on page 42

CT-650 Command-Line Reference Guide Release 9.4 41

Chapter 3 DS3 Test Commands

Description of DS3 test commands

Description of DS3 test commands

This section describes the DS3 test commands.

DS3_Measure

Syntax

Remarks

DS3_Split

Runs an intrusive test.

DS3_Measure <digroup_side> Muxed <ds1_framing_format>
<

test_pattern> <channel> <test_duration>

Transmits a multiplexed DS3 signal with a specified framing and test
pattern.

DS3_Measure <
<

test_duration>

Transmits an unmultiplexed DS3 test p attern.

– This command is available only after successfully starting a

DS3_Split.

– Defaults for the various parameters depend on the circuit under

test.

Establishes an intrusive connection between the monitored digroup
and the RTU.

digroup_side> Unmuxed <test_pattern>

Syntax

Remarks

42 CT-650 Command-Line Reference Guide Release 9.4

DS3_Split <split_mode> <signal_flow>

– This command is available only after executing a Monitor

command.

– For a listing of split modes, see the split_mode parameter on

page 183. For a listing of signal flows, see the signal_flow

parameter on page 182.

– The default values for split-mode and signal_flow depend on the

DCS configuration.

Chapter 3 DS3 Test Commands

Description of DS3 test commands

Example

FEAC_Alarm

Syntax

Example

Remark

The following command monitors a dual-F AD 3/3 DCS and perform an
EF split.

DS3_Split EF_Split Idle_Code

Selects the FEAC alarm to be transm itted in C-bit or multiplexed C-bit
framing mode. The alarm is only transmitted for the re qu ired d ur ation
of two seconds. FEAC alarms can only be transmitted wh en th e RTU
idle condition is set to IDLE.

FEAC_Alarm <digroup_side> <feac_message>

The following command transmits a DS3 FEAC alarm indicating
“service-affecting equipment failure” from the connected side.

feac_alarm connected ds3_sa_eq_fl

For a detailed listing of messages and alarm codes, see page 188.

Monitor

Syntax

Remarks

Starts a new test.

Monitor <system_name> <digroup_side> <test_name>
<

log_file> <fad_type> <framing_format> <test_duration>

– The parameter fad_type is available only for DCSs that are

configured for single and dual FAD test port types.
–If the framing_format is AUTO, the CT-650 automatically

synchronizes to the received signal framing. If one of the other

framing_formats is chosen, the transmitter is set up based on

the RTU idle condition default (Idle or Thru) and the specified

framing is saved to be implemented when the DS3_Split

command is issued.

CT-650 Command-Line Reference Guide Release 9.4

43

Chapter 3 DS3 Test Commands

Description of DS3 test commands

– Allocation of RTUs is performed as follows:

– If requesting a dual-F AD connection, the CT -650 allocate s both

DT3 Test Card RTUs to the DCS.

– If requesting a single-F AD connection is requested, the CT -650

allocates an available RTU to the specified DCS. If another
single-FAD test is running, the CT-650 attempts to allocate
both RTUs on the same DT3 test card before using additional
RTUs.

Example

Tx_X_Bit

Syntax

Remarks

Example

The following command monitors a DS3 signal from the 3ECS3
system, and digroup 1 11. The test name is test234 and log file log234.
The test uses auto framing and continuous test duration.

Monitor 3ecs3 111 test234 log234 auto continuous

Sets the transmission of X-bits from the RTU in the M13 or C-bit
framing modes.

Tx_X_Bit <digroup_side> <x_bits>

– If you do not specify x_bits, the CT-650 uses the value

appearing in the Information Configure Defaults DS3
screen.

– X-BITS can only be manipulated when the RTU idle condition is

set for IDLE mode.

The following command transmits X-bits that emulate the received
signal from the connected side.

Tx_x_bit connected emulate

44 CT-650 Command-Line Reference Guide Release 9.4

Chapter4

DS1 Test Commands

4

This chapter describes the commands available for testing DS1
circuits. These commands are available if you configure d a 3/1 or 1/0
DCS FAD connection. The definitions for command parameters
appear in Appendix B starting on page 173. Topics discussed in this
chapter are as follows:

– “Description of DS1 test commands” on page 46
– “Considerations for SLC-96 testing” on page 50

CT-650 Command-Line Reference Guide Release 9.4 45

Chapter 4 DS1 Test Commands

Description of DS1 test commands

Description of DS1 test commands

This section describes the DS1 test commands.

DI_Monitor

Syntax

Remark

Example

DS1_DI_Measure

Starts an intrusive drop and insert test.

DI_Monitor <system_name> <digroup_number> <channel>
<

test_name> <log_file> <fad_type> <framing_format>

<

test_duration>

The parameter fad_type is available only for DCS with single or dual
FAD cap ability.

The following command initiates a drop and insert test on a DS1 signal
from the DCS named 3ecs1, on digroup 1, and on channel 1. The test
name is test234, and results are stored in a log file called
maint1.log. The test requires automatic framing and runs continu­ously.

Monitor 3ecs1 1 1 test234 maint1.log auto continuous

Executes an intrusive test on the chosen side of the digroup being
tested.

Syntax

Remarks

46 CT-650 Command-Line Reference Guide Release 9.4

DS1_DI_Measure <digroup_side> <test_pattern_type>
<

test_pattern> <test_duration>

– This command is available only after executing a DS1_DI_Split

command.

– Not all test pattern types require a test_pattern parameter.

Chapter 4 DS1 Test Commands

Description of DS1 test commands

Example

DS1_DI_Split

Syntax

Remark

Example

DS1_Measure

The following command starts a cont inuous test on the connected side
of a DS1 line with a 2

23

-1 pseudorandom test pattern.

DS1_DI_Measure connected PRBS 2^23-1 continuous

Establishes an intrusive connection between the monit ored dig ro up
and a DT1 RTU using a specified signal flow.

DS1_DI_Split <signal_flow>

This command is available only after executing a DI_Monitor
command.

The following command performs a drop and insert split from a dual­FAD 3/1 DCS.

DS1_DI_Split idle_code

Executes an intrusive test on a specified digroup.

Syntax

Remarks

Example

DS1_Measure <digroup_side> <test_pattern_type>
<

test_pattern> <test_duration>

– This command is available only after executing a DS1_Split

command.
– Not all test_pattern_types require a test_pattern param-

eter.

The following command continuously tests the connected side of a
DS1 line with a 2

23

-1 test pattern.

Measure connected PRBS 2^23-1 continuous

CT-650 Command-Line Reference Guide Release 9.4

47

Chapter 4 DS1 Test Commands

Description of DS1 test commands

Check_

Pre-existing_Loop

Syntax

Remark

Example

DS1_Split

Syntax

Remarks

Detects a pre-existing loop in a T1 circuit.

Check_Pre-existing_Loop

This command is available only after executing a DS1_Split
command.

Check_Pre-existing_Loop

Establishes an intrusive connection between the monitored digroup
and an RTU.

DS1_Split <split_mode> <signal_flow>

– This command is available only after executing a Monitor or

DI_Monitor command.

– The defaults for split_mode and signal_flow depend on the

type of circuit and framing.

Example

Log_Errors

Syntax

48 CT-650 Command-Line Reference Guide Release 9.4

The following command performs an EF split using an idle-code signal
flow.

DS1_Split ef_split idle_code

Starts logging of errors detected during a test.

Log_Errors <log_bit_error_sec> <log_sev_bit_error_sec>
<

log_frame_error_sec> <log_frame_sev_error_sec>

Chapter 4 DS1 Test Commands

Description of DS1 test commands

Example

Remarks

Monitor

Syntax

The following command enables logging of test results for bit error
seconds and frame error seconds, but not severely errored seconds.

Log_Errors y n y n

–Use the Examine_Log command to review the logged results.
– The logged errors are in addition to logged results displayed by

the Information Configure Miscellaneous command

(see page 27).
–Use the Information Configure Default DS1 command to

verify the default settings for logging errors.

Starts a new test and allocates a new RTU to monitor a DS1 signal.

Monitor <system_name> <digroup_side> <trunk_type>
<

call_side> <test_name> <log_file> <fad_type>

<

framing_format> <test_duration>

Monitors a DS1 signal from a 3/1 or 1/0 DCS that has been config ured
for either a single- or dual-FAD test connection.

Remarks

Monitor <
<

framing_format> <test_duration>

system_name> <test_name> <log_file>

Monitors a DS1 signal from a DSX or direct connection source.

– If any framing other than SLC is chosen, the CT-650 tries to allo-

cate DT1 cards first, then DTU cards.
– If a dual-F AD connection is requested, the CT-650 allocates both

test card RTUs.
– If a single-FAD connection is requested, the CT-650 allocates an

available RTU. If you have another single-FAD test running, the

CT-650 attempts to allocate the other RTU on the same test card

before allocating additional RTUs.

CT-650 Command-Line Reference Guide Release 9.4

49

Chapter 4 DS1 Test Commands

Considerations for SLC-96 testing

Example

UF_Split

Syntax

Remark

Example

The following command initiates a DS1 monitor on the 3ECS1 DCS,
digroup number 111. The test name is test234, and the log file name
is maint1. The test uses automatic framing and continuous test dura­tion.

Monitor 3ecs1 111 test234 maint1 auto continuous

Establishes an intrusive split with the selected digroup.

UF_Split <system_name> <digroup_side> <regroom_npc>
<

framing_format> <test_name> <log_file>

The commands Information CRS and Information TAPS
screens provide cross-connect and system resource information. For
an example of cross-connect information, see “CRS” on page 116.

The following command initiates a universal FAD split on the unifad
system, digroup 44, using ESF framing format. The test name is test3,
and the log file name is log3.

UF_Split unifad 44 esf test3 log3

Yellow_Alarm

Syntax

Turns off or on the insertion of yellow alarms to the specified digroup
side.

Yellow_Alarm <digroup_side> Off|On

Considerations for SLC-96 testing

Below are special considerations for testing SLC-96 systems.
– SLC-96 is supported on the DTU card only.

– The DTU autoframes to SLC-96 DS1 circuits.

50 CT-650 Command-Line Reference Guide Release 9.4

Chapter 4 DS1 Test Commands

Considerations for SLC-96 testing

– DS0 testing of SLC-96 circuits is accomplished using either ESF

or D4 TAD framing.
– DS0 drop and insert VF or DDS is supported on SLC-96 circuits.
– SLC-96 Datalink is not supported.
– SLC-96 Signaling is not supported.
– Only DS1 in-band loopcodes are supported on SLC-96 framed

circuits.
– Any DTU with the default framing is set to SLC will not be allocated

for FT1 testing.
– If a CT-650 has both DTUs and DT1s, you must select SLC

framing in the Monitor command. This enables the CT-650 to

allocate the DTU for the test.

CT-650 Command-Line Reference Guide Release 9.4

51

Chapter 4 DS1 Test Commands

Considerations for SLC-96 testing

52 CT-650 Command-Line Reference Guide Release 9.4

Chapter5

FT1 Test Commands

5

This chapter describes the commands available for testing FT1
circuits. These commands are available if you configure d a 1/ 0 DCS
connection. The definitions for command parameters appear in

Appendix B star ting on page 173. T opics discussed in this chapte r are

as follows:
– “Description of FT1 test commands” on page 54

CT-650 Command-Line Reference Guide Release 9.4 53

Chapter 5 FT1 Test Commands

Description of FT1 test commands

Description of FT1 test commands

This section describes the FT1 commands.

DI_Monitor

Syntax

Remark

FT1_DI_Measure

Syntax

Remarks

Starts a new test to monitor and drop FT1 channels.

DI_Monitor <system_name> <digroup_side> <channel>
<

channel_type> <test_name> <log_file> <test_duration>

The default framing format configured for the RTU must match the
digroup framing format.

Starts an intrusive drop and insert test.

FT1_DI_Measure <digroup_side> <test_pattern_type>
<

test_pattern> <test_duration>

– This command is available only after executing a FT1_DI_Split.
– Not all test_pattern_types require a test_pattern param-

eter.

FT1_DI_Split

Syntax

Remark

54 CT-650 Command-Line Reference Guide Release 9.4

Establishes an EF split using the desired signal flow.

FT1_DI_Split <signal_flow>

This command is available only after executing a DI_Monitor.

Chapter 5 FT1 Test Commands

Description of FT1 test commands

FT1_Measure

Syntax

Remarks

FT1_Split

Syntax

Remark

Log_Errors

Executes an intrusive test on the chosen side of the FT1 FAD being
tested.

FT1_Measure <digroup_side> <test_pattern_type>
<

test_pattern> <test_duration>

– This command is available only after executing an FT1_Split.
– Not all test_pattern_types require a test_pattern param-

eter.

Establishes an EF split between the monitored digroup and a DTU.

FT1_Split <signal_flow>

This command is available only after executing a Monitor command.

Starts logging of errors detected during a test.

Syntax

Example

Remarks

Log_Errors <log_bit_error_sec> <log_sev_bit_err_sec>

The following command enables logging of test results for bit error
seconds and severe bit error seconds.

Log_Errors y y

– To review the logged results, use the Examine_Log command.
– The logged errors are in addition to logged results displayed by

the Information Configure Miscellaneous command

(see page 27).
– To verify the default settings for logging errors, use the Informa-

tion Configure Default DS1/FT1 command.

CT-650 Command-Line Reference Guide Release 9.4

55

Chapter 5 FT1 Test Commands

Description of FT1 test commands

Monitor

Syntax

Remark

Shared_Split

Syntax

Remark

UF_Split

Starts a monitor test.

Monitor <system_name> <digroup_side> <channel>
<

channel_type> <test_name> <log_file> <test_duration>

The default framing format configured for the RTU must match the
digroup framing format.

Establishes a shared split for individual DS0 channels within an FT1
circuit.

Shared_Split <system_name> <digroup_side> <channel>
<

channel_type> <test_name> <log_file>

For an explanation of shared splits, see the CT-650 User’s Guide.

Initiates a Universal FAD split.

Syntax

Remarks

UF_Split <system_name> <digroup_number> <regroom_npc>
<

framing_format> <test_name> <log_file>

UF_Split <
<

channel_type> <test_name> <log_file>

system_name> <digroup_number> <channel>

– For an explanation of splits, see the CT-650 User’s Guide.
– Ensure the RTU framing format matches the DCS FAD framing. If

the DCS is capable of multiple framing formats (D4, ESF, SLC or
Unframed), configure an RTU for each format. D4 and ESF
framing selections on the RTU configuration screen allow the idle
condition to be set to local loopback, all ones, or 0x1C. The
unframed selection only allows local loopback. (This may be an
issue with some DCS configurations, and may briefly generate
alarms).

56 CT-650 Command-Line Reference Guide Release 9.4

Chapter 5 FT1 Test Commands

Description of FT1 test commands

– The serial communications link between the CT-650 and DCS

must have administrative or supervisor rights given to the link to

allow degrooming and grooming of the digroup being tested.
– Establishing the UF_Split may take several minutes to complete

while the digroup is degroomed and regroomed for testing. The

process also includes storing the digroup configuration on the

CT-650. The disconnect process returns the digroup back to its

original configuration and/or mapping.

CT-650 Command-Line Reference Guide Release 9.4

57

Chapter 5 FT1 Test Commands

Description of FT1 test commands

58 CT-650 Command-Line Reference Guide Release 9.4

Chapter6

DS0 DDS Test
Commands

6

This chapter describes the commands available for testing DS0 DDS
circuits. These commands are available if you configure d a 1/ 0 DCS
with a TAD connection. The definitions for command parameters
appear in Appendix B starting on page 173. Y ou can also perfo rm drop
and insert tests on DS0 channels through a 3/1 DCS using a dual-F AD
test port. Topics discussed in this chapter are as follows:

– “Description of DDS test commands” on page 60

CT-650 Command-Line Reference Guide Release 9.4 59

Chapter 6 DS0 DDS Test Commands

Description of DDS test commands

Description of DDS test commands

This section describes the DS0 DDS commands.

DDS_DI_Measure

Syntax

Remarks

DDS_DI_Split

Syntax

Remarks

Executes an intrusive drop and insert test on the chosen side of the
circuit under test.

DDS_DI_Measure <digroup_side> <test_pattern_type>
<

test_pattern> <test_type> <test_duration>

– This command is available only after executing a DDS_DI_Split

command.

– Not all test_pattern_types require a test_pattern param-

eter.

Establishes an intrusive connection between th e monito red TAP from
a 3/1 DCS and a DTU RTU.

DDS_DI_Split <signal_flow>

– This command is available only after executing a DI_Monitor

command.

– This command establishes an EF split on the selected DS0

channel.

– An AB split is established across the DS1 signal with the selected

DS0 channel configured in an EF split.

DDS_Measure

Syntax

60 CT-650 Command-Line Reference Guide Release 9.4

Executes an intrusive test on the chosen side of the circuit under test.

DDS_Measure <digroup_side> <test_pattern_type>
<

test_pattern> <test_type> <test_duration>

Chapter 6 DS0 DDS Test Commands

Description of DDS test commands

Remarks

DDS_Split

Syntax

Remarks

DI_Monitor

– This command is available only after executing a DDS_Split

command.
– Not all test_pattern_types require a test_pattern param-

eter.

Establishes an intrusive connection between th e monito red TAP from
a 3/1 DCS and a DTU RTU.

DDS_Split <signal_flow>

– This command is available only after executing a DI_Monitor

command.
– After executing the command, the unit sends the correct Split

command to the 3/1 DCS to in affect establish an EF split on the

selected DS0 channel.

Starts a new monitor test on a DDS circuit.

Syntax

Remarks

DI_Monitor <system_name> <channelization_mode>
<

digroup_number> <channel> <channel_type> DS0A_subrate

<

test_name> <log_file> <test_duration> <tap>

– For TAD testing, set the DTU default framing to match the DCS

TAD framing or frame sync.
–The DS0A_subrate parameter is required only if channel_type

is DS0A.
–The tap parameter is required only for DCSs with TAD test ports.

CT-650 Command-Line Reference Guide Release 9.4

61

Chapter 6 DS0 DDS Test Commands

Description of DDS test commands

MJU

Syntax

Remarks

Example

Temporarily blocks, releases, or selects an MJU branch.

MJU <digroup_side>
<block_branch|release_branch|select_branch|restore_
mju> <

mju_branch>

– This command is available only after executing a

DDS_DI_Measure command.

–The Select option establishes a test path through the indicated

branch.
–The mju_branch parameter is not available with Restore_MJU.
– If multiple MJUs are cascaded, type consecutive MJU commands

to establish the testing path (see example in the next section).
–The Restore option restores all branches.
– Selecting a branch automatically blocks all other branches on the

MJU.

Figure 10 illustrates two cascading MJU branches, with Printer 1

connected to a secondary MJU device. To access Printer 1, you need
to type the following MJU commands:

MJU selected select_branch 2

62 CT-650 Command-Line Reference Guide Release 9.4

MJU selected select_branch 1

CT-650

1/0 DCS

MJU

MJU

MJU

MJU

Branch 2

Printer 1

Printer 4

Printer 3

Printer 2

Branch 1

Figure 10 Testing MJU branches

Chapter 6 DS0 DDS Test Commands

Description of DDS test commands

Monitor

Syntax

Remarks

Example

Starts a new monitor test on a DDS circuit.

Monitor <system_name> <channelization_mode>
<

digroup_number> <channel> <channel_type> DS0A_subrate

<

test_name> <log_file> <test_duration> <tap>

–The DS0A_subrate parameter is required only if channel_type

is DS0A.

–The tap parameter is required only for DCS with TAD test ports.

The following command monitors a DS0 signal on channel #10 from a
system called tlbs32, using digroup number 234, and a 64K subrate.
The test name is tst1, and the log file name is log1. The test runs
continuously, and uses test access port 6.

Monitor tlbs32 234 10 64k tst1 log1 continuous 6

CT-650 Command-Line Reference Guide Release 9.4

63

Chapter 6 DS0 DDS Test Commands

Description of DDS test commands

Log_Errors

Syntax

Example

Remarks

Starts the logging of errors detected during a test.

Log_Errors <log_bit_error_sec> <log_sev_bit_error_sec>

The following command enables logging of test results for severely bit
error seconds but not bit error seconds.

Log_Errors n y

– To review the logged results, use the Examine_Log command.
– The logged errors are in addition to logged results displayed by

the

Information Configure Miscellaneous command

(see page 27).
– To verify the default settings for logging errors, use the

tion Configure Default DS1

command.

Informa-

64 CT-650 Command-Line Reference Guide Release 9.4

Chapter7

DS0 VF Test Commands

7

This chapter describes the commands available for testing DS0 VF
circuits. These commands are available if you configured a 1/0 DCS
TAD connection. The definitions for command parameters appear in

Appendix B startin g on page 173. You can also perform drop and

insert testing on DS0 channels through a 3/1 DCS using a dual-FAD
test port.

NOTE:

Certain features and options, such as Dial Out and Answer Call,
depend on optional hardware features whic h ma y not be installed
on your CT-6 50. As a result, the syntax described here may differ

slightly from that displayed by your CT-650.
Topics discussed in this chapter are as follows:
– “Trunk types and seizure sequences” on page 66

– “Description of VF test commands” on page 66

CT-650 Command-Line Reference Guide Release 9.4 65

Chapter 7 DS0 VF Test Commands

Trunk types and seizure sequences

Trunk types and seizure sequences

Traffic on VF circuits starts with a seizure, which is an attempt to
request an individual circuit. When a telephone goes off-hook, it actu­ally sends a seizure sequence to the central office, where special
equipment receives the seizure sequence and allocates a circuit as
required.

There are various protocols for seizure, depending on the type of
circuit. The standard sequence is delay dial, which is the seq uence
used between a telephone and the central office tha t services the
phone.

Foreign exchange offices (FXO) use a different type of sequence. An
FXO provides service to a phone that is not in its normal service area.
For example, a company in the 212 area code (New York, NY) can
have an FXO in the 202 area code (Washington, DC). This enab les
local calls between Washington and New York.

Another sequence is used for subscriber loop carriers (SLC). These
carriers provide service to more subscribers in a geographical area
than can actually be supported by the existing cable. Under SLC, more
than one subscriber can use the same VF channel.

For a complete list of seizure sequences for answering and dialing
calls on standard, FXO and SLC VF circuits, see page 181.

Description of VF test commands

The following sections describe the DS0 VF test commands.

Answer_Call

Syntax

66 CT-650 Command-Line Reference Guide Release 9.4

Transmits a series of answer call sequences over the channel selected
with the last
switch or PBX-to-switch testing.

Answer_Call <digroup_side> <seizure_type>
<

number_of_phone_digits> <answer_sequence>

<

number_dialed> <seizure_type_parameter>

Monitor command. The command enables switch-to-

Chapter 7 DS0 VF Test Commands

Description of VF test commands

Remarks

DI_Monitor

Syntax

– This command is available only after executing a VF_DI_Split

command.

– This command is available only if your CT-650 supports the

enhanced signaling feature.

– For a discussion of seizure types, see page 66.

Start s a new test and allo cates a new R TU to monitor a DS0 sign al for
errors.

DI_Monitor <system_name> <channelization_mode>
<

digroup_number> <channel>|Scan <test_type> <test_name>

<

log_file> <test_duration>

Use this syntax for a multifrequency drop and insert monitor of a VF
channel from a 3/1 DCS.

DI_Monitor <system_name> <channelization_mode>
<

digroup_number> <channel>|Scan <trunk_type>

<

digroup_side> <disconnect_timeout> <offhook_timeout>

<

test_name> <log_file> <test_duration>

Use this syntax for a signaling drop and insert monitor of a VF chann el
from a 3/1 DCS.

Dial_Out

Syntax

Transmits a series of digits or a telephone number over the selected
channel, and enables switch-to-switch or PBX-to-switch testing.

Dial_Out <digroup_side> <seizure_type> Dial_Pulse
<

number_dialed> <dial_sequence> <pulse_per_second>

<

percent_break> <digroup_side>

Use this syntax for pulse dialing.

Dial_Out <digroup_side> <seizure_type>
{DTMF|Multi_Freq} <
<

digit_duration> <interdigit_delay> <digroup_side>

number_dialed> <dial_sequence>

Use this syntax for touch-tone dialing.

CT-650 Command-Line Reference Guide Release 9.4

67

Chapter 7 DS0 VF Test Commands

Description of VF test commands

Remarks

Hangup

Syntax

Remarks

Listen

Syntax

Remarks

– This command is available if the Signaling/VF Option is installed.
– For a discussion of seizure types, see page 66.

Releases a connection established with the Dial_Out command.

Hangup <digroup_side>

– This command appears after attempting a call or connection.
– This command is available if the Signaling Op tion is in stalled, and

applies only to drop and insert mode.

Enables the RTU to call a telephone number and estab lish a connec­tion. This feature enables you to remotely listen to a VF circuit.

Listen <phone_#>

– This command is available only after executing a DI_Monitor

command.
– An RTU performing TAD testing can listen to one source at a time.
– An RTU performing drop and insert testin g can listen to one

source, and each source must be wired to make separate calls.

Therefore, you can listen to either RTU with one phone, or both

RTUs on two phones.

Loopback

Transmits loop-up and loop-down tones on the chosen side of the
circuit.

Syntax

68 CT-650 Command-Line Reference Guide Release 9.4

Loopback <digroup_side> DTMF_Loopback <digit_string>
<

low_freq> <upper_freq> <low_output_level>

<

high_output_level> <tone_time>

Chapter 7 DS0 VF Test Commands

Description of VF test commands

Remarks

Monitor

Loopback <
<

tone_level> <tone_time_period>

Loopback <

digroup_side> User_Tone <tone_frequency>

digroup_side> VF Up|Down <loop_time>

–The parameters low_freq, upper_freq, low_output_level,

and

high_output_level are required only if digit_string

is

U (user defined).

– Compatible VF equipment loop up when the tone is initially

detected and loop down when the tone is detected a second time.

– After executing a loop up or loop down,

Restart the test to re-

initialize the measure test.

– To perform a loopback test, loopback the circuit first wi th the

Loopback command, then configure the test signal with the
VF_Measure command. To release the test, loopdown the circuit,

then disconnect the test.

– The choice of tones with the

DTMF_Loopback or User_Tone

parameters depends on the type of equipment at the other end of
the circuit and the type of events you wish to have it generate.

Starts a new test and allocates a new RTU to monitor a DS0 signal.

Syntax

Remark

Monitor <system_name> <digroup_number> <channel>
<

test_type> <test_name> <log_file> <test_duration> <tap>

Use this syntax for a multifrequency monitor of a VF channel from a
1/0 DCS.

Monitor <system_name> <digroup_number> <channel>
<

test_type> <trunk_type> <digroup_side> <test_name>

<

log_file> <test_duration> <tap>

Use this syntax for a signaling monitor of a VF channel from a 1/0
DCS.

The tap parameter is required only for DCS with TAD test ports.

CT-650 Command-Line Reference Guide Release 9.4

69

Chapter 7 DS0 VF Test Commands

Description of VF test commands

Talk/Listen

Syntax

Remarks

Example

Instructs the RTU to route an incoming signal from a phone to the
circuit under test.

Talk/Listen <digroup_side>

– Use this command to communicate with a person at the other end

of the circuit.
– Each end of the circuit can have any device with a speaker or

microphone, such as a telephone or another test device.
– The parameter

digroup_side is required for drop and insert

testing.
–

Talk/Listen is only available after a executing a Measure and

Listen.

–

Measure, Dial_Out, or Loopback determines the Talk/

Listen

–

Measure, Dial_Out, or Loopback reverts a Talk/Listen

back to a

receiver side (TAD Testing only).

Listen.

Below is a sequence of commands that establishes talk/listen.

1 Monitor or DI_Monitor a VF channel.
2 Listen to channel.
3 VF_Split or VF_DI_Split the circuit.
4 Use Talk/Listen.

TLHangup

Syntax

Remark

70 CT-650 Command-Line Reference Guide Release 9.4

Hangs up a Listen or Talk/Listen session.

TLHangup <digroup_side>

The parameter digroup_side is required for drop and insert testing.

Chapter 7 DS0 VF Test Commands

Description of VF test commands

TLStatus

Syntax

Remarks

VF_DI_Measure

Syntax

Displays a screen showing the current status of a Listen or Talk/

Listen

session.

TLStatus <test_name>

This syntax is available to all users.

TLStatus <user_name> <test_name>

This syntax is available to supervisors.

– Talk/Listen results (Port State and Last Act/Sta) are reset

only on a new Listen.

– This command is available after issuing the

Listen command.

Executes an intrusive drop and insert test on the chosen channel.

VF_DI_Measure <digroup_side> <vf_test_type>
<

test_duration>

Available measure

tests

Using the VF_DI_Measure command, you can test a variety of char­acteristics of a VF signal. Table 4 lists the measurements you can
perform on VF signals. Use the syntax in the Syntax column of Table 4
for the

vf_test_type parameter . For example, to fully specify an

echo return loss test using a -13 dB signal for a continuous test period,
type the following command:

VF_DI_Measure 10 Echo_Return -13 Continuous

Table 4 VF measure tests

Test Syntax Description

3 kHz flat
noise mea­surement

3k_Flat Investigates the presence of idle channel noise,

such as crosstalk, white noise, and impulse
noise. The results appear in dBrn, and range
from 20 dBrn to 70 dBrn. A quiet termination at
the circuit’s originating end is required.

CT-650 Command-Line Reference Guide Release 9.4

71

Chapter 7 DS0 VF Test Commands

Description of VF test commands

Table 4 VF measure tests (Continued)

Test Syntax Description

3 kHz notch
noise

Attenuation
distortion

C-Message
noise

3k_Notch Measures noise with a 1004 Hz holding tone

(typically at -16 dBm, assuming a 0 dB TLP)
applied at the circuit's originating point. This test
provides a measure of the noise encountered
by a continuous data signal, because the hold­ing tone activates the channel equipment that
can create noise. Results range from 20 dBrn to
70 dBrn.

Atten_Dist
<transmit_level>
<low_freq> <upper_freq>
<freq_step_size>
<freq_period>

C_Message_Noise Measures the unwanted noise on an idle chan-

Measures the difference between the loss of a
transmitted 1004 Hz holding tone versus the
loss of a tone transmitted at a measurement fre­quency. Once the loss of the holding tone has
been established, the unit compares the loss of
the measurement frequencies (typical range
from 300 to 3500 Hz) to the holding tone to cre­ate an Attenuation Distortion table or curve con­taining 30 measurements. This measurement is
limited to 30 start to stop frequency measure­ments. The test does not test within the range
from 2500 Hz to 2700 Hz to avoid interfering
with in-band signaling.

nel using a digital filter that is C-Message
weighted. The measurements on an idle chan­nel are taken and the results are expressed in
dBrnC, ranging from 10 to 90 dBrnC. If the C­Message Noise is outside the range of 10 to 90
dBrnC, the system indicates whether the value
is less than 10 or greater than 90 dBrnC.

C-notch
noise

C_Notch_Noise Measures the unwanted power on a channel.

Specifically, the test measures the C-Notch
Noise level (dBrnC) and the Signal-to-Noise
(S/N) ratio (dB). If the C-Notch Noise level is
less than 10 dBrnC or greater than 90 dBrnC,
the CT-650 indicates that the value is out of
range. A holding tone of 1004 Hz is required to
perform this test.

72 CT-650 Command-Line Reference Guide Release 9.4

Table 4 VF measure tests (Continued)

Test Syntax Description

Chapter 7 DS0 VF Test Commands

Description of VF test commands

Disable
echo can­celler

Echo return
loss

Impulse
noise

Disable_EC Disables the echo canceller feature of the hard-

ware by transmitting the echo canceller tone
before every VF test. This will ensure that echo
cancellers are properly disabled during VF test­ing. Note that this has the same effect as select­ing Echo_Disable split mode for the

VF_Split command.

Echo_Return <tx_level> Tests for the presence or absence of an “echo”

over a range of 300 Hz to 4000 Hz using a
weighted, swept-frequency sine wave signal.
The echo may be caused by an impedance mis­match or discontinuity between two-wire and
four-wire circuits. The test transmits band-lim­ited noise to measure return loss on VF circuits.

Impulse_Noise
<tx_level>
<ref_threshold>
<threshold_dif>

Counts the number of impulses that exceed
three different thresholds during a given period
of time, and also counts the number of dropouts
that occur during the test. To perform an
Impulse Noise test, the unit sends a holding
tone at a user-specified transmit level, then
uses a C-Message weighting filter on the
received signal. Impulses that exceed one or
more of the thresholds are counted. If an
impulse exceeds all thresholds, all counters are
incremented. The system also counts dropouts.
A dropout is counted if the signal drops by at
least 12 dB for at least four milliseconds. The
system does not count impulse noise hits during
a dropout.

Insertion
loss

Insertion_Loss Determines the overall loss in dB on a given cir-

cuit using the 1004 Hz holding tone at -13.0
dBm. This test is essentially the same as the
Send or Receive Tone test, except that the
transmit level and frequency are fixed values
rather than data entered by the user.

CT-650 Command-Line Reference Guide Release 9.4

73

Chapter 7 DS0 VF Test Commands

Description of VF test commands

Table 4 VF measure tests (Continued)

Test Syntax Description

Intermodu­lation distor­tion

Line tran­sients

Intermod_Dist
<tx_level>

Line_Transient
<tx_level>
<phase_hit_thres>
<gain_hit_thres_1>
<gain_hit_thres_2>
<gain_hit_thres_3>

Measures the second and third harmonics of a
test signal. To measure the harmonics, the
CT-650 uses a test tone that comprises four
equal-level tones. Two of the tones are centered
at 858.95 Hz and are 53 Hz apart; the other two
tones are centered at 1379.1 Hz and are 10.7
Hz apart. The test uses narrow band filters at
520 Hz and 2240 Hz. The average of these two
values is the second-order distortion. A narrow­band filter at 1900 Hz measures the third-order
distortion. The values are expressed in dB
below the received signal. Before sending the
four test tones, the CT-650 measures the noise
in the filters. This value is subtracted from the
four-tone power measurements to ensure accu­rate values for the second and third order distor­tion.

Measures gain hits, phase hits, and dropouts
that occur in a high-speed data circuit. A gain hit
is a rapid change in the level of the signal and is
usually accompanied by a phase hit. A phase hit
is a rapid change in the phase of the signal. A
dropout is a rapid loss in the signal level usually
greater than 12 dB for 4 milliseconds. These
types of line transients can disrupt high-speed
data circuits, and are primarily caused by
switching to standby facilities, radio fades in
microwave paths, and noise transients that
affect carrier equipment. A transient exceeds
the thresholds defined by the user and has a
duration of greater than 4 ms. However, the
CT-650 does not count transients when a drop­out occurs on the circuit under test. This test is
not available when testing signaling.

74 CT-650 Command-Line Reference Guide Release 9.4