Cloud Voice App Overview

The Cloud Voice App keeps your users connected with colleagues, partners, and customers from wherever they happen to be. This page orients you to the three pieces you work with as an administrator: the Cloud Voice App server, the client apps your users run, and the events the system can flag through notifications.

Cloud Voice App server

Cloud Voice ships with a built-in Cloud Voice App server. It comes fully configured and ready to pair with the client apps, so there is no server-side setup for you to do.

Note

The server listens on port 8111. This port is fixed and cannot be changed, so client apps always reach the server on 8111. If your network has a firewall between the clients and the server, make sure 8111 is allowed.

To get users up and running, you only need to:

1. Enable Cloud Voice App clients for the users who need them.
2. Send those users their login credentials.

Once they have credentials, users can sign in to their client app and start using the unified communications (UC) features, meaning voice, chat, presence, and related tools in one app.

Cloud Voice App clients

Client types and requirements

Cloud Voice supports three clients: a mobile client, a desktop client, and a web client. The following table lists the minimum requirements for each.

Client	Platform	Requirements
Mobile client	iOS	iOS 11.0 or later
	Android	Android 8.0 or later
Desktop client	Windows	Windows 7 or later; 2 GHz processor (32-bit or 64-bit); 4 GB memory; 300 MB free disk space (all minimums)
	macOS	OS X 10.11 El Capitan or later
Web client	Browser	Google Chrome 87+, Microsoft Edge 87+, or Opera 72+

Note

Each client is obtained differently:

• Mobile client: installed from the Apple App Store (iOS) or Google Play (Android).
• Desktop client: installed from a Windows or macOS installer.
• Web client: no install needed; users open it in one of the supported browsers above.

Each client also has its own setup and user guide you can point users to.

User permissions

By default, every user can open all menus and change every setting in their client app. To limit that, set up permission rules built from two controls:

• Menu Visibility Permission: keeps chosen menus out of a user’s view.
• Operation Permission: keeps chosen settings out of a user’s reach.

Caution

Permission rules apply across every client a user runs (mobile, desktop, and web) at the same time. Hiding a menu or blocking a setting removes it everywhere for that user, not just on one device, so confirm the change is what you intend before saving.

For the full procedure, see Set up user permissions of Cloud Voice App clients.

Login methods

Users can sign in to their client app in more than one way.

• Quick login: Send credentials through a welcome email. The email carries a QR code and a login link, so users can sign in with a single scan or tap. See Send welcome emails for quick login.
• Manual login: For users who never receive the welcome email or cannot reach their mailbox, hand them the login details directly: their extension account’s username and password, plus the server’s network information. Users then enter those details by hand. See Send login information for manual login.

Tip

Quick login is the easiest path for most users: one scan of the QR code or one tap of the link signs them in, with no username or server details to type. Reach for manual login only when the welcome email does not arrive or the user cannot open their mailbox.

Event notifications

Cloud Voice can watch for key Cloud Voice App events. When one occurs, the system records it in the logs and can alert the contacts you designate. The events fall into two groups.

Event	Description
Operations-related events
Web User Login Success	An extension user signed in to the web client successfully.
Web User Login Failed	An extension user’s sign-in to the web client failed.
Cloud Voice App Client Login Failed	An extension user’s sign-in to the mobile or desktop client failed.
Extension User Password Changed	An extension user’s account password was changed.
Security-related events
Web User Blocked Out	The system blocked a source IP (Internet Protocol) address after too many failed sign-in attempts on the web client.
Cloud Voice App User Blocked Out	The system blocked a source IP address after too many failed sign-in attempts on the mobile or desktop client.

You can adjust the severity level for each event, edit the notification email templates, and maintain the list of contacts who receive alerts under System > Event Notification.

Note

The two “Blocked Out” events are an automatic security protection: after repeated failed sign-ins from the same source IP address (the network address a device connects from), the system blocks that address to slow down password-guessing attacks. Every event above is logged whether or not you set up a notification contact, so the log is always your record even when no email goes out.