Video Calls in Bitrix24: Zoom & Jitsi Integration

Our company is engaged in the development, support and maintenance of Bitrix and Bitrix24 solutions of any complexity. From simple one-page sites to complex online stores, CRM systems with 1C and telephony integration. The experience of developers is confirmed by certificates from the vendor.
Showing 1 of 1All 1626 services
Video Calls in Bitrix24: Zoom & Jitsi Integration
Simple
~1 day
Frequently Asked Questions

Our competencies:

Development stages

Latest works

  • image_website-b2b-advance_0.webp
    B2B ADVANCE company website development
    1356
  • image_bitrix-bitrix-24-1c_fixper_448_0.webp
    Website development for FIXPER company
    943
  • image_bitrix-bitrix-24-1c_development_of_an_online_appointment_booking_widget_for_a_medical_center_594_0.webp
    Development based on Bitrix, Bitrix24, 1C for the company Development of an Online Appointment Booking Widget for a Medical Center
    693
  • image_bitrix-bitrix-24-1c_mirsanbel_458_0.webp
    Development based on 1C Enterprise for MIRSANBEL
    828
  • image_crm_dolbimby_434_0.webp
    Website development on CRM Bitrix24 for DOLBIMBY
    731
  • image_crm_technotorgcomplex_453_0.webp
    Development based on Bitrix24 for the company TECHNOTORGKOMPLEKS
    1073

Situation: you've set up Bitrix24, but video calls aren't being recorded, links aren't reaching clients, and Zoom integration is missing. Built-in tools are limited — no branding, no automatic logging to deals. Standard configuration doesn't solve these tasks. As a result, managers waste time manually creating rooms, and clients forget about meetings. We've seen projects where sales departments lost up to 30% of leads due to missing timely call links. Manager time savings reach up to 40% with automatic link sending, significantly cutting operational costs for a 5-person team. For example, a typical Zoom integration setup can save a team of 10 managers up to $1,200 per month in manual meeting creation time — that's $14,400 annually.

Imagine: a manager creates a meeting in CRM, and the client receives a link via WhatsApp with details. The recording is automatically saved in the deal card. This is achievable with proper integration. We've configured such scenarios for dozens of organizations — from small sales teams to large dealer networks with hundreds of participants. We are certified 1C-Bitrix specialists with over 12 years of experience and have completed more than 200 projects. Request an audit of your current settings — we'll prepare a detailed plan in 1 day.

Problems We Solve

  • Manually created rooms — wasted time, no single entry point. We automate room generation when an activity is created.
  • Recordings inaccessible — Bitrix24 cloud storage doesn't allow MP4 download. We configure external storage (S3) or local recording.
  • No automatic link sending — client doesn't receive an invitation. We connect email/WhatsApp sending on call creation.
  • No integration with external services — Zoom, Jitsi. We implement seamless linkage via REST API.

According to our analysis, automating meeting links increased customer engagement by 25%.

Common Causes of Video Call Failures After Update

Typical reason: a changed version of the Videoconference component or blocked webhook notifications. Solution: update REST route settings, check access rights to crm.activity.update. We guarantee stable operation after every update.

Automated Link Sending to Clients

Use the REST API messageservice.message.add with a letter template or via messenger integration. Scenario: create meeting → generate link → send to client via email/WhatsApp. We implement this in 1–2 days. For example, one client saved $500/month in manual labor costs — that's $6,000 per year.

How to Set Up Automatic Video Calls: Step-by-Step Guide

  1. Enable video calls in portal settings: Settings → Telephony → Video Calls.
  2. Configure REST API access rights: ensure the app has rights to crm.activity.update and messageservice.message.add.
  3. Create an event handler for onCrmActivityAdd that will trigger creation of a meeting in Zoom or Jitsi.
  4. In the handler, call the external service's API to create a room and get the link.
  5. Save the link in a custom field of the deal (e.g., UF_CRM_ZOOM_JOIN_URL).
  6. Send the link to the client via email or WhatsApp using messageservice.message.add.
Example Handler in PHP
class ZoomBitrix24Integration
{
    private ZoomApiClient $zoom;
    private BitrixRestClient $b24;

    public function onActivityCreate(array $activity): void
    {
        if ($activity['TYPE_ID'] != 1) return;
        if (empty($activity['END_TIME'])) return;

        $startTime = new DateTime($activity['START_TIME']);
        $endTime = new DateTime($activity['END_TIME']);
        $duration = ($endTime->getTimestamp() - $startTime->getTimestamp()) / 60;

        $meeting = $this->zoom->createMeeting([
            'topic' => $activity['SUBJECT'],
            'type' => 2,
            'start_time' => $startTime->format('Y-m-d\TH:i:s'),
            'duration' => (int)$duration,
            'timezone' => 'Europe/Moscow',
            'settings' => [
                'auto_recording' => 'cloud',
                'waiting_room' => true,
                'mute_upon_entry' => true,
            ],
        ]);

        $this->b24->call('crm.activity.update', [
            'ID' => $activity['ID'],
            'FIELDS' => [
                'DESCRIPTION' => "Zoom link: {$meeting['join_url']}\n\n" . $activity['DESCRIPTION'],
                'UF_CRM_ZOOM_MEETING_ID' => $meeting['id'],
                'UF_CRM_ZOOM_JOIN_URL' => $meeting['join_url'],
                'UF_CRM_ZOOM_HOST_URL' => $meeting['start_url'],
            ],
        ]);

        $this->sendMeetingLinkToClient($activity, $meeting['join_url']);
    }
}

Video Call Solutions Comparison

