1. Cisco MGCP IP Phone Administrator Guide, Versions 6.x and 7.x
3. Installing Cisco MGCP IP Phones (Versions 6.x and 7.x)
Downloads: This chapterpdf (PDF - 327.0KB) The complete bookPDF (PDF - 881.0KB) | Feedback

Initializing Cisco MGCP IP Phones

Table Of Contents

Initializing Cisco MGCP IP Phones

Prerequisites

Overview of the Initialization Process

Information About Configuration Files

How to Customize the Default Configuration File

How to Customize a Phone-Specific Configuration File

How to Customize the Configuration from the Phone Menu

Unlocking and Locking the Phone

Setting and Restoring Network Parameters

Setting and Restoring Phone-Specific Parameters

Setting End-User Call Preferences

How to Set the Date and Time

Time-Zone Configuration Examples

How to Verify Initialization

Where to Go Next


Initializing Cisco MGCP IP Phones


This chapter describes the initial firmware installation tasks and configuration process for the Cisco IP 7960G/7940G phone in a Media Gateway Control Protocol (MGCP) network. It provides information on the following:

Prerequisites

Overview of the Initialization Process

Information About Configuration Files

How to Customize the Default Configuration File

How to Customize a Phone-Specific Configuration File

How to Customize the Configuration from the Phone Menu

How to Set the Date and Time

How to Verify Initialization

Where to Go Next

Prerequisites

Installation Strategy

Choose one of the following installation strategies:

Download, then customize. Download the firmware image and configuration files to your TFTP server. Connect each phone to power, causing it to automatically download the image and default files. Configure each phone individually as needed.

Customize, then download. Download the firmware image and configuration files to your TFTP server. Open the configuration files and customize parameters for all the phones at once. Save the customized file to the TFTP server. Connect each phone to power, causing it to automatically download the image and customized files.

Network Functionality

Ensure that your network meets the following requirements:

A working IP network is established and configured for MGCP.

For information on configuring IP, refer to the Cisco IOS IP Configuration Guide.
http://www.cisco.com/univercd/cc/td/doc/product/software/ios123/123cgcr/ip_vcg.htm

VoIP is configured on your Cisco routers.

For information on configuring VoIP, refer to the Cisco IOS Voice Configuration Library.
http://www.cisco.com/univercd/cc/td/doc/product/software/ios123/123cgcr/vcl.htm

A TFTP server is configured on your network.

When the phone initializes, it requests the following from the TFTP server:

Latest firmware image

Dual-boot file (OS79XX.TXT)

Phone-specific MAC-address configuration file

Default configuration file

Ring-list file

Dial-plan file

For the information about configuring your TFTP server, refer to your operating-system documentation.

A DHCP server is configured on your network.

The phone uses DHCP to obtain IP addresses. Configuration options are as follows:

dhcp option #1 (IP subnet mask)

dhcp option #3 (default IP gateway)

dhcp option #6 (DNS server IP address)

dhcp option #15 (domain name)

dhcp option #50 (IP address)

dhcp option #66 (TFTP server IP address)

If you do not configure DHCP options on the DHCP server, you must manually configure them on the phone. For information on configuring a DHCP server, refer to your operating-system documentation.

A proxy server is active and configured to receive and forward messages.


Note Refer to the Cisco 7940 and 7960 IP Phones Firmware Upgrade Matrix for additional prerequisites.


Overview of the Initialization Process

The initialization process for the Cisco MGCP IP phone establishes network connectivity and makes the phone operational in your MGCP network. After you connect your phone to the network and to a power supply, the phone begins initialization, during which the following occurs:

1. The phone loads the firmware image.

The phone has nonvolatile flash memory that contains permanent factory information about the phone and, eventually, firmware images and user-defined preferences. During initialization, the phone runs a bootstrap loader that loads the firmware image.

2. The phone learns its VLAN membership.

If the phone is connected to a Cisco Catalyst switch, the switch notifies the phone of the voice VLAN defined on the switch. The phone needs to know its VLAN membership before it can send a DHCP request for its IP settings (if using DHCP).

3. The phone acquires its IP address.

If the phone uses DHCP to obtain IP settings, it queries the DHCP server. Otherwise, it uses IP settings that are stored in flash memory.

4. The phone contacts the TFTP server and downloads the following files (or uses settings that are stored in its flash memory):

SEP<macaddress>.cnf.xml—Creates the filename SEP<macaddress>.cnf.xml on the TFTP server into which you can place one of the following:

<device>

<loadInformation>P0M3-07-3-00</loadInformation>

</device>

The phone then checks the load information and either upgrades the phone firmware in FLASH memory to the version stated in the <LoadInformation> tag using the TFTP loader in the Universal Application Loader, or, if the version matches, exits the Universal Application Loader and executes the firmware already loaded in FLASH memory.

<firmware-version>.loads—If the version matches, enables the phone to exit the Universal Application Loader and executes the firmware already loaded in FLASH memory, as defined in SEP<macaddress>.cnf.xml.

OS79XX.TXT—Enables the phone to initialize and automatically determine the network in which it is being installed.


Note The use of dual boot file OS79XX.TXT is deprecated in favor of individual XML configuration files for the phone using their SEP<macaddress>.cnf.xml style names. This allows Cisco CallManager and MGCP-based configurations to share a common TFTP server, as the XML configuration is phone-specific and allows indivbidual phones to be switched between SIP, SCCP, or MGCP images.


MGCPDefault.cnf—Contains parameters intended for all phones. For information on customizing the file, see the "How to Customize the Default Configuration File" section.

MGC<mac-addr>.cnf—Contains parameters specific to a phone. Use this file as a template from which to create a file for each phone. Insert the MAC address of the phone in the filename.

RINGLIST.DAT—Lists audio files that are the custom-ring-type options for the phones. The files must be in the root directory of the TFTP server.

dialplan.xml—Contains the North American sample dial plan. You can push the file down to the phones with a notify (NTFY) message with a check-sync Event header.


Note Refer to the Cisco 7940 and 7960 IP Phones Firmware Upgrade Matrix for additional information.


5. The phone verifies the firmware version.

If the phone determines that the image defined in a configuration file differs from the image that it has stored in flash memory, it performs a firmware upgrade. During upgrade, the phone downloads the firmware image from the TFTP server, programs the image into flash memory, and reboots.


Note Upon startup, the phone attempts to download both configuration files. If neither file exists, a TFTP timeout occurs after approximately 9 seconds per file. If the files exist, they are parsed and processed. These files are not required for the phone to initialize; however, it takes longer (approximately 20 seconds) for the phone to boot because it is waiting for the timeout on the TFTP server. Both configuration files can use the same values or they can contain empty values. If the files contain empty values, the phone boots using default values for some of the parameters.



Note Values in the phone-specific configuration file take precedence over those in the default configuration file because the phone-specific file is processed last.


Information About Configuration Files

Configuration files reside in a TFTP server subdirectory (you specify the location of this subdirectory with the tftp_cfg_dir parameter). For more information, refer to the Cisco 7940 and 7960 IP Phones Firmware Upgrade Matrix.


Note Be sure to customize configuration files before you power up the phone. When powered up, the phone automatically loads parameters stored in flash memory and then requests configuration files from the TFTP server.


When modifying parameters, remember the following:

Parameters in the configuration file override those stored in the phone's flash memory.

Locally changed parameters are used until the next reboot.

The name of each phone-specific configuration file is unique and is based on the MAC address of the phone.

The format of the filename must be MGCPXXXXYYYYZZZZ.cnf, where XXXXYYYYZZZZ is the MAC address of the phone. The MAC address must be in uppercase; the .cnf extension must be in lowercase (for example, MGCP00503EFFD842.cnf).


Note You can find the MAC address of a phone on the middle sticker adhered to the base of the phone. You can also view it on the Network Configuration menu.


Each line in a configuration file must use the following format and must adhere to the following rules:

variable-name : value ; optional comments

Associate only one value with one variable.

Separate variable names and values with colons.

Set only one variable per line.

Indicate the end of a line with <lf> or <cr><lf>.

Put the variable and value on the same line, and do not break the line.

You can include white space before or after a variable or value. You can include any character within them. However, if white spaces are needed within the value, you must enclose the value in single or double quotes. If the value is enclosed in quotes, the end quote must be the same as the start quote.

You can include comments after the value. Use the semicolon (;) and pound (#) delimiters to distinguish the comments.

You can include comment lines.

You can include blank lines.

You can use any case for variables; they are not case sensitive.

How to Customize the Default Configuration File

You have the following installation choices:

Download, then customize. Download the default configuration file to your TFTP server, and then plug each phone into power and the network. The phones automatically download the default configuration file from the TFTP server. You can then customize parameters if required.

Customize, then download. Download the default configuration file to your TFTP server, open the file, customize parameters for all the phones at once, save the customized file, and then plug the phones into power and the network. The phones automatically download the customized file from the TFTP server.

This section describes how to customize, then download. Maintaining parameters—such as whether phones must register with a proxy server and the codec that phones must use when initiating a call—in the default configuration file allows you to perform global changes, such as upgrading the image version, without having to customize the phone-specific configuration file for each phone.


Note For a complete alphabetical list of configurable parameters, see Appendix B, "Configurable Parameters for the MGCP IP Phone."


Prerequisites

If you have an existing system from a release earlier than Release 7.0, upgrade your system firmware as described in the "How to Upgrade Your Cisco MGCP IP Phone Firmware Image" section on page 4-3 before proceeding.

Procedure


Step 1 Obtain the default configuration file as follows:

a. Go to the Cisco.com MGCP IP 7940/7960 phone software-download site at http://www.cisco.com/cgi-bin/tablebuild.pl/mgcp-ip-phone7960.

b. Download the MGCPDefault.cnf file to the root directory of your TFTP server or to a subdirectory in which all phone-specific configuration files are stored.

Step 2 Using an ASCII text editor such as vi, open the file.

Step 3 Modify parameters as needed.

Step 4 Save the file to the root directory of your TFTP server or to a subdirectory in which all phone-specific configuration files are stored.


Configuration Example

The following is an example of the MGCPDefault configuration file that you downloaded from Cisco.com:

# MGCP Default Configuration File
#
# Any or All of these options can be configured
# in the user config file (MGCConfigGeneric.cnf).
# The user config file options override any options
# specified here in the Default Config File.
# :sample user config file name: MGC003E362FE92.cnf

# image_version - specifies which image version should
#    be on the phone. This is used to upgrade from one
#    MGCP image to a different MGCP image. The OS79XX.TXT
#    file is only used to switch protocols (ie. SIP to MGCP).
image_version: P0M3-06-0-00

# tftp_cfg_dir - specifies the directory to use for the
#    retrieving the MGCConfigGeneric.cnf file. The base
#    for the directory is the base TFTP Server directory.
#    tftp_cfg_dir is limited to 64 characters.
tftp_cfg_dir : ""

# phone_password - specifies the password used to Telnet
#    to the phone. phone_password is limited to 32 characters.
# phone_prompt - specifies the prompt the phone will display
#    when logged in from the console or Telnet session.
#    phone_prompt is limited to 16 characters.
phone_password : "cisco"
phone_prompt : "MGCP Phone"

# sntp_mode - specifies the mode the SNTP server uses
#     (unicast, multicast, anycast (default), directedbroadcast)
# sntp_server - specifies the address of the SNTP server
sntp_mode : anycast
sntp_server : "10.18.198.13"

# The following parameters setup time zone and
# daylight savings settings.
# Supported time zones are :
#   EST, AST, NST, BST, AT, WAT, GMT, HST, YST
time_zone               : EST
dst_offset              : 1
dst_start_month         : "April"
dst_start_day           : 0
dst_start_day_of_week   : "Sun"
dst_start_week_of_month : 1
dst_start_time          : 2
dst_stop_month          : "Oct"
dst_stop_day            : 0
dst_stop_day_of_week    : "Sun"
dst_stop_week_of_month  : 8
dst_stop_time           : 2
dst_auto_adjust         : 1

# Date and Time format displays
# time_format_24hr (1 - yes, 0 - 12 hours format)
# date_format (M/D/Y, D/M/Y, Y/M/D, Y/D/M)
time_format_24hr : 1
date_format : M/D/Y

# MGCP Call Agent Information
# mgcp_gw_controller - address of call agent
# mgcp_input_port - port the phone listens on
# mgcp_output_port - port the call agent listens on
mgcp_gw_controller : 10.18.198.13
mgcp_input_port : 2427
mgcp_output_port : 2727

# mgcp_keepalive - specifies if the RSIP keepalive should
#   be used to keep NAT bindings open to the Call Agent.
#   values are [0 - off (default), 1 - on]
# mgcp_keepalive_timer - specifies the time interval to
#   use for the mgcp keepalive timer if turned on.
#   values are in seconds [10 to 600, 30 is default].
mgcp_keepalive: 0
mgcp_keepalive_timer: 30

# xml_card_dir - specifies the directory to use for the
#    retrieving the xml cards file. The base
#    for the directory is the base TFTP Server directory.
#    xml_card_dir is limited to 64 characters.
# xml_card_file - specifies the file name of the XML Cards
#    file. xml_card_file is limited to 20 characters.
xml_card_dir : ""
xml_card_file : "CARD.XML"

# tos_media - specifies the value to be used for the tos bits.
#    valid range is 0-7.
tos_media: 7

#use_mac_name - specifies whether to use the IP address
#     or MAC Address in the endpoint name. The default is
#     to use the IP address. Valid values are :
#          [ 0 - IP Address (default) 1 - Mac Address ]
use_mac_name: 0

#telnet_level - enables the ability to Telnet into phone
#	and specify the level of access.  The default is
#	disabled.  Valid values are:
#	[ 0-disabled (default), 1-enabled, 2-privileged ]
telnet_level: 0

#logo_url - used to put a specific windows 256-color bmp
#     file as the background image. The image must be a
#     windows 256 color bitmap. The space allotted for the image
#     is 56 pixels height x 90 pixels wide. If the image is
#     bigger, then it will be sized to fit into
#     the space allotted.
logo_url: http://10.10.10.4/projects/phone/logo.bmp

#services_url - used to allow the user to access external
#     XML applications that reside on a server.
services_url: "http://10.10.10.4/CiscoServices/Services.asp"

# End of Generic MGCP Default Config File.

How to Customize a Phone-Specific Configuration File

You can define parameters that are specific to a particular phone, such as the lines configured on a phone and the defined users for those lines, in a phone-specific configuration file.


NoteIf you configure a line to use an e-mail address, that line can be called only by using the e-mail address. Similarly, if you configure a line to use a number, that line can be called only by using the number. Each line can have a different proxy configured.

Define the dial_template parameter in the default configuration file for maintenance and control purposes. Define the parameter in a phone-specific configuration file only if that phone needs to use a different dial plan than the one being used by the other phones in the same system.

For a complete alphabetical list of configurable parameters, see Appendix B, "Configurable Parameters for the MGCP IP Phone."


Procedure


Step 1 Obtain the phone-specific configuration file as follows:

a. Go to the Cisco.com MGCP IP 7940/7960 phone software-download site at http://www.cisco.com/cgi-bin/tablebuild.pl/mgcp-ip-phone7960.

b. Download the MGCP<mac-addr>.cnf file to the root directory of your TFTP server or to a subdirectory in which all phone-specific configuration files are stored.

Step 2 Do the following for each phone that you plan to install:

a. Using an ASCII editor, create and open an MGCP<mac-addr>.cnf file for the phone.

b. Modify parameters as needed.

c. Save the file to the root directory of your TFTP server or to a subdirectory that contains all the phone-specific configuration files. Name the file MGCP<mac-addr>.cnf. The MAC address must be in uppercase and the extension, cnf, must be in lowercase (for example, MGCP00503EFFD842.cnf).


Configuration Example

The following is an example of the phone-specific configuration file that you downloaded from Cisco.com:

# Generic Phone Specific Config File Options
#
The user config file options override any options specified in the Default Config File.
# :sample user config file name: MGC003E362FE92.cnf

# image_version - specifies which image version should
#    be on the phone. This is used to upgrade from an
#    MGCP image to a different MGCP image. The OS79XX.TXT
#    file is only used to switch protocols (ie. SIP to MGCP).
image_version: P0M3-06-0-00

# tftp_cfg_dir - specifies the directory to use for the
#    retrieving the MGC<MAC ADDR>.cnf file. The base
#    for the directory is the base TFTP Server directory.
#    tftp_cfg_dir is limited to 64 characters.
tftp_cfg_dir : ""

# phone_password - specifies the password used to Telnet
#    to the phone. phone_password is limited to 32 characters.
# phone_prompt - specifies the prompt the phone will display
#    when logged in from the console or Telnet session.
#    phone_prompt is limited to 16 characters.
phone_password : "cisco"
phone_prompt : "MGCP Phone"

# sntp_mode - specifies the mode the SNTP server uses
#     (unicast, multicast, anycast (default), directedbroadcast)
# sntp_server - specifies the address of the SNTP server
sntp_mode : anycast
sntp_server : "172.18.198.13"

# The following parameters setup time zone and
# daylight savings settings.
# Supported time zones are :
#   EST, AST, NST, BST, AT, WAT, GMT, HST, YST
time_zone               : EST
dst_offset              : 1
dst_start_month         : "April"
dst_start_day           : 0
dst_start_day_of_week   : "Sun"
dst_start_week_of_month : 1
dst_start_time          : 2
dst_stop_month          : "Oct"
dst_stop_day            : 0
dst_stop_day_of_week    : "Sun"
dst_stop_week_of_month  : 8
dst_stop_time           : 2
dst_auto_adjust         : 1

# Date and Time format displays
# time_format_24hr (1 - yes, 0 - 12 hours format)
# date_format (M/D/Y, D/M/Y, Y/M/D, Y/D/M)
time_format_24hr : 1
date_format : M/D/Y

# MGCP Call Agent Information
# mgcp_gw_controller - address of call agent
# mgcp_input_port - port the phone listens on
# mgcp_output_port - port the call agent listens on
mgcp_gw_controller : 172.18.198.13
mgcp_input_port : 2427
mgcp_output_port : 2727

# mgcp_keepalive - specifies if the RSIP keepalive should
#   be used to keep NAT bindings open to the Call Agent.
#   values are [0 - off (default), 1 - on]
# mgcp_keepalive_timer - specifies the time interval to
#   use for the mgcp keepalive timer if turned on.
#   values are in seconds [10 to 600, 30 is default].
mgcp_keepalive: 0
mgcp_keepalive_timer: 30

# xml_card_dir - specifies the directory to use for the
#    retrieving the xml cards file. The base
#    for the directory is the base TFTP Server directory.
#    xml_card_dir is limited to 64 characters.
# xml_card_file - specifies the file name of the XML Cards
#    file. xml_card_file is limited to 20 characters.
xml_card_dir : ""
xml_card_file : "CARD.XML"

# tos_media - specifies the value to be used for the tos bits.
#    valid range is 0-7.
tos_media: 7

#use_mac_name - specifies whether to use the IP address
#     or MAC Address in the endpoint name. The default is
#     to use the IP address. Valid values are :
#          [ 0 - IP Address (default) 1 - Mac Address ]
use_mac_name: 0

#telnet_level - enables the ability to Telnet into phone
#       and specify the level of access.  The default is
#       disabled.  Valid values are:
#       [ 0-disabled (default), 1-enabled, 2-privileged ]
telnet_level: 0

# End of Generic Phone Specific Config File.

How to Customize the Configuration from the Phone Menu

After the phone has been connected to power and initialized and the configuration files have been downloaded, you can modify your configuration using the phone menu.

This section contains the following procedures:

Unlocking and Locking the Phone

Setting and Restoring Network Parameters

Setting and Restoring Phone-Specific Parameters

Setting End-User Call Preferences


TipTo select a parameter, press the down arrow to scroll to and highlight the parameter, or press the number that represents the parameter (located to the left of the parameter on the LCD).

During configuration, use * for dots (periods) or press the "." soft key when available on the LCD.

During configuration:

To enter a number, press the Number soft key. To enter a name, press the Alpha soft key.

To enter a new value, use the buttons on the dial pad.

If entering letters, use the numbers on the dial pad that are associated with a particular letter. For example, the 2 key has the letters A, B, and C. For a lowercase a, press the 2 key once. To scroll through the available letters and numbers, press the key repeatedly.

To delete any mistakes, press the << soft key.

To cancel all changes and exit a menu during configuration, press Cancel.

After editing a parameter, press the Validate soft key to save the value that you have entered and exit the Edit panel.


Modifying your configuration using the phone menus requires that you unlock and relock the phone. A padlock icon in the upper-right corner of your LCD displays on the phone when the phone is locked. By default, the phone is locked.


Note If the Network Configuration or MGCP Configuration menu is displayed, the lock icon in the upper-right corner of your LCD changes to an unlocked state. If you are located elsewhere in the Cisco IP 7960G/7940G phone menus, the next time you access the Network Configuration or MGCP Configuration menus, the unlocked icon displays, and you can modify the network and MGCP configuration settings.


Unlocking and Locking the Phone

You must unlock and relock the phone to modify a configuration using the phone menus. Similarly, phone users must unlock and relock the phone to modify end-user parameters.

A padlock icon in the upper-right corner of your LCD displays on the phone when the phone is locked. By default, the phone is locked.

Prerequisites

Set the phone password with the phone_password parameter in the phone-specific configuration file.

Procedure


Step 1 To unlock the phone, do the following:

a. Press Settings > Unlock Config. The password prompt displays.

b. Enter a phone password. The phone unlocks, and the unlock icon displays on the LCD.


Note The Unlock Config menu choice changes to Lock Config and the configuration remains unlocked while you work within it. When you exit the configuration menu, the configuration automatically relocks.


Step 2 To relock the phone, select Lock Config or Exit.


Setting and Restoring Network Parameters

You can modify network parameters using the phone menus.


NoteTFTPServer may be a required parameter, depending on how you intend for the phone to locate the TFTP server from which it downloads its configuration file. You can provide the TFTP server IP address in either of two ways:

Provide it to the DHCP server. (For information, see the "Prerequisites" section.) Using normal Cisco Discovery Protocol (CDP) processes, the phone locates the DHCP server upon connection to the network; the server in turn provides the TFTP server address.

Provide it directly to the phone by means of the TFTPServer parameter as described in this procedure. If you use this method, first select DHCP Enabled > No.

For a complete alphabetical list of configurable parameters, see Appendix B, "Configurable Parameters for the MGCP IP Phone."


Procedure


Step 1 Unlock the phone (see the "Unlocking and Locking the Phone" section).

Step 2 Select Settings > Network Configuration. The Network Configuration menu displays.

Step 3 To set a parameter, select it and set it as desired.

Step 4 To restore all parameters to their defaults, select Erase Config > Yes.


Note If DHCP is disabled on a phone, restoring default phone settings reenables DHCP.


Step 5 Select Save. The phone programs the new information into flash memory and resets.

Step 6 Relock the phone.


Setting and Restoring Phone-Specific Parameters

Phone users can modify the phone-specific configuration settings using the phone menus.


NoteParameters defined in the default configuration file override those specified in the phone-specific configuration file.

If a phone-specific configuration file exists, the phone uses parameters entered locally until the next reboot.

If you do not configure the phone using a TFTP server, you must configure the phone locally.

To configure the preferred codec and out-of-band DTMF parameters, press Change until the option displays and then press Save.

If your system has been set up to have the phones retrieve the configuration file from a TFTP server, you must use the server's configuration file to change the parameter value to a null value " " or to "UNPROVISIONED." The phone uses the setting for that variable that it has stored in flash memory.

If the telnet_level parameter is set to allow privileged commands to be executed, the entire MGCP configuration can be erased. Use the erase_protflash command so that the phone can retrieve its configuration files.


Prerequisites

Define the line parameters (those identified as linex) on the phone. If you configure a line to use an e-mail address, that line can be called only by using an e-mail address. Similarly, if you configure a line to use a number, that line can be called only by using the number.

Procedure


Step 1 Unlock the phone (see the "Unlocking and Locking the Phone" section).

Step 2 Select Settings > MGCP Configuration. The MGCP Configuration menu displays.

Step 3 To set a required parameter, select it and set it as desired. The following are required parameters that you must set now if you did not set them in the default configuration file as described in the "How to Customize the Default Configuration File" section:

CA IP address

Phone input port

Phone output port

Step 4 To set an additional parameter, select it and set it as desired.

Step 5 To restore a parameter to its default, do the following:

a. One at a time, highlight the parameter whose setting you want to erase, and then select Edit followed by <<.

b. Select Validate > Exit.

c. If necessary, select Back to exit the menu.

Step 6 Select Save. The phone programs the new information into flash memory and resets.

Step 7 Relock the phone.


Setting End-User Call Preferences

End users can modify call preferences from their own phones, according to how you set the associated parameters.

Prerequisites

Set configuration variables for call preferences as follows (see the "How to Customize a Phone-Specific Configuration File" section):

To enable end users to modify a preference, set to 0 or 1.

To prohibit end users from modifying a preference, set to 2 or 3.

Procedure


Step 1 Unlock the phone (see the "Unlocking and Locking the Phone" section).

Step 2 On the IP phone, select Settings > Call Preferences.

Step 3 Set any of the preferences to the desired setting.

Step 4 Select Save. The phone programs the new information into flash memory and resets.

Step 5 Relock the phone.


How to Set the Date and Time

You can set date, time, and daylight savings time (DST) parameters. The current date and time is supported on the Cisco IP 7960G/7940G phone using Simple Network Time Protocol (SNTP) and is displayed on the LCD. DST and time-zone settings are also supported.

International time-zone abbreviations are supported and must be in all capital letters.


Note We recommend that you set date- and time-related parameters in the default file for all phones. Alternatively, you can set the time-zone parameter manually on the phone or in the phone-specific configuration files.


Prerequisites

Determine the type of DST that you want to configure:

Absolute DST (for example, starts on April 1 and ends on October 1)

Relative DST (for example, starts on the first Sunday in April and ends on the last Sunday of October)

Review the list of common and absolute DST parameters from Appendix B, "Configurable Parameters for the MGCP IP Phone."

Review the information on SNTP in Table 3-1. SNTP parameters specify how the phone obtains the current time from an SNTP server.

Determine your time zone from Table 3-2.

Procedure


Step 1 Using an ASCII text editor such as vi, open the MGCPDefault.cnf file.

Step 2 Modify the following SNTP parameters as needed:

sntp_mode

sntp_server

time_zone

Step 3 Modify the following common DST parameters as needed:

dst_offset

dst_auto_adjust

dst_start_month

dst_stop_month

dst_start_time

dst_stop_time

Step 4 Do one of the following:

Modify the following absolute DST parameters as needed:

dst_start_day

dst_stop_day

Modify the following relative DST parameters as needed:

dst_start_day_of_week

dst_start_week_of_month

dst_stop_day_of_week

dst_stop_week_of_month

Step 5 Save the file to the root directory of your TFTP server.


Note To adjust the phone display to European Day-Month-Year format, add the following entry to the MGCPDefault.cnf file: date_format:D/M/Y.



Table 3-1 describes the effects on SNTP mode when the SNTP server is null (not assigned an IP address) or when it is assigned a valid IP address.

Table 3-1 Effects on the SNTP Mode 

SNTP Server
SNTP Mode
Unicast
Multicast
Any Cast 1
Directed Broadcast
SNTP server parameter is null.

Sends

No known server with which to communicate.

SNTP requests are not sent.

SNTP packet to the local network broadcast address.

After the first SNTP response is received, the phone switches to unicast mode with the server being set as the one who first responded.

SNTP packet to the local network broadcast address.

After the first SNTP response is received, the phone switches to multicast mode.

Receives

No known server with which to communicate.

Multicast data using the SNTP/NTP multicast address from the local network broadcast address from any server on the network.

Unicast SNTP data from the SNTP server that first responded to the network broadcast request.

SNTP data from the SNTP/NTP multicast address and the local network broadcast address from any server on the network.

SNTP server parameter is a valid IP address.

Sends

SNTP request to the SNTP server.

SNTP requests are not sent.

If the mode is anycast and the SNTP server parameter is a valid IP address, the phone sends the request to the broadcast address in version 7.4.

SNTP packet to the SNTP server.

After the first SNTP response is received, the phone switches to multicast mode.

Receives

SNTP response from the SNTP server and ignores responses from other SNTP servers.

SNTP data via the SNTP/NTP multicast address from the local network broadcast address.

SNTP response from the SNTP server and ignores responses from other SNTP servers.

SNTP data from the SNTP/NTP multicast address and the local network broadcast address and ignores responses from other SNTP servers.

1 If sntp_mode is set to anycast, the sntp_server address will be ignored and subsequent sntp requests will be sent to the first

1 sntp server that responded (the first sntp request must be unconditionally sent to the broadcast address) .


Table 3-2 includes the time-zone information that you need to configure SNTP mode and server parameters.

Table 3-2 Time-Zone Information 

Abbreviation
GMT Offset
Cities
Time-Zone Names

IDL

GMT-12:00

Eniwetok

IDL (International Date Line),
IDLW (International Date Line West)

NT

GMT-11:00

Midway

BT (Bering Time), NT (Nome Time)

AHST

GMT-10:00

Hawaii

AHST (Alaska-Hawaii Standard Time),
HST (Hawaiian Standard Time),
CAT (Central Alaska Time)

IMT

GMT-09:30

Isle Marquises

Isle Marquises

YST

GMT-09:00

Yukon

YST (Yukon Standard Time)

PST

GMT-08:00

Los Angeles

PST (Pacific Standard Time)

MST

GMT-07:00

Phoenix

MST (Mountain Standard Time),
PDT (Pacific Daylight Time)

CST

GMT-06:00

Dallas, Mexico City

CST (Central Standard Time),
MDT (Mountain Daylight Time),
Chicago

EST

GMT-05:00

New York

EST (Eastern Standard Time),
CDT (Central Daylight Time),
NYC

AST

GMT-04:00

La Paz

AST (Atlantic Standard Time),
EDT (Eastern Daylight Time)

NST

GMT-03:30

Newfoundland

NST (Newfoundland Standard Time)

BST

GMT-03:00

Buenos Aires

BST (Brazil Standard Time),
ADT (Atlantic Daylight Time),
GST (Greenland Standard Time)

AT

GMT-02:00

Mid-Atlantic

AT (Azores Time)

WAT

GMT-01:00

Azores

WAT (West Africa Time)

GMT

GMT 00:00

London

GMT (Greenwich Mean Time),
WET (Western European Time),
UT (Universal Time)

CET

GMT+01:00

Paris

CET (Central European Time),
MET (Middle European Time),
BST (British Summer Time),
MEWT (Middle European Winter Time),
SWT (Swedish Winter Time),
FWT (French Winter Time)

EET

GMT+02:00

Athens, Rome

EET (Eastern European Time),
USSR-zone1,
MEST (Middle European Summer Time),
FST (French Summer Time)

BT

GMT+03:00

Baghdad, Moscow

BT (Baghdad Time),
USSR-zone2

IT

GMT+03:30

Tehran

IT (Iran Time)

ZP4

GMT+04:00

Abu Dhabi

USSR-zone3,
ZP4 (GMT Plus 4 Hours)

AFG

GMT+04:30

Kabul

Afghanistan

ZP5

GMT+05:00

Islamabad

USSR-zone4,
ZP5 (GMT Plus 5 Hours)

IST

GMT+05:30

Bombay, Delhi

IST (Indian Standard Time)

ZP6

GMT+06:00

Colombo

USSR-zone5,
ZP6 (GMT Plus 6 Hours)

SUM

GMT+06:30

North Sumatra

NST (North Sumatra Time)

WAST

GMT+07:00

Bangkok, Hanoi

SST (South Sumatra Time),
USSR-zone6,
WAST (West Australian Standard Time)

HST

GMT+08:00

Beijing, Hong Kong

CCT (China Coast Time),
HST (Hong Kong Standard Time), USSR-zone7,
WADT (West Australian Daylight Time)

JST

GMT+09:00

Tokyo, Seoul

JST (Japan Standard Time/Tokyo),
KST (Korean Standard Time), USSR-zone8

CAST

GMT+09:30

Darwin

SAST (South Australian Standard Time), CAST (Central Australian Standard Time)

EAST

GMT+10:00

Brisbane, Guam

GST (Guam Standard Time), USSR-zone9, EAST (East Australian Standard Time)

EADT

GMT+11:00

Solomon Islands

USSR-zone10,
EADT (East Australian Daylight Time)

NZST

GMT+12:00

Auckland

NZT (New Zealand Time/Auckland),
NZST (New Zealand Standard Time),
IDLE (International Date Line East)


Time-Zone Configuration Examples

Absolute DST Configuration

The following is an example of an absolute DST configuration:

time_zone : PST
dst_offset : 01/00
dst_start_month : April
dst_start_day : 1
dst_start_time : 02/00
dst_stop_month : October
dst_stop_day : 1
dst_stop_time : 02/00
dst_stop_autoadjust : 1

Relative DST Configuration

The following is an example of a relative DST configuration:

time_zone : PST
dst_offset : 01/00
dst_start_month : April
dst_start_day : 0
dst_start_day_of_week : Sunday
dst_start_week_of_month : 1
dst_start_time : 02/00
dst_stop_month : October
dst_stop_day : 0
dst_stop_day_of_week : Sunday
dst_stop_week_of_month : 8
dst_stop_time : 02/00
dst_stop_autoadjust : 1

How to Verify Initialization

The initialization process establishes network connectivity and makes the phone operational in your IP network.

Procedure


Step 1 After the phone has power connected to it, ensure that the phone cycles through the following steps.The following flash on and off in sequence: Headset button, Mute button, and Speaker button.

Step 2 The Cisco Systems, Inc. copyright appears on the LCD.

Step 3 The following messages appear:

Configuring VLAN—The phone configures the Ethernet connection.

Configuring IP—The phone contacts the DHCP server to obtain network parameters and the IP address of the TFTP server.

Requesting Configuration—The phone contacts the TFTP server to request its configuration files and compares firmware images.

Upgrading Software—The phone displays this message only if it determines that an image upgrade is required. After upgrading the image, the phone automatically reboots to run the new image.

Step 4 The main LCD displays the following:

Primary directory number

Soft keys

If the phone successfully cycles through these steps, it has started up properly.


Where to Go Next

See Chapter 4, "Managing Cisco MGCP IP Phones," for information on upgrading firmware and performing other management tasks.

See Chapter 5, "Monitoring Cisco MGCP IP Phones," for information on debugging and on viewing network statistics.