Aastra 6735i SIP Phone Firmware 3.2.2.7137 Download

Posted at April 25, 2024 by PCI-DB Team

Aastra 6735i SIP Phone Firmware 3.2.2.7137 Description

Fixes:

- Various improvements have been made to the DTMF feature in the 3.2.2 SP3 Release. - Users were able to configure invalid VLAN IDs for both the PC port and phone LAN port using the phone’s local UI or phone’s Web UI. This issue has been corrected. - The option “Goodbye Key Cancels Incoming Call” was not able to be configured through the phone’s Web UI. This issue has been resolved and the option is now available under the Basic Settings -> Preferences -> General section of the Web UI. - A stability issue was observed if the phone had the “sip proxy port” parameter defined in the configuration files and a user rejected an incoming call. This issue has been resolved. - An issue was observed whereby users were not able to configure softkeys for an expansion module using the phone’s <mac>.cfg file. This issue has been corrected.
- A stability issue was observed when the phone was restarted with certain MCS parameters defined in the configuration files. This issue has been fixed.
- An issue occurred whereby the configuration server DNS failover feature was not working and the phone would not try the second IP address if the first one was incorrect. This issue has been corrected.
- Issues were observed whereby attempting to save configured labels for various softkey types would initially fail. A second save attempt would be successful, but the label would revert back to its default after a reboot. These issues have been fixed.
- An issue was observed whereby if the phone was locked, pressing a Speeddial softkey or Speeddial keypad key configured with an emergency dial plan number would not dial the emergency number as expected. This issue has been corrected and emergency number speed dial functionality with locked phones is now working as expected.
- Previously the “confxfer live dial” parameter was not a dynamic parameter. With Release 3.2.2 SP3, the “confxfer live dial” parameter is now dynamic and can be enabled by using an XML script.
- After performing a factory reset and configuring the firmware update server settings, restarting the phone would at times not initiate the firmware upgrade process. This issue has been corrected.
- A stability issue was observed when a user tried to configure the Call Forward feature using the phone’s UI. This issue has been resolved.
- Previously, the maximum number of characters allowed in the value for DHCP Option 66 was limited to 64. With Release 3.2.2 SP3, the maximum number of characters has been increased to 128.
- The option “Display DTMF Digits” was not available to be configured through the IP Phones’ Web UI. This issue has been corrected and the option is now available in the Basic Settings -> Preferences -> General section of the Web UI.
- An issue occurred whereby Telnet port access was open on the phone. Access has now been disabled as the phone does not support configuration or administration via Telnet.
- When the phone was configured to use authentication support for HTTPS with the BroadSoft Client Management System (CMS), the phone did not load the configuration files from the HTTPS server and the time server requests were being sent after the certificate negotiation process. This issue has been corrected
- With the Upload System Info feature configured, the phone would incorrectly upload the local.cfg and server.cfg files to the server after every reboot. This issue has been resolved and the phone now uploads the respective .cfg files only when a stability issue occurs or if the user manually initiates the process.
- With NTP servers disabled on the phone, if the phone was set to utilize an HTTPS configuration server and the HTTPS protocol for downloads, after a restart the phone would not reject downloads from the HTTPS server as expected. This issue has been corrected.
- Placing a “$” character before a parameter defined in the aastra.cfg, <mac>.cfg, or <model>.cfg file will now allow the parameter to be saved in the phone’s local.cfg file. As a result, the affected parameters and settings will be left intact even if the phone is rebooted and new configuration files are downloaded by the phone.
- Various SIP issues in relation to paging functionality have been corrected.
- Robustness improvements made for phone restart, missing or incorrect error messages, and upload of system information.
- When using the IP phone with Aastra 5000 call managers in a redundancy environment, the phone would not send the expected TLS keep-alive frame to the master server in scenarios where a network failure occurred and a switchover to the slave server was conducted. This issue has been fixed.
- When the phone was in a ringing state (applicable to both outgoing and incoming ringing states) and a multicast page was sent to the phone, the phone stopped the respective ring tone but would not receive the multicast page. This issue has been corrected.
- HTTP digest authentication was not functioning as expected in previous releases. This issue has been resolved and HTTP digest authentication is now fully functional in Release 3.2.2 SP3.
- An improvement has been implemented allowing the phone to explicitly force the host port value to be present in the “Via” header of REGISTER messages.
- Immediately after the phone was rebooted and an outgoing call was made (placing the phone in a ringback state), if the phone received an incoming call during this state, after the call waiting tone subsided, both local and remote ringback tones could be heard at the same time. This behavior has been corrected and the remote ringback is now inaudible in the above scenario.
- In addition to 2048-bit Verisign root certificate support, 2048-bit intermediate certificates are now supported by the IP Phones in Release 3.2.2 SP3.
- With phones configured to have two appearances of the same SCA-configured line (e.g. Line 1 and Line 2), when a user dialed a number from an open Line 1 and subsequently pressed Line 2, which was seized by another phone, Line 1 would not be properly released as expected. This issue has been fixed.
- An issue was observed whereby if the phone rejected an SDP offer from either an UPDATE or PRACK while in an early state, the phone would not return to its idle screen. This issue has been corrected.
- While on an active call on Line 1, if a user attempted to place a secondary call on Line 2 using the Callers or Redial List, the dial tone could be heard but the phone would not dial out on Line 2 as expected. These issues have been corrected.
- When in an active call using the headset mode on a phone configured for use on a Zultys account, if a secondary call was incoming and the call waiting tone was enabled, audio would be lost on the active call. This issue has been fixed and the audio is now functioning as expected in such situations.
- When utilizing the MX-ONE call manager, a stability issue was observed if the call manager sent an incorrect SDP in a 183 provisional response to the phone. This issue has been corrected and the phone now responds by returning to the idle screen in such situations.
- An issue was observed whereby the “To” header in the PUBLISH message contained different information in recent firmware releases compared to that of previous firmware releases. This issue has been fixed and the “To” headers are now consistent throughout.
- When in a three-way conference call, placing the handset on hook would only terminate the first leg of the conference instead of terminating both legs as expected. This issue has been fixed.
- Certain Interactive Voice Response (IVR) systems were unable to detect the DTMF tones sent from the phone. This issue has been fixed.
- Issues were observed with regards to the SIP PUBLISH message whereby the “RemoteMetrics” and “LocalMetrics” in the PUBLISH message body was omitted if the respective party did not send RTCP XR information. Additionally, the
- Contact header in the SIP PUBLISH request was missing. These issues have been corrected.
- An issue was observed whereby if a user tried to transfer an active call to an extension configured on a BLF/List softkey, pressing the Xfer or Goodbye key immediately thereafter (to complete the transfer) would at times create two incoming calls on the transfer target. 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