Troubleshooting a Garbled Audio Stream in the Network
When the audio stream is garbled when Cisco Unity Connection created the recording, use the following task list to determine the cause and to resolve the problem. Do the tasks in the order presented until the problem is resolved.
Task List for Troubleshooting a Garbled Audio Stream in the Network
1. 
Confirm that the connection to the caller is clear. Calls that have bad PSTN connections or calls from mobile phones may sometimes have garbled audio streams. Connection cannot correct for a garbled audio stream.
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 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 Connection server by obtaining a sniffer capture at that point. If the audio stream from the sniffer capture is not garbled, Connection may not be handling the audio stream correctly. See the "Troubleshooting How Cisco Unity Connection Makes Recordings" section.
Hello Deepak,
Thanks for your response, very helpful.
To start with the recommendations:
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 Connection.
What sniffer capture tool can we use and how do we know if it is garbled?
Based from the link, I tried to monitor the CPU usage and have seen that it peaks up to 83%, then went down again. Up to how much CPU usage is allowable?
