Devices

List of compatible devices

Warning

There is no guarantee that a device not included in the list will function correctly — even if it's from the same vendor and is partially or fully compatible at the API level.

Outdoor intercoms

Multisubscriber

Vendor	Model	Recommended FW	Note
Beward	DKS	Any stable	The manufacturer sometimes releases models with new names, but their functionality and API remain unchanged for the most part. However, each new model REQUIRES testing before use.
Qtech	QDB-27C-H	227.221.3.89	Out of production 🪦
Intersvyaz	ISCOM X1 rev.2 (Sokol)	2.2.5.15.7
	ISCOM X1 rev.5 (Sokol Plus)	2.5.0.10.13
Sputnik	Cloud		No motion detection (required for FRS). No snapshots (required for FRS and calls to mobile app). Video during a call only via WebRTC from a media server. Interaction via Asgard API.
Rubetek	RV-3434	2025.04.171131928 (http) 2025.04.171131939 (https)
Ufanet	SECRET TOP T3 API SECRET TOP T4 API	2.5.09.09	Beta testing.
Bas-IP	AA-07FB	3.26.4	For motion detection use an external sensor, connected to the door sensor (DS) pins. Doesn't support coordinate matrix systems (AA-07FBV). Please read the instructions for configuring the internal RFID reader!
	AA-07BD	3.13.0	No syslog support. As a result, there will be no event log in the mobile app (except for door openings triggered from the app), and FALPRS is not supported. Please read the instructions for configuring the internal RFID reader!

Single subscriber

Vendor	Model	Recommended FW	Note
Beward	DS	Any stable	The manufacturer sometimes releases models with new names, but their functionality and API remain unchanged for the most part. However, each new model REQUIRES testing before use.
Akuvox	E12S / E12W	12.30.2.102 (v1.0) 312.30.10.9 (v2.0)	We recommend using a v2.0 device: it has better sound and image and it is more stable.
	R20A	320.30.11.53 (v5.0)	Only v5.0 has been tested. Please read the instructions for adding a device to the system!

Controllers | relays

Vendor	Model	Recommended FW	Note
Silines	RODOS	Any stable	RODOS-8 and RODOS-9 have been tested, but the entire product line should be supported.

Client intercoms

Vendor	Model	Notes
Akuvox	C313S C315S
Beward	SM700 SM700W
Bas-IP	AZ-07L	Install the Teledom application on your device

Cameras

Vendor	Model	Recommended FW
Brovotech	IPC-MG7-5x60 IPC-MG7-3x60	Any stable
iPera	iFLOW F-IC-2146CM	Any stable
OMNY	BASE ViBe8EZ-WDS 27135	IPCAM_V4.06.62.251024

Smart configurator

Warning

If you manually change any settings on the device (especially the settings described below), this means that you fully understand what you are doing and understand that these settings can be overwritten by the autoconfigurator.

Our solution automatically configures supported devices. It has two main stages - the initial configuring and the regular configuring.

Initial configuring

This stage automatically triggers when you add a new device. At this point, the device should have a default password so that the configurator has access to this device.

The following things setting up here:

• The device password changes to the one indicated in the settings of the device in RBT.
• Optimal settings for audio and video streams.
• Concierge number (9999).
• SOS number (112).
• Call timeout (45 s).
• Talk timeout (90 s).
• Unlock time (5 sec).
• Depending on the device, other settings occur, the regular change of which is not assumed.

So you can change some of these settings at your own risk and they will not be affected until you reset the device to factory settings.

Tip

If you need to reconfigure a device that has already been added, you need to reset it to factory settings and then bring up initial setup from the entrance menu or set the "Initial setup" panel settings to "Yes" and apply the settings.

Regular configuring

These settings come from the database and server configuration file:

