Call Manager Basic Configuration Wael K. Valencia Community College
CallManager Server VS Win 2K Server
Starting Services on CM
Configuring DHCP on Call Manager Configuring Options
Adding a Server Win 2K address instead of NetBIOS name
Configuring Local Directory Number Information (LDN)
Confirming EPhones Auto-Registration
If the IP phones did not register on time then the CallManager Service will need to be stopped and restarted To do this follow the following steps: –From the “start” Menu choose “programs” “Administrative Tools” “Services” “Cisco CallManager” Test functionality by making calls between extensions.
Reset OR Restart ?
Erasing EPhone Configuration This can also be done individually from your IP phone. Press the “settings” button Network Configurations (#3) Press “Erase configuration” (#33) Notice that the default for option 33 is “No” also notice at the top of your EPhone LCD that the “Network Configuration is locked”. To Unlock it press **#, then select Yes to erase the phone config.
IP Phone boot-up service 1.Obtain Voice VLAN info. 2.Request DHCP information. The DHCP Server sends the IP address of the TFTP server to the IP phone. 3.The IP phone then contacts the TFTP server to get a configuration file. The configuration file specifies the list of CallManagers to which the IP phone should attempt to register. 4.The IP phone then attempts to register the primary CM. If connection failed, the IP phone will try the subsequent servers from the list that was provided by the TFTP server.
Database Clustering The database is a Microsoft SQL Server If the database resides on a single machine, phone network would be vulnerable to a machine outage. Each CallManger cluster consists of a set of networked databases: –Publisher: Provides read and write access for database administrators and CallManager nodes themselves. –Subscriber: Read-Only. CallManger nodes access the subscriber databases only in cases when the Publisher is not available
Verifying SQL Database Information
Indicates a Publisher