Integrating Bitrix24 with Beeline Business Telephony

Integrating Bitrix24 with Beeline Business Telephony

We constantly see companies losing call data because the integration is not set up. Beeline Business corporate telephony operates either through a virtual PBX (Virtual Office) or through plain SIM cards. Both options can be connected to Bitrix24, but the approaches are fundamentally different. With over 50 completed integrations, we have accumulated ready-made solutions for each scenario. This article explains how to configure the integration properly so that no call is lost and you get full analytics.

How to Integrate Beeline Virtual Office with Bitrix24?

The Virtual Office (cloud PBX) provides an API and webhooks for call events. Setup starts by requesting access from Beeline support or through a partner program. In the PBX control panel under Settings → Integrations → API, specify your handler URL and a secret for signing. Beeline sends events in JSON format with HMAC-SHA256 in the X-Beeline-Signature header. The handler must register calls in Bitrix24 via the REST method telephony.externalCall.register (see Bitrix24 helpdesk).

Table of supported events:

After registration, call telephony.externalCall.attachRecord to attach the audio. The recording retention period in the Beeline cloud ranges from 7 days to a year, depending on the tariff.

How to Set Up the Event Handler?

1. Create a PHP script that accepts POST requests from Beeline.
2. Verify the HMAC signature in the X-Beeline-Signature header.
3. Parse the JSON and register the call via telephony.externalCall.register.
4. On the call.record_ready event, download the recording and attach it via telephony.externalCall.attachRecord.
5. Configure error logging and monitoring.

What to Do If Corporate SIMs Without PBX Are Used?

Without a virtual PBX, call events are not directly available. Three solutions exist:

1. Switch to Virtual Office — mobile numbers become internal, integration via API.
2. GSM gateway — a hardware converter from SIM to SIP, connects to any PBX, including Bitrix24 directly.
3. Cloud SIM connectors — services (e.g., SimCom) virtualize SIMs and provide a SIP interface.

The second option often costs less than a full migration but requires hardware maintenance.

Configuration via the Official Beeline App in Bitrix24

Beeline and Bitrix24 are partners. In the Bitrix24 "Telephony" section, select "Connect Telephony" → the "Beeline Business" app. Authorize with your corporate account and map internal numbers to users. This method is suitable for companies already using Virtual Office. It takes about 1 day to set up.

Comparison of API Integration vs. App

We recommend API integration if you need complex routing or analytics on the Bitrix24 side.

Typical Integration Errors

• Incorrect HMAC signature: double-check the secret and algorithm (SHA256).
• Beeline IP address range: add them to your server whitelist.
• Timeouts: the handler must respond within 5 seconds, otherwise Beeline retries.
• Event loss: set up a queue on Redis or RabbitMQ.

What’s Included in the Work

In the integration, we perform a full cycle: from auditing the current scheme to handover. Specifically:

• Documentation of the call flow and number allocation.
• Setting up the event handler on your server (PHP, based on our module).
• Mapping numbers to Bitrix24 users.
• Testing all scenarios: inbound, outbound, transfer, recording.
• Training administrators and answering questions during the first week after handover.
• Post-release support and adjustments based on feedback.

Upon completion, you receive a maintenance guide and an error-handling diagram.

From Our Practice: A Trading Holding Across 6 Cities

A federal trading network had offices in 6 cities, each with its own Beeline Virtual Office account. Each office handled over 200 calls per day. They needed to see all calls in a single Bitrix24, but managers in each city should only see their own. We built the architecture: six webhooks on one server, the handler identifies the city by URL and sets the correct LINE_NUMBER. Access rights were configured via CRM. A non-standard requirement: when a call is transferred from Moscow to St. Petersburg, it had to reach the St. Petersburg manager. We solved it via the PBX transfer event — the handler created a new call with the correct office. Results: missed calls decreased by 30%, and inbound call processing costs were reduced by up to 40% per month. The project took 8 business days, including coordination with Beeline for each account.

Contact us for a free assessment of your scenario. Get a consultation from an integration engineer. Typical integration cost for a single office starts at $500.

Timeline and How to Order

The integration of a single office takes 3 to 7 days. For complex setups (like the case above) — up to 10 business days. We evaluate your scenario for free. We work officially with a guarantee. Get an accurate timeline estimate for your scenario. With 50+ implementations, we have certified approaches.