A and C
The CallManager Serviceability Alarm menu has only two options: Alarm and Alarm Definitions. The first allows the configuration of alarms on individual servers and services. The latter allows you to get a full definition of each alarm (and add your own custom notes to the alarm, if necessary).
The only true statement is that more than one destination can be used to write alarm logs in parallel, and each of them can use its own alarm level. Cisco CallManager relies on the reporting destination to have the proper functionality if e-mail or any other notifications are necessary.
You can configure alarms for every Cisco CallManager service through the Serviceability pages; however, you must enable Java application alarms through the Windows Registry.
A, D, and E
SDI traces log services and run-time events, whereas SDL traces log call-processing information. Both of these traces can be written to plaintext and XML files based on your Cisco CallManager Serviceability configuration.
The Trace Collection tool alleviates much of the trace analysis function from the Cisco CallManager server. This helps save resources and makes for easier, offline analysis of the trace files. The Trace Collection tool downloads and compresses trace files from Cisco CallManager systems to a computer. You can then use a text editor or the Bulk Trace Analysis tool to analyze the files.
C and D
The Trace Analysis tool only has the ability to analyze trace files that are less than 2 MB in size and are in XML format.
You must access the Q.931 Translator through the web interface of the CallManager Serviceability pages. The Voice Log Translator can be used to analyze log files without access to the Cisco CallManager system.
B and D
The SDL trace logging focuses on call logs between IP telephony devices. Naturally, only the Cisco CallManager and CTIManager services will support these types of log files.
The CallManager alarm levels use the same mappings as the syslog messages. An alarm level 5 is assigned a name of "Critical." The only levels above this are Alert (level 6) and Emergency (level 7).
A, B, and D
Cisco CallManager does not support sending alarms directly to SMTP servers (e-mail addresses). It relies on the Real-Time Monitoring Tool (RTMT) to provide this functionality. Cisco also assumes that you will configure the Microsoft Event Log or syslog server to use an SMTP alerting function, if necessary.
Part I: Cisco CallManager Fundamentals
Introduction to Cisco Unified Communications and Cisco Unified CallManager
Cisco Unified CallManager Clustering and Deployment Options
Cisco Unified CallManager Installation and Upgrades
Part II: IPT Devices and Users
Cisco IP Phones and Other User Devices
Configuring Cisco Unified CallManager to Support IP Phones
Cisco IP Telephony Users
Cisco Bulk Administration Tool
Part III: IPT Network Integration and Route Plan
Cisco Catalyst Switches
Configuring Cisco Gateways and Trunks
Cisco Unified CallManager Route Plan Basics
Cisco Unified CallManager Advanced Route Plans
Configuring Hunt Groups and Call Coverage
Implementing Telephony Call Restrictions and Control
Implementing Multiple-Site Deployments
Part IV: VoIP Features
Configuring User Features, Part 1
Configuring User Features, Part 2
Configuring Cisco Unified CallManager Attendant Console
Configuring Cisco IP Manager Assistant
Part V: IPT Security
Securing the Windows Operating System
Securing Cisco Unified CallManager Administration
Preventing Toll Fraud
Hardening the IP Phone
Understanding Cryptographic Fundamentals
Understanding the Public Key Infrastructure
Understanding Cisco IP Telephony Authentication and Encryption Fundamentals
Configuring Cisco IP Telephony Authentication and Encryption
Part VI: IP Video
Introducing IP Video Telephony
Configuring Cisco VT Advantage
Part VII: IPT Management
Introducing Database Tools and Cisco Unified CallManager Serviceability
Configuring Alarms and Traces
Using Additional Management and Monitoring Tools
Part VIII: Appendix
Appendix A. Answers to Review Questions