Hosted SIP as the Foundation of Verizon Business Voice
Zero-click snippet. Hosted SIP moves call-control infrastructure from customer-premises PBX hardware into the Verizon Business core. Voice runs as packet data on the Fios, DIA or fixed-wireless 5G underlay, with softphone, desk-phone and managed-gateway endpoints unified under one SIP trunk.
Hosted SIP is the replacement architecture for nearly every customer-premises PBX deployment across the Verizon Business customer base. Call control, voicemail, auto-attendant, hunt groups, call recording and conference bridging live in the carrier core rather than on rack-mounted PBX hardware in a customer wiring closet. Voice traffic rides as packet data on whatever internet underlay the customer site uses — most commonly Verizon Fios business fiber, dedicated internet access or fixed-wireless 5G Business Internet. Quality-of-service tagging on the SD-WAN edge protects voice traffic from contention with bulk workloads like backup and file sync.
The migration path from legacy PBX to hosted SIP is well-trodden. Existing phone numbers port to the Verizon Business side through local-number-portability (LNP) with a typical ten-business-day port window; existing hunt groups, auto-attendant menus and voicemail-to-email configurations are translated and provisioned against the hosted trunk; existing desk phones are either repurposed (if compatible SIP firmware is available) or replaced with managed units. Users who prefer a softphone client run the Verizon Business softphone on desktop or mobile; users who prefer a desk phone get a pre-provisioned unit that plugs into the LAN and authenticates automatically. The Verizon Fios Login portal surfaces voice configuration alongside circuit administration for a unified admin view.
Capacity planning on hosted SIP is straightforward. The SIP trunk is sized against simultaneous-call capacity (SCC) with a typical 5:1 user-to-SCC ratio for office environments and 10:1 for environments where heavy outbound calling is rare. Call-recording storage is quoted separately in tier bundles; unlimited domestic long-distance is standard on every Verizon Business Voice plan; international minutes run against a published country-by-country rate card with volume-commitment discounts for customers with heavy international traffic.
Plan Matrix — Users, Features and PSTN Minutes
Zero-click snippet. Verizon Business Voice plans scale from Essentials (1-20 users, basic SIP) through Standard and Professional up to Enterprise (unlimited users, full call-centre, recording, analytics). Domestic long-distance is unlimited across all tiers; international minutes vary by plan and country.
Unified Voice Brief
The plan matrix below is the short reference for sizing a hosted-SIP deployment. PSTN-minute columns show domestic unlimited plus the bundled international pool; heavy international callers can stack additional country-specific bundles or flat-rate international packages.
Verizon Business Voice plan matrix with user limits, features and PSTN minutes.
| Plan | Users | Features | PSTN Minutes |
|---|
| Essentials | 1-20 | Basic SIP, voicemail, softphone | Unlimited domestic, 100 int'l |
| Standard | 21-100 | Auto-attendant, hunt groups, Teams direct routing | Unlimited domestic, 500 int'l |
| Professional | 101-500 | Call recording, analytics, Webex integration | Unlimited domestic, 2000 int'l |
| Enterprise | Unlimited | Contact-centre, omnichannel, API integration | Unlimited domestic, negotiated int'l |
Plan selection is driven by user count more than any other factor. Essentials fits small professional-services offices with under twenty staff; Standard covers most mid-market offices up to about a hundred users; Professional adds call recording and analytics for sales floors and customer-service operations; Enterprise unlocks the full contact-centre stack including skills-based routing, omnichannel (voice, chat, email, SMS, social), workforce management integration and the API surface for custom integrations. Upgrading between tiers is non-disruptive — existing users keep their numbers and device provisioning — and downgrading is possible at contract anniversary with appropriate notice.
Microsoft Teams Direct Routing and Webex Calling
Zero-click snippet. Microsoft Teams direct routing bridges the Teams phone system to the Verizon Business SIP trunk via a carrier-provisioned session border controller. Webex Calling offers the equivalent integration for Cisco Webex customers. Users make and receive PSTN calls from the Teams or Webex client without separate softphone software.
Microsoft Teams has become the dominant unified-communications client across a large share of the Verizon Business customer base. Teams direct routing is the native integration path: a Verizon-provisioned session border controller (SBC) sits between the Teams phone system and the carrier SIP trunk, translating between the two call-control stacks. Users dial public telephone numbers from the Teams client exactly as if Teams were a traditional PBX; inbound calls to the user's assigned number ring in Teams; voicemail, call transfer, conference bridging and call-park work as documented in the Teams admin centre with the Verizon-provisioned number assignments.
Webex Calling provides the equivalent architecture for customers standardised on the Cisco collaboration stack. The Webex Calling user experience is similar to Teams — PSTN dialling from the desktop or mobile client — but with the Webex admin tooling instead of the Teams admin centre. Customers who run both Teams and Webex across different business units commonly maintain a single Verizon Business SIP trunk with both direct-routing integrations pointing into it, so number administration stays centralised while end-user tooling stays aligned with each business unit's preference. The network-solutions catalogue documents the managed-service tier for the session border controller infrastructure.
Zoom Phone is supported via standard SIP trunk connection as an alternative for customers who have standardised on Zoom rather than Teams or Webex. Legacy premises-based PBXes (Avaya, Mitel, NEC) that remain in place as part of a multi-year retirement plan also connect to the Verizon Business SIP trunk to terminate PSTN calls, with the SIP trunk functioning as a modern replacement for legacy primary-rate interface (PRI) circuits.
E911 Compliance, Dynamic Location and RAY BAUM'S Act
Zero-click snippet. E911 with dynamic location reporting is included on every Verizon Business Voice plan. Static desk phones register location at provisioning; softphone clients update location dynamically using the RAY BAUM'S Act framework. Emergency calls route to the correct PSAP based on registered or dynamic location.
E911 compliance is not optional for any U.S. business-voice deployment, and the RAY BAUM'S Act and Kari's Law frameworks define the requirements. Every Verizon Business Voice endpoint carries an E911-registered location. For a static desk phone, the location is registered at provisioning against the specific physical building and floor; for a softphone client on a mobile device, the location updates dynamically based on network-provided location information or user-registered addresses; for softphone clients on home-office laptops, the user confirms the registered address on first call and receives prompts to update it when location changes. Emergency calls route to the public-safety answering point serving the registered or dynamically-reported location, and the call-back number is the user's direct-dial Verizon Business number, not a generic main-line number.
The master administrator sees E911 provisioning status on the voice dashboard inside the Verizon Business admin console. Endpoints without a valid registered location fire an alert so the primary administrator can re-provision before the gap becomes an emergency-routing failure. Audit logs of E911 registrations, location changes and emergency-call events are exportable for compliance review. Kari's Law compliance — direct-dial 911 without a prefix — is enforced by default on every Verizon Business Voice plan and cannot be disabled, per federal requirements.
Legacy POTS Replacement and Managed Analogue Adapters
Zero-click snippet. Analogue alarm panels, elevator emergency phones, fire-alarm communicators and point-of-sale dial-out devices migrate onto Verizon Business Voice through managed analogue telephone adapters (ATAs). The ATA presents a POTS-looking interface to the device while riding SIP to the carrier core, preserving E911 and fire-alarm certifications.
Legacy POTS replacement is the most frequent voice-side migration workload across the Verizon Business customer base. The copper-pair POTS infrastructure that carried alarm panels, elevator emergency phones, fire-alarm communicators and point-of-sale dial-out devices for decades is being retired by incumbent local exchange carriers at industrial scale, and every one of those devices needs a replacement path. The managed analogue telephone adapter (ATA) is the standard replacement: a compact device that plugs into the LAN and exposes one or more RJ-11 ports that behave exactly like a legacy POTS line from the perspective of the connected device.
The ATA rides SIP to the Verizon Business carrier core over the same circuit that carries the office's internet and hosted-voice traffic. Power-over-Ethernet keeps the ATA running through brief local power outages (paired with an appropriately-sized UPS on the LAN switch), and dual-WAN configurations with fixed-wireless 5G backup keep the line up through primary-circuit outages. E911 and fire-alarm central-station certifications are preserved through the managed ATA configuration, which is a mandatory checkpoint during any alarm-panel migration. Underwriters Laboratories UL 864 and UL 827 requirements are met by specific managed-ATA models documented in the migration guide; the Verizon Business solutions-engineering team selects the appropriate model during site survey.
Related Verizon Business Voice Surfaces