A business VoIP phone system replaces traditional phone lines and the old PBX cabinet with software that carries calls over your data network and internet connection. For a small or mid-sized business, that usually means lower call costs, phones that work from anywhere and features that once needed a large telecom budget. This guide explains how it works, the choices you'll face, what your network needs and how to switch without losing calls or numbers.

What a business VoIP phone system is

VoIP (voice over IP) sends speech as data packets over an IP network instead of a dedicated phone circuit. A business system adds what a company needs on top: extensions, transfers, menus, queues, voicemail and reports. Every system, whatever the brand, has four parts.

  • The IP PBX: the software that registers your phones and decides where each call goes. It can run in the cloud, on a server or on an appliance in your office. Our guide what is an IP PBX explains the components.
  • SIP trunks: your connection to the public phone network, supplied by a carrier or VoIP provider along with your numbers. SIP (Session Initiation Protocol) is the signaling standard almost every business system uses, defined in IETF RFC 3261. See SIP trunking explained.
  • Endpoints: desk phones, softphone apps with headsets, mobile apps and browser clients. If you're undecided, compare hardphones and softphones, and read SIP vs WebRTC for how browser calling differs.
  • Your network: the switches, Wi-Fi, firewall and internet connection that carry every call. It decides call quality more than any other part.

Hosted, on-premise or self-hosted

The first big decision is where the PBX runs. There's no universally right answer; it depends on your sites, your IT skills and what you need to connect.

ModelWho runs the PBXGood fitWatch out for
Hosted (cloud)The providerDistributed and remote teams, no in-house telecom skillsEvery call depends on your internet link; per-user fees grow with headcount on many services
On-premise appliance or serverYou, at your siteOffices with analog phones, fax, door entry or ISDN lines; sites that want internal calls to work during an internet outageHardware lifecycle, power backup, secure remote access
Self-hosted in your cloudYou, in your own AWS, Azure or similar accountIT teams that want full control without hardwareYou patch, back up and secure the server yourself

Many platforms offer more than one model. 3CX can be hosted by 3CX, self-hosted or installed on-premise, and Yeastar P-Series comes as an appliance, a software edition or a cloud edition. Our comparison of hosted vs on-premise PBX goes deeper on cost and control, and the vendor guides to 3CX editions and Yeastar P-Series plans show what each option includes.

Features SMEs actually use

Feature lists run to hundreds of items. These are the ones that shape daily work in most small and mid-sized businesses:

  • Auto attendant and IVR: a menu that greets callers and routes them ("press 1 for sales"). Short menus work best; see IVR design best practices.
  • Ring groups and call queues: ring groups ring several phones at once, while queues hold callers in line for the next free agent and report on waiting times. Call queues vs ring groups explains when to use each.
  • Mobile and desktop apps: staff use the business number from a laptop or smartphone. Setup tips are in VoIP for remote teams.
  • Voicemail to email: messages arrive as audio files, and on many platforms as transcribed text.
  • Call recording: for training, quality checks and dispute resolution. Consent and retention rules vary by country; our guide to business call recording covers storage and consent. This is general information, not legal advice; check the rules that apply in your country.
  • CRM integration: click-to-call, caller pop-ups with the customer record and automatic call logging.
  • Reports and wallboards: missed calls, waiting times and agent activity, live and historical.

A useful exercise before you compare vendors: list the five features each team will use every day. That list, not the brochure, should drive the choice and the edition you buy.

How business VoIP is licensed

Pricing models differ more than features do, and they change the total cost a lot as you grow.

  • Per user per month: common with hosted services. Simple to budget, but the bill rises with every hire, including people who rarely use the phone.
  • Per system, sized by simultaneous calls: 3CX sells one annual license per system, priced by edition and by simultaneous calls (SC), the number of calls that can be active at the same moment. Each size also caps the number of users. Our guide to how many simultaneous calls you need shows how to size it.
  • Hardware plus a feature plan: Yeastar P-Series appliances include a free Basic plan for basic telephony, with Standard, Enterprise and Ultimate subscriptions that add features, billed monthly or annually.

Whatever the model, budget for the same cost lines: the license or subscription, SIP trunks and call charges, phones and headsets, hosting or server costs, setup and ongoing support. Ask every vendor to quote all of them, not just the license.

What your network needs

Bandwidth

Each call uses bandwidth in both directions, and the amount depends on the codec, the method used to compress the audio. Cisco's planning figures put a G.711 call at about 87.2 kbps each way on Ethernet and a G.729 call at about 31.2 kbps, at the usual 20 ms packet size. Ten simultaneous G.711 calls therefore need about 0.9 Mbps up and down, on top of everything else on the line. Upload capacity is the usual bottleneck on business broadband. See VoIP bandwidth requirements and VoIP codecs compared.

Latency, jitter and packet loss

Voice is sensitive to delay (latency), variation in delay (jitter) and lost packets. A common target, based on ITU-T Recommendation G.114, is to keep one-way delay below about 150 ms. Jitter and packet loss show up as choppy or robotic audio; fixing VoIP call quality walks through diagnosis.

QoS, firewalls and NAT

  • Give voice priority over downloads and backups with quality of service (QoS) on your router and switches. Our guide to QoS for VoIP covers the settings.
  • Put phones on their own VLAN where possible, and use PoE switches so desk phones need no power adapters.
  • Disable SIP ALG on the router unless your provider says otherwise. It's a frequent cause of one-way audio and dropped calls, covered in our NAT and firewall fixes.
  • Consider a second internet connection or a mobile data backup if the phones are business-critical.

Security basics

An exposed PBX is a target for toll fraud: attackers break into an extension or trunk and run up international or premium-rate calls, often over a weekend. The basics stop most attempts:

  • Use long, random SIP passwords and change every default credential.
  • Restrict the admin interface to known IP addresses and turn on two-factor authentication where offered.
  • Block call destinations you never use, and limit international dialing to the people who need it.
  • Keep the PBX and phone firmware updated, and set alerts for unusual call volume or spend.

Our guide to preventing toll fraud and SIP attacks goes through each control.

Emergency calling

Emergency calls need deliberate setup on any VoIP system, especially for remote and mobile users whose location changes. In the United States, the FCC's 911 rules for multi-line telephone systems (Kari's Law and RAY BAUM'S Act) require direct 911 dialing without a prefix, notification to a central point such as a front desk, and dispatchable location information such as street address, floor and room. Other countries have their own rules, and your SIP provider's emergency service terms matter too. Test emergency routing the way your provider recommends before go-live. This is general information, not legal advice; check the rules that apply in your country.

Example: a 25-person office

To see how the pieces fit, take a 25-person professional services firm with one office, a receptionist, a four-person client support team and several staff who work from home two days a week. Its busiest hour has about 60 external calls averaging 3 minutes, plus some internal transfers.

DecisionWhat the firm choseWhy
DeploymentHosted PBXNo server room, staff split between office and home
CapacityAbout 9 simultaneous calls at peak3 Erlangs of external traffic plus internal calls, sized with Erlang B at 1% blocking
Trunk8 channelsInternal calls don't use the trunk
BandwidthAt least 1 Mbps each way reserved for voice9 G.711 calls at about 87 kbps each, with headroom
EndpointsDesk phones at reception and support, apps for everyone elseReception transfers all day; others mostly use laptops
Call flowShort IVR, a ring group for sales, a queue with recording for supportSupport needs waiting-time reports; sales doesn't

The capacity line shows why sizing matters. On 3CX, 9 calls is just over the smallest 8SC size, so the firm can accept slightly more blocking at 8SC (about 2% in the busiest hour) or buy 16SC. On a per-user service the same question becomes how many paid seats it needs, including staff who rarely call.

Questions to ask any vendor or installer

  • What exactly is included in the price, and what costs extra (trunks, numbers, hosting, recording storage, support)?
  • Which features need a higher edition or plan, and at what size?
  • Where does the system run, who patches it and how are backups handled?
  • Which SIP trunk providers and desk phone models are supported?
  • What happens to calls during an internet or power outage?
  • Can we export our configuration and call records if we leave?

How to switch: a migration plan

  1. Audit what you have: numbers, lines, call flows, and every device on a phone line, including fax machines, alarm panels, lift phones and door entry.
  2. Measure call volume from records to size licenses, trunks and bandwidth.
  3. Choose the platform and deployment model against your daily feature list.
  4. Check the network: run a bandwidth and quality test, set up QoS and review firewall rules.
  5. Order SIP trunks and start number porting early, because porting often sets the go-live date. See keeping your business numbers.
  6. Build and test: extensions, IVR, queues, voicemail, recording and emergency calls.
  7. Pilot with one team for a week and fix what they report.
  8. Cut over on a quiet day, keep the old service until every number has ported, and train users on transfers, voicemail and the apps.

If you're leaving analog or ISDN lines, our ISDN to VoIP migration checklist covers the extra steps.

Common mistakes

  • Choosing on headline price: per-user fees, trunk charges and support can outweigh the license.
  • Skipping the network check: poor audio gets blamed on the phone system when the cause is the connection.
  • Porting too late: numbers that don't move on time delay the whole project.
  • Forgetting analog devices: alarms and lift phones may need a gateway or a separate line.
  • Leaving defaults in place: open admin pages and weak passwords invite toll fraud.
  • No owner after go-live: someone needs to update call flows when staff and opening hours change.

How BtoBSkills can help

We design, install and configure business phone systems on 3CX, Yeastar, FreePBX and other Asterisk-based platforms. Our VoIP installation and configuration service runs from a scoping call to a full build with extensions, trunks, call routing, queues and IVR, and the VoIP services collection lists licenses, integrations and support. Request a quote with your number of users and sites.