AEQ BC2000D Series User manual

AEQ Audio Over IP
Routing System
IP-based multi-channel audio network
•ARENA Console / BC2000D Matriz: BC2214 & BC2224 boards.
•FORUM - GRAND FORUM Console: FR14 board.
•CAPITOL IP Console.
•NETBOX 32 AD Audio Interface.
•NETBOX 8 AD Audio Interface.
•NETBOX 4 MH Audio Interface.
•NETBOX DSP Router.
•PHOENIX VENUS V3 Audiocodec.
•SYSTEL IP 16 VoIP ON AIR Telephone System.
•OLYMPIA 3 Commentary unit.
•Dante Virtual Soundcard.
USER´S MANUAL
ED. 06/19
V. 1.1 - 21/06/2019
Software Versions: Dante Controller 4.0.6.5 or higher
Dante Virtual Soundcard 4.0.3.1 or higher
Dante Firmware Update Manager 3.10.2.4 or higher

AEQ Audio Over IP
Routing System
2
CONTENTS
1. INTRODUCTION.......................................................................................................................6
1.1. Fields of application of the product....................................................................................6
1.2. Description of the devices covered by this manual............................................................6
1.2.1. ARENA Console / BC2000D Matrix. BC2214 and BC2224 boards........................6
1.2.2. FORUM - GRAND FORUM console. FR14 board..................................................7
1.2.3. CAPITOL IP Console..............................................................................................7
1.2.4. NETBOX 32 AD Audio interface.............................................................................7
1.2.5. NETBOX 8 AD Audio interface...............................................................................7
1.2.6. NETBOX 4 MH Audio interface...............................................................................7
1.2.7. NETBOX DSP Router.............................................................................................8
1.2.8. PHOENIX VENUS V3 Audiocodec.........................................................................8
1.2.9. OLYMPIA 3 Commentary unit.................................................................................8
1.2.10. SYSTEL IP 16 VoIP ON AIR Telephone System. ................................................8
1.2.11. "Dante Virtual Soundcard". ...................................................................................8
1.2.12. Control Software "Dante Controller". ....................................................................8
1.3. General Features...............................................................................................................9
1.4. Operation of the AEQ AoIP system based on DANTE......................................................9
1.4.1. Discovery and auto-configuration. ..........................................................................9
1.4.2. Differentiation between input and output channels...............................................10
1.4.3. Device Names and Channel Labels......................................................................10
1.4.4. Routing Audio........................................................................................................11
1.4.5. Clock Synchronization. .........................................................................................14
1.4.6. Latency..................................................................................................................15
1.4.7. Device Lock...........................................................................................................15
1.4.8. Dante Control and Monitoring...............................................................................18
2. PHYSICAL DESCRIPTION OF THE UNITS. .........................................................................19
2.1. BC2214 and BC2224 modules description......................................................................19
2.1.1. Front panel description. ........................................................................................19
2.2. FR14 module description.................................................................................................19
2.2.1. Front panel description. ........................................................................................19
2.3. CAPITOL IP BOARD module description........................................................................20
2.3.1. Back panel description..........................................................................................20
2.4. NETBOX 32 AD interface description..............................................................................20
2.4.1. Front panel description. ........................................................................................20
2.5. NETBOX 8 AD interface description................................................................................21
2.5.1. Front panel description. ........................................................................................21
2.6. NETBOX 4 MH interface description. ..............................................................................21
2.6.1. Front panel description. ........................................................................................21
2.7. NETBOX 32 AD router description. .................................................................................22
2.7.1. Front panel description. ........................................................................................22
2.8. PHOENIX VENUS V3 audiocodec description................................................................22
2.8.1. Front panel description. ........................................................................................22
2.9. SYSTEL IP 16 VoIP ON AIR Telephone System. ...........................................................23
2.9.1. Front panel description. ........................................................................................23
2.10. OLYMPIA 3 commentary unit description......................................................................23
2.10.1. Back panel description........................................................................................23
3. BRIEF GUIDE TO SYSTEM INSTALLATION........................................................................24
3.1. Control elements..............................................................................................................24
3.1.1. PC for RTC and monitoring...................................................................................24
3.1.1.1. Applications installation...........................................................................24
3.2. Boards installation in mixing consoles and routers..........................................................24
3.2.1. Installation of BC2214/BC2224 boards in an ARENA console or BC2000D router ....24
3.2.2. Installation of FR14 boards into a FORUM o GRAND FORUM console..............25
3.2.3. Installation of the CAPITOL IP BOARD on a CAPITOL IP console......................25
3.3. Installation of a DANTE network with AEQ mixing consoles and NETBOX....................25
3.3.1. AEQ Audio over IP System for two digital studios and a Central Control.............25