• For outdoor intercoms:
  • DTMF code for main lock (intercom settings -> DTMF Door Opening Code).
  • Event server (server config.json, syslog_servers section).
  • Intercom SIP account (server config.json, backends -> sip section and intercom settings -> Server).
  • Are the locks closed (intercom settings -> Locks Are Open).
  • Flats (flat settings and binding to entrances).
  • RFID key cards (superkeys, subscriber keys, flat keys, entrance keys, house keys, company keys).
  • Gate settings (for shared entrances).
  • Global CMS levels (entrance settings -> Levels).
  • CMS model (entrance settings -> CMS).
  • CMS matrix (CMS settings).
  • NTP (server config.json, ntp_servers section and timezone from city to region or "Europe/Moscow" timezone if not selected).
  • Ticker text (intercom settings -> Display OR entrance settings -> Caller ID if Display is empty).
• For cameras:
  • Event server (server config.json, syslog_servers section).
  • Motion detection settings (camera settings -> Detection).
  • NTP (server config.json, ntp_servers section and camera settings -> Secondary -> Timezone or "Europe/Moscow" timezone if not selected).
  • OSD text (camera settings -> Primary -> Name).

Any changes in the settings of devices, entrances, apartments and RFID keys create tasks to reconfigure the necessary devices. These tasks are queued and start executing within a minute. The configurator will find the difference between the settings in the database and the settings in the device and reconfigure only the necessary parameters.

To manually start the configurator, you can use this command:

php server/cli.php --autoconfigure-device=<domophone|camera> --id=<device ID> [--first-time]

Warning

We currently don't have a mechanism to track changes to the server config file, so if you make changes to the server config.json file, you will have to run the configurator manually or click "Configure intercom" in the entrance menu to which the intercom is linked.

Note

As you can see, some device settings, such as picture settings, audio levels, audio samples, etc., are not tracked and not overwritten by RBT. You can change them as you wish.

Custom class

If you want to change or extend the behavior of the class responsible for the device, you can create a "custom" directory and place your own class with the same name as the original one inside it. The device loader first looks for a class in the "custom" directory. Such directories are not tracked by git. Below is an example in which one method is overridden for the device:

<?php

// /opt/rbt/server/hw/ip/domophone/is/custom/iscomx1plus.php

namespace hw\ip\domophone\is\custom;

class iscomx1plus extends \hw\ip\domophone\is\iscomx1plus
{

    public function configureEncoding(): void
    {
        $this->apiCall('/camera/audio', 'PUT', [
            'aac_enable' => false,
            'format' => 'PCMA',
        ]);
    }
}

Requirements for device integration

For full integration, the device must expose an API and send events in real time to a remote host. Syslog is the preferred mechanism, but other mechanisms, such as HTTP, are also acceptable. The device must support RTSP and provide a current camera snapshot on request. These general requirements apply to both the camera and the outdoor intercom. The more detailed description is provided below.

API requirements:

