France: SIP providers and connecting a number to the PBX

This page continues the general guide on connecting a provider's number to the PBX: that page covers everything that is the same for any operator — the two trunk modes, what to ask the provider, what to fill in the form, network requirements and how to test the connection. Here is the French specifics: who sells a number with a SIP trunk in the country, what that operator issues and what of it goes into Telephony → "Trunks and connections" → "Add provider".

The data was collected on 9 September 2026 from operator documentation and regulator (ARCEP) materials; the links are in the "Sources" section.

In brief#

• You can buy a number with a SIP trunk in France, and your business does not have to register anything for it. There is no telephony licence in the country: the operator works under a declaration filed with ARCEP, and you are simply its subscriber.
• The market is stratified. Trunk parameters are published by the "internet operators" — OVHcloud Telecom, ippi, boxIP, Keyyo, Axialys, Dstny France. The large-enterprise operators (Orange Business Talk IP, SFR TSIP MPLS, Free Pro) deliver the trunk over their own link or MPLS, and such a trunk physically cannot reach a cloud PBX.
• If no operator has been chosen yet, take OVHcloud SIP Trunk: ordered online, €4 excl. VAT per month per channel with per-minute billing or €19.99 excl. VAT per channel with unlimited calls, up to 100 channels, registration (REGISTER) to siptrunk.ovh.net. Cheaper and simpler — ippi and boxIP (from €3 per month).
• The main local pitfall is the number you present on a call. Since 01.01.2026 ARCEP decision No. 2025-2215 applies: the operator must list the permitted numbers in the contract and restrict the presentation technically, while the calling number authentication mechanism (MAN) makes the network drop unauthenticated calls. The "Show as" field with someone else's number will not work in France.
• The second pitfall is OVHcloud. An identity validation procedure is mandatory before the first outgoing calls, and French customers send the documents by ordinary post. Until it is completed the trunk is green but outgoing calls do not go through.
• The third one is Axialys, IP mode only. In password mode its From field is occupied by the trunk identifier, and the operator takes the presented number from a service header that our PBX does not send.
• Documents. A local operator signs the contract with a French entity (SIREN/SIRET). A foreign company will find it easier to take a +33 number from an international provider or from OVHcloud (the account can be opened for a European legal entity, but validation is still required).

Numbers in the country#

• The country code is +33. The national number is 10 digits, the first of which is always 0. In E.164 this is +33 plus 9 digits: the leading zero is dropped, so 01 40 12 34 56 becomes +33140123456.
• Ranges. 01–05 are "multi-purpose" numbers, which since 01.01.2023 are no longer tied to a geographic zone; 06 and 073–079 are mobile; 09 is also multi-purpose and usually belongs to VoIP operators; 08 is premium-rate services; 0700 is machine-to-machine on 14 digits.
• Dialling. Inside France all 10 digits are dialled including the leading zero, abroad — 00 and the country code, or +. Emergency services: 112 (Europe-wide), 15 ambulance, 17 police, 18 fire brigade, 114 for the deaf.

In the "Lines" tab the number can be entered in any format: the PBX matches the last seven digits. ⚠️ In France seven digits mean the number without the leading zero and without the zone code, so 01 40 12 34 56 and 03 40 12 34 56 produce the same tail. This used to be saved by the strict geographic binding, but it was removed in 2023, and one operator happily gives one customer numbers from 01, 03 and 09. With several numbers on one trunk, check the tails manually — "Add a number and routing".

Who issues a number with a SIP trunk#

The first six rows are the operators whose parameters are in public documentation: their cards are below. The rest of the local ones have a separate section: they issue the server address and password only after a contract, and some of them do not reach a cloud PBX at all.

OVHcloud Telecom#

The telecom arm of OVHcloud. Numbers and channels are ordered online in the customer portal, and the product meant for a third-party PBX is exactly SIP Trunk (not "ligne SIP", which targets a phone). The price is €4 excl. VAT per month per channel with per-minute billing or €19.99 excl. VAT per channel with unlimited calls to French landlines and mobiles; up to 100 channels, no commitment, numbers are portable.

What to enter in the admin panel

What to set up at the provider: order the SIP Trunk and the number of channels → complete the identity validation procedure → buy or port the numbers → enable "redirection avec présentation" to the trunk for every alias number → if the PBX is to supply the number, enable "présentation à la volée" and turn off the "Rester anonyme" mode.

Pitfalls ⚠️ Outgoing calls are blocked until identity validation is complete — with a live registration this looks like "the trunk is green but calls do not go", and it is fixed with paperwork, not with configuration. The "Rester anonyme" mode in the portal overrides whatever the PBX sends. The official Asterisk guide dates from 2018: the address, the login format and the codecs in it are current, everything else should be re-checked. The trunk codecs are a-law, u-law and G.722 for HD, that is our whole set. Source: Asterisk — configuration et utilisation, VoIP validation procedure, SIP Trunk pricing — 09.09.2026.

ippi#

A small French VoIP operator with a fully self-service entry: the account is created online, a virtual French number is ordered in the portal, and the FAQ contains a ready Asterisk configuration example. The fastest way to get a French number when you only need one or two.

What to enter in the admin panel

What to set up at the provider: register an account → buy a French virtual number → make sure the number is routed to the same SIP account.

Pitfalls ⚠️ One account, one line. A multi-number setup is poorly supported at ippi: in their own example the incoming call arrives without the number being parsed, so two numbers cannot be told apart in routing. Changing the virtual number costs €5 and goes through support only. If the account has no number at all, outgoing calls present the platform service number +33 1 76 600 700. The codecs are G.711 a-law, G.711 u-law, G.729 and G.722 with a-law first: our set works. Source: ippi FAQ — 09.09.2026.

boxIP#

A French operator that also sells FreePBX hosting, so its documentation is written literally in Asterisk terms. The portal is abo.boxip.fr, the account is created online, with no connection fee. Pricing: Conso — €3 per month (French landlines €0.01/min, mobiles €0.08/min), Full fixes 25 pays — €15 per month per channel, Full fixes + mobiles — €20, and "Trunk Turbo" — up to 100 simultaneous calls with a minimum spend of €100 per month.

What to enter in the admin panel

What to set up at the provider: create an account at abo.boxip.fr → choose a plan and the number of channels → buy or port a number → take the identifier, the password and the registration server address from the "Mes trunk SIP" section.

Pitfalls ⚠️ The trunk address is a bare IP address, not a name: if the operator ever changes it, the trunk will die silently, so keep in touch with support and check the address in the portal. Officially there is a single codec, a-law: calls will work, HD audio will not. boxIP expects the presented number in E.164 with a "+" (+33954545354) — set it in the outbound rule. Source: configuring a SIP trunk, pricing — 09.09.2026.

Keyyo (Bouygues Telecom Pro)#

A Paris operator for small and medium businesses, part of the Bouygues Telecom group. The only one in France that maintains a dedicated public "Paramètres SIP" page — with codecs, the domain, address ranges and ports. Asterisk is named among the compatible systems, but the operator does not provide support for it. Sold through the sales department, there is no public price.

What to enter in the admin panel

What to set up at the provider: request a quote for the Trunk SIP and the number of channels → obtain the SIP accounts and your custid → route the numbers to the trunk → confirm which numbers may be used for presentation.

Pitfalls ⚠️ Two different addresses. keyyo.net is the domain and the realm, while the line registers to <custid>.lb.keyyo.net; putting a bare keyyo.net into the "SIP host" field is the typical mistake that leaves you without registration. The codec list contains G.722, G.729 and G.711 a-law: if only G.729 is left enabled on the account, the trunk will not come up — ask for G.711. Useful when talking to support: the Keyyo platform lives in the 83.136.161.0/24–83.136.164.0/24 networks, SIP is on UDP 5060 and 8060, DTMF is RFC 2833 with payload 101. Source: Paramètres SIP et recommandations VoIP, Asterisk configuration (PDF) — 09.09.2026.

Axialys#

A Paris operator with its own platform and the most detailed trunk technical guide in France — including a dedicated page about Asterisk. The trunk is managed in the intra2.axialys.net extranet. The operator itself recommends IP authorisation and calls the password mode less secure and more capricious.

What to enter in the admin panel

What to set up at the provider: create a SIP account → hand over the static IP of your PBX from the "Server" tab for address-based authorisation → choose the number format (the PBX handles any of them) → keep G.711 a-law among the codecs → agree on the list of numbers allowed for presentation.

Pitfalls ⚠️ In REGISTER mode there is no way to pass the presented number: the From field there must contain the SIP account identifier, and the operator reads the number only from service headers that our PBX does not send. For Axialys choose IP authorisation. The operator has two SBCs, primary and backup, and incoming calls may arrive from both: create a second trunk entry for the backup address, otherwise some calls will not be recognised. After creating the SIP account in the interface, wait about 10 minutes before configuring the PBX, otherwise failed authorisation attempts will get your address temporarily blocked. Call transfer and hold over SIP are not supported by the operator. Source: Guide technique Trunk SIP, Configurer un Asterisk softswitch — 09.09.2026.

Dstny France (ex-OpenIP)#

The French arm of the Belgian Dstny group; the OpenIP brand lives on in the MyOpenIP portal. The product is SIP Trunk Touch, and the wiki with the parameters is public. It is sold through integration partners, there is no direct online purchase.

What to enter in the admin panel

What to set up at the provider: obtain the trunk from a Dstny partner → generate the password in MyOpenIP → add the public IP of your PBX to "IP permises" → choose the number format the trunk delivers to the PBX (+33 is the most convenient) → configure emergency calls at the trunk level.

Pitfalls ⚠️ The trunk password cannot be viewed — only regenerated, and regeneration instantly breaks a working trunk: do it at the same time as editing the trunk in the admin panel. Emergency calls carrying an individual employee's number are taken by the operator from a service header that our PBX does not send, so the trunk-level setting will apply, that is the contract address. The codecs are G.711 a-law and G.729, DTMF is RFC 2833. Source: SIP Trunk Touch — Paramétrage — 09.09.2026.

Contract-only providers and those that will not work#

These operators do have a SIP trunk, but the parameters are issued after a contract — or the trunk does not reach a cloud PBX at all. There can be no "what to enter" table here: ask the account manager for the parameters using the list from "What to ask the provider" and enter them into the same form as for the others.

• Sewan — an operator with the Sophia platform, resold by dozens of integrators under their own brands. The SBC address, the login and the password are issued in the Sophia portal (at a reseller — in its own portal), and the list of permitted addresses of your PBX is entered there as well. There is no public technical guide: demand a "fiche de configuration" from the supplier.
• SFR Business — only TSIP OTT fits, the trunk over the ordinary internet; TSIP MPLS lives inside the operator's own network and will not reach a cloud PBX. The mode is IP authorisation: the PBX needs a public static address, which is also what you hand to the operator. There is a single codec, G.711 a-law; the calling number is mandatory and is carried in the national format. The SBC address is issued with the project, and there is no public specification for mainland France — demand it from the account manager before going live.
• Free Pro (XPR) — the only French operator with a full access specification published on the open web, which is also what explains why it does not suit us: the service assumes at least 30 SIP channels and is delivered over a dedicated link, and "these services cannot be delivered from a third-party operator's network". Asterisk is absent from the list of certified systems.
• Bouygues Telecom Business — the "Bsip" offer, a trunk to your own PABX or IPBX over the existing internet access. There are no public SIP parameters, everything is in the configuration sheet issued with the order. For a venue with 1–4 channels this is the same product as Keyyo but without public documentation: if the choice is free, take Keyyo.
• Orange Business — "Business Talk IP" only arrives over the Orange network (the site's BVPN link). For a PBX in the cloud that would mean a separate link into the cloud, that is expensive and slow. If the venue already has this trunk, a second one from an internet operator is cheaper.
• Kavkom and Sipleo — cloud PBXs with French numbers. The word "trunk" is present in their marketing, but there is no public description of connecting a third-party PBX: ask the supplier directly.

International providers with French numbers#

French numbers are sold by Telnyx, Twilio, DIDWW, Bandwidth, Zadarma, Sonetel and didlogic. For a foreign company this is often the simplest route: in France almost all local operators sell the trunk through a quote and a partner, and self-service exists only at OVHcloud, ippi and boxIP.

• Documents will be asked for anyway. For a French geographic number Telnyx requires an address in France and a proof of address no older than three months, a copy of an identity document (for an individual) or a company registration extract, and for toll-free 800 numbers also a SIREN and business use only; processing takes about 72 hours. For EU citizens a passport or ID card of any Union country is accepted.
• The modes differ. Telnyx and DIDWW offer both registration and a static IP endpoint; Twilio Elastic SIP Trunking works over IP only — you will need the static address of the PBX from the "Server" tab; Zadarma uses registration. The Zadarma, Telnyx and Twilio cards are already in the catalogue when adding a provider: the server address and the mode are filled in automatically.

Number porting#

• Porting works by the RIO code (Relevé d'Identité Opérateur). The code is issued by your current operator, and the request is filed with the new one — the operator you are moving to.
• Typical reasons for a rejection: a wrong RIO code, a contract termination already started at the previous operator, a different contract holder in the old and the new contract (a number registered to a former director is the most frequent case), and errors in the paperwork. Technology breaks here less often than documents do.
• The switch happens on an agreed date and time window, usually in the morning, with a few minutes of interruption.
• A released number cannot be given to another subscriber earlier than 45 days after termination — under the ARCEP decision in force since 01.01.2026. If you left and changed your mind, the number is most likely still free.
• Belgian numbers are ported by OVHcloud through a separate procedure (Easy Switch) — in the same portal, if the chain has a location in Belgium.

Rules and documents#

If it does not work#

1. OVHcloud: registration is there, outgoing calls are not. Almost certainly the identity validation procedure has not been completed — until then the operator blocks calls to the outside. Check the status in the portal; incoming calls work meanwhile.
2. Axialys: calls go out without a number or get rejected. The trunk is configured in REGISTER mode, where the From field is occupied by the account identifier. Switch the trunk to IP mode and hand the static address of the PBX to the operator.
3. Some incoming calls do not arrive. Axialys has two SBCs, Free Pro has Paris and Marseille: calls come from both addresses, while a trunk recognises incoming calls by its own SIP host. Create a second trunk entry for the backup address.
4. Keyyo: no registration although the login and password are correct. The "SIP host" field contains keyyo.net instead of <custid>.lb.keyyo.net — registration goes to the customer's personal address.
5. The call connects but there is silence. Only G.729 has been negotiated on the account, and the PBX does not understand it: ask for G.711 a-law to be enabled. At boxIP, SFR Business and Free Pro only a-law is available — there will be audio, but not HD.
6. Outgoing calls are rejected or leave with a withheld number. The number in the "Show as" field is not on the list permitted by the contract, or the "Rester anonyme" mode is enabled in the OVHcloud portal, which overrides whatever the PBX sends.
7. Two numbers land on the same line. The last seven digits of a French number do not contain the zone code, so numbers from different ranges may share a tail. Separate such lines manually.

Causes that do not depend on the country are in "If calls do not go through"; the SIP trace in the trunk menu is described there too. Checking the address and the port — "Test the connection", transport and codec requirements — "Network and compatibility".

FAQ#

Which operator should I choose if nothing is connected yet?#

OVHcloud SIP Trunk: ordered online, €4 excl. VAT per month per channel, works in registration mode to siptrunk.ovh.net and offers exactly the codecs the PBX speaks. If you need a single number and something cheaper — ippi or boxIP. If the venue plans to grow and needs a trunk with address-based authorisation — Axialys or Dstny France.

Do I need a French company to get a number?#

For a local operator, yes: the contract is signed with a French entity (SIREN/SIRET). At OVHcloud the account can be opened for a European legal entity, but identity validation still has to be completed. A foreign company without French registration will find it easier to take a +33 number from an international provider: it accepts a proof of address rather than an extract from the French register.

Can I present a different number on outgoing calls?#

Only one that is written into the contract with the operator. Since 01.01.2026 the operator is obliged to restrict the list of presented numbers technically, and the network drops unauthenticated calls. In France someone else's number is not "not recommended" — it physically will not go through.

Why will a trunk from Orange or SFR MPLS not work?#

Because it arrives over the operator's own network — over a BVPN or MPLS link to the venue's site rather than over the internet. Our PBX stands in the cloud, and such a trunk can only reach it through a separate link into the cloud. SFR has a solution: order TSIP OTT, the variant over the ordinary internet, not MPLS.

How many channels does a venue need?#

A channel is one simultaneous conversation. A restaurant usually needs 2–4: one is busy with a guest, another with a courier or a supplier. At OVHcloud a channel costs €4 excl. VAT per month and is added in the portal, at boxIP the channels are part of the plan. Free Pro, however, sells the trunk from 30 channels only — that is about a chain, not a single venue.

Sources#

All links checked on 09.09.2026.

Operators

• OVHcloud — Asterisk, configuration et utilisation: https://docs.ovhcloud.com/fr/telephony/asterisk_configuration_et_utilisation/
• OVHcloud — identity validation procedure for VoIP services: https://docs.ovhcloud.com/fr/telephony/la_procedure_de_validation_voip/
• OVHcloud — VoIP FAQ (codecs, RIO, porting): https://docs.ovhcloud.com/fr/telephony/faq-voip/
• OVHcloud — SIP Trunk pricing: https://www.ovhcloud.com/fr/phone/sip-trunk/
• ippi — FAQ with SIP parameters and a configuration example: https://www.ippi.com/frequently-asked-question/
• boxIP — configuring a SIP trunk for making and receiving calls: https://boxip.fr/doc/configurer-un-trunk-sip-pour-emettre-et-recevoir-des-appels/
• boxIP — Trunk SIP pricing: https://boxip.fr/abonnements-trunk-sip/
• Keyyo — Paramètres SIP et recommandations VoIP: https://docs.keyyo.com/docs/telephonie-fixe/expert/parametres-sip/
• Keyyo — Asterisk configuration (PDF): https://www.keyyo.com/fr/support/Keyyo_Asterisk.pdf
• Axialys — Guide technique Trunk SIP: https://guide.axialys.com/guide/guide-technique-trunk-sip/
• Axialys — Configurer un Asterisk softswitch: https://guide.axialys.com/guide/configurer-un-asterisk-softswitch/
• Dstny France — SIP Trunk Touch, Paramétrage: https://wiki.dstny.fr/doku.php?id=sip_trunk_touch:parametrages:start
• Free Pro — Caractéristiques techniques d'accès au service Trunk SIP: https://xpr.freepro.com/docs/trunk-sip/caracteristiques-techniques-dacces-au-service-trunk-sip/
• SFR / Outremer Telecom — STAS Trunk SIP (PDF): https://business.sfrcaraibe.fr/wp-content/uploads/2025/06/stas_client_telephonie_sip_sfr.pdf
• Sewan — "Trunk SIP" in the operator's glossary: https://www.sewan.fr/fr-fr/lexique/trunk-sip/
• Bouygues Telecom Business — Trunk SIP pour IPBX: https://www.bouyguestelecom-business.fr/telephonie/trunk-sip/trunk-sip-pour-ipbx/
• Orange Business — Business Talk IP, XiVO guide (PDF): https://documentscontractuels.orange.fr/versions-anglaises_ann_4217.pdf
• Telnyx — France DID requirements: https://support.telnyx.com/en/articles/1311445-france-did-requirements

Regulator and law

• ARCEP — the numbering plan: https://www.arcep.fr/la-regulation/grands-dossiers-thematiques-transverses/la-numerotation.html
• ARCEP — press release on the numbering plan of 02.12.2025 (number authentication, presentation limits, 45 days): https://www.arcep.fr/actualites/actualites-et-communiques/detail/n/plan-de-numerotation-021225.html
• ARCEP — the numbering plan, revision of 02.12.2025 (PDF): https://www.arcep.fr/fileadmin/user_upload/86-25-version-francaise.pdf

Related pages#

• Connecting a provider's number to the PBX — general steps, trunk modes, network, connection test.
• Setting up SIP phones — how to connect desk phones and DECT to extensions.