Solved SBC Install Issue

Status
Not open for further replies.

GodLovesATryer

Free User
Joined
Feb 14, 2021
Messages
3
Reaction score
1
Hi, I am having an issue setting up an SBC for our in house 3CX. The SBC and 3CX reside on the network. The SBC is being installed to provide secure connections for off premises extensions.
I have setup the 3CX as per the guide , but when it comes to connecting the SBC to the it fails.
I get the message
Unable to reach the 3CX Server at
https://xxxxxxxx.3cx.co.uk:5001
Please double check "3CX Provisioning URL " value and confirm the the SBC Trunk is created properly from within your 3CX Management Console.

Also 3CX must have a valid secure SSL certificate so if you have a custom certificate which has expired or not renewed, the install will fail.

I have tried install the SBC via raspberry pi and debian both with the same result.

I have used the firewall checker on the 3CX all checks ok there .
I can login to the 3CX remotely using the FQDN.

Can any one suggest a remedy?

thanks
 
Ok thanks, I'm use to Avaya IP Office were you would use a SBC to provide secure connections to remote phones.
 
So a standard SBC would do that. The 3CX SBC would be installed local to the remote phones. It's primary benefit is PnP provisioning along with easy firewall traversal (no port forwarding needed). It does also provide encryption of the remote phone traffic.
 
If it is same LAN you cannot reach FQDN https://xxxxxxxx.3cx.co.uk:5001 unless you have local DNS Server or Firewall configuration pointed 3CX FQDN to Local IP 3CX Server IP.
 
  • Like
Reactions: JohnS_3CX
If it is same LAN you cannot reach FQDN https://xxxxxxxx.3cx.co.uk:5001 unless you have local DNS Server or Firewall configuration pointed 3CX FQDN to Local IP 3CX Server IP.
That may be true, but as @cobaltit said, there would be no reason, nor would it be recommended to install the 3CX SBC on the same LAN as the 3CX PBX. Just wanted to point it out.
 
Thanks , for the advice guys got it working with a sbc at the remote end . Just for sh*ts and giggles got it working by stun remote with TLS enabled. The remote end is also a 4G router which took a bit of fiddling to turn off sip alg which was also causing issues.
 
  • Like
Reactions: YiannisH_3CX
Status
Not open for further replies.

Forum statistics

Threads
111,974
Messages
590,081
Members
164,899
Latest member
mazet