| Line 1: | Line 1: | ||
=Smart Failover= | =Smart Failover= | ||
| − | Until Voice Microservices are available, | + | Until Voice Microservices are available, Workspace 9 needs to be deployed. For more information about setting up Workspace on your system see [[Documentation:HTCC:IWWDep:SettingUpSystem#DisasterRecovery|Setting up Smart Failover]]. |
<font color="#B24DE7"> '''Olena's comment''': New page for GAPI-23129 [DOC] [DEP] Smart failover for premise deployment. <br> | <font color="#B24DE7"> '''Olena's comment''': New page for GAPI-23129 [DOC] [DEP] Smart failover for premise deployment. <br> | ||
| Line 9: | Line 9: | ||
==Failover Scenarios== | ==Failover Scenarios== | ||
===Voice Channel=== | ===Voice Channel=== | ||
| − | If the SIP Phone loses connection to the SIP Servers in one data center, | + | If the SIP Phone loses connection to the SIP Servers in one data center, it re-connects to the SIP Servers in the other data center, based on SIP/dual registration protocol. Existing voice calls might be lost. |
| − | GWS has a voice component that monitors the local SIP Server session. It will drop when the SIP Server goes down. This will sever its cometd connection back to the WWE application in the agent's browser, | + | GWS has a voice component that monitors the local SIP Server session. It will drop when the SIP Server goes down. This will sever its cometd connection back to the WWE application in the agent's browser, signaling to it that there is a problem with the voice connection. |
===Workspace=== | ===Workspace=== | ||
| − | + | Workspace triggers a disaster recovery failover to another site based on the following triggers: | |
* DN unregistration (DNStateChanged Inactive event received) | * DN unregistration (DNStateChanged Inactive event received) | ||
* Voice channel unavailability (ServiceStateChanged UNAVAILABLE event received) | * Voice channel unavailability (ServiceStateChanged UNAVAILABLE event received) | ||
| Line 22: | Line 22: | ||
* Registration failure for WebRTC | * Registration failure for WebRTC | ||
| − | The | + | The Workspace application needs to authenticate in order to login to the backup site. The Single Sign-On (SSO) integration is automatically login to the backup site without requiring the agent to enter a password. |
===Data Center=== | ===Data Center=== | ||
Revision as of 15:56, March 8, 2021
Contents
Smart Failover
Until Voice Microservices are available, Workspace 9 needs to be deployed. For more information about setting up Workspace on your system see Setting up Smart Failover.
Olena's comment: New page for GAPI-23129 [DOC] [DEP] Smart failover for premise deployment.
Source https://intranet.genesys.com/pages/viewpage.action?spaceKey=RDA&title=Premise+SIP+BC+and+WWE+9+Smart+Failover
Failover Scenarios
Voice Channel
If the SIP Phone loses connection to the SIP Servers in one data center, it re-connects to the SIP Servers in the other data center, based on SIP/dual registration protocol. Existing voice calls might be lost.
GWS has a voice component that monitors the local SIP Server session. It will drop when the SIP Server goes down. This will sever its cometd connection back to the WWE application in the agent's browser, signaling to it that there is a problem with the voice connection.
Workspace
Workspace triggers a disaster recovery failover to another site based on the following triggers:
- DN unregistration (DNStateChanged Inactive event received)
- Voice channel unavailability (ServiceStateChanged UNAVAILABLE event received)
- CometD real-time channel loss
- Workspace initialization issues at login
- Registration failure for Softphone
- Registration failure for WebRTC
The Workspace application needs to authenticate in order to login to the backup site. The Single Sign-On (SSO) integration is automatically login to the backup site without requiring the agent to enter a password.
Data Center
If the entire data center fails, both the voice channel and the WWE application will fail. This impacts both CometD connections to the WWE client, forcing it to reconnect to the backup site. The SIP endpoint also switches over to its SIP BC (as described above).