Dialpeers

Link a Customer’s ingress trunk to routing rules so inbound SIP is handled end-to-end.

What dialpeers do

A dialpeer is the ingress wiring between your tenant and a routing rule. It ties together:

• Origin customer — the Customer whose switch sent the call.
• SIP trunk (ingress) — which trunk on that Customer received the INVITE.
• Routing rule — which outbound rule (prefix + VMGateClient targets) may be used for that edge.

When SIP hits VMGateServer, only routing rules reachable through an active dialpeer for that Customer and trunk are considered. Billing for the leg still uses the trunk’s rate plan, even when routing targets span multiple networks.

How calls pick a rule

You may create several dialpeers for the same origin customer and trunk, each pointing at a different routing rule (for example one rule for prefix 374 and another for 39).

VMGateServer compares the called number (after tech prefix is stripped) to each linked rule’s destination prefix and picks the longest matching prefix. If no dialpeer exists for that Customer and trunk, or no linked rule matches the destination, the call is rejected with no route.

Routing rules may optionally be scoped to one SIP trunk (chapter 08); dialpeers always specify a concrete trunk.

Add a dialpeer

Open Dialpeers and click + Add dialpeer. You need at least one Customer with a trunk (chapter 06) and at least one routing rule with targets (chapter 08).

In Add dialpeer, enter a Display name, select Origin customer (retail), then choose SIP trunk (ingress) — the trunk list appears only after you pick the Customer. Select the Routing rule (shown as prefix and label, for example 374 — Armenia or * (any)). Click Create.

You cannot duplicate the same origin customer, routing rule, and trunk combination; create a separate dialpeer per rule you want on that trunk.

Origin customer

Origin customer is the same Customer record you manage under Customers — the party whose carrier switch sends SIP to your ingress. The label marks traffic direction (call came from this Customer); there is no separate origin entity in the database.

Choose the Customer first; the trunk dropdown then lists only that Customer’s trunks.

Manage dialpeers

The Dialpeers table shows name, origin customer, routing rule (prefix and label), trunk, and status. Use the ⋮ menu to Edit or Remove.

Edit can change the display name, origin customer, trunk, routing rule, and whether the dialpeer is active. Remove deletes only the dialpeer row — Customers and routing rules are unchanged.

After carrier, prefix, or trunk changes, update dialpeers and routing rules together and place a test call.