Thought I would share this one as it frustrated myself and my client for a while but eventually the solution was simple once the missing pieces are put in place...
I am working on a court house project, we are streaming AES67 to the transcription recorders which are Windows servers running the LAWO R3LAY virtual sound card software (64 channel). My responsibility was to program and deliver the AES67 streams. The clients IT provider is receiving the streams. I was asked to step in and help when receiving the streams become troublesome. Initially, a Wireshark session revealed network (VLAN) issues as no PTP clock packets where observed. Session discovery as we soon discovered was the next hurdle...
We could see the AES67 streams using Dante Controller, so we knew the streams hit the server, R3LAY just didn't see them.
While the Merging Ravenna VSC (MacOS) supports SAP/SDP announcements to detect the streams, the LAWO VSC only supports Bonjour. FYI the Q-Sys AES67 Transmitter provides SAP/SDP announcements only so the marriage of LAWO R3LAY and Q-Sys AES67 is off to a bad start. We now had PTP clock locked but no streams detected.
Initially, I copy and pasted the SDP data from my MacOS VSC (as detected) and manually added a stream to R3LAY by pasting the SDP data into the "Add Stream SDP" method. This worked, jumping for joy! Matt Stapleton stepped in and offered a way to do the same with VLC on Windows. But... The multicast address of the stream changed whenever the DSP core was rebooted. So, my advice is to statically set the multicast address (MANUAL mode) on the AES67 transmitter, for this reason.
One more thing, I set the DSP project to the "Audinate" profile as I had no Q-Lan requirements and the R3LAY VSC defaults to PTP DSCP of 56, although its configurable.
LAWO R3lAY https://www.lawo.com/jade-vsc.html