User Guide - Introduction - Requirements
Client Workstation Requirements
Here we present client workstation requirements. Please understand that ChaseData can only provide aggregated requirements for the processes corresponding to the ChaseData application, therefore, it is for you to determine and account for anything else that you may have consuming resources in your workstation.
Nevertheless, in order to help you get started, here we provide (1) required OS/software environment, (2) required Internet environment, and (3) three sets of hardware environment specifications, Minimal, Standard, and Power, each under a general set of assumptions.
Your OS installation and setup options, your drivers, the services and applications that you install and run, among other things, have an impact on your workstation’s resource consumption and therefore performance. You must account for them on top of any requirements we list here.
The following requirements are per client workstation.
OS/Software Environment Requirements
Communication Requirements
Hardware Environment – Minimal Workstation
These are the very minimal requirements for a workstation that is to be used exclusively for the ChaseData Client app (no other applications running) for basic usage (e.g. 1 or 2 call scripts).
Hardware Environment – Standard Workstation
These are reasonable resources for a workstation that is used for both the ChaseData Client app and typical Office application usage, or if the ChaseData Client app usage is more involved (e.g. larger amount of call scripts).
Hardware Environment – Power Workstation
These are necessary resources for a workstation that is used for both the ChaseData Client app and Office applications under heavy usage, or if the ChaseData Client app usage is heavy (e.g. large amount of call scripts).
NOTE: You can use the following commands from the MS Window Command Prompt to verify the .NET Framework versions:
reg query "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP"
reg query "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\full" /v version
Refer to the following picture.
If you need help accessing the Command Prompt, check the following link:
https://www.wikihow.com/Open-the-Command-Prompt-in-Windows
The System information in the Control Panel provides basic system information; refer to the following picture.
This link from Microsoft explains how to access the Control Panel:
You can check your Windows version running the 'winver' command from the Run window; refer to the following picture.
If you need help getting to the Run window, check the following link:
You can check your DirectX version running the 'dxdiag' command from the Run window; refer to the following picture.
You can right-click the speaker icon on the Windows taskbar to get to the Sound window and configure Playback and Recording devices; refer to the following picture.
Minimum Network Requirements for VoIP
- Voice traffic should be marked to DSCP EF per the QoS Baseline and RFC 3246.
- Loss should be no more than 1 percent.
- One-way latency (mouth to ear) should be no more than 150ms.
- Average one-way jitter should be targeted at less than 30ms.
- A range of 21 to 320 kbps of guaranteed priority bandwidth is required per call (depending on the sampling rate, the VoIP codec, and Layer 2 media overhead). If we
factor in bandwidth fluctuations and other typical internet data traffic
(mostly download), the following is a safe rule of thumb for upload bandwidth vs.
number of simultaneous calls: 500Kbps –> 1 call; 1Mbps –> 3 calls; 5Mbps –
16 calls; 10Mbps – 33 calls; 30Mbps - 100’s of calls.
Router Ports and Settings
Ports relevant to the Agent and Management Console applications:
943 | TCP |
4530 | TCP |
4531 | TCP |
Ports relevant to VoIP:
5060* | TCP / UDP |
8000-8005 | TCP / UDP |
10000-50000 | UDP |
* when doing port triggering in the firewall, trigger 5060 first; if everything works, do not have to trigger the other ones
Feature compatibility:
Disable SIP ALG, usually via the router/modem firewall configuration interface or any other method allowed by your specific router.
SIP ALG (Application Layer Gateway) modifies SIP packets, often corrupting them (from server-side solution perspective) and making them unreadable, which can result in unexpected behavior, such as phones not registering and incoming calls failing.
Related Articles
User Guide - Introduction
Introduction The Call Center as a Service (CCaaS) from ChaseData provides Call Center campaign management with complete Outbound and Inbound call capabilities. The purpose of the ChaseData CCaaS solution is to allow call centers and telemarketers ...User Guide - Initial Configuration - Planning Guide
Initial Configuration Planning Guide We have already shown both a generic initial customer questionnaire and a basic initial setup sequence to get us started with a workable configuration. Next, we’re going to go a little further by presenting ...User Guide - Initial Configuration - Setup Flow
Initial Configuration Setup Flow Strategy Alignment It’s important to be prepared for the specific needs of the customer that requires the Initial Configuration; that way we can focus on those configuration items that are key to get them started for ...User Guide - Agent Portal - Tools
Agent Portal Tools Chat Agents have the ability to communicate with each other, and with managers and supervisors, via an internal Chat tool, and according to what the corresponding Agent Skills allow them to do. Chat Channels are configured by a ...User Guide - Management Console - Introduction
Management Console The ChaseData CCaaS Management Console application is used for a variety of configuration and management tasks. Let’s divide them in the following groups: Setup Data Lookup Monitoring & Analytics. Do note that access to ...