As PBX's are considered critical to the operation of almost all business...I suggest a way to enable 3CX to be run in duplicate, with automatic
...more »
As PBX's are considered critical to the operation of almost all business...I suggest a way to enable 3CX to be run in duplicate, with automatic switch over in the case of failure.
I see it working something like this...
On existing 3CX PC, add a second Ethernet card card, perhaps even require it be a 1000 base T. Obtain a second PC with two Ethernet cards.
Off-line, set up the second PC to duplicate the IP settings of the existing machine, install the base version of 3CX.
At this point you would download and install a 3CX Redundancy Package on the existing machine. It would ask you to select either Master or Slave, select Slave and designate the second NIC as the communication link to the other PC, using a roll-over cable
On the new machine, install the Redundancy Package, but this time select Master and again the NIC to use for inter-machine communication. After installation it would instruct you to plug in the Ethernet cable between the two machines. The Slave machine would detect this and ask if you wanted to transfer all 3CX settings/Voicemail messages, etc. to the Master machine.
This action would not only duplicate the existing machine but also send your 3CX licence code as well.
When that transfer was complete and everything verified, the Slave machine would ask if you wanted to switch operation to the Master. If you answer yes, it would instruct you to plug in the network connection to the master machine and once that was confirmed, initiate a a full network firewall on the Slave machine isolating it from the network so there would only be one instance of the 3CX server IP.
At this point the Master PC would be running 3CX. Any changes, updates, voicemails,time of day, line and trunk status etc. would be passed on to the Slave to keep it up to date. System status/keep alives would also let the Slave know that the Master was operating properly. If any problems were detected, or there was loss of communication, the firewall would drop on the Slave machine and the Slave would attempt to initiate a firewall in the Master PC or shut it down/put it to sleep. An email would also be sent alerting of the switch over.
3CX could continue to operate on the Slave for as long as needed.
If, when operating on the Master, the Slave unit failed, an email would be sent out and the Master would continue to operate for several days or a week, this would prevent someone from using this to operate two independent systems on the same licence.
Once the Master unit was back in operation, it would be switched back a manner similar to the initial installation. If a simple reboot was required, then obviously the 3CX installation would not be necessary and only the current status would have to be transferred, automatically.
Anyway, just an idea...
« less
full details »
Social Web