ADMIN GUIDEEPOS Manager
ON PREMISES v6.1.0 OR HIGHER(BASED ON LINUX DOCKER)

1

Content
1.Introduction
1.1

Product overview............................................................................................................................................................ 6

1.2

Attributes of EPOS Manager.....................................................................................................................................

1.3

Scope of the document............................................................................................................................................... 6

1.4

Intended audience of this document..................................................................................................................... 6

1.5

EPOS Manager Workflow............................................................................................................................................ 7

6

2.System Requirement
2.1

Overview of system requirement............................................................................................................................. 8

2.2

Hardware requirement................................................................................................................................................. 8

2.3

Software requirement................................................................................................................................................... 8

2.3.1

Installing Docker Desktop / Docker Engine.......................................................................................................... 8

2.4

Operating system requirement................................................................................................................................. 12

3.Installing EPOS Manager
3.1

Prerequisites..................................................................................................................................................................... 13

3.2

Installation steps............................................................................................................................................................. 13

3.2.1

SQL Permissions.............................................................................................................................................................. 13

3.2.2

Configuring .env file...................................................................................................................................................... 14

3.2.2.1

Configuring databases.................................................................................................................................................. 14

3.2.2.2

Configuring local storage URL.................................................................................................................................

3.2.2.3

Configuring CName........................................................................................................................................................ 15

3.2.2.4

Configuring Certificate................................................................................................................................................... 15

3.2.3

Configuring custom ports and secure protocol

15

for EPOS Manager......................................................................................................................................................... 16
3.2.3.1

Configuring EPOS Manager for HTTP.................................................................................................................... 16

3.2.3.2

Configuring EPOS Manager for HTTPS.................................................................................................................. 18

3.2.3.2.1 Configuring SSL certificate to be usedfor HTTPS communication.......................................................................................................................................... 20
3.2.4

Hosting the EPOS Manager (On-Premises) Server............................................................................................ 20

3.3

Upgrade from EPOS Manager v5.x.x (Exe installers)
to v6.1.0 and higher...................................................................................................................................................... 20

3.3.1

Configuring .env file...................................................................................................................................................... 20

3.3.2

Configuring custom ports and secure protocol
for EPOS Manager......................................................................................................................................................... 21

3.3.3

Uninstalling EPOS Manager (older version)......................................................................................................... 21

3.3.3.1

Uninstall EPOS Manager.............................................................................................................................................. 21

3.3.3.2

Uninstall EPOS Manager API...................................................................................................................................... 212

3.3.4

Hosting the EPOS Manager (On-Premises) Server............................................................................................. 21

3.3.5

Migrating firmware/software files from WIX to Docker................................................................................... 21

3.4

Upgrading to future EPOS Manager versions...................................................................................................... 22

3.5

Offline installation........................................................................................................................................................... 22

3.5.1

Download docker images............................................................................................................................................. 23

3.5.2

Save images to local file storage............................................................................................................................... 23

3.5.3

Move files to offline server........................................................................................................................................... 23

3.5.4

Load images into offline Docker repository.......................................................................................................... 23

3.5.5

Install EPOS Manager..................................................................................................................................................... 23

4. Getting started
4.1

Pre-Registration................................................................................................................................................................ 24

4.2

Registration......................................................................................................................................................................... 25

4.2.1

On Premise SignUp.......................................................................................................................................................... 25

4.2.2

Logging in............................................................................................................................................................................ 25

4.2.3

Forgot Password................................................................................................................................................................ 25

4.3

Deployment of the EPOS Connect............................................................................................................................. 26

4.3.1

Retrieving client files for the first time.....................................................................................................................

4.3.2

Installing the client manually for the first time...................................................................................................... 27

4.4

EPOS Manager Layout..................................................................................................................................................... 28

4.4.1

Login information.............................................................................................................................................................. 28

4.4.1.1

Settings (General & Data privacy)............................................................................................................................... 28

4.4.1.2

Administration..................................................................................................................................................................... 31

26

4.4.1.2.1 View Admins......................................................................................................................................................................... 31
4.4.1.2.2 Add/Edit Admin................................................................................................................................................................... 31
4.4.1.2.3 Transfer Ownership............................................................................................................................................................. 32
4.4.1.3

Client config.......................................................................................................................................................................... 32

4.4.1.4

Change Password............................................................................................................................................................... 32

4.4.1.5

Help.......................................................................................................................................................................................... 32

4.4.1.6

About....................................................................................................................................................................................... 32

4.4.1.7

Logout..................................................................................................................................................................................... 32

4.4.2

Grid settings......................................................................................................................................................................... 33

4.4.2.1

Row count.............................................................................................................................................................................. 33

4.4.2.2

Display sections................................................................................................................................................................... 33

4.4.2.3

Column display order........................................................................................................................................................ 33

4.4.3

Search...................................................................................................................................................................................... 33

4.4.4

Information fields............................................................................................................................................................... 33

4.4.5

Page navigation.................................................................................................................................................................. 33

4.4.6

Application menu............................................................................................................................................................... 34

3

5. Dashboard
5.1

Active device....................................................................................................................................................................... 35

5.2

Firmware version............................................................................................................................................................... 35

5.3

Software version................................................................................................................................................................ 35

5.4

Call activity............................................................................................................................................................................ 35

5.5Your assets............................................................................................................................................................................ 36

5.5.1

Devices................................................................................................................................................................................... 36

5.5.2

Softphones........................................................................................................................................................................... 36

5.6

Deployments....................................................................................................................................................................... 36

6. Manage user
6.1

Users....................................................................................................................................................................................... 37

6.2

Manual group..................................................................................................................................................................... 38

6.3

AD group.............................................................................................................................................................................. 39

6.4

Inactive users...................................................................................................................................................................... 40

6.5

Deleted users...................................................................................................................................................................... 40

7. Manage devices
7.1

All Devices............................................................................................................................................................................. 41

7.2

Active Devices..................................................................................................................................................................... 43

7.3

Inactive Devices.................................................................................................................................................................. 43

7.4

Removed Devices.............................................................................................................................................................. 43

8. Manage updates
8.1

Firmware updates.............................................................................................................................................................. 45

8.2

Software updates............................................................................................................................................................... 46

8.3

Upload updates.................................................................................................................................................................. 47

8.4

Deployment status............................................................................................................................................................ 47

8.5

Deployment details........................................................................................................................................................... 48

9. Configuration
9.1

Configuration Overview.................................................................................................................................................. 50

9.2

Device Repository.............................................................................................................................................................. 51

9.2.1

Duplicate configuration package................................................................................................................................. 51

9.2.2

Edit configuration package............................................................................................................................................. 51

4

9.2.3

Deployment configuration.............................................................................................................................................. 51

9.3

Software repository........................................................................................................................................................... 52

9.4

Upload Configuration....................................................................................................................................................... 52

9.5

Deployment Status............................................................................................................................................................. 52

10. Provision
10.1

Quick Connect Codes.................................................................................................................................................... 53

10.2

Create/Edit Quick Connect Code............................................................................................................................... 53

11. Meeting Rooms
11.1

Create Meeting Room.................................................................................................................................................... 54

11.2

View Meeting Room........................................................................................................................................................ 54

12. Reports
12.1

User........................................................................................................................................................................................ 55

12.1.1

User Overview.................................................................................................................................................................... 55

12.1.2

Client versions.................................................................................................................................................................... 55

12.1.3Monthly Overview............................................................................................................................................................ 56

12.2

Device................................................................................................................................................................................... 56

12.2.1

Device Overview............................................................................................................................................................... 56

12.2.2Other devices..................................................................................................................................................................... 56

12.2.3

Device adoption................................................................................................................................................................ 57

12.2.4

Headsets per User............................................................................................................................................................ 57

12.2.5

Update Overview.............................................................................................................................................................. 57

12.3

Call Activity......................................................................................................................................................................... 57

12.3.1

Call Overview...................................................................................................................................................................... 58

12.3.2

Call Duration – Device..................................................................................................................................................... 59

12.3.3

Call Duration – Softphone............................................................................................................................................. 60

12.4

Softphone...........................................................................................................................................................................

60

12.4.1

Softphone Adoption.......................................................................................................................................................

60

13.Uninstalling EPOS Manager ......................................................................................................................................... 62

5

1. Introduction
1.1 Product overview
EPOS Manager is a cloud-based or on-premises multi-tenant
server application used for managing and supporting EPOS devices in Enterpriseenvironments.
Companies signing up for a tenant (company) account will gain access to an easy to
manage system, from where enrolled EPOS Connect clients (End-users)in the organization can be managed.
The IT administrator can easily track EPOS devices in the environment from any machine,push configurations and quickly deploy software and firmware updates to a vast
number of end-users.
EPOS Manager: Administering devices, end-users and associated client application.
EPOS Connect: End-user client application, providing local update, configuration and support for interface
with a range of softphones via the embedded drivers for connected devices.
1.2 Attributes of EPOS Manager
EPOS Manager enables a tenant administrator in an organization to:– Manage assets by providing full status overview– Locate devices and fetch device details from anywhere.
– Identify devices in the organization having an outdated version of firmware– Accomplish uniform attributes throughout the environment by deploying firmware/
software updates– Read and set settings on EPOS audio devices from anywhere.
– Identify underutilized devices to fully use the inventory, hence optimizing thebenefit of the device investment.
1.3 Scope of the document
This document contains an overview of EPOS Manager features and how to perform tenant
administrative tasks using the EPOS Manager.
1.4 Intended audience of this document
This document is intended for the selected Tenant Administrator. The tenant administrator
will be able to manage deployed EPOS devices.

6

1.5 EPOS Manager Workflow
The following diagram shows the basic workflow of the EPOS Manager (used by Tenant
Administrator) and EPOS Connect (used by end-users) applications.

72. System Requirement
2.1 Overview of system requirement
Administrators can manage several phases of firmware or software deployment, including
preparation, distribution and upgrades in different phases, depending on their infrastructure
and requirements:– SQL server and EPOS Manager hosted on the same machine– SQL server deployed on one system, EPOS Manager hosted on another system– If server is installed as a virtual machine, then nested virtualization needs to be enabled forservers running the Hyper-V, VMWare or any other virtualization host.
2.2 Hardware requirement
The following hardware is required for the EPOS Manager to install and run
successfully on a system:– Processor: 2 GHz processor– RAM: 16 GB RAM (recommended) - 8 GB RAM (minimum)– Storage: 50 GB available– Network card (Gigabit (10/100/1000baseT) Ethernet adapter)– Desired Configuration: RAID 1 ( recommend for SQL server)
2.3 Software requirement
The following minimal software is required for the EPOS Manager to install and run successfully on a system:– Supported Database Edition: SQL 2017 Standard/Express Edition 64 bit or higher / Azure SQL– Docker Desktop version 3.1 or later– Docker Engine version 20.10.12 or later– PowerShell version 5.0 or later version
2.3.1 Installing Docker Desktop/Docker Engine
Linux Docker hosting environment is required for EPOS Manager. You can install theDocker Desktop with WSL 2 backend software on Windows by following the instructions
here https://docs.docker.com/docker-for-windows/install/
Note: Docker has updated its terms and conditions and it requires a paid subscription.
For more details https://www.docker.com/blog/updating-product-subscriptions/
Installing Docker Engine
Linux Docker hosting environment is required for EPOS Manager. You can install the Docker
Engine with WSL 2 backend software on Windows.
To install the Docker Engine, follow the below instructions.
WSL 2 Backend
Open powershell with admin rights and execute the following commandwsl --install

8

This command will enable the required optional components, download the latest
Linux kernel, set WSL 2 as your default, and install a Linux distribution for you(Ubuntu by default) If your current setup does not have Ubuntu as default, then use this commandwsl --install -d Ubuntu

It will most likely require a restart, and start up with Ubuntu where you will be prompted with adding ausername and root password. Notice, that sudo command is a way of executing commands as admin.
WSL 2
We need to make sure we run WSL 2 instead of WSL. Open Powershell with admin rights.
List the distributions running in WSL / WSL2.

wsl --list -v

This will give a list of distributions installed and running. Below you can see an example ofa distribution NOT running WSL2, and this needs to be upgraded. If all is running WSL2 there
is no need for upgrading.

In Powershell run the following commandwsl --set-default-version <distribution-name> <wsl-version>i.e.

wsl --set-default-version Ubuntu-20.04 2

9Ubuntu command window
Open ubuntu and navigate to mounted drives (your c drive i.e.)

Docker Setup
Run the following commands on Ubuntu (20.04) to setup Docker Engine on your machine.
Note: You will often need to answer Y to proceed installing and updating, and you will need to provide
password to execute the commands.
Update and upgrade your Ubuntu distribution.

sudo apt update
sudo apt upgradeStart installing Docker, Refer to https://docs.docker.com/engine/install/ubuntu/ for more details.

sudo apt-get update

sudo apt-get install \apt-transport-https \ca-certificates \curl \
gnupg \
lsb-releasecurl -fsSL https://download.docker.com/linux/ubuntu/gpg | sudo gpg --dearmor -o/usr/share/keyrings/docker-archive-keyring.gpg

10echo \
"deb [arch=amd64 signed-by=/usr/share/keyrings/docker-archive-keyring.gpg]
https://download.docker.com/linux/ubuntu \$(lsb_release -cs) stable" | sudo tee /etc/apt/sources.list.d/docker.list >/dev/nullsudo apt-get update

sudo apt-get install docker-ce docker-ce-cli containerd.io

sudo apt install docker-compose

sudo service docker startsudo groupadd docker

sudo usermod -aG docker $USER

newgrp docker

At this point you should have a fully operation Docker Engine installed running on Ubuntu under WSL2. You
can check this by trying to run the hello-world image from Docker Hub.

docker run hello-world

One drawback of this approach is that you will need to start the docker service yourself after rebooting or
restarting WSL2. You can do this by running the following command.

sudo service docker start11For making sure Docker is started every time we open the Ubuntu command window, we need to run thenecessary commands in your user startup scripts (.profile). Do it with a check to see if the service is runningfirst, like:sudo service docker status || sudo service docker start

2.4 Operating system requirement
The desired operating system for EPOS Manager is Windows Server 2019with Virtualization enabled, 64 Bit or higher.
EPOS Manager supports Windows Server 2016 (Updated Feb 2018).
Docker Engine supports Windows Server 2019 or higher.
Configuring EPOS Manager with Docker on Windows Server 2016 requires the following setup
Note: 16GB RAM is required.
1. Install "Windows Server 2016 (Updated Feb 2018)"
2. Install Docker Desktop ver 2.0.0 community edition
https://download.docker.com/win/stable/31259/Docker for Windows Installer.exe
When prompted for Containerization and Hyper-V, click yes.

12

3. Installing EPOS Manager
3.1 Prerequisites
The customer has to login to EPOS Manager athttps://enterprise.eposaudio.com by providing cloud Tenant login credentials.

Navigate to Manage Updates layout using “Manage Updates” menu.
To download EPOS Manager,
Go to the tab “Software Updates”. Locate release to be downloaded and click the download
icon in the ‘Action’ column.
Once downloaded, extract the package and it contains files required for the installationof EPOS Manager.
The following files should be available:– ChangeDefaultPartner.ps1– GetResetPasswordURL.ps1– MigrateLocalFolders.ps1– docker-compose-https.yml– docker-compose-http.yml– .env
3.2 Installation steps
3.2.1 SQL Permissions
EPOS Manager uses 3 databases to manage its applications – Web API, Identity, Tenant(Organizations can provide any name for these databases and map these names in the.env file)
EPOS Manager requires that the SQL user provided as part of the .env file has a minimum
permission of db_owner. If the SQL user provided has db_creator access, these databases
would be auto created as part of the installation during docker-compose up. Alternatively,organizations can create these databases upfront and only provide the db_owner accessto the SQL user configured.

13

It is recommended that the below size is allocated for each database at the minimum:– Web API – 5 GB
– Identity – 1 GB
– Tenant – 1 GB
3.2.2 Configuring .env file
EPOS Manager installation can be configured on multiple parameters. The subsequent
sections explain on how the configuration is done in the environment file (.env) available inthe downloaded package. Open the .env in notepad or a suitable editor and the file should
be in the same folder level of the docker-compose files
3.2.2.1 Configuring databases
Identity_ConnectionString - to specify the Identity Database connection string in .env file
UCMP_ConnectionString - to specify the Tenant Database connection string in .env file
WebTool_ConnectionString - to specify the Web API Database connection string in .env fileIf SQL server is running on same server (host.docker.internal alias for local server ip) the
below configuration should be done depending on the type of authentication:
SQL Authentication: “Server=host.docker.internal,1433;Database=< dbname >;uid=< user >;password=< pwd >;”Windows Authentication: “Server=host.docker.internal,1433;Database=< dbname >;Integrated Security=True;”If SQL server is running on a different server specify the IP/hostname of the server depending on the type of authentication:
SQL Authentication: “Server=<IP/hostname>,1433;Database=< dbname >;uid=< user >;password=< pwd >;”Windows Authentication: “Server= <IP/hostname> ,1433;Database= < dbname > ;Integrated
Security=True;”Note: 1433 is the default port of the SQL server. If SQL server is configured to run on adifferent port need to specify the same port here. To find which port SQL server isrunning on you could run the following command in the master database of the SQL
serverxp_readerrorlog 0, 1, N’Server is listening on’
If SQL Server is Azure SQL:
ConnectionString: “Server=< Azure SQL DB Server name >;Database=< dbname >;uid=< user >;password=< pwd >;”14

3.2.2.2 Configuring local storage URL
LocalStorageUrl – this to specify the location where the FW/SW updates will be stored andshared with the EPOS Connect clients.
The storage should be on the same machine where the Docker Desktop/Docker Engine is installed.
As this URL should be accessible by EPOS Connect clients it is recommended that you use an
ip-address/hostname/cname. The default value provided in .env file is
http://localhost:10000/devstoreaccount1
Admin can change the protocol, port, and server name in the LocalStorageUrl.
Note: Port configured in the LocalStorageUrl should be opened through firewall. Changing the port and protocol would require updating the docker-compose files as described in section 3.2.3.
3.2.2.3 Configuring CName
CName – this is to specify the CName by which EPOS Manager is accessible within theorganization.
Default value for CName would be localhost, if the organization has a valid certificate anddomain name then that domain URL could be provided in the CName.
If domain name is not available, it is recommended to provide the hostname / IP address.
3.2.2.4 Configuring Certificate
EPOS Manager can be configured to use secure communication protocol. This requires
the admin to provide the certificate to be used for secure communication and its password. This is covered in section 3.2.3.2.1.

15

3.2.3 Configuring custom ports and secure protocol for EPOS Manager
Configuring the ports is done through the docker-compose file. Docker compose is a toolfor defining and running multi-container docker applications. With docker compose, you
use a YML file to configure your application’s services. Then, with a single command, youcreate and start all the services from your configuration.
In the docker-compose file, the exposed ports are mapped to the internal ports. Inside
docker, the services can communicate by simply specifying URLs as http://< servicename >.
To access the service from outside the docker instance, it must be exposed through one
or more ports.
The downloaded package contains 2 docker compose files:– docker-compose-http– docker-compose-https
3.2.3.1 Configuring EPOS Manager for HTTP
docker-compose-http is configured by default to run EPOS Manager in http and thefollowing ports are used for each of the microservice / functions.
Site NamePort Number

epos_manager_ui

80

epos_manager_webapi

25804

epos_manager_agentgw

8080

epos_manager_identity

25801

epos_manager_api

8082

epos_manager_video

25802

Azurite

10000

If any of the ports needs to be customized, then the following sections of thedocker-compose-http.yml file should be modified accordingly.

16Site Name

References

epos_manager_identity

ASPNETCORE_HTTP_PORT, ports

epos_manager_api

ASPNETCORE_HTTP_PORT, ports
LocalStorageDatabaseUrlsHandlerCnameBackend(port number of the epos_manager_agentgw)
LocalStorageDatabaseUrlsHandlerCnameVideo(port number of the epos_manager_video)VideoDevice_InternalIdentityUrl

epos_manager_webapi(port number of the epos_manager_identity)
ports
WebtoolAPI__StorageConnectionString(BlobEndpoint -> port number of the Azurite)
WebtoolAPI__ResetPasswordLink(port number of the epos_manager_ui)
ports

epos_manager_agentgw

AgentGW__StorageConnectionString(BlobEndpoint -> port number of the Azurite)
ports

epos_manager_ui

WebApiUrl(port number of the epos_manager_webapi)
ASPNETCORE_HTTP_PORT, WebApiCnameUrl(port number of the epos_manager_webapi)
TenantAPI__StorageConnectionString(BlobEndpoint -> port number of the Azurite)

epos_manager_tenant
TenantAPI__ResetPasswordLink(port number of the epos_manager_ui)
TenantAPI__VideoEndPoint(port number of the epos_manager_video)
ASPNETCORE_HTTP_PORT
epos_manager_update

UpdateAPI__StorageConnectionstring(BlobEndpoint -> port number of the Azurite)

