mirror of
https://gitlab.freedesktop.org/gstreamer/gstreamer.git
synced 2024-12-24 09:10:36 +00:00
[MOVED FROM GST-P-FARSIGHT] Clarify the documentation of the "event-type" field when specifying dtmf events
This commit is contained in:
parent
9154bb29ff
commit
918d78dd22
2 changed files with 6 additions and 2 deletions
|
@ -64,7 +64,9 @@
|
|||
* <entry>0-1</entry>
|
||||
* <entry>The application uses this field to specify which of the two methods
|
||||
* specified in RFC 2833 to use. The value should be 0 for tones and 1 for
|
||||
* named events. This element is only capable of generating named events.
|
||||
* named events. Tones are specified by their frequencies and events are specied
|
||||
* by their number. This element can only take events as input. Do not confuse
|
||||
* with "method" which specified the output.
|
||||
* </entry>
|
||||
* </row>
|
||||
* <row>
|
||||
|
|
|
@ -62,7 +62,9 @@
|
|||
* <entry>0-1</entry>
|
||||
* <entry>The application uses this field to specify which of the two methods
|
||||
* specified in RFC 2833 to use. The value should be 0 for tones and 1 for
|
||||
* named events. This element is only capable of generating named events.
|
||||
* named events. Tones are specified by their frequencies and events are specied
|
||||
* by their number. This element can only take events as input. Do not confuse
|
||||
* with "method" which specified the output.
|
||||
* </entry>
|
||||
* </row>
|
||||
* <row>
|
||||
|
|
Loading…
Reference in a new issue