Cisco Cisco Unified IP Interactive Voice Response (IVR) 8.0(1) Administrator's Guide

Page of 448
 
Chapter 5      Provisioning Additional Subsystems
Provisioning the HTTP Subsystem
5-10
Cisco Customer Response Solutions Administration Guide, Release 6.0(1)
Step 4
Click Add.
The HTTP Trigger Configuration web page closes, and the trigger information 
appears on the HTTP Trigger Configuration summary web page.
You are now ready to provision any additional subsystems your CRS applications 
require or to begin configuring CRS applications. See 
Changing Port Numbers
You can set the TCP/IP port number the CRS Engine uses for the internal HTTP 
server when you install the HTTP subsystem. The default port used during 
installation is port 8080.
After the HTTP subsystem is installed, you can change the port in the Tomcat 
server.MIVR.xml file.
To change the TCP/IP port number, complete the following steps.
Note
You need to follow these steps on all the CRS Engine-enabled nodes in the cluster.
Maximum Number of 
sessions
The maximum amount of simultaneous sessions (instances) that the 
application can handle.
Note
The limit for the maximum number of simultaneous remote 
monitoring sessions is 16, but the actual number depends on your 
system’s CPU and memory resources. Entering a number that is too 
high can result in unacceptable system performance.
Idle Timeout (in ms)
The number of milliseconds the system should wait before rejecting the 
HTTP request for this trigger,
Enabled
Radio buttons. Valid options:
Yes - enable the trigger,
No - disable the trigger.
Field Name
Description