1.833.888.0091contact@ehzee.ca

Voice over IP (VoIP) carries phone calls over your data network instead of separate phone lines. We design the network side of a VoIP system so calls stay clear, set up the phones and call handling, and test everything before your people depend on it.

VoIP is flexible and usually cheaper to run than traditional lines, but voice is less forgiving than email or file transfers. A short burst of delay or lost packets that nobody would notice on a web page turns into choppy audio or a dropped call. Most VoIP problems come from a network that was not prepared for voice, so that is where we focus.

What we design and build

  • Network readiness: checking switches, cabling, Power over Ethernet capacity, internet bandwidth and the firewall for voice traffic.
  • Quality of service: separating voice into its own VLAN and marking it so switches and routers give it priority.
  • Phones and endpoints: desk phones, conference phones, softphones on computers and mobiles, and WiFi handsets.
  • Call handling: auto attendants, hunt groups, call queues, voicemail, paging and after-hours routing.
  • Connections: SIP trunks or hosted service, number porting from your current carrier, and links to existing systems where needed.
  • Emergency calling: making sure 911 calls carry the correct location for each phone, including staff who move between sites.

A call leaves the phone as a stream of small packets. Each one passes through your switch, your router and the internet or a private link before it reaches the provider. The place quality is usually lost is the busiest link, often the internet uplink, where voice packets queue behind file transfers and video unless the network has been told to send voice first.

IP desk phone PoE powered PoE switch voice VLAN Router firewall, QoS Internet or private link Provider SIP trunk, PSTN voice marked for priority data waits voice sent first at the uplink WiFi handset roams AP to AP via AP 911 location kept on record
Where a VoIP call can lose quality. Phones put voice on its own VLAN and mark it for priority. At the busiest link, usually the router's internet uplink, voice packets are sent ahead of queued data, which keeps delay and jitter low on the way to the provider.

How it works

  1. Requirements. We ask why you are moving to VoIP or replacing your system, how people use the phone today, and which features matter.
  2. Network assessment. We review switches, cabling, PoE budgets, WiFi and the internet connection, and identify changes needed to carry voice reliably.
  3. Design. We plan VLANs, quality of service, phone placement, call flows, number porting and emergency calling.
  4. Build. We make the network changes, install and configure phones, and set up call handling and voicemail.
  5. Test and cut over. We test call quality, transfers, queues and 911 location before switching over, then support your staff through the first days.

Where phones will use WiFi, we check that the wireless network can support voice: enough signal and SNR throughout the areas people walk, a channel plan that limits interference, and settings that let handsets roam between access points without dropping calls. Voice over WiFi needs a stricter design than data alone, and our WiFi survey and design work feeds directly into the VoIP project.

What we test before cut-over

  • Calls in and out on every trunk or provider connection, including long-distance and toll-free numbers you rely on.
  • Call quality during a busy period, with the network carrying its normal data load, not only after hours.
  • Auto attendant menus, hunt groups, queues, transfers, voicemail-to-email and after-hours routing.
  • WiFi handsets on a walk through the areas staff use, checking that calls survive roaming between access points.
  • 911 calls from each location, coordinated with your provider so they reach the test or non-emergency process the provider specifies, and the location record for each phone.
  • Paging, door phones, fax lines, alarm panels and elevator phones that used the old lines.

That last item is easy to miss. Elevator phones, fire alarm communicators and some security panels were often wired to analogue lines. They may need dedicated lines, approved adapters or a separate solution, and changes to life safety connections should be confirmed with the equipment's service provider and the authority having jurisdiction before the old lines are cancelled.

What to have ready

  • A recent phone bill or carrier account details for every number to be ported.
  • A list of users, extensions, shared lines and how calls are answered today.
  • The address and floor or room details for each phone location, for emergency calling.
  • Network diagrams or switch details, if you have them.

What you get

  • A network ready for voice, with the settings documented.
  • Installed and configured phones, softphones and call flows.
  • Test results for call quality and key features before go-live.
  • Simple user guides and a record of numbers, extensions and call routing.

Emergency calls. With VoIP, a 911 call can only show the location the system has on record. Confirm with your provider how location is handled, and keep it current when phones or people move.

Who it's for

  • Offices replacing an old phone system or moving off copper lines.
  • Organizations with several locations that want one phone system.
  • Warehouses and industrial sites that need WiFi handsets or paging.
  • Property managers setting up phones for building offices, lobbies and service areas.

Related guides

Start with VoIP explained, then read Moving from landlines to VoIP for what to plan during the switch. If phones will run on WiFi, WiFi roaming and handoff explains why calls drop when people walk around.

Common questions

Can we keep our phone numbers?

In most cases, yes. Numbers can usually be ported from your current carrier to a VoIP provider. Porting takes coordination, so we plan it early and schedule the cut-over around it.

Will VoIP work if the internet goes down?

Internal calls may keep working, depending on the system, but outside calls need a connection. Options include a second internet connection, failover to mobile phones, and routing calls to another site. We will help you choose what fits the risk.

Why do calls sound fine in the morning and choppy later in the day?

That pattern usually points to congestion. As the day goes on, backups, video meetings and large downloads fill the internet connection or a busy switch uplink, and voice packets get delayed or dropped unless the network gives them priority. Measuring call quality during busy periods and checking how voice is marked and queued normally finds the cause.

Do we need new switches?

Not always. Phones need Power over Ethernet or local power adapters, and switches need to support VLANs and quality of service. We check what you have before recommending anything new.