Skip to Content
Go back
BAS-IP / Become Integration partner

Open Integration with Third-Party Systems

BAS-IP’s dedication to flexibility and expanded functionality through seamless compatibility.

One of BAS-IP’s main priorities in the rapidly changing information and digital environment is flexibility and adaptability to new challenges and market requirements. Therefore, we are open to integration with any third-party systems and products in order to obtain new functionality to meet customer needs.

General integration development flow

Request Validation

To ensure a comprehensive and transparent description of your integration request, we encourage you to complete the integration request form in detail. If you encounter challenges in formulating the request—such as limited familiarity with BAS-IP products – you are welcome to request a consultation with an integration manager. Our specialist will carefully review your situation and guide you in crafting and submitting your request effectively.

Evaluation and analysis of the request

Once a request is received, the BAS-IP team conducts a thorough evaluation, including:

  • Assessing viability and technical feasibility.
  • Estimating potential benefits and costs of integration

During this phase, the integration manager collaborates with the client to finalize the integration requirements. This may involve:

  • Signing NDAs or other agreements as needed.
  • Providing access to test environments or delivering test equipment.

Upon completing the analysis, the BAS-IP team communicates the decision regarding the request and any associated next step

Coordination of commitments

If the request is approved, the integration manager works with the client to draft and agree upon a document that outlines:

  • Responsibilities of all parties during development.
  • The scope of work.
  • A detailed integration implementation plan.

This ensures alignment and clarity before development begins.

Implementation of integration

Once commitments are finalized, the development team begins working on the solution based on the approved requirements. The integration manager facilitates communication between the development teams of both parties to ensure smooth collaboration.

Post-production and Feedback

After the actual implementation of the request, the responsible party fulfils the obligations agreed upon earlier, which may include:

  • Preparing and delivering documentation and user manuals.
  • Demonstrating the integrated solution.
  • Publishing relevant updates on company platforms.

Feedback is collected and processed in line with previously agreed terms to ensure client satisfaction and continuous improvement.

 

POSSIBLE FIELDS OF THE INTEGRATION

Using BAS-IP open protocols, APIs and hardware interfaces the integration could be developed with such third party systems:

Access control systems

Video management systems

Audio/video communication systems

Home automation

Elevators control systems

Possible technologies of our products to be used in integration

Intercom devices

RTSP

  • Media Stream Control: Supports operations like play, pause, stop, and seek for real-time audio and video.
  • Real-Time Streaming: Enables live or on-demand media streaming over IP networks.
  • Remote Management: Allows clients to control media streams from a server remotely.
  • Wide Application: Commonly used in surveillance systems, IP intercoms, and media servers.
  • Protocol Flexibility: Works seamlessly with various codecs and streaming formats.

Frequent scenario:

Any BAS-IP entrance panel is equipped with a camera and the RTSP protocol accordingly. Thanks to this you can add the intercom as a camera for viewing in a VMS or NVR. The protocol enables one-way real-time audio-video transmission from the device to the server. Also the server may record and store RTSP streams taken from BAS-IP entrance panel cameras.

SIP

  • VoIP Support: Core protocol for Voice over IP (VoIP) communications.
  • Device Interoperability: Ensures compatibility between devices and systems from different manufacturers.
  • Real-Time Communication: Enables instant voice and video calls, conferencing, and messaging.
  • Scalability: Supports both point-to-point and multipoint communication.
  • Integration with Other Protocols: Works alongside RTP for media transport and other protocols for authentication and encryption.

Frequent scenario:

Any BAS-IP intercom supports SIP protocol, which means that the device can be used as a SIP client in third-party VoIP systems. This option provides an opportunity to register a BAS-IP device via SIP on a third-party PBX server, which in turn allows calls between BAS-IP device and any other SIP client, which can be either intercom of other manufacturers, IP phones, soft phones, web applications. SIP provides two-way audio-video communication with the possibility of transmitting additional data during the session, e.g. transmission of DTMF values to initiate lock openings.

Another use case for SIP is to connect a SIP trunk to a PBX server to enable calls from the intercom to mobile and landline numbers, which is a decent solution for customers who need to receive calls directly to the phone rather than to some mobile app.

Wiegand

  • Access Control Interface: Widely used for communication between access control systems and peripheral devices (e.g., card readers, keypads).
  • Simple Data Transmission: Transmits data using three wires: Data0, Data1, and Ground.
  • Standardized Format: Supports common formats like 26-bit or custom configurations for flexibility.
  • Compatibility: Works with various access control systems and legacy devices.
  • Secure Transmission: Uses unidirectional communication, reducing the risk of external interference.

Frequent scenario:

Any BAS-IP intercom is equipped with a Wiegand interface as well as a built-in card reader. This interface allows both the transmission of data read by the built-in reader to a third-party ACS for decision-making and the transmission of data read by the third-party reader to the BAS-IP door communication system for decision-making. This option is appropriate to use when the customer’s system is restricted to use either a certain ACS or certain readers.

HTTP REST API

  • Getting basic information about the device
  • Enable/disable devices features
  • Send/receive data from device
  • Interaction with third-party server

 Frequent scenario:

Any BAS-IP device has its own API to work with internal system entities, features, data and logs. This means that any third-party system can access and work with the device through the corresponding API endpoints and requests. This option allows the development of solutions where BAS-IP devices will be managed and administered from third-party systems and their interfaces. For example, data about users, their IDs and apartments/rooms can be sent to the device from a third-party system interface.

Link Platform

Link SIP

  • VoIP Support: Core protocol for Voice over IP (VoIP) communications.
  • Device Interoperability: Ensures compatibility between devices and systems from different manufacturers.
  • Real-Time Communication: Enables instant voice and video calls, conferencing, and messaging.
  • Scalability: Supports both point-to-point and multipoint communication.
  • Integration with Other Protocols: Works alongside RTP for media transport and other protocols for authentication and encryption.

Frequent scenario:

We provide Link software in software-as-a-service version and self-host on-premises version. Both versions can be used with built-in SIP servers.

The SaaS version of Link software can be connected with SIP trunk to provide Bas-IP intercoms with an option to make calls to mobile and landline numbers.

The self-host version on Link can also be connected with a SIP trunk and moreover built-in SIP server in self-host version allows registration of third party SIP devices and SIP softphones. This option allows connection of third-party SIP intercoms, telephones, softphones to the Link server and, as a result, enables two-way audio-video communication between a third-party device and BAS-IP devices/applications, with the possibility of transmitting additional data during the session, e.g. transmission of DTMF values to initiate lock openings.

Beside the flexible calls management both SaaS and self-host versions of Link provide huge automation configuration features for BAS-IP hardware and software.

This includes:

  • Automatic SIP configuration on BAS-IP intercoms and Link mobile app
  • Automatic access control data transmission to BAS-IP intercoms
  • Automatic generating and sending phone books to devices
  • Logging of SIP calls and other events

Such automation processes ensure fast and simple intercom system basic configuration allowing the system to work almost right out of the box.

Link HTTP REST API

Frequent scenario:

The Link software API allows you to interact with entities and features through the corresponding endpoints. In this way, a third-party system can switch server functions on and off, send and receive data and logs from the server. Among the Link server main opportunities which can be utilized via API are:

  • adding people to their building projects and giving access to areas neсessary for them;
  • granting various permissions depending on user role to the server functionality;
  • providing permanent (card, keychain, access code, QR code, Face ID, UKEY, license plate) or temporary (QR-code, URL, access code, license plate) identifiers for users/guests with configurable validity period;
  • flexible access conditions configuration for various users or guest identifiers;
  • sending messages or polls for all or selected users and their devices;
  • visitors and their actions (passes, calls, interaction with devices) monitoring;
  • remote devices configuration;
  • virtual numbers providing;
  • calls forwarding configuration;
  • mobile apps support.

Link mobile app SDK

  • Core Functionality: Essential tools and libraries for integrating specific features.
  • Platform Compatibility: iOS and Android support.
  • Comprehensive Documentation: Clear guides, sample code, and tutorials for integration.
  • APIs and Interfaces: Seamless communication between the app and SDK services.
  • Authentication and Security: Secure protocols to protect data and resources.

Frequent scenario:

The Link mobile app is the end-user side of the Link infrastructure. The Link app SDK allows you to develop or customize your own app based on our app model and use it in combination with our Link server.

BLE mobile access identifier UKEY

UKEY mobile app SDK

  • Core Functionality: Essential tools and libraries for integrating specific features.
  • Platform Compatibility: iOS and Android support.
  • Comprehensive Documentation: Clear guides, sample code, and tutorials for integration.
  • APIs and Interfaces: Seamless communication between the app and SDK services.
  • Authentication and Security: Secure protocols to protect data and resources.

Frequent scenario:

UKEY is an app that allows you to use your smartphone as an identifier (key) to access the building. The app works via Bluetooth at 2.4 GHz frequency. It allows opening the lock by pressing the correspondent button in the app or by screen unlocking when the phone is near the reader. So that the app provides hands-free access. The Ukey app SDK allows you to develop or customize your own app based on our app model.