Guest

Cisco Unified Communications Manager (CallManager)

Administrative Reporting Tool Reports Display Long Distance Calls as "Internal" or "Other"

Document ID: 5248



Contents

Introduction
Before You Begin
      Requirements
      Components Used
      Conventions
Problem
Solution
Related Information

Introduction

This document addresses call classification problems seen in Administrative Reporting Tool (ART) reports regarding long-distance calls. General familiarity with the Cisco CallManager administration and ART interfaces is assumed.

Before You Begin

Requirements

There are no specific requirements for this document.

Components Used

The information in this document is based on the software and hardware versions below.

  • Cisco CallManager version 3.0.9

  • ART version 1.0.1

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

For more information on document conventions, refer to Cisco Technical Tips Conventions.

Problem

If the Public Switched Telephone Network (PSTN) gateway has not been added or configured within the gateway configuration of the ART, long-distance calls are improperly classified as internal.

Solution

To fix this problem in Cisco CallManager 3.0 and 3.1, do the following:

  1. Launch ART either through the Cisco CallManager interface or by clicking Start > Programs > CallManager 3.0 > Administrative Reporting Tool > ART 1.0.

  2. Click System > Gateway Configuration.

    cm_art-1.gif

  3. Specify the gateway name, IP address, local area code and the location.

    This allows ART to distinguish between a local call and a long-distance call, and to classify them appropriately.

    cm_art-2.gif

  4. Click Insert when done.

    ART is now be able to classify all future calls correctly.

  5. Click Update to save the information in the ART database.

To fix this problem in Cisco CallManager 3.2, 3.3 and 4.x, do the following:

  1. On the Cisco CallManager Administration screen, click Application > Cisco CallManager Serviceability.

    cm_art-3.gif

  2. Click Tools > CDR Analysis and Reporting within the Cisco CallManager Serviceability menu.

    cm_art-4.gif

  3. Click System > System Parameters > Gateway Configuration within the CDR Analysis and Reporting menu.

    cm_art-5.gif

  4. Enter the User Name and Password.

    Note: If you are configuring CDR Analysis and Reporting for the first time, then you need to give administrative rights to a user in order to proceed with this configuration task.

    cm_art-6.gif

  5. Enter the Area Code to associate with a gateway.

    Note: In Cisco CallManager 3.2, 3.3 and 4.x, you do not need to insert gateway information on this screen. The Gateway Configuration screen automatically shows you the list of gateways already configured on your Cisco CallManager server.

    cm_art-7.gif

  6. Click Update when you are done with your configuration.


Related Information



Updated: Feb 02, 2006 Document ID: 5248