Unresponsive Windows SBC causing 'No Service' on desk phones

[kcionline]

Our installer commissioned a Windows 10 based SBC for our small 16 extension setup.

Every 10 days like clock-work, the box becomes totally un-responsive to keyboard/mouse, ping, and even forced shut-down by holding the power button (dell 9020).

The only thing we can do is pull the mains lead out and put it back, every 10 days.

The Windows logs show absolutely nothing.

The provider is at a loss hence why I'm posting here.

Does anyone have any idea what might be causing this?

Is it possible the SBC software is actually killing the PC like a memory leak or something?

 

[cobaltit]

My personal experience for the SBC on Windows was that it's terrible. You should be using a Pi for that size install. Or if you want to continue the Windows route maybe schedule a reboot every Sunday.

 

[BrenttG]

We have some windows SBCs in use, all on the latest build, but what your seeing I wouldnt attribute to the SBC, sounds like that PC has some underlying issue, or else another application is causing the hang. The most common issue we have seen on Windows SBCs is chopping audio or stuck calls, granted both are rare, and have been caused due to the PC cramming windows updates or doing virus scans with a really aggressive antivirus. Windows is not the best land for an SBC, we only have some because it was the only option in the particular environment. We prefer to build them on linux, either as VMs or on small hardware such as a Protectli FW4-0-4-32, they are on amazon.

 

[Alphabetic]

Your Windows Installation becoming unresponsive every 10 days doesnt sound like a coincidence.

Are you running any other software on there?

What are your antivirus schedules?

Look in the task manager to see whats scheduled to run every 10 days.

Run MSCONFIG and check what services (hide microsoft services) are running.

use Task Manager to check what's starting up with the PC.

Search for a memory test in Start and run a memory test.

Check the Windows event logs to see whats happening in the run up to this event.

 

[kcionline]

Your Windows Installation becoming unresponsive every 10 days doesnt sound like a coincidence.

Are you running any other software on there?

What are your antivirus schedules?

Look in the task manager to see whats scheduled to run every 10 days.

Run MSCONFIG and check what services (hide microsoft services) are running.

use Task Manager to check what's starting up with the PC.

Search for a memory test in Start and run a memory test.

Check the Windows event logs to see whats happening in the run up to this event.

Thanks for the advice.

The SBC has nothing else running on it. It is single purpose.

According to the provider, the event logs show nothing at all that might suggest a problem.

Not sure what AV they put on it.

I'm wondering if it could even be a Windows hibernation thing perhaps?

I've asked them for a Debian based replacement as we can't be at the mercy of AV, Windows updates and whatever else in the OS that might be involved.

 

[Alphabetic]

thats a good shout.

i've never had any issues with all my PBX instances on Linux.

It cant be hibernation as that wouldnt be 10 days (by default).

If it is exactly 10 days between problems then It cant even be memory as it's too specific.

As mentioned above, retask your PC for a workstation for someone else. Spend $60 on a Pi, SD card and get a Linux SBC.

 

[kcionline]

Happy to build one on Pi if we have to do it ourselves.

Out of interest, what steps are involved in swapping out a live SBC?

We are using dhcp for the fixed IP reservation. Can we just update the reservation to the new SBC MAC address, and then update 3CX Admin?

 

[Alphabetic]

I would give the Pi static TCP/IP info when setting it up and create an exclusion in DHCP instead.

when the SBC goes offline the phones will become unregistered so make sure your Pi is configured ready to swap.