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 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.
The text was updated successfully, but these errors were encountered:
hamptonng
changed the title
Heplify does not capture RTCP packets when rtp-mux is in use
Heplify does not capture RTCP packets when rtcp-mux is in use
Apr 7, 2022
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 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!
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.
The text was updated successfully, but these errors were encountered: