Keys and
NULL
Option
Data Type
Description
Name
The reason for the last Requery operation.
• REQUERY_ANSWER (0) - Script ends. The
call is successfully sent to the selected target.
This variable is used internally by the
CallRouter. You cannot test this variable in an
IF node.
• REQUERY_ROUTE_SELECT_FAILURE (1)
- Routing client generated an error code from
ReRouteReq msg indicating a Route Select
failure.
• REQUERY_CALLED_PARTY_BUSY (2) -
Routing client generated an error code from
ReRouteReq msg indicating that the called
party is busy.
• REQUERY_NO_ANSWER (3) - Routing client
generated an error code from ReRouteReq msg
indicating no answer.
• REQUERY_ERROR (4) - CallRouter generated
an error code. The attempt to send the call to
target, failed as the target is not reachable (i.e.,
busy, ring no answer).
• REQUERY_ABORTED (5) - The attempt to
send the call to a target failed as the caller
abandoned before the call is delivered to its
destination. In the case of ABANDON and
DISCONNECT, the CallRouter assumes the
call is ended and ends the script. The
RequeryStatus value is set to 5, indicating
REQUERY_ABORTED. This variable is used
internally by the CallRouter. You cannot test
this variable in an IF node.
• REQUERY_TIMED_OUT (6) - The call
attempt failed as the routing client did not
respond to the router within the
DivertOnBusyCallTimeout period (180 seconds
by default). If the target node has Router
Requery enabled, when
DivertOnBusyCallTimeout period expires, the
router closes the Router Requery with
REQUERY_TIMED_OUT. This variable is
used internally by the CallRouter. You cannot
test this variable in an IF node.
• REQUERY_NOT_SUPPORTED(7)–Requery
Database Schema Handbook for Cisco Unified Contact Center Enterprise, Release 15.0(1)
388
All Tables
Route_Call_Detail