ZXJ10V10.0 (V03.

03Eu)
Digital SPC Switching System

User’s Manual
112 Line Tester Console

ZTE CORPORATION
ZXJ10V10.0 (V03.03Eu) Digital SPC Switching Systeming System
User’s Manual
112 Line Tester Console

Manual Version 20040730-R1.0

Product Version V03.03Eu.4

Copyright © 2003 ZTE Corporation

All rights reserved.

No part of this documentation may be excerpted, reproduced, translated, annotated or

duplicated, in any form or by any means without the prior written permission of ZTE
Corporation.

ZTE CORPORATION

ZTE Plaza, Keji Road South, Hi-Tech Industrial Park, Nanshan District, Shenzhen, P.R.China

Website: http://www.zte.com.cn

Postcode: 518057

Customer Support Center: (+86755) 26771900 800-9830-9830

Fax: (+86755) 26770801

Email: support@zte.com.cn

* * * *

S.N.:
Suggestions and Feedback
To improve the quality of ZTE product documentation and offer better services to our customers, we hope
you can give us your suggestions and comments on our documentation and fax this form to +86-755-
26770160; or mail to “Marketing center 3 rd floor ZTE Plaza, Keji Road South, Hi-Tech Industrial Park,
Nanshan District, Shenzhen, P. R. China”. Our postcode is 518057.

Document name ZXJ10V10.0 (V03.03Eu) Digital SPC Switching System User’s Manual 112 Line Tester Console
Product version V03.03Eu.4 Document version 20040730-R1.0
Equipment installation time
Your information

Name Company

Postcode Company address

Telephone E-mail

Presentation: How is information presented? (Introductions, procedures, illustrations, others)

□ Good □ Fair □Average □ Poor □Bad

Your evaluation Accessibility: Can you find the information you want? (Table of contents, Index, headings,
of this numbering, others)

documentation □ Good □ Fair □Average □ Poor □Bad

Intelligibility: Can you understand it when you find it? (Language, vocabulary, readability, others)

□ Good □ Fair □Average □ Poor □Bad

Presentation:

Your suggestions
Accessibility:
for improvement
of this
documentation
Intelligibility:

Your other
suggestions on
ZTE product
documentation
The product ZXJ10 （ V10.0 ） Digital SPC Switching System complies with the
essential protection requirements of the Low Voltage Directive (EC Directive
73/23/EEC) and Electromagnetic Compatibility Directive (EC Directive 89/336/EEC)
and their amendments.

Assessment of compliance of the product with the requirements relating to low voltage
directive (EC Directive 73/23/EEC) and Electromagnetic Compatibility Directive (EC
Directive 89/336/EEC) and their amendments was performed by German TUV Product
Service GMBH, based on the following standards:

EN60950:2000

Safety of information technology equipment

ETSI EN300 386 V1.3.1 2001-09

Electromagnetic compatibility and Radio spectrum Matters (ERM);

Telecommunication network equipment, Electromagnetic Compatibility (EMC)
requirements

Warning:
This is a class A product. In a domestic environment this product may cause radio
interference in which case the user may be required to take adequate measures.
Preface

About This Manual

The ZXJ10V10.0 (V03.03Eu) Digital SPC Switching System (hereinafter ZXJ10 for
short, unless otherwise specified) has the functions of local switching and toll
switching, and the combined function of local switching and toll switching. As the
PSTN continues to develop, this kind of switch can adapt to the development trend of
emerging technologies and the requirements for internetworking. It helps to improve
the network’s sustainability and lowers the overall operational cost of the whole
network.

ZXJ10 has a powerful processing capability, rich service functions and flexible
networking modes. Apart from use in the PSTN and N-ISDN networking, it is also
applicable to the SDH, No.7 signaling network, Telecommunications Management
Network (TMN), and Intelligent Network (IN). The products that have been developed
with ZXJ10 as the platform include ZXIP10-Access Server (AS), ZXIN10 IN system,
ZXSS1010 soft switching system gateway, ZXG10-Mobile Switching System (MSS)
and ZXC10-MSS. We have a good reason to believe that ZXJ10 will have a broader
and broader application prospect in the construction of many networks.

How to Use This Manual

This chapter consists of 6 chapters.

Chapter 1, 112 Server Installation, introduces how to install 112 server.

Chapter 2, Installation of 112 Local Maintenance Console, introduces how to install

112 local maintenance consoles.

Chapter 3, Installation of 112 Remote Server, introduces how to install 112 remote
servers.

Chapter 4, 112 Acceptance and Test Desk, presents the functions of 112 acceptance
and test desk, such as accepting and saving the telephone fault reports from users and
measuring and saving performance indices of phone sets. It also presents the functions
of 112 system administrator, such as dispatch and troubleshooting, 112 user card
 management, routine test management, management of acceptance and test desk and
112 system management.

Chapter 5, 112 Common Interface, deals with 112 concentrated test interface
program.

Chapter 6, Remote Module 112 line tester console, presents the functions and
installation of the remote module 112 line tester console.

Conventions
1. Notational convention

Angular brackets “<and>” identify names of keys and buttons, and the
information typed by an operator from a terminal

Square brackets “[and]” indicate a man-machine interface, menu item, data list
or field name. The symbol “→” separates a multi-level menu, e.g., [File→
New→ Folder] indicates the [Folder] menu item under the [New] submenu of
the menu [File].

2. Keyboard Operation Convention

Format Description
Characters within angular Indicate a key or button name, e.g., <Enter>, <Tab>,
brackets <Backspace>, and <a>
<Key 1+Key 2> Press Key 1 and Key 2 at the same time.
<Key 1, Key 2> Press Key1 first. Then release Key 1 and press Key 2

3. Mouse Operation Convention

Format Description
Click Refers to clicking the primary mouse button (usually the left
mouse button) once
Double-click Refers to quickly clicking the primary mouse button (usually the
left mouse button) twice
Right-click Refers to clicking the secondary mouse button (usually the right
mouse button) once.
Drag Refers to pressing and holding a mouse button and move the
mouse

4. Danger, Warning, Caution and Note Statements

Danger, Warning, Caution and Note statements

 are used throughout this manual to emphasize important and critical
information. You must read these statements to help ensure safety and to prevent
product damage. The statements are defined below.

Danger:

Indicates an imminently hazardous situation which, if not avoided, will result in death
or serious injury. This signal word is to be limited to the most extreme situations.

Warning:

Indicates a potentially hazardous situation which, if not avoided, could result in death
or serious injury.

Caution:

Indicates a potentially hazardous situation which, if not avoided, could result in minor
or moderate injury. It may also be used to alert against unsafe practices.

Note:

A Note statement is used to notify people of installation, operation, or maintenance

information that is important, but not hazard-related.

 Tips:
Indicates a suggestion or hint to make things easier or more productive for the reader

Statement: The actual product may differ from what is described in this
manual due to frequent update of ZTE products and fast development of
technologies. Please contact the local ZTE office for the latest updating
information of the product.
Contents

1 112 Server Installation..............................................................................................................................1-1

1.1 Installation Contents.........................................................................................................................1-1

1.2 112 Server Installation......................................................................................................................1-1

1.2.1 Installation Preparations........................................................................................................1-1

1.2.2 Installation Procedure............................................................................................................1-1

1.3 Installation Check.............................................................................................................................1-3

1.4 Descriptions of Installation Files.....................................................................................................1-3

2 Installation of 112 Local Maintenance Console......................................................................................2-1

2.1 Installation Contents.........................................................................................................................2-1

2.2 Contents............................................................................................................................................2-1

2.3 112 Server Installation......................................................................................................................2-1

2.3.1 Installation Preparations........................................................................................................2-1

2.3.2 Installation Procedure............................................................................................................2-1

2.4 Installation Check.............................................................................................................................2-2

2.5 Descriptions of Installation Files.....................................................................................................2-2

3 112 Remote Server Installation................................................................................................................3-1

3.1 Installation Contents.........................................................................................................................3-1

3.2 112 Server Installation......................................................................................................................3-1

3.2.1 Installation Preparations........................................................................................................3-1

3.2.2 Installation Procedure............................................................................................................3-1

3.3 Installation Check.............................................................................................................................3-1

3.4 Descriptions of Installation Files.....................................................................................................3-1

4 112 Acceptance and Test Desk..................................................................................................................4-1

-i-
 4.1 112 Acceptance and Test Desk.........................................................................................................4-1

4.1.1 Running 112 Acceptance and Test desk................................................................................4-2

4.1.2 112 Complaints Acceptance..................................................................................................4-6

4.1.3 112 Test..................................................................................................................................4-8

4.2 112 System Administrator..............................................................................................................4-13

4.2.1 Running 112 System Administrator....................................................................................4-13

4.2.2 Dispatch and Troubleshooting............................................................................................4-21

4.2.3 User Card Management.......................................................................................................4-26

4.2.4 Routine Test Management...................................................................................................4-29

4.2.5 Test Desk Configuration......................................................................................................4-35

5 112 Common Interfaces............................................................................................................................5-1

5.1 Overview..........................................................................................................................................5-1

5.2 Operating Environment....................................................................................................................5-1

5.2.1 Usage Mode...........................................................................................................................5-1

5.2.2 Function Descriptions...........................................................................................................5-2

5.3 Hardware Connection during Centralized Test................................................................................5-3

5.4 Command Interface..........................................................................................................................5-6

5.4.1 Centralized Test Command...................................................................................................5-6

5.4.2 Emulation Test Command.....................................................................................................5-6

5.4.3 Output Format.......................................................................................................................5-7

5.5 Installation and Running of 112 Common Interface Program.......................................................5-15

5.6 Configuration Modes......................................................................................................................5-21

5.6.1 Serial Port Configuration Mode..........................................................................................5-21

5.6.2 Telnet Configuration Mode.................................................................................................5-22

5.7 112 Test for the Unified Interface Program...................................................................................5-23

5.7.1 System Overview................................................................................................................5-23

5.7.2 Unified Interface Configuration..........................................................................................5-24

-ii-
 5.7.3 Entering Unified Interface Settings....................................................................................5-25

5.7.4 Selecting Interface Services................................................................................................5-25

5.7.5 Service and Communication Configuration.......................................................................5-26

5.7.6 Completing the Configuration............................................................................................5-30

5.7.7 Re-Configuring....................................................................................................................5-31

5.7.8 Executing the Unified Interface Program...........................................................................5-32

5.7.9 Input and Output of Unified Interface Program 112 Test...................................................5-34

6 Remote Module 112 line tester console....................................................................................................6-1

6.1 Overview..........................................................................................................................................6-1

6.2 Networking Requirements................................................................................................................6-1

6.3 Installation Procedure.......................................................................................................................6-1

6.3.1 Computer Installation............................................................................................................6-1

6.3.2 Background Installation........................................................................................................6-2

6.4 Data Configuration...........................................................................................................................6-5

6.4.1 Data Configuration................................................................................................................6-5

6.4.2 Operations.............................................................................................................................6-5

6.5 Precautions for Debugging...............................................................................................................6-5

-iii-
A List of Figures

Fig. 1.2-1 Selecting Line Tester Console in Server Installation...........................................................1-2

Fig. 1.2-2 Dialog Box for Confirming the Re-Initializing of Line Tester Database............................1-2

Fig. 1.2-3 Progress Bar of Line Tester Installation...............................................................................1-2

Fig. 2.3-1 Selecting 112 Subsystems in the Local Maintenance Console Installation.........................2-2

Fig. 4.1-1 Diagram of Logical Relationship between the 112 Acceptance and Test desk and the
Switching System...................................................................................................................................4-1

Fig. 4.1-2 Login Interface of Line Tester..............................................................................................4-2

Fig. 4.1-3 Interface of Line Tester Traffic Configuration.....................................................................4-2

Fig. 4.1-4 Prompt for Error in Reading the Operator Console Number...............................................4-3

Fig. 4.1-5 Main Interface of 112 Acceptance and Test Desk................................................................4-4

Fig. 4.1-6 Prompt of Expired Initialization of OPR Timer...................................................................4-4

Fig. 4.1-7 Interface Change when there is Waiting Call.......................................................................4-7

Fig. 4.1-8 112 Test Results....................................................................................................................4-8

Fig. 4.1-9 Read Files...........................................................................................................................4-10

Fig. 4.1-10 Panel of External/Internal Test Options...........................................................................4-11

Fig. 4.1-11 Panel of Phone Performance Test Options.......................................................................4-11

Fig. 4.1-12 Panel of Phone Performance Test Conclusion Selection.................................................4-11

Fig. 4.1-13 Panel of ISDN Test Options.............................................................................................4-12

Fig. 4.1-14 Panel of Auxiliary Functions (Subscriber Status is Selected)..........................................4-12

Fig. 4.1-15 Panel of Auxiliary Functions (Test Card Self-Diagnosis is Selected).............................4-13

Fig. 4.2-1 Login Interface of 112 System Administrator....................................................................4-13

Fig. 4.2-2 Main Interface of 112 System Administrator.....................................................................4-14

Fig. 4.2-3 Submenu of Dispatch and Troubleshooting.......................................................................4-15

-i-
Fig. 4.2-4 Submenu of Routine Test Task...........................................................................................4-15

Fig. 4.2-5 Submenu of User Card Management.................................................................................4-15

Fig. 4.2-6 Submenu of the Acceptance and Test Desk.......................................................................4-15

Fig. 4.2-7 Submenu of System............................................................................................................4-16

Fig. 4.2-8 Window of Modifying Critical Data of the Fault Judgment..............................................4-17

Fig. 4.2-9 Window of Modifying Administrator Password................................................................4-18

Fig. 4.2-10 Window of Modifying Serial Number.............................................................................4-18

Fig. 4.2-11 Window of Deleting Complaint and Test File..................................................................4-19

Fig. 4.2-12 Window of Modifying Normal Value...............................................................................4-19

Fig. 4.2-13 Window of Modifying Office Code.................................................................................4-20

Fig. 4.2-14 Window of Setting Automatic Print of Dispatch Sheet...................................................4-21

Fig. 4.2-15 Test Results.......................................................................................................................4-22

Fig. 4.2-16 Complaints and Acceptance.............................................................................................4-23

Fig. 4.2-17 Input Window to Universal Query Conditions.................................................................4-24

Fig. 4.2-18 Interface of Dispatch and Troubleshooting......................................................................4-25

Fig. 4.2-19 Printing the Dispatch Sheet..............................................................................................4-25

Fig. 4.2-20 User Card..........................................................................................................................4-26

Fig. 4.2-21 Interface of Editing 112 User Card..................................................................................4-27

Fig. 4.2-22 Batch Print........................................................................................................................4-28

Fig. 4.2-23 Converting User Card.......................................................................................................4-29

Fig. 4.2-24 Routine Test Task..............................................................................................................4-30

Fig. 4.2-25 Routine Test Results.........................................................................................................4-31

Fig. 4.2-26 Edit Table of Routine Test Task........................................................................................4-32

Fig. 4.2-27 Editing the Routine Test Registration..............................................................................4-32

Fig. 4.2-28 Fault Type Selection.........................................................................................................4-34

Fig. 4.2-29 Reading Detailed Routine Test Results............................................................................4-34

Fig. 4.2-30 Password Input Box..........................................................................................................4-35

-ii-
Fig. 4.2-31 Test Desk Configuration...................................................................................................4-35

Fig. 4.2-32 Adding Operator of the Acceptance and Test Desk.........................................................4-36

Fig. 5.2-1 Schematic Diagram of Running Environment of a Emulation Test....................................5-2

Fig. 5.3-1 Position of the Test Interfaces and Test Bus on the User Unit Backplane...........................5-3

Fig. 5.3-2 Backplane of the Switch Test Board....................................................................................5-5

Fig. 5.3-3 Backplane of the User Board................................................................................................5-5

Fig. 5.5-1 Login Interface...................................................................................................................5-16

Fig. 5.5-2 Common Interface Program Interface................................................................................5-17

Fig. 5.5-3 Selecting User Source and Output Mode...........................................................................5-17

Fig. 5.5-4 Log Query Window............................................................................................................5-18

Fig. 5.5-5 Port Selection Interface......................................................................................................5-19

Fig. 5.5-6 Terminal Settings................................................................................................................5-20

Fig. 5.5-7 Communication Parameter Settings...................................................................................5-20

Fig. 5.5-8 Connection Mode Selection...............................................................................................5-21

Fig. 5.6-1 Setting ODBC.....................................................................................................................5-22

Fig. 5.6-2 Telnet Connection...............................................................................................................5-23

Fig. 5.7-1 Interface Machine Structure Diagram................................................................................5-24

Fig. 5.7-2 Welcome Interface of Unified Interface Configuration File Creation Guide....................5-25

Fig. 5.7-3 Selecting Interface Services...............................................................................................5-26

Fig. 5.7-4 Configuring Services of 112 Test External Serial Port......................................................5-27

Fig. 5.7-5 Setting 112 Test External Serial Port Communication.......................................................5-28

Fig. 5.7-6 Configuring 112 Test External TCP/IP Services................................................................5-29

Fig. 5.7-7 Configuring 112 Test External TCP/IP Communication....................................................5-30

Fig. 5.7-8 Prompt Window..................................................................................................................5-30

Fig. 5.7-9 Completion Window...........................................................................................................5-31

Fig. 5.7-10 Prompt of Existed Configuration File..............................................................................5-31

Fig. 5.7-11 Interface of Checking Configurations..............................................................................5-32

-iii-
Fig. 5.7-12 Running Window of Unified Interface Program..............................................................5-33

Fig. 6.2-1 Networking of Remote Module 112 line tester console.......................................................6-1

Fig. 6.3-1 Selecting the Installation Type.............................................................................................6-2

Fig. 6.3-2 Selecting the Terminal Type and Installation Mode.............................................................6-3

Fig. 6.3-3 Selecting the Maintenance Module......................................................................................6-4

Fig. 6.3-4 Subsystem Installation..........................................................................................................6-4

Fig. 6.3-5 Start the Installation..............................................................................................................6-5

Fig. 6.3-6 Installing...............................................................................................................................6-5

-iv-
A list of Tables

Table 5.3-1 Distribution of Test Lines of Test Ports.............................................................................5-4

Table 5.7-1 Structure Table of Command Messages..........................................................................5-34

Table 5.7-2 Structure Table of Data Messages....................................................................................5-35

Table 5.7-3 Data Structure Table of Command Response..................................................................5-35

Table 5.7-4 Data Structure Table of Data Response...........................................................................5-36

-i-
1 112 Server Installation

This chapter introduces how to install 112 server.

1.1 Installation Contents

112 server installation will install 112 system administrator, 112 acceptance and test
desk and 112 routine test process into the ZXJ10 background server. And it will create
and initialize 112 database.

1.2 112 Server Installation

1.2.1 Installation Preparations

For the background server, before the ZXJ10 background operation & maintenance
system is installed, it is required to correctly install the operating system and database
software.

1.2.2 Installation Procedure

In the subsystem options of the installation program of the ZXJ10 background

maintenance system, select 112, and if it’s the first time to install 112, “DB
Initialization” will be checked automatically, as shown in Fig. 1.2 -1. If the 112
database has been created and “DB Initialization” is checked, the interface shown in
Fig. 1.2 -2 will pop up. In it, click <Yes> to confirm the re-initializing of the 112
database. In the installation, the system will clear all the data of the 112 subsystem
database.

1
Fig. 1.2-1 Selecting Line Tester Console in Server Installation

Fig. 1.2-2 Dialog Box for Confirming the Re-Initializing of Line Tester Database

After the installation begins, when 112 subsystem is being installed, a progress bar of
112 subsystem installation will appear, indicating the progress of 112 subsystem
installation, as shown in Fig. 1.2 -3.

Fig. 1.2-3 Progress Bar of Line Tester Installation

2
 Chapter 1 112 Server Installation

1.3 Installation Check

After the 112 subsystem software is installed, start the ZXJ10 server process
management program, and then the 112 routine test process program will be started
automatically. And start the ZXJ10 background operation & maintenance system, in its
floating menu, [Service management → Line tester console] and [Service management
→ 112 system administrator] are enabled.

1.4 Descriptions of Installation Files

After the 112 subsystem software is installed, the following files and directories will be
added under the directory ZXJ10 of the system drive letter:

 File AGTDPR.exe: 112 system administrator program.

 File T112DPR.exe: 112 acceptance and measurement program.

 File Rout_112.exe: 112 routine test program.

 Files New112.hlp and New112.cnt: 112 help files.

 Files BackOS.dll and OprCall.dll: The background dynamic link library of the
ACDS.

Directory CallData: The directory saving the files generated when 112 routine test
process is picking tasks.

3
2 Installation of 112 Local Maintenance
Console

This chapter introduces how to install 112 local maintenance console.

2.1 Installation Contents

2.2 Contents
The installation of 112 local maintenance console will install 112 acceptance and test
desk.

2.3 112 Server Installation

2.3.1 Installation Preparations

For the local maintenance console, before the ZXJ10 background operation &
maintenance system is installed, it is required to correctly install the operating system
and database software.

2.3.2 Installation Procedure

In the subsystem options of the installation program of he ZXJ10 background

maintenance system, select 112, as shown in Fig. 2.3 -4.

1
 Fig. 2.3-4 Selecting 112 Subsystems in the Local Maintenance Console Installation

After the installation begins, when 112 subsystem is being installed, a progress bar of
112 subsystem installation will appear, indicating the progress of 112 subsystem
installation.

2.4 Installation Check

After the 112 subsystem software is installed, start the ZXJ10 background operation &
maintenance system. In its floating menu, [Service management → Line tester console]
and [Service management → 112 system administrator] are enabled.

2.5 Descriptions of Installation Files

After the 112 subsystem software is installed, the following files will be added under
the directory ZXJ10 of the system drive letter.

 File AGTDPR.exe: 112 system administrator program.

 File T112DPR.exe: 112 acceptance and measurement program.

 Files New112.hlp and New112.cnt: 112 help files.

 Files BackOS.dll and OprCall.dll: The background dynamic link library of the
ACDS.

2
 Chapter 2 Installation of 112 Local Maintenance Console

 Directory CallData: The directory saving the files generated when 112 routine
test process is picking tasks.

3
3 112 Remote Server Installation

This chapter introduces how to install 112 remote server.

3.1 Installation Contents

112 remote server installation will install 112 system administrator, 112 acceptance and
test desk and 112 routine test process into the ZXJ10 remote server. And it will create
and initialize 112 database.

3.2 112 Server Installation

3.2.1 Installation Preparations

For the remote server, before the ZXJ10 background operation & maintenance system
is installed, it is required to correctly install the operating system and database
software.

3.2.2 Installation Procedure

112 remote server is installed in the similar way to installing 112 server, except that
after the installation program is completed, it is required to copy the file
\...\install\112\remote\T112dpr.exe into the directory ZXJ10 of the system drive letter.

3.3 Installation Check

After the 112 subsystem software is installed, start the ZXJ10 server process
management program, and then the 112 schedule test process program will be started
automatically. And start the ZXJ10 background operation & maintenance system, in its
floating menu, [Service management → Line tester console] and [Service management
→ 112 system administrator] are enabled.

3.4 Descriptions of Installation Files

After the 112 subsystem software is installed, the following files and directories will be
added under the directory ZXJ10 of the system drive letter.
1
 File AGTDPR.exe: 112 system administrator program.

 File T112DPR.exe: 112 acceptance and measurement program.

 File Rout_112.exe: 112 routine test program.

 Files New112.hlp and New112.cnt: 112 help files.

 Files BackOS.dll and OprCall.dll: The background dynamic link library of the
ACDS.

 Directory CallData: The directory saving the files generated when 112 routine
test process is picking tasks.

2
4 112 Acceptance and Test Desk

This chapter consists of: 112 acceptance and test desk, which accepts and saves the telephone fault
reports from users, and measures and saves performance indices of phone sets; 112 system
administrator, which can implement such functions as dispatch and troubleshooting, 112 user card
management, routine test management, management of acceptance and test desk and 112 system
management.

4.1 112 Acceptance and Test Desk

112 concentrated fault acceptance and measurement system (112 system for short) is designed based
on the related telecom standards and actual requirements of telecom office. Featuring rather high
measuring precision and accuracy and brief fault judging capability, it can satisfy the requirements
of accepting and measuring 112 fault reports in the 112 system. The logical relationship between the
112 system and the entire switching system is shown in Fig. 4.1 -5.

Foreground

Foreground Foreground 112

database process

Background
112 acceptance and
112 database test desk

Background ZDBFUNC
database

Fig. 4.1-5 Diagram of Logical Relationship between the 112 Acceptance and Test desk and the Switching System

4.1.1 Running 112 Acceptance and Test desk

1. Interface entry

1
 In the floating menu of the background maintenance system, click [Service management →
Line tester console], and then the login interface of the 112 acceptance and test desk will
appear, as shown in Fig. 4.1 -6.

Fig. 4.1-6 Login Interface of Line Tester

If the 112 acceptance and test desk runs for the first time, it is required to implement the
corresponding traffic configuration. Click [Configuration] to enter the configuration interface,
as shown in Fig. 4.1 -7. After the configuring, click <Save> to save the console
configuration.

Fig. 4.1-7 Interface of Line Tester Traffic Configuration

2
 Chapter 4 112 Acceptance and Test Desk

Note:

In the floating menu of the background maintenance system, select [Data management → Other →
Synthetic traffic console configuration], to configure the 112 acceptance and measurement consol
traffic according to the related configurations. And if the operator consol number is not configured
correctly, the system will prompt “Wrong OP Console number” in the login process, as shown in Fig.
4.1 -8.

Fig. 4.1-8 Prompt for Error in Reading the Operator Console Number

In the interface shown in Fig. 4.1 -6, input the correct operator ID and password to enter the main
interface of 112 acceptance and test desk, as shown in Fig. 4.1 -9.

3
ZXJ10V10.0 (V03.03Eu) Digital SPC Switching System User’s Manual (112 Liner Tester Console)

Fig. 4.1-9 Main Interface of 112 Acceptance and Test Desk

When the traffic consol has faults, such as the initialization of operator position timer expires, 112
acceptance and test desk will display the corresponding error prompt and close it when the user
confirms it, as shown in Fig. 4.1 -10.

Fig. 4.1-10 Prompt of Expired Initialization of OPR Timer

1. Interface descriptions

The main interface of 112 acceptance and test desk falls into two parts: operation control area
and information display area, as shown in Fig. 4.1 -9.

The operation control areas are: 3 Input area of acceptance information, 4 Input area of the
phone sets to be tested, 5 Selection area of test options and 6 Command button area. The
information display area contains: 1 Result display area, 2 Traffic status display panel and 7
Status bar.

4
 Chapter 4 112 Acceptance and Test Desk

These seven areas are described as follows.

1) Result display area

Total Records: It displays the total records of the results displayed in the list. Current Record:
It displays the record number displayed in the current results list, and you can modify the
current record number to browse the record as required.

Result record list: It displays the test results, complaint records of users, routine test results
and other information.

Status prompt in the result display area: It is the white strip bar under the record list, for
displaying such information as test process and reference conclusion.

2) Traffic status display panel

Queue: It displays the ACDS status graphically, which can be divided into four types: idle,
with waiting call, busy traffic and lock.

User: It displays the user status graphically, which can be divided into four types: idle,
ringing, talking and busy.

Acceptance Phone: It displays the 112 phone set status graphically, which can be divided into
four types: idle, accept the talk, test the talk, hear busy tone, hear ring-back tone and
interception.

Text description: It reflects the quantity of the waiting calls in the ACDS and the current
status of the position, and it is divided into seven types: without waiting call, with waiting
call, locked, please accept the current call as soon as possible, please hook on and accept the
incoming call as soon as possible, please cancel the lock and accept the incoming call, please
hurry. And when there are waiting calls, the number of the first waiting call will be displayed
at the same time.

3) Input area of acceptance information

Faulty Phone: It records the phone number of the faulty phone set reported by the user. When
the user report is accepted, this user’s phone number will be input automatically.

Fault Description: According to user’s report, select the fault descriptions: No tone after
offhook, wrong number, can not call in, can not call out, unclear voice, cross-talk, phone set
fault, noise and other.

Contact Person: Input the information of the contact person of the faulty phone here.

Contact Phone: Input the information of the contact phone of the faulty phone here.

5
ZXJ10V10.0 (V03.03Eu) Digital SPC Switching System User’s Manual (112 Liner Tester Console)

4) Input area of the phone to be tested

To-Be-Tested Phone: Input the phone number of the to-be-tested phone set, or select the
phone number of the phone set to be tested for the complaints, to be tested again, to be tested
for missed routine test and to be tested for user card test.

5) Selection area of test options

Refer to 112 Test

6) Command button area

Refer to 112 Complaint Acceptance and 112 Test

7) Status bar

Prompt bar: It displays the prompt information in the process of accepting and testing.

Version bar: It displays the version information of [ZTE communication, connecting world].

Terminal information bar: It displays the terminal number.

Operator information bar: It displays the operator ID.

Desk DN bar: It displays the DN of the accepted phone.

4.1.2 112 Complaints Acceptance ПРИЕМ ЗАЯВОК.

1. Process of 112 complaints acceptance

When the user dials the 112 complaint phone, the interface displays the waiting calls and the
phone number of the first waiting call, and <Offhook> in the command button area becomes
<Accept>, indicating that operator can accept the incoming call, as shown in Fig. 4.1 -11.

6
 Chapter 4 112 Acceptance and Test Desk

Fig. 4.1-11 Interface Change when there is Waiting Call

After accepting the call, the traffic status display panel on the interface changes accordingly,
and <Accept> is disabled and <Onhook> is enabled. According to the user’s complaint, the
operator inputs contents in the acceptance information input area and hooks on, and then
<SaveAcceptance> is enabled. And it is possible to click <Lock> to lock this position.
Передача заявок в архив

2. Interface descriptions

1) Click <Offhook>, and the input box of the phone number of the called appears, the operator
can call the called user.

2) Click <Accept> to accept and current waiting call.

7
ZXJ10V10.0 (V03.03Eu) Digital SPC Switching System User’s Manual (112 Liner Tester Console)

3) Click <Onhook> to end the current talk.

4) Click <Lock> to lock this position.

5) Click <Monitor> to monitor the called user in the talk.

6) Click <SaveAcceptance> to save the acceptance information into the 112 database.

4.1.3 112 Test ТЕСТИРОВАНИЕ АБОН-ИХ ЛИНИЙ.

1. 112 test process

In the input area of the to-be-tested phone set, input the phone number of the to-be-tested
phone set, and select correct test type and options in the selection area of test options, and
then click <Execute> to start the 112 test. The test process and results will be displayed in the
result display area, as shown in Fig. 4.1 -12.

Fig. 4.1-12 112 Test Results

Through loading the corresponding data records, selecting the phone number of the to-be-
tested phone set and selecting the test options, click <Execute> to start the 112 test.

2. Interface descriptions описание интерфейса

1) Click <Execute> to execute the specified test options to the to-be-tested phone set.

2) Click <Stop> to stop the executing test.

8
 Chapter 4 112 Acceptance and Test Desk

3) Click <Load> and the [Read Files] window appears, as shown in Fig. 4.1 -13. Select the
types of the files to be loaded, and select/input the related conditions, click <OK>, and then
the system will display the loading results in the result display area. At the same time, the
phone numbers in the corresponding files will be added to the pull-down box of [To-Be-
Tested Phone] for selection. (загрузка)
 “Read complaint user files to be test since”: Load the complaint user files after the specified
date as the un-tested status.

 “Read files to be retested since”: Load the test files whose test results are faults and after the
specified date.

 “Read files with routine test not passed”: In the specified routine test files, load the files of the
tests that have not passed the routine test .

 “Read test and records of”: Load the test and complaint of the specified user number.

ВВОДИМ №аб-та .<OK>. Из архива извлекается тест .

 “Read user card”: Load the user card file of the specified user number.

ВВОДИМ №аб-кой карточки.<OK>.Из архива извл. Карточка аб-та.

Fig. 4.1-13 Read Files

4) Click <Print> to print the test results of the current to-be-tested phone set. For the normal

9
ZXJ10V10.0 (V03.03Eu) Digital SPC Switching System User’s Manual (112 Liner Tester Console)

printing, it is required to run 112 system administrator program on the background server and
save the test results. -?

5) Click <SaveTest> to save the test results of the current to-be-tested phone set into the 112
database. ПЕРЕДАЧА ТЕСТА B БАЗУ ДАННЫХ.

6) Click <Admin> to start the 112 system administrator program. АДМИНИСТРАТОР -112

7) Click <Modify>, and the window for modifying the test conclusion appears. In it, input user
phone number and test conclusion, and then click <OK> to modify the test conclusion of this
user’s test records in the 112 database. If 112 database does not contain the test records of this
user, the system will prompt [No test records of this user. Please do test and save the records,
and then modify it].

8) Panel of external/internal line test: It serves to select options of external/internal line test and
select/unselect the forced test on busy, as shown in Fig. 4.1 -14. The external/internal line test
options are: external voltage, external insulation resistance, external capacitance, ringing, loop
resistance and current, and internal test. During the test, you only can select one option or
combination of some options once: The loop resistance and current can only be selected
independently; external voltage, external insulation resistance, external capacitance can only
be selected at the same time; the forced test on busy can not be selected with ringing or
internal test.

Fig. 4.1-14 Panel of External/Internal Test Options

9) Panel of the phone performance test options: It serves to select the phone performance test
options, as shown in Fig. 4.1 -15. The phone performance test options are: ringing/offhook
test, send howler tone and dialing test. Only one option can be tested once. After the phone
performance test, enter the panel of selecting the phone performance test conclusions, and
“Normal” will be selected automatically and the system displays the prompt “Normal.
Confirm or not?”. Click <Yes>, this panel will automatically close; click <No>, you can re-
select the phone performance test conclusion and confirm it.

10
 Chapter 4 112 Acceptance and Test Desk

Fig. 4.1-15 Panel of Phone Performance Test Options

Fig. 4.1-16 Panel of Phone Performance Test Conclusion Selection

10) Panel of ISDN test: It serves to select ISDN test options, as shown in Fig. 4.1 -17. The ISDN
test options are: external voltage, external insulation resistance, external capacitance, LT far
supply, TE activate LT, TE activated by LT, LT activate TE, 2B+D self-loop test, and Statistics
of U interface frame errors. During the test, you can only select one option or combination of
some options once: LT activate TE, 2B+D self-loop test and statistics of U interface frame
errors can only be selected solely; external voltage, external insulation resistance, external
capacitance can only be selected at the same time.

Fig. 4.1-17 Panel of ISDN Test Options дополнительные

11) Panel of auxiliary functions: It serves to select auxiliary function options. And if the selected
option is related to the user, an edit box for inputting user number will be displayed in the
lower part of the panel, as shown in Fig. 4.1 -18. If the selected option is related to the test
card, an edit box for inputting the physical location of the test card will be displayed in the
lower part of the panel, as shown in Fig. 4.1 -19. The auxiliary function options are:
Subscriber status, test card state, block test card, unblock test card, test card self-diagnosis,

