Connecting Lulu to your FreePBX server

Lulu runs as a module inside an existing FreePBX system, so you'll need FreePBX (with Asterisk) already installed and reachable from the internet.

If you don't have FreePBX yet

• Install FreePBX on a dedicated server or VM — the official ISO from freepbx.org is the simplest path.
• Complete the initial setup wizard and confirm at least one extension registers and can make internal calls.

Router / firewall settings

Your FreePBX server needs to be reachable from the internet on a few ports:

• SIP/PJSIP (typically 5060 or a custom port) — for extensions and trunks
• RTP range — for call audio, usually 10000–20000
• 8090/tcp — Lulu's own bridge service, used for click-to-call and status checks

Redis

Lulu uses Redis locally (not internet-facing, no firewall/port-forwarding needed) to handle call events reliably at volume. Most FreePBX distros don't include it by default — if it's missing, install it before running the one-time setup script in the next step:

• yum install redis php-pecl-redis5 (or your distro's equivalent) — the bootstrap script enables and starts it, but doesn't install it if it's genuinely absent.

The module installs from a single file — no manual file copying needed for the install itself.

1. Download the module file — no account needed.
2. In FreePBX, go to Admin → Module Admin.
3. Click Upload Module, choose the file, and confirm.
4. Once installed, click Apply Config if prompted.

A new Lulu Telephony item appears in the top navigation bar. The module sets up its own background services automatically — but one one-time step needs a human with server access, described next.

Nothing to run on the server

The module sets up its own background services, permissions and firewall rules the first time FreePBX starts after installing it. Press Apply Config (or restart Asterisk) and setup completes on its own — there is no script to paste and no SSH access needed.

Open Lulu Telephony in FreePBX. Since the module isn't paired with a Bitrix24 account yet, you'll see the connection screen first.

Connection details

1. Enter your Bitrix24 URL (e.g. yourcompany.bitrix24.com) — this only works if you've already installed the Lulu app from the Bitrix24 marketplace.
2. Enter this server's public IP or domain — the same address you set up port forwarding for.
3. Click Check Connection. Lulu verifies your Bitrix24 app is installed and that this server is actually reachable from the internet.

Contact person

Fill in a name, email, and phone number — this is who Lulu will reach for license renewal reminders, updates, and account-related notices. Use a real inbox someone actually checks.

Once the connection check passes, Submit becomes clickable. Click it to finish pairing.

Under the Lines & Tasks tab, map each FreePBX phone number (DID) to the corresponding Bitrix24 line number, and set up task templates used for missed-call follow-ups.

• Pick a FreePBX DID from the dropdown (pulled directly from your existing Inbound Routes).
• Enter the matching Bitrix24 line number and a label.
• Add as many mappings as you have incoming numbers.
• Configure task templates — these control what task gets created and assigned when a call is missed.

Routing points are where you decide what happens to an inbound call — who it rings, how leads get created, and whether callers are asked to rate the call afterward.

• Create a routing point and choose its destination — an extension, ring group, or queue.
• Decide whether new callers automatically create a lead, and who owns it by default.
• Turn on post-call rating if you want callers asked to rate the call by pressing a number after it ends.
• Set a missed-call policy — who gets notified or assigned a task if nobody answers.

Once saved, point your FreePBX inbound routes at the generated routing point context to put it live.

Once everything's connected, the Connection tab is your day-to-day home base:

• License & Connectivity — shows whether the integration is active, your plan, and extension count.
• Click-to-Call Status and Bridge Service — live status of the two things that need to be working for calls to sync.
• Call Log — a running history of recent calls and how they were handled.
• Error Log — anything that went wrong, with a Download Logs button that bundles everything needed to troubleshoot, ready to hand to support.

If your account moves past 5 extensions, you'll need a paid plan — see pricing.