Output device (speaker) configuration not applied

Good day,

we are in on the verge of completing the implemention for media1 backchannel with multiple decoder types.

We can currently test with MIlestone Management Client, however it looks like it does not take into account the changes of the configuration of the speaker.

When we change any of the settings we would expect the VMS to update the media1 configuration with a profile and appropriate audio decoder (output) configuration.

The VMS queries only for stream URI (`GetStreamUri`) but it is done for the same, unchanged profile, chosen in advance before during the `Add Hardware` process.

This leads to not being able to alter the config (codec, bitrate, sample rate) for push-to-talk at all and the user is left with the config set automatically by the vms.

At the same time the ONVIF Test Tool (v24.06) reports all backchannel test cases for all codecs green.

Please let us know of the following:

  1. Is this the desired behavior of the VMS ?
  2. Sometimes even the `GetStreamUri` ONVIF api is not called – why this might be the case ?
  3. If the answer to 1. is ‘yes’ then - is there anything you could guide us through to make things work correctly so that the VMS admin can use the desired PTT audio stream parameters ?

Let us know if you need any additional info to be able to address our concerns.

Best regards,

- Pawel

Milestone sys used

The described behavior is expected in case when the device does not provide the correct codec list as multiple rtpmap for the Audio Backchannel track.

Please refer to the following documents for more details:

https://doc.milestonesys.com/latest/en-US/onvifdriver/audio_in_out.htm?TocPath=Third-party%20integrations%7CONVIF%C2%AE%20drivers%7CDriver%20settings%7C_____6

https://doc.milestonesys.com/latest/en-US/onvifdriver/audio_backchannel_codec_selection.htm?TocPath=Third-party%20integrations%7CONVIF%C2%AE%20drivers%7CTechnical%20section%7C_____4