[Index]
Overview
The Call Park feature (Call Park and Directed Call Park) allows you to manage call park numbers from the Call Park list.
Call Parks can be added either individually or in bulk using number ranges.
Multiple call park numbers can be added in a single operation, which creates the required number of individual call park numbers instead of creating masked ranges of 10, etc.
Call Park and Directed Call Park can be configured as either service specific or clusterwide, dependent on the status of the Enable Clusterwide CallPark Number/Ranges parameter on the Unified CM.
Call Park allows you to select directory numbers from a drop-down list, but also permits custom entries outside of the number inventory that can begin with '*' or '#', which are then added to the Number Inventory.
Note
Clusterwide call park numbers are available to devices hosted on any server within the Unified CM cluster. If clusterwide call park is disabled, the call park numbers are only available to devices on the nominated Unified CM server.
Clusterwide Call Park
Call Park allows users to place a call on hold, so it can be retrieved from another phone in the system, for example, a phone in another office or in a conference room.
If your users are on an active call at your phone, they can park the call to a call park extension by pressing the Park softkey or the Call Park button. Someone on another phone in your system can then dial the call park extension to retrieve the call.
You can define either a single directory number or a range of directory numbers for use as call park extension numbers. Users can park only one call at each call park extension number.
Clusterwide Directed Call Park
Directed Call Park allows a user to transfer a call to an available user-selected directed call park number.
Directed Call Park numbers are managed at site level, and allow a user to transfer a call to an available user-selected directed call park number. Configured directed call park numbers exist clusterwide. You can configure phones that support the directed call park Busy Lamp Field (BLF) to monitor the busy/idle status of specific directed call park numbers. Users can also use the BLF to speed dial a directed call park number.
Only one call can be parked at each directed call park number. To retrieve a parked call, a user must dial a configured retrieval prefix followed by the directed call park number at which the call is parked. Configure the retrieval prefix in the Directed Call Park Configuration window.
Note
Whenever changes are made to directed call park numbers, any devices that are configured to monitor those directed call park numbers by using the directed call BLF must restart to correct the display. Change notification automatically restarts impacted devices when it detects directed call park number changes. You also can use the Restart Devices button on the Directed Call Park Configuration window.
Adding Call Parks
To add call parks:
Go to (default menus) Apps Management > CUCM then choose either Clusterwide Call Park or Clusterwide Directed Call Park.
Click Add.
Browse to the required Site level.
Enter, at minimum, the following mandatory fields:
Range Size* - Enter a range size of 1 or more.
First Call or Directed Call Park Number*
Description - this description is used in the directory number inventory list view and also the Unified CM call park number.
Partition (Directed Call Park only) - The route partition of the directed call park range, selected from the drop-down list.
CUCM Server* - (Call Park only) - This field is mandatory, and a CUCM Server must be selected IF the Enable Clusterwide CallPark Number/Ranges parameter on the Unified CM is set to False.
Reversion Pattern (Directed Call Park only) - If a call is parked for longer than the allowed time, it reverts to the number selected from the drop-down list. Note that the allowed time is specified in the Call Park Reversion Timer parameter on the Unified CM.
Note
The Enable Clusterwide CallPark Number/Ranges and Call Park Reversion Timer parameters are located on the Unified CM under System > Service Parameters - Service Parameter Configuration (Advanced) - Cisco CallManager (Active) Service > Clusterwide Parameters (Feature - General) section.
Revert CSS Name (Directed Call Park only) - This is the CSS that will be used to attempt to route the call to the reversion pattern above.
Retrieval Prefix* (Directed Call Park only) - for example, a '*' may be used to retrieve a number from the call park number.
Click Save.
Title | Description | Details | |||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Call Park Number/Range * | Enter the call park extension number. You can enter literal digits or the wildcard character X (the system allows one or two Xs). For example, enter 5555 to define a single call park extension number of 5555 or enter 55XX to define a range of call park extension numbers from 5500 to 5599. Note You can create a maximum of 100 call park numbers with one call park range definition. Make sure that the call park numbers are unique. Note You cannot overlap call park numbers between Cisco Unified Communications Manager servers. Ensure that each Cisco Unified Communications Manager server has its own number range. Note The call park range is selected from the list of servers where the call originates. For example, if phone A (registered to node A) calls phone B (registered to node B) and the phone B user presses Park, phone B requires a call park range in the CSS that resides on node A. In a multinode environment where phones and gateways communicate with various nodes and where calls that originate from any server may need to be parked, the phones require a CSS that contains call park ranges from all servers. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Cisco Unified Communications Manager * | Using the drop-down list box, choose the Cisco Unified Communications Manager to which these call park numbers apply. Note You can create a maximum of 100 call park numbers with one call park range definition. Make sure that the call park numbers are unique. Note You cannot overlap call park numbers between Cisco Unified Communications Manager servers. Ensure that each Cisco Unified Communications Manager server has its own number range. Note The call park range is selected from the list of servers where the call originates. For example, if Phone A (registered to node A) calls Phone B (registered to Node B) and the phone B user presses Park, Phone B requires a call park range in the CSS that resides on Node A. In a multinode environment comprised of phones and gateways talking to various nodes, where calls originating from any server may need to be parked, the phones require a CSS that contains call park ranges from all servers. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Partition | If you want to use a partition to restrict access to the call park numbers, choose the desired partition from the drop-down list box. If you do not want to restrict access to the call park numbers, choose <None> for the partition. Note Make sure that the combination of call park extension number and partition is unique within the Cisco Unified Communications Manager. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Description | Provide a brief description of this call park number. The description can include up to 50 characters in any language, but it cannot include double-quotes (“), percentage sign (%), ampersand (&), or angle brackets (<>) |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Clusterwide Data |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Range Size * | Range Size - Can be any block size, not just 10, 100 etc |
|
|||||||||||||||||||||||||||||||||||||||||||||||
First Call Park Number * |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Clusterwide Enabled | Clusterwide Call Park Setting on CallManager |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Description |
|
||||||||||||||||||||||||||||||||||||||||||||||||
CUCM Server |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Partition |
|