Linux SBC fails to connect but Windows version connects on same hardware

[ARHAssociates]

I am setting up an SBC, using a small form factor Dell Desktop computer. If I use the 3CX ISO to build the SBC, then enter the provision URL and key, I get failed to contact. I can drop to root and ping the phone system so the networking is working correctly. If I take the same computer, install Windows 10, then install SBC for Windows using the same provision URL and key, it works.

Any ideas?

 

[ChrisC_3CX]

Are you perhaps using a custom FQDN for this PBX?

Also, if you happen to have the Linux SBC Host running, can you try running:

wget https://<FQDN>:<HTTPS_PORT>

What's the output for the above?

 

[ARHAssociates]

Interse

Are you perhaps using a custom FQDN for this PBX?

Also, if you happen to have the Linux SBC Host running, can you try running:



What's the output for the above?

Interesting, It is a custom certificate, but wget says Certificate not trusted. It is a wildcard certificate from Godaddy. This explains why the windows version works. It is absolutely a valid trusted certificate. I log into the console and the certificate is showing valid.

 

[ChrisC_3CX]

You'll have to make sure the certificate on the PBX end contains the full chain including any intermediate certificates. You should be able to get the whole certificate bundle from the issuer.

 

[ARHAssociates]

You'll have to make sure the certificate on the PBX end contains the full chain including any intermediate certificates. You should be able to get the whole certificate bundle from the issuer.

Godaddy makes the bundle available as a .crt file. Host PBX is also 3CX linux, so where should I place/append the bundle to.

 

[ARHAssociates]

How to a get the SBC install to rerun the setup wizard again to re-input the URL/Key

 

[ARHAssociates]

Godaddy makes the bundle available as a .crt file. Host PBX is also 3CX linux, so where should I place/append the bundle to.

I got it, I just appended the info to the existing .crt file.

 

[ARHAssociates]

SBC is up, thank you, it was just easier to rerun the full installation.

 

[ARHAssociates]

Last question for SBC. I have a field office where this SBC will go. The 3CX host server is available via the Internet or via the internal VPN. I can manage the split dns, but should I go to the publics Internet IP address of 3CX host, or use the internal IP via the VPN - or does it really not matter.

 

[ChrisC_3CX]

To be honest, if you have a site-to-site VPN making your IP Phones logically local to the PBX means you will not need the SBC at all, as a matter of fact you must not use it if that's the case, unless for some reason you do not want that traffic to traverse the VPN and you have all SBC and IP Phone traffic go out to the internet instead of via the VPN tunnel.

 

[ARHAssociates]

To be honest, if you have a site-to-site VPN making your IP Phones logically local to the PBX means you will not need the SBC at all, as a matter of fact you must not use it if that's the case, unless for some reason you do not want that traffic to traverse the VPN and you have all SBC and IP Phone traffic go out to the internet instead of via the VPN tunnel.

The VPN puts the remote office in a different subnet of the 3CX Network (it is not bridging the same network that the 3CX host is on)

Phone Network - 172.20.200.x
Remote Office 172.21.200.x

 

[ChrisC_3CX]

Still, those are local subnets with local routing between them meaning you will have to provision the IP Phones using the Local Provisioning method.

The only problem might be that you won't be able to use PnP provisioning (IP Phones won't come up in the PBXs "Phones" section) due to the fact that they are on different subnets which probably means that multicast does not span across them.

That said, you will have to use to manual link provisioning method mentioned in our provisioning guides.