c-dot dss maxcdothelpline.cdot.in/helpline/documents/c-dot_dssmax/... · 2014-12-29 · c–dot dss...

C-DOT DSS MAX

TRAFFIC ADMINISTRATION

System Practices

Section No. 400-412-0733

Draft 02, December 1998

C-DOT DSS MAX


(This document is updated as per Software Release 2_1_1_1)

© 1998, C-DOT Printed in India

C–DOT DSS MAX


DRAFT 02

DECEMBER 1998

PAUSA 2055

SERIES 400 : ADMINISTRATION

CSP SECTION NO. 400-412-0733

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

© 1998 BY C–DOT, NEW DELHI.

Table of Contents

Chapter 1. Introduction .............................................................................................................................. 5

1.1. Purpose and Scope ...................................................................................................... 5

1.2. Prerequisites................................................................................................................ 6

1.3. Definitions ................................................................................................................... 6

1.4. Conventions ................................................................................................................. 8

Chapter 2. Traffic Administration ........................................................................................................... 10

2.1. Introduction ............................................................................................................... 10

2.2. Traffic Measurements ............................................................................................... 11

2.3. Data Collection .......................................................................................................... 12

2.4. Data Storage.............................................................................................................. 13

2.5. Presentation of Stored Data ..................................................................................... 13

Chapter 3. Traffic Administration Commands ....................................................................................... 14

3.1. Introduction ............................................................................................................... 14

3.2. Command Directory .................................................................................................. 15

3.3. Command Flow.......................................................................................................... 17

Chapter 4. Parameter Description........................................................................................................... 20

4.1. Introduction ............................................................................................................... 20

4.2. Parameter description .............................................................................................. 20

Chapter 5. Operator Command Sheets ................................................................................................... 35

5.1. Introduction ............................................................................................................... 35

5.2. Operator Command Sheets ...................................................................................... 37

Appendix - A Report Fields Description .................................................................................................... 113

A.1 Introduction ............................................................................................................. 113

A.2 Periodic Report on Originating - Terminating Calls (ORG-TRM) ....................... 114

A2 Periodic Report on Originating Traffic and Terminating Traffic......................... 122

A.4 Periodic Report on Incoming Traffic ...................................................................... 123

A4. Periodic Report on Incoming Traffic and Outgoing Traffic .................................. 128

A5. Periodic Report on Exchange Performance ........................................................... 129

Appendix C Delay Parameters................................................................................................................. 144

Delay Parameters for Non-ISDN or Mixed Environment : ............................................... 144

A.5 Periodic Report on Service Circuits (SRV-CKT) ................................................... 134

A.6 Periodic Report on Switching Network (SWT-NET)............................................. 136

A.7 Periodic Report on Outgoing Trunk Group (OG-TRNK) ...................................... 136

A.8 Periodic Report on Incoming Trunk Group (IC-TRNK)........................................ 140

A.9 Daily Report (DLY-REP)......................................................................................... 143

H:\HOME\MAX2111\WORD\MXTRADM2.DOC December 28, 1998

TRAFFIC ADMINISTRATION 5

Chapter 1.

Introduction

1.1. PURPOSE AND SCOPE

This document describes the traffic flow measurements done by the traffic administration software in C-DOT DSS MAX. It is meant to be a handy reference for the operating personnel for carrying out various traffic related functions such as displaying traffic statistics, modifying parameters related to the accumulation of traffic information, starting, stopping and preparing traffic reports from the measurements recorded in the system. For describing these functions a structured approach has been followed which allows for easy comprehension of the procedures involved. This is evident in the structure of the document described below.

Chapter 2 briefly describes the philosophy of traffic measurements viz. functions performed by traffic measurement, how are they achieved and how the data is collected and manipulated.

Chapter 3 describes various functions performed by various classes of traffic commands. Command directory is given alongwith description of a typical command flow. Hardware and software resources required for execution of traffic commands are also discussed.

Chapter 3 builds upon the discussion in chapter 2 and describes the parameters required for each command. To facilitate better appreciation, a position defined approach i.e. in the order in which these will be asked for by the system, has been followed.

Chapter 4 describes each parameter individually in greater detail. The reader will often come back to this chapter for reference in times of doubt. Although online help is always at hand, a better description of the command parameters will be available here.

Chapter 1

6 C-DOT DSS MAX

Lastly, chapter 5 presents the most crucial information viz. traffic command sheets for the operating personnel. Each traffic command is described under the following heads.

1. Command

2. Parameter Entry Form

3. Output Forms

This approach runs, as far as possible, alongside the manner in which the system responds to these commands. The objective here is to minimize the information gap i.e. what you will see on the screen is what is given in this document. Also, to facilitate better comprehension, important fields of the various traffic reports are described in Appendix-A.

1.2. PREREQUISITES

In order to appreciate the contents of this document, the reader is required mandatorily to be conversant with the "C-DOT DSS MAX Man Machine Communication" document. This will make it easier for the operating personnel to interact with the system and also make the man-machine communication more efficient.

It is also assumed that the reader has a basic knowledge of the working of a digital switching system. The reader is advised to read this document, atleast to begin with, from beginning to end sequentially. Later on, as the need dictates, any part of the document may be referred randomly.

1.3. DEFINITIONS

Definition of some basic and often used terms in this document are given below to facilitate better understanding of its contents.

Traffic

A flow of calls and messages. Traffic Engineering is the science of measuring and manipulating data on the usage of circuits or entities and the switching and routing patterns within an exchange in order to maximise efficiency.

Traffic Data

The information collected as a result of observing traffic flow for a specified period of time and conditions. This data is processed to provide an index of the performance of an exchange or its entities.

INTRODUCTION


Traffic Administration

That part of administration services which concerns itself with measurement of traffic flow and providing useful data (in the form of reports or structured presentation on a VDU) for drawing inferences about the performance of the exchange as a whole or its entities. This information is then used to fine-tune the allocation of the limited resources of the exchange.

Command

In man-machine language a specification of an expected action or function by the system. It will act like a specific manipulation which causes transmission of a signal which indicates this manipulation to the exchange.

Mnemonic (or Mnemonic address)

A simple address code with some easily remembered relationship to the actual name of the destination, often using initials or other letters from the name to make up a pronounceable word. For example "DISPL-TRF-OBS" is a mnemonic for the command "Display Traffic Observations".

Parameter

In man-machine language, a variable which identifies and contains a piece of necessary information to execute a command. A position-defined parameter list for a particular command lists the required parameters in the sequence in which the system will need them for successful execution of that command.

Traffic Report

Display of traffic information in a predefined format. The information may have been recorded as a result of activation of some traffic observation for a specific period of time. The report may be displayed on the VDU and printed on a printer.

Trunk Group

Group of trunk circuits (incoming, outgoing or both-way) terminated at the same two points.

The trunk groups may be distributed in the same Base Module (BM) or over a number of BMs in case of multimodule C-DOT exchange.

Service Circuits

A group of circuits which provide specific services like announcements, tones, etc. These may also include circuits like MF senders and receivers, DTMF receivers, etc.

Chapter 1

8 C-DOT DSS MAX

Switching Network

That part of exchange where connections between inlets and outlets are established through 'switches'. The switches or cross-points may be mechanical or semi-conductor registers. In C-DOT exchanges, these are semi-conductor registers.

Processor

A device which controls the functioning of a Stored Program Controlled (SPC) exchange by referring to the information stored in the memory. These are usually 8-bit or 16- bit microprocessors.

Operator Commands Sheets

These are the formatted output forms which are generated by the system in response to traffic administration commands given by the operating personnel at the man-machine terminals. There is an operator command sheet corresponding to every traffic command and may take one or more screen 'pages'.

Output Outside Dialogue (OOD)

The software interface between the switch and storage and display devices like VDU, printer, disk etc. The information can be output to one or more of these devices depending upon the options set by the operating personnel.

1.4. CONVENTIONS

Some conventions have been followed throughout this document. Unless otherwise specified they follow the correspondence given below.

[Parameter] = Square brackets mean a "non-essential" parameter i.e. default value exists for that parameter.

On the other hand, an unbracketed parameter means that the parameter is "essential" and a value must be specified by the user. An error will be reported otherwise.

{P1, P2} = Signifies that the parameter may accept a list of values. The brackets signify start and end of a list.

INTRODUCTION


Parameter1/Parameter2 = It means that out of the two parameters viz. parameter1 and parameter2, any one must be provided.

Parameter1 (Parameter2, Parameter3) = It means that either parameter1 or parameter2 and parameter3 must be provided.

The information appearing before or to the left of a colon (:) or an "is equal to" sign (=) is the system's response and the information to the right is either a user response or a default value which is assumed by the system.

10 C-DOT DSS MAX

Chapter 2.

Traffic Administration

2.1. INTRODUCTION

Traffic administration is one of the most important tasks performed by the administration software because it provides a meaningful index to the exchange performance. Traffic administration consists of various types of supervisions of traffic flow, which accrues from different entities of the exchange. Supervision and measurement of the traffic handled by an exchange have two distinct sets of objectives, corresponding to two types of supervisions.

1. Permanent supervision designed to monitor the instantaneous quality of service offered by an exchange and the traffic loading of its main equipment. The supervision is permanent and it concerns the exchange as a whole. Typical measurements are the total incoming and total outgoing traffic. Key parameter values are displayed to the operating personnel and updated at frequent intervals. Alarms are triggered when exchange traffic exceeds certain set limits and more detailed information is output from time to time.

2. Temporary supervision, on the other hand, concerns limited subsets of various entities of the exchange such as subscriber lines, trunks, processors and parts of the switching network etc. The collected data are not necessarily exploited immediately by the operating personnel. They may be subjected to more sophisticated and rigorous processing off-line by a computer. The data are generated to provide an accurate picture of the traffic handled by the entities in question with a view to, for example, optimizing use of exchange resources, or assisting in location of faults concerning trunks, or procuring information for planning the evolution of exchange capacities and network structures or preparing traffic matrices.

Various uses to which processed traffic data may be put are:

• Performance Evaluation of Exchange as a whole. This may involve measurement of various delays involved in the service. Traffic reports indicate the call failures due to exchange and network reasons, terminals (lines and trunks) under maintenance. Also they indicate delays like dial tone delay, post dialling delay etc. which are indicative of the efficiency of administrative



personnel or in other words dissatisfaction that is caused to the subscribers by the exchange performance.

• Expansion scheduling i.e. gradually adding more subscribers, trunks etc. to the exchange without deterioration in the service.

• Telephony resource dimensioning for any exchange is done on the basis of expected traffic flow carried by the exchange. With the help of traffic reports, it is possible to get a feedback on the correctness of dimensioning based on the actual traffic flow carried by the exchange and hence take necessary corrective action.

• Network planning in order to suitably provide exchanges, tandems, trunks etc. in the given area with optimal usage of resources.

• Fault location on inter-exchange trunk circuits, subscriber lines, service circuits etc. by observing the causes of call failure through various counters.

• Port performance measurement in order to observe the quality of service being provided to a specific port. It may be subscriber port, PBX port etc.

• Miscellaneous observations like Busy Hour Call Attempts (BHCA), Busy Hour (BH) and call mixes can be made which can be later used for better resource scheduling.

• Traffic reports also indicate the calls failed due to subscriber problems. These include: no dialling, incomplete dialling, incorrect dialling, illegal attempts (i.e. services to which they are not eligible), incorrect utilization of special services and long duration conversations etc. Quite a few calls (more than 50%) fail due to these reasons. It is possible to know these figures, even on a per subscriber basis so that subscribers can be educated on efficient utilization of services provided by the exchange and thus prevent unnecessary overloading of the exchange due to repeated attempts in a busy state. This may be done through recorded announcements, etc.

2.2. TRAFFIC MEASUREMENTS

Measurement of traffic may be classified depending upon the type and purpose of the measurement. There can be four such classes.

1. Exchange Traffic Statistics

Consists of measures that reflect the performance and utilization of exchange as a whole. These generally include traffic intensity, call counts, ineffective attempt counts etc.

Chapter 2

12 C-DOT DSS MAX

2. Component Measurement

Consists of measures reflecting the performance and utilization of the individual exchange entities such as trunk groups, service circuits, etc.

3. Network Measurements

Measures which reflect the performance and utilization of the switching network e.g. usage counts of terminal interface, time switch, space switch etc.

4. Customer Measurements

Consists of measures reflecting the utilization and performance of an individual subscriber line e.g. number of originations, call mix etc.

2.3. DATA COLLECTION

Collection of data related to traffic is done at Base Processor (BP) in the Base Module (BM) and at Administration Processor (AP) in the Administration Module (AM). Traffic data is collected during call processing and maintenance operations. Two types of traffic counters are maintained for accumulation of traffic data. Raw counters, which may be updown counters or summation counters and accumulate raw or unprocessed data. Processed data counters, on the other hand, collect processed data. Depending upon various traffic events in the exchange, these counters are updated. Traffic data collection consists of measurements of counts of various events, traffic intensity and call event records.

Event registration is the process of incrementing various summation counters in response to events like incoming seizure and invalid call attempts etc. These are suitable for direct display purposes.

Traffic intensity is measured for a pool of resources or the exchange as a whole. Various groups of resources are measured for traffic intensity depending upon the input data supplied by processes of call processing (CP) subsystem, administration subsystem and maintenance subsystem. These processes update the relevant counters with respect to resource utilisation.

Call Event Records (CERs), on the other hand, are detailed records of all the events that occur during a call. It may include port identity, class of originating line or incoming circuit, dialled number, call routing time, disposition of call and time of occurrence of events, etc. CER is normally destroyed after every call unless the call was under observation and the CER data is needed for further processing. If so, then the CER data is used to produce a Call Detail Record (CDR) for further processing but CER is cleared. In case a trunk port is under observation, the CER is stored in the disk.



Collection of data can be divided into two types : (i) Voluntary (ii) Involuntary. Voluntary data collection is done under the control of man-machine commands. The periodicity of collection, type of observation and output device is controlled by the operating personnel by using the man-machine commands. On the other hand, involuntary data collection takes place automatically. All the call related data e.g. CERs and CDRs, is involuntarily collected. Also, some sampled observations are made on the traffic for measuring availability of exchange resources. This data is used for fine-tuning the system to the concurrent traffic mix in order to achieve optimal utilisation of available resources.

2.4. DATA STORAGE

Data collected as a result of both voluntary and involuntary collection is output to any of the following devices.

• To a Local or Remote Terminal for printing or displaying on MMC terminals. Local terminal is directly connected to the exchange whereas the remote terminal is connected to the exchange via dedicated links.

• To local storage media such as disk from where it may be periodically dumped onto off-line devices such as magnetic tapes for more rigorous post-processing.

• To local storage media during intermediate stages of any observation. After a specified time, the data may be simultaneously displayed on the local terminal and printed.

• To local storage media after any preset threshold is reached. This is also called exceptional measurement data output.

• All the data is, by default, stored on the disk as sequential files. The accumulation is done on a per day basis and these files may be stored in the disk for a few days.

2.5. PRESENTATION OF STORED DATA

Stored data can be presented in various ways depending upon the purpose. Generally, it is presented in the form of reports and Call Detailed Records (CDRs).

• Reports are the predefined formats for presentation of data. Reports are generated under the control of operating personnel using MMCs. Reports may be displayed on the MMC terminal and/or printed. Usually voluntary, reports may also be generated involuntarily under certain exceptional conditions like alarm fail report, malicious call report etc. In such cases, the report is displayed on the OOD terminal as well as printed.

• Call Detail Records (CDRs) are prepared for subscribers under observation. Details of each originating and terminating call are recorded. CDRs are stored in the disk and on demand may be displayed on the Output Outside Dialogue (OOD) terminal and printed.

14 C-DOT DSS MAX

Chapter 3.

Traffic Administration Commands

3.1. INTRODUCTION

Traffic commands are the tools which can be used to observe, record, manipulate and display traffic data. Under administration commands, traffic commands are grouped under two classes :

1. Traffic Administration Commands Update (Class 9)

2. Traffic Administration Commands Display (Class 10)

Update class of commands, as the name suggests, are used to modify or update traffic data and retrieval procedures. Type of observation, periodicity of observation, output options, etc. are some of the parameters which may be manipulated under this class of traffic commands. Within the update class, there are two kinds of commands. One is used for controlling the sampling attributes whereas the other one is used to start/stop a traffic report.

Display class of commands is used to display traffic information about exchange entities like:

• Current traffic information on specific subscriber lines, trunks and trunk groups.

• Call Detail Records (CDRs) of specific type and period for a specific subscriber who is under observation. The subscriber can be put under observation for originating calls and terminating calls.

CDR is not made for malicious calls. Instead, on completion of such calls, a report is immediately displayed on the OOD terminal, printed on the printer, if attached, and dumped on the disk for further processing.

• The names of periodic reports which are enabled currently.

• Exchange elements under observation e.g. subscribers, trunk groups, incoming-outgoing trunks, etc.

• Contents of a specific traffic report for a specific period and module e.g. BM1 to BM32 and AM in case of a multimodule exchange.

TRAFFIC ADMINISTRATION COMMANDS


The following types of periodic traffic reports are prepared in the system with the specified periodicity as and when they are enabled. The periodicity can be specified in multiples of 15 minutes.

• Line Reports on

° originating - terminating calls

° incoming - outgoing calls

° exchange performance

• Trunk Reports on

° incoming trunk groups

° outgoing trunk groups

• Switching Network Report

• Service Circuits Report

• Processor Report

• Exchange Performance Report

• Special Facilities Report

• Daily Reports on

° Base Modules (BMs)

° exchange

• Hunt Group Report

• Route Code Report

• Digital Trunk Report

• Signalling Link Report

• Signalling Route Set Report

• Bearer Service Report

The periodicity of Daily Reports is 1440 minutes i.e. one day, and cannot be modified.

3.2. COMMAND DIRECTORY

Command directory serves the function of a central reference point for all the traffic commands. Operating personnel will get an idea of the function performed by a

Chapter 3

16 C-DOT DSS MAX

command, its mnemonic and position defined parameters. The parameters themselves suggest the function of that command.

The directory is divided into two parts corresponding to the two traffic administration command classes viz. Update and Display.

CLASS 9 TRAFFIC ADMINISTRATION COMMANDS - UPDATE CLASS

S.No. Command Mnemonic Command Name Position Defined Parameters

1. START-TRF-RPT START TRAFFIC REPORT/(S)

RPT-TYP

2. STOP-TRF-RPT STOP TRAFFIC REPORT/(S)

RPT-TYP

3. MOD-RPT-PERDTY MODIFY REPORT PERIODICITY

RPT-TYP, TIM-UNT, RPT-PRD

4. MOD-OUT-OPT MODIFY OUTPUT OPTIONS FOR TRAFFIC REPORT

RPT-TYP, [OPTION]

5. MOD-TGP-OBS MODIFY TGP OBSERVATION

[ADD-TGP], [DEL-TGP], [DEL-ALL], TGP-OBS, [OBS-PRD], [STP-DTE], [STP-TME]

6. MOD-SUB-OBS MODIFY SUBSCRIBER OBSERVATION

[ADD-DIR], [DEL- DIR], [DEL-ALL], SUB-OBS, [OBS-PRD], [STP-DTE], [STP-TME]

7. MOD-TRK-OBS MODIFY TRUNK OBSERVATION

