Test case ID -: Media2-2-3-2 and Media2-2-3-3, Video Encoder Configurations and Configuration Options consistency validation, Frame rate mapping failure.

[anishchejarla1511]

When I am trying to test Video Encoder related functions under Media2 service as part of Profile T, while running the test case, Media2-2-3-2 and Media2-2-3-3, it is trying to check the consistency between GetVideoEncoderConfigurations and GetVideoEncoderConfigurationOptions, in the above test cases the consistency check is failing with an error message saying, frame rate limit mapping failure, I checked the responses of the above functions as well, the frame rate limit value in GetVideoEncoderConfigurations function is present in GetVideoEncoderConfigurationOptions as well but still it says frame rate mapping failure and DUT doesn't return consistent options for the configuration.

Here are the files and snippets related to the above mentioned issue-:

Request_Response_GetVideoEncoderConfigurations.txt
Request_Response_GetVideoEncoderConfigurationOptions.txt

[madhurao68]

Hi,
We're rolling out v26.06 right now and will look into your request shortly. Thanks for bearing with us!

[MariaYa0091]

Hello @anishchejarla1511,

I checked your response from device and for both GetVideoEncoderConfigurationOptionsResponse and GetVideoEncoderConfigurationsResponse you do not follow ONVIF schema.

For your responses all attributes are returned as elements.

In the following values to be added as XML attributes:

• GetVideoEncoderConfigurationOptionsResponse
  • GovLengthRange
  • MaxAnchorFrameDistance
  • FrameRatesSupported
  • ProfilesSupported
  • ConstantBitRateSupported
  • GuaranteedFrameRateSupported
• GetVideoEncoderConfigurationsResponse
  • GovLength
  • AnchorFrameDistance
  • Profile
  • GuaranteedFrameRate
  • Signed

In the case of list type (for example FrameRatesSupported) it shall be space separated list. For example: FrameRatesSupported="33 12 3".

Because of wrong format all wrongly placed elements are ignored.