heplify icon indicating copy to clipboard operation
heplify copied to clipboard

Published 20 hours ago • verified publisher icon sipcapture

Heplify does not capture RTCP packets when rtcp-mux is in use

Open hamptonng opened this issue 3 years ago • 5 comments

We have two FreeSWITCH instances with a call between them (a load testing scenario), and they default to using rtcp-mux (RFC 5761).

In this case, heplify does not pass the RTCP packets for that call to the heplify server so no QoS information is recorded.

hamptonng avatar Apr 07 '22 14:04 hamptonng

Thanks for the report @hamptonng Please attach some examples or PCAP for the missed packets if you'd like this to be looked into

lmangani avatar Apr 07 '22 14:04 lmangani

ldtcall.zip

Thanks for the fast response - pcap attached.

hamptonng avatar Apr 07 '22 15:04 hamptonng

I believe a simple fix is to remove the odd port number check in decoder.go prior to correlateRTCP. Under rtcp-mux RTCP is likely to be on an even port number.

hamptonng avatar Apr 07 '22 16:04 hamptonng

@hamptonng Can you please attach your test pcap ? Unfortunately I don't see it here. In this case we will recheck your PR and test with the pcap, so we can merge or adjust. Thank you!

kYroL01 avatar Sep 30 '22 10:09 kYroL01

The pcap is in the zip file attached to the comment above on 7th April (ldtcall.zip)

hamptonng avatar Sep 30 '22 12:09 hamptonng

@hamptonng I'm sorry, I was looking for a .pcap file. Thank you - I will check and will merge once I tested.

kYroL01 avatar Sep 30 '22 12:09 kYroL01