Tag Archives: Firmware

Yealink Handset Crackling or Buzzing from Handset and Speakerphone

You may occasionally notice that your Yealink phone starts crackling or buzzing.  This has most commonly been observed after the phone has been in operation for sometime without being rebooted or after a firmware update.

Below are some troubleshooting steps that you can try to resolve the buzzing and crackling

  • Try restarting the Yealink Phone (You can either remove the Power or Ethernet Cable if using PoE, alternatively just hold down the X key until you are prompted to restart the phone)
  • Try a Factory Reset on the Phone, ensure that you have all the required settings to reconfigure the device after the factory reset.
  • Update the phone firmware to the latest release and then perform a factory reset prior to configuring or provisioning the phone again.
  • Confirm if crackling or buzzing is just occurring from the handset or also from the speakerphone.  If just the handset exhibits the issue then the cable or handset may need to be replaced.
  • Ensure that the VoIP/SIP Phone System is up to date
  • Ensure that you are using the most appropriate voice Codecs for your phones and the SIP Trunk. (A-law is commonly used in Europe and u-law is generally used in the United States)

Watchguard XTM 1050, XTM 2050, XTM 2 Series, XTM 3 Series, XTM 5 Series, XTM 8 Series – Fireware XTM OS 11.6.5 Update 1 Build # 415678

Watchguard XTM 1050, XTM 2050, XTM 2 Series, XTM 3 Series, XTM 5 Series, XTM 8 Series – Fireware XTM OS 11.6.5 Update 1 Build # 415678

Issues resolved in Fireware XTM v11.6.5 Update 1 Build # 415678

General
•This release resolves an issue that caused some configuration saves to fail to take effect on XTM 21 – 23 devices. [70686]
•A problem that caused the XTM 1050 10 Gigabit Fiber ports to fail has been resolved. [70118]
•This release resolves a problem that caused a kernel crash when a reset packet is sent out through the 10 Gigabit Fiber ports on the XTM 1050 and XTM 2050. [70384, 70296]
•RSS feeds no longer try to download RSS updates every six minutes. RSS updates are now queried every 24 hours. [67355]
•A memory leak related to the OSS-Config process has been resolved. [70662]

Proxies and Subscription Services
•The SIP ALG now supports REFER method for call transfers. [59635]
•File downloads no longer stall when you use an HTTP packet filter policy with IPS. [67659]
•The scand process has been improved to restart more quickly in the event of a crash.

Logging and Reporting
•This release resolves an issue that caused the logging processes on the XTM device to use a high percentage of CPU. [59979, 66060]

Networking
•The SNMP process is now automatically restarted if it becomes stuck in a dormant state. [66491, 70975]
•The IGMP_Max_Membership setting for OSPF has been increased to support a large number of VLANs with dynamic routing. [69979]

FireCluster
•The Terminal Services TO Agent now works correctly when used in an active/passive FireCluster. [70098, 69944]
•This release resolves a problem that caused the master in an XTM 2050 FireCluster to go into an idle state when you added a new interface. [70392]
•This release resolves an issue that caused a low memory condition when an active/passive FireCluster was configured. [70204]
•The Virtual MAC address is no longer sent from the backup master when you use an active/passive FireCluster with DHCP relay enabled. [71028]

VPN
•The amount of time it takes to fail over from a leased line to a branch office VPN with OSPF or BGP has been reduced. [70460]
•This release improves Branch Office VPN stability for XTM devices behind a network device that applies NAT. [70394, 59859]
•This release resolves a problem that caused the IKED process to crash under certain conditions. [70638]
•Frequent Mobile VPN client connect/disconnect sequences no longer cause a low memory condition for the XTM device. [67538]
•The Mobile VPN client for iOS no longer disconnects after three minutes of idle time. [69430]

You can download 11.6.5 Update 1 Build # 415678 from Watchguard Support Portal by logging in to your account.

Watchguard XTM 1050, XTM 2050, XTM 2 Series, XTM 3 Series, XTM 5 Series, XTM 8 Series – Fireware XTM OS 11.6.3 – CSP3 Build # 362451

Watchguard XTM 1050, XTM 2050, XTM 2 Series, XTM 3 Series, XTM 5 Series, XTM 8 Series – Fireware XTM OS 11.6.3 – CSP3 Build # 362451

11.6.3 – CSP3 Build # 362451 Resolves the following issues:

  • BUG70662: The OSS-Config process no longer leaks memory
  • BUG67355: RSS Feeds no longer try and download RSS updates every 6 minutes. The new update interval is 24 hours.
  • BUG70638: Resolved issue causing the iked process to crash under certain conditions.
  • BUG71028: When using FireCluster Active/Passive, with DHCP relay enabled, the Virtual MAC address will no longer be sent from the Backup Master causing network disruption.
  • BUG70975: The SNMP process on XTM 25/26 and XTM 33 will now be restarted automatically in the event it becomes stuck in a dormant state.

You can request 11.6.3 – CSP3 Build # 362451 from Watchguard Support by logging a support case online, they should then be able to provide an ftp download link and appropriate credentials.

Please note that Watchguard CSP releases are cumulative so you should only need to apply the latest to ensure that you also have any previous fixes.

Change of behaviour with TRAN (Transfer) key after upgrading Yealink T3X and Yealink T2X Firmware to V70

I have noticed a change of behaviour with TRAN (Transfer) key after upgrading Yealink T3X and Yealink T2X to the new V70 firmware along with upgrading 3CX Version 11 to Service Pack 3.

It appears that the default DSS Key Transfer Mode is changed from Attended Transfer to Blind Transfer.  An Attended Transfer was always performed when you used the BLF/DSS Keys to perform the Transfer in previous Yealink firmware versions.  For example A calls B wanting to speak with C, B presses TRAN button and then presses the BLF/DSS Key for C.  In this instance B should be able to speak with C (Attended Transfer) to see if they want to take the call rather than A just being passed straight to C (Blind Transfer).

yealink blind transfer

 

You need to login to the Yealink HTTP Interface and then navigate to Phone->Features->Transfer Settings and Change “Transfer Mode via DSSKey” to “Attended Transfer” by using the drop down menu.

yealink attended transfer

So by changing this simple setting you can restore the Attended Transfer function whilst still taking advantage of the V70 Firmware for your Yealink Phone.