Actions

Difference between revisions of "AlphaNet"

From Zenitel Wiki

(→‎Overview)
(→‎Create the ICX-AlphaCom nodes)
 
(195 intermediate revisions by 7 users not shown)
Line 1: Line 1:
−
=Overview=
+
{{AI}}
 +
[[File:AlphaNet Overview.PNG|thumb|500px]]
 +
 
 +
'''AlphaNet''' is Zenitel's internal networking technology made for critical communications. Up to 254 ICX-AlphaCom (or AlphaCom XE) servers can be interconnected in AlphaNet. One server can have up to 100 links to other servers.
 +
 
 +
Some of the highlighted features of AlphaNet are:
  
−
AlphaNet is STENTOFON's internal networking technology made for critical communications. Some of the highlighted features of AlphaNet are:
 
 
*Group and conference calls
 
*Group and conference calls
 
*VoIP bandwidth management
 
*VoIP bandwidth management
Line 8: Line 12:
 
*Backwards compatibility
 
*Backwards compatibility
 
*All features available over the network
 
*All features available over the network
−
*VoIP, digital and analogue infrastructure support
 
  
  
−
'''Group and conference calls'''
+
==AlphaNet Configuration - example==
 +
The following configuration is used in the examples in this article.
 +
[[File:AlphaNet Block.PNG|thumb|left|700px]]
 +
<br style="clear:both;" />
 +
 
 +
==Web settings==
 +
In each node you must:
 +
 
 +
*Set a unique IP address
 +
*Insert an AlphaNet license
 +
*Configure the firewall
 +
 
 +
===Setting IP address===
 +
[[File:AlphaNet IP.PNG|thumb|left|700px|Configure an IP address in each ICX-AlphaCom]]
 +
<br style="clear:both;" />
 +
 
 +
===Inserting AlphaNet license===
 +
Each ICX-AlphaCom node requires an [[Licenses for ICX-500 and ICX-AlphaCom Core|AlphaNet license ILI-AN2 or ILI-AN8]]. AlphaNet licenses can be stacked, and controls the number of simultaneous calls to and from a node.
 +
[[File:AlphaNet License.PNG|thumb|left|700px|Each ICX-AlphaCom node requires an AlphaNet license]]
 +
<br style="clear:both;" />
 +
 
 +
===Configure the firewall===
 +
The '''AlphaNet Data''' port (TCP port 50000)and the '''VoIP Audio''' ports (UDP ports 61000-62000) must be enabled for the Ethernet port used for AlphaNet:
 +
[[File:AlphaNet Firewall.PNG|thumb|left|700px]]
 +
<br style="clear:both;" />
 +
 
 +
== AlphaPro configuration ==
 +
===Create the ICX-AlphaCom nodes===
 +
Create a customer database and define the first ICX-AlphaCom node by clicking the + sign as highlighted below.
 +
[[File:AlphaNet Create.PNG|thumb|left|700px|Create a customer database]]
 +
<br style="clear:both;" />
 +
 
 +
 
 +
Fill in the fields as described below:
 +
* '''Names''': Give a descriptive name to the customer database (e.g. "City Hospital") and to the node (e.g. "A-Building").
 +
* '''Node Number''': Enter a unique node number (1 - 254), good practice to start with node 1 for the first server.
 +
* '''Type''': select the server type. Normally ICX (= ICX-AlphaCom).
 +
* '''Language''': This is the language to be used for display texts in stations.
 +
* '''Number of devices''': The number of IP devices you plan to use on this server. The "CCoIP Station" flag will be enabled on the number of stations selected. You can modify this settings later.
 +
* '''Create exchange database''': Normally checked
 +
* '''Connect to''': Enter the IP address of Eth0 and Eth1, and select which network interface to use for communication with other nodes.
 +
 
 +
[[File:AlphaNet Database.PNG|thumb|left|600px|Select which Ethernet interface to use for the AlphaNet feature by checking the '''AlphaNet''' flag]]
 +
<br style="clear:both;" />
 +
 
 +
 
 +
Add more nodes to the database by clicking the + sign as highlighted below.
 +
 
 +
Adding node 2 to the database:
 +
[[File:AlphaNet CreateN2.PNG|thumb|left|700px|Adding node 2 to the database]]
 +
<br style="clear:both;" />
 +
 
 +
 
 +
Adding node 3 to the database::
 +
[[File:AlphaNet CreateN3.PNG|thumb|left|700px|Adding node 3 to the database]]
 +
<br style="clear:both;" />
 +
 
 +
{{Note| In some cases it is not desired to configure all the exchanges in the AlphaNet from the same AlphaPro database. In that case you should add the remote exchange in the network, but uncheck the tick-off for "Create exchange database".}}
 +
 
 +
===Create AlphaNet routing===
 +
Routing must be specified from all nodes to all nodes. For each node:
 +
 
 +
*Click on [[Exchange_%26_System_(AlphaPro)#NetRouting|Exchange & System > Net Routing]] > Insert
 +
*Select the remote AlphaCom node from the list of unconfigured nodes that pops up
 +
 
 +
[[File:CreateRouting.png|thumb|left|800px]]
 +
<br style="clear:both;" />
 +
 
 +
If the Source Node is an AlphaCom XE7/20/26 and the Destination Node is an ICX-AlphaCom or AlphaCom XE1, enable “'''IP Only'''”
 +
 
 +
{{Note| In an AlphaNet of XE7/20/26 and ICX-AlphaCom or AlphaCom XE1, call recording should be enabled in the ICX-AlphaCom or AlphaCom XE1 node only.  If call recording is required in the XE7/20/26 node, the stations must be IP Stations.  This is due to the Voice Switching operation across AlphaNet not being compatible with the Recorder Interface.}}
 +
 
 +
====Transit Routing====
 +
In the case of Transit Routing, where the Remote nodes are connected via a Central Node, you need to direct the traffic via the Central Node.
 +
[[File:AlphaNet Transit routing.JPG|left|frame]]
 +
<br style="clear:both;" />
 +
 
 +
 
 +
===Dial plans===
 +
Calling from station A in one node to station B in another node can be achieved in different ways.
 +
[[File:DialPlans.png|thumb|left|750px|*) Prefix to node 1 and 2 are included after Factory Default (Directory numbers 54 and 55)]]
 +
<br style="clear:both;" />
 +
 
 +
[[File:DialPlansPrefix.png|thumb|left|750px]]
 +
<br style="clear:both;" />
 +
 
 +
[[File:DialPlansSemi.png|thumb|left|750px]]
 +
<br style="clear:both;" />
 +
 
 +
[[File:DialPlansGlobal.png|thumb|left|750px]]
 +
<br style="clear:both;" />
 +
 
 +
===Global Group Calls===
 +
A '''Global Group''' consists of one '''Local Group''' from each node
 +
[[File:GlobalGroup1.png|thumb|left|912px]]
 +
<br style="clear:both;" />
 +
 
 +
*Factory Default includes Global Group 1 to 10, Directory Numbers 9001 – 9010
 +
*Each Global Group can contain one local group call from each node
 +
 
 +
[[File:GlobalGroup2.png|thumb|left|677px]]
 +
<br style="clear:both;" />
 +
 
 +
Each node broadcasts its own global group membership to the other nodes after:
 +
 
 +
*AlphaPro Send operation
 +
*Restart of AlphaCom
 +
*Dialing service code 7879
 +
 
 +
In this way each node knows which global groups the other nodes are members of.
 +
 
 +
===Cluster node programming===
 +
====Defining Cluster Node====
 +
Cluster programming is an option to simplify programming and updating of numbers in AlphaNet when operating with integrated number series. To get access to the '''AlphaNet Visibility''' menu, the server must be assinged a ''Cluster Node Number'' in the '''Exchange & System''' window. The Cluster Node number can be any number between 1-255. Nodes with the same ''Cluster Node Number'' are members of the same cluster.
 +
 
 +
[[File:Cluster1.png|thumb|left|650px]]
 +
<br style="clear:both;" />
 +
 
 +
====Cluster Global====
 +
Setting Visibility = “Cluster Global” on a User in node 1...
 +
[[File:Cluster2.png|thumb|left|763px]]
 +
<br style="clear:both;" />
 +
 
 +
 
 +
...will automatically create a Global Number (feature 83) in node 2 (and all other nodes in the cluster)
 +
[[File:Cluster3.png|thumb|left|763px]]
 +
<br style="clear:both;" />
 +
 
 +
{{note|If the number already exists in the other cluster node(s), you will get a warning}}
  
−
AlphaNet has full group- and conference call capability. Each AlphaCom E has a built in multi-party conferencing unit, providing local mixing for group and conference calls. This local mixing allows AlphaCom E to only use a single VoIP channel when setting up a group or conference call between exchanges.
+
It is possible to create Global Numbers for many (or all) Users in one operation:
  
 +
*In '''Directory & Features''' select multiple users (feature 9) by click and shift + click.
 +
*Set AlphaNet Visibility = “Cluster Global”
 +
*Check “Apply to all Directory Numbers with this feature”
  
−
'''VoIP Bandwidth management'''
+
[[File:Cluster4.png|thumb|left|758px]]
 +
<br style="clear:both;" />
  
−
AlphaNet provides bandwidth management limiting the VoIP bandwidth to not take more capacity than provisioned. If a high priority call is set up when all VoIP channels are occupied, AlphaCom E will immediately release the call with the lowest priority allowing the high priority call to proceed.
+
{{note|If a number already exists in the other cluster node(s), it will be deleted without warning}}
  
 +
====Cluster Identical====
 +
Instead of creating the same local [[AlphaCom Feature List|feature]] in every node, do it once:
  
−
'''Priority handling of events and resources'''
+
*Set Visibility = “Cluster Identical” on a Feature in one node...
  
−
All calls and events that are sent between nodes are marked with priority. This allows the system to act upon the priority, presenting and handling the events and calls in the correct order.
+
[[File:Cluster5.png|thumb|left|760px]]
 +
<br style="clear:both;" />
  
  
−
'''Alternative routing'''
+
...and a copy will automatically be created in all other nodes in the cluster.
 +
[[File:Cluster6.png|thumb|left|760px]]
 +
<br style="clear:both;" />
  
−
Alternative routing of calls allows call completion even when the primary AlphaNet route is down. As a secondary route AlphaCom E can either use its secondary IP interface or it can put the call over a traditional interface such as an analouge or digital line.
+
<br>
  
 +
==License requirements==
 +
Every node requires an AlphaNet license. The license controls the number of simultaneous calls to and from an AlphaCom. There are two types of AlphaNet license:
  
−
'''Backwards compatibility'''
+
*Dynamic license: Pool of VoIP channels - automatically allocated when needed
  
−
AlphaCom E provides 100% backwards compatibility between traditional AlphaNet technologies and new VoIP AlphaNet. The backwards compatibility allows mixing of the AlphaCom E nodes working over IP with current nodes so configuration can be maintained
+
[[File:DynamicLicense.png|thumb|left|750px]]
−
'''Note:''' AlphaCom E has two RS232 ports which can be used for AlphaNet. If more ports are needed, an Ethernet to use RS232 converter must be used.
+
<br style="clear:both;" />
  
 +
*Static license: VoIP channels must be fixed towards specific node(s)
  
−
'''All features available over the network'''
+
[[File:StaticLicense.png|thumb|left|500px]]
 +
<br style="clear:both;" />
  
−
Consistent features and services across the organization regardless of location, providing improved user friendliness. AlphaCom E provides all current AlphaNet features available today with the enhanced features of connection to LAN/WAN.
+
See also [[Licenses#AlphaNet_license|AlphaNet License]]
  
 +
===2-line static license - details===
 +
An AlphaCom server with a 2-line static license allows maximum two simultaneous AlphaNet calls.
  
−
'''VoIP, digital and analouge infrastructure support'''
+
Static Licenses are typically used in:
  
−
AlphaNet works over any infrastructure being IP, digital or analogue.
+
*Low traffic 2-node system
 +
*AlphaNet with multiple nodes were “end nodes” needs to call "central node” only
  
−
=VoIP AlphaNet Configuration=
+
When using AlphaNet '''Static''' License, one have to configure fixed Audio Connections between the AlphaCom servers. This is done from AlphaPro, [[Exchange_%26_System_(AlphaPro)#NetAudio|Exchange & System > NetAudio]], where you specify that a VoIP channel in the "Source" exchange has a static (fixed) connection to a VoIP channel in the "Destination" exchange.
  
−
==Overview==
+
Each VoIP channel is identified by a virtual physical number:
  
−
The following steps are required for configuration of AlphaNet:
+
*VoIP Channel 1 = Physical Number 605
−
*Insert AlphaNet license if VoIP AlphaNet should be used
+
*VoIP Channel 2 = Physical Number 606
−
*Create all the exchanges in the AlphaNet
+
*..
−
*Create AlphaNet data routing
+
*..
−
*Create AlphaNet audio routes
+
*VoIP Channel 30 = Physical Number 634
−
*Upgrade the directory
 
  
 +
====Example - Low traffic 2-node system====
 +
Two AlphaCom nodes, both with 2-line Static License
 +
[[File:2line1.png|thumb|left|481px|Configuration example: Two nodes, both with 2-line Static License]]
 +
<br style="clear:both;" />
  
−
==Insert AlphaNet license==
+
<br>
 +
'''NetAudio''' configuration:
 +
[[File:2line3.png|thumb|left|887px|Configuration of 1st AlphaNet connection using VoIP channel (605). Insert a second AlphaNet connection using VoIP channel (606)]]
 +
<br style="clear:both;" />
 +
<br>
  
−
This must be done if VoIP AlphaNet should be used.
+
====Example - AlphaNet with multiple nodes, “end nodes” needs to call central node” only====
 +
[[File:2line2.png|thumb|left|918px|Each "end node" has a Static 2-line license. The central node has an 8-line Dynamic license]]
 +
<br style="clear:both;" />
  
 +
<br>
 +
'''NetAudio''' configuration:
  
−
==Create all the exchanges in the AlphaNet==
+
*"NetAudio" must be configured in all "End nodes"
 +
*No configuration of "NetAudio" required in the Central node
  
−
***Information about creating new network and exchange(s) is coming soon
+
[[File:2line4.png|thumb|left|887px|NetAudio configuration in an "End node". A VoIP channel (here 605) is linked to a "Dynamic license" in the Central node]]
−
'''Note:''' In some cases it is not desired to program all the exchanges in the AlphaNet in the same AlphaPro database. In this case you should add the exchange in the network, but uncheck the tick-off for "AlphaNet Adm. Here".
+
<br style="clear:both;" />
  
 +
<br>
  
−
==Create AlphaNet data routing==
 
  
−
'''AlphaNet link between AlphaCom E exchanges:'''
+
==VoIP Bandwidth==
−
*Select the AlphaCom E exchange
+
AlphaNet provides bandwidth management limiting the VoIP bandwidth to not take more capacity than provisioned.
−
*Click on the "Exchange & System" icon
 
−
*Select "Net Routing"
 
−
*Press "Insert"
 
−
*Select the remote AlphaCom node for the AlphaNet
 
−
*Configure primary route:
 
−
*Select "Data on IP" as [[AlphaNet_Data_Protocol|ACDP]] link
 
−
*Select node number for both Data and Audio
 
−
*Check "Audio on IP" if a VoIP audio link shall be used
 
−
*Option: Configure an alternative route
 
−
*The preferred codec should be set to "Best Available"
 
−
*Press "OK"
 
  
−
'''AlphaNet link to traditional AlphaCom exchanges:'''
+
*Each active call uses approx. 100 kbps
−
*Select the AlphaCom exchange
+
*Maximum bandwidth usage: Number of simultaneous calls x 100 kbps
−
*Click on the "Exchange & System" icon
+
**Example: System with16 Dynamic Lines
−
*Select Serial Ports
+
**Max. possible bandwidth usage is 16 x 100 kbps = 1.6 Mbps
−
*Select a free [[AlphaNet_Data_Protocol|ACDP]] link
 
−
*Press "Change"
 
−
*Enable the port and select the serial port for AlphaNet
 
−
*Select link type = Stentofon link layer - AlphaNet
 
−
*Press "OK" and close serial port window
 
−
*Select "Net Routing"
 
−
*Press "Insert"
 
−
*Select the remote AlphaCom node for the AlphaNet
 
−
*Configure primary route:
 
−
*Select [[AlphaNet_Data_Protocol|ACDP]] link that was configured for AlphaNet
 
−
*Select node number for both the Data and Audio
 
−
*Do ''''NOT'''' check "Audio on IP"
 
−
*Option: Configure an alternative route
 
−
*Press "OK"
 
−
'''Note:''' For each AlphaCom it is required to configure AlphaNet links to the AlphaComs it shall be able to communicate to.
 
  
−
==Create AlphaNet audio routes==
+
[[File:Bandwidth.png|thumb|left|500px|Exact bandwidth figures]]
 +
<br style="clear:both;" />
  
−
Create VoIP audio channels:
+
==Additional information==
−
*Select the AlphaCom E exchange
+
===Priority handling of events and resources===
−
*Click on the "Exchange & System" icon
+
All calls and events that are sent between nodes are marked with priority. This allows the system to act upon the priority, presenting and handling the events and calls in the correct order.
−
*Press "Net Audio"
+
If a high priority call is set up when all VoIP channels are occupied, AlphaCom will immediately release the call with the lowest priority allowing the high priority call to proceed.
−
*Press "Insert"
 
−
*Select destination node and press "Select"
 
−
*Enter the parameters as shown (Image coming soon)
 
−
*Enter the parameters as shown
 
−
*Confirm by "OK"
 
−
Repeat the insert operation for the number of wanted VoIP audio channels. <br/>
 
−
'''Note:''' By selecting dynamic route as destination node, the audio channel can dynamically be used to any VoIP AlphaNet link.<br/>
 
−
'''Note:''' The physical numbers 605 to 635 are logical numbers inside the AlphaCom E, reserved for VoIP AlphaNet and SIP
 
−
*Press "Close" to close the AlphaNet Audio Connections window
 
−
*Press "Close to close the Exchange Information window
 
  
−
Create circut switched audio channels:
+
===Alternative routing===
−
*Select the AlphaCom E exchange
+
Alternative routing of calls allows call completion even when the primary AlphaNet route is down.
−
*Click on the "Exchange & System" icon
+
{{note|Alternative routing in mixed environments (AMC9 and AMC-IP) is not supported!}}
−
*Press "Net Audio"
 
−
*Press "Insert"
 
−
*Select destination node and press "Select"
 
−
*Enter the physical numbers in the "Source" and "Destination" exchange as shown (Image coming soon)
 
−
*The module, position and line numbers are automatically defined when physical number is entered.
 
−
*Confirm by "OK"
 
−
*Repeat "Insert" for the number of wanted audio channels
 
  
−
==Cluster node programming==
+
===Backwards compatibility===
 +
AlphaCom provides 100% backwards compatibility between traditional AlphaNet technologies and new VoIP AlphaNet. The backwards compatibility allows mixing of the AlphaCom nodes working over IP with current nodes. This makes the  configuration of the system very easy, allowing quick and precise maintenance.
  
−
Cluster programming is a option to simplify programming and updating of numbers in AlphaNet when operating with integrated number series. To get access to the '''AlphaNet Visibility''' menu, the exchange has to be given a ''Cluster Node Number'' in the '''Exchange & System''' window. Nodes with the same ''Cluster Node Number'' (1-255) are members of the same cluster.
+
==Troubleshooting==
 +
In AlphaWeb, '''System Monitoring''' > '''AlphaNet''', some information about the AlphaNet status is listed.
  
−
*Go to '''User & Stations''' or to '''Directory & Features''' and type new directory number and name, and set the ''AlphaNet Visibility'' to Cluster Global, Cluster Local or Cluster Identical
+
[[File:AlphaNetTroubleshooting.png|thumb|left|796px]]
−
*'''Cluster Global'''<br\> The directory number and name will immediately be copied to the other exchanges in the cluster node as a [[Call remote station feature|global number]]. If the number exists from before in any of the other exchanges, it will be deleted. ''AlphaNet Visibility'' will be set to ''Cluster Automatic'' in the other exchanges.<br\>'''Modify'''<br\>When modifying the number or name of an existing global user, you must do the modification in the exchange were the user is physically connected, i.e. were the visibility is set to ''Cluster Global''.
+
<br style="clear:both;" />
−
*'''Deleting''':<br\>When deleting a directory number that has visibility Cluster Global or Cluster Automatic, it will automatically be deleted from all cluster nodes.
 
−
*'''Cluster Local'''<br\>The directory number will not be copied to the other exchanges in the cluster node.
 
−
*'''Cluster Identical'''<br\>The directory number and name will be copied to the other exchanges. The feature number will be identical in all exchanges, i.e. the feature will remain local in each exchange, but with the same number and name. ''AlphaNet Visibility'' will be set to ''Cluster Identical'' in all exchanges.
 
  
−
==Update the directory in each exchange==
+
*If the node is listed: Routing information in AlphaPro is correct. If not, check [[Exchange_%26_System_(AlphaPro)#NetRouting|NetRouting]] in AlphaPro, then do a Send All followed by a reset.
  
−
Create directory number for AlphaNet Area Codes:
+
*Press '''Ping Test''' to check '''Status''' and '''Ping Time''':  
−
*Click on the "Directory & Features" icon
+
**'''Down''', and no answer to Ping: No TCP/IP communication to remote node. Check network, cables, switches etc...
−
*Press "Insert"
+
**'''Down''', but Ping time is returned: IP communication is OK, but not AlphaNet. Most likely blocking of TCP port 50000 in internal or external firewall. Check if "AlphaNet" is enabled in Filters.
−
*Select ''Area Code for AlphaNet - 81'' from the "Feature" menu
+
**'''Up''': AlphaNet communication is OK
−
*Enter node number for the exchange owning the area code
 
−
*Enter the directory number you want to use as area code
 
−
*Select ''Cluster Identical'' from the "AlphaNet Visibility" menu
 
  
−
Make AlphaCom stations visible in the AlphaNet cluster
+
'''Note:''' The node with the lowest node number is TCP-Client, the highest is TCP-Server.
−
*Click on the "Users & Stations" icon
 
−
*Select the station to have global number
 
−
*Select ''Cluster Global'' from the AlphaNet
 
−
*Confirm by "OK"
 
−
*''Cluster Global'' can also be set from the "Directory & Feature" menu. All stations can then be set in one operation.
 
  
−
Create directory number for Global Numbers for AlphaNet:
+
==Related articles==
−
*Click on the "Directory & Features" icon
 
−
*Press "Insert"
 
−
*Select ''Global Number for AlphaNet - 83'' from the "Feature" menu
 
−
*Enter node number for the exchange
 
−
*Enter the directory number you want to use as global number
 
−
*Confirm by "OK"
 
  
 +
*[[SIP_trunk_node_-_configuration]]
 +
*[[Rebuild_global_group_in_AlphaNet_feature]]
 +
*[[Global_Group_Call_in_AlphaNet_feature]]
 +
*[[Monitoring: AlphaNet]]
  
 
[[Category:AlphaNet]]
 
[[Category:AlphaNet]]
 +
[[Category: Network]]
 +
[[Category: ICX-AlphaCom features]]
 +
[[Category: AlphaCom features]]

Latest revision as of 16:02, 31 July 2024

AI.png
AlphaNet Overview.PNG

AlphaNet is Zenitel's internal networking technology made for critical communications. Up to 254 ICX-AlphaCom (or AlphaCom XE) servers can be interconnected in AlphaNet. One server can have up to 100 links to other servers.

Some of the highlighted features of AlphaNet are:

  • Group and conference calls
  • VoIP bandwidth management
  • Priority handling of events and resources
  • Alternative routing
  • Backwards compatibility
  • All features available over the network


AlphaNet Configuration - example

The following configuration is used in the examples in this article.

AlphaNet Block.PNG


Web settings

In each node you must:

  • Set a unique IP address
  • Insert an AlphaNet license
  • Configure the firewall

Setting IP address

Configure an IP address in each ICX-AlphaCom


Inserting AlphaNet license

Each ICX-AlphaCom node requires an AlphaNet license ILI-AN2 or ILI-AN8. AlphaNet licenses can be stacked, and controls the number of simultaneous calls to and from a node.

Each ICX-AlphaCom node requires an AlphaNet license


Configure the firewall

The AlphaNet Data port (TCP port 50000)and the VoIP Audio ports (UDP ports 61000-62000) must be enabled for the Ethernet port used for AlphaNet:

AlphaNet Firewall.PNG


AlphaPro configuration

Create the ICX-AlphaCom nodes

Create a customer database and define the first ICX-AlphaCom node by clicking the + sign as highlighted below.

Create a customer database



Fill in the fields as described below:

  • Names: Give a descriptive name to the customer database (e.g. "City Hospital") and to the node (e.g. "A-Building").
  • Node Number: Enter a unique node number (1 - 254), good practice to start with node 1 for the first server.
  • Type: select the server type. Normally ICX (= ICX-AlphaCom).
  • Language: This is the language to be used for display texts in stations.
  • Number of devices: The number of IP devices you plan to use on this server. The "CCoIP Station" flag will be enabled on the number of stations selected. You can modify this settings later.
  • Create exchange database: Normally checked
  • Connect to: Enter the IP address of Eth0 and Eth1, and select which network interface to use for communication with other nodes.
Select which Ethernet interface to use for the AlphaNet feature by checking the AlphaNet flag



Add more nodes to the database by clicking the + sign as highlighted below.

Adding node 2 to the database:

Adding node 2 to the database



Adding node 3 to the database::

Adding node 3 to the database


Note icon In some cases it is not desired to configure all the exchanges in the AlphaNet from the same AlphaPro database. In that case you should add the remote exchange in the network, but uncheck the tick-off for "Create exchange database".


Create AlphaNet routing

Routing must be specified from all nodes to all nodes. For each node:

CreateRouting.png


If the Source Node is an AlphaCom XE7/20/26 and the Destination Node is an ICX-AlphaCom or AlphaCom XE1, enable “IP Only”

Note icon In an AlphaNet of XE7/20/26 and ICX-AlphaCom or AlphaCom XE1, call recording should be enabled in the ICX-AlphaCom or AlphaCom XE1 node only. If call recording is required in the XE7/20/26 node, the stations must be IP Stations. This is due to the Voice Switching operation across AlphaNet not being compatible with the Recorder Interface.


Transit Routing

In the case of Transit Routing, where the Remote nodes are connected via a Central Node, you need to direct the traffic via the Central Node.

AlphaNet Transit routing.JPG



Dial plans

Calling from station A in one node to station B in another node can be achieved in different ways.

*) Prefix to node 1 and 2 are included after Factory Default (Directory numbers 54 and 55)


DialPlansPrefix.png


DialPlansSemi.png


DialPlansGlobal.png


Global Group Calls

A Global Group consists of one Local Group from each node

GlobalGroup1.png


  • Factory Default includes Global Group 1 to 10, Directory Numbers 9001 – 9010
  • Each Global Group can contain one local group call from each node
GlobalGroup2.png


Each node broadcasts its own global group membership to the other nodes after:

  • AlphaPro Send operation
  • Restart of AlphaCom
  • Dialing service code 7879

In this way each node knows which global groups the other nodes are members of.

Cluster node programming

Defining Cluster Node

Cluster programming is an option to simplify programming and updating of numbers in AlphaNet when operating with integrated number series. To get access to the AlphaNet Visibility menu, the server must be assinged a Cluster Node Number in the Exchange & System window. The Cluster Node number can be any number between 1-255. Nodes with the same Cluster Node Number are members of the same cluster.

Cluster1.png


Cluster Global

Setting Visibility = “Cluster Global” on a User in node 1...

Cluster2.png



...will automatically create a Global Number (feature 83) in node 2 (and all other nodes in the cluster)

Cluster3.png


Note icon If the number already exists in the other cluster node(s), you will get a warning


It is possible to create Global Numbers for many (or all) Users in one operation:

  • In Directory & Features select multiple users (feature 9) by click and shift + click.
  • Set AlphaNet Visibility = “Cluster Global”
  • Check “Apply to all Directory Numbers with this feature”
Cluster4.png


Note icon If a number already exists in the other cluster node(s), it will be deleted without warning


Cluster Identical

Instead of creating the same local feature in every node, do it once:

  • Set Visibility = “Cluster Identical” on a Feature in one node...
Cluster5.png



...and a copy will automatically be created in all other nodes in the cluster.

Cluster6.png



License requirements

Every node requires an AlphaNet license. The license controls the number of simultaneous calls to and from an AlphaCom. There are two types of AlphaNet license:

  • Dynamic license: Pool of VoIP channels - automatically allocated when needed
DynamicLicense.png


  • Static license: VoIP channels must be fixed towards specific node(s)
StaticLicense.png


See also AlphaNet License

2-line static license - details

An AlphaCom server with a 2-line static license allows maximum two simultaneous AlphaNet calls.

Static Licenses are typically used in:

  • Low traffic 2-node system
  • AlphaNet with multiple nodes were “end nodes” needs to call "central node” only

When using AlphaNet Static License, one have to configure fixed Audio Connections between the AlphaCom servers. This is done from AlphaPro, Exchange & System > NetAudio, where you specify that a VoIP channel in the "Source" exchange has a static (fixed) connection to a VoIP channel in the "Destination" exchange.

Each VoIP channel is identified by a virtual physical number:

  • VoIP Channel 1 = Physical Number 605
  • VoIP Channel 2 = Physical Number 606
  • ..
  • ..
  • VoIP Channel 30 = Physical Number 634

Example - Low traffic 2-node system

Two AlphaCom nodes, both with 2-line Static License

Configuration example: Two nodes, both with 2-line Static License



NetAudio configuration:

Configuration of 1st AlphaNet connection using VoIP channel (605). Insert a second AlphaNet connection using VoIP channel (606)



Example - AlphaNet with multiple nodes, “end nodes” needs to call central node” only

Each "end node" has a Static 2-line license. The central node has an 8-line Dynamic license



NetAudio configuration:

  • "NetAudio" must be configured in all "End nodes"
  • No configuration of "NetAudio" required in the Central node
NetAudio configuration in an "End node". A VoIP channel (here 605) is linked to a "Dynamic license" in the Central node




VoIP Bandwidth

AlphaNet provides bandwidth management limiting the VoIP bandwidth to not take more capacity than provisioned.

  • Each active call uses approx. 100 kbps
  • Maximum bandwidth usage: Number of simultaneous calls x 100 kbps
    • Example: System with16 Dynamic Lines
    • Max. possible bandwidth usage is 16 x 100 kbps = 1.6 Mbps
Exact bandwidth figures


Additional information

Priority handling of events and resources

All calls and events that are sent between nodes are marked with priority. This allows the system to act upon the priority, presenting and handling the events and calls in the correct order. If a high priority call is set up when all VoIP channels are occupied, AlphaCom will immediately release the call with the lowest priority allowing the high priority call to proceed.

Alternative routing

Alternative routing of calls allows call completion even when the primary AlphaNet route is down.

Note icon Alternative routing in mixed environments (AMC9 and AMC-IP) is not supported!


Backwards compatibility

AlphaCom provides 100% backwards compatibility between traditional AlphaNet technologies and new VoIP AlphaNet. The backwards compatibility allows mixing of the AlphaCom nodes working over IP with current nodes. This makes the configuration of the system very easy, allowing quick and precise maintenance.

Troubleshooting

In AlphaWeb, System Monitoring > AlphaNet, some information about the AlphaNet status is listed.

AlphaNetTroubleshooting.png


  • If the node is listed: Routing information in AlphaPro is correct. If not, check NetRouting in AlphaPro, then do a Send All followed by a reset.
  • Press Ping Test to check Status and Ping Time:
    • Down, and no answer to Ping: No TCP/IP communication to remote node. Check network, cables, switches etc...
    • Down, but Ping time is returned: IP communication is OK, but not AlphaNet. Most likely blocking of TCP port 50000 in internal or external firewall. Check if "AlphaNet" is enabled in Filters.
    • Up: AlphaNet communication is OK

Note: The node with the lowest node number is TCP-Client, the highest is TCP-Server.

Related articles

Retrieved from "https://wiki.zenitel.com/w/index.php?title=AlphaNet&oldid=237285"