cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Announcements

Cisco Community Designated VIP Class of 2020

Troubleshooting Directed Call Park

4459
Views
0
Helpful
0
Comments

 

 

Introduction

 

This document describes the tips for common directed call park problems.

 

Directed Call Park allows a user to transfer a call to an available user-selected directed call park number. Configure directed call park numbers in the Cisco Unified Communications Manager Directed Call Park Configuration window. 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. Cisco Unified Communications Manager can park only one call 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.

 

 

Example 1: Using the Directed Call Park Feature—Parked Call Gets Retrieved

 

The following example illustrates the use of the directed call park feature and retrieval of the parked call.

 

1. Users A1 and A2 connect in a call.

 

2. To park the call, A1 presses the Transfer softkey (or Transfer button, if available) and dials directed call park number 80 (for example) or presses the BLF button for directed call park number 80 (if the phone model supports the BLF button).

 

3. A1 either presses the Transfer softkey (or Transfer button) again or goes on hook to complete the directed call park transfer. This action parks A2 on directed call park number 80.

 

The user can complete the transfer only by going on hook rather than pressing the Transfer softkey (or Transfer button) a second time if the Transfer On-hook Enabled service parameter is set to True.

 

 

4. From any phone with a correctly configured partition and calling search space, user B1 dials the directed call park prefix (21, for example) followed by the directed call park number 80 to retrieve the call. B1 connects to A2.

 

Example 2: Using the Directed Call Park Feature—Parked Call Does Not Get Retrieved

 

The following example illustrates the use of the directed call park feature when the parked call does not get retrieved and reverts to the reversion number.

 

1. Users A1 and A2 connect in a call.

 

2. To park the call, A1 presses the Transfer softkey (or Transfer button, if available) and dials directed call park number 80 (for example) or presses the BLF button for directed call park number 80 (if the phone model supports the BLF button).

 

3. A1 either presses the Transfer softkey (or Transfer button) again or goes on hook to complete the directed call park transfer. This action parks A2 on directed call park number 80.

 

The user can complete the transfer only by going on hook rather than pressing the Transfer softkey (or Transfer button) a second time if the Transfer On-hook Enabled service parameter is set to True.

.

4. The call does not get retrieved before the Call Park Reversion Timer (service parameter) expires.

 

5. A2 reverts to the configured reversion number.

 

 

 

Issue :- 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 Unified Communications Manager in the cluster.
  • The partition that is assigned to the call park number does not match the partition that is assigned to the phone directory number.

 

Issue :- The call park number does not display long enough for the user.

 

Set the Call Park Display Timer to a longer duration.

 

 

Issue :- User cannot park calls. After the Transfer softkey (or Transfer button if available) is pressed and the directed call park number is dialed, the call does not get parked.

 

  • Ensure that the partition that is assigned to the call park number matches the partition that is assigned to the phone directory number.
  • Ensure that the partition and calling search space are configured correctly for the device.

 

Issue :- User cannot park calls. After pressing the Transfer softkey (or Transfer button if available) and dialing the directed call park number, the user receives a busy tone, and the IP phone displays the message, Park Slot Unavailable.

 

 

Ensure that the dialed directed call park number is not already occupied by a parked call or park the call on a different directed call park number.

 

 

Issue :- User cannot park calls. After pressing the Transfer softkey (or Transfer button if available) and dialing the directed call park number, the user receives a reorder tone or announcement.

 

 

Ensure that the dialed number is configured as a directed call park number.

 

.

Issue :- Parked calls revert too quickly.

 

Set the Call Park Reversion Timer to a longer duration.

 

Issue :- User cannot park calls. The user receives a reorder tone after the reversion timer expires.

 

Ensure that the user presses the Transfer softkey (or Transfer button if available) before dialing the directed call park number, then presses the Transfer softkey (or Transfer button) again or goes on hook after dialing the directed call park number. Because directed call park is a transfer function, the directed call park number cannot be dialed alone.

 

 

Note:- You can complete the transfer only by going on hook rather than pressing the Transfer softkey (or Transfer button) a second time if the Transfer On-hook Enabled service parameter is set to True.

 

Issue :- User cannot retrieve parked calls. After dialing the directed call park number to retrieve a parked call, the user receives a busy tone, and the IP phone displays the message, Park Slot Unavailable.

 

Ensure that the user dials the retrieval prefix followed by the directed call park number.

.

Issue :- Parked calls do not revert to the number that parked the call.

 

Check the configuration of the directed call park number to ensure that it is configured to revert to the number that parked the call rather than to a different directory number.

 

Issue :- When an attempt is made to delete a directed call park number or range, a message displays that indicates that the number or range cannot be deleted because it is in use.

 

You cannot delete a directed call park number that a device is configured to monitor (by using the BLF button). To determine which devices are using the number, click the Dependency Records link on the Directed Call Park Configuration window.

 

Issue :- After configuring a range of directed call park numbers, user cannot park a call at a number within the range.

 

Review the syntax for entering a range of directed call park numbers. If incorrect syntax is used, the system may appear to configure the range when it actually does not.

 

 

Related Links

Troubleshooting Guide for CUCM 8.x

 

 

 

 

 

 

 

 

 

 

 

 

 
CreatePlease to create content
Content for Community-Ad
FusionCharts will render here