VMGateClient features Cloud 2.5

Field app for VMGate Cloud — not the Classic handset SIP stack. Screenshots on the Cloud overview.

VMGate Cloud handsets run VMGateClient. The app is multi-profile (several VMGate networks per phone), connects to the cloud orchestrator, manages SIM slots, and includes Dongle management (on-device firmware flash), multilingual UI, OTA updates, Incoming GSM modes (including Forward to server for portal Inbound GSM & IVR), and per-profile earnings.

View VMGateClient screenshots

Phone minimum requirements

No root required. VMGateClient is a standard APK from the tenant portal — no bootloader unlock, custom ROM, or system privileges. Install from Management → Client QR Codes in the portal (same source as the VMGateClient manual — Requirements).

The phone must have:

  • Android 13 or newer on an arm64 handset
  • Minimum 8 GB RAM
  • Reliable mobile data or Wi‑Fi for the VMGate network link to VMGateServer
  • One or two active SIM slots with working GSM registration (dual-SIM phones show separate SIM 1 / SIM 2 cards in the app)
  • At least 500 MB free internal storage — VMGateClient and VMGate Audio together use about 200 MB once installed; OTA updates need spare space
  • A USB port that accepts the VMGate USB audio dongle (some models do not support USB accessories — use phones your operator has approved)

Samsung mid-range models (A-series and similar) are commonly deployed. Other Android phones may work but need on-site GSM and audio testing before production. Production audio also requires both VMGateClient and VMGate Audio on the same phone (VMGate Audio is installed on first launch).

For rooted Samsung handset SIP (VMGate Classic 1.5), see Classic phone requirements.

App capabilities

Main screen & dual SIM

Live connection to VMGateServer, per-SIM enable/disable, outbound/inbound channel status, and last-call history on field handsets.

Multiple profiles per handset

Store more than one VMGate network on the same phone; mark one profile Active and switch without reinstalling.

App language & OTA updates

Seven app languages (independent from the phone OS), Check for updates for VMGateClient and VMGate Audio, and field diagnostics.

Inbound GSM & IVR

Forward to server for portal IVR and Customer SIP — or use on-device reject / prepared audio. See handset Incoming GSM settings.

VMGate Dongle Manager

Flash and maintain the VMGate USB audio dongle from the handset — guided port selection and firmware update on the phone.

Per-profile earnings

Earned, To be paid, and Paid by range; totals authored on VMGateServer, read-only in the app.

Incoming GSM on the handset

When a GSM call rings the handset, VMGateClient can reject the caller, play prepared audio from a folder after a short ring, or Forward to server so portal Inbound GSM & IVR runs menus and forward-to-switch. Screenshot: Incoming GSM calls on the Cloud overview.

  • Reject all — leave inbound closed when you are not using portal inbound yet.
  • Prepared audio — on-device WAV folder; Prepare files converts and caches on the phone.
  • Forward to server — required for portal IVR / Forward to Customer SIP.
  • Max duration / Reload — on-device prepared-audio controls.