/mcpMessage Sequences See Call PickUp, on page 503 Backward Compatibility This feature is backward compatible. Call Queuing Feature Support Unified Communications Manager queuing feature provides the ability to hold callers in a queue if there are more calls distributed through the call distribution feature than it can handle at any given time until the hunt members are available to answer them. While a call is in queue, the user is given the initial greeting announcement, music on hold, repeated announcements and so on. TAPI exposes the below call reasons for the respective conditions in extendedCallInfo in the DevSpecific part of the LINECALLINFO structure. • CallQueue {45 (0x2D)} CallQueue call reason is exposed on the calling party call when the call is queued when all HuntMembers of the HuntGroup are busy • CallDeQueue {46 (0x2E)} CallDeQueue call reason is exposed on the connected party call when the dequeued-call is offered on the available Huntmember or any other DN which has been configured in the Queuing feature if no Huntmember is available • CallDeQueueTimerExpired {47 (0x2F)} CallDeQueueTimerExpired call reason is exposed on the connected party call when the queued-call timer expires and the call is offered on the DN which has been configured in the Queuing feature when the "Maximum wait time in Queue" expires • CallDeQueueAgentsBusy {48 (0x30)} CallDeQueueAgentsBusy call reason is exposed on the connected party call when all the hunt members are busy and hence the call is never queued and directly offered on the DN which has been configured in the Queuing feature when "Maximum Number of callers allowed in Queue" is reached • CallDeQueueAgentsUnavailable {49 (0x31)} CallDeQueueAgentsUnavailable call reason is exposed on the connected party call when no hunt member is either logged-in or registered and the call is offered on the DN which has been configured in the Queuing feature when "No hunt members are Logged-in or registered" TAPI shall not expose the ConnectedHuntPilotDN in the devspecific part of LINECALLINFO, on the calling party when the call is queued. The connectedHuntPilotDN is updated when the de-queued call offered on one of the hunt members is answered and goes to connected state. The following Call queue setting configurations are available in the Hunt Pilot Configuration page. 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. Cisco Unified TAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs 31 Features Supported by TSP Call Queuing Feature Support