• Trigger relay(s) on request. This functionality is used for door unlocking via the mobile app or FALPRS.
• Retrieve a snapshot on request. Used by face and license plate recognition system.
• Change the default administrator password.
• Event (syslog) server settings. The device must allow configuring the server URL and port for message forwarding.
• NTP server settings.
• SIP account settings. Optionally, the device may provide settings for a STUN server.
• DTMF codes to trigger relay(s) during a SIP call.
• Text on display.
• Free passage mode. A mode in which the locks remain unlocked for a long time.
• Prefix mode (gate mode) settings. The device must provide a prefix dialing mode when serving multiple buildings with identical apartment numbers, or must support dialing numbers using delimiters (#, *) to distinguish the building number from the apartment number.
• RFID key list operations.
• Apartment settings. The device must allow reading and editing the list of apartments. Typically, each apartment record includes an apartment number, a SIP number for calls, and a personal access code (our system supports only five-digit codes). The listed settings may not necessarily belong to an apartment entity and can represent separate entities.

If the device supports calls to analog handsets it also needs API for:

• Coordinate-matrix commutator (analog system) model.
• Analog numbers for apartments. It may be represented in a matrix format, where the tens and units define the row and column, and the intersection corresponds to the called apartment. Alternatively, they may be represented as a numeric value in the apartment settings or the dialplan. In this case, the number represents the port on the commutator to which the apartment’s analog handset is connected.
• Analog levels. The device may provide options for correction of threshold levels used to detect the line state (on-hook, off-hook, door open button pressed). Thresholds are typically expressed as voltage values or in arbitrary units.
• Analog line diagnostics. The device may provide the ability to retrieve the state of the analog line to an apartment's handset for the purpose of remote diagnosis. The state may be reported as voltage measurements and/or as a textual representation of the current line state (on-hook, off-hook, door open button pressed).

Required messages for the event service

Event type	Examples of messages from real devices
Start motion / face detected	EVENT: Detected motion in 0 areas. Min area size = 0, max area size = 249344 SS_MAINAPI_ReportAlarmHappen(0, 2) EVENT:600:The face was detected and sent to the server
Stop motion (optional)	SS_MAINAPI_ReportAlarmFinish(0, 2)
Door opened via API	Opening main door by API command Opening second door by API command Main door opening by API command EVENT:108:1:Open door by API
Door opened using an RFID key	Opening door by RFID 0000003375A686, apartment 0 EVENT:101:803512EA6C2D04::Open Door By Card, RFID Key:803512EA6C2D04, Apartment No EVENT:100:197DF8B2:Access allowed by public RFID
Door opened using a personal access code	Opening door by code 77777, apartment 12 EVENT:400:42999:11:Open Door By Code, Code:42999, Apartment No 11 EVENT:400:13736:2:Access allowed by apartment code
Door opened using a DTMF code	Open main door by DTMF EVENT:106:1:1:Open Door By DTMF, DTMF Symbol 1 ,Apartment No 1 EVENT:106:1:46:Open door by DTMF Open door by VoIP: end-to-end id: 662874536a4e2259690304, alias: 46, relay: 1
Door opened using an analog handset	Opening door by CMS handset for apartment 12 Open door by AT: end-to-end id: 8776607cc48b1279369351, alias: 39, relay: 1
Door opened using a button (signal on a discrete input)	Main door button press 104:Main door opened by button press EVENT:102:INPUTA:Exit button pressed,INPUTA Open door by exit button: relay: 1 Open door by exit button: relay: 2
Call started	Calling to 12 flat... Calling to 1 house 12 flat... Start - general: end-to-end id: 8776607cc48b1279369351, alias: 39
SIP call started	Calling sip:12@192.168.13.60:5060 through account 000:[77692] Calling sip:1000134903@192.168.13.60:5060 through account 0(0)... Start - VoIP: end-to-end id: 8776607cc48b1279369351, alias: 39, number: 1000050452
Analog call started	CMS handset call started for apartment 12 Start - AT: end-to-end id: 8776607cc48b1279369351, alias: 39, number: 39
SIP call answered	701:[13331] SIP talk started for apartment 36 Baresip event CALL_ESTABLISHED Start VoIP call: end-to-end id: 662874536a4e2259690304, alias: 46
Analog call answered	702:[77692] CMS handset talk started for apartment 6 EVENT:702:Analog handset was picked up Start AT call: end-to-end id: 8776607cc48b1279369351, alias: 39
SIP call ended	SIP call done for apartment 12, handset is down Ending VoIP by reason "14: Call ended, receiver initiative": end-to-end id: 662874536a4e2259690304, alias: 46
Analog call ended	CMS handset call done for apartment 12, handset is down Ending AT call by reason "14: Call ended, receiver initiative": end-to-end id: 8776607cc48b1279369351, alias: 39
All calls ended	000:[77692] All calls are done for apartment 6 EVENT:000:Finished Call' General ending call: end-to-end id: 8776607cc48b1279369351, alias: 39, full duration: 8 s, first call duration: 0 s, second call duration: 4 s