Synchronizing Configurations
You can synchronize the Oracle Communications Session Border Controllers (SBC) in your High Availability (HA) node in the following ways:
- Automatically — Set up configuration checkpointing within the HA node.
- Manually — Check whether or not configurations in the HA node are synchronized, and then copy configuration data from one SBC to the other.
When you initially configure a new HA node, copy the configuration data manually from one SBC to the other. When you complete the process, you can configure your HA node to automatically synchronize configurations.
Oracle recommends that you configure the HA node for configuration checkpointing because that is the most reliable way to ensure that both systems have the same configuration.
Synchronize HA Peers
The process for synchronizing the peers in a High Availability (HA) node for the first time by way of the ACLI includes the following steps.
RTP Timestamp Synchronization
The Oracle Communications Session Border Controller maintains the continuity of egress transcoded media streams during HA switchover by synchronizing the RTP timestamps between active and standby systems.
For a new call, the transcoding resources are allocated and each session is configured with an initial RTP timestamp value. This process is repeated independently on both the active and standby systems to maintain approximately the same timestamps. This minimizes the difference between active and standby-side interpretation of the current RTP timestamp for a new session.
During HA operation, the active system maintains new timers that check for transcoded sessions lasting fifteen minutes or more. The active system re-synchronizes the RTP timestamp after fifteen minutes. This prevents the RTP timestamps from drifting due to clocking differences between active and standby hardware.
In addition, when the standby system boots, it performs a complete session sync with the active system for all currently active sessions.
Using Configuration Checkpointing
The Oracle Communications Session Border Controller’s primary and secondary utility addresses support configuration checkpointing, allowing the standby Oracle Communications Session Border Controller to learn configuration changes from the active Oracle Communications Session Border Controller. This means that you only have to enter configuration changes on the active Oracle Communications Session Border Controller for the configurations across the HA node to be updated.
Configuration checkpointing uses parameters in the network interface and in the Oracle Communications Session Border Controller HA Nodes/redundancy configurations.
If you are using configuration checkpointing, you also need to set up two Oracle Communications Session Border Controller peer configurations: one the primary, and one for the secondary.
HA Configuration Checkpointing
You need to first set applicable network interface configuration parameters, and then establish applicable parameters in the Oracle Communications Session Border Controller HA node (redundancy) configuration.
We recommend that you do not change the configuration checkpointing parameters in the redundancy configuration. Using the defaults, this feature will function as designed.
Note:
Remember to set the appropriate type parameter in the HA node redundancy peers configuration.For the network interface, these parameters appear as they do in the following example when you use the ACLI. This example has been shortened for the sake of brevity.
pri-utility-addr 169.254.1.1
sec-utility-addr 169.254.1.2
For the Oracle Communications Session Border Controller HA node (redundancy) configuration, these parameters appear as they do in the following example when you use the ACLI. This example has been shortened for the sake of brevity. You should not change these values without consultation from Oracle Technical Support or your Oracle Systems Engineer.
cfg-port 1987
cfg-max-trans 10000
cfg-sync-start-time 5000
cfg-sync-comp-time 1000
To configure HA configuration checkpointing in the ACLI:
Manually Checking Configuration Synchronization
You can check that the current and active configurations are synchronized across the HA node. The current configuration is the one with which you are currently working, and the active configuration is the one active on the system.
To confirm that the systems in the HA node have synchronized configurations: