Implemented 3CX SBC Status in Admin GUI

[Anonymous]

Especially with the emphasis on hosted installations, I forsee many SBC's being deployed, either hardware (Pi) or software on Windows clients. Rather than depend on the "Lost registration" notification per extension, Is it possible to treat the SBC similar to a trunk as for as visibility and notifications go? i.e. a new line item under the System Status or maybe show up in the Bridge section. The big difficulty in my mind is if 3CX tracks the SBCs differently from a 3CXPhone tunnel.

As it sits right now the only method of monitoring is status notification by extension, and that has the potential to generate mass amounts of email traffic.

Thoughts?

 

[Nathan Boyd]

Given that this was my original thread and I've been harping about this forever, I figured I would update with the new Beta V16 Update 2. Just updated my test server and SBC this weekend with the Beta.

I Like the progress SBC integration has finally brought! Along with the integration we have notifications about disconnect SBCs as well. GREAT PROGRESS!!!

A couple things that I noticed through the process up the update from 16U1 to 16U2 Beta. I didn't see a step-by-step, only isolated instructions so I figured I'd wrtie up what worked for me. I did the update to the SBC first (Installed from 3CXISO on HyperV) using this procedure:

apt-get update
apt-get upgrade
apt -t testing upgrade 3cxsbc
No Reboot yet, but after going through the procedure, I'd advise a Reboot at this step

Then I updated my V16U1 Linux install (Running in Vultr) to Update 2 Beta.

Following the the update to the PBX, I did see the SBC listed in the "SIP Trunks" menu, but it still had a red status bubble.

A Reboot of the SBC and the Status bubble turned Green.
Select the SBC checkbox and "Push Config" and it was provisioned.

The Statistics Tab is VERY nice to see, especially the UDP Ping line.