The ARGOS IVR can provide data to callers from two (generic) sources, an interactive mainframe transaction or, a local database on the Application Processor.
The satisfaction of a caller into an IVR system, depends on the quality and timeliness of the data that is available and on the speedy response to an IVR inquiry. You may not want your callers to hear "Please wait .... while we access your account information ..."
In the world of IVRs, data may have to be obtained from
many sources. The ARGOS IVR architecture is designed to be "open" with regard to
data sources, whether they be batch or interactive, TCP/IP or SNA, or any number of custom
protocols that don't fit these molds.
The IVR can interact with any hardware or communications support provided by the underlying operating system.
In the UNIX/AIX configuration, the underlying operating system can support virtually all industry standard removable media devices including 6250BPI 9 track magnetic tape, high density cartridges, 1/2 inch, 8mm and 4mm cartridges, floppy disks (in DOS format) and even ZIP drives.
The IVR can also support almost any industry standard form of physical connectivity. Most common are 4/16mb token ring, slow and fast Ethernet, FDDI, direct channel attach and both synchronous and asynchronous serial interfaces.
The protocol suites are also extensive. For TCP/IP, the IVR supports:
For CTI Links, the IVR can interface via vendor supplied custom libraries (e.g. Meridian and Lucent CTI interfaces).
Despite the upsurge in internet types of connectivity, there are still numerous systems using the more classical IBM SNA interface. The IVR can emulate a variety of PU type 2 devices, the most common being printers (LU type 1 and 3) and CRTs (LU type 2). The printer emulation in particular can be an effective way to bring up an application quickly.
Similarly, the IVR has a flexible CRT interface which organizes mainframe resources by function, not by line. Because of this organization mainframe interface resources to be dynamically allocated according to load. IVR scripts can access multiple mainframe resources easily and complex mainframe menu systems can be navigated without code changes.
Our IVR/CRT configurations have been as varied as a single CRT emulation for 96 lines to several CRT emulation, going to different regions, per line.
The Connect Direct Network Data Mover (NDM) is also supported under SNA using a PU type 2 LU type 6.2 interface.
| ARGOS Home Page | Company Information | News | Services | Contact Us | Employment |