Keep the enterprise trunk distinct from adjacent products
Verizon's current page describes IP Trunking for a premises or cloud business phone system. The welcome kit also separates IP Trunking and IP Integrated Access, while excluding Business Connection, Virtual Communications Express, contact-center services and UCCaaS from that kit. Microsoft Operator Connect, Verizon Calling with Teams, Business Digital Voice and the older XO Enterprise SIP service have their own service and handoff models.
Record the exact ordered product, country, access, managed-edge role, PBX or cloud platform, service-guide edition and signed schedule before designing the connection. A capability or price from an adjacent Verizon offer is not evidence for enterprise IP Trunking, even when both use SIP or the Verizon voice network.
Documented service facts
Reviewed 2026-10-06. Compare SIP trunk services →
SIP authentication
Not verifiedThe reviewed public product page, welcome kit and service guide do not publish one customer-facing digest credential, mutual-TLS identity or source-address rule for every IP Trunking order. Verizon says configuration data is supplied after its service configuration is complete. Obtain the implementation worksheet and protect credentials and peer addresses; do not infer authentication from use of Verizon access.
SIP registration
Not verifiedThe public welcome kit identifies a standards-based SIP trunk delivered to an IP PBX but does not establish whether every order uses REGISTER, static IP peering or another account-specific method. Preserve the ordered service type, managed-edge or direct handoff, CPE role, peer addresses, transport and refresh behavior from the implementation record.
Inbound delivery
DocumentedVerizon describes IP Trunking as PSTN calling for a premises or cloud business phone system and says it provides or ports telephone numbers. That establishes the service role, not the exact Request-URI, Diversion, P-Asserted-Identity, number format or PBX destination. Capture the delivered identifiers and match policy for the actual order.
Routing and failover
DocumentedVerizon advertises configurable reliability, portal-based reallocation during disaster recovery and service-level options up to 100% availability. The service guide describes VARRS as an optional mirrored-capacity business-continuity arrangement. These claims do not prove that one order includes VARRS, diverse customer access, a tested alternate destination or survival of established calls; obtain the exact schedule and test approved new-call failures.
Number and regional availability
DocumentedThe product page says Verizon provides full in-country PSTN replacement, including emergency-service access, in almost 40 countries and makes that statement subject to availability and local regulation. It does not establish serviceability, number inventory, port eligibility or regulatory approval for a particular address. Use dated order and port results.
Audio codecs
Not verifiedThe reviewed public sources do not publish one universal codec, packetization, DTMF, RTP-addressing or transcoding profile for every IP Trunking access model and calling platform. Obtain the current interface specification and preserve the actual SDP offer, answer, observed RTP and decoded audio for each PBX-facing leg.
T.38 fax
Not verifiedThe product page mentions interoperability with legacy fax machines in a broad portfolio statement, but the reviewed sources do not establish T.38 entitlement, pass-through mode, gateway behavior, page profile or delivery support for the specific IP Trunking order. Validate the intended fax path and report rather than transferring a general interoperability claim.
Signaling and media encryption
Not verifiedVerizon describes network connectivity and security options, but the reviewed public sources do not define one TLS hostname, certificate-validation workflow, SRTP profile, media-encryption requirement or downgrade policy for every customer PBX handoff. Private or provider-managed transport does not itself prove SIP or RTP encryption; inspect each leg under the signed design.
Concurrent calls and call starts
Not verifiedVerizon describes a scalable service and portal changes, while the service guide discusses capacity and message-rate controls. The public sources do not establish one numeric session, burst, calls-per-second or bandwidth limit for every account. Keep purchased sessions, active calls, call starts, PBX channels, SBC resources and access bandwidth as separate quantities.
Emergency calling
DocumentedVerizon says its in-country PSTN replacement includes access to emergency services in almost 40 countries, subject to availability and local regulation. That does not establish a particular location record, caller identity, callback route, nomadic workflow or permitted test number. Obtain the jurisdiction- and order-specific emergency terms and use the provider-approved test process.
Pricing model
Not verifiedThe IP Trunking page directs buyers to sales and does not publish a complete account price. Obtain a dated quote and signed schedule for sessions, usage, numbers, porting, access, managed edge, continuity options, emergency service, support, minimums, taxes, renewal, service levels and cancellation. Do not transfer Business Digital Voice per-line offers to enterprise IP Trunking.
Administration and support
DocumentedVerizon advertises a self-service portal for near-real-time performance and usage reports, service extensions, configuration changes and training. The welcome kit states that final SIP configuration data becomes available after Verizon completes its service setup. Portal visibility, accepted order, active configuration and successful calls remain separate evidence.
SMS and MMS
Not verifiedThe reviewed enterprise IP Trunking sources do not establish SMS or MMS entitlement on trunk numbers, API access, sender registration, throughput, webhook security or price. Do not transfer messaging features from Business Digital Voice, UCCaaS, contact-center or wireless products to a PBX-facing trunk.
Start from the provider-issued implementation record
The welcome kit says Verizon supplies configuration data needed for the customer's VoIP CPE after Verizon completes its own service configuration. Preserve that worksheet, peer addresses, number inventory, customer and provider demarcations, routing responsibility, transport, identity policy, escalation path and acceptance plan. Do not build from a public example or assume a universal REGISTER or static-peer pattern.
Treat portal state, order state, CPE configuration and loaded PBX or SBC state as separate checkpoints. A visible service extension does not prove that the intended SIP object is active, that inbound requests match the correct tenant or that an outbound identity is authorized.
Qualify access and continuity per location
Verizon lists internet, MPLS, Fios, SD-WAN, Secure Cloud Interconnect, LTE, fixed wireless and third-party-carrier access among possible primary or backup choices. Those are orderable models, not proof that one site's routes, addresses, quality policy or failure domains are diverse. Map each location from PBX through LAN, edge, access and provider demarcation.
The product page describes portal reallocation for disaster recovery and reliability options with service levels up to 100% availability; the service guide describes optional VARRS mirrored capacity. Obtain the exact included option, route order, retryable results, alternate destination, restoration method and measurement terms. Test approved new-call failures and keep established-call survival separate.
Leave unpublished interface details unresolved
The reviewed sources do not establish one universal authentication, registration, codec, DTMF, packetization, TLS, SRTP, T.38 or message-rate profile for every order. Obtain the current interface specification. Preserve final signaling, SDP, RTP, media security, fax switchover and decoded results for the exact PBX-facing legs rather than importing a template from Business Digital Voice, Teams, contact center or XO documentation.
The broad interoperability statement includes PBXs, legacy equipment, fax machines and modems, but it is not an acceptance result for a specific device or workflow. A private or managed access path does not by itself prove application-layer encryption or fax delivery.
Turn geographic, emergency and commercial claims into evidence
Verizon says it provides or ports numbers and offers full in-country PSTN replacement, including emergency-service access, in almost 40 countries, subject to availability and local regulation. Confirm the exact service address, number inventory, port eligibility, identity rights, emergency-location record, callback behavior and provider-approved test process for every jurisdiction.
Use the dated quote, signed agreement and current service-guide edition for sessions, minutes, numbers, access, managed equipment, continuity options, emergency service, support, taxes, renewal, service levels and cancellation. The reviewed sources do not establish SMS or MMS on trunk numbers. No account, quote, contract, service address, trunk, number, port, access circuit, managed edge, PBX, SBC, call, media stream, fax, protected session, failover event, emergency workflow, message, availability, price or support response was inspected or tested for this guide.
Sources & applicability
Primary references for the technical details above. Operational examples and planning checklists are VoIP.info editorial guidance.
- Verizon Business IP Trunking Services ↗
- Verizon VoIP Services welcome kit ↗
- Verizon Voice over IP service guide ↗
Examples require adaptation to your topology. No live PBX or hardware testing is claimed.