1. Brekeke Product Name and Version: 3.8.5.2/493-3
2. Java version: 10.0.1
3. OS type and the version: Linux CentOS 7.5.1804 (Core)
4. UA (phone), gateway or other hardware/software involved: Asterisk
5. Your problem:
If the Primary server dies, the heartbeat on the secondary will fail and the secondary will take over. Is there any way to set up a heartbeat on the secondary that would ever be able to monitor for when the Primary comes back online and would try to set everything back to the Primary server automatically?
Heartbeat question
Moderator: Brekeke Support Team
-
- Posts: 31
- Joined: Wed Oct 17, 2018 2:21 pm
That is disappointing, since dialplan is listed under "FAILOVER / LOAD-BALANCE METHODS" for the Advanced Edition: http://www.brekeke.com/sip/feature-list.php
Not much of a failover "feature" if the dialplan rules have to be manually synchronized.
Since it will not be available until the next release, when is 3.9 going to be available?
Not much of a failover "feature" if the dialplan rules have to be manually synchronized.
Since it will not be available until the next release, when is 3.9 going to be available?
> That is disappointing, since dialplan is listed under "FAILOVER / LOAD-BALANCE METHODS" for the Advanced Edition: http://www.brekeke.com/sip/feature-list.php
It means "Failover in the Dial Plan" not syncing DialPlan definitions.
Please refer to the following wiki topic.
http://wiki.brekeke.com/wiki/How-to-mak ... -Dial-Plan
We will not add the auto sync for DialPlan because required DialPlan rules are different at both Primary and Secondary.
> when is 3.9 going to be available?
It will be beta in the next month.
It means "Failover in the Dial Plan" not syncing DialPlan definitions.
Please refer to the following wiki topic.
http://wiki.brekeke.com/wiki/How-to-mak ... -Dial-Plan
We will not add the auto sync for DialPlan because required DialPlan rules are different at both Primary and Secondary.
> when is 3.9 going to be available?
It will be beta in the next month.