Contents
Call Flows
request-interaction - No Delay
request-inbound-immediate - No Delay
request-inbound-delay - Delay
Customer originated, push notification, separate call for access code
Customer originated, push notification with Access Number/Access Code
request-inbound-delay-location
Customer originated, push notification, separate call for access code
Customer originated, push notification with Access Number/Access Code
request-inbound-poll
Basic Allocation
Location based Allocation
a2c-advanced-sync-enterprise-initiated request-outbound-immediate a2c-advanced-async-enterprise-initiated request-outbound-delay a2c-advanced-poll-enterprise-initiated request-outbound-poll
Advanced Outbound Requests
No Delay – request-outbound-immediate
Delay with Notification – request-outbound-delay
Delay-Polling – request-outbound-poll
Access Number Allocation
No Locking
DNIS only - no match is done here
Match DNIS + ANI
Match DNIS + Access Code
No Match
Locking
The only difference between locking and non-locking call flows is the algorithm that determines how access numbers are handed out. In this case, a given access number is only assigned to a single service which allows for a more reliable match.
Match DNIS + ANI
Same as the equivalent no lock case.
Match DNIS + Access Code
Same as the equivalent no lock case.
No Match
Same as the equivalent no lock case.
This page was last edited on February 28, 2013, at 20:15.
Comments or questions about this documentation? Contact us for support!