Voltera D Networking
While Voltera D supports analog inputs for local audio sources, device discovery and configuration are all managed over a standard IP network connection. Voltera D also supports systems based around AVB, or Dante and AES67 network media transport. This resource provides additional detail about the network capabilities of Voltera D.
Supported network topologies
Voltera D supports similar network topologies as other Tesira Server Class devices. It may be configured and cabled for separated control and media networks, or with converged control and media, utilizing either dual or single cable connectivity. More information on the various network topologies can be found here - Single Network Connection option in Tesira.
Separated Control and Media
Converged Single Cable Control and Media*
*Note: When configured from VenueTune software, the Dante interface supports DHCP or APIPA assignment. If static addresses are planned for control, separated control and media may be more appropriate.
Network port configuration
Port roles
Voltera D has two network interfaces labeled 1 and 2. Port 1 (P1) provides a control connection for device discovery, management, and programming. Port 2 (P2) supports network media (AVB, Dante, AES67). P2 can also support control communications if deployed in a single cable topology. These two port roles are functionally similar to a rack mount TesiraFORTÉ.
PoE
The P1 control port also supports PoE+ (IEE802.3at Class 4). This is helpful in critical applications where the network switches are connected to a UPS. In the event of an outage, PoE sourced power can keep the host processor and access to the DSP alive. Once back up generators or main power is restored, boot time is greatly reduced as just the amplification needs to be brought back up.
Voltera D can alert if it detects a loss of PoE on the P1 network connection.
MAC addresses
Voltera D utilizes 3 unique MAC addresses - one for control on the P1 interface, and one each for AVB and Dante on the P2 interface.
IP Addressing
Depending on the network topology, Voltera D will utilize up to 3 unique IP addresses.
When connected in a separated control and media topology the P1 control interface can support static, DHCP, or APIPA assignment. In this topology all direct device communication takes place over this interface. Below are examples from Tesira software, Device Maintenance > Network Settings...
The media_avb_0 and Dante interfaces are available on P2 and support static, DHCP, or APIPA assignment. Voltera D must be unconfigured in order to change the Dante IP or hostname*.
When connected in a single cable converged topology, the media_avb_0 interface is the target for communication to the device.
* Note: If configuring Voltera D from VenueTune software, the Dante interface supports DHCP or APIPA assignment. Static IP address assignment is not available. Please see the following Cornerstone resource for further detail on managing IP addresses in VenueTune - VenueTune IP address management.
Network media
Voltera D supports AVB, or Dante and AES67. The available options are dependent on the software used for configuration. If using Tesira software, either AVB or Dante and AES67 may be utilized. If configuring from VenueTune, Dante and AES67 are available for network media transport.
AVB
Voltera D can transmit up to 32 channels and receive up to 32 channels of AVB audio. Audio channels must be grouped into up to 32 AVB streams, and each stream can be comprised of up to 32 channels. As the number of streams being used increases, the maximum channel count may decrease. More information on the AVB capabilities of Tesira devices can be found here in the help file.
AVB is supported in both separated or converged topologies.
If part of a multi-device Tesira configuration, AVB will typically be the best choice for network media. All routes to/from other AVB capable Tesira devices in the same system are managed by the Tesira compiler and no additional external routing is required to share audio system wide.
Voltera D can act as a proxy for Tesira expanders. Up to 5 expanders may be proxied from the 4 channel models and up to 9 on the 8 channel versions. A small amount of available DSP overhead in Voltera D allows for input/output expansion and routing even in systems where Votlera D is the only Tesira server class device.
The below table provides an approximation of the default DSP usage and overhead. It is recommended to create the Tesira layout file ahead of time to determine the needed DSP usage for a project. If the DSP requirements exceed the available overhead in Voltera D, another Tesira server class device, such as a TesiraFORTE or Server IO may be added to the system design.
| Voltera Channel Count | DSP in use (failover / analog input mode) | Available DSP (failover / analog input mode) |
| 4 channel | 96.4% / 93.9% | 3.6% / 6.1% |
| 8 channel | 95.2% / 92.6% | 4.8% / 7.4% |
Dante and AES67
Voltera D utilizes the IPCore solution from Audinate. This is similar to the Dante interface found in TesiraFORTÉ X and TesiraFORTÉ DAN. It supports up to 32 x 32 channels and 32 x 32 flows of Dante.
Votlera D also supports 96kHz sample rates for integration in systems where this is required. Please note that other Tesira Dante capable devices support only 48kHz and multi-Device Teisra systems may need to consider this during the planning stages.
As part of the Dante implementation, AES67 support may be enabled for interop with 3rd party devices that have AES67 capabilities only. Cornerstone has excellent resources on both Dante and AES67. Please reference these for additional information.
Mixed Media Networks
Voltera D may be configured to receive/send audio using AVB or Dante. It is not recommend to deploy Voltera D on 3rd party network switches where AVB and Dante are converged. If AVB is used, this may result in Dante clock sync faults to be logged by the device.
802.1X security
Voltera D supports 802.1X port security for the control and AVB interfaces. 802.1X protocol uses a central managed membership list to grant network access only to hardware devices which can provide proper authentication.
802.1X does not work on dynamic AVB VLANs on Extreme Networks hardware. If 802.1X is desired on AVB an alternate AVB VLAN can be manually created and 802.1X enabled.
Please refer to the Biamp Cornerstone article on 802.1X for more details.