(13.3) Solution Architecture
- Ammara Ammara Bokhari
- Navira Zainab
Integration with UCCX
On the backend, the application synchronizes all the changes with UCCX directly over the CCX REST APIs.
The following diagram shows the links of communication between the application and the CCX server.
Integration with UCCX
The direct integration approach saves all changes made through the application configuration interface to the CCX server directly. However, it doesn’t store the changes in the following scenarios:
When UCCX is unreachable
In a UCCX cluster, when any of the UCCX is down and CCX is in a read-only mode
Both of the UCCX cluster nodes are down
On the script level, the UCCX IVR script integrates with Supervisor Tools over the REST APIs to load:
Announcement information
Business calendars on/off settings
Caller profile
The script handles client-side failover of Supervisor Tools and automatically requests to the secondary application server when the primary instance in inaccessible.
UCCX Failover Cluster Support
The Web App connects to Cisco UCCX API Server for reading and writing data to UCCX.
To detect failover, it continuously monitors the API Server state. In the event of connection failure to the primary UCCX API server, it connects to the secondary API Server to read data from UCCX.