Jump to: navigation, search

GVP MCP:mpc:rtp-dejitter-maxgap

 
(4 intermediate revisions by 2 users not shown)
Line 4: Line 4:
 
|valid=rtp.dejitter.maxgap must be an integer that is greater than or equal to 0 and less than or equal to 60000.
 
|valid=rtp.dejitter.maxgap must be an integer that is greater than or equal to 0 and less than or equal to 60000.
 
|takeseffect=At start/restart
 
|takeseffect=At start/restart
|shortdesc=First packet determination based on the wall time gap (in milliseconds) between the RTP packets. The packet arriving after this gap will be treated equivalent by the de-jitter function as the RTP packet with the marker-bit set. If 0, disables determination based on gap.
+
|shortdesc=
 +
First packet determination based on the wall time gap (in milliseconds) between the RTP packets. The packet arriving after this gap will be treated equivalent by the de-jitter function as the RTP packet with the marker-bit set. If 0, disables determination based on gap.
 +
 
 
}}
 
}}
 
{{DraftOption}}
 
{{DraftOption}}

Latest revision as of 15:43, June 29, 2020



View in ref guide.

Edit this option          Publish this option          Clear draft content


Published Option

rtp.dejitter.maxgap

Default Value: 2000
Valid Values: rtp.dejitter.maxgap must be an integer that is greater than or equal to 0 and less than or equal to 60000.
Changes Take Effect: At start/restart


First packet determination based on the wall time gap (in milliseconds) between the RTP packets. The packet arriving after this gap will be treated equivalent by the de-jitter function as the RTP packet with the marker-bit set. If 0, disables determination based on gap.

Draft Option

No draft option

This page was last edited on June 29, 2020, at 15:43.
Comments or questions about this documentation? Contact us for support!