Bitrix24 Integration with FreePBX: Setup, Cases, Timelines

Companies using FreePBX — the graphical interface for Asterisk — often lose call data: calls are not logged in CRM, history disappears, managers manually enter contacts. Industry statistics indicate that up to 20% of inbound leads remain unprocessed without telephony integration. We solve this through a direct link between FreePBX and Bitrix24 using AGI scripts or an AMI daemon. The AGI script utilizes the FastAGI protocol to maintain persistent connections, thereby reducing per-call latency and improving scalability under load. Every call automatically creates a CRM record; the recording attaches to the deal; missed calls become leads. After implementation, call processing conversion grows by 30–40%, and quality control time halves. We use PHP 8.1, Bitrix24 REST API, and AGI/AMI scripts that handle up to 100 concurrent calls without event loss. Manual contact entry can be reduced by up to 20 hours per month, and the integration pays for itself through increased lead handling. The integration typically saves businesses $1,500–$2,000 per month in lost lead recovery costs. With an average lead value of $100, recovering just 20 more leads per month ($2,000) covers the integration cost within the first month.

Bitrix24 FreePBX Integration: Key Problems Solved

Do-it-yourself integration often leads to critical errors. Here are three main issues.

• Incorrect queue mapping. If a call from the support queue lands in the CRM as a sales call, routing suffers. We bind each FreePBX queue to a specific direction via LINE_NUMBER — eliminating confusion.
• Delays in call recording. FreePBX automatically converts WAV to MP3 via cron. If the conversion isn't finished, an empty file loads into CRM. We configure waiting and verification of recording readiness using call detail records (CDR) and queue log analysis.
• Event loss under high load. The AMI can overflow. We implement an event ring buffer and buffering — guaranteeing that no call goes unregistered.

How Bitrix24 FreePBX Integration Works via AGI and AMI

AGI (Asterisk Gateway Interface) is a protocol for calling external scripts from the Asterisk dialplan. In FreePBX we add a call to a custom context:

[from-internal-custom]
exten => _.,1,AGI(bitrix24.php,${EXTEN},${CALLERID(num)},${UNIQUEID})
exten => _.,n,Return()

The PHP 8.1+ script receives three parameters and calls the Bitrix24 REST API: telephony.externalcall.register, telephony.externalcall.finish. For inbound calls we use from-trunk-custom. The code includes unit tests for compatibility with FreePBX 14–16. AGI event processing is 5× faster than AMI without buffering, thanks to direct invocation and synchronous execution within the dialplan.

Comparison of AGI and AMI

Why Bitrix24 FreePBX Integration Queue Mapping Is Critical for CRM

FreePBX allows an unlimited number of queues. We set up an AMI daemon that reads the channel variable QUEUE_NAME and passes it to the CRM. The integration leverages Asterisk's call event architecture, utilizing the chan_dahdi and app_queue modules to ensure synchronous data transfer. Mapping table:

This lets Bitrix24 automatically assign the responsible person and create deals in the correct pipeline.

Case: Law Firm with 6‑Department IVR

The client used FreePBX 15 with multi‑level IVR. Problem: when a call started, a CRM card was created, but if the caller hung up during the menu, an empty call remained — 40% of all inbound calls. We moved the AGI script call from the trunk context to the queue context. Now telephony.externalcall.register triggers only after the caller selects a department and enters the queue. Additionally, we set a trigger: if the caller drops in the queue, a lead is created with the tag “Awaiting call” — a Bitrix24 robot initiates a callback after 5 minutes. Implementation took 6 working days. After deployment, inbound call processing conversion increased from 55% to 82% in the first month. This resulted in an estimated $2,300 additional monthly revenue from recovered leads.

What’s Included and Estimated Timelines

Deliverables

• Audit of FreePBX configuration and Bitrix24 version.
• Design of queue and event mapping scheme.
• Development of AGI/AMI scripts in PHP 8.1+ with unit tests.
• Configuration of call recording and conversion.
• Load testing (up to 100 concurrent calls).
• Administrator training: how to change queue settings without redoing the integration.
• 3‑month workmanship warranty.
• Documentation and user access.

Pricing: standard integration starts at $1,200.

Process

1. Analysis — study dialplan, queues, and IVR (1–2 days).
2. Design — agree on specifications, choose protocol, prototype (1–2 days).
3. Implementation — develop and configure on test environment (2–3 days).
4. Testing — load tests, edge cases (1 day).
5. Deployment and training — move to production, provide instructions (1 day).

A basic integration takes 3 to 5 working days. Complex cases with multi‑level IVR or non‑standard recording take up to 10 working days.

Trust Your Bitrix24 FreePBX Integration to Professionals

Our team holds Bitrix certifications and has completed over 30 FreePBX integration projects. The queue mapping we configure reduces call loss three‑fold compared to standard configuration. Request an audit of your PBX and receive a preliminary integration plan. Contact us for a consultation — we will help set up the FreePBX and Bitrix24 link for your business.

Turnkey Telephony Setup: From SIP to CRM

SIP trunk not registering — the first problem when connecting telephony to Bitrix24. The client sends provider data, you enter it in "Telephony → Telephony Settings → SIP Connector", and the status hangs "Waiting for registration". Ports 5060/5061 for SIP and range 10000–20000 for RTP are blocked on the firewall — classic. Or codec G.729 is not supported, and G.711 consumes 87 kbit/s per line. For 20 simultaneous conversations — count yourself. We connect and configure telephony so that calls are not lost, routing works according to business logic, and CRM receives data automatically.

SIP (Session Initiation Protocol) — standard for voice communication over the internet. Our specialists have 5+ years of experience integrating with Bitrix24. Warranty on configured solutions — 1 year. Contact us for a free audit of your current infrastructure — we often find blind spots: missed calls without tasks, managers with status "On line" and zero calls, IVR branches that no one reaches.

How to Avoid Failures in SIP Registration and Connection?

Improper NAT, closed ports, or incompatible codecs — 90% of failures. We check codec support on the operator's side, configure keepalive and backup SIP servers. After setup, registration stays stable for months.

You already have a contract with an operator, and changing numbers is not an option. We connect to Bitrix24 via SIP connector. For stable operation, you need a channel: at least 100 kbit/s per line for G.729, 87 kbit/s for G.711a.

Typical tasks:

• City numbers from any operator — preserved when switching to B24
• 8-800 numbers for inbound — routing via CRM
• Multi-line numbers with department distribution via IVR
• Analog lines via Grandstream or Linksys VoIP gateways

Where it usually gets stuck:

• SIP/RTP ports are closed at the provider or router level
• NAT not forwarded correctly — one-way audio
• Different codecs on the PBX and Bitrix side — no audio at all

We solve these problems in 1–3 days, not weeks.

Step-by-step instructions for connecting via SIP trunk:

1. Check SIP (5060/5061) and RTP (10000–20000) ports are open on the firewall.
2. Agree on codecs: G.711 or G.729 — test both options.
3. Configure SIP connector in Bitrix24 admin: login, password, provider domain/IP.
4. Enable keepalive (30–60 second interval) for stable registration.
5. Test two-way audio with a test call.
6. Configure backup SIP server in case of primary failure.

Cloud PBX or SIP Trunk: Which to Choose?

Cloud PBX requires no hardware — set up in 1–2 days. SIP trunk retains your numbers and allows a hybrid scheme with an on-premise PBX. Cloud PBX is configured 2-3 times faster and saves up to 40% of budget compared to maintaining your own infrastructure. Compare providers based on real cases.

Why Do You Need Call Recording and How to Set It Up?

All incoming and outgoing calls are recorded automatically. Storage — Bitrix24 cloud (tariff limited) or your own server via the voximplant module. Each recording is attached to a CRM card: contact, deal, lead. Listening — from the deal timeline.

Control tools:

• Recording notification — mandatory under 152-FZ, configured in IVR
• AI transcription — speech recognition via built-in CoPilot module or external service. Converts calls to text, searchable by keywords
• Sentiment analysis — system flags negative calls. Not a replacement for listening, but filters 90% of routine
• Selective recording — only incoming, only specific departments
• Automatic duration control — calls shorter than 15 seconds almost always indicate a problem: dropped, not reached, manager didn't pick up

Manager sees summary reports: number of calls per manager, average duration, missed calls without callbacks. The last point is the most painful: a missed call without a callback task equals a lost client.

Typical Routing Mistakes

Routing is the most fragile part. Set up "in order", but the manager logged in and went to lunch — the call hangs for 40 seconds and drops. Or IVR with five nesting levels — the client hangs up on the third. We use working distribution scenarios:

• By CRM responsible — number found in database, call goes directly to manager
• In order — even load among operators with "On line" status
• By departments via IVR — voice menu, max two levels. More means lost calls
• By time — working/non-working hours, weekends
• By region — detected by number code, distributed to local managers

On incoming call, the system performs: Number found in CRM:

• Route to responsible manager
• Pop-up card: name, company, open deals, contact history
• If manager doesn't answer within 15 seconds — forward to colleague, then to supervisor

Number not found:

• Automatically creates a lead in CRM (setting Telephony → CRM Integration → Create lead for unknown number)
• Call distributed by queue
• All information recorded for later processing

How to Automate Work with CRM Integration?

Pop-up card on incoming call shows:

• Name, company, position
• Current deals with statuses
• Last 5 interactions — calls, emails, chats
• Customer comments
• Buttons: "Create deal", "Set task", "Transfer call"

Automation via business processes is configured in "CRM → Robots and triggers":

• Missed call → lead + callback task for responsible
• Call end → record activity in deal timeline
• Missed without callback within 30 minutes → notify supervisor
• Incoming from client with overdue deal → escalation

Analytics available in "Telephony → Balance and statistics" and CRM reports:

• Number of calls by manager, department, direction
• Average duration and hold time
• Missed call percentage with weekly trend
• Call-to-deal conversion — most important metric for sales

How to Increase Conversion with Callback, Auto-dialer, and Voice Menu?

"Call me back" widget on website — one field (phone), nothing extra. The system calls the manager first, then the client. Each request automatically creates a lead in CRM. Anti-spam: limit requests from one number. A/B testing placement — widget bottom right converts better than left, but depends on design. Callback reduces missed calls by up to 30% compared to manual dialing.

Auto-dialer:

• Dial segment from CRM — manager connects after client answers
• Robotic dial with voice message — order confirmations, appointment reminders
• IVR scenarios: "press 1 to confirm"
• Scheduled with time zone awareness — module checks region by number code

Building a voice menu:

• Welcome message — company name, recording notice
• Department selection via DTMF — max 4–5 items
• Music on hold with queue position
• Non-working hours — voicemail or informational message

Recording by professional voice actor — worthwhile for greeting and main menu. Deeper levels — speech synthesis, easier to update.

What's Included in Telephony Setup?

Deliverables after project completion:

• Configured SIP registration (cloud PBX or SIP trunk turnkey)
• Working call routing (by CRM, queue, IVR)
• Call recording with cloud or server storage
• CRM integration: pop-up cards, auto lead creation, business processes
• Callback widget on website
• Voice menu (IVR) with voice actor recording or synthesis
• Configuration documentation and staff training (2 sessions)
• Technical support for one month after launch

Everything included in the comprehensive setup — no hidden extras. Order telephony setup and get a ready-made infrastructure for working with clients.

Setup Timeline and Pricing

Pricing is calculated individually — depends on number of lines, routing complexity, and required integrations. Average budget for setup ranges from several thousand to tens of thousands in local currency depending on scope. We'll evaluate your project in 1 day. Start with a free audit of your current infrastructure — we often find blind spots: missed calls without tasks, managers with "On line" status and zero calls, IVR branches that no one reaches. Contact us for a consultation — we'll offer the optimal solution for your budget and business processes.