PDF(259.0 KB) View with Adobe Reader on a variety of devices
ePub(80.9 KB) View in various apps on iPhone, iPad, Android, Sony Reader, or Windows Phone
Mobi (Kindle)(90.2 KB) View on Kindle device or Kindle app on multiple devices
Updated:July 18, 2015
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.
Release Notes for Cisco SPA232D Multi-Line DECT ATA and Cisco SPA302D Multi-Line DECT Handset Firmware Version 1.3.5
Firmware Released: September 29, 2014
Document Revised: July 17, 2015
These Release Notes provide information about Cisco SPA232D Multi-Line DECT ATA and Cisco SPA302D Multi-Line DECT Handset firmware version 1.3.5.
As with any firmware release, read these release notes before upgrading the firmware. Cisco also recommends backing up the configuration before any firmware upgrade.
Changes in Firmware Version 1.3.5
For the Cisco SPA302D/SPA232D, following are the changes in the firmware version 1.3.5:
Added a new parameter "DTMF DECT Input Length" to adjust the DTMF length (which is too short) in AVT method. This parameter controls the event duration in RFC 2833 RTP event packet triggered by the DTMF digit sent from the handset.
Note This parameter is available in SPA232D only. The parameter "DTMF Playback Length" under Voice > Regional tab controls DTMF duration in INFO method.
The open Secure Sockets Layer (SSL) open source library used in the ATA is upgraded to 1.0.1g in order to support TLS 1.2.
The SIP parameter "Hook Flash MIME Type" is set to application/broadsoft so that the Broadsoft server recognizes the flashhook event.
The devices with the following PID and TAN numbers (or later numbers) cannot be downgraded to a version older than 1.3.3:
PID-SPA232D-G1 TAN-74-9321-01 F0
PID-SPA232D-G7 TAN-74-9324-01 F0
PID-SPA232D-R1 TAN-74-9323-01 F0
PID-SPA232D-R7 TAN-74-9325-01 F0
If a device is upgraded to SW 1.3.3 or later, the provisioning server requests a server certification signed by the Cisco 2K Small Business CA or can use the certificate signed by 1K CA.
Note The 2K server certificate is not compatible with old firmware (before 1.3.3.) The 1K server certificate is compatible with all firmware, before and after 1.3.3.
Devices with serial number CCQ18230001 (and newer) are built-in with 2K Client Certificate.
For a device with 2K Client Certification, the provisioning server should update the combined CA if client certification is requested.
Note The new combined CA is compatible with both 1K and 2K Client Certification.
Hardware and Firmware Compatibility Matrix
(3 types of devices)
1.3.5p(XU), 1.3.5p, 1.3.2p
1.3.5(XU), 1.3.5, 1.3.4, 1.3.3, 1.3.2n
1.3.2 or earlier
(128MB Flash + New SLIC)
(128MB Flash + Old SLIC)
CCQ17100G3L to CCQ1906001U
(32MB Flash + Old SLIC)
Note 1.3.2p is identical to 1.3.2 and additionally supports 128MB flash and new SLIC. 1.3.5p is based on 1.3.5; both have the same feature set, except that 1.3.5p supports new SLIC while 1.3.5 does not. 1.3.5p(XU), 1.3.5(XU), 1.3.2(XU): SRTP functionality has been removed, and it cannot be configured or provisioned in firmware versions that are designated with XU in the filename.
Note Do not upgrade any device to an unsupported firmware version as detailed in the Hardware and Firmware Compatibility Matrix table.
Note New devices have a label that reads S/W: Must use 1.3.5(004p) or later.
SPA302: After enabling CFWD on the server, the CFWD does not sync with the handset (HS).
SPA232D: No RTP stream issue while making a call 30 minutes after the phone upgrades (with domain name in <Upgrade Rule> and specific configuration setup.)
The default value of LLDP is different from the configuration generated by the SPC tool.
SPA232D: Changing Block Anonymous Call in the HS GUI impacts the value of DTMF Length.
SPA302D: The speaker icon overlaps the ringoff icon on the HS.
SPA302D: Changing the default outgoing line to PSTN on the HS impacts the priority of other outgoing lines.
SPA302D: Making a secure call from the HS causes the voice module to hang (no audio.)
SPA302D: DECT line 10 cannot make the second call.
SPA302D: The HS does not reply 'Busy' while receiving the 5th call.
SPA302D: While making the 5th call there is no audio issue, dialing issue, or FXS no ring issue.
SPA302D: The DTMF tone is too short and not configurable causing DTMF detection failure on the IVR.
InBand DTMF does not work.
SPA232D ignores the NOTIFY expiry.
SPA302D: The Line Status is displayed incompletely if the Display Name is too long.
SPA232D: IVR 73738 does not work for voice parameter reset.
SPA232: FXS port, Enable/Disable DND works even after stopping the DND server.
SPA302D: Call information missing when the User ID is over 20 characters.
Obsolete Link for Music Coupler needs to be updated.
SPA302D: During secure call there is no indication tone on the HS for hold/resume on the remote party.
Due to CSCug32425, when upgrading the SPA232D loaded with v1.3.1 (or a previous firmware version), it is required to upgrade the SPA232D v1.3.2 firmware twice if provisioning the device via the Upgrade Rule to correctly upgrade to the corresponding embedded SPA302D handset software. A special version of SPA232D firmware has been created to be used to perform the first upgrade while the second upgrade can use SPA232D_SPA302D_1.3.2_014_FW.bin which then installs the SPA302D handset software correctly.
This is not an issue while upgrading the SPA232D firmware via the web-based configuration utility, as the SPA232D needs to be upgraded only once.
SPA232D: While continuously running TR69, the ATA displays ‘Connection Refused’ (between the ATA and the server.)
SPA232D: PSTN Caller ID is incorrect with specific configuration.
SPA302D: When a first call is on hold, the second call cannot be answered while the other handset is upgrading.
SPA302D: The CWT tone continues to play on the second incoming call even after the first call ends.
SPA302D: The Dial Plan syntax (without the exclamation mark) does not work on the HS, but works on FXS port.
SPA232D: Media Loopback is not supported.
SPA302D: When both DND and CFWD Busy are enabled then CFWD does not take effect.
SPA232D: The phone sends random DTMF when the "Conference Tone" is changed.
SPA302D: Outgoing line from the HS cannot be emptied.
SPA232D: Download failure of auto-recovery file blocks manual recovery.
SPA232D: Setting IP Dialing format for CFWD target does not work.
SPA302D: ‘Reply 182 on Call Waiting’ does not work on DECT line (works in FXS port.)
SPA232D: "Conference Bridge Ports" does not work.
SPA302D: Cannot dial out when the dialed number is 32 characters.
SPA302D: Hold Tone on the HS is missing during a long call if the call is put on hold by the called party.
SPA302D: Conference cannot be set up using Conference Bridge if the calls are swapped.
SPA232D: While one handset is upgrading, "Call Forwarding" cannot be accessed.
SPA302D: The HS does not display the underline in the name of an incoming call.
SPA232D: Reminder Ring does not play immediately after an end of a PSTN call.
SPA232D: The CFWD last caller setting on PSTN User tab in the web GUI does not take effect.
SPA232D: The max duration setting for PSTN/VoIP Call does not take effect in the handset.
SPA232D: While a PSTN line is in use, Caller ID is not displayed on FXS port during an incoming call.
SPA302D: The SPA302D has a missed call when two or more handsets are using the same line.
Firmware Downgrade Limitation
The devices with the following PID and TAN (or later TAN number) cannot be downgraded to a version older than 1.3.3.
If the device is upgraded to 1.3.3 or later (no hardware related), the server could request a server certification signed by the "Cisco 2k Small Business CA" or keep using certificate signed by 1k CA. Be careful, it is optional because the new signed 2k server certificate is not compatible with old firmware (before 1.3.3). Server certificates signed by 1k CA are working for all firmware, before and after 1.3.3.
SPA112&122&232D with SN CCQ18230001 and after have a built-in 2k Client Certificate. Then server must update the new Combined CA if the client certification is required. The new Combined CA is compatible with the old 1k & 2k certificate, which means it works for all the devices.
Upgrade the Firmware
Upgrade the Cisco SPA232D
Follow these instructions to upgrade the phone adapter.
Step 2 Launch a web browser, and enter the LAN IP addresses of the ATA.
Step 3 Log in to the Configuration Utility. (On first use, enter admin as the username and the password. After logging in, you should configure a unique password that is hard to guess.)
Step 4 Click Administration in the menu bar, and then click Firmware Upgrade in the navigation tree.
Step 5 Click Browse and select the location of the upgrade file that you downloaded.
Step 6 Click the Upgrade button to upgrade the firmware.
Note Upgrading the firmware may take several minutes. Until the process is complete, DO NOT turn off the power, press the hardware reset button, or click the Back button in your current browser.
Upgrade the Cisco SPA302D
Perform this procedure after you upgrade the Cisco SPA232D while you wait for the ATA to reboot.
Note To verify the upgrade, go to the Administration > Firmware Upgrade page, and confirm that the firmware version number is correct.
Step 1 On the handset, press the center Select button, scroll to Settings, and press the Select button again.
Step 2 In the settings menu, choose Update Software, and then press the Select button.
Step 3 At the Check for software update prompt, press Confirm.
Step 4 Within a moment, the handset displays the current version of software on the handset and the latest software version available from the Cisco SPA232D. Press the Select softkey.
Step 5 Place the handset in the charging cradle.
Do not remove the handset from the charging cradle during the upgrade. Do not power off the handset, charging cradle, or base station, or otherwise interrupt the upgrade process.
The handset erases the flash memory, downloads the new software, and verifies the upgrade data. After the upgrade, a message appears indicating the status of the upgrade (for example, if the upgrade succeeded).
Step 6 After the success message appears, press Reset to reboot the handset.
If the upgrade fails, press Reset to reboot the handset. Check the status lights on the Cisco SPA232D to make sure that it is powered on and functioning. Then, repeat the upgrade steps.
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.
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.