Aastra 9480i CT SIP Phone Firmware 3.3.1.2235 Download

Posted at December 22, 2024 by PCI-DB Team

Aastra 9480i CT SIP Phone Firmware 3.3.1.2235 Description

Fixes:

- 6735i & 6737i: During its first boot up process, the phone did not properly initialize the TR-69 stack causing a connection issue with the Auto Configuration Server. This issue has been fixed.
- 6739i: With both 802.1x and TLS/SRTP configured/enabled in the configuration files, the phone did not download the 802.1x certificates during the boot up process as expected. This issue has been resolved.
- 6735i & 6737i: An issue was observed whereby the Globally Routable User- Agent URIs (GRUUs) obtained in the 200 OK REGISTER response was not being used in the SUBSCRIBE request sent from the phone. This issue has been fixed.
- 6735i & 6737i: An issue was observed whereby the phone would send the incorrect “Contact” header in INVITE requests when multiple contacts (all with GRUUs) were received in the 200 OK response to REGISTER. This issue has been resolved.
- 6739, 6755i, 6757i, & 6757i CT: Various 802.1x authentication issues have been resolved in Release 3.3.1 SP2 HF2.
- 6757i: With an active call on Line 1 and an incoming call on Line 2, if the user pressed the Line 2 key at the same time the remote caller on Line 1 terminated the active call, the ringback tone would continue for the Line 2 call even when it was answered. This issue has been fixed.
- 6735i & 6737i: Placing the handset on hook to park a call did not complete the call park as expected. This issue has been resolved.
- 6757i: UI issues were observed in certain scenarios when the phone attempted to hold an active call but the hold attempt failed. This issue has been corrected.
- 6755i & 6757i: With the Microphone Mute and Play Warning Tone features enabled (under Incoming Intercom Settings) the phone would not automatically mute the microphone during an intercom call if using the G.722 codec. This issue has been resolved.
- When using the Aastra Clearspan call manager, an audio level issue was observed if the “ring audibly enable” parameter was enabled and a secondary call was incoming. This issue has been corrected.
- 6755i, 6757i & 6757i CT: An audible artifact could be heard after receiving a 183 Session Progress SIP message in certain scenarios. This issue has been fixed.
- 6735i & 6737i: With BLF/List softkeys configured and multiple BLF/List extensions ringing, an issue was observed whereby the ring splash of a ringing extension would not resume after one of the BLF/List calls was answered and dropped. This issue has been corrected.
- With Line 1 on hold, pressing both the Line 1 and Line 2 keys at the same time caused both of the lines’ audio streams to be heard simultaneously. This issue has been resolved.
- When attempting to make a call on an SCA line already in use, the phone would play a busy tone and notify the user that the call failed as expected, but after pressing the Goodbye key (or placing the handset back in the cradle) to
- clear the busy tone, the LED of the SCA line would become unlit. This issue has been fixed and LED now stays lit in such scenarios.
- 6757i: When using the BroadSoft BroadWorks call manager, a BLF/List version numbering error caused an issue whereby the LEDs for BLF/List softkeys were not being updated to reflect the most recent state. This issue has been resolved.
- 6731i & 6739i: Selecting an XML key configured with the “xml lock override” parameter defined as either “1” or “2” did not produce the desired behavior. This issue has been corrected.
- An issue was observed whereby configuring the “xml get timeout” parameter did not change the timeout behavior as per the defined value. This issue has been resolved.
- 6757i: With the handset off hook and when using an XML script for paging functionality, the paging call would not terminate as expected when the handset was placed back on the cradle. This issue has been fixed.

  It is highly recommended to always use the most recent driver version available.

Try to set a system restore point before installing a device driver. This will help if you installed an incorrect or mismatched driver. Problems can arise when your hardware device is too old or not supported any longer.

Related Aastra Drivers