# SME IP telephony 2026: VoIP infrastructure

IP telephony for SMEs is no longer an optional project on the Côte d'Azur: with the gradual end of the PSTN, organizations from Tourrettes-sur-Loup to Monaco must put a solid VoIP infrastructure in place before the analog line is cut. Host Technology works as a local PACA integrator to size the LAN, the WAN, and the switchboard — not to deliver a box and leave. In 2026, call quality depends on the network as much as on the operator plan.

## What a VoIP infrastructure requires in an SME

An IP phone does not “work” because it has an RJ45 socket. It needs a stable network, bandwidth reserved for voice, correct clock synchronization, and a clear addressing plan. Without that, you get dropped calls, echo, and unwanted overflows to mobile. SME IP telephony is judged by the quality perceived at reception and by sales staff, not by the operator quote. Host Technology always starts from a field measurement in Nice, Cannes, or Monaco.

In 2026, many projects start under the constraint of the end of the PSTN: the temptation is to buy IP handsets before cleaning up the LAN. Host Technology reverses the order: measurement, VLAN, QoS, then handsets and portability.

## QoS: reserve bandwidth for voice

QoS (Quality of Service) marks and prioritizes SIP/RTP packets. On a shared FTTH link or saturated Wi-Fi, voice loses to downloads and cloud backups. The firewall and switches are configured so the voice flow goes first, with latency and jitter thresholds tracked. Without QoS, the best IPBX on the market sounds like a crackling radio. Monitoring then confirms that the markings hold during a real day.

Monitoring QoS markers (drop counters, latency) avoids discovering the problem only through reception. Host managed IT watches these metrics the way it watches server availability.

## Voice VLAN: isolate to stabilize

Separating the voice VLAN from the data VLAN limits broadcast collisions and simplifies firewall rules. IP handsets, wired softphones, and possibly Wi-Fi DECT follow a clear policy. In a hotel or a multi-room practice, this segmentation stops a guest or an antivirus scan from degrading reception. Host sets the VLAN design together with Wi-Fi and out-of-band backup.

The voice VLAN also simplifies cybersecurity: SIP/RTP flows are limited to legitimate equipment and a compromised handset is better isolated. Network and telephony share the same hardening design.

## IPBX choice: on-premise, cloud, or hybrid

On-premise: full control, local latency, ideal if you want to keep internal calls off the Internet. Cloud: mobility, multi-site without a heavy rack, dependence on the WAN link. Hybrid: local switchboard plus remote softphones. Host Technology sets the choice according to the number of handsets, the sites (Nice, Cannes, Monaco), and the need for 4G backup. No option is “universal”; the site decides.

Whatever the choice, back up the configs and document the numbering plan. A poorly documented cloud IPBX is as opaque as an aging PBX.

## Cabling, PoE, and handsets

PoE power for phones, sized switches, a calculated PoE budget, Cat5e/Cat6 cabling checked. DECT or Wi-Fi cordless handsets are planned: radio coverage, roaming, no “it will be fine.” A hotel or a medical practice does not have the same numbering plan as a warehouse. Host delivers handsets, patching, and documentation of the dial plan.

Check the PoE budget before adding cameras or Wi-Fi access points on the same switches as the phones. Host recalculates the load at each network extension.

## SIP trunk, channels, and portability

The SIP trunk brings simultaneous channels toward the operator. It is sized for the call peak, not the average. DID portability is prepared upstream: inventory, RIO, window. In 2026, many PACA SMEs combine a PSTN migration and a new trunk; Host Technology sequences both to avoid two outages.

Also size licenses and queues: a wide trunk with an understaffed reception solves nothing. The integrator aligns technology and business process.

## Checklist before IP telephony cutover

- Inventory of lines, DIDs, faxes still in use, and queues.
- Throughput and latency measurement on the primary link (and the backup).
- Voice VLAN plus QoS rules validated on a pilot handset.
- Portability plan and cutover window with the operator.
- Reception training: transfer, queue, opening message.
- Inbound/outbound call test plus a fiber-cut scenario (4G).
- Backup of IPBX / firewall configs before and after cutover.
- Trunk and link monitoring enabled in the managed-IT contract.

Add backup of recordings and configs to the checklist: IP telephony without a tested restore stays fragile. Host writes it into the managed-IT contract.

## 4G/5G backup and continuity

