Consider creating an API for mobile/web clients to upload QoS reports that can then be organized and returned by Restcomm-Connect. Related to RestComm/webrtcomm#53
jean.deruelle [19:09]
@antonis: one thing occured to me
[19:09]
can we get some insights from the getstats API
[19:09]
to gather more intel
[19:10]
on audio, media, where they are connected
[19:10]
etc
[19:10]
kind of create a debug report
[19:10]
that they can send
[19:10]
so we can analyze
[19:22]
we could give a report through an API
[19:22]
they would call
[19:22]
and then they would be responsible for sending that somewhere
antonis [19:23]
the problem is that right now there is no report through API. The API returns a dictionary with values that the App developer would need to use
jean.deruelle [19:23]
Shall we create an issue in github for restcomm
[19:23]
to agreggate that data per call
[19:24]
can we think of creating a per call stats report
[19:24]
API
[19:24]
that can be sent over SIP or HTTP to REstcomm
[19:24]
and get correlated and stored with the call
[19:24]
so we can start to gather more and more QoS data per call
[19:25]
this would need a lot of brainstorming
[19:25]
but we should start to do that
[19:25]
we could also add QoS to RMS
[19:25]
with Mean Opinion score
[19:25]
that gets added as well
[19:25]
and we are able to troubleshoot with data from both sides of the call
[19:26]
but let's start to think about that and create an issue in both restcomm and restcomm-web-sdk
antonis [19:26]
:thumbsup:
jean.deruelle [19:27]
on how we can have per call stats
[19:27]
in Restcomm
Consider creating an API for mobile/web clients to upload QoS reports that can then be organized and returned by Restcomm-Connect. Related to RestComm/webrtcomm#53