Cisco Cisco IPCC Web Option Release Note
How to Test the RequeryStatus Variable
You can test the error path of these script nodes using Target Requery to determine the specific
network cause of failure and conditionally retry the attempt as necessary. This is done using an
If node to check the value of the Call variable RequeryStatus. The decision path for the script
is then determined by the value of the RequeryStatus variable.
network cause of failure and conditionally retry the attempt as necessary. This is done using an
If node to check the value of the Call variable RequeryStatus. The decision path for the script
is then determined by the value of the RequeryStatus variable.
The following are possible values for the RequeryStatus variable:
Table 2: RequeryStatus Variables
Description
Requery Status Variable
CallRouter internal use. Script ends and the call was successfully sent to
the chosen target. Not visible to users.
the chosen target. Not visible to users.
REQUERY_ANSWER (0)
Routing client generated error code from ReRouteReq msg indicating a
Route Select failure
Route Select failure
REQUERY_ROUTE_SELECT_FAILURE
(1)
(1)
Routing client generated error code from ReRouteReq msg indicating the
called party is busy
called party is busy
REQUERY_CALLED_PARTY_BUSY (2)
Routing client generated error code from ReRouteReq msg indicating no
answer
answer
REQUERY_NO_ANSWER (3)
CallRouter generated error code. The attempt to send the call to target
failed because the target was not reachable (i.e., busy, ring no answer).
failed because the target was not reachable (i.e., busy, ring no answer).
REQUERY_ERROR (4)
CallRouter internal use. Script ends. The attempt to send the call to target
failed because the Routing Client did not respond within the
DivertOnBusyCallTimeout period. Not visible to users.
failed because the Routing Client did not respond within the
DivertOnBusyCallTimeout period. Not visible to users.
REQUERY_TIMED_OUT (5)
CallRouter internal use. Script ends. The attempt to send the call to target
failed because the caller hung up or the call was lost. Not visible to users.
failed because the caller hung up or the call was lost. Not visible to users.
REQUERY_ABORTED (6)
In the case of ABANDON and DISCONNECT, the CallRouter assumes
the call has ended and ends the script. The RequeryStatus value is set to
6, indicating REQUERY_ABORTED. This is used for the internal workings
of the CallRouter but is not visible to users. Which Nodes Support Target
the call has ended and ends the script. The RequeryStatus value is set to
6, indicating REQUERY_ABORTED. This is used for the internal workings
of the CallRouter but is not visible to users. Which Nodes Support Target
Which Nodes Support Target Requery
The following nodes support Target Requery:
•
•
•
Label
•
Queue
•
Queue to Agent
•
Route Select
•
Select
ICM Scripting and Media Routing Guide Cisco ICM/IPCC Enterprise & Hosted Editions Release 7.0(0)
92
Chapter 4: - Selecting Routing Targets
Using Target Requery