SRC 3GPP Gy Peer Communication and Redundancy
The SRC 3GPP Gy configuration enables the definition of multiple Diameter peers to act as OCSes. SRC’s Gy selects one peer to become the active peer, and forwards all CCR messages to it. If the SRC software detects a failure of the active peer, SRC's Gy selects another peer to become the active peer. SRC's Gy does not switch back to the original active peer when it comes back online.
For redundancy purposes, you can configure multiple SRC 3GPP Gys to handle the communication between the same group of SAEs and OCSes. To achieve this redundancy, you configure multiple SRC's Gy instances to point to the same namespace in the shared configuration.
All SRC's Gy instances pointing to the same namespace use a community manager to elect the active member. The active member registers itself with the naming server and is the only member receiving subscriber-tracking events from the SAE and forwarding them to the OCS.
If the active SRC's Gy member fails, the community manager detects the failure and elects another member to become the active member. The new active member registers itself with the naming server thus overwriting the old member’s endpoints. During the failure period, the SAE keeps a fail queue for the SRC 3GPP plug-in and replays the queue to the new active member.