AEQ Audio Over IP
Routing System
3
3.3.1.1. Installation...............................................................................................26
3.3.1.2. Turning ON..............................................................................................26
3.3.1.3. Monitoring audio and creating routes......................................................26
3.3.1.4. Optimization. ...........................................................................................26
3.3.2. AEQ Audio over IP system for medium to large sized stations. ...........................27
3.3.3. AEQ Audio over IP system for medium to large sized stations based on TITAN /
BC 2000 D TDM Matrix.........................................................................................28
4. "DANTE CONTROLLER": REAL-TIME OPERATION SOFTWARE. ....................................30
4.1. "Dante Controller" Description.........................................................................................30
4.2. Minimum System Requirements......................................................................................30
4.3. Installing "Dante Controller".............................................................................................31
4.3.1. Downloading "Dante Controller". ..........................................................................31
4.3.2. Installing "Dante Controller" on Windows. ............................................................31
4.3.3. Updating "Dante Controller" on Windows.............................................................31
4.3.4. Uninstalling "Dante Controller" on Windows.........................................................32
4.4. Where to find the "Dante Controller" application? ...........................................................32
4.5. Configuring "Dante Controller".........................................................................................32
4.6. Using "Dante Controller"..................................................................................................37
4.7. Using "Dante Controller": "Network View". ......................................................................37
4.7.1. "Network View" Menu Bar.....................................................................................38
4.7.2. "Network View" Tool Bar.......................................................................................38
4.7.3. "Network View" Status Bar....................................................................................39
4.7.4. "Network View" Tabs.............................................................................................39
4.7.4.1. "Routing". ................................................................................................39
4.7.4.2. "Device Info" (status of the device).........................................................46
4.7.4.3. "Clock Status".........................................................................................46
4.7.4.4. "Network Status". ....................................................................................56
4.7.4.5. "Events"...................................................................................................57
4.7.5. Automatic Notification of Device Errors. ...............................................................59
4.8. Using "Dante Controller": "Device View"..........................................................................59
4.8.1. "Device View" Menu Bar.......................................................................................61
4.8.2. "Device View" Tool Bar.........................................................................................61
4.8.3. "Device View" Tabs...............................................................................................62
4.8.3.1. "Receive".................................................................................................62
4.8.3.2. "Transmit"................................................................................................65
4.8.3.3. "Status"....................................................................................................66
4.8.3.4. "Latency".................................................................................................67
4.8.3.5. "Device Config". ......................................................................................69
4.8.3.6. "Network Config".....................................................................................72
4.8.3.7. "AES67 Config".......................................................................................74
4.9. Using "Dante Controller": Multicast Transmit Flow Configuration. ..................................75
4.10. Using "Dante Controller" with "Dante Domain Manager"...............................................77
4.10.1. Viewing Domains in "Dante Controller"...............................................................77
4.10.2. Virtual Devices....................................................................................................78
4.10.3. Legacy Devices...................................................................................................79
4.10.4. Domain Credentials. ...........................................................................................79
4.11. Presets...........................................................................................................................80
4.11.1. About Device Roles. ...........................................................................................80
4.11.2. Saving Presets....................................................................................................80
4.11.3. Applying Presets.................................................................................................81
5. CONTROL TERMINAL. "DANTE VIRTUAL SOUNDCARD".................................................85
5.1. Installing the "Dante Virtual Soundcard"..........................................................................86
5.2. Starting the "Dante Virtual Soundcard" Control Panel.....................................................87
5.3. Obtaining a "Dante Virtual Soundcard" License..............................................................87
5.4. Configuring "Dante Virtual Soundcard"............................................................................88
5.4.1. Settings available in "Dante Controller"................................................................88
5.4.2. "Settings" Tab in "Dante Virtual Soundcard".........................................................89
5.4.3. "Licensing" Tab in "Dante Virtual Soundcard". .....................................................92

AEQ Audio Over IP
Routing System
4
5.4.4. "Device Lock" Tab in "Dante Virtual Soundcard"..................................................92
5.4.5. "Domains" Tab in "Dante Virtual Soundcard". ......................................................93
5.4.6. "About" Tab in "Dante Virtual Soundcard"............................................................94
5.5. Using the "Dante Virtual Soundcard" with an Audio Application. ....................................96
5.5.1. Important Notes.....................................................................................................96
5.5.2. Choosing an Audio Application.............................................................................96
5.5.3. Configuring "Dante Virtual Soundcard" as your Audio Interface. .........................96
5.5.4. Windows Audio Shared Mode...............................................................................97
6. "DANTE FIRMWARE UPDATE MANAGER": FIRMWARE UPGRADING SOFTWARE...... 98
6.1. "Dante Firmware Update Manager" description. .............................................................98
6.2. Firmware upgrading procedure........................................................................................99
7. TECHNICAL SPECIFICATIONS. .........................................................................................103
8. A.E.Q. GUARANTEE............................................................................................................104
APPENDIX 1: TROUBLESHOOTING......................................................................................105
A1.1. Messages on Startup...................................................................................................105
A1.2. Computer Configuration Checklist...............................................................................105
A1.3. Thrid-party firewall configuration. ................................................................................105
A1.4. Troubleshooting Dante IP Address Configuration.......................................................105
A1.4.1. Correct IP configuration....................................................................................105
A1.4.2. Possible IP network configuration mistakes.....................................................106
A1.4.3. What are the symptoms of using the wrong network interface on my computer? ..106
A1.4.4. How do I check which network interface my Dante Controller/Dante Virtual
Soundcard is using? .........................................................................................106
A1.4.5. How do I check IP addresses for all devices on my network?.........................107
A1.5. Troubleshooting Switch Configuration and Cabling. ...................................................107
A1.5.1. Symptoms of switch or cabling issues..............................................................107
A1.5.2. Switch and Cabling Checklist...........................................................................107
APPENDIX 2: INSTALLATION DETAILS: CONFIGURATION OF ARENA CONSOLES AND
BC2000D MATRICES FOR USE WITH AOIP MULTICHANNEL BOARDS...........................108
A2.1. Scope...........................................................................................................................108
A2.1.1. ARENA, BC2000D and DANTE internal systems correspondence.................108
APPENDIX 3: INSTALLATION DETAILS: CONFIGURATION OF FORUM AND CAPITOL IP
CONSOLES FOR USE WITH AOIP MULTICHANNEL BOARDS...........................................112
A3.1. Scope...........................................................................................................................112
A3.1.1. FORUM, CAPITOL and DANTE internal systems correspondence.................112
A3.2. Configuration software.................................................................................................117
A3.2.1. "Administration" menu. .....................................................................................117
A3.2.1.1. "Configurations" submenu..................................................................117
A3.2.2. "Hardware Configuration" menu.......................................................................118
A3.2.2.1. "Board Configuration" submenu. ........................................................118
A3.2.2.2. "I/O Configuration" submenu..............................................................120
A3.2.3. "Programmable Configuration" menu...............................................................122
A3.2.3.1. "Routing Configuration" submenu. .....................................................122
A3.2.3.2. "SnapShot Configuration" submenu...................................................123
A3.3. Multichannel audio configuration internal menu options.............................................126
A3.3.1. "MEMORY" menu.............................................................................................126
A3.3.2. Multichannel routing configuration....................................................................126
A3.3.2.1. "INPUT" menu. ...................................................................................127
A3.3.2.2. "OUTPUT" menu. ...............................................................................128
APPENDIX 4: INSTALLATION DETAILS: CONFIGURATION OF NETBOX 4 MH, NETBOX 8
AD, NETBOX 32 AD AND NETBOX DSP................................................................................129
A4.1. Scope...........................................................................................................................129
A4.1.1. NETBOX 4 MH, NETBOX 8 AD, NETBOX 32 AD, NETBOX DSP and DANTE
internal systems correspondence.....................................................................129

AEQ Audio Over IP
Routing System
5
APPENDIX 5: INSTALLATION DETAILS: CONFIGURATION OF PHOENIX VENUS V3.....132
A5.1. Scope...........................................................................................................................132
A5.1.1. PHOENIX VENUS V3 and DANTE internal systems correspondence............132
APPENDIX 6: INSTALLATION DETAILS: CONFIGURATION OF OLYMPIA 3. ...................133
A6.1. Scope...........................................................................................................................133
A6.1.1. OLYMPIA 3 and DANTE internal systems correspondence. ...........................133
APPENDIX 7: DANTE BASED AEQ AOIP ETHERNET SWITCHES. ....................................135
A7.1. General configuration of DANTE based AEQ AoIP Ethernet Switches. .....................135
A7.2. Configuration of CISCO switches for AEQ AoIP systems...........................................136
APPENDIX 8: ADDITIONAL INFORMATION..........................................................................139

AEQ Audio Over IP
Routing System
6
1. INTRODUCTION.
1.1. Fields of application of the product.
Using off-the-shelf routing equipment to send audio over IP in small to medium-sized systems
offers cost advantages over synchronous solutions using AES-10 (MADI) or TDM buses. These
have higher capacity, but require powerful hardware. Besides, large TDM systems can reduce
their cost and at the same time increase their flexibility when they are combined with IP audio
links to connect a few circuits with a central router.
That’s why, when developing the IP audio routing system at AEQ, we have created not only IP
connection devices for the digital consoles, but also connection panels that allow for audio input
and output installation wherever it’s necessary, as well as access boards for the AEQ BC2000D
router.
On the other hand, AEQ insists on offering interoperability with third party devices for the
convenience of our customers. Because of that, the solution we now present is based on
AUDINATE’s technology that is operating with extraordinary performance, making our systems
100% compatible with a wide selection of equipment for Broadcast, Recording Studios and
Professional Audio (see full listing at www.audinate.com).
At the same time, in the near future we are open to adapt this solution to other technologies that
are currently under development, in order to be compatible with other manufacturers, as they
start to become mature and widely available.
Dante™ is a trademark of Audinate Pty Ltd.
Product includes license from Audinate Pty Ltd under US patent number(s) 7747725, 8005939, 7978696,
8171152 and others.Visit Audinate website for more details on Dante: http://www.audinate.com/
1.2. Description of the devices covered by this manual.
1.2.1. ARENA Console / BC2000D Matrix. BC2214 and BC2224 boards.
BC2214 and BC2224 AoIP boards are designed to be installed in BC2000D frames used in
AEQ ARENA digital mixing consoles and AEQ TITAN / BC2000D routers. Both boards have two
Ethernet ports (LAN1 and LAN2) with activity LEDs.
BC2214 board allows you to connect via IP up to 32 input and 32 output channels to/from the
BC2000D internal TDM bus system. This is enough to provide IP connectivity to an ARENA
console in a network, what is equivalent to an up to 512x512 channels IP matrix.
BC2224 board allows you to connect via IP up to 64 input and 64 output channels to/from the
BC2000D internal TDM bus system.
In order to build a large sized router, a BC2000D frame can be equipped with as many BC2214
or BC2224 boards as needed; they can be connected to one or several Gigabit Ethernet
networks, enabling TDM-IP "hybrid" routers with great flexibility.
Besides several AoIP BC2214/BC2224 boards, the BC2000D frame can be equipped with a
number of synchronous TDM access ports such as MADI (BC2211/BC2212) or the 1024
channels BC2213 (HSAL), as required, in order to create a large routing structure.

AEQ Audio Over IP
Routing System
7
1.2.2. FORUM - GRAND FORUM console. FR14 board.
FR14 AoIP board is installed as any other input/output board at the rear panel of the FORUM
console. It allows you to connect up to 32 input and 32 output channels to the unit’s TDM bus.
The FR14 board features two Ethernet ports (LAN 1 and LAN 2), both including activity LEDs.
The same console can be equipped with up to two FR14 AoIP boards. It is not compatible with
the MADI option, so in case one AoIP board is configured in the console, the MADI option will
not be available.
1.2.3. CAPITOL IP Console.
CAPITOL IP is an 8 channel digital mixing console. Its performance is based on the CAPITOL
console and the experience gained with this model. The control surface has been redesigned
with new silent buttons, more programmable keys and a new arrangement of the monitoring
section controls.
IP connectivity in CAPITOL IP console is implemented through a single module with 16 input
and 16 output channels incorporated in its core, and excludes MADI connectivity. So the rear
panel is similar to the former model with two precut holes for both Ethernet connectors.
Depending on the configuration, the unit may come either with the Ethernet connectors or the
MADI optical connector - or without any of these options - but never with both at the same time.
CAPITOL IP consoles can have a single multichannel access: IP or MADI.
1.2.4. NETBOX 32 AD Audio interface.
NETBOX 32 AD is an interface for multi-channel AoIP. It allows you to insert and extract audio
channels in a system based on DANTE technology, at locations where the installation of AEQ
digital consoles is not planned. NETBOX 32 AD features 32 input and 32 output channels
organized in 16 mono analog and 8 stereo digital channels. The stereo digital audio channels
can be configured as AES/EBU or SPDIF standard. It also incorporates 16 GPIs and 16 GPOs
(each GPIO connector includes a power supply pin to feed the external circuitry). Due to its high
input and output capacity, it is especially suitable for central controls and link dispatches and
also to increase or distribute the capacity of TDM BUS matrices such as the AEQ BC2000D.
1.2.5. NETBOX 8 AD Audio interface.
NETBOX 8 AD is an interface for multi-channel AoIP. It allows you to insert and extract audio
channels in a system based on DANTE technology, at locations where the installation of AEQ
digital consoles is not planned. NETBOX 8 AD features 8 inputs and 8 outputs, organized in 4
mono analog and 2 digital stereo channels. Stereo digital ones can be configured as AES/EBU
or SPDIF standards. The second digital stereo channel can also be switched to a USB
connector to ease the connection to an audio workstation. It also provides 4 GPIs and 4 GPOs.
The GPO port includes a power supply pin to feed the output circuitry. Due to its small footprint,
it can be useful to give IP access to analog or digital consoles that are not ready for this type of
connectivity from factory, for recording rooms, talk-rooms or any other auxiliary location.
1.2.6. NETBOX 4 MH Audio interface.
NETBOX 4 MH is an interface for multi-channel AoIP. It allows you to insert and extract audio
channels in a system based on DANTE technology, at Studio rooms and other locations where
mic/line inputs and line/headphone outputs are needed. NETBOX 4 MH features 4 inputs and 4
outputs. The input channels are mic/line type with XLR connector and frontal switch. The output
channels are balanced at line level and are sent to 4 headphone outputs, that can be configured
as stereo pairs. It also provides 4 GPIs and 4 GPOs. The GPO port includes a power supply pin
to feed the output circuitry. It also provides additional special GPIOs for connection of signalling
and control boxes, including 7 optocoupled GPIs and 2 relay GPOs for ON AIR signalling, that
can be feed from the unit.
IMPORTANT NOTE: NETBOX 4 MH does not support redundant operation.

