Tech

How to Interdomain Dialing on the Vodia Phone System

Published on:

July 14, 2023

Vodia gives users the ability to dial other tenants within the system using full NANPA numbers, extensions or extension alias numbers. To access this feature, a multi-tenant license is essential; it empowers you to establish multiple tenants within the system, each resolving to its designated domain. This functionality streamlines communication and fosters an interconnected network within the Vodia Phone System, ensuring efficient and flexible calling across tenants.

Vodia gives you the ability to dial across the phone system to other tenants with a full NANPA number, or with an extension or an alias number for the extension. To use this feature you will need to be running the multi-tenant license; this will enable you to create multi-tenants and have them resolve to that particular domain. For those familiar with the Vodia PBX, here's how to set it up properly.  

doman

Dial Plans 

Vodia uses its dial plan to call outbound - it's usually paired with a SIP trunk but, in this case, we will use the "Loopback" mode”

dialplan

Optional: You could deploy the same dial plan you already have on the system, but you will still need to create the "Loopback" in your dial plan. 

If you want other users to be able to dial across domains, you will need to create the entry in the dial plan; if it's a global dial plan you can just create it there. 

Assuming you already have some entry information in your dial plan, you will need to specify the preference. 

Order of Operation 

Your dial plan has to be clear: do you want to dial another tenant number without leaving the SIP trunk? If so, you will have to define when you want the call to terminate to a SIP trunk. 

In our test, if anyone dials a tenant number, it should go to a local SIP trunk which points to the local IP; in this case it's 127.0.0.1 (see below). 

As you can see, we have created a dummy number on compro.audiomercy.com on extension 4001; in this screenshot extension, 4001 from pbx.audiomercy.com calls number 781-555-6666 on pbx.compro.audiomercy.com.

Try the following:

Create a SIP trunk and rename it. Here are the settings you will need to activate: 

  1. Name to interdomain "keep it simple" ;) 
  2. Type: SIP Gateway
  3. Global Enabled 
  4. Inter-office - Trunk settings set to yes 
  5. Dial plan for outbound calls: here you can choose any dial plan; for now we will need to create a new dial plan, so let's continue building the trunk 

Registration settings 

  1. Under proxy enter 127.0.0.1  
  2. Routing/Redirection as is

Number / Call Identification 

  1. Request: URI "let the system decide" which is the default
  2. From "Based on incoming call" 
  3. To " Same as Request - URI
  4. Remote-Party-ID "Based on incoming call" 
  5. Everything else stays as default
  6. Save

Dial plans

For the dial plan, you can create a new plan or use your existing one 

For the Trunk: use "Try Lookback"; for the pattern use * and pattern * 

You will need to go back into the SIP trunk and choose the new dial plan under the setting "Dial plan for outbound calls"  

Latest Articles

View All

VodiaHub brings click-to-call and call control to every Windows workspace

VodiaHub brings click to call and desktop call control to Windows, making it easier for users to place, answer, manage, and automate calls from the applications they already use every day. With system wide tel: link handling, inbound call screen pops, queue details, and automation support, VodiaHub helps connect the Vodia PBX with Outlook, CRMs, browsers, documents, and other Windows tools. Users can keep working without manually copying phone numbers, opening the user portal, or switching between applications just to handle a call.

July 7, 2026

Desk phones, mobile apps, or both? Choosing the right setup for business calls

Desk phones and mobile apps both have a place in modern business communications. IP desk phones remain a strong choice for receptionists, support teams, customer service agents, and employees who handle a high volume of calls from a fixed location. Mobile apps, on the other hand, give remote, hybrid, and field-based users access to their business extension wherever they work. For many organizations, the best answer is not choosing one over the other, but using both through the same PBX environment so every user has the right calling tool for their role.

July 2, 2026

Vodia Updates PBX REST API Documentation for V70 and Later

Vodia has updated its PBX REST API documentation for V70 and later with a clearer structure, easier navigation, response samples, and an OpenAPI specification. The updated API reference gives service providers, enterprises, partners, and developers a more practical starting point for exploring available API calls, understanding request and response behavior, and building integrations around real PBX workflows, including CRM connectivity, automated provisioning, reporting, analytics, call data, and workflow automation.

June 30, 2026