Multiple 3cx servers

[mendel]

HI,
We have a client who has 3 locations, We have a PBX server at one site and would like to have one at each location and that they should all be able to communicate with each other.Meaning they should all be able to call from one site to the other and transfer calls etc.

So I know that we can do a bridge but from what I know thats between two systems.

What solution is there for 3 systems.

Thanks

 

[Evolute IT]

You can still do bridges. Simply create 2 masters on one, and a slave on each other systems. You'll probably also want a bridge master/slave between the two others themselves, this way you have a full hub&spoke + mesh connection.

 

[mendel]

Thank You!!

 

[PMadmin]

I have a similar situation. We have our Headquarters with 2 Master Tunnels; one slave to North and one slave to West. Headquarters can see users at both places and both places can see users at Headquarters.

I set up a Master/Slave from West to North so they can see each other. The problem is, North can see West users, but West can't see North users, although dialing the extensions does work fine. I've checked my ports, All the Presence settings seem to be correct, I'm at a loss.

 

[VoIPTools]

There are several reasons for keeping each location on a separate instance of 3CX. Some of those reasons could include:

• Redundancy -- if one phone system goes down, the other locations are unaffected
• Internet quality -- Frequently rural locations may have poor internet service and may need to use analog/PRI connections
• Business functions -- they may be completely different businesses that only need to talk to each other rarely
• On hold music -- need different on-hold music for each location (besides queue hold music)
• Geographic location -- You could have one business unit in the USA and another in India (like us) Where to put the PBX?

But there are some VERY good reasons for consolidating the sites into one shared PBX

• A cloud hosted instance (AWS, Azure, Google, etc.) typically has far better infrastructure redundancy
• You can have a shared company directory
• Far less complicated configuration
• Much better utilization of shared simultaneous call paths (rather than over-building multiple 3CX to handle peak loads)
• Easier inter-site communication
• Better pricing of SIP services because of shared minutes
• Centralized administration, installation, configuration, updates, etc.

I remember the days when VoIP could only be used in the internal network and a PRI or analog was used to actually talk outside your office network because the available internet connections were too slow. Today, 99.9% of all phone systems automatically have a dependency on a good internet connection because we all use SIP trunks. So there is, in my view, very few reasons for not consolidating multiple locations into one PBX.

To be clear, I'm not suggesting a multi-tenant shared PBX where the users work for completely different business. That's coming in the near future, but for now, if all parties work in the same business, or are reasonably expected to talk to people in multiple locations, I feel a shared PBX is the way to go.

 

[SweetAction]

I have a similar situation. We have our Headquarters with 2 Master Tunnels; one slave to North and one slave to West. Headquarters can see users at both places and both places can see users at Headquarters.

I set up a Master/Slave from West to North so they can see each other. The problem is, North can see West users, but West can't see North users, although dialing the extensions does work fine. I've checked my ports, All the Presence settings seem to be correct, I'm at a loss.

Easy first test... From the PBX not getting presence information, can you visit the management console of the PBX sending the information in a browser without an issue? Does the SSL cert on the sending PBX have the full chain?

 

[PMadmin]

Maybe this is the problem? That is the North pbx. It can read the West users but not the other way around. West is up to date.

 

[Charles_3CX]

View attachment 37844
Maybe this is the problem? That is the North pbx. It can read the West users but not the other way around. West is up to date.

Here, you need to ensure that all systems are on the same version and that they are on the latest.