Set up the desktop client of the Easybell app

A Cloud Telefonanlage Pro is required to use the Easybell app for desktops.

At least Windows 10 or macOS 13 Ventura must be installed on the computer.

The installation files are available for download in your Cloud Telephone System Pro (see step 4).

1. add new device

Open your Easybell customer portal and then go to Cloud Telefonanlage.

In the "Devices" section, click on "Add".

2. set up the device

Please make the following selection under Basic settings:

End device type: App Type of app: Desktop client

Then set up outgoing and incoming telephony for the device as usual. You can find more information on this process in "Setting up devices in the Cloud Telefonanlage".

3. generate access data

If all the information is complete, you can click on the "Save and generate access data" button in the "Configure device" section and you will now see the access data for this device.

Attention: These are required in step 5.

4. install software

Download links for the desktop client for Microsoft Windows and Apple macOS appear next to the access data.

Please download the appropriate desktop client for your operating system and then continue with the appropriate step in the instructions.

4.1 Installation under Windows

Before you can start the installation, you must first unpack the file. As a rule, double-clicking on the ZIP file that you have downloaded is sufficient for this. Another click on the contained EXE file starts the installation.

If your operating system does not yet have an archiving program on board, please install one first (e.g. WinRAR or similar).

4.2 Installation under macOS

When you run the downloaded file, it is automatically set up and opened as a temporary drive. Please move the desktop client from there to your programs folder.

To start the app, use Spotlight (CMD space bar) and type in "Easybell". Alternatively, open the Applications folder in the Finder (CMD-SHIFT-A) and start the Easybell app there.

5. set up desktop client

When you start the desktop client for the first time, you will be asked for your access data. You can find these in the Cloud Telefonanlage under "Access data and contact" for the respective device (see step 3). You can also access the web interface of the office desk of your device in the app. For this reason, you will be asked for your cookie preferences at the beginning.

Back

Name	Purpose	Lifetime	Type	Provider
CookieConsent	Saves your consent to using cookies.	2 year	HTML	Website
_pk_id	Used to store a few details about the user such as the unique visitor ID.	13 months	HTML	Matomo
_pk_ses	Short lived cookie used to temporarily store data for the visit.	30 minutes	HTML	Matomo
fe_typo_user	Assigns your browser to a session on the server.	session	HTTP	Website
apcCheckData	Availability Check	24 hours	HTML	Website
order_session	Availability Check	36 hours	HTML	Website

Name	Purpose	Lifetime	Type	Provider
_clck	Persists the Clarity User ID and preferences, unique to that site is attributed to the same user ID.	1 year	HTML	Microsoft Corporation
_clsk	Connects multiple page views by a user into a single Clarity session recording.	1 day	HTML	Microsoft Corporation
CLID	Identifies the first-time Clarity saw this user on any site using Clarity.	1 year	HTML	Microsoft Corporation
ANONCHK	Indicates whether MUID is transferred to ANID, a cookie used for advertising. Clarity doesn't use ANID and so this is always set to 0.	10 minutes	HTML	Microsoft Corporation
MR	Indicates whether to refresh MUID.	7 days	HTML	Microsoft Corporation
MUID	Identifies unique web browsers visiting Microsoft sites. These cookies are used for advertising, site analytics, and other operational purposes.	1 year	HTML	Microsoft Corporation
SM	Used in synchronizing the MUID across Microsoft domains.	session	HTML	Microsoft Corporation
_fbp	Used by Facebook to deliver a series of advertisement products such as real time bidding from third party advertisers	3 months	HTML	Facebook
fr	Ads targeting cookie for Facebook	3 months	HTML	Facebook
AnalyticsSyncHistory	This cookie is set by LinkedIn. Used to store information about the time a sync with the lms_analytics cookie took place for users in the Designated Countries	30 days	HTML	LinkedIn
UserMatchHistory	LinkedIn Ads ID syncing	30 days	HTML	LinkedIn
bcookie	Browser Identifier cookie to uniquely identify devices accessing LinkedIn to detect abuse on the platform. For more information about LinkedIn cookies, please navigate to https://www.linkedin.com/legal/l/cookie-table.	1 year	HTML	LinkedIn
bscookie	Used to remember a user's language setting to ensure LinkedIn.com displays in the language selected by the user in their settings	1 year	HTML	LinkedIn
lang	Used to memorize a user's language setting.	session	HTML	LinkedIn
li_sugr	Used to make a probabilistic match of a user's identity outside the Designated Countries	90 days	HTML	LinkedIn
lidc	To facilitate data center selection.	24 hours	HTML	LinkedIn
_guid	Used to identify a LinkedIn Member for advertising through Google Ads	90 days	HTML	Google
_gcl_au	Used to measure ad and campaign performance and conversion rates for Google ads on a site visited	90 days	HTML	Google
_gcl_aw	Used through Google Ads to understand user interaction with the site and advertising	90 days	HTML	Google
_gcl_dc	Used through Google Campaign Manager and DV 360 to understand user interaction with the site and advertising	90 days	HTML	Google
_ga	Used to distinguish users.	2 years	HTML	Google
_ga_V3PFWQFH0B	Used to persist session state.	2 years	HTML	Google

help center