Jump to: navigation, search

GVP MCP:mpc:amrwb-fmtp

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=amrwb.fmtp
 
−
|urlparameter=amrwb-fmtp
 
−
|displayname=AMR-WB FMTP
 
 
|hidden=false
 
|hidden=false
 
|default=octet-align=0 | octet-align=1
 
|default=octet-align=0 | octet-align=1
−
|valid=
 
 
|takeseffect=At start/restart
 
|takeseffect=At start/restart
 
|shortdesc=Specifies the AMR-WB SDP RTP payload configurations offered and accepted by the MCP. Set to one or more fmtp text values separated by the '|' character. The fmtp text is the same as would appear in the SDP negotiation (see RFC 4867). Each "|" separated value configures an AMR-WB payload type. There are two fmtp parameters that can be set for each payload type, octet-align and mode-set. <br><br> Setting octet-align=0 or octet-align=1 disables or enables octet align mode for the payload. <br><br> Setting mode-set restricts the AMR-WB modes for the payload. For example, setting "mode-set=0,1" only allows modes 0 and 1. If mode-set is not set, all modes are allowed unless the mode-set is restricted by the remote end. Valid modes are inclusively 0 to 8. <br><br> For example, setting this parameter to "octet-align=1" enables one payload type with octet aligned mode enabled and any mode allowed, and setting it to "octet-align=0 | octet-align=1" enables two payload types, one with bandwidth efficient mode enabled and any mode allowed, and one with octet aligned enabled and any mode allowed. <br><br> Note, the mode-set parameter can cause transcoding to be required. For example, if a prompt to be played is in AMR-WB format mode 5, but only mode 0 is allowed in the payload, a transcoder will be invoked to transcode from AMR-WB mode 5 to AMR-WB mode 0. <br><br> Some AMR-WB implementations may specify a fmtp options that are not actually activated for the payload. To work around this, the mpc.amrwb.fmtp can be set to "*". For this setting, all fmtp content in an SDP offer will be ignored and "octet-align=0" will be returned in the SDP answer. Similarly, an offer for this configuration will be set to "octet-align=0", and all fmtp content in the answer will be ignored.
 
|shortdesc=Specifies the AMR-WB SDP RTP payload configurations offered and accepted by the MCP. Set to one or more fmtp text values separated by the '|' character. The fmtp text is the same as would appear in the SDP negotiation (see RFC 4867). Each "|" separated value configures an AMR-WB payload type. There are two fmtp parameters that can be set for each payload type, octet-align and mode-set. <br><br> Setting octet-align=0 or octet-align=1 disables or enables octet align mode for the payload. <br><br> Setting mode-set restricts the AMR-WB modes for the payload. For example, setting "mode-set=0,1" only allows modes 0 and 1. If mode-set is not set, all modes are allowed unless the mode-set is restricted by the remote end. Valid modes are inclusively 0 to 8. <br><br> For example, setting this parameter to "octet-align=1" enables one payload type with octet aligned mode enabled and any mode allowed, and setting it to "octet-align=0 | octet-align=1" enables two payload types, one with bandwidth efficient mode enabled and any mode allowed, and one with octet aligned enabled and any mode allowed. <br><br> Note, the mode-set parameter can cause transcoding to be required. For example, if a prompt to be played is in AMR-WB format mode 5, but only mode 0 is allowed in the payload, a transcoder will be invoked to transcode from AMR-WB mode 5 to AMR-WB mode 0. <br><br> Some AMR-WB implementations may specify a fmtp options that are not actually activated for the payload. To work around this, the mpc.amrwb.fmtp can be set to "*". For this setting, all fmtp content in an SDP offer will be ignored and "octet-align=0" will be returned in the SDP answer. Similarly, an offer for this configuration will be set to "octet-align=0", and all fmtp content in the answer will be ignored.
 +
}}
 +
{{DraftOption}}
 +
{{PubExtended}}
 +
{{DraftExtended}}
 +
{{OptionCreate
 +
|component=GVP_MCP
 +
|compshort=GVP_MCP
 +
|prodshort=GVP
 +
|configobject=Application
 
|section=mpc
 
|section=mpc
−
|urlsection=mpc
+
|parameter=amrwb.fmtp
−
|groupid=grpMedia
 
−
|groupname=Media Processing
 
−
|format=string
 
−
|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 02:45, October 31, 2016


View in ref guide.

Edit this option          Publish this option          Clear draft content


Published Option

amrwb.fmtp

Default Value: octet-align=0 | octet-align=1
Valid Values: <parameter=value>[|<parameter=value>]*
Changes Take Effect: At start/restart


Specifies the AMR-WB SDP RTP payload configurations offered and accepted by the MCP. Set to one or more fmtp text values separated by the '|' character. The fmtp text is the same as would appear in the SDP negotiation (see RFC 4867). Each "|" separated value configures an AMR-WB payload type. There are two fmtp parameters that can be set for each payload type, octet-align and mode-set.

Setting octet-align=0 or octet-align=1 disables or enables octet align mode for the payload.

Setting mode-set restricts the AMR-WB modes for the payload. For example, setting "mode-set=0,1" only allows modes 0 and 1. If mode-set is not set, all modes are allowed unless the mode-set is restricted by the remote end. Valid modes are inclusively 0 to 8.

For example, setting this parameter to "octet-align=1" enables one payload type with octet aligned mode enabled and any mode allowed, and setting it to "octet-align=0 | octet-align=1" enables two payload types, one with bandwidth efficient mode enabled and any mode allowed, and one with octet aligned enabled and any mode allowed.

Note, the mode-set parameter can cause transcoding to be required. For example, if a prompt to be played is in AMR-WB format mode 5, but only mode 0 is allowed in the payload, a transcoder will be invoked to transcode from AMR-WB mode 5 to AMR-WB mode 0.

Some AMR-WB implementations may specify a fmtp options that are not actually activated for the payload. To work around this, the mpc.amrwb.fmtp can be set to "*". For this setting, all fmtp content in an SDP offer will be ignored and "octet-align=0" will be returned in the SDP answer. Similarly, an offer for this configuration will be set to "octet-align=0", and all fmtp content in the answer will be ignored.

Draft Option

No draft option

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