Predictive dialing
Contents
Learn about call models and flows for predictive dialing.
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.
Predictive call
The following table describes a predictive call.
Party A | Party B (ACD Group) | Party C |
Make predictive call (TMakePredictiveCall) | ||
EventDialing ConnID 1 |
||
Answer | ||
EventQueued ConnID 1 |
||
EventDiverted ConnID 1 |
||
EventRinging ConnID 1 |
||
Answer (TAnswerCall) | ||
EventEstablished ConnID 1 |
||
Release Phase (ConnID 1) |
a. If the switch reports that a call is connected to an answering machine, Voice Microservices also attach a key-value pair AnswerClass=AM to the call’s UserData.
Abnormal call flow
Interruption point | Party A | Party B | Party C |
* | EventReleased ConnID 1 |
||
** | EventAbandoned ConnID 1 |
||
*** | EventAbandoned ConnID 1 |
a. CallState in this case can be any of the following:
- CallStateGeneralError
- CallStateSystemError
- CallStateBusy
- CallStateNoAnswer
- CallStateAnsweringMachineDetected
- CallStateFaxDetected
- CallStateAllTrunksBusy
- CallStateQueueFull
- CallStateDropped
- CallStateSitDetected
- CallStateSitInvalidnum
- CallStateSitVacant
- CallStateSitIntercept
- CallStateSitUnknown
- CallStateSitNocircuit
- CallStateSitReorder
Predictive call with routing
The following table describes a predictive call with routing.
Party A | Party B (ACD Group) | Party C |
Make Predictive Call (TMakePredictiveCall) | ||
EventDialing ConnID 1 |
||
Answer | ||
EventQueued ConnID 1 |
||
EventRouteRequest ConnID 1 |
||
Route call to A (TRouteCall) | ||
EventRouteUsed ConnID 1 EventDiverted |
||
EventRinging ConnID 1 |
||
Answer (TAnswerCall) | ||
EventEstablished ConnID 1 |
||
Release Phase (ConnID 1) |
a. If the switch reports that a call is connected to an answering machine, Voice Microservices also attach a key-value pair AnswerClass=AM to the call’s UserData.
Abnormal call flow
Interruption point | Party A | Party B | Party C |
* | EventReleased ConnID 1 |
||
** and *** | EventAbandoned ConnID 1 |
||
**** | EventAbandoned ConnID 1 |
a. CallState in this case can be any of the following:
- CallStateGeneralError
- CallStateSystemError
- CallStateBusy
- CallStateNoAnswer
- CallStateAnsweringMachineDetected
- CallStateFaxDetected
- CallStateAllTrunksBusy
- CallStateQueueFull
- CallStateDropped
- CallStateSitDetected
- CallStateSitInvalidnum
- CallStateSitVacant
- CallStateSitIntercept
- CallStateSitUnknown
- CallStateSitNocircuit
- CallStateSitReorder
Predictive call (connected to a device specified in Extensions)
The following table describes a predictive call (connected to a device specified in extensions).
Party A | Party B (ACD Group Specified in the Extensions of TMakePredictiveCall) |
Party C (Routing Point or ACD Group) |
Party D |
Make predictive call (TMakePredictiveCall) | |||
EventDialing ConnID 1 |
|||
Answer | |||
EventQueued ConnID 1 |
|||
EventDiverted ConnID 1 |
|||
EventQueued ConnID 1 |
|||
EventDiverted ConnID 1 |
|||
EventRinging ConnID 1 |
|||
Answer (TAnswerCall) | |||
EventEstablished ConnID 1 |
|||
Release Phase (ConnID 1) |
Abnormal call flow
Interruption point | Party A | Party B | Party C | Party D |
* | EventReleased ConnID 1 |
|||
** | EventAbandoned ConnID 1 |
|||
*** | EventAbandoned ConnID 1 |
a. CallState in this case can be any of the following:
- CallStateGeneralError
- CallStateSystemError
- CallStateBusy
- CallStateNoAnswer
- CallStateAnsweringMachineDetected
- CallStateFaxDetected
- CallStateAllTrunksBusy
- CallStateQueueFull
- CallStateDropped
- CallStateSitDetected
- CallStateSitInvalidnum
- CallStateSitVacant
- CallStateSitIntercept
- CallStateSitUnknown
- CallStateSitNocircuit
- CallStateSitReorder