From 4bb19ddbf6b0eb0fc639ab2ce999d38f7c8ce984 Mon Sep 17 00:00:00 2001 From: Peter Saint-Andre Date: Tue, 31 Oct 2006 20:02:54 +0000 Subject: [PATCH] 0.4 git-svn-id: file:///home/ksmith/gitmigration/svn/xmpp/trunk@140 4b5297f7-1745-476d-ba37-a9c6900126ab --- xep-0181.xml | 33 ++++++++++++++++++++++++++++----- 1 file changed, 28 insertions(+), 5 deletions(-) diff --git a/xep-0181.xml b/xep-0181.xml index a292031a..398c4364 100644 --- a/xep-0181.xml +++ b/xep-0181.xml @@ -23,6 +23,12 @@ jingle-dtmf &stpeter; &seanegan; + + 0.4 + 2006-10-31 + se/psa +

Specified error handling and service discovery.

 + 0.3 2006-07-12 @@ -56,8 +62,7 @@ + code='integer'/> ]]>

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.

@@ -73,14 +78,21 @@ sid='a73sjjvkla37jfea'> + action='button-up'/> ]]> +

The receiving entity MUST send an IQ result if it can process the DTMF:

+ + ]]> +

If the receiving entity does not understand or cannot process the payload, it MUST return an appropriate XMPP error (such as &unavailable; or &unexpected;).

-

Some applications may want to stream Jingle voice RTP directly to a non-XMPP entity, such as a SIP phone. In this scenario, DTMF needs to be sent in the content channel. Jingle DTMF allows to Jingle entities to negotiate whether to send RTP over the XMPP signalling channel as described above, or over the content channel, using RFC 2833.

+

Some applications may want to stream Jingle voice RTP directly to a non-XMPP entity, such as a SIP phone. In this scenario, DTMF needs to be sent in the content channel. Jingle DTMF enables Jingle entities to negotiate whether to send RTP over the XMPP signalling channel as described above, or over the content channel using RFC 2833.

To request that the voice session switches to RFC 2833, a client sends a <dtmf-method/> element, qualified by the 'http://jabber.org/protocol/info/dmtf' namespace as the payload of a Jingle content-info message:

 + +

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.

+ +

This document introduces no known security vulnerabilities.

 +

This document requires no interaction with &IANA;.

 +

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

 + +

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

+ +