Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 

Cisco Unity voicemail ports cannot register with the Cisco CallManager

Core Issue

The Cisco CallManager shows 169.254.84.183 on the voicemail page.

The Cisco Unity Telephony Integration Manager (UTIM) configuration is correct. However, the voicemail ports in Cisco CallManager still show they are registered to 169.254.84.143.

Resolution

To resolve this issue, perform these steps:

  1. Verify that the UTIM configuration is correct.
  2. Check for any error messages in the event log.
  3. Disable the second Network Interface Card (NIC).
  4. Restart the Cisco Unity services.

Note: Cisco recommends that a dual NIC be configured in Adapter Fault Tolerant Mode (AFT) or Network Fault Tolerant (NFT) mode. One NIC is designated as the primary, and the other NIC as the secondary for active-passive fault tolerance. In this configuration, the primary (active) NIC handles 100 percent of the traffic. Only in the event that the primary NIC becomes unavailable does the secondary NIC then become active and handle 100 percent of the traffic.

Also, note that a network cable plugged into the second NIC is not sufficient. Either the TCP/IP for the second NIC or the second NIC in the BIOS must be disabled. Otherwise, Cisco Unity may not work properly.

For more information, refer to these documents:

If the voicemail ports are not registered, perform this procedure in the TAPI Service Provider (TSP) configuration from the console of the Cisco Unity server:

  1. Go to Start > Settings > Control Panel > Phone and Modem Options > Advanced > Cisco Unity-CM TSP > Configure.
  2. Ensure the Cisco CallManager device name prefix is exactly the same as the port names configured for the voicemail ports in Cisco CallManager (with the exception of the 1, 2, 3, 4, and so on appended to each port).
  3. Ensure the IP address of the primary server is correct. It is better to use an IP address than a name. The TCP/IP port is usually set to the default of port 2000.
  4. Ensure that the IP/RTP port base is set to Auto Assign.
3282
Views
0
Helpful
0
Comments