Phone features and setup on Unified CM

Phone feature configuration

You can set up phones to have a variety of features, based on the needs of your users. You can apply features to all phones, a group of phones, or to individual phones.

When you set up features, the Cisco Unified Communications Manager Administration window displays information that is applicable to all phones and information that is applicable to the phone model. The information that is specific to the phone model is in the Product Specific Configuration Layout area of the window.

For information on the fields applicable to all phone models, see the Cisco Unified Communications Manager documentation.

When you set a field, the window that you set the field in is important because there is a precedence to the windows. The precedence order is:

Individual phones (highest precedence)
Group of phones
All phones (lowest precedence)

For example, if you don't want a specific set of users to access the phone web pages, but the rest of your users can access the pages, you can do the following:

Enable access to the phone web pages for all users.
Disable access to the phone web pages for each individual user, or set up a user group and disable access to the phone web pages for the group of users.
If a specific user in the user group needs access to the phone web pages, you can enable it for that particular user.

Set up phone features for all phones

1	Sign into Cisco Unified Communications Manager Administration as an administrator.
2	Select System > Enterprise Phone Configuration.
3	Set the fields you want to change.
4	Check the Enable Enterprise Settings check box for any changed fields.
5	Click Save.
6	Click Apply Config.
7	Restart the phones. This will impact all phones in your organization.

Set up phone features for a group of phones

1	Sign into Cisco Unified Communications Manager Administration as an administrator.
2	Select Device > Device Settings > Common Phone Profile.
3	Locate the profile that you want to set up.
4	Navigate to the Product Specific Configuration Layout pane and set the fields.
5	Check the Override Enterprise Settings check box for any changed fields.
6	Click Save.
7	Click Apply Config.
8	Restart the phones.

Set up phone features for a single phone

1	Sign into Cisco Unified Communications Manager Administration as an administrator.
2	Select Device > Phone.
3	Locate the phone associated with the user.
4	Navigate to the Product Specific Configuration Layout pane and set the fields.
5	Check the Override Enterprise/Common Phone Profile Settings check box for any changed fields.
6	Click Save.
7	Click Apply Config.
8	Restart the phone.

Apply the custom wallpaper and logo

The wallpaper and color theme on the phone screen also applies to the attached Key Expansion Modules (KEM). The logo displays only on the phone screen and does not appear on the KEM screen.

To deploy your custom wallpaper and logo to your phones, follow this workflow:

Prepare your wallpaper and logo images
Upload the images files to the TFTP server
Create a general management file List.xml
Upload the List.xml to the TFTP server
Restart the TFTP server
Configure the wallpaper settings on Cisco Unified Communications Manager Administration

See the following for procedures:

Prepare your wallpaper and logo images

To get the best experience, keep the following tips in mind when choosing or designing your images:

Avoid using clustered images that can make it hard for you to identify the feature buttons or lines on the home screen. Simplicity is key when selecting wallpapers.
Ensure that your chosen wallpapers match your phone's color scheme. Opt for wallpapers that complement either the dark or light color palettes. Dark images are best suited for dark mode, while light images work well for light mode.
Avoid using high contrast images as wallpapers. The extreme contrast can make it challenging to see the logo and other screen elements against the background.

Table 1. The specifications for wallpaper and logo images
Image	Required format	Recommended dimensions	Description
Logo	PNG	380x250 pixels	Images that don't match the recommended dimensions will be scaled proportionally. You don't need to create a separate thumbnail image for the logo. The system automatically scales the logo image to fit the dimensions of the thumbnail.
Wallpaper	PNG	1024x600 pixels	Images that don't match the recommended dimensions may be scaled to fit the phone screen, which may cause the image to become distorted.
Wallpaper thumbnail	PNG	180x100 pixels	Images that don't match the recommended dimensions may be scaled to fit the thumbnail display, which may cause the thumbnail image to become distorted.

Table 2. Limit size of customized wallpapers on Video Phone 8875
Maximum size per image	Maximum number of images	Limit size
1MB	20	1MB x 20

1	Choose your desired logo and wallpaper images.
2	Format the images to meet the required specifications as described in the table above.
3	Rename the wallpaper image files in this format: For wallpaper images, use wallpaper-xxx.png. Replace xxx with your desired name. For example, wallpaper-blue.png, wallpaper-darkgreen.png For wallpaper thumbnail images, use thumbnail-xxx.png. Replace xxx with your desired name. For example, thumbnail-blue.png, thumbnail-darkgreen.png The system cannot utilize wallpaper files that are named using different patterns. However, for the logo file, you have the flexibility to name it as per your requirements.

Create a general management file

The system uses the List.xml file to manage the wallpaper and logo files. In the file, you can specify the wallpapers and the logo available in the phone appearance settings. The List.xml file must be uploaded to the repository where you store the image files.

Here is an example of the definitions in a general management file:

<CiscoIPPhoneImageList version="1.0">
<!-- Please Add Images to the end of the list-->

<ImageItem Name="Blue"
Image="TFTP:Desktops/1024x600x24/wallpaper-blue.png"
Thumbnail="TFTP:Desktops/1024x600x24/thumbnail-blue.png"
Theme = "dark"/>

<ImageItem Name="Purple"
Image="TFTP:Desktops/1024x600x24/wallpaper-purple.png"
Thumbnail="TFTP:Desktops/1024x600x24/thumbnail-purple.png"
Theme = "dark"/>

