Aastra 6737i SIP Phone Firmware 3.3.1.5077 Download

Posted at December 22, 2024 by PCI-DB Team

Aastra 6737i SIP Phone Firmware 3.3.1.5077 Description

Fixes:

- Previously only supported on the 9000i and 6700i series IP phones, the Technical Report (TR)-069 protocol is now supported for the 6735i and 6737i IP phones.
- The phones can now accept a maximum of 256 characters when defining HTTP, HTTPS, TFTP, and FTP server download paths.
- The configuration parameter “sip enforce require hdr” was not functional for the 6735i and 6737i IP phones. When enabled, the phone rejects an INVITE or BYE with a 420 Bad Extension response if the INVITE or BYE contains and unsupported value in the Require header. This issue has been fixed and the parameter is now fully functional in Release 3.3.1 SP2.
- 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.
- The value of the configuration parameter “admin password” only supported 9 digits instead of expected 10. This issue has been fixed and the parameter now correctly supports a total of 10 digits.
- An issue was observed whereby the internal ringback timeout timer was not being reset correctly if a user manually cancelled a call during a ringback state. This caused the phone to automatically cancel calls in a ringback state earlier than expected, ultimately affecting the timeout defined for the “ringback timeout” configuration parameter. This issue has been corrected.
- A VLAN configuration issue caused the phone’s PC port to become unresponsive when a PC connected to the phone was disconnected, used with another phone on a different switch, and then re-connected to the\ initial phone. This issue has been resolved.
- An enhancement has been implemented in Release 3.3.1 SP2 that allows the phones to ignore the event ID parameter in REFER NOTIFY event headers. This enhancement resolves an issue whereby the phone would reject the REFER NOTIFY message from certain SBCs when a transfer was attempted.
- 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.
- An issue occurred whereby the phone did not release its IP address as expected causing the phone to retrieve a new IP address upon every reboot. 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.
- 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.
- 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.
- Issues were observed whereby 802.1x authentication either failed or was being lost during the phone’s boot-up process. These issue have been resolved.
- When using the phones with the Aastra MX-ONE call manager, the phone would not unregister a user correctly in certain situations causing issues when re-registering the user on a different phone. This issue has been corrected.
- When using the Aastra 5000 call manager in conjunction with the CTI dialer, if TLS/SRTP mode was enabled, the audio stream was not being decrypted correctly causing no audio to be heard by both parties in an active call. This issue has been corrected.
- 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 using the AMR/AMR-WB codec, an audio issue would occur if there was a discrepancy between the dynamic payload codec numbers used by the local and remote phones. This issue has been resolved.
- An issue was observed whereby, in certain scenarios and after a codec change, the phone would unexpectedly respond to a REINVITE with a 488 Not Acceptable Here message. This issue has been corrected.
- An issue was observed whereby the phones were not parsing the Annex B media attribute correctly. This issue has been fixed and parsing of the Annex B attribute is now fully functional in Release 3.3.1 SP2.
- 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 used in conjunction with the Aastra 400 call manager, in certain scenarios, one-way audio would be observed after placing a call on hold and then retrieving the call. This issue has been resolved.
- An intermittent issue was observed whereby ring tones were not audible through the speaker when they were selected using the phone’s UI. This issue has been fixed.
- When used with the Aastra MX-ONE call manager, if the phone was configured with a Personal Number (PEN) softkey and the softkey was in an ON state, the PEN softkey status was unexpectedly lost during the login/registration process. This issue has been fixed.
- When utilizing the Aastra MX-ONE server, an issue was observed whereby a phone’s number would be presented twice in an attended transfer, if the phone’s P-Asserted-Identity (PAI) did not contain a display name. This issue has been resolved and in such situations, the number is now only displayed once as expected.
- 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.
- 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.
- 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.
- When the phone was in an idle state but the handset was off hook, if a call was incoming, placing the handset on hook caused the incoming call’s ringing to stop. This issue has been fixed.
 - After establishing a call using the G.722 wideband codec, a decrease in the ringer volume was observed. 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