cc/td/doc/product/voice/srst/srst40
hometocprevnextglossaryfeedbacksearchhelp
PDF

Table Of Contents

Setting Up Cisco Unified IP Phones

Contents

Information About Setting Up Cisco Unified IP Phones

How to Set Up Cisco Unified IP Phones

Configuring IP Phone Clock, Date, and Time Formats

Configuring IP Phone Language Display

Configuring Customized System Messages for Cisco Unified IP Phones

Configuring a Secondary Dial Tone

Configuring Dual-Line Phones

How to Set Up Cisco IP Communicator for Cisco Unified SRST

Verifying Cisco IP Communicator

Troubleshooting Cisco IP Communicator

Where to Go Next


Setting Up Cisco Unified IP Phones


This chapter describes how to set up the displays and features that callers will see and use on Cisco Unified IP Phones during Cisco Unified CallManager fallback.


Note Prior to Cisco Unified Survivable Remote Site Telephony (SRST) 4.0, the name of this product was Cisco SRST.



Note The Cisco IOS Voice Configuration Library includes a standard library preface, glossary, and feature and troubleshooting documents and is located at http://www.cisco.com/en/US/products/ps6441/prod_configuration_guide09186a0080565f8a.html.


Contents

Information About Setting Up Cisco Unified IP Phones

How to Set Up Cisco Unified IP Phones

How to Set Up Cisco IP Communicator for Cisco Unified SRST

Where to Go Next

Information About Setting Up Cisco Unified IP Phones

Cisco Unified IP Phone configuration is limited for Cisco Unified SRST because IP phones retain nearly all Cisco Unified CallManager settings during Cisco Unified CallManager fallback. You can configure the date format, time format, language, and system messages that appear on Cisco Unified IP Phones during Cisco Unified CallManager fallback. All four of these settings have defaults, and the available language options depend on the IP phones and Cisco Unified CallManager version in use. Also available for configuration is a secondary dial tone, which can be generated when a phone user dials a predefined PSTN access prefix and can be terminated when additional digits are dialed. Dual-line phone configuration is required for dual-line phone operation during Cisco Unified CallManager fallback.

How to Set Up Cisco Unified IP Phones

This section contains the following tasks:

Configuring IP Phone Clock, Date, and Time Formats (Optional)

Configuring IP Phone Language Display (Optional)

Configuring Customized System Messages for Cisco Unified IP Phones (Optional)

Configuring a Secondary Dial Tone (Optional)

Configuring Dual-Line Phones (Required Under Certain Conditions)

Configuring IP Phone Clock, Date, and Time Formats

The Cisco Unified IP Phone 7970G and Cisco Unified IP Phone 7971G-GE IP phones obtain the correct timezone from Cisco Unified CallManager. They also receive the Coordinated Universal Time (UTC) time from the SRST router during SRST registration. When in SRST mode, the phones take the timezone and the UTC time, and apply a timezone offset to produce the correct time display.

Cisco IP Phone 7960 IP phones and other similar SCCP phones such as the Cisco IP Phone7940, get their display clock information from the local time of the SRST router during SRST registration. If the Cisco Unified SRST router is configured to use the Network Time Protocol (NTP) to automatically sync the Cisco Unified SRST router time from an NTP time server, only UTC time is delivered to the router. This is because the NTP server could be physically located anywhere in the world, in any timezone. As it is important to display the correct local time, use the clock timezone command to adjust or offset the Cisco Unified SRST router time.

The date and time formats that appear on the displays of all Cisco Unified IP Phones in Cisco Unified CallManager fallback mode are selected using the date-format and time-format commands as configured below:

SUMMARY STEPS

1. clock timezone zone hours-offset [minutes-offset]

2. call-manager-fallback

3. date-format {mm-dd-yy | dd-mm-yy | yy-dd-mm | yy-mm-dd}

4. time-format {12 | 24}

5. exit

DETAILED STEPS

 
Command or Action
Purpose

Step 1 

clock timezone zone hours-offset [minutes-offset]

Example:

Router(config)# clock timezone PST -8

Sets the time zone for display purposes.

zone—Name of the time zone to be displayed when standard time is in effect. The length of the zone argument is limited to 7 characters.

hours-offset—The number of hour difference from Coordinated Universal Time (UTC).

minutes-offset—(Optional) Minutes difference from UTC.

Step 2 

call-manager-fallback

Example:

Router(config)# call-manager-fallback

Enters call-manager-fallback configuration mode.

Step 3 

date-format {mm-dd-yy | dd-mm-yy | yy-dd-mm | yy-mm-dd}

Example:

Router(config-cm-fallback)# date-format yy-dd-mm

Sets the date format for IP phone display. The choices are mm-dd-yy, dd-mm-yy, yy-dd-mm, and yy-mm-dd, where

dd—day

mm—month

yy—year

The default is set to mm-dd-yy.

Step 4 

time-format {12 | 24}

Example:

Router(config-cm-fallback)# time-format 24

Sets the time display format on all Cisco Unified IP Phones registered with the router. The default is set to a 12-hour clock.

Step 5 

exit

Example:

Router(config-cm-fallback)# exit

Exits call-manager-fallback configuration mode.


Example

The following example sets the time zone to Pacific Standard Time (PST), which is 8 hours behind UTC and sets the time display format to a 24 hour clock:

Router(config)# clock timezone PST -8
Rounter(config)# call-manager-fallback
Rounter(config-cm-fallback)# time-format 24

Configuring IP Phone Language Display

During Cisco Unified CallManager fallback, the language displays shown on Cisco Unified IP Phones default to the ISO-3166 country code of US (United States). The Cisco IP Phone 7940 and Cisco IP Phone 7960 can be configured for different languages (character sets and spelling conventions) using the user-locale command.


Note This configuration option is available in Cisco SRST V2.1 and later running under Cisco CallManager V3.2 and later. Systems with software prior to Cisco SRST V2.1 and Cisco CallManager V3.2 can use the default country, United States (US), only.


SUMMARY STEPS

1. call-manager-fallback

2. user-locale country-code

3. exit

DETAILED STEPS

 
Command or Action
Purpose

Step 1 

call-manager-fallback

Example:

Router(config)# call-manager-fallback

Enters call-manager-fallback configuration mode.

Step 2 

user-locale country-code

Example:

Router(config-cm-fallback)# user-locale ES

Selects a language by country for displays on the Cisco IP Phone 7940 and Cisco IP Phone 7960.

The following ISO-3166 codes are available to Cisco SRST and Cisco Unified SRST systems running under Cisco CallManager V3.2 or later:

DE—German.

DK—Danish.

ES—Spanish.

FR—French.

IT—Italian.

JP—Japanese Katakana (available under Cisco Unified CallManager V4.0 or later).

NL—Dutch.

NO—Norwegian.

PT—Portuguese.

RU—Russian.

SE—Swedish.

US—United States English (default).

Step 3 

exit

Example:

Router(config-cm-fallback)# exit

Exits call-manager-fallback configuration mode.

Examples

The following example offers a configuration for the Portugal user locale.

call-manager-fallback
 user-locale PT

Configuring Customized System Messages for Cisco Unified IP Phones

The system message command is used to customize the system message displayed on all Cisco UnifiedIP Phone 7910, Cisco Unified IP Phone 7940G, and Cisco Unified IP Phone 7960G units during Cisco Unified CallManager fallback.

One of two keywords, primary and secondary, must be included in the command. The primary keyword is for IP phones that can support static text messages during fallback, such as the Cisco IP Phone 7940 and Cisco IP Phone 7960 units. The default display message for primary IP phones in fallback mode is "CM Fallback Service Operating."

The secondary keyword is for Cisco Unified IP Phones that do not support static text messages and have a limited display space, such as the Cisco IP Phone 7910. Secondary IP phones flash messages during fallback. The default display message for secondary IP phones in fallback mode is "CM Fallback Service."

Changes to the display message will occur immediately after configuration or at the end of each call.


Note The normal in-service static text message is controlled by Cisco Unified CallManager.


SUMMARY STEPS

1. call-manager-fallback

2. system message {primary primary-string | secondary secondary-string}

3. exit

DETAILED STEPS

 
Command or Action
Purpose

Step 1 

call-manager-fallback

Example:

Router(config)# call-manager-fallback

Enters call-manager-fallback configuration mode.

Step 2 

system message {primary primary-string | secondary secondary-string}

Example:

Router(config-cm-fallback)# system message primary Custom Message

Declares the text for the system display message on IP phones in fallback mode.

primary primary-string—For Cisco Unified IP Phones that can support static text messages during fallback, such as the Cisco Unified IP Phone 7940 and Cisco Unified IP Phone 7960 units. A string of approximately 27 to 30 characters is allowed.

secondary secondary-string—For Cisco Unified IP Phones that do not support static text messages, such as the Cisco Unified IP Phone 7910. A string of approximately 20 characters is allowed.

Step 3 

exit

Example:

Router(config-cm-fallback)# exit

Exits call-manager-fallback configuration mode.

Examples

The following example sets "SRST V3.0" as the system display message for all Cisco Unified IP Phones on a router:

call-manager-fallback
 system message primary SRST V3.0
 system message secondary SRST V3.0
 exit

Configuring a Secondary Dial Tone

A secondary dial tone can be generated when a phone user dials a predefined PSTN access prefix and can be terminated when additional digits are dialed. An example is when a secondary dial tone is heard after the number 9 is dialed to reach an outside line.

SUMMARY STEPS

1. call-manager-fallback

2. secondary-dialtone digit-string

3. exit

DETAILED STEPS

 
Command or Action
Purpose

Step 1 

call-manager-fallback

Example:

Router(config)# call-manager-fallback

Enters call-manager-fallback configuration mode.

Step 2 

secondary-dialtone digit-string

Example:

Router(config-cm-fallback)# secondary-dialtone 9

Activates a secondary dial tone when a digit string is dialed.

Step 3 

exit

Example:

Router(config-cm-fallback)# exit

Exits call-manager-fallback configuration mode.

Examples

The following example sets the number 8 to trigger a secondary dial tone:

call-manager-fallback
secondary-dialtone 8

Configuring Dual-Line Phones

Dual-line phone configuration is required for dual-line phone operation during Cisco Unified CallManager fallback. Consultative transfer is also required (see the "Enabling Consultative Call Transfer and Forward Using H.450.2 and H.450.3 with Cisco SRST 3.0" section on page 82).

Dual-line IP phones are supported during Cisco Unified CallManager fallback using the max-dn command. Dual-line IP phones have one voice port with two channels to handle two independent calls. This capability enables call waiting, call transfer, and conference functions on a phone-line button.

In dual-line mode, each IP phone and its associated line button can support one or two calls. Selection of one of two calls on the same line is made using the blue Navigation button located below the phone display. When one of the dual-line channels is used on a specific phone, other phones that share the ephone-dn will be unable to use the secondary channel. The secondary channel will be reserved for use with the primary dual-line channel.

It is recommended that hunting be disabled to the second channel. For more information, see the "Configuring Dial-Peer and Channel Hunting" section on page 78.

SUMMARY STEPS

1. call-manager-fallback

2. max-dn max-directory-numbers [dual-line] [preference preference-order]

3. exit

DETAILED STEPS

 
Command or Action
Purpose

Step 1 

call-manager-fallback

Example:

Router(config)# call-manager-fallback

Enters call-manager-fallback configuration mode.

Step 2 

