Lucent Technologies DEFINITY Enterprise Communication Server Release 8.2 Administrators Guide

							DEFINITY ECS Release 8.2
Administrator’s Guide  555-233-506  Issue 1
April 2000
Features and technical reference 
1537 Tenant Partitioning 
20
Because some features are not partitioned, you must take care to administer these 
features to prevent inter-tenant access. Refer to ‘‘
Interactions’’ on page 1542 for a 
list of these features.
You must ensure that: 
nAll tenants can call and be called by partition 1. This is the system default. 
If you change this default some call types fail. For example, dial 0 fails, as 
do SVN calls, ACA calls, etc.
nAll stations in a call-pickup group are under control of the same tenant
nAll stations with bridged appearances are under control of the same tenant
nStations in different departments (for the purposes of attendant services) 
can call each other
Refer to DEFINITY ECS System Description to determine the number of tenants 
that your system allows.
You must assign a tenant partition number to each object (endpoint, virtual 
endpoint, or other entity) that has an assigned COR. The exceptions are 
authorization codes and fixed-assignment virtual endpoints.
You administer Tenant Partitioning via the Tenant Partitioning screen; you need to 
administer one form for each tenant partition. Begin the initial administration of 
the Tenant Partitioning feature by completing the tenant partitioning form. Keep in 
mind that you must specify an attendant group for each tenant that you define, 
even if there are no consoles assigned to the attendant group. You must also assign 
an attendant console to a tenant partition and you must assign a group number to 
the Attendant Console screen.
Tenant Partitioning capabilities
Tenant Partitioning can provide the following services to tenants: telephone 
equipment, building wiring, public and private network access, and attendant 
services. In addition, the feature can provide a full range of DEFINITY ECS 
capabilities to even the smallest tenant office, including Call Coverage, Remote 
Access, Night Service Routing, and others. Tenants can also purchase DEFINITY 
ECS adjuncts available on the switch, such as Call Management System (CMS) 
activity reporting. 
						

							DEFINITY ECS Release 8.2
Administrator’s Guide  555-233-506  Issue 1
April 2000
Features and technical reference 
1538 Tenant Partitioning 
20
Tenant Partitioning provides advantages to both the telecommunications service 
provider and individual tenants:
nShared resources offer enhanced services at lower cost to the tenant, with 
increased profit for the service provider.
nThe tenant has the appearance of a dedicated DEFINITY ECS without the 
expense.
nAll tenants can have attendant services.
nA trained, full-time system administrator can install, administer, and 
maintain the switch.
With proper administration, tenant resources, including trunking facilities, and all 
other switch endpoints can be protected from access by other tenants.
Partitioning tenants
The default for Tenant Partitioning is one universal tenant for the system. This 
tenant, partition 1, is usually reserved for the service provider. By default it has 
access to all facilities and any other tenant can access it.
The service provider creates additional partitions based on tenant requirements. 
When deciding which tenant partitions to create, remember:
nYou can assign each switch endpoint to one and only one tenant partition. 
And, you must pass each switch endpoint to a partition. For example, you 
must assign each telephone, attendant console, trunk, and virtual endpoint, 
such as an listed directory number (LDN) or vector directory number 
(VDN), to a tenant partition.
nMost tenant partitions are discrete, separate units. By default, the system 
prevents all tenants, except partition 1, from accessing stations or trunking 
facilities belonging to other tenants. However, you can change this default. 
You can give explicit permission for one tenant to access another. For 
example, you can allow tenant 6 to call tenants 9 and 16 only.
NOTE:
If a tenant has permission to call another tenant, it has access to every 
endpoint belonging to that tenant. For example, if tenant 6 has 
permission to call tenant 9, tenant 6 can also use any trunking 
facilities present in tenant partition 9. 
						

							DEFINITY ECS Release 8.2
