SBC with 3CX

[amith80kumar]

I am installing SBC with 3CX for the first time. After linux based SBC installed, I see the SBC is showing red in 3CX.

what are the configurations that I need to do to get SBC registered?

 

[fxbastler]

Read and use the manual:
https://www.3cx.com/docs/3cx-tunnel-session-border-controller/

Pay attention to the order of the steps during installation. If the order is incorrect, the SBC IP may be blacklisted by the 3CX und you have to wait 24h with a 3CX SMB.

 

[fortech]

Footnote for what it is worth on this thread,
Installing SBC is quite seamless when you follow the documentation / steps / involved.
you will need to
tell 3cx instance you want to add a 3cx SBC instance
then during install of the 3cx sbc instance, you must provide your 3cx - FQDN for linking // and a 'secret key' to allow the SBC to register itself / link to the 3cx instance
it really is not hard, but it is definitely the case of 'must do it in the correct sequence, or it will not work'
clearly the SBC needs internet access / ability to route and communicate to the 3cx instance
definitely similar concept to the famous far side comic, "Pants, then Shoes!"
as per
https://au.pinterest.com/pin/first-pants-then-your-shoes--385339311864641525/



Tim

 

[amith80kumar]

thanks for your message. I did exactly the same and in order. when it asked me to key in the provisioning URL and authentication key ID, I gave the correct URl and key and it took it. However the SBC shows red in the portal and when I try to add a phone and register, the phone wouldnot register. The phone has reachability to internet. Not sure if SBC is doing its job. Anyway I can check the logs?

 

[fortech]

Hi, OK - so - if your SBC is showing up as red, then it is not active / not working correctly / not linked to the 3cx correctly.
So phone deployment via the SBC is also not possible until that is resolved.

what version of 3cx are you using (free vs non-free / trial / other?)

depending on the version of 3cx you are using, will give (more or less) visibilty to logs in the console

is there a possible scenario, there is a firewall interfere with your SBC<>3cx communication somehow?
for example SBC is in the branch office
3cx in cloud / has public IP
branch office firewall has outbound firewall rules which interfere with outbound traffic maybe?

normally if you install the SBC <> and it links up and communicates to the 3cx instance, that typically means "good to go" and then after ~5minute (or 30 second..) delay - the SBC should show up as visible / green dot status / in the 3cx webUI

so the fact that is not happening, maybe is telling us
Firewall at 3cx site is interfering?
or
Firewall at SBC site is interfering?

Tim