We are connecting a webrtc client (not browser) to the milestone VMS’s webrtc stream, and we see choppy video. Our analysis shows:
The WebRTC video stream generated by the Milestone XProtect VMS contains invalid RTP (Real-time Transport Protocol) timestamps. While the Session Description Protocol (SDP) specifies a clock-rate of 90,000 Hz for the video stream, the source is incorrectly generating timestamps at a much lower frequency.
RTP Timestamp Clock Rate Mismatch
In a standard H.264 WebRTC stream, the RTP timestamp must advance at the rate defined in the SDP (90,000 Hz) to ensure proper synchronization.
The Milestone source is delivering timestamps at a rate of approximately 1,000 Hz.
Because the timestamps are off by a factor of 90, the receiving client cannot correctly calculate the presentation time for the video frames.
Required Resolution
To resolve this issue on the Milestone side, the WebRTC egress component must be updated as follows:
Correct Timestamp Scaling: Update the RTP timestamp generation to ensure it scales at the 90,000 Hz clock rate required for H.264 video, rather than the current 1,000 Hz rate.
Clock-Rate Alignment: Ensure the internal clock used to generate these timestamps matches the frequency negotiated in the SDP to prevent continuous synchronization resets.
There is no feedback on this investigation yet.
If you had a support case it shouldn’t be closed until the investigation pertaining to your case is done and you get the reply. It is completely valid to have a support case for your development using Milestone’s API or SDK.
Milestone Development have created a new API Gateway that includes a fix, for now this is an experimental fix, not an official fix. Your feedback on the fix is important for us, whether it fixes the issue or not.
(Temporary experimental fix is now removed again.)
I went to install the patch that was sent over, it is 2025r2 – I am already running 2025r3 version of the API Gateway. The installer fails noting that I have a newer version running. Do you all want me to downgrade the API gateway? Is there any risk doing this during production hours? Thank you.
Milestone Development started working on creating a new API Gateway that includes the fix for 25R3. It will be also an experimental fix, not an official fix, and let me get back to you when it is ready to deliver.