D2500 - Telecom Analyzer - messkom.de

TELECOM 

ANALYZER 

D2500 

USER’S MANUAL

USER’S MANUAL TELECOM ANALYZER D2500 

TELECOM 

ANALYZER 

D2500 

USER’S MANUAL 

The information contained in this document is the 

property of Aethra ® S.p.A., it is subject to change 

without notice and it shall in no way be binding for 

Aethra ® S.p.A. 

© Copyright Aethra ® S.p.A. 2005. All rights 

reserved. 

Rev. 0/1.00 - July 2005. Cod. 074022006ML 

This manual is composed of 175 pages


INDEX 

1. INTRODUCING THE INSTRUMENT........................................... 11 

1.1. ABOUT THIS CHAPTER ......................................................... 11 

1.2. FRONT PANEL FEATURES.................................................... 11 

1.3. NETWORK CONNECTIONS................................................... 12 

1.3.1. AVAILABLE ACCESSES................................................... 13 

1.3.2. V/X INTERFACE................................................................ 13 

1.4. OPERATING MODES.............................................................. 14 

1.5. COMMUNICATION PORTS AND CONNECTORS................. 15 

1.6. TURNING ON THE INSTRUMENT ......................................... 15 

1.7. TURNING OFF THE INSTRUMENT ....................................... 17 

1.8. THE USER INTERFACE ......................................................... 17 

1.8.1. KEYS ................................................................................. 17 

1.8.2. THE G.U.I. STRUCTURE .................................................. 18 

1.8.3. FIELDS .............................................................................. 19 

1.8.4. PERFORMING A TEST..................................................... 20 

2. PERFORMING AN AUTOMATIC TEST ...................................... 23 


2.2. CHOOSING AN AUTOMATIC TEST....................................... 23 

2.3. PERFORMING AN ACCESS CHECK ..................................... 24 

2.3.1. SETTING UP AN ACCESS CHECK.................................. 25 

2.3.2. RUNNING AN AUTOMATIC ACCESS TEST.................... 26 

2.4. PERFORMING AN X.25 ACCESS TEST ................................ 28 

2.4.1. SETTING UP AN X.25 ACCESS TEST............................. 29 

2.4.2. RUNNING AN X.25 ACCESS TEST.................................. 29 

3. PERFORMING A MANUAL TEST ............................................... 31 


3.2. OPENING THE MANUAL TEST SCREEN.............................. 31 

3.3. COMMON SETUP ................................................................... 34 

3.3.1. ISDN ACCESS................................................................... 34 

3.3.2. UNFRAMED G.703 ACCESS............................................ 38 

3.3.3. POTS ACCESS ................................................................. 38 

3.3.4. V/X ACCESS (VX2000 OPTION) ...................................... 39 

3.3.4.1. V.35, V36 INTERFACES ..................................................39 

3.3.4.2. V.24 INTERFACE..............................................................40 

3.3.4.3. G.703 CO-DIR INTERFACE.............................................41 

3.3.5. V.11 (X.21)......................................................................... 41 

3.3.6. FRAME RELAY (FR2K OPTION) ...................................... 42 

3.4. PERFORMING A CALL TEST................................................. 43 

3.4.1. SETTING UP A CALL TEST.............................................. 44 

3.4.2. SENDING A CALL ............................................................. 44 

3.4.3. ANSWERING AN INCOMING CALL ................................. 46 

3.4.3.1. POTS CONFIGURATION.................................................46 

3.4.3.2. ISDN SLAVE PROTOCOL CONFIGURATION ...............47 

3.4.3.3. ISDN MASTER PROTOCOL CONFIGURATION............47 

3.4.4. CHECKING THE SUPPLEMENTARY SERVICES ........... 48 

3.5. BER TEST ............................................................................... 49 

3.5.1. SETTING UP A BER TEST ............................................... 50 

INDEX 3

TELECOM ANALYZER D2500 USER’S MANUAL 

3.5.2. RUNNING A BER TEST .................................................... 53 

3.5.3. PERFORMING AN NX64K BER TEST.............................. 55 

3.5.4. RUNNING A BER TEST OVER V/X INTERFACE............. 56 

3.6. PERFORMING GENERATE TRAFFIC TEST ......................... 56 

3.6.1. SETTING UP A GENERATE TRAFFIC TEST................... 56 

3.6.2. RUNNING A GENERATE TRAFFIC TEST........................ 57 

3.7. PERFORMING A FOX TEST................................................... 58 

3.7.1. SETTING UP THE FOX TEST........................................... 58 

3.7.2. RUNNING A FOX TEST .................................................... 59 

3.8. PERFORMING A U-INTERFACE TEST (NT1-U ONLY)......... 60 

3.8.1. SETTING UP THE U-INTERFACE TEST.......................... 60 

3.8.2. RUNNING A U INTERFACE TEST.................................... 61 

3.9. ACTING AS LOOP BOX .......................................................... 61 

3.9.1. SETTING UP A LOOP BOX............................................... 62 

3.9.2. SETTING UP A CALL-BACK ............................................. 62 

3.9.3. RUNNING A LOOP BOX TEST ......................................... 64 

3.10. TESTING THE X.25 ON THE D CHANNEL ............................ 64 

3.10.1. SETTING UP AN X.25 ON D CHANNEL TEST................. 64 

3.10.2. RUNNING AN X.25 ON D CHANNEL TEST ..................... 65 

3.11. TESTING THE X.25 ON THE B CHANNEL............................. 67 

3.11.1. SETTING UP AN X.25 ON B CHANNEL TEST................. 67 

3.11.2. RUNNING AN X.25 ON B CHANNEL TEST...................... 69 

3.12. IP PING TEST.......................................................................... 70 

3.12.1. SETTING UP AN IP PING TEST ....................................... 70 

3.12.2. RUNNING AN IP PING TEST............................................ 72 

3.13. IP TRACE ROUTE ................................................................... 73 

3.13.1. SETTING UP AN IP TRACE ROUTE TEST ...................... 73 

3.13.2. RUNNING AN IP TRACE ROUTE TEST........................... 74 

3.14. IP GENERATE TRAFFIC......................................................... 76 

3.14.1. SETTING UP AN IP GENERATE TRAFFIC TEST............ 76 

3.14.2. RUNNING AN IP GENERATE TRAFFIC TEST................. 78 

3.15. TONE GENERATOR AND MEASUREMENTS ....................... 79 

3.15.1. SETTING UP A TONE GENERATOR AND MEASUREMENT TEST 80 

3.15.2. RUNNING A TONE GENERATOR AND MEASUREMENT TEST 81 

3.15.3. MEASURING THE B CHANNEL ROUND TRIP DELAY (ECHO) 82 

3.16. USING THE D1029N ADAPTER (NT1-S ONLY)..................... 83 

3.17. LT-U SIMULATION (LT-U2K OPTION) ................................... 84 

3.18. S/T-BUS WIRING TEST (WT2000 OPTION) .......................... 84 

3.18.1. SETTING UP AN S/T-BUS WIRING TEST........................ 85 

3.18.2. RUNNING AN S/T-BUS WIRING TEST ............................ 85 

3.19. AT TERMINAL (TTY) TEST (V.24 ASYNCHRONOUS) .......... 86 

3.19.1. SETTING UP AN AT TERMINAL (TTY) TEST .................. 86 

3.19.2. RUNNING AN AT TERMINAL (TTY) TEST ....................... 87 

4. PREDEFINED TESTS.................................................................. 89 


4.2. SAVING A PREDEFINED TEST.............................................. 89 

4.3. PERFORMING A PREDEFINED TEST................................... 90 

4.3.1. DEFAULT PREDEFINED TEST ........................................ 92 

4.4. DELETING A PREDEFINED TEST ......................................... 93 

4.5. USING THE FAVORITES FEATURE ...................................... 94 

5. USING THE INSTRUMENT FOR MONITORING ........................ 97 

4 INDEX



5.2. MONITOR VS ANALYZE......................................................... 98 

5.3. BACKGROUND MONITOR VS HIGH IMPEDANCE MONITOR 99 

5.4. SETTING UP FOR MONITORING .......................................... 100 

5.5. BRI-U MONITORING (D2022 OPTION).................................. 101 

5.6. START MONITORING............................................................. 102 

5.6.1. MONITORING THE B CHANNEL...................................... 102 

5.7. STOP MONITORING............................................................... 104 

5.8. SAVING THE TRACE.............................................................. 104 

6. USING THE MULTIMEDIACARD (MMC2000 OPTION) ............. 105 

6.1. INTRODUCTION ..................................................................... 105 

6.1.1. CONNECTION................................................................... 105 

6.2. FORMATTING THE MULTIMEDIACARD ............................... 105 

6.2.1. HOW TO FORMAT THE MULTIMEDIACARD WITH MMCWIZARD 106 

6.3. SETTING UP THE MULTIMEDIACARD.................................. 107 

6.4. UPLOADING THE FILE INTO THE PC ................................... 108 

7. SMART STATUS ......................................................................... 111 


7.2. PRIMARY ACCESS STATUS ................................................. 111 

7.2.1. G.703 ACCESS ................................................................. 112 

7.2.2. G.826 ................................................................................. 113 

7.3. BASIC ACCESS STATUS ....................................................... 114 

7.4. B CHANNELS STATUS........................................................... 114 

7.4.1. RESTARTING B CHANNELS............................................ 116 

7.4.2. B CHANNELS CONNECTION........................................... 116 

7.5. DEVICE INFORMATION ......................................................... 118 

7.6. V/X INTERFACE ACCESS STATUS (VX2000 OPTION) ....... 119 

7.7. V.11 (X.21) ACCESS STATUS................................................ 120 

7.8. FRAME RELAY PROTOCOL STATUS (FR2K OPTION) ....... 121 

7.9. READING THE POTS LINE STATUS ..................................... 122 

7.10. READING THE BATTERY STATUS ....................................... 122 

8. ANALYZING A MONITOR TRACE .............................................. 125 


8.2. ANALYZING A TRACE............................................................ 125 

8.3. ANALYZING A TRACE IN OVERVIEW MODE....................... 127 

8.4. ANALYZING A TRACE IN FULL DECODING MODE ............. 127 

8.5. ANALYZING A TRACE IN MIX DECODING MODE ............... 128 

8.6. ANALYZING A TRACE IN HEXADECIMAL DECODING MODE 129 

8.7. INSERTING A CALL FILTER .................................................. 130 

9. STATISTICS ................................................................................ 131 

10. CONFIGURING THE INSTRUMENT........................................... 135 


10.2. OPENING THE CONFIGURATION MENU ............................. 135 

10.3. USING THE PHONEBOOK ..................................................... 135 

10.4. ADJUSTING THE VOLUME .................................................... 137 

10.5. CHANGING THE AUDIO CONNECTION................................ 137 

10.6. CHANGING THE INFORMATION LANGUAGE...................... 137 

10.7. SETTING THE DATE AND TIME ............................................ 137 

10.8. CHANGING THE BAUD RATE................................................ 137 

10.9. SELF DIAGNOSTICS .............................................................. 138 

INDEX 5


10.10. INFORMATION AND OPTIONS .............................................. 139 

10.11. BATTERY MANAGEMENT...................................................... 139 

10.12. CHANGING THE CONTRAST................................................. 139 

10.13. SCREEN SAVER MANAGEMENT .......................................... 139 

10.14. TEST PROGRAMMING ........................................................... 140 

10.14.1. AUTOMATIC BACKGROUND MONITOR ......................... 141 

10.14.2. SELF SWITCHING OFF .................................................... 141 

11. USING MEMORY, PRINTER AND PC ........................................ 143 


11.2. SAVING TEST RESULTS........................................................ 143 

11.3. VIEWING TEST RESULTS...................................................... 144 

11.4. PRINTING TEST RESULTS OR MONITORED TRACES....... 145 

11.5. USING “PC108 FOR WINDOWS TM ” SOFTWARE................... 145 

12. MAINTAINING THE INSTRUMENT............................................. 147 


12.2. CLEANING AND STORAGE.................................................... 147 

12.2.1. CLEANING THE INSTRUMENT........................................ 147 

12.2.2. STORING THE INSTRUMENT.......................................... 147 

12.3. BATTERIES ............................................................................. 147 

12.3.1. CHARGING THE BATTERIES........................................... 147 

12.3.2. EXTENDING BATTERY OPERATING TIME..................... 148 

12.3.3. DIMMING THE BACKLIGHT.............................................. 148 

12.3.4. REPLACING THE NIMH BATTERY PACK ....................... 148 

12.4. DISPLAY .................................................................................. 149 

12.4.1. PROTECTIVE LABEL ........................................................ 149 

12.5. TROUBLESHOOTING ............................................................. 150 

12.5.1. THE INSTRUMENT DOES NOT START UP..................... 150 

12.5.2. THE SCREEN REMAINS BLACK...................................... 150 

12.5.3. BATTERIES OPERATE LESS THAN THREE HOURS .... 150 

12.5.4. THE SOFTWARE DOES NOT RECOGNIZE THE INSTRUMENT 150 

12.5.5. THE PRINTER DOES NOT PRINT ................................... 150 

13. SPECIFICATIONS ....................................................................... 151 

13.1. INTRODUCTION...................................................................... 151 

13.1.1. SAFETY CHARACTERISTICS .......................................... 151 

13.1.2. PERFORMANCE CHARACTERISTICS ............................ 151 

13.1.3. ENVIRONMENTAL DATA.................................................. 151 

13.2. COMPLIANCE.......................................................................... 151 

13.3. BASIC RATE............................................................................ 151 

13.4. PRIMARY RATE ...................................................................... 152 

13.5. V.11 (X.21) ACCESS ............................................................... 153 

13.6. V/X ACCESS (VX2000 OPTION)............................................. 153 

13.7. POTS ACCESS (AB2000N OPTION)...................................... 154 

13.8. PROTOCOLS........................................................................... 154 

13.9. POWER WITH INTERNAL BATTERIES ................................. 155 

13.10. POWER WITH EXTERNAL ADAPTER ................................... 155 

13.11. MISCELLANEOUS................................................................... 156 

13.12. DATA CONNECTION .............................................................. 157 

13.13. USE AND STORAGE CONDITIONS....................................... 157 

13.14. REFERENCE REGULATIONS (RELIABILITY TESTS) .......... 158 

CONNECTOR TERMINATIONS............................................................ 161 

6 INDEX


CONNECTIONS .................................................................................... 167 

ISDN LOOPBOX STATE MACHINE ..................................................... 173 

INDEX 7


SAFETY RULES 

The change from cold to hot environments can cause the formation of condense inside the device. To 

avoid malfunctioning, wait at least 2 hours before connecting the device to the supply mains. 

Warning: for power supply connection use an easily accessible outlet located near the device. 

Never remove the mains plug for permanent connection. 

WARNING: RISK OF ELECTRIC SHOCK 

The power supply used by this device involves lethal voltage levels. 

Do not access internal parts of the device (and/or of the power supply unit). 

If objects or liquids penetrate inside the device, immediately disconnect the power supply cable. Before 

using the device again, have it checked by specialized staff. 

Refer to qualified staff for service. 

In case of intervention, always check that the power supply has been completely and successfully 

disconnected. 

In case of fire, absolutely avoid using water to extinguish it. 

This equipment may not be treated as household waste. Instead it shall be handed over to the 

applicable collection point for the recycling of electrical and electronic equipment. By ensuring this 

product is disposed of correctly, you will help prevent potential negative consequences for the 

environment and human health, which could otherwise be caused by inappropriate waste handling of 

this product. For more detailed information about recycling of this product, please contact your local 

city office, your household waste disposal or the dealer where you purchased this product. 

SAFETY RULES 9


WARNINGS 

CAUTION: 

Many of the components used in this device are sensitive to electrostatic charge. 

In case of manipulation of the connection cables, disconnect the power supply and avoid direct 

contacts with the connector terminals. 

When handling electronic components, to eliminate any static electricity touch a grounded surface. If 

possible, wear a grounding armband. 

Failure to comply with these warnings could cause permanent damage to device. 

Connect the measurement cable of the U interface to the instrument connector and then to the 

telecommunication line to avoid accidental contacts with live parts of the TNV circuits. 

To guarantee continuous protection for operator safety, only use the mains adapter supplied with the 

instrument. 

CLEANING 

To clean the device use a soft cloth either dry or soaked with little detergent. Never use any type of 

solvents, such as alcohol or gasoline, to avoid damaging the finish. 

10 WARNINGS - CLEANING


1. INTRODUCING THE INSTRUMENT 

1.1. About this Chapter 

This chapter describes the features of the Telecom Analyzer D2500. 

► Front panel 

► Top case with network connections 

► Side of the instrument with communication ports and connectors 

Next you will find instructions on how to turn on and off the instrument and 

on the operation of the user interface. 

1.2. Front Panel Features 

Refer to Fig. 1-1 for a description of the front panel controls and displays. 

� LCD Screen 

Fig. 1-1 Front Panel 

Displays all menus, data, and results. Where necessary, the screen 

also displays messages in reversed video. 

� LED indicators 

The LED indicators are grouped as follows: 

► RUN, indicate that a test is in progress. 

► Three LED’s to indicate the operating mode over Primary 

Access (PRI) or over VX datacom interface. 

► Six LED’s to indicate the operating mode over Basic 

Access (BRI). 

► Three LED’s to indicate a layer 1, 2, or 3 activity. 

CHAPTER 1 - INTRODUCING THE INSTRUMENT 11


� Arrow keys 

Use these keys to move the cursor in all directions or scroll through 

pages when prompted. 

Use the right arrow key to choose when prompted. 

� Alphanumeric keypad 

Use these keys to input telephone numbers and alphanumeric data. 

� Microphone 

Use this internal microphone to make voice calls. 

� Loudspeaker (on rear side) 

Use this internal loudspeaker to hear voice calls. You can adjust the 

speaker volume to your preference. See chapter 10. 

1.3. Network connections 

Three RJ45 connectors are located at the top of the instrument. Use one 

of these connectors at a time to connect the instrument to a network 

reference point via a network cable. Depending on the reference point, 

you must use one of network cables supplied with the instrument. Refer to 

Fig. 1-2 for a description of the top case. 

Fig. 1-2 Top Case with Network Connections 

E1 Use this connector for all simulation tests or monitoring on the E1 

interface (Primary Rate). 

S/T Use this connector for all simulation tests or monitoring on the S 

or T interface (Basic Rate). 

U Use this connector for all simulation tests on the U interface 

(Basic Rate). 

12 CHAPTER 1 - INTRODUCING THE INSTRUMENT


1.3.1. Available accesses 

Listed below, the type of interfaces supported by the devices: 

ACCESS DESCRIPTION 

BRI Basic Access 2B+D over Uko/So/To according to ETS 300 

012 – ITU-T I.430 – ETR 080 standards. 

PRI 

(CRC4) 

Primary Access 30B+D over S2/T2 with CRC4 control 

according to ETS 300 011, G.704 standards. 

PRI Primary Access 30B+D over S2/T2 according to ETS 300 

011, G.704 standards, without CRC4 control. 

Unframed 

G.703 

2Mbit access with line code G.703 in UNFRAMED mode. 

V/X Access over synchronous interface according to V.35 - V.36 

- V.11 (X.21) - V.24 - CODIRECTIONAL standards. 

POTS Access over analog telephone line with 2 wires physical 

interface. 

Accesses BRI, PRI (CRC4) and PRI support signalling protocols over D 

channel at common channel (CCS) as reported in specification, moreover, 

the same interfaces support LEASED connections (e.g. PCM30, 

PCM30CRC, PCM31, PCM31CRC). 

1.3.2. V/X Interface 

The D2500 is able to perform tests over WAN/datacom lines with a bit rate 

up to 2.048 Mbit/s. 

Thanks to the possibility to emulate both DTE (Data Terminal Equipment) 

and DCE (Data Communications Equipment), the D2500 allows to carry 

out quality tests, bit error rate (BER), in end-to-end mode over datacom 

line, or checks toward the User’s DTE (CSU, router, or other WAN 

equipment). 

The criteria monitoring and the possibility to manage local loops (LL), 

allow to extend controls over datacom line. 

The V11/X.21 interface is embedded in the main unit (a software option 

must be installed) and then there’s no need for any external adapter. An 



