Working with queues
Contents
Learn about call models for queues.
For simplicity, the examples on this page use abbreviated attribute values. For example, ConnID 1, which – in actual events – displays as <ConnID>@<metainformation>.
The following comments and abbreviations are used in the call models:
- OPT–Optional.
 - DIAL–Might be a dialed number or is not present if Voice Microservices have no information about the other party.
 
Multiple-queue call treated at an IVR port with treatment at IVR queue
The following table describes a multiple-queue call treated at an IVR port with treatment at the IVR queue.
| A | Q1 | Q2 | Q3 | IVR | Agent | 
| Inbound/internal call to Q1 | Call to Q1 | ||||
| EventDialing ConnID 1  | 
|||||
| EventQueued ConnID 1  | 
|||||
| Call placed in second queue | |||||
| EventQueued ConnID 1  | 
|||||
| Call placed in IVR queue for treatment when no agents ready  | 
|||||
| EventQueued ConnID 1  | 
|||||
| EventDiverted ConnID 1  | 
EventRinging ConnID 1  | 
||||
| Answer | |||||
| EventEstablished ConnID 1  | 
|||||
| Agent Ready | |||||
| EventDiverted ConnID 1  | 
EventDiverted ConnID 1  | 
EventReleased a ConnID 1  | 
EventRinging ConnID 1  | ||
| Answer | |||||
| EventEstablished b ConnID 1  | 
EventEstablished ConnID 1  | 
a. EventReleased can occur before an agent becomes available because the IVR finishes call treatment.
b. In some deployments, EventEstablished for party A can occur at the same time as the IVR EventEstablished, especially if a call comes through the PSTN.
Abnormal call flow
| Interruption Point | A | Q1 | Q2 | Q3 | IVR | Agent | 
| * | EventReleased OtherDN Q1  | 
EventAbandoned ConnID 1  | 
EventAbandoned ConnID 1  | 
EventAbandoned ConnID 1  | 
EventReleased ConnID 1  | 
Multiple-queue, call treated at an IVR port with direct treatment at IVR port
The following table describes a multiple-queue call treated at an IVR port with direct treatment at the IVR queue.
| External party | Q1 | Q2 | IVR | Agent | 
| Inbound/internal call to Q1 | Call to Q1 | |||
| EventDialing ConnID 1  | 
||||
| EventQueued ConnID 1  | 
||||
| Call placed in second queue | ||||
| EventQueued ConnID 1  | 
||||
| Call placed directly to IVR port | ||||
| EventRinging ConnID 1  | 
||||
| Answer | ||||
| EventEstablished ConnID 1  | 
||||
| Agent ready | ||||
| EventDiverted ConnID 1  | 
EventDiverted ConnID 1  | 
EventReleased a ConnID 1  | 
EventRinging ConnID 1  | |
| Answer | ||||
| EventEstablished b ConnID 1  | 
EventEstablished ConnID 1  | 
a. EventReleased can occur before an agent becomes available because the IVR finishes call treatment.
b. In some deployments, EventEstablished for party A can occur at the same time as the IVR EventEstablished, especially if a call comes through the PSTN.
Abnormal call flow
| Interruption Point | External party | Q1 | Q2 | IVR | Agent | 
| * | EventReleased OtherDN Q1  | 
EventAbandoned ConnID 1  | 
EventAbandoned ConnID 1  | 
EventReleased ConnID 1  | 
Multiple-queue call with call removed from queue
The following table describes a multiple-queue call with the call removed from the queue.
| A | Q1 | Q2 | IVR | Agent | 
| Inbound call to Q1 | Call to Q1 | |||
| EventQueued ConnID 1  | 
||||
| Call placed in second queue | ||||
| EventQueued ConnID 1  | 
||||
| Call placed in third queue for treatment when no agents ready | ||||
| EventQueued ConnID 1  | 
||||
| Call cleared from third queue | ||||
| EventDiverted ConnID 1  | 
||||
| Agent ready | ||||
| EventDiverted ConnID 1  | 
EventDiverted ConnID 1  | 
EventRinging ConnID 1  | ||
| Answer | ||||
| EventEstablished ConnID 1  |