Doorbell App and Fora Soft logos

Video calls from building intercoms to a mobile app

Published: Nov 14, 2026
Incoming intercom call from the front door with live entrance camera video and Decline, Unlock and Answer buttons
Resident's app: front door camera, Open the door button and recent calls
Call log on the debug page with panels, backend answers, routes and call statuses
Fora Soft built the telephony and video layer of Doorbell App, between the door panel and the mobile app: a cloud bridge on LiveKit SIP that brings a SIP call into a video room with the app; a SIP server that routes each call; a media server for entrance cameras; and a software VoIP adapter for the client's on-site hardware. Later we moved SIP server functions onto the device itself. The client's team built the iOS and Android app and the main backend.
Doorbell App delivers calls from building intercoms to residents' mobile phones: a visitor dials an apartment on the existing door panel, and the resident answers in a mobile app with live video from the entrance camera. The client is a US company that upgrades access control in buildings; its name is not disclosed. We worked on the project from April 2024 to August 2025. A related project: Doma.ai.
Call flow: the door panel sends tones to the software VoIP adapter, a SIP call goes to the SIP server, which routes it to a LiveKit video room with the app and entrance camera or to a phone number

How the system works

The system works like this: the panel's call becomes a SIP call, and the SIP server decides where it goes. It ends up either in a video room with the app and the camera or on a regular phone number, which can also be another intercom's line.

The hardest part of the project is joining three worlds that don't work together out of the box: analog phone lines and tone dialing at the door, SIP telephony in the middle, and WebRTC video in the app. Because this is door access, a call still has to reach the resident when the client's backend returns an invalid response or the primary carrier is down.

Who uses the platform

  • Visitors dial an apartment on the door panel, the intercom unit already installed at the entrance. Many of these panels dial by tones and carry voice only.
  • Residents receive the call in the client's mobile app, see and talk to the visitor, and can unlock the door from the app.
  • The client's team runs the main backend, which decides for each call whether it goes to the app or to a phone number, and sends push notifications to residents.
Resident's app: front door camera view, Open the door button and recent calls from a visitor, a courier and an unknown caller
Lock screen push notification: visitor at the front door, and a door unlocked from the app

Highlights

  • Live video for voice-only intercoms, with the existing panels left in place.
  • One device fewer in the client's kit: our software replaced a hardware VoIP adapter.
  • Calls that still get through when the client's backend or the primary carrier fails: a fallback to the resident's phone, a backup carrier, automatic re-registration and self-restart.
  • Two-way tone handling, so old panels can dial out and receive a door-unlock command from the app.
  • The riskiest part checked first: LiveKit SIP, then in preview, was tested with the client's carrier before the rest was built.

Video calls from a legacy intercom to a mobile app

Buildings with old panels get video calls without replacing the panel, using the camera already installed at the entrance.

Once our software adapter on the on-site device has turned the panel's call into a SIP call, it has to reach the app, which runs on WebRTC. We connected the two using LiveKit SIP, LiveKit's SIP-to-WebRTC bridge. The call from the panel lands in a LiveKit video room, and the resident's app and the entrance camera join the same room. The resident hears the visitor, talks back and sees who is at the door. The SIP server works with standard SIP devices and softphones, so the system isn't tied to one vendor's intercoms.

A call goes like this:

  • A visitor dials an apartment on the panel. A tone-dialing panel sends tones, and the adapter turns them into a number and places a SIP call.
  • The SIP server asks the client's backend whether the call goes to the app or to a phone number (section 4 covers what happens if the answer is invalid).
  • For an app call, the call joins a video room. Our software reports the call and the caller's number to the backend, which sends push notifications to residents. Until someone answers, the visitor hears a waiting message or tone, which stops on its own when the resident joins.
  • The media server pulls video from the camera linked to that panel and sends it into the same room.
  • The resident answers in the app, sees and talks to the visitor, and can unlock the door. The unlock command reaches the panel as a tone, the same kind a push-button phone sends.
  • If nobody answers within the set time, or the backend asks to end the call, the call ends and the video room is deleted, so abandoned calls and rooms don't pile up.
Incoming intercom call in the app with live entrance camera video and Decline, Unlock and Answer buttons
Telephony options compared: LiveKit SIP picked over our own FreeSWITCH server and Twilio cloud telephony, tested with the client's carrier first

Proof of concept before full development

The stack choice was confirmed by a working test on the client's own carrier before the rest of the system was built. The work went from a proof of concept that checked whether the chosen services worked together to software running on the client's own hardware.

We compared three approaches: LiveKit SIP, our own FreeSWITCH server and Twilio cloud telephony. For each we laid out the pros and cons, including per-minute pricing and the cost of running our own servers. We picked LiveKit, then tested the riskiest part first: LiveKit SIP was in preview at the time, and its developers had tested it with only two carriers, while the client used a third. We confirmed compatibility with that third carrier.

A software VoIP adapter instead of a separate device

