[MOVED FROM GST-P-FARSIGHT] Clarify the documentation of the "event-type" field when specifying dtmf events

This commit is contained in:
Olivier Crête 2008-10-15 16:21:50 -04:00 committed by Edward Hervey
parent 9154bb29ff
commit 918d78dd22
2 changed files with 6 additions and 2 deletions

View file

@ -64,7 +64,9 @@
* <entry>0-1</entry> * <entry>0-1</entry>
* <entry>The application uses this field to specify which of the two methods * <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 * 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> * </entry>
* </row> * </row>
* <row> * <row>

View file

@ -62,7 +62,9 @@
* <entry>0-1</entry> * <entry>0-1</entry>
* <entry>The application uses this field to specify which of the two methods * <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 * 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> * </entry>
* </row> * </row>
* <row> * <row>