Running 950 endpoints on a single server can work. However, if it’s mission critical then I would anyway split it in multiple servers.
The 3 servers shouldn’t be HA, since it’ll just replicate. I’d do extensions 100-399 on Server-A, 400-699 on Server-B 700-999 on Server-C and then use internal trunks to interconnect them.
Then our Carreer plus offers us only 250 extensions, so if we want more, do we need a new VitXi licence (that we didnt find on the web site VitalPBX Add-Ons Modules | VitalPBX - Advanced PBX System) or we will be obliged to buy a new Carreer Plus Licence?
Then what should be the function of the trunk that will interconnect them instead of let each server work independently?
You will need to set the patterns on the outbound routes to match the extension range of the other servers and match to correct trunk. You will also need to enable Intra-Company.
For example, on PBX-A you would need 2 outbound routes:
Name: Route to PBX-B Pattern: [4-6]XX Trunk: PBX-B
Name: Route to PBX-C Pattern: [7-9]XX Trunk: PBX-C
Hello dear @miguel , thanks for the clarification.
We are able to get a bigger server with like 64GB RAM minimum and 2Terra SSD
But last question to clarify is, as it seams like the Career Plus Licence allows only 250 VitXi Clients, what should we do then if we get bigger server that can supports 500+ Clients?
I’d be very interested on whether that specification or similar can take that amount of VitXi clients. Concurrent calls you can use the concurrent call script to test the specification.