Skip to main content


         This documentation site is for previous versions. Visit our new documentation site for current releases.      
 

Verifying your update

Updated on October 12, 2021

If you use a computer telephony integration (CTI) link engine, verify that Pega Call™ and the third-party Java archives (JAR files) are accessible after you have updated your application. If you have not already done so, restart the application server to ensure that Pega Call and the third-party Java archives are loaded into the Pega Platform.

Note: In Pega Call used with Pega Customer Service, ensure that both these applications are always on the same patch release version. For example, if your Pega Call version is 8.5.3, then your Pega Customer Service version needs to also be 8.5.3. When you update one of these applications, you need to update the other one as well.
  1. Log in to the application using your administrative privileges.
  2. In the header of Dev Studio, click ConfigureChannel ServicesPega CallAdministration and Configuration.
  3. Click the Version Information tab to display the version.
  4. Verify that the Pega Call Engine (8.05.01.xxx) and the Channel Services Codeset (08-05-01) are accessible.
  5. If you use Avaya or Genesys CTI, verify that the corresponding third-party libraries are accessible.
  • Previous topic Disabling background class saving with JBoss e-Tier
  • Next topic Modifying the service packages and access groups

Tags

Pega Call 8.5

Have a question? Get answers now.

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

Visit the Support Center

Did you find this content helpful?

Yes
No

Want to help us improve this content?
Suggest an edit

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

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us