<ImageItem Name="logo"
Image="TFTP:Desktops/1024x600x24/logo.png"/>

</CiscoIPPhoneImageList>

Table 3. Elements in the List.xml file
Element	Description	Example
Root element	Make sure you include the root element `CiscoIPPhoneImageList` in your XML file. When you update the XML file, make sure you change the version number as well. Otherwise, the system won't load your updates.	`<CiscoIPPhoneImageList version="1.0"> </CiscoIPPhoneImageLis>`
Wallpaper item element	You can add multiple `ImageItem` elements. Each element contains the information for a particular wallpaper file and has the following four parameters: `Name=`: The display name of the wallpaper in the appearance settings. `Image=`: Specifies the TFTP path of the image file as `TFTP:Desktops/1024x600x24/wallpaper-xxx.png`, where replace wallpaper-xxx.png with your wallpaper filename. `Thumbnail=`: Specifies the file path of the wallpaper thumbnail file as `TFTP:Desktops/1024x600x24/thumbnail-xxx.png`, where replace thumbnail-xxx.png with your actual thumbnail filename. `Theme=`: Specifies the default color theme when the phone uses the default custom wallpaper that the administrator specifies. If the color mode isn't specified, it defaults to the light theme. This parameter doesn't apply when access to the appearance settings is enabled. Options: dark, light	`<ImageItem Name="Blue" Image="TFTP:Desktops/1024x600x24/wallpaper-blue.png" Thumbnail="TFTP:Desktops/1024x600x24/thumbnail-blue.png" Theme = "dark"/>`
Logo item element	Your phone supports only one logo to be added. The logo item element also uses the `ImageItem` element but has the following two parameters. `Name="logo"`: Include `Name="logo"` as is in your XML file. Don't change the value. The system uses it to identify the logo file. `Image=`: Specifies the TFTP path of the logo file as `TFTP:Desktops/1024x600x24/xxx.png`, where replace xxx.png with your actual logo filename.	`<ImageItem Name="logo" Image="TFTP:Desktops/1024x600x24/logo.png"/>`

The following figure shows the user interface elements of Appearance settings:

1.	The logo image
2.	The thumbnail image of the wallpaper
3.	The display name of the wallpaper
4.	The logo switch The logo switch allows users to decide whether they want to display the logo when they have access to the Appearance settings. The switch becomes available upon applying the List.xml file, which contains the specified logo image element.
5.	The color theme toggle

Before you begin

Obtain the file path on the TFTP server that you've uploaded the wallpaper and logo images to.

1	Create a new file with your text editor or XML editor.
2	Add the elements with the information of your image files included. The file path and file names are case-sensitive. Make sure you enter them correctly.
3	Save the file as List.xml.

Upload files to the TFTP server

Upload the List.xml file and all your wallpaper and logo image files to the path Desktops/1024x600x24 on the TFTP server. After you apply the custom wallpaper settings on Cisco Unified Communications Manager, your phones download the images from the server.

1	On Cisco Unified Communications Manager Administration, select Cisco Unified OS Administration in the Navigation field and click Go.
2	Select Software Updates > TFTP File Management > Upload File.
3	Click Choose File and select the file to upload in your local drive.
4	Specify the upload directory for the wallpaper image.
5	Click Upload File.
6	Repeat Step 3 through Step 5 to upload more files.

What to do next

Restart the TFTP server.

Restart the TFTP server

To apply the changes that you've made, restart the TFTP server.

1	On Cisco Unified Communications Manager Administration, select Cisco Unified Serviceability in the Navigation field and click Go.
2	Navigate to Tools > Control Center - Feature Services.
3	Select your server and click Go.
4	Select Cisco TFTP in the CM Services section.
5	Click Restart.

Configure the wallpaper settings on Cisco Unified Communications Manager Administration

As an administrator, you can designate the wallpaper image that will be applied to the deployed phones. If you grant users access to the appearance settings on their phones, they can choose whether to display the logo and select their preferred wallpaper from the provided options. However, if you do not grant them access, the appearance settings will be hidden on the phones.

Before you begin

Before you start configuring the wallpaper settings on Cisco Unified Communications Manager Administration, finish the following actions first:

Prepare your wallpaper and logo images
Create a general management file (List.xml)
Upload the List.xml file and the image files to the TFTP server

1	Log in to Cisco Unified Communications Manager Administration.
2	Navigate to Device > Device Settings > Common Phone Profile.
3	Locate and click the profile that your phones are using.
4	In the Common Phone Profile Information section, check the check box of Enable End User Access to Phone Background Image Setting if you want to allow users to change the phone screen background image. Otherwise, leave the check box unchecked.
5	Go to the Product Specific Configuration Layout section and enter the filename of the wallpaper image file in the Background Image field. It's important to enter the exact filename that you specified in the List.xml file. If you enter a wrong filename, the system will fail to load the wallpaper.
6	Click Save and then Apply Config.
7	Restart the phones.

Customize wallpaper by sending XML to the phone

In addition to uploading a prepared XML file to a TFTP server, you can also directly send an XML request to the phone to customize the wallpaper of the phone and KEM screens.

Do one of the following actions as needed:

To configure all deployed phones, go to System > Enterprise Phone Configuration.
To configure phones sharing the same phone profile, go to Device > Device Settings > Common Phone Profile.
To configure an individual phone, go to Device > Phone. Then find your phone and open the Phone Configuration page.

Set Phone Personalization to Enabled.

Associate the phone to the user.

Select User Management > User.
Find and locate the user that you want to configure.
In the Device Information section, click Device Associate.
Find and select the device, and then click Save Selected/Changes.

Prepare an HTML file that contains the XML information specified for customized wallpaper.

Here's an example of the HTML file:

<HTML>
<HEAD>
</HEAD>
<BODY>

<FORM action="<Phone_IP_Address>" Method="POST">
<TEXTAREA NAME="XML" Rows="8" Cols="100">
<setBackground>
<background name="<Name>" theme="<light/dark>">
<image><File_Path></image>
<thumbnail><File_Path></thumbnail>
<kem><File_Path></kem>
</background>
</setBackground>
</TEXTAREA>
<BR>
<input type="submit" value="POST to bumblebee"/> <P>
</FORM>

</BODY>
</HTML>

Element	Description	Example
FORM	IP address of the phone	`<FORM action="http://10.74.23.246/CGI/Execute" Method="POST">`
setBackground	Make sure you include the root element in the HTML file.	`<setBackground> </setBackground>`
background	The value of the attribute "name" will be displayed on the phone. "theme" defines the default theme of the wallpaper.	`<background name="Sunset" theme="light">`
image	File path of the wallpaper image. The PNG format is only supported.	`<image>http://10.79.63.28/wallpaper-sunset.png</image>`
thumbnail	File path of the wallpaper thumbnail image.	`<thumbnail>http://10.79.63.28/thumbnail-sunset.png</thumbnail>`
kem	File path of the wallpaper image for the phone Key Expansion Module (KEM). It's an optional element.	`<kem>http://10.79.63.28/lajiang/wallpaper-sunset.png</kem>`

Save and file to your local disk, and open it with a web browser, and then click the button.

The wallpaper will be pushed to the phone. When the configuration is complete, the users can view and set the wallpaper as usual on the phone screen.

(Optional) To remove the custom wallpaper from the phone, do the following:

Make sure that the <image> element is empty, other elements can remain the same. For example:
```
<image></image>
```
Save the file, open it with a browser, and then click the button.

The previously downloaded wallpaper will be removed from the phone. The default wallpaper setting will be applied to the phone.

Configure Application Dial Rules

Cisco Unified Communications Manager supports application dial rules that allow you to add and sort the priority of dialing rules for applications. Application dial rules automatically strip numbers from or add numbers to telephone numbers that the user dials. For example, the dial rules automatically add the digit 9 in front of a 7-digit telephone number to provide access to an outside line.

1	In Cisco Unified Communications Manager Administration, go to Call Routing > Dial Rules > Application Dial Rules.
2	Click Add New to create a new application dial rule, or choose an existing application dial rule to edit it.
3	Fill in the following fields: Name This field comprises a unique name for the dial rule that can contain up to 20 alphanumeric characters and any combination of spaces, periods (.), hyphens (-), and underscore characters (_). Description This field comprises a brief description that you enter for the dial rule. Number Begins With This field comprises the initial digits of the directory numbers to which you want to apply this application dial rule. Number of Digits This required field comprises the initial digits of the directory numbers to which you want to apply this application dial rule. Total Digits to be Removed This required field comprises the number of digits that you want Cisco Unified Communications Manager to remove from directory numbers that apply to this dial rule. Prefix With Pattern This required field comprises the pattern to prepend to directory numbers that apply to this application dial rule. Application Dial Rule Priority This field displays when you enter the Prefix With Pattern information. The field allows you to set the priority order of the application dial rules.
4	Click Save.

Configure your phone for power saving (Office Hours)

To conserve power and ensure the longevity of the phone screen display, you can set the Office Hours feature to turn off the display when it is not needed.

When the Office Hours feature is enabled, the phone goes into Display-Off Mode after working hours. You can light up the display by pressing any key on the phone. The display remains on until the phone has been in idle for a designated length of time, then it turns off automatically.

Do one of the following actions as needed:

To configure all deployed phones, go to System > Enterprise Phone Configuration.
To configure phones sharing the same phone profile, go to Device > Device Settings > Common Phone Profile.
To configure an individual phone, go to Device > Phone. Then find your phone and open the Phone Configuration page.

Customize the office hours settings with the following parameters.

Table 4. Parameters for Office Hours
Parameter	Default and options	Description
Enable Office Hours	Default: Enabled Options: Enabled, Disabled	Check this option to enable the Office Hours feature for Cisco Desk Phone 9800 Series. The Office Hours feature is designed to minimize power usage during inactivity periods on the phone. You can configure the phone to automatically turn off the screen outside of the designated working periods.
Work Days	Default: Monday through Friday	Customize the workdays by holding down the Ctrl key and selecting the desired days. During non-workdays, the phone will automatically turn off the screen. By default, workdays are set from Monday to Friday. Set working hours for workdays using the Working Hour Start and Working Hour End fields.
Working Hours Start	Default: 07:00	Set the start time for working hours using the 24-hour format. Outside of the specified working hours, the phone will automatically turn off the screen. Examples: 09:00 for 09:00 am; 17:30 for 05:30 pm
Working Hours End	Default: 19:00	Set the end time for working hours using the 24-hour format. Outside of the specified working hours, the phone will automatically turn off the screen. Examples: 09:00 for 09:00 am; 17:30 for 05:30 pm Ensure that the interval between the start and end time longer than 60 minutes.
Display Off Idle Timeout	Default: 5 Options: 1-60	Set the timeout period in minutes for the phone to automatically turn off the screen after being awakened during Display-Off Mode.

