Acceptance Testing: C-Dot Dss Max

C-DOT DSS MAX
ACCEPTANCE TESTING
Section No. 400-314-0715
System
Practices Draft 02, February 1999
C-DOT DSS MAX
ACCEPTANCE TESTING
(Valid for different configurations of SBM-RAX, MAX & TAX)
(Updated w.r.t. S/W link 2_1_1_1 to support CCS7,
ISDN and 800 K BHCA)
© 1999, C-DOT
Printed in India
C-DOT DSS MAX
ACCEPTANCE TESTING
DRAFT 02
FEBRUARY 1999
MAGHA 2055
SERIES 300 : INSTALLATION
CSP SECTION NO. 400-314-0715
THIS C–DOT SYSTEM PRACTICE REFERS TO THE C–DOT DIGITAL SWITCHING SYSTEM
MAIN AUTOMATIC EXCHANGE (ABBREVIATED AS C–DOT DSS MAX IN THE REST OF THIS
PUBLICATION).
THE INFORMATION IN THIS SYSTEM PRACTICE IS FOR INFORMATION PURPOSES AND IS
SUBJECT TO CHANGE WITHOUT NOTICE.
A COMMENT FORM HAS BEEN INCLUDED AT THE END OF THIS PUBLICATION FOR
READER'S COMMENTS. IF THE FORM HAS BEEN USED, COMMENTS MAY BE ADDRESSED
TO THE DIRECTOR (SYSTEMS ), CENTRE FOR DEVELOPMENT OF TELEMATICS, 39, MAIN
PUSA ROAD, NEW DELHI - 110 005
© 1999 BY C–DOT, NEW DELHI.

Table of Contents
Chapter 1. Introduction .....................................................................................................................................5
Chapter 2. Conformity Check ...........................................................................................................................7

2.1. Document ..........................................................................................................................7
2.2. Hardware...........................................................................................................................7
2.3. Software.............................................................................................................................8
Chapter 3. Cabling, MDF and Power Distribution Checks.............................................................................9
3.1. Cabling ..............................................................................................................................9
3.2. MDF/DDF..........................................................................................................................9
3.3. Power Distribution .........................................................................................................10
Chapter 4. Alarm Tests for Power & Fire Alarms .........................................................................................12
4.1. Power Alarms..................................................................................................................12
4.2. Fire Alarms .....................................................................................................................12
Chapter 5. System Level Tests .......................................................................................................................13
5.1. Self Test of Devices .........................................................................................................13
5.2. IOP Testing .....................................................................................................................13
5.3. Initialization Tests..........................................................................................................19
5.4. Equipped Card Testing...................................................................................................21
5.5. Power Supply Alarm Testing in BASE MODULE........................................................21
5.6. Power Supply Alarm Testing in Central Module Rack ................................................23
5.7. Switch Unit Alarms ........................................................................................................27
Chapter 6. Exchange Data Checks .................................................................................................................28
6.1. Local Data .......................................................................................................................28
6.2. Trunk & Route Related Data .........................................................................................28
6.3. Charging Data.................................................................................................................28
Chapter 7. Switching Function Check............................................................................................................30
7.1. Tests on Local Subscriber Lines ....................................................................................30
7.2. Junction Testing .............................................................................................................30
7.3. Subscriber Features........................................................................................................33
7.4. Testing of Tones/Announcements ..................................................................................35
7.5. Testing of RSU Functions ..............................................................................................36
Chapter 8. ISDN & CCS7 Testing Within the Exchange..............................................................................39
8.1. Testing of ISDN Services ...............................................................................................39
8.2. ISDN U-Interface Testing ..............................................................................................39
8.3. ISDN Bearer Services.....................................................................................................43
8.4. ISDN Supplementary Services ......................................................................................47
8.5. Test of ISDN Services On CCS7 ....................................................................................48
8.6. Signalling Check .............................................................................................................50
8.7. Check for Analogue Subs Facilities ...............................................................................51
Chapter 9. Testing of Spare Cards .................................................................................................................52
9.1. Card Testing....................................................................................................................52
9.2. Testing of BM/LM Related Cards ..................................................................................52
9.3. Testing of IOP Related Cards of IOP-VH......................................................................60
9.4. Testing of CM Related Cards .........................................................................................60
Chapter 10. Service Quality ..............................................................................................................................67
Appendix A Operation Procedures for Supplementary Services in C-DOT...................................................71

A.1 Number Identification Supplementary Services ..........................................................71
A.2 Call Offering Supplementary Service............................................................................72
A.3 Call Completion Supplementary Services.....................................................................72
A.4 Dynamic Locking for Access Levels...............................................................................74
A.5 Miscellaneous Supplementary Services ........................................................................74
H:\HOME\MAX2111\WORD\DSSMAXAT.DOC February 22, 1999

Chapter 1.
Introduction
This document is intended to be used for acceptance testing of C-DOT DSS to certify
that C-DOT DSS will provide the satisfactory service after it’s commissioning in the
network. This document is common for Acceptance Testing of different
configurations of C-DOT DSS as SBM RAX, MAX-L, MAX-XL or TAX. The test plan
covers the acceptance testing for optional features such as RSU, CCS7 and ISDN
which may or may not be the part of exchange at the time of commissioning.
In general, the test procedures, which are common, can be executed sequentially.
Where ever, some test procedures are different and may not be valid for specific
configuration, such tests are clearly marked and explained.
The software release supports any mix of the different hardware modules. The tests
are also explained accordingly. Depending on the availability of specific
configuration being planned for commissioning, the relevant procedures may be
identified for acceptance testing.
Different possible configurations in C-DOT DSS are :
SBM-RAX : The product is defined as BM-XL (with BPC) and IOP-VH.
MAX-L : The product C-DOT MAX-L is defined as CM-L with a
maximum of 16 BMs and IOP-VL/IOP-VH. Depending on the
site configuration, the BMs can be Line BM, Digital Trunk
BM, Trunk BM with Analog as well as Digital Trunk or RSU.
Further, it is possible that all the BMs can be BM-L or BM-XL
(with BPC and BME).
MAX-XL : The product C-DOT MAX-XL is defined as CM-XL with BPC
with a maximum of 32 BMs and IOP-VH. Depending on the
Further, it is possible that all the BMs can be BM-XL with
BPC and BME).
MAX-XLE : The product C-DOT MAX-XLE is defined as CM-XL with HPC
with a maximum of 32 BMs and IOP-VH. Depending on the
ACCEPTANCE TESTING 5
Chapter 1.
All the BMs are equipped with HPC and HMS to meet higher
BHCA requirement.
TAX-XL : The product C-DOT TAX-XL is defined as CM-XL with BPC, a
max. of 32 BMs with BPC and IOP-VH. Depending on the site
configuration, the BMs can be Digital Trunk BM or Trunk BM
with Analog as well as Digital Trunks. The CCS7 signalling
unit is equipped with HPC to meet requirement of higher
BHCA and 64 signalling links.
TAX-XLE : The product C-DOT TAX-XL is defined as CM-XL with HPC, a
max. of 32 BMs with HPC and IOP-VH. Depending on the site
configuration, the BMs can be Digital Trunk BM or Trunk BM
with Analog as well as Digital Trunks. The CCS7 signalling
unit is equipped with HPC to meet requirement of higher
BHCA and 64 signalling links.
NOTE : 1. In all the above configurations, the optional hardware modules
such as SUM for CCS7 and ISTU to support ISDN, may also be
equipped.
2. Even though the configurations of CM-XL with BM-L or CM-L
with BM-XL is not mentioned above, they are very much feasible
and may exist at some sites, being integrated due to relocation of
the switching racks from one site to another site. In fact, it is
possible to integrate any mix of switching modules at the same
site, subject to the limitation that necessary engineering
instructions, related to inter rack cabling is followed and traffic
conditions are taken into account.
6 C-DOT DSS MAX

Chapter 2.
Conformity Check
2.1. DOCUMENT
Ensure that the documents as per despatch list are available.

Ensure that other registers for proper record keeping (administrative and technical)
are also available e.g. exchange log-book, subscribers complaint's record,
subscribers data, etc.
Ensure that adequate number of fault and repair statement forms and fortnightly
performance report/statistical data forms are also available at site.
2.2. HARDWARE
i. Check the appearance of iron work and racks.

ii. Painting should be smooth and nuts and bolts for fixing the rack and iron work
should be tight.
iii. Ensure that proper marking is done on racks for their identification.
iv. Ensure that proper cable markers have been put on various cables as per
installation document. Check cable markers for the following cables -
♦ All -48V power cables i.e. power cables from power room to switch room
upto the individual racks, from power room to IOP's, ADP, inverter, PCM
equipments (if any), etc.
♦ All earth distribution cables from earth collector plate to MDF, power
room, inverter input, individual racks, chassis earth plate, PCM
equipments (if any) etc.
♦ Subscriber and trunk connections cables from racks to MDF.
♦ PCM cables from racks to Digital Distribution frame, and from Digital
Distribution frame to the PCM equipment.
♦ Cables from AP to IOP's, ADP in MAX-L/MAX-XL. In SBM, these cables
are connected to BP instead of AP.
♦ Cables between IOP's and between Base Module and Line Modules.
Chapter 2.
v. Check the configuration and equipage of PCBs within racks as per the equipage
list.
vi. Ensure that the fuse ratings of all PDP fuses, rack fuses, fan assembly and PSU
card fuses are correct.
2.3. SOFTWARE
Verify the software version of EPROMs, cartridges and floppies by matching the
labels with the software status as given in the Media Detail Form of the S/W
Release.
8 C-DOT DSS MAX

Chapter 3.
Cabling, MDF and Power Distribution

Checks
3.1. CABLING
Ensure that all the cables are neatly laced and properly routed. All cables should be
protected from contact with sharp edges. Also check for the proper cable types and
cable terminations as mentioned in the installation document. Check for the
following type of cables.
• Subscriber and trunk cables from racks to MDF.
• PCM cables from racks to DDF and from DDF to PCM equipment.
• -48V power cables from power room to racks, IOP, ADP, inverter and PCM
equipments.
• Earth distribution cables from earth collector plate to MDF, power room,
inverter input, racks, IOPs, ADP and PCM equipment.
• 220V AC from inverter to the power points provided to supply power to IOP
terminals and printers.
• Engine alternator to AC distribution box/panel.
• AC distribution box to different points in power room, switch room & IOP/OMC
room.
3.2. MDF/DDF
i. The location of the verticals should be verified with reference to the approved
floor plan and the alignment of a number of verticals should be checked by
means of plumb line.
ii. Examine whether each vertical is rigid and firmly fixed to the adjacent verticals
and to the floor.
iii. Check whether all nuts and bolts are tight and secure.
iv. Check up whether the verticals have a coat of the proper type and colour of paint
and good finish.
9
Chapter 3.
v. Sharp bends in cable or wiring should be avoided. Also ensure that both external
plant cable and cables from the racks are brought to MDF in a tidy fashion.
vi. Wire of approved quality and specification should be used for cross-connections
on frames. In two conductor jumpers, white is to be used for positive and red for
negative leads. Jumper wires should not be hanging loose on the frame so as to
make the appearance untidy. They should not, on the other hand, be pulled very
tight as that will cause tracking of circuits very difficult. These jumpers should
be connected just tight so as to have neat and tidy finish.
vii. The location and the proper fitting and mounting of the protection modules on
the various (line side) verticals of the frame should be checked.
3.3. POWER DISTRIBUTION
3.3.1. -48V Power Distribution
-48V power distribution has been planned with the aim to achieve a drop of
not more than 1V from the source point (DC switching cubicle of power room)
to the destination point (PDP). -48V power is brought out from IDP in power
room to DCDP in switch room and then to Power Distribution Panel (PDP)
through two separate sets of cables, one for copy 0 and the other for copy 1
portion of the racks. From IOP-PDP, -48V power is also given to IOPs,
inverter and PCM equipment (transmission room). All power cables are fed
through fuses of proper ratings as mentioned in the document.
Inside the switch room, copy 0 portion of PDP distributes power to all copy 0
portion of all the racks of the suite through separate fuses. Similarly copy 1
portion of PDP distributes power to all copy 1 portions of all racks of the suite
through separate fuses. Corresponding to each fuse on PDP, there are two
LED's-yellow and red on the FBI card, used on the PDP.
When all fuses corresponding to all copies of racks are OK, main yellow LED
on PDP glows. When any of the rack copy fuse blows, corresponding red LED
glows.
Inside the OMC room, PDP fuse alarm indication is brought out in the form
of audio (bell) and visual (lamp) alarm. Blowing of any of PDP fuses results in
activation of this alarm, in OMA box.
In the OMC room, another alarm indication from power room is brought out
in audio (bell) and visual (lamp) form. Presence of any alarm conditions in
the power room is reflected on DC switching cubicle and also activates the
audio visual alarm in the OMC room. The sizes of different cables, and their
termination methods have been indicated in the installation document.
10 C-DOT DSS MAX

CABLING, MDF AND POWER DISTRIBUTION CHECKS
3.3.2. 220V AC from Inverter
220V AC from inverter is distributed to various points to provide power to

IOP terminals and printers. Measure the AC voltage present at inverter
output.
3.3.3. 3 Phase AC Distribution
AC distribution panel gets 3 phase AC from Engine Alternator and the local
supply. Through changeover switch on the AC distribution panel, any of the
supply can be selected and given to Power Room for float rectifier, various
power points in switch room/IOP room/OMC room provided for general
purpose and lighting points in different rooms of the exchange.
3.3.4. DC Earth Distribution
From DC earth pit, earth is brought to DC earth collector plate. The

resistance of the mother earth should be less than 0.5 ohms. Earth is
distributed from the earth collector plate to MDF, DDF, power room,
switching cubicle, PDP in switch room, PCM equipment and inverter input,
and shields of underground cables in cable chamber.
Ensure that the earth distribution is as mentioned in the installation
document. Also verify the method of earth cable termination at each point on
MDF, and ensure that external cable (line) side of the MDF (i.e. MDF
verticals) have their backmount frames connected with a very low resistance
(<0.5 ohm) to the main MDF earth point. For this purpose, a very thin copper
strip is placed between the MDF frame work and the backmount frame.
C-DOT DSS MAX 11

Chapter 4.
Alarm Tests for Power & Fire Alarms
4.1. POWER ALARMS
As described in section 2.3.1, power alarms are brought out in OMC room from PDP
of switch room & from switching cubicle of Power Room, both in audio (bell) &
visual (lamp) form.
i. Remove one of the fuses of PDP or filter boxes in the racks (BMs, LMs & CM) or
fan assembly of CM rack & verify that corresponding alarm indications are
properly reflected on PDP. Also verify that it also results in activation of audio
visual alarm in OMC room.
Replace the fuse & verify the deactivation of alarms at PDP & in OMC room.
Repeat the above for different fuses of PDP & filter boxes in the racks.
ii. Simulate some fault conditions in the power plant & verify that it results in
activation of appropriate alarm indications on DC switching cubicle & audio-
visual alarm in OMC room.
Remove the fault condition in power plant & verify that it results in deactivation
of alarms indications on DC switching cubicle & audio-visual alarm in OMC
room.
4.2. FIRE ALARMS

