You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are getting SEVERE Endpoint.findAudioSourceProps#899: No properties found for SSRC 478973860. error logs and are not sure if everything is fine, since people are having various problems like sound is often missing out without any particular reason.
Current behavior
This log entry occurs pretty often. We recently had a pretty big conference with over 300 people and we saw 70 thousands entries with this "no propertries found for SSRC" error.
Expected Behavior
No error.
Possible Solution
We are not aware of them.
Steps to reproduce
No specific steps, we are getting this randomly.
Environment details
Huge K8S deploy based on community helm chart, we are currently using build 9779.
We turned FINER logs on one of our JVB pods and was able to capture full log with those errors: conf-redacted.txt
IP and some IDs was replaced by random values, but we saved the structure of log.
@bgrozev I briefly wrote about this problem there: #2269.
The text was updated successfully, but these errors were encountered:
Description
We are getting SEVERE
Endpoint.findAudioSourceProps#899: No properties found for SSRC 478973860.
error logs and are not sure if everything is fine, since people are having various problems like sound is often missing out without any particular reason.Current behavior
This log entry occurs pretty often. We recently had a pretty big conference with over 300 people and we saw 70 thousands entries with this "no propertries found for SSRC" error.
Expected Behavior
No error.
Possible Solution
We are not aware of them.
Steps to reproduce
No specific steps, we are getting this randomly.
Environment details
Huge K8S deploy based on community helm chart, we are currently using build 9779.
We turned FINER logs on one of our JVB pods and was able to capture full log with those errors:
conf-redacted.txt
IP and some IDs was replaced by random values, but we saved the structure of log.
@bgrozev I briefly wrote about this problem there: #2269.
The text was updated successfully, but these errors were encountered: