-
Cisco Unified CallManager Features and Services Guide, Release 5.0(1)
-
Index
-
Preface
-
Cisco CallManager Extension Mobility
-
Cisco IP Manager Assistant With Proxy Line Support
-
Cisco IP Manager Assistant With Shared Line Support
-
Cisco Call Back
-
Client Matter Codes and Forced Authorization Codes
-
Music On Hold
-
Cisco CallManager AutoAttendant
-
Barge and Privacy
-
Call Park
-
Call Pickup Group
-
Immediate Divert
-
Malicious Call Identification
-
Multilevel Precedence and Preemption
-
Custom Phone Rings
-
Cisco WebDialer
-
Cisco CallManager Attendant Console
-
Call Display Restrictions
-
Quality Report Tool
-
External Call Transfer Restrictions
-
Presence
-
FeedbackTable Of Contents
System Requirements for Call Park
Calling Search Space and Partitions
Installing and Activating Call Park
Call Park Configuration Checklist
Setting the Service Parameters for Call Park
Configuring a Call Park Number
Call Park Configuration Settings
Call Park
The Call Park feature allows you to place a call on hold, so it can be retrieved from another phone in the Cisco CallManager system (for example, a phone in another office or in a conference room). If you are on an active call at your phone, you 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. You can park only one call at each call park extension number.
This chapter provides the following information about call park:
•
System Requirements for Call Park
•
•
•
•
Introducing Call Park
The Call Park feature works within a Cisco CallManager cluster, and each Cisco CallManager in a cluster must have call park extension numbers defined. (For information about using call park across clusters, see the "Using Call Park Across Clusters" section.) You can define either a single directory number or a range of directory numbers for use as call park extension numbers. Ensure that the directory number or range of numbers is unique.
Valid call park extension numbers comprise integers and the wildcard character, X. You can configure a maximum of XX in a call park extension number (for example, 80XX), which provides up to 100 call park extension numbers. When a call gets parked, Cisco CallManager chooses the next call park extension number that is available and displays that number on the phone.
Cisco CallManager can park only one call at each call park extension number.
Note
Using the Call Park Feature
Figure 9-1 illustrates the call park process.
1.
2.
3.
4.
5.
Figure 9-1 Call Park Process
Using Call Park Across Clusters
Users can dial the assigned route pattern (for example, a route pattern for an intercluster trunk could be 80XX) and the call park number (for example 8022) to retrieve parked calls from another Cisco CallManager cluster. Additionally, you must ensure that calling search spaces and partitions are properly configured. See the following example.
Example of Retrieving Parked Calls from Another Cluster
Two clusters exist in the network (cluster A and cluster B). Cluster A includes user A1 and user A2. Cluster B includes user B1 and user B2.
Cluster A includes call park numbers in the range of 81xx. Cluster B includes call park numbers in the range of 82xx, which the administrator configured.
Cluster A includes route patterns that are configured to other cluster park ranges as 82xx (routes to Cluster B). Cluster B includes route patterns that are configured to other cluster park ranges as 81xx (routes to Cluster A).
When user A1 parks a call at 8101, all users (which have correct partitions configured) in Cluster A and Cluster B can retrieve the parked call because of the route pattern configuration. When user B1 parks a call at 8202, all users (which have correct partitions configured) in Cluster A and Cluster B can retrieve the parked call because of the route pattern configuration. See Figure 9-2.
Figure 9-2 Retrieving Parked Calls by Using Intercluster Trunks
System Requirements for Call Park
To operate, call park requires the following software component:
•
The following SCCP and SIP phones support call park with the Park softkey in the Standard User and Standard Feature softkey templates:
•
The following SCCP phones support call park with the Park softkey in the Standard User and Standard Feature softkey templates:
•
The following SCCP phones support call park with the Call Park button on the phone button template:
•
•
•
Interactions and Restrictions
The following sections describe the interactions and restrictions for call park:
Interactions
The following sections describe how call park interacts with Cisco CallManager applications and call processing:
•
CTI Applications
CTI applications (for example, Attendant Console) access call park functionality, including monitoring activity on call park DNs. To monitor a call park DN, an application or end user that is associated with the CTI application must be added to the Standard CTI Allow Call Park Monitoring user group.
Refer to the "Configuration Checklist for Cisco CallManager Attendant Console" section on page 16-16 for details.
Music On Hold
Music on hold allows users to place calls on hold with music that a streaming source provides. Music on hold allows two types of hold:
•
•
Route Plan Report
The route plan report displays the patterns and directory numbers that are configured in Cisco CallManager. Use the route plan report to look for overlapping patterns and directory numbers before assigning a directory number to call park. Refer to the Route Plan Report chapter in the Cisco CallManager Administration Guide.
Calling Search Space and Partitions
Assign the Call Park directory number or range to a partition to limit call park access to users on the basis of the device calling search space. See Calling Search Space Configuration and Partition Configuration in the Cisco CallManager Administration Guide.
Immediate Divert
Call park supports Immediate Divert (iDivert softkey). For example, user A calls user B, and user B parks the call. User B retrieves the call and then decides to send the call to voice-messaging mailbox by pressing the iDivert softkey. User A receives the voice-messaging mailbox greeting of user B.
Barge
The following paragraphs describe the differences between Barge and cBarge with call park.
Barge with Call Park
The target phone (the phone that is being barged upon) controls the call. The barge initiator "piggy backs" on the target phone. The target phone includes most of the common features, even when the target is being barged; therefore, the barge initiator has no feature access. When the target parks a call, the barge initiator then must release its call (the barge).
cBarge with Call Park
The target and barge initiator act as peers. The cBarge feature uses a conference bridge, which makes it behave similar to a MeetMe conference. Both phones (target and barge initiator) have full access to their features.
Restrictions
The following restrictions apply to call park:
•
•
•
•
See the "Configuring a Call Park Number" section for configuration details.
Installing and Activating Call Park
Call park, a system feature, comes standard with Cisco CallManager software. It does not require special installation.
Configuring Call Park
This section contains the following information:
•
•
•
Call Park Configuration Checklist
Table 9-1 provides a checklist to configure Call Park.
Table 9-1 Call Park Configuration Checklist
Step 1
Configure a partition for call park extension numbers to make partition available only to users who have the partition in their calling search space.
Configuring a Partition, Cisco CallManager Administration Guide
Media Termination Point Configuration, Cisco CallManager Administration Guide
Step 2
Configure a unique call park number or define a range of call park extension numbers for each Cisco CallManager in the cluster.
Step 3
Add all servers that call park uses to the appropriate Cisco CallManager group.
Note
Cisco CallManager Group Configuration, Cisco CallManager Administration Guide
Step 4
Assign the Standard User softkey template to each device that has call park access. For phones that do not use softkeys, the phone button template with the Call Park button automatically gets configured.
Softkey Template Configuration, Cisco CallManager Administration Guide
Step 5
In the User Group Configuration window, assign application and end users to the Standard CTI Allow Call Park Monitoring user group. This applies only to users associated with CTI applications requiring Call Park monitoring capability (for example, Attendant Console).
Adding Users to a User Group, Cisco CallManager Administration Guide
Step 6
Notify users that the call park feature is available.
Refer to the phone documentation for instructions on how users access call park features on their Cisco IP Phone.
Setting the Service Parameters for Call Park
Cisco CallManager provides two clusterwide service parameters for call park: Call Park Display Timer and Call Park Reversion Timer. Each service parameter includes a default and requires no special configuration.
•
•
Note
Finding a Call Park Number
Because you may have several call park numbers in your network, Cisco CallManager lets you locate specific call park numbers on the basis of specific criteria. Use the following procedure to locate call park numbers.
Note
Procedure
Step 1
The Find and List Call Park Numbers window displays. Use the two drop-down list boxes to search for a call park number.
Step 2
•
•
•
•
Note
From the second Find Call Park Numbers where drop-down list box, choose one of the following criteria:
•
•
•
•
•
•
Step 3
Tip
A list of discovered call park numbers displays by
•
•
•
•
•
Step 4
The window displays the call park number that you choose.
Additional Information
See the "Related Topics" section.
Configuring a Call Park Number
This section describes how to add, copy, and update a single call park extension number or range of extension numbers.
Procedure
Step 1
Step 2
•
•
•
The Call Park Number Configuration window displays.
Step 3
Step 4
Additional Information
See the "Related Topics" section.
Call Park Configuration Settings
Table 9-2 describes the call park configuration settings. For related procedures, see the "Related Topics" section.
Deleting a Call Park Number
This section describes how to delete call park numbers from the Cisco CallManager database.
Procedure
Step 1
Step 2
Step 3
Note
Additional Information
See the "Related Topics" section.
Troubleshooting Call Park
Table 9-3 provides troubleshooting recovery tips for common call park problems.
Table 9-3 Troubleshooting Tips for Call Park
User cannot park calls. When the user presses the Park softkey or feature button, the call does not get parked.
Ensure that a unique call park number is assigned to each Cisco CallManager in the cluster. See the "Configuring a Call Park Number" section.
The partition that is assigned to the call park number does not match the partition that is assigned to the phone directory number. See the "Configuring a Call Park Number" section and the "Configuring a Directory Number" section in the Cisco CallManager Administration Guide.
The call park number does not display long enough for the user.
Set the Call Park Display Timer to a longer duration. See the "Setting the Service Parameters for Call Park" section.
Additional Information
See the "Related Topics" section.
Related Topics
•
•
•
•
•
•
•
•
•
•
•
•
