Redundant SBC Documentation

[xirgo]

Hello everyone,

I see that there the Redundant SBC feature was implemented in v16 Update 4 however I cannot find any documentation about it anywhere.
Would anyone who has gone through the process be willing share what steps they needed to take to get this functionality?

 

[cobaltit]

Can you link where you are seeing the redundant SBC feature? I didn't see anything in the change log when searching for keywords 'redundant' or 'sbc' nor anything in the alpha/beta/final blog posts.

 

[xirgo]

Hey Cobaltit.

see https://www.3cx.com/community/threads/redundant-sbc-support.50505/page-3. This feature is showing up as "implemented" and Nick the 3CX CTO says it would be available in Update 4.

Now that I look at this feature request I see you were actually the original requester of this feature

 

[cobaltit]

Ahh gotcha. Yeah I see the same thing as you but my feeling is that either this didn't make it in update 4, or the management console support made it but the SBC update didn't. I would expect an update of the SBC before that happens and there hasn't been a SBC update in while, and certainly not since NIck's response. Unfortunately I think this is still pending.

https://www.3cx.com/blog/change-log/3cx-session-border-controller-build-history/

 

[xirgo]

sounds good, i guess im not crazy then!

I've been able to come up with a few solutions that would require it being installed on a virtual machine and then putting that VM on a HA cluster. The other method was similar but instead of having it on an HA cluster I would run a replication job with something like veeam replication to another host and have a failover plan setup in the event the first instance went down. Both in my opinion are overkill when we could just run two VM's one as a slave both with access to the same virtual IP if the first one misses a few heartbeats.