Template Information
|
Name
|
Enter a
name to identify this UDT.
|
Required and Frequently Entered Settings
|
Description
|
Enter the
purpose of the UDT. You can enter the functional rule of a group of users or
the key features enabled in the template. .
Tip
|
You
can click the pencil icon to place tokens in the description. Tokens are
variables that are replaced with actual values, after you create this UDT. You
can select the available elements from the list (such as User First Name). For
example, the token "#Lastname#s desk phone" becomes "Smith's desk phone" for a
user with the last name "Smith."
|
Note
|
When
you insert the device with this template, the element in the description is
propagated based on the actual device or user information.
|
|
Device Pool
|
Select the
device pool for the UDT. The device pool defines sets of common characteristics
for this UDT, such as region, date/time group, softkey template, and MLPP
information.
|
Device
Security Profile
|
Choose
the device security profile for the UDT. The security profile for the UDT is
model and protocol independent.
Note
|
You can
only select a model-independent security profile for a UDT.
|
To
identify the settings that the profile contains, see the
menu.
Note
|
If you
enable the security feature for a template, the security setting is applied to
the phone inserted with this template only when the phone supports all of the
following security features.
-
Security Authentication
-
Security Encryption
-
File
Encrypt
Otherwise you insert the phone with the default non-secure
security profile with the same model and device protocol of the inserted phone.
|
For more
information about how CAPF settings that you update in the phone configuration
window affect security profile CAPF settings, see the
Cisco
Unified Communications Manager Security Guide.
|
SIP Profile
|
Select
the default SIP profile or a specific profile that was previously created. SIP
profiles provide specific SIP information such as registration and keepalive
timers, media ports, and Do Not Disturb control.
|
Phone Button
Template
|
Select the
appropriate phone button template for the UDT. The phone button template
determines the behavior of buttons, and identifies which feature (such as line
and speed dial) is used for each button.
Note
|
You must
select a phone button template before you can expand the Phone Button
Configuration field.
|
Note
|
You can
only assign universal phone button templates to a UDT.
|
|
Phone Buttons Configuration
|
Use this
section to view and change the settings for the universal phone button
template. This section lists the configurable buttons for the phone button
template that you select in the Phone Button Template field.
You can
update a universal phone button template to add or remove features; add or
remove lines and speed dials; or assign features, lines, and speed dials to
different buttons on the phone that you add after you create the UDT. You can
change the button labels in the default phone button templates, but you cannot
change the function of the buttons in the default templates.
Note
|
If you
update a phone template, be sure to inform affected users of the changes.
|
|
Line
Appearance
|
Directory
Number
|
Select a
directory number (DN) from the drop-down list box. After you create a device
with this UDT, the DN will exist on the newly created device automatically.
|
Line Label
|
If left
blank, this defaults to the line number. If you desire a different label for
the line on the phone, you can enter it here.
Tip
|
You can
use tokens (pencil icon) to enter the line label.
|
|
Display
(Caller ID)
|
Leave this
field blank to have the system display the extension.
Use a
maximum of 30 alphanumeric characters. Typically, use the username or the
directory number (if using the directory number, the person receiving the call
may not see the proper identity of the caller).
Tip
|
You can
use tokens (pencil icon) to enter the display.
|
|
Ring
Setting When Phone is Idle *
|
Use this
field to set up the ring setting for this UDT for the line appearance when an
incoming call is received and no other active calls exist on that device.
Select one of the following options:
-
Use
system default
-
Disable
-
Flash
only
-
Ring
once
-
Ring
|
Ring
Setting When Phone is in Use
|
From the
drop-down list box, select the ring setting that is used for this UDT when it
has an active call on a different line. Select one of the following options:
-
Use
system default
-
Disable
-
Flash
only
-
Ring
once
-
Ring
-
Beep
only
|
Visual
Message Waiting Indicator Policy *
|
Enter the
external phone number (or mask) that is used to send Caller ID information for
this UDT.
You can
enter a maximum of 24 number, the international escape character +, and "X"
characters. The Xs represent the directory number and must appear at the end of
the pattern. For example, if you specify a mask of 972813XXXX, an external call
from extension 1234 displays a caller ID number of 9728131234.
|
Audible
Message Waiting Indicator Policy *
|
Use this
field to configure the ring setting for the line appearance when an incoming
call is received and no other active calls exist on that device. Select one of
the following options:
-
Use
system default
-
Disable
-
Flash
only
-
Ring
once
-
Ring
|
Recording
Options *
|
This
field determines the recording option on the line appearance of an agent. The
default recording option is Call Recording Disabled.
Select
one of the following options:
- Call
Recording Disabled
-
You
cannot record call that you make on this line appearance.
- Selective Call Recording Enabled
-
You
can record calls that you make on this line appearance by using a softkey or
programmable line key that is assigned to the device, a CTI-enabled
application, or both interchangeably.
Selective recording supports two modes:
- Silent recording
-
Call recording status is not reflected on the Cisco IP device
display. Silent recording is typically used in a call center environment to
allow a supervisor to record an agent call. A CTI-enabled application running
on the supervisor desktop is generally used to start and stop the recording for
an agent-customer call.
- User recording
-
User recording-Call recording status is reflected on the Cisco
IP device display. You can start or stop a recording by using using a softkey,
programmable line key, or CTI-enabled application running on the user desktop.
To enable user recording, add the Record softkey or programmable line key to
the UDT. Do not add the Record softkey if you only want silent recording.
When the
recording option is set to either Automatic Call Recording Enabled or Selective
Call Recording Enabled, you can associate the line appearance with a recording
profile.
When
automatic recording is enabled, start- and stop-recording requests using a
softkey, programmable line key, or CTI-enabled application are rejected.
|
Recording
Profile
|
This field
determines the recording profile on the line appearance of an agent. Choose an
existing recording profile from the drop-down list box. To create a recording
profile, use the
menu option.
The
default value specifies None.
|
  Call
Pickup Group Audio Alert Setting (Phone Active)
|
This
field determines the type of notification an incoming call sends to members of
a call pickup group. If the called phone does not answer, the phones in the
call pickup group that are busy will either hear a beep (beep beep) or hear
nothing (disabled).
- Use
System Default
-
The
setting of the Cisco CallManager service parameter Call Pickup Group Audio
Alert Setting of Busy Station determine the value of this field.
- Disable
-
No
alert is sent to member of the call pickup group.
- Beep
Only
-
A
beep beep is sent to members of the call pickup group.
|
Call
Pickup Group Audio Alert Setting (Phone Idle)
|
This
field determines the type of notification an incoming call sends to members of
a call pickup group. If the called phone does not answer, the phones in the
call pickup group that are idle will either hear a short ring (ring once) or
hear nothing (disabled).
- Use
System Default
-
The
setting of the Cisco CallManager service parameter Call Pickup Group Audio
Alert Setting of Idle Station determines the value of this field.
- Disable
-
No
alert is sent to members of the call pickup group.
- Ring
Once
-
A
short ring is sent to members of the call pickup group.
|
Monitoring
Calling Search Space
|
The
monitoring calling search space of the supervisor line appearance must include
the agent line or device partition to allow monitoring the agent.
Set the
monitoring calling search space on the supervisor line appearance window.
Choose an existing calling search space from the drop-down list box.
The
default value specifies None.
|
SpeedDial
|
(number
from 1 to 199 in the left column)
|
This
column identifies the speed-dial button (for example, 1, 2, 3, or 4) or the
abbreviated-dial index for abbreviated dial.
|
Number
|
Enter the
number that you want the system to dial when the user presses the speed-dial
button. You can enter digits 0 through 9, *, #, and +, which is the
international escape character. For a Pause in Speed Dial, you can enter comma
(,) which can act as a delimiter as well as other pause before sending DTMF
digits.
|
Label
|
Enter the
text that you want to display for the speed-dial button or abbreviated-dial
number.
Note
|
If you
are configuring a Pause in Speed Dial, you must add a label so that FAC, CMC,
and DTMF digits are not displayed on the phone screen.
|
|
BLF
SpeedDial
With the
BLF Presence feature, a watcher can monitor the status of the presence entity
(also called presentity). When you configure BLF/SpeedDial buttons, the
presence entity appears as a speed dial on the device of the watcher.
The
following section describes the settings that you configure for BLF/SpeedDial
buttons.
|
Destination
|
Perform
one of the following tasks to configure a SIP URI or a directory number as a
BLF/SpeedDial button:
-
Only
for phones that are running SIP, enter the SIP URI. For phones that are running
SCCP, you cannot configure SIP URI as BLF/SpeedDial buttons.
-
For
phones that are running either SCCP or SIP, enter a directory number in this
field or go to the Directory Number drop-down list box. If you want to
configure non-Unified CM directory numbers as BLF/SpeedDial buttons,
enter the directory number in this field.
For this
field, enter only numerals, asterisks (*), and pound signs (#).
Note
|
If you
configure the Destination field, do not select an option from the Directory
Number drop-down list box. If you select an option from the Directory Number
drop-down list box after you configure the Destination,
Unified CM deletes the Destination configuration.
|
|
Directory
Number
|
The
Directory Number drop-down list box displays a list of directory numbers that
exist in the
Unified CM database. Configure this setting only if
you did not configure the Destination field.
For a UDT
that runs either SCCP or SIP, select the number (and corresponding partition,
if it displays) that you want the system to dial when the user presses the
speed-dial button; for example, 6002-Partition 3. Directory numbers that
display without specific partitions belong to the default partition
|
Label
|
Enter the
text that you want to display for the BLF/SpeedDial button.
This field
supports internationalization. If your phone does not support
internationalization, the system uses the text that displays in the Label ASCII
field.
|
BLF
Directed Call Park
|
Directory
Number
|
The
Directory Number drop-down list box displays a list of directory numbers that
exist in the
Unified CM database.
For a UDT
that runs either SCCP or SIP, select the number (and corresponding partition,
if it appears) that you want the system to dial when the user presses the
speed-dial button; for example, 6002 in 3. Directory numbers that appear
without specific partitions belong to the default partition.
|
Label
|
Enter the
text that you want to appear for the BLF/Directed Call Park button.
This
field supports internationalization. If your phone does not support
internationalization, the system uses the text that appears in the Label ASCII
field.
|
Service
URL
|
Button
Service
|
Enter the name of the
service. If the service is not marked as an enterprise subscription, the
service name appears in areas where you can subscribe to a service; for
example, under Cisco Unified Communications Self Care Portal. Enter up to 32
characters for the service name.
|
Label
|
Enter the
text that you want to appear for the Service URL button.
|
Device Settings
|
Device Name
|
Enter a
name to identify the device that uses this UDT.
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 enter dot (.), dash (-), and underscore (_).
|
Owner User
ID
|
From the drop-down list box, select the User ID
that you want to assign as the device owner for devices that use this UDT.
By
default, this field is set to the
Current Device Owner's User ID. If this option is
configured, when you use this UDT to create a device in the Quick User/Phone
Add menu, the user ID under which you create the device is assigned as the
device owner. In addition, if self provisioning is enabled for a user, when
that user logs into the device for the first time, the device is created
automatically with that user’s user ID as the device owner.
You may
also select a specific user ID as the device owner for all devices that use
this UDT. If you choose this option, when you use this UDT to create a device
in the Quick User/Phone Add menu, regardless of which user you use to create
the device, Cisco Unified Communications Manager assigns the user ID in the UDT
Owner User ID drop-down list box as the device owner.
|
Mobility
User ID
|
From the
drop-down list box, select the user ID of the assigned mobility user. You can
either select a user ID to own all devices created using this UDT, or select
Current Device Owner's User Id to have the user who
the devices are created for (using this UDT) as the owner of the device.
Tip
|
Assign
the element that represents the user ID to the UDT to associate the UDT to the
user or owner ID.
|
|
Join Across
Lines
|
From the
drop-down list box, enable or disable the Join Across Lines feature or select
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.
|
Always Use
Prime Line
|
From the
drop-down list box, choose one of the following options:
- Off
-
When
a device is idle and receives a call on any line, a user answers the call from
the line on which the call is received.
- On
-
When
a device is idle (off hook) and receives a call on any line, the primary line
is chosen for the call. Calls on other lines continue to ring, and the user
must select those other lines to answer these calls.
- Default
-
Unified CM 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 a
device is idle, the primary line becomes the active line for retrieving voice
messages when a user presses the Messages button.
- Off
-
If a
device is idle, pressing the Messages button automatically dials the
voice-messaging system from the line that has a voice message.
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
a user presses the Messages button.
- Default
-
Unified CM uses the configuration from the Always Use
Prime Line for Voice Message service parameter, which supports the Cisco
CallManager service.
|
Single
Button Barge
|
From the
drop-down list box, enable or disable the Single Button Barge/cBarge feature
for this UDT 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 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.
|
Privacy
|
For
privacy on this UDT, select
On in the Privacy drop-down list box.
|
Built in
Bridge
|
Enables
or disables the built-in conference bridge for the barge feature (select
On,
Off, or
Default).
|
Allow
Control of Device from CTI
|
Check
this check box to allow CTI to control and monitor this UDT.
If the
associated directory number specifies a shared line, you should check the check
box as long as at least one associated device specifies a combination of device
type and protocol that CTI supports.
|
Hotline
Device
|
Check
this check box to enable Hotline device for this UDT. Hotline devices can only
connect to other Hotline devices. This feature is an extension of PLAR, which
configures a device 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.
|
Logged
into Hunt Group
|
This
check box indicates that this UDT is currently signed in to a hunt list
(group). When this UDT is added to a hunt list, the administrator can sign the
user in or out by checking or unchecking this check box.
Users use
the softkey on a device to sign in or out of the hunt list.
|
Retry
Video Call as Audio
|
This
check box applies only to video endpoints that receive a call. If devices using
this UDT receive 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 devices on this UDT
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), route list,
or 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,
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 connected line display information for
each call.
|
Enable
Extension Mobility
|
Check this
check box if to allow this UDT to support extension mobility.
|
Require
Off-Premise Location
|
Check this
check box if the device inserted with this template requires off-premise
location update upon the 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 the template that remote or mobile devices use, which have
frequent location change.
|
Device Routing
|
SIP Dial
Rules
|
If
required, select the appropriate SIP dial rule. SIP dial rules provide local
dial plans for this UDT, so users do not have to press a key or wait for a
timer before the call is processed.
Leave the
SIP Dial Rules field set to
None if you do not want dial rules to apply to this
UDT. This means that the user must use the dial softkey or wait for the timer
to expire before the call gets processed.
|
Calling
Search Space
|
From the
drop-down list box, select the appropriate calling search space (CSS). A CSS
comprises a collection of partitions that are searched to determine how a
dialed number should be routed. The calling search space for this UDT and the
calling search space for the directory number are used together. The directory
number CSS takes precedence over the device CSS.
|
Calling
Party Transformation CSS for Inbound Calls
|
This
setting allows you to localize the calling party number on this UDT for inbound
calls. Make sure that the Calling Party Transformation CSS that you select
contains the calling party transformation pattern that you want to assign to
this UDT.
Tip
|
Before
the call occurs, the device must apply the transformation by using digit
analysis. If you configure the Calling Party Transformation CSS for Inbound
Calls as None, the transformation does not match and is not applied. Ensure
that you configure the Calling Party Transformation Pattern in a non-null
partition that is not used for routing.
|
|
Calling
Party Transformation CSS for Outbound Calls
|
This
setting allows you to localize the calling party number on this UDT for
outbound calls. Make sure that the Calling Party Transformation CSS that you
choose contains the calling party transformation pattern that you want to
assign to this UDT.
Tip
|
Before
the call occurs, the UDT must apply the transformation by using digit analysis.
If you configure the Calling Party Transformation CSS for Outbound Calls as
None, the transformation does not match and is not applied. Ensure that you
configure the Calling Party Transformation Pattern in a non-null partition that
is not used for routing.
|
|
Rerouting
Calling Search Space
|
From the
drop-down list box, select a calling search space to use for rerouting.
The
rerouting calling search space of the referrer is 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.
|
SUBSCRIBE
Calling Search Space
|
Supported
with the BLF Presence feature, the SUBSCRIBE calling search space determines
how
Unified CM routes BLF presence requests that come from
this UDT. This setting allows you to apply a calling search space separate from
the call-processing search space for presence (SUBSCRIBE) requests for the UDT.
From the
drop-down list box, select the SUBSCRIBE calling search space to use for BLF
presence requests for this UDT. All calling search spaces that you configure in
Unified CM Administration appear 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.
|
Use
Device Pool Calling Party Transformation CSS for Inbound Calls
|
To use the
Calling Party Transformation CSS that is configured in the device pool that is
assigned to this UDT, check this check box. If you do not check this check box,
this UDT uses the Calling Party Transformation CSS setting for inbound calls.
|
Use
Device Pool Calling Party Transformation CSS for Outbound Calls
|
To use
the Calling Party Transformation CSS that is configured in the device pool that
is assigned to this UDT, select this check box. If you do not select this check
box, the UDT uses the Calling Party Transformation CSS for outbound calls that
you selected in the Phone Configuration window.
|
Phone Settings
|
Common
Profile
|
From the
drop-down list box, select a common phone profile from the list of available
common phone profiles.
Select
View Details for specific details about each common phone profile.
|
Common
Device Configuration
|
From the
drop-down list box, you can select a common device configuration that was
configured in the Common Device Configuration window.
Select
View Details for specific details about each common device configuration.
|
Softkey
Template
|
From the
drop-down list box, select a softkey template.
Leave the
softkey template set to <None> to use the softkey template configured in
the assigned Common Phone Profile.
|
Feature
Control Policy
|
From the
drop-down list box, select a feature control policy that has already been
configured in the Feature Control Policy configuration window (
Leave the
softkey template set to <None> to use the feature control policy
configured in assigned Common Phone Profile.
|
Phone
Personalization
|
The Phone
Personalization setting allows you to enable this UDT so that it works with
Phone Designer. Phone designer is a Cisco Unified Communications widget that
allows a user to customize the wallpaper and ring tones on a device.
From the
Phone Personalization drop-down list box, select one of the following options:
- Disabled
-
The
user cannot customize this UDT by using Phone Designer.
- Enabled
-
The
user can use Phone Designer to customize this UDT.
- Default
-
This
UDT uses the configuration from the Phone Personalization enterprise parameter.
Note
|
You
must install and configure Phone Designer, so a user can customize the device.
|
|
Protocol
Settings
|
MTP
Preferred Originating Codec
|
From the
drop-down list box, select the codec to use if a media termination point is
required for SIP calls.
|
Digest
User
|
Select an
end user that you want to associate with this UDT for this setting that is used
with digest authentication (SIP security).
Note
|
Ensure
that you configured digest credentials for the user that you choose, as
specified in the End User setting window.
|
After you
save the UDT and apply the setup update to the device, the digest credentials
for the user is added to the phone configuration file.
For more
information about digest authentication, see the
Cisco
Unified Communications Manager Security Guide.
|
Outbound
Call Rollover
|
Use this
setting if you are creating this UDT for a Cisco Unified IP Phone 7931.
- No
Rollover
-
Conference and transfer do not work in this mode. If a user
attempts to use either of these features, the phone status displays as Error
Pass Limit.
Note
|
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 is placed on hold, and a new call initiates on Line 9 to complete the
transfer.
|
Media
Termination Point Required
|
Check
this check box if you want to use an MTP to implement features that H.323 does
not support (such as hold and transfer). Uncheck this check box if you do not
want to use an MTP to implement features.
Note
|
Check
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 a 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 UDT.
|
Require
DTMF Reception
|
Check
this check box to require DTMF reception for this UDT.
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.
|
|
IP Phone Services
Subscription
|
Select
the
Subscribe button and select the service. If the
service is not marked as an enterprise subscription, the service name appears
in areas where you can subscribe to a service.
Enter up to 128 characters for the service
name.
For Java
MIDlet services, the service name must exactly match the name that is defined
in the Java Application Descriptor (JAD) file.
Note
|
You must
configure IP Phone services and save them before you can configure Service URL
Buttons.
|
Note
|
Unified CM allows you to create two or more IP phone
services with identical names. Cisco recommends that you do not do so unless
most or all phone users are advanced, or unless an administrator always
configures the IP phone services. Be aware that if AXL or any third-party tool
accesses the list of IP phone services for configuration, you must use unique
names for IP phone services.
|
|
Security
Settings
|
General
Security Settings
|
Use
Trusted Relay Point
|
From the
drop-down list box, enable or disable whether Unified CM inserts a trusted
relay point (TRP) device with this media endpoint. Select one of the following
values:
- Default
-
If
you select this value, the UDT uses the Use Trusted Relay Point setting from
the common device configuration.
- Off
-
Select this value to disable the use of a TRP with this UDT.
This setting overrides the Use Trusted Relay Point setting in the common device
configuration.
- On
-
Select this value to enable the use of a TRP with this UDT. This
setting overrides the Use Trusted Relay Point setting in the common device
configuration.
A Trusted
Relay Point (TRP) device designates an MTP or transcoder device that is labeled
as Trusted Relay Point.
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 is used as the required MTP.
If both
TRP and RSVPAgent are needed for the endpoint, 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, Unified CM first tries to find
a transcoder that is also designated as a TRP.
|
Protected
Device
|
Check
this check box to designate this UDT as protected, which enables a device to
play a 2-second tone to notify the user when a call is encrypted and both
devices are configured as protected. The tone plays for both parties when the
call is answered. The tone does not play unless both devices are protected and
the call occurs over encrypted media.
This
setting represents only one of several configuration requirements for the
secure indication tone to play. For more information about the secure
indication tone feature and the configuration requirements, see the
Cisco
Unified Communications Manager Security Guide.
Note
|
If you
check this check box and the system determines that the call is not encrypted,
a device plays an indication tone to alert the user that the call is not
protected.
|
|
Certificate Authority Proxy Function (CAPF) Settings
|
Certificate Operation
|
From the
drop-down list box, select one of the following options:
For more information on CAPF operations, see the
Cisco Unified Communications Manager Security Guide
.
Note
|
The Certificate Operation is applied to the phone using
this template for Auto-Registration, Self-Provisioning.
|
|
Authentication Mode
|
This
field allows you to choose the authentication method that this UDT uses during
the CAPF certificate operation.
From the
drop-down list box, select 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 UDT.
- By
Null String
-
Installs/upgrades, deletes, or troubleshoots a locally
significant certificate without user intervention.
Note
|
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 UDT. If a LSC exists in the UDT,
authentication occurs via the LSC, regardless of whether a MIC exists in the
UDT. If a MIC and LSC exist in the UDT, authentication occurs via the LSC. If a
LSC does not exist in the UDT, but a MIC does exist, authentication occurs via
the MIC.
At
any time, the UDT uses only one certificate to authenticate to CAPF even though
a MIC and LSC can exist in the UDT 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 UDT. If a MIC exists in
the UDT, authentication occurs via the MIC, regardless of whether a LSC exists
in the UDT. If a LSC exists in the UDT, but a MIC does not exist,
authentication occurs via the LSC.
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
select the By Authentication String option in the Authentication Mode drop-down
list box, this field applies. Manually enter a string or select the
Generate String button to generate a string.
Note
|
Ensure
that the string contains 4 to 10 digits.
|
To
install, upgrade, delete, or troubleshoot a locally significant certificate, a
user or administrator must enter the authentication string on a device.
|
Key Size
(Bits)
|
For this
setting that is used for CAPF, select the key size for the certificate from the
drop-down list box. The default setting equals 1024. Other options include 512
and 2048.
Note
|
If you
select a higher key size than the default setting, the UDT takes longer to
generate the entropy that is required to generate the keys. Key generation,
which is set at low priority, allows the UDT to function while the action
occurs. 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.
|
|
Service Configuration
Settings
|
Information
|
Enter the
location (URL) of the help text for the information button.
Leave this
field blank to accept the default setting.
|
Directory
|
Enter the
server from which the UDT obtains directory information.
Leave
this field blank to accept the default setting.
|
Messages
|
Leave
this field blank (not used by
Unified CM).
|
Services
|
Enter the
location (URL) for IP phone services.
|
Authentication Server
|
Enter the
URL that the UDT uses to validate requests that are made to the web server. If
you do not provide an authentication URL, the advanced features for UDT that
require authentication do 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 HTTP client.
The rule
contains two parts for when to use the proxy server parameter:
If you do
not configure this URL, the UDT attempts to connect directly to the URL.
To accept
the default setting, leave this field blank.
|
Idle
|
Enter the
URL that appears on the display when the UDT device is not used for the time
that is specified in Idle Timer field. For example, you can display a logo on
the LCD when the UDT device is not 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 appears.
To accept
the value of the Idle URL Timer enterprise parameter, leave this field blank.
|
Secure
Authentication URL
|
Enter the
secure URL that the UDT device uses to validate requests that are made to the
web server.
Note
|
If you
do not provide a Secure Authentication URL, a device uses the nonsecure URL. If
you provide both a secure URL and a nonsecure URL, a 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 UDT obtains directory information.
This parameter specifies the URL that this UDT uses when you press the
Directory button.
Note
|
If you
do not provide a Secure Directory URL, a device uses the nonsecure URL. If you
provide both a secure URL and a nonsecure URL, a 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 appears on the display when this UDT is
idle, as specified in Idle Timer field. For example, you can display a logo on
the LCD when the UDT is not used for 5 minutes.
Note
|
If you
do not provide a Secure Idle URL, a device uses the nonsecure URL. If you
provide both a secure URL and a nonsecure URL, a 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 UDT can find help text
information. This information appears when the user presses the information (I)
button or the question mark (?) button.
Note
|
If you
do not provide a Secure Information URL, this UDT uses the nonsecure URL. If
you provide both a secure URL and a nonsecure URL, this UDT selects 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. This UDT contacts this URL when the user
presses the Messages button.
Note
|
If you
do not provide a Secure Messages URL, a device uses the nonsecure URL. If you
provide both a secure URL and a nonsecure URL, a 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 Secure Services URL is the
location that the UDT contacts when the user presses the Services button.
Note
|
If you
do not provide a Secure Services URL, a device uses the nonsecure URL. If you
provide both a secure URL and a nonsecure URL, a device chooses the appropriate
URL, based on its capabilities.
|
To accept
the default setting, leave this field blank.
Maximum
length: 255
|
Services
Provisioning
|
From the
drop-down list box, select how the UDT supports the services:
- Internal
-
The
UDT uses the phone configuration file to support the service.
Select this option or Both for Cisco-provided default services where the
Service URL was not updated; that is, the service URL indicates
Application:Cisco/<name of service>; for example,
Application:Cisco/CorporateDirectory.
Select Internal or Both for Cisco-signed Java MIDlets because Cisco-signed Java
MIDlets are provisioned in the configuration file.
- External URL
-
Selecting External URL indicates that the UDT ignores the
services in the phone configuration file and retrieves the services from a
Service URL.
If
you configure 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 UDT.
- Both
-
Selecting Both indicates that the UDT supports both the services
that are defined in the configuration file and external applications that are
retrieved from service URLs.
|
Troubleshooting
Settings
|
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
-
Unified CM writes the decrypted or nonencrypted
messages to a file, and the system encrypts each file. The system creates a new
file daily with a new encryption key.
Unified CM, which stores the file for seven days, also
stores the keys that encrypt the file in a secure location.
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 about 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, appears.
For more
information about packet capturing, see the
Cisco
Unified Communications Manager Troubleshooting Guide.
|
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 appears when the UDT supports SSH access.
Cisco
Technical Assistance Center (TAC) uses secure shell for troubleshooting and
debugging. Contact TAC for further assistance.
For more
information about how to configure encrypted phone configuration files to
ensure that the Unified CM does not send unencrypted SSH credentials to the UDT
device, see the
Cisco
Unified Communications Manager Security Guide.
|
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.
For more
information about configuring encrypted phone files to ensure that Unified CM
does not send unencrypted SSH passwords to the UDT device, see the
Cisco
Unified Communications Manager Security Guide.
|
Locale Settings
|
User Locale
|
From the
drop-down list box, select the locale that is associated with the UDT. The user
locale identifies a set of detailed information to support users, including
language and font.
Note
|
If no
user locale is specified,
Unified CM uses the user locale that is associated
with the device pool.
|
Note
|
If the
users require that information appear in any language other than English,
verify that the locale installer is installed before you configure the user
locale. See
the Unified CM Locale Installer documentation.
|
|
Network Locale
|
From the
drop-down list box, select the locale that is associated with the UDT. The
network locale contains a definition of the tones and cadences that the UDT in
a specific geographic area uses.
Note
|
If no
network locale is specified,
Unified CM uses the network locale that is associated
with the device pool.
|
Note
|
If
users require that country-specific tones be played, verify that the locale is
installed before ypu configure the network locale. See the Unified CM Locale
Installer documentation.
|
|
Multilevel Precedence
Preemption (MLPP) Settings
|
MLPP
Domain
|
Select an MLPP domain from
the drop-down list box for the MLPP domain that is associated with this UDT. If
you leave the
None value, devices with this UDT inherit the MLPP
domain from the value that was set for the device pool. If the device pool does
not have an MLPP domain setting, this UDT 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 uses the capability when it places an MLPP precedence call.
From the
drop-down list box, select a setting to assign to this UDT from the following
options:
- Default
-
This
UDT inherits its MLPP indication setting from its device pool.
- Off
-
This
UDT does not handle nor process indication of an MLPP precedence call.
- On
-
This
UDT does handle and process indication of an MLPP precedence call.
Note
|
Do not
configure a UDT 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.
|
Note
|
Turning
on MLPP Indication (at the enterprise parameter, device pool, or device level)
disables normal Ring Setting behavior for the lines on a device, unless MLPP
Indication is turned off (overridden) for the UDT.
|
|
MLPP
Preemption
|
If
available, this setting specifies whether this UDT that can preempt calls in
progress uses the capability when it places an MLPP precedence call.
From the
drop-down list box, select a setting to assign to this UDT from the following
options:
- Default
-
This
UDT inherits its MLPP preemption setting from its device pool.
- Disabled
-
This
UDT does not allow preemption of lower precedence calls to take place when
necessary for completion of higher precedence calls.
- Forceful
-
This
UDT allows preemption of lower precedence calls to take place when necessary
for completion of higher precedence calls.
Note
|
Do not
configure a UDT 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.
|
|
Do Not Disturb (DND)
Settings
|
Do Not
Disturb
|
Check this
check box to enable Do Not Disturb (DND) for this UDT.
|
DND Option
|
When you
enable DND on the UDT, this parameter allows you to specify how the DND
features handle incoming calls:
- Call
Reject
-
This
option specifies that no incoming call information is presented to the user.
Depending on how you configure the DND Incoming Call Alert parameter, the UDT
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 UDT, so the user can accept the call.
- Use
Common Phone Profile Setting
-
This
option specifies that the device on the UDT uses the DND Option setting from
the Common Phone Profile window.
Note
|
For
7940 and 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 is 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 appears on a device.
From the
drop-down list, select one of the following options:
- None
-
This
option specifies that this UDT uses the DND Incoming Call Alert setting from
the Common Phone Profile window.
- Disable
-
This
option disables both beep and flash notification of a call, but, for the DND
Ringer Off option, incoming call information still appears. For the DND Call
Reject option, no call alerts appear, and no information is sent to the UDT.
- Beep
Only
-
For
an incoming call, this option causes the associated device to play a beep tone
only.
- Flash
Only
-
For
an incoming call, this option causes the associated device to display a flash
alert.
|
Automatic Alternate Routing
(AAR) Settings
|
AAR Group
|
Select the
automated alternate routing (AAR) group for this UDT. 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, Unified CM uses the
AAR group that is associated with Device Pool or Line.
|
AAR
Calling Search Space
|
Select the
appropriate calling search space for this UDT 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.
|
Busy Lamp Field
Settings
|
BLF
Presence Group
|
Configure
this field with the BLF Presence feature.
From the
drop-down list box, select a BLF presence group for this UDT. The selected
group specifies the devices, end users, and application users that can monitor
this directory number.
The
default value for BLF Presence Group specifies Standard Presence group,
configured with installation. BLF presence groups that are configured in
Unified CM Administration also appear in the drop-down
list box.
Presence
authorization works with BLF presence groups to allow or block presence
requests between groups.
|
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.
|
Music on Hold
Settings
|
User Hold
MOH Audio Source
|
To
specify the audio source that plays when a user initiates a hold action, select
an audio source from the drop-down list box.
If you do
not select an audio source,
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, select
.
|
|
Network
Hold MOH Audio Source
|
To
specify the audio source that plays when the network initiates a hold action,
select an audio source from the drop-down list box.
If you do
not choose an audio source,
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, select
.
|
|
Location
Settings
|
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, select the appropriate location for this UDT.
A
location setting of
Hub_None means that the locations feature does not
keep track of bandwidth. 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.
|
Geolocation
|
From the
drop-down list box, select a geolocation.
You can
select the
Unspecified geolocation, which designates that this
UDT does not associate with a geolocation.
You can
also select a geolocation that is configured with the
menu option.
|
Device
Mobility Mode
|
From the
drop-down list box, turn the device mobility mode on or off for this UDT or
select
Default to use the default device mobility mode. The
default setting uses the value for the Device Mobility Mode service parameter.
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
|
Media
Resource Group List
|
Select
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, Unified CM uses the Media Resource Group List
that is defined in the device pool.
|
Remote
Device
|
If you
are experiencing delayed connect times over SCCP pipes to remote sites, check
the Remote Device check box. Checking this check box tells
Unified CM to allocate a buffer for the UDT when it
registers and to bundle SCCP messages.
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.
|
Unified CM sends
the bundled messages to the UDT when the station buffer is full, as soon as it
receives a media-related message, or when the Bundle Outbound SCCP Messages
timer expires.
Note
|
To
specify a setting other than the default setting (100 msec) for the Bundle
Outbound SCCP Messages timer, set up 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.
|
|