The Tenant Partitioning feature is unavailable with Offer B.
The Tenant Partitioning feature provides the following services to tenants:
You can also use the Tenant Partitioning feature to assign a separate music source to each tenant partition that plays when a user or an attendant places a caller on hold.
Note:
If you use equipment that rebroadcasts music or other copyrighted materials, you might be required to obtain a copyright license from, or pay fees to, a third party. A Magic-on-Hold system does not require such a license. You can purchase a Magic-on-Hold system from Avaya, or from an Avaya business partner.
Proper administration can protect tenant resources, including trunking facilities, and all other Communication Manager endpoints from unauthorized access by other tenants.
For the Tenant Partitioning feature to function properly in your system, you must ensure that:
All tenants can call and be called by tenant 1. This is the system default. If you change this default, some call types fail. For example, dial 0 fails, as do security violation calls and automatic circuit assurance calls.
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 entity, such as an endpoint or a virtual endpoint, to which you assign a Class of Restriction (COR). You do not assign a tenant partition number to an authorization code or to fixed-assignment virtual endpoints.
You must specify an attendant group for each tenant that you define, even if the attendant group does not have an assigned console. You must also assign an attendant console to a tenant partition, and you must assign a group number to the attendant console.
