Devices
All devices (panels, controllers, monitors, etc.) must be added to the Link server to associate physical devices with data on the server. Adding a device to the Link server gives the ability for remote interaction and monitoring.
In the tab, you can add a new device, check already added device settings, editor deletethem. Also for each device, there is the ability to cope information, start initialization (only for SP-03), restart the task queue, and synchronize device data (to send to a device all information about settings, identifiers, users, etc., that the server has) .
Synchronize device data feature can be useful to automatically fill renewed device with existing data. For example, after replacing a broken device.
For correct server functioning, all devices must be added to the access rules that apply to the corresponding groups.
How to add a device to the Link server
Go to the Devices tab of the Device management section.
Click the plus icon in the left low corner.
Enter the device name.
Select its type: panel, monitor, access controller, elevator controller, IP camera (for Hikvision cameras), barrier (for AxxonOne integration).
Select the device model.
Indicate the device Serial number (check the Dashboard tab of the device web interface or device box). If you are adding an IP camera, enter any number in this field.
Select a group/subgroup where the device is installed.
If necessary, set location geodata for panels. This data is required for the Link app, when a visitor with a pass (added to Apple Wallet) approaches the available panel (with location), the pass will be automatically shown.
Add a description, if necessary.
Allow remote lock opening (from the device web interface, via API), if necessary.
Enter network settings for server and device interaction:
select the appropriate communication protocol: HTTP or MQTT (is recommended to use);
enter the device IP address and port (for HTTP only);
enter login and password that are used to enter the device web interface;
indicate server interaction password (is created in the Management system section (Network tab) of the device web interface).
Also, the same network settings as for the server must be entered in the device web interface. The management system must be enabled for the device:
Log in to the device web interface. By default, the username is admin, and the password is 123456.
Go to the Network tab > Management system section.
Select the necessary protocol: HTTP or MQTT (is recommended to use) in the Mode field.
Enter all required data.
Submit settings.
Detailed instructions are here.
If required, configure additional settings in the corresponding section for the panel or IP camera:
select the ID of the alarm output relay on the camera that must be activated when the license plate is recognized (available for IP cameras).
set a timeout for the relay activity (available for IP cameras).
mark that the panel that is used with an additional camera for license plate recognition (required only for panels with connected Axis cameras).
For details about the usage of license plates as identifiers, see How to configure license plate recognition.
Click the Save button in the left low corner when all required data will be entered.
Users must be added to the group first, then devices must be added.
If you add devices before adding a user to a group, a feature of automatic creation of forward rules will not work correctly. If you add a device to a group without a user, device virtual number applies to an administrator, but not to the group user. So, the created forwarding queue will include the administrator instead of the user.
Remote device configuration
Device basic configurations can be done in the device web interface. And if they are done, there is no need to set them from the Link side. But if some of the following parameters are missed or require corrections, they, also, can be done in the corresponding sections. You must enable the setting section you want to send.
The following settings can be entered:
Automatic forwarding settings is a feature of automatically creating forwarding rules for apartment group user/s and sending them to device/s. If this feature is enabled, for all groups will be automatically created and applied virtual numbers. When adding a user that has a virtual number/s to a group, forwarding that includes all user numbers is automatically created. In addition, SIP and address settings are also automatically created and sent to the device.
But if there are troubles with them (e.g., logical addresses are already set for devices manually and do not match created on the server or the Link set and sent SIP settings for connecting to an external address, but internal is required, etc.), it is possible to set and sent the following settings to the device manually:
SIP settings are required for calls via SIP protocol. For correct SIP functioning, you must:
enable SIP;
select SIP address type:
◦ Server URL — for example, eu.bas-ip.link for Europe, usa.bas-ip.link for United States, as.bas-ip.link for Asia;
◦ Server external IP address — e.g.203.0.113.5, use when no domain is available;
◦ Server local IP address — e.g.192.168.1.100, use in LAN.
The Server local IP address option is available in newer versions of the system. Use it when both the device and the server are on the same local network.
If you push a Server URL to the device, make sure that all manually configured forwarding rules and concierge call settings also use the same Server URL.
If they point to the external IP address instead, calls will not work.
The same applies in reverse — if the device uses an external IP, all destinations must match.
select transport protocol — UDP, TCP or TLS;
enter SIP server address — this can be either an IP address or a domain name, for example
eu.bas-ip.link;enter SIP server proxy — this can also be either an IP address or a domain name, for example
sip:eu.bas-ip.link;server STUN IP address — for example,
stun.l.google.com;port of the STUN server — for example, 19302;
SIP number as the login;
password for the SIP number;
timeout for re-registration to renew the lost connection with the SIP server.