Smoke detectors are provided at various places in the exchange e.q. switch room
and IOP/OMC room. Sensors from all the smoke detectors are brought out on a
panel in OMC room. The Panel has lamp indications for all the zones where smoke
detectors have been put.
With each smoke detector, one LED is provided which starts glowing whenever
smoke detector detects smoke/fire. Whenever smoke/fire is present in any zone of
exchange, smoke detector of that zone detects it & glows its LED. In OMC room
also, Fire detection lamp indication for the zone appears on the Panel & hooter of
the panel starts beeping. Audio-visual fire alarm indication on the panel & visual
LED indication on the corresponding smoke detector remain as long as smoke/fire is
detected by the smoke detector. Ensure that all the smoke detector fire alarms are
functioning properly by producing some smoke below the smoke detectors &
verifying activation of appropriate fire alarms.
12 ACCEPTANCE TESTING
Chapter 5.
System Level Tests
5.1. SELF TEST OF DEVICES
Switch on VDU's, printers & ADP & perform self test. For self-test procedure of
VDU's & printers, refer manufacturer's manual. For ADP, press LED test button &
verify that all LED's and seven segment displays are lighted properly.
5.2. IOP TESTING
The following tests shall be performed on each of the IOPs from the console VDU.
5.2.1. Onboard Devices Tests for C-DOT IOP
5.2.1.1. RTC Test

SYNTAX : VHC x.x > rtc <DD> <MM> <YY> <HR> <MIN>
<SEC> <DOW> <duration> <dis_opt>
USAGE~ : This command allows the user to program the Real Time
Clock to generate an alarm after ‘n' seconds.
Periodic display can be enabled or disabled through a flag.
All parameters need to be specified in hex (or give with an
`Amperesand’, & Sign).
Parameter ranges:
date : 1-31
month : 1-12
year : 0-99
hours : 0-23
minutes : 0-59
seconds : 0-59
day of week : 1-7
display option : 1-> enables periodic display
0->disables periodic display
C-DOT DSS MAX 13

Chapter 5.
For e.g. : for a given date July 27, 1998 Mon 16:20:29
Parameters are :
Date : 1b
Month : 7
Year : 62
Hours : 10
Minutes : 14
Seconds : 14
Day of week : 2
Display option : 1
Message displayed ! Wake up !!! July 27, 1998 Mon
16:20:29
5.2.2. Memory Diagnostic Tests
5.2.2.1. Checker Board Test

SYNTAX : VHC x.x> check <iter> <addr><count>
USAGE~ : The Checker Board pattern viz. ‘aa' and ‘55' are filled in
the specified memory area, read back and checked. It may
be checked up with the below mentioned values.
VHCX.X>check 1 1020000 400000
VHCX.X>check 1 1420000 400000
VHCX.X>check 1 1820000 400000
VHCX.X>check 1 1C20000 3dFFFF
This test will take about 6 minutes for each command.
After completion of this test it shows :
Test Over ! Total error : 0
5.2.2.2. March Test
SYNTAX : VHC x.x> march <iter> <addr> <count>
USAGE~ : This test can be used to detect address line shorting. It
fills the specified memory area with 0's and then 1
location is changed to ‘ff'. The memory is read back and
14 C-DOT DSS MAX

SYSTEM LEVEL TESTS
ensured that the contents of no other location have
changed. This process is repeated with each address
failing in the test area, ‘count' number of times.
For e.g. VHC X.X> march 1 1020000 1000
VHC X.X> march 1 1420000 1000
VHC X.X> march 1 1820000 1000
VHC X.X> march 1 1C20000 1000
This test will take about 15 minutes for each command.
After completion of test it shows :
5.2.2.3. Walking Test
SYNTAX : VHC x.x> walk <iter> <addr> <count> <flag>
USAGE~ : This test can detect data line shorting. The test area is
filled with zeroes or ones depending on a software flag
which can be set/reset by the user.
Flag=0 : Walking zero test. Base Pattern = ‘ff' Flag = 1 :
Walking one test. Base Pattern = ‘00'. The zeroth bit of
location 1 is changed to 0/1. The test area is read and
verified that no other location has been affected. Zeroth
bit is restored and the entire process repeated for bit
1,2,... . It may be checked up with the below mentioned
values.
VHCX.X>walk 1 1020000 400000 0
VHCX.X>walk 1 1020000 400000 1
This test will take about 35 minutes for each command
after completion of test it shows :
5.2.3. Diagnostics Commands for ACIA/HDLC
5.2.3.1. Asio Test #1

SYNTAX : VHC x.x> asio <chnl> <iter> <0-external, 1-interval >
USAGE~ : This test requires a loopback connector (Tx and Rx
shorted) on the specified channel. The command performs
a link stability test and over-run test on the specified link.
Cumulative error counts and timeouts are indicated on
C-DOT DSS MAX 15

Chapter 5.
the screen. The test is performed 10 number of times. The

mode specifies whether the tests are to be performed in
the external mode or internal mode. Default value for
mode is polled. It is advisable to perform this test in
interrupt mode.
For e.g. VHC X.X> asio 1 1
After completion of test it will show :
Iteration : 1, Timeout : 0, Mismatch : 0, Success : 1
Cont. →
VHCX.X>asio 1 10
Specification of both parameters is essential.
5.2.3.2. Host Test
SYNTAX : VHC x.x> host <iter>
USAGE~ : The host port test dumps character patterns onto the host
terminal. This is useful to check the interrupt mode
operation of the host hardware. Iterations specifies the
number of times the test is to repeated.
Specification of the parameter is necessary.
For e.g. VHC X.X> host 1
This command will take about 1 sec. After completion of
test it will show.
Iteration : 1, Timeout : 0
Cont. →
5.2.3.3. VDU Test
SYNTAX : VHC x.x> vdu <chnl> <iter>
USAGE~ : The VDU test dumps character patterns onto the
terminal connected to the specified ASIO port. <iter>
specifies the number of times the test is to be repeated.
For e.g. VHC X.X> vdu 1 1
This command will take about 1 sec. After completion of
test it will show :
VDU test on link 1
16 C-DOT DSS MAX

SYSTEM LEVEL TESTS
Iteration : 1, Timeout : 0
Specification of first parameter is essential.
5.2.3.4. HDLC Test
SYNTAX : VHC x.x> hdlc <chnl> <iter>
<0-external, 1-internal>
USAGE~ : This test requires a loopback connector. The tests
performed include loop-back test, underrun test, overrun
test and frame-abort test. Error counts are indicated on
the screen. The number of iterations should also be
specified. The mode specifies whether the tests are to be
performed in the external mode (0) or internal mode (1).
Default value for mode is polled. It is advisable to perform
this test with following parameters.
VHCX.X>hdlc 0 10 for HDL1
VHCX.X>hdlc 5 10 for HDLC6
For e.g. VHC X.X> hdlc 1 1 0
If the test is o.k then it will take shout 1 sec. and it shows:
If the test is failed then it will take about 10 secs. and it
will show :
5.2.3.5. Printer Test
SYNTAX : VHC x.x> print <chnl> <iter>
[<mode: 0-polled, 1-interrupt>]
USAGE~ : This command validates the specified printer port by
outputting a sliding pattern to it. The pattern can be
visually inspected. The channel can be one of the ASIO
modem channels. Iteration count also needs to be
specified.
Both parameters need to be input.
For e.g. VHC X.X> Print 0 1
A message on printer will be displayed i.e.
Serial printer test on port #0 (in polled mode)
C-DOT DSS MAX 17

Chapter 5.
5.2.4. Diagnostic Commands for SCSI Devices
5.2.4.1. SCSI Bus Reset

SYNTAX : VHC x.x> scrs
USAGE~ : The command causes the SCSI bus to be reset.
All devices are initialized - by assigning the relevant
parameters as part of this command. The command takes
no parameters.
It will give nothing, when it is o.k.
5.2.4.2. Test Drive Unit
SYNTAX : VHC x.x> tdu <dev>
USAGE~ : The command selects the device specified and/or ready. If
no floppy/cartridge is present and this command is given
for the respective SCSI device a message saying “Drive
not ready or no FLOP/CART” will be printed.
Devices can be specified in the following manner :
w0 - Winchester
For e.g. VHC X.X>tdu w0
If it is o.k. then no message will display and it will come
back to prompt again.
If it is faulty then message will display on screen.
c - Cartridge Drive
For e.g. VHC X.X>tdu C
If there is no cartridge then it will show
Drive not ready
No defaults assumed.
5.2.4.3. Inquiry
SYNTAX : VHC x.x> inq <device>
USAGE~ : Inquiry command gives the detail of the SCSI device
connected. The bits of first 8 bytes have specific
information whose details will be available in the
respective device manual. The remaining bytes shows the
model number and the name of the manufacturer.
18 C-DOT DSS MAX

SYSTEM LEVEL TESTS
For e.g. VHC X.X>inq w0
It will show the model of the disk used. For Example :
0022-1270024 Quantum Fire ball TM1280530B0
5.2.4.4. Read Capacity
SYNTAX : VHC x.x> cap <device>
USAGE~ : Read capacity command gives the maximum number of
blocks that can be accessed through the SCSI disk and the
size of each block with total capacity in MB.
For e.g. VHC X.X>cap w0
The result may be :
Total no. of blocks = 2503871 of 512 bytes each capacity =
1222 MB
5.3. INITIALIZATION TESTS
A set of tests need to be performed to test that the system initializes under various
configurations of hardware. These tests involve software loading from the IOPs. The
system must be connected with both the IOPs. The following tests are to be
performed:
TIC nos. corresponding to the concentration TUs are TI02-0, TI03-0, TI04-0, TI06-0,
TI07-0, TI08-0, TI10-0, TI11-0, TI12-0, TI14-0, TI15-0, TI16-0, for copy 0 TICs.
Similarly TI02-1, TI03-1, TI04-1, TI06-1, TI07-1, TI08-1, TI10-1, TI11-1, TI12-1,
TI14-1, TI15-1, TI16-1 for copy 1 TICs.
NOTE : In case of ISDN Terminal Units, in addition to TIXX, ICC units status
will be displayed.
5.3.1. Initialization with the Default Status Map
This test involves complete downloading of software from the IOPs. The two
IOPs must be in warm start level and all the frames in all the racks in the
exchange must be in a switched off condition to start with. If the exchange is
already in powered up state, the following procedure must be followed before
performing this test :
i. If the IOPs are in duplex, bring them to warm-start level by issuing the
command 'INIT-IOP : 2, 1;' from its console.
ii. Switch off the copy-0 and copy-1 PSUs of all the frames in all the racks.
C-DOT DSS MAX 19

Chapter 5.
iii. Power up the frames of the CM in the following sequence –
APU, SCU, SSU & BTU.

iv. Power up the frames of the BM in the following sequence -
TU1, TU2, TU3, TU4, equipped concentration TUs, TSU and BPU. Reset
all the controller cards in the BM & LMs in the same order as they were
powered on.
v. Issue the command 'INIT-IOP :5, 1;' from IOP-0. The 'Code Loading
Begins' message should appear on the IOP-0 console. After loading is
complete, the 'Load Pass' report should appear on the OOD and printer.
vi. Check the system status using DISPL-SYS-ALL command and make some
inter-BM calls covering all BMs.
vii. Now bring IOP-0 to warm start level by issuing 'INIT-IOP :2, 1;' command
and repeat steps (ii) to (vi) using IOP-1.
5.3.2. Initialization with following Configurations
Before proceeding with test, the IOPs should be brought in duplex. Using the
INTCHG command, make all copy zero controllers INS-ACT and copy 1
controllers INS-SBY in all the modules.
In all of the following tests 5.3.2.1 to 5.3.2.6, the same procedure as given
below is to be used:
Using 'INTCHG' command, ensure the desired configurations of the
controllers as INS-ACT/INS-SBY. Issue an INIT-SYS command to give a
softstart (SS). The message 'Data Loading Begins' should appear on the IOP
console. After sometime the 'Load Pass' report appears on the OOD/Printer,
check the system status using DISPL-SYS-ALL command. Check that all the
copies which were active before the softstart are still active. Make some inter-
BM calls covering all the BMs.
5.3.2.1. All copy zero controllers are active in the BMs i.e. TI01-0, TI05-0, TI09-0,
TI13-0, copy 0 TICs of equipped concentration TUs, TS-0, SCIC-0, TOGC-0,
BMS-0, BP-0, copy-1 controllers are standby. Check for the CM that AP-0,
SSC-0, IFCs, MU-0 and MU-1 of CM and AM both, SS-0, CMS- 1, CMS-2,
CMS-3 and CMS-4 are active & AP-1, SSC-1, SS-1 are standby. Check for the
IOP that IOP-0 is active & IOP-1 is standby. Make inter-BM calls covering all
BMs.
5.3.2.2. TI01-0, TI05-0, TI09-0, TI13-0, copy0 TICs of equipped concentration TUs,
TSC-1, SCIC-0, TOGC-0, BMS-0, BP-1, MU-0, MU-1 active (in BMs), AP-1,
20 C-DOT DSS MAX

SYSTEM LEVEL TESTS
SSC-0, IFCs, MU-0 and MU-1 of CM and AM both, SS-0, CMS1, CMS2,
CMS3 and CMS4 active (in the CM) and IOP-0 active.
5.3.2.3. TI01-0, TI05-0, TI09-0, TI13-0, Copy 0 TICs of equipped concentration TUs,
TSC-1, SCIC-1, TOGC-1, BMS-0, BP-1, MU-0, MU-1 active (in the BMs), AP-
1, SSC-1, IFCs, MU-0 and MU-1 of AM and CM both, SS-0, CMS-1, CMS-2,
CMS-3 and CMS-4 active (in the CM) and IOP-0 active.
5.3.2.4. Initialisation with all copy 1 controllers active i.e. TI01-1, TI05-1, TI09-1,
TI13-1, copy 1 TICs of equipped concentration TUs, TSC-1, SCIC-1, TOGC-1,
BMS-1, BP-1, MU-0, MU-1 active (in the BMs), AP-1, SSC-1, IFCs, SS-1, MU-
0 and MU-1 of both CM and AM, CMS-1, CMS-2, CMS-3 and CMS-4 active
(in the CM) and IOP-1 active.
TSC-0, SCIC-1, TOGC-1, BMS-1, BP-0, MU-0, MU-1 active (in the BMs), AP-
0, SSC-1, IFCs, SS-1, MU-0 and MU-1 of CM and AM both, CMS-1, CMS-2,
CMS-3 and CMS-4 active (in the CM) and IOP-1 active.
TSC-0, SCIC-0, TOGC-0, BMS-1, BP-0, MU-0 and MU-1 active (in the BMs),
AP-0, SSC-0, IFCs, SS-1, MU-0 and MU-1 of CM and AM both, CMS-1, CMS-
2, CMS-3 and CMS-4 active (in the CM) & IOP-1 active.
5.4. EQUIPPED CARD TESTING
Each card equipped in BMs, LMs & CM shall be tested one by one. The procedure
for card testing is same as given in chapter 8 (for spare cards). No card has to be
taken out. Each card has to be diagnosed for its health.
5.5. POWER SUPPLY ALARM TESTING IN BASE MODULE
Depending upon the site configuration, a BM may have different types of frames
equipped. Accordingly, e.g. if ISTU is equipped, testing as per 5.5.3 has to be carried
out . The tests for all the frames in the BM as well as LM may be performed.
5.5.1. Power Supply Alarm Testing in Analog TU / DTU
Switch off one of the power supplies of a TU and check that the alarm is
reported on the OOD/Printer and the ADP. Switch it ON and the alarm
should get cleared on the ADP while clearing messages should come on the
OOD/Printer. Repeat the same for the other PSU in the TU.
The above procedure should be repeated for all the PSUs of TUs including
concentrate TUs in the system.
C-DOT DSS MAX 21

Chapter 5.
5.5.2. Power Supply Alarm Testing in SUM
There are four power supplies, two in each plane feeding the power to
corresponding copy of the SUM and both of them work in "Load Sharing
Mode".
i) Switch OFF the power supply in Slot 1 and wait for the alarm to be
raised on ADP, OOD and Printer. Now switch ON the Power Supply
and wait for alrm to be cleared from the ADP as well as becomes
NORMAL on OOD/Printer.
ii) Repeat the test for power supplies in Slot Nos. 3, 23 and 25 one by one
ensuring that both the PSUs in the same side are not switched OFF
simultaneously.
5.5.3. Power supply Alarm Testing in ISTU
i) Switch OFF the power supply in Slot 1 and wait for the alarm to be
raised on ADP, OOD and Printer. Now switch ON the Power Supply
and wait for alarm to be cleared from the ADP as well as becomes
Normal on OOD/Printer.
ii) Repeat the test for power supply in Slot No. 3. ensuring that both the
PSUs in the same side are not switched OFF simultaneously.
5.5.4. Power Supply Alarm Testing in BPU
Ensure that BP-0 is standby. If BP-0 is active then make it standby using the
command INTCHG with UNIT- ID = BP-0, MOD-ID = <BM-id>. Now make
BP-0 out-of- service using command PUT-SWU-OOS with UNIT-ID = BP-0,
MOD-ID = <BM-id>. Make MU-0 out-of-service using command PUT-SWU-
OOS with UNIT-ID = MU-0, MOD-ID = <BM-id>.
Switch off the copy 0 PSU of the BPU and check that the power alarm is
reported on OOD, ADP and printer. Now put it on and bring BP-0 inservice
using command PUT-SWU-INS with UNIT-ID = BP-0, MOD-ID = <BM-id>.
Bring MU-0 inservice using command FRC-SWU-INS with UNIT-ID = MU-0,
MOD-ID = <BM-id>. Check that the power alarm reported for BPU copy 0
gets cleared on OOD, ADP and printer.
After both the BP-0 and the MU-0 are inservice make BP-1 out-of-service
using the command PUT-SWU-OOS with UNIT-ID = BP-1, MOD-ID = <BM-
id>. Make MU-1 out-of- service using the command PUT-SWU-OOS with
UNIT-ID = MU-1, MOD-ID = <BM-id>. Now switch off the PSU of the BP-1
i.e., copy 1 in BPU and check that the power alarm gets reported on OOD
and printer. Switch ON the power supply, bring the BP-1 and MU-1 inservice
using similar commands as used above for bringing in BP-0 & MU-0 and
check that the alarm gets cleared on OOD, ADP and printer.
22 C-DOT DSS MAX

SYSTEM LEVEL TESTS
The above procedure should be repeated for each BM.
5.5.5. Power Supply Alarm Testing in TSU
Make all the controllers of copy-0 i.e., BMS-0, SCIC-0, TSC-0, TOGC-0 as
INS-SBY and then make them OOS-OPR. Also make MFC 1 and MFC2 as
OOS-OPR.
Switch OFF the copy 0 PSU of the TSU and check that the power alarm for
BMS-0 is reported on OOD, ADP & printer. Wait for about two minutes and
now put the PSU ON. Check that the power alarm for this copy also gets
cleared on OOD, ADP & printers and bring all the controllers in copy zero of
TSU to inservice state using 'PUT-SWU-INS" command one by one.. After all
the copy 0 controllers are inservice, repeat the procedure for copy 1 PSU of
the time switch unit.
The above procedure is repeated for all other BMs.
5.6. POWER SUPPLY ALARM TESTING IN CENTRAL MODULE RACK
Being the most critical component of the exchange, the power supply alarm
reporting should be properly verified for each and every power unit in the rack. As
per the site specific configuration, one of the two types of Central Module as CM-L
or CM-XL may be used. Accordingly any one of the following two sections as 5.6.1
for CM-L or 5.6.2 for CM-XL is applicable.
5.6.1. Power Supply Alarm Testing In CM-L Rack
CM-L rack consists of only four frames i.e. BTU, SSU, SCU and APU in that
order from top.
5.6.1.1. Power Supply Alarm Testing in SSU & SCU (Frame 2 & Frame 3 from
the top)
i) Ensure that copy 0 of SS is standby. If SS-0 is active then make it
standby using the command INTCHG with UNIT- ID = SS-0. Now
make SS-0 out-of-service using PUT-SWU-OOS command. Make MU-0
of CM out-of-service using command PUT-SWU-OOS with UNIT-
ID=MU-0, MOD-ID = CM. Also ensure that copy 0 of SSC is standby. If
SSC-0 is active then make it standby using the command INTCHG
with UNIT-ID = SSC-0. Now make SSC-0 out-of-service using
command PUT- SWU-OOS.
Switch off the copy 0 PSU of the SCU (frame 3 from the top) and check
that the power alarm with id SSC-0 is reported on OOD and printer.
Now put it ON and check that the power alarm report for SSC-0
(copy-0) changes to NORMAL on OOD & printer. Now switch off the
PSU in slot 1 of SSU (frame 2 from the top). Power Supply Alarm
C-DOT DSS MAX 23

Chapter 5.
should be raised for id SWC1-0. Switch on the power supply and see
that alarm changes to NORMAL on OOD/Printer. Repeat the test for
slot no. 23 (frame 2). Here PSU alarm will be raised for SWC9-0
instead of SWC1-0. Bring SSC-0 in service using command PUT-SWU-
INS with UNIT-ID = SSC-0. Bring MU-0 inservice using command
FRC- SWU-INS with UNIT-ID = MU-0, MOD-ID = CM. Bring SS-0
inservice using command PUT-SWU-INS with UNIT-ID = SS-0.
ii) After SSC-0, MU-0 of CM and SS-0 coming in service, make SS-1 out-
of-service using the command PUT-SWU-OOS with UNIT-ID = SS-1.
Make MU-1 of CM out-of-service using the command PUT-SWU-OOS
with UNIT-ID = MU-1, MOD-ID = CM. Make SSC-1 out-of-service
using the command PUT-SWU-OOS with UNIT-ID = SSC-1. Now
switch off the PSU of the SCU copy 1 (slot 25) and check that the PSU
alarm with id SSC-1 is raised. Switch off Power Supplies in slot no. 3 &
25 of frame 2. PSU alarms with id SWC1-1 & SWC9-1 are raised on
OOD/Printer. Now switch on the Power Supplies, one by one in slot 25
of frame 3 and slots 3 & 25 of frame 2. The PSU alarms should change
to NORMAL on OOD/Printer. Make the SSC-1, SS-1 and MU-1 of CM
inservice using same commands as used above for bringing in SSC-0,
SS-0 & MU-0 of CM and check that the alarms get cleared on OOD and
printer.
5.6.1.2. Power Supply Alarm Testing in APU (Frame 5 from the top)
Ensure that copy-0 of AP is standby. If AP-0 is active then make it standby
using the command INTCHG with UNIT- ID = AP-0. Now make AP-0 out-of-
service using command PUT-SWU-OOS with UNIT-ID = AP-0. Make MU-0 of
AM out-of- service using command PUT-SWU-OOS with UNIT-ID = MU-0,
MOD-ID = AM. Make CMS1 out-of-service using command PUT- SWU-OOS
with UNIT-ID = CMS1. Make CMS3 out-of-service using command PUT-
SWU-OOS with UNIT-ID = CMS3.
Switch Off the copy 0 PSU of the APU and check that the power alarm is
reported on OOD and printer. Now put it on and bring AP-0 inservice using
command PUT-SWU-INS with UNIT-ID = AP-0. Bring MU-0 of AM inservice
using the command FRC-SWU-INS with UNIT-ID = MU-0. Bring CMS-1
inservice using the command PUT-SWU-INS with UNIT-ID = CMS1. Bring
CMS3 inservice using the command PUT-SWU- INS with UNIT-ID = CMS3.
Check that the power alarm reported for APU copy 0 gets cleared on OOD
and Printer.
After coming of AP-0, MU-0 of AM, CMS1 & CMS3 inservice, make AP-1 out-
of-service using the command PUT-SWU-OOS with UNIT-ID = AP-1. Make
MU-1 of AM out-of-service using the command PUT-SWU-OOS with UNIT-
ID = MU-1. Make CMS2 out-of-service using the command PUT-SWU-OOS
with UNIT-ID = CMS2. Make CMS4 out-of-service using the command PUT-
24 C-DOT DSS MAX

SYSTEM LEVEL TESTS
SWU-OOS with UNIT-ID = CMS4. Now switch off the PSU of the APU copy 1
and check that the power alarm gets reported on OOD and printer. Switch on
the power supply, bring the AP-1, MU-1 of AM, CMS2 and CMS4 inservice
using similar commands as used above and check that the alarm gets cleared
on OOD and printer.
5.6.1.3. Power Supply Alarm Testing in BTU (Frame 1 from the Top)
Ensure that both the PSUs in slot no. 1 & 3 of bus 0 are ON. Switch off the
PSU of slot 1.
Check that the power alarm is reported on OOD and printer with id IFC1.
Now switch ON the PSU in slot 1 and check that the alarm is changed to
NORMAL on OOD and printer.
Switch OFF PSU of slot 3 in BTU. Check that the power alarm is reported on
OOD and printer with id IFC2. Now put it on and check that the alarm is
changed to NORMAL on OOD and Printer.
Repeat the above test for PSUs in slot no. 23 & 25. Here PSU alarms will be
raised with id IFC17 and IFC18 instead of IFC1 & IFC2 respectively.
5.6.2. Power Supply Alarm Testing In CM-XL Rack
CM-XL consists of 6 frames i.e. BTU-0, SSU0, SSU1, BTU1, SCU and APU in
that order from top.
5.6.2.1. Power Supply Alarm Testing in APU (Frame 6 from the TOP)
i) Switch off the Power Supply in slot 1. Wait for the PSU Alarm to be
raised on OOD/PRINTER with id AP-0. Switch ON the Power Supply.
Alarm should retire from ADP and it should change to NORMAL on
OOD/PRINTER. Repeat the test for PSU in slot no. 3 after ensuring
that PSU in slot no. 1 is ON.
ii) Switch OFF PSU in slot no. 23. PSU Alarm should be raised for AP-1
on ADP & OOD/PRINTER. Now switch on the power supply. Alarm
should change to NORMAL on ADP & OOD/PRINTER. Repeat the test
for PSU in slot no. 25 after ensuring that PSU in slot no. 23 is ON.
5.6.2.2. Power Supply Alarm Testing in SCU (Frame 5 from the top) :
i) Ensure that SSC-0 and SS-0 is INS-SBY. Now one by one, put SSC-0,
SS-0 and MU-0, OOS-OPR for MOD-NO : cm using MMI command
PUT-SWU-OOS. Switch unit alarms for these units will be raised on
OOD/PRINTER. Switch off power supply in slot 1 and wait for power
supply alarm for SSC-0 to be raised on OOD Printer. Switch ON the
Power Supply and observe that Alarm should change to NORMAL on
OOD/PRINTER. Make SSC-0, SS-0 and MU-0, INS-SBY one by one
using CRP command PUT-SWU-INS for MOD-NO: CM.
C-DOT DSS MAX 25

Chapter 5.
ii) Interchange the controllers SSC-0 & SS-0 to make them INS-ACT.
Now make SSC-1, SS-1 and MU-1 OOS-OPR for MOD-NO: cm and
wait for Switch Unit alarms to be raised for these units on
OOD/PRINTER. Switch off Power Supply in Slot 25 and wait for the
Power Supply Alarm for SSC-1 to be raised on OOD/PRINTER. Switch
ON the power supply and observe that Alarm should change to
NORMAL on OOD/PRINTER. Make SSC-1, SS-1 and MU-1, INS-SBY
one by one using CRP command. PUT-SWU-INS for MOD-No : CM.
Note : No alarm is generated for Power Supply units in slot no. 3 & 23.
5.6.2.3. Power Supply Alarm Testing in BTUs (Frame 1 & 4 from the top)
i) Switch off Power Supply in slot No. 1 of frame 1 and wait for the Power
Supply Alarm for IFC1 to be raised on OOD/PRINTER. Switch ON the
Power Supply and wait for the alarm to change to NORMAL on
OOD/PRINTER. When the Power Supply is switched off, alarm for CM
is also raised on ADP and retires for ADP when Power Supply is
Switched ON.
ii) After ensuring that Power Supply in Slot 1 of frame 1 is ON, repeat the
test as listed in (i) for Power Supply in Slot no. 3 of frame -1. Here,
Power Supply Alarm will be raised for IFC 2, instead of IFC1.
iii) Repeat the test as listed in (i) for Power Supply of Slot no. 23 of frame
1. Here Power Supply Alarm will be raised for IFC9.
iv) After ensuring that Power Supply of Slot No. 23 in frame 1 is ON,
repeat test (i) for Power Supply of Slot No. 25. Here Power Supply
Alarm will be raised for IFC10.
v) Repeat the test (i) to (iv) for Power Supplies in Slot No. 1,3,23 & 25 of
frame 4. Power Supply alarms will be raised for IFC17, IFC18, IFC25
& IFC26 respectively.
5.6.2.4. Power Supply Alarm Testing in SSUs (Frame No. 2 & 3 from the top)
i) Switch off Power Supply in slot No. 1 of frame 2 and wait for the Power
Supply Alarm for SWC1-0 to be raised on OOD/PRINTER. Switch ON
the Power Supply and wait for the alarm to change to NORMAL on
OOD/PRINTER. When the Power Supply is switched off, alarm for CM
is also raised on ADP and retires for ADP when Power Supply is
Switched ON.
ii) After ensuring that Power Supply in Slot 1 of frame 2 is ON, repeat the
test as listed in (i) for Power Supply in Slot no. 3 of frame 2. Here,
Power Supply Alarm will be raised for SWC2-0.
26 C-DOT DSS MAX

SYSTEM LEVEL TESTS
iii) Repeat the test as listed in (i) for Power Supply of Slot no. 23 of frame
2. Here Power Supply Alarm will be raised for SWC1-1.
iv) After ensuring that Power Supply of Slot No. 23 in frame 2 is ON,
repeat test (i) for Power Supply of Slot No. 25. Here Power Supply
Alarm will be raised for SWC2-1.
v) Repeat the test (i) to (iv) for Power Supplies in Slot No. 1,3,23 & 25 of
frame 3. Power Supply alarms will be raised for SWC9-0, SWC10-0,
SWC9-1 & SWC10-1 respectively.
5.7. SWITCH UNIT ALARMS
The following procedure should be repeated for all the copies of the following
controllers one by one :
TIC/TUC, TTC, ANN, TSC, SCIC, BMS, TGA, MFC, BPC, AP, SSC, CMS. In case,
SUM is equipped to provide CCS7 signalling, the test for corresponding TUC and
BPC (SU7) for both the copies should be done. Similarly if ISTU is equipped to
provide ISDN service, the test is to be repeated for ITC (TI) and ICC units.
Press the reset button of the “Standby” controller till the alarm is raised for that
controller. Check for reporting of the alarm on ADP/OOD/Printer. Make the unit
out-of-service by issuing a "FRC-SWU-OOS" command. Bring it inservice by issuing
a PUT- SWU-INS command for the controller and check that alarm is cleared.
C-DOT DSS MAX 27

Chapter 6.
Exchange Data Checks
6.1. LOCAL DATA
Check the exchange code using DISPL-XCOD commands. Also check the list of
directory nos. using DISPL-DIRNO command and their status using "DISPL-TRM-
STATUS" command.
Line type, Instrument type and facilities enabled for different subscribers (eg. STD
allowed, etc.) may be checked using DISPL-SUB command on sample basis. List of
reserved directory nos. may be checked using DISPL-DIRNO-RSRV command.
Details about different Hunt groups may be verified using DISPL-HGP command.
6.2. TRUNK & ROUTE RELATED DATA
Using DISPL-TGP command, check the IC, OG and BW trunk groups, type of line
and register signalling, the hardware used (2-wire physical/E&M/Digital),
allowing/barring of Trunk offer and Manual Hold facility, Prefix digits and Dial
tone feed on seizure option for IC trunk groups, rank of digit (ROD) and minimum
digits for seize forward for OG trunk groups, trunk group priority and category (to
determine routing and charging restrictions), for all the trunk groups.
Using DISPL-ALL-ROUT command, check the list of all route codes. Using DISPL-
TGP-ROUT commands display the routes associated with each trunk group. Also
check the characteristics of each route like route flag (which defines routing
restrictions) for different incoming routing categories, charge rate no., digit length
(maximum no. of digits including the Route code) and trunk group choices using
DISPL-ROUT-CHAR command.
6.3. CHARGING DATA
Check the data related to type of days in the charging calendar, time zones and
corresponding tariff classes for each type of day, charge rates for different tariff
classes and the charge units for different modes (eg. activation, de-activation, actual
usage etc.) of services. Check that the data complies with the data supplied by the
customer. Use the following commands for verification of the data :
EXCHANGE DATA CHECKS
DISPL-DAY-TYP (display type of day for different days of the year)

DISPL-TYP-DAY (display time slices and corresponding tariff classes
for all types of days)
DISPL-CRG-RTN (display charging information for different tariff
classes and charge rate numbers)
DISPL-SSRV-CRG (display charge units for different modes of a service
with a given service type).
DISPL-CHB-CRG (display the details of charge band association with
charge rate number).
C-DOT DSS MAX 29

Chapter 7.
Switching Function Check
7.1. TESTS ON LOCAL SUBSCRIBER LINES
i. Verify polarity of all 'a' (tip) and 'b' (ring) wires at the MDF. At 'a', there should
be -48V and at 'b', there should be GND potential.
ii. Make calls between two subscriber lines. Cover all the subscriber lines and
check the parameters like ringing, ring tripping and metering for each call.
iii. Give loop on a line and verify through command that its status becomes LLO
(Line Lock Out) after some time. Remove the loop from the line and verify that
its status becomes normal.
iv. Make calls to non-metered subscribers & check that metering is not done for
such calls.
v. Make calls from CCB lines & check that reversal is given on called party answer.
7.2. JUNCTION TESTING
Connect the junctions of the exchange in the network and perform the following
tests.
7.2.1. Incoming Calls to the Exchange
i. Set up an incoming call in each of the following cases :

• Called party does not answer during ringing. If clear forward is not
received from originating exchange for same reason; then after
about 480 secs., ringing should stop.
• Called party answers. Check for metering over junction when called
party answers (Reversal of potential or equivalent condition). In
case called party is of non-metered category, check for no metering
over junction when called party answers.
• When call is established, calling party disconnects first. Check that

called party receives parking tone and answer signal from the
incoming junction is removed.
SWITCHING FUNCTION CHECK
• When called party disconnects first, a clear forward is expected due
to CSH time out at originating exchange; if however clear forward
is not received for some reason then after about 480 secs, the called
party should become free.
• When called party disconnects first and reanswers before expiry of

CSH Time out (normally 60 seconds) supervision time, call should
continue.
• Called party is busy while the call is made then calling party should
get busy tone.
ii. Malicious Call :

Setup an incoming call to a local subscriber with malicious call tracing
facility. Flash during conversation and check the output message printout,
on OOD and printer.
iii. Blocking Condition :
Set blocking condition on incoming junctions (using PUT-TRM-OOS
command) and check that the blocking condition is returned to the
originating exchange.
iv. Trunk Offering :
Make call between two local subscribers. Setup an operator with trunk
offer facility on an incoming trunk. Check proper trunk offer signal
functioning.
v. On each incoming junction, make five successive calls and check that the
calls are successful.
vi. Answering Circuit Test :
On each incoming trunk group, select one junction and dial answering
circuit number. Answering circuit call should be successful. It is assumed
that the answering circuit number is already created for the exchange
using command 'CRE-SPL-NUM'.
7.2.2. Outgoing Calls from the Exchange
i. Make an outgoing call (not STD or ISD) and check that subscriber meter
increments properly. Check for immediate calling party release and
delayed (60 secs. time out) called party release.
ii. Repeat (i) above for STD and ISD calls also. In this case, as soon as
clearback is received, call is disconnected.
iii. Make an outgoing call (not STD or ISD) and check.
C-DOT DSS MAX 31

Chapter 7.
• When called party does not answer, calling party gets parking tone
after one min.
• When called party is busy, calling party gets busy tone.
• When call is made to non-metered number, calling party's meter

does not increment.
• When all outgoing trunks in a direction are made out of service

(using PUT-TRM-OOS or FRC-TRM-OOS command) calling party
gets congestion tone or announcement.
• When calling party dials incomplete number without dialling the

last digit, it gets parking tone after 5 secs., and the outgoing
junction is released.
iv. On each outgoing junction, make five successive calls and check that the
calls are successful.
v. Manual Hold :
From a local subscriber, make an outgoing call to MH operator (eg. 100).
Call should be successful and should not be disconnected unless the MH
operator disconnects.
vi. Answering Circuit Test :
On each outgoing trunk group, select one junction and give the command
TST-TRM ; TST-SET = 203 (answering circuit test) for the junction. The
test should be successful.
7.2.3. Operator Position Tests
7.2.3.1. 163 Tests

From any telephone line go off-hook and dial 163. The call should land on 163
telephone in the exchange. Operator should answer & give command TST-
TRM with TST-SET = 107 for the calling number. When the caller hears a
click sound, he should dial '0'. On operator's VDU, result should come
indicating loop current, resistance, dialling speed and make-break ratio.
7.2.3.2. Complaint Position 198
i. From a local subscriber, dial 198. Call should land on the complaint
position telephone and should not be metered when operator answers.
ii. From a local subscriber, dial xxx2198 (xxx = exchange code). Call should
land on the complaint position telephone and should not be metered when
operator answers.
32 C-DOT DSS MAX

iii. Try incoming call from some other exchange to complaint position (xxx
2198). Call should be successful and there should be no metering on
incoming junction when operator answers.
7.3. SUBSCRIBER FEATURES
The services are to be registered and invocation/control procedure is to be followed

as specified in Appendix-A at the end of the document.
7.3.1. Subscriber Controlled STD
i. Select a subscriber having "Subscriber controlled STD" feature. Select the

current access level to bar STD/ISD calls from subscriber and ensure that
no STD/ISD calls are passing from the subscriber.
ii. Select the current access level to allow STD/ISD calls and ensure that
STD/ISD calls from the subscriber are passing, STD/ISD calls from the
subscriber will be allowed in this case only if subscriber's access barring
parameter for STD/ISD calls is set for allowing them.
iii. Select the current access level to allow only 10X calls. Ensure that no
local, STD and ISD calls are passing from the subscriber. Only 10X calls
are getting through.
iv. Select the current access level to allow all calls. Now change the keyword
from subscriber telephone, and verify that the new keyword works in
selecting the new access level.
v. Repeat the tests for 90 level barring and verify for proper functioning.
7.3.2. Automatic Alarm
Select a subscriber having automatic alarm facility. Try to book an alarm for
future time using subscriber telephone. Ensure that alarm gets matured at
specified time. When subscriber answers, he should get proper
announcement.
7.3.3. Call Waiting Controlled by Called Subscriber
i) Select a number having call waiting called (CLD-CALL-WTD) facility.

This is a terminating facility.
ii) Establish a call in conversation phase from or to this number. Now
make one more call from some other telephone to this number. The
caller will get the ring back tone and this number will be fed zip tone
to inform that one more call is waiting.
iii) Replace the handset of the number getting the zip tone. First call will
be cleared and ringing current will be fed for the second call.
C-DOT DSS MAX 33

Chapter 7.
iv) If the party desires to continue with both parties then by giving Hook
Switch Flash, switchover will take place. Another Hook Switch Flash
will switchover again to the first party.
7.3.4. Diversion to a Selected Number (Follow Me)
i) Select a number having this facility

ii) Now activate this facility to divert this number to some other number.
iii) On lifting the handset, check that the number is having a warning Dial
Tone instead of the normal Dial Tone.
iv) Now dial this number from some other number. The call will not go to
this number but instead will go to the directed number.
7.3.5. Diversion Busy to a Selected Number
i) Select a number having this facility.

ii) Now activate this facility to divert the call to the specified number
when the subscriber is busy
iv) Make a call and keep the subscriber busy. Now from another
telephone, make a call to the busy subscriber and verify that the call in
diverted to the predefined number.
7.3.6. Diversion on No Answer to a Selected Number
i) Select a number having this facility.

ii) Now activate the facility, specifying the destination number.
iv) Make a call to this subscriber and do not answer. Wait for "Ring Time
Out". The call should be diverted to the destination number after "Ring
Time Out".
7.3.7. Hotline Without Time-Out
i) Select a number having hotline without time-out facility.

ii) Select the destination number at the time of activating the facility.
iii) On lifting handset, the call will go to the registered number.
34 C-DOT DSS MAX

7.3.8. Hotline With Time-out
i) Select a number having hotline with time-out facility.

ii) Select the destination number at the time of activation for facility
iii) On lifting handset and waiting for about 8(secs), the call will land on
the registered number.
Note : The Services 7.3.4, 7.3.5, 7.3.6 & 7.3.8 can be activitated with
destination number as upto ISD subject to the condition that the
current access level of the subscriber permits that level, being
selected for the destination number.
7.3.9. Calling Line Identity Presentation (CLIP) and Calling Line Identity
Restriction (CLIR)
The facility is used by the subscriber to know the caller. Also it may be used
by special callers eg., security agencies to hide the identity.
i) Subscribe the feature for A, with CLIP attachment to display the caller
identity.
ii) Ensure that ECN is implemented for Port A.
iii) Now make a call from B to A. The call is offered to A with the identity
of ‘B’, being displayed on the CLIP attachment of A.
iv) Now subscriber CLIR to B and repeat step (iii). The caller identity is
not displayed.
Note : In case of ISDN, additional attachment is not required as the feature is
inbuilt in the ISDN phone.
7.4. TESTING OF TONES/ANNOUNCEMENTS
i) Select a directory number with instrument type as DTMF with Dialling By

Equipment (DBE) facility.
ii) For testing of different tones in different BMs, dial the digits as listed in
Table 7.1.
iii) For testing of different Announcements, dial the digits as listed in Table 7.2.
Only English Language Announcements are listed but, when the desired
digits are dialled, corresponding Hindi or Regional Language Announcement
is also switched along with the English Announcement if the site is equipped
with the bi-lingual announcements.
C-DOT DSS MAX 35

Chapter 7.
7.5. TESTING OF RSU FUNCTIONS
At the sites where RSUs are being commissioned along with the main exchange or
separately, the following tests are to be performed to ensure proper switching of
calls in both the cases when PCM links are working between main exchange and
RSU as well as in case of its failure.
i) Verify that RBMSA configuration is created for Level 1 emergency services as
10X. If not created use the command MOD-RBMSA-CONFIG to create 100
with one subscriber as the alternate number.
ii) Dial 100 and verify that the call is landed on the 100 position of the main
exchange or in case of multi-exchange area, the call is landed on the 100
position as specified in the network.
iii) Create fault in the PCM links so that all the PCMs are down. RBM will be
configured in stand-alone mode. Now dial 100 and verify that the call
matures on 100 position of the RSU instead of being routed to the 100 of
main exchange.
iv) Ensure that local calls are switched properly. On dialling STD route codes,
the subscriber is connected proper Tone / Announcement to confirm that in
the absence of network connectivity, the subscriber is fed correct in-band
information.
iv) Restore the PCMs and repeat step (ii) again to verify that the RSU has come
up and providing network connectivity properly.
Table 7.1
Verification of various Tones
Sl. No. Digits to be dialled Expected Tone
1. * 683 xx 1 6 03 01 # Dial Tone
2. * 683 xx 1 6 03 02 # Busy Tone
3. * 683 xx 1 6 03 03 # Ring Back Tone
4. * 683 xx 1 6 03 04 # Number Unobtainable Tone
5. * 683 xx 1 6 03 05 # Call Routing Tone
6. * 683 xx 1 6 03 06 # Congestion Tone
7. * 683 xx 1 6 03 07 # Intrusion Tone
8. * 683 xx 1 6 03 08 # Distinctive Ring Back Tone
9. * 683 xx 1 6 03 09 # Transfer Dial Tone/ Warning Dial Tone
10. * 683 xx 1 6 03 10 # Not valid in 2_1_1_1
11. * 683 xx 1 6 03 11 # Positive Indication Tone
12. * 683 xx 1 6 03 12 # Action Fail Tone
13. * 683 xx 1 6 03 13 # Special Information Tone
14. * 683 xx 1 6 03 14 # Zip Tone
36 C-DOT DSS MAX

Sl. No. Digits to be dialled Expected Tone
15. * 683 xx 1 6 03 15 # Pay Tone
16. * 683 xx 1 6 03 16 # Continuous Test Tone
17. * 683 xx 1 6 03 17 # Slow Interrupted Tone
18. * 683 xx 1 6 03 18 # Fast Interrupted Tone
19. * 683 xx 1 6 03 19 # Very Slow Interrupted Tone
20. * 683 xx 1 6 03 20 # Hold Tone
21. * 683 xx 1 6 03 21 # Parking Tone
22. * 683 xx 1 6 03 22 # Silence Tone
23. * 683 xx 1 6 03 23 # Test Tone
24. * 683 xx 1 6 03 24 # MF Tone
Note :
(i) Use an instrument having DTMF facility. In case of a Rotary Telephone,
replace 1 in place of *. No need to dial any digit in place of # in the end.
(ii) xx : BM-NO with possible values as 01 to 16 in MAX-L and 01 to 32 in MAX-
XL
Table 7.2
Verification of various announcements
Sl. No. Digits to be dialled Expected Announcements
1. * 683 xx 1 1 03 01 # The lines to the route dialled by you are out of order. Kindly try
after some time.
2. * 683 xx 1 1 03 02 # All the lines to the route dial led by you are busy. Kindly try after
sometime.
3. * 683 xx 1 1 03 03 # There is no route corresponding to the digits dialled by you. Kindly

confirm the number from directory or consult enquiry operator.
4. * 683 xx 1 1 03 04 # Route code you have dialled has been recently changed. Kindly
5. * 683 xx 1 1 03 05 # The number you have dialled is not working any more. Kindly
6. * 683 xx 1 1 03 06 # The line to which you have dialled is presently out of order..
7. * 683 xx 1 1 03 07 # This is the alarm call booked by you. We hope you found the facility
useful.
8. * 683 xx 1 1 03 08 # No one is presently available on this telephone to take the call.
9. * 683 xx 1 1 03 09 # Kindly wait you are in a queue.
10. * 683 xx 1 1 03 10 # This facility is not available on your telephone.
11. * 683 xx 1 1 03 11 # Country code dialed is not available. Please contact trunk
exchange.
C-DOT DSS MAX 37

Chapter 7.
Sl. No. Digits to be dialled Expected Announcements
12. * 683 xx 1 1 03 12 # Silence Tone
13. * 683 xx 1 1 03 13 # This telephone is Out of Service due to non payment of Telephone
Bills. Please contact the Accounts officer for details.
14. * 683 xx 1 1 03 14 # All the line to this subscriber are busy. Kindly try after some time.
15. * 683 xx 1 1 03 15 # This telephone number does not exist.
Note :
(i) Use an instrument having DTMF facility. In case of a Rotary Telephone
replace * by 1. No need to dial any digit in place of # in the end.
(ii) xx : BM-NO with possible values as 01 to 16 in MAX-L and 01 to 32 in MAX-
XL
38 C-DOT DSS MAX

Chapter 8.
ISDN & CCS7 Testing Within the

Exchange
8.1. TESTING OF ISDN SERVICES
This chapter has been organised in three different sections to ensure complete
testing of ISDN services within the exchange as well as across the network. The
testing of ISDN services require the following add-on equipments.
1. 2 nos. of Network Terminator (NT)
2. 2 nos. of Terminal Adapter (TA)
3. 2 nos. of IBM compatible PC with add-on data cards
4. Connecting U and S bus cables.
A reference test set up for acceptance testing of ISDN services is shown in figure
8.1. Create the Directory Numbers with service profile as “DIGITAL” subscribers,
as explained in the document “Exchange Operations”. Now the tests on the interface
can be performed.
8.2. ISDN U-INTERFACE TESTING
The U-Interface (LT) in C-DOT DSS confirms to 2BIQ line coding and Embedded
Operational Channel (EOC) functions are part of 2BIQ line coding. The EOC
functions are used to support the functional testing on LT in the exchange as well
as NT in the customer premises up to S-Interface. The integrated tests are
sufficient to test and isolate the faults in the interface.
8.2.1. Test Procedures for ISDN U-Interface
The CRP command TST-TRM is used to perform the tests on the U-interface
in C-DOT DSS. On execution of CRP command, the following parameter
entry sheet is displayed on the screen.
RTN-COD : G
RPT-FMT : B
REPEAT : NO
TML-TYP : LINE
Chapter 8
TST-SET : 60X
TEN : Circuit Number
DIRNO. : Directory Number
Only one of the two parameters as TEN or DIRNO, should be specified at a
time. The command can be executed after defining the parameter values. The
successful execution of the tests confirm that the line is fault free.
The valid value for the test sets are 607, 608, 609 and 610. The details of the
test sets are listed. The test set 607 is used to test the exchange side i.e. (LT)
and test set 608 is used to verify the customer end up to S-Interface.
The test sets 609 is used to monitor the characteristics of cable pair. The
parameters are measured and absolute values are displayed. The test is
executed subjected to the condition that the TTC card is INS.
8.2.2. Activation/Deactivation from LT
It is possible to activate to deactivate the interface from the exchange side.

FRC-TRM-OOS (to deactivate the interface from LT)
TML-TYP :
TEN :
DIRNO :
The command can be executed after defining the parameter values. The
successful execution of the command confirms that the interface has been
deactivate.
FRC-TRM-INS (to activate the interface from LT without tests)
TML-TYP :
TEN :
DIRNO :
The command can be executed after defining the parameter values. The
successful execution of the command will result in activation attempt, being
initiated from LT. However, in case of fault of LT or NT, the interface will be
deactivated with its status, marked as OOS-SO.
PUT-TRM-INS (to activate the interface from LT after successful testing)
TML-TYP :
TEN :
DIRNO :
The command can be executed after defining the parameter values subject to
the condition that the TLC is already created. The successful execution of the
command confirms that there is no fault in LT. The line status is marked as
40 C-DOT DSS MAX

ISDN & CCS7 TESTING WITHIN THE EXCHANGE
INS-FREE. In case of fault in DLL or NT, the interface will be deactivated
with its status, marked as OOS-SO.
8.2.3. Procedure for Testing of ISDN Termination Card
In case, more than 50% interfaces corresponding to a Interface Card is

reported as faulty, it is advised to perform the tests on the BRL card. The
card can be tested using CRP command TST-TRML-CARD with parameters
as :
RTN-COD : G
RPT-FMT : B
REPEAT : NO
TML-CRD-TYP : BRI
TST-SET : 605 or 606
CARD-SLOT :
The status of the BRL card can be displayed by using CRP command DISPL-
TRML-CARD-STATUS with parameter as :
TML-CRD-TYP : BRI
CARD-SLT :
The status of the card can be displayed as INS-NRM, INS-FRC or OOS-SE.
INS-NRM : Card has been brought INSERVICE after
performing the complete tests, successfully.
INS-FRC : The card has been made INSERVICE, forcibly.
OOS-SE : The card is faulty.
The status of a BRL card can be modified to “Out of Service” by using CRP
command FRC-TRML-CARD-OOS. Similarly, its status can be modified to
“In service” by using CRP command FRC-TRML-CARD-INS without testing
or PUT-TRML-CARD-INS after successful testing.
8.2.4. Creating a Reference Test Circuits (TLC) in C-DOT DSS
The TLC is created to simulate the functions of LT when tests set 608 is
executed to verify the functioning of NT up to S-Interface. Similarly, it
simulates the functions of NT to test the LT in the exchange. This helps in
integration of all the functional requirements of testing of ISDN-Interface in
C-DOT DSS as the tests are simulated in conformance to actual functional
requirement. This avoids the use of any additional test equipment to isolate
and locate the fault.
Sufficient checks are also incorporated to verify the sanity of TLC, time to
time. This possible by testing the TLC at the time of creation itself. The TLC
C-DOT DSS MAX 41

Chapter 8
is functionally tested in totality before making it available for testing of other

ISDN-interfaces in C-DOT DSS.
The TLC is created by using CRP command CRE-TST-CKT with parameters
as :
TLC-TEN :
TST-TEN :
The basic requirements are :
1. The TLC-TEN should be the first free circuit (i.e. not associated with
DIRNO) of any BRL card.
2. The status of the BRL card should be INS-NRM. This can be ensured
by executing the command TST-TRML-CARD
3. The TST-TEN should be any free circuit (i.e. not associated with
DIRNO) of the same BRL card or any other BRL card in the ISTU.
After executing the command, the TLC is created and subjected to functional
tests by using the TST-TEN as reference circuit. Once the functional tests are
executed and passed, the status of the circuit is marked as INS-FREE which
be verified using command DISPL-TRM-STATUS. In case of failure, the
status of the circuit is marked as OOS-SE. In such cases, it is advised to
delete the TLC and create it after changing the BRL card. Alternatively, it is
possible to create the TLC on any alternative BRL-Card.
Procedure to Delete a TLC
The TLC can be deleted using CRP command DEL-TST-CKT with
parameters as :
TLC-TEN :
The mandatory requirement of deleting the test circuit is that the BRL card
should be made OOS-OPR using CRP command FRC-TRM-CARD-OOS.
8.2.5. How to Observe the Status of ISDN-Interface ?
DISPL-TRM-STATUS (to monitor the status of interface)

STAT-TRM :
TML-TYP :
TEN :
DIRNO :
On execution of the above command, the current status of the U-interface is
displayed which may be as:
OOS-SO : Fault may be in LT, DLL or NT
42 C-DOT DSS MAX

OOS-SE : Fault is confirmed in LT
INS-FREE or : The interface is activated upto NT and free to
INS-FREE provide service.
CP-BUSY : The interface is busy and providing service.
OOS-SUS : It is transient status and valid for internal use by
the system itself. The status of the terminal is
made OOS-SE or OOS-SO after verification of fault
condition. It the fault is found to be transient in
nature, the status of line is marked as INS-FREE
and available to the subscribers to provide the
service.
8.2.6. Summary Sheet of the CRP Commands for O&M of ISDN Interface in
C-DOT DSS
1. 1. CRE-TST-CKT To create a test circuit to simulate the functional of LT
and NT for functional testing of ISDN-interface.
2. DISPL-TRM-STATUS To display the status of the interface
3. FRC-TRM-OOS To deactivate the interface from the exchange
4. FRC-TRM-INS To activate the interface from the exchange without
testing
5. PUT-TRM-INS To activate the interface from the exchange after
successful testing of LT
6. TST-TRM To test the interface as LT as well as NT up to S-
Interface at the customer premises
7. DISPL-TRML-CARD-STATUS To display the status of the card
8. FRC-TRML-CARD-OOS To make the card out of service for replacement or as a
mandatory requirement to delete the test circuit.
9. FRC-TRML-CARD-INS To make the card in service forcibly i.e. with out
performing the detail tests
10. PUT-TRML-CARD-INS To make the card in service after performing the detail
tests on the card as well as all the 8 LTs.
11. TST-TRML-CARD To test the card
12. DEL-TST-CKT To delete the test circuit if it is faulty
8.3. ISDN BEARER SERVICES
Using the setup as shown in figure 8.1, different calls are made to test ISDN to
ISDN, ISDN to PSTN and PSTN to ISDN interworking tests. The details of the
tests are given in the following table. The successful tests will ensure the
C-DOT DSS MAX 43

Chapter 8
ISDN&PSTN interworking across the network. “Packet Mode” Bearer services need
not be tested as they are not available in C-DOT DSS at present but likely to be
available in immediate future.
Test Sheet for Teleservices in case of ISDN

S. No Test Description Expected Result / Response
1 ISDN to ISDN Call
(i) Basic ISDN to ISDN local Call The calls should be successful
(ii) ISDN to ISDN Call through DECADIC routes
(iii) ISDN to ISDN Call through MOD-R2 route
(iv) ISDN to ISDN Call through CCS7 route
2 Two Simultaneous ISDN Calls
(i) The calls are originated from two ISDN subscribers The calls should be successful
A1 & A2 on the same ISDN line and terminated on
the two ISDN subscribers B1 & B2 on another ISDN
line.
The calls should be successful
(ii) The calls are originated from two ISDN subscribers
A1 & B1 on the different ISDN lines and terminated
on the two ISDN subscribers A2 & B2 on different
ISDN lines.
3 ISDN Calls with in the Interface
The two ISDN phones are connected on the same interface The call is offered to the second
using multi-drop connector . The call is made from B by ISDN phone on the same line
dialling its own directory number. and connection is established on
answer.
4 Two Simultaneous ISDN Calls with same and

different Bearer Services.
The calls are originated from two ISDN subscribers

A1(SPEECH) & A2 (3.1 KHz) on the one ISDN line and
terminated on the two ISDN subscribers B1(SPEECH) &
The calls should be successful
B2 (3.1KHz) on another ISDN line. (A1&B1 are PHILIPS
ISDN Phones and A2&B2 are C-DOT TAs).
44 C-DOT DSS MAX

Test Result Sheet for G3 FAX Services

S. No Test Description Expected Result/Response
1 ISDN to ISDN using TA
The test set up is made by connecting two C-DOT TAs on The call should be successful
lines A & B. The Analog Ports at TAs, are configured as between two FAX machines
FAX ports. The call is made from FAX connected to A , by and the FAX transmission is
dialling the number B . also through.
2 ISDN to Analog
The test set up is made by connecting C-DOT TA on ISDN The call should be successful
line A and its Analog Port is configured as FAX port. A and the FAX transmission is
FAX machine is connected to TA of ISDN line A and also through.
another FAX machine is connected to Analog Line C. The
call is made from FAX connected to A , by dialling the
number C .
3 Analog to ISDN
The test set up is made as explained in Step-2. The call is The call should be successful
made from FAX connected to C, by dialling the number of and the FAX transmission is
ISDN line A. also through.
Test Result Sheet for Misc. Services related to ISDN

S. No. Test Description Expected Result / Response
1 ISDN Call to Level 1 Services
Level 1 positions , 198 as non metered services and 131 as
metered services are already created in the Exchange.
A call is made from ISDN Phone A to 198.
A call is made from ISDN Phone A to 131. The call is put through
successfully without
incrementing meters.
The call is put through
successfully, incrementing the
meter of A.
Test Result Sheet for Bearer Services

S.No. Test Description Expected Result / Response
1 File Transfer Using PC ( 64 Kbps UDI data call )
The test set up is made by connecting two C-DOT TAs on The call is put through
ISDN lines A & B. The TAs are configured as Synchronous successfully with bearer
DTEs. The PCs are connected at the asynchronous data service as “ 64 Kbps UDI “ and
ports .The call is made from A by dialling the number B, the file is transferred from
from the keypad. terminal A to B.
C-DOT DSS MAX 45

Chapter 8
46 C-DOT DSS MAX

8.4. ISDN SUPPLEMENTARY SERVICES
In C-DOT DSS, all the PSTN feature available for analog subscribers, are also
available to ISDN subscribers except multi-party services. For details of
supplementary services, refer Annexure-A of this document. The section 7.3 can
also be used for testing of the common features on ISDN subscribers. The ISDN
specific supplementary services are tested as per the procedure, explained
subsequently in this section.
Even though the supplementary services DDI and SUB addressing are supported in
C-DOT DSS and validated by TEC for its functioning, it is not feasible to test at site
due to unavailability of suitable test equipments. The supplementary services as
CD, UUS, CUG, CONF and 3 PTY are not supported in C-DOT DSS at
present.
8.4.1. Connected Line Identification Presentation (COLP) and Connected

Line Presentation Restriction (COLR).
This facility is used by the subscriber to know that who is the ultimate
destination, being connected against his dialled number. This is important in
case of diversion when the call is being diverted to some other number.
i) A has subscribed COLP
ii) B has subscribed to diversion and diversion is activated with
destination directory number ‘C’.
iii) A calls to B but the call land on C.
iv) Now C answers the call and A gets the information on the LCD display
that the connected number in C and not the dialled number B.
8.4.2. Advice of Charge (AOC)
This facility is used to know the charge for the call as it is the case of 16 KHz
metering pulse in case of Analog line.
i) Subscribe the facility AOC-E on A.
ii) Make a call from A to the network.
iii) Release the call after successful conversation and verify the total
charge units being displayed on the LCD display.
iv) Now subscribe AOC-D on A and repeat (ii) and (iii). The charge units
are periodically updated on the LCD display with periodicity defined
and controlled by a system parameter AOC-D timer.
C-DOT DSS MAX 47

Chapter 8
8.4.3. Terminal Portability (TP)
This feature is used by the subscriber to suspend the call and resume it later
on.
i) Subscribe the facility TP on A.
ii) Make a call to B
iii) Press “SUSPEND” on the ISDN terminal equipment.
iv) The call is suspended. Now remove S-BUS and reconnect. Press
“Resume” and A is again connected to B.
8.5. TEST OF ISDN SERVICES ON CCS7
Establish a CCS7 link between two new technology exchanges. Ensure that the
CCS7 link follows the National Standard link USERPART=ISUP, error correction
method = BASIC, Signalling point code = linear codes allotted by TEC, minimum
signalling link = 2 for one direction (link set).
A protocol analyzer should be connected across both the signalling data links for
observation of MTP and ISUP messages.
8.5.1. Signalling Link Management
Note: It is assumed that a linkset with 2 links has already been created and
the links are activated and available. The protocol analyzer is set in the
“MTP Monitor” mode.
8.5.2. Normal alignment of signalling links
a) Check the status of the both signalling links through DISPL-LS-STS.

It should be activated and available. In the activated state, SLTM and
SLTA messages should be seen on the MTP monitor from both the
connected nodes.
b) Deactivate one of the links by giving MOD-LS-STS command so that
the status of the link is now shown to be deactivated via the DISPL-
LS-STS command.
c) Now, activate the same link by giving MOD-LS-STS command after
making sure that the MTP messages are being seen on the analyzer.
Store the MTP messages from the moment when the link was in
deactivated state. Calculate the value of the “Normal Alignment”
timers from the time stamps of the level2 messages. Refer to the annex
of ITU-T Rec. Q.703 for the definition and the value of the timers.
Generally the nominal values are taken. The link should successfully
become activated and available.
48 C-DOT DSS MAX

8.5.3. Emergency alignment of signalling links

It should be activated and available. In the activated state, SLTM and
connected nodes.
b) Deactivate both the links one by one by giving MOD-LS-STS command
so that the status of the links is now shown to be deactivated via the
DISPL-LS-STS command.
c) Now, activate one of the links by giving MOD-LS-STS command after
making sure that the MTP messages are being seen on the analyzer.
Store the MTP messages from the moment when the link was in
deactivated state. Calculate the value of the “Emergency Alignment”
timers from the time stamps of the level2 messages. Refer to the annex
of ITU-T Rec. Q.703 for the definition and the value of the timers.
Generally the nominal values are taken. The link should successfully
become activated and available.
8.5.4. Activation/Deactivation of signalling links
This gets tested in tests 8.5.2 & 8.5.3 above.
8.5.5. Load sharing within a link set

It should be activated and available. Else, make the link/s active by
giving MOD-LS-STS command. In the activated state, SLTM and
connected nodes.
b) Run CCS7 call traffic between the nodes, if not so already. Start the
LNK-REP traffic report. Let the traffic run for about 15 minutes.
c) Observe the LNK-REP. The number of octets received and transmitted
should to roughly the same for each of the two links. This confirms load
sharing between the links.
8.5.6. Changeover and changeback
a) In the presence of ISUP call traffic or a specially made call, deactivate

one of the two links to initiate changeover of the messages from this
link to the other link. None of the calls should get cut.
b) Now activate this link (this is changeback) and repeat the case by
deactivating the other link while maintaining the calls. None of the
calls should get cut even now.
C-DOT DSS MAX 49

Chapter 8
8.6. SIGNALLING CHECK
8.6.1. Bothway Circuit Selection
Create a BW TGP with 4 circuits and associate it with CCS7 route. This
route connects exchange A & B. The point code for exchange A is X1 and B is
X2, where X1 > X2. Then for all OG calls from exchange A even circuits will
be seized, but if both the even circuits are busy and another call is
successfully completed by seizing odd circuit.
8.6.2. Enbloc Operation
a) Keep min-dgt-szfd parameter value at the ISUP TGP equal to the

number of digits (dgt-len) on the route. This will make all the address
digits to be filled in the IAM message itself.
b) Now in the presence of ISUP call traffic, observe the ISUP message
flow. Only IAM messages for the calls originating from the C-DOT
switch should be seen, i.e., no SAM messages should be seen.
8.6.3. Overlap operation
a) Keep min-dgt-szfd parameter value at the ISUP TGP less than the
number of digits (dgt-len) on the route. This will make only some of the
initial address digits to be filled in the IAM message. The rest will be
in SAM messages with one digit per message.
b) Now in the presence of ISUP call traffic, observe the ISUP message
flow. Now, in addition to the IAM messages SAM messages should also
be seen for the calls originating from the C-DOT switch.
8.6.4. Blocking & Unblocking of speech channels
a) Deactivate both the links one by one by giving MOD-LS-STS command

so that the status of the links is now shown to be deactivated via the
DISPL-LS-STS command.
b) See the status of the speech circuits via the DISPL-BLK7-STS
command. The blocking status should be “Locally Blocked.”
c) Now activate one of the links by giving MOD-LS-STS command so that
the status of the link is now shown to be activated via the DISPL-LS-
STS command.
d) See the status of the speech circuits via the DISPL-BLK7-STS
command. The blocking status should be now be “Not Blocked.”
50 C-DOT DSS MAX

8.7. CHECK FOR ANALOGUE SUBS FACILITIES
Check outgoing only, incoming only, malicious calls identification, hot line etc.
Remarks : MCI should be verified with CLIP, CLIR etc.
C-DOT DSS MAX 51

Chapter 9.
Testing of Spare Cards
9.1. CARD TESTING
All the spare cards received at the site should be checked.

Spare card testing can be divided in three parts - Testing of BM/LM related spare
cards, IOP related spare cards & CM related spare cards.
9.2. TESTING OF BM/LM RELATED CARDS
Testing of BM/LM related spare cards can be divided into the following -
The BM/LM related spare cards can be tested by first making a system card of that
type OOS-OPR (out-of-service operator). Replace the system card with a spare card.
Using CRP command, the spare card can be tested. After testing, the spare card
should be removed & the system card should be put back. Using command, the
system card should be again brought into service.
9.2.1. Testing of Cards in Controller Complex having duplicate copies
The following spare cards can be tested using the procedure given in this
section and equipage details in Fig 9.1 (A) to 9.1 (F).
CPU, BPC or HPC, TME or BME, TSC, TSM, TSS, or ETS, TSI; HMS or
MSC & MSD; TIC, SPC, TUI, TUC, BPC in SUM, ITC and ICC in ISTU.
i. Say CPU, BPC or HPC card is to be tested.
Issue command PUT-SWU-OOS for the standby copy of BP. Against
UNIT-ID give BP-0 or BP-1 whichever is standby. This will make that
copy OOS-OPR.
ii. Now replace the system level card by spare card. Issue command DGN-
SWU with the UNIT-ID same as that given in step 1. DGN-SWU
command will diagnose the card & indicate the health status of the card.
Diagnostic will pass in case of good card.
52 C-DOT DSS MAX

TESTING OF SPARE CARDS
=======================================================
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26
P T T T T T T T T T S T T T S T T T T T T T T P
S C C C C C C C C I P U U I P C C C C C C C C S
U C C I I C C U
I OR OR I
I I
S S
P P
NOTE: 1 TC MAY BE LCC, CCM, TWT OR E&M

2 IN CASE OF TU4 AS ATU IN BM, SLOT 24 WILL BE TTC.
FIG. 9.1A
ANALOG TERMINAL UNIT (ATU) CONFIGURATION
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26
P D D D D T T T T D D D D P
S T T T T U U U U T T T T S
U S C S C C I I C S C S C U
I Ø Ø 1 1 2 2 3 3 I
FIG. 9.1B
DIGITAL TERMINAL UNIT (DTU) CONFIGURATION
\DESIGN\DSSMAX\DSSMX-AT\DSSATATU
C-DOT DSS MAX 53

Chapter 8
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26
P P L L L L L L L L I I I I I I L L L L L L L L
S S C C C C C C C C T C I I C T C C C C C C C C
U U 1 2 3 4 5 6 7 8 C C C C C C 9 10 11 12 13 14 15 16
1 2 Ø Ø Ø 1 1 1
LC BRL OR PRL CARDS
NOTE : IIC CARDS ARE REQUIRED ONLY IN CASE OF CONCENTRATION OF ISTU
FIG. 9.1C
ISTU CONFIGURATION
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26
P P B S S S S H T T T T H S S S S B P P
S S M H H H H P U U U U P H H H H M S S
U U E M M M M C C I I C C M M M M E U U
1 2 1 2 3 4 OR OR 5 6 7 8 4 3
B B
P P
C C
SHM #7 PROTOCOL HANDLER CARD
NOTE: (i) WITH BPC, ONLY SHM1, 2, 3, AND 4 CAN BE EQUIPPED.

(ii) HPC IS USED TO SUPPORT SHM 1 TO 8 AND HIGHER MESSAGE PROCESSING CAPABILITY.
FIG. 9.1D
#7SU CONFIGURATION
\DESIGN\DSSMAX\DSSMX-AT\DSSATDCO
54 C-DOT DSS MAX

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26
P B H H B P
S M P P M S
U E C C E U
II OR OR II
B B
P P
C C
NOTE: HPC USED TO SUPPORT 800K BHCA
FIG. 9.1E
BASE PROCESSOR UNIT (BPU) CONFIGURATION
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26
P T M M S A M M T T T T T T T T M M A S M M T P
S G F F C F S S S S S S S S S S S S F C F F G S
U A C C I B D C I M C S S C M I C D B I C C A U
II C C II
OR OR
H H
M M
S S
NOTE : (i) REPLACE TSS CARDS BY ETS CARDS IN CASE OF REMOTE BASE MODULE (RSU)
(ii) MSC AND MSD ARE REPLACED BY HMS FOR 800K BHCA
FIG. 9.1F
TIME SWITCH UNIT (TSU) CONFIGURATION
\DESIGN\DSSMAX\DSSMX-AT\DSSATDTS
C-DOT DSS MAX 55

Chapter 8
iii) Remove the spare card from the system & put back the original system
card. Issue command PUT-SWU-INS for the card with UNIT-ID same
as that mentioned in step 1 to bring the system card back into service.
Now for testing of other cards step 1 to step 3 is to be repeated. For UNIT-ID
to be given for each card, use table 9.1. Say for testing of MSD and MSC
cards UNIT-ID will be BMS-0 or BMS-1.
Table 9.1
Sl. No. UNIT-ID CARDS TESTED
1. TSC TSC
TSM
TSS or RTS/ETS
TSI
2. BMS MSC } or HMS

MSD }
3. TIXX TIC* }
(XX = 01 to 16) SPC } or TUC*
TUI
TUI }
4. BP BPC or HPC in BM-XL

CPU & BIC in BM-L
5. MU BME in BM-XL
BID & TME in BM-L
* TIC is used in Analog TU and TUC is used in Digital TU.
9.2.2. Testing of MFC & TGA Cards
i. Issue command FRC-SRV-OOS with SRV-TYP = MF for a system level

MFC card & SRV-TYP = TONE for TGA card.
ii. Now replace the system level card by the spare card to be tested. Issue
command TST-SRV with SRV-TYP same as that mentioned in step 1. In
case of MFC card, specify TST-SET = 301 & in case of TOGC card, specify
TST-SET = 304. Result of the test will indicate health of the spare card.
iii. TOGC (i.e. TGA) card can also be checked using dialling by equipment no.
facility. Issue command PUT-SRV-INS for the TOGC card with SRV-TYP
= TONE to bring it inservice. Using MOD-SUB-FAC command, assign the
originating facility of DIALLING-EQPT to a subscriber (preferably a
DTMF subscriber). Dial appropriate digits as given to Table 7.1 & verify
56 C-DOT DSS MAX

whether correct tone is switched or not. After testing is complete, issue
command FRC-SRV-OOS with SRV-TYP = TONE to make the card OOS-
OPR.
iv. Remove the spare card from the system and put back the original system
card. Issue command PUT-SWU-INS for the card with UNIT-ID same as
that mentioned in step 1 to bring the system card back into service.
9.2.3. Testing of ANNC Card
i. Issue command FRC-SWU-OOS with UNIT-ID = ANNC.

ii. Replace the system level ANNC card by the spare card.
iii. Issue command PUT-SWU-INS with UNIT-ID = ANNC to bring the card
inservice. Using MOD-SUB-FAC command, assign the originating facility
of DIALLING-EQPT to a DTMF subscriber. Dial appropriate digits as
given in Table 7.2 & verify the announcement.
After announcement are checked, repeat step 1.
iv. Remove the spare card from the system & put back the original system
card. Issue command PUT-SWU-INS with UNIT-ID = ANNC to bring the
original system card inservice.
9.2.4. Testing of Digital Trunk (DTS & DTC) Cards
i. Issue command FRC-TRML-CARD-OOS for a Digital Trunk in the

system.
ii. Replace the system level DTS or DTC card by the corresponding spare
card to be tested.
iii. Issue command TST-TRML-CARD with TST-SET = 401 in case spare DTS
card is to be tested, & TST-SET = 402 in case spare DTC card is to be
tested. The result will indicate health of the spare card.
card. Issue command PUT-TRML-CARD-INS to bring the system level
digital trunk inservice.
9.2.5. Testing of Line & Analog Trunk Cards (LCC, CCB, TWT, EMF)
i. Issue command FRC-TRM-OOS with TML-TYP = LINE in case of LCC or

CCB card and TML-TYP = TRK in case of TWT or EMF card. In this
command while specifying TEN or DIRNO, cover all the 8 circuits of the
card so that all the circuits become OOS-OPR.
ii. Replace the system level card by the spare card to be tested.
C-DOT DSS MAX 57

Chapter 8
iii. Issue command TST-TRM with TST-SET = 103 in case of LCC or CCB or
TST-SET = 202 in case of TWT or EMF card. The result of the test will
indicate health of the circuits in the spare card.
level card. Issue command PUT-TRM-INS with TML-TYP = TEN or
DIRNO same as that mentioned in step 1 above.
9.2.6. Testing of Digital/ISDN Line Cards (Only at the sites where ISDN is
equipped).
i) Issue the command FRC-TRML-CARD-OOS command with CARD-

TYP=BRI and also specify the slot number,
ii) Replaces the system level card by the spare level card to be tested.
iii) Issue command PUT-TRML-CARD-INS with other parameters as
defined in (i). The result of the command should display the status of
the card as INS-NRM.
NOTE : Same procedure is valid for testing of BRL and PRL cards with only
difference that CARD-TYP should be specified as PRI.
9.2.7. Testing of CCS7 Signalling Link (SHM) Card in SUM
The SUM cards are equipped in SUM which is equipped in one of the BMs in
the main exchange Irrespective of the capacity of the exchange, only one
SUM is equipped.
The SHM card can be tested by repeating the steps (i) to (iii) of 8.2.6 with
only difference that the CARD-TYP will be PHC.
9.2.8. Testing of TTC Card
i) Issue command FRC-SWU-OOS with UNIT-ID = TTC.

ii) Replace the system level TTC card by the spare card to be tested.
iii) Issue command PUT-SWU-INS with UNIT-ID = TTC to bring the card
inservice.
iv) Select a good working line circuit & issue the command TST-TRM with
TST-TRM with TST-SET = 103 (exchange side tests), TML-TYP =
LINE for the line circuit. The report should display the capacitance
value measured..
v) Now ensure that a good telephone of line capacitance as 1.8 uf is
connected to the line. Issue command TST-TRM with TST-SET = 102
(outside plant open loop Test) & RPT-FMT = D (detailed report
format). The test should pass.
58 C-DOT DSS MAX

vi) 162 tests
Connect a telephone (rotary or DTMF) to a line port. From the
telephone, dial 162. RBT should be fed. Handset should be replaced
and to be lifted again after about 20 secs. Continuous tone should be
fed indicating that line insulation tests have passed.
Now handset should be replaced. Ring should be fed (for bell
adjustment). Handset should be lifted. After about 5 secs. continuous
tone should be fed indicating that loop current test has passed. Now '0'
should be dialled if telephone is rotary, otherwise a sequence of digits 1
2 3 4 5 6 7 8 9 * 0 # should be dialled if the telephone is DTMF.
Continuous tone should be fed indicating that dial test has passed.
Conduct the test both for a rotary and a DTMF telephone.
vii) Repeat step (i). Remove the spare TTC card from the system & put
back the original system card. Repeat step (iii).
9.2.9. Testing of Power Supply Cards (PSU I & PSU II)
PSU I cards are used in TUs of BM/LM & PSU II cards are used in BPU or
TSU of BM.
9.2.9.1. Testing of PSU I Cards
i) Switch off one PSU I card of a TU. Power alarm should be reported on
OOD/Printer & ADP.
Replace the system level PSU I card by the spare card to be tested.
ii) Switch on the spare PSU I card. Power alarm should get cleared on
OOD/Printer & ADP.
iii) Switch off the system PSU I card in the other copy of the same TU.
TICs/TUCs of the TU should remain inservice & lines/trunks of the TU
should keep working. Now switch on the system PSU I.
iv) Now switch off the spare PSU I in the system. Remove the spare PSUI
card put back the original system card & switch it on.
9.2.9.2. Testing of PSU II Cards
i) Using INTCHG command for different cards, make all copy 0 cards in
TSU active & copy 1 cards in TSU standby. The cards for which
INTCHG command in TSU may be required are TSC, BMS & SCIC.
ii) Now using PUT-SWU-OOS command, make BMS-1, SCIC-1 & TSC-1
OOS-OPR. For equipped MFC cards in copy 1 (card slots 22 & 23 of
TSU), use command FRC-SRV-OOS with SRV-TYP = MF to make
them OOS-OPR.
C-DOT DSS MAX 59

Chapter 8
iii) Switch off copy 1 PSU II (card slot 25) in TSU. Power alarm should be
reported OOD/Printer & ADP. Replace the system level PSU II card by
the spare card to be tested.
iv) Switch on the spare PSU II card. Power alarm should get cleared from
OOD/Printer & ADP.
v) Using PUT-SWU-INS command, bring BMS-1, SCIC-1 & TSC-1
inservice. Using PUT-SRV-INS command, bring copy 1 equipped MFC
cards (in card slots 22 & 23 of TSU) inservice.
vi) Repeat step 2. Remove spare PSU II card from the system & put back
the original system card. Repeat step 5.
9.3. TESTING OF IOP RELATED CARDS OF IOP-VH
IOP related spare cards can be tested by first shutting down one of the two IOPs &
then replacing system level IOP cards by the cards to be tested. To shutdown SBY-
IOP, execute CRP command INIT-IOP: 2,1; and then INIT-IOP: 1,1; and wait for
few minutes.
Once the spare card is put in the IOP, the procedure given below can be used for
testing different cards. After spare cards are tested, they should be removed &
original system level IOP cards should be put back. This IOP should now be booted
& brought in service using the procedure given in "CDOT DSS MAX Maintenance
Procedures" document.
9.3.1. Testing of Power Supply Module
The following procedure may be used -

i) Replace the system level card by the spare card to be tested.
ii) Switch on the IOP. Monitor prompt should appear on the console
terminal.
iii) Switch off the IOP & replace the spare card by the original system
level card in IOP.
9.3.2. Testing of VHC

i) Repeat steps (i) & (ii) of section 9.3.1 for VHC card.
ii) Conduct tests given in sections 5.2.1 to 5.2.4.
iii) Repeat step (iii) of section 9.3.1 for VHC card.
9.4. TESTING OF CM RELATED CARDS
The detailed of equipage with their slot is given in Fig. 9.2 for CM-L and 9.3 for CM-
XL. Refer these figure for testing the spare cards.
60 C-DOT DSS MAX

9.4.1. Testing of PSM/ESM Cards in CM-XL or SSM/ESL Cards in CM-L
i) Put IFC1 OOS-OPR by using CRP command PUT-SWU-OOS. Make
sure that BUS-1 IFC for BM1 (IFC17) is INS-ACT.
ii) Jackout IFC1 card. Jackin spare IFC card in place of it.
iii) Make IFC1 INS-ACT by using CRP command PUT-SWU-INS.
iv) Put IFC17 (Bus1 IFC for BM1) OOS-OPR by using CRP command
PUT-SWU-OOS.
v) Make some line to line calls from BM1 to BM4. Calls should not fail.
vi) Put IFC17 INS-ACT by using CRP command PUT-SWU-INS.
vii) Follow steps 1 & 2. Jackout spare IFC card. If more cards are there as
spare, jack the next spare card in or jack in original cards.
9.4.2. Testing of PSS Cards in CM-XL & SSS cards in CM-L
i) By using CRP command DISPL-SWU-ALL or DISPL-SWU-STATUS,
find out the status of switch plane copy0 (SS-0) and switch plane copy
1 (SS-1). Status of one switch plane should be INS-ACT and status of
second switch plane should be INS-SBY. Take the case when SS-0 is
INS-ACT and SS-1 is INS-SBY.
ii) Put switch planecopy 1 (SS-1) OOS-OPR by using CRP command PUT-
SWU-OOS.
iii) Jackout SWC1-1 card (SWC1-1 card caters to bus 0 of BM1 to BM4).
SWC1-1 card will be in slot 15 in 2nd frame in CM-XL and in slot 9 in
2nd frame in CM-L.
iv) Jack in space switch card given as spare in the position of SWC1-1.
v) Run space switch diagnostics on switch plane copy 1 (SS-1) by using
command DGN-SWU. Diagnostics should pass. Follow Step 2.
vi) If more spare switch card are there, jack the next switch card in and
follow step 5. If no more spare cards are there, jack in original card.
C-DOT DSS MAX 61

Chapter 8
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26
BUS -Ø BUS -1
S S S S S S S S S S S S S S S S
P P S S S S S S S S S S S S S S S S P P
S S M M M M M M M M M M M M M M M M S S
U U 1 2 3 4 5 6 7 8 17 18 19 20 21 22 23 24 U U BTU
II II E E E E E E E E E E E E E E E E II II
Ø 1 S S S S S S S S S S S S S S S S 2 3
L L L L L L L L L L L L L L L L
1 2 3 4 5 6 7 8 17 18 19 20 21 22 23 24
SS -Ø SS -1 SS -Ø SS -1
P P COPY-Ø COPY -1 COPY -Ø COPY-1 P P

}
}
}
}
S S S S
U U S S S S S S S S S S S S S S S S S S U U SSU
II II S S S S S S S S C C S S S S S S S S II II
Ø 1 S S S S S S S S T T S S S S S S S S 2 3
1 2 3 4 1 2 3 4 0 1 9 10 11 12 9 10 11 12
SSC -Ø SSC -1
P MU - Ø MU - 1 P
}
}
}
}
S S
U T B B C B B S S S S B B C B B T U SCU
II M I I P I I C C C C I I P I I M II
Ø E D C U C D K T T K D C U C D E 1
0 0 0 0 0 0 0 1 1 1 1 1 1 1
M M S S S S M M
BUS - Ø BUS - 1
P CMS C CMS A MU - Ø AP -Ø AP -1 MU - 1 CMS B CMS D P

}
}
}
}
}
}
S } S
U M M M M T B B C C B B T M M M M U APU
II S S S S M I I P P I I M S S S S II
Ø D C D C E D C U U C D E C D C D 1
0 0 0 1 1 1
SPARE
SPARE
NOTE : RSM CARD CAN BE USED IN PLACE OF ESL WHEREVER 4 PCMs ARE REQUIRED
FIG. 9.2
CM-L (CONFIGURATION) \DESIGN\DSSMAX\DSSMX-AT\DSSATF4
62 C-DOT DSS MAX

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26
P P P P P P P P C C P P P P P P P P
S S S S S S S S M M S S S S S S S S
A P P M M M M M M M M L L M M M M M M M M P P
S S S S
or or or or or or or or - - or or or or or or or or
U U U U BTUØ
E E E E E E E E A A E E E E E E E E
II II II II
B S S S S S S S S 0 0 S S S S S S S S
M M M M M M M M 0 0 M M M M M M M M
C C
M M
A P P P P P P P P P P L L P P P P P P P P P P
S S S S S S S S S S S S S S S S S S S S
- -
U U S S S S S S S S S S S S S S S S U U SSUØ
II II A A II II
0 0
B
0 0
C C
M M
A P P P P P P P P P P L L P P P P P P P P P P
S S S S S S S S S S S S S S S S S S S S
- -
U U S S S S S S S S S S S S S S S S U U SSU1
A A
II II II II
0 0
B
0 0
P P P P P P P P C C P P P P P P P P
S S S S S S S S M M S S S S S S S S
A P P M M M M M M M M L L M M M M M M M M P P
S S S S
or or or or or or or or - - or or or or or or or or
U U U U BTU1
E E E E E E E E A A E E E E E E E E
II II II II
B S S S S S S S S 0 0 S S S S S S S S
M M M M M M M M 0 0 M M M M M M M M
C C C C
M M M M
A P P C B L C N B L L B N C L B C P P
S S C M B S P P S B M C S S
- - - -
U U K E X C C C C X E K U U SCU
II II A A A A II II
0 0 0 0
B
0 0 0 0
C C C C C C C C C C
M M M M M M M M M M
A P P H L L H B B L L B B H P P
L L L L H L L
S S M M M P P M M M S S
- - - - - - - - - -
U U S S E C C E S S U U APU
II II A A A A A A A A A A II II
B 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0
NOTE : ABSENCE OF ANY PSM OR ESM CARDS SHOULD BE EQUIPPED BY THE DUMMY LOAD CARD APC-CML 483/S-S00
ABSENCE OF ANY PSS CARD SHOULD BE EQUIPPED WITH THE DUMMY LOAD CARD APC-CSL 484/S-S00
ABSENCE OF ANY CARD IN APU AND SCU FRAMES SHOULD BE EQUIPPED WITH THE DUMMY LOAD CARD APC-CML 483/S-A00
ALL VACENT SLOTS IN ALL FRAMES SHOULD BE EQUIPPED WITH CORRESPODING DUMMY LOAD CARDS
FIG. 9.3
CENTRAL MODULE-XL CONFIGURATION
\DESIGN\DSSMAX\DSSMX-AT\DSSATCMC
C-DOT DSS MAX 63

Chapter 8
vi) If more spare switch card are there, jack the next switch card in and
follow step 5. If no more spare cards are there, jack in original card.
vii) Put SS-1 inservice by using CRP command PUT-SWU-INS. Status of
SS-1 will become INS-SBY.
viii) Give CRP command INTCHG for SS-1. SS-1 will become INS- ACT.
Make some inter-BM calls covering all BMs.
9.4.3. Testing of Clock Card in CM-L or CM-XL
i) By using CRP command, DISPL-SWU-ALL or DISPL-SWU-STATUS,

find out the status of switch plane copy 0 (SS-0) and switch plane copy
1 (SS-1). Status of one switch plane should be INS-ACT and status of
second switch plane should be INS-SBY. Take the case when SS-0 is
INS-ACT and SS-1 is INS-SBY.
ii) Put switch plane copy 1 (SS-1) OOS-OPR by using CRP command
PUT-SWU-OOS. Jackout copy 1 clock card.
iii) Jack in clock card given as spare in the place of jacked out clock card.
iv) Run space switch diagnostics on switch plane copy 1 (SS- 1) by using
command DGN-SWU. Diagnostics should pass.
v) Put switch plane copy 1 (SS-1) inservice by using CRP command PUT-
SWU-INS. See SS-1 status by using CRP command DISPL-SWU-
STATUS. Status of SS-1 will be INS-SBY.
vi) Give CRP command INTCHG for making switch plane SS-1 active. See
the status of SS-0 and SS-1 using CRP command DISPL-SWU-ALL.
Status of SS-0 should be INS-SBY and of SS-1 INS-ACT.
vii) Put switch plane SS-0 OOS-OPR by using CRP command PUT- SWU-
OOS.
viii) Make some inter-BM calls covering all BMs.
ix) Put switch plane SS-0 INS-ACT by using CRP command PUT- SWU-
INS. See the Status of SS-0 by using CRP command DISPL-SWU-
STATUS. Status of SS-0 will be INS-SBY.
x) Same as step 2. Jack in the original and make it INS.
9.4.4. Testing of NSC Card in CM-XL only
Repeat all above steps as specified in 9.4.3 for NSC card but before testing,
allow 3 hrs warm up time after making card inservice.
64 C-DOT DSS MAX

9.4.5. Testing of CPU Card in CM-L and BPC or HPC Card in CM-XL
i) By using CRP command DISPL-SWU-ALL or DISPL-SWU-STATUS,

find the status of both the copies of AP. Take the case when AP-0 is
active and AP-1 is standby.
ii) Put the AP-1 OOS-OPR using CRP command PUT-SWU-OOS.
iii) Jack out OOS-OPR AP-1 card. Jack in the card which has been given
as spare for AP.
iv) Run diagnostics on OOS-OPR AP using CRP command DGN- SWU.
Diagnosis should pass.
v) Bring in OOS-OPR AP using CRP command PUT-SWU-INS. See the
status of AP-1 using DISPL-SWU-STATUS. Status of AP-1 will be
INS-SBY.
vi) Execute INTCHG AP-1 to make it INS-ACT. See the status of AP-1
using CRP command DISPL-SWU-STATUS. AP-1 status should be
INS-ACT.
vii) Both the IOPs should be ACT and SBY.
viii) Jack out the CPU card and jack in the original system card, after
making AP-1 INS-SBY and then OOS-OPR. After replacement, make it
INS-SBY.
9.4.6. Testing of HMS Card in CM-XL only
i) Put CMS 1 OOS-OPR by using CRP command PUT-SWU-OOS.

ii) Jackout HMS cards.
iii) Jackin the HMS card given as spares.
iv) Run diagnostics on CMS 1 using CRP command DGN-SWU.
v) Put CMS 1 INS-ACT by using CRP command PUT-SWU-INS.
vi) Put CMS2 OOS-OPR by using CRP command PUT-SWU-OOS.
vii) Make some inter-BM calls covering all BMs.
viii) Bring in CMS2 by using CRP command PUT-SWU-INS.
ix) Same as step 2 & 3.
x) Jackin the original HMS cards and make it INS.
C-DOT DSS MAX 65

Chapter 8
9.4.7. Testing of BME Card
i) See the status of both memory units (MU-0 & MU-1) in APU frame by
using CRP command DISPL-SWU- STATUS. Status of both units MU-
0 and MU-1 will be INS- ACT.
ii) Put MU-0 OOS-OPR by using command PUT-SWU-OOS.
iii) Jack out BME card (MU-0) in AP
iv) Jack in the BME card given as spares.
v) Run diagnostics on MU-0 by using CRP command DGN-SWU. Memory
diagnostics takes long time. So wait for the final results. Diagnosis
should pass. Reports will come on OOD.
vi) Jack out the BME card which was jacked in in step 4.
vii) Jack in the original BME card and make it INS.
66 C-DOT DSS MAX

Chapter 10.
Service Quality
In C-DOT DSS MAX, Service Quality test is conducted as the final test to ascertain the
stability/peformance of the exchange It is performed using C-DOT load test generator
which generates 50,000 calls distributed over all the Base Modules. However, due to the
constraints of length of the interconnection cables used between Load Test Generator and
Base Modules of the Exchange, it may not be possible to consider all the Base Modules for
Service Quality in one cycle. In such cases, it is desired to divide the Service Quality Test
in two or more cycles as the case may be. Efforts may be made to connect as many BMs as
possible for first Service Quality Cycle of 50000 calls. Remaining left out BMs are to be
considered in next Service Quality Cycle.
NOTE : In case of SBM Exchanges, the use of LTG is not desired as it is smaller
exchange and also the availability of LTG for small exchanges is no
guaranteed. The current practice is continued, as of Service Quality using 16
telephone sets may be one of the alternatives.
Example :
If there are 10 Base Modules at the site, first five BMs can be connected for first Service
Quality Cycle of 50,000 calls and remaining five BMs in next cycle. If there are more Base
Modules, Service Quality Test may be divided in three cycles for 50,000 calls each Trunk
BMs are included using loop back calls.(Fig. 10.1)
Note :
If it is possible to arrange more LTGs, they can be connected to different Base Modules
and Service Quality Cycles can be run independently for 50,000 calls generated by each
LTG. This will reduce the time required for Service Quality of large exchanges. (Fig.
10.2).
Service Quality Cycle :
Each Service Quality Cycle is completed in two steps :
STEP-1 :
Before starting the Load Test Generator, COPY-0 or COPY-1 controllers of the Base
Modules being considered for Service Quality Cycle and that of Central Module are to
made INS-ACT. Now start the LTG and wait for about 10 minutes and thereafter
interchange all the controllers of the Base Modules and that of the Central Module, one by
Chapter 10.
one. Each and every interchange of controllers should pass and no alarm should be raised
on ADP or OOD/PRINTER during this process.
This will ensure the system stability and successful reconfiguration of hardware in case of
any failure under partial load conditions. In this STEP-1, call failures should not be
monitored because the transient calls (the calls under set-up phase) may fail during
interchange of some controllers.
STEP-2 :
After successful completion of STEP-1, COPY-0 of all the controllers of the Base Modules
under consideration and that of Central Module are to be made INS-ACT. Now start the
Load Test Generator for 25,000 calls. After completion of 25,000 calls, make COPY-1 of all
the controllers INS-ACTIVE and start the Load Test Generator once again to run 25,000
calls. Note down total failures which should not be more than 15, for 50,000 calls.
Note :
1. In case of C-DOT TAX-XL or C-DOT TAX-XLE, the load can be generated by
equipping analog Terminal Units and creating the subscribers. They will be
removed after completing the service quality.
68 C-DOT DSS MAX

C-DOT DSS MAX
LTG
64 PAIR
CABLE 1
TRUNK TRUNK
BM BM
CABLE 2
LOOP BAK LOOP BACK
TRUNK
CM
BM
LOOP BACK
TRUNK TRUNK
BM BM
FIG. 10.1
\DESIGN\DSSMAX\DSSMX-AT\DSSATF1
69
SERVICE QUALITY
70
Chapter 10.
LTG LTG SETUP-1

64 PAIR
CABLE 1
CABLE 2
TRUNK TRUNK
BM BM
LOOP BACK LOOP BACK
TRUNK
CM
BM
CABLE 1
LOOP BACK
64 PAIR
LTG
LTG SETUP-2
CABLE 2
TRUNK TRUNK
BM BM
LOOP BACK LOOP BACK
FIG. 10.2 \DESIGN\DSSMAX\DSSMX-AT\DSSATF2
C-DOT DSS MAX

Appendix A
Operation Procedures for

Supplementary Services in C-DOT
A.1 NUMBER IDENTIFICATION SUPPLEMENTARY SERVICES

Sl. Facility Registration Registration Activation Deactivation Remarks
as ORG-FAC as TRM-FAC
No.
1. CLIP CLIP NO NO In case of PSTN
Subscriber, the telephone
instrument should support
CLI display.
2. CLIR CLIR-PR NO NO
3. CLIRO CLIP&CLIRO NO NO
4. MCID MCID See Note-1 NO Subscriber is put under
malicious observation
using command MOD-
SUB-OBS with OBS-
TYP=MALC
5. MSN MSN NO NO Only for ISDN
6. DDI NO NO Only for ISDN . Applicable
to DDI groups , created
using command CRE-HGP.
7. SUB SUB NO NO Only for ISDN. GRNT-
MSN to grant the facility
and ADD-MSN-DN to add
additional MSN
Subscribers.
8. COLP NO NO Only for ISDN. Can be
used with C-DOT-TA210 as
PHILIPS Phone does not
support the feature. The
facility is available by
default to all the
subscribers and no
registration is required.
9. COLR COLR-PR NO NO Only for ISDN
10. COLRO COLRO NO NO Only for ISDN
Note-1 : The PSTN subscriber can invoke the service just by HSF. A ISDN
subscriber can invoke the service by * 65 # after switching over to
Chapter 10.
“Keypad Dialling Mode” from conversation stage. Procedure to switch

over to “Keypad Dialling “ is specific to the user’s equipment e.g for
PHILIPS Phone , the keys < Memory > <Display> are to be pressed .
The complete procedure for invocation of MCID service from PHILIPS
ISDN Phone is : <Memory> <Display> *65# . In the absence of any
procedure from TEC for ISDN Subscribers , the in built capability of
PHILIPs telephone has been exploited to support the feature.
A.2 CALL OFFERING SUPPLEMENTARY SERVICE

as ORG-FAC as ORG-FAC
No.
11. LH NO NO Applicable to HGP and

DDI groups , created
using command CRE-
HGP.
12. CFU(FXD) ABSNT-FXD- *28# #29# GNT-ABS-SRV

NUM
13. CFU(SEL) ABSNT-SEL- *14 B# #15# Subscriber has to

NUM activate the facility
14. CFB(GRP) DOB-SET- *66# #67# GRNT-DIV

NUM
15. CFB(SEL) DOB-SEL- *220 B# #221# Subscriber has to

16. CFNR(GRP) DONA-SET- *224# #225# GRNT-DIV

NUM
17. CFNR(SEL) DONA-SEL- *222 B# #223# Subscriber has to

A.3 CALL COMPLETION SUPPLEMENTARY SERVICES

No.
18. Call Waiting CLD-CALL- * 18 # # 19 # See Note-2

WTNG
19. Call Hold CH-WR or HOLD NO Only for ISDN
CH-WOR
20. Terminal TERMPORT SUSPEND/ NO Only for ISDN
Portability RESUME
21. Hot Line TMD-HT-LN * 20 B # # 21 # GRNT-HTLN to activate

(Timed) the facility first time or
when deactivated by the
subscriber.
72 C-DOT DSS MAX

OPERATION PROCEDURES FOR SUPPLEMENTARY SERVICES IN C-DOT

No.
22. Hot-Line UNTMD-HT- NO NO GRNT-HTLN

LN
( Un-timed)
Note-2 : Invocation procedure for ISDN and PSTN subscribers are different. A
ISDN subscriber uses functional keys to put the existing call to wait to
receive another call in waiting. The PSTN subscriber has to invoke the
feature by HSF and can toggle between two subscribers repeatedly by
using HSF. Also for ISDN subscriber, CH should also be subscribed on
the interface.
Sl. Facility Registration Registration Activation / Usage Procedure Remarks

No.
23. CNF- CNF-3W HSF *250 B # to add B

3PTY
HSF *253# to toggle Only for PSTN
HSF * 254 B # to drop B
HSF * 254 # to drop last party
HSF * 252 # to activate
24. CNF- CNF-6W As above with difference that dial 251 in

6PTY place of 250 to add a party B as
conference member. Subsequently , before Only for PSTN
adding a new member into the conference
, the procedure HSF * 252 # to activate
the conference should be followed ,
before attempting to add a new party C
using procedure HSF * 251 C # .
C-DOT DSS MAX 73

Chapter 10.
A.4 DYNAMIC LOCKING FOR ACCESS LEVELS
Sl. Facility Registratio Registratio Activation / Usage Procedure Remarks

n as ORG- n as TRM-
No. FAC FAC
25. Dynamic SUB-OG- * 23 ABCD ABCD # to select the N=0 for all allowed
STD Locking BRRD password
N=1 for Local Access
* 23 ABCD PQRS # to change the
password N=3 for STD Access
* 24 ABCD N # where ‘N’ is the N=4 for 10X Access

current access
N=5 for Regional i.e. 90
Access
Note-3 : The values for ‘N’ are valid , subject to the condition that the access
level , being selected , is allowed by registration.
A.5 MISCELLANEOUS SUPPLEMENTARY SERVICES

No. as ORG-FAC as TRM-FAC
26. Alarm ALRM-AUTO * 16 hh mm# #17 hh mm # Alternatively, a subscriber

(Once) can subscriber can
register an alarm call with
help of OPERATOR . It
possible by registering the
facility ALRM-SEMI and
then granting it using
command GRNT-ALARM.
27. Queuing QUING-NO- *686 # #685# Use HSF *684 # for

DCTV suspending the Queue to
make an originating call .
or
Only for PSTN (See
QUING-DCTV Note-4)
28. AOC-E AOC-E NO NO Only for ISDN.
29. AOC-D AOC-D NO NO Only for ISDN.
30. 16 Khz for NO NO Only for PSTN. The

subscriber should be
Home created with MTR-CLS
Meters =CHK-MTR.
Note-4 : The facility is valid for ISDN interface when configured as Hunt
Group. However for individual ISDN subscriber , more than one call
can wait on an ISDN interface as specified/allowed by the
administrator for that interface.
74 C-DOT DSS MAX

OPERATION PROCEDURES FOR SUPPLEMENTARY SERVICES IN C-DOT
GENERAL COMMENTS
1. There are a number of services which are activated on registration by the
exchange administrator and no procedure is required to be followed by the
subscriber. The columns “ Activation “ and “ Deactivation” for such services
are marked as NO. For other services, the procedure specified in the table ,
should be followed by DTMF as well ISDN subscribers unless it is specified .
The services are available for ISDN as well as PSTN interfaces unless
specifically mentioned.
2. The procedure is specified for DTMF subscribers using * and #. Alternatively
Decadic as well as DTMF subscribers can use the procedures by dialling. '1' in
place of * or # in the beginning, with out dialling any digit in place of # in the
end. For example,*228 # will be 1 228.
C-DOT DSS MAX 75

System
Practices COMMENTS
The following comments pertain to:
Document Name
CSP Section - -
Issue/Draft , -
No. (Month) (Year)
COMMENTS :
(Use a separate sheet if required)
Please mail your comments to: Your Reference:

Centre for Development of Telematics Name :
Designation :
Attn: Mr. Y.K. Pandey
Company :
Director, Systems
Address :
39, Main Pusa Road
New Delhi 110 005
Tel.: +91-11-5740374 Tel. :
Fax: +91-11-5756378 Fax :

Acceptance Testing: C-Dot Dss Max

Uploaded by

Acceptance Testing: C-Dot Dss Max

Uploaded by

C-DOT DSS MAX

C-DOT DSS MAX

SERIES 300 : INSTALLATION

CSP SECTION NO. 400-314-0715

THE INFORMATION IN THIS SYSTEM PRACTICE IS FOR INFORMATION PURPOSES AND IS

SUBJECT TO CHANGE WITHOUT NOTICE.

TO THE DIRECTOR (SYSTEMS ), CENTRE FOR DEVELOPMENT OF TELEMATICS, 39, MAIN

PUSA ROAD, NEW DELHI - 110 005

© 1999 BY C–DOT, NEW DELHI.

Chapter 2. Conformity Check ...........................................................................................................................7

Appendix A Operation Procedures for Supplementary Services in C-DOT...................................................71

H:\HOME\MAX2111\WORD\DSSMAXAT.DOC February 22, 1999

6 C-DOT DSS MAX

Ensure that the documents as per despatch list are available.

i. Check the appearance of iron work and racks.

8 C-DOT DSS MAX

Cabling, MDF and Power Distribution

3.3. POWER DISTRIBUTION

3.3.1. -48V Power Distribution

10 C-DOT DSS MAX

3.3.2. 220V AC from Inverter

220V AC from inverter is distributed to various points to provide power to

3.3.3. 3 Phase AC Distribution

3.3.4. DC Earth Distribution

From DC earth pit, earth is brought to DC earth collector plate. The

C-DOT DSS MAX 11

Alarm Tests for Power & Fire Alarms

4.1. POWER ALARMS

4.2. FIRE ALARMS

System Level Tests

5.1. SELF TEST OF DEVICES

5.2. IOP TESTING

5.2.1. Onboard Devices Tests for C-DOT IOP

5.2.1.1. RTC Test

C-DOT DSS MAX 13

5.2.2. Memory Diagnostic Tests

5.2.2.1. Checker Board Test

14 C-DOT DSS MAX

5.2.3. Diagnostics Commands for ACIA/HDLC

5.2.3.1. Asio Test #1

C-DOT DSS MAX 15

the screen. The test is performed 10 number of times. The

16 C-DOT DSS MAX

C-DOT DSS MAX 17

5.2.4. Diagnostic Commands for SCSI Devices

5.2.4.1. SCSI Bus Reset

18 C-DOT DSS MAX

5.3. INITIALIZATION TESTS

5.3.1. Initialization with the Default Status Map

C-DOT DSS MAX 19

iii. Power up the frames of the CM in the following sequence –

APU, SCU, SSU & BTU.

5.3.2. Initialization with following Configurations

20 C-DOT DSS MAX

5.4. EQUIPPED CARD TESTING

5.5. POWER SUPPLY ALARM TESTING IN BASE MODULE

5.5.1. Power Supply Alarm Testing in Analog TU / DTU

C-DOT DSS MAX 21

5.5.2. Power Supply Alarm Testing in SUM

5.5.3. Power supply Alarm Testing in ISTU

5.5.4. Power Supply Alarm Testing in BPU

22 C-DOT DSS MAX

5.5.5. Power Supply Alarm Testing in TSU

5.6. POWER SUPPLY ALARM TESTING IN CENTRAL MODULE RACK

5.6.1. Power Supply Alarm Testing In CM-L Rack

C-DOT DSS MAX 23

24 C-DOT DSS MAX

5.6.2. Power Supply Alarm Testing In CM-XL Rack

C-DOT DSS MAX 25

26 C-DOT DSS MAX

5.7. SWITCH UNIT ALARMS

C-DOT DSS MAX 27

Exchange Data Checks

6.1. LOCAL DATA

6.2. TRUNK & ROUTE RELATED DATA

6.3. CHARGING DATA