Difference between revisions of "Pulse Trunking"

Latest revision as of 16:21, 7 March 2019

Example of Pulse Systems interconnected by Pulse Trunking

Pulse Trunking makes it possible to call between different Pulse systems. The routing between Pulse systems are easily configured in the Pulse Server Directory.

Prerequisites

Software requirements

The Pulse Server must be a station in the Turbine family with software version 4.2.3.9 or higher. Note that Pulse Trunking is not supported when an INCA Station is used as Pulse Server.

License requirements

When using a Pulse server with ver. 4.7:

A Pulse Enterprise License (Item no. 1009660002)

When using a Pulse server with ver. 4.2:

A Pulse Enterprise License (Item no. 1009660002)
A Pulse Trunking License (Item no. 1009662101) per route.

Supported features

Point to point calls with Caller ID
Door opening
Call transfer
Call forwarding
Ringlist
Station profiles

Configuration

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

Directory Number range (To - From) in the remote site
Logical name for the route
IP address and SIP port of the remote Pulse Server (Pulse Server SIP port is normally 5060)
Profile to assign calls coming from/to the route. Profiles can be used to restrict access to/from a route

Note that transit calls are not possible. There must be a direct route from the calling Pulse site to the called Pulse site.

To add a route on a Pulse Server, select Server Management > Server Configuration > Directory Settings

Pulse route configuration

Directory Start: First number in the remote Pulse system.
Directory End: Last number in the remote Pulse system. The number range must have the same amount of digits. For example 200 - 299, not 50 - 150.
Name: Logical name for the route. Any text can be used.
Profile: Profile to assign calls coming from/to the route. Profiles can be used to restrict access to/from a route.
Host: IP-Address of remote Pulse Server
Port: The SIP port used. Normally 5060.

Configuration example

Pulse system 1
Name	Saturn
Pulse server IP Address	192.168.1.10
Numberplan	40-80

Pulse system 2
Name	Venus
Pulse server IP Address	192.168.5.10
Numberplan	120-160

Pulse Configuration Example

IMPORTANT INFO REGARDING MULTIPLE PULSE SYSTEMS ON ONE LAN IP SUBNET
Because of the Pulse auto-detect and configuration, it is NOT recommended to run multiple Pulse Systems on the same LAN IP-Subnet. 
If you still, despite our recommendations want to run multiple Pulse system on the same lan subnet, we strongly recommend that you 

 -Connect and set up Pulse system 1
 -Disconnect Pulse system 1 
 -Connect and set up Pulse system 2
 -When done with all separate configuration, connect both Pulse systems.

If you are going to do configuration changes, please remember to disconnect the other Pulse system from the network.

Limitations

Pulse Server can have maximum of 50 configured Pulse trunks.
Transit calls: A client may only call to sites to which there is a direct route. In the example in the top of this article, the satellite Pulse sites may only call to central site, while central site can call all sites.
Call Transfer/Forwarding can only be done to stations to which there is a direct route.
Group calls: It is not possible to do group calls from one Pulse system to another.

@@ Line 1: / Line 1: @@
 {{P}}
-[[File:pulse_trunk.PNG|thumb|500px|Example of Pulse System]]
+[[File:pulse_trunk.PNG|thumb|500px|Example of Pulse Systems interconnected by Pulse Trunking]]
-Pulse Multisite Trunking is a feature in the Pulse Server for enabling calls between different Pulse sites.
+Pulse Trunking makes it possible to call between different Pulse systems. The routing between Pulse systems are easily configured in the Pulse Server Directory.
-Pulse Trunk Routes must be configured to enable calls between different Pulse sites. A Pulse Route is easily configured in the Pulse Server Directory.
-If routes are configured appropriately then any client at a Pulse Server can call any client at different Pulse Server.
-=Prerequisites=
+==Prerequisites==
-* The [[Pulse Server]] must be a station in the [[Turbine series|Turbine family]] with software version 4.2.3.6 or higher. Pulse Trunking is not supported when [[INCA series|INCA Station]] is used as Pulse Server.
+===Software requirements===
-* A Pulse Enterprise License (Item no. 1009660002)
+The [[Pulse Server]] must be a station in the [[:Category:Stations#Turbine_stations|Turbine family]] with software version 4.2.3.9 or higher. Note that Pulse Trunking is not supported when an [[:Category:Stations#INCA_stations|INCA Station]] is used as Pulse Server.
-* A Pulse Trunking License (Item no. 1009662101) per route.
-=Features=
+===License requirements===
-*Easy to configure and setup
+When using a Pulse server with ver. 4.7:
-*HD Audio support
+* A [[Pulse Licensing|Pulse Enterprise License]] (Item no. 1009660002)
-*Supports supplementary functions such as call transfer, call forwarding, ringlist and service profiles
-*One license is required to configure ONE Trunk Route between two sites
+When using a Pulse server with ver. 4.2:
+* A [[Pulse Licensing|Pulse Enterprise License]] (Item no. 1009660002)
+* A [[Pulse Licensing|Pulse Trunking License]] (Item no. 1009662101) per route.
-=Configuration=
+==Supported features==
+* Point to point calls with Caller ID
+* Door opening
+* Call transfer
+* Call forwarding
+* Ringlist
+* Station profiles
-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.<br>
+==Configuration==
-In addition Pulse Server 2 must have a configured route to Pulse site 1, with the number of range Pulse site 2 and IP-address of Pulse Server 1.
+Pulse Trunk Routes must be configured to enable calls between different Pulse sites. A route consists of:
+# Directory Number range (To - From) in the remote site
+# Logical name for the route
+# IP address and SIP port of the remote Pulse Server (Pulse Server SIP port is normally 5060)
+# Profile to assign calls coming from/to the route. Profiles can be used to restrict access to/from a route
+Note that transit calls are not possible. There must be a direct route from the calling Pulse site to the called Pulse site.
-To add a route on a Pulse Server, go to
-<br>
+To add a route on a Pulse Server, select '''Server Management''' > '''Server Configuration''' > '''Directory Settings'''
-'''''Server Management -> Server Configuration -> Directory Settings'''''
 <br>
 [[File:pulse-trunk-configuration.PNG|left|thumb|500px|Pulse route configuration]]
 <br style="clear:both;" />
-* '''Directory Start:'''<br> Start of the number range on the remote Pulse system.
+* '''Directory Start:''' First number in the remote Pulse system.
-* '''Directory End:'''<br> End of remote number range on remote Pulse system.
+* '''Directory End:''' Last number in the remote Pulse system. The number range must have the same amount of digits. For example 200 - 299, not 50 - 150.
- '''Note!'''
+* '''Name:''' Logical name for the route. Any text can be used.
- The number range defined in a Pulse Trunk configuration must have the same amount of digits. For example 200 - 299, not 50 - 150.
+* '''Profile:''' Profile to assign calls coming from/to the route. Profiles can be used to restrict access to/from a route.
-* '''Name:'''<br> Logical name for the route.
+* '''Host:''' IP-Address of remote Pulse Server
-* '''Profile:'''<br> Profile to assign calls coming from/to the route. Profiles can be used to restrict access to/from a route.
+* '''Port:''' The SIP port used. Normally 5060.
-* '''Host:'''<br> IP-Address of remote Pulse system..
-* '''Port:'''<br> The SIP port of remote Pulse system.
-<br>
-==Example==
+===Configuration example===
 {| class="wikitable" style="float:left; margin-left: 10px;"
@@ Line 48: / Line 52: @@
 |Saturn
 |-
-|'''IP Address'''
+|'''Pulse server IP Address'''
 |192.168.1.10
 |-
@@ Line 61: / Line 65: @@
 |Venus
 |-
-|'''IP Address'''
+|'''Pulse server IP Address'''
 |192.168.5.10
 |-
@@ Line 83: / Line 87: @@
   If you are going to do configuration changes, please remember to disconnect the other Pulse system from the network.
-=Limitations=
+==Limitations==
-* '''Transit calls:''' A client may only call to sites where there exists direct routes. In the example in the top of this article, the satellite Pulse sites may only call to central site, while central site can call all sites. '''Call Transfer/Forwarding''' can only be done to stations to which there is a direct route.
+* Pulse Server can have maximum of '''50 configured Pulse trunks'''.
-* '''Capacity:''' Each Pulse Server may have up to 50 Pulse Trunk Routes.
+* '''Transit calls:''' A client may only call to sites to which there is a direct route. In the example in the top of this article, the satellite Pulse sites may only call to central site, while central site can call all sites.
+* '''Call Transfer/Forwarding''' can only be done to stations to which there is a direct route.
 * '''Group calls:''' It is not possible to do group calls from one Pulse system to another.
+[[Category: Pulse - Configuration]]
-[[Category:Pulse]]