Cisco SPA942 IP Phone Firmware 6.1.5a

Fixes:

- SIP message over 3Kb causes phone to reboot. Broadsoft BLF monitor lists can be up to 64Kb, and caused phone to reboot.
- RTP TOS value always follows EXT1.
- If the phone receives a SIP request (such as a BYE) from the peer while it has an outbound INVITE transaction pending a final response from the same peer (as in making a call), then the phone may reboot if the final response is not 200 class and is received prior to Timer J expiration for the other SIP request (see RFC-3261 for Timer J definition).
- When the SPA phone is the transfer target of a call transfer operation, it should not send a BYE to the transferor when it receives an INVITE from the transferee (with a Replaces header) if it is still in ringing state; instead it should send a 487 response to the transferor to end the INVITE transaction with the transferor.
- Phone does not include Contact header in all SIP 18x responses it sends out, but the response has a to-tag propagated which establishes a SIP dialog.
- When making an outgoing call, the phone does not send an ACK after receiving the SIP 200 OK for the original SIP INVITE if the 200 OK contains a header with name that is longer than 31 characters.
- Phone not responsive if CTI enabled but EXT 1 <Proxy> is blank.
- Wrong GUI display when accessing voicemail from a SPA400 via a SPA9000, when the SPA400 is not booted up or the USB drive is not plugged in.
- If Contact header in a 200 response to INVITE has a long URL parameter, and maddr is located near the end of this url parameter, phone may not locate the maddr parameter correctly, and hence cannot send ACK to the expected address (given in the maddr parameter).
- Context: Broadsoft SCA—No peer name/number. Problem: a) Phone does not show peer's name/number of a shared line on the GUI when the shared line was used by another phone. b) After phone picks up a shared call that is on hold by another phone, the screen of the phone connected with the peer does not show peer's name or number.
- Caller ID display problem (not following <Caller ID Header> setting precisely).
- When parsing pick up response from a phone that's not ringing, phone may hang since the response does not include any ringing calls.
- Set up with Broadsoft SCA setup. If a user goes on/off hook to seize a shared call appearance very quickly (for example, more than 15 times with 30s), the call appearance may become erratic and cannot be released until the phone reboots.
- When using SIP/TCP w/ Broadsoft, the server does not respond to NOTIFY/keep-alive messages from the phone, causing the phone to drop the TCP connection.
- SPA unit cannot handle compact form SIP Content-Length header when receiving SIP messages over TCP transport. It will act as if the messages do not carry any message body.
- SPA942/SPA922: Setting localization sometimes causes change in audio pitch.
- Improve Broadsoft Extension Mobility Feature. a) Extended TCP/IP timeout on a profile resync operation (after a connection to the profile server has been established). b) Corrected a bug when user/ password information is mistyped on the phone's login screen.
- SPA932—Pressing two keys simultaneously for call pickup causes reboot.
- SPA932 support for Sylantro BLF.
- SPA932 LED error after removing user from Broadsoft monitor list.
- SPA932 subscribe URL change results in status error.
- SPA962: Problem with Russian display. Solution: Localization support of selective fields entered by users.

About VoIP Phone Updates:

Firmware updates for VoIP Phones are very important as they usually contain many bug fixes, add new features and updates, as well as add additional security features.

One of the main problems users come across when attempting to upgrade their VoIP Phone is that their device may be locked to a certain Carrier. Adding an unlocked version of the firmware may cause the device to stop working on certain networks. This operation may void your carrier warranty and, as such, is not recommended.

Before downloading, make sure that you have selected the appropriate firmware for your device and that the update supports the VoIP service provider you use.

Generally, it is important to upgrade older firmware in sequence (v1 to v2 to v3) and so on, because many manufacturers don't launch standalone update packages.

Although using beta release firmware packages is tempting, it can prove to be quite risky as well. If you choose to try beta release updates, please read the detailed firmware notes and make sure that you have the possibility to revert to an older and more stable version in case the beta turns out faulty.

If you feel that this update can improve the functionality of your VoIP Phone, please use the download button and follow the installation instructions.