Skip to content

Homer UI does not display Jitter/Loss/MOS stats #612

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
vladpaiu opened this issue May 20, 2025 · 2 comments
Open

Homer UI does not display Jitter/Loss/MOS stats #612

vladpaiu opened this issue May 20, 2025 · 2 comments
Assignees
Labels
help wanted Extra attention is needed test needed something to be tested

Comments

@vladpaiu
Copy link

vladpaiu commented May 20, 2025

Hello,

I'm using heplify and homer-app ( 1.5.3 ) and have rtpengine replicating RTCP ( coming in from some webrtc-based apps ) to heplify.
I do see data in the hep_proto_5_default table, I have both 200 and 201 rtcp in there, pasting 2 sample records :

homer_data=> select * from hep_proto_5_default where sid='B3FDDCE8-B497-4C39-A43F-D58353DC427B';
id | sid | create_date |
protocol_header
| data_header |
raw

-------+--------------------------------------+-------------------------------+---------------------------------------------------------------------------------------------
------+---------------------------------+-----------------------------------------------------------------------------------------------------------------------------------
34641 | B3FDDCE8-B497-4C39-A43F-D58353DC427B | 2025-05-07 05:20:34.563883+00 | {"dstIp": "10.40.1.57", "srcIp": "1.2.3.4", "dstPort": 21678, "srcPort": 52222, "proto
col": 17, "captureId": "10", "payloadType": 5, "timeSeconds": 1746595234, "timeUseconds": 563883, "correlation_id": "B3FDDCE8-B497-4C39-A43F-D58353DC427B", "protocolFamily"
: 2} | {"node": "10", "proto": "rtcp"} | { "sender_information":{"ntp_timestamp_sec":3955584034,"ntp_timestamp_usec":2395977570,"octets":5605,"rtp_timestamp":1980108676, "
packets":84},"ssrc":4242424910,"type":200,"report_count":0,"report_blocks":[],"sdes_report_count":1,"sdes_information": [ {"sdes_chunk_ssrc":4242424910,"type":1,"text":"RGO
UmlyKT1Xaj92/"}] }
34642 | B3FDDCE8-B497-4C39-A43F-D58353DC427B | 2025-05-07 05:20:34.552278+00 | {"dstIp": "10.40.1.57", "srcIp": "4.3.2.1", "dstPort": 21678, "srcPort": 52222, "proto
col": 17, "captureId": "10", "payloadType": 5, "timeSeconds": 1746595234, "timeUseconds": 552278, "correlation_id": "B3FDDCE8-B497-4C39-A43F-D58353DC427B", "protocolFamily"
: 2} | {"node": "10", "proto": "rtcp"} | { "ssrc":4242424910,"type":201,"report_count":1,"report_blocks":[{"source_ssrc":3213144602,"highest_seq_no":10343,"fraction_lost":
0,"ia_jitter":366,"packets_lost":0,"lsr":0,"dlsr":0}] }

But in the UI, in the QoS tab, I can only see packets and octets for that specific callid, but not jitter & loss & mos. It's like the app is only managing to interpret RTCP 200, but not RTCP 201.

Any ideas about it ?

Copy link

Your report is appreciated. Please star this repository to motivate its developers! ⭐

@kYroL01 kYroL01 added help wanted Extra attention is needed test needed something to be tested labels May 20, 2025
@rita7lopes
Copy link

Hey @vladpaiu,
We were able to replicate the issue in our lab.
This is a UI bug; the information is all there, but the UI is not picking it up.

Whenever the fix is ready, we will let you know.

Thank you!!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Extra attention is needed test needed something to be tested
Projects
None yet
Development

No branches or pull requests

4 participants