11
ZXJ10V10.0 (V03.03Eu) Digital SPC Switching System User’s Manual (112 Liner Tester Console)

release test card, block subscriber and unblock subscriber. Only one of these options can be
selected once. Включ./Выключ. Абонентов. Статус абонента.

Fig. 4.1-18 Panel of Auxiliary Functions (Subscriber Status is Selected)

Fig. 4.1-19 Panel of Auxiliary Functions (Test Card Self-Diagnosis is Selected)

4.2 112 System Administrator Установлен новый код AD 112

4.2.1 Running 112 System Administrator

112 system administrator is the tool managing all the 112-related resources and functions in the
ZXJ10 switching system. It can implement such functions as dispatch and troubleshooting, 112 user
card management, routine test management, management of acceptance and test desk and 112
system management.

1. Interface entry

In the floating menu of the background maintenance system, click [Service management →
112 system administrator], and then the login interface of the 112 system administrator will
appear, as shown in Fig. 4.2 -20.

12
 Chapter 4 112 Acceptance and Test Desk

Fig. 4.2-20 Login Interface of 112 System Administrator <ZXJ10> new cod : AD112

In the interface shown in Fig. 4.2 -20, input the correct system administrator password to
enter the main interface of 112 system administrator, as shown in Fig. 4.2 -21.

Fig. 4.2-21 Main Interface of 112 System Administrator

2. Interface descriptions

The main interface of the 112 system administrator consists of three parts: menu bar, function
selection area and data area. In the menu bar, [TestResult] contains no submenu. And the other
submenus, except the [system] submenu, such as [Dis and Trb], [Routine Task], [UserCard]
and [Manage <Line Tester> Accept], correspond to the options in the function selection area.
The data area is divided into the data display area and data command area. The data display
13
ZXJ10V10.0 (V03.03Eu) Digital SPC Switching System User’s Manual (112 Liner Tester Console)

area serves to display and edit data, and the data command area serves to display the
command buttons related to the corresponding data. For sub-functions in the function
selection area, this chapter will describe the command buttons in the data command area in
detail. This section only lists the submenus of the main menu, and describes the function
interfaces of the system submenu in detail, and other sub-functions will be presented in
subsequent sections.

1) The submenu of dispatch and troubleshooting is shown in Fig. 4.2 -22.

Fig. 4.2-22 Submenu of Dispatch and Troubleshooting

2) The submenu of routine test task is shown in Fig. 4.2 -23.

Fig. 4.2-23 Submenu of Routine Test Task

3) The submenu of user card management is shown in Fig. 4.2 -24.

Fig. 4.2-24 Submenu of User Card Management

4) The submenu of the acceptance and test desk is shown in Fig. 4.2 -25.

14
 Chapter 4 112 Acceptance and Test Desk

Fig. 4.2-25 Submenu of the Acceptance and Test Desk

5) The submenu of system is shown in Fig. 4.2 -26.

Fig. 4.2-26 Submenu of System

 Click [System → Modify Critical Data], and the window of modifying the critical data of the
fault judgment appears, as shown in Fig. 4.2 -27. This window serves to modify the critical
value of the external voltage, resistance and capacity of the fault judgment, according to the
local geographical environment and line conditions and experience, to make the judgment
more exact.

Lower limit of AB Res.: The value range is 0.6 ~ 2, and the default value is 1. When the
resistance between A and B is less than this value, we can judge the mixed AB wires.

Middle limit of AB Res.: The value range is 20~100, and the default value is 20. When the
resistance between A and B is less than this value and not less than the lower limit of AB
resistance, we can judge that user insulation is bad.

Upper limit of AB Res.: The value range is 1000~4000, and the default value is 2000. When
the resistance between A and B is less than this value and not less than the middle limit of AB
resistance, we can judge user normal.

Lower limit of A (B) G Res.: The value range is 0.6~2, and the default value is 1. When the
resistance between A (B) and ground is less than this value, we can judge that A (B) wire
touches the ground.

Upper limit of A (B) G Res.: The value range is 5~10, and the default value is 10. When the
resistance between A(B) and ground is less than this value and not less than the lower limit of

15
ZXJ10V10.0 (V03.03Eu) Digital SPC Switching System User’s Manual (112 Liner Tester Console)

A(B)G resistance, we can judge bad insulation between A(B) wire and ground.

Lower limit of AB capacity: The value range is 0.4~0.8, and the default value is 0.4. When the
capacity between A and B is less than this value, we can judge the user is disconnected.

Upper limit of AB capacity: The value range is 2~8, and the default value is 6. When the
capacity between A and B is less than this value and not less than the lower limit of AB
capacity, we can judge the normal user; when the capacity between A and B is greater than
this value, we can judge that the user hooks off or the wires are mixed.

Fig. 4.2-27 Window of Modifying Critical Data of the Fault Judgment

 Click [System → Modify Password], and the window of modifying the administrator
password appears, as shown in Fig. 4.2 -28:

16
 Chapter 4 112 Acceptance and Test Desk

Fig. 4.2-28 Window of Modifying Administrator Password

 Click [System → Modify Serial Number], and the window of modifying the serial number
appears, as shown in Fig. 4.2 -29. The serial numbers of all the test records and complaint
records will be counted from the new serial number.

Fig. 4.2-29 Window of Modifying Serial Number

 Click [System → Remove Test Flag], and the dialog box about removing the current test flags
appears. After confirming it, all the current test flags in the records will be set as un-tested.

 Click [System → Delete Complaint and Test File], and the window of deleting the complaint
and test file appears, as shown in Fig. 4.2 -30. Click <OK> to delete the complaint and test
record of this serial number in the database.

17
ZXJ10V10.0 (V03.03Eu) Digital SPC Switching System User’s Manual (112 Liner Tester Console)

Fig. 4.2-30 Window of Deleting Complaint and Test File

 Click [System → Modify Normal Value], and the window of modifying normal value appears,
as shown in Fig. 4.2 -31. In the normal value list, select the normal value to be modified, to
modify its upper threshold and lower threshold values, and then click <OK>. A dialog box
will pop up, with “Thank you for using <Modify normal value>! You have modified the
system parameters, and all the modified parameters will be effective after the 112 subsystem
is restarted!”, indicating that all the modification will not be effective until 112 system
administrator, 112 acceptance and test desk and 112 routine test process are restarted.

Fig. 4.2-31 Window of Modifying Normal Value

 Click [System → Modify Office Code], and the window of modifying the office code appears,
as shown in Fig. 4.2 -32. Input old and new office codes, and then click <Modify> to replace
the old office code of the user number in the user card by the new office code.

18
 Chapter 4 112 Acceptance and Test Desk

Fig. 4.2-32 Window of Modifying Office Code

 Click [System → Auto print dispatch sheet settings], and the window of setting the auto print
of dispatch sheet appears, as shown in Fig. 4.2 -33. In it, we can set whether automatically
print the dispatch sheet of manual (automatic) test, whether the dispatch sheet of the manual
(automatic) test automatically printed concludes the test data, the copies of the dispatch sheet
of the manual (automatic) test, interval of scanning the un-printed dispatch sheet of the test
and whether automatically set the dispatch flag after the print is completed.

19
ZXJ10V10.0 (V03.03Eu) Digital SPC Switching System User’s Manual (112 Liner Tester Console)

Fig. 4.2-33 Window of Setting Automatic Print of Dispatch Sheet

4.2.2 Dispatch and Troubleshooting

1. Interface entry

Click <TestResult> in the function selection area, and the data display area and data command
area of the dispatch and troubleshooting will be displayed in the data area, as shown in Fig.
4.2 -34.

20
 Chapter 4 112 Acceptance and Test Desk

Fig. 4.2-34 Test Results

Click <Complaint & Accept> in the function selection area, and the data display area and data
command area of the compliant and acceptance will be displayed in the data area, as shown in
Fig. 4.2 -35.

21
ZXJ10V10.0 (V03.03Eu) Digital SPC Switching System User’s Manual (112 Liner Tester Console)

Fig. 4.2-35 Complaints and Acceptance Обзор принятых заявок.

2. Interface descriptions

1) In the data command area of the dispatch and troubleshooting, click <Query>, and the input
window of query conditions will appear, as shown in Fig. 4.2 -36. It is the input window of
universal query conditions, and “Field name” is the related filed name of the current data area,
“Operating symbol” contains equal, greater than, less than, not less than, not greater than, not
equal, not greater than and not less than. Click <OK> to display the records meeting the
conditions.

22
 Chapter 4 112 Acceptance and Test Desk

Fig. 4.2-36 Input Window to Universal Query Conditions

2) In the data command area of dispatch and troubleshooting, click <Dispatch and
Troubleshooting> to enter the interface of dispatch and troubleshooting, as shown in Fig. 4.2
-37. The data display area displays all the test result records. In it, the phone set with flag
indicates dispatched, and the one with red cross indicates un-dispatched.

 Click <Troubleshooting>, and the data display area will display the test result records of all
the phone sets which have been tested and the result is normal, and these phone sets are with
[OK], indicating the status of repaired.

 Click <Remove Repaired User> to delete the complaint and test record of the repaired phone
set. Before this operation, you should enter the troubleshooting status.

 Click <Set Dispatch Flag>, to set the phone set as the status of dispatched.

 Click <Remove Dispatch Flag>, to set the phone set as the status of un-dispatched.

 Click <Print Dispatch Sheet>, and the window of printing dispatch sheet will appear, as
shown in Fig. 4.2 -38. Before the printing, it is required to select one or multiple users in the
test results.

 Click <Browse Test Result> to return to the test result interface.

23
ZXJ10V10.0 (V03.03Eu) Digital SPC Switching System User’s Manual (112 Liner Tester Console)

Fig. 4.2-37 Interface of Dispatch and Troubleshooting

Fig. 4.2-38 Printing the Dispatch Sheet

3) In the data command area of dispatch and troubleshooting, click <Delete> to display the input
window of universal query conditions. Confirm it to delete all the records meeting the
conditions.

4) In the data command area of complaint and acceptance, click <Query> to display the input
window of universal query conditions. Confirm it to display all the records meeting the

24
 Chapter 4 112 Acceptance and Test Desk

conditions.

5) In the data command area of complaint and acceptance, click <Delete> to display the input
window of universal query conditions. Confirm it to delete all the records meeting the
conditions.

4.2.3 User Card Management

1. Interface entry

Click <UserCard> in the function selection area, and the data display area and data command
area of the user card will be displayed in the data area, as shown in Fig. 4.2 -39.

Fig. 4.2-39 User Card

2. Interface descriptions

1) Click <Add> to display the dialog box of adding a user card. In it, input the number of the
user card to be added, the system will save it and automatically enter the interface of editing
112 user card, as shown in Fig. 4.2 -40. After the editing, confirm it.

25
ZXJ10V10.0 (V03.03Eu) Digital SPC Switching System User’s Manual (112 Liner Tester Console)

Fig. 4.2-40 Interface of Editing 112 User Card

2) Click <Delete>, and the confirmation box of deleting user card will appear. Confirm it to
delete the selected 112 user card.

3) Click <Modify>, and the interface of editing 112 user card will appear. After the editing,
confirm it.

4) Click <Print> to print the selected 112 user card.

5) Click <Query> to display the input window of query conditions. Confirm it to delete all the
records meeting the conditions.

6) Click <Batch Print>, and the interface of batch print will appear. Select the user to be printed
and click <Print>.

26
 Chapter 4 112 Acceptance and Test Desk

Fig. 4.2-41 Batch Print

7) Click <Batch Del>, and the input window of query conditions will appear. Confirm it to
delete all the records meeting the conditions.

8) Click <Amount> to display the total amount of user cards in the data display area.

9) Click [UserCard → Clear user card], and the dialog box of clearing user card will appear.
Confirm it to clear all the data in the user card.

10) Click [UserCard → Synchronize user card], and the dialog box of synchronizing user card
will appear. Confirm it to synchronize the user card data from the switch data.

11) Click [UserCard → Backup user card], and the dialog box of backing up user card will
appear. Confirm it to backup the user card data to the text file.

12) Click [UserCard → Restore user card], and the dialog box of restoring user card will appear.
Confirm it to restore the user card data from the text file.

13) Select [UserCard → User card update converting], and the interface of converting user card
will appear, as shown in Fig. 4.2 -42. Confirm it, and a dialog box pops up. In it, select the
user card file for the upgrade converting.

27
ZXJ10V10.0 (V03.03Eu) Digital SPC Switching System User’s Manual (112 Liner Tester Console)

Fig. 4.2-42 Converting User Card

14) Click [UserCard → Append physical position] to append the physical position of the user card
from the switch database.

4.2.4 Routine Test Management Процедура управлением тестом.

1. Interface entry

Click <Routine Test Task> in the function selection area, and the data display area and data
command area of the routine test task will be displayed in the data area, as shown in Fig. 4.2
-43.

Fig. 4.2-43 Routine Test Task

28
 Chapter 4 112 Acceptance and Test Desk

Click <Routine Test Result> in the function selection area, and the data display area and data
command area of the routine test results will be displayed in the data area, as shown in Fig.
4.2 -44.

Fig. 4.2-44 Routine Test Results

1. Interface descriptions

1) Click <Register Routine Test Task > in the data command area of the routine test task, and the
interface of edit table of the routine test task will appear. In it, data display area and data
command area of the edit table of the routine test task will be displayed in the data area, as
shown in Fig. 4.2 -45.

 Click <Add>, and the window of adding a routine test task will appear, as shown in Fig. 4.2
-46. In it, input the start phone number, number of consecutive subscriber, routine test item,
start test time, total test numbers and start test period. Click <Confirm> to add the routine test
task. And click <Cancel> to close this window.

 Click <Delete>, and the dialog box of deleting the routine test task will appear. Confirm it to
delete the selected routine test task.

29
ZXJ10V10.0 (V03.03Eu) Digital SPC Switching System User’s Manual (112 Liner Tester Console)

 Click <Submit Routine Test> to submit the routine test task and return to the routine test task
interface.

 Click <Return without Submiting> to return to the routine test task interface without
submitting the routine test task.

Fig. 4.2-45 Edit Table of Routine Test Task

30
 Chapter 4 112 Acceptance and Test Desk

Fig. 4.2-46 Editing the Routine Test Registration

1) In the data command area of routine test task, click <Terminate Routine Test> to stop the
routine test task being executed.

2) In the data command area of routine test task, click <Test immediately>, and the input box of
immediate routine test task will appear, input the number to execute the routine test task with
the specified task number.

3) In the data command area of routine test results, click <Query>, and the input window of
universal query conditions will appear. Confirm it to display all the records meeting the
conditions.

4) In the data command area of routine test results, click <Delete log and Result>, and the input
window of universal query conditions will appear. Confirm it to delete all the records meeting
the conditions.

5) In the data command area of routine test results, click <Verify Routine Test log> to refresh the
data in the data display area of routine test results.

6) In the data command area of routine test results, click <Read Detailed Result>, and the fault
type selection window will appear, as shown in Fig. 4.2 -47. Select the fault type to be read in
detail, and enter the interface of detailed routine test result, as shown in Fig. 4.2 -48.

 Click <Query>, and the input window of universal query conditions will appear. Confirm it to
31
ZXJ10V10.0 (V03.03Eu) Digital SPC Switching System User’s Manual (112 Liner Tester Console)

display all the records meeting the conditions.

 Click <Verify the Routine Test Result> to refresh the data in the data display area of detailed
routine test results.

 Click <Return> to return to the routine test result interface.

 Click <Print> to print the data of the detailed routine test result.

Fig. 4.2-47 Fault Type Selection

32
 Chapter 4 112 Acceptance and Test Desk

Fig. 4.2-48 Reading Detailed Routine Test Results

4.2.5 Test Desk Configuration

1. Interface entry

Click <Desk Configure> in the function selection area, and the password input box will
appear, as shown in Fig. 4.2 -49. Input the system administrator password, and then the data
display area and data command area of the test desk configuration will be displayed in the
data area, as shown in Fig. 4.2 -50.

Fig. 4.2-49 Password Input Box

33
ZXJ10V10.0 (V03.03Eu) Digital SPC Switching System User’s Manual (112 Liner Tester Console)

Fig. 4.2-50 Test Desk Configuration

2. Interface descriptions

1) Click [Add], and the interface of adding the operator of acceptance and test desk will appear,
as shown in Fig. 4.2 -51. Input the operator number and password, and then click <OK>.

Fig. 4.2-51 Adding Operator of the Acceptance and Test Desk

2) Click <Delete>, and the dialog box of deleting the operator of the acceptance and test desk

34
 Chapter 4 112 Acceptance and Test Desk

will appear. Confirm it to delete the selected operator of the acceptance and test desk.

35
5 112 Common Interfaces

5.1 Overview
With the development of the telecommunication industry and the increase in user
requirements, more and more users require the switch manufacturers to provide the 112
centralized test interface. To meet the requirements of the telecommunication
departments for the centralized test of the ZXJ10 switch, ZTE has developed the 112
centralized test interface program of the ZXJ10 version under the Windows
2000/Windows NT platform.

5.2 Operating Environment

5.2.1 Usage Mode Выбор загрузки.

The ZXJ10 version 112 common interface program is installed on the ZXJ10 client. It
works in three modes:

1. It is connected to the external 112 test platforms of other manufacturers via

serial port.

2. With the network cable, it communicates with external 112 test platforms of
other manufacturers via telnet.

3. 112 test platforms of other producers are connected to the ZXJ10 client, which
runs 112 common interface program. And with winnttcp between the
backgrounds, net112 communicates with 112 interface program.

Notes:

1. The 112 common interface program can work in only one mode at a time;
otherwise confusion will occur.

2. The installation file of 112 common interface program is:

VERSION\N112INST\DISK1\SETUP.EXE. The default directory for
installation is: c:\program files\zte\inter112\*.*.

3. 112 common interface program has two program files: inter112.exe and
net112.exe. For a centralized test, run inter112.exe.For an emulation test, run

1
 inter112.exe and net112.exe.A schematic diagram of emulation test connection
is shown in Fig. 5.2 -52.

4. 112 common interface program can run on multiple clients, and a client can run
one 112 common interface program only.

5. 112 common interface program and 112 acceptance and test desk can run
simultaneously.

6. 112 common interface program and the TSERVER can run simultaneously on
the same terminal.

Serial port or Client

External 112 test platform of TELNET (run the unified interface
other manufactures program)

Serial port or TELNET TCP/IP

