3CX SBC v16 issues

[Tahir]

We were on v15 3CX all was working well but was unable to upgrade to v16 as it was a custom install from way back before PBX Express etc was used i believe. I took a backup of the PBX and installed a fresh VPS with latest Debian release and restored the PBX, all is working well however it now seems to have lost connection with my previous SBC where I just updated IP details to point to the new VPS.

I have tried to reinstall SBC v16 over the top but its not on a supported OS. So I have another server where I am trying to install the SBC but it says it cant communicate with the PBX or to check the SSL is valid if its custom (which it is). Both the SSL is valid and the PBX is contactable and accessible via the FQDN + IP from the new machine but the SBC v16 software keeps throwing an error about being able to communicate. I have checked firewalls on the PBX VPS and all are green plus the firewall rules on our existing SBC network are fine as they worked on v15.

Any ideas?

 

[CentrexJ]

Are you using a custom fqdn? You hint at it but not sure.

If you didn’t integrate the intermediate certificate with your ssl certificate this will happen. integrate the intermediate cert and re add the ssl cert to 3CX.

 

[Tahir]

Hi,
Yes this is a custom FQDN. It uses a wild card Rapid SSL / GeoTrust SSL certificate. Any ideas how to add the CA to Debian? Im not that good with Linux.

 

[Tahir]

What is odd is that the 3CX PBX install is working fine, its accessible and throws no SSL errors, Debian has GeoTrust CA certs installed. Why cant i use the SBC?

 

[Tahir]

Ok, so reading into this in more depth it seems v16 SBC screws all the users who wanted to use their own FDQN and SSL. So as i have my own, non *.3cx.co.uk FQDN and SSL how can I get SBC to work or is it now a broken system requiring another fresh install with a stupid *.3cx.co.uk domain to work?

 

[CentrexJ]

You can fix the certificate with windows. Import your ssl to windows MMC certificate services then import the intermediate cert. then export the certificate file with intermediate and update it in 3CX.

 

[Tahir]

It is a linux pbx on debian

 

[Tahir]

But the certificate cant be the issue because it works fine in the web. I feel its 3CX trying to stop people using their own FQDN's.

 

[cobaltit]

But the certificate cant be the issue because it works fine in the web.

So unless you are browsing the management console FROM the PC running the SBC this is flawed logic

I feel its 3CX trying to stop people using their own FQDN's.

So as you are already using your own FQDN this is clearly not the case. Perhaps you may want to re-think why you are using your own FQDN instead of the 3CX provided one. Every instance we manage is using a 3CX provided FQDN because I value my time and I like it when things just work. 3CX did all the hard work for me testing and making sure that configuration works.

 

[Tahir]

To be fair, I have gone down the route of changing to a *.3cx.co.uk FQDN now to avoid all the SSL issues. All appears to be working as is the 3CX SBC however just having some issues with the SIP trunks now not registering, all else is fine. Odd however as the same SIP trunks were working prior to re-install and re-import of the backup.

 

[cobaltit]

Is this a supported provider? If so, I'd add a fake trunk with their template so you can compare settings. v16 added some additional features as to how they handle DNS lookups and it there seemed to be some issues with some providers.

 

[Tahir]

Yup, just re-checked, this is a Gamma SIP provider so should be supported and I have another site using the template on v16.0.2 and it works fine, mine however on v16.0.4 is not working. Any ideas what could be wrong and where I could look?

 

[Tahir]

Also cant seem to delete one of the trunks because it seems to think its bound to an emergency number, but also cant find the location to delete this:


SIP trunks bound to emergency numbers cannot be deleted.
Go to Settings -> PBX -> Emergency numbers. Unlink the SIP Trunk from the Emergency Number and try again.

Found this under General Settings.

 

[Tahir]

UPDATE:

all appears resolved now.
To fix the issues with the SIP trunks i deleted them all, rebooted PBX, recreated but not with the correct templates. So for Voipfone i used the Voiceflex template and change the settings, and for the Gamma I used Zen Business Talk SIP and changed the settings. Seems the default templates are not correct on this version or something was very iffy.

All working so far. Hope this helps anyone else in the same boat.

 

[cobaltit]

Welll we really can't be sure what the issue is since apparently you are on Update 4 which is still alpha. As 3CX would say, in order to confirm you'd need to test under Update 3.

 

[Tahir]

As mentioned above, this has now been resolved even on Update 4. Thankfully not had do do any downgrades to test the issues.