Cisco Unified Communications Manager (CallManager)

Document ID: 67175

Contents

Introduction
Prerequisites
      Requirements
      Components Used
      Conventions
Identify the Codec in Use
NetPro Discussion Forums - Featured Conversations
Related Information

Introduction

This document describes how to verify the codec in use for a specific call through the Unity Diagnostic Tool in a Cisco CallManager and Cisco Unity environment.

Prerequisites

Requirements

Cisco recommends that you have knowledge of these topics:

• Cisco CallManager

• Cisco Unity

Components Used

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

• Cisco CallManager

• Cisco Unity

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.

Identify the Codec in Use

Complete these steps to identify the codec in use from Cisco Unity.

1. Run Configure Micro Traces.

   Use this task to configure individual component traces and levels.

   1. Select Start > Programs > Unity > Unity Diagnostic Tool.

   2. Double-click Configure Micro Traces (see arrow A in Figure 1).

      The Welcome to the Configure Micro Traces Wizard window displays (see Figure 2).

      Figure 1—Cisco Unity Diagnostic Tasks

      

   3. Click Next (see arrow A in Figure 2). The Configure Micro Traces wizard displays (see Figure 3).

      Figure 2—Welcome to the Configure Micro Traces Wizard

      

   4. Check SkinnyTsp (see arrow A in Figure 3).

      Figure 3—Configure Micro Traces

      

   5. Click Next (see arrow B in Figure 3).

   6. Click Finish.

2. Double-click Start New Log Files to start a new log file (see arrow B in Figure 1).

3. Make a phone call.

4. Double-click Start New Log Files to close current log files.

5. Locate the correct log in the c:\CommServer\Logs.

   The format of the file name is diag_svchost_xxxxxxxx_yyyyyy where xxxxxxxx represents the year and date, and yyyyyy represents the hour, minute, and second. In this case, the file name is diag_svchost_20051003_220000 (see arrow A in Figure 4).

   Figure 4—Log Folder - C:\CommServer\Logs

   

6. Open the log files with Notepad and search a line similar to this output:

   Note: This output is displayed over multiple lines due to space limitations.

   Receive StationOpenReceiveChannelMessage (72 bytes) conferenceID=16777218 
   passThruPartyID=16777249 millisecondPacketSize=20 compressionType=4=Media_Payload_G711Ulaw64k 
   qualifierIn=[ecValue=0=Media_EchoCancellation_Off g723BitRate=0] callReference=16777218 

   In this case, the compressionType=4 represents G.711 (see the bold characters in the output). If the compressionType=11 is displayed, it represents G.729A.

NetPro Discussion Forums - Featured Conversations

Related Information

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