Mitel SX-200 DIGITAL Pabx General Description Manual

							Tenanting 
1. INTRODUCTION 
1 .Ol Tenanting is a feature which allows up to 25 tenants to share 
features and capabilities of the SX-200@ DIGITAL PABX. PABX 
features are enabled for each tenant through CDE. 
Reason for Reissue 
1.02 This Section is reissued to describe tenanting and to explain 
how to use and program tenanting in an SX-200 DIGITAL@ 
PABX with Generic 1000 or Generic 1001 software. 
Page l-l/l  
						

							Tenanting 
2. GENERAL DESCRIPTION 
Overview 
2.01 Tenanting is a very powerful and flexible feature available with 
the SX-200° DIGITAL PABX. A good understanding of tenanting 
coupled with a thorough analysis of the customer’s requirements will 
enable the PABX to be installed in a most cost-effective manner. The 
customer (or customers) can share the economies of a larger’ PABX, 
such as specialized trunks, leased services, and other features. Station 
Message Detail Recording (SMDR), described in Section 
MITL9108-093-451-NA, allows equitable assessment of costs among 
all users. 
2.62 The SX-200@ DIGITAL PABX allows up to 25 tenants (or cus- 
tomers) to be defined. The PABX may be operated as a single 
tenant, or in a multiple customer or multiple tenant mode, by sharing 
services such as attendants or trunks. A typical installation may have 
several tenants, each with its own trunks, stations and attendant. 
Members of different tenants may be programmed to access each 
other (but not necessarily each other’s features) without going through 
the local Central Office, or may be totally independent of each other. 
2.03 
A typical multiple tenant application is a company which oc- 
cupies a large building and has attendants and/or sub- 
attendants in different areas, such as each floor or department. Some 
features, such as attendant recall, access the local attendant instead of 
the main attendant position, but other features such as WATS, ARS, Tie 
lines, or abbreviated dialing are available to all users. 
2.04 
A typical multiple customer application is a building served by 
one PABX, with telephone service for each customer (tenant) 
going through the PABX independently. When one customer calls an- 
other, the calling party must access one of its CO trunks and dial the 
customer’s listed directory number: the call will go through the CO and 
then appear as an incoming CO call at the called customer. 
Independent Consoles, Trunks, and Stations 
2.05 The PABX is divided into distinct tenants; all stations, 
SUPERSET@ Sets, trunks, and attendant consoles are assigned 
to a tenant as they are programmed into the PABX. The PABX can have 
a maximum of’ 11 consoles. Trunks and “Dial 0” calls are programmed 
to ring to only their associated attendant position. Outgoing calls will 
seize only trunks within their same tenant, as shown in Figure 2-l. 
Tenant Interconnection 
2.66 The PABX may be programmed to allow certain tenants to 
connect to each other internally within the system or to allow 
for sharing of services such as an attendant console or trunks. 
Page 2-l  
						

							Tenanting 
2.07 Each tenant may be allowed or not allowed to connect directly 
to any other tenant. For example, an attendant console to be 
shared by tenants. 1, 2, and 3, can be assigned to tenant 25, and 
programmed to connect internally to tenants 1, 2, and 3; tenants 1, 2, 
and 3 may still be programmed to NOT connect to each other, as 
shown in Figure 2-2. 
2.08 Note the special case when tenant 1 can call tenant 2 but 
tenant 2 cannot call tenant 1. If SUPERSET qTM A in tenant 1 
calls SUPERSET qTM B in tenant 2, and upon receiving no answer, sends 
the message to call Set A, Set B can return the call to Set A (by 
pressing its MSG, READ MSG, and CALL softkeys) even though tenant 2 
is normally restricted from calling tenant 1. 
Identifying Tenants on Consoles and SUPERSET@ Sets 
2.09 Attendant consoles or SUPERSET@ Sets may be programmed 
into one tenant that can provide a common answering point for 
incoming calls to all tenants, as well as calls that are unanswered by 
any tenant. Each tenant may not call the other tenants or access each 
other’s trunks, but all of their calls will be directed to the common 
answering point. The incoming calls may be DID, DIL, or regular CO 
trunks. 
2.10 When recalls are answered at a common answering point, the 
name of the tenant that did not answer is displayed as a NO 
ANSWER, so that the recall may be answered with an appropriate 
TENANT 1 TENANT 25 
TENANT 1 TRUNKS TENANT 25 TRUNK3 
8293ROE’ 
Figure 2-l Tenant Connections to PABX 
Page 2-2  
						

							Tenanting 
TENANT 1 
TENANT 3 
I 
I 
TENANT 2 
SHARED CONSOLE (TENANT 25) 
I 
Figure 2-2 Tenant Interconnection with Shared Console 
Page 2-3  
						

							Tenanting 
response. If the called party has a SUPERSET qTM Set, that party’s name 
is displayed instead; however, the set may .be programmed to display 
the company name instead. 
2.11 The call rerouting point for all tenants may be two SUPERSET 
qTM Sets, with each tenant having its own key for recalls, as 
shown in Figure 2-3. A recall to a busy line will camp on to that line, 
allowing queuing for each tenant’s recalls. 
Local Night Switching 
2.12 Tenants sharing the system may each require different system 
operation with respect to Day/Night mode. The PABX allows 
each tenant to switch into Night service independently, and to operate 
independently when it has switched to Night service. Figure 2-4 shows 
two typical examples. 
2.13 An attendant with a console may switch to Night 1 or Night 2 
by pressing the FUNCTION key followed by the appropriate 
softkey. 
2.14 A tenant with a SUPERSET qTM Set programmed as a sub- 
attendant may switch to Night service by pressing the SELECT 
FEATURES key and the softkey “NIGHT ANS” to toggle between Night 1 
and Day service, either displaying .“NIGHT SERVICE”, or flashing “DAY 
SERVICE” and then reverting to time and date display, respectively. 
Night Switching Control 
2.16 Each tenant may switch into Night service independently, from 
its console or sub-attendant SUPERSET qTM Set. Since call re- 
routing destinations and incoming CO trunks are programmed for Day, 
Night 1, and Night 2, switching to Night service will automatically 
reroute all calls for that tenant. 
2.16 It may be desirable to have a console or SUPERSET qTM Set 
(such as a night security desk) able to switch all tenants into 
Night 1 or Night 2 service. The security desk console may be pro- 
grammed as a tenant that controls the Night status of tenants; when 
the security guard comes on duty and sets “Night 2”, all associated 
tenants switch into Night 2. If a tenant forgot to switch to Night 
service, and calls were not being rerouted, the status will be corrected 
when the night security guard comes on duty and sets “Night 2” to 
reroute calls to the security desk. 
Night Bells and Night Answer 
2.17 The system allows incoming calls to be redirected to a Night 
bell. A station in that tenant may dial the “TAFAS ACCESS - 
LOCAL TENANT” feature access code to answer the first call in that 
tenant’s queue. Similarly, the SUPERSET qTM Set prompt “NIGHT ANS” 
will light if there is a call in its tenant queue. Any extension may dial 
the “TAFAS-any” feature access code to pick up a call in any tenant to 
which it is allowed to connect. 
Page 2-4  
						

							Tenanting 
TENANTS 
OCTEL 
_ txACK’S 
JONES’S 
Figure 2-3 SUPERSET qTM Set Sewing Several Tenants 
Page 2-5  
						

							Tenanting 
“Dial 0” Routing 
2.18 Any tenant group may operate with a central attendant position 
handling incoming calls and “Dial 0” calls, or may program its 
own Day/Night directory numbers to route “Dial 0” calls. Figure 2-5 
shows two examples. 
2.19 The feature access code for attendant access (usually “0”) is 
programmed systemwide for all stations. Each tenant may then 
specify the Day, Night 1, and Night 2 answer points to route callers 
who dial this access code. 
Call Rerouting Features and Answer Point 
2.20 Each tenant may determine its method of rerouting “Dial 0” 
calls, intercepts for illegal access, or calls that are not an- 
swered, or reach busy parties. The answer point may be an Attendant 
console, SUPERSET@ Set line, station, hunt group, or Night bell. The 
caller is automatically camped on to a busy station or SUPERSET@ Set. 
Calls may also be routed to a staffed Night answering desk for the 
PABX, or to an outside answering service. 
2.21 Rerouted calls arrive at a console as NO ANSWER or BUSY 
recalls. From the display, the attendant can identify which ten- 
ant originated the recall. Calls rerouted to a SUPERSET@ Set may ring 
into a different key for each tenant, thereby identifying the company 
TENANT 1 (DAV) TENANT 2 (NIGHT) 
TRUNKS ROUTED TO 
SUPERSET 4 SET LINES TRUFJKS ROUTE!2 TO 
NIGHT BELL 
8296ROEO 
Figure 2-4 Night Switching Options 
Page 2-6  
						

							Tenanting 
that originated the recall. If the line is busy, a recall will automatically 
camp on to the SUPERSET@ Set. 
2.22 
Several examples of Call Rerouting follow; a complete, list is 
given in the CDE Section. 
Direct inward Dial Rerouting 
2.23 In some cases DID trunks may be shared among tenants. The 
block of numbers obtained is used by all the tenants, each with 
its own phone numbers listed in the telephone directory. The DID 
trunks are placed into one tenant which is programmed to be able to 
connect to the other tenants that share the DID trunks. If no one 
answers an incoming call, or if the number is busy it may be rerouted 
to a specified answer point as a No Answer/Busy recall. 
Direct-In Line Rerouting 
2.24 Incoming DIL trunks are directed to ring destinations in any 
tenant that they can connect to. An unanswered incoming call 
may be rerouted to a specified answer point (Day, Night 1, or Night 2) 
as a No Answer recall, from the tenant into which the trunk rang. 
TENANT 1 TENANT 2 
“DIAL 0” CALLS ROUTED TO SUPERSET 4 SET LINES “DIAL 0” CALLS ROUTED TO ATTENDANT CONSOLE 
8297ROEO 
Figure 2-5 “Dial 0” Call Routing 
Page 2-7  
						

							Tenanting 
Numbering Plan 
2.25 Since tenants are allowed to connect to each other, numbers 
must be unique among all tenants, and must be nonconflicting 
across the entire system; for example, there may be one and ONLY 
ONE extension 201 in the PABX. Similarly, feature access codes must 
be the same throughout the system. SMDR records may be sorted for 
each tenant by its unique extension numbers. 
Automatic Route Selection with Multiple Tenants 
2.26 Automatic Route Selection (ARS) enables the system to access, 
in a specific sequence, possible routes to a given destination. 
Routes are listed within the system in the order in which they are to 
be tried. 
2.27 Route definition is based on trunk groups, each of which is 
listed as first to sixth choice to some destinations. Since some 
tenants may be allowed to access only specific trunks, the ARS pack- 
age checks the tenant interconnection table to verify if a caller may 
access a particular trunk. If the first choice trunks are not available to a 
particular tenant, the system skips them and takes the next choice 
trunks instead. The system automatically searches available trunks 
from first choice to last choice as it attempts to find a free trunk. 
2.28 If tenant interconnection is allowed, shared trunks should be 
accessible from all participating tenants. ARS will optimize all 
calls made from these tenants. The administrator must collect and sort 
the SMDR reports for billing to each tenant. 
Sub-Attendants and Message Centers 
2.29 A company may set up its system with a main attendant con- 
sole for receiving incoming calls and routing them to stations 
in the system. Usually the attendant who handled an incoming trunk 
call, receives the No Answer recall. Any department wanting to handle 
its own recalls (for example, to take messages), may program alternate 
recall points for its calls. The department is programmed as a tenant, 
and then uses call rerouting for its calls. 
2.30 The person can take a message and set message waiting on 
the absent party’s set. Members of a department may call their 
own “message center” by dialing “0”; since each tenant programs its 
own dial “0” answering point, people don’t have to remember how to 
call their message desk. They can call another department’s message 
desk by dialing its extension number. 
Page 2-8/8  
						

							Tenanting 
3. PROGRAMMING AND CUSTOMER DATA ENTRY FOR TENANTING 
3.01 This Part describes how the Customer Data Entry (CDE) package 
handles setting up the various functions described eat-her. The 
forms are more fully explained in the CDE documentation in Section 
MITLS 108-093-Z 1 0-NA. 
CDE Access Restrictions 
3.02 There are five levels of access to Customer Data Entry; Installer, 
Maintenance 1, Maintenance 2, Supervisor, and Attendant; ac- 
cess by each level is restricted during initial Customer Data Entry to 
prevent unauthorized database modifications. 
Tenant Assignments 
3.03 Stations, sets, consoles, and trunks are assigned to a tenant 
when they are programmed into the system during CDE. The 
field labelled “TEN” is the tenant assignment field. Enter the tenant 
number (l-25) to which the station or SUPERSET@ Set belongs. The 
STATION/SUPERSET@ SETS programming form (Form 3-1) shows ex- 
tension 4612 in tenant 1 and extension 1234 in tenant 2. 
4:26 1 -JAN-85 alarm status t NO ALARM 
BAY SLOT 
1 1 
1 1 
I 1 
c 
1 
I 
1 1 
1 1 
1 1 
1 1 
I 2 
1 2 
l- CCT 
Cl 
02 
03 
04 
05 
06 
07 
08 
01 
02 
03 
04 
01 TEN 
1 4612 1 I 
se 
2 1234 1 1 Set 
3XT NUM 
c 
I 
1 4612 
2-FIND EXT 
T cos COR 
1 1 
I TYP r ANNOUNCE 
Set - 
l- 
I 3-EXPAND SET 
14- 
T- BLF COMMENTS 
I 
6-QUIT 7-BAY/SLT/CCT 8-DELETE S-REV1 EW M. SMITH 
J. DOE 
-4 M. SMITH 
B-RANGE 
I 
Form 3-l Stations/SUPERSET@ Sets Programming Form 
Page 3-l