VMGateClients — install & onboard

Install the app, generate join codes, enroll phones on a network, and manage clients from the portal.

Install the app

Open Client QR Codes under Management. That page shows a QR and download URL for the current stable VMGateClient APK. Share it with installers before pairing — it is separate from join codes, which enroll a device to your tenant.

Copy the URL if QR scanning is inconvenient. If no release is published yet, the page says so — check back after your operator publishes a build.

Day-to-day pairing steps on the phone (USB dongle, enter code, profile) are in the VMGateClient manual.

Join Codes

Join Codes enroll a VMGateClient onto a specific Network. Without a valid code the app cannot attach to your tenant.

Open Join Codes, confirm the correct network is selected in the status strip, then click + Generate Code. In the dialog, pick the network, optional label, Max uses (0 = unlimited), and optional expiry in days (leave blank for no expiry).

Generate and share a code

Codes are network-specific — always generate for the network where the phone should land. After generation, copy the code from the dialog and send it to the installer over a secure channel.

Limit Max uses or set an expiry if the code might leak. The Join Codes table shows usage (count/max or count/∞) and whether each code is still active or expired.

The same physical phone may enroll on more than one network over time (separate join codes per network). Each enrollment appears under VMGateClients when that network is selected.

After pairing — status and control

When the installer enters the code in VMGateClient, the app activates on your network and the device appears under VMGateClients for the selected network. There is no separate “approve” step in the portal — a valid join code completes enrollment.

The Status column shows whether the client can take traffic (for example ready, no_dongle, or off). Day-to-day configuration — network defaults, slot policy, bulk edits, and associated rates — is in chapter 05.

Unauthorize (⋮ menu) stops new calls on that network and revokes overlay access for that enrollment. Use it when a device should stay listed but must not receive traffic.

Remove client is only available when the device has no call history on that network; otherwise use Unauthorize. The portal shows a message if remove is blocked.

Remove, unauthorize, and network cleanup

Before deleting a network, remove or migrate all VMGateClients and join codes on it. When cleaning up a client, unauthorize first if it has ever carried traffic — remove is for devices that never completed billable calls on that network.