Skip to content
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

Feature request: translate RTP jitter units from FreeSwitch to MS. #516

Open
garryavx opened this issue Jan 13, 2022 · 4 comments
Open

Feature request: translate RTP jitter units from FreeSwitch to MS. #516

garryavx opened this issue Jan 13, 2022 · 4 comments

Comments

@garryavx
Copy link

So, as I understand it the RTP units are displayed in homer as freeswitch gives them: 1/sampling rate. meaning that if I get a value of 190 from FS, and I'm using 722/16000, my jitter is 190/16000hz = ~12ms.

would be cool if homer would do that math for me.

I get my RTCP data from Hepipe.js (I cannot use the capture agent as I use TLS for everything in and out).
I took a look at the data it's getting from the ESL and the jitter and sample rate are both reported. I was hoping for an option to have the translation done and homer present the jitter value in ms.

here's an example from my hepipe log:
{ name: 'SSRC', value: 'a03ba3fa' }, { name: 'NTP-Most-Significant-Word', value: '3851097186' }, { name: 'NTP-Least-Significant-Word', value: '489978459' }, { name: 'RTP-Timestamp', value: '655110746' }, { name: 'Sender-Packet-Count', value: '1937' }, { name: 'Octect-Packet-Count', value: '123145' }, { name: 'Last-RTP-Timestamp', value: '655111706' }, { name: 'RTP-Rate', value: '48000' }, { name: 'Capture-Time', value: '1642108386138833' }, { name: 'Source0-SSRC', value: '19ea7842' }, { name: 'Source0-Fraction', value: '0' }, { name: 'Source0-Lost', value: '0' }, { name: 'Source0-Loss-Avg', value: '0' }, { name: 'Source0-Highest-Sequence-Number-Received', value: '9944' }, { name: 'Source0-Jitter', value: '0' }, { name: 'Source0-LSR', value: '341924976' }, { name: 'Source0-DLSR', value: '47193' }, { name: 'Rtt0-Avg', value: '0.034473' }

@garryavx
Copy link
Author

ah, it does occur to me that an alternative solution is to find a way to have the capture agent decrypt the tls traffic with the cert

@lmangani
Copy link
Member

@garryavx that's impossible with properly configured TLS - the code supports this for RSA and is a dead end, as it should

@lmangani
Copy link
Member

@garryavx i would suggest patching up hepipe to produce new fields with the calculations - or replacing the values with the ones you're proposing. Once that works reliably, we can consider ways to introduce it into the codebase as a generic.

@garryavx
Copy link
Author

hey I might actually be able to do that. homer is intimidating but the hepipe.js stuff looks more approachable. I'll see what I can do

garryavx added a commit to garryavx/hepipe.js that referenced this issue Jan 14, 2022
I added a variable called msjitter that takes the RTP jitter unit and the RTP_Rate, and converts to seconds, then to MS.

This will need to be added into homer separately, 
sipcapture/homer#516
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants