Cisco Unified CallManager System Guide, Release 4.2(3)
Cisco Unified IP Phones
Downloads: This chapterpdf (PDF - 496.0KB) The complete bookPDF (PDF - 5.08MB) | Feedback

Cisco Unified IP Phones

Table Of Contents

Cisco Unified IP Phones

Supported Cisco Unified IP Phones

H.323 Clients and CTI Ports

Cisco IP Communicator

Phone Button Templates

Default Phone Button Templates

Guidelines for Customizing Phone Button Templates

Softkey Templates

Add Application

Configure Softkey Layout

Softkey Template Operation

Methods for Adding Phones

Directory Numbers

Shared Line Appearance

Managing Directory Numbers

Making and Receiving Multiple Calls Per Directory Number

Transfer and Conference Behavior

Direct Transfer and Join Behavior

Onhook Call Transfer

Original Calling Party on Transfer

Phone Features

Phone Association

Phone Administration Tips

Phone Search

Messages Button

Directories Button

Cisco Unified CallManager User Options

MaxPhonesFallBackQueueDepth Service Parameter

Dependency Records

Phone Failover and Fallback

Phone Configuration Checklist

Where to Find More Information


Cisco Unified IP Phones


Cisco Unified IP Phones as full-featured telephones can plug directly into your IP network. H.323 clients, CTI ports, and Cisco IP Communicator comprise software-based devices that you configure similarly to the Cisco Unified IP Phones. Cisco Unified CallManager Administration allows you to configure phone features such as call forwarding and call waiting for your phone devices. You can also create phone button templates to assign a common button configuration to a large number of phones.

After you have added the phones, you can associate users with them. By associating a user with a phone, you give that user control over that device.

This section covers the following topics:

Supported Cisco Unified IP Phones

H.323 Clients and CTI Ports

Cisco IP Communicator

Phone Button Templates

Softkey Templates

Softkey Template Operation

Methods for Adding Phones

Directory Numbers

Phone Features

Phone Association

Phone Administration Tips

Phone Failover and Fallback

Phone Configuration Checklist

Where to Find More Information

Supported Cisco Unified IP Phones

Table 40-1 provides an overview of the features that are available on the following Cisco Unified IP Phones that Cisco Unified CallManager supports:

Cisco Unified IP Phone 7900 family

Cisco Unified IP Phone Expansion Module 7914

Cisco IP Conference Station 7935 and 7936

Cisco Unified IP Phone model 30 VIP

Cisco Unified IP Phone model 12 series

Not all Cisco Unified IP Phone models support all features and services. For the latest information on features and services that support these phone models, refer to the following documentation:

Phone administration or user documentation that supports the phone model and this version of Cisco Unified CallManager

Firmware release notes for your phone model

Cisco Unified CallManager release notes

Table 40-1 Supported Cisco Unified IP Phones and Features 

Cisco Unified IP Phone Model
Description

Cisco Unified IP Phone model 7970 and Cisco Unified IP Phone model 7971

The Cisco Unified IP Phone models 7970 and 7971, full-featured, eight-line business sets, support the SCCP and SIP protocols and the following features:

A backlit, color touchscreen display for easy access to call details and features.

Four fixed feature buttons:

Messages—Accessing voice-messaging messages

Settings—Adjusting phone settings

Services—Accessing services

Directories—Accessing call logs and directories

A Help (?) button for immediate assistance with calling features

Eight programmable buttons to use as line buttons and speed-dial buttons, or for other phone services

Five softkeys for accessing additional call details and functionality (Softkeys change depending on the call state for a total of 16 softkeys.)

An internal, two-way, full-duplex speakerphone and microphone mute

The Cisco Unified IP Phone models 7970/71G-GE specify the gigabit ethernet version of the Cisco Unified IP Phone model 7970/71 while Cisco Unified IP Phones models 7970G, 7960G, and 7940G represent the non-gigabit version.

Cisco Unified IP Phone model 7960 and Cisco Unified IP Phone model 7961

The Cisco Unified IP Phone models 7960 and 7961, full-featured, six-line business sets, support the SCCP and SIP protocols and the following features:

A help (?) button

Six programmable buttons to use as line, speed-dial, or feature buttons

Four fixed buttons for accessing voice-messaging messages, adjusting phone settings, accessing services, and accessing directories

Four softkeys for accessing additional call details and functionality (Softkeys change depending on the call state for a total of 16 softkeys.)

A large LCD display that shows call details and softkey functions

An internal, two-way, full-duplex speakerphone and microphone mute

Cisco Unified IP Phone model 7940 and Cisco Unified IP Phone model 7941

The Cisco Unified IP Phone models 7940 and 7941, two-line business sets with features similar to the Cisco Unified IP Phone model 7960, support the SCCP and SIP protocols and include the following features:

A help (?) button

Two programmable buttons to use as line, speed-dial, or feature buttons

Four fixed buttons for accessing voice-messaging messages, services, and directories, and for adjusting phone settings

Four softkeys for accessing additional call details and functionality (Softkeys change depending upon the call state for a total of 16 softkeys.)

A large LCD display that shows call details and softkey functions

An internal, two-way, full-duplex speakerphone and microphone mute

Cisco Unified IP Phone model 7920

The Cisco Wireless IP Phone model 7920, which is an easy-to-use IEEE 802.11b wireless IP phone, provides comprehensive voice communication in conjunction with Cisco Unified CallManager and Cisco Aironet (r) 1200, 1100, 350, and 340 series of Wi-Fi (IEEE 802.11b) access points. Features include

A pixel-based display for intuitive access to calling features.

Two softkeys that dynamically present calling options to the user.

A four-way rocker switch that allows easy movement through the displayed information.

Volume control for easy decibel-level adjustments of the handset and ringer when in use.

Cisco Unified IP Phone Expansion Module 7914

Cisco Unified IP Phone Expansion Module 7914 extends the functionality of the Cisco Unified IP Phone Model 7960 by providing 14 additional buttons. To configure these buttons as lines or speed dials, use Phone Button Template Configuration.


Note You can create the Cisco Unified IP Phone Expansion Module 7914 phone button template by renaming the phone button template that is used for the standard Cisco Unified IP Phone model 7960. Refer to "Configuring a Cisco Unified IP Phone Expansion Module 7914 Phone Button Template" in the Cisco Unified CallManager Administration Guide.


The Cisco Unified IP Phone Expansion Module 7914 includes an LCD to identify the function of the button and the line status.

You can daisy chain two modules to provide 28 additional lines or speed-dial and feature buttons.

Cisco Unified IP Phone model 7912G

The Cisco Unified IP Phone model 7912G, which is a single-line phone that supports a maximum of two calls at the same time, provides basic-feature functionality for individuals who conduct low to medium telephone traffic.

This model, which supports inline power, provides an integrated 10/100 Ethernet switch for connectivity to a collocated PC.

This model offers four dynamic softkeys.

Cisco Unified IP Phone model 7911

The Cisco Unified IP Phone Model 7911, which is a single-line phone that supports a maximum of two calls at the same time, supports the SCCP and SIP protocols and provides basic-feature functionality for individuals who conduct low to medium telephone traffic.

The Cisco Unified IP Phone Model 7911 provides menus that are similar to the Cisco Unified IP Phone Model 7970. The Applications Menu button opens a main applications menu.

This model, which supports inline power, provides an integrated 10/100 Ethernet switch for connectivity to a collocated PC.

This model offers four dynamic softkeys.

Cisco Unified IP Phone model7910

The Cisco Unified IP Phone model 7910, a single-line, basic-feature phone that is designed primarily for common-use areas with medium telephone traffic such as lobbies or breakrooms, includes the following features:

Four dedicated feature buttons for Line, Hold, Transfer, and Settings

Six programmable feature buttons that you can configure through phone button templates in Cisco Unified CallManager

Available features include Call Park, Redial, Speed Dial, Call Pickup, Conference, Forward All, Message Waiting, and Meet-Me Conference.

A two-line LCD display (24 characters per line) that indicates the directory number, call status, date, and time

An internal speaker that is designed for hands-free dialing.

Cisco Unified IP Phone model 7905G

The Cisco Unified IP Phone model 7905G, a low-cost, single-line, basic-feature phone that is designed primarily for common-use areas such as cafeterias, breakrooms, lobbies, and manufacturing floors, includes the following features:

LCD that displays features such as time, date, phone number, caller ID, call status, and softkey tabs

Four softkeys that engage any functions that display on the corresponding LCD screen tabs. Softkey functions change depending on the status of the phone

Three dedicated buttons for Hold, Menu, and Navigation

An internal speaker that is designed for hands-free dialing

Cisco Unified IP Phone model 7902G

The Cisco Unified IP Phone model 7902G provides a cost-effective, entry-level IP phone for a lobby, laboratory, manufacturing floor, or another area where only basic calling capability is required. The single-line Cisco Unified IP Phone model 7902G includes the following features:

Fixed feature keys that provide one-touch access to the redial, transfer, conference, and voice-messaging access features

Three dedicated buttons for hold, menu, and volume control

Inline power that allows the phone to receive power over the LAN

Cisco Unified IP Conference Station 7936

The Cisco IP Conference Station model 7936, a full-featured, IP-based, hands-free conference station for use on desktops and offices and in small-to medium-sized conference rooms, includes the following features:

Three softkeys and menu navigation keys that guide a user through call features and functions

Available features include Call Park, Call Pick Up, Group Call Pick Up, Transfer, and Conference (Ad Hoc and Meet-Me).

An LCD display that indicates the date and time, calling party name, calling party number, digits dialed, feature, and line status

A digitally tuned speaker and three microphones that allow conference participants to move around while speaking

Microphone mute

