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

Jitsi Video Conferencing in V70: A Controlled Approach to Privacy

Video conferencing is widely used, but rarely examined in terms of where it runs and who controls the infrastructure behind it. In many cases, video traffic is handled by external systems, introducing dependencies that are often overlooked. This piece explores how integrating Jitsi directly into the PBX brings video into the same environment as voice and communication management, giving organizations clearer boundaries, reduced reliance on third-party platforms, and greater control over how communication is handled.

April 21, 2026

Skills-Based Routing in V70: Match Calls to the Right Agent

Skills-based routing in V70 helps ensure incoming calls are matched with the most qualified available agents based on defined skills, language, and expertise. By combining IVR input with intelligent call distribution, organizations can reduce unnecessary transfers, improve first-contact resolution, and shorten handling time. With V70, skills can be defined directly within the PBX, allowing teams to set thresholds, prioritize expertise, and control how calls are routed across departments, queues, and different operational environments.

April 7, 2026

Snapshots in V70: Capture and Restore Your PBX with Confidence

PBX snapshots in V70 provide a reliable way to capture system state before changes are applied, enabling fast recovery, controlled rollback, and more predictable system management when updating configurations, testing call flows, or operating across multiple tenants. By preserving a point-in-time version of the system, administrators can reduce the risk of disruption, restore services quickly when issues arise, and maintain stability while making ongoing changes in complex communication environments.

March 31, 2026