Solved: Unity Multi-tenant Service

angel-moon · ‎06-02-2010

Hello all,

In a multi-tenant environment is there a limit to how many different tenants, independant AAs, schedules, etc that can be configured within Unity?

Thanks in advance. All replies rated.

David Hailey · ‎06-02-2010

This would definitely require some serious consideration regarding architecture and capabilities. First take a look here to get an idea of what design guidelines you need to be aware of:

http://www.cisco.com/en/US/docs/voice_ip_comm/unity/5x/design/guide/5xcudg040.html

First, you need to consider if Unity will be capable of providing the services that you want given what you have described. Since Unity is tightly integrated into Active Directory and Exchange, you may need to look at having multiple Unity systems that are digitally networked. But, before we go further down the Unity route - definitely take a look at the design guide in general and particularly, the section noted above.

With Unity Connection, the architecture is likely to be much simpler as there is no inherent dependence on AD or Exchange. Granted, you would be providing an Integrated Messaging (IMAP) vs. Unified Messaging experience; however, the complexity would be reduced. Unity Connection doesn't care necessarily care about AD (unless you want to set up LDAP integration) or Exchange (unless you want to set up a external service which provides calendar integration with voicemail). It also provides the ability to build separate partitions and CSS's that would keep each "customer" separate and distinct of one another. You also still have the ability to stand up multiple systems and digitally network to provide greater scalability, as needed.

Hailey

Please rate helpful posts!

View solution in original post

David Hailey · ‎06-02-2010

Within a single Unity system, there is no real tenant concept. There is no way to separate components via partitions, calling search spaces, and etc. However, the only thing you are limited to is what is in the license file - so essentially, that is the number of subscribers. AA's and other components are not counted via license.

Unity Connection is a different product and it does offer the ability to set-up the system in a mutli-tenant configuration. Users, AA's, and etc can be assigned to specifiec partitions and/or calling search spaces. In this way, you can control what users, AA's, and other components have visibility into similar to how things are done in CUCM. As for the limits, same things as Unity - the number of users are counted via license but not the other system components.

One note of importance, you may be limited by hardware in terms of what can be configured on the system. In other words, a 7825 cannot support the same number of users and other components as a 7845. Make sure you review the supported platforms list for the platform you are using.

Hailey

Please rate helpful posts!

Added hardware limitation info

angel-moon · ‎06-02-2010

Thanks Hailey!

I know as far as sys admin level goes there is no real way to segment the users but I thought the user experience could be segmented such that Company A has an AA based on their Extension and DID with their own separate schedules and call routing and Company B could have a completely separate AA based on their extension and DID, etc. Also with each company having different mail stores, even if the mail stores are in fact on the same Exchange server. The goal is to have many different companies using the same infrastructure but be handled as separate entities (from their point of view anyway). Possible with Unity or just Unity Connection?

Thanks in advance!

David Hailey · ‎06-02-2010

Angel,

In order to better answer your question, I have a question for you regarding your design or potential design for Unity. Do each of these separate companies have their own Active Directory / Exchange environment? If so, I assume that your intent is to have a standalone Unity / AD / Exchange environment that provides voice messaging only or potentially integrated messaging services to these companies? Is that the case? If not, what do you envision the Unity architecture to be?

Hailey

Please rate helpful posts!

angel-moon · ‎06-02-2010

Hello Hailey,

there would be a mixture of completely hosted AD/Exchange environments where the customer AD exists within a different OU but within the same Forest and on the same Exchange server but different mail stores. Other customers would have their own AD/Exchange.

Thanks in advance!

David Hailey · ‎06-02-2010

This would definitely require some serious consideration regarding architecture and capabilities. First take a look here to get an idea of what design guidelines you need to be aware of:

http://www.cisco.com/en/US/docs/voice_ip_comm/unity/5x/design/guide/5xcudg040.html

First, you need to consider if Unity will be capable of providing the services that you want given what you have described. Since Unity is tightly integrated into Active Directory and Exchange, you may need to look at having multiple Unity systems that are digitally networked. But, before we go further down the Unity route - definitely take a look at the design guide in general and particularly, the section noted above.

With Unity Connection, the architecture is likely to be much simpler as there is no inherent dependence on AD or Exchange. Granted, you would be providing an Integrated Messaging (IMAP) vs. Unified Messaging experience; however, the complexity would be reduced. Unity Connection doesn't care necessarily care about AD (unless you want to set up LDAP integration) or Exchange (unless you want to set up a external service which provides calendar integration with voicemail). It also provides the ability to build separate partitions and CSS's that would keep each "customer" separate and distinct of one another. You also still have the ability to stand up multiple systems and digitally network to provide greater scalability, as needed.

Hailey

Please rate helpful posts!