This is a build-to-order module with a typical lead time of one working week from kickoff, depending on scope (single site vs. multi-queue, recording integration, custom automations). After purchase we run a short discovery call to capture your Asterisk/FreePBX version, dial plan, extension map and CRM matching rules, then develop, deploy to a staging Odoo, run UAT with your live extensions, and go live after your sign-off. There is no instant download — you're buying a tailored, installed and tested integration, not an off-the-shelf ZIP.

Every build includes a post-go-live support window covering bug fixes and configuration adjustments for the delivered scope, plus compatibility maintenance across Odoo 17, 18 and 19 so an Odoo upgrade doesn't break your CTI. You receive the full module source code, so you're never locked in. Extended support or a maintenance retainer, plus new-feature work, is available and quoted separately.

Yes. The connector talks to Asterisk via the Asterisk Manager Interface (AMI) or ARI, which FreePBX exposes as well, so it works with standard FreePBX and raw Asterisk deployments. On the Odoo side it runs on both Community and Enterprise editions and is delivered and tested against Odoo 17, 18 and 19. During discovery we confirm your exact versions and any PBX modules (queues, recording) so the build matches your environment.

When your extension rings, Asterisk emits an event over the secure WebSocket (WSS) bridge. The Odoo module normalises the caller ID (E.164/national) and searches res.partner and crm.lead phone and mobile fields for a match, then pops the record for the agent who received the call. If no match is found, it can optionally create a lead or activity from the unknown number so the opportunity isn't lost. Matching rules and normalisation are configured to your data during the build.

Yes. Real-time events flow over an encrypted WebSocket (WSS) channel, AMI/ARI credentials are stored server-side (never in the browser), and access to call-log data is governed by Odoo security — ir.model.access.csv access rights plus record rules that scope calls per company and per user. In a multi-company Odoo, each company's calls and extensions stay isolated. We also handle reverse-proxy, certificate and NAT configuration as part of deployment.

Yes. Call events are written to Odoo where automated actions and server actions can create follow-up activities, tag opportunities, escalate helpdesk tickets or fire webhooks. Because the module posts to the record's mail.thread chatter and exposes a documented XML-RPC / JSON-RPC surface, external dashboards, wallboards or dialers can read call data or originate calls programmatically. Custom automations are scoped during discovery.