When No Hunt Members Are Logged In or Registered

E.

There are three main scenarios where alternate numbers are used: -> When queue is full When maximum wait time is met -

-> When no hunt members are logged in or registered When queue is full - Call Queuing allows up to 100 callers to be queued per hunt pilot (the maximum number of callers allowed in queue on a hunt pilot page)

Once this limit for new callers been reached on a particular hunt pilot, subsequent calls can be routed to an alternate number.

This alternate number can be configured through the "Destination When Queue is Full" settings)

Hunt Pilot configuration page (through the When maximum wait time is met - Each caller can be queued for up to 3600 seconds per hunt pilot (the maximum wait time in queue)

Once this limit is reached, that caller is routed to an alternate number.

This alternate number can be configured through the Hunt Pilot configuration page (through the "Maximum wait time in queue" settings)

When no hunt members are logged in or registered In a scenario where none of the members of the hunt pilot are available or registered at the time of the call, hunt pilot configuration provides an alternate number field (through the "When no hunt members are logged in or registered" settings) where calls can be routed.

For Call Queuing, a hunt pilot member is considered available if that member has both deactivated do not disturb (DND) and logged into the hunt group.

In all other cases, the line member is considered unavailable or logged off.

References: http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/admin/9_0_1/ccmfeat/CUCM_BK_CEF0C471_00_cucm-features-services-guide-90/ CUCM_BK_CEF0C471_00_cucm-features-and-services-guide_chapter_0111.html.

When no hunt members are logged in or registered to a Cisco Unified Communications Manager (CUCM) native call queue, the call handling depends on the configuration settings of the hunt pilot and line group associated with the call queue. Here's a detailed explanation of the options mentioned in the answers:

A. Forward Hunt No Answer settings: If the Forward Hunt No Answer setting is configured on the Hunt Pilot configuration page, calls to the call queue are forwarded to the specified destination after a specified number of rings or seconds if no hunt member answers the call.

B. Not Available Hunt Option settings: If the Not Available Hunt Option is configured on the Line Group Configuration page, calls to the call queue are handled based on the specified option when no hunt member is available. The available options are Try Next Member, Hunt Group, or Final.

C. Forward Hunt Busy settings: If the Forward Hunt Busy setting is configured on the Hunt Pilot configuration page, calls to the call queue are forwarded to the specified destination if all hunt members are busy.

D. Forward Busy Calls To destination: If the Forward Busy Calls To destination is configured on the Line Group Configuration page, calls to the call queue are forwarded to the specified destination when all members of the line group are busy. If this setting is not configured, the call is disconnected.

E. Queuing section parameters: The Queuing section on the Hunt Pilot Configuration page allows the administrator to configure various parameters related to call queuing, such as maximum wait time, maximum number of callers, and queuing priority. These parameters control how the call queue behaves when there are no available hunt members to answer the call.

Therefore, the correct answer depends on the specific configuration of the hunt pilot and line group associated with the call queue. The administrator can choose any of the above options to configure the call queue behavior when no hunt members are logged in or registered.