-
null
The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
Beginning with Cisco Unity Connection 10.0(1) release, a concept of tenant partitioning has been introduced where administrator can configure multiple small medium businesses (SMBs) as tenants on a single Unity Connection server installation.
If Unity Connection server is being shared by N (N=2, 3, 4….) tenants for voicemail service, each tenant can be setup as a separate “tenant” that is effectively isolated from other tenant hosted on the same server. Hence, a tenant entity refers to logical group of resources in Unity Connection assigned to a single company, where each tenant is assigned with only one partition, search space, and phone system.
Tenant partitioning also introduces the concept of using the corporate email addresses as their alias, which enables alias uniqueness across tenants. In addition, separate Unity Connection SMTP domain is provided for each tenant.
Figure 7-1Sample Deployment scenario depicts the high level topology or deployment scenario that is being followed for tenant partitioning. Here, tenant 1 and tenant 2 have unique phone systems to identify inbound and outbound voicemail traffic. Each tenant has its own dedicated Cisco Unified Communication Manager.
Here each tenant has its own partition, schedule set, schedule, schedule detail, search space, search space member, phone system, class of service, user template, distribution list, distribution list membership, user operator, call handler template, directory handler, interview handler, call handlers (operator, opening greeting, Good Bye), and routing rules.
Note In Multi-tenancy mode, any configuration can be done using REST APIs. The configuration done using administrator pages is not supported.
Note: If you are upgrading Unity Connection 10.0(1) with Tenant Partitioning configured to a higher release then the Tenant Partitioning feature remains enabled on the upgraded system also.
The tenant partitioning implementation does not require any additional licenses.
Tenant Partitioning is a feature that offers a voice messaging solution for up to 60 tenants where each tenant can have maximum of 100 users on the Cisco Unity Connection 7vCPU OVA. For more information, see the “Specifications for Virtual Platform Overlays for Currently Shipping Connection 10.x Servers” section of the Cisco Unity Connection 10.x Supported Platforms List at http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/connection/10x/supported_platforms/10xcucspl.html#pgfId-703559.
The following is the list of limitations of Tenant Partitioning: