Cisco Room Bar pRo with Shure mXA920 - aes67 setup

[mrdivakar]

Dear Cisco Support Team,

We are currently working on integrating AES67 audio from a Shure MXA920R microphone to a Cisco Room Bar Pro and are following the official integration guidelines.

Here is a summary of our current setup:

• The AV Integrator license is activated on the Cisco Room Bar Pro.

• The Shure mic is configured with a static Dante IP: 169.254.1.225 and is directly connected to the PoE Ethernet port of the Cisco Room Bar Pro.

• AES67 is enabled on the microphone and a multicast flow has been successfully created.

• The multicast address used is: 239.69.40.222.

On the Cisco side, we have configured the following settings:

mathematica

CopyEdit

xConfiguration Audio Ethernet Encryption: Optional xConfiguration Audio Ethernet SAPDiscovery Mode: On

However, when we try to execute the following command:

arduino

CopyEdit

xStatus Audio Input Ethernet DiscoveredStream

we receive a “command rejected” error.
Appreciate your support in resolving this issue.

[Jonathan Schulenberg]

Edit: Correction, your post doesn't actually state that the SAPDiscovery group was changed, only what the AES67 group is. You shouldn't need xConfiguration Audio Ethernet SAPDiscovery Address then.

You're entering that command via an SSH session to the Bar Pro and not via Control Hub, correct?

[mrdivakar]

hi Jonathan,

thank you for the response , yes you are correct ,  the mentioned multicast address is for Shure mic which i can see in dante controller .  i am entering the commands from web UI in Api section . 

so basically, on Shure Mic side, static ip configured for Dante and Control IP is DHCP,  shure mic is connectd to poe port of cisco room bar pro.  multicast flow created with aes67 . and then accessing the cisco web ui and in api section , running the commands 

xConfiguration Audio Ethernet Encryption: Optional
xConfiguration Audio Ethernet SAPDiscovery Mode: On

both are accepted.

when i try sending below command , it is rejected

xStatus Audio Input Ethernet DiscoveredStream.

Could you please advise what could be causing this rejection, or if there are additional steps needed for the stream discovery?

[Jonathan Schulenberg · Accepted solution]

You need to open an SSH session for a proper CLI. It's failing in the web UI because "xStatus Audio Input Ethernet DiscoveredStream" isn't a full/proper command; it's the "starts with" of five separate commands. The CLI behavior is to show all potential matches - but the web UI expects an exact match. That's what you see in the setup guide example:

Any discovered streams will now be enumerated and are visible in:

xStatus Audio Input Ethernet DiscoveredStream

It will then report the discovered streams like this:

*s Audio Input Ethernet DiscoveredStream <DiscoveryIndex> Channels: <channels>
*s Audio Input Ethernet DiscoveredStream <DiscoveryIndex> MediaIP: "239.xxx.xxx.xxx"
*s Audio Input Ethernet DiscoveredStream <DiscoveryIndex> Name: <Stream name>
*s Audio Input Ethernet DiscoveredStream <DiscoveryIndex> OriginIP: "169.254.1.2xx"
*s Audio Input Ethernet DiscoveredStream <DiscoveryIndex> Status: "Valid offer"

---

[mrdivakar]

hi jonathan,

thannk you for the guidance  , it works well with Putty tool .and now the discovered stream command is working fine and registratin is completed, 

thank you