Cisco Cisco MediaSense Release 8.5(3) Fehlerbehebungsanleitung

Contributed by Pavan Dave, Cisco TAC Engineer.

Nov 14, 2014

Introduction
Missing Audio
     Example
Missing or Incorrect Call Information
     Example 1 − Phone Number Clipped
     Example 2 − No Phone Number

This document describes two issues you might encounter with Cisco MediaSense and provides
troubleshooting information about them. MediaSense is a call recording platform that listens for and records
all communications directed at it. If that information, which can be voice or data, is not received or received
properly, it might not appear in MediaSense as desired or expected. However, it is often a configuration or
network−related issue.

The first type of call is where the audio is not present but the data is received. In these situations, the problem
is typically with a configuration or network−related issue with Access Control Lists (ACLs), Cisco Unified
Communcations Manager (CUCM), or Cisco Unified Border Element (CUBE).

The best way to verify this type of issue is to make sure that the call control logs are enabled, pull the logs via
the Cisco Real−Time Monitoring Tool (RTMT), and have the session ID of the missing audio call log to
search.

After you collect the call control logs, open them, search for the session ID, and verify that the size under
diskusage is not 0. If the logs show size="0", MediaSense probably did not receive the audio and that is why
it is not there.

In this example, the session ID is 78e146437088a93.

0000049583: 10.201.227.136: May 28 2014 11:27:09.022 −0400: %CCBU_COMMON−6−VSMS

 HTTP Info: {Thrd=Pool−capture−thread−2800} %[HTTP Response Body=<Session>

   <diskusage>

      <recording name="78e146437088a93−TRACK0" size="0" repository="/

       recordedMedia" />

      <recording name="78e146437088a93−TRACK1" size="0"repository="/

       recordedMedia" />

   </diskusage>

</Session>][HTTP Response Content Type=application/xml][HTTP Response Status