SIP trunk and portability: get IP telephony right in PACA

The business SIP trunk and number portability are the heart of a successful IP telephony cutover in PACA. Keeping DID numbers while moving to the cloud or a local IPBX avoids losing years of business cards and local listings. Host Technology, from Tourrettes-sur-Loup, runs channels, SIP security, and portability day for SMEs from Nice to Monaco — with the network and QoS in the same package.

SIP trunk: what you are actually buying

Simultaneous channels, authentication (IP or login), codecs, sometimes hosted DIDs. It is not “the fiber”: it is the voice pipe toward the operator. Undersizing channels produces permanent busy tone; oversizing inflates the bill. Host calculates from the real call peak (reception plus campaigns), not from a marketing average.

A poorly tuned SIP trunk (timers, codecs, T.38 fax) produces intermittent symptoms that are hard to explain to reception. Host Technology validates these parameters in pre-production.

Trunk security

IP filtering, strong passwords, TLS/SRTP if available, a ban on unnecessary international calls, monitoring of registration attempts. A poorly secured exposed trunk becomes a fraud platform. SME cybersecurity includes telephony: Host Technology hardens the firewall and SIP rules together.

Watch abnormal outbound call volumes: a sign of fraud. Monitoring and operator caps limit the financial damage.

Portability: inventory before the file

Complete list of numbers, RIO, exact holder, fax still on copper, multi-site lines. A forgotten DID means a client falling into the void. Queues and welcome messages are also mapped so they can be recreated identically on the day.

For Monaco and France, check numbering and operator specifics: portability files are not always handled like a classic French DID.

Cutover window and rollback plan

Choose a slot with on-call cover, and avoid Friday evening. Prepare overflow mobiles and a temporary message. A documented rollback reassures management. Host coordinates the losing and gaining operators to limit telephone back-and-forth.

Warn partners and numbers on file (suppliers, alarms) if a temporary change of caller ID is planned. Business communication is part of the day.

SIP trunk and portability checklist

1. Inventory of DIDs / RIO / uses (reception, fax, alarms).
2. Size simultaneous channels for the business peak.
3. Validate voice VLAN, QoS, and firewall (SIP/RTP ports).
4. Secure the trunk (IP allowlist, credentials, restrictions).
5. File the complete portability dossier and confirm the window.
6. Pre-cutover tests (test numbers), then cross-checks on the day.
7. Train reception; check queues and schedules.
8. Enable trunk monitoring plus IPBX config backup.

Host documents each special use with its own cutover date, so the main switchboard is not blocked.

Fax, alarms, and special uses

A SIP trunk does not magically replace a legal fax or a PSTN alarm. Adapter, IP fax, or a business replacement: each case is handled in the project. On the Côte d'Azur, Host includes them to avoid emergencies after portability.

The checklist becomes the signed acceptance report: without a business signature, the old link is not cut. Simple discipline, and effective.

Multi-site and numbering

Several PACA sites can share a trunk or have one per site. The numbering plan (prefixes, overflow) must stay readable for reception. A stable SD-WAN or VPN serves internal calls; QoS remains mandatory on each LAN.

A clear numbering plan (site prefix, cross-site queues) stops reception from dialing “by feel.” Host trains it and leaves it posted next to the switchboard.

After the day: settling-in and managed IT

The first week produces tickets: schedules, queues, softphone rights. Managed IT absorbs these adjustments. Monitoring alerts if the trunk unregisters. Configs join the backup policy. Portability succeeds only when day-to-day operations are calm.

The first trunk invoice is checked: channels, DIDs, international options. Gaps are easier to negotiate immediately.

Mistakes that cost money

• Portability without a complete DID inventory.
• Channels undersized on the day of a sales campaign.
• A firewall cutting RTP intermittently.
• No 4G backup during the operator window.
• No inbound call test from an outside mobile.

In practical terms, every PACA site has its own constraints (building, seasonality, multi-site setups across Monaco and Nice): Host Technology adapts the action plan rather than copying a fixed national template, with a single point of contact for the network, telephony, backup, and managed IT.

The documentation delivered at the end of the project (diagrams, accounts, failover procedures, operator contacts) is designed so a third party can take it over: that is a Host requirement, not an optional extra. It reduces dependence on a single person and speeds up later audits.

Finally, plan a review at 30 and 90 days: recurring tickets, QoS or throughput measurements, restore tests, and additional training. That is often when supervision thresholds are adjusted and management sees the operational gain on the Côte d'Azur.

The mistakes listed above come back in most of the urgent files Host takes over after an improvised cutover. They are better handled upstream.

• Have each department validate the list of its published numbers.
• Keep proof of ownership, the RIO, and the last operator invoice.
• Test inbound, outbound, withheld, international, and emergency-service calls.
• Check caller ID presentation and DID routing.
• Prepare a communication channel independent of the switchboard.
• Keep the old service active until formal business acceptance.

Success is measured by the number of calls correctly routed, not by the green status the operator displays. Acceptance must cover each public number, mobile and landline calls, schedules, queues, overflow, and regulated uses. It also states who decides a rollback and until what time. For a PACA SME, Host Technology centralizes this evidence in a report shared with reception and management. This document stops an anomaly discovered after the old contract is cancelled from becoming a commercial emergency.

After cutover, occupancy statistics, abandoned calls, and incidents must be reviewed with the business owners. They make it possible to adjust channels, queues, schedules, and overflows rather than keeping the cutover-day configuration indefinitely. Host Technology organizes a thirty-day review, checks the operator invoice, and verifies that old services have been closed without removing a useful dependency. Portability thus becomes the starting point of better-run IP telephony, not only an administrative change.

FAQ: frequently asked questions

How many channels should a SIP trunk have?

The number depends on the peak of simultaneous calls, queues, outbound campaigns, and conferences, not on the total number of employees. Available statistics must be analyzed and a reasonable margin added for events. A Nice hotel in season or a sales team in Cannes does not have the same profile as an administrative office. Host Technology sizes the trunk, configures occupancy alerts, and plans a simple upgrade. That limits busy tones without permanently funding unused channels.

How long does number portability take?

The lead time varies with the operator, the line type, the quality of the file, and the presence of complex groupings. Inconsistent holder information or a forgotten number can cause a rejection and shift the calendar. Work must therefore start several weeks before the desired date, the old contract kept, and the lines to be ported never cancelled by the company itself. Host Technology checks the inventory, follows losing-to-gaining exchanges, and confirms the window only when the technical prerequisites have been tested.

Can all existing DID numbers be kept?

Most business numbers can be ported, but the rules depend on the area, the country, and the operator, notably for Monaco or certain special services. Numbers included in a head number or a group must be identified precisely. Host Technology cross-checks invoices, RIO, directories, and the old switchboard configuration. Each DID then receives a destination in the new IPBX. This work stops a little-used number, still published with an important partner, from disappearing.

How do you secure a SIP trunk against fraud?

Authorized sources must be limited, unique and strong credentials used, TLS and SRTP enabled when the chain allows it, unused destinations closed, and operator caps set. Monitoring must detect abnormal registrations and unusual outbound volumes, especially outside opening hours. IPBX administrator accounts need MFA and access restrictions. Host Technology coordinates hardening of the firewall, IP telephony, and the operator portal, then backs up the validated configurations.

What happens if the Internet drops after portability?

A SIP trunk depends on the IP network, but continuity can be prepared. The firewall fails over to a 4G/5G link, QoS reserves bandwidth for reception, and the operator can overflow calls to mobiles if the trunk becomes unreachable. NAT settings and authentication must work on the secondary link. Host Technology tests this scenario before the day with real calls. The SME thus keeps a degraded but operational switchboard during the fiber incident.

A SIP trunk cutover and portability to prepare in Nice, Cannes, Monaco, or the hinterland? Contact Host Technology for end-to-end support — file, QoS, the day itself, and monitoring.