Aastra 6737i SIP Phone Firmware 3.3.1.5089 Download

Posted at May 1, 2024 by PCI-DB Team

Aastra 6737i SIP Phone Firmware 3.3.1.5089 Description

Fixes:

- 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.
- 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.
- 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.
- Various 802.1x authentication issues have been resolved in Release 3.3.1 SP2 HF2.
- Placing the handset on hook to park a call did not complete the call park as expected. 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.
- 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.
- 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.

  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