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

PegaCALL Screen Pop Error



After switching from White Mesa to IIS in your PegaCALL environment an error pccurs.

Error Messages

Transport error: 404 Error: Not Found

Steps to Reproduce

Open ChannelServices-Admin-CTILink ctconnect2 and select 'Test Connectivity'.

Root Cause

IIS is not configured completely. 


1. See tech note:  TechNote_Installing PegaCALL CTILink Server with Microsoft.

2. Remove references to ‘instancename’ in both PGLinkService.wsml and ServerRequest.wsml.

Example: PROGID='CTILink.IISCTI.Server.1 to PROGID='CTILink.PhoneRequestor.1

IISCTI instance name is removed since the deployment is done at the base directory (C:\Program Files (x86)\Pegasystems\PegaCALL\CTILink) rather than another directory (C:\Program Files (x86)\Pegasystems\PegaCALL\CTILink\IISCTI).


Published July 29, 2015 - 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