Multi-tenant with 3CX hosting. Can't add new BT HSIPT Trunk (UK)

[robsonh]

Yesterday I migrated my multi-tenant 3CX instance from self-hosting on AWS to 3CX’s hosted platform. The migration appears to have completed successfully - all IP phones and existing SIP trunks are operational.

I have been using BT Wholesale (HSIPT) SIP trunks, and the existing trunks continue to function without any issues. However, I am unable to add any new trunks because BT Wholesale is not listed as a Supported or Preferred provider in the hosted environment. This restriction only appeared after moving to 3CX hosting.

How can I continue using my preferred SIP trunk provider, BT Wholesale (HSIPT), when running on 3CX’s hosted platform?

 

[bitn2]

You cant, only supported providers.

 

[YiannisH_3CX]

Hi @robsonh

When you restore a multi-tenant backup to a Hosted by 3CX installation you essentially create an SMB server where not all templates are available. Since BT Wholesale is an IP based provider the template is not available now. This restriction is in place so IP based providers do not cause issues on multi-tenant systems.
You need to either switch Multi Company off or go back to self hosting or use a supported provider from now on.

 

[robsonh]

Hi @robsonh

When you restore a multi-tenant backup to a Hosted by 3CX installation you essentially create an SMB server where not all templates are available. Since BT Wholesale is an IP based provider the template is not available now. This restriction is in place so IP based providers do not cause issues on multi-tenant systems.
You need to either switch Multi Company off or go back to self hosting or use a supported provider from now on.

Thank you for coming back to me. Apologies if I am misunderstanding but I believe that I am using registration based trunks? Would it be possible for me to share the SIP Trunk checker's report with you privately to verify this?

 

[YiannisH_3CX]

The template we have for BT wholesale trunks are IP based however all BT templates are not available in SMB due to limitations in their configuration.