Troubleshooting Guide for Cisco Unity Connection Release 10.x

Troubleshooting Audio Quality in Cisco Unity Connection 10.x

---

See the following sections:

• Using Check Telephony Configuration Test
• Problem with Choppy Audio
• Problem with Garbled Recordings
• Problem with Garbled Prompts on Phone
• Problem with Volume of Recordings
• Using Traces to Troubleshoot Audio Quality Issues

Using Check Telephony Configuration Test

Note The Check Telephony Configuration test does not test IPv6 connectivity. (IPv6 is supported in Cisco Unity Connection for Cisco Unified Communications Manager integrations.) The test confirms that Unity Connection can communicate with the phone system using IPv4 addressing.

To Use the Check Telephony Configuration Test to Troubleshoot Audio Quality

Step 1 In Cisco Unity Connection Administration, in the Related Links box in the upper right corner of any Telephony Integrations page, select Check Telephony Configuration and select Go.

If the test is not successful, the Task Execution Results displays one or more messages with troubleshooting steps. After correcting the problems, run the test again.

Step 2 In the Task Execution Results window, select Close.

Problem with Choppy Audio

Use the troubleshooting information in this section if the audio you hear from Unity Connection is choppy. Consider the following possible causes:

• The hard disk from which Unity Connection is playing a recording is full. To resolve the situation, eliminate unnecessary files from the hard disk.
• The network Unity Connection to the Unity Connection server is not adequate. To resolve the situation, improve the network Unity Connection.
• The Unity Connection platform has a malfunctioning component. To resolve the situation, identify the malfunctioning hardware component, then repair or replace it.
• Another process is using too much CPU time. To resolve the situation, stop the process and run it when phone traffic is lighter.

Problem with Garbled Recordings

Use the troubleshooting information in this section if recordings sound garbled. See the following possible scenarios:

• The audio stream sounded garbled when Unity Connection created the recording. See the “Troubleshooting a Garbled Audio Stream in the Network” section.
• The audio stream did not sound garbled when Unity Connection created the recording, but became garbled later. See the “Troubleshooting How Unity Connection Makes Recordings” section.

Problem with Garbled Prompts on Phone

When Unity Connection prompts sound garbled or jittery when heard on the phone, use the following task list to determine the cause and to resolve the problem.

Follow the tasks to troubleshoot garbled prompts on the phone:

1. Determine whether the audio stream is garbled at the closest point to the phone by obtaining a sniffer capture at that point. If the audio stream from the sniffer capture is not garbled, the cause may be in the network or with Unity Connection.

2. Determine whether the garbled audio stream is caused by problems with the network. Use network analysis tools to do the following:

• Check for latency, packet loss, and so on.
• Search for devices on the network that are causing garbled audio streams. Some examples are routers, gateways, transcoders, and gateways that are configured for one packet size (such as G.711 30ms) while Unity Connection is configured for another packet size (such as G.711 20ms).

3. Determine whether the audio stream is garbled at the closest point to the Unity Connection server by obtaining a sniffer capture at that point. If the audio stream from the sniffer capture is not garbled, Unity Connection may not be handling the audio stream correctly.

4. Enable the Media (Wave) Traces macro traces in Cisco Unity Connection Serviceability. For detailed instructions on enabling the macro trace and viewing the trace logs, see the “Using Cisco Unity Connection Serviceability Traces to Troubleshoot Problems” section.

5. Obtain a snapshot of CPU usage on the Unity Connection server using the CPU and Memory display in the Real-Time Monitoring Tool (RTMT). For detailed information on using RTMT, see the applicable Cisco Unified Real-Time Monitoring Tool Administration Guide at http://www.cisco.com/en/US/products/ps6509/prod_maintenance_guides_list.html.

6. Contact Cisco TAC.

Problem with Volume of Recordings

Use the troubleshooting information in this section if the volume of recordings is too loud or too soft, or if the recordings do not have any sound. Consider the following:

• Verify the audio level at each hardware point in the network by obtaining a sniffer capture at each point.

– If the audio level from the sniffer capture at one point is too soft or too loud, the cause may be the configuration of the hardware (such as routers, gateways, transcoders) at that point. Check the automatic gain control (AGC) settings for the applicable hardware.

– If the audio level from the sniffer capture at all points is too loud or too soft, see the “Changing the Volume for Unity Connection Recordings” section.

• Disable automatic gain control (AGC) for Unity Connection so that Unity Connection does not automatically adjust the volume of recordings. See the “Disabling Automatic Gain Control (AGC) for Unity Connection” section.
• If the recordings do not have any sound, confirm that the advertised codec settings are correct. See the “Confirming the Advertised Codec Settings.” section.

Changing the Volume for Unity Connection Recordings

To Change the Volume for Unity Connection Recordings

---

Step 1 In Cisco Unity Connection Administration, expand System Settings and select General Configuration.

Step 2 On the Edit General Configuration page, in the Automatic Gain Control (AGC) Target Decibels field, enter the applicable number and select Save.

---

Note AGC decibel levels are set in negative numbers. For example, –26 db is louder than –45 db.

---

---

 

Using Traces to Troubleshoot Audio Quality Issues

You can use traces to troubleshoot audio quality issues. For detailed instructions on enabling the applicable traces and viewing the trace logs, see the “Using Cisco Unity Connection Serviceability Traces to Troubleshoot Problems” section.