Solved Cant provision SBC Pi

[Alphabetic]

Hi Guys,

I've just deployed a 3CX on the latest version to date.

I've set up an SBC in SIP Trunks and i'm trying to set it up on the Pi but it tells me it cannot reach the server.

the only thing difference is that this time I've used ports 443 and 80 instead of 5001 and 5000.

I'ev copied and pasted the prov link and password from the mgmt console but i'm still getting the same thing.

 

[Alphabetic]

Ok this is a result of doing too much at once.

I set the hostname of the Pi to be the FQDN during set up.

 

[ChrisC_3CX]

The first things to check would be the following:

1. Is Port 443 reachable from that site? Maybe you could try reaching the Management Console from the same site the SBC is as a quick check.

2. Is the FQDN resolvable from the SBC site? Maybe try an "nslookup FQDN" from that site, or better yet, from the SBC itself.

3. Are you perhaps using a custom FQDN instead of a 3CX one? It might be that the CA is not trusted by the SBC's OS, in which case you would have to import it on the OS level.

I think the easiest way to test all three of the above is to rung the following command on the SBC which should provide you with a more specific reason:

wget https://FQDN:443


Note: Despite the fact that you were able to resolve this, I'll leave this post for anyone else that might be facing a similar issue for a different reason.