Skip to main content

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

Creating an OpenCTI Desktop connector

Updated on January 10, 2022

To use the OpenCTI Desktop framework to integrate Pega Call with a third-party Computer Telephony Integration (CTI) system, create your implementation file, and then create an OpenCTI Desktop link.

  1. In Dev Studio, enter pega_cti_desktopAPI in the search bar.
  2. Click the pega_cti_desktopAPI.js file to open it.
  3. Click Save as to create an instance of the file. This instance is your JavaScript implementation file.
  4. Change the object name and name space from pega.cti.desktopApi to custom.cti.desktopApi.MyConnectorName.
  5. Click Create and open.
  6. In the file, set the object name and name space.
    @public - Prototype definition for pega.cti.desktopApi
    pega.cti.desktopApi = function() {
    pega.cti.desktopApi.prototype = {
    @public - Prototype definition for custom.cti.desktopApi.MyConnectorName
    custom.cti.desktopApi.MyConnectorName = function() {
    custom.cti.desktopApi.MyConnectorName.prototype = {
  7. Click Save.
  8. In the navigation pane of App studio, click SettingsPega Call.
  9. In the list of computer telephony integration (CTI) settings, click CTI link setup.
  10. On the CTI link setup page, click Add new link.
  11. Enter a name and description for the link.
  12. In the Link list, select OpenCTIDesktop.
    The page displays additional settings that are specific to OpenCTI Desktop links.
  13. In the Javascript object field, enter custom.cti.desktopApi.MyConnectorName.
  14. In the Primary server url field, enter the URL address of your server.
  15. Optional: To enter the URL address of your failover server, use the Failover server url field.
  16. Confirm your updates by clicking Save.

Have a question? Get answers now.

Visit the Support 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. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us