03-12-2013, 03:49 AM
Hi,
I work for Octasic, a Canadian company that offer hardware/software solutions for MCU. One of our clients have some troubles with the VP530 yealink phone when doing a video conference (h.264 or h.263). After investigation, we noticed that the phone average fps is about 20 fps but continue to rtp time stamp the frames at 30 fps (increment 3000 on a clock of 90000 khz on the rtp header).this create a big drift between the RTP time stamp and the frame receiving time and make it impossible on the decoder end point (Octasic equipment) to dejitters the received stream from the yealink VP530 as the RTP time stamp is erroneous and the increment do not correspond to the real frame rate.
Waiting for an update and an ETA of the fix release from your side.
Regards.
I work for Octasic, a Canadian company that offer hardware/software solutions for MCU. One of our clients have some troubles with the VP530 yealink phone when doing a video conference (h.264 or h.263). After investigation, we noticed that the phone average fps is about 20 fps but continue to rtp time stamp the frames at 30 fps (increment 3000 on a clock of 90000 khz on the rtp header).this create a big drift between the RTP time stamp and the frame receiving time and make it impossible on the decoder end point (Octasic equipment) to dejitters the received stream from the yealink VP530 as the RTP time stamp is erroneous and the increment do not correspond to the real frame rate.
Waiting for an update and an ETA of the fix release from your side.
Regards.