Topic Last Modified: 2012-10-29

The Lync Server 2013 Call Park application lets Enterprise Voice users do any of the following:

When a user parks a call, Lync Server transfers the call to a temporary number, called an orbit, where the call is held until it is retrieved or it times out. Lync Server sends the orbit to the user who parked the call. To retrieve the parked call, the user can dial the orbit number or click the orbit link or button in the Conversation window.

The user who parked a call can notify someone to retrieve the call by using an external mechanism, such as instant messaging (IM) or a paging system, to communicate the orbit number to someone else. The user who parked the call can leave the Conversation window open to receive notification when the call is retrieved.

Because orbit ranges are globally unique, it is possible to retrieve calls from any Lync Server site or PBX phone if routing is configured appropriately. If no one retrieves the call within a configurable amount of time, the call rings back to the person who parked it. If that person does not answer the ringback, the call is transferred to a fallback destination, such as to an operator, if so configured. You can configure the number of times the call rings back before being transferred from one to ten times. If no one answers a transferred call, the call is disconnected. The orbit is freed when the call is retrieved or disconnected.

When you deploy Call Park, you need to reserve ranges of extension numbers for parking calls. These extensions need to be virtual extensions: extensions that have no user or phone assigned to them. You then configure the call park orbit table with the ranges of extension numbers and specify which Application service hosts the Call Park application that handles each range. Each Front End pool has a Call Park table on the corresponding Back End Server that is used to manage calls that are parked on the pool. The list of orbit ranges is stored in Central Management store and is used to route orbits to the destination pool. Each Lync Server pool where the Call Park application is deployed and configured can have one or more orbit ranges. Orbit ranges must be globally unique across the Lync Server deployment.

You also configure other Call Park settings, such as where calls are redirected if they time out and whether the person on the phone hears music while parked. You can also specify the music file to play while the call is on hold.

Customized music-on-hold files for Call Park are not backed up as part of the Lync Server 2013 disaster recovery process and will be lost if the files uploaded to the pool are damaged, corrupted, or erased. Always keep a separate backup copy of the customized music-on-hold files that you have uploaded for Call Park.

The Call Park application is a component of Enterprise Voice. When you deploy Enterprise Voice, the Call Park application is installed and activated automatically. Before you can use Call Park, however, the Enterprise Voice administrator must configure it and enable it for users through voice policy.