Select Save.

Select Apply Config.

Control the settings menu access

The Cisco Video Phone includes the following configuration menus:

About this device: Shows basic information about the phone device.
Issues and diagnostics: Displays the current status of the phone. If the phone has any issue, the menu displays the detailed information, for example, Network failed, Reg failed, Upgrade failed, and so on. In this menu, you can also report the problem and check the phone's statistics information.
Language and region:
- Time settings: Provides a configuration option to choose the time format.
- Language: Provides a configuration option to choose the display language on the phone.
Audio:
- Bluetooth: Toggle on or off the Bluetooth connectivity.
- Ringtone and volume: Specifies a different ringtone to a specific line, adjusts audio volume.
- Microphone: Sets up the noise removal feature and others.
- Aux port: Chooses the use purpose of the Aux port, for headset connection or log collection.
Screen and video:
- Brightness: Adjusts up the phone's default brightness.
- Appearance: Chooses a different color theme on the phone.
Network and service:
- Network connection: Provides options for viewing and configuring network settings such as Wi-Fi and Ethernet.
- Security setup: Provides options for viewing and configuring security settings such as security mode and Locally Significant Certificate (LSC) update.
Restart and reset:
- Restart: Restarts the phone.
- Reset security certificate: Resets security certificate to factory defaults.
- Factory reset: Restores the phone to factory settings. All data will be erased and the user must reactivate the phone after the factory reset.

You can control whether a phone has access to the Settings menu or to options on this menu by using the Cisco Unified Communications Manager Administration Phone Configuration.

1	In Cisco Unified Communications Manager Administration, select Device > Phone.
2	Locate the phone that you will set up.
3	Navigate to the Product Specific Configuration area and set the Settings Access field. Enabled: Allows access to the Settings menu. Disabled: Prevents access to the Settings menu. In this case, the user can't find any menus on the Settings menu. The Settings menu is empty. Restricted: Allows access only to the Audio related sub-menus. Prevents access to other options on the Settings menu.
4	Select Save.
5	Select Apply Config.
6	Restart the phone.

Set up date and time group

You can select a predefined date and time group for a device pool in the Cisco Unified Communications Manager Administration. If your desired group is not in the list, you can create a new group or modify an existing one.

1	In Cisco Unified Communications Manager Administration, select System > Device Pool.
2	Locate the device pool that you need to set up.
3	Navigate to the Roaming Sensitive Settings area and select a group from the Date/Time Group field.
4	Select Save.
5	(Optional) If you want to create or modify a Date/Time group, do the following: Select System > Date/Time Group. Navigate to the Date/Time Group Information area, set the following parameters: Group Name: Enter a unique for the Date/Time group. Time Zone: Select a proper time zone for the Date/Time group. Time Format: Select a time format that the phone displays. For the parameters "Separator" and "Date Format", the settings of them don't take effect. Select Save.

Set up Do Not Disturb

When Do Not Disturb (DND) is turned on, either no audible rings occur during the ringing-in state of a call, or no audible or visual notifications of any type occur.

You can configure the phone with a softkey template with DND as one of the selected features.

For more information, see the " Configure Software-Based Endpoints" chapter in System Configuration Guide for Cisco Unified Communications Manager, Release 11.5(1) or later.

1	Sign into Cisco Unified Communications Manager Administration as an administrator.
2	Select Device > Phone.
3	Locate the phone that you will set up.
4	Navigate to the Do Not Disturb pane, set the following parameters: Do Not Disturb: This check box allows you to enable or disable DND on the phone. DND Option: Ring Off, Call Reject, or Use Common Phone Profile Setting. Do not choose Call Reject if you want priority (MLPP) calls to ring this phone when DND is turned on. DND Incoming Call Alert: Choose the type of alert (Disable, Flash Only or Beep Only) to play on a phone for incoming calls when DND is active. For the parameters DND Option and DND Incoming Call Alert, both can be found in the Common Phone Profile window (Device > Device Settings > Common Phone Profile) and the Phone Configuration window (Device > Phone). The setting in the Phone Configuration window takes precedence.
5	Click Save.

Set up forward all

You can set up the phone to redirect incoming calls to another phone number or to your voicemail by using the Cisco Unified Administration Manager.

1	Sign into Cisco Unified Communications Manager Administration.
2	Select Device > Phone.
3	Locate the phone that you will set up.
4	Select the target line from the Association pane.
5	Navigate to the Call Forward and Call Pickup Settings pane, enter a forwarded-to destination number in the field Forward All.
6	Click Save.

Set up call forward notification

You can control the call forward settings by using the Cisco Unified Communications Manager. The Call Forward Notification feature allows you to configure the information that the user sees when receiving a forwarded call.

Sign into Cisco Unified Communications Manager Administration.

Select Device > Phone.

Locate the phone that you will set up.

Select the target line from the Association pane.

Navigate to the Forwarded Call Information Display on Device pane, set the following parameters:

Parameter	Description
Caller Name	When this check box is checked, the caller name displays in the notification window. By default, this check box is checked.
Caller Number	When this check box is checked, the caller number displays in the notification window. By default, this check box is not checked.
Redirected Number	When this check box is checked, the information about the caller who last forwarded the call displays in the notification window. Example: If Caller A calls B, but B has forwarded all calls to C and C has forwarded all calls to D, the notification box that D sees contains the phone information for caller C. By default, this check box is not checked.
Dialed Number	When this check box is checked, the information about the original recipient of the call displays in the notification window. Example: If Caller A calls B, but B has forwarded all calls to C and C has forwarded all calls to D, then the notification box that D sees contains the phone information for caller B. By default, this check box is checked.

Select Save.

Add speed-dial numbers

You can set up a phone to add speed-dial numbers from the Cisco Unified Communications Manager. So the user can call the people by using the numbers directly.

1	In Cisco Unified Communications Manager Administration, select Device > Phone.
2	Locate the phone that you will set up.
3	In the Phone Configuration window, select Add a new SD.
4	Enter valid speed-dial numbers in the Number fields.
5	Enter the related texts in the Label fields. These texts will display on the phone screen.
6	Click Save.

Configure park monitoring

Park monitoring is supported only when a phone parks a call. Park monitoring then monitors the status of a parked call. The park monitoring call alert does not clear until the parked call gets retrieved or is abandoned by the parked call. This parked call can be retrieved by using the same call alert on the phone that parked the call.

For more information about how to configure park monitoring in Cisco Unified Communications Manager, see Feature Configuration Guide for Cisco Unified Communications Manager, Release 12.5(1) or later.

Set up park monitoring timers

Cisco Unified Communications Manager Administration provides three cluster-wide service timer parameters for park monitoring: Park Monitoring Reversion Timer, Park Monitoring Periodic Reversion Timer, and Park Monitoring Forward No Retrieve Timer. Each service parameter includes a default and requires no special configuration. These timer parameters are for park monitoring only; the Call Park Display Timer and Call Park Reversion Timer are not used for park monitoring. See the following table for descriptions of these parameters.

Configure the timers in the Cisco Unified Communications Manager Service Parameters page.

In Cisco Unified Communications Manager Administration, choose System > Service Parameters.

Select a server for the phone and the service Cisco CallManager (Active).

In the Clusterwide Parameters (Feature - General) section, set the fields as described in the following table.

Table 5. Service parameters for park monitoring
Field	Description
Park Monitoring Reversion Timer	This parameter determines the number of seconds that Cisco Unified Communications Manager waits before prompting the user to retrieve a call that the user parked. This timer starts when the user parks an active call on the phone, and a reminder is issued when the timer expires. Default is 60 seconds. You can override the value that this service parameter specifies on a per-line basis in the Park Monitoring section of the Directory Number Configuration window (in Cisco Unified Communications Manager Administration, choose Call Routing > Directory Number). Specify a value of 0 to immediately utilize the periodic reversion interval that the Park Monitoring Periodic Reversion Timer service parameter specifies. (See the description that follows.) For example, if this parameter is set to zero and the Park Monitoring Periodic Reversion Timer is set to 15, the user is immediately prompted about the parked call and every 15 seconds thereafter until the Park Monitoring Forward No Retrieve Timer (see the description that follows) expires.
Park Monitoring Periodic Reversion Timer	This parameter determines the interval (in seconds) that Cisco Unified Communications Manager waits before prompting the user again that a call is parked. To connect to the parked call, the user can simply go off-hook during one of these prompts. Cisco Unified Communications Manager continues to prompt the user about the parked call as long as the call remains parked and until the time that the Park Monitoring Forward No Retrieve Timer (see the description that follows) specifies expires. Specify a value of 0 to disable periodic prompts about the parked call. Default is 30 seconds.
Park Monitoring Forward No Retrieve Timer	This parameter determines the number of seconds that park reminder notifications occur before the parked call forwards to the Park Monitoring Forward No Retrieve destination that is specified in the parker's Directory Number Configuration window. (If no forward destination is provided in Cisco Unified Communications Manager Administration, the call returns to the line that parked the call.) This timer starts when the time that the call is parked. When Park Monitoring Reversion Timer and Park Monitoring Forward No Retrieve Timer expire, the call is removed from park and forwards to the specified destination or returns to the parker line. Default is 300 seconds.

Set up park monitoring for directory numbers

The Directory Number Configuration window contains a Park Monitoring area where you can configure the three parameters.

In Cisco Unified Communications Manager Administration, choose Call Routing > Directory Number.

Click Find and select the directory number on which you want to configure the park monitoring.

In the Park Monitoring section, set the fields as described in the following table.

Table 6. Park monitoring parameters
Field	Description
Park Monitoring Forward No Retrieve Destination External	When the parkee is an external party, the call forwards to the specified destination in the parker's Park Monitoring Forward No Retrieve Destination External parameter. If the field is empty, the parkee is redirected to the parker line.
Park Monitoring Forward No Retrieve Destination Internal	When the parkee is an internal party, the call forwards to the specified destination in the parker’s Park Monitoring Forward No Retrieve Destination Internal parameter. If the field is empty, the parkee is redirected to the parker line.
Park Monitoring Reversion Timer	This parameter determines the number of seconds that Cisco Unified Communications Manager waits before prompting the user to retrieve a call that the user parked. This timer starts when the user parks a call on the phone, and a reminder is issued when the timer expires. Default: 60 seconds If you configure a nonzero value, this value overrides the value of this parameter set in the Service Parameters window. However, if you configure a value of 0 here, then the value in the Service Parameters window is used.

