Networks & ingress

Create VMGate networks, read SIP ingress endpoints, and operate more than one network under one tenant.

What a network is

A Network is an isolated VMGate overlay: its own VMGateClients, join codes, and optional routing context. Customers’ SIP trunks point at a network’s ingress; clients enrolled on that network receive calls routed to it.

Think of a network as a logical site or country pool — not as a carrier name. Customers and trunks are configured separately.

Create a network

Open Networks in the Management group and click + Add network. Enter a display name your operators will recognize. The portal provisions VMGateServer-side resources (overlay, SIP port, server join) and shows the network in the list.

Provisioning can take a minute. If a network stays incomplete, use Finish VMGate network setup or Fix VMGate network from that network’s actions menu.

Your plan caps how many networks you may create. Delete unused networks only after removing all VMGateClients and join codes from them.

SIP ingress IP and port

Your tenant has one public ingress IP. Each network gets its own SIP port on that IP — together they form the network’s SIP ingress (IP:port). That is what your Customers’ switches must dial.

Find the endpoint on the network row in Networks, in the status strip when that network is selected (labelled SIP ingress), or when configuring trunks. Give carriers the full IP:port plus any required tech prefix on the trunk.

Traffic must arrive from source IP addresses you whitelist on the trunk — unknown sources are rejected.

Multiple networks

Use separate networks when you need hard separation — for example different countries, a reseller’s VMGateClients, or test vs production. Each network has its own clients, join codes, and SIP port; routing rules and dialpeers can target that network’s clients.

Concurrent calls still share your tenant-wide port entitlement unless plan features state otherwise.

Switch networks in the portal

When you have more than one network, click the network name in the status strip to switch the selected network. Join Codes, VMGateClients, and other Management views scope to that selection. Always confirm the correct network before generating join codes or reading client lists.