IVG Avaya architecture

The following diagrams detail the supported integration models for IVG, On-Premise Callback software, and Avaya TSAPI or Avaya CVLAN.

Standalone On-Premise 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

TSAPI

TSAPI architecture diagram

CVLAN

CVLAN architecture diagram

Standalone Callback deployment - Multiple IVG

This deployment model is composed of the following:

  • Standalone On-Premise Callback environment
  • Multi IVG (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

TSAPI

TSAPI architecture diagram

CVLAN

cvlan architecture diagram

Standalone Callback deployment - Multiple IVG - Remote Database

This deployment model is composed of the following:

  • Standalone On-Premise Callback environment
  • Multi IVG (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

TSAPI

tsapi architecture diagram

CVLAN

cvlan architecture diagram

High Availability Callback deployment - Multiple IVG - Standalone Database

This deployment model is composed of the following:

  • High Availability On-Premise Callback environment
  • Multi IVG (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

TSAPI

tsapi architecture diagram

CVLAN

cvlan architecture diagram