-
Notifications
You must be signed in to change notification settings - Fork 17
Devices
Vendor | Model | Recommended FW | Note |
---|---|---|---|
Beward | DKS | Any stable | The manufacturer constantly 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 | |
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 | 2024.10.157121410 | |
Ufanet | SECRET TOP T3 API | 2.4.09.04 | Beta testing |
Vendor | Model | Recommended FW | Note |
---|---|---|---|
Beward | DS | Any stable | The manufacturer constantly 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 |
Vendor | Model | Recommended FW | Note |
---|---|---|---|
Silines | RODOS-8 | Any stable |
Vendor | Model | Notes |
---|---|---|
Akuvox |
C313S C315S |
|
Beward |
SM700 SM700W |
|
bas IP | AZ-07L | Install the Teledom application on your device |
⚠️
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.
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.
💡
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.
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 (entrance settings -> Caller ID).
- For cameras:
- Event server (server config.json,
syslog_servers
section). - Motion detection settings (camera settings -> Secondary -> Detection Area).
- 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).
- Event server (server config.json,
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]
⚠️
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.
💡
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.