3cx Deployment for 300 plus user

[mnl_hash]

Hi ,

I have done 3cx deployment on a smaller scale where i have required 16 SIM calls, for approx. 20 users as that company needed call centre functionality as well.
However i am working on a project where we would need to migrate 500 plus users to 3cx. These users are spread among multiple locations within Canada.
The biggest two teams will have approximately 150 users each. I will be looking into deployment of 3cx Enterprise or Pro Edition. Since other locations will have anywhere from 5 to 50 or 60 users. I wanted to know your thoughts on deployment.

1. The best case would be to use one system and create Different Groups for different teams and Locations. So that management can have oversight on all users. I am thinking since all teams will be in different groups, Main Admin will be assigned as managers of all groups. Team managers will be assigned as managers of their specific teams. In this way head office will be able to see call recordings and other oversight over the rest of the teams. I would need to create call ques and use multiple IVRs, they will need to use it as a call centre as well. I am thinking of doing it like this as company wide extensions can be granted and employees will be able to communicate internally using company wide extensions. Call quality is very important and we dont want to ever reach capacity weather its incoming or outgoing calls. We would also need call recordings saved for the longest time possible. Is the self hosted 3cx server big enough to handle this many users without lag, poor call quality or dropped calls?

2. Second approach which can be taken is to create separate systems for different teams. If we take this approach, is there a way to use internal extensions dialling across different 3cx systems? Is there a way to have head office oversight ?

3. How many channels are needed per user to ensure we never max out, for a high call volume company?


Also there might be many other things which i need to consider , since i dont have much experience with deployment on this large scale , i would appreciate if you guys can help out and guide.

Thanks

 

[Evolute IT]

1. You can give management access to the console to manage extensions in their own group/location. Otherwise, U6/U7 will bring more powerful groups to allow better segmentation.

2. Yes, you can dial between systems when using bridges. You control the prefix and routing so you can go either direct dial or prefix dial.

3. Depends on their call volume. Rule of thumb is 3 users per SC, so 100SC for 300 users (I'd go 96 or 128.)

 

[mnl_hash]

Hi

Thanks for some guidance
1 what is U6/U7
2. Where can I find info on bridges
3. Thanks

Thanks for advise

 

[Evolute IT]

U6/U7 are future updates down the road. We are currently on Update 5 (v18.)

As for bridges, right here: https://www.3cx.com/docs/manual/connecting-pbx-bridges/

 

[mnl_hash]

Any other suggestions for this kind of deployment?
Would i need sbc installed for each site using hard phones?

 

[SteveITS]

Are they on different networks or all the same network? An SBC generally makes life way easier because the phones auto-detect and show up in 3CX. Otherwise any off-site phone needs to use STUN with forwarded ports.

Is the self hosted 3cx server big enough to handle this many users without lag, poor call quality or dropped calls?

https://www.3cx.com/docs/recommended-hardware-specifications-for-3cx/

 

[vectra]

I have around 400+ users on nine locations running on single instance in azure. All branches connected over IPsec vpn with VM in azure so phones deployed same as they are on LAN. Another deployment 300+ users hosted on google VM and all phones using STUN. If you have decent Firewall no need to setup forwarding rules. Every phone should have unique SIP port and range of RTP ports. In your case I will deploy 48 call instance per each bigger group (150 users) and 64 instance for rest. Each office can start with 1000, 2000, 3000 range for extensions then you can bridge PBX so you don't need to add prefix to call second branch.