1. Brekeke Product Name and Version: Brekeke SIP Server, Version 3.8.3.4, Advanced
2. Java version: 1.8.0_161
3. OS type and the version: Windows Server 2012 R2 Standard
4. UA (phone), gateway or other hardware/software involved: Responder 5 Direct Connect Integration to CUCM. 2 BSSs for Redundancy.
5. Your problem:
Hello. I am trying a 2 BSS redundancy setup for the first time, and I have a few questions:
1. When setting the Heartbeat on the Secondary server, I understand the Action needed in the Brekeke Admin, setting the VIP to the Interface name.
My question is, is there anything else that needs to be done at the OS level for this to occur, or does this rule actually add the VIP to the OS on the secondary server?
2. This integration uses SIP trunking, from CUCM SIP trunk pointed to VIP set at the OS level on the Primary BSS. Question: Is it possible to monitor connection to CUCM, and have an action to failover if the CUCM is showing offline?
3. The CUCM rep is telling me that he is setting up one SIP trunk from the CUCM node, pointed to the VIP. Is this typical, or would you typically see 2 SIP trunks setup? Both pointing to the VIP, but originating from distinct CUCMs. I would think that 2 would be better, if we can monitor connection to CUCM, to failover to distinct new CUCM IP if the original is showing offline.
Thanks in advance for any help.
-Tom
2. Java version: 1.8.0_161
3. OS type and the version: Windows Server 2012 R2 Standard
4. UA (phone), gateway or other hardware/software involved: Responder 5 Direct Connect Integration to CUCM. 2 BSSs for Redundancy.
5. Your problem:
Hello. I am trying a 2 BSS redundancy setup for the first time, and I have a few questions:
1. When setting the Heartbeat on the Secondary server, I understand the Action needed in the Brekeke Admin, setting the VIP to the Interface name.
My question is, is there anything else that needs to be done at the OS level for this to occur, or does this rule actually add the VIP to the OS on the secondary server?
2. This integration uses SIP trunking, from CUCM SIP trunk pointed to VIP set at the OS level on the Primary BSS. Question: Is it possible to monitor connection to CUCM, and have an action to failover if the CUCM is showing offline?
3. The CUCM rep is telling me that he is setting up one SIP trunk from the CUCM node, pointed to the VIP. Is this typical, or would you typically see 2 SIP trunks setup? Both pointing to the VIP, but originating from distinct CUCMs. I would think that 2 would be better, if we can monitor connection to CUCM, to failover to distinct new CUCM IP if the original is showing offline.
Thanks in advance for any help.
-Tom