The Busy Lamp Field (BLF) feature enables you to monitor other users' lines. The following enhancements enable you to configure the BLF feature.

• If you have configured a BLF list for the phone, you can activate or deactivate monitoring of the entire list with the new BLF List setting. This setting is available on the Attendant console preferences menu of the phone. Setting it to Show activates monitoring of the BLF list. The phone assigns available line keys in sequence to monitor the BLF list entries, and starts showing the status of the monitored lines on the BLF keys. You can also access this setting on the phone administration web page, in Voice > Att Console > General.

  Note

  The Use Line Keys For BLF List setting has significance only when monitoring of the BLF list is active. This parameter controls whether the phone uses its own line keys for monitoring the BLF list. When it is set to No, the phone uses only the keys on any Key Expansion Module present for monitoring the BLF list.

• You can also configure line keys individually to monitor other users, if you allow it. Feature configuration on line keys has been enhanced to support BLF in addition to speed dial. Users can also add speed dial and call pick up to the BLF key configuration, if you allow these options. Use the new Customizable PLK options field in Voice > Att Console > General on the phone administration web page to control which options are allowed. To allow an option, add the option to this field. The speed dial option is added by default when you upgrade the phone firmware to this release, to keep the default behaviour of the phone consistent with the previous release.

  As in the previous release, you must disable line keys from functioning as extensions, to allow feature configuration on line keys on the phone. Also as in the previous release, you press and hold down a line key for two seconds to configure a feature on the line key.

  You can select any available line key to configure features. You can also select a line key that is functioning as a speed-dial key or as a BLF key. You cannot select keys on which you have configured other features.

  The phone subscribes to the BLF list URI that you specify, to be notified of changes in the status of monitored lines. If you do not specify a BLF list URI, the phone subscribes to $USER@$PROXY.

Where to Find More Information

• Cisco IP Phone 6800 Series Multiplatform Phones Administration Guide

• Cisco IP Phone 6800 Series Multiplatform Phones User Guide

• Cisco IP Phone 6800 Series Multiplatform Phones Provisioning Guide

You and your user can set the phones to display text in Catalan. On the phone administration web page, the Locale field in Voice > Regional contains the new ca-ES option.

Where to Find More Information

• Cisco IP Phone 6800 Series Multiplatform Phones Administration Guide

• Cisco IP Phone 6800 Series Multiplatform Phones Provisioning Guide

You can control when the phone reports its configuration to the provisioning server. This is in addition to the standard report upload that happens as part of the phone shutdown or restart.

Use the new Report to Server drop-down list on the phone administration web page, in Voice > Provisioning > Upload Configuration Options. When you choose On Local Change, the phone reports its configuration when any configuration parameter changes by an action on the phone or on the phone administration web page. The phone waits for a few seconds after a change is made, and then reports the configuration. This wait time is defined in the Upload Delay On Local Change field. Specify a value in number of seconds (10 minimum, 60 default, 900 maximum). This delay ensures that changes are reported to the web server in batches, rather than reporting a single change at a time.

Alternately, the phone can report its configuration at regular intervals. Choose Periodically in the Report to Server drop-down list. Then, in the Periodic Upload to Server field, specify an interval in number of seconds (600 minimum, 3600 default, 2592000 (30 days) maximum).

In all cases, the report rule that you specify defines the configuration report that the phone sends. Two report upload destination URLs are supported in the Report Rule field which provide flexibility in both destination and content of the uploaded report.

This feature has no user impact.

Where to Find More Information

• Cisco IP Phone 6800 Series Multiplatform Phones Administration Guide

• Cisco IP Phone 6800 Series Multiplatform Phones Provisioning Guide

You can now choose to include a device identifier for the phone in syslog messages that are uploaded to the syslog server. While the IP address of a phone may change over time, the device identifier does not change. This can ease the process of identifying the source of each message in a stream of incoming messages from multiple phones. The device identifier appears after the timestamp in each message.

On the phone administration web page, you will see a new field named Syslog Identifier in Voice > System > Optional Network Configuration. You can also configure this setting in the XML configuration file. You can choose the type of device identifier to include:

• none

• the MAC address of the phone, in the standard colon-separated format, or as continuous upper case or lower case letters and digits

• the product serial number of the phone

This feature has no user impact.

Where to Find More Information

