QOS | Data through DSS

[kishan.patel (Kishan)]

Hey Team,

We currently subscribe for data to be pushed through DSS. Our focus is on QOS data.

We quickly learned we get 3 to 4 messages per minute per person of data.
The following is an example of 1 payload that came in:

 "payload": {
    "object": {
      "uuid": "fTbjpjeXQF609+2ByHuWpA==",
      "participant": {
        "qos": [
          {
            "date_time": "2020-12-08T17:42:00Z",
            "details": {
              "jitter": "11 ms",
              "bitrate": "100 kbps",
              "latency": "71 ms",
              "max_loss": "0.0%",
              "avg_loss": "0.0%"
            },
            "type": "audio_input"
          },
          {
            "date_time": "2020-12-08T17:42:00Z",
            "details": {
              "jitter": "10 ms",
              "bitrate": "32 kbps",
              "latency": "72 ms",
              "max_loss": "0.0%",
              "avg_loss": "0.0%"
            },
            "type": "as_input"
          },
          {
            "date_time": "2020-12-08T17:42:00Z",
            "details": {
              "jitter": "10 ms",
              "bitrate": "8 kbps",
              "latency": "69 ms",
              "max_loss": "0.0%",
              "avg_loss": "0.0%"
            },
            "type": "video_input"
          }
        ],
        "user_id": "16787456"
      }
    },

Question:
What is (“type”: “as_input”) telling us here? What device, in which direction, is ‘as_input’?

This link exists but the schema information is generic and the descriptions are re-used:
https://marketplace.zoom.us/docs/api-reference/zoom-api/dashboards/dashboardmeetingparticipantqos

[will.zoom (Will)]

Hi @kishan.patel,

Good question—After checking with my team, I believe as_input is referencing screen share device.

Let me know if this helps to clarify!

Thanks,
Will