A and E
Microsoft SQL Server 2000 Enterprise Manager allows you to manipulate the SQL database in many ways. It can be a dangerous tool because it can corrupt the CallManager database structure quite easily. Cisco recommends using the DBLHelper utility, which can quickly verify the status of the database replication and make repairs, if necessary.
Cisco CallManager Serviceability provides services to monitor alarms, generate CARs, and collect and analyze traces. All other statements are false.
A and C
The only services that can be managed through the Control Center are those that relate directly to the Cisco CallManager. In this case, the Cisco CallManager and TFTP services are valid choices. There is no Cisco DHCP service, and the Extension Mobility function is controlled as a TomCat web service. Cisco WebDialer is a separate application install.
C and E
The Cisco CallManager services can be activated and deactivated through either the Windows 2000 Services MMC or in Cisco CallManager Service Activation. Cisco recommends the latter of these.
The DBLHelper application should only be run directly on the publisher server because this server holds the only writable copy of the SQL database.
Because the publisher holds the only writable copy of the SQL database, all configuration changes are prevented until the publisher server is restored.
CDRs are the "exception to the rule" of modifying the database while the publisher server is down. In actuality, the SQL database is not modified, rather, the subscribers will write CDRs to their SQL transaction file while the publisher is down and replicate the updates back to the publisher after connectivity is restored.
A and C
Only the publisher server will have a Replication Monitor (which has an image that looks like a heartbeat monitor) utility and will have a Publications folder under the database you are examining.
DBLHelper provides an extremely simple interface that holds little risk for damaging the SQL Server 2000 database structure when repairing replication issues. SQL Server 2000 Enterprise Manager should only be used if DBLHelper is unable to repair the replication.
A green smiley face means replication is working okay, whereas a red sad face indicates a replication failure.
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