Cisco Unity Express -- Custom Script Editor FAQs

From DocWiki

Revision as of 18:56, 29 July 2010 by Saawan (Talk | contribs)
Jump to: navigation, search

Main Cisco Unity Express DocWiki Page: Cisco Unity Express

Search the Cisco Unity Express documentation on the DocWiki:


Question: What is the quickest way to start developing custom scripts?

Answer: Starting with Cisco Unity Express Release 3.2, we have introduced script editor in the CUE Administration GUI. Go to System > Scripts > New. See this link:

For all versions, here is a quick start guide for creating custom scripts:

Question: Where can I download an editor installer for my Cisco Unity Express version and sample scripts?

Answer: Download the appropriate Cisco Unity Express Custom Script Editor from Cisco's web site at:

Choose the appropriate Cisco Unity Express version that you are running.

Once you are on the appropriate Cisco Unity Express version software page, download the editor and sample scripts.

  • Click Utilities to download the Cisco Unity Express editor and install it on a windows PC.
  • Click Sample Auto-Attendant Scripts to download the sample scripts.

Question: How can I capture debug traces/logs when my script is not working as designed?

Answer: Use one of the following methods.

Method 1:

  1. Make sure the system is idle.
  2. Run "clear trace" on Cisco Unity Express.
  3. Run "show trace buffer tail" on Cisco Unity Express.
  4. Make the simplest call to demonstrate your problem.
  5. Wait until the logs stop scrolling. This may take 3 to 5 minutes.
  6. Press CTRL-C to exit.
  7. Send the logs for the failure case to Cisco.

Method 2: You will need a FTP server.

  1. Make sure the system is idle.
  2. Make the simplest call to demonstrate your problem.
  3. Run “log trace buffer save” on Cisco Unity Express.
  4. Run “copy log atrace_save.log url ftp://x.x.x.x/....”
  5. Send the file to Cisco.

Question: How can I record, add, modify, or delete various prompts?

Answer: You can assign a number to the AvT application (in the GUI, go to Voicemail > Call Handling), and record prompts by dialing into the system. You can find documentation at

Question: I am having problems installing or running the Cisco Unity Express editor on Windows XP.

Answer: If you are having problems with the installation, check the install .log file at c:\.

Some other suggestions to follow:

If the problem persists, do the following:

  • Run the editor with the -debug flag. A console window will appear. Send the traces that appeare on this console to Cisco.
  • Also send the installation log which is located under c:\CiscoInstall.log to Cisco.

Question: I have Windows 7 and the editor installer does not support it.

Answer: Windows 7 provides a way to run Windows XP on it. The procedure is outlined at Once Windows XP starts running, you may proceed to install and use Cisco Unity Express editor on it.

Question: I want my script to use dial-by-first name instead.

Answer: It is possible within every new or existing script. If you are using Editor Express then following figure shows the option to switch to dial-by-first name.


Question: I want to create a CME TCL script to perform functions like call queuing, hunt groups and music on hold.

Answer: It cannot be done with Cisco Unity Express customer script. Please get in touch TAC to configure CME or/and design a new TCL script.

Question: I want to install and use a script that can speak in two or more languages.

Answer: You can install additional languages using the CUE cli command "software install addon url <URL>". Once installed then there is a sample script on CCO called Use this script as reference design for your specific call flow. In case you are finding problems then send email to along with debug traces. The procedure of capturing debug traces is mentioned above in another FAQ.



Rating: 5.0/5 (2 votes cast)

Personal tools