• Cisco IP Phone 6800 Series Multiplatform Phones Administration Guide

• Cisco IP Phone 6800 Series Multiplatform Phones Provisioning Guide

Besides Feature Key Synchronization (FKS), you can also enable the do not disturb (DND) and call forwarding synchronization between the phone and the server through the XSI service. When both FKS and XSI Synchronization are enabled, FKS takes precedent over XSI Synchronization.

You use the new fields DND Enable and CFWD Enable on the phone administration web page to enable or disable this feature. When enabled, the settings of DND and call forwarding on the server are synchronized to the phone. The status changes made on the phone will also be synchronized to the server.

The fields are located in the XSI Line Service section from Voice > Ext (n).

Where to Find More Information

• Cisco IP Phone 6800 Series Multiplatform Phones Administration Guide

• Cisco IP Phone 6800 Series Multiplatform Phones Provisioning Guide

For Cisco IP Phone 6841 and 6851 Multiplatform Phones, the WideBand Handset Enable field enables or disables the phone to use a wideband handset. By default, the system configures this field against the phone's hardware version. The default setting is No for hardware version 00 and 01, and Yes for hardware version 02.

You can also change the setting as needed. If your phone is using a wideband handset, set this field to Yes.

The WideBand Handset Enable field is located in the General section of the Voice > Phone tab on the phone administration web page.

This feature has no user impact.

Where to Find More Information

Cisco IP Phone 6800 Series Multiplatform Phones Administration Guide

You can specify a compliance standard for the phone. When a compliance standard is specified, the acoustic parameters that conform to the specified standard are loaded to the phone.

You can specify the audio compliance standard from the phone administrator web page Voice > User > Audio Compliance. The options are: ETSI and TIA. TIA (A set of standards by Telecommunications Industry Association) is the default.

The feature has no user impact.

Where to Find More Information

• Cisco IP Phone 6800 Multiplatform Phones Administration Guide

• Cisco IP Phone 6800 Multiplatform Phones Provisioning Guide

Profile account authentication enables the phone to resynchronize the provisioning profile. You can specify a profile authentication type for phone users to use.

The new field Profile Authentication Type replaces the Profile Account Enable field on the phone administration web page. The available options are: Disabled, Basic HTTP Authentication, and XSI Authentication.

When you disable this feature, the phone user can't enter the authentication account on the phone screen. When you specify an authentication type, the phone user can use the provided credentials to resynchronize the provisioning profile either when prompted or through the Profile account setup menu on the phone screen.

If XSI Authentication is specified as the authentication type, you can use either XSI login credentials or SIP credentials to resynchronize the provisioning profile. Logging into XSI server with SIP credentials requires Broadsoft Broadworks 20.0 or later versions.

To use SIP credentials, set XSI Host Server, XSI Authentication Type (as SIP Credentials), SIP Auth ID, and SIP Password in the XSI Phone Service section from the Voice > Phone tab on the phone administration web page.

Where to Find More Information

• Cisco IP Phone 6800 Series Multiplatform Phones Administration Guide

• Cisco IP Phone 6800 Series Multiplatform Phones Provisioning Guide

• Cisco IP Phone 6800 Series Multiplatform Phones User Guide

The phone now supports RFC 8188-based HTTP content encryption with AES-128-GCM ciphering for configuration files. With this encryption method, any entity can read the HTTP message headers. However, only the entities that know the Input Keying Material (IKM) can read the payload. When the phone is provisioned with the IKM, the phone and the provisioning server can exchange configuration files securely, while allowing third-party network elements to use the message headers for analytic and monitoring purposes.

The new XML configuration parameter IKM_HTTP_Encrypt_Content holds the IKM on the phone. For security reasons, this parameter is not accessible on the phone administration web page. It is also not visible in the phone's configuration file, which you can access from the phone's IP address or from the phone's configuration reports sent to the provisioning server.

Note	The phone continues to support the AES-256-CBC encryption method. As in the previous release, you specify the AES-256-CBC key with the --key keyword in profile rules and report rules. Which of the two encryption and decryption methods the phone applies depends on the inputs that you provide.

If you want to use the RFC 8188-based encryption, ensure the following:

• Provision the phone with the IKM by specifying the IKM with the new XML parameter IKM_HTTP_Encrypt_Content in the configuration file that is sent from the provisioning server to the phone.