Ability to add external microphones to support larger rooms

Cisco IP Conference Station 7935

The Cisco IP Conference Station 7935, a full-featured, IP-based, hands-free conference station for use on desktops and offices and in small-to medium-sized conference rooms, includes the following features:

Three softkeys and menu navigation keys that guide a user through call features and functions

Available features include Call Park, Call Pick Up, Group Call Pick Up, Transfer, and Conference (Ad Hoc and Meet-Me).

An LCD display that indicates the date and time, calling party name, calling party number, digits dialed, feature, and line status

A digitally tuned speaker and three microphones that allow conference participants to move around while speaking

Microphone mute

Cisco Unified IP Phone model 12 SP+

The Cisco Unified IP Phone model 12 SP+ offers many of the same features as PBX or POTS telephones. This IP phone includes the following features:

12 programmable line and feature buttons

An LED that is associated with each of the 12 feature and line buttons to indicate feature and line status

A two-line LCD display (20 characters per line) for call status and identification

An internal, two-way speakerphone and microphone mute

Cisco Unified IP Phone model 30 VIP

The Cisco Unified IP Phone model 30 VIP offers many of the same features as PBX or POTS telephones. This IP phone includes the following features:

26 programmable line and feature buttons

An LED that is associated with each of the 26 feature and line buttons to indicate feature and line status

A two-line LCD for displaying date and time, calling party name, calling party number, and digits dialed

An internal, two-way speakerphone with microphone mute

Dedicated feature buttons for Transfer, Hold, and Redial


H.323 Clients and CTI Ports

Cisco Unified CallManager Administration enables you to configure software-based devices such as H.323 clients and CTI ports. Software-based Cisco Unified CallManager applications such as Cisco SoftPhone, Cisco AutoAttendant, and Cisco Unified IP Interactive Voice Response (IVR) use CTI ports that are virtual devices.

H.323 clients include Microsoft NetMeeting devices.

You configure H.323 clients and CTI ports through the Phone Configuration window in Cisco Unified CallManager Administration like you do phones, but they often require fewer configuration settings.


Note Cisco recommends that you do not configure CTI ports or devices that use TAPI applications in a line group.


For information on H.323 clients and shared line appearances, see the "Shared Line Appearance" section.

For instructions on how to configure H.323 clients and CTI ports, refer to "Cisco Unified IP Phone Configuration" in the Cisco Unified CallManager Administration Guide.

Cisco IP Communicator

Cisco IP Communicator, a software-based application, allows users to place and receive phone calls by using their personal computers. Cisco IP Communicator depends upon the Cisco Unified CallManager call-processing system to provide telephony features and voice-over-IP capabilities.

This interaction with Cisco Unified CallManager means that Cisco IP Communicator provides the same functionality as a full-featured Cisco Unified IP Phone, while providing the portability of a desktop application. Additionally, it means that you administer Cisco IP Communicator as a phone device by using the Cisco Unified CallManager Administration Phone Configuration window.

Phone Button Templates

Cisco Unified CallManager includes several default phone button templates. When adding phones, you can assign one of these templates to the phones or create a new template.

Creating and using templates provides a fast way to assign a common button configuration to a large number of phones. For example, if users in your company do not use the conference feature, you can create a template that reassigns this button to a different feature, such as speed dial.

To create a template, you must make a copy of an existing template and assign the template a unique name. You can make changes to the custom templates that you created, and you can change the labels of the default phone button templates. You cannot change the function of the buttons in the default templates. You can rename existing templates and modify them to create new ones, update custom templates to add or remove features, lines, or speed dials, and delete custom templates that are no longer being used. When you update a template, the change affects all phones that use the template.

Renaming a template does not affect the phones that use that template. All Cisco Unified IP Phones that use this template continue to use this template after it is renamed.

Make sure that all phones have at least one line that is assigned to each phone. Normally, this assignment specifies button 1. Phones can have additional lines that are assigned, depending on the Cisco Unified IP Phone model. Phones also generally have several features, such as speed dial, that are assigned to the remaining buttons.

You can delete phone templates that are not currently assigned to any phone in your system if they are not the only template for a given phone model. You cannot delete a template that is assigned to one or more devices or the default template for a model (specified in the Device Defaults Configuration window). You must reassign all Cisco Unified IP Phones that are using the template that you want to delete to a different phone button template before you can delete the template.


Note The standard phone button template for the Cisco Unified IP Phone model 7960, which supports the Cisco Unified IP Phone Expansion Module 7914, includes buttons for both devices (up to 34 buttons).


Use the Dependency Records link on the Phone Button Template Configuration window to view the devices that are using a particular template.

Cisco Unified CallManager does not directly control all features on Cisco Unified IP Phones through phone button templates. Refer to the Cisco Unified IP Phone Administration Guide for Cisco Unified CallManager and other phone documentation for detailed information about individual Cisco Unified IP Phone 7900 family models.

Default Phone Button Templates

Although all Cisco Unified IP Phones support similar features, you implement these features differently on various models. For example, some models configure features such as Hold or Transfer by using phone button templates; other models have fixed buttons or onscreen program keys for these features that are not configurable. Also, the maximum number of lines or speed dials that are supported differs for some phone models. These differences require different phone button templates for specific models.

Each Cisco Unified IP Phone model comes with a default phone button template. You can use the default templates as is to quickly configure phones. You can also copy and modify the templates to create custom templates.

Custom templates enable you to make features available on some or all phones, restrict the use of certain features to certain phones, configure a different number of lines or speed dials for some or all phones, and so on, depending on how the phone will be used. For example, you may want to create a custom template that can be applied to phones that will be used in conference rooms. Table 40-2 provides descriptions of the default phone button template for each Cisco Unified IP Phone model.

Table 40-2 Default Phone Button Templates Listed by
Template Name 

Default Phone Button Template Name
Default Phone Button Template Description

Standard 7985

The Standard 7985 template uses buttons 1 and 2 for lines and assigns buttons 3 through 8 as speed dials. Access other phone features, such as call park, call forward, redial, hold, resume, voice-messaging system, conferencing, and so on, by using softkeys on the Cisco Unified IP Phone model 7985.

Standard 7971 SCCP

The Standard 7971 SCCP template uses buttons 1 and 2 for lines and assigns buttons 3 through 8 as speed dials. Access other phone features, such as call park, call forward, redial, hold, resume, voice-messaging system, conferencing, and so on, by using softkeys on the Cisco Unified IP Phone model 7971.

Standard 7971 SIP

The Standard 7971 SIP template uses buttons 1 and 2 for lines and assigns buttons 3 through 8 as speed dials. Access other phone features, such as call park, call forward, redial, hold, resume, voice-messaging system, conferencing, and so on, by using softkeys on the Cisco Unified IP Phone model 7971.

Standard 7970 SCCP

The Standard 7970 SCCP template uses buttons 1 and 2 for lines and assigns buttons 3 through 8 as speed dials. Access other phone features, such as call park, call forward, redial, hold, resume, voice-messaging system, conferencing, and so on, by using softkeys on the Cisco Unified IP Phone model 7970.

Standard 7970 SIP

The Standard 7970 SIP template uses buttons 1 and 2 for lines and assigns buttons 3 through 8 as speed dials. Access other phone features, such as call park, call forward, redial, hold, resume, voice-messaging system, conferencing, and so on, by using softkeys on the Cisco Unified IP Phone 7970.

Standard 7961 SCCP and Standard 7961G-GE SCCP

The Standard 7961 SCCP template uses buttons 1 and 2 for lines and assigns buttons 3 through 6 as speed dials or lines or for the features privacy and service URL. Access other phone features, such as abbreviated dial, call park, call forward, redial, hold, resume, call back, conferencing, and so on, by using softkeys on the Cisco Unified IP Phone model 7961.

Standard 7961 SIP

The Standard 7961 SIP template uses buttons 1 and 2 for lines and assigns buttons 3 through 6 as speed dials or lines or for the features privacy and service URL. Access other phone features, such as abbreviated dial, call park, call forward, redial, hold, resume, call back, conferencing, and so on, by using softkeys on the Cisco Unified IP Phone model 7961.

Standard 7960 SCCP

The Standard 7960 SCCP template uses buttons 1 and 2 for lines and assigns buttons 3 through 6 as speed dials or lines or for the features privacy and service URL. Access other phone features, such as abbreviated dial, call park, call forward, redial, hold, resume, call back, conferencing, and so on, by using softkeys on the Cisco Unified IP Phone model 7960.

Standard 7960 SIP

The Standard 7960 SIP template uses buttons 1 and 2 for lines and assigns buttons 3 through 6 as speed dials or lines or for the features privacy and service URL. Access other phone features, such as abbreviated dial, call park, call forward, redial, hold, resume, call back, conferencing, and so on, by using softkeys on the Cisco Unified IP Phone model 7960.

Standard 7941 SCCP and Standard 7941G-GE SCCP

The Standard 7941 SCCP template comes with a preconfigured one-line phone button template (button 1 for line 1 and button 2 for speed dial). Access phone features, such as abbreviated dial, call park, call forward, redial, hold, resume, call back, conferencing, and so on, by using softkeys on the Cisco Unified IP Phone model 7941.

Standard 7941 SIP

The Standard 7940 SIP template comes with a preconfigured one-line phone button template (button 1 for line 1 and button 2 for speed dial). Access phone features, such as abbreviated dial, call park, call forward, redial, hold, resume, call back, conferencing, and so on, by using softkeys on the Cisco Unified IP Phone model 7941.

Standard 7940 SCCP

The Standard 7940 SCCP templates comes with a preconfigured one-line phone button template (button 1 for line 1 and button 2 for speed dial). Access phone features, such as abbreviated dial, call park, call forward, redial, hold, resume, call back, conferencing, and so on, by using softkeys on the Cisco Unified IP Phone model 7940.

Standard 7940 SIP

The Standard 7940 SIP template comes with a preconfigured one-line phone button template (button 1 for line 1 and button 2 for speed dial). Access phone features, such as abbreviated dial, call park, call forward, redial, hold, resume, call back, conferencing, and so on, by using softkeys on the Cisco Unified IP Phone model 7940.

Standard 7920

The Standard 7920 template uses buttons 1 and 2 for lines and assigns buttons 3 through 6 for speed dials.

Standard 7912 SCCP

The Standard 1912 SCCP template uses button 1 for line 1, buttons 2 through 5 for speed dial, button 6 for Hold, and button 7 for Settings.

Standard 7912 SIP

The Standard 7912 SIP template uses button 1 for line 1, buttons 2 through 5 for speed dial, button 6 for Hold, and button 7 for Settings.

Standard 7911 SCCP

The Standard 7911 SCCP template uses button 1 for line 1, makes button 2 configurable (default specifies None), and assigns buttons 3 through 6 as speed dials. Access other phone features, such as abbreviated dial, call park, call forward, redial, hold, resume, call back, conferencing, and so on, by using softkeys on the Cisco Unified IP Phone model 7911.

Standard 7911 SIP

The Standard 7911 SIP template uses button 1 for line 1, makes button 2 configurable (default specifies None), and assigns buttons 3 through 6 as speed dials. Access other phone features, such as abbreviated dial, call park, call forward, redial, hold, resume, call back, conferencing, and so on, by using softkeys on the Cisco Unified IP Phone model 7911.

Standard 7910

The default phone button template for the Cisco Unified IP Phone model 7910 uses button 1 for message waiting, button 2 for conference, button 3 for forwarding, buttons 4 and 5 for speed dial, and button 6 for redial.

The Cisco Unified IP Phone model 7910 includes fixed buttons for Line, Hold, Transfer, and Settings.

Standard 7905 SCCP

The Standard 7905 SCCP template uses button 1 for line 1, buttons 2 through 5 for speed dial, button 6 for Hold, and button 7 for Settings.

Standard 7905 SIP

The Standard 7905 SIP template uses button 1 for line 1, buttons 2 through 5 for speed dial, button 6 for Hold, and button 7 for Settings.

Standard 7902

The default phone button template for the Cisco Unified IP Phone model 7902 uses button 1 for line 1, buttons 2 through 5 for speed dial, button 6 for Hold, and button 7 for Settings.

Standard 7936

The default phone button template, which is not configurable, for the Cisco Unified IP Conference Station 7936 uses button 1 for line 1.

Standard 7935

The default phone button template, which is not configurable, for the Cisco IP Conference Station 7935 uses button 1 for line 1.

Standard 30 SP+

The default Cisco Unified IP Phone model 30 SP+ template uses buttons 1 through 4 for lines, and button 5 for call park; button 6 through 8 and 17 through 21 remain undefined, and button 9 through 13 and 22 through 25 apply for speed dial; button 14 applies for message waiting indicator, button 15 for forward, and button 16 for conference.

Note For only the Cisco Unified IP Phone model 30 SP+, assign button 26 for automatic echo cancellation (AEC).

Standard 30 VIP

The default Cisco Unified IP Phone model 30 VIP template uses buttons 1 through 4 for lines, button 5 for call park, button 6 through 13 and 22 through 26 for speed dial, button 14 for message waiting indicator, button 15 for call forward, and button 16 for conference.

Standard 12 Series, including the 12 S, 12 SP, and 12 SP+

The default Cisco Unified IP Phone 12 Series template uses buttons 1 and 2 for lines, button 3 for redial, buttons 4 through 6 for speed dial, button 7 for hold, button 8 for transfer, button 9 for forwarding, button 10 for call park, button 11 for message waiting, and button 12 for conference.

Default VGC Virtual Phone Template

The default phone button template for the Cisco VGC Virtual Phone uses button 1 for a line and buttons 2 through 10 for speed dials.

Standard ATA 186 (and 188)

The default phone button template for the Cisco ATA 186 and Cisco ATA 188 uses button 1 for a line and buttons 2 through 10 for speed dials.

Standard IPMA Assistant 7960

The default phone button template for the Cisco IPMA Assistant uses button 1 and buttons 7 through 12 for lines, buttons 2 through 6 and buttons 17 through 34 for speed dials.

ISDN BRI Phone

The default phone button template for the ISDN BRI phone uses button 1 for line 1.

Default IP Communicator Template

The default Cisco IP Communicator template uses buttons 1 and 2 for lines and assigns buttons 3 through 8 as speed dials. Access other phone features, such as call park, call forward, redial, hold, resume, voice messaging system, conferencing, and so on using softkeys (by configuring the softkey template to the phone).

Standard IP-STE

The Standard IP-STE template uses buttons 1 and 2 for lines.

Standard Analog

The Standard Analog template for analog phones uses button 1 for line 1.

Generic SIP Phone - 2 Lines

The Generic SIP Phone - 2 Lines template, which is used for third-party SIP phones, uses buttons 1 and 2 for lines.


Guidelines for Customizing Phone Button Templates

Use the following guidelines when you are creating custom phone button templates:

Make sure that phone users receive a quick reference card or getting started guide that describes the most basic features of the custom template. If you create a custom template for employees in your company to use, make sure that it includes the following features and that you describe them on the quick reference card that you create for your users.

Cisco Unified IP Phone models 7970, 7960, 7940—Line (one or more)

Cisco Unified IP Phone model 7912—Line, speed dial, hold, and settings

Cisco Unified IP Phone model 7910—Forward all

Cisco Unified IP Phone models 7905 and 7902—Line, speed dial, hold, and settings

Cisco Unified IP Phone model 12 SP+—Line (one or more), hold, call park, and forward all

Cisco Unified IP Phone model 30 VIP—Line (one or more), call park, and forward all

Cisco VGC Virtual Phone and Cisco ATA 186 (and 188)—Line and speed dials

Consider the nature of each feature to determine how to configure your phone button template. You might want to assign multiple buttons to speed dial and line; however, you usually require only one of the other phone button features that are described in Table 40-3.

Table 40-3 Phone Button Feature Description 

Feature
Description

AEC

If you are configuring a template for the Cisco Unified IP Phone model 30 VIP, you must include one occurrence of this feature and assign it to button 26. Auto echo cancellation (AEC) reduces the amount of feedback that the called party receives when the calling party is using a speakerphone. Users should press the AEC button on a Cisco Unified IP Phone model 30 SP+ when they are using speakerphone. Users do not need to press this button when speakerphone is not in use. This feature requires no configuration for it to work.

Answer/release

In conjunction with a headset apparatus, the user can press a button on the headset apparatus to answer and release (disconnect) calls.

Auto answer

If this feature is programmed on the template, activating this button causes the speakerphone to go off hook automatically when an incoming call is received.

Note You configure this feature for some phones models through the Phone Button Template window. You configure this feature for some phone models in the Phone Configuration window.

Call park

In conjunction with a call park number or range, when the user presses this button, call park places the call at a directory number for later retrieval. You must have a call park number or range that is configured in the system for this button to work, and you should provide that number or range to your users, so they can dial in to the number(s) to retrieve calls.

Call Park BLF

Users can monitor the busy/idle status of directed call park numbers using the Call Park Busy Lamp Field (BLF) buttons. Users can also speed dial those numbers by pressing the BLF buttons. One directed call park number gets configured for each Call Park BLF button. To successfully park or retrieve a call by using a Call Park BLF button, you must ensure that the partition and the calling search space of the device are configured correctly.

Note Use this button with the directed call park feature (a transfer function), not with the standard call park feature (a hold function).

Conference

Users can initiate an ad hoc conference and add participants by pressing the Conference button. (Users can also use the Join softkey to initiate an ad hoc conference.)

Only the person who initiates an ad hoc conference needs a conference button. You must make sure that an ad hoc conference bridge device is configured in Cisco Unified CallManager Administration for this button to work. See Conference Bridges for more information.

Forward all

Users press this button to forward all calls to the designated directory number. Users can designate forward all in the Cisco Unified IP Phone Configuration windows, or you can designate a forward all number for each user in Cisco Unified CallManager Administration.

Hold

Users press this button to place an active call on hold. To retrieve a call on hold, users press the flashing line button or lift the handset and press the flashing line button for the call on hold. The caller on hold receives a tone every 10 seconds to indicate the hold status or music (if the Music On Hold feature is configured). The hold tone feature requires no configuration to work.

Line

Users press this button to dial a number or to answer an incoming call. You must have added directory numbers on the user phone for this button to work.

Meet-Me conference

When users press this button, they initiate a meet-me conference, and they expect other invited users to dial in to the conference. Only the person who initiates a meet-me conference needs a meet-me button. You must make sure that a meet-me conference device is configured in Cisco Unified CallManager Administration for this button to work.

Message waiting

Users press this button to connect to the voice-messaging system.

None

Use None to leave a button unassigned.

Redial

Users press this button to redial the last number that was dialed on the Cisco Unified IP Phone. This feature requires no configuration to work.

Privacy

Users press this button to activate/deactivate privacy.

Service URL

Users press this button to access a Cisco Unified IP Phone Service such as personal fast dials, stock quotes, or weather.

Speed-dial

Users press this button to speed dial a specified number. System administrators can designate speed-dial numbers in Cisco Unified CallManager Administration. Users can designate speed-dial numbers in the Cisco Unified IP Phone User Options Menu.

Transfer

Users press this button to transfer an active call to another directory number. This feature requires no configuration to work.


Softkey Templates

Use softkey templates to manage softkeys that are associated with applications such as Cisco Unified CallManager Assistant or call-processing features such as Cisco Call Back on the Cisco Unified IP Phones. The administrator uses the Softkey Template Configuration windows in Cisco Unified CallManager Administration to create and update softkey templates.

Cisco Unified CallManager supports two types of softkey templates: standard and nonstandard. Standard softkey templates in the Cisco Unified CallManager database contain the recommended selection and positioning of the softkeys for an application. Cisco Unified CallManager provides the following standard softkey templates:

Standard User

Standard Feature

Standard IPMA Assistant

Standard IPMA Manager

Standard IPMA Shared Mode Manager


Note The default process does not assign a softkey template to the Cisco Unified IP Phone. The administrator must assign standard or nonstandard softkey templates to the Cisco Unified IP Phone by assigning the templates individually to each phone or by assigning the common profile to each phone.


The administrator creates a nonstandard softkey template by using the Softkey Template Configuration windows in Cisco Unified CallManager Administration. To create a nonstandard softkey template, the administrator copies a standard softkey template and makes changes. The administrator can add and remove applications that are associated with any nonstandard softkey template. Additionally, the administrator can configure softkey sets for each call state for a nonstandard softkey template.

The Softkey Template Configuration window lists the standard and nonstandard softkey templates and uses different icons to differentiate between standard and nonstandard templates.

The administrator assigns softkey templates in the following Cisco Unified CallManager Administration configuration windows:

Common Profile Configuration

Phone Configuration (Cisco Unified IP Phones models 7905, 7912, 7920, 7940, 7960, 7970)

User Device Profile Configuration

Add Application

The administrator can add a standard softkey template that is associated with a Cisco application to a nonstandard softkey template. When the administrator clicks the Add Application button from the Softkey Template Configuration window, a separate window displays and allows the administrator to choose the standard softkey template that is to be added to the end of the nonstandard softkey template. Duplicate softkeys get deleted from the end of the set that is moving to the front of the set.


Tip To refresh the softkeys for an application in the nonstandard softkey template, choose the standard softkey template that is already associated with the nonstandard softkey template. For example, if the administrator originally copied the Standard User template and deleted some buttons, choose the Standard User softkey template by clicking on the Add Application button. This adds the buttons that are included in the chosen softkey template.


The number of softkeys in any given call state cannot exceed 16. A message displays, and the add application procedure stops when the maximum number of softkeys is reached. The administrator must manually remove some softkeys from the call state before trying to add another application to the template.

The Delete Application button allows the administrator to delete application softkey templates that are associated with a nonstandard softkey template. Only the softkeys that are associated with the application get deleted. When softkeys are commonly shared between applications, they remain in the softkey template until the last application that shares the softkeys is removed from the softkey template.

Configure Softkey Layout

The administrator can configure softkey sets for each call state for a nonstandard softkey template. When the administrator clicks the Configure Softkey Layout link from the Softkey Template Configuration window, the Softkey Layout Configuration window displays.

The Softkey Layout Configuration window contains the following fields:

Call states—Lists the different call states of a Cisco Unified IP Phone. You cannot add, update, or delete call states. The highlighted call state indicates the chosen call state and the softkeys that are available for that call state. Table 40-4 lists the call states.

Table 40-4 Call States 

Call State
Description

Connected

Displays when call is connected

Connected Conference

Consultation call for conference in connected call state

Connected Transfer

Consultation call for transfer in connected call state

Digits After First

Off-hook call state after user enters the first digit

Off Hook

Dial tone presented to phone

Off Hook With Feature

Off-hook call state for transfer or conference consultation call

On Hold

Call on hold

On Hook

Displays when no call exists for that phone

Remote In Use

Another device that shares the same line uses call.

Ring In

Call received and ringing

Ring Out

Call initiated and the destination ringing


Unselected softkeys—Lists softkeys that are associated with a call state. This field lists the unselected, optional softkeys when the call state is highlighted. The softkeys that are listed in this field get added to the chosen softkeys field by using the right arrows. You can add the Undefined softkey more than once in the chosen softkey list. Choosing Undefined results in a blank softkey on the Cisco Unified IP Phone.

Selected softkeys—Lists softkeys that are associated with the chosen call state. This field lists the chosen softkeys when the call state is highlighted. The maximum number of softkeys in this field cannot exceed 16. See Figure 40-1 for a sample softkey layout.


Note Cisco recommends that a softkey remain in the same position for each call state. This provides the user with consistency and ease of use; for example, the More softkey always appears in the fourth softkey position from the left for each call state.


Figure 40-1 Sample Softkey Layout

Softkey Template Operation

For applications such as Cisco Unified CallManager Assistant to support softkeys, ensure softkeys and softkey sets are configured in the database for each device that uses the application.

You can mix application and call-processing softkeys in any softkey template. A static softkey template associates with a device in the database. When a device registers with Cisco Unified CallManager, the static softkey template gets read from the database into call processing and then gets passed to the device to be used throughout the session (until the device is no longer registered or is reset). When a device resets, it may get a different softkey template or softkey layout because of updates that the administrator makes.

Softkeys support a field called application ID. An application, such as Cisco Unified CallManager Assistant, activates/deactivates application softkeys by sending a request to the device through the Cisco CTIManager and call processing with a specific application ID.

When a user logs into the Cisco IP Manager Assistant service and chooses an assistant for the service, the application sends a request to the device, through Cisco CTIManager and call processing, to activate all its softkeys with its application ID.

At any time, several softkey sets may display on a Cisco Unified IP Phone (one set of softkeys for each call).

The softkey template that is associated with a device (such as a Cisco Unified IP Phone) in the database designates the one that is used when the device registers with call processing. Perform the association of softkey templates and devices by using Softkey Template configuration in Cisco Unified CallManager Administration. See "Softkey Template Configuration" in the Cisco Unified CallManager Administration Guide.

Methods for Adding Phones

You can automatically add phones to the Cisco Unified CallManager database by using auto-registration, manually by using the phone configuration windows, or in groups with the Bulk Administration Tool (BAT).

By enabling auto-registration before you begin installing phones, you can automatically add a Cisco Unified IP Phone to the Cisco Unified CallManager database when you connect the phone to your IP telephony network. For information on enabling auto-registration, refer to "Enabling Auto-Registration" in the Cisco Unified CallManager Administration Guide. During auto-registration, Cisco Unified CallManager assigns the next available sequential directory number to the phone. In many cases, you may not want to use auto-registration; for example, if you want to assign a specific directory number to a phone or if you plan to implement authentication or encryption, as described in Cisco Unified CallManager Security Guide.


Tip Cisco Unified CallManager automatically disables auto-registration if you configure the clusterwide security mode for authentication and encryption through the Cisco CTL client.


If you do not use auto-registration, you must manually add phones to the Cisco Unified CallManager database or use the Bulk Administration Tool (BAT). BAT, a plug-in application, enables system administrators to perform batch add, modify, and delete operations on large numbers of Cisco Unified IP Phones. Refer to the Bulk Administration Tool User Guide for detailed instructions on using BAT.

Directory Numbers

Using Directory Number Configuration in Cisco Unified CallManager Administration, you can configure and modify directory numbers (lines) that are assigned to phones. Keep in mind, however, that directory numbers do not always associate with devices (see the "Managing Directory Numbers" section).

You can configure up to 200 calls for a line on a device in a cluster, with the limiting factor being the device. As you configure the number of calls for one line, the calls available for another line decrease. Cisco Unified IP Phones that support the multicall display (such as a Cisco Unified IP Phone model 7960) support up to 200 calls per DN and 2 calls per DN for non-multicall display devices (such as Cisco Unified IP Phone model 7905).

The Cisco Unified IP Phone displays the following information about each line:

Unique call identifier (from 1 to 200). This identifier remains consistent across all multicall display devices that have a shared line appearance.

Call select status, an icon which shows the state of the currently selected call.

Call information such as calling party or called party.

Call state icon such as connected or hold.

Duration of a call

For configuration information, see "Adding a Directory Number" in the Cisco Unified CallManager Administration Guide.

Shared Line Appearance

You can set up one or more lines with a shared line appearance. A Cisco Unified CallManager system considers a directory number to be a shared line if it appears on more than one device in the same partition. For example, if directory number 9600 on phone A is in the partition called Dallas and on phone B in the partition called Texas, that directory number does not represent a shared line appearance. (The directory number 9600 for phone A and phone B must exist in the same partition; for example, Dallas.)

In a shared line appearance, for example, you can set up a shared line, so a directory number appears on line 1 of a manager phone and also on line 2 of an assistant phone. Another example of a shared line would comprise a single incoming 800 number that is set up to appear as line 2 on every sales representative phone in an office. You can also choose to update a directory number and have the updates apply to all devices that share the directory number.

The following information provides tips and lists the restrictions for using shared line appearances with Cisco Unified CallManager:

Shared Line Tips

You create a shared line appearance by assigning the same directory number and partition to different devices.

If other devices share a line, the words Shared Line display in red next to the directory number in the Directory Number Configuration window in Cisco Unified CallManager Administration.

If you change the Calling Search Space or Call Forward and Pickup settings on any device that uses the shared line, the changes apply to all devices that use that shared line.

To stop sharing a line appearance on a device, change the directory number or partition name for the line and update the directory number in the Directory Number Configuration window in Cisco Unified CallManager Administration.

In the case of a shared line appearance, Remove From Device removes the directory number on the current device only and does not affect other devices.

If you are experiencing delayed connect times over SCCP pipes to remote sites, check the Remote Device check box in the Phone Configuration window. Checking this check box tells Cisco Unified CallManager to allocate a buffer for the phone device when it registers and to bundle SCCP messages to the phone. Because this feature consumes resources, be sure to check this check box only when you are experiencing signaling delays for SCCP phones. Refer to Cisco Unified IP Phone Configuration in the Cisco Unified CallManager Administration Guide for more information.

Cisco Unified CallManager Assistant with shared line support allows managers and assistants to share lines (refer to Cisco Unified CallManager Assistant With Shared Line Support in the Cisco Unified CallManager Features and Services Guide).

Most devices with a shared line appearance can make or receive new calls or resume held calls at the same time. Incoming calls display on all devices that share a line, and anyone can answer the call. Only one call stays active at a time on a device. For limitations, see the "Shared Line Restrictions" section.

Call information (such as calling party or called party) displays on all devices that share a line. If the Privacy feature is turned on by one of the devices, other devices that share the line will not perceive outbound calls that are made from the device that turned privacy on. All devices still perceive inbound calls to the shared line.

Devices with shared line appearances can initiate independent transfer transactions.

Devices with shared line appearances can initiate independent conference transactions.

Devices with shared line appearance support the Call Forward Busy Trigger and the Maximum Number of Calls settings. You can configure Call Forward Busy Trigger per line appearance, but the configuration cannot exceed the maximum number call setting for that directory number.

The following example demonstrates how three Cisco Unified IP Phones with the same shared line appearance, directory number 2000, use Call Forward Busy Trigger and Maximum Number of Calls settings. This example assumes that two calls occur. Assume that the following values have been configured for the devices:

Cisco Unified IP Phone 1—Configured for a maximum call value of 1 and busy trigger value of 1

Cisco Unified IP Phone 2—Configured for a maximum call value of 1 and busy trigger value of 1

Cisco Unified IP Phone 3—Configured a for maximum call value of 2 and busy trigger value of 2

When User 1 dials directory number 2000 for the first call, all three devices ring. The user for the Cisco Unified IP Phone 3 picks up the call, and the Cisco Unified IP Phones 1 and 2 go to remote in use. When the user for Cisco Unified IP Phone 3 puts the call on hold, user can retrieve the call from the Cisco Unified IP Phone 1 or Cisco Unified IP Phone 2. When User 2 dials directory number 2000 for the second call, only Cisco Unified IP Phone 2 and Cisco Unified IP Phone 3 ring.

The following example demonstrates how an H.323 client, MGCP POTS Phone, and Cisco Unified IP Phone with the same shared line appearance, directory number 2000, can use the Call Forward Busy Trigger and the Maximum Number of Calls settings. This example assumes that two calls occur. Assume that the following values have been configured for the devices:

H.323 client—Configured for a maximum call value of 1 and busy trigger value of 1

MGCP POTS Phone—Configured for a maximum call value of 1 and busy trigger value of 1

Cisco Unified IP Phone—Configured for a maximum call value of 2 and busy trigger value of 2

When User 1 dials directory number 2000 for the first call, all three devices ring. The user for the Cisco Unified IP Phone picks up the call; when the user for Cisco Unified IP Phone puts the call on hold, the user(s) for H323 client and MGCP POTS Phone cannot retrieve the call. If User 2 dials directory number 2000 for the second call, only the Cisco Unified IP Phone rings. Users for the MCGP POTS Phone or the H.323 Client cannot answer the call.

For information on Maximum Number of Calls setting, refer to the "Directory Number Configuration Settings" in the Cisco Unified CallManager Administration Guide.

The check box, Update Directory Number of All Devices Sharing this Line, in the Directory Number Configuration window, determines whether a shared directory number gets updated to all devices sharing the number. Refer to the "Update Directory Number of All Devices Sharing this Line" section for more information.

Be aware that a shared line phone should not be able to interact with the call that it rejects, due to the limitation of the maximum number of calls per DN or for other reasons. For example, A and A' share the same DN. A' and A have the maximum number of calls set to 1 and 2, respectively. When C and D call the share line DN, A' answers these two calls. A can only interact with the first call, as it rejects the second call due to its own maximum number of calls per DN limitation. For this reason, Cisco recommends that the same value be configured for the maximum number of calls for all shared line MCID devices. For N number of devices sharing the same line, both Maximum Calls setting and Busy Trigger setting must be set to N. This allows each shared line user to receive at least one call.

The shared line phone should not interact with the call that it does not receive (because the Line Control does not maintain call information). So, a newly registered device will not recognize any existing calls on that line. The newly registered device cannot resume any held call if the call started before this device was registered with the Line Control. For example, A and A' share the same line, A is powered down (or logged out for the extension mobility user), and A's receives an active call. After phone A is on and it registers with Cisco Unified CallManager, A should not perceive the existing active call in this line.

If shared line phones' calls should interact with each other, Cisco recommends that you set the maximum number of calls for all shared lines MCID devices to 2*N, where N specifies the number of shared line devices.

Shared Line Restrictions

Do not use shared lines for Cisco Unified CallManager Attendant Console pilot points or hunt group members. The phone that acts as the attendant console supports shared lines.

Do not use shared line appearances on any Cisco Unified IP Phone that requires auto-answer capability and do not turn on auto answer for a shared line appearance.

Do not configure shared line appearances on the primary lines of the phones; for example, if two phones have a shared line appearance, only one of the phones should have the primary line configured as shared (the other phone should have the secondary line configured as shared).

Barge and Privacy work with shared lines only.

Cisco recommends that you do not configure shared lines for Cisco Unified IP Phones, H.323 clients, and MGCP POTS phones. If you do so, you cannot use the hold/resume feature on the H.323 client or MGCP POTS phone.

Shared lines are not supported in SIP SRST.

Managing Directory Numbers

Directory numbers associate with devices such as phones, route points, CTI ports, and H.323 clients. Administrators manage directory numbers from the Directory Number Configuration and Route Plan Report windows in Cisco Unified CallManager Administration. Use the Directory Number Configuration window to add, update, and remove directory numbers from a device, route point, or port. Use the Route Plan Report window to delete or update unassigned directory numbers from Cisco Unified CallManager database.


Note Do not associate a directory number with a CTI route point or CTI port if the directory number is a member of a line group.


The Directory Number Configuration window contains two check boxes: Active and Update Directory Number of All Device Sharing this Line.

Active Check Box

The Active check box, which only displays for unassigned directory numbers, determines whether the directory number gets loaded and used by Cisco Unified CallManager. By checking the check box, the directory number gets loaded and used by Cisco Unified CallManager. For example, the directory number belonged to an employee who left the company. The directory number had certain settings configured, like call forwarding to voice-messaging system. By leaving the directory number active, a call that is intended for the directory number will get forwarded. This eliminates the need to reconfigure another employee to have the same call-forwarding options. If the check box is not checked, Cisco Unified CallManager does not load the directory number, which results in settings that are configured for that DN not being used (for example, call forward destinations), and callers will not get their call properly forwarded.

Update Directory Number of All Devices Sharing this Line

This check box determines whether a shared directory number gets updated to all devices that share the number. By checking the check box, all devices that share the directory number will receive the directory number change. By leaving the check box unchecked, only the current device that displays in the window gets the directory number changed, and all other devices that share the directory number remain unchanged.


Note This check box only applies to the actual directory number and partition. It does not apply to the other device settings such as voice-messaging profile, call-forwarding options, or MLPP. If any of these settings are changed for a shared line, all devices get changed.


For directory number configuration and update information, refer to "Configuring Directory Numbers" in the Cisco Unified CallManager Administration Guide. For information about deleting and updating unassigned directory numbers, refer to "Deleting Unassigned Directory Numbers" and "Updating Unassigned Directory Numbers" in the Cisco Unified CallManager Administration Guide.

Making and Receiving Multiple Calls Per Directory Number

Cisco Unified CallManager supports various behaviors when users make and receive multiple calls per DN: Transfer/Direct Transfer and Conference/Join.

Transfer allows different line appearances in one device to initiate independent transfer transactions and allows multiple transfer transactions per line appearance per device.

Conference allows different line appearances in one device to initiate independent conference transactions and allows multiple conference transactions per line appearance per device.


Note Devices that do not support multicall display, such as Cisco Unified IP Phone model 7910, cannot transfer or conference two existing calls together.


Transfer and Conference Behavior

If only one active call exists on the directory number, the first invocation of a feature results in putting the active call on hold and initiating a new call by using the same directory number. When the new call gets set up, the second invocation of the same feature starts the feature operation. The first invocation of Transfer/Conference will always initiate a new call by using the same directory number, after putting the active call on hold.

Direct Transfer and Join Behavior

The following information describes Direct Transfer and Join behavior:

Direct Transfer joins two established calls (call is in hold or in connected state) into one call and drops the feature initiator from the call. Direct Transfer does not initiate a consultation call and does not put the active call on hold.

Join does not create a consultation call and does not put the active call on hold. To implement Join, choose at least two calls and then press the Join softkey on one of the calls. Join can include more than two calls, which results in a call with more than three parties. Join supports up to 16 participants in a call. To choose an active or held call, highlight the call and press the "Select" softkey. A checked indicator shows next to the selected call on the phone. The call that initiates the Join gets automatically included, even if not selected.

Join does not create a consultation call and does not put the active call on hold. To implement Join, choose at least two calls and then press the Join softkey on one of the calls. Join can include more than two calls, which results in a call with three or more parties. Join supports up to 16 participants in a call. To choose an active or held call, highlight the call and press the Select softkey. A selected call has a checked indicator shown next to it on the phone.

The call that initiates the Join gets automatically included, even if not selected. The active call gets included even if not selected.

If all the calls in the join are a basic call, then the call that initiated the join is the primary call. If any call in the join is a conference call (that is, it was in a conference before being joined), then that call is the primary call.

