Feature Configuration Guide for Cisco Unified Communications Manager, Release 15 and SUs - Call Park and Directed Call Park

Publisher

Cisco Systems

URL

https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/admin/cucm_b_feature-configuration-guide-for-15/cucm_mp_c6f1c31d_00_call-park-and-directed-call.html

Published

2026-09-16

Updated

unknown

Accessed

2026-09-24

HTTP status

200

License

Cisco documentation; all rights reserved; no-redistribution; short excerpts and locators only

Source notes citing this source

• The clusterwide service parameter Enable cluster-wide Call Park Number/Ranges (Feature - General) defaults to False and decides whether Call Park is cluster-wide or bound to a specific node. in context
• Cisco recommends not configuring both Directed Call Park and the Park softkey, and if both are used their number ranges must not overlap. in context
• Phones that support directed call park BLF buttons can monitor the busy or idle state of specific directed call park numbers. in context
• Parking to a directed call park number that already holds a call gives the user busy tone and the message Park Slot Unavailable. in context
• Directed call park numbers exist cluster-wide, unlike default Call Park numbers, which are bound to a node. in context
• The Retrieval Prefix is a required directed call park field, and a parked call is retrieved by dialling the retrieval prefix followed by the directed park number. in context
• If a directed call park number has no Reversion Number, an unretrieved call reverts to the parker after the Call Park Reversion Timer expires. in context
• The Release 15 Directed Call Park task flow runs: clusterwide Directed Call Park, directed call park number, BLF/Directed Call Park buttons, then synchronize with affected devices. in context
• Directed Call Park is transfer-based: the user presses Transfer, dials a directed call park number, and completes the transfer, rather than using the Park softkey. in context
• Call Park lets a user on an active call press Park to hold the call at a call park extension, which another phone then dials to retrieve the call. in context
• The Call Park Display Timer service parameter defaults to 10 seconds and sets how long the park number is shown on the parking phone. in context
• For call park to survive failover and fallback, park numbers should be configured on the publisher and on the subscriber nodes. in context
• If a hunt group member parks a call that arrived through a hunt pilot, the call goes back to the hunt pilot when the Call Park Reversion Timer expires. in context
• Users can retrieve a call parked on another Unified CM cluster by dialling an intercluster-trunk route pattern that covers the park number (for example 80XX, dialling 8022). in context
• The music on hold a parked caller hears is chosen by the parking phone's Network Hold MOH Audio Source setting. in context
• When the Park Monitoring Forward No Retrieve destination is left empty, the call returns to the parker once the Forward No Retrieve timer expires. in context
• Park Monitoring is an optional Call Park feature in which Unified CM watches a parked call and, once its timer expires, forwards it to a preassigned number, sends it to voicemail, or returns it to the parker. in context
• Park Monitoring timers can be set on a directory number, hunt pilot or universal line template, and a value of 0 or empty falls back to the corresponding service parameter. in context
• Park Monitoring uses three timers: Reversion (wait before prompting the parker), Periodic Reversion (interval between reminders) and Forward No Retrieve (reminder period before forwarding). in context
• Unified CM can park only one call at each call park extension number. in context
• A call park range may be placed in a partition to restrict which calling search spaces can reach it, or left in <None> for unrestricted access. in context
• Each call park number or range is tied to one Unified CM node through the Unified Communications Manager field, and by default every node needs its own unique park numbers. in context
• Over QSIG intercluster trunks the parked party does not see the To parked number message. in context
• A call park number or range uses digits plus at most two X wildcards, so one range (for example 80XX) gives up to 100 park extensions. in context
• The Call Park Reversion Timer service parameter defaults to 60 seconds; when it expires an unretrieved parked call returns to the device that parked it. in context
• If the same park range is reused in different partitions, users should have only one of those partitions in their calling search space. in context
• For shared lines on devices registered to different nodes, the line registers to the node on which a device registers first, so each node must carry park numbers. in context
• The Release 15 Call Park task flow runs: clusterwide Call Park, partition, call park number, softkey template, associate template with common device configuration, associate softkey with phone, Call Park button, then Park Monitoring. in context

Cite this source record

APA

WarmTransfer. (2026, September 16). Feature Configuration Guide for Cisco Unified Communications Manager, Release 15 and SUs - Call Park and Directed Call Park. WarmTransfer. https://warmtransfer.net/knowledge/sources/cisco-cucm-featcfg-15-call-park

BibTeX

@misc{warmtransfer-cisco-cucm-featcfg-15-call-park,
  title  = {Feature Configuration Guide for Cisco Unified Communications Manager, Release 15 and SUs - Call Park and Directed Call Park},
  author = {{WarmTransfer}},
  year   = {2026},
  url    = {https://warmtransfer.net/knowledge/sources/cisco-cucm-featcfg-15-call-park},
  note   = {Cisco Systems, accessed 2026-09-24}
}