moparisthebest/xeps
1
0
Fork 0
mirror of https://github.com/moparisthebest/xeps synced 2024-11-24 10:12:19 -05:00
Code Issues Releases Wiki Activity

0.5

Browse Source 
git-svn-id: file:///home/ksmith/gitmigration/svn/xmpp/trunk@292 4b5297f7-1745-476d-ba37-a9c6900126ab
This commit is contained in:
Peter Saint-Andre 2006-12-21 21:26:52 +00:00
parent ce6655724b
commit 87dbc9f8e0
1 changed files with 20 additions and 14 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

34
xep-0181.xml
View File

@ -20,9 +20,15 @@
</dependencies>
<supersedes/>
<supersededby/>
<shortname>jingle-dtmf</shortname>
<shortname>TO BE ASSIGNED</shortname>
&stpeter;
&seanegan;
<revision>
<version>0.5</version>
<date>2006-12-21</date>
<initials>psa</initials>
<remark><p>Defined schema for error namespace; modified spec to use provisional namespace before advancement to Draft (per XEP-0053).</p></remark>
</revision>
<revision>
<version>0.4</version>
<date>2006-10-31</date>
@ -66,17 +72,17 @@
]]></example>
<p>The &lt;dtmf/&gt; 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.</p>
<p>Unless, the 'action' attribute is 'button-up', the &lt;dmtf/&gt; 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. <note>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.</note></p>
<p>The &lt;dtmf&gt; element SHOULD be sent as the payload of a Jingle content-info message as illustrated in the following example.</p>
<p>The &lt;dtmf&gt; element SHOULD be sent as the payload of a Jingle content-info message as illustrated in the following example. (See <link url='#ns'>Protocol Namespaces</link> regarding issuance of a permanent namespace.)</p>
<example caption="Entity Sends DTMF Message"><![CDATA[
<iq from='juliet@capulet.com/balcony'
to='ivr.shakespeare.lit'
id='dtmf1'
type='set'>
<jingle xmlns='http://jabber.org/protocol/jingle'
<jingle xmlns='http://www.xmpp.org/extensions/xep-0166.html#ns'
action='content-info'
initiator='juliet@capulet.com/balcony'
sid='a73sjjvkla37jfea'>
<dtmf xmlns='http://jabber.org/protocol/jingle/info/dtmf'
<dtmf xmlns='http://www.xmpp.org/extensions/xep-0181.html#ns'
code='7'
action='button-up'/>
</jingle>
@ -99,11 +105,11 @@
to='ivr.shakespeare.lit'
id='dtmf2'
type='set'>
<jingle xmlns='http://jabber.org/protocol/jingle'
<jingle xmlns='http://www.xmpp.org/extensions/xep-0166.html#ns'
action='content-info'
initiator='juliet@capulet.com/balcony'
sid='a73sjjvkla37jfea'>
<dtmf-method xmlns='http://jabber.org/protocol/jingle/info/dtmf' method='rtp'>
<dtmf-method xmlns='http://www.xmpp.org/extensions/xep-0181.html#ns' method='rtp'>
</jingle>
</iq>
]]></example>
@ -123,15 +129,15 @@
type='error'>
<error type='cancel'>
<feature-not-implemented xmlns='urn:ietf:params:xml:ns:xmpp-stanzas'/>
<unsupported-dtmf-method xmlns='http://jabber.org/protocol/jingle/info/dtmf#errors'/>
<unsupported-dtmf-method xmlns='http://www.xmpp.org/extensions/xep-0181.html#ns-errors'/>
</error>
</iq>
]]></example>
</section1>
<section1 topic='Service Discovery' anchor='disco'>
<p>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.</p>
<p>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.</p>
<p>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.</p>
<p>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.</p>
</section1>
<section1 topic='Security Considerations' anchor='security'>
@ -143,11 +149,11 @@
</section1>
<section1 topic='XMPP Registrar Considerations' anchor='registrar'>
<section2 topic='Protocol Namespaces' anchor='registrar-ns'>
<p>The &REGISTRAR; shall include 'http://jabber.org/protocol/jingle/info/dtmf' in its registry of protocol namespaces.</p>
<section2 topic='Protocol Namespaces' anchor='ns'>
<p>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 &REGISTRAR; shall issue permanent namespaces in accordance with the process defined in Section 4 of &xep0053;.</p>
</section2>
<section2 topic='Service Discovery Features' anchor='registrar-disco'>
<p>The XMPP Registrar shall include 'http://jabber.org/protocol/jingle/info/dtmf#rtp' in its registry of service discovery features.</p>
<p>The XMPP Registrar shall include 'http://www.xmpp.org/extensions/xep-0181.html#ns-rtp' in its registry of service discovery features.</p>
</section2>
</section1>
@ -157,8 +163,8 @@
<xs:schema
xmlns:xs='http://www.w3.org/2001/XMLSchema'
targetNamespace='http://jabber.org/protocol/jingle/info/dtmf'
xmlns='http://jabber.org/protocol/jingle/info/dtmf'
targetNamespace='http://www.xmpp.org/extensions/xep-0181.html#ns'
xmlns='http://www.xmpp.org/extensions/xep-0181.html#ns'
elementFormDefault='qualified'>
<xs:element name='dtmf'>