Actions

Difference between revisions of "Linked Edge Controllers"

From Zenitel Wiki

(Configuration example)
Line 1: Line 1:
 
{{E}}
 
{{E}}
[[File:pulse_trunk.PNG|thumb|500px|Example of Pulse Systems interconnected by Pulse Trunking]]
+
[[File:pulse_trunk.PNG|thumb|500px|Example of IC-EDGE Systems interconnected by Edge Link]]
Pulse Trunking makes it possible to call between different Pulse systems. The routing between Pulse systems are easily configured in the Pulse Server Directory.
+
Linked Edge Controllers makes it possible to call between different IC-EDGE Systems. The routing between IC-EDGE Systems are easily configured in the Edge Controller Directory.
  
 
==Prerequisites==
 
==Prerequisites==
 
===Software requirements===
 
===Software requirements===
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.
+
The [[Edge Controller]] must be a station in the [[:Category:Stations#Turbine_stations|Turbine family]] with software version 5.0.3.0 or higher.  
  
 
===License requirements===
 
===License requirements===
When using a Pulse server with ver. 4.7:
+
No license is required to use Edge Link.
* A [[Pulse Licensing|Pulse Enterprise License]] (Item no. 1009660002)
 
 
 
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.
 
  
 
==Supported features==
 
==Supported features==
Line 24: Line 19:
  
 
==Configuration==
 
==Configuration==
Pulse Trunk Routes must be configured to enable calls between different Pulse sites. A route consists of:
+
Edge Link Routes must be configured to enable calls between different Edge sites. A route consists of:
 
# Directory Number range (To - From) in the remote site
 
# Directory Number range (To - From) in the remote site
 
# Logical name for the route
 
# Logical name for the route
# IP address and SIP port of the remote Pulse Server (Pulse Server SIP port is normally 5060)
+
# IP address and SIP port of the remote Edge Controller (Edge Controller 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
 
# 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.
+
{{Note|Transit calls are not possible. There must be a direct route from the calling Edge site to the remote Edge site}}
  
  
To add a route on a Pulse Server, select '''Server Management''' > '''Server Configuration''' > '''Directory Settings'''
+
To add a route on an Edge Controller, select '''Edge Controller''' > '''System Configuration''' > '''Directory'''
 
<br>
 
<br>
[[File:Linked edge1.png|left|thumb|500px|Pulse route configuration]]
+
[[File:Linked edge1.png|left|thumb|500px|Edge Link route configuration]]
 
<br style="clear:both;" />
 
<br style="clear:both;" />
* '''Directory Start:''' First number in the remote Pulse system.  
+
* '''Number Start:''' First number in the remote IC-EDGE 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.  
+
* '''Number Stop:''' Last number in the remote IC-EDGE 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.
 
* '''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.
 
* '''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
+
* '''Host:''' IP-Address of remote Edge Controller
 
* '''Port:''' The SIP port used. Normally 5060.
 
* '''Port:''' The SIP port used. Normally 5060.
  
Line 76: Line 71:
  
  
  '''IMPORTANT INFO REGARDING MULTIPLE PULSE SYSTEMS ON ONE LAN IP SUBNET'''
+
  '''IMPORTANT INFO REGARDING MULTIPLE IC-EDGE 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.  
+
  Because of the Edge auto-detect and configuration, it is '''NOT''' recommended to run multiple IC-EDGE 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  
+
  If you still, despite our recommendations want to run multiple IC-EDGE Systems on the same LAN subnet, we strongly recommend that you  
 
   
 
   
   -Connect and set up Pulse system 1
+
   -Connect and set up IC-EDGE System 1
   -Disconnect Pulse system 1  
+
   -Disconnect IC-EDGE System 1  
   -Connect and set up Pulse system 2
+
   -Connect and set up IC-EDGE System 2
   -When done with all separate configuration, connect both Pulse systems.
+
   -When done with all separate configuration, connect both IC-EDGE Systems.
 
   
 
   
  If you are going to do configuration changes, please remember to disconnect the other Pulse system from the network.
+
  If you are going to do configuration changes, please remember to disconnect the other IC-EDGE System from the network.
  
 
==Limitations==
 
==Limitations==
* Pulse Server can have maximum of '''50 configured Pulse trunks'''.   
+
* Edge Controller can have maximum of '''50 configured Edge Links'''.   
* '''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.  
+
* '''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 Edge 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.
 
* '''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.  
+
* '''Group calls:''' It is not possible to do group calls from one Edge system to another.  
  
 
[[Category: IC-EDGE Configuration]]
 
[[Category: IC-EDGE Configuration]]

Revision as of 12:09, 16 September 2019

Edge-icon.jpg
Example of IC-EDGE Systems interconnected by Edge Link

Linked Edge Controllers makes it possible to call between different IC-EDGE Systems. The routing between IC-EDGE Systems are easily configured in the Edge Controller Directory.

Prerequisites

Software requirements

The Edge Controller must be a station in the Turbine family with software version 5.0.3.0 or higher.

License requirements

No license is required to use Edge Link.

Supported features

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

Configuration

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

  1. Directory Number range (To - From) in the remote site
  2. Logical name for the route
  3. IP address and SIP port of the remote Edge Controller (Edge Controller 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
Note icon Transit calls are not possible. There must be a direct route from the calling Edge site to the remote Edge site



To add a route on an Edge Controller, select Edge Controller > System Configuration > Directory

Edge Link route configuration


  • Number Start: First number in the remote IC-EDGE System.
  • Number Stop: Last number in the remote IC-EDGE 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 Edge Controller
  • Port: The SIP port used. Normally 5060.

Configuration example

IC-EDGE system 1
Name Saturn
Edge controller IP Address 192.168.1.10
Numberplan 40-80
IC-EDGE system 2
Name Venus
Edge controller IP Address 192.168.5.10
Numberplan 120-160


Lnked Edge controllers - Example



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

 -Connect and set up IC-EDGE System 1
 -Disconnect IC-EDGE System 1 
 -Connect and set up IC-EDGE System 2
 -When done with all separate configuration, connect both IC-EDGE Systems.

If you are going to do configuration changes, please remember to disconnect the other IC-EDGE System from the network.

Limitations

  • Edge Controller can have maximum of 50 configured Edge Links.
  • 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 Edge 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 Edge system to another.