%ents; ]>
Jingle DTMF This specification defines an XML format for encapsulating Dual Tone Multi-Frequency (DTMF) events in informational messages sent within the context of Jingle audio sessions, e.g. to be used in the context of Interactive Voice Response (IVR) systems. Note well that this format is not to be used in the context of RTP sessions, where native RTP methods are to be used instead. &LEGALNOTICE; 0181 Experimental Standards Track Standards Council XMPP Core XEP-0166 NOT_YET_ASSIGNED &stpeter; &seanegan; 0.11 2008-09-23 psa

Clarified that use of this protocol is discouraged for RTP-aware applications and is designed only for communication with endpoints that do not support RTP.

 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 psa

Removed negotiation flow so that this specification describes only the XMPP transport of DTMF events; added error flows to be used if the code is not understood or if a non-XMPP method is preferred.

 0.8 2008-03-20 psa

Clarified negotiation flow; added payload-types per RFC 4733.

 0.7 2007-11-27 psa

Editorial review and consistency check; corrected the schema.

 0.6 2007-06-20 psa

Corrected several errors and updated to reflect changes to core Jingle spec.

 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 se/psa

Specified error handling and service discovery.

 0.3 2006-07-12 se/psa

Updated syntax to use action and code attributes rather than tone element in order to provide real-time interaction; specified how to negotiate use of the RFC 4733 format via content-info messages.

 0.2 2006-06-29 psa

Allowed characters A, B, C, and D; updated schema.

 0.1 2006-03-23 psa

Initial version.

 0.0.1 2006-03-21 psa First draft.

Traditional telephony systems such as the public switched telephone network (PSTN) use Dual Tone Multi-Frequency (DTMF) events for dialing and to issue commands such as those used in interactive voice response (IVR) applications. Internet telephony systems also use DTMF tones, usually for interoperability with the PSTN but sometimes also in native Internet services.

XMPP applications that use &xep0166; and the Real-time Transport Protocol (&rfc3550;) for voice chat as described in &xep0167; MUST support and prefer native RTP methods of communicating DTMF information, in particular the "audio/telephone-event" and "audio/tone" media types. Such applications SHOULD NOT use the protocol described herein for communicating DTMF information with RTP-aware endpoints.

However, XMPP applications MAY support and use the protocol described herein for communicating DTMF information with endpoints that are not RTP-aware, such as gateways to the PSTN.

The format for the representation of DTMF events over XMPP is as follows &VNOTE;:

]]>

The <dmtf/> element MUST be empty.

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

Attribute Definition Example Inclusion
code 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.). # REQUIRED
duration The 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). 400 RECOMMENDED
volume The 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. 37 OPTIONAL

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

]]>

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

]]>

If the receiving entity does not support this protocol, it MUST return a &unavailable; stanza error.

]]>

If the receiving entity does not understand the specified code, it MUST return a &feature; stanza error.

]]>

If the receiving entity is using or wishes to use a different method for exchanging DTMF events (e.g., the methods specified in &rfc2833; or its successor &rfc4733;), it MUST return a ¬acceptable; stanza error.

]]>

If an entity supports Jingle DTMF (i.e., sending of DTMF in the XMPP signalling channel as specified herein), it MUST return a &xep0030; feature of "urn:xmpp:jingle:dtmf:0" in response to service discovery information requests.

In order for an application to determine whether an entity supports this protocol, where possible it SHOULD use the dynamic, presence-based profile of service discovery defined in &xep0115;. However, if an application has not received entity capabilities information from an entity, it SHOULD use explicit service discovery instead.

This document introduces no known security vulnerabilities.

This document requires no interaction with &IANA;.

This specification defines the following XML namespace:

  • urn:xmpp:jingle:dtmf:0

Upon advancement of this specification from a status of Experimental to a status of Draft, the ®ISTRAR; shall add the foregoing namespace to the registry located at &NAMESPACES;, as described in Section 4 of &xep0053;.

 &NSVER; ]]>

Thanks to Diana Cionoiu, Olivier Crête, Robert McQueen, and Paul Witty for their feedback. Several sentences were borrowed from RFC 4733.