Setting Up Flash Call Verification in 1C-Bitrix

We often encounter situations where SMS verification fails: the carrier blocks the mailing, the phone is roaming, or the balance is zero. In such cases, a missed call (Flash Call) comes to the rescue. The user enters their number, the system calls and hangs up — the last 4 digits of the incoming number become the confirmation code. This is 5-10 times cheaper than SMS, and reliability is higher. Our team configures this mechanism turnkey: from selecting a provider to integrating with your Bitrix. We'll assess the project within 1 day — contact us for a preliminary estimate.

How Does a Missed Call Work?

Technically, the scheme is as follows: your server instructs the telephone platform to make a call from one of the numbers in the pool. The user sees an incoming call, remembers (or copies) the last 4 digits, and enters them into the form. There's no need to answer the call.

The key requirement: the provider must offer a pool of numbers with different last 4 digits and the ability to select a specific number for outgoing calls.

Why Is a Missed Call Cheaper Than SMS?

Flash Call is cheaper: the average cost of one verification via missed call is 5-10 times lower than SMS. This is especially noticeable at volumes of 1,000+ verifications per day. Additionally, the call is guaranteed to be delivered even in roaming, where SMS may be blocked. The freed-up budget can be allocated to marketing or improving the customer experience.

Which Providers Support Flash Call?

We'll select the optimal provider for your traffic and budget.

Implementation in Bitrix

The architecture is similar to SMS verification, but instead of a text code, the system generates a 4-digit suffix and selects a phone number from the pool with that suffix.

Table for storing verification sessions:

CREATE TABLE custom_flashcall_verification (
    id INT AUTO_INCREMENT PRIMARY KEY,
    phone VARCHAR(20) NOT NULL,
    caller_number VARCHAR(20) NOT NULL,
    code VARCHAR(4) NOT NULL,
    created_at DATETIME NOT NULL,
    attempts INT DEFAULT 0,
    verified TINYINT DEFAULT 0
);

Generation logic:

function initiateFlashCall(string $targetPhone): array {
    // Generate a 4-digit code (0001–9999)
    $code = str_pad(random_int(1, 9999), 4, '0', STR_PAD_LEFT);

    // Select a number from the pool ending with this code
    $callerNumber = FlashCallPool::getNumberByCode($code);

    if (!$callerNumber) {
        throw new \Exception('No available number for code: ' . $code);
    }

    // Initiate a call via the provider's API
    $provider = new ExolveFlashCallProvider();
    $provider->call($callerNumber, $targetPhone);

    // Save to database
    FlashCallVerificationTable::add([
        'PHONE' => $targetPhone,
        'CALLER_NUMBER' => $callerNumber,
        'CODE' => $code,
        'CREATED_AT' => new \Bitrix\Main\Type\DateTime(),
    ]);

    return ['success' => true, 'hint' => 'Expect an incoming call'];
}

Managing the Number Pool

The number pool is a critical part of the system. For codes 0000–9999, a minimum pool of several hundred numbers is needed; otherwise collisions are inevitable under high load.

Pool table:

CREATE TABLE custom_flashcall_pool (
    id INT AUTO_INCREMENT PRIMARY KEY,
    phone_number VARCHAR(20) NOT NULL,
    code_suffix VARCHAR(4) NOT NULL,
    in_use TINYINT DEFAULT 0,
    last_used DATETIME,
    INDEX idx_code (code_suffix),
    INDEX idx_available (in_use, last_used)
);

When selecting a number from the pool, the first available with the required suffix that hasn't been used in the last 30 seconds is taken. After verification completes, the number is returned to the pool.

User Interface

The verification form via missed call differs from SMS:

1. User enters their phone number
2. A message appears: "You will now receive a call from a number. Remember its last 4 digits."
3. Input field with mask _ _ _ _
4. Countdown timer (usually 30–60 seconds)
5. "Call again" button after the timer expires

