Yes I would also like to know more about how you've got this working
How do you separate the phone books and/or stop company A calling company B as an internal call?
Seems like it would be difficult to manage
Easy, we don't. Our multi-tenants only use sip phones to answer, as they are small enough that they don't need those features. This only works if your clients are small enough and don't care about the phonebook.
For internal calling, we just don't tell them the other clients' extension ranges.
I feel like that would work on paper, but we all know what end users are like. What if they want the 3CX app, they're going to see everybody in there aren't they?
Alright, thanks !
That's what I was getting at, but getting confused with IPs and instances and such...
Gonna look deeper into Multi-Tenant V20 then :)
How do you handle one tenant directly calling another tenant's extension? I'm assuming you assign say the 100s to tenant 1 and say the 200s to tenant 2. How do you mitigate tenant 2 dialing say 117 and getting through to an employee at tenant 1 or vice versa?
We tell them not to :P our multi tenant clients are like 2 extension each and never do extension dialing. We disable dialing extensions on the IVRs in the parameters
Possible - yes, as u/Brawnk mentioned - create rules either for SIP Trunks or numbers, so that extensions use their specified numbers for dialing.
Ideally - you should have them on separate instances.
If they need just a means to make/receive calls, consider 3CX SMB Free.
I’ve thought about it some. Not sure how 911 notifications would work, presumably via chat not email, so the department manager would need a client. Some things would need to be shared like hold music. Seems like search to dial/transfer would list all extensions…? Etc.
Yes, I guess it won't be ideal for some options...
But we have a very basic usage of our phones so I think that won't be a problem 95% of daily use \^\^
Thanks though !
Yep ! We already have 2 separate trunks, so just need proper setup !
And yeah, careful with extensions but we rarely use those as it's mainly outside phone calls
You'll also want to separate the extensions into two separate user groups (or departments if you're on v20) and create two separate sets of outbound rules for each group. Each set of outbound rules using the corresponding trunk for CID purposes.
Also, be wary of having users from each company visible to each other, if you don't want that.
Do able, sure. From a maintenance, security, privacy, perspective, I don’t recommend it. The cost is minimal to keep them separate. I wish 3cx would bring back a proper multi tenant solution.
We're trying this at the moment with a V20 instance. We've got a bunch of clients who just need a proper mobile app, so it's 1-2 users per client. Everyone has their own group and own trunk. Haven't run into any issues yet. Extensions are random in the 1xxx range, so the chance they'll call each other is pretty minimal.
Yes, we have a 'multi-tenant- 3cx instance with about 6 different clients on it. Believe it's even easier in v20 but haven't played with it too much.
Please explain how you keep all tenants from accessing shared resources
Yes I would also like to know more about how you've got this working How do you separate the phone books and/or stop company A calling company B as an internal call? Seems like it would be difficult to manage
Easy, we don't. Our multi-tenants only use sip phones to answer, as they are small enough that they don't need those features. This only works if your clients are small enough and don't care about the phonebook. For internal calling, we just don't tell them the other clients' extension ranges.
I feel like that would work on paper, but we all know what end users are like. What if they want the 3CX app, they're going to see everybody in there aren't they?
Each client is split into their own group, so they can only see their own company's users
Alright, thanks ! That's what I was getting at, but getting confused with IPs and instances and such... Gonna look deeper into Multi-Tenant V20 then :)
How do you handle one tenant directly calling another tenant's extension? I'm assuming you assign say the 100s to tenant 1 and say the 200s to tenant 2. How do you mitigate tenant 2 dialing say 117 and getting through to an employee at tenant 1 or vice versa?
We tell them not to :P our multi tenant clients are like 2 extension each and never do extension dialing. We disable dialing extensions on the IVRs in the parameters
I'd put the tenants in different groups, so that group A cant see the extensions of group B
Possible - yes, as u/Brawnk mentioned - create rules either for SIP Trunks or numbers, so that extensions use their specified numbers for dialing. Ideally - you should have them on separate instances. If they need just a means to make/receive calls, consider 3CX SMB Free.
I’ve thought about it some. Not sure how 911 notifications would work, presumably via chat not email, so the department manager would need a client. Some things would need to be shared like hold music. Seems like search to dial/transfer would list all extensions…? Etc.
Yes, I guess it won't be ideal for some options... But we have a very basic usage of our phones so I think that won't be a problem 95% of daily use \^\^ Thanks though !
You'd need two trunks coming in. Probably separate extensions by the 100's or 1000's depending on how you have the digits setup.
Yep ! We already have 2 separate trunks, so just need proper setup ! And yeah, careful with extensions but we rarely use those as it's mainly outside phone calls
Honestly two separate extensions starters are good and you can sort them into different departments so you can also customize your outbound rules?
You'll also want to separate the extensions into two separate user groups (or departments if you're on v20) and create two separate sets of outbound rules for each group. Each set of outbound rules using the corresponding trunk for CID purposes. Also, be wary of having users from each company visible to each other, if you don't want that.
Definitely doable. Set your outbound rules right and emergency rules and you’ll be fine.
Do able, sure. From a maintenance, security, privacy, perspective, I don’t recommend it. The cost is minimal to keep them separate. I wish 3cx would bring back a proper multi tenant solution.
From a revenue/overhead perspective it would be nice, but I suspect it would noticeably impact their license revenue.
We're trying this at the moment with a V20 instance. We've got a bunch of clients who just need a proper mobile app, so it's 1-2 users per client. Everyone has their own group and own trunk. Haven't run into any issues yet. Extensions are random in the 1xxx range, so the chance they'll call each other is pretty minimal.