Monday, March 15, 2010

Configuring CM Express to Support Endpoints

In this section we explore three methods of configuring endpoints on a CM Express system: configuring optional settings, rebooting IP Phones, and troubleshooting and verifying the configuration.


Providing Firmware

IP Phone firmware files ship with the CM Express software or can be downloaded from cisco.com. For the router to serve the firmware to the phones, the tftp-server fiashifilename command is used. You must enter this command for every firmware file needed. Some phones require more than one file to be loaded—for example, the 791 IG requires six separate files.

Telephony Service Configuration

Manual setup of the CM Express system is done using the CLI. From the global config, the command telephony-service enables config-telephony mode. This prompt is where your first steps of defining the max-ephones and max-ephone-dn settings (described earlier) would take place.

Phone Firmware Loads

The firmware files that were copied into Flash and made available to the phones via TFTP must be associated with the phones; this is done using the load model firmware-file command. Filenames are case sensitive, and the file extension should not be included in the command. (Tip: Use the Cut-and-Paste function of your terminal client to prevent annoying typos!) For Java-based phones, it is only necessary to load the TERMnn.x-y-x-w.loads or SCCPnn.x-y-x-w.loads firmware filename (without the .loads extension), although the other files must be available via TFTP.

Defining Source IP and Port

The CM Express software uses SCCP to communicate with the phones. (SIP signaling is also possible but is not covered in this document.) The command ip source-address ip-address [port port] defines the IP address of the router that will be used as the source for SCCP messages. The default SCCP TCP port is 2000 and does not normally need to be changed, but the option is available if the situation should require it.

Autoregistration

The autoregistration function is enabled by default; this allows a phone to be discovered and registered to an available ephone slot (provided the ip source-address command is configured). The command no auto-reg-ephone prevents a phone from registering unless its MAC address is explicitly configured already. CM Express records the MACs of all phones that attempt to register but are blocked by autoregistration being disabled; use the show ephone
attempted-registrations command to see the list and the clear telephony-service ephone attempted-registrations command to see and clear the list.


Location Customization

CM Express supports phone display language, time display, and ring cadence localization. The user-locale languagecode command will change the language displayed on all 7940 and 7960 phones; the 7920 is not affected and must be configured with its individual language capability local to the phone. The network-locale language-code command will change the call progress tones and ring cadence (again with the exception of the 7920).

Following are language codes supported for User Locale:
  • DE: Germany
  • DK: Denmark
  • ES: Spain
  • FR: France
  • IT: Italy
  • NL: Netherlands
  • NO: Norway
  • PT: Portugal
  • RU: Russian Federation
  • SE: Sweden
  • US: United States (default)
  • JA:Japan
Following are language codes supported for Network Locale:
  • AT: Austria
  • CA: Canada
  • CH: Switzerland
  • DE: Germany
  • DK: Denmark
  • ES: Spain
  • FR: France
  • GB: United Kingdom
  • IT: Italy
  • JA: Japan
  • NL: Netherlands
  • NO: Norway
  • PT: Portugal
  • RU: Russian Federation
  • SE: Sweden
  • US: United States (default)
To change the time display format, use the time-format {12 I 24} command. To change the date format, use date-format {mm-dd-yy I dd-mm-yy I yy-dd-mm I yy-mm-dd}.


To change the time display format, use the time-format {12 I 24} command. To change the date format, use date-format {mm-dd-yy I dd-mm-yy I yy-dd-mm I yy-mm-dd}.


Rebooting IP Phones

There are two commands available to reboot IP Phones, each with a slightly different behavior. The reset command causes a hard reboot of the phone and invokes DHCP and TFTP. Use reset when changing firmware, user/network locales, or URLs. The reset command can be executed to reset a single phone at the config-ephone prompt, or at the config-telephony prompt to reset one or more phones. The full syntax is reset {all [time-interval] I cancel I mac-address Isequence-all}. The command options work as follows:

There are two commands available to reboot IP Phones, each with a slightly different behavior. The reset command causes a hard reboot of the phone and invokes DHCP and TFTP. Use reset when changing firmware, user/network locales, or URLs. The reset command can be executed to reset a single phone at the config-ephone prompt, or at the config-telephony prompt to reset one or more phones. The full syntax is reset {all [time-interval] I cancel I mac-address Isequence-all}. The command options work as follows:

  • all: Resets all phones.
  • time-interval: Changes the interval between the router resetting the phones in sequence (default = 15sec).
  • cancel: Stops the reset process.
  • mac-address: Resets a specific phone.
  • sequence-all: The router waits for one phone to reset and reregister before resetting the next phone to prevent the phones from overloading the TFTP server. This can be time consuming; the router waits 4 minutes as a timeout before resetting the next phone, whether or not the reregistration of the previous has finished.

The restart command causes a soft (warm) reboot and is useful for minor configuration changes, such as buttons, lines, and speed-dial modifications. This command can also be executed either at the config-ephone prompt or at the configtelephony prompt. The syntax is restart {all [time-interval] I mac-address}, with the command parameters the same as
the reset command.


Troubleshooting Endpoints

Check the following when troubleshooting:
  • Verify IP addressing: Use the Settings button on the phone to check the configuration of the IP phone. The TFTP Server IP should be the CM Express router.
  • Verify the files in flash memory: Verify that the correct firmware files are in the flash memory of the Cisco Unified Communications Manager Express router using the show flash command.
  • Debug the TFTP server: Use debug tftp events to ensure that the Cisco Unified Communications Manager Express router is correctly providing the firmware and XML files.
  • Verify the firmware installation of the phones: Use the debug ephone register command to verify which firmware is being installed.
  • Verify that the locale is correct: Use the show telephony-service tftp-bindings command to view the files that the TFTP server is providing.
  • Verify the phone setup: Use the show ephone command to view the status of the ephones and whether they are registered correctly.
  • Review the configuration: Use the show running-config command to verify the ephone-dn configuration.