Device
Information
|
Active Load
ID
|
This field
displays the name of the active firmware load if the
Cisco Unified IP
Phone has registered with
Cisco Unified Communications
Manager.
In some
cases, the Active Load ID field displays
"Unknown." For example,
Cisco Unified Communications
Manager Administration might display
"Unknown" in the Active Load ID field for any of the following
circumstances:
- For SCCP phones, when the
phone is a
Cisco Unified IP
Phone 7940 (SCCP), 7960 (SCCP), or 7985 (SCCP), because these phone
models do not support the necessary version of SCCP.
- For SCCP and SIP phones, when
the phone is any third-party phone.
- When
Cisco Unified Communications
Manager cannot determine the status of the phone.
|
Device is
Active
|
The Device
Is Active message in the Phone Configuration window in
Cisco Unified Communications
Manager Administration displays when a phone consumes device license
units and when a phone can register with Cisco Unified CM.
For a phone that uses a real MAC address, not the dummy MAC address that is created via BAT, the Device Is Active message
displays, which indicates that the phone uses device license units and can register with Cisco Unified Communications Manager.
For a phone that uses the dummy MAC address that is created via BAT, the Device Is Active message does not display. If you
manually convert the dummy MAC address to a real MAC address in the Phone Configuration window, the Device Is Active message
displays after you save the configuration; this ensures that the phone can register with Cisco Unified Communications Manager and that licensing consumes device license units for the phone.
|
Device
Trust Mode
|
Select
whether the device is trusted or not trusted. You can configure this setting
for analog phones using SCCP, and for some third-party endpoints.
|
MAC Address
|
Enter the
Media Access Control (MAC) address that identifies
Cisco Unified IP
Phones (hardware phones only). Make sure that the value comprises 12
hexadecimal characters.
For
information on how to access the MAC address for your phone, see the
Cisco Unified IP
Phone Administration Guide for
Cisco Unified Communications
Manager that supports your phone model.
Cisco VG248
Analog Phone Gateway:
The MAC
address for the Cisco VG248 gateway specifies the endpoint from the Gateway
Configuration window of
Cisco Unified Communications
Manager Administration.
Only one MAC
address exists for the Cisco VG248 Analog Phone Gateway. All 48 ports share the
same MAC address. Cisco Unified CM requires unique MAC addresses for all
devices.
Cisco Unified Communications
Manager converts the MAC address for each device by
-
Dropping
the first two digits of the MAC address
-
Shifting
the MAC address two places to the left
-
Adding
the two-digit port number to the end of the MAC address (to the right of the
number)
EXAMPLEMAC Address for the Cisco VG248 is
000039A44218
the MAC address for registered port 12 in the
Cisco Unified Communications Manager is0039A4421812
Cisco VG224
Analog Phone Gateway:
You can
configure a Cisco VG224 gateway as an MGCP gateway or an SCCP gateway. When it
is configured as an SCCP gateway, it can have 24 analog phone endpoints. When
it is configured this way, it functions similarly to an IOS SCCP gateway. The
MAC address for each individual phone gets calculated by using a formula that
considers the slot position, subunit, port, and the last 10 characters of the
original MAC address.
|
Device Name
|
Enter a name
to identify software-based telephones, H.323 clients, and CTI ports.
For device names that are not based on a MAC address, as a general rule, you can enter 1 to 15 characters comprised of alphanumeric
characters (a-z, A-D, 0-9). In most cases you can also use dot (.), dash (-), and underscore (_).
Tip
|
Because
the rules for the device name field depend on the device type, Cisco recommends
that you see the product documentation to determine which character set is
valid for your device, as well as the number of characters allowed. For
example, when you configure the device name for the
Cisco Unified Personal
Communicator, make sure that the name starts with UPC.
|
Note
|
For Cisco Spark Remote Devices (Cisco Spark-RDs), you can enter 1 to 32 characters comprising of alphanumeric characters like
a-z, A-D, 0-9 and the following special characters: dot (.), dash (-), and underscore (_).
|
Note
|
Ensure
that the device name of a
Cisco Unified Mobile
Communicator does not exceed 15 characters. If the device name of a
Cisco Unified Mobile
Communicator exceeds 15 characters, migration of this device will
fail upon upgrade to a different release of
Cisco Unified Communications
Manager. If an existing
Cisco Unified Mobile
Communicator device name specifies a longer name, shorten the device
name to 15 or fewer characters.
Cisco Unified Mobile
Communicator supports dual mode phones. The preceding limit of 15
characters also applies to
Cisco Unified Mobile
Communicator dual mode. When the MI for a dual mode phone is longer
than 15 characters, the cellular network rejects the phone registration.
|
|
Description
|
Identify the
purpose of the device. You can enter the user name (such as John Smith) or the
phone location (such as Lobby) in this field.
For Cisco
VG248 gateways, begin the description with
VGC<mac address>.
The description can include
up to 50 characters in any language, but it cannot include double-quotes ("),
percentage sign (%), ampersand (&), back-slash (\), or angle brackets
(<>).
|
Device Pool
|
Choose the
device pool to which you want this phone assigned. The device pool defines sets
of common characteristics for devices, such as region, date/time group, and
softkey template.
|
Common
Device Configuration
|
Choose the
common device configuration to which you want this phone assigned. The common
device configuration includes the attributes (services or features) that are
associated with a particular user. Configure the common device in the Common
Device Configuration window.
To see the
common device configuration settings, click the View Details link.
|
Phone Button
Template
|
Choose the
appropriate phone button template. The phone button template determines the
configuration of buttons on a phone and identifies which feature (line, speed
dial, and so on) is used for each button.
Cisco
Unified CM does not make this field available for H.323 clients or CTI ports.
|
Saving or Applying a configuration change
|
The following icons and buttons are found in the Configuration windows of the Cisco Unified Communications Manager Administration GUI to Save or Apply configuration changes:
-
Save—Saves the current record.
-
Reset—Opens a popup window that offers the following choices:
-
Reset—Shuts down the device and then restarts it.
-
Restart—Restarts the device without shutting it down.
-
Close—Closes the popup window without taking any action.
-
Apply Config—When you change the configuration settings of a record, you may receive a message that directs you to click the
Apply Config button to have the changes take effect. When you click the Apply Config button, a popup window advises of the possible actions that will take place when you click OK.
|
Softkey
Template
|
Choose the
appropriate softkey template. The softkey template determines the configuration
of the softkeys on
Cisco Unified IP
Phones. Leave this field blank if the common device configuration
contains the assigned softkey template.
|
Common Phone
Profile
|
From the
drop-down list box, choose a common phone profile from the list of available
common phone profiles.
|
Calling
Search Space
|
From the
drop-down list box, choose the appropriate calling search space (CSS). A
calling search space comprises a collection of partitions that are searched to
determine how a dialed number should be routed. The calling search space for
the device and the calling search space for the directory number get used
together. The directory number CSS takes precedence over the device CSS.
Note
|
When
set to <none>,
Unified CM uses the device mobility calling search
space, which is configured on the device pool.
|
|
AAR
Calling Search Space
|
Choose the
appropriate calling search space for the device to use when it performs
automated alternate routing (AAR). The AAR calling search space specifies the
collection of route partitions that are searched to determine how to route a
collected (originating) number that is otherwise blocked due to insufficient
bandwidth.
|
Media
Resource Group List
|
Choose the
appropriate Media Resource Group List. A Media Resource Group List comprises a
prioritized grouping of media resource groups. An application chooses the
required media resource, such as a Music On Hold server, from the available
media resources according to the priority order that is defined in a Media
Resource Group List.
If you
choose <None>, Cisco Unified CM uses the Media Resource Group List that
is defined in the device pool.
|
User Hold
MOH Audio Source
|
To specify
the audio source that plays when a user initiates a hold action, click the
drop-down arrow and choose an audio source from the list that displays.
If you do
not choose an audio source, Cisco Unified CM uses the audio source that is
defined in the device pool or the system default if the device pool does not
specify an audio source ID.
Note
|
You
define audio sources in the Music On Hold Audio Source Configuration window.
For access, choose
.
|
|
Network
Hold MOH Audio Source
|
To specify
the audio source that is played when the network initiates a hold action, click
the drop-down arrow and choose an audio source from the list that displays.
If you do
not choose an audio source, Cisco Unified CM uses the audio source that is
defined in the device pool or the system default if the device pool does not
specify an audio source ID.
Note
|
You
define audio sources in the Music On Hold Audio Source Configuration window.
For access, choose
.
|
|
Location
|
Use
locations to implement call admission control (CAC) in a centralized
call-processing system. CAC enables you to regulate audio quality and video
availability by limiting the amount of bandwidth that is available for audio
and video calls over links between locations. The location specifies the total
bandwidth that is available for calls to and from this location.
From the
drop-down list box, choose the appropriate location for this
Cisco Unified IP
Phone.
A location
setting of Hub_None means that the locations feature does not keep track of the
bandwidth that this
Cisco Unified IP
Phone consumes. A location setting of Phantom specifies a location
that enables successful CAC across intercluster trunks that use H.323 protocol
or SIP.
To
configure a new location, use the
menu option.
|
AAR Group
|
Choose the
automated alternate routing (AAR) group for this device. The AAR group provides
the prefix digits that are used to route calls that are otherwise blocked due
to insufficient bandwidth. If no AAR group is specified, Cisco Unified CM uses
the AAR group that is associated with Device Pool or Line.
|
User
Locale
|
From the
drop-down list box, choose the locale that is associated with the phone user
interface. The user locale identifies a set of detailed information to support
users, including language and font.
Cisco
Unified CM makes this field available only for phone models that support
localization.
Note
|
If no
user locale is specified,
Cisco Unified Communications Manager uses the user
locale that is associated with the common device configurations.
If the
users require that information be displayed (on the phone) in any language
other than English, verify that the locale installer is installed before
configuring user locale. See the
Cisco Unified
Communications Manager Locale Installer documentation.
|
|
Network
Locale
|
From the
drop-down list box, choose the locale that is associated with the phone. The
network locale contains a definition of the tones and cadences that the phone
in a specific geographic area uses.
Cisco
Unified CM makes this field available only for phone models that support
localization.
Note
|
If no
network locale is specified, Cisco Unified CM uses the network locale that is
associated with the device pool.
If users
require that country-specific tones be played (on the phone), verify that the
locale is installed before configuring the network locale. See the
Cisco Unified
Communications Manager
Locale Installer documentation.
|
|
Built In
Bridge
|
Enable or
disable the built-in conference bridge for the barge feature by using the Built
In Bridge drop-down list box (choose On, Off, or Default).
Note
|
Cisco Unified IP
Phones 7940 and 7960 cannot support two media stream encryptions or
SRTP streams simultaneously. To prevent instability due to this condition, the
system automatically disables the built-in bridge for 7940 and 7960 phones when
the device security mode is set to encrypted.
|
|
Privacy
|
For each
phone that wants Privacy, choose On in the Privacy drop-down list box.
|
Device
Mobility Mode
|
From the
drop-down list box, turn the device mobility feature on or off for this device
or choose Default to use the default device mobility mode. Default setting uses
the value for the Device Mobility Mode service parameter for the device.
Click View
Current Device Mobility Settings to display the current values of these device
mobility parameters:
-
Cisco Unified
Communications Manager Group
- Roaming Device Pool
- Location
- Region
- Network Locale
- AAR Group
- AAR Calling Search Space
- Device Calling Search Space
- Media Resource Group List
- SRST
|
Wireless
LAN Profile Group
|
Select a
wireless LAN profile group from the drop-down list box. You may also click
View Details to display the settings for this
wireless LAN profile group.
Note
|
You can
specify the Wireless LAN Profile Group at the Device Pool level or the
individual phone level.
|
Note
|
This
field does not apply to all phone models.
|
|
Wi-Fi
Hotspot Profile
|
Select a
Wi-Fi Hotspot Profile from the drop-down list box. You may also click
View Details to display the settings for this Wi-Fi
Hotspot Profile.
Note
|
This
field does not apply to all phone models.
|
|
Signaling
Port
|
This field
applies only to H.323 devices. The value designates the H.225 signaling port
that this device uses.
Default
value specifies 1720. Valid values range from 1 to 65535.
|
Video
Capabilities Enabled/disabled
|
This check
box turns video capabilities on and off.
Note
|
This
field does not apply to all phone models.
|
|
Owner User
ID
|
From the
drop-down list box, choose the user ID of the assigned phone user. The user ID
gets recorded in the call detail record (CDR) for all calls made from this
device. Assigning a user ID to the device also moves the device from
"Unassigned Devices" to
"Users" in the License Usage Report.
|
Mobility
User ID
(Dual-mode
phones only)
|
From the
drop-down list box, choose the user ID of the person to whom this dual-mode
phone is assigned.
Note
|
The
Mobility User ID configuration gets used for the Cisco Unified Mobility and
Mobile Voice Access features for dual-mode phones.
The Mobility User Id is taken from the admin page and is the same as Owner User Id.
|
|
Phone
Personalization
|
The Phone
Personalization setting allows you to enable a
Cisco Unified IP
Phone, so it works with Phone Designer, a Cisco Unified
Communications widget that allows a phone user to customize the wallpaper and
ring tones on the phone. From the Phone Personalization drop-down list box,
choose one of the following options:
- Disabled-The user cannot
customize the
Cisco Unified IP
Phone by using Phone Designer.
- Enabled-The user can use
Phone Designer to customize the phone.
- Default-The phone uses the
configuration from the Phone Personalization enterprise parameter if you choose
Default in both the Phone Configuration and Common Phone Profile Configuration
windows. If you choose Default in the Common Phone Profile Configuration window
but not in the Phone Configuration window, the phone uses the configuration
that you specify in the Phone Configuration window.
You must
install and configure Phone Designer, so the phone user can customize the
phone. Before you install and configure Phone Designer, identify which
Cisco Unified IP
Phone models work with Phone Designer, as described in the Phone
Designer documentation. For more information on Phone Designer, see the Phone
Designer documentation.
|
Services
Provisioning
|
From the
drop-down list box, choose how the phone will support the services:
- Internal—The phone uses the
phone configuration file to support the service.
Choose
this option or Both for Cisco-provided default services where the Service URL
has not been updated; that is, the service URL indicates
Application:Cisco/<name of service>; for
example,
Application:Cisco/CorporateDirectory.
Choose
Internal or Both for Cisco-signed Java MIDlets because Cisco-signed Java
MIDlets are provisioned in the configuration file.
-
External URL—Choosing External URL indicates that the phone
ignores the services in the phone configuration file and retrieves the services
from a Service URL.
If you
configured a custom Service URL for a service, including a Cisco-provided
default service, you must choose either External URL or Both; if you choose
Internal in this case, the services that are associated with the custom URLs do
not work on the phone.
- Both—Choosing Both
indicates that the phone support both the services that are defined in the
configuration file and external applications that are retrieved from service
URLs.
|
Primary
Phone
|
Choose the
physical phone that will be associated with the application, such as IP
communicator or Cisco Unified Personal Communicator. When you choose a primary
phone, the application consumes fewer device license units and is considered an
"adjunct" license (to the primary phone).
|
Wait for
Far End H.245 Terminal Capability Set
|
This field
applies only to H.323 devices.
This check
box specifies that Cisco Unified CM waits to receive the far-end H.245 Terminal
Capability Set before it sends its H.245 Terminal Capability Set. By default,
the system checks this check box. To specify that Cisco Unified CM should
initiate capabilities exchange, uncheck this check box.
|
Phone Load
Name
|
Enter the
custom software for the
Cisco Unified IP
Phone.
The value
that you enter overrides the default value for the current model.
For more
information about
Cisco Unified IP
Phone software and configuration, see the
Cisco Unified IP
Phone Administration Guide for
Cisco Unified
Communications Manager, which is specific to the phone model and
Unified CM release.
|
Single
Button Barge
|
From the
drop-down list box, enable or disable the Single Button Barge/cBarge feature
for this device or choose Default to use the service parameter setting.
- Off—This setting disables
the Single Button Barge/cBarge feature; however, the regular Barge or cBarge
features will still work.
- Barge—This setting enables
the Single Button Barge feature.
- CBarge—This setting enables
the Single Button cBarge feature.
- Default—Uses the Single
Button Barge/cBarge setting that is in the service parameter.
|
Join
Across Lines
|
From the
drop-down list box, enable or disable the Join Across Lines feature for this
device or choose Default to use the service parameter setting.
- Off—This setting disables
the Join Across Lines feature.
- On—This setting enables the
Join Across Lines feature.
- Default—This setting uses
the Join Across Lines setting that is in the service parameter.
|
Use
Trusted Relay Point
|
From the
drop-down list box, enable or disable whether Cisco Unified CM inserts a
trusted relay point (TRP) device with this media endpoint. Choose one of the
following values:
- Default—If you choose this
value, the device uses the Use Trusted Relay Point setting from the common
device configuration with which this device associates.
- Off—Choose this value to
disable the use of a TRP with this device. This setting overrides the Use
Trusted Relay Point setting in the common device configuration with which this
device associates.
- On—Choose this value to
enable the use of a TRP with this device. This setting overrides the Use
Trusted Relay Point setting in the common device configuration with which this
device associates.
A Trusted
Relay Point (TRP) device designates an MTP or transcoder device that is labeled
as Trusted Relay Point.
Cisco
Unified CM places the TRP closest to the associated endpoint device if more
than one resource is needed for the endpoint (for example, a transcoder or
RSVPAgent).
If both
TRP and MTP are required for the endpoint, TRP gets used as the required MTP.
If both
TRP and RSVPAgent are needed for the endpoint, Cisco Unified CM first tries to
find an RSVPAgent that can also be used as a TRP.
If both
TRP and transcoder are needed for the endpoint, Cisco Unified CM first tries to
find a transcoder that is also designated as a TRP.
|
BLF
Audible Alert Setting (Phone Idle)
|
This
setting determines the busy lamp field (BLF) audible alert setting when no
current call exists on the BLF DN:
- On—An audible alert sounds.
- Off—No audible alert
sounds.
- Default—The configuration
in the Service Parameters Configuration window determines the alert option.
|
BLF
Audible Alert Setting (Phone Busy)
|
This
setting determines the BLF audible alert setting when at least one active call
exists on the BLF DN, but no call pickup alerts exist:
- On—An audible alert sounds.
- Off—No audible alert
sounds.
- Default—The configuration
in the Service Parameters Configuration window determines the alert option.
|
Always Use
Prime Line
|
From the
drop-down list box, choose one of the following options:
- Off—When the phone is idle
and receives a call on any line, the phone user answers the call from the line
on which the call is received.
- On—When the phone is idle
(off hook) and receives a call on any line, the primary line gets chosen for
the call. Calls on other lines continue to ring, and the phone user must select
those other lines to answer these calls.
- Default—Cisco Unified Communications Manager uses the
configuration from the Always Use Prime Line service parameter, which supports
the Cisco CallManager service.
|
Always Use
Prime Line for Voice Message
|
From the
drop-down list box, choose one of the following options:
- On—If the phone is idle,
the primary line on the phone becomes the active line for retrieving voice
messages when the phone user presses the Messages button on the phone.
- Off—If the phone is idle,
pressing the Messages button on the phone automatically dials the
voice-messaging system from the line that has a voice message. Cisco Unified CM
always selects the first line that has a voice message. If no line has a voice
message, the primary line gets used when the phone user presses the Messages
button.
- Default—Cisco Unified CM
uses the configuration from the Always Use Prime Line for Voice Message service
parameter, which supports the Cisco CallManager service.
|
Geolocation
|
From the
drop-down list box, choose a geolocation.
You can
choose the Unspecified geolocation, which designates that this device does not
associate with a geolocation.
You can
also choose a geolocation that has been configured with the
menu option.
|
Feature
Control Policy
|
From the
drop-down list box, you can choose a feature control policy that has already
been configured in the Feature Control Policy configuration window
().
|
Retry
Video Call as Audio
|
This check
box applies only to video endpoints that receive a call. If this phone receives
a call that does not connect as video, the call tries to connect as an audio
call.
By
default, the system checks this check box to specify that this device should
immediately retry a video call as an audio call (if it cannot connect as a
video call) prior to sending the call to call control for rerouting.
If you
uncheck this check box, a video call that fails to connect as video does not
try to establish as an audio call. The call then fails to call control, and
call control routes the call via automatic alternate routing (AAR) and/or
route/hunt list.
|
Ignore
Presentation Indicators (internal calls only)
|
Check this
check box to configure call display restrictions on a call-by-call basis. When
this check box is checked, Cisco Unified CM ignores any presentation
restriction that is received for internal calls.
Use this
configuration in combination with the calling line ID presentation and
connected line ID presentation configuration at the translation pattern level.
Together, these settings allow you to configure call display restrictions to
selectively present or block calling and/or connected line display information
for each call.
See the
translation configuration settings for more information about the calling line
ID presentation and the connected line ID presentation parameters.
|
Allow
Control of Device from CTI
|
Check this
check box to allow CTI to control and monitor this device.
If the
associated directory number specifies a shared line, the check box should be
enabled as long as at least one associated device specifies a combination of
device type and protocol that CTI supports.
|
Logged
into Hunt Group
|
This check
box, which gets checked by default for all phones, indicates that the phone is
currently logged in to a hunt list (group). When the phone gets added to a hunt
list, the administrator can log the user in or out by checking (and unchecking)
this check box.
Users use
the softkey on the phone to log their phone in or out of the hunt list.
|
Remote
Device
|
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 CM to allocate a buffer for the phone device when it
registers and to bundle SCCP messages to the phone.
Tip
|
Because
this feature consumes resources, be sure to check this check box only when you
are experiencing signaling delays for phones that are running SCCP. Most users
do not require this option.
|
Cisco
Unified CM sends the bundled messages to the phone when the station buffer is
full, as soon as it receives a media-related message, or when the Bundle
Outbound SCCP Messages timer expires.
To specify
a setting other than the default setting (100 msec) for the Bundle Outbound
SCCP Messages timer, configure a new value in the Service Parameters
Configuration window for the Cisco CallManager service. Although 100 msec
specifies the recommended setting, you may enter 15 msec to 500 msec.
The phone
must support SCCP version 9 to use this option. The following phones do not
support SCCP message optimization:
Cisco Unified IP
Phone 7935/7936. This feature may require a phone reset after update.
|
Protected
Device
|
Check this
check box to designate a phone as protected, which enables the phone to play a
2-second tone to notify the user when a call is encrypted and both phones are
configured as protected devices. The tone plays for both parties when the call
is answered. The tone does not play unless both phones are protected and the
call occurs over encrypted media.
Checking
this check box represents only one of several configuration requirements for
the secure indication tone to play. For a detailed description of the secure
indication tone feature and the configuration requirements, see the
Cisco Unified
Communications Manager Security Guide
.
If you
check this check box and the system determines that the call is not encrypted,
the phone plays nonsecure indication tone to alert the user that the call is
not protected.
|
Hotline
Device
|
Check this
check box to make this device a Hotline device. Hotline devices can only
connect to other Hotline devices. This feature is an extension of PLAR, which
configures a phone to automatically dial one directory number when it goes
off-hook. Hotline provides additional restrictions that you can apply to
devices that use PLAR.
To
implement Hotline, you must also create a softkey template without
supplementary service softkeys, and apply it to the Hotline device.
|
Require
off-premise location
|
Check this
check box if the device inserted requires off-premise location update upon
registration. Off-premise location update is required when the device location
cannot be detected automatically by Cisco Emergency Responder.
Check this
check box only for remote or mobile devices that change locations frequently.
|
|
Caller ID For Calls From
This Phone
|
Calling
Party Transformation CSS
for Calls from this Phone
|
From the drop-down list
box, choose the calling search space (CSS) that contains the calling party
transformation pattern that you want to apply on the calling number when this
phone initiates a call.
Cisco Unified CM transforms
the calling party using the digit transformations configured on the matching
calling party transformation pattern when this phone initiates a call. This
setting allows you to transform the calling party number before Cisco Unified
CM routes the call. For example, a transformation pattern can change a phone
extension to an E.164 number. This setting is generally configured when a user
dials using a URI instead of digits. Cisco Unified CM allows calling party
transformations on various patterns when dialing using digits, this setting
provides similar transformation provision even when dialing using a URI.
|
Use Device
Pool Calling Party Transformation CSS
(Caller ID for Calls from
this Phone)
|
Check this check box to use
the Calling Party Transformation CSS configured at the device pool to which
this phone belongs to transform the calling party for calls initiated from this
phone. At the device pool, Calling Party Transformation CSS present under Phone
Settings is used to transform the calling party for calls initiated from this
phone.
Leave this check box
unchecked to apply the Calling Party Transformation CSS setting that appears in
this configuration window.
|
Remote Number
Transformation
|
Calling
Party Transformation CSS
for Remote Number
|
From the drop-down list
box, choose the calling search space (CSS) that contains the calling party
transformation pattern that you want to apply on the remote calling number for
calls received on this phone. Cisco Unified CM transforms the remote calling
number using the digit transformations configured on the matching calling party
transformation pattern before presenting it to this device. For example, a
transformation pattern can change remote number in E.164 format to a localized
version.
This setting can be used to
transform the remote connected number for direct calls initiated from this
phone. This setting can also be used to transform remote connected number post
feature invocation irrespective of the direction of the call. The
transformation of a remote connected number is controlled using the service
parameter “Apply Transformations On Remote Number” (present under advanced
section of Cisco Call Manager service). Refer to this parameter description for
more details.
|
Use Device
Pool Calling Party Transformation CSS
for Remote Number (Device
Mobility Related Information)
|
Check this check box to
apply the Calling Party Transformation CSS configured at the device pool to
which this phone belongs to transform the remote calling and remote connected
number. At the device pool, Calling Party Transformation CSS present under
Device Mobility Related Information section is used to transform remote calling
and remote connected number.
Leave this check box
unchecked to apply the Calling Party Transformation CSS setting that appears in
this configuration window for transforming the remote number.
|
Protocol
Specific Information
|
Packet
Capture Mode
|
This
setting exists for troubleshooting encryption only; packet capturing may cause
high CPU usage or call-processing interruptions. Choose one of the following
options from the drop-down list box:
- None—This option, which
serves as the default setting, indicates that no packet capturing is occurring.
After you complete packet capturing, configure this setting.
- Batch Processing Mode—Cisco
Unified CM writes the decrypted or nonencrypted messages to a file, and the
system encrypts each file. On a daily basis, the system creates a new file with
a new encryption key. Cisco Unified CM, which stores the file for seven days,
also stores the keys that encrypt the file in a secure location. Cisco Unified
CM stores the file in the PktCap virtual directory. A single file contains the
time stamp, source IP address, source IP port, destination IP address, packet
protocol, message length, and the message. The TAC debugging tool uses HTTPS,
administrator username and password, and the specified day to request a single
encrypted file that contains the captured packets. Likewise, the tool requests
the key information to decrypt the encrypted file.
For more
information on packet capturing, see the
Troubleshooting
Guide for
Cisco Unified
Communications Manager
.
|
Packet
Capture Duration
|
This
setting exists for troubleshooting encryption only; packet capturing may cause
high CPU usage or call-processing interruptions.
This field
specifies the maximum number of minutes that is allotted for one session of
packet capturing. The default setting equals 0, although the range exists from
0 to 300 minutes.
To
initiate packet capturing, enter a value other than 0 in the field. After
packet capturing completes, the value, 0, displays.
For more
information on packet capturing, see the
Cisco Unified
Communications Manager
Troubleshooting
Guide
.
|
SRTP
Allowed
|
As this
check box explains, if this flag is checked, IPSec needs to be configured in
the network to provide end-to-end security. Failure to do so will expose keys
and other information.
For more
information on SRTP encryption, see the
Cisco Unified
Communications Manager Security Guide
.
|
Presence
Group
|
Configure
this field with the Presence feature.
From the
drop-down list box, choose a Presence group for the end user. The selected
group specifies the devices, end users, and application users that can monitor
this directory number.
The
default value for Presence Group specifies Standard Presence group, configured
with installation. Presence groups that are configured in
Cisco Unified
Communications Manager Administration also appear in the drop-down
list box.
Presence
authorization works with presence groups to allow or block presence requests
between groups.
|
Device
Security Profile
|
Choose the
security profile to apply to the device.
You must
apply a security profile to all phones that are configured in
Cisco Unified
Communications Manager Administration.
Installing Cisco Unified
Communications Manager
provides a set of predefined, nonsecure security
profiles for auto-registration. To enable security features for a phone, you
must configure a new security profile for the device type and protocol and
apply it to the phone. If the phone does not support security, choose a
nonsecure profile.
To
identify the settings that the profile contains, choose
.
Note
|
The CAPF
settings that are configured in the profile relate to the Certificate Authority
Proxy Function settings that display in the Phone Configuration window. You
must configure CAPF settings for certificate operations that involve
manufacturer-installed certificates (MICs) or locally significant certificates
(LSC). See the
Cisco Unified
Communications Manager Security Guide for more information about how
CAPF settings that you update in the phone configuration window affect security
profile CAPF settings.
|
|
SIP Dial
Rules
|
If
required, choose the appropriate SIP dial rule. SIP dial rules provide local
dial plans for
Cisco Unified IP
Phones 7905, 7912, 7940, and 7960, so users do not have to press a
key or wait for a timer before the call gets processed.
Leave the
SIP Dial Rules field set to <None> if you do not want dial rules to apply
to the IP phone that is running SIP. This means that the user must use the Dial
softkey or wait for the timer to expire before the call gets processed.
|
MTP
Preferred Originating Codec
|
From the
drop-down list box, choose the codec to use if a media termination point is
required for SIP calls.
|
Rerouting
Calling Search Space
|
From the
drop-down list box, choose a calling search space to use for rerouting.
The
rerouting calling search space of the referrer gets used to find the route to
the refer-to target. When the Refer fails due to the rerouting calling search
space, the Refer Primitive rejects the request with the
"405
Method Not Allowed" message.
The
redirection (3xx) primitive and transfer feature also uses the rerouting
calling search space to find the redirect-to or transfer-to target.
|
Out-of-Dialog Refer Calling Search Space
|
From the
drop-down list box, choose an out-of-dialog refer calling search space.
Cisco
Unified CM uses the out-of-dialog (OOD) Refer Authorization calling search
space (CSS) to authorize the SIP out-of-dialog Refer. The administrator can
restrict the use of out-of-dialog Refer by configuring the OOD CSS of the
Referrer. Refer Primitive rejects the OOD Refer request with a
"403
Forbidden" message.
|
SUBSCRIBE
Calling Search Space
|
Supported
with the Presence feature, the SUBSCRIBE calling search space determines how
Cisco Unified CM routes presence requests that come from the phone. This
setting allows you to apply a calling search space separate from the
call-processing search space for presence (SUBSCRIBE) requests for the phone.
From the
drop-down list box, choose the SUBSCRIBE calling search space to use for
presence requests for the phone. All calling search spaces that you configure
in
Cisco Unified
Communications Manager Administration display in the SUBSCRIBE
Calling Search Space drop-down list box.
If you do
not select a different calling search space for the end user from the drop-down
list, the SUBSCRIBE calling search space defaults to None.
To
configure a SUBSCRIBE calling search space specifically for this purpose, you
configure a calling search space as you do all calling search spaces.
|
Outbound
Call Rollover
|
Use this
setting for the
Cisco Unified IP
Phone 7931.
- No Rollover—Conference and
transfer will not work in this mode. If a user attempts to use either of these
features, the phone status displays as
"Error
Pass Limit." Choose this setting only if you need to support CTI
applications.
- Rollover Within Same
DN—Conferences and call transfers complete by using the same directory number
(on different lines). For example, consider a phone that has directory number
1506 that is assigned to both Line 6 and 7. The user has an active call on Line
6 and decides to transfer the call. When the user presses the Transfer button,
the call on Line 6 gets placed on hold, and a new call initiates on Line 7 to
complete the transfer.
- Rollover to any
line—Conferences and call transfers complete by using a different directory
number and line than the original call. For example, consider a phone that has
directory number 1507 assigned to Line 8 and directory number 1508 assigned to
Line 9. The user has an active call on Line 8 and decides to transfer the call.
When the user presses the Transfer button, the call on Line 8 gets placed on
hold, and a new call initiates on Line 9 to complete the transfer.
|
SIP
Profile
|
Choose the
default SIP profile or a specific profile that was previously created. SIP
profiles provide specific SIP information for the phone such as registration
and keepalive timers, media ports, and do not disturb control.
|
Digest
User
|
Choose an
end user that you want to associate with the phone for this setting that is
used with digest authentication (SIP security).
Ensure
that you configured digest credentials for the user that you choose, as
specified in the End User Configuration window.
After you
save the phone configuration and apply the configuration update to the phone,
the digest credentials for the user get added to the phone configuration file.
For more
information on digest authentication, see the
Cisco Unified
Communications Manager Security Guide
.
|
Media
Termination Point Required
|
Use this
field to indicate whether a media termination point is used to implement
features that H.323 does not support (such as hold and transfer).
Check the
Media Termination Point Required check box if you want to use an MTP to
implement features. Uncheck the Media Termination Point Required check box if
you do not want to use an MTP to implement features.
Use this
check box only for H.323 clients and those H.323 devices that do not support
the H.245 empty capabilities set or if you want media streaming to terminate
through a single source.
If you
check this check box to require an MTP and this device becomes the endpoint of
a video call, the call will be audio only.
|
Unattended
Port
|
Check this
check box to indicate an unattended port on this device.
|
Require
DTMF Reception
|
For phones
that are running SIP and SCCP, check this check box to require DTMF reception
for this phone.
Note
|
In
configuring
Cisco Unified
Mobility features, when using intercluster DNs as remote destinations
for an IP phone via SIP trunk (either intercluster trunk [ICT] or gateway),
check this check box so that DTMF digits can be received out of band, which is
crucial for Enterprise Feature Access midcall features.
|
|
RFC2833
Disabled
|
For phones
that are running SCCP, check this check box to disable RFC2833 support.
|
Certification Authority Proxy Function (CAPF) Information
|
Certificate Operation
|
From the
drop-down list box, choose one of the following options:
For more
information on CAPF operations, see the
Cisco Unified
Communications Manager Security Guide
.
|
Authentication Mode
|
This field
allows you to choose the authentication method that the phone uses during the
CAPF certificate operation.
From the
drop-down list box, choose one of the following options:
- By Authentication
String—Installs/upgrades, deletes, or troubleshoots a locally significant
certificate only when the user enters the CAPF authentication string on the
phone.
- By Null String—
Installs/upgrades, deletes, or troubleshoots a locally significant certificate
without user intervention.
This
option provides no security; Cisco strongly recommends that you choose this
option only for closed, secure environments.
- By Existing Certificate
(Precedence to LSC)—Installs/upgrades, deletes, or troubleshoots a locally
significant certificate if a manufacture-installed certificate (MIC) or locally
significant certificate (LSC) exists in the phone. If a LSC exists in the
phone, authentication occurs via the LSC, regardless whether a MIC exists in
the phone. If a MIC and LSC exist in the phone, authentication occurs via the
LSC. If a LSC does not exist in the phone, but a MIC does exist, authentication
occurs via the MIC.
Before
you choose this option, verify that a certificate exists in the phone. If you
choose this option and no certificate exists in the phone, the operation fails.
At any
time, the phone uses only one certificate to authenticate to CAPF even though a
MIC and LSC can exist in the phone at the same time. If the primary
certificate, which takes precedence, becomes compromised for any reason, or, if
you want to authenticate via the other certificate, you must update the
authentication mode.
- By Existing Certificate
(Precedence to MIC)—Installs, upgrades, deletes, or troubleshoots a locally
significant certificate if a LSC or MIC exists in the phone. If a MIC exists in
the phone, authentication occurs via the MIC, regardless whether a LSC exists
in the phone. If a LSC exists in the phone, but a MIC does not exist,
authentication occurs via the LSC.
Before
you choose this option, verify that a certificate exists in the phone. If you
choose this option and no certificate exists in the phone, the operation fails.
Note
|
The CAPF
settings that are configured in the Phone Security Profile window interact with
the CAPF parameters that are configured in the Phone Configuration window.
|
|
Authentication String
|
If you
chose the By Authentication String option in the Authentication Mode drop-down
list box, this field applies. Manually enter a string or generate a string by
clicking the Generate String button. Ensure that the string contains 4 to 10
digits.
To
install, upgrade, delete, or troubleshoot a locally significant certificate,
the phone user or administrator must enter the authentication string on the
phone.
|
Key Size
(Bits)
|
For this
setting that is used for CAPF, choose the key size for the certificate from the
drop-down list box. The default setting equals 1024. Other options include 512
and 2048.
If you
choose a higher key size than the default setting, the phones take longer to
generate the entropy that is required to generate the keys. Key generation,
which is set at low priority, allows the phone to function while the action
occurs. Depending on the phone model, you may notice that key generation takes
up to 30 or more minutes to complete.
Note
|
The CAPF
settings that are configured in the Phone Security Profile window interact with
the CAPF parameters that are configured in the Phone Configuration window.
|
|
Operation
Completes by
|
This
field, which supports the Install/Upgrade, Delete, and Troubleshoot Certificate
Operation options, specifies the date and time in which you must complete the
operation.
The values
that display apply for the publisher database server.
|
Certificate Operation Status
|
This field
displays the progress of the certificate operation; for example, <operation
type> pending, failed, or successful, where operating type equals the
Install/Upgrade, Delete, or Troubleshoot Certificate Operation options. You
cannot change the information that displays in this field.
|
Expansion
Module Information
(The
following fields only display when the expansion modules are supported by the
phone.)
|
Module 1
|
Choose the
appropriate expansion module or none.
|
Module 1
Load Name
|
Enter the
custom software for the appropriate expansion module, if applicable.
The value
that you enter overrides the default value for the current model. Ensure the
firmware load matches the module load.
|
Module 2
|
Choose the
appropriate expansion module or none.
|
Module 2
Load Name
|
Enter the
custom software for the second expansion module, if applicable.
The value
that you enter overrides the default value for the current model. Ensure the
firmware load matches the module load.
|
Module 3
|
Choose the
appropriate expansion module or none.
|
Module 3
Load Name
|
Enter the
custom software for the appropriate expansion module, if applicable.
The value
that you enter overrides the default value for the current model. Ensure the
firmware load matches the module load.
|
External
Data Locations Information (Leave blank to use default)
|
Information
|
Enter the
location (URL) of the help text for the information (i) button. Leave this
field blank to accept the default setting.
|
Directory
|
Enter the
server from which the phone obtains directory information. Leave this field
blank to accept the default setting.
Note
|
If you
set a Secured Directory URL enterprise parameter in the Enterprise Parameters
Configuration window, that value overwrites the value of this field.
|
|
Messages
|
Leave this
field blank (not used by
Cisco Unified
Communications Manager).
|
Services
|
Enter the
location (URL) for IP phone services.
|
Authentication Server
|
Enter the
URL that the phone uses to validate requests that are made to the phone web
server. If you do not provide an authentication URL, the advanced features on
the
Cisco Unified IP
Phone that require authentication will not function.
By default, this URL
accesses a Cisco Unified Communications Self Care Portal window that was
configured during installation.
Leave this
field blank to accept the default setting.
|
Proxy
Server
|
Enter the
host and port (for example, proxy.cisco.com:80) that are used to proxy HTTP
requests for access to non-local host addresses from the phone HTTP client.
The rule
contains two parts for when to use the proxy server parameter:
-
The
hostname contains a
"."
-
The
hostname specifies an IP address in any form.
If you do
not configure this URL, the phone attempts to connect directly to the URL.
To accept
the default setting, leave this field blank.
|
Idle
|
Enter the
URL that displays on the
Cisco Unified IP
Phone display when the phone has not been used for the time that is
specified in Idle Timer field. For example, you can display a logo on the LCD
when the phone has not been used for 5 minutes.
To accept
the default setting, leave this field blank.
|
Idle Timer
(seconds)
|
Enter the
time (in seconds) that you want to elapse before the URL that is specified in
the Idle field displays.
To accept
the value of the Idle URL Timer enterprise parameter, leave this field blank.
|
Secure
Authentication URL
|
Enter the
secure URL that the phone uses to validate requests that are made to the phone
web server.
Note
|
If you
do not provide a Secure Authentication URL, the device uses the nonsecure URL.
If you provide both a secure URL and a nonsecure URL, the device chooses the
appropriate URL, based on its capabilities.
|
By default, this URL
accesses a Cisco Unified Communications Self Care Portal window that was
configured during installation.
Leave this
field blank to accept the default setting.
Maximum
length: 255
|
Secure
Directory URL
|
Enter the
secure URL for the server from which the phone obtains directory information.
This parameter specifies the URL that secured
Cisco Unified IP
Phones use when you press the Directory button.
Note
|
If you
do not provide a Secure Directory URL, the device uses the nonsecure URL. If
you provide both a secure URL and a nonsecure URL, the device chooses the
appropriate URL, based on its capabilities.
|
Leave this
field blank to accept the default setting.
Maximum
length: 255
|
Secure
Idle URL
|
Enter the
secure URL for the information that displays on the
Cisco Unified IP
Phone display when the phone is idle, as specified in Idle Timer
field. For example, you can display a logo on the LCD when the phone has not
been used for 5 minutes.
Note
|
If you
do not provide a Secure Idle URL, the device uses the nonsecure URL. If you
provide both a secure URL and a nonsecure URL, the device chooses the
appropriate URL, based on its capabilities.
|
To accept
the default setting, leave this field blank.
Maximum
length: 255
|
Secure
Information URL
|
Enter the
secure URL for the server location where the
Cisco Unified IP
Phone can find help text information. This information displays when
the user presses the information (i) button or the question mark (?) button.
Note
|
If you
do not provide a Secure Information URL, the device uses the nonsecure URL. If
you provide both a secure URL and a nonsecure URL, the device chooses the
appropriate URL, based on its capabilities.
|
To accept
the default setting, leave this field blank.
Maximum
length: 255
|
Secure
Messages URL
|
Enter the
secure URL for the messages server. The
Cisco Unified IP
Phone contacts this URL when the user presses the Messages button.
Note
|
If you
do not provide a Secure Messages URL, the device uses the nonsecure URL. If you
provide both a secure URL and a nonsecure URL, the device chooses the
appropriate URL, based on its capabilities.
|
To accept
the default setting, leave this field blank.
Maximum
length: 255
|
Secure
Services URL
|
Enter the
secure URL for
Cisco Unified IP
Phone services. The is the location that the secure
Cisco Unified IP
Phone contacts when the user presses the Services button.
Note
|
If you
do not provide a Secure Services URL, the device uses the nonsecure URL. If you
provide both a secure URL and a nonsecure URL, the device chooses the
appropriate URL, based on its capabilities.
|
To accept
the default setting, leave this field blank.
Maximum
length: 255
|
Extension
Information
|
Enable
Extension Mobility
|
Check this
check box if this phone supports extension mobility.
|
Log Out
Profile
|
This
drop-down list box specifies the device profile that the device uses when no
one is logged in to the device by using
Cisco Extension
Mobility. You can choose either Use Current Device Settings or one of
the specific configured profiles that are listed.
If you
select a specific configured profile, the system retains a mapping between the
device and the login profile after the user logs out. If you select Use Current
Device Settings, no mapping gets retained.
|
Log In
Time
|
This field
remains blank until a user logs in. When a user logs in to the device by using
Cisco Extension
Mobility, the time at which the user logged in displays in this
field.
|
Log Out
Time
|
This field
remains blank until a user logs in. When a user logs in to the device by using
Cisco Extension
Mobility, the time at which the system will log out the user displays
in this field.
|
Configuration File Encryption Symmetric Key Information
|
Symmetric
Key
|
Enter a
string of hexadecimal characters that you want to use for the symmetric key.
Valid characters include numerals, 0-9, and upper/lower case characters, A-F
(or a-f).
Make sure
that you enter the correct bits for the key size; otherwise, Cisco Unified CM
rejects the value. Cisco Unified CM supports the following key sizes:
-
Cisco Unified IP
Phones 7905 and 7912 (SIP only)—256 bits
-
Cisco Unified IP
Phones 7940 and 7960 (SIP only)—128 bits
Use this
string for one-time use only. Every time that you update the configuration
settings, you must generate a new key before you apply the configuration
changes to the phone.
For more
information on symmetric key operations for encrypted configuration file
downloads, see the
Cisco Unified
Communications Manager Security Guide
.
|
Generate
String
|
If you
want
Cisco Unified
Communications Manager Administration to generate a hexadecimal
string for you, click the Generate String button.
|
Revert to
Database Value
|
If you
want to restore the value that exists in the database, click this button. This
button proves useful if you enter an error in the Symmetric Key field before
you save the configuration.
|
H.323
Information
|
Outgoing
Caller ID Pattern
|
For
outgoing calls to the H.323 Client, enter the pattern, from 0 to 24 digits,
that you want to use for caller ID.
|
Calling
Party Selection
|
Choose the
directory number that is sent on an outbound call to the H.323 Client.
The
following options specify which directory number is sent:
- Originator—Send the
directory number of the calling device.
- First Redirect Number—Send
the directory number of the redirecting device.
- Last Redirect Number—Send
the directory number of the last device to redirect the call.
- First Redirect Number
(External)—Send the external directory number of the redirecting device.
- Last Redirect Number
(External)—Send the external directory number of the last device to redirect
the call.
|
Calling
Party Presentation
|
Choose
whether the Cisco Unified CM transmits or blocks caller ID.
If you
want Cisco Unified CM to send caller ID, choose Allowed.
If you do
not want Cisco Unified CM to send caller ID, choose Restricted.
Default
specifies that caller ID does not get sent.
|
Display IE
Delivery
|
This check
box enables delivery of the display information element (IE) in SETUP and
CONNECT messages for the calling and called party name delivery service.
The
default setting checks this check box.
|
Redirecting Number IE Delivery Outbound
|
Check this
check box to indicate the first redirecting number and the redirecting reason
of the call when the call is forwarded. (The UUIE part of the outgoing SETUP
message from the Cisco Unified CM includes the Redirecting Number IE.)
Uncheck
the check box to exclude the first redirecting number and the redirecting
reason from the outgoing SETUP message.
You use
Redirecting Number IE for voice-messaging integration only. If your configured
voice-messaging system supports Redirecting Number IE, you should check the
check box.
Note
|
The
default setting leaves this check box unchecked.
|
|
Redirecting Number IE Delivery Inbound
|
Check this
check box to accept the Redirecting Number IE in the incoming SETUP message to
the Cisco Unified CM. (The UUIE part of the SETUP message includes the
Redirecting Number IE.)
Uncheck
the check box to exclude the Redirecting Number IE in the incoming SETUP
message to the Cisco Unified CM.
You use
Redirecting Number IE for voice-messaging integration only. If your configured
voice-messaging system supports Redirecting Number IE, you should check the
check box.
Note
|
Default
leaves the check box unchecked.
|
|
Gatekeeper
Information
|
Gatekeeper
Name
|
This field
specifies the name of the gatekeeper that controls the H.323 client. Ensure the
gatekeeper is configured in Cisco Unified CM before an H.323 client is allowed
to specify the gatekeeper in its configuration. Default specifies empty.
|
E.164
|
Always use
a unique E.164 number. Do not use null value.
|
Technology
Prefix
|
This field
specifies a number ending with the # sign that describes the capability of an
endpoint in a zone. This field has no impact if via Zone configuration can be
used. Default specifies 1#*. Do not use null value.
|
Zone
|
This field
specifies the zone name of the zone that the gatekeeper manages. Do not use the
following values: same zone name for the H.323 client and trunk; null.
|
Associated
Mobility Identity
|
(mobility
identity)
|
If a
mobility identity has already been configured for this device, this area
displays the Name and Destination Number of the mobility identity. You can
click either value to display the Mobility Identity Information in the Remote
Destination Configuration window.
Note
|
This
field displays only after a Cisco Unified Mobile Communicator device has been
added. The Cisco Unified Mobile Communicator must be enabled for a mobile
phone.
|
|
Add New
Mobility Identity
|
If no
mobility identity has been defined for this device, click this link to add a
mobility identity. The Remote Destination Configuration window displays, which
allows you to add a new mobility identity to associate with this device.
Note
|
This
field displays only after a Cisco Unified Mobile Communicator device has been
added.
|
|
Associated
Remote Destinations
|
(remote
destination)
|
If a
remote destination has already been configured for this device, this area
displays the Name and Destination Number of the remote destination(s). You can
click the values to display the Remote Destination Information in the Remote
Destination Configuration window.
|
Add a New
Remote Destination
|
Click this
link to add a remote destination to associate with this device. The Remote
Destination Configuration window displays, which allows you to add a new remote
destination to associate with this device.
|
Route
calls to all remote destinations when client is not connected
|
Determines whether calls should be routed to all remote destinations when the
active remote destination is not set. Check this check box to receive calls
during network connection outage or to use a third-party voicemail system.
Note
|
This
field appears only on a CTI remote device type.
|
|
MLPP
Information
|
MLPP
Domain
|
Choose an
MLPP domain from the drop-down list box for the MLPP domain that is associated
with this device. If you leave the None value, this device inherits its MLPP
domain from the value that was set in the common device configuration. If the
common device configuration does not have an MLPP domain setting, this device
inherits its MLPP domain from the value that was set for the MLPP Domain
Identifier enterprise parameter.
|
MLPP
Indication
|
If
available, this setting specifies whether a device that can play precedence
tones will use the capability when it places an MLPP precedence call.
From the
drop-down list box, choose a setting to assign to this device from the
following options:
- Default—This device
inherits its MLPP indication setting from the common device configuration.
- Off—This device does not
handle nor process indication of an MLPP precedence call.
- On—This device does handle
and process indication of an MLPP precedence call.
Note
|
Do not
configure a device with the following combination of settings: MLPP Indication
is set to Off or Default (when default is Off) while MLPP Preemption is set to
Forceful.
Turning
on MLPP Indication (at the enterprise parameter or device level) disables
normal Ring Setting behavior for the lines on a device, unless MLPP Indication
is turned off (overridden) for the device.
|
|
MLPP
Preemption
|
Be aware
that this setting is not available on all devices. If available, this setting
specifies whether a device that can preempt calls in progress will use the
capability when it places an MLPP precedence call.
From the
drop-down list box, choose a setting to assign to this device from the
following options:
- Default—This device
inherits its MLPP preemption setting from the common device configuration.
- Disabled—This device does
not allow preemption of lower precedence calls to take place when necessary for
completion of higher precedence calls.
- Forceful—This device allows
preemption of lower precedence calls to take place when necessary for
completion of higher precedence calls.
Note
|
Do not
configure a device with the following combination of settings: MLPP Indication
is set to Off or Default (when default is Off) while MLPP Preemption is set to
Forceful.
|
|
Confidential Access Level
|
Select
the appropriate CAL value from the drop-down list box.
|
Confidential Access Mode
|
From the
drop-down list box, select one of the following options to set the CAL mode:
|
Do Not
Disturb (DND)
|
Do Not
Disturb
|
Check this
check box to enable Do Not Disturb on the phone.
|
DND Option
|
When you
enable DND on the phone, this parameter allows you to specify how the DND
features handle incoming calls:
- Call Reject—This option
specifies that no incoming call information gets presented to the user.
Depending on how you configure the DND Incoming Call Alert parameter, the phone
may play a beep or display a flash notification of the call.
- Ringer Off—This option
turns off the ringer, but incoming call information gets presented to the
device, so the user can accept the call.
- Use Common Phone Profile
Setting—This option specifies that the DND Option setting from the Common Phone
Profile window will get used for this device.
Note
|
For
7940/7960 phones that are running SCCP, you can only choose the Ringer Off
option. For mobile devices and dual-mode phones, you can only choose the Call
Reject option. When you activate DND Call Reject on a mobile device or
dual-mode phone, no call information gets presented to the device.
|
|
DND
Incoming Call Alert
|
When you
enable the DND Ringer Off or Call Reject option, this parameter specifies how a
call displays on a phone.
From the
drop-down list, choose one of the following options:
- None—This option specifies
that the DND Incoming Call Alert setting from the Common Phone Profile window
gets used for this device.
- Disable—This option
disables both beep and flash notification of a call, but, for the DND Ringer
Off option, incoming call information still gets displayed. For the DND Call
Reject option, no call alerts display, and no information gets sent to the
device.
- Beep Only—For an incoming
call, this option causes the phone to play a beep tone only.
- Flash Only—For an incoming
call, this option causes the phone to display a flash alert.
|
Secure
Shell Information
|
Secure
Shell User
|
Enter a
user ID for the secure shell user. You can enter any alphanumeric or special
characters up to 50 characters. Invalid characters include”, %, &, <,
>, and \. This field displays when the phone device that you are configuring
supports SSH access.
Cisco
Technical Assistance Center (TAC) uses secure shell for troubleshooting and
debugging. Contact TAC for further assistance.
See the
Cisco Unified
Communications Manager Security Guide
for this release for information about how to configure
encrypted phone configuration files to ensure that Cisco Unified CM does not
send SSH credentials to the phone in the clear.
|
Secure
Shell Password
|
Enter the
password for a secure shell user. You can enter any alphanumeric or special
characters up to 200 characters. Invalid characters include”, %, &, <,
>, and \. Contact TAC for further assistance.
See the
Cisco Unified
Communications Manager Security Guide
for this release for information about how to configure
encrypted phone configuration files to ensure that Cisco Unified CM does not
send SSH passwords to the phone in the clear.
|
Association Information
|
Modify
Button Items
|
After you
add a phone, the Association Information area displays on the left side of the
Phone Configuration window.
Click this
button to manage button associations for this phone. A dialog box warns that
any unsaved changes to the phone may be lost. If you have saved any changes
that you made to the phone, click OK to continue. The Reorder Phone Button
Configuration window displays for this phone.
|
Line [1] -
Add a new DN
Line [2] -
Add a new DN
|
After you
add a phone, the Association Information area displays on the left side of the
Phone Configuration window.
Click
these links to add a directory number(s) that associates with this phone. When
you click one of the links, the Directory Number Configuration window displays.
|
Add a new
SD
|
After you
add a phone, the Association Information area displays on the left side of the
Phone Configuration window.
Click this
link to add speed-dial settings for this phone. When you click the link, the
Speed Dial and Abbreviated Dial Configuration window displays for this phone.
|
Add a new
SURL
|
After you
add a phone, the Association Information area displays on the left side of the
Phone Configuration window.
Click this
link to configure service URL buttons for this phone. When you click the link,
the Configure Service URL Buttons window displays for this phone.
|
Add a new
BLF SD
|
After you
add a phone, the Association Information area displays on the left side of the
Phone Configuration window.
Click this
link to configure busy lamp field/speed dial settings for this phone. When you
click the link, the Busy Lamp Field Directed Call Park Configuration window
displays for this phone.
|
Add a new
BLF Directed Call Park
|
After you
add a phone, the Association Information area displays on the left side of the
Phone Configuration window.
Click this
link to configure busy lamp field/directed call park settings for this phone.
When you click the link, the Busy Lamp Field Directed Call Park Configuration
window displays for this phone.
|
Product-Specific Configuration Layout
|
Model-specific configuration fields that the device manufacturer
defines
|
To view
field descriptions and help for product-specific configuration items, click the
"?"
information icon in the Product Specific Configuration area to display help in
a popup dialog box.
If you
need more information, see the documentation for the specific device that you
are configuring or contact the manufacturer.
Select the
"Override
Common Settings" box for any corresponding setting in the Product Specific
Configuration area that you wish to update. If you do not check this box, the
corresponding parameter setting does not take effect. Parameters that you set
in the Product Specific Configuration area may also appear in the Device
Configuration window for various devices and in the Enterprise Phone
Configuration window. If you set these same parameters in these other windows
too, the setting that takes precedence is determined in the following order: 1)
Device Configuration window settings, 2) Common Phone Profile window settings,
3) Enterprise Phone Configuration window settings.
|