If your agents run FreeSWITCH but your customer data lives in Odoo, every call means alt-tabbing: copy a number from a partner form, dial it by hand on a softphone, then type notes back into the CRM after hangup. Inbound calls are worse — the phone rings with just a caller ID and nobody knows which res.partner, open opportunity, or helpdesk ticket it belongs to until they've asked the customer to repeat themselves. Odoo's native VoIP is built around its own Enterprise softphone and the paid Axivox/OnSIP connectors; there is no supported bridge to a self-hosted FreeSWITCH switch, so the ESL event stream, your dialplan, and your call recordings stay completely invisible to Odoo. That gap is exactly where this connector lives.

ECOSIRE builds a dedicated Odoo module that opens a persistent Event Socket Library (ESL) connection to your FreeSWITCH server and translates its events into Odoo records. Click-to-dial is wired into partner, lead/opportunity, and helpdesk phone fields via an OWL widget that fires an originate command through ESL to ring the agent's extension first, then the customer. Inbound CHANNEL_CREATE/CHANNEL_ANSWER events are matched against res.partner.phone/mobile (with configurable E.164 normalization) so a screen-pop opens the right partner, opportunity, or ticket the instant the phone rings. Every call writes a freeswitch.call.log record — a proper models.Model with @api.depends computed talk-time, direction, agent, disposition, and Many2one links back to the partner and originating document — and if you record calls, the log carries a link (or attachment) to the recording so it is one click from the CRM timeline. Access is governed by ir.model.access.csv plus record rules so agents see their own calls while supervisors see the queue, and QWeb reports plus optional automated actions turn raw call events into follow-up activities and daily agent summaries.

Technically, the connector is a real Odoo addon with a clean __manifest__.py declaring its dependencies (base, mail, crm, optionally helpdesk/sale), Python ORM models, XML and OWL views, and security definitions — no core patches, so it upgrades cleanly. The ESL listener runs as a managed background worker (a long-lived connection with reconnect/backoff), and outbound actions are also exposed over Odoo's JSON-RPC/XML-RPC API so a wallboard or external dialer can trigger calls. Queue and agent statistics (mod_callcenter events, if you use it) are aggregated into dashboards for live and historical agent performance. We target Odoo 17.0, 18.0 and 19.0; the module works on Community and Enterprise, and where your edition has Helpdesk or Field Service we wire screen-pop and logging into those documents too.

Because every FreeSWITCH deployment is different — your dialplan, your extension scheme, whether you run mod_callcenter, how recordings are stored, and which Odoo apps agents actually work in — this is delivered build-to-order rather than as an instant download. We start with a short scoping call to map your dialplan, ESL credentials, number-normalization rules, and the exact CRM/Helpdesk flows you want. From confirmed scope, typical delivery is one working week: we build against your requirements, demo on a staging instance for UAT, then install on production with a rollback plan and hand over the git repository and documentation. You get source code for your Odoo version, a training session, and a post-go-live support window — no fabricated benchmarks, just a module built and supported by an Odoo engineering team.