Pulse System Description

Overview

The Vingtor-Stentofon Pulse system is a SIP intercom system intended for small to mid-size installations for up to 64 IP stations. Some of the key features of Pulse are:

• Easy to install and configure
• Cost effective for solutions where up to 64 IP stations are needed in the network
• Supports creating Pulse trunks to inter-connect up to 50 different Pulse systems
• Single Pulse system works across multiple network subnets
• SIP Gateway interface that is easy to setup (e.g. SIP-to-GSM, SIP-to-PSTN, etc.)
• Open IP standards (SIP, HTTP(S), NTP, SNMP, RTP, etc.)
• Shared network infrastructure with other systems (CCTV, PCs, etc)
• Special SDK with API that can be used to create custom intercom solutions
• Integrated managed switch in terminals
• Wide set of special purpose IP stations and PC client
• VS-IMT: Dedicate management tool for easy configuration of large number of stations

Pulse server functions

Station auto-discovery and configuration

All Vingtor-Stentofon IP stations use auto-discovery feature which enables fully automatic discovery of all the IP stations on then network by Pulse server.

Station configuration can be done directly from Pulse server StationWeb. After IP stations are discovered with Pulse station auto-discovery, they can be immediately set up and configuration saved and applied for multiple stations at once. All the basic functions can be directly configured from Pulse server. For more specific configuration and customization, StationWeb of every IP station can be used as configuration tool. In addition, VS-IMT can be used to configure one or multiple stations in Pulse system.

More info can be found in FS IP Station auto-discovery and Configuration.

Multi-subnet support

Pulse can be deployed as a single-server system with IP stations being installed in different network subnets. There are some prerequisites for network setup so Pulse can operate without problems:

1. Network subnets (segments) with IP stations need to be routable
2. IP Multicast routing needs to be enabled and configured on the layer-3 switch or router. This is required by Pulse IP station auto-discovery and Pulse Group Call functions
3. All protocols and ports that Pulse IP stations are using must not be filtered between network subnets

Network with multiple Pulse systems

In scenarios where multiple Pulse systems are installed with dedicated servers on different subnets, IT administrator should block all multicast traffic between different Pulse systems. Still, Pulse handles such scenarios in the following way:

1. Group calls: Each Pulse client will receive "Pulse server ID" during registration process and it will filter out all the group calls multicast traffic if it does not belong to this "server ID". In addition, each server will generate a set of multicast audio addresses based on it's unique MAC address.
2. Station Discovery: During configuration of Pulse clients on sever StationWeb, discovery of all IP station on network is done. Those stations that are configured with another server IP address will automatically be deselected for configuration.

Server Call Forwarding

The Pulse Server supports server side call forwarding. When a station activates call forwarding it will notify the Pulse Server, which will store the call forwarding state. The Pulse Server will handle call forwarding for the station, thus the call forwarding will work even if the station is off-line. Forwarding status can be observed on the web page of the Pulse Server ("Server Monitoring"), where the target station of the forwarding is shown.

Station 204 is forwarded to station 203

Pulse trunking

Pulse Trunking is a feature in the Pulse Server for enabling calls between different Pulse sites. The function is enabled with Pulse-Server-Enterprise license. A total of 50 trunk routes can be configured on the Pulse server.

Pulse Trunk Routes must be configured to enable calls between different Pulse sites. A route consists of:

1. Number range for the site the route goes to
2. Logical name for the route
3. IP address and SIP port of the remote Pulse Server on the remote site (Pulse Server SIP port is normally 5060)
4. Profile to assign calls coming from/to the route. Profiles can be used to restrict access to/from a route

For two sites to call each other 2 routes must be configured. First, a route must be configured in Pulse Server 1, the route must define the number range of Pulse site 2 and the IP address of Pulse Server 2. In addition Pulse Server 2 must have a configured route to Pulse site 1, with the number range of Pulse site 1 and IP address of Pulse Server 1.

If only 1 route is enabled, site 1 with the Enterprise license can call site 2, but site 2 cannot call site 1

Example of Pulse Systems interconnected by Pulse Trunking

A client may only call to sites where there exists direct routes. In the example, the Remote sites may only call Central site, because only a route to Central site is configured. The Central site may call all of the Remote sites because it has routes configured to each Remote site. Configuration example for Central site Pulse server:

Configuration example of Pulse Trunking

Pulse SDK

Pulse system can be extended and customized with VS-SDK for Pulse. Key features are:

• Build your own Vingtor-Stentofon Pulse intercom solution
• Java and .NET APIs with ready-to-use examples and documentation (Intercom API)
• Remotely control Turbine intercoms

SDK comes with easy to use API, out-of-box integration with Pulse Intercom system, support for all Turbine Intercom devices and PC soft-client, demo apps, code examples and API reference documentation. Intercom API even supports advanced Call center functions.

More info about VS-SDK for Pulse can be found in VS-SDK for Pulse (Intercom API).