Can you explain the design considerations for Unity connection unified messaging and how to implement in enterprise network?
For unified messaging, I would consider the following
1. Exchange on-premise (2003, 2007 or 2010) or cloud (Office 365)
2. What UM features you're looking for i.e. Single Inbox, SpeechView, TTS, Access to Exchange Calendar etc. For more details, I suggest the following -
Introduction to Unified Messaging in Cisco Unity Connection 9x
3. UM accounts that are created in Exchange with role of ApplicationImpersonation. For more details on Unity Connection Single Inbox and Exchange 2010 performance characteristics, I recommend the following document
Cisco Unity Connection Single Inbox with Microsoft Exchange 2010
4. UM Service to be created on Unity Connection. This can be used for granting UM feature access to users.
For example, you might configure one unified messaging service that enables text to speech (TTS), another that enables access to Exchange calendars and contacts, and a third that enables single inbox. With this design, if you want a user to have access to all three features, you would create three unified messaging accounts for the user, one for each of the three unified messaging services.
5. Number of users with UM feature is the same as a voice messaging deployment, however the following consideration applies "Allowing Connection or Exchange mailboxes larger than 2 GB can affect Connection and Exchange performance."
6. Populating SMTP Proxy address field in unity connection for each user with UM access. This is the user's exchange email address or use Viewmail for Outlook (VMO) as it addresses messages to Unity Connection only.
7. Firewall b/w Unity Connection & MS Exchange. For more on ports used by Unity Connection, refer to
IP Communications Required by Cisco Unity Connection 9.x
8. Bandwidth Requirements. For that I recommend going through the following document
Requirements for Using Unified Messaging Features
9. Round Trip Latency should be less than 250 ms. Sync threads required for mailbox sync or else users may experience delays. The default is 4 and the max is 64 (can be changed by a CLI command). For more details on latency and calculating connections needed, refer to Latency section in the design guide located here -
10. Whether or not secure voicemails are required by user with UM access.
11. Mailbox quotas & messag aging in connection. As mentioned earlier having mailbox size of 2GB or more can affect Exchange & Connection performance. So having mailbox quotas & message aging policy can help in improved performance. Preferrably have the same quota at both ends.
From a deployment perspective, you need to consider the following
1. UM accounts & services to be used for UM features
2. Populating SMTP Proxy address. One way of doing this is to enable LDAP sync and creating a user template with Generate SMTP Proxy Address with corporate email address checkbox checked. If you're adding users via BAT, the field is CreateSmtpProxyFromCorp. In case you're updating existing users the field is SmtpProxyAddresses. For details, I recommend the following document -
Using the Cisco Unity Connection 9.x Bulk Administration Tool
3. For more details on configuring UM for Unity Connection, I recommend the following guide
Unified Messaging Guide for Cisco Unity Connection Release 9.x
Single Inbox in Cisco Unity Connection 9.x - Design Guide for Cisco Unity Connection Release 9.x
What are the monitoring capabilities supported in Unity connection unified messaging, using SNMP.
From a monitoring perspective, unity connection supports SNMP v1, 2 & 3 and supports the following MIB's
1. CISCO-CDP-MIB - Use the Cisco Unified Communications Manager CDP subagent in order to read the Cisco Discovery Protocol MIB (CISCO-CDP-MIB). This MIB enables Cisco Unified Communications Manager and Cisco Unity Connection to advertise themselves to other Cisco devices on the network.
2. CISCO-SYSLOG-MIB - Syslog tracks and logs all system messages, from informational through critical. With this MIB, network management applications can receive syslog messages as SNMP traps.
3. CISCO-UNITY-MIB - The CISCO-UNITY-MIB uses the Connection SNMP Agent in order to get information about Cisco Unity Connection.
The contents of CISCO-UNITY-MIB can be found here -
If you have CUOM in your network, you can use the following document to configure Cisco Unity Connection for use with CUOM - https://supportforums.cisco.com/docs/DOC-31423
Additionally, I recommend the following interesting document
Unity Connection: SNMP Monitoring Configuration Example
Can I get your recommandation on design and configuration of Unity Connection in a multi-tenant environment ?
Thanks in advance !!
Multi-tenancy in Unity Connection can be achieved using Partitions and Search Spaces which were introduced in Unity Connection 7.0(1). Partitions & Search Spaces are mostly used when networking unity connection via VPIM or digital networking, however the same concept can be applied for Multi-tenancy.
Here are some recommendations that I would follow
1. Create one partition for each site/tenant.
2. Create one search space per site/tenant.
3. Add the site’s partition.
4. Assign all the subscribers to corresponding partition/search space.
Assuming you're using CUCM as the Phone System, here are some considerations for that
Configuring Dial Plan on CUCM
1. Unique outdial numbers:
a. Create a hunt pilot per site/tenant on CUCM
b. Create a routing rule to match the hunt pilot and assign the search space of the call to associated site.
c. For transfers and outdials always use the unique number outdial number…
2. Per site/voicemail ports.
a. Create a set of voicemail ports per site on CUCM
b. Create a switch on Unity Connection per set of voicemail ports
c. Create a routing rule to match the switch and assign the search space of call to the site.
For more on Partitions & Search Spaces in Unity Connection, please refer to the following
Managing Partitions and Search Spaces in Cisco Unity Connection 9.x
Hello Aashish !! Thank you very much !! I appreciate your thorough response !!!
I am aslo looking into upgrading my Unity Connection cluster in the next few months to the 9.x release. I am currently running 8.0.2 on physical server and I'll be migrating to UCX 9.x on UCS platform.
1- Can I upgrade from 8.0.2 directly to 9.x ?
2- Can I get your recommandation on planning / best practices for this migration path ?
3- Any changes with licensing going from 8.0.2 to 9.x ?
Also I am on CUCM 7.1.3 and I'll be upgrading CUCM 7.1.3 to 9.x as well.
Thanks Aashish !!
You're Welcome, glad to help. For the upgrade queries, here are my thoughts
1. Yes you can go direct to 9.x
2. From a migration perspective
*** Considerations Prior to upgrade ***
a. Since Unified Messaging was added in CUC 8.5 onwards, the way TTS and access to exchange calendar, contacts work has changed and will require a reconfiguration. For details on the same, please refer to
Features that You Must Reconfigure When You Upgrade to Connection 9.x at
b. Installation of COP file is needed prior to upgrade to prepare server for 9.x
COP File ReadMe Location - http://www.cisco.com/web/software/282204704/18582/ciscocm.refresh_upgrade_v1.1.pdf
c. Upgrade can take 4+ hours, so plan accordingly. Better to have users empty their deleted items folder, this will provide a little edge during upgrade/migration as CUC upgrade/migration process moves deleted items as well, so if the folder is empty that will save you a little time. Additionally configure Messaging Aging policies to automatically delete messages from deleted items folder after specified number of days. For more details on messaging aging refer to
Controlling the Size of Mailboxes in Cisco Unity Connection 8.x
*** Migration Procedure ***
a. Take a backup of existing CUC 8.0.2 and note down network infra settings especially hostname + IP Address
b. Shutdown the server
c. Build Virtual Machine using OVA and make sure the vDisk is greater than or equal to the Disk on physical server i.e. 160 GB. For details refer to the System Requirements for Cisco Unity Connection Release 9.x at
d. Build Virtual machine with same version on physical server and same hostname + IP.
e. Perform a data restore on this server.
f. Install all licenses (if you have any un-used licenses for 8.0.2, install them now)
g. Upgrade to release 9.x now
h. Depending on your deployment you may consider deploying Enterprise License Manager in a co-res mode i.e. with CUCM or as a stand-alone ELM server. ELM is the new way of managing licenses within CUCM & CUC. More on licensing changes starting UC 9.x, please refer to the following https://supportforums.cisco.com/docs/DOC-27237.
i. Once you upgrade to CUC 9.x, all pre-9.x licenses will be stored in CUC database.
j. Sync CUC with ELM and use the migrated license wizard to migrate licenses to 9.x. For details, refer to the Migrate licenses using Upgrade Licenses wizard at
*** References ***
Migrating from a Cisco Unity Connection Standalone Physical Server to a Connection 9.x Virtual Machine
Upgrading Cisco Unity Connection 7.x, 8.0, 8.5, or 8.6 to the Shipping 9.x Version
3. For CUCM 7.1.3 to 9.x upgrade, you can go direct as well. Please refer to the following documentation for CUCM
Cisco Unified Communications Manager Software Compatibility Matrix
CUCM Migration to Virtual Platform
Upgrading to Unified Communications Manager 9.1(1a)
I have 2 questions,
the first question about redanduncy. what is the maximum number of servers in Unity Connection Cluster ?
the 2nd question, regarding upgrade from Unity 4.0(4) to unity connection 8.6. Unity connection 8.6 will be VMware over UCS. I read the upgrade procedure to use COBRAS utility. this procedure didn't mention anything about licenses. I compare this procedure the DMA tool for CCM which requires to add all phones to convert the license to DLU.
thanks in advance
A Unity Connection cluster has 2 servers in Active/Active state and this is the maximum you can have. More on Cisco Unity Connection, please refer to the following document
About a Cisco Unity Connection 8.x Cluster
For 2nd question, you first need to consider an upgarde from 4.0.4 to 4.0.5 as COBRAS supports Unity 4.0.5 onwards. Secondly the licenses need to be re-issued with License MAC of Cisco Unity Connection. You can find more details on the procedure in the following document
License Files and Migrations from Cisco Unity
Some References for migration procedures
Task List for Migrating from Cisco Unity to Connection 8.x by Gradually Moving Data (Requires Unity 8.0 for networking)
Task List for Migrating from Cisco Unity 4.0(5) or Later to Connection 8.x by Using a Flash Cutover
thanks a lot for your reply. I have a note about upgrade unity from version 4.0(4) to 4.0(5).
kindly find the below link. it seems 4.0(4) is supported for direct upgrade.
Thx for the url. You can go directly from Unity 4.0(4) to Unity Connection 8.6. This support was recently added and the Unity Connection upgrade guide still mentions the minimum version for migration is 4.0(5). I have reached out to the BU to have that information corrected in the Unity Connection upgrade guide.
As a matter of fact, I have filed a documentation defect for the same, to have the document updated
CSCuf93155 - CUC 7.x/8.x/9.x migration from Unity in upgrade guide needs correction
I have unified messaging configured and working right with UCX 8.5.1. Is there a way to alert the user via email that their voicemail box is full? I'm concerned that if we allow users to turn on this feature that they may start filing email away into folders in Exchange and fill up their voicemail box on UCX. I tested this with a test box and filled it up. The greeting still plays and it appears to record the message, but if the box is full, the message is not saved and there is no indication to the caller or the intended recipient that there was a message left or a problem.
Is there any way to setup UCX to send the recipient a message that their mailbox has reached capacity?
You can consider Message Aging policies along with aging alerts with customized text. For this you'll have to make use of an SMTP Smart Host and a corporate email address need to be populated as well (since you're using Unified Messaging, I'm sure this is already in place). For more details, I recommend the following document
Controlling the Size of Mailboxes in Cisco Unity Connection 8.x
what is the difference between cisco unity and cisco unity connection ? when should I recommend unity and when should I recommend unity connection ?
also if the customer has unity 4 or 5 , what is better to keep the unity or convert to unity connection ?