Tag Archives: troubleshoot

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)

Sophos Services FQDN and IP Address List

This list includes some of the FQDNs and IP Addresses used by Sophos Services, this may be useful for identifying outgoing traffic and creating web filtering exceptions.

*.cloudfront.net
*.ctr.sophos.com
*.hydra.sophos.com
*.sophos.com
*.sophosupd.com
*.sophosupd.net
*.sophosxl.net
108.128.21.191
108.128.75.57
176.34.202.39
18.200.140.39
18.200.233.166
18.200.76.187
18.201.4.220
23.56.184.93
3.248.161.254
3.248.236.19
3.248.239.225
34.240.132.250
34.240.132.63
34.240.70.198
34.240.87.136
34.241.47.153
34.242.175.229
34.242.189.0
34.242.190.168
34.243.109.72
34.243.155.26
34.243.46.159
34.246.1.161
34.246.93.20
34.247.133.51
34.247.19.150
34.248.0.181
34.249.116.122
34.249.16.38
34.249.213.108
34.249.56.234
34.249.75.71
34.250.177.130
34.250.201.204
34.250.232.147
34.251.0.214
34.251.206.176
34.252.99.77
34.253.34.19
34.254.24.5
4.sophosxl.net
46.137.119.69
46.51.205.49
52.16.156.95
52.16.224.248
52.18.132.38
52.18.142.239
52.18.201.121
52.19.111.54
52.19.130.35
52.19.133.193
52.208.138.248
52.208.151.187
52.208.47.80
52.208.61.137
52.209.113.230
52.209.174.16
52.209.74.179
52.211.118.19
52.211.181.255
52.211.215.132
52.211.33.11
52.211.40.77
52.212.179.152
52.212.19.181
52.212.243.39
52.212.80.79
52.213.185.15
52.213.222.108
52.213.224.21
52.213.227.181
52.213.81.142
52.214.122.237
52.214.193.2
52.215.191.67
52.31.157.236
52.48.158.77
52.48.251.68
52.49.52.52
52.49.55.251
52.51.136.43
52.51.19.238
54.154.78.113
54.155.110.171
54.155.150.168
54.155.54.127
54.171.179.249
54.171.2.113
54.171.211.242
54.171.39.210
54.171.82.87
54.194.136.103
54.194.149.107
54.194.158.193
54.194.23.13
54.194.31.233
54.216.250.187
54.220.121.131
54.228.154.173
54.229.182.239
54.229.193.103
54.229.26.205
54.229.29.253
54.246.206.153
54.246.225.42
54.73.159.85
54.73.59.214
54.75.131.11
54.76.53.13
54.77.101.166
54.77.103.108
54.77.109.237
54.77.183.40
54.77.190.39
54.78.168.73
54.78.85.182
63.32.154.88
63.32.247.92
63.34.49.237
63.35.134.40
99.81.41.145
99.81.95.11
amazonaws.com
api.stn100yul.ctr.sophos.com
api-cloudstation-us-east-2.prod.hydra.sophos.com
az416426.vo.msecnd.net
central.sophos.com
cloud.sophos.com
cloud-assets.sophos.com
d1.sophosupd.com
d1.sophosupd.net
d2.sophosupd.com
d2.sophosupd.net
d3.sophosupd.com
d3.sophosupd.net
dc.services.visualstudio.com
dci.sophosupd.com
dci.sophosupd.net
downloads.sophos.com
dzr-api-amzn-eu-west-1-9af7.api-upe.p.hmr.sophos.com
dzr-mcs-amzn-eu-west-1-9af7.upe.p.hmr.sophos.com
dzr-mcs-amzn-us-west-2-fa88.upe.p.hmr.sophos.com
http.00.a.sophosxl.net
http.00.s.sophosxl.net
id.sophos.com
mcs.stn100hnd.ctr.sophos.com
mcs.stn100syd.ctr.sophos.com
mcs.stn100yul.ctr.sophos.com
mcs2.stn100hnd.ctr.sophos.com
mcs2.stn100syd.ctr.sophos.com
mcs2.stn100yul.ctr.sophos.com
mcs2-cloudstation-eu-central-1.prod.hydra.sophos.com
mcs2-cloudstation-eu-west-1.prod.hydra.sophos.com
mcs2-cloudstation-us-east-2.prod.hydra.sophos.com
mcs2-cloudstation-us-west-2.prod.hydra.sophos.com
mcs-cloudstation-eu-central-1.prod.hydra.sophos.com
mcs-cloudstation-eu-west-1.prod.hydra.sophos.com
mcs-cloudstation-us-east-2.prod.hydra.sophos.com
mcs-cloudstation-us-west-2.prod.hydra.sophos.com
samples.sophosxl.net
sdds3.sophosupd.com
sdds3.sophosupd.net
sdu-feedback.sophos.com
sophos.com
sophosupd.com
sophosxl.net
ssp.feedback.sophos.com
sus.sophosupd.com
sus.sophosupd.net
t1.sophosupd.com

