TCL vs.

VXML Applications
TCL and VoiceXML are two different approaches to provide automated functions on voice gateway such
as IVR, B-ACD, CAC, Calling Routing Maniplution, etc.
The main difference between Tcl and VoiceXML is that the router executes a Tcl scripts by it self (the
script can be stored locally or remote location), whereas a VoiceXML script is a client-server model. If the
gateway associates a call with a VoiceXML application, the application loads the appropriate VoiceXML
document that can call for the gateway to interact with various web applications. This document might
play audio prompts and collect digits. You can load additional VoiceXML documents based on the caller
input.
Note: MGCP is not supported with Tcl or VoiceXML applications. To support applications, the
gateway

Deploying TCL Scripts and VoiceXML

1.

For TCL scripts below are the required steps:

Load the script to flash memory or the TFTP server
HQ#dir
Directory of flash:/

47 -rw30421 Jan 24 2010 00:37:46 +00:00 app-b-acd-3.0.0.2.tcl

48 -rw- 1016832 Jan 24 2010 00:37:36 +00:00 app-b-acd-3.0.0.2-ReadMe.txt
49 -rw55599 Jan 24 2010 00:38:06 +00:00 app-b-acd-aa-3.0.0.2.tcl
2. Load the associated audio prompts to flash memory or the RTSP server
HQ#dir
Directory of flash:/

3.

7 -rw75650 Jan 24 2010 00:38:30 +00:00 en_bacd_allagentsbusy.au

8 -rw83291 Jan 24 2010 00:38:58 +00:00 en_bacd_disconnect.au
9 -rw63055 Jan 24 2010 00:39:20 +00:00 en_bacd_enter_dest.au
10 -rw37952 Jan 24 2010 00:39:34 +00:00 en_bacd_invalidoption.au
11 -rw496521 Jan 24 2010 00:42:08 +00:00 en_bacd_music_on_hold.au
12 -rw123446 Jan 24 2010 00:42:48 +00:00 en_bacd_options_menu.au
13 -rw42978 Jan 24 2010 00:43:04 +00:00 en_bacd_welcome.au
Initialize the application
application
service application-name location

4.

Specify the initial local parameter values

application
service application-name
param parameter-name value

5.

Configure the dial peers to use the script or ephone-dn/voice register pool.
dial-peer voice ID [voip|pots]
service application-name
or
ephone-dn ID
application application-name

or
voice register pool ID
application application-name
TCL/VoiceXML services are applied to inbound dial-peers (inbound calls only). To apply them to
outbound calls,
dial-peer voice ID [voip|pots]
service application-name outbound
6.

TCL scriptes can call packages. Packages are C subrouties or functions which can be called by the main
script (program). Packages should be uploaded to flash or TFTP server and defined as below:
package package-name location
Then the package can be called using its name in the TCL script. To check all available packeges use the
command show call application voice summary

7.

Specify the initial global parameter values

Parameters have two types: local and global. Local parameters are defined per script (you can have two
local parameters sharing same name in two different scripts. Each will be initialized individually) while
global parameters are shared between all scripts.
Global parameters initialization is applied in one location and will impact the same parameter in all
scriptes sharing it. An example of global paramters are package parameters.
Below command can be used to initialize global parameters:
paramspace parameter-namespace parameter-name parameter-value
This can be applied per dial-peer, service level (global), per-package with precendece order from high
(dial-peer) to low (package) in case same initialization applied at differnet locations.
Note: If you change a parameter value, you must reload the script for the changes to take effect.

1.

For VXML deployments:

Initialize the application
application
service application-name location

2.

Note: The location of the VXML should point to VXML server, e.g. Mobile Voice Access
Configure the dial peers to use the application or ephone-dn/voice register pool.
dial-peer voice ID [voip|pots]
service application-name
or
ephone-dn ID
application application-name
or

voice register pool ID

application application-name
TCL/VoiceXML services are applied to inbound dial-peers (inbound calls only). To apply them to
outbound calls,
dial-peer voice ID [voip|pots]
service application-name outbound
3. Configure an outbound dial peer (SIP/H323) pointing to VXML server.
Note: Inbound dial-peers providing TCL/VXML applications cant be used for other purposes, e.g.
normal inbound PSTN calls.
Posted by Mohammed Al Baqari at 2:27 am