Configure Cross domain for Call Property service
Functionality added for cross domain interaction between web based java/jquery requests and the Call Property Service. The following settings have been added to the AppSettings section in the web.config file:
This setting should be the same domain as the domain of the web application from which the request to the Call Property Service originated. Sign * means that all domains are allowed.
<add key="Access-Control-Allow-Origin" value="http://mywebapplication.domain.com"/>
This setting contains the supported headers in case a web request is received.
<add key="Access-Control-Allow-Headers" value="Content-Type, Accept, SoapAction" />
This setting contains the allowed web request actions.
<add key="Access-Control-Allow-Methods" value="POST,GET,OPTIONS" />
The Access-Control-Max-Age response header indicates how long the results of a preflight request (that is the information contained in the Access-Control-Allow-Methods and Access-Control-Allow-Headers headers) can be cached.
<add key="Access-Control-Max-Age" value="1728000" />
Normally only the Access-Control-Allow-Origin should be changed to allow the domain of a web application to access the Call Property Service.
Cross domain settings for Silverlight (Extension Window Call Classifications tab)
This functionality was already available, but is described to give a complete overview of the cross domain options regarding the Call Property Service. In case the extension window and the Call Property service are hosted in 2 different domains, we will have 2 options to enable cross domain interaction between the extension window and Call Property service:
Option 1 is to run the extension window with elevated rights and the official Workstreampeople certificate installed. This will allow cross domain interaction between the extension window and Call Property Service.
Option 2 is adding additional configuration in IIS. It is possible to add a clientaccesspolicy.xml file to the root folder of the web site in which the CallProperty Service application is hosted. We can add the domain of the extension window in this client access policy file. This will enable cross domain communication between the extension window call classification tab and the Call Property Service.
Fig.1: The clientaccesspolicy.xml file has been placed in the IIS root folder to enable cross domain interaction between a Silverlight application and the Call Property Service.
Example of a clientaccesspolicy file:
<?xml version="1.0" encoding="utf-8"?>
<resource path="/" include-subpaths="true"/>
The domain uri setting should contain the domain of the extension window.
Desktop applications do not require any cross domain settings to interact with the Call Property Service. The Attendant Call Classifications plugin and console test applications should not require any cross domain settings.