The selected status of the final call after the join depends on the selected status of the primary call before the join. If the primary call was selected, then after the join, the final call remains selected. If the primary call was not selected, then after the join, the final call remains unselected.

Onhook Call Transfer

Modifications to the Call Transfer feature add the onhook (hangup) action as a possible last step to complete a call transfer. Ensure the Transfer On-hook Enabled service parameter, which enables onhook call transfer, is set to True for onhook call transfer to succeed. If the service parameter is set to False, the onhook action ends the secondary call to the third party.

In the existing implementation, if user B has an active call on a particular line (from user A) and user B has not reached the maximum number of calls on this line, the Cisco Unified IP Phone provides a Transfer softkey to user B. If user B presses the Transfer softkey (or Transfer button, if available) once, user B receives dial tone and can make a secondary call: user B dials the number of a third party (user C). Cisco Unified CallManager provides a Transfer softkey to user B again. If user B presses the Transfer softkey again (or Transfer button, if available), the transfer operation completes.

With the new onhook call transfer implementation, user B can hang up after dialing user C, and the transfer completes. Both the existing and new implementations work in both the case of a blind transfer (user B disconnects before user C answers) and also in the case of a consult transfer (user B waits for user C to answer and announces the call from user A).

The previous implementation remains unchanged: user B can press the Transfer softkey twice to complete the transfer.

Original Calling Party on Transfer

When enabled, the Original Calling Party on Transfer feature displays the original calling party name and number on calls that are transferred by using Cisco Unity voice-messaging system.

Administrators enable this feature by setting the Cisco CallManager service parameter, Display Original Calling Number on Transfer from Cisco Unity, to True. This parameter determines whether Cisco Unified CallManager displays the original calling party number for calls that are transferred from the Cisco Unity voice-messaging system. Valid values specify True (display the original calling number when a call is transferred from a Unity voice-messaging port) or False (display the number of the Unity voice-messaging port through which the call was transferred). The default setting specifies False.

The following steps describe the scenario when the service parameter is enabled and a user performs a consult transfer to another Unity number.

1. User A makes a call to user B.

2. The call gets forwarded to the Unity server.

3. The Unity server executes a consulted transfer to another number.

4. Cisco Unified CallManager inspects the device type that initiates the consult transfer, and the calling party number and name for user A get presented to the called party.


Note When the Original Calling Party on Transfer feature is enabled on Cisco Unified CallManager, a transfer loop can occur on Unity. For more information, refer to the Cisco Unified CallManager 4.2 Integration Guide for Cisco Unity 4.0.


Call Accounting

Because Cisco Unified CallManager will send the calling party information for the Unity-initiated consult transfer call, the CDR of the consult transfer call will show that the original caller calls the transfer destination party; it does not show that the Unity port calls the transfer destination party.

Phone Features

Cisco Unified CallManager enables you to configure the following phone features on Cisco Unified IP Phones: barge, privacy release, call back, call waiting, call forward, call park, call pickup, immediate divert, hold reversion, malicious call identification, quality report tool, service URL, and speed dial and abbreviated dial.

Barge and Privacy

The Barge and Privacy features work together. Both features work with shared lines only.

Barge adds a user to a call that is in progress. Pressing the Barge or cBarge softkey automatically adds the user (initiator) to the shared line call (target), and the users currently on the call receive a tone. Barge supports built-in conference and shared conference bridges.

Privacy allow a user to allow or disallow other users of shared-line devices to view its call information or to allow another user to barge into its active calls.

For more information about Barge and Privacy, refer to Barge, Privacy, and Privacy on Hold in the Cisco Unified CallManager Features and Services Guide.

Call Back

The Cisco Call Back feature allows you to receive callback notification on your Cisco Unified IP Phone when a called party line becomes available. To receive callback notification, a user presses the CallBack softkey while receiving a busy or ringback tone. You can activate callback notification on a line on a Cisco Unified IP Phone within the same Cisco Unified CallManager cluster as your phone. You cannot activate callback notification if the called party forwarded all calls to another extension.

For more information about the Call Back feature, refer to the Cisco Unified CallManager Features and Services Guide and the user guide for the specific Cisco Unified IP Phone.

Call Forward

Call forward allows a user to configure a Cisco Unified IP Phone, so all calls that are destined for it ring another phone. Several types of call forward exist:

Call forward all—Forwards all calls.

Call forward busy—Forwards calls only when the line is in use and busy trigger setting is reached.

Call forward no answer—Forwards calls when the phone is not answered after the configured no answer ring duration.

Call forward no bandwidth—Applies the forwarding values in the AAR settings fields when a call is blocked for insufficient bandwidth.

Call forward unregistered—Forwards calls that are routed to a directory number with no registered devices.

The administrator can configure call forward information display options to the original dialed number or the redirected dialed number or to both. The administrator can enable or disable the calling line ID (CLID) and calling name ID (CNID). The display option gets configured for each line appearance.

The call forward busy trigger gets configured for each line appearance in a cluster and cannot exceed the maximum number of calls that are configured for a line appearance. The call forward busy trigger determines how many active calls exist on a line before the call forward busy setting gets activated (for example, 10 calls).

The call forward no answer ring duration gets configured for each line appearance in a cluster, and the default specifies 12 seconds. The call forward no answer ring duration determines how long a phone rings before the call forward no answer setting gets activated.


Tip Keep the busy trigger slightly lower than the maximum number of calls, so users can make outgoing calls and perform transfers.


Configure call forward in the Directory Number Configuration window in Cisco Unified CallManager Administration.

Call Park

Call park allows a user to place a call on hold, so anyone who is configured to use call park on the Cisco Unified CallManager system can retrieve it.

For example, if a user is on an active call at extension 1000, the user can park the call to a call park extension such as 1234, and another user can dial 1234 to retrieve the call.

To use call park, you must add the call park extension (in this case, 1234) in Cisco Unified CallManager Administration when you are configuring phone features. For more information about call park, refer to Call Park and Directed Call Park in the Cisco Unified CallManager Features and Services Guide.

Directed Call Park

Directed Call Park allows a user to transfer a parked call to an available user-selected directed call park number. Configure directed call park numbers in the Cisco Unified CallManager Directed Call Park Configuration window. Configured directed call park numbers exist cluster wide. You can configure phones that support the directed call park Busy Lamp Field (BLF) to monitor the busy/idle status of specific directed call park numbers. Users can also use the BLF to speed dial a directed call park number.

A user can retrieve a parked call by dialing a configured retrieval prefix followed by the directed call park number where the call is parked. For example, if the call is parked on directed call park number 80 and the configured retrieval prefix is 2, a user can retrieve the call by dialing 280.

For more information about directed call park, refer to Call Park and Directed Call Park in the Cisco Unified CallManager Features and Services Guide.

Call Pickup

Cisco Unified CallManager provides the following types of call pickup:

Call pickup—Allows you to answer another ringing phone in your designated call pickup group. You can configure group call pickup notification (audible, visual, or both) for this type of call pickup.

Group call pickup—Allows you to answer incoming calls in another pickup group.

Other group call pickup—Allows you to answer incoming calls in a pickup group that is associated with your own group.

All three types of call pickup can operate automatically or manually. If the service parameter, AutoCallPickupEnabled, is enabled, the Cisco Unified CallManager automatically connects you to the incoming call after you press one of the following softkeys on the phone:

Pickup—For call pickup (calls in your own pickup group)

GPickup—For group call pickup (calls in another pickup group)

OPickup—For other group call pickup (calls in a pickup group that is associated with your own pickup group)

After the call pickup feature is automated, you need to use only one keystroke for a call connection except for group call pickup. You dial the DN of that other pickup group after you press the GPickup softkey on the phone.


Note CTI applications support monitoring the party whose call is picked up. CTI applications do not support monitoring the pickup requester or the destination of the call that is picked up. Hence, Cisco IPMA does not support auto call pickup (one-touch call pickup).


You configure the call pickup feature when you are configuring phone features in Cisco Unified CallManager.

When adding a line, you can indicate the call pickup group. The call pickup group indicates a number that can be dialed to answer calls to this directory number (in the specified partition). For more information about call pickup, refer to the "Call Pickup" section and the "Call Pickup Group Configuration" chapter of the Cisco Unified CallManager Administration Guide.

Call Select

The Select softkey allows a user to select a call for feature activation or to lock the call from other devices that share the same line appearance. Pressing the Select softkey on a selected call deselects the call.

When a device selects the call, it gets put in the Remote-In-Use state on all other devices that share the line appearance. You cannot select a call in the Remote-In-Use state. In other words, selecting a call instance will lock it from other devices that share the same line appearance.

A special display symbol identifies selected calls.

Call Waiting

Call waiting lets users receive a second incoming call on the same line without disconnecting the first call. When the second call arrives, the user receives a brief call-waiting indicator tone, which is configured with the Ring Setting (Phone Active) in the Directory Number Configuration window.

Configure call waiting in the Directory Number Configuration window in Cisco Unified CallManager Administration by setting the busy trigger (greater than 2) and maximum number of calls.


Tip To configure call waiting for phones with no display (such as the Cisco Unified IP Phone Model 30 VIP), set the busy trigger to 2 and the maximum number of calls to 2.


Conference List

The conference list feature provides a list of participant directory numbers that are in an ad hoc conference. The name of the participant displays if it is configured in Cisco Unified CallManager Administration.

Any participant can invoke the conference list feature on the phone and can view the participants. The conference controller can invoke the conference list feature and can view and remove any participant in the conference by using the Remove softkey.

Direct Transfer