Client
Background 129 server
(run inter112.exe and net112.exe）
TCP/IP
TCP/IP

ZXJ10 switch

Fig. 5.2-52 Schematic Diagram of Running Environment of a Emulation Test

5.2.2 Function Descriptions

112 common interface program can provide services externally in a centralized mode
or an emulation mode.

The so-called centralized mode refers to such a mode that test hardware is provided by
another manufacturer and is connected to the backplane of the ZXJ10 user layer. It
issues to the 112 common interface program a connection command, to get the right to
occupy a test line. After the use, the occupancy right is released through a
disconnection command. The program inter112.exe is required to run on the client.

The so-called emulation mode refers to such mode that no test hardware is provided by
any other manufacturer, and no hardware connection is needed, while only the ZXJ10
self-contained test card will be used for a test. The related data obtained from the
ZXJ10 test will be transferred to net112.exe, and further transferred to other

2
 Chapter 5 112 Common Interfaces

manufacturers, which will be responsible for the analysis of these data and give out a
conclusion. The programs inter112.exe and net112.exe are required to run on the client.

5.3 Hardware Connection during Centralized Test

Since the test heads of the centralized 112 test system by manufacturers are expensive,
and there are few test heads in the test systems bought by carriers, so such a test mode
is generally used at present, by which centralized tests are performed to the minor part
of users and emulation tests are performed to a major part of users, for the deployment
of centralized 112 test system engineering. As a result, there are not many test lines that
should be interconnected for a centralized test. Considering the convenience of
deployment and simplicity of maintenance, it is recommended that test heads are
directly connected to the user backplane in interconnecting the test lines.

The ZXJ10V10.0 connection is shown in Fig. 5.3 -53.

3 4 23 24 25 26
ASLC ASLC MTT MTT SPI SPI

Test bus 1
Test
interface 1

Test bus 2 Test

interface 2

ASLC ASLC MTT MTT SP SP

Test bus 1
Soft
line 1

Test bus 2
Soft
line 2

Fig. 5.3-53 Position of the Test Interfaces and Test Bus on the User Unit Backplane

The test head of general centralized test equipment can be pulled quite long, and its
four test lines (Internal test A-line TIA, internal test B-line TIB, external test A-line
TOA and external test B-line TOB) are led out in the form of probes, and can be
arranged at random. Each user unit of the ZXJ10V10.0 also provides test ports, and
each test port corresponds to a group of test bus, which contains four test lines

3
ZXJ10V10.0 (V03.03Eu) Digital SPC Switching System User’s Manual (112 Liner Tester Console)

altogether (TIA, TIB, TOA and TOB). Connect these four lines correspondingly to the
four lines of the test head. The positions of the test ports and test bus on the user unit
backplane are shown in Fig. 5.3 -53.

We can see from Fig. 5.3 -53 that there are two layers of users in each user unit. Each
layer of users can be divided into upper-half layer and lower-half layer according to the
test bus, occupying test buses 1 and 2 respectively. So, a user unit is externally
symbolized as two test ports, and a centralized 112 test system should provide 2 test
heads to be connected with this unit.

When connecting the test heads of 112 test system and the backplane, it is
recommended to connect the 2 test heads to test port 1 and test port 2 of slot 24 on the
upper-half layer of the user unit. The distribution of the four test lines of test port 1 and
test port 2 is shown in Table 5.3 -1.

Table 5.3-1 Distribution of Test Lines of Test Ports

Test Signal Test Port 1 Test Port 2

TIA 14A 19A

TIB 14C 19C

TOA 13A 20A

TOB 13C 20C

Connections of the ZXJ10V4.X are described as follows:

The external test bus of the ZXJ10V4.X can be led out from the backplane of the
switch test board, or from the backplane of the user board. The detailed connection
method is shown in Fig. 5.3 -54 and Fig. 5.3 -55. Four groups of external test buses
can be led out from one user module, and no interconnection between the external test
buses is permitted, otherwise the test result may be affected. A bus can cover 800~900
users.

4
 Chapter 5 112 Common Interfaces

11C 11A 11C:TOA0 11A:TIA0

12C:TOB0 12A:TIB0
12C 12A

13C 13A 13A:TIA1

13C:TOA1
14C 14A 14C:TOB1 14A:TIB1

15C 15A 15C:TOA2 15C:TIA2

16C:TOB2 16C:TIB2
16C 16A

17C 17A 17C:TIA3

17C:TOA3
18C 18A 18C:TOB3 18C:TIB3

Fig. 5.3-54 Backplane of the Switch Test Board

7C:TOA0
7C 7A
7A:TIB0

8C:TOB
8C 8A
8A:TIB
TO TI

Fig. 5.3-55 Backplane of the User Board

TOA, TOB, TIA and TIB of the user layer are connected with the test pins (TOAx,
TOBx, TIAx and TIBx) corresponding to the groups (0~3) where they are located. If
several layers belong to the same test group, you should connect them to the
corresponding TOA, TOA, TIA and TIB. Users on the same layer have been connected
already.

5
ZXJ10V10.0 (V03.03Eu) Digital SPC Switching System User’s Manual (112 Liner Tester Console)

5.4 Command Interface

5.4.1 Centralized Test Command

112 common interface of the ZXJ10 version has two input commands, whose formats
have inherited the connection command and disconnection command in the ZXJ10
V4.X version. The letter-form command is TEST_RELAY_ON/1122 and numeral-
form command is TEST_RELAY_OFF/1123.

In the ZXJ10 switch receiving 112 test center, "$%" is used as the start delimiter for
strings, and "\r" is used as the end delimiter; likewise, in the ZXJ10 switch, "$%" is
also used as start delimiter for the return strings, and "\r" is used as the end delimiter.

For example:

The connection command is: $%TEST_RELAY_ON:1=UserPhoneNum; \r.

The delimiter will be omitted hereinafter for convenience.

The connection command is: TEST_RELAY_ON:1=UserPhoneNum; or 1122:1=

UserPhoneNum;

The disconnection command is: TEST_RELAY_OFF:1=UserPhoneNum; or 1123:1=

UserPm;

The user type command is: TEST_TYPE:1=UserPhoneNum; or 1112:1=

UserPhoneNum;

Descriptions:

1. A disconnection command must be used after using a connection command;

2. A connection command must be used before using a disconnection command;

3. A semicolon must be used to end a command.

5.4.2 Emulation Test Command

Before using an emulation test, net112.exe should be run first.

The assigning user test command (emulated user seizure): ASSIGN_SDN:1 =

UserPhoneNum;

or 1108:1 = UserPhoneNum;

The test user circuit command (emulation internal test): TEST_INSIDE; or 1109;

6
 Chapter 5 112 Common Interfaces

The test user line electrical performance command (emulation external test):
TEST_OUTSIDE:1=Scope;

Or 1110:1=Scope;

For forced test: TEST_OUTSIDE:1=Scope;2=0;

or TEST_OUTSIDE:2=Scope;

or 1110:1=Scope;2=0;

or 1110:2=Scope;

(Scope: The value is 0~8, 0- All, 2- Resistance, 3- Voltage, 1, 4, 6, 8-N/A, 5-

Capacitance, 7- ground resistance).

The exit user line test command (emulation exit): EXIT_TEST; or 1114;

In the above commands, UserPhoneNum is the user phone number to be tested by the
test center.

An ASCII-format semicolon must be used to end a command, and commands are also
punctuation-sensitive in the middle, so the punctuation in the above commands should
be used with care.

5.4.3 Output Format

112 common interface program of the ZXJ10 version features two output formats:
Chinese character output format and ASCII code output format. Only the Chinese
character output format is available for emulation command output method.

5.4.3.1 Chinese Character Output Format

Because the interpretation results returned by man-machine command are Chinese

character strings, this output mode is the default output mode. The ASCII structure
mentioned above is a result forcedly converted through the interface program.

The structure of Chinese character string return mode of disconnection or connection

command is shown as follows:

An instance of connection command return:

Command is checked correctly.

Serial No.:000057 No.: 1122 Code: TEST_RELAY_ON

Date: Sep 5th, 2003 Time: 15:18:27

7
ZXJ10V10.0 (V03.03Eu) Digital SPC Switching System User’s Manual (112 Liner Tester Console)

=======MML output========

User phone number = 34560096

User equipment number=3-2-5-0

Test group number=31

User module number=3

Serial No.:000057 No.: 1122 Code: TEST_RELAY_ON

Date: Sep 5th, 2003 Time: 15:18:27

=======MML output========

User status=Idle

Command execution is completed

An instance of disconnection command return:

Command is checked correctly.

Command is executed correctly.

Command execution is completed

An instance of user type command return:

MML>1112:1=21580010;

Serial No.:000592 No.: 1112 Code: TEST_TYPE

Date: Sep 16th, 2003 Time: 14:28:36

User phone number = 21580010

=======MML output========

User type: PSTN user.

Command execution is completed

MML>TEST_TYPE:1=21580020;

Serial No.:0005926 No.: 1112 Code: TEST_TYPE

Date:Sep 16th, 2003 Time: 14:44:15

User phone number = 21580010

8
 Chapter 5 112 Common Interfaces

=======MML output========

User type: ISDN user

Command execution is completed

An instance of emulation capturing user command return:

MML>1108:1=34560096;

Serial No.: 000058 No.: 1108 Code: ASSIGN_SDN

Date: Sep 5th, 2009 Time: 15:20:43

=======MML output========

User number =34560096

User equipment number =1-1-7-0

Serial No.: 000058 No.: 1108 Code: ASSIGN_SDN

Date: Sep 5th, 2003 Time: 15:20:43

=======MML output========

User status=Idle

Command execution is completed

Instance of emulation internal test command return:

MML>1109;

Serial No.:00059 No.: 1109 Code: TEST_INSIDE

Date: Sep 5th, 2003 Time: 15:21:18

=======MML output========

Tested user=34560096

Internal test result =No dial tone after hookoff

Command execution is completed

An instance of emulation external test command return:

MML>1110:1=0;

Command is checked correctly!

Serial No.:000064 No.: 1110 Code: TEST_OUTSIDE

9
ZXJ10V10.0 (V03.03Eu) Digital SPC Switching System User’s Manual (112 Liner Tester Console)

Date: Sep 5th, 2003 Time: 15:22:15

=======MML output========

A-line DC voltage (V) = 0.0018

A-line AC voltage (V) = 0.0055

B-line DC voltage (V) = 0.0021

B-line AC voltage (V) = 0.0082

A-B DC voltage (V) =0.0011

A-B AC voltage (V) = 0.0039

Serial No.:000060 No.: 1110 Code: TEST_OUTSIDE

Date: Sep 5th, 2003 Time: 15:22:15

=======MML output========

A-ground capacitance (microfarads) = 0.0000

B-ground capacitance (microfarads) = 0.0000

A-B capacitance (microfarads) = 0.0000

Serial No.:000060 No.: 1110 Code: TEST_OUTSIDE

Date: Sep 5th, 2003 Time: 15:22:15

=======MML output========

A-ground resistance (kilo-ohms) =10000.0000

B-ground resistance (kilo-ohms) =10000.0000

A-B resistance (kilo-ohms ) = 10000.0000

Command execution is completed

MML>1110:1=0;2=0;

Command is checked correctly!

Serial No.:000064 No.: 1110 Code: TEST_OUTSIDE

Date: Sep 5th, 2003 Time: 15:39:14

=======MML output========

A-line DC voltage (V) = 0.0002

10
 Chapter 5 112 Common Interfaces

A-line AC voltage (V) = 0.0057

B-line DC voltage (V) = 0.0003

B-line AC voltage (V) = 0.0090

A-B DC voltage (V) =0.0004

A-B AC voltage (V) = 0.0043

Serial No.:000062 No.: 1110 Code: TEST_OUTSIDE

Date: Sep 5th, 2003 Time: 15:37:45

=======MML output========

A-ground capacitance (microfarads) = 0.0000

B-ground capacitance (microfarads) = 0.0000

A-B capacitance (microfarads) = 0.0000

Serial No.:000062 No.: 1110 Code: TEST_OUTSIDE

Date: Sep 5th, 2003 Time: 15:37:45

=======MML output========

A-ground resistance (kilo-ohms) =10000.0000

B-ground resistance (kilo-ohms) =10000.0000

A-B resistance (kilo-ohms ) = 10000.0000

Command execution is completed

MML>1110:1=2;

Command is checked correctly!

Serial No.:000064 No.: 1110 Code: TEST_OUTSIDE

Date: Sep 5th, 2003 Time: 15:39:14

=======MML output========

A-ground resistance (kilo-ohms) =10000.0000

B-ground resistance (kilo-ohms) =10000.0000

A-B resistance (kilo-ohms ) = 10000.0000

Command execution is completed

11
ZXJ10V10.0 (V03.03Eu) Digital SPC Switching System User’s Manual (112 Liner Tester Console)

MML>1110:1=3;

Command is checked correctly!

Serial No.:000065 No.: 1110 Code: TEST_OUTSIDE

Date: Sep 5th, 2003 Time: 15:39:50

=======MML output========

A-line DC voltage (V) = 0.0020

A-line AC voltage (V) = 0.0055

B-line DC voltage (V) = 0.0025

B-line AC voltage (V) = 0.0083

A-B DC voltage (V) =0.0017

A-B AC voltage (V) = 0.0037

MML>1110:1=5;

Command is checked correctly!

Serial No.:000067 No.: 1110 Code: TEST_OUTSIDE

Date: Sept 5th, 2003 Time: 15:40:53.

=======MML output========

A-ground capacitance (microfarads) = 0.0000

B-ground capacitance (microfarads) = 0.0000

A-B capacitance (microfarads) = 0.0000

Command execution is completed

MML>1110:1=7;

Command is checked correctly!

Serial No.:000069 No.: 1110 Code: TEST_OUTSIDE

Date: Sept 5th, 2003 Time: 15:41:56

=======MML output========

A-ground resistance (kilo-ohms) =10000.0000

B-ground resistance (kilo-ohms) =10000.0000

12
 Chapter 5 112 Common Interfaces

Command execution is completed

MML>1110:1=8;

Command is checked correctly!

Test of this parameter is not supported at present.

An instance of emulation exit command return:

MML>1114;

Command is checked correctly.

Command is executed correctly.

Command execution is completed

5.4.3.2 ASCII Code Output Format

In the ZXJ10 switch receiving 112 test center, "$%" is used as the start delimiter for
strings, and "\r" is used as the end delimiter; likewise, in the ZXJ10 switch, "$%" is
also used as start delimiter for the return strings, and "\r" is used as the end delimiter.
The middle part is the return result of the command check or execution. The return
string format is as follows:

STRUCT

char Stmark [2]; // start delimiter

char ExtStatus; // command execution status

char usernumber[40]; // user telephone number

char socketnum[11]; // user equipment number

char groupnum[3]; // test group number

char modelnum[2]; // user module number

char RetStatus[3]; // execution result code or user status

char Endmark[2]; // end delimiter

The return format is the same to all the external test commands.The middle part of the
commands with no return result is vacant.

13
ZXJ10V10.0 (V03.03Eu) Digital SPC Switching System User’s Manual (112 Liner Tester Console)

ExtStatus RetStaus Cause

0 00 Command check error

0 01 No such a command

0 02 Error of parameters contained in the command

0 03 The switch version does not support this command

0 04 The test command is not consistent with the test mode

0 05 Non-super user cannot send non-test commands

1 00 Connection succeeded

1 99 Release succeeded

1 01 (Other commands) executed successfully

1 02 PSTN user (user type test)

1 03 ISDN user (user type test)

2 00 Error of input user number

2 01 Internal execution error

2 02 User has been blocked

2 03 Error of input test card parameter

2 04 Test card does not exit

2 05 Press <Release> before acceptance

2 06 No complaint user queue

2 07 Exit the previous user test

2 08 Operation error, no test object

2 09 Emulation test is busy, please try later

2 10 Test results are abnormal

2 11 Pulse number receiving results are abnormal

2 12 Error of input number of routine tests

2 13 No test unit

2 14 No test card is available, and current test failed

14
 Chapter 5 112 Common Interfaces

2 15 The tested user is busy, please try later

2 16 Test desk hooked on, the current test exited safely

2 17 Test line is busy

2 18 Please hook off before test

2 19 Blocking failed

2 20 Call is blocked

2 21 User dialing timeout, number receiving test is

automatically terminated

2 22 User hookoff timeout, ringing test is automatically

terminated

2 23 User hookon timeout, howler tone is automatically

terminated

2 24 The user is not testable

2 25 The test card has not been installed

2 26 Command is timeout

2 27 Failed to send message

5.5 Installation and Running of 112 Common Interface Program

First, install 112 common interface program, and then directly run SETUP.EXE.112
interface program file name is inter112.EXE, and its configuration files are
B112INT.INI and B112SERI.INI. And B112INT.INI is the own configuration file of
the common interface program, it contains the configurations of output mode, user
source and writing log or not. B112SERI.INI is the configurations of serial port
parameters of the common interface, it contains such parameters as baud rate, data bit
and serial communication control parameter. The configuration files are under the
directory WINNT. If an emulation test is to be started, the file B112INT.INI should be
edited, and input correct number of the standard OPR of 112 special service group (not
a pilot number).

After installing the interface program, log in the background maintenance system.
Click [Start → Program → Inter112 → Inter112] to start the interface program, and the
login interface shown in Fig. 5.5 -56 will appear. Input the user name and password
15
ZXJ10V10.0 (V03.03Eu) Digital SPC Switching System User’s Manual (112 Liner Tester Console)

(initial user name is netman and the initial password is zxnetman).

Fig. 5.5-56 Login Interface

After successful login, enter the main interface (Fig. 5.5 -57).

Fig. 5.5-57 Common Interface Program Interface

In the main interface shown in Fig. 5.5 -57, select [Password Management], and the
interface shown in Fig. 5.5 -56 will appear, for selecting the password.

In the main interface (Fig. 5.5 -57), click [Output Mode Settings] to enter the interface
shown in Fig. 5.5 -58.

16
 Chapter 5 112 Common Interfaces

Fig. 5.5-58 Selecting User Source and Output Mode

Generally, if "Over Remote Agent" is selected, it indicates that the system is connected
with a tester of another manufacturer through telnet or a serial port.

If the system is not connected to 112 interface of another manufacturer temporarily, but
is used in net112 for local user test instead, select "Local" as the user source.

Two output modes can be set in the “Output Mode”. See sections 5.4.3.1 and 5.4.3.2
for details.

"Fix Test Group” indicates that the test group number in the connection results is fixed.

If an emulation test is to be enabled, it is required to select “Emulation Test" and input

the standard OPR number set in 112 special service group, and the user card
corresponding to this number should be normal.

"Command Timeout" indicates that how long after INTER112 sending a message is set
as timeout.

"Standard Opr Number" indicates a standard OPR number configured for 112.

For the requirement of debugging, "Write Log File" can be selected, so that the net112
system will store the received commands, which can be queried by clicking the [Log
Viewer] menu or <Log Viewer> in the interface shown in Fig. 5.5 -57 (see Fig. 5.5
-59).

17
ZXJ10V10.0 (V03.03Eu) Digital SPC Switching System User’s Manual (112 Liner Tester Console)

Fig. 5.5-59 Log Query Window

In the main interface shown in Fig. 5.5 -57, click <Communication Option>, an
interface shown in Fig. 5.5 -60 will pop up. In it, you can make some modification for
the communication parameters.

Select the [Port Selection] tab to set "1st line" as a local actually connected serial port.
Ignore those that are not used.

18
 Chapter 5 112 Common Interfaces

Fig. 5.5-60 Port Selection Interface

In the [Terminal Settings] tab (see Fig. 5.5 -61), modify the Telnet port number being
used, and the numbers at two ends should be the same. For "Terminal Type" and
"Sending", the default values are usually used. If changed, they should be the same as
the peer end.

Fig. 5.5-61 Terminal Settings

In the "COM Settings" tab (See Fig. 5.5 -62), you can set serial port parameters, flow
control, DTR status and RTS status. Communication parameters should be set the same
as the hardware settings, otherwise, the connection may fail.

19
ZXJ10V10.0 (V03.03Eu) Digital SPC Switching System User’s Manual (112 Liner Tester Console)

Fig. 5.5-62 Communication Parameter Settings

In this tab, click [Connection Mode], the interface shown in Fig. 5.5 -63 will appear,
used for selecting the actual connection mode.

Fig. 5.5-63 Connection Mode Selection

5.6 Configuration Modes

5.6.1 Serial Port Configuration Mode

Set the serial port in these steps:

1. Close 112 common interface program, start the hyper terminal and make sure

20
 Chapter 5 112 Common Interfaces

that it can correctly receive commands issued from the peer end.

2. Record the related settings in the hyper terminal: COM port, baud rate, data bit,
stop bit, check bit and flow control.

3. Close the hyper terminal, and start 112 common interface program ([Start →
Program → Inter112 → Inter112), as shown in Fig. 5.5 -57.Click [COM
Settings] (see Fig. 5.5 -62). In [Port Selection], set the first corresponding port
as a port used by the hyper terminal. The related parameters in [COM Settings]
should be set in consistency with the hyper terminal.

4. In the interface of selecting output mode (See Fig. 5.5 -58), set “Over Remote
Agent” for the user source, “String Output” as the output mode, and check
"Write Log File", and then restart 112 common interface program.

5. In the interface of viewing the log (See Fig. 5.5 -59), check whether the test
commands sent from the peer end can be received. If commands sent from the
peer end can be received, it indicates the serial port has been correctly set.

6. If the commands received are different from those sent from the peer end, or no
command can be received at all, the communication parameters in 112 common
interface program should be adjusted until they are correct.

7. If it still does not work, replace a serial port and repeat Steps 1 to 5.

5.6.2 Telnet Configuration Mode

Set telnet mode in the following steps:

1. Open the control panel and open ODBC settings. Click <Add>, and then a
window of adding new data source will appear. In it, select “Microsoft dbase
driver (*.dbf) and click <OK>, the [ODBS dBASE Setup] window will appear,
as shown in Fig. 5.6 -64.

21
ZXJ10V10.0 (V03.03Eu) Digital SPC Switching System User’s Manual (112 Liner Tester Console)

Fig. 5.6-64 Setting ODBC

1) [Data Source Name]: telsvrb

2) Do not select [Use Current Directory]