Administrator’s Guide  555-233-506  Issue 1
April 2000
Features and technical reference 
1539 Tenant Partitioning 
20
nEven if two extensions are blocked from calling each other by Tenant 
Partitioning restrictions, either extension can still reach the other by dialing 
the extension’s Direct Inward Dialing (DID) number via the public 
network.
nIf any facilities are to be shared among tenants who do not want complete 
access to each other’s facilities, you must group the shared facilities in a 
separate partition. For example, if two tenants share a trunk, but do not 
have direct access to each other’s telephones, that trunk will need to be 
placed in its own partition so that both tenants can access it.
It is also important to consider the following constraints and requirements of 
access control, attendant services, music sources on hold, and network route 
selection when you establish or assign partitions.
Access control
Features such as call coverage are limited by tenant-to-tenant access restrictions. 
For example, suppose tenant 1 includes a telephone from tenant 2 in its coverage 
path. If tenant 3 has permission to call tenant 1 but not tenant 2, a call from tenant 
3 to tenant 1 skips the tenant 2 coverage point.
You may also want to set up tenants with special access privileges. For example, 
you might give a restaurant in an office complex permission to be called by any 
other tenant. Likewise, permission to call or be called by other tenants is helpful 
for building security or DEFINITY ECS administration or troubleshooting.
You can also assign all CO trunks to one tenant partition that can then be accessed 
by all other tenants.
Attendant services
Tenant Partitioning allows you to provide personalized attendant services to each 
tenant.
The system provides one principal and one night or day/night attendant per 
attendant group. You assign each tenant an attendant group for service. Each 
attendant group has a separate queue. Queue warning lamps remain dark when 
Tenant Partitioning is active. However, information displayed when someone 
presses a queue-status button reflects the status of the attendant-group queue. The 
total number of calls queued for all tenants cannot exceed the system limit.
Attendant groups may serve more than one tenant. In this case, the attendant 
group cannot extend a call from one tenant via facilities belonging to another 
tenant, unless the former tenant has permission to access the other’s facilities. 
						

							DEFINITY ECS Release 8.2
Administrator’s Guide  555-233-506  Issue 1
April 2000
Features and technical reference 
1540 Tenant Partitioning 
20
Each tenant may have a designated night-service station. The system directs calls 
to an attendant group in night service to the night-service station of the 
appropriate tenant (when a night attendant is not available). When someone places 
an attendant group into night service, all trunk groups and hunt groups that belong 
to tenants served by that attendant group go into night service. In this case, the 
system routes incoming calls to the night-service destination of the appropriate 
tenant. Each tenant can have its own LDN night destination, trunk answer on any 
station (TAAS) port, or night attendant.
An attendant can specify that access to a trunk group is under attendant control if 
the trunk group is assigned to a tenant served by that attendant’s group. The 
system directs any valid user attempt to access the trunk group to the attendant 
group serving the tenant.
Network route selection
You can place trunk groups belonging to different tenants in the same route 
pattern. Calls routing to that pattern select the first trunk group in the pattern with 
access permission by the calling tenant (subject to normal constraints).
Tenant partitioning examples
The following is a simple example of how you might administer Tenant 
Partitioning in an office complex.
You assign tenant partition 1, the universal tenant, as the service provider. All 
other tenants can call and be called by the service provider.
You assign tenant partitions 2–15 to individual businesses in the complex. You 
maintain the system-default restrictions for these tenants. That is, tenants cannot 
access telephones, trunking facilities, or other switch endpoints belonging to other 
tenants.
You assign tenant partition 16 to the restaurant in the building complex. You give 
all tenants permission to call this tenant. However, to prevent the restaurant from 
accessing trunks and other facilities belonging to tenants, you do not permit the 
restaurant to call any other tenants.
You assign tenant partition 17 to all Central Office (CO) trunk groups. You give all 
tenants permission to call this tenant.
You assign tenant partition 18 to a trunk group that tenants 3 and 7 want to share. 
You give Tenants 3 and 7 access to this partition; you deny all other tenants 
access. To prevent toll fraud, you do not allow tenant 18 to call itself. 
						

							DEFINITY ECS Release 8.2
Administrator’s Guide  555-233-506  Issue 1
April 2000
Features and technical reference 
1541 Tenant Partitioning 
20
The Automatic Route Selection (ARS) route pattern can be the same for all 
tenants. In this example, the trunk for tenant partition 18 (the private trunk shared 
by tenants 3 and 7) is first in the route pattern. Tenant partition 17 is second. 
Tenants 3 and 7 route first to partition 18 and then as a second choice to 
partition 17. You deny all other tenants access to partition 18 and so the system 
routes them directly to partition 17.
All facilities that are not shared, including trunk groups, VDNs, telephones, 
attendant consoles, and other endpoints, are assigned to the tenant partition that 
they serve.
Table 94
 summarizes the calling permissions for the different partitions. Yes 
indicates that the partitions have permission to call and be called by each other; no 
indicates that partitions cannot call or be called by each other.
Table 94. Calling permissions for partitions
Calling 
tenant 
partition 
numberCalled tenant partition number
12, 4—6, 8—15 3,7 16 17 18
1 yes yes yes yes yes yes
2, 4-6, 
8-15yes Each partition 
can call itself 
but not the 
othersno yes yes no
3,7 yes no Each partition 
can call itself 
but not the 
othersyes yes yes
16 yes no no yes yes no
17 yes yes yes yes yes no
18 yes no yes no no no
Continued on next page 
						

							DEFINITY ECS Release 8.2