[ADD-TRK], [DEL-TRK], [DEL-ALL], TRK-OBS, [OBS-PRD], OBS-FILT, [STP-DTE], [STP-TME]

8. MOD-HGP-OBS MODIFY HUNT GROUP OBSERVATION

[ADD-HGP], [DEL-HGP], [DEL-ALL], OBS-TYP, [OBS-PRD], [STP-DTE], [STP-TME]

9. MOD-ROUT-OBS MODIFY ROUT OBSERVATION

[ADD-ROU], [DEL-ROU], [DEL-ALL], [OBS-PRD], [STP-DTE], [STP-TME]

Fig. 3-1a Traffic Administration Commands-Update Class



CLASS 10 TRAFFIC ADMINISTRATION COMMANDS - DISPLAY CLASS

S.No. Command Mnemonic Command Name Position Defined Parameters

1. DISPL-TRF-OBS DISPLAY TRAFFIC OBSERVATION

OBS-TYP

2. DISPL-SUB-TRFINF DISPLAY SUBSCRIBER TRAFFIC INFORMATION

[DMP-OPT], [DIRNO], [TEN]

3. DISPL-TRK-TRFINF DISPLAY TRUNK TRAFFIC INFORMATION

[DMP- OPT], [TGP-NUM], [TEN]

4. DISPL-CDR DISPLAY CALL DETAIL RECORD

DIRNO, [CDR-TYP], [FRM- DATE], [TO-DATE], [FRM-TIME], [TO-TIME]

5. DISPL-TRF-RPT DISPLAY TRAFFIC REPORT

RPT-ID, [FRM-DATE], [TO-DATE], [FRM-TIME], [TO-TIME], [MOD-NO]

6. DISPL-MFSA-INF DISPLAY MF SIGNALLING ANALYSIS INFORMATION

[TEN],[TRK-OBS], [OBS-FILT], [FRM-DATE],[TO-DATE],[FRM-TIME],[TO-TIME]

Fig. 3-1b Traffic Administration Commands-Display Class

3.3. COMMAND FLOW

Irrespective of the command, all the commands when executed, follow a similar pattern of man-machine interaction. Command flow is the interaction between the operating personnel and the administration software, more specifically, the Command Recognition Process (CRP). In order to appreciate the usual steps involved in command flow, a sample command "MOD-SUB-OBS" i.e. "Modify subscriber observation", is described below:

Modify Subscriber Observation (MOD-SUB-OBS) Command Flow

1. At the CRP prompt (<), either give the command MOD-SUB-OBS or define the menu path for this command i.e. 1 (Administration Command Classes), 9 (Traffic Administration Command Update), 7 (Modify Subscriber Observation). The path will be 1 9 7.

Chapter 3

18 C-DOT DSS MAX

Yet another method would be to traverse the menus and choose appropriate options.

(Error will be reported if the command is not entered properly)

2. Security Checks Performed by CRP

° Checks whether the user has the authority to issue this command.

(Error will be reported if any of these checks fails)

3. Parameter Entry Form Displayed

° The command mnemonic, command and all the position defined parameters are displayed.

° Non-essential parameters, i.e. default value exists for them, are shown enclosed in square brackets. For example, in this case all parameters except SUB- OBS are non-essential.

° User enters parameter values as desired. Error messages will be displayed for illegal entries.

Help is available from the system for each parameter on typing 'h' and 'CR' (Carriage Return) while the cursor is at the desired parameter.

4. Options displayed to Repeat/Terminate/Execute (R/T/E) the command with the given input parameters.

5. User enters the "Execute" i.e. "E" option. The system will respond by displaying the message :

Executing

At this moment, system carries out certain "housekeeping" functions.

6. CEP reads detailed parameter validation information from disk, such as:

° Terminal Equipment Number (TEN) Status.

° Directory Number Status.

° System limits on the number of simultaneous observations that can be activated.

° Subscriber observation type restrictions, etc.

7. CEP checks status and limits



° Terminal Equipment Number is free and equipped

° Directory number is free and not frozen

° Subscriber is not already under the same observation

8. CEP updates information on disk concerning

° Terminal Equipment Number status - equipped and in use

° Directory number status - used

° Directory number to equipment translation

° Increment the number of subscribers under that particular type of observation

° Initialise and start counters for the required observation period

9. If the command is executed successfully, CRP will display output results in the form of "Output Forms" which may occupy one or more VDU screens and/or printer pages.

10. Output command execution results on

° VDU, or

° VDU and Printer, or

° Printer (as chosen by the operator)

20 C-DOT DSS MAX

Chapter 4.

Parameter Description

4.1. INTRODUCTION

On issuing a traffic administration command, the system will respond by asking for parameters required for execution of that command. Parameters are variables which identify and contain a piece of necessary information to execute a command. Although online 'help' is available on the parameter entry form, it is very important for the operating personnel to understand the correct application of each parameter.

Some of the parameters are used in more than one command. In the parameter description to follow, these parameters are discussed only once. Contextual peculiarities, if any, are pointed out at the appropriate places.

Parameter description for each parameter is covered under the following subheads :

PARAMETER NAME : Name of the parameter

MNEMONIC : Address code in the form of a pronounceable word

TYPE : ASCII, numeric or logical i.e. type of data acceptable

POSSIBLE VALUES : A set of values and/or range acceptable

DEFAULT : The value automatically assigned if the operator doesn't assign any value i.e. just presses the <CR> key.

REMARK/S : Some more information regarding special attributes of the parameter.

4.2. PARAMETER DESCRIPTION

On the proceeding pages, all the parameters used by traffic administration commands are described. All the parameters are described in the same format in order to facilitate easy reference.

PARAMETER DESCRIPTION


4.2.1. ADD-DIR (Subscriber Directory Number to be added for Observation)

PARAMETER NAME : Subscriber Directory Number to be added for observation

MNEMONIC : ADD-DIR

TYPE : 7 Numeric, Range 200 8999999

POSSIBLE VALUES : Range 200 to 8999999, starting digit is not 0, 1 or 9

DEFAULT : 0 i.e. no directory number is to be added for observation)

EXAMPLE : 5485000 to 5485020 & 5483000

REMARKS : Every subscriber is identified by a unique number in the exchange called directory number. This has two parts, the first one is exchange code and second one is identification number of subscriber. Either range or set of values or both are allowed. For range, 'to' is to be given between the Ist value and last value. For set of values, '&' is to be given between two values For using both range and set of values, example is given above

4.2.2. ADD-HGP (Principal Directory Number of the Hunt Group to be added for Observation)

PARAMETER NAME : Principal Directory Number of the Hunt Group to be added for observation

MNEMONIC : ADD-HGP

TYPE : 7 Numeric


DEFAULT : 0 (i.e. no HGP principal directory number is to be added for observation)

EXAMPLE : 5485999 & 5485001

REMARK : Range is not allowed. Set is allowed.

Chapter 4

22 C-DOT DSS MAX

4.2.3. ADD-ROU (Route Code to be Added for Observation)

PARAMETER NAME : Route code to be added for observation

MNEMONIC : ADD-ROU

TYPE : 12 Numeric

POSSIBLE VALUES : 0 to 999999999999

DEFAULT : 0 (i.e. no route is to be added for observation).

EXAMPLE : 01 & 52

REMARK Range is not allowed. Set is allowed

4.2.4. ADD-TGP (Trunk Group Number to be Added for Observation)

PARAMETER NAME : Trunk Group Number to be Added for Observation

MNEMONIC : ADD-TGP

TYPE : 3 Numeric


DEFAULT : 0 (i.e. no TGP is to be added for observation).

REMARK : Range and set of values allowed

4.2.5. ADD-TRK (Add Trunks for Observation)

PARAMETER NAME : Trunk Number to be Added for Observation

MNEMONIC : ADD-TRK

TYPE : Same as TEN

POSSIBLE VALUES : 1-1-1-1-1 to 32-3-6-26-32

DEFAULT : 0-0-0-0-0

REMARK : Range or set of values allowed separate character 'to' for range and '&' for set of values.



4.2.6. CDR-TYP (Call Detail Record Type)

PARAMETER NAME : Call Detail Record Type

MNEMONIC : CDR-TYP

TYPE : 6 ASCII

* POSSIBLE VALUES : 1. CLLNG (For calling subscriber under Observation)

2. CLLD (For called subscriber under Observation)

3. DIV (For Diverted calls)

4. SPLFTY (For observation of those calls where any special facility is used)

DEFAULT : CLLNG

EXAMPLE : CLLNG & CLLD

REMARK : Set of values allowed. Range is not allowed.

4.2.7. DEL-ALL (Delete all Elements from Observation)

PARAMETER NAME : Delete all Elements from Observation

MNEMONIC : DEL-ALL

TYPE : 3 ASCII (Logical)

POSSIBLE VALUES : 1. Yes 2. No

DEFAULT : No

4.2.8. DEL-DIR (Subscriber Directory Number over which observation is to be stopped)

PARAMETER NAME : Subscriber Directory Number over which observation is to be stopped

MNEMONIC : DEL-DIR

TYPE : 7 Numeric


DEFAULT : 0 (i.e. no. DIRNO is specified.)

EXAMPLE : 5485000 to 5485020 and 5483000

REMARKS : Same as for ADD-DIR

Chapter 4

24 C-DOT DSS MAX

4.2.9. DEL-HGP (Principal directory number of the Hunt Group to be deleted for Observation)

PARAMETER NAME : Principal directory number of the Hunt Group to be deleted to observation

MNEMONIC : DEL-HGP

TYPE : 7 Numeric


DEFAULT : 0 (i.e. no HGP principal directory number is to be deleted from observation).

EXAMPLE : 5485999 & 5485001

REMARK : Range is not allowed. Set is allowed

4.2.10. DEL-ROU(Route code to be deleted from observation)

PARAMETER NAME : Route code to be deleted from observation

MNEMONIC : DEL-ROU

TYPE : 12 Numeric


DEFAULT : 0 (i.e. no route is to be deleted from observation)

EXAMPLE : 01 & 52

REMARK : Range is not allowed Set is allowed.

4.2.11. DEL-TGP (Trunk Group Number over which Observation is to be Stopped)

PARAMETER NAME : Trunk Group Number over which observation is to be stopped

MNEMONIC : DEL-TGP

TYPE : 3 Numeric


DEFAULT : 0. (i.e. no TGP is to be deleted from observation)

REMARK : Range and set of values allowed



4.2.12. DEL-TRK (Trunk Number to be Deleted from Observation)

PARAMETER NAME : Trunk number to be deleted from observation

MNEMONIC : DEL-TRK

TYPE : Same as TEN


DEFAULT : 0-0-0-0-0

REMARKS : Range or set of values allowed.

4.2.13. DIRNO (Directory Number)

PARAMETER NAME : Directory Number

MNEMONIC : DIRNO

TYPE : 7 Numeric

POSSIBLE VALUES : Upto 7-digit number in the range 200 to 8999999, i.e. starting digit is not 0, 1 or 9

DEFAULT : Mandatory parameter. No default value. NONE in DISPL-SUB-TRFINF

EXAMPLE : 5485000 to 5485020 & 5483000

REMARKS : Same as for ADD-DIR

4.2.14. DMP-OPT (Dump Option)

PARAMETER NAME : Dump option for dumping of port counters

MNEMONIC : DMP-OPT

TYPE : 3 ASCII (logical)

POSSIBLE VALUES : 1. YES 2. NO

DEFAULT VALUE : No.

Chapter 4

26 C-DOT DSS MAX

4.2.15. FRM-DATE (Date from which Information is Required)

PARAMETER NAME : Date from which information is Required

MNEMONIC : FRM-DATE

TYPE : 3 subfields, separator character = - Subfield 1, 2 numeric, range 1 31 Subfield 2, 2 numeric, range 1 12 Subfield 3, 4 numeric, range 1970 2036

POSSIBLE VALUES : 1-1-1970 to 31-12-2036

DEFAULT : None.

4.2.16. FRM-TIME (Time since when Information is Required)

PARAMETER NAME : Time since when information is required

MNEMONIC : FRM-TIME

TYPE : 2 Subfields separator character = : Subfield 1, 2 numeric, range 23 Subfield 2, 2 numeric, range 59

POSSIBLE VALUES : 00:00 to 23:59

DEFAULT : 0:0 (i.e. from the current time.)

4.2.17. MOD-NO (Module Number)

PARAMETER NAME : Module Number

MNEMONIC : MOD-NO

TYPE : 5 ASCII

POSSIBLE VALUES : 1. BM-01

2. BM-02

3. BM-03

. . .

32. BM-32

33. AM

34. SUM

DEFAULT : BM-01



4.2.18. OBS-FILT (Filtering for MF Signalling observation)

PARAMETER NAME : Filtering for MF Signalling observation

MNEMONIC : OBS-FILT

POSSIBLE VALUES : IN MOD-TRK-OBS (13 ASCII) 1. NONE 2. ALL 3. SETUP-FAILURE

IN DISPL-MFSA-INF (19 ASCII)

1. ALL

2. FAIL-BWD-SIG-ABS

3. FAIL-BWD-SIG-PRM

4. FAIL-FWD-SIG-PRM

5. FAIL-INV-SIG

6. FAIL-CHG-NUM

7. FAIL-NUM-UNACT

8. FAIL-SUB-LIN-OO-ORD

9. FAIL-SUB-BSY

10. FAIL-CONG

11. FAIL-SIG-FAIL

12. FAIL-IDT

DEFAULT : Mandatory for MOD-TRK-OBS [ALL] for DISPL-MFSA-INF

4.2.19. OBS-PRD (Observation Period)

PARAMETER NAME : Period for which the observation is to remain active

MNEMONIC : OBS-PRD

TYPE : 4 subfields, separator character = : Subfield 1, 2 numeric, range 11 Subfield 2, 2 numeric, range 29 Subfield 3, 2 numeric, range 23 Subfield 4, 2 numeric, range 59

POSSIBLE VALUES : 00:00:00:00 to 11:29:23:59

DEFAULT : 0:0:0:0 (i.e. indefinitely.)

Chapter 4

28 C-DOT DSS MAX

4.2.20. OBS-TYP (Type of Observation to be Displayed)

PARAMETER NAME : Type of traffic observation to be displayed

MNEMONIC : OBS-TYP

TYPE : 6 ASCII

POSSIBLE VALUES : 1. REPORT (Traffic reports which are enabled)

2. SUB (Subscribers which are under Observation)

3. TRUNK (Trunks which are under observation for CER DUMP)

4. TGP (Trunk Group which was under Observation)

* 5. HNT (Hunt Groups which are under Observation)

* 6. ROUT (Destination Code which was under Observation)

DEFAULT : Mandatory parameter. No default value.

REMARK : Set of values allowed. Range not allowed.

4.2.21. OPTION (Output Device Option/s)

PARAMETER NAME : Output device option(s).

MNEMONIC : OPTION

TYPE : 5 ASCII

POSSIBLE VALUES : 1. VDU

2. PRINT

DEFAULT : NONE

REMARK : Set of values also allowed i.e. 1 & 2.



4.2.22. RPT-ID (Report Identity)

PARAMETER NAME : Report Identity

MNEMONIC : RPT-ID

TYPE : 9 ASCII

POSSIBLE VALUES : 1. SRV-CKT (Service Circuit Group)

2. SWT-NET (Switching Network)

3. PRO-REP (Processor)

4. RUT-REP (Route Code Report)

5. IC-TRNK (Incoming Trunk Group)

6. OG-TRNK (Outgoing Trunk Group)

7. ORG-HNT (Hunt Group Report on originating calls))

8. ORG-TRM (Originating and Terminating calls, BM-wise and AM-wise)

9. IC-OG (Incoming and Outgoing calls, BM-wise and AM-wise)

10. EXCH-PER (Exchange performance, BM-wise and AM-wise)

11. SPL-FAC (Special Facilities, BM-wise and AM-wise)

12. DLY-REP (Daily Report)

13. TRM-HNT (Hunt Group Report on Terminating Calls))

14. BW-TRNK

15. DTK

16. LNK-REP

17. RTSET-REP

18. BER-SRVC


REMARKS : Range not allowed. Set of values allowed

Chapter 4

30 C-DOT DSS MAX

4.2.23. RPT-PRD (Periodicity of Report Preparation)

PARAMETER NAME : Periodicity of Report Preparation

MNEMONIC : RPT-PRD

TYPE : 4 Numeric



REMARK : This is the period after which periodic reports are prepared.

4.2.24. RPT-TYP (Report Type)

PARAMETER NAME : Report Type

MNEMONIC : RPT-TYP

TYPE : 9 ASCII

POSSIBLE VALUES : 1. LNE-REP (Line Reports)

2. SPL-FAC (Special Facilities Report)

3. PRO-REP (Processor Report)

4. HNT-REP (Hunt Group Report)

5.* DLY-REP (Daily Report, its periodicity cannot be changed)

6. TRK-REP (Trunk Group Report)

7. RUT-REP (Route Report)

8. SWT-NET (Switching Network Report)

9. SRV-CKT (Service Circuits Report)

10. DTK (Digital Trunk Report)

11. LNK-REP

12. RTSET-REP

13. BER-SRVC

POSSIBLE VALUES (For MOD-SMPLNG-FREQ Command only)

1. HNT-REP 2. TRK-REP 3. SWT-NET 4. SRV-CKT


REMARKS : Set of values allowed Range not allowed.

• DLY-REP is not a valid case in .MOD-RPT-PERDTY]



4.2.25. STP-DTE (Date of Stopping Observation)

PARAMETER NAME : Date of Stopping an Observation

MNEMONIC : STP-DTE

TYPE : 3 subfields, separator character = - Subfield 1, 2 numeric range 1 31 Subfield 2, 2 numeric range 1 12 Subfield 3, 4 numeric range 1970 2036

POSSIBLE VALUES : 1-1-1970 to 31-12-2036

DEFAULT : None

4.2.26. STP-TME (Time of Stopping Observation)

PARAMETER NAME : Time of Stopping a Observation

MNEMONIC : STP-TME

TYPE : 2 subfields, separator character = : Subfield 1, 2 numeric, range 23 Subfield 2, 2 numeric, range 59


DEFAULT : 0:0 (i.e. from the current time, if obs prd is not specified).

4.2.27. SUB-OBS (Subscriber Observation Type)

PARAMETER NAME : Subscriber Observation Type

MNEMONIC : SUB-OBS

TYPE : 10 ASCII

POSSIBLE VALUES : 1. OBS-ORG (Originating Traffic Under Observation)

2. OBS-TRM (Terminating Traffic Under Observation)

3. MAL-OBS (Malicious Call Observation)

* 4. SHRT-MAL

5. SPE-OBS


Chapter 4

32 C-DOT DSS MAX

4.2.28. TEN (Terminal Equipment Number)

PARAMETER NAME : Terminal Equipment Number

MNEMONIC : TEN

TYPE : Five subfields, separator character = -

First subfield, 2 numeric, range 32

Second subfield, 1 numeric, range 3

Third subfield, 1 numeric, range 6

Fourth subfield, 2 numeric, range 26

Fifth subfield, 2 numeric, range 32


DEFAULT : NONE (i.e. TEN not specified.). ALL in DISPL-MFSA-INF.

REMARK : Range and set of values allowed. with separator characters 'to' and '&' respectively.

