Mitel SX-200 DIGITAL Pabx General Description Manual

							Tenanting 
Interconnections Between Tenants 
4: 26 l-JAN-85 3.04 Each tenant may be allowed or not allowed to call any other 
tenant, by programming the TENANT INTERCONNECTION TABLE. 
On each horizontal line, an WJ indicates tenants that may be called, 
and a “.” indicates tenants that may not be called from that identified 
tenant. 
3.05 The diagonal of the matrix is Izbelled “0” because a tenant may 
not be prohibited from calling within itself. Note that the con- 
nection control is unidirectional; if tenant 1 may call into tenant 2, 
tenant 2 may not necessarily be able to call into tenant 1. This allows 
for a master tenant who could call everyone, but not be called. 
3.06 Form 3-2 shows an example where tenant 1 may call any 
tenant except tenants 5 and 7. 
alarm status = NQ ALARM 
01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 2i 22 23 24 25 
oio * * * * * * * * * * * * * * * * * * * * * * 
02*0**;*4****************** 
03**0********************** 
04***9********************* 
o?j.***o******************** 
Q6*****0******************* 
Qy.*****o****************** 
Q8*******0***************** 
og* * * * * * * * 0 * * * * * * * * * * * * *‘* * * 
1Q*********o*******a******* 
11**********0************** 
42***********0************* 
Form 3-2 Tenant Interconnection Table 
Page 3-2  
						

							Tenanting 
Call Rerouting 
3.07 The CALL REROUTING TABLE (Form 3-3) specifies where each 
tenant is to route different types of calls in Day, Night 1, or 
Night 2. If no number is specified, the caller receives reorder tone. 
3.08 For dial-in and DID trunks, forwarding and intercepting is for 
calls that are dialed into the tenant currently being displayed. 
DID trunks, which can access multiple tenants, are routed by the tenant 
whose local directory number was dialed. 
3.09 Night bells and Attendant LDN keys are programmed into the 
system with directory numbers for reference, and may be 
specified here along with stations, SUPERSET@ Sets, and SUPERSET@ 
Set lines. 
TABLE 4-29 
FORM 19 - CALL REROUTING TABLE 
CDE TERMINAL DISPLAY 
4:26 
I -JUN-86 alarm status = NO ALARM 
[TENANT : 11 TYPE OF CALL DAY Nl N2 
Stat ion Dial 0 
Routing + 
Priority Dial 0 Rout i ng 
DID Recall Points On Busy 11821 1821 
DID Recall Points On No Answer 
DID Routing For Calls Into This Tenant 
DID Intercept Routing For Calls Into This Tenant 
DID Vacant Number Routing For This Tenant 
DID Attendant Night Access Points 
Non-Dial-In Trunks Alternate Recall Points 
Dial-In Tie Recall Points On Busy 
Dial-In Tie Recall Points On No Answer Dial-In Tie Routing For Calls Into This Tenant ----- 
Station Dial 0 Routing 
I- 2- 
3-QUIT 7-TENANT 3- 4.-TOP 
0- S- 1821 1821 
5-BOTTOM 
O- 
ATTENDANT CONSOLE DISPLAY 
Form 3-3 Call Rerouting Table 
Page 3-3  
						

							Tenanting 
Night Switching 
3.10 A TENANT NIGHT SWITCHING CONTROL matrix allows one or 
more tenants (such aS a night security desk console or SUPER- 
SET@ Set) to switch all tenants into Night service. This matrix is similar 
to the TENANT INTERCONNECTION TABLE. 
3.11 The tenant being examined (horizontal row) will Night-switch 
each tenant programmed with an 
Irk” in its column. This matrix 
is unidirectional; tenant 1 may be programmed to Night-switch tenant 
2, but tenant 2 may not be programmed to Night-switch tenant 1. 
Form 3-4 shows an example where tenant 1 will Night-switch all 
tenants into Night service, but all other tenants will only Night-switch 
themselves. Tenant 1 therefore is the “master tenant” for Night switch- 
ing control. 
4:26 1 -JAN-85 alarm status = ND ALARM 
01 02 03 04 05 06 07 08 OS 10 11 62 13 14 15 16 11 18 19 20 21 22 23 24 25 
CID * * * * * * * * * * * * * * * *.* * * * * * * * 
02 . c 
03..i):::::::::::::::: 1::::: 
04.. * 0 
05....0::::::::::::::::::.: 
06. rn o -. 0 
07......0: 1:: 1::::::::::::: 
08.. s.. . . 0 
og...... ..o:::::::::::: 1::: 
IO.........0 
li.... *.- o ..;J: 1:. 1: 1: 1::. 1: 
1a...........o............. 
010************************ 
l- 2- 
3- 4-TOP B-BOTTOM 
6-QUIT 7-TENANT NUM 8-SWITCHED 9- O-ENTER 
Form 3-4 Tenant Night Switching Control 
Page 3-4/4  
						

							MITEL STANDARD PRACTICE 
