Asterisk

Sangoma vs Buying a Vanity Phone Number Outright

37 min read

Sangoma is the open-source-rooted PBX vendor in the comparison cluster. The company began in 1984 as a Canadian SS7 and SIP signaling-card maker, acquired Digium (the original sponsor of Asterisk and the Switchvox business unit) in 2018, acquired Star2Star and the StarBox cloud platform in 2021, and today ships FreePBX (the open-source GPL-licensed Asterisk distribution), PBXact (the commercial appliance and cloud build of FreePBX with Sangoma support), Switchvox (the on-premises and cloud Asterisk-based UC platform Digium built before the acquisition), and Sangoma Talk (the company's hosted UCaaS). Across all of those products, the PSTN side is BYO — Sangoma certifies its own SIPStation trunking service plus dozens of third-party SIP carriers, but the platform itself never sold the digits. That structural fact is the reason Sangoma is the most BYO-friendly and open-source-friendly UCaaS in this comparison cluster, and the reason the technically-inclined IT director or managed service provider who chose Sangoma is also the buyer most likely to appreciate outright number ownership as the structurally cleanest answer for the brand-bearing line on the company's signage.

Decision tree for any FreePBX, PBXact, Switchvox, or Sangoma Talk buyer weighing the platform against a memorable, owned inbound number. Numbered, in order:

  1. Is your IT team or MSP partner Asterisk-fluent and comfortable running a Linux-based PBX on bare metal, in a hypervisor, or on a Sangoma-supplied appliance? Then FreePBX or PBXact is the lowest-TCO PBX answer in the comparison cluster, especially at 50+ seats where the open-source license plus per-system support tier crushes per-seat UCaaS economics.
  2. Does the digit-string on signage, business cards, vehicle wraps, billboards, the lobby directory, the field-service truck, the radio spot, and the invoice header need to live as a recall asset for the next 10 to 25 years? Buy it outright from Digit Exclusive. From $200–$250, paid once. Sangoma does not curate premium vanity inventory at depth — the SIPStation marketplace and any third-party SIP trunk certified for FreePBX, PBXact, Switchvox, or Sangoma Talk assigns DIDs from rate-center pools, which is fine for backline numbers but inadequate for the single line your customers actually remember.
  3. Are both true at once — Sangoma is the right PBX AND the inbound number is brand-bearing? Buy the vanity outright, then port it onto your chosen Sangoma-supported SIP trunk (SIPStation, Bandwidth, Twilio Elastic SIP Trunking, Telnyx, IntelePeer, Voipfone, Lumen, AT&T SIP Trunking, Verizon Business SIP, or any of the dozens of carriers FreePBX and PBXact certify). FreePBX or PBXact handles call control, ring groups, queues, IVR, follow-me, time conditions, and the Asterisk dialplan. You own the digits forever. This is the textbook BYO architecture under FCC Local Number Portability rules (47 CFR Part 52).
  4. Already a year into a Sangoma deployment with a SIP-trunk-assigned DID nobody on the executive team can remember? Buy a vanity outright, port it onto the same SIP trunk you already use, and reroute the inbound route in the FreePBX or PBXact admin UI to the same extension, ring group, queue, or IVR. The replacement is a 30-minute admin-UI change after the port-in completes; existing dialplan, recording rules, and IP phone provisioning stay intact.
  5. Trying to pick a winner between Sangoma and outright vanity? Stop. They are different layers. Sangoma sells the call-control platform — FreePBX as open-source software, PBXact as a commercial appliance or cloud, Switchvox as the Digium-heritage Asterisk UC platform, Sangoma Talk as hosted UCaaS. The vanity number is the regulated US telephone number on the common-carrier network, ported to whichever SIP trunk you chose. The grown-up answer for any Sangoma shop with a public-facing line is both, with the SIP trunk slotted into the middle.

The rest of this article expands the checklist — the four Sangoma deployment paths in plain English, the open-source-versus-commercial-appliance economics that make FreePBX cheaper than per-seat UCaaS at scale, the four-column comparison, the cost math at 1, 5, and 25 years for a 25-seat MSP-deployed shop, the seven-step port-in walkthrough, and the questions Asterisk-fluent IT teams and MSP partners actually ask. We sell premium vanity numbers From $200–$250, paid once, owned forever. FreePBX is open-source-free; PBXact, Switchvox, and Sangoma Talk price separately under per-system or per-user models depending on the SKU. Two different products. Two different jobs. Almost always combined inside any Sangoma deployment that cares about its inbound number.

Why Sangoma Is the Most Open-Source-Friendly UCaaS in This Comparison Cluster

Sangoma owns Asterisk. The 2018 acquisition of Digium brought the original sponsor of the Asterisk open-source telephony framework, the Switchvox commercial Asterisk distribution, the FreePBX open-source distribution and graphical management layer, and the SIPStation trunking marketplace under one roof. That is a unique structural position in the US PBX market. Every other UCaaS in the comparison cluster — RingCentral, 8x8, Microsoft Teams Phone, Cisco Webex Calling, Dialpad, Vonage, Zoom Phone, Mitel, Avaya — ships proprietary call-control software with bundled or partner-curated PSTN. Only Sangoma ships an open-source GPL-licensed PBX (FreePBX) alongside its commercial appliance, cloud, and hosted offerings, and only Sangoma actively maintains the underlying open-source telephony engine (Asterisk) that powers thousands of unrelated commercial products and white-label PBXs across the industry.

On the PSTN side, every Sangoma product uses customer-supplied SIP trunks. SIPStation is Sangoma's own US SIP trunking service, tightly integrated into the FreePBX and PBXact UIs for one-click setup; outside SIPStation, FreePBX and PBXact certify dozens of third-party carriers — Bandwidth for tier-one US infrastructure, Twilio Elastic SIP Trunking for developer-friendly programmable voice, Telnyx for global SIP with strong North American footprint, IntelePeer for enterprise-grade managed SIP, Voipfone and SIP.us for cost-optimized US trunks, Lumen and Verizon Business SIP for tier-one carrier relationships under existing telecom MSAs, and AT&T SIP Trunking for AT&T-anchored shops. None of those carriers curates a deep vanity inventory; they assign DIDs from rate-center pools. That is the gap an outright purchase fills.

The four Sangoma deployment paths, in plain English

FreePBX self-hosted on Linux. Download the free, GPL-licensed FreePBX Distro (CentOS-based historically, now SNG7 / FreePBX 17 on Debian-derived OS) and install on bare metal, ESXi VM, KVM, Proxmox, Hyper-V, or a hyperscaler instance (AWS EC2, Microsoft Azure VM, Google Compute Engine, DigitalOcean Droplet, Vultr, OVH, Hetzner). Asterisk runs underneath; the FreePBX web UI provides the configuration layer for extensions, trunks, inbound routes, outbound routes, ring groups, queues, IVR, time conditions, follow-me, conferences, voicemail, paging, and the dialplan. Add commercial Sangoma modules (System Admin Pro, EndPoint Manager, XactView, Class of Service, Conference Pro, Voicemail Reports, etc.) for license fees if needed, or stay fully open-source with community modules. The path Asterisk-fluent IT teams pick when they want maximum control and the lowest acquisition cost.

PBXact appliance or cloud. PBXact is the commercial, hardened, Sangoma-supported build of FreePBX. Available as physical appliance (PBXact 25, 40, 60, 100, 400, 1000, 2000, 5000 — sized to user count), as virtual machine for VMware or Hyper-V, or as PBXact Cloud (Sangoma-hosted multi-tenant or dedicated instances). Includes most commercial modules pre-licensed, includes Sangoma technical support, includes warranty on physical appliances, and includes the SIPStation integration for one-click trunk activation. The path most regulated-vertical buyers, MSP-fronted SMB deployments, and IT-light shops pick when they want FreePBX power without the administrator burden of curating commercial modules and Linux patching themselves.

Switchvox on-premises or cloud. Switchvox is the Asterisk-based UC platform Digium built before the 2018 Sangoma acquisition, marketed at SMB and mid-market shops that want a simpler, more polished admin UX than raw FreePBX with deeper bundled UC features (presence, chat, Switchboard call-control HUD, mobile clients, conference rooms, integrations with Salesforce, Google Workspace, and Microsoft 365). Available as on-premises appliance (Switchvox E-series), as software for self-host, or as Switchvox Cloud at roughly $30+ per user per month. The path SMB shops pick when the admin team wants a more turn-key product than FreePBX without leaving the Sangoma ecosystem or the Asterisk lineage.

Sangoma Talk hosted UCaaS. Sangoma Talk is the company's hosted, multi-tenant UCaaS offering — the strategic answer to per-seat cloud competitors like RingCentral, 8x8, Dialpad, and Vonage. Per-user-per-month pricing, fully managed by Sangoma, no Linux skills required, includes desktop and mobile softphones, basic UC features, and SIPStation-style bundled US trunking. The path very small shops and non-technical buyers pick when they want a Sangoma-branded experience without any of the appliance, software, or trunk-selection decisions FreePBX, PBXact, and Switchvox require. Sangoma Talk is also the SKU that competes most directly with the rest of the per-seat UCaaS market, and the SKU that loses most of the BYO-friendliness wedge that defines the rest of the Sangoma portfolio.

Open-source-plus-support — the structural pricing wedge

Sangoma is the only vendor in this comparison cluster with a free, GPL-licensed PBX as a real production option. FreePBX powers tens of thousands of US deployments under the open-source license; the deployment cost is whatever the Linux server costs to run, plus optional Sangoma commercial modules and optional Sangoma support tiers. PBXact bundles those modules and support into a per-system fee that is still typically much cheaper than a per-seat UCaaS at 50+ seats. By contrast, RingCentral, 8x8, Microsoft Teams Phone (Microsoft Teams Phone Standard SKU), Cisco Webex Calling Professional, and Dialpad all price per user per month, which means the hundredth extension costs the same as the first. That is the math that makes FreePBX and PBXact dramatically cheaper than per-seat UCaaS at scale and the reason cost-conscious mid-market operators, MSPs, and regulated-vertical IT directors choose them.

Where Sangoma is honestly mid-pack

FreePBX and PBXact are not the most polished consumer-grade UX. The FreePBX admin UI is a power-user interface designed for telephony administrators, not a friction-free product designed for non-technical end-users — RingCentral, Dialpad, and OpenPhone all ship cleaner consumer-facing apps, and Switchvox is closer but still admin-heavy. Sangoma Talk is the consumer-friendlier SKU but loses the BYO and open-source wedges that make the rest of the portfolio interesting. FreePBX and PBXact require more deployment effort and more ongoing patch hygiene than turn-key cloud UCaaS — Asterisk security advisories, FreePBX module updates, OS patching, SBC configuration for remote extensions, and certificate management are real operational work. Sangoma is not the deepest pure-play contact center for inbound queue depth — Genesys Cloud, NICE CXone, Five9, and 8x8 XCaaS lead at multi-thousand-seat contact-center deployments. Sangoma is not the right fit for a Microsoft 365-native shop with no Asterisk capacity and no MSP partner — see Microsoft Teams Phone vs outright vanity for that buyer profile. Sangoma is not the right fit for a Cisco-anchored Fortune 2000 shop on an active Cisco Enterprise License Agreement — see Cisco Webex Calling vs outright vanity for that buyer profile. Sangoma wins where Asterisk fluency, open-source preference, on-premises control, and per-system pricing matter most: cost-conscious SMB and mid-market shops, MSP-fronted deployments, regulated verticals (government, healthcare, legal, defense-adjacent) wanting on-premises control, multi-site retail and hospitality operators, and any shop with strong open-source or Linux operational discipline. That is enough.

Four-Column Comparison: Sangoma, Outright Vanity, Hybrid, Mobile

Honest comparison adds the consumer-mobile path most "Sangoma vs vanity" articles skip. Many solo professionals, side-hustlers, and 1-to-3-person partnerships do not need the FreePBX, PBXact, Switchvox, or Sangoma Talk layer at all — a memorable owned number on a Verizon, AT&T, T-Mobile, Mint Mobile, or Google Voice SIM does the entire job, and Sangoma deployment economics only break even at roughly 5+ extensions on the paid tiers anyway.

Dimension Sangoma subscription / appliance only Outright vanity (Digit Exclusive only, on consumer SIM) Hybrid: Outright + port via Sangoma SIP trunk Consumer mobile only
Setup cost FreePBX free open-source. PBXact appliance ~$1,000-$10,000 one-time + support. Switchvox Cloud ~$30+/user/mo. Sangoma Talk per-user/mo. SIPStation or third-party SIP trunk setup typically free. From $200–$250 one-time From $200–$250 once + SIP trunk setup (typically free) + port-in fee (often included) Carrier activation only
Year-1 cost (25-seat shop, FreePBX path) Server $400-$1,000 + optional commercial modules $250-$800 + optional Sangoma support $300-$1,200 + SIPStation or third-party DID + per-min usage = ~$900-$3,000 $250-$600 paid once $250-$600 once + ~$900-$3,000/yr (FreePBX + trunk + optional support) Carrier plan only
5-year cost (25-seat shop, FreePBX path) ~$4,500-$15,000 (server lifecycle + trunk usage + optional support renewals) $250-$600 total ~$4,700-$15,600, but the digits remain yours forever Assigned-pool number is forgettable; 1-2 carrier churns over 5 years
25-year cost (career-length brand line) ~$22,500-$75,000+ if FreePBX server, trunk, and support held flat (they will not) $250-$600 total Subscriptions and hardware lifecycles recur; the recall asset never resets 4-6 carrier numbers churned in 25 years; brand recall reset every time
Number ownership at end of contract Number lives on SIPStation, Bandwidth, Twilio, Telnyx, or your chosen SIP trunk — fully portable under FCC LNP Yours, on a regulated common carrier of your choice Yours, portable to any US carrier or PBX Carrier owns it; portable but rarely memorable
Premium vanity selection Depends entirely on SIP trunk carrier inventory — usually small, generic, rate-center-pool DIDs 15,593 unique premium patterns across area codes Same as outright; routes through FreePBX/PBXact/Switchvox and your IP phone fleet Carrier random-assigns; vanity rare
IP phone + softphone integration Yes — Sangoma desk phones (s-series, P-series, D-series), plus Yealink, Fanvil, Snom, Polycom, Grandstream, Cisco SPA via FreePBX EndPoint Manager and Sangoma Phone Apps N/A — no PBX layer Yes — native, on the owned number None
Best fit Asterisk-fluent IT shops, MSP-fronted SMB, regulated on-premises (gov, healthcare, legal), open-source-preference buyers, multi-site retail/hospitality Solo, creator, 1-to-3-person partnership Any Sangoma deployment with a brand-bearing inbound line Personal use, internal-only lines

Five-year math is the row most Sangoma renewals quietly absorb without comment. A 25-seat FreePBX shop with a self-hosted Linux server, optional Sangoma commercial modules, optional support tier, and a Bandwidth or SIPStation SIP trunk runs roughly $4,500 to $15,000 over five years before factoring in hardware refresh or PBXact upgrade cycles. Adding a $250 to $600 outright vanity from our 15,593-number inventory is a rounding error against that recurring stream. The digits become a brand asset on the balance sheet, independent of which PBX, which appliance generation, or which SIP trunk you run in 2031.

Who Sangoma Actually Wins For

The real Sangoma buyer profile is structural and surprisingly wide because the open-source-plus-commercial portfolio plus BYO-everything architecture fits a specific buyer culture more than a specific industry:

Asterisk-fluent SMB and mid-market shops with internal IT capacity

The 25-to-250-seat shop with an in-house IT director or sysadmin who already runs Linux workloads, has Asterisk experience or is willing to invest in it, manages firewall rules on Sophos, Fortinet, WatchGuard, or pfSense, and patches Linux servers on a regular cadence is the prototype FreePBX or PBXact buyer. The open-source license caps acquisition cost at zero, the optional Sangoma support tier covers escalation when the team hits something obscure, the BYO SIP trunk lets the IT team shop carriers competitively, and the on-premises or self-hosted-cloud deployment fits inside existing operational discipline. Replacing the PBX with a per-seat UCaaS suite would multiply recurring spend without delivering a feature the IT team values.

MSP-fronted SMB deployments under managed-service contracts

The 5-to-50-seat shop without internal Asterisk capacity but with an MSP partner running the IT stack frequently lands on FreePBX or PBXact because the MSP packages it as a managed service. The Sangoma Channel Partner program (Authorized, Silver, Gold, Platinum tiers) provides the certification, deal registration, co-marketing, and revenue economics the MSP needs. The MSP runs the FreePBX or PBXact instance under its own brand, hosts on its own infrastructure or uses PBXact Cloud, brings the SIP trunk relationship from SIPStation or a wholesale carrier like Bandwidth, Twilio, or Telnyx, and bundles IP phone provisioning. The customer signs one monthly invoice with the MSP. The vanity number is a separate procurement decision the MSP coordinates but does not source — pointing the MSP at Digit Exclusive and asking them to coordinate the port through SIPStation or the chosen third-party SIP trunk is the cleanest division of labor.

Regulated on-premises verticals

Government agencies, healthcare practices, legal firms, and financial services shops where on-premises voice control is a binding compliance or policy constraint often land on FreePBX or PBXact because the self-hosted Linux deployment keeps the call-control software inside the customer's own data center under the customer's own change-control. HIPAA, SOC 2, state-government data residency requirements, and certain DoD and law-enforcement adjacency requirements all become easier to satisfy when the PBX is not a SaaS service exporting metadata to a third-party cloud. Open-source code review and the absence of a proprietary call-control black box are real advantages in regulated audits. The vanity number on the agency's main published line, the practice main line, the firm's intake line, or the financial advisor's published line is a separate decision and the outright-purchase answer holds regardless of which PBX vendor the IT director picks at any future review.

Multi-site retail, restaurant, and hospitality operators

The 10-to-200-location operator with a corporate office and field locations — quick-service restaurants, multi-unit retail, regional hospitality groups, dental and medical practice federations, fitness chains, automotive service chains — runs FreePBX or PBXact cleanly because the per-system or per-appliance cost scales with deployment count rather than per-seat-in-perpetuity. A regional QSR with 80 locations can architect either a single multi-tenant PBXact instance per region with regional SIP trunks, or a per-location PBXact 25 appliance, depending on operational preference. The brand-bearing main line per location, the corporate main line, the franchisee inquiry line, and the customer service line all benefit from outright-owned vanity treatment because the digit-strings outlive any single PBX renewal cycle. Premium vanity inventory for these operators is a one-time procurement that compounds for the life of the brand.

Open-source-preference IT directors and engineering-led SMBs

The fastest-growing FreePBX cohort in 2026 is the open-source-preference shop — engineering-led startups, technically-inclined SMBs, university IT departments, research institutes, and any organization that explicitly avoids vendor lock-in as a strategic principle. FreePBX is GPL-licensed, the underlying Asterisk framework is GPL-licensed, the configuration is portable as plain-text files plus a MariaDB schema, and the SIP trunk architecture means the carrier is swappable. There is no proprietary call-control black box, no per-seat licensing cliff, and no surprise annual escalator. For these buyers, Sangoma Talk and Switchvox Cloud are off the table because they reintroduce the SaaS lock-in pattern; FreePBX or PBXact on-premises is the only acceptable answer. The vanity number on the published line is a separate procurement that fits the same anti-lock-in posture — owned outright, ported across carriers under FCC LNP whenever the shop changes SIP trunk relationships.

Sangoma-deployed shops migrating away from legacy on-premises PBX

A large Sangoma buyer cohort is the existing legacy on-premises PBX customer migrating off Avaya IP Office, Mitel MiVoice Office, NEC SV-series, Allworx, ShoreTel (now Mitel-acquired), or older Cisco Unified Communications Manager Express deployments. The migration path keeps the existing SIP-compatible IP phone fleet (Yealink, Fanvil, Snom, Polycom, Grandstream all re-provision cleanly via the FreePBX EndPoint Manager), keeps the existing SIP trunk if the carrier supports modern signaling, and shifts call control onto a fresher, lower-TCO Asterisk-based platform. The vanity numbers being retired from the legacy PBX or the new vanity being purchased for the post-migration brand refresh both ride into the new architecture under FCC LNP. Premium vanity inventory is what most of these migrations quietly miss until the marketing director asks why the new system still rings on the same forgettable assigned-pool DID.

Where the Sangoma buyer profile breaks

If the binding constraint is Microsoft 365-native culture with Outlook, SharePoint, Teams, and Copilot already owning the desktop and a procurement office that wants one Microsoft invoice, see Microsoft Teams Phone vs outright vanity. If the constraint is Cisco-anchored Fortune 2000 enterprise standards under an active Enterprise License Agreement, see Cisco Webex Calling vs outright vanity. If the constraint is broad UCaaS with international depth and integrated contact center for non-technical buyers, see RingCentral vs outright vanity. If the constraint is bottom-end pricing for a 1-to-5-person shop with no IT or MSP capacity at all, see Grasshopper vs outright vanity or Phone.com vs outright vanity. If the constraint is a software PBX with simpler Linux profile and per-system licensing without the open-source baggage, see 3CX vs outright vanity — the closest sibling architecture.

Why Sangoma Reps and Channel Partners Do Not Try to Sell You the Number

Sangoma operates SIPStation as its own US SIP trunking marketplace, which means Sangoma does sell PSTN connectivity — but SIPStation, like every other SIP trunk in the comparison cluster, assigns DIDs from rate-center pools. There is no premium-vanity catalog inside SIPStation. The platform is built for fast trunk activation, competitive per-minute pricing, and tight FreePBX / PBXact integration; it is not built for repeating-digit (8888, 7777, 5555), AABB and ABAB layouts, ascending sequences, palindromes, or word-spell patterns. That structural fact is the reason Sangoma-fronted deployments are unusually clean to combine with an outright vanity — there is no Sangoma-bundled premium-vanity SKU the customer needs to negotiate against, no per-user PSTN add-on locked to the PBX subscription, no minimum carrier commitment that forecloses a different SIP trunk choice down the road.

What that means for a brand-bearing line: buy the vanity outright from a broker, ask SIPStation or your chosen third-party SIP trunk provider (Bandwidth, Twilio, Telnyx, IntelePeer, Voipfone, Lumen, AT&T SIP Trunking, Verizon Business SIP, or whichever Sangoma-supported carrier your MSP has a wholesale relationship with) to port it in, route inbound through FreePBX or PBXact inbound routes to the right extension, ring group, queue, IVR menu, or follow-me destination, and let the call ring on Sangoma s-series, P-series, or D-series desk phones plus Yealink, Fanvil, Snom, Polycom, Grandstream, or Cisco SPA endpoints, plus the Sangoma Connect or Switchvox softphone clients. The asset is yours. The PBX is Sangoma's. The carrier is whichever SIP trunk partner your MSP or IT director picked. Three vendors, three layers, zero conflict.

Premium-vanity inventory does not live inside SIPStation or any third-party SIP trunk pool at depth — repeating-digit (8888, 7777, 5555), AABB and ABAB layouts, ascending sequences, palindromes, and word-spell patterns require a purpose-built broker. 15,593 unique premium numbers across all 50 states and DC, sold as one-time outright purchases starting From $200–$250.

The Hybrid Path: Outright Vanity Ported Into FreePBX, PBXact, or Switchvox via Your SIP Trunk

The hybrid pattern is the architecturally cleanest outcome inside any Sangoma deployment — supported natively across FreePBX, PBXact, Switchvox, and Sangoma Talk because every Sangoma product is BYO-PSTN by design, documented inside the FreePBX wiki and PBXact admin guide, and what most cost-conscious Sangoma customers with brand-bearing inbound lines converge on. Seven-step walkthrough:

  1. Pick the vanity from Digit Exclusive's 15,593-number inventory, filtering by state, area code, pattern type, and budget. Most premium inventory sits between $250 and $1,500. One-time checkout.
  2. Receive carrier-of-record activation from the seller-side carrier. You become subscriber-of-record on a regulated common carrier. The number is yours immediately, before any porting decision.
  3. Pick your Sangoma SIP trunk provider — SIPStation if you want the tightest FreePBX / PBXact integration, Bandwidth if you want tier-one US infrastructure, Twilio Elastic SIP Trunking for developer-friendly programmable voice, Telnyx for global SIP, IntelePeer for enterprise-grade managed SIP, or any of the dozens of carriers FreePBX and PBXact certify. If your MSP partner already runs a wholesale relationship with one of these carriers, that is the path of least resistance.
  4. Initiate inbound port at the destination SIP trunk carrier. Sign LOA, supply seller-side carrier verification, send recent bill copy. Standard FOC date is 5 to 10 business days for US local numbers under FCC LNP.
  5. Provision in FreePBX or PBXact admin UI. Connectivity → Trunks → your trunk → confirm the new DID is in the carrier-side DID list, then Connectivity → Inbound Routes → Add Inbound Route. Map the new vanity DID to the destination — extension, ring group, queue, IVR menu, follow-me, time condition, or simultaneous-ring group. Configure caller ID name, business hours routing, after-hours overflow, voicemail, call recording, and any compliance-driven announcement per your posture. Switchvox uses analogous Inbound Calls and Auto-Attendant menus; Sangoma Talk routes via the hosted admin portal.
  6. Provision phones and softphone clients. Sangoma s-series, P-series, and D-series desk phones auto-provision via Sangoma Phone Apps; Yealink, Fanvil, Snom, Polycom, Grandstream, and Cisco SPA endpoints provision via the FreePBX or PBXact EndPoint Manager. The Sangoma Connect softphone runs on iOS, Android, Windows, and macOS; the Switchvox softphone runs on the same platforms. The vanity displays on inbound caller ID and outbound caller ID per the rules you set.
  7. Document the architecture in your Sangoma runbook or your MSP's customer documentation. The number, the SIP trunk provider, the LOA, the inbound route, the IP phone provisioning template. If you ever change SIP trunks, the number ports out under FCC LNP and follows you. If you ever leave Sangoma entirely (3CX, Microsoft Teams Phone Direct Routing, RingCentral BYOC, Cisco Webex Calling Local Gateway, or back to a different Asterisk distribution), the number ports out and follows you. The asset is decoupled from every PBX renewal cycle, forever.

The walkthrough takes roughly 1 to 3 weeks end-to-end for a typical SMB or mid-market FreePBX or PBXact deployment, dominated by carrier port-in lead time rather than admin-UI work. For multi-site operators with dozens of DIDs across a regional Sangoma deployment, the project is bigger but the per-number mechanics are identical.

Cost Math: 1, 5, and 25 Years for a 25-Seat FreePBX Shop

The framing Sangoma renewals quietly run on. Three time horizons, FreePBX self-host path:

Year 1. FreePBX open-source license = $0. Linux server (bare metal or cloud) at $40 to $100 per month = $480 to $1,200 per year. Optional Sangoma commercial modules (System Admin Pro, EndPoint Manager, XactView, etc.) = $250 to $800 one-time or as-needed. Optional Sangoma support tier (Silver, Gold, Platinum) = $300 to $1,200 per year. SIPStation or third-party SIP trunk DID at roughly $1 to $5 per month plus per-minute usage at typical SMB volume = $300 to $800 per year. Total Year 1 recurring: ~$900 to $3,000. Add a $250 to $600 outright vanity once. Total Year 1: ~$1,100 to $3,600. Of that, $250 to $600 is permanent and ~$900 to $3,000 is recurring.

Year 5. FreePBX + server + trunk + optional support at flat pricing = $4,500 to $15,000. With realistic 3 to 5 percent annual escalation on hosting and SIP usage = $5,000 to $17,000. The FreePBX license itself is free and stays free; the optional commercial modules and support tier renew predictably. Owned vanity = same $250 to $600. The recall asset has not appreciated and has not depreciated; it has done its job for five years for free.

Year 25 (career-length brand line). FreePBX + server + trunk + optional support across multiple hardware refresh cycles and likely a couple of platform-version migrations (FreePBX 14 to 15 to 16 to 17 to whatever ships next) = $25,000 to $80,000+. Even at the cheapest end of the FreePBX-fronted cost curve, the recurring stream over a career is non-trivial. Owned vanity = same $250 to $600. The number on the corporate signage, the multi-location lobby directory, the franchisee recruitment page, the field-service truck wrap, the radio spot, and the business card has compounded brand recall for 25 years and cost nothing after the original purchase. This is the lease-vs-purchase decision in its most honest form. Lease the PBX from Sangoma — the call-control software, the optional commercial modules, the support tier, the SIPStation integration, the appliance hardware, or the Switchvox or Sangoma Talk service all justify the recurring spend. Purchase the digits outright from Digit Exclusive — the recall asset has nothing to gain from recurring spend and everything to lose from vendor lock.

Sangoma vs Adjacent Comparisons

For Asterisk-fluent buyers, MSP partners, and open-source-preference IT directors evaluating Sangoma alongside the rest of the UCaaS market, the adjacent comparisons on this site cover the realistic alternatives:

None of these vendors compete with us on the number itself. All of them support inbound porting under FCC LNP rules — keeping your number when you change providers. The structural answer for any shop with a brand-bearing line is the same regardless of which PBX you pick: buy the digits outright, port them into whichever UCaaS layer earns the seat. For Sangoma shops specifically, the open-source-plus-commercial portfolio plus BYO-everything architecture makes the hybrid pattern especially clean and especially honest about vendor lock-in posture.

Related vanity-number resources

Related vanity-number resources

FAQ: Sangoma and Outright Vanity

Does Sangoma sell vanity phone numbers?

Not at depth. Sangoma operates SIPStation as its own US SIP trunking marketplace, tightly integrated into FreePBX and PBXact for one-click trunk activation, but SIPStation assigns DIDs from rate-center pools rather than curating a premium-vanity catalog. For repeating-digit (8888, 7777, 5555), AABB, ABAB, ascending-sequence, palindrome, and word-spell premium patterns, work with a broker like Digit Exclusive and port the number into SIPStation or any of the dozens of third-party SIP carriers FreePBX, PBXact, Switchvox, and Sangoma Talk certify (Bandwidth, Twilio Elastic SIP Trunking, Telnyx, IntelePeer, Voipfone, Lumen, AT&T SIP Trunking, Verizon Business SIP) under FCC Local Number Portability rules.

Can I port a vanity number I bought outright into FreePBX, PBXact, Switchvox, or Sangoma Talk?

Yes. Sangoma is structurally one of the easiest UCaaS targets to port a vanity into because every product in the portfolio is BYO-PSTN by design — the platform never bundles the digits. Buy the vanity outright from Digit Exclusive, sign the Letter of Authorization with SIPStation or your selected third-party SIP trunk provider (Bandwidth, Twilio, Telnyx, IntelePeer, or any other Sangoma-supported carrier), supply seller-side carrier verification and a recent bill, and the port completes in 5 to 10 business days for standard US local numbers under FCC LNP regulations (47 CFR Part 52). The number then provisions in the FreePBX or PBXact admin UI under Connectivity → Trunks and Connectivity → Inbound Routes, gets routed to extensions, ring groups, queues, IVR menus, follow-me destinations, or time conditions, and answers on Sangoma s-series, P-series, D-series, plus Yealink, Fanvil, Snom, Polycom, Grandstream, or Cisco SPA-series IP phones, plus the Sangoma Connect or Switchvox softphone clients.

What is the difference between FreePBX, PBXact, Switchvox, and Sangoma Talk?

FreePBX is the free, GPL-licensed open-source distribution of Asterisk plus a graphical admin UI. Maximum control, lowest acquisition cost, requires Linux administration and Asterisk fluency, optional commercial modules and optional Sangoma support tiers available a la carte. PBXact is the commercial, hardened, Sangoma-supported build of FreePBX — available as physical appliance (PBXact 25 through 5000 sized to user count), as virtual machine for VMware or Hyper-V, or as PBXact Cloud. Includes most commercial modules pre-licensed, includes Sangoma technical support, includes warranty on physical appliances. Switchvox is the Asterisk-based UC platform Digium built before the 2018 Sangoma acquisition — simpler admin UX than raw FreePBX, more bundled UC features (Switchboard call-control HUD, presence, chat), available as on-premises Switchvox E-series appliance, as software for self-host, or as Switchvox Cloud at roughly $30+ per user per month. Sangoma Talk is the company's hosted, multi-tenant per-user-per-month UCaaS — fully managed, no Linux skills required, the SKU that competes most directly with RingCentral, 8x8, and Dialpad. All four use the same BYO SIP trunk architecture; none of them bundles premium vanity inventory.

How much does Sangoma actually cost in 2026?

It depends on the SKU. FreePBX is open-source and free — you pay only for the Linux server (typically $40 to $100 per month), optional commercial modules ($250 to $800 one-time or as-needed), optional Sangoma support tier ($300 to $1,200 per year for Silver / Gold / Platinum), and the SIP trunk usage. PBXact appliances run roughly $1,000 to $10,000+ one-time depending on user-count tier (PBXact 25 through 5000), plus annual support and module renewals. PBXact Cloud bills monthly per system. Switchvox Cloud runs roughly $30+ per user per month. Sangoma Talk runs per-user-per-month at rates competitive with the rest of the cloud UCaaS market. SIPStation SIP trunk usage runs per-DID per-month plus per-minute or unlimited-minute packages. Verify current pricing on the official Sangoma pricing page and through your Sangoma Channel Partner; Sangoma runs occasional promotions, partner discounts, and education / nonprofit / government pricing.

Can I port my number out of Sangoma if I switch PBXs?

Yes, and this is structurally simpler than porting out of bundled-PSTN UCaaS platforms because the number was never on the Sangoma PBX in the first place — it lives on whichever SIP trunk provider you chose (SIPStation, Bandwidth, Twilio, Telnyx, IntelePeer, etc.). To switch PBX vendors, you change SIP trunk integration on the receiving PBX (3CX self-host, Microsoft Teams Phone via Direct Routing or Operator Connect, RingCentral via Bring Your Own Carrier, Cisco Webex Calling via Local Gateway BYO PSTN, a different Asterisk distribution, etc.) and either keep the same SIP trunk carrier or initiate a port-out from your current SIP trunk to a new one under FCC LNP rules. If you bought the vanity outright before porting in, you are already subscriber-of-record on a regulated common carrier; the port-out simply moves the routing. The number is yours regardless of which PBX vendor wins the next budget cycle.

What is the Sangoma Channel Partner program and why does it matter for my deployment?

Sangoma is sold and implemented largely through certified channel partners — managed service providers, value-added resellers, telecom integrators, Asterisk consultancies, and independent IT consultants — under a tiered partner program (Authorized, Silver, Gold, and Platinum based on certification level, deal volume, and customer satisfaction). The partner brings the Asterisk and Linux engineering, the SIP trunk relationships (SIPStation or third-party), the SBC configuration if remote extensions sit outside the LAN, the firewall rules, the IP phone fleet selection (Sangoma s-series, P-series, D-series, plus Yealink, Fanvil, Snom, Polycom, Grandstream, Cisco SPA), the EndPoint Manager templates, and the ongoing managed service. Most US Sangoma deployments under 100 seats are MSP-fronted, which means the same partner who runs your Microsoft 365 tenant, your Veeam or Datto backup, your Sophos or Fortinet firewall, and your Datto or N-able RMM also runs your phone system. Sourcing the vanity number is a separate procurement decision the partner is happy to coordinate but does not source themselves; pointing the partner at Digit Exclusive and asking them to coordinate the port through SIPStation or the chosen third-party SIP trunk is the cleanest division of labor.

Does Sangoma work with Microsoft 365, Microsoft Teams, or Google Workspace?

Yes to all three at the integration layer. FreePBX and PBXact integrate with Microsoft 365 for user provisioning via Microsoft Entra ID (formerly Azure AD), expose calendar status for presence, and support click-to-call from Outlook contacts via the Sangoma Phone Apps. Switchvox ships native Microsoft 365, Google Workspace, and Salesforce integrations out of the box, including click-to-call, contact sync, and presence-based call routing. Sangoma Talk integrates with Microsoft 365 and Google Workspace for SSO and contact sync. None of these is a replacement for Microsoft Teams Phone if your organization has already standardized on Teams Phone Direct Routing or Operator Connect — see Microsoft Teams Phone vs outright vanity for that buyer profile. Sangoma is the right answer if your organization wants Teams as the messaging and meetings platform but a separate, cost-optimized PBX with BYO SIP trunks for the voice layer, or wants to avoid Microsoft-centric voice strategy entirely.

Is Sangoma a good fit for managed service providers and IT-consulting shops?

Yes. FreePBX and PBXact are among the most MSP-friendly PBX platforms in the US market because the open-source FreePBX SKU lets the MSP package PBX as a managed service with predictable margins regardless of seat count, the PBXact appliance and PBXact Cloud SKUs add a turn-key option for IT-light customers, the Sangoma Channel Partner program (Authorized through Platinum) provides revenue tiers and co-marketing, the Linux self-host option means the MSP can leverage existing data center infrastructure and firewall expertise, and the BYO SIP trunk architecture means the MSP keeps wholesale carrier relationships with SIPStation, Bandwidth, Twilio, Telnyx, IntelePeer, and others under the MSP's master agreement. The vanity number procurement sits cleanly outside that managed-service relationship — the MSP coordinates the port, the customer owns the digits forever.

Is Sangoma better than 3CX, RingCentral, 8x8, or Microsoft Teams Phone?

Different wedges. Sangoma wins for any organization that wants the lowest total cost of ownership at 50+ seats with on-premises or self-hosted-cloud control, an Asterisk-fluent IT team or MSP partner, BYO SIP trunk flexibility, open-source-preference posture, or regulatory-vertical on-premises requirements. 3CX is the closest sibling — commercial Linux PBX with per-system licensing, no open-source SKU, friendlier admin UX than raw FreePBX, lighter Linux profile. RingCentral wins on breadth of UCaaS depth with strong international reach and integrated contact center for non-technical buyers who want a single bundled vendor. 8x8 wins on XCaaS unification of UC and contact center under a single platform. Microsoft Teams Phone wins for Microsoft 365-native shops where Outlook, SharePoint, and Teams already own the desktop. None of them sells premium vanity inventory at depth, and all of them support inbound porting from outright brokers. Pick the PBX whose wedge matches your binding constraint. Buy the digits outright regardless.

Can I keep my Sangoma desk phones, Yealink, Fanvil, Snom, Polycom, or Cisco IP phones when I buy a vanity outright?

Yes. The vanity number provisions in the FreePBX or PBXact admin UI under Connectivity → Trunks and Connectivity → Inbound Routes (or analogous Switchvox and Sangoma Talk admin sections) and assigns to any registered SIP endpoint or softphone client. Sangoma s-series, P-series, and D-series desk phones auto-provision via the Sangoma Phone Apps and Zero-Touch Provisioning. Yealink (T3 / T4 / T5 series), Fanvil (X-series, V-series), Snom (D-series), Polycom (VVX series, legacy SoundPoint), Grandstream (GXP / GRP), and Cisco SPA-series provision via the FreePBX or PBXact EndPoint Manager. The Sangoma Connect softphone runs on iOS, Android, Windows, and macOS; the Switchvox softphone runs on the same platforms. The number assignment is independent of the device hardware. If you migrated from a legacy on-premises PBX (Avaya IP Office, Mitel MiVoice Office, NEC, Allworx, ShoreTel) to FreePBX or PBXact, your existing SIP-compatible IP phone fleet typically keeps working after a re-provisioning step, and the new outright-owned vanity becomes the published main line, ring-group entry point, or IVR DID.

About Digit Exclusive and the Outright Path

Digit Exclusive is a US vanity-number broker with 15,593 unique premium numbers across area codes and all 50 states plus DC, sold as one-time outright purchases From $200–$250. No subscription, no recurring fees, no rental. Patterns include repeating digits, AABB, ABAB, ABBA, ascending sequence, palindromes, and word-spell layouts. The number transfers to subscriber-of-record on a regulated common carrier at checkout; from there it ports under FCC LNP rules to whichever carrier or PBX you choose — including SIPStation, any FreePBX-certified third-party SIP trunk, or any other Sangoma-supported carrier.

Browse all numbers across the catalog, filter by state on a state pillar like California vanity numbers, Texas vanity numbers, or Florida vanity numbers for multi-state operators, or read the outright purchase explainer for the legal and porting mechanics in detail. For Sangoma-fronted shops, FreePBX self-hosters, PBXact appliance owners, Switchvox shops, and Sangoma Channel Partners who want a single decision tree, this article is it. For Sangoma licensing, channel partner tier questions, SIPStation activation, or third-party SIP trunk provider selection, talk to your Sangoma certified partner. For premium vanity inventory across the US, talk to us. Visit our contact page or browse the about page for our story.

For the broader buyer reference covering the outright-purchase model versus Sangoma or any other hosted-PBX subscription, see buy a phone number outright — five-step purchase flow, side-by-side cost table, FCC LNP FAQ.

For the dedicated pricing-research breakdown — tier-by-tier prices ($200–$250 entry, $500-$2,500 mid, $10,000-$25,exclusive) and the five-year cumulative-cost math versus monthly subscription rentals — see how much does a vanity phone number cost.

Related browsing: repeating digit numbers

Related outright-number comparisons

If you are comparing Sangoma with direct number ownership, these adjacent guides help separate phone-system choice from vanity-number ownership.

The US phone number marketplace landscape

This article touched on the marketplace model for buying US phone numbers. For the complete picture — how the marketplace model works under FCC NANP and LNP rules, side-by-side comparison of the seven established US marketplaces (Digit Exclusive, RingBoost, NumberBarn, PhoneNumberGuy, PhoneNumberExpert, 800.com, PhoneNumberWorld), pricing comparison vs VoIP subscription providers over 5 years — see our phone number marketplace guide. It includes the legal framework, the 4-step buying workflow, and the 5-year cost math that consistently favors outright purchase over subscription for any number used 18+ months.

Subscription vs outright purchase: If you are weighing recurring subscriptions against a one-time purchase, our Google Voice alternatives for business comparison covers real 2026 pricing, A2P 10DLC failures, and Workspace-bundle traps for owned-number alternatives.

Ready to buy? Start here

Every guide ends at the same place: real one-of-one US numbers, sold outright, ported to your carrier under FCC §52. Pick your starting point below.