SBC crashing 'Exception code: 0xc0000374'

[Alan H]

We have 1 SBC running on a machine that isn't being utilized that much. Every month or so the service crashes the phones drop, and I have to login into the machine and restart the service to bring the phones back online. I was wondering if I can have multiple SBC running simultaneously on the same network, just incase the main one drops , the other ones will pick up and you will not drop the calls.

 

[Saqqara]

What version of 3BC ? Windows or Debian ?

Have you checked and installed the latest version -
https://www.3cx.com/docs/3cx-tunnel-session-border-controller/

Yes, you can have multiply SBC on the same local network with different IP's, but this will not help you as you configure the SBC IP address for each extension.

If the SBC fails, the extension will not use the other running SBC

 

[Alan H]

It's windows, and the version is 3CX SBC 15.5.7503, would Debian be better? I can spin up a machine and place it on that. Is there away to fix this drop issue?

 

[YiannisH_3CX]

It's windows, and the version is 3CX SBC 15.5.7503, would Debian be better? I can spin up a machine and place it on that. Is there away to fix this drop issue?

That depends on what is causing the crush. If the machine hosting the SBC is not dedicated to the SBC then i would recommend moving the SBC to a dedicated machine to avoid issues.

 

[Alan H]

The machine is a backup domain controller, that is barely to not at all used. so I consider it a dedicated machine because, we really don't use the domain controllers. As for what is causing the crash this is the windows error file.

Faulting application name: 3cxsbc.exe, version: 15.5.7436.0, time stamp: 0x5a38b344
Faulting module name: ntdll.dll, version: 6.3.9600.18438, time stamp: 0x57ae642e
Exception code: 0xc0000374
Fault offset: 0x00000000000f1b70
Faulting process id: 0x13e0
Faulting application start time: 0x01d49e20b6a93a7e
Faulting application path: C:\ProgramData\3CXSBC\3cxsbc.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: a7c1e510-18d6-11e9-80cd-b6ca5e0c1802
Faulting package full name:
Faulting package-relative application ID: