Describe the bug
A POOR connection quality event was received for the user, even though the connection is stable and the signal strength is good.
Check Log
connection_quality {
updates {
participant_sid: "PA_FfdABigXhCBy"
score: 1.8044316
}
updates {
participant_sid: "PA_4p9vwC46JBoe"
quality: EXCELLENT
quality_value: 2
score: 4.1391697
}
updates {
participant_sid: "PA_V8G9o9Bmv9iY"
quality: GOOD
quality_value: 1
score: 3.554451
}
updates {
participant_sid: "PA_xViiYi7Lmcsy"
quality: EXCELLENT
quality_value: 2
score: 4.0442033
}
updates {
participant_sid: "PA_GZqpaYq6uGpH"
quality: EXCELLENT
quality_value: 2
score: 4.5
}
updates {
participant_sid: "PA_ob5xGhaF9aLx"
quality: EXCELLENT
quality_value: 2
score: 4.492146
}
updates {
participant_sid: "PA_mowUo6HFoW9w"
quality: EXCELLENT
quality_value: 2
score: 4.3083653
}
updates {
participant_sid: "PA_YzgoUVPpwqRC"
quality: EXCELLENT
quality_value: 2
score: 4.5
}
updates {
participant_sid: "PA_oiW4HqE9UXfr"
quality: GOOD
quality_value: 1
score: 2.9030166
}
}
quality and quality_value keyword not coming above response the livekit sdk return to the POOR quality state
To Reproduce
Steps to reproduce the behavior:
- during the call checking connection quality response
Expected behavior
when Connection is stable and strength that time POOR state should not come.
Screenshots
NIL
Device Info:
Additional context
I want to know why this keywords are missing
quality and quality_value