Release Notes for Cisco Small Business SPA30X, SPA50X, and SPA51X IP Phone Firmware Version 7.6.1
First Published: September 22, 2015
These Release Notes describe the updates and fixes in version 7.6.1 of the Cisco Small Business SPA30X, SPA50X, and SPA51X IP Phone firmware.
As with any firmware release, read these release notes before you upgrade the firmware. Cisco also recommends that you back up the configuration before you perform any firmware upgrade.
Before You Upgrade
When you upgrade a Cisco SPA50X or Cisco SPA30X IP Phone, if you have installed a firmware version prior to 7.5.2b, you must first upgrade to 7.5.2b before you upgrade to release 7.5.3 or to a later release. See the following table for more information.
Firmware Release Installed on Your Phone
Special Instructions for Upgrading to Release 7.5.3 or Later
Upgrade to 7.5.2b first, then upgrade to 7.5.3 or later.
For SPA30X, SPA50X, and SPA51X, the openssl upgrades from openssl 0.9.8zc to openssl 0.9.8zg.
New and Changed Features
SUBSCRIBE failover behavior is the same as the behavior of Register/Invite messages. The phone restarts subscribe messages, including subscribe event type Call-Info, BLF, Hoteling, and as-feature-event, if the registration IP changes, regardless of the Auto Register When Failover setting.
When the Auto Register When Failover setting is Yes, all SUBSCRIBE failovers trigger reregistration.
SIP Accept Encoding Parameter
A new parameter, SIP Accept Encoding, is added to support the content-encoding gzip feature.
The options are none and gzip:
If none is selected, no changes are made. The default is none.
If gzip is selected, the SIP message header contains the string “Accept-Encoding: gzip”, and the phone is able to process the SIP message body, which is encoded with the gzip format.
SPA5xxG: general issues due to codec mismatch.
SPA525/5x5: change SIP Accept Encoding do not work for in-dialog subscribe.
The SPA 30x/50x phone do not support font size 12, for Hebrew language.
For SPA phones, a “+” sign is missing for the numeric inputs of PAB number entry.
The SPA phones do not support Xuser and Xpassword.
The SPA5x5 phone, displays the CFWD softkey for other call states (dialing), even if the CFWD service is disabled.
For SPA5x5/51x phone, the string, “Blind transfer number” is missing in XML Dictionary.
The following caveats are resolved after release 7.6.0.
7.5.7 BLF Presence status is stuck intermittently (content-encoding: gzip).
SPA5x5 proxy failover after 503 to SUBSCRIBE.
SPA504G: DNS SRV CNAME support.
SPA5x5: Phone freeze after receiving BLF Notify with empty content body.
SPA5x5: won't resubscribe for the As Feature Events upon fallback.
SPA502G: Called Display Name not using PAI information.
SPA51x only: Auto-Provisioning failed when SSLVerifyClient require.
Behavior During Times of Network Congestion
Anything that degrades network performance can affect 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 devices, schedule administrative network tasks during a time when the devices are not being used or exclude the devices from testing.
Use the following sections to obtain related information.
Subscribe to What’s New in Cisco Product Documentation, which lists all new and revised Cisco technical documentation as an RSS feed and delivers content directly to your desktop using a reader application. The RSS feeds are a free service.
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1110R)
Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental.