Avaya Communication Manager Administrator's Manual page 1717

Interactions
Tenant-partition identification is not passed between servers/switches. A network of servers running
Communication Manager does not enforce Tenant Partitioning restrictions without special
administration. For example, Tenant Partitioning on a network of servers running Avaya Communication
Manager does not enforce tenant-specific tie trunks.
Administration of the following features requires special care to avoid undesired intertenant access.
•
Bridging
•
Call Pickup
•
Call Vectoring
•
Controlled Restriction
•
Facility Busy Indication
•
Facility Test Calls
•
Integrated Directory
•
Inter-PBX Attendant Calls
•
Main/Satellite/Tributary
•
Malicious Call Trace
•
Personal CO line
•
Private Networking (AAR)
•
Service Observing
•
Uniform Dial Plan
The function of any feature that specifies a tenant partition is affected by tenant-to-tenant restrictions, as
follows.
•
Automatic Alternate Routing (AAR)/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.
•
Attendant 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.
•
Attendant 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.
Administrator's Guide for Avaya Communication Manager
November 2003
Feature Reference
Tenant Partitioning
1717