The default CallManager installation without MLA uses the Windows 2000 Administrator account for both CallManager Administration and server administration. A sniffed username and password could mean the demise of both the CallManager Administration interface and the underlying Windows operating system.
The URL to access the Cisco CallManager Administration interface remains the same. The only difference is using the HTTPS protocol rather than just HTTP.
There is no read-write access in Cisco MLA. This setting would be the same as full access.
After you enable MLA and restart the World Wide Web Service in Windows 2000, a new account "CCMAdministrator" is stored in the Windows 2000 Registry for full CallManager Administration access.
There is no Standard Device functional group. Rather, MLA splits the device functions into the specific devices managed, such as Standard Phone or Standard Gateway.
There is no FullAccess group in the MLA user group defaults. The full access role is assigned to the SuperUserGroup.
Self-signed certificates raise an automatic red flag in any client web browser. This is because there is no trusted authority (a Certificate Authority) authenticating the web server.
The MLA user accounts are stored in an LDAP directory. By default, this is the DC Directory installed with the Cisco CallManager; however, you can change this directory storage to anther directory (such as Active Directory).
CallManager MLA stores the CCMAdminstrator account in the Windows Registry. This allows a "back door" into the CallManager Administration interface if the LDAP directory is unavailable.
A and C
By default, MLA is disabled for a clean CallManager install; however, it will remain enabled (with a new, random CCMAdministrator password) if upgrading from previous MLA (and Cisco CallManager) version that was enabled.
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