Difference between revisions of "Linked Edge Controllers"
From Zenitel Wiki
(Created page with "{{E}} thumb|500px|Example of Pulse Systems interconnected by Pulse Trunking Pulse Trunking makes it possible to call between different Pulse systems....") |
(→Limitations) |
||
| (9 intermediate revisions by 3 users not shown) | |||
| Line 1: | Line 1: | ||
{{E}} | {{E}} | ||
| − | [[File: | + | [[File:Edge Link.png|thumb|600px|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== | ==Prerequisites== | ||
| − | === | + | ===Firmware and Hardware Requirements=== |
| − | + | In each IC-EDGE system one of the intercom stations must be set as the "[[Edge Controller]]". The Edge Controller is acting as a server for the other intercom stations in the system. Most Zenitel IP devices can act as an Edge Controller, see [[Edge Controller|full list here]]. | |
| − | + | Minimum firmware version on the Edge Controller is version 5.0.3.0. | |
| − | |||
| − | |||
| − | + | ===License Requirements=== | |
| − | * | + | No license is required to use Edge Link. |
| − | * | + | |
| + | ===Network Port Requirements=== | ||
| + | The following ports must be open in the IP network: | ||
| + | * UDP port 5060 for SIP | ||
| + | * UDP port range 61000-61250 for audio | ||
| + | |||
| + | If system includes TCIV and video calls then the ephemeral UDP port range 32768-60999 must be open too. | ||
==Supported features== | ==Supported features== | ||
| Line 24: | Line 28: | ||
==Configuration== | ==Configuration== | ||
| − | + | 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 | + | # 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 | + | {{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 | + | To add a route on an Edge Controller, select '''Edge Controller''' > '''System Configuration''' > '''Directory''' |
<br> | <br> | ||
| − | [[File: | + | [[File:Linked edge1.png|left|thumb|500px|Edge Link route configuration]] |
<br style="clear:both;" /> | <br style="clear:both;" /> | ||
| − | * ''' | + | * '''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. | * '''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 | + | * '''Host:''' IP-Address of remote Edge Controller |
* '''Port:''' The SIP port used. Normally 5060. | * '''Port:''' The SIP port used. Normally 5060. | ||
| Line 47: | Line 51: | ||
{| class="wikitable" style="float:left; margin-left: 10px;" | {| class="wikitable" style="float:left; margin-left: 10px;" | ||
| − | |+ | + | |+IC-EDGE system 1 |
|- | |- | ||
|'''Name''' | |'''Name''' | ||
|Saturn | |Saturn | ||
|- | |- | ||
| − | |''' | + | |'''Edge controller IP Address''' |
|192.168.1.10 | |192.168.1.10 | ||
|- | |- | ||
| Line 60: | Line 64: | ||
{| class="wikitable" style="float:left; margin-left: 10px;" | {| class="wikitable" style="float:left; margin-left: 10px;" | ||
| − | |+ | + | |+IC-EDGE system 2 |
|- | |- | ||
|'''Name''' | |'''Name''' | ||
|Venus | |Venus | ||
|- | |- | ||
| − | |''' | + | |'''Edge controller IP Address''' |
|192.168.5.10 | |192.168.5.10 | ||
|- | |- | ||
| Line 72: | Line 76: | ||
|} | |} | ||
<br style="clear:both;" /> | <br style="clear:both;" /> | ||
| − | [[File: | + | [[File:EdgeLinkExample.png|left|thumb|1000px|Lnked Edge controllers - Example]] |
<br style="clear:both;" /> | <br style="clear:both;" /> | ||
| − | '''IMPORTANT INFO REGARDING MULTIPLE | + | '''IMPORTANT INFO REGARDING MULTIPLE IC-EDGE SYSTEMS ON ONE LAN IP SUBNET''' |
| − | Because of the | + | 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 | + | 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 | + | -Connect and set up IC-EDGE System 1 |
| − | -Disconnect | + | -Disconnect IC-EDGE System 1 |
| − | -Connect and set up | + | -Connect and set up IC-EDGE System 2 |
| − | -When done with all separate configuration, connect both | + | -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 | + | If you are going to do configuration changes, please remember to disconnect the other IC-EDGE System from the network. |
==Limitations== | ==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 | + | * '''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 | + | * '''Group calls:''' It is not possible to do group calls from one Edge system to another. |
[[Category: IC-EDGE Configuration]] | [[Category: IC-EDGE Configuration]] | ||
| + | [[Category: Network]] | ||
Latest revision as of 10:32, 2 June 2022
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.
Contents
Prerequisites
Firmware and Hardware Requirements
In each IC-EDGE system one of the intercom stations must be set as the "Edge Controller". The Edge Controller is acting as a server for the other intercom stations in the system. Most Zenitel IP devices can act as an Edge Controller, see full list here.
Minimum firmware version on the Edge Controller is version 5.0.3.0.
License Requirements
No license is required to use Edge Link.
Network Port Requirements
The following ports must be open in the IP network:
- UDP port 5060 for SIP
- UDP port range 61000-61250 for audio
If system includes TCIV and video calls then the ephemeral UDP port range 32768-60999 must be open too.
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:
- Directory Number range (To - From) in the remote site
- Logical name for the route
- 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
|
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
- 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
| Name | Saturn |
| Edge controller IP Address | 192.168.1.10 |
| Numberplan | 40-80 |
| Name | Venus |
| Edge controller IP Address | 192.168.5.10 |
| Numberplan | 120-160 |
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.