3CX Announces Multi-Tenant Capability

[Natalie_Vox]

I see there have been a number of members mentioning crucial features that are missing from a true multi-tenanted platform. Another thing that is missing (and apologies if this was mentioned. I did try read through everything) is extension ranges. If customer A has a 3-digit extension range and customer B has a 4-digiti extension range, then they cannot be placed on the same "multi-tenanted" environment. We've been advised to have 2 separate 3CX licenses on separate VMs to cater for this. And although this is a practical solution, it negates the commercial benefit of a single platform for multiple companies and makes the provisioning and set-up (which was supposed to be simple and straightforward) far more complex.
Please could this be considered for future enhancements?

 

[SteveITS]

Like SMB, it’s a department on a server. The way 3CX is designed the extension length is the same for all users on the server. So they’d need to allow varying extension lengths.

 

[colinuk]

@Natalie_Vox - you mentioned in a later update this morning ( on a different thread ) ref same extension range in different departments - is this possible now or is there a date on the roadmap to implement? Reason for asking is we standardise on 3 digit extensions in the 200 range and it would be good to maintain parity

1. The ability for different companies on the same instance to have the same extension range / numbering plan

 

[Natalie_Vox]

@Natalie_Vox - you mentioned in a later update this morning ( on a different thread ) ref same extension range in different departments - is this possible now or is there a date on the roadmap to implement? Reason for asking is we standardise on 3 digit extensions in the 200 range and it would be good to maintain parity

1. The ability for different companies on the same instance to have the same extension range / numbering plan

This is not a feature at the moment and I don't see it on the roadmap for future features. Hence my post in the ideas forum. Please go up-vote that idea so that it can get attention from 3CX
https://www.3cx.com/community/threads/multi-tenant-feature-enhancements.128177/

 

[N_G]

As explained in the documentation, you need to decide on a unique extension range for each department and also the extension length per system is fixed. Obviously each group can not have the same extensions. So if for some reason you need this then you will need to look for another multi tenant system.

 

[thiago.lemos@nassautecnol]

Error in viewing the status of extensions in version 20, the extensions are registered and working but the system does not see them and shows them as not registered.
Have you ever noticed this?

20.0 Update 2 (Build 715 Release),

Everyone in this prin is registered and ready to make calls

 

[SteveITS]

shows them as not registered

Ensure notifications are enabled in your browser, for the 3CX server/site. (the web client shows a bell in the upper left, if they are not enabled)

 

[thiago.lemos@nassautecnol]

Yes, I am enabled, I tested both through the webclient and through the Windows app.

 

[SoaringTowers]

Don't believe I saw this in this thread but is the MS Teams integration going to be multi-tenanted too?

 

[N_G]

No teams direct routing integration will require a dedicated instance, as will server side CRM integration, CFD, custom scripts etc.

 

[CSX Cloud]

We were excited to hear about multi-tenancy coming back but its not a true feature as you cannot have multiple users with the same extension as you could in prior version and most of the other platforms on the market. Hope this is something to be considered in more mature releases.

 

[MaxDaemon]

We were excited to hear about multi-tenancy coming back but its not a true feature as you cannot have multiple users with the same extension as you could in prior version and most of the other platforms on the market. Hope this is something to be considered in more mature releases.

Yeah, I have the same concern. I did come up with the idea (as I'm sure someone else has) of making the system a 5 digit system, then using - for instance - 10309 which would be customer 10, extension 309 and so on.

This would be a bit cumbersome for the customer, but since everyone in that company would be able to pre-pend the 10 and then the unique 3 digit ext, it would work.

 

[greychain]

How does it handle the SC licensing? If I have tenant A with a 4 SC license and tenant B with a 64 SC license how does it manage to allocate the licenses?

 

[SteveITS]

How does it handle the SC licensing? If I have tenant A with a 4 SC license and tenant B with a 64 SC license how does it manage to allocate the licenses?

Multi tenant is only one license for the server. Minimum either 64 or 32 SC. Departments/tenants are all under that.

 

[ChrisHumphreys]

Bulk editing is coming
separate phonebook per department is coming
select outbound caller ID will come on a user and per call basis, I.e. you can select your outbound route and caller ID from the app dial pad

Any chance a user can select their outbound caller ID from the PWA App?

 

[richiewhite]

I identified a likely pain point in SIP Trunks around system owners being able to assign DDIs to users/call-handling exts that are assigned to a different department. Popped a post in the Ideas forum as this could be a pain point for ourself to move smaller clients to multi-tenant

 

[tronic]

I identified a likely pain point in SIP Trunks around system owners being able to assign DDIs to users/call-handling exts that are assigned to a different department. Popped a post in the Ideas forum as this could be a pain point for ourself to move smaller clients to multi-tenant

The "system owner" has access to all DID and can assign any of them to any user. But a department "owner" can only see numbers that are part of their department sip trunk.

Are you sure you only have this sip trunk in the client's department and not also in default department?

 

[richiewhite]

The "system owner" has access to all DID and can assign any of them to any user. But a department "owner" can only see numbers that are part of their department sip trunk.

Are you sure you only have this sip trunk in the client's department and not also in default department?

I'm confident, as the trunk had the department I was testing with selected in the Limit To dropdown, is it possible to assign a trunk to multiple departments, outside of the System-Wide setting?

 

[tronic]

We were excited to hear about multi-tenancy coming back but its not a true feature as you cannot have multiple users with the same extension as you could in prior version and most of the other platforms on the market. Hope this is something to be considered in more mature releases.

Why is this such a requirement?
As you would only use an extension or queue/IVR number on a big system, where you wouldn't have enough BLF keys for all the users.
But MCM is designed for small user numbers. In those numbers, desk phone can have a BLF per user and all the apps you would click on their name/picture or search for a name and dial. Numbers then become irrelevant.
What use case would it really matter?

 

[tronic]

I'm confident, as the trunk had the department I was testing with selected in the Limit To dropdown, is it possible to assign a trunk to multiple departments, outside of the System-Wide setting?

If you played with MCM prior to SP2 then it might not have added everything to the correct department correctly. As really, SP2 is when MCM came out.

Make sure the sip trunk is not in the default department and its selected in the sip trunk to be part of the correct department.