optional adapter (VX2000) is required for the other Datacom interfaces 

(V.24, V.35, V.36, CO-DIR). 

Fig. 1-3 

In order to connect to the line, use the appropriate cable according to the selected mode. In order to 

operate correctly, first connect the cable, then configure the device. 

1.4. Operating modes 

The table below, shows the operating modes available on the test 

equipment. Some of that requires a specific option. 

PRIMARY RATE 

TE-E1 The instrument simulates a Terminal Equipment on the 

E1 interface. 

MON- 

E1 

The instrument monitors the E1 interface in high impedance. 

See chapter 5. 

NT-E1 The instrument simulates a Network Termination on the 

E1 interface. 

BASIC RATE 

TE-S The instrument simulates a Terminal Equipment on the S/T 

interface. 

MON- 

S 

The instrument monitors the S/T interface in high impedance. 

See chapter 5. 

NT-S The instrument simulates a Network Termination on the S/T 

interface. 

NT-U The instrument simulates a Network Termination on the 

U interface. 



MON- 

U 

The instrument monitors on the U interface. See Chapter 5. 

LT-U The instrument simulates the exchange Line Termination on the 

U interface for tests towards a user NT. 

Table 1-1 Instrument Modes 

In Appendix B is reported the information about how to connect the test equipment to the line using 

the specific options. 

1.5. Communication ports and connectors 

Refer to Fig. 1-4 for the available ports and connectors. 

Fig. 1-4 Side of the Instrument 

POWER IN Connection for the AC/DC adapter supplied with the 

instrument. 

POWER 

OUT 

Warning 

To avoid electrical shock, use only Aethra ® adapter, model 

531000064. 

Connection for external accessory power plug. 

Warning 

To avoid electrical shock, use only Aethra ® accessories. 

HANDSET Connection for an external telephone handset. 

RS 232 Serial port for interfacing with a PC or printer via a standard 

RS 232 cable. 

V11 V.11 port for interfacing with the B channel via a standard 

ISO4904 cable. 

1.6. Turning on the Instrument 

To power the instrument from a standard AC outlet, perform the steps 

below. For battery power information, refer to chapter 12. 



1 Plug the AC/DC adapter in the AC outlet. 

2 Connect the AC/DC adapter to the POWER IN plug of the 

instrument. See Fig. 1-5. 

Fig. 1-5 Powering the Instrument 

3 Turn the instrument on. The opening screen appears on the 

display. 

4 

The opening screen shows the time and date. 

If the instrument does not turn on, the batteries may be dead. Leave the instrument connected to the 

outlet for 15 minutes and try again. 

Continue. The TEST MENU appears on the display. 

Now you can choose to perform one of the following tests: 

► Automatic tests. See chapter 2. 

► Manual tests. See chapter 3. 



► Predefined tests. see chapter 4. 

1.7. Turning off the Instrument 

1.8. The user interface 

Hold it pressed for min. 2 seconds to turn the instrument off. 

The instrument is provided with a newly designed GUI (Graphic User 

Interface) for easy, immediate operation. 

1.8.1. Keys 

Opens the main menu and selects the type of test from 

predefined, automatic or manual tests. 

Enables to analyse signalling messages captured through 

the instrument directly on the instrument screen. See chapter 

8. 

Exits from a menu. 

Scrolls through pages and fields of the graphic interface. 

Confirms an insertion field or activates the function 

associated with a softkey. 

Display page 1 of the available information on the instrument 

and line status. 

Enables to view saved test results. See chapter 8. 

Enables to configure the instrument. See chapter 10. 

Enables to enter telephone numbers, alphanumeric data and 

send DTMF tones. See § 3.4.2. 

The instrument is also provided with a series of virtual keys (softkeys) that 

appear on the left side of the page and change their meaning according to 

the test status or requirement. 

Selects a softkey. 

Activates the function associated with the softkey. 



1.8.2. The G.U.I. structure 

The various pages of the G.U.I. use the same graphic symbols and keys 

for navigation. The first line of each page indicates the page title and gives 

information on the instrument and test status. 

Fig. 1-6 Status Line 

The blinking alternation of these two symbols in the monitor in progress icon, means that the 

available memory is full. This is true if in the background monitor setup is selected circular 

buffer mode. See chapter 5. 

Pages are made up of fields, softkeys and results. 

Selected softkey 

Softkeys available 

Test status 

Results 

Number of pages 

The test results may be contained in different pages. Use the keys to 

scroll through the result pages. 

The test parameters can be modified with the fields. Use the keys to 

select the desired field. The line with black background will scroll through 

the available fields. 

In each page one or more helping icons are displayed on the keys used to 

modify the parameter or accept the entered value. They are used to enter 

data, scroll through pages, confirm values or execute special functions. 

Use to access a new menu. 

Use to scroll a menu with cyclic selection mode or to 

scroll the fields available in the page. 

Use to scroll the results pages or to change page during 

the setup step (setup of the device, the access or the 



1.8.3. Fields 

selected test). 

Indicates an alphanumeric data insertion field. 

Use to confirm the entered value or execute a special 

function. 

Fields are used to modify the test parameters. 

Scroll through the fields. The selected field has white 

characters on a black background. 

Following are some examples of the available fields. 



1.8.4. Performing a test 

Fields with cyclic selection mode, the parameter value is selected from the 

predefined ones, that can be highlighted scrolling with . 

Edit fields, the parameter value is modified by inserting data directly. Editing of 

Alfanumeric field is available with insert and cursor movement inside the field 

itself. 

Press ENTER to enter the editing mode; 

Use the UP and DOWN arrow keys to move left and right; 

RIGHT arrow key adds a space; 

LEFT arrow key deletes the left char. 

Edit fields with help on-line, the keys can be used to activate additional 

functions 

To run a test, perform the following preliminary steps: 

1 

Open the TEST MENU. The last used setup appears on the 

screen. 



2 

3 

4 

5 

Select the Access Mode and choose the Act as field. Once 

selected these two fields ( ) select the type of test: it can 

be selected among the PREDEFINED TESTS (see chapter 

4), MANUAL TESTS (see chapter 3) and AUTOMATIC 

TESTS (see chapter 2). 

Connect the instrument to the line according to the 

instructions given on the display The type of connection 

depends on the choices of “Access” and “Act as” previously 

done 

Setup of the parameters for the execution of the test (softkey 

SETUP) 

Press to start the test. (softkey START). 



2. PERFORMING AN AUTOMATIC TEST 


This chapter describes the procedure used to perform an automatic test. 

This test allows you to automatically test the ISDN configuration of the 

access. Fig. 2-1 shows the navigation for the automatic test. 

2.2. Choosing an Automatic Test 

Fig. 2-1 Navigation for Automatic Tests 

The first step to make an automatic test is to select the access type and 

instrument mode: 

1 

2 

3 

Open the TEST MENU. 

The last used setup appears on the screen. 

Select the ACCESS field. 

Select the “Act as” field. The lower selection of the screen 

CHAPTER 2 - PERFORMING AN AUTOMATIC TEST 23


4 

5 

6 

7 

8 

shows the selected network configuration. 

The lower section of the screen shows the selected network 

configuration. The yellow LED that corresponds to the 

selected mode goes on. You can choose the instruments 

modes listed in Table 2-1. 

Select AUTOMATIC TESTS. 

The following window appears: 

( 

Connect the device as shown, according to the picture 

displayed. The kind of connection depends on the access 

and the mode previously chosen. 

Access the Automatic Test menu. 

Choose the test you want to perform. Now the result page of 

the test is immediately shown. Each test is described in the 

following pages. 

Setup the test parameters (softkey SETUP). 

Start the test (softkey START). 

2.3. Performing an Access Check 

This test allows to verify, automatically, in distinct sequences the following 

access parameters: 

24 CHAPTER 2 - PERFORMING AN AUTOMATIC TEST


1 Layer 1 

2 Layer 2 configuration 

3 Layer 3 (bearer and teleservices) 

4 Supplementary services 

5 B channels 

Setting appropriately the parameters above-mentioned, the user can 

decide the test sequences to perform. Setting the value “Automatic”, the 

device will carry out a complete test sequence, checking all the 

parameters regarding the interested level. 

If it is chosen: “L2: Point to Point” and / or “L3: User”, the relative values must be programmed before 

in the COMMON SETUP page. 

The test sequence configured can be saved with a name defined by the 

user, in order to be recalled for future uses. See chapter 4 for further 

information. 

If this automatic test reports problems, e.g. unavailable services or profiles, it’s recommended to 

perform a specific manual tests 

2.3.1. Setting Up an Access Check 

Define the following parameters for an automatic test: 

Called number: Enter the phone number of the called party. 

� Remote number for calls to a remote user. 

� Local number for autocalls. 

Pause intercalls(sec.): Enter the number of seconds for the pause 

between two calls. In some cases a pause ranging from 2 to 8 seconds is 

necessary to obtain correct results. 

L1: Choose YES to enable the automatic test of Layer 1. 



L2: Choose AUTOMATIC to enable the automatic test of the configuration 

of Layer 2 (PP, PMP) or choose a configuration to test. 

L3 (bearer services): Choose AUTOMATIC to enable the automatic test 

of the capabilities of Bearer services and Teleservices (Speech, Data, Fax 

Gr.4,…) or choose the service to test. 

Supplementary services: Choose AUTOMATIC to enable the automatic 

test of the supplemetary services available for the access (CLIP, DDI, CF, 

…), or choose a service to test. 

B channel check: Choose AUTOMATIC to enable the automatic test of 

the availability of B channel, or choose the channel to test 

2.3.2. Running an automatic access test 

When you have defined the setup for the automatic test, continue as 

follows: 

1 

2 

Note that: 

Come back to result page. 

Start the Access test. 

The LED RUN goes on and the START key changes to STOP. Use this 

key to stop the test. 

To obtain the access configuration, the instrument makes a series of calls 

to the entered number, changing the profile and the B channel every time, 

and tries to verify the supplementary services. 

Following are some examples of “RESULT: ACCESS TEST” screens. 

3 

Scroll through the result pages. 

Page 1 shows information about the called number and the status of 

layers 1and 2. In a P-P connection, the configuration Master/Slave is 

automatically detected. 



Page 2 shows an overview of the tele- and bearer services available. The 

last row displayed on this page shows the availability on the access of a 

second protocol. Only for bi-protocol network (E-DSS1/1TR6). 

The instrument makes a series of calls to the entered number, each time 

with a different profile. 

For calls to a remote number: 

► The LOCAL column shows the services enabled at the local 

access for the selected channel. 

► The REM column shows the services enabled at the remote 

access for the selected channel. 

For autocalls: 

► The OUT column shows the services enabled at the local 

access for outgoing calls. 

► The IN column shows the services enabled at the local access 

for incoming calls. 

Page 3 shows an overview of the supplementary services analyzed by the 

device. 

The following table shows the displayed symbols with their meaning. 

YES Implemented, active or actionable service 

NO* Implemented, but not subscribed, service 

NO Service not present 

?? Service availability cannot be determined 

In order to the check availability of the DDI/MSN service, you need to 

perform an autocall and insert, as called number, one of the secondary 

numbers expected by the tested access. 

If the service is available, the device displays the two numbers of the 

access preceded by the symbol ‘arrow’ indicating the direction of the call. 

Usually the calling number, provided by the network, is the basic number 



of the access. The result of this test depends on the network 

configuration. 

Page 4 shows the B channels available at the local access for outgoing 

calls. 

Generally the“--“ indicates that the profile, service or B channel has not 

been verified yet. “OK” appears in the column when the profile or the B 

channel is available. If the service or the B channel is not available, the 

cause is shown with the relative ISDN code number (cause code). Use the 

arrow keys to display information on the cause codes and relative location 

on pages 5 and 6. 

You can save and/or print the test results at the end of the test. See 

chapter 11 for more information about saving and printing. 

To automatically obtain a complete indication on the access configuration, enter the number of the 

tested access as “CALLED NUMBER”. 

Specific manual tests are recommended in case of not available services or profiles. See chapter 3. 

2.4. Performing an X.25 Access Test 

Use this test to verify if and which link (TEI) supports the X.25 service 

(SAPI 16). A further test may be performed in order to control the 

availability of the LCI given to the access. 



2.4.1. Setting up an X.25 Access Test 

In order to verify the TEI enabled to X.25 service, no parameter 

configuration is needed. For the test regarding LCI, the following 

parameters can be defined: 

1 

Set the test parameters. 

Called address: Enter the possible X.25 number of the remote to call. It 

may be the own number, if configured as bidirectional in the Central 

Office. 

LCI start: Enter the value of the first LCI, assigned to the access to verify. 

The test does not require the insertion of a specific number to call in order to verify the valid LCI 

values. 

Range: Enter the maximum number of LCI to verify, starting from the one 

entered above. 

2.4.2. Running an X.25 Access Test 

Connect the instrument to the tested access and continue as follows: 

1 

2 

Note that: 


Start the X.25 Access check. 

The LED RUN goes on, and the START key changes to STOP. Use this 

key to stop the test. 



The instrument checks each link with TEI value from 0 to 63 and shows 

the test result as indicated in the table below: 

TEI not checked yet 

Service not available 

Establishment layer 2 link (SAPI 16) 

R Establishment layer 2 link (SAPI 16) and reception of layer 3 

RESTART message 

Some exchanges consider the X.25 as active only if a RESTART indication is sent. 

In case the device detects some TEI which support the X.25 service, for 

the first three links it is also performed the LCI test. In this case the device 

checks the range availability of the LCI set for each link. 

LCI values may change for each single TEI. 



3. PERFORMING A MANUAL TEST 


This chapter describes the procedure used to configure parameters and 

perform a manual test. This test allows you to test the line quality and the 

available services in detail. Navigation has the same sequence for all 

tests. See Fig. 3-1. 

Fig. 3-1 Navigation for Manual Tests 

About the FTP download addresses, the filename input is limited to 25 chars, the URL is 50 chars and 

the PWD and USERID are 25 chars each one. 

3.2. Opening the Manual Test Screen 

To select the manual test: 

CHAPTER 3 - PERFORMING A MANUAL TEST 31


1 

2 

3 

4 

5 

6 



Select the ACCESS type. 

Select the mode (“ACT AS” field). The lower section of the 

screen shows the selected network configuration. 

The lower section of the screen shows the network 

configuration in use. The yellow LED that corresponds to the 

selected mode goes on. The available instrument modes are 

shown in Table 3-1. 

Select MANUAL TESTS. 

Choose the test you want to perform. 

Choose the test you want to perform. Now the result page of 

the test is immediately shown. Each test is described in the 

following pages. 

32 CHAPTER 3 - PERFORMING A MANUAL TEST


The functions in the TEST MENU can differ according to the selected network configuration and 

according to the device in use. See Table 3-1. 

Table 3-1 Manual Tests vs. Network Configuration 

Table 3-1 shows all the tests available for the various network configurations. For the functional 

characteristics of each single device, see Table 1-1. 

The table below shows available tests for optional features AB2000N and 

WT2000. 

Table 3-2 optional features AB2000N and WT2000 



3.3. Common Setup 

This page is used to setup the common parameters for the various tests 

for the selected access. This makes the device management easier since 

the common fields will remain unchanged. 

1 

1 

2 

3.3.1. ISDN access 

To select the COMMON SETUP page. 

The COMMON SETUP page can be selected from any test. 

Select the field you are interested in. 

The following parameters can be defined for the ISDN access: 

Protocol: Choose the local singling protocol. 

Set the “LEASED LINE” value to perform tests without signalling protocol over the D channel, i.e. 

Unframed BER. Use the “OTHER” parameter to capture signalling protocols not directly supported by 

the instrument in Monitor mode. See chapter 5. 

Protocol type: Define the operation mode of the active protocol between 

Master and Slave. When you select the instrument operation mode, i.e. 

TE or NT, the “Protocol type” parameter will be automatically set with the 

typical value for the configuration. 

Change the parameter in case of special use of the instrument only. 

CDN(type/plan): Set the Type of Number and the Called Party 

Numbering Plan. It is possible to select among Unknown , ISDN, Private 

and National. 1TR6, TN1R6, DASS, DPNSS don’t support the last two 

values. 



CGN(type/plan): Set the Type of Number and the Calling Party 

Numbering Plan. It is possible to select among Unknown , ISDN, Private 

and National. 1TR6, TN1R6, DASS, DPNSS don’t support the last two 

values. 

Sensitivity RX: Choose between HIGH and LOW for higher or lower 

sensitivity in the RX side. 

Clock TX: Choose the type of clock used for transmission between 

“Internal” or “Looped”. 

Idle word: Word transmitted by the device into the unused time-slots. PRI 

only (choose between Default word or an User-defined word). 

Ignores L1 alarms: Timer used to ignore layer 1 alarms that are shorter 

than the inserted value. 

B channel in use: Choose the B channel requested for outgoing calls. 

� Any, the instrument requests a free B channel to the network. 

� Rotation, the instrument requests a different B channel for each call. 

The channel is selected between the available ones 

� , the user chooses a specific B channel. 

User profile: Choose the call user profile you want to use for the test. You 

can choose from a predefined list or define your own user profile. 

Band: Select the Time Slot allocation modality between: 

� 64 Kbit Automatic, the first free Time Slot is automatically assigned. 

� 64 Kbit Rotation, assigns the following free Time Slot at every 

START of the test. 

It is also possible to select the channels to be used, that is to select single 

Time Slots on which carry out the test. Only PRI Leased Line. 

1 

Select “Band:” from the first COMMON SETUP page in 

Primary access (Leased Line), choose User and press 

ENTER. 



2 

3 

Select the Time Slots on which perform the test and press 

ENTER. 

Exit from Common Setup pages and carry out the test. 

Own/MSN: Enter your local MSN number. If defined, the instrument 

activates a check on this parameters for incoming calls. In Network 

simulation or Point-to-Point configuration, it is possible to set the 

Own/MSN to cover a range of numbers by using wildcard characters. 

In order to accept only incoming calls which are included among a certain range, e.g. if you want to 

accept calls with ‘Called Number’ among 12300 and 12399, and reject all others, you can set the 

Own/MSN to 123**. As calling number, the tester will use a '0' per each wildcard. 

To insert wildcard character in the Own/MSN field 

Own sub address: If necessary, enter your local sub address. If defined, 

the instrument activates a check on this parameters for incoming calls. 

User to user information: Define the information you want to send with 

the USER-TO-USER supplementary service. Data is entered in 

hexadecimal format. 

TEI management: Choose one of the TEI management preferences. The 

instrument manages both Point-to-Point and Point-Multipoint connections. 

CLIR/COLR: Activate or deactivate the Calling Line Identification 

Restriction (CLIR) and Connected Line Identification Restriction (COLR). 

CUG (Closer User Group): This supplementary service is used to define 

a closed group of users and create a private virtual network, in which only 

the members can communicate. Set the Closed User Group (CUG) value 

between: 

� No request: CUG service is not requested 

� Inside: to call a internal member of the CUG 

� Outside: to call a user that doesn't belong to any CUG 



� User (x): to call a user that belongs to a specific CUG, enter the 

CUG identification 

Call accept: Select the incoming calls that will be automatically answered 

by the instrument with the loopbox function. The function can be 

deactivated by setting the “None” value. See § 3.9. 

100Ω termination: Choose if you want to add a 100Ω termination to the 

S/T socket. This option can be used if the S/T bus is not terminated 

correctly. The default value is NO. BRI-S only. 

CRC4: Activate or deactivate the CRC4 procedure. PRI only. 

Bits Sa (Sa4..Sa8): Set the “Sa” bit of the 2Mbit frame. PRI only. 

Gain RX: Inserts amplification stage in reception in case of very 

attenuated line signal or for monitor on measurement protected point. PRI 

only. 

Line Code: Set the line code for the BRI U interface between 2B1Q or 

4B3T. Only U interface. 

Load (30..2500mW): Set the load in milliwatts you insert in the BRI U 

interface in case of NT-U mode. Use the 1100-mW default value when no 

other value is preferred. Only U interface. 

Vmin threshold (25..100V): Set the minimum voltage value on the BRI U 

interface under which the instrument resets its line interface. Use the 28 V 

(ETR080) default value when no other value is preferred. 



3.3.2. Unframed G.703 access 

1 

2 

The Frame Relay settings can be accessed form the Test 

Menu page: 

See § 3.3.6 for all the details about these Frame Realy 

settings. 

Exit from Frame Relay settings page. 

The following parameters are used for Unframed G.703 access: 

Sensitivity RX: Choose between HIGH and LOW for higher or lower 

sensitivity in the RX side. 

Clock TX: Select the type of clock used for transmitting choosing between 

‘Internal’ or ‘Looped’. 

Ignores L1 alarms: Timer used to ignore layer 1 alarms that are shorter 

than the inserted value. 

3.3.3. POTS access 

The following parameters are available for the POTS access: 

Termination: Set the line impedance value. The instrument supports four 

impedance models: CTR21 standard, 600Ω resistive, complex impedance 

(Belgium), complex impedance (Germany, Spain). 

Line current limit: Set the maximum current permitted by the current 

regulations. 

Selection mode: Set the dialing type for the telephone number from tone 

(DTMF) and 40/60 or 33/66 pulses. 

Flash time: Duration time of the Flash 'R' key to request special services. 

The value ranges from 40 to 1000 msec. 

DTMF tx level (dBr): Set the line transmission level of the DTMF tones. 



3.3.4. V/X access (VX2000 option) 




(V.24, V.35, V.36, CO-DIR). 

The following parameters are used for V/X access: 

Act as DTE Act as DCE 

Interface type: Choose the interface to use among: 

� V.35, V.36, V.24 (Asynchronous and Syncronous) and G.703/CO- 

DIR. 

3.3.4.1. V.35, V36 interfaces 

Line rate: Select the line rate (from 64 to 2048 kbits, Nx64) used by the 

device to transmit data. Only if Clock RX = Internal and mode = DCE 

Flow control: Activate or deactivate the flow control. 

� None, management and checking of C108, C107, C105, C106 and 

C109 criteria between DTE and DCE is disabled. 

� Hardware, the device manages and controls the above mentioned 

criteria. 

Loop3 (C141): Set “YES” to ask to DCE to perform a local loop (LL) of the 

data. Only DTE mode. 

The loop (LL) request is supported only for V.35, V.36, and V.24 synchronous interfaces. 

Reception Clock: Define the type of clock used to sample received data. 

� DTE mode, select the external source for clock between C114 and 

C115. By default DTE uses C115 criterion. 

� DCE mode, EXTERNAL CLOCK: The device samples received data 

with clock coming from DTE (C113). By default DCE uses C113 

criterion. INTERNAL CLOCK: The device samples received data 

with clock referred to C115. 



In DCE mode, data transmission clock is fixed at INTERNAL (C115 brought back over C114). 

In DTE mode, source for data transmission clock is the clock coming from DCE over C114 criterion 

brought back over C113. 

Clock RX phase: Select on which reception clock edge incoming data 

change, the device samples data on the opposite edge. By default the 

DCE switches data on the clock’s falling edge. Only DTE mode. 

Clock TX phase: Select on which transmission clock edge incoming data 

change, DTE samples data on the opposite edge. By default the device 

switches data on the clock’s falling edge. Only DCE mode. 

DCD (109): It sets the presence of C109 criterion. Only DCE. 

3.3.4.2. V.24 interface 

This type of interface is used in presence of unbalanced transmissions 

both synchronous and asynchronous. 

V.24: Select the communication mode of V.24 interface. 

� Synchronous, for synchronous transmission of data. 

� Asynchronous, for data transmission where clock is obtained directly 

from data both, in transmission and reception. 

In case of synchronous transmission, the parameters to be set are the same reported in § 0 for V.35 

interface (see § 3.3.4.1). 

Start-stop bits: Set the number of control bits to be inserted, 1 or 2, as 

START and STOP bits for data packets transmitted or received. 

Pattern: Set the number of bits composing each single character 

(pattern). 

Baud rate: Set the communication baud rate between DTE and DCE. 

Parity: The Parity bit may be added at the end of each data pattern, for a 

further control over the quality of transmitted and received data. 

� None, no Parity bit is added. 



� Odd, a control over set bits = 1 of data pattern is performed and, if 

the calculation of set bits =1 turns out to be even, a further set bit = 

1 is added at the end of the pattern. On the contrary, if the number 

turns out to be odd a set bit = 0 is added at the end of the pattern. 

� Even, a control over set bits = 1 of data pattern is performed and, if 

the calculation of set bits =1 turns out to be odd, a further set bit = 1 

is added at the end of the pattern. On the contrary, if the number 

turns out to be even a set bit = 0 is added at the end of the pattern. 

Flow control: Set this parameter in order enable a flow control of data 

both in reception and transmission. 

� None, no data flow control is carried out. 

� Xon/Xoff (only TTY), by forcing the control at Xon/Xoff, the device 

interprets the character “Xoff” in order to interrupt the transmission 

and the character “Xon” in order to restart it. 

� Hardware, a criteria control is carried out. 

DCD (109): It sets the presence of C109 criterion. Only DCE. 

3.3.4.3. G.703 CO-DIR interface 

This type of interface is used for balanced transmissions over lines with 

standard G.703 CODIRECTIONAL. 

Line rate: Select the line rate (from 64 to 512 kbit/s, Nx64), used by the 

device for data transmission and reception. 

Violation: Enable the frame violation control for the synchronization of the 

frame. 

PLL Rx: The device hooks up the reception clock to the received data 

clock, with an internal PLL. If you enable such PLL, the device samples 

received data with its internal clock. 

3.3.5. V.11 (X.21) 






(V.24, V.35, V.36, CO-DIR). 

Line rate: Select the line rate (from 64 to 2048 kbits, Nx64) used by the 

device to transmit data. 

Flow control: Set this parameter in order to enable a flow control of data 

both in reception and transmission. 

� None, no data flow control is carried out. 

Clock RX phase: Select on which reception clock edge incoming data 

change, the device samples data on the opposite edge. By default the 

DCE switches data on the clock’s falling edge. Only DTE mode. 

Clock TX phase: Select on which transmission clock edge incoming data 

change, DTE samples data on the opposite edge. By default the device 

switches data on the clock’s falling edge. Only DCE mode. 

Timeout max (sec): Select in the range between 7 to 255. 0 is OFF. Only 

DTE mode. 

3.3.6. Frame Relay (FR2K option) 

You can access the common setup page regarding Frame Relay, only 

with the following configurations: 

� Primary, Primary (CRC4) in LEASED LINE 

� V/X interface 

� Unframed G.703 

Once configured the Frame Relay, tests at IP layers can be executed in 

order to check the IP network; moreover the FOX Test (see § 3.7) can be 

executed to qualify the line about CIR performances. 

The Frame Relay settings can be accessed directly in the Test Menu 

page: 



DLCI: Insert the number relative to the logic channel to use (Data Link 

Control Identifier). 

DLCI length: Select the length of the header belonging to FR frames, 

normally the value used is 2 bytes. 

LMI standard: Set the type of link controlling among the supported ones, 

ITU-T, ANSI or CISCO. The device emulates a UNI interface. 

Fragment. (FRF.12): Select the type of fragmentation of the transmitted 

packets according to recommendation Frame Relay Forum 12. The 

device supports both, UNI and End-to-End fragmentation. It is possible to 

perform tests entering both types of fragmentation. For a proper use of 

this parameter, it is necessary to check out the network configuration. 

UNI Fragment size: Set the maximum size of UNI packet. 

End-to-End Fragment size: Enter the maximum size of End-to-End 

packet. 

HDLC encoding: In case of X.21 line, you can set the line encoding 

between NRZ and NRZI. The last one, was used for SNA connections. By 

inserting the NRZI encoding you need to set also the line bit rate. See § 0. 

3.4. Performing a Call Test 

Use the MAKE A CALL test to manually test the availability of ISDN 

services and/or an audio connection. The instrument allows to receive 

incoming calls and make outgoing calls to a remote terminal. For outgoing 

calls the instrument supports both the overlap and en-bloc mode. 

Use this test to check the information coming from the network and the 

implemented supplementary services. 



The availability of the supplementary services in the instrument menu changes according to the 

current state of the call. For example, you can activate the 3-party conference only after holding a call 

and activating a second call. 

In case of voice call, the audio connection can be established using the 

instrument’s speaker and microphone, or an external handset that is 

connected to the HANDSET jack at the right hand side of the instrument. 

To choose the type of external handset, see chapter 10 ‘Configuring the 

Instrument’. 

The test is available also in POTS mode, allowing tests on analogue line or on a/b termination of an 

NT1+ / NT-IP / IAD. 

To perform the test on POTS line, you need to use the optional AB2000N adapter. 

See Appendix B for information on connections. 

There is another way to perform a call test. When in main menu or in manual test menu, the user can 

start a call simply by pressing a number on the keypad (FAST MAKE A CALL). 

3.4.1. Setting Up a Call Test 

The following parameters can be defined for a call test: 

Called number: Enter the phone number of the user to be called. 

� Remote number for calls to a remote user. 

� Local number for autocalls. 

To add the SENDING COMPLETE information element, enter '#' at the end of the number. ISDN only. 

Sub number: If necessary, enter the subaddress of the called party. ISDN 

only. 

3.4.2. Sending a Call 

When you have defined the setup for the call test, continue as follows: 

1 




2 

Start the CALL test. 

The LED RUN goes on, the LOOP key appears at the left bottom of the 

screen and the START key changes into STOP. Use it to stop the test. 

The test results appear on the screen. 

3 


First line indicates the current status of the test, in this example active on 

channel B2. 

The result pages can also indicate the following items: 

► Messages and disconnection causes 

► Information elements from network (DISPLAY) or user (USER- 

TO-USER) 

► Connected remote number, called number with subaddress, if 

any 

► Charge advise for the call, if any 

► Request, reception of information on supplementary services. 

► Progress Indicator 

In case of POTS access, the instrument displays services in FSK modes. 

When the call becomes active, the following function keys appear on the 

bottom left of the screen: 



4 

4 

4 

To activate the activation/deactivation page of 

supplementary services. See § 3.4.4. 

To send audio tones over the channel: select the softkey and 

use the numeric keypad to send the corresponding DTMF 

tone over the active channel. 

To simulate the disconnection with presence of in band 

tones. 

4 This key can be used to maintain active the current call and 

place a new call. In this way multiple calls can be activated 

simultaneously. 

3.4.3. Answering an Incoming Call 

You can manually answer incoming calls under the following condition: 

► The instrument is in the MAKE A CALL menu and the test is in 

incoming call waiting state. 

► The incoming call is compatible with the number and profile set 

in the instrument. 

In case of voice calls you can use the instrument’s internal speaker and microphone or the external 

telephone handset that is connected to the HANDSET jack in order to communicate with the remote 

user. 

3.4.3.1. POTS configuration 

To answer an incoming call: 

1 An incoming call is received and the device generates an 

acoustic tone. The softkey START changes to ANSWER. 

2 

3 

Answers the call and makes the audio connection. 

Clears the call after connection. 



4 

Simulates the Flash key for service requests to the exchange 

3.4.3.2. ISDN Slave Protocol Configuration 

To answer an incoming call: 

1 An incoming call is received, the instrument generates an 

acoustic tone and sends the ALERTING message. The 

START key changes to ANSWER. 

2 

3 

4 

Answers the call and connects the B channel 

Disconnects the incoming call without connecting the B 

channel 

Clears the call after connection 

The protocol is in Slave mode by default when the instrument is configured as TE or NT1-U. 

3.4.3.3. ISDN Master Protocol Configuration 

In this configuration, see § 3.3, the instrument answers to incoming calls 

without the SENDING COMPLETE information element and the Called 

Number (Cdn) is shorter than the Own/MSN value set in the instrument. 

The instrument sends the SETUP ACK message only and generates a 

special acoustic tone. 

The CALL PROCEEDING, ALERTING and CONNECT messages can 

then be sent by pressing the corresponding softkey. 

The instrument will automatically send the ALERTING message upon 

receipt of the SENDING COMPLETE message or a CDN with length 

higher or equal to the Own/MSN value. 



This allows to check the implementation of the Overlap Sending (DDI) state at the remote interface. 

1 An incoming call is received. The START key changes to 

ANSWER 

2 

3 

4 

Sends the CALL PROCEEDING message 

Sends the ALERTING message 

Sends the CONNECT message and connects the B channel 

The protocol is in Master mode by default when the instrument is configured as NT1-S or NT-E1. 

3.4.4. Checking the Supplementary Services 

Use the SUPPLEMENTARY SERVICES function to check the various 

supplementary services available over the ISDN access. Depending on 

the call status, you can activate, deactivate or check each supplementary 

services. 

1 

2 

3 

Select the Supplementary Services page. 

Move to the selection line of the requested service. 

Choose the requested service. 



4 

5 

6 

7 

3.5. BER Test 

Move to the ACTION line and decide the action to be 

associated with the requested service. 

Insert the parameters as requested by the service. 

Executes the selected action by moving to the first line of the 

page. The supplementary services supported by the 

instrument are listed in the specifications contained in 

chapter 13. 

Display the result page for the invoked service. 

The most used way to verify the transmission quality of a data connection, 

is performing a BER (BIT ERROR RATE) test. In order to perform this 

test, the device sends a sequence of pseudorandom bits (PRBS) on line 

and measures the error bits ratio (BER) as the number of wrong bits 

received divided by the total number of bits received. The final result, is 

then estimated according to absolute parameters or weighed according to 

the standard G.821. 

The test may be carried out in presence of an ISDN connection with 

signalling protocol (e.g. E-DSS1), but also in leased data connection with 

several linking technologies (e.g. 2Mb G.703, V.35). 

Some of the parameters concerning the test have to be configured 

according to the type of connection under verification. 

The final results instead, can be estimated in the same way a part from 

the type of access. 

Various types of test may be performed in order to verify the BER on a 

line, the most common are: 

� Autocall 



� Loop 

� End-to-end 

The ‘Autocall’ mode expects the use of only one testing device, this 

carries out a call toward himself by using ISDN connections with signalling 

protocol over D channel. In this way it is possible to check the quality of 

line up to the local exchange. This is the typical test to carry out in first 

installation phase. 

The ‘loop’ test allows to check a point-to-point connexion by the use of a 

testing equipment and a remote loop. According to the network type, it 

may be a physical loop or a device used as terminal (e.g. a second D2500 

set as ‘act as loopbox’) which performs a logical loop. The ‘loop’ test 

checks the global quality of the line, but it can’t determines the 

problematic route (NT�TE or TE�NT). 

To perform the test in ‘loop’ mode, a remote instrument must be set with 

an active loop on the channel. See § 3.9. 

This test can be used to check the quality of the physical line during installation. To perform the test, 

disconnect all the devices on the line, configure the instrument as NT and set a physical loop at the 

remote end of the tested line 

‘End-to-end’ mode qualifies the line between two terminals (point-to-point), 

in order to carry out this test you have to use two testing equipments and 

place them at the extreme points of the line. It is possible to perform this 

test over ISDN connections with signalling protocol over D channel, and 

over leased connections. The test ‘end-to-end’ allows to check the quality 

of the single line (NT�TE and TE�NT) going to determinate the 

problematic route. 

To perform the test in end-to-end mode, a remote instrument must be set 

with the same test configuration of the local instrument, by pressing the 

START key on both instruments. 

In case of leased connections, without signaling protocol, data is sent 

toward the channel when the softkey START is pressed and the physical 

layer is active. 

3.5.1. Setting Up a BER Test 

Define the following parameters for a BER test: 



Called number: Enter the phone number of the called party. Only with 

protocol. 

� Remote number in outgoing mode (end to end 1B) 

� None in incoming mode (1B) 

� Local number in autocall (selfcall 2B) 

Sub number: If necessary, enter the subaddress of the called party. Only 

with protocol. 

Mode: Select the Call mode. Only with protocol. 

� Outgoing 64k: the instrument generates a call to a remote 

instrument. Once connected the instrument sends its sequence and 

at the same time measures the received one. This makes it possible 

to test a single network section and identify the “noisiest” path. The 

remote instrument must be configured in INCOMING mode with the 

same sequence. 

To make an auto call, select Outgoing 64k and enter your own telephone number as CALLED 

NUMBER. In this case the test is performed using two B channels (128k). In primary access a N*64k 

can be performed by configuring the LOOPBOX mode. See § 3.9. 

Example of an auto call test 

� Incoming 64k: the instrument waits for a call from a remote 

instrument. As soon as a compatible call is received, the instrument 



answers automatically and starts sending and measuring according 

to the set pseudorandom sequence. Use a remote instrument that is 

set in OUTGOING mode with the same sequence. 

Example of end -to-end test 

� Incoming 64k all bear: the instrument waits for a call from a remote 

device. As soon as a call is received, the instrument, without 

performing any compatibility control of the called profile, answers 

automatically and starts to generate the PRBS and measure the 

BER according to the pseudorandom sequence set. 

In ‘Incoming 64k all bear’, the test equipment can be used as an automatic answer remote machine, 

which activates every kind of incoming call an performs a BER test with generation and measure of 

the PRBS sequence. 

Band: To select the bandwidth on which perform the test. Only BASIC 

ACCESS and LEASED LINE mode. 

When the device is set in PRI or PRI(CRC4) it is possible to configure, from COMMON SETUP page, 

the channels’ mapping on which carry out the test. The device supports BER test in Nx64 mode. 

Bit Sequence: Set the pseudo-random bit sequence to be used from the 

list or define your own pattern. 

Pass/Fail Test: Choose the BER value. This value is used to determine 

the pass or fail test condition. Use E-7 (10-7) when no other value is 

requested. The G.821 value calculates the acceptability threshold 

according to the performance target expected by the G.821 

recommendation. The HRX(%) parameter modifies such threshold. 

Error Injection: Insert the number of wrong bits which the device sends 

on line. It is possible to use both manual and automatic mode. In 

automatic mode, you need to insert the BER value to be sent. 

SES Threshold: Choose the number of errors per second in order to 

consider the second as Severely Errored. Use the G.821 default value, 

corresponding at 10-3 when no specific value is requested. 

DM Threshold: Choose the number of errors per minute in order to 

consider the minute ad Degraded. Use the G.821 default value when no 



specific value is requested. In the last G.821 recommendation issue, DM 

result has been cancelled from the recommendation but, the device 

implements the DM measure anyway. 

HRX(%): Enter the variation percentage for the acceptability threshold 

according to the type of call (e.g. National or International). 

If test fails then: Select the action to be taken by the device in case of 

threshold acceptability overcoming, you can shot down the link ending the 

test, maintain it active or continue the test ignoring the result. Used for call 

routing search. 

Auto print: Select the autoprint condition in order to send the test results 

over RS232 serial port, e.g. to download them to a PC. 

� time interval: 15 or 30 minutes 

� DM: when the DM threshold value is overcame 

� End of cycle: results are printed when each cycle ends 

� End of cycle if fails: results are printed at the end of the cycle, only if 

this has ended with FAIL result. 

Duration: Choose the duration of the test from the predefined list or 

define your own duration. 

Measurement cycles: Set the number of tests the instrument has to do 

on the network. Is only active in Outgoing 64k/56K mode. Set together 

with the pause between cycles. 

Pause between cycles: Set the pause between two tests in seconds. Set 

together with the measurement cycles. 

3.5.2. Running a BER test 

When you have defined the setup for the BER test, continue as follows: 

1 

To come back to result page 

2 If testing only the physical line: 

► PRI: Make sure you have made a loop at the 

remote site and have disconnected the line from 

the network. 

► BRI: Make sure you have disconnected the bus 

from each terminal and from the network, connect 

one end to the instrument and loop the other end. 



3 

Start the BER test (or UNFRAMED BER) 

The RUN LED turns on and the test results appear on the screen. 

Only for BER tests over connections with signalling protocol, the device 

displays a third page with data regarding the ISDN call. 

4 

4 

4 


Insert a wrong bit or a specific error ratio in the transmitted 

pattern. 

Reset the counters. 

The three pages show the following results for each call: 

The first line indicates the status of the test. 

► Bit Error Rate (BER) 

► Received bits 

► Errored bits transmitted 

► Errored bits received 

► Receiver synchronisation on the received sequence 

► Number of elapsed seconds with receiver out of synchronism 

► PASS/FAIL test result according to the configured setting (a big 

OK is displayed on the screen when the test result is PASS) 

► G.821 data: SES (severely errored seconds), DM (degraded 

minutes), ES (errored seconds), US (unavailable seconds) in 



absolute value and percentage. According to G.821 

recommendation 

The two threshold acceptability measures (PASS/FAIL), report the FAIL 

(NOK) value if the errored bits received ratio exceeds the threshold 

indicated in the test setup or if the G.821 parameters exceed the values 

provided by the recommendation. In case the Test Pass/Fail is set with 

G.821, both results will be identical. 

If the instrument detects a remote loop, the second results page will 

display the round trip delay value in milliseconds. See § 3.15.3. 

In case of an incoming bit error is detected, the instrument generates a warning sound. 

3.5.3. Performing an Nx64K BER Test 

It is possible to perform a BER test with a band of Nx64Kbps with N 

programmable between 1 and 31(G.704) or fixed at 32(G.703), for primary 

access. 

In G.704 mode, the channels used to transmit and receive the PRBS 

sequence can be sequential or defined by the user. It is admitted every 

channel combination. 

With the parameter ‘Band’, you can select the maximum number of 

channels to be used, once the link is active it is possible to select each 

timeslot on which to run the test. See § 3.3 for further info. 

In Unframed G.703 mode, the line rate is fixed at 2Mbit/s. 

The timeslot zero (0) on the E1 frame is used to synchronise the frame itself and transport the 

overhead control bits. In fw version previous to 2.56, the Unframed BER test used always the timeslot 

zero (0) of the frame to synchronise and transport the overhead control bits. From 2.56 version, with 

bandwidth set at 2Mbit, the device sends bits in unframed mode transmitting data also on timeslot 

zero (0) of the E1 frame. The old 2Mbit mode has been substituted with “31 channel” mode. 



3.5.4. Running a BER test over V/X interface 

VX2000 adapter is fed directly by the D2500, this causes a decrease of the battery duration. 

The V.11/X.21 interface is embedded in the main unit (software option required), no need for external 

VX2000 adapter. This optional adapter is required for other Datacom interfaces (V.24, V.35, V.36, 

CO-DIR). 

The test can be carried out both end-to-end and ‘loop’ mode (single end). 

In the first case it is necessary to put another D2500 (and another 

VX2000, if needed) at the remote end of the line (fig. 3-1). In ‘loop’ mode 

(single end), it is necessary perform a loop over the line. The loop can be 

request to DCE with C141 criterion, through a specific command given to 

the DCE or carrying out a physical loop between TX side and RX side. 

Fig. 3-1 (end-to-end) 

In order to set the parameters and to perform the test, refer to § 0. 

3.6. Performing Generate Traffic test 

Use the GENERATE TRAFFIC test to check the capacity of the access to 

manage traffic over the D channel. You can set the instrument to 

automatically generate several calls at chosen time intervals. 

3.6.1. Setting Up a Generate Traffic test 

Define the following parameters for a Generate Traffic test: 


� Remote number to perform the test to a remote user 

� Local number to perform the test in autocall 

Sub number: If necessary, enter the subaddress of the called party. 



Number of bursts: Set the total duration of the test expressed with the 

number of bursts. 

Pause between burst: Set the time interval between two bursts of calls. 

Parallel calls per burst: Set the maximum number of parallel calls for 

each group of calls. 

Single call duration: Set the minimum duration of the single call. 

Pause between calls: Set the pause between the calls in a group. 

Test traffic on: Select the type of traffic to be tested. The instrument can 

test the call on one of the following parameters: 

� Delivery, the call succeeds and ends when the ALERTING message 

has been detected. 

� Connection, the call succeeds and ends when the CONNECT 

message has been detected. The call remains active for the set 

duration. 

3.6.2. Running a Generate Traffic test 

When you have defined the setup for the Generate Traffic test, continue 

as follows: 

1 

2 


Start the Generate Traffic test. 

The LED RUN goes on and the test results appear on the screen. 

The status line indicates the status of the test. 

During the test the instrument makes a loop on every active B channel. 

The screen indicates the total number of calls and the number of failed 

cycles the instrument has detected. 



“Failure” means that the instrument was not able to make all calls. 

To view and analyze failures: 

3 

Scroll through the pages indicating a failed call with related 

information. Observe that the cause number for each failure 

appears on the screen. 

This example shows Failure 1 with related information, such as the time of 

the failure, the call with the corresponding burst that has failed, and the 

cause number. 

3.7. Performing a Fox Test 

Use the Fox Test to check the line quality for the interface selected. The 

content of the frames leaving from the device (and that should come back 

not corrupt) is the string “THE QUICK BROWN FOX JUMPS OVER THE 

LAZY DOG” (all English consonants) plus all the digits from 0 to 9 plus all 

vowels plus *#. 

This test should be used especially when qualifying the Frame Relay 

accesses (even though it works also for other accesses). In this situation, 

the Frame Relay must be enabled in the main page (Test Menu) of the 


3.7.1. Setting Up the Fox Test 

Define the following parameters for the Fox test: 



Mode: Choose to generate traffic both in TX and RX or or to check only 

the reception side. 

CIR (Kbps): Committed Information Rate, it’s the target throughput in 

Kbps over a time constant period. 

OK threshold (CIR %): Set the threshold of CIR to consider the test as 

OK, e.g. with a 100% threshold the measured CIR must be equal to the 

target CIR previously set. 

Data field length: Choose in a range from 64 to 2000 byte. 

Sampling period: Choose among 10 seconds, 30 seconds, 1 minute, 5 

minutes, 10 minutes, 30 minutes and 60 minutes. 

Duration: Choose among User (15 s), 1 minute, 15 minutes, 60 minutes, 

24 hours or Continuous. 

3.7.2. Running a Fox test 

When you have defined the setup for the Generate Traffic test, continue 

as follows: 

1 

2 


Start the Fox test. 



These are the other data that follow: 



► Frames (TX and RX) 

► Rate (kbps) measured 

► CIR (kbps) measured 

► CIR (%), according to the threshold selected in the setup page 

(it influences the pass/fail result) 

► Frames lost 

The OK threshold (CIR %) determines the result of the test. If the 

percentage between target CIR and measured CIR is lower than the 

threshold, then the result will be FAIL. In case of a succesfull test, a big 

OK is displayed on the screen. 

The second page provides a graphical representation of the CIR along the 

executions of the test. 

3.8. Performing a U-Interface Test (NT1-U only) 

Use the U-INTERFACE test to check the line quality of the U interface to a 

user. Line quality is measured in analog way. 

3.8.1. Setting Up the U-Interface Test 

Define the following parameters for a U-interface test: 

Load (mW): Set the load in milliwatts inserted on the line. Use the 1100 

mW default value when no other value is requested. 

Vmin threshold: Set the minimum voltage value under which the 

instrument resets its line interface. Use the 28 V (ETR080) default value 

when not other value is requested. 

Line Code: Set the line code at 2B1Q or 4B3T. NT-U (BRI) only 

Power supply bit PS1: Choose PS1 as indicated in the table below. Only 

for 2B1Q. 

Power supply bit PS2: Choose PS2 as indicated the table below. Only 

for 2B1Q. 



PS1 PS2 Description 

0 0 Primary power and back-up battery failure. 

0 1 Primary power failure. 

1 0 Back-up battery failure. 

1 1 Normal primary power and back-up battery. 

3.8.2. Running a U Interface Test 

Table 3-2 PS Bit Assignments 

When you have defined the setup for the U-Interface test, continue as 

follows: 

1 



The central part of the screen automatically gives information on the line 

voltage and line current. 

When you use the 2B1Q line code, the bottom lines give the activation 

and de-activation time. These times are automatically calculated when 

you have connected the instrument for the first time to the line and made a 

call. 

2 

Start measuring the binding resistance of the U interface. 


3.9. Acting as Loop Box 

The ACT AS LOOP BOX function allows to automatically answer to 

incoming calls and loop the corresponding B channels. 

You can also set up the LOOP BOX to perform a compatibility check on 

incoming calls based on the profile and the Own/MSN value set in the 



Common Setup menu. In this case only compatible calls will be accepted. 

Incompatible calls will be rejected. 

By default this mode is automatically active in the background when other 

tests are performed. It is used to perform BER tests in auto call mode, § 

3.5, or where an instrument with automatic answering is necessary. 

The manual answer to incoming calls is configured as default; then in case of an incoming call, the 

instrument displays the B Channel status page (see § 7.4) where the user can decide whether he 

should answer or not. 

3.9.1. Setting Up a Loop Box 

Define the following parameters to activate the loopbox function: 

Call accept: Choose the control mode on incoming calls. 

� Only Compatible, the loopbox function only accepts incoming calls 

compatible with the set profile. 

� None, the loopbox function does not accept incoming call, sending 

to the remote the disconnection cause 21 (Call Reject). 

� All, the loopbox function accepts all incoming calls. 

Disc. Cause: The disconnection cause sent to the remote can be: 

� Default (21), default cause (Call Reject). 

� User (..), the user can define his own disconnection cause. 

3.9.2. Setting Up a Call-Back 

You can simulate an exchange cross-connection through the Call forward 

function or make a return call (call-back) to the calling number. The B 

channel Status function displays call-back connections, if any. See 

chapter 7. 

To activate the call forwarding and the call-back features, you have to 

setup the following parameters: 

Call forward: to activate the cross-connection function. Upon receipt of an 

incoming call compatible with the set profile, addressed to a number 

(CDN) that is different from the one set as Own/MSN in the Common 



Setup menu, an outgoing call is made to the called number (CDN). Once 

the call is active, the B channels are connected (cross-loop). This function 

is active only if the Own/MSN field is configured, in P-P or with Master 

protocol mode. See § 3.4.3.3. 

This mode can be used to simulate a call from one port to the other port of an NT+ / NT-IP or 

exchange. To perform this test, configure the instrument as LT-U (option LT-U2K) o NT-S or NT-E1, 

connect it to the device, enter a number in the Own/MSN field (i.e. 123), activate the Call forward 

function and enter a number (i.e. 555) from the remote terminal. The instrument will recognize that the 

call is not addressed to it and will send it to the called number. 

Callback: To activate the call-back function. The instrument can be set to 

generate a direct outgoing call to the calling number (CGN) for each 

incoming call. The function can be activated only if the calling number is 

determined. The outgoing call will be generated: 

� Immediate, with connection, after the reception of the incoming call. 

� After connection end, after the remote disconnection of the incoming 

call, accepted and connected in loop. 

� After delivery end, after the remote disconnection of the incoming 

call, accepted (ALERTING), but not connected. 

� None, never. 

Answer: If the Callback is set at “None”, it is possible to choose the 

answer mode between: 

� Automatic, the device answers automatically to the incoming call 

� Manual, when an incoming call is received, the device makes a 

warning tone, the “bell” item appears on the upper part of the screen 

and the user can decide if answer or not. See chapter 7. 

Wait time: Waiting time between the remote disconnection and the callback 

call. 

Duration: Maximum duration of the outgoing call-back call. 

Escape#: The digits entered in this field will be dialed before the called 

number if the incoming call CGN is of National or International type. The 

dialed number will be made up of . 

Max call-back num: to set the maximum number of simultaneously active 

call-back calls. A loop of the B channel is performed on the last call with 

no call-back. PRI only. 



By setting the < Immediate, with connection.> value in the field and performing a BER 

test in autocall, § 3.5, the measurement will be simultaneously made on NB channels, where N is 

equal to


Packet length: Set the length of the data packets. Set together with the 

packet content. 

QMD bits: Activate or deactivate the QMD bits for each transmitted 

packet. The Q bit indicates the transmitted packet as data or commands, 

the M bit indicates that the packet is the prosecution of a previously 

transmitted packet, the D bit indicates that the transmitted packet is 

acknowledged by the local network or the remote terminal. 

Transmission speed: Set the transmission speed of the packets. 

Echo received data: Activate or deactivate the echo on received data. 

Call request facility: Set None or User in order to insert a Facility field 

into the Call Request message. 

CUG X.25: (Closed User Group) This supplementary service is used to 

define a closed group of users and create a private virtual network, in 

which only the members can communicate. Set the Closed User Group 

(CUG) value between No, 0 (Normal), 0 OA (Outgoing Access) and 0 

Bilateral. 

Call request user data: Set None or User in order to insert a User Data 

field into the Call Request message. 

Own address: Enter the X.25 number assigned to the tested access for 

compatibility on incoming calls. 

TEI: Use the TEI value assigned to the access. X.25 service uses a fixed 

value of TEI. 

LCI: Logical Channel Identifier, which must be set at one of the values of 

the LCI range used by the access. The instruments uses this value for 

outgoing calls, while accepting any LCI value for incoming calls. 

Window layer 3: Number of level 3 packets which can be transmitted 

without waiting for a reply ("3" by default). 

3.10.2. Running an X.25 on D Channel Test 

When you have defined the setup for the X.25 on D Channel test, 

continue as follows: 

1 




2 

Start the X.25 on D Channel test. 


3 

3 


Reset the test counters 

The result pages display the following information: 

► The status of the test 

► The number of packets, bytes and bps rate (bits per second) 

that the instrument has transmitted and received 

► Statistics on transmitted and received packets. The data also 

gives indication of invalid packets the instrument has received 

and packets with HDLC (High Level Data Link Control) errors. 

Follows a clarification table of the various items regarding the results’ 

pages: 

Packets: Number of transmitted and received packets. 

Bytes: Number of transmitted and received Bytes. 

Bps: Throughput in transmission and reception expressed in bit per 

second. 

DATA: Number of transmitted and received DATA messages. 

RR: Number of transmitted and received RR messages. 

RNR: Number of transmitted and received RNR messages. 



Reset: Number of transmitted and received RESET messages. 

ResCNF: Number of transmitted and received RESET CONFIRM 

messages. 

Restart: Number of transmitted and received RESTART messages. 

RestCNF 

: 

Number of transmitted and received RESTART CONFIRM 

messages. 

Reject: Number of transmitted and received REJECT messages. 

Int: Number of transmitted and received INTERRUPT messages. 

IntCNF: Number of transmitted and received INTERRUPT CONFIRM 

messages. 

Diagnost 

: 

Number of diagnostic packets transmitted and received. 

Invalid: Number of invalid packets transmitted and received. 

Outseq.: Number of out of sequence packets transmitted and received. 

Pages 4 and 5 concern completely L2 frames statistics. 

The device has the possibility to send a specific message using X.25 user data packet on the D 

channel. The maximum length of the message is 128 bytes. For further information refer to PC108 for 

Windows User’s manual. 

3.11. Testing the X.25 on the B channel 

Use an X.25 on the B channel test to verify the operation of the X.25 

service and the throughput on reception and transmission side of the 

ISDN line, in Vc (virtual circuit) or pVc (permanent virtual circuit) mode. 

3.11.1. Setting Up an X.25 on B channel test 

Define the following parameters for an X.25 on B Channel test: 

Mode: Choose the Call mode. 



� Vc Incoming/Outgoing, the instrument waits/sends an X.25 call over 

a Virtual channel 

� pVc Incoming/Outgoing, the instrument waits/sends an X.25 call 

over a permanent Virtual channel (leased line) 

� Automatic Incoming, the instrument waits an X.25 call and sets itself 

depending on the remote configuration 

Called number: Enter the ISDN phone number of the called party. 

� Remote number to make a call to a remote user 

� Own number to make an auto-call 

Sub number: If necessary, enter the sub number of the called party. 

Packet content: Set the contents of the data packets to be transmitted. 

Set together with the packet length. 

Packet length: Set the length of the data packets. Set together with the 

packet content. 

QMD-Bits: Activate or deactivate the QMD bits for each transmitted 

packet. The Q bit indicates the transmitted packet as data or commands, 

the M bit indicates that the packet is the prosecution of a previously 

transmitted packet and the D bit indicates that the transmitted packet is 

acknowledged by the local network or the remote terminal. 

Transmission speed: Set the transmission speed of the packets. 

Echo received data: Activate or deactivate the echo on received data. 

LCI: Enter an identification number for the channel in use, to avoid the 

interfere of other terminals on the data transmission. 

Window layer 3: Number of level 3 packets which can be transmitted 

without waiting for a reply ("3" by default). 

Layer 2: Choose the layer 2 simulation mode. 

� DTE, to set the device as DTE (Data Terminal Equipment) 

� DCE, to set the device as DCE (Data Communication Equipment) 

� DXE, the device sets itself depending on the remote configuration 

(only for incoming call mode) 

In an end-to-end test, one test set must be configured as Outgoing and one as Incoming, to perform 

the test first start the equipment sets as Incoming and then the device sets as Outgoing. 



3.11.2. Running an X.25 on B channel test 

Once defined the setup for the X.25 on B Channel test, continue as 

follows: 

1 

2 


Start the X.25 on B Channel test. 


3 



► The status of the test 

► The number of packets, bytes and bps rate (bits per second) 

that the instrument has transmitted and received 

► Net throughput on transmission and reception side 

► Virtual circuit in use (pVc o Vc) 

► Layer 2 simulation mode (DTE o DCE) 

► Statistical data of transmitted and received frames with 

indication of invalid frames 

► Called number, remote and sub 

Follows a clarification table of the various items regarding the results’ 

pages: 

Packets: Number of transmitted and received packets. 

Bytes: Number of transmitted and received Bytes. 



Bps: Throughput in transmission and reception expressed in bit per 

second. 

PVc: Informs if it is a pVc or not, and if Layer 2 is configured as DTE 

or DCE. 

LCI: LCI assigned. 

DATA: Number of transmitted and received DATA messages. 

RR: Number of transmitted and received RR messages. 

RNR: Number of transmitted and received RNR messages. 

Reset: Number of transmitted and received RESET messages. 

ResCNF: Number of transmitted and received RESET CONFIRM 

messages. 

Restart: Number of transmitted and received RESTART messages. 

RestCNF 

: 

Number of transmitted and received RESTART CONFIRM 

messages. 

Reject: Number of transmitted and received REJECT messages. 

Int: Number of transmitted and received INTERRUPT messages. 

IntCNF: Number of transmitted and received INTERRUPT CONFIRM 

messages. 

Diagnost 

: 

Number of diagnostic packets transmitted and received. 

Invalid: Number of invalid packets transmitted and received. 

Outseq.: Number of out of sequence packets transmitted and received. 

Pages 4 and 5 concern completely L2 frames statistics. 

3.12. IP Ping Test 

Use this test to verify the correct operation of the Internet connection and 

check if a remote network or host is reachable, by using the ICMP 

protocol (Internet Control Message Protocol). The response from the 

remote will provide information about the net structure. 

3.12.1. Setting Up an IP Ping test 

Define the following parameters to perform an IP Ping test: 



Called number: Enter the ISDN phone number of the called party. Only 


Sub number: If necessary, enter the sub number of the called party. Only 


Dest. IP/Dest. URL: Enter the IP destination address to Ping. 

1 

Press the key ASTERISK to switch from the field “Dest. IP” 

to “Dest. URL” and viceversa. 

Ping request number: Enter the number of Ping (Echo) requests. 

Max response time (sec): Enter the maximum response time between 

the Ping requests. The test set waits this time before considering the 

request expired. 

Data field length: Assign data field length of the Ping packet, to verify if 

the remote is reachable a part from the packet length. 

Don’t fragment: To verify if the remote is reachable whether with 

fragment or not fragment packets. 

Pause inter ping (msec): Assign a pause for every ping request. 

Protocol type: IP or IP over PPP, used on links where an initial 

authentication phase is needed. 

Authentication: Assign the authentication mode for IP over PPP 

protocols. Use ‘PAP and CHAP’ value to support both modes at same 

time. 

User Name: Enter the User name for the identification. Only for IP over 

PPP. 

Password: Enter the User password. Only for IP over PPP. 

IP Address: Select the User IP address mode: 

� Static: The IP address is manually configured by the User 



� Dynamic: An assignment request of the IP address is sent by the 

User. Only for IP over PPP 

Local IP: Enter the local IP address. Only in Static mode. 

PPP type: Allows to select the PPP protocol simulation type performed by 

the device: 

� Client: The device simulates a user terminal, with authentication 

request to a remote server. 

� Client + link verify: The device, in Client simulation, sends an echo 

request every ten seconds in order to verify if the link is still active. 

� Server: The device simulates a server and allows to verify the 

authentication phase coming from a remote terminal. 

� Server + link verify: The device, in Server simulation, sends an echo 


DNS server: Enter the DNS address which allows the solution of names 

from IP to URL and vice versa. 

3.12.2. Running an IP Ping test 

Once defined the setup to perform the IP Ping test, continue as follows: 

1 

2 

Come back to result page 

Start the IP Ping test 


3 



The Status line indicates the status of the test; and the PING line indicates 

the status of the Ping; Idle, Waiting for reply or Pause. 

► PPP link state and response messages (once the link is active, 

the PPP item changes in PING) 

► Date, time and elapsed time 



► Msg, ICMP (Echo) state and response time or messages 

transmitted from the remote to the device, with relative IP 

address 

► Echo requests transmitted and Echo reply received 

► Minimum, medium, maximum response time 

► Local, Server, Remote and Reply IP address 

► Number of Ping transmitted to the device from a remote user 

with relative IP address 

It’s also possible to interrupt the actual Ping phase, change the remote IP 

address and start a new burst of Ping 

4 

5 

6 

3.13. IP Trace Route 

To interrupt the actual Ping phase. 

To change the remote IP address. 

To start a new burst of Ping requests. 

Through the IP Trace Route test, the user can display all the remote IP 

address met before reaching the IP destination address. Moreover the 

response times of every single remore IP address are provided in order to 

verify possible bottle necks on the line. 

3.13.1. Setting Up an IP Trace Route test 

Define the following parameters to perform an IP Trace Route test: 

Called number: Enter the ISDN phone number of the called party. Only 


Sub number: If necessary, enter the sub number of the called party. Only 


Dest.IP/Dest. URL: Insert the IP or URL destination address 



1 



Max response time (sec): Maximum response time between Ping 

requests. The test set waits this time before considering the request 

expired. 

Protocol type: IP or IP over PPP, used on links where an initial 



protocols. Use ‘PAP and CHAP’ value to support both modes at same 

time. 


PPP. 


IP Address: Select the User IP address mode: 

� Static: The IP address is manually configured by the User 

� Dynamic: An assignment request of the IP address is sent by the 

User. Only for IP over PPP 

Local IP: Enter the local IP address. Only in Static mode. 













3.13.2. Running an IP Trace Route test 

Once defined the parameters to perform the IP Trace Route test, continue 

as follows: 



1 

2 


Start the IP TRACE ROUTE test. 


3 


The results pages can indicate the following items: 

The status line indicates the status of the test; the PING line indicates the 

PING status; 


► Local and Destination IP address 

► Number of PING requests 

► Trace Route with the addresses met to reach the Destination IP 

address and the corresponding response time (msec) 

Moreover it’s possible to interrupt the present IP traffic phase, change the 

setup and start a new Trace Route. 

Interrupt the running Trace Route. 

Change the test parameters. 

Start a new Trace Route using the same connection. 

To print the test results. 

To save the test results in the memory of the instrument. 



3.14. IP Generate Traffic 

Through the test IP GENERATE TRAFFIC, you can simulate a real IP 

traffic condition. This allows to carry out a more exhaustive test toward the 

network, instead the simple IP PING. 

The equipment performs a data transfer between hosts by simulating the 

functionalities of both. This consent to carry out a test using two devices 

or one device and a standard TFTP server. 

Among the test results provided, a statistic of the throughput reached 

during the transfer is displayed. Such statistic is only indicative and it can’t 

represent the absolute maximum value available on the network 

3.14.1. Setting Up an IP Generate Traffic test 

Define the following parameters to perform an IP Generate Traffic test: 

Called number: Enter the remote terminal’s ISDN phone number. Only 


Sub number: If necessary, enter the remote terminal’s ISDN sub number. 

Only with protocol. 

Dest. IP/Dest. URL: Insert the IP or URL destination address 

1 



Traffic: Select the type of traffic to simulate: 

� TFTP Download, data is transferred from the remote host to the 

device. This allows to simulate a file downloading toward the 

network. The device asks for the transfer of a predefined file that 

must be already present at remote server site. Problems won’t occur 

if using as server a second equipment (e.g. D2500). 

� TFTP Upload, data is transferred from the device to the remote 

server. The remote server must be enabled for the service TFTP 

and must has appropriate qualifications in order to write the file 



transferred. Problems won’t occur if using as server a second 

equipment (e.g. D2500). 

� TFTP Upload+Download, the device performs a simulation both in 

upload toward a server and in download from the remote server. 

Data is transferred in both directions. 

� TFTP Server, the device simulates a server which waits for 

commands on behalf of a remote equipment. 

� Ping Packets, the device performs a traffic simulation by sending 

Ping packets, as it happens in the “IP Ping” test. 

� HTTP Download, data are transferred for a remote HTTP server to 

the instrument. This allows to simulate a web page download 

through the network. The instruments doesn’t need the download of 

a predefined web page. 

� FTP Download, data are transferred from a remote FTP server to 

the instrument. This allows to simulate a file download through the 

network. The PASV mode is implemented: the server is informed by 

the client that it is in passive mode. Then the server provides 

(opens) a port to be used for data traffic. 

File name: Enter the name of the file to transfer (FTP Download only). 

File length (KB): Enter the file length to transfer in KByte. 

Anticipation window (blocks): Enter the number of blocks sent by the 

device before waiting the acknowledge message reception. The device 

implements a TFTP standard Client, such protocol expects an anticipation 

window equal to a block, this means that, for each data packet sent, a 

verification is waited by the sender. The more you increase the 

anticipation window’s number, the faster the throughput obtained is, but 

the system may doesn’t work with a standard TFTP server. Problems 

won’t occur if using as server a second device. 

Packets timeout (s): Set the maximum waiting time for the 

AKNOWLEDGE message, after which the device considers the 

transmitted packet lost. 

Measurement cycles: Set the number of cycle tests the instrument has to 

do on the network. 

Pause between cycles: Set the pause among cycles. Set together with 

the measurement cycles. 



Protocol type: Select IP if performing a traffic simulation over a direct IP 

network or select IP over PPP for connections where an initial 



protocols. With the value ‘PAP and CHAP’, the device carries out the 

authentication in one mode and only if fails, it tries to use the remaining 

one. This allows to ignore the authentication protocol used by PPP server. 


PPP. 


IP address mode: Select the User IP address mode: 

� Static: The IP address is manually configured by the User. 

� Dynamic: An assignment request of the User’s IP address is sent to 

the Server by using the DHCP protocol. Only for IP over PPP. 

Local IP: Enter the local IP address. Only in ‘IP address mode: Static’. 













3.14.2. Running an IP Generate Traffic test 

Once defined the setup to perform the test, continue as follows: 

1 

2 


Start the IP Generate Traffic test. 




3 



The Status line indicates the status of the test and the TFTP line indicates 

the status of the file in transfer: Uploading, Downloading, Complete and, 

at the end of the test, the disconnection causes. 


► Number of the cycle in progress 

► Blocks, Bytes and Throughput, in Kbps, received in Downstream 

and transmitted in Upstream. Data depend on the file length to 

be transferred and on the type of transfer to be simulated. 

► Local, Server and Destination IP address 

► Transmitted errors both in Downstream and Upstream 

► Minimum, average and maximum Throughput, in Kbps, received 

in Downstream and transmitted in Upstream. 

It’s also possible to interrupt the actual IP traffic phase, change the setup 

and start a new IP traffic generation 

4 

5 

6 

To interrupt the actual Ping traffic phase 

To change the destination IP address and/or the other 

parameters 

To start a new Ping traffic generation using the same internet 

connection 

3.15. Tone Generator and Measurements 

The test allows to use the device as generator of sinusoidal signals 

included into the phonic band 300 - 3400 Hz, with the possibility to 

perform both fixed frequencies and programmed scansions. The output 

level is selectable as well between +3 and -45dBm0. 



The output signal is generated at PCM code level if you the test is carried 

out toward digital channel and at analogue level over POTS interface. In 

this case the maximum output level is 0dBm and it is referred to a 

characteristic impedance of 600 Ohm. 

Besides the tone generator, you can also use this test to perform phonic 

band measurements both at PCM and Analogue level. Possible 

measurements are: 

� Frequency 

� Level in effective value (RMS) 

� Noise 

� Line’s round trip delay (ECHO) 

The test allows to send on line a single tone or to carry out a scansion of 

the band both, in manual and automatic mode. The level value is 

definable by the user as well as the scanning time and the delta frequency 

in Hz. 

Used in couple with a remote receiver it is possible to check for instance, 

the correct opening and transparency of the audio channel in case of 

conversion into digital lines, or it is possible to check the quality of the 

band considering parameters such as distortion and line attenuation. 

The Tone Generator and Measurement test over POTS requires AB2000N option. 

3.15.1. Setting up a Tone Generator and Measurement test 

Define the following parameters for a Tone Generator test: 


Sub number: If necessary, enter the subaddress of the called party. ISDN 

only. 



Freq start (Hz): Insert the initial frequency value (range from 300 to 

3400). If the value is different from Freq.stop, the device performs a 

scansion of frequencies included between the two values. 

Freq stop (Hz): Insert the final frequency value (range from 300 to 3400). 

If the value is different from Freq.start, the device performs a scansion of 

frequencies included between the two values. 

∆F (Hz): Define Delta value (gap) to use to pass from a tone frequency to 

another in manual mode. 

RMS Level (dBm0): Choose the width for the sinusoidal tones generated. 

Sweep Time: Select the waiting time between one tone and the other, 

sending tones may be carried out manually by selecting ‘Manual’. Only if 

Freq.start and Freq.stop are different. 

Automatic echo print: Select the automatic printing condition in order to 

send the test results over RS232 serial port. The printing starts each time 

variations on response time measurement are detected. 

3.15.2. Running a Tone Generator and Measurement test 

Once defined the setup for test, continue as follows: 

1 

2 

3 

4 

5 

Come back to result page 

Start the Tone Generator test 

To begin to send tones toward the acoustic band. 

To stop sending tones toward the acoustic band. 

To send another tone (next), in case of ‘Sweep Time: 

Manual’. 



5 

5 

In order to send the next tone, in case Freq.start is equal to 

Freq.stop. 

In order to send the previous tone, in case Freq.start is equal 

to Freq.stop. 

3.15.3. Measuring the B channel round trip delay (ECHO) 

The delay can be measured in ISDN configuration, after connecting a B 

channel. The delay is the time needed to transport a byte from the local to 

the remote terminal and back. Its value depends on the call routing. 

The line response time measurement can’t be carried out in case the tone generator test is in 

progress. 

To measure the ECHO time: 

1 Activate a connection to a terminal with data loop (if not 

already existing). 

2 

3 

If the Tone Generator test is active, press this key in order to 

stop it. 

To start the line response time measurement. 

In the result pages it is displayed the minimum and maximum response 

time and the level’s measurement of the eco signal (RMS). 

The ISDN is oriented to transport one byte at a time (byte-timing). 

For a correct measurement, the remote terminal must make a data loop 

on the channel. 



This measurement can be useful in case of users with video terminals that are sensitive to the delay 

between B channels. A channel can have a different delay values for different calls, according to the 

call route in the switching exchanges. 

The instrument can measure delay up to ten seconds. In case of higher 

values, or if the remote terminal does not make the data loop, the 

instrument will inform the user with the "NO REMOTE LOOP". 

Once the delay has been measured, the delay value is saved until the call 

is disconnected. Subsequently the active call can be looped with the 

LOOP softkey. See § 3.4.2. The delay for this call is displayed on the B 

channel status page. See chapter 7. 

3.16. Using the D1029N Adapter (NT1-S only) 

Use the D1029 adapter to supply phantom power supply over the S0 BUS 

in order to verify the proper working of the terminal equipment (TE) in 

standard and emergency mode. 

To ensure proper verification, make sure you have disconnected the TE from the NT1 network 

termination. 

The D1029 takes its own power from the ‘AUX’ connector located in the 

AC/DC adapter supplied with the instrument. See Appendix B for 

information on connections. 

The D1029 connector, a RJ45 connector indicated as “FROM 

ANALYZER”, must be connected to the instrument’s RJ45 connector 

indicated as ’S/T’. 

The D1029 enables to simulate both the standard and emergency 

operating condition, by inverting the phantom power supply polarity. The 

device provides the tested terminal with approx. 1100mW in standard 

condition and approx. 430mW in emergency condition. 

To choose the desired mode, use the switch located on the side of the 

D1029. 

The two LED’s located on the front panel allow for checking the absorption 

of the tested terminal. When the LED’s are off, the terminal absorption 

over the S BUS is either null or lower than 3 mW. 

The green “NORMAL” LED goes on if absorption is lower than 1100mW 

when simulation standard operation, and the red “EMERGENCY” LED 



goes on if absorption is lower than 430mW when simulating the 

emergency operation. 

The LED’s flash to indicate an excessive absorption of the tested terminal 

(with reference to the power supplied by the D1029). 

3.17. LT-U Simulation (LT-U2K option) 

This option allows for simulating the U interface of a Basic access of an 

ISDN exchange and performing call tests from and to an NT1 or NT1+ 

termination. This allows to check configurations and functions of the 

socket and the connected devices over the S/T interface and the a/b 

analog interface for the NT1+. 

To power the U interface, use the LT-U adapter. See Appendix B for 

information on connections. 

Connect the LT-U ADAPTER to the “AUX” connector of the AC/DC Aethra 531000971 adapter 

supply with the instrument. 

After connecting the U connector of the instrument and the U line of the 

NT socket to the LT-U ADAPTER, set Basic Access, LT-U mode, on the 

instrument. The functions are the same as the NT-S mode. 

This mode also allows for making calls from one user terminal to the other 

one by simulating a self-call. To do it, go to the “LOOPBOX” menu window 

and follow the instructions given in paragraph 3.9. 

3.18. S/T-BUS Wiring Test (WT2000 option) 

Use an S/T-BUS test to verify the correct installation of the S/T BUS. The 

instrument detects polarity inversions, interruptions or short circuits 

between the bus pairs. 

The test must be performed when the ISDN connection is not active. To 

perform the test the WT2000 option is necessary. This option consists in 

two adapters, one Master (WT2000M) and one Slave (WT-Slave). 

Connect the WT2000M to the instrument to the V.11 plug with the 

corresponding cable. Connect the WT2000M to the tested bus and close 

the other bus end with the WT-Slave. Disconnect both the NT and TE on 

the BUS, if any. 



To ensure proper verification, make sure you have disconnected the TE and the NT1 network 

termination from the S/T BUS. 

For information on connections see Appendix B. 

3.18.1. Setting up an S/T-BUS Wiring Test 

No parameter setting is necessary for the test. 

3.18.2. Running an S/T-BUS Wiring Test 

When you have defined the setup for this test, continue as follows: 

1 

2 

Connect the instrument as displayed on the screen and 

press the RIGHT CURSOR key. 

► Connect one end of the bus to the WT2000M 

adapter and close the other end with the WT-Slave 

adapter 

Start the test 

The result page displays the following information for each call: 

► Presence (and value) of voltage on the bus 

► Short-circuited pairs 

► Interrupted pairs 

► Crossed pairs 

► Presence of closing resistances 

► Resistance value in ohms 

The results are shown both in text and graphic format with indications for 

each wire of the S/T-BUS. 



3.19. AT Terminal (TTY) test (V.24 asynchronous) 

This feature allows the device to simulate a TTY terminal. In this way you 

can, for instance, send AT commands toward a modem, a terminal 

adapter or a user’s router for configurations and debugs. 

The instrument stores into an internal buffer characters both transmitted 

and receiver, with the possibility to manage and display special 

characters. 

This test is available only in VX mode with asynchronous V.24 interface. See § 3.3.4.2. 

3.19.1. Setting up an AT Terminal (TTY) Test 

Define the following parameters for the AT Terminal (TTY) test: 

Mode: Select the message sending mode. 

� Character, by selecting this mode each single character is sent as 

soon as it is pressed on the keyboard. 

� Message, by selecting this mode the entire outgoing message is 

sent only after the completion of it. 

Auto LF: In ‘Message’ mode, control characters are inserted at the end of 

the message. These characters are responsible for data traffic regulation 

and are: CR (Carriage Return, in order to place the next message at the 

beginning of the line) and LF (Line Feed, in order to place the next 

message at the head line). Only in ‘Message’ mode. 

� Yes, to insert automatically the control character LF at the end of the 

message 

� NO, to disable the insertion of the control character LF 

Show control characters: To show on the screen the control character 

CR and LF (not printable). This field regards only messages in reception. 

� YES, the control characters CR and LF are shown on the screen, 

but not interpreted. 

� NO, the characters are interpreted, but not displayed. 



If in the COMMON SETUP page regarding V.24 interface, see § 3.3.4.2, the field ‘Flow control’ is set 

at ‘Xon/Xoff’, displaying of control characters is forced at ‘NO’ because Xon/Xoff are control 

characters as well and so they have to be interpreted. 

Local echo: By setting this parameter at ‘YES’, the device reports on 

screen the characters or messages sent. 

3.19.2. Running an AT Terminal (TTY) Test 

Once the test configuration parameters have been set, continue as 

indicated below: 

1 

2 

3 


Start the test. 

To enter the characters or the messages to be sent. 

Now you will be able to send messages or characters: 

5 

To enter capital letters characters. 

To enter small letters characters. 

Special characters. Es.: space, punctuation, etc.. 

Hexadecimal characters. 

To exit from the editing page. 

To cancel the last character inserted. Only in “Mode: 

Message”. 

To cancel the whole string inserted. Only in “Mode: 

Message”. 

To send the message. Only in “Mode: Message”. 

To select the type of character to be set (capital, small, 

punctuation or hexadecimal). 



6 

Select the character and press ENTER. 

In the results page will be displayed all the messages transmitted and 

received, identified into two distinct colors: 

► White text over black background for messages transmitted by 

the device. 

► Black text over white background for messages received by the 




4. PREDEFINED TESTS 


You can save the setup of the most frequent used tests for later use. This 

setup is then added to the list of predefined tests. Make use of these 

predefined tests to have a quick and faultless test setup of your 

instrument. It must be noticed that the configuration of the test is saved 

and not its result. 

Navigation for the predefined tests is illustrated in Fig. 4-1. 

4.2. Saving a Predefined Test 

Fig. 4-1 Navigation of the Predefined Tests 

First you have to add a predefined test setup to memory. The following 

example shows how to save the test setup of a BER test: 

1 

The internal memory of the device can store up to 10 different predefined setup for each kind of test. 

Open a SETUP: BER screen. The bottom line of the last 

CHAPTER 4 - PREDEFINED TESTS 89


2 

3 

4 

SETUP page is always defined as ‘Save setup as 

predefined’. 

Open the ‘Save setup as predefined’ screen. 

Enter a label for each test set up. Use the numeric keypad to 

enter characters. Numeric key 1 is used for entering a space 

or the following characters: 

+ - ? ! , . : “ & $ ( ) / % @ 

The label can include max. 12 characters. 

Confirm and save the test setup. 

The setup has been added to the list of predefined tests. 

The last test you have performed is automatically saved as 'Last test'. 

4.3. Performing a predefined test 

When you have saved one or more predefined tests, you can make use of 

them to have a quick and faultless test setup of your instrument. 

The following example shows how to run a predefined BER test. 

1 

Open the TEST MENU screen. 

90 CHAPTER 4 - PREDEFINED TESTS


2 

3 

4 

5 

6 

Open the PREDEFINED TESTS screen. 

Select the desired test, i.e. BER. 

Select the test, i.e. Aethra Tel. 

Connect the instrument as shown. 

The device configures itself with all the test parameters in the way they have been saved. 

Start the test. The LED RUN is on and the test results 

appear on the screen. 

For example: 

You can modify/optimise your predefined test setup at any time with the SETUP key. Change your 

setup and save it again. 

You can recall reconfiguration of the last test you have performed by 

selecting the “Last test” option in the “Selected test” field. 



4.3.1. Default Predefined Test 

You can set one of the predefined tests as default configuration. 

This allows you to set and perform the same type of test when you switch 

on the instrument. 

1 

2 

3 

4 

5 

Opens the TEST MENU screen. 

Opens the TEST MENU: PREDEFINED screen. 

Selects the type of test, i.e. BER. 

To highlights the field Press Enter to: and set the operation 

to be carried out on the file, with "Set as Ф test" 

Selects the test to be carried out as predefined, as you 

switch on the instrument. 



6 

Cancels the current selection. 

4.4. Deleting a predefined test 

To delete a test from the predefined ones: 

1 

2 

3 

4 

5 

Open the TEST MENU screen. 

Open the TEST MENU: PREDEFINED screen. 

Selected test: to select the type of test for the visualisation 

of the predefined configuration list 

Press Enter to: Set the operation to be carried out on the 

file, "Delete" 

Select the predefined test to be deleted 



4.5. Using the Favorites feature 

It is possible to create a list of the most used tests into the predefined 

tests, ‘Favorites’ page. 

To add a predefined test into the Favorite list follow the steps listed below: 

1 

2 

3 

Choose the setup that you want to save 

Open the ‘Save setup as predefined’ screen and name the 

setup 

Confirm and save the test setup. 

Now the setup has been added to the list of the predefined tests. 

4 

5 

Recall the PREDEFINED TESTS setup and select, ‘Press 

ENTER to: ’Add favorites’ 

Select the test to add and press ENTER. 

Now the test’s setup is saved into the Favourites page. 



If you delete a test listed into the Favourites page, you will remove only the link to the test but not the 

test itself. 



5. USING THE INSTRUMENT FOR MONITORING 


This chapter gives detailed information on all parameters used to 

configure the instrument for monitoring the traffic of an ISDN access and 

signalling on a POTS access, according to the device used. Two 

monitoring modes are available: 

► The instrument is capable of monitoring the traffic while 

executing a test. Throughout this manual this mode is referred to 

as “background mode”. 

► The instrument can be set-up in a way that it monitors all traffic 

on the selected interface. Throughout this manual this mode is 

referred to as “ high impedance mode”. 

The parameters that can be set up in both modes are the same: filters and 

control of buffer. In both cases the resulting trace can be stored and 

analyzed on the screen. 

The monitor on POTS does not have the same filters as ISDN. 

Data captured by the device may be stored for further analysis or 

downloaded into a personal computer through the software Aethra ® 

“PC108 for Windows TM ”. 

Monitoring navigation is illustrated in Fig. 5-1. 

CHAPTER 5 - USING THE INSTRUMENT FOR MONITORING 97


5.2. Monitor vs Analyze 

Fig. 5-1 Monitoring Navigation 

It’s important not to confuse the phase of “monitor” with the one of 

“analyze”. In fact the former occurs “live”, with the device capturing all the 

events on the chosen interface, showing them on the display but not 

letting the user to interact (except for the preliminary setup of the monitor). 

The trace is saved and then the pression of the button “Analyze” allows 

the instrument to access such data and to display them. Now the 

interaction between data and user is possible (for further information see 

chapter 8). 

The difference above can be cleared by Fig. 5.2. 

98 CHAPTER 5 - USING THE INSTRUMENT FOR MONITORING


Fig. 5-2 Monitor vs Analyze 

5.3. Background Monitor vs High Impedance Monitor 

The High Impedance Monitor is a hardware, passive monitor, where all 

the traffic on the selected interface is monitored. It produces the display of 

the list of the events on the screen. 

On the contrary, the Background Monitor allows a monitoring during the 

simulation and the execution of a test. 

To better distinguish between the two types of monitor, Fig. 5.3 can be 

useful: 

Fig. 5-3 Background Monitor vs High Impedance Monitor 



5.4. Setting Up for Monitoring 

The following example describes the setup for S/T BUS monitoring in 

high-impedance. Differences to other monitoring modes will be indicated 

throughout the text. 

1 

2 

3 



Select ACT AS: MON-S. 

Note that the next line changes from “MANUAL TESTS” to 

“SETUP & START MONITOR”. 

Select SETUP & START MONITOR and open the SETUP: 

MONITOR screen. 

ISDN POTS 

Use the functions in this screen to remove superfluous messages from the 

monitored traffic. 

These messages will no longer be available during analysis. 

Capture layer: Choose the layer to be captured in the monitor test. 

Capture TEI: Capture specific TEI numbers. You can also use this filter to 

define one single TEI that needs to be monitored. 

Capture SAPI: Capture messages with specific SAPI values. 



Capture Channel: Capture messages on specific channel. Only for 

DASS2 and DPNSS. 

Capture Repeated frames: Captures repeated UINFO frames on DASS2 

and DPNSS protocol due to compelled signalling system. Only for DASS2 

and DPNSS. 

Capture Msg ⇒ TE: Captures specific messages that are sent to the 

terminal. 

Capture Msg ⇒ NT: Captures specific messages that are sent to the 

network. 

Buffer Mode: Choose whether monitoring should stop when the 

memory’s space is full, or older data should be overwritten. 

CRC4: Activate or deactivate the CRC4 procedure. PRI only. 

Protocol: Choose the local singling protocol. 

100 Ω termination: Choose if you want to add a 100Ω termination to the 

S/T socket. This option can be used if the S/T bus is not correctly 

terminated in the connection point of the device. The default value is NO. 

BRI-S only. 

Gain RXA/RXB: It is possible to insert an amplifier for each side of the 

link. Only in Monitor PRI mode. 

Ignore L1 alarms: Timer used to ignore layer 1 alarms that are shorter 

than the inserted value. Only in Monitor PRI mode. 

For the other parameters, refer to paragraph 3.3 COMMON SETUP. 

5.5. BRI-U Monitoring (D2022 Option) 

This accessory is used to monitor signalling over the D-channel between 

the exchange and the user over a Basic access, when monitoring over the 

S/T interface is not possible. 

This is typical of the installation of NT1+ network terminations, in which 

the signalling protocol for analogue interfaces can only be analyzed over 

the U interface. 

The D2022 is placed in series between the two wires of the U interface 

coming from the exchange (LT) and the user network termination (NT). It 

connects to the device by means of the cable supplied, with the 'V.11' and 



'POWER OUT' connectors. The D2022 is powered by the device, which 

can be powered with AC/DC adapter or internal batteries. In the latter 

case, battery operation is reduced consequently. 

The D2022 is available in the U interface version with 2B1Q and 4B3T line 

code. To monitor signalling over the U interface directly, select the 'MON- 

U' mode and carry out the 'MONITOR' test. For information on 

connections see Appendix B. 

First connect the D2022 to the NT termination and then to the LT line. 

5.6. Start Monitoring 

When you have set the filters, you can start the monitoring test. 

1 

2 


Start monitoring. 

Note that the START key changes to STOP. 

If the trace regarding the previous monitor test has not been saved, the device asks for a confirmation 

to start a new capture session overwriting the data previously captured. 

The LED RUN goes on and the test results appear on the screen. For 

information on connections see Appendix B. 

5.6.1. Monitoring the B channel 

To have a more detailed problem’s check on data connection, e.g. PPP/IP 

or FRAME RELAY, the device provides a capturing function of HDLC 

frames over B Channel. 

To activate this function: 

1 

Setup the device in Monitor mode 



2 

3 

4 

Go into the Monitor results page according to the instructions 

reported in the previous chapters 

Select ‘CHAN’ softkey 

Configure the parameters 

B channel capture: Choose the B channel to capture. 

� No, the instrument disables the capture on B channel 

� Bx, the instrument captures the Bx channel selected 

� Automatic, the instrument captures the first B channel activated. As 

soon as the network release the channel, the device stops 

capturing. 

Max length: Inset the maximum number of bytes to save. The smaller is 

the value, the bigger is the quantity of packets that is possible to save into 

the internal memory of the device. To obtain a long trace is suggested to 

use PC108 for Windows or the MultiMediaCard optino MMC2000. 

Other B channel capture: It is possible to enable the capturing of a 

second B channel among the left ones. 

5 

Select “Execute at next start” and press the right arrow 



The device can capture up to two channels simultaneously, choosing among D, D+1B and 2B. 

Selecting the capture 2B, is not possible to memorise packets relative to the D channel. 

In 2B automatic mode, the device starts capturing as soon as the interested channels are activated, 

the capturing remains active until a specific manual command made by the user. 

For a detailed decoding of the captured events on B channel, refers to PC108 for Windows software 

manual. 

5.7. Stop Monitoring 

1 

Stop monitoring. 

5.8. Saving the Trace 

Before saving the trace you need to stop monitoring. 

When you have stopped monitoring you can save the trace as follows: 

1 

2 

3 

Open the SAVE THIS RESULT screen. 

Enter a label for the monitor trace. Use the numeric keypad 

to enter characters and key 1 to enter a space or other ASCII 

characters. 

Confirm and save the monitor trace. 

The stored traces can be used for the following routines at a later date: 

► Printing a hard copy of the trace. See chapter 11. 

► Download traces to a PC. See chapter 11. 

► Analyze traces directly on the screen. See chapter 8. 



6. USING THE MULTIMEDIACARD (MMC2000 OPTION) 

6.1. Introduction 

The MMC2000 option, allows to expand the internal memory of the device 

up to 16MByte by the use of a MULTIMEDIACARD as support, on 

which is possible to store a bigger quantity of data compared to the 

device’s internal buffer. Therefore, in case of long monitoring, won’t be 

necessary leaving a PC linked to the device in order to capture all the 

events of a test. The support (CARD) can be easily found at any computer 

or photo shop. 

6.1.1. Connection 

In order to use the expansion box is needed: 

1 Connect the option to the device AC/DC main adapter, 

POWER IN connector, using the Y cable provided with the 

option. 

Once connected proceed according to your own necessity. 

To store data from the device: 

2 Connect the option to the RS232 serial port of the device 

through the Y cable. 

To download data from the MultiMediaCard to the personal computer: 

2 Connect the option to the RS232 serial port of the personal 

computer. 

The led “ACT” blinks YELLOW when there is data exchange with the device, goes solid YELLOW 

when the device is not detected (in this case check the device configuration or the connections). 

The led “PWR” goes RED in presence of power supply (if the led is off check the main supply). 

6.2. Formatting the MultiMediaCard 

The first operation to do in order to use correctly the MultiMediaCard, is 

formatting the CARD itself, by the use of the software PC108 for 

Windows XP edition, or the software MMCWizard provided with the 

option MMC2000. 

CHAPTER 6 - USING THE MULTIMEDIACARD (MMC2000 OPTION) 105


If this operation is not carried out, the device won’t recognize the MultiMediaCard, making 

impossible its use. 

6.2.1. How to format the MultiMediaCard with MMCWizard 

With MMC2000 option, or by the use PC108 for Window XP edition a 

software called ‘MMCWizard’ is provided, this program serves to: 

► Format the MultiMediaCard 

► Upload data from the Card to the PC 

► Delete the no more used files from the CARD 

In order to format the MultiMediaCard, follow the instructions below: 

1 Connect the option to the PC (through the serial cable 

RS232), connect the device main adapter to the option’s 

POWER IN and insert the MultiMediaCard into the 

appropriate slot (push the MultiMediaCard into the slot 

until you hear a “click”) 

2 Install and open the MMCWizard application program that is 

inside the floppy disk provided with the option or perform the 

operation from PC108 for Window XP edition, (see PC108 

manual). 

Once the program MMCWizard is opened, the icon appears on the Sys 

Tray Bar of your PC (at the bottom of the screen). 

► The icon goes green in normal operative condition 

► The icon goes red if the software detects connection anomalies 

If the icon goes red, in spite of all the connections are correct, click with the right button of the mouse 

on the icon and select “Configure” a window, that shows the device information and configurations will 

appear. In there, it is possible to change the serial speed rate (in order to work correctly, the serial 

speed rate must be set at 115200 bps). 

To run a MultiMediaCard formatting: 

Press the icon FORMAT to format the CARD 

The PC asks for a confirmation to continue the operation. Press ”YES” to 

confirm or “NO” to cancel. 

By formatting the MultiMediaCard, all data contained into the card will be lost. 

Once formatted, the MultiMediaCard is ready to be used. 

106 CHAPTER 6 - USING THE MULTIMEDIACARD (MMC2000 OPTION)


6.3. Setting Up the MultiMediaCard 

In order to setup the MMC2000 option on the device follow the instructions 

below: 

1 

2 

or 

2 

3 

4 

5 

6 

7 

Open the TEST MENU page. 


Select SETUP & START MONITOR. 

Select the MANUAL TESTS menu and select 

BACKGROUND MONITOR test. 

Enter into the Monitor Test SETUP page. 

Select BUFFER MODE: MULTIMEDIACARD. 

Select ‘Use this setup for monitoring’. 

Start the test. 

After the START, the device asks for a file name that will be stored into the MultiMediaCard, this 

operation allows the user to find the stored file into the CARD 

Insert the file name. 



If the MMC2000 option is not connected to the device, the message “MMB not present” will appear 

on the display 

Now the device will store all the test events into the MultiMediaCard 

internal buffer. 

Once the test is finished, it is possible to disconnect the box from the 

device and connect it to a personal in order to download the stored data. 

The MultiMediaCard can be used only with the device in MONITOR mode. 

6.4. Uploading the file into the PC 

In order to upload the stored data from the MultiMediaCard to the PC, 

follow the instructions below: 

UPLOADING ELAPSED TIME NUMBER OF UPLOADED EVENTS 

1 Open the Memory Box management program. Once 

connected with the MMC2000 adapter, the software will 

display all the stored file into the CARD. 

2 Select the file that you want to upload. 

3 

Press the icon “DOWNLOAD” to download data to the PC, or 

double click on the file name displayed on the screen. 

The program asks to rename the selected file, creating a file “.aps” which 

it is possible to open with PC108 for Windows software 

108 CHAPTER 6 - USING THE MULTIMEDIACARD (MMC2000 OPTION)


It’s also possible to make a multiple DOWNLOAD selecting two or more files simultaneously. In this 

case the program won’t ask to rename the files, downloading them into the folder, with the original 

name 

For further information about how to use the PC108 for Windows 

software, see the PC108 for Windows User’s Manual. 

When a DOWNLOAD is running, only the key STOP is active and it is possible to interrupt the 

operation in every moment 

Other function keys: 

Interrupt a DOWNLOAD in progress. 

Delete a file from the MultiMediaCard internal buffer. 

Update the files into the MultiMediaCard. 



7. SMART STATUS 

7.1. About this chapter 

The Smart Status function allows you to view the configuration and the 

current state of both instrument and tested interface. Interaction with the B 

channel status is also possible. 

7.2. Primary Access status 

The first page shows the layer 1 status, with information about 

synchronization, alarms and errors for each direction. 

1 

About synchronization: 

Displays page 1 of the available information. 

► FRAME, indicates that the frame synchronization has been 

reached. 

► CRC, (Cyclic Redundancy Code) indicates that the CRC 

synchronization has been reached. Only PRI with CRC4. 

About the presence of alarm conditions: 

► LOS, (Loss Of Signal) indicates the absence of received 

impulses due to interruption, short circuit, etc. 

► LFA, (Lost Frame Alignment) indicates that the device has lost 

the frame synchronization because of an excessive noise over 

the line, signal/noise ratio too low or high CRC errors. 

► AIS, (Alarm Indicator Signal) indicates that the network has sent 

an alarm signal due to various types of errors detected at the 

local exchange. 

► RAI, (Remote Alarm Indicator) indicates that the remote or local 

terminal is in alarm condition. 

About the presence of error conditions: 

► CODE, indicates error in the transmission code HDB3. 

CHAPTER 7 - SMART STATUS 111


► LOCAL CRC, indicates that the device has receiver a faulty 

data verification code from the local terminal. 

► REMOTE CRC, indicates that the device has receiver a faulty 

data verification code from the remote terminal. 

About the signalling activity: 

► D CHANNEL, indicates activity over D channel. 

About alignment word: 

2 

► FAS, synchronism word present into the even frames of E1flow. 

Are displayed all the eight bits of the timeslot 0. 

► NFAS, synchronism word present into the uneven frames of 

E1flow. Are displayed all the eight bits of the timeslot 0. 

Go to pages 2 and 3. 

Page 2 displays the B channel activity (see § 7.4) while page 3 shows 

errors and alarm counters. A counters reset function is available by 

pressing the key. 

7.2.1. G.703 access 

If an Unframed G.703 at 2Mb test is performed, the timeslot zero (0) of the 

frame E1 is no more used to synchronize the frame. The tests use all 

timeslots (32) in order to receive and transmit the PRBS sequence. 

Moreover, it is not available the CRC4 control and the other overhead bits. 

The Status page displays: 

112 CHAPTER 7 - SMART STATUS


Page 2 displays the B channel activity while page 3 shows errors and 

alarm counters. A counters reset function is available by pressing the 

key. 

In this configuration, information such as FRAME and CRC SYNC, LFA 

alarms, AIS and RAI, LOCAL CRC and REMOTE CRC errors is not 

available over the frame. 

7.2.2. G.826 

Page 4 shows the values detected according to G.826 to monitor the inservice 

line quality parameters. 

3 

Goes to page 4. 

This measure is disabled if an Unframed G.703 at 2Mbit test is carried out. 

This standard, valid for 2Mb connections or higher, allows to check the 

access quality without performing specific off-service tests, such as BERT 

G.821. See § 3.5. 

G.826 measures errors and alarms in the flow through the analysis of the 

synchronism blocks (LFA, CRC4) intrinsically contained in the frame. 

The results allow to measure the unavailability flow time (UAS), number of 

errored seconds (ES), number of severely errored seconds (SES) and 

errored blocks (BBER) both in uni-directional mode for each direction 

(Downstream, Upstream) and in bi-directional mode, by considering the 

flow as a single communication channel. 

Values are shown both in absolute (ABS) and ration (RATIO) format. The 

PASS/FAIL test refers to the quality objectives set in G.826. 

4 

Resets counters. 



7.3. Basic Access status 

In case of Basic access, the third page shows the activation state of the 

physical layer (INFO 1, 2, 3 and 4), the presence of data switching over D 

channel (D channel packet). 

1 

Displays page 1 of the available information 

In case of BRI-U - 2B1Q mode, the page shows FEBE and NEBE 

counters as well as activation and deactivation times of the physical layer. 

7.4. B channels status 

2 


This page displays all B channels with state according to the icons below: 

 

Channel not used. 

Activity (in monitor mode) or test in progress (in simulation 

mode). 

B channel data connected to the internal audio circuit. 

B channel data connected to the external HANDSET plug. 

Presence of incoming call, only if the answer has been set in 

manual mode (default). See § 3.9.2. 

B channel data are connected to V.11 connector. 

Active loop. 

Channel is connected in cross-loop with the channel . 

BER test in progress. 

When the controlling protocol LMI is active. In case of Frame 

Relay. 

IP test in progress. 



X.25 test in progress. 

In Simulation mode you can select the looped or cross-looped B channels 

and display the connected remote number in the last line of the screen of 

page 2, if available. If the delay is available for the selected channel, § 

3.15.3, the instrument displays it in alternation with the connected number. 

Press ENTER on the selected channel to disconnect the associated call. 

In Monitor mode you can select the B channels with activity and display 

the connected remote number in the last line of the display, if available. 

Press ENTER on the selected channel to listen to the audio of the 

associated call. 

In Monitor mode information on the B channel is only given with the 'MONITOR' test in progress and 

only refers to the connections established after the START. 

Depending on the device owned, you will have the following displays: 

3 

4 

Selects a B channel and displays the remote number 

connected. 

Monitor 

PRI simulation 

BRI simulation 

Disconnects the call associated to the B channel. Simulation 

mode only. 



4 

Listens to the audio of the associated call. Monitor mode 

only. 

If there is an active loop, it’s not possible to change the signalling protocol set, in order to avoid B 

channel lock problems. 

7.4.1. Restarting B channels 

In simulation mode with Point-to-Point configuration, see § 3.3, you can 

send the RESTART message over a specific B channel chosen, after 

selecting RESTART B CHANNEL on the first line and then selecting the B 

channel. Only in simulation. 

4 

5 

Selects RESTART B-CHANNEL. Simulation mode only. 

PRI BRI 

Selects the B channel and sends the RESTART message. 

7.4.2. B channels connection 

In simulation, if the answering mode loopbox is set as Manual, see § 3.9, 

the device shows the icon “bell” at every incoming call compatible with the 

profile set, see § 3.3, and the can answer or disconnect the call manually. 

After connection the call, the user can decide to perform a loop over the 

corresponding B channel, or to connect the audio. 

In case of 'LEASED LINE', you can manually make a loop or connect the 

audio on a specific channel as soon as the physical layer is active. 

The device has only one audio circuit therefore, if the channel is 

connected in audio mode, the channel which was previously connected 

goes automatically in loop. 



4 

5 

With LOOP is meant that the data received by the device over a specific channel is re-transmitted 

without modifications over the same channel. 

To select CONNECT AUDIO / LOOP. Only in simulation 

mode. 

PRI BRI 

PRI BRI 

To select the B channel to be connected in loop or audio. 

In Simulation mode the instrument displays additional information on the 

channel if the call-back or call forwarding function is active. See § 3.9.1. 

If present, the remote number is shown in the "{[CD]�, [CB] �} [+,++] N" 

format: 

N Remote number compared to the instrument. 

+/++ Type of number: unknown/national+/international++. 

� N B channel associated to a call from N. 

� N B channel associated to a call to N. 

CD Indicates a call followed by a call-back upon disconnection 

(call-back delayed). Simulation mode only. See § 3.9.2. 

CB Indicates a call made as call-back. Simulation mode only. 

See § 3.9.2. 



CF Indicates a call made as cross-loop (call forwarding). 

Simulation mode only. See § 3.9.2. 

In Basic access, page 2 also displays voltage power level of the phantom 

power with related power mode. 

7.5. Device information 

Displays page with the available information. 

PRI/BRI 

This page shows: 

► Instrument configuration 

► Type of test in progress 

► Current test state 

► Filling percentage of the internal buffer for storing monitor 

events 

► Current date and time 

► State of the single layers referred to the OSI model when 

significant 

The current layers status it is also displayed through three LEDs placed 

on the screen’s protection lens, according to the following table: 

LED off � Level not active. 

Green 

LED 

Yellow 

LED 

Red 

LED 

� Level active. 

� Level in an intermediate state. 

� Level in presence of anomalies. 



In case of DASS2/DPNSS protocols, the layer 2 LED turns green only if all the links are active (30 for 

PRI or 2 for BRI). Otherwise, if one link at least is active, the LED turns yellow. 

In case of tests over G.703, G.704 or V/X interfaces, the layer 1 LED turns green when the physical 

layers (frame, clock, criteria) is ready. The layer 2 LED is always off and the layer 3 LED will turn 

green when the test will be active. 

7.6. V/X interface access status (VX2000 option) 

The first page shows criteria status, toward DCE and toward DTE. 

1 


Criteria displayed are: 

► C103, data transmitted from DTE 

► C104, data transmitted from DCE 

► C113, clock transmitted from DTE 

► C114/C115, clock transmitted from DCE 

► C105 (RTS), C106 (CTS), C107 (DSR), C108 (DTR), C109 

(DCD) 

► C141, loop request from DTE to DCE 

The second page regarding V/X interface access, displays the type of 

activity of the interface used. 

1 

Goes to 2nd page. 

The device integrates a frequency measurer, with resolution +/- 1Hz, for 

measuring the reception clock. The measurer is able to calculate the 

incoming clock frequency and the correct phasing compared to data. 



A possible error, for example due to the inversion of the clock itself, is 

highlighted on the screen as well as the clock absence. 

Clock Rx value, is displayed into the Status pages only if the clock source has been set as ‘External’, 

in the common setup. 

By selecting the field relative to the activity of the interface and by 

pressing the key ENTER, the user can insert a loop on data, the device, in 

transmission, will send the data received from remote. Perform the same 

operation in order to remove the loop. 

7.7. V.11 (X.21) Access status 

The first page shows criteria status, toward DCE and toward DTE. 

1 


Criteria displayed are: 

► C103, data transmitted from DTE 

► C104, data transmitted from DCE 

The second page regarding V/X interface access, displays the type of 

activity of the interface used. 

1 

Goes to 2nd page. 

The device integrates a frequency measurer, with resolution +/- 1Hz, for 

measuring the reception clock. The measurer is able to calculate the 

incoming clock frequency and the correct phasing compared to data. 

A possible error, for example due to the inversion of the clock itself, is 

highlighted on the screen as well as the clock absence. 



Clock Rx value, is displayed into the Status pages only if the clock source has been set as ‘External’, 

in the common setup. 

By selecting the field relative to the activity of the interface and by 

pressing the key ENTER, the user can insert a loop on data, the device, in 

transmission, will send the data received from remote. Perform the same 

operation in order to remove the loop. 

7.8. Frame Relay protocol status (FR2K option) 

If FR2K option is installed, it will be possible carrying tests in order to 

install and check Frame Relay services over WAN (Wide Area Network) 

links. The device is able to emulate a CPE (Customer Premise 

Equipment) device, in order to determinate the availability of Frame Relay 

service before installing the end user terminal (e.g. a router). 

The protocol is available over G.703, G.704, V.11-X.21, V.35 and V.36 

interfaces. 

The test equipment shows in the Smart Status page regarding Frame 

Relay, all the information about traffic, quality of the service (QoS), 

controlling protocol LMI. 

In the first screen page the device displays: 

► Number of transmitted and received frames 

► Counters of frames with FECN (Forward Explicit Congestion 

Notification) bit 

► Counters of frames with BECN (Backward Explicit Congestion 

Notification) bit 

► Counters of frames with DE (Discard Eligibility) bit 

► Number of frames rejected because of errors over DLCI, 

heading or packet’s fragmentation 

► Number of frames with unexpected DLCI and unexpected DLCI 

values 

If LMI protocol has been activated, a second status page will be available 

with statistical information about DLCI. The following data is displayed: 

► Number of transmitted and received LMI frames 

► Number of wrong LMI frames 

► Status of DLCI selected 



► List of all PVCs configured over the link (DLCI and relative 

status) 

In presence of LMI activity, that is the network answers to the queries, the 

device displays a specific icon on the top of the screen. 

1 

Goes to page 4 and 5. 

7.9. Reading the POTS line status 

If the AB2000N option is present and the instrument is configured to 

operate over a normal POTS analog line, you can display the status of 

some POTS line parameters. 

1 

Display page 1 of the available status information. 

7.10. Reading the battery status 

You can view the status of internal batteries or battery recharge at any 

time. 

1 

2 

Display page 1 with status information. 

Select the page regarding the battery status. 

If powered with batteries, the instrument displays the battery 

voltage. 

If the AC/DC external adapter is connected, it is displayed 

also the internal battery recharging status. 



3 

Goes to the page with the information about external 

accessories 

temperature. 

connected and the device’s internal 



8. ANALYZING A MONITOR TRACE 


This chapter describes the signalling protocol analysis function of the 

instrument. You can analyze saved or real time monitor traces directly on 

the instrument’s screen. 

Various display modes are available to make data analysis easier. It is 

possible to filter out data so that only the important messages are visible 

on the screen. Every message is labelled with a date, time, and direction 

of the message (�TE or � NT). The displayed data can be downloaded 

to a printer or a computer. You are also able to save this filtered data, 

provided that enough memory is available. 

You can display a trace in four modes: 

► Overview mode 

► Hexadecimal decoding mode 

► Mix decoding mode 

► Full decoding mode. 

For the analysis of a POTS access, filters and displaying modes are not the same as ISDN. 

8.2. Analyzing a Trace 

To analyze a trace: 

1 

2 

3 

Open the HISTORY menu. 

Select the list of saved MONITOR tests. 

Select the trace to be analyzed, i.e. “Aethra Srl” 

CHAPTER 8 - ANALYZING A MONITOR TRACE 125


or 

3 

Open the last saved TRACE directly. 

Use this menu to set up the filters that remove some of the messages in 

the trace. 

The following filters are available for the ISDN access: 

► Show layer: Display all layer 3, 2 and/or 1 messages. 

► Show TEI: Display messages with specific TEI numbers only. 

► Show SAPI: Display messages with specific SAPI numbers only. 

► Show Channel: Display messages on specific channel. Only for 


► Show Repeated frames: Display repeated UINFO frames on DASS2 

and DPNSS protocol due to compelled signaling system. Only for 


► Show Msg ⇒ TE: Display specific messages sent to the terminal. 

► Show Msg ⇒ NT: Display specific messages sent to the network. 

► Show number: Display only the messages with the entered number 

(CLI, COLD). 

► Direction: Allows to modify the events’ decoding, according to the 

chosen direction. It’s used especially for the decoding of some 

protocols which relates the messages’ meaning with the message 

direction. 

You can capture the HDLC protocols that are not directly supported by the instrument by selecting 

the “OTHER” option in the Protocol field. For a detailed analysis, use the PC software. See § 3.3.1. 

126 CHAPTER 8 - ANALYZING A MONITOR TRACE


8.3. Analyzing a Trace in Overview Mode 

4 

The screen shows the trace data in overview mode. 

The page shows information on messages. Information includes message 

direction, SAPI, TEI, Call Reference and layer 3 and/or layer 2 and/or 

layer 1 messages, C/R and P/F bits as well as Nr and Ns counters. 

5 

In DASS2/ DPNSS protocols, an ‘r’ is inserted close to each repeated UINFO frame. 

All physical level events and FSK messages are displayed for 

the POTS access. 

Scroll through the messages. The � cursor moves according 

to the key used. When at the top or bottom of the screen, the 

highlight area remains still and the message list starts 

scrolling. 

8.4. Analyzing a Trace in Full Decoding Mode 

To display a message in detail, continue from step 6 as follows: 

This screen gives more detailed information on the selected message, 

including direction, contents and absolute time. 



6 

7 

8 

ISDN POTS 

Scroll the message contents. 

ISDN 

POTS 

Select another message. 

To return to overview mode: 

9 

Return to overview mode. 

To go to mix decoding mode: 

9 

Change decoding mode. 

The duration of each call can be determined with the time values shown: in ISDN use the time values 

between SETUP and DISCONNECT, in POTS between OFF HOOK and ON HOOK events. 

8.5. Analyzing a Trace in Mix Decoding Mode 

From the full decoding mode you can display the trace in mix decoding 

mode as follows: 



1 

Select an event. The screen changes to the mix decoding 


The screen displays all information on the selected message, indicating 

the octet value and the length of each single message. 

2 

3 

Scroll through the pages with information on the selected 

message. 


To return to the overview mode: 

4 

Return to the overview mode. 

To go to the hexadecimal decoding mode: 

5 


8.6. Analyzing a Trace in Hexadecimal Decoding Mode 

From the mix decoding mode you can display the trace in hex decoding 

mode as follows: 

1 

Select an event. The screen changes to the hex decoding 


The screen displays all information on the selected message, with the 

message contents in hexadecimal format. 

2 

Scroll through the pages with information on the selected 

message. 



3 


To return to the overview mode: 

4 

Return to the overview mode. 

To go to the full decoding mode: 

4 


8.7. Inserting a call filter 

You can insert a filter to display the events related to a specific call in the 

path. To insert the display filter: 

1 Select a level 3 event related to the call to be displayed. For 

easier search, use the “Show number” filter. 

2 

Insert the filter. 

When you have inserted the call filter and you have removed the number 

filter, only the related events will be displayed. 



9. STATISTICS 

Statistical data about monitor’s stored traffic is available in various pages 

for the Euro-DSS1 protocol. Statistics are divided into layer 2, layer 3 and 

advanced statistics. 

1 

2 

3 

4 

Statistics are updated in real time for immediate data analysis during the test. 

Open the last TRACE stored in the memory. 

Access the statistics pages. 

Access Layer 2 statistics. 

Access to another page showing the frames according to the 

SAPI value (0, 1, 16 and 63). 

All types of layer 2 frames are indicated for layer 2 together with wrong 

messages, if any. Results are shown both in percentage and absolute 

value. 

Fig. 9-1 

Additional checks can be performed by analyzing statistics on the TEI 

management. 

CHAPTER 9 - STATISTICS 131


Fig. 9-2 

Data allow for evaluating the average use of the tested access (normal 

calls, X.25 or layer 2 management). 

5 

Access Layer 3 statistics on messages. 

As regards layer 3 (fig. 9-3), the total number of message is given for each 

type. 

Fig. 9-3 

Advanced statistics are available in the traffic summary, divided by call 

and disconnection cause. 

6 

Display statistics on calls. 

The column of Fig. 9.4 shows the total number of current outgoing and 

incoming calls. The “OK” column shows to the total number of successful 

calls (from SETUP to DISC). The “KO” column shows the total number of 

failed calls. 

Fig. 9-4 

The “Reached �NT destinations” field shows the total number of calls 

with successful dialing, in the column “NUM”, with minimum, average and 

132 CHAPTER 9 - STATISTICS


maximum duration time in the T.Min, T.Med and T.Max columns. The ‘(not 

reached)’ field, shows the number of calls which have not reach the 

destinations. 

Finally, the minimum, mean and maximum duration of outgoing and 

incoming calls is given. 

7 

8 

9 

Display information on the use of each B channel. 

Display statistics on disconnection causes, indicating the 

total number of calls from and to the terminal according to 

the disconnection cause 

Display the LOCATION of disconnected calls. 

CHAPTER 9 - STATISTICS 133


10. CONFIGURING THE INSTRUMENT 


This chapter describes the general configuration of the instrument. You 

can change default settings or prepare the instrument for specific use. 

10.2. Opening the Configuration Menu 

1 

2 

Open the Config. menu. 

Highlight and select the CONFIG field 

Only when the “Act as” field is filled in with MONITOR (i.e. MON-S, with BRI ISDN), the pression of 

leads directly to step 2 (General Setup). 

From this menu you can select an item to open a submenu, or use the 

arrow keys to configure. 

2 

To scroll through the pages select CHANGE PAGE. 

10.3. Using the phonebook 

You can define up to 20 numbers in a phone book. 

To add a name to the phonebook: 

1 

Select the PHONEBOOK submenu. 

CHAPTER 10 - CONFIGURING THE INSTRUMENT 135


2 

3 

4 

5 

5 

6 

7 

Enter a new name. 

Use the numeric keypad to enter Name, Main (phone) 

number, and other data. 

Select “Save this entry” to add the new name and number to 

the phonebook. 

To modify an existing entry. 

To delete a name from the phonebook. 

To scroll the name according to the list. 

To display the details of the names in the list. 

136 CHAPTER 10 - CONFIGURING THE INSTRUMENT


10.4. Adjusting the volume 

1 Select the Volume Levels submenu. 

2 

3 

4 

5 

Audio: use the arrow keys to adjust the speaker volume. 

Keypad Beep: to adjust the keypad beep volume. The 

instrument beeps according to the selected volume each 

time you change the value. 

Ringer: to adjust the ringer volume for phone test. 

Warning: to activate the warning acoustic signal, e.g. BER. 

10.5. Changing the audio connection 

1 Select the AUDIO submenu. For audio connection you can 

use the instrument’s internal microphone and speaker. Use 

the arrow keys to select. 

10.6. Changing the Information Language 

1 Select the LANGUAGE submenu. Use the arrow keys to 

choose a language. 

10.7. Setting the Date and Time 

The instrument has a date and time clock. 

To change date and time: 

1 

2 

3 

DATE FORMAT: Set the date format to DDMMYY (i.e. 19 

Apr 2003), or MMDDAA (i.e. Apr 19 2003). 

Select the DATE or TIME fields. 

Use the numeric keypad to type the new date or time. Use 

the arrow keys to backspace to previous digits. Note that the 

separator characters - and : are automatically inserted. 

10.8. Changing the Baud Rate 

1 Select the RS232 BAUDRATE submenu. 



10.9. Self Diagnostics 

You can choose the baud rate for serial communication with 

a computer or a printer. Use the arrow keys to change the 

baud rate. 

You can perform several self diagnostics to check the functionality of the 

instrument. To perform a self diagnostic: 

1 

2 

Select the DIAGNOSTIC submenu. 

Perform the selected test. 

The screen displays the results of the diagnostics test. 

3 Perform a General RESET of the instrument. 

4 

4 

It is recommended to perform a General RESET after updating the internal firmware of the 

instrument. 

Confirm Reset. 

Cancel Reset. 



10.10. Information and options 

1 Select the INFORMATION AND OPTIONS submenu to ask 

for the model identity (release number and options) at any 

time. To display the identity: 

2 

Select the INFORMATION AND OPTIONS submenu. 

The first screen shows the software version numbers and 

the instrument serial number (identification). 

The second screen shows a list of the software options 

available for the instrument (enabled and not enabled) 

10.11. Battery Management 

The instrument is provided with an automatic battery recharge circuit. To 

start the recharge cycle, you only need to connect the external mains 

adapter. Recharge time is approx. 3 hours with the instrument off, and 

approx. 6 hours with the instrument on. 

10.12. Changing the Contrast 

You can set the contrast of the screen to your preference. Use the arrow 

keys to change and relate to the pattern on bottom of the screen. 

10.13. Screen Saver Management 

1 

Select the SCREEN SAVER MANAGEMENT submenu. The 

instrument allows you to activate the screen saver function 

when left in the same page for a long time to avoid screen 

degradation. You can also set a password to return to 

normal operation. 



10.14. Test Programming 

1 

Select the PROGRAMMED TESTS submenu. 

The instrument allows you to automatically activate a test at a set date 

and time. Once you have selected the test to be performed, the instrument 

goes in stand-by state, displaying the current time and the automatic 

START time, if any. In simulation mode, you can set the automatic start 

(Auto Monitor) of the MONITOR IN BACKGROUND function. 

2 

3 

4 

Set the start date and time 

Select, if you wish, the AutoMonitor function (automatic start 

of the BACKGROUND MONITOR function). 

Starts the selected test 



5 

Cancels the function 

10.14.1. Automatic Background Monitor 

It is possible to act in such a way that the feature BACKGROUND 

MONITOR activates itself automatically when the test starts, without 

setting it from time to time. In order to enable this feature, the following 

conditions must be true: 

► The device must be configured in simulation mode (TE, NT, 

etc.) 

► Only for tests where Background Monitor is expected 

1 Select “Automatic” in “Start Monitor” field 

The BACKGROUND MONITOR is automatically activated at every test starting and stops itself a few 

seconds before the end of the test. 

The setup took into consideration by this test is the last entered in background monitor’s setup page. 

See § 5.4. 

10.14.2. Self switching off 

The instrument can be configured for automatic switching off at the end of 

the test. 

The user has one-minute time from the end of the test to cancel the self 

switching off function by pressing any button. 



11. USING MEMORY, PRINTER AND PC 


This chapter describes the use of the instrument’s memory, and how to 

communicate with a printer or PC. 

You find information on the following topics: 

► Saving and viewing of test results or monitored traces 

► Printing test results or monitored traces 

► Communicating with a PC using the AETHRA “PC108 for 

Windows TM ” software. 

11.2. Saving Test Results 

You can save results to memory from any RESULT screen. In addition to 

the result, also the test setup is saved. This enables you to view, analyze, 

and print the test result at a later date. The following examples illustrate 

how to save the results of a BER test: 

The internal memory of the device can store up to 10 different results for each kind of test. 

1 Open a RESULT screen. 

2 

Open the SAVE THIS RESULT screen. 

You can enter a label for the test result. Use the numeric keypad to enter 

characters. Numeric key 1 is used for entering a space or other 

characters. 

CHAPTER 11 - USING MEMORY, PRINTER AND PC 143


3 

Confirm and save the test results. 

The results of the last test you have performed are automatically saved. 

11.3. Viewing Test Results 

You can save the test results captured in the field. This is useful to view 

and analyze the test results on a later date, i.e. in your office. 

To view the test results: 

1 

2 

3 

Open the HISTORY menu. 

Selected test: Choose the type of test whose result list you 

want to view. 

Press ENTER to: set the operation to be performed on the 

selected file, “Select” or “Delete”. 

4 Select and open the test results from the list. 

The test results appear on the screen. 

You can recall the results of the last test by selecting the 

“Last test” option in the “Selected test” field. 

The test settings shall be automatically restored when recalling a result from the memory. 

144 CHAPTER 11 - USING MEMORY, PRINTER AND PC


11.4. Printing Test Results or Monitored Traces 

To print test results or monitored traces, you need to connect the 

instrument to a serial printer. Use RS 232 cross cable to connect a printer 

to the RS 232 port of the instrument. See Fig. 11-1. 

Fig. 11-1 Connecting a Printer 

You can print test results from any RESULT screen. The following 

example illustrates how to print the results of a BER test: 

1 Open the RESULT screen. 

2 

Start printing. 

A message that indicates that the instrument is printing appears at the 

bottom of the screen. All screens are presented as a single result when 

printing. 

11.5. Using “PC108 for Windows TM ” software 

To use the Aethra “PC108” software you need to connect the instrument 

to a computer. Use the RS 232 cable to connect a computer to the RS 

232 port of the instrument. See Fig. 11-2. 

CHAPTER 11 - USING MEMORY, PRINTER AND PC 145


Fig. 11-2 Connecting a PC 

For all information on the software installation and use, see the software 

User’s Manual. 

146 CHAPTER 11 - USING MEMORY, PRINTER AND PC


12. MAINTAINING THE INSTRUMENT 


This chapter covers basic maintenance procedures that can be performed 

by the user. 

12.2. Cleaning and Storage 

12.2.1. Cleaning the Instrument 

Clean the instrument with a damp cloth and a mild soap. Do not use 

abrasives, solvents or alcohol, since they may damage the instrument. 

12.2.2. Storing the Instrument 

When storing the instrument, even for extended periods of time, it is not 

necessary to remove the battery pack. However, the batteries will 

gradually discharge. To keep the batteries in optimal conditions, perform 

periodically a complete charge/discharge cycle at least once a month. 

12.3. Batteries 

12.3.1. Charging the Batteries 

At delivery, the NiMH (Nickel-Metal Hydride) batteries must be charged. 

When fully charged, the batteries typically provide three hours at 25°C 

with backlight off. 

When the instrument is powered by the battery, the battery icon at the top 

of the screen informs you about the condition of the battery. The battery 

symbols are: . The symbol appears when there is less than 

five minutes of operating time left. 

Use the setup shown in Fig. 12-1 to charge the batteries and power the 

instrument. To charge the batteries more quickly, turn off the instrument. 

CHAPTER 12 - MAINTAINING THE INSTRUMENT 147


Fig. 12-1 Charging the Batteries 

No damage will occur to the instrument if you leave it charging for long periods, i.e. during the 

weekend. 

12.3.2. Extending Battery Operating Time 

Charging the batteries when they are not completely empty, reduces the 

battery operating time. To keep the batteries in optimal condition, observe 

the following guidelines: 

► Operate the instrument on batteries until the symbol appears 

at the top of the screen. This indicates that the batteries are very 

low and that they need to be recharged. 

► Operating time will be reduced if the instrument is used or 

handled at temperatures that differ from the recommended 

values. 

12.3.3. Dimming the Backlight 

At power-up the screen has a high bright display. 

To save battery power, the screen has an economic brightness when 

operated on the battery pack (no power adapter connected). When you 

connect the power adapter, the screen automatically changes to 

maximum brightness. 

If you have not pressed a key for at least five minutes, the backlight goes 

down to low level. 

12.3.4. Replacing the NiMH Battery Pack 

It should not usually be necessary to replace the battery pack. If you do 

want to replace the battery pack, refer to Figure 12-2 and follow the 

instructions below. 

148 CHAPTER 12 - MAINTAINING THE INSTRUMENT


Warning 

To avoid electrical shock, remove any cable before opening the battery 

access cover. 

NOTE 

This instrument contains Nickel-Metal Hydride batteries. Do not dispose of this battery pack with 

other solid waste. Used batteries should be disposed of by a qualified recycler or hazardous materials 

handler. 

Fig. 12-2 Replacing the Battery Pack 

1 Disconnect any cable both at the source and at the 

instrument. 

2 Locate the battery access cover on the bottom rear. Loosen 

the two screws with a screwdriver. 

3 Remove the battery cover. 

4 Take the battery pack out of the compartment. 

5 Disconnect the two battery plugs from the connectors. 

6 Install a new battery pack. 

Ensure that the batteries are placed in the battery compartment as shown in Fig. 11-2. Use only the 

Aethra battery pack. 

7 Reinstall the battery cover and secure the two screws with a 

screw driver. 

12.4. Display 

12.4.1. Protective label 

The test equipment is sent from the factory with a protective transparent 

plastic label on the display screen for dust and scratches protection during 

the transport. 

CHAPTER 12 - MAINTAINING THE INSTRUMENT 149


This label may reduce the brightness and the contrast of the screen, 

please remove the label stick in order to have the better display of the 

screen. 

12.5. Troubleshooting 

12.5.1. The Instrument Does Not Start Up 

► The batteries may be dead. Charge the batteries first: power the 

instrument with the power adapter without turning it on. After 

about 15 minutes, try turning on the instrument again. 

12.5.2. The Screen Remains Black 

► Make sure that the instrument is turned on. 

► There might be a problem with the contrast. Make sure you 

have set the contrast properly. See § 10.12: “Changing the 

Contrast”. 

12.5.3. Batteries Operate Less Than Three Hours 

► The battery may be in poor condition. Try refreshing the battery 

as described in this chapter “Extending Battery Operation Time”. 

12.5.4. The Software Does Not Recognize the Instrument 

► Make sure that the instrument is turned on. 

► Make sure that the interface cable is properly connected 

between the instrument and the PC. 

► Make sure that the COM port and the rate selected in ISDN 

software are correct. If necessary, change the COM port setting 

or connect the interface cable to another COM port. 

12.5.5. The Printer Does Not Print 

► Make sure that the interface cable is properly connected 

between the instrument and the printer. 

► Make sure that you are using a crossed cable. 

► Make sure that the baud rate you have selected, matches with 

the baud rate of the printer. If not, select another baud rate. See 

chapter 10.8: “Changing the Baud Rate”. 

150 CHAPTER 12 - MAINTAINING THE INSTRUMENT


13. SPECIFICATIONS 

13.1. Introduction 

13.1.1. Safety Characteristics 

This instrument has been designed and tested in accordance with the 

following standards: CEI EN 61010-1 (CEI IEC 1010-1), CEI EN41003 

and CEI EN 60950. 

This manual contains information and warnings that must be followed by 

the user to ensure safe operation and to keep the instrument in a safe 

condition. Use of this equipment in a manner not specified by the 

manufacturer may impair protection provided by the equipment. 

13.1.2. Performance Characteristics 

Aethra ® guarantees the properties expressed in numerical values with the 

stated tolerance. Specified non-tolerance numerical values indicate those 

that could be nominally expected from the mean of a range of identical 

instruments. 

13.1.3. Environmental Data 

The environmental data mentioned in this manual are based on the results 

of the manufacturer’s verification procedures. 

13.2. Compliance 

ISDN Standards 

CTR3 BRI, layer 1, 2 and 3 

CTR4 PRI, layer 1, 2 and 3 

CTR33 X.25 BRI 

13.3. Basic Rate 

Layer 1, S/T Interface 

PHYSICAL 

INTERFACE 

CHANNEL 2B + D 

4- wire line bus 

CHAPTER 13 - SPECIFICATIONS 151


STRUCTURE 

LINE CODE Modified AMI 

COMPLIANCE ITU-T (CCITT) Rec. I.430, ETS 300 012 

TOTAL BIT RATE 192 Kb/s 

NET BIT RATE 144 Kb/s 

CONNECTOR RJ 45 (ISO 8877), pin 3, 6, 4, 5 

IMPEDANCE menu-selectable, high impedance or 100Ω 

Layer 1, U Interface 

PHYSICAL 

INTERFACE 

TRANSMISSION 

METHOD 

CHANNEL 

STRUCTURE 

2-wire line bus 

transmission with echo cancellation 

2B + D 

2B1Q LINE CODE complies with ETR 080 (TS 101 080 V.1.3.1) 

and ANSI TI.601 (1988) 

4B3T LINE CODE complies with ETR 080 (TS 101 080 V.1.3.1) 

NET DATA RATE 144 Kb/s 

CONNECTOR one RJ45 (ISO 8877) connector for both 

interfaces, pin 4 and 5 

13.4. Primary Rate 

Primary Rate Interface 

PHYSICAL 

INTERFACE 

LINE CODE HDB3 

CHANNEL 

STRUCTURE 

4-wire line bus 

G.703, PCM30, PCM30CRC, PCM31, 

PCM31CRC 

152 CHAPTER 13 - SPECIFICATIONS


COMPLIANCE CCITT G.703, G.704, Rec. I.431, ETS 300 011 

BIT RATE 2.048 Mb/s 

CONNECTOR RJ45 (ISO 8877), pin 1, 2, 4 and 5 

CLOCK SOURCE Internal, regenerated by RX 

IMPEDANCE menu-selectable: high impedance or 120Ω. 

13.5. V.11 (X.21) Access 

Serial interface 

V.11, X.21 

Compliance 

Line code 

Line code, with kit 

SPK-2K 

External adapter for coaxial cable 75 Ω 

CCITT (ITU-T) Rec. V.11 

NRZ 

NRZ, NRZI 

13.6. V/X Access (VX2000 option) 

Serial interface 

V.35 

V.36 

Compliance 

Compliance 

TRANSMISSION BIT 

RATE 

Max bit rate 

Max bit rate, with kit 

SPK-2K 



1.024Mb/s 

2.048Mb/s 



13.7. POTS Access (AB2000N option) 

Layer 1 

PHYSICAL 

INTERFACE 

2-wire line 

IMPEDANCE Menu-selectable, 600Ω, CTR21, complex 

Belgium, Germany & Spain 

MAKING CURRENT 50 mA, 100 mA 

SUPPORTED CLASS 

SERVICES 

V23 CLI / Call Waiting, Called party number, 

CIDCW, CID 

FLASH TIME Programmable 40-1000 msec 

DIALLING DTMF, Pulse 40/60-33/66 

CONNECTOR RJ 11 , pin 2,3 

13.8. Protocols 

Euro-ISDN (ETSI EDSS-1) 

LAYER 2 

Protocol 

Compliance 

TEI Management 

LAYER 3 

Protocol 

Compliance 

Based on CCITT (ITU-T) Rec. Q.921 

ETS 300 125 

P-MP, P-P with value definable by the user (0- 

63) 

Based on CCITT (ITU-T) Rec. Q.931 

ETS 300 102-1/2, ETS 300 122, ETS 300 196 

Other signaling protocols available (Basic Call Control) 



Q.SIG 

Compliance 

DPNSS 

Compliance 

DASS-2 

Compliance 

CORNET ® 

Compliance 

OTHERS… 

Other protocols available 

FRAME RELAY, FR2K 

option 

Compliance 

Controlling protocol 

(LMI) 

IP suite 

Compliance 

ISO/IEC 11572, ETS 300 172 

BT BTNR 188 

BT BTNR 190 

13.9. Power with Internal Batteries 

Siemens ® CorNet ® -N, -NX, -NQ, -T 

1TR6, TN1R6 ® , VN4, X.25, X.31 

FRF.1.1, FRF.3.1, FRF.12.1, FRF.14.0 

ANSI T1.617, ITU-T Q.933, Original LMI Cisco 

RFC791, 792, 1350, 1618, 1661, 2427 

NO. OF BATTERIES One packet of 5 elements 

TYPE Rechargeable Ni-MH 

NOMINAL VOLTAGE 1,2 V 

CAPACITY 1500 mA/h 

DEAD BATTERY 

WARNING 

13.10. Power with External Adapter 

Graphic display and acoustic signal 

MAINS VOLTAGE 230 Vac +- 10% @ 50 Hz 



MAINS VOLTAGE 

(with universal 

adapter 531000064) 

DIRECT VOLTAGE 10 Vcc 

Rechargeable NiMH Batteries 

115/230 Vca +- 10% @ 50 Hz-60Hz 

OPERATING TIME ≅3 hours @ 25°C, without backlight 

RECHARGE ≅3 hours when the devise is switched off, ≅6 

hours when the devise is switched oon @ 25°C 

Power Connection 

INPUT POWER POWER IN, used for battery recharge 

CONNECTOR jack 5 mm 

OUTPUT POWER POWEWR OUT, used for accessories 

CONNECTOR 4-wire mini DIN, accessory recognition included 

13.11. Miscellaneous 

Supplementary services supported 

ETSI E-DSS1 MSN, SUB, CLIR, COLR, COLP, CLIP, 3PTY, 

AOC, CFB, CFNR, CFU, CUG, CW, CD, DDI, 

ECT, HOLD & RETRIEVE, MCID, TP, UUS, 

CCBS, CHARGE ADVISE, KEYPAD. 

Display 

DISPLAY AREA 240 x 200 pixel 

BACKLIT 

With CA/CC adapter 

With batteries 

Acoustics 

100% brightness 

80 % brightness, 10% brightness when not 

used for 5 minutes. Press any key to turn it on. 



BUILT-IN 

MICROPHONE 

BUILT-IN SPEAKER volume adjustable from +9 to -15 dB 

HANDSET 

CONNECTOR 

Mechanics 

RJ-9, 600 Ω 

WEIGHT 1 kg (2.3 pounds) 

DIMENSIONS 65 x 130 x 260 mm (2.5 x 5.1 x 10.2 inches), 

included holster 

13.12. Data Connection 

RS 232 

CONNECTOR internally optically insulated D-9 (V.28 CCITT 

ISO4902) for PC, printing and remote control 

DATA RATE 4800, 9600, 19200, 38400, 57600, and 115200 

bit/s 

MAX DATA RATE 

WITH KIT SPK-2K 

APPLIED 

230400 bit/s 

TO PRINTER supports ASCII 

TO PC/NOTEBOOK dump + settings and remote control with ISDN 

software 

V.11 

CONNECTOR D-15 (V.11 ISO4903) for digital access to B 

channel 

13.13. Use and Storage Conditions 

OPERATING 

TEMPERATURE 

-5°C ÷ +45 °C 



OPERATING 

TEMPERATURE LIMIT 

RELATIVE 

OPERATING 

HUMIDITY (without 

condensation) 

STORAGE 

TEMPERATURE 

-10°C ÷ +55°C 

≤ 93% RH @ 40°C 

≤ 70% RH @ 55°C 

-40 ÷ +70 °C 

13.14. Reference Regulations (reliability tests) 

STORAGE CEI 50-3 

CEI EN 60068-2-1 

IEC 68-2-2 

TRANSPORT CEI 50-6 

IEC 68-2-32 

IEC 68-2-35 

OPERATING 

CONDITIONS 

CONDUCTED 

EMISSIONS 

IRRADIATED 

EMISSION 

CEI 50-3 

CEI EN 68068-2-1 

IEC 68-2-2 

IEC 68-2-3 

IEC 68-2-14 

CEI 50-6 

IEC 68-2-31 

IEC 68-2-32 

IEC 68-2-35 

CEI EN 55022 

CEI EN 55022 

IMMUNITY CEI EN 50082-1 



SAFETY CEI EN 61010-1 

CEI EN 41003 

CEI EN 60950 

This product complies with requirements of the EMC Directive 

89/336/EC and Low Voltage Directive 73/23/EC, as amended by 

Directives 92/31/EC and 93/68/EC. 



APPENDIX A 

160 APPENDIX A


CONNECTOR TERMINATIONS 

A.1. PRIMARY RATE (P.R.I.) 

ISO8877 standard connector - 120Ω impedance 

PI 

N 

1 RX 

2 RX 

4 TX 

5 TX 

FUNCTION 

Plug ISO 8877 

A.2. BASIC RATE (B.R.I.) 

A.2.1 “S/T” interface 

1 

ISO8877 standard connector - 100Ω impedance 

PI 

N 

FUNCTION 

TE Remote 

power 

3 TX + PWR + 

4 RX + PWR - 

5 RX - PWR - 

6 TX - PWR + 

Plug ISO 8877 

1 

The remote power supply pin assignment, displayed above, is related to 

the supply provided by the NT1 in normal operation conditions. 

APPENDIX A 161


A.2.2 “U” interface 

PI 

N 

4 LINE 

5 LINE 

FUNCTION 

A.3. V.11 (as DCE) 

Pi 

n 

Plug ISO 8877 

1 

V.11 Function Criteria direction 

2 R(A) Rx Data In From DTE to DCE 

9 R(B) Rx Data In From DTE to DCE 

4 T(A) Tx Data Out From DCE to DTE 

11 T(B) Tx Data Out From DCE to DTE 

6 S(A) Clock out From DCE to DTE 

13 S(B) Clock out From DCE to DTE 

7 B(A) Byte-timing out From DCE to DTE 

14 B(B) Byte-timing out From DCE to DTE 

5 I(A) Indication out From DCE to DTE 

12 I(B) Indication out From DCE to DTE 

3 C(A) Control In From DTE to DCE 

10 C(B) Control In From DTE to DCE 

162 APPENDIX A


A.4. RS.232 

PIN 

* 

RS 

232 

DEVICE PERSONAL 

COMPUTER 

2 C104 Transmission Reception 

3 C103 Reception Transmission 

5 C102 Ground Signal Ground Signal 

*Ending with 9-pole standard connector. 

A.5. HANDSET TYPE 

TYPE “1” 

PI 

N 

1 TX + 

2 TX - 

3 RX + 

4 RX - 

FUNCTION 

Plug RJ 9 

1 

*The transmission/reception impedance is 600Ω in external direct mode. 

TYPE “2” 

PI 

N 

1 RX - 

2 TX + 

3 TX - 

4 RX + 

FUNCTION 

Plug RJ 9 

1 

APPENDIX A 163


A.6. RS232 – Modem connection 

The diagram below shows the basic connection between a device and a 

modem or a printer (DCE). The device does not support the C105 and 

C108 criteria control. 

With this connection, you have to set in the modem (via software): 

IGNORE CRITERIA C108 (DTR) and C105 (RTS) 

Normally the majority of the modems allow this type of setting via 

software, but if you are not able to do that, follow the sketch below: 

The diagram below shows the connection between a device and a PC 

(DTE). The device doesn’t handle the C105 control lead. Use a 8N1 serial 

port configuration without any flow control mode. At least you may connect 

the pins 7-8 as in the draw below. 

All pins-out are referred to a 9 poles connector. 

164 APPENDIX A


A.7. G.703 120Ω connector with HDSL/SHDSL terminations 

In case of NTs over HDSL/SHDSL devices, you may find the following 

connectors: 

M4 

2Mbit/s (120Ω) 

Connector D-SUB DIN 41652 9 pins F 

Pin Wire Signal Descript 

ion 

1 

2 

3 

4 

5 

6 

7 

8 

9 

b 

a 

b 

a 

2 Mbit/s 

outgoing 

2 Mbit/s 

incoming 

1/0 

Tx 

network 

Rx 

network 

APPENDIX A 165


APPENDIX B 

166 APPENDIX B


CONNECTIONS 

B.1. LT-U2K 

BRI LT-U mode 

B.2. D1029N 

BRI NT-S mode with phantom power feed to TE on S/T Bus 

B.3. RJ45 ADAPTER 

B.3.1. BRI/PRI TE Test mode 

APPENDIX B 167


B.3.2. BRI TE Test mode with 2 TEs 

B.3.3. TE mode BRI/PRI 

B.3.4. MON mode 

168 APPENDIX B


B.3.5. SPECIAL Mode (3 test instruments) 

B.4. D2022 BRI U-MON mode 

B.5. AB2000N 

POTS TE mode 

APPENDIX B 169


B.6. WT2000 S/T BUS Wiring Test mode 

B.7. VX2000 

DTE/DCE Tester mode 

B.8. MMC2000 

The V11/X.21 interface is embedded in the main unit (a software option must be installed) and then 

there’s no need for any external adapter. The optional adapter (VX2000) is required for the other 

Datacom interfaces (V.24, V.35, V.36, CO-DIR). 

MultiMediaCard memory extension. 

170 APPENDIX B


APPENDIX B 171

XDSL TESTER D2071 USER’S MANUAL 

APPENDIX C 

172 APPENDIX C


ISDN LOOPBOX STATE MACHINE 

APPENDIX C 173

D2500 - Telecom Analyzer - messkom.de

Create successful ePaper yourself

Delete template?

Save as template?