Sites that have the Cisco Customer Response Application (CRA) 2.x
co-located with Cisco CallManager has issues with the start of the Application
Engine if the new Attendant Console 1.x is installed on the same server.
There are no specific requirements for this document.
The information in this document is based on CRA 2.x.
For more information on document conventions, refer to the
Technical Tips Conventions.
Any application hosted by the CRA server does not work. Cisco IP
AutoAttendant, IP-ICD, and Extension Mobility are some of the most common
applications that run on the Apps server.
The Engine Status page (http://ipaddress/appadmin) shows the SubSystems
as "Unavailable" as shown here.
Figure 1: Application Administration --
This problem only occurs if all of these are true:
For more information about the Attendant Console, see:
Unified Communications Manager Attendant Console.
Change the RMI Port on the Apps server to use something other than 1099
(for example, 1098). Follow these steps to change the RMI
Log in to the Application Administration web page
(http://ipaddress/appadmin). Click Engine, then click
Change the RMI Port Number to
Figure 2: Application Administration -- Change RMI Port
Start the Engine.
Click Start > Progams >
Administrative Tools >
Find the World Wide Web Publishing Service and the
Figure 3: Services