Administrator’s Guide  555-233-506  Issue 1
April 2000
Features and technical reference 
1542 Tenant Partitioning 
20
Detailed description of Multiple Music-on-Hold
Tenant Partitioning allows you to assign each tenant a music source, unique to 
each tenant partition, to be heard when a call is placed on hold. The tenant number 
assigned to the destination extension usually determines which music source is 
heard. This capability allows you to tailor the music or messages for the business 
needs of each tenant partition.
If the COR of the extension that places the call on hold permits music-on-hold, a 
caller on hold hears the music source assigned to the partition at which the call 
initially terminates. For example, if calls coming into the DEFINITY ECS route 
first to an I
NTUITY automated attendant that then routes the call to the appropriate 
tenant partition, the caller on hold hears the music source of the I
NTUITY 
automated attendant, not the tenant partition to which it is routed. Likewise, if a 
caller in tenant partition 2 makes an out-going call using tenant partition 1’s trunk 
groups, the caller will hear the music source assigned to tenant partition 1. If the 
COR of the called extension does not permit music on hold, however, the caller 
hears nothing. 
The maximum number of music sources allowed is the same as the maximum 
number of tenant partitions allowed; each music source can be used by one or 
more tenant partitions.
You can assign one of the following music-on-hold types to each tenant partition.
Interactions
Tenant-partition identification is not passed between switches. A network of 
DEFINITY ECS systems does not enforce Tenant Partitioning restrictions without 
special administration. For example, Tenant Partitioning on a network of 
DEFINITY ECS systems does not enforce tenant-specific tie trunks.
Table 95. Music-on-Hold Types
Type System Response for a caller placed on hold
none silence
tone system-wide administered tone
music the music associated with the administered port. The number of 
possible music sources equals the number of possible tenant 
partitions. Each partition can have its own music source. 
						

							DEFINITY ECS Release 8.2
Administrator’s Guide  555-233-506  Issue 1
April 2000
Features and technical reference 
1543 Tenant Partitioning 
20
Administration of the following features requires special care to avoid undesired 
intertenant access.
nBridging
nCall Pickup
nCall Vectoring
nControlled Restriction
nFacility Busy Indication
nFacility Test Calls
nIntegrated Directory
nInter-PBX Attendant Calls
nMain/Satellite/Tributary
nMalicious Call Trace
nPersonal CO line
nPrivate Networking (AAR)
nService Observing
nUniform Dial Plan
The function of any feature that specifies a tenant partition is affected by 
tenant-to-tenant restrictions, as follows.
nAAR/ARS
Do not confuse tenant partitions with Time-of-Day Plan Numbers and 
Partition Groups in AAR/ARS. You can still use Time-of-Day Plan 
Numbers and Partition Groups can still be used to select one of eight route 
patterns for AAR/ARS routing when Tenant Partitioning is in effect.
nAttendant and Attendant Group Features
Tenant Partitioning creates multiple attendant groups. Attendant operations 
such as direct-station or trunk-group select (DCS/DTGS) are subject to 
tenant-to-tenant restrictions, both at selection time and at split time.
All calls put on hold by an attendant from the attendant group hear the 
music source from the attendant group.
nAttendant Control of Trunk-Group Access
An attendant group controls access only to trunk groups that belong to 
tenants that are served by that attendant group. 
						

							DEFINITY ECS Release 8.2
Administrator’s Guide  555-233-506  Issue 1
April 2000
Features and technical reference 
1544 Tenant Partitioning 
20
nAUDIX, DEFINITY AUDIX, and AUDIX Voice Power
AUDIX voice and data ports are subject to the same tenant-to-tenant 
restrictions as any other endpoint.
AUDIX can restrict one group of subscribers from sending voice mail to 
another group. The tenant-partitioning provider can create up to 10 
different communities within each AUDIX that either have or do not have 
permission to send voice messages across community boundaries.
nAuthorization Codes
Authorization codes are associated with classes of restriction. If you want 
to have a set of authorization codes that is unique to a given tenant, you 
could select a group of CORs for a that tenant and only assign those CORs 
to objects in that partition. 
nAutomatic Wakeup
Wakeup music will be the music source assigned to the wakeup station’s 
tenant partition.
nBridged Call Appearance
All stations with bridged call appearances should be administered to be 
under control of the same tenant.
nCall Coverage
Tenant-to-Tenant access restrictions apply to coverage paths. If a tenant 
cannot access a particular tenant, it cannot access that tenant as part of 
another tenant’s coverage point.
When an attendant is specified as part of a coverage path, the attendant 
group of the called tenant, not the calling tenant, is accessed.
When a call goes to coverage, is answered, and is put on hold, the music on 
hold is the music source assigned to the tenant partition of the terminal that 
was originally called.
nCall Detail Record (CDR)
CDR does not report the tenant partition number of the extension or trunk 
group used. You must infer the tenant partition number from the extension 
or trunk-group number.
nCall Pickup
Administer all stations in a call-pickup group to be under control of the 
same tenant. The system supports Call Pickup only if the caller and the 
called party can both call the pickup user. The caller and the called party do 
not need to be in the same pickup group. 
						

							DEFINITY ECS Release 8.2
Administrator’s Guide  555-233-506  Issue 1
April 2000
Features and technical reference 
1545 Tenant Partitioning 
20
nCall Vectoring/VDN
A caller routed to a new destination by a vector step hears the music 
assigned to the last active VDN. While a call is in vector processing, the 
tenant number (TN) assigned to the active VDN (as determined by VDN 
Override) determines the music source heard by callers on hold in most 
circumstances. Note the following exception, however.
If you use a wait-time  hearing  then  
command where the  is a music source (assigned on the 
Announcements/Audios Sources form), that music source will play instead 
of the music source associated with the active VDN.
The COR assigned to the VDN must permit music-on-hold.
nCMS
You can administer CMS to provide CMS reports to each tenant. You can 
restrict each CMS login to control, on a permission basis, only those 
entities that are assigned to a particular tenant. Outputs to separate printers 
allow any tenant to print their own CMS reports. The tenant-partitioning 
provider must administer CMS to provide this separation of tenant 
permissions.
nDial Access to Attendant
When a tenant dials an attendant, it accesses its own assigned attendant 
group.
nEmergency Access to the Attendant
When a tenant dials emergency access, it accesses its own assigned 
attendant group.
nExpert Agent Selection (EAS)
For agents in an EAS system, the Class of Restriction assigned to the 
logical agent ID (not the physical extension) determines whether callers on 
hold can hear music.
nHunt groups
The tenant number assigned to the hunt group extension determines the 
music source callers to the hunt group hear while they’re in queue or on 
hold.
nIntercept Treatment
When access to the attendant is designated as intercept treatment, the caller 
accesses their assigned attendant group. 
						

							DEFINITY ECS Release 8.2
Administrator’s Guide  555-233-506  Issue 1
April 2000
Features and technical reference 
1546 Tenant Partitioning 
20
nMalicious Call Trace
By default, Malicious Call Trace extensions are assigned to tenant partition 
1. Therefore, if Malicious Call Trace is enabled, any telephone with 
permission to call tenant partition 1 can use it.
nMultiple Listed Directory Numbers
Each Listed Directory Number is assigned to a tenant partition.
nMultiple Audio/Music Sources for Vector Delay
When an audio source is specified by a wait-time  hearing 
 vector step, the audio source assigned to the tenant number of 
the active VDN is the one that plays.
If you use a wait-time  hearing  then  
command where the  is an audio source (assigned on the 
Announcements/Audios Sources form), that audio source will play instead 
of the one associated with the active VDN. For information on 
administering multiple audio sources see the DEFINITY ECS Call 
Vectoring/EAS Guide or DEFINITY BCS and Guestworks Call Vectoring 
Guide.
nMusic-on-Hold Access
When Tenant Partitioning is enabled, you can assign a unique source for 
music to each tenant. If Tenant Partitioning on the System-Parameters 
Customer-Options form is set to 
y, you must use the Music Sources form to 
administer music-on-hold.
nNight Service
Each tenant can have its own Listed Directory Number (LDN) night 
destination, Trunk Answer on Any Station (TAAS) port, or night attendant.
nPC Interfaces
You must assign each PC interface to a tenant partition.
nPC/PBX Connections
You must assign each PC/PBX Connection to a tenant partition.
nPC/ISDN
You must assign each PC/ISDN to a tenant partition.
nRemote Access
You must assign each Remote Access barrier code to a tenant.
nTraffic Studies
Traffic studies do not report the tenant partition number of the extension or 
trunk group used. You must infer the tenant partition number must be 
inferred from the extension or trunk-group number.