Table Of Contents

Optional Network Resource Requirements in Cisco Unity Connection 8.x

DHCP

DNS

Microsoft Exchange

LDAP Directory

Optional Network Resource Requirements in Cisco Unity Connection 8.x

---

If the resources discussed in this section are used, the applicable servers must be available at all times and in close physical proximity to Cisco Unity Connection (over a local area network, not a wide area network), or Connection functionality will be impaired. See the following sections:

•DHCP

•DNS

•Microsoft Exchange

•LDAP Directory

DHCP

Use of Dynamic Host Configuration Protocol (DHCP) is optional with Cisco Unity Connection and can be used to automatically configure network settings on the Connection server. If DHCP is not used, network settings such as hostname, IP address, IP mask, and gateway address must be manually entered during install or configured after install by using the command line interface.

DNS

Use of DNS name resolution is optional with Cisco Unity Connection, but if available, is recommended for use with Connection. If DNS name resolution is not enabled, IP addresses (not hostnames) should be used for all network devices.

Microsoft Exchange

Revised November 16, 2010

For all versions of Connection, when you are using Exchange 2010, Exchange 2007, or Exchange 2003 as a calendar application, you can configure Cisco Unity Connection to allow users to do several meeting-specific tasks by using the phone, for example, to hear a list of the participants for a meeting, send a message to the meeting organizer, or send a message to the meeting participants. Meeting organizers can also cancel a meeting. In addition, if users are using Microsoft Outlook, they can hear a list of upcoming meetings, and accept or decline meeting invitations.

Connection also enables users to import Exchange contacts by using the Messaging Assistant web tool. The contact information can then be used in rules that users create in the Cisco Unity Connection Personal Call Transfer Rules web tool and when users place outgoing calls by using voice commands.

Connection can play Exchange email over the phone by using Text to Speech.

For Connection 8.5 and later only, you can synchronize Connection and Exchange mailboxes so that Connection voice messages appear in the Outlook inbox. (This feature is commonly known as single inbox.)

See the System Requirements for Cisco Unity Connection Release 8.x (available at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/8x/requirements/8xcucsysreqs.html) for more information on supported versions of Microsoft Exchange for accessing calendar information, importing personal contacts, accessing email, and configuring mailbox synchronization. Also see the following documentation, as applicable:

•Connection 8.5 and later: The "Configuring Cisco Unity Connection 8.5 and Later and Microsoft Exchange for Unified Messaging" chapter of the Unified Messaging Guide for Cisco Unity Connection Release 8.5 and Later, at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/8x/unified_messaging/guide/85xcucumgx.html.

•Connection 8.0: The "Creating Calendar and Contact Integrations in Cisco Unity Connection 8.0" and the "Configuring Text-to-Speech Access to Exchange Emails in Cisco Unity Connection 8.0" chapters of the System Administration Guide for Cisco Unity Connection Release 8.x, at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/8x/administration/guide/8xcucsagx.html.

LDAP Directory

Revised June 9, 2011

Cisco Unity Connection can optionally use an LDAP directory (for example, Microsoft Active Directory) for LDAP directory synchronization and authentication. See the System Requirements for Cisco Unity Connection Release 8.x for more information on supported LDAP directories (the document is available at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/8x/requirements/8xcucsysreqs.html). See the "LDAP Directory Integration with Cisco Unity Connection 8.x" chapter for design considerations when integrating Connection with an LDAP directory.

For LDAP directory to work smoothly with Connection in WAN environment you need to take care of following:

•Latency should not exceed 80 ms roundtrip

•Access Control lists for corresponding ports and IPs shall be provisioned on the network devices