Start with the ordered access and interface
AT&T says IP Flexible Reach connects through AT&T Dedicated Internet or AT&T VPN and carries calls on its MPLS network rather than the public internet. Record the exact access service, demarcation, managed or customer equipment, signaling and media peers, routes, quality-of-service policy and responsibility boundary from the current implementation package.
A private or managed network path does not by itself establish SIP authentication, registration mode, TLS, certificate validation or SRTP. The reviewed public pages do not publish a complete selected-interface profile, so preserve the provider-issued configuration and the loaded PBX or SBC state before changing either side.
Documented service facts
Reviewed 2026-10-07. 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
DocumentedAT&T describes calling plans that support inbound and outbound calling, local and long-distance calling, virtual telephone numbers and use with existing premises equipment. Those statements do not establish an account's assigned inventory, port state, Request-URI, asserted identity or normalization. Retain the order, number record and matched PBX destination for authorized acceptance calls.
Routing and failover
DocumentedAT&T's business-continuity page lists call forwarding to other locations as an IP Flexible Reach use, and the product page describes branch-office extensions. Neither statement defines automatic trigger, retry, customer-access diversity, restoration order or established-call outcome for one design. Bind continuity to the ordered feature set and a provider-approved new-call failure exercise.
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
DocumentedAT&T says concurrent call channels can be increased or decreased and describes the service for six or more concurrent calls. Its product FAQ says the service does not impose a limit on calls originated per second, but that statement does not remove ordered channels, access bandwidth, PBX, SBC, destination or abuse-control limits. Use the dated order and an approved load plan for numeric and observed behavior.
Emergency calling
DocumentedAT&T's implementation centre states that customer equipment reviews are not a warranty that the equipment or software will complete 911 or E911 calls and assigns the customer responsibility for ensuring operation with its vendor. Preserve the registered address, calling identity, callback path, power and access dependencies, written account terms and provider-approved validation procedure; maintain an alternative calling method.
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
DocumentedAT&T advertises web performance and call-detail reporting plus e-ordering. Its support pages list Business Center workflows, IP Flexible Reach repair, installation and administrator support contacts. Preserve portal roles, named escalation, purchased support terms, ticket evidence, maintenance notices and the division of responsibility among AT&T, the access service and customer equipment.
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 channels, call starts and access capacity separate
AT&T advertises adjustable concurrent call channels and positions the service for six or more concurrent calls. The product FAQ also says there is no provider limit on calls originated per second. That statement does not turn channels, active calls, attempts per second, bursts, access bandwidth, PBX and SBC resources and destination controls into one capacity figure.
Use the dated order for entitlements and a provider-approved load plan for observed behavior. AT&T's Class of Service and bandwidth-management descriptions are design inputs, not measured quality or availability for an uninspected deployment.
Trace number delivery and continuity separately
AT&T describes inbound and outbound calling, local and long-distance service, international calling, virtual telephone numbers, branch-office extensions and call forwarding to other locations. Each remains subject to the chosen plan, number inventory, port state, dial plan, asserted identity, PBX route and regulatory eligibility.
For continuity, document the ordered forwarding or routing feature, trigger, retry, destination, customer-access dependencies, restoration order and established-call expectation. A portfolio or continuity-page capability is not evidence that a particular account is configured or that a failure exercise passed.
Treat 911 and E911 as a complete workflow
AT&T's implementation centre explicitly says its review of customer equipment or software is not a warranty that 911 or E911 calls will complete and assigns the customer responsibility for ensuring proper operation with the equipment vendor. Keep the service address, calling identity, callback number, PBX route, access and power dependencies and site procedures in one controlled record.
Use only the provider-approved validation procedure; do not place an uncoordinated emergency call. Maintain an independently powered alternative method and do not infer location delivery or successful completion from ordinary inbound or outbound calling.
Accept media, operations and commercial terms independently
Obtain the current codec, packetization, DTMF, fax, protection and early-media profile from the implementation package and preserve offer-answer and packet evidence for each required workflow. Public Class of Service or network-carriage language does not supply those interface details.
Bind portal reports, e-ordering, administrator roles, repair and installation contacts, maintenance handling, channels, calling plans, usage, numbers, access, managed equipment, tax and term to dated account records. No AT&T IP Flexible Reach service, path, capability, price, support result or call was tested for this record.
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 ↗
Examples require adaptation to your topology. No live PBX or hardware testing is claimed.