Configuring CM Express to Support Endpoints Best CCNA Training Institute in Delhi Gurgaon

Network Bulls
www.networkbulls.com
Best Institute for CCNA CCNP CCSP CCIP CCIE Training in India
M-44, Old Dlf, Sector-14 Gurgaon, Haryana, India
Call: +91-9654672192


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. The following is a
sample command set:
load 7960-7940 P00303020214
load 7920 cmterm_7920.4.0-01-08
load 7941 TERM41.7-0-3-0S
© 2008 Cisco Systems Inc. All rights reserved. This publication is protected by copyright. Please see page 147 for more details.
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.
Create XML Config Files
The create cnf-files command takes the configurations (including the firmware load, the source IP address, and port we
just defined) and builds an XML config file for each phone. This is a necessary step, and one that you may repeat from
time to time, for example, if you upgrade firmware or make other changes to the phone configuration.
DID Configurations
It is common to have a range of DID numbers (fully qualified E.164 numbers) that allow outside callers to reach internal
extensions directly; usually, the DIDs have the four-digit internal extension as the last four digits. CM Express supports
this configuration with the dialplan-pattern command. This function expands extension numbers to full E.164 numbers
and converts incoming E.164 numbers to local extensions. The command is also needed to register the range of numbers
the command specifies with a gatekeeper; in fact, once configured, the range is automatically registered if a gatekeeper
is configured. You can disable this with the no-reg keyword. The full syntax is dialplan-pattern tag pattern
Automated Deployment of Endpoints
In some cases, it is desirable to automate the deployment of phones. The telephony-service auto-assign command will
dynamically create ephones as physical phones are connected to the system, assigning an available ephone-dn to the
ephone. The ephone-dns must all be the same type (that is, single line or dual line). You must have a range of ephone-dns
configured, but it is no longer necessary to create each ephone and associate it manually.
The auto assign start-dn to stop-dn [type phone-type] [cfw number timeout seconds] command syntax specifies the
range of ephone-dns to use for a given phone model, the Call Forward Busy number to use (typically the voice-mail port),
and timeout values. You can enter multiple commands to specify ranges for your different phone types; if no phone type
is specified, any phone that registers will be assigned an ephone-dn from the specified range. The 7914 sidecar is not
supported by this command; phones with this add-on must have it manually added. The auto-assign cannot be used for
ephone-dns that serve paging, MoH, intercom or MWI functions. Nor can it be used for shared-line implementations.
Changes must be performed manually at the CLI, followed by resetting the affected phones. The following is a sample of
how the command can be used:
t e l e p h o n y - s e r v i ce
auto assign 11 to 20 type 7920
auto assign 21 to 30 type 7940
auto assign 31 to 40 type 7960
auto assign 41 to 50
ephone-dn 1 d u a l - l i ne
number 5301
© 2008 Cisco Systems Inc. All rights reserved. This publication is protected by copyright. Please see page 147 for more details.
extension-length length extension-pattern pattern [no-reg]. The pattern uses the same wildcards as dial peers. A
sample configuration to set up a dial plan pattern for extensions 5300-5399 and expand them to the DID range of
867-555-5300-867-555-5399 would look like this:
t e l e p h o n y - s e r v i ce
d i a l p l a n - p a t t e r n 1 86755553.. e x t e n s i o n - l e n g t h 4 extension p a t t e r n 5 3 ..
© 2008 Cisco Systems Inc. All rights reserved. This publication is protected by copyright. Please see page 147 for more details.
The preceding output assigns ephone-dns from 11 to 20 to 7920s, 21 to 30 to 7940s, 31 to 40 to 7960s, and 41 to 50 to
any other type of phone (including those already specified, if there are no more ephone-dns in their range).
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
© 2008 Cisco Systems Inc. All rights reserved. This publication is protected by copyright. Please see page 147 for more details.
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}.
© 2008 Cisco Systems Inc. All rights reserved. This publication is protected by copyright. Please see page 147 for more details.
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:
• 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.
© 2008 Cisco Systems Inc. All rights reserved. This publication is protected by copyright. Please see page 147 for more details.
• 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.