4.2.29. TGP-NUM (Trunk Group Number)

PARAMETER NAME : Trunk Group Number

MNEMONIC : TGP-NUM

TYPE : 3 Numeric


DEFAULT : 0 (i.e. all TGPs are specified)

4.2.30. TGP-OBS (Type of Trunk Group Observation)

PARAMETER NAME : Type of trunk group observation

MNEMONIC : TGP-OBS

TYPE : 10 ASCII

POSSIBLE VALUES : 1. TGP-RPT (Trunk Group Reports)

*2. CALL-CONST (Call Constitution Observation)

*3. CALL-DSPSN (Call Dispersion Observation)


* Not available presently.



4.2.31. TIM-UNT (Time Unit)

PARAMETER NAME : Time Unit

MNEMONIC : TIM-UNT

TYPE : 3 ASCII

POSSIBLE VALUES : 1. HRS (Hours)

2. MIN (Minutes)


4.2.32. TO-DATE (Date upto which Information is required)

PARAMETER NAME : Date upto which information is required

MNEMONIC : TO-DATE

TYPE : 3 Subfields, separator character = - Subfield 1, 2 numeric range 1 31 Subfield 2, 2 numeric range 1 12 Subfield 3, 4 numeric range 1970 2036

POSSIBLE VALUES : 1-1-1970 TO 31-12-2036

DEFAULT : None

4.2.33. TO-TIME (Time upto which Information is Required)

PARAMETER NAME : Time upto which information is required

MNEMONIC : TO-TIME

TYPE : 2 Subfields, separator character = : Subfield 1, 2 numeric, range 23 Subfield 2, 2 numeric, range 59


DEFAULT : 24:00 (i.e. upto midnight of the TO-DATE or the current time if TO-DATE = current date.)

Chapter 4

34 C-DOT DSS MAX

4.2.34. TRK-OBS (Type of Trunk Observation)

PARAMETER NAME : Type of trunk observation

MNEMONIC : TRK-OBS

TYPE : 10 ASCII

POSSIBLE VALUE : 1. CER-DUMP (Dumping of Call Event Record in case the call lands on the trunk)

2. MF-SIG-ANA



Chapter 5.

Operator Command Sheets

5.1. INTRODUCTION

Operator command sheets are given to help the operating personnel in familiarising themselves with the interactions that take place while issuing various traffic administration commands. At best, they purport to be a WYSIWYG i.e. what you see is what you get, representation of these interactions. The operating personnel can get an idea about the functions that are performed by a traffic administration command, the parameter that are required for its execution, the precautions to be observed and various probable error messages that he or she may encounter and what they mean. Although 'help' is available online, it will always be a help to pre-familiarise oneself before attempting any traffic administration command.

Typically the course of interaction follows this path :

1. Operator issues the appropriate command at the CRP prompt.

2. The system responds with a "parameter entry form" and prompts the operator to fill in the required values for respective parameters. When all the valid parameter values are filled in.

3. The system then asks the operator to give his/her choice as to whether he/she wants to :

Repeat(R), Terminate(T) or Execute(E) the command with the given parameters.

If the operator chooses to :

Repeat(R) - If the command is executed successfully the action returns to the "parameter entry form" and once again step 2 is gone through. But if the command is rejected, on pressing the 'CR' (Carriage Return) the system returns to the CRP prompt.

Chapter 5

36 C-DOT DSS MAX

Terminate(T) - The command is abandoned and system returns to the CRP prompt. It also displays the message "Command Terminated".

Execute(E) - The system displays a temporary message "Executing .....", indicating that it is processing the command. After execution, the system displays the message "Command Executed" and is ready for the issue of next command if the operator so desires. For the commands whose execution entails certain output informations from the system, the result of execution is displayed in the form of "Output Forms" which may come on one or more screens. In case there is any execution error detected by the system, it will respond with an "Error Report". An error report contains the code of the error encountered and a short description of the error. The operator will have to consult the "C-DOT DSS MAX Error Dictionary" for a detailed description of the error and take suitable remedial actions.

Some general comments about the process of execution of traffic administration commands :

• Help is available on the parameter entry form for each of the parameters- essential or non-essential. Typing an 'h' and 'CR' (Carriage Return) will display the help available for that parameter. The parameter value can then be chosen either by selecting the appropriate parameter mnemonic or simply keying in the serial number of the mnemonic in the online help.

• Non-essential i.e. optional parameters are enclosed in square brackets ([]) whereas essential i.e. mandatory parameters are not. The system will assume default values of the non-essential parameters if no value is entered by the operator i.e. just <CR> is pressed.

• Default values of the non-essential parameter are already displayed on the parameter entry form.

• An error message is displayed in case an illegal value is entered for any parameter. The operator may seek on-line help in such a situation.

• Output forms and parameter entry form for each command have a pre-defined structure.

OPERATOR COMMAND SHEETS


• Modify commands are not accepted by the system when the IOP is not in inservice level. (Pl. see "C-DOT DSS MAX Man Machine Communication" document also.)

5.2. OPERATOR COMMAND SHEETS

In the proceeding description, general information, parameter entry form and output forms for each traffic administration command are given. The descriptions of the parameters required for all the commands have already been given in chapter 4.

For purposes of clarity, only representative samples of output forms are described and are meant to give a fair idea about the results that are displayed from each command. For some of the commands, the data may not be valid as applied to a specific site.

The organisation of description for all the command is as follows:

1. General information about the command alongwith precautions and probable errors. Some commands may be supported with description of certain special attributes.

2. Parameter Entry Form.

3. Output Forms (may not be valid for some commands).

Each of these descriptions is identifiable from the header information given. The header is not the system's session header but is used in this document only for uniformly structuring the information pertaining to each command and ease of reference.

All the displays are shown without the session headers and command entry lines. These parts of the display are particular to an exchange and the site of installation and change from one exchange administration to another. For this reason, in the description that follows, these portions are not shown and only the contents of "work window/s" are described.

Chapter 5

38 C-DOT DSS MAX

TRAFFIC ADMINISTRATION COMMAND : Start Traffic Reports

MNEMONIC : START-TRF-RPT CLASS : Update MENU POSITION : 1 9 1

GENERAL INFORMATION

COMMAND : Start Traffic Reports

MNEMONIC : STAR-TRF-RPT

FUNCTION : To start i.e. activate one or more traffic reports

RESULT OF OPERATION : Various traffic reports which have been started are shown with the set periodicity. The periodicity and output options for reports are set by using the appropriate traffic commands.

PRECAUTIONS : This command should be given if the desired reports are not already active. This may be checked by using the appropriate display command i.e. DISPL-TRF-OBS.

REMARKS : The traffic reports enabled by this command will occur after every integral time-multiple of the set periodicity. For example, if a report is enabled at 0900 hours and the periodicity is set at 15 minutes, then the traffic report will be available at 09.15 hours, 09.30 hours, 09.45 hours and so on. However, if the periodicity of the report is changed to 30 minutes, say after 20 minutes of 1000 hrs, then one report will be generated for the 05-minute period (10.15 Hrs to 10.20 Hrs), one report will be generated at 10.30 hrs, and then 30 minutes reports will come i.e. at 11.00 hrs and so on.

The traffic report for trunk groups will not be prepared after execution of this command unless trunk groups for which reports are required are put under observation using "MOD-TGP-OBS" command.

The 'Daily Report' for BMs and exchange will come at 0000 hrs at night (i.e. at midnight) once this traffic report is enabled using this command. Its periodicity is fixed (i.e. 1440 minutes) which can not be changed.

*POSSIBLE ERROR : Report is already active

* Some errors are applicable to all the commands. Examples are: "no such command code", "not all parameters specified", "both DIR and TEN specified", etc. In this document, command execution with valid command syntax and parameters is considered.



TRAFFIC ADMINISTRATION COMMAND :Start Traffic Reports


PARAMETER ENTRY FORM

START-TRF-RPT START TRAFFIC REPORT

RPT-TYP : LNE-REP & SPL-FAC

Chapter 5

40 C-DOT DSS MAX

TRAFFIC ADMINISTRATION COMMAND : Start Traffic Reports


OUTPUT FORM

START A SPECIFIED TYPE OF TRAFFIC REPORT

REPORT TYPE UNIT PERIODICITY*

Line MIN 60

Special_Facility MIN 60

* Assuming that the operator has already set the report periodicity to 60 minutes for these report types by using the command MOD-RPT-PERDTY.

* Errors

Traffic report already on.



TRAFFIC ADMINISTRATION COMMAND : Stop Traffic Reports

MNEMONIC : STOP-TRF-RPT CLASS :Update MENU POSITION : 1 9 2

GENERAL INFORMATION

COMMAND : Stop Traffic Reports

MNEMONIC : STOP-TRF-RPT

FUNCTION : To stop i.e. deactivate one or more traffic reports

RESULT OF OPERATION : List of report types deactivated as a result of this command is displayed.

REMARKS : On execution of this command, traffic reports that were active and are now being disabled, will occur for the last time for the period since they occurred last (before deactivation command was given) until the time of deactivation i.e. execution of this command.

Let us say a report was enabled to occur at 0900 hours, 0930 hours, 1000 hours, and so on with a periodicity of 30 minutes.

The deactivation command is given and executed at 09.50 hours. Clearly, the deactivation command is given and last time the report came was at 09.30 hours. Now, for the period between 09.30hours and 09.50 hours (i.e. 20 minutes), a report will be generated at 09.50 hrs and the report will not be generated further on.

PRECAUTION : This command should be used if the desired report was already active. This may be predetermined by using the appropriate display command (DISPL-TRF- OBS).

POSSIBLE ERROR : Report not active

Chapter 5

42 C-DOT DSS MAX


MNEMONIC STOP-TRF-RPT CLASS : Update MENU POSITION : 1 9 2


STOP-TRF-RPT STOP TRAFFIC REPORTS

RPT-TYP : SWT-NET & SRV-CKT




MNEMONIC : STOP-TRF-RPT CLASS : Update MENU POSITION : 1 9 2

OUTPUT FORM

STOP A SPECIFIED TYPE OF TRAFFIC REPORT

REPORT TYPE UNIT PERIODICITY

Switching_Network MIN 60

Service_Circuit MIN 60

Chapter 5

44 C-DOT DSS MAX

TRAFFIC ADMINISTRATION COMMAND : Modify Report Periodicity

MNEMONIC : MOD-RPT-PERDTY CLASS : Update MENU POSITION : 1 9 4

GENERAL INFORMATION

COMMAND : Modify Report Periodicity

MNEMONIC : MOD-RPT-PERDTY

FUNCTION : To modify the periodicity of a specified report type.

RESULT OF OPERATION : Old and new periodicity of the report/s are displayed.

PRECAUTIONS : • This command should not be used twice within a period of 1 minute.

• Periodicity of "daily report" is always 1440 minutes and cannot be modified.

REMARKS : Similar to the start and stop commands, whenever the periodicity of a traffic report is modified, the very last report will be generated for the period from the last integral time-lapse to the time of execution of this command.

Let us say a report was enabled to occur at 0900 hours, 0930 hours, 1000 hours, and so on with a periodicity of 30 minutes. The periodicity is modified to 15 minutes at 09.20hours. The last report (with 30 minutes periodicity) thus occurred at 0900 hours.

Now, for the period between 0900 hours and 09.20 hours, a report will be generated and henceforth reports will occur at 09.30 hours, 09.45 hours, 10.00 hours, and so on.

Minimum periodicity for any report can be specified to 15 minutes. The periodicity can be specified in multiples of 15 minutes. The periodicity for 'Daily Report' cannot be modified. It is always fixed and has been kept as 1440 minutes. 'Daily Report' will always come at 00.00 hours in the night (i.e., at midnight) once it is started






MOD-RPT-PERDTY MODIFY REPORT PERIODICITY

RPT-TYP : LNE-REP & SPL-FAC

TIM-UNT : MIN

RPT-PRD : 15

Chapter 5

46 C-DOT DSS MAX



OUTPUT FORM

MODIFY PERIODICITY OF A TRAFFIC REPORT

REPORT TYPE UNIT OLD NEW

Line MIN 60 15

Special_Facility MIN 60 15



TRAFFIC ADMINISTRATION COMMAND : Modify Output Option

MNEMONIC : MOD-OUT-OPT CLASS : Update MENU POSITION : 1 9 5

GENERAL INFORMATION

COMMAND : Modify Output Option

MNEMONIC : MOD-OUT-OPT

FUNCTION : To modify output device option i.e. VDU, printer and both VDU and printer, for a specified traffic report.

RESULT OF OPERATION : Old and new options for the specified report types, that are modified, are displayed alongwith the respective reports. The options may be VDU or printer or both VDU and printer.

PRECAUTION : Default output device is the disk.

REMARK : After execution of this command, the reports will be directed to the selected options (devices) also as and when they are sent to the disk.

Chapter 5

48 C-DOT DSS MAX

TRAFFIC ADMINISTRATION COMMAND Modify Output Options for Traffic Reports

MNEMONIC : MOD-OUT-OPT CLASS : Update MENU POSITION : 1 9 5


MOD-OUT-OPT MODIFY OUTPUT OPTIONS FOR TRAFFIC REPORTS

RPT-TYP : LNE-REP & SPL-FAC & PRO-REP

[OPTION] : PRINT & VDU



TRAFFIC ADMINISTRATION COMMAND : Modify Output Options for Traffic Reports

MNEMONIC : MOD-OUT-OPT Class : Update MENU POSITION : 1 9 5

OUTPUT FORM

MODIFY OUTPUT OPTION OF TRAFFIC REPORT

REPORT TYPE OLD NEW

Line VDU PRINT&VDU

Special_Facility VDU PRINT&VDU

Processor VDU PRINT&VDU

Chapter 5

50 C-DOT DSS MAX

TRAFFIC ADMINISTRATION COMMAND : Modify Trunk Group Observation

MNEMONIC : MOD-TGP-OBS CLASS : Update MENU POSITION : 1 9 6

GENERAL INFORMATION

COMMAND : Modify Trunk Group Observation

MNEMONIC : MOD-TGP-OBS

FUNCTION : To start or stop a specified type of observation for a specified trunk group for a specified period.

RESULT OF OPERATION : Trunk groups added or deleted from a particular type of observation is displayed. The old and new periods of observation are also displayed.

PRECAUTIONS : • Atleast one parameter out of ADD-TGP, DEL-TGP and DEL-ALL, must be specified

• Either "Stop-Time and Stop-Date" or "Observation-Period" must be specified. Once given, this stands for the complete observation.

• The trunk group to be put under observation must have already been created.

• No. of trunk groups that can be put under observation is limited by the system load limit.

REMARKS : On putting a trunk group under observation for reports, the reports will start occurring at the set intervals of time (periodicity). The report will be output to the device/s selected alongwith the disk.

When all the three parameter namely, 'OBS-PRD', 'STP-DTE' and 'STP-TME' are given default values while executing "MOD-TGP-OBS" command, then trunk groups specified in the command are put under observation for indefinite time till those trunk groups are removed from the observation list.



TRAFFIC ADMINISTRATION COMMAND : Modify TGP Observation

MNEMONIC : MOD-TGP-OBS CLASS Update MENU POSITION : 1 9 6


MOD-TGP-OBS MODIFY TGP OBSERVATION

[ADD-TGP] : 80 & 81

[DEL-TGP] : 1 & 2

[DEL-ALL] : NO

TGP-OBS : TGP-RPT

[OBS-PRD] : 0:0:0:0

[STP-DTE] : NONE

[STP-TME] : 0:0

Chapter 5

52 C-DOT DSS MAX

TRAFFIC ADMINISTRATION COMMAND : Modify TGP Observation

MNEMONIC : MOD-TGP-OBS CLASS : Update MENU POSITION : 1 9 6

OUTPUT FORM

MODIFY TRUNK GROUP OBSERVATION REPORT

OBS_TYPE = REPORT-OBSERVATION

TRUNK GROUP ADDED TO THE LIST

80

81

TRUNK GROUP DELETED FROM THE LIST

1

2

OLD STOP DATE 0-0-0

OLD STOP TIME 0:0

NEW STOP DATE 0-0-0

NEW STOP TIME 0:0

Errors :

* Add tgp number is already in observation

* Trunk group in add list does not exist.

* Trunk group in delete list is not in observation.



TRAFFIC ADMINISTRATION COMMAND : Modify Subscriber Observation

MNEMONIC : MOD-SUB-OBS CLASS : Update MENU POSITION : 1 9 7

GENERAL INFORMATION

COMMAND : Modify Subscriber Observation

MNEMONIC : MOD-SUB-OBS

FUNCTION : To modify i.e. put or remove one or all subscriber/s from a specified type of observation for a given period of time.

RESULT OF OPERATION : List of subscribers added and/or deleted from a particular category of observation, and, old and new values of the time-period are displayed.

PRECAUTIONS : • Atleast one parameter out of the three ADD-DIR/DEL-DIR/DEL-ALL parameters must be specified.

• The directory number must have already been created.

• Either "Stop-Date" and "Stop-Time" or "Observation-Period" must be specified. Once specified, it stays for the entire observation.

REMARKS : On putting a subscriber under observation for specific type of calls and period, CDRs will be prepared for each of the calls whether successful or not. The CDRs are then stored on the disk.

However, for malicious calls, CDRs are not prepared. Instead, the report is immediately displayed on the OOD terminal, output to the disk and the printer at the end of such calls. This report can also be retrieved from the disk later on for post- processing.

POSSIBLE ERRORS : DIRNO/TEN already under observation

Chapter 5

54 C-DOT DSS MAX




MOD-SUB-OBS MODIFY SUBSCRIBER OBSERVATION

[ADD-DIR] : 543060 & 543045

[DEL-DIR] : 543089

[DEL-ALL] : NO

SUB-OBS : OBS-ORG

[OBS-PRD] : 0:0:0:0

[STP-DTE] : NONE

[STP-TME] : 0:0





OUTPUT FORM

MODIFY SUBSCRIBER OBSERVATION REPORT

OBSERVATION TYPE = SUBSCRIBERS ORIG

SUBSCRIBERS ADDED TO THE LIST

ADDED-DIRNO

[

543060

543045

]

SUBSCRIBERS DELETED FROM THE LIST

DELETED-DIRNO

[

543089

]

OLD STOP DATE 0-0-0

OLD STOP TIME 0:0

NEW STOP DATE 0-0-0

NEW STOP TIME 0:0

Chapter 5

56 C-DOT DSS MAX

TRAFFIC ADMINISTRATION COMMAND : Modify Trunk Observation

MNEMONIC : MOD-TRK-OBS CLASS : Update MENU POSITION : 1 9 8

GENERAL INFORMATION

COMMAND : Modify Trunk Observation

MNEMONIC : MOD-TRK-OBS

FUNCTION : To put trunk/trunks under observation for CER-DUMP for a given period of time.

RESULT OF OPERATION : List of trunks added or deleted from observation, old and new values of the time-period are displayed.

PRECAUTIONS : • At least one parameter must be specified.

• The TEN specified should be an "assigned" trunk TEN.

• Either "Stop-Date" and "Stop- Time" or "Observation-Period" must be specified.

REMARKS : On putting a trunk under observation, CERs for all calls landing on that trunk are dumped onto the disk. CER's are dumped for all types of calls whether successful or not.

POSSIBLE ERRORS : Trunk already under observation

