The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
These release notes support the Cisco Unified IP Phones 8961, 9951, and 9971 running SIP firmware release 9.3(2)SR1.
The following table lists the Cisco Unified Communications Manager release and protocol compatibility for the Cisco Unified IP Phones.
Cisco Unified IP Phone | Protocol | Cisco Unified Communications Manager |
---|---|---|
Cisco Unified IP Phones 8961, 9951, and 9971 |
SIP |
Cisco Unified Communications Manager release 7.1(5) and later |
Refer to publications that are specific to your language, phone model, and Cisco Unified Communications Manager release. Navigate from the following documentation URL:
Refer to publications that are specific to your language, phone model, and Cisco Unified Communications Manager release. Navigate from the following documentation URL:
See the Cisco Unified Communications Manager Documentation Guide and other publications that are specific to your Cisco Unified Communications Manager release. Navigate from the following documentation URL:
See the Cisco Business Edition 5000 Documentation Guide and other publications that are specific to your Cisco Business Edition 5000 release. Navigate from the following URL:
Refer to publications that are specific to your language. Navigate from the following documentation URL:
This release contains no new or changed features.
Before you install the firmware release, you must ensure that your Cisco Unified Communications Manager is running the latest device pack.
If your Cisco Unified Communications Manager does not have the required device pack to support this firmware release, the firmware may not work correctly.
For information on the Cisco Unified Communications Manager Device Packs, see http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/compat/devpack_comp_mtx.html.
Before using the Cisco Unified IP Phone with Cisco Unified Communications Manager, your Cisco Unified Communications Manager servers must be running a version of the server software that supports the phones. All Cisco Unified Communications Manager servers in the cluster must support the phones. For information about the minimum Cisco Unified Communications Manager software version that the phone requires, see the introductory sections of these release notes.
For more information on Cisco Unified Communications Manager installations and upgrades, see the documents for your Cisco Unified Communications Manager version at the following location: http://www.cisco.com/en/US/products/sw/voicesw/ps556/prod_installation_guides_list.html
To download and install the Cisco Unified Communications Manager version, perform these steps.
Step 1 | Go to the following URL: http://www.cisco.com/cisco/software/navigator.html?mdfid=268439621&catid=278875240 |
Step 2 | Choose your Cisco Unified Communications Manager version. |
Step 3 | Choose the appropriate software type. |
Step 4 | Hover over the desired file. When the popup window displays, click the Readme link to open the readme file. |
Step 5 | Choose Download or Add to cart for the desired file. |
Step 6 | Use the instructions in the readme file to install the updated file on the Cisco Unified Communications Manager. |
Before using the Cisco Unified IP Phone Firmware Release 9.3(2)SR1 with Cisco Unified Communications Manager, you must install the latest firmware on all Cisco Unified Communications Manager servers in the cluster.
Step 1 | Go to the following URL: http://www.cisco.com/cisco/software/navigator.html?mdfid=268437892&flowid=5293 | ||
Step 2 | Depending on your phone model, choose Cisco Unified IP Phones 8900 Series or Cisco Unified IP Phones 9900 Series. | ||
Step 3 | Choose your phone type. | ||
Step 4 | Choose Session Initiation Protocol (SIP) Software. | ||
Step 5 | In the Latest Releases folder, choose 9.3(2)SR1. | ||
Step 6 | Select one of the following firmware files, click the Download Now or Add to cart button, and follow the prompts:
| ||
Step 7 | Click the + next to the firmware file name in the Download Cart section to access additional information about this file. The hyperlink for the readme file is in the Additional Information section, which contains installation instructions for the corresponding firmware: | ||
Step 8 | Follow the instructions in the readme file to install the firmware. |
If a Cisco Unified Communications Manager is not available to load the installer program, the following .zip files are available to load the firmware.
![]() Note | Firmware upgrades over the WLAN interface may take longer than upgrades using a wired connection. Upgrade times over the WLAN interface may take more than an hour, depending on the quality and bandwidth of the wireless connection. |
Step 1 | Go to the following URL: http://www.cisco.com/cisco/software/navigator.html?mdfid=268437892&flowid=5293 |
Step 2 | Depending on your phone model, choose Cisco Unified IP Phones 8900 Series or Cisco Unified IP Phones 9900 Series. |
Step 3 | Choose your phone type. |
Step 4 | Choose Session Initiation Protocol (SIP) Software. |
Step 5 | In the Latest Releases folder, choose 9.3(2)SR1. |
Step 6 | Download the relevant zip files. |
Step 7 | Unzip the files. |
Step 8 | Manually copy the unzipped files to the directory on the TFTP server. See Cisco Unified Communications Operating System Administration Guide for information about how to manually copy the firmware files to the server. |
The Cisco Unified Video Camera is supported on Cisco Unified Communications Manager Release 7.1(5) and later.
This section contains important information to consider with the Cisco Unified IP Phone 8961, 9951, and 9971.
Users of the Personal Address Book or Fast Dial feature may receive an error message followed by a request to log back into the network. In DNS round robin configurations, the phone does not retain access with the same IP address. In this situation, the phone displays a message to indicate that the user must log into the phone again.
The Plantronics Audio 615M headset is not compatible with the Cisco Unified IP Phone 8961. You must use an alternate headset type for this IP phone. For more information, see https://tools.cisco.com/bugsearch/bug/CSCth71104.
The Plantronics CS50 USB headset causes the phone to request power from the switch even though the headset is self powered. In this case, if a device such as a camera or expansion module is connected and active on the phone, the switch will reject the power request for the headset because the power budget has been exceeded. In this case, the headset cannot be used.
Because of limitations in the H.264 video signaling standards, Cisco Unified IP Phones 9951 and 9971 may not correctly display video that is received from devices supporting resolutions greater than 640 x 480. In this case, the user sees a black video screen.
To ensure that video from such devices displays properly on the IP phone, configure high definition phones and Cisco Unified IP Phones 8961, 9951, and 9971 into different call regions and limit the video bandwidth to 384 kb/s when calling between regions.
The Cisco Virtualization Experience Client 2100 (VXC 2100) Series are zero clients designed to deliver a user desktop from a centralized host server, providing access to desktop applications as if they were available locally. The Cisco VXC 2100 Series attaches to the Cisco Unified IP Phones 8961, 9951, and 9971 through a spine connector cable.
When running VXC with a single-tunnel option, high traffic to or from VXC may affect the phone's performance. Cisco Unified IP Phones 8961, 9951, and 9971 support 384kbps throughput bandwidth for VXC.
Set VPN MTU to 1406 to reduce packet reassemble in Cisco Unified IP Phones 8961, 9951, and 9971, to improve bandwidth in limited packet rate.
Video and audio applications may not play smoothly through VXC, even on a device plugged directly into a LAN.
USB CD-ROMs and other USB storage devices have limited support. In the current VXC environment, the expected performance is a low bit/transfer rate for USB storage devices and USB CD-ROMs connected to the VXC device.
For more information, see http://www.cisco.com/c/en/us/support/collaboration-endpoints/virtualization-experience-client-2000-series/tsd-products-support-series-home.html.
If you send multiple text messages to Cisco Unified IP Phones 8961, 9951, and 9971 within a few seconds using CiscoIPPhoneExecute.xml, the phone may reply with an HTTP/1.1 503 Service Unavailable message, and the user may not receive the text message on their phone screen.
Cisco Unified IP Phones 8961, 9951, and 9971 do not support UDP for SIP. Do not configure the UDP protocol for SIP signaling on Cisco Unified IP Phones 8961, 9951, and 9971.
When using Cisco Unified IP Phones 8961, 9951, and 9971 for a secure video call over VPN and VXC VPN, the maximum supported bandwidth is 320 kbps.
The phone will go into an unregistered state if it is downgraded from a 9.3(1) load to a pre-9.2(3) load while VPN is turned on. Turn off VPN before downgrading to a pre-9.2(3) load.
If a firmware update occurs while phones are in use, users may experience problems with their phone, such as:
Firmware updates during normal call activity are not affected.
![]() Note | Cisco recommends that firmware updates are made during periods of inactivity. An example of a period of inactivity would be a maintenance window. |
Cisco IP Phones use a Switch Virtual Interface (SVI) to manage VLANs. If the SVI changes and the phones require new IP addresses, some phones require a reboot so that the new IP address is used. The following phones must be rebooted in this condition:
Cisco Unified IP Phone 6901
Cisco Unified IP Phone 6911
Cisco Unified IP Phone 6921
Cisco Unified IP Phone 6941
Cisco Unified IP Phone 6945
Cisco Unified IP Phone 6961
Cisco Unified IP Phone 8941
Cisco Unified IP Phone 8945
Cisco Unified IP Phone 8961
Cisco Unified IP Phone 9951
Cisco Unified IP Phone 9971
Anything that degrades network performance can affect Cisco IP Phone voice and video quality, and in some cases, can cause a call to drop. Sources of network degradation can include, but are not limited to, the following activities:
Administrative tasks, such as an internal port scan or security scan
Attacks that occur on your network, such as a Denial of Service attack
To reduce or eliminate any adverse effects to the phones, schedule administrative network tasks during a time when the phones are not being used or exclude the phones from testing.
By default, Cisco IP Phones are set up for the English (United States) locale. To use the Cisco IP phones in other locales, you must install the locale-specific version of the Unified Communications Manager Endpoints Locale Installer on every Cisco Unified Communications Manager server in the cluster. The Locale Installer installs the latest translated text for the phone user interface and country-specific phone tones on your system so that they are available for the Cisco IP Phones.
To access the Locale Installer required for a release, access http://software.cisco.com/download/navigator.html?mdfid=286037605&flowid=46245, navigate to your phone model, and select the Unified Communications Manager Endpoints Locale Installer link.
For more information, see the "Locale Installer" section in the Cisco Unified Communications Operating System Administration Guide.
![]() Note | The latest Locale Installer may not be immediately available; continue to check the website for updates. |
The following sections list the open and resolved caveats, and describe how to get further information on the caveats.
Known problems (bugs) are graded according to severity level. These release notes contain descriptions of the following:
You can search for problems by using the Cisco Bug Search.
To access Cisco Bug Search, you need the following items:
The following table lists severity 1, 2, and 3 defects that are open for the Cisco Unified IP Phones for Firmware Release 9.3(2)SR1.
For more information about an individual defect, you can access the online record for the defect by clicking the Identifier or going to the URL that is shown. You must be a registered Cisco.com user to access this online information.
Because defect status continually changes, the table reflects a snapshot of the defects that were open at the time this report was compiled. For an updated view of open defects, access Bug Toolkit as described in Access Cisco Bug Search.
Identifier |
Headline |
---|---|
Phone keep alive timer issue in 9.2.(2) phone load |
|
ETSGJ-CH: Conference message is showing in ENGLISH instead of JAPANESE |
|
Can't answer call through BT headset after hold revert |
|
99xx become abnormal or crash after long period of network impairments |
|
No UI feedback when dialing external speed dial using softkey in onhook |
|
Blackwire C220 "accessory not supported" |
|
Cisco IP phone lost wireless connectivity during call |
|
the loading of image fail of 99xx phones in option66 case |
|
OpenSSL SSL_CTX_new Uninitialized Buffer Remote Information Disclosure |
|
Dialed digits lost while making conf or xfer call quickly in video call |
|
Call be disconnected when reauthent happen for phone |
|
Savi 7xx can't reconnect automatically after enable side USB on CUCM |
|
Bluetooth Device Does Not Reconnect |
|
BLF/SD - Busy Lamp Field fails when URI contains special characters |
|
Pip is messed display when swapping pip and remote video |
|
Call comes at nearly the same time with the idle url popping up |
|
SR 621074913 - XSI API on CP-9971 |
|
Call Quality is Reduced When Upgrade Phone Load |
|
RTCP port will keep open when posting RTPRx/RTPTx to phone then end call |
|
No DNS query after reset with alternate TFTP provisioned |
|
The extra softkey will flash in the new call window |
|
Unsaved camera view area setting is used for video call |
|
No call log for early attended conf call if conf list is disabled in FCP |
|
Expected incoming call alert/toast may not be displayed |
|
Preceding or tailing white space in domain name is not trimmed |
|
Video is hidden if end held party during early attended xfer/conf |
|
"Recording Failed" does not disappear if press Record during xfer/conf |
|
Pressing Intercom the second time does not always cancel intercom call |
|
softkey changed and don't work when voice mail is unavailable |
|
Same config file is downloaded twice if disable DHCP |
|
Unexpected lock icon on call back UI if secure URL is provisioned |
|
Abnormal dial UI if press MeetMe or GroupPickup during xfer/conf attempt |
|
Call failed from call history(xfer/conference) with double taps the list |
|
Multi-leg call log of Group/Other Pickup if Auto Call Pickup is enabled |
|
"Unknown Caller" in call log if offhook and auto pickup |
|
Cisco IP phone uses low FPS on CTMS |
|
calling party name is shown as junk character in 99XX |
|
URI with charaters of #{}| can't be searched in NAV-DOWN call history |
|
URI dialing: different result for different dial method |
|
Inappropriate UI behavior of Revert softkey and editing dot1x MD5 secret |
|
Time of scrolling between calls is 20-60ms longer than requirement |
|
Unchanged LED&icon of Record PFK if record during xfer&conf attempt |
|
Black bar under PiP window if remote video resolution is 768*448 |
|
On Receiving CUCM Call, DN not displayed in CME 9951 |
|
Performance of switching between video calls is degraded |
|
Web browser is still work some time when web access is disable |
|
NOTIFY is not accepted by CUCM if digest authentication is enabled |
|
Video is not pop up after cancel a transfer call in non-simplified mode |
|
Pick Up fail during on hold when busy trigger is 2 and MLPP enabled |
|
RT phone needs to protect itself if receiving malformed SDP-shudnt crash |
|
misleading status message for image signed by wrong phone model/key |
|
URI should not displayed in call history when "Block Caller Id" is ON. |
|
Video call statistics UI disappears on rx-only phone after call ended |
|
Quickly start a session will cause XSI application not to rise |
|
Call History: Extra space between caller ID and conference icon |
|
Fail to active callback on different line via PFK during transfer |
|
RTCP: Conflict with RFC3550 on BYE Packet transmission at vid call start |
|
BT: Draggy digits tone in BT headset when doing off hook dialing |
|
unable to end call via BT headset in some scenario |
|
Repeated CTI push of XSI object causes device UI responsiveness delay |
|
Clear history does not work on the idle application window |
|
application window doesn't recover after the call |
|
9951 loses audio on active call when link with pc port is disconnected |
|
Fragment identification is not seq num for RTP when DF bit is set to 1 |
|
Phone cannot register to HCluster after forced logout from HCluster |
|
Toast appear three times while insert two camera |
|
Busy is not returned by phone when push a service to a busy phone |
|
Rcvr/Sender audio Packets will be recount after pc port is disconnecte |
|
Actional alert is malformed when much info is displayed |
|
9951 Phone rejects incoming INVITE containing "Accept-language" in SRST |
|
DN not dialing out when select item from call log during active call |
|
No dial UI if press speaker after specific URI dialing operations |
The following table lists severity 1, 2, and 3 defects that are resolved for the Cisco Unified IP Phones for Firmware Release 9.3(2)SR1.
For more information about an individual defect, you can access the online record for the defect by clicking the Identifier or going to the URL that is shown. You must be a registered Cisco.com user to access this online information.
Because defect status continually changes, the table reflects a snapshot of the defects that were resolved at the time this report was compiled. For an updated view of resolved defects, access Bug Toolkit as described in Access Cisco Bug Search.
Identifier |
Headline |
---|---|
Doc: 89XX/99XX phones drop transfer/conference attempt during UI update |
|
99xx phones - line status stuck on hold state - phantom hold |
|
Empty session bubble on phone if barge between shared lines |
|
Improper call history of BLF pickup |
|
Session key ignored after call ended on 9951 and 9971 phones |
|
Problematic reception report blocks in RTCP from 99xx IP Phone |
|
Firmware 9-3-2-10 changed behavior on 99xx phones with BLF transfer |
|
De-Escalation of secure video to audio leads to call drop. |
|
9951 IP phone paired with BT hands free device crashes and reboots |
|
9971 Acoustic Fine-Tuning for certain customers |
|
Barging Into Existing Conference Does Not Work |
|
802.1x EAP/TLS with 8961 Phone not working |
|
Onhook dialing does not work when speaker phone is disabled on 89XX/99XX |
|
8961 - Corruption of EAP packets - Frame Size increases to 1514 bytes |
|
Simplified Conference & Transfer feature to 9.3(2) ES |
|
cannot do onhook dial after press call or speaker |
|
9971 auto dials the Speed Dial and BLF SD as Phantom calls |
|
Barge is enabled when the call is not connected |
|
Phone restart while conferencing an active call |
|
Stop CUCM-pub during active call, the call will be ended at caller side |
|
89xx/99xx phone reboot upon ignoring actionable alert repeatedly |
For information on the support policy for Cisco IP Phones, see http://www.cisco.com/c/en/us/support/docs/collaboration-endpoints/unified-ip-phone-7900-series/116684-technote-ipphone-00.html.
For information on obtaining documentation, submitting a service request, and gathering additional information, see the monthly What’s New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at:
http://www.cisco.com/c/en/us/td/docs/general/whatsnew/whatsnew.html
Subscribe to the What’s New in Cisco Product Documentation as a Really Simple Syndication (RSS) feed and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free service and Cisco currently supports RSS Version 2.0.