To specify the language used for the prompts, use the locale command in Cisco Unity Express configuration trigger mode. Use the no form of this command to set the language to the system default.
locale xx_YY
no locale
U.S. English
CCN configuration trigger mode
Use the locale command to specify the language used for the prompts heard by the caller.
The following examples sets the trigger language to French.
se-10-0-0-0# config t
se-10-0-0-0(config)# ccn trigger jtapi phonenumber 1234
se-10-0-0-0(config-trigger)# locale fr_FR
se-10-0-0-0(config-trigger)# end
|
|
---|---|
Enters trigger configuration mode. |
|
Displays the CCN trigger details. |
To specify the language used for the prompts, use the locale command in Cisco Unity Express configuration trigger mode. Use the no form of this command to set the language to the system default.
locale xx_YY
no locale
U.S. English
CCN configuration trigger mode
Use the locale command to specify the language used for the prompts heard by the caller.
The following examples sets the trigger language to French.
se-10-0-0-0# config t
se-10-0-0-0(config)# ccn trigger sip phonenumber 1234
se-10-0-0-0(config-trigger)# locale fr_FR
se-10-0-0-0(config-trigger)# end
se-10-0-0-0(config)#
|
|
---|---|
Enters trigger configuration mode. |
|
Displays the CCN trigger details. |
To specify the types of messages to be displayed on the console, use the log console command in Cisco Unity Express configuration mode. To stop messages from displaying, use the no form of this command.
log console {errors | filter {module | entity | activity} | info | warning}
no log console {errors | filter {module | entity | activity}| info | warning}
errors |
Error messages. |
filter |
Events filtered from syslog. |
module |
Cue modules. |
entity |
Cue module entities. |
activity |
Cue entity actions. |
info |
Information messages. |
warning |
Warning messages. |
Only fatal error messages are displayed.
Cisco Unity Express configuration
These messages are also saved in the messages.log file.
The following example configures error messages to be displayed on the console:
se-10-0-0-0# config t
se-10-0-0-0(config)# log console errors
se-10-0-0-0(config)# exit
|
|
---|---|
Specifies the server that stores the Cisco Unity Express applications. |
To specify the types of messages to be displayed on the console, use the log console command in Cisco Unity Express configuration mode. To stop messages from displaying, use the no form of this command.
log console monitor {module | entity | activity}
no log console monitor {module | entity | activity}
module |
Cue modules. |
entity |
Cue module entities. |
activity |
Cue entity actions. |
Only fatal error messages are displayed.
Cisco Unity Express EXEC
These messages are also saved in the messages.log file.
The following example configures error messages to be displayed on the console:
se-10-0-0-0# log console monitor networking database results
|
|
---|---|
Specifies the server that stores the Cisco Unity Express applications. |
To configure an external server for saving log messages, use the log server command in Cisco Unity Express configuration mode. To delete the log server, use the no form of this command.
log server address {ip-address | hostname}
no log server address {ip-address | hostname}
ip-address |
IP address of the external log server. |
hostname |
Hostname of the external log server. |
No external log server is configured. The local hard disk is used for saving log messages.
Cisco Unity Express configuration
An external log server contains a copy of the messages.log file that is stored on the hard disk of the router that contains the Cisco Unity Express module. Copying the file to a server permits flexibility in viewing, printing, and troubleshooting system messages.
The following example assigns 10.1.61.16 as the external log server:
se-10-0-0-0# config t
se-10-0-0-0(config)# log server address 10.1.61.16
se-10-0-0-0(config)# exit
To save trace configuration upon rebooting, use the log trace boot command in Cisco Unity Express EXEC mode.
log trace boot
This command has no arguments or keywords.
Cisco Unity Express EXEC
The current trace configuration is lost upon reboot because tracing is CPU intensive. To ensure that the current trace configuration is saved when the CUE module is rebooted, use the log trace boot command.
The following example illustrates the log trace command:
se-10-0-0-0# log trace boot
|
|
---|---|
show trace |
Displays the modules and entities being traced. |
To save the current trace information, use the log trace buffer save command in Cisco Unity Express EXEC mode.
log trace buffer save
This command has no arguments or keywords.
Cisco Unity Express EXEC
Current trace information stored in the memory buffer can be saved to a file. The file created with the log trace buffer save command is atrace_save.log.
The following example illustrates the log trace command:
se-10-0-0-0# log trace buffer save
|
|
---|---|
Displays the modules and entities being traced. |
|
Displays a list of the trace logs. |