Pega Call Embedded UI not working in CS Constellation (AWS Connect)

[dliev (Diego Lievano)]

Currently, I am facing an issue with Pega Call in Customer Service Constellation ('24.1.1) connecting with Amazon Connect.

I followed the guide Implementing Pega Call in Constellation and I am able to connect the interaction to Amazon Connect. After I manually log in with Amazon Connect credentials, I am getting an error in the browser console:

Refused to frame ‘https://*********.my.connect.aws/’ because an ancestor violates the following Content Security Policy directive: “frame-ancestors ‘none’”.

Here are some research I have done and some of the things I did within Pega and Amazon Connect:

• In Pega environment:

• Added in the application rule a new Policy Rule, allowing all Frame-Ancestors.

• Modified DSS (http/responseHeaders) and added Content Security Policy to all (*)

• In Amazon Connect:

• Added a Third Party Application (adding the Pega URL as the Access URL and Approved Origins)

• In the Approved Origins, I added the Pega’s environment URL.

Nothing seems to be working, still getting the same error.

Attached Image with the error, Pega Call seems to be connected but I am not able to get the pop up or launching the interaction immediately.

[BELIN (Neal Beliveau)]

@dliev It certainly looks connected from the screenshot. Are you sure your call treatment rules are setup correctly? Those control the pop and interaction behaviors.

If so, please enter a support ticket if you need more help.

[SandeepPenumadu]

@dliev Could you please double-check the server URL for your Amazon Connect configured? Make sure to add “/ccp-v2” at the end of the URL (for example - Amazon Connect Contact Control Panel). Also, verify if your Pega Instance is whitelisted in AWS for the corresponding Amazon Connect instance.

Configuring Amazon Connect links (pega.com)

[SohamChanda1107 (Soham Chanda)]

@SandeepPenumadu Hi , Its still not working for me , given the ccp-v2 at the end of connection link still getting frame ancestor issue, even updated the application CSP with allow all for frame ancestors, still iframe is being restricted.
Refused to frame ‘’ because an ancestor violates the following Content Security Policy directive: “frame-ancestors ‘none’”.

[SandeepPenumadu]

@Soham_Chanda1107 Could you kindly submit a Support incident, ensuring that all the necessary details are included, in order to receive further assistance? Thank you.