Jump to: navigation, search

GVP MCP:mpc:persistdympayfmtpair
 
(6 intermediate revisions by 2 users not shown)
Line 5: Line 5:
 
|takeseffect=Immediately
 
|takeseffect=Immediately
 
|shortdesc=With regards to RFC3264, a history of mappings from payload to format per m-line should be maintained for a session. This is to ensure a dynamic payload assigned to a particular format per m-line will not be reused for a different format when given a reINVITE and asked for an offer. When enabled, the aforementioned behavior will be performed. Note that a given reINVITE with an offer will be responded with regards to, if any, the given dynamic payloads, not the maintained payloads, due to backward-compatibility. When disabled, the legacy GVP method, where history is not remembered, will be used.
 
|shortdesc=With regards to RFC3264, a history of mappings from payload to format per m-line should be maintained for a session. This is to ensure a dynamic payload assigned to a particular format per m-line will not be reused for a different format when given a reINVITE and asked for an offer. When enabled, the aforementioned behavior will be performed. Note that a given reINVITE with an offer will be responded with regards to, if any, the given dynamic payloads, not the maintained payloads, due to backward-compatibility. When disabled, the legacy GVP method, where history is not remembered, will be used.
 +
 
}}
 
}}
 
{{DraftOption}}
 
{{DraftOption}}

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



View in ref guide.

Edit this option          Publish this option          Clear draft content


Published Option

persistdympayfmtpair

Default Value: 1
Valid Values: Choose between: 0 or 1
Changes Take Effect: Immediately


With regards to RFC3264, a history of mappings from payload to format per m-line should be maintained for a session. This is to ensure a dynamic payload assigned to a particular format per m-line will not be reused for a different format when given a reINVITE and asked for an offer. When enabled, the aforementioned behavior will be performed. Note that a given reINVITE with an offer will be responded with regards to, if any, the given dynamic payloads, not the maintained payloads, due to backward-compatibility. When disabled, the legacy GVP method, where history is not remembered, will be used.

Draft Option

No draft option

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