AEQ Audio Over IP
Routing System
8
1.2.7. NETBOX DSP Router.
NETBOX DSP device is able to receive audio from the DANTE network and then return it,
mixed and processed, to be used in another device or subsystem. It can also generate a test
tone (1KHz) and vumeters of all the inputs and outputs. There are 4 different versions of
NETBOX DSP: NETBOX DSP 64, NETBOX DSP 96, NETBOX DSP 128 y NETBOX DSP 160,
with routing and mixing capabilities on 64, 96, 128 or 160 inputs to any of the 64, 96, 128 or 160
outputs in the AoIP network, respectively. It's possible to add any quantity of inputs (up to 160
depending on the version) in any of the outputs. In addition, there is gain control for all the
inputs, outputs and cross points. Any output can also be muted. All 4 versions have the same
processing capability on a maximum of 64 selectable inputs, that can be sent processed to any
of the outputs.
It also incorporates 16 GPIs and 16 GPOs (each GPIO connector includes a power supply pin
to feed the external circuitry), as well as 256 virtual GPIs and 256 virtual GPOs that can be
transported through the IP network between compatible devices (this way, a GPI can drive the
GPOs of other devices).
1.2.8. PHOENIX VENUS V3 Audiocodec.
PHOENIX VENUS V3 is a double multiformat and multi-algorithm audiocodec. It offers
optionally (it can be activated by means of a license) the possibility of inserting and extracting
audio channels in a system based on DANTE technology through one of its 2 Ethernet ports.
PHOENIX VENUS V3 features 4 inputs and 4 outputs.
IMPORTANT NOTE: PHOENIX VENUS V3 does not support redundant operation.
1.2.9. OLYMPIA 3 Commentary unit.
OLYMPIA 3 is a digital commentary unit (CU) that allows you to insert and extract audio
channels in a system based on DANTE technology through one of its 3 Ethernet ports.
OLYMPIA 3 features 8 inputs and 8 outputs.
1.2.10. SYSTEL IP 16 VoIP ON AIR Telephone System.
SYSTEL IP 16 is a VoIP ON AIR telephone system that allows you to insert and extract audio
channels in a system based on DANTE technology through 2 of its 3 Ethernet ports. SYSTEL IP
16 features 32 inputs and 32 outputs.
1.2.11. "Dante Virtual Soundcard".
Being an open system, any third-party device compatible with DANTE technology can be
incorporated. Among them, the "Dante Virtual Soundcard" is especially interesting, as a
complement to the equipments presented by AEQ. This software can be downloaded, in trial
and full versions at www.audinate.com. Chapter 5 in this manual explains how to configure and
operate it.
Any computer with "Dante Virtual Soundcard" installed can receive and send channels from / to
AEQ consoles and matrixes. It is very useful for monitoring and intercom purposes from the
network control stations where the "Dante Controller" application, described below, is installed.
IMPORTANT NOTE: "Dante Virtual Soundcard" does not support redundant operation.
1.2.12. Control Software "Dante Controller".
The system is able to auto detect all DANTE-enabled equipment that can provide Audio within
the network. Through the "Dante Controller" application installed on one or more computers on
the network, the user can choose among the available audio channels which one should be
received from the different consoles or interfaces. The application is very comprehensible and
easy to operate. Chapter 4 in this manual explains how to operate it.

AEQ Audio Over IP
Routing System
9
Compatibility with other manufacturers is absolute. "Dante Controller" software makes the
different IP access cards work together, no matter which manufacturer provides the equipment
they are installed in.
1.3. General Features.
•Up to 512 audio channels in each Gigabit Ethernet network. Possibility of integration of
several networks in a TITAN / BC2000D 5120 x 5120 circuit concentrator.
•Double Ethernet Audio over IP connections in all AEQ consoles and digital matrices.
•Standalone, double audio over IP interfaces, making audio input and output
connections to central controls, link dispatches, analog studios, reporter cabins and any
other locations where an AEQ digital mixing console is not available an easy task.
•The system is usually structured as a star-topology using Gigabit Ethernet switches.
•For smaller installations, the system can be cascaded or "daisy chained", as network
interfaces are duplicated.
•Where maximum availability is a design goal, the network can be wired with duplicate
switches, ensuring uninterrupted operations with redundant paths.
•Data transport between devices that allows converting a GPI on one device into a GPO
on another device in the network.
1.4. Operation of the AEQ AoIP system based on DANTE.
1.4.1. Discovery and auto-configuration.
When a Dante-enabled device is connected to an IP/Ethernet network, it will automatically:
•Configure its IP address.
•Advertise itself to allow automatic discovery.
Within seconds of a Dante-enabled device connecting to a network, "Dante Controller" will
automatically discover and display the device, allowing you to configure channels and route
audio.
Network automatic configuration.
A Dante-enabled device connected to a network will automatically setup its own network
configuration, including its IP address.
If the network has a DHCP server, which may be the case for installed networks, it will receive
its IP configuration using the standard DHCP protocol.
On a network without a DHCP server, which may be the case for temporary or smaller
networks, the Dante-enabled device will automatically assign itself an address using link local
protocols, in the same way PCs and printers often do.
Automatic discovery.
A Dante-enabled device will advertise information about itself to other Dante devices and
"Dante Controller", including:
•Device name.
•Audio channel labels.
•Number of audio channels.
•Sample rates and bit depths.

AEQ Audio Over IP
Routing System
10
This information can be seen when viewing a device on "Dante Controller", and allows Dante
devices to determine compatibility with other devices, such as compatible sample rates to allow
audio to be routed.
Device Channels.
A Dante device has a number of channels associated with it. These are either transmit (Tx) or
receive (Rx) channels. Receive channels and devices are listed down the left side of the grid.
Transmit channels and devices are listed along the top of the grid.
Transmit channels are advertised on the network. A receiver uses this advertisement to
establish a subscription to the channel. A transmit channel can be sent to multiple receivers
using unicast or multicast.
Receive channels are connected to transmit channels via a subscription. Each receive channel
will receive audio over the network from at most one transmit channel. Chapter 4.7.4.1 explains
this in detail.
1.4.2. Differentiation between input and output channels.
Channels are classified according to whether they put audio data onto, or take audio data off
the network:
•A channel that puts audio data onto the network is known as a transmitter, Tx or output
channel.
•A channel that takes data off the network is known as a receiver, Rx or input channel.
1.4.3. Device Names and Channel Labels.
In Dante, devices and audio channels are identified by names and labels. Device names and
channel labels can be customized.
IMPORTANT NOTE: Device names must be unique on a Dante network. Channel labels must
be unique on the device.
Dante routing is performed using the device names and channel labels. A receive channel can
be subscribed to the name of a transmit channel at a device.

AEQ Audio Over IP
Routing System
11
Example: "Analog_L@FORUM-IP 1" describes a channel labelled "Analog_L" on a device
named "FORUM-IP 1".
If a device or channel is renamed, Dante routing considers it to be a different device or channel.
If a new device or channel is then given the old name, Dante routing will route from the new
device in place of the previous device.
Example: The power supply on "Netbox 3" fails and "Netbox 3" needs to be replaced. The old
"Netbox" is removed, and a new "Netbox" is plugged in and named "Netbox 3". Dante receivers
previously subscribed to the old "Netbox 3" will now automatically restore their subscriptions to
the new "Netbox 3".
Device names must be unique on the network. If you attempt to rename a device using "Dante
Controller" to a name that is already in use on the network, "Dante Controller" will notify you and
reject the name change.
Example: There is an existing device on the network called "MY16 - Slot1". If user attempts to
rename another device to "MY16- Slot1" "Dante Controller" will notify you that the name is
already in use. The device will not be renamed.
If a new device is added to the network with a name that already exists, a name conflict is
detected, and one of the devices will rename itself by appending (2) to its name. This device will
not be able to transmit audio until it is renamed.
NOTE: A device that has been renamed with (2) appended (e.g. "MY16- Slot1 (2)") will NOT BE
ABLE to transmit audio until it is renamed. The device name must be changed by the user to be
a valid non conflicting name before the device can become fully functional.
Rules for Names and Labels.
•All Dante names and labels are up to 31 characters in length. Name and label
comparisons are caseinsensitive; "Guitar" and "guitar" are treated as the same label.
Unicode and non-roman characters are not supported.
•Device names should follow Domain Name System (DNS) hostname rules. Legal
characters are AZ, a-z, 0-9 and '-' (dash or hyphen).
•Tx channel labels may use any character except '=' (equals), '.' (full stop or period) or
'@' (at). Tx channel labels must be unique on a device. Tx channel labels do not need
to be unique on the network as they are always qualified by device (channel@device).
•RX channel labels follow the same rules as Tx channel labels.
1.4.4. Routing Audio.
Routing Terminology.
Device: A device means a Dante-enabled device, and more specifically that component of the
audio equipment that implements the Dante interface. A Dante device typically has Tx and Rx
channels and other routing-related properties.
Transmit (Tx) channel: A transmit channel transmits audio from the audio hardware onto the
network.
Receive (Rx) channel: A receive channel receives audio from the network and sends it to the
audio hardware.
Flow: Dante audio routing creates flows. Each flow carries several channels of audio from a
transmitter to one or more receivers. Unicast routing creates flows to single receivers. Multicast
routing creates flows that can be received by multiple receivers. Multicast flows are assigned
IDs enabling them to be identified in "Dante Controller".

AEQ Audio Over IP
Routing System
12
Unicast routing: Unicast flows are point-to-point from a single transmitter to a single receiver.
Unicast flows typically have room for 4 channels of audio.
Multicast routing: Multicast flows are one-to-many from a single transmitter to any number of
receivers. Use "Dante Controller" to choose which channels are to be multicast. Unlike unicast
routing, multicast flows consume network bandwidth even if there are no receivers, but do not
require additional bandwidth to add more receivers.
Subscription: A subscription configures a receive channel (Rx) to receive audio from a transmit
channel (Tx) on another Dante device.
Subscription status: For a receive channel, subscription status indicates whether it is
subscribed, whether it is receiving unicast or multicast audio, whether the subscription is OK, or
whether an error has occurred.
Subscription.
Dante routing is performed by associating a receiving (Rx) channel with a transmitting (Tx)
channel. This is called subscription.
Example: Route Tx channels 1 and 2 (labelled "Audio L" and "Audio R") on the device labelled
"Source" to Rx channels 3 and 4 on the device labelled "Dest".
Rx channels 3 and 4 on "Dest" are subscribed as follows:
•3. Audio L@Source
•4. Audio R@Source
Dante will perform the necessary audio routing to deliver the audio from the Tx channels to the
Rx channels.
Redundancy.
Many Dante devices support redundant audio routing. These devices have two network
interfaces, labelled primary and secondary. Primary interfaces should be connected to one
physical network.
IMPORTANT NOTE: If redundancy is being used, secondary interfaces should be connected to
a second separated network. Secondary interfaces cannot communicate with primary
interfaces.

AEQ Audio Over IP
Routing System
13
If the secondary network is connected to a device that supports redundancy, it is enabled
automatically. Audio data is transmitted on both the primary and secondary networks
simultaneously. In the event of a failure on one network, audio will continue to flow via the other
network.
NOTE 1: Dante redundancy requires that both the primary and secondary interfaces on any
redundant device are connected using the same link speed. For example, if the primary
interface is connected to a 1 Gbps switch port, the secondary interface must also be connected
to a 1 Gbps switch port. Similarly, if the primary interface is connected to a 100 Mbps switch
port, the secondary interface must also be connected to a 100 Mbps switch port.
NOTE 2: Dante devices that do not support redundancy must be connected to the primary
network only.
Audio Formats.
Some Dante devices support a range of audio formats (sample rates). AEQ equipment operates
at FS=48 kHz, 24 bits PCM.
It is only possible to set up a subscription between channels which have a common audio
format. If AEQ pieces of equipment are connected to systems from other manufacturers, make
sure that they are setup to operate at 48 kHz 24 bits PCM. Channels on devices with
incompatible formats will be shown in grey, and will not be routable.
Flows.
Dante audio routing creates 'flows'. Each flow carries one or more channels of audio from a
transmitting device to one or more receiving devices. There are two types of flow: unicast and
multicast.
Unicast routing creates flows to a single receiving device; a unicast flow typically assigns space
for 4 channels of audio. Unicast flows are set up when a receiver subscribes to an available
audio channel, and are automatically removed when the receiver unsubscribes from all
channels in that flow.
Multicast routing creates flows that can be received by multiple receivers. Multicast flows are
assigned IDs, enabling them to be identified in "Dante Controller", and to facilitate their removal.
In contrast to unicast flows, multicast flows must be set up on the transmitting Dante device
before receivers can subscribe to these flows.

AEQ Audio Over IP
Routing System
14
Advanced Routing: Using Multicast.
Dante routing is unicast by default. This means that a separate flow is set up between each
transmitter and receiver. If several receivers are all subscribed to the same channels of a
transmitter, it may sometimes be more efficient to use multicast.
Multicast sends the same set of channels to multiple receivers. In practice, this usually means
that the audio flow is flooded throughout the network. If many receivers want the same
channels, using multicast can reduce overall network use, especially on the transmitter,
because only one copy of each audio channel needs to be sent, rather than many.
Dante receivers will automatically prefer multicast to unicast if it is available. This means that if a
new multicast flow is created containing the channels that a receiver is currently receiving as
unicast, the receiver will switch over to receiving audio from the multicast flow and the unicast
flow will be removed.
1.4.5. Clock Synchronization.
All Dante-enabled devices use the IEEE 1588 Precision Time Protocol (PTP) across the
network to synchronize their local clocks to a master clock, providing sample-accurate time
alignment throughout the network.
One Dante device will be elected as the PTP Master Clock for the network; all other Dante
devices act as a PTP Slave Clocks to the elected master clock. Although many Dante devices
may be capable of becoming PTP Master Clock, only one device will win the election. Devices
with clock inputs (e.g. Word Clock or AES3) will be preferred in the election process. A gigabit
connected device is preferred over a device connected via 100Mbps. A tie-breaker rule of the
lowest MAC address is used if several equivalent candidate master clocks are available. The
election process may be overridden by manually setting 'Preferred Master' on a device.
Dante Clock Types.
Each Dante hardware device can derive its clock from either its high-quality onboard clock
circuit, or an externally connected word clock. In the case of "Dante Virtual Soundcard", the
computer’s clock will be used.
Clock Settings.
Slave to External Clock Word.
A Dante device set to "Slave to External Clock Word" will use the external word clock from its
host equipment to tune its onboard VCXO. A Dante device with this attribute set will become the
PTP Master Clock, unless there is another Dante device present with 'Preferred Master' set.
Preferred Master.
Sometimes it may be necessary to force a particular device to provide the PTP Master Clock. A
Dante device with 'Preferred Master' set will always be chosen as the PTP Master Clock. If
more than one device has 'Preferred Master' set, the device with the lowest MAC address will
be chosen.
Clocking and Synchronization in Redundant Networks.
In a redundant network, the clock synchronization protocol operates over both primary and
secondary networks. Each network will have a designated PTP master clock; usually this will be
the same device on both networks. If this is not the case (e.g. if a non-redundant device is
designated Preferred Master) then one device will bridge the clock synchronization information
from the primary to the secondary network, ensuring that all devices derive their clock from the
same source. Redundant PTP Slave clocks will synchronize their local clocks based on
information from one of the networks they are connected to. In event of a failure on one
network, a redundant device will continue to receive clock synchronization information over the
other network.

AEQ Audio Over IP
Routing System
15
1.4.6. Latency.
In Dante, variation in latency in the network is compensated for at the receiver. Each receiver
has a device latency setting. This setting defines the latency between the timestamps on the
incoming audio samples and when those samples are played out.
The typical default latency for a Dante device is 1 msec. This is sufficient for a very large
network, consisting of a Gigabit network core (with up to 10 hops between edge switches) and
100 Mbps links to Dante devices. Smaller, Gigabit-only networks can use lower values of
latency (down to 150 µsec for very fast devices, such as PCIe cards). Recommended latency
settings are displayed in "Dante Controller", and may also be found in the documentation
accompanying the product.
Latency is set on the receiver. However, when a subscription is made, there is an automatic
negotiation process between the receiver and the transmitter, to ensure that the latency for the
subscription is high enough to prevent packet loss.
For example, Ultimo devices support a minimum of 1ms latency. If a faster device (such as a
PCIe card) is set to 0.25ms latency and is then subscribed to an Ultimo transmitter, the latency
used for the subscription will be 1ms, which is the minimum supported latency for the
subscription. Subscriptions to other devices (such as a Brooklyn II device using AEQ devices
with two AoIP ports) will be set at 1ms (or whatever latency the receiver is set to). This
effectively makes the device latency setting a 'default' latency, which is used unless the
transmitter doesn't support it.
NOTE: The minimum latency available for a device connected to a 100 Mbps network port is 1
msec. Using a latency lower than 1 msec over a 100 Mbps link will result in a subscription error,
with the tooltip 'Tx Scheduler Failure'.
Latency and Dante Virtual Soundcard.
"Dante Virtual Soundcard" allows a standard Apple Mac or Windows PC to function as a Dante
device. Because "Dante Virtual Soundcard" runs on a general purpose computer without special
hardware to support Dante timing requirements, additional latency needs to be added to
connections received from a "Dante Virtual Soundcard" transmitter.
"Dante Virtual Soundcard" is configured with custom latency values for reliable operation. Dante
devices with Rx channels that are subscribed to Tx channels from a "Dante Virtual Soundcard"
transmitter will automatically configure themselves to use these higher latency values for those
channels only. The latency on all other subscriptions on the receiver is unaffected.
1.4.7. Device Lock.
Device Lock allows you to lock and unlock supported Dante devices using a 4-digit PIN
(Personal Identification Number).
When a device is locked, audio will continue to flow according to its existing subscriptions, and it
can be monitored, but it cannot be controlled or configured – its subscriptions and configuration
settings become read-only.
To configure a locked device you must first unlock it using the PIN with which it was locked.
Locked devices can be identified by:
•A small grey padlock icon against the device name in the Network View > Routing tab
•A red background highlight when the device is moused over in the Network View >
Routing tab.
•A check (tick) in the Device Lock column in the Network View > Device Info tab.
•A red padlock icon in the Device View toolbar

AEQ Audio Over IP
Routing System
16
Not all Dante devices support Device Lock. The feature will be rolled out over time via device
manufacturer firmware updates.
To check if a Dante device can be locked:
•Use the Advanced Filter to check for locked, unlocked and unsupported devices.
•Check the Device Info tab – devices that support Device Lock have a checkbox in the
Device Lock column; devices that do not support Device Lock show ‘N/A’ in the Device
Lock column.
•Open the device in Device View – if the padlock icon in the toolbar is blue or red, the
device supports device lock; if it is greyed out, it does not support Device Lock.
NOTE: Earlier versions of "Dante Controller" (prior to v3.10) do not support Device Lock, and
will not actively identify when Dante devices are locked. Attempts to configure or subscribe to a
locked device in earlier versions of "Dante Controller" will fail silently.
Locking a Dante device.
To lock an unlocked Dante device:
Using Device View:
1. Open the device in Device View (Ctrl+D, or
Command+D) and click the padlock icon
The Lock Device panel is displayed.
2. In the Lock Device panel, enter a 4-digit PIN in the PIN
field.
3. Enter the same PIN in the Confirm PIN field.
4. Click ‘Lock’.
The padlock icon will change to red indicating that the device is now locked.
From the Device Info Tab:
1. In Network View, select the Device Info tab.
2. Click the Device Lock checkbox for the device.
3. Follow steps 2-4 from the above process.
Unlocking a Dante device.
To unlock a locked Dante device:
Using Device View:
1. Open the device in Device View (Ctrl+D, or
Command+D) and click the padlock icon
2. In the Unlock Device panel, enter the 4-digit PIN in the
PIN field.
3. Click ‘Unlock’.
The padlock icon will change to blue indicating that the
device is now unlocked.
From the Device Info Tab:
1. In Network View, select the Device Info tab.
2. Click the Device Lock checkbox for the device.
3. Follow steps 2-3 from the above process.

AEQ Audio Over IP
Routing System
17
Unlocking a device when you have forgotten the PIN.
If you have forgotten the PIN for a locked device, you can reset the PIN.
To reset the PIN for a locked device:
1. Isolate the device from the rest of the Dante network.
2. Disconnect and reconnect the device.
3. Wait for at least 2 minutes.
4. Use the ‘Forgot PIN’ option in the Unlock Device panel.
How to Isolate a Device from the Rest of the Dante Network.
There are 3 ways to isolate a device from the rest of the network.
Option 1: Remove all other Dante devices from the Dante network.
You can isolate a device by physically disconnecting all other Dante devices from the network
switch, or by completely powering down all other devices, leaving on the network only the
locked device and the computer running "Dante Controller".
NOTE: Dante Virtual Soundcard and Dante Via are considered to be Dante devices – all
running instances of those applications must be fully stopped, even if they are on the same
computer on which you are running "Dante Controller".
Option 2: Connect your "Dante Controller" computer directly to the device.
Physically remove the device from the main Dante network switch, and either connect it directly
to your "Dante Controller" computer (using a normal Ethernet cable), or connect the device and
your computer to a separated network switch (to which there are no other Dante devices
connected).
Option 3: Use a VLAN.
Set up a Virtual Local Area Network on which there are only the locked device, and the Dante
Controller computer.
Resetting the PIN for a Locked, Isolated Device.
Once you have isolated the locked device, disconnected and reconnected it, and then waited for
at least 2 minutes:
1. Open the Unlock Device panel for the device (See Unlocking a Dante Device).
2. Click the ‘Forgot PIN’ option.
3. Click Reset.
The device is now unlocked, and can be re-locked using a new PIN if required.
Subscriptions from Unlocked Devices to Locked Devices.
If there are existing subscriptions to a device when it is locked, those subscriptions will continue
to function as normal.
They can also be removed, and replaced (assuming the subscribing device is unlocked).
No new subscriptions can be made to a locked transmitter. The 'Access control' tooltips are
associated with attempted subscriptions to locked transmitters.
NOTE: If you attempt to subscribe a legacy (pre-v3.10 firmware) receiver to a locked
transmitter, subscription status icons for any existing subscriptions (made before the device was
locked) may change to indicate an error state. However, audio will continue to flow for those
subscriptions. To reset the subscription icons: Remove all subscriptions, and reinstate the
original subscriptions only.

AEQ Audio Over IP
Routing System
18
Locking Devices with Residual Connections.
Occasionally, a transmitter will have residual unused connections (transmitting but
unsubscribed channels) from a previous subscription state, which need to be closed before the
device is locked. This can cause an interruption to audio from that device.
When you attempt to lock a device and residual connections are detected, "Dante Controller"
presents a warning dialog:
Click Ok to proceed or Cancel to abort the lock process.
While the residual connections are being closed, "Dante Controller" displays a progress dialog:
When the preparation process is finished, the standard Lock Device dialog is presented, and
the device can be locked as normal.
1.4.8. Dante Control and Monitoring.
In addition to automatic configuration and discovery, audio transport and routing, Dante-enabled
devices can also be controlled and monitored in various ways. This includes being able to view
and change specific parameters, such as clock configuration settings. Dante devices are also
capable of sending status events that can be viewed using "Dante Controller". Status events
include changes in clock status, or network interface changes.
NOTE: The computer service that manages control and monitoring is called 'ConMon'.

AEQ Audio Over IP
Routing System
19
2. PHYSICAL DESCRIPTION OF THE UNITS.
In order to understand the installation and cabling process associated to each unit, first you
need to be familiar with the connectors and other specific elements of the AoIP solution
described in this manual and the equipment front and back panels. In the case of BC2000D,
ARENA, FORUM, GRAND FORUM and CAPITOL IP units, have in mind that the general
information about them is included in the respective user manuals, so this one includes only
specific pieces of information related to the AoIP solution.
2.1. BC2214 and BC2224 modules description.
2.1.1. Front panel description.
Any number of BC2214/BC2224 modules can be installed in the back Input/Output
slots of the BC2000D router or ARENA digital mixing console frames. Each module has
two connectors, LAN 1 and LAN 2, each one with its respective physical link signaling
LEDs.
-LAN LEDs:indicate the status of the audio local area network: LAN 1 (main
interface) and LAN 2 (secondary interface).
Status:
•Off: no local network connection.
•Blinking green: link is established at data level.
•Steady yellow: link is established at physical level only.
If the boards are wired to a dedicated audio network using a switch, in LAN 1 only, the
green LED should be blinking and the yellow one should be steady on. If the wiring is
connected in "Daisy Chain" mode, without switch, or there is a redundant network, both
green LEDs should be blinking and both yellow ones should be steady on.
IMPORTANT NOTE: When there is a redundant network, primary and secondary
interfaces must be connected to separated networks.
2.2. FR14 module description.
2.2.1. Front panel description.
One or two FR14 modules can be installed in the FORUM digital mixing console
back Input/Output slots 14 and 13, respectively. Each module features two
connectors, LAN 1 and LAN 2, with their corresponding physical connection
indicator LEDs:
-LAN LEDs:indicate the status of the audio local area network: LAN 1
(main interface) and LAN 2 (secondary interface).
Status:
•Off: no local network connection.
•Blinking green: link is established at data level.
•Steady yellow: link is established at physical level only.
If the boards are wired to a dedicated audio network using a switch, in LAN 1 only, the green
LED should be blinking and the yellow one should be steady on. If the wiring is connected in
"Daisy Chain" mode, without switch, or there is a redundant network, both green LEDs should
be blinking and both yellow ones should be steady on.
IMPORTANT NOTE: When there is a redundant network, primary and secondary interfaces
must be connected to separated networks.

AEQ Audio Over IP
Routing System
20
2.3. CAPITOL IP BOARD module description.
2.3.1. Back panel description.
Only one CAPITOL IP BOARD
module can be installed inside
the CAPITOL IP digital mixing
console core. In that case, two
Ethernet LAN 1 and LAN 2
ports will be installed in the
AoIP area of the core back panel, with their corresponding physical connection indicator LEDs:
-LAN LEDs: indicate the status of the audio local area network: LAN 1 (main interface)
and LAN 2 (secondary interface).
Status:
•Off: no local network connection.
•Blinking green: link is established at data level.
•Steady yellow: link is established at physical level only.
If the boards are wired to a dedicated audio network using a switch, in LAN 1 only, the green
LED should be blinking and the yellow one should be steady on. If the wiring is connected in
"Daisy Chain" mode, without switch, or there is a redundant network, both green LEDs should
be blinking and both yellow ones should be steady on.
IMPORTANT NOTE: When there is a redundant network, primary and secondary interfaces
must be connected to separated networks.
2.4. NETBOX 32 AD interface description.
2.4.1. Front panel description.
NETBOX 32 AD includes 2 connectors, LAN 1 and LAN 2, placed on the back panel of the unit,
each one with its respective physical link signaling LEDs.
On front panel, there are indicators related to the unit status, communications and audio levels.
The ones that are interesting regarding AoIP connection are:
-LAN LEDs: indicate the status of the audio local area network: LAN 1 (main interface)
and LAN 2 (secondary interface).
Status:
•Off: no local network connection.
•Blinking green: link is established at data level.
If the unit is wired to a dedicated audio network using a switch, only LAN 1 should be blinking. If
the wiring is connected in "Daisy Chain" mode, without switch, or there is a redundant network,
both LEDs be blinking.
IMPORTANT NOTE: When there is a redundant network, primary and secondary interfaces
must be connected to separated networks.