Configuring the CTI iFrame

After you have created your partner application, you must gather the following information, which is used to configure the application inside of the Call Summary and Call Tagging feature:

  • The URL of the partner application page
  • The window domain of the final page with which the partner application is loaded

URL of the Partner Application

You must provide the URL for the partner application page that will be embedded in Call Summary and Call Tagging as part of the CTI iFrame. This should include any static query parameters that the partner application expects.

Call Summary and Call Tagging appends the crmDomain query parameter to this URL, which is the window location of the Call Summary and Call Tagging application. For example:

https://opav12345.getway.mycti.cloud/crm/embeddableApp.html?enableFrameworkClientId=true&dedicatedLoginWindow=true

This example shows an iFrame URL that is used by Call Summary and Call Tagging for loading the partner application, where, crmDomain=<Service-Guide-window-location> is appended by Call Summary and Call Tagging.

https://opav23abc5a4z.getway.mycti.cloud/crm/embeddableApp.html?enableFrameworkClientId=true&dedicatedLoginWindow=true&crmDomain=

Window Domain of the Final Page

You must provide the window domain, including the protocol, host and port number, of the final page with which the partner application will be loaded. The window domain may not be same as the hostname present in the iFrame URL above, as the final window may be loaded after multiple redirections. This is common when using authentication providers, and can result in a window location that is different than the initial URL. For example:

https://apps.usawest.mycti.cloud