3) [Directory]: c:\Program Files\zte\inter112\Dbf

2. Start 112 common and select [Communication Options → Terminal Settings]

(see Fig. 5.5 -61), change “Telnet Port Number” as 7777 (or other port
numbers). .

3. In the interface of viewing logs (see Fig. 5.5 -59), check whether there is
prompt of “Telnet function can not be used”, if no, it indicates that the telnet
works normally.

4. You can start the program telnet.exe locally to test if the telnet mode works
normally. Click [Start → Programs → Accessories → Telnet], and select
[Connect → Remote System]. An interface shown in Fig. 5.6 -65 will pop up.

Fig. 5.6-65 Telnet Connection

Input the local equipment name in “Host Name” and the port number just set in

22
 Chapter 5 112 Common Interfaces

“Port”, and then click <Connect>.

5. If the connection succeeds, enter the login user name and password, which are
both "aa".

5.7 112 Test for the Unified Interface Program

5.7.1 System Overview

The wide availability of switches requires a great deal of services with external
interfaces, such as immediate charging, suspension, activation, 112 centralized
acceptance test and man-machine command. When interconnecting with the systems of
different manufactures, even the same service has different requirements for
communication modes (such as RS232 and TCP/IP) and message format. So, this
system offers centralized management for the external interfaces of the switch, that is,
these services will be provided in a unified manner by one interface. An interface
machine program is to be placed in front of the service software that is to provide
external services, an internal protocol is adopted between the service software and the
interface machine, and communications will be performed by means of a standard
WINNTTCP.EXE program of switch. This interface machine program can run on both
server and terminal. It not only can run on the same machine with the service program,
but also can run in a machine independently, as a result, it can be extended through U
card (runs on the client). It transfers and converts messages. It has the following
characteristics:

1. Its external communication modes can be flexibly selected, such as RS232 and
SOCKET.

2. It is easy to add a communication mode, and the communication parameters can

be set flexibly.

3. The message formats can be flexibly converted in an open mode.

4. Tracing, emulation (internally and externally) and statistics can be performed for
forwarded messages.

5. It can simultaneously provide external interfaces to multiple service programs

respectively and provide multiple interfaces to a service program.

Taking the extensibility into full consideration, the interface program is divided into
several tasks. The number of tasks can be configured flexibly, and so can the service

23
ZXJ10V10.0 (V03.03Eu) Digital SPC Switching System User’s Manual (112 Liner Tester Console)

type of each task, module number of the service program, external interface mode and
parameters. A schematic diagram of the interface structure is shown in Fig. 5.7 -66.

Immediate charging
terminal
Message
Man-machine COM1
command conversion

112 .
Message
. COM2
conversion
. Task
...
Communicate Message
TCP/IP
conversion
through
WINNTTCP . . .
. . .
. . .

Fig. 5.7-66 Interface Machine Structure Diagram

5.7.2 Unified Interface Configuration

The unified interface configuration program is a support program of the unified

interface execution program, and it is used to create a configuration file to be invoked
by the execution program. The configuration file records the configuration information
of the communication channels, and the corresponding relations among tasks. In the
running process, the execution program will generate the corresponding receiving and
sending objects according to the configurations, to implement the data transfer between
internal services and external ports. An introduction to the configuration and
implementation of the unified interface 112 test is given below.

For a centralized test mode, it is required to run the inter112.exe program and the
unified interface program.

For an emulation test mode, it is required to run the inter112.exe, net112.exe and the
unified interface programs.

5.7.3 Entering Unified Interface Settings

Click [Start → Programs → ZTE Interface Application → ZTE Uni-Interface

Configure Guide] to execute the execution configuration creation guide. If it is the first
time to run the program on the local computer, a window shown in Fig. 5.7 -67 will
appear.

24
 Chapter 5 112 Common Interfaces

Fig. 5.7-67 Welcome Interface of Unified Interface Configuration File Creation Guide

Click <Next>to enter the window of selecting interface service, as shown in Fig. 5.7-3.

5.7.4 Selecting Interface Services

The window of selecting interface services is shown in Fig. 5.7 -68.

25
ZXJ10V10.0 (V03.03Eu) Digital SPC Switching System User’s Manual (112 Liner Tester Console)

Fig. 5.7-68 Selecting Interface Services

In the window shown in Fig. 5.7 -68, determine the number of the external interfaces
and the communication mode of the external interfaces (COM or TCP/IP), and then
click <Next> to enter the specific configuration of services and communication. The
configuration is performed in the tree map mode.

5.7.5 Service and Communication Configuration

5.7.5.1 Adopting Serial Port Mode

1. Service configuration

Click "Line Tester" of the first line in the tree configuration map, and then 112
test service configuration will be displayed on the right side. “Operation
ModuleNo” and “Operation BureauNo” are the location identifications of
service program, for example, if the bureau number of the PC containing the
service program man-machine command and interface program is 1, and the
related node number is 135, you should input 135 in “Operation ModuleNo”, 1
in “Operation BureauNo”, 135 in “Interface ModuleNo” and 1 in "Interface
BureauNo". Input these numeral in the corresponding position, the service
configuration is completed. Select “Yes” for "Trans-Flag in Recv" and "Yes" for
"Trans-Flag in Send", and select “Copy112.dll” in the pull-down box of “Trans-
Dll Name”, as shown in Fig. 5.7 -69.

26
 Chapter 5 112 Common Interfaces

Fig. 5.7-69 Configuring Services of 112 Test External Serial Port

2. Communication configuration

Click "Line Tester Output setting through COM1” of the second line in the tree
configuration map, and then 112 test communications setting is displayed on the
right. These settings are general settings of the serial port communication. It is
to be noted that "ComRecv BeginChar" is the begin identifier for the interface
program receiving data from the serial port. It can either be one character or
multiple characters, and can also be vacant."ComRecv EndChar" is the end
identifier for the interface program receiving data from the serial port. It can
either be one character or multiple characters, but should not be vacant. If the
end character is a special one, please click the small button on the right to select
a special end character. Select “Yes” for "Trans-Flag in Recv" and "Yes" for
"Trans-Flag in Send", and select “Com112.dll” in the pull-down box of “Trans-
Dll Name”.

27
ZXJ10V10.0 (V03.03Eu) Digital SPC Switching System User’s Manual (112 Liner Tester Console)

