Which cloud PBX providers actually integrate with Odoo, how each one connects, what the integration costs and where call recordings are stored.
A PBX is the system that decides what happens to a call. Who it rings, in what order, what the caller hears, and what gets recorded. There are three shapes on the market, and they behave very differently when you ask them to talk to Odoo.
This is the part most articles get wrong, so it is worth being precise.
Odoo ships a telephony app. In Odoo 19 it is called Phone and sits under Productivity. In Odoo 18 and earlier the same app is called VoIP.
What it is not is a phone system. The Phone app is a softphone panel and a set of hooks into Odoo records. It has no call routing, no IVR, no queues, no numbers and no carrier. It needs a real PBX or SIP provider behind it.
There is a second limit that catches people out. On Odoo's own editions comparison, VoIP sits in the Enterprise column. If you run Odoo Community, the built-in telephony app is not yours to use. That is precisely why the community voip_oca module exists, and why a provider that ships its own module, such as Voxbi, can serve Community users when Odoo's own app cannot.
Odoo names three providers for the Phone app, and it is worth quoting exactly. The Odoo 19 documentation says: "Odoo supports three verified providers by default: Axivox, DIDWW, and OnSIP." That is a short list, it is not a ranking, and it is not the whole market. Plenty of providers integrate with Odoo through their own module or their own API instead. The section on the ranking below explains how to tell those apart.
Who actually uses it. Odoo's spread is unusual. The One App Free tier and the open-source Community edition put it inside very small companies, often with one or two users and one app. The Standard and Custom tiers, sold through a partner network of more than 21,000 firms, put it inside mid-market manufacturers, distributors, retailers and service companies. It is heavily used in Belgium, France, the Netherlands, Luxembourg and Germany, which is the same footprint as most European cloud PBX providers. That overlap is why Odoo telephony integration is a competitive battleground in the Greater Region and not a niche request.
There are three ways this is done, and knowing which one a provider uses tells you most of what you need to know about it.
Odoo has around 50 main applications. Only some of them care about the telephone. These are the ones where a connected phone system changes daily work.
Odoo competes in a crowded market. This is the short version, for context rather than as a buying guide.
SAP. Business One for smaller companies, S/4HANA above it. The deepest functionality in manufacturing and finance, the highest cost and the longest implementations.
Microsoft Dynamics 365 Business Central. Strong where a company already runs Microsoft 365, sold through a large partner channel.
Oracle NetSuite. Cloud-only, popular with fast-growing and multi-entity companies, priced well above Odoo.
Zoho One. The closest thing to Odoo's "everything for one per-user price" model, lighter on manufacturing and inventory.
Sage and ERPNext. Sage holds a large installed base in accounting-led deployments. ERPNext is the other serious open-source option.
Odoo's position between them is consistent: broader than the small-business tools, cheaper and faster to deploy than the large incumbents, and the only one of the group with a genuinely open-source core.
Odoo does not run a telephony partner programme. There is no "approved cloud PBX" directory, and the partner finder on odoo.com filters by industry, grade and country only. So the phrase "works with Odoo" is unpoliced, and a lot of vendors use it loosely.
There are only three ways a provider can genuinely claim it, and telling them apart is most of the work of choosing.
That is also the answer to the question of why the shortlist looks the way it does. We started from the three providers Odoo verifies, added every provider that builds its own integration, and included the partner-built ones so you can see where they land.
A "best of" list on a vendor's own blog is worth exactly as much as its method, so here is ours in full.
We score each provider on six things a buyer can check without talking to a salesperson. Every cell comes from the provider's own published pages, checked on 10 September 2026. Nothing is estimated, and where a provider does not publish something we score it as not published rather than guessing.
| Rank | Provider | Score | Entry price as published |
|---|---|---|---|
| 1 | Voxbi | 7/7 | €2.90 per user per month |
| 2 | JustCall | 5/7 | \$29 per user per month |
| 3 | DIDWW | 5/7 | Usage rate cards |
| 4 | VoIPstudio | 4/7 | \$6 per user per month |
| 5 | sipgate | 4/7 | €12.95 per user per month |
| 6 | OnSIP | 4/7 | \$18.95 per user per month |
| 7 | Ringover | 4/7 | €47 per user per month |
| 8 | Zadarma | 3/7 | Integration free, calls per minute |
| 9 | voip_oca and your own PBX | 3/7 | Free module |
| 10 | Placetel | 3/7 | €7.90 per user for the connector, plus a plan |
| 11 | CloudTalk | 3/7 | €29 per user per month |
| 12 | 3CX | 3/7 | €760 per system per year at 16 calls |
| 13 | Aircall | 3/7 | Not published |
| 14 | Axivox | 3/7 | Not published |
| 15 | Wildix | 1/7 | Not published |
| 16 | Telavox | 1/7 | Not published |
| 17 | Dstny | 1/7 | Not published |
| 18 | NFON | 1/7 | Not published |
🇱🇺 Luxembourg. The only provider on this list that publishes all six things. Its own module, installed automatically from the Voxbi Cockpit, on Odoo 16 to 19, on Odoo Online, Odoo.sh and self-hosted, and on Odoo Community too. €2.90 per user per month on Voxbi Plus, numbers €2.00, EU hosting by default, and named SLAs on the managed tiers.
Watch for: on Odoo Online the module counts as custom code, which adds about €32 a month. That is not a Voxbi charge, it is Odoo's, and it does not apply on Odoo.sh or self-hosted.
Best for: companies that want the integration to work on day one and want to check the terms before a sales call.
🇺🇸 United States and India. Built by JustCall, no third-party module, and it is the only provider besides Voxbi that publishes both a version requirement and an SLA. Its help pages state "Your Odoo CRM account must be on Odoo version 18 or above" and the integration is included from the Team plan at $29 per user per month.
Watch for: no EU data residency statement. The module sold under JustCall's name on the Odoo apps store is actually Serpent Consulting's at €400, which is not the official path.
Best for: teams already on JustCall.
🇮🇪 DIDWW Ireland Limited, Dublin. One of Odoo's three verified providers, with published rate cards and a claimed 99.998 percent network uptime.
Watch for: this is a carrier, not a phone system. You get numbers and SIP trunking. Routing, queues, recording and a helpdesk are not part of it, and it needs Odoo's Phone app, which means Odoo Enterprise.
Best for: buyers who need numbers in a lot of countries and already have a PBX.
🇬🇧 United Kingdom. The cheapest published per-user price on this page at $6 per user per month pay as you go, and a published 99.99 percent uptime guarantee.
Watch for: the documented setup points Odoo's own VoIP app at a VoIPstudio WebSocket address, so it needs Odoo Enterprise in practice. VoIPstudio does not say so, and it publishes no Odoo version support at all.
Best for: price-led buyers on Odoo Enterprise who are willing to test the setup themselves.
🇩🇪 Germany. Built in house, runs inside the sipgate app, and German data location. €12.95 per user per month on business S.
Watch for: sipgate publishes no Odoo version support and no edition statement. Its own help article notes the API key route needs Odoo's Custom subscription, which is Odoo's most expensive tier.
Best for: German companies that want a German provider.
🇺🇸 United States. An Odoo verified provider with a clear $18.95 per user per month price.
Watch for: the Odoo 19 documentation is explicit that "OnSIP VoIP services are available in the United States (US) only. A US billing address and US credit card are required to use the service." For a European buyer that is not a caveat, it is a full stop.
Best for: United States companies only.
🇫🇷 France. One of only two providers that publish their own module on the Odoo apps store, ringover_dialer, covering Odoo 14 to 19.
Watch for: €47 per user per month on Business, three users minimum on a twelve month commitment, which is the highest published per-user price here. Ringover's pricing page never actually names Odoo. And if you are in a regulated sector, read Ringover's general terms first, because they disclaim suitability for critical functions, which is a live question under DORA in the Luxembourg financial sector.
Best for: French sales teams that want a dialler and are not price sensitive.
☎️ Zadarma builds its own integration, states it "works without additional modules and intermediaries" and is "completely free", but publishes no version support, no edition, no residency and no SLA. CloudTalk publishes its own module and names the tier on its Odoo page, a CloudTalk Essential plan at €29 per user per month, but nothing else. 3CX has been natively integrated with Odoo CRM since Version 20 Update 10, which is a genuinely good route if you already run 3CX, though it needs the AI or Pro edition and is priced per system rather than per user, at €760 a year for Pro at sixteen simultaneous calls. voip_oca is free and open source, works on Community, and covers Odoo 17 to 19, but you bring the PBX, the numbers and the maintenance. Placetel and Aircall are partner-built, as described above. Axivox is the interesting case and gets its own note below.
📉 Wildix, Telavox, Dstny and NFON publish no price, no Odoo version support and no residency or SLA statement, and none of them builds the integration itself. NFON's CRM Connect page still lists Odoo Enterprise versions 8 to 14, which are all out of support. Telavox's integration is contact lookup only, and its Odoo module has been unpublished. A low score here is a statement about what these vendors publish, not about how their platforms perform.
Most Odoo telephony articles quote a per-user price and stop. That number is never the bill. Here is the full stack, using published rates checked on 10 September 2026.
What it does inside Odoo
Logs inbound and outbound calls automatically with time, duration, direction and handler
Turns any phone number in Odoo into a click-to-call link
Shows caller name, company, recent calls, tickets and activities while the phone is ringing
Attaches AI transcripts and summaries to the record
Adds an AI topic, keywords, labels and an NPS score to each logged call
Shows caller information on supported desk phones
Read the documentation
Setup guide: Connect Odoo to Voxbi
Integration overview: Odoo VoIP integration
Odoo Community: Odoo Community Edition VoIP integration
API reference: docs.voxbi.com
Odoo 20 is released during Odoo Experience 2026, which runs from 24 to 26 September 2026 at Brussels Expo. If you are choosing a phone system this month, ask every provider one question: when will you support Odoo 20?
| Odoo version | Telephony app name | Notes |
|---|---|---|
| 16 | VoIP | Supported by Voxbi |
| 17 | VoIP | Supported by Voxbi and voip_oca |
| 18 | VoIP | Supported by Voxbi and voip_oca |
| 19 | Phone | Current version. Voxbi and voip_oca. Axivox documented in depth by Odoo |
| 20 | To be confirmed | Releasing 24 to 26 September 2026. Confirm provider support before you commit |
Where is Odoo hosted? Odoo Online, Odoo.sh or self-hosted changes which providers are even possible and whether a custom-code fee applies.
Which Odoo version are you on, and when will you move to 20? Ask for the provider's Odoo 20 date in writing.
Enterprise or Community? Some providers support Community only on self-hosted. Some not at all.
How many numbers do you actually need? Usually one per company, not one per user. Check that any quote reflects this.
Which countries do you need numbers in? Coverage varies a lot and it is the most common reason a shortlist collapses.
Where will call recordings, transcripts and AI output be stored? Ask for the region for each of the three separately, because they are often different.
Who maintains the Odoo module? If it is you, price your own time. If it is a third party on the apps store, ask who patches it when Odoo 20 breaks it.
Is there a support contract and an SLA, and what does the SLA actually pay out? Read the credit cap, not the uptime percentage.
What does it cost to leave? Number portability, contract notice period and data export, in that order.
Does Odoo have its own phone system?
No. Odoo has a Phone app, called VoIP before version 19, which is a softphone and a set of links into Odoo records. It has no numbers, no routing, no queues and no carrier. You still need a cloud PBX or a SIP provider behind it.
Is the Odoo VoIP or Phone app available in Community edition?
No. On Odoo's editions comparison, VoIP sits in the Enterprise column. Community users have two routes instead: the free voip_oca module from the OCA, or a provider that ships its own module. Voxbi supports Community on self-hosted installs, using the same module and the same setup as Enterprise.
Which cloud PBX does Odoo officially recommend?
Odoo does not run a telephony partner programme and publishes no approved list. The Odoo 19 documentation does say "Odoo supports three verified providers by default: Axivox, DIDWW, and OnSIP." Axivox is documented in the most depth, across versions 14 to 19. Everything else on the market is either built by the provider or built by a consultancy.
Is a provider's module on the Odoo apps store an official integration?
Not necessarily, and this is the most common mistake. Most telephony connectors on the apps store are published by Odoo consultancies, not by the phone provider. Check the author field. Ringover and CloudTalk publish their own. The Aircall and Wildix integrations are partner-built, and Telavox's has been unpublished entirely.
Can I use a cloud PBX with Odoo Online?
Yes, but check two things. The provider must support Odoo Online, and any module they install counts as custom code, which Odoo charges a monthly maintenance fee for. For the Voxbi module that is around €32 a month.
How long does it take to connect a cloud PBX to Odoo?
With a provider that installs its own module, about fifteen minutes of configuration and roughly an hour for the first sync to complete. Building your own connector against a PBX is a project, not a task.
Will the integration survive an Odoo upgrade?
It depends who maintains the module. A provider-maintained module is updated for each Odoo release. A module you built or a community module you adopted is your responsibility every September.
Do I need a phone number for every user?
Usually not. Cloud PBX extensions sit behind a main company number, so one number per company is the normal starting point. Direct dial numbers per user are an option you add deliberately, not a requirement.
What is the free option?
The OCA module voip_oca is free and AGPL-3 licensed, for Odoo 17, 18 and 19. It is only free in licence terms. You still need a PBX that accepts SIP over WebSocket, numbers, minutes and your own time to run it.
We already have a 3CX or Asterisk system. Do we have to replace it?
No. You can keep it and buy a certified SIP trunk. The trade-off is that the Odoo link is then yours to build and maintain through Odoo's yearly releases.
All figures on this page were checked on 10 September 2026 against the sources below.
Odoo company figures: odoo.com about page
Odoo pricing tiers: odoo.com/pricing
Odoo editions comparison: odoo.com/page/editions
Odoo 19 Phone app, verified providers and the OnSIP United States restriction: Odoo 19 documentation
Odoo Experience 2026 and Odoo 20 release: Odoo Experience 2026
3CX native Odoo CRM integration from Version 20 Update 10: 3CX documentation
Ringover module and pricing: apps.odoo.com ringover_dialer and ringover.com/pricing
CloudTalk plan requirement: cloudtalk.io/odoo and cloudtalk.io/pricing
JustCall version requirement: JustCall help centre
Other provider prices: VoIPstudio, sipgate, OnSIP, 3CX
voip_oca module: OCA apps store
Mixvoip OCA Gold Sponsorship: Odoo Community Association
Voxbi Odoo integration and setup: voxbi.com/integrations/odoo and the setup guide
Voxbi pricing: voxbi.com/pricing
ERP market share estimate: 6sense ERP market share
Prices exclude VAT.
Call logs, metadata and recordings each need their own retention period. This guide shows how to set them by purpose, who owns each one, and what happens when someone deletes a call in an app.
How to set outbound caller ID per user, site or queue, check it across Teams, mobile and softphone, and keep every presented number authorised and authenticated.
Keep every number when you change operator. Build the inventory, match the holder name, let the new operator lead the port and test before the old service ends.
Talk to us or to a certified Voxbi partner.
