Aastra 9133i SIP Phone Firmware 1.4.3.0809 Download

Posted at November 19, 2024 by PCI-DB Team

Aastra 9133i SIP Phone Firmware 1.4.3.0809 Description

Fixes:

- 480CT: If you configure Time Server 1 as blank, and then configure either Timer Server 2 or Time Server 3 with FQDN, the phone correctly switches to Time Server 2 and 3 as expected.
- 480i CT: A new feature was added to the 480i CT phone. When the phone is on a call and a second call comes in on Line 2, if the user hangs up on the first call, then the call that is ringing on L2 is automatically picked up.
- The “Onhook Action” URI now initiates when the line on a call is terminated, regardless of whether the local handset, speakerphone, or headset hangs up or the far end handset, speakerphone, or headset hangs up.
- Transferring a call or conferencing a call no longer gets interrupted if a call comes into the phone.
- Pressing a mapped Conference key now sends DTMF digits within the active call using SIP INFO or RTP DTMF method.
- Phones now have enough memory when using the BLF List feature with BroadSoft servers.
- All Timezone settings are now correct.
- BLA: The phone no longer terminates its own SUBS when a Sylantro server sends SUBS with Expire: 0 and terminates the subscription for BLA by sending NOTIFY in the subscription state.
- After restoring factory defaults and rebooting the phone, the phone now uses the applicable DNS.
- 480i: Timer Server 1, 2, and 3 now get the applicable IP or FQDN.
- 9112i, 9133i: TUI Phone sip priority header is no longer blank. The TUI for both the 9112i and 9133i now shows “1 SIP” at the screen to enter the SIP Priority for the phones.
- Phone no longer requires a power cycle if loading an XML greater than 5000 bytes.
- When a user picks up the CT Base handset and the far end is using the CT handset, the audio-path now works as expected , and the speaker LEDs light up as correctly on the CT Base and the CT handset.
- When the phone is on an active call and the user presses the Transfer key and dials another extension, and then the callers decides to cancel the transfer, pressing the Cancel key now works as expected and cancels the transfer.
- If you change the download protocol parameter to a value other than “tftp” (i.e., http, https, ftp) in the configuration file, and then the phone gets its configuration parameters using mDNS auto-discovery, the HTTP, HTTPS, or FTP setting is correctly applied.
- The Copy softkey for Directory and Callers List is now correctly disabled when the Directory and/or Callers List is disabled on the phone.
- 480i: The NOTIFY for event REFER from the phone is no long missing the Subscription-state header.
- 480i: The SIP Caller ID feature now works properly. When the “Update Caller-ID” is enabled, the phone no longer displays the information about the previous call.
- 9112i: If configuring a SIP outbound proxy in the configuration file, the value for that outbound proxy now displays correctly in the Aastra Web UI in the Outbound Proxy field instead of the Backup Proxy field.
- 480i, 480i CT: After pressing the “More” softkey to go to a second page on the LCD, the second page now stays on the display.
- 9133i: The phone no longer intermittently locks up, especially after a user checks voicemail on the phone.
- Consultative transfer through SBC now works properly.
- 9133i: Phone no longer factory defaults when turning off the power to the phone.
- Using the volume control during an active call while using the handset or speakerphone, the LCD now correctly displays the volume setting for the Handset or Speakerphone for only 3 seconds and then disappears as expected.
- 9112i: The phone no longer has an improper error handling vulnerability that causes a denial of service.
- 9112i: The Format String vulnerability on the phone no longer causes a denial of service (DoS).
- 480i - DTMF is now correctly sent after call setup when using a speed dial softkey.
- 9133i: Phone now downloads firmware from the server on the first attempt without locking up.
- 9133i: Configured “Pickup” softkey now works as expected.
- 9133i: Phone now longer experiences sporadic "No Service" states.
- 9133i: The failover of an NTP time server now works as expected.
- 480i: Phones no longer lock up due to BLA Subscription termination from server. Memory status information has been added to the Troubleshoot option in the Aastra Web UI to be able to view memory status.
- 480i, 480i CT: The phone no longer locks up when pressing the delete key to delete an entry from the Caller’s List, and then press the UP arrow within a couple of seconds after deleting the entry.
- Copyright date is now updated in the firmware.
- When 4 incoming calls are placed on hold on a phone, and the user then tries to place a call using a speed dial, the LCD now displays “No Line Available” as expected if no line is available. The Line Mgr now correctly checks to make sure a line is available before placing the call.
- The tSipEngine task now works correctly while handling INVITE messages.
- 9133i: The Backup Registrar feature and Proxy Server feature now failover as expected.
- Subsequently pressing the Transfer key and then the Redial key now works correctly as expected.
- 480i: The Phone no longer gets stuck at "50% Updating config" if corrupted .tuz file is being decrypted. If .tuz files are corrupted, the message “Bad encrypted file” displays to the phone and the phone continues to boot as expected.
- 9133i: SIP Phone BLA is now able to pickup held calls for all incoming calls when an outgoing call is attempted from the same line appearance.
- 480i: When a Directory entry with the Character ¿ (U00BF) is displayed in the Spanish language, the phone now allows you to change or delete the entry as expected.
- The feature “Incoming call interrupts dialing" has been updated and the correct feature behavior is identified in this release note in the section

  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