You are here

Vingtor-Stentofon SDK

Key Features

  • Easy integration between AlphaCom and system management software
  • Based on Microsoft .NET
  • Microsoft Visual Studio development environment
  • Large base of library components
  • Reduces implementation time and cost of system integration

The Vingtor-Stentofon Software Development Kit (SDK) is based on Microsoft .NET technology and gives the 3rd party developer access to a wide set of software components as well as an extensive Microsoft .NET development environment and tool set.

Vingtor-Stentofon AlphaCom is a powerful communications audio server with many features directly applicable to the security industry such as direct calling, call requests and call queue handling, call transfers and escalation, PA functionality through All and Group Calls, priority calls and many more.

Close integration

Vingtor-Stentofon SDK (Software Development Kit) allows for a very close integration between the AlphaCom and security management systems. Internal exchange status information is reported by raising events and commands can be sent into the exchange by calling the appropriate method. This gives the management system full access to all features of the exchange.

Usage Integration with Microsoft .NET applications Integration with Web services
Self configuration Auto discovery of complete network configuration Auto generation of AlphaCom E and station state data
Networking Supports STENTOFON AlphaNet
DLL names and Namespaces



Apply for SDK

Once registered with an account and/or while logged in you will find the SDK application form on your profile page.

More information

Events and methods

The following is a selection of the available interfacing options, put in the context of actual implementation situations.

Call request events

A very powerful feature of the AlphaCom Audio Servers is the call request. Using this feature, a remote intercom station puts itself into the call queue of one or several guard stations. This happens when the call button on the remote intercom is pressed. The call queue handling is all done by the exchange; for instance if one guard answers, the request is removed from all call queues from other guard stations in which the call was placed. Also in case of call request transfers or escalation, the queue always reflects the correct situation. This means that management system software only needs to monitor the appropriate queue events and use this information to, for instance, flash an assigned icon to the remote intercom station.

Call connect command

Often when there is a call request, the guard wants to be able to click on the flashing icon to accept the call. Calling the method to send a connect message with the directory numbers of the guard and the icon associated intercom stations as parameters, will set up the call.

Call connected event

When the call is set up, the audio servers API will generate the call request removed events(see above) and an event stating that the guard intercom station and the remote intercom are in conversation. These messages can directly be used to change the appearance of the remote intercom icon.

Cancel call command

When the guard cancels the call, the software calls a method to cancel the call.

Call disconnected event

An event stating that the call between the two intercom stations has been disconnected is raised. The icon can be put in the ‘idle’status.

Other available events and methods

Some of the most used events and methods are:

  • Reporting the status of the intercom stations: connected, disconnected, working OK
  • Force a pre-recorded alarm message to an intercom station, group of stations or PA amplifiers
  • Force an audio program to an intercom station, group of stations or PA amplifiers
  • Make a PA announcement to pre-defined zones
  • Open doors or operate other equipment through relays
  • Read door open/closed status or other status signals through logical inputs
Solution: Integrated
Systems: AlphaCom Server System