Cisco Unified Communications Manager (CallManager)

Document ID: 18011

Contents

Introduction
Prerequisites
      Requirements
      Components Used
      Conventions
Configuration Steps
Related Information

Introduction

There are quite a few deployments with Cisco CallManager servers located at a central site and several remote sites that have IP phones. In some scenarios, there are transcoders, conference bridges and other resources deployed at both central and remote sites. This document describes the steps needed to enable the remote phones to make use of local DSP resources.

Prerequisites

Requirements

Readers of this document should be knowledgeable of the following:

• General familiarity with Cisco CallManager configuration (especially Media Resource Group and lists)

Components Used

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

• Cisco CallManager version 3.1.2c

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, see the Cisco Technical Tips Conventions.

Configuration Steps

Follow the instructions provided below:

1. Create the Media Resource Group for the remote site. In the Cisco CallManager Administration page, click Service > Media Resource Group. Give a name to the Media Resource Group and assign the remotely located devices (such as conference bridges, transcoders, or MOH servers) to it.

   

2. Create a Media Resource Group List. Go to Service > Media Resource Group List and assign the Media Resource group to it.

   

3. Repeat steps 1 and 2 to create multiple media resource groups and lists if needed. Assign the Media Resource Group list to the remote phones.

   

With this configuration, the phones at remote sites will first attempt to find the resource within the first media resource group in the list. If nothing is available, they will attempt to find the resource within the next media resource group (if one is configured) in the media resource group list. If no resource is available within any group in the list, only then will the resource within the default group be used. This enables the remote phones to prefer local resources over central resources and save bandwidth.

Related Information

• Voice Technology Support
• Voice and IP Communications Product Support
• Recommended Reading: Troubleshooting Cisco IP Telephony
• Technical Support - Cisco Systems