3CX Phone System Multitenant ** COMING SOON

[asfuture]

is anybody there with experience about this?? is multitenant suportted by 3CX???

 

[simonb]

Re: mutitenant

Hi Archie

All you really need is a barring matrix to stop company A calling company B equally if you have comapny A on numbers 100 to 199 and B on 200 -299 as long as they dial out on there own sips trunks you have a multi tennant switch

Just dont tell A they can ring B

 

[leejor]

Re: mutitenant

Sets with an internal dialplan, set to block (permit) certain extensions/numbers, would prevent "miss-dials" from going to someone/somewhere, it shouldn't. Just don't plan on having more than one operator.

 

[sigma1]

Re: mutitenant

Multitenant is not such a smart idea anyway. You will rely on a shared host (BAD). Hosted/dedicated is a far smarter way to go.

Also, your DSL goes down... Well, you have forwarding rules for UNREGISTERED, that could be your cell phone, built in, real time backup.

Hosted is the way to go especially managed hosted with a company that supplies you with the router and can control QOS end-end. Popping a 3CX server on a open public IP address and then having you play with phones, flaky stun service is a poor choice. We saw the need and we filled that gap.

 

[eagle2]

Re: mutitenant

The only features required are:
• trunk line group
• operator per extension / trunk group
This is enough to fulfill most of multi-tenant requirements.

Also, this functionality is standard for most PBXs.

Regards

 

[SY]

Re: mutitenant

"hostel"=multitenant (everyone is too close to neighbor and it is possible to ask for the help at any time, but neighbors may be annoying. The "commandant" is required. It will resolve issues.)
"private house"=standalone installation (everyone resolves problems alone, but neighbor never bothers. Everyone chooses neighbors to share information and to get help)

Optimal solution is somewhere in the middle... "tenement-house" and ability to choose/build it.

• trunk line group

outbound/inbound rules already cover this requirement.

• operator per extension / trunk group

This requirement is not clear. What does it mean? What is the "operator" and how does "operator" appear in call scenarios?

 

[KerryG]

Re: mutitenant

Today there is only one default operator extension for the entire system. Ideally this could be set via the IVR menu the caller hit or via the trunk itself.

 

[eagle2]

Re: mutitenant

• trunk line group

outbound/inbound rules already cover this requirement.

• operator per extension / trunk group

This requirement is not clear. What does it mean? What is the "operator" and how does "operator" appear in call scenarios?

Stepan,

what I meant is having trunk line groups like you already having extension groups.
In outbound rules you may specify the extension group(s) which may use the trunk line.

Having trunk groups you may group different lines into group for different purposes, one is tenant usage.
Extension group may be regarded already as tenant, you need this for trunk lines also.
What is necessary is to have a separate operator for each tenant, so to solve exception cases.

This would be enough to achieve "multi-tenant" operation which is available for example in Panasonic PBXs and others, which will solve almost all multi-tenant requests, except unique extension numbers. Extension groups and trunk groups must be assigned to specific tenant. The rest of extenions / extension groups and lines / trunk groups are not accessible / visible for the rest of the tenants.


The other benefit from trunk groups is load-balancing line usage (especially important in case of available free minutes from operators, etc.). or other reasons, especially with analog lines and single SIP accounts.

Kind regards,
Orlin.

 

[nb]

Re: mutitenant - Coming Soon!!!!!

Who is interested to try the new version of 3CX Phone System Multitenant 10?

Let me know - [email protected]

We are nearly finished with this.

Just to let you know this will be available only on X64 Architecture computers with OS type

Server 2008
Server 2008 R2
Windows 7 SP1

Thanks

 

[eagle2]

We are definitely interested.

Regards
Orlin.

 

[andrewbucklin]

Very excited to hear about the multitenant support that Service Pack 4 to 3CX version 10 offers!

http: //www.3cx.com/blog/support/installing-3cx-phone-system-multi-tenant/ - NO LONGER AVAILABLE
http: //www.3cx.com/blog/support/general-information-on-3cx-phone-system-multi-tenant/ - NO LONGER AVAILABLE

 

[netswork]

We host systems now. The customer connects to us via VPN or dedicated circuit. We maintain a private MPLS network for this purpose.

We are also the network provider and install firewalls with QOS settings for voice. We have had no issues, but the multi-tenant will be nice. Less servers.