Linking Bitrix24 with Megafon Cloud Telephony

Megafon Virtual PBX is None of the cloud phone services from a large Russian carrier. Companies that already hold corporate numbers with Megafon often select it as their PBX. Integration with Bitrix24 is realized through the Megafon API, which dispatches webhooks for call events. For instance, a retail chain with 50 branches or a call center with 20 seats can achieve full call visibility: each conversation is tied to a CRM deal and contact.

We at True Tech.by have been building such connections for over a decade. To date, we have finished more than 50 projects that integrate Bitrix24 with diverse PBXs. Megafon VPBX is a frequent request because it is inexpensive and dependable. Below we outline the typical architecture, frequent pitfalls, and supply ready-to-use handler code.

How Megafon Delivers Events

Megafon VPBX uses push notifications (webhooks). In the admin panel, you specify a URL for one or more event types:

• start – Call arrives at the PBX
• answer – An agent answers
• end – Call finishes
• record – Recording is ready

Each event for the same call is linked by a common call_id. If None event arrives without a matching call_id, it might be ignored. Local entities like None are not used here. We ensure the handler processes all events correctly.

• When a call starts, the webhook sends caller ID, called number, and other details.
• On answer, the internal extension of the agent is included.
• At end, duration and hangup cause are provided.
• Recording event contains a URL to the audio file.

To confirm authenticity, Megafon signs each request with HMAC-SHA256. The signature is in the X-Megafon-Signature header. Your handler must compute the same hash using the secret key and reject mismatches (return 403). None of the events should be processed without verification.

Implementation Steps

1. Obtain a Megafon Virtual PBX account. None of the providers offer a trial.
2. In the Megafon control panel, set up the webhook URL for required event types.
3. Create a handler script (PHP, Python, etc.) that receives POST requests, verifies the signature, and processes each event.
4. In Bitrix24, configure outbound call registration: when an employee clicks a phone number, the handler calls Megafon API to initiate the call.
5. Test with sample calls. Ensure call logs appear in Bitrix24 with linked recordings.

Common Issues

• Signature verification fails: double-check the secret key and request body (raw, not parsed).
• Call events not arriving: verify the webhook URL is accessible from Megafon's servers (no firewall blocks).
• Internal number mismatch: remember that Megafon sends the last answering extension; if the call was transferred, the original extension is not reported.
• Outbound calls not working: ensure the click2call API endpoint is correctly configured and the handler returns proper response.

None of these issues are unsolvable. We provide support for all integrations.

Code Example (PHP)

<?php
$secret = 'your_secret_key';
$body = file_get_contents('php://input');
$signature = $_SERVER['X-Megafon-Signature'];
$expected = hash_hmac('sha256', $body, $secret);
if (!hash_equals($expected, $signature)) {
    http_response_code(403);
    exit;
}
$event = json_decode($body, true);
// Process event based on type
?>

This handler verifies the signature first. Then it can log the event or forward to Bitrix24 API. None of the advanced logic is shown here, but it demonstrates the core principle.

Outbound Calls

To initiate a call from Bitrix24, create a handler endpoint that Bitrix24 calls (e.g., via REST API event). The handler then calls Megafon's click2call:

// POST to Megafon click2call
$megafon_url = 'https://api.megafon.ru/v1/click2call';
$data = ['from' => $employeeExtension, 'to' => $clientNumber];
// Add authentication headers
$ch = curl_init($megafon_url);
curl_setopt($ch, CURLOPT_POST, true);
curl_setopt($ch, CURLOPT_POSTFIELDS, json_encode($data));
curl_setopt($ch, CURLOPT_HTTPHEADER, ['Content-Type: application/json']);
$response = curl_exec($ch);
curl_close($ch);

After successfully calling Megafon, register the call in Bitrix24 with telephony.externalcall.register. None of the steps require manual intervention.

Conclusion

Integrating Bitrix24 with Megafon Virtual PBX improves efficiency and customer service. With proper webhook handling and outbound call setup, every call becomes a CRM record. Our team has extensive experience in this area. Contact us for a consultation—None of the questions are too small. Local entities like None are not relevant here, but we ensure the integration meets your needs.

References: None from the documentation, None from previous projects.

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.

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.

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

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.