Aastra 6731i SIP Phone Firmware 3.2.2.3109

Fixes:

- 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 send only 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 send only 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 send only INVITE would not be sent). This issue has been fixed. 
- An issue was observed whereby in certain situations if a phone with an SCA configured 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.
- The phones can now accept a maximum of 256 characters when defining HTTP, HTTPS, TFTP, and FTP server download paths.
- All phones except the 6735i, 6737i, and 6739i: An enhancement has been made whereby a phone configured with the Assistant role (when using the BroadSoft BroadWorks Executive and Assistant services feature) will now recognize filter key values that start with a national number prefix (e.g. “0” for France).
- 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.
- 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.
- 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.
- 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.
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.
- 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
- 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 ring back 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 signaling priority. This issue has been corrected and the phone now sends the proper configured voice signaling priority in the SIP Real-time Transport Protocol (RTP) packets. 
 - When initiating a transfer or conference call by first pressing a Speed dial key configured as a prefix ending with a + symbol (e.g. #31#+) and then by using the dialpad or a Spee ddial 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.

About VoIP Phone Updates:

Firmware updates for VoIP Phones are very important as they usually contain many bug fixes, add new features and updates, as well as add additional security features.

One of the main problems users come across when attempting to upgrade their VoIP Phone is that their device may be locked to a certain Carrier. Adding an unlocked version of the firmware may cause the device to stop working on certain networks. This operation may void your carrier warranty and, as such, is not recommended.

Before downloading, make sure that you have selected the appropriate firmware for your device and that the update supports the VoIP service provider you use.

Generally, it is important to upgrade older firmware in sequence (v1 to v2 to v3) and so on, because many manufacturers don't launch standalone update packages.

Although using beta release firmware packages is tempting, it can prove to be quite risky as well. If you choose to try beta release updates, please read the detailed firmware notes and make sure that you have the possibility to revert to an older and more stable version in case the beta turns out faulty.

If you feel that this update can improve the functionality of your VoIP Phone, please use the download button and follow the installation instructions.