max-dn max-directory-numbers [dual-line] [preference preference-order]

Example:

Router(config-cm-fallback)# max-dn 15 dual-line preference 1

Sets the maximum number of directory numbers (DNs) or virtual voice ports that can be supported by the router and activates the dual-line mode.

max-directory-numbers—Maximum number of directory numbers or virtual voice ports supported by the router. The maximum number is platform-dependent. The default is 0. See the "Platform and Memory Support" section on page 29 for further details.

dual-line—(Optional) Allows IP phones in Cisco Unified CallManager fallback mode to have a virtual voice port with two channels.

preference preference-order (Optional)—Sets the global preference for creating the VoIP dial peers for all directory numbers that are associated with the primary number. Range is from 0 to 10. Default is 0, which is the highest preference.

The alias command also has a preference keyword that sets alias command preference values. Setting the alias command preference keyword allows the default preference set with the max-dn command to be overriden. See Configuring Call Rerouting, page 66 for more information on using the max-dn command with the alias command.

Step 3 

exit

Example:

Router(config-cm-fallback)# exit

Exits call-manager-fallback configuration mode.

Examples

The following example sets the maximum number of DNs or virtual voice ports that can be supported by a router to 10 and activates the dual-line mode for all IP phones in Cisco Unified CallManager fallback mode.

call-manager-fallback
 max-dn 10 dual-line
 exit

How to Set Up Cisco IP Communicator for Cisco Unified SRST

Cisco IP Communicator is a software-based application that delivers enhanced telephony support on personal computers. Cisco IP Communicator appears on a user's computer monitor as a graphical, display-based IP phone with a color screen, a key pad, feature buttons, and soft keys.

For information about operation, see the Cisco IP Communicator online help and user documentation.

Prerequisites

You should have the following before you begin this task:

IP address of the Cisco Unified SRST TFTP server

Headset with microphone for your PC (Optional; you can use PC internal speakers and microphone)

SUMMARY STEPS

1. Download the latest version of the Cisco IP Communicator software and install it on your PC.

2. (Optional) Attach the headset to your PC.

3. Start the Cisco IP Communicator software application.

4. Define the IP address of the Cisco Unified SRST TFTP server.

5. Wait for the Cisco IP Communicator application to connect to the Cisco Unified SRST system and register itself.

6. Perform final configuration of buttons and numbers for the Cisco IP Communicator from the Cisco Unified SRST router.

DETAILED STEPS


Step 1 Download the latest version of the Cisco IP Communicator software and install it on your PC.

Step 2 (Optional) Attach a headset to your PC.

Step 3 Start the Cisco IP Communicator software application.

Step 4 Define the IP address of the Cisco Unified SRST TFTP server.

a. Open the Network > User Preferences window.

b. Enter the IP address of the Cisco Unified SRST TFTP server.

Step 5 Wait for the Cisco IP Communicator application to connect to the Cisco Unified SRST system and registers itself.


Verifying Cisco IP Communicator


Step 1 Use the show running-config command to display ephone-dn and ephone information associated with this phone.

Step 2 After Cisco IP Communicator registers with Cisco Unified CME, it displays the phone extensions and soft keys in its configuration. Verify that these are correct.

Step 3 Make a local call from the phone and ask someone to call you. Verify that you have a two-way voice path.


Troubleshooting Cisco IP Communicator


Step 1 Use the debug ephone detail command to diagnose problems with calls. For more information, see the Cisco IOS Debug Command Reference. Go to http://www.cisco.com/en/US/products/sw/iosswrel/tsd_products_support_category_home.html and click the appropriate Cisco IOS Software Release and Command References.


Where to Go Next

The next step is setting up call handling. For instructions, see the " Setting Up Call Handling" chapter.


hometocprevnextglossaryfeedbacksearchhelp

Posted: Mon Jun 19 10:56:44 PDT 2006
All contents are Copyright © 1992--2006 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.