Cisco Cisco Unified Customer Voice Portal 11.0(1)
Note:
• The Reporting Service and the Database are separated for functional clarity. Together they
comprise the Reporting Server.
• The connection of the Operations Console to the Call Server, through an OAMP Resource
Manager (ORM) is simply indicative. An ORM is co-located with each managed Unified
CVP component, and the Operations Console is connected to each component. The ORM is
invisible to the end-user.
CVP component, and the Operations Console is connected to each component. The ORM is
invisible to the end-user.
Figure 1: CVP Architecture
A Call Server is a physical machine on which resides, for example, the IVR Service, the SIP
Service, and the ICM Service. The Call Server uses a central messaging bus to allow each service
to communicate. The Reporting Service connects to the message bus either through an in-process
plug-in or an out-of-process plug-in depending on whether the Reporting Service resides in the
same JVM with the message bus system. It listens to all the messages passing through the
message bus and captures call-state change messages sent from SIP or IVR services or reporting
messages from a VXML Server.
Service, and the ICM Service. The Call Server uses a central messaging bus to allow each service
to communicate. The Reporting Service connects to the message bus either through an in-process
plug-in or an out-of-process plug-in depending on whether the Reporting Service resides in the
same JVM with the message bus system. It listens to all the messages passing through the
message bus and captures call-state change messages sent from SIP or IVR services or reporting
messages from a VXML Server.
The Reporting Service then parses those messages and converts them into batches of appropriate
SQL statements and executes them into a SQL database using the Java Database Connectivity
(JDBC) API. The Reporting Service can also receive and process Unified CVP admin messages
to perform Unified CVP system administrative tasks, such as turning on or off debugging,
querying statistics, and so forth. As the diagram shows, the Reporting Service can be shared by
multiple Call Servers that belong to the same Unified CVP deployment.
SQL statements and executes them into a SQL database using the Java Database Connectivity
(JDBC) API. The Reporting Service can also receive and process Unified CVP admin messages
to perform Unified CVP system administrative tasks, such as turning on or off debugging,
querying statistics, and so forth. As the diagram shows, the Reporting Service can be shared by
multiple Call Servers that belong to the same Unified CVP deployment.
Note:
There only needs to be one Reporting Server in a deployment. During temporary database
outages, messages are buffered to file and inserted into the database when the database comes
back on-line. The amount of time that messages can be buffered depends on the system
throughput.
back on-line. The amount of time that messages can be buffered depends on the system
throughput.
If more than one Reporting Server is used, be aware that:
• Each Call Server and each VXML Server can be associated with only one Reporting Server
• Reports cannot span multiple Informix databases
Reporting Guide for Cisco Unified Customer Voice Portal Release 7.0(2)
6
Chapter 1: Introduction to the Reporting Server
How the Reporting Server Functions