Avaya Communication Manager Administrator's Manual page 1714

Feature Reference
Tenant Partitioning
The service provider creates additional partitions based on tenant requirements. When deciding which
tenant partitions to create, remember:
•
You can assign each Communication Manager endpoint to one and only one tenant partition. And,
you must pass each endpoint to a partition. For example, you must assign each telephone,
attendant console, trunk, and virtual endpoint, such as an LDN or VDN, to a tenant partition.
•
Most 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.
•
Even 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.
•
If 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 the administration or troubleshooting of
Communication Manager.
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.
1714 Administrator's Guide for Avaya Communication Manager
November 2003