Reference material
proxy
On executing a proxy node the VCS attempts to forward the call to the locations specified in the current
location set. If multiple entries are in the location set then this results in a forked call. If the current location
set is empty the call is forwarded to its original destination.
The proxy node supports the following optional parameters:
timeout=<1..86400>
stop-on-busy = "yes" | "no"
The proxy action can lead to the results shown in the table below.
failure
busy
noanswer
redirection
default
The CPL can perform further actions based on these results. Any results nodes must be contained within the
proxy node. For example:
<proxy timeout="10">
<busy>
<!--If busy route to recording service-->
<location clear="yes" url="recorder">
<proxy/>
</location>
</busy>
</proxy>
reject
If a reject node is executed the VCS stops any further script processing and rejects the current call.
The custom reject strings status=string and reason=string options are supported here and should be
used together to ensure consistency of the strings.
Unsupported CPL elements
The VCS does not currently support some elements that are described in the CPL RFC. If an attempt is
made to upload a script containing any of the following elements an error message will be generated and the
VCS will continue to use its existing policy.
The following elements are not currently supported:
time-switch
n
string-switch
n
language-switch
n
Cisco VCS Administrator Guide (X8.1.1)
Timeout duration, specified in seconds
Whether to stop searching if a busy response is received
The proxy failed to route the call
Destination is found but is busy
Destination is found but does not answer
VCS is asked to redirect the call
CPL to run if the other results do not apply
CPL reference
Page 370 of 507