SX-200” DIGITAL 
PRIVATE AUTOMATIC BRANCH EXCHANGE (PABX) 
TRAFFIC MEASUREMENT 
Copyright of MITEL Corporation 1986 
@Registered Trademark of MITEL Corporation  
						

							Traffic Measurement 
CONTENTS PAGE 
l.GENERAL ........................................ l-l 
Introduction ..................................... 
l-l 
Reason for Reissue ............................... l-l 
Traffic Analysis ................................... l-l 
System Architecture ............................... 
l-l 
Data Demultiplexer ................................ l-2 
2. TRAFFIC MEASUREMENT METHODS ................... 2-l 
General 
......................................... 2-l 
Types of Traffic Counts Accumulated ................. 2-l 
Register Count Examples ........................... 
2-5 
Power Failure .................................... 
2-6 
3. TRAFFIC MEASUREMENT COMMANDS ................. 
3-l 
Maintenance Terminal and Console ................... 3-l 
Traffic Commands ................................ 
3-l 
4.lNSTALLATION ..................................... 4-l 
General ......................................... 4-l 
Connection Requirements, Local Printer ............... 4-7 
5. REPORTS ........................................ 5-l 
Analyzing Traffic Reports ........................... 5-6 
. 
. . . 
111  
						

							Traffic Measurement 
1. GENERAL 
Introduction 
1 .Ol This Section describes principles of telephone traffic measure- 
ment for an SX-200@ DIGITAL PABX, inc!uding programming 
and operating procedures for obtaining Traffic Measurement data. 
Reason for Reissue 
1.02 This Section is reissued to provide information about Traffic 
Measurement for the SX-200@ DIGITAL PABX with Generic 1000 
or Generic 1001 software. 
Traffic Analysis 
1.03 Traffic 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 usag e during the period is also re- 
corded. Call holding time is the average length of each call. 
usage = 
(Erlangs) peg counts (per hour) X call holding time (in seconds) 
~- 
3600 (seconds per hour) 
usage = peg counts (per hour) X call holding time (in seconds) 
(CCS) 100 (seconds per CCS period) 
usage = 
(Erlangs) usage (CCS) 
36 or, 1 Erlang = 36 CCS 
1.05 Traffic 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. 
System Architecture 
1.06 The SX-200@ DIGITAL PABX is composed of several Bays con- 
nected together by Pulse Code Modulation (PCM) links. The 
system is controlled by a Main Control Card (MCC) whfch contains a 
circuit switch (MITEL DX chips) to connect any two ports within the 
system. 
Page l-l  
						

							Traffic Measurement 
197 There are four digital Bays (1, 2, 3, and 4) within the SX-200@ 
DIGITAL 336-port configuration. A non-blocking digital link 
connects the MCC to Bays 1 and 2 in the Control shelf. Bays 3 and 4 
are each connected to the MCC via a non-blocking PCM link. 
1.08 There are two digital Bays (1 and 2) and three analog Bays (3, 4, 
and 5) within the SX-200@ DIGITAL 480-port configuration. A 
non-blocking digital link connects the MCC to Digital Bays 1 and 2 in 
the Control shelf. Each analog Bay is a peripheral shelf with 31 speech 
paths which connects to the MCC via a PCM link. 
1.09 If an extension connects from one Analog Bay to another Ana- 
log Bay, one speech path and PCM channel is used in each Bay 
(of 31 per Peripheral shelf). If an extension on an Analog Bay connects 
to another extension within the same bay, only one speech path is 
used. This feature is referred to as local switching since the speech 
path does not go to and return from the DX switch, but remains on 
only the local speech path within the Bay. Local switching applies only 
to Bays 3, 4 and 5. Calls between a Digital Bay and an Analog Bay 
occupy one speech path and PCM channel between the two bays. Calls 
within the Digital bays use the non-blocking PCM channels. To op- 
timize traffic, trunks should be in the Digital Bays; trunks in the Analog 
Bays should be evenly distributed among the bays, and should prefer- 
ably be outgoing. 
Data Demultiplexer 
1.10 In some situations it may be desirable to output various print- 
outs (Hotel/Motel, Maintenance, SMDR, or Traffic Measurement) 
to different printing or recording devices. The Data Demultiplexer, 
MITEL Part Number 9160-OOO-OOI-NA (refer to Section MITL9160-080- 
300-NA), provides four separate outputs which may be routed as 
desired. 
Page l-2/2  
						

							Traffic Measurement 
2. TRAFFIC MEASUREMENT METHODS 
General 
2.01 Traffic 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 begin 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.02 Data 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.03 Two 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- 
dates the register only if its value exceeds that in the register. This 
Page 2-l  
						

							Traffic Measurement 
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 Records For Each Group. The number of system, feature, 
receiver, and channel pegs is fixed for each system. The number of 
console, trunk group, and trunk pegs can vary; at the beginning of each 
period, records are allocated for consoles, trunk groups, and trunks. 
Each consoie and trunk group that is programmed in CDE is allocated 
one record. The programmed trunks are allocated the remaining re- 
cords, in ascending trunk number order. In Generic 1000, 84 records 
are allocated; in Generic 1001, 112 records are allocated. 
Example: 
System configuration: For Generic 1000 the following For Generic 1001 the following 
traffic would be recorded: traffic would be recorded: 
- 4 consoles - 4 consoles - 4 consoles 
 
- 15 trunk groups - 15 trunk groups - 15 trunk groups 
- 90 trunks numbered 1 to 70 - 65 trunks numbered 1 to 65 - 70 trunks numbered 1 to 70 
89 devices (total) 84 records (total) 89 records (total) 
23 records still available 
2.04 The 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. 
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. 
3 s Dial Tone: This is incremented every time that an exten- 
sion or dial-in trunk has to wait 3 or more 
seconds for dial tone. 
Console Calls: Count of all calls directed to any console in- 
cluding calls that hang up before they are an- 
swered. 
Console orig.: Count of all console originations. 
Dial 0 Calls: Count of all dial 0 calls that are answered at 
any console. This includes internal calls as well 
as priority dial 0 calls. 
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. 
Page 2-2  
						

							Traffic Measurement 
Recall: 
Activity: Count of ail console-answered recalls. 
Each time a device has activity, this count is 
incremented. 
Illegal Calls: 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 
Callback: 
Call forward: 
Call hold: 
Call park: 
Call pickup: 
Camp-on: 
Console conf.: 
Console hold: 
DND: 
Ext. conf.: 
Flash Hold: 
Guest Room: 
Hold pickup: 
Msg Waiting: 
Override: 
Paging: 
Serial Call: 
TAFAS: 
Wake-Up: Count of callbacks that have been setup. 
Count of all call forwarding setups at any ex- 
tension or console. 
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. 
Count of camp-ons for extension-to-trunk, 
extension-to-extension, and trunk-to-exten- 
sion. 
Count of the number of times consoles use the 
conference softkey. 
Count of the number of all console call holds. 
Count of do not disturb setups. 
Count of extension conferences. 
Count of transfers or flash and holds from an 
extension or console. 
Count 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 applied message waiting. 
Count of completed busy overrides. 
Count of successful pager accesses. 
Count of console serial cal!s. 
Count of TAFAS (night answer) answered from 
dialed feature access code or Set softkey. 
Count of call wake-up setups. 
DTMF Receivers - records activity on receivers within system 
- maximum peg = 65535 
Page 2-3