Brekeke Heartbeat Remote Access Setup
With remote access, you can monitor multiple primary servers' SIP or network status from the same remote Brekeke server at the same time. When this remote server detects one of monitored primary servers is down or no SIP response, actions can be initiated to a secondary(backup) server from this remote server.
SETUP ON THE PRIMARY SERVER
Depend on your need, set up necessary heartbeat and actions on primary server.
If redundacy is needed, check primary server setup in Brekeke SIP Server or PBX redundancy documents and wiki pages for Brekeke SIP server [Mirroing] and/or Brekeke pbx [Auto Sync] setup.
SETUP ON THE SECONDARY SERVER
- If redundancy is needed, check secondary server setup in Brekeke SIP Server or PBX redundancy documents and wiki pages for Brekeke SIP server [Mirroing] and/or Brekeke pbx [Auto Sync] setup.
- At secondary server [SIP Server]>[heartbeat]>[Remote Access]>[IP Address Pattern], set remote server IP pattern in regular expression format, like 192.168.*
No heartbeat or actions are needed on secondary server, which will be set up on the remote server
- Save the remote access setting on secondary server. No restart is needed.
SETUP ON THE REMOTE SERVER
- According to your needs, on remote Brekeke server>[SIP Server]>[Configuration]>[Heartbeat], set up the heartbeat and actions which will monitor primary server status and do the actions on the secondary server
- At [Remote URL] in each action, set secondary server URL as below, donot add http://
- for Brekeke PBX: secondary_server_IP:port/pbx/gate
- for Brekeke SIP Server: secondary_server_IP:port/proxy/gate
- Start heartbeat on remote server