This topic describes the benefits of using Unified Messaging in Cisco Unity Connection.
Unified Messaging decouples Cisco Unity Connection from the Exchange infrastructure and dependencies in the following ways:
- Does not stop functioning if a global catalog is unavailable.
- Does not require schema extensions to the Active Directory.
- Does not depend on hub transport and edge transport server roles for mail transfer agent functionality (that is, delivery or receipt of voice mails).
- Does not depend on mailbox server roles for voice message storage.
- Does not depend on client access server for front-ending client requests.
- Cisco clients still have complete access to voice messages if any or all of the Exchange infrastructure is down.
If the global catalog is not available, Cisco Unity (not Cisco Unity Connection) or Exchange Unified Messaging stops working. With Cisco Unity Connection Unified Messaging, a schema extension is not required.
Cisco Unity Connection does not rely on the hub transport (the edge transport servers in Exchange) to deliver voicemails from Cisco Unity Connection. Cisco Unity Connection does not depend on the mailbox server rules because Cisco Unity Connection is just synchronizing the messages into Exchange.
Cisco Unity Connection Unified Messaging reduces the dependencies on Exchange and Active Directory. If the message synchronization is not working because the Exchange infrastructure is not available, callers can still leave messages and users can still receive their messages. The communication between Cisco Unity Connection and Exchange is a two-way synchronization.
Cisco Unity Connection is the authoritative message store. However, a message deleted in Exchange via Microsoft Outlook, for example, is also deleted in Cisco Unity Connection and vice versa.
If a user sends a message to an Exchange distribution list (for example, a voicemail using ViewMail for Outlook), the message is received in a Cisco Unity Connection inbox and in Exchange. The message will be synchronized between both systems.
When secure messages are used in Cisco Unity Connection, the messages are not synchronized into Exchange. Cisco Unity Connection synchronizes a pointer instead, so that the message can be streamed from Cisco Unity Connection. Secure messaging does not allow audio files to leave the system, for example, as an attachment to an email.