Azuriteepos_manager_reportfunctions

messaging.rabbitmq.functions

Ports
AzureWebJobsStorage(BlobEndpoint -> port number of the Azurite)
AzureWebJobsStorage(BlobEndpoint -> port number of the Azurite)

17

Note: HTTP ports configured in the docker-compose-http file should be opened
through firewall.
3.2.3.2 Configuring EPOS Manager for HTTPSSSL (Secure Sockets Layer) certificates are an integral part of securing the sensitive information sent across the internet. Information is encrypted to block any unintended access.
For a more secure connection, the tenant may edit port or configure protocol to HTTPS
for all websites as follows
docker-compose-https is configured by default to run in https and the following ports areused for each of the micro service / functions.
Site NamePort Number

epos_manager_ui

44308

epos_manager_webapi

44335

epos_manager_agentgw

44334

epos_manager_identity

44310

epos_manager_api

44313

epos_manager_video

44319

Azurite

10000

If any of the ports needs to be customized, then the following sections of thedocker-compose-https.yml file should be modified accordingly.

18Site Name

References

epos_manager_identity

ASPNETCORE_HTTPS_PORT, ports

epos_manager_api

ASPNETCORE_HTTPS_PORT, ports
LocalStorageDatabaseUrlsHandlerCnameBackend(port number of the epos_manager_agentgw)
LocalStorageDatabaseUrlsHandlerCnameVideo(port number of the epos_manager_video)VideoDevice_InternalIdentityUrl

epos_manager_webapi(port number of the epos_manager_identity)
ports
WebtoolAPI__StorageConnectionString(BlobEndpoint -> port number of the Azurite)
WebtoolAPI__ResetPasswordLink(port number of the epos_manager_ui)
ports

epos_manager_agentgw

AgentGW__StorageConnectionString(BlobEndpoint -> port number of the Azurite)
ports

epos_manager_ui

WebApiUrl(port number of the epos_manager_webapi)
ASPNETCORE_HTTPS_PORT, WebApiCnameUrl(port number of the epos_manager_webapi)
TenantAPI__StorageConnectionString(BlobEndpoint -> port number of the Azurite)

epos_manager_tenant
TenantAPI__ResetPasswordLink(port number of the epos_manager_ui)
TenantAPI__VideoEndPoint(port number of the epos_manager_video)
ASPNETCORE_HTTPS_PORT
epos_manager_update

UpdateAPI__StorageConnectionstring(BlobEndpoint -> port number of the Azurite)

Azuriteepos_manager_reportfunctions

messaging.rabbitmq.functions

Ports
AzureWebJobsStorage(BlobEndpoint -> port number of the Azurite)
AzureWebJobsStorage(BlobEndpoint -> port number of the Azurite)

19

