User reports/suspects RTP statistics in MGCP reports are broken
A user reports that the RTP statistics (number of lost packets, ...) reported at the end of the conversation are broken. They were looking at the MGCP reports, so it could still be that RTCP is correct but MGCP wrong.
Let's try to test this manually and think of how we can create a test case about this kind of behavior.
- Status changed from New to In Progress
- % Done changed from 0 to 20
I have done some tests where I intentionally drop RTP frames regualry. The number of intentionally dropped frames matches the number in the statistics. Some more information about the error behavior and the affected values would be very helpful.