Before Installation
This information is required before the basic installation of the system.
Information | Comments | Example | Status |
Hypervisor host Access to hypervisor:
| Only reqired, if VMs are to be configured. | 1.1.1.1 | |
Hypervisor type The type of the hypervisor used is needed if the tools are not pre-installed. | Part of the standard installation is to install tools for Hyper-V or VMWare If the hypervisor is neither of these, the tools must be installed by the customer. | HyperV / VMWare | |
Network For the subnet(s) of the virtual machines:
| Network: 192.168.1.0 | ||
Naming convention The required naming convention for the virtual machines. | Only reqired, if VMs are to be configured. | acd-dbm.example.com | |
DNS Servers The addresses of the DNS servers used in the network are required. | 192.168.1.254 | ||
Time server The IP address of at least one reliable time server. | A reliable NTP time server must be available for the installation. Windows domain controllers are not always reliable NTP sources. | ptbtime1.ptb.de | |
CentOS Root Login The root user and password is required for the CentOS servers. | If the root user is not supplied, the supplied user account must be able to execute commands with sudo and change to root with sudo -s. | User: root Password: secret | |
Windows Login An AD domain user or a local user is required for the Windows Server(s). | This user must have local administrator rights to the machine. | User: administrator Password: secret | |
Internet connection Available from the VMs directly or proxy server settings. | The installation cannot be performed without internet access. | Proxy Server: proxy.example.com:8080 | |
Windows updates All windows updates should be performed on the windows server before handover. | The customer is responsible for updating the windows operating system. | ||
Virus scanners Not all virus scanners are good news. The jtel system is a real-time communication system - and some virus scanners are very intrusive indeed (or just plain and simply badly configured) and can have a serious impact on system performance. | It is solely the customer's responsibility for deploying an adequate virus scanner. | ||
External file share The file share used by the system can be external and provided, for example, by a high availability storage system. If this is to be external, an SMB file share is required and the following information:
| Note, because Windows machines will inevitably use the logged in user and password when accessing the share, this is recommended to be the same as the username and password used on the windows machine(s). This is required to be so if the applications on the windows machine are to be configured as windows services. | User: jtelacd Password: secret | |
Firewall and Routing All of the machines for the ACD installation will be installed with a firewall, and the necessary ports opened for communication between the machines. A firewall between the PBX and the ACD must be correctly configured to allow SIP / RTP and the PBX connector from the jtel system to access the PBX. | A firewall between the servers is not recommended, better as a standalone solution in it's own subnet with a firewall covering access to the load balancer by http(s) for accessing the webservers. A firewall between the PBX and the ACD is not recommended. A proxy between the PBX and the ACD (for accessing the PBX connector) is definately not recommended and may cause serious problems with operation (timeouts and other errors). | ||
Web Access If a certificate is required (i.e. the portal should be accessed via https) then a certificate is to be provided before installation. The certificate must be provided in .pem Format including the following:
|
After Installation
Information | Comments | Example | Status |
LDAP(S)
| Only required for LDAP / LDAPS authorization of logins. For further information, visit this page | ldaps://domaincontroller.example.com:636 | |
Email Server For sending email via SMTP:
| Server: smtp.example.com Protocol: SMTPS / starttls Port: 587 User: jtelacd@example.com Password: secret Sender: jtelacd@example.com |
Tests after Basic Installation
It is recommended to perform the following tests after basic installation is complete:
Test | Required Result | Status |
---|---|---|
SIP licenses installed and correct count | Correct count | |
Configuration of telephony server
| channel_count = SIP licenses | |
Configuration of telephony server
| Total channels, inbound and outbound channel counts correct. | |
Configuration of telephony server
| Lines and P2 correspond to number of purchased agent / supervisor / queue / IVR and transfer channels | |
Symmetric RTP setup
| File present and correct count | |
PBX Connector
| Receives messages regarding monitored extensions in log. | |
Time Synchronisation | All servers syncing with a reliable time server.
| |
Platform UDP Listener | Configured and running on telephony and webservers, cluster connecting OK | |
MySQL replication | SHOW SLAVE STATUS\G output good on all DBs
| |
Telephony Server | No errors when starting up | |
Webservers | No errors when starting up | |
Load Balancer | haproxy
| |
PBX Connection
|
| |
PBX Connection
|
| |
System parameters | Check other system parameters and make any necessary modifications |
Tests after System Configuration
It is recommended to perform the following tests after some configuration (setting up test numbers and an ACD group):
Test | Required Result | Status |
---|---|---|
Configure an ACD group with a logged on agent and music on hold. Setup group to allow calls without logged in agents. |
| |
Incoming call to a test number, agent not available. |
| |
Incoming call on test number, agent available. |
| |
Accept Call button |
| |
Number display on called device |
| |
Supervisor |
| |
Statistics |
| |
PBX Connector |
| |
Voice Mail - setup a rule to record a voice mail and activate this rule |
|