Mitel SX 200 DIGITAL Pabx General Descriptions Manual

							MITEL STANDARD PRACTICESECTION MITL9109-094-450-NAIssue 3, September 1989
SX-200” DIGITAL
PRIVATE AUTOMATIC BRANCH EXCHANGE (PABX)
TRAFFIC MEASUREMENT
@Copyright 1989, MITEL Corporation. All rights reserved.
T”Trademark of MITEL Corporation
‘Registered Trademark of MITEL Corporationi 
						

							Traffic Measurement
CONTENTS
1. GENERAL
introduction..........................................1Reason for Reissue....................................1 
1Traffic Analysis........................................
12. TRAFFIC MEASUREMENT METHODS
General.............................................
3Types of Traffic Counts Accumulated.......................
3Register Count Examples................................
8:’Power Failure.........................................83. TRAFFIC MEASUREMENT COMMANDS
Maintenance Terminal and Console . . . . . . . . . .
Traffic Commands . . . . . . . . . . . . . . . . . . . . . . . .
4. INSTALLATION
General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Connection Requirements, Local Printer . . . . . . . .
5. 
.REPORTSGeneral . . . . . . . . . . . . . . . . . . . . . . . , . . . . . . . .
Analyzing Traffic Reports . . . . . . . . . . , . . . . . . . .
. . .
. . .
. . .
. . 9
. . .. . . .
9. 
* .9
. . .11
. . .11
. . .13. . .
15 
						

							SECTION MITL9109-094-450-NA
iv 
						

							Traffic Measurement
1. GENERAL
Introduction1.01This Section .describes principles of telephone traffic measure-
ment for an 
SX-2OU@ DIGITAL PABX, including programming and
operating procedures for obtaining Traffic Measurement data.
Reason for Reissue
1.02This Section is re issued to provide information about Traffic
Measurement for the SX-200 DIGITAL PABX with Generic 1002
or Generic 1003 software. Note that 672-port reports and Automated
Attendant reports are not available with Generic 1002.I
Traffic Analysis
1.03Traffic Analysis consists of two activities; the first is to collect
data about the system (measurement), and the second is to
interpret this data (analysis) to optimize performance. Once traffic
measurement has been started in the PABX it continues automatically
until changed or stopped. Traffic measurement produces only one
report for the system, even if tenant service is provided.
1.04 Traffic measurement accumulates data in the form of peg
counts and usage over a specified period of time. A peg count
is the total number of times a facility (device, service, or feature) is
accessed irrespective of the length of each access; usage is the length
of time or duration for which each facility is used. In certain applica-
tions the peak value of facility usage during the period is 
also re-
corded. Call holding time is the average length of each call.
usage =peg counts (per hour) X call holding time (in seconds)
(Erlangs)3600 (seconds per hour)
usage =
VWpeg counts (per hour) X call holding time (in seconds)
100 (seconds per CCS period)
usage =
(Erlangs)usage 
(CCS)36or, 1 Erlang = 36 CCS
1.05Traffic measurement results may be examined to determine the
adequacy of equipment provisioning, and the effectiveness of
programmed options and features. Analyzing the results will identify
changes which can be implemented by reprogramming and/or 
reprovi-sioning to improve system performance.
Page 1 
						

							SECTION MITL9109-094-450-NAPage 2 
						

							Traffic Measurement