Using the DirTrfr and Select softkeys, a user can transfer any two established calls, which remove the calls from the IP phone. For more information about Direct Transfer, see the "Making and Receiving Multiple Calls Per Directory Number" section.

Hold Reversion

The Hold Reversion feature alerts a phone user when a held call exceeds a configured time limit. When the held call duration exceeds the limit, Cisco Unified CallManager generates alerts, such as a ring or beep, at the phone to remind the user to handle the call. The held call becomes a reverted call when the hold duration exceeds the configured time limit.

For example, if you configure this feature to notify you when a call remains on hold past 30 seconds, Cisco Unified CallManager sends an alert, such as a ring or beep, to the phone after 30 seconds. You can also configure reminder alerts at configured intervals. A user can retrieve a reverted call by going off hook, which deactivates the feature.

As administrator, you configure hold reversion timers and other feature settings in Cisco Unified CallManager Administration for the cluster or for a line.

For more information about hold reversion, see Hold Reversion in the Cisco Unified CallManager Features and Services Guide.

Immediate Divert

The Immediate Divert feature allows you to immediately divert a call to a voice-messaging system. Managers and assistants, or anyone who shares lines, use this feature. When the call gets diverted, the line becomes available to make or receive new calls.

Access the Immediate Divert feature by using the iDivert softkey. Configure this softkey by using the Softkey Template Configuration window of Cisco Unified CallManager Administration. The softkey template gets assigned to phones that are in the Cisco Unified CallManager system.

For more information about Immediate Divert, refer to Immediate Divert in the Cisco Unified CallManager Features and Services Guide.

Join

Using the Join softkey, a user can join up to 15 established calls (for a total of 16) to create a conference. For more information about Join, see the "Making and Receiving Multiple Calls Per Directory Number" section.

Malicious Call Identification (MCID)

The MCID feature provides a useful method for tracking troublesome or threatening calls. When a user receives this type of call, the Cisco Unified CallManager system administrator can assign a new softkey template that adds the Malicious Call softkey to the user phone. For POTS phones that are connected to a SCCP gateway, users can use a hookflash and enter a feature code of *39 to invoke the MCID feature.

For more information about MCID, refer to the "Malicious Call Identification" chapter in the Cisco Unified CallManager Features and Services Guide.

Quality Report Tool

The Quality Report Tool (QRT), a voice-quality and general problem-reporting tool for Cisco Unified IP Phones, allows users to easily and accurately report audio and other general problems with their IP phone. QRT gets loaded as part of the Cisco Unified CallManager installation, and the Cisco Extended Functions (CEF) service supports it.

As system administrator, you enable QRT functionality by creating, configuring, and assigning a softkey template to associate the QRT softkey on a user IP phone. You can choose from two different user modes, depending upon the level of user interaction that you want with QRT. You then define how the feature will work in your system by configuring system parameters and setting up Cisco Unified CallManager Serviceability tools. You can create, customize, and view phone problem reports by using the QRT Viewer application.

Support for the QRT feature extends to any model IP phone that includes the following capabilities:

Support for softkey templates

Support for IP phone services

Controllable by CTI

Contains an internal HTTP server


Note For more information, refer to the following URL for the appropriate
Cisco Unified IP Phone guide for your phone model:
http://www.cisco.com/univercd/cc/td/doc/product/voice/c_ipphon/index.htm.


When users experience problems with their IP phones, they can report the type of problem and other relevant statistics by pressing the QRT softkey on the Cisco Unified IP Phone during one of the following call states:

Connected

Connected Conference

Connected Transfer

On Hook

From a supported call state, and using the appropriate problem classification category, a user can then choose the reason code that best describes the problem that is being reported for the IP phone. A customized phone problem report provides you with the specific information.

For detailed information about configuring and using the Quality Report Tool feature, refer to Quality Report Tool in the Cisco Unified CallManager Features and Services Guide. For more information about configuring and using the
QRT Viewer, refer to the
Cisco Unified CallManager Serviceability Administration Guide.

For information about the user interface, refer to the appropriate Cisco Unified IP Phone Guide for your model IP phone and the Cisco Unified IP Phone Administration Guide for Cisco Unified CallManager.

Call Diagnostics and Voice-Quality Metrics

You can configure Cisco Unified IP Phones to collect call diagnostics and voice-quality metrics by setting a service parameter in Cisco Unified CallManager Administration as described in the following steps:

1. From Cisco Unified CallManager Administration, choose System > Service Parameters.

2. In Clusterwide Parameters (Device - General), locate the Call Diagnostics Enabled service parameter.

3. From the drop-down list box, choose one of the following states:

Enabled Only When CDR Enabled Flag is True

Enabled Regardless of CDR Enabled Flag

4. Click Save.

For more information about configuring service parameters in Cisco Unified CallManager Administration, refer to "Service Parameters Configuration" in the Cisco Unified CallManager Administration Guide. For information on configuring Cisco Unified IP Phones in Cisco Unified CallManager Administration, refer to "Cisco Unified IP Phone Configuration" in the Cisco Unified CallManager Administration Guide. For information on configuring the Cisco Unified IP Phones for which call diagnostics and voice-quality metrics are available, refer to the Cisco Unified IP Phone user and administration documentation.

Service URL

You can also configure a Cisco Unified IP Phone Service URL, such as the extension mobility service, to a phone button. When the button gets pressed, the service gets invoked.

To configure a service URL on a phone button for the user, the administrator performs the following steps:

1. Using Cisco Unified IP Phone Services Configuration, create a service.

2. Using Phone Button Configuration, create a custom phone button template to include the service URL feature.

3. Using Phone Configuration, add the custom phone button template to each phone that requires the service URL button.

4. Using Phone Configuration, subscribe to each appropriate service.

5. Using Phone Configuration, add the service URL button.

6. Notify the users to configure services for their phone by using the Add/Update your Service URL Buttons link on the User Options Menu.

Speed Dial and Abbreviated Dial

Cisco Unified CallManager supports the configuration of up to 99 speed-dial entries, which are accessed through phone buttons and abbreviated dialing.

When the user configures up to 99 speed-dial entries, the user can assign part of the speed-dial entries to the speed-dial buttons on the IP phone; the remaining speed-dial entries get used for abbreviated dialing. When a user starts dialing digits, the AbbrDial softkey displays, and the user can access any speed-dial entry by entering the appropriate index. For information about configuring speed dials, refer to "Configuring Speed-Dial Buttons" in the Cisco Unified CallManager Administration Guide.

Phone Association

Users can control some devices, such as phones. Applications that are identified as users control other devices, such as CTI ports. When users have control of a phone, they can control certain settings for that phone, such as speed dial and call forwarding. For more information on associating phones with users, refer to "Associating Devices to a User" in the Cisco Unified CallManager Administration Guide.

Phone Administration Tips

The following sections contain information that might help you configure phones in the Cisco Unified CallManager Administration.

Phone Search

The following sections describe how to modify your search to locate a phone. If you have thousands of Cisco Unified IP Phones in your network, you may need to limit your search to find the phone that you want. If you are unable to locate a phone, you may need to expand your search to include more phones.


Note Be aware that the phone search is not case sensitive.


Searching by MAC Address

To search for a phone by its MAC address, choose Device Name and ends with and enter the last four or five characters in the MAC address.

Searching by Description

If you enter a user name and/or extension in the Description field when you are adding the phone, you can search by using that value in the Find and List Phones window.

Searching by Device Type

To search for a phone by its device type, choose Device Type and either enter a device type or choose a device type from the drop-down list box below the Find button.

Searching by Call Pickup Group

To search for a phone by its call pickup group, choose Call Pickup Group and choose a call pickup group name; then, click the Find button. Alternatively, click the Find button only.

Searching by Directory Number

To search for a phone by its directory number (DN), choose Directory Number and either enter a search criteria (such as begins with or ends with) or click the Find button.


Note Some directory numbers do not associate with phones. To search for those directory numbers, which are called unassigned DN, use the Route Plan Report window.


Searching by Using Wildcard Characters

To search by using wildcard searches, check the Allow wildcard check box. Wildcard searches get checked by default. Refer to the following example for a description of how Cisco Unified CallManager uses the wildcard search on a directory number.


Note In the Find and List Phones window, Cisco Unified CallManager recognizes only SQL wildcards. The asterisk (*) does not represent a recognized SQL wildcard. Use the percent sign (%) to search for any variable-length string of characters.


Example

Create phones with directory numbers that are all digits and another directory number that contains an expression:

DN 2001

DN 2002

DN 2003

DN 300[123]

Perform a search for a Directory Number that ends with [123] and Allow wildcards check box checked. The result of the search includes 2001, 2002, and 2003 (because it uses 123 as the wildcard search). If you perform the same search with Allow wildcards check box unchecked, the result of the search includes only 300[123] (the exact pattern). Table 40-5 lists the wildcard search strings that Cisco Unified CallManager allows in the Find and List Phones window.

Table 40-5 Wildcard Search Strings 

Wildcard Character
Description
Example

_ (underscore)

Any single character.

Where au_fname LIKE "_ean" finds all four-letter first names that end with ean (Dean, Sean, Jean).

[ ]

Any single character within the specified range ([a-f]) or set ([abcdef]).

Where au_lname LIKE "[CP] arsen" finds author last names ending with arsen and beginning with any single character between C and P; for example, Carsen, Larsen, Karsen.

[^]

Any single character not within the specified range ([^a-f]) or set ([^abcdef]).

Where au_lname LIKE "de[^l]" lists all author last names beginning with de and where the following letter is not l.

%

Any number of characters.

The expression SEP% finds all phones that begin with SEP, such as SEP111, SEP2222, SEP33333, and so forth.


Searching by Calling Search Space

