/mcp• Maximum Number of Callers Allowed in Queue (1–100): This is the queue depth configuration and reflects the maximum number calls that can be in the queue at any point of time. • Destination When Queue is Full: User Configurable Destination number to which the calls are forwarded when the Maximum Number of callers allowed in queue limit is reached. • Disconnect: This option results in the call getting rejected and dropped when the Maximum Number of callers allowed in queue limit is reached. • Maximum Wait Time in Queue (10–3600 seconds): User configurable Maximum wait time a call can be in the queue. • Destination When Maximum Wait Time is met: User Configurable destination DN to which the call is forwarded when the maximum wait time in queue is reached. • Disconnect: This option results in the call getting rejected and dropped when the the maximum wait time in queue is reached. • When There Are No Hunt Members Logged In or Registered: User configurable destination DN to which the queue feature forwards the calls when none of the hunt members in the HuntPilot are registered or logged in. • Disconnect: This option results in the call getting rejected and dropped when there are no hunt members available for the dialed hunt pilot. • Destination: User Configurable destination DN to which the call is forwarded when no hunt members available for the dialed hunt pilot. If a caller calls a hunt pilot with all its members busy, a CiscoHuntConnection will be created temporarily. Then, when this feature is enabled, the hunt connection will drop and a new connection will be created which will have the address name same as that of the hunt pilot and the address type will be CiscoAddress.INTERNAL. This new connection will be moved to CallControlConnection.QUEUED state and it will remain in this state until the call gets dequeued or dropped. Cisco JTAPI exposes the following new reasons: • CiscoFeatureReason.REASON_QUEUING • CiscoFeatureReason.REASON_DEQUEUING • CiscoFeatureReason.REASON_DEQUEUING_TIMER_EXPIRED • CiscoFeatureReason.REASON_DEQUEUING_AGENTS_BUSY • CiscoFeatureReason.REASON_DEQUEUING_AGENTS_UNAVAILABLE The above reasons indicate when a call gets enqueued and dequeued respectively because of the various configurations on the Hunt Pilot. Cisco Unified JTAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs 126 Features Supported by Cisco Unified JTAPI Native Queuing