A cut fiber must not cut reception. A firewall with cellular failover, tested failover rules, and possibly mobile overflow: telecom continuity is part of the VoIP infrastructure. On the Côte d'Azur, operator works and local incidents regularly make the point.

The fiber-cut scenario must include a real inbound and outbound call, not only the “4G UP” icon on the firewall. Continuity is proved by ear.

## Network, telephony, and managed IT: one package

Separating the fiber provider, the firewall provider, and the telephony provider multiplies the “not my side.” Host Technology groups telephony, network, config backup, and monitoring for a PACA SME: one contact, one calendar, a settling-in period after go-live. That is the role of the integrator in Tourrettes-sur-Loup.

A single point of contact also speeds changes: a new floor, a new hotel, a second site in Monaco. An initial design built to grow avoids rebuilding everything.

- One-way latency kept low and stable, including when backups or video meetings start.
- Jitter under control on the LAN, business Wi-Fi, and the operator egress.
- Near-zero packet loss on priority RTP flows.
- PoE budget with headroom for phones, access points, and future extensions.
- Numbering plan, overflow rules, and schedules documented.
- Active monitoring of the SIP trunk, the fiber, and the 4G/5G backup.

- Reception and critical fixed handsets on PoE Ethernet.
- Mobile sales staff equipped with softphones under a clear policy.
- Guest Wi-Fi strictly separated from the voice VLAN.
- IPBX, firewall, and switch configurations backed up after every change.
- Quarterly tests of fiber cut and automatic return.
- A business contact trained on transfers, queues, and emergency messages.

A reliable IP telephony infrastructure is run with measurable criteria and explicit responsibilities. The fiber provider guarantees its access, the integrator controls the LAN, the firewall, and the IPBX, while the company validates the call paths. For a PACA SME, this split avoids grey areas at the first incident. The acceptance file must therefore contain the network measurements, the witness calls, the configuration backups, and the continuity scenario, then be reviewed at each move or headcount increase.

## FAQ: frequently asked questions

### What throughput is needed for SME IP telephony?

Raw throughput per call stays modest, but sizing is not a matter of multiplying a few kilobits by the number of handsets. Simultaneous calls, codecs, encryption, the VPN, video meetings, and above all upload saturation must be considered. An SME in Nice or Cannes can have fast fiber and still suffer jitter. Host Technology measures the peaks, reserves voice with QoS, and keeps margin for data use so quality is consistent rather than a flattering one-off speed test.

### Should you choose a cloud IPBX or one installed on site?

The cloud makes mobility, updates, and multi-site deployment easier, while a local IPBX gives more control over some flows and can keep internal calls running without the Internet. The right choice depends on business constraints, the level of managed IT, the fiber, and the business-continuity / disaster-recovery plan. Host Technology compares both architectures with their full cost, their RTO, and their degraded mode. For many SMEs on the Côte d'Azur, a secured cloud solution with reliable FTTO or FTTH and 4G/5G backup is a relevant compromise.

### Is a voice VLAN enough to guarantee good calls?

No. The voice VLAN segments equipment and simplifies security, but it creates neither bandwidth nor priority by itself. DSCP marking must also be applied, QoS queues configured on the switches and the firewall, the SIP trunk checked, and physical faults corrected. A chain is only as strong as each link that keeps the priority. Host Technology therefore checks the full path from the phone to the operator and measures latency, jitter, and loss during genuinely busy hours.

### How do you keep the switchboard up during a fiber outage?

The firewall must detect the failure, fail over automatically to 4G/5G backup, and reserve that capacity for VoIP, the critical VPN, and essential applications. Backups and updates are temporarily throttled. Depending on the SIP trunk, a NAT adjustment or overflow to mobiles may be required. The setup is credible only after an inbound and outbound call test with the primary link deliberately cut. Host Technology documents this scenario and builds it into the company’s voice continuity plan.

### Why call a local integrator in PACA?

A migration mixes cabling, fiber, network configuration, portability, training, and support after cutover. A local contact can measure the site, work on the rack, and coordinate the operator without sending the SME between several hotlines. From Tourrettes-sur-Loup, Host Technology supports Nice, Cannes, Monaco, and the hinterland with a shared view of IP telephony, the network, and backup. That proximity speeds diagnosis and, above all, makes it possible to design an architecture suited to the building and to real opening hours.

Need an IP telephony audit on your site on the Côte d'Azur or in Monaco? Contact Host Technology for a field assessment — throughput, QoS, VLAN, cutover plan — before signing a voice plan at random.
