Guest

Cisco Unified Communications Manager (CallManager)

CallManager Call Forward No Answer Fails Because of Partition Name Change

Cisco - CallManager Call Forward No Answer Fails Because of Partition Name Change

Document ID: 68068

Updated: Feb 02, 2006

   Print

Introduction

This document describes one reason why the Call Forward No Answer (CFNA) fails to work and provides a solution in a Cisco CallManager environment.

Prerequisites

Requirements

Cisco recommends that you have knowledge of this topic:

  • Cisco CallManager

Components Used

The information in this document is based on these software and hardware versions:

  • Cisco CallManager Version 4.x

The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, make sure that you understand the potential impact of any command.

Conventions

Refer to Cisco Technical Tips Conventions for more information on document conventions.

Background Information

A partition comprises a logical group of directory numbers (DNs) and route patterns with similar reachability characteristics. Devices like DNs and route patterns are typically in partitions. These are entities that are associated with DNs that users dial. For simplicity, partition names usually reflect their characteristics, such as "LALongDistancePT," "LA911PT," and so on. When a DN or route pattern is placed into a certain partition, this action creates a rule that specifies which devices can call that device or route list.

Problem

If no one is available to answer the phone when a call comes in, the phone rings until the caller hangs up. Cisco CallManager fails to transfer the call to the Cisco Unity Voice Mail. It seems that the communication between Cisco CallManager and Cisco Unity is broken.

Figure 1 shows a possible configuration. "1000" in the Coverage/Destination field represents the Cisco Unity Voice Mail Pilot as arrow A in Figure 1 shows.

Figure 1 – Call Forward Configuration

cfnafailure1.gif

Solution

The root cause of the issue is the partition name change. It causes the Forward Manager to get out of synchronization and call forwarding to fail. CFNA ceases to work for all lines in that partition if you change the partition name in Cisco CallManager 4.x.

After you change the partition name, you must restart Cisco Database Layer Monitor and Cisco CallManager.

Complete these steps:

  1. Choose Start > Programs > Administrative Tools > Services.

  2. Right-click Cisco Database Layer Monitor.

    See arrow B in Figure 2.

    Figure 2 – Services

    cfnafailure2.gif

  3. Select Restart in the popup box.

  4. Right-click Cisco CallManager.

    See arrow A in Figure 2.

  5. Select Restart in the popup box.

Related Information

Updated: Feb 02, 2006
Document ID: 68068