Trunk given for delete is not in observation.






MOD-TRK-OBS MODIFY TRUNK OBSERVATION

[ADD-TRK] : 1-1-1-9-1

[DEL-TRK] : 1-1-1-9-2

[DEL-ALL] : NO

TRK-OBS : CER-DUMP

OBS-FILT : NONE

[OBS-PRD] : 0:0:0:0

[STP-DTE] : 31-12-1997

[STP-TIM] : 1:30

Chapter 5

58 C-DOT DSS MAX



OUTPUT FORM

MODIFY TRUNK OBSERVATION REPORT

OBSERVATION TYPE CER-DUMP

TRUNKS ADDED TO THE LIST

1-1-1-9-1

TRUNKS DELETED FROM THE LIST

1-1-1-9-2

OLD STOP DATE 0-0-0

OLD STOP TIME 0:0

NEW STOP DATE 31-12-1997

NEW STOP TIME 1:30



TRAFFIC ADMINISTRATION COMMAND : Modify Hunt Group Observation

MNEMONIC : MOD-HGP-OBS CLASS : Update MENU POSITION: 1 9 9

GENERAL INFORMATION

COMMAND : Modify Hunt Group Observation

MNEMONIC : MOD-HGP-OBS

FUNCTION : This command is used to add/delete a hunt group or delete all hunt groups from observation.

RESULT OF OPERATION : Display of the hunt group(s) added/deleted or all hunt groups deleted from observation and the period of observation in case of addition.

PRECAUTION : � Out of [OBS-PRD],[STP-DTE] and [STP-TME] only one should be specified. i.e. either [OBS-PRD] or both [STP-DTE] and [STP-TME].

� Out of [HGP], [DEL-HGP] and [DEL-ALL], atleast one must be specified.

� The hunt group should exist

� Number of hunt groups under observation is limited by the system load limit.

REMARK : If [OBS-PRD], [STP-DTE] and [STP-TME] are all default then the hunt group will be put under observation indefinately.

POSSIBLE ERROR : Hunt group may be already under observation if adding is being attempted and vice-versa.

Chapter 5

60 C-DOT DSS MAX




MOD-HGP-OBS MODIFY HUNT GROUP OBSERVATION

[ADD-HGP] : 449999

[DEL-HGP] : 0

[DEL-ALL] : NO

[OBS-PRD] : 0:0:23:0

[STP-DTE] : NONE

[STP-TME] : 0:0

The command, say, was given on 9-3-1998 at 13:10 hrs.





OUTPUT FORM

MODIFY HUNT GROUP OBSERVATION REPORT

PDN(s) ADDED : 449999

OLD STOP DATE : 0-0-0

OLD STOP TIME : 0:0

NEW STOP DATE : 10-3-1995

NEW STOP TIME : 12:10

Note :

If HGP is removed from observation then in place of PDN(s) ADDED,

PDN(s) DELETED will be shown.

Chapter 5

62 C-DOT DSS MAX

TRAFFIC ADMINISTRATION COMMAND : Modify Route Observation

MNEMONIC : MOD-ROUT-OBS CLASS : Update MENU POSITION: 1 9 10

GENERAL INFORMATION

COMMAND : Modify Route Observation

MNEMONIC : MOD-ROUT-OBS

FUNCTION : This command is used to add/delete a route or delete all routes from traffic observation.

RESULT OF OPERATION : Display of the route added/deleted or all routes deleted from observation and the period of observation in case of additions.

PRECAUTION : � Out of [OBS-PRD],[STP-DTE] and [STP-TME] only one should be specified. i.e. either [OBS-PRD] or both [STP-DTE] and [STP-TME].

� Out of [OBS-PRD], and, [STP-DTE] and [STP-TME], only one should be specified general i.e. either [OBS-PRD] or both [STP-DTE] and [STP-TME].

� Out of [ADD-ROUT], [DEL-ROUT] and [DEL-ALL], atleast one must be specified.

� The route should exist

� Number of routes under observation is limited by the system load limit.

REMARK : If [OBS-PRD], [STP-DTE] and [STP-TME] are all default then the route will be put under observation indefinitely.

POSSIBLE ERROR : Route may be already under observation if adding is being attempted and vice-versa.





PARAMETER ENTRY FROM

MOD-ROUT-OBS MODIFY ROUTE OBSERVATION

[ADD-ROU] : 52

[DEL-ROU] : 01

[DEL-ALL] : NO

[OBS-PRD] : 0:0:23:0*

[STP-DTE] : NONE

[STP-TME] : 0:0

* The command, say, was given on 9-3-1998 at 13:10 hrs.

Chapter 5

64 C-DOT DSS MAX



OUTPUT FORM

MODIFY ROUTE OBSERVATION REPORT

ROUTE(s) ADDED : 52

ROUTE(S) DELETED : 01

OLD STOP DATE : 0-0-0

OLD STOP TIME : 0:0

NEW STOP DATE : 10-3-1998

NEW STOP TIME : 12:10



TRAFFIC ADMINISTRATION COMMAND : Display Traffic Observation

MNEMONIC : DISPL-TRF-OBS CLASS : Display MENU POSITION: 1 10 1

GENERAL INFORMATION

COMMAND : Display Traffic Observation

MNEMONIC : DISPL-TRF-OBS

FUNCTION : To display the exchange entities like subscribers, trunk groups, trunks, etc. currently under observation. Enabled reports may also be displayed.

RESULT OF OPERATION : Report for each type of entity under observation. On giving the type option as 'Report', all the traffic reports which are enabled currently are displayed alongwith their respective periodicity and output option.




DISPL-TRF-OBS DISPLAY TRAFFIC OBSERVATION

OBS-TYP : REPORT &SUB &TGP &TRUNK & ROUT & HNT

Chapter 5

66 C-DOT DSS MAX



OUTPUT FORM

Case I :

DISPLAY TRAFFIC OBSERVATION REPORT

OBS_TYPE = REPORT

[REPORT TYPE UNIT PERIODICITY OUTPUT OPTION

Line MIN 60 PRINT&VDU

Special_Facility MIN 60 PRINT&VDU

Processor MIN 60 PRINT&VDU

Daily MIN 1440 NONE

Trunk_Group MIN 120 NONE

Route_Code MIN 60 VDU

Switching_Network MIN 60 VDU

Service_Circuit MIN 60 VDU

]

Case II :

OBSERVATION TYPE = SUBSCRIBERS

[DIRNO TEN OBS_TYPE

543060 12-1-1-10-5 ORIG

543090 12-1-1-20-3 TERM

543045 12-1-2-8-6 ORIG

543040 12-1-2-8-7 ORIG&TERM

]





OUTPUT FORM


OBSERVATION TYPE = SUBSCRIBERS

DISPERSION OBSERVATION = OFF

STOP DATE FOR ORIG OBSERVATION = 21-03-1998

STOP TIME FOR ORIG OBSERVATION = 16:00

STOP DATE FOR TERM OBSERVATION = 21-03-1998

STOP TIME FOR TERM OBSERVATION = 17:00

STOP DATE FOR MALC OBSERVATION = 29-03-1998

STOP TIME FOR MALC OBSERVATION = 23:00

STOP DATE FOR SHRT MALC OBSERVATION = 0-0-0

STOP TIME FOR SHRT MALC OBSERVATION = 0:0

STOP DATE FOR SPEECH OBSERVATION = 0-0-0

STOP TIME FOR SPEECH OBSERVATION = 0:0

Chapter 5

68 C-DOT DSS MAX



OUTPUT FORM

Case III :


OBSERVATION TYPE = TRUNK-GROUP OBSERVATION

TRUNK GROUP NUMBER

80

81

OBSERVATION TYPE = CALL-DISPERSION

TRUNK GROUP NUMBER

0

OBSERVATION TYPE = CALL-CONSTITUTION

TRUNK GROUP NUMBER

0

STOP DATE = 0-0-0

STOP TIME = 0:0

STOP DATE FOR DISPERSION OBSERVATION = 0-0-0

STOP TIME FOR DISPERSION OBSERVATION = 0:0

STOP DATE FOR CONSTITUTION OBSERVATION = 0-0-0

STOP TIME FOR CONSTITUTION OBSERVATION = 0:0



Case IV :


OBSERVATION TYPE = CER DUMP

TRUNKS UNDER OBSERVATION

STOP DATE FOR CER-DUMP OBSERVATION = 0-0-0

STOP TIME FOR CER-DUMP OBSERVATION = 0:0

OBSERVATION TYPE = MF-SIG-ANA

TRUNKS UNDER OBSERVATION

1-1-3-9-1

STOP DATE FOR MF-SIG-ANA OBSERVATION = 0-0-0

STOP TIME FOR MF-SIG-ANA OBSERVATION = 0:0

Case V :


OBSERVATION TYPE = ROUTE CODE UNDER OBSERVATION

ROUTE CODE

009

STOP DATE FOR ROUTE OBSERVATION 30-3-1998

STOP TIME FOR ROUTE OBSERVATION 17:31

Case VI :


OBSERVATION TYPE = HUNT GROUP OBSERVATION

[HUNT GROUP NUMBER(S) OBSERVATION TYPE

6713050 TRAFFIC_OBSERVATION

]

STOP DATE FOR TRAFFIC OBSERVATION = 0-0-0

STOP TIME FOR TRAFFIC OBSERVATION = 0:0

STOP DATE FOR SPEECH OBSERVATION = 0-0-0

STOP TIME FOR SPEECH OBSERVATION = 0:0

Chapter 5

70 C-DOT DSS MAX

TRAFFIC ADMINISTRATION COMMAND : Display Subscriber Traffic Information

MNEMONIC: DISPL-SUB-TRFINF CLASS : Display MENU POSITION: 1 10 2

GENERAL INFORMATION

COMMAND : Display Subscriber Traffic Information

MNEMONIC : DISPL-SUB-TRFINF

FUNCTION : To display the current traffic information on the specified subscriber.

RESULT OF OPERATION : Traffic information on specified directory number/TEN like, total originations, total successful calls, total terminating calls, total outgoing calls and the cause-wise number of call failures are displayed.

PRECAUTION : If both directory number and TEN are given, then the directory number has the overriding priority

REMARK : On execution of this command, traffic information on the desired subscriber/s from 00:00 time to the current time is displayed and will also be dumped onto the disk if the dump option chosen is "YES".

Once this command is executed, all counters of the traffic information will get resetted to zero. Second time when this command will be given on the same day then it will display the traffic information from the time when this command was last given till the time when this command is given second time. Thus for a particular period the traffic information can be collected on a particular line using this command. These per port traffic counters will get resetted to zero automatically at 00.00 hrs daily




MNEMONIC : DISPL-SUB-TRFINF CLASS : Display MENU POSITION: 1 10 2


DISPL-SUB-TRFINF DISPLAY SUBSCRIBER TRAFFIC INFORMATION

[DMP-OPT] : NO

[DIRNO] : 4442062

[TEN] : NONE

Note : This command is allowed only in online mode.

Chapter 5

72 C-DOT DSS MAX


MNEMONIC: DISPL-SUB-TRFINF CLASS : Display MENU POSITION: 1 10 2

OUTPUT FORM

REPORT ON ORIGINATING & TERMINATING CALLS ON A LINE PORT

DIRECTORY NUMBER : 4442062

TERMINAL EQUIPMENT NO : 1-1-2-6-2

REPORT ON ORIGINATING CALLS

Total originating call attempts 8

Total completed calls 2

CALLS RELEASED DUE TO 6

- No digits dialled 0

- IDT 0

- Partial Dialling 0

- Abandonment after dialling complete 0

- Calling subscriber being access barred 0

- Non availability of internal resources 0

- Faulty signalling 0

- Any other reason

REPORT ON TERMINATING CALLS

Total attempts 8

Total completed terminating calls 7

CALLS RELEASED DUE TO

- Subscriber being busy/LLO 0

- Called subscriber maint busy 0

- No answer/Abandoned after dialling complete 1

- Faulty signalling

- User Rejection 0



TRAFFIC ADMINISTRATION COMMAND : Display Trunk Traffic Information

MNEMONIC: DISPL-TRK-TRFINF CLASS : Display MENU POSITION: 1 10 3

GENERAL INFORMATION

COMMAND : Display Trunk Traffic Information

MNEMONIC : DISPL-TRK-TRFINF

FUNCTION : To display traffic information on trunks in a specified trunk group.

RESULT OF OPERATION : Current traffic information on all the trunks in the specified trunk group or only the specified trunks in the trunk group is displayed. Information consists of data like total call requests, total successful calls and number of call failures for various causes of failure.

REMARKS : On execution of this command, traffic information on the trunks, from 00:00 to current time is displayed and will also be dumped onto the disk if the dump option chosen is "YES".

To get information on all the trunks in the trunk group just specify the trunk group number. For individual trunk traffic information, specify the trunk's TEN also.

Once this command is executed, the counter values are resetted to zero after displaying the current traffic information. This command can be used to find out the traffic on a particular trunk for a given period. For example if traffic on a particular trunk is to find out from 12.00 hrs. to 13.00 hrs. Then execute this command for a particular trunk at 12.00 hrs. It will reset all counters to zero. Then execute this command again at 13.00 hrs. Now response will display the traffic information on a specified trunk for a period of 1 hours (from 12.00 hrs to 13 hrs.) These per port traffic counters will get resetted to zero automatically at 00.00 hrs daily

Chapter 5

74 C-DOT DSS MAX




DISPL-TRK-TRFINF DISPLAY TRUNK TRAFFIC INFORMATION

