Jump to: navigation, search

GVP MCP:mpc:tts-persistdympayfmtpair

Line 2: Line 2:
 
|hidden=true
 
|hidden=true
 
|default=1
 
|default=1
|valid=
+
|valid=Choose between: 0 or 1
 
|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 for TTS sessions. 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 for TTS sessions. 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}}
 +
  
 
{{PubExtended}}
 
{{PubExtended}}
 +
 
{{DraftExtended}}
 
{{DraftExtended}}
 +
  
 
{{OptionCreate
 
{{OptionCreate

Revision as of 20:19, November 23, 2017




View in ref guide.

Edit this option          Publish this option          Clear draft content


Published Option

tts.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 for MRCP TTS sessions. 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

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