VMGateClients — manage & policy

Configure how enrolled phones behave on the GSM side — network defaults, per-client policy, bulk edits, and payout rate links.

After a device joins with a join code (chapter 04), use this chapter for day-to-day operator configuration. Routing targets (chapter 08) decide which clients may take traffic; this chapter controls how each SIM slot dials, idles, rings, and caps usage.

Network defaults

Every network can define a template policy for new enrollments. Open Networks, find the network, open the ⋮ menu, and choose Edit defaults.

The defaults page shows one card per SIM slot position on that network. Each card uses the same policy fields as a live client slot (see Slot policy below). Click Edit policy on a card, change values, and save.

Important: defaults apply only when a VMGateClient first joins that network. Changing defaults later does not rewrite policy on clients already enrolled. Set defaults before bulk onboarding; use bulk edit or per-slot edits to change existing devices.

Configure defaults on each network before generating join codes (chapter 04). Networks and ingress are covered in chapter 03.

VMGateClients list

Open Management → VMGateClients. Select the correct Network in the status strip — the table is scoped to that network only.

Columns:

Device — friendly name and VMGate node id.
Owner — reseller or direct owner when attributed.
Network — network name and overlay IP.
Status — whether the client can take traffic (for example ready, no_dongle, or off).
Slots — ready vs active SIM summary.
Balance, Calls, Last Seen — billing and connectivity at a glance.

Use the ⋮ menu on each row for Details, Associated rates, Unauthorize, and Remove client (lifecycle actions are also in chapter 04).

Bulk edit policy

Above the table, use row checkboxes or the master checkbox to select clients. The scope dropdown chooses All on this page or All in this network. The counter shows how many clients are selected.

Click Edit policy to open one form applied to every SIM slot on every selected client. Fields you leave unchanged (or marked mixed when selected slots disagree) stay as-is on each slot. Confirm before save — the dialog shows how many clients and slots will be updated.

For daily minutes and daily attempts, fill both min and max or clear both; one bound without the other is rejected. Idle min and max are both required when you set an idle range (1–3600 seconds).

Bulk edit is the fastest way to roll out cap or dial-policy changes across a fleet on one network after you adjust network defaults for future enrollments only.

Client detail page

From the list, ⋮ → Details opens the full client view. The header shows device identity, network, cooldown state, and a Timezone selector — pick the IANA timezone used for daily and monthly counters on this client (saves immediately).

Below the header, one card per SIM slot shows live counters and current policy:

Cooldown, idle range, ring timeout, provisional SIP response, dial policy, country code strip.
Daily attempts; daily minutes usage as Real seconds today vs the day’s drawn cap (min/max entered in minutes).
Monthly and package usage as Real seconds this month / Real seconds this package vs caps entered in minutes; package renewal day.

Each slot card has Edit policy for that slot only, plus Reset daily, Reset monthly, and Reset package when you need to clear counters and re-draw caps without changing the underlying limits.

Slot policy

Slot policy is edited from network defaults, bulk edit, or a slot card on the detail page. Sections:

Daily caps (random per day)

Set min and max for Daily minutes and Daily attempts. Each day VMGateServer picks a random cap inside the range for that slot. Leave a bound empty for no cap on that side — but min/max pairs must be consistent (both set or both empty).

Monthly and package caps

In Edit policy, enter Monthly cap and Package cap in minutes (same unit as daily minutes min/max). On the detail page, usage is shown as real seconds used against that cap — for example Real seconds this month and Real seconds this package.

Monthly cap applies across the calendar month in the slot’s timezone. Package cap applies across the current package period; set Renewal day (1–31) for when the period rolls. Empty fields mean no cap.

Idle range (per call)

After a call ends, VMGateServer waits a random idle period between Min and Max seconds before offering the slot again. Both bounds are required when configuring idle (1–3600 sec).

Dial policy (to VMGateClient)

Applied on the cloud before the handset dials GSM:

Country code to strip — digits only, no +. Required when using a local dial format.
Dial policy — Pass through, Leading +, Local with leading 0, or Local without leading 0.

Match dial policy to how numbers arrive from your carriers and how the SIM expects local dialling.

Ring and provisional response

Ring timeout is how many seconds VMGateServer waits for the VMGateClient to report GSM ringing after it places the mobile dial. Until ringing is detected, the ingress caller may see only 100 Trying — no 180 or 183 yet.

If GSM ringing is not detected within the configured timeout, VMGateServer ends the attempt and the ingress SIP call is rejected with 503 Service Unavailable.

Provisional response applies only after GSM ringing is confirmed. Choose 180 Ringing (signaling only — caller hears local ringback) or 183 Session Progress (early media toward ingress while the mobile rings).

Associated rates

VMGateClient-scoped rate plans define operator payout per destination prefix. From the list, ⋮ → Associated rates to view or remove plans linked to that device.

You can also associate from Configuration → Rates when creating a VMGateClient-scoped plan (chapter 10). Keep payout plans aligned with Customer trunk rates and reseller decks so CDR and billing reports reconcile.

Chapter 04 — install, join codes, unauthorize, remove.
Chapter 03 — create networks and pick the status-strip network scope.
Chapter 08 — routing targets that send calls to clients and slots.
Chapter 10 — rate plan scopes and destination tables.