Jump to: navigation, search

GVP MCP:mpc:rtp-maxrtppacketsize

m (1 revision imported)
Line 1: Line 1:
−
----
+
{{PubOption
−
__NOTOC__
 
−
 
 
−
<!-- ==================== -->
 
−
<!-- DO NOT EDIT -->
 
−
=Published=
 
−
{{Optionstmp
 
−
|internalformid=1 (DO NOT EDIT THIS VALUE)
 
−
|fromxml=true
 
−
|docstatus=Published
 
−
|fromxml=true
 
−
|parameter=rtp.maxrtppacketsize
 
−
|urlparameter=rtp-maxrtppacketsize
 
−
|displayname=Maximum RTP Packet Size
 
 
|hidden=false
 
|hidden=false
 
|default=0
 
|default=0
Line 18: Line 5:
 
|takeseffect=At start/restart
 
|takeseffect=At start/restart
 
|shortdesc=Specifies the maximum size of RTP packets that are sent from the platform in bytes. This also controls the maximum size of the SRTP packets being sent. If 0 is specified, there is no limit - unless internal buffer specified by rtp.audiobuffersize or rtp.videobuffersize runs out of space. Note that for SRTP, huge packet sizes (above 80KB which is greater than the typical 1500 MTU limit) may cause SRTP encryption errors before being sent out. If the problem is encountered for very large video packets, it can be worked around by negotiating lower level/bitrate or by leveraging codec specific transport mechanisms (e.g. packetization-mode=1 SDP fmtp for H264).
 
|shortdesc=Specifies the maximum size of RTP packets that are sent from the platform in bytes. This also controls the maximum size of the SRTP packets being sent. If 0 is specified, there is no limit - unless internal buffer specified by rtp.audiobuffersize or rtp.videobuffersize runs out of space. Note that for SRTP, huge packet sizes (above 80KB which is greater than the typical 1500 MTU limit) may cause SRTP encryption errors before being sent out. If the problem is encountered for very large video packets, it can be worked around by negotiating lower level/bitrate or by leveraging codec specific transport mechanisms (e.g. packetization-mode=1 SDP fmtp for H264).
 +
}}
 +
{{DraftOption}}
 +
{{PubExtended}}
 +
{{DraftExtended}}
 +
{{OptionCreate
 +
|component=GVP_MCP
 +
|compshort=GVP_MCP
 +
|prodshort=GVP
 +
|configobject=Application
 
|section=mpc
 
|section=mpc
−
|urlsection=mpc
+
|parameter=rtp.maxrtppacketsize
−
|groupid=grpMedia
 
−
|groupname=Media Processing
 
−
|format=numeric
 
−
|prodshort=GVP
 
−
|component=GVP_MCP
 
−
|compshort=MediaControlPlatform
 
−
}}
 
−
[[Category:GVP_MCP_options]]
 
−
 
 
−
<!-- DO NOT EDIT -->
 
−
<!-- ==================== -->
 
−
 
 
−
==Extended Description==
 
−
 
 
−
{{Extended
 
−
|internalformid=1 (DO NOT EDIT THIS VALUE)
 
−
|docstatus=
 
−
|mandatory=
 
−
|introduced=
 
−
|modified=
 
−
|discontinued=
 
−
|feature=
 
−
|relatedoptions=
 
−
|relatedlinks=
 
−
|configobject=
 
−
|moredesc=
 
 
}}
 
}}
  
−
=Draft=
+
[[Category:GVP_MCP_options]]
−
 
 
−
{{Optionstmp
 
−
|internalformid=2 (DO NOT EDIT THIS VALUE)
 
−
|docstatus=
 
−
|parameter=
 
−
|displayname=
 
−
|hidden=
 
−
|default=
 
−
|valid=
 
−
|takeseffect=
 
−
|shortdesc=
 
−
|section=
 
−
|groupid=
 
−
|groupname=
 
−
|format=
 
−
|prodshort=
 
−
}}
 
−
 
 
−
==Extended Description==
 
−
 
 
−
{{Extended
 
−
|internalformid=2 (DO NOT EDIT THIS VALUE)
 
−
|docstatus=
 
−
|mandatory=
 
−
|introduced=
 
−
|modified=
 
−
|discontinued=
 
−
|feature=
 
−
|relatedoptions=
 
−
|relatedlinks=
 
−
|configobject=
 
−
|moredesc=
 
−
}}
 

Revision as of 03:07, October 31, 2016


View in ref guide.

Edit this option          Publish this option          Clear draft content


Published Option

rtp.maxrtppacketsize

Default Value: 0
Valid Values: mpc.rtp.maxrtppacketsize must be an integer that is greater than or equal to 0 and less than or equal to the maximum integer as defined by the Genesys Administrator Help.
Changes Take Effect: At start/restart


Specifies the maximum size of RTP packets that are sent from the platform in bytes. This also controls the maximum size of the SRTP packets being sent. If 0 is specified, there is no limit - unless internal buffer specified by rtp.audiobuffersize or rtp.videobuffersize runs out of space. Note that for SRTP, huge packet sizes (above 80KB which is greater than the typical 1500 MTU limit) may cause SRTP encryption errors before being sent out. If the problem is encountered for very large video packets, it can be worked around by negotiating lower level/bitrate or by leveraging codec specific transport mechanisms (e.g. packetization-mode=1 SDP fmtp for H264).

Draft Option

No draft option

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