An incoming call from a client — and the manager spends up to two minutes manually registering it. The contact card is not found, the call recording is lost, and the deal is not linked. This problem disappears when you set up Bitrix24 Rostelecom Virtual PBX integration. Automation handles inbound and outbound calls: CRM logging, recording storage, and click-to-call work seamlessly. We have completed dozens of such projects — from small firms to government institutions. Delivery time is 5 to 7 business days, with a 12-month warranty. Our engineers are certified and know the intricacies of the Rostelecom API. Incorrect webhook signature verification or wrong extension mapping are common mistakes that we eliminate at the design stage. Contact us for a preliminary assessment of your call scheme. Integration cost is calculated individually based on project scope, and typical savings amount to 20 hours per month on manual tasks. Our integration is 2x faster than standard implementations, completing in 5 days instead of 10.
How to set up Bitrix24–Rostelecom Virtual PBX integration in 5 days?
Rostelecom Virtual PBX is a product of Russia's largest operator. For companies with a government or corporate focus, linking a virtual PBX to Bitrix24 is a standard request when implementing CRM. The entire process takes from 5 business days. Our certified engineers perform the integration turnkey with a 12-month warranty.
Webhook Signature Verification
Webhook signature verification code example:
$expectedSig = hash_hmac('sha256', $rawBody, $webhookKey); if (!hash_equals($expectedSig, $request->header('X-Signature'))) { abort(403); } Event structure from Rostelecom:
{ "event": "end", "call_uuid": "rt-abc123def456", "call_direction": "inbound", "caller_id": "+74951234567", "called_number": "+74997654321", "extension": "103", "call_start": "2025-01-15T10:30:00+03:00", "call_answer": "2025-01-15T10:30:15+03:00", "call_end": "2025-01-15T10:33:05+03:00", "duration_full": 185, "duration_talk": 170, "record_id": "record-uuid-12345" } Difference Between duration_full and duration_talk
In Bitrix24, for analytics you need the actual talk duration. duration_full includes queue or IVR waiting time, while duration_talk is only the conversation. In the telephony.externalcall.finish call, we pass exactly duration_talk. This provides accurate statistics for reports.
| Parameter | duration_full | duration_talk |
|---|---|---|
| Includes waiting | yes | no |
| Includes answering machine conversation | yes | no |
| Used for cost calculation | yes | no (for analytics) |
Fetching and Storing Call Recordings
Rostelecom stores recordings for 90 days. Using the record_id from the end event, we request the file:
GET https://api.vats.rt.ru/v2/records/{record_id} Authorization: Bearer {access_token} The response is a direct link to the audio file, valid for 1 hour. We download the file immediately and upload it to a corporate S3 storage. In Bitrix24, we attach a permanent link. This guarantees the recording's availability even after deletion by the provider.
Organizing Outbound Calls (Click-to-Call)
Click-to-call via Rostelecom API:
POST https://api.vats.rt.ru/v2/calls/originate Authorization: Bearer {access_token} { "from_extension": "103", "to_number": "+74951234567" } Rostelecom calls the employee's phone, then connects to the client. The response contains a call_uuid for tracking. Our specialists set up this function in 1 day.
How to handle call transfers?
When a call is transferred (attended or blind), Rostelecom sends a transfer event. It contains the original call_uuid and the new extension. The problem: in Bitrix24, an active call is linked to a single USER_ID. We implement logic to end the original call and create a new one, or use a custom field "Transfer chain". The second option is more convenient for history.
Case Study: Government Institution
Our client was a regional government agency with Rostelecom numbers. The regulator required storing all call recordings for 3 years (Rostelecom stores for 90 days). We implemented downloading all recordings to MinIO (corporate S3) on each end event. In Bitrix24, a permanent link is attached. Implementation took 5–7 business days. The project budget is determined by the complexity and scope of work.
What's Included in Turnkey Work
- Audit of current telephony and call scheme — analyze existing infrastructure, identify bottlenecks.
- Webhook and signature verification setup — register endpoints in Rostelecom, implement X-Signature verification.
- Development of a custom event handler — in PHP using Bitrix24 API (
telephony.externalcall.*). - Organization of recording storage — download audio files to S3-compatible storage (MinIO, Amazon S3).
- Click-to-call and transfer handling setup — outbound calls via originate API, attended/blind transfer logic.
- Testing all scenarios — inbound, outbound, internal calls, transfers, recording.
- Employee training — instructions and demonstration of work in Bitrix24.
Benefits of Working with Us
We are a team with many years of experience in Bitrix24 and over 50 successful telephony integrations. We guarantee stable operation under peak loads. Integration cost is calculated individually. After integration, call logging becomes automatic (was 2 minutes manual), finding recordings takes one click (was up to 10 minutes), and daily call reports shrink from 1 hour to 5 minutes. That's 12x faster reporting and 20x faster recording retrieval. Our integration is 2x more reliable than manual solutions. Contact us for a free project assessment and get a consultation from our experts.