• If this encryption is applied to the configuration files sent from the provisioning server to the phone, ensure that the Content-Encoding HTTP header in the configuration file has "aes128gcm".

  In the absence of this header, the AES-256-CBC method is given precedence. The phone applies AES-256-CBC decryption if a AES-256-CBC key is present in a profile rule, regardless of IKM.

• If you want the phone to apply this encryption to the configuration reports that it sends to the provisioning server, ensure that there is no AES-256-CBC key specified in the report rule.

This feature has no user impact.

Where to Find More Information

• Cisco IP Phone 6800 Series Multiplatform Phones Provisioning Guide

• Cisco IP Phone 6800 Series Multiplatform Phones Administration Guide

You can initiate a phone problem report remotely. To do this, initiate a SIP-NOTIFY message from the server to the phone, with the Event specified as prt-gen. The phone generates a problem report using the Cisco Problem Report Tool (PRT), with the problem description "Remote PRT Trigger". If you have configured an upload rule for problem reports, the phone also uploads the problem report according to the upload rule.

You can see the status of the most recent problem report initiation on the phone administration web page > Info > Status. A new section called PRT Status shows the location of initiation and the status of the report generation, and the status of the report upload.

You can access a remotely-initiated problem report from the same location as locally-initiated problem reports on the phone administration web page.

This feature has no user impact.

Where to Find More Information

• Cisco IP Phone 6800 Series Multiplatform Phones Administration Guide

Your phone now supports early media negotiation and precondition signaling.

For an outgoing call, a SIP message from the phone includes the P-Early-Media header, which contains the status of the early media stream. If the status in the header is not indicating that the network is blocking the early media stream, the phone plays the early media instead of the ringback tone while waiting for the call to be connected.

Precondition signaling defers incoming call notifications until the phone receives the message that preconditions are satisfied to establish the call.

Where to Find More Information

• Cisco IP Phone 6800 Series Multiplatform Phones Administration Guide

You can now search for contacts by name in multiple directories simultaneously. The new All menu item in the Directories menu provides this function. The phone searches for the name in the following locations if Broadsoft directories are configured:

• All Broadsoft directories

  • Enterprise directory

  • Group directory (included in the Enterprise directory)

  • Enterprise Common directory

  • Group Common directory

  • Personal directory

• The LDAP directory, if configured

• The personal address book on the phone

The search function behaves in a similar manner to the name-search function within individual directories. The search results show both full and partial name matches. You can select a contact in the search results and then view contact details, add the contact to the personal address book, and call the contact. You can also edit the number before making the call.

Where to Find More Information

• Cisco IP Phone 6800 Series Multiplatform Phones User Guide

• Cisco IP Phone 6800 Series Multiplatform Phones Administration Guide

The following list contains the severity 1, 2, and 3 defects that are open for the Cisco IP Phone 6800 Series Multiplatform Phones that use Firmware Release 11.2(3).

For more information about an individual defect, you can access the online history for the defect by accessing the Bug Search tool and entering the Identifier (CSCxxnnnnn). You must be a registered Cisco.com user to access this defect information.

Because the defect status continually changes, the list reflects a snapshot of the defects that were resolved at the time this report was compiled. For an updated view of the resolved defects or to view specific bugs, access the Bug Search Toolkit as described in the View Caveats.

• CSCvn72142 The phone web page shows that PC port is Link Down when switch negotiate mode from 100MB full to auto

The following list contains the severity 1, 2, and 3 defects that are resolved for the Cisco IP Phone 6800 Series Multiplatform Phones that use Firmware Release 11.2(3).

For more information about an individual defect, you can access the online history for the defect by accessing the Bug Search tool and entering the Identifier (CSCxxnnnnn). You must be a registered Cisco.com user to access this defect information.

Because the defect status continually changes, the list reflects a snapshot of the defects that were resolved at the time this report was compiled. For an updated view of the resolved defects or to view specific bugs, access the Bug Search Toolkit as described in the View Caveats.

• CSCvk64079 After powering off and powering on 6821, the 1st call using speaker, switch to handset won't work

• CSCvn14708 Phone gets an IPV6 address but no IPV4 address

• CSCvn15658 Phone LCD did not response

• CSCvn23929 Phone blind transfer failed

• CSCvn99848 Phone reboots when press hold button

For information on the support policy for phones, see https://cisco.com/go/phonefirmwaresupport.