Storport.sys – Pre Service Pack 3 Revision History for Windows Server 2008 SP2, Windows Vista SP2 and Windows Small Business Server 2008 (SBS 2008)

Storport.sys – Pre Service Pack 3 Revision History for Windows Server 2008 SP2, Windows Vista SP2 and Windows Small Business Server 2008 (SBS 2008)

08-Nov-2012 – 6.0.6002.22969 – Storport.sys – x86/x64 – http://support.microsoft.com/kb/2780444 – “0x0000012E” Stop error occurs when an application sends a 12-byte SCSI opcode to an iSCSI target in Windows Vista SP2, Windows Server 2008 SP2, Windows 7 SP1, and Windows Server 2008 R2 SP1

06-Apr-2012 – 6.0.6002.22834 – Storport.sys – x86/x64 – http://support.microsoft.com/kb/2528357 – Nonpaged pool leak when you disable and enable some storage controllers in Windows Vista, in Windows 7, in Windows Server 2008 or in Windows Server 2008 R2

07-Sep-2011 – 6.0.6002.22711 – Storport.sys – x86/x64 – http://support.microsoft.com/kb/2511500 – “0x0000007E” Stop error after you perform a hot removal of a PCI device in Windows 7, in Windows Server 2008 R2, in Windows Vista or in Windows Server 2008

17-Jun-2011 – 6.0.6002.22661 – Storport.sys – x86/x64 – http://support.microsoft.com/kb/2553708 – A hotfix rollup that improves Windows Vista and Windows Server 2008 compatibility with Advanced Format disks

11-May-2010 – 6.0.6002.22402 – Storport.sys – x86/x64 – http://support.microsoft.com/kb/983554 – “0x000000BE” Stop error message when you use the Storport.sys driver to manage some storage devices in Windows Server 2008, in Windows Vista, in Windows 7 or in Windows Server 2008 R2

18-Mar-2010 – 6.0.6002.22367 – Storport.sys – x86/x64 – http://support.microsoft.com/kb/981751 – “Stop error code 0x0000007E (SYSTEM_THREAD_EXCEPTION_NOT_HANDLED) in Windows Server 2008 or in Windows Vista

02-Feb-2010 – 6.0.6002.22327 – Storport.sys – x86/x64 – http://support.microsoft.com/kb/979764 – A hotfix is available that improves the logging capabilities of the Storport.sys driver to troubleshoot poor performance issues for the disk I/O in Windows Server 2008

04-May-2009 – 6.0.6002.22128 – Storport.sys – x86/x64 – http://support.microsoft.com/kb/968675 – The storport.sys driver leaks nonpaged pool memory when volumes are scanned, mounted, or dismounted in Windows Server 2008 and Windows Vista

Windows Kernel Power Event ID 41 Error

Windows 7 or Windows Server 2008 R2 may restart unexpectedly, you may get a brief glimpse of a BSOD (Blue Screen of Death) and then find yourself back at the Windows login prompt.  When you inspect the Windows Event Log you will find the following event logged

Log Name: System
Source: Microsoft-Windows-Kernel-Power
Event ID: 41
Level: Critical
Description:
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

The additional info under the event is important because the various bug check codes can indicate different causes.

EventData
BugcheckCode          0
BugcheckParameter1    0x0
BugcheckParameter2    0x0
BugcheckParameter3    0x0
BugcheckParameter4    0x0

Having faced this error recently it eventually turned out that the problem was due to incompatible memory (not faulty memory).  The batch of machines in question were all branded but due to an error with the manufacturers memory compatability matrix had been supplied with the wrong additional memory modules.  When we reverted the machines to the standard 2GB module that was already installed they operated perfectly, we eventually arranged for the additional modules to be swapped and that was the end of the issue.

An important thing to remember is that a memory checker will not show that your memory is faulty if it just incompatible with your particular system or mainboard.

Your system or mainboard manufacturers support should be able to confirm memory compatability and advise on the correct upgrade/type for your system