Note: HTTPS ports configured in the docker-compose-https file should be opened
through firewall.
3.2.3.2.1 Configuring SSL certificate to be used for HTTPS communication
A SSL certificate is required if EPOS Manager needs to be configured for HTTPS communication. Organizations can use existing domain certificates or procure a new one. The certificate should be placed in a folder named “Certs” which must be at the same level as thedocker-compose-https.yml file.
Place the Personal Information Exchange (.pfx) file inside the Certs folder. If the certificate
is protected with a passphrase, then this needs to be set as well. Following certificate details has to be added as part of the .env file
– CertificatePath - /root/ucmpcerts/<certificate_filename>.pfx– CertificatePassword - <certificate_password>
3.2.4 Hosting the EPOS Manager (On-Premises) Server
To host the EPOS Manager (On-Premises) server open powershell and navigate to the folder where the docker
compose files are available and then execute the following command
Starting EPOS Manager– For HTTP: docker-compose -f docker-compose-http.yml up– For HTTPS: docker-compose -f docker-compose-https.yml up
The script will pull the docker container images of EPOS Manager from Docker Hub(https://hub.docker.com/) and start the docker instance.
Stopping EPOS Manager– For HTTP: docker-compose -f docker-compose-http.yml down
– For HTTPS: docker-compose -f docker-compose-https.yml down
The script will stop the docker instance of EPOS Manager.
3.3 Upgrade from EPOS Manager v5.x.x (Exe installers) to v6.1.0 and higher
EPOS Manager v5.0.0 – v6.0.0 is based on Wix installers. EPOS Manager latest versions
are based on docker and need to follow the below steps for upgrade.
3.3.1 Configuring .env file
Follow the steps as described in section 3.2.2 for configuring the .env file. The below databasenames should be used in the connection string so that the same database is referred.
– Identity_ConnectionString – SennComm_Identity– UCMP_ConnectionString - SennComm_Ucmp– WebTool_ConnectionString – Database name configured during the installationof previous EPOS Manager.

20

3.3.2 Configuring custom ports and secure protocol for EPOS Manager
Follow the steps described in section 3.2.3. If HTTP is used in previous installation and no
ports are changed then the default docker-compose-http.yml can be used without any
changes.
3.3.3 Uninstalling EPOS Manager (older version)
To Uninstall EPOS Manager from the system, follow the steps below:
Step 1: Open Control Panel.
Step 2: Select Programs.
Step 3: Click Uninstall a Program from Programs and Features.
Locate the following two files to successfully uninstall the application:– EPOS Manager.
– EPOS Manager API.
Note: When uninstalling the application always uninstall EPOS Manager and then uninstall
EPOS Manager API.
3.3.3.1 Uninstall EPOS Manager
To uninstall EPOS Manager from the system, follow the steps sequentially.
Right click on the “Installed EPOS Manager” and select “Uninstall”. In the Programs andFeatures dialogue box click “Yes”. Click “OK” in the “Uninstall EPOS Manager” UI box. A
progress bar will track the uninstalling of the application.
3.3.3.2 Uninstall EPOS Manager API
To uninstall EPOS Manager API from the system, follow the steps below:
Right click on the Installed EPOS Manager API and select “Uninstall”. In the Programs andFeatures dialogue box click “Yes”. A progress bar will track the uninstalling of the application.
Note: Do not delete manually any folders in the below location until the migration is complete.
[IISInstalledDrive]\inetpub\wwwroot
3.3.4 Hosting the EPOS Manager (On-Premises) Server
Follow the steps described in section 3.2.4.
Note: If there are any changes done to the ports or protocol of epos_manager_webapi
from the previous version, download the latest tenantconfiguration.dat from EPOSManager UI and circulate to all users.
3.3.5 Migrating firmware/software files from WIX to Docker
After hosting EPOS Manager, the firmware / software updates uploaded in the previous
version need to be migrated to the new system.
As part of the downloaded package MigrateLocalFolders.ps1 script will be available. Run
the MigrateLocalFolders.ps1 file using the below command and the files will be copied to
the Azure storage
21

\MigrateLocalFolders.ps1 -FirmwareUpdatesFolderPath “C:\inetpub\wwwroot\UpdateAPI\
FirmwareUpdates” '– SoftwareUpdatesFolderPath “C:\inetpub\wwwroot\UpdateAPI\SoftwareUpdates” '– StandAloneVPsFolderPath “C:\inetpub\wwwroot\UpdateAPI\StandAloneVPs” '– AzuriteUrl http://:10000
Note: The default location of IIS is in root of C:\ drive, but if not, please adjust folder paths
accordingly.
AzuriteUrl should be updated to the one configured in Section 3.3.1.
3.4 Upgrading to future EPOS Manager versions
Download the EPOS Manager package from the cloud.
Navigate to the folder where the existing EPOS Manager docker instance is running.
Stop the existing instance using the below command:– For HTTP: docker-compose -f docker-compose-http.yml down
– For HTTPS: docker-compose -f docker-compose-https.yml down
Configure the environment file and docker compose file from the new package.
Start the new EPOS Manager docker instance using the below command– For HTTP: docker-compose -f docker-compose-http.yml up– For HTTPS: docker-compose -f docker-compose-https.yml up
Note: If there are any changes done to the ports or protocol of epos_manager_webapi
from the previous version, download the latest tenantconfiguration.dat from EPOSManager UI and circulate to all users.
3.5 Offline installation
EPOS Manager docker instance can be installed offline using the below steps. The complete
offline installation needs the images to be uploaded manually to a local Docker repository.
When docker-compose file is pulling the images, it will find them locally and use those, andas such no need for an online connection to Docker Hub.
This needs to be done as below
1. Pull images to intermediate computer’s local Docker repository
2. Save images from local Docker repository to movable file storage
3. Move images to offline server
4. Load images to offline servers Docker repository
5. Install EPOS Manager

22Below diagram illustrates the flow from left to right3.5.1 Download docker images
On an intermediate computer, Docker for Desktop/Docker Engine needs to be installed. Use thedocker-compose files from the package to download the images to local docker repository.
You can use any of the below commands to pull the epos manager docker container images.
– docker-compose -f .\docker-compose-http.yml pull– docker-compose -f .\docker-compose-https.yml pull
Note: Clean up all the existing images from Docker desktop/Docker Engine before pulling new images
3.5.2 Save images to local file storage
The images from a docker repo must be exported to .tar format. This needs to be donewith exporting based on repo reference and tag, to preserve tags. This is important for
docker compose, so there is no need to change the image references.
Open powershell and run the below command to generate the .tar file
docker images ' | ConvertFrom-String ' | select-skip 1 ' | ForEach-Object { ' docker save"$($.P1) : $ ($.P2)"-o'"$($_.P1.Replace('eposaudio/',").Replace('mcr.microsoft.com/azure-storage/',")).tar" '}Once this command is executed the .tar files will be available in the folder from where thecommand was run.
3.5.3 Move files to offline server
The .tar files and the EPOS Manager package downloaded needs to be moved to theoffline server, by using an external hard drive or similar. The .tar files should be placed in
the same folder as the docker-compose files of EPOS Manager.
3.5.4 Load images into offline Docker repository
When the exported images are moved to the offline server, the .tar files of the images
needs to be uploaded into the local Docker repository.
Open powershell and navigate to the folder where the .tar files are available and run thefollowing command to load the images
Get-ChildItem -Path .\ -Filter *.tar -Recurse -File ` | ForEach-Object { docker load --input $_ }3.5.5 Install EPOS Manager
Follow the installation steps from section 3.2 to do the installation of EPOS Manager.
23

4. Getting Started
4.1 Pre-Registration
Once you installed EPOS Manager On-premise, a default partner will be created automatically.
It is recommended to change your default partner details after you install the On-premisesolution first time as below steps. You can always use the partner details to reset your password.
Default Partner details:– Partner Name: Default Partner– PartnerId: 9E8F4402-943A-4D92-8DE2-D29615E68D0D– PartnerKey : bZxBAeK8)vWqDA7x74j!Xf)EqOyiCnJdMjuxEIQ2
To change the default partner details, you can execute the poweshell script
ChangeDefaultPartner.ps1 available in the downloaded package.
The script will ask for the below input parameters:– Identityendpoint: The URL of epos_manager_identity. For example http://localhost:8081– PartnerId: Current PartnerId. If it is the default one, refer to above details.
– PartnerKey: Current PartnerKey. If it is the default one, refer to above details.
– ParnerName: Tenant Admin to enter the new Partner name which you wish to put.
– Ucmpendpoint: The URL of epos_manager_api. For example http://localhost:8082
The output of the script will be the updated Partner name, PartnerId, PartnerKey. Pleasesave these details as it is required to reset the password for Tenant Admin.

24

4.2 Registration
4.2.1 On Premises SignUp
You can sign up on EPOS Manager On-Premise Solution at http://< UI URL >/#/signup
UI URL – the hostname/IP address of the system where the EPOS Manager is installed.
For the signing up in the network, following company information is required:– Company Name
– Tenant Name
– Admin First Name
– Admin Last Name
– Admin Email ID– Region– Country– Time Zone
– Enter Password– Re-enter Password– Show Password
Please read the Licence Agreement carefully. Select the “I agree” option and sign up.
Click Submit button to finish signing up in the on premise environment.
4.2.2 Logging in
Post registration, you can login by using your Email ID as the username and thepassword set during registration.
For connecting to EPOS Manager, following browsers are recommended:– Google Chrome– Microsoft Edge
– Internet Explorer (IE) 11– Mozilla Firefox.
For connecting to EPOS Manager from a Mac OS, Safari browser is recommended.
Login to EPOS Manager at: http://< UI URL >UI URL – the hostname/IP address of the system where the EPOS Manager is installed.
4.2.3 Forgot Password
In case the login password has been forgotten, Tenant Admin can use the powershell
script GetResetPasswordURL.ps1, available in the downloaded package, to generate thereset password URL. A sub admin can alternatively request the Tenant Admin to generate
the Reset Password URL from the Administration view.
The script will ask for the below input parameters:– Identityendpoint: The URL of epos_manager_identity. For example http://local host:8081– PartnerId: Current PartnerId. If it is the default one, refer to section 4.1 for details.
– PartnerKey: Current PartnerKey. If it is the default one, refer to section 4.1 for details.
– Ucmpendpoint: The URL of epos_manager_api. For example http://localhost:8082
25

– Email Id: Email address of the user for whom the password reset is required.
– The output of the script will be the Reset Password URL. Tenant Admin can copy thislink to the browser and reset the password.

4.3 Deployment of the EPOS Connect
The end-user application EPOS Connect must be installed on end-user machines required
to be managed via the EPOS Connect.
EPOS Connect supports the following variants:– EPOS Connect for Win– EPOS Connect for MAC– EPOS Connect for VDI and thin clients
Clients can use any of these variants based on the organizations infrastructure.
4.3.1 Retrieving client files for the first time
Navigate to Manage Updates layout using “Manage Updates” menu. Go to the tab“Software Updates”. In this view, you have the possibility of downloading the latest EPOS
Connect client to your local machine by clicking the download icon.
Once package containing zip file is downloaded, please create a folder where you unpack
the downloaded file. After unpacking the file, folder should now contain the following files
for windows: (version number can vary)
1. EPOSConnect_x.x.x.x.exe
2. PackageInfo.xml
3. product details.txt
4. TenantConfiguration.dat
5. WebToolAgent.xml
6. WebToolAgentReleaseNote.txt
EPOS Connect for Win latest version supports msi installer and can also be downloaded
from the same view. It will contain the following files for Windows:
1. DSEASDK.msi
2. EPOSConnect_x.x.x.x.msi
3. PackageInfo.xml
4. product details.txt
5. TenantConfiguration.dat
6. WebToolAgent.xml
26

7. WebToolAgentReleaseNote.txt
Both msi need to be installed on the machine. EPOS Connect msi needs to be installed for firmware updates
and device configuration. DSEA SDK msi needs to be installed for call control support. The sequence ofinstallation is EPOS Connect MSI followed by DSEA SDK MSI. The custom MSI parameter‘AUTOLAUNCH_ENABLED=0’ has to be set for the DSEA SDK MSI installation.
EPOS Connect for MAC installer can be downloaded following the same steps as for EPOS
Connect for Win.
4.3.2 Installing the client manually for the first time
From the installation folder containing the installation files and the TenantConfiguration.dat
file, run the exe/pkg file. (Administration rights to the machine are required.)
Follow the guide and complete installation.
Start the application by clicking the EPOS Connect shortcut on the desktop – or find it bytyping EPOS Connect in the search program under the Windows menu. On MAC you canstart the application by typing EPOS Connect in the AppFinder and launching it.
Please leave time for the product to initialize and negotiate with the cloud service. Usually
it takes a few minutes, but in a few cases it can take up to 5 minutes.
Log in to your web portal and click on the Manage User menu item. Your user automaticallygets added to the system after the negotiation has taken place.
Mass Deployment
The ability to distribute software to a number of users or computers from a centralized
location has become a requirement for many administrators.
The software is installed without the administrator physically visiting each machine. An
administrator can use system management software to control a user’s environment.
EPOS Connect installation supports silent installation and uninstallation.
Windows:
The command line arguments used for the silent installation of the EPOS Connect application installer is:
EPOSConnect_x.x.x.xxxxx.exe /S /v/qn
For silent uninstallation of the EPOS Connect, run command from the location of installer file:
EPOSConnect_x.x.x.xxxxx.exe -silent –uninstall
For silent uninstallation of SDK, run command in admin mode from the location of installer file:wmic product where name="DSEA SDK" call uninstall /nointeractive
Note: The silent installation does not trigger the application to start, so a restart of the PC
is required to start up application. If an administrator wishes to start the application
after silent installation he should launch the below exe after installation.
32 bit OS: C:\Program Files\EPOS\EPOS Connect\ECLaunch.exe
64 bit OS: C:\Program Files (x86)\EPOS\EPOS Connect\ECLaunch.exe
MAC:
The command line arguments used for silent installation of the EPOS Connect:27

installer -pkg EPOSConnect.pkg -target /For silent removal of EPOS Connect Application it is recommend that you use the uninstall
script as part of EPOS Connect Application. Open the terminal and run the below command:/Library/Application Support/EPOS/EPOS Connect/uninstall.sh
Product Code (Windows Only)
The Product details.txt files contain the Product Code. This is used for detection validation.

4.4 EPOS Manager Layout
The layout of EPOS Manager is divided into sections as described below.
4.4.1 Login information
The login information will give the administrator access to settings, download
the account unique “TenantConfiguration.dat” file, change credentials and terminate thecurrent session.
In the dropdown menu, select the option that corresponds to the required function tobe performed.
Please note that changes made in settings will be applicable for all users
4.4.1.1 Settings (General & Data privacy)
System settings are displayed here.
General settings:“Time Zone Preference” Can be set according to relevant location“Updates End Point address” – Server address to EPOS Manager Update API. Configurable.
“Partner” - choose the partner who will get access to your EPOS Manager tenant for
device management and data insights. Configurable.
Client settings:
Name

Configurable

Description(Able to be changed by Tenant Admin)

Server address of EPOS Manager
Back End Point

API to which the EPOS Connect

Not Configurable

will be connecting toServer address of the Video API
Video End Point

microservice to which

Not Configurable

EPOS Connect for Video will beconnecting toTenant ID

Heart Beat

Tenant specific system ID to

Non Configurable

uniquely identify the tenant.
Interval in seconds for client polling EPOS Manager for updates.
28

Configurable

Name

Update mode

Configurable

Description(Able to be changed by Tenant Admin)

Enable option for Update from

Configurable

file on clients. This is by default

Note: Not applicable fordisabled so end-user will not

EPOS Connect for VDI

have the option to select upgrade

and thin clients as Updatefrom file.

from File is not supported.

Enable option for Allow Downgradeof the firmware. This is by default
Allow Downgrade

disabled as EPOS always

Configurable

recommend to run on the latest
firmware version
Collect Personal Data:
Collect Personal Data is selectedby default as EPOS always
Collect Personal

recommend to collect user

Data

records. Deselecting this option

Configurable

can cause hard delete of all theusers related to that tenant.
If IT admin switches to anonymize
with AD then admin can use AD
Anonymize with AD

groups to push the update andEPOS Connect will not send theuser information to the EPOSManager.

Configurable
Note: Admin can customize
what personal information
can be collected with
Anonymize with AD andAnonymize without AD
options.

If IT admin switches to anonymize
without AD then admin cannot
able to push the updates to AD
Anonymize withoutgroup. EPOS Connect shouldAD

never talk to AD and send the databack to the server. Also, in ‘Manage
User’ section ‘AD Group’ tab will behidden.

29

Configurable

Collect Reports:
By default call statistics settings
is set to collect and agent should
consider the setting of call statistics
for sending data. If the IT admin
unchecks this option, delete all theCall Statistics

table data related to the callConfigurable

activity and stop generating theCall Activity Reports for that tenant. Also, ‘Call Activity’ related data
shown in ‘Dashboard’ section will
be displaying lock-icon.
By default softphone statistics
settings is set to collect and agent
should send the softphone list
to the server after receiving thechanges in the heartbeat. If the IT
Softphoneadmin unchecks this option, delete

Statistics

all softphone related informa-

Configurable

tion from the database and stop
generating the Softphone Reports
for that tenant. Also, ‘Softphone’statistics table will be hidden from‘Dashboard’ section.
Note: Not applicable for EPOS Connect for VDI and thin clients as reports feature is not supported.
Custom message for EPOS Connect end users based on device support status:
Select default or custom message.
Not Support

If Admin selects custom option,

devices

he/she can enter the custom mes-

Configurable

sage up to 250 characters
Select default or custom message.
Conditional

If Admin selects custom option,

Support devices

he/she can enter the custom message up to 250 characters.

30

Configurable

4.4.1.2 Administration
EPOS Manager enables the possibility to create more admin users with different roles andprivileges to manage this application.
Note: Only the administrator created on signup can create more admin users.
4.4.1.2.1 View Admins
The tab ‘View Admins’ is in the main view of the ‘Manage Admin’ layout, showing all theadmins information.
The following details can be found in the view:– Admin Name
– Role– Email ID– Contact– Country– Region– Created On– Created By
You can edit or permanently delete a specific admin from the database using the icon
buttons available in the grid ‘Action’ column.
To create a new admin, click ‘Add Admin’ button available in the ‘Manage Admin’ layout
and fill in the required information
Tenant Admin can generate Reset Password URL for sub admins from the View Admins
Grid by clicking the Reset Password icon in the Action column for the sub admins. Whenclicked on this it will generate the reset password URL and show as pop up. Admin canshare this link to the sub admin to reset the password.
4.4.1.2.2 Add/Edit Admin
To create new admin or update admin, following information is required:– Admin First Name
– Admin Last Name
– Admin Email ID– Admin Contact– Region– Country– Time Zone
– RoleAfter filling in all the required details, click on ‘Add’ button to submit the details. Once details
submitted successfully, Tenant Admin can use the Reset Password URL from View Admins Gridand share it to the sub admin to reset the password. 'Admin Email ID' is not editable in Edit Admin.
Three different roles are supported:– Power User
(Provides full permissions for all the features except access to ‘Administration’ feature)31

– Internal User
(Provides read-only permission for all the features except access to ‘Administration’ feature)– Tenant Admin(Logged-In Tenant details will be displayed in View-Admin grid and Delete action will behidden for the same)
4.4.1.2.3 Transfer Ownership
To transfer the ownership to other admin, click on edit icon of admin to which you want to transfer theownership, then click on 'Transfer Ownership' button.
4.4.1.3 Client config
A Tenant account specific Token (TenantConfiguration.dat) can be downloaded here,
for deploying to end-user installations.
1. The token must be deployed to end-user machines when installing the EPOS Connect.
2. The token ensures that the clients are allowed to connect to the tenant-specific accounton the EPOS Manager system.
3. The token is required for clients to be managed and to receive updates from theIT administrator.
The token (TenantConfiguration.dat) contains Tenant account specific information, ensuring
a secure connection between the end-user application and the tenant-specific account.
Once downloaded, the TenantConfiguration.dat file is encrypted and cannot be read.
1. Backend Endpoint (server address of EPOS Manager API with which theEPOS Connect will communicate)
2. Initial Heartbeat Time (The value set in “Heart Beat” indicates the duration in seconds
after which the EPOS Connect will contact the server and check for available FW
and SW updates).
3. Tenant specific ID
4.4.1.4 Change Password
The administrator can change the account password at any time. Go to the tenant
dropdown menu and select “Change Password”
4.4.1.5 Help
Documentation and user guides for the system can be accessed by selecting “Help”.
4.4.1.6 About
Select “About” to learn about system information.
The following system info will be shown:– Version– Build– Date of the application
4.4.1.7 Logout
To secure account details and eliminate misuse of the system, select Logout after finishingtasks in the system

32

4.4.2 Grid settings
In Grid Settings, the listed column view can be arranged.
A user can customize the field columns by changing the following settings:– Column properties– Display selections– Column display order
The changes made in the grid will be valid only for that specific machine and specificbrowser until that specific browser’s application data is cleared.
4.4.2.1 Row count“Number of rows” per page to be viewed can be set by clicking the dropdown button.
4.4.2.2 Display selections
Including, excluding and order of displayed fields can be set in the grid settings view.
Add to the Selected Column from the Available Column.
Remove from the Selected Column to the Available Column.
Add all fields to the Selected Column from the Available Column.
Remove all fields from the Selected Column to the Available Column.
4.4.2.3 Column display order
The column display order in the Selected Columns box determines the display order in the
final view. Top to bottom order in the list box makes the change in reference to left to rightorder in the display. Once the column selection is highlighted in the Selected
Columns, the column display order can be changed using the following functions.
Moves the selected column up in the list box (left in the final display).
Moves the selected column down in the list box (right in the final display).
To get the default settings, click “Restore Default Settings”.
4.4.3 Search
Use the Search bar to quickly search for a specific attribute in the current view.
4.4.4 Information fields
The information field shows the result of the chosen main menu and associated tabs. The
listed order can be sorted alphabetically and numerically in ascending or descending order.
To change the order of sorting, click on the field name to change the displayed order.
4.4.5 Page navigation
Navigating multiple pages in EPOS Manager is easily accessed at the bottom of thedisplayed view.

33

4.4.6 Application menu
The main menu contains associated selectable tabs, which will display subject specificinformation:– Dashboard– Manage Device– Manage Updates– Manage User
– Configuration– Provision– Meeting Rooms– Reports
The selected menu will always be highlighted.

34

5. Dashboard
Dashboard gives the overall analysis of active devices, version updates, call Activity, Assets,
and Deployments etc.
The dashboard contains the following categories– Active Device– Firmware Version– Software Version– Call Activity– Your Assets– Deployments

5.1 Active Device
This chart gives the information about the total count of active devices to the total
number of devices. On click of Overview button, the site will navigate to the ‘Device’ tab of‘Reports’, selecting ‘Device Overview’ from sub-category.
5.2 Firmware Version
This chart gives the information about the total count of firmware versions up to date to
the total number of firmware versions available. On click of Overview button, the site will
navigate to the ‘Device’ tab of ‘Reports’, selecting ‘Update Overview’ from sub-category.
5.3 Software Version
This chart gives the information about the total count of software versions up to date to
the total number of software versions available. On click of Overview button, the site will
navigate to the ‘User’ tab of ‘Reports’, selecting ‘Client Versions’ from sub-category.
5.4 Call Activity
Call Activity gives the total number of calls and Total call time. On click of Details button,
the site will navigate to the ‘Call Activity’ tab of ‘Reports’, selecting ‘Call Overview’ fromsub-category.
Note: Not Supported by EPOS Connect for VDI and thin clients.

35

5.5 Your Assets
Total Devices: This shows the total number of devices. On click of ‘Total Devices’ count, user
is redirected to “All Devices” tab of “Manage Device” section.
5.5.1 Devices
This section contains the summary of Devices in a tabular view with the following columns.
– Device– Type– Percentage– Quantity
5.5.2 Softphones
This section contains the summary of Softphones in a tabular view with the following
columns.
– Softphone– Type– Percentage– Quantity
Note: Not Supported by EPOS Connect for VDI and thin clients.
The total number of users, Users without devices, Total Admins count is shown at thebottom of the table. On Click of ‘Total Users’ count and ‘Users without Device’, user
is redirected to “Users” tab of “Manage User”. And on click of ‘Total Admins’, user isredirected to ‘View Admins’ tab of ‘Manage Admin’.
5.6 Deployments
This section gives the deployment status of the updates and configurations. The following
details are present in tabular view.
– Type : Download icon indicates update and settings icon indicates configuration– Date– Device– Group– Update Status36

6. Manage user
Manage user menu is for managing users having the client application EPOS Connect
installed on their local machine.
The user are automatically created in the system the first time the EPOS Connect isstarted on the end-user machine.
6.1 Users
For the user to be created in the system, the information FirstName, LastName and Emailaddress needs to be available. This will happen automatically by the client querying the AD.
If this information is not available or empty, the user will be created using the machine loginname as username and email address as a combination of login name and domain name or id
generated by the EPOS Connect client. Information such as Office, Country and City will also
be queried. If no information is available the user information will stay blank.
The Administrator can manually add this information to the user if desired by clicking theedit icon on every user.
User have an option to export the data by clicking on the excel icon on the top right corner.
The users screen view will have the following details– User(User information is the combination of First Name and Last Name)– E-mail– Client Version– Client Type– Host Type
– No of Device(s)(Will have the number of devices associated with the user)– Last seen
– Current User Login– Action(Have options to edit or delete the user)
For much more information, Tenant or IT Admin can click on user name link to view
Detail(s), Device(s) & Machine(s).
The Details tab view contains the following details– First Name
– Last Name
– E-mail– Client Version– Client Type– Last seen
– Country– Office– City– Current User Login
37

The Devices tab view contains the following details– Device Name
– FW Version– Registered User
– Current User
(Gives info if the current user using that device)– Last Seen
The Machines tab view contains the following details– Machine Name
– Operating System– OS Version– Model– System Type– Processor Name
– Client Version– Client Type– LogsOn expanding the ‘Machine Name’, details of the softphone installed in that machine will
be displayed.
Logs for a machine can be initiated by clicking the "Request" button. Request can be cancelled using the"Cancel" button. Logs can be downloaded using the download icon once the logs are available (Logs will beavailable for download within 2 hours of request). If a log is requested for the next time, old logs can be
downloaded until the new logs are available for the download.
6.2 Manual group
When deploying a FW or SW update, this must be done to a group.
(In case just one user is to receive an update, add the user to an empty group)
The Manual Group tab allows the tenant administrator to organize users into groups.
Example: A tenant administrator can choose to create groups for indicating departments,
locations, floors, etc.
For creating a new group, click “Create New Group”.
Select New Group from group type and fill in the following details:– Group name
– Group description– Group Type (Custom/All/Location)– Location (applicable only for Location option)
Select the Custom Users option from the Group Type for enabling the manual selection.
Add relevant users to a group by selecting users enrolled into the system and transfer tothe group member list.

38

To quickly identify a specific user in the system, use the search bar located above theusers list to search for the user to be added to the group.
To remove user(s) from a group, click the “x” icon in the action column inside the groupmember list.
Select the All Users option from the Group Type if you want all users registered in the system toreceive the updates, also users added in the future. Enabling this All Users option will
overrule any other selecting you might have made and will disable the grids for manual selection.
Select the Location option from the Group Type if you want UserGroups based on a dynamic location-based
filter. Location dropdown contains Office, City and Country. When selected the search bar will get enabled.
Use search bar to search and list the location based user(s) in the below user grid.
Once group information and users have been added, click “Create” to save the created group.
You can edit, hide or permanently delete a specific group. To edit the parameters for agroup, click the edit icon.
When a change to group parameters has been performed, click “Save” to apply changes.
6.3 AD group
The AD Group tab allows the tenant administrator to create, view and edit user groups
reflecting the Active Directory (AD) distribution lists used in their organization.
The AD Group created in EPOS Manager can be used by EPOS Connect to determine if theend-user belongs to the Active Directory distribution list or not and make the update orconfiguration available.
The following details can be viewed:– AD group name– Creator– Date and time
You can edit, hide or permanently delete a specific AD group.
To create a new AD group, select the Create AD Group button. Fill in the AD Group Name
(reference name in EPOS Manager and should start with the syntax AD_*) and AD Search String.
Click Add to create the new AD group.
Note: As an example, the below stated information is required to be filled in the“Create AD Group” window to create an AD Group.
AD Group Name: AD_GroupIdentifier
AD Search String: LDAP://LocalDomain/CN=GroupIdentifier,OU=Group,OU=Department,
OU=Organization,OU=Operating region,DC=Root domain,DC=com (AD search string for the
distribution list. You can use the Windows Tool ADExplorer to identify the AD search string
to be used.)
Where
CN = Common name39

OU = Organizational unit Name
DC = Domain component.
To edit an AD Group, click theedit button and make the desired changes for the AD Group Nameand AD Search String.
Click “Save” to apply the changes.
Note: It is not possible to edit an AD Group if there are active deployments using the group.
It is required to stop deployments, edit and then resend the deployment.
Note: EPOS Connect for MAC and EPOS Connect for VDI and thin clients do not support AD Groups.
6.4 Inactive users
It helps to manage the inactive users in the system for a certain span of time period andan option is provided to filter inactive users based on different time period.
Following are the different time periods:– 1 Month– 3 Months (Default)– 6 Months– 1 Year
User have an option to export the data by clicking on the excel icon on the top right corner
Delete option is provided in the layout to delete the users.
6.5 Deleted users
Users deleted from the “Manage User” list will be placed under the “Deleted User” tab.
A tenant administrator can choose to either permanently delete a user from the system, or
to restore the user.
If a user resides in the “Deleted users” list, the EPOS Connect client belonging to the user
will no longer be able to receive updates.
If a user is permanently removed from the “Deleted Users” tab, all user specific information andhistorical data about usage is deleted.
User have an option to export the data by clicking on the excel icon on the top right corner
Select the “Restore User” button to move the user from the deleted users tab list to theUsers tab list and the user will be able to receive updates again.
Select the “Delete User” button to permanently delete the user from the system.

40

7. Manage device
The Manage Device menu is for managing the assets deployed in the organization.
You can view the details by clicking on the particular asset.
7.1 All Devices
The tab “All Devices” is the main view, shows all EPOS devices.
The following details can be found in the view:– Device Name
– Meeting Room
– Vendor– Type– Device ID– FW Version (update available icon/release notes is shown when a new update is available)– Current User
– Last Seen
– Host Name
For even more detailed information about a device, click on the device name and find thefollowing information about the device.
– Device name– Status of device– Type– Device ID– Firmware Version (update available icon/release notes is shown when a new update is available)– First seen
– Last used date
– Last user
– Request Logs (redirects to the user machine details)– Meeting Room (link will navigate to the meeting room view page.)– Country– Office– City– First Contact FW Version– First Contact IP Address– Last Contact IP Addres– Current User Login– Current User Email
Note: Deployment can be done on click of update available icon.
Video devices support single device deployment along with All Devices.
Single Device deployment - Deploys the update to the selected video device.
All Devices deployment - Deploys to all the devices of the selected device type.
Refer (section 8 Manage Update for deploy window options).
The "Configuration" tab in the details page shows list of configuration settings for the device.
41

Click on the edit icon to perform device specific configuration deployment (only for video devices).
Tenant configuration deployment takes priority over the device specific config deployment (based on thelatest deployed time)An

icon will be displayed next to the setting value if there is a difference between the tenant/device

deployed configuration to the configuration of the device. Following actions can be done to sync the values.
1. Connect device to network
2. Wait for the heartbeat (every 2 hours) or sync immediately:
Video app on device - Click 'Device Setting’-‘Device Sync’-‘Sync Now’
Desktop app - Click 'Update overview'-'Check for updates'.
3. Upgrade to the latest firmware.
4. Contact support team.
In the case of conflict, device value will be shown in the tooltip.
The "ConnectedTo" tab in the details page shows which products are connected to each other withan easy way to navigate between the products by clicking the hyperlink of the product in
the connected to list.
Note :
1. Configuration tab will display only if there is any configuration settings avilable for that device.
2. ConnectedTo tab will display only if device is connected to other device.
To Remove Device, select device and click on the “Remove” button, once we click on that a pop-up
information appears and the following details will be displayed:– Status (shows that device is Active or Inactive)– Device Name
– Device ID– Vendor– Description (used to add the reason to remove device)
The removed device can be viewed by clicking the tab “Removed Devices”.
Note: Remove button functionality works same in “Active Devices” and “Inactive Devices” tab.
To change the meeting room, select the devices in the adjacent box of the same row and click on 'Change
Meeting Room' button. Select meeting room from dropdown and click the Save button. To remove themeeting room, select the devices in the adjacent box of the same row and click on 'Change Meeting Room'button. Remove the meeting room and click the Save button.
Note: If you associate a device to a meeting room which is already associated to another meeting room, thenthat device will be disassociated from previous meeting room. One device can associate to one meeting room
at a time.
‘Device Type’ filter is added with a multiselect option and supports the following device types filter– Wireless DECT
– Wired USB
42

– Wireless BT– Speakerphone– Video
By default, 'All' will be applied.
7.2 Active Devices
Active Devices tab shows the details of devices which are active in the system fora certain span of time period and an option is provided to filter active devices
based on different time period.
The view includes the following details:– Device Name
– Meeting Room
– Vendor– Type– Device Id– FW Version– Current User
– Last Seen
– Host Name
Following are the different time periods:– 1 Month– 3 Months (Default)– 6 Months– 1 YearA device can be removed by selecting it from the “Active Devices” list.
7.3 Inactive Devices
It helps to manage the inactive devices in the system for a certain span of time period
and an option is provided to filter inactive devices based on different time period.
The view includes the following details:– Device Name
– Meeting Room
– Vendor– Type– Device ID– FW Version– Current User
– Last Seen – Host Name
Following are the different time periods:– 1 Month– 3 Months (Default)– 6 Months– 1 Year43

A inactive device can be removed by selecting it from the “Inactive devices” list.
7.4 Removed Device
It shows details of all the removed devices.
Devices taken out for maintenance, or discarded can be removed from the system by using
the “Removed devices” tab.
Once a device is removed from the “All Devices”, “Active Devices” and “Inactive Devices” tab, device will be
moved to the “Removed devices” tab.
The view includes the following details:– Device Name
– Meeting Room
– Device ID– Firmware Version– Current User
– Type of the device– Last used time and date
– Reason for removal – Host Name
Select a device which you would like to delete and then click on the “Delete Device” button.

44

8. Manage updates
The “Manage Updates” menu can be used for managing software updates of application andfirmware updates of the assets (headsets) deployed in the organization. You can choose to schedule updates
to take place at specific time of the day. You can choose to deploy a “Mandatory” update to a device, toensure that an important update of that device will be performed mandatorily.
You can choose to deploy a “Silent” update to a device, to ensure that an update happens
silently, without any user interaction or when the user is logged off from the machine, in thedefined Update Window. Silent update is only applicable for firmware updates. After theend date, the “Silent Update” will behave as a mandatory update for the end user.
Note : Silent update is not supported if the machine is in sleep mode or turned off.
All Devices deployment - Deploys to all the devices of the selected device type.
You can select the type of update from the drop down menu.
– You can choose specific user group for the update by clicking on the drop down menu
and selecting the boxes adjacent to the desired user group. ”Select all” will select all theuser groups. ”Deselect all” will clear all the selections in the list. To ease the selection, typethe name of the user group in the search box and perform the desired action.
– For scheduling date and time, click in the box and select date and time as required.
– To select date, click on the specific day in the month of the year.
To return to the date selection, click the calendar button.
– It is possible to download the software or a firmware locally by clicking the download icon.
– To discard any version of the software or firmware, click on the reject button.
In the deploy window:
Device deployment - Device(s): Device(s)-Version.
Software deployment - Application(s): Application(s)-Version.
Deploy To supports following options User Group/All/Single Device
Tooltip
User Group - Deploy to all users in the specified User Group(Only for audio devices)
All (Devices) - Deploy to all registered devices of the selected type
All (Software) - Deploy to all users of the selected application
Single Device - Deploy to a single device(Only for single video device deployment)
Note : The "All" tooltip depends on whether the deployment is being applied to a device oran application (Software).
Select if the release should be mandatory to user(s) or deployed as optional to user(s).
or deployed as silent to user(s). Silent update is only applicable for firmware updates.
Select time schedule for deployment
Select default or custom message (applicable only for mandatory updates). If Admin
selects custom option, he/she can enter the custom message up to 250 characters.
Deploy.

45

8.1 Firmware updates
Under the tab “Firmware Updates” new device-specific firmware releases from EPOS
will be available for deployment in the organization.
To benefit from device firmware improvements and enhanced functionality released via
updates from EPOS, it is highly recommended to keep devices in the organization updated.
User can filter the data using the versions and devices dropdowns.
Versions dropdown has two options– Show Latest: gives the highest Firmware version list.
– Show All: will display all the records
Devices dropdown has two options.
– Show All: will display all firmware version list.
– Connected: will display firmware list related to connected devices.
The following details about the release can be viewed:– Device name of the device to be upgraded– Type of the device which can be firmware– Latest version of the firmware in the device– Release notes by clicking on the associated icon
– Date and time of receiving the update notification– Source from where the update is sent
– Type of build which can be Beta or Production.
From the column “Action” you can deploy, download or delete the software released from
EPOS.
Deploy multiple Firmware updates to multiple user groups/all devices by selecting thecheck box(s) against each Firmware and then click on the Deploy button which is above
the grid and next to versions.
Refer (section 8 Manage Update for deploy window options).
To promote a "BETA build to Production", click on the promote build icon next to beta then the build will bechanged from beta to production.
8.2 Software updates
Under the tab “Software Update” new versions of the end-user software“EPOS Connect” will be available for deployment in your organization.
User can filter the data using the versions dropdown which has two options.
– Show Latest : gives the highest Software version list.
– Show All: will display all the records
The following details can be viewed:– Release notes– Date and time of receiving the update notification.
– Source from where the update has been sent.
From the column “Action,” you can deploy, download or delete the software released from
EPOS. EPOS Connect for Win latest version supports msi installer and can be downloaded.
46

Deploy multiple Software updates to multiple user groups by selecting the check box(s)against each Software and then click on the Deploy button which is above the grid andnext to versions.
Refer (section 8 Manage Update for deploy window options).
Note: When deploying a software update of the client a warning will be presented.
This is because the EPOS Connect software requires administrative rights for
installation. This has the following impact.
For users without administrative rights on their machine, they will be prompted toenter user credentials and password for a user with the right permissions.
For user with administrative rights the user can still be prompted with a “Do you wantallow the following program to make changes to this computer” message box. Thisis default windows behaviour caused by the UAC settings. This can be removed bychanging the UAC settings to never notify, but this is not recommended. The user
has to click yes for the software to install.
The recommended way of updating the software is to use a mass deployment toolsuch as SCCM / Jamf Pro.
To promote a "BETA build to Production", click on the promote build icon next to beta then the build will bechanged from beta to production.
8.3 Upload updates
EPOS will be sending out notifications whenever there is a new firmware or software
release to the Tenant Admin who has signed up for EPOS Manager.
IT admin can download the update from the cloud server and upload it to local EPOSManager so that they are available to be deployed with in the organization.
The Administrator can select radio button for either software or firmware update.
Note: The following three priorities can be selected by the administrator.
– Critical Update– Recommended Update– Minor Update
For software or firmware update select the priority .Click in the box to browse or dragthe file in the box to attach the file. Select Upload to deploy it later.After uploading the package, admin canview the upload status of package in the below grid.Upload status will be Upload Failed(with error
message)/Upload Success/In progress (spinner icon).admin can delete the package and reupload in case of inprogress(spinner) status for a prolonged time.
8.4 Deployment Status
All active deployment jobs are listed in this view.
The following information is presented here:– Job Created : Time stamp the job was created.
47

– Type: The job type. (Currently only Update)– Device: The device, software targeted with this job.
– Group name: The name of the group the update is sent to.
– Version: Version of the software, firmware that was deployed.
– Devices Reached: KPI of the distribution.
– Update success: KPI of update being completed.
– The “Device Reached“ KPI represents:
Color as status is not yet available- It is a background job, it collects the KPI status and display
one of the below status after some time interval.
Color as download success.
Color as download not yet done.
On hovering over the color bar, it shows the number of devices for which the firmware
download was a success or not yet downloaded.
The “Upgrade Status” KPI represents:
Color as status is not yet available- It is a background job, it collects the KPI status and display
one of the below status after some time interval.
Color as upgrade successRed color as upgrade failed
Orange color as upgrade pending.
When clicking the color bar or device link will bring you to the details page.
Note: The KPI information is only rendered after 60 minutes and will therefore only beavailable thereafter.
8.5 Deployment details
The deployment details page gives you more specific information of the actual status.
– Scheduled Time: The schedule time that was given when deployed.
– Update: The name of the device or software and its new version.
– Deploy Group: The name of the group the update is sent to.
– Devices Reached: KPI of the distribution.
– Update success rate: KPI of update being completed.
– Deploy Type: Update type deployed to end-users Mandatory/Optional/Silent– Deployment Start Date: The date from when Silent update is applicable.
– Deployment End Date: The date when Silent update period ends.
– Update Window: Updates will be applied only during this time interval
The “Device reached “ KPI represents:48

Color as status is not yet available- It is a background job, it collects the KPI status and display
one of the below status after some time interval.
Color as download success.
Color as download not yet done.
On hovering over the color bar, it shows the number of devices for which the firmware
download was a success or not yet downloaded.
The “Upgrade Status” KPI represents:
Color as upgrade successColor as upgrade failed
Color as upgrade pending.
“Update Success” tab displays the devices for which deployment succeeded.
“Update failure” tab displays the devices for which deployment failed. (Update wasdownloaded and the update attempt was done)“Update pending” tab displays the devices for which update is pending. Download had been
done but update has not yet started.)
Device not Reached tab displays the devices which have not yet downloaded the update.

49

9. Configuration
EPOS Manager enables the possibility to read the settings of the connected devices
and softphone settings of EPOS Connect.
Using the tool, a user is able to push configurations and lock specific settings on theend users devices by pushing a configuration package.
In the current example we will be pushing a regulatory compliance setting to a group.
The flow is very similar to a firmware update so the prerequisites are the same.
Before the configuration please ensure that the devices are updated with the latest
firmware update.
9.1 Configuration Overview
The configuration overview page is designed to act as a dashboard to view and easily
compare configuration settings. The page lists all devices that are applicable for a
configuration and gather all the settings in one place.
In Configuration overview layout, implemented ‘Device Type’ filter and currently thisfilter supports to filter on below device types– Wireless DECT
– Wired USB– Wireless BT– Speakerphone– EPOS Connect– Video
By default, ‘Wireless DECT’ filter will be applied
In this view all configurable devices are listed and you can do a global search to filter
on either devices, users or deployed configuration package.
The deployed pack column shows if and what configuration package has been pushed
to the specific device.
The version column gives the information about the release versions of the uploaded pack.
Shows the number of configuration parameters available on the product. Clicking it will
open up a view of all the configurations and their value on the product.
If the number shows 0 it means that the device does not support any configuration. Most
likely because the firmware version is not supporting it. Suggestion is to update to latest
firmware.

For comparing a single value, it is possible to click the drop down on the title bar to
select 1 of the available configurations. The grid now changes to only show the selectedconfiguration and value. This provides an easy way to compare many devices quickly justby viewing them.
50

9.2 Device Repository
The Device Repository TAB contains a list of all raw device packages uploaded. These
packages will be read only when uploaded and all values will be empty.
User can filter the data using the versions and devices dropdowns.
Versions dropdown has two options– Show Latest: Will show highest version followed by the latest timestamp of thereceived On / Uploaded On column.
– Show All: will display all the records.
Devices dropdown has two options.
– Show All: will display all device packages.
– Connected: will display packages related to connected devices.
9.2.1 Duplicate configuration package For editing the package and choosing the values of theconfiguration it is required tocreate a copy of the package. This is done by clicking the “Copy” icon on the line,
providing a new pack name and clicking “Save”.
A new package is then added and an “Edit” icon is shown on the line.
9.2.2 Edit configuration package
Once the package is duplicated, it is now editable and a small edit icon will appear.
Configuration repository screenshot highlighting edit icon
Package can now be duplicated again, deployed, edited or deleted.
Clicking the edit button opens the package to allow setting the values.
The values can be selected by opening the drop down. When a selection has been madea graphical representation is shown for the device MMI where available. When selecting avalue and deploying it, the given value will be locked on the end user device and the user
will not be able to change the value themselves, not even by changing the physical switch.
To release the setting again (to enable the user to alter the settings), the blank value
needs to be chosen and the package needs to be redeployed.
The settings can be saved by clicking the “Save” button.
9.2.3 Deployment Configuration
Once package is ready, deploy the package using the deploy icon.
Deploy multiple software/device configuration to multiple user groups by selecting thecheck box(s) against each software/device configuration and then click on the Deploy
button which is above the grid and next to versions.
In the deploy window:
Device Configurations - Device(s): Device(s)-Version.
Software Configurations – Pack Name(s): Pack Name(s)-Version.
51

Deploy To supports following options User Group/All.
Tooltip
User Group - Deploy to all users in the specified User Group(Only for audio devices).
All (Devices) - Deploy to all registered devices of the selected type.
All (Software) - Deploy to all users of the selected package.
Note: The "All" tooltip depends on whether the deployment is being applied to a device oran application (Software).
Deploy.
The configuration will happen silently on the end user device on the next heartbeat.
9.3 Software repository
The Software Configuration TAB contains a list of all raw EPOS Connect softphone
configuration packages uploaded. These packages will be read only when uploaded
and all values will be empty.
User can filter the data using the versions dropdown which has two options.
– Show Latest: Will show the highest version followed by the latest timestamp of thereceived On / Uploaded On column.
– Show All: will display all the records
All grid action use cases like duplicating, editing and deploying the packages are similar tothe ‘Device Repository’ TAB grid action use cases. (Referring to the section 9.2.1 to 9.2.3)
9.4 Upload Configuration
EPOS will be sending out notifications whenever there is a configuration update to the
Tenant Admin who has signed up for EPOS Manager.
IT admin can download the configuration from the cloud server and upload it to local
EPOS Manager so that they are available to be deployed within the organization
The Tenant Administrator can then upload a configuration package as a zip file and the
package will be uploaded.
9.5 Deployment Status
Very similar to the firmware deployment, it is possible to follow the status of theconfiguration package deployment (Referring to the section 8.4).

52

10. Provision
The provision menu is used for provisioning of smart devices with the IT Admin preferred settings
using Quick Connect Codes. You can view the details of Quick Connect Code and Create/Edit
Quick Connect Code.
10.1 Quick Connect Codes
The following details can be found in the view:– Code– Communication App– Quick Connect Name
– Active– Devices Used
– Devices Allowed– Expiry Date
– Date Created
You can edit or permanently delete a specific Quick Connect Code using the icon buttons
available in the ‘Action’ column.
You can even copy QR Code using the copy icon in the ‘Action’ column.
'Active' column in the grid states whether the Quick Connect Code is active or not and can beused to provision devices.
To update Quick Connect Code click on ‘Code’ in the grid or edit icon.
To create a new Quick Connect Code, click on ‘Create Quick Connect Code’ button available in‘Quick Connect Codes’ layout and fill the required information.
10.2 Create/Edit Quick Connect CodeTo create the new Quick Connect Code, the following information is required.
– Quick Connect Name
– Expiry Date
– Number of Devices Allowed– Select Models– Communication App– Language– Timezone– Timeformat– Admin Password– System Web Access Code– Status of System Web Access
After filling the required details click on Create button to create the Quick Connect Code andstays in the same page with details filled and QR code generated.
Cancel button redirects to previous page (to list of Quick Connect Codes).
Users can download QR Code (downloads.png) or Copy QR code.

5311. Meeting Rooms
Tenant admins can create meeting room(s) and associate their devices to the meeting room. You canView/Edit/Remove the details of a meeting room.
The following details can be found in the view:– Meeting Room Name
– Devices Attached - Expand to view the Device Name, FWVersion (update available icon/release notes isshown when a new update is available)– FW Update Available
Sorting is provided on "Meeting Room Name" column and default records will be in ascending alphabet orderof "Meeting Room Name".
Manage Device --> Device details page can be used to associate/disassociate a device to a meeting room.
You can view the associated devices to a particular meeting room in the View Meeting Room page. You can
edit or remove a specific Meeting Room using the icon buttons available in the ‘Action’ column.
Note: Deployment can be done on click of update available icon.
Video devices support single device deployment along with All.
Single Device deployment - Deploys the update to the selected video device.
All Devices deployment - Deploys to all the devices of the selected device type.
Refer (section 8 Manage Update for deploy window options).
11.1 Create Meeting RoomTo create a new Meeting Room, click on ‘Create Meeting Room’ button from 'Meeting Rooms' view page andprovide a name for the meeting room and click on Create button.
11.2 View Meeting Room
To see the details of devices attached to a meeting room, click on meeting room name in Meeting Rooms gridview.
The following details can be found in the 'View Meeting Room':– Status (Active/Inactive)– Device Name
– Device ID– FW Version (update available icon/release notes is shown when a new update is available)– Action
You can navigate to the Manage Device page by using the Manage Device link and associate/disassociate adevice. You can remove the device by clicking on Remove option available under 'Action' column.
User will navigate to device detail page on click of "Device Name" in meeting room view page.
User can see the FW version, Release notes under FW Version column if any update is available.

5412. Reports
Reports offer an in-depth analysis of the existing device conditions in an organization.
The reports have two sub-menus showing the details of the following:– User– Device– Call activity– Softphone
A chart being viewed can be downloaded or printed by clicking theicon shown at the right

top corner of the chart’s interactive region.
To select the desired output format, click the icon and select the relevant option.
The below stated options are available to the tenant:
1. PNG image
2. JPEG image
3. PDF document
4. SVG vector image
Click the legends to show or hide the values in the existing chart.
An active user for a monthly statistics is defined as:“Someone who has used the EPOS Connect at least once during the month”
An active user for daily statistics is defined as:“Someone who has used the EPOS Connect at least once during the day”
Note: All the data for the reports is with reference to the Greenwich Mean Time (GMT).
12.1 User
The total number of active and inactive users will display an index with a standard goal
and help to identify inactive devices. A status summary of deployed EPOS Connect client
software compared to available versions is also available.
12.1.1 User Overview“User overview” will show the daily statistics summary of the total number of active users
in a week.
The pointer can be placed over any section of the day column for the exact key values.
12.1.2 Client versions
The Client share pie chart will show the share of EPOS Connect variants.
The Client version share pie chart shows the version of the EPOS Connect being usedbased on the Client Type filter selected.

55

12.1.3 Monthly Overview
The overview will show the monthly statistics summary of the total number of users andactive users in a year. To view the exact numeric value, position the pointer over any section.
This graph can be used to verify that the installations correspond to the number of users/
employees.
12.2 Device
Evaluating the statistics of the devices used by the end-user reflects the device usage inan organization.
The device menu also provides an overview of the competitor products (including distribution)in the organization.
12.2.1 Device Overview
An overview shows a clear synopsis of the total number of devices (active/inactive) withthe following active devices of the series.
The following active vs. inactive devices under series are shown in the chart.
Wired ED headsets (analog headsets)
Wireless DECT headsets
Wireless BT headsets (Bluetooth products)
Wired USB headsets
Speakerphones
Video
There are different types of devices used by the end-users. “Device overview” help to findout the usability index of the active devices on a daily basis.
– Wired ED headsets (analog headsets)– Wireless DECT headsets– Wireless BT headsets (Bluetooth products)– Wired USB headsets– Speakerphones– Video
The trend of the active devices can be seen on a weekly basis.
12.2.2 Other devices
The “Other Devices” menu shows the usage of EPOS products as well as devices fromcompetitors.
Click on a segment to explode that segment for a better understanding of the comparison.

56

12.2.3 Device adoption
An overview shows a clear synopsis of the total number of devices (active/inactive)
with the following active devices of the series.
The following active vs. inactive devices under series are shown in the chart.
Wired ED headsets (analog headsets)
Wireless DECT headsets
Wireless BT headsets (Bluetooth products)
Wired USB headsets
Speakerphones
Video
The chart identifies the number of devices that have not been connected in threedifferent time ranges. The following selections are available:
Monthly : the chart shows a full calendar month.
Half yearly : the chart shows six calendar months.
Yearly : the chart shows a full calendar year.
We can switch to a detailed view by clicking on any of the device family types.
12.2.4 Headsets per User
This report overview shows the user count based on the number of headsets being used.
12.2.5 Update Overview
The overview will show the percentage of the devices which are having the latest version
to the ones which are yet to be updated. The firmware version approved by the tenant istaken as reference to calculate the percentage.
When clicking the report, the user can view the detailed report for each device model
which shows the count of the devices with different firmware version currently used.
12.3 Call Activity
Evaluating the statistics of the call activity of the end-user reflects the call activity statistics
by the company.
The Call activity menu does an analysis based on the call type and call duration ofsoftphones and devices.
Note: Not Supported by EPOS Connect for VDI and thin clients.

5712.3.1 Call Overview
Call overview gives the analysis about the number of incoming and outgoing calls
attended during the specified period.
Following are the different time period filters can be applied on the chart– Last week: the chart shows the number of calls attended daily basis for the last seven days
– Last Month: the chart shows number of calls attended daily basis for the last month i.e.
last thirty days.
– Monthly: the chart shows the number of calls attended monthly basis for the last one year
– Half Yearly: the chart shows the number of calls attended half yearly basis for the last
one year– Yearly: the chart shows the number of calls attended yearly basis for last one year
By clicking on a specific series/bar in the chart, more details of the call for thecorresponding time period will be displayed in the table view.
The following details can be found in the table view.
– User Name
– Softphone Name
– Softphone Version– Device– Type– Start Time
– End Time– Duration
The user has an option to export the data to an excel sheet by clicking the excel iconpresent on the top right side58

12.3.2 Call Duration – Device
Call duration–Device tab gives the information about the call duration of different devices
during the specified period.
Following are the different time period filters can be applied on the chart– Last week: the chart shows call duration for which each device used on daily basis
for the last seven days
– Last Month: the chart show call duration for which each device used on daily basis
for the last month i.e. last thirty days.
– Monthly: the chart shows call duration for which each device used on monthly basis
for the last one year
– Half Yearly: the chart shows call duration for which each device used on half yearlybasis for the last one year
– Yearly: the chart shows call duration for which each device used on yearly basis forthe last one year
By clicking on a specific item in the chart the drilldown data for the corresponding timeinterval will be displayed in the table where all the details of the call for the different
devices will be displayed
The following details can be found in the table view.
– User Name
– Softphone Name
– Softphone Version– Device– Type– Start Time
– End Time– Duration
The user has an option to export the data in the table to an excel sheet by clicking theexcel icon present on the top right side.

59

12.3.3 Call Duration – Softphone
Call duration–Softphone tab gives the information about the call duration of different
softphones during the specified period.
Following are the different time period filters can be applied on the chart– Last week: the chart shows call duration for which each softphone used on daily basis
for the last seven days
– Last Month: the chart shows call duration for which each softphone used on daily basis
for the last month i.e. last thirty days.
– Monthly: the chart shows call duration for which each softphone used on monthly basis
for the last one year
– Half Yearly: the chart shows call duration for which each softphone used on half yearlybasis for the last one year
– Yearly: the chart shows call duration for which each softphone used on yearly basis forthe last one year
By clicking on a specific item in the chart the drilldown data for the corresponding timeinterval will be displayed in the table where all the details of the call for the different
softphones will be displayed
The following details can be found in the view.
– User Name
– Softphone Name
– Softphone Version– Device– Type– Start Time
– End Time– Duration
The user has an option to export the data in the table to an excel sheet by clicking theexcel icon present on the top right side.
12.4 Softphone
Softphone Adoption overview shows the statistics of the different Softphones usage
spread across the company.
Note: Not Supported by EPOS Connect for VDI and thin clients.
12.4.1 Softphone Adoption
Softphone adoption gives the analysis of the clients using the different softphones ofdifferent brands. This section has three charts.
SOFTPHONE BRAND SHARE: This report gives the information about percentage of total
softphones of different brands.

60

SOFTPHONE SHARE: This report gives the information about the percentage of total
users using different softphones for a given brand.
Filter option is available to change the brand and filter the specific data for the selected
brand.
SOFTPHONE VERSION: The report gives the information about the number of users using
a specific version softphone used.
Filter option is available to change the softphone and filter the specific data for theselected softphone.
By clicking on a specific chart series/bar in the above charts, more details will be displayedin table view.
The following details will be included in the table view.
– User Name
– Softphone– Version– Host Name
– Model– Operating system– OS Version– Platform
Three filter options in the table view, to filter based on Brand, Softphone and Version. The
user has an option to export the filtered data to an excel sheet by clicking the excel iconpresent on the top right side.

61

13. Uninstalling EPOS Manager
To Uninstall EPOS Manager from the system, follow the below steps
1. Stop the EPOS Manager docker instanceFor HTTP: docker-compose -f docker-compose-http.yml down
For HTTPS: docker-compose -f docker-compose-https.yml down
2. Delete the EPOS Manager docker container images from Docker Desktop/Docker Engine.
To delete the docker container images from Docker Desktop
a. Open Docker desktop
b. Go to Imagesc. Click on Clean up button
d. Select all images of eposaudio and click on remove button.
To delete docker container images from Docker Engine, refer to below links
https://docs.docker.com/engine/reference/commandline/container_rm/
https://docs.docker.com/engine/reference/commandline/rmi/

62

Contact information
Support Portal:

Eposaudio.com/enterprise-support

E-mail:Software-help@eposaudio.com

Phone:

Find your local support phone
number and opening hours here below.

ASIA-PACIFIC

DenmarkSpain

T +45 89882841

T +34 911238085

8:00 – 17:00

8:00 – 17:00

China

FinlandSwedenT +86 1057319666

T +358 942450352

T +46 844680895

9:00 – 18:00

8:00 – 17:00

8:00 – 17:00

FranceSwitzerland

T +33 170610386

T +41 315281132

8:00 – 17:00

8:00 – 17:00

India

Germany

United Kingdom

T 1 800 200 3632

T +49 3030808045

T +44 2035144072

9:00 – 18:00

8:00 – 17:00

8:00 – 17:00

Japan

Hungary

T +81 364 068 919

T +36 14088056

9:00 – 18:00

8:00 – 17:00

New Zealand

Iceland

MexicoT +64 (9) 580 0489

T +353 15262572

T +52 5553502401

8:00 – 17:00

8:00 – 17:00

8:00 – 17:00

Singapore

Ireland

T +65 6408 5143

T +353 15262572

9:00 – 18:00

8:00 – 17:00

South Korea

Luxembourg

United States

T +82 1544 1699

T +352 27860234

T 1-800-895-7412

10:00 – 18:00

8:00 – 17:00

8:00 – 17:00

Australia
T +61 2 9910 6700
8:00 – 17:00

Hong Kong S.A.R.,
China
T +85 234128400
9:00 – 18:00

EUROPE
Austria
T +43 720880857
8:00 – 17:00

Netherlands
T +31 20-8080956
8:00 – 17:00

Belgium

RussiaT +32 28080784

T 8800-1008557

8:00 – 17:00

8:00 – 17:00

LATIN AMERICA
Brazil
T +55 1143807556
8:00 – 17:00

NORTH AMERICA
Canada
T 1-800-895-7412
8:00 – 17:00

MIDDLE EAST/AFRICA
United Arab Emirates
T 800 035703844
8:00 – 17:00

63