Administrator Guide: net.Supervisor 1.4.6

Prerequisites

net.Supervisor needs to have some specific modules and softwares versions installed to work properly.

Note that net.Supervisor can have a big impact on the performances of your SOP. Please read the section "Maximum number of net.Supervisor instances per SOP".

Modules and resources

Module

• SOP API, version 2.33.7 or higher
• Application management server 3.3.2 or higher
• SOP Base Module 1.4.1 or higher. Note that if you are using PUM, SOP Base should be 1.4.5 or higher
• netSupervisor module 1.4.6

Resource

• netSupervisor resource 1.1 or higher

SMP requirements

• Version 1.3.0 or higher
• If this is not the case, please ask Escaux Support to perform an upgrade.

Network requirements

• The SOP IP address must be reachable from the client's computer using TCP and the ports 4445 as well as 80

Host minimum requirements

Processor	Pentium 4 2.4 GHz or equivalent
Memory	1GB RAM
Hard Disk Space	500MB
Operating system*	Windows 2000, Windows XP, Windows Vista, MAC OS X or Ubuntu
Connection	IP network connection (broadband, LAN, wireless)
Java	Java 6 and Java 7 are supported

• Windows Operating Systems: 32-bit processors only

Configuration

The following tasks must be performed at the SMP:

• Create an SMP account for the Supervisor, if not already done.
• Create a net.Supervisor resource and select the queues you want to monitor in net.Supervisor
• Add a permission to for this user to be able to use the resource
• Apply the changes

Create an account

You need to create an account, which can be used by the supervisor to login in the net.Supervisor application. If the supervisor already has an account (e.g. as a net.Desktop user), this step can be skipped.

Please, ensure that you have 1 account per net.Supervisor instance.

Create the net.Supervisor resource

net.Supervisor need its own resource like any phone, this is where all the parameters can be set for a particular net.Supervisor account.

• Select 'net.Supervisor',
• Click 'Create'

Permissions

Create an association between the net supervisor account and a net.Supervisor resource.

• Select the supervisor user and the resource you created in the previous section.
• Click create
• Do not forget to apply the changes.

Installation instructions (Windows, Mac OSX, Ubuntu Linux)

For redundancy and failover reasons it is strongly advised to create the following entry in your internal DNS servers:

netsupervisor.yourdomain.com        A        a.b.c.d

where a.b.c.d is the IP address of the SOP server located at the same site as the DNS server.

In order to install the net.Supervisor client, each user simply points his/her web browser to the following URL:

http://netsupervisor.yourdomain.com/netSupervisor/

Follow the instructions as described.

During the installation, a pop up might appear asking to activate/run a Java applet. You will see an image as the one below. Please select the 'Always trust content from this publisher' and 'Run' the applet.

Limitations, known issues and frequently asked questions

• net.Supervisor GUI may freeze after network failure or computer standby: (M5803)
• The "History to consider" parameter of the tile "Average number of calls waiting" must be bigger than the timeout of the queue(s) as well as the average waiting time. If not the value will not be accurate.
• The queues that are not currently selected in a given net.Supervisor window will not be updated if calls enter this queue. Only the queue currently selected will be fully monitored.

Maximum number of net.Supervisor instances per SOP

net.Supervisor is a real time application that queries the SOP when there are new calls entering a monitored queue. Therefore the number of running net.Supervisor instances can impact to a significant extent the performances of the SOP.

Please note that each net.Supervisor window must be considered as a fully independent net.Supervisor instance, even if those windows are open on the same computer and monitor the same queue.

For a SOP having a large amount of traffic (max 1 call per second) entering its queues, the following limitations are applicable :

• On a HP DL120 : Max 2 instances of net.Supervisor
• On a HP DL360 : Max 8 instances of net.Supervisor

This dimensioning is done based on Escaux Fusion 2.1. Features that are resource hungry, such as call recording, transcoding, complex callflows will have a significant impact on the performance of the SOP. Please contact us if you would like to validate your system readiness.

Acceptance tests

A list of acceptance test can be found in this document.