[This is pre-release documentation and subject to change in future releases. This topic's current status is: Milestone-Ready]

Topic Last Modified: 2010-06-20

Call Park is a call management feature that is installed by default when you deploy Enterprise Voice. This topic describes what you need to have in place before you can configure Call Park and the permissions you need to perform configuration tasks.

This section assumes that you have read the planning documentation related to Call Park (see Planning for Call Management Features).

Call Park Configuration Prerequisites

Call Park requires the following components:

  • Application service

  • Call Park application

These components are installed automatically when you deploy Enterprise Voice.

If you want callers to hear music while the call is parked, a music-on-hold file is also required. A default music-on-hold file is installed automatically when you deploy Enterprise Voice. You can substitute the default file with your own music-on-hold file. Call Park uses File Store to hold the audio file.

Call Park Configuration Permissions

You can use the following administrative tools to configure Call Park:

  • Communications Server Control Panel

  • Communications Server Management Shell

You use these tools to set up the Call Park orbit table and to configure other settings used by Call Park.

Configuring Call Park requires any of the following administrative roles, depending on the task:

  • CsVoiceAdministrator: This administrator role can create, configure and manage all voice-related settings and policies.

  • CsUserAdministrator: This administrator role can enable Call Park in voice policy. This administrator role also has read-only view access to all voice configurations.

  • CsAdministrator: This administrator role can perform all of the tasks of CsVoiceAdministrator and CsUserAdministrator.

For more information about administrative permissions, see Role-Based Access Control in "Planning for Communications Server 2010".

See Also