Cisco Cisco Administrative Workstation Technical References
64
Error! No text of specified style in document.
64
really is. If the agent enters the “Not Ready” state in this interval
TPF
1
FPT
, the PG
will assign all of the time since the call hung up to the handle time for the
call, even if the agent had actually entered the NCCM server “Idle” state
after the call hung up and had subsequently entered the “Not Ready” state.
call, even if the agent had actually entered the NCCM server “Idle” state
after the call hung up and had subsequently entered the “Not Ready” state.
Also if the agent answers another call in the above mentioned interval, the
PG will attribute all of the time before the new call is answered, to the
handle time for the previous call even if the agent was actually in the
“Idle” state between the two calls.
PG will attribute all of the time before the new call is answered, to the
handle time for the previous call even if the agent was actually in the
“Idle” state between the two calls.
5.4. Handling of ROUTE CALL Script Command
Two cases can occur when the processing of a NCCM server call leads to
the execution of a
the execution of a
ROUTE CALL XXXX
script command:
XXXX is a number that sends the call off-switch (e.g., a number
that includes a trunk access code).
that includes a trunk access code).
In this case, the call is no longer under the control of the NCCM server
software. When this occurs the PG receives no more information about
the call and stops monitoring it. The call is removed from real time
calls in queue statistics. The disposition in the termination call detail
record is set to “Redirected.” The call is reflected in historical services
records as an “overflow out” call.
software. When this occurs the PG receives no more information about
the call and stops monitoring it. The call is removed from real time
calls in queue statistics. The disposition in the termination call detail
record is set to “Redirected.” The call is reflected in historical services
records as an “overflow out” call.
If the call is routed to another CDN or ACD DN on the same switch
(e.g., a trunk call that winds up going to a number on the same switch)
the PG will track this as a new call.
(e.g., a trunk call that winds up going to a number on the same switch)
the PG will track this as a new call.
XXXX is a number that is local to the switch (e.g., the number of a
local ACD DN).
local ACD DN).
In this case, the Aura Contact Center PG will continue to track the call
as long as you have specified the “local” parameter in the HDX
Routed command. (See “
as long as you have specified the “local” parameter in the HDX
Routed command. (See “
for more information.)
5.5. Handling of ROUTE CALL CONTROLLED Script
Command
Two cases can occur when the processing of a NCCM server call leads to
the execution of a
the execution of a
ROUTE CALL XXXX CONTROLLED
script command:
XXXX is a number that sends the call off-switch (e. g. a number
that includes a trunk access code).
that includes a trunk access code).
In this case, the call may no longer be under the control of the NCCM
server software. When the PG receives the
server software. When the PG receives the
SEND INFO
command
associated with the
ROUTE CALL CONTROLLED
it has no way of
determining whether the
ROUTE CALL CONTROLLED
will terminate
NCCM server processing, or whether control will return to the NCCM
server script. Therefore, the PG waits for a period of time to see if it
server script. Therefore, the PG waits for a period of time to see if it
TP
1
PT
The interval between when the call hangs up and when the PG receives an RTD
message telling it what SCCS state the agent entered after the call hung up.