From 145d61d3063fcc8fa5d28621429bf66fc757578c Mon Sep 17 00:00:00 2001 From: Peter Saint-Andre Date: Fri, 30 May 2008 16:11:40 +0000 Subject: [PATCH] 0.10 git-svn-id: file:///home/ksmith/gitmigration/svn/xmpp/trunk@1895 4b5297f7-1745-476d-ba37-a9c6900126ab --- xep-0181.xml | 53 ++++++++++++++++++++++++++++++++++++---------------- 1 file changed, 37 insertions(+), 16 deletions(-) diff --git a/xep-0181.xml b/xep-0181.xml index a23394d6..3264ddae 100644 --- a/xep-0181.xml +++ b/xep-0181.xml @@ -20,9 +20,15 @@ - TO-BE-ASSIGNED + NOT_YET_ASSIGNED &stpeter; &seanegan; + + 0.10 + 2008-05-30 + psa +

Simplified syntax by removing button-down and button-up actions (all actions are assumed to be button-down) and setting 100ms default value for duration.

 + 0.9 2008-04-18 @@ -92,16 +98,39 @@

The format for the representation of DTMF events in XMPP is as follows &NSNOTE;:

]]> -

The <dtmf/> element SHOULD possess an 'action' attribute, the value of which MUST be either "button-up" or "button-down" (specifying whether the button is being depressed or released). This enables DTMF tones to be reconstructed in real time. If the 'action' attribute is not included, the recipient MUST assume that the action is a "button-down" event.

-

Unless the 'action' attribute has a value of "button-up", the <dmtf/> element MUST possess a 'code' attribute that specifies the tone to be generated. The value of the 'code' attribute SHOULD be one the following characters: 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, #, and * (however, the characters A, B, C, and D MAY be sent as well Although A, B, C, and D were originally defined as part of DTMF, they were never deployed to telephony consumers and were used only for control purposes at private branch exchanges (PBXs) and central office operator stations; however, they are used in certain non-telephony applications of DTMF, such as ham radio.).

-

The OPTIONAL 'duration' attribute specifies indicates the duration of the event, in milliseconds, expressed as an unsigned integer. The receiver SHOULD ignore the event if the 'duration' value is zero. If the 'duration' attribute is not included and the event is explicitly or implicitly a "button-down" event, the recipient MUST assume that the event expires after a reasonable timeout (100 milliseconds is RECOMMENDED) or when a "button-up" event is received, whichever comes first.

-

The OPTIONAL 'volume' attribute specifies the power level of the tone, expressed in dBm0 after dropping the sign. Power levels range from 0 to -63 dBm0. Thus, larger values denote lower volume.

-

The <dtmf> element SHOULD be sent as the payload of a Jingle session-info message as illustrated in the following example &NSNOTE;.

+

The <dmtf/> element MUST be empty.

+

The attributes of the <dmtf/> element are as follows.

+ + + + + + + + + + + + + + + + + + + + + + + + + +
AttributeDefinitionExampleInclusion
codeThe tone to be generated. The value of the 'code' attribute SHOULD be one the following characters: 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, #, and * (however, the characters A, B, C, and D MAY be sent as well Although A, B, C, and D were originally defined as part of DTMF, they were never deployed to telephony consumers and were used only for control purposes at private branch exchanges (PBXs) and central office operator stations; however, they are used in certain non-telephony applications of DTMF, such as ham radio.).6REQUIRED
durationThe duration of the event, in milliseconds, expressed as a non-negative integer. The receiver SHOULD ignore the event if the value is zero. The default value is 100 (i.e., 100ms).400RECOMMENDED
volumeThe power level of the tone, expressed in dBm0 after dropping the sign. Power levels range from 0 to -63 dBm0. Thus, a larger value denotes a lower volume.37OPTIONAL
+

The <dtmf> element SHOULD be sent as the payload of a Jingle session-info message as illustrated in the following example.

- - - - - - - - - +