Cisco Unity Express -- Custom Script Editor FAQs

From DocWiki

(Difference between revisions)
Jump to: navigation, search
Line 7: Line 7:
For all versions, here is a quick start guide for creating Custom Scripts:
For all versions, here is a quick start guide for creating Custom Scripts:
 +
http://www.cisco.com/en/US/partner/products/sw/voicesw/ps5520/products_tech_note09186a008041d950.shtml
http://www.cisco.com/en/US/partner/products/sw/voicesw/ps5520/products_tech_note09186a008041d950.shtml

Revision as of 19:24, 28 July 2010

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

Answer: Starting with CUE 3.2, we have introduced script editor in the CUE Administration GUI - System -> Scripts -> New.

http://www.cisco.com/en/US/docs/voice_ip_comm/unity_exp/rel3_2/administrator/gui/edit_exp.html


For all versions, here is a quick start guide for creating Custom Scripts:

http://www.cisco.com/en/US/partner/products/sw/voicesw/ps5520/products_tech_note09186a008041d950.shtml




Question: .

Answer:




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

Answer:

Method-1:

1. Make sure the system is idle.

2. Run "clear trace" on CUE.

3. Run "show trace buffer tail" on CUE.

4. Make the simplest call to demonstrate your problem.

5. Wait until the logs stop scrolling ... Might take 3 to 5 minutes.

6. Press CTRL-C to exit.

7. Send us the logs for the failure case.


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 CUE.

4. Run “copy log atrace_save.log url ftp://x.x.x.x/....”

5. Send us this file.



Rating: 5.0/5 (2 votes cast)

Personal tools