This page was last edited on October 2, 2019, at 19:20.
Comments or questions about this documentation? Contact us for support!
The high availability model for the Recording Client Function is essentially the same as the high availability model for Genesys SIP Server and Genesys Media Server.
SIP Server can be deployed in an active/hot-standby pair; whenever the primary instance fails, the hot-standby instance will take over and will have knowledge of all established sessions. If a recording session has been established with a recording server, a failure of SIP Server will not affect the operation of the communication and the recording session.
Resource Manager is a SIP Proxy that can operate in either active/hot-standby or active/active pair. When there is a failure at the Resource Manager, the remaining instance of Resource Manager will become active and continue to accept incoming requests. The remaining instance will remember the affinity of the recording sessions with Media Server as well as the recording server. The failure should be transparent to SIP Server, Media Server, and the recording server function.
When the media is bridged through Media Server, Media Server becomes a single point of failure for the duration of the communication session. If Media Server fails, Resource Manager notifies SIP Server about the failure so that SIP Server can take alternative action on the call. SIP Server should re-establish the recording session by joining the endpoints to another available Media Server. When the endpoints are joined to the now-active Media Server, Media Server will establish a new recording session with the same parameters to the recording server function.
The total amount of recorded media lost is the sum of time for Resource Manager to detect MS1 failure plus the amount of time to failover the recording session to another Media Server instance.
Handling high availability of the Recording Server Function is the responsibility of the third party recorder. The following are typical ways to manage failover of a component in Recording Server Function, and Genesys does not restrict how third party manages high availability of Recording Server Function.
Failure of a call recorder:
Failure of a T-lib client:
To protect against any loss of recorded media in the case of a failure in the recording server function, the recorder has the option of duplicating the recording by establishing two independent recording sessions. The following steps outline the mechanism of duplication:
Note: Media Server is still a single point of failure since RTP media is still pinned through a single instance of Media Server. This duplication only protects against the failure of SIP Server, failure of Resource Manager, and failure of recording server.