- IBM AIX V6.1 (5765-G62) with minimum Technology Level 03 Service pack 01
- IBM XL C Enterprise Edition for AIX, V9 (5724-S70) – the C RTE component included with the AIX installation media.
- IBM 32-bit SDK for AIX, Java Technology Edition, V6, Service Refresh 7 (SR7), level 22.214.171.124. This is available as a free download and must be installed prior to the installation of WebSphere Voice Response V6.1.
- IBM DB2 Workgroup Server Edition V9.5(1) (5765-F35) at minimum fix pack level 4.*
* IBM DB2 Workgroup Server Edition (DB2 WSE) Version 9.5, program number 5765-F35, is shipped with WebSphere Voice Response V6.1 as a “limited use” copy, entitling customers to install and use DB2 WSE, subject to the terms and conditions of the license agreement that accompanies DB2 WSE. Note that DB2 WSE is not part of WebSphere Voice Response V6.1 and is subject to its own license agreement. The full (or unlimited) version of DB2 WSE is also available as a separate product from IBM.
Optional cost-free software requirements:
- License Use Management Runtime
Optional software requirements available at additional cost:
- IBM XL C/C++ Enterprise Edition for AIX, V9 compiler (5724-S71) to compile Custom Servers.
- IBM Communications Server for AIX, V6.3 for host communication using terminal emulation (5765-E51)
- HACMP, V6.1 — customers requiring high availability using a redundant NFS and DB2® server
- Tivoli® NetView for AIX — one of several Tivoli products for SNMP-based system management
- JAWS screen reader on a PC for accessibility; for more information, visit: freedomscientific.com/fs_products/software_jaws5intro.asp
- WebSphere Voice Server, V5.1 or other third party MRCP-V1-Draft 4-compliant speech server — customers requiring text-to-speech and voice recognition
- IBM Power4, Power5, Power6, or Power7 processor-based Power Systems servers (those systems supported by AIX 6.1) or IBM BladeCenter Power processor-based blade servers.
- VoIP SIP connectivity requires a Power Systems server or BladeCenter Power processor-based blade server. No DTTA physical adapter is required – the standard system Ethernet adapter is used. Optionally, a VoIP/TDM gateway is required to connect to legacy TDM infrastructure.
- For TDM telephony connectivity, one or more IBM DTTA (FC 6312) adapters (up to a maximum of four) are required in a supported IBM Power Systems server.
Details of supported machines:
- BladeCenter computers
For Voice Over Internet (VoIP) Telephony capability using Session Initiation Protocol (SIP), WebSphere Voice Response for AIX runs on different models of NEBS compliant BladeCenter computers without the need for a Digital Trunk Ethernet Adapter (DTEA) card. All Power BladeCenter systems are supported for VoIP/SIP, including: BladeCenter JS20, JS21, JS23, and JS43.
The VoIP/SIP support is implemented by a software simulation of a DTEA card named Digital Trunk No Adapter (DTNA), which allows most WebSphere Voice Response for AIX applications to run without the need for a DTTA, or DTEA adapter.
For information about Voice over IP and how it is implemented in WebSphere Voice Response Version 6.1, see Voice over IP.
- System p5 and pSeries computers (LINK to page with copy in doc, “System p5”)
For details of telephony adapters supported, see:
- Telephony hardware
- DTTA and DTEA adapters are supported on systems capable of holding a PCI card.
- WebSphere Voice Response 6.1 does not support the DTXA adapter, withdrawn in June 2004.
AIX LPAR support considerations:
Using DTNA and VoIP/SIP, four WebSphere Voice Response LPARs are supported per BladeCenter blade or pSeries machine. An appropriate allocation of CPU, memory, storage and Ethernet resources must be assigned to each WebSphere Voice Response LPAR. As a guideline, a system performance rPerf of 20 can support a 480-channel WebSphere Voice Response LPAR running speech-enabled VoiceXML applications.
See www.ibm.com/systems/power/hardware/notices/rperf.html for further information on rPerf.
Virtualization and Micro-partitioning in WebSphere Voice Response LPARs are supported, but not recommended. For performance reasons it is recommended wherever possible that each WebSphere Voice Response LPAR has its own dedicated communications adapter (for example, Ethernet), disk adapter (for example, SCSI), and its own physical disks.
It is strongly recommended that no other applications are run in the same LPAR (or system, if LPAR is not used) as WebSphere Voice Response.