moparisthebest
/
xeps
mirror of https://github.com/moparisthebest/xeps
1
0
Fork 0
Code Issues Releases Wiki Activity

RFC 4733 supersedes 2833 

git-svn-id: file:///home/ksmith/gitmigration/svn/xmpp/trunk@311 4b5297f7-1745-476d-ba37-a9c6900126ab
This commit is contained in:
Peter Saint-Andre 2007-01-04 18:48:31 +00:00
parent a92beb0f31
commit 66a8cbbc17
2 changed files with 6 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
xep-0181.xml
View File

@ -39,7 +39,7 @@
<version>0.3</version>
<date>2006-07-12</date>
<initials>se/psa</initials>
<remark><p>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 2833 format via content-info messages.</p></remark>
<remark><p>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.</p></remark>
</revision>
<revision>
<version>0.2</version>
@ -97,10 +97,10 @@
]]></example>
<p>If the receiving entity does not understand or cannot process the payload, it MUST return an appropriate XMPP error (such as &unavailable; or &unexpected;).</p>
</section1>
<section1 topic='Negotiating RFC 2833' anchor='2833'>
<p>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.</p>
<p>To request that the voice session switches to RFC 2833, a client sends a &lt;dtmf-method/&gt; element, qualified by the 'http://jabber.org/protocol/info/dmtf' namespace as the payload of a Jingle content-info message:</p>
<example caption="Client requests using RFC 2833"><![CDATA[
<section1 topic='Negotiating RFC 4733' anchor='4733'>
<p>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 &rfc4733;.</p>
<p>To request that the voice session switches to RFC 4733, a client sends a &lt;dtmf-method/&gt; element, qualified by the 'http://jabber.org/protocol/info/dmtf' namespace as the payload of a Jingle content-info message:</p>
<example caption="Client requests using RFC 4733"><![CDATA[
<iq from='juliet@capulet.com/balcony'
to='ivr.shakespeare.lit'
id='dtmf2'

1
xep.ent
View File

@ -397,6 +397,7 @@
<!ENTITY rfc4566 "<span class='ref'>RFC 4566</span> <note>RFC 4566: SDP: Session Description Protocol &lt;<link url='http://www.ietf.org/rfc/rfc4566.txt'>http://www.ietf.org/rfc/rfc4566.txt</link>&gt;.</note>" >
<!ENTITY rfc4622 "<span class='ref'>RFC 4622</span> <note>RFC 4622: Internationalized Resource Identifiers (IRIs) and Uniform Resource Identifiers (URIs) for the Extensible Messaging and Presence Protocol (XMPP) &lt;<link url='http://www.ietf.org/rfc/rfc4622.txt'>http://www.ietf.org/rfc/rfc4622.txt</link>&gt;.</note>" >
<!ENTITY rfc4646 "<span class='ref'>RFC 4646</span> <note>RFC 4646: Tags for Identifying Languages &lt;<link url='http://www.ietf.org/rfc/rfc4646.txt'>http://www.ietf.org/rfc/rfc4646.txt</link>&gt;.</note>" >
<!ENTITY rfc4733 "<span class='ref'>RFC 4733</span> <note>RFC 4733: RTP Payload for DTMF Digits, Telephony Tones, and Telephony Signals &lt;<link url='http://www.ietf.org/rfc/rfc4733.txt'>http://www.ietf.org/rfc/rfc4733.txt</link>&gt;.</note>" >
<!-- Internet-Drafts -->