Add audioUpstreamLevel and audioDownstreamLevel to ClientReportMetric

[hungns2010]

Issue #: N/A

Description of changes:

• Add audioUpstreamLevel and audioDownstreamLevel to ClientMetricReport.
• audioUpstreamLevel will be collected through: https://developer.mozilla.org/en-US/docs/Web/API/RTCAudioSourceStats. This Stats doesn't have ssrc field so we need to collect it through GlobalMetricReport.
• 'audioDownstreamLevel` will be collected through: https://developer.mozilla.org/en-US/docs/Web/API/RTCInboundRtpStreamStats

Testing: npm run build:release

Can these tested using a demo application? Please provide reproducible step-by-step instructions.

• Add a console.log(metric) after line 635 of ClientMetricReport.ts file. build the serverless demo app: https://7vkcow9r86.execute-api.us-east-1.amazonaws.com/Prod/
• test the meeting in Chrome, Firefox, Safari, IOS Safari.
• metric in Firefox:

audioDecoderLoss: 0
audioDownstreamJitterMs: 1
audioDownstreamLevel: 0.0032654805139316996
audioPacketLossPercent: 0
audioPacketsReceived: 49
audioPacketsReceivedFractionLoss: 0
audioPacketsSent: 48
audioSpeakerDelayMs: 67.45098039215675
audioUpstreamJitterMs: 19
audioUpstreamLevel: NaN
audioUpstreamRoundTripTimeMs: 14
availableIncomingBitrate: NaN
availableOutgoingBitrate: NaN
currentRoundTripTimeMs: NaN
nackCountReceivedPerSecond: 0
videoPacketSentPerSecond: 0
videoUpstreamBitrate: 0

• metric in Safari:

audioDecoderLoss: 0
audioDownstreamJitterMs: 0
audioDownstreamLevel: 0.00015259254737998596
audioPacketLossPercent: 0
audioPacketsReceived: 50
audioPacketsReceivedFractionLoss: 0
audioPacketsSent: 50
audioSpeakerDelayMs: 29.39999999999994
audioUpstreamJitterMs: 19.979166666666664
audioUpstreamLevel: NaN
audioUpstreamRoundTripTimeMs: 8
availableIncomingBitrate: NaN
availableOutgoingBitrate: 300000
currentRoundTripTimeMs: 9
nackCountReceivedPerSecond: 0
videoPacketSentPerSecond: 0
videoUpstreamBitrate: 0

• metric in Chrome:

audioDecoderLoss: 0,
audioDownstreamJitterMs: 0,
audioDownstreamLevel: 0.00003051850947599719,
audioPacketLossPercent: 0,
audioPacketsReceived: 50,
audioPacketsReceivedFractionLoss: 0,
audioPacketsSent: 50,
audioSpeakerDelayMs: 35,
audioUpstreamJitterMs: 19.979,
audioUpstreamLevel: 0.010071108127079073,
audioUpstreamRoundTripTimeMs: 9.781,
availableIncomingBitrate: NaN,
availableOutgoingBitrate: 300000,
currentRoundTripTimeMs: 11,
nackCountReceivedPerSecond: 0,
videoPacketSentPerSecond: 0,
videoUpstreamBitrate: 0

• metric in IOS Safari:

audioDecoderLoss: 0
audioDownstreamJitterMs: 1
audioDownstreamLevel: 0.00003051850947599719
audioPacketLossPercent: 0
audioPacketsReceived: 50
audioPacketsReceivedFractionLoss: 0
audioPacketsSent: 50
audioSpeakerDelayMs: 45.80000000000291
audioUpstreamJitterMs: 20
audioUpstreamLevel: NaN
audioUpstreamRoundTripTimeMs: 62
availableIncomingBitrate: NaN
availableOutgoingBitrate: 2502188
currentRoundTripTimeMs: 48
nackCountReceivedPerSecond: 0
videoPacketSentPerSecond: 143
videoUpstreamBitrate: 1276176

Checklist:

1. Have you successfully run npm run build:release locally? Yes

2. Do you add, modify, or delete public API definitions? If yes, has that been reviewed and approved? No

3. Do you change the wire protocol, e.g. the request method? If yes, has that been reviewed and approved? No

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

[ltrung]

Does all browser support this new metric? Can you link the source? Seem like it only worked in Chrome. Can you update your testing instructions that you have tested in FF and Safari (including mobile).

[hungns2010]

Does all browser support this new metric? Can you link the source? Seem like it only worked in Chrome. Can you update your testing instructions that you have tested in FF and Safari (including mobile).

Updated the links in the details and will provide the serverless app + instructions for test later.