The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
This document explains the Remote Method Invocation (RMI) error message, "Connection refused to host:[localhost:1099]; nested exception is: java.net.ConnectException: Connection refused" when you debug a script in the Cisco Customer Response Application (CRA) Editor in a Cisco IP Contact Center (IPCC) Express environment. It also provides a workaround.
Cisco recommends that you have knowledge of these topics:
Cisco IPCC Express
The information in this document is based on these software and hardware versions:
Cisco IPCC Express 3.0.x and 3.1.x
Cisco CRA Editor 3.0.x and 3.1.x
The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, make sure that you understand the potential impact of any command.
Refer to Cisco Technical Tips Conventions for more information on document conventions.
When you attempt to debug scripts with the Cisco CRA Editor, this RMI Error pop-up window appears.
When the error message is displayed, the ping to the Cisco CallManager server by name fails from the remote client desktop. This indicates the client desktop cannot resolve the name of the Cisco CallManager. To correct this problem verify and/or modify the ccndir.ini file which is located in the c:\Winnt\system32\ccn directory on the client desktop. Use the Cisco CallManager IP address for the LDAPURL property, as shown here.
After the ccndir.ini file is modified, below, and the CRA Editor is restarted, and the remote client desktop is able to debug script with the CRA Editor.