Windows SBC Best Practice

[Gandeep]

I am trying to setup 3CX SBC on a raspberry pi 3 using Stretch.
I keep getting unable to reach the 3CX Server at....
I am able to ping it fine and the firewall checker passes.
Any suggestions?

 

[NickD_3CX]

I am trying to setup 3CX SBC on a raspberry pi 3 using Stretch.
I keep getting unable to reach the 3CX Server at....
I am able to ping it fine and the firewall checker passes.
Any suggestions?

Try following the instructions here first: https://www.3cx.com/docs/installing-pbx-raspberry-pi/
Specifically only do what is mentioned in sections:

• Prepare the SD card with Raspbian
• Set hostname
• Set a static IP

the rest is for installing the PBX. Basically, start over again.

Then try again to follow the instructions here: https://www.3cx.com/docs/3cx-tunnel-session-border-controller/#h.wrvwnh8912cq

 

[Gandeep]

It was an issue with the Cert.
I needed the Cert, Root Cert and Intermediate Cert in one file.

 

[kahodges]

I can tell you firsthand, as a third party IT consulting company, I run into customers who are scared to death of the term Linux, and even had some throw tantrums over it. I go along with their lack of knowledge on the subject, and just do not tell them that their NAS is running on Linux, or their file server is running Linux, or their brand new PBX is running on a Debian install on Digital Ocean. Once they have been complacent in knowing how smooth things have been running for a while, we have a conversation over a couple of adult style drinks. Wins them over every time.

 

[AGidi]

As many mentioned, Windows SBC best practice is linux.
We have been deploying SBCs for several years now in Mexico, we tried ONCE on windows. Dropped it and went linux all the way. We create what we call infront of the client an "SBC Appliance" we dont tell them, they don´t want to know. We have dozen smallers ones and some larger units for larger PBXs, it just works. best wishes