# Unified CM hunt pilots and hunt lists and line groups Canonical: https://warmtransfer.net/knowledge/cucm-hunt-pilots Last verified: 2026-09-24 In Unified CM Release 15, a hunt pilot is a number or pattern plus associated digit manipulations that routes calls to a group of phones or directory numbers in a line group[^45]. A hunt list is a prioritized list of line groups, while line groups allow multiple phones to answer calls directed to a single directory number[^22][^26]. ## Configuration structure and order The Release 15 hunt pilot configuration task flow requires configuring line groups first, then hunt lists, and finally hunt pilots[^12]. In the Hunt List Configuration window, a checkbox is provided to mark the hunt list as used for voice mail[^60]. Unified CM line groups cannot point to CTI ports or CTI route points, which prevents hunt pilots from distributing calls to CTI-controlled endpoints[^41]. When a call is distributed by a hunt pilot, it overrides all partition and calling search space restrictions as it is offered to line group members[^43]. Cisco does not recommend configuring Unified Mobility devices in a hunt pilot[^39]. ## Distribution algorithms and line group settings In CallManager 4.2(1), the line group RNA Reversion Timeout defines the duration in seconds after which an unanswered call is distributed to the next available or idle member, or to the next line group[^57]. Distribution algorithms documented for CallManager 4.2(1) define specific selection rules[^59][^29][^4]: - **Top Down**: Distributes calls to idle or available members starting from the first idle or available member in the line group down through the last[^59]. - **Longest Idle Time**: Distributes calls exclusively to idle members, beginning with the member idle the longest[^29]. - **Broadcast**: Distributes calls to all idle or available members of the line group simultaneously[^4]. CallManager 4.2(1) documentation advises against placing shared-line directory numbers into line groups using the Broadcast algorithm[^5]. When using the Circular algorithm, if a call offered to a logged-off agent is rejected with any reject type other than Huntlogout, the circular index does not increment and the subsequent call is directed to that same agent[^10]. ## Hunting behavior and forwarding When Unified CM hunts to a line group member, it ignores that specific member's Call Forward No Answer, Call Forward Busy, and Call Forward All configurations[^21]. If a hunt party does not answer or is busy, hunting continues to the next hunt party; once the hunt list is exhausted or times out, the call executes the hunt pilot's hunt call treatment settings[^24]. The hunt pilot Maximum Hunt Timer accepts a range of 1 to 3600 seconds, defaulting to 1800 seconds[^34]. Cisco describes this timer as the maximum duration for hunting without queuing[^33]. If a hunt member answers or the hunt list exhausts prior to expiration, the Maximum Hunt Timer is canceled[^32]. Call Forward No Coverage (CFNC) provides forwarding when the hunt list is exhausted or times out and the hunt pilot designates Use Personal Preferences for final forwarding; CFNC provides both Internal and External variants[^8]. ## Call queuing Call queuing prerequisites require activating the Cisco IP Voice Media Streaming App on at least 1 node, along with running the Cisco CallManager and Cisco RIS Data Collector services[^55]. The Release 15 task flow for call queuing consists of configuring announcements, configuring a Music On Hold audio source, configuring hunt pilot queuing, and enabling automatic logout on no answer[^56]. Hunt pilot queuing configuration accepts 1 to 100 callers for Maximum Number of Callers Allowed in Queue, with a default setting of 32[^31]. The periodic announcement interval accepts 10 to 300 seconds and defaults to 30[^44]. Enabling queuing on a hunt pilot automatically disables its Forward Hunt No Answer and Forward Hunt Busy settings[^49]. All line group hunt options for a queuing hunt pilot must be configured to Try Next Member, then Try Next Group in the hunt list[^50]. WarmTransfer's reading of the sources is that on a queuing-enabled hunt pilot, overflow is controlled by the queue-full, maximum-wait, and no-members-logged-in destinations rather than by Forward Hunt No Answer or Busy[^53]. Queuing overflow and member handling follow specific rules: - **Maximum wait time**: When a queued caller reaches the limit, Unified CM disconnects the call or routes it to a designated destination, with an optional Maximum Wait Time calling search space[^35]. - **Queue full**: Unified CM disconnects the call or directs it to an alternate destination[^46]. - **No logged-in or registered members**: The call is disconnected or routed to a secondary destination using an optional calling search space[^42]. - **Agent distribution**: When a line member becomes idle, Unified CM offers that member the caller with the longest wait time across all hunt groups to which the member belongs[^30]. - **Automatic logout**: A member who fails to answer a queue call is logged off only if Automatically Logout Hunt Member on No Answer is selected on the Line Group[^2]. Once logged off, that agent receives no further hunt calls until pressing the HLOG softkey[^20]. - **Notifications**: The Hunt Group Logoff Notification does not play for users who manually log out or are automatically logged off for missing their turn in queue[^52]. Unified CM does not support Unified Mobility with call queuing[^38]. Call queuing is also unsupported with H.323 Fast Start[^16]. ## Device logout and HLOG operation Hunt group logout operates per device rather than per line; logging out removes the device from every line group associated with it[^17]. The Logged Into Hunt Group configuration checkbox defaults to checked for all phones[^27]. The HLog softkey toggles the logged-in status and displays during On Hook, Off Hook, and Connected states[^19]. Cisco 7940 and 7960 phones using SIP, as well as third-party phones, do not support the HLog softkey and do not present Logged out of hunt groups on their status lines[^25]. Furthermore, Log Out of Hunt Groups (HLog) is incompatible with Extension Mobility Cross Cluster, and Cisco states call queuing should not be deployed alongside EMCC[^18]. ## Capacity and reporting Scale and sizing constraints include: - A single cluster supports up to 15000 hunt list devices[^11]. Cisco provides 1500 hunt lists of 10 IP phones each or 750 hunt lists of 20 IP phones each as illustrative examples within this limit[^13]. - When 1500 hunt lists are configured, Cisco recommends setting the dial plan initialization timer service parameter to 600 seconds[^14]. - A single subscriber node supports at most 100 queuing-enabled hunt pilots[^54]. - Across all queuing hunt pilots on 1 node, total queue slots are capped at 3200[^47]. - Cisco recommends placing no more than 35 directory numbers in a single Broadcast line group when call queuing is enabled[^3]. - The maximum number of media streams Unified CM can send for call queuing matches the Music On Hold stream limit[^48]. The Release 15 CDR field huntPilotDN holds the hunt pilot DN through which the call was routed and huntPilotPartition holds that DN's partition; both default to an empty string[^6]. ## See also - See also [Unified CM dial plan partitions and calling search spaces](https://warmtransfer.net/knowledge/cucm-dial-plan). - See also [Unified CM Extension Mobility and cross-cluster Extension Mobility](https://warmtransfer.net/knowledge/cucm-extension-mobility). ## Applicability Applies to: Cisco Unified Communications Manager and Cisco Unified CallManager. Deployments: on-premises and dedicated instance. Sources checked 2026-09-24. ## What remains uncertain The behavior of hunt lists when line members span across different Unified CM clusters is not covered by the sources below. ## Sources [^1]: Unified CM line groups offer four distribution algorithms: Top Down, Circular, Longest Idle Time and Broadcast. Source: [System Configuration Guide for Cisco Unified Communications Manager, Release 15 and SUs - Configure Hunt Pilots](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/admin/15/systemConfig/cucm_b_system-configuration-guide-15/cucm_b_system-configuration-guide-14_chapter_010011.html), Configure Line Groups. Checked 2026-09-24. [^2]: A line member who does not answer a queue-enabled hunt call is logged off the hunt group only if Automatically Logout Hunt Member on No Answer is checked in the Line Group window. Source: [Feature Configuration Guide for Cisco Unified Communications Manager, Release 15 and SUs - Configure Call Queuing](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/admin/cucm_b_feature-configuration-guide-for-15/cucm_m_configure-call-queuing.html), Enable Automatic Logout on No Answer. Checked 2026-09-24. [^3]: Cisco recommends no more than 35 directory numbers in a single line group that uses the Broadcast algorithm with call queuing. Source: [System Configuration Guide for Cisco Unified Communications Manager, Release 15 and SUs - Configure Hunt Pilots](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/admin/15/systemConfig/cucm_b_system-configuration-guide-15/cucm_b_system-configuration-guide-14_chapter_010011.html), Hunt Pilot Overview > performance and scalability. Checked 2026-09-24. [^4]: In CallManager 4.2(1) Broadcast distributes a call to all idle or available members of the line group simultaneously. Source: [Cisco Unified CallManager Administration Guide, Release 4.2(1) - Line Group Configuration](https://www.cisco.com/en/US/docs/voice_ip_comm/cucm/admin/4_2_1/ccmcfg/b03lngrp.html), Line Group Configuration Settings > Distribution Algorithm > Broadcast. Checked 2026-09-24. [^5]: CallManager 4.2(1) documentation says not to put shared-line directory numbers in a line group that uses the Broadcast algorithm. Source: [Cisco Unified CallManager Administration Guide, Release 4.2(1) - Line Group Configuration](https://www.cisco.com/en/US/docs/voice_ip_comm/cucm/admin/4_2_1/ccmcfg/b03lngrp.html), Line Group Configuration Settings > Distribution Algorithm note. Checked 2026-09-24. [^6]: The Release 15 CDR field huntPilotDN holds the hunt pilot DN through which the call was routed and huntPilotPartition holds that DN's partition; both default to an empty string. Source: [Call Reporting and Billing Administration Guide for Cisco Unified Communications Manager Release 15 and SUs, CDR Field Descriptions](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/callReportingBillingAdmin/15/cucm_b_reporting-billing-administration-guide-15/cucm_b_reporting-and-billing-administration-guide_chapter_01010.html), CDR Field Descriptions table > huntPilotDN; huntPilotPartition. Checked 2026-09-24. [^7]: When huntPilotDN is not populated, Cisco advises checking pattern usage 7 (PATTERN_HUNT_PILOT) to identify hunt list calls. Source: [Call Reporting and Billing Administration Guide for Cisco Unified Communications Manager Release 15 and SUs, CDR Field Descriptions](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/callReportingBillingAdmin/15/cucm_b_reporting-billing-administration-guide-15/cucm_b_reporting-and-billing-administration-guide_chapter_01010.html), CDR Field Descriptions table > huntPilotDN note. Checked 2026-09-24. [^8]: Call Forward No Coverage forwards calls when the hunt list is exhausted or timed out and the hunt pilot used for coverage specifies Use Personal Preferences for its final forwarding; it has Internal and External variants. Source: [Feature Configuration Guide for Cisco Unified Communications Manager, Release 15 and SUs - Call Forwarding](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/admin/cucm_b_feature-configuration-guide-for-15/cucm_mp_c9779fc8_00_call-forwarding-12-0.html), Call Forwarding Overview > Call Forward No Coverage; Forward No Coverage Internal/External fields. Checked 2026-09-24. [^9]: In CallManager 4.2(1) Circular distributes a call starting from the (n+1)th member, where n is the member that most recently received a call, wrapping to the top after the last member. Source: [Cisco Unified CallManager Administration Guide, Release 4.2(1) - Line Group Configuration](https://www.cisco.com/en/US/docs/voice_ip_comm/cucm/admin/4_2_1/ccmcfg/b03lngrp.html), Line Group Configuration Settings > Distribution Algorithm > Circular. Checked 2026-09-24. [^10]: With the Circular algorithm, if a call to a logged-off agent is rejected with a reject type other than Huntlogout, the circular index does not increment and the next call goes to the same agent. Source: [System Configuration Guide for Cisco Unified Communications Manager, Release 15 and SUs - Configure Hunt Pilots](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/admin/15/systemConfig/cucm_b_system-configuration-guide-15/cucm_b_system-configuration-guide-14_chapter_010011.html), Hunt Pilot Interactions and Restrictions table > Circular algorithm row. Checked 2026-09-24. [^11]: A single Unified CM cluster supports a maximum of 15000 hunt list devices. Source: [System Configuration Guide for Cisco Unified Communications Manager, Release 15 and SUs - Configure Hunt Pilots](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/admin/15/systemConfig/cucm_b_system-configuration-guide-15/cucm_b_system-configuration-guide-14_chapter_010011.html), Hunt Pilot Overview > performance and scalability. Checked 2026-09-24. [^12]: The Release 15 hunt pilot configuration task flow is line groups first, then hunt lists, then hunt pilots. Source: [System Configuration Guide for Cisco Unified Communications Manager, Release 15 and SUs - Configure Hunt Pilots](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/admin/15/systemConfig/cucm_b_system-configuration-guide-15/cucm_b_system-configuration-guide-14_chapter_010011.html), Hunt Pilot Configuration Task Flow. Checked 2026-09-24. [^13]: Cisco gives 1500 hunt lists of ten IP phones each or 750 hunt lists of twenty IP phones each as example combinations within the 15000 hunt list device limit. Source: [System Configuration Guide for Cisco Unified Communications Manager, Release 15 and SUs - Configure Hunt Pilots](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/admin/15/systemConfig/cucm_b_system-configuration-guide-15/cucm_b_system-configuration-guide-14_chapter_010011.html), Hunt Pilot Overview > performance and scalability. Checked 2026-09-24. [^14]: Cisco recommends setting the dial plan initialization timer service parameter to 600 seconds when 1500 hunt lists are configured. Source: [System Configuration Guide for Cisco Unified Communications Manager, Release 15 and SUs - Configure Hunt Pilots](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/admin/15/systemConfig/cucm_b_system-configuration-guide-15/cucm_b_system-configuration-guide-14_chapter_010011.html), Hunt Pilot Overview > performance and scalability. Checked 2026-09-24. [^15]: Forward Hunt No Answer and Forward Hunt Busy each offer Do Not Forward Unanswered Calls, Use Forward Settings of Line Group Member, or Forward Unanswered Calls to a destination with a calling search space. Source: [Feature Configuration Guide for Cisco Unified Communications Manager, Release 15 and SUs - Call Forwarding](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/admin/cucm_b_feature-configuration-guide-for-15/cucm_mp_c9779fc8_00_call-forwarding-12-0.html), Hunt Call Treatment Fields for Call Forwarding > Forward Hunt No Answer; Forward Hunt Busy. Checked 2026-09-24. [^16]: H.323 Fast Start does not support Unified CM call queuing. Source: [Feature Configuration Guide for Cisco Unified Communications Manager, Release 15 and SUs - Configure Call Queuing](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/admin/cucm_b_feature-configuration-guide-for-15/cucm_m_configure-call-queuing.html), Call Queuing Restrictions. Checked 2026-09-24. [^17]: Hunt group logout works per device: logging out removes the phone from all line groups associated with it, not from individual lines. Source: [Feature Configuration Guide for Cisco Unified Communications Manager, Release 15 and SUs - Accessing Hunt Groups](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/admin/cucm_b_feature-configuration-guide-for-15/cucm_mp_a9c61bd0_00_accessing-hunt-groups-12-0.html), Hunt Group Logout overview. Checked 2026-09-24. [^18]: Log Out of Hunt Groups (HLog) is not compatible with Extension Mobility Cross Cluster, and Cisco says call queuing should not be deployed with EMCC. Source: [Feature Configuration Guide for Cisco Unified Communications Manager, Release 15 and SUs - Configure Call Queuing](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/admin/cucm_b_feature-configuration-guide-for-15/cucm_m_configure-call-queuing.html), Call Queuing Restrictions. Checked 2026-09-24. [^19]: The HLog softkey toggles a phone between logged in and logged out of hunt groups and appears in the On Hook, Off Hook and Connected call states. Source: [Feature Configuration Guide for Cisco Unified Communications Manager, Release 15 and SUs - Accessing Hunt Groups](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/admin/cucm_b_feature-configuration-guide-for-15/cucm_mp_a9c61bd0_00_accessing-hunt-groups-12-0.html), HLog softkey. Checked 2026-09-24. [^20]: An agent logged off for not answering a queuing hunt call receives no further hunt pilot calls until pressing the HLOG softkey. Source: [Feature Configuration Guide for Cisco Unified Communications Manager, Release 15 and SUs - Configure Call Queuing](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/admin/cucm_b_feature-configuration-guide-for-15/cucm_m_configure-call-queuing.html), Enable Automatic Logout on No Answer. Checked 2026-09-24. [^21]: When Unified CM hunts to a line group member, it ignores that member's Call Forward No Answer, Call Forward Busy and Call Forward All settings. Source: [Feature Configuration Guide for Cisco Unified Communications Manager, Release 15 and SUs - Call Forwarding](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/admin/cucm_b_feature-configuration-guide-for-15/cucm_mp_c9779fc8_00_call-forwarding-12-0.html), Configure Call Forwarding when Hunt List is Exhausted or Hunt Timer Expires. Checked 2026-09-24. [^22]: A Unified CM hunt list is a prioritized list of line groups. Source: [System Configuration Guide for Cisco Unified Communications Manager, Release 15 and SUs - Configure Hunt Pilots](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/admin/15/systemConfig/cucm_b_system-configuration-guide-15/cucm_b_system-configuration-guide-14_chapter_010011.html), Configure Hunt Lists. Checked 2026-09-24. [^23]: In CallManager 4.2(1) the line group hunt options for No Answer, Busy and Not Available each offer Try next member then try next group, Try next member but do not go to next group, Skip remaining members and go directly to next group, and Stop hunting. Source: [Cisco Unified CallManager Administration Guide, Release 4.2(1) - Line Group Configuration](https://www.cisco.com/en/US/docs/voice_ip_comm/cucm/admin/4_2_1/ccmcfg/b03lngrp.html), Line Group Configuration Settings > Hunt Options. Checked 2026-09-24. [^24]: When a hunt party fails to answer or is busy, hunting resumes with the next hunt party, and after the hunt list is exhausted or times out the call follows the hunt pilot's hunt call treatment settings. Source: [Feature Configuration Guide for Cisco Unified Communications Manager, Release 15 and SUs - Call Forwarding](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/admin/cucm_b_feature-configuration-guide-for-15/cucm_mp_c9779fc8_00_call-forwarding-12-0.html), Configure Call Forwarding when Hunt List is Exhausted or Hunt Timer Expires. Checked 2026-09-24. [^25]: Cisco 7940 and 7960 phones running SIP and third-party phones do not show Logged out of hunt groups on the status line and do not support the HLog softkey. Source: [Feature Configuration Guide for Cisco Unified Communications Manager, Release 15 and SUs - Accessing Hunt Groups](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/admin/cucm_b_feature-configuration-guide-for-15/cucm_mp_a9c61bd0_00_accessing-hunt-groups-12-0.html), Hunt group logout supported devices note. Checked 2026-09-24. [^26]: Unified CM line groups let multiple phones answer calls directed to a single directory number. Source: [System Configuration Guide for Cisco Unified Communications Manager, Release 15 and SUs - Configure Hunt Pilots](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/admin/15/systemConfig/cucm_b_system-configuration-guide-15/cucm_b_system-configuration-guide-14_chapter_010011.html), Configure Line Groups. Checked 2026-09-24. [^27]: The Logged Into Hunt Group checkbox in phone configuration is checked by default for all phones. Source: [Feature Configuration Guide for Cisco Unified Communications Manager, Release 15 and SUs - Accessing Hunt Groups](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/admin/cucm_b_feature-configuration-guide-for-15/cucm_mp_a9c61bd0_00_accessing-hunt-groups-12-0.html), Logged Into Hunt Group checkbox. Checked 2026-09-24. [^28]: The Hunt Group Logoff Notification service parameter plays a distinct ring tone on a logged-off phone when a hunt group call arrives for its lines. Source: [Feature Configuration Guide for Cisco Unified Communications Manager, Release 15 and SUs - Accessing Hunt Groups](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/admin/cucm_b_feature-configuration-guide-for-15/cucm_mp_a9c61bd0_00_accessing-hunt-groups-12-0.html), Hunt Group Logoff Notification. Checked 2026-09-24. [^29]: In CallManager 4.2(1) Longest Idle Time distributes calls only to idle members, starting from the longest idle member. Source: [Cisco Unified CallManager Administration Guide, Release 4.2(1) - Line Group Configuration](https://www.cisco.com/en/US/docs/voice_ip_comm/cucm/admin/4_2_1/ccmcfg/b03lngrp.html), Line Group Configuration Settings > Distribution Algorithm > Longest Idle Time. Checked 2026-09-24. [^30]: When a line member becomes idle, Unified CM extends to that member the queued caller with the longest wait time across the multiple hunt groups the member belongs to. Source: [Feature Configuration Guide for Cisco Unified Communications Manager, Release 15 and SUs - Configure Call Queuing](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/admin/cucm_b_feature-configuration-guide-for-15/cucm_m_configure-call-queuing.html), Call Queuing Overview. Checked 2026-09-24. [^31]: Maximum Number of Callers Allowed in Queue on a Unified CM hunt pilot accepts 1 to 100 with a default of 32. Source: [Feature Configuration Guide for Cisco Unified Communications Manager, Release 15 and SUs - Configure Call Queuing](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/admin/cucm_b_feature-configuration-guide-for-15/cucm_m_configure-call-queuing.html), Configure Hunt Pilot Queuing > Maximum Number of Callers Allowed in Queue. Checked 2026-09-24. [^32]: The Maximum Hunt Timer is canceled if a hunt member answers or the hunt list is exhausted before it expires. Source: [Feature Configuration Guide for Cisco Unified Communications Manager, Release 15 and SUs - Call Forwarding](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/admin/cucm_b_feature-configuration-guide-for-15/cucm_mp_c9779fc8_00_call-forwarding-12-0.html), Hunt Call Treatment Fields for Call Forwarding > Maximum Hunt Timer. Checked 2026-09-24. [^33]: Cisco describes the Maximum Hunt Timer as the maximum time for hunting without queuing. Source: [Feature Configuration Guide for Cisco Unified Communications Manager, Release 15 and SUs - Call Forwarding](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/admin/cucm_b_feature-configuration-guide-for-15/cucm_mp_c9779fc8_00_call-forwarding-12-0.html), Hunt Call Treatment Fields for Call Forwarding > Maximum Hunt Timer. Checked 2026-09-24. [^34]: The Maximum Hunt Timer on a Unified CM hunt pilot accepts 1 to 3600 seconds with a default of 1800 seconds. Source: [Feature Configuration Guide for Cisco Unified Communications Manager, Release 15 and SUs - Call Forwarding](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/admin/cucm_b_feature-configuration-guide-for-15/cucm_mp_c9779fc8_00_call-forwarding-12-0.html), Hunt Call Treatment Fields for Call Forwarding > Maximum Hunt Timer. Checked 2026-09-24. [^35]: When a queued caller reaches the maximum wait time, the hunt pilot either disconnects the call or routes it to a configured destination, optionally with a Maximum Wait Time calling search space. Source: [Feature Configuration Guide for Cisco Unified Communications Manager, Release 15 and SUs - Configure Call Queuing](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/admin/cucm_b_feature-configuration-guide-for-15/cucm_m_configure-call-queuing.html), Configure Hunt Pilot Queuing > When maximum wait time is met. Checked 2026-09-24. [^36]: The Release 15 Feature Configuration Guide states the Maximum Wait Time in Queue field range is 10 to 3600 seconds with a default of 900 (disputed). Source: [Feature Configuration Guide for Cisco Unified Communications Manager, Release 15 and SUs - Configure Call Queuing](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/admin/cucm_b_feature-configuration-guide-for-15/cucm_m_configure-call-queuing.html), Configure Hunt Pilot Queuing > Maximum Wait Time in Queue. Checked 2026-09-24. [^37]: The Release 15 System Configuration Guide states the maximum wait time in queue for a hunt pilot ranges from 0 to 3600 seconds with a default of 900 (disputed). Source: [System Configuration Guide for Cisco Unified Communications Manager, Release 15 and SUs - Configure Hunt Pilots](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/admin/15/systemConfig/cucm_b_system-configuration-guide-15/cucm_b_system-configuration-guide-14_chapter_010011.html), Hunt Pilot Overview > performance and scalability. Checked 2026-09-24. [^38]: Unified CM does not support Unified Mobility with call queuing. Source: [Feature Configuration Guide for Cisco Unified Communications Manager, Release 15 and SUs - Configure Call Queuing](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/admin/cucm_b_feature-configuration-guide-for-15/cucm_m_configure-call-queuing.html), Call Queuing Restrictions. Checked 2026-09-24. [^39]: Cisco does not recommend configuring Unified Mobility devices in a hunt pilot. Source: [System Configuration Guide for Cisco Unified Communications Manager, Release 15 and SUs - Configure Hunt Pilots](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/admin/15/systemConfig/cucm_b_system-configuration-guide-15/cucm_b_system-configuration-guide-14_chapter_010011.html), Hunt Pilot Interactions and Restrictions table > Unified Mobility row. Checked 2026-09-24. [^40]: When a call to a hunt pilot goes unanswered in the first line group of the hunt list, Unified CM offers the call to the next line group in the hunt list. Source: [System Configuration Guide for Cisco Unified Communications Manager, Release 15 and SUs - Configure Hunt Pilots](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/admin/15/systemConfig/cucm_b_system-configuration-guide-15/cucm_b_system-configuration-guide-14_chapter_010011.html), Hunt Pilot Overview. Checked 2026-09-24. [^41]: Unified CM line groups cannot point to CTI ports or CTI route points so hunt pilots cannot distribute calls to CTI-controlled endpoints. Source: [System Configuration Guide for Cisco Unified Communications Manager, Release 15 and SUs - Configure Hunt Pilots](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/admin/15/systemConfig/cucm_b_system-configuration-guide-15/cucm_b_system-configuration-guide-14_chapter_010011.html), Hunt Pilot Overview. Checked 2026-09-24. [^42]: When no hunt members are logged in or registered, a queuing hunt pilot either disconnects the call or routes it to a secondary destination with an optional calling search space. Source: [Feature Configuration Guide for Cisco Unified Communications Manager, Release 15 and SUs - Configure Call Queuing](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/admin/cucm_b_feature-configuration-guide-for-15/cucm_m_configure-call-queuing.html), Configure Hunt Pilot Queuing > When no hunt members are logged in or registered. Checked 2026-09-24. [^43]: A call distributed by a Unified CM hunt pilot overrides all partition and calling search space restrictions when it is offered to line group members. Source: [System Configuration Guide for Cisco Unified Communications Manager, Release 15 and SUs - Configure Hunt Pilots](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/admin/15/systemConfig/cucm_b_system-configuration-guide-15/cucm_b_system-configuration-guide-14_chapter_010011.html), Hunt Pilot Overview. Checked 2026-09-24. [^44]: The periodic announcement interval for a queuing hunt pilot accepts 10 to 300 seconds with a default of 30. Source: [Feature Configuration Guide for Cisco Unified Communications Manager, Release 15 and SUs - Configure Call Queuing](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/admin/cucm_b_feature-configuration-guide-for-15/cucm_m_configure-call-queuing.html), Configure Hunt Pilot Queuing > Periodic Announcement Interval. Checked 2026-09-24. [^45]: In Unified CM Release 15 a hunt pilot is a number or pattern plus associated digit manipulations that routes calls to a group of phones or directory numbers in a line group. Source: [System Configuration Guide for Cisco Unified Communications Manager, Release 15 and SUs - Configure Hunt Pilots](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/admin/15/systemConfig/cucm_b_system-configuration-guide-15/cucm_b_system-configuration-guide-14_chapter_010011.html), Hunt Pilot Overview. Checked 2026-09-24. [^46]: When a hunt pilot queue is full, Unified CM either disconnects the new call or routes it to an alternate destination. Source: [Feature Configuration Guide for Cisco Unified Communications Manager, Release 15 and SUs - Configure Call Queuing](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/admin/cucm_b_feature-configuration-guide-for-15/cucm_m_configure-call-queuing.html), Configure Hunt Pilot Queuing > When queue is full. Checked 2026-09-24. [^47]: The total number of queue slots across all queuing-enabled hunt pilots on one Unified CM node is limited to 3200. Source: [System Configuration Guide for Cisco Unified Communications Manager, Release 15 and SUs - Configure Hunt Pilots](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/admin/15/systemConfig/cucm_b_system-configuration-guide-15/cucm_b_system-configuration-guide-14_chapter_010011.html), Hunt Pilot Overview > performance and scalability. Checked 2026-09-24. [^48]: The maximum number of media streams Unified CM can send for call queuing is the same as the Music On Hold stream limit. Source: [Cisco Collaboration Sizing Guide - Collaboration Sizing Guide for CSR 14](https://www.cisco.com/c/en/us/td/docs/solutions/PA/size/SRND_sizing14/sizing14.html), Music on Hold / call queuing sizing section. Checked 2026-09-24. [^49]: Enabling queuing on a hunt pilot automatically disables its Forward Hunt No Answer and Forward Hunt Busy settings. Source: [Feature Configuration Guide for Cisco Unified Communications Manager, Release 15 and SUs - Call Forwarding](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/admin/cucm_b_feature-configuration-guide-for-15/cucm_mp_c9779fc8_00_call-forwarding-12-0.html), Hunt Call Treatment Fields for Call Forwarding. Checked 2026-09-24. [^50]: For a queuing-enabled hunt pilot, all line group hunt options must be set to Try Next Member, then Try Next Group in the hunt list. Source: [Feature Configuration Guide for Cisco Unified Communications Manager, Release 15 and SUs - Configure Call Queuing](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/admin/cucm_b_feature-configuration-guide-for-15/cucm_m_configure-call-queuing.html), Call Queuing Interactions. Checked 2026-09-24. [^51]: With queuing enabled and no calls queued, a new call is extended to the logged-in idle line member that has been idle longest. Source: [Feature Configuration Guide for Cisco Unified Communications Manager, Release 15 and SUs - Configure Call Queuing](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/admin/cucm_b_feature-configuration-guide-for-15/cucm_m_configure-call-queuing.html), Call Queuing Overview. Checked 2026-09-24. [^52]: When call queuing is enabled on a hunt pilot, the Hunt Group Logoff Notification does not play for users who log out or are logged off for missing their turn in the queue. Source: [Feature Configuration Guide for Cisco Unified Communications Manager, Release 15 and SUs - Configure Call Queuing](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/admin/cucm_b_feature-configuration-guide-for-15/cucm_m_configure-call-queuing.html), Call Queuing Interactions > Hunt Group Logoff Notification. Checked 2026-09-24. [^53]: On a queuing-enabled hunt pilot, overflow is controlled by the queue-full, maximum-wait and no-members-logged-in destinations rather than by Forward Hunt No Answer or Busy (inferred). Source: [Feature Configuration Guide for Cisco Unified Communications Manager, Release 15 and SUs - Configure Call Queuing](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/admin/cucm_b_feature-configuration-guide-for-15/cucm_m_configure-call-queuing.html), Configure Hunt Pilot Queuing (combined with Call Forwarding chapter, Hunt Call Treatment Fields). Checked 2026-09-24. [^54]: A single Unified CM subscriber node supports at most 100 hunt pilots with call queuing enabled. Source: [System Configuration Guide for Cisco Unified Communications Manager, Release 15 and SUs - Configure Hunt Pilots](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/admin/15/systemConfig/cucm_b_system-configuration-guide-15/cucm_b_system-configuration-guide-14_chapter_010011.html), Hunt Pilot Overview > performance and scalability. Checked 2026-09-24. [^55]: Call queuing requires Cisco IP Voice Media Streaming App activated on at least one node plus the Cisco CallManager and Cisco RIS Data Collector services running. Source: [Feature Configuration Guide for Cisco Unified Communications Manager, Release 15 and SUs - Configure Call Queuing](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/admin/cucm_b_feature-configuration-guide-for-15/cucm_m_configure-call-queuing.html), Call Queuing Prerequisites. Checked 2026-09-24. [^56]: The Release 15 call queuing task flow is configure announcements, configure a Music On Hold audio source, configure hunt pilot queuing, then enable automatic logout on no answer. Source: [Feature Configuration Guide for Cisco Unified Communications Manager, Release 15 and SUs - Configure Call Queuing](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/admin/cucm_b_feature-configuration-guide-for-15/cucm_m_configure-call-queuing.html), Call Queuing Configuration Task Flow. Checked 2026-09-24. [^57]: In CallManager 4.2(1) the line group RNA Reversion Timeout is the time in seconds after which an unanswered call is distributed to the next available or idle member or to the next line group. Source: [Cisco Unified CallManager Administration Guide, Release 4.2(1) - Line Group Configuration](https://www.cisco.com/en/US/docs/voice_ip_comm/cucm/admin/4_2_1/ccmcfg/b03lngrp.html), Line Group Configuration Settings > RNA Reversion Timeout. Checked 2026-09-24. [^58]: If Logged Into Hunt Group is unchecked on any device in the hunt group, a hunt call does not extend to that user's Single Number Reach remote destinations unless all devices are logged in. Source: [System Configuration Guide for Cisco Unified Communications Manager, Release 15 and SUs - Configure Hunt Pilots](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/admin/15/systemConfig/cucm_b_system-configuration-guide-15/cucm_b_system-configuration-guide-14_chapter_010011.html), Hunt Pilot Interactions and Restrictions table > Single Number Reach row. Checked 2026-09-24. [^59]: In CallManager 4.2(1) Top Down distributes a call to idle or available members starting from the first idle or available member of the line group through to the last. Source: [Cisco Unified CallManager Administration Guide, Release 4.2(1) - Line Group Configuration](https://www.cisco.com/en/US/docs/voice_ip_comm/cucm/admin/4_2_1/ccmcfg/b03lngrp.html), Line Group Configuration Settings > Distribution Algorithm > Top Down. Checked 2026-09-24. [^60]: The Unified CM Hunt List Configuration window has a checkbox to mark the hunt list as used for voice mail. Source: [System Configuration Guide for Cisco Unified Communications Manager, Release 15 and SUs - Configure Hunt Pilots](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/admin/15/systemConfig/cucm_b_system-configuration-guide-15/cucm_b_system-configuration-guide-14_chapter_010011.html), Configure Hunt Lists procedure. Checked 2026-09-24.