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:
| Event |
Trigger |
call.start |
Incoming call registered |
call.answer |
Employee answered |
call.end |
Conversation ended |
call.record_ready |
Recording ready for download |
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?
- Create a PHP script that accepts POST requests from Beeline.
- Verify the HMAC signature in the
X-Beeline-Signature header.
- Parse the JSON and register the call via
telephony.externalCall.register.
- On the
call.record_ready event, download the recording and attach it via telephony.externalCall.attachRecord.
- 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:
-
Switch to Virtual Office — mobile numbers become internal, integration via API.
-
GSM gateway — a hardware converter from SIM to SIP, connects to any PBX, including Bitrix24 directly.
-
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
| Parameter |
API via webhooks |
Beeline App |
| Flexibility |
Full control over handler |
Limited to app settings |
| Implementation speed |
2–5 days development |
1 day |
| Support for non-standard scenarios |
Yes |
No |
| Dependence on partner access |
Yes |
No |
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.
How Choosing the Wrong 1C-Bitrix Edition Breaks Your Project
You bought Small Business, launched a store, traffic grew to 5,000 unique visitors per day — and the site crashed. Composite cache is only available in Business, web cluster too. An upgrade costs the difference in license price plus work to configure new modules. Choosing and configuring the right 1C-Bitrix edition upfront saves up to 40% on licensing. It also avoids unplanned upgrade costs — saving on average 15,000–30,000 RUB when upgrading from Small Business to Business in advance instead of urgently. Over 8 years of working with Bitrix, we have performed over 200 upgrades and seen all typical mistakes: from buying Start for a 50,000-product catalog to using Business for a landing page with 100 visits per day. Our principle is to select the edition that matches your real needs and configure it so you do not overpay for unnecessary modules — and also do not hit a ceiling at the first traffic spike.
1C-Bitrix Editions: Site Management
Four editions, and the difference lies not in the number of features but in the available core modules. The official 1C-Bitrix documentation states that composite cache is only available in Business and above.
| Module / Feature |
Start |
Standard |
Small Business |
Business |
| Information blocks |
+ |
+ |
+ |
+ |
| Web forms |
+ |
+ |
+ |
+ |
| Basic SEO |
+ |
+ |
+ |
+ |
| Blog, forum, social network |
– |
+ |
+ |
+ |
sale (e-store) module |
– |
– |
+ |
+ |
1C exchange (catalog) |
– |
– |
+ |
+ |
Composite cache (main.composite) |
– |
– |
– |
+ |
Web cluster (cluster) |
– |
– |
– |
+ |
| Multisite |
– |
– |
– |
+ |
| REST API |
– |
– |
– |
+ |
Start is minimal, only content modules: iblock, form, basic SEO. For business card sites and landing pages. No sale module — cannot build a store.
Standard adds communication: blog, social network, forum, extended tech support. For corporate sites and portals with user-generated content.
Small Business is the first edition with e-commerce: the sale module appears. Comfortable ceiling is up to about 10,000 products without serious optimization. For small stores and catalogs with ordering.
Business is the full set: composite cache (TTFB drops from 800 ms to 50–80 ms — 10–15 times faster), web cluster, multisite, multi-warehouse, REST API. For large stores, marketplaces, projects with 10,000+ visitors per day.
How Does Composite Cache Reduce Server Load?
Composite cache (main.composite) speeds up page loading 10–15 times compared to dynamic generation. For a store with 3,000+ visitors per day, without composite the server starts struggling: average response time increases, database overload, checkout pages time out. Composite solves this radically — HTML is served by nginx without running PHP. It is important to correctly configure exclude masks for cart, personal account, and pages requiring real-time data. We configure this on every upgrade to Business.
1C-Bitrix official documentation: "Composite cache is available only in Business edition and higher."
Avoiding Common Mistakes in Edition Selection
Typical Mistakes
- Buying Start for an online store — no
sale module, you either need to upgrade immediately or hack a custom ordering system.
- Choosing Small Business for a project that will grow to 10,000 products in six months — composite cache cannot be enabled, upgrading to Business costs the license difference plus configuration work.
- Using Business for a landing page — overpaying for features that will never be used.
Choosing an Edition for an Online Store
| Store Type |
Recommended Edition |
Key Limitation |
| Up to 1,000 products, traffic up to 500 unique visitors/day |
Small Business |
No composite cache (TTFB > 500 ms at peaks) |
| 1,000–10,000 products, 500–5,000 unique visitors/day |
Small Business with tuning or Business (immediately) |
Load hits PHP-FPM limit |
| 10,000+ products, 5,000+ unique visitors/day |
Business |
Need composite + cluster |
| Marketplace, 100,000+ products |
Business + web cluster |
Horizontal scaling mandatory |
Hard Criteria for Edition Selection
By modules:
- 1C exchange (
catalog) → at least Small Business
- Composite cache (
main.composite) → only Business
- Web cluster (
cluster) → only Business
- Multisite → only Business
- REST API → only Business
By load:
- Up to 1,000 unique visitors/day — any edition can handle
- 1,000–10,000 unique visitors/day — Small Business with nginx/php-fpm tuning hits a ceiling. Business with composite cache is the right choice
- 10,000+ unique visitors/day — only Business with composite and cluster
By budget:
- The price difference between editions is 2-5x
- Upgrade at any time — pay the difference in license cost
- Our principle: take the minimum sufficient. But if you know you will need composite in six months, get Business immediately, because an upgrade also involves configuration work. The total upgrade cost (license difference + setup) typically ranges from 10,000 to 50,000 RUB.
What Happens If You Ignore License Renewal?
An active license provides updates — new versions, security patches, bug fixes, marketplace access, and vendor tech support. When it expires, the site continues to work but remains without updates. For stores this is dangerous — security patches fix vulnerabilities in sale, catalog, main modules. Data leaks from b_sale_order or b_user are just a matter of time. Renewal costs a fraction of buying a new license — typically 20–30% of the full price. Regular renewal is insurance against unpatched CVEs.
Cost Benefits of Planned Edition Upgrades
1C-Bitrix allows upgrading without reinstallation — data is preserved. Process:
- Pay the difference in license cost
- Activate new key: Settings → Updates → Registration
- Install newly available modules via admin panel
- Configure new functionality
- Test compatibility
What we do during an upgrade:
- Check custom code for conflicts with new modules — especially custom event handlers like
OnBeforeOrderAdd, OnSaleBasketSaved
- Enable and configure composite cache — correct exclude masks for dynamic pages (cart, checkout, personal account)
- Configure multi-warehouse if needed —
b_catalog_store, warehouse selection rules
- Run full functional testing on staging
- Document changes
As a result, you get:
- A working site on the new edition with no data loss
- Configured composite cache (if upgraded to Business)
- Testing report and recommendations for further optimization
- Access to staging and documentation of changes
Integrating Site Management with Bitrix24
A common scenario: site on 1C-Bitrix + CRM in Bitrix24. Orders from b_sale_order automatically become leads or deals, unified authorization, client base synchronization. Site forms (form or custom) feed into the CRM funnel. These are two separate licenses and two separate products — integration between them is standard and stable.
Practical Recommendations
- Do not skimp on the edition if you know the functionality will be needed in six months. Upgrading costs the same difference plus configuration and testing.
- Business for projects with growth ambitions — composite cache pays for the price difference at the first traffic spike. Without composite, 3,000+ unique visitors/day will strain the server.
- Bitrix24 and Site Management are different products with different licenses. Confusion here costs money.
- Renew your license annually — renewal is much cheaper than buying a new one, and without updates you risk unpatched CVEs.
What We Offer: Turnkey Selection and Configuration
We do not just consult — we handle the full cycle: analyze your current project, select the edition, purchase the license (if needed), migrate, configure all modules, and train your team. As part of the service, you get:
- An edition selection report with justification
- Migration plan (if upgrading)
- Fully set up staging with the new edition
- Composite cache and cluster configuration (if necessary)
- Documentation of the new configuration
- Guarantee of site functionality after the transition
Contact us today — we can assess your project within one business day and propose the optimal configuration. Receive a personalized cost estimate for selecting and configuring your 1C-Bitrix edition right now.