Setting Up Call Recording in Bitrix24: Cloud PBX & SIP

We often encounter a situation where 'the client said — the manager said' destroys a deal. Without a call recording, it's impossible to objectively resolve a conflict, train an employee, or confirm an incident. Setting up call recording in Bitrix24 is technically simple but critically important when launching telephony. Mistakes at this stage lead to data loss, wasted time, and client distrust.

Why call recording is not a luxury but a necessity

Recording isn't for total control — it provides material for analyzing complex negotiations, legal protection, and service quality analysis. Even one conflict without a recording can cost more than setting up the entire system. According to our practice, companies that implement recording reduce disputed situations by 40% and save up to 5 hours per month on reviews.

How recording works in cloud PBX and via SIP

Bitrix24 cloud PBX. Everything is enabled with a toggle: 'Telephony' → 'Settings' → 'Call recording' → 'Record all calls'. As noted in the Bitrix24 help desk, recordings are stored in the cloud and automatically attached to CRM items. No scripts — just enable it.

SIP trunk or external PBX. Recording is done on the PBX side (Asterisk, 3CX, etc.), and the file is passed to Bitrix24 via the telephony.externalCall.attachRecord API. Without this, calls will appear in CRM but without audio. This requires configuring a handler on the PBX side — often fails due to incorrect call parameters or missing call-end event. More details on the method can be found in the REST API telephony documentation.

Typical setup mistakes

• Call completed but recording not attached — the API didn't wait for full file upload or the call ID didn't match.
• Duplicate recordings — attachRecord called twice for the same call.
• Empty files — the PBX started recording but the call was dropped before capture.
• Insufficient Drive space — no rotation configured.

All these issues are solvable at the design stage. We guarantee that after setup, recording works without failures and data is not lost.

How we do it (proof of expertise)

We start with an audit of your current telephony and Bitrix24 integration. For a cloud PBX, this takes 30 minutes. For a SIP trunk, we create a file transfer diagram, agree on timeouts and metadata.

Then we develop the handler script on the PBX side (Asterisk dialplan or 3CX Call Flow). The recording is uploaded after the call ends, a POST request is sent to telephony.externalCall.attachRecord with the call ID, file, and start time. We check for a 200 response code — otherwise retry with exponential backoff.

Real case: On a logistics company project handling 200+ calls daily, we reduced recording attachment failures from 15% to under 1% by implementing a retry mechanism and monitoring. The client saved 3 hours per week on manual checks.

Integration with Bitrix24

We create an incoming webhook with telephony permissions (scope telephony). For bulk setup, we use the REST API from a ready-made module. We test with a test call.

Setting up selective recording

If not all calls need recording, we filter on the PBX side: only calls from new clients (not found in CRM) or longer than 30 seconds. The cloud PBX does not offer this flexibility — only a global toggle.

Rotation and storage

We configure automatic deletion of recordings older than N days via a Bitrix24 agent or CRON. Alternatively, export to S3 and attach a link instead of the file. Comparison of options:

How to guarantee recording integrity?

Even with proper setup, failures can occur. We recommend enabling monitoring: an agent checks that at least one file was attached in the last hour. If not, it sends a notification to the admin. This reduces data loss risk to 1%. In our projects, we always include such monitoring.

What's included in the work?

• Audit of current telephony and Bitrix24 integration
• Prototype and technical specification preparation
• Development of recording transfer script (for SIP trunk)
• Cloud PBX configuration (if applicable)
• Integration of selective recording by conditions
• Recording rotation and access rights setup
• Testing with real calls
• Documentation and employee training

Estimated timelines

Pricing is individual, depending on PBX complexity and scope of modifications. We'll estimate your project in 1 day — just contact us.

What professional setup delivers

Properly configured recording guarantees data integrity, saves time on conflict resolution, and enables manager training on real conversations. Companies with certified specialists and over 5 years of Bitrix24 experience (our team is exactly that case) ensure flawless operation even under high load.

Order call recording setup — get a consultation and preliminary cost estimate. Result: recording works, data is not lost, employees are satisfied. Don't postpone setup — write to us, and we'll make recording work in 1-5 days.

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.