Fig. 5.7-70 Setting 112 Test External Serial Port Communication

5.7.5.2 Adopting TCP/IP Mode

If TCP/IP mode is selected for the interface service, the configuration window will be
as shown in Fig. 5.7 -71.

1. Service configuration

Click "Line Tester" of the first line in the tree configuration map, and then 112
test service configuration will be displayed on the right side. “Operation
ModuleNo” and “Operation BureauNo” are the location identifications of
service program, For example, if the bureau number of the PC containing the
service program man-machine command and interface program is 1, and the
related node number is 135, you should input 135 in “Operation ModuleNo”, 1
in “Operation BureauNo”, 135 in “Interface ModuleNo” and 1 in "Interface
BureauNo". Select “Yes” for "Trans-Flag in Recv" and "Yes" for "Trans-Flag in
Send", and select “Copy112.dll” in the pull-down box of “Trans-Dll Name”.

28
 Chapter 5 112 Common Interfaces

Fig. 5.7-71 Configuring 112 Test External TCP/IP Services

2. Communication configuration

Click "Line Tester Output setting through SOCKET” of the second line in the
tree configuration map, and then 112 test communications configuration is
displayed on the right. As the unified interface program is a SOCKET server to
monitor the connection from the client, so a port number should be designated in
"SOCKET Server PortNo". It is to be noted that when there are multiple
TCP/IPs in the configuration, a different SOCKET port number should be
designated for the configuration of each TCP/IP, and the port number should be
consistent with the peer end through negotiation. Select “Yes” for "Trans-Flag in
Recv" and "Yes" for "Trans-Flag in Send", and select “Sock112.dll” in the pull-
down box of “Trans-Dll Name”.

29
ZXJ10V10.0 (V03.03Eu) Digital SPC Switching System User’s Manual (112 Liner Tester Console)

Fig. 5.7-72 Configuring 112 Test External TCP/IP Communication

After configuring the service and communication, click <Next>, and then a prompt
window will pop up, as shown in Fig. 5.7 -73.

Fig. 5.7-73 Prompt Window

Click <OK> to enter the completion window shown in Fig. 5.7 -74 Click <Cancel> to
stay in the window of configuring service and communication.

5.7.6 Completing the Configuration

The configuration completion window is shown in Fig. 5.7 -74. This window displays
the name and location of the configuration file. Click <End> to complete the creation
of configuration file. The configuration file name is ZxCfg.ini. You can select to read
the note file for interface or not. If "Read the note file for Interface" is selected, a text

30
 Chapter 5 112 Common Interfaces

file of instructions of the unified interface program and configuration file will pop up.

Fig. 5.7-74 Completion Window

5.7.7 Re-Configuring

If the configuration file has already been created and [ZTE Uni-Interface Configuration
Program] is running, a prompt window will appear, as shown in Fig. 5.7 -75.

Fig. 5.7-75 Prompt of Existed Configuration File

If resetting is required, click <Reset> to enter the normal setting window and return to

31
ZXJ10V10.0 (V03.03Eu) Digital SPC Switching System User’s Manual (112 Liner Tester Console)

the above-mentioned setting process. If checking and modifying the previous

configurations are only required, click <Browse> to enter the window shown in Fig.
5.7 -76.Based on the previous configurations, you can modify the communication
parameters. Click <Accept> to save the modification.

Fig. 5.7-76 Interface of Checking Configurations

5.7.8 Executing the Unified Interface Program

Two preconditions are required for running the unified interface program: Configuring
the file correctly and the running process c:\zxj10\Winnttcp.exe. After the above two
preconditions are satisfied, you can run the unified interface execution program
normally. The unified interface execution program serves as the communication bridge
between different service program and external ports.

After the program runs, the window shown in Fig. 5.7 -77 will appear.

32
 Chapter 5 112 Common Interfaces

Fig. 5.7-77 Running Window of Unified Interface Program

Trace messages in different time areas of message processing through selecting

“RecMsgBefTrans”, “RecMsgAftTrans”, ”SndMsgBefTrans” or “SndMsgAftTrans”.

You can check “Write Debug-Tracing” to write the file into the hard disk.

Or click <Clear> to clear messages on the interface.

When there are data being transmitted in the interface program, the related debugging
information will appear in the information box below. It is to be noted that when "Write
Debug-Tracing" is checked, the data received and sent by the interface will be recorded
into the text file Debug.txt in the form of code stream. This file is used to locate errors.
When everything is normal, this option is generally not required.

Another tab [Error Notice] of the window is used to display some prompts of errors, to
help you to locate errors during running through viewing these prompts.

33
ZXJ10V10.0 (V03.03Eu) Digital SPC Switching System User’s Manual (112 Liner Tester Console)

5.7.9 Input and Output of Unified Interface Program 112 Test

5.7.9.1 Format Conventions

The command message format is used for the data transmission between 112 test
execution program and the unified interface.

The command message and command response format is used for the data transmission
between the unified interface and the external ports.

Since the unified interface can provide multiple services, corresponding conventions
are used for four data structures: command message, data message, command response
and data response, to standardize the data transmission between the service program
and the unified interface. These four structures are described in Table 5.7 -2 ~ Table
5.7 -5.

The unified structure of command messages is shown in Table 5.7 -2.

Table 5.7-2 Structure Table of Command Messages

Data Type Abbreviations Description

Message type: 1 for data message; 2 for command message;
BYTE MsgType
3 for data response; 4 for command response
BYTE Version Version number
BYTE HeadLen Message head length
DWORD SerialNo Serial number
Terminal ID, used to designate a task in the unified interface
BYTE TerminalID
program
LEN Len Message body length
POINTER DataIn Message body data area pointer

The unified structure of data messages is shown in Table 5.7 -3.

34
 Chapter 5 112 Common Interfaces

Table 5.7-3 Structure Table of Data Messages

Data Type Abbreviations Description

Message type: 1 for data message; 2 for command
BYTE MsgType
message; 3 for data response; 4 for command response
BYTE Version Version number
BYTE HeadLen Message head length
DWORD SerialNo Serial number
Terminal ID, used to designate a task in the unified
BYTE TerminalID
interface program
WORD UnitLen Data unit length
BYTE UnitNum Data unit number
POINTER DataIn Message body data area pointer

The unified data structure of command response is shown in Table 5.7 -4.

Table 5.7-4 Data Structure Table of Command Response

Data Type Abbreviations Description

Message type: 1 for data message; 2 for command
BYTE MsgType
message; 3 for data response; 4 for command response
BYTE Version Version number
BYTE HeadLen Message head length
DWORD SerialNo Serial number
Terminal ID, used to designate a task in the unified
BYTE TerminalID
interface program
BYTE Retcode Response data: 0 for success; others for failure.

The unified data structure of data response is shown in Table 5.7 -5.

35
ZXJ10V10.0 (V03.03Eu) Digital SPC Switching System User’s Manual (112 Liner Tester Console)

Table 5.7-5 Data Structure Table of Data Response

Data Type Abbreviations Description

Message type: 1 for data message; 2 for command message; 3
BYTE MsgType
for data response; 4 for command response
BYTE Version Version number
BYTE HeadLen Message head length
DWORD SerialNo Serial number
Terminal ID, used to designate a task in the unified interface
BYTE TerminalID
program
BYTE Retcode Response data: 0 for success; others for failure.

5.7.9.2 Input Format

The input data are transmitted in the direction of from external port to the unified
interface. The input format is the standard 112 test command line, for the details, please
refer to Section 5.4. The command line input does not perform grammar analysis,
which will be implemented by 112 test execution program. For the communication
mode adopting the serial port as external port, please attach a start character and an end
character for serial port receiving respectively at the beginning and end of the
command line.

5.7.9.3 Output Format

The output data are transmitted in the direction of from the unified interface to the
external port.

The output format of the successful command line is:

COMMAND INPUT: +input command line echo+#13#10+112 test return report

+#13#10

And, the input command line echo refers to echo the input command line.

112 test return report refers to the return results of the command check or execution
returned by 112 test program, and it is output in the format of ASCII code. For the
details, please refer to Section 5.4.3.2.

36
 Chapter 5 112 Common Interfaces

6 Remote Module 112 line tester console

6.1 Overview
For a multi-module office, 112 centralized acceptance and test is usually adopted.
However, in some areas, according to management requirement and requirement for
facilitating the 112 complaints from remote module users, quickly locating phone faults
and troubleshooting, it is required to realize 112 acceptance and test of the local
module users at the remote module. So, the ZXJ10 switch provides the remote module
112 line tester console. An introduction to the installation methods of the remote
module 112 line tester console is given below.

6.2 Networking Requirements

Remote modules are usually located in villages and towns, with the test desk and racks
in the same equipment room. And a remote module 112 line tester console and remote
module MP are connected through a HUB, as shown in Fig. 6.2 -78.

To SNM

Master /slave
ZXJ10 MP comm. line
RSM

Hub
Line Test and measurement desk

Fig. 6.2-78 Networking of Remote Module 112 line tester console

6.3 Installation Procedure

6.3.1 Computer Installation

For the installation of the operating system and database, please refer to the
ZXJ10V10.0 (V03.03Eu) Digital SPC Switching System Installation Manual(Software)

1
6.3.2 Background Installation

1. Run the \INSTALL\INSTALL.EXE file of the version to install the background

version. In the interface shown in Fig. 6.3 -79, select "Remote Server" for
"Type", and input the local node number in "Please select a remote server".
Click <OK> to enter the interface shown in Fig. 6.3 -80.

Fig. 6.3-79 Selecting the Installation Type

2. In the interface shown in Fig. 6.3 -80, select "Client" and "Local Terminal" for
"Terminal Type", and select "Install COMM System" for "Installation Mode".

2
 Chapter 5 112 Common Interfaces

Fig. 6.3-80 Selecting the Terminal Type and Installation Mode

3. In the interface shown in Fig. 6.3 -80, click <Next>, and the interface shown in
Fig. 6.3 -81 will pop up. Click a maintenance module in “Named Node
Settings” and select < >>>. In “Node Name” on the right, select “Maintenance
Module”, and input the remote module node number in “Node Code”, and then
select <<<>. Leave other parameters unchanged, and click <Next> to enter the
interface of selecting installation options, as shown in Fig. 6.3 -82.

3
Fig. 6.3-81 Selecting the Maintenance Module

4. Check [Communication System], [Authority System], [ZXJ10 Switch DB],

[Line Tester Console] and [File Management System], and then start initializing
the database, as shown in Fig. 6.3 -82.

Fig. 6.3-82 Subsystem Installation

5. Click <Next> and the interface shown in Fig. 6.3 -83 appears.

Fig. 6.3-83 Start the Installation

6. Click <Start Installation>, and the installation prompt window will pop up, as
shown in Fig. 6.3 -84.

4
 Chapter 5 112 Common Interfaces

Fig. 6.3-84 Installing

7. After the installation, copy the \…\install\112\remote\T112dpr.exe file in the

installation disk into c:\ZXJ10 directory.

8. Run c:\zxj10\WINNTTCP.EXE (or server process dispatch monitoring), and run

c:\zxj10\T112dpr.exe for login.

6.4 Data Configuration

6.4.1 Data Configuration

For the detailed procedure of the data configuration, please refer to Chapter 2.

6.4.2 Operations

Please refer to Chapter 4.

6.5 Precautions for Debugging

1. Normally, run c:\zxj10\tcpmaint.exe (or press <Ctrl+Alt+F12>) to enter the
background communication status observation. In [TCP status], it can be seen
that the connection status of node 4 is "True". When test operations or hookoff
operations are undergoing, in [Application program information], it can be seen
that the sending module of 112 line tester console is 4.

2. The remote module 112 does not support the routine test.

Sysfacec.exe cannot be run on the remote module 112 test terminal. If you run
the program, you will not be able to log in the local/remote module server, and
there will be a prompt of "Login failed".