diff --git a/xep-0181.xml b/xep-0181.xml index e1b1ecd0..b4340528 100644 --- a/xep-0181.xml +++ b/xep-0181.xml @@ -20,9 +20,15 @@ - jingle-dtmf + TO BE ASSIGNED &stpeter; &seanegan; + + 0.5 + 2006-12-21 + psa +

Defined schema for error namespace; modified spec to use provisional namespace before advancement to Draft (per XEP-0053).

 + 0.4 2006-10-31 @@ -66,17 +72,17 @@ ]]>

The <dtmf/> element SHOULD possess one 'action' attribute, which MUST be either "button-up" or "button-down", specifying whether the button is being depressed or released. This allows DTMF tones to be reconstructed in real-time. If the 'action' attribute is not included, the recipient MUST assume this to be a "button-down" event, and imply a "button-up" event after a reasonable timeout (100 milliseconds is RECOMMENDED) or when another DMTF event is received.

Unless, the 'action' attribute is '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 <dtmf> element SHOULD be sent as the payload of a Jingle content-info message as illustrated in the following example.

+

The <dtmf> element SHOULD be sent as the payload of a Jingle content-info message as illustrated in the following example. (See Protocol Namespaces regarding issuance of a permanent namespace.)

- - @@ -99,11 +105,11 @@ to='ivr.shakespeare.lit' id='dtmf2' type='set'> - - + ]]> @@ -123,15 +129,15 @@ type='error'> - + ]]> -

If an entity supports Jingle DTMF (which natively includes sending of DTMF in the XMPP signalling channel), it MUST return a &xep0030; feature of "http://jabber.org/protocol/jingle/info/dtmf" in response to service discovery information requests.

-

If an entity also supports sending of DTMF in the content channel, it MUST also return a service discovery feature of "http://jabber.org/protocol/jingle/info/dtmf#rtp" in response to service discovery information requests.

+

If an entity supports Jingle DTMF (which natively includes sending of DTMF in the XMPP signalling channel), it MUST return a &xep0030; feature of "http://www.xmpp.org/extensions/xep-0181.html#ns" in response to service discovery information requests.

+

If an entity also supports sending of DTMF in the content channel, it MUST also return a service discovery feature of "http://www.xmpp.org/extensions/xep-0181.html#ns-rtp" in response to service discovery information requests.

 @@ -143,11 +149,11 @@ - -

The ®ISTRAR; shall include 'http://jabber.org/protocol/jingle/info/dtmf' in its registry of protocol namespaces.

+ +

Until this specification advances to a status of Draft, its associated namespaces shall be "http://www.xmpp.org/extensions/xep-0180.html#ns" and "http://www.xmpp.org/extensions/xep-0180.html#ns-errors"; upon advancement of this specification, the ®ISTRAR; shall issue permanent namespaces in accordance with the process defined in Section 4 of &xep0053;.

 -

The XMPP Registrar shall include 'http://jabber.org/protocol/jingle/info/dtmf#rtp' in its registry of service discovery features.

+

The XMPP Registrar shall include 'http://www.xmpp.org/extensions/xep-0181.html#ns-rtp' in its registry of service discovery features.

 @@ -157,8 +163,8 @@