Document ID: 18745
Contents
Introduction
Prerequisites
Requirements
Components Used
Conventions
Disable Both Entry and Exit Tones
Cisco Support Community - Featured Conversations
Related Information
Introduction
A tone plays when a conference participant enters or exits a conference call. The tone can be an annoyance if there is a large number of participants who enter or exit the call. This document describes how to disable these tones.
Prerequisites
Requirements
Readers of this document should have knowledge of these topics:
-
Cisco CallManager
-
Cisco Conference Connection
-
Administrator level of expertise with Microsoft Windows 2000
Components Used
The information in this document is based on Cisco Conference Connection versions 1.1.1 and 1.1.2.
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.
Disable Both Entry and Exit Tones
Complete these steps to disable the entry and exit tones.
-
Click Start > run and type regedit to open your registry editor.
-
Change the value of this registry key to 0 (zero):
HKEY_LOCAL_MACHINE\SOFTWARE\Data Connection\DCMS\SCC\PlayBeep
In Cisco Conference Connection version 1.1.1.2, look for the PlayTone key instead of PlayBeep and set it to 0 (zero).
-
After you change the registry key, reboot the Cisco Conference Connection Server during your maintenance window.
The exit and entry tones are now disabled. Consult your Cisco Technical Support engineer or your Cisco systems engineer if you are not sure about any of these procedural steps.
Cisco Support Community - Featured Conversations
Related Information
- Voice Technology Support
- Voice and Unified Communications Product Support
-
Recommended Reading: Troubleshooting Cisco IP Telephony
- Technical Support - Cisco Systems
| Updated: Feb 03, 2006 | Document ID: 18745 |