[DMP-OPT : NO

[TGP-NUM] : 0

*[TEN] : 1-1-3-5-1

* Here, traffic information on only one trunk TEN 1-1-3-5-1 is desired. Default option (0) for TGP-NUM has been given.





OUTPUT FORM

REPORT ON INCOMING & OUTGOING CALLS ON A TRUNK PORT

TRUNK GROUP NUMBER 10

TERMINAL EQUIPMENT NO 1-1-3-5-1

REPORT ON INCOMING CALLS

Total incoming call requests 2




- Partial Dialling 0

- IDT 0




- Any other reason

REPORT ON OUTGOING CALLS

Total outgoing call attempts 0

Total completed outgoing calls 0


- Congestion at remote end 0


Chapter 5

76 C-DOT DSS MAX

TRAFFIC ADMINISTRATION COMMAND : Display Call Detail Record

MNEMONIC : DISPL-CDR CLASS : Display MENU POSITION: 1 10 4

GENERAL INFORMATION

COMMAND : Display Call Detail Record

MNEMONIC : DISPL-CDR

FUNCTION : To display Call Detail Record (CDR) of a subscriber.

RESULT OF OPERATION : The record may be prepared for a calling, called, diverted number or special facility subscriber

• Directory number of the subscriber whose CDR is being displayed.

• CDR of the calls involving the subscriber concerned.

PRECAUTION : The directory number specified must have been put under observation in the period specified for displaying CDR.

POSSIBLE ERROR : CDR information not available i.e. the subscriber was not under observation.






DISPL-CDR DISPLAY CALL DETAIL RECORD

DIRNO : 4442061

[CDR-TYP] : CLLNG & CLLD

[FRM-DATE] : NONE

[TO-DATE] : NONE

[FRM-TIME] : 0:0

[TO-TIME] : 24:0

Chapter 5

78 C-DOT DSS MAX



OUTPUT FORM (CALLING)

DISPLAY CALL DETAIL RECORD INFORMATION

CALL DETAIL RECORD TYPE = CLLNG

CALLING SUBSCRIBER DETAILS

DIRECTORY NUMBER = 4442061

TERMINAL EQUIPMENT NO = 1-1-2-6-1

OBSERVATION CLASS = OBS-ORG

CATEGORY = PRIO1

CALL IDENTITY = BM_1

CALL DATE = 10-MAR-1998 14:28:19

Bearer Service AUDIO

CALLED SUBSCRIBER DETAILS



CATEGORY = NOT_APPLICABLE



CALLED SUBSCRIBER PATH DESCRIPTOR

TSS1 IDENTITY = FFFF


TS IDENTITY = 59C

BASE MODULE NUMBER = BM_1

CALLING SUBSCRIBER PATH DESCRIPTOR



TS IDENTITY = 4BD


ORIGINATION TIME = D39154

DIAL TONE CONNECT TIME = D391B8

FIRST DGT RCV TIME = D39B40

LAST DIGIT RECEIVE TIME = D3B250

TONE CONNECT TIME = FFFFFFFF

ANSWER RECEIVED TIME = D3D380

CLEAR FORWARD TIME = D41D18

CLEAR BACKWARD TIME = FFFFFFFF

TSS RELEASE TIME = D41D20

CALL STATUS = NRML_CALL_CLR

METER_COUNT = 19

Chapter 5

80 C-DOT DSS MAX



OUTPUT FORM (CALLED)

DISPLAY CALL DETAIL RECORD INFORMATION

CALL DETAIL RECORD TYPE = CALLED

CALLED SUBSCRIBER DETAILS



OBSERVATION CLASS = OBS-TRM

CATEGORY = PRIO1

CALL IDENTITY = BM_1

CALL DATE = 10-MAR-1998 15:31:06

CALLING SUBSCRIBER DETAILS



CATEGORY = PRIO1

Bearer Service AUDIO

CALLED SUBSCRIBER PATH DESCRIPTOR



TS IDENTITY = 4C0




CALLING SUBSCRIBER PATH DESCRIPTOR



TS IDENTITY = 4BF


TONE CONNECT TIME = 10D3CEC

ANSWER RECEIVED TIME = 10D4DB8

CLEAR FORWARD TIME = 10D7D9C

CLEAR BACKWARD TIME = 10D9793C

TSS RELEASE TIME = 10D7DA6

CALL STATUS = NRML_CALL_CLR



OUTPUT FORM (CALLING)

* CDRs of all the calls originated and terminated from/To 4442061 will be displayed similarly.

Chapter 5

82 C-DOT DSS MAX

TRAFFIC ADMINISTRATION COMMAND : Display Traffic Reports

MNEMONIC : DISPL-TRF-RPT CLASS : Display MENU POSITION: 1 10 5

GENERAL INFORMATION

COMMAND : Display Traffic Report

MNEMONIC : DISPL-TRF-RPT

FUNCTION : To display the specified traffic report from the disk. The reports may be on various entities which were under observation for a certain period of time on specified days.

RESULT OF OPERATION : Traffic report on the chosen entity. Reports may be displayed for Service Circuits, Switching Network, Processors, Incoming Trunks, Outgoing Trunks, Originating and Terminating Calls, Incoming and outgoing calls, Exchange performance, Special Facility and Daily reports.

POSSIBLE ERRORS : • "To Date" less than "From Date"

• “To Time" less than "From Time" (when "To Date" and "From Date" are same)

• No such report i.e. traffic report has not been started on the desired entity.



TRAFFIC ADMINISTRATION COMMAND : Display Traffic Report



DISPL-TRF-RPT DISPLAY TRAFFIC REPORT

RPT-ID : SRV-CKT & SWT-NET & PRO-REP & RUT-REP & IC-TRNK &

OG- TRNK & ORG-TRM & IC-OG & EXCH-PER & SPL-FAC &

DLY-REP & TRM-HNT /7 BW-TRNK & DTK* & LNK-REP &

RTSET-RPT & BER-SRVC

[FRM-DATE] : 10-3-1998

[TO-DATE] : 10-3-1998

[FRM-TIME] : 10:59

[TO-TIME] : 24:0

[MOD-NO] : BM-01 & AM**

* DTK is available only for MBM exchanges.

** AM is not applicable for SBM exchanges.

Chapter 5

84 C-DOT DSS MAX



OUTPUT FORM (SERVICE CIRCUIT GROUPS)

PERIODIC REPORT ON SERVICE CIRCUIT GROUPS

DATE: 10-MAR-1998 11:00:00 OBS DUR: 15minutes

MODULE NO: BM_1

DTMF

Number of circuits assigned 10

Number of circuits operational 10

Number of circuits under maintenance 0

Total seizure attempts 0

Total call failures due to non availability of circuits 0

Traffic intensity (erlangs) 0

Congestion period (sec) 0

Average circuits busy (%) 0

Average circuits out of service (%) 0

MFR












MFS










TEST CIRCUIT










Chapter 5

86 C-DOT DSS MAX



OUTPUT FORM (PROCESSORS)

PERIODIC REPORT ON PROCESSORS

DATE : 10-MAR-1998 14:00:04 OBS DUR : 60 Minutes

PROCESSOR ACTUAL IDLE MESSAGES OCCUPANCY

NUMBER PERIOD TIME (MS.) HANDLED (MS.)

(MS.)

BM_1 3600000 3491055 382507 108945

BMS_1 3594350 2606142 387601 988208

BMS_0 0 0 0 0





OUTPUT FORM (INCOMING TRUNK GROUPS)

PERIODIC REPORT ON IC TRUNK GROUPS

DATE : 10-MAR-1998 14:00:03 OBS DUR: 60minutes

TRUNK GROUP NUMBER 20*





Total number of terminating call attempts 0

Total transit call attempts 0




- Number unobtainable 0

- Wrong prefix 0

- Called subscriber busy 0




- Partial dialling 0


- Any other reason 0

* Such reports will come for all IC trunk groups put under observation.

Chapter 5

88 C-DOT DSS MAX



OUTPUT FORM (OUTGOING TRUNK GROUPS)

PERIODIC REPORT ON OUTGOING TRUNK GROUPS

DATE : 10-MAR-1998 14:00:03 OBS DUR: 60minutes








CALLS FAILED DUE TO


- Non availability of trunk circuits 0


TGP UTILIZATION DATA



Minimum circuits remaining idle (%) 8

Calls overflowing to alternate groups 0

Calls through as first choice 0

Calls through as second choice 0

Calls through as third choice 0

Calls through as fourth choice 0

Calls through as fifth choice 0

Calls through as sixth choice 0

Calls through as seventh choice 0





OUTPUT FORM (ORIGINATING CALLS AND TERMINATING CALLS)

PERIODIC REPORT ON ORIGINATING TRAFFIC & TERMINATING TRAFFIC

DATE: 10-DEC-1996 11:15:00 OBS DUR: 15minutes

MODULE NO: BM_1

REPORT ON PSTN SUBSCRIBERS

Number of lines assigned 15

Number of lines operational 12

Number of lines under maintenance 3


Subscriber dialled call attempts 0

Operator dialling call attempts 0

REPORT ON ISDN SUBSCRIBERS

Number of lines assigned 0




Subscriber dialled call attempts 0

Operator dialled call attempts 0

SYSTEM ORIGINATING CALLS

Total call attempts 0

CALL RELEASED DUE TO


- IDT/Partial dialling 0

- Calling subscriber being access barred 0



Chapter 5

90 C-DOT DSS MAX

REPORT ON ORIGINATING-TERMINATING CALLS


Total local call attempts 0

Total successful calls 0


Subscriber (PSTN/ISDN) terminated call attempts 0

System terminated call attempts 0

Operator terminated call attempts 0


Total local call attempts 0






SYSTEM ORIGINATED CALLS






-- Abandonment after dialling complete 0


- Called subscriber out of order 0

- Called subscriber being access barred 0

- No answer 0


- Called number changed 0




- Non availability of remote unit links 0

- System overload 0



REPORT ON ORIGINATING-OUTGOING CALLS



Total successful outgoing calls 0






SYSTEM ORIGINATED CALLS






- No answer/abandoned after dialling complete 0

- Wrong prefix 0




- System overload 0


Chapter 5

92 C-DOT DSS MAX

- External plant and network reasons





- Any other reason

REPORT ON TERMINATING CALLS




- Subscriber being busy/LLO 0


- No answer/abandoned after dialling complete 0





OUTPUT FORM (INCOMING CALLS AND OUTGOING CALLS)

PERIODIC REPORT ON INCOMING TRAFFIC AND OUTGOING TRAFFIC

DATE: 09-MAR-1998 14:00:56 OBS DUR: 60minutes

MODULE NO: BM_1

Number of trunks assigned 84

Number of trunks operational 54

Number of trunks under maintenance 30






- External plant and network reasons 0




REPORT ON INCOMING-TERMINATING CALLS










- Called subscriber out of order 0

- Called subscriber being access barred 0


- Called number changed 0

Chapter 5

94 C-DOT DSS MAX



- System overload 0



REPORT ON INCOMING-OUTGOING CALLS






- No answer/Abandoned after dialling complete 0

- Wrong prefix 0




- System overload 0


- External plant and network reasons






REPORT ON OUTGOING CALLS






Note : * The Report on outgoing calls will be displayed if in option of [BM-NUM] any AM no. is given if BM-NO is given as option then this report will not be displayed.





OUTPUT FORM (EXCHANGE PERFORMANCE)

PERIODIC REPORT ON EXCHANGE PERFORMANCE

DATE: 10-DEC-1996 11:15:00 OBS DUR: 60minutes

MODULE NO: AM


ORIGINATING TRAFFIC INFORMATION

FOR PSTN SUBSCRIBERS 0


Success rate (%) 0


Outgoing call attempts (%) 0

Outgoing successful call attempts (%) 0

Outgoing completed call attempts (%) 0

Local call attempts (%) 0

Local successful call attempts (%) 0

Local completed call attempts (%) 0

Others (%) 0

Avg. holding time of completed calls (sec) 0

Avg. holding time of uncompleted calls (sec) 0

No. of calls with dial tone delay > 2.5 sec. 0

Calls with dial tone delay between 1 sec and 2.5 sec 0

Avg. dial tone delay (microsec) 0

Avg. ringing signal sending delay (ms) 0

No. of outgoing calls with call setup dely > 800ms 0

Avg. call setup delay (ms) 0

No. of call with call release delay > 600 ms 0

Avg. exchange call release delay (ms) 0

FOR ISDN SUBSCRIBERS


Success rate (%) 0

Chapter 5

96 C-DOT DSS MAX


Outgoing call attempts (%) 0

Outgoing successful call attempts (%) 0

Outgoing completed call attempts (%) 0

Local call attempts (%) 0

Local successful call attempts (%) 0

Local completed call attempts (%) 0

Others (%) 0



Overlap sending

No. of calls with call request delay > 2.5 sec 0

No. of calls with call request delay between 1 sec and 2.5 sec. 0

Avg. call request delay (micro sec) 0

Enbloc sending

No. of calls with call request delay >2.5 sec. 0

No. of calls with call request delay between 1 sec. & 2.5 sec 0


Avg. call indication sending delay (ms) 0

Overlap sending

No. of outgoing calls with call setup delay > 1 sec. 0

Enbloc sending

No. of outgoing calls with call setup delay > 1.2 sec 0


No. of calls with call release delay > 600 ms 0


INCOMING TRAFFIC INFORMATION

Total incoming call attempts 0

Success rate (%) 0


Transit call attempts (%) 0

Transit successful call attempts (%) 0

Transit completed call attempts (%) 0

Terminating call attempts (%) 0

Terminating successful call attempts (%) 0



Terminating completed call attempts (%) 0

Others (%)



No. of transit calls for which exchange call setup delay > 600 ms 0


No. of calls with call release delay > 600 ms 0


Avg. ringing signal sending delay (ms) 0

Chapter 5

98 C-DOT DSS MAX

PERIODIC REPORT ON SPECIAL FACILITIES

DATE : 19-DEC-1998 16:22:36 OBS DUR : 10 minutes

MODULE NO: AM

NO. OF SUBS HAVING THE FOLLOWING FACILITY

Automatic Alarm 0

Outgoing Call Restriction 0

3-Way Conferencing 0

6-Way Conferencing 0

Call Qing with Deactivation 0

Call-waiting cntld. by called subs 0

Call-waiting cntld. by calling subs 0

Div. On busy to a single subs 0

Div. On busy to a Hunt Group 0

Hotline with Timeout 0

Hotline without Timeout 0

Abs. subs div to a manual Annc. 0

Abs. subs div to a fixed Number 0

Abs. subs div to a selected Number 0

Dialling by Equipment Number 0

Intrusion Barring 0

Semi-automatic Alarm 0

INTRUSION BARRING

No. of times activation successful 0

No. of times activation unsuccessful 0

No. of times deactivation successful 0

No. of times deactivation unsuccessful 0



AUTOMATIC ALARM

No. of alarm activation successful 0

No. of alarm activation unsuccessful 0



SEMI AUTOMATIC ALARM

No. of alarm booking requests successful 0

No. of alarm cancellation successful 0

No. of alarms (both types) matured in first try 0

No. of alarms (both types) matured in second try 0

No. of alarms (both types) trials unsuccessful 0

SUBSCRIBER CONTROLLED OUTGOING CALL RESTRICTION





No. of times keyword change successful 0

No. of times keyword change unsuccessful 0

MULTIWAY CALL

No. of times party included in 3-way successful 0

No. of time party included in 3-way unsuccessful 0

No. of times party included in 6-way successful 0

No. of times party included in 6-way unsuccessful 0

No. of times all parties brought in successful 0

No. of times all parties brought in unsuccessful 0

No. of times master toggled successfully 0

No. of times master toggled unsuccessfully 0

No. of party removed successful 0

No. of party removed unsuccessful 0

CALL QUEUEING WITH DEACTIVATION





No. of Queue suspension requests successful 0

No. of Queue suspension request unsuccessful 0

Chapter 5

100 C-DOT DSS MAX

CALL WAITING CONTROLLED BY CALLED SUBSCRIBER

No. of times this facility is used 0

No. of times this facility invocation successful 0

CALL WAITING CONTROLLED BY CALLING SUBSCRIBER

No. of calls failed due to call waiting not allowed 0

DIVERSION ON BUSY TO A SINGLE SUBSCRIBER





No. of calls diverted due to this facility 0

DIVERSION ON BUSY TO A GROUP WITH HUNT FACILITY






HOT LINE WITH TIMEOUT


HOT LINE WITHOUT TIME OUT


ABSENT SUBSCRIBER DIVERSION TO MANUAL ANNOUNCEMENT

No. of times activation successful





OUTPUT FORM (SPECIAL FACILITY, BM)

PERIODIC REPORT ON SPECIAL FACILITIES (Contd...)





ABSENTEE SUBSCRIBER DIVERSION TO FIXED NUMBER






ABSENTEE SUBSCRIBER DIVERSION TO SELECTED NUMBER





No. of calls diverted intra-exchange 0

No. of calls diverted inter-exchange 0

DIALLING BY EQUIPMENT NUMBER

No. of times landing on a line successful 0

No. of times landing on a line unsuccessful 0

No. of times landing on trunk successful 0

No. of times landing on trunk unsuccessful 0

No. of times landing on service ckt successful 0

No. of times landing on service ckt unsuccessful 0

TERMINAL PORTABILITY

Number of call suspensions successful 0

Number of suspended calls resumed 0

CALL HOLD

Number of call hold invocations 0

Chapter 5

102 C-DOT DSS MAX



OUTPUT FORM (DAILY REPORT)

DAILY REPORT ON BASE MODULES

DATE : 11-MAR-1998 00:00:01 OBS DUR: 1440 minutes

MODULE NO: BM_1

Busy hour call attempts (Incoming) 0

Busy hour call attempts (Originating) 0

Busy hour (Incoming) 0

Busy hour (Originating) 0

Day to busy hour ratio 0

DAILY REPORT ON EXCHANGE


MODULE NO: AM

Busy hour call attempts (incoming) 0

Busy hour call attempts (Originating) 448

Busy hour (incoming) 0

Busy hour (Originating) 1945 hrs. - 2045 hrs

Day to busy hour ratio 1





OUTPUT FORM (HUNT GROUP REPORT ON ORIGINATING CALLS)

PERIODIC REPORT ON HUNT GROUPS (ORIGINATING CALLS)


PRINCIPAL DIRECTORY NUMBER 5559999

Number of lines equipped 1






Chapter 5

104 C-DOT DSS MAX



OUTPUT FORM (HUNT GROUP REPORT ON TERMINATING CALLS)

PERIODIC REPORT ON HUNT GROUPS (TERMINATING CALLS)


PRINCIPAL DIRECTORY NUMBER 5559999




Failure due to congestion in line group 0

Failure due to ring time out 0

Failure due to abandonment after dialling completion 0

Any other reason 0


Average waiting time 0

Maximum waiting time 0





OUTPUT FORM (REPORT ON ROUTE CODE)

PERIODIC REPORT ON ROUTE CODE


ROUTE CODE 06



Transit successful call attempts 0

CALLS FAILED DUE TO


- IDT 0



- No answer 0






- System overload 0

- Access barred 0





Grade of service 0

Proportion of call to given destination switched over alternate

trunk group 0

Calls through 1st trunk group 0

Calls through 2nd trunk group 0

Chapter 5

106 C-DOT DSS MAX

Calls through 3rd trunk group 0

Calls through 4th trunk group 0






PERIODIC REPORT ON BOTHWAY TRUNK GROUPS

DATE : 19-DEC-1998 15:42:08 OBS DUR: 1minutes





Number of circuits under LLO 0

Total incoming call attempts 0


Total terminating call attempts 0



INCOMING CALLS FAILED DUE TO


- Wrong prefix 0








OUTGOING CALLS FAILED DUE TO



- Collisions 0


TGP UTILIZATION DATA



Minimum circuits remaining idle (%) 0

Calls overflowing from controlling circuits 0

Calls overflowing from controlled circuits 0

Chapter 5

108 C-DOT DSS MAX

Controlling Circuits :








Controlled Circuits :












OUTPUT FORM (DIGITAL TRUNK)

PERIODIC REPORT ON DIGITAL TRUNK

DATE : 10-JAN-1995 10:46:12 OBS DUR: 15minutes

BM-NO BM_18*

Number of DTKs equipped 32

Number of DTKs operational 30

Number of DTKs under maintenance 2


Total number of successful originating calls 20

Number of originating calls failed due to

- non availability of time slot 20


Total successful terminating calls 0

Number of terminating calls failed due to

- non availability of time slot 0

Traffic intensity on digital links (erlangs) 2

Chapter 5

110 C-DOT DSS MAX

DISPL-TRF-RPT : OUTPUT FORM

RATLAM (TAX-XL)

PERIODIC REPORT ON SIGNALLING LINK

DATE 08-AUG-1997 19:00:16

MODULE NO SUM

Duration Of Observation 56 minutes

Link Set Bundle Number 1

Logical link in the Bundle 0

Number of signalling octets transmitted 44017

Number signalling octets received 15273

Duration of link in the inservice state 3360 Seconds

Duration of link unavailability 0 Seconds

Number of signalling units received in err 0

Duration of link failure 0 Seconds

Number of MSUs dumped due to SL congestion 0

Number of link failures 2

Time of link failure Reason for link failure

18:30:33 High_Bit_Error_Rate

18:38:17 High_Bit_Error_Rate

00:00:00 0

00:00:00 0

00:00:00 0

00:00:00 0

00:00:00 0

00:00:00 0

00:00:00 0

00:00:00 0

.

.



DISPL-TRF-RPT : OUTPUT FORM

PERIODIC REPORT ON SIGNALLING ROUTE SET

DATE 14-MAR-1997 13:30:27

MODULE NO SUM

Duration Of Observation 15 minutes

Destination point code of Routeset 9998

Signalling Network NW-NAT

Signalling Route set number 1

Duration of Unavailability of Routeset 0

Number of Message dumped due to Routing Error 0

Number of times point code became inaccessible 2*

Time when point code became inaccessible 18:30:33

18:38:17

00:00:00

00:00:00

00:00:00

00:00:00

00:00:00

* Since there is only signalling link to DPC 9998, whenever the link fails, this particular destination will become inaccessible.

Chapter 5

112 C-DOT DSS MAX



OUTPUT FORM

PERIODIC REPORT ON BEARER SERVICE

DATE : 23-JUL-1998 10:45:51 OBS DUR: 15minutes

MODULE NO: BM_32

Bearer Service 3.1 Khz AUDIO



Avg. holding time of completed calls (sec.) 10

Avg. holding time of uncompleted calls (sec.) 0

Bearer Service SPEECH





Bearer Service UNRESTRICTED DATA






Appendix - A

Report Fields Description

A.1 INTRODUCTION

In this part of the document, the fields of various traffic reports have been described in order to facilitate a better comprehension of the meaning and utility of the information provided by each traffic report.

The following terminology has been used in the following sections:

ORG-TRM : Originating Terminating

ORG-OG : Originating Outgoing

IC-TRM : Incoming Terminating

IC-OG : Incoming Outgoing (Transit)

IDT : Inter Digit Time

CP Busy : A subscriber line is said to be in 'CP Busy' state if it is : in conversation phase/offhook/dialling or receiving a tone. Similarly a trunk circuit is said to be in 'CP Busy' state from the time it is seized to the time it is released.

Admin Busy (AD-Busy) : A subscriber line will be in 'Admin Busy' state if its status is made BNP-ANNC or BNP-DISC.

The status of any subscriber line is made BNP-ANNC or BNP-DISC using MMC command 'MOD-LIN- STA" only when its services are to be suspended temporarily because of "Bill Not Paid" reason. There will be no dial tone on a subscriber line when its status is made BNP-ANNC or BNP-DISC, instead, an announcement to the effect is fed.

Maintenance Busy : A subscriber line/trunk circuit will be in 'Maintenance Busy' or 'Under Maintenance' if its status is made Out Of Service (OOS). An Out Of Service (OOS) line/trunk may have following status :

i) OOS-OPR

ii) OOS-SE

Appendix - A

114 C-DOT DSS MAX

iii) OOS-EXT

iv) OOS-TST

"OOS-OPR" status of a line or trunk is made by the operator (through a PUT/FORCE-TRM/TGP-OOS command) for maintenance purposes. "OOS-SE' status of a line is made by the system when it finds some exchange side fault e.g. the line card is jacked out without making its lines OOS-OPR. "OOS-EXT" status of INSERVICE lines are made by the system when it finds that their higher order unit (like both copies of TICs) are out of service.

The lines will become INSERVICE from "OOS-EXT' status automatically if one of the TICs in that TU becomes INSERVICE

"OOS-TST" status of line is made by system when it finds that line under test (for example, "TST-TRM" is getting executed for that line).

A.2 PERIODIC REPORT ON ORIGINATING - TERMINATING CALLS (ORG-TRM)

A.2.1 Periodic Report On Originating Traffic

No. Fields Explanations

1.1 REPORT ON PSTN SUBSCRIBERS

1.1.1 No. of lines assigned : It indicates total number of PSTN lines which have been created and assigned directory numbers. These are equal to sum of (No. of Lines Operational) and (No. of lines under Maintenance).

1.1.2 No. of Lines Operational

: It indicates total no. of PSTN lines which have been created and are operational i.e. inservice (INS).

1.1.3 No. of lines under Maintenance

: It indicates total no. of PSTN line Ckts which are unavailable i.e. out of service (OOS).

1.1.4 Total Originating Call Attempts

: It indicates total number of originating calls made from PSTN lines. These are equal to sum of (Subscriber Originated Call Attempts) and (Operator Originated Call Attempts).

1.1.4.1 Subscriber Dialled Call Attempts

: It indicates total number of calls which originated from PSTN subscribers.

1.1.4.2 Operator Dialled Call Attempts

: It indicates total number of calls which originated from operators connected to PSTN lines.

1.2 REPORT ON ISDN SUBSCRIBERS

1.2.1 No. of lines assigned : It indicates total number of ISDN lines which have been created and assigned directory numbers. These are equal to sum of (No. of Lines Operational) and (No. of lines under Maintenance).

REPORT FIELDS DESCRIPTION



1.2.2 No. of Lines Operational

: It indicates total no. of ISDN lines which have been created and are operational i.e. inservice (INS).

1.2.3 No. of lines under Maintenance

: It indicates total no. of ISDN line Ckts which are unavailable i.e. out of service (OOS).


: It indicates total number of originating calls made from ISDN lines. These are equal to sum of (Subscriber Originated Call Attempts) and (Operator Originated Call Attempts).

1.2.4.1 Subscriber Dialled Call Attempts

: It indicates total number of calls which originated from ISDN subscribers.

1.2.4.2 Operator Dialled Call Attempts

: It indicates total number of calls which originated from operators connected to ISDN lines.

1.3 SYSTEM ORIGINATED CALLS

1.3.1 Total Call Attempts : It indicates total number of calls which originated from the system. e.g. maturity of automatic alarms, alarm reporting, forwarded calls, etc.

1.4 CALLS RELEASED DUE TO

1.4.1 No Digits Dialled : The calling subscriber abandoned the call after going off-hook. i.e. Without dialling any digit.

1.4.2 IDT/Partial Dialling i) IDT time out occurs between the 2 consecutive dialled digits and it is not possible with the received digits to determine whether it is an outgoing call, or ii) All digits have not been received for the local calls, or iii) Call was abandoned with number of digits less than digits indicated by system parameter namely "min-subs- dials". See NOTE

1.4.3 Calling Subscriber Access Barred

: The calling subscriber’s request for a service/facility was not authorised e.g. in event of non-payment of dues, request for unsubscribed service, etc. It shall also include calls disallowed due to subscriber initiated outgoing call barring.

1.4.4 Non availability of Internal Resources

: Non-availability of internal paths (time slots) at calling subscriber (i.e. due to internal blocking) which could occur only in case of concentration or all operational DTMF service circuits were busy for making a call from DTMF subscribers.

1.4.5 Any Other Reasons : Calls which do not come in the above reasons e.g., invocation of feature by subscriber like call failing due to recovery because of inconsistent data.

2 REPORT ON ORIGINATING-TERMINATING CALLS


Appendix - A

116 C-DOT DSS MAX


2.1.1 Total Local Call Attempts

: It indicates total no. of ORG-TRM calls i.e. intra-exchange calls which originated from PSTN subscribers/operators. It includes both successful and unsuccessful calls and is equal to sum of (Subscriber Terminated Call Attempts), (System Terminated Call Attempts) and (Operator Terminated Call Attempts).

2.1.2 Total Successful Call Attempts

: It indicates total local calls which originated from PSTN subscribers/operators, for which information about state of called user was received. Apart from completed calls, they include calls released due to

i) abandonment after dialling complete ii) calls to CP busy subscribers iii) calls to subscribers out of order iv) called subscriber being access barred v) no answer at the end of ringing vi) number unobtainable vii) called number changed viii) system terminated calls (e.g. subscriber initiated feature like request for activation/ deactivation of a supplementary service, automatic line testing, calls which get forwarded).

2.1.3 Total Completed Call Attempts

: It indicates total local calls which originated from PSTN subscribers/operators and for which an answer signal was received.

2.1.4 Subscriber Terminated Call Attempts

: It indicates total calls which originated from PSTN subscribers/operators and terminated on a subscriber line (PSTN or ISDN) within the exchange.

2.1.5 System Terminated Call Attempts

: It indicates total calls which originated from PSTN subscribers/operators and terminated on the exchange e.g. due to subscriber initiated feature like activation/deactivation of a supplementary service, alarm monitoring, automatic line testing, calls which get forwarded, etc.

2.1.6 Operator Terminated Call Attempts

: It indicates total calls which originated from PSTN/ISDN subscribers/operators and terminated on a operator connected to PSTN or ISDN line within the exchange.


2.2.1 Total Local Call Attempts

: It indicates total no. of ORG-TRM calls i.e. intra-exchange calls which originated from ISDN subscribers/operators. It includes both successful and unsuccessful calls and is equal to sum of (Subscriber Terminated Call Attempts), (System Terminated Call Attempts) and (Operator Terminated Call Attempts).

2.2.2 Total Successful Call Attempts

: It indicates total local calls which originated from ISDN subscribers/operators, for which information about state of called user was received. Apart from completed calls, they




include calls released due to

i) abandonment after dialling complete ii) calls to CP busy subscribers iii) calls to subscribers out of order iv) called subscriber being access barred v) no answer at the end of ringing vi) number unobtainable vii) called number changed viii) system terminated calls (e.g. subscriber initiated feature like request for activation/ deactivation of a supplementary service, automatic line testing, calls which get forwarded).

2.2.3 Total Completed Calls : It indicates total local calls which originated from ISDN subscribers/operators and for which an answer signal was received.

2.2.4 Subscriber Terminated Call Attempts

: It indicates total calls which originated from ISDN subscribers/operators and terminated on a subscriber line (PSTN or ISDN) within the exchange.

2.2.5 System Terminated Call Attempts

: It indicates total calls which originated from ISDN subscribers/operators and terminated on the exchange e.g. due to subscriber initiated feature like activation/deactivation of a supplementary service, alarm monitoring, automatic line testing, calls which get forwarded, etc.

2.2.6 Operator Terminated Call Attempts

: It indicates total calls which originated from ISDN subscribers/operators and terminated on a operator connected to PSTN or ISDN line within the exchange.

2.3 SYSTEM ORIGINATED CALL

2.3.1 Total successful calls : It indicates the total local calls which originated from the system for which information about state of called user was received.

2.3.2 Total completed Calls : It indicates the total calls which originated from the system & for which an answer signal was received.

2.3.3 Subscriber (PSTN/ ISDN) terminated call attempts

: It indicates the total calls which originated from the system & terminated on a. Subscriber line (PSTN or ISDN)

2.3.4 Operator terminated call attempts

: It indicates total calls which originated from the system & terminated on a operator connected to PSTN or ISDN line within the exchange.


2.4.1 Abandonment after Dialling Complete

: Calls that are abandoned after all digits are dialled i.e. the call is released while it is in ringing phase.

Appendix - A

118 C-DOT DSS MAX


2.4.2 Called Subscriber Busy : Calls made to a subscriber who is CP busy i.e. in conversation/off-hook/dialling/receiving tone phase.

2.4.3 Called Subscriber Out of Order

: Either the called subscriber is maintenance busy due to testing/out of service in which case the called subscriber may be in one of the following status:

i) OOS-OPR ii) OOS-SE iii) OOS-EXT iv) OOS-TST

(Or calls were made to a PSTN subscriber who is in Line Lock out condition i.e. the subscriber went to a passive off-hook state after a threshold time.)

2.4.4 Called Subscriber Access Barred

: Calls made to a subscriber who has calls disallowed due to subscriber initiated incoming call barring or due to non-payment of dues.

2.4.5 No Answer : Calls in which ring time out occurs i.e. No Answer is given.

2.4.6 Number Unobtainable : Calls for which the dialled number is valid in the exchange i.e., number contains the xchg-code but is currently free i.e. not assigned to a subscriber.

2.4.7 Called Number Changed

: Calls for which the dialled number has been changed e.g. due to change in exchange code, or been recently deleted. After a period of time calls to these numbers shall get failed as ‘number unobtainable’.


: Calls failed due to non-availability of internal paths (time slots) at the called subscriber (i.e. due to internal blocking) which could occur only in case of concentration.

2.4.9 Non availability of Remote Unit Links

: Calls failed due to congestion of resources which connect remote unit to the main exchange. NOTE : Either the calling or called subscriber may be on the remote unit.

2.4.10 System Overload : ORIG-TRM calls which were failed due to system overload because for module (BM) to which called subscriber was connected, either CPU idle time had reduced to a threshold value or memory overload had occurred.

2.3.11 Faulty Signalling : Calls failed due to access protocol failures (level 3) at the calling/called ISDN subscriber interface.

2.3.12 Any other Reasons : Calls which have failed, and the failure type is not one of those mentioned above. Some of them are as follows:

i) Failure because of feature interaction.

ii) Calls failing because of nonavailability of 3 way time slot for offering call to busy subscriber.

iii) DBE calls failing due to invalid equipment number/ nonavailability of service circuits.




iv) Calls failing due to user rejection by ISDN subscriber.

3 REPORT ON ORIGINATING-OUTGOING CALLS


3.1.1 Total Outgoing Call Attempts

: It indicates total no. of ORG-OG calls originated from PSTN subscribers/operators. It includes both successful and unsuccessful calls.

3.1.2 Total Successful outgoing Calls

: It indicates total ORG-OG calls which originated from PSTN subscribers/operators, for which information about state of called user was received. Apart from completed calls, they include calls released due to

i) abandonment after dialling complete ii) calls to CP busy subscribers (in the destination exchange) iii) number unobtainable (at succeeding exchange) iv) remote congestion (in the network) v) any other failure (at succeeding exchange)

3.1.3 Total Completed Calls : It indicates total ORG-OG calls which originated from PSTN subscribers/operators and for which an answer signal was received.


3.2.1 Total Outgoing Call Attempts

: It indicates total no. of ORG-OG calls originated from ISDN subscribers/operators.

3.2.2 Total Successful outgoing Calls

: It indicates total ORG-OG calls which originated from ISDN subscribers/operators, for which information about state of called user was received. Apart from completed calls, they include calls released due to

i) abandonment after dialling complete ii) calls to CP busy subscribers (in the destination exchange) iii) number unobtainable (at succeeding exchange) iv) remote congestion (in the network) v) any other failure (at succeeding exchange)

3.2.3 Total Completed Calls : It indicates total ORG-OG calls which originated from ISDN subscribers/operators and for which an answer signal was received.

3.3 SYSTEM ORIGINATED CALLS

3.3.1 Total outgoing call Attempts

: It indicates total number of ORG-OG calls originated from system. It includes both successful & unsuccessful calls.

3.3.2 Total Successful Outgoing Calls

: It indicates total ORG-OG calls which originated from the system for which inf. about state of called user was received. A part from completed calls, they include calls released due to

Appendix - A

120 C-DOT DSS MAX


i) Calls to CP busy sub.

ii) Remote congestion

iii) Any other failure

3.3.3 Total completed outgoing calls

: It indicates total ORG-OG calls which originated from system & for which on answer signal was received.


3.4.1 IDT/Partial Dialling : After number of digits indicated by system parameter namely "min-subs-dial” have been received, i) IDT time out occurs between the 2 consecutive dialled digits, or ii) The calling subscriber abandoned the call without dialling adequate number of digits for a closed numbering route, or iii) Call was abandoned with number of digits less than minimum digits required for routing on the open numbering route.

3.4.2 Abandonment After Dialling Complete/No Answer

: Calls that are abandoned after all digits are dialled i.e. equal to required number of digits on a closed numbering route or greater that minimum digits required for call to be successful on an open numbering route. It also includes calls in which ring time out occurs i.e. No Answer is received.

3.4.3 Wrong Prefix : Calls for which the first few digits of the dialled number don’t correspond to own exchange code or any route existing in the exchange. It also includes calls in which dialled digits contain some invalid digits.

3.4.4 Non availability of Trunk Circuits

: Calls that failed because all trunk circuits of all outgoing trunk groups available in main route as well as in alternate route were busy when outgoing calls were made.


: Calls that failed either due to non-availability of internal paths (time slots) at the outgoing end (i.e. due to internal blocking) which could occur only in case of concentration or if all operational service ckts were busy when outgoing calls are made. e.g. All MF senders may be busy for MF signalling outgoing calls.


: Calls that failed due to congestion of resources which connect remote unit to the main exchange. NOTE : Either the calling subscriber or outgoing trunk may be on the remote unit.

3.4.7 System Overload : ORIG-TRM calls, which were failed due to system overload because for modules (BM) to which outgoing trunks were connected, either CPU idle time had reduced to a threshold value or memory overload had occurred.

3.4.8 Faulty Signalling : Calls failed due to access protocol failures (level 3) at the calling ISDN subscriber or faulty signalling at the outgoing




end due to fault in the network or fault in the switch itself. Some reasons for failure are as follows :

i) Invalid signalling ii) Backward signal permanently present. iii) Backward signal absent.

3.4.9 External Plant and Network Reasons

3.4.9.1 (a) Called Subscriber Busy

: Calls made to a subscriber in succeeding exchange who is CP busy i.e. in conversation/off-hook/dialling/receiving tone phase.

3.4.9.2 (b) Number Unobtainable

: Calls failed from the succeeding exchange due to the dialled number not existing or not being assigned.

3.4.9.3 (c) Remote Congestion : Calls failed due to congestion/fault or lack of resources in the succeeding exchanges.

3.4.9.4 (d) Any Other Reasons : Calls which have failed from the succeeding exchange and the failure type is not one of those mentioned above. Some of them are as follows:

i) Calls failing because of no route to requested transit network/no route to destination. ii) Calls failing due to no response from ISDN user/ ring time out occurs i.e. No Answer is received. iii) Calls failing due to called subscriber out of order. iv) Calls failing due to temporary failure. v) Calls failing due to faulty signalling. vi) Calls failing due to service not available. vii)Calls failing due to incomplete address information. viii)Invalid exchange code/route code.

3.4.10 Any Other Reasons : Calls which have failed, and the failure type is not one of those mentioned above. Some of them are as follows:

i) Calls failing because of outgoing restrictions. ii) DBE calls failing due to invalid equipment number. iii) Calls failing due to junction faulty/spurious ANSWER.

NOTE : "Min-subs-dials" is a system parameter which determines the minimum digits which are to be dialled before routing of the call begins.

Appendix - A

122 C-DOT DSS MAX

PERIODIC REPORT ON ORIGINATING TRAFFIC AND TERMINATING TRAFFIC

This module wise report on originating calls has the following additional fields apart from those in the exchange wise ‘PERIODIC REPORT ON ORIGINATING TRAFFIC’


4 REPORT ON TERMINATING CALLS

4.1 Total Terminating Call Attempts

: Total calls terminating on the module, which is the sum of (total no. of ORG-TRM calls) and (total no. of IC-TRM calls).

4.2 Total Completed Terminating Calls

: Out of the total terminating call attempts, the ones which are answered. i.e. sum of (total no. of completed ORG-TRM calls and total no. of completed IC-TRM calls).

4.3 CALLED RELEASED DUE TO

4.3.1 Subscriber being busy/LLO : Called subscriber in conversation or off-hook or dialling or tone receiving or LLO phase. i.e. Called subscriber is in CP busy state or in LLO state.

4.3.2 Subscriber being Maint Busy

: Called subscriber being maintenance busy.

4.3.3 No Answer/Abandoned after dialling complete

: Total calls that failed due to no answer till ring time out and due to abandonment during ringing phase.



A.3 PERIODIC REPORT ON INCOMING TRAFFIC


1.1 No. of Circuits Assigned : It indicates total number of incoming trunk circuits which have been created and assigned as part of the incoming trunk groups. These are equal to sum of (Number of Circuits Operational) and (Number of Circuits Under Maintenance).

1.2 Number of Circuits Operational

: It indicates total no. of incoming trunk circuits which have been created and are operational i.e. inservice (INS).

1.3 Number of Circuits Under Maintenance

: It indicates total number of incoming trunk circuits which are unavailable i.e. out of service (OOS).

1.4 Total Incoming Call Attempts

: It indicates total incoming calls and is equal to sum of (Total Incoming-Terminating Call Attempts), (Total Transit Call Attempts) and Unsuccessful calls which get failed before it can be determined whether they are terminating or outgoing.


1.5.1 No Digits Dialled : No digits were received from the preceding exchange on the seized incoming trunk.

1.5.2 IDT/Partial Dialling : i) IDT time out occurs between the 2 consecutive digits received and it is not possible with the received digits to determine whether it is a transit call, or ii) All digits have not been received for the IC- TRM calls, or iii) Number of digits received is less than digits indicated by system parameter namely "min-subs- dial".

1.5.3 Nonavailability of Internal Resources

: Non-availability of service circuits at the time of incoming call. e.g. All MF receivers were busy for receiving a call on MF trunks.


1.5.4.1 (a) Faulty Signalling : Calls which failed due to faulty signalling at the incoming end due to fault in the network or fault in the switch itself. The reasons for failure are as follows :

i) Invalid signalling ii) Forward signal permanently present.

1.5.4.2 (b) Any Other Reasons : Calls which do not fail due to faulty signalling.

1.5.5 Any Other Reasons : Calls which do not come in the above needs.

Appendix - A

124 C-DOT DSS MAX


2 REPORT ON INCOMING TERMINATING CALLS

2.1 Total number of Terminating Call Attempts

: It indicates total IC-TRM calls which includes both successful and unsuccessful calls. It is equal to sum of (Subscriber Terminated Call Attempts), (System Terminated Call Attempts) and (Operator Terminated Call Attempts).

2.2 Total Successful Calls : It indicates total IC-TRM calls for which state of called user was received. Apart from completed calls, they include calls released due to

i) abandonment after dialling complete ii) calls to CP busy subscribers iii) calls to subscribers out of order iv) called subscriber being access barred v) no answer at the end of ringing vi) number unobtainable vii) called number changed viii) system terminated calls (e.g. calls on answering circuit, alarm monitoring, calls which get forwarded).

2.3 Total Completed Calls : It indicates total IC-TRM calls which are answered i.e. An ANSWER signal is received.

2.4 Subscriber (PSTN/ISDN) Terminated Call Attempts

: It indicates total incoming calls which terminated on a subscriber line (PSTN or ISDN) within the exchange.

2.5 System Terminated Call Attempts

: It indicates total incoming calls which terminated on the exchange e.g. due to call on an answering circuit, alarm monitoring, calls which get forwarded, etc.

2.6 Operator Terminated Call Attempts

: It indicates total incoming calls which terminated on a operator connected to PSTN or ISDN line within the exchange.


2.7.1 Abandonment after Dialling Complete

: Calls that are abandoned after all digits are received i.e. the call is released while it is in ringing phase.

2.7.2 Called Subscriber Busy : Calls made to a subscriber who is CP busy i.e. in conversation/off-hook/dialling/receiving tone phase.

2.7.3 Called Subscriber Out of Order

: Either the called subscriber is maintenance busy due to testing/out of service in which case the called subscriber may be in one of the following status:

i) OOS-OPR ii) OOS-SE iii) OOS-EXT iv) OOS-TST

Or calls were made to a PSTN subscriber who is in Line Lock out condition i.e. the subscriber went to a passive




off-hook state after a threshold time.

2.7.4 Called Subscriber Access Barred

: Calls made to a subscriber who has calls disallowed due to subscriber initiated incoming call barring or due to non-payment of dues.

2.7.5 Number Unobtainable : It indicates total of incoming calls that have failed because though the called number corresponding to the digits received on incoming trunks is valid in the exchange, it is currently free i.e. not assigned to a subscriber.

2.7.6 Called Number Changed : Calls for which the dialled number has been changed e.g. due to change in exchange code, or been recently deleted. After a period of time calls to these numbers shall get failed as ‘number unobtainable’.


: Calls failed due to non-availability of internal paths (time slots) at the called subscriber (i.e. due to internal blocking) which could occur only in case of concentration.


: Calls failed due to congestion of resources which connect remote unit to the main exchange. NOTE : Either the incoming trunk or called subscriber may be on the remote unit.

2.7.9 System Overload : IC-TRM calls which were failed due to system overload because for module (BM) to which called subscriber was connected, either CPU idle time had reduced to a threshold value or memory overload had occurred.

2.7.10 Faulty Signalling : Calls failed due to faulty signalling at the incoming end or access protocol failures (level 3) at the called ISDN subscriber interface. The reasons for failure at incoming end are as follows :

i) Invalid signalling ii) Forward signal permanently present.

2.7.11 Any other Reasons : Calls which have failed, and the failure type is not one of those mentioned above. Some of them are as follows:

i) Calls failing because of non availability of 3 way time slot for offering call to busy subscriber.

ii) Calls failing due to user rejection by ISDN subscriber.

3 REPORT ON INCOMING OUTGOING CALLS

3.1 Total Transit Call Attempts

: It indicates total number of successful and unsuccessful transit calls.

3.2 Total Successful outgoing Calls

: It indicates total transit calls for which information about state of called user was received. Apart from completed calls, they include calls released due to

i) abandonment after dialling complete

Appendix - A

126 C-DOT DSS MAX


ii) calls to CP busy subscribers (in the destination exchange) iii) number unobtainable (at succeeding exchange) iv) remote congestion (in the network) v) any other failure (at succeeding exchange)

3.3 Total Completed outgoing Calls

: It indicates total transit calls for which an answer signal was received.


3.4.1 IDT/Partial Dialling : After number of digits indicated by system parameter namely "min-subs-dial” have been received, i) IDT time out occurs between the 2 consecutive received digits, or ii) Inadequate number of digits were received for call on a closed numbering route, or iii) Digits received were less than the minimum digits required for routing on the open numbering route.

3.4.2 Abandonment After Dialling Complete/No Answer

: It indicates total of incoming complete calls that have failed due to abandonment of the call after receiving all the digits on incoming trunks i.e. equal to required number of digits on a closed numbering route or greater that minimum digits required for call to be successful on an open numbering route.

3.4.3 Wrong Prefix : Calls for which the first few digits of the number received don’t correspond to own exchange code or any route existing in the exchange. It also includes calls in which the received digits contain some invalid digits.

3.4.4 Non availability of Trunk Circuits

: Calls that failed because all trunk circuits of all outgoing trunk groups available in main route as well as in alternate route were busy when calls were received.


: Calls that failed either due to non-availability of internal paths (time slots) at the outgoing end (i.e. due to internal blocking) which could occur only in case of concentration or if all operational service ckts were busy when calls were received. e.g. All MF senders may be busy for MF signalling outgoing calls.


: Calls that failed due to congestion of resources which connect remote unit to the main exchange. NOTE : Either the incoming or outgoing trunk may be on the remote unit.

3.4.7 Faulty Signalling : Calls failed due to faulty signalling at the incoming/outgoing end due to fault in the network or fault in the switch itself. The reasons for failure are as follows :

i) Invalid signalling ii) Backward signal permanently present.




iii) Forward signal permanently present. iv) Backward signal absent.

3.4.8 System Overload : Transit calls which were failed due to system overload because for modules (BM) to which outgoing trunks were connected, either CPU idle time had reduced to a threshold value or memory overload had occurred.


3.4.9.1 (a) Called Subscriber Busy : Calls made to a subscriber in succeeding exchange who is CP busy i.e. in conversation/off-hook/dialling/receiving tone phase.

3.4.9.2 (b) Number Unobtainable : Calls failed from the succeeding exchange due to the dialled number not existing or not being assigned.

3.4.9.3 (c) Remote Congestion : Calls failed due to congestion/fault or lack of resources in the succeeding exchanges.

3.4.9.4 (d) Any Other Reasons : Calls which have failed from the succeeding exchange and the failure type is not one of those mentioned above. Some of them are as follows:

i) Calls failing because of no route to requested transit network/no route to destination. ii) Calls failing due to no response from ISDN user/ ring time out occurs i.e. No Answer is received. iii) Calls failing due to temporary failure. iv) Calls failing due to faulty signalling. v) Calls failing due to service not available. vi) Calls failing due to incomplete address information.

3.4.10 Any Other Reasons : Calls which have failed, and the failure type is not one of those mentioned above. Some of them are as follows:

i) Calls failing due to junction faulty/spurious ANSWER ii) Dual seizure.

NOTE : "Min-subs-dials" is a system parameter which determines the minimum digits which are to be dialled before routing of the call begins.

Appendix - A

128 C-DOT DSS MAX

PERIODIC REPORT ON INCOMING TRAFFIC AND OUTGOING TRAFFIC

This module wise report on incoming calls has the following additional fields apart from those in the exchange wise ‘PERIODIC REPORT ON INCOMING TRAFFIC’

Fields Explanations

4 REPORT ON OUTGOING CALLS

4.1 Total Outgoing Call Attempts

: Total no. of calls outgoing from the module i.e. sum of (total no. of ORG-OG calls) and (total no. of transit or IC-OG calls)

4.2 Total Completed Outgoing Call Attempts

: Calls outgoing from the module for which answer is received.


4.3.1 Congestion at Remote End : Non availability of resources (time slots, trunks, etc.)/overload at the succeeding exchanges.

4.3.2 Faulty Signalling : Failure due to faulty signalling at the outgoing end due to fault in the network or fault in the switch itself. The reasons for failure are as follows :

i) Invalid signalling ii) Backward signal permanently present. iii) Backward signal absent.



A4. PERIODIC REPORT ON EXCHANGE PERFORMANCE


1.1 Total Call Attempts : Total line originations (PSTN + ISDN) + total IC call requests i.e. equal to (no. of ORG-TRM calls) + (no. of ORG-OG calls) + (no. of IC-TRM calls) + (no. of IC-OG i.e. transit calls) + Unsuccessful calls which cannot be determined to be terminating or outgoing.

2 ORIGINATING TRAFFIC INFORMATION



: Total PSTN line originations i.e. equal to (no. of PSTN ORG-TRM calls) + (no. of PSTN ORG-OG calls) + Unsuccessful PSTN calls which cannot be determined to be terminating or outgoing.

2.1.2 Success Rate (%) : Total PSTN originating (ORG-OG&ORG-TRM)

Successful calls (Total PSTN line originations)

NOTE : For definition of successful calls, refer to points 2.1.2 & 3.1.2 of ‘Periodic report on Originating Traffic’.

2.1.3 Traffic Intensity (erlangs)

:

(Total holding time of PSTN (ORG-OG) Calls in secs + Total holding time of PSTN (ORG-TRM) Calls in secs)

Report period (in secs)

2.1.4 Originating-Outgoing Call Attempts (%)

:

(Total PSTN ORG-OG calls) *100 (Total PSTN line originations)

2.1.4.1 Outgoing Successful Calls (%)

:

(Total PSTN ORG-OG Successful calls) *100 (Total PSTN line originations)

2.1.4.2 Outgoing Completed Calls (%)

:

(Total PSTN ORG-OG Completed calls) *100 (Total PSTN line originations)

2.1.5 Local Call Attempts (%)

:

(Total PSTN ORG-TRM calls) *100 (Total PSTN line originations)

2.1.5.1 Local Successful Calls (%)

:

(Total PSTN ORG-TRM Successful calls) *100 (Total PSTN line originations)

2.1.5.2 Local Completed Calls (%)

:

(Total PSTN ORG-TRM Completed calls) *100 (Total PSTN line originations)

Appendix - A

130 C-DOT DSS MAX


2.1.6 Others (%) :

(Total PSTN line originations

- Total PSTN (ORG-TRM&ORG-OG) calls) (Total PSTN line originations)

2.1.7 Avg. Holding Time of Completed Calls (Sec)

:

(Total holding time of completed PSTN ORG-OG calls in secs + total holding time of completed PSTN ORG-

TRM calls in secs) (Total no. of completed PSTN ORG-OG calls + Total no. of completed PSTN ORG-TRM calls).

2.1.8 Avg. Holding Time of Uncompleted Calls (Sec)

:

(Total holding time of uncompleted PSTN ORG-OG calls in secs + total holding time of uncompleted PSTN ORG-

TRM calls in secs) (Total no. of uncompleted PSTN ORG-TRM calls + Total no.

of uncompleted PSTN ORG-OG calls).

2.1.9 No. of Calls with dial tone delay >2.5 sec

: It indicates the number of PSTN originations for which the time between off-hook and reception of dial tone was greater than 2.5 seconds. It is mostly due to non availability of resources.

2.1.10 No. of calls with dial tone delay between 1 sec and 2.5 sec

: It indicates the number of PSTN originations for which the time between off-hook and reception of dial tone was between 1 and 2.5 seconds.

2.1.11 Avg. Dial Tone Delay (ms)

: (Total dial tone delay observed in all PSTN line originations) (Total PSTN line originations)

2.1.12 Avg. Ringing Signal Sending Delay (ms)

: (Total ringing signal sending delay for PSTN calls in ms) (Total no. of PSTN calls for which ringing has been fed)

2.1.13 No. of Outgoing Calls with Call Setup Delay > 800ms

: It indicates number of PSTN ORG-OG calls for which call setup delay is greater than 800ms.

2.1.14 Avg. Call Setup Delay (ms)

: (Total Call Setup delay observed in all PSTN ORG- OG calls) (Total PSTN ORG-OG calls)

2.1.15 No. of Calls with Call Release delay > 600ms

: It indicates number of PSTN ORG-TRM&ORG-OG calls for which call release delay is greater than 600ms.

2.1.16 Avg. Call Release Delay (ms)

:

(Total call release delay) in ms observed in all successful PSTN calls

(Total successful PSTN calls)



: Total ISDN line originations i.e. equal to (no. of ISDN ORG-TRM calls) + (no. of ISDN ORG-OG calls) + Unsuccessful ISDN calls which cannot be determined to be terminating or outgoing.




2.2.2 Success Rate (%) : Total ISDN originating (ORG-OG&ORG-TRM)

Successful calls (Total ISDN line originations)

NOTE : For definition of successful calls, refer to points 2.2.2 & 3.2.2 of ‘Periodic report on Originating Traffic’.

2.2.3 Traffic Intensity (erlangs)

:

(Total holding time of ISDN (ORG-OG) Calls in secs + Total holding time of ISDN (ORG-TRM) Calls in secs)

Report period (in secs)

2.2.4 Originating-Outgoing Call Attempts (%)

:

(Total ISDN ORG-OG calls) *100 (Total ISDN line originations)

2.2.4.1 Outgoing Successful Calls (%)

:

(Total ISDN ORG-OG Successful calls) *100 (Total ISDN line originations)

2.2.4.2 Outgoing Completed Calls (%)

:

(Total ISDN ORG-OG Completed calls) *100 (Total ISDN line originations)

2.2.5 Local Call Attempts (%)

:

(Total ISDN ORG-TRM calls) *100 (Total ISDN line originations)

2.2.5.1 Local Successful Calls (%)

:

(Total ISDN ORG-TRM Successful calls) *100 (Total ISDN line originations)

2.2.5.2 Local Completed Calls (%)

:

(Total ISDN ORG-TRM Completed calls) *100 (Total ISDN line originations)

2.2.5 Others (%) :

(Total ISDN line originations

- Total ISDN (ORG-TRM&ORG-OG) calls) (Total ISDN line originations)

2.2.7 Avg. Holding Time of Completed Calls (Sec)

:

(Total holding time of completed ISDN ORG-OG calls in secs + total holding time of completed ISDN ORG-

TRM calls in secs) (Total no. of completed ISDN ORG-OG calls + Total no. of completed ISDN ORG-TRM calls).

2.2.8 Avg. Holding Time of Uncompleted Calls (Sec)

:

(Total holding time of uncompleted ISDN ORG-OG calls in secs + total holding time of uncompleted ISDN ORG-

TRM calls in secs) (Total no. of uncompleted ISDN ORG-TRM calls +

Total no. of uncompleted ISDN ORG-OG calls).

2.2.9 No. of Calls with Call Request delay >2.5 sec (Overlap Sending)

: It indicates the number of ISDN originations for which the time between receiving SETUP message and passing back of SETUP ACKNOWLEDGE message was greater than 2.5 seconds. It is mostly due to non availability of resources.

Appendix - A

132 C-DOT DSS MAX


2.2.10 No. of calls with Call Request delay between 1 sec and 2.5 sec (Overlap Sending)

: It indicates the number of ISDN originations for which the time between receiving SETUP message and passing back of SETUP ACKNOWLEDGE message was between 1 and 2.5 seconds.

2.2.11 Avg. Call Request Delay (ms) (Overlap Sending)

: (Total Call Request delay observed in all ISDN line originations using overlap sending procedures) (Total ISDN line originations using overlap sending procedures)

2.2.12 No. of Calls with Call Request delay >2.5 sec (Enbloc Sending)

: It indicates the number of ISDN originations for which the time between receiving SETUP message and passing back of CALL PROCEEDING message was greater than 2.5 seconds. It is mostly due to non availability of resources.

2.2.13 No. of calls with Call Request delay between 1.2 sec and 2.5 sec (Enbloc Sending)

: It indicates the number of ISDN originations for which the time between receiving SETUP message and passing back of CALL PROCEEDING message was between 1 and 2.5 seconds.

2.2.14 Avg. Call Request Delay (ms) (Enbloc Sending)

: (Total Call Request delay observed in all ISDN line originations using enbloc sending procedures) (Total ISDN line originations using enbloc sending procedures)

2.2.15 Avg. Call Indication Sending Delay (ms)

: (Total Call Indication sending delay for ISDN calls in ms) (Total no. of ISDN calls for which ringing has been fed)

2.2.16 No. of Outgoing Calls with Call Setup Delay > 1 sec (Overlap Sending)

: It indicates number of ISDN ORG-OG calls for which call setup delay is greater than 1 second.

2.2.17 No. of Outgoing Calls with Call Setup Delay > 1.2 sec (Enbloc Sending)

: It indicates number of ISDN ORG-OG calls for which call setup delay is greater than 1.2 seconds.

2.2.18 Avg. Call Setup Delay (ms)

: (Total Call Setup delay observed in all ISDN ORG-OG calls) (Total ISDN ORG-OG calls)

2.2.19 No. of Calls with Call Release delay > 600ms

: It indicates number of ISDN ORG-TRM&ORG-OG calls for which call release delay is greater than 600ms.

2.2.20 Avg. Call Release Delay (ms)

:

(Total call release delay) in ms observed in all successful ISDN calls

(Total successful ISDN calls)

3 INCOMING TRAFFIC INFORMATION

This includes information relating to all incoming calls.

3.1 Total Incoming Call Attempts

: Total incoming calls i.e. equal to (no. of IC-TRM calls) + (no. of IC-OG calls) + Unsuccessful incoming calls which cannot




be determined to be terminating or outgoing.

3.2 Success Rate (%) : Total incoming (IC-OG&IC-TRM)

Successful calls *100 (Total incoming calls)

NOTE : For definition of successful calls, refer to points 2.2 & 3.2 of ‘Periodic report on Incoming Traffic’.

3.3 Traffic Intensity (Erlangs)

: Total holding time of IC-TRM and IC-OG calls (in secs.) Report period (in secs.)

3.4 Transit Call Attempts (%)

:

(Total IC-OG calls) *100 (Total incoming calls)

3.4.1 Transit Successful Call Attempts (%)

:

(Total IC-OG Successful calls) *100 (Total incoming calls)

3.4.2 Transit Completed Call Attempts (%)

:

(Total IC-OG Completed calls) *100 (Total incoming calls)

3.5 Terminating Call Attempts (%)

:

(Total IC-TRM calls) *100 (Total incoming calls)

3.5.1 Terminating Successful Calls (%)

:

(Total IC-TRM Successful calls) *100 (Total incoming calls)

3.5.2 Terminating Completed Calls (%)

:

(Total IC-TRM Completed calls) *100 (Total incoming calls)

3.6 Others (%) :

Total incoming calls -

Total (IC-TRM&IC-OG) calls *100 (Total incoming calls)

3.7 Avg. Holding Time of Completed Calls (Sec)

:

(Total holding time of completed IC-TRM calls in secs + total holding time of completed IC-OG calls in secs)

(Total no. of completed IC-TRM calls + Total no. of completed IC-OG calls).

3.8 Avg. Holding Time of Uncompleted Calls (Sec)

:

(Total holding time of uncompleted IC-TRM calls in secs + total holding time of uncompleted IC-OG calls in secs)

(Total no. of uncompleted IC-TRM calls + Total no. of uncompleted IC-OG calls).

3.9 No. of Transit Calls with Call Setup Delay > 600ms

: It indicates number of IC-OG calls for which call setup delay is greater than 600ms.

3.10 Avg. Call Setup Delay (ms)

: (Total Call Setup delay observed in all Transit calls) (Total transit calls)

Appendix - A

134 C-DOT DSS MAX


3.11 No. of Calls with Call Release delay > 600ms

: It indicates number of IC-TRM&IC-OG calls for which call release delay is greater than 600ms.

3.12 Avg. Call Release Delay (ms)

:

(Total call release delay) in ms observed in all successful incoming calls (Total successful incoming calls)

3.13 Avg. Ringing Signal Sending Delay (ms)

: (Total ringing signal sending delay for incoming calls in ms) (Total no. of incoming calls for which ringing has been fed)

A.5 PERIODIC REPORT ON SERVICE CIRCUITS (SRV-CKT)

DTMF/MFR/MFS/TEST CIRCUIT

No. of Ckts. Assigned : Total number of service circuits of this type available. These circuits were equipped. Their number includes both operational and "out of service" circuits.

No. of Ckts. Operational : Total number of circuits, which are assigned and are operational. Thus, their no. is equal to (no. of ckts. assigned)-(no. of ckts. under maintenance).

No. of Ckts. Under Maintenance : Total number of circuits which are unavailable i.e. out of service. Their no. = (No. of Ckts. Assigned) - (No. of Ckts. Operational).

Total Seizure Attempts : Total number of times a specific type of SRV-CKT was (attempted) tried to be seized. It includes all successful and unsuccessful attempts at seizure.

Total Call Failures Due to non-availability of Circuits

: Total no. of calls which had failed due to non-availability of a specific type of service circut. The non-availability might have been due to all operational circuits being busy or their being no circuits operational.