If you choose calling search space, the options that are available in the database display. You can choose one of these options from the drop-down list box below the Find button.

Searching by Device Pool

If you choose device pool, the options that are available in the database display (for example, default). You can choose one of these options from the drop-down list box below the Find button.

Searching by LSC Status

If you choose LSC status, the options that are available in the database display (for example, operation pending). You can choose one of these options from the drop-down list box below the Find button.

Searching by Device Security Mode

If you choose device security mode, the options that are available in the database display (for example, use system default). You can choose one of these options from the drop-down list box below the Find button.

Finding All Phones in the Database

To find all phones that are registered in the database, choose Device Name from the list of fields; choose "is not empty" from the list of patterns; then, click the Find button.


Note The list in the Find and List Phones window does not include analog phones and fax machines that are connected to gateways (such as a Cisco VG200). This list shows only phones that are configured in Cisco Unified CallManager Administration.


Messages Button

By performing the following actions, you can configure a voice-messaging access number for the messages button on Cisco Unified IP Phone models 7970, 7960, and 7940, so users can access the voice-messaging system by simply pressing the messages button:

1. Configure the voice-mail pilot number by choosing Feature > Voice Mail > Voice Mail Pilot.

2. Configure the voice-mail profile by choosing Feature > Voice Mail > Voice Mail Profile.

3. Choose the appropriate profile from the Voice Mail Profile field on the Directory Number Configuration window. By default, this field uses the default voice-mail profile that uses the default voice-mail pilot number configuration.


Note Typically, you can edit the default voice-mail pilot and default voice-mail profiles to configure voice-messaging service for your site.


For more information on configuring a voice-messaging service, see Voice Mail Connectivity to Cisco Unified CallManager.


Note For the Cisco Unified IP Phone models 12 SP+ and 30 VIP, you can use phone button templates to configure a button with the message-waiting feature for access to a voice-messaging service.


Directories Button

The Cisco Unified IP Phone models 7970, 7960, and 7940 can display a directory of employee names and phone numbers. Although you access this directory from the directories button on the IP phone, you must configure it before users can access it. To use the corporate directory, you must enter users into a Lightweight Directory Access Protocol (LDAP) directory that is configured with Cisco Unified CallManager.

The URL Directories enterprise parameter defines the URL that points to the global directory for display on Cisco Unified IP Phone models 7970, 7960, and 7940 phones. The XML device configuration file for the phone stores this URL.


Tip If you are using IP addresses rather than DNS for name resolution, make sure that the URL Directories enterprise parameter value uses the IP address of the server for the hostname.

If the phone URL was not updated correctly after the URL Directories enterprise parameter was changed, try stopping and restarting the Cisco TFTP service; then, reset the phone.


Cisco Unified CallManager User Options

Cisco Unified IP Phone users can access the Cisco Unified CallManager User Options through their web browser, so they can configure a variety of features on their phone. Some of the configurable features include call forward, speed dial, and personal address book. By setting enterprise parameters as either True or False, administrators can configure which features are made available to users; for example, the administrator can set the Show Speed Dial Settings enterprise parameter to False, and users cannot configure speed dials on their phones.

MaxPhonesFallBackQueueDepth Service Parameter

The Cisco CallManager service uses the MaxPhonesFallBackQueueDepth service parameter to control the number of phones to queue on the higher priority Cisco Unified CallManager when that Cisco Unified CallManager is available for registration. The default specifies 10 phones per second. If a primary Cisco Unified CallManager were to fail, the phones will fail over to the secondary Cisco Unified CallManager. The failover process happens as fast as possible, using the priority queues to regulate the number of devices that are currently registering.

When the primary Cisco Unified CallManager recovers, the phones get returned to that Cisco Unified CallManager; however, you do not need to remove a phone from a working Cisco Unified CallManager, in this case the secondary, as fast as possible because the phone is on a working system. The queue depth gets monitored (using the MaxPhonesFallBackQueueDepth service parameter setting) to determine whether the phone that is requesting registration gets registered now or later. If the queue depth is greater than 10 (default), the phone stays where it is and tries later to register to the primary Cisco Unified CallManager.

In the Service Parameters Configuration window, you can modify the MaxPhonesFallBackQueueDepth service parameter. If the performance value is set too high (the maximum is 500), phone registrations could slow the Cisco Unified CallManager real-time response. If the value is set too low (the minimum is 1), the total time for a large group of phones to return to the primary Cisco Unified CallManager will be long.

Dependency Records

If you need to find out what directory numbers a specific phone is using or to what phones a directory number is assigned, click the Dependency Records link that the Cisco Unified CallManager Administration Phone Configuration or Directory Number Configuration window provides. The Dependency Records Summary window displays information about directory numbers that are using the phone. To find out more information about the directory number, click the directory number, and the Dependency Records Details window displays. If the dependency records are not enabled for the system, the dependency records summary window displays a message.

For more information about Dependency Records, refer to "Accessing Dependency Records" and "Removing a Directory Number from a Phone" in the Cisco Unified CallManager Administration Guide.

Phone Failover and Fallback

This section describes how phones fail over and fail back if the Cisco Unified CallManager to which they are registered becomes unreachable. This section also covers conditions that can affect calls that are associated with a phone, such as reset or restart.

Cisco Unified CallManager Fails or Becomes Unreachable

The active Cisco Unified CallManager designation applies to the Cisco Unified CallManager from which the phone receives call-processing services. The active Cisco Unified CallManager usually serves as the primary Cisco Unified CallManager for that phone (unless the primary is not available).

If the active Cisco Unified CallManager fails or becomes unreachable, the phone attempts to register with the next available Cisco Unified CallManager in the Cisco Unified CallManager Group that is specified for the device pool to which the phone belongs.

The phone device reregisters with the primary Cisco Unified CallManager as soon as it becomes available after a failure. See the "MaxPhonesFallBackQueueDepth Service Parameter" section for information about phone registration during failover.


Note Phones do not fail over or fall back while a call is in progress.


Phone is Reset

If a call is in progress, the phone does not reset until the call finishes.

Phone Configuration Checklist

Table 40-6 provides steps to manually configure a phone in Cisco Unified CallManager Administration. If you are using auto-registration, Cisco Unified CallManager adds the phone and automatically assigns the directory number.

Table 40-6 Phone Configuration Checklist 

Configuration Steps
Procedures and Related Topics

Step 1 

Gather the following information about the phone:

Model

MAC address

Physical location of the phone

Cisco Unified CallManager user to associate with the phone

Partition, calling search space, and location information, if used

Number of lines and associated DNs to assign to the phone

Phone Search

Step 2 

Add and configure the phone.

Adding a Phone, Cisco Unified CallManager Administration Guide

Step 3 

Add and configure lines (DNs) on the phone. You can also configure phone features such as call park, call forward, and call pickup.

Adding a Directory Number, Cisco Unified CallManager Administration Guide

Step 4 

Configure speed-dial buttons.

You can configure speed-dial buttons for phones if you want to provide speed-dial buttons for users or if you are configuring phones that do not have a specific user who is assigned to them. Users can change the speed-dial settings on their phones by using Cisco Unified IP Phone User Options.

Configuring Speed-Dial Buttons, Cisco Unified CallManager Administration Guide

Step 5 

Configure Cisco Unified IP Phone services.

You can configure services for Cisco Unified IP Phone models 7970, 7960, 7940, 7912, 7905, and Cisco IP Communicator if you want to provide services for users or if you are configuring phones that do not have a specific user who is assigned to them. Users can change the services on their phones by using the Cisco Unified IP Phone User Options.

Configuring Cisco Unified IP Phones, Cisco Unified CallManager Administration Guide

Step 6 

Customize phone button templates and softkey templates, if required. Configure templates for each phone.

Adding Phone Button Templates, Cisco Unified CallManager Administration Guide

Configuring Cisco Unified IP Phones, Cisco Unified CallManager Administration Guide

Adding Nonstandard Softkey Templates, Cisco Unified CallManager Administration Guide

Step 7 

Assign services to phone buttons, if required.

Adding a Cisco Unified IP Phone Service to a Phone Button, Cisco Unified CallManager Administration Guide

Step 8 

Provide power, install, verify network connectivity, and configure network settings for the Cisco Unified IP Phone.

Cisco Unified IP Phone Administration Guide for Cisco Unified CallManager

Step 9 

Associate user with the phone (if required).

Associating Devices to a User, Cisco Unified CallManager Administration Guide

Step 10 

Make calls with the Cisco Unified IP Phone.

Refer to the user guide for your Cisco Unified IP Phone.

Where to Find More Information

Related Topics

Voice Mail Connectivity to Cisco Unified CallManager

Call Pickup

Enabling Auto-Registration, Cisco Unified CallManager Administration Guide

Configuring Cisco Unified IP Phones, Cisco Unified CallManager Administration Guide

Associating Devices to a User, Cisco Unified CallManager Administration Guide

Phone Button Template Configuration, Cisco Unified CallManager Administration Guide

Service Parameters Configuration, Cisco Unified CallManager Administration Guide

Barge, Privacy, and Privacy on Hold, Cisco Unified CallManager Features and Services Guide

Call Park and Directed Call Park, Cisco Unified CallManager Features and Services Guide

Immediate Divert, Cisco Unified CallManager Features and Services Guide

Quality Report Tool, Cisco Unified CallManager Features and Services Guide

Additional Cisco Unified CallManager Documentation

Phone administration documentation that supports your phone model and this version of Cisco Unified CallManager

Cisco Unified IP Phone user documentation, including Getting Started documents

Firmware release notes for your phone model

Bulk Administration Tool User Guide

Cisco Unified CallManager Assistant User Guide

Cisco IP Communicator Administration Guide