Solved URGENT SBC HELP NEEDED

[360CTM]

Hello fellow 3cx guru's, I am having a major headache with an SBC. I have had this system operational for over a year and one day the SBC just simply failed. Went to the customer and restarted and checked everything out. back on line I left and 4 hours later it was down again. Provisioned a new SBC, reprovisioned phones, everything worked. 2-4 hours later down again.
Went back out again today and made a few changes with the network. everything was fine again, left feeling confident with my repairs, and now down again. I am beside myself with where to go from here, was there an update pushed out that is causing this issue? Is anyone else dealing with this?

These is a windows based SBC for a small system of 7 phones.

 

[cobaltit]

Given the lack of complaints on the forums I'm fairly certain there's no update issue. Personally I've never liked the Windows SBC and we only do Linux/Pi SBCs. You haven't given much info as to what troubleshooting you've done. You restarted the service, the entire box? Was it locked up? Any errors in the event log?

 

[360CTM]

Given the lack of complaints on the forums I'm fairly certain there's no update issue. Personally I've never liked the Windows SBC and we only do Linux/Pi SBCs. You haven't given much info as to what troubleshooting you've done. You restarted the service, the entire box? Was it locked up? Any errors in the event log?

No log errors. The SBC is still powered on and i can remote into the SBC. Sorry I don't have any more info to provide. From my end everything looks like it should be working fine. On a fresh startup they can make and receive calls without issue. Then after a while (Latest restart was 20 min to failure), the trunk shows down and no calls can be made. I have checked the firewall for any potential blocking issues, no changes have been made to the network, setup, phone system, etc. Its not a firewall issues as the system works fine when up. It's not an install issue, as this system was operational for over a year without one hiccup.

Maybe my next step is to try a linux box.

 

[HRMNY]

Does the 3CXSBC service show stopped or running, when it happens?

Does restarting the service fix the issue? Or does rebooting the pc only fix it?

When you say event log do you mean Windows Event Log or 3CX logs in "C:\ProgramData\3CXSBC\Logs"?

 

[360CTM]

3cx event log. Ill go check the windows log. When it fails the service is still running. I am curretly running the first SBC from my house to see if I can recreate the problem.

 

[360CTM]

thanks for the help. I have plugged in the original failed box at my house and it is staying live, so I am hunting sown network issues / conflicts now

 

[princer800]

Yes - IP conflict could definetly do somthing like this.

 

[hogan71088]

If theres an IP conflict it will most likely be up and down like a yoyo. Setup the trunk alert and see if you continuously get alerts.

 

[princer800]

Arp timeout is 1500 seconds (25 min) - and if you have another systemthat responds faster - systems could get stuck onthat device. Unplug the SBC and start a ping - better not answer.
Always do an "arp -a" after any ping test to seeif IP is in arp table. PC's pretty much have firewalls on these days - so won't png but they will arp - and mess you up.

 

[360CTM]

Problem solved. It was a freaking bad network cable. days spent troubleshooting, and its a freaking bad network cable, about $1000 spent on replacement gear. ARRRRRGGGGGGGHHHHHHH. Story of my life.

 

[AlexanderReichert]

Problem solved. It was a freaking bad network cable. days spent troubleshooting, and its a freaking bad network cable, about $1000 spent on replacement gear. ARRRRRGGGGGGGHHHHHHH. Story of my life.

But still thank you for sharing the solution. Good reminder to check even the basic things.