It's important to inform the user that they don't need to answer the call — this is non-standard and can cause confusion without an explanation.

Integration with Bitrix

Verification is embedded via an AJAX controller (\Bitrix\Main\Engine\Controller) and connected to the registration or checkout form via JavaScript. In the bitrix:sale.order.ajax component, a verification step is added between entering contact details and confirming the order. Full documentation for Bitrix REST API can be found in the official guide.

Fallback option: if the call doesn't arrive within 90 seconds, the user is offered to switch to SMS verification.

What's Included in Turnkey Setup

• Selection and connection of a Flash Call provider
• Development of the number pool and collision management
• Implementation of the verification form with timer and fallback
• Integration with your Bitrix (component, controller, database)
• Load testing and documentation
• Admin training and launch support

Over 5 years of experience with Bitrix and 30+ successful integration projects guarantee quality results.

Typical Errors and How to Avoid Them

Timelines

For high-load stores with 1,000+ verifications per day, it's worth designing pool redundancy and monitoring provider availability.

Get a specialist consultation — contact us to estimate timelines and cost for your project.

What Professional 1C-Bitrix Installation Includes

We start by checking innodb_buffer_pool_size. The default MySQL value (128 MB) is a death sentence for an online store with a catalog of 10,000+ items. We set 70–80% of available RAM on a dedicated server, 50% on VPS. This single setting speeds up the site by 2–3 times compared to the default. We'll assess your project in one day — get a consultation. Contact us to order turnkey installation with performance guarantee.

How to Choose Hosting and Edition for 1C-Bitrix Installation?

BitrixVM is a virtual machine with a pre-installed stack: nginx + Apache, PHP-FPM, MySQL/MariaDB, Sphinx, Push server. For VPS — the best start. Everything is already configured for Bitrix, including OPcache, log rotation, and firewall. Management via web panel on port 8890. Bitrix documentation recommends starting with BitrixVM for predictable performance.

VPS/VDS is the sweet spot. Minimum configuration for a medium online store: 2 vCPU, 4 GB RAM, SSD. Optimal: 4 vCPU, 8 GB RAM. OS: Ubuntu 22.04 or Debian 12. If not BitrixVM, we configure the stack manually for the task. Virtual hosting — only for business cards and landing pages. Requirements: PHP 8.0+, MySQL 5.7+ / MariaDB 10.0+, 512 MB RAM, .htaccess. 1C-Bitrix hosting partners guarantee compatibility. Dedicated server — for highload. Typical architecture: web server separate, database separate, Redis/Memcached separate. For Enterprise edition — web cluster with load balancer. Cloud (Yandex Cloud, VK Cloud, Selectel) — when load spikes: sales, seasonal peaks. Autoscaling via Managed Kubernetes or simple VM vertical scaling.

Choosing the edition is equally important. A common mistake: choosing "Small Business" for a store that grows to B2B with wholesale prices and three warehouses in six months. Upgrading to "Business" — pay the difference, data is not lost, but it's better to plan ahead. Our specialists select the edition for current tasks and with room for growth. For example, the "Business" license (about 35,000 RUB) pays off through multi-warehouse and 1C exchange, while the wrong choice can lead to a loss of up to 30,000 RUB monthly on excess resources.

What Server Settings Are Critical for 1C-Bitrix?

Web Server and PHP

nginx as reverse proxy + Apache (mod_php) or nginx + PHP-FPM directly. The second option saves memory — Apache is not needed. But some Bitrix modules use .htaccess, so for compatibility we sometimes keep Apache. nginx configuration: fastcgi_read_timeout 300 — for long operations (1C import), client_max_body_size 1024m — large file uploads. Block access to .settings.php, .settings_extra.php, bitrix/.settings.php — they contain database passwords. Rewrite rules from urlrewrite.php — Bitrix generates them, but with nginx + PHP-FPM they need to be duplicated. PHP 8.0–8.2 with extensions: mbstring, curl, gd, xml, json, opcache, redis/memcached. Key php.ini settings: opcache.memory_consumption=256, opcache.max_accelerated_files=20000, max_execution_time=300, memory_limit=512M, upload_max_filesize=100M, post_max_size=128M.

Database and Caching

MySQL/MariaDB. Key my.cnf parameters: innodb_buffer_pool_size — 70–80% RAM, innodb_log_file_size=256M, tmp_table_size=256M, max_heap_table_size=256M, thread_pool_size — number of CPU cores. Encoding utf8mb4 mandatory, otherwise emoji and special characters break. Redis is preferable to Memcached for Bitrix — supports persistent connections and is more reliable. In production, Redis handles concurrent writes three times faster than Memcached under typical load. Configure in .settings_extra.php:

'cache' => ['value' => ['type' => ['class_name' => '\\Bitrix\\Main\\Data\\CacheEngineRedis']]]
'session' => ['value' => ['mode' => 'default', 'handlers' => ['general' => ['type' => 'redis']]]]

sudo apt install redis-server
sudo systemctl enable redis

SSL, Email, and Cron

SSL — Let's Encrypt via certbot in 90% of cases. Redirect HTTP → HTTPS (301), HSTS, TLS 1.2/1.3, OCSP Stapling. In Bitrix, switch to HTTPS in the main module settings. Email: abandon mail() — connect SMTP (Yandex.Mail for domain, Mail.ru for Business). Be sure to configure SPF, DKIM, DMARC. Without SPF, emails go to spam. Test deliverability via mail-tester.com — score 9+/10. Cron: Bitrix agents switch to system cron — * * * * * /usr/bin/php /var/www/bitrix/modules/main/tools/cron_events.php. Schedule 1C exchange (15–60 min), search reindex, backups (mysqldump + rsync, rotation 7+4), temporary file cleanup.

Security and Administration

File system: owner www-data, directories 755, files 644, upload 775. nginx blocks access to configuration files. Enable Bitrix Proactive Protection — WAF, activity control (block after 5 failed attempts), kernel integrity check. For admin panel: two-factor authentication via Google Authenticator or OTP, restrict access by IP via nginx for paranoid.

How Long Does 1C-Bitrix Installation and Configuration Take?

Post-Installation Checklist

1. Performance Monitor (/bitrix/admin/perfmon_panel.php) — aim for 30+ points. Below 20 means serious configuration issues.
2. System Check — automatic check of all parameters. Red items must be fixed, yellow — case by case.
3. Security Scanner — check for typical vulnerabilities.
4. PageSpeed Insights — TTFB < 200ms on VPS, LCP < 2.5s.
5. Test 1C exchange — if integration is planned, verify CommerceML exchange before launch.

Additionally, check software versions, caching settings, cron operation, SSL certificate, SPF/DKIM/DMARC, access rights, delete default users and pages. For projects with 54-FZ, ensure fiscalization is configured via OFD provider.

Deliverables

• Fully configured server for 1C-Bitrix with MySQL, PHP, nginx optimization.
• Installed and activated license of the required edition.
• SSL certificate, email settings, cron and backups.
• Documentation: all configuration parameters, access credentials, cron tasks.
• Content manager training: how to log into admin panel, add products, upload images.
• Post-installation support for 30 days — consultations on settings.

Why Trust Professionals with Installation?

Incorrect installation means lost time and money. We've seen projects where a store on "Start" couldn't handle 50 visitors because innodb_buffer_pool_size wasn't configured. After migrating to VPS with correct configuration, the site "flew". Incorrect configuration can cost 30,000 RUB monthly due to excessive resource consumption. You get a ready-made architecture that scales. Order turnkey 1C-Bitrix installation — get a reliable platform for business growth. Contact us for a free consultation: we'll calculate the cost and time for your project. Over 7 years of experience, 120+ Bitrix projects implemented, including highload stores with million-item catalogs. Get in touch — we'll help configure Bitrix for your project.