Tech

AT&T IP Flexible Reach and the Vodia IOP PBX

Published on:

March 22, 2021

AT&T IP Flexible Reach is a SIP trunking service that provides integrated access for both IP and TDM PBX environments. It consolidates voice and data services, simplifying operations and potentially reducing costs. When paired with the Vodia IOP PBX, this integration allows seamless management of SIP trunks, including features like fax over email or connecting traditional fax devices with an FXS adapter. To configure, you’ll need the IP Flex service with "SIP handoff" for direct SIP call routing. With Vodia's SIP trunk template, setting up AT&T Flexible Reach is streamlined, matching DID numbers to extensions or hunt groups by default, making it ideal for businesses seeking reliability and ease of use.

AT&T IP Flexible Reach is a Session Initiation Protocol (SIP) trunking service that delivers integrated access for IP PBX, TDM PBX or Key System environments. It provides potential total cost benefits through the consolidation of voice and data – one provider, single transport and management options.

You can easily configure these services with the Vodia IOP PBX server and provide dial tone to all your SIP desktop phones. You can connect fax using an FXS SIP device, or let the Vodia IOP PBX deliver the fax straight to your customer via email.

Vodia IOP PBX

When ordering the SIP service, it's important you get the IP Flex service with “SIP handoff” - this means inbound and outbound phone calls will be delivered directly via SIP and not over analog lines or PRI.

Flexible Reach SIP Trunk is now part of the Vodia SIP Trunk template. Once you have configured AT&T,  log in to your Vodia IOP device, navigate to your domain and scroll down to Trunks. Click create and select AT&T. 

Create SIP Template for AT&T

Enter the AT&T’s IP Flexible Reach

  • Name:  AT&T
  • Enter the AT&T’s IP Flexible Reach IP address in the Domain 
  • Enter the AT&T’s IP Flexible Reach DID number

To learn more about how to create a DID for your extension, please review the Vodia management article - https://doc.vodia.com/docs/did-management

DID for extension for AT&T in Vodia

By default, Vodia will send any incoming call to the DID number programmed to its respective extension, hunt group, ring group or IVR account (e.g., Auto-Attendant) and distribute that inbound call to a specific account when the caller presses a digit to make a choice. The Vodia AT&T template does a good job of matching the correct DID number by default, which makes it a great option for integrators looking for an easy, reliable solution.

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