Set up park monitoring for hunt lists

When a call that was routed via the hunt list is parked, the Park Monitoring Forward No Retrieve Destination parameter value is used (unless it is empty) when the Park Monitoring Forward No Retrieve Timer expires.

1	In Cisco Unified Communications Manager Administration, choose Call Routing > Route/Hunt > Hunt Pilot.
2	Click Find and select the hunt pilot on which you want to configure the park monitoring.
3	Set the Park Monitoring Forward No Retrieve Destination parameter. If the field is empty, the call forwards to the destination that is configured in the Directory Number Configuration window when the Park Monitoring Forward No Retrieve Timer expires.

Set the label for a line

You can set up a phone to display a text label instead of the directory number. Use this label to identify the line by name or function. For example, if your user shares lines on the phone, you could identify the line with the name of the person that shares the line.

1	In Cisco Unified Communications Manager Administration, select Device > Phone.
2	Locate the phone to be configured.
3	Locate the line instance and set the Line Text Label field.
4	If you want to apply the label to other devices that share the line, check the Update Shared Device Settings check box and click Propagate Selected.
5	Click Save.

Use problem report tool

Users can submit problem reports to you with the Problem Report Tool.

The Problem Report Tool logs are required by Cisco TAC when troubleshooting problems. The logs are cleared if you restart the phone. Collect the logs before you restart the phones.

To issue a problem report, users access the Problem Report Tool and provide the date and time that the problem occurred, and a description of the problem.

If the PRT upload fails, you can access the PRT file for the phone from the URL http://<phone-ip-address>/FS/<prt-file-name>. This URL is displayed on the phone in the following cases:

If the phone is in the factory default state. The URL is active for 1 hour. After 1 hour, the user should try to submit the phone logs again.
If the phone has downloaded a configuration file and the call control system allows web access to the phone.
The Customer Support Upload URL field isn't configured correctly.
You must add a server address to the Customer Support Upload URL field on Cisco Unified Communications Manager.
The phone isn't assigned with an IP address.

If you are deploying devices with Mobile and Remote Access (MRA) through Expressway, you must also add the PRT server address to the HTTP Server Allow list on the Expressway server.

Configure a customer support upload URL

You must use a server with an upload script to receive PRT files. The PRT uses an HTTP POST mechanism, with the following parameters included in the upload (utilizing multipart MIME encoding):

devicename (example: “SEP001122334455”)
serialno (example: “FCH12345ABC”)
username (the username configured in Cisco Unified Communications Manager, the device owner)
prt_file (example: “probrep-20141021-162840.tar.gz”)

A sample script is shown below. This script is provided for reference only. Cisco does not provide support for the upload script installed on a customer's server.

<?php

// NOTE: you may need to edit your php.ini file to allow larger

// size file uploads to work.

// Modify the setting for upload_max_filesize

// I used: upload_max_filesize = 20M

// Retrieve the name of the uploaded file

$filename = basename($_FILES['prt_file']['name']);

// Get rid of quotes around the device name, serial number and username if they exist

$devicename = $_POST['devicename'];

$devicename = trim($devicename, "'\"");

$serialno = $_POST['serialno'];

$serialno = trim($serialno, "'\"");

$username = $_POST['username'];

$username = trim($username, "'\"");

// where to put the file

$fullfilename = "/var/prtuploads/".$filename;

// If the file upload is unsuccessful, return a 500 error and

// inform the user to try again

if(!move_uploaded_file($_FILES['prt_file']['tmp_name'], $fullfilename)) {

header("HTTP/1.0 500 Internal Server Error");

die("Error: You must select a file to upload.");

}

?>

The phones only support HTTP URLs.

1	Set up a server that can run your PRT upload script.
2	Write a script that can handle the parameters listed above, or edit the provided sample script to suit your needs.
3	Upload your script to your server.
4	In Cisco Unified Communications Manager, go to the Product Specific Configuration Layout area of the individual device configuration window, Common Phone Profile window, or Enterprise Phone Configuration window.
5	Check Customer support upload URL and enter your upload server URL. Example: http://example.com/prtscript.php
6	Save your changes.

Assured Services SIP

Assured Services SIP(AS-SIP) is a collection of features and protocols that offer a highly secure call flow for Cisco IP Phones and third-party phones. The following features are collectively known as AS-SIP:

Differentiated Services Code Point (DSCP)
Transport Layer Security (TLS) and Secure Real-time Transport Protocol (SRTP)
Internet Protocol version 6 (IPv6)

To configure AS-SIP, complete the following tasks on Cisco Unified Communications Manager:

Configure a Digest User—Configure the end user to use digest authentication for SIP requests.
Configure SIP Phone Secure Port—Cisco Unified Communications Manager uses this port to listen to SIP phones for SIP line registrations over TLS.
Restart Services—After configuring the secure port, restart the Cisco Unified Communications Manager and Cisco CTL Provider services. Configure SIP Profile for AS-SIP-Configure a SIP profile with SIP settings for your AS-SIP endpoints and for your SIP trunks. The phone-specific parameters are not downloaded to a third-party AS-SIP phone. They are used only by Cisco Unified Manager. Third-party phones must locally configure the same settings.
Configure Phone Security Profile for AS-SIP—You can use the phone security profile to assign security settings such as TLS, SRTP, and digest authentication.
Configure AS-SIP Endpoint—Configure a Cisco IP Phone or a third-party endpoint with AS-SIP support.
Associate Device with End User—Associate the endpoint with a user.
Configure SIP Trunk Security Profile for AS-SIP—You can use the sip trunk security profile to assign security features such as TLS or digest authentication to a SIP trunk.
Configure SIP Trunk for AS-SIP—Configure a SIP trunk with AS-SIP support.

For detailed information about configuring AS-SIP, see the " Configure AS-SIP Endpoints" chapter, in System Configuration Guide for Cisco Unified Communications Manager, Release 11.5(1) or later.

Set up wideband codec

By default, the G.722 codec is enabled for your phone. If Cisco Unified Communications Manager (Unified CM) is configured to use G.722 and the far endpoint supports G.722, the call connects using the G.722 codec in place of G.711.

This situation occurs regardless of whether the user has enabled a wideband headset or wideband handset. If either the headset or handset is enabled, the user may notice greater audio sensitivity during the call. Greater sensitivity means improved audio clarity but also means that the far endpoint can hear more background noise, such as rustling papers or nearby conversations. Even without a wideband headset or handset, some users may find the additional sensitivity of G.722 distracting.

The Advertise G.722 and iSAC Codec service parameter affects whether wideband support exists for all devices that register with this Cisco Unified CM server or for a specific phone.

To configure wideband support for all devices:

On Cisco Unified Communications Manager Administration, click System > Enterprise Parameters
Set the Advertise G.722 and iSAC Codec field.

The default value of this enterprise parameter is True, which means that all Cisco IP Phone Models that register to this Cisco Unified CM advertise G.722. If each endpoint in an attempted call supports G.722 in the capabilities set, Cisco Unified CM uses that codec for the call whenever possible.

To configure wideband support for a specific device:

On Cisco Unified Communications Manager Administration, choose Device > Phone.
Set the Advertise G.722 and iSAC Codec parameter in the Product Specific Configuration area.

The default value of this product-specific parameter is to use the value that the enterprise parameter specifies. If you want to override this on a per-phone basis, choose Enabled or Disabled

Set up the audio and video port range

Audio and video traffic can be sent to different RTP port ranges in order to improve Quality of Service (QoS).

The following fields control the port ranges in Cisco Unified Communications Manager Administration:

Audio ports
- Start Media Port (default: 16384)
- Stop Media Port (default: 32766)
Video ports
- Start Video (This is to set the video start port).
  - Minimum: 2048
  - Maximum: 65535
- Stop Video (This is to set the video stop port)
  - Minimum: 2048
  - Maximum: 65535

The following rules apply when configuring the video port fields:

After the Start Video RTP Port and Stop Video RTP Port are configured, the phone uses ports within the video port range for video traffic. The audio traffic uses the media ports.
If the audio and video port ranges overlap, the overlapped ports carry both audio and video traffic. If the video port range isn’t configured correctly, the phone uses the configured audio ports for both audio and video traffic.

For more information, see the documentation for your particular Cisco Unified Communications Manager release.

1	In Cisco Unified Communications Manager Administration, select Device > Device Settings > SIP Profile
2	Set the Start Media Port and Stop Media Port fields for the audio port range.
3	Select Save.
4	Navigate to one of the following windows: System > Enterprise Phone Configuration Device > Device Settings > Common Phone Profile Device > Phone > Phone Configuration
5	Set the Start Video RTP Port and Stop Video RTP Port fields for the range of ports required. The value for Stop Video RTP Port must be at least 16 larger than the value for Start Video RTP Port.
6	Select Save.

Video transmit resolution setup

Cisco Video Phone 8875 supports the following video formats:

1080p (1920x1080)
720p (1280x720)
600p (1024x600)–Default
WVGA (800x480)
VGA (640x480)
360p (640x360)
CIF (352x288)
240p (432x240)
SIF (352x240)
QCIF (176x144)

The phone negotiate the best bandwidth and resolution based on the phone configuration and phone screen limitations.

The following table shows the resolutions, frames per second, and video bit rate range for each of the supported video types.

Table 7. Supported video types
Video type	Video resolution	Frames per second (fps)	Video bit rate range
1080p	1920 x 1080	30	3500–4000 kbps
1080p	1920 x 1080	15	2667–4000 kbps
720p	1280 x 720	30	2040–3750 kbps
720p	1280 x 720	15	1185–3750 kbps
600p	1024 x 600	30	1584–3000 kbps
600p	1024 x 600	15	840–3000 kbps
WVGA	800 x 480	30	990–1500 kbps
WVGA	800 x 480	15	525–1500 kbps
VGA	640 x 480	30	520–1500 kbps
VGA	640 x 480	15	280–1500 kbps
360p	640 x 360	30	600–1350 kbps
360p	640 x 360	15	315–1350 kbps
240p	432 x 240	30	270–525 kbps
240p	432 x 240	15	96–525 kbps
CIF	352 x 288	30	200–350 kbps
CIF	352 x 288	15	120–350 kbps
SIF	352 x 240	30	200–350 kbps
SIF	352 x 240	15	120–350 kbps
QCIF	176 x 144	30	94–350 kbps
QCIF	176 x 144	15	64–350 kbps
QCIF	176 x 144	15	17–350 kbps

Set up barge

You can set up the phone to allow a user to join a remotely active (conference) call on a shared line.

For more information about how to set up barge in Cisco Unified Communications Manager, see Feature Configuration Guide for Cisco Unified Communications Manager, Release 12.5(1) or later.

Set up password protection for the settings menu

You can secure the phone settings menu with the password protection. Once enabled, the users are required to provide the correct password to access the settings menu.

1	Sign into Cisco Unified Communications Manager Administration as an administrator.
2	Select Device > Device Settings > Common Phone Profile
3	Locate the profile that you want to set up.
4	Navigate to the Common Phone Profile Information pane and set up a password in the Local Phone Unlock Password field.
5	Click Save.
6	Click Apply Config.
7	Restart the phones.

Set up call recording

You can enable the call recording feature on a phone so that the users can record an active call or call conference.

Only the user who triggers the call recording might receive an audible alert to indicate that the call is being recording. The other connected parties don't receive any audible alert for the recording.

You can set whether the alert sound will be audible to both the user who triggers the recording and to other connected parties.

When an active call is being recorded, the user can receive or place intercom calls. However, if the user places an intercom call, the active call is put on hold. This action causes the recording session to terminate.

For more information, see the Monitoring and Recording section in Feature Configuration Guide for Cisco Unified Communications Manager, Release 12.5(1) or later .

1	In Cisco Unified Communications Manager Administration, add the softkey Record (Record). For more information, see Configure feature soft buttons with a softkey template.
2	Apply the new or updated softkey template to a phone. For more information, see Apply a softkey template to a phone.
3	Enable Built in Bridge field for the phone. Choose Device > Phone. Click Find to locate the phone that you want to configure. From the Built in Bridge drop-down list, choose On to enable it Click Save.
4	Configure a phone line for recording. Choose Device > Phone. Click Find to locate the phone that you configured. In the left Association pane, click a phone line for the recording setup. From the Recording Option drop-down list, choose Selective Call Recording Enabled. From the Recording Profile drop-down list, choose a recording profile that is configured for the line. For more information about how to create a new recording profile, see the Create a Recording Profile section in Feature Configuration Guide for Cisco Unified Communications Manager, Release 12.5(1) or later . Click Save.

Set up join and direct transfer

You can set up the Join and Direct Transfer feature on a phone. If you enable the feature, the users can quickly add a person into a conference call or transfer a call through the Calls tab displayed in the new call session. You can also change the scope of the calls listed in the tab.

1	Do one of the following actions from Cisco Unified CM Administration: To set up the feature for a specific phone: Choose Device > Phone and locate the phone that you want to set up. To set up the feature for a group of phones: Choose Device > Device Settings > Common Phone Profile and locate the profile that you want to set up. To set up the feature for all phones: Choose System > Enterprise Phone Configuration.
2	Set up the field Join And Direct Transfer Policy: Same line, across line enable: All active calls can be transferred or joined. The Calls tab displays in the new call session. It shows all active calls from all lines on the phone. Same line enable only: Only active calls in the same line can be transferred or joined. The Calls tab displays in the new call session. It only shows the active calls from a selected line. Same line, across line disable: No active calls can be transferred or joined. The Calls tab in the new call session doesn't display.
3	Click Save.

Multilevel Precedence and Preemption

Multilevel Precedence and Preemption (MLPP) allows you to prioritize calls during emergencies or other crisis situations. You assign a priority to your outgoing calls that range from 1 to 5. Incoming calls display an icon and the call priority. Authenticated users can preempt calls either to targeted stations or through fully subscribed TDM trunks.

This capability assures high-ranking personnel of communication to critical organizations and personnel.

MLPP is often used with Assured Services SIP(AS-SIP). For detailed information about configuring MLPP, see the chapter Configure Multilevel Precedence and Preemption in Feature Configuration Guide for Cisco Unified Communications Manager.

IPv6 ready logo setup

Define the IPv6 interface identifier for the device. The interface identifier you choose, either MAC or Opaque, will determine the method that is used for generating part of the IPv6 address. This is applicable to both link-local IPv6 addresses and Stateless Address Auto Configuration (SLAAC) addresses. The address contains a 64-bit prefix and a 64-bit interface identifier generated by the device. With MAC, an EUI-64 based interface identifier is generated, as described in RFC-2373. With Opaque, a random 64-bit interface identifier is generated as described in RFC-7217 on the first boot of the device, and this is used forever, or until factory reset.

Configure Cisco IPMA

The Unified Communications Manager Assistant feature is a plug-in that an assistant can use to handle calls on behalf of a manager, intercept manager calls, and route them appropriately.

Manager Assistant supports up to 3500 managers and 3500 assistants. To accommodate this number of users, you can configure up to three Manager Assistant applications in one Unified Communications Manager cluster and assign managers and assistants to each instance of the application.

Manager Assistant supports shared line support and proxy line support.

For information about administration configuration for IPMA, see Manager Assistant in Feature Configuration Guide for Cisco Unified Communications Manager

Thanks for your feedback.