Traffic Intensity (E, erlangs) : Summation of time periods for which a specific type of SRV-CKT was used during a report period in sec. E Report period of the traffic report in secs

It can also be defined as Total no. of Circuits found busy on each sampling Total no. of times sampled



Congestion Period (seconds) : Time for which all service circuits of a specific type were busy during the period of the traffic report. OOS circuits are also counted as busy.

Example: Report Periodicity = 60 minutes sampling Interval = 15 minutes At Time=0, all ckts. (DTMF, Say) Found busy, Counter=0+1=1 (Initial) At Time=15, only 9 out of 10 ckts were busy. Counter=1 (no change) Similarly: At time=30, all busy; Counter=1+1=2 At time=45, all busy; Counter=2+1=3 At time=60, 8/10 busy; Counter=3 Then: Congestion Period = 3x15 min. or 45x60 seconds

Circuits Busy %

:

(The average number of circuits found busy during sampling instants) x 100 (Total no. of Operational Circuits)

Example Total no. of Ckts = 10(say) Sampling instant no. of ckts (1 sec. each) busy 1 3 2 7 3 7 4 6 5 5 Total = 28

Avg. = 28/5 = 5.6 Circuits Busy = 5.6/100/10= 56% (%)

Circuits Out of Service (% )

:

The avg. no. of circuits found out of service (i.e. assigned - operational during report period) x 100 (Total no. of circuits assigned) (Calculated the same way as above for Circuits Busy (%))

Appendix - A

136 C-DOT DSS MAX

A.6 PERIODIC REPORT ON SWITCHING NETWORK (SWT-NET)

Total Seizure Attempts : The total number of times any of the 128 channels on a particular 128-Channel link was seized.

No. of seizure failures : The total number of times the attempts to seize any of the 128 channels on a particular 128- channel link failed due to the channel being busy or out of order.

Occupancy (%) : Average number of channels found busy during sampling instants.

Example : Total Channels = 128 Sampling instant no. of chnls 1 20 2 47 3 53 4 40 5 40 Total = 200 Avg. = 200/5 = 40 Occupancy = 40%

Congestion Period : Average time for which all 128 channels of the link were found busy during sampling.

A.7 PERIODIC REPORT ON OUTGOING TRUNK GROUP (OG-TRNK)

Note : In the definition of parameters of outgoing trunk group report "desired outgoing trunk group" refers the outgoing (OG) trunk group for which report is generated.

Trunk Group Number : It indicates the outgoing trunk group for which report is generated.

Number of Circuits Assigned : It indicates total number of trunk circuits assigned to a desired outgoing trunk group. It should be equal to sum of operational circuits and circuits under maintenance.

Number of Circuits Operational : Total number of circuits which are assigned and operational.

Number of Circuits Maintenance : Total number of circuits which are out of service.

Total Seizure Attempts : Total number of successful and unsuccessful attempts made through the trunks of the desired OG trunk group by the :



i) Operator (Operator Dialled Call Attempts)

ii) Subscribers (Subscribers Dialled Call Attempts)

iii) Other Exchange (Transit Call Attempts) (IC-OG)

Total Transit Call Attempts : Total number of transit call attempts (IC-OG calls) passed through the trunks of desired OG trunk group.

Total Successful Calls : Total number of various types of successful calls (operator, subscribers dialled and transit) passed through trunks of desired outgoing trunk group during the period of the traffic report.

Operator Dialled Call Attempts : It indicates total number of operator dialled call attempts (successful and unsuccessful) passed via trunks of desired outgoing trunk group.

Subscriber Dialled Call Attempts : It indicates total number of subscriber dialled call attempts (successful and unsuccessful) passed via trunks of desired outgoing trunk group.

Traffic Intensity (erlangs) : Same explanation as for service circuits.

Congestion Period (sec) : Same explanation as for service circuits.

Minimum no. of circuits Remaining Idle : Minimum no. of circuits found idle during sampling instants within the period of the traffic report. Example : Total O/G trunks = 20 (say) Sampling instant No. of ckts Idle 1 10 2 5 3 7 4 3 5 6

Minimum number = 3 Minimum number of circuits remaining idle = 3

Calls Failing with Busy Signal : It includes total number of calls failing with busy signal (called party busy) and are passing through trunks of desired trunk group. It includes ORG-OG calls and IC-OG calls.

Calls Overflowing to Alternate Groups : It indicates the total number of calls overflowing to alternate trunk groups from the desired OG trunk group (for which report is generated) in all the routes where this desired OG trunk group is associated. For example, if

Appendix - A

138 C-DOT DSS MAX

O/G trunk group number 21, is associated with route 60 and 61 in the choices as shown below :

Route 60 TGP-CHC = 1-21-10-31 & 2-10-21-31 Route 61 TGP-CHC = 1-10-21-31 & 2-21-10-31 Where outgoing trunk group number 10 and 31, are other choices. In the report of outgoing trunk group 21, calls overflowing to alternate group = Sum of following calls.

i) Calls (successful and unsuccessful originated from subscribers (having priority 1) and calls (successful and unsuccessful) coming from IC trunks (having priority 1) for route 60 passing through the outgoing trunk group 10 and 31 when trunk group 21 used in 1st choice is not having any free trunk.

ii) Calls (successful and unsuccessful) originated form subscribers (having priority 2) and calls (successful and unsuccessful) coming from IC trunks (having priority 2) for route 60 passing through the outgoing trunk group 31 when trunk group 21 used in 2nd choice is not having any free trunk.

iii) Calls (successful and unsuccessful) originated from subscribers (having priority 1) and calls (successful and unsuccessful) coming from IC trunks (having priority 1) for route 61 passing through the trunks of outgoing trunk group 31 when OG trunk group 21 used in 2nd choice is not having any free trunk.

iv) Calls (successful and unsuccessful) originated from subscribers (having priority 2) and calls (successful and unsuccessful) coming from IC trunk (having priority 2) for route 61 passing through the trunks of outgoing trunk group 10 and 31 when OG trunk group 21 used in 1st choice is not having any free trunk.

Calls Failing with Other Reasons : It indicates those outgoing calls (ORG-OG and IC-OG) which had failed due to following reasons and gone through the trunks of desired outgoing trunk group

a) Ring timeout



b) Called number was unobtainable i.e. non-existing or in frozen list.

c) Called number was in LLO state

d) Called number was access barred.

e) Signalling failure

f) Invalid signalling

g) Backward signal permanent

h) Forward signal permanent

i) Backward signal absent

j) Congestion in trunk

k) Remote congestion

l) Junction faulty

m) Blocking

n) Dual seizure

o) Spurious answer etc.

Calls through as First Choice : It indicates the total number of calls (successful and unsuccessful) that passed through the desired OG trunk group (for which report is generated) in all the routes where this trunk group is used as first choice trunk group in "TGP-CHC" parameter for all the priorities.

Calls through as Second Choice : It indicates the total number of calls (successful and unsuccessful) that passed through the desired OG trunk group (for which report is generated) in all the routes where this trunk group is used as second choice trunk group in "TGP-CHC" parameter for all the priorities.

Note : Similarly "Calls through other choices" are also defined.

Appendix - A

140 C-DOT DSS MAX

A.8 PERIODIC REPORT ON INCOMING TRUNK GROUP (IC-TRNK)

Note : In the definition of the parameters of this report "desired incoming trunk group" has been used to indicate the incoming trunk group for which this report has been generated.

Trunk Group Number : It indicates the incoming trunk group number for which this report has been generated.

Number of Circuits Assigned : It indicates the total number of trunk circuits assigned to the desired incoming trunk group and is equal to sum of number of circuits operational and number of circuits under maintenance.

Number of Circuits Operational : It indicates those assigned trunk circuits of the desired incoming trunk group which were operational.

Number of Circuits Under Maintenance : It indicates those circuits which have been assigned to the desired incoming trunk group and are out of service is i.e. maintenance busy.

Total Seizure Attempts : Total number of successful and unsuccessful Incoming Terminating (IC-TRM) and Incoming Outgoing (IC- OG) calls that passed through the trunks of desired incoming trunk group.

Total Incoming Call Attempts : It indicates the total successful and unsuccessful incoming terminating (IC-TRM) calls that passed through the trunks of desired incoming trunk group.

Total Transit Call Attempts : It indicates the total successful and unsuccessful transit (IC-OG) calls that passed through the trunks of desired incoming trunk group.

Total Successful Calls : It indicates the total successful incoming terminating (IC-TRM) and incoming outgoing (IC-OG) calls that passed through the trunks of desired incoming trunk group.

Traffic Intensity (erlangs) : Same explanation as given in the report on Service Circuits (SRV-CKT)

CALLS FAILED DUE TO

Number Unobtainable : It indicates the total number of incoming calls (IC-TRM and IC-OG) which had failed due to the reason that called number was not existing or was in frozen list and had passed through the trunks of the desired incoming trunk group.



Wrong Prefix : It indicates the total number of incoming calls (IC-TRM and IC-OG) which had failed due to wrong prefix in the dialled number and had passed through the trunks of the desired incoming trunk group. Wrong prefix means that first few digits of the dialled numbers are wrong. These could be an invalid exchange code or route code.

Called Subscriber Busy : It indicates the total number of those incoming (IC-TRM and IC-OG) calls which had failed due to the reason that the called subscriber being busy and had passed through the trunks of the desired incoming trunk group.

Called Subscriber Admin Busy : It indicates the total number of those incoming (IC-TRM and IC-OG) calls which had failed due to the reason that the called subscriber was Admin busy and had passed through the trunks of the desired incoming trunk group.

Called Subscriber Maintenance Busy : It indicates the total number of those incoming (IC-TRM and IC-OG) calls which had failed due to called subscriber being Maintenance busy and has passed through the trunks of the desired incoming trunk group.

Abandonment after Dialling Complete : It indicates the total number of those incoming (IC-TRM and IC-OG) calls which had failed due to abandonment of the call after receiving all the digits on the trunks of the desired incoming trunk group.

No Digits Dialled : It indicates the total number of seizures on trunks of desired incoming trunk group without receiving any digit.

Partial Dialling (one digit) : It indicates the total number of those incoming calls which were released due to partial dialling (i.e. one digit or digits less than the digits indicated by "min-subs dials" system parameter received on trunks of the desired incoming trunk group).

Partial Dialling (more than one digit) : It indicates the total number of those incoming calls which were released due to partial dialling (i.e. digits equal to or more than the digits indicated by "min-subs- dials" system parameter received on trunks of the desired incoming trunk group).

Congestion in Switch : It indicates the total number of those incoming calls (IC-TRM & IC- OG) which had failed due to internal congestion in switch and has passed through the trunks of the desired incoming trunk group.

Appendix - A

142 C-DOT DSS MAX

Any other Reason : It indicates the total number of incoming calls (IC-TRM & IC-OG) which had failed due to any of the following reasons and had passed through the trunks of the desired incoming trunk group.

a) Ring timeout

b) Called number was in line lockout (LLO) state

c) Called number was access barred

d) Signalling failure

e) Invalid signalling

f) Backward signal permanent

g) Forward signal permanent

h) Backward signal absent

i) Resource not allocated

j) Congestion in trunk

k) Remote congestion (in transit calls)

l) Outgoing restriction (in transit calls)

m) Junction faulty

n) Blocking

o) Spurious answer

p) Overload

q) Dual seizure



A.9 DAILY REPORT (DLY-REP)

Note : Daily report comes once in a day at midnight. Its periodicity is 24 hours and cannot be modified.

Day to Busy Hour Ratio : It indicates the ratio of total call attempts made during the whole day and call attempts made during the Busy Hour.

Busy Hour : Busy Hour is that 60 minute period during which the exchange experienced max. number of call attempts, incoming and/or originating. For example, if 15 minute samples are collected for the full day then the consecutive 4 samples which have the max. total no. of call attempts is termed as the Busy Hour as illustrated below.

15 Min. Period Call Attempts Call Attempts Attempts Hour

00:00 to 00:15 400 0:15 to 0:30 500 0:30 to 0:45 300 0:45 to 1:00 200 1400 1:00 to 1:15 800 1800 1:15 to 1:30 700 2000 1:30 to 1:45 600 2300 . . . . etc. etc.

The Busy Hour in this case will be 00:45 to 01:45 hours. If it is calculated for I/C calls then it is called Busy Hour (Incoming) and for originating calls it is called Busy Hour (originating).

Busy Hour Call Attempts (BHCA) : The no. of call attempts, successful and unsuccessful, made during the busy hour. In the above example the BHCA = 2300. This figure can be calculated for both incoming and outgoing calls.

144 C-DOT DSS MAX

Appendix B

Delay Parameters

This section contains the Delay Parameters, which shall be supported by CDOT MAX. The values of these parameters have also been taken from CCITT recommendation and may be suitably modified for Indian Network.

DELAY PARAMETERS FOR NON-ISDN OR MIXED ENVIRONMENT :

Local Exchange CALL REQUEST DELAY - Originating Outgoing And Internal - traffic connections

ANALOGUE SUBSCRIBER LINES (DIAL TONE DELAY) -

Call Request Delay for Analog subscriber (also referred to as DIAL TONE DELAY) is defined as the interval from the instant when the Off-Hook condition is recognizable at the subscriber line interface of the exchange until the exchange begins to apply dial tone to the line.

Recommended values are :

Mean Value <= 400 ms <= 800 ms

0.95 Prob. of not exceeding 600 ms 1000ms

DIGITAL SUBSCRIBER LINES Using OVERLAP Signalling -

Call Request Delay for Digital Subscriber line using Overlap sending, is defined as the interval from the instant at which the SETUP message is received from the subscriber signalling system until the SETUP ACKNOWLEDGE message is passed back to the subscriber signalling system.



0.95 Prob. of Not exceeding 600 ms 1000 ms

DELAY PARAMETERS


DIGITAL SUBSCRIBER LINES Using EN-BLOC Signalling -

Call Request Delay for Digital Subscriber line using En-bloc sending, is defined as the interval from the instant at which the SETUP message is received from the susbscriber signalling system until the CALL PROCEEDING message is passed back to the subscriber signalling system.




Exchange Call Setup Delay - Transit And Originating Outgoing Traffic:

Exchange call setup delay is defined as the interval from the instant that the information required for outgoing circuit selection is available for processing in the exchange, until the instant when the seizing signal has been sent to the subsequent exchange or the corresponding signaling information is passed to the signalling system.

Exchange Call Setup Delay For Transit Connections - CAS Or Mixed (CAS,CCS) -

For transit traffic connections, that involve circuits that use Channel associated signalling or mix of channel associated and common channel signalling.




Note Currently Same calculations are being used for transit exchange using CCITT Signalling System No. 7 exclusively.

Exchange CALL SETUP Delay For ORIGINATING-OUTGOING Traffic

ANALOGUE Subscriber Originated Outgoing Call:

The time when address information necessary for call setup (Routing in the switch) is complete and till the outgoing trunk selection is done.




Appendix B

146 C-DOT DSS MAX

Note: Same definitions for this delay parameter apply even when the Originating Subscriber is a DIGITAL Subscriber and uses either OVERLAP and ENBLOC sending.

ALERTING SENDING DELAY - Terminating And Internal Traffic Connections :

ALERTING SENDING DELAY For Call Terminating On ANALOGUE Subscriber :

For calls terminating on ANALOGUE SUBSCRIBER LINES, the alerting sending delay is defined as the interval from the instant when the last digit is available for processing in the exchange until the RINGING TONE is sent backwards towards the calling user.




Note: The above values are applicable for calls Terminating on a ANALOGUE subscriber, irrespective of the fact that the call was an Internal call (i.e. Originating terminating) or was a Incoming Terminating call.

Note: Alert sending delay is not supported for calls terminating on DIGITAL subscriber in the CDOT MAX Switches.

Exchange Call Release Delay -

Exchange call Release delay is the interval from the instant at which the last information required for releasing a connection is available for processing in the exchange to the instant that the switching network through connection in the exchange is no longer available for carrying traffic and the disconnection signal is sent to the subsequent exchange, if applicable.

The value for this parameter for Originating, Terminating, Transit and Internal traffic connection is as defined below:




Note : Following section contains parameters for ISDN Subscriber. They are not different from the Delay parameters described above.

DELAY PARAMETERS


SERVICE OBJECTIVE FOR ISDN CIRCUIT SWITCHED SERVICES

Call Request Delay (overlap Sending) / Dial Tone Delay

For Digital Subscribers lines using overlap sending, call request delay is defined as the interval from the instant at which the SETUP message has been received from the subscriber signalling system until the SETUP ACKNOWLEDGE is passed back to the subscriber signalling system.


Mean Value <= 400 ms

0.95 Prob. Not exceeding 600 ms

Call Request Delay (Enbloc Sending)

For Digital Subscriber Lines using en-bloc sending, call request delay is defined as the interval from the instant at which the SETUP message is received from the subscriber signalling system until the call proceeding message is passed back to the subscriber signalling system.



0.95 Prob. Not exceeding 800 ms.

Exchange Setup Delay For Originating Outgoing Traffic Connections (Overlap)

For outgoing traffic originating from Digital subscriber lines using overlap sending, the time interval starts when the INFORMATION message is received contains a 'Sending complete indication' or when the address information necessary for call set-up is complete, till the instant when the seizure signal has been sent to the subsequent exchange or the corresponding signalling information is passed to the signalling system.




Appendix B

148 C-DOT DSS MAX

Exchange Setup Delay For Originating Outgoing Traffic Connections (Enbloc)

For outgoing traffic originating from Digital subscriber lines using en-bloc sending, the time interval starts when the SETUP message is received, till the instant when the seizure signal has been sent to the subsequent exchange or the corresponding signalling information is passed to the signalling system.




Incoming Call Indication Sending Delay (For Terminating Calls)

For calls terminating on Digital subscriber lines, the incoming call indication sending delay is defined as the interval from the instant at which the necessary signalling information is received from the signalling system to the instant at which the SETUP message is passed to the signalling system of the called digital subscriber line.



0.95 Prob. Not Exceeding 600 ms.

Alerting Sending Delay For Terminating Traffic

For calls terminating on Digital subscriber lines, the alerting sending delay is defined as the interval from the instant that an ALERTING message is received from the digital subscriber line signalling system to the instant at which an ADDRESS COMPLETE message is passed to the inter exchange signalling system or ringing tone is sent in backward direction towards calling user.




Through Connection Delay

For connections terminating on Digital subscriber lines, the through connection delay is the interval from the instant at which the Connect message is received from the signalling system until the through connection is established and available for

DELAY PARAMETERS


carrying traffic as those indicated by passing to the respective signalling systems of the ANSWER message.



0.95 Prob. Not exceeding 300 ms

Exchange Call Release Delay

Call Exchange delay is the interval from the instant at which the last information required for releasing a connection is available for processing in the exchange to the instant that the switching network through connection in the exchange is no longer available for carrying traffic and the disconnection signal is sent to the subsequent exchange, if applicable.




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: Centre for Development of Telematics

Attn: Mr. Y.K. Pandey Director, Systems

39, Main Pusa Road New Delhi 110 005 Tel.: +91-11-5740374 Fax: +91-11-5756378

Your Reference: Name : Designation : Company : Address : Tel. : Fax :

c-dot dss maxcdothelpline.cdot.in/helpline/documents/c-dot_dssmax/... · 2014-12-29 · c–dot dss...

Documents