- Joined
- Aug 11, 2014
- Messages
- 24
- Reaction score
- 1
Hi, we have installed a V18 3cx system on a windows machine that is on a site that is a 100 mile round trip to get to/from.
In case their machine goes down we want to have a "standby" system ready at our office that we can link to site in an emergency via VPN whilst we get to deal with the main machine. This machine would be preconfigured with a backup from the main site.
The standby machine would only be booted up if their machine on site is not serviceable remotely and we need to physically attend site. Basically it gives us some breathing space on the service call.
We have done this is in the past on another site with an earlier version (V14 IIRC) before they went cloud based, and that was quite easy to do back then.
Is this viable with V18 system too? Is it easy to swap licence validation between the machines as required?
The system on site is connected to the outside world using an ISDN30 interface rather than an external sip trunk, , and there are no remote or App users, if that makes any difference.
In case their machine goes down we want to have a "standby" system ready at our office that we can link to site in an emergency via VPN whilst we get to deal with the main machine. This machine would be preconfigured with a backup from the main site.
The standby machine would only be booted up if their machine on site is not serviceable remotely and we need to physically attend site. Basically it gives us some breathing space on the service call.
We have done this is in the past on another site with an earlier version (V14 IIRC) before they went cloud based, and that was quite easy to do back then.
Is this viable with V18 system too? Is it easy to swap licence validation between the machines as required?
The system on site is connected to the outside world using an ISDN30 interface rather than an external sip trunk, , and there are no remote or App users, if that makes any difference.