Unsupported multi-tenent 3cx

[Alberto Pascoal]

How would like to know if is possible to run 3cx on multinent scenario for my customers

 

[Saqqara]

Current version is not designed for multitenant - you will have so many issues to overcome if you try

Host each client in the cloud, or separate virtual machines inhouse

 

[Alphabetic]

3CX have also been there, done that and decided they didnt like it

 

[Anaphylaxis]

3CX have also been there, done that and decided they didnt like it

Any reason why? Seems like it would be an extremely useful feature to have. Same with horizontally scalable PBXs

 

[Alphabetic]

Any reason why? Seems like it would be an extremely useful feature to have. Same with horizontally scalable PBXs

Probably to do with redundancy. If the host went down it to all PBX instances down with it. I imagine that ultimately it was down to keeping 3CX as simple as possible too. You'd think it was convenient until you had a ransomware attack or a power outtage.

 

[Evolute IT]

Redundancy and security. Those are the reasons.

 

[VoIPTools]

I have to agree with all the other posts above. There are so many places where you can run into conflict with other tenants. For example, you would have to not use the company directory. You could not have custom on-hold music for each tenant, you would have to block the ability to dial other extensions not in your tenant... the length of challenges is very long. It's so cheap to set up a linux VM that it simply is not worth the effort and shortcomings.

 

[leejor]

The multi tenant version was retired with the release of version 15...

https://www.3cx.com/blog/news/cloud-ready-pbx-multi-tenant/

 

[Anaphylaxis]

Probably to do with redundancy. If the host went down it to all PBX instances down with it. I imagine that ultimately it was down to keeping 3CX as simple as possible too. You'd think it was convenient until you had a ransomware attack or a power outtage.

I am using a dedicated server hosting these as linux containers, this could directly interface with our hypervisor I don't see how this is any different than using a VPS. I also have full control over the security of 1 machine instead of having to manage many different machines I just don't even allow ssh on the containers..

Redundancy and security. Those are the reasons.

See above.

I have to agree with all the other posts above. There are so many places where you can run into conflict with other tenants. For example, you would have to not use the company directory. You could not have custom on-hold music for each tenant, you would have to block the ability to dial other extensions not in your tenant... the length of challenges is very long. It's so cheap to set up a linux VM that it simply is not worth the effort and shortcomings.

These are 3CX limitations not limitations of a multi-tenant environment. Additionally yes, it's very cheap to setup a linux VM (free if you have a hypervisor), so why can't 3CX just do this and manage it using their multi-tenant hypervisor system?

 

[Alphabetic]

These are 3CX limitations not limitations of a multi-tenant environment. Additionally yes, it's very cheap to setup a linux VM (free if you have a hypervisor), so why can't 3CX just do this and manage it using their multi-tenant hypervisor system?

Because then it's your fault when it all goes pete tong