SBC Beta

[Lee Cramman]

I'm trying out the new SBC beta. I've updated both the SBC and PBX to the latest version as per the instructions but once all services restart my legacy SBC shows as 'down' under 'Trunks'.

This means I can't push a config to it. Looking at the Authentication KEY ID, it's not the same one my SBC uses.

Meanwhile, my SBC continues to function...

Any ideas how I can get the SBC listed under the GUI?

 

[eddv123]

I set this up on Friday and found you could use the legacy v15 SBC with the system still alongside the v16 but the v15 would not appear in the Trunk area like the v16 one did - its not meant to I don't believe.

Also ensure that you do not get the SBC Password, PBX tunnel password and Authentication KEY ID confused either as it would seem that these are all different to one another.

 

[Nathan Boyd]

@Lee Cramman Did you update the SBC to the Beta, or just to the latest stable version? the path I took on my test setup was to upgrade the SBC using this command set:

apt-get update
apt-get upgrade
apt -t testing upgrade 3cxsbc

Then Updated the PBX itself to the Beta and the SBC showed up in Trunks, but as offline. After a reboot of the SBC OS, it showed as online, but needed a config pushed to it. Using the "Push Config" button and it was all golden.

This is Great progress from 3CX!!

 

[Lee Cramman]

@eddv123 the SBC is updated. I possibly am getting those things mixed up!

@Nathan Boyd that's exactly what I did - so maybe I need a reboot of the SBC? I'll give that a spin.

Thanks guys.

 

[Lee Cramman]

SBC reboot worked perfectly. I suspect a stop and start of the service would also have worked but it's probably useful info for anyone else out there.

 

[MichaelB_3CX]

When you upgrade your SBC and SBC connects to an Update 2 PBX it should create the SBC Trunk instantly. If you had to reboot the SBC to see this I only could imagine that after update the SBC did not start service or it did not resolve your FQDN? Will be nice to have some logs about this to understand better, could be you can try to reproduce this again and send me logs via pm.

 

[Lee Cramman]

Sorry, unable to reproduce as don't have a legacy SBC to import any more...

I would guess that you are correct about the SBC service though as it was still functional, it just wasn't showing as live / available in the admin console.

I doubt there was a problem resolving FQDN as this would have been evident on other hardware on the same network / subnet connecting to the PBX through the same gateway so I'm pretty sure it was a service restart issue.

 

[Nathan Boyd]

@Lee Cramman I'm not positive about that. During my initial testing, I did a service restart when the SBC still didn't show as online prior to rebooting the SBC.

 

[Lee Cramman]

@Lee Cramman I'm not positive about that. During my initial testing, I did a service restart when the SBC still didn't show as online prior to rebooting the SBC.

Well, my thoughts were an educated guess and yours are experience so I would be inclined to think you are right. @MichaelB would like to have some logs from you if it's reproducible.