The client's on-site kit became simpler and smaller: it lost one device.

We replaced a Grandstream hardware VoIP adapter (ATA) with software built on PJSIP. It runs on an Orange Pi Zero 3 compact computer that is already part of the client's kit and also serves as its 4G router.

The adapter runs in a Docker container and is configured with a settings file, so we debugged the same code and settings on a regular computer and then ran it on the board. It places and receives calls: on an incoming call it rings the connected phone line. It talks to the other programs on the device through short commands and status messages such as "handset off-hook", "dial a number", "call started", "call answered" and "error". Because other programs control the adapter only through these messages, we could test it by sending them ourselves before the board that connects to the phone line was available.

Then: door panel, Grandstream hardware ATA and Orange Pi Zero 3 router. Now: door panel and Orange Pi Zero 3 with our PJSIP adapter
Call log on the debug page: answered app calls, fallback to the resident's phone after an invalid or timed-out backend answer

A fallback route to the resident's phone

A failure on the client's side doesn't have to leave the visitor unanswered.

Before each call, the SIP server asks the client's backend where to send it: to the app, or through a carrier to a regular number, which can be a phone or another intercom's line. If the backend returns an invalid response, the SIP server sends the call to the resident's phone number by itself. The time the SIP server waits for the backend's answer is configurable.

Tone dialing for legacy panels

Old panels work as they are, including remote door unlock.

An old panel calls a resident by tone dialing, the same way a push-button phone does. We taught the adapter to detect these tones right in the audio, assemble the number and call it. Tones go the other way too: the adapter handles them as RTP events under RFC 2833 on the SIP side and can play tones into the call on the line side. This is how the panel receives commands from the resident, such as a door unlock sent from the app. We also added echo cancellation so calls over the analog line sound cleaner.

Two-way tones: the panel dials by tones and the adapter places a SIP call; an unlock from the app goes as an RFC 2833 event and is played to the panel as a tone
Entrance cameras linked to panels over RTSP: one streaming during a call, the others idle, with credentials kept on the server

Camera video only for the duration of the call

Camera traffic and media server load come only from active calls.

Entrance cameras stream over RTSP, which LiveKit doesn't accept directly, so we built a media server. On an incoming call it pulls the camera's stream into the call's room. When the call ends, the media server stops pulling the stream. The system works with the cameras already installed at the entrance. Camera logins and passwords stay on the server and are not sent to the app.

Safeguards for round-the-clock operation

The adapter is designed to run unattended. We built several safeguards into it:

  • if the primary carrier is unavailable, calls go through a backup one;
  • the adapter restores its SIP registration by itself, with a configurable interval and number of retries;
  • it uses a STUN server to help it work behind a router;
  • on a critical error it reports the failure and restarts itself.

Registration status and the progress of each call are visible to the other programs on the device, and logs go to external logging systems (rsyslog, Splunk).

Adapter status: primary carrier with backup, automatic SIP registration, STUN and critical error restart, with logs sent to rsyslog and Splunk
Then: adapter on the device, cloud SIP server and video room. Now: adapter with SIP server functions and video room

SIP server functions moved onto the device

The less a call depends on cloud servers, the fewer places there are where a single failure can leave a building without a connection.

The cloud SIP server came first. At a later stage we moved SIP server functions into the adapter software on the device itself.

Telephony bugs found and fixed

Visitors and residents notice telephony failures right away. We found and fixed problems that are hard to reproduce:

  • a long pause before the resident's phone started ringing, so visitors could leave before anyone answered;
  • a replaced caller ID, so residents saw an unknown number;
  • adapter registration failures on the server;
  • network errors in the adapter's Docker container.
Telephony issues fixed: long pause before ringing, replaced caller ID, adapter registration failures and Docker network errors
CI pipeline: ESLint and Commitlint, SonarQube gate and Docker image passed, automatic deploy to development, manual deploy to testing and demo

Test environments and automated checks

The team could test calls without waiting for the mobile app.

We set up separate development, testing and demo environments. Each accepts calls from a regular softphone and has a debug page and API documentation.

Builds and deployments are automated. Every merge request goes through code style and commit message checks and a SonarQube quality gate. Code merged into the development branch is deployed to its environment automatically, and the testing and demo environments are updated with one click. After builds of the development and testing branches, tracker tasks move to the next status automatically. Server logs and load are visible in a shared monitoring system.

Technologies

🖥 Platforms
iOS, Android (client's app), Linux cloud server, Orange Pi Zero 3 (embedded Linux)
📞 Telephony
LiveKit SIP, SIP, PJSIP, DTMF (RFC 2833), STUN, BulkVS SIP trunk
📹 Video
LiveKit, WebRTC, RTSP
📊 Logging and monitoring
rsyslog, Splunk, ELK, Grafana
🔁 CI/CD and quality
GitLab CI/CD, SonarQube, ESLint, Commitlint
⚙️ Backend
Redis, Docker, Traefik
Doorbell App logo with iOS and Android labels