...
You have an existing PBX system that will be your Primary server.
You have an identical PBX system that will be your Secondary server.
The two servers can communicate on an IP level.
Both systems are configured with their own IP addresses.
Both the systems IP network, can be a local network or can be on separate geographically location.
SSH and HTTP(s) ports should be open between both the servers.
Both servers are running the Advanced Recovery module, and it is "licensed" on each system.
Backup & Restore , API and Filestore are dependent modules that must be installed on both the systems.
ICMP/Ping between Primary and Secondary is required.
...
We need to establish SSH connection between both the servers.
Please find below instructions refer to Setting up the SSH key to copy primary server SSH key to secondary so that we can easily SSH to secondary server from primary without needing password.
Login to your Primary server with an SSH client such as PuTTy, SecureCRT, or other SSH client.
At the primary server Linux CLI prompt type: sudo -u asterisk ssh-copy-id -i /home/asterisk/.ssh/id_rsa.pub root@SecondaryServerIP and enter the password when prompted.
| Info |
|---|
Make sure you replace the SecondaryServerIP with the IP Address of your Secondary PBX. (use IP and not a hostname that may be common to both primary and warmspare; if fqdns are desired create 3 records the common name , specific name for primary and specific name for warm spare - ie mypbx.company.com , mypbx1.company.com , mypbx2.company.com) If the Firewall is configured, pay attention to creating the right rule allowing the two servers to talk to each other. |
3. If above command completes without error, you are ready to test:
At the prompt type: ssh -i /home/asterisk/.ssh/id_rsa root@SecondaryServerIP
If all went well, you should now be logged in to the Secondary server.
...
PBX 17+ Improvements :
Redirect option to Backup & Restore module :
Added new option “+Go to Backup & Add Key” into Advanced recovery → Global settings” which will redirect to backup module > Global Settings to copy this pbx key or add another pbx key.
...
Verify SSH Connectivity -
| Note |
|---|
On a fresh system, this one time step is mandatory for PBX 17+ system. ‘precheck’ command should be run on both the servers. |
Check SSH Connection from Primary Server:
SSH into the primary server.
Run the following command, replacing
SecondaryIPwith the secondary server's IP address: fwconsole advr --precheck SecondaryIPIf the command is successful, it should display “SSH Connectivity is Good”.
Screen-shot attached below
...
Check SSH Connection from Secondary Server:
SSH into the secondary server.
Run the following command, replacing
PrimaryIPwith the primary server's IP address: fwconsole advr --precheck PrimaryIPIf the command is successful, it should display “SSH Connectivity is Good”.
| Info |
|---|
SSH Folder permissions In the case that the web GUI show errors during the SSH connection, worth checking the correct permissions are set for the SSH folder and the files it contains. The permissions should look something like: /home/asterisk/.ssh |
...
| Info |
|---|
The above files must exist in both servers (primary and secondary). Any discrepancy with the permissions in any of the files, please re-do SSH association step N°2stated above. |
Install Advanced Recovery module
...
Notification Extension: which extension to call during failover event. On system failure event, active system will initiate call to configured extension and will play the configured announcement. Intention of this call notification is to update admin about the system failure
Recording when primary fails : select recording to play when the Primary server fails. This will specify the list of "recordings" to choose from as configured in System Recording module.
Recording when standby fails: select recording to play when the standby/Warm Spare server fails. This will specify the list of "recordings" to choose from as configured in System Recording module.
Notification Email: email address where notifications will be sent to.
...
This will finish the "Quick configuration" part of Advanced Recovery module. If any further modifications of the configuration are needed then please refer to Advanced Recovery Expert Configuration wiki.
We need to start "Advanced Recovery Service" daemon as soon as we done with "Quick configuration" process as described in below section.
...
Once Quick configuration wizard is over then any further configuration or change must be done on the 'Advanced Configuration' page. Changes like changing GraphQL API tokens, modifying the Primary/Secondary server IP address, etc. we will need to use "Advanced configuration" as mentioned in Advanced Recovery Expert Configuration
Switchover
Advanced Recovery module decides Primary is down by detecting at least one of the following conditions:
...
Advanced recovery module has an option to regenerate the configuration of already connected/configured Sangoma's S and D series phones via Endpoint Manager.
"Advanced Recovery → Endpoint → Regenerate EPM config for S and D series phones"
...
Sangoma S and D series phones support the configuration of a "Failover" IP along with the Primary IP.
The Endpoint Manager module, which is "Free" to use for Sangoma's S and D series phones, can be used to help configure this setup.
...