status: Sends an message telling the router to display its status.
stop_log: Requests logmsg to stop logging messages.
symbols: Displays names of objects and symbols.
test_edit_config: Causes router to load config with the scripted interface.
test_edit_script: Causes router to test the script real time data interface.
test_indirect_route: Test request for ScriptIndirectRoute.
test_route: Analyzes routes for valid labels.
test_update_script: Causes router to test the script update interface.
tuning_param, tune: Controls tuning in the router.
watch: Sends watch expressions to the router.
Turning up ICM Call Router Tracing with RTTest
You can enable specific trace levels within RTTest by issuing the debug command, followed
by one or more trace options. Respective trace entries can then be viewed in router logs.
For example, debug /route turns up tracing to show:
•
Dialed Number (DN)
•
Automatic Number Identification (ANI)
•
Caller Entered Digits (CED), if any
•
ICM routing label returned to the carrier network.
To see all possibilities for /debug, at the RTTest prompt, enter debug /? as shown below.
rttest: debug /? Usage: debug_control [/realtime] [/5minute] [/agent]
[/config] [/route] [/halfhour] [/rcmeter] [/expr] [/select] [/dupadd]
[/failpgerror] [/symbol] [/tranroute] [/datain] [/delivery] [/cic] [/
admin] [/pervarsumm] [/pervardetail] [/expform] [/vru] [/callq] [/
activepath] [/all] [/help] [/?]
Cisco Support Tools User Guide for Cisco Unified Software Release 2.1(1)
188
Chapter 13: - Using Cisco Common Tools
How to Use the RTTest Utility