2. TRAFFIC MEASUREMENT METHODS
General2.01Traffic measurement data is accumulated in periods of from 1
to 60 minutes in length. The start time, which is specified to the
nearest minute, and the duration (required number of periods) identify
the daily time when measurements are collected. These three param-
eters are entered from the console or maintenance terminal. Once set,
traffic measurement will 
beg.in at the same time each day, and for the
same duration until changed or stopped. The system clock times the
length of each period; however, a guard timer also monitors each
period and can terminate the period if it times-out before the system
clock does. This would occur only if the system clock has been
changed during a measurement period. The period length is not guar-
anteed if the clock is changed or the system is reset during a mea-
surement period.
2.02Data is accumulated into active registers during each period; at
the end of each period data is transferred to storage registers
and the active registers are zeroed in preparation for receiving data
from the next traffic measurement period. The data is held in these
storage registers from which it may be printed or written to magnetic
tape or a similar storage device. At the end of each period, the data in
the storage registers is replaced by the data accumulated in the active
registers during the period. If the data was not retrieved from the
storage registers during a period, new data received at the end of that
period overwrites the data, and it is lost. This sequence then repeats
for the specified duration.
Types of Traffic Counts Accumulated
2.03Two basic types of data are accumulated in the registers: peg
counts and usage counts. Usage counts may be further divided
into normal usage and maximum value counts, as outlined following:
Peg Counts. Each time a facility (device, service, or feature) is used,
the Call Processing software increments its register by one count. A
peg count is not concerned with the length of time of usage.
Usage Count. The amount of time for which a facility is used may be
calculated from the usage count. At 10 second intervals, the Call
Processing software scans each facility and increments the register if
it is in use. The usage count is directly proportional to the time that a
circuit is in use. Each accumulated usage count is converted into ccs
or Erlangs for the Report. The maximum usage is 6553.50 ccs or 182.04
Erlangs; this could only occur if 182 devices in a facility are all busy
for 1 hour. The consoles are scanned every second for accuracy in the
average waiting time for an answered call.
Maximum Value Count. This type of count is obtained similar to that
above, except that the value obtained at each scan does not increment
the register; instead it is compared with the register’s value and 
up-Page 3 
						

							SECTION MITL9109-094-450-NAdates the register only if its value exceeds that in the register. This
value reflects the scanned maximum count of the usage of a resource.
Since this is a scanned value it is possible that a busy peg may exist
without the maximum count reaching the number available.
Number Of Dynamic Records for Hunt Groups, Trunk Groups and
Trunk. The number of system, feature, receiver and channel pegs or
records is fixed for each system. The number of console, hunt group,
trunk group and trunk records can vary; at the beginning of each
period, records are allocated for consoles, trunk groups and trunks.
Each console, hunt group and trunk group that is programmed in CDE
is allocated one record. The programmed trunks are allocated the
remaining records, in ascending trunk number order. A total of 112
records is allocated.
Example: .
For Generic 1003 the following traffic would be recorded:
- 4 consoles
- 8 hunt groups
- 15 trunk groups
- 70 trunks numbered 1 to 70
97 records (total)
15 records still available (112 
- 97)
2.04The following data is accumulated during traffic measurement:
System Activity -indicates the extent of activity on the basic system
- maximum peg count = 65535
1 
s Dial Tone:This is incremented every time that an exten-
sion or dial-in trunk has to wait 1 or more
seconds for dial tone. This peg is not incre-
mented by the Automated Attendant feature.
2 
s Dial Tone:This is incremented every time that an exten-
sion or dial-in trunk has to wait 2 or more
seconds for dial tone. This peg is not incre-
mented by the Automated Attendant feature.
3 
s Dial Tone:
Console Calls:This is incremented every time that an exten-
sion or dial-in trunk has to wait 3 or more
seconds for dial tone. This peg is not incre-
mented by the Automated Attendant feature.
Count of all calls directed to any console in-
cluding calls that hang up before they are an-
swered.
Console orig.:
Dataset orig.:
Dial 0 Calls:Count of all console originations.
Each time a data call is originated either by ADLor DTRX this peg is incremented.
Count of all dial 0 calls that are answered at
any console. This includes internal calls as well
as priority dial 0 calls.
Page 4 
						

							Traffic Measurement
Ext origin.:
Intercepted:Each time an idle extension goes off-hook it
causes this register to increment by one count.
It does not increment when a ringing extension
goes off-hook.
Count of all intercepted calls that are answered
at all consoles.
Recall:
Activity:
Illegal Calls:Count of all console-answered recalls.
Each time a device has activity, this count is
incremented.
Whenever an extension, console or dial-in trunk
dials a vacant or illegal number.
Features -indicates the activity of those features which have been
programmed for the installation.
- maximum peg count = 65535
ADL Access:
Callback:
Call forward:
Call hold:
Call park:
Call pickup:Count of number of hard holds by an extension.
Count of number of call parks.
Count of legally dialed call pickups, includes
local pickups or directed pickups from exten-
sions.
Camp-on:Count of camp-ons for extension-to-trunk,
extension-to-extension,and trunk-to-exten-
sion.
Console 
conf.:Count of the number of times consoles use the
conference 
softkey.Console hold:
DND:
DTRX Session:
Ext. 
conf.:Flash Hold:Count of the number of all console call holds.
Count of do not disturb setups.
Count of successful DTRX session accesses.
Count of extension conferences.
Count of transfers or flash and holds from an
extension or console.
Guest Room:
Hold pickup:
Maid in RoomCount of Guest Room 
softkey depressions.
Count of successful hold pickups (calls held at
the console in a hold slot and picked up using
the dialed console and hold slot number).
Count of number of accesses to Feature Access
Code 35.
Msg Waiting:Count of applied message waiting.
Override:
Count of completed busy overrides. Count of 
sucessful ADL feature accesses.
Count of callbacks that have been setup.
Count of all call forwarding setups at any ex-
tension or console.
.Page 5 
						

							SECTION MITL91 Q9-094-450-NAPaging:
Serial Call:
TAFAS:Count of successful pager accesses.
Count of console serial calls.
Count of TAFAS (night answer) answered from
dialed feature access code or Set 
softkey.Wake-Up:Count of call wake-up setups.
UCD 
Login/outCount of UCD Agent logins and logouts.DTMF Receivers 
-records activity on receivers within system
- maximum peg = 65535
Peg:Represents the total number of times that the
DTMF receivers were accessed during the mea-
surement period.
Usage:Represents the total usage (Erlangs or CCS) for
the DTMF receivers during the measurement
period. Does not include busied-out receivers
(maximum = 6553.5 ccs).
Busy Peg:Represents the number of times a call could not
be allocated a DTMF receiver immediately due
to busy conditions.
Maximum in use/
Available:The scanned maximum count of the number of
receivers in use during the period and the 
num-
.ber that are available for use. Does not include
busied-out receivers.
Channel Usage And Local Switching 
-records activity between Bays
and within each Peripheral Bay
Bay Number:Identifies Bay for which data is being accu-
mulated.
Channel Usage:
Max Channel/
Available:Usage of channels available to the Bay. Does
not include channels allocated for music or
tones (maximum = 6553.5 ccs).
The scanned maximum number of channels in
use and the number available for use. Does not
include channels allocated for music or tones.
Local SwitchingUsage of analog peripheral bay local switching
Usage:(maximum = 6553.5 ccs).
Max Local Switching: The scanned maximum number of local switch-
es found in an analog peripheral bay.
Console 
-records activity of each console on the system
Console Number:Directory number of the console. The console
directory number is determined at the time of
CDE Entry in Form 07, Console Assignments. If
this console had been deleted, it will display
???? indicating that the directory number could
not be determined.
Page 6 
						

							Traffic Measurement
Usage:Non-idle use of the console. The console is
non-idle when it is using a channel. The con-
sole is idle when it is ringing, using the applica-
tion key,or using the select features key
(maximum = 36 ccs).
Call Waiting Usage:Usage of the Console queue when calls cannot
be immediately answered (maximum = 655.35ccs).Calls Answered:Calls answered using the console. Includes
softkey and ANSWER key answers (maximum
peg count 
= 65535).
Avg Waiting Time:Average waiting time for a call to the console
to be answered.
Hunt Groups
- records activity of each hunt group
Hunt Group Number:
Peg:Skip Peg:
Usage:
Busy Peg:
Max in use/Available:Programmed hunt group number.
Number of accesses to hunt group, including
busy attempts (maximum = 65535).
Number of failures to get a receiver, which 
re-
sutted in shipping the recording and routing to
the default destination (for Automated Atten-
dant Hunt Groups only).
Usage of all devices in the hunt group
(maximum = 6553.5 ccs).
Number of times the hunt group was busy.
Scanned maximum number of devices in the
hunt group that were busy (busied-out devices
are not included) and the number of devices
available for use in the group.
I’Trunk Groups 
-records activity of each trunk group
Trunk Group Number: Programmed trunk group number.
Peg:Number of accesses to trunk group, including
busy attempts (maximum = 65535).
Usage:Usage of all trunks in the trunk group making
outgoing calls, measured in CCS or Erlangs
(maximum= 6553.5 ccs).
Busy Peg:Number of times the trunk group was busy
(maximum = 255).
Max in use/Available: Scanned maximum number of trunks in the
trunk group that were busy; busied-out trunks
are not included. The number of available trunks
in a trunk group is determined at the time of
the report and is not in the storage registers.
Page 7