Cisco Unity Express (CUE) supports a rich scripting ability. Since its first release, CUE has supported a Script Editor application which is installed on a Windows XP PC to create scripts. Once saved, the files can be uploaded to a CUE module and used.
With CUE 3.0, an additional feature, called Editor Express was developed. It can be accessed via the CUE GUI and is TAC supported. Simply log in to the CUE web page with an account that has administrative rights. Then select System > Scripts. Then the New button can be pressed to start developing a script. This feature allows for quick development of simple scripts.
To clarify, TAC supports the Editor Express feature, but it is up to the user to make sure the logic of their script, error handling, etc, is correct. Editor Express scripts can also be downloaded and opened in the offline Script Editor application; however, any scripts that are uploaded cannot be accessed by the Editor Express module.
Note: Custom script editing is only applicable to auto attendant applications. The voicemail script and other system scripts cannot be altered in any way and prompts cannot be manipulated.
In most cases, try to use the Editor Express feature first. The Editor Express feature is documented in each release's Administration Guide.
Offline Script Editor Development Support
Custom script support is not available through the regular Cisco TAC. For questions, comments, and help with a custom script, send an email to email@example.com. To maximize everyone's time:
If you have a script and something's not working the way you think it should, please provide the following information when posting to the alias:
Current copy of the script (.aef) file
CUE version (show software version)
CUE configuration (show run)
CUE integration (show software license)
If CME (or if the problem only occurs in SRST mode), collect a "show run" and "show version" from the CME
Most importantly, collect a trace of the failure by issuing the following commands via the CUE CLI, ideally when there's not any other calls in the system (to minimize output). To do this, first set up a terminal emulator such that the output is being logged to a file. This will speed up collection of the output.
1. "clear trace."
2. place the call to reproduce the issue.
3. "show trace buffer long". This can generate a lot of output, even for a single call. Wait for the output to stop scrolling. It will eventually.
Note: The call should be placed immediately after the "clear trace" command, and the "show trace buffer long" should be issued immediately after the call is finished. This reduces the amount of debug lines. If too much time expires, or the issue isn't reproduced in one call, simply start over at step 1.