Solved 3CX SBC not working after update 3CX PBX to V18

[FerryMiddelkoop]

I have a raspberry pi 4 B8 and am trying to install 3CX SBC on it. However after installation the data must be entered from the SBC trunk but a message keeps coming up that the 3CX server cannot be reached. Have gone through all the steps listed on the 3CX website but it still doesn't work. Anyone experience this?

 

[cobaltit]

Are you copy/pasting from the management console or otherwise entering it in exactly as shown in the provisioning info section? Something as simple as adding a trailing '/' can throw it off

 

[FerryMiddelkoop]

Are you copy/pasting from the management console or otherwise entering it in exactly as shown in the provisioning info section? Something as simple as adding a trailing '/' can throw it off

View attachment 23668

I'm typing it exactly. But the sbc version that you can download from the manual is Version 16 and I think it goes wrong there.

 

[cobaltit]

If you are following the guide when it has you download the SBC software on Step 5 it will be grabbing the latest SBC which is 18.0.27

 

[NickD_3CX]

Hi @FerryMiddelkoop ,

Just to make sure you are following the correct guide, this is the one you are following right?
https://www.3cx.com/docs/3cx-tunnel-session-border-controller/

One more thing you could try is, to check if indeed the SBC cannot contact your 3CX Server, from the command line of the SBC type the following command:

wget -O- https://<your FQDN>:<HTTPS Port>/sbc/<Authentication KEY ID>

So if your FQDN was my3cx.contoso.com running on port 5001 and my Authentication KEY ID was pfWSSCkkp6wX, I'd type this:

wget -O- https://my3cx.contoso.com:5001/sbc/pfWSSCkkp6wX

This should show an output similar to this:



Also, where is the 3CX Server installed, in the Hosting Provider or on-prem? The SBC, is it in a different location or on the same LAN as the 3CX?

 

[Alphabetic]

Just my 2 cents.

I had successfully set up a Pi 4 with my v18 SBC this morning.

Make sure your DNS is set up correctly.

 

[FerryMiddelkoop]

Hi @FerryMiddelkoop ,

Just to make sure you are following the correct guide, this is the one you are following right?
https://www.3cx.com/docs/3cx-tunnel-session-border-controller/

One more thing you could try is, to check if indeed the SBC cannot contact your 3CX Server, from the command line of the SBC type the following command:

wget -O- https://<your FQDN>:<HTTPS Port>/sbc/<Authentication KEY ID>

So if your FQDN was my3cx.contoso.com running on port 5001 and my Authentication KEY ID was pfWSSCkkp6wX, I'd type this:

wget -O- https://my3cx.contoso.com:5001/sbc/pfWSSCkkp6wX

This should show an output similar to this:
View attachment 23681


Also, where is the 3CX Server installed, in the Hosting Provider or on-prem? The SBC, is it in a different location or on the same LAN as the 3CX?

i have tried it and get the following error message
ERROR: The certificate of "domain name" is not trusted
ERROR: The vertificate of "domain name" doesn't have a known issuer

However, I do get a message that the PBX can be reached.

But the certificate is good from the PBX. I tried to install the SBC on a windows machine, and there it works.

 

[FerryMiddelkoop]

Hi @FerryMiddelkoop ,

Just to make sure you are following the correct guide, this is the one you are following right?
https://www.3cx.com/docs/3cx-tunnel-session-border-controller/

One more thing you could try is, to check if indeed the SBC cannot contact your 3CX Server, from the command line of the SBC type the following command:

wget -O- https://<your FQDN>:<HTTPS Port>/sbc/<Authentication KEY ID>

So if your FQDN was my3cx.contoso.com running on port 5001 and my Authentication KEY ID was pfWSSCkkp6wX, I'd type this:

wget -O- https://my3cx.contoso.com:5001/sbc/pfWSSCkkp6wX

This should show an output similar to this:
View attachment 23681


Also, where is the 3CX Server installed, in the Hosting Provider or on-prem? The SBC, is it in a different location or on the same LAN as the 3CX?

i have tried it and get the following error message
ERROR: The certificate of "domain name" is not trusted
ERROR: The vertificate of "domain name" doesn't have a known issuer

However, I do get a message that the PBX can be reached.

But the certificate is good from the PBX. I tried to install the SBC on a windows machine, and there it works.

 

[NickD_3CX]

I'll send you a PM to ask for some info.

 

[NickD_3CX]

After investigating, the issue was in fact related to the certificates.
A custom FQDN and certificates were being used on the 3CX Server, but had not been installed with the Intermediate Certificates.

After the Intermediate Certificates were added, it started working.

Windows OS must have these Intermediate Certs built-in, whereas Debian not, hence why the Windows SBC worked.

For anyone else reading this, if you are unsure what you need to do, best choose to use 3CX FQDN, the certificate generation will be done automatically by the software.