IVG Genesys architecture
Genesys supported integrations
Genesys component requirements are:
- Management Framework 8.1
- IP Tservers (SIP Server) 8.1
- Universal Routing Server (URS) 8.1
Genesys IVG platform
IVG is used in conjunction with On-Premise Callback software and can be integrated with Genesys environments to process incoming calls through to successful callback.
Deployment architecture diagrams
The following figures detail the supported integration models for IVG, On-Premise Callback software, and Genesys.
Standalone Callback deployment and single IVG
This deployment model is composed of the following:
- Standalone On-Premise Callback environment
- Single IVG
- Local PostgreSQL database
- Tomcat local on the IVG
- VIS published to Tomcat
- Call Control Interaction Server (CCIS) (CCXML) published to Tomcat
Standalone Callback deployment and multiple IVG
This deployment model is composed of the following:
- Standalone On-Premise Callback environment
- Multiple IVGs (N+1)
- PostgreSQL local on the first IVG; remote to all other IVGs
- Tomcat local on each IVG
- VIS published to each Tomcat
- Call Control Interaction Server (CCIS) (CCXML) published to each Tomcat
Standalone Callback deployment and multiple IVG with a remote database
This deployment model is composed of the following:
- Standalone On-Premise Callback environment
- Multiple IVGs (N+1)
- PostgreSQL remote from all IVGs
- Tomcat local on each IVG
- VIS published to each Tomcat
- Call Control Interaction Server (CCIS) (CCXML) published to each Tomcat
High availability Callback deployment and multiple IVG
This deployment model is composed of the following:
- High availability On-Premise Callback environment
- Multiple IVGs (N+1)
- PostgreSQL remote from all IVGs
- Tomcat local on each IVG
- VIS published to each Tomcat
- Call Control Interaction Server (CCIS) (CCXML) published to each Tomcat