Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

CTI engine does not auto start after a JVM restart.



After configuring a CTI server definition and connecting to Cisco, the CTI engine is working fine but if the PRPC JVM has to be restarted, it does not auto restart eventhough the "AutoStart" flag is enabled. 

Error Messages

None that I can see

Steps to Reproduce

have CTI engine running. Shutdown PRPC and restart. Observe that the CTI engine did not auto start

Root Cause

CTILINK Engine will not auto start with a green check showing.  The green check only shows after a CSR is connected and monitoring a  device.


The autostart options means that the ctilink engine is primed and ready to accept logins. It was not intended to start the engine and display a green check box as running. The CSR can login into any CTILINK Engine even w/o autostart enabled. At that time the engine will connect and run with the green check mark.  The Autostart "primes" this connection so it takes less time to process. 

Published January 31, 2016 - Updated December 2, 2021

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us