Aastra 6739i SIP Phone Firmware 3.3.1.2208 Download

Posted at December 22, 2024 by PCI-DB Team

Aastra 6739i SIP Phone Firmware 3.3.1.2208 Description

Fixes:

- The phones can now accept a maximum of 256 characters when defining HTTP, HTTPS, TFTP, and FTP server download paths.
- Previously, when a programmed key was removed (via Web UI or the IP Phone UI’s Speed Dial Edit Menu), the key would not be completely removed from the local.cfg file. Consequently, if the same softkey was defined in the aastra.cfg or MAC.cfg files, the key would not show up (as the remaining parameters in the local.cfg file override the server.cfg file). This issue has been corrected and now when a programmed key is removed, the whole content of the respective key is removed from the local.cfg file.
- An issue was observed whereby users were unable to configure the date on the phone manually using the phone’s UI if the Screen Language was set to German. This issue has been resolved.
- An issue occurred whereby if the “call transfer disabled” parameter was set to 1 (True), a call could still be transferred during a conference call if the user pressed the Leave or Xfer softkey/hardkey. This issue has been corrected.
- The TLS persistent connection keep alive retry timeout was observed to be exponential instead of periodic resulting in issues when network interruptions occurred. These issues have been fixed.
- When using DHCP Option 43 to transfer VLAN ID assignment, in certain scenarios, upon reboot the phone would receive the applicable VLAN information and enable VLAN as expected but the VLAN ID would be configured with an invalid value. This issue has been resolved.
- When utilizing TR-069 functionality, it was observed that the phone was unable to open the required port in order to accept an incoming HTTP request from the Auto Configuration Server (ACS). This issue has been fixed.
- Entrust root certificates are now supported on the phones in Release 3.3.1 SP2
- Robustness of the phones was increased to fix various intermittent stability issues observed in certain scenarios.
- When performing an outgoing call using the Directory with the handset off hook, the phone would incorrectly switch to a different line to dial out. This issue has been corrected.
- When using the phones in TLS/SRTP mode in conjunction with the Aastra 5000 call manager and CTI dialer, a one-way audio issue was observed when the CTI dialer was used to initiate a phone call with a 5300ip series phone. This issue has been fixed.
- A logging in/out issue was observed when using the phone with the Aastra MX-ONE call manager. This issue has been resolved.
- When using the phone with a Metaswitch call manager, if the phone was in a conference call whereby one party was an Interactive Voice Response (IVR) system, the IVR would not recognize the digits pressed on the phone. 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.
- Pressing a softkey configured for Intercom functionality when the “Call Transferred” message was displayed on screen would cause the phone to reject subsequent incoming calls with a “486 Busy Here” message. This issue has been fixed.
- When using the A5000 call manager and calling a number corresponding to the configured local dial plan, no ringback would occur on the phone if the phone received a 180 RINGING message very quickly after receiving the 100 TRYING message. This issue has been corrected.
- After completing a call transfer of an inbound call, the line that received the initial inbound call would still remain in a transferring state in certain scenarios. This issue has been resolved.
- An issue occurred whereby the phone was not taking into account the configured LLDP-MED voice signalling priority. This issue has been corrected and the phone now sends the proper configured voice signalling priority in the SIP Real-time Transport Protocol (RTP) packets.
- A stability issue occurred causing the phone to restart during a call and when a call was initiated and then subsequently cancelled (i.e. Phone A pressed the Cancel key and Phone B pressed the Options key simultaneously while Phone A was calling Phone B). This issue has been resolved.
- When initiating a transfer or conference call by first pressing a Speeddial key configured as a prefix ending with a + symbol (e.g. #31#+) and then by using the dialpad or a Speeddial key to dial a proper phone number, the INVITE of the second leg of the call would only contain the prefix. This issue has been fixed.
- When used in the conjunction with the Aastra 5000 call manager and with TLS enabled, if the IP link between the call manager and phone was disconnected for a period of time longer than the configured value for the “sip registration period” parameter, upon reconnection of the IP link, the phone would reestablish a TLS connection but would not refresh the registration of the accounts associated with the connection. This issue has been corrected.
- An issue was observed whereby the phone would not answer an UPDATE request if the UPDATE request contained an SDP offer. This issue has been fixed.
- When attempting to initiate a transfer in certain scenarios, if the sendonly INVITE (sent when placing the call on hold) was rejected by a 488 Not Acceptable Here response, the phone did not indicate that the hold attempt failed and also remained on the transfer screen. This issue has been fixed and now the phone returns to the previous connected view and displays a “Hold Failed” message in such situations.
- When on an active call on Line 1, if the Hold or L2 hardkey was pressed and the resulting sendonly INVITE was rejected by a 488 Not Acceptable Here response, pressing the Hold or L2 hardkey again would have no effect (i.e. the expected sendonly INVITE would not be sent). This issue has been fixed.
- An issue was observed whereby in certain situations if a phone with an SCAconfigured line received a re-INVITE message with PAI details brought upon by an attended transfer, the expected NOTIFY message to update the caller ID would not be received. This issue has been resolved.
- When the phone is in an idle state and the backlight is turned off (i.e. when the inactivity brightness level is configured as 0), the first touch of the screen now only “wakes up” the phone ensuring there is no inadvertent activation of any buttons/functions.
- A noticeable decrease in the maximum on-hook speaker volume was observed when upgrading to 3.x firmware. This issue has been fixed and the on-hook speaker volume is now comparable to the settings of previous releases.
- When using the CommuniGate Pro call manager, after completing a successful supervised transfer, the transfer recipient’s screen did not display the expected calling party’s information. This issue has been fixed.
- A line switching problem occurred when lifting the handset to answer Line 3 (while Line 1 and Line 2 were on hold). This issue has been corrected.
- When a successful transfer was performed, the phone would not respond to any dialpad inputs during the period of time the “Call Transferred” message was displayed on screen. This issue has been fixed.
- When using the phone with the Aastra 400 call manager, entries within the Redial and Caller Lists would appear as empty buttons if the entry contained only a number and no name. This issue has been resolved.
- In situations where an outbound call was unsuccessful and resulted in a “Call Failed” message to appear on screen, any incoming calls during this time were not being indicated to the user. This issue has been corrected.
- If an outgoing call was made and the phone received a SIP 183 message with PAI details, the phone would at times display the phone number instead of the information contained in the PAI header. This issue has been resolved.
- After establishing a call using the G.722 wideband codec, a decrease in the ringer volume was observed. This issue has been resolved.
 - An issue was observed whereby incoming caller names were not being displayed correctly on screen if the incoming caller corresponded to an entry in the Directory that contained diacritical marks. 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