Feature Reference
Tenant Partitioning
Administrator’s Guide for Avaya Communication Manager
1715
November 2003
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 Communication Manager 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 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.
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 100, Calling permissions for partitions,
on page 1716 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.