- Cisco Unity Express Features
- Overview of Cisco Unity Express Voice Mail and Auto Attendant
- Entering and Exiting the Command Environment
- Configuration Tasks
- Configuring System Components
- Configuring Users and Groups
- Configuring Voice Mail
- Configure Smart Licensing
- Configuring Authentication, Authorization, and Accounting
- Configuring the Administration via Telephone Application
- Configuring Auto Attendants
- Configuring Message Notification
- Configuring VoiceView Express
- Networking Cisco Unity Express
- Configuring Distribution Lists
- Configuring Security
- Backing Up and Restoring Data
- Language Support
- Configuring Advanced Voice Mail
- Advanced Configuration
- Monitoring the System
- Configuring SNMP Monitoring
- Registering Cisco Unity Express Endpoints to Cisco Unified Messaging Gateway
- Configuring Your Cisco IOS Gateway for T.37 On-Ramp and Off-Ramp Fax Support
- Troubleshooting
- Monitoring Active Calls
- Monitoring Future Messages
- Monitoring Active IMAP and VoiceView Express Sessions
- Monitoring Queues
- Displaying SNMP and Management Data Activity
- Viewing System Activity Messages
- Checking AIM Compact Flash Memory Wear Activity
- Viewing Historical Reports
- Viewing Real Time Reports
Monitoring the System
This chapter contains procedures for monitoring the Cisco Unity Express system’s health and performance and includes the following sections:
- Monitoring Active Calls
- Monitoring Future Messages
- Monitoring Active IMAP and VoiceView Express Sessions
- Monitoring Queues
- Displaying SNMP and Management Data Activity
- Viewing System Activity Messages
- Checking AIM Compact Flash Memory Wear Activity
- Viewing Historical Reports
- Viewing Real Time Reports
Monitoring Active Calls
This section describes the commands that permit monitoring of active calls on the Cisco Unity Express system and contains the following sections:
- Displaying Active Calls by Application
- Displaying Active Calls by Route
- Displaying Incoming Fax Calls
- Terminating an Active Call
Displaying Active Calls by Application
To display active calls by application, use the following command in Cisco Unity Express EXEC mode:
show ccn call application [ all [ subsystem { jtapi | sip }] |
application-name [ subsystem { jtapi | sip }]]
where all displays active calls for all applications, application-name displays active calls for the specified application, and jtapi and sip display active calls for those subsystems.
The command displays information about the port, the call, and the media.
The following is sample output for the show ccn call application command:
Displaying Active Calls by Route
Cisco Unity Express supports displaying active calls by route. (A route is a trigger number configured for an application. Use the show ccn trigger command to display a list of configured triggers.)
To display active calls by route, use the following command in Cisco Unity Express EXEC mode:
show ccn call route [ all [ subsystem { jtapi | sip }] | route-address [ subsystem { jtapi | sip }]]
where all displays active calls for all applications, route-address displays active calls for the specified route, and jtapi and sip display active calls for those subsystems.
The command displays information about the port, the call, and the media for both JTAPI and SIP subsystems.
The following example is sample output for the show ccn call route all command:
The following example displays active calls for the route 1200, which is a trigger number for the voice-mail application.
Displaying Incoming Fax Calls
To display a list of incoming fax calls when incoming calls are recorded, use the show ccn call fax incoming command in Cisco Unity Express EXEC mode. This command displays the connection time, sender’s phone number, and the receiver’s phone number for all the incoming fax sessions.
The following example is sample output for the show ccn call fax incoming command:
Terminating an Active Call
An active call can be terminated by using the call’s implementation ID or using the implementation ID of the port through which the call came in to the system. Use the show ccn call route command to obtain the call or port implementation ID. See Displaying Active Calls by Route.
To terminate an active call, use the following command in Cisco Unity Express EXEC mode:
ccn call terminate { callimplid | portimplid } impli-id
where impli-id is the implementation ID of the call or port.
The following example terminates a call with implementation ID 1567/1:
The following example terminates a call coming through a port with implementation 2225550150:
Monitoring Future Messages
Monitoring future messages involves the following procedures:
For a description of future messages, see Configuring the Delivery of Future Messages.
Displaying Future Messages
You can use several CLI commands to display information about future messages.
Displaying All Future Messages
To display details of all messages scheduled for future delivery, use the show voicemail messages future command in Cisco Unity Express EXEC mode.
The following is sample output for the command:
Displaying the Number of Future Messages for Each Subscriber
To display the number of messages scheduled for future delivery for each subscriber, use the show voicemail mailboxes command in Cisco Unity Express EXEC mode.
The following is sample output for the command:
Displaying the Number of Scheduled Messages for a Subscriber
To display the number of scheduled messages for a specific subscribe, use the show voicemail detail mailbox command in Cisco Unity Express EXEC mode.
The following is sample output for the command:
Deleting a Future Message
To delete a message scheduled for future delivery, use the following command in Cisco Unity Express EXEC mode:
voicemail message future message-id delete
where message-id is the message ID of the scheduled message. Use the show voicemail messages future command to display the message IDs of the scheduled messages.
An error message appears if message-id does not exist or if message-id does not belong to a message scheduled for future delivery.
The following example deletes a future message:
Monitoring Active IMAP and VoiceView Express Sessions
Several CLI commands are available for monitoring active IMAP and VoiceView Express sessions:
- Displaying IMAP Sessions
- Displaying VoiceView Express Sessions
- Terminating an Active VoiceView Express Session
Displaying IMAP Sessions
To display status information about active Internet Mail Access Protocol (IMAP) sessions, use the show imap sessions command in Cisco Unity Express EXEC mode.
The following is sample output for the command:

Note This command is not available on the AIM-CUE/AIM2-CUE.
Displaying VoiceView Express Sessions
To display status information about active VoiceView Express sessions, use the show voiceview sessions command in Cisco Unity Express EXEC mode.
The following is sample output for the command:

Note This command is not available on the AIM-CUE/AIM2-CUE.
Terminating an Active VoiceView Express Session
To terminate an active VoiceView Express session, use the following command in Cisco Unity Express EXEC mode:
service voiceview session terminate mailbox-id
where mailbox-id is the ID of the mailbox that has the active VoiceView Express session.
The following example terminates a VoiceView Express session for mailbox ID user 3:
Additionally, a new TUI or VoiceView Express session preempts and terminates an existing VoiceView Express session.
Monitoring Queues
Several CLI commands are available for monitoring Cisco Unity Express queues:
Monitoring Network Queues
To display status information about network queues, use the show network queues command in Cisco Unity Express EXEC mode.
The following example shows output from the command:
Monitoring Notification Queues
To display status information about message notification queues, use the following command in Cisco Unity Express EXEC mode:
show voicemail notification queue { email | phone }
where email displays details about the e-mail queue, and phone displays details about the phone notification queue.
The following example shows output from two version of the show voicemail notification queue command:
After a job enters one of the queues, you cannot delete the job. The system deletes the job after the notification is sent.
Monitoring Fax Queues
Faxes are always sent in queued mode.To display the fax queue for Cisco Unity Express IVR, use the show ccn subsystem fax outbound fax command in Cisco Unity Express IVR user EXEC mode.
The following example shows sample output from the command:
se-10-0-0-0> show ccn subsystem fax outbound queue
============================================================================
Fax ID Recipient Subject Retry Scheduled
============================================================================
15 9784551212 subject of Fax - max 30 char 1 2007/05/30 10:52:00
Displaying SNMP and Management Data Activity
If you have not configured Simple Network Management Protocol (SNMP) monitoring on the Cisco Unity Express system, see the procedure in the “Configuring SNMP Monitoring” section.
Use the following trace commands in Cisco Unity Express EXEC mode to display the SNMP and management data activity:
- trace snmp { agent all | agent debug | all } —Enables tracing of SNMP activities.
- trace management { agent all | agent debug | all } —Enables tracing of management data requests.
The following examples show sample output for these commands:
4280 06/03 10:10:31.100 snmp agnt 1 com.cisco.aesop.mgmt.snmp.SnmpNative.SnmpTableGetLong(CISCO-UNITY-EXPRESS-MIB,cueMboxTable,cueMboxNumberOfMessages,1)
4280 06/03 10:10:31.100 snmp agnt 1
com.cisco.aesop.mgmt.snmp.MBeanUtil.invoke(Voicemail:name=Stats,MboxStatsTableValue,
<parms>,<signature>)
4280 06/03 10:10:31.109 snmp agnt 1 com.cisco.aesop.mgmt.snmp.SnmpNative.SnmpTableGetLong(CISCO-UNITY-EXPRESS-MIB,cueMboxTable,cueMboxNumberOfMessages,1) = cueMboxNumberOfMessages
4280 06/03 10:10:31.171 snmp agnt 1
com.cisco.aesop.mgmt.snmp.SnmpNative.SnmpTableGetLong(CISCO-UNITY-EXPRESS-MIB,cueMboxTable,cueMboxNumberOfMessages,0)
4280 06/03 10:10:31.171 snmp agnt 1 com.cisco.aesop.mgmt.snmp.MBeanUtil.invoke(Voicemail:name=Stats,MboxStatsTableValue,
<parms>,<signature>)
4280 06/03 10:10:31.180 snmp agnt 1
com.cisco.aesop.mgmt.snmp.SnmpNative.SnmpTableGetLong(CISCO-UNITY-EXPRESS-MIB,cueMboxTable,cueMboxNumberOfMessages,0) = cueMboxNumberOfMessages
4280 06/03 10:10:31.241 snmp agnt 1
com.cisco.aesop.mgmt.snmp.SnmpNative.SnmpTableGetLong(CISCO-UNITY-EXPRESS-MIB,cueMboxTable,cueMboxNumberOfNewMessages,1)
4280 06/03 10:10:31.241 snmp agnt 1
com.cisco.aesop.mgmt.snmp.MBeanUtil.invoke(Voicemail:name=Stats,MboxStatsTableValue,
<parms>,<signature>)
4280 06/03 10:10:31.250 snmp agnt 1
com.cisco.aesop.mgmt.snmp.SnmpNative.SnmpTableGetLong(CISCO-UNITY-EXPRESS-MIB,cueMboxTable,cueMboxNumberOfNewMessages,1) = cueMboxNumberOfNewMessages
4280 06/03 10:10:31.313 snmp agnt 1
com.cisco.aesop.mgmt.snmp.SnmpNative.SnmpTableGetLong(CISCO-UNITY-EXPRESS-MIB,cueMboxTable,cueMboxNumberOfNewMessages,0)
4280 06/03 10:10:31.313 snmp agnt 1
com.cisco.aesop.mgmt.snmp.MBeanUtil.invoke(Voicemail:name=Stats,MboxStatsTableValue,
<parms>,<signature>)
4280 06/03 10:10:31.322 snmp agnt 1 com.cisco.aesop.mgmt.snmp.SnmpNative.SnmpTableGetLong(CISCO-UNITY-EXPRESS-MIB,cueMboxTable,cueMboxNumberOfNewMessages,0) = cueMboxNumberOfNewMessages
4280 06/03 10:10:31.384 snmp agnt 1
com.cisco.aesop.mgmt.snmp.SnmpNative.SnmpTableGetLong(CISCO-UNITY-EXPRESS-MIB,cueMboxTable,cueMboxNumberOfSavedMessages,1)
4280 06/03 10:10:31.385 snmp agnt 1
com.cisco.aesop.mgmt.snmp.MBeanUtil.invoke(Voicemail:name=Stats,MboxStatsTableValue,
<parms>,<signature>)
4280 06/03 10:10:31.393 snmp agnt 1
com.cisco.aesop.mgmt.snmp.SnmpNative.SnmpTableGetLong(CISCO-UNITY-EXPRESS-MIB,cueMboxTable,cueMboxNumberOfSavedMessages,1) =cueMboxNumberOfSavedMessages
4280 06/03 10:10:31.454 snmp agnt 1
com.cisco.aesop.mgmt.snmp.SnmpNative.SnmpTableGetLong(CISCO-UNITY-EXPRESS-MIB,cueMboxTable,cueMboxNumberOfSavedMessages,0)
4280 06/03 10:10:31.455 snmp agnt 1
com.cisco.aesop.mgmt.snmp.MBeanUtil.invoke(Voicemail:name=Stats,MboxStatsTableValue,
<parms>,<signature>)
4280 06/03 10:10:31.463 snmp agnt 1
com.cisco.aesop.mgmt.snmp.SnmpNative.SnmpTableGetLong(CISCO-UNITY-EXPRESS-MIB,cueMboxTable,cueMboxNumberOfSavedMessages,0) =cueMboxNumberOfSavedMessages
087 06/03 10:18:42.523 mgmt agnt 1 com.cisco.aesop.mgmt.voicemail.VoiceConnectivity.getUpdateStatus in
087 06/03 10:18:42.523 mgmt agnt 1 com.cisco.aesop.mgmt.voicemail.VoiceConnectviity.update in
087 06/03 10:18:42.524 mgmt agnt 1 com.cisco.aesop.mgmt.voicemail.VoiceConnectivity.udpateTables in
087 06/03 10:18:42.525 mgmt agnt 1 com.cisco.aesop.mgmt.SysdbUtil.get(/sw/protorbcp,device)
087 06/03 10:18:42.526 mgmt agnt 1 com.cisco.aesop.mgmt.SysdbUtil.get(/hw/eth/eh0,ip,addrdefault)
087 06/03 10:18:42.529 mgmt agnt 1 com.cisco.aesop.mgmt.voicemail.JTAPIUtil.gettapiPortStatus in
087 06/03 10:18:42.574 mgmt agnt 1 com.cisco.aesop.mgmt.voicemail.JTAPIUtil.gettapiPortStatus {3504={id=3, implid=3504, state=IDLE}, 3503={id=0, implid=3503,tate=IDLE}, 3502={id=1, implid=3502, state=IDLE}, 3500={id=2, implid=3500, stat=IDLE}}
087 06/03 10:18:42.574 mgmt agnt 1 com.cisco.aesop.mgmt.voicemail.JTAPIUtil.gettapiPortStatus out
087 06/03 10:18:42.576 mgmt agnt 1 com.cisco.aesop.mgmt.SysdbUtil.get(/sw/apps/f/ccnapps/configurations/craAesop/ccnwfapp,wfjtapi,ciscoccnatcallmanager)
087 06/03 10:18:42.581 mgmt agnt 1 com.cisco.aesop.mgmt.voicemail.JTAPIUtil.getctiveCCM in
087 06/03 10:18:42.581 mgmt agnt 1 com.cisco.aesop.mgmt.SysdbUtil.get(/sw/limit,global,applicationMode)
087 06/03 10:18:42.602 mgmt agnt 1 com.cisco.aesop.mgmt.voicemail.JTAPIUtil.getctiveCCM out
087 06/03 10:18:42.604 mgmt agnt 1 com.cisco.aesop.mgmt.SysdbUtil.get(/sw/apps/f/ccnapps/configurations/craAesop/ccnwfapp,wfsip,providerHostname)
087 06/03 10:18:42.607 mgmt agnt 1
087 06/03 10:18:42.610 mgmt agnt 1 com.cisco.aesop.mgmt.SysdbUtil.get(/sw/apps/f/ccnapps/configurations/craAesop/ccnwfapp,wfsip,providerPortnumber)
087 06/03 10:18:42.614 mgmt agnt 1 com.cisco.aesop.mgmt.SysdbUtil.get(/sw/limit,global,applicationMode)
087 06/03 10:18:42.615 mgmt agnt 1 com.cisco.aesop.mgmt.voicemail.VoiceConnectivity.udpateTables out
087 06/03 10:18:42.615 mgmt agnt 1 com.cisco.aesop.mgmt.voicemail.VoiceConnectivity.update out
087 06/03 10:18:42.616 mgmt agnt 1 com.cisco.aesop.mgmt.voicemail.VoiceConnectivity.getUpdateStatus out
Viewing System Activity Messages
Cisco Unity Express captures messages that describe activities in the system.
If you have not configured a syslog server, see the “Configuring a Syslog Server” section for the procedure.
The system activities are categorized into four levels of severity depending on their impact on the system’s functioning:
- Information—The message describes normal system activity, including debug, information, and notice messages.
- Warning—The message is an alert that a non-normal activity is occurring. The Cisco Unity Express system continues to function.
- Error—The message indicates that a system error has occurred. The Cisco Unity Express system may or may not have stopped functioning.
- Fatal—The message describes a critical, alert, or emergency situation with the system. The Cisco Unity Express system has stopped functioning.
These messages are collected and directed to three possible destinations:
- messages.log file—This option is the default. The file contains all system messages and resides on the Cisco Unity Express module hard disk. You can view them on the console or copy them to a server to review for troubleshooting and error reporting.
- Console—View the system messages as they occur with the log console info command.
- External system log (syslog) server—Cisco Unity Express copies the messages to another server and collects them in a file on that server’s hard disk. The syslog daemon configuration on the external server determines which directory will save the messages log.
The external server must be configured to listen for User Datagram Protocol (UDP) on port 514 from the IP address of the Cisco Unity Express module.
Checking AIM Compact Flash Memory Wear Activity
Cisco Unity Express tracks the use and wear of the AIM compact flash memory as log and trace data are saved to the module. To display this data, use the show interface ide 0 command in Cisco Unity Express EXEC mode.
The following is sample output:
Viewing Historical Reports
The Historical Reporting feature enables you to save information and statistics related to call and application events in a historical reporting database on the module. You can use this historical data later to generate various types of usage reports, using the Cisco Unified Communications Express Historical Reporting Client.
For information on how to configure Historical Reporting, see the “Configuring Historical Reporting” section.
To view historical reports, use the Administration > Historical Reporting option of the GUI. For instructions about using the Cisco Unified Communications Express Historical Reporting Client, see the G online help for the GUI.

Note To use the Historical Reporting feature, users must have their privileges set to ViewHistoricalReports.
Viewing Real Time Reports
The Real Time Reports feature enables you to view real-time statistics for various call-related and application-related events.
To view real-time reports, use the Reports > Real Time Reports option of the GUI. For more information about real-time reports, see the online help for the GUI.

Note To view Real Time Reports, users must have their privileges set to ViewRealtimeReports.