Start with the ordered access and dated implementation record
AT&T currently presents IP Flexible Reach as SIP trunking for existing premises telephony equipment over AT&T Dedicated Internet or AT&T Virtual Private Network access. The product page also describes branch-office trunk sharing, virtual telephone numbers, adjustable concurrent-call channels, reporting and call-detail records. Those portfolio statements do not identify one account's signaling peers, authentication, delivered number format or enabled portal controls.
Preserve the signed order, Welcome Letter, enterprise and group identifiers, access service, implementation worksheet, PBX or SBC handoff, portal role and change ticket. The implementation centre says configuration begins after contract signature and transfers to maintenance after test and turn-up; neither a product label nor portal visibility proves an accepted call path.
Documented service facts
Reviewed 2026-10-20. Compare SIP trunk services →
SIP authentication
Not verifiedThe reviewed public AT&T pages do not define the selected trunk's authentication mode, SIP realm, credential ownership, source-address controls or mutual-authentication behavior. Preserve the signed order, implementation record, provider-issued interface profile and observed challenge or source validation without exposing secrets.
SIP registration
Not verifiedThe public product and implementation pages do not establish whether a selected design registers, uses static peers or combines mechanisms. Do not infer a registrar from the SIP-trunk label. Record the ordered signaling peers, transport, Contact behavior, expiry and refresh policy, qualification and source-address requirements from the implementation package and loaded PBX or SBC state.
Inbound delivery
DocumentedA group contains assigned numbers and users; a group trunk group is the path between AT&T IP Flexible Reach and the PBX. A trunk call routing scheme can bundle multiple group trunk groups. Preserve group and number inventory, scheme membership, provider-selected group trunk group, customer-edge receipt and PBX route separately.
Routing and failover
DocumentedThe dated administrator guide documents Linear, Round Robin, % Allocation and Most Idle routing plus separate Unreachable Destination and Forward Always controls. Preserve effective account configuration and observed new-call legs without inventing a universal probe, SIP-code matrix, timer, precedence rule, restoration sequence or established-call result.
Number and regional availability
DocumentedAT&T describes local, long-distance and international calling and virtual telephone numbers for local visibility. Public portfolio language is not proof that a service address, number, portability request or destination is eligible. Preserve dated serviceability, number-inventory, port and regulatory responses for the exact requirement.
Audio codecs and DTMF
Not verifiedThe reviewed public pages describe business-grade voice, AT&T network carriage, Class of Service and deployment bandwidth management but do not publish a complete current codec, packetization, DTMF, early-media or transcoding profile for the selected interface. Obtain the provider-issued profile and retain both SDP bodies, negotiated payload mapping and decoded digit evidence.
T.38 fax
Not verifiedThe reviewed first-party pages do not establish T.38 or audio-fax entitlement, direction, switchover, redundancy, gateway compatibility or page limits for IP Flexible Reach. Treat fax as a separate ordered and accepted workflow using the current implementation record.
Signaling and media encryption
Not verifiedAT&T describes calls carried on its MPLS network rather than the public internet, while access requires AT&T Dedicated Internet or AT&T VPN. Network placement is not proof of SIP TLS, certificate validation, SRTP, media-key negotiation or protection across every downstream leg. Record the ordered transport and preserve handshake and SDP evidence for the actual path.
Concurrent calls and call starts
DocumentedThe current product page describes adjustable concurrent-call channels and no AT&T service limit on originated calls per second; the dated portal guide separately exposes maximum, incoming, outgoing and burst values per group trunk group. These statements do not remove ordered, access, destination, PBX, SBC or abuse-control limits.
Emergency calling
DocumentedAT&T's implementation centre assigns the customer responsibility for ensuring its equipment and software operate correctly for 911/E911. Preserve eligible number, registered location, calling identity, callback path, power and access dependencies, written terms and the provider-approved validation procedure.
Pricing model
DocumentedAT&T says customers can change concurrent call channels and pay for the lines they need, with optional calling plans and on-net VoIP-to-VoIP calls described separately. No complete public account price was found. Use a dated quote and bill for access, channels, usage, numbers, ports, features, managed equipment, support, taxes, term, renewal and cancellation.
Administration and support
DocumentedThe dated guide assigns trunk-call-routing management to Enterprise Administrators and may give Group Administrators View Only or Hidden scheme access. Preserve enterprise, group, group trunk group and scheme identifiers, portal role, inventory or call-detail reports, change ticket and current provider workflow; dated screens are not a universal current interface.
SMS and MMS
Not verifiedThe reviewed IP Flexible Reach pages do not establish SMS or MMS entitlement on trunk numbers, sender registration, API or portal access, throughput, webhook security, retention or price. Treat messaging as a separately ordered service and workflow rather than an implied property of SIP trunking or virtual telephone numbers.
Keep groups, assigned numbers and group trunk groups distinct
The 2019 Group Administrator Guide describes a group as a location-scoped object with assigned phone numbers and users. A group trunk group is the path between AT&T IP Flexible Reach and the organization's PBX, with maximum, incoming and outgoing concurrent-call values. A trunk call routing scheme can bundle multiple group trunk groups and select among them.
A number in a group, membership in a routing scheme, a provider-selected group trunk group, receipt at the customer edge and a PBX route match are separate evidence. Trace one authorized number through those states before changing Asterisk or FreePBX.
Name the routing algorithm before interpreting distribution
The dated guide documents four routing algorithms. Linear follows an ordered list and advances when a group trunk group is unavailable or at capacity. Round Robin alternates across group trunk groups. % Allocation distributes according to configured percentages and redistributes around unavailable or full members. Most Idle counts active calls and selects the least-used member.
These are selection policies, not proof of a particular call. Preserve the scheme name, algorithm, member set, order or percentages, concurrent-call state and every observed provider leg. One call cannot prove a percentage distribution, and a later PBX answer does not establish why the provider selected that path.
Separate scheme selection from forwarding and unreachable controls
The Group Trunk Group profile documented in 2019 includes concurrent-call settings, an Unreachable Destination action and timer, and a Forward Always action. Those controls are different from a multi-member routing scheme. A call can therefore follow a scheme member, a configured unreachable action or an unconditional forward for different reasons.
Do not invent a universal SIP response-code matrix, detection method, timer, retry count, precedence rule, restoration sequence or established-call outcome. Preserve the exact effective controls, provider timestamp and call identifier, then correlate the provider attempt with customer-edge receipt and PBX handling.
Treat access, capacity, reporting and media as separate evidence
AT&T currently says the service uses ADI or AVPN, supports adjustable concurrent-call channels and does not impose an origination calls-per-second limit. The dated guide separately exposes maximum, incoming, outgoing and burst values for a group trunk group. These statements do not remove account, access-bandwidth, destination, PBX, SBC, abuse-control or ordered-capacity limits.
Class of Service, portal reports and call-detail records remain correlated evidence rather than proof of packet treatment, customer-edge receipt, route choice or two-way media. Retain both SDP bodies, RTP endpoints and decoded media for authorized representative calls.
Apply permissions, continuity and emergency boundaries
The dated guide says an Enterprise Administrator manages trunk call routing schemes, while a Group Administrator may have View Only or Hidden access. Missing edit controls can therefore be a role boundary rather than a service defect. AT&T's current 2026 premises-versus-cloud article lists trunk-to-trunk failover and call preservation as features, but that summary does not prove one order's enabled design, trigger, access diversity or established-call result.
The implementation centre assigns customers responsibility for verifying 911 and E911 operation with their equipment vendor. Preserve number, registered location, calling identity, callback, access and provider-approved validation separately. Correct only the first proven divergence and keep rollback evidence; no account, route, call or emergency result was tested for this guide.
Sources & applicability
Primary references for the technical details above. Operational examples and planning checklists are VoIP.info editorial guidance.
- AT&T IP Flexible Reach product page ↗
- AT&T Business Voice and VoIP portfolio ↗
- AT&T: What is IP Flexible Reach? ↗
- AT&T IP Flexible Reach implementation centre ↗
- AT&T Business support contacts ↗
- AT&T Business Center support ↗
- AT&T business-continuity resources ↗
- AT&T IP Flexible Reach Group Administrator Guide ↗
- AT&T IP Flexible Reach product brief ↗
- AT&T cloud-based versus premises phone systems ↗
Examples require adaptation to your topology. No live PBX or hardware testing is claimed.