- Joined
- Sep 13, 2018
- Messages
- 1
- Reaction score
- 0
I would like to confirm the feasibility and best-practice configuration for a planned failover deployment using 3CX.
Current and Planned Setup
Main Office (Primary 3CX Server)
Current and Planned Setup
Main Office (Primary 3CX Server)
- Existing SIP Trunk from MPT: 14 DIDs / 80 concurrent calls (direct cable connection)
- Plan to add a new SIP Trunk from MPT (direct cable connection)
- Both SIP trunks will operate simultaneously during normal operation.
- The Secondary 3CX Server will be relocated to the Branch Office.
- Main Office and Branch Office are connected via local LAN routing.
- The new SIP trunk will also be directly connected at the Branch Office.
- This SIP trunk should be used by the Secondary 3CX Server during failover.
- During normal operation, the Primary 3CX Server should use both SIP trunks.
- When the Primary Server becomes unavailable, the Secondary Server should automatically take over and operate using the new SIP trunk located at the Branch Office.
- Existing MPT SIP Trunk (Main Office): 14 DID / 80 concurrent calls
- New MPT SIP Trunk (Branch Office): 1 DID / 10 concurrent calls
- Is this failover with different SIP trunk using design supported by 3CX?
- (How SIP trunk work? It's working look like backup trunk?Does a SIP trunk automatically function as a backup trunk, or does it require specific configuration to provide failover?)
- Could you please provide best-practice guidance for configuring this scenario?