Keep platform readiness, activation and number cutover separate
Verizon describes pre-installation testing of its platform before an activation call. During activation, native or test DIDs and message traces are used to verify the ordered service. A successful activation is evidence for that bounded exercise; it does not prove that later ported numbers, every PBX route, emergency identity or continuity path are correct.
Porting transfers a number from another provider, while migration can move an existing Verizon number into Verizon VoIP without the same portability process in some cases. Preserve which process applies, the authorized number list, order and location, activation result, firm date when applicable, port or migration completion, and each post-cutover call separately.
Documented service facts
Reviewed 2026-10-20. 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 activates the ordered service with native or test DIDs before a later port or migration may complete. Preserve the authorized and final number inventory, cutover record, provider attempt, delivered identity, customer-edge receipt and PBX route separately; selected successful tests do not prove every number.
Routing and failover
DocumentedThe online service document describes optional VARRS mirrored capacity on a secondary Verizon SBC HA pair. The rates page separately lists PBX Group Unreachable or Call Forward Unreachable redirection. These mechanisms, customer access diversity and PBX recovery remain separate evidence without a universal trigger or timer.
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 verifiedThe rates page describes simultaneous calling units selected per IP Trunking hub or remote location. Purchased units, active calls, call starts, access bandwidth, SBC resources, PBX channels and redirect capacity remain separate; public material does not prove one account's available end-to-end capacity.
Emergency calling
DocumentedEmergency behavior remains jurisdiction-, service-type-, registered-location- and number-specific. A normal activation or port test does not validate emergency routing, caller identity, registered address, callback path, power or access dependencies; use current terms and the provider-approved procedure.
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
DocumentedThe welcome workflow separates provider pre-install testing, activation with native or test DIDs, later port or migration activity, post-activation changes and support. Preserve the final technical letter, confirmed numbers, traces, customer CPE state, cutover evidence and terminal change status rather than treating an order milestone as a call-path result.
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.
Build from the final technical letter and confirmed number inventory
The welcome kit says final SIP domain, signaling FQDN and addresses, media addresses, DNS address, native or test numbers and an ordered screened number are supplied after Verizon completes configuration. Reserved numbers can change before provisioning is complete. Treat the final implementation record—not an earlier reservation, public example or copied PBX template—as the authority for the handoff.
Native or test numbers must be intentionally handled by the customer CPE, whether routed to a destination or rejected in a controlled way. That responsibility does not identify the right destination for a later ported DID. Keep provider number ownership, delivered identity, PJSIP identification, context, digit normalization and the first loaded Asterisk or FreePBX route as distinct evidence.
Interpret port verification without overclaiming
The current welcome workflow places a port or migration after service activation and asks the customer to make several calls on recently moved numbers. Preserve the actual calls, directions, calling and called identities, timestamps, provider correlation, customer-edge receipt, PBX match, answer and media. A small successful sample does not prove every number in a range or every route condition.
A provider-side completion, number inventory or successful selected call also does not prove that an old carrier route is gone everywhere, that the intended PBX group answered, or that all emergency and callback records are correct. Reconcile one affected number and one unaffected control before changing routing.
Name each continuity mechanism and its scope
The online service document describes VARRS as optional mirrored capacity on a secondary geographically diverse Verizon SBC high-availability pair. The rates page separately lists Redirect to Telephone Number for PBX Group Unreachable or Call Forward Unreachable across a configured PBX or key group. These are not interchangeable: VARRS protects a provider SBC path, while a number-group redirect changes where eligible new calls terminate.
The public material does not establish one universal health probe, SIP-code matrix, retry count, timer, precedence rule, restoration sequence or established-call result. Confirm the ordered option, covered numbers or groups, destinations and effective account configuration before describing recovery.
Follow the selected provider leg through the customer demarcation
The welcome kit places the IP Trunking demarcation according to the ordered and managed equipment and says the technical letter supplies the addresses and ports needed at an existing firewall. A generic Verizon, SIP or endpoint port list is not a substitute for that record.
If no matching INVITE reaches the customer edge, retain the provider order, number and continuity evidence and avoid speculative PBX edits. If it arrives, preserve source, Request-URI, To and asserted identity, then follow the effective PJSIP identify, context, normalization and first loaded route. A provider trace or portal report is correlated evidence, not proof of edge receipt, route selection, SDP agreement or two-way media.
Keep emergency, commercial and laboratory claims bounded
Emergency behavior varies by country, service type, registered location and number identity. The welcome kit says some services or jurisdictions have distinct limitations. Preserve the eligible number, registered address, calling identity, callback path, power and access dependencies, current terms and provider-approved validation without substituting an ordinary port test for emergency proof.
The public pages do not establish one account price, availability result or universal PBX compatibility. Use the dated quote, signed order and current service documents for simultaneous calling units, access, equipment, features, support and continuity. No Verizon account, order, port, trunk, PBX group, redirect, VARRS design, packet, call, media stream, emergency result, price, availability, compatibility 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 — September 2024 edition ↗
- Verizon Voice over IP online service document ↗
- Verizon Voice Over IP rates and charges ↗
Examples require adaptation to your topology. No live PBX or hardware testing is claimed.