Multiple Session Border Controllers in v16

[per.eriksson_1]

Dear All,

I must do something wrong here...

I use Grandstream 2130 phones and PFSense all over and the settings in the firewall are the same. I can only get 1 SBC to work and I need 4 in different locations.

• Installed 3cx debian without issues. Smartphones works from everywhere
• The first SBC Debian works fine, provisioning and everything from one remote site.
• I then do exactly the same thing with the other 3 sites. They all comes up nicely in the trunks view and seems to be ok. I see the new phones in the phone panel and the SBC manage to push the provisioning link nicely into the phones but the phones doesn’t reboot and refuses to provision.
• I can access the 3cx server via HTTPS on the same LAN as the non provisioning phones are on and the 3cx windows app works fine as well.

I don’t really understand what is going on here as the first site comes up without any issues at all and the others refuse. I read on the forum that v15 had some secret trick to make several SBC’s work together. Apparently it was of the type that could not be written out on the forum. Is that trick still needed in V16.

Does someone have v16 working with more than 1 SBC's and possible have had the same issue and solved it?

Regards

Per

 

[eddv123]

As a test can you try (depending what access you have) manually configuring the device with the provisioning link perhaps ? we do this for STUN and SBC phones at times, but SBC you will have to try and see yourself.

The provisioning process involves sending an HTTPS request for its provisioning file, 2130's are supported phones but are you also running supported firmware for the device also.

https://downloads.3cx.com/downloads/v160/templates/firmwareupdates/grandstream/gxp2130fw.bin

 

[leejor]

If this is the same issue, from almost 2 years ago... https://www.3cx.com/community/threads/multiple-sbcs-connecting-to-one-pbx.54299/ and was not resolved in an SBC update.

Then you may want to do, as advised in the last post, and contact 3CX directly.

 

[eddv123]

This cant be an un-resolved issue, unless I have missed something.

We have lots of sites on v16 using multiple SBC devices (and via PfSense firewalls also) they all work very well with no issues at all. The largest amount we have that I am aware of is 8 SBC's to a single 3CX system.

 

[JohnS_3CX]

A few things to check here:

1. Ensure that there is no firewall blocking the phones from accessing the provisioning URL and downloading the file
2. Run a capture on the phone interface to see if it receives the NOTIFY message from the SBC, which should contain the provisioning URL
3. Ensure the DNS the phones are using, can indeed resolve the FQDN

And of course, when provisioning the extension in the management console, ensure that the SBC IP field is the correct IP of the SBC at that specific site.

Note: if the SBC machines are Pi's or VMs, please ensure you did not clone them. The OS of each SBC must be a fresh install to generate some unique IDs.

 

[per.eriksson_1]

Strangely enough, when I added DHCP option 66 it started to work on the other sites which is, what I understand, a bit contradicting to the instructions....
Phones not having PnP connects directly to the server while PnP phones goes via SBC.
When the 3 other sites started working then the first one stopped working until it also got DHCP option 66....

Ohhh...Forgot to mention that I also have VPN between the sites which makes direct connection possible. What is best, pure VPN or SBC i dont know but time will tell. I try the SBC way for now.

 

[leejor]

If you have VPN between sites, then the SBCs are unnecessary. Essentially all sets are "local".

 

[per.eriksson_1]

i had no luck with only option 66 when I set it all up from the beginning so that's why i went the SBC route.
I will do a new try today when site 5 shall be configured.

 

[cobaltit]

Do all the sites have unique subnets?

 

[per.eriksson_1]

Yes, the normal way to do VPN as we need routing between the sites.
I will do more tries with the Grandstream 2130. the Yealink worked immediately as soon it got the provisioning link on site 5 so why not the Grandstream.....