CallScripter is a real time application and so resource availability on the client machine should be specified with this and other client side application demands in mind.
This article is an indicative resource requirement for the most recent supported browser, with older browsers being less resource efficient.
Advised Dedicated Resources
For general operations we recommend a minimum of a single core and 500MB of RAM dedicated for the Internet Explorer browser that CallScripter is run within; whether this be a physical desktop or a virtualised environment. This is to facilitate the local processing required for page transitions and for reasonable volumes of script logic within an acceptable time.
Any other client side applications and OS resource requirements would be in addition to this.
Due to the nature of CallScripter and its customer driven content in some highly demanding scenarios additional resources may be required.
Operating Environment
If you are using a CallScripter CT Provider Internet Explorer must be running natively within the Windows Desktop Environment that the agents are connecting to. The CallScripter application requires to access locally installed software on the client environment (COM objects).
If this Windows Desktop Environment is virtualised or physical has no bearing on the CallScripter CT Provider operation. This is due to the communication and local resource loading that the Internet Explorer browser needs to perform from the locally installed CT Provider and 3rd party telephony resources.
Speed Test
We have observed that some virtualised environments can give lower performance than physical pcs and thus all JavaScript processing can take longer. As CallScripter (especially initial script pop) relies heavily upon JavaScript this can require additional consideration during script building, above and beyond when used on physical desktops.
As a rough indication a standard physical desktop pc will range between 100ms and 200ms for Total Time (lower is better). With Virtual environments often up at 400ms~.
Some environments have been found to take up to 2000ms and so the CallScripter application will not react as quickly as desired in these scenarios.
