Cisco Unified MeetingPlace

Document ID: 50814

Contents

Introduction
Prerequisites
      Requirements
      Components Used
      Conventions
Background Information
How It Works
Key Concepts
Related Information

Introduction

This document explains Cisco MeetingPlace Web audio functionality.

Prerequisites

Requirements

There are no specific requirements for this document.

Components Used

The information in this document is based on Cisco MeetingPlace Web (all versions).

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

Background Information

The main function of the aAudio sService in Cisco MeetingPlace Web is to perform the audio conversion fromMeetingPlace Voice (MPV, or .mpv) format to Waveform Audio (WAV, or .wav) format, and then from .wav to other formats that you have configured on your system. (The .mpvMPV files are audio files that are generated on the Cisco MeetingPlace server.) Note the order of conversion, because it plays a crucial part in understanding and troubleshooting audio problems within Cisco MeetingPlace Web.

How It Works

When a meeting is recorded and the meeting has ended, a .mpv file is automatically generated and saved on the Cisco MeetingPlace server. If Cisco MeetingPlace Web is working properly, the Cisco MeetingPlace Web Replication/Data Service downloads a copy of the .mpv file to the Microsoft Windows NT machine, and then queues the meeting for audio conversion. (If the Cisco MeetingPlace Web Replication/Data Service is stopped, the audio conversion stops at this point.)

From this point, the aAudio sService takes over. First, it converts the .mpv file to a .wav file. If successful, it converts the .wav to other formats configured on the system (such as .ra, .mp3, .wm, and so on). If all conversions are successful, the .mpv file is deleted from the Windows NT machine. The Replication/Data Service, in return, marks the conversion process as complete, and the MPAgent posts the file. However, if the aAudio sService cannot complete all conversions, the meeting's audio links are not updated and produce a "processing now" status on the Cisco MeetingPlace Web interface. The main thing to remember is that all conversions must be completed before the recordings are posted.

Key Concepts

These are some of the key concepts to understand about Cisco MeetingPlace Web audio functionality:

• The .mpv files are generated on the Cisco MeetingPlace server.

• The Data Service queues the meeting for audio conversion.

• The .mpv files are downloaded to the Windows NT machine.

• The Audio Service accepts the conversion request from Data Service.

• The Audio Service converts the .mpv file to .wav and other formats.

• If all conversions are successful, the Audio Service deletes the .mpv file on the Windows NT machine, and then reports to the Replication/Data Service.

• The Replication/Data Service marks the conversion as complete.

• The MPAgent updates the audio links on the Cisco MeetingPlace Web interface.

Related Information

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