This document describes how to properly configure Cisco Unity to work with two Network Interface Cards (NICs) when integrating Cisco Unity with a CallManager. Voice messaging will not work as expected if it is not properly configured.
Many enterprise customers who source their own hardware will purchase a platform that has two NICs on it. If these NICs are not configured properly, voice messaging will not work correctly and you will experience problems such as one-way audio or Message Waiting Indicator (MWI) malfunction. This document indicates the supported configuration for dual NICs.
Configuring dual NICs for active-active load sharing, meaning that 50 percent of the traffic is handled by each NIC, could lead to one-way audio and MWI problems. This setup is currently not supported on a Cisco Unity server .
The following is a cause of dual NICs resulting in one-way audio during call processing with a Cisco CallManager integration, using Skinny protocol:
There are two supported configurations when installing Cisco Unity on a platform with two NICs:
Cisco Unity does support using dual NICs configured in an active-passive manner for fault tolerance. In this NIC configuration, the primary (active) NIC handles 100 percent of the traffic. Only in the event that it goes down, does the secondary NIC become active and would handle 100 percent of the traffic. Therefore, only one IP address and one network (no subnets with each NIC on a different subnet) is supported.
All contents are Copyright © 1992--2003 Cisco Systems, Inc. All rights reserved. Important Notices and Privacy Statement.
|Updated: Dec 01, 2003||Document ID: 46266|