Provisioning The Http Subsystem - Cisco CRS-1 - Carrier Routing System Router Administration Manual

Customer response solutions release 4.1(1)
Hide thumbs Also See for CRS-1 - Carrier Routing System Router:
Table of Contents

Advertisement

Provisioning the HTTP Subsystem

Provisioning the HTTP Subsystem
Note
Note
Note
Cisco Customer Response Solutions Administration Guide, Release 4.1(1)
5-8
The HTTP subsystem is available only if your system has a license installed for
one of the following product packages:
- Unified IP IVR
- Unified CCX Premium
The Cisco CRS system uses the HTTP subsystem to enable CRS applications to
respond to requests from a variety of web clients, including computers and IP
phones.
If you are not using HTTP applications, you do not need to provision the HTTP
subsystem.
The CRS system uses subdirectories in the Cisco CRS installation directory to
store text substitution, eXtensible Style Language (xsl) templates, static and
dynamic web pages, and Java Servlet Pages (JSPs).
Use the Document Management page to upload these documents. For more
information on the Document Management page, see
Prompts, Grammars, Documents, and Custom Files."
To provision the HTTP subsystem, you need to provision HTTP triggers. HTTP
applications use triggers to activate the application in response to an incoming
HTTP message.
In addition—if necessary—you can change the TCP/IP port used by the HTTP
server.
This section describes:
Configuring HTTP Triggers, page 5-9
Changing Port Numbers, page 5-10
Chapter 5
Provisioning Additional Subsystems
Chapter 7, "Managing

Advertisement

Table of Contents
loading

This manual is also suitable for:

Crs release 4.1(1)

Table of Contents