Administrator's Guide

Features and technical reference
555-233-5061870 Issue 5 October 2002
Tenant Partitioning
(Not available with Offer B) Tenant Partitioning provides telecommunications
services to multiple independent groups of users through a single Avaya
MultiVantage. Most commonly, Tenant Partitioning provides these services from
a single provider to multiple tenants of an office complex. This eliminates the
need for each tenant to purchase services separately, while still giving each tenant
the appearance of a dedicated Avaya MultiVantage. You can also use this feature
to provide group services, such as departmental attendants, on a single-customer
Avaya MultiVantage. Tenant Partitioning also allows you to assign a unique music
source for each tenant partition for callers who are put on hold.
NOTE:
If you use equipment that rebroadcasts music or other copyrighted materials,
you may be required to obtain a copyright license from, or pay fees to, a
third party such as the American Society of Composers, Artists, and
Producers (ASCAP) or Broadcast Music Incorporated (BMI). You can
purchase a Magic-on-Hold
®
system, which does not require such a license.
Detailed description
Tenants are defined and assigned by you, the system administrator. You must have
the same authorization as that required for COR administration.
Because some features are not partitioned, you must take care to administer these
features to prevent inter-tenant access. See ‘‘Interactions’’ on page 1876 for a list
of these features.
You must ensure that:
■ All 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.
■ All stations in a call-pickup group are under control of the same tenant
■ All stations with bridged appearances are under control of the same tenant
■ Stations in different departments (for the purposes of attendant services)
can call each other
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.