Jump to: navigation, search

GVP MCP:mpc:rtp-dejitter-maxgap

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=For internal use.
+
|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}}
Line 16: Line 16:
 
|section=mpc
 
|section=mpc
 
|parameter=rtp.dejitter.maxgap
 
|parameter=rtp.dejitter.maxgap
 +
|groupid=grpMedia
 +
|groupname=Media Processing
 +
|format=numeric
 +
|displayname=RTP De-Jitter Max Gap
 
}}
 
}}
  
 
[[Category:GVP_MCP_options]]
 
[[Category:GVP_MCP_options]]

Revision as of 04:02, February 24, 2017


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

Comments or questions about this documentation? Contact us for support!