Table of Contents
Advertisement
2.2.2
PTP configuration
Check / configure all relevant PTP parameters the device offers; follow the guidelines given in section
2.1.5
PTP.
2.2.3
Device-specific configuration
Some devices need further configuration to interoperate properly with other AES67 gear. Here are a
few commonly observed settings which may have to be configured individually:
2.2.3.1
AES67 mode
Some devices require you to activate the AES67 mode (i.e. Dante devices), other devices support
AES67 natively (RAVENNA, Livewire).
2.2.3.2
Multicast address range
Despite not being fully AES67-compliant, some devices only support a limited range of multicast
addresses for AES67 interoperation (i.e. Dante devices). The range needs to be configured properly
with all devices; note that this may even affect devices which don't exhibit this limitation, as AES67
streams would only be identified / accepted when their multicast address is within that configured
range. As some devices don't have a general device-level configuration for multicast address range
(they can work with any valid multicast address in the range 239.x.y.z), this may be have to be
respected when configuring individual streams.
2.2.3.3
Discovery
While most devices also use their native discovery method for announcement of AES67 streams,
some devices offer the ability to enable other discovery options on demand (i.e. enable SAP support).
2.2.3.4
Audio-related configuration
Some devices support different sampling rates, but only one may be selected at any given time
(usually because a device only has one clock circuitry). AES67 calls for support of 48 kHz, but other
sample rates may be used; make sure you select the desired sample rate. Further device-specific
parametrization may be required; check with the operator's manual.
2.3
Check for proper synchronization (PTP)
Once all devices have been configured, check for proper synchronization. This is important because
all devices on the network derive their locally generated media clocks from the network clock
distributed with PTP.
2.3.1
Grandmaster selection
It is advised that you select a device as the preferred master beforehand and set every other device
to slave-only mode. Follow the steps under
all devices should indicate that they are listening to the same Grandmaster (IP address and / or GM-
ID should be identical). If you see different GM-IDs, the BMCA did not work as intended and at least
one device is assuming a false GM role. Here's a quick checklist:
2.1.5.2 BMCA parameters
Page 12 of 28
AES67 Practical Guide
. Once properly configured,
Advertisement
Table of Contents