Feature Built-in B24 Calls Zoom Integration Jitsi on Your Server
Branding No Partial Full
Recording B24 Cloud Cloud Recording MP4 on Server
Confidentiality Medium Medium High
Participants Up to 24 Up to 300 Up to 100+
CRM Automation Partial Full Full
Setup Time 1 day 3–5 days 2–3 weeks
Cost Included in plan $15/month (basic) Server + setup ~$2000

Jitsi on your server supports 3 times more participants than built-in calls, with full data control. Zoom integration reduces manual entry by 80% compared to manual meeting creation. If you work with confidential data (finance, healthcare), Jitsi is the only option meeting security requirements. Moreover, Jitsi is 3x cheaper than Zoom over a year for 50 users — saving up to $6,000 annually. Built-in calls are simpler but less flexible than Jitsi for large meetings. For a typical Zoom integration project, the one-time cost is $1,500-$3,000, while annual savings on manual labor exceed $12,000.

Typical Setup Errors and Solutions

Error Cause Solution
Link not sent Connector for sending not configured Check email/WhatsApp settings
Webhook not received Incorrect URL or disabled Check webhook list in settings
Recording not saved Insufficient cloud space Configure external storage

Setting Up Built-in Bitrix24 Video Calls

Built-in tool: Calls → Video Call or button in chat. Technically works via WebRTC SDK BX24. To activate:

Portal settings → Telephony → Video Calls → Enable

By default, it supports up to 12–24 participants (depends on plan), cloud recording on paid plans.

Limitations of built-in solution: no room interface customization, no built-in 'create room from deal' integration, recording stored only in B24 cloud.

Zoom Integration via REST API

For companies that use Zoom as their main video conferencing tool — automatic creation of a Zoom meeting when a 'Meeting' activity is created in Bitrix24. Integration code uses REST API and Zoom Meeting SDK (example above).

Automatic Sending of Link to Client

After meeting creation — the meeting URL is automatically sent to the client. Via email (letter template with Zoom link) or via messenger (WhatsApp, Telegram — if integration is configured):

$this->b24->call('messageservice.message.add', [
    'FROM_CONNECTOR' => 'WHATSAPP',
    'FROM_LINE' => $lineId,
    'TO' => $clientPhone,
    'MESSAGE' => "Hello! Link to our meeting:\n{$meetingUrl}\n"
              . "Time: {$startTime->format('d.m.Y H:i')}",
]);

Call Recording and Storage

When using built-in Bitrix24 Videoconference — recordings are available in chat history. For integration with external storage:

  1. Zoom Cloud Recording — webhook from Zoom when recording is ready (recording.completed) → upload to S3-compatible storage → link in deal card.
  2. Local recording on server — if you have your own WebRTC server (Jitsi Meet, BigBlueButton) with configured MP4 recording.

Jitsi Meet as an Alternative

For companies that require full confidentiality (data doesn't leave your own infrastructure) — Jitsi Meet on your own server. Integration with Bitrix24: when a meeting is created, a unique room is generated on your Jitsi server:

$roomName = 'deal-' . $dealId . '-' . uniqid();
$jitsiUrl = JITSI_SERVER_URL . '/' . $roomName;
$tokenJwt = $this->generateJitsiJwt($roomName, $moderatorName);

$hostUrl = $jitsiUrl . '?jwt=' . $tokenJwt;
$clientUrl = $jitsiUrl;

Replace JITSI_SERVER_URL with the actual URL of your Jitsi server.

Process and Timeline

What's Included

  • Audit of current portal and communication channel configuration
  • Setting up built-in B24 video calls (plan, settings)
  • Zoom API integration: creating meetings from CRM activities
  • Zoom webhook: saving recordings in deal card
  • Auto-sending link to client (email/messenger)
  • Alternatively: deploying Jitsi Meet on your server + JWT authorization
  • Staff training and technical documentation

Approximate Timeframes

  • Built-in B24 video calls setup: 1 day
  • Zoom API integration (meetings + recordings): 3–5 days
  • Jitsi Meet deployment with JWT and CRM integration: 2–3 weeks

We'll evaluate your project in 1 day. Contact us for a consultation and individual cost estimate. We guarantee stable integration even under high loads. Our Bitrix24 video calls setup includes Zoom Bitrix24 integration and Jitsi Meet configuration for CRM video conferencing — all three key services combined for seamless meeting automation.

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.

Provider Real Benefit Pitfalls
Bitrix24.Telephony Built-in, setup via portal UI Tied to B24 tariff, more expensive at scale
Sipuni Native module for B24, quick integration Limited number geography
Mango Office Powerful analytics, speech analytics included Above-market price
UIS (CoMagic) Call tracking + PBX all-in-one Complex admin panel
Zadarma 70+ countries, budget-friendly API sometimes slow, support slow
MegaFon PBX FMC — mobile as office SIP setup via support, not UI
MTT Flexible tariffs, good API No native module for B24
Rostelecom Stability, government sector Slow setup, bureaucracy

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.

Which codecs to choose for stable operation? G.711 (A-law/µ-law) — standard codec, bandwidth 87 kbit/s per line. G.729 — compressed codec, 31 kbit/s. If bandwidth is limited, G.729 is preferred, but not all providers support it. Also possible G.722 (HD voice) — requires 64 kbit/s and PBX support.

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

Task Timeframe
Cloud PBX + basic routing 1–2 days
SIP trunk (if provider releases data quickly) 1–3 days
Routing + IVR 2–5 days
CRM integration: robots, triggers, cards 3–5 days
Callback widget 1 day
Comprehensive setup with audit 2–3 weeks

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.